Open Stack

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/c8d1a9f901aa7b956c055668532967fd34202fe4#diff-52a39eb793da5f54635afbdceeeddc16482afb9ab022d981ebea7743dc81dc8cR446

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 at 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 at 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.html#software-deployment-resources
>>
>> 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
>>
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230510/5362591b/attachment.htm>