KVM host maintenance support

Registered by dan kim

similar blueprient was already registerd by Oshrit Feder on 2013-01-23.
Here.
https://blueprints.launchpad.net/nova/+spec/host-maintenance
Sadly, it is not on going althrough the system administrator needs "host maintenance mode with kvm"

Now, On ice-house term, I think the concept of the blueprint should be changed.

I suggest Host class should be in libvirt driver and It implements set_host_enabled() and host_maintenance_mode() like xenapi and vmware cases.
set_host_enabled() method should control nova-compute service and nova-network (if it works in multi dhcp mode).
host_maintenance_mode() method should evacuates vms to other hosts with live-migration (or other way)

Blueprint information

Status:
Complete
Approver:
Vish Ishaya
Priority:
Undefined
Drafter:
dan kim
Direction:
Needs approval
Assignee:
dan kim
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Russell Bryant

Related branches

Sprints

Whiteboard

Yes, I'd like this supported in the libvirt driver. However, I don't necessarily agree with the approach listed. In particular, at least automatically doing any evacuation should not be included. Some refining of the design and approach is needed here. Feel free to start a discussion on openstack-dev if you'd like to go over it. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyYes, I'd like this supported in the libvirt driver. However, I don't necessarily agree with the approach listed. In particular, at least automatically doing any evacuation should not be included. Some refining of the design and approach is needed here. Feel free to start a discussion on openstack-dev if you'd like to go over it. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

It has been quite a long time since this was updated, so I'm assuming it's not actively worked on. Looking at this again, I'm not sure what value this adds over just doing a service-disable and then issuing a migration or evacuate API call, anyway ... --russellb

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.