<div dir="ltr"><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 7:01 AM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On 07/11/2013 08:48 AM, John Griffith wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Thu, Jul 11, 2013 at 6:29 AM, Dirk Müller <<a href="mailto:dirk@dmllr.de" target="_blank">dirk@dmllr.de</a><br></div><div class="im">
<mailto:<a href="mailto:dirk@dmllr.de" target="_blank">dirk@dmllr.de</a>>> wrote:<br>
<br>
Hi Sean,<br>
<br>
> Cinder uncapping python-keystoneclient will get us past this.<br>
<br>
There is a review exactly proposing that:<br>
<br>
<a href="https://review.openstack.org/#/c/36344/" target="_blank">https://review.openstack.org/#<u></u>/c/36344/</a><br>
<br>
<br>
Actually for a number of reasons:<br>
<a href="https://review.openstack.org/#/c/36559/" target="_blank">https://review.openstack.org/#<u></u>/c/36559/</a> is what we needed,<br>
which I gave up on last night a bit after midnight when James Blair moved it<br>
to the front of the queue and it encountered a hiccup, at which point<br>
some other<br>
core Cinder folks took over baby-sitting it and it's finally through.<br>
<br>
<br>
<br>
<br>
> Though I'm not<br>
> quite sure how we got to this break point in the first place.<br>
<br>
<br>
I think this is due to the django_openstack_auth breakage that let<br>
this one slip by (there was for a short amount of time a >= 0.3<br>
requirement on python-keystoneclient from somewhere).<br>
<br>
Yep, although it wasn't that short of a period of time. I also raised<br>
this concern<br>
over the ML regarding common-requirements etc and had ZERO response.<br>
</div></blockquote>
<br>
I think the issue is that it came in the fire drill when we were running around getting to the bottom of the last gate fail.... sorry.<br></blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">
Didn't mean it in that way at all... my message my not have been clear anyway.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I guess I thought my full uncapping strategy might supercede just a sync issue, no?</blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">To be honest and try to recap my opinion on this I don't really care at all how it's done, but:</div>
<div class="gmail_default" style="font-family:'courier new',monospace">I *thought* the whole point of the common-requirements deal was to have EVERYBODY on the same page</div><div class="gmail_default" style="font-family:'courier new',monospace">
and avoid this very situation.</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">However it turned out a number of projects were out of sync earlier this week so we headed in to a</div>
<div class="gmail_default" style="font-family:'courier new',monospace">a bit of a death spiral. And the change that bumped it... I haven't looked back to figure out how</div><div class="gmail_default" style="font-family:'courier new',monospace">
exactly that made it in to begin with but I assume it was done by something like NOT using the </div><div class="gmail_default" style="font-family:'courier new',monospace">requirements file to install the client or something? This is all I can figure because when I first</div>
<div class="gmail_default" style="font-family:'courier new',monospace">noticed that things were out of sync on Monday I thought *ok, I'll just remove the upper bound on Cinder</div><div class="gmail_default" style="font-family:'courier new',monospace">
to match the other projects since we're ignoring common-requirements*. That didn't work because as it</div><div class="gmail_default" style="font-family:'courier new',monospace">turns out we DO in fact have enforcement if you try and change your requirements file in a project and</div>
<div class="gmail_default" style="font-family:'courier new',monospace">it doesn't match what's in the common file (a good thing in my opinion).</div><div class="gmail_default" style="font-family:'courier new',monospace">
<br></div><div class="gmail_default" style="font-family:'courier new',monospace">So I sent the email regarding the state of things... then yesterday as everybody noticed things fell apart</div><div class="gmail_default" style="font-family:'courier new',monospace">
when the common-requirements file was updated BUT Cinder was not updated to match (makes sense right). So</div><div class="gmail_default" style="font-family:'courier new',monospace">you think *sure, update common, no go update cinder etc*, well in theory that's great but with everything</div>
<div class="gmail_default" style="font-family:'courier new',monospace">going on yesterday the average time to get a patch in was somewhere around 2 hours or something and throw in</div><div class="gmail_default" style="font-family:'courier new',monospace">
our favorite gating bug of the month (bug 1194026, which now has over 125 rechecks when combined with it's duplicate)</div><div class="gmail_default" style="font-family:'courier new',monospace">and it didn't take 12 hours to get the change in, it took closer to 20 hours.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Obviously there's an opportunity here. Whether that's taking all of the requirements version information and having it ONLY</div>
<div class="gmail_default" style="font-family:'courier new',monospace">come from the common-requirements file or uncapping or whatever everybody else wants to do I don't really care it just</div><div class="gmail_default" style="font-family:'courier new',monospace">
needs to be addressed.</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">My proposal would be each projects requirements file is used as nothing more than a list of the packages it needs/wants,</div>
<div class="gmail_default" style="font-family:'courier new',monospace">the common-requirements file is what's used to determine version to install and is where the actual install work is done,</div><div class="gmail_default" style="font-family:'courier new',monospace">
removing upper bounds could save a lot of issues as well, but I think there could be some consequences there as well.</div><h3 class="" style="margin:10px 0px 0.2em;padding:1.5em 0px 5px;border:none;font-weight:normal;font-size:16px;font-family:'Helvetica Neue',Arial,Helvetica,sans-serif;vertical-align:baseline;color:rgb(207,47,25);line-height:1">
<br></h3><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im"><br>
<br>
-Sean<br>
<br>
-- <br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br></div><div class=""><div class="h5">
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>