diff options
author | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2014-11-14 16:24:57 +0000 |
---|---|---|
committer | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2014-11-14 16:25:05 +0000 |
commit | 9ee360ce6d98f00ea28a6eb5ae39054453417084 (patch) | |
tree | 50504041bd39ab8281bbdc8ed58c6620c7053beb | |
parent | 8c4edec0a58dca142772e95280ea62544349011e (diff) | |
download | infrastructure-9ee360ce6d98f00ea28a6eb5ae39054453417084.tar.gz |
Flesh out README a bit.
-rw-r--r-- | README | 39 |
1 files changed, 38 insertions, 1 deletions
@@ -1 +1,38 @@ -Experiments in deploying infrastructure for the Baserock project +Baserock project public infrastructure +====================================== + +None of these systems are currently Baserock systems, which should be +considered a bug. The need for project infrastructure outweighs the +benefit of using the infrastructure to drive improvements to Baserock, +at the time of writing. + +The infrastructure is set up in a way that parallels the preferred Baserock +approach to deployment. All files necessary for (re)deploying the systems +should be contained in this Git repository, with the exception of certain +private tokens (which should be simple to inject at deploy time). Each +service should be provided by a system which services only one function. + +Front-end +--------- + +All of the Baserock project's infrastructure should be behind a single +IP address, with a reverse proxy that forwards the request to the +appropriate machine based on the URL (primarily the subdomain). + +The 'frontend' system takes care of this. If you want to add a new +service to the Baserock Project infrastructure you will need to alter +the haproxy.cfg file in the frontend/ directory. + +To deploy this system: + + packer build -only=production frontend/packer_template.json + +Full HAProxy 1.5 documentation: <https://cbonte.github.io/haproxy-dconv/configuration-1.5.html>. + +Deployment to DataCentred +------------------------- + +The Packer tool requires a floating IP to be available at the time a system is +being deployed to OpenStack. Currently 85.199.252.152 should be used for this. +If you specify a floating IP that is in use by an existing instance, you will +steal it for your own instance and probably break one of our web services. |