Service-managed fleets

Service-managed fleets are fleets of workers that have default settings provided by Deadline Cloud. These default settings are designed to be efficient and cost-effective.

Some of the default settings limit the amount of time that workers and tasks can run. A worker can only run for seven days and a task can only run for five days. When the limit is reached, the task or worker stops. If this happens, you might lose work that worker or task was running. To avoid this, monitor your workers and tasks to ensure they don't exceed the maximum duration limits. To learn more about monitoring your workers, see Using the Deadline Cloud monitor.

Create a service-managed fleet

1. From the Deadline Cloud console, navigate to the farm you want to create the fleet in.

2. Select the Fleets tab.

3. Choose Create fleet.

4. Enter a Name for your fleet.

5. (Optional) Enter a Description. A clear description can help you quickly identify your fleet's purpose.

6. Select Service-managed fleet type.

7. Choose either the Spot or On-demand instance market option for your fleet. Spot instances are unreserved capacity that you can used at a discounted price, but may be interrupted by On-demand requests. On-demand instances are priced by the second, but have no long-term commitment, and will not be interrupted. By default, fleets use Spot instances.

8. (Optional) Set the maximum number of instances to scale the fleet so that capacity is available for the jobs in the queue. We recommend that you leave the minimum number of instances at 0 to ensure the fleet releases all instances when no jobs are queued.

9. For service access for your fleet, select an existing role or create a new role. A service role provides credentials to instances in the fleet, granting them permission to process jobs, and to users in the monitor so that they can read log information.

10. Choose Next.

11. Enter the minimum and maximum vCPU’s that you require for you fleet.

12. Enter the minimum and maximum memory that you require for you fleet.

13. (Optional) You can choose to allow or exclude specific instance types from your fleet to ensure only those instance types are used for this fleet.

14. (Optional) You can specify the size of the Amazon Elastic Block Store (Amazon EBS) gp3 volume that will be attached to the workers in this fleet. For more information, see the EBS user guide.

15. Choose Next.

16. (Optional) Define custom worker capabilities that define features of this fleet that can be combined with custom host capabilities specified on job submissions. One example is a particular license type if you plan to connect your fleet to your own license server.

17. Choose Next.

18. (Optional) To associate your fleet with a queue, select a queue from the dropdown. If the queue is set up with the default Conda queue environment, your fleet is automatically provided with packages that support partner DCC applications and renderers. For a list of provided packages, see Default Conda queue environment.

19. Choose Next.

20. (Optional) To add a tag to your fleet, choose Add new tag, and then enter the key and value for that tag.

21. Choose Next.

22. Review your fleet settings, and then choose Create fleet.