You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Rick Bross (JIRA)" <ji...@apache.org> on 2011/08/12 16:27:27 UTC
[dev] [jira] [Created] (LIBCLOUD-108) Change EC2 Provider to support AWS
separately so that AWS endpoints are not hard coded
Change EC2 Provider to support AWS separately so that AWS endpoints are not hard coded
--------------------------------------------------------------------------------------
Key: LIBCLOUD-108
URL: https://issues.apache.org/jira/browse/LIBCLOUD-108
Project: Libcloud
Issue Type: Improvement
Components: Compute
Affects Versions: 0.6.0
Reporter: Rick Bross
Priority: Minor
Currently, calling AWS endpoints requires that a provider be selected by region. Based on the provider chosen (for example Provider.EC2_US_WEST, EC2_US_EAST, etc), the internal code creates the endpoint. Since Amazon constructs the endpoints in a well know fashion:
https://ec2.{region}.amazonaws.com
It makes more sense to create a Provider for AWS that simply takes the region as a parameter and constructs the endpoint on the fly. That way, if libcloud is deployed as the base for other software, the entire suite does not have to be updated when Amazon adds a new region.
Currently, I use Provider.EUCALYPTUS for AWS endpoints by constructing the the URL myself based on the region before calling libcloud to accomplish this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-108) Change EC2 Provider to support
AWS separately so that AWS endpoints are not hard coded
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508142#comment-13508142 ]
Tomaz Muraus commented on LIBCLOUD-108:
---------------------------------------
Just FYI - some of the changes related to improving EC2 experience are now in trunk.
> Change EC2 Provider to support AWS separately so that AWS endpoints are not hard coded
> --------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-108
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-108
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.6.1
> Reporter: Rick Bross
> Priority: Minor
> Labels: AWS, Amazon, EC2, Eucalyptus, beginners, endpoint, url
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, calling AWS endpoints requires that a provider be selected by region. Based on the provider chosen (for example Provider.EC2_US_WEST, EC2_US_EAST, etc), the internal code creates the endpoint. Since Amazon constructs the endpoints in a well know fashion:
> https://ec2.{region}.amazonaws.com
> It makes more sense to create a Provider for AWS that simply takes the region as a parameter and constructs the endpoint on the fly. That way, if libcloud is deployed as the base for other software, the entire suite does not have to be updated when Amazon adds a new region.
> Currently, I use Provider.EUCALYPTUS for AWS endpoints by constructing the the URL myself based on the region before calling libcloud to accomplish this.
--
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
[dev] [jira] [Commented] (LIBCLOUD-108) Change EC2 Provider to support
AWS separately so that AWS endpoints are not hard coded
Posted by "Jayyy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494582#comment-13494582 ]
Jayyy commented on LIBCLOUD-108:
--------------------------------
This would really be a nice change. We shall streamline AWS to one single libcloud provider.
> Change EC2 Provider to support AWS separately so that AWS endpoints are not hard coded
> --------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-108
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-108
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.6.1
> Reporter: Rick Bross
> Priority: Minor
> Labels: AWS, Amazon, EC2, Eucalyptus, beginners, endpoint, url
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, calling AWS endpoints requires that a provider be selected by region. Based on the provider chosen (for example Provider.EC2_US_WEST, EC2_US_EAST, etc), the internal code creates the endpoint. Since Amazon constructs the endpoints in a well know fashion:
> https://ec2.{region}.amazonaws.com
> It makes more sense to create a Provider for AWS that simply takes the region as a parameter and constructs the endpoint on the fly. That way, if libcloud is deployed as the base for other software, the entire suite does not have to be updated when Amazon adds a new region.
> Currently, I use Provider.EUCALYPTUS for AWS endpoints by constructing the the URL myself based on the region before calling libcloud to accomplish this.
--
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
[dev] [jira] [Updated] (LIBCLOUD-108) Change EC2 Provider to support AWS
separately so that AWS endpoints are not hard coded
Posted by "Tomaz Muraus (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus updated LIBCLOUD-108:
----------------------------------
Labels: AWS Amazon EC2 Eucalyptus beginners endpoint url (was: AWS Amazon EC2 Eucalyptus endpoint url)
> Change EC2 Provider to support AWS separately so that AWS endpoints are not hard coded
> --------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-108
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-108
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.6.1
> Reporter: Rick Bross
> Priority: Minor
> Labels: AWS, Amazon, EC2, Eucalyptus, beginners, endpoint, url
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, calling AWS endpoints requires that a provider be selected by region. Based on the provider chosen (for example Provider.EC2_US_WEST, EC2_US_EAST, etc), the internal code creates the endpoint. Since Amazon constructs the endpoints in a well know fashion:
> https://ec2.{region}.amazonaws.com
> It makes more sense to create a Provider for AWS that simply takes the region as a parameter and constructs the endpoint on the fly. That way, if libcloud is deployed as the base for other software, the entire suite does not have to be updated when Amazon adds a new region.
> Currently, I use Provider.EUCALYPTUS for AWS endpoints by constructing the the URL myself based on the region before calling libcloud to accomplish this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira