Open Stack

Jay Pipes on 16 July 2012 18:31 wrote:
 
> On 07/16/2012 09:55 AM, David Kranz wrote:


> Sure, although in this *particular* case the Cinder project is a
> bit-for-bit copy of nova-volumes. In fact, the only thing really of
> cause for concern are:
> 
> * Providing a migration script for the database tables currently in the
> Nova database to the Cinder database
> * Ensuring that Keystone's service catalog exposes the volume endpoint
> along with the compute endpoint so that volume API calls are routed to
> the right endpoint (and there's nothing preventing a simple URL rewrite
> redirect for the existing /volumes calls in the Compute API to be
> routed
> directly to the new Volumes endpoint which has the same API

Plus stand up a new rabbit HA server. 
Plus stand up a new HA database server. 
Plus understand the new availability constraints of the nova<->cinder interface point
Plus whatever else I haven't scoped yet

And there are bug fixes and correctness fixes slowly going into Cinder, so it is not a bit--for-bit copy any longer...