Bug 1043706

Summary:	[RFE][nova]: Validate target host with scheduler hints for live migration optionally
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-nova	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:	Ami Jeain <ajeain>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	unspecified	CC:	markmc, ndipanov, sgordon, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged, Upstream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/validate-targethost-live-migration
Whiteboard:	upstream_milestone_none upstream_status_started upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-05 12:52:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1041140

Description RHOS Integration 2013-12-17 00:44:08 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/validate-targethost-live-migration.

Description:


This is related to blueprint https://blueprints.launchpad.net/openstack/?searchtext=live-migration-to-conductor. The blueprint is trying to move live migration logic to nova-conductor, this is a good direction.

But for live migration with target host, the current implementation is that once target host was specified for live migration, then the conductor will only validate the host by nova compute. For some cases, there is also a need to validate the host in nova scheduler, as there might be some requirement that customer want to validate the target host for live migration with some scheduler filters.

In the current implementation the user can specify scheduler hints related to the placement of the instance. Those scheduler hints are used when the instance run for the first time and they are ignored afterwards. In order to achieve the validation of the target host we need to persist scheduler hints into the database which makes it possible to verify that the target host passes scheduler filters/hints during live migration.

There are some cases when this verification during live migration will lead the system locked and the user will not be able to migrate an instance, so a new option should be added in order to force the migration without verifying the target host by nova-scheduler.

Specification URL (additional information):

None