Database and Repository Installation (Advanced)

Overview

Before proceeding with this installation, it is highly recommended to read through the Render Farm Considerations documentation, including the AWS Thinkbox Deadline Shared Responsibility Model. It outlines what AWS Thinkbox is responsible for and what customers are responsible for, and should be considered before installing and using Deadline.

The Database is the global database component of the Deadline Render Farm Management System. It stores the jobs, settings, and Slave configurations. The Clients access the Database via a direct socket connection over the network. It only needs to be installed on one machine (preferably a server), and does not require a license. Deadline uses MongoDB for the Database.

The Repository is the global file system component of the Deadline Render Farm Management System. It stores the plugins, scripts, logs, and any auxiliary files (like scene files) that are submitted with the jobs. The Clients access the Repository via a shared network path. It only needs to be installed on one machine (preferably a server), and does not require a license.

The Database and Repository together act as a global system where all of Deadline’s data is stored. The Clients then connect to this system to submit, render, and monitor jobs. It is important to note that while the Database and Repository work together, they are still separate components, and therefore can be installed on separate machines if desired.

Note

The Repository installer requires an internet connection to download and install the MongoDB database. If your operating system isn’t supported, or if an internet connection isn’t available, you must manually install the database by following the Manual Database Installation documentation. When running the Repository installer, you can then choose the option to connect to an existing MongoDB database.

Installation

While the Repository can be installed on any operating system, the Repository installer is only available for Windows, Linux, and Mac OS X. However, the machine that you run the Repository installer on doesn’t have to be the same machine you’re installing the Repository to. For example, if you have an existing share on a FreeBSD server or a NAS system, you can run the Repository installer on Windows, Linux, or Mac OS X and choose that share as the install location.

To install the Repository, simply run the appropriate installer for your operating system and follow the steps. This procedure is identical for all operating systems. The Repository installer also supports silent installations.

setup directory

When choosing the Installation Directory, you can choose either a local path on the current machine, or the path to an existing network share. Note that if you choose a local path, you must ensure that path is shared on the network so that the Clients can access it.

Warning

Do NOT install over an existing installation unless it’s the same major version, or there could be unexpected results.

If you’re installing over an existing Repository installation, all previous binaries, plug-ins, and scripts will be backed up prior to being overwritten. After the installation is complete, you can find these backed up files in the Backup folder in the Repository installation root. Note that installing over an existing repository is only supported for repairing a damaged repository, or for performing a minor upgrade. Major upgrades require a fresh repository installation. See the Upgrading or Downgrading Deadline Documentation for more information.

After choosing the Repository Installation directory, you will be asked to install a new MongoDB Database, or connect to an existing one.

mongodb_setup

Installing a New MongoDB Database

If you choose to install a new MongoDB Database, you can then choose to have the installer download MongoDB for you. Note though that this requires an internet connection. Please ensure the MongoDB version is minimum 3.2.12 and maximum 3.2.18.

If you do not have an internet connection on the machine you’re running the installer on, your other choice is to simply download the MongoDB pre-packaged binaries from another machine with an internet connection. Just make sure to download the .tgz or .zip file for your operating system (and not the .msi file if you’re installing on a Windows machine). After downloading the MongoDB package, copy it to the machine you’re running the installer on, and then specify the path to it in the Repository installer.

Note

When specifying the path to the pre-packaged binaries, the Repository Installer is expecting a .tgz or .zip file that was downloaded from MongoDB’s website. It does not support binaries that were manually bundled.

mongodb_install_type

No matter your choice, you will then be asked to choose an installation location, a hostname and a port number.

Warning

Ensure you choose locally attached storage to install the Database. Do NOT install the DB to a NAS/network drive. Do NOT share out the DB directory once installed.

mongodb_settings

The MongoDB Hostname is the host name or the IP address of the machine that the MongoDB database will be running on. If desired, you can specify multiple entries and separate them with semicolons. There are a couple reasons to specify multiple entries:

  • You have machines on different subnets that need to access the database differently (ie: machines in the cloud might use a different host name than machines on the local network).
  • Some machines need to resolve the database machine by its host name, and others need to use its IP address.

Note that if there are IP addresses listed that cannot be resolved, the Deadline Command application can run slower on Linux and Mac OS X Clients because it won’t exit until the connection attempt for those IP addresses time out.

