Anuket Project
2021-12-06 - [Anuket RA-1] - Workstream Meeting Agenda and Minutes
Meetings Every Monday at 15:30 UTC
Zoom Meeting link: https://zoom.us/j/99279174971?pwd=eWozNENnYkpLSXdRSzZvblNKVU1wdz09
Attendees:
Name (Organisation) | will incorporate Participant report from Zoom.
Name |
|---|
@Cédric Ollivier |
@Ildiko |
@Karine Sevilla |
@Pankaj.Goyal |
As a courtesy to your colleagues please mute yourself when in listen mode. Thanks
Important Topics to cover:
RM Alignment
Important Information:
1. Lakelse Release Milestones | Lakelse Specification Planning Dashboard
Milestone | Date | Notes |
|---|
Meeting Recording: none
Agenda and Minutes
Agenda Bashing
Antitrust Policy: https://r.lfnetworking.org/Antitrust%20Slide.pdf and GSMA Anti-Trust Policy Notice
Next Release planning
Other Meetings
2022 LFN Developer & Testing Forum January Jan 10-13, 2022: PG to set up page for editing presentation
2022-01-DD - Anuket: AI/ML for NFV Usecases - Failure Prediction Models — Girish L Rohit Singh Rathaur30m
AI/ML for NFV Usecases
Page:
2022-01-DD - Anuket: Anuket Assured - How can we deliver on the Anuket Value Proposition for Cloud Infrastructure and Cloud Native Workloads? — 90m, Lincoln Lavoie, Scot Steele
Review the current Anuket value proposition, what has been accomplished thus far, what remains to be completed, and determine what we can accomplish in 2022.
Page:
2022-01-DD - Anuket: DevIntOps -- Agile Delivery of NFV — 30m
Brief introduction about Telco-vendors collaboration pattern - DevIntOps, which would leads to faster delivery and better quality of NFV in production ENV.
Page:
2022-01-DD - Anuket: Hybrid Multi-Cloud Infrastructure — 60m
Present current state of modelling Hybrid Multi-Cloud Infrastructure in Anuket Lakelse specifications in view of evolving telecommunications industry, and lead an open discussion on the topics requiring attention in future Anuket releases.
Page:
2022-01-DD - Anuket: Lakelse Retrospective — 60m / David McBride
Lakelse Release Retrospective
Page:
2022-01-DD - Anuket: RA-1 (OpenStack based) What's next? — 60 minutes
The intent is to solicit inputs for RA-1 in order to adjust the content of Moselle release.
Topics of interest: what else, acceleration, multi-cloud/hybrid cloud, Telco edge cloud, storage, and automation
Page:
2022-01-DD - Anuket: RA2 Status — 60m Riccardo Gasparetto Stori
What's new in Anuket RA2 - Cloud Native Reference Architecture in the Lakelse release & community discussion for Moselle release
Page:
2022-01-DD - Anuket: RC2 Glossary Definition & Path Forward — 60m
The RC2 project is in need of revamping. This hour will focus on 2 topics:
1) Defining a glossary of terms to support common understanding between RA, RC, and Rel Mgmt.
2) Identifying a path forward for the project to ensure the RA, RI, and RC project teams are in sync.
Page:
2022-01-DD - Anuket: RI2 - Path Forward — 60m
The intent of this session is to focus on the following topics -
What is the value of the RI2 Project in Anuket?
How can we increase the value of RI2?
Workload testing as part of Anuket Assured
Collaboration with other LFN projects
Collaboration with other projects outside of LFN
Where do we go on from here, i.e. what are the expectations?
How to fill the gaps between RA2 and RI2?
How to achieve full RC2 compliance in CI?
What are the challenges?
Onboarding of a workload in Anuket
Requirements for CNFs
Page:
2022-01-DD - Anuket: Thoth Shared Data Model for Intelligent Networking — Beth Cohen Sridhar Rao60m
Discussion of how to create a common data model to support AI/ML for Intelligent Networking
Page:
2022-01-DD - Anuket: Traffic & Load Generators as Pods - Opportunities and Challenges — For Inter-pod dataplane performance analysis, it becomes mandatory to run Traffic-generators as Pods. In this talk we will present the opportunities and challenges considering these scenarios and opensource tools.
GSMA OITF meeting on December 6th:
Status of PRD NG 133 – has been distributed for ISAG review on November 30, 2021 (review ends December 14, 2021). After that, it goes for publishing.
What would be in the next version and when? NG 133 v2 based on Wallaby OpenStack release
Lakelse is not enough for another version; maybe Moselle
Add the conformance sections – may require RC1 cleanup | Moselle
What else for OITF?
RA2?
cooperation with other groups within GSMA
Ideas:
LCM or LMA
Automation
AOB
rst conversion:
@Karine Sevillahas made substantive progress
Once rst file loaded in Gitxxx then rst becomes the Master; md file is obsolete
No Meetings: Dec. 20, Dec. 27, January 10
Vacation Plans:
Pankaj: December 20 - 23
Ildiko:
Karine: on vacation December 22 - January 2
Backlog Issues
Issue # | Deliverable | PR # | Status | Action Items | Comments |
|---|---|---|---|---|---|
Storage Content Improvements | Improve content and align with new RM content Priority: Include in release | ||||
Align with RM Automation Ch09 - RM Issue #2087 | Work with RM and then include in RA1 | Priority: Nice to have | |||
RM Hardware Acceleration | Add real deployment scenarios | Priority: Include in release | |||
Add requirements around the use of OpenStack APIs for Edge, Hybrid, and Multi-clouds | review GSMA OPAG work | Priority: Nice to have | |||
Update Requirements and Content for Edge | Control in RM @Ildiko DNS in RM @Ildiko IPv6 in RM @Ildiko | Priority: Include in release | |||
Leverage pandoc's yaml metadata_block | @Cédric Ollivierto give an example | Priority: Include in release | |||
Add specifications reference matching requirements | Priority: Include in release | ||||
TBD | Update Requirements and Content for Hybrid Multi-cloud: OpenStack Omni | Issue still to be created | Priority: Nice to have | ||
Automated process to produce GSMA documentation from Anuket Gitxxx | (not content) | ||||
O-RAN use case align with WG 6.2 | O2 interface into the O-Cloud (NFVi) vRU, RIC, vDU and vCU – specs | Priority: Nice to have |
rst conversion steps
rst references see "The reStructuredText Cheat Sheet: Syntax"
and "Quick reStructuredText"First step:
trim lines to 80 characters (for continuous lines (in commands) use "\");
standardise list character to "*";
remove html wherever possible (e.g., <p>; inclusion of figures; not tables);
introduce blank line before and after titles, and first-level list;
inclusion of figures " <!-- width="50%" -->";
Second step convert to rst: "pandoc -f markdown source.md -o target.rst" (for multiple files use "for i in $(seq n); do pandoc chapter0$1.md -o chapter0$1.rst" where n is between 0 and 9)
Second step: manual correction of all references; change html; use "Atom target.rst"