зеркало из https://github.com/docker/labs.git
updating a few references to 1.12
This commit is contained in:
Mano Marks
Родитель
e6265ec928
Коммит
dbd6a8ae14
|
|
@ -62,7 +62,7 @@ NETWORK ID NAME DRIVER SCOPE
|
|||
ef4896538cc7 none null local
|
||||
```
|
||||
|
||||
The output above shows the container networks that are created as part of a standard installation of Docker 1.12.
|
||||
The output above shows the container networks that are created as part of a standard installation of Docker.
|
||||
|
||||
New networks that you create will also show up in the output of the `docker network ls` command.
|
||||
|
||||
|
|
|
|||
|
|
@ -89,6 +89,6 @@ Two interfaces have been created inside the container that correspond to two bri
|
|||
|
||||
|
||||
|
||||
> The Docker Overlay driver has existed since Docker Engine 1.9, and an external K/V store was required to manage state for the network. Docker Engine 1.12 integrated the control plane state into Docker Engine so that an external store is no longer required. 1.12 also introduced several new features including encryption and service load balancing. Networking features that are introduced require a Docker Engine version that supports them, and using these features with older versions of Docker Engine is not supported.
|
||||
> The Docker Overlay driver has existed since Docker Engine 1.9, and an external K/V store was required to manage state for the network. Docker 1.12 integrated the control plane state into Docker Engine so that an external store is no longer required. 1.12 also introduced several new features including encryption and service load balancing. Networking features that are introduced require a Docker Engine version that supports them, and using these features with older versions of Docker Engine is not supported.
|
||||
|
||||
Next: **[MACVLAN](07-macvlan.md)**
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
##<a name="lb"></a>Load Balancing Design Considerations
|
||||
|
||||
Load balancing is a major requirement in modern, distributed applications. The new Docker Swarm mode introduced in 1.12 comes with a native internal and external load balancing functionalities that utilize both `iptables` and `ipvs`, a transport-layer load balancing inside the Linux kernel.
|
||||
Load balancing is a major requirement in modern, distributed applications. Docker Swarm mode introduced in 1.12 comes with a native internal and external load balancing functionalities that utilize both `iptables` and `ipvs`, a transport-layer load balancing inside the Linux kernel.
|
||||
|
||||
###Internal Load Balancing
|
||||
When services are created in a Docker Swarm cluster, they are automatically assigned a Virtual IP (VIP) that is part of the service's network. The VIP is returned when resolving the service's name. Traffic to that VIP will be automatically sent to all healthy tasks of that service across the overlay network. This approach avoids any client-side load balancing because only a single IP is returned to the client. Docker takes care of routing and equally distributing the traffic across the healthy service tasks.
|
||||
|
|
@ -38,7 +38,7 @@ $ docker service inspect myservice
|
|||
###External Load Balancing (Docker Routing Mesh)
|
||||
You can expose services externally by using the `--publish` flag when creating or updating the service. Publishing ports in Docker Swarm mode means that every node in your cluster will be listening on that port. But what happens if the service's task isn't on the node that is listening on that port?
|
||||
|
||||
This is where routing mesh comes into play. Routing mesh is a new feature in Docker 1.12 that combines `ipvs` and `iptables` to create a powerful cluster-wide transport-layer (L4) load balancer. It allows all the Swarm nodes to accept connections on the services' published ports. When any Swarm node receives traffic destined to the published TCP/UDP port of a running `service`, it forwards it to service's VIP using a pre-defined overlay network called `ingress`. The `ingress` network behaves similarly to other overlay networks but its sole purpose is to transport mesh routing traffic from external clients to cluster services. It uses the same VIP-based internal load balancing as described in the previous section.
|
||||
This is where routing mesh comes into play. Routing mesh is a feature introduced in Docker 1.12 that combines `ipvs` and `iptables` to create a powerful cluster-wide transport-layer (L4) load balancer. It allows all the Swarm nodes to accept connections on the services' published ports. When any Swarm node receives traffic destined to the published TCP/UDP port of a running `service`, it forwards it to service's VIP using a pre-defined overlay network called `ingress`. The `ingress` network behaves similarly to other overlay networks but its sole purpose is to transport mesh routing traffic from external clients to cluster services. It uses the same VIP-based internal load balancing as described in the previous section.
|
||||
|
||||
Once you launch services, you can create an external DNS record for your applications and map it to any or all Docker Swarm nodes. You do not need to worry about where your container is running as all nodes in your cluster look as one with the routing mesh routing feature.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Docker Swarm comes with integrated PKI. All managers and nodes in the Swarm have
|
|||
|
||||
###Securing the Data Plane
|
||||
|
||||
In Docker Engine 1.12 Swarm mode the data path (e.g. application traffic) can be encrypted out-of-the-box. This feature uses IPSec tunnels to encrypt network traffic as it leaves the source container and decrypts it as it enters the destination container. This ensure that your application traffic is highly secure when it's in transit regardless of the underlying networks. In a hybrid, multi-tenant, or multi-cloud environment, it is crucial to ensure data is secure as it traverses networks you might not have control over.
|
||||
In Docker Swarm mode the data path (e.g. application traffic) can be encrypted out-of-the-box. This feature uses IPSec tunnels to encrypt network traffic as it leaves the source container and decrypts it as it enters the destination container. This ensure that your application traffic is highly secure when it's in transit regardless of the underlying networks. In a hybrid, multi-tenant, or multi-cloud environment, it is crucial to ensure data is secure as it traverses networks you might not have control over.
|
||||
|
||||
This diagram illustrates how to secure communication between two containers running on different hosts in a Docker Swarm.
|
||||
|
||||
|
|
|
|||
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 53 KiB |
|
|
@ -11,7 +11,7 @@ When a new service (container) is created it should be able register itself with
|
|||
</p>
|
||||
|
||||
|
||||
The mechanisms that provide service discovery and load balancing can take many forms. They can be external service or provided natively within Docker without extra infrastructure. In Docker 1.12 automatic service discovery and load balancing is provided right out of the box by the Docker Engine. A service can be defined and traffic is load balanced via DNS to containers. DNS load balancing is covered later in this guide.
|
||||
The mechanisms that provide service discovery and load balancing can take many forms. They can be external service or provided natively within Docker without extra infrastructure. In Docker Swarm Mode automatic service discovery and load balancing is provided right out of the box. A service can be defined and traffic is load balanced via DNS to containers. DNS load balancing is covered later in this guide.
|
||||
|
||||
External solutions for service discovery and/or load balancing is also possible and may be desired to levarage existing infrastructure or to take advantage of special features. Common external service discovery mechanisms include Consul, etcd, and Zookeeper. Common external load balancers include HAproxy, Nginx, F5, and many more.
|
||||
<br>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Docker Swarm Mode Tutorials
|
||||
|
||||
[Docker Swarm Mode](https://docs.docker.com/engine/swarm/) is a feature included with Docker Engine 1.12. These tutorials are designed to help you quickly get started testing these new features.
|
||||
[Docker Swarm Mode](https://docs.docker.com/engine/swarm/) is a feature Docker introduced in 1.12. These tutorials are designed to help you quickly get started testing these new features.
|
||||
|
||||
* [Docker Swarm Mode full tutorial](beginner-tutorial/README.md)
|
||||
* [Service deployment on a swarm in the Cloud](cloud-quick-start/README.md)
|
||||
|
|
|
|||
|
|
@ -116,13 +116,13 @@ bxn1iivy8w7faeugpep76w50j worker3 Ready Active
|
|||
You can also find all your machines by running
|
||||
```
|
||||
$ docker-machine ls
|
||||
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
|
||||
manager1 - virtualbox Running tcp://192.168.99.100:2376 v1.12.1
|
||||
manager2 - virtualbox Running tcp://192.168.99.101:2376 v1.12.1
|
||||
manager3 - virtualbox Running tcp://192.168.99.102:2376 v1.12.1
|
||||
worker1 - virtualbox Running tcp://192.168.99.103:2376 v1.12.1
|
||||
worker2 - virtualbox Running tcp://192.168.99.104:2376 v1.12.1
|
||||
worker3 - virtualbox Running tcp://192.168.99.105:2376 v1.12.1
|
||||
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
|
||||
manager1 - virtualbox Running tcp://192.168.99.100:2376 v17.03.0-ce
|
||||
manager2 - virtualbox Running tcp://192.168.99.101:2376 v17.03.0-ce
|
||||
manager3 - virtualbox Running tcp://192.168.99.102:2376 v17.03.0-ce
|
||||
worker1 - virtualbox Running tcp://192.168.99.103:2376 v17.03.0-ce
|
||||
worker2 - virtualbox Running tcp://192.168.99.104:2376 v17.03.0-ce
|
||||
worker3 - virtualbox Running tcp://192.168.99.105:2376 v17.03.0-ce
|
||||
```
|
||||
|
||||
The next step is to create a service and list out the services. This creates a single service called `web` that runs the latest nginx:
|
||||
|
|
@ -331,7 +331,7 @@ Resources:
|
|||
Plugins:
|
||||
Network: bridge, host, null, overlay
|
||||
Volume: local
|
||||
Engine Version: 1.12.1
|
||||
Engine Version: 17.03.0-ce
|
||||
Engine Labels:
|
||||
- provider = virtualbox
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
# Service deployment on a swarm in the Cloud
|
||||
|
||||
Script that create a swarm cluster and deploy a simple service.
|
||||
Swarm is created with Swarm mode of Engine 1.12. Can be created on
|
||||
Script that create a swarm cluster and deploy a simple service. The Swarm is created with Swarm mode using Docker 1.12 or higher. Can be created on
|
||||
* Virtualbox
|
||||
* Microsoft Azure
|
||||
* Digitalocean
|
||||
|
|
@ -86,10 +85,10 @@ List all Docker host created
|
|||
```
|
||||
$ docker-machine ls
|
||||
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
|
||||
manager1 - virtualbox Running tcp://192.168.99.100:2376 v1.12.0-rc2
|
||||
manager2 - virtualbox Running tcp://192.168.99.101:2376 v1.12.0-rc2
|
||||
worker1 - virtualbox Running tcp://192.168.99.102:2376 v1.12.0-rc2
|
||||
worker2 - virtualbox Running tcp://192.168.99.103:2376 v1.12.0-rc2
|
||||
manager1 - virtualbox Running tcp://192.168.99.100:2376 v17.03.0-ce
|
||||
manager2 - virtualbox Running tcp://192.168.99.101:2376 v17.03.0-ce
|
||||
worker1 - virtualbox Running tcp://192.168.99.102:2376 v17.03.0-ce
|
||||
worker2 - virtualbox Running tcp://192.168.99.103:2376 v17.03.0-ce
|
||||
```
|
||||
|
||||
# Service details
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче