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

OpenNebula should not assume total available data in Ceph cluster is available for ONE #1232

Closed
OpenNebulaProject opened this issue Nov 20, 2017 · 3 comments

Comments

@OpenNebulaProject
Copy link


Author Name: Stefan Kooman (Stefan Kooman)
Original Redmine Issue: 5134, https://dev.opennebula.org/issues/5134
Original Date: 2017-04-27


OpenNebula Ceph monitor assumes all data in the Ceph cluster is available for ONE, i.e. max_avail. Monitor should check if there is a quota assigned to the pool and if so, use this value instead of max_avail. See #127 for a possible fix.

@OpenNebulaProject
Copy link
Author


Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2017-05-16T13:03:35Z


You can set LIMIT_MB, to limit maximum capacity allowed for the datastore. Could that address this issue?

@OpenNebulaProject
Copy link
Author


Original Redmine Comment
Author Name: Stefan Kooman (Stefan Kooman)
Original Date: 2017-06-21T08:04:10Z


It's more about monitoring than it's about not able to limit usage. A cloudadmin that is checking the datastores wants to see the amount of available storage, not some theoretical maximum. When datastore attributes "TOTAL_MB", "FREE_MB", "USED_MB" are used for monitoring a cluster, you also want to get the right values.

@stale
Copy link

stale bot commented Mar 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. The OpenNebula Dev Team

@xorel xorel added this to the Release 5.8.1 milestone Mar 15, 2019
rsmontero pushed a commit that referenced this issue Mar 15, 2019
xorel added a commit to xorel/one that referenced this issue Mar 18, 2019
xorel added a commit to xorel/one that referenced this issue Mar 18, 2019
Signed-off-by: Jan Orel <jorel@opennebula.systems>
rsmontero pushed a commit that referenced this issue Mar 18, 2019
Signed-off-by: Jan Orel <jorel@opennebula.systems>
rsmontero pushed a commit that referenced this issue Mar 18, 2019
Signed-off-by: Jan Orel <jorel@opennebula.systems>
(cherry picked from commit 25852e4)
rsmontero pushed a commit that referenced this issue May 19, 2021
Co-authored-by: Jorge Lobo <jlobo@opennebula.systems>
rsmontero pushed a commit that referenced this issue May 20, 2021
Co-authored-by: Jorge Lobo <jlobo@opennebula.systems>
(cherry picked from commit c944294)
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