Need an API to retrieve the total,used,free space of osds of a cluster
Shouldn't this be rather implemented in 2.0? switching to that version.
*** Bug 1295810 has been marked as a duplicate of this bug. ***
Yes this should be implemented in 2.0 so that USM can consume
We don't have this in the data from ceph which looks like this: "osd_metadata": [ { "backend_filestore_partition_path": "unknown", "backend_filestore_dev_node": "unknown", "kernel_description": "#114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015", "distro_version": "14.04", "back_addr": "104.236.159.39:6804/1002134", "osd": 0, "distro_codename": "trusty", "hostname": "vagrant-ubuntu-trusty-64", "mem_swap_kb": "0", "id": 0, "ceph_version": "ceph version 9.2.0 (bb2ecea240f3a1d525bcb35670cb07bd1f0ca299)", "distro": "Ubuntu", "hb_back_addr": "104.236.159.39:6805/1002134", "osd_objectstore": "filestore", "osd_data": "/var/lib/ceph/osd/ceph-0", "arch": "x86_64", "hb_front_addr": "104.236.159.39:6806/1002134", "distro_description": "Ubuntu 14.04.3 LTS", "filestore_backend": "generic", "front_addr": "104.236.159.39:6800/2134", "kernel_version": "3.13.0-71-generic", "osd_journal": "/var/lib/ceph/osd/ceph-0/journal", "filestore_f_type": "0xef53", "mem_total_kb": "2049944", "os": "Linux", "cpu": "Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz" } ], Either rhs-controller can schedule a utilization check with salt or Ceph needs to grown the capability first.
Which one would be a better choice in your opinion?
Can calamari use 'ceph osd df' command to get utilization from ceph and expose it through an API?. We expect per OSD based utilization data here
That is a possibility. It should take 2 days
line 7: Require API to retrieve the osd utilization http://192.81.214.250:8000/api/v2/cluster/6c7718eb-1774-4b8e-b802-854c43241067/cli POST { "command": ["ceph", "osd", "df", "--format=json-pretty"] }
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
verified in ceph version 10.2.1-3.el7cp (f6e1bde2840e1da621601bad87e15fd3f654c01e)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1755