Open Stack

Hey everyone,

@piotr suggested here dropping marathon as well
https://review.opendev.org/c/openstack/magnum/+/821213 but since it's been
used by dcos, does it make sense to remove it as well along with mesos?

Maybe the correct question here would be: should we be dropping dcos as
well? If so, maybe a new PR for would be more suitable.

Regards,
Guilherme Steinmuller

On Wed, Dec 8, 2021 at 5:42 PM Guilherme Steinmüller <
gsteinmuller at vexxhost.com> wrote:

> Hey there,
>
> I took the liberty to kick off a patch to start the mesos code removal
> [1]. It's a lot of lines of code and files removed lol
>
> But I believe it's going to be an improvement on the current code as mesos
> is not really being used out there.
>
> [1] https://review.opendev.org/c/openstack/magnum/+/821124
>
> Regards
> Guilherme Steinmuller
>
> On Wed, Dec 8, 2021 at 11:54 AM Tobias Urdin <tobias.urdin at binero.com>
> wrote:
>
>> Hello Mohammed,
>>
>> I agree, we should cleanup things that has been broken for years now.
>>
>> Best regards
>> Tobias
>>
>> On 8 Dec 2021, at 15:35, Spyros Trigazis <strigazi at gmail.com> wrote:
>>
>> Hello Mohammed,
>>
>> I do not think anyone is interested in it anymore, we could just drop it.
>> Even if resources are left behind they can be cleaned up with heat/other
>> openstack APIs.
>>
>> Spyros
>>
>> On Sat, Dec 4, 2021 at 11:53 AM Mohammed Naser <mnaser at vexxhost.com>
>> wrote:
>>
>>> Hi there,
>>>
>>> Does it make sense for us to drop the Mesos driver code from the code
>>> base?
>>>
>>> I don't know of anyone that actually uses it and I believe it's likely
>>> not been tested for years.
>>>
>>> Mohammed
>>>
>>> --
>>> Mohammed Naser
>>> VEXXHOST, Inc.
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220131/789a15d1/attachment.htm>