09:01:35 #startmeeting Dragonflow 09:01:36 Meeting started Mon Jan 9 09:01:35 2017 UTC and is due to finish in 60 minutes. The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:39 The meeting name has been set to 'dragonflow' 09:01:47 Who is here for the Dragonflow meeting? 09:01:51 * xiaohhui raises his hand 09:01:57 Good morning 09:02:02 yuli_s, nick-ma_, lihi ? 09:02:27 irenab ? 09:02:31 All right. Let's start 09:02:39 #info dimak and xiaohhui in meeting. 09:02:39 hi 09:02:46 #info irenab is in meeting too 09:03:02 #topic Roadmap 09:03:40 Since we are so few hands today, I'll just run through what I know about the roadmap, and you'll add anything I will missed. 09:04:10 IPv6 - I know lihi is working on the comments to the neighbour discovery / advertising patch. 09:04:27 #link Add IPv6 ND Neighbor Advertiser application https://review.openstack.org/#/c/412208/ 09:05:12 SFC had no progress due to the work on NB refactor 09:05:31 Chassis health and service health, rajivk uploaded a patch with implementation 09:05:35 😞 09:05:49 #link Added support for service status reporting https://review.openstack.org/#/c/415997/ 09:06:09 I think we should have the openstack bot quote patches in the same way it quotes bugs 09:06:52 I have to go over the specs again, but rajivk's patch definitely includes the second spec (Spec to support service status reporting https://review.openstack.org/#/c/402395/ ) 09:07:07 About chassis health, I will put my spirit in review and code base on rajivk's work. 09:07:24 xiaohhui, great. Thanks! I think he would appreciate that too. 09:07:33 As far as I know, there is no progress in TAPaaS. 09:07:54 yuli_s has been working on aggregating the rally results, and didn't have a lot of time to look into it 09:08:22 NB API - We are still trying to get infra to accept jsonmodels. They are trying to convince us to use oslo.versionedobjects (OVO) 09:08:38 The needed fixes were merged 09:08:49 We think that OVO is a bit of an overkill for what we want to do, whereas jsonmodels is very simple. 09:08:56 dimak, great. Thanks! 09:09:07 And I honestly think we're not at the point yet where we can benefit from OVO 09:09:42 #link Add jsonmodels requirement https://review.openstack.org/#/c/415164/ 09:09:58 I see Matthew Thode removed his objections. 09:10:15 I'm trying to get tonyb on IRC but timezone differences make it a bit difficult 09:11:07 All right. 09:11:27 Anything else for roadmap? 09:11:31 I'll upload some refactor patches 09:11:52 I've started to port Chassis model so we can see how it will look 09:12:06 dimak, Great. 09:12:17 I'd love some input whether it makes things better or worse before we port other models :) 09:12:20 I'll also update the spec today to incorporate everyone's latest comments. 09:12:38 #topic Bugs 09:13:01 I don't see anything new and urgent except one issue 09:13:09 Bug 1651643 09:13:09 bug 1651643 in DragonFlow "metadata service cannot start due to zmq binding conflict" [Critical,In progress] https://launchpad.net/bugs/1651643 - Assigned to Li Ma (nick-ma-z) 09:13:43 It's popping up all the time, forcing services to fail since we have too many publishers/subscribers. 09:14:23 I see nick-ma_ is on it. But he isn't here now. 09:14:30 What is the specific output of the error? 09:14:43 It's in the bug report: 09:14:49 I see 09:14:50 ZMQError: Address already in use 09:15:04 I see address in use in df-local-controller occasionally too 09:15:12 Yes 09:15:47 I think the issue is that we were lazy, and thought that in compute node side, we don't need the publisher service for multiproc publishers 09:15:49 (e.g. zmq) 09:16:29 The truth is I'm not sure we need a publisher on the metadata service either. I think that's an error since everyone uses nb_api. 09:17:52 Any other bugs that need to be discussed? 09:18:33 #topic Open Discussion 09:18:44 The floor is for the taking. 09:19:03 Nothing on my end 09:19:20 Nothing from me too 09:19:34 All right. Then thanks everyone! 09:19:42 Keep up the great work! 09:19:45 Good bye! 09:19:48 #endmeeting