Message-
From: Sumit Naiksatam [mailto:sumitnaiksa...@gmail.com]
Sent: Monday, August 12, 2013 12:24 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] FWaaS: Support for explicit commit
Hi Aaron,
I seemed to have missed this email from you earlier. As compared
Hi Aaron,
I seemed to have missed this email from you earlier. As compared to
existing Neutron resources, the FWaaS Firewall resource and workflow
is slightly different, since it's a two step process. The rules/policy
creation is decoupled (for audit reasons) from its application on the
backend fi
Hi Sumit,
Neutron has a concept of a bulk creation where multiple things can be
created in one api request rather that N (and then be implemented
atomically on the backend). In my opinion, I think it would be better to
implement a bulk update/delete operation rather than a commit. I think that
hav
We had some discussion on this during the Neutron IRC meeting, and per
that discussion I have created a blueprint for this:
https://blueprints.launchpad.net/neutron/+spec/neutron-fwaas-explicit-commit
Further comments can be posted on the blueprint whiteboard and/or the
design spec doc.
Thanks,
~
Hi Sumit,
So all the other Network Services like LBaaS, VPNaaS as well also has
to support implicit and explicit 'Commit' modes for configuration.
It is certainly a good idea to support implicit and explicit modes. It is
good if all the other network services also follows the same.
regards,
ba
On 03/08/13 02:43, Sumit Naiksatam wrote:
Hi All,
In Neutron Firewall as a Service (FWaaS), we currently support an
implicit commit mode, wherein a change made to a firewall_rule is
propagated immediately to all the firewalls that use this rule (via
the firewall_policy association), and the rule
Hi All,
In Neutron Firewall as a Service (FWaaS), we currently support an
implicit commit mode, wherein a change made to a firewall_rule is
propagated immediately to all the firewalls that use this rule (via
the firewall_policy association), and the rule gets applied in the
backend firewalls. This
