JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-115  -  Node provisioning facility
Posted Jan 11, 2013 - updated Mar 02, 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
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Samples
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1
Issue description
The idea is to provide a sample that illustrates how the JPPF grid topology can be dynamically adjusted based on user-defined criteria. This could be done via a combination of:
  • node activation / deactivation
  • adjusting the nodes thread pool size selectively
  • using the driver-based node management features (JPPFNodeForwardingMBean)



#4
Comment posted by
 lolo4j
Feb 11, 08:52
trunk revision 3039
#7
Comment posted by
 lolo4j
Feb 13, 07:52
After thinking about it for a while, I believe the node provisioning feature introduced in the sample is in fact a major and very useful JPPF feature, which should be provided and documented as such. I am thus reopening this issue.

The work that should be done:
  • put the sample's code into the node code base
  • add isSlave() and isMaster() to the node's interface (org.jppf.node.Node or a sub-interface) so this can be used in the extensions such as NodeLifeCycleListener, based on "jppf.node.master = true|false" and "jppf.node.slave = true|false" properties in the configuration
  • implement Feature request JPPF-214 - Ability to redirect std and err output for nodes and drivers, to be used by the slave nodes
  • enable turning provisioning on or off via JMX, including in the admin console, and add a column "standard|master|slave" in the console's topology view to indicate the type of node
  • add a "provisioning" view in the admin console to display a hierarchy driver/master/slaves, with GUI actions for doing the provisioning operations (with an editor for configuration overrides)
  • offline nodes cannot be master nodes
  • document accordingly
#9
Comment posted by
 lolo4j
Feb 22, 11:16
implemented in: