| 2021-04-01 09:08:47 |
Aurelien Lourot |
description |
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 Magnum 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):
----------
Environment example:
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.4.110:10.99.4.160
export TEST_MAGNUM_QCOW2_IMAGE_URL=http://10.99.1.3:8080/fedora-coreos-33.20210117.3.2-openstack.x86_64.qcow2
export OS_VIP00=10.99.2.206
The first set of env variables:
TEST_NET_ID
TEST_GATEWAY
TEST_NAME_SERVER
TEST_CIDR_EXT
TEST_FIP_RANGE
is needed for the zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step [3]
Notice that TEST_NET_ID points to the juju_network where the Juju units are attached. This way, we allow overcloud Magnum VMs to reach Keystone from the undercloud (which is required).
We use this basic_overcloud_network configure step into multiple charms. We can probably copy-paste it and add it to this job. For example, this is also used at nova-cloud-controller charm [4]
The TEST_MAGNUM_QCOW2_IMAGE_URL corresponds to an OS qcow2 cloud image orchestrated by Magnum.
The current Zaza tests expect that image to be fedora-coreos. A ready to use cloud image can be downloaded from [5]
From there you’ll get an archive (with the xz format). Unarchive the image, and upload it to a web server within the CI infrastructure.
And, the OS_VIP00 is meant to be given to deploy Magnum in HA using the HAcluster subordinate charm. We also use this into multiple other Zaza jobs. For example, we have it used in the Keystone charm [6]
----------
[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] https://opendev.org/openstack/charm-magnum/src/commit/659774aec3cfa805759d51499fdd4eb9602aacfd/src/tests/tests.yaml#L15
[4] https://opendev.org/openstack/charm-nova-cloud-controller/src/commit/997987e791d6d42cbffefa6793b54971b0f86e52/tests/tests.yaml#L25
[5] https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable
[6] https://opendev.org/openstack/charm-keystone/src/commit/b0ea402ec0fd14f8a686c597a434c3e68e4f3c3b/tests/bundles/overlays/local-charm-overlay.yaml.j2#L5 |
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 Magnum 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):
----------
Environment example:
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.4.110:10.99.4.160
export TEST_MAGNUM_QCOW2_IMAGE_URL=http://10.99.1.3:8080/fedora-coreos-33.20210117.3.2-openstack.x86_64.qcow2
export OS_VIP00=10.99.2.206
The first set of env variables:
TEST_NET_ID
TEST_GATEWAY
TEST_NAME_SERVER
TEST_CIDR_EXT
TEST_FIP_RANGE
is needed for the zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step [3]
Notice that TEST_NET_ID points to the juju_network where the Juju units are attached. This way, we allow overcloud Magnum VMs to reach Keystone from the undercloud (which is required).
We use this basic_overcloud_network configure step into multiple charms. We can probably copy-paste it and add it to this job. For example, this is also used at nova-cloud-controller charm [4]
The TEST_MAGNUM_QCOW2_IMAGE_URL corresponds to an OS qcow2 cloud image orchestrated by Magnum.
The current Zaza tests expect that image to be fedora-coreos. A ready to use cloud image can be downloaded from [5]
From there you’ll get an archive (with the xz format). Unarchive the image, and upload it to a web server within the CI infrastructure.
And, the OS_VIP00 is meant to be given to deploy Magnum in HA using the HAcluster subordinate charm. We also use this into multiple other Zaza jobs. For example, we have it used in the Keystone charm [6]
----------
A review for re-enabling Zaza exists already [7]
[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] https://opendev.org/openstack/charm-magnum/src/commit/659774aec3cfa805759d51499fdd4eb9602aacfd/src/tests/tests.yaml#L15
[4] https://opendev.org/openstack/charm-nova-cloud-controller/src/commit/997987e791d6d42cbffefa6793b54971b0f86e52/tests/tests.yaml#L25
[5] https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable
[6] https://opendev.org/openstack/charm-keystone/src/commit/b0ea402ec0fd14f8a686c597a434c3e68e4f3c3b/tests/bundles/overlays/local-charm-overlay.yaml.j2#L5
[7] https://review.opendev.org/c/openstack/charm-magnum/+/783023 |
|
| 2021-04-01 15:09:18 |
Aurelien Lourot |
description |
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 Magnum 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):
----------
Environment example:
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.4.110:10.99.4.160
export TEST_MAGNUM_QCOW2_IMAGE_URL=http://10.99.1.3:8080/fedora-coreos-33.20210117.3.2-openstack.x86_64.qcow2
export OS_VIP00=10.99.2.206
The first set of env variables:
TEST_NET_ID
TEST_GATEWAY
TEST_NAME_SERVER
TEST_CIDR_EXT
TEST_FIP_RANGE
is needed for the zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step [3]
Notice that TEST_NET_ID points to the juju_network where the Juju units are attached. This way, we allow overcloud Magnum VMs to reach Keystone from the undercloud (which is required).
We use this basic_overcloud_network configure step into multiple charms. We can probably copy-paste it and add it to this job. For example, this is also used at nova-cloud-controller charm [4]
The TEST_MAGNUM_QCOW2_IMAGE_URL corresponds to an OS qcow2 cloud image orchestrated by Magnum.
The current Zaza tests expect that image to be fedora-coreos. A ready to use cloud image can be downloaded from [5]
From there you’ll get an archive (with the xz format). Unarchive the image, and upload it to a web server within the CI infrastructure.
And, the OS_VIP00 is meant to be given to deploy Magnum in HA using the HAcluster subordinate charm. We also use this into multiple other Zaza jobs. For example, we have it used in the Keystone charm [6]
----------
A review for re-enabling Zaza exists already [7]
[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] https://opendev.org/openstack/charm-magnum/src/commit/659774aec3cfa805759d51499fdd4eb9602aacfd/src/tests/tests.yaml#L15
[4] https://opendev.org/openstack/charm-nova-cloud-controller/src/commit/997987e791d6d42cbffefa6793b54971b0f86e52/tests/tests.yaml#L25
[5] https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable
[6] https://opendev.org/openstack/charm-keystone/src/commit/b0ea402ec0fd14f8a686c597a434c3e68e4f3c3b/tests/bundles/overlays/local-charm-overlay.yaml.j2#L5
[7] https://review.opendev.org/c/openstack/charm-magnum/+/783023 |
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:
- 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):
----------
Environment example:
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.4.110:10.99.4.160
export TEST_MAGNUM_QCOW2_IMAGE_URL=http://10.99.1.3:8080/fedora-coreos-33.20210117.3.2-openstack.x86_64.qcow2
export OS_VIP00=10.99.2.206
The first set of env variables:
TEST_NET_ID
TEST_GATEWAY
TEST_NAME_SERVER
TEST_CIDR_EXT
TEST_FIP_RANGE
is needed for the zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network configure step [3]
Notice that TEST_NET_ID points to the juju_network where the Juju units are attached. This way, we allow overcloud Magnum VMs to reach Keystone from the undercloud (which is required).
We use this basic_overcloud_network configure step into multiple charms. We can probably copy-paste it and add it to this job. For example, this is also used at nova-cloud-controller charm [4]
The TEST_MAGNUM_QCOW2_IMAGE_URL corresponds to an OS qcow2 cloud image orchestrated by Magnum.
The current Zaza tests expect that image to be fedora-coreos. A ready to use cloud image can be downloaded from [5]
From there you’ll get an archive (with the xz format). Unarchive the image, and upload it to a web server within the CI infrastructure.
And, the OS_VIP00 is meant to be given to deploy Magnum in HA using the HAcluster subordinate charm. We also use this into multiple other Zaza jobs. For example, we have it used in the Keystone charm [6]
----------
A review for re-enabling Zaza exists already [7]
[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] https://opendev.org/openstack/charm-magnum/src/commit/659774aec3cfa805759d51499fdd4eb9602aacfd/src/tests/tests.yaml#L15
[4] https://opendev.org/openstack/charm-nova-cloud-controller/src/commit/997987e791d6d42cbffefa6793b54971b0f86e52/tests/tests.yaml#L25
[5] https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable
[6] https://opendev.org/openstack/charm-keystone/src/commit/b0ea402ec0fd14f8a686c597a434c3e68e4f3c3b/tests/bundles/overlays/local-charm-overlay.yaml.j2#L5
[7] https://review.opendev.org/c/openstack/charm-magnum/+/783023 |
|
