[
https://issues.apache.org/jira/browse/CLOUDSTACK-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738776#comment-13738776
]
ASF subversion and git services commented on CLOUDSTACK-4266:
-------------------------------------------------------------
Commit 6fcb2dfde7931f3e22909873e3afed594ffb2985 in branch refs/heads/4.2 from
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6fcb2df ]
CLOUDSTACK-4266: UI > Infrastructure > clusters > create cluster dialog > make
Nexus 1000v fields optional.
> [UI] VSM specific input fields to be made optional on UI if no traffic
> chooses Nexus 1000v
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4266
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4266
> 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: Sateesh Chodapuneedi
> Assignee: Jessica Wang
> Priority: Critical
> Fix For: 4.2.0
>
>
> Currently Nexus VSM specific input fields like Nexus 1000v ip/user/password
> etc. are mandatory in UI (shows red asterisk) while adding clsuter if global
> config parameter 'vmware.use.nexus.vswitch' is true.
> We need to amend this because we now have option to override the cloud level
> setting (which is from global configuration parameter set to 'true') or zone
> level setting (traffic lebel at zone level) at cluster level while adding
> cluster. Hence it makes no sense to ask user to provide VSM details, while
> adding cluster, when user chooses not to use Nexus 1000v for any of the
> traffics.
> Hence need to make these fields as optional (remove the red asterisks)
--
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
