Re: [openstack-dev] [Tripleo] fluentd logging status
On Fri, Aug 31, 2018 at 3:08 PM, Juan Antonio Osorio Robles < jaosor...@redhat.com> wrote: > Logging is a topic that I think should get more love on the TripleO side. > > On 08/24/2018 12:17 PM, 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. > > Wes, do you have an opinion about this? I think it would be a good idea to > avoid these types of regressions. > > > 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. > > One bug to fix all this is fine, but we do need a public place to track > all the work that needs to be done. Lets reference that place on the bug. > Could be Trello or an etherpad, or whatever you want, it's up to you. > I'm creating the google spreadsheet [4] to track the status of the fluentd logging from pike to master. > > 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,...) > * Add the non-configured services. (manila,...) > * Add an automated check to find a possible unconfigured/misconfigured > problem. > > 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 > > [4] https://docs.google.com/spreadsheets/d/1Keh_hBYGb92rXV3VN44oPR6eGnX9LnTpcadWfMO8dZs/edit?usp=sharing > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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 > > -- Juan Badia Payno Software Engineer Red Hat EMEA ENG Openstack Infrastructure __ 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
Re: [openstack-dev] [Tripleo] fluentd logging status
Logging is a topic that I think should get more love on the TripleO side. On 08/24/2018 12:17 PM, 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. Wes, do you have an opinion about this? I think it would be a good idea to avoid these types of regressions. > > 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. One bug to fix all this is fine, but we do need a public place to track all the work that needs to be done. Lets reference that place on the bug. Could be Trello or an etherpad, or whatever you want, it's up to you. > > 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,...) > * Add the non-configured services. (manila,...) > * Add an automated check to find a possible > unconfigured/misconfigured problem. > > 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
Re: [openstack-dev] [Tripleo] fluentd logging status
Logging is a topic that I think should get more love on the TripleO side. On 08/24/2018 12:17 PM, 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. Wes, do you have an opinion about this? I think it would be a good idea to avoid these types of regressions. > > 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. One bug to fix all this is fine, but we do need a public place to track all the work that needs to be done. Lets reference that place on the bug. Could be Trello or an etherpad, or whatever you want, it's up to you. > > 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,...) > * Add the non-configured services. (manila,...) > * Add an automated check to find a possible > unconfigured/misconfigured problem. > > 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
Re: [openstack-dev] [Tripleo] fluentd logging status
On Fri, Aug 24, 2018 at 2: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,...) > * Add the non-configured services. (manila,...) Awesome, I noticed this with manila just yesterday, and added it to my list of To-Do/cleanup. I'm glad you're taking note/working on it, please add me to review (gouthamr) / let me know if you'd like me to do something. > * Add an automated check to find a possible unconfigured/misconfigured > problem. > > 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
Re: [openstack-dev] [Tripleo] fluentd logging status
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 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
Re: [openstack-dev] [Tripleo] fluentd logging status
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-dev] [Tripleo] fluentd logging status
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,...) * Add the non-configured services. (manila,...) * Add an automated check to find a possible unconfigured/misconfigured problem. 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
