Hi,

Two cycles ? I thought that most of work was implemented by vexxhost ? https://github.com/vexxhost/magnum-cluster-api Do you have reviews somewhere if you are working on ClusterAPI ?

Thanks

On 4/18/23 13:53, Jake Yip wrote:

HI Takashi,

Sorry I missed replying.

On 30/3/2023 1:46 pm, Takashi Kajinami wrote:

...

1. Magnum

It seems SoftwareDeployment is used by k8s_fedora_atomic_v1 driver but I'm not too sure whether this driver is still supported, because Fedora Atomic was EOLed a while ago, right ?

No It's still in the main k8s_fedora_coreos_v1 driver. It basically is how everything is set up, so we still depend on this greatly for now.

We are also working on a ClusterAPI driver who will bypass heat altogether. We hope to get it working within two cycles, then we can remove k8s_fedora_coreos_v1 together, possibly within another two cycles.

Thanks!

Regards Jake

Hi,

For tacker, we've agreed to drop SoftwareDeployment in tacker and heat-translator as the result of discussion in our team last week. Sorry for the late notice.

Thanks, Yasufumi

On 2023/04/26 19:07, Jake Yip wrote:

Hi,

Yes, there are a couple of WIP reviews in magnum by John.

Regards, Jake

On 18/4/2023 11:16 pm, Michal Arbet wrote:

...

Hi,

Two cycles ? I thought that most of work was implemented by vexxhost ? https://github.com/vexxhost/magnum-cluster-api Do you have reviews somewhere if you are working on ClusterAPI ?

Thanks

On 4/18/23 13:53, Jake Yip wrote:

...

HI Takashi,

Sorry I missed replying.

On 30/3/2023 1:46 pm, Takashi Kajinami wrote:

...

1. Magnum

It seems SoftwareDeployment is used by k8s_fedora_atomic_v1 driver but I'm not too sure whether this driver is still supported, because Fedora Atomic was EOLed a while ago, right ?

No It's still in the main k8s_fedora_coreos_v1 driver. It basically is how everything is set up, so we still depend on this greatly for now.

We are also working on a ClusterAPI driver who will bypass heat altogether. We hope to get it working within two cycles, then we can remove k8s_fedora_coreos_v1 together, possibly within another two cycles.

Thanks!

Regards Jake

-- Michal Arbet Openstack Engineer

Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic

+420 604 228 897 michal.arbet@ultimum.io _https://ultimum.io_

LinkedIn https://www.linkedin.com/company/ultimum-technologies | Twitter https://twitter.com/ultimumtech | Facebook https://www.facebook.com/ultimumtechnologies/timeline

Rabi pointed out one quite important point which I missed when I wrote the previous email.

So I noticed we do not run any tests to evaluate SoftwareDeployment/Config in heat CI.

We have a scenario test but it was disabled when we migrated our jobs to zuul v3(during Ussuri) and we have had no test coverage since then.

https://github.com/openstack/heat/commit/c8d1a9f901aa7b956c055668532967fd342...

Since TripleO has removed usage of SoftwareConfig/Deployment a while ago and Magnum is also getting rid of it, we'd have no test coverage left.

Unfortunately currently resources around the heat project are quite small, and honestly I'm not too sure if anyone can work on adding the test coverage soon. We have to create a customized image with some toolings, as I earlier mentioned, but that has been kept as TODO for long.

So I'm looking for any volunteers to restore the test coverage in upstream CI so that we can test the feature, which is required for maintenance. If no one appears then we likely have to deprecate the feature before 2024.1, so that we can remove it in 2025.1, instead of keeping the feature untested and unmaintained.

On Wed, May 10, 2023 at 12:11 PM Takashi Kajinami tkajinam@redhat.com wrote:

(replying to the base message because there are a few separate threads going).

Thanks for these inputs and sorry for my late reply. So according to Jake Magnum still requires SoftwareDeployment/Config. I got one off-list reply from the user using the feature. Based on these feedbacks, we can keep the feature for now.

The main challenge with keeping this feature is that we have to maintain a specific image with additional tools installed. We can try our best to keep these maintained but if anyone can help maintaining the job/tools, test the features and share any test feedback, that is much appreciated.

On Thu, Mar 30, 2023 at 11:46 AM Takashi Kajinami tkajinam@redhat.com wrote:

...

Hello,

We discussed this briefly in the past thread where we discussed maintenance of os-*-agent repos, and also talked about this topic during Heat PTG, but I'd like to formalize the discussion to get a clear agreement.

Heat has been supporting SoftwareDeployment resources to configure software in instances using some agents such as os-collect-config[1]. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.ht...

This feature was initially developed to be used by TripleO (IIUC), but TripleO is retired now and we are losing the first motivation to maintain the feature. # Even TripleO replaced most of its usage of softwaredeployment by config-download lately.

Because the heat project team has drunk dramatically recently, we'd like to put more focus on core features. For that aim we are now wondering if we can deprecate and remove this feature, and would like to hear from anyone who has any concerns about this.

Quickly looking through the repos, it seems currently Magnum and Tacker are using SoftwareDeployment, and it'd be nice especially if we can understand their current requirements.

1. Magnum

It seems SoftwareDeployment is used by k8s_fedora_atomic_v1 driver but I'm not too sure whether this driver is still supported, because Fedora Atomic was EOLed a while ago, right ?

2. Tacker

SoftwareDeployment can be found in only test code in the tacker repo. We have some references kept in heat-translator which look related to TOSCA templates.

Thank you, Takashi Kajinami