1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
9 .. In this section explain the purpose of the scenario and the
10 types of capabilities provided
12 The purpose of os-nosdn-kvm-ha scenario testing is to test the
13 High Availability deployment and configuration of OPNFV software suite
14 with OpenStack and without SDN software. This OPNFV software suite
15 includes OPNFV KVM4NFV latest software packages for Linux Kernel and
16 QEMU patches for achieving low latency. High Availability feature is achieved
17 by deploying OpenStack multi-node setup with 3 controllers and 2 computes nodes
19 KVM4NFV packages will be installed on compute nodes as part of deployment.
20 This scenario testcase deployment is happening on multi-node by using
23 Scenario Components and Composition
24 ===================================
25 .. In this section describe the unique components that make up the scenario,
26 .. what each component provides and why it has been included in order
27 .. to communicate to the user the capabilities available in this scenario.
29 This scenario deploys the High Availability OPNFV Cloud based on the
30 configurations provided in ha_nfv-kvm_heat_ceilometer_scenario.yaml.
31 This yaml file contains following configurations and is passed as an
32 argument to deploy.py script
34 * scenario.yaml:This configuration file defines translation between a
35 short deployment scenario name(os-nosdn-kvm-ha) and an actual deployment
36 scenario configuration file(ha_nfv-kvm_heat_ceilometer_scenario.yaml)
38 * deployment-scenario-metadata:Contains the configuration metadata like
39 title,version,created,comment.
41 * stack-extensions:Stack extentions are opnfv added value features in form
42 of a fuel-plugin.Plugins listed in stack extensions are enabled and
45 * dea-override-config: Used to configure the HA mode,network segmentation
46 types and role to node assignments.These configurations overrides
47 corresponding keys in the dea_base.yaml and dea_pod_override.yaml.
48 These keys are used to deploy multiple nodes(3 controllers,2 computes)
51 * **Node 1**: This node has MongoDB and Controller roles. The controller
52 node runs the Identity service, Image Service, management portions of
53 Compute and Networking, Networking plug-in and the dashboard. The
54 Telemetry service which was designed to support billing systems for
55 OpenStack cloud resources uses a NoSQL database to store information.
56 The database typically runs on the controller node.
58 * **Node 2**: This node has Controller and Ceph-osd roles. Ceph is a
59 massively scalable, open source, distributed storage system. It is
60 comprised of an object store, block store and a POSIX-compliant distributed
61 file system. Enabling Ceph, configures Nova to store ephemeral volumes in
62 RBD, configures Glance to use the Ceph RBD backend to store images,
63 configures Cinder to store volumes in Ceph RBD images and configures the
64 default number of object replicas in Ceph.
66 * **Node 3**: This node has Controller role in order to achieve high
69 * **Node 4**: This node has Compute role. The compute node runs the
70 hypervisor portion of Compute that operates tenant virtual machines
71 or instances. By default, Compute uses KVM as the hypervisor.
73 * **Node 5**: This node has compute role.
75 * dha-override-config:Provides information about the VM definition and
76 Network config for virtual deployment.These configurations overrides
77 the pod dha definition and points to the controller,compute and
78 fuel definition files.
80 * os-nosdn-kvm-ha scenario is successful when all the 5 Nodes are accessible,
83 Scenario Usage Overview
84 =======================
85 .. Provide a brief overview on how to use the scenario and the features available to the
86 .. user. This should be an "introduction" to the userguide document, and explicitly link to it,
87 .. where the specifics of the features are covered including examples and API's
89 * The high availability feature can be acheived by executing deploy.py with
90 ha_nfv-kvm_heat_ceilometer_scenario.yaml as an argument.
91 * Install Fuel Master and deploy OPNFV Cloud from scratch on Hardware
96 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
98 * Install Fuel Master and deploy OPNFV Cloud from scratch on Virtual
103 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
105 * os-nosdn-kvm-ha scenario can be executed from the jenkins project
106 "fuel-os-nosdn-kvm-ha-baremetal-daily-master"
107 * This scenario provides the High Availability feature by deploying
108 3 controller,2 compute nodes and checking if all the 5 nodes
109 are accessible(IP,up & running).
110 * Test Scenario is passed if deployment is successful and all 5 nodes have
111 accessibility (IP , up & running).
112 * Observed that scenario is not running any testcase on top of deployment.
114 Known Limitations, Issues and Workarounds
115 =========================================
116 .. Explain any known limitations here.
118 * Test scenario os-nosdn-kvm-ha result is not stable. After node reboot
119 triggered by kvm plugin, sometimes puppet agent (mcollective) is not
120 responding with in the given time.
125 For more information on the OPNFV Danube release, please visit
126 http://www.opnfv.org/danube