Welcome to Manage 2.8
This document provides the release notes for Gemini Enterprise Manage v2.8. It describes new capabilities and notable changes relative to the previous production release.
For the full capabilities of Manage 2.8 as compared with Manage 2.6.x, please read in combination with the Welcome to Gemini Manage Ver 2.8 document.
Upgrade from previous versions
Manage 2.8 is released as a system upgrade pack which contains new features, system-level changes, and patches released since the Manage 2.6 release.
Confirm your current Manage version before applying this upgrade pack.
An existing installation of Manage 2.6 and above is required for this upgrade pack.
For customers running earlier versions, please contact the Gemini Support team via the Support Portal or contact email@example.com for information on upgrading to the latest version.
What's New in Manage 2.8
System and Foundation
- New Featured Platform that supports Tableau Server. It allows user to deploy Tableau on Gemini Enterprise software from an uploaded binary from the official Tableau website. Users are able to control the running services and observe the status of Tableau.
- New Featured Platform that introduces Gemini Explore. Gemini Explore is a graph analytics solution that helps diagnose problems or uncover visual insights from your data. It allows users to deploy Gemini Explore on Gemini Enterprise by pulling binaries from the internet. Users are able to control running services and observe the status. Consult with Gemini Support or access to Gemini Support Portal for more Gemini Explore documentations. Please note Gemini Explore is still in its experimental phase. Contact your Gemini sales to obtain the activation key file if you would like to request a trial.
- Cloudera has been removed from the existing featured platforms.
- New Manage Group registration process. The direction of registration process has been reversed so that the Manage administrator is able to occupy unmanaged 'Child' nodes directly from the 'Parent' node.
- The bash profile of OS user splunk has been updated to make shell accesses more user friendly.
- Fixed multiple security vulnerabilities discovered and validated prior to
June 3, 2020.
- New SSH Key management enhancements that allow users to manage SSH public keys per OS user, and the ability to import/export these Keys from one instance to another.
- New validation feature when creating an LDAP configuration connection. This tests connectivity to the destination LDAP server.
- New capability that allows the cloning of OS users and LDAP configurations to other Manage nodes.
- New Manage Nodes dashboard that lists all the managed nodes including Agent nodes, and reports on their currect status. This includes metrics such as CPU, RAM and available disk space.
- New boot-enable option using Linux systemd for Splunk that enables support for the Splunk workload management feature. This gives modern service control management in Linux, as well as cgroup support. *Note: For new installations of Splunk, services will be managed by systemd by default. For adopted nodes with Splunk installed and running, Manage will keep the boot-enable setting as is (initd).*
- New Splunk Environments feature that allows a user to
gather a Splunk diag from each
member node and store centrally
within the Splunk diagnostic dashboard of the parent node.
- New heartbeat monitoring capability in Splunk Environments that will detect a Splunk 'running' status on each node and display a warning when Splunk stops.
- New action button in Config Editor dashboard that allows a user to uncompress a zip file in a particular folder.
- Hunk support is deprecated and has been removed.
- MGR-2779: Password Policy is not getting applied if Password Expiration Duration checkbox is unchecked and then checked again.
- MGR-3183: Job stays in Dispatched state on master node and is not getting dispatched to agent nodes.
- MGR-3241: The upload time display of a license is not formatted.
- MGR-3267: Incorrect message when unmount has failed.
- MGR-3309: Unable to add single node to an existing cluster.
- MGR-3326: A scheduled job will run immediately after created in Gemini Cluster.
- MGR-3567: Sometimes destroy a Splunk standalone instance will produce a phantom node.
- MGR-3569: Sometimes navigating a page would take too long.
- Sometimes there is a fail message when installing an app from the Gemini Integration Center. In fact the app has been installed successfully.
- VMware Appliance: If there are iSCSI devices mounted, the boot-up process will fail unless you unmount all iSCSI devices BEFORE running the upgrade process.
Supported Platform Application Versions
- Splunk Enterprise 8.0
- Splunk Enterprise 7.0
- Splunk Enterprise 7.1
- Splunk Enterprise 7.2
- Splunk Enterprise 7.3
- Splunk Enterprise 8.0
- Splunk Light 7.0
- Splunk Light 7.1
- Splunk Light 7.2
- Splunk Light 7.3
- Splunk Light 8.0
Deprecated and removed features
- Cloudera has been removed from Featured Platforms.
- Hunk support has been removed from Splunk Manager.
|1.||A reboot is required after upgrade. Backup the system and ensure it is offline before an upgrade. For VMware Appliances, ensure all the iSCSI devices are unmounted.|
|2.||The upgrade process will take 5-10 minutes. During the upgrade, all Manage services will be stopped, allowing no operation of Manage.|
|3.||Under no circumstance should a manual reboot be conducted during the upgrade. This will cause unrecoverable damage. Gemini appliance will reboot automatically following a successful upgrade.|
All third-party products mentioned within this document are the property of their respective owners.