...
If you develop with Odysseus and checked out its sourcecode, you can start OdysseusNet by adding the plugin de.uniol.inf.is.odysseus.net.monolithic.feature (if you're developing with the monolithic version of Odysseus) or the plugin de.uniol.inf.is.odysseus.net.server.feature (server-version of Odysseus) to your product- or launch-definitions. These features contain all underlying OdysseusNet-Features currently available. A more detailed description which feature encapsulates which function can be found in Developing with OdysseusNet.
Docker
OdysseusNet is also available as docker image: odysseusol/odysseusnet.
Remark: Currently, we are developing a master/worker based version of OdysseusNet. In this case, only the master node needs to be an OdysseusNet image. The worker images could be standard Odysseus images. To allow easisier result handling, we provide an image for the worker nodes with an integrated kafka handling: odysseusol/odysseus_kafka
See OdysseusNet Docker Compose Example
Remark: In cases where the workers should communicate with each other, it is important, that the master and the worker are in the same network, i.e. in case of using docker, you cannot use a master from outside the docker network. To communicate with the master node, you should use WebStudio. Another solution would be to use e.g. kafka (that is visible to all the nodes) to communicate between the nodes.
See e.g. https://docs.docker.com/network/ or https://www.tutorialworks.com/container-networking/
Network structure of OdysseusNet: OdysseusNodes and NodeGroups
...