Re: [openstack-dev] [tripleo] Decreasing resource usage in tripleo CI
On 07/05/14 00:07, Clint Byrum wrote: +1 to the plans. We've recently freed up a few more boxes for the HP region, and we'll be rolling those out as we migrate from saucy to trusty for the rest of the cloud. But we should do all of the things below anyway. Thanks, didn't hear any objections, patch submitted https://review.openstack.org/#/c/92808/1 Excerpts from Derek Higgins's message of 2014-05-06 15:34:41 -0700: Hi, I mentioned this at the tripleo meeting today and to get opinions out there I'd like to bring it up here, In tripleo we are currently very tight on resources to run our CI jobs and I'd like to scale back temporarily until we have either more capacity or reorganize things a bit, to more efficiently use what we have. Basically I'd like to see us do 3 things 1. Get rid of check-tripleo-seed-precise job This is currently a subset of both check-tripleo-undercloud-precise and check-tripleo-overcloud-precise so is basically using up resources with no extra gain, if we put plans in place to deploy the undercloud/overcloud on a persistent seed we can add it back again. 2. Move the check-tripleo-ironic-undercloud-precise into the experimental-tripleo queue, this test is non voting and currently doesn't work, when its fixed we can put it back into the check-tripleo queue and delete the check-tripleo-ironic-seed-precise job, as it should be a subset of the ironic undercloud job (similar to the seed job mentioned in point 1) 3. Get back onto 8G nodepool instances, we moved to 16G instances a while back to work around a problem, I've a patch up that should allow us to get back to 8G nodes https://review.openstack.org/#/c/91545/ Any objections or alternate ideas? thanks, Derek. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo] Decreasing resource usage in tripleo CI
Hi, I mentioned this at the tripleo meeting today and to get opinions out there I'd like to bring it up here, In tripleo we are currently very tight on resources to run our CI jobs and I'd like to scale back temporarily until we have either more capacity or reorganize things a bit, to more efficiently use what we have. Basically I'd like to see us do 3 things 1. Get rid of check-tripleo-seed-precise job This is currently a subset of both check-tripleo-undercloud-precise and check-tripleo-overcloud-precise so is basically using up resources with no extra gain, if we put plans in place to deploy the undercloud/overcloud on a persistent seed we can add it back again. 2. Move the check-tripleo-ironic-undercloud-precise into the experimental-tripleo queue, this test is non voting and currently doesn't work, when its fixed we can put it back into the check-tripleo queue and delete the check-tripleo-ironic-seed-precise job, as it should be a subset of the ironic undercloud job (similar to the seed job mentioned in point 1) 3. Get back onto 8G nodepool instances, we moved to 16G instances a while back to work around a problem, I've a patch up that should allow us to get back to 8G nodes https://review.openstack.org/#/c/91545/ Any objections or alternate ideas? thanks, Derek. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] Decreasing resource usage in tripleo CI
+1 to the plans. We've recently freed up a few more boxes for the HP region, and we'll be rolling those out as we migrate from saucy to trusty for the rest of the cloud. But we should do all of the things below anyway. Excerpts from Derek Higgins's message of 2014-05-06 15:34:41 -0700: Hi, I mentioned this at the tripleo meeting today and to get opinions out there I'd like to bring it up here, In tripleo we are currently very tight on resources to run our CI jobs and I'd like to scale back temporarily until we have either more capacity or reorganize things a bit, to more efficiently use what we have. Basically I'd like to see us do 3 things 1. Get rid of check-tripleo-seed-precise job This is currently a subset of both check-tripleo-undercloud-precise and check-tripleo-overcloud-precise so is basically using up resources with no extra gain, if we put plans in place to deploy the undercloud/overcloud on a persistent seed we can add it back again. 2. Move the check-tripleo-ironic-undercloud-precise into the experimental-tripleo queue, this test is non voting and currently doesn't work, when its fixed we can put it back into the check-tripleo queue and delete the check-tripleo-ironic-seed-precise job, as it should be a subset of the ironic undercloud job (similar to the seed job mentioned in point 1) 3. Get back onto 8G nodepool instances, we moved to 16G instances a while back to work around a problem, I've a patch up that should allow us to get back to 8G nodes https://review.openstack.org/#/c/91545/ Any objections or alternate ideas? thanks, Derek. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
