Geo: Make adding a Secondary node easier
Adding a secondary
GeoNode record is a manual, error-prone process. In particular, the
name field must match exactly.
The following discussion from gitlab-development-kit!745 (merged) should be addressed:
There isn't a convenient rake task to add the secondary node because the command must be run on the secondary, but written on the primary.
rake gitlab:geo:announce_secondaryto be run on a new secondary that securely announces it to the primary node.
Then choose one:
- Most convenient and least work option: The primary automatically adds a
GeoNoderecord for the secondary (if this can done safely).
- Otherwise: Click "Add this secondary" in the primary Geo Nodes UI.
- A new secondary basically runs
rake gitlab:geo:announce_secondaryevery minute if a primary
GeoNodeexists and the machine doesn't match any