History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3619
Type: Improvement Improvement
Status: Open Open
Priority: Trivial Trivial
Assignee: Robin Shen
Reporter: U. Artie Eoff
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Resource depends on another resource can "use" dependency resource

Created: 16/Sep/20 02:15 AM   Updated: 16/Sep/20 02:15 AM
Component/s: None
Affects Version/s: 9.0.47
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
Currently we can create a resource with "Nodes matching all specified criterias" -> ("Node matches another resource" and "All nodes with specified attribute value"). But when we "use" this resource, the matched resource in the criteria does not get marked as "used"... only the current resource is marked as "used".

We would like to create a resource that "matches another resource" with additional criteria but also "uses" the matched resource.

For example, we have agents that can only run QUICK_TEST jobs and agents that can run both QUICK_TEST and LONG_TEST jobs. For QUICK_TEST job configurations we select agent with resource QUICK_TEST. For LONG_TEST jobs configurations we select agent with resource LONG_TEST. However, when an agent is running a LONG_TEST job, we don't want it to run a QUICK_TEST job.

Our current workaround is to only define a "TEST" resource, then in a LONG_TEST-based configuration we select agent with TEST resource plus LONG "attribute value".

Hope this makes sense. Let me know if you need better explanation.

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.