Ask Your Question
0

does live migration always run rsync even if storage is glusterfs?

asked 2013-08-05 13:47:32 -0500

Sifty gravatar image

updated 2013-08-05 13:50:48 -0500

When live migrating an instance between servers using glusterfs, rsync is used to migrate the image each time even though all nodes have access to the same glusterfs storage drive. The /var/lib/nova/instances folder is a glusterfs mount and works perfectly. Is there a way to prevent the live migration rsync'ing the image each time and just checking the image exists, or is that just the way openstack works ?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-08-06 03:52:46 -0500

unmesh-gurjar gravatar image

After checking the source code for determining if Compute has a shared storage ( https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L3810 ), I doubt that in your case the 'instances_path' in nova.conf for the Compute hosts are different (assuming that the shared storage is correctly configured). If the 'instances_path' are the same, a file created on that path from source Compute must be available at same path on the destination Compute; in which case, 'mv' would be used instead of an 'rsync'.

Hope it helps!

edit flag offensive delete link more

Comments

Thanks for the code reference, I am using the Grizzly CentOS RPMs which greatly differ from the master branch so it looks like live migration is something that is still being worked on. The line on 3810 does not exist in the RPM source code.

Sifty gravatar imageSifty ( 2013-08-06 07:08:59 -0500 )edit

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: 2013-08-05 13:47:32 -0500

Seen: 299 times

Last updated: Aug 06 '13