Package Name

Topic

What should this package be called?

Current Resolution

• The message handling package is called rocon_scheduler_requests.

Discussion Thread

• (Jack) Come up with a shorter name than scheduler_request_manager. I am considering scheduler_requests, but am open to other suggestions.

• (Daniel) I'm not too worried what it is for now. We were temporarily just using concert_scheduler in the quick hack we have in now. I typically prefix the centralised concert specific packages with concert_ (e.g. concert_master, concert_service_manager, concert_roles ...) and others with rocon (e.g. rocon_gateway, rocon_hub, rocon_app_manager).

  • (Jack) I am fine with renaming the message handling component something like concert_scheduler_requests or concert_resource_requests if that fits in better.

  • (Jack) Since we envision multiple scheduler implementations, they will need separate names. I was planning to write one called concert_simple_scheduler that just grants requests on a first-come-first-served basis. I suspect that will be adequate for many applications.

• (Daniel) I keep thinking and talking about this more like a resource allocator rather than a scheduler. What's the background for thinking of it like a scheduler?

  • (Jack) The problem appears to be isomorphic with traditional operating system schedulers, especially the early batch systems which had to assign non-preemptable resources like printers and tape drives. The scheduler needed to find an allocation plan to maximize throughput for multiple requesters. It is a resource allocator, but due to contention it is also a planner.

  • (Daniel) I love these tidbits. It would be great to have this 'flavour' with a few links describing it on the readme or in the sphinx generated documentation.

  • (Jack) docs and README updated