[Beaker-devel] API design for harness independent system reservations

Dan Callaghan dcallagh at redhat.com
Fri May 16 01:04:46 UTC 2014


Since this particular part of the feature (selecting when to reserve) is 
proving quite contentious I suggest that we start out implementing the 
simplest possible thing: if <reservesys/> is given, reserve 
unconditionally after all tasks are finished.

Or we could do the next simplest thing:

<reservesys/> reserve unconditionally
<reservesys onpass="false"/> reserve if there is any result besides Pass

This matches the current functionality of /distribution/reservesys with 
RESERVE_IF_FAIL=1.

-- 
Dan Callaghan <dcallagh at redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/beaker-devel/attachments/20140516/bc65a6d9/attachment.sig>


More information about the Beaker-devel mailing list