You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Erik Torres Serrano (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 10:57:53 UTC
[dev] [jira] [Created] (LIBCLOUD-148) OpenNebula's OCCI interface returns
the state ACTIVE, which is unknown to libcloud
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
Priority: Minor
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
[dev] [jira] [Resolved] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts resolved LIBCLOUD-148.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
Patch has been applied.
> 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
> Fix For: 0.8.0
>
> Attachments: opennebula.diff
>
>
> 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
[dev] [jira] [Updated] (LIBCLOUD-148) OpenNebula's OCCI interface returns
the state ACTIVE, which is unknown to libcloud
Posted by "Erik Torres Serrano (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Torres Serrano updated LIBCLOUD-148:
-----------------------------------------
Priority: Major (was: Minor)
> 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
>
> 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
[dev] [jira] [Updated] (LIBCLOUD-148) OpenNebula's OCCI interface returns
the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts updated LIBCLOUD-148:
----------------------------------
Attachment: opennebula.diff
Patch to update the list of states for a compute node.
> 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
> Attachments: opennebula.diff
>
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Erik Torres Serrano (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199658#comment-13199658 ]
Erik Torres Serrano commented on LIBCLOUD-148:
----------------------------------------------
It seems that the ACTIVE state can be unfolded to such different things as RUNNING, SHUTDOWN or FAILURE:
http://doc.bonfire-project.eu/R2/reference/states-occi-resources.html
I don't know exactly how the unfolding works, but it will be great if libcloud could match and report these "internal" states. Definitely, this is a major improvement!
> 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
> Priority: Minor
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Erik Torres Serrano (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200377#comment-13200377 ]
Erik Torres Serrano commented on LIBCLOUD-148:
----------------------------------------------
Hi Hutson,
Thanks for your prompt response. Incredible fast solution!
Please, keep this going! You have a great project, and a great team.
Regards,
Erik
> 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
> Fix For: 0.8.0
>
> Attachments: opennebula.diff
>
>
> 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
[dev] [jira] [Commented] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200310#comment-13200310 ]
Hutson Betts commented on LIBCLOUD-148:
---------------------------------------
>From OpenNebula's documentation, the following are states that a VM can be transitioned to upon user request:
STOPPED
SUSPENDED
RESUME
CANCEL
SHUTDOWN
REBOOT # OpenNebula v3.2 only.
DONE
By reading their code, I can say that the following are the states a VM can exist in, at least as far as OCCI is concerned:
INIT
PENDING
HOLD
ACTIVE
STOPPED
SUSPENDED
DONE
FAILED
It's interesting, their own documentation, for v3.2, shows:
<COMPUTE href="http://www.opennebula.org/compute/32">
...
<STATE>running</STATE>
...
</COMPUTE>
I still need to compare the difference between OpenNebula versions, but I hope to have a patch shortly.
> 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
[dev] [jira] [Commented] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200326#comment-13200326 ]
Hutson Betts commented on LIBCLOUD-148:
---------------------------------------
Erik,
To my knowledge, there is no way to "unfold" the states using the OCCI interface. However, if there is a way, by all means, I would love to implement it.
It seems that states are only pulled from "VM_STATE=%w{INIT PENDING HOLD ACTIVE STOPPED SUSPENDED DONE FAILED}"
However, I still can't quite be sure. If I see a way to achieve the unfolding through the OCCI interface I'll be sure to implement it.
> 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
> Attachments: opennebula.diff
>
>
> 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
[dev] [jira] [Closed] (LIBCLOUD-148) OpenNebula's OCCI interface returns
the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hutson Betts closed LIBCLOUD-148.
---------------------------------
> 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
> Fix For: 0.8.0
>
> Attachments: opennebula.diff
>
>
> 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
[dev] [jira] [Assigned] (LIBCLOUD-148) OpenNebula's OCCI interface
returns the state ACTIVE, which is unknown to libcloud
Posted by "Hutson Betts (Assigned) (JIRA)" <ji...@apache.org>.
[ 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