From 67ff2c229379b55f84dfa3fc417d4db3b493ffbf Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Fri, 3 Feb 2017 10:18:08 -0800 Subject: [PATCH] Review DTR architecture and sys reqs Fixes docker/docs-private#46 --- datacenter/dtr/2.2/guides/architecture.md | 19 +++++++++---------- .../2.2/guides/install/system-requirements.md | 10 +++++----- 2 files changed, 14 insertions(+), 15 deletions(-) diff --git a/datacenter/dtr/2.2/guides/architecture.md b/datacenter/dtr/2.2/guides/architecture.md index e9e1102dc4..f1df5baa27 100644 --- a/datacenter/dtr/2.2/guides/architecture.md +++ b/datacenter/dtr/2.2/guides/architecture.md @@ -35,7 +35,6 @@ are created: | Name | Type | Description | |:-------|:--------|:---------------------------------------------------------------------------------------| -| dtr-br | bridge | Allows DTR components on the same node to communicate with each other in a secure way | | dtr-ol | overlay | Allows DTR components running on different nodes to communicate, to replicate DTR data | @@ -43,15 +42,14 @@ are created: DTR uses these named volumes for persisting data: -| Volume name | Description | -|:------------------------------------|:---------------------------------------------------------------------------------| -| dtr-ca-<replica_id> | Root key material for the DTR root CA that issues certificates | -| dtr-etcd-<replica_id> | DTR configuration data | -| dtr-notary-<replica_id> | Certificate and keys for the Notary components | -| dtr-postgres-<replica_id> | DTR configuration data | -| dtr-registry-<replica_id> | Docker images data, if DTR is configured to store images on the local filesystem | -| dtr-rethink-<replica_id> | Repository metadata | -| dtr-nfs-registry-<replica_id> | Docker images data, if DTR is configured to store images on NFS | +| Volume name | Description | +|:--------------------------------------|:---------------------------------------------------------------------------------| +| dtr-ca-<replica_id> | Root key material for the DTR root CA that issues certificates | +| dtr-notary-<replica_id> | Certificate and keys for the Notary components | +| dtr-nautilus-store-<replica_id> | Vulnerability scans data | +| dtr-registry-<replica_id> | Docker images data, if DTR is configured to store images on the local filesystem | +| dtr-rethink-<replica_id> | Repository metadata | +| dtr-nfs-registry-<replica_id> | Docker images data, if DTR is configured to store images on NFS | You can customize the volume driver used for these volumes, by creating the volumes before installing DTR. During the installation, DTR checks which volumes @@ -70,6 +68,7 @@ You can also configure DTR to use these storage backends: * NFS * Amazon S3 * Cleversafe +* Google Cloud Storage * OpenStack Swift * Microsoft Azure diff --git a/datacenter/dtr/2.2/guides/install/system-requirements.md b/datacenter/dtr/2.2/guides/install/system-requirements.md index 104d0d0d6a..05ca08299c 100644 --- a/datacenter/dtr/2.2/guides/install/system-requirements.md +++ b/datacenter/dtr/2.2/guides/install/system-requirements.md @@ -10,17 +10,17 @@ Before installing, be sure your infrastructure has these requirements. ## Software requirements You can only install DTR on a node that is being managed by Docker Universal -Control Plane 2.1. +Control Plane. ## Ports used When installing DTR on a node, make sure the following ports are open on that node: -| Direction | Port | Purpose | -|:---------:|:-----|:--------------------------------------| -| in | 80 | Web app and API client access to DTR. | -| in | 443 | Web app and API client access to DTR. | +| Direction | Port | Purpose | +|:---------:|:--------|:--------------------------------------| +| in | 80/tcp | Web app and API client access to DTR. | +| in | 443/tcp | Web app and API client access to DTR. | These ports are configurable when installing DTR.