Hi Thomas,

The issue is that the StackHPC has gone into a fundamentally different path: using Helm charts with manual resources.  We've taken the more modern path which will be the future of CAPI which is managed topologies.

I have not seen an interest in them wanting to explore our path, because they use these Helm charts in their own product (Azimuth?) and want to use them for that AND th Magnum driver.  We have no interest in using plain Helm charts because we're heavily invested into managed topologies feature which has been in use for many months now.

So it's a matter of choice/selection/decision, and I believe we have the better option here. 

tl;dr: we've taken two approaches, ours is more modern and compatible with future state of things.  the other driver relies on basic Helm charts that were built for some other use case and being retrofitted for this case.

Thanks
Mohammed
From: Thomas Goirand <zigo@debian.org>
Sent: February 27, 2024 10:26 AM
To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: Re: [magnum] Dropping default Cluster API driver
 
[You don't often get email from zigo@debian.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

On 2/21/24 21:33, Dale Smith wrote:
> However, I'm not sure I'm in support of asking another driver to be
> relocated and not contributed when it wants to be.

As a user of Magnum, I very much would prefer it "batteries included",
with the driver in-tree.

As a package maintainer, I would very much prefer *not* to have to
maintain 2 out-of-tree driver packages.

It's really a shame if this is happening for social reasons.

The best possible outcome would be one single driver maintain in
collaboration between StackHPC and Vexxhost, in-tree in Magnum,
maintained in the OpenStack community.

Please make this happen...

Cheers,

Thomas Goirand (zigo)