Next, you need to specify security options for the Database.

mongodb_security_settings

Although We strongly recommend enabling SSL/TLS authentication, you may choose to disable it by unchecking the Require client authentication via SSL/TLS checkbox. If it is enabled, you are presented with the following options:

  • Certificate Directory: The installer will generate the required certificates for authentication and place them in this directory. This is where you will find a client certificate that can be used to connect to the Database.
  • Certificate Password: You may associate a password with the client certificate. If you do, clients will require this password in order to connect to the Database. If you do not wish to set a password, leave this field blank.
  • Use client certificate for DB user authentication: If enabled, the client certificate will also be used for Database user authentication. The installer will create a user on the Database corresponding to the client certificate that is generated.

Note

Once the certificates have been generated, the ‘Deadline10Client.pfx’ file will need to be securely moved to client machines that are expected to connect to this Repository directly; it will be needed at connection time. In addition, the user(s) running the client processes will need to be granted Read access to the file (the installer creates the file with restrictive permissions).

Warning

It is important to be aware of who might have access to the file throughout the process of distributing it to the client machines – the operating system might change the access level of the file to be overly broad on a copy, for example. We recommend always maintaining each certificate with the minimal subset of permissions for the users that need to connect to the Deadline Repository.

When you press Next, the installer will install the database and try to connect to it and configure it for Deadline. This can take a minute or two. If an error occurs, you will be prompted with the error message. If the setup succeeds, you can then proceed with the installation of the Repository.

Connecting to an Existing MongoDB Database

Warning

Do NOT install over an existing installation unless it’s the same major version, or there could be unexpected results.

If you choose to connect to an existing MongoDB Database, you will be asked to specify the Database Settings so that the installer can connect to and configure the Database. Please ensure the MongoDB version is minimum 3.2.12 and maximum 3.2.18.

mongodb_connection_settings

These settings will also be used by the Clients to connect to the database. The following are required:

  • Database Server: The host name or the IP address of the machine that the MongoDB database is running on. If desired, you can specify multiple entries and separate them with semicolons.
  • Database Port: The port that the MongoDB database is listening on.
  • Database Name: The name of the Database. Make sure to enter the same name you used when you initially set up the Database. If you installed the Database using the Repository installer, it should be sufficient to leave it set to the default value.
  • Replica Set: If you set up your MongoDB database manually and it is part of a Replica Set, specify the Replica Set Name here. If you don’t have Replica Set, just leave this blank.

Next, you will be asked to provide security information for connecting to the Database.

mongodb_connection_ssl_settings

If the Database does not have SSL authentication enabled, uncheck the Use SSL/TLS when communicating with server option. Otherwise, provide the following options:

  • Client Certificate: This is the path to a client SSL certificate to use when connecting to the Database.
  • Certificate Password: This is the password for the Database SSL certificate. If the certificate does not require a password, leave this field blank.
  • Use client certificate for DB user authentication: Enable this if the client certificate is also used for Database user authentication. Note that a user corresponding to the client certificate must already exist on the Database.

When you press Next, the installer will try to connect to the database using these settings to configure it. This can take a minute or two. If an error occurs, you will be prompted with the error message. If the setup succeeds, you can then proceed with the installation of the Repository.

Command Line or Silent Installation

The Repository installer can be run in command line mode or unattended mode on each operating system. Note though that on Mac OS X, you must run the installbuilder.sh script that can be found in the Contents/MacOS folder, which is inside the Mac Repository Installer package.

To run in silent mode, pass the “–mode unattended” command line option to the installer. For example, on Windows:

DeadlineRepository-X.X.X.X-windows-installer.exe --mode unattended

To run in command line mode, pass the “–mode text” command line option to the installer. For example, on Linux:

./DeadlineRepository-X.X.X.X-linux-x64-installer.run --mode text

To get a list of all available command line options, pass the “–help” command line option to the installer. For example, on Mac OS X:

/DeadlineRepository-X.X.X.X-osx-installer.app/Contents/MacOS/installbuilder.sh --help

