Thursday, 2016-08-11

*** zhurong has quit IRC00:01
*** stanchan has quit IRC00:05
*** gouthamr has quit IRC00:08
*** gouthamr has joined #openstack-meeting-300:09
*** gouthamr has quit IRC00:10
*** VW has joined #openstack-meeting-300:12
*** toddjohn has quit IRC00:12
*** Sukhdev has quit IRC00:13
*** Sukhdev has joined #openstack-meeting-300:13
*** toddjohn has joined #openstack-meeting-300:18
*** gouthamr has joined #openstack-meeting-300:29
*** VW has quit IRC00:33
*** stanzgy has quit IRC00:35
*** tonytan4ever has quit IRC00:37
*** xiangfei2 has joined #openstack-meeting-300:47
*** toddjohn has quit IRC00:58
*** chandanc has joined #openstack-meeting-301:00
*** mtanino has joined #openstack-meeting-301:02
*** zhurong has joined #openstack-meeting-301:06
*** galstrom_zzz is now known as galstrom01:07
*** xiangfei2 has quit IRC01:07
*** toddjohn has joined #openstack-meeting-301:08
*** bpokorny_ has joined #openstack-meeting-301:10
*** mickeys has quit IRC01:13
*** bpokorny has quit IRC01:14
*** bpokorny_ has quit IRC01:14
*** toddjohn has quit IRC01:16
*** spzala has quit IRC01:21
*** gouthamr_ has joined #openstack-meeting-301:28
*** Sukhdev has quit IRC01:28
*** chandanc has quit IRC01:28
*** Sukhdev has joined #openstack-meeting-301:30
*** gouthamr has quit IRC01:31
*** s3wong has quit IRC01:35
*** tonytan4ever has joined #openstack-meeting-301:38
*** mtanino has quit IRC01:41
*** rama_y has joined #openstack-meeting-301:41
*** tonytan4ever has quit IRC01:42
*** galstrom is now known as galstrom_zzz01:46
*** zhurong has quit IRC01:50
*** mtanino has joined #openstack-meeting-301:51
*** zhurong has joined #openstack-meeting-301:51
*** Sukhdev has quit IRC01:56
*** mtanino has quit IRC01:57
*** loquacity is now known as loquacities01:58
*** tonytan4ever has joined #openstack-meeting-302:01
*** tonytan_brb has joined #openstack-meeting-302:04
*** tonytan4ever has quit IRC02:07
*** spzala has joined #openstack-meeting-302:22
*** spzala has quit IRC02:27
*** zhurong has quit IRC02:28
*** zhurong has joined #openstack-meeting-302:28
*** chandanc has joined #openstack-meeting-302:40
*** chandanc_ has joined #openstack-meeting-302:42
*** chandanc has quit IRC02:45
*** gouthamr_ has quit IRC02:49
*** baoli has joined #openstack-meeting-302:52
*** spzala has joined #openstack-meeting-302:53
*** vishwanathj_ has joined #openstack-meeting-302:54
*** sarob has joined #openstack-meeting-302:54
*** sarob has quit IRC02:58
*** yamahata has quit IRC02:58
*** iyamahat has quit IRC02:58
*** spzala has quit IRC02:59
*** spzala has joined #openstack-meeting-303:01
*** baoli has quit IRC03:03
*** spzala has quit IRC03:05
*** baoli has joined #openstack-meeting-303:09
*** gouthamr has joined #openstack-meeting-303:10
*** krotscheck_ has joined #openstack-meeting-303:12
*** krotscheck has quit IRC03:13
*** baoli has quit IRC03:13
*** krotscheck_ is now known as krotscheck03:14
*** gouthamr has quit IRC03:19
*** dimtruck is now known as zz_dimtruck03:22
*** julim has joined #openstack-meeting-303:26
*** revon has quit IRC03:30
*** tonytan_brb has quit IRC03:34
*** armax has quit IRC03:36
*** amotoki has quit IRC03:39
*** reedip has quit IRC03:47
*** beagles has quit IRC03:47
*** markmcclain has quit IRC03:47
*** rama_y has quit IRC03:48
*** jtomasek has quit IRC03:48
*** luzC has quit IRC03:50
*** dcwangmit01_ has joined #openstack-meeting-303:50
*** luzC has joined #openstack-meeting-303:51
*** coolsvap has joined #openstack-meeting-303:51
*** sc68cal has quit IRC03:52
*** dcwangmit01 has quit IRC03:52
*** b3nt_pin has joined #openstack-meeting-303:52
*** reedip has joined #openstack-meeting-303:52
*** sc68cal has joined #openstack-meeting-303:52
*** b3nt_pin is now known as Guest5456303:52
*** markmcclain has joined #openstack-meeting-303:54
*** jtomasek has joined #openstack-meeting-303:59
*** spzala has joined #openstack-meeting-304:02
*** spzala has quit IRC04:06
*** vishwanathj has quit IRC04:20
*** vishwanathj has joined #openstack-meeting-304:21
*** julim has quit IRC04:27
*** tonytan4ever has joined #openstack-meeting-304:34
*** tonytan4ever has quit IRC04:39
*** numan_ has joined #openstack-meeting-304:56
*** spzala has joined #openstack-meeting-305:01
*** dkehn_ has quit IRC05:03
*** spzala has quit IRC05:05
*** lpetrut has joined #openstack-meeting-305:11
*** anilvenkata has joined #openstack-meeting-305:19
*** claudiub has quit IRC05:19
*** sdake has quit IRC05:20
*** dkehn_ has joined #openstack-meeting-305:22
*** lpetrut has quit IRC05:31
*** lpetrut has joined #openstack-meeting-305:34
*** vishwanathj_ has quit IRC05:36
*** david-lyle_ has joined #openstack-meeting-305:43
*** TheJulia_ has joined #openstack-meeting-305:43
*** dlundquist_ has joined #openstack-meeting-305:43
*** jed56_ has joined #openstack-meeting-305:43
*** serverascode_ has joined #openstack-meeting-305:43
*** xgerman_ has joined #openstack-meeting-305:45
*** slaweq__ has joined #openstack-meeting-305:46
*** yantarou_ has joined #openstack-meeting-305:48
*** jed56 has quit IRC05:48
*** TheJulia has quit IRC05:48
*** njohnston has quit IRC05:48
*** david-lyle has quit IRC05:48
*** dlundquist has quit IRC05:48
*** yantarou has quit IRC05:48
*** bapalm has quit IRC05:48
*** xgerman has quit IRC05:48
*** slaweq has quit IRC05:48
*** serverascode has quit IRC05:48
*** mestery has quit IRC05:48
*** Guest81876 is now known as dasanind05:48
*** bapalm_ has joined #openstack-meeting-305:48
*** njohnston_ has joined #openstack-meeting-305:48
*** dlundquist_ is now known as dlundquist05:48
*** yantarou_ is now known as yantarou05:48
*** TheJulia_ is now known as TheJulia05:48
*** jed56_ is now known as jed5605:49
*** xgerman_ is now known as xgerman05:49
*** mestery has joined #openstack-meeting-305:51
*** serverascode_ is now known as serverascode05:51
*** pt_15 has quit IRC05:56
*** spzala has joined #openstack-meeting-306:02
*** spzala has quit IRC06:06
*** vishwanathj has quit IRC06:15
*** vishwanathj has joined #openstack-meeting-306:15
*** irenab_ has joined #openstack-meeting-306:16
*** irenab has quit IRC06:19
*** irenab_ is now known as irenab06:19
*** mickeys has joined #openstack-meeting-306:19
*** mickeys has quit IRC06:26
*** lpetrut has quit IRC06:30
*** Poornima has joined #openstack-meeting-306:31
*** rdopiera has left #openstack-meeting-306:33
*** pgadiya has joined #openstack-meeting-306:44
*** nkrinner_afk is now known as nkrinner06:45
*** pcaruana has joined #openstack-meeting-306:45
*** reedip has quit IRC06:57
*** irenab_ has joined #openstack-meeting-307:00
*** f13o has joined #openstack-meeting-307:00
*** irenab has quit IRC07:01
*** irenab_ is now known as irenab07:01
*** spzala has joined #openstack-meeting-307:02
*** chandanc_ has quit IRC07:05
*** spzala has quit IRC07:07
*** claudiub has joined #openstack-meeting-307:07
*** milan has joined #openstack-meeting-307:11
*** stanzgy has joined #openstack-meeting-307:15
*** reedip has joined #openstack-meeting-307:15
*** sarob has joined #openstack-meeting-307:16
*** matrohon has joined #openstack-meeting-307:19
*** sarob has quit IRC07:20
*** dkehn_ has quit IRC07:24
*** claudiub has quit IRC07:26
*** mbound has joined #openstack-meeting-307:31
*** dkehn_ has joined #openstack-meeting-307:38
*** mrmartin has joined #openstack-meeting-307:42
*** tonytan4ever has joined #openstack-meeting-307:51
*** tonytan4ever has quit IRC07:56
*** jtomasek_ has joined #openstack-meeting-308:02
*** spzala has joined #openstack-meeting-308:03
*** spzala has quit IRC08:08
*** mrmartin has quit IRC08:10
*** mrmartin has joined #openstack-meeting-308:12
*** mrmartin has quit IRC08:13
*** chandanc_ has joined #openstack-meeting-308:14
*** f13o has quit IRC08:18
*** iyamahat has joined #openstack-meeting-308:20
*** rossella_s has joined #openstack-meeting-308:22
*** sdake has joined #openstack-meeting-308:23
*** iyamahat has quit IRC08:24
*** vishwanathj_ has joined #openstack-meeting-308:26
*** abalutoiu has joined #openstack-meeting-308:31
*** ihrachys has joined #openstack-meeting-308:33
*** f13o has joined #openstack-meeting-308:36
*** coolsvap is now known as _coolsvap_08:41
*** mbound has quit IRC08:43
*** kzaitsev_mb has joined #openstack-meeting-308:47
*** Poornima has quit IRC09:03
*** sarob has joined #openstack-meeting-309:17
*** sarob has quit IRC09:21
*** sambetts|afk is now known as sambetts09:23
*** amitkqed has quit IRC09:27
*** amitkqed has joined #openstack-meeting-309:27
*** lpetrut has joined #openstack-meeting-309:30
*** _coolsvap_ is now known as coolsvap09:38
*** matrohon has quit IRC09:54
*** zhurong has quit IRC10:01
*** f13o has quit IRC10:08
*** matrohon has joined #openstack-meeting-310:08
*** sdague has joined #openstack-meeting-310:16
*** lpetrut has quit IRC10:17
*** mbound has joined #openstack-meeting-310:33
*** amotoki has joined #openstack-meeting-310:35
*** mbound has quit IRC10:38
*** alexismonville has joined #openstack-meeting-310:40
*** amotoki has quit IRC10:40
*** Guest54563 is now known as beagles10:41
*** alexismonville has quit IRC10:51
*** jed56 has quit IRC10:55
*** dkehn_ has quit IRC10:56
*** chandanc_ has quit IRC11:02
*** spzala has joined #openstack-meeting-311:05
*** vishwanathj_ has quit IRC11:06
*** spzala has quit IRC11:10
*** sarob has joined #openstack-meeting-311:11
*** dkehn_ has joined #openstack-meeting-311:15
*** stanzgy has quit IRC11:16
*** sarob has quit IRC11:16
*** f13o has joined #openstack-meeting-311:19
*** amitkqed has quit IRC11:28
*** amitkqed has joined #openstack-meeting-311:28
*** alexismonville has joined #openstack-meeting-311:37
*** alexismonville has quit IRC11:41
*** alexismonville has joined #openstack-meeting-311:46
*** rtheis has joined #openstack-meeting-311:48
*** alexismonville has quit IRC11:48
*** alexismonville has joined #openstack-meeting-311:48
*** alexismonville has quit IRC11:49
*** alexismonville has joined #openstack-meeting-311:49
*** tonytan4ever has joined #openstack-meeting-311:53
*** alexismonville has quit IRC11:54
*** milan has quit IRC11:56
*** tonytan4ever has quit IRC11:57
*** gouthamr has joined #openstack-meeting-311:59
*** yamamoto has joined #openstack-meeting-312:02
*** aohuanxuan has joined #openstack-meeting-312:03
*** milan has joined #openstack-meeting-312:03
*** spzala has joined #openstack-meeting-312:06
*** zhurong has joined #openstack-meeting-312:08
*** baoli has joined #openstack-meeting-312:10
*** spzala has quit IRC12:11
*** yamamoto has quit IRC12:13
*** yamamoto has joined #openstack-meeting-312:15
*** yamamoto has quit IRC12:19
*** yamamoto has joined #openstack-meeting-312:20
*** matrohon has quit IRC12:22
*** tovchinnikova has joined #openstack-meeting-312:25
*** sergio_nubeliu has joined #openstack-meeting-312:28
*** yamamoto has quit IRC12:29
*** zz_dimtruck is now known as dimtruck12:34
*** matrohon has joined #openstack-meeting-312:36
*** matrohon has quit IRC12:36
*** lpetrut has joined #openstack-meeting-312:37
*** lpetrut has quit IRC12:41
*** sdake has quit IRC12:43
*** lpetrut has joined #openstack-meeting-312:43
*** pt_15 has joined #openstack-meeting-312:44
*** baoli_ has joined #openstack-meeting-312:47
*** hamzy has quit IRC12:48
*** matrohon has joined #openstack-meeting-312:49
*** baoli has quit IRC12:50
*** lpetrut has quit IRC12:50
*** toddjohn has joined #openstack-meeting-312:51
*** lpetrut has joined #openstack-meeting-312:51
*** tonytan4ever has joined #openstack-meeting-312:54
*** f13o has quit IRC12:55
*** tonytan4ever has quit IRC12:57
*** tonytan4ever has joined #openstack-meeting-312:57
*** toddjohn has quit IRC13:00
*** toddjohn has joined #openstack-meeting-313:01
*** lblanchard has joined #openstack-meeting-313:01
*** vhoward has joined #openstack-meeting-313:02
*** toddjohn has quit IRC13:05
*** dtroyer has joined #openstack-meeting-313:07
*** spzala has joined #openstack-meeting-313:07
* dtroyer taps mic13:08
dtroyeranyone here?13:08
*** yamamoto has joined #openstack-meeting-313:09
rtheishi dtroyer13:09
* dtroyer woke up late13:09
*** njohnston_ is now known as njohnston13:09
dtroyer#startmeeting openstackclient13:10
openstackMeeting started Thu Aug 11 13:10:26 2016 UTC and is due to finish in 60 minutes.  The chair is dtroyer. Information about MeetBot at http://wiki.debian.org/MeetBot.13:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:10
*** openstack changes topic to " (Meeting topic: openstackclient)"13:10
openstackThe meeting name has been set to 'openstackclient'13:10
dtroyerjust for the record I suppose…13:10
*** chandanc has joined #openstack-meeting-313:10
rtheissure13:11
dtroyer#topic osc 3 release13:11
*** openstack changes topic to "osc 3 release (Meeting topic: openstackclient)"13:11
*** azemlyanov has joined #openstack-meeting-313:11
dtroyerosc-lib 1.0 hit the streets this morning, once https://review.openstack.org/353959 merges we'll have some gate tests running on OSC using it13:11
*** spzala has quit IRC13:12
rtheisnice13:12
dtroyerlooks like Henry's change has a +2 from stevemar, so I'll once over that again and it'll be on its way13:12
dtroyerI had some integration tests I wanted in 3.0, but in reality since that testing and we don't branch no big deal if it doesn't make it13:13
rtheissounds good13:13
rtheisstevemar has https://review.openstack.org/#/c/353883/ to update requirements in osc13:14
rtheisAnything else for 3.0?13:14
dtroyerbreaking news in -sdks, maybe one more fix13:14
dtroyerbut otherwise I think that's the list we've been holding for13:14
dtroyerthe o-c-c fun Friday and Monday set osc-lib back a few days, I needed to add the precedence fix to osc-lib13:15
rtheisokay13:15
*** f13o has joined #openstack-meeting-313:16
dtroyerI'm refining the email stevemar started in https://etherpad.openstack.org/p/osc-3.0-release to send, probably this afternoon.13:16
dtroyerI don't know if the release review will be ready today, I'll pudh it up whenever it is, but don't expect it to merge before Monday13:17
dtroyer#topic open discussion13:18
*** openstack changes topic to "open discussion (Meeting topic: openstackclient)"13:18
*** spzala has joined #openstack-meeting-313:18
*** beagles is now known as beagles_brb13:18
dtroyeranything else you want to talk about rtheis?13:18
rtheishttps://bugs.launchpad.net/python-openstackclient/+bug/156015713:19
openstackLaunchpad bug 1560157 in python-openstackclient ""openstack network list" fails with "An SSL error occurred."" [Medium,Fix released] - Assigned to Richard Theis (rtheis)13:19
rtheisquestion about backporting ... do we ask them to upgrade osc instead?13:19
dtroyerabsolutely, we don't backport except in security issues13:20
dtroyerI'll reply there13:20
rtheisthanks dtroyer13:21
rtheisthat's it for me13:21
*** dimtruck is now known as zz_dimtruck13:21
dtroyercool13:21
dtroyerone more pause for anyone else who snuck in…13:21
rtheisFYI: I'll be at neutron mid-cycle next week discussing osc and osc plugin13:22
rtheisI may miss this meeting13:22
*** pgadiya has quit IRC13:22
dtroyerno worries, or hot topics may show up here ;)13:22
rtheis:)13:22
*** julim has joined #openstack-meeting-313:22
dtroyerok then, I'll go see what mordred just posted to fix more arg handling…13:23
dtroyer#endmeeting13:23
*** openstack changes topic to " (Meeting topic: ops_guide)"13:23
openstackMeeting ended Thu Aug 11 13:23:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-08-11-13.10.html13:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-08-11-13.10.txt13:23
openstackLog:            http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-08-11-13.10.log.html13:24
*** vhoward has quit IRC13:26
*** beagles_brb is now known as beagles13:27
*** tonytan4ever has quit IRC13:29
*** aohuanxuan has quit IRC13:30
*** matrohon has quit IRC13:32
*** toddjohn has joined #openstack-meeting-313:37
*** toddjohn has quit IRC13:37
*** toddjohn has joined #openstack-meeting-313:37
*** matrohon has joined #openstack-meeting-313:39
*** vgridnev has joined #openstack-meeting-313:39
*** singlethink has joined #openstack-meeting-313:41
*** yamamoto has quit IRC13:41
*** asettle has joined #openstack-meeting-313:42
*** yamamoto has joined #openstack-meeting-313:43
*** asettle has quit IRC13:43
*** bklei has joined #openstack-meeting-313:43
*** yamamoto has quit IRC13:43
*** asettle has joined #openstack-meeting-313:44
*** yamamoto has joined #openstack-meeting-313:44
*** bklei has quit IRC13:44
*** prateek has joined #openstack-meeting-313:47
*** sdake has joined #openstack-meeting-313:47
*** uxdanielle has joined #openstack-meeting-313:49
*** rbak has joined #openstack-meeting-313:51
*** zz_dimtruck is now known as dimtruck13:56
*** raissa has joined #openstack-meeting-313:56
*** ddieterly has joined #openstack-meeting-313:56
*** elmiko has joined #openstack-meeting-313:58
*** egafford has joined #openstack-meeting-313:58
*** iyamahat has joined #openstack-meeting-313:58
*** sskripnick has joined #openstack-meeting-314:00
vgridnev#startmeeting sahara14:00
openstackMeeting started Thu Aug 11 14:00:26 2016 UTC and is due to finish in 60 minutes.  The chair is vgridnev. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
vgridnev#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
egaffordo/14:00
openstackThe meeting name has been set to 'sahara'14:00
vgridnevo/14:00
elmikohi o/14:00
*** doffm_ is now known as doffm14:00
tellesnobregahey o/14:01
*** sskripnick has left #openstack-meeting-314:01
*** baoli_ has quit IRC14:02
mionkinhi14:02
vgridnev#chair egafford14:02
openstackCurrent chairs: egafford vgridnev14:02
vgridnevha mode14:02
*** tosky has joined #openstack-meeting-314:02
toskyhi14:02
vgridnev#topic News / updates14:02
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:02
vgridnevworking on kerberos integration, 75 % of patches are ready for review ( I think )14:03
toskyI'm a bit stuck on documenting the source of the jars, but I plan to have a doc patch soon14:03
vgridnevtosky, have you saw https://review.openstack.org/#/c/351920/ ?14:04
egaffordStarting on the Ambari image generation yaml. Going pretty well; testing is really lovely compared to DIB (since it's idempotent and in-place, so any changes already on the image are already on the image and you don't have to wait for them.)14:04
toskyvgridnev: ups, no14:04
vgridnevtosky, spark and cdh jobs are happy (main consumers of job)14:05
mionkinI finished work on designate and now working on replacing old CLI commands in grenade14:05
toskyyeah, interesting14:05
egaffordMost of it's done; working on how best to deal with shared resources (like java setup scripts, etc.)14:05
vgridnevok, not absolutely happy14:05
*** tonytan4ever has joined #openstack-meeting-314:05
toskyvgridnev: there are the usual quota issues, but I guess we can talk later about them14:06
toskylater in the meeting14:06
vgridnevsure14:06
*** sdake_ has joined #openstack-meeting-314:07
*** tonytan4ever has quit IRC14:07
vgridnevone more release of client is going to be done later this week ( I think today or friday )14:08
*** tonytan4ever has joined #openstack-meeting-314:08
vgridnevthat will include sorting for pagination, and designate14:08
*** sdake has quit IRC14:09
mionkinit's great14:09
*** VW has joined #openstack-meeting-314:11
vgridnev#topic Open discussion14:11
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:11
vgridnevuh, voting for talks finished, so now we should wait for results14:12
toskyso, is there anything we can do to help with quota issues in the Sahara CI?14:12
toskylike reduce the number of the slots (even if it would slow down the jobs)14:12
*** anilvenkata has quit IRC14:13
*** tonytan_brb has joined #openstack-meeting-314:14
vgridnevis it still present? will take a look on that one more time14:14
toskyI think that most of the failures come from that; even in the review you mentioned above (see errors like: APIException: Quota exceeded for instance: Requested 6, but available 3)14:14
*** tonytan4ever has quit IRC14:14
NikitaKonovalovtosky: I've seen this already. For some reason quotas on ci labs went very low.14:15
NikitaKonovalovI've updated them14:15
NikitaKonovalovshould be fine now14:15
toskyoh, thanks14:16
vgridnevdo we need some extra ATCs for sahara? see for details: [openstack-dev] [all][ptl][tc] extra ATCs for newton14:20
vgridnevI can propose a commit if there are good candidates14:20
*** VW_ has joined #openstack-meeting-314:20
* egafford checks Stackalytics for the actual ATC list...14:22
*** VW has quit IRC14:22
*** VW has joined #openstack-meeting-314:22
egaffordelmiko managed to get 2 in \o/14:23
vgridnevnote: Sergey Lukjanov and Alexander Ignatov already has ATC14:23
elmikolol14:24
elmikosadly, i don't think our group is gonna make the trip to barcelona =(14:24
egaffordI don't see anyone missing from the list of folks who've actually submitted patches. tmckay, croberts, and elmiko all have ATC this cycle, and... yeah. :(14:24
*** piet_ has joined #openstack-meeting-314:25
vgridnevso, who is going to travel to Barca? egafford tellesnobrega and tosky ?14:25
*** VW_ has quit IRC14:26
*** crobertsrh has joined #openstack-meeting-314:26
tellesnobregavgridnev, unfortunately i'm not making this time14:26
tosky95% on my side, yes14:26
egaffordvgridnev: I think it might just be tosky and I this time. Brazil is far from Barcelona.14:26
*** vishwanathj_ has joined #openstack-meeting-314:26
*** tonytan_brb is now known as tonytan4ever14:27
tellesnobrega:(14:27
egaffordtellesnobrega: Is there still a chance that you might make it if some preso gets accepted or something, or is it Just a No at this point.14:27
egafford?14:27
tellesnobregaegafford, i didn't submit the preso, I got too busy with other stuff and missed the deadline14:28
tellesnobregaSotK, I would say its pretty much a firm no14:28
egaffordAh, ok. Well, you got a lot of other stuff done, so that's good at least.14:29
tellesnobregaunless some miracle happens :)14:29
vgridnevtosky, yes, it is easier for folks who in europe to get attended14:29
vgridnevthis time14:29
*** amotoki has joined #openstack-meeting-314:31
egaffordvgridnev: Is it time to start talking about pruning our core reviewer list a little?14:31
vgridnevwe can discuss that; sure14:32
vgridnev#topic Core review list14:32
*** openstack changes topic to "Core review list (Meeting topic: sahara)"14:32
egaffordWe've talked about it for the last 2 cycles or so; folks who are still in Sahara's orbit a little we should probably keep, but some folks probably just aren't coming back.14:32
egaffordalazarev has moved on entirely, and I don't think I ever met John Speidel, for instance.14:33
vgridnevthem are no longer in list14:34
vgridnevok14:34
egaffordhttps://launchpad.net/~sahara-drivers/+members#active14:34
egaffordIs this the wrong list?14:34
vgridnevuh, sahara-drivers14:34
vgridnevhttps://review.openstack.org/#/admin/groups/133,members14:35
egaffordNice. Okay, that's a pretty sensible group; there's at least a chance that any of those people could contribute a review.14:36
egaffordWe could be more aggressive in removing people, but it doesn't seem necessary.14:37
toskyoh, not sure it's really important, but could I be added to https://launchpad.net/~sahara-tests-drivers ?14:38
*** tenobreg has joined #openstack-meeting-314:39
tenobregyeah, we can wait another cycle and do this again14:39
egafford+1; you sure do drive sahara tests.14:39
*** jtomasek_ has quit IRC14:40
vgridnevegafford, we can be more aggressive, so we need to define some policy probably14:40
egaffordYeah, agreed.14:40
*** yamamoto has quit IRC14:40
vgridnevlike if you are core and there are 2 cycles with very low rate in reviews, so then sorry, you will be removed14:41
tenobregmaybe have a minimum number of reviews each cycle, and if the core stay below this threshold for 2 cycles, we can remove14:41
*** tellesnobrega has quit IRC14:41
*** tenobreg is now known as tellesnobrega14:42
egaffordvgridnev: Yeah; I want to say we can make exceptions in rare cases where someone is legitimately away for a full year but plans to come back, but in that case we can always just vote to re-add people.14:42
egaffordIt's a year; that's a long time.14:42
egaffordAny idea of a threshold for reviews?14:42
*** raj_singh_ has joined #openstack-meeting-314:43
elmikoprobably some percentage of total reviews in a cycle?14:43
*** matrohon has quit IRC14:43
egaffordelmiko: Yeah, definitely.14:43
tellesnobregaelmiko, +114:44
vgridnevno percentage is bad14:44
vgridnevI ate 36%14:45
vgridnevhttp://stackalytics.com/?module=sahara-group14:45
*** numan_ has quit IRC14:45
vgridnev50 reviews per cycle is really good value; at least 2 reviews per week in cycle14:46
NikitaKonovalovI'd say a core reviewer should at least have a vote on all (or almos all) specs. This guaratess that the core team actually agrees on what is going to be implemented14:46
*** ddieterly is now known as ddieterly[away]14:46
vgridnevNikitaKonovalov, agreed, specs is also good idea14:46
tellesnobregathis is a good point NikitaKonovalov, core have to review 80% of specs, and have at least 50 reviews per cycle14:47
*** sdake has joined #openstack-meeting-314:47
*** sdake_ has quit IRC14:47
tellesnobregasomething like that14:47
*** yamamoto has joined #openstack-meeting-314:47
egaffordI like total reviews per cycle; say someone is legitimately away at the beginning of a cycle (for any reason) and misses a bunch of specs.14:47
egaffordI think encouraging the cores to always vote on specs is really good but I don't know that we should implement a cutoff metric based on it, because it could end up hurting people somewhat randomly.14:48
egaffordI do like the 50 review per cycle rule.14:48
toskyuhm, I'm a bit below, need to raise my value :)14:48
egaffordtosky: Heh.14:48
egaffordYou've got 4 left; I think you're gonna be ok.14:49
tellesnobregaand you can always pick it up on the next cycle, as long as you don't stay 2 cycles below that14:49
egaffordSeems totally reasonable to me. A flat number of reviews per cycle is really easy to know if you're going to make it (so it's really transparent) and it's a good measure of contribution across the whole cycle.14:50
vgridnevuh, I forgot about stable main team: alazarev still there, but I don't have access to remove.  I think that we need to define our team for stable14:50
vgridnevand, should we remove matt from core list?14:51
*** ddieterly[away] is now known as ddieterly14:51
vgridnevand probably make some replacement?14:51
*** matrohon has joined #openstack-meeting-314:51
vgridnevtellesnobrega is in top3 right now, for example14:52
vgridnevI like matt -> tellesnobrega replacement14:52
egaffordvgridnev: :D14:52
* egafford doesn't even have to ping you about that now!14:52
egafford\o/14:52
tellesnobregai like that replacement as well :)14:52
egaffordSolid +2.14:53
vgridnevfor stable team, I think that we should just remove andrew from list14:54
egaffordAnd yeah, mattf has no reviews for 2 cycles.14:54
toskydefinitely +214:54
egaffordvgridnev: Agreed re: alazarev, I think we're ok there. We may want to replace Trevor with someone more active next cycle if elmiko, tmckay, and croberts continue to slowly drift away.14:55
elmikoi think you should definitely replace me14:56
elmikoi doubt i will be able to work on openstack after this cycle14:56
elmiko(if you would even call this "working on openstack")14:56
egaffordelmiko: Do you speak for tmckay and/or croberts when you say that?14:57
elmikoi can't say for sure, but probably. let me ask them14:57
vgridnev#action I have to document our core policy somewhere, post that in ML, and then nominate tellesnobrega for core, post in ML about removing folks from stable team.14:57
vgridnevwe have around 2 mins14:58
crobertsrhI am only doing a few reviews here and there.  I haven't done any coding in awhile now.14:58
*** rajinir has joined #openstack-meeting-314:58
*** zhurong has quit IRC14:58
*** matrohon has quit IRC14:58
egaffordcrobertsrh: Your review numbers are weirdly solid, though, so thanks.14:58
crobertsrhReviews are a habit that I just can't seem to break :)14:59
*** Benj_ has joined #openstack-meeting-314:59
egaffordNo pressure on our side to break it. ;)14:59
elmikotmckay says that goes for him too14:59
*** mlavalle has joined #openstack-meeting-315:00
vgridnev#endmeeting15:00
*** openstack changes topic to " (Meeting topic: ops_guide)"15:00
openstackMeeting ended Thu Aug 11 15:00:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-08-11-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-08-11-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-08-11-14.00.log.html15:00
*** abalutoiu has quit IRC15:00
*** tosky has left #openstack-meeting-315:00
elmikothanks vgridnev egafford !15:00
*** pavel_bondar has joined #openstack-meeting-315:00
mlavalle#startmeeting neutron_l315:00
tellesnobregathanks guys15:00
openstackMeeting started Thu Aug 11 15:00:32 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
*** elmiko has left #openstack-meeting-315:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
*** janzian has joined #openstack-meeting-315:00
openstackThe meeting name has been set to 'neutron_l3'15:00
haleybhi15:00
pavel_bondarhi15:00
carl_baldwino/15:00
njohnstono/15:00
mlavalle#chair carl_baldwin15:01
openstackCurrent chairs: carl_baldwin mlavalle15:01
mlavalleis tidwellr around?15:01
mlavalleAgenda for today is here:15:01
mlavalle#link https://etherpad.openstack.org/p/neutron-l3-subteam15:01
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
jschwarz\o/15:02
mlavalleThe obvious reminder is the Neutron mid-cycle meeting next week in Cork Ireland15:02
*** raissa has left #openstack-meeting-315:03
carl_baldwinIt is coming right up. Looking forward to seeing people there.15:03
mlavalleThe other annoucement is we have to keep an eye on Newton-3 milestone15:04
mlavalle#link http://releases.openstack.org/newton/schedule.html15:05
mlavalleAugust 29th - September 2nd15:05
mlavalleso it is coming our way really quickly15:05
*** steve_ruan has joined #openstack-meeting-315:05
mlavalleany other annoucements from the team?15:05
carl_baldwinNot from me.15:06
mlavalleif not, let's move on15:06
mlavalle#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:06
*** VW has quit IRC15:07
mlavalleThe first up is one that haleyb and jschwarz have been discussing in the Neutron channel: https://bugs.launchpad.net/neutron/+bug/161219215:07
openstackLaunchpad bug 1612192 in neutron "L3 DVR: Unable to complete operation on subnet" [Critical,Confirmed]15:07
*** raj_singh_ has quit IRC15:07
*** armax has joined #openstack-meeting-315:07
mlavallefrom what I got from the conversation, it might not be a Neutron issue but rather a Tempest one?15:08
haleybmlavalle: yes, there seems to be an issue in a tempest test - add-router-interface is failing, and the unwind is barfing on a port still being in the subnet15:08
jschwarzhaleyb, mind you, I saw this happen on rally a while back as well15:08
haleybbut i see a DBDeadlock on create_port() so wonder if it's an ml2 change15:08
jschwarzmaybe it's an API change that snuck into Neutron unawares?15:09
*** VW has joined #openstack-meeting-315:10
* haleyb feels like he slides down the pole info a fire station every morning :)15:10
mlavalleso can we say that we need to research this one further?15:10
haleybmlavalle: yes, need to look further, will scream if i need help15:11
mlavallehaleyb, jschwarz thank you for keeping an eye on this15:12
mlavalleNext up is https://bugs.launchpad.net/neutron/+bug/154098315:12
openstackLaunchpad bug 1540983 in OpenStack-Gate "Gate failures for neutron in test_dualnet_multi_prefix_slaac" [Undecided,Expired]15:12
mlavalleSo this morning I went to logstash to try to find ocurrences of this bug15:12
mlavalleI am using the query at the top of the bug: message:"in test_dualnet_multi_prefix_slaac" AND voting:115:13
mlavalleand couldn't find a case over the past 7 days15:13
mlavalleAm using a wrong query maybe?15:13
haleybmlavalle: logstash wasn't cooperating for me today either, but that one is infrequent15:14
*** matrohon has joined #openstack-meeting-315:14
carl_baldwinI was thinking there was another related one. Me trying to swap in memories of that.15:15
haleybI did however see a similar failure in the dvr tests, in that case dhcp failed to start, so second VM failed to get IP, and it went downhill from there15:15
mlavalleok, I'll keep an eye on it daily, to make sure we don't get in trouble close to N-315:16
carl_baldwinCould be related to https://bugs.launchpad.net/neutron/+bug/160954015:16
openstackLaunchpad bug 1609540 in neutron "Deleting csnat port fails due to no fixed ips" [Critical,In progress] - Assigned to Carl Baldwin (carl-baldwin)15:16
*** piet_ has quit IRC15:16
mlavalleYeah, that's the next one in the agenda15:17
mlavalleand carl_baldwin and I couldn't find cases of the expected message yesterday15:17
carl_baldwinThey both involve the same unit test.15:17
carl_baldwinmlavalle: Yeah, that is strange. I would expect to see that debug message.15:18
mlavalleI will talk to infra today to make sure logstash catches debug level messages15:18
*** piet_ has joined #openstack-meeting-315:18
mlavalleI guess all we can do for the time being is to be vigilant about these 2 bugs15:19
*** f13o has quit IRC15:19
mlavalleI'll check them daily and will talk to infra15:19
carl_baldwinmlavalle: Thanks.15:20
carl_baldwinIt'd be nice to know that we can search for debug messages successfully.15:20
mlavalleNext bugs are high importance. First one was reduced to high lately: https://bugs.launchpad.net/neutron/+bug/156287815:21
openstackLaunchpad bug 1562878 in neutron "L3 HA: Unable to complete operation on subnet" [High,Confirmed] - Assigned to Ann Taraday (akamyshnikova)15:21
mlavalleThanks to jschwarz for followin up with it. any comments?15:21
jschwarzI tried to reproduce this one earlier this week but couldn't15:21
jschwarzsince it's not occurring in the gate afaik, the importance can be lowered IMO15:21
mlavalleeven lower than high?15:21
jschwarzMedium seems nice since if me and Ann can't reproduce this on rally, this might have been fixed already15:22
mlavalleok, thanks15:23
mlavalleNext up is https://bugs.launchpad.net/neutron/+bug/159607515:23
openstackLaunchpad bug 1596075 in neutron "Neutron confused about overlapping subnet creation" [High,In progress] - Assigned to Kevin Benton (kevinbenton)15:23
mlavalleAs I said last week, this is a long complicated affair, involving several potential patches15:24
*** mionkin has quit IRC15:24
mlavalleI pinged kevinbenton yesterday and he is still working on a couple of fixes for this. Once they are ready, he will have some more interaction with the submitter to confir it is fixed15:24
*** crobertsrh has left #openstack-meeting-315:25
*** baoli has joined #openstack-meeting-315:25
mlavalleNext up is https://bugs.launchpad.net/neutron/+bug/160316215:25
openstackLaunchpad bug 1603162 in neutron "Pluggable IPAM rollback fails with reference driver" [High,In progress] - Assigned to Carl Baldwin (carl-baldwin)15:25
carl_baldwinI think I've got this one fixed.15:25
*** tidwellr has joined #openstack-meeting-315:26
carl_baldwinI was just starting to look at the multinode dvr grenade job. I doubt the failure is related.15:26
carl_baldwin#link https://review.openstack.org/#/c/348956/15:26
carl_baldwinI wanted to be sensitive to rechecks thuogh.15:26
carl_baldwin*though15:26
mlavalle++15:27
*** yamamoto has quit IRC15:28
*** mickeys has joined #openstack-meeting-315:28
mlavalleif there are no more comments, let's move on. Thanks for the update carl_baldwin15:28
carl_baldwinI'll get some reviewers on the fix today.15:28
mlavalleThnaks!15:28
mlavalleNext up is https://bugs.launchpad.net/neutron/+bug/161048315:29
openstackLaunchpad bug 1610483 in neutron "Pluggable IPAM rollback mechanism is not robust" [High,Confirmed]15:29
mlavalleany comments on this one carl_baldwin?15:30
carl_baldwinThis affects external drivers mostly since the reference driver (for now) uses the context DB rollback.15:30
carl_baldwinpavel_bondar: Have you guys had a chance to think about this at all?15:31
pavel_bondarcarl_baldwin: yes, I agree with the issue, current rollback is not actually reliable and has to be reworked15:31
*** dtroyer has left #openstack-meeting-315:31
carl_baldwinSo, in summary, we have no plans yet to fix this but it is an issue that we should plan for soon.15:32
*** mickeys has quit IRC15:32
mlavalleThanks!15:33
pavel_bondarI would pick this task, but since I am not longer part of Infoblox openstack team (working on Infoblox another project) I don't have enough bandwith to drive it to the end.15:33
pavel_bondarProbably I could assist with comments&review, but probably what my current bandwidth allows15:34
carl_baldwinpavel_bondar: Anyone else there to pass it on to?15:34
carl_baldwinWe can take this out of band, mlavalle15:35
mlavalleFinally we have https://bugs.launchpad.net/neutron/+bug/159932915:35
openstackLaunchpad bug 1599329 in neutron "Potential regression on handing over DHCP addresses to VMs" [High,In progress]15:35
pavel_bondarcarl_baldwin: it is better to check with John B. about it, I am not sure15:35
carl_baldwinpavel_bondar: Will do.15:35
mlavalleWe were waiting to see if a fix solved this one. Haven't heard anything15:36
mlavalleI will check around today about this one15:36
mlavalleany other comments?15:36
haleybmlavalle: that looks similar to something i noticed yesterday - VM dhcp fails15:37
haleybhttp://logs.openstack.org/51/337851/19/check/gate-tempest-dsvm-neutron-dvr-multinode-full/c944b3d/logs/screen-q-dhcp.txt.gz was the info i found so far, but it was a multinode failure, not strict dvr15:37
mlavalleok, will take a look. will ping you if i have questions15:38
haleybtx15:38
mlavalle#topic Routed networks15:39
*** openstack changes topic to "Routed networks (Meeting topic: neutron_l3)"15:39
carl_baldwinHi15:39
carl_baldwinI think we're doing pretty well here.15:40
carl_baldwinWe have had some review on the create / delete segment ml2 patch.15:40
mlavalleyeah15:40
carl_baldwinI'm not sure if xiaohhui is in a position to handle the feedback.15:40
carl_baldwin#link https://review.openstack.org/#/c/31735815:41
*** dimtruck is now known as zz_dimtruck15:41
carl_baldwinLooks like xiaohhui is on it.15:41
mlavalleyeah he uploaded a revision last night15:41
*** iyamahat has quit IRC15:42
carl_baldwinGood, I had written him an email to see if he needs assistance. I hadn't heard back.15:42
*** zz_dimtruck is now known as dimtruck15:42
carl_baldwinI'll keep watching it.15:42
carl_baldwinDo we have anything else pressing for Newton?15:43
mlavalleI'll push the segment ids in port patch next revision today15:43
mlavalleand we may need to pay some attention to docs15:43
carl_baldwinYes, docs! My only hope now is the plane ride.  :)15:44
mlavalleCool! Let's move on then15:45
mlavalle#topic BGP Dynamic Routing15:45
*** openstack changes topic to "BGP Dynamic Routing (Meeting topic: neutron_l3)"15:45
tidwellrhi15:45
carl_baldwinIt'll be nice to go over how we're doing at the mid-cycle and figure out what we need to do for Ocata.15:45
mlavalletidwellr, steve_ruan you are up15:45
carl_baldwinThat's the last thing about routed networks from me ^15:46
tidwellr:)15:46
steve_ruantidwellr, to totally break the dependency15:47
tidwellrwe've been discussing the eVPN spec this week, we're going to explore a different approach15:47
steve_ruanyou bgp will not depend on networking-bgpvpn, right?15:47
tidwellrhowever, I don't think we've ever taken the RFE to the drivers team15:47
tidwellrsteve_ruan: I think we should explore that15:47
steve_ruanok15:47
*** kzaitsev_mb has quit IRC15:48
tidwellranyway, I don't see anything on the eVPN fron getting into Newton, but getting a start on Ocata would be good15:48
tidwellrcarl_baldwin: has this RFE been discussed at the drivers meeting yet?15:48
*** sdake_ has joined #openstack-meeting-315:49
carl_baldwintidwellr: no.15:49
*** mickeys has joined #openstack-meeting-315:49
tidwellrcarl_baldwin: we have a spec we've been iterating on, I assume we'd be asked for one anyway15:49
carl_baldwinThe focus of the drivers meeting has shifted a bit to discussing status of Newton items.15:50
tidwellrcarl_baldwin: ok, good to know. I don't think there's any rush to explore this with the drivers team at the moment15:50
*** elmiko has joined #openstack-meeting-315:51
carl_baldwintidwellr: ok15:51
*** sdake has quit IRC15:51
*** milan has quit IRC15:51
tidwellrI'd like to see it discussed so that maybe we can have something for Ocata15:51
mlavalleanything else tidwellr steve_ruan ?15:51
tidwellrnot from me15:51
steve_ruanno,thanks15:51
mlavalleThanks for the update!15:51
mlavalle#topic FWaaS15:51
*** openstack changes topic to "FWaaS (Meeting topic: neutron_l3)"15:51
njohnstonHi!  So things are looking good for l3 agent extensions - https://review.openstack.org/#/c/339246/ has one +2 (thanks carl_baldwin!), needs another.15:52
carl_baldwintidwellr: Let's get it teed up for discussion. We might be able to touch on it at the mid-cycle.15:52
carl_baldwinnjohnston: Thanks for the reminder to revisit that one.15:52
njohnstoncarl_baldwin: Sure thing!15:52
njohnstonThe FWaaS side to act as an l3 agent extension is also coming along: https://review.openstack.org/#/c/337699/15:52
*** woodster_ has joined #openstack-meeting-315:53
carl_baldwinnjohnston: Excellent.15:53
njohnstonWe're hoping to land significant swaths of FWaaS v2 core functionality on Friday, so it's good to see these things coming together.15:53
njohnstonI think if I can get https://review.openstack.org/#/c/339246/ merged, all that leaves in the codebase of Neutron proper is a fullstack test, which will get very involved15:54
njohnstonand I am deferring that work until a little later15:54
njohnstonI think that's it for me15:55
*** bpokorny has joined #openstack-meeting-315:55
*** bpokorny has quit IRC15:55
*** kzaitsev_mb has joined #openstack-meeting-315:55
mlavallenjohnston: thanks for the update!15:55
*** dtroyer has joined #openstack-meeting-315:55
*** pavel_bondar has quit IRC15:55
*** bpokorny has joined #openstack-meeting-315:55
mlavalle#topic Conversion to Pluggable IPAM15:55
*** openstack changes topic to "Conversion to Pluggable IPAM (Meeting topic: neutron_l3)"15:55
carl_baldwinWe got that bug worked out.15:56
carl_baldwinI think we're almost in good shape.15:57
carl_baldwinI hope to get the bug fix merged and then get a few rechecks on the switch to pluggable before the mid-cycle.15:57
*** cdent has joined #openstack-meeting-315:57
carl_baldwinThen, pull the trigger at the mid-cycle.15:57
mlavalleGreat!15:57
*** iyamahat has joined #openstack-meeting-315:58
carl_baldwinThe gate is slow these days.15:58
*** gouthamr-afk has joined #openstack-meeting-315:58
njohnstonQueue max delay: 32.70 hours https://twitter.com/openstackstatus/status/76374733917771776015:58
mlavalleyikes15:59
*** tovchinnikova has quit IRC15:59
mlavalleok team, time is almost up15:59
carl_baldwinThat's less than 50015:59
carl_baldwinThanks, mlavalle15:59
njohnstonthanks all!15:59
mlavalleThank you for your attendance and hard work15:59
mlavalle#endmeeting16:00
*** openstack changes topic to " (Meeting topic: ops_guide)"16:00
openstackMeeting ended Thu Aug 11 16:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-08-11-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-08-11-15.00.txt16:00
tidwellrbye16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-08-11-15.00.log.html16:00
*** janzian has left #openstack-meeting-316:00
cdent#startmeeting api_wg16:00
openstackMeeting started Thu Aug 11 16:00:15 2016 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api_wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
*** tidwellr has left #openstack-meeting-316:00
cdent#chair etoews elmiko16:00
openstackCurrent chairs: cdent elmiko etoews16:00
* mlavalle waves at cdent16:00
etoewso/16:00
cdenthey mlavalle16:00
*** azemlyanov has quit IRC16:01
cdent#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:01
elmikoo/16:01
cdentIs that a new agenda or last week's agenda?16:01
etoewsnewish16:02
etoews#topic start a "what's happening in the wide world of APIs" section of the newsletter?16:02
*** openstack changes topic to "start a "what's happening in the wide world of APIs" section of the newsletter? (Meeting topic: api_wg)"16:02
etoewsis this something we care to do?16:02
cdentI recall discussing it a couple weeks ago, and there was enthusiasm in principle and concern in effort16:02
elmikoseems nice16:03
etoewsdo you folks see enough stuff on a weekly basis that might help fill out such a section?16:03
elmikoare we talking about adding links to things outside of openstack?16:03
etoewsyes16:03
elmikoi'm not confident that i could fill a section on a weekly basis16:03
cdentI wish I did see enough stuff but at the moment that's not happening16:03
etoewsalright. let's not put something in there we're not confident we can care and feed16:04
cdentIt kind of feels like unless one of the three of us gets a good deal more time, such a section would be quite anaemic and might be better off waiting16:04
cdentjinx16:04
elmikoheh16:05
cdent#topic open16:05
*** openstack changes topic to "open (Meeting topic: api_wg)"16:05
cdent(open before we get into the regulars)16:05
cdentany visitors who have things they want to bring up, or anything else from anyone?16:05
etoewsshall we add a new regular topic about bugs https://bugs.launchpad.net/openstack-api-wg ?16:06
cdentI just wanted to report that I've committed my to do list to doing a weekly review of those bugs16:06
cdentyeah that16:06
cdentin my most recent review of them I added some comments16:06
*** gouthamr-afk has quit IRC16:07
etoewsi noticed that.16:08
* cdent add bug review section to agenda template16:08
*** steve_ruan has quit IRC16:08
cdent#topic bug review16:08
*** openstack changes topic to "bug review (Meeting topic: api_wg)"16:08
elmikooh man, we've got some triage to do16:09
etoewsi'm going address https://bugs.launchpad.net/openstack-api-wg/+bug/1593308 right now.16:09
openstackLaunchpad bug 1593308 in openstack-api-wg "The recommended way of transmitting error/fault information back to the user" [Undecided,New] - Assigned to Everett Toews (everett-toews)16:09
*** kzaitsev_mb has quit IRC16:09
cdentmy comments were mostly "what is this bug actually asking for"16:09
cdentetoews, king of the workshop16:10
*** egafford has left #openstack-meeting-316:10
*** seldenr has joined #openstack-meeting-316:11
cdentbrb16:13
etoewshuh. for some reason my `Closes-Bug: 1593308` in https://github.com/openstack/api-wg/commit/e13a8f49bfac2593da29708f51690dfe56592f14 had no affect on https://bugs.launchpad.net/openstack-api-wg/+bug/159330816:13
openstackLaunchpad bug 1593308 in openstack-api-wg "The recommended way of transmitting error/fault information back to the user" [Undecided,New] - Assigned to Everett Toews (everett-toews)16:13
*** kzaitsev_mb has joined #openstack-meeting-316:14
cdentetoews: I think that's something that has to be configured and since we set up launchpad after setting up the repos that config isn't there. I don't remember the details on how to do it16:15
cdentbut I'll take the action of figuring it out16:15
cdent#action (cdent) get api-wg gerrit and launchpad hooked up for closes-bug16:15
*** mlavalle has left #openstack-meeting-316:16
etoewscdent: shall i add a link to errors.rst from http.rst? seems like a helpful thing to do.16:16
cdentit does yes16:16
elmikobrb16:16
*** baoli has quit IRC16:17
* etoews adds note to http.rst16:18
*** baoli has joined #openstack-meeting-316:18
cdentI reckon that can go on concurrently16:21
cdent#topic previous meeting action items16:21
*** openstack changes topic to "previous meeting action items (Meeting topic: api_wg)"16:21
cdentthere were no actual action items in the log from the previous meeting, was there other stuff that should be followed up?16:22
*** Swami has joined #openstack-meeting-316:23
*** matrohon has quit IRC16:23
etoewshttps://review.openstack.org/35420216:23
etoewscdent: elmiko: i think that can be a quick workflow+1 if you're amenable16:24
elmikoyup, looking now16:25
elmikolgtm16:25
*** gouthamr-afk has joined #openstack-meeting-316:25
cdentis the linking right? I have little faith in my rst16:26
cdentit does look right16:26
etoewsworks locally anyway...16:27
*** yamahata has joined #openstack-meeting-316:27
cdentis there anything more to say about the capabilities stuff from last time?16:28
etoewsone less bug in the world https://bugs.launchpad.net/openstack-api-wg/+bug/159330816:28
openstackLaunchpad bug 1593308 in openstack-api-wg "The recommended way of transmitting error/fault information back to the user" [Undecided,Fix released] - Assigned to Everett Toews (everett-toews)16:28
elmikocdent: i didn't have any more to add16:29
etoewscdent: not really.16:29
cdentk16:29
cdent#topic guidelines16:29
*** openstack changes topic to "guidelines (Meeting topic: api_wg)"16:29
cdent#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:29
cdentwe might be able to freeze my uri advice16:29
cdentsorry wrong link16:31
etoewsfreezing now...16:31
cdent#undo16:31
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x7f5bc06f87d0>16:31
cdent#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:31
etoewscdent: ran the liaison harassment script on the uri review16:33
elmikolol16:33
cdent\o/16:33
etoewsdo you think a links guideline should be its own top level links.rst or just part of http.rst? https://bugs.launchpad.net/openstack-api-wg/+bug/156205816:35
openstackLaunchpad bug 1562058 in openstack-api-wg "Links guideline" [Undecided,New]16:35
*** vishwanathj_ has quit IRC16:36
* elmiko looking16:36
cdenti tink top level, because the http guideline has mostly turned into being about the protocol: headers, response codes, etc. Not bodies16:36
elmikoi kinda like keeping the guidelines smaller and more digestable, that http guideline is already quite dense16:36
etoews++16:37
cdentyeah at some point we could probably consider busting http into response codes, methods, other stuff16:37
* etoews gets busy writing a links guideline16:38
* cdent hopes etoews strives to be controversial and change the world ;)16:38
elmikohehe16:38
etoewsheh16:39
cdentthat reminds me of something: the errors.rst requires links in the jsonschema16:39
*** toddjohn has quit IRC16:39
cdentare we really expecting every error to have somewhere to go to describe that error, or is it going to turn out that people just always put some random help link for all errors?16:39
*** toddjohn has joined #openstack-meeting-316:40
elmikoideally the former, realistically the latter16:40
cdentfurther: do we expect that people will actually follow those links in the course of client-ing16:40
elmikoi think it would be way cool if the projects produced detailed error pages that could be linked to (possibly in their docs). but i think this doesn't seem likely.16:41
* cdent nods16:42
cdentshall we move on to api impact?16:42
cdent(mostly because of time)16:43
cdent#topic APIImpact16:43
*** openstack changes topic to "APIImpact (Meeting topic: api_wg)"16:43
cdent#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:43
*** ivar-lazzaro has joined #openstack-meeting-316:43
cdentShall we continue our usual tradition of leaving these until someone comes calling?16:44
*** toddjohn has quit IRC16:44
elmikoi think so, it's tough to break some of these down without an advocate16:44
* cdent nods16:44
elmikoin theory, the APIImpact flag is great. in meat space, it doesn't seem to work out as we had hoped16:45
*** ivar-laz_ has joined #openstack-meeting-316:45
cdentI think with sufficiently more time there could be a lot more productive engagement, but for the time being that's not really realistic16:45
elmiko++16:45
cdentwe can work on it, incremental16:45
*** banix has joined #openstack-meeting-316:45
cdentwe've already done bug review so:16:46
cdent#topic weekly newsletter16:46
*** openstack changes topic to "weekly newsletter (Meeting topic: api_wg)"16:46
cdentI've already started a bit at16:46
cdent#link  https://etherpad.openstack.org/p/api-wg-newsletter16:46
cdentplease review for sanity and typos etc16:46
cdentyou may wish to note that I've got out of order footnotes, do we care?16:46
elmikoi don't mind, i think i had them out of order on the one from last week16:47
*** ivar-lazzaro has quit IRC16:48
elmiko+1 from me on that copy, cdent16:48
*** tonytan4ever has quit IRC16:48
cdentetoews: any edits?16:48
*** bpokorny has quit IRC16:49
etoewscdent: if you give me 10 min, i might be able to get a link guideline out for review to include in there.16:49
etoewsyour call. send now or later works for me.16:50
cdentetoews: the other option, if you don't, is that you own sending the newsletter when you're done?16:50
etoewscan do16:50
cdentrawk16:50
etoewsawk16:50
* cdent looks at elmiko 16:50
* etoews looks at elmiko too just to be creepy16:50
elmikohaha16:51
elmikoi'm fine with waiting16:51
cdent#topic new business16:51
*** openstack changes topic to "new business (Meeting topic: api_wg)"16:51
elmikoSTOP STARING AT ME!!!! AAAaaaaa16:51
elmiko;)16:51
cdentany other gossip, issues, problems, suppositions, fud, incentives,  or other miscellany?16:52
etoewscan we add a fud section to the newsletter?16:52
elmikolol ++16:52
elmikowe could really make this a hot rag if we start dishing out openstack gossip16:53
cdentthe api wg has decided to stop using http, it's all grpc henceforth16:53
elmikonice16:53
elmikoand everyone needs to start supporting QUIC, yesterday!16:53
*** sskripnick has joined #openstack-meeting-316:54
*** ivar-laz_ has quit IRC16:54
*** olaph has joined #openstack-meeting-316:54
cdentactually I've got something:16:55
*** yamahata has quit IRC16:55
*** armax has quit IRC16:55
*** yamahata has joined #openstack-meeting-316:56
* elmiko looks at cdent16:56
*** rama_y has joined #openstack-meeting-316:56
cdentsince I missed the capabilities stuff: is it something that would fit under the dome of cross-project-spec type stuff? that is, not just a guideline from us.16:56
* cdent starts getting anxious16:56
* cdent shuffles feet16:56
* cdent points at etoews 16:56
elmikoi think it does16:56
etoewssure.16:57
*** sdake_ has quit IRC16:57
cdentMy main curiosity is because this is a thing coming on the horizon in nova and I'd really like it if for once nova rather than leading and expecting people to follow, collaborated16:57
cdent(am I allowed to say that out loud?)16:57
etoewsyep16:57
elmikoi think that seems entirely sensible16:58
etoewsthat reminds me. we should really have something about the api-wg in dhellmann's new cross project repo .16:58
*** armax has joined #openstack-meeting-316:58
*** julim has quit IRC16:58
* etoews can't find link for it...16:58
cdenthis goals thing, or something else?16:58
etoewsi think that's it.16:58
etoewsit's in review now right?16:59
cdentyes16:59
*** bpokorny has joined #openstack-meeting-316:59
etoewsya. that thing. something for another day.16:59
cdentwe've reach the end of our scheduled time16:59
*** armax has quit IRC16:59
cdentyou got the newsletter, etoews16:59
etoewsyep. i'll send the newsletter once i'm done with this guideline.16:59
cdenti'm going to add "more on capabilities" to agenda16:59
cdentfor next time16:59
etoewsciao17:00
cdentthanks everybody, it's always a good time17:00
cdent#endmeeting17:00
*** openstack changes topic to " (Meeting topic: ops_guide)"17:00
openstackMeeting ended Thu Aug 11 17:00:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-08-11-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-08-11-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-08-11-16.00.log.html17:00
elmikothanks cdent etoews !17:00
docaedocourtesy ping olaph kzaitsev_mb sskripnick17:00
sskripnickhiyo17:01
docaedo#startmeeting app-catalog17:01
openstackMeeting started Thu Aug 11 17:01:29 2016 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: app-catalog)"17:01
openstackThe meeting name has been set to 'app_catalog'17:01
olapho/17:01
docaedo#link https://wiki.openstack.org/wiki/Meetings/app-catalog#Proposed_Agenda_for_August_11th.2C_2016_.281700_UTC.2917:01
docaedo^^ todays agenda17:01
* docaedo thinks maybe "status updates" should be removed since that's often the whole meeting :)17:02
kzaitsev_mbo/17:02
docaedo#topic Status updates17:02
*** openstack changes topic to "Status updates (Meeting topic: app-catalog)"17:02
*** elmiko has left #openstack-meeting-317:02
*** cdent has left #openstack-meeting-317:02
sskripnickI have a little update17:02
sskripnickhttp://r-ci.tk:8100/17:02
docaedoI don't have any status updates that don't relate to things we have for later in the agenda (ie. glare stuff)17:02
*** sambetts is now known as sambetts|afk17:03
sskripnickHere you can login/logout and if you are member of app-catalog-core team (on launchpad) you can approve drafts17:03
sskripnickapp-catalog-core is open group, anyone can join17:03
docaedosskripnick: nice! I'll check that out later today17:03
docaedoOh I do have an update - I am on leave starting tomorrow, will return 8/2217:04
docaedoWe can have a meeting next week, would just need kzaitsev_mb to volunteer to chair it :)17:04
kzaitsev_mbsure, have no problem with that =)17:04
sskripnickso have a nice ... almost two weeks =)17:05
docaedooh just one week plus a day :) but yes, will be a nice break17:05
docaedoOK we can move on to...17:06
docaedo#topic App Catalog API v2.0 spec and framework (flask+sqlalchemy, django, something else?)(sskripnick)17:06
*** openstack changes topic to "App Catalog API v2.0 spec and framework (flask+sqlalchemy, django, something else?)(sskripnick) (Meeting topic: app-catalog)"17:06
*** s3wong has joined #openstack-meeting-317:06
sskripnickso if we are going to have own backend, we need some framework17:07
*** ivar-lazzaro has joined #openstack-meeting-317:07
sskripnickwe have already django and flask in codebase17:07
sskripnicki think we should chose one of them17:07
sskripnickI not big fan of alchemy, so I prefer to use django17:07
docaedoI am confused a little - glare is the backend piece, and the front end (web UI) should talk to glare via the API17:08
docaedoI'm just not sure here what has to change other then augmenting what already exists on the web UI piece17:08
sskripnickglare is not enough. we need to store some additional info like user comments17:08
sskripnickbtw we had a discussion with you and kzaitsev_mb %)17:09
docaedosskripnick: ah right, that's the part, thanks - in tokyo it sounded like the rating parts could be stored as metadata with each individual asset, but that is not going to be possible I think17:09
sskripnickyes. also we need to be able to perform fulltext search17:10
sskripnickand display only latest versions of artifacts17:10
sskripnickcurrently glare cant do this17:10
docaedosskripnick: I like django too17:10
docaedohow does/will glare handle versioning?17:10
docaedobecause that was a major reason for starting with glare instead of just writing our own to handle that17:11
*** mickeys has quit IRC17:11
kzaitsev_mb+1 on django (I actually like it's orm a bit more that sqlalchemy, but that's just a matter of tast I suppose)17:11
sskripnickglare does handle versioning, but it show all artifact versions when listing17:11
*** lpetrut has quit IRC17:11
*** mickeys has joined #openstack-meeting-317:11
docaedosskripnick: but that's easy - the UI can ask for all versions but only display the newest17:12
sskripnickglare cant handle this17:12
sskripnickit always show everything17:12
docaedoand what I'm getting at is that we can implement glare without having to do EVERYTHING at once (i.e. we do not need user comments, rating, etc. from the beginning)17:12
sskripnickbtw we can just unpublish old versions17:12
docaedosskripnick: I understand - I am saying the web UI can ask glare for everything, but only expose the newest17:12
*** rossella_s has quit IRC17:13
kzaitsev_mbhowever I would opt to move as much logic to frontend (i.e. angular code). This way it should b easy to reuse parts (controllers, static html, etc) in a form of XStatic packages between site and app-catalog-ui17:13
docaedoand I don't think we want to unpublish old versions, we should have a way for a user to get at an older version if they want17:13
sskripnickthere will be issues with pagination17:13
*** baoli has quit IRC17:13
docaedokzaitsev_mb: yes that's what I'm saying, put that logic in angular17:13
*** baoli has joined #openstack-meeting-317:13
sskripnickso we are going to speak with glare directly, and implement some additional features later?17:14
sskripnickplease take a look: https://review.openstack.org/#/c/354133/17:15
*** prateek_ has joined #openstack-meeting-317:15
*** numans has joined #openstack-meeting-317:15
docaedowhy not follow the same pattern we use today? the web UI when it loads hit's the API to get the asset list, so as it is the web UI only interfaces with the API17:15
sskripnickwe have two options: communicate with glare directly for basic data, and communicate with app-catalog-own-api for some extended data like comments or full text search17:16
*** mickeys has quit IRC17:16
sskripnickand second option -- develop single consistent api17:16
sskripnicknot be tied to glare backend17:16
docaedosskripnick: ok I think I understand17:17
docaedoI would say for now, we go with first option for this work - communicate with glare directly for basic data17:18
kzaitsev_mbI'm having a small déjà vu =)17:18
docaedothen we iterate from there to add extended data17:18
sskripnickbtw we have to expose glare anyways. we need it for glare-to-glare syndication17:18
docaedobut for switch to glare the goal should be basic feature compatability with current "api" of app catalog17:18
*** prateek has quit IRC17:19
sskripnickdocaedo: ok, I like it17:19
sskripnickso we need to emulate old api? but how we a going to create/edit assets?17:20
sskripnickthere is no yaml file anymore17:20
kzaitsev_mbthe issue here is that glare api != app-catalog api, although certain calls would be identical17:20
docaedono not exactly, sorry I'm probably not being clear17:20
kzaitsev_mbsskripnick: old api only had get )17:20
docaedoalso I was looking at the conversation on the channel earlier, and noting this image: https://dl.dropboxusercontent.com/u/13626875/app-catalog.png17:20
docaedokfox1111 had a point that made good sense17:21
docaedo"if we go with the top one, and glare looses all its steam, but we want to support our v2 api for a long time, we will have many more options with the bottom one."17:21
docaedo"if glare's a huge success and we never need to add any new stuff, we can make a v3 that just removes the proxy and wait for v2 to die off."17:21
docaedoso that was the conversation where we agreed it would make sense for app catalog to have it's own API, which is what sskripnick started with (and then I argued against, silly me!)17:22
docaedo(I have to apologize, have been involved in a lot of other stuff lately so took me a while to remember all the app-catalog stuff this morning!)17:23
sskripnick:)17:23
sskripnickokay. so I can just finish current implementation and we can merge it? (with glare only. no own database)17:24
docaedosskripnick: just to answer also regarding emulating old API, I do not think that's a critical goal - if it turns out to be possible without much effort (and if we are already writing a shim in front of glare API that might not be hard), we could try17:24
docaedosskripnick: yes, I tihnk you can continue with current implementation, no need to create additional database17:24
docaedoI think it makes sense to make glare work with minimal features, and adding on user comments, rating, etc. can come later17:25
sskripnickok. so django will be waiting %)17:25
*** ddieterly is now known as ddieterly[away]17:25
kzaitsev_mbsskripnick docaedo I'm 95% sure that it would be easy to implemenvt v1 api with glare v1 api17:26
kzaitsev_mband I'd like to disagree that it's not criticall17:26
kzaitsev_mbit would break (or at least stall) app-catalog-ui17:26
sskripnickit is easy, but why we need this? and how to use it?17:26
docaedosskripnick: I think django can wait - kzaitsev_mb what do you think about that?17:26
sskripnickif we use glare we should have a UI for adding/approving17:26
docaedokzaitsev_mb: yes you are right about that breaking app-catalog-ui - I guess you are right that it's critical17:27
kzaitsev_mbsskripnick: app-catalog-ui is a dashboard for a.o.o. It has been out for a while and breaking it doesn't sound good to me17:27
sskripnickoh i understand. its all about app-catalog-ui horizon17:27
kzaitsev_mbhorizon-dashboard for a.o.o17:27
sskripnickyes, sure we should implement it17:27
docaedokzaitsev_mb: do you agree that the additional functionality (rating, comments - basically stuff glare can't handle) can happen later?17:29
kzaitsev_mbif it ever becomes a problem (after all there is a huge jon file dump) — it can be optimised(cached) and deprecated gracefully.17:29
*** sdake has joined #openstack-meeting-317:29
kzaitsev_mbdocaedo: sure17:29
docaedokzaitsev_mb: yes I agree, creating that json from what is in glare should be really easy, and caching it and serving from api/v1 would keep us backwards compatible17:30
*** nkrinner is now known as nkrinner_afk17:30
sskripnickso for now we just need to finish the UI and deploy glare on subdomain and swift storage and memcached17:31
docaedo"swift storage"?  you mean just connect to external swift somewhere right?17:31
sskripnickyes17:31
docaedocool :)17:31
docaedoready for next argument?17:32
sskripnickyep17:32
docaedo#topic App Catalog API v2.0 spec and framework (flask+sqlalchemy, django, something else?)(sskripnick)17:32
*** openstack changes topic to "App Catalog API v2.0 spec and framework (flask+sqlalchemy, django, something else?)(sskripnick) (Meeting topic: app-catalog)"17:32
docaedooops17:32
docaedo#topic Artifacts verification (https://blueprints.launchpad.net/app-catalog/+spec/artifacts-verification )(sskripnick)17:32
*** openstack changes topic to "Artifacts verification (https://blueprints.launchpad.net/app-catalog/+spec/artifacts-verification )(sskripnick) (Meeting topic: app-catalog)"17:32
sskripnickthe idea it to be able to verify artifacts17:33
sskripnicklike change requests in gerrit17:33
sskripnick+v/-v from jenkins on every proposed artifact17:33
docaedoI appreciate the idea behind this, but it's going to require a HUGE effort, and can't work easily with the existing infra gate17:33
docaedoconsider that we need a "reference" cloud to start with, otherwise to test a simple application the gate would need to first deploy devstack, then fetch a huge image (some are over 2gb)17:34
docaedothen use murano for instance to build the heat stack17:34
docaedouse heat to deploy it17:34
docaedoand then eventually, somehow, "test" that17:34
sskripnickthere is some work-in-progress in murano team17:35
docaedoThat's the workflow we would follow right now if we were going to use the existing test infrastructure17:35
docaedoif we're just talking about third-party, and these things happening on some other cloud that already exists, I think it's great :)17:35
*** asettle has quit IRC17:35
docaedoand basically I am in agreement that this will be a really useful thing to add17:35
sskripnickit may be third party, or existing infra, or both17:36
docaedobut I don't think this is tied to the app-catalog17:36
kzaitsev_mbI'm thinking of examples and do not see any =) I mean pypi doesn't test python packages uploaded, does it? nor does docker hub or deb repos17:36
sskripnickwe need to support it to make it possible17:36
docaedoIt COULD be part of the app-catalog, but it's something next to it in a way, "providing the community a CI infrastructure for murano things"17:36
kzaitsev_mbyep, resonates well with what imarnat is driving17:37
docaedoI do get it, but I'm saying it does not need to start being tightly coupled to the app-catalog17:37
kzaitsev_mb(he has just returned from vacation AFAIK btw, just sharing =))17:37
docaedofor instance the repository split for murano that was talked about17:37
docaedotesting the apps that get added into the murano-apps repository - that's where the focus on this CI should be17:37
sskripnickwe can make possible to do the same for other artifact types17:38
kzaitsev_mbsskripnick: is the bp part of the ongoing work by imarnat on CI for murano-apps and other assets?17:38
sskripnickkzaitsev_mb: no17:38
sskripnickoh wait17:39
docaedohonestly I think that blueprint as it stands belongs under murano, not app-catalog17:39
sskripnickkzaitsev_mb: yes it is17:39
kzaitsev_mbyou got me confused17:39
kzaitsev_mb=)17:39
sskripnick-_-17:39
sskripnickok lets return to this later. we have enough work for today17:40
docaedomy point is that the app catalog can't test everything that comes into it, and the way different asset types will be tested will be very different :)17:40
docaedoI'll add my comments to the blueprint anyway, and we can at least discuss that way17:40
docaedothough I agree, definitely not something we need to cover today :)17:41
docaedo#topic Next steps for Glare integration17:42
*** openstack changes topic to "Next steps for Glare integration (Meeting topic: app-catalog)"17:42
docaedoJust want to know what sskripnick wants others to do to help out with the effort at this point :)17:42
kzaitsev_mbsskripnick: I'm not sure if the code should live in app-catalog =) it might be a separate project (at least a separate repo.) if murano is going to be one of the first asset types tested by this CI — I see little problem adding the repo under murano project17:43
kzaitsev_mbneeds to be discussed a bit =)17:43
kzaitsev_mbok, moving on )17:43
kzaitsev_mbsskripnick: any demands, things we can help you with?17:44
docaedo#action docaedo to play with login/logout/validate on http://r-ci.tk:8100/17:44
sskripnickI need some help with puppet. Everything else almost finished17:44
sskripnickOh, also I need some help with html/css17:44
sskripnickCurrently UI looks a bit ugly17:44
sskripnickand I can't make it better >_<17:45
*** parora has joined #openstack-meeting-317:45
docaedosskripnick: any specifics, be sure to ask on #openstack-app-catalog (might get a surprise help from kfox, never know!)17:45
sskripnicksounds good :)17:46
docaedoI will see what I can do about puppet deployment piece when I get back from leave17:46
sskripnickok thanks17:46
docaedo#action docaedo to look at "install glare with puppet" week of 8/2217:46
docaedoI think we are good :)  Anyone have anything else for today?17:47
*** prateek_ has quit IRC17:48
*** sarob has joined #openstack-meeting-317:48
*** mickeys has joined #openstack-meeting-317:48
* docaedo will wait at least another minute or two...17:48
*** tonytan4ever has joined #openstack-meeting-317:49
igormarnat_docaedo: Hi!17:49
*** piet_ has quit IRC17:49
igormarnat_Sorry, I'm a little bit late:)17:50
docaedoigormarnat_: hey there!17:50
*** lpetrut has joined #openstack-meeting-317:50
docaedohaha yeah we were about to endmeeting :P17:50
igormarnat_Not sure if you had a chance to discuss what exactly needs to be done to switch to new implementation which we have now in Beta17:50
*** mickeys_ has joined #openstack-meeting-317:50
igormarnat_Do we have etherpad about it, or smth like that?17:50
docaedono etherpad at the moment, next step is for me to write the puppet deployment bits, and then work with infra to get it testing with their trove and swift17:51
docaedoso we'd have a staging/test version up on openstack infra17:51
docaedoand there's some work to do on an API shim so the API endpoint exposed is not tied to glare but exposes same functionality (as well as duplicates v1 API)17:52
igormarnat_docaedo: got it. Do you need help with puppet?17:52
docaedowell I'm on leave next week so I won't get to it for a week and a half, if someone else wants to pick it up in the mean time and ping folks on #openstack-infra for help that would be fine17:52
*** mickeys has quit IRC17:53
docaedoexisting deploying stuff is at https://git.openstack.org/cgit/openstack-infra/puppet-apps_site - future changes should be patches to that repo17:53
*** prateek_ has joined #openstack-meeting-317:53
*** tonytan4ever has quit IRC17:54
docaedo(5 minutes left)17:55
*** SumitNaiksatam has joined #openstack-meeting-317:55
*** piet has joined #openstack-meeting-317:56
*** dkehn_ has quit IRC17:56
docaedoOK I think we're good now folks, thanks!17:56
*** parora has quit IRC17:56
*** rkukura has joined #openstack-meeting-317:57
sskripnickthanks. bye17:57
docaedo#endmeeting17:57
*** openstack changes topic to " (Meeting topic: ops_guide)"17:57
openstackMeeting ended Thu Aug 11 17:57:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-08-11-17.01.html17:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-08-11-17.01.txt17:57
openstackLog:            http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-08-11-17.01.log.html17:57
*** asettle has joined #openstack-meeting-317:57
*** Amit_ has joined #openstack-meeting-317:57
*** _sarob has joined #openstack-meeting-317:58
*** woodster_ has quit IRC17:59
*** Amit_ has left #openstack-meeting-317:59
*** sarob has quit IRC18:00
SumitNaiksatamrkukura: ivar-lazzaro igordcard: hi18:00
rkukurahi18:00
ivar-lazzarohi18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu Aug 11 18:00:54 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Aug_11th.2C_4th.2C_July_21st_201618:01
*** amitbose has joined #openstack-meeting-318:01
SumitNaiksatam#topic Quality of Service support via NSPs18:02
*** openstack changes topic to "Quality of Service support via NSPs (Meeting topic: networking_policy)"18:02
SumitNaiksatamamitbose: hi18:02
*** hemanthravi has joined #openstack-meeting-318:02
SumitNaiksatamigordcard: there?18:02
SumitNaiksatamhemanthravi: hi18:02
hemanthravihi18:02
amitbosehi18:02
SumitNaiksatamjust wanted to quickly address any pending issues that igordcard might be having with his patch (in case he is around)18:02
SumitNaiksatamprobably not18:03
SumitNaiksatami have commented on his patch18:03
SumitNaiksatammoving on18:03
SumitNaiksatampatch btw is #link https://review.openstack.org/#/c/30170118:03
SumitNaiksatam#topic L3-Policy mapping to Address Scope & Subnetpool18:04
*** openstack changes topic to "L3-Policy mapping to Address Scope & Subnetpool (Meeting topic: networking_policy)"18:04
SumitNaiksatam#link https://review.openstack.org/#/c/34392918:04
*** julim has joined #openstack-meeting-318:04
SumitNaiksatamrkukura: thanks for the review comments, (and amitbose thanks for your review earlier as well)18:04
SumitNaiksatamrkukura: i saw your main comment earlier in the morning, and then noticed a few more comments just a few minutes back18:05
rkukuraone main issue, and several minor ones18:05
SumitNaiksatamrkukura: i think your more recent comments are mostly aligned with your main comment L18118:05
rkukuraright18:05
SumitNaiksatamrkukura: yeah so lets go over that18:05
SumitNaiksatamothers, please do chime in18:06
rkukurathe main issue is with the 1-to-mainy mapping to subnetpools18:06
SumitNaiksatamrkukura: right18:06
SumitNaiksatamrkukura: so the requirement there is not purely for prefix scaling purposes18:06
rkukuraIt doesn’t seem necessary, and might add signficiant complexity18:06
SumitNaiksatamrkukura: i agree it adds complexity18:06
SumitNaiksatamrkukura: but there are use cases where you would need to associate explicitly associate subnetpools (as opposed to modifying existing subnetpools)18:07
rkukurain particular, I’m worried about how this plays with neutron’s requirement that all subnets on a network come from the same subnetpool, if any of them are from a subnetpool18:07
SumitNaiksatamrkukura: so the requirement is to be able to associate one or more subnetpool resources, and not just add prefixes18:08
ivar-lazzarorkukura: isn't the requirement that they come from the same address scope?18:08
rkukuraI’m not sure I see why adding a new subnetpool is ever preferable to adding a prefix to an existing subnetpool18:08
ivar-lazzarorkukura: does it have to be the same subnetpool? that's odd18:08
rkukuraOn a network, it has to be the same subetpool18:09
SumitNaiksatamrkukura: i believe you are only looking at the scaling use case18:09
rkukuraI’m not sure about on a router, but I expect that to be based on address_scope18:09
rkukuraI am not sure what other use cases apply18:09
rkukurascaling being needing more subnets, I think18:09
ivar-lazzaroI guess visibility is another concern18:09
*** dkehn_ has joined #openstack-meeting-318:10
SumitNaiksatamrkukura: however, the user might be explicitly creating the subnetpool18:10
SumitNaiksatamivar-lazzaro: yeah, the l3p sharing use case18:10
rkukuraSure, the user can explicitly create a subnetpool and use it to create an L3P18:10
SumitNaiksatamamitbose was pointing out that earlier as well18:10
SumitNaiksatamthe l3p is shared and each tenant creates its own subnetpool and associates with the l3p18:11
ivar-lazzarowith a single shared VRF, you still might want to limit the subnets for each tenant18:11
rkukuraI vaguely recall some use cases being mentioned in discussion, which I didn’t quite undertand at the time, but I don’t see any of this in the spec18:11
rkukuraSo why is it necessary to share an L3P but not share the subnetpool?18:11
SumitNaiksatamrkukura: okay, i will add a sentence on that use case to clarify18:11
*** vgridnev has quit IRC18:11
*** lpetrut has quit IRC18:11
ivar-lazzarowhich could be accomplished by looking at the subnetpool ownership/sharing18:11
ivar-lazzarorkukura: ^^18:12
rkukuraDo we really need that complexity?18:12
SumitNaiksatamrkukura: why would you force the subnetpool to be shared?18:12
ivar-lazzaroI think that is the use case, whether or not it can really be accomplished is to be evaluated18:12
rkukuraIf you need to share it, share the L3P18:12
rkukuraIf you don’t need to share it, don’t share the L3P18:12
ivar-lazzarodoesn't seem really complex does it? You have a space of non overlapping IPs between your tenants18:13
*** lpetrut has joined #openstack-meeting-318:13
ivar-lazzaropretty much like having overlapping_ips set to false18:13
ivar-lazzarobut you still need each tenant to use the assigned subnet18:13
ivar-lazzaroIn Neutron you would do that by having a shared AS18:14
ivar-lazzaroand private SP18:14
rkukuraFirst, if we do need multiple subnetpools in an L3P, they would have to have the same AS, and therefore no overlap18:14
ivar-lazzarodoes it make sense?18:14
amitboseI'm not convinced if having multiple subnetpools is adding too much complexity, but it does allow us to address more use-cases18:14
*** numans has quit IRC18:14
SumitNaiksatamrkukura: right, they would have to be the same AS18:14
rkukuraWhy not just have each tenant have a non-shared L3P, with all of these sharing an AS?18:14
ivar-lazzarorkukura: you might want to run cross-tenant traffic without NAT18:15
ivar-lazzaroat least that's my guess18:15
*** amotoki has quit IRC18:15
ivar-lazzaroin any case, I think we should at least be able to accomodate these use cases18:15
ivar-lazzaromeaning that we could still have a list of subnetpools18:15
ivar-lazzarobut limit to 1 for now18:15
SumitNaiksatamrkukura: the requirement is to be able to share the construct at the GBP resource level18:16
ivar-lazzaroso that we can remove the constraint once we see fit without breaking compatibility18:16
SumitNaiksatamrkukura: i am referring to the l3p18:16
*** vgridnev has joined #openstack-meeting-318:16
rkukuraMaybe some of the semantics we have on L3P should be moved to AS18:16
ivar-lazzaro(but I agree with the _v4 _v6 comment)18:16
SumitNaiksatamrkukura: for somebody purely driving the GBP workflow, the fact that AS is shared is not even visible, unless the L3P is shared18:17
SumitNaiksatamivar-lazzaro: v4 and v6 separation is also not that big of a deal18:17
*** lpetrut has quit IRC18:17
SumitNaiksatamivar-lazzaro: it probably looks more cleaner18:17
SumitNaiksatamivar-lazzaro: but there is hardly any extra computation cost if its a single list18:17
rkukuraThe _v4, _v6 thing is a more minor issue18:18
SumitNaiksatamwe will be filtering based on the address_scope id18:18
ivar-lazzaroSumitNaiksatam: yeah, that's the kind of thing that becomes easily incompatible once you release the driver... So we probably want to make sure we take the right decision right away18:18
SumitNaiksatamrkukura: but i can make that change if it looks more cleaner from an API perspective18:18
rkukuraWhat really bothers me is that we will require some set of SPs to have the same AS, but neutron allows the SP->AS association to be mutated at will18:19
SumitNaiksatamrkukura: that is separate issue18:19
rkukuraAnd we will also require the L3P to be associated with that same AS18:19
SumitNaiksatamwhich needs to be addressed, regardless of subnetpool list or no18:19
SumitNaiksatam*not18:19
ivar-lazzaroIf we have a single SP we theoretically don't care about the AS18:20
SumitNaiksatamfor SPs already associated with an L3P we will have to in some way disallow update of AS18:20
rkukuraIt just seems much cleaner to me to say that an L3P has exctly one SP for each family, and18:20
ivar-lazzarobut I'm very nervous about taking this route and be burned later18:20
rkukurathe AS is whatever that SP points to18:20
ivar-lazzaroI'd rather get the model right, and maybe limit the length of that list to 118:20
SumitNaiksatamrkukura: at the neutron model level that is the only change, but it will not be as trivial for the backend because things will have to be rewired to change the AS mapping18:21
rkukuraI’m just not (yet) convinced that a list of SPs is the right model18:21
SumitNaiksatamrkukura: which may or may not be possible18:21
ivar-lazzarorkukura: how would you solve the use case we discussed above with the current model?18:22
*** amotoki has joined #openstack-meeting-318:22
rkukuraWe need to handle updates to a SP’s AS for neutron18:22
SumitNaiksatamrkukura: so when the update to the SP happens, GBP would have to interpose anyway18:22
*** dtroyer has left #openstack-meeting-318:22
ivar-lazzarowe might say we won't support those, but it seems a bit risky considering we already have users that have a big single shared VRF18:22
rkukuraIs the use case that you somehow want multiple tenants to have different SPs but share an L3P/AS?18:22
SumitNaiksatamrkukura: right18:23
rkukuraSo why do the different tenants need their own SPs?18:23
ivar-lazzaroEach tenant has different subnets assigned. But they are in the same VRF to allow cross traffic when needed18:23
rkukuraI agree if they are sharing the L3P/AS, they will be sharing the VRF18:23
rkukuraI’d just like to understand why they can’t also share the SP?18:24
ivar-lazzarorkukura: because he who design the network is not the same as who run the applications18:24
ivar-lazzaroalso, address space separation is good to avoid a tenant to be too noisy18:24
rkukuraWhy would ether of thee care which SP some tenant uses?18:24
SumitNaiksatamrkukura: so that one tenant does not use the other tenants IPs?18:24
ivar-lazzarowithout necesserely enforcing quotas18:25
*** ihrachys has quit IRC18:25
rkukurathe SPs do enforce quotes, based on individual IPs for v4 and based on /64 spaces for v618:25
ivar-lazzaroSumitNaiksatam: that is already enforced by using the same shared VRF18:25
ivar-lazzaroI see two main advantages:18:26
*** ddieterly[away] has quit IRC18:26
SumitNaiksatamivar-lazzaro: how is it enforced by using the same shared VRF??18:26
ivar-lazzaro- 1) Accounting traffic by IP18:26
ivar-lazzaroSumitNaiksatam: using the same VRF you can't have overlapping IPs. even if you have one single shared SP18:26
SumitNaiksatamivar-lazzaro: i am not talking about overlapping IPs18:27
*** mickeys_ has quit IRC18:27
ivar-lazzaro2) slice the subnets to prevent a tenant from growing too much18:27
*** mickeys has joined #openstack-meeting-318:27
SumitNaiksatamivar-lazzaro: my question to rkukura was more rhetorical18:27
ivar-lazzaroOh ok, I misinterpreted18:28
*** pvaneck has joined #openstack-meeting-318:28
*** sskripnick has left #openstack-meeting-318:28
ivar-lazzaroI guess rkukura question is more like "why would anyone care about which tenant uses which subnet"18:28
ivar-lazzarogiven a shared routing domain18:28
SumitNaiksatamivar-lazzaro: good points18:29
SumitNaiksatam basically the summary is that we want to be able to cleanly separate the applications (and the subnets they use) in a shared address space18:29
rkukuraRegarding ivar-lazzaro’s 2), I’m not sure I understand this. If the tenant owns any SP, they can always add new prefixed to it. Only quotas prevent them from doing that.18:29
ivar-lazzarorkukura: can they? even if created by an admin?18:29
rkukuraI’m not even sure the quote prevents them from adding the prefix, just from allocatiing subnets18:29
ivar-lazzarobut even if they can, other tenants won't run out of IPs18:30
SumitNaiksatamand to support the range of use cases that fall under this category, association to a list of SPs seems like the right thing to model18:30
rkukuraIf the admin creates it using the tenant’s tenant_id, its the same as if the tenant created it18:30
ivar-lazzarobecause they already have their allocated slice18:30
rkukuraSo what about the fact that SPs cannot be mixed on a network?18:30
ivar-lazzaroso you would be able to grow, but not to "invade"18:30
SumitNaiksatamivar-lazzaro: i like the use of “invade” ;-)18:31
rkukuraHow is the user supposed to know which of this list of SPs is even being used for the L2P they want to use?18:31
SumitNaiksatamrkukura: that is a good point18:31
ivar-lazzarorkukura: isn't that covered via resource visibility?18:31
*** ddieterly has joined #openstack-meeting-318:31
SumitNaiksatamivar-lazzaro: in this case the user would see the other SPs as well18:32
SumitNaiksatamivar-lazzaro: but wont be able to use them18:32
ivar-lazzaroIf the SPs are not marked as shared, doing a "show" on the L3P would only list the ones you can have access to18:32
rkukuraDo we even know whether neutron prevents the prefixes within one SP from overlapping with the prefixes in another SP when the two SPs share an AS? I suspect the enforcement is at subnet allocation instead, but could be wrong.18:32
ivar-lazzarohow?18:32
*** toddjohn has joined #openstack-meeting-318:32
ivar-lazzaroEvery non-admin query is filtered by ownership or shareability18:32
ivar-lazzaroAFAIR18:33
SumitNaiksatamivar-lazzaro: because there is no resource visibility being enforced on the SPs’ list attribute when you do a show on the L3P18:33
rkukuraSo each user of the shared L3P sees different results for the same attribute? I’d think they would see the IDs, but not be able to show the resource the ID identifies.18:33
ivar-lazzaroSumitNaiksatam: I see what you mean, that's because those values are loaded by the L3P join18:33
ivar-lazzarorkukura: it does prevent it by spec18:34
ivar-lazzarorkukura: not sure if it's actually implemented18:34
rkukuraivar-lazzaro: Prevent prefix overlap within an AS?18:34
ivar-lazzarorkukura: yeah18:34
SumitNaiksatamivar-lazzaro: i dont know of a way to enforce that with the current policy.json mechanism18:34
ivar-lazzaroThat's why I believe we should limit the list to 1 right now18:34
ivar-lazzarowe know there are valid use cases18:35
ivar-lazzarobut we need to get the implementation right18:35
ivar-lazzaroexcept that the implementation can be changed later, the model is a bit trickier18:35
SumitNaiksatamivar-lazzaro: you are probably suggesting that this filtering can be done in the “make_dict”?18:35
rkukuraGiven the flexibility, I’m sure we’d find use cases that can take advantage of the flexibiltiy. But the question I have is whether these same use cases can be solved better by other means.18:35
SumitNaiksatamrkukura: if that is an open ended question, i think we have to go with an approach that readily solves those use cases18:36
ivar-lazzarorkukura: how would you address those cases with a single SP?18:36
*** mickeys has quit IRC18:37
ivar-lazzarorkukura: I'm ok even with just having a plan, ad long as we know that we won't need to come back and break the model compatibility18:37
rkukuraI’d use quotes to address hording18:37
ivar-lazzarowhat about accounting?18:37
*** mickeys has joined #openstack-meeting-318:38
SumitNaiksatamrkukura: “hording”?18:38
rkukuraI’m not sure if subnetpool prefixes are ever really the best/only solution for accounting, but maybe18:38
ivar-lazzaroeven though that's not the right word18:38
ivar-lazzaro"accounting"... It's more like IP identity18:38
SumitNaiksatamoh you mean “quotas to address hoarding”…nevermind18:38
rkukuraWe can certainly map the individual ports to tenants18:38
rkukurahoarding is what I meant18:39
ivar-lazzaroaccounting is more of a commercial term I guess, what I mean is for an operator to be able to know the identity of the traffic by looking at the IP18:39
SumitNaiksatamrkukura: ivar-lazzaro: i would prefer to not rat hole into the quotas/hoarding/invading/accounting discussion18:39
ivar-lazzaro(with IPv6, sometimes they even do that by host)18:39
*** chandanc_ has joined #openstack-meeting-318:39
SumitNaiksatamsince the separation of concerns seems like a more prominent use case to me18:39
SumitNaiksatamthe accounting aspects are probably implementation specific18:40
SumitNaiksatamsome support might be currently available and some might not be18:40
SumitNaiksatambut that discussion side steps the sharding paradigm concerns18:40
ivar-lazzaroI think I just misused the word accounting18:40
SumitNaiksatamsharding -> sharing18:41
ivar-lazzarobut what I meant is that the operator can identify the tenant generating traffic by just looking at the source IP18:41
rkukuraI’m not going to -2 the spec based on this one-to-many mapping to SPs. I’m not comfortable with it, and would rather start simple if possible, but if you guys are confident it is implementable and useful, I’m don’t have any evidence to prove you wrong18:41
*** mickeys has quit IRC18:42
ivar-lazzarorkukura: isn't limiting the list to "1" simple enough to start?18:42
*** chandanc has quit IRC18:42
SumitNaiksatamrkukura: 1-1 is restrictive and leads to a incompatible change down the line18:42
ivar-lazzarowe stay on the safe side as far as the model is concerned, but we keep the implementation simple18:42
SumitNaiksatam1-many is less restrictive though we dont have to implement from get-go (stating the obvious)18:42
ivar-lazzaroI think it's a win-win18:42
rkukuraTo me, the key thing is that we don’t introduce potential inconsistencies that we then have to figure out how to enforce. Even just storing both the AS and a single SP in the DB leads to those potential inconsistencies.18:43
ivar-lazzarorkukura: I thought that wasn't too hard to enforce for a single SP, but I might be wrong18:45
SumitNaiksatamrkukura: i will make it explicit in the spec that for a SP associated with a L3P, you should not be changing the AS association18:45
rkukuraIf we were really confident a single SP per address family per L3P would suffice, then I’d argue we don’t store the AS explicitly, and don’t have to worry about maintaining consistency.18:45
SumitNaiksatamrkukura: we will try to enforce this as well, but the details of that wont be part of this spec18:45
rkukuraIn neutron, you are allowed to change the SP/AS association.18:45
ivar-lazzarorkukura: but you can validate this using a gbp mechanism driver18:45
ivar-lazzarowhich will probably be needed down the line anyways18:46
SumitNaiksatamrkukura: yes you are, and you can change the association for SPs not associated with an L3P18:46
rkukuraI’d prefer that we just live with that and have the L3P reference a single SP per AF, and use that SP’s AS (if there is one). But clearly we don’t have concensus on this.18:46
SumitNaiksatamrkukura: but i feel you are leaning to towards 1-many :-P18:47
ivar-lazzarothe model rkukura is proposing is definitively easier to manage and implement... But I'm really worried about the lack of flexibility18:47
rkukuraI’ve convinced myself I’m not going to convince either of you ;)18:47
SumitNaiksatamyes, its easier to implement with one SP18:48
*** galstrom_zzz is now known as galstrom18:48
SumitNaiksatamwhat does everyone feel about modeling separate lists for v4 and v6 SPs?18:48
SumitNaiksatamversus just having one list?18:48
ivar-lazzarowould that be possible to not include the AS as long as we limit the SPs to 1?18:48
ivar-lazzaroonce the request arise, would that be even possible to change the current model to add the AS id?18:49
ivar-lazzaroprobably not, it would require special migration for the existing AS18:49
rkukuraI’d suggest we define the AS attribute in the API, but not store it in the DB18:49
SumitNaiksatamivar-lazzaro: i believe there is a requirement up front to be able to create L3P with an explicit AS (everything else is implicitly created)18:49
rkukuraSo you can create an L3P passing in an existing AS and a prefix, et.c18:50
rkukuraetc.18:50
*** aarefiev_ has joined #openstack-meeting-318:50
ivar-lazzaroSumitNaiksatam: yeah but we could read that dynamically. However, the moment we need to manage multiple SPs we would need to "fix" that attribute18:51
SumitNaiksatamrkukura: you cannot lazily create SPs unless you store the AS in the DB (at least in the explicit AS case)18:52
SumitNaiksatamivar-lazzaro: i am saying, the user provides an explicit AS and not SP18:53
rkukuraDo we plan to create the SPs lazily? Assuming a shared AS that enforces non-overlap between prefixes, it would seem we would need to create the SP immediately to validate it.18:54
*** lblanchard has quit IRC18:54
ivar-lazzarorkukura: right18:54
SumitNaiksatamrkukura: i havent completely thought through, but by not persisting the AS, we completely take away that option18:54
SumitNaiksatamrkukura: also what happens if the last SP is deleted18:55
SumitNaiksatamtime check - we have 5 mins18:56
rkukuraWe are running short on time, and I’ve said my piece, so I am happy to leave it up to SumitNaiksatam to decide which approach to take, and I will support that.18:56
SumitNaiksatammy earlier question - “: what does everyone feel about modeling separate lists for v4 and v6 SPs?”18:56
ivar-lazzaroSumitNaiksatam: +1 for that18:56
rkukura+118:56
SumitNaiksatamokay so separate lists18:57
SumitNaiksatamso i will respin a new version of the spec in line with the discussion here and address rkukura’s other comments18:57
ivar-lazzaroman that was quick18:57
rkukurasounds good18:57
SumitNaiksatamrkukura: ivar-lazzaro amitbose thanks for the passionate engagement on this! ;-P18:58
rkukuracovered the whole agenda ;)18:58
SumitNaiksatam#topic Open Discussion18:58
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:58
igordcardI'm here now18:58
SumitNaiksatamwe havent had open discussion for a while18:58
SumitNaiksatamah igordcard right on cue18:58
SumitNaiksatamigordcard: let me know if you have furhter problems with your patch, we can touch base offline18:59
igordcardyeah I arrived a few mins ago but wasn't waiting for the open18:59
igordcardthere was some other issue with the exercise but I'm now on vacation18:59
igordcardI will further look into it in a couple weeks is that okay?18:59
SumitNaiksatamigordcard: sure np, enjoy your vacation18:59
*** kzaitsev_mb has quit IRC19:00
igordcardthanks19:00
SumitNaiksatamalrighty thanks everyone for joining today!19:00
SumitNaiksatambye!19:00
ivar-lazzaroadieu!19:00
igordcardbye bye19:00
rkukurathanks SumitNaiksatam19:00
rkukurabye19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to " (Meeting topic: ops_guide)"19:00
openstackMeeting ended Thu Aug 11 19:00:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-08-11-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-08-11-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-08-11-18.00.log.html19:00
*** rkukura has left #openstack-meeting-319:00
*** hemanthravi has quit IRC19:00
*** shamail has joined #openstack-meeting-319:01
shamailAnyone here for the AUC meeting?19:01
*** MeganR has joined #openstack-meeting-319:01
shamailHi MeganR19:02
*** amitbose has left #openstack-meeting-319:02
MeganRHi19:02
shamailI think it’s just us, let’s skip the meeting for today?19:03
MeganRhonestly, that is a great idea!  :)19:03
shamailI didn’t have much on the agenda besides updates from action items19:03
shamailSounds good.  I didn’t get to any of mine :(19:03
MeganRand I haven't made much progress on my action items!19:03
MeganR:)19:03
shamailAlrighty, see you next week!19:03
MeganRbye!19:04
*** shamail has left #openstack-meeting-319:04
*** ivar-lazzaro has quit IRC19:04
*** MeganR has quit IRC19:04
*** ivar-lazzaro has joined #openstack-meeting-319:04
*** fifieldt has quit IRC19:06
*** gouthamr-afk has quit IRC19:11
*** gouthamr-afk has joined #openstack-meeting-319:13
*** mickeys has joined #openstack-meeting-319:15
*** VW has quit IRC19:15
*** VW has joined #openstack-meeting-319:16
*** fifieldt has joined #openstack-meeting-319:17
*** aarefiev_ has quit IRC19:20
*** Sukhdev has joined #openstack-meeting-319:22
*** chandanc_ has quit IRC19:22
*** vhoward has joined #openstack-meeting-319:23
*** maishsk has joined #openstack-meeting-319:29
*** piet has quit IRC19:29
*** bknudson has left #openstack-meeting-319:31
*** piet has joined #openstack-meeting-319:32
*** ddieterly is now known as ddieterly[away]19:33
*** tonytan4ever has joined #openstack-meeting-319:35
*** f13o has joined #openstack-meeting-319:37
*** vgridnev has quit IRC19:38
*** tonytan4ever has quit IRC19:40
*** prateek_ has quit IRC19:40
*** alexismonville has joined #openstack-meeting-319:41
*** SumitNaiksatam has quit IRC19:41
*** SumitNaiksatam has joined #openstack-meeting-319:46
*** kzaitsev_mb has joined #openstack-meeting-319:46
*** neiljerram has joined #openstack-meeting-319:50
*** neiljerram has quit IRC19:51
*** tonytan4ever has joined #openstack-meeting-319:52
*** ivar-lazzaro has quit IRC19:53
*** lpetrut has joined #openstack-meeting-319:55
*** dconde has joined #openstack-meeting-319:56
*** dconde has quit IRC19:56
*** ddieterly[away] is now known as ddieterly19:57
*** piet has quit IRC20:02
*** ivar-lazzaro has joined #openstack-meeting-320:08
*** maishsk_ has joined #openstack-meeting-320:11
*** maishsk has quit IRC20:13
*** maishsk_ is now known as maishsk20:13
*** toddjohn has quit IRC20:14
*** banix has quit IRC20:14
*** toddjohn has joined #openstack-meeting-320:14
*** vhoward has quit IRC20:16
*** DevonBoatwright has joined #openstack-meeting-320:16
*** toddjohn has quit IRC20:18
*** amotoki has quit IRC20:20
*** kzaitsev_mb has quit IRC20:20
*** gouthamr-afk has quit IRC20:26
*** toddjohn has joined #openstack-meeting-320:27
*** toddjohn has quit IRC20:29
*** toddjohn has joined #openstack-meeting-320:29
DevonBoatwright#startmeeting ops_guide20:30
openstackMeeting started Thu Aug 11 20:30:16 2016 UTC and is due to finish in 60 minutes.  The chair is DevonBoatwright. Information about MeetBot at http://wiki.debian.org/MeetBot.20:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:30
*** openstack changes topic to " (Meeting topic: ops_guide)"20:30
openstackThe meeting name has been set to 'ops_guide'20:30
DevonBoatwrightHey everyone.. is anyone here today for the meeting?20:30
DevonBoatwrightShilla is out of town at the moment.20:30
DevonBoatwrightSo I'm going to run the meeting20:30
*** lpetrut has quit IRC20:31
DevonBoatwrightAnd.... maybe I am an hour early20:32
DevonBoatwrightI'll be back in an hour!20:32
DevonBoatwright#endmeeting20:32
*** openstack changes topic to " (Meeting topic: ops_guide)"20:32
openstackMeeting ended Thu Aug 11 20:32:17 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-20.30.html20:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-20.30.txt20:32
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-20.30.log.html20:32
*** beagles is now known as beagles_biab20:38
*** mickeys has quit IRC20:39
*** toddjohn has quit IRC20:44
*** toddjohn has joined #openstack-meeting-320:45
*** sergio_nubeliu has quit IRC20:45
*** iyamahat has quit IRC20:45
*** yamahata has quit IRC20:45
*** tonytan4ever has quit IRC20:46
*** pt_15 has quit IRC20:46
*** toddjohn has quit IRC20:47
*** toddjohn has joined #openstack-meeting-320:47
*** sdake has quit IRC20:48
*** toddjohn_ has joined #openstack-meeting-320:48
*** armax has joined #openstack-meeting-320:49
*** toddjoh__ has joined #openstack-meeting-320:49
*** toddjohn has quit IRC20:52
*** toddjohn_ has quit IRC20:53
*** lpetrut has joined #openstack-meeting-320:56
*** mickeys has joined #openstack-meeting-320:58
*** f13o has quit IRC20:59
*** banix has joined #openstack-meeting-321:00
*** kzaitsev_mb has joined #openstack-meeting-321:02
*** banix has quit IRC21:03
*** banix has joined #openstack-meeting-321:04
*** yamahata has joined #openstack-meeting-321:06
*** ddieterly has quit IRC21:06
*** kzaitsev_mb has quit IRC21:11
*** seldenr has quit IRC21:12
*** bknudson has joined #openstack-meeting-321:14
*** kzaitsev_mb has joined #openstack-meeting-321:16
*** sdake has joined #openstack-meeting-321:16
*** maishsk has quit IRC21:21
*** coolsvap has quit IRC21:21
*** tonytan4ever has joined #openstack-meeting-321:21
*** iyamahat has joined #openstack-meeting-321:24
*** baoli has quit IRC21:25
*** woodster_ has joined #openstack-meeting-321:27
*** maishsk has joined #openstack-meeting-321:29
DevonBoatwright#startmeeting ops_guide21:30
openstackMeeting started Thu Aug 11 21:30:38 2016 UTC and is due to finish in 60 minutes.  The chair is DevonBoatwright. Information about MeetBot at http://wiki.debian.org/MeetBot.21:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:30
*** openstack changes topic to " (Meeting topic: ops_guide)"21:30
openstackThe meeting name has been set to 'ops_guide'21:30
DevonBoatwrightHello everyone!21:31
darrenchello!21:31
DevonBoatwrightIs there anyone here now? I accidentally started the meeting an hour early a bit ago21:31
DevonBoatwrightOh hi darren!21:31
DevonBoatwrightAnyone else here?21:32
darrencIt doesn't look like it21:32
*** sdake has quit IRC21:33
DevonBoatwrightHmm.21:33
DevonBoatwrightWant to still go ahead with the meeting?21:33
darrencwe could wait a few minutes21:33
DevonBoatwrightYea.. okie21:34
* darrenc quickly updates the agenda21:34
*** rcaballeromx has joined #openstack-meeting-321:35
DevonBoatwrightLOL! I noticed that from before!21:36
DevonBoatwrightOK.. so...21:39
DevonBoatwrightMaybe we should just get started?21:39
DevonBoatwrighton our one sided conversation? heehee21:39
DevonBoatwrightDid anyone else join?21:39
darrencIs it worthwhile?21:39
rcaballeromxI am here.21:39
DevonBoatwrightOh hello!21:39
rcaballeromxHi.21:39
DevonBoatwrightdarren, I am still showing agenda for July. Is it updated?21:40
rcaballeromxMaybe I am out of line, but what is the purpose of this meeting?21:41
darrencrefresh your page now21:41
darrenchi rcaballeromx21:41
rcaballeromxHi darrenc21:41
darrencessentially discuss the progress of the Ops Guide and Arch Guide in relation to the newton deliverables21:42
rcaballeromxOk, got it, thanks.21:43
DevonBoatwright#topic Previous meeting action items21:43
*** openstack changes topic to "Previous meeting action items (Meeting topic: ops_guide)"21:43
DevonBoatwrightthere's the bug spotlight. #link https://bugs.launchpad.net/openstack-manuals/+bug/145776721:43
openstackLaunchpad bug 1457767 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Fix released] - Assigned to KATO Tomoyuki (kato-tomoyuki)21:43
DevonBoatwrightOh that;s cool.. I've seen it pop up who the bug is assigned to21:44
DevonBoatwright#link https://bugs.launchpad.net/openstack-manuals/+bug/145777021:44
openstackLaunchpad bug 1457770 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Confirmed]21:44
darrencyep, so we've had some volunteers to help out with the bugs21:44
darrencwhich is great21:44
DevonBoatwright#link https://bugs.launchpad.net/openstack-manuals/+bug/145776821:44
openstackLaunchpad bug 1457768 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Confirmed]21:44
DevonBoatwrightYes, that's awesome!21:45
DevonBoatwright#link https://bugs.launchpad.net/openstack-manuals/+bug/149911421:45
openstackLaunchpad bug 1499114 in openstack-manuals "Document tools for Network Troubleshooting" [Undecided,Fix released]21:45
* rcaballeromx is looking at those...21:45
darrencHere's one I'm working on: https://bugs.launchpad.net/openstack-manuals/+bug/135972221:46
openstackLaunchpad bug 1359722 in openstack-manuals "Show complete workflow when provisioning an instance" [Wishlist,In progress] - Assigned to Darren Chan (dazzachan)21:46
*** toddjoh__ has quit IRC21:47
darrencbut I'll need someone who understands the topic in more detail to help21:47
darrencI've a pinged a few ppl21:47
DevonBoatwrightok. Yes, these all look more technical21:48
DevonBoatwrightI haven't had much success in finding or recruiting people to help. Sorry.21:48
rcaballeromxBug 1499114 looks like something I can do.21:49
openstackbug 1499114 in openstack-manuals "Document tools for Network Troubleshooting" [Undecided,Fix released] https://launchpad.net/bugs/149911421:49
DevonBoatwrightOh nice! That would be great21:49
DevonBoatwrightShould we move on or any questions about the bugs?21:50
darrenchmm, why does it say "Fixed released"?21:50
darrencIt's not fixed21:52
DevonBoatwrightInteresting. Can it be changed back?21:52
DevonBoatwrightIt doesn't let me edit the status of it21:52
darrencyep, done21:52
*** kzaitsev_mb has quit IRC21:52
DevonBoatwrightCool. Shall we move on?21:53
DevonBoatwright#topic Ops Guide21:53
*** openstack changes topic to "Ops Guide (Meeting topic: ops_guide)"21:53
darrencone thiong21:53
darrencthing*21:53
DevonBoatwrightOh.. whoops.21:53
*** kzaitsev_mb has joined #openstack-meeting-321:54
DevonBoatwright#topic Previous meeting action items21:54
*** openstack changes topic to "Previous meeting action items (Meeting topic: ops_guide)"21:54
darrencrcaballeromx: you can get in touch with edgar magana if you need help21:54
darrencwith that bug21:54
rcaballeromxWill do.21:55
darrencthanks :)21:55
rcaballeromxI am assigning it to me.21:55
DevonBoatwrightdarren.. do I do the action item tag at the end of the meeting or can I do it now?21:55
darrenccool, thanks21:55
*** asettle has quit IRC21:55
*** rtheis has quit IRC21:55
darrencyou can do it now21:55
darrenc:)21:55
DevonBoatwright#action rcaballeromx to pick up bug 149911421:55
openstackbug 1499114 in openstack-manuals "Document tools for Network Troubleshooting" [Undecided,Confirmed] https://launchpad.net/bugs/1499114 - Assigned to Rodrigo Caballero (rodrigo-caballero-abraham)21:55
DevonBoatwrightokie. Done. Should I change topic now?21:56
darrencsure21:57
DevonBoatwright#topic Ops Guide21:57
*** openstack changes topic to "Ops Guide (Meeting topic: ops_guide)"21:57
DevonBoatwrightSo there is a bullet here about providing more Enterprise ops documentation21:57
DevonBoatwrightDarren, maybe you can chat more about that?21:59
rcaballeromxWhat exactly does that entail?21:59
*** uxdanielle has quit IRC21:59
darrencyeah, shilla mentioned she was going to do that21:59
*** njohnston is now known as njohnston_21:59
darrencrcaballeromx: shilla has been providing enterpise ops documentation in a google doc22:00
DevonBoatwrightok. She is at a Mirantis conference right now so couldn't be at the meeting.22:00
*** gouthamr has quit IRC22:00
rcaballeromxOk.22:00
darrencI've been extracting contact and migrating it to the ops guide22:01
*** gouthamr has joined #openstack-meeting-322:01
darrenccontent*22:01
darrenctroubleshooting content seems to generate a lot of input from operators22:02
darrencDevonBoatwright: can you put that as an action item for shilla?22:02
DevonBoatwrightSure thing.. action to provide more enterprise ops documentation in google doc?22:03
darrencyep, thanks22:03
DevonBoatwright#action Shilla to provide more enterprise ops documentation in google docs22:04
DevonBoatwright#topic Arch Guide22:04
*** openstack changes topic to "Arch Guide (Meeting topic: ops_guide)"22:04
DevonBoatwrightSo there is a work items wiki page here: #link  https://wiki.openstack.org/wiki/Architecture_Design_Guide_restructure_work_items22:05
*** ddieterly has joined #openstack-meeting-322:05
*** VW has quit IRC22:05
darrencSo the arch guide working group has been meeting up weekly22:05
*** VW has joined #openstack-meeting-322:05
rcaballeromxAre any of the chapters already done?22:06
darrencthe plan is to pair up sme/writer and focus on a few areas in the Arch Guide22:06
darrenc...in short sprints. Dates TBD22:07
*** dimtruck is now known as zz_dimtruck22:07
darrencrcaballeromx: not yet22:07
*** gouthamr has quit IRC22:08
rcaballeromxOk, so that content does not exist yet, correct?22:08
rcaballeromxSorry for the questions, but I just want to make sure I follow properly.22:08
darrencYes there is some content22:08
darrencnp22:09
*** tonytan4ever has quit IRC22:09
darrencThere is an Arch Guide that's published, but we are restructuring and rewriting the guide22:09
rcaballeromxI get that.22:10
darrencWe attempted to do this in Mitaka, but didn't quite get there22:10
*** rama_y has quit IRC22:10
darrencand then some cloud architects have come onboard to help22:10
darrencand proposed a new spec for Newton22:11
darrencSo we are working on the guide based on the spec22:11
darrenclet me find the link22:11
*** rbak has quit IRC22:11
rcaballeromxI would consider Chapter 2 Use Cases to be the most crucial.22:11
rcaballeromxHowever, no one seems to be on it, or am I reading the wiki wrong?22:12
darrencyeah, there is some content in there22:13
*** rama_y has joined #openstack-meeting-322:13
rcaballeromxOk.22:13
darrencI've been migrating mitaka changes in the relevant section22:13
darrencsections*22:13
rcaballeromxdarrenc: Feel free to assign me some stuff where you think I can help.22:13
darrencthat would be great!22:14
darrencYou're welcome to join the Arch Guide meeting as well22:14
darrencthanks!22:14
*** lpetrut has quit IRC22:14
rcaballeromxNo problem.22:14
rcaballeromxDo you have a link to that meeting?22:14
darrencyeah, it's on https://wiki.openstack.org/wiki/Documentation/OpsGuide22:16
darrencwe meet on VIdyo22:16
*** kzaitsev_mb has quit IRC22:16
rcaballeromxOk.22:16
rcaballeromxI will join next time.22:16
darrenccool, thanks rcaballeromx22:17
DevonBoatwright#topic Open Discussion22:17
*** openstack changes topic to "Open Discussion (Meeting topic: ops_guide)"22:17
rcaballeromxYou are welcome, darrenc22:17
DevonBoatwrightOps midcycle- Do we need an ops guide session?22:18
darrencDo you know if anyone on this team is going to the midcycle?22:19
darrencIs shilla going?22:19
* rcaballeromx is not going.22:20
DevonBoatwrightWhere is it?22:20
* darrenc is not going22:20
darrencNY22:20
darrenchttps://wiki.openstack.org/wiki/Operations/Meetups22:21
DevonBoatwrightNo.. I don't think Shilla is going. We're going to OpenStack East22:21
DevonBoatwrightthis is right after, correct?22:21
darrencWe can add it as a suggestion to the etherpad: https://etherpad.openstack.org/p/NYC-ops-meetup22:21
*** mickeys has quit IRC22:22
darrencbut there's not much point if no one on this team is going22:22
DevonBoatwrightI don't think anyone else I know of on the team is going22:22
darrencyeah, 25-26 August22:22
darrencah ok22:23
*** kzaitsev_mb has joined #openstack-meeting-322:23
*** mickeys has joined #openstack-meeting-322:24
darrencWell I'll add to the etherpad anyway22:24
darrencand if there's a session, I can chat to a few ppl who are going22:25
darrencoh, someone has proposed some docs discussion on the etherpad22:26
darrencline 8022:27
darrencanyway, that's it from me22:28
DevonBoatwrightjust noticed that.. was reading the etherpad22:28
*** mickeys has quit IRC22:29
DevonBoatwrightOk.. Well, thanks for joining the meeting darrenc and rcaballeromx!22:29
darrencthanks DevonBoatwright22:29
DevonBoatwrightIf no one else has anything, I will end meeting. We have one minute left anyway22:29
rcaballeromxThanks.22:29
DevonBoatwrightSee you all next meeting!22:29
DevonBoatwright#endmeeting22:29
*** openstack changes topic to " (Meeting topic: ops_guide)"22:29
openstackMeeting ended Thu Aug 11 22:29:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-21.30.html22:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-21.30.txt22:29
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_guide/2016/ops_guide.2016-08-11-21.30.log.html22:29
darrenccya!22:30
*** singlethink has quit IRC22:34
*** galstrom is now known as galstrom_zzz22:35
*** rcaballeromx has left #openstack-meeting-322:35
*** VW has quit IRC22:35
*** DevonBoatwright has quit IRC22:41
*** kzaitsev_mb has quit IRC22:44
*** alexismonville has quit IRC22:47
*** kzaitsev_mb has joined #openstack-meeting-322:47
*** alexismonville has joined #openstack-meeting-323:05
*** tonytan4ever has joined #openstack-meeting-323:10
*** Benj_ has quit IRC23:10
*** Sukhdev has quit IRC23:13
*** tonytan4ever has quit IRC23:14
*** ddieterly has quit IRC23:21
*** kzaitsev_mb has quit IRC23:29
*** testing1234 has joined #openstack-meeting-323:29
*** kzaitsev_mb has joined #openstack-meeting-323:29
*** iyamahat has quit IRC23:43
*** iyamahat has joined #openstack-meeting-323:45
*** ajmiller_ has quit IRC23:47
*** rama_y has quit IRC23:47
*** skath_ has joined #openstack-meeting-323:48
*** beagles_biab is now known as beagles23:49
*** ddieterly has joined #openstack-meeting-323:50
*** zhurong has joined #openstack-meeting-323:52
*** skath has quit IRC23:52
*** skath_ is now known as skath23:52
*** toddjohn has joined #openstack-meeting-323:53
*** sdague has quit IRC23:55
*** toddjohn has quit IRC23:58
*** banix has quit IRC23:58

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