From e2ea1e36c6e1c7788cf3c6bc74678988c911f629 Mon Sep 17 00:00:00 2001 From: Nate Johnston Date: Wed, 7 Sep 2016 19:17:46 +0000 Subject: [PATCH] Add reno note for FWaaS v2 None of the existing release notes mention FWaaS v2, so a separate release note is being added to debut it and describe the extent of its implementation. Change-Id: Iba874d49591f2f37a8623c1910cfcbb68634fa2f --- .../notes/fwaas_v2-374471c215af0ca0.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 releasenotes/notes/fwaas_v2-374471c215af0ca0.yaml diff --git a/releasenotes/notes/fwaas_v2-374471c215af0ca0.yaml b/releasenotes/notes/fwaas_v2-374471c215af0ca0.yaml new file mode 100644 index 000000000..577d1a2d7 --- /dev/null +++ b/releasenotes/notes/fwaas_v2-374471c215af0ca0.yaml @@ -0,0 +1,18 @@ +--- +prelude: > + The FWaaS team is pleased to release FWaaS v2.0. This release of FWaaS + supports either the original FWaaS v1 or the new FWaaS v2. +features: + - In FWaaS v2 firewall policies are applied to router ports, as opposed to + applying to routers in FWaaS v1. + - Earlier the FWaaS agent integrated with the L3 agent by having the L3 Agent + class inherit from the FWaaS Agent class. This meant that other service + agents could not also integrate with the L3 agent. Now, using the L3 agent + extensions mechanism, FWaaS (v1 and v2) plugs in to the L3 agent. This + means that it can interoperate peacefully with other L3 advanced services + that also implement the L3 agent extension mechanism, all without any code + changes to Neutron. +upgrade: + - There is not currently a defined upgrade path from FWaaS v1 to FWaaS v2. + - FWaaS v1 can not be enabled at the same time as FWaaS v2; one or the other + must be chosen.