← Back to team overview

openstack team mailing list archive

Re: moving glance service

 

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-05-02 14:06:46 INFO nova.api.openstack [req-82f4ccb3-3d2e-4eca-a603-9a6ae7d74bd2 507c88590f1346f38004fba8c6a99f01 d104a47607bb4a7c9db341650d32fab5] http://10.10.10.1:8774/v1.1/d104a47607bb4a7c9db341650d32fab5/images/detail returned with HTTP 500
where 10.10.10.1 is the *old* glance instance IP and new one is supposed to be 10.10.10.2. 

When I spin up openstack-glance-{api,registry} on 10.10.10.1 - everything works as it should and images are stashed over on 10.10.10.2, but it's confusing why I need to run it with the old IP and can't just disable it?


>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 missing service on original node.
>Can somebody please confirm that (in Folsom) those steps are sufficient:
>* add new endpoint with updated URLs
>* remove old endpoint
>* shutdown original glance
>* startup new glance
>* ...profit? ;-)


Follow ups

References