Skip to content

Commit

Permalink
Add extended reservation documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
val500 committed Dec 12, 2024
1 parent 508cf36 commit ad36f79
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/explanation/extended-reservation.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
Extended Reservation
============

Normal users can reserve a machine with Testflinger for a maximum of 6 hours.
However, for certain use cases this is limiting. Testflinger has the ability
to allow authorised clients to request longer reservation times. See the Reserve
section of the :doc:`Test Phase <../reference/test-phases>` documentation for more
information on how to set reservation times.
Using this feature requires :doc:`authenticating <./authentication>` with
Testflinger server.
1 change: 1 addition & 0 deletions docs/explanation/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,5 @@ This section covers conceptual questions about Testflinger.
queues
job-priority
restricted-queues
extended-reservation
authentication
1 change: 1 addition & 0 deletions docs/reference/test-phases.rst
Original file line number Diff line number Diff line change
Expand Up @@ -178,6 +178,7 @@ Variables in ``reserve_data``:

* ``ssh_keys``: The list of public SSH keys to use for reserving the device. Each line includes an identity provider name and your username on the provider's system. Testflinger uses the ``ssh-import-id`` command to import public SSH keys from trusted, online identity. Supported identities are Launchpad (``lp``) and GitHub (``gh``).
* ``timeout``: Reservation time in seconds. The default is one hour (3600), and you can request a reservation for up to 6 hours (21600).
Authenticated clients can request longer :doc:`reservation times <../explanation/extended-reservation>` with prior authorisation.

If either ``reserve_command`` is missing from the agent configuration, or the the ``reserve_data`` section is missing from the job, this phase will be skipped.

Expand Down

0 comments on commit ad36f79

Please sign in to comment.