cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4266) [UI] VSM specific input fields to be made optional on UI if no traffic chooses Nexus 1000v
Date Thu, 29 Aug 2013 21:19:52 GMT


ASF subversion and git services commented on CLOUDSTACK-4266:

Commit 0f4917154ea07db434ce110287c8adc2d7e4a50d in branch refs/heads/master from [~jessicawang]
[;h=0f49171 ]

CLOUDSTACK-4266: UI > Infrastructure > clusters > add cluster dialog > if configuration
'vmware.use.dvswitch' is set to false (i.e. override public/guest traffic checkboxes are hidden),
hide VSM fields (regardless of another configuration '').

> [UI] VSM specific input fields to be made optional on UI if no traffic chooses Nexus
> ------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4266
>                 URL:
>             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 ''
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:

View raw message