From 791495bcebb253a002efa684b63f4cc6397b233c Mon Sep 17 00:00:00 2001 From: Patrick Dwyer Date: Mon, 30 Apr 2018 16:15:06 -0400 Subject: [PATCH] Updated documentation to include DNS requirements --- deployment.md | 8 ++++++++ swarm.md | 7 ++++++- 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/deployment.md b/deployment.md index c53c916..7174020 100644 --- a/deployment.md +++ b/deployment.md @@ -26,3 +26,11 @@ The following ports need to be open and accessible between hosts in the Sensing - **9555/tcp**: Swarm external port for Kafka communication - **17141/tcp**: Sensing API Insecure port - **17504/tcp**: Sensing API Secure port + +# DNS + +Internal DNS (as handled by Route 53) **must include** the following routes, for now all pointing at the Swarm Master node: + + - sensing-api.savior.internal + - sensing-ca.savior.internal + - sensing-kafka.savior.internal diff --git a/swarm.md b/swarm.md index 9738728..ca78aa6 100644 --- a/swarm.md +++ b/swarm.md @@ -66,6 +66,11 @@ The utility of each of these ports: - **17141**: Sensing API Insecure port (HTTP) - **17504**: Sensing API Secure port (HTTP/TLS) +As well, internal DNS (as handled by Route 53) **must include** the following routes, for now all pointing at the Swarm Master node: + + - sensing-api.savior.internal + - sensing-ca.savior.internal + - sensing-kafka.savior.internal ### Manager Node @@ -111,7 +116,7 @@ Start the external docker overlay network > sudo docker network create --driver overlay --attachable --subnet 192.168.1.0/24 apinet ``` -Notice that we're directly setting a subnet for use in the Swarm network - if we don't do this, the default network used in swarm has conflicts with the default subnet in the AWS VPC, that is overlapping `10.0.1.0/24` segments, which wreaks havoc with DNS and container routing. The name of this network, `apinet`, **must** match the defined external network name in the `docker-compose-swarm.yml` and `docker-compose-registry.yml` compose files. +Notice that we're directly setting a subnet for use in the Swarm network - if we don't do this, the default network used in swarm has conflicts with the default subnet in the AWS VPC, that is overlapping `10.0.1.0/24` segments, which wreaks havoc with DNS and container routing. The name of this network, `apinet`, **must** match the defined external network name in the `docker-compose-swarm.yml` compose file. ## Pull the API code