Description of problem: Currently plugins are found within the Sahara core code. The problem with this is that we slow the upgrades progress and force the users to upgrade OpenStack version in order to get a new version of a plugin in. We want to remove the code from Sahara core and have it installed as a library so we can release more often. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
More than "remove", it's about "decoupling".
While the work is ongoing, it is very unlikely that this will end up in Rocky. Moving.
The code of the plugins has been split into separate repositories and then different packages. Those packages are now available in the container images for Sahara (sahara-api and sahara-engine; see also https://bugzilla.redhat.com/show_bug.cgi?id=1690537 ). The split package code is recognized by sahara core. Verified on openstack-sahara-api-10.0.1-0.20190503161819.994ff8c.el8ost.noarch openstack-sahara-common-10.0.1-0.20190503161819.994ff8c.el8ost.noarch puppet-sahara-14.4.1-0.20190420121202.abf76b2.el8ost.noarch python3-sahara-10.0.1-0.20190503161819.994ff8c.el8ost.noarch python3-sahara-plugin-ambari-1.0.1-0.20190503150400.75f8698.el8ost.noarch python3-sahara-plugin-cdh-1.0.1-0.20190503160353.b73a04d.el8ost.noarch python3-sahara-plugin-mapr-1.0.1-0.20190503160355.7f4e060.el8ost.noarch python3-saharaclient-2.2.0-0.20190312151158.25043cb.el8ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811