[
https://issues.apache.org/jira/browse/LIBCLOUD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750059#comment-13750059
]
Tomaz Muraus commented on LIBCLOUD-383:
---------------------------------------
Sorry for the delay.
I haven't added classes for other regions yet, but we are slowly moving towards
"region argument" instead of "class per region" model.
This means there will only be one class and you will be able to pass "region"
argument to the class constructor.
This "region argument" change will most likely be available in the next release
(I don't have an exact ETA yet), so I'm not sure how much value does it add to
commit your patch to trunk at the moment.
Ideally you would be able to port ElasticHosts driver to the "region argument"
model, but that's a slightly bigger and more involved task.
As far as the tests go - we currently don't have specific tests for
ElasticHosts, but we do have tests for ElasticStack
(libcloud/test/compute/test_elasticstack.py) based providers on which the
ElasticHosts driver is based one.
Thanks
> 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
