<commit_before># ceph_check 

ceph_check is a reporting tool, which checks a newly installed or an existing Ceph cluster, 
and report various unsupported or unoptimal configurations.  

An installation has to be according to the suggested guidelines, and checking/confirming 
this is a great way to prevent problems in the future.  

Points worth considering:

1. This program should be run from the Ceph Administrator node, as the 'ceph' user.
2. If a custom username has been used to setup the Ceph cluster, use that account to execute the program.
3. The user running this script should have *read* permissions to the admin keyring.
4. SSH passwordless login should be setup for the user to the Ceph cluster nodes.

The above four points are the suggested requirements for an RHCS/Ceph installation, and hence can be expected 
to be present in a RHCS/Ceph cluster. 

1. ceph_check will detect custom keyring locations, and use it appropriately. If you are using a custom
admin keyring, you will need to mention that in /etc/ceph/ceph.conf.

2. The user running this script should have at least *read* permissions to the admin keyring.

3. 
ceph_check will detect custom keyring locations, and use it accordingly. The user running the script
should have read permissions though, which is of course the case if you want to execute any 'ceph' commands.


<commit_msg>Added a few points to 'README.md'<commit_after># ceph_check 

ceph_check is a reporting tool, which checks a newly installed or an existing Ceph cluster, 
and report various unsupported or unoptimal configurations.  

An installation has to be according to the suggested guidelines, and checking/confirming 
this is a great way to prevent problems in the future.  

## Points worth considering:

1. This program should be run from the Ceph Administrator node, as the 'ceph' user.
2. If a custom username has been used to setup the Ceph cluster, use that account to execute the program.
3. The user running this script should have *read* permissions to the admin keyring.
4. SSH passwordless login should be setup for the user to the Ceph cluster nodes.

The above four points are the suggested requirements for an RHCS/Ceph installation, and hence can be expected 
to be present in a RHCS/Ceph cluster. 

## Features:

1. ceph_check will detect custom keyring locations, and use it appropriately. As a norm, any custom keyrings
should be mentioned in /etc/ceph/ceph.conf for the Ceph cluster to work properly.

2. Checks the package versions on all the nodes in the Ceph cluster, and will report any descrepancies.

3. Reports the generic status of the Cluster.

4. Check if there is a custom cluster name. 'ceph' is the one that is supported right now.

5. Checks the number of placement groups in the pools, and suggests a proper value.

6. Reports if a single journal disk is being used for more than 6 OSD disks, since 6 is the suggested value.

7. <More to be added> 



{'fraction_non_alphanumeric': 0.03874915023793338, 'fraction_numerical': 0.006798096532970768, 'mean_word_length': 4.04802744425386, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '997226', 'n_tokens_mistral': 778, 'n_tokens_neox': 749, 'n_words': 475}