Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 756B710BAF for ; Fri, 2 Aug 2013 21:45:49 +0000 (UTC) Received: (qmail 72992 invoked by uid 500); 2 Aug 2013 21:45:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 72973 invoked by uid 500); 2 Aug 2013 21:45:49 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 72965 invoked by uid 500); 2 Aug 2013 21:45:49 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 72962 invoked by uid 99); 2 Aug 2013 21:45:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 21:45:49 +0000 Date: Fri, 2 Aug 2013 21:45:49 +0000 (UTC) From: "Venkata Siva Vijayendra Bhamidipati (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-3905) [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728166#comment-13728166 ] Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3905: ----------------------------------------------------------------- The usage of nexus 1000v and vmware dvs are each controlled by their global configuration flags vmware.use.nexus.vswitch and vmware.use.dvswitch respectively. If one is set, the other cannot be used. If both are set, it pretty much boils down to the code that checks for one flag before the other. Currently, the mgmt server doesn't have a way to specify mutual exclusivity between global flags. Either we should put this in, or move these flags from a global config level to the zone level, where explicit code checks can be put in to disallow both flags to be set. > [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true > ----------------------------------------------------------------------------- > > Key: CLOUDSTACK-3905 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3905 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Network Devices > Affects Versions: 4.2.0 > Reporter: Sailaja Mada > Priority: Critical > Fix For: 4.2.0 > > > Steps: > 1. Set below Global config parameters to true : > vmware.use.dvswitch Enable/Disable Nexus/Vmware dvSwitch in VMware environment true > > vmware.use.nexus.vswitch Enable/Disable Cisco Nexus 1000v vSwitch in VMware environment true > 2. Tried to add Standard vSwitch/DVSwitch Cluster : > Observations: > 1. Nexus 1000v Switch configuration details are mandatory to add cluster > 2. It will not let to add new cluster with DVS/Standard vSwitch. -- 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