...

• Antitrust notices
  • Linux Foundation Anti-Trust Policy Notice
  • GSMA Anti-Trust Policy Notice
• Walk-in items
  • Review current status versus Baraque plan (change freeze starts 14th September):
    • Chapter02 - CNF requirements missing (Olivier Smithto check offline)
    • Chapter03 - some sections still missing content (issues have been created to deal with these)
    • Chapter04 - relying on below PRs being completed
    • Chapter05 - relying on issues/1581 being assigned and a PR being created/merged
    • Chapter06 - OK
• Project review
  • Chapter 4 restructuring
    • https://github.com/cntt-n/CNTT/blob/master/doc/ref_arch/kubernetes/chapters/chapter04.md

    • 4.4 Container runtimes - issues/1636 - Satish Verma

      • Presented a slide about the plan
      • The contribution will contain a set of runtimes and their parameters

    • 4.9 Kubernetes workloads - issues/1853 - Gergely Csatari , Taylor Carpenter , Riccardo Gasparetto Stori , Olivier Smith

      • The chapter was originally empty
      • Ch2 level is handled in issues/1496
      • Do we need to move to backlog, or can someone create some content to review in time for 14th September PR merge deadline?
  • https://github.com/cntt-n/CNTT/projects/10
    • Please take the issue without assignee and self assign them
• AOB
  • CNF requirements activity has been running, looking at collating requirements from multiple sources: https://docs.google.com/spreadsheets/d/1TxrrCDKQEzca_snuIXMAcz4GCHj9b99-Obnhs20rCB0/edit#gid=39883758
    • Meeting minutes (meetings are each Tuesday at 9am PT): https://docs.google.com/document/d/1eStYtBIoAvz8kh8k2NtvTnjfKZ_6km9HVzCEBt4s0tY/edit#heading=h.tqki8edcltqu
      • Please join and contribute!

    • Approach for first iteration of requirements targeting CNTT RA-2

      1. Pick example workload(s) and application(s) for context (as needed)

         • Note: Applications (telecom or otherwise) are used for context when discussing the K8s native and underlying end-user requirements. Specific workloads and applications may have implementation requirements which are not included

      2. Gather requirements

         • Cloud native fundamentals

         • K8s native

         • Determine underlying end-user requirements (eg. network segmentation for XYZ)

      3. Determine which are a good start for CNTT RA-2

      4. Create PR to RA2 (eg. against #1496)

      5. Review with community

• Actions/Next steps
  • Frederick to present a quick NSM intro in one of the future meetings
  • Stale issues - propose we close if in To-do and no PR created after ?? days/weeks/months
    • No objections - Tom Kivlinto create proposal
  • Network specification - Tom Kivlinproposal to replace table 4-5 with a diagram that shows the architecture, with an associated table showing which part of the architecture deals with each requirement.  e.g. I don't think it's relevant that the multiplexer has to provide Network Policies as existing CNI plugins that the multiplexer calls can (and perhaps should) deal with that.   (Do we need a "Unix" principle - "do one thing, well"?)
  • Tom Kivlin to create an issue on the backlog

Meeting Recording

Topic: CNTT RA2 Kubernetes Weekly Meeting
Start Time : Sep 3, 2020 07:58

Meeting Recording:
https://zoom.us/rec/share/tn3ny0nzu_y37Qoxa9eVZUOmy8Il-40nz5orBAiGi2FMLRC-_VFWSZrokWGBJzdZ._OFUIHdngvzkaa5U