deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-214) instance start/stop/destroy makes many calls to backend (depending on provider)
Date Thu, 17 May 2012 01:04:07 GMT


Dies Koper commented on DTACLOUD-214:

That solution seemed so obvious I thought it had been considered and dismissed already :)

That would work fine for the FGCP driver, it will receive an illegal state error from the
cloud and can convert it to the HTTP 405 error (Method is not Allowed) as is generated now.
I can submit a patch to take out the current code and implement and test this for the FGCP
driver, but won't be able to do so for the other providers.
> instance start/stop/destroy makes many calls to backend (depending on provider)
> -------------------------------------------------------------------------------
>                 Key: DTACLOUD-214
>                 URL:
>             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
> 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:!default.jspa
For more information on JIRA, see:


View raw message