Enable live migration to rely on nova-scheduler

Bug #1691056 reported by Hidekazu Nakamura on 2017-05-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aditi sharma

Bug Description

Currently, destination_node is mandatory for migrate action.
But live migration in Nova can rely on nova-scheduler for it's destination node.

It is useful destination node is optional when migration type is live:
If destination node is not given, destination node can be chosen by nova-scheduler.
If destination node is given, migrate action will do as the same as current behavior.

refererence: https://developer.openstack.org/api-ref/compute/?expanded=migrate-server-migrate-action-detail

aditi sharma (adi-sky17) on 2017-05-16
Changed in watcher:
assignee: nobody → aditi sharma (adi-sky17)
description: updated

Fix proposed to branch: master
Review: https://review.openstack.org/476369

Changed in watcher:
status: New → In Progress

Reviewed: https://review.openstack.org/476369
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=6731851383fef218e02d25edeb4f3c0cf6853c0c
Submitter: Jenkins
Branch: master

commit 6731851383fef218e02d25edeb4f3c0cf6853c0c
Author: aditi <email address hidden>
Date: Thu Jun 22 06:25:39 2017 +0000

    Enable migration to rely on nova-scheduler

    This patch removes the requirement to specify destination node,
    for migrate action. There can be some strategies that wants to rely
    on nova-scheduler for destination node. It will not impact any current
    strategy behavior.

    Change-Id: Ia12b2f0b8369e632a7959b28e485d86b6cff83e9
    Closes-Bug: #1691056

Changed in watcher:
status: In Progress → Fix Released

This issue was fixed in the openstack/watcher 1.3.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers