Bug 887196
| Summary: | [RFE] [gluster] Introduce a column to indicate that volume is already optimized | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Prasanth <pprakash> | |
| Component: | Frontend.WebAdmin | Assignee: | Sahina Bose <sabose> | |
| Status: | CLOSED WONTFIX | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | --- | CC: | amukherj, bsettle, bugs, godas, grajaiya, lsvaty, mmahoney, Rhev-m-bugs, sabose, scohen, sdharane | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.4?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
|
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 975632 979286 (view as bug list) | Environment: | ||
| Last Closed: | 2019-06-17 05:31:20 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 975632 | |||
|
Description
Prasanth
2012-12-14 09:54:08 UTC
*** Bug 1017515 has been marked as a duplicate of this bug. *** Currently, there's no foolproof way to know if a volume has already been optimized. If the user has set the volume option from UI, then we can identify it. But if options are set manually from CLI, engine does not know of it and cannot mark it. This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag. This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?. Atin, is there any way to know if a group profile has been set on a volume? The way group profile is applied in glusterd is following: CLI reads the group profile and form the list of key=value pairs and pass them to glusterd as part of volume set request. So technically glusterd process this request as a volume set operation than a group profile. So in short, there's not any such identifier currently by which we can distinguish it. (In reply to Atin Mukherjee from comment #7) > The way group profile is applied in glusterd is following: > > CLI reads the group profile and form the list of key=value pairs and pass > them to glusterd as part of volume set request. So technically glusterd > process this request as a volume set operation than a group profile. So in > short, there's not any such identifier currently by which we can distinguish > it. @Sahina, So its clear that there is no way to find out whether the volume is optimized for virt usecase, except for the crude way of list of volume options set on the volume. Not all volumes created in RHHI-V environment, are used for storing VM image. So, we can't generalize and optimize the volume for virt use case. This is the known limitation. Having said that, we can CLOSE this bug as WONTFIX. Thanks |