owned this note changed 5 years ago
Published Linked with GitHub

Decomission TripleO ROCKY, QUEENS

<weshay|ruck> marios|ruck, http://dashboard-ci.tripleo.org/d/3-DYSmOGk/jobs-exploration?orgId=1&var-influxdb_filter=branch%7C%3D%7Cstable%2Fqueens&from=now-30d&to=now&fullscreen&panelId=22
[08:35:23] <marios|ruck> weshay|ruck: where is my power :D
[08:35:35] <weshay|ruck> heh
[08:35:46] <weshay|ruck> marios|ruck, all the sceario jobs for queens are nv
[08:36:35] <weshay|ruck> queens periodic should be...
[08:36:36] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-content-provider
[08:36:36] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-containers-multinode
[08:36:36] <weshay|ruck> 2020-10-21 tripleo-buildimage-overcloud-hardened-full-centos-7
[08:36:36] <weshay|ruck> 2020-10-21 tripleo-buildimage-overcloud-full-centos-7 
[08:36:36] <weshay|ruck> 2020-10-21 tripleo-buildimage-ironic-python-agent-centos-7
[08:37:06] <weshay|ruck> where content-provider.. is container-build
[08:38:05] <weshay|ruck> marios|ruck, and remove non-voting queens jobs
[08:38:48] <weshay|ruck> so... remove
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario010-multinode-oooq-container
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario007-multinode-oooq-container 
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario003-multinode-oooq-container 
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario002-multinode-oooq-container
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario001-multinode-oooq-container
[08:38:49] <weshay|ruck> 2020-10-21 tripleo-ci-centos-7-scenario000-multinode-oooq-container-upgrades 
[08:38:49] <weshay|ruck> 2020-10-21 openstack-tox-cover 
[08:39:09] <weshay|ruck> marios|ruck, Alex and I decided to move those to nv 1 or 2 cycles ago.. permenately
[08:39:30] <weshay|ruck> but left them as criteria in periodic.. for imports
[08:39:43] <weshay|ruck> now we don't have imports
[08:39:47] <weshay|ruck> so nuke'em
[08:40:04] <weshay|ruck> duke nukem
[08:40:49] <marios|ruck> weshay|ruck: i agree with what you write above. my understanding per the mail thread is "final decisions still to be made" regarding the import
[08:40:59] <marios|ruck> weshay|ruck: so once we have that yeah the above plan makes sense.
[08:41:01] * ykarel has quit (Ping timeout: 246 seconds)
[08:41:03] <marios|ruck> weshay|ruck: we might even go further
[08:41:43] <weshay|ruck> k...  I expect the TRAC to make a decision on this in early December.
[08:41:46] <marios|ruck> weshay|ruck: and consider marking the branch unmaintained. because eventually any jobs we leave there will break and no one will be fixing those
[08:41:54] <marios|ruck> or at least it won't be any ones priority
[08:42:03] <weshay|ruck> marios|ruck, so let's revisit this in a couple weeks
[08:42:20] <weshay|ruck> marios|ruck, no no
[08:42:39] <weshay|ruck> let's keep queens as maintained.. I think we HAVE to... but only w/ the one job
[08:42:59] <weshay|ruck> extended maint.. and all
[08:43:04] <marios|ruck> weshay|ruck: i don't think we *have* to because of the stable:follows-policy thing i mentioned as pointed out by apevec
[08:43:32] <weshay|ruck> I think that's not correct
[08:43:35] <marios|ruck> weshay|ruck: i.e. if we decide to make it unmaintained, there is a possibility the TC will raise an objection
[08:43:42] * weshay|ruck looks at opendev doc
[08:43:46] <marios|ruck> weshay|ruck: k well it would be good to find out
[08:44:34] <marios|ruck> weshay|ruck: i was looking at that today https://governance.openstack.org/tc/reference/tags/stable_follows-policy.html
[08:45:14] <marios|ruck> weshay|ruck: especially @ Rationale "some do not actively backport significant bugfixes, some don’t monitor proposed backports, or monitor the CI system on their stable branches…"
[08:45:56] <marios|ruck> weshay|ruck: you can see repo tags at https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml
[08:46:19] <weshay|ruck> maybe it is up to us
[08:46:19] <weshay|ruck> Send an announcement to the openstack-discuss mailing list (in order to give some time for others to step up as maintainers if there are volunteers).
[08:46:19] <weshay|ruck> Remove any related zuul jobs that are defined in other repositories and not needed anymore.
[08:46:19] <weshay|ruck> Propose a patch against the given project/repository. (For example, see: https://review.opendev.org/#/c/677478/)
[08:46:19] <weshay|ruck> After the branch is tagged with $series-eol, request the infra team to delete the branch.
[08:46:54] <weshay|ruck> marios|ruck, we could do a test run of that w/ rocky
[08:47:02] <weshay|ruck> def.. no imports of rocky now
[08:47:10] <marios|ruck> weshay|ruck:  at https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases "The branch is under Extended Maintenance rules, but there are no maintainers." i mean if no one is maintaining it then we can just move to unmaintained?
[08:47:19] <marios|ruck> i.e no community members availa to maintain it
[08:47:35] <marios|ruck> weshay|ruck: ack ok
[08:48:11] <weshay|ruck> so initiate destruction of tripleo rocky.. any time.. 
[08:48:19] <weshay|ruck> and in dec.. we'll find out about queens
[08:48:22] <marios|ruck> weshay|ruck: ok i will do that next week
[08:48:31] <marios|ruck> weshay|ruck: and see what happens
[08:50:26] <marios|ruck> weshay|ruck: hmm but why rocky first
[08:50:29] <marios|ruck> weshay|ruck: i mean queens is older
[08:53:03] <weshay|ruck> marios|ruck, rocky first.. because there are no imports
[08:53:20] * rlandy|rover|brb is now known as rlandy|rover
[08:53:26] <marios|ruck> weshay|ruck: ack
[08:53:40] <weshay|ruck> marios|ruck, ping me next week and we can work on it together
[08:53:47] <weshay|ruck> would be nice to lighten everyones load
[08:53:49] <weshay|ruck> and focus
[08:53:53] <marios|ruck> weshay|ruck: ack
Select a repo