Newly-formed Interim TSC needs to meet quickly to decide procedures for election of TWO Co-Chairs
(a proposal exists to categorize the affiliation of each co-chair, which is non-meritocratic; chairs must be objective facilitators of meetings and decisions, and not operate otherwise)
This has not been discussed at a meeting of the Interim TSC!
AIRSHIP - passes Functest health check tests, Upstream dependencies, no on RBAC and floating IP, Telemetry requirements study partially completed pushed to next release (collectd and others). Testing by Functest (RC-1) still has a long way to go (tempest, others), conformance testing configuration needs to be worked (integration).
CIRV - RELREQ 5 - Done
VSPERF - RELREQ 6 and 9 -Done
SampleVNF - Documentation - also needs help on Stable branch creation
List of the Individual Projects Releasing with OPNFV-JERMA and Status
AIRSHIP (only open ticket is 87 - resolve remaining issues
CIRV
Doctor
Barometer - issues are closed
kuberef -
Dovetail
FDS - withraw, upstream component not available
VSPERF
SampleVNF - 167 unclear, all project specific issues are closed.
Agree on RC1, remaining milestones and dates ?
RC1: Today (#agree that RC1 is met?)
Technical Release: December 3
Marketing Release: December 15
Monday Tech Discuss on Future Release management & automation
How do we characterize the JERMA Release Test Suite?
OPNFV provides the building-blocks (tests) for CNTT's RC.
Repeatable, consumable, stable.
Hand-off OPNFV-JERMA to RC activities and OVP badging (not the same)
Main goal OPNFV-JERMA is to check if the test case integration/automation and requirement coverage.
More specifically, is JERMA an RC Tech Preview? Prototype? Beta? Experimental?
JERMA is the most comprehensive set of tests aligned to the CNTT RA-1 and RC-1.
CNTT determines the definition of Compliance (test cases in RC).