Thursday, 2016-08-04

*** yushiro has joined #openstack-meeting-300:00
*** rossella_s has quit IRC00:00
*** yushiro has left #openstack-meeting-300:00
*** rossella_s has joined #openstack-meeting-300:00
*** bklei has quit IRC00:02
*** bklei has joined #openstack-meeting-300:03
*** stanchan has quit IRC00:06
*** toddjohn has quit IRC00:09
*** bklei has quit IRC00:09
*** sdake has quit IRC00:10
*** baoli has joined #openstack-meeting-300:13
*** mtanino has quit IRC00:14
*** stanchan has joined #openstack-meeting-300:15
*** toddjohn has joined #openstack-meeting-300:15
*** toddjohn has quit IRC00:17
*** toddjohn has joined #openstack-meeting-300:17
*** baoli has quit IRC00:18
*** toddjohn has quit IRC00:23
*** banix has quit IRC00:33
*** tonytan4ever has joined #openstack-meeting-300:33
*** tonytan4ever has quit IRC00:38
*** pvaneck has quit IRC00:50
*** toddjohn has joined #openstack-meeting-300:54
*** toddjohn has quit IRC00:55
*** toddjohn has joined #openstack-meeting-300:55
*** bpokorny_ has joined #openstack-meeting-300:56
*** bpokorny has quit IRC00:59
*** bpokorny_ has quit IRC01:01
*** stanchan has quit IRC01:02
*** zhurong has joined #openstack-meeting-301:06
*** Sukhdev has quit IRC01:12
*** clu_ has quit IRC01:15
*** zhurong has quit IRC01:16
*** zhurong has joined #openstack-meeting-301:17
*** toddjohn has quit IRC01:17
*** s3wong has quit IRC01:20
*** asettle has joined #openstack-meeting-301:24
*** toddjohn has joined #openstack-meeting-301:26
*** asettle has quit IRC01:28
*** stanchan has joined #openstack-meeting-301:41
*** toddjohn has quit IRC01:49
*** dimtruck is now known as zz_dimtruck01:55
*** spzala has joined #openstack-meeting-301:55
*** jschwarz has quit IRC01:56
*** baoli has joined #openstack-meeting-301:56
*** banix has joined #openstack-meeting-301:56
*** dmellado has quit IRC01:57
*** ajo has quit IRC01:57
*** stanchan has quit IRC01:57
*** VW has joined #openstack-meeting-301:57
*** spzala has quit IRC02:00
*** jschwarz has joined #openstack-meeting-302:02
*** dmellado has joined #openstack-meeting-302:02
*** ajo has joined #openstack-meeting-302:03
*** amotoki has joined #openstack-meeting-302:10
*** sarob has joined #openstack-meeting-302:23
*** VW has quit IRC02:24
*** zz_dimtruck is now known as dimtruck02:24
*** markvoelker has joined #openstack-meeting-302:26
*** baoli has quit IRC02:26
*** sarob has quit IRC02:27
*** dkehn_ has quit IRC02:31
*** VW has joined #openstack-meeting-302:31
*** ddieterly has joined #openstack-meeting-302:33
*** ddieterly has quit IRC02:36
*** zhurong has quit IRC02:36
*** zhurong has joined #openstack-meeting-302:38
*** dkehn_ has joined #openstack-meeting-302:43
*** chandanc_ has joined #openstack-meeting-302:49
*** toddjohn has joined #openstack-meeting-302:50
*** sarob has joined #openstack-meeting-302:51
*** toddjohn has quit IRC02:54
*** sarob has quit IRC02:55
*** hichihara has joined #openstack-meeting-302:56
*** yamahata has quit IRC03:03
*** iyamahat has quit IRC03:04
*** sdake has joined #openstack-meeting-303:04
*** banix has quit IRC03:14
*** toddjohn has joined #openstack-meeting-303:21
*** mrmartin has joined #openstack-meeting-303:22
*** coolsvap has joined #openstack-meeting-303:22
*** sdake has quit IRC03:23
*** toddjohn has quit IRC03:26
*** stanchan has joined #openstack-meeting-303:30
*** persia has quit IRC03:30
*** persia has joined #openstack-meeting-303:33
*** jrist has joined #openstack-meeting-303:34
*** stanchan has quit IRC03:45
*** markvoelker has quit IRC03:46
*** VW has quit IRC03:47
*** sdake has joined #openstack-meeting-303:50
*** amotoki has quit IRC03:54
*** VW has joined #openstack-meeting-303:54
*** amotoki has joined #openstack-meeting-303:55
*** rossella_s has quit IRC04:00
*** rossella_s has joined #openstack-meeting-304:00
*** sarob has joined #openstack-meeting-304:01
*** Sukhdev has joined #openstack-meeting-304:03
*** Sukhdev has quit IRC04:04
*** Sukhdev has joined #openstack-meeting-304:04
*** sarob has quit IRC04:06
*** yushiro has joined #openstack-meeting-304:13
*** julim has quit IRC04:16
*** yushiro has left #openstack-meeting-304:17
*** markvoelker has joined #openstack-meeting-304:22
*** chandanc_ has quit IRC04:26
*** markvoelker has quit IRC04:26
*** sdake has quit IRC04:37
*** stanchan has joined #openstack-meeting-304:58
*** flwang2 has joined #openstack-meeting-304:59
*** stanchan has quit IRC04:59
*** stanchan has joined #openstack-meeting-305:00
*** flwang1 has quit IRC05:01
*** VW has quit IRC05:01
*** flwang2 has quit IRC05:03
*** Niham has joined #openstack-meeting-305:09
*** Niham has quit IRC05:09
*** markvoelker has joined #openstack-meeting-305:16
*** markvoelker has quit IRC05:22
*** toddjohn has joined #openstack-meeting-305:23
*** toddjohn has quit IRC05:27
*** irenab has joined #openstack-meeting-305:34
*** Poornima has joined #openstack-meeting-305:36
*** lpetrut has joined #openstack-meeting-305:46
*** mickeys has joined #openstack-meeting-305:49
*** mickeys has quit IRC05:53
*** sarob has joined #openstack-meeting-306:02
*** pt_15 has quit IRC06:06
*** sarob has quit IRC06:07
*** asettle has joined #openstack-meeting-306:09
*** jtomasek has quit IRC06:09
*** pcaruana has joined #openstack-meeting-306:10
*** asettle has quit IRC06:14
*** stanchan has quit IRC06:21
*** toddjohn has joined #openstack-meeting-306:24
*** yushiro has joined #openstack-meeting-306:28
*** stanchan has joined #openstack-meeting-306:28
*** toddjohn has quit IRC06:28
*** yushiro has left #openstack-meeting-306:29
*** belmoreira has joined #openstack-meeting-306:30
*** pgadiya has joined #openstack-meeting-306:32
*** Sukhdev has quit IRC06:38
*** stanchan has quit IRC06:38
*** anilvenkata has joined #openstack-meeting-306:39
*** yamamoto_ has quit IRC06:41
*** jlanoux has joined #openstack-meeting-306:45
*** jed56 has joined #openstack-meeting-306:47
*** armax has quit IRC06:51
*** stanchan has joined #openstack-meeting-306:52
*** spzala has joined #openstack-meeting-306:56
*** lpetrut has quit IRC06:59
*** iyamahat has joined #openstack-meeting-306:59
*** spzala has quit IRC07:00
*** ihrachys has joined #openstack-meeting-307:02
*** stanchan has quit IRC07:02
*** stanchan has joined #openstack-meeting-307:09
*** abalutoiu has joined #openstack-meeting-307:11
*** lpetrut has joined #openstack-meeting-307:11
*** Poornima has quit IRC07:12
*** ccamacho has quit IRC07:16
*** itxaka has joined #openstack-meeting-307:18
*** yamahata has joined #openstack-meeting-307:18
*** ccamacho has joined #openstack-meeting-307:18
*** lpetrut has quit IRC07:31
*** dimtruck is now known as zz_dimtruck07:32
*** iyamahat has quit IRC07:35
*** lpetrut has joined #openstack-meeting-307:40
*** ihrachys has quit IRC07:40
*** vishwanathj has quit IRC07:44
*** RuiChen has joined #openstack-meeting-307:46
*** stanchan has quit IRC07:48
*** ihrachys has joined #openstack-meeting-307:48
*** mickeys has joined #openstack-meeting-307:50
*** mickeys has quit IRC07:55
*** mickeys has joined #openstack-meeting-307:56
*** lpetrut has quit IRC07:56
*** ihrachys has quit IRC07:57
*** markvoelker has joined #openstack-meeting-307:58
*** ihrachys has joined #openstack-meeting-307:59
*** rossella_s has quit IRC08:00
*** mickeys has quit IRC08:00
*** rossella_s has joined #openstack-meeting-308:00
*** markvoelker has quit IRC08:03
*** stanchan has joined #openstack-meeting-308:04
*** ihrachys has quit IRC08:06
*** ihrachys has joined #openstack-meeting-308:10
*** hichihara has quit IRC08:14
*** stanchan has quit IRC08:20
*** yamahata has quit IRC08:22
*** toddjohn has joined #openstack-meeting-308:25
*** toddjohn has quit IRC08:30
*** flwang1 has joined #openstack-meeting-308:40
*** asettle has joined #openstack-meeting-308:40
*** zz_dimtruck is now known as dimtruck08:52
*** markvoelker has joined #openstack-meeting-308:53
*** jtomasek has joined #openstack-meeting-308:53
*** iyamahat has joined #openstack-meeting-308:54
*** markvoelker has quit IRC08:57
*** iyamahat has quit IRC08:59
*** yamamoto_ has joined #openstack-meeting-308:59
*** dimtruck is now known as zz_dimtruck09:01
*** yamamoto_ has quit IRC09:02
*** yamamoto has joined #openstack-meeting-309:03
*** yamamoto has quit IRC09:08
*** numans has joined #openstack-meeting-309:11
*** lpetrut has joined #openstack-meeting-309:26
*** stendulker has joined #openstack-meeting-309:28
*** markvoelker has joined #openstack-meeting-309:47
*** markvoelker has quit IRC09:52
*** yamamoto has joined #openstack-meeting-309:53
*** sambetts|afk is now known as sambetts09:55
*** sarob has joined #openstack-meeting-310:03
*** zhurong has quit IRC10:04
*** sarob has quit IRC10:08
*** ihrachys has quit IRC10:11
*** kzaitsev_mb has joined #openstack-meeting-310:13
*** itoader has joined #openstack-meeting-310:17
*** toddjohn has joined #openstack-meeting-310:27
*** itoader has quit IRC10:27
*** yamamoto has quit IRC10:29
*** yamamoto has joined #openstack-meeting-310:30
*** amotoki has quit IRC10:31
*** toddjohn has quit IRC10:31
*** yamamoto has quit IRC10:32
*** ihrachys has joined #openstack-meeting-310:33
*** kzaitsev_mb has quit IRC10:37
*** qwebirc49115 has joined #openstack-meeting-310:38
*** qwebirc49115 has left #openstack-meeting-310:38
*** markvoelker has joined #openstack-meeting-310:41
*** markvoelker has quit IRC10:46
*** kzaitsev_mb has joined #openstack-meeting-310:53
*** anilvenkata is now known as anilvenkata_afk10:53
*** spzala has joined #openstack-meeting-310:57
*** tellesnobrega has quit IRC10:58
*** spzala has quit IRC11:01
*** stendulker has quit IRC11:02
*** ihrachys has quit IRC11:02
*** ihrachys has joined #openstack-meeting-311:06
*** jlanoux has quit IRC11:09
*** amotoki has joined #openstack-meeting-311:17
*** sdague has joined #openstack-meeting-311:21
*** yamamoto has joined #openstack-meeting-311:23
*** itoader has joined #openstack-meeting-311:24
*** alexismonville has joined #openstack-meeting-311:25
*** itoader has quit IRC11:31
*** kzaitsev_mb has quit IRC11:34
*** markvoelker has joined #openstack-meeting-311:35
*** jlanoux has joined #openstack-meeting-311:35
*** tellesnobrega has joined #openstack-meeting-311:37
*** markvoelker has quit IRC11:39
*** amotoki has quit IRC11:50
*** anilvenkata_afk is now known as anilvenkata11:52
*** asettle has quit IRC11:57
*** asettle has joined #openstack-meeting-311:57
*** asettle has quit IRC12:02
*** markvoelker has joined #openstack-meeting-312:05
*** rtheis has joined #openstack-meeting-312:09
*** zhurong has joined #openstack-meeting-312:12
*** baoli has joined #openstack-meeting-312:20
*** kzaitsev_mb has joined #openstack-meeting-312:25
*** baoli_ has joined #openstack-meeting-312:25
*** asettle has joined #openstack-meeting-312:26
*** toddjohn has joined #openstack-meeting-312:28
*** baoli has quit IRC12:29
*** toddjohn has quit IRC12:33
*** zhipeng has joined #openstack-meeting-312:35
*** toddjohn has joined #openstack-meeting-312:39
*** amotoki has joined #openstack-meeting-312:43
*** baojg_ has joined #openstack-meeting-312:44
*** zz_dimtruck is now known as dimtruck12:53
*** toddjohn has quit IRC12:55
*** tellesnobrega has quit IRC12:56
*** tangchen has quit IRC12:59
*** lblanchard has joined #openstack-meeting-313:00
*** dimtruck is now known as zz_dimtruck13:03
*** bklei has joined #openstack-meeting-313:04
*** tellesnobrega has joined #openstack-meeting-313:04
*** numans has quit IRC13:05
*** spzala has joined #openstack-meeting-313:09
*** spzala has quit IRC13:09
*** toddjohn has joined #openstack-meeting-313:09
*** spzala has joined #openstack-meeting-313:09
*** iyamahat has joined #openstack-meeting-313:10
*** sdake has joined #openstack-meeting-313:11
*** bklei has quit IRC13:11
*** markvoelker has quit IRC13:13
*** toddjohn has quit IRC13:13
*** bklei has joined #openstack-meeting-313:16
*** baojg_ has quit IRC13:17
*** Liuqing has joined #openstack-meeting-313:17
*** ihrachys has quit IRC13:18
*** VW has joined #openstack-meeting-313:19
*** cleong has joined #openstack-meeting-313:19
*** sdake has quit IRC13:24
*** rbak has joined #openstack-meeting-313:26
*** galstrom_zzz is now known as galstrom13:28
*** matrohon has joined #openstack-meeting-313:30
*** julim has joined #openstack-meeting-313:31
*** rbak has quit IRC13:36
*** numans has joined #openstack-meeting-313:36
*** toddjohn has joined #openstack-meeting-313:38
*** tovchinnikova has joined #openstack-meeting-313:39
*** yamamoto has quit IRC13:46
*** matrohon has quit IRC13:48
*** yamamoto has joined #openstack-meeting-313:49
*** ddieterly has joined #openstack-meeting-313:50
*** pgadiya has quit IRC13:51
*** markvoelker has joined #openstack-meeting-313:51
*** rbak has joined #openstack-meeting-313:53
*** sdake has joined #openstack-meeting-313:54
*** yamamoto has quit IRC13:56
*** baoli_ has quit IRC13:59
*** dasanind has joined #openstack-meeting-314:00
*** ddieterly has quit IRC14:01
*** ddieterly has joined #openstack-meeting-314:01
*** belmoreira has quit IRC14:02
*** uxdanielle has joined #openstack-meeting-314:04
*** matrohon has joined #openstack-meeting-314:05
*** matrohon has quit IRC14:05
*** coolsvap has quit IRC14:11
*** jproulx has joined #openstack-meeting-314:12
*** rockyg has joined #openstack-meeting-314:12
*** marst has quit IRC14:13
*** thatsdone has joined #openstack-meeting-314:14
*** VW has quit IRC14:15
*** xavierr is now known as xavierr|mtg14:17
*** matrohon has joined #openstack-meeting-314:22
*** amotoki has quit IRC14:22
*** alexismonville has quit IRC14:23
*** marst has joined #openstack-meeting-314:24
*** VW has joined #openstack-meeting-314:28
*** Benj_ has joined #openstack-meeting-314:29
*** mtanino has joined #openstack-meeting-314:31
*** zz_dimtruck is now known as dimtruck14:31
*** vishwanathj has joined #openstack-meeting-314:32
*** matrohon has quit IRC14:32
*** tangchen has joined #openstack-meeting-314:32
*** Benj_ has quit IRC14:34
*** asettle has quit IRC14:38
*** asettle has joined #openstack-meeting-314:39
*** banix has joined #openstack-meeting-314:40
*** tellesnobrega has quit IRC14:41
*** raj_singh_ has joined #openstack-meeting-314:45
*** stanchan has joined #openstack-meeting-314:47
*** Liuqing has quit IRC14:47
*** stanchan has quit IRC14:48
*** Liuqing has joined #openstack-meeting-314:48
*** matrohon has joined #openstack-meeting-314:49
*** cbouch has joined #openstack-meeting-314:50
*** tidwellr has joined #openstack-meeting-314:51
*** uxdanielle has quit IRC14:53
*** beagles is now known as beagles_brb14:56
*** thatsdone has quit IRC14:57
*** yamamoto has joined #openstack-meeting-314:57
*** john-davidge has joined #openstack-meeting-314:58
*** mickeys has joined #openstack-meeting-314:59
*** mickeys has quit IRC14:59
*** mickeys has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-315:00
*** banix has quit IRC15:00
tidwellr#startmeeting neutron_l315:00
openstackMeeting started Thu Aug  4 15:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is tidwellr. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
tidwellr#chair mlavalle carl_baldwin15:00
openstackCurrent chairs: carl_baldwin mlavalle tidwellr15:00
tidwellrcalr_baldwin is here, we do announcements! j/k15:01
tidwellr#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** tangchen has quit IRC15:03
*** banix has joined #openstack-meeting-315:03
tidwellrmid-cycle is coming 17th-19th15:03
*** rockyg has quit IRC15:04
tidwellranybody have a sense for what some of the hot topics might be?15:04
*** Liuqing has quit IRC15:05
carl_baldwinThere have been some ML posts. There are lots of topics.15:05
*** rockyg has joined #openstack-meeting-315:05
carl_baldwinEtherpad has a lot of info on it.15:05
*** yamamoto has quit IRC15:05
*** Liuqing has joined #openstack-meeting-315:05
tidwellrI asked because I didn't see much other than travel info in the etherpad15:06
haleybtidwellr: ^^15:06
tidwellrah, that's the one I was looking for15:06
*** numans has quit IRC15:06
*** steve_ruan has joined #openstack-meeting-315:06
carl_baldwinYou're right. I might have been thinking of another page.15:06
john-davidgeah, haleyb beat me to it15:06
haleyband seeing the inside of pubs is a work item for some15:06
carl_baldwinYep, that page.15:06
carl_baldwinThe two should be cross-linked.15:07
mlavallehaleyb: you not going?15:07
*** janzian has joined #openstack-meeting-315:08
haleybmlavalle: no, on vacation with family that week, although i'll try to be online for some15:08
*** anilvenkata has quit IRC15:08
mlavalleEnjoy the vacation though!15:09
haleybyes, i tried to have the vacation moved to IE15:09
tidwellrany more announcements?15:10
tidwellralright, moving on15:11
tidwellr#topic Bugs15:11
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:11
tidwellrlooking at the agenda, it looks like we should go over potential backports15:12
*** lcastell has quit IRC15:12
*** luzC has quit IRC15:12
HenryGI would like to highlight one bug15:12
HenryGBug 156287815:12
openstackbug 1562878 in neutron "L3 HA: Unable to complete operation on subnet" [High,Confirmed] - Assigned to Ann Taraday (akamyshnikova)15:12
* carl_baldwin looks...15:13
HenryGIt has been occuring regularly in the check/gate since July 24.15:14
carl_baldwinHenryG: Should it be critical?15:15
carl_baldwinMost gate failures are treated as critical. Especially if they're occurring regularly.15:15
*** Benj_ has joined #openstack-meeting-315:15
HenryGcarl_baldwin: the recurrence is low enough that a recheck usually passes15:15
HenryGBut I am leaning towards critical15:16
carl_baldwinHenryG: Do you have a logstash query URL you've been using?15:16
HenryGI put it in comment #515:17
*** VW has quit IRC15:17
HenryGRemove the build_queue:"gate" option to see all the occurrences15:17
haleybjschwarz: is ^^ on your radar?  I know you've been looking at HA issues15:17
*** VW has joined #openstack-meeting-315:18
carl_baldwinHenryG: Ah, I see it.15:19
*** baoli has joined #openstack-meeting-315:19
carl_baldwinHenryG: That looks like a lot of occurrences. But, many are in the same run.15:21
jschwarzhaleyb, yes, it's on my radar15:21
jschwarzhaleyb, it's in my queue (which is a bit full atm), but Ann should be back next week and I hope to cooperate with her on this15:21
carl_baldwinI'm scratching my head over how retrying DBConnectionError will cause it.15:21
*** lcastell has joined #openstack-meeting-315:21
HenryGcarl_baldwin: I suck at logstash queries15:21
*** luzC has joined #openstack-meeting-315:22
carl_baldwinHenryG: Me too.15:22
jschwarzalso, I got this reproduced locally on a simple 2-node devstack deployment15:22
jschwarzso that should give us a better understanding on why it's happening15:23
HenryGcarl_baldwin: I doubt the BDConnectionError patch causes it, I just located the last merge that went in before the bug started showing up.15:23
*** baoli_ has joined #openstack-meeting-315:23
*** tangchen_ has joined #openstack-meeting-315:23
*** baoli has quit IRC15:23
carl_baldwinHenryG: Do you think maybe you just hit the limit of what logstash keeps around?15:24
*** matrohon has quit IRC15:24
*** armax has joined #openstack-meeting-315:24
carl_baldwinI think it only keeps about 7 days of data.15:24
HenryGcarl_baldwin: It allows me to select 30 days from the drop-down.15:25
HenryGAnyway, I think the jschwarz option is the better way to track this down.15:26
* jschwarz lols @ "the jschwarz option"15:26
carl_baldwinjschwarz: Is it reliably reproducible?15:26
jschwarzcarl_baldwin, I remember running a bunch of rally tests (5ish?) and it happened a few times (2-3)15:27
carl_baldwinHenryG: I think all my queries get clamped at around 7 days even when selecting the 30 day option.15:27
carl_baldwinjschwarz: Sounds good.15:28
* mlavalle has never been able to get a 30 days query15:28
carl_baldwinShould we keep it assigned to Ann?15:28
HenryGcarl_baldwin: then I have been on many wild goose chases :(15:28
carl_baldwinHenryG: I've been on those.15:28
jschwarzcarl_baldwin, I think so - she'll come back next week and I'll discuss this bug with her and see if I should take it or not15:28
*** armax has quit IRC15:29
*** baoli_ has quit IRC15:29
carl_baldwinLet's move on.15:29
*** armax has joined #openstack-meeting-315:29
*** baoli has joined #openstack-meeting-315:29
*** iyamahat has quit IRC15:29
openstackLaunchpad bug 1604370 in neutron "functional: test_legacy_router_ns_rebuild is unstable" [High,Fix released] - Assigned to Terry Wilson (otherwiseguy)15:30
*** notmars has joined #openstack-meeting-315:30
*** zhurong has quit IRC15:30
tidwellrlooks like we can pull this off the agenda15:30
*** raj_singh_ has quit IRC15:30
mlavalleit seems fix is realeased15:31
*** baoli_ has joined #openstack-meeting-315:31
tidwellrmoving on15:31
openstackLaunchpad bug 1596075 in neutron "Neutron confused about overlapping subnet creation" [High,In progress] - Assigned to Kevin Benton (kevinbenton)15:31
mlavalleI spent some time this morning tracking this one15:31
mlavalleIt is a complicated affair, involving the quota engine, db retries and Galera15:32
mlavalle2 patchsets have been merged in relationship to it15:32
mlavalleand kevinbenton is working on another 2 fixes:15:32
mlavalleI'll keep tracking it15:34
*** baoli has quit IRC15:34
tidwellrmlvalle: thanks for staying on top of this15:34
openstackLaunchpad bug 1599329 in neutron "Potential regression on handing over DHCP addresses to VMs" [High,In progress]15:35
*** amotoki has joined #openstack-meeting-315:35
carl_baldwinIn watch mode.15:36
tidwellryeah, looks like we're just waiting to see if this strikes again15:36
tidwellrcan we take off the agenda?15:36
openstackLaunchpad bug 1605277 in neutron "[IPAM] 'Internal' ipam driver does not allow to delete all pools on subnet update" [High,Fix released] - Assigned to Carl Baldwin (carl-baldwin)15:36
*** ddieterly is now known as ddieterly[away]15:37
*** ddieterly[away] is now known as ddieterly15:37
tidwellrcool, done15:37
*** ddieterly is now known as ddieterly[away]15:37
openstackLaunchpad bug 1603162 in neutron "Pluggable IPAM rollback fails with reference driver" [High,In progress] - Assigned to Carl Baldwin (carl-baldwin)15:37
tidwellrcarl_baldwin: any luck with this one?15:38
carl_baldwinI've had some discussion on the ML with kevinbenton . We have some ideas.15:38
carl_baldwinI've got to get on this one quickly.15:38
carl_baldwinI'll be working on it today.15:39
tidwellrthis is a blocker for the cutover to pluggable IPAM, right?15:39
openstackLaunchpad bug 1608406 in neutron "BGP: DVR fip host routes query including legacy/HA fip routes" [Undecided,In progress] - Assigned to LIU Yulong (dragon889)15:40
tidwellrjust wanted to call this out as it has backport potential15:40
*** ddieterly[away] is now known as ddieterly15:40
*** matrohon has joined #openstack-meeting-315:40
tidwellrthis is my worst BGP nightmare come true15:40
tidwellrwe're sending the wrong next-hop for a FIP15:42
haleybtidwellr: just for mitaka, right?  just updating bug tags15:42
tidwellrboth newton and mitaka15:42
*** uxdanielle has joined #openstack-meeting-315:43
haleybfor backport i meant :)15:43
tidwellroh, right15:43
tidwellryes, mitaka for backport :)15:43
tidwellrugh, it's been a morning......15:44
tidwellrI was able to reproduce locally, attaching a legacy router and a distributed router to the same external network results in a FIP on the legacy router also being announced as accessible via one of the FIP gateways15:44
tidwellrI'm helping chase this down15:44
* mlavalle appreciates that it is early in tidwellr time zone and he still shows up15:45
*** beagles_brb is now known as beagles15:45
*** uxdanielle has quit IRC15:46
tidwellrany more bugs to discuss?15:46
jschwarzI have one but that can be left for the Open Discussion if there's time15:46
mlavalleWe have, filed by a certain carl_baldwin15:46
openstackLaunchpad bug 1609540 in neutron "Deleting csnat port fails due to no fixed ips" [Critical,In progress] - Assigned to Kevin Benton (kevinbenton)15:46
carl_baldwinIt is in watch mode.15:46
carl_baldwinI'm going to keep an eye on it and hopefully reduce the severity soon.15:47
*** stanchan has joined #openstack-meeting-315:47
*** bpokorny has joined #openstack-meeting-315:47
*** marst has quit IRC15:48
*** revon has joined #openstack-meeting-315:48
mlavalleI'll put in the etherpad anyway15:48
*** iyamahat has joined #openstack-meeting-315:48
tidwellralright, we don't have much time to dive in to routed networks, FWaaS, RFE's, etc.15:48
mfranc213hello, i'm filling in for njohnston again this week.  just 3 things:15:49
mfranc213the handle_router method was split into add_router and update_router in the L3 Agent Extension Manager patch (
*** banix has quit IRC15:49
tidwellrI'm thinking we move to open discussion15:49
mfranc213so sorry15:49
*** abalutoiu has quit IRC15:49
tidwellrmfranc213: no worries, go for it15:49
mfranc213next patchset for the FWaaS L3 agent extension was issued yesterday (Refactor FWaaS' L3 agent extension)15:50
mfranc213ork on the FWaaS plugin  is proceeding and i believe we will get a patchset pushed in the next couple of days.15:50
tidwellr#topic Open Discussion15:50
mfranc213that's it!15:50
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:50
steve_ruan need 1 more "+2"15:50
tidwellrmfranc213: thanks for the update15:50
*** yamahata has joined #openstack-meeting-315:50
steve_ruananyone can help?15:50
*** tangchen_ has quit IRC15:51
carl_baldwinhaleyb: could you take a look ^15:51
carl_baldwinmfranc213: I'll take a look at that change.15:51
john-davidgeA couple of updates on service subnets. Brian noticed a possible problem with the deletion logic for and pushed a fix yesterday. It should be good to go. And a WIP for the follow-up patch is here - It's almost ready for review.15:51
haleybi'm on it15:51
tidwellrsteve_ruan: thanks for making some noise about that one15:51
mfranc213thank you carl_baldwin15:51
jschwarzI filed which deals with a weird state HA routers can get into while creating/updating it.. the solution I have in mind involves refactoring update_router_db for the l3_hamode_db.py15:52
openstackLaunchpad bug 1609738 in neutron "l3-ha: a router can be stuck in the ALLOCATING state" [Undecided,New] - Assigned to John Schwarz (jschwarz)15:52
haleybjohn-davidge: and the OSC patch just got a +215:52
jschwarzsuch that modifying admin_state_up will unschedule/schedule the router (as opposed for the current ha attribute change which does this one)15:53
john-davidgehaleyb: woop \o/15:53
jschwarzI need more opinions though on this matter15:53
*** Benj_ has quit IRC15:53
mlavallejohn-davidge: I took a look at
john-davidgemlavalle: Yes, thanks for the review. I've already incorporated it into the next patch. Should help with performance at scale15:54
*** marst has joined #openstack-meeting-315:54
mlavallejschwarz: is there a patchset up for review or should we comment in the bug?15:56
jschwarzmlavalle, comments on the bug will be much appreciated15:57
jschwarzit's quite a refactor and I started working on it today and it broke a few things :<15:57
mlavalleyeap, that's what big refactors do15:58
*** gouthamr-afk has joined #openstack-meeting-315:58
mlavalleit seems bugs left us exhausted today :-)15:59
*** rossella_s has quit IRC16:00
tidwellrmlavalle: indeed16:00
tidwellrthanks everyone!16:00
*** openstack changes topic to " (Meeting topic: ops_guide)"16:00
openstackMeeting ended Thu Aug  4 16:00:31 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
*** rossella_s has joined #openstack-meeting-316:00
etoews#startmeeting api wg16:00
openstackMeeting started Thu Aug  4 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at
*** matrohon has quit IRC16: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
etoews#chair cdent elmiko etoews16:00
openstackWarning: Nick not in channel: cdent16:00
openstackWarning: Nick not in channel: elmiko16:00
openstackCurrent chairs: cdent elmiko etoews16:00
*** janzian has left #openstack-meeting-316:01
mlavallethey left you alone etoews ;-)16:01
jschwarzthanks guys16:01
*** banix has joined #openstack-meeting-316:01
etoewsmlavalle: apparently so :)16:01
*** toddjohn has quit IRC16:01
mlavalleif you feel lonely, ping me ;-)16:01
dramakrietoews: hi16:03
*** tangchen_ has joined #openstack-meeting-316:04
etoewsdramakri: hello!16:04
*** Liuqing has quit IRC16:04
dramakrietoews: will we be discussing - APIs for exposing resource capabilities?16:05
etoewsdramakri: unfortunately we seem to be a bit understaffed at the moment. the other 2 usual members of the api working group weren't able to make it today.16:06
*** elmiko has joined #openstack-meeting-316:06
etoewswould you still like to discuss it?16:06
etoewshello elmiko!16:07
*** tidwellr has left #openstack-meeting-316:07
elmikohey, sorry bout that16:07
elmikolost track of time16:07
etoewsnp. well let's dive in and see if we can make any progress.16:07
etoews#topic APIs for exposing resource capabilities16:07
*** openstack changes topic to "APIs for exposing resource capabilities (Meeting topic: api wg)"16:07
*** jlanoux has quit IRC16:07
etoewsdramakri: care to provide some context? what are you hoping to get out of this discussion?16:08
*** gouthamr_afk has joined #openstack-meeting-316:08
dramakrietoews: sure16:08
*** baoli_ has quit IRC16:08
*** bpokorny has quit IRC16:09
dramakriI propose defining a capability API for every resource in a REST API where it makes sense and is needed.16:09
dramakrithis was started for Cinder.16:09
*** ddieterly is now known as ddieterly[away]16:09
dramakriIn the context of Cinder, we would have a capability API at the root resource level (GET /v3.x/{tenant_id}/capabilities) that would return, e.g., [“volume-backup", “other-capability”]16:10
dramakriCinder cores suggested that this might be a generic enough problem with other OpenStack services as well16:10
dramakriso I am wondering if there are any other projects currently working on capabilities - lets say nova16:10
etoewsheh. that was my question too.16:11
elmikocould you define "capabilities" a little more?16:11
*** gouthamr-afk has quit IRC16:12
dramakricapabilities are the features supported by a cinder service or a lower level resource like volume_types16:13
elmikoare these o/s level capabilities then?16:13
etoewsas a wild swing at seeing what other services support things called "capability or capabilities" i did this search
dramakri"volume-backup" would be an example for service-level or root resource.16:14
*** baoli has joined #openstack-meeting-316:14
etoewsit's certainly a popular term. ;)16:14
dramakrietoews: looking at your link16:14
elmikoheh, that's why i'm curious. is this just some sort of open-ended metadata or is there something behind the term capabilities?16:14
etoewshard to say if everything in those results maps to the concept you're describing though16:15
elmikolike, i think kernel capabilities when i hear that as some sort of o/s level thing16:15
*** ddieterly[away] is now known as ddieterly16:15
*** seldenr has joined #openstack-meeting-316:15
dramakri"capability" is a functionality that may or may not be supported. So, it becomes important to have a way to know whether it is suppoted16:16
dramakriFor example: volume backup. Some Cinder services support, some dont.16:16
elmikogot it16:16
dramakriIf Horizon could knew when it is supported, it can enable the "Create Volume Backup" button16:16
*** bpokorny has joined #openstack-meeting-316:16
*** matrohon has joined #openstack-meeting-316:17
dramakriIn Cinder, existing APIs to epose capabilities don't follow any pattern16:17
dramakriOne sticks it inside the "extra specs" field of a propery bag16:18
dramakriAnother defines an API, and so on16:18
dramakriThe spec seeks to regularize it for Cinder and hopefully for other OpenStack projects too16:18
dramakriThe key concept is "one capability API per resource, where it makes sense"16:19
elmikohmm, sounds a lot like metadata to me. i'm having a hard time visualizing how we would standardize the capabilities themselves16:19
etoewseven better would be...if a capability isn't supported, it offers a description of *why* it isn't support that is digestible by an end user.16:19
elmikoetoews++ great suggestion16:20
dramakriThe list of capabilities is open ended. We do not know the list of capabilities that are not supported16:21
etoewselmiko: it sounds to me like what they basically have now is unstructured metadata (in extra specs) and are looking to structure that into something called capabilities16:21
etoewsdramakri: is that ^ a fair take on it?16:21
dramakriextra specs is just one way Cinder uses. But, yes, your statements is true in general16:21
elmikoyeah, i was just thinking from the pattern it sounds like something that could use the mechanics of the metadata guideline, perhaps...16:22
elmikoalbeit with some sort of capabilities specific endpoint, or similar, for each resource16:22
etoewsor metadata reserved for use by capabilities16:23
dramakrielmiko: do you have a link for the "metadata guideline"?16:23
*** matrohon has quit IRC16:23
elmikoi'm guessing you would ignore the updating and creating parts (which would be handled by the server)16:24
dramakriOn a quick glance, it seems similar16:27
*** bklei_ has joined #openstack-meeting-316:28
*** steve_ruan has quit IRC16:28
*** cbouch has quit IRC16:28
*** zhipeng_ has joined #openstack-meeting-316:30
dramakriHas the metadata guideline been adopted by all OpenStack projects?16:30
elmikowell, it doesn't quite work like that. but i've seen more than one project adopt it16:30
*** zhipeng has quit IRC16:31
etoewsit's the way forward for any project doing a metadata api16:31
etoews(or changes to a metadata api)16:31
*** ddieterly is now known as ddieterly[away]16:32
*** bklei has quit IRC16:32
dramakriDoes it mean that we should use the term "capabilities" for Cinder?16:32
*** kro_focused is now known as krotscheck16:32
dramakri*we should NOT use the term ...16:33
*** bpokorny has quit IRC16:33
elmikoimo, it's fine if we want to describe a general use for the metadata stuff as capabilities. i feel this is more a process thing within openstack though16:34
*** dasanind has quit IRC16:34
*** vgridnev has joined #openstack-meeting-316:34
dramakriI am not clear if implementing the capabilities API (as my spec calls for) would adhere or violate the metadata guidelines16:36
elmikohonestly, it feels like a cross-project spec (assuming those still exist)16:36
dramakriIn particular, it is ok to use "resource-capability" API path suffix instead of "metadata"?16:36
dramakriIs it ok to not support create, delete16:36
elmikoit sounded like the capabilities API is a sub-set of the metadata guide16:36
dramakriIs it ok to use the simply list representations of the capabilities16:37
elmikoas a convention, i would think it's fine to propose that projects adopt a "resource-capability" endpoint.16:37
elmikoat this point though, maybe it would make sense to propose this as a guideline and see what the community thinks?16:38
dramakriHow and where would we propose such a thing to the community16:38
etoewsif so, it should follow the interaction conventions already in the metadata guideline (minus create, update, and delete)16:39
elmikoif you write a guideline and submit it as a review to the api-wg, we will debate it and announce to the community to get a broader audience16:39
*** vgridnev has quit IRC16:39
*** SumitNaiksatam has joined #openstack-meeting-316:39
etoewsdramakri: we have this too
*** matrohon has joined #openstack-meeting-316:40
dramakriThanks for the pointer for writing guidelines16:40
*** notmyname has joined #openstack-meeting-316:40
*** bpokorny has joined #openstack-meeting-316:41
dramakriIn the meanwhile can we proceed with the implementation for resource-capabilities API in Cinder (
etoewsit would most likely result in the new file
*** toddjohn has joined #openstack-meeting-316:42
*** pt_15 has joined #openstack-meeting-316:42
etoewsdramakri: we also recommend doing some research into what the other projects are already doing with respect to capabilities. if you do so, the place for that research is here
*** tellesnobrega has joined #openstack-meeting-316:43
elmikojust from looking at the spec for that work, i don't see anything that stands out as counter to the api-wg guidelines16:44
*** VW_ has joined #openstack-meeting-316:45
elmikoi'm sure there are some rest purist arguments to be made about adding the "/capabilities" to any resource endpoint, but i don't see a huge issue with that16:45
dramakrigood to know16:45
etoewswe're rest pragmatists around here ;)16:45
*** VW has quit IRC16:46
dramakriIt is "resource-capability" BTW. I so wanted to use "capability" but i would clash with some one-off API in Cinder16:46
elmikoah, sorry, my inaccuracy16:46
*** vgridnev has joined #openstack-meeting-316:46
dramakriFor publishing the guideline for review, can it just summarize the spec and then point to the spec for details or do I need to paraphrase the full thing?16:46
elmikoyou should spell out how the guideline should be implenented by other projects16:47
elmikoso, it needs to be a little more detailed. like the metadata guideline, for example.16:47
*** Swami has joined #openstack-meeting-316:48
dramakriI see16:48
etoewsya. do something close to the metadata guideline.16:48
etoewsand it would be worthwhile to call out why you're _not_ using the metadata guideline as is16:48
elmikoooh, good point ++16:49
*** john-davidge has left #openstack-meeting-316:49
dramakriOk so I will (1) do some research on how other projects define capabilities, (2) go ahead with my spec implementation if I don't find a pattern adopted by all other proejcts, (3) publish the guideline for defining resource capabilities at a later time16:49
etoewsdramakri: sgtm!16:50
dramakrithanks etoews and elmiko!16:50
*** Sukhdev has joined #openstack-meeting-316:50
etoewsthanks for the good discussion dramakri16:50
*** mohankumar__ has joined #openstack-meeting-316:51
elmikodramakri: agreed with etoews, sounds good16:51
*** bklei_ has quit IRC16:53
*** alexismonville has joined #openstack-meeting-316:53
*** david-lyle has quit IRC16:53
etoewselmiko: not much new besides this discussion. should we do a newsletter this week?16:53
*** david-lyle has joined #openstack-meeting-316:53
etoews(i'm okay skipping it)16:53
elmikohmm, i'm usually in favor of writing one16:53
*** bklei has joined #openstack-meeting-316:54
etoewsokay. let's do it.16:54
elmikobut, i don't have a strong opinion on it. did we add anything new in the last week?16:54
*** olaph has joined #openstack-meeting-316:54
*** ddieterly[away] is now known as ddieterly16:54
*** jtomasek has quit IRC16:55
*** asettle has quit IRC16:55
etoewsnot that i can see16:55
elmikook, i wonder if we maybe mention the capability discussion. seems like some interesting food for thought?16:56
elmikook, looking at the etherpad now16:57
*** bklei_ has joined #openstack-meeting-316:58
etoewsoops. gotta end the meeting.17:00
*** openstack changes topic to " (Meeting topic: ops_guide)"17:00
openstackMeeting ended Thu Aug  4 17:00:03 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** VW_ has quit IRC17:00
elmikoetoews: k, i'll finish this up17:00
*** belmoreira has joined #openstack-meeting-317:00
*** singlethink has joined #openstack-meeting-317:00
etoewselmiko: many thanks.17:00
docaedocourtesy ping kfox1111 sslypushenko mfedosin olaph kzaitsev_mb igormarnat_17:00
*** VW has joined #openstack-meeting-317:00
*** piet_ has joined #openstack-meeting-317:01
*** mfedosin has joined #openstack-meeting-317:01
docaedo#startmeeting app-catalog17:01
openstackMeeting started Thu Aug  4 17:01:16 2016 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at
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
docaedoWe usually start with status updates, but I'll start a small/easy (maybe?) topic real quick, since the rest of the meeting is mostly going to be status updates and talking about them17:02
mfedosinsskripnick is sick17:02
*** bklei has quit IRC17:02
docaedomfedosin: unacceptable! app-catalog has no sick days!17:02
docaedo#topic Review and merge policies (docaedo)17:02
*** openstack changes topic to "Review and merge policies (docaedo) (Meeting topic: app-catalog)"17:02
*** sambetts is now known as sambetts|afk17:03
docaedoI brought this up because I realize we've never (as a team) formally talked about this17:03
*** flaper87 has quit IRC17:03
docaedoand the way I review and merge additions to assets is different from how I consider anything that could actually break the web site17:03
docaedoso just wanted to state how I'm doing it, and see if there's agreement or if anyone thinks I'm being too crazy with the +W17:04
docaedoif it's just adding or updating assets (touching assets.yaml) I do not think we need to sit on those updates, and I feel like it's safe for me (or other cores, which really now is just kzaitsev_mb) to merge if it looks good17:05
docaedobut if it's a schema change or something that impacts the web site, there should be at least one other reviewer, and generally should sit for 24 hours to give anyone who cares a chance to look at it17:05
docaedothoughts/opinions on that?17:05
kzaitsev_mbso you basically suggest a single +2+A policy for changes, that only affect assets.yaml17:06
docaedokzaitsev_mb: yes, well said17:07
kzaitsev_mbsounds reasonable to me, since it shouldn't break anything, and many projects have very similar rules, say for i18n commits or proposal bot commits17:07
mfedosin+1. I see nothing bad in it17:08
docaedocool thanks - I wanted to make sure everyone was OK with that just in case I was being too much of a cowboy17:09
docaedo#topic Status updates17:09
*** openstack changes topic to "Status updates (Meeting topic: app-catalog)"17:09
olaphsounds like a plan17:10
mfedosinwe have a big update today17:10
kzaitsev_mb#agreed a single +2+A policy for changes, that only affect assets.yaml17:10
docaedofor me, I'm planning to continue going through bugs and blueprints, just to try to do some grooming17:10
mfedosinGlare leaves Glance project17:10
docaedokzaitsev_mb: thanks17:10
mfedosinthere is a mail in ML17:11
*** sarob has joined #openstack-meeting-317:11
*** matrohon has quit IRC17:11
mfedosinI think it'll help us to move forward faster17:11
docaedomfedosin: yeah I saw that .. it makes sense, is a little unfortunate that it's come to that, but I can see why.  If just talking about storing a disk image leads to so much confusion, I don't see how glare can continue as is17:11
mfedosinso, we'll spend next week moving our code to the new repo17:12
docaedomfedosin: as asked by SpamapS it would be good to put together a clear retrospective on this to also share, so people can see why you felt the split was the best step forward17:12
kzaitsev_mbthis one? ^^17:12
*** belmoreira has quit IRC17:13
*** _sarob has joined #openstack-meeting-317:13
docaedokzaitsev_mb: thats the one17:13
mfedosinkzaitsev_mb: correct17:13
docaedotim and clint asked good question on the thread and are making good points, that this will hurt adoption, but from what I saw it sounded like glance project had said there would be very long term restrictions on what "glare" would be allowed to do while under glance, is that right?17:14
*** zhipeng_ has quit IRC17:14
*** zhipeng has joined #openstack-meeting-317:15
mfedosindocaedo: unfortunately yes17:15
*** lpetrut has quit IRC17:15
mfedosinthere were no specs merged in Glance during Newton cycle17:15
mfedosinno new features had been added since Juno cycle17:16
*** sarob has quit IRC17:16
mfedosinand I'm afraid that the same may happen with Glare17:16
*** SumitNaiksatam has quit IRC17:16
*** tovchinnikova has quit IRC17:17
*** s3wong has joined #openstack-meeting-317:17
mfedosinWe may wallow in useless discussions if we stay in Glance17:17
mfedosinso, have you seen what sskripnick did?17:18
*** gouthamr_afk has quit IRC17:18
docaedoI think everything else to talk about today falls under this topic:17:18
docaedo#topic Next steps for Glare integration17:18
*** openstack changes topic to "Next steps for Glare integration (Meeting topic: app-catalog)"17:18
docaedoSounds like you will have some work this next week to move the repo17:18
docaedoI was wondering if I could get the deployment information for that test environment?17:19
docaedoI'd like to recreate it on a different machine and start working through the puppet manifest we'll need to deploy it to production17:19
docaedoand once I have a "close enough" version (even if it's not complete), I can commit a review for infra to look at17:19
mfedosinyes, but for sure code will be merged before the week after17:19
docaedothen we'll get that up on a staging VM to work through integration with swift, DB, etc17:20
mfedosinhe added auth with OpenID, adding new artifacts, and so on17:20
kzaitsev_mbmaybe we should catch sskripnick and demand some (answers) instructions? =)17:20
mfedosinSergey will be available tomorrow17:21
mfedosinand we can chat with him17:21
docaedokzaitsev_mb: good plan, hopefully he'll be feeling better17:21
mfedosinalso he pushed all code on review17:21
docaedotomorrow will be a really good day for me to work on that too, if we have a chance any way17:21
kzaitsev_mbgotta ping him anyway on the fate of our commits with v0.117:22
kzaitsev_mbprobably we would abandon them17:22
mfedosinkzaitsev_mb: they should be abandoned :)17:22
kzaitsev_mbjust need a confirmation from his side, then17:23
mfedosinHe agrees with that, I know17:23
mfedosinkzaitsev_mb: okay, let's wait for tomorrow and get his confirmation17:24
docaedosounds like there's not much more on this then, until we get more details tomorrow?  and of course the big news of glare splitting out17:24
mfedosindocaedo: I have several questions about storing images...17:24
mfedosinfirst of all, is there any storage for binary assets in App-Catalog?17:25
docaedook great, ask away, let's talk!17:25
mfedosinlike swift or ceph or anything else?17:25
docaedomfedosin: binary assets will be stored in swift17:25
docaedoswift will not run on that node, we'll get credentials to it17:25
mfedosindocaedo: cool, swift is good17:25
mfedosinwhat about images?17:26
mfedosindo we have any plans to store them in our local swift?17:26
mfedosinor we just want provide link to some external sources17:26
docaedomfedosin: images could be store the same way in swift (as they are in the CDN now), but maybe the question is do we provide a direct link to swift, or proxy everything through glare?17:27
docaedoI don't know how glare handles versions with respect to the object itself? I assume because of versions, we'll need glare to proxy everything17:28
mfedosinif we add image to glare directly, then it will be proxied17:28
docaedo(and I'm not sure what you mean when you say "local swift", because we won't run swift on the app-catalog VM)17:28
mfedosinyeah, by "local swift" I mean swift we have credentials for17:29
docaedomfedosin: ah right, ok - then yes, plan will be to store things in local swift if the user wants, otherwise they can just put in an entry that has a pointer to something external (like with heat templates)17:29
mfedosinthat's great, glare supports both ways - with internal and external locations17:30
docaedowe will need both types, some users will want to just point (like pointing at a coreos weekly image or something) vs. I know murano wants the images to be stored in the app catalog17:30
docaedogreat, I know that was the plan we discussed long ago, so happy it's still the plan17:30
mfedosinI just wanted to understand what to do with images17:31
mfedosinalso, there is another topic17:32
docaedothank you for asking and making sure we're on the same page17:32
mfedosinI think we have to make glare to provide public api17:32
mfedosinso, there will be a web site (app-catalog) and near there will be genereic glare api17:33
mfedosinfor glare-to-glare communication17:33
docaedosure, I think it's just going to be a route so -> glare17:33
mfedosinand for Horizon plugin17:33
docaedothat should work, right?17:34
mfedosinimarnat asked to write docs about app-catalog/glare integration17:34
mfedosinoops, kzaitsev_mb corrected me17:35
*** dasanind has joined #openstack-meeting-317:35
mfedosinwe decided, that it will be just new domain17:37
docaedothat's a good point, to make sure we are covering everything on the docs17:37
mfedosinlike -> glare17:37
docaedonew domain? what do you mean?17:37
*** stanchan has quit IRC17:37
docaedooh for direct glare access, I don't remember that but I do not object and it seems reasonable17:38
kzaitsev_mbas long as glare is protected via the same auth17:38
mfedosinyes, for direct glare access17:38
kzaitsev_mbmfedosin: docaedo: it would be trivial to route to actually =)17:39
kzaitsev_mbso the direct access can still be proxied with not-so-direct access )17:39
*** rockyg has quit IRC17:40
mfedosinand for sure there will be -> glare17:40
docaedonice - so how should we tackle the documentation?17:41
*** SumitNaiksatam has joined #openstack-meeting-317:42
docaedoI am sure we all agree SOMEONE should write the documentation :)17:44
mfedosinI hope to start the documentation next week17:44
docaedo#action mfedosin foolishly agrees to start the documentation17:44
mfedosinI'll be on vacation, but I'll be able to find some time17:44
docaedooh wait! don't do that on vacation!17:44
*** Marcellin_ has joined #openstack-meeting-317:45
*** Sukhdev has quit IRC17:45
docaedomfedosin: but if you start an outline on an etherpad and share it on #openstack-app-catalog I can help, and hopefully others as well17:46
mfedosinI don't like write docs in etherpad17:47
mfedosinI prefer google docs17:47
*** spzala has quit IRC17:48
docaedomfedosin: sure, that can work for collaborating, then ultimately it would need to go into probably app-catalog/docs repo17:48
mfedosinI'll add as a reviewer17:48
*** vishwanathj has quit IRC17:48
docaedothat works for me17:48
*** spzala has joined #openstack-meeting-317:48
*** ddieterly is now known as ddieterly[away]17:49
docaedo#topic Open discussion17:50
*** openstack changes topic to "Open discussion (Meeting topic: app-catalog)"17:50
docaedoAnyone have anything for open discussion today?17:50
olaphnot I17:51
mfedosinI learned everything I wanted.17:51
kzaitsev_mbnot me, I've just returned from vacations and trying to deal with the ammount of mail I have to read/respond to )17:51
docaedokzaitsev_mb: just declare unread email bankruptcy and mark it all as read!17:52
docaedoOK I think we are done then, thanks everyone, and looking forward to talking hopefully more on glare stuff tomorrow!17:52
*** spzala has quit IRC17:53
*** rkukura has joined #openstack-meeting-317:53
*** openstack changes topic to " (Meeting topic: ops_guide)"17:53
openstackMeeting ended Thu Aug  4 17:53:37 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:53
openstackMinutes (text):
olaphthanks all!17:53
*** spzala has joined #openstack-meeting-317:54
*** _sarob has quit IRC17:57
*** bklei_ has quit IRC17:58
*** kzaitsev_mb has quit IRC17:58
*** bklei has joined #openstack-meeting-317:59
SumitNaiksatamrkukura: hi18:00
rkukurahi SumitNaiksatam18:00
SumitNaiksatamigordcard: hi18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu Aug  4 18:00:50 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
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
*** elmiko has left #openstack-meeting-318:01
SumitNaiksatam#info agenda
*** ccamacho has quit IRC18:01
SumitNaiksatamigordcard: there?18:01
*** s3wong has quit IRC18:01
SumitNaiksatam#topic L3-Policy mapping to Address Scope & Subnetpool18:02
*** openstack changes topic to "L3-Policy mapping to Address Scope & Subnetpool (Meeting topic: networking_policy)"18:02
*** julim has quit IRC18:02
SumitNaiksatami need at least one more +2 on this one ;-)18:02
*** shamail has joined #openstack-meeting-318:02
SumitNaiksatamrkukura: if you can take a look that will be great18:03
rkukuraSumitNaiksatam: Yes, I do plan to re-review ASAP18:03
SumitNaiksatamrkukura: great, thanks18:04
*** rockyg has joined #openstack-meeting-318:04
SumitNaiksatamanything we can discuss here on that topic?18:04
*** stanchan has joined #openstack-meeting-318:05
*** julim has joined #openstack-meeting-318:05
rkukuraI have not looked at it or thought too much about it since last time, so I don’t have anything new right now.18:05
SumitNaiksatamrkukura: okay18:05
SumitNaiksatamseems like all our other team members are MIA18:06
*** mfedosin has quit IRC18:06
SumitNaiksatam#topic Quality of Service support via NSPs18:06
*** openstack changes topic to "Quality of Service support via NSPs (Meeting topic: networking_policy)"18:06
SumitNaiksatami think igordcard has been having some problems with the integration test setup18:06
SumitNaiksatami think i know what the issue is, and was hoping to discuss it with him here18:07
SumitNaiksatami will put the comments on the review directly18:07
rkukuramake sense18:07
SumitNaiksatamrkukura: not sure you get a chance to look at the patch18:07
*** tsufiev has left #openstack-meeting-318:07
SumitNaiksatamrkukura: i was leaning towards merging this in the feature branch if it looks sane18:08
rkukuranot recently - I’ll try to review it soon18:08
SumitNaiksatamwe can separately consider when and how to merge it into master18:08
SumitNaiksatamrkukura: sure18:08
*** lpetrut has joined #openstack-meeting-318:09
SumitNaiksatami dont how much else for today18:09
SumitNaiksatamrkukura: anything else at your end?18:09
*** olaph has left #openstack-meeting-318:10
SumitNaiksatamif not we can go back to working on AIM :-)18:10
rkukurayes, that’s what’s on my mind18:10
*** openstack changes topic to " (Meeting topic: ops_guide)"18:11
openstackMeeting ended Thu Aug  4 18:11:19 2016 UTC.  Information about MeetBot at . (v 0.1.4)18:11
openstackMinutes (text):
rkukurathat extension manager issue I was talking with you about a few days ago popped up again, costing me most of another day :(18:11
rkukuraSumitNaiksatam: I hope I’ll have at least that resolved by the meeting in <2 hours18:12
*** rkukura has left #openstack-meeting-318:12
*** tpeoples has quit IRC18:12
*** stanchan has quit IRC18:15
*** toddjohn has quit IRC18:16
*** toddjohn has joined #openstack-meeting-318:16
*** alexismonville has quit IRC18:17
*** tonytan4ever has joined #openstack-meeting-318:21
*** Sukhdev has joined #openstack-meeting-318:22
*** kebray has joined #openstack-meeting-318:24
*** sarob has joined #openstack-meeting-318:26
*** songole has joined #openstack-meeting-318:29
*** mickeys has quit IRC18:29
*** tenobreg has joined #openstack-meeting-318:29
*** mickeys has joined #openstack-meeting-318:30
*** tellesnobrega has quit IRC18:32
*** mickeys has quit IRC18:34
*** singlethink has quit IRC18:40
*** ddieterly[away] is now known as ddieterly18:47
*** mohankumar__ has quit IRC18:53
*** stanchan has joined #openstack-meeting-318:54
*** stanchan has quit IRC18:55
*** ddieterly is now known as ddieterly[away]18:55
*** pvaneck has joined #openstack-meeting-318:56
*** stanchan has joined #openstack-meeting-318:56
*** toddjohn has quit IRC18:59
*** MeganR has joined #openstack-meeting-318:59
*** toddjohn has joined #openstack-meeting-319:01
shamail#startmeeting auc19:01
openstackMeeting started Thu Aug  4 19:01:26 2016 UTC and is due to finish in 60 minutes.  The chair is shamail. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: auc)"19:01
openstackThe meeting name has been set to 'auc'19:01
shamailHi everyone.  Who is here for the AUC recognition meeting?19:01
shamailHi MeganR19:02
shamailHow was your break?19:02
MeganRit was great, but catching up from being out isn't fun19:03
shamail+1 :)19:03
MeganRthat will teach me to take a week off without internet  :)19:03
*** vgridnev has quit IRC19:03
shamailHere is agenda I had hoped we could cover today but Summer vacations seems to be keeping our attendance low :)19:03
shamailLet’s tackle what we can and then close it out, sound good?19:04
MeganRI would be fine for a shorter meeting - then I can work on my "tasks" for here  :)19:04
shamail#topic Update on data collection for non-IRC WGs19:04
*** openstack changes topic to "Update on data collection for non-IRC WGs (Meeting topic: auc)"19:04
shamailHave you had a chance to reach out to the WGs that do not use IRC yet?19:05
shamailIf not, do you want help?19:05
*** ccamacho has joined #openstack-meeting-319:05
MeganRSo, I started today going through some meeting notes on the WG that are not using IRC, going back about 5-6 weeks, and taking an average of the attendees.  I figure that will help with a number.19:05
MeganRThen I need to send out two emails - one for the attendee count, asking the chairs to verify and the second for the Google form review - I didn't have a chance to send that out earlier.19:06
shamailCould you reach out to the WG chairs and just ask them to provide you with a list of active members?19:06
*** xavierr|mtg is now known as xavierr19:06
shamailI feel it is unfair for you to be gathering that information for all of them on your own19:06
shamailThe chairs should be able to knock it out fairly quick19:07
shamailIs it just Enterprise and Faulty Genes?19:07
MeganRnp - I'll do that this afternoon - and ISV  :)19:07
*** fifieldt has quit IRC19:07
shamailAwesome, thanks19:07
shamailOh yeah, ISV19:07
MeganRI was thinking, if someone has attended within the past month we count them as active19:08
shamailThanks MeganR!19:08
*** songole has quit IRC19:08
shamailWe could also have the other scenario though (someone has been active but has gone on extended break for summer)19:08
shamailOkay to move on?19:09
MeganRvery true - I was thinking more along the lines of something easy for them to pull together, and will give us a rough estimate.19:09
MeganRyup - good to go19:09
shamailFair :)19:09
shamail#topic Update on preliminary count19:09
*** openstack changes topic to "Update on preliminary count (Meeting topic: auc)"19:09
shamailHere is what I have so far… still missing some but in good shape I think:19:10
shamailRunning totals (as of 07/14/2016):19:10
shamailCommitters to UC governed repositories (OSOps, User Stories, Ops-Tags): 1919:10
shamailActive WG members (for WGs that use IRC): 2819:10
shamailAsk OpenStack moderators: 2019:10
shamailTrack chairs for upcoming summit: 9819:10
shamailOrganizers of Official OpenStack User Groups: 4619:10
shamailContributors to Superuser: 2819:10
shamailOverall AUC Count (duplicates have not been removed from data): 23919:10
shamailData that still needs to be collected (as of 08/02/2016):19:11
shamailActive WG members (for WGs not on IRC): TBD19:11
shamailOps Meetup Moderators: TBD19:11
*** armax_ has joined #openstack-meeting-319:11
shamailThe count is lower than I anticipated so far19:11
shamailI don’t think the remaining two categories will increase it significantly19:11
MeganRI agree, especially thing that there are some duplicates - interesting19:11
*** armax has quit IRC19:12
*** armax_ is now known as armax19:12
shamailOnce we get the final two categories we can share the findings with UC19:12
MeganRsounds good19:12
shamail#topic Discussion on AUC status cycle19:13
*** openstack changes topic to "Discussion on AUC status cycle (Meeting topic: auc)"19:13
*** sdake_ has joined #openstack-meeting-319:13
shamailSo Tom and I have been having a conversation in gerrit on a patch I submitted19:13
*** VW has quit IRC19:13
shamailTom was proposing that we run the count more often (rather than once per cycle) and also questioning how long AUC status is valid19:14
shamailHe raised some great points and gave some good reference links in his last comment19:14
shamailKey questions/considerations:19:14
shamailCorrect me if I'm wrong here, but it seems much of the thinking is around getting an AUC designation on summit badges? If so, I'd advise trying to think more broadly, but to complete this one first: did you know that ATC discount codes are sent out at multiple points throughout the cycle? Part of the reasoning behind that is to encourage those qualifying to register early so we have the best possible idea of numbers as early as we can.19:15
shamailHow about User Committee Voting. That might happen in January, for instance. Assuming AUC members are qualified to vote, when is their eligibility determined? From the last list made in milestone 3 of whatever release cycle was previously done?19:15
*** maishsk has joined #openstack-meeting-319:15
shamailHow does that kind of script work for AUC candidates standing for the UC election?19:15
maishskSorry I am late19:15
shamailMore outlandish: what about if the foundation somehow falls upon a ton of stickers and some stamps/envelopes and want to mail AUC recipients some "tomorrow"19:15
shamailHi maishsk, np19:15
shamail#chair maishsk19:15
openstackCurrent chairs: maishsk shamail19:15
MeganRHi maishsk19:15
maishskHi All19:15
*** sdake has quit IRC19:16
shamailmaishsk: we are discussing comments by Tom on
MeganRHe brings up great points, and now I think I understand what he was originally asking19:17
shamailI will investigate whether we can modify for UC election eligbility19:17
shamail#action Research modifying ATC election eligibility script for AUC (shamail)19:17
shamailSame here MeganR19:17
MeganRand if we automate most of this, we should be able to run it whenever necessary19:17
*** fifieldt has joined #openstack-meeting-319:18
shamailwelcome fifieldt19:18
shamailwe were just talking about our conversation on
shamailSo how can we address these items?19:18
*** vishwanathj has joined #openstack-meeting-319:19
shamailDo we think the AUC ‘term’ should be from milestone-3 to milestone-3… This would allow someone to get badge status at the summit following their contributions but also stay AUC for a good portion of the next cycle to be eligible for elections and voting19:19
* shamail putting together an example using real world dates19:20
maishskSo I am trying to understand the issue here - is it one of timing? Length of validity of the AUC? or something else?19:20
shamailIt is two fold:19:20
shamail1) The timing of when the data is gathered and how often19:20
*** vishwanathj has quit IRC19:21
shamail2) How long AUC is valid once obtained (the benefits of AUC are applicable beyond the summit itself since they are eligible to stand for and vote in UC elections)19:21
*** vishwanathj has joined #openstack-meeting-319:21
shamailFor example, if we did milestone-3 to milestone-3 between Mitaka and Liberty...19:22
*** ddieterly[away] is now known as ddieterly19:23
*** Benj_ has joined #openstack-meeting-319:23
*** uxdanielle has joined #openstack-meeting-319:24
shamailFor the Mitaka summit, any AUC contributions made after  Liberty milestone-3 (roughly Sept 2015) would qualify someone to have AUC badge in the summit19:24
shamailSubsequently, the person would’ve stayed ‘AUC’ until Feb 201619:24
shamailWhich means they could’ve voted in Mitaka UC elections (if there was such a thing) if they happened a month or two after the release of Liberty19:25
*** ihrachys has joined #openstack-meeting-319:25
shamailWe could also collect the data (and have scripts handy to do ad-hoc collection) at least once a month.19:26
maishskI am sorry - but it could be the late hour - and me spacing out - but I still do not understand the issue19:26
shamailThe issue is how long should AUC be valid to allow for summit benefits and any additional rights during the release cycle.19:26
shamailWe had discussed one release cycle (forward facing… so a contribution right now would give someone AUC for Ocata)19:27
shamailbut does that actually work or should status have some buffer beyond a release cycle for elections19:27
*** Benj_ has quit IRC19:28
shamailI guess as I am writing this, one question that we probably need to know the answer to (before we could formulate a response to the current challenge) is what does the UC think will be there election cycle19:28
maishskHonestly - I have not really given this any thought - but I feel I must ask - are we trying to re-invent the wheel?19:28
shamailOn the contrary, I think we want to align this as closely to ATC schedules as possible so the question becomes how.19:29
maishskI assume that all these questions are not only for the AUC - they should be relevant for the ATC as well - so why should the AUC be any different?19:29
shamailmaishsk: +119:29
MeganRI agree - and honestly, the thought of voting had not even occurred to me.19:30
shamailI’ll do some more work here and come back with a formulated response to how we can closely align with ATC’s answers to these questions19:30
maishskAnd regarding the voting cycle - I would hope that the UC elections - if and when they occur - will also align with the ATC19:30
*** vishwanathj has quit IRC19:31
shamailmaishsk: +1 but we need the UC to tell us if they plan to align with the TC schedule (7 positions in spring, 6 in fall)19:31
shamailor whether they will have elections for all members at once (per year)19:31
*** vishwanathj has joined #openstack-meeting-319:31
shamailWe need to align with ATC and UC should align with TC19:31
shamail#action Send an email to UC to understand their thoughts on the election process in the future19:32
shamailAnything else on this topic for now?  Sorry, for not articulating it properly initially but I think we are all on the same page now19:33
*** vishwanathj has quit IRC19:33
MeganRthat sounds good19:33
shamail#topic Milestone-5 update19:33
*** openstack changes topic to "Milestone-5 update (Meeting topic: auc)"19:33
*** vishwanathj has joined #openstack-meeting-319:33
shamailmaishsk: Have you had a chance to make any more edits to the “self-nomination” process for AUC?19:34
shamailor do we consider it being in good shape and just need to summarize it?19:34
maishskI did not really have a chance to go over it - but I think we are in good shape19:35
shamailDo you mind summarize the proposal and sending it to the UC to get their feedback?19:35
*** tonytan_brb has joined #openstack-meeting-319:36
*** Benj_ has joined #openstack-meeting-319:36
*** stanchan has quit IRC19:36
maishskI will draw up a summary19:37
maishsk#action maishsk will summarize up Milestone 5 and send out to UC19:37
shamail#action Summarize milestone-5 output and validate desired AUC self-nomination review committee composition and process (maishsk)19:37
shamail#topic Opens19:37
*** openstack changes topic to "Opens (Meeting topic: auc)"19:38
shamailDoes anyone else have additional topics for today?19:38
maishskNot really - but I was going over the milestones we set19:38
*** VW has joined #openstack-meeting-319:38
*** baoli has quit IRC19:38
maishskand looking at #719:38
*** tonytan4ever has quit IRC19:38
*** Sukhdev has quit IRC19:39
maishskIt is quite vague19:39
shamailmaishsk: +1, I will go ahead and remove it19:40
maishskCreate a model of estimated costs while working with user committee on new charter19:40
shamailthats more of a UC thing19:40
maishskThat was my thought as well19:40
maishskthanks shamail19:40
shamailAlright, have a great day/evening!19:40
*** openstack changes topic to " (Meeting topic: ops_guide)"19:40
openstackMeeting ended Thu Aug  4 19:40:52 2016 UTC.  Information about MeetBot at . (v 0.1.4)19:40
openstackMinutes (text):
maishskThanks all19:40
*** itxaka has quit IRC19:41
*** MeganR has quit IRC19:42
*** baoli has joined #openstack-meeting-319:42
*** jrist has quit IRC19:43
*** kzaitsev_mb has joined #openstack-meeting-319:45
*** lblanchard has quit IRC19:47
*** kzaitsev_mb has quit IRC19:50
*** kzaitsev_mb has joined #openstack-meeting-319:52
*** maishsk has quit IRC19:53
*** rakhmerov has quit IRC19:53
*** shamail has left #openstack-meeting-319:53
*** dasanind has quit IRC19:55
*** maishsk has joined #openstack-meeting-319:56
*** jrist has joined #openstack-meeting-319:56
*** vhoward has joined #openstack-meeting-319:57
*** rakhmerov has joined #openstack-meeting-319:57
*** matrohon has joined #openstack-meeting-319:58
*** maishsk has quit IRC19:59
*** kebray has quit IRC19:59
*** vishwanathj has quit IRC19:59
*** rockyg has quit IRC19:59
*** vishwanathj has joined #openstack-meeting-319:59
*** asettle has joined #openstack-meeting-320:00
*** maishsk has joined #openstack-meeting-320:03
*** asettle has quit IRC20:04
*** s3wong has joined #openstack-meeting-320:08
*** baoli has quit IRC20:13
*** markvoelker has quit IRC20:13
*** baoli has joined #openstack-meeting-320:14
*** vishwanathj has quit IRC20:14
*** vishwanathj has joined #openstack-meeting-320:14
*** stanchan has joined #openstack-meeting-320:15
*** toddjohn has quit IRC20:16
*** flwang1 has quit IRC20:16
*** sarob has quit IRC20:20
*** banix has quit IRC20:22
*** kzaitsev_mb has quit IRC20:23
*** ihrachys has quit IRC20:29
*** abalutoiu has joined #openstack-meeting-320:31
*** lpetrut has quit IRC20:33
*** lpetrut has joined #openstack-meeting-320:35
*** abalutoiu_ has joined #openstack-meeting-320:37
*** jrist has quit IRC20:38
*** vishwanathj has quit IRC20:38
*** vishwanathj has joined #openstack-meeting-320:39
*** abalutoiu has quit IRC20:39
*** vishwanathj has quit IRC20:40
*** vishwanathj has joined #openstack-meeting-320:41
*** stanchan has quit IRC20:41
*** dimtruck is now known as zz_dimtruck20:42
*** pvaneck_ has joined #openstack-meeting-320:43
*** stanchan has joined #openstack-meeting-320:45
*** pvaneck has quit IRC20:46
*** tonytan_brb has quit IRC20:48
*** jrist has joined #openstack-meeting-320:50
*** zz_dimtruck is now known as dimtruck20:50
*** bklei_ has joined #openstack-meeting-320:53
*** bklei has quit IRC20:56
*** matrohon has quit IRC20:57
*** piet_ has quit IRC20:59
*** vhoward has quit IRC21:00
*** mickeys has joined #openstack-meeting-321:02
*** baoli_ has joined #openstack-meeting-321:02
*** rtheis has quit IRC21:03
*** baoli has quit IRC21:04
*** vishwanathj has quit IRC21:05
*** vishwanathj has joined #openstack-meeting-321:06
*** yamamoto has joined #openstack-meeting-321:06
*** mickeys has quit IRC21:07
*** vishwanathj has quit IRC21:11
*** vishwanathj has joined #openstack-meeting-321:11
*** baoli_ has quit IRC21:12
*** s3wong_ has joined #openstack-meeting-321:12
*** baoli has joined #openstack-meeting-321:12
*** yamamoto has quit IRC21:13
*** vishwanathj has quit IRC21:13
*** vishwanathj has joined #openstack-meeting-321:13
*** s3wong has quit IRC21:15
*** vishwanathj has quit IRC21:16
*** vishwanathj has joined #openstack-meeting-321:16
*** ddieterly is now known as ddieterly[away]21:17
*** s3wong_ is now known as s3wong21:17
*** baoli has quit IRC21:18
*** julim has quit IRC21:18
*** julim has joined #openstack-meeting-321:18
*** baoli has joined #openstack-meeting-321:18
*** stanchan has quit IRC21:18
*** Sukhdev has joined #openstack-meeting-321:18
*** stanchan has joined #openstack-meeting-321:20
*** julim has quit IRC21:23
*** vishwanathj has quit IRC21:24
*** vishwanathj has joined #openstack-meeting-321:24
*** baoli has quit IRC21:26
*** sarob has joined #openstack-meeting-321:26
*** bklei_ has quit IRC21:27
*** amotoki has quit IRC21:27
*** bklei has joined #openstack-meeting-321:28
*** yamahata has quit IRC21:30
*** bklei has quit IRC21:30
*** sarob has quit IRC21:31
*** bklei has joined #openstack-meeting-321:31
*** spzala has quit IRC21:32
*** spzala has joined #openstack-meeting-321:32
*** dimtruck is now known as zz_dimtruck21:36
*** spzala has quit IRC21:36
*** vishwanathj has quit IRC21:37
*** flwang1 has joined #openstack-meeting-321:37
*** vishwanathj has joined #openstack-meeting-321:37
*** VW has quit IRC21:38
*** vishwanathj has quit IRC21:38
*** VW has joined #openstack-meeting-321:38
*** vishwanathj has joined #openstack-meeting-321:39
*** mickeys has joined #openstack-meeting-321:40
*** davidmichaelkarr has left #openstack-meeting-321:40
*** galstrom is now known as galstrom_zzz21:42
*** zz_dimtruck is now known as dimtruck21:43
*** vishwanathj has quit IRC21:44
*** vishwanathj has joined #openstack-meeting-321:45
*** cleong has quit IRC21:46
*** kzaitsev_mb has joined #openstack-meeting-321:48
*** ddieterly[away] is now known as ddieterly21:48
*** yamahata has joined #openstack-meeting-321:49
*** vishwanathj has quit IRC21:49
*** vishwanathj has joined #openstack-meeting-321:50
*** vishwanathj has quit IRC21:53
*** amotoki has joined #openstack-meeting-321:53
*** vishwanathj has joined #openstack-meeting-321:54
*** banix has joined #openstack-meeting-322:01
*** Benj_ has quit IRC22:02
*** bklei has quit IRC22:02
*** VW has quit IRC22:03
*** s3wong has quit IRC22:05
*** bpokorny_ has joined #openstack-meeting-322:05
*** s3wong has joined #openstack-meeting-322:05
*** sarob has joined #openstack-meeting-322:07
*** bpokorny has quit IRC22:08
*** bpokorny_ has quit IRC22:09
*** vishwanathj has quit IRC22:14
*** vishwanathj has joined #openstack-meeting-322:15
*** piet_ has joined #openstack-meeting-322:18
*** stanchan has quit IRC22:18
*** stanchan has joined #openstack-meeting-322:20
*** kzaitsev_mb has quit IRC22:27
*** stanchan has quit IRC22:30
*** zhipeng has quit IRC22:31
*** lpetrut has quit IRC22:32
*** bklei has joined #openstack-meeting-322:32
*** spzala has joined #openstack-meeting-322:33
*** dimtruck is now known as zz_dimtruck22:34
*** spzala has quit IRC22:38
*** VW has joined #openstack-meeting-322:42
*** s3wong_ has joined #openstack-meeting-322:45
*** s3wong has quit IRC22:49
*** s3wong_ is now known as s3wong22:49
*** notmars has quit IRC22:50
*** spzala has joined #openstack-meeting-322:50
*** sdague has quit IRC22:52
*** stanchan has joined #openstack-meeting-322:52
*** kzaitsev_mb has joined #openstack-meeting-322:54
*** rbak has quit IRC22:55
*** ddieterly is now known as ddieterly[away]22:58
*** ddieterly[away] has quit IRC22:58
*** kzaitsev_mb has quit IRC23:01
*** seldenr has quit IRC23:02
*** sarob has quit IRC23:02
*** asettle has joined #openstack-meeting-323:03
*** asettle has quit IRC23:07
*** Swami has quit IRC23:09
*** kzaitsev_mb has joined #openstack-meeting-323:13
*** kzaitsev_mb has quit IRC23:19
*** VW has quit IRC23:20
*** revon has quit IRC23:20
*** markvoelker has joined #openstack-meeting-323:28
*** amotoki has quit IRC23:28
*** zz_dimtruck is now known as dimtruck23:30
*** marst has quit IRC23:32
*** mrmartin has quit IRC23:34
*** toddjohn has joined #openstack-meeting-323:34
*** VW has joined #openstack-meeting-323:36
*** markvoelker_ has joined #openstack-meeting-323:37
*** toddjohn has quit IRC23:38
*** toddjohn has joined #openstack-meeting-323:38
*** markvoelker has quit IRC23:41
*** stanchan has quit IRC23:43
*** sdake has joined #openstack-meeting-323:44
*** sdake_ has quit IRC23:46
*** yushiro has joined #openstack-meeting-323:49
*** marst has joined #openstack-meeting-323:49
*** yushiro has left #openstack-meeting-323:49
*** kzaitsev_mb has joined #openstack-meeting-323:51
*** mickeys has quit IRC23:54
*** zhurong has joined #openstack-meeting-323:55
*** stanchan has joined #openstack-meeting-323:56
*** vishwanathj has quit IRC23:56
*** piet_ has quit IRC23:56
*** Marcellin_ has quit IRC23:57

Generated by 2.14.0 by Marius Gedminas - find it at!