Note that there are a few Repository installer options that are only available from the command line, which you can view when running the “–help” command. These options include:

  • --help: Display the list of valid options.
  • --version: Display product information.
  • --unattendedmodeui <unattendedmodeui>: Unattended Mode UI. Default: none. Allowed: none minimal minimalWithDialogs.
  • --optionfile <optionfile>: Installation option file. Default: "".
  • --debuglevel <debuglevel>: Debug information level of verbosity. Default: 2. Allowed: 0 1 2 3 4.
  • --mode <mode>: Installation mode. Default: win32 (Windows), gtk (Linux) or osx (Mac OS X). Allowed: win32 unattended (Windows), gtk xwindow text unattended (Linux), or osx text unattended (Mac OS X).
  • --debugtrace <debugtrace>: Debug filename. Default: "".
  • --installer-language <installer-language>: Language selection. Default: en. Allowed: en.
  • --prefix <prefix>: The path to install the Repository to. Default: C:\Program Files\Thinkbox\DeadlineRepository<VERSION> (Windows), /opt/Thinkbox/DeadlineRepository<VERSION> (Linux) or /Applications/Thinkbox/DeadlineRepository<VERSION> (Mac OS X), where <VERSION> is: 10.
  • --backuprepo <backuprepo>: If set to true, many folders in the Repository will be backed up before overwriting them. Default: true.
  • --setpermissions <setpermissions>: If set to true, access rights will be set to 777 for the repository directory. Default: true.
  • --installmongodb <installmongodb>: This will install a new Mongodb instance. Default: None (must be specified in unattended mode). Allowed: true false.
  • --dbOverwrite <dbOverwrite>: Only applies if installing MongoDB. If true, any existing database will be over-written by the newly installed copy. Default: false.
  • --prepackagedDB <prepackagedDB>: Location of prepackaged MongoDB binaries (.tgz, .zip). If set, overrides dbInstallationType to prepackagedDB. Default: "".
  • --dbInstallationType <dbInstallationType>: Option doesn’t need to be used. Defaults to downloading the database. Specifying ‘prepackagedDB’ with an associated path will override this option. Default: downloadDB. Allowed: downloadDB prepackagedDB.
  • --mongodir <mongodir>: Only applies if installing MongoDB. This is the path MongoDB will be installed to. Default: C:\Program Files\Thinkbox\DeadlineDatabase<VERSION> (Windows), /opt/Thinkbox/DeadlineDatabase<VERSION> (Linux) or /Applications/Thinkbox/DeadlineDatabase<VERSION> (Mac OS X), where <VERSION> is: 10.
  • --backupdb <backupdb>: Only applies if installing MongoDB. If set to true, the data in the existing Database will be backed up before overwriting it. Default: true.
  • --dbListeningPort <dbListeningPort>: Only applies if installing MongoDB. The port on which the installer MongoDB server will listen for incoming connections. If connecting to an existing server, use <dbport> instead. Default: 27100.
  • --certgen_outdir <certgen_outdir>: Only applies if installing MongoDB. The output directory in which generated x509 certificates will be placed. Default: C:\Program Files\Thinkbox\DeadlineDatabase<VERSION>\certs (Windows), /opt/Thinkbox/DeadlineDatabase<VERSION>/certs (Linux) or /Applications/Thinkbox/DeadlineDatabase<VERSION>/certs (Mac OS X), where <VERSION> is: 10.
  • --certgen_password <certgen_password>: Only applies if installing MongoDB. Specifies a password to use when encrypting the Client Certificate. Leave blank to generate an un-encrypted private key (not recommended). Default: "".
  • --createX509dbuser <createX509dbuser>: Only applies if installing MongoDB. If this is enabled, the client certificate will be used as authorization for commands within MongoDB. This will enable authorization on the Database server. Default: true.
  • --requireSSL <requireSSL>: Only applies if installing MongoDB. If enabled, Deadline client connections will be authenticated via TLS/SSL. Certificates will be generated for this purpose and placed in <certgen_outdir>. Default: true.
  • --dbhost <dbhost>: The host name or IP address of the machine that MongoDB is running on. Default: "".
  • --dbport <dbport>: The port that MongoDB is listening on. Default: 27100.
  • --dbname <dbname>: The name of the MongoDB database that the data is stored in. Default: deadline[VERSION]db where [VERSION] is: 10.
  • --dbreplicaset <dbreplicaset>: The name of the MongoDB database replica set, if you have one set up. Default: "".
  • --dbuser <dbuser>: The user name to connect to MongoDB with. Default: "".
  • --dbpassword <dbpassword>: The password to connect to MongoDB with. Default: "".
  • --dbauth <dbauth>: If enabled, Deadline will use this account to connect to MongoDB. Default: false.
  • --dbsplit <dbsplit>: If enabled, the database collections will be split into separate databases to improve performance. Default: false.
  • --dbclientcert <dbclientcert>: If <dbssl> is true, this certificate will be presented when connecting to the server. Additionally, if <dbauth> is true, and <dbuser> is empty, this will also be used to authorize commands against the database. Default: "".
  • --dbcertpass <dbcertpass>: The password required to decrypt <dbclientcert>, if any. Leave blank if the certificate is un-encrypted. Default: "".
  • --dbssl <dbssl>: Use SSL/TLS when communicating with server. Default: false.

