General configuration

All default configuration values are defined in timmy/ Timmy works with these values if no configuration file is provided. If a configuration file is provided via -c | --config option, it overlays the default configuration. An example of a configuration file is timmy_data/rq/config/example.yaml.

Some of the parameters available in configuration file:

  • ssh_opts - parameters to send to ssh command directly (recommended to leave at default), such as connection timeout, etc. See timmy/ to review defaults.
  • env_vars - environment variables to pass to the commands and scripts - you can use these to expand variables in commands or scripts
  • fuel_ip - the IP address of the master node in the environment
  • fuel_user - username to use for accessing Nailgun API
  • fuel_pass - password to access Nailgun API
  • fuel_tenant - Fuel Keystone tenant to use when accessing Nailgun API
  • fuel_port - port to use when connecting to Fuel Nailgun API
  • fuel_keystone_port - port to use when getting a Keystone token to access Nailgun API
  • fuelclient - True/False - whether to use fuelclient library to access Nailgun API
  • fuel_skip_proxy - True/False - ignore http(s)_proxy environment variables when connecting to Nailgun API
  • rqdir - the path to the directory containing rqfiles, scripts to execute, and filelists to pass to rsync
  • rqfile - list of dicts:
    • file - path to an rqfile containing actions and/or other configuration parameters
    • default - True/False - this option is used to make logs_no_default work (see below). Optional.
  • logs_no_default - True/False - do not collect logs defined in any rqfile for which “default” is True
  • logs_days - how many past days of logs to collect. This option will set start parameter for each logs action if not defined in it.
  • logs_speed_limit - True/False - enable speed limiting of log transfers (total transfer speed limit, not per-node)
  • logs_speed_default - Mbit/s - used when autodetect fails
  • logs_speed - Mbit/s - manually specify max bandwidth
  • logs_size_coefficient - a float value used to check local free space; ‘logs size * coefficient’ must be > free space; values lower than 0.3 are not recommended and will likely cause local disk fillup during log collection
  • do_print_results - print outputs of commands and scripts to stdout
  • clean - True/False - erase previous results in outdir and archive_dir dir, if any
  • outdir - directory to store output data. WARNING: this directory is WIPED by default at the beginning of data collection. Be careful with what you define here.
  • archive_dir - directory to put resulting archives into
  • timeout - timeout for SSH commands and scripts in seconds

Configuring actions

Actions can be configured in a separate yaml file (by default timmy_data/rq/default.yaml is used) and / or defined in the main config file or passed via command line options -P, -C, -S, -G.

The following actions are available for definition:

  • put - a list of tuples / 2-element lists: [source, destination]. Passed to scp like so scp source <node-ip>:destination. Wildcards supported for source.
  • cmds - a list of dicts: {‘command-name’:’command-string’}. Example: {‘command-1’: ‘uptime’}. Command string is a bash string. Commands are executed in alphabetical order of their names.
  • scripts - a list of elements, each of which can be a string or a dict:
    • string - represents a script filename located on a local system. If filename does not contain a path separator, the script is expected to be located inside rqdir/scripts. Otherwise the provided path is used to access the script. Example: './'
    • dict - use this option if you need to pass variables to your script. Script parameters are not supported, but you can use env variables instead. A dict should only contain one key which is the script filename (read above), and the value is a Bash space-separated variable assignment string. Example: './': 'var1=123 var2="HELLO WORLD"'
    • LIMITATION: if you use a script with the same name more than once for a given node, the collected output will only contain the result of the last execution.
    • INFO: Scripts are not copied to the destination system - script code is passed as stdin to bash -s executed via ssh or locally. Therefore passing parameters to scripts is not supported (unlike cmds where you can write any Bash string). You can use variables in your scripts instead. Scripts are executed in the following order: all scripts without variables, sorted by their full filename, then all scripts with variables, also sorted by full filename. Therefore if the order matters, it’s better to put all scripts into the same folder and name them according to the order in which you want them executed on the same node. Mind that scripts with variables are executed after all scripts without variables. If you need to mix scripts with variables and without and maintain order, just use dict structure for all scripts, and set null as the value for those which do not need variables.
  • files - a list of filenames to collect. passed to scp. Supports wildcards.
  • filelists - a list of filelist filenames located on a local system. Filelist is a text file containing files and directories to collect, passed to rsync. Does not support wildcards. If the filename does not contain path separator, the filelist is expected to be located inside rqdir/filelists. Otherwise the provided path is used to read the filelist.
  • logs
    • path - base path to scan for logs
    • include - list of regexp strings to match log files against for inclusion (if not set = include all). Optional.
    • exclude - list of regexp strings to match log files against. Excludes matched files from collection. Optional.
    • start - date or datetime string to collect only files modified on or after the specified time. Format - YYYY-MM-DD or YYYY-MM-DD HH:MM:SS or N where N = integer number of days (meaning last N days). Optional.

