Booking ahead
For the evening that is already known about: release testing every Tuesday and Thursday, or one late night next week. A booking is a keep-on arranged in advance. When the window opens, Delegaris does what Turn on until… would do at that moment, as you.
Making a booking
- On the Resources page, click the machine's name to open its details.
- Press Book ahead….
- Fill in the dialog:
| Field | What to do |
|---|---|
| How often | Once or Every week |
| Date | For a single booking, the day |
| Days | For a weekly booking, tick the days it repeats on (Mon to Sun) |
| From and Until | The hours. An end earlier than the start runs past midnight |
| Time zone | The clock those hours are on. It starts as your own, for example Europe/London; change it to a name such as America/New_York for a machine people use on another clock |
| What it is for | Optional. Kept with the keep-on in Activity and Reports |
- Press Book. A message confirms it, for example "Booked web-1: Every Tue and Thu, 18:00 to 22:00 (Europe/London)".
The machine's detail panel lists its bookings under Booked, with who made each and when the next one starts.
What happens when the window opens
At the start of each window Delegaris:
- starts the machine if it is off,
- takes its schedule tag off, so the scheduler leaves it alone, and
- at the end of the window puts the tag back, and stops the machine if its schedule would have it off then (or, where the schedule's hours are not known, stops it).
It does this as the person who booked, with their access as it is on the day. Access taken away in the meantime still counts, so a booking can stop working if someone's rules change.
Everything else about a keep-on applies: others can extend it, you can Change time, Stop it now or Put back on schedule once it is running, and Slack reminders arrive as usual.
Who can book
- Booking needs the keep-on right (Keep on, or turn on, for a set time) outright. Where keeping a machine on needs approval, it cannot be booked; ask on the day instead. The Book ahead… button does not appear.
- Protected machines can only be booked by administrators.
- A window can be no longer than the longest keep-on set under Settings > Schedules (24 hours unless changed). The dialog says what the limit is.
- Each person can have up to 50 bookings waiting at once.
The Bookings page
Bookings in the top bar lists your bookings that are still to run:
| Column | What it shows |
|---|---|
| Resource | The machine, and what the booking is for |
| When | For example "Every weekday, 18:00 to 22:00 (Europe/London)" |
| Next | When the next window opens |
| Last time | When it last ran and how it went, or "Not yet" |
Press Cancel to cancel a booking. Cancelling a booking does not end a keep-on it has already started; end that from the machine itself.
Administrators also see Yours and Everyone's at the top. Everyone's lists every booking, with a Booked by column, and administrators can cancel any of them.
A single booking disappears from the list once its window has passed. A weekly one stays until it is cancelled.
When a booking cannot run
- The machine cannot be started (no permission any more, keeping on now needs approval, or AWS refused): you are told in Slack, and the reason is shown under Last time on the Bookings page.
- Delegaris was not running when the window opened: if the window is still open when it starts again (with more than two minutes left), it runs for what is left. A window that has already closed is recorded as missed, not run late.
What is recorded
Making and cancelling a booking are recorded in Activity. Each run appears as a turn-on by the person who booked, with "booked" and the booking's number as its reason, and shows in the keep-on report like any other keep-on.