You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Speed and core are actual attributes of a host and not additional properties.
I think these should be added next to the id, name and state in the JSON dict of each machine in the SIMULATION_BEGINS event.
In the same vein, it would be good to have all the Batsim options forwarded to the scheduler in the SIMULATION_BEGIN, in order to test from the scheduler which options have been enabled and eventually send a warning to the user if one option is mandatory for this scheduler.
I'm thinking for example about the options --energy and --enable-compute-sharing which are not forwarded if I'm not mistaken.
Description
On a Simgrid platform where attributes "speed" and "core" are defined, Batsim does not forward them in the SIMULATION_BEGINS message.
How to reproduce
Platform used
Expected behavior
I should see
core
andspeed
fields in theproperties
field of the nodes, in the SIMULATION_BEGINS message.Current behavior
I do not have them :
Is this a bug or am I missing out on something?
The text was updated successfully, but these errors were encountered: