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

Hutson Betts reassigned LIBCLOUD-148:
-------------------------------------

    Assignee: Hutson Betts
    
> OpenNebula's OCCI interface returns the state ACTIVE, which is unknown to 
> libcloud
> ----------------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-148
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-148
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>    Affects Versions: 0.7.1
>         Environment: OpenNebula 3.2
>            Reporter: Erik Torres Serrano
>            Assignee: Hutson Betts
>
> I have found that OpenNebula 3.2 returns the state ACTIVE for virtual 
> machines that are actually running:
> For example, consider this query, using the OCCI interface:
> username@hostname:~$ wget http://hostname:4567/compute/347 
> --http-user=username --http-password=0000000000000000000000000000000000 
> --auth-no-challenge -qO-
> <COMPUTE 
> href="http://hostname:4567/compute/347";><ID>347</ID><CPU>1</CPU><MEMORY>256</MEMORY><NAME>vps1</NAME><STATE>ACTIVE</STATE><DISK
>  id="0"><STORAGE href="http://hostname:4567/storage/14"; 
> name="Ubuntu-11.10"/><TYPE>DISK</TYPE><TARGET>hda</TARGET></DISK><NIC><NETWORK
>  href="http://hostname:4567/network/0"; 
> name="internal"/><IP>10.0.0.3</IP><MAC>50:00:00:00:00:03</MAC></NIC></COMPUTE>
> Now, the same query, but using the native interface:
> username@hostname:~$ onevm list
>     ID USER     GROUP    NAME         STAT CPU     MEM        HOSTNAME        
> TIME
>    347 username  users    vps1         runn   0  268.2M     hostname 08 
> 01:32:13
> The same machine has two different states: running for the native interface, 
> and active for OCCI. However, libcloud does not consider the active state, 
> and returns unknown.
> Kind regards,
> Erik

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

        

Reply via email to