Open Stack

I have been doing so in the number of patches I pushed to reduce error
traces due to the communication between server and dhcp agent.

I wanted to take care of the l3 agent too, but one thing I noticed is
that I couldn't find a log for it (I mean on the artifacts that are
published at job's completion). Actually, I couldn't find an l3 agent
started by devstack either.

Am I missing something?

On 27 November 2013 09:08, Salvatore Orlando <sorlando at nicira.com> wrote:
> Thanks Maru,
>
> This is something my team had on the backlog for a while.
> I will push some patches to contribute towards this effort in the next few
> days.
>
> Let me know if you're already thinking of targeting the completion of this
> job for a specific deadline.
>
> Salvatore
>
>
> On 27 November 2013 17:50, Maru Newby <marun at redhat.com> wrote:
>>
>> Just a heads up, the console output for neutron gate jobs is about to get
>> a lot noisier.  Any log output that contains 'ERROR' is going to be dumped
>> into the console output so that we can identify and eliminate unnecessary
>> error logging.  Once we've cleaned things up, the presence of unexpected
>> (non-whitelisted) error output can be used to fail jobs, as per the
>> following Tempest blueprint:
>>
>> https://blueprints.launchpad.net/tempest/+spec/fail-gate-on-log-errors
>>
>> I've filed a related Neutron blueprint for eliminating the unnecessary
>> error logging:
>>
>>
>> https://blueprints.launchpad.net/neutron/+spec/log-only-exceptional-conditions-as-error
>>
>> I'm looking for volunteers to help with this effort, please reply in this
>> thread if you're willing to assist.
>>
>> Thanks,
>>
>>
>> Maru
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>