The Documentation Sub-committee objective is to promote a consistent documentation structure and quality assurance across both the Akraino Project level and all individual Blueprint Families. It also serves the Akraino TSC requirements to follow the Akraino Procedures aiming Quanlity assurance process and perform the required Documentation review.
...
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:
...
- 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)
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.
...
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
...