Fix DevStack to configure tempest's service_availability
Tempest's service_availability config option includes all the service
availability which is further used by tests to take decision of skip
or run the test.
For example, [service_availability].nova is true then, compute test will run
or if [service_availability].aodh is false then, all aodh related tests either
in aodh tempest plugin or any other plugins will be skipped.
Now question is what is the best way to set the each service availability for
tempest or tempest plugins tests. We have 2 category of service here-
1. Service tested by Tempest (nova, cinder, keystone, glance, swift, neutron)
(let's say type1 service)
2. Services tested by Tempest plugins (all other than above list)
(let's say type2 service)
We need the standard way to set both type of service so that we can maintain
the setting of service_availability config options in consistent way.
As discussed on bug#1743688/ and review https://review.openstack.org/#/c/536723/,
we will use devstack lib/tempest to set the type1 service which is services test
owned by Tempest and type2 service setting will be done by devstack plugins of
those service.
For example - [service_availability].ironic will be set by ironic's devstack plugin.
because that is best place we know ironic is installed and available.
To do that we need:
1. Add setting of [service_availability].* in devstack plugins
2. Remove setting of type2 service from devstack lib/tempest
This commit does the second part and all depends-on patches handle the first part.
Reviewed: https:/ /review. opendev. org/619973 /git.openstack. org/cgit/ openstack/ devstack/ commit/ ?id=f0dd9996cc6 35709276f51e4d9 4c5ebbf5d5b49f
Committed: https:/
Submitter: Zuul
Branch: master
commit f0dd9996cc63570 9276f51e4d94c5e bbf5d5b49f
Author: ghanshyam <email address hidden>
Date: Mon Nov 26 07:38:54 2018 +0000
Fix DevStack to configure tempest's service_ availability
Tempest's service_ availability config option includes all the service
availability which is further used by tests to take decision of skip
or run the test.
For example, [service_ availability] .nova is true then, compute test will run availability] .aodh is false then, all aodh related tests either
or if [service_
in aodh tempest plugin or any other plugins will be skipped.
Now question is what is the best way to set the each service availability for
tempest or tempest plugins tests. We have 2 category of service here-
1. Service tested by Tempest (nova, cinder, keystone, glance, swift, neutron)
(let's say type1 service)
2. Services tested by Tempest plugins (all other than above list)
(let's say type2 service)
We need the standard way to set both type of service so that we can maintain availability config options in consistent way.
the setting of service_
As discussed on bug#1743688/ and review https:/ /review. openstack. org/#/c/ 536723/,
we will use devstack lib/tempest to set the type1 service which is services test
owned by Tempest and type2 service setting will be done by devstack plugins of
those service.
For example - [service_ availability] .ironic will be set by ironic's devstack plugin.
because that is best place we know ironic is installed and available.
To do that we need: availability] .* in devstack plugins
1. Add setting of [service_
2. Remove setting of type2 service from devstack lib/tempest
This commit does the second part and all depends-on patches handle the first part.
Related-Bug: #1743688
Change-Id: If3aec9fd1c61e2 bb53233be437b97 b811dc82414