Running jobs in Lifecycle Manager
Launch and monitor install, configure, upgrade, and import jobs from the Clusters workspace of 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
Launch and monitor install, configure, upgrade, and import jobs for DSE clusters from the Clusters workspace of Lifecycle Manager.
After Lifecycle Manager (LCM) successfully creates a cluster during an install job, LCM automatically adds the cluster to the OpsCenter workspace for monitoring and management.
Importing a cluster topology is also tracked in the Jobs summary and details.
Lifecycle Manager runs jobs concurrently for different clusters; however, jobs for the same cluster execute sequentially and remain in the pending state while other jobs are currently running.
Meld Remote Execution
At the beginning of each job, an ephemeral and stateless binary program (meld) is copied to the target node to execute the job.
As of OpsCenter 6.7.0, meld does not depend on the presence of a Python runtime.
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:
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.
For further instructions, see Installing a DataStax Enterprise cluster using Lifecycle Manager.