Bug 1324982

Summary:	[RFE] limit system reservation and extend times to some maximum time based on policy settings
Product:	[Retired] Beaker	Reporter:	drohwer
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	mjia
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:13:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description drohwer 2016-04-07 18:42:24 UTC

Description of problem:

We are looking for the ability to limit the system reservation and extend times to maximum of X number of days for each based on an Access Policy setting.  The initial system reserve would be up to X days with a X days extension. 

So for example we would have an Access Policy setting for resources set to something like:
   - Initial System reservation time = 2 days maximum
   - Extend System time = 2 additional days maximum
so that the resource could only be used for a maximum time of 4 days given the scenario above as an example.

This would allow us to have a pool/set of machines in certain policy configurations that would only be tied up for a maximum of 4 days therefore allowing all users to use the systems but not abuse them by continually extending time.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 jiazhan 2016-06-13 05:57:57 UTC

Hi bkr dev team:
This is Kevin Zhang from CEE, I think drohwer's RFE is quite necessary and that's an issue that we got feedback from CEE users that the current max reserve days of 7 is not enough for normal case , can we extend it to a range of 1-20 days. as I mentioned on item 1 in  the mail to beaker user list. cee users think that's quite necessary and save their time on manually requesting loaning or extend time on the box.

Comment 2 jiazhan 2016-06-13 06:23:38 UTC

 at present, user can use extendtesttime.sh to reserve the box without time limit if they use it with cron job
can we make updates on beaker to set a time limit that user can use the extendtesttime.sh to extend the reserve?

Comment 3 Roman Joost 2016-10-25 04:40:27 UTC

I'm moving this item back to Triaged, since we can't work on it before we haven't written up a design proposal, discussed it and hashed out a solution.