cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3268) [UI]No UI for Transferring Portable IP Across Networks
Date Thu, 01 Aug 2013 06:31:49 GMT


venkata swamybabu budumuru commented on CLOUDSTACK-3268:


Sorry..I have lost this bug as it is not shown in my list.

Currently, Murali has done a feature called "Poratable public IP". Here is the flow on how
user can transfer portable IP from one zone to the other.

Example configuration:

- 2 zones 
- non-ROOT domain user
- 2 isolated networks (Network1 in Zone1 and Network2 in Zone2)

(1) As ROOt admin, provision portable IP range at region level
(2) As an end-user, user will click on "Acquire IP address" at network level (Network1) with
option "Cross-Zones" set to "Yes"

(i) The above action will associate a portable IP address from the range defined in step :1
 to Network1

(3) Now user has the following option

 (i) When there are no services (staticNat/PF/Lb etc..,) enabled then user will be able to
directly create a service with a different network id i.e. Network2 in zone2. This implicitly
will result in a IP transferring across zones and networks. 

(3) (i) zone transfer is what Radhika mentioned here. 

As of the current UI, user cannot perform step (3) (i) but, from API, he can do it.

Here is the FS in case if you have any more question about the functionality

> [UI]No UI for Transferring Portable IP Across Networks
> ------------------------------------------------------
>                 Key: CLOUDSTACK-3268
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Radhika Nair
>            Priority: Critical
>             Fix For: 4.2.0
> There is no UI for transferring a Portable IP across network. No UI for transferring
to a specific VM in a specific network. 
> We have been firing APIs to accomplish that.

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:

View raw message