Add missing release notes

Change-Id: If3eb28475d3c124cc1660a3e7ed9790bc4c2c148

releasenotes/notes/add-hostgw-backend-option-1d1f9d8d95ec374f.yaml

@@ -0,0 +1,10 @@
+---
+features:
+  - Add flannel's host-gw backend option. Magnum deploys cluster over a
+    dedicated neutron private network by using flannel. Flannel's host-gw
+    backend gives the best performance in this topopolgy (private layer2) since
+    there is no packet processing overhead, no reduction to MTU, scales to many
+    hosts as well as the alternatives. The label "flannel_use_vxlan" was
+    repurposed when the network driver is flannel. First, rename the label
+    flannel_use_vxlan to flannel_backend. Second, redefine the value of this
+    label from "yes/no" to "udp/vxlan/host-gw".

releasenotes/notes/add-opensuse-driver-f69b6d346ca82b87.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - Add support for a new OpenSUSE driver for running k8s cluster on OpenSUSE.
+    This driver is experimental for now, and operators need to get it from
+    /contrib folder.

releasenotes/notes/bp-auto-generate-name-052ea3fdf05fdbbf.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - Auto generate name for cluster and cluster-template. If users create
+    a cluster/cluster-template without specifying a name, the name will be
+    auto-generated.

releasenotes/notes/bp-barbican-alternative-store-35ec3eda0abb0e25.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - Decouple the hard requirement on barbican. Introduce a new certificate
+    store called x509keypair. If x509keypair is used, TLS certificates will
+    be stored at magnum's database instead of barbican. To do that, set the
+    value of the config ``cert_manager_type`` as ``x509keypair``.

releasenotes/notes/bp-decouple-lbaas-c8f2d73313c40b98.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - Decouple the hard requirement on neutron-lbaas. Introduce a new property
+    master_lb_enabled in cluster template. This property will determines if
+    a cluster's master nodes should be load balanced. Set the value to false
+    if neutron-lbaas is not installed.

releasenotes/notes/bp-magnum-notifications-8bd44cfe9e80f82b.yaml

@@ -0,0 +1,7 @@
+---
+features:
+  - Emit notifications when there is an event on a cluster. An event could be
+    a status change of the cluster due to an operation issued by end-users
+    (i.e. users create, update or delete the cluster). Notifications are sent
+    by using oslo.notify and PyCADF. Ceilometer can capture the events and
+    generate samples for auditing, billing, monitoring, or quota purposes.

releasenotes/notes/bp-mesos-slave-flags-de6cf8c4d2c3c916.yaml

@@ -0,0 +1,7 @@
+---
+features:
+  - >
+      Enable Mesos cluster to export more slave flags via labels in
+      cluster template. Add the following labels: mesos_slave_isolation,
+      mesos_slave_image_providers, mesos_slave_work_dir,
+      and mesos_slave_executor_environment_variables.

releasenotes/notes/fix-global-stack-list-7a3a66169f5c4aa8.yaml

@@ -0,0 +1,10 @@
+---
+security:
+  - Fix global stack list in periodic task. In before, magnum's periodic task
+    performs a `stack-list` operation across all tenants. This is disabled
+    by Heat by default since it causes a security issue. At this release,
+    magnum performs a `stack-get` operation on each Heat stack by default.
+    This might not be scalable and operators have an option to fall back to
+    `stack-list` by setting the config `periodic_global_stack_list` to
+    `True` (`False` by default) and updating the heat policy file (usually
+    /etc/heat/policy.json) to allow magnum list stacks.

releasenotes/notes/remove-container-endpoint-3494eb8bd2406e87.yaml

@@ -0,0 +1,20 @@
+---
+prelude: |
+    Magnum service type and mission statement was changed [1].
+
+    Change service type from "Container service" to "Container Infrastructure
+    Management service". In addition, the mission statement is changed to
+    "To provide a set of services for provisioning, scaling, and managing
+    container orchestration engines."
+
+    The intend is to narrow the scope of the Magnum project to focus on
+    integrating container orchestration engines (COEs) with OpenStack.
+    API features intended to uniformly create, manage, and delete
+    individual containers across any COE will be removed from Magnum's
+    API, and will be re-introduced as a separate project called Zun.
+
+    [1] https://review.openstack.org/#/c/311476/
+upgrade:
+  - All container/pod/service/replication controller operations were removed.
+    Users are recommended to use the COE's native tool (i.e. docker, kubectl)
+    to do the equivalent of the removed operations.