<html><body>
<p><tt><font size="2">Stephen Wong <s3wong@midokura.com> wrote on 12/15/2013 12:00:32 PM:<br>
<br>
> From: Stephen Wong <s3wong@midokura.com></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> Date: 12/15/2013 12:04 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [neutron] [policy] Policy-group relationship</font></tt><br>
<tt><font size="2">> <br>
> Hi Mohammad,<br>
> <br>
> Good writeup, one minor comment at the end below (look for [s3wong]).<br>
> <br>
> On Thu, Dec 12, 2013 at 3:42 PM, Mohammad Banikazemi <mb@us.ibm.com> wrote:<br>
> > Continuing the discussion we had earlier today during the Neutron Group<br>
> > Policy weekly meeting [0], I would like to initiate a couple of email<br>
> > threads and follow up on a couple of important issues we need to agree on so<br>
> > we can move forward. In this email thread, I would like to discuss the<br>
> > policy-group relationship.<br>
> ><br>
> > I want to summarize the discussion we had during the meeting [1] and see if<br>
> > we have reached an agreement:<br>
> ><br>
> > There are two models for expressing the relationship between Groups and<br>
> > Policies that were discussed:<br>
> > 1- Policies are defined for a source Group and a destination Group<br>
> > 2- Groups specify the Policies they "provide" and the Policies they<br>
> > "consume"<br>
> ><br>
> > As expressed during the IRC meeting, both models have strong support and we<br>
> > decided to have a resource model that can be used to express both models.<br>
> > The solution we came up with was rather simple:<br>
> ><br>
> > Update the resource model (shown in the attribute tables and the taxonomy in<br>
> > the google doc [2]) such that policy can refer to a "list" of source Groups<br>
> > and a "list" of destination Groups.<br>
> > This boils down to having two attributes namely, src_groups and<br>
> > destination_groups (both list of uuid-str type) replacing the current<br>
> > attributes src_group and dest_group, respectively.<br>
> ><br>
> > This change simply allows the support for both models. For supporting model<br>
> > 1, specify a single source Group and a single destination Group. For model<br>
> > 2, specify the producers of a Policy in the source Group list and specify<br>
> > the consumers of the Policy in the destination Group list.<br>
> <br>
> [s3wong] this is interesting. Let's say we have two groups A & B, and<br>
> A wants to send traffic to B, so in this case, B is providing a policy<br>
> which A will consume. In your proposal above, I would have to put A in<br>
> destination group list and B in source group list although the traffic<br>
> direction is the reverse. Would that cause a bit of a confusion?<br>
> </font></tt><br>
<br>
<tt><font size="2">Yeah, that's a good point. Producers are the destination of traffic flows.</font></tt><br>
<tt><font size="2">So should we have them under destination group? Even that is a bit confusing.</font></tt><br>
<tt><font size="2">May be we need different names for the two groups.</font></tt><br>
<br>
<tt><font size="2">-Mohammad</font></tt><br>
<tt><font size="2"><br>
> Thanks,<br>
> - Stephen<br>
> <br>
> <br>
> ><br>
> > If there is agreement, I will update the taxonomy and the attribute tables<br>
> > in the doc.<br>
> ><br>
> > Best,<br>
> ><br>
> > Mohammad<br>
> ><br>
> ><br>
> > [0] <a href="https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy">https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy</a><br>
> > [1]<br>
> > <a href="http://eavesdrop.openstack.org/meetings/networking_policy/2013/">http://eavesdrop.openstack.org/meetings/networking_policy/2013/</a><br>
> networking_policy.2013-12-12-16.01.log.html<br>
> > [2]<br>
> > <a href="https://docs.google.com/document/d/">https://docs.google.com/document/d/</a><br>
> 1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit#heading=h.x1h06xqhlo1n<br>
> > (Note the new additions are at the end of the document.)<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > OpenStack-dev@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
</font></tt></body></html>