[
https://issues.apache.org/jira/browse/LIBCLOUD-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868876#comment-13868876
]
ASF subversion and git services commented on LIBCLOUD-470:
----------------------------------------------------------
Commit f44c3648119f8a1e9e3f190bca1bc8e52a2012a3 in branch refs/heads/trunk from
[~cderamus]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=f44c364 ]
Issue LIBCLOUD-470: Add VPC Elastic IP support. This not only adds full EIP
support for EC2-Classic/VPC, but also adds a new ElasticIP abstraction
that will make future promotion into the base API much easier. New tests
were added to validate VPC association/disassociation/release calls work
as expected.
Closes #220.
Signed-off-by: Tomaz Muraus <[email protected]>
> Update EC2 address calls with VPC support
> -----------------------------------------
>
> Key: LIBCLOUD-470
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-470
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Chris DeRamus
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> AWS elastic IP addresses for VPC work a tad differently than EC2.
> Add a new class EC2ElasticIpAddress which will store all attributes listed in
> the documentation:
> http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-DescribeAddresses.html.
>
> Update ex_describe_addresses to return a list of EC2ElasticIpAddress objects
> Update ex_release_address to include the allocation id as a keyword argument.
> This is required to release a VPC address.
> Update ex_allocate_address with a domain keyword argument to support
> allocating addresses within VPCs.
> Update ex_disassociate_address with a association_id keyword argument to
> support disassociating VPC addresses from an instance inside of a VPC network.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
