891185 - [socorro-bixie] Build Development Environment

Status: RESOLVED INCOMPLETE

(Infrastructure & Operations Graveyard :: WebOps: Socorro, task, P1)

Description

[Brandon Burton [:solarce]]

From email

>> For testing Bixie we will need a home for the bixie-collector, bixie-processor, bixie-crontabber, bixie-crashmover, bixie-middleware, bixie-webapp(django). We also need access to RabbitMQ, Postgres, HBase, and ElasticSearch. Existing HBase and RabbitMQ can be reused. 

>> I haven't spoken to Adrian, but I'm reasonably sure that existing ES can be used. Selena is nervous about disk space and wants a clone of our staging DB setup before we put the bixie infra under any regular load.


DEV:
    1 host
      * same netflows to RabbitMQ, Postgres, Hbase, and ES as on socorro-dev)

Comment 1

[Brandon Burton [:solarce]]

:lonnen, :laura, I find three physical boxes in inventory named socorro-queuey[1-3].stage.webapp.phx1.mozilla.com that are marked as "building", was there still plans to use queuey?

Comment 2

[Laura Thomson :laura]

rhelmer was dealing with queuey, let's ask him. But I don't think so.

Comment 3

[Robert Helmer [:rhelmer]]

(In reply to Laura Thomson :laura from comment #2)
> rhelmer was dealing with queuey, let's ask him. But I don't think so.

(In reply to Brandon Burton [:solarce] from comment #1)
> :lonnen, :laura, I find three physical boxes in inventory named
> socorro-queuey[1-3].stage.webapp.phx1.mozilla.com that are marked as
> "building", was there still plans to use queuey?

Nope going with rabbitmq instead!