You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2015/08/12 08:21:45 UTC

[jira] [Updated] (CLOUDSTACK-7369) assignVirtualMachine API name not intuitive

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

Rajani Karuturi updated CLOUDSTACK-7369:
----------------------------------------
    Fix Version/s:     (was: 4.6.0)

> assignVirtualMachine API name not intuitive
> -------------------------------------------
>
>                 Key: CLOUDSTACK-7369
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7369
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.5.0
>            Reporter: Nitin Mehta
>
> I just went to a meetup and was talking to [~jlkinsel] who was talking about moving vms from one account to another and was doing it manually through a huge set of db queries. We already had this api in place since 3.0.x but folks are not aware of it due to unintuitive api name. I can think of 2 solutions at the moment.
> 1. Create another api say changeVmOwnership and internally point it to the same logic as assignVirtualMachine. Mark assignVirtualMachine as deprecated api name for 5.0
> 2. OR in the api documentation name it as changeVmOwnership so that folks would know such functionality exists and is available through APIs



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