Release Notes
IOMesh 1.0.1 Release Notes
What's New
New Feature
Automatically configures open-iscsi for all schedulable nodes in the Kubernetes cluster when deploying IOMesh or adding nodes to the IOMesh cluster.
Resolved Issues
- The I/O performance was not as expected due to inconsistent port information between the
chunkservice registered with themetaservice and the locally recorded port information. The issue has been resolved in this release. - IOMesh was unable to run in Kubernetes clusters of 1.21 or earlier versions due to incompatibility between the
zookeeper-operatorversion and Kubernetes version. The issue has been resolved in this release. - In Kubernetes clusters 1.20 or earlier versions, when enabling the NDM webhook, the creation of BlockDevice and BlockDeviceClaim failed due to empty CR parameters. The issue has been resolved in this release.
Specifications
| Component | Version |
|---|---|
| iomesh-operator | 1.0.1 |
| csi-driver | 2.6.0 |
| zbs | 5.3.0 |
| zookeeper | 3.5.9 |
| node-disk-manager | 1.8.0 |
| hostpath-provisioner | 0.5.3 |
| block-device-monitor | 0.1.0 |
| local-pv-manager | 0.1.0 |
Compatibility
Server Architecture Compatibility for IOMesh
IOMesh is compatible with Intel x86_64, Hygon x86_64 or Kunpeng AArch64 architectures.
Kubernetes and Linux OS Compatibility for IOMesh
| Software/OS | Version |
|---|---|
| Kubernetes |
|
| Linux OS |
|
NOTE: IOMesh has no dependencies on the Linux OS version. The versions listed above are tested versions only.
IOMesh 1.0.0 Release Notes
What's New
New Features
Installation & Deployment
- Adds support for deploying IOMesh on the Hygon x86_64 and Kunpeng AArch64 architectures.
- Adds support for Kubernetes version 1.25.
- Enables deployment of multiple IOMesh clusters within a single Kubernetes cluster.
Storage
- Allows for dynamically provisioning PVs using local storage like a directory or block device for pod use.
- Implements CSI typology feature to ensure that when there are multiple IOMesh clusters, pods that use PVs from a specific cluster can be scheduled on the worker node that holds that cluster.
- Triggers pod high availability when its worker node has a power outrage.
Operations & Management
- Detects abnormal disks and isolates disks in
Unhealthystate to minimize the impact on system performance and reduce operational burden.
Improved Features
Storage
- Reduced IO interruption to within 22 seconds in case of node or network failure, ensuring that data access is timely and reliable even in the face of disruptions.
- Enhanced data security by assigning a temporary replica to hold newly written data after a replica has been removed.
- Enhanced data channel fault tolerance to prevent disconnection due to IO timeout.
- Optimized Lease Owner allocation mechanism to avoid IO failures due to network failures, enabling more efficient and robust data transmission.
- Cleared the file lock created when executing
iscsiadm, or else the CSI driver will be unavailable. - Simplified the configuration method for accessing IOMesh from outside its Kubernetes cluster, eliminating the need to create a separate Kubernetes service and making it easier to access and use IOMesh.
- Optimized the default CPU/memory resource limit setting for pods to avoid pods running slowly due to insufficient resources.
Operations & Management
- Added an alert panel on the IOMesh dashboard and display of information about cluster, physical disk, and PV, providing administrators with real-time monitoring and status updates.
Resolved Issues
Storage
- Meta DB space become full after a snapshot of a large volume was taken, making the ZooKeeper unavailable. This issue has been resolved in this version.
- After the chunk IP was changed, the data channel manager was unable to detect the new chunk IP, resulting in data migration failure. The issue has been resolved in this version.
Operations & Management
- Uninstalling IOMesh via
Helmsometimes left pod resources behind, which has been resolved in this version.
Specifications
| Component | Version |
|---|---|
| iomesh-operator | 1.0.0 |
| csi-driver | 2.6.0 |
| zbs | 5.3.0 |
| zookeeper | 3.5.9 |
| node-disk-manager | 1.8.0 |
| hostpath-provisioner | 0.5.3 |
| block-device-monitor | 0.1.0 |
| local-pv-manager | 0.1.0 |
Compatibility
Server Architecture Compatibility for IOMesh
IOMesh is compatible with Intel x86_64, Hygon x86_64 or Kunpeng AArch64 architectures.
Kubernetes and Linux OS Compatibility for IOMesh
| Software/OS | Version |
|---|---|
| Kubernetes |
|
| Linux OS |
|
NOTE: IOMesh has no dependencies on the Linux OS version. The versions listed above are tested versions only.
Known Issues
- If a Kubernetes cluster has multiple IOMesh clusters deployed, the IOMesh dashboard will display alert information of all clusters instead of just one.
- The IOMesh dashboard cannot display the correct storage capacity usage when the IOMesh cluster has invalid storage capacity.
- A PV with
Blockas the volume mode can still be written due to a Kubernetes code defect even if the access mode is ReadOnlyMany. - The following issues persist due to a flaw in the NDM mechanism:
- After an IOMesh cluster is uninstalled, the disk corresponding to the block device used by this cluster might not be cleared.
- After the IOMesh Device Local PV is deleted, the disk corresponding to the block device might not be cleared.
- The status of a block device might switch back and forth between
activeandinactive, which sometimes causes the disk to be unmountable.
- After removing the chunk pod on a worker node, IOMesh CR still shows disks on this node.
- After an IOMesh cluster is uninstalled, the metrics in the IOMesh Operator may not be completely cleaned up. This can cause the license edition to not be displayed in the dashboard if you later deploy an IOMesh cluster with the same name in the same namespace. You may restart the Operator pod to fix this issue.
- If a prober pod of BDM(Block Device Monitor) panics during startup due to network issues or other problems, the detection process will not be automatically recovered. This may cause the IOMesh dashboard to display incorrect disk information. Restarting the prober pod can fix this issue.
- Newly deployed IOMesh 1.0.0 clusters may not display the correct version of IOMesh Block Storage on the IOMesh dashboard due to an error in obtaining the meta leader. This issue does not affect clusters upgraded from previous versions to 1.0.0.
IOMesh 0.11.1 Release Notes
What's New
New Feature
Add support for Kubernetes versions 1.22 to 1.24.
Improved Features
- Optimized the method of clearing corresponding LUNs in IOMesh after deleting the PV with the reclaim policy set to Retain.
- Improved the way of managing
open-iscsito ease IOMesh installation on various Linux distribution software. - Simplified Snapshot Controller installation. The Snapshot Controller will be installed together with IOMesh.
Fixed Problems
- Fixed the problem that the name of
iscsi-redirectd daemonsetdid not conform to the naming convention. - Fixed the problem that the operations of SCSI-3 PR (Persistent Reservation) might fail due to non-compliance with the SCSI-3 PR protocol.
- Fixed the problem that the time to mount a disk was occasionally too long.
- Fixed the problem that configurations could not take effect when the user customized the NDM image repository.
- Fixed the problem that the number of cloned PV replicas or PV replicas created from a snapshot might be inconsistent with that of original PV replicas.
Specifications
| Component | Version |
|---|---|
| iomesh-operator | 0.11.1 |
| csi-driver | 2.5.1 |
| zbs | 5.1.2 |
| zookeeper | 3.5.9 |
| node-disk-manager | 1.8.0 |
| hostpath-provisioner | 0.5.2 |
Compatibility
Server Architecture Compatibility for IOMesh
IOMesh is compatible with Intel x86_64 and AMD x86_64 architectures.
Kubernetes and Linux OS Compatibility for IOMesh
| Item | Version |
|---|---|
| Kubernetes |
|
| Linux OS |
|
NOTE: IOMesh has no dependencies on the Linux OS version. The versions listed above are tested versions only.
IOMesh 0.11.0 Release Notes
What's New
New Features
Installation and Deployment
- Support deployment of the IOMesh cluster in the all-flash mode.
- Support deployment of the IOMesh cluster using the offline installation package.
Functionality
Support providing iSCSI storage services to the compute platforms disaggregated from the IOMesh cluster.
Operation
- Implement the NodeGetVolumeStas interface in CSI Spec and support PV monitoring with third-party monitoring platforms such as Prometheus.
- Support displaying the connection status of Chunk services.
Improved Features
- Declare reserved CPU and memory resources for IOMesh Operator, NDM, and Zookeeper Operator to ensure the QoS of their pods.
- Introduce Webhook to avoid unexpected parameter changes of clusters.
- Simplify IOMesh installation by improving the IOMesh deployment script.
- Optimize the license renewal method to update the license using the Kubernetes API.
- Optimize the replica policy with only replication factor two or three is supported.
- Optimize the process of ZBS upgrade.
- Optimize the Liveness/Readyness probing methods of IOMesh pods to avoid false alarms due to high system load.
Resolved Issues
The issues listed below are resolved in this release.
- NDM 1.7.x creates partitions for the disk by default when the WWID is not identified, causing the disk to be not mounted as cacheWithJournal or dataStoreWithJournal.
- The disk cannot be mounted when installing IOMesh Operator in the OpenShift Container Platform.
- The IOMesh system crashes because the loop device has been mounted by NDM.
- Probe cannot get the process status and causes a CrashLoop, as the process name has been modified.
- Memory leaks because Probe does not close RPC connections.
- Memory leaks due to ZBS Client not being freed.
- The newly created pods attached with PVCs time out when the number of pods attached with PVCs on a Kubernetes worker node exceeds 100.
- A timeout occurs when formatting a PV as an XFS file system, as the size of PV exceeds 5TB.
- The disk cannot be mounted while device manager logs show messages of successful mounting.
Known Issues
- Replica factor of PVs by CSI volume cloning may not be consistent with original PVs.
Specifications
| Component | Version |
|---|---|
| iomesh-operator | 0.11.0 |
| csi-driver | 2.4.0 |
| zbs | 5.2.0 |
| zookeeper | 3.5.9 |
| node-disk-manager | 1.8.0 |
| hostpath-provisioner | 0.5.2 |
Compatibility
IOMesh supports servers running on Intel x86_64 and AMD x86_64 architectures.
IOMesh Compatibility
| Software/OS | Compatible Version |
|---|---|
| Kubernetes |
|
| Linux OS |
|