17:00:03 #startmeeting gbp_status_arch 17:00:03 Meeting started Fri Mar 13 17:00:03 2015 UTC. The chair is tbachman. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:03 The meeting name has been set to 'gbp_status_arch' 17:00:06 #chair alagalah 17:00:06 Current chairs: alagalah tbachman 17:00:12 #topic agenda 17:01:16 #link https://meetings.opendaylight.org/opendaylight-group-policy/2015/gbp_status_arch/opendaylight-group-policy-gbp_status_arch.2015-02-27-18.02.html Minutes from last week’s meeting 17:03:32 #topic Trello 17:10:51 #info alagalah, martin_sunal, and others have been working on the neutron provider 17:11:02 #info Worked out a lot of the mappings, but still some more work to be done 17:11:53 #info yapeng moved the port name from openstack-endpoint renderer to the generic endpoint; moved the URI in openstack, and changed the port name 17:12:10 #info yapeng says the code has been merged to the master branch, for kilo, and will be back-ported to the Juno branch 17:12:32 #info yapeng says both openstack-gbp and regular gpb were validated against yapeng’s work 17:12:55 #info Sanjay asks if the augmentation for the port has been added to the northbound 17:13:03 #info alagalah says he’ll address that in a minute 17:13:28 #info yapeng says from the openstack side, the change has been completed and merged — hoping to be completed/approved by the end fo the day 17:14:31 #info alagalah says that having this back-ported to Juno will allow us to remove the old openstack-gbp code from ODL 17:14:44 yapeng: great job! :) 17:15:55 #info alagalah says that we’re still in the same state with port-name — we didn’t want to break what yapeng was working on; alagalah saw the patch to change the port name and will try to look at it over the weekend 17:17:17 #info alagalah has added support for EPs being in multiple EPGs, but there are lots of implications; control plane part is done, data plane still being worked on 17:17:52 #info alagalah says when an EP was only part of a single EPG, network containment was simple — defined by EPG; with multi-EPG, this is defined by the EP. 17:29:38 #info Sanjays asks about moving network location from Endpoint 17:31:14 #info alagalah says the EPG’s NetworkDomainID is more generic — the EP has an L2 and L3 context 17:51:07 #info alagalah introduces the architecture proposed for multi-EPG support 17:51:40 #info alagalah says that the EP will be able to specify the network domain, which would override the network domain in the EPG; this is important when an EP can belong to mulitple EPGs 17:52:05 #info Sanjay asks what can be done when an EP doesn’t have a network domain — doesn’t want to touch a bunch of EPs in order to update a domain 17:52:16 #info alagalah says this is being looked at — not sure of the specifics just yet 17:52:42 #info alagalah says this could be handled by a network domain EPG 18:07:57 #endmeeting