You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Prachi Damle (JIRA)" <ji...@apache.org> on 2013/02/08 22:51:14 UTC
[jira] [Created] (CLOUDSTACK-1217) Need to refactor cloud-engine
createVM flow to handle Storage and Network allocation separately.
Prachi Damle created CLOUDSTACK-1217:
----------------------------------------
Summary: Need to refactor cloud-engine createVM flow to handle Storage and Network allocation separately.
Key: CLOUDSTACK-1217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1217
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.1.0
Reporter: Prachi Damle
Assignee: Prachi Damle
Fix For: 4.1.0
The new cloud-engine OrchestrationService :: createVirtualMachine() and createVirtualMachineFromScratch() API's take in parameters needed to allocate a VM, volume and network.
Instead it should just take care of allocating a VM. To allocate volume and network, we should have separate APIs in OrchestrationService like createVolume() - attachVolume() and createNetwork()/ allocateNic() etc.
This way we need not carry volume/network parameters inside VM object during create VM.
--
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