On Fri, 2012-06-15 at 20:54 -0400, Lars Kellogg-Stedman wrote:
Thanks for the reply, makes sense. Just to make sure I understand
things, it sounds like Nova does not currently query Keystone for
endpoints and continues to rely on explicit configuration (or to
rephrase your answer, the reason
What's the point of a service catalog (list of endpoints) if we don't want
to use it?! Looking up endpoints should be a cacheable request and in the
grand scheme of things -- low impact.
Nate
On Jun 18, 2012 10:13 AM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Fri, 2012-06-15 at
On Mon, 2012-06-18 at 10:18 -0400, Nathanael Burton wrote:
What's the point of a service catalog (list of endpoints) if we don't
want to use it?! Looking up endpoints should be a cacheable request
and in the grand scheme of things -- low impact.
We do use the service catalog, quite
I don't see nova-network running...
And in fact, that seems to have been at the root of a number of
problems. Thanks! With some work over the weekend I'm now successfully
booting instances with networking using the Flat network manager.
Great.
It wasn't clear from the documentation that
Thus, I suspect that nova may not even use the Keystone endpoints...
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the asynchronous, distributed nature of OpenStack,
an endpoint
On Mon, 2012-06-18 at 10:41 -0400, Lars Kellogg-Stedman wrote:
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the asynchronous, distributed nature of OpenStack,
an endpoint directory
On 06/18/2012 10:41 AM, Lars Kellogg-Stedman wrote:
Thus, I suspect that nova may not even use the Keystone endpoints...
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the
Howdy all,
I've spent the past few days slogging through the initial steps of
getting OpenStack and running and I seem to have hit a wall. If this
isn't the right list for this question, please feel free to direct me
elsewhere.
I have two systems running the OpenStack components right now. The
Well, apologies for the stupid subject line. In the interests of
sewing as much confusion as possible, here's the question that was
supposed to go along with that subject:
nova.conf appears to sport several configuration options related to
glance, including:
- glance_host
- glance_port
-
Hey Lars,
Sadly I don't have much in the way of a solution for you, but I do have
some suggestions. Comments inline.
On 6/15/12 4:17 PM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
Howdy all,
I've spent the past few days slogging through the initial steps of
getting OpenStack and
I'm used to using rabbit, but I did notice you didn't include a
nova-scheduler in your list above...
There is a nova-scheduler service running on the controller:
Binary Host Zone Status
State Updated_At
nova-cert
I don't really know anything about AMQ or how OpenStack utilizes the
message broker. Are there any commands I can run that would exercise
the message broker and confirm whether or not it is working correctly?
For what it's worth:
qpid provies a test suite (qpid-python-test that appears to
Hi Lars -
Sounds like you're really looking for a conceptual understanding and I
like that! Keystone does maintain the service catalog, and the Image
service (glance) needs specific entries. See
http://docs.openstack.org/essex/openstack-compute/install/yum/content/keystone-concepts.html.
I
On Fri, 2012-06-15 at 16:26 -0400, Lars Kellogg-Stedman wrote:
nova.conf appears to sport several configuration options related to
glance, including:
- glance_host
- glance_port
- glance_api_servers
These seem suspiciously similar.
Indeed.
Do they do the same thing?
Yes, they do.
The reason these options have not gone away is probably a combination of
supporting non-Keystone authentication and general programmer laziness…
Kevin,
Thanks for the reply, makes sense. Just to make sure I understand
things, it sounds like Nova does not currently query Keystone for
endpoints
15 matches
Mail list logo
