Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8810

Closed (moved)
(moved)
Open
Created May 02, 2013 by Andrea Shepard@andrea

We need a demonstration of alternate scheduling policy capability

Per my notes on the March 2013 dev meeting. promised to Karsten:

"Implement some example of an alternate scheduling policy by 2013-04-30"

Well, okay, one day late. This is just a mechanism to select circuitmux subclasses from the config file to override the default, and one example - an oldest queued cell selection policy.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking