You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jessica Wang (JIRA)" <ji...@apache.org> on 2013/08/27 02:06:52 UTC
[jira] [Resolved] (CLOUDSTACK-4508) [UI] Nexus VSM details should
be mandatory when Switch type Nexus is selected with override traffic
labels provided for Public / Guest Traffic
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica Wang resolved CLOUDSTACK-4508.
--------------------------------------
Resolution: Fixed
> [UI] Nexus VSM details should be mandatory when Switch type Nexus is selected with override traffic labels provided for Public / Guest Traffic
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4508
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4508
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.2.0
> Reporter: Brian Federle
> Assignee: Jessica Wang
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: vsmfields.png
>
>
> Observation:
> 1. When Nexus global config is set to true , we enable Nexus details to be provided while adding cluster
> 2. With DATACenter to Zone mapping feature, we mandate only Cluster name to be added with Add Cluster.
> But while adding cluster if Swtich type Nexus is selected with override traffic labels provided for Public / Guest Traffic , we have to make Nexus details as mandatory .
> Nexus VSM details should be mandatory when Switch type Nexus is selected with override traffic labels provided for Public / Guest Traffic
> Reason; If we do not mandate them even though Switch type Nexus is selected with override traffic labels provided for Public / Guest Traffic , Admin may miss to provide as its not mandatory and It becomes a useless cluster without Nexus details.
--
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