Open Stack

+1

Will we deprecate Zaqar as well ?
AFAIK Zaqar is a part of deployment method by Mistral,
As I've never seen users have Zaqar deployed in overcloud
I think we are good to deprecate it following Mistral.

On Fri, Oct 9, 2020 at 1:38 AM Wesley Hayutin <whayutin at redhat.com> wrote:

> +1
>
> On Thu, Oct 8, 2020 at 8:04 AM John Fulton <johfulto at redhat.com> wrote:
>
>> On Thu, Oct 8, 2020 at 9:47 AM Marios Andreou <marios at redhat.com> wrote:
>> > On Thu, Oct 8, 2020 at 3:34 PM 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?
>> >
>> >
>> > +1 - at least for tripleo CI we aren't running mistral on anything
>> newer than train
>>
>> +1  In main branch (to be Victoria) Ceph and Derived parameters are
>> not using Mistral anymore.
>>
>> >
>> >
>> >
>> >>
>> >>
>> >> Thanks,
>> >> --
>> >> Emilien Macchi
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201009/3349cdd3/attachment.html>