Closed
Bug 891409
Opened 12 years ago
Closed 12 years ago
[socorro-bixie] Build Staging Environment
Categories
(Infrastructure & Operations Graveyard :: WebOps: Socorro, task, P1)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bburton, Assigned: bburton)
References
Details
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.
STAGE:
5 host cluster
* admin node for crontabber, crashmover
* collector, processor, mware, and webapp get one node each
* netflows to socorro stage datastores
Data Stores:
Clone stage's existing Database infra
Assignee | ||
Comment 1•12 years ago
|
||
The initial batch of manifests, templates, and files have been committed to Puppet svn with the completed of bug 904690
I've gone through everything and done a simple rename of 'stage' to 'bixie_stage' to start the customization
I haven't applied to the new Puppet classes to the node definitions yet, I'll work with :lonnen to get them into a better state and we'll begin testing them.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•12 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → INCOMPLETE
Updated•9 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•