DOC: Configuration Objects

Configuration Objects are used to customize the CBTOOL behavior for each specific environment, plus to alter the execution behavior while running experiments. These objects are basically a list of key-value pairs (in fact, they are internally implemented as Python dictionaries) that are stored on the Object Store (implemented in Redis as hashes).

At the beginning of a CBTOOL execution (or whenever the tool is started with the --soft_reset or --hard_reset option), the configuration objects are built by parsing multiple configuration files, stored on the ~/cbtool/configs/templates/ directory plus a "private" configuration file (by the default, CBTOOL looks for a file called (your username)_cloud_definitions.txt in ~/cbtool/configs). After all configuration objects are built by the combination of multiple files (the "private" configuration file is used to override any attribute described on any other files), each object is stored on the Object Store (i.e., a Redis) server.