Deadline Docker Container

Andrew_Graham · April 4, 2021, 1:58am

Thanks Bobo, I will try and update as soon as I can. I’ve been trying to generate immutable AMI’s with deadline, in the eventual transition to docker, but for now I just want to build immutable AMI’s before that will be possible. This is proving to be tricky!

The installers must be performed first, without certificates, during the AMI build. Then on boot, via user data we have to generate the certs and configure the DB to use them. I am going to just focus on the DB for now, before I will tackle RCS and rendernodes. I’m working this out with a single bash script that splits installation and certificate generation until I’m convinced it works.

I cannot get deadline to work if I generate certs after the install though. I’ve got two automated install scripts here that install the DB and RCS that I’ve produced in the hope that Thinkbox will see the problem in a diff between them.

This script on ubuntu 18 works.

github.com

firehawkvfx/packer-firehawk-amis/blob/deca865cbff0e8dfe053ce49855a608d000ce434/modules/firehawk-ami/scripts/deadlinedb_install_with_certs.sh

#!/bin/bash

# This installs certificates with the DB.

set -e
pwd=$(pwd)
SCRIPTDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )" # The directory of this script

# User vars
cert_org="Firehawk VFX"
cert_ou="CG"
installers_bucket="software.dev.firehawkvfx.com"
deadlineuser_name="ubuntu"
deadline_version="10.1.9.2"
mongo_url="https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1604-3.6.19.tgz"
dbport="27100"
host_name="deadlinedb.service.consul"
deadline_client_certificate="Deadline10Client.pfx"
deadline_proxy_certificate="Deadline10RemoteClient.pfx"

This file has been truncated. show original

This version which installs certs seperate to the DB does work initially, but on reboot, any db queries will fail.

github.com

firehawkvfx/packer-firehawk-amis/blob/deca865cbff0e8dfe053ce49855a608d000ce434/modules/firehawk-ami/scripts/deadlinedb_install_post_gen_certs.sh

#!/bin/bash

# This tests generation of certs post install of the DB.

set -e
pwd=$(pwd)
SCRIPTDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )" # The directory of this script

# User vars
cert_org="Firehawk VFX"
cert_ou="CG"
installers_bucket="software.dev.firehawkvfx.com"
deadlineuser_name="ubuntu"
deadline_version="10.1.9.2"
mongo_url="https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1604-3.6.19.tgz"
dbport="27100"
host_name="deadlinedb.service.consul"
deadline_client_certificate="Deadline10Client.pfx"
deadline_proxy_certificate="Deadline10RemoteClient.pfx"

This file has been truncated. show original

I try to validate with a query after reboot and get this error:

 /opt/Thinkbox/DeadlineDatabase10/mongo/application/bin/deadline_mongo --eval 'printjson(db.getCollectionNames())'
MongoDB shell version v3.6.19
connecting to: mongodb://deadlinedb.service.consul:27100/deadline10db?gssapiServiceName=mongodb
2021-04-03T11:51:33.165+0000 E QUERY    [thread1] Error: network error while attempting to run command 'isMaster' on host 'deadlinedb.service.consul:27100'  :
connect@src/mongo/shell/mongo.js:263:13
@(connect):1:6
exception: connect failed

One thing I am suspicious of, is the importance of mongo_client.pem and how is it made? it is different to the standard localhost.pem?

Andrew_Graham · April 4, 2021, 4:27am

I’ve updated the example scripts from that repo with tag v0.0.2.

I realised there we some lines in the config not being added. I’ve also removed the password from the functioning installer.

Theres really not much between those two files. I suspect it must have something to do with mongo_client.pem not being produced correctly.