Skip to content

Publishing rendered products to AYON#9

Merged
antirotor merged 4 commits into
developfrom
feature/publishing
May 15, 2026
Merged

Publishing rendered products to AYON#9
antirotor merged 4 commits into
developfrom
feature/publishing

Conversation

@antirotor
Copy link
Copy Markdown
Member

@antirotor antirotor commented Apr 28, 2026

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 publishing
attr.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:

  • set DISABLE_CONDA_ENV on the publishing machine.
  • provided you are using your Queue environment similar to conda_queue_env_console_equivalent.yaml you can just add check for that variable and exit - put it somewhere after the check for empty Conda packages:
if [ -n $DISABLE_CONDA_ENV ]; then
    echo "disabling Conda environment."
    exit 0
fi
  • the job is passing AYON_BUNDLE variables 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.

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.
@antirotor antirotor self-assigned this Apr 28, 2026
@antirotor antirotor added the type: feature Adding something new and exciting to the product label Apr 28, 2026
@antirotor antirotor marked this pull request as draft April 28, 2026 12:04
implemented rudimentary publishing. Missing some key features (like handling color management, proper frame data, etc.)
@antirotor antirotor merged commit 0fa2d0d into develop May 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: feature Adding something new and exciting to the product

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant