Re: [openstack-dev] [all] Removal of puppet and ruby from nodepool images
On Mon, May 01, 2017 at 12:11:14PM -0400, Paul Belanger wrote: > On Mon, May 01, 2017 at 09:59:01AM -0400, Paul Belanger wrote: > > On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > > > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > > > Greetings, > > > > > > > > We, openstack-infra, are on our final steps of removing puppet (and > > > > ruby) from > > > > our images jobs run in nodepool. At this point, I think we are > > > > confident we > > > > shouldn't break any projects however I wanted to send this email just > > > > to keep > > > > everybody up to date. > > > > > > > > If you do depend on puppet or ruby for your project jobs, please make > > > > sure to > > > > update your intree bindep.txt file and express the dependency. > > > > > > > > If you do have a problem, please join us in #openstack-infra so we can > > > > help. > > > > > > > As a heads up, we are rolling out another set of changes today. This is > > > the > > > final setup needed from manging our diskimage in nodepool with puppet. > > > > > > As a result, jobs should now be setting up there SSH known_hosts files as > > > needed. For example: > > > > > > ssh-keyscan >> ~/.ssh/known_hosts > > > > > > Or if you'd like to continue with disabled host checking: > > > > > > ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null > > > > > And today was the day we approved the change[1] \o/ > > > > We plan on starting rebuilds in the next 30min, and take a few hours to > > build / > > upload everything. In the mean time, if you start to see random failures > > please > > join us in #openstack-infra to troubleshoot. > > > > We'll be doing our best to monitor http://status.opentack.org/zuul and > > http://status.openstack.org/elastic-recheck/ to find any affected jobs. > > > > -PB > > > > [1] https://review.openstack.org/#/c/460728/ > > > The centos-7 and fedora-25 images are live now. We are moving foward with > ubuntu-trusty and ubuntu-xenial next. > And ubuntu-trusty and ubuntu-xenial images online now. We'll continue to watch jobs to see if there are any issues that are found. Moving forward, if you job required puppet or ruby, you'll now need to use the bindep.txt file to include these dependencies. -PB __ 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] [all] Removal of puppet and ruby from nodepool images
On Mon, May 01, 2017 at 09:59:01AM -0400, Paul Belanger wrote: > On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > > Greetings, > > > > > > We, openstack-infra, are on our final steps of removing puppet (and ruby) > > > from > > > our images jobs run in nodepool. At this point, I think we are confident > > > we > > > shouldn't break any projects however I wanted to send this email just to > > > keep > > > everybody up to date. > > > > > > If you do depend on puppet or ruby for your project jobs, please make > > > sure to > > > update your intree bindep.txt file and express the dependency. > > > > > > If you do have a problem, please join us in #openstack-infra so we can > > > help. > > > > > As a heads up, we are rolling out another set of changes today. This is the > > final setup needed from manging our diskimage in nodepool with puppet. > > > > As a result, jobs should now be setting up there SSH known_hosts files as > > needed. For example: > > > > ssh-keyscan >> ~/.ssh/known_hosts > > > > Or if you'd like to continue with disabled host checking: > > > > ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null > > > And today was the day we approved the change[1] \o/ > > We plan on starting rebuilds in the next 30min, and take a few hours to build > / > upload everything. In the mean time, if you start to see random failures > please > join us in #openstack-infra to troubleshoot. > > We'll be doing our best to monitor http://status.opentack.org/zuul and > http://status.openstack.org/elastic-recheck/ to find any affected jobs. > > -PB > > [1] https://review.openstack.org/#/c/460728/ > The centos-7 and fedora-25 images are live now. We are moving foward with ubuntu-trusty and ubuntu-xenial next. -PB __ 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] [all] Removal of puppet and ruby from nodepool images
On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > Greetings, > > > > We, openstack-infra, are on our final steps of removing puppet (and ruby) > > from > > our images jobs run in nodepool. At this point, I think we are confident we > > shouldn't break any projects however I wanted to send this email just to > > keep > > everybody up to date. > > > > If you do depend on puppet or ruby for your project jobs, please make sure > > to > > update your intree bindep.txt file and express the dependency. > > > > If you do have a problem, please join us in #openstack-infra so we can help. > > > As a heads up, we are rolling out another set of changes today. This is the > final setup needed from manging our diskimage in nodepool with puppet. > > As a result, jobs should now be setting up there SSH known_hosts files as > needed. For example: > > ssh-keyscan >> ~/.ssh/known_hosts > > Or if you'd like to continue with disabled host checking: > > ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null > And today was the day we approved the change[1] \o/ We plan on starting rebuilds in the next 30min, and take a few hours to build / upload everything. In the mean time, if you start to see random failures please join us in #openstack-infra to troubleshoot. We'll be doing our best to monitor http://status.opentack.org/zuul and http://status.openstack.org/elastic-recheck/ to find any affected jobs. -PB [1] https://review.openstack.org/#/c/460728/ __ 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] [all] Removal of puppet and ruby from nodepool images
On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > Greetings, > > We, openstack-infra, are on our final steps of removing puppet (and ruby) from > our images jobs run in nodepool. At this point, I think we are confident we > shouldn't break any projects however I wanted to send this email just to keep > everybody up to date. > > If you do depend on puppet or ruby for your project jobs, please make sure to > update your intree bindep.txt file and express the dependency. > > If you do have a problem, please join us in #openstack-infra so we can help. > As a heads up, we are rolling out another set of changes today. This is the final setup needed from manging our diskimage in nodepool with puppet. As a result, jobs should now be setting up there SSH known_hosts files as needed. For example: ssh-keyscan >> ~/.ssh/known_hosts Or if you'd like to continue with disabled host checking: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -PB __ 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] [all] Removal of puppet and ruby from nodepool images
Greetings, We, openstack-infra, are on our final steps of removing puppet (and ruby) from our images jobs run in nodepool. At this point, I think we are confident we shouldn't break any projects however I wanted to send this email just to keep everybody up to date. If you do depend on puppet or ruby for your project jobs, please make sure to update your intree bindep.txt file and express the dependency. If you do have a problem, please join us in #openstack-infra so we can help. Thanks -PB __ 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
