Adding a configuration profile
Add a configuration profile that defines the configuration for DataStax Enterprise clusters. The config profile informs Lifecycle Manager which supported version of DataStax Enterprise to install, configure, and manage.
Add a configuration profile that defines the configuration for DataStax Enterprise
clusters. The config profile informs Lifecycle Manager which supported version of
DataStax Enterprise to install, configure, and manage. DSE versions 4.7 and later
are supported.
Note: When you manually upgrade the version of
DataStax Enterprise installed on a cluster, you must add a new Config Profile
that reflects the actual version of DSE installed and update your clusters,
datacenters, and nodes to use the new profile where appropriate. To prevent any
potential loss of settings between different versions, the DSE version cannot be
edited after saving the Config Profile. LCM jobs fail if the installed DSE version does not match the
version specified in the Config Profile associated with a cluster, datacenter,
or node. Automated DSE upgrades are not supported in Lifecycle Manager at this
time.
Note: The data (cluster topology models, 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.
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
Note: The data (cluster topology models, 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 database. You must also configure failover to mirror the
lcm.db.
Procedure
What's next
- Continue customizing the sections of the config profile as appropriate for clusters, datacenters, or nodes.
- Configure Java setup for automatically installing and managing Java installs and upgrades, and for installing and managing the JCE Policy files (recommended).
- Configure a package proxy to cache and accelerate package downloads (recommended), isolate DataStax Enterprise clusters offline from the internet, or both.
- Select the newly added Config Profile and assign it to the appropriate cluster, datacenter, or node in the Clusters Workspace. Edit the cluster, datacenter, or node and select the Config Profile.
- Run a configuration job to propagate the configuration profile to its targets.