You can browse the source code for the development focus branch or get a copy of the branch using the command:
bzr branch lp:lava-celery

There are download files available for LAVA Celery (deprecated).

LAVA Celery (deprecated) has 3 active branches owned by 1 person and 1 team. There were 0 commits in the last month.

Bazaar branches

Name Status Last Modified Last Commit
Series: trunk, linaro-11.11
1 Development 2012-09-25 00:26:09 UTC 2012-09-25
32. post release bump

Author: Michael Hudson-Doyle
Revision Date: 2012-09-25 00:26:09 UTC

post release bump

lp:~doanac/lava-celery/celery-back 1 Development 2013-01-10 03:02:06 UTC 2013-01-10
97. need some fixes for dispatcher deploy...

Author: Andy Doan
Revision Date: 2013-01-10 03:01:31 UTC

need some fixes for dispatcher deployed. also including michael's new filter API

lp:~doanac/lava-celery/logging-madness (Has a merge proposal) 1 Development 2012-06-27 03:43:08 UTC 2012-06-27
19. fix oddness with logging in tasks Th...

Author: Andy Doan
Revision Date: 2012-06-27 03:40:12 UTC

fix oddness with logging in tasks

The run_remote command wasn't handling all exceptions which under
certain circumstances made celeryd handle the exception. This is
somewhat okay, but the error gets logged in the worker. When you
think about the scenario where we run the dispatcher on a remote
system, the caller (scheduler in this case) will need to see these
types of errors.

The other issue I hit was that when exceptions come from the
CloudifierDispatcher code, the stdout/stderr references get all
munged up in celery's twisted maze of redirecting its stdout to
its loggers. The only simple way out I found was with the hack:

 sys.stderr.logger.root.handlers[0].stream = logging.sys.__stderr__

This also adds a bit of debbuging to indicate when a command is
received, what arguments were passed, and when it finished

13 of 3 results
You can't create new branches for LAVA Celery (deprecated).