Lifecycle Manager configuration options
Configuration options available in opscenterd.conf for Lifecycle Manager.
opscenterd.conf
The location of the opscenterd.conf file depends on the type of installation:- Package installations: /etc/opscenter/opscenterd.conf
- Tarball installations: install_location/conf/opscenterd.conf
lcm.db
The location of the Lifecycle Manager database lcm.db depends on the type of installation:- Package installations: /var/lib/opscenter/lcm.db
- Tarball installations: install_location/lcm.db
Reference of configuration options in available opscenterd.conf for Lifecycle Manager. After changing properties in the opscenterd.conf file, restart OpsCenter for the changes to take effect.
- [lifecycle_manager] db_location
- The location of the lcm.db database used for storing Lifecycle Manager information. Default: /var/lib/opscenter/lcm.db
Note: The data (cluster topology, configuration profiles,
credentials, repositories, job history, and so forth) for Lifecycle Manager is
stored in the lcm.db database. Your organization is
responsible for backing up the lcm.db database. You must also
configure failover to mirror the
lcm.db database.
- [lifecycle_manager] cacerts_directory
- The directory to use when storing SSL-related files that are automatically generated during provisioning tasks. Default: /var/lib/opscenter/ssl/lcm
- [lifecycle_manager] cacerts_truststore_location
- The location of the truststore containing the root CA cert for signing certificates. Default: /var/lib/opscenter/ssl/lcm/lcm-auto-generated.truststore
- [lifecycle_manager] cacerts_truststore_password
- The password to open the cacerts truststore.
- [lifecycle_manager] crypto_key_file
- The key to use to encrypt sensitive data in the database for storing Lifecycle Manager information. The encryption key is automatically generated if it does not already exist. Default: /etc/opscenter/lcm.key
- [lifecycle_manager] job_manager_polling_interval
- Polling frequency in seconds when performing Lifecycle Manager tasks. Default: 5 seconds.
- [lifecycle_manager] node_install_idle_timeout
- Duration of inactivity in seconds before marking an install job as idle. Default: 900 seconds.
- [lifecycle_manager] node_restart_idle_timeout
- Duration of inactivity in seconds before marking a node restart job as idle. Default: 300 seconds.
- [lifecycle_manager] node_configure_idle_timeout
- Duration of inactivity in seconds before marking a node configuration job as idle. Default: 300 seconds.
- [lifecycle_manager] node_cluster_import_idle_timeout
- Duration of inactivity in seconds before marking a cluster import job as idle. Default: 120 seconds.
- [lifecycle_manager] node_install_agent_idle_timeout
- Duration of inactivity in seconds before marking an agent install job as idle. Default: 120 seconds.
- [lifecycle_manager] cassandra_connection_timeout
- Duration in seconds to allow for connecting to DataStax Enterprise when provisioning a DataStax Enterprise cluster. Default: 20 seconds.
- [lifecycle_manager] ssh_connect_timeout_in_seconds
- The number of seconds to wait for the SSH server on a target node to respond to a connection attempt during an LCM job. Default: 30 seconds.
- [lifecycle_manager] ssh_max_attempts
- The maximum number of times to attempt an SSH connection to a given target during an LCM job. Default: 3.
- [lifecycle_manager] ssh_retry_delay_in_seconds
- The number of seconds to wait between SSH connection retries during an LCM job. Default: 10 seconds.
- [lifecycle_manager] disable_platform_check
- Platform check ensures DSE compatibility and support. Disable at your own risk. Default: False.