Note, where applicable (path contains spaces), it is recommended to encapsulate options in quotation marks, such as:

--prefix "C:\Program Files\Thinkbox\DeadlineRepository<VERSION>" --mongodir "C:\Program Files\Thinkbox\DeadlineDatabase<VERSION>"

where <VERSION> is the Deadline major version such as: 10.

Note

Please ensure any directory paths do NOT have any trailing slashes

Installation Logging

Our Repository installer creates an installation log in the system’s temporary directory. On Linux and Mac OS X, this typically means the /tmp directory. On Windows, the log will be created in the user’s local temp directory, usually C:\Documents and Settings\%USERNAME%\Local Settings\Temp. The default name of the generated log file is bitrock_installer.log, but if the file already exists from a previous installation, the installer will try to create an unique filename trying bitrock_installer_[pid].log and bitrock_installer_[pid]_[uid].log where [pid] is the PID of the process and [uid] is an unique identifier. On Linux, if the /tmp directory is not writable, it will attempt to use /var/tmp, /usr/tmp and ~/tmp instead.

Database Resource Limits

Linux and macOS systems impose a limit on the number of resources a process can use, and these limits can affect the number of open connections to the database. It is important to be aware of these limits, and make sure they are set appropriately to avoid unexpected behaviour. Note that MongoDB will allocate 80% of the system limit for connections, so if the system limit is 1024, the maximum number of connections will be 819.

If you choose a UNIX-based system to host the database, make sure the system limits are configured properly to avoid connection issues. See MongoDB’s UNIX ulimit Settings documentation for more information, as well as the recommended system limits to use.

You can check your current Linux/macOS resource limits in a terminal shell:

# Overall resource limits for current shell session and processes started by it (Linux/macOS)
>>> ulimit -a

# Overall resources limits system-wide (macOS)
>>> launchctl limit

MongoDB provides these Recommended ulimit Settings for optimal performance of your database. Note, you must restart the Deadline Database daemon after changing these ulimit settings.

Open File Descriptor Limits

If you choose to use a Linux or macOS system to host the database and you use the Repository installer to install it, MongoDB’s limits for the number of open files will be set to 64000 (for Linux) and 10000 (for macOS), the value recommended by MongoDB.

Linux

You can adjust this limit by editing the ULIMITSETTING value in /etc/init.d/Deadline10db after the Repository installer has finished. You will need to restart the MongoDB service for your changes to take effect.

macOS

You can adjust this limit by editing the HardResourceLimits and SoftResourceLimits values in /Library/LaunchDaemons/org.mongodb.mongod_Deadline10DatabaseService.plist after the Repository installer has finished. You will need to restart the MongoDB service for your changes to take effect.

Open Firewall Ports

To ensure that the Deadline applications can communicate with MongoDB, you will need to update the firewall on the machine that MongoDB is running on. You can either disable the firewall completely (assuming it operates in an internal network), or you can open the port that you chose for the database to use during install. More information on opening ports can be found below.

Windows

Open Windows Firewall with Advanced Security. Click on Inbound Rules in the left panel to view all inbout rules, and then right-click on Inbound Rules and select New Rule to start the Inbound Rule Wizard. Select Port for the Rule Type, and then click Next.

new_rule rule_type

On the Protocol and Ports page, choose TCP, and then specify the port that you chose for the database during the install, and then press next. Then on the Action page, choose Allow The Connection and press Next.

rule_port rule_allow

