Concourse on Lattice

These two scripts will get you going from a regular old Lattice deployment to a running, scalable Concourse cluster.

Have fun!

usage

Grab Lattice, deploy it somewhere (follow their docs), and target it.

Then, run:

./start-atc 'postgres://user:pass@your-progres-server.com:5432/atc'
./start-worker 'http://atc.your-lattice-ip.xip.io'

This will spin up a single, empty ATC server, and then one worker, which will register with the ATC.

To populate the ATC with a Concourse pipeline config, download Fly from the ATC's web UI, and run the following:

export ATC_URL='http://atc.your-lattice-ip.xip.io'
fly configure -c path/to/pipeline.yml

Or, just run one-off builds against it.

scaling up

Both the ATC and the workers can be scaled up and down. though it doesn't really make sense to have any more than you have cells.

caveats

• Concourse's build scheduling across workers is nowhere near as sophisticated as Diego's, but is "good enough" to just throw on Lattice, given that most builds are finite and don't have predetermined memory/disk limits.

• Currently the workers are publicly routable. This is bad.

• The PostgreSQL server must run externally. Once Diego does persistence/TCP routing this will be easier.

• The workers have no memory/disk limits, and may tend to monopolize their host cell.