[openstack-dev] [neutron] [policy] Complementary or alternative semantics?

Mohammad Banikazemi mb at us.ibm.com
Tue Jan 7 04:17:42 UTC 2014

Hi Tim,

It is complementary (as an extension to the core API).


From:	Tim Hinrichs <thinrichs at vmware.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>,
Date:	01/06/2014 07:35 PM
Subject:	[openstack-dev] [neutron] [policy] Complementary or alternative

Over the holidays I realized there's something about the proposed Neutron
policy API that I don't understand.  Is the proposed API complementary to
the core API, or is it intended to be an alternative?  By complementary, I
mean that a user can create a bunch of networks, subnets, and ports and
then constrain how those things interoperate by writing policy.  By an
alternative, I mean that a user must choose either networks/subnets/ports
or policy, but cannot choose both.  I had always assumed we were talking
about a complementary API but wanted to double-check.


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140106/56f53207/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140106/56f53207/attachment.gif>

More information about the OpenStack-dev mailing list