cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1217) Need to refactor cloud-engine createVM flow to handle Storage and Network allocation separately.
Date Fri, 22 Mar 2013 19:59:16 GMT

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

Chip Childers updated CLOUDSTACK-1217:
--------------------------------------

    Fix Version/s:     (was: 4.1.0)

Clearing fix-version, since this doesn't seem to be something that got done for 4.1.
                
> 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
>
> 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

Mime
View raw message