<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 27 July 2016 at 19:10, Tony Breeds <span dir="ltr"><<a target="_blank" href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">On Mon, Jul 18, 2016 at 04:09:54PM +0200, Markus Zoeller wrote:<br>
> Since yesterday, Nova uses "oslo.context" 2.6.0 [1] but the needed<br>
> change [2] is not yet in place, which broke "gate-nova-python27-db"[3].<br>
> Logstash counts 70 hits/h [4]. Most folks will be at the midcycle in<br>
> Portland and won't be available for the next 2h or so.<br>
> If you can have a look at it and merge it, that would be great.<br>
><br>
> References:<br>
> [1]<br>
> <a target="_blank" rel="noreferrer" href="https://github.com/openstack/requirements/commit/238389c4ee1bd3cc9be4931dd2639aea2dae70f1">https://github.com/openstack/requirements/commit/238389c4ee1bd3cc9be4931dd2639aea2dae70f1</a><br>
> [2] <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/342604/1">https://review.openstack.org/#/c/342604/1</a><br>
> [3] <a target="_blank" rel="noreferrer" href="https://bugs.launchpad.net/nova/+bug/1603979">https://bugs.launchpad.net/nova/+bug/1603979</a><br>
> [4] logstash: <a target="_blank" rel="noreferrer" href="http://goo.gl/79yFb9">http://goo.gl/79yFb9</a><br>
<br>
I feel like we need to make a plan to more forward and that's going to require<br>
some coordination.<br>
<br>
The requirements team saw this coming in that nova's tests failed when 2.6.0<br>
was added to the upper-constraints.txt. We had a plan[1] but then failed to<br>
execute. The requirements team has a couple of TODOs from there but the<br>
biggest one is to add actual cross-project gate checks so that we have *very<br>
strong* signals that things will break.<br>
<br>
So the state we're in is<br>
oslo.context 2.6.0 is out and used in all projects that *do not* honor upper-constraints.txt<br>
oslo.context 2.5.0 is being used by all projects that *do* honor upper-constraints.txt<br>
<br>
The Path forward IMO is<br>
<br>
a) Unblock oslo.context 2.6.0<br>
  - But leave upper-constraints.txt pointing to 2.5.0<br>
  - <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/347608/">https://review.openstack.org/#/c/347608/</a><br>
    * We can test shims/fixes against this.<br></blockquote><div><br></div><div>I think this gets easier with the release of 2.7 as we can hopefully just bump minimum requirements to here and forget the whole 2.6 mess. <br> <br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
b) Identify projects that break with > 2.5.0<br>
  - Seems like this is (at least)<br>
    - Trove<br></blockquote><div> </div><div>check job: <a href="https://review.openstack.org/#/c/349204/">https://review.openstack.org/#/c/349204/</a><br><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
    - Nova<br></blockquote><div><br>check job: <a href="https://review.openstack.org/#/c/348204/">https://review.openstack.org/#/c/348204/</a><br><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
    - Designate<br></blockquote><div><br>check job: <a href="https://review.openstack.org/#/c/349205/">https://review.openstack.org/#/c/349205/</a> <br><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
    - Others?<br>
c) Add shims to them to work with 2.5.0 and newer<br>
  - Nova: <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/342604/">https://review.openstack.org/#/c/342604/</a> and <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/348057/">https://review.openstack.org/#/c/348057/</a><br>
d) Bump u-c to point at "the latest"<br>
e) Bump the minium in g-r to 2.6.0<br>
f) Remove items from 'c'<br>
<br>
Notes:<br>
 - The requirements team will not be able to merge any change that bumps<br>
  oslo.context in u-c until step 'd'. The reality here is due to our<br>
  tooling/gating that probably means that all u-c changes will be paused<br>
 - As stated in my pre-amble we're working on testing to make this better.<br>
 - We almost certainly need a corss-project session during the design summit to<br>
  discuss the API boundry for the context and how projects are<br>
  expected/allowed to use it.<br></blockquote><div><br></div><div>Thanks Tony. I think this will work well. I hope not many other projects will need the same shims nova did as we've patched a few already. <br></div><div>I completely agree on the cross-project oslo.context session and offer to take that one as there are a number of plans around improving it that have not been properly communicated. <br><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
Yours Tony.<br>
<br>
[1] <a target="_blank" rel="noreferrer" href="http://eavesdrop.openstack.org/irclogs/%23openstack-requirements/%23openstack-requirements.2016-07-15.log.html#t2016-07-15T03:42:24">http://eavesdrop.openstack.org/irclogs/%23openstack-requirements/%23openstack-requirements.2016-07-15.log.html#t2016-07-15T03:42:24</a><br>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a target="_blank" rel="noreferrer" href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a target="_blank" rel="noreferrer" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>