Re: [TripleO] Last maintained release of TripleO is Wallaby
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Best Ümit Seren
From: James Slagle james.slagle@gmail.com Date: Wednesday, 8. February 2023 at 18:38 To: OpenStack Discuss openstack-discuss@lists.openstack.org Subject: [TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
-- -- James Slagle --
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June.
(Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans)
Thanks, Eoghan
Best
Ümit Seren
*From: *James Slagle james.slagle@gmail.com *Date: *Wednesday, 8. February 2023 at 18:38 *To: *OpenStack Discuss openstack-discuss@lists.openstack.org *Subject: *[TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
--
-- James Slagle
Hi,
Please, can I ask what is the future of tripleo-image-elements ? https://github.com/openstack/tripleo-image-elements
Thank you 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 https://ultimum.io/*
LinkedIn https://www.linkedin.com/company/ultimum-technologies | Twitter https://twitter.com/ultimumtech | Facebook https://www.facebook.com/ultimumtechnologies/timeline
čt 9. 2. 2023 v 12:26 odesílatel Eoghan Glynn eglynn@redhat.com napsal:
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June.
(Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans)
Thanks, Eoghan
Best
Ümit Seren
*From: *James Slagle james.slagle@gmail.com *Date: *Wednesday, 8. February 2023 at 18:38 *To: *OpenStack Discuss openstack-discuss@lists.openstack.org *Subject: *[TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
--
-- James Slagle
On Thu, Feb 9, 2023 at 8:56 AM Michal Arbet michal.arbet@ultimum.io wrote:
Hi,
Please, can I ask what is the future of tripleo-image-elements ? https://github.com/openstack/tripleo-image-elements
This repo is part of TripleO. I would not anticipate the current TripleO team maintaining tripleo-image-elements past Wallaby. If any of the elements are deemed general purpose enough, they could be added to diskimage-builder[1] instead. I think that's the most logical place for them.
[1] https://github.com/openstack/diskimage-builder/tree/master/diskimage_builder...
Thank you 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 | Twitter | Facebook
čt 9. 2. 2023 v 12:26 odesílatel Eoghan Glynn eglynn@redhat.com napsal:
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June.
(Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans)
Thanks, Eoghan
Best
Ümit Seren
From: James Slagle james.slagle@gmail.com Date: Wednesday, 8. February 2023 at 18:38 To: OpenStack Discuss openstack-discuss@lists.openstack.org Subject: [TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
--
-- James Slagle
Where can I find the video of that presentation? On Thursday, February 9, 2023, 06:28:42 AM EST, Eoghan Glynn eglynn@redhat.com wrote:
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June. (Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans) Thanks,Eoghan
Best
Ümit Seren
From:James Slagle james.slagle@gmail.com Date: Wednesday, 8. February 2023 at 18:38 To: OpenStack Discuss openstack-discuss@lists.openstack.org Subject: [TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
Openinfra has the videos on their youtube channel.
https://www.youtube.com/@OpenStackFoundation
Good channel to sub too if you haven't
Cheers
On Thu, Feb 9, 2023 at 10:10 AM Albert Braden ozzzo@yahoo.com wrote:
Where can I find the video of that presentation? On Thursday, February 9, 2023, 06:28:42 AM EST, Eoghan Glynn < eglynn@redhat.com> wrote:
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June.
(Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans)
Thanks, Eoghan
Best
Ümit Seren
*From:*James Slagle james.slagle@gmail.com *Date: *Wednesday, 8. February 2023 at 18:38 *To: *OpenStack Discuss openstack-discuss@lists.openstack.org *Subject: *[TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
--
-- James Slagle
I believe this[0] is the video you're looking for. I located it on the Foundation's youtube channel[1].
-Julia
[0]: https://www.youtube.com/watch?v=Vt64p73VdIQ [1]: https://www.youtube.com/@OpenStackFoundation
On Thu, Feb 9, 2023 at 7:09 AM Albert Braden ozzzo@yahoo.com wrote:
Where can I find the video of that presentation? On Thursday, February 9, 2023, 06:28:42 AM EST, Eoghan Glynn < eglynn@redhat.com> wrote:
On Thu, Feb 9, 2023 at 6:18 AM Ümit Seren uemit.seren@gmail.com wrote:
What are the implications with regards to RDO and RHOSP which are based on TripleO ? Will they move to a different deployment method or will also development seize after Zed ?
Yes, the team at Red Hat is working on a different deployment method for our product, specifically by hosting the control plane natively on OpenShift while managing the dataplane with pure Ansible. We talked about this strategy a bit at the Open Infra Summit in Berlin last June.
(Since you asked, I'm answering ... but I don't want to derail what should be a community-oriented discussion about TripleO by conflating it with our future product plans)
Thanks, Eoghan
Best
Ümit Seren
*From:*James Slagle james.slagle@gmail.com *Date: *Wednesday, 8. February 2023 at 18:38 *To: *OpenStack Discuss openstack-discuss@lists.openstack.org *Subject: *[TripleO] Last maintained release of TripleO is Wallaby
The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment.
The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust.
TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan.
--
-- James Slagle
On 2023-02-09 15:02:14 +0000 (+0000), Albert Braden wrote:
Where can I find the video of that presentation?
[...]
If it was recorded, you should hopefully be able to find it in this list:
https://www.openstack.org/videos/summits/berlin-2022
I haven't watched it, but my best guess would be this one:
https://www.openstack.org/videos/summits/berlin-2022/OpenStack-brings-Kubern...
On 2023-02-09 15:50:57 +0000 (+0000), Jeremy Stanley wrote: [...]
I haven't watched it, but my best guess would be this one:
[...]
Scratch that, just saw Julia's reply and her guess looks far more likely.
participants (8)
-
Albert Braden
-
Eoghan Glynn
-
James Slagle
-
Jeremy Stanley
-
Julia Kreger
-
Michael Knox
-
Michal Arbet
-
Ümit Seren