Hi, Sachi, Please see my inlined replies.
Also, please refer to this link when you try to integrate OpenStack GBP and ODL GBP: https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack Yapeng From: Sachi Gupta [mailto:sachi.gu...@tcs.com] Sent: Tuesday, January 13, 2015 4:02 AM To: OpenStack Development Mailing List (not for usage questions); groupbasedpolicy-...@lists.opendaylight.org; Yapeng Wu Cc: bu...@noironetworks.com Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver Specs Hi, While working on the integration of Openstack With ODL GBP, I have the below queries: 1. Endpoint-group Create: When I create a new policy-target-group from Openstack say "gbp target-policy-group-create group1", it internally creates a l2.policy which includes the creation of the network and subnet. Meaning creation of EPG will create Network and subnet implicitly in Openstack and also the corresponding EPG, subnet, l3-context, l2-flood-domain, l2-bridge-domain will be created in the ODL GBP. So during the above EPG creation, neutron network and subnet call will come to the neutron northbound of ODL or only to ODL GBP?? [Yapeng] First, when creating policy-target-group, you need to give “provided-policy-rule-sets” or “consumed-policy-rule-sets” parameter. Currently we don’t support policy-target-group update. Second, neutron network and subnet call won’t go to ODL. 1. 1. In ODL, there is no Endpoint create API, instead there is an API to register the endpoints. So what is the sync between the OS and ODL for Endpoint create and register.? [Yapeng] The current working scheme is as follow: ODL GBP has new APIs for openstack-endpoint register and unregister supports. When Openstack GBP creates policy-target, a neutron port will be created by implicit driver, openstack-endpoint register API will be invoked and the OVS tap-port-id will be passed as parameter to ODL GBP. Later when VM is booted, the OVS tap-port-id will be populated on openvswitch, this will trigger ODL to update ovs flow tables.  https://git.opendaylight.org/gerrit/#/c/13554/  https://git.opendaylight.org/gerrit/#/c/13896/ Thanks & Regards Sachi Gupta From: Yapeng Wu <yapeng...@huawei.com> To: "OpenStack Development Mailing List (not for usage questions)" <email@example.com> Date: 01/12/2015 09:01 PM Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver Specs ________________________________ Hello, Sachi, They both works. “End point group” has been renamed to “policy target group”. It is recommended to use “gbp policy-target-group-create”. Yapeng From: Sachi Gupta [mailto:sachi.gu...@tcs.com] Sent: Monday, January 12, 2015 7:03 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver Specs Hi, Can anyone explain the difference between gbp group-create and gbp policy-target-group-create?? I think both these are working same. Thanks & Regards Sachi Gupta From: Sumit Naiksatam <sumitnaiksa...@gmail.com> To: "OpenStack Development Mailing List (not for usage questions)" <firstname.lastname@example.org> Date: 11/26/2014 01:35 PM Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver Specs ________________________________ Hi, This GBP spec is currently being worked on: https://review.openstack.org/#/c/134285/ It will be helpful if you can add "[Policy][Group-based-policy]" in the subject of your emails, so that the email gets characterized correctly. Thanks, ~Sumit. On Tue, Nov 25, 2014 at 4:27 AM, Sachi Gupta <sachi.gu...@tcs.com> wrote: > Hey All, > > I need to understand the interaction between the Openstack GBP and the > Opendaylight GBP project which will be done by ODL Policy driver. > > Can someone provide me with specs of ODL Policy driver for making my > understanding on call flow. > > > Thanks & Regards > Sachi Gupta > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org 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
__________________________________________________________________________ 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