Document Image Added

The Documentation Sub-committee : To objective is to promote a consistent documentation structure and quality assurance across both the Akraino Project level and all individual Blueprint Families through both the Akraino Wiki and specific whitepapers.

Please join the Documentation Sub-Committee mail list by self-adding within the Akraino Mail List Sub-Groups page. 

Sub-Committee Chair: Ike Alisson elected 17 Nov 2020 for one year.

Meeting Details:

Akraino Edge Stack 1 is inviting you to a scheduled Zoom meeting.

...

Join Zoom Meeting
https://zoom.us/j/651429670?pwd=QW16NGJXTmdUNHVVK3FXbkxKV3ZnUT09

Meeting ID: 651 429 670
Passcode: 883460
One tap mobile
+16699006833,,651429670# US (San Jose)
+12532158782,,651429670# US (Tacoma)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 646 558 8656 US (New York)
+1 . It also serves the Akraino TSC requirements to follow the Akraino Procedures aiming Quality assurance process and perform the required Documentation review.

About procedure to place a request for a Documentation review, please read/follow the instructions listed under Documentation Sub-committee Sub-catalogue titled "How to Request a Documentation review?

For further detailed information related to Documentation Sub-committee procedures and templates, you can look at the following sub-catalogues:

How to Request a Documentation Review?

Akraino Blueprint API Template

Akraino Blueprint Architecture Template

Akraino Blueprint Datasheet template

Akraino Blueprint Installation Guide Template

Akraino Blueprint Release Notes Template

Akraino Blueprint Test Template

Please join the Documentation Sub-Committee mail list by self-adding within the Akraino Mail List Sub-Groups page. 

Sub-Committee Chair: Ike Alisson elected 17 Nov 2020 for one year.

Meeting Details:

Akraino Edge Stack 1 is inviting you to a scheduled Zoom meeting.

Topic: Documentation and Release Planning
Time: Sep 25, 2020 07:00 AM Pacific Time (US and Canada)
Every week on Fri, until Sep 3, 2021, 50 occurrence(s)

Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://zoom.us/meeting/u5Esc-uhqDwqDEmrwbuc-hTf4Jwhm-b0VQ/ics?icsToken=98tyKu-trz8oE9KSsFyCd7UqW5nlb9_2k1Vrp7FKngrmTihnZFfcIepPf7AvJumB

Join Zoom Meeting
https://zoom.us/j/651429670?pwd=QW16NGJXTmdUNHVVK3FXbkxKV3ZnUT09

Meeting ID: 651 429 670
Passcode: 883460
One tap mobile
+16699006833,,651429670# US (San Jose)
+12532158782,,651429670# US (Tacoma)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
855 880 1246 US Toll-free
877 369 0926 US Toll-free
+1 587 328 1099 Canada
+1 647 374 4685 Canada
+1 647 558 0588 Canada
+1 778 907 2071 Canada
+1 204 272 7920 Canada
+1 438 809 7799 Canada
855 703 8985 Canada Toll-free
Meeting ID: 651 429 670
Find your local number: https://zoom.us/u/abS2XFh8ku

...

Documentation sub-committee members(From Nov 2023~): 

We have started the process to elect a new chair for the Documentation sub-committee.  The process started on 23 Nov and will continue until Noon 15 Dec 2023 (Pacific)  

The election process is two steps.  The first is for people to self-nominate for the position.  To do this, put a Y in the correct column if you wish to run for Chair.  The second step is to have an election for the position.  If there is only one person who has self nominated, then that person will be chair.  

Note: Please ensure that both the name and email address for each member is listed on each sub-committee membership wiki page in order to properly set up CIVS voting when required. 

Interested parties sign up:

Documentation sub-committee members(From Nov 2020~Nov 2023): 

Note: Election Nov 5 2020- Unfortunately Samir has notified the TSC that he will not be able to continue as Chair.  Thus we are opening up the self-nomination process.  Please put a Y in the Self-nomination column if you wish to be chair.  If not, please put an N.  This process will go until Noon on 12 Nov (Pacific time).  If there is only one self nominee then that person will become chair.  If there are two or more, we will have an election. 

Interested parties sign up:

...

Friday 11/20/2020 Pacific

1/ 7:00 am – 7:15 am The AI Edge: School/Education Video Security Monitoring, Hechun Zhang

2/ 7:15 am – 7:30 am 

...

3/ 7:30 am- 7:45 am- Predictive Maintenance (with a Thermal Imaging Camera, vibration sensors, etc.)

4/ 7:45 am – 8:00 am -  Release 4 Documentation - Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)

Meeting Notes:

On Friday, 12/04, there had been a substantial failure in planing BPs review. There could be made review only of the BP on Lightweight 5G Telco Edge (EALTEdge). For ther other 3 (three) BPs, the following had been indicated briefly during the session:

