Opened 5 years ago

Last modified 19 months ago

#2673 assigned task

unify scheduler endpoints

Reported by: dustin Owned by:
Priority: major Milestone: 0.9.5
Version: Keywords: schedulers
Cc:

Description

We currently have both /schedulers and /forceschedulers endpoints. Those should be collapsed into one type, with a type field added to that type so that the UI can single out force schedulers for extra attention.

Change History (13)

comment:1 Changed 4 years ago by dustin

  • Owner set to dustin
  • Status changed from new to assigned

comment:2 Changed 4 years ago by dustin

So, the forcescheduler endpoint looks to the local host configuration for information about the scheduler, including the list of builders and the field specs. That won't work in a multi-master context, if the scheduler is not configured on the webhead.

So I think the first step here is to expand the schedulers table to include both of these pieces of information. Since schedulers only run on one host at a time, they can simply update this data when they become active.

With this in place, the queries become trivial. The control method will still require that the scheduler be configured locally, but fixing that is another bug.

comment:3 Changed 4 years ago by dustin

The builder names should be encoded as a many-to-many table, with a new builders endpoint just for fun.

The field set should probably be encoded as a generic 'configuration' metadata field, so that other schedulers can provide other kinds of information. Then the frontend for force schedulers can just filter schedulers with a 'force_fields' configuration value.

comment:4 Changed 4 years ago by dustin

  • Owner dustin deleted

comment:5 Changed 4 years ago by dustin

  • Summary changed from [nine] Two endpoints for schedulers? to Two endpoints for schedulers?

comment:6 Changed 4 years ago by dustin

  • Summary changed from Two endpoints for schedulers? to unify scheduler endpoints

comment:7 Changed 3 years ago by dustin

I'd like to fix this before 0.9.0 is released, otherwise we'll need to keep backward-compatibility for /forceschedulers

comment:8 Changed 3 years ago by dustin

  • Milestone changed from 0.9.0 to 0.9.1

Or we can just break that compatibility. We'll decide later :)

comment:9 Changed 2 years ago by tardyp

updated the raml to mark forcescheduler as "soon" deprecated

comment:10 Changed 22 months ago by tardyp

  • Milestone changed from 0.9.1 to 0.9.2

Ticket retargeted after milestone closed

comment:11 Changed 20 months ago by tardyp

  • Milestone changed from 0.9.2 to 0.9.3

Ticket retargeted after milestone closed

comment:12 Changed 19 months ago by tardyp

  • Milestone changed from 0.9.3 to 0.9.4

Ticket retargeted after milestone closed

comment:13 Changed 19 months ago by tardyp

  • Milestone changed from 0.9.4 to 0.9.5

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.