Hwameistor Release Notes¶
This page lists the Release Notes related to Hwameistor, so that you can understand the evolution path and feature changes of each version.
2023-4-30¶
v0.9.3¶
Optimization¶
- Optimized Populate disk owner information during use phase
- Optimized Merge the properties of the disk itself when the udev event is triggered
- Optimized Add tags to svc
- Optimized Separate disk allocation and disk status update process
- Optimized Rename the Exportor port to http-metrics
- Optimized Add port name in exporter service
Fixes¶
- Fixed LD bound, but no capacity in LSN
- Fixed Metrics port listening issue
- Fixed May occur
not found
issue - Fixed UI tag issue in Helm
2023-3-30¶
v0.9.2¶
Optimization¶
- Added UI relok8s
v0.9.1¶
Optimization¶
- Added Volume Status monitoring Issue#741
- Fixed Local Storage deployment parameter Issue #742
v0.9.0¶
Features¶
- Added Disk Owner Issue #681
- Added Grafana DashBoard Issue #733
- Added Operator installation method, automatically pull UI when installing Issue #679
- Added UI application Label Issue #710
Optimization¶
- Added disk used capacity Issue #681
- Optimized Skip scoring mechanism when no available disk is found Issue #724
- Set DRDB port defaults to 43001 Issue #723
2023-1-30¶
v0.8.0¶
Optimization¶
- Optimized Chinese documentation
- optimized value.yaml file
- Optimized Roadmap
- Optimized When the installation fails, set the default failure policy
2022-12-30¶
v0.7.1¶
Features¶
-
Added Hwameistor DashBoard UI, which can display the usage status of storage resources and storage nodes.
-
Added interface to manage Hwameistor storage nodes, local disks, and migration records.
-
Added storage pool management function, which supports the interface to display the basic information of the storage pool and the corresponding node information of the storage pool.
-
Added local volume management function, which supports the interface to perform data volume migration and high availability conversion.
Optimization¶
- Optimized Unnecessary logs before data migration, and avoid the impact of Job execution under other Namespaces.