Attendees:
No need to add, this will be done after the meeting.
Agenda and Minutes:
- Antitrust notices
- Walk-in items
- PR1872 / PR1912: need to reach consensus, suggest we use the CNTT process: https://github.com/cntt-n/CNTT/blob/master/doc/gov/chapters/chapter05.md
- Discuss when more members are present or even have a special meeting for the same
- Project review
- https://github.com/cntt-n/CNTT/projects/10
- Please take the issue without assignee and self assign them
- https://github.com/cntt-n/CNTT/projects/10
- AOB
- Permanent FYI
- Please review Meld Zone for info about CNTT/OPNFV merger: Meld Zone
- Please vote on the name of teh new organisation
- Regular meeting looking to collate CNF requirements from multiple sources - please feel free to join and contribute:
- Meeting notes https://docs.google.com/document/d/1eStYtBIoAvz8kh8k2NtvTnjfKZ_6km9HVzCEBt4s0tY/edit#
- Working spreadsheet https://docs.google.com/spreadsheets/d/1TxrrCDKQEzca_snuIXMAcz4GCHj9b99-Obnhs20rCB0
- Approach:
- Determine business requirements - including non-functional
- Determine functional technical requirements
- Determine K8s / cloud native implementation options and best practices
- Highlight tradeoffs, conflicts, gaps
- Examine applications or write new PoC (eg. existing NFs and their components)
- Create or find tests that check applications against the requirements
- Please review Meld Zone for info about CNTT/OPNFV merger: Meld Zone
- Actions/Next steps
- Frederick to present a quick NSM intro in one of the future meetings
- 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
