Hi Tim, It is complementary (as an extension to the core API).
Mohammad
From: Tim Hinrichs <thinri...@vmware.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>,
Date: 01/06/2014 07:35 PM
Subject: [openstack-dev] [neutron] [policy] Complementary or alternative
semantics?
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.
Thanks,
Tim
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<<inline: graycol.gif>>
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
