[tripleo] deprecating Mistral service

Luke Short ekultails at gmail.com
Sat Oct 10 22:27:10 UTC 2020


+1 I believe it is good for us to focus on the core OpenStack services that
still have an active community and usage in production. For better or
worse, Mistral has dropped in popularity due to other similar
swiss-army-knife workflow automation tools.

On Thu, Oct 8, 2020, 6:34 AM Emilien Macchi <emilien at redhat.com> wrote:

> Hi folks,
>
> In our long term goal to simplify TripleO and deprecate the services that
> aren't used by our community anymore, I propose that we deprecate Mistral
> services.
> Mistral was used on the Undercloud in the previous cycles but not anymore.
> While the service could be deployed on the Overcloud, we haven't seen any
> of our users doing it. If that would be the case, please let us know as
> soon as possible.
> Removing it from TripleO will help us with maintenance (container images,
> THT/puppet integration, CI, etc).
> Maybe we could deprecate it in Victoria and remove it in Wallaby?
>
> Thanks,
> --
> Emilien Macchi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201010/50785b22/attachment.html>


More information about the openstack-discuss mailing list