+1. Would be good to get some feedback on how frequently these are used outside of older releases of TripleO though.
Maybe move them to Heat to maintain stable with the end goal of deprecating and removing if nothing and no one else is using them. But any feedback on usage of these projects would be appreciated and helpful in making that decision.
PTG topic proposal?
Brendan
On 22 Feb 2023, at 3:27 pm, Takashi Kajinami <tkajinam@redhat.com> wrote:
jfyi; I've also pushed a change[1] to the governance repository.
On Wed, Feb 22, 2023 at 10:43 AM Takashi Kajinami <tkajinam@redhat.com> wrote:
>
> Hello,
>
>
> tl;dr
> Can we move os-(apply|collect|refresh)-config to Heat's governance ?
>
> Currently we have the following three repositories maintained under the TripleO's governance.
> - os-apply-config
> - os-collect-config
> - os-refresh-config
>
+1
> These three are the agents to run deployment tasks according to SoftwareDeployment resources[1]
> in Heat. Historically the feature was developed to be used by TripleO, and these agents have been
> maintained by the TripleO team. However these repositories will be retired as TripleO is being retired[2].
>
> Because the feature itself should be still maintained in heat (especially for stable branches), I'd like
> to propose migrating these repositories to Heat's governance.
>
> I noticed the repository does not have any stable branches after stable/victoria so we likely have to
> create stable/wallaby and beyond but I'll leave this topic for follow-up.
>
> [1]
https://docs.openstack.org/heat/latest/template_guide/software_deployment.html#software-deployment-resources
> [2]
https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032083.html
>
> Thank you,
> Takashi Kajinami
--
Regards,
Rabi Mishra