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

Move externally hosted images to the repo, and update image links

This commit is contained in:
Maria Bermudez 2019-02-05 16:14:01 -08:00
parent 4380320118
commit 0abb3de031
4 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
engine/swarm/images/swarm-discovery-service.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 141 KiB

BIN
engine/swarm/images/swarm-high-availability.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 130 KiB

BIN
engine/swarm/images/swarm-multiple-clouds.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 93 KiB

6
swarm/plan-for-production.md
View File

@ -138,7 +138,7 @@ For example, if your cluster is running in the Ireland Region of Amazon Web
Services (eu-west-1) and you configure three swarm managers (1 x primary, 2 x Services (eu-west-1) and you configure three swarm managers (1 x primary, 2 x
secondary), you should place one in each availability zone as shown below. secondary), you should place one in each availability zone as shown below.
![Swarm managers spread across availability zones](http://farm2.staticflickr.com/1657/24581727611_0a076b79de_b.jpg) ![Swarm managers spread across availability zones](/engine/swarm/images/swarm-high-availability.png)
In this configuration, the swarm cluster can survive the loss of any two In this configuration, the swarm cluster can survive the loss of any two
availability zones. For your applications to survive such failures, they must be availability zones. For your applications to survive such failures, they must be
@ -186,7 +186,7 @@ domains (availability zones). It also has swarm nodes balanced across all three
failure domains. The loss of two availability zones in the configuration shown failure domains. The loss of two availability zones in the configuration shown
below does not cause the swarm cluster to go down. below does not cause the swarm cluster to go down.
![Swarm cluster configured for HA](http://farm2.staticflickr.com/1675/24380252320_999687d2bb_b.jpg) ![Swarm cluster configured for HA](/engine/swarm/images/swarm-discovery-service.png)
It is possible to share the same Consul, etcd, or Zookeeper containers between It is possible to share the same Consul, etcd, or Zookeeper containers between
the swarm discovery and Engine container networks. However, for best the swarm discovery and Engine container networks. However, for best
@ -199,7 +199,7 @@ You can architect and build swarm clusters that stretch across multiple cloud
providers, and even across public cloud and on premises infrastructures. The providers, and even across public cloud and on premises infrastructures. The
diagram below shows an example swarm cluster stretched across AWS and Azure. diagram below shows an example swarm cluster stretched across AWS and Azure.
![Swarm cluster stretched across AWS and Azure](http://farm2.staticflickr.com/1493/24676269945_d19daf856c_b.jpg) ![Swarm cluster stretched across AWS and Azure](/engine/swarm/images/swarm-multiple-clouds.png)
While such architectures may appear to provide the ultimate in availability, While such architectures may appear to provide the ultimate in availability,
there are several factors to consider. Network latency can be problematic, as there are several factors to consider. Network latency can be problematic, as