Storage Node Admin UI Changes - [Bug 1016175]

Catherine Robson crobson at redhat.com
Thu Oct 24 17:33:06 UTC 2013


Mike and Stefan,

I agree I should take a look at this and work with you for the user 
interface part of this bug.  I'm in all day meetings today and 
tomorrow.  It looks like I really need to take a detailed look at the 
existing page and the recommendations below, and will probably have some 
questions as well.  I don't think I can do this during my meetings, so 
I'm hoping I can take a look at this over the weekend and talk with you 
on Monday about the UI side of it.  Is that an acceptable plan or are 
you trying to finish this bug for a release and need feedback prior to that?

Thanks,
Catherine

mike thompson wrote:
> This one is complicated enough that it needs UXD feedback. Catherine 
> can hook you up with UXD resources.
>
> -- Mike
>
>
> On Oct 23, 2013, at 1:01 PM, Stefan Negrea <snegrea at redhat.com 
> <mailto:snegrea at redhat.com>> wrote:
>
>> Hello Everybody,
>>
>> We've been working on a redesign of the Cluster Settings tab (Storage 
>> Admin UI) in the context of BZ 1016175. The screen turns out to be 
>> fairly complex from a user perspective because of the way settings 
>> get applied. In the short term only the password will be propagated 
>> to the Storage Cluster, while other settings will only be update in 
>> the RHQ system settings.
>>
>> The server-side work for BZ 1016175 is complete, but we need feedback 
>> for the UI changes.
>>
>> Here are the steps we plan on taking today to convey how settings are 
>> applied and be prepared for the future:
>> 1) Group the settings into three settings sections: Cluster, New 
>> Deployments, Credentials
>> 2) Add extra verbose description to each field and the title of the 
>> section
>> 3) Make fields that are not updateable today as read-only
>> 4) The screen has only one Save button
>>
>> New Cluster settings tab (groups + fields + description):
>>
>> 1) Cluster Settings
>> Description: On save these setting will not be propagated to existing 
>> Storage Nodes. Please review the documentation on how update the CQL 
>> and Gossip ports for all Storage Nodes.
>> - CQL Port - Port on which the Storage Nodes listen for CQL client 
>> connections. <b>Warning:</b> if this setting does not match the 
>> configured Storage Cluster CQL port, the server will NOT be able to 
>> communicate with the Storage Cluster and will go into maintenance mode.
>> -Gossip Port - The port used for internode communication in the 
>> Storage Cluster. <b>Warning:</b> if this setting does not match the 
>> configured Storage Cluster Gossip port, any new Storage Nodes will 
>> NOT be able to communicate and be part of the existing Storage Cluster.
>>
>> 2) Deployment Settings
>> Description: Only applies to new installations.
>> - Automatic Deployment - If this is set, the newly installed storage 
>> nodes will be automatically deployed to the storage cluster.
>>
>> 3) Credentials Settings
>> Description: Password changes are propagated to the Storage Cluster 
>> and all HA servers.
>> - Username (read-only) - Username for Storage Node CQL 
>> authentication. This property is read-only because changes are not 
>> allowed.
>> - Password - Password for Storage Node CQL authentication. Change 
>> will get propagated to the all deployed Storage Nodes and applied to 
>> newly installed nodes. All HA servers will have storage cluster 
>> sessions refreshed automatically to use the new password.
>> - Verify Password - Validation (needs to match Password)
>>
>> For the future:
>> 1) Updates to the CQL port, Gossip Port, and username will be 
>> propagated to the entire storage cluster automatically from the RHQ 
>> server.
>> 1) When the feature to propagate port changes is implemented, the 
>> warnings and verbose descriptions will be replaced with something 
>> similar to the Password field.
>> 2) When the username changes will be allowed, the text for the will 
>> be changed to something similar to the password field.
>>
>>
>> Any feedback is greatly appreciated.
>>
>> Bug - https://bugzilla.redhat.com/show_bug.cgi?id=1016175
>> Fix Branch - 
>> https://git.fedorahosted.org/cgit/rhq/rhq.git/log/?h=bug/1016175
>>
>>
>> Thank you,
>> Stefan Negrea
>>
>> Software Engineer
>>
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org 
>> <mailto:rhq-devel at lists.fedorahosted.org>
>> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/rhq-devel/attachments/20131024/4d99a34b/attachment.html>


More information about the rhq-devel mailing list