The first step is to configure the relevant paths in the file gvars.py, located in the src directory of the BDS installation.
The file contains examples and useful defaults. The following variables must be modified during the initial installation:
- cfg_mode—Must be set to file in the current version
- cfg_file—Full pathname of the configuration file
- online—True: saving RMS files to S3 and to local storage. False: saving RMS files only to local storage.
- tmp_folder—Temporary folder for storing intermediate processing results. Folder has to be readable and writeable by the user under which BDS code will be executed. Example: tmp_folder = /tmp
- log_file—Full pathname of the log file. The user, under which the BDS code will be executed, must have read and write permissions. Example: log_file = /var/log/brs/brs.log
- log_level—Controls the filtering of information placed in the log file. Valid values: DEBUG or ERROR.
The volume of output log data is very large when using DEBUG level. Example: log_level = ERROR
- log_days_to_keep—Number of days to retain log data. The log file is rotated daily and files older than this value are automatically deleted. Example: log_days_to_keep = 30
A Note About Passwords
Passwords (and s3 keys) that need provisioning in later sections must be provisioned in encrypted form. Template file provisioning must not contain passwords in plain-text format. To obtain encrypted passwords, run the admin utility with the encrypt command: brsctl.py encrypt
The admin utility prompts you for password and prints out the encrypted password. Copy and paste it into the corresponding entry or record in the template.