On the Profile page, choose the networks that this rule applies to, and then press next. Then on the Name page, specify a name for the rule (for example, MongoDB Connection), and then press Finish.

rule_network rule_name

Linux

On RedHat and CentOS, the following commands should allow incoming connections to the Mongo database if iptables are being used. Just make sure to specify the port that you chose for the database during the install.

>>> sudo iptables -I INPUT 1 -p tcp --dport [DB_PORT] -j ACCEPT
>>> sudo ip6tables -I INPUT 1 -p tcp --dport [DB_PORT] -j ACCEPT

where [DB_PORT] is the MongoDB port such as: 27100

Ubuntu has no firewall installed by default, and we have not yet tested Fedora Core’s FirewallD.

Mac OS X

Mac OS X has its firewall disabled by default, but if enabled, it is possible to open ports for specific applications. Open up System Preferences,, choose the Security & Privacy option, and click on the Firewall tab.

../_images/mac_firewall.png

Press the Firewall Options button to open the firewall options. Press the [+] button and choose the path to the mongod application, which can be found in the database installation folder in mongo/application/bin (for example, /Applications/Thinkbox/DeadlineDatabase<VERSION>/mongo/application/bin/mongod). Then click OK to save your settings.

../_images/mac_firewall_options.png

Sharing The Repository

For Deadline to operate properly, the Repository must be visible to all machines that are connecting to it. This section explains how to share your Repository folder and configure its permissions to ensure the Clients have necessary access.

The clients must have read access to the Repository root and all of its subdirectories. In addition, the Clients should have full read/write access to the following folders in the Repository:

  • jobs: This is where job auxiliary files are copied to during submission.
  • jobsArchived: This is where archived jobs are exported to.
  • reports: This is where the physical log files for job and Slave reports are saved to.

It is possible to achieve this by setting open read/write/execute permissions to the Repository root and all of its subfolders. While this is the easiest to configure, it does introduce some possible security risks. The following folders are especially sensitive because they contain Python scripts that will be executed on the render machines. We recommend that these folders be restricted to read/execute permissions only (no write access):

  • plugins: Contains Python scripts for the various render plugins supported by Deadline.
  • events: Contains Python scripts for event plugins.
  • scripts: Contains Python scripts that can be run from the Monitor.
  • custom: This directory can house additional plugins, events, and scripts.

It’s also worth noting that jobs often have additional auxiliary files submitted with them, which are normally stored in the jobs folder in the Repository, unless an alternate directory for auxiliary files is configured in the Repository Options. These auxiliary files can range from simple configuration files to scene files. Since these files may contain sensitive information, it is recommended to restrict write access to the jobs directory only to trusted users.

The guides below describe how to share the Repository with full read/write permissions.

Windows

Note

The images shown here are from Windows 10, but the steps are virtually identical for other versions of Windows.

Note

It is assumed that you are performing these instructions as a user with elevated permissions. On Windows, this is an administrator-type account that can execute commands as an administrator.

Note

For the purpose of this setup, we will create a local user account named deadlineuser. This user will be granted appropriate access to the Repository. Other non-elevated users shouldn’t be able to access the Repository.

First we will configure the appropriate Repository folder permissions.

  1. On the machine where the Repository is installed, navigate to the installation folder with the Windows Explorer.
  2. Right-click on the Repository folder, selecting Properties from the context menu.
  3. Select the Security tab and click Edit… to modify folder permissions.
../_images/windows_repository_initial_permissions.png
  1. Remove the Authenticated Users and Everyone groups. This can be done by selecting the corresponding entry from the Group or user names list and clicking the Remove button.

  2. Add deadlineuser with restricted access:
    1. Click the Add… button.
    2. Enter deadlineuser into the Enter the object names to select text field.
    ../_images/windows_select_users_or_groups.png
    1. Click OK.
    2. Select deadlineuser from the Group or user names list.
    3. Ensure deadlineuser only has permissions to allow Read, Read & execute, and List folder contents.
    ../_images/windows_repository_final_permissions.png
    1. Click OK to save the Repostiory folder permission settings.
  3. Add full access for deadlineuser to the Repository’s jobs/, jobsArchived/, and reports/ folders. After navigating into the Repository folder, the following steps should be completed for each of these folders.
    1. Right-click on the folder and select Properties from the context menu.
    2. Select the Security tab and click Edit… to modify folder permissions.
    3. Select deadlineuser from the Group or user names list.
    4. Ensure deadlineuser has permissions to allow Modify and Write.
    ../_images/windows_repository_full_control_permissions.png
    1. Click OK to save the folder permission settings. Complete these steps for the jobs/, jobsArchived/, and reports/ folders.

