Forums PDG/TOPs Tractor Scheduler Node Refreshed

Tractor Scheduler Node Refreshed

   2424   4   2
User Avatar
chrisgreb
Member
603 posts
Joined: Sept. 2016
Offline
 
We've recently made some major fixes and enhancements to the Tractor scheduler binding in PDG.

  • Cook is now submitted under one Tractor Job (each PDG work item becomes a Tractor Task)
  • TCP Port requirements for host are now gone.
  • UI and parm refreshed: The shared storage root and $HFS are now set on the scheduler node instead of needing to exist in the blade config.

Hopefully these changes make it easier to get started with Tractor. Any and all feedback is appreciated!

Attachments:
trnode.png (39.1 KB)

 Report
User Avatar
vochsel
Member
12 posts
Joined: April 2017
Offline
 
Hey, thanks so much for this.

We are running some tests and we've come into a need to specify the relay and xmlport ports due to our firewall restrictions. Is there a possibility to expose this in the Scheduler parms? We hardcoded the values in prtractor.py 

mq_cmd = '"__PDG_PYTHON__" "__PDG_SCRIPTDIR__/pdgmq.py" --xmlport 40002 --relayport 40001 --start'

and it worked.

Another thing that might be useful for new people is setting the default value of $HFS NFS path to 
$HFS
and the default value of Shared File Root Path NFS to 
$HIP

Another another thing is we noticed four frames appeared to fail in the PDG node output, but they actually rendered fine. This is possibly a more edge case problem. The log in Tractor was as follows: 
*** Starting:
/mnt/ala/software/ext_packages/houdini/17.5.278/install/bin/hython /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/pdgtemp/8465/scripts/rop.py -p /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/benandrewmattyay.hipnc -n /obj/topnet1/ropmantra1/ropnet1/mantra1 -to /obj/topnet1/ropmantra1 -i ropmantra1_ropfetch1_21_2 -fs 21 -fe 21 -fi 1
Error:       Unknown operator on load "stage.def".
             Unknown operator on load "stage.parm".
             Unknown operator on load "stage.userdata".
             Unknown operator on load "stage.datablocks".
             Unknown operator on load "stage.net".
Loading .hip file /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/benandrewmattyay.hipnc.
PDG_RESULT: ropmantra1_ropfetch1_21_2;-1;'__PDG_DIR__/render/benandrewmattyay.ropmantra1.0021.exr';file/image;0

Again, thanks so much for this change. Seeing them all under one job is great!

Thanks,
Ben
Edited by vochsel - June 6, 2019 21:38:07
 Report
User Avatar
protozoan
Member
1616 posts
Joined: March 2009
Online
 
chrisgreb
Any and all feedback is appreciated!

Thank you for putting the work into this! We will re-PDG-ify our Tractor within the next days.
Martin Winkler
money man at Alarmstart Germany
 Report
User Avatar
chrisgreb
Member
603 posts
Joined: Sept. 2016
Offline
 
vochsel
We are running some tests and we've come into a need to specify the relay and xmlport ports due to our firewall restrictions. Is there a possibility to expose this in the Scheduler parms? We hardcoded the values in prtractor.py

Makes sense, I will add those parms in the next build.
As for the error messages, they look to be due to missing operator definitions, which should not be fatal. The file was probably saved with Alpha content and then run on the farm without that enabled.
 Report
User Avatar
vochsel
Member
12 posts
Joined: April 2017
Offline
 
Awesome, thanks for adding those params!

Cheers for the direction with that error message. I'm going to put that one down to trying new things late on a Friday afternoon at work…
 Report
  • Quick Links