[rdo-dev] Re: Plans in RDO for TripleO deprecation
On Tue, Feb 21, 2023 at 8:57 PM Steve Baker wrote: > > I see os-collect-config/os-apply-config/os-refresh-config are in the retired > list. > > Package openstack-heat-agents are coupled with these 3 packages, as one of > the agent options, and for bootstrap on a provisioned host. There may be RDO > community usage of these packages independent of TripleO. > > Can these be moved to non-tripleo openstack projects, along with > openstack-heat-agents? > Sure, then I think it makes sense to add os-collect-config/os-apply-config/os-refresh-config to common components together with openstack-heat-agents. I've move them in the etherpad. Thanks > On 22/02/23 04:30, Alfredo Moralejo Alonso wrote: > > Hi, > > As communicated in an openstack-discuss thread [1] the TripleO team is > willing to deprecate master and Zed branches of TripleO repos. While > the process for Zed is still under discussion with TC [2], there will > not be new releases for Antelope and following releases. In the last > meeting of RDO we discussed how to manage this change in RDO [3], and > this is our proposal. > > TripleO packages in RDO releases > > - We will maintain TripleO packages in RDO in RDO-Trunk master until > the content of the master branch is removed. According to the info > provided by TripleO CI team, jobs for the master branch will keep > running for some time. > - Zed release is under discussion. We will follow the same approach as > for the master branch and remove the packages from RDO Trunk once the > branches are removed. We'll keep them if they stay in Extented > Maintenance. > - For Antelope release, which is under preparation for GA, we will not > include TripleO packages in CloudSIG official repos. We will also > remove them rpm RDO Trunk once we have confirmation from the TripleO > CI team that they don't need it anymore (or with master branch removal > at latest) > > Currently, TripleO component includes 102 packages but not all of them > are TripleO specific: > > - Non-tripleo puppet modules: we will maintain those in a new > component "puppet". > - Some packages for OpenStack services Heat, Zaqar and Mistral. We > need to look for new components for those, would common be a good fit? > - Non-TripleO ansible roles: are those used out of TripleO? I guess > not, but I'm willing to get feedback from RDO users about what may be > useful so that we can move it to another component > - TripleO packages. To be retired. If any package can be useful for > any other deployment tool, those may be moved to the suitable > component too. > > You can find the entire list of packages in > https://review.rdoproject.org/etherpad/p/post-tripleo-proposal , feel > free to check it and provide any feedback there. > > RDO definition-of-done > > Since last releases, the release criteria for new releases of RDO has > been based on puppet-openstack-integration, packstack (which also > relies on OpenStack Puppet modules) and TripleO jobs results. > > This change forces us to adapt the RDO definition of done. In Antelope > the release criteria will be only based on the > puppet-openstack-integration and packstack jobs (8 jobs) Correct for > Antelope. Going forward, we will reevaluate this in future releases. > > We will continue refining this plan the next few weeks, please let us > know any doubt or suggestion that you may have on this thread, in #rdo > or in the weekly meetings (wed. 14:00 UTC in #rdo). > > Best regards, > > Alfredo > > [1] > https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032083.html > [2] > https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032238.html > [3] > https://meetings.opendev.org/meetings/rdo_meeting___2023_02_15/2023/rdo_meeting___2023_02_15.2023-02-15-14.03.log.html > ___ > dev mailing list -- dev@lists.rdoproject.org > To unsubscribe send an email to dev-le...@lists.rdoproject.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s > > ___ > dev mailing list -- dev@lists.rdoproject.org > To unsubscribe send an email to dev-le...@lists.rdoproject.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s ___ dev mailing list -- dev@lists.rdoproject.org To unsubscribe send an email to dev-le...@lists.rdoproject.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
[rdo-dev] Re: Plans in RDO for TripleO deprecation
On Wed, Feb 22, 2023 at 3:44 AM Takashi Kajinami wrote: > > I've left some comments in the etherpad. Several puppet modules were required > by TripleO > but are not used by p-o-i or packstack so can be removed. Thanks, i've just updated the etherpad with your feedback. > > Some ansible roles such as ansible-role-atos-hsm are maintained under > Barbican's governance > so the barbican team would have better insight. > > On Wed, Feb 22, 2023 at 4:57 AM Steve Baker wrote: >> >> I see os-collect-config/os-apply-config/os-refresh-config are in the retired >> list. >> >> Package openstack-heat-agents are coupled with these 3 packages, as one of >> the agent options, and for bootstrap on a provisioned host. There may be RDO >> community usage of these packages independent of TripleO. >> >> Can these be moved to non-tripleo openstack projects, along with >> openstack-heat-agents? > > I agree with this and these would be required to use SoftwareDeployment in > Heat outside of TripleO. > However we first have to move these repos to Heat's governance, otherwise > these will be retired. > I'll check with a few other cores and get back to you. > > >> >> On 22/02/23 04:30, Alfredo Moralejo Alonso wrote: >> >> Hi, >> >> As communicated in an openstack-discuss thread [1] the TripleO team is >> willing to deprecate master and Zed branches of TripleO repos. While >> the process for Zed is still under discussion with TC [2], there will >> not be new releases for Antelope and following releases. In the last >> meeting of RDO we discussed how to manage this change in RDO [3], and >> this is our proposal. >> >> TripleO packages in RDO releases >> >> - We will maintain TripleO packages in RDO in RDO-Trunk master until >> the content of the master branch is removed. According to the info >> provided by TripleO CI team, jobs for the master branch will keep >> running for some time. >> - Zed release is under discussion. We will follow the same approach as >> for the master branch and remove the packages from RDO Trunk once the >> branches are removed. We'll keep them if they stay in Extented >> Maintenance. >> - For Antelope release, which is under preparation for GA, we will not >> include TripleO packages in CloudSIG official repos. We will also >> remove them rpm RDO Trunk once we have confirmation from the TripleO >> CI team that they don't need it anymore (or with master branch removal >> at latest) >> >> Currently, TripleO component includes 102 packages but not all of them >> are TripleO specific: >> >> - Non-tripleo puppet modules: we will maintain those in a new >> component "puppet". >> - Some packages for OpenStack services Heat, Zaqar and Mistral. We >> need to look for new components for those, would common be a good fit? >> - Non-TripleO ansible roles: are those used out of TripleO? I guess >> not, but I'm willing to get feedback from RDO users about what may be >> useful so that we can move it to another component >> - TripleO packages. To be retired. If any package can be useful for >> any other deployment tool, those may be moved to the suitable >> component too. >> >> You can find the entire list of packages in >> https://review.rdoproject.org/etherpad/p/post-tripleo-proposal , feel >> free to check it and provide any feedback there. >> >> RDO definition-of-done >> >> Since last releases, the release criteria for new releases of RDO has >> been based on puppet-openstack-integration, packstack (which also >> relies on OpenStack Puppet modules) and TripleO jobs results. >> >> This change forces us to adapt the RDO definition of done. In Antelope >> the release criteria will be only based on the >> puppet-openstack-integration and packstack jobs (8 jobs) Correct for >> Antelope. Going forward, we will reevaluate this in future releases. >> >> We will continue refining this plan the next few weeks, please let us >> know any doubt or suggestion that you may have on this thread, in #rdo >> or in the weekly meetings (wed. 14:00 UTC in #rdo). >> >> Best regards, >> >> Alfredo >> >> [1] >> https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032083.html >> [2] >> https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032238.html >> [3] >> https://meetings.opendev.org/meetings/rdo_meeting___2023_02_15/2023/rdo_meeting___2023_02_15.2023-02-15-14.03.log.html >> ___ >> dev mailing list -- dev@lists.rdoproject.org >> To unsubscribe send an email to dev-le...@lists.rdoproject.org >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s >> >> ___ >> dev mailing list -- dev@lists.rdoproject.org >> To unsubscribe send an email to dev-le...@lists.rdoproject.org >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s > > ___ >
[rdo-dev] [rdo-users] [Meeting] RDO meeting minutes - 2023-02-22
== #rdo: RDO meeting - 2023-02-22 == Meeting started by jcapitao[m] at 14:01:41 UTC. The full logs are available athttps://meetings.opendev.org/meetings/rdo_meeting___2023_02_22/2023/rdo_meeting___2023_02_22.2023-02-22-14.01.log.html . Meeting summary --- * roll call (jcapitao[m], 14:01:59) * Retiring glare (jcapitao[m], 14:07:08) * LINK: https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/PVXIRURCMONAWLNSUN2PP6FDOROCDURQ/ (jcapitao[m], 14:07:18) * LINK: https://review.rdoproject.org/r/c/rdoinfo/+/47036 (jcapitao[m], 14:07:32) * Glare project and client have been retired during Antelope release preparation (jcapitao[m], 14:13:55) * Update about Antelope status (jcapitao[m], 14:14:41) * LINK: https://issues.redhat.com/browse/RDO-84 (jcapitao[m], 14:15:52) * LINK: https://review.rdoproject.org/etherpad/p/antelope-release-preparation (jcapitao[m], 14:16:02) * libs and clients projects are reqchecked (jcapitao[m], 14:16:59) * Antelope Trunk builder creation is still WIP, the bootstrapping process will start afterward (jcapitao[m], 14:19:48) * Plan for TripleO deprecation (jcapitao[m], 14:25:40) * LINK: https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/TCLLGNXWWPBV3JJKP77XBV2W6K4TP7S4/ (jcapitao[m], 14:25:54) * RDO will not include TripleO in CloudSIG Antelope repo (amoralej, 14:27:00) * we will continue shipping tripleo packages in RDO Trunk in master and zed while the upstream branches exist in EM, we'll remove once they are removed or EOLed (amoralej, 14:27:56) * For antelope we will keep them also building from master branches until removed (amoralej, 14:28:32) * once we retire tripleo packages we need to reorganize packages and components (amoralej, 14:30:08) * LINK: https://review.rdoproject.org/etherpad/p/post-tripleo-proposal (amoralej, 14:30:31) * a new package tcib has been requested for https://github.com/openstack-k8s-operators/tcib (amoralej, 14:36:50) * the proposed name for the new component is "podified", still open to discussion (amoralej, 14:41:38) * LINK: https://review.rdoproject.org/r/c/rdoinfo/+/47169 (amoralej, 14:44:25) * Next chair (jcapitao[m], 14:50:34) * Open Floor (jcapitao[m], 14:52:36) Meeting ended at 15:01:20 UTC. People present (lines said) --- * jcapitao[m] (64) * amoralej (52) * opendevmeet (7) * spotz (5) * karolinku[m] (4) * rdogerrit (1) * karolinku (0) Generated by `MeetBot`_ 0.1.4 ___ dev mailing list -- dev@lists.rdoproject.org To unsubscribe send an email to dev-le...@lists.rdoproject.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
[rdo-dev] Re: Plans in RDO for TripleO deprecation
On Wed, Feb 22, 2023 at 8:58 AM Marios Andreou wrote: > > On Tue, Feb 21, 2023 at 5:31 PM Alfredo Moralejo Alonso > wrote: > > > > Hi, > > > > As communicated in an openstack-discuss thread [1] the TripleO team is > > willing to deprecate master and Zed branches of TripleO repos. While > > the process for Zed is still under discussion with TC [2], there will > > not be new releases for Antelope and following releases. In the last > > meeting of RDO we discussed how to manage this change in RDO [3], and > > this is our proposal. > > > > TripleO packages in RDO releases > > > > - We will maintain TripleO packages in RDO in RDO-Trunk master until > > the content of the master branch is removed. According to the info > > provided by TripleO CI team, jobs for the master branch will keep > > running for some time. > > - Zed release is under discussion. We will follow the same approach as > > for the master branch and remove the packages from RDO Trunk once the > > branches are removed. We'll keep them if they stay in Extented > > Maintenance. > > - For Antelope release, which is under preparation for GA, we will not > > include TripleO packages in CloudSIG official repos. We will also > > remove them rpm RDO Trunk once we have confirmation from the TripleO > > CI team that they don't need it anymore (or with master branch removal > > at latest) > > > > Currently, TripleO component includes 102 packages but not all of them > > are TripleO specific: > > > > - Non-tripleo puppet modules: we will maintain those in a new > > component "puppet". > > - Some packages for OpenStack services Heat, Zaqar and Mistral. We > > need to look for new components for those, would common be a good fit? > > - Non-TripleO ansible roles: are those used out of TripleO? I guess > > not, but I'm willing to get feedback from RDO users about what may be > > useful so that we can move it to another component > > - TripleO packages. To be retired. If any package can be useful for > > any other deployment tool, those may be moved to the suitable > > component too. > > > > You can find the entire list of packages in > > https://review.rdoproject.org/etherpad/p/post-tripleo-proposal , feel > > free to check it and provide any feedback there. > > > > RDO definition-of-done > > > > Since last releases, the release criteria for new releases of RDO has > > been based on puppet-openstack-integration, packstack (which also > > relies on OpenStack Puppet modules) and TripleO jobs results. > > > > This change forces us to adapt the RDO definition of done. In Antelope > > the release criteria will be only based on the > > puppet-openstack-integration and packstack jobs (8 jobs) Correct for > > Antelope. Going forward, we will reevaluate this in future releases. > > > > sounds right ^^^ and just to note that even before the tripleo > announcement there were no plans for tripleo to create an Antelope > branch (in the same way we skipped X and Y). The main difference is > there will be no 'tagged' version of tripleo for you to include as we > did for previous skipped releases. Even though existing pipelines for > master will (likely) still be running when you make the release, it > doesn't make sense to tag a tripleo promotion for A given the plans > going forward. FYI, I've just sent a patch to RDO documentation to update the definition of done for antelope[1]. https://review.rdoproject.org/r/c/rdo-website/+/47186 [1] https://www.rdoproject.org/rdo/release-checklist/ > > thanks, marios > > > We will continue refining this plan the next few weeks, please let us > > know any doubt or suggestion that you may have on this thread, in #rdo > > or in the weekly meetings (wed. 14:00 UTC in #rdo). > > > > Best regards, > > > > Alfredo > > > > [1] > > https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032083.html > > [2] > > https://lists.openstack.org/pipermail/openstack-discuss/2023-February/032238.html > > [3] > > https://meetings.opendev.org/meetings/rdo_meeting___2023_02_15/2023/rdo_meeting___2023_02_15.2023-02-15-14.03.log.html > > ___ > > dev mailing list -- dev@lists.rdoproject.org > > To unsubscribe send an email to dev-le...@lists.rdoproject.org > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > > > To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s > ___ dev mailing list -- dev@lists.rdoproject.org To unsubscribe send an email to dev-le...@lists.rdoproject.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s
