Open Stack

>
> In many cases the users I've spoken to who are looking for a live path out
> of nova-network on to neutron are actually completely OK with some "API
> service" downtime (metadata service is an API service by their definition).
> A little 'glitch' in the network is also OK for many of them.
>
> Contrast that with the original proposal in this thread ("snapshot VMs in
> old nova-network deployment, store in Swift or something, then launch VM
> from a snapshot in new Neutron deployment") - it is completely unacceptable
> and is not considered a migration path for these users.
>

There have been several discussions and ideas over time. I've tried to
collect as many as I've had exposure to on the whiteboard here:
https://blueprints.launchpad.net/neutron/+spec/nova-to-quantum-upgrade

Generally speaking we've all agreed before that while zero downtime would
be great, minimal downtime would be just fine. If it means a little API
downtime and some packet loss while an instance is replugged (maybe doing a
suspend while this happens would be safer) then it's still a big win.
Having to snap, delete and redeploy is less desirable but if there's an
automated process for that which can be controlled by the user (not the
admin) then that may be ok too.

Best regards,

Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140806/ebbeddb1/attachment.html>