Skip to content

v 0.5.0-alpha

Pre-release
Pre-release
Compare
Choose a tag to compare
@GlennBullingham GlennBullingham released this 14 Oct 12:41
v0.5.0
be7eb17

Release Summary

Release Date: 14th October 2020

Mayastor is currently in an early stage of development. This release is considered alpha software. As such, it is not intended for use in production.

New Features:

  • Block Device Discovery - Mayastor instances now expose a gRPC API which is used to enumerate block disk devices attached to the host node, as an aid to the identification of suitable candidates for inclusion within storage Pools during configuration. This functionality is also accessible within the mayastor-client diagnostic utility.

Enhancements:

  • Storage Pool Finalizers - Storage pools are now protected from inadvertent deletion whilst they contain replicas, through the addition of a finalizer to the Pool CRD object by the pool operator when the pool replica count is non-zero.

Bug Fixes:

9 new bugs were identified during testing.
5 bugs closed, resolution "fixed".

As of 15th September 2020, all bugs found by MayaData during internal testing and development are being logged, triaged and resolved directly within the Mayastor GitHub repository, thereby granting visibility to the OpenEBS and Mayastor communities.

Getting Started

The Mayastor quick deployment guide can be found here

Upgrade

Upgrades from previous versions of Mayastor are not supported. Any earlier release should be removed prior to installing this version. For testing purposes, it is preferable to install to a new, clean cluster.

Known Issues

Issue: Some Mayastor custom resource objects may lack status information after creation

Symptom
After creation, the status section of some custom resource objects may be seen to be missing. For example, in the case of a newly declared Mayastor Pool (MSP):

kubectl get -n mayastor get msp
NAME         NODE                                STATE   AGE
diskpool-1   aks-agentpool-41030923-vmss000003           46m

This has also been seen to affect Mayastor Volume (MSV) custom resource objects, which similarly may lack status information after creation and may be unavailable for use as a result.

Workaround
Restart the Mayastor MOAC pod. This can be achieved by deleting the pod, causing k8s to reschedule it in accordance with the moac deployment definition. Affected state information should be restored once MOAC has restarted.

Status
Confirmed bug. A fix for this issue is being targeted for the scheduled 0.6.0 release.

Support

If you are having issues during installation, configuration or upgrade, you can contact us via:

Assets 3
Loading