<commit_before>---
date: 2016-10-19T09:00:00+00:00
title: Release notes
---
## Vamp 0.9.1
_19th October 2016_

### What is new
* The biggie: We've added Websockets support to our HTTP API. And we're already using this heavily in our new UI to improve responsiveness and speed. https://github.com/magneticio/vamp/issues/529
* We've updated our UI to a dark theme due to public demand, we love it as it's much easier on the eyes, and of course we're very interested in hearing [your thoughts](mailto:<EMAIL>)!
* You can now configure Vamp to use a key-value store for persistence data storage. By default nothing is set, and thus you need to choose either ElasticSearch or key-value. In our Docker images we use key-value as the persistence data store (`database; type”key-value”`), this can be found in the [Vamp Quickstart configuration](https://github.com/magneticio/vamp/blob/master/bootstrap/src/main/resources/reference.conf). The design reasons for this addition  are less dependencies on elasticsearch, better re-use of the available key-value stores that come with cluster-managers (like Zookeeper in DCOS or etcd in Kubernetes) and more robustness (i.e. if we loose ES the persistence data is still available, only the metrics data is temporarily unavailable). https://github.com/magneticio/vamp/issues/750
* And of course lots of improvements and bug-fixes that can be found here: https://github.com/magneticio/vamp/issues?q=is%3Aissue+milestone%3A0.9.1+is%3Aclosed

### What has changed

* In the [Vamp configuration](/documentation/installation/configure-vamp/#persistence) we set `persistence caching` by default to `false`. In our Vamp images we set this to `true` to make it easier on the persistence store load. https://github.com/magneticio/vamp/issues/792
* We've changed the updating deployment service states. https://github.com/magneticio/vamp/issues/797
* **BREAKING CHANGE**: In the Vamp configuration the “rest-api” section has changed to “http-api”. When running Vamp 0.9.1 you need to change this setting accordingly. NB REST and websockets are both a part of our HTTP API. Check this [Vamp configuration](https://github.com/magneticio/vamp/blob/master/bootstrap/src/main/resources/reference.conf) example.

## Vamp 0.9.0 Beta release
_9th September 2016_

The Vamp 0.9.0 release is a very important milestone in the lifecycle of Vamp, as we're removing the Alpha label and are moving to Beta! This means that we will do our utmost best to avoid breaking changes in our API's and DSL, focus even more on stabilising and optimising the current feature-set, while of course continuously introducing powerful new features.

The Vamp 0.9.0 release is the culmination of three months of hard work by our amazing team! This release incorporates nothing less than 115 issues and I'm very proud of what we've achieved.

![Vamp 0.9.0 UI](/images/screens/vamp_UI_090.png)

Some of the most notable new features are:

* a brand new opensource UI with much better realtime graphs, sparklines, info, events panel and access to all relevant API objects like breeds, deployments but also new options like gateways and workflows.  
* powerful integrated workflows for automation and optimisation like autoscaling, automated canary-releasing etc. using efficient Javascript-based scripting.
* Kubernetes and Rancher support.
* support for custom virtual host names in gateways.
* support for custom HAProxy templates.
* a brand new Vamp Runner helper application for automated integration testing, mocking scenarios and educational purposes.  

And, of course, there's a massive amount of improvements, bug fixes and other optimisations.
<commit_msg>updated release notes<commit_after>---
date: 2016-10-19T09:00:00+00:00
title: Release notes
---
## Vamp 0.9.1
_19th October 2016_
### What has changed
* **BREAKING CHANGE**: In the Vamp configuration the “rest-api” section has changed to “http-api”. When running Vamp 0.9.1 you need to change this setting accordingly. NB REST and websockets are both a part of our HTTP API. Check this [Vamp configuration](https://github.com/magneticio/vamp/blob/master/bootstrap/src/main/resources/reference.conf) example.
* In the [Vamp configuration](/documentation/installation/configure-vamp/#persistence) we set `persistence caching` by default to `false`. In our Vamp images we set this to `true` to make it easier on the persistence store load. https://github.com/magneticio/vamp/issues/792
* We've changed the updating deployment service states. https://github.com/magneticio/vamp/issues/797

### What is new
* The biggie: We've added Websockets support to our HTTP API. And we're already using this heavily in our new UI to improve responsiveness and speed. https://github.com/magneticio/vamp/issues/529
* We've updated our UI to a dark theme due to public demand, we love it as it's much easier on the eyes, and of course we're very interested in hearing [your thoughts](mailto:<EMAIL>)!
* You can now configure Vamp to use a key-value store for persistence data storage. By default nothing is set, and thus you need to choose either ElasticSearch or key-value. Take a look at the [Vamp Quickstart configuration](https://github.com/magneticio/vamp/blob/master/bootstrap/src/main/resources/reference.conf) for possible settings. The design reasons for this addition  are less dependencies on elasticsearch, better re-use of the available key-value stores that come with cluster-managers (like Zookeeper in DCOS or etcd in Kubernetes) and more robustness (i.e. if we loose ES the persistence data is still available, only the metrics data is temporarily unavailable). Possible issues might be the performance of the key-value store. https://github.com/magneticio/vamp/issues/750
* And of course lots of improvements and bug-fixes that can be found here: https://github.com/magneticio/vamp/issues?q=is%3Aissue+milestone%3A0.9.1+is%3Aclosed

## Vamp 0.9.0
_9th September 2016_

The Vamp 0.9.0 release is a very important milestone in the lifecycle of Vamp, as we're removing the Alpha label and are moving to Beta! This means that we will do our utmost best to avoid breaking changes in our API's and DSL, focus even more on stabilising and optimising the current feature-set, while of course continuously introducing powerful new features.

The Vamp 0.9.0 release is the culmination of three months of hard work by our amazing team! This release incorporates nothing less than 115 issues and I'm very proud of what we've achieved.

![Vamp 0.9.0 UI](/images/screens/vamp_UI_090.png)

Some of the most notable new features are:

* a brand new opensource UI with much better realtime graphs, sparklines, info, events panel and access to all relevant API objects like breeds, deployments but also new options like gateways and workflows.  
* powerful integrated workflows for automation and optimisation like autoscaling, automated canary-releasing etc. using efficient Javascript-based scripting.
* Kubernetes and Rancher support.
* support for custom virtual host names in gateways.
* support for custom HAProxy templates.
* a brand new Vamp Runner helper application for automated integration testing, mocking scenarios and educational purposes.  

And, of course, there's a massive amount of improvements, bug fixes and other optimisations.

{'fraction_non_alphanumeric': 0.07049787409134549, 'fraction_numerical': 0.01947606638321218, 'mean_word_length': 4.692427790788447, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 14, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6872858', 'n_tokens_mistral': 2067, 'n_tokens_neox': 1865, 'n_words': 958}