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-noha 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-noha scenario testing is to test the No
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. When deployed using Fuel, No High
20 Availability feature is achieved by deploying OpenStack multi-node setup with
21 1 controller and 3 computes nodes and using Apex the setup is with 1 controller
24 KVM4NFV packages will be installed on compute nodes as part of deployment.
25 This scenario testcase deployment is happening on multi-node by using OPNFV Fuel
29 **Using Fuel Installer**
31 Scenario Components and Composition
32 ------------------------------------
33 .. In this section describe the unique components that make up the scenario,
34 .. what each component provides and why it has been included in order
35 .. to communicate to the user the capabilities available in this scenario.
37 This scenario deploys the No High Availability OPNFV Cloud based on the
38 configurations provided in no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml.
39 This yaml file contains following configurations and is passed as an
40 argument to deploy.py script
42 * ``scenario.yaml:`` This configuration file defines translation between a
43 short deployment scenario name(os-nosdn-kvm_ovs_dpdk-noha) and an actual deployment
44 scenario configuration file(no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml)
46 * ``deployment-scenario-metadata:`` Contains the configuration metadata like
47 title,version,created,comment.
51 deployment-scenario-metadata:
52 title: NFV KVM and OVS-DPDK NOHA deployment
55 comment: NFV KVM and OVS-DPDK
57 * ``stack-extensions:`` Stack extentions are opnfv added value features in form
58 of a fuel-plugin.Plugins listed in stack extensions are enabled and
59 configured. os-nosdn-kvm_ovs_dpdk-noha scenario currently uses KVM-1.0.0 plugin.
64 - module: fuel-plugin-kvm
65 module-config-name: fuel-nfvkvm
66 module-config-version: 1.0.0
67 module-config-override:
68 # Module config overrides
70 * ``dea-override-config:`` Used to configure the NO-HA mode,network segmentation
71 types and role to node assignments.These configurations overrides
72 corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
73 These keys are used to deploy multiple nodes(``1 controller,3 computes``)
77 - This node has MongoDB and Controller roles
78 - The controller node runs the Identity service, Image Service, management portions of
79 Compute and Networking, Networking plug-in and the dashboard
80 - Uses VLAN as an interface
83 - This node has compute and Ceph-osd roles
84 - Ceph is a massively scalable, open source, distributed storage system
85 - By default, Compute uses KVM as the hypervisor
86 - Uses DPDK as an interface
89 - This node has compute and Ceph-osd roles
90 - Ceph is a massively scalable, open source, distributed storage system
91 - By default, Compute uses KVM as the hypervisor
92 - Uses DPDK 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
100 The below is the ``dea-override-config`` of the no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml file.
109 net_segment_type: vlan
112 interfaces: interfaces_vlan
113 role: mongo,controller
115 interfaces: interfaces_dpdk
116 role: ceph-osd,compute
117 attributes: attributes_1
119 interfaces: interfaces_dpdk
120 role: ceph-osd,compute
121 attributes: attributes_1
123 interfaces: interfaces_dpdk
124 role: ceph-osd,compute
125 attributes: attributes_1
136 networking_parameters:
137 segmentation_type: vlan
146 neutron_vlan_range: true
148 render_addr_mask: null
160 description: Configures Nova to store ephemeral volumes in RBD. This works best if Ceph
161 is enabled for volumes and images, too. Enables live migration of all types of Ceph
162 backed VMs (without this option, live migration will only work with VMs launched from
164 label: Ceph RBD for ephemeral volumes (Nova)
169 description: Configures Glance to use the Ceph RBD backend to store images. If enabled,
170 this option will prevent Swift from installing.
171 label: Ceph RBD for images (Glance)
173 - settings:storage.images_vcenter.value == true: Only one Glance backend could be selected.
178 * ``dha-override-config:`` Provides information about the VM definition and
179 Network config for virtual deployment.These configurations overrides
180 the pod dha definition and points to the controller,compute and
181 fuel definition files. The no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
182 has no dha-config changes i.e., default configuration is used.
184 * os-nosdn-kvm_ovs_dpdk-noha scenario is successful when all the 4 Nodes are accessible,
191 * In os-nosdn-kvm_ovs_dpdk-noha scenario, OVS is installed on the compute nodes with DPDK configured
193 * Hugepages for DPDK are configured in the attributes_1 section of the
194 no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml
196 * Hugepages are only configured for compute nodes
198 * This results in faster communication and data transfer among the compute nodes
201 Scenario Usage Overview
202 -----------------------
204 .. Provide a brief overview on how to use the scenario and the features available to the
205 .. user. This should be an "introduction" to the userguide document, and explicitly link to it,
206 .. where the specifics of the features are covered including examples and API's
208 * The high availability feature is disabled and deploymet is done by deploy.py with
209 noha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml as an argument.
210 * Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
214 Command to deploy the os-nosdn-kvm_ovs_dpdk-noha scenario:
219 $ sudo ./deploy.sh -f -b file:///tmp/opnfv-fuel/deploy/config -l devel-pipeline -p default \
220 -s no-ha_nfv-kvm_nfv-ovs-dpdk_heat_ceilometer_scenario.yaml -i file:///tmp/opnfv.iso
223 -b is used to specify the configuration directory
225 -i is used to specify the image downloaded from artifacts.
231 Check $ sudo ./deploy.sh -h for further information.
233 * os-nosdn-kvm_ovs_dpdk-noha scenario can be executed from the jenkins project
234 "fuel-os-nosdn-kvm_ovs_dpdk-noha-baremetal-daily-master"
235 * This scenario provides the No High Availability feature by deploying
236 1 controller,3 compute nodes and checking if all the 4 nodes
237 are accessible(IP,up & running).
238 * Test Scenario is passed if deployment is successful and all 4 nodes have
239 accessibility (IP , up & running).
242 **Using Apex Installer**
244 Scenario Components and Composition
245 -----------------------------------
246 .. In this section describe the unique components that make up the scenario,
247 .. what each component provides and why it has been included in order
248 .. to communicate to the user the capabilities available in this scenario.
250 This scenario is composed of common OpenStack services enabled by default,
251 including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and
252 by default, Tacker and Congress services are also enabled. Ceph is used as
253 the backend storage to Cinder on all deployed nodes.
255 The os-nosdn-kvm_ovs_dpdk-noha.yaml file contains following configurations and
256 is passed as an argument to deploy.sh script.
258 * ``global-params:`` Used to define the global parameter and there is only one
259 such parameter exists,i.e, ha_enabled
266 * ``deploy_options:`` Used to define the type of SDN controller, configure the
267 tacker, congress, service functioning chaining support(sfc) for ODL and ONOS,
268 configure ODL with SDNVPN support, which dataplane to use for overcloud
269 tenant networks, whether to run the kvm real time kernel (rt_kvm) in the
270 compute node(s) to reduce the network latencies caused by network function
271 virtualization and whether to install and configure fdio functionality in the
277 sdn_controller: false
285 * ``performance:`` Used to set performance options on specific roles. The valid
286 roles are 'Compute', 'Controller' and 'Storage', and the valid sections are
307 Scenario Usage Overview
308 -----------------------
309 .. Provide a brief overview on how to use the scenario and the features available to the
310 .. user. This should be an "introduction" to the userguide document, and explicitly link to it,
311 .. where the specifics of the features are covered including examples and API's
313 * The high availability feature can be acheived by executing deploy.sh with
314 os-nosdn-kvm_ovs_dpdk-noha.yaml as an argument.
316 * Build the undercloud and overcloud images as mentioned below:
324 * Command to deploy os-nosdn-kvm_ovs_dpdk-noha scenario:
331 ./deploy.sh -v --ping-site <ping_ip-address> --dnslookup-site <dns_ip-address> -n \
332 ~/apex/config/network/intc_network_settings.yaml -d ~/apex/config/deploy/os-nosdn-kvm_ovs_dpdk-noha.yaml
335 -v is used for virtual deployment
336 -n is used for providing the network configuration file
337 -d is used for providing the scenario configuration file
343 For more information on the OPNFV Euphrates release, please visit
344 http://www.opnfv.org/Euphrates