Configuration Options › Controller Customization

Controller Customization

The following parameters are for customizing the setup of the controller before a grid installation.

Note: This approach can be useful when setting up multiple grids on the same LAN that with the same initial configuration.

The controller customization parameters are not specified on the aldo command line or in its configuration files. Instead, they are found in a separate configuration file:

controller.conf

The file is read by default from the distribution root directory. An alternate file can be specified, if desired, using the ctl_cfg= parameter on the aldo command line.

All of the controller customization settings are applied to the grid when it is first installed with the aldo new command. Some of the settings can be reconfigured, using the aldo set command. To read and apply the customization file on the aldo set command, specify the ctl_cfg parameter on the command line, as follows:

• aldo set grid.... ctl_cfg==

  An empty value for ctl_cfg applies the default customization (either factory-default, or the one found in controller.conf, if the file is present).

• aldo set grid.... ctl_cfg== file-path

  An explicit file name can be given, to specify an alternate customization file.

When the customization file is not present, the following factory default values are used:

oem_kit

A directory name, which is specified as an absolute path, containing OEM customization files (grid "branding"). If the value is not set, ALDO looks for a subdirectory named oem_kit in the distribution home directory, from which the aldo command was run.

Note: Except for the special case of oem_kit being empty, a relative directory name cannot be specified.

Leaving the directory empty or setting the value of oem_kit to none disables the OEM branding. The aldo new command will not install an OEM kit. If the ctl_cfg= parameter is specified, the aldo set command removes the installed OEM kit from the grid.

Applied both on new and set.

Default: ./oem_kit (see the previous note)

support_userid

CA Support account user ID (for example, joe@CO.com). Set to empty to disable the support account.

Applied only on new, ignored on set. To add/remove/modify users on a working grid, use the command line or the GUI interface.

Default: Empty

support_ssh

SSH public key of the support user, in OpenSSH format. If empty, the support account cannot be accessed over ssh.

Applied only on new, ignored on set. To add/remove/modify users on a working grid, use the command line or the GUI interface.

Default: CA Technologies key accessible to CA Support

usr1_id

ID of the initial user to install in the user database. If empty, the database is empty. The Installer has to log in to the controller and set up the first user manually. This setting is preferred, if the different grids planned to be installed on the same LAN are not shared. Otherwise, set this parameter to the email of a user that initially has access to all grids.

Applied only on new, ignored on set. To add/remove/modify users on a working grid, use the command line or the GUI interface.

Default: Empty

usr1_pwd

Password for the initial user. The default value of '-' displays a prompt.

Applied only on new, ignored on set. To add/remove/modify users on a working grid, use the command line or the GUI interface.

Default: -

usr1_ssh

Public SSH key for the initial user. If this parameter is not set but usr1_id is set, the initial user has no command line access until a key is configured. root login to the controller with one of the "administrator" keys (for example, the administrator that installed the grid) is needed for that access.

Applied only on new, ignored on set. To add/remove/modify users on a working grid, use the command line or the GUI interface.

Default: Empty