cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-3469) [VMware] Support to make username/password optional while adding VMware cluster
Date Thu, 11 Jul 2013 15:35:48 GMT


Sateesh Chodapuneedi resolved CLOUDSTACK-3469.

    Resolution: Fixed
> [VMware] Support to make username/password optional while adding VMware cluster
> -------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3469
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.0
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.2.0
> Currently AddCluster dialog (after choosing VMware) treats following 2 input parameters
are mandatory.
> UI would be changing these 2 parameters to optional.
> These 2 needs to be made optional, because in some cases these 2 parameters are necessary
and in some cases not. If a zone is lagacy zone these parameters are mandatory. In case of
non-legacy zone these parameters are optional as at the point of adding a VMware cluster,
we should have had this information already as user has provided this information already
as part of adding VMware DC to zone.
> Ofcourse, even in case of non-legacy zone, user may provide this information as a specific
cluster needs different credentials from the credentials specified while adding VMware DC
to zone.
> While adding VMware cluster, these conditions need to be take care of.
> 1) If zone is legacy then throw Exception if username/password are not provided.
> 2) If zone is non-legacy and username/password are not provided, retrieve credentails
provided by user while addiing VMware DC to zone & continue the rest of process to add
VMware cluster to cloudstack zone.
> 3) If zone is non-legacy and username/password are provided, then no changes required.
Just leave current logic as is.

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