commit 97b532c9725937ae441ba088284cee9c13e7e1e6
Author: wu.chunyang <wuchunyang@yovole.com>
Date:   Sun Aug 16 21:09:29 2020 +0800

    add releasenote for octavia configuration
    
    Change-Id: Ic3faf90ef7aea1c506e113fe77f62d916d1b118b
    Implements: blueprint implement-automatic-deploy-of-octavia

diff --git a/releasenotes/notes/automatic-deploy-of-octavia-efe94f4db86d9106.yaml b/releasenotes/notes/automatic-deploy-of-octavia-efe94f4db86d9106.yaml
new file mode 100644
index 0000000..f316e7b
--- /dev/null
+++ b/releasenotes/notes/automatic-deploy-of-octavia-efe94f4db86d9106.yaml
@@ -0,0 +1,17 @@
+---
+features:
+  - |
+    Adds support for automatic registration resources required for Octavia.
+    This includes a management network and subnet, security groups, flavor
+    and SSH key. The amphora image must be uploaded manually currently.
+    `BP#automatic-deploy-of-octavia
+    <https://blueprints.launchpad.net/kolla-ansible/+spec/implement-automatic-deploy-of-octavia>`__
+  - |
+    Adds support for automatic generation of certificates for Octavia via the
+    ``kolla-ansible octavia-certificates`` command.
+upgrade:
+  - |
+    Resources required for Octavia are now registered automatically by
+    default. Octavia users upgrading from Ussuri should set
+    ``octavia_auto_configure`` to ``no`` in ``globals.yml`` to avoid
+    registering conflicting resources.