[jira] [Issue Comment Deleted] (CLOUDSTACK-9596) migrateVirtualMachine API does not respect affinity group assignment

["Swen Brueseke (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swen Brueseke updated CLOUDSTACK-9596:
--------------------------------------
    Comment: was deleted

(was: +1 for adding a new parameter
API should return failed, because of affinity group assigment and in UI you should be able to use checkbox to force a migration as root admin.)

> 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)