...
- Storage: discussion was led by John Hartley. As an outcome, John is planning to:
- Review RA-1 and Ra-2 storage contents to plan a consistent storage story across these three specs
- Comments directed to the storage story to be: application and use case driven, conceptual rather than technology specific
- Create detailed GitHub issues following form an overall Issue #2056; these issues will (after discussion and approval of RM meeting) create the scope for Lakesle
- Automation for Cloud Infrastructure: discussion led by Saad. As an outcome, Saad is planning to:
- Review the proposed contents against the existing specs (RA-x, RC-x)
- Clarify what aspects are specific to IaC vs general CI/CD pipeline (which generally would be out of the Anuket scope)
- Clarify delineation between VNF/CNF and Network layers, as per the discussion at the meeting
- Present the updated contents for further discussion and acceptance by the RM meeting, which will allow creation of respective GitHub Issues to define the Laksle scope for this topic
- Semantic Networking: discussion led by Per. As an outcome, Per is planning to:
- Move the contents of PR#2546 to RA-2
- Create a new Issue/PR for RM to discuss the topic on a conceptual level (not on K8s level) as an introductory material for the RA-2 detailed K8s discussion.
- Hardware Acceleration: discussion led by Petar. As an outcome, Petar is planning to:
- Align/map our contents (especially in and around diagram Fig 3-17) to the model discussed in ORAN O-RAN.WG6.AAL-GAnP-v01.00.pdf (especially around ORAN's Acceleration Layer concept)
- Multi-cloud: discussion postponed to the next RM meeting due to the lack of time
- Previous comments fromthe team:
- Review of PRs
- PR#2486: Per to summarise thus topic in RM, but move the K8s details into RA2; discuss at the next RM Meeting
- We reviewed and agreed on the Lakelse topics and their prioroties: Lakelse Specification Planning Dashboard - Anuket - Anuket
- Focus on: Storage, Multi-cloud scope for Lakelse, Network semantics PR#2486 - review, Hardware acceleration
- Multi-cloud scope: Needs to be use case driven:
- see sample use cases: ETSI GR MEC 035 V3.1.1 (2021-06): Multi-access Edge Computing (MEC); Study on Inter-MEC systems and MEC-Cloud systems coordination Inter-MEC-cloud-systems-coordination-ETSI-gr_mec035v030101p-2021-06.pdf
- For OPG see their latest PRD document OPG.02-v1.0.pdfPotential topics:
- Centralised vs autonomous distributed control
- Orchestration across multi-cloud
- How to provide connectivity between different clouds/sites Infrastructure as code
- Management across multi-cloud
- Multi-cloud security, Walter volunteered to run with this: Issue#2314
- Terminology, what to use? Perhaps from OPG?
- Hardware acceleration
- RM is complete according to Petar; anything missing? Otherwise we can close the topic.
- ORAN acceleration layer which perhaps should be reflected in RM: O-RAN.WG6.AAL-GAnP-v01.00.pdf
- RA-2 is almost complete
- How to reflect it in RA-1? Planned for Lakesle
- Test cases
- Implementation
- Lakelse Schedule - Anuket - Anuket
- M2 (Scope Freeze) - August 31
- Infrastructure LCM Automation (9.5.1) - owned by Saad, issue 2087
- Security updates - owned by Karine- issues 2314, 2481, 2482, 2540, 2541, 2542
- Storage - owned by John Hartley - Issue 2056
- PaaS services inclusion - owned by Pankaj - create new issues AP on Pankaj - mid August, based on survey results
- Suggested by Pankaj new topic: Virtual data path acceleration (vDPA). Experts needed.
Actions:
...