[
https://issues.apache.org/jira/browse/JCLOUDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662036#comment-13662036
]
Ioannis Canellos commented on JCLOUDS-71:
-----------------------------------------
@[~tangyong]:
1) You are right! The node-list command should be passed the shell table
factory too, as it happens with image-list, hardware-list, location-list etc.
2) Any Karaf command can be executed outside OSGi (without starting the OSGi
framework and without starting Karaf itself). The only requirement is the
command itself not to have a direct dependency from OSGi.
jclouds-karaf powers jclouds-cli which is more or less a jclouds branded
distribution of karaf with just jclouds inside it. It provides 2 flavours: i) a
karaf based interactive shell and ii) a command line flavor that can be used
without even starting karaf/osgi. To support the later we have refactored the
commands so that they can also function outside OSGi. This means that the
commands need to work without the aid of the blueprint for dependency
injection.
So in the case of the shell table factory, the command will instantiate the
non-OSGi based implementation, but if blueprint is available it will inject the
OSGi based one.
You can find more about jclouds-cli here: https://github.com/jclouds/jclouds-cli
> jclouds:image-list can not list current image of openstack env
> --------------------------------------------------------------
>
> Key: JCLOUDS-71
> URL: https://issues.apache.org/jira/browse/JCLOUDS-71
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-karaf
> Affects Versions: 1.7.0
> Environment: openstack 2012.1.3-dev(Essex)
> karaf 2.3.1
> jclouds-karaf master
> Reporter: TangYong
> Priority: Critical
> Attachments: jclouds-commands.xml.patch
>
>
> Seeing the following:
> karaf@root> jclouds:compute-service-create --api openstack-nova --endpoint
> http://10.167.157.86:5000/v2.0 --identity admin:admin --credential ******
> --add-option jclouds.keystone.credential-type=passwordCredentials
> Waiting for compute service with name: openstack-nova.
> karaf@root> jclouds:node-list
> [id] [location]
> [hardware] [group] [status]
> RegionOne/a1da4e27-9974-4941-bf25-c53a7d2a0f5d
> 1ce52682441c34ad7afde77fb30634211b5ce02884ba54ca0f35ff0a RegionOne/1 null
> RUNNING
> RegionOne/285c730c-bd64-4818-91aa-b87db88e1e3e
> 1ce52682441c34ad7afde77fb30634211b5ce02884ba54ca0f35ff0a RegionOne/2 null
> RUNNING
> RegionOne/d18ff351-7c1e-452c-bcbb-1e4e4ac34ae7
> 1ce52682441c34ad7afde77fb30634211b5ce02884ba54ca0f35ff0a RegionOne/2 null
> RUNNING
> karaf@root> jclouds:image-list
> null
> null
> karaf@root>
> In my openstack env, using nova image-list can obtain the following:
> root@ubuntu:~# nova image-list
> +--------------------------------------+-----------------------------+--------+--------+
> | ID | Name | Status
> | Server |
> +--------------------------------------+-----------------------------+--------+--------+
> | 7cf21d93-d04a-4fb4-a09b-f546a9461726 | Ubuntu 12.04 cloudimg amd64 | ACTIVE
> | |
> +--------------------------------------+-----------------------------+--------+--------+
> So, I think that this is a bug. Wish team can confirm it.
--
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
