-
Language:
English
-
Language:
English
Chapter 1. What's New in this Release?
This section describes the key features and enhancements in the Red Hat Openshift Container Storage 3.10 release.
- Arbiter volume support enabling availability with efficient storage utilization and better performance: Arbiter volume supports all persistent volume types with better consistency and less disk space requirements. The arbiter uses client quorum to compare this metadata with the metadata of the other nodes to ensure consistency in the volume and prevent split-brain conditions.
- Information about setting up arbiter volumes is available in https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-creating_arbiter
- Information about managing arbiter volumes is available in https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#Managing_Arbiter_Volumes
- Rebranding: With the release of OpenShift Container Platform 3.10, we are rebranding Container Native Storage to Red Hat OpenShift Container Storage. Along with this rebranding, the terms describing the method of deployment have also been changed to:
- Converged mode (formerly referred to as ‘Container Native Storage’ or ‘CNS’) refers to running storage services in a container itself, like any other service.
- Independent mode (formerly referred to as ‘Container Ready Storage’ or ‘CRS’) refers to running storage services outside the container platform as a standalone subsystem which gets consumed by OCP.
- Ansible as the primary mode of installation: Ansible is now the preferred mode of installation and end-to-end ansible workflows are integrated into the Red Hat Openshift Container Storage Deployment Guide. Ansible automates the process of installing Red Hat Openshift Container Storage in both converged and independent mode, and this makes it less error prone when compared to manually executing numerous commands:
- To install Red Hat Openshift Container Storage in converged mode, see https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-Documentation-Deploy-CNS
- To install Red Hat Openshift Container Storage in independent mode, see https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-Documentation-Deploy-CRS
- Separate Deployment Guide and Operations Guide: Enhancements and features available in the Red Hat Openshift Container Storage are now available in two separate guides - one for Deployment and upgrade and another for administrative tasks. With Red Hat Openshift Container Storage 3.10 we have the following two guides:
- Enhanced OCS monitoring and configuration visibility using the Prometheus framework: The statistics of gluster block PVs can be obtained by setting up Prometheus and enabling volume metrics for glusterfs plugin. The different metrics of the PVs that can be viewed on Prometheus are:
kubelet_volume_stats_available_bytes: Number of available bytes in the volume.kubelet_volume_stats_capacity_bytes: Capacity in bytes of the volume.kubelet_volume_stats_inodes: Maximum number of inodes in the volume.kubelet_volume_stats_inodes_free: Number of free inodes in the volume.kubelet_volume_stats_inodes_used: Number of used inodes in the volume.kubelet_volume_stats_used_bytes: Number of used bytes in the volume.
For more information about Volume metrics, see https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/operations_guide/#enable_vol_metrics. - Reclaiming persistent volume: You can now set the persistentVolumeReclaimPolicy in the storage class. When this parameter is set to "Retain" the underlying persistent volume is retained even after the corresponding persistent volume claim is deleted. This ensures you do not lose your data if you accidentally delete the PVCs.
- For more information about setting the persistentVolumeReclaimPolicy in the storage class for file storage, seehttps://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/operations_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-OpenShift_Creating_Persistent_Volumes-Dynamic_Prov
- For more information about setting the persistentVolumeReclaimPolicy in the storage class for block storage, see https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/operations_guide/#Block_dynamic_prov_vol
- Replace a block on block storage: With the release of Red Hat OpenShift Container Storage 3.10, you can replace a block from a node that is out of resource or is faulty, to a new node. For more information see, https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/operations_guide/#replace_block
- Ansible-based uninstall (cleanup) of all resources and artifacts from the cluster: By using ansible based uninstall, any existing GlusterFS-related resources and configurations from a Red Hat OpenShift Container Storage deployment is removed. For more information about Uninstall Red Hat Openshift Container Storage see, https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Uninstall_CNS
