Configuration

Configuration

The software contains a configuration file, which can be used to change some system parameter, this file is /resources/orchestator.xml

The project contains already a configuration file with default values, before to change it setting the values to be used in the real use case, remember to run this commands in the project folder

git update-index --skip-worktree src/main/resources/orchestrator.xml
git update-index --skip-worktree src/main/resources/frevoConfiguration.json

These are the values in the file

<settings>
   <serverURI>123.123.123.123</serverURI> <!-- URI of the XMPP server  -->
   <serverName>pippo.pluto.it</serverName>  <!-- name of the XMPP server  -->
   <username>orchestrator</username> <!-- username to be used to connect to the XMPP Server -->
   <serverPassword>orchestrator</serverPassword> <!--  password to be used from the orchestator to connect to the XMPP server (temporary solution) -->
   <optimizationUser>frevo</optimizationUser> <!--  XMPP username of the Optimization Tool  --> 
   <configEnabled>true</configEnabled> <!-- Indication if the configuration of the simulators has to be done or not -->
   <startingTimeout>30000</startingTimeout> <!-- Time used to wait new Simulation Managers -->
   <localOptimization>false</localOptimization> <!-- Indicates if the  Optimization Tool has to be launched by the Orchestrator -->
   <optimizationToolPath>/home/Desktop/frevo.xmpp-0.0.1-SNAPSHOT-jar-with-dependencies.jar</optimizationToolPath> <!-- Path of the optimization tool executable -->
   <optimizationToolPassword>blah</optimizationToolPassword> <!-- To be used if the Optimization Tool has to be launched from the Orchestrator  -->
   <localSimulationManager>false</localSimulationManager> <!-- Indicates if the  Simulation Manager has to be launched by the Orchestrator -->
   <simulationManagerPath>/home/Desktop/stageManager.jar</simulationManagerPath> <!-- Path of the simulation manager executable -->

</settings>

If the software has been launched also for the deployment of the Simulation Managers, before it is needed to set up one cluster of available Simulation Servers using Kubernetes. Then the list of Simulation Managers to be installed can be defined using a configuration file, to be inserted in the configuration folder. The file needs to be named deployment.json and located in the SOO configuration folder (one example can be found in resources/deployment.json). The file format is based on the one defined for the deployments of Kubernetes and can be used to deploy all the managers that are needed for the desired optimization/simulation process.