<tt><font size=2>Jonathan Proulx <jon@jonproulx.com> wrote on 06/11/2015
05:13:36 PM:<br>
<br>
> From: Jonathan Proulx <jon@jonproulx.com></font></tt>
<br><tt><font size=2>> To: David Medberry <openstack@medberry.net></font></tt>
<br><tt><font size=2>> Cc: "openstack@lists.openstack.org"
<openstack@lists.openstack.org></font></tt>
<br><tt><font size=2>> Date: 06/11/2015 05:25 PM</font></tt>
<br><tt><font size=2>> Subject: Re: [Openstack] Insanity check: Kilo-Keystone
w/ Juno-everything else</font></tt>
<br><tt><font size=2>> <br>
> On Thu, Jun 11, 2015 at 5:00 PM, David Medberry <br>
> <openstack@medberry.net> wrote:<br>
> > We have run with (really) Liberty keystone, Liberty horizon and
everything<br>
> > else Juno.<br>
> ><br>
> > I suspect you can do this mixed thing as long as you pay careful
attention.<br>
> <br>
> Definitely seems like it *should* work as the API *shouldn't* change.<br>
> Glad to hear this actually seems to be the case<br>
> <br>
> > Likewise, when we upgrade our TWO REGIONAL DATACENTERS we always
do one and<br>
> > then the next a couple days later, so all of our upgrades have
had a single<br>
> > KEYSTONE against two different rest-of-the-clouds and that works
just fine.<br>
> ><br>
> > You may find more info on the openstack-operators list (a pretty
good place<br>
> > for this kind of of topic.)<br>
> <br>
> Familiar with the ops list, my (probably misguided) thought for<br>
> posting here was to maybe get dev & ops people. Though I
suppose this<br>
> is becoming more the intro to openstack list in practice.<br>
</font></tt>
<br><font size=2 face="sans-serif">Your thoughts are not as misguided as
you'd believe, I think most devs</font>
<br><font size=2 face="sans-serif">subscribe to this list as well.</font>
<br>
<br><font size=2 face="sans-serif">Echoing David's reply, this should work.
The Keystone team tries really</font>
<br><font size=2 face="sans-serif">hard to not mangle any APIs, and if
we do, we always provide deprecation</font>
<br><font size=2 face="sans-serif">warnings in the log files.</font>
<br>
<br><font size=2 face="sans-serif">Furthermore, the inter-service communication
you mention should only</font>
<br><font size=2 face="sans-serif">depend on the keystonemiddleware pieces
that are used between services.</font>
<br><font size=2 face="sans-serif">This hasn't changed in a while.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,<br>
<br>
Steve Martinelli<br>
OpenStack Keystone Core</font>
<br>
<br><tt><font size=2>> <br>
> Thanks,<br>
> -Jon<br>
> <br>
> > -dave<br>
> ><br>
> > On Thu, Jun 11, 2015 at 1:58 PM, Jonathan Proulx <jon@jonproulx.com>
wrote:<br>
> >><br>
> >> Hi All,<br>
> >><br>
> >> As part of an expansion to a second Region (and 2nd datacenter)
I'm<br>
> >> considering building out the new region on Kilo and upgrading
the<br>
> >> (shared) Keystone to Kilo while leaving the rest of the current<br>
> >> region at Juno.<br>
> >><br>
> >> Obviously this is not a tested or supported configuration
but in my<br>
> >> small development environment so far it seems to work.<br>
> >><br>
> >> Is anyone running mixed versions like this in production,
or<br>
> >> conversely know of any fatal flaws I may be missing in test
that might<br>
> >> surface to bite me later?<br>
> >><br>
> >> Thanks,<br>
> >> -Jon<br>
> >><br>
</font></tt>
<br>