Versions Compared

    Key

    • This line was added.
    • This line was removed.
    • Formatting was changed.
    Comment: Published by Scroll Versions from this space and version 7.5-0
    Info

    If both of the following conditions are true, you will need to take the extra steps outlined in Transferring data from MySQL to PostgreSQL when upgrading the supervisor:

    • You are upgrading the supervisor from pre-7.0 to Qube 7 (for example from 6.10-0a to 7.0-0)

    • You wish to bring your Qube 6 job data forward into Qube 7

     

    It is generally easier and quicker to use the new Qube! Installer for all installs and upgrades. However, if you have a requirement for manual installs, you can follow these steps. For all of the software components, you will need to log in as an Administrator account (Windows), log in as root or use sudo (Linux) or know the Administrator password (OS XmacOS).

    You should install the Supervisor first, and then any Workers and/or Clients. It is better to have the Supervisor waiting for Workers to show up, than the other way around.

    Contents

    Python

    This

    On a new macOS 10.15 system, you will need to open a terminal, and type "python3" and hit enter. That will run a "stub" script and allow you to download and install python3.

    Table of Content Zone
    locationtop

    Prerequisites

    Linux

    Linux requires the following be installed on the Supervisor and Worker machines

    The supervisor requires the following packages to be present:

    • mysqlpython3
    • mysql-server
    • xinetd

    We suggest installing all the required packages with 'yum' , as we test against the MySQL versions that ship with that distroon CentOS/RHEL Linux systems, and 'apt' on Ubuntu.

    Windows /

    OS X

    macOS

    Anchor

    perl

    python

    perl

    python

    PerlThis is required only for the Workers running the Jobtypes as most are controlled by Perl (with the exception of the cmdline and cmdrange).
    Typically, Linux and Mac OS X come with Perl already installed. If not, RPMs should be available on the distribution CD or by download from the Internet

    Python

    New in 7.5, Python3 (3.6, 3.7, or 3.8) is required for the installation process, as well as for the supervisor. For the workers, it isalso required if running jobtypes that are python controlled.
    Linux and macOS may not come installed with python3 (CentOS/RHEL 7.x, macOS). If not, for RHEL/CentOS, 'sudo yum install python3' should do the trick. For Windows, free Perl Python distributions can be downloaded from ActiveState at www.activestatepython.comorg. On Windows, Qube! is compatible with Perl 5.6 to Perl 5.14.

    Anchor
    pythonpython
    Anchor
    perl
    perl
    Perl

    Perl is required only for the Workers running the Jobtypes that as most are python controlled. If there are none that are used, then this is an optional install.controlled by Perl (with the exception of the cmdline and cmdrange).
    Typically, Linux and Mac OS X macOS come with Python Perl already installed. If not, RPMs yum should be available on the distribution CD or by download from the Internet. For able to install it. On Windows, free Python Perl distributions can be downloaded from ActiveState at www.activestateperl.comorg. We recommend Strawberry Perl. On Windows, Qube! is compatible with Python versions 2.3 through 2.7  .with Perl 5.26.

    Download the Components

    The components are available from the PipelineFX downloads site, via http.

    Linux

    Installing the Supervisor

    1. Disable selinux and firewall using "setup" or available initial boot setup utility

    2. [optional] Mount required network locations using /etc/fstab

    3. Use package installation manager such as yum or apt-get to install "xinetdpython3" & and "mysql-serverxinetd"

    4. Download the required packages for your distribution qube-core, qube-supervisor.  Optionally download qubeguiQubeUI

    5. Install qube-core package with the command: $ rpm –ivh qube-core-*.rpm

    6. Install qube-supervisor package with the command: $ rpm –ivh qube-supervisor-*.rpm

    7. [optional] Using your favorite editor, edit /etc/bashrc to contain the lines :

    Code Block
    export QBDIR=/usr/local/pfx/qube
 
    export PATH=$PATH:$QBDIR/bin:$QBDIR/sbin

    Installing the Worker

    1. Ensure that the worker has all necessary rendering software installed and licensed.
    2. Disable selinux and firewall using "setup" or available initial boot setup utility.
    3. Mount required network locations using /etc/fstab.
    4. Use package installation manager such as yum or apt-get to ensure "xinetd" and "python3" is installed.
    5. Download required packages for your distribution: qube-core, qube-worker. Optionally download qubegui QubeUI and any pertinent jobtypes.
    6. Install qube-core package with the command: $ rpm -ivh qube-core-*
    7. Install qube-worker package with the command: $ rpm -ivh qube-worker-*

    Installing the Client(s)

    There are two clients, and you can install both of them on any user machine. The ArtistView UI is intended for everyday use by artists, while the WranglerView UI is a more advanced interface for power users and render farm admins. Each is compiled so that it contains all its dependencies.

    Install the qube-gui

    QubeUI (new in 7.5) is the unified GUI, and intended to soon replace WV. As of 7.5-0, some of the WV features are yet to be ported to QubeUI, such as the administration features.

    1. Install the QubeUI package with the command: $ rpm -ivh qubeguiQubeUI*Install the ArtistView UI with the command:  $ rpm -ivh qubeArtistView-<ver>.<linux>.rpm
    2. Optionally install WranglerView: rpm -ivh qubegui-*
    3. Make sure that /usr/local/pfx/qube/bin is in the user's PATH variable

    Windows

    Installing the Supervisor 

    1. Install the qube Core MSI by double-clicking the icon. A short message describing the installation will be displayed. If you need to stop the installation, click Cancel at any time.Image Removed
    2. Install the Qube Supervisor MSI by double-clicking the icon. A short message describing the installation will be displayed. If you need to stop the installation, click Cancel at any time:Image RemovedOnce installed
    3. Once the MSI finishes, there's a script that must be run one time by hand. From an Administrator command prompt, run "C:\Program Files\pfx\qube\utils\supe_postinstall.bat"
    4. Once the script finishes running, the Supervisor daemon starts up, and the system will be configured to automatically start up the Supervisor anytime the host is rebooted.
    5. On Windows, the The installer will also install and start up the MySQL PostgreSQL service, followed by the installation and start up of the supervisor or qubesupervisor service.

    Installing the Worker

    1. Install the Qube aube Worker MSI by double-clicking the icon. A short message describing the installation will be displayed. If you need to stop the installation, click Cancel at any time.Image Removed

    Installing the Client(s)

    There are two clients, and you can install both of them on any user machine. The ArtistView UI is intended for everyday use by artists, while the WranglerView UI is a more advanced interface for power users and render farm admins. Each is compiled so that it contains all its dependencies.

    Double–click the qubeArtistView

    QubeUI (new in 7.5) is the unified GUI, and intended to soon replace WV. As of 7.5-0, some of the WV features are yet to be ported to QubeUI, such as the administration features.

    1. Double–click the QubeUI.msi file to install the ArtistView GUI. Use QubeUI.
    2. Optionally use the qubegui.msi file to install the WranglerView GUI.
    3. Follow the step–by–step instructions in the MSI installer application.
    4. From the Start Menu, select PipelinefxQubeQubeUI to launch the WranglerView GUI QubeUI, or PipelinefxArtistView WranglerView to launch the ArtistView WV GUI. Or , or double click on the appropriate respective desktop icon.
    OS X

    macOS

    Installing the Supervisor

    1. Double-click the downloaded .dmg file in order to mount the image containing the .pkg file. Open the disk image. Double-click the qube-core .pkg file to launch the Installer..
    2. The Installer will present a series of screens. Click Continue to proceed. If you need to abort the installation, select Quit from the File menu:Image Removed
    3. Installation of the Qube software requires authentication by an Administrative user. If not running as root, tType type in the user name and password of a user with Administrator privileges and click OK to continue with the installation: Image Removed
    4. Double-click the downloaded .dmg file in order to mount tie image containing the .pkg file. Open the disk image. Double-click the qube-supervisor .pkg file to launch the Installer.
    5. The Installer will present a series of screens. Click Continue to proceed. If you need to abort the installation, select Quit from the File menu:Image Removed
    6. Installation of the Qube software requires authentication by an Administrative user. If not running as root, tType type in the user name and password of a user with Administrator privileges and click OK to continue with the installation
    7. Once installed, the Supervisor daemon starts up, and the system will be configured to automatically start up the Supervisor anytime the host is rebooted.
    8. On OS X, the The installer will also install and start up the MySQL PostgreSQL service, followed by the installation and start up of the supervisor or qubesupervisor service.

    Installing the Worker

    1. Double-click the downloaded .dmg file in order to mount tie image containing the .pkg file. Open the disk image. Double-click the qube-worker .pkg file to launch the Installer.
    2. The Installer will present a series of screens. Click Continue to proceed. If you need to abort the installation, select Quit from the File menu: Image Removed
    3. Installation of the Qube software requires authentication by an Administrative user. If not running as root, Type in the user name and password of a user with Administrator privileges and click OK to continue with the installation

    Installing the Client(s)

    1. Double–click on the .dmg file to mount the disk image file. Open the disk image, and double–click the .pkg file to begin the GUI installation.
    2. Follow the step–by–step instructions in the Installer application.
    3. In /Applications/pfx/qube/bin, double–click the qubeQubeUI icon to launch the WranglerView UIQubeUI, or the ArtistView icon Qube Icon to launch the ArtistView UIWranglerView.

    Installing Multiple Workers using Apple Remote


    Apple Remote desktop Client can also push the pkg files out to your farm. Here is a brief description of the process

    1. Select qube-core, qube-worker, and qubegui and right/ctrl click > open to mount the packagesImage Removed
    2. Open Remote Desktop application
    3. Select required machines for installation
    4. Click Install in the top menuImage Removed
    5. Drag qube-core into the install Packages window

    Image Removed

            7.
    1. Click Install
            8.
    1. Repeat steps 4 to
    7
    1. 6 for qube-worker.
            9.
    1. Repeat steps 4 to
    7
    1. 6 for
    qubegui
    1. QubeUI

    Anchor
    jobtype
    jobtype
    JobType Installation

    Some of the application interfaces construct a commandline command line that is then run directly on the Workers and do not require any additional installation. Other application interfaces (like Maya, and 3dsMax, and XSI) are controlled via (perl or python) scripts. These scripts are installed on the Worker by installing the desired jobtypes.

    The application interfaces with these back-end scripts need to be installed on the Workers. Similarly, there are a few jobtypes that also have front-end scripts to provide in-application submission that should be installed on the Client machines.
    See http://www.pipelinefx.com/products/supported-applications and http://www.pipelinefx.com/docs for details on the specific application interfaces that you are using.

    Tip
    titleNote

    You can install these jobtypes centrally on a network fileserver. See the configuration parameter worker_template_path for the search path used by the Workers for their jobtypes.