[openstack-dev] [cinder] How do we prevent the user to directly call os-reserve?

Clay Gerrard clay.gerrard at gmail.com
Wed Sep 12 07:41:17 UTC 2012

On Tue, Sep 11, 2012 at 11:08 PM, Rongze Zhu <zrzhit at gmail.com> wrote:
> In your solution, there are two instances of cinder-api, Are
> there race conditions? Can I start two instances of cinder-api in the same
> host?

Yeah, I mean I don't see how it could be worse than load balancing two
instances of cinder-api.  You can change the port the service binds to
in the config, so I've had two instances running on the same host -
there's some init script work to do there though.

This is just one idea I had, anyone else got a better plan to address
Rongze's original question?

On Tue, Aug 28, 2012 at 4:19 AM, Rongze Zhu <zrzhit at gmail.com> wrote:
> Hi Everyone, I have a question about cinder volume actions.
> There are some APIs in
> cinder/api/openstack/volume/contrib/volume_actions.py, for example,
> os-attach/os-detach/os-reserve/os-unreserve/os-initialize_connection/os-terminate_connection/os-volume_upload_image.
> I know that they are only used for nova, but if a user to call directly
> os-reserve by HTTP REST, it will cause confusion, because os-reserve will
> change volume status in database. How do we prevent the user to directly
> call os-reserve?

More information about the OpenStack-dev mailing list