1118297 - create terraform config for Socorro

Status: RESOLVED FIXED

(Socorro :: Infra, task)

Description

[Robert Helmer [:rhelmer]]

Socorro needs a Terraform config to describe the Socorro infra:

load balancers -> collectors
processors
crontabber
postgres server(s)
ES server(s)
S3 bucket(s)
SQS

Comment 1

[Daniel Maher [:phrawzty]]

Excited to work on this one with you, Rob. :D

Comment 2

[Daniel Maher [:phrawzty]]

Initial commit of the working model: https://github.com/mozilla/socorro-infra/pull/8

Comment 3

[Daniel Maher [:phrawzty]]

08:44:32 < phrawzty> rhelmer: what would you consider the condition(s) for resolution to be ?
08:47:20 < rhelmer> phrawzty: so re: your question, I guess that when we make changes to the packer
                    config in socorro-infra then a CI job builds and pushes a new AMI
08:48:07 < rhelmer> phrawzty: what I was typing before was trying to think through the mechanics of
                    bootstrapping the buildbox ... it needs to build the env/consul RPMs that go into
                    the packer box right? and we want the buildbox to use the packer-generated AMI,
                    which this box is also building :)
08:49:08 < rhelmer> that should all be fine once we've run everything once
08:49:43 < rhelmer> phrawzty: I guess right now we can't easily trigger changes to only terraform or
                    only packer since they're in the same repo though
08:51:25 < rhelmer> phrawzty: anyway I think when we push changes to socorro-infra that involve packer
                    changes, packer should run in CI and generate a new AMI, and that resolves bug
                    1118294
08:51:55 < rhelmer> phrawzty: terraform picking up that new AMI and running "terraform apply" is a
                    next step, but separate from that bug
08:53:29 < phrawzty> rhelmer: in this case, does "CI" refer to Travis, or to whatever we're running
                     (Jenkins, DeadCI) ?
08:53:54 < rhelmer> phrawzty: I was thinking DeadCI on our buildbox would be the place

Comment 4

[Daniel Maher [:phrawzty]]

oh god formatting sorry

Comment 5

[Robert Helmer [:rhelmer]]

Taking per our discussion in https://docs.google.com/a/mozilla.com/document/d/1vBtHAnXRbl84SVW19BsOqP4p22YwaN5S1BKheKERmjw/edit#

Comment 6

[Robert Helmer [:rhelmer]]

I think the only thing we're missing here is making sure we've captured pre-existing resources like S3 buckets, and possibly other things.

Terraform doesn't support some things like IAM roles yet but I don't think we need to leave this bug open for that, we can add it as support becomes available.

Comment 7

[Daniel Maher [:phrawzty]]

To integrate the S3 buckets into our model we'd need to prefix them with $environment - this is problematic since, well, they already exist and are being used.  The yak shave here would be creating new buckets and copying all the data over.  How bad do we want it? :)

Comment 8

[Daniel Maher [:phrawzty]]

We've created the hell out of many Terraform configs over the past month or so, and I suspect that this bug is no longer appropriate since it no longer encapsulates a measurable goal.  Closing out - we can create new TF-related bugs as necessary.