-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Houdini PDG Afanasy Scheduler #514
Comments
Here is the first commit. It uses dynamic method. On work item schedule a new block/task will be appended to an existing job. Each TOP node work items are joined in a block. In feature we should have an ability to setup TOP node Afanasy task parameters via block parameters (capacity, service, parser and so on). Also it helps to visualize job structure in GUIs. For now "control" job is just an empty task - an opened Houdini scene is needed with a running graph. |
There is a lots of work to do. |
…n each cook start. Before it, sheduler worked just once, than Houdini restart was needed. Comments added on virual functions (callbacks) References #514.
Would it perhaps be an idea to create the scheduler 100% using python and replace the .hda? This way it's easier to subclass it to make customizations. |
If it is possible, it will be better. |
Now a new Afanasy job will be created on the first item onSchedule. Job, block and task creation are in separate functions. References #514.
Yes, look at the other schedulers. In the |
It seems that layout is not supported by |
Hmmm.. I will try and see if something can be done through "on creation" callbacks.. |
References: #514. (documentation just started - header added)
"Submit Job As Graph" sends a job with 1 block and 1 task to cook TOP network. |
On farm artist machine can be not reachable by name. References: #514.
By default, workItemResultServerAddr() returns local host name and port. But on our farm, artist machine is not reachable by name, only by IP. The solution to find a local IP address is used from: May be better to create an option (checkbox) for this on the scheduler node. |
Now you can specify graph job capacity and hosts mask to run it on some slow machine, or run it on the same host and at the same time with work items tasks. References #514.
This can help to assign cook job on a special host(s) and use a special ticket (licence). References #514.
Default service is hbatch and parser is mantra. If it is a ropfetch with mantra, service is hbatch_mantra. If it is an ffmpegencodevideo service and parser is ffmpeg. That is all checks for now. This function will be improved in feature. References #514.
This is a default parameter on scheduler nodes. And it behaves as on other schedulers. References: #514.
Report work item fail on error. Block on failed work items. Use IP address as working item result server. Tick Period and Max Items Per Tick. References: #514.
Scheduler node screenshot for documentation added. References: #514.
Task environment variables are passed to parser. References: #514.
Hi everybody!
This issue is created to discuss PDG Afanasy scheduler implementation.
Since the implementation scheduler is started, I decided to create a new issue for more concrete discussion.
The text was updated successfully, but these errors were encountered: