Friday, 2016-02-26

*** yamamoto_ has joined #openstack-dragonflow00:18
*** yamamoto_ has quit IRC00:23
*** gongysh has joined #openstack-dragonflow00:54
*** yamamoto_ has joined #openstack-dragonflow01:20
*** yamamoto_ has quit IRC01:26
*** yamamoto has joined #openstack-dragonflow02:04
*** yamamoto has quit IRC02:15
*** yamamoto has joined #openstack-dragonflow03:01
*** gongysh has quit IRC04:23
*** gongysh has joined #openstack-dragonflow05:16
*** gampel has joined #openstack-dragonflow06:48
*** gongysh has quit IRC07:08
*** gongysh has joined #openstack-dragonflow08:44
*** gongysh has quit IRC09:39
*** gongysh has joined #openstack-dragonflow09:40
*** gampel has quit IRC10:30
*** matrohon has joined #openstack-dragonflow10:47
matrohonhi all10:48
matrohonI was wondering if totally getting rid of the neutron RDBMS was considered in dragonflow?10:50
matrohonoanson, ^ may be you have an answer?10:50
gongyshmatrohon,  I think we should delete the neutron RDBMS.10:56
matrohongongysh, yep, that's something I'd like to experiment in the context of https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/734210:57
matrohongongysh, I was looking at opensource distributed sdn controller, with nosql backend10:58
matrohondragonflow looks promising10:59
matrohonI'll try to attend the dragonflow's irc meeting next monday11:00
gongyshmatrohon, many projects have both neutron db and remote plugin db.11:00
gongyshmatrohon,  I don't think they are a must.11:01
matrohongongysh, yep, but they not atteempt to duplicate the neutron db entirely11:01
matrohongongysh, +111:02
matrohonOpenContrail for instance doesn't use the neutron DB layer, only the API11:02
matrohonI was wondering if dragonflow was planning to do so11:03
matrohonI saw that nick-ma was trying to fix inconsistency issue between neutron db and DF's db11:03
matrohonit would be useless without the neutron db :)11:04
matrohongtg let's discuss that monday morning11:05
nick-mamatrohon: what I did is just the first step on db consistency. Most of the nosql server just provides eventual consistency, and some of them takes time on convergence. Neutron db provides strong consistency which makes the virtual topology more reliable. I'm thinking lots of options on how to make the whole solution reliable and also scalable.11:09
nick-mamatrohon: I will continue working on this topic.11:09
matrohonnick-ma, great! I'm also very interested11:10
nick-manick-ma: welcome to dragonflow meeting. :-)11:10
nick-mamatrohon: welcome :-)11:10
matrohonnick-ma, RamCloud looks very promising to cover this area11:10
matrohonnick-ma, thanks11:11
matrohon:)11:11
openstackgerrithujie proposed openstack/dragonflow: implement ovsdb monitor function for dragonflow  https://review.openstack.org/28294511:14
*** gongysh has quit IRC11:22
*** yamamoto has quit IRC12:08
*** yamamoto has joined #openstack-dragonflow13:01
*** yamamoto has quit IRC13:05
*** yamamoto has joined #openstack-dragonflow13:25
*** yamamoto has quit IRC13:30
*** yamamoto has joined #openstack-dragonflow14:16
*** yamamoto has quit IRC16:50
*** yamamoto has joined #openstack-dragonflow16:50
*** hardwind has joined #openstack-dragonflow17:11
*** matrohon has quit IRC17:19
*** WANG_Feng has quit IRC17:20
*** yamamoto has quit IRC17:28
*** yamamoto has joined #openstack-dragonflow17:28
*** yamamoto has quit IRC17:28
*** yamamoto has joined #openstack-dragonflow17:30
*** yamamoto has quit IRC18:12
*** yamamoto has joined #openstack-dragonflow18:12
*** yamamoto has quit IRC18:12
*** yamamoto has joined #openstack-dragonflow18:13
*** yamamoto has quit IRC20:13
*** yamamoto has joined #openstack-dragonflow20:13
*** yamamoto has quit IRC20:13
*** yamamoto has joined #openstack-dragonflow21:14
*** yamamoto has quit IRC21:19
*** yamamoto has joined #openstack-dragonflow22:16
*** yamamoto has quit IRC22:21
*** yamamoto has joined #openstack-dragonflow23:17
*** yamamoto has quit IRC23:23
*** yamamoto has joined #openstack-dragonflow23:54

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!