[
https://issues.apache.org/jira/browse/CLOUDSTACK-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695347#comment-13695347
]
Radhika Nair commented on CLOUDSTACK-652:
-----------------------------------------
No UI for transferring Portable IP to another network...
> High Availability: EIP enhancements
> -----------------------------------
>
> Key: CLOUDSTACK-652
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-652
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.1.0
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Labels: features
> Fix For: 4.2.0
>
>
> At present CloudStack has AWS EIP like functionality available where in user
> can a acquire a public IP, and associate static NAT (1:1) with an instance
> he owns. At any time user can dis-associate the static NAT between the
> acquired public IP and instance, and create a new static-NAT between the
> public IP and any other VM instance he owns. But current EIP semantics
> available in CloudStack, will only let an user transfer EIP from one instance
> to another instance with in the same zone.
> In AWS, EIP [1] can be transferred across the availability zones. EIP can be
> used for building failover architectures on AWS. For e.g. refer to [2][3] for
> failover architectures with EIP.
> [1] http://aws.amazon.com/articles/1346
> [2]
> http://support.rightscale.com/09-Clouds/AWS/02-Amazon_EC2/Designing_Failover_Architectures_on_EC2/00-Best_Practices_for_using_Elastic_IPs_(EIP)_and_Availability_Zones
> [3] http://harish11g.blogspot.in/2012/06/aws-high-availability-outage.html
> As part of this enhancement I would like to achieve following goals.
> 1. CloudStack supports EIP service only in basic zone. Enhance CloudStack, to
> provide EIP service in isolated/shared networks of advanced zone as well.
> This should bring the parity of EIP service availability in both basic and
> advanced zones.
> 2. Introduce a notion of ' Elastic IP' pool per region. User should be able
> to acquire an elastic IP from the pool, and establish static NAT from the EIP
> to any of the instances user owns in the zones under the region.
> 3. Elastic IP service provider in the zone, will be responsible for
> advertising the route for EIP to upstream router. For this RHI (Route Health
> Injection) functionality commonly available in ADC like NetScaler, Big IP,
> ADX etc will be leveraged. At the network manager framework level no specific
> ADC/Appliance will be assumed as Elastic IP service provider and an abstract
> Network Element command that achieves route health injection will need to be
> introduced.
> Finally, i would like implement EIP across zone, using NetScaler load
> balancer appliances. CloudStack already supports NetScaler as EIP service
> provider in the zone. I would like to enhance the NetScaler integration so as
> to provide EIP across the zones functionality.
> Release Planning:
> Dev list discussion: http://markmail.org/message/lx6tyikvmvd6wix4
> Functional Spec: unknown
> Feature branch: unknown
--
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
