Versions Compared

Old Version 8

changes.mady.by.user Walter Kozlowski

Saved on

compared with

New Version Current

changes.mady.by.user Per Andersson

Saved on

Key

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

...


  • Agenda:
    • Linux Foundation Anti-Trust Policy No, 
    • Recording Policies:
    • Agenda Bashing
      •  Cleanup of work space (RM wiki)
    • Announcements 
    • LFN DTF Workshop 14 - 15 March
    • Migration of RM to rst - outstanding issues, actions and automation (let's do what we preach ...) - Gergely and Cedric (TBC)
      • Readthedocs: https://cntt.readthedocs.io/en/latest/
      • Section numbers will not be visible in GitHub, will be generated automatically in readtehdocs
      • Section titles should be unique in the same chapter (PR#2836)

      • Some wrong links in PR#2837 (https://github.com/cntt-n/CNTT/issues/2837)

      • Figure number - the same, Table numbers - Cedric will check
      • Cedric is preparing a guide to rst transition
      • Internal links need fixing: PR#2832: ALL - review, and then merge (https://github.com/cntt-n/CNTT/pull/2832/) Karine will focus on Chapter 7, John - Chapter 8, Walter - rest, other people encouraged to assist
        • Karine reviewed Chapter 7 links
        • ALL (Pankaj, Walter, John) - review changes and internal links
    • Pankaj Goyal: "bug" issues: #2716 - 2720
    • Discussion on proposed new time for RM meetings 
      • Current time on Wednesday soon move, for most participants:
        • Australia (Melbourne, Sydney): From 7:00 on Thursday to 6:00 on Thursday (change from AEDT to AEST on 3rd April)
        • Europe (e.g. France/Sweden/Belgium): From 21:00 on Wednesday to 22:00 on Wednesday (change from CET to  CEST on 27th March)
        • US (Central Time): Stays at 13:00 on Wednesday  (change from CT to CDT on 13th March)
        Possible time (after 3rd of April
      • CHOSEN, next week change(Walter to change calendar and resend invites)
        • Australia (ASDT) 23:00 on Wednesdays
        • Europe (CEST) 15:00 on Wednesdays
        • US  (MDT)(Denver)  7:00 on Wednesdays
        • US (EDT) (East Coast) 9:00 on Wednesdays
        Alternative (or alternate) times (after 3rd of April)
        • Australia (ASDT) 7:00 on ThursdaysEurope (CEST) 23:00 on Wednesdays
        • US  (MDT)(Denver)  15:00 on Wednesdays
        • US (EDT) (East Coast) 17:00 on Wednesdays
        Next RM meeting as per the current time, and we will decide on time and on the switch date
    • Next release (Moselle) planning - Issue and PR review
      • Next Milestone: M2 - Scope Freeze, 22 Mar 2022
      • Moselle Issues review and updates

...

Issue #

Deliverable

Comments

2794Hybrid Multi-Cloud

Updates to:

  • multi-cloud summary table and examples (PR#2676) wiki  , PR#2824
  • storage for multi-cloud (Issue#2578), storage sections are under review by John Hartley - contents both in Storage and Multi Cloud sections, will be cross-referenced

  • hybrid / multi-cloud security and regulatory (Issue #2804), address the gaps in Sec 8.2.8 (Aspects of Multi-Cloud Security), and update Requirements in Sec 7, (references in RAs are from Chapter 7).  Plan proposed:

  • Create general section in Chapter 7 (Security) on overall regulatory high level directions (Issue#2839)
  • In Sec 8.2.8 (Aspects of Multi-Cloud Security) refer to relevant portions of this general section on regulatory matters (plus any needed extensions)
    • Update Requirements in Sec 7 appropriately (Issue#2841)

  • APIs (Issue#2812), to be done in Chapter 6 - alignment will be necessary, reference in RAs are from Chapter 6
  • single pane requirements (a minimum set) (Issue #2797), Chapter 8 in the new Requirements section 
  • multi cloud use cases (as examples to drive requirements), needs a discussion at RM meeting
    • specialised specialized clouds (e.g. game clouds) Walter to create an Issue
2793Security 

Developments on:

  • SBOM, alignment with LFN security forum (Issue#2810) in Chapter 7; will need to be understood in the context of overall Software Supply Chain and considered from both open source and vendor software (Issue#2839Issue#2838)
  • Security for hybrid and multi-cloud, Issue #2804 (to be removed?), Issue#2840,) Issue#2840
  • Regulatory directives for cybersecurity, issue#2839

  • Add reference to FS.40 v2 which is now a non binding PRD and must be added, issue#2828

  • Restructure and update section about common security standards, issue #2841

  • Both "Monitoring for security" and "Security of monitoring" aspects are included in Table 7-7 which needs review by the team, and updates 
2795Storage

Updates to storage:  storage sections are under review by John Hartley

  • Storage principles (Issue#2666) - propose placement of contents wStorage for multi-cloud (Issue#2578) - contents in Multicloud section
Storage
  •  Storage for multi-cloud (Issue#2578) -
propose placement of contents
  • contents both in Storage and Multi Cloud sections, will be cross-referenced
  • Storage scenarios (Issue#2747) - propose placement of contents, currently focused
2087Infrastructure LCM Automation (revised title)

Walter Kozlowskito start PRs for the Issues:

  • Infrastructure LCM Automation Introduction (Issue#2816) - state goal/ambition of Anuket work, PR#2851
  • Infrastructure LCM Automation Framework (Issue#2848) - Create a high level framework identifying different layers and different actors in the Infrastructure LCM Automation
  • Infrastructure LCM Automation Principles (Issue#2849) - Create principles for Infrastructure LCM Automation to govern best practices. Need to be on high level because of different specificity of operations in different telecoms.
  • Infrastructure LCM Automation Best Practice (Issue#2850) - Develop high level best practice guidance for Infrastructure LCM Automation
PR#2826: Remove the following sections (blank) - under review
  • 9.5.1.1. Hardware Configuration CI/CD
    • 9.5.1.2. Networking
    • Automation
    9.5.1.3. Software Development CI/CD1.
    2785General PaaS Services

    Section 5.1.5 lists a set of General PaaS Services. We need to specify requirements for each of these services -- an issue will be opened for each service. - Pankaj Goyalto start work on contents in wiki page (RM Work Spaces) and PRs (collaborate with Per Andersson)

    ...