TangYong created JCLOUDS-88:
-------------------------------
Summary: jclouds:node-list is not in line with nova list while
using openstack
Key: JCLOUDS-88
URL: https://issues.apache.org/jira/browse/JCLOUDS-88
Project: jclouds
Issue Type: Improvement
Components: jclouds-karaf
Affects Versions: 1.7.0
Reporter: TangYong
Fix For: 1.7.0
[jclouds-karaf result]
karaf@root> jclouds:node-list
[id] [location]
[hardware] [group] [status]
RegionOne/2699a427-6f20-4725-b54f-5fd170ad44a3
1ce52682441c34ad7afde77fb30634211b5ce02884ba54ca0f35ff0a RegionOne/2 null
RUNNING
[nova list result]
root@ubuntu:~# nova list
+--------------------------------------+-------------+--------+-------------------------------------+
| ID | Name | Status |
Networks |
+--------------------------------------+-------------+--------+-------------------------------------+
| 2699a427-6f20-4725-b54f-5fd170ad44a3 | cargoTestVM | ACTIVE |
private=192.168.22.39, 10.167.157.5 |
+--------------------------------------+-------------+--------+-------------------------------------+
Compared with the above result, the following metadata was not displayed,
1) Name
2) Networks
[Influence Analyze]
For an user using jclouds-karaf, 1) and 2) metadata are important, especially
2), by 2) he/she maybe ready to ssh the node etc. We do not wish the user will
enter into IaaS again after using cli commands.
For 1), maybe is not important, however, as a friend display, at least this
should be more meaningful than node id.
Originally, I plan to set Priority is Minor, however, from [Influence Analyse],
maybe being Major.
Needing a vote.
--
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
