Switch Elasticsearch and Kibana to 5 version
Change-Id: I0e7fe750b177acfdbed0e69efe7c901a328a31ca
diff --git a/.releasenotes/notes/new-classes-es-kibana-59e86910979d52a4.yaml b/.releasenotes/notes/new-classes-es-kibana-59e86910979d52a4.yaml
new file mode 100644
index 0000000..d6e2ecd
--- /dev/null
+++ b/.releasenotes/notes/new-classes-es-kibana-59e86910979d52a4.yaml
@@ -0,0 +1,21 @@
+---
+summary: >
+ Added two new classes for Elasticsearch and Kibana
+
+features:
+ - |
+ Added two new classes to support Elasticsearch v2 and v5 and Kibana
+ v4 and v5.
+ Update the Elasticsearch and Kibana classes in the
+ ``classes/cluster/<cluster_name>/stacklight/server.yml`` file of
+ the Reclass model of your MCP deployment according to the required
+ versions:
+
+ #. For Elasticsearch, change the ``linux.system.repo.elasticsearch`` class
+ to ``linux.system.repo.elasticsearch.2`` or ``linux.system.repo.elasticsearch.5``.
+ To deploy Elasticsearch version 2, specify the ``elasticsearch_version: 2``
+ parameter in the same file.
+ #. For Kibana, change the ``linux.system.repo.kibana`` class to
+ ``linux.system.repo.kibana.4`` or ``linux.system.repo.kibana.5``.
+ To deploy Kibana version 4, specify the ``kibana_version: 4``
+ parameter in the same file.
diff --git a/.releasenotes/notes/switch-es-kibana-to-5-3ef55164a574e066.yaml b/.releasenotes/notes/switch-es-kibana-to-5-3ef55164a574e066.yaml
new file mode 100644
index 0000000..86692c7
--- /dev/null
+++ b/.releasenotes/notes/switch-es-kibana-to-5-3ef55164a574e066.yaml
@@ -0,0 +1,19 @@
+---
+summary: >
+ Updated Elasticsearch and Kibana to versions 5
+
+features:
+ - |
+ Updated Elasticsearch and Kibana to v5. Elasticsearch and Kibana v5
+ are now installed by default.
+
+ To upgrade existing Elasticsearch and Kibana installations to v5,
+ follow the procedures described in the MCP Operations Guide.
+
+ .. TODO: add a link to the upgrade procedure.
+
+ Kibana versions prior to 5.6.x are incompatible with Elasticsearch
+ 5.x. Therefore, once you upgrade Elasticsearch to v5, you must also
+ upgrade Kibana to v5 as described in the MCP Operations Guide.
+
+ .. TODO: add a link to the upgrade procedure.