incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-574) Service Configuration: tabify settings for each service
Date Wed, 04 Jul 2012 21:50:56 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated AMBARI-574:
-------------------------------------------

    Fix Version/s: 0.9.0
    
> Service Configuration: tabify settings for each service
> -------------------------------------------------------
>
>                 Key: AMBARI-574
>                 URL: https://issues.apache.org/jira/browse/AMBARI-574
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-574.patch
>
>
> Currently, Step 6 of the Cluster Install Wizard is one massive form that shows all parameters
for all services (and takes up multiple screens worth of vertical space).
> This is disorienting and not very user-friendly.
> There is a number of improvements that can be made for this page:
>  * Create a tab for each service and organize configuration parameters within the tabbed
content
>  * Be explicit about the fields that are required but do not have any default content
>  * Show Nagios and Hive configurations first, as they contain fields that are required
but don't have default content
>  * Always require the user to enter passwords (currently, Nagios Admin password is pre-filled
but they are showing as *** so this is confusing)
>  * Do not let the user submit the form if there are any client-side validation errors
that have not been addressed (toggle the submit button enabled/disabled state based on the
number of client-side validation errors).
>  * Upon submission and server-side validation error, show the number of validation errors
for each service inside the corresponding tab
>  * As the user make corrections, clear the field error messages (for example, when we
show the field error that the field is required, but we don't clear the error message after
the user fills the field).
>  * Dynamically change the number of errors per service in the tab as client-side validation
errors are generated/cleared.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message