Bug 1282519 - Expose replication factor to the user
Expose replication factor to the user
Status: ON_QA
Product: RHQ Project
Classification: Other
Component: Storage Node, Core UI (Show other bugs)
4.13
Unspecified Unspecified
high Severity unspecified (vote)
: ---
: RHQ 4.14
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks: 1234991
  Show dependency treegraph
 
Reported: 2015-11-16 11:32 EST by John Sanda
Modified: 2015-11-18 14:22 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Sanda 2015-11-16 11:32:09 EST
Description of problem:
The replication_factor (RF) should be exposed in the storage node admin UI as a read-only property in the cluster settings section. We need to show the RF for both the rhq and system_auth keyspaces. When there are storage node deployment problems, users frequently have to verify that the RF is set to the correct, expected value. The only way to verify the value right now is very cumbersome. You first have to decode the password defined in the rhq.storage.password property in rhq-server.properties. Decoding it can be done from the RHQ CLI. You then have to enable thrift on the storage node. This can be done using the nodetool command line tool. Then you have to log into cqlsh to execute the DESCRIBE KEYSPACE command to get the RF.

It might be good to make it accessible in the remote API as well so users can also get at the information from the CLI or other command line clients.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 John Sanda 2015-11-18 14:22:39 EST
The replication settings or more precisely the replication_factor of both the rhq and the system_auth keyspaces are now read-only properties in the cluster settings view of the storage node admin UI. I have also introduced StorageSettingsManagerBeanRemote which is exposed in the remote API / CLI and has the method,

    StorageClusterSettings getClusterSettings(Subject subject);

so that replication settings as well as other cluster settings exposed in the UI can also be queried and obtained from the CLI. Changes have been pushed to master.

commit hashes:
7e246dbad2
e95cfff30
8c7a6174cae
7388c02dec
ea893e01a19a

Note You need to log in before you can comment on or make changes to this bug.