In this tutorial we will going to setup Odysseus Studio with OdysseusNet capabilities and start it as a master node. Then worker nodes are started with docker-compose and will be dynamically added to the master node with OdysseusNet in Odysseus Studio. At next queries will be remotely executed on the worker nodes from the master node.
Setup of Odysseus Studio with OdysseusNet
Setup Odysseus with Development with Odysseus, but change the following
- Clone the odysseusnet-repository https://git.swl.informatik.uni-oldenburg.de/scm/oi/odysseusnet.git
- Choose the development-branch
- Choose the target_development_stable.target within Eclipse RCP
Now you have installed the target platform, before you launch the product, we are going to add the OdysseusNet monolithic target to the normal monolithic target (see for a general tutorial Adding features to products) :
- Double click the de.uniol.inf.is.odysseus.monolithic.product.product under the directory de.uniol.inf.is.odysseus.monolithic.product.product in the Eclipse Project explorer
- Go the the Contents-Tab
- Add de.uniol.inf.is.odysseus.net.monolithic.feature to the list of features
- Save with CTRL+S
- Go to the Overview-Tab, synchronize and launch the eclipse application, this launches the Odysseus Studio (see Odysseus Studio)
The OdysseusNet monolithic target also includes the OdysseusNet server target.
If successfully started you can close Odysseus Studio for now for changing OdysseusNet config under ODYSSEUS_HOME (OdysseusNet Configuration)
With Linux the ODYSSEUS_HOME (ODYSSEUS_HOME) is ~/.odysseus, there you can change the odysseusNet.config to
if you want to persist your registered nodes, you could also add:
In this case you should replace <PATHTOHOME> e.g. with the ODYSSEUS_HOME folder.
Setup of Odysseus worker nodes
Now we start Nexmark (a data stream simulation tool, see Getting Started with Nexmark) and Odysseus worker nodes with docker-compose, therefore create a docker-compose.yml in a directory (it will be named $CURRENT_DIRECTORY here for reference, in practice it could be e. g. the odysseusnet-repo) and with the following content (adopted from OdysseusNet Docker Compose Example):
As of now a normal Ubuntu 20.04 only supports docker-compose yml syntax to version 3.3 instead of 3.8 in Windows as stated in other yml files, but most of them are downwards compatible, because newer features are not that widespread at the moment.
As a workaround make sure the worker01-03 directories have the 777-permissions with:
Otherwise the internal Odysseus worker node user cannot access the volume properly and fails.
All configuration files will be placed under the $CURRENT_DIRECTORY, e. g. there are the following files:
logs odysseus.conf odysseusNet.conf reloadlog.store scheduling.conf store
You can then start the docker stack with:
Setup of Odysseus Webstudio
You can use the Odysseus Webstudio (WebStudio) for monitoring and interacting with the worker nodes. There are two options:
- Only use the webstudio
- Develop the webstudio
Use the webstudio
If you just want to use the Webstudio you should just download the docker-compose.yml file from here:
For Linux: As this is not a root container, you need to give read access to the user of the docker container. The easiest way is to use 777
Develop the webstudio
To install it, first clone the Webstudio-repo (https://git.swl.informatik.uni-oldenburg.de/projects/API_APPS/repos/webstudio/browse?at=refs%2Fheads%2Fdevelopment) and checkout the development-branch with
Then create and give the all permissions to everyone to the following directories as a workaround:
For starting the docker stack you can set the images accordingly in the docker-compose.yml in the home dir
At last you can start the stack with:
Add the nodes in Odysseus Studio
It the view is not available, you should use Window/Show View/other... and then select Nodes from the OdysseusNet section.
Before you can install queries on the nodes, you have to add the worker nodes with:
Install the remote query
Run the following OdysseusScript query in Odysseus Studio.
Remark, that the host is 'nexmark' instead of 'localhost', because the remote worker node 'worker_01' is started in the default docker network and access the nexmark by the DNS resolved service name 'nexmark'
See the remote query output
Here is described how you can see the remote query output.
You can the following query in Odysseus Studio to access the output (Reading Query Results via REST/Websocket):
You have to adjust the optioins-uri in the query with the rootOperators-websockets-CSV uri from
You can then show the last x elements:
In Webstudio you can see the query output unter the queries tab: