Dmitry Makovey a écrit :
>>Hi,
>>
>>Nova does not get the glance endpoint from keystone, this is a
>parameter in nova.conf : either glance_host + glance_port or
>glance_api_servers
>>
>>Hope this helps.
>
>
>It sure did! Thank you.
>
>I'm puzzled though why do we have the same information rep
>Hi,
>
>Nova does not get the glance endpoint from keystone, this is a parameter in
>nova.conf : either glance_host + glance_port or glance_api_servers
>
>Hope this helps.
It sure did! Thank you.
I'm puzzled though why do we have the same information replicated in bazillion
places? We've got
Hi,
Nova does not get the glance endpoint from keystone, this is a parameter in
nova.conf : either glance_host + glance_port or glance_api_servers
Hope this helps.
Dmitry Makovey a écrit :
>now that I'm at the office - here's the error I'm getting following my
>original instructions:
>
>201
now that I'm at the office - here's the error I'm getting following my original
instructions:
2013-05-02 14:06:46 10310 TRACE nova.api.openstack CommunicationError: Error
communicating with http://10.10.10.1:9292 [Errno 111] ECONNREFUSED
2013-05-02 14:06:46 10310 TRACE nova.api.openstack
2013-0
Hi, after playing a bit with all-in-one setup I'm slowly moving services out to
dedicated nodes. Got my Cinders sorted etc. However trying to move glance it
seems that old glance endpoint gets cached someplace thus when I plug in new
endpoint and remove old one I get all kinds of errors about mi
5 matches
Mail list logo