diff options
Diffstat (limited to 'docs/installationprocedure')
3 files changed, 58 insertions, 22 deletions
diff --git a/docs/installationprocedure/abstract.rst b/docs/installationprocedure/abstract.rst index 728f0aa1c..853db170e 100644 --- a/docs/installationprocedure/abstract.rst +++ b/docs/installationprocedure/abstract.rst @@ -2,6 +2,10 @@ .. http://creativecommons.org/licenses/by/4.0 +******** +Abstract +******** + This document will give the user instructions on how to deploy available -KVM4NFV CICD build scenario verfied for the Colorado release of the OPNFV +KVM4NFV CICD build scenario verfied for the Danube release of the OPNFV platform. diff --git a/docs/installationprocedure/kvm4nfv-cicd.installation.instruction.rst b/docs/installationprocedure/kvm4nfv-cicd.installation.instruction.rst index 23177344e..ef6d32fc9 100644 --- a/docs/installationprocedure/kvm4nfv-cicd.installation.instruction.rst +++ b/docs/installationprocedure/kvm4nfv-cicd.installation.instruction.rst @@ -17,9 +17,9 @@ 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 +Intel POD10 is used as test environment for kvmfornfv to execute cyclictest. As +part of this test environment Intel pod10-jump is configured as jenkins slave +and all the latest build artifacts are downloaded on to it. Intel pod10-node1 is the host on which a guest vm will be launched as a part of running cylictest through yardstick. @@ -28,20 +28,44 @@ Build instructions Builds are possible for the following packages- -**kvmfornfv source code**- The ./ci/build.sh is the main script used to trigger +**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 + default case). Example: + +.. code:: bash + + cd kvmfornfv/ + + For Kernel/Qemu RPMs, + 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 + "ubuntu"). Example: + +.. code:: bash + + cd kvmfornfv/ + + For Kernel/Qemu Debians, + 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 + option is passed as "both"). Example: + +.. code:: bash + + cd kvmfornfv/ + + For Kernel/Qemu RPMs and Debians, + sh ./ci/build.sh -p both -o build_output Installation instructions ------------------------- diff --git a/docs/installationprocedure/kvm4nfv-cicd.release.notes.rst b/docs/installationprocedure/kvm4nfv-cicd.release.notes.rst index a54fe0b11..1913be8d7 100644 --- a/docs/installationprocedure/kvm4nfv-cicd.release.notes.rst +++ b/docs/installationprocedure/kvm4nfv-cicd.release.notes.rst @@ -10,8 +10,7 @@ Release Note for KVM4NFV CICD Abstract ======== -This document contains the release notes for the Colorado release of -OPNFV when using KVM4NFV CICD process. +This document contains the release notes for the Danube release of OPNFV when using KVM4NFV CICD process. Introduction ============ @@ -68,12 +67,12 @@ Module version change Document version change ~~~~~~~~~~~~~~~~~~~~~~~ The following documents are added- -- configurationguide -- instalationprocedure -- userguide -- overview -- glossary -- releasenotes + - configurationguide + - installationprocedure + - userguide + - overview + - glossary + - releasenotes Reason for new version ---------------------- @@ -85,10 +84,19 @@ Feature additions | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| JIRA: | NFV Hypervisors-KVMKVMFORNFV-34 | +| JIRA: | NFV Hypervisors-KVMFORNFV-34 | | | | +--------------------------------------+--------------------------------------+ -| JIRA: | NFV Hypervisors-KVMKVMFORNFV-34 | +| JIRA: | NFV Hypervisors-KVMFORNFV-57 | +| | | ++--------------------------------------+--------------------------------------+ +| JIRA: | NFV Hypervisors-KVMFORNFV-58 | +| | | ++--------------------------------------+--------------------------------------+ +| JIRA: | NFV Hypervisors-KVMFORNFV-59 | +| | | ++--------------------------------------+--------------------------------------+ +| JIRA: | NFV Hypervisors-KVMFORNFV-60 | | | | +--------------------------------------+--------------------------------------+ @@ -121,7 +129,7 @@ Known issues | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| JIRA: | | +| JIRA: | NFV Hypervisors-KVMFORNFV-75 | +--------------------------------------+--------------------------------------+ | JIRA: | | +--------------------------------------+--------------------------------------+ @@ -129,10 +137,10 @@ Known issues Workarounds ----------- -See JIRA: <link> +See JIRA: https://jira.opnfv.org/projects References ========== -For more information on the OPNFV Brahmaputra release, please visit -http://www.opnfv.org/brahmaputra +For more information on the OPNFV Danube release, please visit +http://www.opnfv.org/danube |