Bug 1520126
Summary: | [RFE] Set curator configmap on metrics store machine | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine-metrics | Reporter: | Shirly Radco <sradco> |
Component: | RFEs | Assignee: | Shirly Radco <sradco> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0.7 | CC: | bugs, eheftman, rmeggins, sradco, ylavi |
Target Milestone: | ovirt-4.2.2 | Keywords: | FutureFeature |
Target Release: | 1.1.3 | Flags: | rule-engine:
ovirt-4.2+
rule-engine: exception+ lsvaty: testing_plan_complete- ylavi: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-metrics-1.1.3-1.el7ev | Doc Type: | Enhancement |
Doc Text: |
Previously, to configure the curator parameter for the metrics index, the user had to manually update it.
In this release, the curator parameter is configured when running the metrics configuration script.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-29 11:15:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Metrics | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1475135, 1528913, 1543477 |
Description
Shirly Radco
2017-12-03 09:39:37 UTC
Using Severity... ? Please make this non-mandatory, for Verification I am using non-ViaQ setup, thus would be good if playbook won't fail on this. Also what is the result, benefit, outcome of the RFE? Can you provide some verification steps on what to test from oVirt side? Also note that there is an openshift-ansible parameter "curator_config_contents". You can use this to provide the contents of the curator config file to use. The value of this parameter is a string, not a filename e.g. ansible-playbook -e curator_config_contents="$( cat mylocalcurator.yaml )" ... That is, the value is a string which has as its value the contents of a YAML formatted file. Shirly/Yaniv Is this a feature that we want to document and/or will it require changing the current installation? When this feature is done, we will need to remove from the documentation the manual step of configuring the curator. verified in ovirt-engine-metrics-1.1.3.2-1.el7ev.noarch This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |