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

Rename interlock in TOC (#414)

This commit is contained in:
Jim Galasyn 2018-01-10 16:27:36 -08:00
parent a1b2624583
commit d9d05a6ee6
5 changed files with 51 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
_data/toc.yaml
View File

@ -1701,13 +1701,13 @@ manuals:
title: Manage secrets title: Manage secrets
- path: /datacenter/ucp/3.0/guides/user/secrets/grant-revoke-access/ - path: /datacenter/ucp/3.0/guides/user/secrets/grant-revoke-access/
title: Grant access to secrets title: Grant access to secrets
- sectiontitle: Interlock - sectiontitle: Layer 7 routing
section: section:
- title: Interlock overview - title: Layer 7 routing overview
path: /datacenter/ucp/3.0/guides/interlock/ path: /datacenter/ucp/3.0/guides/interlock/
- sectiontitle: Introduction - sectiontitle: Introduction
section: section:
- title: What is Interlock - title: What is Layer 7 routing
path: /datacenter/ucp/3.0/guides/interlock/intro/ path: /datacenter/ucp/3.0/guides/interlock/intro/
- title: Architecture - title: Architecture
path: /datacenter/ucp/3.0/guides/interlock/intro/architecture/ path: /datacenter/ucp/3.0/guides/interlock/intro/architecture/
@ -1723,7 +1723,7 @@ manuals:
path: /datacenter/ucp/3.0/guides/interlock/install/offline/ path: /datacenter/ucp/3.0/guides/interlock/install/offline/
- sectiontitle: Configuration - sectiontitle: Configuration
section: section:
- title: Interlock - title: Layer 7 routing
path: /datacenter/ucp/3.0/guides/interlock/configuration/ path: /datacenter/ucp/3.0/guides/interlock/configuration/
- title: Service labels - title: Service labels
path: /datacenter/ucp/3.0/guides/interlock/configuration/service-labels/ path: /datacenter/ucp/3.0/guides/interlock/configuration/service-labels/
@ -1733,7 +1733,7 @@ manuals:
path: /datacenter/ucp/3.0/guides/interlock/extensions/nginx/ path: /datacenter/ucp/3.0/guides/interlock/extensions/nginx/
- title: HAProxy - title: HAProxy
path: /datacenter/ucp/3.0/guides/interlock/extensions/haproxy/ path: /datacenter/ucp/3.0/guides/interlock/extensions/haproxy/
- sectiontitle: Deploy apps with Interlock - sectiontitle: Deploy apps with Layer 7 routing
section: section:
- title: Basic deployment - title: Basic deployment
path: /datacenter/ucp/3.0/guides/interlock/usage/ path: /datacenter/ucp/3.0/guides/interlock/usage/

29
datacenter/ucp/3.0/guides/interlock/index.md
View File

@ -1,30 +1,39 @@
--- ---
title: Interlock overview title: Layer 7 routing overview
description: Learn about Interlock, an application routing and load balancing system description: Learn about Layer 7 routing, an application routing and load balancing system
for Docker Swarm. for Docker Swarm.
keywords: ucp, interlock, load balancing keywords: ucp, layer 7, routing, load balancing
ui_tabs:
- version: ucp-3.0
orhigher: false
next_steps:
- path: ops/
title: Updates
- path: ops/tuning/
title: Tuning
--- ---
{% if include.version=="ucp-3.0" %}
Interlock is an application routing and load balancing system for Docker Swarm. It uses Layer 7 routing is an application routing and load balancing system for Docker Swarm. It uses
the Docker Remote API to automatically configure extensions such as Nginx or HAProxy for the Docker Remote API to automatically configure extensions such as Nginx or HAProxy for
application traffic. application traffic.
## About ## About
- [Introduction](intro/index.md) - [Introduction](intro/index.md)
- [What is Interlock](intro/index.md) - [What is Layer 7 routing](intro/index.md)
- [Architecture](intro/architecture.md) - [Architecture](intro/architecture.md)
## Deployment ## Deployment
- [Get started](install/index.md) - [Get started](install/index.md)
- [Deploy Interlock manually](install/manual-deployment.md) - [Deploy Layer 7 routing manually](install/manual-deployment.md)
- [Deploy Interlock offline](install/offline.md) - [Deploy Layer 7 routing offline](install/offline.md)
- [Deploy Interlock for production](install/production.md) - [Deploy Layer 7 routing for production](install/production.md)
## Configuration ## Configuration
- [Interlock configuration](configuration/index.md) - [Layer 7 routing configuration](configuration/index.md)
- [Service labels](configuration/service-labels.md) - [Service labels](configuration/service-labels.md)
## Extensions ## Extensions
@ -48,3 +57,5 @@ application traffic.
- [Updates](ops/index.md) - [Updates](ops/index.md)
- [Tuning](ops/tuning.md) - [Tuning](ops/tuning.md)
{% endif %}

6
datacenter/ucp/3.0/guides/interlock/install/index.md
View File

@ -1,8 +1,8 @@
--- ---
title: Get started with Interlock title: Get started with Layer 7 routing
description: earn about Interlock, an application routing and load balancing system description: Learn about Layer 7 routing, an application routing and load balancing system
for Docker Swarm. for Docker Swarm.
keywords: ucp, interlock, load balancing keywords: ucp, layer 7, routing, load balancing
ui_tabs: ui_tabs:
- version: ucp-3.0 - version: ucp-3.0
orhigher: false orhigher: false

18
datacenter/ucp/3.0/guides/interlock/intro/architecture.md
View File

@ -1,6 +1,6 @@
--- ---
title: Interlock architecture title: Layer 7 routing architecture
description: Learn about Interlock, an application routing and load balancing system description: Learn about Layer 7 routing, an application routing and load balancing system
for Docker Swarm. for Docker Swarm.
keywords: ucp, interlock, load balancing keywords: ucp, interlock, load balancing
ui_tabs: ui_tabs:
@ -21,7 +21,7 @@ The following are definitions that are used:
- GRPC: A high-performance RPC framework - GRPC: A high-performance RPC framework
## Services ## Services
Interlock runs entirely as Docker Swarm services. There are three core services Layer 7 routing runs entirely as Docker Swarm services. There are three core services
in an Interlock routing layer: core, extension and proxy. in an Interlock routing layer: core, extension and proxy.
## Core ## Core
@ -30,17 +30,17 @@ an upstream configuration for the extensions. This is served on a GRPC API that
extensions are configured to access. extensions are configured to access.
## Extension ## Extension
The extension service is a helper service that queries the Interlock GRPC API for the The extension service is a helper service that queries the Layer 7 routing GRPC API for the
upstream configuration. The extension service uses this to configure upstream configuration. The extension service uses this to configure
the proxy service. For proxy services that use files such as Nginx or HAProxy the the proxy service. For proxy services that use files such as Nginx or HAProxy the
extension service generates the file and sends it to Interlock using the GRPC API. Interlock extension service generates the file and sends it to Interlock using the GRPC API. Interlock
then updates the corresponding Docker Config object for the proxy service. then updates the corresponding Docker Config object for the proxy service.
## Proxy ## Proxy
The proxy service handles the actual requests for the upstream application services. These The proxy service handles the actual requests for the upstream application services. These
are configured using the data created by the corresponding extension service. are configured using the data created by the corresponding extension service.
Interlock manages both the extension and proxy service updates for both configuration changes Layer 7 routing manages both the extension and proxy service updates for both configuration changes
and application service deployments. There is no intervention from the operator required. and application service deployments. There is no intervention from the operator required.
{% endif %} {% endif %}

28
datacenter/ucp/3.0/guides/interlock/intro/index.md
View File

@ -1,6 +1,6 @@
--- ---
title: What is Interlock title: What is Layer 7 routing
description: Learn about Interlock, an application routing and load balancing system description: Learn about Layer 7 routing, an application routing and load balancing system
for Docker Swarm. for Docker Swarm.
keywords: ucp, interlock, load balancing keywords: ucp, interlock, load balancing
ui_tabs: ui_tabs:
@ -10,7 +10,7 @@ ui_tabs:
{% if include.version=="ucp-3.0" %} {% if include.version=="ucp-3.0" %}
Interlock is an application routing proxy service for Docker. Layer 7 routing is an application routing proxy service for Docker.
## Design Goals ## Design Goals
@ -19,48 +19,48 @@ Interlock is an application routing proxy service for Docker.
- Support external load balancers (nginx, haproxy, F5, etc) via extensions - Support external load balancers (nginx, haproxy, F5, etc) via extensions
- Least privilege for extensions (no Docker API access) - Least privilege for extensions (no Docker API access)
Interlock was designed to be a first class application routing layer for Docker. Layer 7 routing was designed to be a first class application routing layer for Docker.
The following are the high level features it provides: The following are the high level features it provides:
## Automatic Configuration ## Automatic Configuration
Interlock uses the Docker API for configuration. The user does not have to manually Layer 7 routing uses the Docker API for configuration. The user does not have to manually
update or restart anything to make services available. update or restart anything to make services available.
## Native Swarm Support ## Native Swarm Support
Interlock is fully Docker native. It runs on Docker Swarm and routes traffic using Layer 7 routing is fully Docker native. It runs on Docker Swarm and routes traffic using
cluster networking and Docker services. cluster networking and Docker services.
## High Availability ## High Availability
Interlock runs as Docker services which are highly available and handle failures gracefully. Layer 7 routing runs as Docker services which are highly available and handle failures gracefully.
## Scalability ## Scalability
Interlock uses a modular design where the proxy service is separate. This allows an Layer 7 routing uses a modular design where the proxy service is separate. This allows an
operator to individually customize and scale the proxy layer to whatever demand. This is operator to individually customize and scale the proxy layer to whatever demand. This is
transparent to the user and causes no downtime. transparent to the user and causes no downtime.
## SSL ## SSL
Interlock leverages Docker Secrets to securely store and use SSL certificates for services. Both Layer 7 routing leverages Docker Secrets to securely store and use SSL certificates for services. Both
SSL termination and TCP passthrough are supported. SSL termination and TCP passthrough are supported.
## Context Based Routing ## Context Based Routing
Interlock supports advanced application request routing by context or path. Layer 7 routing supports advanced application request routing by context or path.
## Host Mode Networking ## Host Mode Networking
Interlock supports running the proxy and application services in "host" mode networking allowing Layer 7 routing supports running the proxy and application services in "host" mode networking allowing
the operator to bypass the routing mesh completely. This is beneficial if you want the operator to bypass the routing mesh completely. This is beneficial if you want
maximum performance for your applications. maximum performance for your applications.
## Blue-Green and Canary Service Deployment ## Blue-Green and Canary Service Deployment
Interlock supports blue-green service deployment allowing an operator to deploy a new application Layer 7 routing supports blue-green service deployment allowing an operator to deploy a new application
while the current version is serving. Once traffic is verified to the new application the operator while the current version is serving. Once traffic is verified to the new application the operator
can scale the older version to zero. If there is a problem the operation is quickly reversible. can scale the older version to zero. If there is a problem the operation is quickly reversible.
## Service Cluster Support ## Service Cluster Support
Interlock supports multiple extension+proxy combinations allowing for operators to partition load Layer 7 routing supports multiple extension+proxy combinations allowing for operators to partition load
balancing resources for uses such as region or organization based load balancing. balancing resources for uses such as region or organization based load balancing.
## Least Privilege ## Least Privilege
Interlock supports (and recommends) being deployed where the load balancing Layer 7 routing supports (and recommends) being deployed where the load balancing
proxies do not need to be colocated with a Swarm manager. This makes the proxies do not need to be colocated with a Swarm manager. This makes the
deployment more secure by not exposing the Docker API access to the extension or proxy services. deployment more secure by not exposing the Docker API access to the extension or proxy services.