Review DTR architecture and sys reqs

Fixes docker/docs-private#46
This commit is contained in:
Joao Fernandes 2017-02-03 10:18:08 -08:00
parent 14381533fa
commit 67ff2c2293
2 changed files with 14 additions and 15 deletions

View File

@ -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

View File

@ -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.