627573 - Instrument input to send messages to pulse

Status: RESOLVED WONTFIX

(Input :: General, enhancement, P2)

Description

[LegNeato]

Instrument input to send messages to pulse.mozilla.org. All the cool kids/systems are doing it these days.

We'll probably want to use carrot (https://github.com/ask/carrot) or kombu (https://github.com/ask/kombu). I believe both have pretty trivial integration with Django.

I've set up a durable topic exchange named "org.mozilla.exchange.feedback". Input should publish it's messages with routing keys in the following (or similar) format:

  * input.happy.[product].[version].[locale].[platform]
  * input.sad.[product].[version].[locale].[platform]
  * input.suggestion.[product].[version].[locale].[platform]

Comment 1

[Aakash Desai [:aakashd]]

I'll add this as something to think about with the API. Though, there is the already available ATOM feeds that could pretty much do everything you'd want (unless I'm not looking at this the right way).

Comment 2

[LegNeato]

I want push, not polling. The data is only 1/2 the battle...getting it live/realtime without polling is the other 1/2.

Comment 3

[Fred Wenzel [:wenzel]]

We use carrot anyway, I think (together with django-celery). I am not going to add this to the request-response cycle whenever people submit feedback, but we can ping celery on submission and then do all sorts of madness (including extracting terms and other beautiful things), including pinging Pulse.

Looks like one of our 3.x releases (3.2?) is going to have to focus on deferred processing. CCing rsnyder and davedash about this, too.

Comment 4

[LegNeato]

Taking this as I have it working locally. I'm listening to signals and sending the pulse/amqp message in a different process (not using celery).

I plan to clean it up tomorrow and stick a patch up for review.

Comment 5

[Fred Wenzel [:wenzel]]

Hot. Somewhat related: I hooked up Input (and some other projects) to post code updates to Pulse.

Comment 6

[LegNeato]

Wow, this dropped off my radar with all the FF release stuff. Hoping to work more on it today.

Comment 7

[Aakash Desai [:aakashd]]

Yeah, I was wondering about that :). We're code freezing for 3.3 today and releasing on the 15th. So, I can slot you in for 3.4 if that's enough time to get this landed.

Comment 8

[LegNeato]

Good, slot me into 3.4 then. That'll make it not get dropped.

Comment 9

[LegNeato]

(In reply to comment #8)
> Good, slot me into 3.4 then. That'll make it not get dropped.

Apparently this was false :-/

Comment 10

[Fred Wenzel [:wenzel]]

No worries. We're in the process of bringing the Input development process back in line with what Firefox does, and this ended up a lower priority. We can probably accommodate this bug whenever you find time and feel like writing a patch for it though.

Comment 11

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

Moving to FUTURE, when this is ready we'll just merge it with whatever version of Input is going out.

Comment 12

[Will Kahn-Greene [:willkg] ET needinfo? me]

I don't really understand what this bug is about. We've rewritten Input since the bug was originally reported and it's likely requirements and the world has completely changed since then, so I'm going to mark it as WONTFIX.

If it's still relevant to the new Input, please file a new bug.