Bug 1431767 - Deliver the necessary Opstools clients so Enterprise Common Logging can work for OpenStack
Summary: Deliver the necessary Opstools clients so Enterprise Common Logging can work ...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: fluentd
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: Upstream M2
: 12.0 (Pike)
Assignee: Juan Badia Payno
QA Contact: Leonid Natapov
Depends On:
Blocks: 1442136 1469903
TreeView+ depends on / blocked
Reported: 2017-03-13 17:25 UTC by Maria Bracho
Modified: 2018-02-05 19:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:15:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Maria Bracho 2017-03-13 17:25:26 UTC
Description of problem: Deliver Enterprise Common Logging for OpenStack. 
Includes aligning with Red Hat's ECL strategy and product to include OpenStack as part of this offering.
This includes any modifications to the fluentd clients required to be delivered by director and connected with the central logging collector.

Comment 7 Fabio Massimo Di Nitto 2017-06-21 13:15:25 UTC
The current implementation in TripleO is capable of configuring fluentd to connect to ECL (non-SSL).
The resulting fluentd configuration is able to send log to the ECL server side
no SSL/TSL testing has been performed yet due to lack of access to the ECL server side test environment.

Any other request should be filed as separate bugs (for example: #1446276, #1454793, etc)

Comment 14 errata-xmlrpc 2017-12-13 21:15:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.