My co-worker has it working on OOO, Pike release bm not containers. There was a plan to clean up the code and open it up since it’s all ansible-playbooks doing the work.
Remo > On Aug 24, 2018, at 07:37, Ben Nemec <openst...@nemebean.com> wrote: > > > > On 08/24/2018 04:17 AM, Juan Badia Payno wrote: >> Recently, I did a little test regarding fluentd logging on the gates >> master[1], queens[2], pike [3]. I don't like the status of it, I'm still >> working on them, but basically there are quite a lot of misconfigured logs >> and some services that they are not configured at all. >> I think we need to put some effort on the logging. The purpose of this email >> is to point out that we need to do a little effort on the task. >> First of all, I think we need to enable fluentd on all the scenarios, as it >> is on the tests [1][2][3] commented on the beginning of the email. Once >> everything is ok and some automatic test regarding logging is done they can >> be disabled. >> I'd love not to create a new bug for every misconfigured/unconfigured >> service, but if requested to grab more attention on it, I will open it. >> The plan I have in mind is something like: >> * Make an initial picture of what the fluentd/log status is (from pike >> upwards). >> * Fix all misconfigured services. (designate,...) > > For the record, Designate in TripleO is not considered production-ready at > this time. There are a few other issues that need to be resolved too. I'll > add this to my todo list though. > >> * Add the non-configured services. (manila,...) >> * Add an automated check to find a possible unconfigured/misconfigured >> problem. > > This would be good. I copy-pasted the log config from another service but > had no idea whether it was correct (apparently it wasn't :-). > >> Any comments, doubts or questions are welcome >> Cheers, >> Juan >> [1] https://review.openstack.org/594836 >> [2] https://review.openstack.org/594838 >> [3] https://review.openstack.org/594840 >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
