High Availability on AWS
Adds walkthrough for setting up GitLab in AWS in High Availability mode.
Merge request reports
Activity
I'm starting to see how GLU and docs can be complimentary. If GLU is the guide while docs are the reference material, that makes sense. This merge request doesn't reference the HA docs at all, but it should. There are probably parts of the HA docs that should be moved to a GLU topic, too (Generic HA guide?).
- source/high-availability/aws/index.html.md 0 → 100644
285 from anywhere. 286 287 The Load Balancer Health will allow us to indicate where to ping and what 288 makes up a healthy or unhealthy instance. 289 290 We won't add the instance on the next session because we'll destroy it 291 momentarily as we'll be using the image we where creating. We will keep 292 the Enable Cross-Zone and Enable Connection Draining active. 293 294 After we finish creating the Load Balancer we can re visit our Security 295 Groups to improve access only through the ELB and any other requiremnt 296 you might have. 297 298 *** 299 300 ## Auto Scaling Group @balameb We don't know the effects of downscaling - Sidekiq jobs could be lost if the shutdown isn't graceful enough. Given our lack of experience with downscaling GitLab, and no knowledge of anyone currently doing this, let's avoid mentioning it as an option in this guide. Autoscaling is not required in AWS so we can just describe a 2-3 node static instance.
LGTM, consider adding a TOC (self-generated, e.g. as on about.gitlab.com/handbook ).
Related issue https://gitlab.com/gitlab-org/University/issues/33
mentioned in commit a8139483
