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) |
Karine Sevilla(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
- Agenda Bashing
- Release information
- rst conversion status
- Review of PRs in progress
- Creation of detailed issues for Moselle
- Next Meetings, vacation plans, daylight saving time changes
- AOB
Release information
Moselle Release milestones
Milestone | Date | Notes |
---|---|---|
M1 | 2022-02-01 | Release definition |
M2 | 2022-03-22 | Scope freeze |
M3 | 2022-04-19 | Content freeze |
M4 | 2022-05-17 | Proofreading |
M5 | 2022-06-07 | Release readiness |
M6 | 2022-06-14 | Sign 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
PRs review
Issues review
Content can be added right now ( it won't be a big deal to solve any small conflit with ongoing RST conversion).
Issue # | Deliverable | Comments |
---|---|---|
2787 | Storage |
1- 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.
Develop on interactions between OpenStack Cinder/Swift and storage backends Add examples of backend solutions |
2732 | Specification references updates |
|
2500 | Edge |
|
2775 | Cloud Topology | Content improvement (issue #2775):
|
2786 | Acceleration |
|
2784 | Hybrid and multi cloud |
|
2776 | Automation |
|
Next meetings
The changes for daylight saving is scheduled at different date per country, it will change the meeting time.
What is more convenient for people attending this meeting?
2 Proposals for 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
2022-03-21: meeting canceled
2022-04-04: next meeting
Actions
Name | Action |
---|---|
Cédric | Check Pankaj proposal of reference creation for links used repeatedly |
Cédric | Start modifications of internal links into RST files |
Cédric/Karine | Check the use of VScode and tox locally with windows |
Cédric/Karine | RST conversion last step: link to RTD for references (internal and external) in a temporary step and then Sphinx when RM is done |
All | Start providing new content for Moselle |