On Mon, Dec 16, 2013 at 7:31 PM, Ursula Junque <email address hidden> wrote:
> That's my understanding, confirmed by fginther:
> <Ursinha> fginther, let me see if I got the message queue idea: "Lander"
> updates whatever it is in the message queue, ticket system polls the
> message queue for updates, therefore there's no need of a write API to
> update ticket status for phase 0?
> <fginther> Ursinha, yes, you're correct
>
We have a "rabbit worker" example that you can steal from to get started:
On Mon, Dec 16, 2013 at 7:31 PM, Ursula Junque <email address hidden> wrote:
> That's my understanding, confirmed by fginther:
> <Ursinha> fginther, let me see if I got the message queue idea: "Lander"
> updates whatever it is in the message queue, ticket system polls the
> message queue for updates, therefore there's no need of a write API to
> update ticket status for phase 0?
> <fginther> Ursinha, yes, you're correct
>
We have a "rabbit worker" example that you can steal from to get started:
http:// bazaar. launchpad. net/~canonical- ci-engineering/ ubuntu- ci-services- itself/ trunk/view/ head:/branch- source- builder/ run_worker
Its juju deployable with:
http:// bazaar. launchpad. net/~canonical- ci-engineering/ ubuntu- ci-services- itself/ trunk/view/ head:/juju- deployer/ branch- source- builder. yaml#L17
I'm guessing your "on_message" calls would basically be updates to the
django model or something