Versions Compared

    Key

    • This line was added.
    • This line was removed.
    • Formatting was changed.

    ...

    Expand
    titleMacro Variables

    To simplify definition of templates as well as Worker configurations, the qbwrk.conf also supports the use of macro variables. These are in the format:

    The template names self and this are reserved words and can be used to reference local settings. The variable $_ is also reserved for the local template's name as well as to represent child templates which inherit the template.

    Format

    [template]key = value[host]otherkey = ${template.key}
    evaluates to:
    [template]key = value[host]otherkey = value

    Example

    [ref]
    worker_cluster = /project[logs]
    worker_logfile = "/logdir/${_}.workerlog"

    [qb001] : template

    • inherit template

    worker_cluster = "${ref.worker_cluster}/vfx"

    • For Worker qb001, worker_cluster will evaluate to "/project/vfx".

    [qb002] : template

    • inherit template

    worker_cluster = $ref.worker_cluster

    • In the case of Worker qb002, worker_cluster is defined to be the worker_cluster entry from template ref: "/project".
    Expand
    titleKey / Value Pairs

    The qbwrk.conf file is broken up into sections containing key/value pair settings. Each section is described by a header between brackets "[" and "]". Section names may only consist of the characters a-z, A-Z, 0-9 and "_". As for the key/value pair format, the key's name is always represented first, followed by an "=" sign and finally the value. While whitespace such as spaces or tabs don't matter, it is important that the key/value pair remain on a single line unless curly braces are used to describe the value.

    Format

    [section]
    key = valuekey = "value1 value2"
    key = { value1 value2 }

    Example

    [qb001]

    •  hostname

    worker_cluster = /projects/movie

    • config entry
    Expand
    titlePredefined Platform Sections

    There are a few "special" section names that can be used for the different platforms. These will be associated with the Workers using the respective platform.

    • [winnt]
    • [osx]
    • [linux]

    Example

    [linux]
    worker_cluster = /mylinuxboxes

    Expand
    titleTemplate Inheritance

    The advantage of the macro file format is the use of template inheritance and value replacement. A section is allowed to "inherit" another section's key/value pairs. This can be accomplished by adding a colon and a space-delimited list of templates.

    Icon

    The qbwrk.conf file is read from top - to - bottom. A template can only inherit from an already-defined template that appears before it in the file.

    Example

    The section:

    [qube]
    key9 = value00

    [section]
    key = value
    key1 = value1

    [section2] : section
    key = value3

    [section3] : section2 qube

    evaluates to:

    [qube]
    key9 = value00

    [section]
    key = value
    key1 = value1

    [section2]
    key = value3
    key1 = value1

    [section3]
    key = value3
    key1 = value1
    key9 = value00

    ...