Bug 1041971

Summary:	[RFE][horizon]: Need ability to evacuate host in syspanel
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	aberezin, ajeain, aortega, jpichon, markmc, mrunge, rhos-flags, slong, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/evacuate-host
Whiteboard:	upstream_milestone_juno-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	python-django-horizon-2014.2-4.el7ost	Doc Type:	Enhancement
Doc Text:	An admin user can now evacuate a compute host using the dashboard. Two tabs now provide information for hypervisors: 'Hypervisor' and 'Compute Host' (Admin > Hypervisors). If a host is down, an 'Evacuate Host' action is now visible for it on the Compute Host tab (providing a modal window to perform the evacuation).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 14:54:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 20:22:06 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/evacuate-host.

Description:

Syspanel should provide functionality to migrate all instances off a host (evacuate host).

Specification URL (additional information):

None

Comment 3 Ido Ovadia 2014-10-27 09:52:47 UTC

Test plan need review:
https://tcms.engineering.redhat.com/plans/printable/?plan=15523

Comment 4 Matthias Runge 2014-10-28 08:06:13 UTC

Looks good for me Ido.

Comment 7 errata-xmlrpc 2015-02-09 14:54:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0154.html