JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
OPEN  Feature request JPPF-371  -  New sample to upgrade Windows nodes to .Net-capable status
Posted Feb 19, 2015 - updated Sep 25, 2017
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
lolo4j (lolocohen) has been working on this issue since February 19, 2015 (09:38)
Issue details
  • Type of issue
    Feature request
  • Status
     
    New
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Samples
  • Resolution
    Not determined
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF Vision
Issue description
We propose to create a new sample/demo which will upgrade any node running on a Windows machine such that, after the upgrade, they can execute .Net jobs and tasks.

What needs to be done:
  • use an execution policy to select Windows nodes and filter out those who are already .Net capable. The policy should be stored as an XML file that users can easily modify
  • use a broadcast job using this policy, to execute a Java task on the nodes to upgrade
  • the job would use a data provider whcih stores all the files that must be added: dlls, jar files and addtional config files
  • the task would use this data provider to store the files at the proper location in the node's distribution, modify the existing config file, and finally perform a deferred restart of the node
  • the task would also send JMX notifications of the upgrade status (at least start/end, with successfull completion or failure status)