Closed Bug 1336267 Opened 8 years ago Closed 8 years ago

set up socorro-pigeon for antenna -stage [antenna]

Categories

(Socorro :: Antenna, task)

Product:
Socorro
Component:
Antenna
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: willkg, Assigned: miles)

References

Details

Antenna saves to s3 and then s3 emits PUT events which Pigeon is listening for. Then Pigeon sends crash ids to RabbitMQ queues. Right now, Antenna on -stage doesn't have Pigeon set up. This bug covers setting up Pigeon in the Antenna -stage environment.
One thing we want to make sure we don't do is set up something such that Socorro collector -stage saves something to s3 which triggers Pigeon which adds a crash to RabbitMQ socorro.normal queue because it'll already be in the queue and then we'll end up processing lots of crashes twice.
Assignee: nobody → miles
Update: pigeon has a smooth lambda deployment pipeline that includes auto-encryption of the secret env vars that we use (PIGEON_VIRTUAL_HOST and PIGEON_PASSWORD) client side. Updating the pigeon deployment is being baked into the main antenna deployment pipeline going forward. Both antenna and pigeon are currently pointed at the ops infra s3 buckets.
This was completed this week successfully, with pigeon running in the ops infra and pointing at CloudAMQP. We are also now running pigeon in the webeng infra for testing antenna saving to the Socorro stage crash bucket. Currently, antenna is saving to a test bucket in webeng infra that triggers a pigeon in webeng infra that points at CloudAMQP. Marking this resolved. Pigeon is running, and proven working.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
This is a big deal. Hooray!
Switching Antenna bugs to Antenna component.
Component: Infra → Antenna
You need to log in before you can comment on or make changes to this bug.