Re-enable Zaza

[Aurelien Lourot]

Zaza has been disabled in the past because we need to set up things first in our testing environment. In a nutshell we'll need:
- a long-living NetApp appliance
- some env vars in ubuntu-openstack-ci (example [0])
- some env vars in zosci-config (example [1])
- an osci.yaml file for zOSCI to run (example [2])
- some Zaza setup/configure steps to set dynamic things for the test

Based on details given by ionutbalutoiu (modified by lourot):
----------
This requires a functional external NetApp ONTAP cluster configured. And the Zaza overcloud VMs must be able to reach the NetApp ONTAP cluster via the overcloud external network.

Example environment:

export TEST_NET_ID=$(openstack network show juju_network -f value -c id)
export TEST_GATEWAY=10.99.1.1
export TEST_NAME_SERVER=10.99.1.2
export TEST_CIDR_EXT=10.99.0.0/16
export TEST_FIP_RANGE=10.99.3.110:10.99.3.160

export TEST_MANILA_NETAPP_MANAGEMENT_ADDRESS=10.113.1.191
export TEST_MANILA_NETAPP_ADMIN_NAME=admin
export TEST_MANILA_NETAPP_ADMIN_PASSWORD=Passw0rd

export TEST_MANILA_NETAPP_VSERVER_NAME=svm0

export TEST_MANILA_NETAPP_ROOT_VOL_AGGR_NAME=test_cluster_01_VM_DISK_1

We also use zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step. The idea is to give as TEST_NET_ID an OpenStack network that is able to reach external NetApp ONTAP cluster.

For example the juju_network can be the external network from the undercloud, and it’s routed to reach the management address of the NetApp ONTAP cluster (10.113.1.191).

The environment variables:
TEST_MANILA_NETAPP_MANAGEMENT_ADDRESS
TEST_MANILA_NETAPP_ADMIN_NAME
TEST_MANILA_NETAPP_ADMIN_PASSWORD

correspond to the external NetApp ONTAP cluster connection information.

The env variable TEST_MANILA_NETAPP_VSERVER_NAME corresponds to the name of an already configured vserver (or storage VM in newer NetApp ONTAP versions) with NFS already enabled. This is going to be used by the non-DHSS test.

And, the env variable TEST_MANILA_NETAPP_ROOT_VOL_AGGR_NAME corresponds to the NetApp ONTAP storage aggregate name that is used as storage pool to spawn new storage VMs by the Manila driver. This is used by the DHSS test.

Example on how to find out the name of the default storage aggregate name in the NetApp ONTAP cluster [3]

This needs to be executed after SSH-ing into one of the NetApp ONTAP cluster nodes. Perhaps this value can be extracted from the web UI as well.

Keep in mind that the DHSS test also needs a share network defined. The Zaza test will create the share network, and it’s associated to the network given to the zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step.

So, it’s important to know that the Manila driver will set static IPs to the NetApp ONTAP storage VMs from the range given as TEST_FIP_RANGE. As long as the Zaza overcloud VMs have connectivity to storage VMs with static IPs from that range, we're good for the DHSS test case.
----------

A review for re-enabling Zaza exists already [4]

[0] https://bazaar.launchpad.net/~uosci/ubuntu-openstack-ci/trunk/view/head:/run/job-parts/osci_openstack_common.sh#L60
[1] https://github.com/openstack-charmers/zosci-config/blob/master/zuul.d/jobs.yaml#L212
[2] https://github.com/openstack/charm-keystone/blob/master/osci.yaml
[3] http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-940%2Fstorage__aggregate__show.html
[4] https://review.opendev.org/c/openstack/charm-manila-netapp/+/783892