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

Brian Federle edited comment on CLOUDSTACK-1669 at 3/13/13 11:10 PM:
---------------------------------------------------------------------

Assigning to Jessica for API call modification in zone wizard code to support 
multiple VLAN ranges.

Jessica, please see firebug-vlan-ranges-info.jpg for updated location in data 
object to get non-contiguous VLAN ranges.
                
      was (Author: bfederle):
    Assigning to Jessica for API call modification in zone wizard code to 
support multiple VLAN ranges.

Jessica see firebug-vlan-ranges-info.jpg for updated location in data object to 
get non-contiguous VLAN ranges.
                  
> 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: Jessica Wang
>             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

Reply via email to