docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Interlock Deploy Documentation 

The previous version had inconsistencies. Some times the interlock
service was referred to as `ucp-interlock` other times just as
`interlock`. This commit made `ucp-interlock` consistent throughout.
This commit is contained in:
ollypom 2019-11-07 19:55:57 +00:00
parent d723a11f13
commit df79628808
No known key found for this signature in database
GPG Key ID: 2E6D9F4EBCB6B160
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
ee/ucp/interlock/deploy/index.md
View File

@ -1,5 +1,5 @@
--- ---
title: Deploy a layer 7 routing solution title: Deploy a layer 7 routing solution
description: Learn the deployment steps for the UCP layer 7 routing solution description: Learn the deployment steps for the UCP layer 7 routing solution
keywords: routing, proxy, interlock keywords: routing, proxy, interlock
redirect_from: redirect_from:
@ -43,11 +43,11 @@ to communicate.
4. The `ucp-interlock-extension` generates a configuration to be used by 4. The `ucp-interlock-extension` generates a configuration to be used by
the proxy service. By default the proxy service is NGINX, so this service the proxy service. By default the proxy service is NGINX, so this service
generates a standard NGINX configuration. UCP creates the `com.docker.ucp.interlock.conf-1` configuration file and uses it to configure all generates a standard NGINX configuration. UCP creates the `com.docker.ucp.interlock.conf-1` configuration file and uses it to configure all
the internal components of this service. the internal components of this service.
5. The `ucp-interlock` service takes the proxy configuration and uses it to 5. The `ucp-interlock` service takes the proxy configuration and uses it to
start the `ucp-interlock-proxy` service. start the `ucp-interlock-proxy` service.
Now you are ready to use the layer 7 routing service with your Swarm workloads. There are three primary Interlock services: core, extension, and proxy. To learn more about these services, see [TOML configuration options](https://docs.docker.com/ee/ucp/interlock/config/#toml-file-configuration-options). Now you are ready to use the layer 7 routing service with your Swarm workloads. There are three primary Interlock services: core, extension, and proxy. To learn more about these services, see [TOML configuration options](https://docs.docker.com/ee/ucp/interlock/config/#toml-file-configuration-options).
The following code sample provides a default UCP configuration. This will be created automatically when enabling Interlock as described in this section. The following code sample provides a default UCP configuration. This will be created automatically when enabling Interlock as described in this section.
@ -160,7 +160,7 @@ oqkvv1asncf6p2axhx41vylgt
Next, create a dedicated network for Interlock and the extensions: Next, create a dedicated network for Interlock and the extensions:
```bash ```bash
$> docker network create -d overlay interlock $> docker network create --driver overlay ucp-interlock
``` ```
### Create the Interlock service ### Create the Interlock service
@ -172,13 +172,12 @@ on setting up for a production environment.
```bash ```bash
$> docker service create \ $> docker service create \
--name interlock \ --name ucp-interlock \
--mount src=/var/run/docker.sock,dst=/var/run/docker.sock,type=bind \ --mount src=/var/run/docker.sock,dst=/var/run/docker.sock,type=bind \
--network interlock \ --network ucp-interlock \
--constraint node.role==manager \ --constraint node.role==manager \
--config src=service.interlock.conf,target=/config.toml \ --config src=service.interlock.conf,target=/config.toml \
{{ page.ucp_org }}/ucp-interlock:{{ page.ucp_version }} -D run -c /config.toml {{ page.ucp_org }}/ucp-interlock:{{ page.ucp_version }} -D run -c /config.toml
sjpgq7h621exno6svdnsvpv9z
``` ```
At this point, there should be three (3) services created: one for the Interlock service, At this point, there should be three (3) services created: one for the Interlock service,
@ -186,17 +185,17 @@ one for the extension service, and one for the proxy service:
```bash ```bash
$> docker service ls $> docker service ls
ID NAME MODE REPLICAS IMAGE PORTS ID NAME MODE REPLICAS IMAGE PORTS
lheajcskcbby modest_raman replicated 1/1 nginx:alpine *:80->80/tcp *:443->443/tcp sjpgq7h621ex ucp-interlock replicated 1/1 {{ page.ucp_org }}/ucp-interlock:{{ page.ucp_version }}
oxjvqc6gxf91 keen_clarke replicated 1/1 {{ page.ucp_org }}/ucp-interlock-extension:{{ page.ucp_version }} oxjvqc6gxf91 ucp-interlock-extension replicated 1/1 {{ page.ucp_org }}/ucp-interlock-extension:{{ page.ucp_version }}
sjpgq7h621ex interlock replicated 1/1 {{ page.ucp_org }}/ucp-interlock:{{ page.ucp_version }} lheajcskcbby ucp-interlock-proxy replicated 1/1 {{ page.ucp_org }}/ucp-interlock-proxy:{{ page.ucp_version }} *:80->80/tcp *:443->443/tcp
``` ```
The Interlock traffic layer is now deployed. The Interlock traffic layer is now deployed.
## Next steps ## Next steps
- [Configure Interlock](../config/index.md) - [Configure Interlock](../config/index.md)
- [Deploy applications](../usage/index.md) - [Deploy applications](../usage/index.md)
- [Production deployment information](./production.md) - [Production deployment information](./production.md)
- [Offline installation](./offline-install.md) - [Offline installation](./offline-install.md)