15:03:36 <tbachman> #startmeeting gbp_status_arch
15:03:36 <odl_meetbot> Meeting started Wed Aug 12 15:03:36 2015 UTC.  The chair is tbachman. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:03:36 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:36 <odl_meetbot> The meeting name has been set to 'gbp_status_arch'
15:03:40 <tbachman> #chair alagalah
15:03:40 <odl_meetbot> Current chairs: alagalah tbachman
15:03:57 <tbachman> #topic Agenda bashing/roll call
15:04:02 <tbachman> #info committers please #info in
15:04:05 <tbachman> #info tbachman
15:04:16 <alagalah> #info alagalah
15:04:37 <tbachman> #link https://lists.opendaylight.org/pipermail/groupbasedpolicy-dev/2015-August/001303.html email from alagalah with today’s agenda
15:04:51 <tbachman> #link https://meetings.opendaylight.org/opendaylight-group-policy/2015/gbp_status_arch/opendaylight-group-policy-gbp_status_arch.2015-08-05-15.00.html minutes from last week’s meeting
15:05:47 <tbachman> #topic Beryllium release planning
15:06:02 <tbachman> #undo
15:06:02 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1c3f8d0>
15:06:14 <tbachman> #topic Stable Lithium Updates
15:07:40 <tbachman> #info alagalah says the focus of the current work is on stability — CSIT standup for GBP/SFC, clustering support, etc.
15:09:36 <tbachman> #info alagalah says that a lot of the team has done a great job of adding unit tests (kinsey, kblagov, tomas_c|2, et. al.) and CSIT (tomas_c|2, kblagov, et. al.)
15:10:27 <tbachman> #info alagalah says after CSIT, we’re creating documentation, to help folks understand things like the robot framework
15:10:47 <tbachman> #info alagalah says we’re looking at adding the GBP neutron pieces into an OPNFV project
15:11:42 <tbachman> #info alagalah says an endgoal is to be able to test upstream openstack against the GBP neutron integration
15:12:49 <tbachman> #info alagalah says multinode testing done by tomas_c|2 will be a big help
15:15:10 <alagalah> #topic Stable Lithium updates - Thomas Demo of how cool the demo env is without restarting controller
15:16:10 <alagalah> #info tbachman Is showing the standard 6 node GBPSFC demo with ODL running on his laptop (not in the demo VMs)
15:17:50 <alagalah> #info Doing a demo of asymmetric chain
15:21:48 <alagalah> #info showed the traffic working, then runs ./cleandemo.sh which removes the Datastore and Network element data
15:21:58 <alagalah> #info then runs the standalone GBP demo
15:22:33 <martin_sunal> #info martin_sunal
15:30:06 * tbachman waves to martin_sunal
15:30:37 <tbachman> #info alagalah says that the SFC project has different scheduling algorithms; GBP isn’t leveraging this at the moment, but could with some small modifications
15:31:10 <tbachman> #info alagalah says the RSP is referenced by name, so we could come up with a naming convention to use to enable this
15:32:22 <tbachman> #info alagalah is trying to modify the GBPSFC demo so that SFs can be put in docker containers
15:33:34 <martin_sunal> hey tbachman, how are you?
15:34:10 <tbachman> martin_sunal: :)
15:35:03 <tbachman> #topic Beryllium release planning
15:35:22 <tbachman> #link https://docs.google.com/document/d/1NZPhsEccY5lBOXI0v1uygE0Y_iIjCjRNcs27H4e4CMw/edit?usp=sharing Brainstorming document for Beryllium release planning
15:35:38 <tbachman> #link https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Beryllium GBP Beryllium release plan
15:36:11 <tbachman> #link https://trello.com/b/fDQss8ez/odlgbp-beryllium Trell board for GBP Beryllium release
15:36:50 <tbachman> #info alagalah says we have until September 3rd to get the final release plan completed
15:38:44 <tbachman> #info alagalah says code freeze is in December
15:40:20 <tbachman> #info alagalah says that anything modeled in YANG can be exposed to the outside world via REST
15:41:16 <tbachman> #info alagalah says that navigating the full model can be daunting — led to discussion of how to map DSL from northbound into the model
15:44:29 <tbachman> #info alagalah says this allows us to keep domain specifics in a dictionary — allowing for DSL mappings
15:44:51 <tbachman> #info alagalah says this has implications into the UX — how do we expose this to the user
15:45:53 <tbachman> #info alagalah says we could potentially use yang-ui as a means of enabling this type of “expert-mode”
15:48:07 <tbachman> #info yapeng asks if the neutron northbound would become a consumer of this expert-mode
15:48:38 <tbachman> #info alagalah says it’s actually the opposite — our contract with NN is to map the interfaces it exposes
15:49:38 <tbachman> #info yapeng asks who would use the new API
15:49:48 <tbachman> #info alagalah says anyone using ODL GBP for Neutron
15:52:04 <tbachman> #info alagalah says the core engine should  have no domain specifics in it
15:52:58 <tbachman> #info alagalah says we need to separate the forwarding and access models into different files
15:53:30 <tbachman> #info alagalah says the forwarding model is in the main GBP project, and there is no alternate forwarding model; this precludes others from easily adding new forwarding models
15:59:53 <yapeng> Is ODL having statistics collection project?
16:00:03 <tbachman> yapeng: I think the TSDR project does that
16:00:11 <tbachman> Not sure how comprehensive it is
16:00:17 <yapeng> thanks, i will take a look
16:00:20 <tbachman> np!
16:01:04 <tbachman> #info alagalah says anyone wishing to contribute should start with our wiki page (also see Trello board)
16:02:04 <yapeng> what is needed to meet Release plan on Sept 3rd? Does it require a detailed design?
16:02:54 <tbachman> yapeng: we have to declare the features we plan on delivering
16:03:01 <tbachman> that’s the big one
16:03:13 <yapeng> ok, thanks!
16:03:19 <tbachman> np!
16:03:41 <tbachman> #info alagalah will be at LinuxCon next week - will try to kick off discussion on the ML for the Beryllium release
16:03:43 <tbachman> #endmeeting