Anuket Project

Meetings Every Monday at 14:30 UTC

Zoom Meeting link: https://zoom.us/j/99279174971?pwd=eWozNENnYkpLSXdRSzZvblNKVU1wdz09

Attendees:

  • Name (Organisation) |  will incorporate Participant report from Zoom.

Name

Ildiko Vancsa (Open Infra)

Karine Sevilla(Orange)

Pankaj Goyal(Microsoft)

Cedric Ollivier(Orange)


As a courtesy to your colleagues please mute yourself when in listen mode. Thanks

Antitrust Policy

This meeting is held in accordance with the LFN and GSMA anti-trust policies.

https://r.lfnetworking.org/Antitrust%20Slide.pdf and GSMA Anti-Trust Policy Notice

Agenda and Minutes

  1. Agenda Bashing
  2. Release information
  3. OITF#11 meeting 
  4. GSMA document structure
  5. rst conversion status
  6. Review of PRs in progress
  7. Review of detailed issues for Moselle
  8. Next Meetings
  9.  AOB

Release information

  • New Moselle Release milestones approved by the TSC on 19th of April


Milestone(Official)GitHubDateNotes
M1 
2022-02-01Release definition
M2
2022-03-22Scope freeze
M3 (Software project only, not for specs)
2022-05-03RC valid. testing
M4M32022-05-24Content freeze
M4-sM42022-06-07Proofreading
M5
2022-06-07Release readiness
M6
2022-06-14Sign off


Moselle Specification Planning Dashboard - RA1

GSMA OITF#11 meeting

NG.133 v2.0 content presented. It will based on RA1 and RC1 Anuket Moselle release.

The 9th of September is the milestone approved during the meeting to enter into the GSMA process for NG.133 v2.0 publication.

The new Anuket creation of documents was presented and questions to GSMA on the production of the GSMA pdf document.

2 action points are identified on GSMA side (Javier Sendin):

  • Can PDF documents be used during the GSMA Review process?
  • Get the GSMA PRD Word Template styles corrected (e.g., Normal style)

Next meeting OITF in London 20-23 June: Pankaj will not go, Karine not sure to go, it can be only on Thursday, if any interest.

The meeting will be held in hybrid mode.

GSMA document structure

Issues to generate the following tables:

  • Terminology: switch from "ref" to "include" on RST 
  • Abbreviation/Acronym: A new table must be created in RST and manually edited, with "include" instruction 
  • References and bibliography: 2 tables to be created, add the references inside the text manually. Proposal from Pankaj to create 1 RST file with 2 tables(References, Bibliography) with references and numbering in sequence (no redundant number), example here. Start ASPA and finalise during proofreading period.
  • Tables of requirements: on traceability column, 3 options : keep only name title on RST,  Keep name and links for RST and GSMA, post process to remove links on GSMA

RST conversion

First step: md files cleaning is done, PR #2766 merged

RST files are generated and uploaded, PR #2799, merged, 

RST cleaning following rst conversion:

  • Ch01 and Ch02, PR#2811: reference links fixed → merged
  • Ch03, Ch04, PR#2815: reference links fixed , Figures captions, Lines breaks →merged
  • Ch05, PR#2817: Addition of backslashes to fix cut words → merged
  • Ch02 , PR#2821: Addition of backslashes to fix cut words → merged
  • Ch07, PR#2819: duplicated title removed → merged
  • Ch08, PR#2820: numbering removed for internal link→ merged
  • Ch06, PR#2818: reference links fixed, tables fixed → merged

Tox issues on RST files: PR#2830 -> merged

First start page for all Anuket specs, PR#2845 → merged

Tox added, links modified, tables format modified, PR#2856 → merged

 Configuration of figures numbering format, PR#2893 → merged

Ongoing RST : Figures caption and references to figures number, for all chapters

Tables Chapter 2: PR#2911 merged


All: help needed to format tables

PRs review

PR #2926: wrap chap2 tables (continued)

Issues review


Issue #

Deliverable

Comments

2787Storage
  • Chapter 3 (issue #2860)

 Expand the section "Virtual storage" highlighting the storage requirements for workloads and for the infrastructure components. Refer to RM chapter 3.

On the "Cloud Topology" section, describe the differences per hosting environments: large DC to edge infrastructures, in conjunction with RM Chapter 3, 3.6.4. Storage scenarios and architecture fit.

  • Chapter 4 (issue #2861)

Develop on interactions between OpenStack Cinder/Swift and storage backends.

Add examples of backend solutions.

  • Hyperconverged storage for Edge (ssue #2874)
2732Specification references updates 
  • Chapter 2: add specification content references into requirements' tables (issue #2877)
  • By chapters: add requirements references matching content 
2500Edge
  • Collect requirements and characteristics from existing production deployments ( Chapters 2 & 4) (issue #2500). It is linked with RM content for chapter "API"
2775Cloud Topology

Content improvement (issue #2775):

  • Chapter 03: Topology overview, make clearer the redundancy models, eventually with high level diagrams
  • Chapter 04: Cloud Topology and Control plane scenarios, in table 4-5,  "*" and "**" need to be defined
2786Acceleration
  • Development on acceleration focusing on use cases. Identify the acceleration needs and technologies for workloads hosted in Data Centre and for workloads deployed at the edge (#2786)
2784Hybrid and multi cloud
  • Hybrid multi-cloud orchestration (#2784)
  • Evaluate other communities: ONAP, GSMA OPG, ...  (#2784) (New CAMARA LF project)
2776Automation 
  • Lifecycle Automation: align with RM development on automation (issue #2238)
  • Deployment automation: give more guidance (issue #2776)

RST conversion
  • Creation of rst files and removal of md files (issue #2796) closed
  • Add name to all figures reused by the other streams(issue#2872)

GSMA doc
  • Add metadata to automate GSMA doc creation (issue#2609)


Next meetings

2022-05-09:  next meeting

Actions

NameAction
AllReview PRs
AllStart providing new content for Moselle
Joël To have a look on Storage
KarineWrite PR to update section on installers and automation
Pankaj Write content on edge following RM work
All Need to find more contributror on acceleration


Meeting Recording: none


  • No labels