You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
I'm trying to create a cluster with floating ips of the openstack, however when I perform the join in the second VM, only the private ip of the VM is recognized in the ingress network. Even so, swarm is able to deploy services on both VMs, however, if I deploy an application (php admin) in VM1 that should query a database in VM2 (my-sql), communication does not occur because in the ingress networks in both VMs has the option peers a floating ip (of the node in which the swarm was started) and private ip (of the VM that held the join). On the other hand, if I use private ip (that are in same network) to create the cluster, everything happens as it should.
Is it possible to work around this problem and specify the floating ip of openstack at the time of doing the docker swarm join?
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION
89qbyvpqplno7zv45u5ie4dng * ubuntu1 Ready Active Leader 18.09.0
ilj6ohk1senwlzjunymzy9wya ubuntu2 Ready Active 18.09.0
I'm trying to create a cluster with floating ips of the openstack, however when I perform the join in the second VM, only the private ip of the VM is recognized in the ingress network. Even so, swarm is able to deploy services on both VMs, however, if I deploy an application (php admin) in VM1 that should query a database in VM2 (my-sql), communication does not occur because in the ingress networks in both VMs has the option peers a floating ip (of the node in which the swarm was started) and private ip (of the VM that held the join). On the other hand, if I use private ip (that are in same network) to create the cluster, everything happens as it should.
Is it possible to work around this problem and specify the floating ip of openstack at the time of doing the docker swarm join?
VM1
internal ip: 192.168.1.11
floating ip: 10.7.229.134
VM2
internal ip: 192.168.1.9
floating ip: 10.7.229.135
Reproduce:
In VM1:
docker swarm init --advertise-addr 10.7.229.134
In VM2:
docker swarm join --token SWMTKN-1-3ugdbfymlzzu3eocur7leq5lpft861e1xq1ff2mmeuxjyc4x2c-du8acd24p90miebr45sb86yjh 10.7.229.134:2377
This done, when I inspect the network ingress in VM1 and VM2, I get the following:
in VM1:
docker network inspect ingress
in VM2:
docker network inspect ingress
In VM1:
docker node ls
docker node inspect ubuntu1
docker node inspect ubuntu2
Note that when I inspect VM2, the floating ip is shown in the ManagerStatus part
Cluster visualizer from portainer:
The text was updated successfully, but these errors were encountered: