Skip to end of metadata
Go to start of metadata

Various Akraino Release Upstream Dependencies and Compliance Table


As of R4, in order to build a stable release (A release is a release which Downstream and Community can rebuild after a certain long period of time), Upstream will need to specify upstream repositories completely and with corresponding version/branch information. Also Upstream Sub-committee recommends to use tag instead of branch if possible.


R4 Requirement: (TO BE DISCUSSED in TSC)

  • If a BP has no code changes to upstream repositories, then it would just need to specify fully its upstream release versions in its release document, matching with its bluval testing versions.
  • If a BP has code changes to upstream repositories, then it would need to either merge the code into the upstream before the R4 release time frame and updates its release versions. If the code cant be merged the code into upstream timely, then the BP will not fit into the R4 (TBD).
  • Or an upstream fork is acceptable, but the fork should be locked before R4 release and the code should be merged back to upstream eventually.


R4 Release Review Status (In Progress, all BPs please follow the schedule)


Project NameUpstream DocumentReview DateUpstream Completion StatusComments
Connected Vehicle BlueprintRelease Note for R4
Yes

IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint FamilyRelease 4 Release Note-IEC Type4
Yes

Upstream Dependency Matrix and Upstream Project Information and Radio Edge Cloud Release 412/1/2020Yes

ICN - Integrated Cloud-Native FamilyUpstream Dependency Matrix and Upstream Project Information and ICN R4 Release Notes



ELIOT IoT Gateway BlueprintELIOT R4 - IoT Gateway Release Notes and match to the matrix Upstream Dependency Matrix and Upstream Project Information for IOT Gateway12/1/2020Yes

ELIOT SD-WAN/WAN Edge/uCPE BlueprintELIOT R4 - SD-WAN/ WAN Edge / uCPE Release Notes#UpstreamSoftwareVersionchanges12/6/20202Yes

Network Cloud and TF Integration Project




KNI Provider Access EdgeUpstream Dependency Matrix and Upstream Project Information



KNI Industrial EdgeUpstream Dependency Matrix and Upstream Project Information



Micro-MECRelease Notes for the MicroMEC Blueprint Release 3



The AI Edge: School/Education Video Security MonitoringVideo Security Monitoring R3 Release Notes



5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint




IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family




IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint FamilyR3 Release Notes of IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family
Need update to R4 (12/9/2020)

Enterprise Applications on Lightweight 5G Telco EdgeR4 - Release Notes of Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)12/9/2020Completed

Public Cloud Edge Interface (PCEI) BlueprintPCEI R4 Release Notes



The AI Edge: Federated ML application at edgeFederated ML application at edge R4 Release Notes



KubeEdge Edge Service Blueprint




Private LTE/5G ICN Blueprint




AI/ML and AR/VR applications at Edge




IoT Workloads at the Smart Device Edge - Predictive Maintenance (with a Thermal Imaging Camera, vibration sensors, etc.)IIoT Predictive Maintenance Release Notes



ELIOT AIoT in Smart Office Blueprint




Network Cloud with Tungsten FabricUpstream Dependency Matrix and Upstream Project Information and Network Cloud with Tungsten Fabric




IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family

Release 4 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge

01/15/2021


The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS)

I-VICS R4 Release Notes





Private 5G/LTE BlueprintUpstream Dependency Matrix and Upstream Project Information




  • No labels