Bug 1431767

Summary: Deliver the necessary Opstools clients so Enterprise Common Logging can work for OpenStack
Product: Red Hat OpenStack Reporter: Maria Bracho <mbracho>
Component: fluentdAssignee: Juan Badia Payno <jbadiapa>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: achernet, djuran, fdinitto, jcantril, mmagr, mrunge, pportant, rmeggins, tkatarki, tvignaud
Target Milestone: Upstream M2Keywords: FutureFeature, OtherQA, TestOnly, Triaged
Target Release: 12.0 (Pike)   
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: 2017-12-13 21:15:40 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:
Bug Depends On:    
Bug Blocks: 1442136, 1469903    

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.

https://access.redhat.com/errata/RHEA-2017:3462