deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DTACLOUD-214) instance start/stop/destroy makes many calls to backend (depending on provider)
Date Mon, 21 May 2012 02:15:40 GMT

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

Dies Koper updated DTACLOUD-214:
--------------------------------

    Attachment: 0001-leave-it-up-to-the-driver-to-return-405-error-Method.patch

patch to remove state check and let the driver take care of returning the correct error code.
Includes change required for FGCP driver.
                
> instance start/stop/destroy makes many calls to backend (depending on provider)
> -------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-214
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-214
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Dies Koper
>            Assignee: David Lutterkort
>            Priority: Minor
>         Attachments: 0001-extract-code-to-check-instance-state-to-separate-met.patch,
0001-leave-it-up-to-the-driver-to-return-405-error-Method.patch
>
>
> Before performing an action on an instance, DC retrieves the current instance state to
confirm it is in a valid state to perform the requested action.
> It does this by calling the instance() API. On some drivers, at least FGCP's, this operation
makes a number of calls to the backend: one to get the instance attributes such as its name,
one to get the state, one to get its assigned public IP address(es), one to get the initial
password, etc.
> While all it needs is the state.
> If we extract and move the state retrieval code to a separate method we can override
it with more efficient calls for providers that benefit from it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message