1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
5 ============================================
6 os-nosdn-kvm_ovs_dpdk_bar-ha Description
7 ============================================
12 .. In this section explain the purpose of the scenario and the
13 types of capabilities provided
15 The purpose of os-nosdn-kvm_ovs_dpdk_bar-ha scenario testing is to test the
16 High Availability deployment and configuration of OPNFV software suite
17 with OpenStack and without SDN software. This OPNFV software suite
18 includes OPNFV KVM4NFV latest software packages for Linux Kernel and
19 QEMU patches for achieving low latency. High Availability feature is achieved
20 by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes.
22 OPNFV Barometer packages is used for traffic,performance and platform monitoring.
23 KVM4NFV packages will be installed on compute nodes as part of deployment.
24 This scenario testcase deployment is happening on multi-node by using OPNFV Fuel deployer.
26 Scenario Components and Composition
27 -----------------------------------
28 .. In this section describe the unique components that make up the scenario,
29 .. what each component provides and why it has been included in order
30 .. to communicate to the user the capabilities available in this scenario.
32 This scenario deploys the High Availability OPNFV Cloud based on the
33 configurations provided in ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml.
34 This yaml file contains following configurations and is passed as an
35 argument to deploy.py script
37 * ``scenario.yaml:`` This configuration file defines translation between a
38 short deployment scenario name(os-nosdn-kvm_ovs_dpdk_bar-ha) and an actual deployment
39 scenario configuration file(ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml)
41 * ``deployment-scenario-metadata:`` Contains the configuration metadata like
42 title,version,created,comment.
46 deployment-scenario-metadata:
47 title: NFV KVM and OVS-DPDK HA deployment
50 comment: NFV KVM and OVS-DPDK
52 * ``stack-extensions:`` Stack extentions are opnfv added value features in form
53 of a fuel-plugin.Plugins listed in stack extensions are enabled and
54 configured. os-nosdn-kvm_ovs_dpdk_bar-ha scenario currently uses KVM-1.0.0 plugin and barometer plugin.
59 - module: fuel-plugin-kvm
60 module-config-name: fuel-nfvkvm
61 module-config-version: 1.0.0
62 module-config-override:
63 # Module config overrides
64 - module: fuel-plugin-collectd-ceilometer
65 module-config-name: fuel-barometer
66 module-config-version: 1.0.0
67 module-config-override:
68 # Module config overrides
71 * ``dea-override-config:`` Used to configure the HA mode,network segmentation
72 types and role to node assignments.These configurations overrides
73 corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
74 These keys are used to deploy multiple nodes(``3 controllers,2 computes``)
78 - This node has MongoDB and Controller roles
79 - The controller node runs the Identity service, Image Service, management portions of
80 Compute and Networking, Networking plug-in and the dashboard
81 - Uses VLAN as an interface
84 - This node has Ceph-osd and Controller roles
85 - The controller node runs the Identity service, Image Service, management portions of
86 Compute and Networking, Networking plug-in and the dashboard
87 - Ceph is a massively scalable, open source, distributed storage system
88 - Uses VLAN as an interface
91 - This node has Controller role in order to achieve high availability.
92 - Uses VLAN as an interface
95 - This node has compute and Ceph-osd roles
96 - Ceph is a massively scalable, open source, distributed storage system
97 - By default, Compute uses KVM as the hypervisor
98 - Uses DPDK as an interface
101 - This node has compute and Ceph-osd roles
102 - Ceph is a massively scalable, open source, distributed storage system
103 - By default, Compute uses KVM as the hypervisor
104 - Uses DPDK as an interface
106 The below is the ``dea-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.
116 interfaces: interfaces_1
119 interfaces: interfaces_1
120 role: mongo,controller
122 interfaces: interfaces_1
123 role: ceph-osd,controller
125 interfaces: interfaces_dpdk
126 role: ceph-osd,compute
127 attributes: attributes_1
129 interfaces: interfaces_dpdk
130 role: ceph-osd,compute
131 attributes: attributes_1
145 description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph
146 is enabled for volumes and images, too. Enables live migration of all types of Ceph
147 backed VMs (without this option, live migration will only work with VMs launched from
149 label: Ceph RBD for ephemeral volumes (Nova)
154 description: Configures Glance to use the Ceph RBD backend to store images. If enabled,
155 this option will prevent Swift from installing.
156 label: Ceph RBD for images (Glance)
158 - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
163 * ``dha-override-config:`` Provides information about the VM definition and
164 Network config for virtual deployment.These configurations overrides
165 the pod dha definition and points to the controller,compute and
166 fuel definition files.
168 The below is the ``dha-override-config`` of the ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml file.
175 libvirtName: controller1
176 libvirtTemplate: templates/virtual_environment/vms/controller.xml
178 libvirtName: controller2
179 libvirtTemplate: templates/virtual_environment/vms/controller.xml
181 libvirtName: controller3
182 libvirtTemplate: templates/virtual_environment/vms/controller.xml
184 libvirtName: compute1
185 libvirtTemplate: templates/virtual_environment/vms/compute.xml
187 libvirtName: compute2
188 libvirtTemplate: templates/virtual_environment/vms/compute.xml
190 libvirtName: fuel-master
191 libvirtTemplate: templates/virtual_environment/vms/fuel.xml
197 * os-nosdn-kvm_ovs_dpdk_bar-ha scenario is successful when all the 5 Nodes are accessible, up and running.
202 * In os-nosdn-kvm_ovs_dpdk_bar-ha scenario, OVS is installed on the compute nodes with DPDK configured
204 * Baraometer plugin is also implemented along with KVM plugin
206 * Hugepages for DPDK are configured in the attributes_1 section of the
207 no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
209 * Hugepages are only configured for compute nodes
211 * This results in faster communication and data transfer among the compute nodes
214 Scenario Usage Overview
215 ------------------------
216 .. Provide a brief overview on how to use the scenario and the features available to the
217 .. user. This should be an "introduction" to the userguide document, and explicitly link to it,
218 .. where the specifics of the features are covered including examples and API's
220 * The high availability feature can be acheived by executing deploy.py with
221 ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml as an argument.
222 * Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
226 Command to deploy the os-nosdn-kvm_ovs_dpdk_bar-ha scenario:
231 $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \
232 -s ha_nfv-kvm_nfv-ovs-dpdk-bar_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
235 -b is used to specify the configuration directory
237 -i is used to specify the image downloaded from artifacts.
243 Check $ sudo ./deploy.sh -h for further information.
245 * os-nosdn-kvm_ovs_dpdk_bar-ha scenario can be executed from the jenkins project
246 "fuel-os-nosdn-kvm_ovs_dpdk_bar-ha-baremetal-daily-master"
247 * This scenario provides the High Availability feature by deploying
248 3 controller,2 compute nodes and checking if all the 5 nodes
249 are accessible(IP,up & running).
250 * Test Scenario is passed if deployment is successful and all 5 nodes have
251 accessibility (IP , up & running).
253 Known Limitations, Issues and Workarounds
254 -----------------------------------------
255 .. Explain any known limitations here.
257 * Test scenario os-nosdn-kvm_ovs_dpdk_bar-ha result is not stable.
262 For more information on the OPNFV Euphrates release, please visit
263 http://www.opnfv.org/Euphrates