You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Pranav Saxena (JIRA)" <ji...@apache.org> on 2013/04/03 23:31:16 UTC

[jira] [Resolved] (CLOUDSTACK-1669) UI for non-contiguous VLAN ranges

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pranav Saxena resolved CLOUDSTACK-1669.
---------------------------------------

    Resolution: Fixed
      Assignee: Pranav Saxena  (was: Jessica Wang)

The UI is now checked into master and due to the re-design for this feature , one would be able to update the Vlan ranges through the guest networks section under the infrastructure -> zone-> zone name -> physical network -> guest network (configure) -> add a Vlan range here . 

Thanks !
                
> UI for non-contiguous VLAN ranges
> ---------------------------------
>
>                 Key: CLOUDSTACK-1669
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1669
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Brian Federle
>            Assignee: Pranav Saxena
>             Fix For: 4.2.0
>
>         Attachments: firebug-vlan-ranges-info.jpg, vlan-range-edit-detailView.jpg, vlan-ranges-zonewizard.jpg
>
>   Original Estimate: 168h
>          Time Spent: 72h
>  Remaining Estimate: 96h
>
> 1) Zone wizard: Add UI component to display multiple VLAN ranges, per guest network -- Brian
> 2) Guest traffic detail view: Merge 'start' and 'end' VLAN fields to 1 field that is in range format. On save, process string to determine modified VLAN ranges. -- Brian
> Format is '[start]-[end], ...'
> i.e., '1200-1203, 1400-1500', ...'
> 3) Modify server calls to support non-contiguous VLAN ranges for zone creation and modification of existing guest traffic ranges -- Jessica

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