Attendees:
Zoom link: https://zoom.us/j/92317903558
Please add your name in here:
- bill.mulligan (Kubermatic)
- Pankaj.Goyal (AT&T)
- Trevor Cooper (Intel)
- Cédric Ollivier (Orange)
- Georg Kunz (Ericsson Software Technologies)
- Al Morton (AT&T)
- jganbar (Deactivated) (VMware)
- Taylor Carpenter (Vulk Coop)
- Satish Verma (Spirent)
Agenda and Minutes
- Kubernetes Usage in Telecommunications Survey https://forms.gle/wwyyam8aPGNYRTv79
- Issue Review: https://github.com/cntt-n/CNTT/projects/32#card-36881576
- Chapter 1 Introduction https://github.com/cntt-n/CNTT/pull/1624
- Thanks for the help. It has been merged.
- Terminology definition for testing per issue https://github.com/cntt-n/CNTT/pull/1649
- Add reviews to update the glossary
- Requirements and Testing Principles PR https://github.com/cntt-n/CNTT/pull/1738
- Waiting for Cedric to come back from vacation
- Fix Test Integration Introduction https://github.com/cntt-n/CNTT/issues/1863
- Who else can help review?
- Define terminology and scope of RC2 (Functional vs. Performance) https://github.com/cntt-n/CNTT/issues/1495
- Can we close for now?
- Chapter 3 Introduction https://github.com/cntt-n/CNTT/pull/1832
- Thanks for the review, waiting for Scott to merge
- The initial content of Kubernetes Traceability Matrix
- https://github.com/cntt-n/CNTT/pull/1868/
- what items are relevant and how should we structure the table of contents to cover the requirements?
- might be useful start with talking about Kubernetes conformance and how it meets requirements before test case mapping
- CNTT RA-2 requirements (snapshot) and relationship to testing in different initiatives https://docs.google.com/spreadsheets/d/12EWZVvlumktXoywvmlYPR_DrU34e7Gk_rSED3VyCG4o/edit
- Chapter 1 Introduction https://github.com/cntt-n/CNTT/pull/1624
- AOB
- Workload + CNF shared requirements that can be used by different efforts (eg. OVP2 + CNTT and CNCF)
- https://docs.google.com/spreadsheets/d/1TxrrCDKQEzca_snuIXMAcz4GCHj9b99-Obnhs20rCB0/edit#gid=2002882762
- Collaborative effort. Identify the type of requirement. Potential testing source. Where the requirement comes from