Docker Linux Container - Open vSwitch Containers - Múltiplos Servidores
Neste tutorial, vou abordar de uma forma um pouco mais complexa a configuração do Docker Container. Pensando no conceito de Cloud Computing e também no conceito de múltiplas zonas, resolvi então implementar o Open vSwitch (OVS) no ambiente em que estou estudando.
Parte 5: Testando
Chegou a hora do ping.
Servidor docker-centos6-5-srv1:
[root@docker-centos6-5-srv1 docker]# ping 172.16.42.1
PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data.
64 bytes from 172.16.42.1: icmp_seq=1 ttl=64 time=0.058 ms
64 bytes from 172.16.42.1: icmp_seq=2 ttl=64 time=0.060 ms
64 bytes from 172.16.42.1: icmp_seq=3 ttl=64 time=0.046 ms
^C
--- 172.16.42.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2305ms
rtt min/avg/max/mdev = 0.046/0.054/0.060/0.010 ms
[root@docker-centos6-5-srv1 docker]# ping 172.16.42.2
PING 172.16.42.2 (172.16.42.2) 56(84) bytes of data.
64 bytes from 172.16.42.2: icmp_seq=1 ttl=64 time=1.56 ms
64 bytes from 172.16.42.2: icmp_seq=2 ttl=64 time=0.391 ms
64 bytes from 172.16.42.2: icmp_seq=3 ttl=64 time=0.556 ms
^C
--- 172.16.42.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2366ms
rtt min/avg/max/mdev = 0.391/0.836/1.563/0.519 ms
Servidor docker-centos6-5-srv2:
[root@docker-centos6-5-srv2 docker]# ping 172.16.42.2
PING 172.16.42.2 (172.16.42.2) 56(84) bytes of data.
64 bytes from 172.16.42.2: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from 172.16.42.2: icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from 172.16.42.2: icmp_seq=3 ttl=64 time=0.033 ms
^C
--- 172.16.42.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2340ms
rtt min/avg/max/mdev = 0.033/0.035/0.038/0.007 ms
[root@docker-centos6-5-srv2 docker]# ping 172.16.42.1
PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data.
64 bytes from 172.16.42.1: icmp_seq=1 ttl=64 time=1.33 ms
64 bytes from 172.16.42.1: icmp_seq=2 ttl=64 time=0.391 ms
64 bytes from 172.16.42.1: icmp_seq=3 ttl=64 time=0.487 ms
^C
--- 172.16.42.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2625ms
rtt min/avg/max/mdev = 0.391/0.738/1.337/0.425 ms
Agora é a hora de brincar entre os containers.
Servidor docker-centos6-5-srv1:
[root@docker-centos6-5-srv1 docker]# ping 172.16.42.1
PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data.
64 bytes from 172.16.42.1: icmp_seq=1 ttl=64 time=0.058 ms
64 bytes from 172.16.42.1: icmp_seq=2 ttl=64 time=0.060 ms
64 bytes from 172.16.42.1: icmp_seq=3 ttl=64 time=0.046 ms
^C
--- 172.16.42.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2305ms
rtt min/avg/max/mdev = 0.046/0.054/0.060/0.010 ms
[root@docker-centos6-5-srv1 docker]# ping 172.16.42.2
PING 172.16.42.2 (172.16.42.2) 56(84) bytes of data.
64 bytes from 172.16.42.2: icmp_seq=1 ttl=64 time=1.56 ms
64 bytes from 172.16.42.2: icmp_seq=2 ttl=64 time=0.391 ms
64 bytes from 172.16.42.2: icmp_seq=3 ttl=64 time=0.556 ms
^C
--- 172.16.42.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2366ms
rtt min/avg/max/mdev = 0.391/0.836/1.563/0.519 ms
Servidor docker-centos6-5-srv2:
[root@docker-centos6-5-srv2 docker]# ping 172.16.42.2
PING 172.16.42.2 (172.16.42.2) 56(84) bytes of data.
64 bytes from 172.16.42.2: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from 172.16.42.2: icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from 172.16.42.2: icmp_seq=3 ttl=64 time=0.033 ms
^C
--- 172.16.42.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2340ms
rtt min/avg/max/mdev = 0.033/0.035/0.038/0.007 ms
[root@docker-centos6-5-srv2 docker]# ping 172.16.42.1
PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data.
64 bytes from 172.16.42.1: icmp_seq=1 ttl=64 time=1.33 ms
64 bytes from 172.16.42.1: icmp_seq=2 ttl=64 time=0.391 ms
64 bytes from 172.16.42.1: icmp_seq=3 ttl=64 time=0.487 ms
^C
--- 172.16.42.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2625ms
rtt min/avg/max/mdev = 0.391/0.738/1.337/0.425 ms
Agora é a hora de brincar entre os containers.
*Gostei deste Open vSwitch, solução bem interessante.
------------------------------------------------------
¿? -> keyboard Error: No Keyboard Present, PRESS F1 to continue.