[Beaker-devel] First draft of reservations design proposal

Nick Coghlan ncoghlan at redhat.com
Fri Sep 27 01:22:24 UTC 2013


On 09/27/2013 09:04 AM, Dan Callaghan wrote:
> Excerpts from Nick Coghlan's message of 2013-09-26 18:47:05 +1000:
>> A similar time limiting mechanism is proposed for system loans, as 
>> well as
>> the ability to indicate when reserving a system in Manual mode that the
>> loan should be returned automatically when the reservation is returned.
> 
> For Manual systems, loans and reservations seem redundant with each 
> other. Can we just get rid of one or the other?

I did consider that, but the nice thing about having them separate is
that when a system is loaned to you, you can flip it back and forth
between Automated and Manual without breaking anything. I could see
there being an *implied* reservation associated with a loan, though, so
whenever a loaned system is in Manual mode, a reservation is
automatically created for the loanee (which is automatically returned if
the system is placed in Automated mode).

That reminds me though - should we look into adding the "system=fqdn"
attribute for hostRequires in 0.16? That's the idea [1] to allow a
recipe to be scheduled on a system regardless of its current condition:

    <hostRequires system="thesystem.example.com"/>

When the requirement is set that way, Beaker would only filter out
currently reserved systems and systems the user isn't permitted to
reserve, rather than all the other filtering it does (further suggesting
that it's worth keeping loans and reservations separate, even in the
Manual case).

Cheers,
Nick.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=790492#c10

Cheers,
Nick.

-- 
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane

Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)


More information about the Beaker-devel mailing list