Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 22 Aug 2013 06:18:53 +0000 (UTC)
From: "Kirk Kosinski (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12664979.1377152270617.15462.1377152333994@arcas>
In-Reply-To: <JIRA.12664979.1377152270617@arcas>
References: <JIRA.12664979.1377152270617@arcas>
Subject: [jira] [Created] (CLOUDSTACK-4438) Improve documentation for
 traffic labels configuration KVM, vSphere, and XenServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kirk Kosinski created CLOUDSTACK-4438:
-----------------------------------------

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


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