v 0.4.0-alpha
Pre-releaseRelease Summary
Release Date: 18th September 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:
- Enhanced User Documentation - The previous user quickstart guide has been updated and extended, and is now hosted on GitBook. This new content deprecates the README.md file in the /deploy directory of the Mayastor repository. GitBook will be the principle repository of Mayastor user documentation during this phase of development.
- k3s Support - Mayastor may be deployed on kubernetes clusters built using the lightweight k3s distribution
Enhancements:
- Rebuild Restart Tolerance - If one or more children of a Nexus are either pending, or undergoing, rebuild this process this will now resume automatically upon a restart of the Mayastor pod hosting that nexus. Child state will be correctly deduced on restart.
- Nexus I/O Internal Retry - In the event that an I/O operation directed at the child of a nexus fails, the nexus will internally queue and retry (attempt count is configurable) instead of immediately returning an error to the consuming application container via the front-end target. This isolates the application from the effects of transient events e.g. temporary losses of connectivity.
- Pool Auto-naming - As a convenience to the user, if no value is specified in the
name
field of a Mayastor Pool (MSP) declaration, a unique name will be generated automatically during pool creation.
Bug Fixes:
14 new bugs were identified during testing.
16 bugs closed, resolution "fixed".
From 15th September 2020, all bugs found by MayaData during internal testing and development will be 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: Mayastor Pool (MSP) custom resource objects may lack status information after creation
Symptom
After creating a new pool definition the status section of the MayastorPool custom resource is missing. For example:
kubectl get -n mayastor get msp
NAME NODE STATE AGE
diskpool-1 aks-agentpool-41030923-vmss000003 46m
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. Pool state information should be available once MOAC has restarted.
Status
Confirmed bug
Support
If you are having issues during installation, configuration or upgrade, you can contact us via:
- OpenEBS on Kubernetes Slack community
- Already signed up? Head to our discussions at #openebs
- Raising an issue