Attention

At this point, your Repository should only be accessible by deadlineuser (and admin users). The Repository folder (and all subfolders) should be able to be read and executed from by deadlineuser but not written to. Only the Repository subfolders jobs/, jobsArchived/, and reports/ should be able to be written to and modified.

Now we need to make sure the Repository folder is shared. Again, the images shown here are from Windows 10, but the steps are virtually identical for other versions of Windows.

  1. On the machine where the Repository is installed, navigate to the installation folder with the Windows Explorer.
  2. Right-click on the Repository folder, selecting Properties from the context menu.
  3. Select the Sharing tab.
../_images/windows_repository_sharing.png
  1. Click the Advanced Sharing… button.
  2. In the dialog, check the Share this folder checkbox.
../_images/windows_repository_sharing_advanced.png
  1. Click the Permissions button.
  2. Ensure Everyone has permissions to allow Full Control.
../_images/windows_repository_sharing_permissions.png
  1. Press OK to apply the permissions, then press OK again to share the Repository folder.
  2. Close the Repository folder Properties dialog.

Linux

Note

It is assumed that you are performing these instructions as a user with elevated permissions. On Linux, this is a user that can execute commands through sudo.

Note

For the purpose of this setup, we will create a user named deadlineuser. This user will be granted appropriate access to the Repository. Other non-elevated users shouldn’t be able to access the Repository.

First we will configure the appropriate Repository folder permissions.

  1. Change the owner of the Repository to be deadlineuser:

    >>> sudo chown -R deadlineuser:nogroup /path/to/repository
    

Note

Some distributions of Linux use nobody instead of nogroup.

  1. Add restricted access permissions to the Repository folder for the owner (deadlineuser is the owner at this point):

    >>> sudo chmod -R 500 /path/to/repository
    

Note

This sets permissions for all subfolders and files such that only the owner is able to read/execute. Other users won’t have access to the Repository folder.

  1. Add full access permissions for the owner (deadlineuser) to the Repository’s jobs/, jobsArchived/, and reports/ folders.

    >>> cd /path/to/repository
    >>> sudo chmod -R 700 jobs/ jobsArchived/ reports/
    

Attention

At this point, your Repository should only be accessible by deadlineuser (and admin users). The Repository folder (and all subfolders) should be able to be read and executed from by deadlineuser but not written to. Only the Repository subfolders jobs/, jobsArchived/, and reports/ should be able to be written to and modified.

Now you’re ready to set up your network sharing protocol. The recommended sharing protocol for Linux is Samba.

Note

You may not have Samba installed on your Linux machine. On Ubuntu, Samba can be installed with:

>>> sudo apt-get update
>>> sudo apt-get install samba

To share the Repository directory, modifications need to be made to /etc/samba/smb.conf. Add the following to the end of smb.conf:

[DeadlineRepository]
path = /path/to/repository
writeable = Yes
guest ok = No
create mask = 0700
force create mode = 0700
force directory mode = 0700
unix extensions = No

Once these modifications are saved, we need to setup a password for our Samba user (you will be prompted for the password):

>>> sudo smbpasswd -a deadlineuser

Now we can restart the Samba sharing service:

>>> sudo service smbd restart

On Linux clients, the Samba share can be mounted using cifs-utils:

>>> sudo mkdir /mnt/repo
>>> sudo mount -t cifs -o username=deadlineuser,password=<password> //<samba_server_address>/DeadlineRepository /mnt/repo

Note

<samba_server_address> must either be the IP address or hostname of the machine hosting the Samba share (likely the machine with the Repository installed).

Mac OS X

Note

The images shown here are from OS X El Capitan (10.11.4), but the steps are virtually identical for other versions of OS X.

Note

For the purpose of this setup, we will create a user named deadlineuser. This user will be granted appropriate access to the Repository. Other non-elevated users shouldn’t be able to access the Repository.

