From 403b7c93ea8a3d62faf0f2ff633e0def73c24fc6 Mon Sep 17 00:00:00 2001 From: Ihar Hrachyshka Date: Fri, 24 Feb 2017 08:26:02 +0000 Subject: [PATCH] Added release note for NeutronExternalNetworkBridge deprecation The previous patch [1] that changed the default value for the parameter and that also deprecated the parameter missed a release note. This change fixes the mistake. [1] Iade7fbaf92c8c601227f4456a15ea3f13a907ee2 Change-Id: I72f6f7e50d729734ae6d61191f788ae2aed15145 --- ...-NeutronExternalNetworkBridge-7d42f1a0718da327.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 releasenotes/notes/deprecate-NeutronExternalNetworkBridge-7d42f1a0718da327.yaml diff --git a/releasenotes/notes/deprecate-NeutronExternalNetworkBridge-7d42f1a0718da327.yaml b/releasenotes/notes/deprecate-NeutronExternalNetworkBridge-7d42f1a0718da327.yaml new file mode 100644 index 0000000000..090672967e --- /dev/null +++ b/releasenotes/notes/deprecate-NeutronExternalNetworkBridge-7d42f1a0718da327.yaml @@ -0,0 +1,10 @@ +--- +upgrade: + - The ``NeutronExternalNetworkBridge`` parameter changed its default value + from ``br-ex`` to an empty string value. It means that by default Neutron + L3 agent will be able to serve multiple external networks. (It was always + the case for those who were using templates with the value of the parameter + overridden by an empty string value.) +deprecations: + - The ``NeutronExternalNetworkBridge`` parameter is deprecated and will be + removed in a next release.