New features in DSE OpsCenter 6.7

New and improved features for the most current major release of OpsCenter Monitoring and Lifecycle Manager for DataStax Enterprise clusters.

The following pages describe the new features in the DataStax Enterprise (DSE) OpsCenter 6.7 release, including major changes from the previous major version.

For a complete list of improvements, resolved issues, and known issues (including the associated ticket numbers and links to KB articles for any workarounds), refer to the release notes and known issues for your installed version of OpsCenter.

For upgrade instructions, see Upgrading DSE OpsCenter.

New features

The following new and improved features are highlighted for the current DSE OpsCenter version 6.7 release.

DataStax Enterprise 6.7
  • Added support for provisioning and monitoring DSE 6.7 clusters.
  • Upgraded to the new DataStax Enterprise Java driver with full support for DSE 6.7.
Lifecycle Manager (LCM)
  • Meld, the remote execution component of Lifecycle Manager that deploys configuration changes to DSE nodes, no longer depends on a Python runtime.
  • LCM managed Java installations now use OpenJDK instead of Oracle Java. This change simplifies licensing and ensures continued support.
  • The default job concurrency policy in LCM now behaves the same as the Single install policy. This default improves robustness of install jobs at the cost of executing jobs more slowly.
Backup Service
  • Azure Blob Storage and Amazon S3-compatible storage support are now included for backup and restore operations.
  • When running a restore, OpsCenter now uses a new default restore mechanism that bypasses SSTableloader to significantly increase performance.

Updates from OpsCenter 6.5

The following changes are updates from the OpsCenter 6.5 major releases.

LCM now installs OpenJDK as the default option

Starting in January 2019, Oracle is ending public updates for the Oracle Java 8 runtime, requiring commercial users to purchase a paid license to obtain updates.

To simplify licensing going forward, LCM in OpsCenter 6.7.0 is introducing support for installing OpenJDK as the default option. LCM will install OpenJDK as distributed by operating system vendors through .deb or .rpm packages. Existing clusters will be migrated to OpenJDK unless Oracle is explicitly selected as the Java vendor prior to running the first install or upgrade job from within OpsCenter 6.7.0.

To understand how this change effects your OpsCenter installation, see Choosing a Java vendor in Lifecycle Manager.