x
/
fuel-plugin-nsxv
Code Issues Proposed changes

Test plan for Variants of nova_metadata_ips (management or public) 

Add 3 tests:
nsxv_metadata_mgt_disabled
nsxv_metadata_mgt_enabled
nsxv_metadata_mgt_reserve_enabled

Change-Id: I8905112f51e790814f7711df041a4f4dd805d96c
This commit is contained in:
Andrey Setyaev 2016-03-23 14:20:01 +00:00
parent 6f2b85249b
commit aab17fb813
1 changed files with 157 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -912,3 +912,160 @@ Expected result
Environment has been deployed successfully.
Check availability metadata server with disabled nsxv_metadata_listen_mgmt
------------------------------------------------------------------
ID
##
nsxv_metadata_mgt_disabled
Description
###########
Test case verifies option nsxv_metadata_listen_mgmt in disabled state.
Complexity
##########
core
Steps
#####
1. Configure cluster.
2. Install fuel and nsxv plugin.
3. Configure nsxv plugin.
Manually specify the IP address, network mask and default route for the proxy metadata router.
4. Launch instance and run command from it::
wget -O - 169.254.169.254
Expected result
###############
Option 'Use mgmt network to access the metadata server' (nsxv_metadata_listen_mgmt) was disabled by default.
Request should return::
Connecting to 169.254.169.254 (169.254.169.254:80)
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
Check availability metadata server with nsxv_metadata_listen_mgmt enabled and nsxv_mgt_reserve_ip disabled
--------------------------------------------------------------------------------------------------
ID
##
nsxv_metadata_mgt_enabled
Description
###########
Test case verifies option nsxv_metadata_listen_mgmt in enabled state, nsxv_mgt_reserve_ip is disabled.
Complexity
##########
core
Steps
#####
1. Configure cluster.
2. Install fuel and nsxv plugin and enable option 'Use mgmt network to access the metadata server' (nsxv_metadata_listen_mgmt).
3. Configure nsxv plugin.
Manually specify the IP address, network mask and default route for the proxy metadata router.
4. Launch instance and run command from it::
wget -O - 169.254.169.254
Expected result
###############
Option 'Use mgmt network to access the metadata server' and
option 'Reservation ip address in management network for use with NSXv metadata proxy' are disabled by default.
Request should return::
Connecting to 169.254.169.254 (169.254.169.254:80)
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
Check availability metadata server with nsxv_metadata_listen_mgmt enabled and nsxv_mgt_reserve_ip enabled
-------------------------------------------------------------------------------------------------
ID
##
nsxv_metadata_mgt_reserve_enabled
Description
###########
Test case verifies options:
nsxv_metadata_listen_mgmt enabled
nsxv_mgt_reserve_ip enabled.
Complexity
##########
core
Steps
#####
1. Configure cluster.
2. Install fuel and nsxv plugin.
3. Configure nsxv plugin and enable both options 'Use mgmt network to access the metadata server' (nsxv_metadata_listen_mgmt),
'Reservation ip address in management network for use with NSXv metadata proxy' (nsxv_mgt_reserve_ip).
You must specify the portgroup id as "Metadata portgroup MoRef ID" which looks at management network openstack.
4. Launch instance and run command from it::
wget -O - 169.254.169.254
Expected result
###############
Option 'Use mgmt network to access the metadata server' and
option 'Reservation ip address in management network for use with NSXv metadata proxy' are disabled by default.
Request should return::
Connecting to 169.254.169.254 (169.254.169.254:80)
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04