Ask Your Question
1

Is live migration possible without a shared mount when the source of the VM is a cinder volume?

asked 2014-02-27 15:45:06 -0600

ajeffrey gravatar image

updated 2014-02-27 22:08:27 -0600

Environmental details:

Openstack vers/environment: Devstack in multi mode using the Netapp C-Mode NFS driver for Cinder but with no shared mounts for the /opt/stack/data/nova/instances directory.

Hypervisor: KVM/QEMU VM: booted from a cinder 2GB disk created from the Cirros image and set bootable Command: nova live-migration 26e1cea3-644c-4934-a19e-67e98b6ddf90 ubuntu2 Error in n-cpu.log: InvalidSharedStorage: ubuntu is not on shared storage: Live migration can not be used without shared storage

Since cinder by definition is on shared storage shouldn't this command work using the netapp nfs storage which is already available to both nodes?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2014-03-05 11:03:53 -0600

figless gravatar image

i'm seeing the same behaviour. i'm trying to configure NetApp NFS (7mode), using havana. I have configured cinder correctly, I can create volumes and boot instances from them.

Trying to perform a live migration for a VM running on http://server1.example.com to http://server2.example.com shows the following in the server1.example.com:/var/log/nova/compute.log

"InvalidSharedStorage: http://server2.example.com is not on shared storage: Live migration can not be used without shared storage."

On both http://server[1-2].example.com the NFS volume is mounted (as /var/lib/nova/mnt/5547cefd223df00df6e37cdd7e810415)

Any suggestions as to why this is failing would be greatly appreciated.

edit flag offensive delete link more

Comments

have you tried the --block_migrate option? It works for me without 'shared storage' i.e. nfs mounted /../../images dir.

ajeffrey gravatar imageajeffrey ( 2014-03-07 09:47:53 -0600 )edit

--block-migrate on shared storage can be troublesome - it's really made for non-shared filesystems.

jamesvautin gravatar imagejamesvautin ( 2014-12-25 03:01:29 -0600 )edit
0

answered 2014-02-27 21:40:40 -0600

ajeffrey gravatar image

updated 2014-02-27 21:42:21 -0600

Update: When i use the --block_migrate option the live migration succeeds (which is nice but unexpected). This seems inconsistent with the operation that apparently occurred because there was nothing to migrate (with a cinder volume residing on a NetApp NFS share being served to the hypervisor on two compute nodes). What actually got moved was the vm and it's memory, processes, etc. Is this the recommended way to perform this operation? It seems like the first command without the --block_migrate option should have performed a pre-check to see if shared cinder storage for the vm was there and if so perform a standard migration.

edit flag offensive delete link more

Comments

live block migration on shared storage is really not ideal - it would be better to understand why the shared storage is not recognized as such.

jamesvautin gravatar imagejamesvautin ( 2014-12-25 03:00:33 -0600 )edit
0

answered 2014-06-17 01:35:50 -0600

Hi, i am doing the same thing. can you gide me please? i have two OpenStack cloud with two computes node. i want to migrate VM from one compute to another

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-02-27 15:45:06 -0600

Seen: 2,592 times

Last updated: Jun 17 '14