Neat! I have a kind of sick curiosity to see a real error in it now. Any reason we shouldn't go ahead and create accounts for everyone on the team for this? Could you please make it part of the lava project group and establish a blueprint with some work items for the remaining work left to be done? It would be great to highlight this as a success story for hacking on something we just talked about this week. Great work!
On Wed, Feb 8, 2012 at 7:14 PM, Zygmunt Krynicki < zygmunt.krynicki@linaro.org> wrote:
Hi.
I've created a new extension for LAVA called lava-raven. This extension wraps Raven (which is a client for Sentry) in a easy to install package. The code is up on launchpad [1] and pypi [2], pypi also has a short documentation on how to set up sentry+raven in a LAVA instance.
Along with raven I did a few small changes to linaro-django-xmlrpc (merge request [3]) to support raven better (those changes don't depend on raven though) and lava-server (merge request [4]). Here it's mostly a small helper base class for creating headless extensions. The MP is quite long because I took the liberty of doing documentation cleanups at the same time. Please have a look at those so that they can land quickly.
Lastly with the help of Canonical IS team I've setup a new DNS for our Sentry instance at [5]. Sadly sentry is not easy to put in a URL prefix so I had to resort to another top level domain. Sentry is built on top of django so it has a local user database. There is no OpenID support and currently only I have an account there. Ping me to get another account if you need it. As we use sentry we'll see if we can keep this view public (I strongly doubt it as it has all the request data, including (probably) security tokens. Sentry currently runs as a new system user (sentry) on validation control server. It's currently using sqlite backend so we may want to create a PostgresSQL user/database for it instead if it gets slow.
In any way, as soon as those bits land we'll have live monitoring of various parts of LAVA. All of the things that are integrated with LAVA Server will automatically benefit (that includes the scheduler _except_ for the scheduler daemon). As we progress towards using celery all of our stack will be transparently using Raven. For those bits that won't quickly become celery tasks I think it would be worth to patch some optional raven support (I'm looking at you lava-dispatcher).
Best regards ZK
[1] https://launchpad.net/lava-raven [2] http://pypi.python.org/pypi/lava-raven/0.1 [3] https://code.launchpad.net/~zkrynicki/linaro-django-xmlrpc/better-sentry-sup...https://code.launchpad.net/%7Ezkrynicki/linaro-django-xmlrpc/better-sentry-support/+merge/92179 [4] https://code.launchpad.net/~linaro-validation/lava-server/production/+merge/...https://code.launchpad.net/%7Elinaro-validation/lava-server/production/+merge/92190 [5] http://sentry.validation.linaro.org/
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation