18:05:00 #startmeeting networking_policy 18:05:01 Meeting started Thu Feb 8 18:05:00 2018 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:05:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:05:05 The meeting name has been set to 'networking_policy' 18:05:18 not much of an agenda from me today 18:05:33 perhaps just the talk submission? 18:05:39 annakk: did you submit it? 18:05:51 not yet 18:06:02 planning after the meeting? 18:06:07 annakk: sure 18:06:17 rkukura: tbachman: your thoughts on the email thread? 18:06:27 SumitNaiksatam: looks good! 18:06:50 just sent a update 18:06:51 I have a couple minor suggestions 18:06:59 annakk: thanks 18:07:05 rkukura: sure 18:07:34 One would be to mention that there is a generic solution along with the NSX and ACI solutions 18:07:59 rkukura: oh yeah of course, very good point 18:08:03 taken for granted :-) 18:08:29 it might make more sense to say “several years” instead of “several cycles” 18:09:04 i agree 18:09:17 makes it sound more mature 18:09:23 ok :) 18:09:40 agree 18:10:10 last is that I’m wondering if we should make any mention of discussing GBPs status within OpenStack, or if we are better off ignoring that 18:10:40 rkukura: my feeling is that we are better of ignoring that since at this point we dont have any concrete to state 18:10:41 I don't know.. it might draw attention 18:10:51 i believe the abstract can be slighlty altered if accepted 18:11:06 so if things change, we might have a chance to do that a little bit later as well 18:11:19 that's good to know 18:11:24 any -> anything 18:11:51 annakk: in the past you could update your abstract, and also swap authors/presenters 18:12:08 of course not substatially/materially change the talk itself :-) 18:12:23 i wanted to throw “materially” there 18:12:33 but if GBP supports IoT by then we'll be able to include it :) 18:12:34 if we could come up with some very subtle way to refer to “becoming official” within the roadmap, it might help 18:12:36 been hearing a lot of legal speak on TV for the past days :-) 18:13:03 annakk: i think we would be 18:13:08 I’m a bit concerned about reviewers of the abstract dismissing GBP because it is not an official project, so mentioning that might make it more relevant to them 18:13:33 annakk: although if you have plans to do that, you can perhaps mention that is something that is in the works? 18:13:55 SumitNaiksatam: I thought it was a joke, but who knows :) 18:14:17 IoT and ML 18:14:23 Blockchain 18:14:29 and i was just typing that you should be committed to doing it :-) 18:14:30 service mash! 18:14:33 lol 18:14:44 we need to rename our project 18:14:46 blockchain was in syndey summit btw 18:14:56 tbachman: +1 18:14:58 lol 18:15:22 “service meshed block chain of internet of things” 18:15:27 GroupBasedPolicyContainerizedBlockchainwithSmartContractsServiceMeshing 18:15:32 :) 18:15:32 there you go 18:15:32 Oh, left off IoT 18:16:22 we can wrap early if nothing more to discuss 18:16:22 we are the networking analog of self-driving marketing 18:16:28 annakk: thanks for working on the abstract 18:16:34 annakk: yeah, huge thanks! 18:16:41 tbachman: lol 18:16:47 did we decide on which authors to list? 18:17:04 annakk: did you decide ^^^ ? 18:17:37 no, but Sumit suggests Gary should be there as an openstack dinasour 18:17:41 and Sumit 18:17:52 heh 18:17:58 “Sage" 18:17:59 annakk: lol, thanks for attributing that to me :-) 18:18:04 i hope gary is not listening 18:18:07 :) 18:18:28 * tbachman tabs for auto-complete on gar 18:18:45 tbachman: me doing the same 18:18:51 there are bunch of them :-) 18:18:52 hey - I was interviewed gary for his 1st OpenStack job 18:19:05 s/I was interviewed/I interviewed/ 18:19:07 oh! then s/gary/rkukura 18:19:10 rkukura: are you trying to claim the throne? 18:19:17 annakk: rotfl 18:19:20 closest to extinct? 18:19:23 lol 18:19:39 “elder statesman" 18:19:52 my involvement in openstack/neutron preceedes all of you 18:19:56 i should get out of here 18:19:58 SumitNaiksatam, annakk, and garyk probably makes most sense 18:19:59 for sure 18:19:59 lol 18:20:11 SumitNaiksatam: you may be right 18:20:30 i think we can swap the authors later 18:20:32 I started during the week of the essex summit 18:20:59 i started in cactus/diablo 18:21:15 should not have mentioned that! 18:21:23 tricked you 18:21:39 yeah, you got me 18:21:44 pre-quantum even 18:21:53 nova-networking days 18:21:56 lol 18:22:17 anyway, annakk please feel free to ping us on the email thread if you need further help 18:22:33 ok, sure 18:22:38 just a quick question — has anyone recently tried building top-of-tree master with a clean setup? 18:22:53 you mean UTs? 18:22:54 * tbachman is getting a weird problem with tox 18:22:55 yeah 18:23:07 Cloning https://github.com/noironetworks/python-opflex-agent.git (to master) to ./.tox/py27/src/python-opflexagent-agent 18:23:08 fatal: unable to access 'https://github.com/noironetworks/python-opflex-agent.git/': Could not resolve host: github.com 18:23:08 Command "git clone -q https://github.com/noironetworks/python-opflex-agent.git /home/vagrant/work/openstack/upstream/group-based-policy/.tox/py27/src/python-opflexagent-agent" failed with error code 128 in None 18:23:09 I ran tox last night with current master plus my current branch 18:23:09 let me fire off in the upstream test patch 18:23:19 need to clear out .tox, etc. 18:23:32 I can do it from a command line by itself 18:23:35 which is what’s weird 18:23:39 yes, I had to clear out .tox because of changes in AIM 18:23:44 k 18:24:08 will have to go figure this one out 18:24:23 just rebased the test patch, lets see 18:24:31 actually, I may be seeing issues 18:24:37 oh 18:24:53 two AIM UTs had failed, thought it was timeouts, but need to investigate 18:25:14 its possible that AIM might have broken us 18:25:19 its happened in the past :-( 18:25:40 wont jump to conclusions though 18:25:50 lets watch the upstream test patch as well 18:25:59 alrighty, thanks all 18:26:09 bye until next week! 18:26:13 SumitNaiksatam: bye! 18:26:14 I had rerun the AIM UTs, and now 5 failed :( 18:26:15 #endmeeting