You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "manasaveloori (JIRA)" <ji...@apache.org> on 2013/06/26 09:08:19 UTC

[jira] [Commented] (CLOUDSTACK-3126) NTier: vpc.max.networks includes all the User Tier Networks and Private Networks

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

manasaveloori commented on CLOUDSTACK-3126:
-------------------------------------------

Observed the issue with following steps:
1. set vpc.max.networks=3.
2. Create a VPC.
3. Create 2 tier networks and 1 private gateway.
4. Now try to create 3rd tier network--it fails



1. Now create a VPC.
2. Create 3 tier networks.
3.Create any number of private gateways-----it succeeds

                
> NTier: vpc.max.networks includes all the User Tier Networks and Private Networks
> --------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3126
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3126
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> A New User to CloudStack might assume that the vpc.max.networks includes only the guest networks in a VPC. But the global parameter includes all the VPC private networks including private gateway networks and site2site vpn gateway networks too. Currently, the User might gets confused to understand why is he/she is able to create User networks lesser than the vpc.max.networks limit. Either we need to report the message with more information or release note this observation.

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