1. 05 May, 2017 1 commit
  2. 19 Apr, 2017 1 commit
  3. 11 Apr, 2017 2 commits
  4. 10 Apr, 2017 1 commit
  5. 08 Apr, 2017 1 commit
  6. 07 Apr, 2017 10 commits
  7. 06 Apr, 2017 3 commits
  8. 12 Jan, 2017 2 commits
  9. 11 Jan, 2017 1 commit
  10. 10 Jan, 2017 1 commit
  11. 13 Sep, 2016 1 commit
  12. 07 Sep, 2016 1 commit
  13. 06 Sep, 2016 1 commit
    • Millian Poquet's avatar
      Pybatsim multiworkload support · b5263f33
      Millian Poquet authored
      Pybatsim should now be able to handle the new job_identifier syntax WLOAD!ID.
      Batsim now stores the number of simulated machines into Redis.
      Since the scheduler does not need to read the workload file anymore,
      this argument has been removed from pybatsim's launcher.py.
  14. 04 Aug, 2016 1 commit
    • Millian Poquet's avatar
      Major commit: multiple workloads. · 3ecccd22
      Millian Poquet authored
      This commit is a big step forward to handle multiple workloads at the same time.
      Protocol update. Jobs are no longer identified only by a unique number, but
      by a workload_name and a unique number within this workload_name. The separator
      between these two fields is '!'. The default workload, the one read from the
      input JSON file, is called "static". If the scheduler gives an order about
      a job by only calling it by its unique number, the 'static' workload is
      assumed, for compatibility reasons.
      Batsim code update. There is no longer "Jobs" and "Profiles" roaming in the
      BatsimContext. Now, Jobs and Profiles are grouped together inside one Workload
      instance. Different Workload instances can be stored into a Workloads (note
      the 's'!), which is just a map<string, Workload*> with wrapping methods
      to simplify job handling. A Workloads is instanciated in the BatsimContext.
      Batsim code update. Jobs are now identified by a structure JobIdentifier.
      This struct is just a string (the workload name) and an integer (the unique
      job number within its workload). JobIdentifier are used within most
      ipp messages now. Furthermore, jobs know in which workload they are,
      and Jobs know in which Workload they are.
      Batsim tests pass this commit, but a Redis server should be launched to
      avoid assertion fails. Redis is not yet used on the scheduler side,
      this part has not been tested yet. Travis has not been updated yet to
      install and execute Redis, so the tests won't work on Travis at the moment.
  15. 09 May, 2016 1 commit
  16. 04 May, 2016 1 commit
  17. 29 Mar, 2016 1 commit
  18. 26 Jan, 2016 1 commit
    • Millian Poquet's avatar
      Machine: ranges are now used instead of sets. · 4567c6dd
      Millian Poquet authored
      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).
  19. 11 Jan, 2016 1 commit
  20. 19 Dec, 2015 1 commit