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

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

Commit 6d9a3d82f9b617d40d0ee1472bef87cb630595d6 in cloudstack's branch 
refs/heads/master from [~wilder.rodrigues]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d9a3d8 ]

CLOUDSTACK-9075 - Uses the same vlan since it should have been already released

    - After the first test is done, the clean up will delete the whole VPC, 
also releasing the VLAN that was in use.


> As a Developer I want the Private GW feature fixed on single VPCs
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9075
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9075
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.6.0
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>             Fix For: 4.7.0
>
>
> The Private GW feature is broken since the VR refactor. it should be fixed 
> for single VPCs and more tests should be included in order to cover it as a 
> whole.
> 1. Test Private GW ACL replace
>     - existing tests
> 2. Test Private GW connectivity through 2 VPCs
>    - New test
> The new test should perform the following steps:
> 1. Create 2 VPCs
> 2. Create 2 Tiers - 1 per VPC
> 3. Deploy 2 VMs - 1 per Tier
> 4. Acquire 2 pub IPs - 1 per VPC
> 5. Create 2 PF rules - 1 per pub IP
> 6. Create 2 ACLs + rules - 1 per VPC
> 7. Assign new ACLs to Tiers
> 8. Create 2 Private GWs - 1 per VPC
> 9. Replace the Pvt GWs ACLs
> 10. Create 2 Static routes - 1 per Pvt GW
> 11. SSH into VM1 (VPC1) and from there ping VM2 (VPC2)
> Please note that the Private GWs have to be in the same VLAN.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to