<font face="arial" size="2"><p style="margin:0;padding:0;font-family: arial; font-size: 10pt;">Jim,</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;">Okay. I'm still a bit fuzzy on the order of operations we'd need to make in order to get branch in when a config file changes.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;"> </p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;">Take this review for example:</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;"> </p>
<p style="margin:0;padding:0;"><span style="font-family: arial; font-size: 10pt;"> https://review.openstack.org/#change,2919</span></p>
<p style="margin:0;padding:0;"> </p>
<p style="margin:0;padding:0;"><span style="font-family: arial; font-size: 10pt;">Based on what I understand devstack needs to support both version of the nova config file in order for the branches to land smoothly? That seems like something we wouldn't want to do. Am I misunderstanding something?</span></p>
<p style="margin:0;padding:0;"> </p>
<p style="margin:0;padding:0;"><span style="font-family: arial; font-size: 10pt;">Also, in order to coordinate these types of changes shouldn't all core members on gated projects have core privileges on devstack as well? This would allow us to coordinate making these types of changes?</span></p>
<p style="margin:0;padding:0;"> </p>
<p style="margin:0;padding:0;"><span style="font-family: arial; font-size: 10pt;">Dan</span></p>
<p style="margin:0;padding:0;"><span style="font-family: arial; font-size: 10pt;"><br /></span></p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt;">-----Original Message-----<br />From: "James E. Blair" <corvus@inaugust.com><br />Sent: Wednesday, January 4, 2012 12:09pm<br />To: "OpenStack Mailing List" <openstack@lists.launchpad.net><br />Subject: Re: [Openstack] Integration test gating on trunk<br /><br /></p>
<div id="SafeStyles1326227719" style="font-family: arial; font-size: 10pt;">
<p style="margin:0;padding:0;">"Dan Prince" <dan.prince@rackspace.com> writes:<br /><br />> Hi Jim,<br />> <br />> A couple of questions for you:<br />> <br />> 1) You mentioned how to coordinate changes between glance and nova but<br />> what about devstack. Does that same process apply to devstack as well?<br />> For example if there were a configuration file change (api-paste<br />> changes often and can cause failures) would I push the required change<br />> to devstack first and then nova? Or would we need to make devstack<br />> handle multiple versions of the configuration files?<br /><br />Yes, the same is true for coordinating changes across all of the<br />projects, including devstack (one change at a time in sequence).<br /><br />> 2) Where are the devstack instances running (public cloud, private<br />> Openstack cloud, etc.). If the public cloud is down for maintenance<br />> does that mean code can't land? Are there any plans to run this on a<br />> private or OpenStack backed cloud? Regardless of what we are doing is<br />> there a backup plan in place so that code can land?<br /><br />They are currently running in the Rackspace public cloud. There is a<br />cache of N machines (N==5 currently) running and ready to receive<br />devstack installs for this test, with new ones being added by a frequent<br />Jenkins job[1] to replace those consumed. That helps smooth over<br />operational errors and short outages. If all of those are consumed, the<br />job will fail, and we won't be able to land patches. Considering the<br />importance of RS public cloud availability, I think that waiting until<br />it's up again is probably going to be a viable option. If there is some<br />sort of extended outage, we can discuss disabling the job.<br /><br />In the medium to long term, we plan on mitigating this risk by consuming<br />VMs from multiple cloud providers. HP has offered its public cloud for<br />this purpose. I'd like the normal mode of operation to launch VMs on<br />both (all?) of the cloud providers participating to balance load and<br />resource usage, and of course that gets us higher availability, at least<br />for the kind of scenario you described.<br /><br />> 3) Are there any plans on making this run on branches in merge prop<br />> (before we approve them)? I would love to know that devstack passes<br />> ahead of time before I approve a branch.<br /><br />Yes, running tests when patchsets are uploaded is in the plan. With the<br />new gerrit trigger plugin we installed last week, we have the technical<br />capability to run Jenkins jobs on proposal, approval, or merge. I<br />believe we will start working on that soon, after we address some<br />security concerns.<br /><br />-Jim<br />[1] https://jenkins.openstack.org/job/devstack-launch-vms/<br /><br />_______________________________________________<br />Mailing list: https://launchpad.net/~openstack<br />Post to : openstack@lists.launchpad.net<br />Unsubscribe : https://launchpad.net/~openstack<br />More help : https://help.launchpad.net/ListHelp</p>
</div></font>