[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[tripleo] deprecating Mistral service


Although the decision was made long ago (about 1.5 years AFAIK) itâ??s still disappointing for me to see it happening and I feel like saying something.

It may sound weird but, in the best attempt to be technically honest, I actually agree with the decision to remove Mistral from TripleO. As far as I know, TripleO never used the strongest distinguishing sides of Mistral (like running workflows at scale, using it for very long running workflows etc). Mistral was mostly used just to extend configurability customizability of TripleO. Red Hatâ??s engineers who I had a great pleasure to work with on Mistral a few times told me â??Hey, we are allocated to Mistral but we just donâ??t know what else to work on that our company would need. It just works for us. Works very well for the case we use it. Bugs are very rare, maintenance doesnâ??t require 4 people from Red Hat. So weâ??ll be shrinking our presence.â?? So it happened, as expected. I realized there was no point in trying to keep them on the project. Then some new engineers came and said: â??Why canâ??t we use something else, more well-known, like Ansible?â?? So, honestly, for this use case, yes. However, I heard many times that Ansible is essentially the same thing as Mistral but it is more mature, well maintained, etc etc. And every time I had to explain why these two technologies are fundamentally different, have different purposes, different method of solving problems.

Iâ??m saying this now because I feel it is my fault that I failed to explain these differences clearly when we started actively promoting Mistral years ago. And it would be bad if misunderstanding of the technology was the real reason behind this decision. For what itâ??s worth, if you ever want me to elaborate on that, let me know. This thread is not a good place for that, I apologize.

And finally, I want to reassure you that the project is still maintained. More than that, it keeps evolving in a number of ways and new functionality is consistently being added. The number of active contributors is now lower than in our best times (Also true I believe for OpenStack in general) but itâ??s now promising to change.

Again, my apologies for writing it here.


Renat Akhmerov
11 окÑ?. 2020 г., 05:28 +0700, Luke Short <ekultails at gmail.com>, пиÑ?ал:
> +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/20201012/30975325/attachment.html>