replaced external IP address of RabbitMQ by rabbit.sapsailing.com

Change-Id: I877990fe29277884cd3251f187c8a284a4d25ea7
This commit is contained in:
Axel Uhl
2016-04-22 11:49:24 +02:00
parent 00e0f9a438
commit 61e6f1a113
+3 -3
View File
@@ -46,7 +46,7 @@ Whichever master is current, we map the main Apache URL http://kielerwoche2015-m
- http://club.tractrac.com/events/event_20150625_KielerWoch/jsonservice.php for the Silbernes Band
## Replication
- RabbitMQ server for replication: 52.16.112.6 (Web: http://52.16.112.6:15672/) or internal host name rabbit.internal.sapsailing.com)
- RabbitMQ server for replication: rabbit.sapsailing.com (Web: http://rabbit.sapsailing.com:15672/) or internal host name rabbit.internal.sapsailing.com)
- Replication Exchange Name: KW2015
## Switching from one Master to Another
@@ -64,7 +64,7 @@ Whichever master is current, we map the main Apache URL http://kielerwoche2015-m
- upgrade the replicas (including the Cube Replica) to the new master if the new master runs a different release than the old master, using `refreshInstance.sh`
- adjust the replicas' (including the Cube Replica) `env.sh` to point to the new master with their `REPLICATE_MASTER_SERVLET_HOST` setting
- restart the Java server instance on the replicas (including the Cube Replica), using the usual `./stop; ./start` sequence. This will automatically re-start the replication
- when the replicas have finished their initial load (can be verified by looking at the RabbitMQ queues at http://ec2-52-16-112-6.eu-west-1.compute.amazonaws.com:15672/#/queues which should no longer have any "initialLoad" queues), add them again to the load balancer
- when the replicas have finished their initial load (can be verified by looking at the RabbitMQ queues at http://rabbit.sapsailing.com:15672/#/queues which should no longer have any "initialLoad" queues), add them again to the load balancer
- in the Cube server's Apache configuration let http://kielerwoche2015.sapsailing.com point again to the local replica by editing `/etc/apache2/sites-enabled/001-events.conf`, then as user `root` run `service httpd reload`
- shut down the other master server to avoid confusion with database writes
@@ -75,4 +75,4 @@ Whichever master is current, we map the main Apache URL http://kielerwoche2015-m
## Local network setup
basically see [[Set up local network with replication server|wiki/event-network-with-replica]] operating with a Meraki and a local replica server using 1 physical WAN interface on the Meraki. Meraki network config for this event can be found under [[Meraki Dashboard|https://n142.meraki.com/KiWo-TraWo/n/Rzu9tdoc]]
- Accessing replica server from `sailing-demo.sapsailing.com` via ssh or http from `ADMIN` network
- Accessing replica server from `sailing-demo.sapsailing.com` via ssh or http from `ADMIN` network