...

1/ 7:00 am – 7:15 am PDT- Intergrated Cloud Native Kuralamudhan Ramakrishnan (Deactivated)

2/7:15 am – 7:30 am -  Network Cloud with Tungsten Fabric Sukhdev Kapur

3/ 7:30 am- 7:45 am- IEC Type 4 AR/VR Bart Dong

4/ 7:45 am – 8:00 am - Connected Vehicle Blueprint(Aka CVB) Tao Wang

Meeting Notes:

There were conducted 2 reviews, namely BP IEC Type 4 AR/VR and BP Connected Vehicles (Aka CVB). Both BPs are in co-operation. CVB PTL, Tao Wang elaborated on the issue/status with the BPs APIs and that it had already been reviewed/discussed with the Akraino TSC API Sub-committee and agreed on it. No major issues in the documentation. There had been conveyed a remark on elaborating the status with the UC(s) so that the reader is aware where the BPs are used.

...

1/ 7:00 am – 7:30 am PDT 

2/7:30 am – 8:00 am -  

1/8/2021 schedule

1/ 7:00 am – 7:30 am PDT Public Cloud Edge Interface (PCEI) Blueprint Family Oleg Berzin

2/7:30am – 8:00 am - 

Meeting notes:

The following remarks shall be treated as "recommendations" pursuing enhancements/improvements and in no way treated as "mandatory" to follow and/or implement.

...

1/ 07:00 am - 07:30 am PDT - 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint Zigeng Fu Feng Yang

2/ 07:30 am - 08:00 am PDT

...

1/ 07:00 am - 07:30 am PDT IEC type 5 SmartNIC Yihui Wang

2/ 07:30 am - 08:00 am PDT

2/05/2021 schedule

1/ 07:00 am - 07:30 am PDT

2/ 07:30 am - 08:00 am PDTMeeting notes:

The documentation is well prepared and detailed. The Architecture and HW and SW is well specified. The installation and verification are also well specified. There is elaboration on the differences between Rel 3 and Rel 4. In the Installation documentation there is also provided verification instructions. The performed tests are made on load throughput. The latency is left outside as it is dependant on UC Latency requirements. On the Test document, there shall be made some minor refinements to avoid misunderstandings from the text as it is presented the "tested and deployed Architecture" rather than ( as indicated in the text) "The Test Architecture".

Akraino TSC is recommended to accept and thereby, approve the BPs presented set of Documentation for Akraino Rel 4.

2/ 07:30 am - 08:00 am PDT

2/05/2021 schedule

1/ 07:00 am - 07:30 am PDT  IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family hanyu ding

2/ 07:30 am - 08:00 am PDT

2/24/2021 Presentations on Amazon AI ML Platform (SageMaker) Algorithms, Models

The following presentations are listed below:

1. Amazon Innovate Opening Key notes

2. From PoC to Strategies for achieving ML at Scale

3. How do you innovate to drive Business outcomes

4. Use of AI ML to enhance the Customer Experience

5. Closing Keynotes

2/25/2021 Review/Meeting notes

Documentation review of Blueprint "The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System (I-VICS) is done over e-mail.  Akraino Rel 4 Blueprint Documentation set at link: The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS).

All the required Blueprint's docs for Akraino Rel 4 are available and well prepared. There is provided reference to the utilized Blueprint's Open Source Platform SW (with link to the tool needed for Installation of SW as part of the Platform SW,namely, ROS2 - Robot Operating System 2) and support for 2 UCs namely, "Valet parking" and "SOTIF - Safety of the Intended Functionality".  There is provided reference to HW list for a demo with Lexus RX 450h case. In the Installation Guide" document, the needed HW is specified. The Release document addresses mainly UC SOTIF. The Blueprint's APIs are based on FATE (Federated AI Technology Enabler), which is an Open-Source Project initiated by Webank’s AI Department to provide a Secure Computing Framework to support the Federated AI ecosystem.It seems that the current Blueprint HW and SW configueration is an outcome of Test/Trial/PoC (with Lexus RX 450h). The Blueprint had also added a document "Landing Applications", that provides a list of other Akraino Blueprints that can potentially run (as Application(s)) on the Blueprint (as a Platform). There is also a room for evolvement for the Blueprint to utilize the V2X UC specification(s) in ETSI MEC and 3GPP 5G for V2X SST.

It is recommended to Akraino TSC to accept the "AI Edge I-VICS" Blueprint documentation and deem them as "approved/eligible" for Akraino Rel. 4.

05 May 2021 Video Security Monitoring Rel. 4 Documentation Review/Meeting notes, PTL Liya Yu.

