<div dir="ltr">CC'ed ODL GBP --- although this doesn't concern them at this point, it may be of interest to the team<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 26, 2014 at 12:10 AM, Sachi Gupta <span dir="ltr"><<a href="mailto:sachi.gupta@tcs.com" target="_blank">sachi.gupta@tcs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Hi All,</font>
<br>
<br><font face="sans-serif">Request you all to provide inputs of
the below queries:</font>
<br>
<ul>
<li><font face="sans-serif">As per my understanding GBP constructs
are mapped to neutron calls for example - creating an endpoint, the neutron
mapping driver will map it to the existing port creation method. Similarly
to achieve the complete functionality of GBP openstack, I have checked
for the neutron calls and it includes network, subnet, port, router, security
group.</font></li></ul></blockquote><div> Correct.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<ol>
<li value="1"><font face="sans-serif">Creating a contract - policy
rules..Will this include a call to firewall rules or only security group
calls will be done?</font></li></ol></blockquote><div> At this point, only security group calls.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><ol><li value="1">
</li><li value="2"><font face="sans-serif">I need to integrate Openstack
with Opendaylight(ODL). To achieve the interface between two will it be
done by ML2 plugin and neutron mapping driver of Openstack or something
additional is required?</font></li></ol></blockquote><div><br></div><div> That should be enough. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><ol><li value="2">
</li><li value="3"><font face="sans-serif">The neutron northbound APIs
of ODL include network, subnet, port, router, security groups, firewall
calls. Any other call that needs to be included a part from these in ODL.</font></li></ol></blockquote><div><br></div><div> Even FWaaS APIs are supported in ODL now? If so, I guess ODL is even ready to do (basic) 'redirect' action once it is implemented on the mapping driver then.</div><div><br></div><div> And no, you should not need any other APIs.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><ol><li value="3">
</li><li value="4"><font face="sans-serif">Do the neutron calls that will
be mapped by the neutron mapping driver of openstack are something different
from the previous neutron calls that were being made without using GBP???
For example: The network create call that was used previously with ODL
without using GBP in openstack. Will it be different from the network call
to ODL that will be made by GBP mapping driver of openstack.</font></li></ol></blockquote><div> No. The intent of mapping driver is to allow network policies to be rendered by current Neutron plugins. So the ODL calls should NOT be any different from before, the magic happens in the mapping driver layer. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><ol><li value="4">
</li><li value="5"><font face="sans-serif">How the GBP project in openstack
will be affecting the Opendaylight neutron calls??</font></li></ol></blockquote><div><br></div><div> It doesn't. That said, I fully expect the ODL Neutron handling layer to support GBP APIs in the (near) future. When that happens, instead of using the mapping driver, you will have an additional choice of using the ODL GBP driver.</div><div><br></div><div>Hope it helps,</div><div>- Stephen</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><font face="sans-serif"><br>
<br>
Thanks in Advance<br>
Sachi Gupta<br>
</font>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">Sumit Naiksatam <<a href="mailto:sumitnaiksatam@gmail.com" target="_blank">sumitnaiksatam@gmail.com</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif">"OpenStack Development
Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">09/23/2014 04:33 AM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [openstack-dev]
Group-Based Policy Understanding and Queries</font>
<br>
<hr noshade><div class="HOEnZb"><div class="h5">
<br>
<br>
<br><tt><font>Thanks for your interest in GBP, responses inline.<br>
<br>
On Sun, Sep 21, 2014 at 11:35 PM, Sachi Gupta <<a href="mailto:sachi.gupta@tcs.com" target="_blank">sachi.gupta@tcs.com</a>>
wrote:<br>
> Hi All,<br>
><br>
> Request you all to provide inputs on below understanding:<br>
><br>
> Openstack: Group-based policy is a blueprint for Juno-3 release of<br>
> Openstack. It will extend OpenStack Networking with policy and connectivity<br>
> abstractions that enable significantly more simplified and<br>
> application-oriented interfaces than with the current Neutron API
model.<br>
> When will be the code ready for Group-based policy as an open source?<br>
<br>
The code has been in review in gerrit for a while now, you can find<br>
all the links to all the patches here:<br>
</font></tt><a href="https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches" target="_blank"><tt><font>https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches</font></tt></a><tt><font><br>
We are also consolidating this code in Stackforge so that its usable<br>
starting from the Juno release.<br>
<br>
> Openstack group policy API will be an extension to the Neutron APIs.
There<br>
> will be a policy manager to manage the policy and policy rules. Will
GBP a<br>
> part of neutron?? If yes, then will GBP be a part of Horizon under
neutron?<br>
<br>
The wiki page above has links to client, Horizon and Heat patches.<br>
<br>
> Policy driver which will act as an interface(ODL Policy Driver). For
eg. we<br>
> used neutron ML2 plugin as an interface between Openstack neutron
and ODL<br>
> neutron northbound. When will the policy driver for ODL available?<br>
> Openstack policy driver for ODL will act as an interface to ODL. Which
API<br>
> in ODL, Policy calls from Openstack ODL Policy driver will be hitting??<br>
><br>
<br>
I know that this was planned, so you would probably need to check with<br>
the author of the following patch for the status on this:<br>
</font></tt><a href="https://review.openstack.org/#/c/105606/" target="_blank"><tt><font>https://review.openstack.org/#/c/105606/</font></tt></a><tt><font><br>
We can also bring this up for discussion during the weekly IRC:<br>
</font></tt><a href="https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy" target="_blank"><tt><font>https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy</font></tt></a><tt><font><br>
<br>
><br>
><br>
> Thanks & Regards<br>
> Sachi Gupta<br>
><br>
> =====-----=====-----=====<br>
> Notice: The information contained in this e-mail<br>
> message and/or attachments to it may contain<br>
> confidential or privileged information. If you are<br>
> not the intended recipient, any dissemination, use,<br>
> review, distribution, printing or copying of the<br>
> information contained in this e-mail message<br>
> and/or attachments to it are strictly prohibited. If<br>
> you have received this communication in error,<br>
> please notify us by reply e-mail or telephone and<br>
> immediately and permanently delete the message<br>
> and any attachments. Thank you<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>
</font></tt>
<br></div></div><br>_______________________________________________<br>
controller-dev mailing list<br>
<a href="mailto:controller-dev@lists.opendaylight.org">controller-dev@lists.opendaylight.org</a><br>
<a href="https://lists.opendaylight.org/mailman/listinfo/controller-dev" target="_blank">https://lists.opendaylight.org/mailman/listinfo/controller-dev</a><br>
<br></blockquote></div><br></div></div>