[heat][tripleo] os-apply-config os-refresh-config os-collect-config project governance
Hello Heat team o/
as discussed in the thread at [1] TripleO is no longer using os-collect-config, os-refresh-config and os-apply-config as part of the OpenStack deployment. As such we are considering moving these repos to the independent release model.
However as pointed out in [1] it seems that Heat is still using these - documented at [2]. Is the Heat community interested in taking over the ownership of these? To be clear what the proposal here is, I posted [3] - i.e. move these projects under the Heat governance.
Thanks for your time, thoughts and comments on this, either here or in [3]. If you are NOT interested in owning these then we will likely move them to independent, or possibly even unmaintained/eol (in due course).
regards, marios
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019751.h... [2] https://docs.openstack.org/heat/latest/template_guide/software_deployment.ht... [3] https://review.opendev.org/c/openstack/governance/+/770285
On Tue, Jan 12, 2021 at 7:47 AM Marios Andreou marios@redhat.com wrote:
Hello Heat team o/
as discussed in the thread at [1] TripleO is no longer using os-collect-config, os-refresh-config and os-apply-config as part of the OpenStack deployment. As such we are considering moving these repos to the independent release model.
However as pointed out in [1] it seems that Heat is still using these - documented at [2]. Is the Heat community interested in taking over the ownership of these? To be clear what the proposal here is, I posted [3] - i.e. move these projects under the Heat governance.
Thanks for your time, thoughts and comments on this, either here or in [3]. If you are NOT interested in owning these then we will likely move them to independent, or possibly even unmaintained/eol (in due course).
I realized a possible wrinkle with moving these to Heat governance. TripleO still relies on the stable/train branches given these projects are still used in train, and there exists a possibility that TripleO cores may need to backport patch(es) to the train branch in these projects.
Le mar. 12 janv. 2021 à 14:26, James Slagle james.slagle@gmail.com a écrit :
On Tue, Jan 12, 2021 at 7:47 AM Marios Andreou marios@redhat.com wrote:
Hello Heat team o/
as discussed in the thread at [1] TripleO is no longer using os-collect-config, os-refresh-config and os-apply-config as part of the OpenStack deployment. As such we are considering moving these repos to the independent release model.
However as pointed out in [1] it seems that Heat is still using these - documented at [2]. Is the Heat community interested in taking over the ownership of these? To be clear what the proposal here is, I posted [3] - i.e. move these projects under the Heat governance.
Thanks for your time, thoughts and comments on this, either here or in [3]. If you are NOT interested in owning these then we will likely move them to independent, or possibly even unmaintained/eol (in due course).
I realized a possible wrinkle with moving these to Heat governance. TripleO still relies on the stable/train branches given these projects are still used in train, and there exists a possibility that TripleO cores may need to backport patch(es) to the train branch in these projects.
Maybe adding some tripleo cores as stable maintainers could help the both teams to converge, thoughts? Heat could be more the focused on the current series and tripleo cores could propose fixes and lead backports to stable branches.
--
-- James Slagle
On Tue, Jan 12, 2021 at 6:58 PM James Slagle james.slagle@gmail.com wrote:
On Tue, Jan 12, 2021 at 7:47 AM Marios Andreou marios@redhat.com wrote:
Hello Heat team o/
as discussed in the thread at [1] TripleO is no longer using os-collect-config, os-refresh-config and os-apply-config as part of the OpenStack deployment. As such we are considering moving these repos to the independent release model.
However as pointed out in [1] it seems that Heat is still using these - documented at [2]. Is the Heat community interested in taking over the ownership of these? To be clear what the proposal here is, I posted [3] - i.e. move these projects under the Heat governance.
Thanks for your time, thoughts and comments on this, either here or in [3]. If you are NOT interested in owning these then we will likely move them to independent, or possibly even unmaintained/eol (in due course).
I realized a possible wrinkle with moving these to Heat governance. TripleO still relies on the stable/train branches given these projects are still used in train, and there exists a possibility that TripleO cores may need to backport patch(es) to the train branch in these projects.
I thought we switched to config-download by default from stable/rocky and disabled os-collect-config[1]. Not sure if anyone uses it beyond that with TripleO. Looking at the number of functional changes backported to stable/queens (AFICS only 3 of them)[2], probably it won't be a major bottleneck, assuming the heat community wants to own it.
[1] https://review.opendev.org/plugins/gitiles/openstack/tripleo-puppet-elements... [2] https://bit.ly/3qeTqX2
--
-- James Slagle
On Tue, Jan 12, 2021 at 9:32 AM Rabi Mishra ramishra@redhat.com wrote:
On Tue, Jan 12, 2021 at 6:58 PM James Slagle james.slagle@gmail.com wrote:
On Tue, Jan 12, 2021 at 7:47 AM Marios Andreou marios@redhat.com wrote:
Hello Heat team o/
as discussed in the thread at [1] TripleO is no longer using os-collect-config, os-refresh-config and os-apply-config as part of the OpenStack deployment. As such we are considering moving these repos to the independent release model.
However as pointed out in [1] it seems that Heat is still using these - documented at [2]. Is the Heat community interested in taking over the ownership of these? To be clear what the proposal here is, I posted [3] - i.e. move these projects under the Heat governance.
Thanks for your time, thoughts and comments on this, either here or in [3]. If you are NOT interested in owning these then we will likely move them to independent, or possibly even unmaintained/eol (in due course).
I realized a possible wrinkle with moving these to Heat governance. TripleO still relies on the stable/train branches given these projects are still used in train, and there exists a possibility that TripleO cores may need to backport patch(es) to the train branch in these projects.
I thought we switched to config-download by default from stable/rocky and disabled os-collect-config[1]. Not sure if anyone uses it beyond that with TripleO. Looking at the number of functional changes backported to stable/queens (AFICS only 3 of them)[2], probably it won't be a major bottleneck, assuming the heat community wants to own it.
You're right. I meant to say queens instead of train.
participants (4)
-
Herve Beraud
-
James Slagle
-
Marios Andreou
-
Rabi Mishra