JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-295  -  Execution policies should have access to job and grid information
Posted Jul 25, 2014 - updated Aug 14, 2014
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Core
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
Scripted execution policies can access the following information, set a predefined script variables:
  • server-side SLA of the job being evaluated
  • client-side SLA of the job being evaluated (client-side only)
  • metadata of the job being evaluated
  • number of channels to which the job is already dispatched (i.e. nodes on the server side, client connections on the client side)
  • server statistics (server side only)
We propose to make this information available to any type of execution policy

#2
Comment posted by
lolo4j
Jul 25, 20:07
Execution policies are currently represented as a tree, where each node is a subclass of ExecutionPolicy. What's missing is the ability to navigate upwards in the tree, thus we need to add a parent attribute. This way, the additional job and grid parameters need only be set onto the root of the tree, and access requests can be easily propagated to the root. This also means the existing code must take care of setting the parent for the relevant policies that have children (OrRule, AndRule, XorRule, NotRule, Preference).
#3
Comment posted by
lolo4j
Aug 14, 06:40
implemented in trunk revision 3321