[
https://issues.apache.org/jira/browse/CLOUDSTACK-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747440#comment-13747440
]
Sateesh Chodapuneedi commented on CLOUDSTACK-4438:
--------------------------------------------------
CLOUDSTACK-3398 talks about UI improvement to reflect the enhancement done for
traffic label. As part of implementing vDS support in cloudstack, vmware
traffic label is added one more field. It is vswitch type. Please find more
about traffic label format can be found in FS with very detailed description of
the label with examples.
Following is from FS at
https://cwiki.apache.org/CLOUDSTACK/integration-of-cloudstack-with-vmware-dvs.html
See point (2) in section - Architecture and Design description
• Traffic label format is [["Name of
vSwitch/dvSwitch/EthernetPortProfile"][,["VLAN ID"][,["vSwitch Type"]]]]
1. Description
2. All the 3 fields are optional
3. Default values for the 3 fields are as below
1. 1st field - Represents the name of virtual/distributed virtual switch
at vCenter. The default value assumed would depend upon the type of virtual
switch. Defaults values are as follows.
1. vSwitch0 if type of virtual switch is "VMware vNetwork Standard virtual
switch"
2. dvSwitch0 if type of virtual switch is "VMware vNetwork distributed
virtual switch"
3. epp0 if type of virtual switch is "Cisco Nexus 1000v distributed
virtual switch"
2. 2nd field - VLAN ID to be used for this traffic where ever applicable.
This field would be used for only public traffic as of now. In case of guest
traffic this field would be ignored and could be left empty for guest traffic.
1. By default empty string would be assumed which translates to untagged
VLAN for that specific traffic type.
3. 3rd field - Type of virtual switch specified as string. Possible valid
values are vmwaredvs, vmwaresvs, nexusdvs. Each translates as follows.
1. "vmwaresvs" represents "VMware vNetwork Standard virtual switch"
2. "vmwaredvs" represents "VMware vNetwork distributed virtual switch"
3. "nexusdvs" represents "Cisco Nexus 1000v distributed virtual switch"
4. If nothing is specified (left empty) that means zone level default
virtual switch (based on value of global parameters) would be assumed.
Following are the global configuration parameters.
1. vmware.use.dvswitch - This should be true to enable any kind (VMware
DVS / Cisco Nexus 1000v DVS) of distributed virtual switch in cloudstack
deployment. If this is false that means default virtual switch in that
cloudstack deployment is "standard virtual switch" only.
2. vmware.use.nexus.vswitch - This parameter would be ignored unless
"vmware.use.dvswitch" is true. Set this to "true" to enable Cisco Nexus 1000v
distributed virtual switch in a cloudstack deployment.
4. As per above mentioned format, furnishing few possible values for
networkLabel,
1. "" (empty string)
2. dvSwitch0
3. dvSwitch0,200
4. dvSwitch0,300,vmwaredvs
5. myEthernetPortProfile,,nexusdvs
6. dvSwitch0,,vmwaredvs
> Improve documentation for traffic labels configuration KVM, vSphere, and
> XenServer
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4438
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4438
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.2.0
> Reporter: Kirk Kosinski
> Labels: installguide, kvm, networking, vsphere, xenserver
>
> The installation guide currently has a "Physical Networking Setup for
> XenServer" section (see CLOUDSTACK-661). There should be corresponding
> sections for KVM and vSphere, and the XenServer section can use some slight
> improvements.
> For KVM, the traffic labels defined in CloudStack should correspond to the
> bridge name on the hypervisor, and for vSphere the traffic labels should
> correspond to the vSwitch name.
> For vSphere, a VLAN ID can be included for management traffic (see
> CLOUDSTACK-3870). There are some references to this currently but no clear
> explanation. The syntax is (currently) "<vSwitch_Name>,<VLAN_ID>", for
> example "vSwitch0,100" for vSwitch0 and VLAN ID 100. This might change if
> CLOUDSTACK-3398 is implemented.
> Considering that vSphere supports a VLAN ID for management traffic, in the
> XenServer section it would be wise to explicitly state that management server
> traffic must not be put on a VLAN. This is explained in the XenServer
> documentation but is commonly misunderstood.
--
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
