16:13:04 <edwarnicke> #startmeeting MD-SAL Weekly meeting
16:13:04 <odl_meetbot> Meeting started Tue May  6 16:13:04 2014 UTC.  The chair is edwarnicke. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:13:04 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:13:04 <odl_meetbot> The meeting name has been set to 'md_sal_weekly_meeting'
16:13:05 <jmedved> #info moiz - what is the need of habving multiple transaction per thread?
16:13:10 <edwarnicke> #chair jmedved
16:13:10 <odl_meetbot> Current chairs: edwarnicke jmedved
16:13:16 <edwarnicke> #chair abhijitkumbhare
16:13:16 <odl_meetbot> Current chairs: abhijitkumbhare edwarnicke jmedved
16:13:19 <jmedved> info tony for example, model driven stats manager
16:13:19 <edwarnicke> #chair icbts
16:13:19 <odl_meetbot> Current chairs: abhijitkumbhare edwarnicke icbts jmedved
16:13:22 <edwarnicke> #chair alagalah
16:13:22 <odl_meetbot> Current chairs: abhijitkumbhare alagalah edwarnicke icbts jmedved
16:13:32 <jmedved> a thread creates a lot fo transaction w/o need for them to finish
16:13:47 <alagalah> #info a thread creates a lot fo transaction w/o need for them to finish
16:14:05 <edwarnicke> #topic Example Infinispan Datastore Implementation
16:14:12 <jmedved> #info a transaction is created per event, and transactions are not tied to a thread
16:14:52 <alagalah> jmedved: If we get echo again you may need to mute everyone apart from presenter
16:15:06 <jmedved> #info moiz wants to understand tha if he processes notifications on a songle thread, what is the use case for creating multiple transactions per thread?
16:15:45 <alagalah> jmedved: Someone must be using their laptop microphone and the speaker is feeding back into it (is my guess)
16:15:52 <abhijitkumbhare> may i ask a basic question - what is the new datastore that was added a few weeks ago? Is it the one Moiz/Raghu are talking about?
16:15:52 <jmedved> #info tony responds that a start manager can be updating multiple parts of the subtree in different transactions at different times
16:16:25 <jmedved> abhijitkumbhare: no, this is just hte prototype
16:16:40 <jmedved> the new data store is a tree-based from scratch implementation
16:16:43 <abhijitkumbhare> OK - so this could be used instead of akka
16:16:49 <jmedved> no
16:16:51 <alagalah> jmedved: Slides published ?
16:16:57 <jmedved> this will work with akka
16:17:00 <jmedved> orthogonal
16:17:01 <abhijitkumbhare> OK
16:17:42 <jmedved> in clustered data store, a shard will be an actor. the shard actor will use an in-memory data store backed up by some sort of persistence
16:18:23 <jmedved> alagalah: slides will be published after the meeting
16:18:46 <alagalah> jmedved: Thank you
16:18:57 <djx> where?
16:19:59 <jmedved> djx: md-sal page - https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL
16:20:21 <djx> jmedved: thanks
16:22:07 <edwarnicke> jmedved: djx had asked if we are recording the meeting...
16:22:16 <jmedved> #info tony: old subtree/ new subtree - nformation about new subtree root is captured in listerner, not transaction
16:23:11 <jmedved> #info moiz: when a transaction is created you can not tell which part will be changed, therefore you need to capture the whole tree. but you can re-create the original subtree from the changed subtree
16:23:24 <jmedved> ewarnicke: yes we are
16:24:04 <jmedved> #info ewarnicke: it is incredibly useful to have the original subtree. get a sense of what is going on, what changed, etc.
16:24:53 <jmedved> #info moiz: data change should be in the event,
16:25:56 <jmedved> #info tony: good to have both old and new subtree available in event,s then listener can be stateless; very hard to write binding aware listener that acts only on the delta; for example flow change, you need to know how the flow looked before and after
16:26:45 <jmedved> #info moiz no denyoing that data is useful; but wer may have to optimize this, since it can be a lot of data;
16:27:13 <jmedved> #info raghu - don’t know which part is modified, so you may have to take a snapshot of the whole subtree
16:27:43 <jmedved> #info tony: use instance identifier you can determine the subtree which is being changed
16:28:07 <jmedved> #info basheerudin - registrations happen at different levels, so you may have to waklk the whole tree
16:29:13 <jmedved> #info tony: for instance identifiers, you can determine exactly what changed and when
16:29:49 <alagalah> jmedved: edwarnicke What happens to the original subtree after the transaction is complete?
16:30:17 <jmedved> #info moiz problem is creating a nomralized node from the tree cache. when you create an infinispan transaction you create a normalized node and keep it ready and it has to be from the root
16:30:50 <jmedved> #info tony: you can do it from instance id which are listeners and root f the subtree
16:31:24 <jmedved> #info tony: data change event you are returning different subtrrees to different listeners based on their registrations
16:31:55 <jmedved> #info moiz create multiple of normalized node instances
16:37:15 <icbts> #info Ed Warnicke begins new topic
16:37:20 <jmedved> #info ewarncike how to facilitate involvement in md-sal issues
16:37:44 <alagalah> New topic ?
16:38:01 <jmedved> #info how can we organize work so that chunks can be pulled by different folks
16:38:07 <jmedved> alagalah: yes please
16:38:09 <djx> yep, that was one of the difficulties I got the first time I saw odl
16:38:10 <alagalah> #topic https://docs.google.com/a/noironetworks.com/document/d/1GdvAiPVMNI1VChojegP-HTrNZznNGvgx2a0I6j7hGdk/edit
16:38:20 <alagalah> #topic ewarncike how to facilitate involvement in md-sal issues
16:38:36 <alagalah> #info how can we organize work so that chunks can be pulled by different folks
16:39:46 <alagalah> #info edwarnicke asks "Who is ready to pick up a shovel?"
16:40:17 <alagalah> #info (hard to tell who is responding on WebEx) edwarnicke: Folks from Brocade want to help
16:40:57 <alagalah> edwarnicke: Can you have them #info here ??
16:41:20 <jmedved> #info ewarnicke: who has interest working on a datastore?
16:41:41 <edwarnicke> If folks interested in working on datastore could #info in...
16:41:57 <jmedved> #info arash eghtesadi working on a k-v data store, would like to have a mentor for a better view, ask questions
16:42:29 <alagalah> edwarnicke: +1 sharding tree-wise
16:43:25 <jmedved> #info raghu: need a series of POCs to validate different assumptions
16:45:32 <dbainbri> #info I would like to be involved, need to figure out at what level and time commitment.
16:45:53 <djx> edwarnicke how about skype?
16:51:27 <edwarnicke> djx: I am agnostic as to meeting method
16:52:11 <djx> I don't know who was saying that google hangout have a limit. I don't know about skype
16:52:18 <abhijitkumbhare> #info - same like dbainbri - would like to listen in initially & figure out the level and time commitment later
16:52:48 <edwarnicke> #info Bug list for MD-SAL: https://bugs.opendaylight.org/buglist.cgi?list_id=7399&short_desc=Milestone&resolution=---&query_format=advanced&short_desc_type=allwordssubstr&component=mdsal&product=controller
16:53:02 <mlemay> #info (sorry IRC client was crashed)
16:53:58 <edwarnicke> #link https://bugs.opendaylight.org/buglist.cgi?list_id=7399&short_desc=Milestone&resolution=---&query_format=advanced&short_desc_type=allwordssubstr&component=mdsal&product=controller - Current MD-SAL Bugs
16:53:58 <raghu67> #info. Okay. I noted David and Abhijit as interested in data store. Anyone else I missed?
16:54:10 <jmedved> #info md-sal milestone bugs: 688, 629,
17:01:09 <icbts> Friday demo sounds good :)
17:01:16 <LuisGomez> #info i will be interested in joining datastore and cluster calls
17:01:41 <raghu67> #info Luis. Okay. Noted
17:03:46 <phrobb> Should someone (Ed) do a "#stopmeeting" to close this one out?
17:04:07 <phrobb> … I think it needs to be a meeting Chair
17:07:41 <phrobb> edwarnicke, abhijitkumbhare, alagalah, jmedved: could one of you please issue a #stopmeeting command?
17:07:54 <jmedved> #stopmeeting
17:08:02 <alagalah> #endmeeting