Scenario Overview and Description¶

1. Scenario Abstract¶

This chapter includes detailed explanation of various sceanrios files deployed as part of kvm4nfv D-Release.

1.1. 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`

1.2. D- 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_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

2. KVM4NFV Scenario-Description¶

2.1. Abstract¶

This document describes the procedure to deploy/test KVM4NFV scenarios in a nested virtualization environment. This has been verified with os-nosdn-kvm-ha, os-nosdn-kvm-noha,os-nosdn-kvm_ovs_dpdk-ha, os-nosdn-kvm_ovs_dpdk-noha and os-nosdn-kvm_ovs_dpdk_bar-ha test scenarios.

2.2. Version Features¶

Release	Features
Colorado	Scenario Testing feature was not part of the Colorado release of KVM4NFV
Danube	High Availability/No-High Availability deployment configuration of KVM4NFV software suite Multi-node setup with 3 controller and 2 compute nodes are deployed for HA 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, os-nosdn-kvm_ovs_dpdk-noha, os-nosdn-kvm_ovs_dpdk_bar-noha are supported

2.3. Introduction¶

The purpose of os-nosdn-kvm_ovs_dpdk-ha,os-nosdn-kvm_ovs_dpdk_bar-ha and os-nosdn-kvm_ovs_dpdk-noha,os-nosdn-kvm_ovs_dpdk_bar-noha scenarios testing is to test the High Availability/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 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.

No-High Availability feature is achieved by deploying OpenStack multi-node setup with 1 Fuel-Master,1 controllers and 3 computes 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.

2.4. System pre-requisites¶

RAM - Minimum 16GB
HARD DISK - Minimum 500GB
Linux OS installed and running
Nested Virtualization enabled, which can be checked by,

$ cat /sys/module/kvm_intel/parameters/nested
  Y

$ cat /proc/cpuinfo | grep vmx

Note: If Nested virtualization is disabled, enable it by,

For Ubuntu:
$ modeprobe kvm_intel
$ echo Y > /sys/module/kvm_intel/parameters/nested
$ sudo reboot

For RHEL:
$ cat << EOF > /etc/modprobe.d/kvm_intel.conf
  options kvm-intel nested=1
  options kvm-intel enable_shadow_vmcs=1
  options kvm-intel enable_apicv=1
  options kvm-intel ept=1
  EOF
$ cat << EOF > /etc/sysctl.d/98-rp-filter.conf
  net.ipv4.conf.default.rp_filter = 0
  net.ipv4.conf.all.rp_filter = 0
  EOF
$ sudo reboot

2.5. Environment Setup¶

2.5.1. 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.

Acquire::http::proxy "http://<username>:<password>@<proxy>:<port>/";
Acquire::https::proxy "https://<username>:<password>@<proxy>:<port>/";
Acquire::ftp::proxy "ftp://<username>:<password>@<proxy>:<port>/";
Acquire::socks::proxy "socks://<username>:<password>@<proxy>:<port>/";

For CentOS., 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

2.5.2. Network Time Protocol (NTP) setup and configuration¶

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:

server 127.127.1.0
fudge 127.127.1.0 stratum 10

Restart the ntp server to apply the changes

$ sudo service ntp restart

2.6. Scenario Testing¶

There are three ways of performing scenario testing,

1 Fuel
2 OPNFV-Playground
3 Jenkins Project

2.6.1. Fuel¶

1 Clone the fuel repo :

$ git clone https://gerrit.opnfv.org/gerrit/fuel.git

2 Checkout to the specific version of the branch to deploy by:

The default branch is master, to use a stable release-version use the below.,

3 Building the Fuel iso :

$ cd ~/fuel/ci/
$ ./build.sh -h

Provide the necessary options that are required to build an iso. Create a customized iso as per the deployment needs.

$ cd ~/fuel/build/
$ make

(OR) Other way is to download the latest stable fuel iso from here.

http://artifacts.opnfv.org/fuel.html

4 Creating a new deployment scenario

(i). Naming the scenario file

Include the new deployment scenario yaml file in ~/fuel/deploy/scenario/. The file name should adhere to the following format:

<ha | no-ha>_<SDN Controller>_<feature-1>_..._<feature-n>.yaml

(ii). Meta data

The deployment configuration file should contain configuration metadata as stated below:

deployment-scenario-metadata:
        title:
        version:
        created:

(iii). “stack-extentions” Module

To include fuel plugins in the deployment configuration file, use the “stack-extentions” key:

Example:
        stack-extensions:
           - module: fuel-plugin-collectd-ceilometer
             module-config-name: fuel-barometer
             module-config-version: 1.0.0
             module-config-override:
             #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-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.

Example:
dea-override-config:
       environment:
           mode: ha
           net_segment_type: tun
       nodes:
       - id: 1
          interfaces: interfaces_1
          role: mongo,controller,opendaylight
       - id: 2
         interfaces: interfaces_1
         role: mongo,controller
       - id: 3
          interfaces: interfaces_1
          role: mongo,controller
       - id: 4
          interfaces: interfaces_1
          role: ceph-osd,compute
       - id: 5
          interfaces: interfaces_1
          role: ceph-osd,compute
settings:
    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).
                      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.
                      label: Ceph RBD for images (Glance)
                      restrictions:
                      - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
                      type: checkbox
                      value: true
                      weight: 30

Under the “dea-override-config” should provide atleast {environment:{mode:’value},{net_segment_type:’value’} and {nodes:1,2,...} and can also enable additional stack features such ceph,heat which overrides corresponding keys in the dea_base.yaml and dea_pod_override.yaml.

(v). “dha-override-config” Module

In order to configure the pod dha definition, use the “dha-override-config” key. 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 short scenario names should follow the scheme below:

       [os]-[controller]-[feature]-[mode]-[option]

[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.

[controller]: mandatory
example values: nosdn, ocl, odl, onos

[mode]: mandatory
possible values: ha, noha

[option]: optional

Used for the scenarios those do not fit into naming scheme. Optional field in the short scenario name should not be included if there is no optional scenario.

Example:
    1. os-nosdn-kvm-noha
    2. os-nosdn-kvm_ovs_dpdk_bar-ha

Example of how short scenario names are mapped to configuration yaml files:

os-nosdn-kvm_ovs_dpdk-ha:
    configfile: ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml

Note:

( - ) used for separator of fields. [os-nosdn-kvm_ovs_dpdk-ha]
( _ ) used to separate the values belong to the same field. [os-nosdn-kvm_ovs_bar-ha].

5 Deploying the scenario

Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario:

$ 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

where,

-b is used to specify the configuration directory

-f is used to re-deploy on the existing deployment

-i is used to specify the image downloaded from artifacts.

-l is used to specify the lab name

-p is used to specify POD name

-s is used to specify the scenario file

Note:

Check $ sudo ./deploy.sh -h for further information.

2.6.2. OPNFV-Playground¶

Install OPNFV-playground (the tool chain to deploy/test CI scenarios in fuel@opnfv, ):

$ cd ~
$ 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

./ci_pipeline.sh --help  ##to learn more options.

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.

Check paramiko package version by following below steps in your system:

$ 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.

>>> import paramiko
>>> print paramiko.__version__
>>> exit()

You will get the current paramiko package version, if it is 2.x.x, uninstall this version by

$  sudo pip uninstall paramiko

Ubuntu 14.04 LTS has python-paramiko package (1.10.0), install it by

$ sudo apt-get install python-paramiko

Verify it by following:

$ python
>>> import paramiko
>>> print paramiko.__version__
>>> exit()

2 Clone the fuel@opnfv

Check out the specific version of specific branch of fuel@opnfv

$ cd ~
$ git clone https://gerrit.opnfv.org/gerrit/fuel.git
$ cd fuel
By default it will be master branch, in-order to deploy on the Colorado/Danube branch, do:
$ git checkout stable/Danube

3 Creating the scenario

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

$ cd ~/OPNFV-Playground/ci_fuel_opnfv/

For os-nosdn-kvm_ovs_dpdk-ha :

$ ./ci_pipeline.sh -r ~/fuel -i /root/fuel.iso -B -n intel-sc -s os-nosdn-kvm_ovs_dpdk-ha

For os-nosdn-kvm_ovs_dpdk_bar-ha:

$ ./ci_pipeline.sh -r ~/fuel -i /root/fuel.iso -B -n intel-sc -s os-nosdn-kvm_ovs_dpdk_bar-ha

The “ci_pipeline.sh” first clones the local fuel repo, then deploys the os-nosdn-kvm_ovs_dpdk-ha/os-nosdn-kvm_ovs_dpdk_bar-ha scenario from the given ISO, and run Functest and Yarstick test. The log of the deployment/test (ci.log) can be found in ~/OPNFV-Playground/ci_fuel_opnfv/artifact/master/YYYY-MM-DD—HH.mm, where YYYY-MM-DD—HH.mm is the date/time you start the “ci_pipeline.sh”.

Note:

Check $ ./ci_pipeline.sh -h for further information.

2.6.3. 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:

“fuel-os-nosdn-kvm_ovs_dpdk-ha-baremetal-daily-master” (os-nosdn-kvm_ovs_dpdk-ha)

“fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master” (os-nosdn-kvm_ovs_dpdk_bar-ha)

NOHA scenarios:

“fuel-os-nosdn-kvm_ovs_dpdk-noha-virtual-daily-master” (os-nosdn-kvm_ovs_dpdk-noha)

“fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-virtual-daily-master” (os-nosdn-kvm_ovs_dpdk_bar-noha)

os-nosdn-kvm_nfv_ovs_dpdk-noha Overview and Description¶

1. os-nosdn-kvm_nfv_ovs_dpdk-noha Description¶

1.1. Introduction¶

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.

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.

1.2. Scenario Components and Composition¶

This scenario deploys the No High Availability OPNFV Cloud based on the configurations provided in no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml. This yaml file contains following configurations and is passed as an argument to deploy.py script

scenario.yaml: This configuration file defines translation between a short deployment scenario name(os-nosdn-kvm_ovs_dpdk-noha) and an actual deployment scenario configuration file(no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml)
deployment-scenario-metadata: Contains the configuration metadata like title,version,created,comment.

deployment-scenario-metadata:
   title: NFV KVM and OVS-DPDK NOHA deployment
   version: 0.0.1
   created: Dec 20 2016
   comment: NFV KVM and OVS-DPDK

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-noha scenario currently uses KVM-1.0.0 plugin.

stack-extensions:
   - module: fuel-plugin-kvm
     module-config-name: fuel-nfvkvm
     module-config-version: 1.0.0
     module-config-override:
       # Module config overrides

dea-override-config: Used to configure the NO-HA mode,network segmentation types and role to node assignments.These configurations overrides corresponding keys in the dea_base.yaml and dea_pod_override.yaml. These keys are used to deploy multiple nodes(1 controller,3 computes) as mention below.
- Node 1:
  - This node has MongoDB and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Uses VLAN as an interface
- Node 2:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 3:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 4:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
The below is the dea-override-config of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.

dea-override-config:
  fuel:
    FEATURE_GROUPS:
    - experimental
  environment:
    net_segment_type: vlan
  nodes:
  - id: 1
    interfaces: interfaces_vlan
    role: mongo,controller
  - id: 2
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 3
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 4
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1

  attributes_1:
    hugepages:
      dpdk:
        value: 1024
      nova:
        value:
          '2048': 1024

  network:
    networking_parameters:
      segmentation_type: vlan
    networks:
    - cidr: null
      gateway: null
      ip_ranges: []
      meta:
        configurable: false
        map_priority: 2
        name: private
        neutron_vlan_range: true
        notation: null
        render_addr_mask: null
        render_type: null
        seg_type: vlan
        use_gateway: false
        vlan_start: null
      name: private
      vlan_start: null

  settings:
    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).
          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.
          label: Ceph RBD for images (Glance)
          restrictions:
          - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
          type: checkbox
          value: true
          weight: 30

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 no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml has no dha-config changes i.e., default configuration is used.
os-nosdn-kvm_ovs_dpdk-noha scenario is successful when all the 4 Nodes are accessible, up and running.

Note:

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 are only configured for compute nodes
This results in faster communication and data transfer among the compute nodes

1.3. Scenario Usage Overview¶

The high availability feature is disabled and deploymet is done by deploy.py with noha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml as an argument.
Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware Environment:

Command to deploy the os-nosdn-kvm_ovs_dpdk-noha scenario:

$ 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

where,

-b is used to specify the configuration directory

-i is used to specify the image downloaded from artifacts.

Note:

Check $ sudo ./deploy.sh -h for further information.

os-nosdn-kvm_ovs_dpdk-noha scenario can be executed from the jenkins project “fuel-os-nosdn-kvm_ovs_dpdk-noha-baremetal-daily-master”
This scenario provides the No High Availability feature by deploying 1 controller,3 compute nodes and checking if all the 4 nodes are accessible(IP,up & running).
Test Scenario is passed if deployment is successful and all 4 nodes have accessibility (IP , up & running).

1.4. Known Limitations, Issues and Workarounds¶

Test scenario os-nosdn-kvm_ovs_dpdk-noha result is not stable.

1.5. References¶

For more information on the OPNFV Danube release, please visit http://www.opnfv.org/Danube

os-nosdn-kvm_nfv_ovs_dpdk-ha Overview and Description¶

1. os-nosdn-kvm_nfv_ovs_dpdk-ha Description¶

1.1. Introduction¶

The purpose of os-nosdn-kvm_ovs_dpdk-ha scenario testing is to test the 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. 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.

1.2. Scenario Components and Composition¶

This scenario deploys the High Availability OPNFV Cloud based on the configurations provided in ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml. This yaml file contains following configurations and is passed as an argument to deploy.py script

scenario.yaml: This configuration file defines translation between a short deployment scenario name(os-nosdn-kvm_ovs_dpdk-ha) and an actual deployment scenario configuration file(ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml)
deployment-scenario-metadata: Contains the configuration metadata like title,version,created,comment.

deployment-scenario-metadata:
   title: NFV KVM and OVS-DPDK HA deployment
   version: 0.0.1
   created: Dec 20 2016
   comment: NFV KVM and OVS-DPDK

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-ha scenario currently uses KVM-1.0.0 plugin.

stack-extensions:
   - module: fuel-plugin-kvm
     module-config-name: fuel-nfvkvm
     module-config-version: 1.0.0
     module-config-override:
       # Module config overrides

dea-override-config: Used to configure the HA mode,network segmentation types and role to node assignments.These configurations overrides corresponding keys in the dea_base.yaml and dea_pod_override.yaml. These keys are used to deploy multiple nodes(3 controllers,2 computes) as mention below.
- Node 1:
  - This node has MongoDB and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Uses VLAN as an interface
- Node 2:
  - This node has Ceph-osd and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Ceph is a massively scalable, open source, distributed storage system
  - Uses VLAN as an interface
- Node 3:
  - This node has Controller role in order to achieve high availability.
  - Uses VLAN as an interface
- Node 4:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 5:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
The below is the dea-override-config of the ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.

dea-override-config:
  fuel:
    FEATURE_GROUPS:
    - experimental
  nodes:
  - id: 1
    interfaces: interfaces_1
    role: controller
  - id: 2
    interfaces: interfaces_1
    role: mongo,controller
  - id: 3
    interfaces: interfaces_1
    role: ceph-osd,controller
  - id: 4
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 5
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1

  attributes_1:
    hugepages:
      dpdk:
        value: 1024
      nova:
        value:
          '2048': 1024

  settings:
    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).
          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.
          label: Ceph RBD for images (Glance)
          restrictions:
          - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
          type: checkbox
          value: true
          weight: 30

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 below is the dha-override-config of the ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.

dha-override-config:
  nodes:
  - id: 1
    libvirtName: controller1
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 2
    libvirtName: controller2
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 3
    libvirtName: controller3
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 4
    libvirtName: compute1
    libvirtTemplate: templates/virtual_environment/vms/compute.xml
  - id: 5
    libvirtName: compute2
    libvirtTemplate: templates/virtual_environment/vms/compute.xml
  - id: 6
    libvirtName: fuel-master
    libvirtTemplate: templates/virtual_environment/vms/fuel.xml
    isFuel: yes
    username: root
    password: r00tme

os-nosdn-kvm_ovs_dpdk-ha scenario is successful when all the 5 Nodes are accessible, up and running.

Note:

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 are only configured for compute nodes
This results in faster communication and data transfer among the compute nodes

1.3. Scenario Usage Overview¶

The high availability feature can be acheived by executing deploy.py with ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml as an argument.
Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware Environment:

Command to deploy the os-nosdn-kvm_ovs_dpdk-ha scenario:

$ 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

where,

-b is used to specify the configuration directory

-i is used to specify the image downloaded from artifacts.

Note:

Check $ sudo ./deploy.sh -h for further information.

os-nosdn-kvm_ovs_dpdk-ha scenario can be executed from the jenkins project “fuel-os-nosdn-kvm_ovs_dpdk-ha-baremetal-daily-master”
This scenario provides the High Availability feature by deploying 3 controller,2 compute nodes and checking if all the 5 nodes are accessible(IP,up & running).
Test Scenario is passed if deployment is successful and all 5 nodes have accessibility (IP , up & running).

1.4. Known Limitations, Issues and Workarounds¶

Test scenario os-nosdn-kvm_ovs_dpdk-ha result is not stable.

1.5. References¶

For more information on the OPNFV Danube release, please visit http://www.opnfv.org/Danube

os-nosdn-kvm_nfv_ovs_dpdk_bar-noha Overview and Description¶

1. os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description¶

1.1. Introduction¶

The purpose of os-nosdn-kvm_ovs_dpdk_bar-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.

OPNFV Barometer packages is used for traffic,performance and platform monitoring. 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.

1.2. Scenario Components and Composition¶

This scenario deploys the No High Availability OPNFV Cloud based on the configurations provided in no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml. This yaml file contains following configurations and is passed as an argument to deploy.py script

scenario.yaml: This configuration file defines translation between a short deployment scenario name(os-nosdn-kvm_ovs_dpdk_bar-noha) and an actual deployment scenario configuration file(no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml)
deployment-scenario-metadata: Contains the configuration metadata like title,version,created,comment.

deployment-scenario-metadata:
   title: NFV KVM and OVS-DPDK HA deployment
   version: 0.0.1
   created: Dec 20 2016
   comment: NFV KVM and OVS-DPDK

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.

stack-extensions:
   - module: fuel-plugin-kvm
     module-config-name: fuel-nfvkvm
     module-config-version: 1.0.0
     module-config-override:
      # Module config overrides
   - module: fuel-plugin-collectd-ceilometer
     module-config-name: fuel-barometer
     module-config-version: 1.0.0
     module-config-override:
       # Module config overrides

dea-override-config: Used to configure the HA mode,network segmentation types and role to node assignments.These configurations overrides corresponding keys in the dea_base.yaml and dea_pod_override.yaml. These keys are used to deploy multiple nodes(1 controller,3 computes) as mention below.
- Node 1:
  - This node has MongoDB and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Uses VLAN as an interface
- Node 2:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 3:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 4:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
The below is the dea-override-config of the no-ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.

dea-override-config:
  fuel:
    FEATURE_GROUPS:
    - experimental
  environment:
    net_segment_type: vlan
  nodes:
  - id: 1
    interfaces: interfaces_vlan
    role: mongo,controller
  - id: 2
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 3
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 4
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1

  attributes_1:
    hugepages:
      dpdk:
        value: 1024
      nova:
        value:
          '2048': 1024

  network:
    networking_parameters:
      segmentation_type: vlan
    networks:
    - cidr: null
      gateway: null
      ip_ranges: []
      meta:
        configurable: false
        map_priority: 2
        name: private
        neutron_vlan_range: true
        notation: null
        render_addr_mask: null
        render_type: null
        seg_type: vlan
        use_gateway: false
        vlan_start: null
      name: private
      vlan_start: null

  settings:
    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).
          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.
          label: Ceph RBD for images (Glance)
          restrictions:
          - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
          type: checkbox
          value: true
          weight: 30

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.
os-nosdn-kvm_ovs_dpdk_bar-noha scenario is successful when all the 4 Nodes are accessible, up and running.

Note:

In os-nosdn-kvm_ovs_dpdk_bar-noha scenario, OVS is installed on the compute nodes with DPDK configured
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 are only configured for compute nodes
This results in faster communication and data transfer among the compute nodes

1.3. Scenario Usage Overview¶

The high availability feature is disabled and deploymet is done by deploy.py with noha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml as an argument.
Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware Environment:

Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-noha scenario:

$ 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

where,

-b is used to specify the configuration directory

-i is used to specify the image downloaded from artifacts.

Note:

Check $ sudo ./deploy.sh -h for further information.

os-nosdn-kvm_ovs_dpdk_bar-noha scenario can be executed from the jenkins project “fuel-os-nosdn-kvm_ovs_dpdk_bar-noha-baremetal-daily-master”
This scenario provides the No High Availability feature by deploying 1 controller,3 compute nodes and checking if all the 4 nodes are accessible(IP,up & running).
Test Scenario is passed if deployment is successful and all 4 nodes have accessibility (IP , up & running).

1.4. Known Limitations, Issues and Workarounds¶

Test scenario os-nosdn-kvm_ovs_dpdk_bar-noha result is not stable.

1.5. References¶

For more information on the OPNFV Danube release, please visit http://www.opnfv.org/Danube

os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Overview and Description¶

1. os-nosdn-kvm_nfv_ovs_dpdk_bar-ha Description¶

1.1. Introduction¶

The purpose of os-nosdn-kvm_ovs_dpdk_bar-ha scenario testing is to test the 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. High Availability feature is achieved by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes.

OPNFV Barometer packages is used for traffic,performance and platform monitoring. 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.

1.2. Scenario Components and Composition¶

This scenario deploys the High Availability OPNFV Cloud based on the configurations provided in ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml. This yaml file contains following configurations and is passed as an argument to deploy.py script

scenario.yaml: This configuration file defines translation between a short deployment scenario name(os-nosdn-kvm_ovs_dpdk_bar-ha) and an actual deployment scenario configuration file(ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml)
deployment-scenario-metadata: Contains the configuration metadata like title,version,created,comment.

deployment-scenario-metadata:
   title: NFV KVM and OVS-DPDK HA deployment
   version: 0.0.1
   created: Dec 20 2016
   comment: NFV KVM and OVS-DPDK

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-ha scenario currently uses KVM-1.0.0 plugin and barometer plugin.

stack-extensions:
   - module: fuel-plugin-kvm
     module-config-name: fuel-nfvkvm
     module-config-version: 1.0.0
     module-config-override:
      # Module config overrides
   - module: fuel-plugin-collectd-ceilometer
     module-config-name: fuel-barometer
     module-config-version: 1.0.0
     module-config-override:
       # Module config overrides

dea-override-config: Used to configure the HA mode,network segmentation types and role to node assignments.These configurations overrides corresponding keys in the dea_base.yaml and dea_pod_override.yaml. These keys are used to deploy multiple nodes(3 controllers,2 computes) as mention below.
- Node 1:
  - This node has MongoDB and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Uses VLAN as an interface
- Node 2:
  - This node has Ceph-osd and Controller roles
  - The controller node runs the Identity service, Image Service, management portions of Compute and Networking, Networking plug-in and the dashboard
  - Ceph is a massively scalable, open source, distributed storage system
  - Uses VLAN as an interface
- Node 3:
  - This node has Controller role in order to achieve high availability.
  - Uses VLAN as an interface
- Node 4:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
- Node 5:
  - This node has compute and Ceph-osd roles
  - Ceph is a massively scalable, open source, distributed storage system
  - By default, Compute uses KVM as the hypervisor
  - Uses DPDK as an interface
The below is the dea-override-config of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.

dea-override-config:
  fuel:
    FEATURE_GROUPS:
    - experimental
  nodes:
  - id: 1
    interfaces: interfaces_1
    role: controller
  - id: 2
    interfaces: interfaces_1
    role: mongo,controller
  - id: 3
    interfaces: interfaces_1
    role: ceph-osd,controller
  - id: 4
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1
  - id: 5
    interfaces: interfaces_dpdk
    role: ceph-osd,compute
    attributes: attributes_1

  attributes_1:
    hugepages:
      dpdk:
        value: 1024
      nova:
        value:
          '2048': 1024

  settings:
    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).
          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.
          label: Ceph RBD for images (Glance)
          restrictions:
          - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
          type: checkbox
          value: true
          weight: 30

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 below is the dha-override-config of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.

dha-override-config:
  nodes:
  - id: 1
    libvirtName: controller1
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 2
    libvirtName: controller2
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 3
    libvirtName: controller3
    libvirtTemplate: templates/virtual_environment/vms/controller.xml
  - id: 4
    libvirtName: compute1
    libvirtTemplate: templates/virtual_environment/vms/compute.xml
  - id: 5
    libvirtName: compute2
    libvirtTemplate: templates/virtual_environment/vms/compute.xml
  - id: 6
    libvirtName: fuel-master
    libvirtTemplate: templates/virtual_environment/vms/fuel.xml
    isFuel: yes
    username: root
    password: r00tme

os-nosdn-kvm_ovs_dpdk_bar-ha scenario is successful when all the 5 Nodes are accessible, up and running.

Note:

In os-nosdn-kvm_ovs_dpdk_bar-ha scenario, OVS is installed on the compute nodes with DPDK configured
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 are only configured for compute nodes
This results in faster communication and data transfer among the compute nodes

1.3. Scenario Usage Overview¶

The high availability feature can be acheived by executing deploy.py with ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml as an argument.
Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware Environment:

Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-ha scenario:

$ 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

where,

-b is used to specify the configuration directory

-i is used to specify the image downloaded from artifacts.

Note:

Check $ sudo ./deploy.sh -h for further information.

os-nosdn-kvm_ovs_dpdk_bar-ha scenario can be executed from the jenkins project “fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master”
This scenario provides the High Availability feature by deploying 3 controller,2 compute nodes and checking if all the 5 nodes are accessible(IP,up & running).
Test Scenario is passed if deployment is successful and all 5 nodes have accessibility (IP , up & running).

1.4. Known Limitations, Issues and Workarounds¶

Test scenario os-nosdn-kvm_ovs_dpdk_bar-ha result is not stable.

1.5. References¶

For more information on the OPNFV Danube release, please visit http://www.opnfv.org/Danube