Re: [openstack-dev] [openstack-ansible] dropping xenial jobs
FYI: Thanks to Jesse, he has picked up this work and it's up here: https://review.openstack.org/#/c/609329/6 On Wed, Oct 10, 2018 at 9:56 AM Jesse Pretorius wrote: > > On 10/10/18, 5:54 AM, "Mohammed Naser" wrote: > > >So I’ve been thinking of dropping the Xenial jobs to reduce our overall > > impact in terms of gate usage in master because we don’t support it. > > I think we can start dropping it given our intended supported platform for > Stein is Bionic, not Xenial. We'll have to carry Xenial & Bionic for Rocky as > voting jobs. Anything ported back and found not to work for both can be fixed > through either another patch to master which is back ported, or a > re-implementation, as necessary. > > > > > Rackspace Limited is a company registered in England & Wales (company > registered number 03897010) whose registered office is at 5 Millington Road, > Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be > viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may > contain confidential or privileged information intended for the recipient. > Any dissemination, distribution or copying of the enclosed material is > prohibited. If you receive this transmission in error, please notify us > immediately by e-mail at ab...@rackspace.com and delete the original message. > Your cooperation is appreciated. > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mohammed Naser — vexxhost - D. 514-316-8872 D. 800-910-1726 ext. 200 E. mna...@vexxhost.com W. http://vexxhost.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-ansible] dropping xenial jobs
On 10/10/18, 5:54 AM, "Mohammed Naser" wrote: >So I’ve been thinking of dropping the Xenial jobs to reduce our overall > impact in terms of gate usage in master because we don’t support it. I think we can start dropping it given our intended supported platform for Stein is Bionic, not Xenial. We'll have to carry Xenial & Bionic for Rocky as voting jobs. Anything ported back and found not to work for both can be fixed through either another patch to master which is back ported, or a re-implementation, as necessary. Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com and delete the original message. Your cooperation is appreciated. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-ansible] dropping xenial jobs
On Wed, 2018-10-10 at 06:50 +0200, Mohammed Naser wrote: > Hi everyone! > > So I’ve been thinking of dropping the Xenial jobs to reduce our > overall impact in terms of gate usage in master because we don’t > support it. > > However, I was a bit torn on this because i realize that it’s > possible for us to write things and backport them only to find out > that they’d break under xenial which can be deployed with Rocky. > > Thoughts? Ideas? I was thinking maybe Lee an experimental job.. not > really sure on specifics but I’d like to bring in more feedback. > > Thanks, > Mohammed > _ > _ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Hello, In the past we removed the jobs (ocata didn't have trusty jobs, IIRC), and made sure backports were still passing the gates of newton with trusty jobs voting. It may force a re-implementation in lower branches, but it is fine for me, as ansible versions also differ and might require re-implementation anyway. That said, we didn't have the flexibility we have now with Zuul v3, and making the jobs voting/nv/experimental. The middle ground would be to have a non-voting check job. It is fine, but it consumes resources for patches that aren't supposed to be backported, and therefore I think it's not the greatest solution. I like the "check experimental" part. It has an inconvenient: it relies on our good behaviour: When a bug is raised (so first element, we should not forget the bug link!) for backport, we should all keep in mind to check experimental before attempting the merge on the higher branch. That said, I still prefer the "check experimental" that nothing. You have my vote! Best regards, JP __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-ansible] dropping xenial jobs
Hi everyone! So I’ve been thinking of dropping the Xenial jobs to reduce our overall impact in terms of gate usage in master because we don’t support it. However, I was a bit torn on this because i realize that it’s possible for us to write things and backport them only to find out that they’d break under xenial which can be deployed with Rocky. Thoughts? Ideas? I was thinking maybe Lee an experimental job.. not really sure on specifics but I’d like to bring in more feedback. Thanks, Mohammed __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
