[TripleO] Removal of TripleO Zed Integration and Component Lines
Hello All,
Removal of TripleO Zed Integration and Component Lines
Per the decision to not maintain TripleO after the Zed release [1], the Zed integration and component lines are being removed in the following patches:
https://review.rdoproject.org/r/c/config/+/48073
https://review.rdoproject.org/r/c/config/+/48074
https://review.rdoproject.org/r/c/rdo-jobs/+/48075
To be clear, please note that following these changes, the gate for stable/zed TripleO repos will no longer be updated or maintained. Per the earlier communications, there should be no more patches submitted for stable/zed TripleO repos, and any backports will go to stable/wallaby or stable/train.
The last promoted release of Zed through TripleO is: https://trunk.rdoproject.org/centos9-zed/current-tripleo/delorean.repo (hash:61828177e94d5f179ee0885cf3eee102), which was promoted on 05/15/2023.
The Ceph promotion lines related to Zed are also removed in the above patches.
Check/gate testing for the master branch is in process of being removed as well (https://review.opendev.org/c/openstack/tripleo-ci/+/882759).
[1] https://review.opendev.org/c/openstack/governance/+/878799
Hi Ronelle,
It's actually not what was discussed and decided.
After Zed, means starting from Antelope, which is the release after Zed. Zed release should still be able to accept patches and interested parties are allowed to contribute to the branch until it goes to the Extended Maintenance according to the release schedule [1].
So there can be no active contributions to the Zed release, but CI or gating should not be dropped on purpose to prevent any interested party on contribute to the branch.
[1] https://releases.openstack.org/
вт, 16 мая 2023 г., 12:53 Ronelle Landy rlandy@redhat.com:
Hello All,
Removal of TripleO Zed Integration and Component Lines
Per the decision to not maintain TripleO after the Zed release [1], the Zed integration and component lines are being removed in the following patches:
https://review.rdoproject.org/r/c/config/+/48073 https://review.rdoproject.org/r/c/config/+/48074 https://review.rdoproject.org/r/c/rdo-jobs/+/48075To be clear, please note that following these changes, the gate for stable/zed TripleO repos will no longer be updated or maintained. Per the earlier communications, there should be no more patches submitted for stable/zed TripleO repos, and any backports will go to stable/wallaby or stable/train.
The last promoted release of Zed through TripleO is: https://trunk.rdoproject.org/centos9-zed/current-tripleo/delorean.repo (hash:61828177e94d5f179ee0885cf3eee102), which was promoted on 05/15/2023.
The Ceph promotion lines related to Zed are also removed in the above patches.
Check/gate testing for the master branch is in process of being removed as well (https://review.opendev.org/c/openstack/tripleo-ci/+/882759).
[1] https://review.opendev.org/c/openstack/governance/+/878799
On 2023-05-16 19:15:23 +0200 (+0200), Dmitriy Rabotyagov wrote:
It's actually not what was discussed and decided.
After Zed, means starting from Antelope, which is the release after Zed. Zed release should still be able to accept patches and interested parties are allowed to contribute to the branch until it goes to the Extended Maintenance according to the release schedule [1].
So there can be no active contributions to the Zed release, but CI or gating should not be dropped on purpose to prevent any interested party on contribute to the branch.
[...]
Just to be clear, the concern you're raising is over the tripleo-ci change[*] that's removing jobs in the upstream CI for the stable/zed branch?
Also worth noting, it looks like these jobs skipped multiple releases previously, since they're currently only run for stable/train, stable/wallaby and stable/zed.
[*] https://review.opendev.org/882759
On Tue, May 16, 2023 at 1:18 PM Dmitriy Rabotyagov noonedeadpunk@gmail.com wrote:
Hi Ronelle,
It's actually not what was discussed and decided.
After Zed, means starting from Antelope, which is the release after Zed. Zed release should still be able to accept patches and interested parties are allowed to contribute to the branch until it goes to the Extended Maintenance according to the release schedule [1].
So there can be no active contributions to the Zed release, but CI or gating should not be dropped on purpose to prevent any interested party on contribute to the branch.
I feel the wording "on purpose to prevent..." is a mis-characterization of the intent.
The discussion resulted in no volunteers or contributors willing to maintain TripleO Zed. The outcome was to consider it 'supported but no maintainers'[1]. Now, I can't really describe how that works in actual practice. Who is supporting it if there are no maintainers? Are there a group of individuals somewhere that consider themselves the supporters of TripleO Zed, but not the maintainers? To the best of my knowledge, no, there is not.
To be clear, this patch https://review.opendev.org/c/openstack/tripleo-ci/+/882759 is for zed jobs on branchless CI repos. As there are no maintainers for Zed, if they start failing, we will need to mark them non-voting if we don't remove them. The intent with removing them was to signal the reality of the situation with what is actually still being maintained. And by maintained, I mean people actually working on it.
If you would instead prefer that those jobs continue to exist, then ok. I don't understand the status of them at this time, and I don't expect them to stay passing (if they are). I also disagree that the absence of those jobs prevents anyone from submitting a patch to TripleO Zed.
The integration lines promoted through RDO results in repositories of rpm's. When those are torn down (via the rdoproject.org patches), the content will still exist, but it will not be updated in a way that TripleO typically expects. The CI and gate jobs that run on TripleO patches proposed to stable/zed of branched TripleO repos may or may not continue to pass as a result of stale content.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032663.ht...
[1] https://releases.openstack.org/
вт, 16 мая 2023 г., 12:53 Ronelle Landy rlandy@redhat.com:
Hello All,
Removal of TripleO Zed Integration and Component Lines
Per the decision to not maintain TripleO after the Zed release [1], the Zed integration and component lines are being removed in the following patches:
https://review.rdoproject.org/r/c/config/+/48073 https://review.rdoproject.org/r/c/config/+/48074 https://review.rdoproject.org/r/c/rdo-jobs/+/48075To be clear, please note that following these changes, the gate for stable/zed TripleO repos will no longer be updated or maintained. Per the earlier communications, there should be no more patches submitted for stable/zed TripleO repos, and any backports will go to stable/wallaby or stable/train.
The last promoted release of Zed through TripleO is: https://trunk.rdoproject.org/centos9-zed/current-tripleo/delorean.repo (hash:61828177e94d5f179ee0885cf3eee102), which was promoted on 05/15/2023.
The Ceph promotion lines related to Zed are also removed in the above patches.
Check/gate testing for the master branch is in process of being removed as well (https://review.opendev.org/c/openstack/tripleo-ci/+/882759).
[1] https://review.opendev.org/c/openstack/governance/+/878799
-- -- James Slagle --
On Tue, May 16, 2023 at 4:32 PM James Slagle james.slagle@gmail.com wrote:
On Tue, May 16, 2023 at 1:18 PM Dmitriy Rabotyagov noonedeadpunk@gmail.com wrote:
Hi Ronelle,
It's actually not what was discussed and decided.
After Zed, means starting from Antelope, which is the release after Zed. Zed release should still be able to accept patches and interested
parties are allowed to contribute to the branch until it goes to the Extended Maintenance according to the release schedule [1].
So there can be no active contributions to the Zed release, but CI or
gating should not be dropped on purpose to prevent any interested party on contribute to the branch.
I feel the wording "on purpose to prevent..." is a mis-characterization of the intent.
The discussion resulted in no volunteers or contributors willing to maintain TripleO Zed. The outcome was to consider it 'supported but no maintainers'[1]. Now, I can't really describe how that works in actual practice. Who is supporting it if there are no maintainers? Are there a group of individuals somewhere that consider themselves the supporters of TripleO Zed, but not the maintainers? To the best of my knowledge, no, there is not.
To be clear, this patch https://review.opendev.org/c/openstack/tripleo-ci/+/882759 is for zed jobs on branchless CI repos. As there are no maintainers for Zed, if they start failing, we will need to mark them non-voting if we don't remove them. The intent with removing them was to signal the reality of the situation with what is actually still being maintained. And by maintained, I mean people actually working on it.
If you would instead prefer that those jobs continue to exist, then ok. I don't understand the status of them at this time, and I don't expect them to stay passing (if they are). I also disagree that the absence of those jobs prevents anyone from submitting a patch to TripleO Zed.
The integration lines promoted through RDO results in repositories of rpm's. When those are torn down (via the rdoproject.org patches), the content will still exist, but it will not be updated in a way that TripleO typically expects. The CI and gate jobs that run on TripleO patches proposed to stable/zed of branched TripleO repos may or may not continue to pass as a result of stale content.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032663.ht...
James, thanks for the fuller explanation.
As we understand, removing CI branchful jobs should not prevent anyone committing patches to the stable/zed branch. We did not even remove any testing from TripleO related repos that have a stable/zed branch - for example: https://github.com/openstack/tripleo-heat-templates/blob/stable/zed/zuul.d/l... stil has templates included.
What we are proposing to remove is just forcing stable/zed branch testing on changes to CI repos - which are branchless.
[1] https://releases.openstack.org/
вт, 16 мая 2023 г., 12:53 Ronelle Landy rlandy@redhat.com:
Hello All,
Removal of TripleO Zed Integration and Component Lines
Per the decision to not maintain TripleO after the Zed release [1], the
Zed integration and component lines are being removed in the following patches:
https://review.rdoproject.org/r/c/config/+/48073 https://review.rdoproject.org/r/c/config/+/48074 https://review.rdoproject.org/r/c/rdo-jobs/+/48075To be clear, please note that following these changes, the gate for
stable/zed TripleO repos will no longer be updated or maintained. Per the earlier communications, there should be no more patches submitted for stable/zed TripleO repos, and any backports will go to stable/wallaby or stable/train.
The last promoted release of Zed through TripleO is: https://trunk.rdoproject.org/centos9-zed/current-tripleo/delorean.repo
(hash:61828177e94d5f179ee0885cf3eee102),
which was promoted on 05/15/2023.
The Ceph promotion lines related to Zed are also removed in the above
patches.
Check/gate testing for the master branch is in process of being removed
as well (https://review.opendev.org/c/openstack/tripleo-ci/+/882759).
[1] https://review.opendev.org/c/openstack/governance/+/878799
--
-- James Slagle
On 2023-05-16 16:31:50 -0400 (-0400), James Slagle wrote: [...]
I feel the wording "on purpose to prevent..." is a mis-characterization of the intent.
[...]
On further discussion in #openstack-tc, it appears some of the concern was due to the phrase "there should be no more patches submitted for stable/zed TripleO repos" and the "should" there was interpreted as implying that the prior contributors were doing this in order to disallow participation by future contributors who might want to do so. It seems like this was not actually the intent you were trying to convey, and was an unfortunate misreading. If you had said that further patches for that branch are not expected, or that you personally wouldn't be submitting patches for that branch, I doubt the reaction would have been so strong.
On Tue, May 16, 2023 at 5:45 PM Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-05-16 16:31:50 -0400 (-0400), James Slagle wrote: [...]
I feel the wording "on purpose to prevent..." is a mis-characterization of the intent.
[...]
On further discussion in #openstack-tc, it appears some of the concern was due to the phrase "there should be no more patches submitted for stable/zed TripleO repos" and the "should" there was interpreted as implying that the prior contributors were doing this in order to disallow participation by future contributors who might want to do so. It seems like this was not actually the intent you were trying to convey, and was an unfortunate misreading. If you had said that further patches for that branch are not expected, or that you personally wouldn't be submitting patches for that branch, I doubt the reaction would have been so strong.
Fair enough. Given the circumstances, I wouldn't personally encourage anyone to contribute patches to Zed given there are no reviewers, degraded CI, and degraded content. To me, that is a pretty big signal that you probably don't want to submit code there as it's not going to end up how you expect.
I certainly defer to however the TC wants to phrase it for these future contributors.
-- -- James Slagle --
On 2023-05-16 18:27:47 -0400 (-0400), James Slagle wrote: [...]
Fair enough. Given the circumstances, I wouldn't personally encourage anyone to contribute patches to Zed given there are no reviewers, degraded CI, and degraded content. To me, that is a pretty big signal that you probably don't want to submit code there as it's not going to end up how you expect.
I certainly defer to however the TC wants to phrase it for these future contributors.
Well yes, obviously (to me at any rate) random drive-by contributions would be pointless, and any group of people interested in resuming actual development on it would need to be ready to also take over maintenance responsibilities, do code review, fix CI jobs, et cetera.
Odds of that happening are slim, but it can't be ruled out. After all, it happened before... TripleO was originally started by HPCloud dev teams.
On Wed, May 17, 2023 at 12:47 AM Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-05-16 16:31:50 -0400 (-0400), James Slagle wrote: [...]
I feel the wording "on purpose to prevent..." is a mis-characterization of the intent.
[...]
On further discussion in #openstack-tc, it appears some of the concern was due to the phrase "there should be no more patches submitted for stable/zed TripleO repos" and the "should" there was interpreted as implying that the prior contributors were doing this in order to disallow participation by future contributors who might want to do so. It seems like this was not actually the intent you were trying to convey, and was an unfortunate misreading. If you had said that further patches for that branch are not expected, or that you personally wouldn't be submitting patches for that branch, I doubt the reaction would have been so strong.
This has been well explained by James and Ronelle, but having worked with Ronelle on that announcement and since the sentence in question was added on my suggestion ("there should be no more patches submitted..." ) I feel a responsibility to clarify the intent behind it.
The intent is to signal that after this point there will be degraded CI for all TripleO repos' stable/zed branch because it will no longer be maintained by the team that has been doing so until now. The gate will break and your patches will be blocked from merging unless you skip jobs or start fixing them (we have not removed the job definitions or zuul layouts but they are going to fall into disrepair). For this reason, "there should be no more patches submitted for stable/zed TripleO repos".
thanks all for helping to clarify and my apologies for the concerns this raised - in retrospect the wording could been expanded a little to make it clearer,
regards, marios
-- Jeremy Stanley
participants (5)
-
Dmitriy Rabotyagov
-
James Slagle
-
Jeremy Stanley
-
Marios Andreou
-
Ronelle Landy