Create a queue environment - AWS Deadline Cloud
Default Conda queue environment

Create a queue environment

A queue environment is a set of environment variables and commands that set up fleet workers. You can use queue environments to provide software applications, environment variables, and other resources to jobs in the queue.

When you create a queue, you have the option of creating a default Conda queue environment. This environment provides service-managed fleets access to packages for partner DCC applications and renderers. For more information, see Default Conda queue environment.

You can add queue environments using the console, or by editing the json or YAML template directly. This procedure describes how to create an environment with the console.

  1. To add a queue environment to a queue, navigate to the queue and select the Queue environments tab.

  2. Choose Actions, then Create new with form.

  3. Enter a name and description for the queue environment.

  4. Choose Add new environment variable, and then enter a name and value for each variable you add.

  5. (Optional) Enter a priority for the queue environment. The priority indicates the order that this queue environment will run on the worker. Higher priority queue environments will run first.

  6. Choose Create queue environment.

Default Conda queue environment

When you create a queue associated with a service-managed fleet, you have the option of adding a default queue environment that supports Conda to download and install packages in a virtual environment for your jobs.

If you use a customer-managed fleet, you must configure a queue environment that has the same behavior as the console Conda queue environment. For an example, see conda_queue_env_console_equivalent.yaml in the deadline-cloud-samples repository on GitHub.

Conda provides packages from channels. A channel is a location where packages are stored. Deadline Cloud provides a channel, deadline-cloud, that hosts Conda packages that support partner DCC applications and renderers. Select each tab below to view the available packages for Linux or Windows.

Linux

  • Blender

    • blender=3.6

    • blender-openjd

  • Houdini

    • houdini=19.5

    • houdini-openjd

  • Maya

    • maya=2024

    • maya-mtoa=2024.5.3

      We are investigating reports of stalled renders with MtoA version 2024.5.3. If you have tasks that have stalled without an error, contact support.

    • maya-openjd

  • Nuke

    • nuke=15

    • nuke-openjd

Windows

  • KeyShot

    • keyshot=2024.1

    • keyshot-openjd

When you submit a job to a queue with the default Conda environment, the environment adds two parameters to the job. These parameters specify the Conda packages and channels to use to configure the job's environment before tasks are processed. The parameters are:

  • CondaPackages – a space-separated list of package match specifications, such as blender=3.6 or numpy>1.22. The default is empty to skip creating a virtual environment.

  • CondaChannels – a space separated list of Conda channels such as deadline-cloud, conda-forge, or s3://amzn-s3-demo-bucket/conda/channel. The default is deadline-cloud, a channel available to service-managed fleets that provides partner DCC applications and renderers.

When you use an integrated submitter to send a job to Deadline Cloud from your DCC, the submitter populates the value of the CondaPackages parameter based on the DCC application and submitter. For example, if you are using Blender the CondaPackage parameter is set to blender=3.6.* blender-openjd=0.4.*.