16:12:18 <colindixon> #startmeeting MD-SAL Interest Call
16:12:18 <odl_meetbot> Meeting started Tue Aug  5 16:12:18 2014 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:12:18 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:12:18 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:12:23 <colindixon> #topic agenda
16:12:45 <colindixon> #link https://wiki.opendaylight.org/view/MD-SAL_Weekly_Call this is where the agenda and notes will be
16:16:12 <colindixon> #topic status update
16:19:26 <edwarnicke> #topicrequest I think Moiz and company have a clustering demo for today to show folks
16:20:37 <colindixon> edwarnicke: noted
16:31:13 <rovarga_> #link https://git.opendaylight.org/gerrit/#/c/9496/ is the introduction of the writer implementation
16:35:55 <flaviof> #link https://gist.github.com/3a4ac3907c45049c6789
16:39:39 <tbachman> colindixon: can you mute coby?
16:39:57 <colindixon> I can’t
16:40:01 <colindixon> I’m not the host
16:40:04 <tbachman> ah
16:40:12 <colindixon> :-(
16:40:28 <colindixon> there we go
16:41:17 <tbachman> ah — guess there’s no recording then?
16:41:36 <tbachman> no worries
16:42:48 <edwarnicke> Timecheck... only 18 min left for clustering demo
16:42:57 <colindixon> edwarnicke:
16:42:58 <colindixon> I know
16:45:17 <colindixon> #topic clustering demo
16:46:03 <dmm> @colin: where is the call info?
16:46:27 <colindixon> dmm: https://wiki.opendaylight.org/view/MD-SAL_Weekly_Call
16:46:39 <dmm> thx
16:46:50 <colindixon> #info there won’t be a recording because we don’t have the host
16:47:10 <tbachman> colindixon: thx for running!
16:47:23 <colindixon> #info moiz shows the config in “configuration/initial/module-shards.conf”
16:47:30 <colindixon> #undo
16:47:30 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2695850>
16:47:45 <colindixon> #info moiz shows the config in “configuration/initial/module-shards.conf”
16:48:07 <colindixon> #info it includes information about the shards and the shard leaders in JSON format
16:49:32 <colindixon> #link https://git.opendaylight.org/gerrit/#/c/9677/ this patch has the code which has this file
16:50:21 <colindixon> #info demos that data is available from any node even though it’s stored only on one node
16:50:23 <colindixon> Cool!
16:50:51 <colindixon> not that we have a logging problem :-/
16:51:12 <colindixon> can we make logging a requirement for Lithium
16:51:57 <colindixon> #info demos with toaster that changing the toaster config on one node and showing it’s represented on all nodes in the cluster
16:52:15 <colindixon> #info then he shuts down the leader of the toaster shard
16:52:21 <colindixon> #info shows that the data is still there
16:52:59 <colindixon> #info the leader has now changed to one of the up nodes
16:53:47 <colindixon> #info this means we can still change the values even after the old leader has failed
16:54:08 <colindixon> #info in addition, we have persistence from this
16:54:41 <colindixon> #topic questions for the demo
16:54:56 <colindixon> #info colindixon asks “this looks like it’s working, is that right?”
16:55:38 <colindixon> #info answer is that there are still some places where things need to be tweaked, for example sending of snapshots of state between nodes vs. just updates
16:55:54 <colindixon> #info robert varga asks how serialization is working for them
16:56:58 <colindixon> #info answer is that they’re using protocol buffers for serialization and they’re benchmarking it, but the scaling seems like it could use a bit of work
16:58:15 <colindixon> #topic clustering RPC demo
16:58:59 <colindixon> #info starts one mininet instance pointing to one controller instance in the cluster
17:01:01 <colindixon> #info shows that you can make the RPC call from a different instance in the cluster and it will appropriately go to the right instance
17:02:14 <colindixon> #info the demo actually shows doing a RESTCONF operation to the flow service, which then turns it into an RPC to the OpenFlow plugin, which installs the flow
17:03:02 <colindixon> #info Ramkumar asks what changes are needed from the OpenFlow plugin
17:03:55 <colindixon> #info answer is none by default, they will need to change things if they want to take advantage of the clustering. i.e., recover from a failed instance cleanly
17:06:39 <colindixon> #info there is a question about how the remote RPCs are routed to the appropriate cluster instance
17:07:19 <colindixon> #info answer is that you shouldn’t have to worry about that unless you want to really carefully control it
17:08:15 <colindixon> #endmeeting