[07:14] <lifeless> bigjools: so is there a blog post up about the pitfalls of celery (and why you're moving away from it?)
[07:14] <bigjools> heh
[07:14] <bigjools> hi stalker!
[07:14] <lifeless> you know it
[07:15] <bigjools> there's nothing wrong with it per se, it just doesn't do what we want
[07:17] <lifeless> ok
[07:17] <lifeless> what do you want? That it doth not do?
[07:17] <bigjools> bi-directional comms and notifications that it's down
[07:18] <bigjools> ie more than just a job processing system
[07:18] <lifeless> interesting
[07:18] <bigjools> because we're not directing generic jobs anywhere, we direct them to specific queues
[07:18] <bigjools> we've NIHed bidirectional comms
[07:19] <lifeless> RPC calls, or actual cooperating messages to long lived routines?
[07:19] <bigjools> RPC
[07:19] <bigjools> some will be long lived
[07:20] <bigjools> but we need feedback on important stuff, like "did my power on command work?" :)
[14:02] <blake_r> allenap: can I get a quick review for this, 1.6 upgrade fix, https://code.launchpad.net/~blake-rouse/maas/fix-1341001/+merge/226673
[14:06] <allenap> blake_r: Sure.
[21:37] <lazyPower> Is there a configuration guide that i've missed to proxy ppa requests since maas installs an apt-proxy on all of its hosts? i'm getting frustrated with having to remote in an dcomment out the apt-proxy on all of my maas nodes when testing juju charms that make use of a ppa
[23:09] <bigjools> lazyPower: edit the squid config that maas installs to be more permissive