[
https://issues.apache.org/jira/browse/LIBCLOUD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768655#comment-13768655
]
Tomaz Muraus commented on LIBCLOUD-400:
---------------------------------------
This one has been figured out on the IRC. I'm opening a separate ticket for
documentation (LIBCLOUD-401).
{quote}
[16:11] < arthurlutz> | hi, is libcloud supposed to work on openstack essex ?
[17:58] <@ Kami_> | arthurlutz: hey, yeah it should
[17:59] <@ Kami_> | arthurlutz: (i saw your ticket, just hand't had the
time to reply yet)
[17:59] <@ Kami_> | arthurlutz: but the exception basically means driver
can't find the
endpoint in the keystone
[17:59] <@ Kami_> | arthurlutz: in the service catalog*
[17:59] < arthurlutz> | Kami_: on the keystone side it seems to send back
something with some
info
[17:59] < arthurlutz> | some publicURL etc
[18:00] <@ Kami_> | arthurlutz: yeah, it's not finding the endpoint,
probably looking for
entry, gimme a sec
[18:03] <@ Kami_> | arthurlutz:
https://github.com/apache/libcloud/blob/trunk/libcloud/common/openstack.py#L351
service_type and name and probably not set correctly
[18:03] <@ Kami_> | arthurlutz: you can set those by passing
ex_force_service_type and
ex_force_service_name argument to the driver constructor
[18:03] < arthurlutz> | set them to what ?
[18:04] < arthurlutz> | Kami_: ^
[18:05] <@ Kami_> | arthurlutz: depend on the entries in the serice catalog
[18:05] <@ Kami_> | arthurlutz: if you can gist the service catalog
response somewhere i
can have a look
[18:11] <@ Kami_> | arthurlutz: you can view the response using
libcloud_debug
http://ci.apache.org/projects/libcloud/docs/troubleshooting.html#debugging
[18:11] < arthurlutz> | forcing the compute type and name works
[18:11] < arthurlutz> | indeed
[18:11] < arthurlutz> | Kami_: thanks
{quote}
> libcloud.common.types.LibcloudError: <LibcloudError in None 'Could not find
> specified endpoint'>
> ------------------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-400
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-400
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Affects Versions: 0.13.1
> Reporter: Arthur Lutz
> Priority: Blocker
>
> Using libcloud against an in-house installation of OpenStack Essex gives me
> this :
> Traceback (most recent call last):
> File "trylibcloud.py", line 21, in <module>
> nodes = driver.list_nodes()
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/compute/drivers/openstack.py",
> line 207, in list_nodes
> self.connection.request('/servers/detail').object)
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/compute/drivers/openstack.py",
> line 145, in request
> method=method, headers=headers)
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/common/openstack.py",
> line 584, in request
> return super(OpenStackBaseConnection, self).request(**kwargs)
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/common/base.py",
> line 571, in request
> action = self.morph_action_hook(action)
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/common/openstack.py",
> line 580, in morph_action_hook
> self._populate_hosts_and_request_paths()
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/common/openstack.py",
> line 607, in _populate_hosts_and_request_paths
> url = self._ex_force_base_url or self.get_endpoint()
> File
> "/home/arthur/local/virtualenvs/cloudenvy/local/lib/python2.7/site-packages/libcloud/common/openstack.py",
> line 549, in get_endpoint
> raise LibcloudError('Could not find specified endpoint')
> libcloud.common.types.LibcloudError: <LibcloudError in None 'Could not find
> specified endpoint'>
> Is libcloud supposed to work for the essex version of Openstack ? With
> keystone ?
> If not, maybe the documentation should be updated to include this information
> ?
--
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
