[size=150]AWS Confidential Beta Material[/size]
This is the second beta for Deadline 10. Please visit the link below to access the setup documentation and installers:
thinkboxsoftware.box.com/s/847j … by6wx29zes
First, download Deadline.AWSBeta2.zip, and unzip it. This package contains 3 files:
- DAWS Beta Rundown.docx: This is the main document for setting up Deadline 10 and Deadline.AWS. START HERE!
- DAWSPermissions.json: This is the basic policy with all the permissions required to use Deadline.AWS, which is referenced in the DAWS Beta Rundown document.
- Installing Cloud Link.docx: This is the installation documentation for the Cloud Link component, which is referenced in the DAWS Beta Rundown document.
Second, during the setup process, you will be required to install the Deadline 10 Repository and Client, as well as the Cloud Link component. So download the installers for the appropriate operating system(s).
At this point, you should have everything you need to start using Deadline 10 and Deadline.AWS.
If you have feedback on the setup process or anything in general, let us know on the Discussion Forum.
Bugs can reported in the Bug Reports Forum.
What’s New in Deadline 10.0.0.14 (Beta 2)
Choose Your Instance Type
When starting a Fleet, there is now the option to use the default instance types or to use a custom set. If the custom set option is selected, a full list of instances types are shown, and you can choose one or more instance types to use.
Instance Tagging
The Deadline infrastructure and Fleet render nodes in AWS will now have appropriate
DeadlineRole tag assigned to them. The infrastructure instances will be tagged with DeadlineInfrastructure and the render nodes will be tagged with DeadlineRenderNode.
Easier Proxy Server Setup
Part of the setup process is installing and running the Deadline Proxy Server on one of your on-premise machines. This required you to manually run the Deadline Proxy Server from the command line, and on Windows, you needed to add a namespace reservation. The Deadline Client installer now has a new “Deadline Remote Connection Setup” component, which is optional. If enabled, a menu item for the Proxy Server will be added to the Launcher menu, and the namespace reservation will be added automatically on Windows.
Remote Connection Server
The Remote Connection Server is a new Deadline application that is meant to be a drop-in replacement for the DeadlineProxyServer application. At any point during the setup process where the Deadline Proxy Server is referenced, you can choose to use the Remote Connection Server instead. The only difference at this time is that the AWS render nodes will dequeue jobs faster using the Remote Connection Server. Additional performance improvements will be made, and as a result the Proxy Server will eventually be phased out. So we encourage you to use the new Remote Connection Server!
General Deadline.AWS Panel Improvements
- Removed the Graph buttons from the Deadline.AWS panel, since the lists in this panel do not have any graphs associated with them yet.
- Infrastructures that don’t make it through the creation process can now be deleted from the Infrastructure list.
- The [+] button for starting Infrastructure now only appears in Super User Mode, or if the current user has permissions to use this feature.
Please note that the installers for version 10.0.0.14 have been pulled due to a critical error with the Proxy Server/Remote Connection Server. This bug prevented Deadline from acquiring DAWS settings and infrastructures from a remote connection. This issue has been addressed in version 10.0.0.15, and the new installers can be downloaded via the link provided for version 10.0.0.14.
If you have already installed version 10.0.0.14, please update.