diff options
Diffstat (limited to 'docs/release/scenarios')
| -rw-r--r-- | docs/release/scenarios/abstract.rst | 42 | ||||
| -rw-r--r-- | docs/release/scenarios/index.rst | 24 | ||||
| -rw-r--r-- | docs/release/scenarios/kvmfornfv.scenarios.description.rst | 423 | ||||
| -rw-r--r-- | docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst | 10 | ||||
| -rwxr-xr-x | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/index.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst) | 6 | ||||
| -rw-r--r-- | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk-ha.description.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst) | 132 | ||||
| -rwxr-xr-x | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/index.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst) | 6 | ||||
| -rw-r--r-- | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/os-nosdn-kvm_ovs_dpdk-noha.description.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst) | 133 | ||||
| -rwxr-xr-x | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/index.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst) | 6 | ||||
| -rw-r--r-- | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/os-nosdn-kvm_ovs_dpdk_bar-ha.description.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst) | 20 | ||||
| -rwxr-xr-x | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/index.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst) | 6 | ||||
| -rw-r--r-- | docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/os-nosdn-kvm_ovs_dpdk_bar-noha.description.rst (renamed from docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst) | 26 |
12 files changed, 712 insertions, 122 deletions
diff --git a/docs/release/scenarios/abstract.rst b/docs/release/scenarios/abstract.rst index dcdd62fa9..2ccc437a5 100644 --- a/docs/release/scenarios/abstract.rst +++ b/docs/release/scenarios/abstract.rst @@ -4,39 +4,35 @@ ***************** Scenario Abstract ***************** -This chapter includes detailed explanation of various sceanrios files deployed as part -of kvm4nfv D-Release. +This chapter includes detailed explanation of various scenarios files deployed as part +of kvm4nfv E-Release. Release Features ---------------- -+------------------------------------------+------------------+-----------------+ -| **Scenario Name** | **Colorado** | **Danube** | -| | | | -+==========================================+==================+=================+ -| - os-nosdn-kvm-ha | ``Y`` | ``Y`` | -+------------------------------------------+------------------+-----------------+ -| - os-nosdn-kvm_nfv_ovs_dpdk-noha | | ``Y`` | -+------------------------------------------+------------------+-----------------+ -| - os-nosdn-kvm_nfv_ovs_dpdk-ha | | ``Y`` | -+------------------------------------------+------------------+-----------------+ -| - os-nosdn-kvm_nfv_ovs_dpdk_bar-noha | | ``Y`` | -+------------------------------------------+------------------+-----------------+ -| - os-nosdn-kvm_nfv_ovs_dpdk_bar-ha | | ``Y`` | -+------------------------------------------+------------------+-----------------+ ++------------------------------------------+------------------+-----------------+-------------------+ +| **Scenario Name** | **Colorado** | **Danube** | **Euphrates** | +| | | | | ++==========================================+==================+=================+===================+ +| - os-nosdn-kvm-ha | ``Y`` | ``Y`` | | ++------------------------------------------+------------------+-----------------+-------------------+ +| - os-nosdn-kvm_ovs_dpdk-noha | | ``Y`` | ``Y`` | ++------------------------------------------+------------------+-----------------+-------------------+ +| - os-nosdn-kvm_ovs_dpdk-ha | | ``Y`` | ``Y`` | ++------------------------------------------+------------------+-----------------+-------------------+ +| - os-nosdn-kvm_ovs_dpdk_bar-noha | | ``Y`` | | ++------------------------------------------+------------------+-----------------+-------------------+ +| - os-nosdn-kvm_ovs_dpdk_bar-ha | | ``Y`` | | ++------------------------------------------+------------------+-----------------+-------------------+ -D- Release Scenario's overview +E- Release Scenario's overview ------------------------------- +------------------------------------------+-----------------------+---------------------+------------------+----------+----------+ | **Scenario Name** | **No of Controllers** | **No of Computes** | **Plugin Names** | **DPDK** | **OVS** | | | | | | | | +==========================================+=======================+=====================+==================+==========+==========+ -| - ``os-nosdn-kvm_nfv_ovs_dpdk-noha`` | 1 | 3 | KVM | Y | Y | +| - ``os-nosdn-kvm_ovs_dpdk-noha`` | 1 | 1 | KVM | Y | Y | +------------------------------------------+-----------------------+---------------------+------------------+----------+----------+ -| - ``os-nosdn-kvm_nfv_ovs_dpdk-ha`` | 3 | 2 | KVM | Y | Y | -+------------------------------------------+-----------------------+---------------------+------------------+----------+----------+ -| - ``os-nosdn-kvm_nfv_ovs_dpdk_bar-noha`` | 1 | 3 | KVM & BAR | Y | Y | -+------------------------------------------+-----------------------+---------------------+------------------+----------+----------+ -| - ``os-nosdn-kvm_nfv_ovs_dpdk_bar-ha`` | 3 | 2 | KVM & BAR | Y | Y | +| - ``os-nosdn-kvm_ovs_dpdk-ha`` | 3 | 2 | KVM | Y | Y | +------------------------------------------+-----------------------+---------------------+------------------+----------+----------+ diff --git a/docs/release/scenarios/index.rst b/docs/release/scenarios/index.rst index f1f93c31a..def82debd 100644 --- a/docs/release/scenarios/index.rst +++ b/docs/release/scenarios/index.rst @@ -16,45 +16,45 @@ Scenario Overview and Description ./kvmfornfv.scenarios.description.rst ******************************************************* -os-nosdn-kvm_nfv_ovs_dpdk-noha Overview and Description +os-nosdn-kvm_ovs_dpdk-noha Overview and Description ******************************************************* .. toctree:: - :caption: os-nosdn-kvm_nfv_ovs_dpdk-noha + :caption: os-nosdn-kvm_ovs_dpdk-noha :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst + ./os-nosdn-kvm_ovs_dpdk-noha/os-nosdn-kvm_ovs_dpdk-noha.description.rst ***************************************************** -os-nosdn-kvm_nfv_ovs_dpdk-ha Overview and Description +os-nosdn-kvm_ovs_dpdk-ha Overview and Description ***************************************************** .. toctree:: - :caption: os-nosdn-kvm_nfv_ovs_dpdk-ha + :caption: os-nosdn-kvm_ovs_dpdk-ha :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst + ./os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk-ha.description.rst *********************************************************** -os-nosdn-kvm_nfv_ovs_dpdk_bar-noha Overview and Description +os-nosdn-kvm_ovs_dpdk_bar-noha Overview and Description *********************************************************** .. toctree:: - :caption: os-nosdn-kvm_nfv_ovs_dpdk_bar-noha + :caption: os-nosdn-kvm_ovs_dpdk_bar-noha :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst + ./os-nosdn-kvm_ovs_dpdk_bar-noha/os-nosdn-kvm_ovs_dpdk_bar-noha.description.rst ********************************************************* -os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Overview and Description +os-nosdn-kvm_ovs_dpdk_bar-ha Overview and Description ********************************************************* .. toctree:: - :caption: os-nosdn-kvm_nfv_ovs_dpdk_bar-ha + :caption: os-nosdn-kvm_ovs_dpdk_bar-ha :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst + ./os-nosdn-kvm_ovs_dpdk_bar-ha/os-nosdn-kvm_ovs_dpdk_bar-ha.description.rst diff --git a/docs/release/scenarios/kvmfornfv.scenarios.description.rst b/docs/release/scenarios/kvmfornfv.scenarios.description.rst index 5a5328666..bc8c585e7 100644 --- a/docs/release/scenarios/kvmfornfv.scenarios.description.rst +++ b/docs/release/scenarios/kvmfornfv.scenarios.description.rst @@ -29,10 +29,10 @@ Version Features +-----------------------------+---------------------------------------------+ | | - High Availability/No-High Availability | | | deployment configuration of KVM4NFV | -| | software suite | -| Danube | - Multi-node setup with 3 controller and | +| | software suite using Fuel | +| | - Multi-node setup with 3 controller and | | | 2 compute nodes are deployed for HA | -| | - Multi-node setup with 1 controller and | +| Danube | - Multi-node setup with 1 controller and | | | 3 compute nodes are deployed for NO-HA | | | - Scenarios os-nosdn-kvm_ovs_dpdk-ha, | | | os-nosdn-kvm_ovs_dpdk_bar-ha, | @@ -40,6 +40,18 @@ Version Features | | os-nosdn-kvm_ovs_dpdk_bar-noha | | | are supported | +-----------------------------+---------------------------------------------+ +| | - High Availability/No-High Availability | +| | deployment configuration of KVM4NFV | +| | software suite using Apex | +| | - Multi-node setup with 3 controller and | +| Euphrates | 2 compute nodes are deployed for HA | +| | - Multi-node setup with 1 controller and | +| | 1 compute node are deployed for NO-HA | +| | - Scenarios os-nosdn-kvm_ovs_dpdk-ha, | +| | os-nosdn-kvm_ovs_dpdk-noha, | +| | are supported | ++-----------------------------+---------------------------------------------+ + Introduction @@ -53,14 +65,18 @@ This OPNFV software suite includes OPNFV KVM4NFV latest software packages for Linux Kernel and QEMU patches for achieving low latency and also OPNFV Barometer for traffic, performance and platform monitoring. -High Availability feature is achieved by deploying OpenStack -multi-node setup with 1 Fuel-Master,3 controllers and 2 computes nodes. +When using Fuel installer, High Availability feature is achieved by deploying OpenStack +multi-node setup with 1 Fuel-Master,3 controllers and 2 computes nodes. No-High Availability +feature is achieved by deploying OpenStack multi-node setup with 1 Fuel-Master,1 controllers +and 3 computes nodes. -No-High Availability feature is achieved by deploying OpenStack -multi-node setup with 1 Fuel-Master,1 controllers and 3 computes nodes. +When using Apex installer, High Availability feature is achieved by deploying Openstack +multi-node setup with 1 undercloud, 3 overcloud controllers and 2 overcloud compute nodes. +No-High Availability feature is achieved by deploying Openstack multi-node setup with +1 undercloud, 1 overcloud controller and 1 overcloud compute nodes. KVM4NFV packages will be installed on compute nodes as part of deployment. -The scenario testcase deploys a multi-node setup by using OPNFV Fuel deployer. +The scenario testcase deploys a multi-node setup by using OPNFV Fuel and Apex deployer. System pre-requisites --------------------- @@ -103,11 +119,26 @@ If Nested virtualization is disabled, enable it by, Environment Setup ----------------- +**Enable network access after the installation** +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +For **CentOS**., +Login as "root" user. After the installation complete, the Ethernet interfaces are not enabled by +the default in Centos 7, you need to change the line "ONBOOT=no" to "ONBOOT=yes" in the network +interface configuration file (such as ifcfg-enp6s0f0 or ifcfg-em1 … whichever you want to connect) +in /etc/sysconfig/network-scripts sub-directory. The default BOOTPROTO is dhcp in the network +interface configuration file. Then use following command to enable the network access: + +.. code:: bash + + systemctl restart network + **Configuring Proxy** ~~~~~~~~~~~~~~~~~~~~~ For **Ubuntu**., -Create an apt.conf file in /etc/apt if it doesn't exist. Used to set proxy for apt-get if working behind a proxy server. +Create an apt.conf file in /etc/apt if it doesn't exist. Used to set proxy for apt-get if working +behind a proxy server. .. code:: bash @@ -123,6 +154,124 @@ Edit /etc/yum.conf to work behind a proxy server by adding the below line. $ echo "proxy=http://<username>:<password>@<proxy>:<port>/" >> /etc/yum.conf +**Install redsocks** +~~~~~~~~~~~~~~~~~~~~ + +For **CentOS**., +Since there is no redsocks package for CentOS Linux release 7.2.1511, you need build redsocks from +source yourself. Using following commands to create “proxy_redsocks” sub-directory at /root: + +.. code:: bash + + cd ~ + mkdir proxy_redsocks + +Since you can’t download file at your Centos system yet. At other Centos or Ubuntu system, use +following command to download redsocks source for Centos into a file “redsocks-src”; + +.. code:: bash + + wget -O redsocks-src --no-check-certificate https://github.com/darkk/redsocks/zipball/master + +Also download libevent-devel-2.0.21-4.el7.x86_64.rpm by: + +.. code:: bash + + wget ftp://fr2.rpmfind.net/linux/centos/7.2.1511/os/x86_64/Packages/libevent-devel-2.0.21-4.el7.x86_64.rpm + +Copy both redsock-src and libevent-devel-2.0.21-4.el7.x86_64.rpm files into ~/proxy_redsocks in your +Centos system by “scp”. + +Back to your Centos system, first install libevent-devel using libevent-devel-2.0.21-4.el7.x86_64.rpm +as below: + +.. code:: bash + + cd ~/proxy_redsocks + yum install –y libevent-devel-2.0.21-4.el7.x86_64.rpm + +Build redsocks by: + +.. code:: bash + + cd ~/proxy_redsocks + unzip redsocks-src + cd darkk-redsocks-78a73fc + yum –y install gcc + make + cp redsocks ~/proxy_redsocks/. + +Create a redsocks.conf in ~/proxy_redsocks with following contents: + +.. code:: bash + + base { + log_debug = on; + log_info = on; + log = "file:/root/proxy.log"; + daemon = on; + redirector = iptables; + } + redsocks { + local_ip = 0.0.0.0; + local_port = 6666; + // socks5 proxy server + ip = <proxy>; + port = 1080; + type = socks5; + } + redudp { + local_ip = 0.0.0.0; + local_port = 8888; + ip = <proxy>; + port = 1080; + } + dnstc { + local_ip = 127.0.0.1; + local_port = 5300; + } + +Start redsocks service by: + +.. code:: bash + + cd ~/proxy_redsocks + ./redsocks –c redsocks.conf + +*Note* +The redsocks service is not persistent and you need to execute the above-mentioned commands after +every reboot. + +Create intc-proxy.sh in ~/proxy_redsocks with following contents and make it executable by +“chmod +x intc-proxy.sh”: + +.. code:: bash + + iptables -t nat -N REDSOCKS + iptables -t nat -A REDSOCKS -d 0.0.0.0/8 -j RETURN + iptables -t nat -A REDSOCKS -d 10.0.0.0/8 -j RETURN + iptables -t nat -A REDSOCKS -d 127.0.0.0/8 -j RETURN + iptables -t nat -A REDSOCKS -d 169.254.0.0/16 -j RETURN + iptables -t nat -A REDSOCKS -d 172.16.0.0/12 -j RETURN + iptables -t nat -A REDSOCKS -d 192.168.0.0/16 -j RETURN + iptables -t nat -A REDSOCKS -d 224.0.0.0/4 -j RETURN + iptables -t nat -A REDSOCKS -d 240.0.0.0/4 -j RETURN + iptables -t nat -A REDSOCKS -p tcp -j REDIRECT --to-ports 6666 + iptables -t nat -A REDSOCKS -p udp -j REDIRECT --to-ports 8888 + iptables -t nat -A OUTPUT -p tcp -j REDSOCKS + iptables -t nat -A PREROUTING -p tcp -j REDSOCKS + +Enable the REDSOCKS nat chain rule by: + +.. code:: bash + + cd ~/proxy_redsocks + ./intc-proxy.sh + +*Note* +These REDSOCKS nat chain rules are not persistent and you need to execute the above-mentioned +commands after every reboot. + **Network Time Protocol (NTP) setup and configuration** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -133,7 +282,8 @@ Install ntp by: $ sudo apt-get update $ sudo apt-get install -y ntp -Insert the following two lines after “server ntp.ubuntu.com” line and before “ # Access control configuration; see `link`_ for” line in /etc/ntp.conf file: +Insert the following two lines after “server ntp.ubuntu.com” line and before “ # Access control +configuration; see `link`_ for” line in /etc/ntp.conf file: .. _link: /usr/share/doc/ntp-doc/html/accopt.html @@ -153,8 +303,9 @@ Scenario Testing There are three ways of performing scenario testing, - 1 Fuel - - 2 OPNFV-Playground - - 3 Jenkins Project + - 2 Apex + - 3 OPNFV-Playground + - 4 Jenkins Project Fuel ~~~~ @@ -235,14 +386,16 @@ To include fuel plugins in the deployment configuration file, use the “stack-e #module-config overrides **Note:** -The “module-config-name” and “module-config-version” should be same as the name of plugin configuration file. +The “module-config-name” and “module-config-version” should be same as the name of plugin +configuration file. The “module-config-override” is used to configure the plugin by overrriding the corresponding keys in the plugin config yaml file present in ~/fuel/deploy/config/plugins/. ``(iv). “dea-override-config” Module`` -To configure the HA/No-HA mode, network segmentation types and role to node assignments, use the “dea-override-config” key. +To configure the HA/No-HA mode, network segmentation types and role to node assignments, use the +“dea-override-config” key. .. code:: bash @@ -271,16 +424,22 @@ To configure the HA/No-HA mode, network segmentation types and role to node assi editable: storage: ephemeral_ceph: - description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes). + description: Configures Nova to store ephemeral volumes in RBD. + This works best if Ceph is enabled for volumes and images, too. + Enables live migration of all types of Ceph backed VMs (without this + option, live migration will only work with VMs launched from + Cinder volumes). label: Ceph RBD for ephemeral volumes (Nova) type: checkbox value: true weight: 75 images_ceph: - description: Configures Glance to use the Ceph RBD backend to store images.If enabled, this option will prevent Swift from installing. + description: Configures Glance to use the Ceph RBD backend to store + images.If enabled, this option will prevent Swift from installing. label: Ceph RBD for images (Glance) restrictions: - - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected. + - settings:storage.images_vcenter.value == true: Only one Glance + backend could be selected. type: checkbox value: true weight: 30 @@ -296,7 +455,8 @@ This is an optional key present at the ending of the scenario file. ``(vi). Mapping to short scenario name`` -The scenario.yaml file is used to map the short names of scenario's to the one or more deployment scenario configuration yaml files. +The scenario.yaml file is used to map the short names of scenario's to the one or more deployment +scenario configuration yaml files. The short scenario names should follow the scheme below: .. code:: bash @@ -306,7 +466,8 @@ The short scenario names should follow the scheme below: [os]: mandatory possible value: os -Please note that this field is needed in order to select parent jobs to list and do blocking relations between them. +Please note that this field is needed in order to select parent jobs to list and do blocking +relations between them. .. code:: bash @@ -349,7 +510,8 @@ Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario: .. code:: bash $ cd ~/fuel/ci/ - $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso + $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \ + -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso where, ``-b`` is used to specify the configuration directory @@ -370,6 +532,203 @@ where, Check $ sudo ./deploy.sh -h for further information. +Apex +~~~~ + +Apex installer uses CentOS as the platform. + +**1 Install Packages :** + +Install necessary packages by following: + +.. code:: bash + + cd ~ + yum install –y git rpm-build python-setuptools python-setuptools-devel + yum install –y epel-release gcc + curl -O https://bootstrap.pypa.io/get-pip.py + um install –y python3 python34 + /usr/bin/python3.4 get-pip.py + yum install –y python34-devel python34-setuptools + yum install –y libffi-devel python-devel openssl-devel + yum -y install libxslt-devel libxml2-devel + +Then you can use “dev_deploy_check.sh“ in Apex installer source to install the remaining necessary +packages by following: + +.. code:: bash + + cd ~ + git clone https://gerrit.opnfv.org/gerrit/p/apex.git + export CONFIG=$(pwd)/apex/build + export LIB=$(pwd)/apex/lib + export PYTHONPATH=$PYTHONPATH:$(pwd)/apex/lib/python + cd ci + ./dev_deploy_check.sh + yum install –y python2-oslo-config python2-debtcollector + + +**2 Create ssh key :** + +Use following commands to create ssh key, when asked for passphrase, just enter return for empty +passphrase: + +.. code:: bash + + cd ~ + ssh-keygen -t rsa + +Then prepare the authorized_keys for Apex scenario deployment: + +.. code:: bash + + cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys + +**3 Create default pool :** + +Use following command to default pool device: + +.. code:: bash + + cd ~ + virsh pool-define /dev/stdin <<EOF + <pool type='dir'> + <name>default</name> + <target> + <path>/var/lib/libvirt/images</path> + </target> + </pool> + EOF + +Use following commands to start and set autostart the default pool device: + +.. code:: bash + + virsh pool-start default + virsh pool-autostart default + +Use following commands to verify the success of the creation of the default pool device and starting +and setting autostart of the default pool device: + +.. code:: bash + + virsh pool-list + virsh pool-info default + +**4 Get Apex source code :** + +Get Apex installer source code: + +.. code:: bash + + git clone https://gerrit.opnfv.org/gerrit/p/apex.git + cd apex + +**5 Modify code to work behind proxy :** + +In “lib” sub-directory of Apex source, change line 284 “if ping -c 2 www.google.com > /dev/null; +then” to “if curl www.google.com > /dev/null; then” in “common-functions.sh” file, since we can’t +ping www.google.com behind Intel proxy. + +**6 Setup build environment :** + +Setup build environment by: + +.. code:: bash + + cd ~ + export BASE=$(pwd)/apex/build + export LIB=$(pwd)/apex/lib + export PYTHONPATH=$PYTHONPATH:$(pwd)/apex/lib/python + export IMAGES=$(pwd)/apex/.build + +**7 Build Apex installer :** + +Build undercloud image by: + +.. code:: bash + + cd ~/apex/build + make images-clean + make undercloud + +You can look at the targets in ~/apex/build/Makefile to build image for specific feature. +Following show how to build vanilla ODL image (this can be used to build the overcloud image for +basic (nosdn-nofeature) and opendaylight test scenario: + +.. code:: bash + + cd ~/apex/build + make overcloud-opendaylight + +You can build the complete full set of images (undercloud, overcloud-full, overcloud-opendaylight, +overcloud-onos) by: + +.. code:: bash + + cd ~/apex/build + make images + +**8 Modification of network_settings.yaml :** + +Since we are working behind proxy, we need to modify the network_settings.yaml in ~/apex/config/network +to make the deployment work properly. In order to avoid checking our modification into the repo +accidentally, it is recommend that you copy “network_settings.yaml” to “intc_network_settings.yaml” +in the ~/apex/config/network and do following modification in intc_network_settings.yaml: + +Change dns_nameservers settings from + +.. code:: bash + + dns_servers: ["8.8.8.8", "8.8.4.4"] +to + +.. code:: bash + + dns_servers: ["<ip-address>"] + +Also, you need to modify deploy.sh in apex/ci from “ntp_server="pool.ntp.org"” to +“ntp_server="<ip-address>"” to reflect that fact we couldn’t reach outside NTP server, just use +local time. + +**9 Commands to deploy scenario :** + +Following shows the commands used to deploy os-nosdn-kvm_ovs_dpdk-noha scenario behind the proxy: + +.. code:: bash + + cd ~/apex/ci + ./clean.sh + ./dev_deploy_check.sh + ./deploy.sh -v --ping-site <ping_ip-address> --dnslookup-site <dns_ip-address> -n \ + ~/apex/config/network/intc_network_settings.yaml -d \ + ~/apex/config/deploy/os-nosdn-kvm_ovs_dpdk-noha.yaml + +**10 Accessing the Overcloud dashboard :** + +If the deployment completes successfully, the last few output lines from the deployment will look +like the following: + +.. code:: bash + + INFO: Undercloud VM has been setup to NAT Overcloud public network + Undercloud IP: <ip-address>, please connect by doing 'opnfv-util undercloud' + Overcloud dashboard available at http://<ip-address>/dashboard + INFO: Post Install Configuration Complete + +**11 Accessing the Undercloud and Overcloud through command line :** + +At the end of the deployment we obtain the Undercloud ip. One can login to the Undercloud and obtain +the Overcloud ip as follows: + +.. code:: bash + + cd ~/apex/ci/ + ./util.sh undercloud + source stackrc + nova list + ssh heat-admin@<overcloud-ip> + OPNFV-Playground ~~~~~~~~~~~~~~~~ @@ -382,8 +741,10 @@ Install OPNFV-playground (the tool chain to deploy/test CI scenarios in fuel@opn $ git clone https://github.com/jonasbjurel/OPNFV-Playground.git $ cd OPNFV-Playground/ci_fuel_opnfv/ -- Follow the README.rst in this ~/OPNFV-Playground/ci_fuel_opnfv sub-holder to complete all necessary installation and setup. -- Section “RUNNING THE PIPELINE” in README.rst explain how to use this ci_pipeline to deploy/test CI test scenarios, you can also use +- Follow the README.rst in this ~/OPNFV-Playground/ci_fuel_opnfv sub-holder to complete all necessary +installation and setup. +- Section “RUNNING THE PIPELINE” in README.rst explain how to use this ci_pipeline to deploy/test CI +test scenarios, you can also use .. code:: bash @@ -393,14 +754,16 @@ Install OPNFV-playground (the tool chain to deploy/test CI scenarios in fuel@opn ``1 Downgrade paramiko package from 2.x.x to 1.10.0`` -The paramiko package 2.x.x doesn’t work with OPNFV-playground tool chain now, Jira ticket FUEL - 188 has been raised for the same. +The paramiko package 2.x.x doesn’t work with OPNFV-playground tool chain now, Jira ticket FUEL - 188 +has been raised for the same. Check paramiko package version by following below steps in your system: .. code:: bash $ python - Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. + Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] on linux2 Type "help", "copyright", + "credits" or "license" for more information. >>> import paramiko >>> print paramiko.__version__ @@ -448,7 +811,8 @@ Implement the scenario file as described in 3.1.4 ``4 Deploying the scenario`` -You can use the following command to deploy/test os-nosdn kvm_ovs_dpdk-(no)ha and os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario +You can use the following command to deploy/test os-nosdn kvm_ovs_dpdk-(no)ha and +os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario .. code:: bash @@ -482,12 +846,15 @@ Note: Jenkins Project ~~~~~~~~~~~~~~~ -os-nosdn-kvm_ovs_dpdk-(no)ha and os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario can be executed from the jenkins project : +os-nosdn-kvm_ovs_dpdk-(no)ha and os-nosdn-kvm_ovs_dpdk_bar-(no)ha scenario can be executed from the +jenkins project : ``HA scenarios:`` 1. "fuel-os-nosdn-kvm_ovs_dpdk-ha-baremetal-daily-master" (os-nosdn-kvm_ovs_dpdk-ha) 2. "fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master" (os-nosdn-kvm_ovs_dpdk_bar-ha) + 3. "apex-os-nosdn-kvm_ovs_dpdk-ha-baremetal-master" (os-nosdn-kvm_ovs_dpdk-ha) ``NOHA scenarios:`` - 1. "fuel-os-nosdn-kvm_ovs_dpdk-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk-noha) - 2. "fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk_bar-noha) + 1. "fuel-os-nosdn-kvm_ovs_dpdk-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk-noha) + 2. "fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-virtual-daily-master" (os-nosdn-kvm_ovs_dpdk_bar-noha) + 3. "apex-os-nosdn-kvm_ovs_dpdk-noha-baremetal-master" (os-nosdn-kvm_ovs_dpdk-noha) diff --git a/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst index f64f26ffc..a02033d58 100644 --- a/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst +++ b/docs/release/scenarios/os-nosdn-kvm-ha/os-nosdn-kvm-ha.description.rst @@ -98,7 +98,8 @@ Scenario Usage Overview .. code:: bash - sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/hardware/dea.yaml -dha ~/CONF/hardware/dha.yaml -s /mnt/images -b pxebr -log ~/Deployment-888.log.tar.gz + sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/hardware/dea.yaml -dha \ + ~/CONF/hardware/dha.yaml -s /mnt/images -b pxebr -log ~/Deployment-888.log.tar.gz * Install Fuel Master and deploy OPNFV Cloud from scratch on Virtual Environment: @@ -107,7 +108,8 @@ Scenario Usage Overview .. code:: bash - sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/virtual/dea.yaml -dha ~/CONF/virtual/dha.yaml -s /mnt/images -log ~/Deployment-888.log.tar.gz + sudo python deploy.py -iso ~/ISO/opnfv.iso -dea ~/CONF/virtual/dea.yaml -dha \ + ~/CONF/virtual/dha.yaml -s /mnt/images -log ~/Deployment-888.log.tar.gz * os-nosdn-kvm-ha scenario can be executed from the jenkins project "fuel-os-nosdn-kvm-ha-baremetal-daily-master" @@ -129,5 +131,5 @@ Known Limitations, Issues and Workarounds References ---------- -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/danube +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/euphrates diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/index.rst index ddb6071c8..70a7fbf11 100755 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/index.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/index.rst @@ -1,14 +1,14 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk-ha: +.. _kvmfornfv-os-nosdn-kvm_ovs_dpdk-ha: ***************************************************** -os-nosdn-kvm_nfv_ovs_dpdk-ha Overview and Description +os-nosdn-kvm_ovs_dpdk-ha Overview and Description ***************************************************** .. toctree:: :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst + ./os-nosdn-kvm_ovs_dpdk-ha.description.rst diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk-ha.description.rst index a96130cad..9fac19247 100644 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-ha/os-nosdn-kvm_nfv_ovs_dpdk-ha.description.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk-ha.description.rst @@ -3,7 +3,7 @@ .. http://creativecommons.org/licenses/by/4.0 ========================================= -os-nosdn-kvm_nfv_ovs_dpdk-ha Description +os-nosdn-kvm_ovs_dpdk-ha Description ========================================= Introduction @@ -20,7 +20,11 @@ QEMU patches for achieving low latency. High Availability feature is achieved by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes. KVM4NFV packages will be installed on compute nodes as part of deployment. -This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer. +This scenario testcase deployment is happening on multi-node by using OPNFV Fuel +and Apex deployer. + + +**Using Fuel Installer** Scenario Components and Composition ----------------------------------- @@ -135,13 +139,17 @@ argument to deploy.py script editable: storage: ephemeral_ceph: - description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes). + description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph + is enabled for volumes and images, too. Enables live migration of all types of Ceph + backed VMs (without this option, live migration will only work with VMs launched from + Cinder volumes). label: Ceph RBD for ephemeral volumes (Nova) type: checkbox value: true weight: 75 images_ceph: - description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing. + description: Configures Glance to use the Ceph RBD backend to store images. If enabled, + this option will prevent Swift from installing. label: Ceph RBD for images (Glance) restrictions: - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected. @@ -190,7 +198,8 @@ argument to deploy.py script * In os-nosdn-kvm_ovs_dpdk-ha scenario, OVS is installed on the compute nodes with DPDK configured -* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml +* Hugepages for DPDK are configured in the attributes_1 section of the +no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml * Hugepages are only configured for compute nodes @@ -199,7 +208,7 @@ argument to deploy.py script Scenario Usage Overview ----------------------- .. Provide a brief overview on how to use the scenario and the features available to the -.. user. This should be an "introduction" to the userguide document, and explicitly link to it, +.. user. This should be an "introduction" to the userguide document, and explicitly link to it, .. where the specifics of the features are covered including examples and API's * The high availability feature can be acheived by executing deploy.py with @@ -213,7 +222,8 @@ Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario: .. code:: bash $ cd ~/fuel/ci/ - $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso + $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \ + -s ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso where, -b is used to specify the configuration directory @@ -234,14 +244,110 @@ where, * Test Scenario is passed if deployment is successful and all 5 nodes have accessibility (IP , up & running). -Known Limitations, Issues and Workarounds ------------------------------------------ -.. Explain any known limitations here. -* Test scenario os-nosdn-kvm_ovs_dpdk-ha result is not stable. +**Using Apex Installer** + +Scenario Components and Composition +----------------------------------- +.. In this section describe the unique components that make up the scenario, +.. what each component provides and why it has been included in order +.. to communicate to the user the capabilities available in this scenario. + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +All services are in HA, meaning that there are multiple cloned instances of +each service, and they are balanced by HA Proxy using a Virtual IP Address +per service. + +The os-nosdn-kvm_ovs_dpdk-ha.yaml file contains following configurations and +is passed as an argument to deploy.sh script. + +* ``global-params:`` Used to define the global parameter and there is only one + such parameter exists,i.e, ha_enabled + +.. code:: bash + + global-params: + ha_enabled: true + +* ``deploy_options:`` Used to define the type of SDN controller, configure the + tacker, congress, service functioning chaining support(sfc) for ODL and ONOS, + configure ODL with SDNVPN support, which dataplane to use for overcloud + tenant networks, whether to run the kvm real time kernel (rt_kvm) in the + compute node(s) to reduce the network latencies caused by network function + virtualization and whether to install and configure fdio functionality in the + overcloud + +.. code:: bash + + deploy_options: + sdn_controller: false + tacker: true + congress: true + sfc: false + vpn: false + rt_kvm: true + dataplane: ovs_dpdk + +* ``performance:`` Used to set performance options on specific roles. The valid + roles are 'Compute', 'Controller' and 'Storage', and the valid sections are + 'kernel' and 'nova' + +.. code:: bash + + performance: + Controller: + kernel: + hugepages: 1024 + hugepagesz: 2M + Compute: + kernel: + hugepagesz: 2M + hugepages: 2048 + intel_iommu: 'on' + iommu: pt + ovs: + socket_memory: 1024 + pmd_cores: 2 + dpdk_cores: 1 + +Scenario Usage Overview +----------------------- +.. Provide a brief overview on how to use the scenario and the features available to the +.. user. This should be an "introduction" to the userguide document, and explicitly link to it, +.. where the specifics of the features are covered including examples and API's + +* The high availability feature can be acheived by executing deploy.sh with + os-nosdn-kvm_ovs_dpdk-ha.yaml as an argument. + +* Build the undercloud and overcloud images as mentioned below: + +.. code:: bash + + cd ~/apex/build/ + make images-clean + make images + +* Command to deploy os-nosdn-kvm_ovs_dpdk-ha scenario: + +.. code:: bash + + cd ~/apex/ci/ + ./clean.sh + ./dev_dep_check.sh + ./deploy.sh -v --ping-site <ping_ip-address> --dnslookup-site <dns_ip-address> -n \ + ~/apex/config/network/intc_network_settings.yaml -d ~/apex/config/deploy/os-nosdn-kvm_ovs_dpdk-ha.yaml + +where, + -v is used for virtual deployment + -n is used for providing the network configuration file + -d is used for providing the scenario configuration file References ---------- -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/Danube +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/Euphrates diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/index.rst index 742ddb1ee..e5901cc62 100755 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/index.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/index.rst @@ -1,14 +1,14 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk-noha: +.. _kvmfornfv-os-nosdn-kvm_ovs_dpdk-noha: ******************************************************* -os-nosdn-kvm_nfv_ovs_dpdk-noha Overview and Description +os-nosdn-kvm_ovs_dpdk-noha Overview and Description ******************************************************* .. toctree:: :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst + ./os-nosdn-kvm_ovs_dpdk-noha.description.rst diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/os-nosdn-kvm_ovs_dpdk-noha.description.rst index a7778d963..6bd5d4adc 100644 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk-noha/os-nosdn-kvm_nfv_ovs_dpdk-noha.description.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk-noha/os-nosdn-kvm_ovs_dpdk-noha.description.rst @@ -3,7 +3,7 @@ .. http://creativecommons.org/licenses/by/4.0 ========================================== -os-nosdn-kvm_nfv_ovs_dpdk-noha Description +os-nosdn-kvm_ovs_dpdk-noha Description ========================================== Introduction @@ -16,11 +16,17 @@ The purpose of os-nosdn-kvm_ovs_dpdk-noha scenario testing is to test the No High Availability deployment and configuration of OPNFV software suite with OpenStack and without SDN software. This OPNFV software suite includes OPNFV KVM4NFV latest software packages for Linux Kernel and -QEMU patches for achieving low latency. No High Availability feature is achieved -by deploying OpenStack multi-node setup with 1 controller and 3 computes nodes. +QEMU patches for achieving low latency. When deployed using Fuel, No High +Availability feature is achieved by deploying OpenStack multi-node setup with +1 controller and 3 computes nodes and using Apex the setup is with 1 controller +and 1 compute. KVM4NFV packages will be installed on compute nodes as part of deployment. -This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer. +This scenario testcase deployment is happening on multi-node by using OPNFV Fuel +and Apex deployer. + + +**Using Fuel Installer** Scenario Components and Composition ------------------------------------ @@ -151,13 +157,17 @@ argument to deploy.py script editable: storage: ephemeral_ceph: - description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes). + description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph + is enabled for volumes and images, too. Enables live migration of all types of Ceph + backed VMs (without this option, live migration will only work with VMs launched from + Cinder volumes). label: Ceph RBD for ephemeral volumes (Nova) type: checkbox value: true weight: 75 images_ceph: - description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing. + description: Configures Glance to use the Ceph RBD backend to store images. If enabled, + this option will prevent Swift from installing. label: Ceph RBD for images (Glance) restrictions: - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected. @@ -180,7 +190,8 @@ argument to deploy.py script * In os-nosdn-kvm_ovs_dpdk-noha scenario, OVS is installed on the compute nodes with DPDK configured -* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml +* Hugepages for DPDK are configured in the attributes_1 section of the +no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml * Hugepages are only configured for compute nodes @@ -205,7 +216,8 @@ Command to deploy the os-nosdn-kvm_ovs_dpdk-noha scenario: .. code:: bash $ cd ~/fuel/ci/ - $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso + $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \ + -s no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso where, -b is used to specify the configuration directory @@ -226,14 +238,107 @@ where, * Test Scenario is passed if deployment is successful and all 4 nodes have accessibility (IP , up & running). -Known Limitations, Issues and Workarounds ------------------------------------------ -.. Explain any known limitations here. -* Test scenario os-nosdn-kvm_ovs_dpdk-noha result is not stable. +**Using Apex Installer** + +Scenario Components and Composition +----------------------------------- +.. In this section describe the unique components that make up the scenario, +.. what each component provides and why it has been included in order +.. to communicate to the user the capabilities available in this scenario. + +This scenario is composed of common OpenStack services enabled by default, +including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and +by default, Tacker and Congress services are also enabled. Ceph is used as +the backend storage to Cinder on all deployed nodes. + +The os-nosdn-kvm_ovs_dpdk-noha.yaml file contains following configurations and +is passed as an argument to deploy.sh script. + +* ``global-params:`` Used to define the global parameter and there is only one + such parameter exists,i.e, ha_enabled + +.. code:: bash + + global-params: + ha_enabled: false + +* ``deploy_options:`` Used to define the type of SDN controller, configure the + tacker, congress, service functioning chaining support(sfc) for ODL and ONOS, + configure ODL with SDNVPN support, which dataplane to use for overcloud + tenant networks, whether to run the kvm real time kernel (rt_kvm) in the + compute node(s) to reduce the network latencies caused by network function + virtualization and whether to install and configure fdio functionality in the + overcloud + +.. code:: bash + + deploy_options: + sdn_controller: false + tacker: true + congress: true + sfc: false + vpn: false + rt_kvm: true + dataplane: ovs_dpdk + +* ``performance:`` Used to set performance options on specific roles. The valid + roles are 'Compute', 'Controller' and 'Storage', and the valid sections are + 'kernel' and 'nova' + +.. code:: bash + + performance: + Controller: + kernel: + hugepages: 1024 + hugepagesz: 2M + Compute: + kernel: + hugepagesz: 2M + hugepages: 2048 + intel_iommu: 'on' + iommu: pt + ovs: + socket_memory: 1024 + pmd_cores: 2 + dpdk_cores: 1 + +Scenario Usage Overview +----------------------- +.. Provide a brief overview on how to use the scenario and the features available to the +.. user. This should be an "introduction" to the userguide document, and explicitly link to it, +.. where the specifics of the features are covered including examples and API's + +* The high availability feature can be acheived by executing deploy.sh with + os-nosdn-kvm_ovs_dpdk-noha.yaml as an argument. + +* Build the undercloud and overcloud images as mentioned below: + +.. code:: bash + + cd ~/apex/build/ + make images-clean + make images + +* Command to deploy os-nosdn-kvm_ovs_dpdk-noha scenario: + +.. code:: bash + + cd ~/apex/ci/ + ./clean.sh + ./dev_dep_check.sh + ./deploy.sh -v --ping-site <ping_ip-address> --dnslookup-site <dns_ip-address> -n \ + ~/apex/config/network/intc_network_settings.yaml -d ~/apex/config/deploy/os-nosdn-kvm_ovs_dpdk-noha.yaml + +where, + -v is used for virtual deployment + -n is used for providing the network configuration file + -d is used for providing the scenario configuration file + References ---------- -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/Danube +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/Euphrates diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/index.rst index a8192edcc..73e7927fd 100755 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/index.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/index.rst @@ -1,14 +1,14 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk_bar-ha: +.. _kvmfornfv-os-nosdn-kvm_ovs_dpdk_bar-ha: ********************************************************* -os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Overview and Description +os-nosdn-kvm_ovs_dpdk_bar-ha Overview and Description ********************************************************* .. toctree:: :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst + ./os-nosdn-kvm_ovs_dpdk_bar-ha.description.rst diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/os-nosdn-kvm_ovs_dpdk_bar-ha.description.rst index 0ab20514a..ee182297a 100644 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha/os-nosdn-kvm_nfv_ovs_dpdk_bar-ha.description.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-ha/os-nosdn-kvm_ovs_dpdk_bar-ha.description.rst @@ -3,7 +3,7 @@ .. http://creativecommons.org/licenses/by/4.0 ============================================ -os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description +os-nosdn-kvm_ovs_dpdk_bar-ha Description ============================================ Introduction @@ -142,13 +142,17 @@ argument to deploy.py script editable: storage: ephemeral_ceph: - description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes). + description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph + is enabled for volumes and images, too. Enables live migration of all types of Ceph + backed VMs (without this option, live migration will only work with VMs launched from + Cinder volumes). label: Ceph RBD for ephemeral volumes (Nova) type: checkbox value: true weight: 75 images_ceph: - description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing. + description: Configures Glance to use the Ceph RBD backend to store images. If enabled, + this option will prevent Swift from installing. label: Ceph RBD for images (Glance) restrictions: - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected. @@ -199,7 +203,8 @@ argument to deploy.py script * Baraometer plugin is also implemented along with KVM plugin -* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml +* Hugepages for DPDK are configured in the attributes_1 section of the +no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml * Hugepages are only configured for compute nodes @@ -223,7 +228,8 @@ Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-ha scenario: .. code:: bash $ cd ~/fuel/ci/ - $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso + $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \ + -s ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso where, -b is used to specify the configuration directory @@ -253,5 +259,5 @@ Known Limitations, Issues and Workarounds References ---------- -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/Danube +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/Euphrates diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/index.rst index 3a07e98c9..e1557b0fe 100755 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/index.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/index.rst @@ -1,14 +1,14 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -.. _kvmfornfv-os-nosdn-kvm_nfv_ovs_dpdk_bar-noha: +.. _kvmfornfv-os-nosdn-kvm_ovs_dpdk_bar-noha: *********************************************************** -os-nosdn-kvm_nfv_ovs_dpdk_bar-noha Overview and Description +os-nosdn-kvm_ovs_dpdk_bar-noha Overview and Description *********************************************************** .. toctree:: :numbered: :maxdepth: 3 - ./os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst + ./os-nosdn-kvm_ovs_dpdk_bar-noha.description.rst diff --git a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/os-nosdn-kvm_ovs_dpdk_bar-noha.description.rst index 47a7f1034..48f2852fe 100644 --- a/docs/release/scenarios/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha/os-nosdn-kvm_nfv_ovs_dpdk_bar-noha.description.rst +++ b/docs/release/scenarios/os-nosdn-kvm_ovs_dpdk_bar-noha/os-nosdn-kvm_ovs_dpdk_bar-noha.description.rst @@ -3,7 +3,7 @@ .. http://creativecommons.org/licenses/by/4.0 ============================================ -os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description +os-nosdn-kvm_ovs_dpdk_bar-ha Description ============================================ Introduction @@ -51,7 +51,8 @@ argument to deploy.py script * ``stack-extensions:`` Stack extentions are opnfv added value features in form of a fuel-plugin.Plugins listed in stack extensions are enabled and - configured. os-nosdn-kvm_ovs_dpdk_bar-noha scenario currently uses KVM-1.0.0 plugin and barometer-1.0.0 plugin. + configured. os-nosdn-kvm_ovs_dpdk_bar-noha scenario currently uses KVM-1.0.0 plugin and + barometer-1.0.0 plugin. .. code:: bash @@ -157,13 +158,17 @@ argument to deploy.py script editable: storage: ephemeral_ceph: - description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph is enabled for volumes and images, too. Enables live migration of all types of Ceph backed VMs (without this option, live migration will only work with VMs launched from Cinder volumes). + description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph + is enabled for volumes and images, too. Enables live migration of all types of Ceph + backed VMs (without this option, live migration will only work with VMs launched from + Cinder volumes). label: Ceph RBD for ephemeral volumes (Nova) type: checkbox value: true weight: 75 images_ceph: - description: Configures Glance to use the Ceph RBD backend to store images. If enabled, this option will prevent Swift from installing. + description: Configures Glance to use the Ceph RBD backend to store images. If enabled, + this option will prevent Swift from installing. label: Ceph RBD for images (Glance) restrictions: - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected. @@ -174,7 +179,8 @@ argument to deploy.py script * ``dha-override-config:`` Provides information about the VM definition and Network config for virtual deployment.These configurations overrides the pod dha definition and points to the controller,compute and - fuel definition files. The noha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml has no dha-config changes i.e., default configuration is used. + fuel definition files. The noha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml has no + dha-config changes i.e., default configuration is used. * os-nosdn-kvm_ovs_dpdk_bar-noha scenario is successful when all the 4 Nodes are accessible, up and running. @@ -187,7 +193,8 @@ argument to deploy.py script * Baraometer plugin is also implemented along with KVM plugin. -* Hugepages for DPDK are configured in the attributes_1 section of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml +* Hugepages for DPDK are configured in the attributes_1 section of the + no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml * Hugepages are only configured for compute nodes @@ -210,7 +217,8 @@ Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-noha scenario: .. code:: bash $ cd ~/fuel/ci/ - $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default -s no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso + $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \ + -s no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso where, -b is used to specify the configuration directory @@ -240,5 +248,5 @@ Known Limitations, Issues and Workarounds References ---------- -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/Danube +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/Euphrates |