[
https://issues.apache.org/jira/browse/LIBCLOUD-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900637#comment-13900637
]
Chris DeRamus commented on LIBCLOUD-518:
----------------------------------------
Yeah we're using libcloud to manage about ten different AWS accounts and we do
the business logic before sending off any requests associated with the elastic
IP life cycle. So far we've had no issues with both EC2 classic and VPC IPs by
handling the conditions on our end before leveraging libcloud.
> EC2NodeDriver.ex_associate_address_with_node's domain parameter is redundante
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-518
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-518
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Reporter: Tom Prince
> Labels: ec2, vpc
>
> Whether an address and/or instance is in a VPC can be determined from
> attributes, so the value of the parameter must have can be determined from
> other arguments. (There can also be sanity checking, to ensure that a classic
> EIP isn't associated to a VPC instance, or vice-versa).
> ex_disassociate_address should also get this treatement.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
