You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/26 16:00:20 UTC

[jira] [Commented] (CLOUDSTACK-3214) transferring portable IP across zones with enableStatic NAT does not work

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693970#comment-13693970 ] 

ASF subversion and git services commented on CLOUDSTACK-3214:
-------------------------------------------------------------

Commit ff167134e45a3321dd5d9a3f45e3f9621b16d759 in branch refs/heads/master from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ff16713 ]

CLOUDSTACK-3214: transferring portable IP across zones with enableStatic
NAT does not work

making an exception for portabe IP, so that if the current datacenter with
portable IP is associated is different from destiantion data center

also on transfer on to new zone, transfer the portable ip association to
new data center, physical network id's

                
> transferring portable IP across zones with enableStatic NAT does not work
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3214
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3214
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>
>
> on portable IP association is transfered from a netwok in a zone to another network in zone, using enableStaticNat api, it fails with exception that current network and destination VM's network are different.
> This needs to be relaxed for portable IP

--
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