cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yiping Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9596) migrateVirtualMachine API does not respect affinity group assignment
Date Tue, 15 Nov 2016 19:12:59 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667977#comment-15667977
] 

Yiping Zhang commented on CLOUDSTACK-9596:
------------------------------------------

Since we can not assume the target host for migration is always from results of findHostForMigration
api call, we have to make sure that migrateVirtualMachine itself will be aware of affinity
group assignment, and explicitly respect or ignore affinity group assignment, based on the
proposal new parameter value.


As for findHostForMigration api,  I am surprised that it also does not respect affinity group
assignments.  IMHO, it should.

> migrateVirtualMachine API  does not respect affinity group assignment
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9596
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9596
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.8.0
>         Environment: RHEL 6.7 + XenServer 6.5
>            Reporter: Yiping Zhang
>
> Using  migrateVirtualMachine API, for example using cloudmonkey, one can move two VM
instances in the same anti-host affinity group on to the same host.
> There are two possible outcomes for the migration of instances belonging to the same
anti-host affinity groups onto the same host:
> 1) ignore affinity group assignment, migration succeeds (current api behavior)
> 2) respect affinity group assignment, migration fails with message that action is  forbidden
by affinity group assignment.
> The best solution is to add another parameter to the API call to toggle api's behavior.
  For example, if the second behavior is chosen as default, then a parameter "force=true"
( where default value is false for param "force") will force the migration to ignore affinity
group assignment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message