[
https://issues.apache.org/jira/browse/LIBCLOUD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750105#comment-13750105
]
Tomaz Muraus commented on LIBCLOUD-383:
---------------------------------------
Yeah, some work on that has already started (e.g. EC2 and Rackspace driver),
but those things aren't finished yet and there are some issues which need to be
fixed (current "setting a class attribute" approach is not correct and needs to
be changed to passing an argument to the connection class and setting an
instance attribute in the connection constructor)
The approach you have suggested should work, you just need to make sure the
"host" argument is correctly set on the Connection as an instance and not as a
class attribute. Setting a class attribute (which is currently done in some of
the drivers mentioned above) won't work correctly if you have multiple drivers
with different regions instantiated at the same time.
As an alternative, you should also be able to use "_ex_connection_class_kwargs
method on the driver -
https://github.com/apache/libcloud/blob/trunk/libcloud/common/base.py#L863.
> Elastichosts driver missing us-3 api endpoint classes
> -----------------------------------------------------
>
> Key: LIBCLOUD-383
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-383
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Michael Bennett
> Priority: Trivial
> Fix For: 0.12.3
>
>
> The elastichosts driver is missing a NodeDriver and Connection class for the
> us-3 api endpoint (meta-data is present however). It is also missing and
> entry in libcloud.compute.types.Provider and
> libcloud.compute.providers.DRIVERS
--
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
