You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "shweta agarwal (JIRA)" <ji...@apache.org> on 2013/05/28 14:07:19 UTC

[jira] [Commented] (CLOUDSTACK-766) nTier Apps 2.0 : Assign a VLAN ID to a network

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

shweta agarwal commented on CLOUDSTACK-766:
-------------------------------------------

More from functional specs
 "Create network" dialog changes:

    Display network offering with specifyVlan=true as an option, only on Root Admin UI. To get this offerings with listNetworkOfferings API, add specifyVlan=true to the list of parameters.
    Add and display Vlan field when network offering with SpecifyVlan=true is selected.

Changes have to be done on the on following tabs:

    Networks tab,
    VPC->Create new Tier tab

2) "CreateNetworkOffering" dialog changes. 

When specifyVlan=true, don't automatically send specifyIpRanges=true. Do it the following way:
* Shared networks: Always send specifIpRanges=true* Isolated networks. When specifyVlan=true check box is selected, send specifyIpRanges=true only when no SourceNatService is selected. Don't send anything in all other cases.
                
> nTier Apps 2.0 : Assign a VLAN ID to a network
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-766
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-766
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>            Reporter: Kishan Kavala
>            Assignee: Brian Federle
>             Fix For: 4.2.0
>
>
> This item is a sub task (2.18) of https://issues.apache.org/jira/browse/CLOUDSTACK-621 
> Allow admins to specify a VLAN ID while defining a Tier of a VPC.

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