ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I'd recommend just going through any docker orchestration tutorial, e.g. docker swarm/stacks or even kubernetes if your feeling bold, as starting processes from cluster of docker hosts isn't very ros specific.
https://docs.docker.com/get-started/swarm-deploy/
One catch may be on how you expose the container to each other via the software define networking bridged across the docker hosts. The simplest avenue would be to ensure any ros related containers on any host are all interfaced to the same virtual network, as port forwarding is of little use with ros.
https://docs.docker.com/network/overlay/
Note that the software defined network layer may have side effects on your QoS settings, given the transport layer would be wrapped by whatever abstraction swarm or kubernetes is configured to use in securing the virtual network traffic between docker hosts in the cluster.
(Old post, back from 2016)
https://www.percona.com/blog/2016/08/03/testing-docker-multi-host-network-performance/
https://docs.docker.com/network/overlay/#encrypt-traffic-on-an-overlay-network https://www.metricfire.com/blog/understanding-dockers-net-host-option/
2 | No.2 Revision |
I'd recommend just going through any docker orchestration tutorial, e.g. docker swarm/stacks or even kubernetes if your feeling bold, as starting processes from cluster of docker hosts isn't very ros specific.
https://docs.docker.com/get-started/swarm-deploy/
One catch may be on how you expose the container to each other via the software define networking bridged across the docker hosts. The simplest avenue would be to ensure any ros related containers on any host are all interfaced to the same virtual network, as port forwarding is of little use with ros.
https://docs.docker.com/network/overlay/
Note that the software defined network layer may have side effects on your QoS settings, given the transport layer would be wrapped by whatever abstraction swarm or kubernetes is configured to use in securing the virtual network traffic between docker hosts in the cluster.
(Old post, back from 2016)
https://www.percona.com/blog/2016/08/03/testing-docker-multi-host-network-performance/
https://docs.docker.com/network/overlay/#encrypt-traffic-on-an-overlay-network
https://docs.docker.com/network/overlay/#encrypt-traffic-on-an-overlay-network
https://www.metricfire.com/blog/understanding-dockers-net-host-option/