[
https://issues.apache.org/jira/browse/JCLOUDS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662012#comment-13662012
]
Ioannis Canellos commented on JCLOUDS-71:
-----------------------------------------
Hi Tang,
thanks for submitting the patch.
I disagree with the removal of the shell table factory from the image list
command (in the blueprint descriptor).
What should be done instead is to make sure that the both the injected factory
and the PropertyShellTableFactory both use the org.apache.jclouds.shell
configuration.
In case its not that clear:
These commands are executed both in the OSGi context (from within Karaf) and
outside it (when are being invoked by jclouds-cli).
When inside OSGi we are passing a shell table factory implementation that is
backed by the configuration admin (ManagedShellTableFactory). When running
outside OSGi we are just using the property file based
(PropertyShellTableFactory) implementation.
So both need to be aligned.
Could you please modify the patch and resend?
Thanks again.
> 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
