You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 26 Next »

    Icon

    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 X).

    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

    Prerequisites

    Linux

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

    The supervisor requires the following packages to be present:

    • xinetd

    We suggest installing all the required packages with 'yum'.

    Windows / OS X

    Perl

    This 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. For Windows, free Perl distributions can be downloaded from ActiveState at www.activestate.com. On Windows, Qube! is compatible with Perl 5.6 to Perl 5.26.

    Python

    New in 7.0, Python 2.6 or 2.7 is required for the Supervisor. For the workers, it is only required if running jobtypes that are python controlled. If there are none that are used, then this is an optional install.
    Typically, Linux and Mac OS X come with Python already installed. If not, RPMs should be available on the distribution CD or by download from the Internet. For Windows, free Python distributions can be downloaded from ActiveState at www.activestate.com. On Windows, Qube! is compatible with Python versions 2.3 through 2.7  .

    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 "xinetd"

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

    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 :

    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" is installed.
    5. Download required packages for your distribution: qube-core, qube-worker. Optionally download qubegui 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.

    1. Install the qube-gui package with the command: $ rpm -ivh qubegui*
    2. Install the ArtistView UI with the command:  $ rpm -ivh qubeArtistView-<ver>.<linux>.rpm
    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.
    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:
    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. The installer will also install and start up the PostgreSQL service, followed by the installation and start up of the qubesupervisor service.

    Installing the Worker

    1. Install the Qube 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.

    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.

    1. Double–click the qubeArtistView.msi file to install the ArtistView GUI. Use the qubegui.msi file to install the WranglerView GUI.
    2. Follow the step–by–step instructions in the MSI installer application.
    3. From the Start Menu, select Pipelinefx➡Qube to launch the WranglerView GUI or Pipelinefx➡ArtistView to launch the ArtistView GUI. Or double click on the appropriate desktop icon.

    OS X

    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:
    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: 
    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:
    6. 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
    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. The installer will also install and start up the PostgreSQL service, followed by the installation and start up of the supervisor 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: 
    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 qube icon to launch the WranglerView UI, or the ArtistView icon to launch the ArtistView UI.

    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 packages
    2. Open Remote Desktop application
    3. Select required machines for installation
    4. Click Install in the top menu
    5. Drag qube-core into the install Packages window
    6. Click Install
    7. Repeat steps 4 to 6 for qube-worker.
    8. Repeat steps 4 to 6 for qubegui

    JobType Installation

    Some of the application interfaces construct a commandline that is then run directly on the Workers and do not require any additional installation. Other application interfaces (like Maya, 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.

    Note

    Icon

    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.

    • No labels