][keystone][heat] Are
AVAILABLE_REGIONS and multi-region service catalog mutually exclusive?
On Thu, May 14, 2015 at 9:39 AM, Geoff Arnold ge...@geoffarnold.com
wrote:
+1
There seems to be a significant disconnect between Heat, Horizon and
Keystone on the subject of multi-region configurations
+1
There seems to be a significant disconnect between Heat, Horizon and Keystone
on the subject of multi-region configurations, and the documentation isn’t
helpful. At the very least, it would be useful if discussions at the summit
could result in a decent Wiki page on the subject.
Geoff
On
That’s interesting, because I wasn’t aware that “cloud” was part of the formal
OpenStack taxonomy. Historically, we defined a region as a set of endpoints,
supplied by an instance of Keystone. You seem to be saying that a cloud is a
collection of regions configured in the same Keystone.
+1
A wiki page laying out a mutually agreeable taxonomy seems like a good starting
point.
Geoff
On May 14, 2015, at 7:47 AM, Anne Gentle annegen...@justwriteclick.com
wrote:
On Thu, May 14, 2015 at 9:39 AM, Geoff Arnold ge...@geoffarnold.com
mailto:ge...@geoffarnold.com wrote:
+1
On Thu, May 14, 2015 at 9:39 AM, Geoff Arnold ge...@geoffarnold.com wrote:
+1
There seems to be a significant disconnect between Heat, Horizon and
Keystone on the subject of multi-region configurations, and the
documentation isn’t helpful. At the very least, it would be useful if
On 14/05/15 10:39, Geoff Arnold wrote:
+1
There seems to be a significant disconnect between Heat, Horizon and
Keystone on the subject of multi-region configurations, and the
documentation isn’t helpful. At the very least, it would be useful if
discussions at the summit could result in a decent
On Thursday, May 14, 2015, Anne Gentle annegen...@justwriteclick.com
wrote:
On Thu, May 14, 2015 at 9:39 AM, Geoff Arnold ge...@geoffarnold.com
javascript:_e(%7B%7D,'cvml','ge...@geoffarnold.com'); wrote:
+1
There seems to be a significant disconnect between Heat, Horizon and
Keystone on
On 2015-05-14 12:34 AM, David Lyle wrote:
Horizon only supports authenticating to one keystone endpoint at a time,
specifically to one of the entries in AVAILABLE_REGIONS as defined in
settings.py. Once you have an authenticated session in Horizon, the
region selection support is merely for
Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [horizon][keystone][heat] Are
AVAILABLE_REGIONS and multi-region service catalog mutually exclusive?
That’s interesting, because I wasn’t aware that “cloud” was part of the formal
OpenStack taxonomy. Historically
On 14/05/15 14:41, Geoff Arnold wrote:
That’s interesting, because I wasn’t aware that “cloud” was part of the formal
OpenStack taxonomy.
Um, OK. AWS, Rackspace and Helion are all different clouds, even though
the last two both run OpenStack. Do we really need a formal taxonomy for
that?
If we don’t want to deprecate AVAILABLE_REGIONS, we certainly need to clean up
the ambiguity. And to be honest, the existing documentation for both
multi-region” schemes (AVAILABLE_REGIONS and Keystone based) is completely
inadequate.
Geoff
On May 14, 2015, at 1:13 PM, Mathieu Gagné
On May 13, 2015, at 21:34, David Lyle dkly...@gmail.com wrote:
On Wed, May 13, 2015 at 3:24 PM, Mathieu Gagné mga...@iweb.com wrote:
When using AVAILABLE_REGIONS, you get a dropdown at login time to choose
your region which is in fact your keystone endpoint.
Once logged in, you get a
When using AVAILABLE_REGIONS, you get a dropdown at login time to choose
your region which is in fact your keystone endpoint.
Once logged in, you get a new dropdown at the top right to switch
between the keystone endpoints. This means you can configure an
Horizon installation to login to multiple
Further digging suggests that we might consider deprecating AVAILABLE_REGIONS
in Horizon and enhancing the multi-region support in Keystone. It wouldn’t take
a lot; the main points:
Implement the Regions API discussed back in the Havana time period -
I’m looking at implementing dynamically-configured multi-region support for
service federation, and the prior art on multi-region support in Horizon is
pretty sketchy. This thread:
http://lists.openstack.org/pipermail/openstack/2014-January/004372.html
is the only real discussion I’ve found, and
On Wed, May 13, 2015 at 3:24 PM, Mathieu Gagné mga...@iweb.com wrote:
When using AVAILABLE_REGIONS, you get a dropdown at login time to choose
your region which is in fact your keystone endpoint.
Once logged in, you get a new dropdown at the top right to switch
between the keystone
16 matches
Mail list logo
