Bug 1545559 - [RFE] Assign externalIP to the Elasticsearch Service
Summary: [RFE] Assign externalIP to the Elasticsearch Service
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: RFEs
Version: 1.0.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: 1547123
TreeView+ depends on / blocked
 
Reported: 2018-02-15 09:48 UTC by Shirly Radco
Modified: 2018-04-04 06:55 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-metrics-1.1.3.1
Doc Type: Enhancement
Doc Text:
In this release, the oVirt metrics configuration script automatically assigns an external IP to the Elasticsearch service.
Clone Of:
Environment:
Last Closed: 2018-03-29 11:18:39 UTC
oVirt Team: Metrics
Embargoed:
sradco: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87761 0 master MERGED Assign an IP Address to the Elasticsearch Service 2018-02-15 16:43:43 UTC

Description Shirly Radco 2018-02-15 09:48:02 UTC 
Description of problem:
Assign an IP Address to the Elasticsearch Service on the metrics store machine, so that we can configure the metrics and logs index curation parameter and make it configurable.

Currently user need to do this manually.
Comment 1 Rich Megginson 2018-02-15 14:59:42 UTC 
I don't understand - Elasticsearch already has an IP address?
Comment 2 Shirly Radco 2018-02-18 07:58:38 UTC 
This bug sets the "externalIP" for Elasticsearch service.
Comment 3 Lukas Svaty 2018-03-07 14:13:04 UTC 
verified in ovirt-engine-metrics-1.1.3.2-1.el7ev.noarch
Comment 4 Sandro Bonazzola 2018-03-29 11:18:39 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.