-
Notifications
You must be signed in to change notification settings - Fork 476
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
Comments
Original Redmine Comment You can set LIMIT_MB, to limit maximum capacity allowed for the datastore. Could that address this issue? |
Original Redmine Comment 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. |
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 |
(cherry picked from commit cd7a147)
Signed-off-by: Jan Orel <jorel@opennebula.systems>
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.
The text was updated successfully, but these errors were encountered: