2020-06-011 - [CNTT - RC2] - Meeting Agenda and Minutes
Attendees:
Zoom link: https://zoom.us/j/92317903558
Please add your name in here:
@bill.mulligan (Loodse)
@Rabi Abdel (Vodafone)
@Taylor Carpenter (Vulk Coop)
@Luc Provoost (Intel)
@David Spence (Deactivated) (Red Hat)
@Michael Pedersen (Intel, Tieto, CNF Testbed)
@Pankaj.Goyal (AT&T)
@jganbar (Deactivated) (VMware)
Agenda and Minutes:
Issue Review: https://github.com/cntt-n/CNTT/projects/32#card-36881576
Introduction Draft - any more comments before the merge
Chapter Structure
Any volunteers for seeding initial content?
Performance will be discussed at the June meeting
RC1/RC2
Should we copy or should there be a common infrastructure?
There will be a meeting about this, let me know if you want to attend
Review of https://github.com/cntt-n/CNTT/pull/1624 [RC2 Ch01] Intial Content for Introduction
#1624https://github.com/cntt-n/CNTT/pull/1624#pullrequestreview-428905052
Clarification requested on:
The goal for the RC2 conformance is verifying the actual behaviour and capabilities of a running platform.
Versions are an indication that a behaviour or capability may be there, but it needs to be actually tested.
Suggestion for word change. Split sentence.
Testing to confirm specific versions of APIs is out of scope
Testing specific software components is out of scope.
Alternative:
**Not in Scope**
Functional testing / validation of the application provided by the CNF is outside the scope of this work.
Testing to confirm specific versions of APIs
Testing specific software components
What does term Traceability mean within CNTT?
AOB
Beta testers wanted for CNF Conformance
Action Items:
Ask to change naming from 1 and 2 to OpenStack and K8s - @bill.mulligan
Define what traceability means - @Rabi Abdel