deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-567) Not all instance statuses supported by OpenStack driver
Date Fri, 14 Jun 2013 08:32:20 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683204#comment-13683204
] 

Marios Andreou commented on DTACLOUD-567:
-----------------------------------------

Hi Kamil,                                                                  
                                                                           
since Deltacloud is an abstraction API we 'map' the various VM power states from each individual
cloud provider to a set of power state abstractions. As you note, these include 'RUNNING',
'PENDING', 'STOPPED' etc [1].
                                                                           
For those states that you list as unsupported - do you think we can map them to the existing
Deltacloud states? If so can you suggest a mapping (either here or with a patch). For example,
perhaps we could map 'RESIZE' and 'REBUILD' to 'PENDING'. For those that don't 'fit' into
any of the current Deltacloud states - can you suggest new states to cover those?
                                                                           
With respect to the OS-EXT-STS:task_state and OS-EXT-STS:vm_state - indeed we don't consider
those at all. However I did recently add the ability to grab those values as part of a server
description in the ruby-openstack rubygem [2][3] - this is the gem that the Deltacloud OpenStack
driver uses to 'talk' to the OpenStack services. I'm not sure where/how to report this information
however - do you have any suggestions? I think perhaps adding a 'provider_ext' attribute to
the server model [4] which would be a hash (key=>value) to capture this type of 'extra'
information?
                                                                           
thanks, marios                                                             
                                                                           
[1] http://deltacloud.apache.org/instance-states.html                      
[2] https://github.com/ruby-openstack/ruby-openstack/pull/26               
[3] https://github.com/marios/ruby-openstack/commit/d23681d1e46587eae217853b2dd8cdad01a05bf9#L1R75
[4] https://github.com/deltacloud/deltacloud-core/blob/master/server/lib/deltacloud/models/instance.rb
                
> Not all instance statuses supported by OpenStack driver
> -------------------------------------------------------
>
>                 Key: DTACLOUD-567
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-567
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Kamil Figiela
>
> OpenStack defines multiple instance stauses. Only few of them are supported by DeltaCloud
driver.
> Currently supported statuses are:
> * REBOOT, HARD_REBOOT => REBOOT
> * DELETED => STOPPED
> * BUILD => PENDING
> * ERROR => ERROR
> * ACTIVE => RUNNING
> Not supported statuses, but present in OpenStack spec, are:
> * PASSWORD
> * REBUILD
> * RESCUE
> * RESIZE
> * REVERT_RESIZE
> * SHUTOFF
> * SUSPENDED
> * UNKNOWN
> * VERIFY_RESIZE
> Additionally current OpenStack version includes RackSpace extensions (http://docs.rackspace.com/servers/api/v2/cs-gettingstarted/content/show_server.html)
that provide additional info on instance state.
>  * OS-EXT-STS:task_state
>  * OS-EXT-STS:vm_state

--
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