Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • batsim batsim
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

La mise à jour du service Gitlab est terminée. Merci aux collègues du service de production de la DSI qui ont réalisé cette opération qui outre les aspects évolution du logiciel nous a permis de faire le nécessaire face à des failles de sécurité.
Les principales releases notes concernant cette montée de version sont disponibles ici :
https://about.gitlab.com/releases/2023/01/22/gitlab-15-8-released/
https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/
https://about.gitlab.com/releases/2022/11/22/gitlab-15-6-released/

  • batsim
  • batsimbatsim
  • Issues
  • #67
Closed
Open
Issue created Apr 26, 2018 by MERCIER Michael@mmercierOwner

Simplify the Batsim protocol

Currently some message of the batsim protocol have optional fields:

  1. SUBMIT_JOB allows the scheduler to give a optional profile which is redundant with the SUBMIT_PROFILE message. Maybe just removing the optional profile is enough

  2. JOB_SUBMITTED have 3 different ways to give information to the scheduler.

Also, I already reach the limitation of forwarding information in the message for the JOB_KILLED message: The progress given for composed profile is quite simple if the scheduler knows the profiles, but if it does not the code of Batsim to manage this become more and more complex.

So, I suggest to use the SIMULATION_BEGINS message to give a maximum of information (It already does that with the config, the resources, the workloads and I just added the profiles. Now we can add the jobs so we can simplify the JOB_SUBMITTED message.

It implies to store these information in the scheduler from the beginning so the memory consumption would be higher of course. But I think that we kept redis exactly for this purpose: when we reach scaling limitation.

Edited Aug 31, 2018 by Millian Poquet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking