Add knowledge of storage network to scenario tests
In many deployments, shared file systems are exported
over a shared storage network. Typically, this shared
storage network is not reachable from within
private tenant networks. Our tests currently
have no cognizance of this topology, and expect that
shares are always exported on a network routable or
directly reachable through private tenant networks.
Add a configuration option to allow configuring the
name or UUID of a shared storage network. If specified
this network will be plugged into VMs created by the
scenario tests and access control will be on the
storage network IP, if NFS.
Change-Id: I8d8063d46284076499d868a5f9b3d13a2a78b5b0
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
diff --git a/manila_tempest_tests/config.py b/manila_tempest_tests/config.py
index c6b9c73..e0e8ea3 100644
--- a/manila_tempest_tests/config.py
+++ b/manila_tempest_tests/config.py
@@ -86,6 +86,15 @@
help="Forces access rules to be as specified on NFS scenario"
" tests. This can used for working around multiple "
"NATs between the VMs and the storage controller."),
+ cfg.StrOpt("storage_network",
+ help="Name or UUID of a neutron network that is used to access "
+ "shared file systems over. If specified, test virtual "
+ "machines are created with two NICs, the primary NIC is "
+ "attached to the private project network and the "
+ "secondary NIC is attached to the specified storage "
+ "network. If using NFS, access control is done with the "
+ "help of the IP address assigned to the virtual machine's "
+ "storage network NIC."),
cfg.ListOpt("enable_ro_access_level_for_protocols",
default=["nfs", ],
help="List of protocols to run tests with ro access level."),