First we will configure the appropriate Repository folder permissions.

  1. On the machine where the Repository is installed, navigate to the installation folder with the Finder.

  2. Right-click on the Repository folder and select Get Info from the context menu.

  3. Expand the Sharing & Permissions section and unlock the settings (if necessary).

  4. Change permissions for the everyone group to No Access. This will prevent undesignated users from accessing the Repository.

  5. Make sure (this should already be the case) that the admin group has full Read & Write permissions.

  6. Add deadlineuser with restricted access:
    1. Click the “+” button at the bottom left of the dialog.
    2. Select deadlineuser from the Users & Groups tab.

    Note

    Users in this list appear as their “Full Name” rather than their actual username. This must be specified when the user is created.

    1. Make sure deadlineuser has Read only permissions.
../_images/osx_repository_initial_permissions.png
  1. Apply permissions to nested files and folders.
    1. Click the gear/cog dropdown button at the bottom left of the dialog.
    2. Select Apply to enclosed items….
  2. Add full access permissions for deadlineuser to the Repository’s jobs/, jobsArchived/, and reports/ folders. After navigating into the Repository folder, the following steps should be completed for each of these folders.
    1. Right-click on the folder and select Get Info from the context menu.
    2. Expand the Sharing & Permissions section and unlock the settings (if necessary).
    3. Change permissions for deadlineuser to Read & Write (should already be Read only).

If you prefer to set the permissions from the Terminal, run the following commands:

$ sudo chown -R root:admin /path/to/repository
$ sudo chmod -R 770 /path/to/repository
$ sudo chmod -R +a "deadlineuser allow list,readattr,readextattr,readsecurity" /path/to/repository
$ cd /path/to/repository
$ sudo chmod +a "deadlineuser allow list,add_file,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity" jobs/ jobsArchived/ reports/

Attention

At this point, your Repository should only be accessible by deadlineuser (and admin users). The Repository folder (and all subfolders) should be able to be read and executed from by deadlineuser but not written to. Only the Repository subfolders jobs/, jobsArchived/, and reports/ should be able to be written to and modified.

Now we need to make sure the Repository folder is shared.

  1. Open System Preferences and select the Sharing settings.
  2. Make sure the File Sharing checkbox is checked/enabled.
  3. Add the Repository folder to the Shared Folders list by clicking the “+” button beneath the list.
  4. Make sure that Everyone has full Read & Write access.
../_images/osx_repository_sharing.png

Note

It is recommended to use the Samba sharing protocol. This can be specified by clicking Options… and checking the Share file and folders using SMB checkbox.

Uninstallation

The Repository installer creates an uninstaller in the folder that you installed the Repository to. To uninstall the Repository, simply run the uninstaller and confirm that you want to proceed with the uninstallation.

../_images/uninstall_repo.png

Note that if you installed the Database with the Repository installer, it will be uninstalled as well. If you chose to connect to a Database that you manually installed, the Database will be unaffected.

Command Line or Silent Uninstallation

The Repository uninstaller can be run in command line mode or unattended mode on each operating system.

To run in command line mode, pass the “–mode text” command line option to the installer. For example, on Linux:

./uninstall --mode text

To run in silent mode, pass the “–mode unattended” command line option to the installer. For example, on Windows:

uninstall.exe --mode unattended

To get a list of all available command line options as a pop-up dialog, pass the “–help” command line option to the installer. For example, on Windows:

uninstall.exe --help

To get a list of all available command line options in the terminal, pass the “–help” command line option to the installer and an additional option when on Mac OS X:

./uninstall osx-intel --help

Note that there are a few Repository uninstall options that are only available from the command line, which you can view when running the “–help” command. These options include:

  • --help: Display the list of valid options.
  • --version: Display product information.
  • --debuglevel <debuglevel>: Debug information level of verbosity. Default: 2. Allowed: 0 1 2 3 4.
  • --mode <mode>: Installation mode. Default: win32 (Windows), gtk (Linux) or osx (Mac OS X). Allowed: win32 unattended (Windows), gtk xwindow text unattended (Linux), or osx text unattended (Mac OS X).
  • --debugtrace <debugtrace>: Debug filename. Default: "".
  • --installer-language <installer-language>: Language selection. Default: en. Allowed: en.

Uninstall Logging

Our Repository uninstall process creates an uninstall log in the system’s temporary directory with the same behaviour as the Repository Installation log.