openculinary / infrastructure

This repository documents the steps required to set up a fresh RecipeRadar environment
GNU Affero General Public License v3.0
5 stars 5 forks source link

Documentation: update with notes from creation of standby node #48

Closed jayaddison closed 3 weeks ago

jayaddison commented 3 weeks ago

Describe the reason for these changes and the problem that they solve

To provide ample maintenance time to replace a faulty system drive in our production server, it's worthwhile to spin up a secondary standby host that can handle traffic during the reinstallation of the server.

This process is also useful to confirm that we can run the production service from multiple machines, a property that may be useful in future.

This changeset documents the process involved in creating and running the standby host.

Note: the standby host has been installed in an unprivileged LXC container on a physically separate machine.

Briefly summarize the changes

  1. TODO: document the LXC setup steps

How have the changes been tested?

  1. Local development testing -- in particular, with three foundational microservices (api, backend and frontend), and all of the essential system services (OpenSearch, PostgreSQL, HAProxy, RabbitMQ) running within the container, the site was opened successfully from a web browser outside the container, and a successfully recipe search was performed with subsequent confirmation that an event was logged to the events.searches database table as expected.

List any issues that this change relates to Supports/documents #47.