Page tree
Skip to end of metadata
Go to start of metadata

Overview

The CNTT (Common NFVI Telecom Taskforce) launched officially in June.  Its mission is to define a common NFV Infrastructure to simplify the development and deployment of virtualized networking application for the telecom industry.  The group held its first community wide F2F meeting with around 80 vendor and operator attendees, with the objective of gathering requirements for the contents of the Release 2 document. CNTT develops Reference Models and Reference Architectures.  This is a wiki space for using those outputs to create Reference Implementations and Reference Certifications.

Project description:

CNTT is currently working on the common NFVi reference model and reference architecture. The goals of CNTT can only be achieved if the model and architecture specifications end up being implemented as a reference for vendors to compare their commercial products against.  Therefore, it is this project’s goal to work with upstream communities and other related projects in OPNFV to create reference implementations as one or several scenarios of OPNFV, along with required test cases and test frameworks.

Detailed mission for this project includes:

  • This project will act a feature project which is responsible for defining RI scenarios that comply with the CNTT reference model and reference architectures.
  • Work with upstream projects to defined RI details including detailed scenario descriptions and integration strategies.
  • Work with relevant projects in OPNFV, including installer projects, testing projects, infrastructure projects, to integrate, deploy and test RIs as part of OPNFV release life-cycle.
  • Implement a limited number of RIs that address CNTT reference architectures to meet operators’ requirements. Limit the number of RI to ensure limiting the VNF verification effort
  • Develop test-cases for testing RI.  These test cases could be used by the compliance program for verification and compliance.
  • Work with LF Compliance and Verification Committee (CVC) to integrate RI, test cases and test frameworks within OVP compliance Framework.

As the Common NFVI initiative matures, project scope is expected to grow significantly. This project will periodically review scope and make recommendations to the TSC as to whether it should be split into multiple projects focusing on different areas, or whether it should remain a single project of OPNFV.

Scope:

The project will act as the landing space for CNTT RA within OPNFV, and will be a starting point for creating RIs. The scope of this project includes:

  • Work with communities of upsteam ingredients and with CNTT, to adopt Reference Architectures defined in CNTT
  • Translate RAs into deployable scenario descriptions, which can be considered as Reference Implementations for CNTT
  • Figuring out gaps for current components of RA, and work with upsteams or related projects in OPNFV to close the gap.
  • Work with installer projects, to generate scenarios and deployable code packets for specific installers
  • Work with testing projects, provide test requirements and test cases for RI testing, including the identification, and documentation of needed test cases.
  • Work with LFN Compliance and Verification Committee (CVC) to integrate RI, test cases/frameworks with OVP Framework.

OPNFV Testing Projects that are already looking to meet CNTT requirements with new features should continue to do so.

Testability:

  • This project intends to follow and adhere to the gates and quality criteria used by OPNFV.

Documentation:

Documentation will be available on official OPNFV Documentation portal and will include:

  • Pointers to CNTT Reference Architectures for Common NFVI with related information on ingredients and configurations
  • Gaps discovered from experience with integrating, deploying and testing RIs
  • Reference implementation description for Common NFVI
  • Test requirements for Common NFVI
  • All documentation generated by CNTT-RI project will reside in CNTT main repository (migrate to OPNFV CNTT-RI repo in future).

Dependencies:

  • This project depends closely on the progress of CNTT.
  • Much work can be done while the CNTT finishes its first RA

Meeting Logistic:

CIRV project and CNTT RI WS will use a combined call. 

Every Wed. at UTC 1300-1400

 https://zoom.us/j/694881078


Meeting Minutes:

Minutes can be found in LFN wiki

https://wiki.lfnetworking.org/pages/viewpage.action?pageId=25364128


CNTT RI Doc:

https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl

CNTT RI installer description file


Committers and Contributors:

Committers

Contributors

Leads and contributors for CNTT RI WS

https://wiki.lfnetworking.org/display/LN/CNTT+Workstream+Signup


Planned deliverables:

  • Reference implementation for Common NFVI
  • Test Requirements for Common NFVI

Proposed Meeting Frequency:

  • This project will meet on a weekly basis.

Proposed Release Schedule:

  • This project is planned for the first release in 2020 Q1.

Key Project Facts

Project Name: Common Infrastructure Realization & Validation (CIRV)
Repo name: 

  1. CIRV https://gerrit.opnfv.org/gerrit/admin/repos/cirv - main(primary) repo
  2. CIRV_Spirenthttps://gerrit.opnfv.org/gerrit/admin/repos/cirv-spirent - adjunct repo, dedicated to Spirent, used for uploading/managing code contributions for RI/RC validations in direct support of CNTT 

Lifecycle State: Approved
Primary Contact: Mike Fix (AT&T) <michael.fix@att.com>

Project Lead: Mike Fix (AT&T) <michael.fix@att.com>

Jira Project Name: CIRV
Jira Project Prefix: CIRV
Mailing list tag: cntt-ref-imp@lists.opnfv.org

  • No labels