...
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:
- To review the Radio Edge Cloud Documentation and get back to Paul Carver via mail as a result to Paul Carver's input that there had been not changes/updates.
- To get back to AI Edge with information about the possibility to re-schedule preferably for Monday, Nov., 7th, and get back in written either today Friday or on the weekend.
- To go through the documentaiton on Predictive Maintenance and get back to Vladimir Suvorov via mail.
- The following remarks had been provided during the Documentation review of the BP on 5G Telco Edge (EALTEdge):
- to update the Akraino logo with the latest one without the term "Edge Stack" to avoid infringement rights violation
- to refer explicitly to the BPs through which 5G connectivity is provided and the BP Enterprise Application works as currently there is an indication on the respective BP Family. It is also recommended to provide a reference to an internal Road Map development when it is tentativel plannes (in the Road Map, e.g. Q2 2021 or Q3, 2021) to deliver the intergation so that recipeients know that there is a preliminary plan for the BPs connectivity to 5G as indicated in the BP and threin E2E functionality compliance.
- to verify with the Akraino API subcommittee about the BPs reference to ETSI MEC MEP internal references to be denoted/treated as APIs
- the above remark on the APIs and possible mismatch between "ETSI MEC MEP internal inerfaces (3 groups on defined as Mx (external), Mp (internal) and Mm (on Management) is related to explicit indication on any APis that are used whether being compliant to Open API initiative 3.0 (on Open APis.org).
Since the respective documentation review of 1 (one) BP took a whole hour and it was inidcated that previously, there had been provided time slots only for 2 BPs Documentaiton Review during a Documentation Sub.committee review, the previous procedure to ´have 2 (two) BPs documentation review per TSC session is reinforced.
12/11 schedule
1/ 7:00 am – 7:15 am PDT- Intergrated Cloud Native Kuralamudhan Ramakrishnan
...
4/ 7:45 am – 8:00 am - Connected Vehicle Blueprint(Aka CVB) Tao Wang
12/18 schedule
1/ 7:00 am – 7:15 am PDT
3/ 7:30 am- 7:45 am-
4/ 7:45 am – 8:00 am -
1/8/2021 schedule
1/ 7:00 am – 7:15 30 am PDT
2/7:15 30 am – 78:30 00 am - 3
1/8/2021 schedule
1/ 7:30 00 am - – 7:45 30 am - PDT
1/15/2021 schedule
1/ 7:00 am – 7:15 am 30am PDT
3/ 7:30 am- 7:45 am-
4/ 7:45 am – 8:00 am - PDT
Rel 3 Final Documentation and Milestone Review
...