Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Thu, 17 Jan 2013 06:54:22 +0000 (UTC)
From: "Radhika Nair (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12627994.1358405577723.150743.1358405662383@arcas>
In-Reply-To: <JIRA.12627994.1358405577723@arcas>
References: <JIRA.12627994.1358405577723@arcas>
Subject: [jira] [Created] (CLOUDSTACK-997) Improve documentation of
 assignVirtualMachine API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Radhika Nair created CLOUDSTACK-997:
---------------------------------------

             Summary: Improve documentation of assignVirtualMachine API
                 Key: CLOUDSTACK-997
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-997
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Doc
    Affects Versions: 4.0.0
            Reporter: Radhika Nair
            Priority: Minor
             Fix For: 4.1.0


(Requested by Abhinandan Prateek) 

Add more info about this API, as it is not well understood and users contact the engineers to ask for explanation. 

assignVirtualMachine: To assign a VM from one account to another (admin API). 

Example Usage: 

http://127.0.0.1:8096/client/api?command=assignVirtualMachine&domainid=2&account=rest&virtualMachineId=15&networkids=204&response=json 


The command allows you to assign a VM from one account to another under same domain. Right now this feature is available for Basic zones with security groups and Advance zones with guest networks. 

The VM is restricted to move between accounts under same domain. 


Params: 

virtualMachineId: The vm id under consideration 

domainId, account: The domina id and account name of the new owner. 

networkIds: The network id list of the new networks in which the moved VM will participate. In case no network ids are provided the VM will be part of the default network for that zone. In case there is no network yet created for the new account the default network will be created. 

securitygroupids: The security group list is required if you are moving a VM in a basic networked zone. The new security group will be part of VM after the move. In case no security groups are provided the VM is part of the default security group. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira