[
https://issues.apache.org/jira/browse/LIBCLOUD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750099#comment-13750099
]
Michael Bennett commented on LIBCLOUD-383:
------------------------------------------
Has work for this change already begun?
After taking a quick look, what I think would need to change is have an
ElasticHostsDriver that takes a region argument in its __init__ method, get the
appropriate host for that region and then pass that as an argument to a call to
super which should take care of everything else (BaseDriver already takes a
host kwarg that it will also pass to the connection Class). Or am I missing
something?
If no one has started working on this, I'd be willing to implement it.
Cheers
> 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
