Installation procedure¶

Colorado 1.0¶

This document will give the user instructions on how to deploy available KVM4NFV CICD build scenario verfied for the Colorado release of the OPNFV platform.

1. KVM4NFV CICD Installation Instruction¶

1.1. Preparing the installation¶

The OPNFV project- KVM4NFV (https://gerrit.opnfv.org/gerrit/kvmfornfv.git) is cloned first, to make the build scripts for Qemu & Kernel, Rpms and Debians available.

1.2. HW requirements¶

These build scripts are triggered on the Jenkins-Slave build server. Currently Intel POD1 is used as test environment for kvmfornfv to execute cyclictest. As part of this test environment Intel pod1-jump is configured as jenkins slave and all the latest build artifacts are downloaded on to it. Intel pod1-node1 is the host on which a guest vm will be launched as a part of running cylictest through yardstick.

1.3. Build instructions¶

Builds are possible for the following packages-

kvmfornfv source code- The ./ci/build.sh is the main script used to trigger the Rpms (on ‘centos’) and Debians (on ‘ubuntu’) builds in this case.

How to build Kernel/Qemu Rpms- To build rpm packages, build.sh script is run with -p and -o option (i.e. if -p package option is passed as “centos” or in default case). Example: sh ./ci/build.sh -p centos -o build_output
How to build Kernel/Qemu Debians- To build debian packages, build.sh script is run with -p and -o option (i.e. if -p package option is passed as “ubuntu”). Example: sh ./ci/build.sh -p ubuntu -o build_output
How to build all Kernel & Qemu, Rpms & Debians- To build both debian and rpm packages, build.sh script is run with -p and -o option (i.e. if -p package option is passed as “both”). Example: sh ./ci/build.sh -p both -o build_output

1.4. Installation instructions¶

Installation can be done in the following ways-

1. From kvmfornfv source code- The build packages that are prepared in the above section, are installed differently depending on the platform.

Please visit the links for each-

2. Using Fuel installer-

Please refer to the document present at /fuel-plugin/README.md

1.5. Post-installation activities¶

After the packages are built, test these packages by executing the scripts present in ci/envs for configuring the host and guest respectively.

2. Release Note for KVM4NFV CICD¶

2.1. Abstract¶

This document contains the release notes for the Colorado release of OPNFV when using KVM4NFV CICD process.

2.2. Introduction¶

Provide a brief introduction of how this configuration is used in OPNFV release using KVM4VFV CICD as scenario.

Be sure to reference your scenario installation instruction.

2.3. Release Data¶

Project	NFV Hypervisors-KVM
Repo/tag	kvmfornfv
Release designation
Release date
Purpose of the delivery	Automate the KVM4VFV CICD scenario

2.3.1. Deliverables¶

2.3.1.1. Software deliverables¶

Kernel and Qemu- RPM and Debian build packages

2.3.1.2. Documentation deliverables¶

KVM4NFV CICD process documentation available under <project>/docs/ under various categories.

2.3.2. Version change¶

2.3.2.1. Module version change¶

Build scripts made available for Kernel rpm, Kernel deb, Qemu rpm, Qemu deb packages.
Releng scripts made available to trigger these kvm4nfv build scripts for automating complete CICD process.

2.3.2.2. Document version change¶

The following documents are added- - configurationguide - instalationprocedure - userguide - overview - glossary - releasenotes

2.3.3. Reason for new version¶

2.3.3.1. Feature additions¶

JIRA REFERENCE	SLOGAN
JIRA:	NFV Hypervisors-KVMKVMFORNFV-34
JIRA:	NFV Hypervisors-KVMKVMFORNFV-34

2.3.3.2. Bug corrections¶

JIRA TICKETS:

JIRA REFERENCE	SLOGAN
JIRA:

2.4. Known Limitations, Issues and Workarounds¶

2.4.1. System Limitations¶

2.4.2. Known issues¶