Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

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

...

Issue #

Deliverable

Comments

2787Storage
  • Chapter 3 (issue#2860issue #2860)

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

2- 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#2861issue #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)

...

The changes for daylight saving is are scheduled at different date 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:

  • 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-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