`<< Back <../>`__ .. _1-overview: 1. Overview =========== .. raw:: html
Table of Contents ----------------- - `1.1 Introduction. <#1.1>`__ - `1.1.1 About Reference Implementation. <#1.1.1>`__ - `1.1.2 Terminology. <#1.1.2>`__ - `1.2 Scope. <#1.2>`__ - `1.3 Relationship to other communities. <#1.3>`__ - `1.4 Roadmap. <#1.4>`__ .. _11-introduction: 1.1 Introduction ---------------- .. _111-about-reference-implementation: 1.1.1 About Reference Implementation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This document includes the requirement and deployment details of the the first reference implementation for CNTT. This first reference implementation follows the requirement and architecture design of the `OpenStack Based Reference Architecture <../../../ref_arch/openstack/chapters>`__. This document will includes the detailed requirement of RI for CNTT, NFVi configurations according to the requirement of RA and each different flavor of VNF, Lab requirements for RI deployment and validation and installer requirement. This reference implementation will fully reveal the capabilities and features defined in CNTT RM and RA, and thus will be utilized as 'golden NFVi' in the Reference Compliance of CNTT. In order to promote quick deployment of RI and not re-invent wheels, the CNTT community works closely with OPNFV, utilizing and evolving OPNFV CI pipeline and installer automation and testing automation capabilities. Detailed collaboration and contribution to OPNFV will be concluded in the following sessions. .. _112-terminology: 1.1.2 Terminology ~~~~~~~~~~~~~~~~~ Terminology in this document will follow `CNTT Terminology <../../../common/glossary.md>`__. .. _12-scope: 1.2 Scope --------- The scope of this document is illustrated in **Figure 1-1** below: .. raw:: htmlFigure 1-1: RI-1 Scope.
a) generate eco-system requirements for the establishment of Reference Implementation, including Labs, toolings, installers, releases and automation requirements b) Provide detailed description file definition for installers, VNF features, and etc.. c) Provide detailed Lab criteria and operations d) Provide a Run-book for the first RI, which includes detailed steps for the deployment and configuration. e) Provide detailed design for automation of deployment and testing, provide continuous integration and delivery pipeline for RI f) Gap analysis with required actions for existing eco-system within LFN/OPNFV community projects .. _13-relationship-to-other-communities: 1.3 Relationship to other communities ------------------------------------- .. raw:: htmlFigure 1-2: RI-1 Relation to other communities.
1. Relationship with OPNFV Current collaboration with OPNFV includes: a) OPNFV CIRV project. This project is the 'landing' place for CNTT in OPNFV. It is responsible for driving activities of CNTT within OPNFV, working with multiple projects, including Airship, Functest, Dovetail, and ext.. The project team is working closely with the CNTT RI WSs. Detailed information of this project can be found here: `https://wiki.opnfv.org/pages/viewpage.action?pageId=47284396