...
- Full Merger of equal communities: a "Re-imagining" that produces a project where both communities are needed for success.
- Merger Outcome: a single organization where telcos work together with vendors and other interested organizations and individuals to define, implement and test the cloud architectures that fulfill the common requirements of telecom applications
- OPNFV+CNTT=NewName (Community and Marketing determine NewName, if communities want it).
- Community and Board Decision is needed about the name of the organization
- Create a new name for the merged organization, or
- Find a way to keep existing organization names
- Create a new name for the merged organization, or
- OPNFV Release process already allows for frequent project self-releases, so any CNTT release schedule can be accommodated.
- Ensure all leadership needs and project activities are covered in the organizational structure
- New TSC Elections and Officers (when organizations combine,
- see timeline below).
- New Structures can be accommodated by mutual agreement
(points below are mostly structural recommendations with a lot of flexibility! Probably do not appear on the Description slide)
- CNTT Work Streams become individual Projects, with PTLs, Committers, Contributors, and Project descriptions.
- This can be a structure where the existing workstreams have 1:1 mapping to new formal projects, or some restructuring is possible/optional.
- This can be a structure where the existing workstreams have 1:1 mapping to new formal projects, or some restructuring is possible/optional.
- Build new WGs according to CNTT’s need for tiered structure (if any WG are needed).
- Existing OPNFV projects could choose to continue to be independent projects or choose to combine with new projects being formed
- Commitment from all OPNFV+CNTT members to supply a fixed amount of resources to both requirements and code development.
- New project to Integrate all relevant project outputs into a cohesive deliverable for automated Conformance testing.
- Reduce overall governance structure of OPNFV+CNTT, where possible. Reduce the overall number of meetings related to former CNTT activities.
...
Development Project Release Artifacts (assuming recommended development
- Stable Project Repos
- Project Documentation
- For projects integrating with an Automated Conformance Test Suite, Integration test results
- Development
- Maintenance and lifecycle for all projects, including OVP
Requirement/Documentation Projects
- Stable Project Repos
- Reference Model Documentation Jointly approved by GSMA (or moves to GSMA, similar question for Reference Architecture)
- GSMA members are encouraged to participate
Interfaces and Dependencies
Upstream projects and communities: OpenStack, CNCF, LFN,
Continue "Working Upstream": Open Stack, CNCF, other LFN projects (FDIO, ODL, ONAP, ...),ETSI NFV, IETF, others (Continue "Working Upstream")
- The merger option simplifies the relationship with GSMA.
Approximate Timeline
Factors:
- Governing Board Decision in October 2020?2020 on Fully-fleshed-out plan (Ideally, an announcement at ONS = late Sept 2020)
- OPNFV JERMA meta-Release Calendar: December 2020 Release date
- CNTT Baraque Release in September 2020 (insert additional releases planned...)
- Current CNTT officer term ends in December 2020
- Intermediate tasks to flesh-out, post GB decision, such as the structure of the new organization
- Nomination periods and Elections take about 6 weeks - propose to start the Election Calendar in November 2020 (half of December is unavailable).
- NewName selection: Community and Marketing
...
Dependencies and Relationships
- Upstream projects and communities: OpenStack, CNCF, LFN, ETSI NFV, IETF, others
- The merger option simplifies the relationship[ with GSMA.
Approximate Timeline
Factors
...