Filtering nodes

  • soft_filter - use to skip any operations on non-matching nodes
  • hard_filter - same as above but also removes non-matching nodes from NodeManager.nodes dict - useful when using timmy as a module
Nodes can be filtered by the following parameters defined inside soft_filter and/or hard_filter:
  • roles - the list of roles, ex. [‘controller’,’compute’]
  • online - enabled by default to skip non-accessible nodes
  • status - the list of statuses. Default: [‘ready’, ‘discover’]
  • ids - the list of ids, ex. [0,5,6]
  • any other attribute of Node object which is a simple type (int, float, str, etc.) or a list containing simple types

Lists match any, meaning that if any element of the filter list matches node value (if value is a list - any element in it), the node passes.

Negative filters are possible by prefacing filter parameter with no_, example: no_id = [0] will filter out Fuel.

Negative lists also match any - if any match / collision found, the node is skipped.

You can combine any number of positive and negative filters as long as their names differ (since this is a dict).

You can use both positive and negative parameters to match the same node parameter (though it does not make much sense): roles = [‘controller’, ‘compute’] no_roles = [‘compute’] This will skip computes and run only on controllers. As already said, does not make much sense :)

Parameter-based configuration

It is possible to define special by_<parameter-name> dicts in config to (re)define node parameters based on other parameters. For example:

    cmds: {'check-uptime': 'uptime'}

In this example for any controller node, cmds setting will be reset to the value above. For nodes without controller role, default (none) values will be used.

Negative matches are possible via no_ prefix:

    cmds: {'check-uptime': 'uptime'}

In this example uptime command will be executed on all nodes except Fuel server.

It is also possible to define a special once_by_<parameter-name> which works similarly, but will only result in attributes being assigned to a single (first in the list) matching node. Example:

    cmds: {'check-uptime': 'uptime'}

Such configuration will result in uptime being executed on only one node with controller role, not on every controller.

rqfile format

rqfile format is a bit different from config. The basic difference:


scripts: [a ,b, c]
    scripts: [d, e, f]


  __default: [a, b, c]
    compute: [d, e, f]

The config and rqfile definitions presented above are equivalent. It is possible to define actions in a config file using the config format, or in an rqfile using rqfile format, linking to the rqfile in config with rqfile setting. It is also possible to define part here and part there. Mixing identical parameters in both places is not recommended - the results may be unpredictable (such a scenario has not been thoroughly tested). In general, rqfile is the preferred place to define actions.

Configuration application order

Configuration is assembled and applied in a specific order:

  1. default configuration is initialized. See timmy/ for details.
  2. command line parameters, if defined, are used to modify the configuration.
  3. rqfile, if defined (default - rq.yaml), is converted and injected into the configuration. At this stage the configuration is in its final form.
  4. for every node, configuration is applied, except once_by_ directives:
    1. first the top-level attributes are set
    2. then by_<attribute-name> parameters are iterated to override settings and append(accumulate) actions
  5. finally once_by_`<attribute-name> parameters are applied - only for one matching node for any set of matching values. This is useful, for example, if you want a specific file or command from only a single node matching a specific role, like running nova list only on one controller.

Once you are done with the configuration, you might want to familiarize yourself with Usage.