Releases: dotmesh-io/dotmesh
Dotmesh release-0.5.2
- dotmesh#305 - Prometheus instrumentation of the Dotmesh server.
- dotmesh#401 - Framework for an upcoming feature, PV-per-node mode in Kubernetes, including a lot of infrastructure to test it in CI!
- dotmesh#418 - Improvements to our CI infrastructure, and a fix to a deletion edge case we found thanks to those improvements.
- dotscience#3 (API BREAKING CHANGE): The Commit API call now accepts arbitrary key=value metadata in the request, and returns the commit ID.
Install instructions: https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.5.1
- Fix #352 - make divergence recovery more reliable
- Make subdot roots writeable by all users to support container images which run as non-root users
- Implement #305 - initial Prometheus instrumentation of dotmesh-server
- Fix #404 - make push/clone/pull more reliable
- Stop spewing binary data into the logs
- Fix #414 - show correct status for branches in
dm dot show - Fix #403 and #416 - stop pushed dots getting stuck in pushPeerState
- Fix #182 - use go1.10 build caching in containerized builds to bring build times down by 3x
- WIP on #401 to implement PV-per-node mode (not tested, documented or enabled by default yet)
- Fix #373 - always show the progress bar even for very fast transfers
Install (docker, kubernetes): https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.5.0
Implemented #344 - Write a basic dotmesh operator that implement our current Daemonset behaviour.
Various stability fixes to state machines, error handling and debug utilities:
#384 - debug dump RPC
#352 - re-convergence after divergence (still a WIP, probably not release-notes-ready yet)
QUICK FIX didn't get an issue - handle "mount" requests in activeState for quicker startup of new dots
#389: Fixed missing error handling in handoffState, curing a possible deadlock
Note specific upgrade instructions for upgrading etcd and etcd operator in this release: https://docs.dotmesh.com/install-setup/upgrading/#dotmesh-0-4-0-5
Install (docker, kubernetes): https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.4.0
Fix #354 - upgrade etcd operator to 0.8.4.
Fix #372 - dm cluster backup-etcd and dm cluster restore-etcd commands to enable backups & restores.
Fix #353 - dm dot show command now shows replication status.
Note specific upgrade instructions for upgrading etcd and etcd operator in this release: https://docs.dotmesh.com/install-setup/upgrading/#dotmesh-0-3-0-4
Install (docker, kubernetes): https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.3.3
Fix #352 - converge diverged branches when replicating
Fix #325 - mask API keys in error messages and logs
Fix #358 - deletion attempts cause deadlock
Fix #86 - support receiving a filesystem that had been deleted
Install (docker, kubernetes): https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.3.2
Fix #339 - intermittent errors when pushing to multi node clusters.
Fix #351 - make dotmesh server logs show up in kubernetes
Fix #303 - make dm cluster init idempotent
Install (docker, kubernetes): https://docs.dotmesh.com/install-setup
Upgrading: https://docs.dotmesh.com/install-setup/upgrading
Dotmesh release-0.3.1
Dotmesh release-0.3.1
Dotmesh is a system for capturing, organizing and sharing application states. The first release of Dotmesh offers support for managing dots on Kubernetes and plain Docker clusters, and interoperability with the Dothub.
This release includes the binary
- dm : The dotmesh client, a git-like CLI for interacting with datadots.
The client can be used to install dotmesh-server, assuming you have Docker installed and your user account has access to the Docker daemon.
$ dm cluster init
This pulls the dotmesh server for this release.
- dotmesh-server : The server-side component for storing datadots. This can be run on individual servers or a cluster.
The dotmesh server also package dynamic provisioner, and flex-volume driver. Dotmesh uses etcd, and ZFS under the hood to manage and store stateful information.
More information on the command line usage, features, installation instructions and concepts can be found at the Dotmesh Docs
Current binaries support OSX and Linux (nixOS, Ubuntu 16.04 LTS and CentOS 7.4).
For more information about product support, team, and blog please head over to https://dotmesh.com/
For a list of current issues
Changes in this version
- dotmesh#317: Improved speed of cloning/pulling from remote clusters
- dotmesh#297: Switch dotmesh port from 6969 to 32607 and switch kubernetes hostPort to nodePort
Dotmesh release-0.3.0
Dotmesh release-0.3.0
Dotmesh is a system for capturing, organizing and sharing application states. The first release of Dotmesh offers support for managing dots on Kubernetes and plain Docker clusters, and interoperability with the Dotmesh Hub.
This release includes the binary
- dm : The dotmesh client, a git-like CLI for interacting with datadots.
The client can be used to install dotmesh-server, assuming you have Docker installed and your user account has access to the Docker daemon.
$ dm cluster init
This pulls the dotmesh server for this release.
- dotmesh-server : The server-side component for storing datadots. This can be run on individual servers or a cluster.
The dotmesh server also package dynamic provisioner, and flex-volume driver. Dotmesh uses etcd, and ZFS under the hood to manage and store stateful information.
More information on the command line usage, features, installation instructions and concepts can be found at the Dotmesh Docs
Current binaries support OSX and Linux (nixOS, Ubuntu 16.04 LTS and CentOS 7.4).
For more information about product support, team, and blog please head over to https://dotmesh.com/
For a list of current issues
Changes in this version
- dotmesh#306: CentOS 7.4 support
- dotmesh#260: Proxy push/pull requests, to support transfers with a multi-node cluster
- dotmesh#263: Support non-default Flexvolume plugin locations, enabling Kubernetes 1.8 in GKE
Dotmesh release-0.2.2
Dotmesh release-0.2.2
Dotmesh is a system for capturing, organizing and sharing application states. The first release of Dotmesh offers support for managing dots on Kubernetes and plain Docker clusters, and interoperability with the Dotmesh Hub.
This release includes the binary
- dm : The dotmesh client, a git-like CLI for interacting with datadots.
The client can be used to install dotmesh-server, assuming you have Docker installed and your user account has access to the Docker daemon.
$ dm cluster init
This pulls the dotmesh server for this release.
- dotmesh-server : The server-side component for storing datadots. This can be run on individual servers or a cluster.
The dotmesh server also package dynamic provisioner, and flex-volume driver. Dotmesh uses etcd, and ZFS under the hood to manage and store stateful information.
More information on the command line usage, features, installation instructions and concepts can be found at the Dotmesh Docs
Current binaries support OSX and Linux (nixOS and Ubuntu 16.04 LTS).
For more information about product support, team, and blog please head over to https://dotmesh.com/
For a list of current issues
Changes in this version
- dotmesh#295: Fix versioning logic when re-releasing.
Dotmesh release-0.2.0
Dotmesh release-0.2.0
Dotmesh is a system for capturing, organizing and sharing application states. The first release of Dotmesh offers support for managing dots on Kubernetes and plain Docker clusters, and interoperability with the Dotmesh Hub.
This release includes the binary
- dm : The dotmesh client, a git-like CLI for interacting with datadots.
The client can be used to install dotmesh-server, assuming you have Docker installed and your user account has access to the Docker daemon.
$ dm cluster init
This pulls the dotmesh server for this release.
- dotmesh-server : The server-side component for storing datadots. This can be run on individual servers or a cluster.
The dotmesh server also package dynamic provisioner, and flex-volume driver. Dotmesh uses etcd, and ZFS under the hood to manage and store stateful information.
More information on the command line usage, features, installation instructions and concepts can be found at the Dotmesh Docs
Current binaries support OSX and Linux (nixOS and Ubuntu 16.04 LTS).
For more information about product support, team, and blog please head over to https://dotmesh.com/
For a list of current issues
Changes in this version
- dotmesh#292: Remove dependency on HostPort networking in Kubernetes
- dotmesh#284: Better logging of flexvolume errors
- dotmesh#290: Fixed upgrade process