[Openstack-operators] Grizzly: live-migration with attached volume?
steve.cousins at maine.edu
Fri Sep 12 19:10:03 UTC 2014
Thanks for the information. I just tried doing it with a VM with only 2
cores and it has been working fine. So it seems that it may be specific to
the number of cores that are involved. I'll try with 4 to see if that works
ok. Thankfully we don't have many 8-core machines but we still have the
need to migrate them for maintenance.
Does this core-specific information help to figure out what the problem is?
On Fri, Sep 12, 2014 at 2:31 PM, Jonathan Proulx <jon at jonproulx.com> wrote:
> On Fri, Sep 12, 2014 at 1:44 PM, Stephen Cousins
> <steve.cousins at maine.edu> wrote:
> > Does anyone live-migrate VM's successfully when volumes are attached?
> My setup is significantly different so probably not terribly helpful,
> but to answer the question I did do live migrations with Volumes
> attached on my Grizzly cloud (since upgraded to Icehouse). We don't
> have shared storage for the ephemeral disks and our Volumes are iSCSI
> attached (from an equallogic san), so something like:
> nova live-migration --block-migrate <server> [<host>]
> I wouldn't say it was 100% but the volume piece wasn't a problem. Well
> once I figured out in my case I needed to flip some bits on the SAN
> side to allow multiple logins to the same target as source and
> destination are both connected during a migration, but I wouldn't
> expect that to be an issue with NFS
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators