HA for the Join Form

[WillNilges]

We need to figure out how to keep the join form and the like operational even if MeshDB goes down.

This probably means

• Load balancer and/or floating IP
• Hosting each service atomically in both SN3 and SN10
• Caching Join Form submissions in Meshforms
• Serverside Validation of submissions in Meshforms

[WillNilges]

We agree that we won't be able to set up a whole separate instance of MeshDB in the next month, because we probably won't have the hardware (There are problems with providing a router VM direct access to the network interface). It might do to set up an instance of the Join Form elsewhere, such as Grandbox, or even our DigitalOcean droplet that hosts the status page. That way, at the very least, we will have the recordings of the submissions in S3.

[WillNilges]

We have the option of relying on .nycmesh.net for DNS (which is cloud hosted). I was thinking we could set up a separate instance of Meshforms on grandbox, or we could put one on a digital ocean droplet.

Or we could just move meshforms to the droplet.

[WillNilges]

Maybe we set up an HAProxy instance in the cloud, and then point it at prod1 and then a cloud-hosted instance of meshforms. That's probably the safest bet.

[WillNilges]

This is also a lot of work, and a lot of resources that we don't really have to do correctly. The join form + proxy in the cloud is a nice idea, but perhaps not a blocker for launch.