more networking info in olympic-setup.md

@Override

public void serializeForInitialReplicationInternal(ObjectOutputStream oos) throws IOException {

StringBuffer logoutput = new StringBuffer();

logger.info("Serializing regattas...");

oos.writeObject(regattasByName);

logoutput.append("Serialized " + regattasByName.size() + " regattas\n");

for (Regatta regatta : regattasByName.values()) {

logoutput.append(String.format("%3s\n", regatta.toString()));

}

logger.info("Serializing events...");

oos.writeObject(eventsById);

logoutput.append("\nSerialized " + eventsById.size() + " events\n");

for (Event event : eventsById.values()) {

logoutput.append(String.format("%3s\n", event.toString()));

}

logger.info("Serializing regattas observed...");

oos.writeObject(regattasObservedWithRaceAdditionListener);

logger.info("Serializing regatta tracking cache...");

logger.info("Serializing persisted competitors...");

oos.writeObject(competitorAndBoatStore);

logoutput.append("Serialized " + competitorAndBoatStore.getCompetitorsCount() + " persisted competitors\n");

logger.info("Serializing configuration map...");

oos.writeObject(raceManagerDeviceConfigurationsById);

logoutput.append("Serialized " + raceManagerDeviceConfigurationsById.size() + " device configuration entries\n");

for (DeviceConfiguration config : raceManagerDeviceConfigurationsById.values()) {

logoutput.append(String.format("%3s\n", config.getName()));

}

logger.info("Serializing anniversary races...");

final Map<Integer, Pair<DetailedRaceInfo, AnniversaryType>> knownAnniversaries = anniversaryRaceDeterminator

.getKnownAnniversaries();

oos.writeObject(knownAnniversaries);

logoutput.append("Serialized " + knownAnniversaries.size() + " anniversary races\n");

logger.info("Serializing next anniversary...");

final Pair<Integer, AnniversaryType> nextAnniversary = anniversaryRaceDeterminator

.getNextAnniversary();

oos.writeObject(nextAnniversary);

logoutput.append("Serialized next anniversary " + nextAnniversary + "\n");

logger.info("Serializing race count for anniversaries...");

final int currentRaceCount = anniversaryRaceDeterminator.getCurrentRaceCount();

oos.writeInt(currentRaceCount);

logoutput.append("Serialized race count for anniversaries " + currentRaceCount + "\n");

logger.info("Serializing remote sailing server references...");

final ArrayList<RemoteSailingServerReference> remoteServerReferences = new ArrayList<>(remoteSailingServerSet

.getCachedEventsForRemoteSailingServers().keySet());

oos.writeObject(remoteServerReferences);

logoutput.append("Serialized " + remoteServerReferences.size() + " remote sailing server references\n");

logger.info(logoutput.toString());

}

### Application Servers

SSH local port forwards (configured with the ``-L`` option) that use hostnames instead of IP addresses for the remote host specification are resolved each time a new connection is established through this forward. If the DNS entry resolves to multiple IPs or if the DNS entry changes over time, later connection requests through the port forward will honor the new host name's DNS resolution.

``sap-p1-2`` normally is a replica for the ``tokyo2020`` replica set, using the local RabbitMQ running on ``sap-p1-1``. Its outbound ``REPLICATION_CHANNEL`` will be ``tokyo2020-replica`` and uses the RabbitMQ running in ap-northeast-1, using an SSH port forward with local port 5673 for the ap-northeast-1 RabbitMQ (15673 for the web administration UI). A reverse port forward from ap-northeast-1 to the application port 8888 on ``sap-p1-2`` has to be established which replicas running in ap-northeast-1 will use to reach their master through HTTP. This way, adding more replicas on the AWS side in the cloud will not require any additional bandwidth between cloud and on-site network, except that the reverse HTTP channel, which uses only little traffic, will see additional traffic per replica whereas all outbound replication goes to the single exchange in the RabbitMQ node running in ap-northeast-1.

## User Groups and Permissions