0b25bc9178d870415338f10b01bca83cf88fa097
wiki/info/landscape/olympic-setup.md
| ... | ... | @@ -503,4 +503,32 @@ Moderators who need to comment on the races shall be given more elaborate permis |
| 503 | 503 | |
| 504 | 504 | To achieve this effect, the ``tokyo2020-server`` group has the ``sailing_viewer`` role assigned for all users, and all objects, except for the top-level ``Event`` object are owned by that group. This way, everything but the event are publicly visible. |
| 505 | 505 | |
| 506 | -The ``Event`` object is owned by ``tokyo2020-moderators``, and that group grants the ``sailing_viewer`` role only to its members, meaning only the members of that group are allowed to see the ``Event`` object. |
|
| ... | ... | \ No newline at end of file |
| 0 | +The ``Event`` object is owned by ``tokyo2020-moderators``, and that group grants the ``sailing_viewer`` role only to its members, meaning only the members of that group are allowed to see the ``Event`` object. |
|
| 1 | + |
|
| 2 | +## Landscape Upgrade Procedure |
|
| 3 | + |
|
| 4 | +update git on all replicas |
|
| 5 | +stop replication on all cloud replicas: |
|
| 6 | +``` |
|
| 7 | +$ for i in `./get-replica-ips`; do ssh -o StrictHostKeyChecking=no sailing@$i "cd /home/sailing/servers/tokyo2020; /home/sailing/code/java/target/stopReplicating.sh 4qUrxMVQanLghETmM95XX3fshkHK0wNAQycuPAVNW0E="; done |
|
| 8 | +``` |
|
| 9 | + |
|
| 10 | +stop replication on-site |
|
| 11 | + |
|
| 12 | +put release in /home/trac/ |
|
| 13 | + |
|
| 14 | +refresh instance stop start on sap-p1-1 / on-site master |
|
| 15 | + |
|
| 16 | +after on-site master is healthy / available register cloud master forwarder to target groups, pay attention in eu-west-1 webserver instance works as cloud master forwarder |
|
| 17 | + |
|
| 18 | +./stop /start on on-site replica |
|
| 19 | + |
|
| 20 | +launch more like this with new user data, append (manual) to name of instance, make sure master target group has a healthy target. |
|
| 21 | + |
|
| 22 | +check :8888/gwt/status , if initial load is not starting most probably registration to master has failed (check log for Exception), if so login and do stop & start |
|
| 23 | + |
|
| 24 | +edit target group, deregister and register in the same window, save changes |
|
| 25 | + |
|
| 26 | +terminate old auto-replica |
|
| 27 | + |
|
| 28 | +wait for autoscaling group to create a new autoscaling instance, after healthy terminate manually launched instance/replica |