Bug 1729408
Summary: | RFE: storage: Ceph RBD image-meta support to set features like QoS I/O throttling | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Jules <jules> |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | berrange, crobinso, libvirt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-12-17 12:30:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jules
2019-07-12 08:29:48 UTC
Just seen that there is an similar logic already that applies to storage pool namespace: https://github.com/libvirt/libvirt/commit/ab6ca812763b539e5380d8d6c4fa9da939125814 So this maybe can get extended, to allow defining conf parameters per disk xml. The only difference would be that it needs to loop through each defined disk source name (in my example): libvirt-pool/new-libvirt-image to assign each image volume the limit option with their corresponding value. Another note: From reading the Ceph RBD docs, "image-meta set" can be applied at runtime and take action immediately. So an option to change these values on-the-fly via libvirt api would be a killer feature. Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution. |