Sean, I agreed with you. But after I read Yan's user case. I think the FWaaS API may become too complex for that case.
By extending security group is better option. On Thu, Jul 16, 2015 at 11:48 AM, Sean M. Collins <s...@coreitpro.com> wrote: > On Tue, Jul 14, 2015 at 03:31:49AM PDT, Kevin Benton wrote: > > Unfortunately the security groups API does not have mac-level rules right > > now. > > There is also the fact that the Security Group API is limited (by > design) to do fairly simple things, and also that the model has similar > fields to the AWS API for Security Groups. > > Overall, I want to try and minimize (or even avoid) any changes to the > Security Group API, and try and collect usecases for more complex > filtering to see if the FwaaS API can satisfy - since it is an API that > we have more freedom to change and modify compared to an API that is > named the same as something in AWS - and it is meant for more complex > usecases. > > http://lists.openstack.org/pipermail/openstack-dev/2015-June/068319.html > -- > Sean M. Collins > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
