cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayapal Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7104) VPC public ips not configured after network implement from implementing
Date Thu, 28 Aug 2014 08:16:58 GMT

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

Jayapal Reddy commented on CLOUDSTACK-7104:
-------------------------------------------

Problem:
------------
In VPC, network implemented after GC VPC public ips are configured on the VR.

Root Cause Analysis:
--------------------------
When network is implemented after GC, ipassoc is not performed on this network.
Due to this public ip address is not configured on VR.

Proposed solution:
----------------------
In IpAddressManager we have method to check ipassoc is needed or not in checkIfIpAssocRequired.
Returning true when network state is implementing.

QA Verification steps:
---------------------------
1. create vpc and create tier in vpc.
2. Set network.gc to low in the global settings.
3. Acquire ip and configure PF rule on the ip.
4. Stop all the vms in the tier.
5. network will remove all the rules and ips on the router after the network gc interval.
6.start the vm. Once the vm is started go to VR check all public ips on VR are configured
correctly.
Command to check in VR:
ip addr show


> VPC public ips not configured after network implement from implementing
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7104
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7104
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.5.0
>
>
> Reproducing steps:
> 1. create vpc and create tier in vpc.
> 2. Set network.gc to low in the global settings.
> 3. Acquire ip and configure PF rule on the ip.
> 4. Stop all the vms in the tier.
> 5. network will remove all the rules and ips on the router after the network gc interval.
> 6. Now start the vm, observe that the PF public ip is not configured on the interface.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message