x
/
fuel-plugin-nsxv
Code Issues Proposed changes

Merge "Test Plan for NSXv Plugin v.2.0.0"

This commit is contained in:
Jenkins 2015-12-15 14:49:06 +00:00 committed by Gerrit Code Review
parent 7592c7d490 52fd6923fa
commit ff9d280179
10 changed files with 1172 additions and 1395 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/test/conf.py
View File

@ -51,9 +51,9 @@ copyright = u'2015, Mirantis Inc.'
# built documents.
#
# The short X.Y version.
version = '1.0.0'
version = '2.0.0'
# The full version, including alpha/beta/rc tags.
release = '1.0.0'
release = '2.0.0'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.

7
doc/test/index.rst
View File

@ -8,4 +8,9 @@ Testing documents
:glob:
:maxdepth: 1
source/*
source/nsx-v_test_plan
source/test_suite_failover
source/test_suite_integration
source/test_suite_scale
source/test_suite_smoke
source/test_suite_system

33
doc/test/source/nsx-v_test_plan.rst
View File

@ -1,6 +1,6 @@
==================================
Test Plan for NSXv plugin v.1.1.0
==================================
================================
Test Plan for NSXv plugin v2.0.0
================================
.. contents:: Table of contents
:depth: 3
@ -41,7 +41,7 @@ Following test types should be provided:
* GUI tests
Performance testing will be executed on the scale lab and a custom set of
rally scenarios must be run with NSXv environment. Configuration, enviroment
rally scenarios must be run with NSXv environment. Configuration, environment
and scenarios for performance/scale testing should be determine separately.
Intended Audience
@ -56,7 +56,7 @@ Limitation
Plugin (or its components) has the following limitations:
* VMware NSXv plugin can be enabled only with Neutron tunnel segmentation.
* Enviroment with enabled VMware NSXv plugin can't contains compute nodes.
* Environment with enabled VMware NSXv plugin can't contains compute nodes.
* Only VMware NSX Manager Virtual Appliance 6.1.4 or later is supported.
Product compatibility matrix
@ -70,11 +70,11 @@ Product compatibility matrix
- Version
- Comment
* - MOS
- 7.0 with Kilo
- 8.0
-
* - OpenStack release
- Kilo with Ubuntu 14.04
-
* - Operatin System
- Ubuntu 14.0.4
- Only Ubuntu is supported in MOS 7.0
* - vSphere
- 5.5 and 6.0
-
@ -88,8 +88,8 @@ Evaluation Mission and Test Motivation
Project main goal is to build a MOS plugin that integrates a Neutron VMware
NSX plugin. This will allow to use Neutron for networking in vmware-related
environments. The plugin must be compatible with the version 7.0 of Mirantis
OpenStack and should be tested with sofware/hardware described in
environments. The plugin must be compatible with the version 8.0 of Mirantis
OpenStack and should be tested with software/hardware described in
`product compatibility matrix`_.
See the VMware NSX Plugin specification for more details.
@ -122,7 +122,7 @@ QA to accept software builds from Development team.
The goal of integration and system testing is to ensure that new or modified
components of Fuel and MOS work effectively with Fuel VMware NSXv plugin
without gaps in dataflow.
without gaps in data flow.
**Regression testing**
@ -205,12 +205,3 @@ Acceptance criteria
* All required documents are delivered
* Release notes including a report on the known errors of that release
**********
Test cases
**********
.. include:: test_suite_smoke.rst
.. include:: test_suite_integration.rst
.. include:: test_suite_system.rst
.. include:: test_suite_destructive.rst
.. include:: test_suite_gui.rst

490
doc/test/source/test_suite_destructive.rst
View File

@ -1,490 +0,0 @@
Destructive
===========
TC-101: Check abilities to bind port on NSXv to VM, disable and enable this port.
----------------------------------------------------------------------------------
**ID**
nsxv_ability_to_bind_port
**Description**
::
Verifies that system could manipulate with port.
**Complexity**
core
**Requre to automate**
Yes
**Steps**
::
Log in to Horizon Dashboard.
Navigate to Project -> Compute -> Instances
Launch instance VM_1 with image TestVM-VMDK and flavor m1.tiny.
Launch instance VM_2 with image TestVM-VMDK and flavor m1.tiny.
Verify that VMs should communicate between each other. Send icmp ping from VM _1 to VM_2 and vice versa.
Disable NSXv_port of VM_1.
Verify that VMs should not communicate between each other. Send icmp ping from VM _2 to VM_1 and vice versa.
Enable NSXv_port of VM_1.
Verify that VMs should communicate between each other. Send icmp ping from VM _1 to VM_2 and vice versa.
**Expected result**
Pings should get a response
TC-102: Verify that vmclusters should migrate after shutdown controller.
------------------------------------------------------------------------
**ID**
nsxv_shutdown_controller
**Description**
::
Verify that vmclusters should migrate after shutdown controller.
**Complexity**
core
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard:
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
Add nodes:
3 controllers
Setup Fuel interfaces on slaves:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set
Managment: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Click button 'save settings'
Click button 'verify networks'
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Deploy Cluster
Run OSTF
Shutdown controller with vmclusters.
Check that vmclusters should migrate to another controller.
**Expected result**
VMclusters should migrate to another controller.
TC-103: Deploy cluster with plugin, addition and deletion of nodes.
-------------------------------------------------------------------
**ID**
nsxv_add_delete_nodes
**Description**
::
Verify that system functionality is ok after redeploy.
**Complexity**
advanced
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard:
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
select Vmware vcenter esxi datastore for images (glance)
Add nodes:
3 controllers
2 compute-vmwares
1 cinder-vmdk
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set
Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Run OSTF
Remove node with cinder-vmdk role.
Add node with cinder role
Redeploy cluster.
Run OSTF
Remove node with compute-vmware role
Add node with cinder-vmware role
Redeploy cluster.
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed.
TC-104: Deploy cluster with plugin and deletion one node with controller role.
------------------------------------------------------------------------------
**ID**
nsxv_add_delete_controller
**Description**
::
Verifies that system functionality is ok when controller has been removed.
**Complexity**
advanced
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard:
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
select Vmware vcenter esxi datastore for images (glance)
Add nodes:
4 controller
1 compute-vmware
1 cinder-vmdk
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set
Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Run OSTF
Remove node with controller role.
Redeploy cluster
Run OSTF
Add controller
Redeploy cluster
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed.
TC-105: Verify that it is not possible to uninstall of Fuel NSXv plugin with deployed environment.
---------------------------------------------------------------------------------------------------
**ID**
nsxv_plugin
**Description**
::
It is not possible to remove plugin while at least one environment exists.
**Complexity**
core
**Requre to automate**
Yes
**Steps**
::
Copy plugin to to the Fuel master node using scp.
Install plugin
fuel plugins --install plugin-name-1.0-0.0.1-0.noarch.rpm
Ensure that plugin is installed successfully using cli, run command 'fuel plugins'.
Connect to the Fuel web UI.
Create a new environment using the Fuel UI Wizard:
add name of env and select release version with OS
as hypervisor type: select vcenter check box and Qemu radio button
network setup : Neutron with tunnel segmentation
storage backends: default
additional services: all by default
Click on the Settings tab.
In Settings tab:
enable NSXv plugin
Add nodes:
1 controller
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
Deploy cluster
Run OSTF
Try to delete plugin via cli Remove plugin from master node fuel plugins --remove plugin-name==1.0.0
**Expected result**
Alert: "400 Client Error: Bad Request (Can't delete plugin which is enabled for some environment.)" should be displayed.
TC-106: Check cluster functionality after reboot vcenter.
---------------------------------------------------------
**ID**
nsxv_plugin
**Description**
::
Verifies that system functionality is ok when vcenter has been rebooted.
**Complexity**
core
**Requre to automate**
Yes
**Steps**
::
Create a new environment using the Fuel UI Wizard:
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
select Vmware vcenter esxi datastore for images (glance)
Add nodes:
3 controller
1 computer
1 cinder-vmware
1 cinder
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set
Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Run OSTF
Launch instance VM_1 with image TestVM-VMDK and flavor m1.tiny.
Launch instance VM_2 with image TestVM-VMDK and flavor m1.tiny.
Check connection between VMs, send ping from VM_1 to VM_2 and vice verse.
Reboot vcenter
vmrun -T ws-shared -h https://localhost:443/sdk -u vmware -p VMware01 reset "[standard] vcenter/vcenter.vmx"
Check that controller lost connection with vCenter
Wait for vCenter
Ensure that all instances from vCenter displayed in dashboard.
Ensure connectivity between vcenter1's and vcenter2's VM.
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed. Ping should get response.

124
doc/test/source/test_suite_failover.rst Normal file
View File

@ -0,0 +1,124 @@
Failover
========
Verify that it is not possible to uninstall of Fuel NSX-v plugin with deployed environment.
-------------------------------------------------------------------------------------------
ID
##
nsxv_uninstall_negative
Description
###########
It is not possible to remove plugin while at least one environment exists.
Complexity
##########
smoke
Steps
#####
1. Install NSXv plugin on master node.
2. Create a new environment with enabled plugin.
3. Try to delete plugin via CLI Remove plugin from master node.
Expected result
###############
Alert: "400 Client Error: Bad Request (Can't delete plugin which is enabled for some environment.)" should be displayed.
Shutdown primary controller and check plugin functionality.
-----------------------------------------------------------
ID
##
nsxv_shutdown_controller
Description
###########
Check plugin functionality after shutdown primary controller.
Complexity
##########
core
Steps
#####
1. Log in to Fuel with preinstalled plugin and deployed environment with 3 controllers.
2. Log in to Horizon.
3. Create VM and check connectivity to outside world from VM.
4. Shutdown primary controller.
5. Ensure that VIPs are moved to other controller.
6. Ensure connectivity to outside world from created VM.
7. Create a new network and attach it to router.
8. Create a VM with new network and check network connectivity.
Expected result
###############
Networking is working correct after failure of primary controller.
Check cluster functionality after reboot vcenter.
-------------------------------------------------
ID
##
nsxv_reboot_vcenter
Description
###########
Verifies that system functionality is ok when vcenter has been rebooted.
Complexity
##########
core
Steps
#####
1. Log in to Fuel with preinstalled plugin and deployed environment.
2. Log in to Horizon.
3. Launch instance VM_1 with image TestVM-VMDK and flavor m1.tiny.
4. Launch instance VM_2 with image TestVM-VMDK and flavor m1.tiny.
5. Check connection between VMs, send ping from VM_1 to VM_2 and vice verse.
6. Reboot vcenter: 'vmrun -T ws-shared -h https://localhost:443/sdk -u vmware -p VMware01 reset "[standard] vcenter/vcenter.vmx"'
7. Check that controller lost connection with vCenter.
8. Wait for vCenter.
9. Ensure that all instances from vCenter displayed in dashboard.
10. Ensure connectivity between vcenter1's and vcenter2's VM.
11. Run OSTF.
Expected result
###############
Cluster should be deployed and all OSTF test cases should be passed. ping should get response.

39
doc/test/source/test_suite_gui.rst
View File

@ -1,39 +0,0 @@
GUI Testing
===========
TC-131: Verify that all elements of NSXv plugin section require GUI regiments.
-------------------------------------------------------------------------------
**ID**
nsxv_plugin
**Description**
::
Verify that all elements of NSXv plugin section meets the requirements.
**Complexity**
smoke
**Requre to automate**
Yes
**Steps**
::
Login to the Fuel web UI.
Click on the Settings tab.
Verify that section of NSXv plugin is present on the Settings tab.
Verify that check box ‘NSXv plugin’ is disabled by default.
Verify that user can enabled. Enable NSXv plugin by click on check box ‘NSXv plugin’.
Verify that all labels of NSXv plugin section have same font style and color.
Verify that all elements of NSXv plugin section are vertical aligned.
**Expected result**
All elements of NSXv plugin section meets the requirements.

309
doc/test/source/test_suite_integration.rst
View File

@ -1,297 +1,54 @@
Integration
===========
TC-031: Deploy HA cluster with Fuel NSXv plugin.
-------------------------------------------------
**ID**
nsxv_ha_mode
**Description**
::
Installation in HA mode with 3 controllers.
**Complexity**
core
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard.
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
Add nodes:
3 controller
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Managment: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Deploy cluster
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed.
Deploy cluster with NSX-v plugin and ceilometer.
------------------------------------------------
TC-032: Deploy cluster with Fuel NSXv plugin and Ceph for Glance and Cinder.
-----------------------------------------------------------------------------
**ID**
nsxv_ceph_no_vcenter
**Description**
::
Verifies installation of plugin with Glance and Cinder.
**Complexity**
core
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard.
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
select 'Ceph RBD for volumes' (Cinder) and 'Ceph RBD for images(Glance)'
Add nodes:
1 controller
1 controller + ceph-osd
1 controller + cinder-vmware + ceph-osd
1 cinder-vmware + ceph-osd
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 3 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Deploy cluster
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed.
TC-034: Deploy cluster with Fuel VMware NSXv plugin and ceilometer.
--------------------------------------------------------------------
**ID**
ID
##
nsxv_ceilometer
**Description**
::
Installation of plugin with ceilometer.
Description
###########
**Complexity**
Check deployment with Fuel NSXv plugin and Ceilometer.
Complexity
##########
core
**Requre to automate**
No
Steps
#####
**Steps**
::
1. Log into Fuel with preinstalled plugin.
2. Create a new environment with following parameters:
* Compute: KVM/QEMU with vCenter
* Networking: Neutron with tunnel segmentation
* Storage: default
* Additional services: ceilometer
3. Add nodes with following roles:
* Controller + Mongo
* Controller + Mongo
* Controller + Mongo
* ComputeVMware
4. Configure interfaces on nodes.
5. Configure network settings.
6. Enable and configure NSXv plugin.
7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
8. Verify networks.
9. Deploy cluster.
10. Run OSTF.
Create a new environment using the Fuel UI Wizard.
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: install ceilometer
In Settings tab:
enable NSXv plugin
Add nodes:
3 controller + mongo
1 compute-vmware
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 1 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
Deploy cluster
Run OSTF.
**Expected result**
Expected result
###############
Cluster should be deployed and all OSTF test cases should be passed.
TC-035: Deploy cluster with Fuel VMware NSXv plugin, Ceph for Cinder and VMware datastore backend for Glance.
-------------------------------------------------------------------------------------------------------------
**ID**
nsxv_ceph
**Description**
::
Verifies installation of plugin for vcenter with Glance and Cinder.
**Complexity**
core
**Requre to automate**
No
**Steps**
::
Create a new environment using the Fuel UI Wizard.
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: default
In Settings tab:
enable NSXv plugin
select 'Ceph RBD for volumes' (Cinder) and 'Vmware Datastore for images(Glance)'
Add nodes:
3 controller + ceph-osd
2 cinder-vmware
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Deploy cluster
Run OSTF
**Expected result**
Cluster should be deployed and all OSTF test cases should be passed.

117
doc/test/source/test_suite_scale.rst Normal file
View File

@ -0,0 +1,117 @@
Scale
=====
Deploy cluster with plugin and deletion one node with controller role.
----------------------------------------------------------------------
ID
##
nsxv_add_delete_controller
Description
###########
Verifies that system functionality is ok when controller has been removed.
Complexity
##########
core
Steps
#####
1. Log into Fuel with preinstalled plugin.
2. Create a new environment with following parameters:
* Compute: KVM/QEMU with vCenter
* Networking: Neutron with tunnel segmentation
* Storage: default
* Additional services: ceilometer
3. Add nodes with following roles:
* Controller
* Controller
* Controller
* Controller
* CinderVMware
* ComputeVMware
4. Configure interfaces on nodes.
5. Configure network settings.
6. Enable and configure NSXv plugin.
7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
8. Deploy cluster.
9. Run OSTF.
10. Remove node with controller role.
11. Redeploy cluster.
12. Run OSTF.
13. Add controller.
14. Redeploy cluster.
15. Run OSTF.
Expected result
###############
Cluster should be deployed and all OSTF test cases should be passed.
Deployment with 3 Controllers, ComputeVMware, CinderVMware and check adding/deleting of nodes
---------------------------------------------------------------------------------------------
ID
##
nsxv_add_delete_nodes
Description
###########
Verify that system functionality is ok after redeploy.
Complexity
##########
core
Steps
#####
1. Connect to a Fuel web UI with preinstalled plugin.
2. Create a new environment with following parameters:
* Compute: KVM/QEMU with vCenter
* Networking: Neutron with VLAN segmentation
* Storage: Ceph
* Additional services: default
3. Add nodes with following roles:
* Controller
* Controller
* Controller
* ComputeVMware
4. Configure interfaces on nodes.
5. Configure network settings.
6. Enable and configure NSXv plugin.
7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
8. Deploy cluster.
9. Run OSTF.
10. Add node with CinderVMware role.
11. Redeploy cluster.
12. Run OSTF
13. Remove node with CinderVMware role.
14. Redeploy cluster.
15. Run OSTF.
Expected result
###############
Changing of cluster configuration was successful. Cluster should be deployed and all OSTF test cases should be passed.

314
doc/test/source/test_suite_smoke.rst
View File

@ -1,148 +1,260 @@
Smoke
=====
TC-001: Verify that Fuel VMware NSXv plugin is installed.
----------------------------------------------------------
**ID**
Install Fuel VMware NSX-v plugin.
---------------------------------
nsxv_plugin
**Description**
::
ID
##
Test case verifies plugin installation.
nsxv_install
**Complexity**
Description
###########
Check that plugin can be installed.
Complexity
##########
smoke
**Requre to automate**
Yes
Steps
#####
**Steps**
::
1. Connect to fuel node via ssh.
2. Upload plugin.
3. Install plugin.
Connect to fuel node via ssh.
Upload plugin.
Install plugin.
**Expected result**
Expected result
###############
Ensure that plugin is installed successfully using cli, run command 'fuel plugins'. Check name, version and package version of plugin.
Ensure that plugin is installed successfully using CLI, run command 'fuel plugins'. Check name, version and package version of plugin.
TC-002: Verify that Fuel VMware NSXv plugin is uninstalled.
-------------------------------------------------------------
**ID**
Uninstall Fuel VMware NSX-v plugin.
-----------------------------------
nsxv_plugin
**Description**
::
ID
##
Test verifies that plugin could be uninstalled.
nsxv_uninstall
**Complexity**
Description
###########
Check that plugin can be removed.
Complexity
##########
smoke
**Requre to automate**
Yes
Steps
#####
**Steps**
::
1. Connect to fuel node with preinstalled plugin via ssh.
2. Remove plugin.
Connect to fuel node with preinstalled plugin via ssh.
Remove plugin from master node
Connect to the Fuel web UI.
Create a new environment.
Click on the Settings tab and check that section of NSXv plugin is not displayed.
**Expected result**
Expected result
###############
Verify that plugin is removed, run command 'fuel plugins'. Section of NSXv plugin is not displayed.
Verify that plugin is removed, run command 'fuel plugins'.
TC-003: Deploy cluster with plugin and vmware datastore backend.
Verify that all elements of NSXv plugin section meets the requirements.
-----------------------------------------------------------------------
ID
##
nsxv_gui
Description
###########
Verify that all elements of NSXv plugin section meets the requirements.
Complexity
##########
smoke
Steps
#####
1. Login to the Fuel web UI.
2. Click on the Settings tab.
3. Verify that section of NSXv plugin is present on the Settings tab.
4. Verify that check box 'NSXv plugin' is disabled by default.
5. Verify that user can enabled. Enable NSX-v plugin by click on check box 'NSXv plugin'.
6. Verify that all labels of NSX-v plugin section have same font style and color.
7. Verify that all elements of NSX-v plugin section are vertical aligned.
Expected result
###############
All elements of NSX-v plugin section are required GUI regiments.
Deployment with plugin, controller and vmware datastore backend.
----------------------------------------------------------------
**ID**
ID
##
nsxv_smoke
**Description**
::
Test verifies installation with base configuration.
Description
###########
**Complexity**
Check deployment with NSXv plugin and one controller.
Complexity
##########
smoke
**Requre to automate**
No
Steps
#####
**Steps**
::
1. Log into Fuel with preinstalled plugin.
2. Create a new environment with following parameters:
* Compute: KVM/QEMU with vCenter
* Networking: Neutron with tunnel segmentation
* Storage: default
* Additional services: default
3. Add nodes with following roles:
* Controller
4. Configure interfaces on nodes.
5. Configure network settings.
6. Enable and configure NSXv plugin.
7. Configure settings:
* Enable VMWare vCenter/ESXi datastore for images (Glance).
8. Configure VMware vCenter Settings. Add 1 vSphere cluster and configure Nova Compute instances on controllers.
9. Verify networks.
10. Deploy cluster.
11. Run OSTF.
Create a new environment using the Fuel UI Wizard.
add name of env and select release version with OS
as hypervisor type: select vcenter check box and QEMU/KVM radio button
network setup : Neutron with tunnel segmentation.
storage backends: default
additional services: all by default
In Settings tab:
enable NSXv plugin
select Vmware vcenter esxi datastore for images (glance)
Add nodes:
1 controller
1 compute-vmware
Interfaces on slaves should be setup this way in Fuel interface:
eth0 - admin(PXE)
eth1 - public
eth2 - management
eth3 - VM(Fixed) ID:103
eth4 – storage
Networks tab:
Public network: start '172.16.0.2' end '172.16.0.126'
CIDR '172.16.0.0/24'
Gateway 172.16.0.1
Floating ip range start '172.16.0.130' end '172.16.0.254'
Storage: CIDR '192.168.1.0/24'
Vlan tag is not set-Management: CIDR '192.168.0.0/24'
Vlan tag is not set
Neutron L2 configuration by default
Neutron L3 configuration by default
Verify networks.
Fill vcenter credentials:
Availability zone: vcenter
vCenter host: '172.16.0.254'
vCenter username: <login>
vCenter password: <password>
Add 2 vSphere Clusters:
vSphere Cluster: Cluster1
Service name: vmcluster1
Datastore regex:.*
vSphere Cluster: Cluster2
Service name: vmcluster2
Datastore regex: .*
Fill Glance credentials:
vCenter host: 172.16.0.254
vCenter username: <login>
vCenter password: <password>
Datacenter name: Datacenter
Datastore name: nfs
Deploy cluster
Run OSTF
**Expected result**
Expected result
###############
Cluster should be deployed and all OSTF test cases should be passed.
Deploy HA cluster with NSX-v plugin.
------------------------------------
ID
##
nsxv_bvt
Description
###########
Check deployment with NSXv plugin, 3 Controllers, 2 CephOSD, CinderVMware and computeVMware roles.
Complexity
##########
smoke
Steps
#####
1. Connect to a Fuel web UI with preinstalled plugin.
2. Create a new environment with following parameters:
* Compute: KVM/QEMU with vCenter
* Networking: Neutron with tunnel segmentation
* Storage: Ceph
* Additional services: default
3. Add nodes with following roles:
* Controller
* Controller
* Controller
* CephOSD
* CephOSD
* CinderVMware
* ComputeVMware
4. Configure interfaces on nodes.
5. Configure network settings.
6. Enable and configure NSXv plugin.
7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
8. Verify networks.
9. Deploy cluster.
10. Run OSTF.
Expected result
###############
Cluster should be deployed and all OSTF test cases should be passed.
Verify that nsxv driver configured properly after enabling NSX-v plugin
-----------------------------------------------------------------------
ID
##
nsxv_config_ok
Description
###########
Need to check that all parameters of nsxv driver config files have been filled
up with values entered from GUI. Applicable values that are typically used are
described in plugin docs. Root and intermediate certificate are signed, in
attachment.
Complexity
##########
smoke
Steps
#####
1. Install NSXv plugin.
2. Enable plugin on tab Settings -> NSXv plugin.
3. Fill the form with corresponding values.
4. Uncheck option "Bypass NSX Manager certificate verification".
5. Do all things that are necessary to provide interoperability of NSXv plugin and NSX Manager with certificate.
6. Check Additional settings. Fill the form with corresponding values. Save settings by pressing the button.
Expected result
###############
Check that nsx.ini on controller nodes is properly configured.

1130
doc/test/source/test_suite_system.rst
View File

File diff suppressed because it is too large Load Diff