1.9 (Zeus)

Changelog for 1.9 (Codename: Zeus)

Starting with 1.9, Director now provides an intelligent, simplified and user-friendly recommendation-based wizard to provision OpenEBS cStor pools based on the new CStorPoolCluster (CSPC) schema.
This feature is available on OpenEBS 1.9 installed from Director.
Director first discovers all the block devices attached to each node in the cluster.
Director supports provisioning CSPC pool instances of 4 RAID groups - Stripe, Mirror, Raidz and Raidz2 and provides two types of recommendations - capacity and configuration - based on the device types.
Once the user chooses the RAID group and an existing device type, Director suggests the minimum and maximum possible pool capacities for the selected RAID group and device type. A user can specify any capacity in this range.
Once the user provides the capacity, Director suggests the available nodes and the block device configuration which can serve the capacity.
User can select any number of nodes from this list and deploy the pools with a single click.
A new Data Agility Operator (DAO) component named 'cstorpoolauto' handles the provisioning of OpenEBS cStor pools in the connected cluster. This operator is a Kubernetes custom controller based on metacontroller add-on.
For more information on OpenEBS cStor pool provisioning support in Director, visit here.

A Director user gets the new volume CSI drivers and CSPC operators pre-bundled with the OpenEBS 1.9 installation.
This facilitates to create CSI-based cStor volumes on platforms like Ubuntu, CentOS, SuSE and others.
For more information on the OpenEBS installation from Director, visit here.

Prior to Director 1.9, there was no UI workflow to upgrade OpenEBS control-plane components.
User had to upgrade the control-plane components on his own and come to Director for patching of only pools and volumes.
With this release, a user can perform an end-to-end upgrade of all OpenEBS components to the version 1.9.0.
This is only supported for OpenEBS installations done through Director.
For more information on the upgrade support, visit here.

Director versions, prior to 1.9, supported backup and restore of stateful applications as a part of DMaaS (Data Migration as a Service).
However this support was limited to applications using OpenEBS cStor volumes.
Director 1.9 provides an alternate way for scheduling backups based on Velero Restic plugin.
This approach works for backup and restore of all types of applications regardless of whether they use OpenEBS (Jiva, CStor, LocalPV) or non-OpenEBS persistent volumes.
Effectively, any cloud-native application can now be backed up and restored using Director DMaaS workflow.
For more information on how to backup and restore your application using DMaaS, visit here.

UI now supports listing of all the nodes in the cluster under a 'Nodes' section.
UI now supports listing of all the block devices in the cluster under a 'Block Devices' section.
Added a 'Management' sub-menu in the cluster menu side-bar.
The 'Storage Pools', 'Nodes' and 'Block Devices' are listed under the 'Management' sub-menu.
Added collapsible project side-bar functionality.
Added a quick navigation for 'Active Clusters'.
Enhanced display for view-by filter in the OpenEBS pools, block devices and volumes page.

Added support for fetching details of CSI volumes and CSPC pool clusters and instances.
Added support for fetching metrics of the above resources and display monitoring graphs.
Added log collection support for the above resources.
Added validation for the configurable fields of the alert rules.

Fixed an issue where the user-selected filters were being overridden on an automatic refresh of the 'Alerts' page.
Fixed an issue where a blank page comes up sometimes when a user clicks on login or logout.
Fixed an issue due to which an On-prem Administrator was not able to sign in once he has changed his email address.
Fixed an issue where the node CPU and memory usage details were not getting fetched from the topology (Scope) components on some Kubernetes platforms.
Fixed an issue where duplicate metrics were being plotted in the monitoring graphs for pools and volumes.
Fixed an issue which caused a flood of 'Pool Unhealthy' alerts.

A user, who is a part of multiple projects, will not be able to open monitoring graphs and logs of different projects in different browser tabs.
Currently, Minio application monitoring only works for Minio with image minio/minio:RELEASE.2019-09-18T21-55-05Z and earlier. The images later than minio/minio:RELEASE.2019-09-18T21-55-05Z have an in-built authentication that needs to be supported by Director.
Sometimes, monitoring graphs display error if Director consul or ingester pod restarts. The workaround is to manually restart the consul pod and all the ingester, querier and distributor pods.