openstack team mailing list archive

["Day, Phil" <philip.day@xxxxxx>]

Thanks Vish,

So are both maintained at present - for example if there was a bug fix to volume creation would it be applied to the VolumeController in both places ?

I'm just trying to work out how best to provide compatibility as we roll forwards - seems like for some period we may need to have both the compute extension and the Volume API server running.

Phil

From: Vishvananda Ishaya [mailto:vishvananda@xxxxxxxxx]
Sent: 10 September 2012 18:08
To: Day, Phil
Cc: openstack@xxxxxxxxxxxxxxxxxxx (openstack@xxxxxxxxxxxxxxxxxxx) (openstack@xxxxxxxxxxxxxxxxxxx)
Subject: Re: [Openstack] Which volume API in Nova ?

Prior to creating our own endpoint for volumes inside of nova (one of the first steps in the transition that happened right before the essex release), volume control was done by compute extensions. We left these extensions in case anyone was using them. They should be roughly functionally equivalent, but the compute extension is located at:
http://host:8774/os-volumes (host and port of the compute endpoint)
and the volume api is at:
http://host:8776/volumes (host and port of the volume endpoint)

Vish

On Sep 10, 2012, at 8:34 AM, "Day, Phil" <philip.day@xxxxxx<mailto:philip.day@xxxxxx>> wrote:


Hi Folks,

I know things are in transition right now from Nova to Cinder, but can someone shed light on the difference between "api.openstack.compute.contrib.volumes" and "api.openstack.volume" ?

Thanks
Phil
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp