[tripleo][operators] Removal of mistral from the TripleO Undercloud
kecarter at redhat.com
Fri Mar 13 19:24:46 UTC 2020
In the pursuit to remove Mistral from the TripleO undercloud, we've
discovered an old capability that we need to figure out how best to handle.
Currently, we provide the ability for an end-user (operator / deployer) to
pass in "N" Mistral workflows as part of a given deployment plan which is
processed by python-tripleoclient at runtime . From what we have
documented, and what we can find within the code-base, we're not using this
feature by default. That said, we do not remove something if it is
valuable in the field without an adequate replacement. The ability to run
arbitrary Mistral workflows at deployment time was first created in 2017
 and while present all this time, its documented  and intra-code-base
uses are still limited to samples . As it stands now, we're on track to
making Mistral inert this cycle and if our progress holds over the next
couple of weeks the capability to run arbitrary Mistral workflows will be
the only thing left within our codebase that relies on Mistral running on
So the question is what do we do with functionality. Do we remove this
ability out right, do we convert the example workflow  into a
stand-alone Ansible playbook and change the workflow runner to an
arbitrary playbook runner, or do we simply leave everything as-is and
deprecate it to be removed within the next two releases? Although it would
be perfectly acceptable to keep Mistral around a little while longer, it
would also be a bummer if this one capability was the only reason we were
not able to remove Mistral from the Undercloud.
Any and all feedback from operators, deployers, developers, former
developers, etc would be greatly appreciated.
Thank you in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss