Introduction

While trying to create or clone a configuration-profile (CP) in Lifecycle Manager (LCM) within OpsCenter, the desired DSE version doesn't appear in the Datastax Enterprise Version dropdown.

The use case might be to run an install job to install a new cluster or configure a recently imported cluster.

Configuration-profiles (CP's) are driven by OpsCenter definitions. In order to use a new DSE version with LCM, one must be running a compatible version of OpsCenter and also have definitions that are newer than the DSE release you want to install or configure.

OpsCenter Compatibility

Each major release of OpsCenter is compatible with certain major releases of DSE. The list of compatible releases can be found on the Product Compatibility page. Ensure that your OpsCenter version supports the version of DSE that you're trying to install.

Definitions Updates

DSE patch releases are made available regularly and OpsCenter gains support for these new patch releases through definitions updates. In order for LCM to handle CP's for the new DSE versoin, OpsCenter must have sufficiently up-to-date definitions.

Definitions updates can be acquired in one of three ways:

1. Automatic Updates: OpsCenter ships with automatic definitions updates enabled by default. On startup, and periodically while running, an OpsCenter instance will attempt to contact opscenter.datastax.com on port 443 via HTTPS and download updated definitions.
2. Manual Updates: For OpsCenter instances that are offline or lack outbound https connectivity to opscenter.datastax.com, definitions can be updated manually.
3. Upgrade OpsCenter: Each new release of OpsCenter ships with built-in definitions that are up-to-date as of the time of release and upgrading OpsCenter will also update definitions. Note that in some cases, the most recent DSE patch release will be newer than the most recent OpsCenter release. In this case it's necessary to update definitions or to wait for a new OpsCenter release.

Cloning Configuration-Profiles

Additional constraints are present when cloning a pre-existing configuration profile. It's only possible to clone to the same DSE version or a newer version within the same stable series. For example, if I have a pre-existing CP for DSE 5.1.8 then I can clone it to 5.1.8 or 5.1.9. I cannot clone it to DSE 5.1.7, that's older than what I started with. I also cannot close it to DSE 6.0.4, that's a newer stable series.