Publishing rendered products to AYON#9
Merged
Merged
Conversation
Add roles to HostRequirements to handle publishing on specific machines
Publish step and HostRequirements added, missing functions to initiate the publishing and collector for the rendered outputs.
implemented rudimentary publishing. Missing some key features (like handling color management, proper frame data, etc.)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Description
This PR is adding functionality to publish rendered outputs to AYON.
Additional review information
This is adding publishing as a step to the job. Currently, it expects AYON to be available on the machine that will process the job (in
PATH) but there is already ongoing effort to pack AYON Launcher as a Conda/Rez package that could be made available to the cloud worker machine. At that point (provided machine has network access to AYON server), the publishing can be done even on cloud.But for now, the expected setup is to have machine with AYON Launcher set and able to connect to target AYON server. To do this and still use cloud machines for rendering, you need to set up two fleets - SMF (Service Managed Fleet) and CMF (Customer Managed Fleet) - SMF will serve for the rendering and CMF for publishing. For more info, see the discussion in related issue #8
To set it up, you need to specify currect
hostRequirements- on Deadline Cloud side, you need to add either to the whole fleet or specific machine required role;attr.role = publish- for machines that can do the publishingattr.role = render- for those that can render.Note: you can define names of the roles in AYON addon settings.
With this setup, you can handle machines that are suitable only for publishing, those that should only render and those that can do both.
If the publishing machine cannot work with Conda - it is crashing on Conda setup, you can do the following trick:
DISABLE_CONDA_ENVon the publishing machine.AYON_BUNDLEvariables but not API keys or access credentials - you need to set that on the machine itself. Later on, we can use AWS Credential Manager for that.