Documentation review of Blueprint " Video Security Monitoring Release 4 Documentation" Rel. 4 is done over e-mail. All the required Blueprint's docs for Akraino Rel 4 are available and well prepared. The following remarks shall be considered as advisory and as a recommendation rather as mandaroty and subject to be used a ground for changein the BP's Documentation text:

• In the API document. There is not an explicit reference to Open API Specification (OAS https://spec.openapis.org/oas/v3.1.0) and if the API structure follows it. In the Architecure Document, there is justa title "Open API. In case that BP follows OAS, it is recommended to explicitly state that in the BP's API Document. The API document is thorough. It is follows any Architecture Standard API structure, it is recommended to also explicitly refere to it.
• In the Architecure Document, there is used the abbrerviation MEC. As "MEC" abbreviation is used by the ETSI MEC and respective Standard Solution Architecture, in case that the BluePrint follows the ETSI MEC Architecture Standard Specification, then it is recommended to use its complete denomination (ETSI MEC). If not, it is recommended not to use the abbreviation MEC, but its full name. The presented Architecture figures present the call flow based on Kubernetes (K3S Light and K8S). There is lack of indication of used interfaces and protocols. Therein, the respective presentation is just a "Diagram" rather than an "Architecure". It is recommended to indicate respective "Protocls" and "Interfaces" to indicate connections and/or dependencies. With regard to AI, there is harldy any information. It is recomended to add information about the utlized ML Algorithms, Type of Models and Models Training Approach, used Data Granularity and Charactristics for Training models, How the "test case data" is treated with regard to CNN RLU (to start with).
• Installation Document is thorough and detailed. It is recommended to update with a Section related to ML (AI) Data handling/treatment and New Data gathering, Storage, Update and use for ML Model build-up and Algorithm(s) training.
• Related to "Release" Document, it is recommended to provide the BP's Roadmap with respective Releases (Features, Functionalities, Dependancies, Security and Time Table) and with respect to that refer to what is new related to Akraino Rel. 4. It is impossible to understand how the Solution/Product/Platform is planned to be evolved.
• On the Security Test Document, it is preferable for the Akraino TSC to receive the Akraino Security Sub-committee assessment analysis.

Attached below 5G General Performance Requirements for Video Production Applications & Airborne Base Stations for NPN (Non Public Network)

Image Added  Image Added

Assessment summary and Recommendation to Akraino TSC: Overall assessment is that the BP's Documentation for Akraino Rel 4 is well prepared and thorough for each Part. There is a good overview on the overall Solution and related UCs. Therein, it is recommended to the Akraino TSC to deem the BP's Rel. 4 Documentation as accepted.

3. Rel 3 Final Documentation and Milestone Review

19 May 2020 Documentation Report: All the BPs besides the ones listed below are good to go:

...

3/ 8:30 am- 8:45 am-

4/ 8:45 am – 9:00 am - Radio Edge Cloud (REC), Paul Carver

Meeting Notes:

...

1/ 7:00 am – 7:15 am PDT- 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint, Feng Yang

2/7:15 am – 7:30 am PDT - 

...

1/ 7:00 am – 7:15 am PDT- The AI Edge: School/Education Video Security Monitoring, Hechun Zhang

2/7:15 am – 7:30 am - 

3/ 7:30 am- 7:45 am- AI/ML and AR/VR applications at Edge Vikram Siwach

4/ 7:45 am – 8:00 am- Enterprise Applications on Lightweight 5G Telco Edge, khemendra kumar  Abhijit Dasgupta

...

1/6:00 am - 6:15 am PDT - IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family, JiaXuan Tiejun Chen 

1/6:15 am - 6:30 am PDT - Public Cloud Edge Interface (PCEI) Blueprint, cmti CA

1/6:30 am - 6:45 am PDT - Network Cloud and TF Integration Project, Sukhdev Kapur

1/6:45 am - 7:00 am PDT - 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint Feng Yang

Meeting Notes:

SmartNIC: Accepted no Comments

...

1/ 7:00 am – 7:15 am PDT- IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family thorking Mark Shan

2/7:15 am – 7:30 am - Intergrated Cloud Native Kuralamudhan Ramakrishnan (Deactivated)

3/ 7:30 am- 7:45 am- Connected Vehicle Blueprint(Aka CVB) thorking Jim Xu (Deactivated) Mark Shan

...

1. Table of Content is missing from some of the documents. This needs to be added
2. Architecture Document:
   1. Component Description does not include a description of all the components.
   2. There is no description of the Application that would have to be deployed on top of the OTE. There need to be some details on the application used to validate the functions of the OTE; along with criteria of other possible applications that can be used
3. Installation Docuement: 
   1. There is a DB that is used to configure OTE. The DB Schema Script to configure OTE is provided, but there needs to be some description of what is being configured and the different tables referred to in the Schema. Without it, users outside the BP team referred to in the Schema. Without it, users outside the BP team will not be able to use it.
   2. The OTE Web portal is a critical piece of the BP. It is used to bring up the framework, configure things, deploy an application and monitor whether the BP is working. However, this portal is in Chinese. Hence, someone who does not understand Chinese will not be able to use it.The OTE Web portal is a critical piece of the BP. It is used to bring up the framework, configure things, deploy an application and monitor whether the BP is working. However, this portal is in Chinese. Hence, someone who does not understand Chinese will not be able to use this BPthis BP

19/02 2021

Persentation to API TSC - subcommittee

View file
name DMTF Redfish Specification Jan 2021.pdf height 250

      

View file
name DMTF Redfish Scalable Platforms Management API Specification Aug 2018.pdf height 250

Release 2 Final Documentation and Milestone Review

11/01 - 

1/ 7:00 am – 7:15 am PDT- Micro-MEC, Tapio Tallgren, (absent, rescheduled to 11/22)

2/7:15 am – 7:30 am PDT - Connected Vehicle Blueprint, xin qiu (not complete,  rescheduled to 11/08)

3/ 7:30 am- 7:45 am- Radio Edge Cloud (REC), Paul Carver (absent, rescheduled to 11/22)

4/ 7:45 am – 8:00 am - Network Cloud and TF Integration Project,  @Sukhdev Kapur ( great start, some requirements are not met, follow up on 11/08)

...

New Final Review Schedule as on 11/01
11/08-  IEC Type 1 - Trevor Tao Cristina Pauna, Type 2-Cristina Pauna, xinhuili,  IEC Type 4,  Wen-Ping Ying Wenhui Zhang Tina Tsou, ELIOT AIOT, jereliu@tencent.com, Network Cloud and TF Integration Project,  Connected Vehicle Blueprint, xin qiu,

11/15- SEBA Aaron Byrd,  ICN,  Kuralamudhan Ramakrishnan,

11/20- Radio Edge Cloud (REC), Paul Carver

11/22-  Network Cloud Rover - David Plunkett ,  Network Cloud Unicycle with SR-IOV- David Plunkett,  Network Cloud Unicycle with OVS-DPDK, ELIOT IOT & SDWAN, khemendra kumar,

11/29-  KNI provider Access Edge, Yolanda Robla Mota, , AI ML, AR/VR application at the edge, Vikram Siwach, Radio Edge Cloud (REC), Paul Carver, IEC Type 4,  Wen-Ping Ying Wenhui Zhang Tina Tsou, ELIOT AIOT, jereliu@tencent.com,

...

10/04 -    Radio Edge Cloud (REC), Paul Carver,   ICN,  Kuralamudhan Ramakrishnan (Deactivated),  Network Cloud Unicycle with SR-IOVDavid Plunkett

Network Cloud and TF Integration Project, Sukhdev Kapur

10/11-   Micro-MEC, Tapio Tallgren, SEBA Julie Lorentzen 

...

10/25-AI/ML, AR/VR application at the edge, Vikram Siwach, ELIOT AIOT, IOT, SDWAN, Guoxu (Jeremy) Liu, khemendra kumar, Network Cloud and TF Integration Project, Sukhdev Kapur, KNI provider Access Edge, Yolanda Robla Mota, Connected Vehicle Blueprint, xin qiu , Network Cloud Rover, David Plunkett Starling X Bill Zvonar, IEC Type 2 Pauna, xinhuili,

...

Documentation Readiness Discussion for Rel 1

04/26 7:00 am PDT – Unicycle for NEC & Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family -david.plunkett@att.com

05/03  7:00 am PDT-  OVS-DPDK Unicycle Dell Blueprint Proposal-  Rakesh Bohra <rakesh.bohra@ericsson.com>, 

                                   StarlingX Far Edge Distributed Cloud - Bill Zvonar,

                                   Eliot- Abhijit

05/10 7:00 am PDT – Kubernetes-Native Infrastructure for Edge (KNI-Edge) Family, Frank Zdarsky, Eliot- Abhijit

05/17 7:00 am PDT –  Edge Video Processing- adnan.saleem@radisys.com,  IEC Type 1 for Integrated Edge Cloud (IEC) Blueprint Family- trevor.tao@arm.com

05/24 6:00 am PDT –

IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family- lxinhui@vmware.com,  

 Edge Video Processing- adnan.saleem@radisys.com, 

 IEC Type 1 for Integrated Edge Cloud (IEC) Blueprint Family- trevor.tao@arm.com

Eliot IoT Gateway- khemendra.kumar@huawei.com 

         Radio Access Cloud pcarver@att.com

 19 Apr 2019 7:00 am PDT

...