[openstack-dev] Quantum and keystone auth
dan at nicira.com
Mon Apr 1 22:45:46 UTC 2013
On Mon, Apr 1, 2013 at 11:13 AM, Thomas Goirand <zigo at debian.org> wrote:
> Unless I've dreamed, it appears that the way to configure Quantum
> keystone auth has changed from Folsom to Grizzly. It used to be in
> /etc/quantum/api-paste.ini in filter:authtoken, and now it is in
> I wonder what was the reason for such a change, which for sure, will
> break upgrades in ways or others. [I'm not so sure yet how I will deal
> with that at the packaging level, but what I'm sure, is that if I want
> to address this upgrade problem, it will increase my packaging complexity.]
As Eugene mentioned in his reply, this is not expected to break backward
compatibility, and in fact, your old packaging should continue to work
fine. The only change committed was a change to the example, as it is now
valid to put the config in either location, but telling users to put it in
quantum.conf seemed more straightforward.
> Also, l3_agent.ini used to have keystone auth things as well. It's now
> completely gone. But there is now metadata_agent.ini. Is it that l3
> reads its config from this file now, with Grizzly? Or does it read it
> from /etc/quantum/quantum.conf?
The l3-agent no longer requires keystone auth, as it uses RPC to fetch this
The metadata_agent.ini is actually for a new agent that is un-related to
the keystone changes. This is new functionality in Grizzly to handle
metadata with overlapping IP addresses. We have a doc bug tracking
details on how to install this agent (
https://bugs.launchpad.net/openstack-manuals/+bug/1099573) but in the
meantime you could probably look at devstack or the Ubuntu packages if
you're interested in how it is used + configured).
> Finally, is there some kind of release notes available explaining all
> these (quite disruptive) changes?
> Thomas Goirand (zigo)
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
Nicira, Inc: www.nicira.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev