Anuket Project

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
Cedric Ollivier (Orange)


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

Antitrust Policy

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

Agenda and Minutes

  1. Agenda Bashing
  2. Release information
  3. rst conversion status
  4. Review of PRs in progress
  5. Creation of detailed issues for Moselle
  6. Next Meetings, vacation plans, daylight saving time changes
  7.  AOB

Release information


MilestoneDateNotes
M1 2022-02-01Release definition
M22022-03-22Scope freeze
M32022-04-19Content freeze
M42022-05-17Proofreading
M52022-06-07Release readiness
M62022-06-14Sign off


Moselle Specification Planning Dashboard - RA1

We are now working to reach M2 milestone(scope freeze). We can start the creation of detailed issues for Moselle.

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

RST preview

Atom includes a simple RST viewer which is very simple to install/use but doesn't interpret sphinx :ref: or :doc:.

For its part, VSCode offers an RST viewer wich may interpret Sphinx attributes but it's very hard to setup all extensions and to solve the conflicts - for a very small benefit at the end

In case of VSCode Cedric Ollivier recommends the docutils rendering at the time of writting.

Also being discussed with ONAP, see ONAP guide: Setup of a Documentation Development System — onap master documentation

PRs review

A snapshot of https://github.com/cntt-n/CNTT/pull/2856/ was published for review.

All remaining links would be added in other commits.

Issues review

Content can be added right now ( it won't be a big deal to solve any small conflits with ongoing RST conversion).


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.

2732Specification references updates 
  • Chapter 2: add specification content references into requirements' tables (issue #2732)
  • Other chapters: add requirements matching content 
2500Edge
  • Collect requirements and characteristics from existing production deployments ( Chapters 2 & 4) (issue #2500)
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)
2776Automation 
  • Lifecycle Automation: align with RM development on automation (issue #2238)
  • Deployment automation: give more guidance (issue #2776)


Next meetings

The changes for daylight saving are scheduled at different dates per country, it will change the meeting time.

What is more convenient for people attending this meeting?

2 Proposals for the meetings starting in April from March 28:

  • 14:30 UTC: 08:30 Denver, 07:30 Seattle, 16:30 Paris
  • 15:00 UTC: 09:00 Denver, 08:00 Seattle, 17:00 Paris

Karine Sevillawill send an email to check with Pankaj Goyaland Ildiko Vancsatheir preferences.

2022-03-21: meeting canceled, Karine will be on holidays  March 21-25.

2022-03-28 2022-04-04: next meeting

Actions

NameAction
AllReview PR:  https://github.com/cntt-n/CNTT/pull/2856/
Cédric Check Pankaj proposal of reference creation for links used repeatedly
CédricStart modifications of internal links into RST files
Cédric/KarineCheck the use of VScode and tox locally with windows
Cédric/KarineRST conversion last step: link to RTD for references (internal and external) in a temporary step and then Sphinx when RM is done
AllStart providing new content for Moselle
Karine Send an email to move the meeting time

Meeting Recording: none


  • No labels