- bac: manage your services together with their supporting infrastructure
- gmb: beware: Launchpad's ec2 command will sometimes silently break if your download cache doesn't have what you need.
- gary_poster/gmb: if you get a weird ec2 result, don't forget about ec2's postmortem option.
[introduction] [project report] [tricks] [topics]
bac: manage your services together with their supporting infrastructureWe have a service running persistently on our company's private cloud (the service is tarmac, as discussed in past weeks). We occasionally need to restart this instance for various reasons. Rather than trying to communicate the new IP for every new instance among our team manually, bac had the great idea to use dynamic DNS to make a persistent reference to the ephemeral machine.
The ddclient package can automate this nicely. Brad's first inclination was to run code this locally on his own persistent, non-ephemeral server.
However, he soon realized that he could run the software instead on the cloud – on the same machine that was running our persistent service. This made configuration simpler and, arguably more importantly, kept him from having to provide some kind of reliability guarantee to the company for his own personal machines.
The one challenge is how to store passwords and other authentication tokens in a way that is secure, shared among those who may restart the service, and also friendly to automation. We solve it with private branches, protected with SSH, managed by launchpad.
The overarching lesson is to keep your services managed together with their support infrastructure as much as possible.