Comment 32 for bug 1743688

Note: we are facing these issue because service_available config option is registered by tempest plugin repo which is separate repo from service. So registration of config option and setting value is happening via separate repo.

These are the final steps to fix the service_availabilty config option.

1. Devstack should set only tempest own services - https://review.openstack.org/#/c/619973/
2. each plugin to set their service as service_availability in their devstack plugin - In progress
3. Change the default value of service_available.<service> config option default value to false.
4. Add used tempest plugins in tempest plugins's requirements.txt after adding it in g-r.

That way we will solve all the issues currently faced by cross tempest plugin:
1. Required tempest plugin's service_availability config option is registered:
- Any tempest plugin can install required tempest plugins as a dependency in requirement.txt.
2. Service_available value is set correctly:
- Each service will set its service_available config option correctly while installation itself via devstack plugin.