-
Notifications
You must be signed in to change notification settings - Fork 0
Transition Mechanics
Tom Mitchell edited this page Jan 17, 2017
·
7 revisions
Things to do on the big day:
-
Snapshot both AWS hosts- Done. -
Set maintenance mode
-
N.B. This is a manual process on the AWS clearinghouse host
# Portal: sudo geni-manage-maintenance --set-outage \ "18-Jan-2017 3:00 p.m. UTC: The GENI Portal is down for scheduled maintenance." # Clearinghouse: sudo sh -c 'echo "18-Jan-2017 3:00 p.m. UTC: The GENI Portal is down for scheduled maintenance." > /etc/geni-chapi/geni_maintenance_outage.msg'
-
Enter maintenance mode
sudo geni-manage-maintenance --set-outage \ "18-Jan-2017 3:00 p.m. UTC: The GENI Portal is down for scheduled maintenance." sudo geni-manage-maintenance --clear-alert
-
Shutdown and Snapshot
- As always
- Start DNS transition
- ch.geni.net: 52.207.161.119
- portal.geni.net: 54.80.225.141
-
Disable apache service
# This should do it: update-rc.d -f apache2 remove
- Another method: http://askubuntu.com/questions/19320/how-to-enable-or-disable-services
- Reboot to test
- Export databases
- See https://github.com/GENI-NSF/geni-portal/wiki/Data-Migration
- See https://github.com/GENI-NSF/geni-ch/wiki/Data-Migration
-
Import databases
-
Test, Test, Test
-
Clear maintenance mode
-
N.B. This is a manual process on the AWS clearinghouse host
# Portal: sudo geni-manage-maintenance --clear-outage # Clearinghouse: sudo rm /etc/geni-chapi/geni_maintenance_outage.msg