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

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

Commit 12ca1d9102483c71f5008de846b861de317b0f36 in branch refs/heads/4.2 from 
[~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=12ca1d9 ]

CLOUDSTACK-4089: (WIP) Add new fields to zone wizard for configuring traffic 
type for VMware

                
> Provide a drop down to specify VLAN,Switch type, Traffic label name while 
> configuring Zone(VMWARE)
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4089
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Brian Federle
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: dropPN.png
>
>
> Observation:
> Setup: VMWARE 
> 1. While configuring Zone,  During Physical network creation ,  currently 
> there is a text field to specify VLAN Id for the traffic ,  Traffic label 
> name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) 
> 2. It is text field and there is a possibility of missing some of the 
> parameters. 
> 3.  While adding cluster we have an option to specify the traffic label name 
> and drop down to select the Switch type.  
> This is the request to provide  a drop down to specify VLAN,Switch type, 
> Traffic label name while configuring Zone(VMWARE).  This will avoid a lot of 
> confusion between Zone vs Cluster level configuration.
> It also simplifies the configuration process. 

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