GitLab

This modification impacts all parts of Batsim in which machines were involved.
The protocol has also been updated to allow the scheduler to send machine ranges
in its allocations. The previous syntax is still supported. Now, each comma-separated
value can either be 1 machineID or a range of machineIDs (syntax: machineIDa-machineIDb
to represent the closed interval [machineIDa, machineIDb]).

Please note that Batsim has been only been tested with old schedulers (that do not
support the new protocol syntax).

Protocol update: the scheduler can now ask for the current total consumed energy and Batsim can give the answer. It has been tested via fcfs_sleeper.py, which asks for the consumed energy instead of NOPping with probability 1/2.

Separation of the network and the server in different files (which simplified the use of XBT_LOG). Minor fixes: missing enumerated cases in string conversion, use of a switch to generate a warning on future enumerated value misses. Minor cosmetic modifications.

The protocol is now more formally explained in a markdown file (in doc/proto_description.md). Addition of two protocol features: job rejection and the possibility for the scheduler to ask for being awaken at a given time. These features have not been tested.

If the energy is enabled (by setting the -p run option), the platform is assumed to contain energy information.
Such information is read by SimGrid itself but another ones, such as the 'sleep_pstates' property, are read by Batsim.
A lot of assertions has been put in the reading of the platform file which will help generating energy platforms.
An example of such a platform can be found in platforms/energy_platform.xml. This platform follows the same rules
that those of SimGrid energy platforms but assures pstate coherency via the 'sleep_pstates' property: it says
which pstates are sleep pstates and which pstates are its associated virtual pstates (for switching ON and OFF
each pstate). More information can be found in the file 'platforms/energy_platform.xml'

The scheduler can now send messages of the form TIMESTAMP:P:M=S where M is a machineID and S the asked new pstate
for machineID. Batsim does the stuff to simulate the time & energy consumptions of the switchON/OFF (if any, you
can also switch from one computation state to another). Once the pstate of a machine has changed, Batsim sends
it on the socket with messages of the form TIMESTAMP:p:M=S where M is a machineID and S the new pstate of the
corresponding machine (note the lowercase 'p' instead of an uppercase 'P').

To simulate the energy & time costs of the switch ON/OFF, the exact same mechanism as the one presented in
SimGrid energy 1O1 is used: computing 1 flop on virtual pstates whose computational power and power
consumption met our time and energy consumptions needs.

Good advance in the C++ version. JSON files are now parsed. Machines' states are now taken into account in a better way to log what happens in the Pajé file.

New modelisation of the inter-process communication and of the process creation (and parameters). A context has been created to avoid any global variable. Network is now implemented in C++. Network parsing is done in C++ too. The server socker is now BatSim's. To be continued.