This is also stored as an item on our github issue database:
https://github.com/autotest/autotest/issues/644
Disclaimer: I'm by no means a specialist in the fine art of writing user
stories, just thought I'd write how I envision this functionality to
work. My final goal is to have also more fine grained control over
machine selection (hardware capabilities), but as we did not implement
advanced scheduling yet, I won't include that in the couple of user
stories I wrote.
1) Kayla is a Software Engineer working for FooCorp. She needs a RHEL
5.8 box for a couple of days to reproduce a problem found by a customer
in one of FooCorp's products.
She wants to go to the hosts list, select one host, and tell that this
host has to be provisioned with RHEL 5.8, and that she'll use it for 48
hours.
She then presses 'Reserve' and after 20 minutes, gets an email telling
that her request was fullfilled and she's supposed to use the machine
from now (May 15th, 2003, 15:00 GMT) to (May 17th, 2013, 15:00 GMT),
with login information, and with her SSH public key (that she already
registered at the autotest server on her profile page) already installed
in the box, so she can log in there without having to use a password.
An email comes out 2 hours before the reservation is about to end,
telling her that, and once the time has passed, the machine becomes
available for new test jobs immediately.
2) Rob is a Test Automation Engineer working for BarCorp. He needs a box
so he can verify whether his cgroup test suite is working properly on
the linus's tree, head of the master branch.
He wants to use the command line to select one host, and tell that this
host has to run a kernel compiled from linus's git repo, master branch,
and that he is going to use it for an indeterminate amount of time.
He then presses 'Reserve' and after 20 minutes, gets an emaill telling
that his request was fullfilled and he has a reservation on that system
from now (May 15th, 2003, 15:00 GMT) and doesn't have an end time
specified, with login information (user and password, since he didn't
register an SSH key at the autotest server). The email states that is a
bad practice to specify indefinite amounts of time, since he might
forget to release the system, so it can be used efficiently among his
peers, and that he has to explicitly go to the web interface (hosts
tab), and select to 'release' the system, after which the machine
becomes available to run jobs again.
So, what do you think?
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
