Job tasks in Lifecycle Manager (LCM)
From the Clusters workspace of LCM, you can run and monitor jobs for DSE clusters, including install, configure, upgrade, and import jobs.
After LCM successfully creates a cluster during an install job, LCM automatically adds the cluster to the OpsCenter workspace for monitoring and management.
Imported cluster topology is also tracked in the Jobs summary and details.
Job concurrency
LCM runs jobs concurrently for different clusters. However, jobs for the same cluster execute sequentially. Queued jobs remain in a pending state while other jobs are 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.
meld does not depend on the presence of a Python runtime.
Supported OS platform check for DSE installs
When starting a DSE install job,LCM checks that the target operating system is a supported platform for DSE. This check ensures that install jobs only run on platforms that are compatible with the DSE version being installed.
If the platform isn’t compatible, the job doesn’t run.
Outcomes are logged and visible in the Job Details.
DataStax recommends leaving the OS platform check enabled to ensure that install jobs only run on supported platforms. If you disable this check, OpsCenter doesn’t stop install jobs from running on unsupported platforms. This can result in failed jobs, errors in DSE, and other issues with the deployment.
To disable this check, set the disable_platform_check option to True in the [lifecycle_manager] section of the opscenterd.conf file.
The location of this file depends on the type of installation:
-
Package installations:
/etc/opscenter/opscenterd.conf -
Tarball installations:
INSTALL_DIRECTORY/conf/opscenterd.conf
