Objectives Create a new VNF or Network Service project that will hold all of its descriptor, test and lifecycle script artifacts. Pre-requisites Access to a CI/CD Hub and a development environment with a Lifecycle Manager and VIM Design details of the new VNF or Network Service. VNFCs or VNFs it will contain (name and version) Software Images associated with each VNFC. (There may be multiple images for each target VIM type, e. »

Objectives Manage versions of all VNF or test software images in a general repository. Making the images available in a formal manner to the CI/CD tools. Pre-requisites You are provided with the software images to upload on your local machine. Repository Structure The image directory structure in the CI/CD nexus general repository is as follows: . ├── raw └── vdus └── <vdu-name> ├── <image-name-version>.<type> ├── image-3.4.12.qcow2 ├── image-3.4.00.tar To upload an image into nexus: »

Objectives Develop VNF or Network Service project artifacts that, when complete, will constitute a releasable package. Pre-requisites CI/CD Hub and a development environment with a dedicated Telco Network Cloud Orchestration (TNC-O) and VIM A VNF or Network Service project already exists. Developing a VNF or Network Service Descriptor Push your project into dev environment (assume this is called ‘dev’ in the LMCONFIG file for LMCTL): $ cd <myvnf dir> $ lmctl project push dev Design the VNF or Network Service Descriptor »

Objectives Release a VNF or Network Service package that has been confirmed ready for production use to a production environment Pre-requisites The VNF or Network Service package is available in the Nexus general repository and marked ready for production deployment. Introduction When a package has been developed and its been agreed that it has been fully tested by its stakeholders, it can be released. Releasing a VNF or Network Service package is done by triggering the Release pipeline job manually in Jenkins and giving the version of the package to deploy. »

Objectives This section shows how to add VNF functional behaviour tests or Network Service performance and interoperability test artifacts to your project structure in the CI/CD Hub. Pre-requisites Development VIM and CI/CD Hub and TNC-O up and running LMCTL setup on your local machine with a profile configured for the above development environment VNF design documenting how test scenarios are expected to be run and the metrics and behaviour from all participating VNFs that constitute a successful test run. »

Objectives Update a VNF or NS Project after Release One a version of a project has been packaged and released it cannot be updated. A new version must be created and tested. Pre-requisites Existing package New package Update Project to next version In the case where you want to update the last version: Checkout the project on the develop branch Edit the projects descriptor (VNF or NS) to increment the version Edit the the Behaviour test template for the NS or VNF being tested to the new version make changes to your project for the update. »