Configuring¶

Received variables¶

List of variables with their extraction methods are available in the appendix:

variables.txt

Variable example:

AUTH_URL
Variable default value: http://localhost:5000
Variable extraction sequence: OS_AUTH_URL

where:

• AUTH_URL is the internal variable name;
• http://localhost:5000 is the default value for the variable, if none of the extraction methods found a variable by the extraction sequence;
• OS_AUTH_URL is the name of the variable from which the value for the specified internal variable will be retrieved.

Module variables¶

Use the appropriate prefix in order to set parameters for a specific module. Module prefixes:

• Dashboard - DASH;
• Monitor - MONITOR;
• CloudManager - CM;
• Scheduler - SCHEDULER;
• Journal - JOURNAL;
• RSserver - RS.

Example:

Suppose there are following variables in the global environment:

DB_SUPERUSER_PASSWORD="123456"
CM_DB_SUPERUSER_PASSWORD="cloud_pass"

Variable will be extracted as the password to access database based on the extraction methods.

In this case the password for accessing database will be 123456 for all modules except CloudManager and the password will be cloud_pass for the module CloudManager.

Extraction methods¶

Product settings are managed in the following ways:

1. Through operating system environment variables;
2. Reading existing modules configuration files (will be performed when specifying the --overwrite-configs utility argument);
3. Passing parameters to the autosetup script arguments;
4. Through the script argument autosetup (parameter config_file) specifying the config file.

Order of the methods determines the retrieval of the variable.

Each next one overrides the value extracted earlier, this ensures the retrieval priority.

Setting up auto installation¶

aos-autosetup --packages cloudmanager dashboard

dashboard
monitor
cloudmanager
scheduler
journal
rs_server

Environment variables¶

Environment variables are extracted by name from system environment variables. Only those that are in the list of extracted variables are used. If the environment variable LC_ALL is not specified, then it is created, the value for it is used from the variable LANG.

Configuring autoinstallation using a script¶

aos-autosetup --os-auth-url "http://controller:5000" --os-username root
aos-autosetup --help - this command lists all the available arguments in order

aos-autosetup --config-file ~/adm

export OS_AUTH_URL="http://controller:5000"
export OS_USERNAME=root

aos-autosetup --overwrite-configs

aos-autosetup --pip-args="--no-deps"
aos-autosetup --pip-args="--pre --no-deps"

aos-autosetup --pip-args="--no-index --find-links ./packages"