[libvirt] [RFC][PATCH] virt-manager calls migration API

Hi, I just make the proto patch that calls migration API from virt-manager. Form unity point of view, This proto patch adds Migrate in as same layer as operations for the Domain. Fisrt, this patch adds "Migrate" to the right-click menu when selected a domain. Run Run Pause Pause Shutdown Shutdown --------- ---> -------- Open(O) Migrate -------- Open(O) When "Migrate" selected, it goes on new window open which shows available(have been connecting) hosts. Of course, I have been knowing that there is Drag&Drop way. By the way, (1)It is necessary to migrate a domain that users modify an environmental setting. (ex. for XenD xend-config, ...) And (2)I think it that is necessary to improve usability that there is "precheking" beofre migrating. (ex. same cpu family/processor number?, enough free memory?, ...) Do you already have a idea that virt-manager servies above (1)(2) ? Finally, I understand that migrated domain's state switches Running and Shutoff alternately, because current virt-maneger manages domains by UUID. Is there a plan that this problem is solved? virtManager/domain.py | 27 ++++++ virtManager/engine.py | 82 ++++++++++++++++++++ virtManager/hostlist.py | 172 ++++++++++++++++++++++++++++++++++++++++++ virtManager/manager.py | 27 ++!!!! vmm-hostlist.glade | 195 ++++++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 488 insertions(+), 15 modifications(!) Thanks, Shigeki Sakamoto.

S.Sakamoto wrote:
Hi, I just make the proto patch that calls migration API from virt-manager. Form unity point of view, This proto patch adds Migrate in as same layer as operations for the Domain. Fisrt, this patch adds "Migrate" to the right-click menu when selected a domain.
You probably want to send this to et-mgmt-list, which is where virt-manager development happens, but I will comment on one thing below...
(2)I think it that is necessary to improve usability that there is "precheking" beofre migrating. (ex. same cpu family/processor number?, enough free memory?, ...)
I sent an e-mail last month with proposals for doing this within libvirt. I put up all of the information I have in the libvirt wiki here: http://wiki.libvirt.org/page/TodoPreMigrationChecks (if you have more ideas, please add them). In short, yes, we really want to do some pre-migration sanity checking, and I think that libvirt is probably the right place to do them. Someone needs to think about it further, though, and then sit down and implement it. Chris Lalancette

You probably want to send this to et-mgmt-list, which is where virt-manager development happens,
OK. For this, I tried to hear in et-mgmt-list.
I sent an e-mail last month with proposals for doing this within libvirt. I put up all of the information I have in the libvirt wiki here:
Thank you for your information. I see above libvirt wiki and I have a few idea adding checks within libvirt. These point of view are Guest and Host sanity in BASIC CHECKS. How about this points ? 1)Guest sanity is checking whether already existing or not on the destination. Otherwise the uniqueness of the domain(UUID, name) are lost. * I think that it is right to check this in libvirt. How do you think this ? 2)Host sanity is checking whether a migration flag is ON at each virtualization. Thanks, Shigeki Sakamoto.
participants (2)
-
Chris Lalancette
-
S.Sakamoto