16:08:37 <alagalah> #startmeeting GBP Policy Repo
16:08:37 <odl_meetbot> Meeting started Mon Apr 28 16:08:37 2014 UTC.  The chair is alagalah. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:08:37 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:08:37 <odl_meetbot> The meeting name has been set to 'gbp_policy_repo'
16:09:51 <alagalah> #info Rob Adams has been blocked due to issues with how YANG/MD-SAL works, and the code generation.. net-net it took more time than he anticipated
16:11:25 <alagalah_> #info readams is sharing on ghangout his preliminary yang model. This has not been pushed to the repo (we are still getting our Jenkins environment up etc etc... so COMMITs not yet possible)
16:11:54 <alagalah_> #info filename is endpoint.yang
16:12:53 <alagalah_> #info readams says his yang is a simple database of all the endpoints stored in the registry, and replicating APIC, there are two copies of every endpoint, 1 keyed my L2 namespace and MAC and 1 keyed by L3 namespace and IP
16:13:58 <alagalah_> #info Renderers/Or anything that knows about endpoints, are responsible for writing endpoint information to the repository. Or anything exernal like OpenStack that knows endpoints that could write into it.
16:14:15 <alagalah_> #info using an RPC call that understands it has to write to both places with a timestamp (for consistency)
16:14:58 <alagalah_> #info L2/3 namespace id, tenant id, group id, condition id... L3 address = namespace+IP addr tuple
16:15:14 <alagalah_> #info implemented as a LIST
16:15:43 <alagalah_> #info keyed by L2 address (ie namespace + MAC) and similarly for L3 address (ie namespace + IP ADDR)
16:15:57 <alagalah_> #info has RPCs "registerEndpoint" and "unregisterEndpoint"
16:17:15 <alagalah> #info this is a preliminary strawman
16:17:22 <alagalah> #info some of the MD-SAL examples on the wiki (ie Toaster) do not work as advertised, which the MD-SAL team is aware of and is working towards fixing
16:17:40 <alagalah> #info will implement sharding once that code appears
16:17:47 <alagalah> #info hemanth....
16:17:54 <alagalah> hemanthravi: can you #info your question
16:17:57 <alagalah> I couldn't hear you
16:18:25 <hemanthravi> #info does the generated code have methods to store/access from the md-sal data-store
16:18:38 <hemanthravi> #info or do you need to need to fill in the methods
16:18:38 <alagalah> #info readams answers hemanthravi question (couldn't pick it up) but is talking about instanceIDs as key into tree
16:19:17 <alagalah> #info readams not sure if there is enforcement of endpoint containing key data.... may need validation code when renderer writes? Or ensure that renderers are always part of GBP and hence part of a controlled architecture
16:19:50 <alagalah> #info readams feels that we may need a wrapper API around the generated API ...
16:20:56 <alagalah_> #info alagalah feels we should work with the MD-SAL team to ensure that the generated APIs are useful, as ideally we shouldn't use wrappers.
16:20:57 <alagalah_> #info alagalah feels we should work with the MD-SAL team to ensure that the generated APIs are useful, as ideally we shouldn't use wrappers.
16:21:41 <alagalah_> #topic Who can contribute code and how much time?
16:21:57 <hemanthravi> #info i'll get back on this later today
16:22:03 <hemanthravi> reg the amount of time
16:22:07 <readams> #topic Who can contribute code and how much time?
16:22:28 <s3wong> #info s3wong can contribute code to this group, and around 20% time a week
16:22:47 <readams> #info do you mean just for this subgroup or for GBP as a whole?
16:23:04 <alagalah_> #info alagalah clarifies this is for this sub-group
16:23:29 <readams> #info I'll contribute 100% of my time until this is done later this week
16:23:30 <alagalah_> aboch: banix regXboi Are any of you interested in contributing to this sub-group and if so how much time can you devote ?
16:23:48 <regXboi> which one is this?
16:23:58 <alagalah_> Policy Repo/End point registry
16:24:12 <alagalah_> regXboi: I don't think this will be anywhere near as onerous as Renderers
16:24:13 <regXboi> um...
16:24:19 <regXboi> let me read the #info
16:24:28 <regXboi> because I think I'm worried about what I see there
16:24:32 <regXboi> give me an orbit or 6
16:24:33 <banix> I need to understand this better
16:24:53 <aboch> alagalah_: not ready yet. Sorry.
16:25:04 <alagalah_> banix: Sure... if you are interested, join the ghangout but we are just about done.
16:25:30 <alagalah_> #info readams points out that this isn't really onerous and we don't have a lot more to talk about at this point until we have a working prototype
16:25:33 <regXboi> so I don't think you are done
16:25:37 <regXboi> what's the hangout link
16:25:38 <alagalah_> aboch: not sweat
16:25:43 <regXboi> I'm reading something here that I don't like
16:25:44 <alagalah_> regXboi: ending meeting
16:25:48 <alagalah_> Ping me
16:25:49 <s3wong> alagalah: readams: how about ML2 ODL driver? I think there is an assumption that mestery will do it, but I don't think he has the time
16:26:01 <regXboi> InstanceIDs as key into the tree?
16:26:05 <regXboi> how useful is that?
16:26:11 * regXboi thinks not very
16:26:12 <alagalah_> regXboi: I may have minuted that wrong, I was playing catchup
16:26:18 <alagalah_> regXboi: Wifi madness
16:26:42 <regXboi> readams: can you clarify that point?
16:26:50 <alagalah_> I'll get with readams and augment the minutes
16:26:59 <alagalah_> Or join hangout
16:27:04 <alagalah_> https://plus.google.com/hangouts/_/calendar/ZHZvcmtpbkBub2lyb25ldHdvcmtzLmNvbQ.ilarq9u79ea3u3a5q0hhg1gd8s
16:28:36 <alagalah_> #info readams says instanceID == URI ...
16:28:53 <alagalah_> #info regXboi still has concerns... alagalah may have mis-worded minutes
16:29:07 <dvorkinista> regXboi: what would you like it to be?
16:29:11 <alagalah_> #info Point has been clarified, regXboi is happy... and thats a good thing
16:29:13 <dvorkinista> regXboi: what is your concern?
16:29:28 <regXboi> I heard instanceId and was worried about opacity
16:29:34 <alagalah_> regXboi: Ack
16:30:19 <dvorkinista> opacity at full capacity
16:32:30 <readams> #endmeeting
16:32:44 <regXboi> um... can't do that unless you are chair
16:32:48 <regXboi> we need alagalah back
16:33:02 <regXboi> as alagalah
16:33:04 <regXboi> not alagalah_
16:36:08 <alagalah_> #endmeeting
16:36:11 <alagalah_> bugger
16:36:13 <regXboi> nope
16:36:17 <regXboi> you need to be alagalah
16:36:20 <regXboi> change your nick
16:36:21 <alagalah_> I thought I made rob char
16:36:24 <regXboi> nope
16:36:31 <alagalah_> How do I do that?
16:36:35 <regXboi> so /nick alagalah
16:36:41 <regXboi> (no underscore)
16:36:52 <alagalah> #endmeeting