tempest plugins should be loaded though configuration

[Jeffrey Zhang]

tempest plugins should be loaded though configuration.

Now the tempest plugins load plugins as long as the plugin is installed.

It is not friendly especially for building docker images.

So there should be an option used to specific which plugins you want.

[Andrea Frittoli (andrea-frittoli)]

Could you explain why this is not friendly for building docker images?

Tempest plugins are now moved to dedicated repositories - it was a community goal in Queens - so if you don't want a plugin you simply do not install it / include it in your docker image.

And even if you install a plugin, you still have the option to configure which service is available and which not as well as filtering tests via regular expression.

[chandan kumar (chkumar246)]

We have discussion regarding this bug in #openstack-qa office hour: http://eavesdrop.openstack.org/meetings/qa_office_hour/2018/qa_office_hour.2018-02-01-09.05.log.html
We agreed that:
* Bundle all the plugins in a single containers.
* User service_available config params to enable or disable a plugin while using it
* In tempest we have blacklist or whitelist test params to play with tests.

I think it solves the problem. This bug is no longer valid.