Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor Ceph EC_POOL space usage when using erasure coded pool #3222

Closed
7 tasks
al3xhh opened this issue Apr 11, 2019 · 0 comments
Closed
7 tasks

Monitor Ceph EC_POOL space usage when using erasure coded pool #3222

al3xhh opened this issue Apr 11, 2019 · 0 comments

Comments

@al3xhh
Copy link
Contributor

al3xhh commented Apr 11, 2019

Description
Currently the ceph monitor scripts don't take in account the data from the EC_POOL_NAME, they just use the data from POOL_NAME.

Use case
It is really useful for cloud admins to know the real space, because the data is being stored on the EC_POOL instead of the POOL.

Interface Changes
The changes are related to Ceph scripts.

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@dann1 dann1 self-assigned this May 3, 2019
@dann1 dann1 added this to the Release 5.8.2 milestone May 3, 2019
dann1 added a commit that referenced this issue May 13, 2019
dann1 added a commit that referenced this issue May 13, 2019
dann1 added a commit that referenced this issue May 14, 2019
@dann1 dann1 changed the title Ceph monitor scripts takes in account the EC_POOL_NAME data Monitor Ceph EC_POOL space usage when using erasure coded pool May 14, 2019
rsmontero pushed a commit that referenced this issue May 20, 2019
rsmontero pushed a commit that referenced this issue Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants