Run an Install and Configure Jobs Overview

Jobs are launched from the Clusters workspace of Lifecycle Manager. Monitor install, configure, and import jobs in the Jobs workspace of Lifecycle Manager.

Jobs are launched from the Clusters workspace of Lifecycle Manager. Monitor install, configure, and import jobs in the Jobs workspace of Lifecycle Manager.

Lifecycle Manager runs jobs concurrently for different clusters; however, jobs for the same cluster execute sequentially and remain in the Pending state while other install or configure jobs are currently running.

The primary job types you can run on an entity in the LCM topology model (that is; cluster, datacenter, or node) are Install and Configure:
  • Install Job: An Install job downloads, installs, and configures DataStax Enterprise versions 4.7 and later onto your pre-launched instances. LCM efficiently skips work that is already completed. For example, DSE is not downloaded again if the correct version of DSE is already installed on a target node, but configure steps are performed if necessary. If a DSE package is already installed but is a different version than specified in the install job, the install job fails. Install jobs are idempotent operations and can be safely rerun, ensuring your cluster continues to operate according to your desired configuration. If a job fails for some transient reason, it can be rerun and LCM efficiently completes the remaining work. Prior to OpsCenter provisioning with LCM, manually removing all traces of DataStax Enterprise packages from the affected nodes was required after a failed provisioning attempt. As of OpsCenter version 6.1.3, and
    Note: If the version of DataStax Enterprise associated with a configuration profile being pushed differs from the installed version, the job fails. Version upgrades or downgrades of DataStax Enterprise are not supported within Lifecycle Manager.
  • Configure Job: A Configure job pushes an associated configuration profile to the appointed nodes and restarts the cluster. An Install Job runs a Configure job in addition to installation.

After Lifecycle Manager successfully creates a cluster during an install job, LCM automatically adds the cluster to the OpsCenter workspace for monitoring and management.

Supported OS platform check for DSE installs

As of OpsCenter version 6.1.3 and later, LCM automatically performs an OS supported platform check for the version of DSE being installed. Success or failures are logged and are also visible when drilling into the Job Details:

Job details showing failed OS platform check for an LCM install job

The OS platform check can be disabled at your own risk by setting the disable_platform_check option to True in the [lifecycle_manager] section of the OpsCenter configuration file, opscenterd.conf.

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