...
Meeting last week. An open dialog with ONAP & EMCO, both doing orchestration but a different layer. Using 5G SBP as vehicle to make proposals back to their communities. EMCO is offering a cloud agnostic layer and ONAP benefits from this. We intend to develop a joint message/positioning statement to be reviewed in the ONAP and EMCO TSCs. Goal: Identify the integration points. There may be some areas of overlap for some use cases ,
Workplan -
- ONAP/Magma Integration
- :
- CBA development to automatically register the Magma AGW with the Magma 'Controller' is complete
- Trying out the Magma Helm Chart workaround while Wavelabs works on updating the Helm Charts
- On the Helm Charts, there are two paths: short-term (Aarna) Yogen will try to workaround forcing the namespaces to be the same. Long-term fix; K8s resources need to be installed in different namespaces, and therefore be split into separate Helm packages (Wavelabs). The long term fix is a best practice offered on ONAP for Enterprise community and should be documented.
- Slicing-
- From ONAP for Enterprise Meeting: Jorge Hernandez Review any KPI Network Slicing requirement to be submitted to the Magma team - working with Kader Khan 's team.
- Principle/approach to consider VES as ONAP/Magma segways for KPI Collection sounds to be OK - no push back
- Suggestion was to work with Kader Khan 's team to define requirements, architecture (high/low) and E2E flows but no commitment about implementation
- Potential POC with basic flows between ONAP/Magma including DCAE/VES collectors
- Potential ONAP contribution to Magma code directly to support this use case?
- Kaloom was able to fix the firewall issues and now we have the high and low video use case working through the 2 different slices
- Next Step: gather requirements for slicing. Working with the Magma team.
- From ONAP for Enterprise Meeting: Jorge Hernandez Review any KPI Network Slicing requirement to be submitted to the Magma team - working with Kader Khan 's team.
- Radio
- GenXComm Radio. Can we start using it? Intel/integration issue. GenXComm coming on as a member.
- Labs for 2022: UNH Solid, Kaloom still on board? Do we need CENGN?
- Louis reached out to Kaloom for documentation above and broach lab question.
- Rebaca/Magma:
- Kader (Wavelabs)- successfully tested ABot with basic 5G Magma call. Youtube demo (timestamp 11:49): https://www.youtube.com/watch?v=E03Qu9btX3o&list=PLQ88zlc9KWGfhOZsRdtqs6UbP9vEeUExz&index=4
- Next Step- integrate ABot with Magma CICD - in progress
- CICD pipeline running. Parthiban to share links
Document as you build
- Placeholder - Do we need separate call for 5GSPB phase Next for execution? (similar to weekly 5G Cloud Native Network demo). Alternate Tuesdays?
and these are being worked through. Catherine to start a draft message as a start (end to end flow will come later). Open Question: Will there be profile/blueprint variations? We are building an E2E Stack Framework. Naming will be important. Example: Emergency services blueprint, supply chain blueprint, etc. Open Question: What can we do within this context/resources as a Linux Foundation initiative. We need to define what we are doing and set expectations accordingly.
Workplan -
- ONAP/Magma Integration - Service Delivery
- :
- CBA development to automatically register the Magma AGW with the Magma 'Controller' is complete
- Trying out the Magma Helm Chart workaround while Wavelabs works on updating the Helm Charts
- On the Helm Charts, there are two paths: short-term (Aarna) Yogen will try to workaround forcing the namespaces to be the same. Long-term fix; K8s resources need to be installed in different namespaces, and therefore be split into separate Helm packages (Wavelabs). The long term fix is a best practice offered on ONAP for Enterprise community and should be documented.
- ONAP/Magma Integration - Service Assurance
- From ONAP for Enterprise Meeting: Jorge Hernandez Review any KPI Network Slicing requirement to be submitted to the Magma team - working with Kader Khan 's team.
- Principle/approach to consider VES as ONAP/Magma segways for KPI Collection sounds to be OK - no push back
- Suggestion was to work with Kader Khan 's team to define requirements, architecture (high/low) and E2E flows but no commitment about implementation
- Potential POC with basic flows between ONAP/Magma including DCAE/VES collectors
- Potential ONAP contribution to Magma code directly to support this use case?
- Kaloom was able to fix the firewall issues and now we have the high and low video use case working through the 2 different slices
- Next Step: gather requirements for slicing. Working with the Magma team.
- From ONAP for Enterprise Meeting: Jorge Hernandez Review any KPI Network Slicing requirement to be submitted to the Magma team - working with Kader Khan 's team.
- Radio
- GenXComm Radio. Can we start using it? Intel/integration issue. GenXComm coming on as a member.
- Labs for 2022: UNH Solid, Kaloom still on board? Do we need CENGN?
- Louis reached out to Kaloom for documentation above and broach lab question.
- Rebaca/Magma:
- Kader (Wavelabs)- successfully tested ABot with basic 5G Magma call. Youtube demo (timestamp 11:49): https://www.youtube.com/watch?v=E03Qu9btX3o&list=PLQ88zlc9KWGfhOZsRdtqs6UbP9vEeUExz&index=4
- Next Step- integrate ABot with Magma CICD - in progress
- CICD pipeline running. Parthiban to share links
Document as you build
- Placeholder - Do we need separate call for 5GSPB phase Next for execution? (similar to weekly 5G Cloud Native Network demo). Alternate Tuesdays?
Yogendra: Working on a Helm chart issue by splitting them up. Access gateway. Small infra changes. We'll them be taking up the Magma orchestrator. Is there any specific help from Magma needed (Suresh)? Yes, that would be a great help (orchestrator charts). Suresh and Yogendra to synch offline. Helm chart fixes will require namespace changes (the ideal path). Status? Yogendra
Adjacent Communities 5G Super Blueprint Integration (All)
...