On develop, there are breaking changes to the etcd key space which is used by the control-plane components and the io-engine to retain information about replicas which contain the correct volume data. An upgrade strategy is yet to be devised, but you may try these steps at your own risk:
- Stop the mayastor-control-plane components.
- When the pool operator is no longer running, remove the finalizers and delete all
MayastorPoolCR's - Enable compatibility mode with the mayastor data replica information
$> ETCDCTL_API=3 etcdctl put "/openebs.io/mayastor/apis/v0/clusters/$KUBE_SYSTEM_UID/namespaces/$NAMESPACE/CoreRegistryConfig/db98f8bb-4afc-45d0-85b9-24c99cc443f2" '{"id":"db98f8bb-4afc-45d0-85b9-24c99cc443f2","registration":"Automatic", "mayastor_compat_v1": true}'
- Move etcd data from
/namespace/$NAMESPACE/control-plane/to/openebs.io/mayastor/apis/v0/clusters/$KUBE_SYSTEM_UID/namespaces/$NAMESPACE/ - Install the new version of mayastor-io-engine and mayastor-control-plane from mayastor-extensions
- Recreate the
MayastorPoolswith the new CRD typeDiskPool
Mayastor is developed under Apache 2.0 license at the project level. Some components of the project are derived from other open source projects and are distributed under their respective licenses.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Mayastor by you, as defined in the Apache-2.0 license, licensed as above, without any additional terms or conditions.