Thursday, 2016-04-07

*** zz_dimtruck is now known as dimtruck00:00
*** dimtruck is now known as zz_dimtruck00:13
*** tqtran has quit IRC00:15
*** iyamahat has quit IRC00:17
*** hoangcx has quit IRC00:23
*** hoangcx has joined #openstack-meeting-300:23
*** ddieterly[away] has quit IRC00:26
*** mtanino__ has joined #openstack-meeting-300:27
*** rmoe has quit IRC00:28
*** mtanino has quit IRC00:28
*** rmoe has joined #openstack-meeting-300:28
*** vtech has quit IRC00:33
*** dslevin has joined #openstack-meeting-300:33
*** mtanino__ has quit IRC00:33
*** dslevin has quit IRC00:34
*** hoangcx has quit IRC00:34
*** dslevin has joined #openstack-meeting-300:34
*** absubram has quit IRC00:34
*** hoangcx has joined #openstack-meeting-300:35
*** dslevin has quit IRC00:35
*** dslevin has joined #openstack-meeting-300:35
*** dslevin has quit IRC00:36
*** dslevin has joined #openstack-meeting-300:37
*** dslevin has quit IRC00:37
*** baojg has joined #openstack-meeting-300:37
*** dslevin has joined #openstack-meeting-300:39
*** dslevin has quit IRC00:39
*** jrist has quit IRC00:39
*** ddieterly has joined #openstack-meeting-300:40
*** dslevin has joined #openstack-meeting-300:41
*** dslevin has quit IRC00:42
*** jrist has joined #openstack-meeting-300:42
*** sc68cal has quit IRC00:42
*** dslevin has joined #openstack-meeting-300:43
*** dslevin has quit IRC00:43
*** mickeys has quit IRC00:45
*** mickeys has joined #openstack-meeting-300:48
*** annegentle has joined #openstack-meeting-300:49
*** mickeys has quit IRC00:52
*** zz_dimtruck is now known as dimtruck00:54
*** clu_ has quit IRC00:54
*** annegentle has quit IRC00:54
*** iyamahat has joined #openstack-meeting-300:55
*** alexpilotti has quit IRC00:57
*** zhurong has joined #openstack-meeting-300:58
*** alexpilotti has joined #openstack-meeting-301:01
*** bpokorny has quit IRC01:02
*** pvaneck has quit IRC01:03
*** tqtran has joined #openstack-meeting-301:11
*** tqtran has quit IRC01:16
*** absubram has joined #openstack-meeting-301:17
*** kebray_ has quit IRC01:21
*** stanzgy has joined #openstack-meeting-301:21
*** reedip has quit IRC01:22
*** reedip has joined #openstack-meeting-301:25
*** sdake has quit IRC01:28
*** sdake has joined #openstack-meeting-301:32
*** ajmiller has joined #openstack-meeting-301:38
*** ajmiller has quit IRC01:39
*** julim has joined #openstack-meeting-301:40
*** baoli has joined #openstack-meeting-301:44
*** baoli has quit IRC01:47
*** ddieterly is now known as ddieterly[away]01:47
*** baoli has joined #openstack-meeting-301:48
*** alexpilotti has quit IRC01:50
*** toddjohn has joined #openstack-meeting-301:50
*** toddjohn has quit IRC01:53
*** toddjohn has joined #openstack-meeting-301:53
*** s3wong has quit IRC01:54
*** Poornima has joined #openstack-meeting-301:54
*** JieLi has joined #openstack-meeting-301:57
*** toddjohn has quit IRC01:58
*** alexpilotti has joined #openstack-meeting-302:01
*** hoangcx has quit IRC02:02
*** salv-orlando has joined #openstack-meeting-302:03
*** hoangcx has joined #openstack-meeting-302:03
*** hoangcx has left #openstack-meeting-302:03
*** alexpilotti has quit IRC02:05
*** baoli has quit IRC02:06
*** Aish has joined #openstack-meeting-302:08
*** Aish has quit IRC02:09
*** pgadiya has joined #openstack-meeting-302:13
*** piet has joined #openstack-meeting-302:17
*** sdake_ has joined #openstack-meeting-302:20
*** ddieterly[away] is now known as ddieterly02:21
*** sdake has quit IRC02:22
*** salv-orlando has quit IRC02:23
*** ddieterly is now known as ddieterly[away]02:26
*** iyamahat has quit IRC02:27
*** salv-orlando has joined #openstack-meeting-302:28
*** salv-orlando has quit IRC02:33
*** piet has quit IRC02:37
*** yamamoto_ has joined #openstack-meeting-302:37
*** alexpilotti has joined #openstack-meeting-302:46
*** alexpilotti has quit IRC02:50
*** iyamahat has joined #openstack-meeting-302:51
*** nick_zhuyj has joined #openstack-meeting-302:53
*** piet has joined #openstack-meeting-302:55
*** steve_ruan has joined #openstack-meeting-302:55
*** nick_zhuyj has quit IRC02:58
*** nick_zhuyj has joined #openstack-meeting-302:59
*** alexpilotti has joined #openstack-meeting-303:00
*** eliqiao has quit IRC03:01
*** openstackstatus has quit IRC03:01
*** zhurong_ has joined #openstack-meeting-303:02
*** zhurong has quit IRC03:02
*** Poornima has quit IRC03:02
*** eliqiao has joined #openstack-meeting-303:02
*** Poornima has joined #openstack-meeting-303:03
*** nick_zhuyj has quit IRC03:04
*** alexpilotti has quit IRC03:05
*** pgadiya has quit IRC03:05
*** pgadiya has joined #openstack-meeting-303:05
*** sdake_ has quit IRC03:06
*** reedip__ has quit IRC03:07
*** sdake has joined #openstack-meeting-303:07
*** reedip__ has joined #openstack-meeting-303:07
*** sdake has quit IRC03:17
*** sdake has joined #openstack-meeting-303:18
*** pgadiya has quit IRC03:19
*** yamamoto_ has quit IRC03:20
*** egallen_ has joined #openstack-meeting-303:20
*** toddjohn has joined #openstack-meeting-303:22
*** egallen has quit IRC03:23
*** egallen_ is now known as egallen03:23
*** ddieterly[away] has quit IRC03:26
*** toddjohn has quit IRC03:27
*** JieLi has quit IRC03:28
*** sdake has quit IRC03:28
*** piet has quit IRC03:29
*** alexpilotti has joined #openstack-meeting-303:32
*** dimtruck is now known as zz_dimtruck03:32
*** vtech has joined #openstack-meeting-303:33
*** piet has joined #openstack-meeting-303:34
*** alexpilotti has quit IRC03:36
*** vtech has quit IRC03:41
*** fitoduarte has joined #openstack-meeting-303:41
*** FallenPegasus has joined #openstack-meeting-303:42
*** neelashah has joined #openstack-meeting-303:49
*** salv-orlando has joined #openstack-meeting-303:50
*** sekrit has quit IRC03:51
*** salv-orlando has quit IRC03:52
*** salv-orlando has joined #openstack-meeting-303:53
*** neelashah has quit IRC03:56
*** piet has quit IRC03:56
*** julim has quit IRC03:57
*** salv-orlando has quit IRC03:58
*** alexpilotti has joined #openstack-meeting-304:00
*** FallenPegasus has quit IRC04:01
*** alexpilotti has quit IRC04:05
*** sekrit has joined #openstack-meeting-304:05
*** numan_ has joined #openstack-meeting-304:07
*** yamamoto_ has joined #openstack-meeting-304:10
*** Sukhdev has joined #openstack-meeting-304:11
*** absubram_ has joined #openstack-meeting-304:14
*** absubram_ has quit IRC04:14
*** absubram has quit IRC04:15
*** amotoki has joined #openstack-meeting-304:20
*** toddjohn has joined #openstack-meeting-304:24
*** iyamahat has quit IRC04:26
*** banix has joined #openstack-meeting-304:26
*** toddjohn has quit IRC04:28
*** persia has quit IRC04:31
*** persia has joined #openstack-meeting-304:33
*** irenab has quit IRC04:37
*** askb has joined #openstack-meeting-304:38
*** eliqiao_ has joined #openstack-meeting-304:43
*** eliqiao has quit IRC04:44
*** salv-orlando has joined #openstack-meeting-304:57
*** armax has quit IRC04:59
*** alexpilotti has joined #openstack-meeting-305:00
*** salv-orlando has quit IRC05:01
*** rossella_s has quit IRC05:03
*** rossella_s has joined #openstack-meeting-305:03
*** Poornima has quit IRC05:03
*** alexpilotti has quit IRC05:05
*** numan_ has quit IRC05:08
*** salv-orlando has joined #openstack-meeting-305:11
*** Poornima has joined #openstack-meeting-305:24
*** hdaniel has joined #openstack-meeting-305:24
*** alexpilotti has joined #openstack-meeting-305:25
*** banix has quit IRC05:25
*** alexpilotti has quit IRC05:30
*** anilvenkata has joined #openstack-meeting-305:33
*** irenab has joined #openstack-meeting-305:36
*** Sukhdev has quit IRC05:40
*** alexpilotti has joined #openstack-meeting-305:41
*** tfukushima has joined #openstack-meeting-305:41
*** alexpilotti has quit IRC05:46
*** nkrinner has joined #openstack-meeting-305:49
*** moshele has joined #openstack-meeting-305:50
*** alexpilotti has joined #openstack-meeting-305:57
*** alexpilo_ has joined #openstack-meeting-306:01
*** alexpilotti has quit IRC06:02
*** lpetrut has joined #openstack-meeting-306:05
*** alexpilo_ has quit IRC06:06
*** numan_ has joined #openstack-meeting-306:10
*** hdaniel has quit IRC06:17
*** scheuran has joined #openstack-meeting-306:22
*** askb has quit IRC06:23
*** moshele has quit IRC06:24
*** toddjohn has joined #openstack-meeting-306:25
*** pcaruana has joined #openstack-meeting-306:26
*** numan_ has quit IRC06:28
*** eliqiao_ is now known as eliqiao06:28
*** numan_ has joined #openstack-meeting-306:28
*** toddjohn has quit IRC06:30
*** alexpilotti has joined #openstack-meeting-306:32
*** mrmartin has joined #openstack-meeting-306:34
*** alexpilotti has quit IRC06:37
*** vtech has joined #openstack-meeting-306:40
*** vtech has quit IRC06:40
*** tqtran has joined #openstack-meeting-306:43
*** vgridnev has joined #openstack-meeting-306:46
*** tqtran has quit IRC06:47
*** salv-orlando has quit IRC06:52
*** woodster_ has quit IRC06:57
*** hdaniel has joined #openstack-meeting-306:58
*** alexpilotti has joined #openstack-meeting-307:00
*** vtech has joined #openstack-meeting-307:04
*** alexpilotti has quit IRC07:04
*** hdaniel has quit IRC07:05
*** mrmartin has quit IRC07:08
*** atuvenie has joined #openstack-meeting-307:11
*** ihrachys has joined #openstack-meeting-307:11
*** jlanoux has joined #openstack-meeting-307:13
*** moshele has joined #openstack-meeting-307:15
*** lpetrut has quit IRC07:21
*** hdaniel has joined #openstack-meeting-307:21
*** pgadiya has joined #openstack-meeting-307:23
*** baojg has quit IRC07:25
*** baojg has joined #openstack-meeting-307:25
*** matrohon has joined #openstack-meeting-307:29
*** mbound has quit IRC07:31
*** rbak has quit IRC07:32
*** rbak has joined #openstack-meeting-307:32
*** mrmartin has joined #openstack-meeting-307:36
*** dedery has joined #openstack-meeting-307:38
*** matrohon_ has joined #openstack-meeting-307:51
*** itxaka has joined #openstack-meeting-307:51
*** matrohon_ has quit IRC07:51
*** hdaniel has quit IRC07:52
*** salv-orlando has joined #openstack-meeting-307:54
*** moshele has left #openstack-meeting-308:00
*** vgridnev has quit IRC08:02
*** atuvenie has quit IRC08:04
*** hdaniel has joined #openstack-meeting-308:05
*** mbound has joined #openstack-meeting-308:07
*** salv-orlando has quit IRC08:10
*** mickeys has joined #openstack-meeting-308:11
*** mickeys has quit IRC08:25
*** mickeys has joined #openstack-meeting-308:26
*** salv-orlando has joined #openstack-meeting-308:26
*** toddjohn has joined #openstack-meeting-308:26
*** openstackstatus has joined #openstack-meeting-308:29
*** ChanServ sets mode: +v openstackstatus08:29
*** mickeys has quit IRC08:30
*** toddjohn has quit IRC08:31
*** mickeys has joined #openstack-meeting-308:31
-openstackstatus- NOTICE: jobs depending on npm are now working again08:33
*** e0ne has joined #openstack-meeting-308:50
*** salv-orl_ has joined #openstack-meeting-308:52
*** mickeys has quit IRC08:52
*** kenji-i has quit IRC08:53
*** mickeys has joined #openstack-meeting-308:54
*** mickeys has quit IRC08:54
*** mickeys has joined #openstack-meeting-308:54
*** mickeys has quit IRC08:54
*** salv-orlando has quit IRC08:55
*** alexpilotti has joined #openstack-meeting-309:02
*** rossella_s has quit IRC09:03
*** rossella_s has joined #openstack-meeting-309:03
*** sambetts|afk is now known as sambetts09:05
*** alexpilotti has quit IRC09:07
*** zhurong_ has quit IRC09:09
*** vgridnev has joined #openstack-meeting-309:17
*** qwebirc52297 has joined #openstack-meeting-309:21
*** hichihara has quit IRC09:23
*** kzaitsev_mb has joined #openstack-meeting-309:23
*** neiljerram has joined #openstack-meeting-309:26
*** lpetrut has joined #openstack-meeting-309:28
*** alex_xu has quit IRC09:32
*** hoangcx has joined #openstack-meeting-309:35
*** alex_xu has joined #openstack-meeting-309:36
*** hoangcx has left #openstack-meeting-309:36
*** JieLi has joined #openstack-meeting-309:38
*** yamamoto_ has quit IRC09:40
*** alexpilotti has joined #openstack-meeting-309:43
*** alexpilotti has quit IRC09:48
*** kzaitsev_mb has quit IRC09:52
*** JieLi has quit IRC09:53
*** kzaitsev_mb has joined #openstack-meeting-309:59
*** obondarev has quit IRC10:00
*** obondarev has joined #openstack-meeting-310:06
*** numan_ has quit IRC10:07
*** egallen has quit IRC10:07
*** qwebirc52297 has quit IRC10:08
*** baojg has quit IRC10:09
*** obondarev has quit IRC10:12
*** kzaitsev_mb has quit IRC10:12
*** alexpilotti has joined #openstack-meeting-310:14
*** kzaitsev_mb has joined #openstack-meeting-310:15
*** hoangcx has joined #openstack-meeting-310:16
*** mrmartin has quit IRC10:18
*** alexpilotti has quit IRC10:19
*** sdague has joined #openstack-meeting-310:20
*** numan_ has joined #openstack-meeting-310:21
*** alexpilotti has joined #openstack-meeting-310:21
*** numan_ has quit IRC10:22
*** numan_ has joined #openstack-meeting-310:22
*** toddjohn has joined #openstack-meeting-310:28
*** kmartin has quit IRC10:28
*** obondarev has joined #openstack-meeting-310:31
*** toddjohn has quit IRC10:32
*** yamamoto has joined #openstack-meeting-310:42
*** egallen has joined #openstack-meeting-310:45
*** andymaier has joined #openstack-meeting-310:53
*** alex_xu has quit IRC10:55
*** steve_ruan has quit IRC10:55
*** alex_xu has joined #openstack-meeting-310:57
*** jlanoux has quit IRC10:58
*** egallen has quit IRC11:00
*** jlanoux has joined #openstack-meeting-311:03
*** yamamoto has quit IRC11:04
*** jlanoux_ has joined #openstack-meeting-311:05
*** yamamoto has joined #openstack-meeting-311:06
*** jlanoux has quit IRC11:07
*** rtheis has joined #openstack-meeting-311:18
*** alexpilotti has quit IRC11:21
*** mbound has quit IRC11:24
*** tfukushima has quit IRC11:25
*** mbound has joined #openstack-meeting-311:29
*** vtech has quit IRC11:34
*** vtech has joined #openstack-meeting-311:35
*** vgridnev has quit IRC11:39
*** stanzgy has quit IRC11:40
*** alex_xu has quit IRC11:41
*** alex_xu has joined #openstack-meeting-311:43
*** dslevin1 has joined #openstack-meeting-311:44
*** dslevin1 has quit IRC11:44
*** ChanServ changes topic to "OpenStack Meetings ||"11:45
*** dslevin1 has joined #openstack-meeting-311:46
*** banix has joined #openstack-meeting-311:50
*** anilvenkata has quit IRC11:50
*** mrmartin has joined #openstack-meeting-311:51
*** mbound has quit IRC11:54
*** mbound has joined #openstack-meeting-311:54
*** mbound has quit IRC11:56
*** andymaier has quit IRC11:59
*** mbound has joined #openstack-meeting-312:01
*** vgridnev has joined #openstack-meeting-312:03
*** lpetrut has quit IRC12:07
*** jhesketh has quit IRC12:07
*** lpetrut has joined #openstack-meeting-312:07
*** jhesketh has joined #openstack-meeting-312:07
*** baoli has joined #openstack-meeting-312:13
*** baoli_ has joined #openstack-meeting-312:13
*** neelashah has joined #openstack-meeting-312:17
*** baoli has quit IRC12:18
*** alexpilotti has joined #openstack-meeting-312:21
*** neelashah has quit IRC12:22
*** alexpilotti has quit IRC12:24
*** alexpilotti has joined #openstack-meeting-312:25
*** doug-fish has joined #openstack-meeting-312:26
*** salv-orl_ has quit IRC12:28
*** toddjohn has joined #openstack-meeting-312:29
*** banix has quit IRC12:31
*** banix has joined #openstack-meeting-312:32
*** banix has quit IRC12:32
*** toddjohn has quit IRC12:34
*** kzaitsev_mb has quit IRC12:38
*** salv-orlando has joined #openstack-meeting-312:40
*** doug-fish has quit IRC12:42
*** egallen has joined #openstack-meeting-312:42
*** doug-fish has joined #openstack-meeting-312:42
*** doug-fish has quit IRC12:47
*** sigmavirus24_awa is now known as sigmavirus2412:47
*** toddjohn has joined #openstack-meeting-312:49
*** piet has joined #openstack-meeting-312:50
*** julim has joined #openstack-meeting-312:51
*** annegentle has joined #openstack-meeting-312:51
*** mrmartin has quit IRC12:53
*** doug-fish has joined #openstack-meeting-312:54
*** kzaitsev_mb has joined #openstack-meeting-312:55
*** doug-fis_ has joined #openstack-meeting-312:56
*** dedery has quit IRC12:57
*** Poornima has quit IRC12:57
*** Poornima has joined #openstack-meeting-312:58
*** mbound has quit IRC12:58
*** vikram has joined #openstack-meeting-312:59
*** toddjohn has quit IRC12:59
*** doug-fish has quit IRC12:59
*** mrmartin has joined #openstack-meeting-313:00
*** mbound has joined #openstack-meeting-313:00
*** crobertsrh has joined #openstack-meeting-313:02
*** rossella_s has quit IRC13:03
*** rossella_s has joined #openstack-meeting-313:03
*** Poornima has quit IRC13:04
*** vtech has quit IRC13:04
*** vtech has joined #openstack-meeting-313:05
*** lblanchard has joined #openstack-meeting-313:09
*** anilvenkata has joined #openstack-meeting-313:12
*** rmoe has quit IRC13:13
*** rmoe has joined #openstack-meeting-313:15
*** mrmartin has quit IRC13:19
*** itxaka is now known as itxaka|lunch13:22
*** mbound has quit IRC13:22
*** doug-fis_ has quit IRC13:23
*** mbound has joined #openstack-meeting-313:28
*** toddjohn has joined #openstack-meeting-313:31
*** banix has joined #openstack-meeting-313:34
*** annegentle has quit IRC13:38
*** yamamoto has quit IRC13:40
*** sc68cal has joined #openstack-meeting-313:42
*** rbak has quit IRC13:42
*** irenab has quit IRC13:44
*** mrmartin has joined #openstack-meeting-313:48
*** piet has quit IRC13:49
*** mbound has quit IRC13:51
*** mbound_ has joined #openstack-meeting-313:51
*** mrmartin has quit IRC13:52
*** tonytan4ever has joined #openstack-meeting-313:53
*** ddieterly has joined #openstack-meeting-313:54
*** mrmartin has joined #openstack-meeting-313:55
*** jpomeroy has joined #openstack-meeting-313:55
*** pino|work has joined #openstack-meeting-313:55
*** piet has joined #openstack-meeting-313:56
*** ddieterly is now known as ddieterly[away]13:56
*** kzaitsev_mb has quit IRC13:56
*** yamamoto has joined #openstack-meeting-313:57
*** mionkin has joined #openstack-meeting-313:59
*** tosky has joined #openstack-meeting-314:00
elmiko#startmeeting sahara14:00
openstackMeeting started Thu Apr  7 14:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at
*** Poornima has joined #openstack-meeting-314:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** alexpilotti has quit IRC14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
elmiko#chair vgridnev14:00
openstackCurrent chairs: elmiko vgridnev14:00
elmiko#chair SergeyLukjanov14:00
openstackCurrent chairs: SergeyLukjanov elmiko vgridnev14:00
elmikohi =)14:00
vgridnevhey folks14:01
*** Poornima has joined #openstack-meeting-314:01
elmiko#topic News / updates14:01
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:01
*** yamahata has joined #openstack-meeting-314:01
PoornimaHello everyone14:01
vgridnevit's announced that Mitaka was released!14:02
*** alexpilotti has joined #openstack-meeting-314:02
*** lblanchard has quit IRC14:02
vgridnevalso, FYI:14:02
*** esikachev has joined #openstack-meeting-314:03
elmikovgridnev: that's nice to see14:03
vgridnevthis additional tags for sahara in governance ^^14:03
toskyso, rejoice!14:03
*** yamamoto has quit IRC14:03
elmikoi've mainly been working on my presentation for openstack summit, and some internal stuff14:04
*** rpjr_ has joined #openstack-meeting-314:05
elmikoalthough, i am happy to see that the service.api refactor spec got merged =)14:05
*** NikitaKonovalov_ has joined #openstack-meeting-314:05
*** cloudtrainme has joined #openstack-meeting-314:05
esikachevi am working on prepearing sahara-tests for release, added filters for jobs on sahara-ci14:05
*** lblanchard has joined #openstack-meeting-314:05
pgadiyaI am testing my changes which I have made w.r.t API v2 development on my local environment. Once tested will send the patch for review14:06
toskyworking on moving tempest API tests, almost ready (and thanks again to SergeyLukjanov, vgridnev and esikachev for the time spent and the support)14:06
PoornimaI am going through sahara service api now14:06
crobertsrhI've had a couple of fixes for a couple of ugly UI issues....14:06
*** sdake has joined #openstack-meeting-314:07
crobertsrhOne patch seems to break the integration tests, but I'm not sure why.  Any tips would be great since I'm currently unable to run the integration tests locally.
vgridnevcrobertsrh, ok, I will try soon14:08
NikitaKonovalov_o/ I'm mostly busy with intrnal stuff, but promiss elmiko to start working on slides14:08
vgridnevit's important fix for us, I think14:08
elmikoNikitaKonovalov_: awesome =)14:08
vgridnevanything else new?14:09
vgridnev#topic API v2 progress14:10
*** openstack changes topic to "API v2 progress (Meeting topic: sahara)"14:10
vgridnevelmiko, how is it going?14:10
elmikojust waiting for some reviews on14:10
*** neelashah has joined #openstack-meeting-314:10
elmikothen i'm hoping to add more patches on top14:10
elmikoi'm happy to hear that pgadiya and Poornima are getting up to speed as well =)14:11
vgridnevi've approved today spec about service.api, so going to take look on patch above14:11
*** rbak has joined #openstack-meeting-314:11
elmikoyea, thanks vgridnev14:11
vgridnevok, cool14:11
elmikootherwise, not much to report14:11
vgridnevok, next then14:11
vgridnev#topic Scenario tests releases (tosky, esikachev)14:11
*** openstack changes topic to "Scenario tests releases (tosky, esikachev) (Meeting topic: sahara)"14:11
*** sdake has quit IRC14:12
*** nkrinner has quit IRC14:12
vgridnevfolks, what do we need additional in the first release of sahara-tests?14:12
esikachevfor release, i think, we need this patches#link #link
toskyas anticipated before, I'm testing the tempest tests converted as tempest plugin inside sahara-tests - I'd like to have it as well, coming before end of today14:12
*** tmckay has joined #openstack-meeting-314:13
* tmckay is here but distracted by another meeting where he has to talk ...14:13
toskyagree with both reviews esikachev  pointed out; I reviewed one, and I was collecting details about reno14:13
vgridnevI think that we need to make release till end of the next week, I think. Or if it will be possible to in the begging of the next week.14:13
toskyI think that the reno one should have few other details14:14
esikachevvgridnev: +1 for begging of the next week14:14
esikachevtosky: ok14:14
vgridnevops, beginning, I think14:14
toskybeginning is better than begging :)14:14
vgridnevI will take another look on reno stuff then14:15
vgridnevok, anything else?14:15
*** NikitaKonovalov_ has quit IRC14:15
esikachevthats all from me14:15
toskynot from my side14:15
vgridnev#topic Newton summit topics and schedule preparing (vgridnev, NikitaKonovalov)14:16
*** openstack changes topic to "Newton summit topics and schedule preparing (vgridnev, NikitaKonovalov) (Meeting topic: sahara)"14:16
*** NikitaKonovalov_ has joined #openstack-meeting-314:16
vgridnevok, first. Sad news: I'm not going to summit this time, btw I have crazy ideas to join via Hangouts or something like that14:16
*** alexpilotti has quit IRC14:17
elmikosad that you won't be there, but having the hangout will be good =)14:17
vgridnevNikitaKonovalov will be my representative at the summit14:17
crobertsrhIf the conference network permits :)14:17
elmikogood point14:17
Poornimavgridnev, elmiko me too14:17
*** toddjohn has quit IRC14:17
Poornimaon hangout14:18
elmikohopefully the laptops won't outnumber us ;)14:18
vgridnevoh, forgot link14:18
vgridnev#link #link
crobertsrhSounds like one or more of us should try to get some sort of meeting solution set up and communicate it to others during summit14:18
elmikocrobertsrh: do you mean like online meeting solution?14:19
crobertsrhOf course, time zone might also impact people's chance to attend "remotely"14:19
*** julim has quit IRC14:19
crobertsrhI think Austin is UTC-6, right?14:20
elmikothat sounds about right14:20
vgridnevabout schedule: most of meeting are going to be started at the morning, so I for sure will have abilities to join14:20
*** sdake has joined #openstack-meeting-314:21
crobertsrhThat is good14:21
vgridnevwe have draft schedule already in etherpad, I think that we should spend next meeting to finalise schedule14:22
elmikovgridnev: +114:22
crobertsrhI will be out next week14:22
crobertsrhI think elmiko and tmckay will be as well14:22
*** julim has joined #openstack-meeting-314:22
tmckayoh, next meeting? Yeah.14:22
elmikoyea, gonna miss next weeks meeting. oops14:22
elmikobut, i can certainly follow along if we propose something via email14:23
crobertsrhWe can always discuss in the regular channel if there's anything we can't address today14:23
vgridnev+1, then I think that I will start finalising schedule together with Nikita14:23
vgridnevI guess that we will need chairs for sessions, right?14:24
elmikojust propose it to the ML once you and NikitaKonovalov_ have a plan14:24
crobertsrhAt a first look, I don't see anything controversial on the schedule pad at the moment14:24
elmikoi will volunteer to run the apiv2 and security sessions, as is tradition ;)14:24
crobertsrhI'll run the UI session, per tradition14:24
*** egafford has joined #openstack-meeting-314:24
elmiko(assuming we use them)14:24
vgridnevSo, if you want to lead a session, please post this data to ether pad, so that we will have ability to understand that14:25
tmckayI will heckle crobertsrh in the UI session, so that's covered14:25
crobertsrhwhew, thanks tmckay14:25
elmikoi will heckle tmckay heckling crobertsrh XD14:25
tmckayHA :)14:25
crobertsrhYou get him good elmiko, he deserves it14:26
egaffordI will break the cycle of violence by not heckling elmiko14:26
elmikogotta preserve the chain of responsibility14:26
*** baoli_ has quit IRC14:26
tmckayegafford, you will be mocked for that. Mocking is different than heckling14:26
vgridnev#action vgridnev, NikitaKonovalov to prepare draft schedule at post results in ML14:26
vgridnevok, anything else that we should cover in there?14:28
*** rhochmuth has joined #openstack-meeting-314:28
vgridnevBTW, please continue collecting ideas14:28
vgridnevMore ideas is better always14:28
Poornimaelmiko, If we write a patch do we need to share it on same branch14:29
*** yamamoto has joined #openstack-meeting-314:29
vgridnev#topic Revisiting Sahara Blueprints14:29
*** openstack changes topic to "Revisiting Sahara Blueprints (Meeting topic: sahara)"14:29
Poornima is already merged to git14:29
vgridnevso, we have few blueprints to discuss14:30
Poornimaor we need file a bug and create branch across that bug ?14:30
elmikoPoornima: if you use the "Partial-Implements: bp v2-api-experimental-imp" in your commit message, it will be put on the appropriate topic14:30
*** baoli has joined #openstack-meeting-314:30
*** zz_dimtruck is now known as dimtruck14:30
elmikoPoornima: no need to file a bug14:30
*** matrohon has quit IRC14:31
vgridnevthere are few blueprints that we should mark to implemented state, I guess14:31
elmikojust make sure to use the "Partial-Implements" tag in your commit message14:31
*** matrohon has joined #openstack-meeting-314:31
Poornimagot you :)14:31
vgridnevis it true that this one is implemented ^^14:31
elmikoi /think/ it's fully implemented14:32
vgridnevok, then14:32
egafford+1; I believe that you and I finished that off vgridnev.14:32
egafford(Re: trusts, not scalability.)14:32
*** huichun has joined #openstack-meeting-314:33
vgridnevegafford, got it14:33
egaffordScalability bp seems done as of Kilo (by default settings,) yes?14:34
elmikoyea, seems like it14:34
vgridnevfor me too, ok14:34
vgridnevand this one, finally:
*** toddjohn has joined #openstack-meeting-314:35
vgridnevdo we want to extend fake plugin in some way?14:35
elmikonot sure if we achieved all those goals, but i thought fake plugin was in14:35
crobertsrhIt's mostly done, isn't it?14:35
crobertsrhI can't think of ways that it's not done14:35
vgridnevok, then it's implemented. I guess that it was done for heat / direct engine testing, and it good enough in our gates14:37
elmikosounds good14:37
vgridnevand finally, there are two blueprints, which are looks strange for me:14:38
toskyit was done for upstream gates, so they don't require a full image build14:38
elmikothat suspend/resume sounds complicated14:38
vgridnevwe have spec approved there, but with out actual details of implementation14:39
elmikoimo, we should drop the vagrant one in favor of a playbook for kolla14:39
elmiko(which would by definition include an ansible route for deploying sahara)14:39
egaffordelmiko: +1; personally I love vagrant, but reuse of OpenStack ecosystem tools will only improve all our lives in the long run.14:40
crobertsrh+1 for ansible/kolla14:40
pino|workegafford: ... when they make sense14:40
egaffordpino|work: Valid, but kolla's kinda great, though young.14:40
elmikoit's a nice idea, and i don't have an active objection to it. but if we are talking about designating resources, my preference is for kolla.14:40
pino|workegafford: it was a general note, not directed to kolla14:41
elmikoregardless of the kolla integration, having an ansible playbook for sahara would be awesome14:41
pino|work(it actually was targeted to something else, but that's mildly ot)14:41
*** lblanchard has quit IRC14:41
*** ddieterly has joined #openstack-meeting-314:42
*** banix has quit IRC14:42
egaffordI don't see the drafter in the meeting at the moment.14:42
vgridnevok, it looks like we agreed about invalidating vagrant spec14:43
elmikoyea, haven't see him in awhile14:43
egaffordYeah, it's been dead since Sept. 2014.14:43
vgridnevabout suspend stuff, I think that we should remove spec, and keep that as idea14:43
elmikoi'm ok with that, we probably need to rewrite the spec anyway14:44
crobertsrhYeah, fine idea, just not likely to happen anytime "soon"14:44
*** sverma has joined #openstack-meeting-314:44
vgridnevok, thanks folks14:44
vgridnevlet's move on then14:44
vgridnev#topic Open discussion14:45
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:45
vgridnevanything additional that we should to discuss?14:45
*** Poornima has quit IRC14:45
elmikonothing from me14:46
crobertsrhNothing from me14:46
vgridnevI'm going to prepare fixes to put in stable/mitaka shortly, just FYI.14:46
*** rhochmuth has left #openstack-meeting-314:46
vgridnevsince stable/mitaka is now opened for post-release things14:46
*** numan_ has quit IRC14:47
*** Poornima has joined #openstack-meeting-314:47
crobertsrhYes, I think the 2 cosmetic, but ugly UI fixes should be backported14:48
vgridnevcrobertsrh, +114:48
vgridnevanything else?14:48
huichunvgridnev:  suspend and resume will move to N?14:49
vgridnevhuichun, for jobs?14:49
vgridnevyes, N is now opened, let's make that happen14:49
*** esikachev has quit IRC14:49
toskya long 114:50
vgridnevthanks, folks!14:50
elmikothanks all14:50
*** openstack changes topic to "OpenStack Meetings ||"14:50
openstackMeeting ended Thu Apr  7 14:50:51 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:50
openstackMinutes (text):
*** crobertsrh has left #openstack-meeting-314:50
*** tosky has left #openstack-meeting-314:51
*** mionkin has quit IRC14:51
*** salv-orl_ has joined #openstack-meeting-314:52
*** kzaitsev_mb has joined #openstack-meeting-314:52
*** salv-orl_ has quit IRC14:53
*** sverma has quit IRC14:53
*** esikachev has joined #openstack-meeting-314:54
*** salv-orlando has quit IRC14:54
*** pgadiya has quit IRC14:54
*** mickeys has joined #openstack-meeting-314:55
*** sigmavirus24 is now known as sigmavirus24_awa14:55
*** tidwellr1 has joined #openstack-meeting-314:55
*** pino|work has left #openstack-meeting-314:55
*** anilvenkata has quit IRC14:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
*** Poornima has quit IRC14:56
*** NikitaKonovalov_ has quit IRC14:56
*** mlavalle has joined #openstack-meeting-314:56
*** NikitaKonovalov_ has joined #openstack-meeting-314:57
*** kzaitsev_mb has quit IRC14:58
*** janzian has joined #openstack-meeting-314:59
*** steve_ruan has joined #openstack-meeting-315:00
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Apr  7 15:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** gouthamr has joined #openstack-meeting-315:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
*** gouthamr has left #openstack-meeting-315:00
*** woodster_ has joined #openstack-meeting-315:00
mlavalle#chair carl_baldwin15:00
openstackCurrent chairs: carl_baldwin mlavalle15:00
mlavalle#chair tidwellr115:00
openstackCurrent chairs: carl_baldwin mlavalle tidwellr115:00
*** NikitaKonovalov_ has quit IRC15:01
mlavallethat way we are fault tolerant ;-)15:01
*** iyamahat has joined #openstack-meeting-315:01
mlavalle#topic Announcements15:01
*** NikitaKonovalov_ has joined #openstack-meeting-315:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** egafford has left #openstack-meeting-315:02
mlavalleSummit is just 3 weeks ago. Looking forward to see you all personally in Austin15:02
mlavallejust 3 weeks away^^^^15:02
*** johnbelamaric has joined #openstack-meeting-315:02
mlavalleany other annoucements from the team?15:03
mlavalleok, if not15:03
mlavalle#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
mlavalleThis week we added a few high priority bugs15:04
mlavallefirst up is
openstackLaunchpad bug 1563883 in neutron "test_net_ip_availability_after_subnet_and_ports failed in _assert_total_and_used_ips" [High,Fix released] - Assigned to Armando Migliaccio (armando-migliaccio)15:04
mlavalleit seems armax proposed solution and it merged15:05
mlavallenext up is
openstackLaunchpad bug 1543094 in neutron "[Pluggable IPAM] DB exceeded retry limit (RetryRequest) on create_router call" [High,In progress] - Assigned to Ryan Tidwell (ryan-tidwell)15:06
tidwellr1good progress this week15:06
mlavalleyeah, I saw that :-)15:07
*** ajmiller has joined #openstack-meeting-315:07
tidwellr1still polishing a fix, but I've made it through the unit tests15:07
carl_baldwintidwellr1: Is your fix linked to the bug?15:08
tidwellr1yes, it is15:08
*** Na__ has joined #openstack-meeting-315:08
tidwellr1sequential allocation of IP's has certainly been the expectation, we're proposing changing that15:08
tidwellr1I wonder how well it will be receieved....15:08
*** Na__ has quit IRC15:08
* carl_baldwin must have missed it.15:08
carl_baldwinOh mlavalle linked it.  Thanks mlavalle15:08
pavel_bondartidwellr1, thanks for working on that!15:09
*** Na_Zhu has joined #openstack-meeting-315:09
mlavalleany other comments about this one?15:09
tidwellr1nope, still WIP15:09
carl_baldwinI'm going to propose a change to IPAM to allow drivers to consider more than one subnet at a time.  That should help the performance of this change.15:09
*** fitoduarte has quit IRC15:10
*** stanzgy has joined #openstack-meeting-315:10
mlavalleall right moving on...15:10
mlavallenext one is being worked by pavel_bondar I believe:
openstackLaunchpad bug 1564335 in neutron " [Pluggable IPAM] delete subnet in ml2 plugin does not comply with pluggable ipam (deletes ip allocations directly from db)" [High,In progress] - Assigned to Pavel Bondar (pasha117)15:11
pavel_bondarpart of issue is addressed with  the first patch #link
*** tmckay has quit IRC15:12
carl_baldwinI'll have another look.15:12
pavel_bondarbut it does not cover ipam driver awareness of  SLAAC deallocations, which is expected to be fixed in separate patch.15:12
carl_baldwinI also need to catch up with the discussion on the bug report.15:13
mlavalleany other comments?15:14
mlavalleok, moving on15:15
mlavallenext up is
openstackLaunchpad bug 1566291 in neutron "L3 agent: at some point an agent becomes unable to handle new routers" [High,In progress] - Assigned to Oleg Bondarev (obondarev)15:15
mlavalleobondarev has proposed a fix and carl_baldwin and haleyb have commented on it15:16
mlavalleanything to discuss in this meeting?15:16
carl_baldwinLooks like it might just be ready for a +215:16
haleybyes, think mine was just a nit15:16
obondarevhi, I'm about to address a comment from haleyb15:17
obondarevjust a few sec15:17
carl_baldwinobondarev: Ping when it is up.15:17
obondarevcarl_baldwin: yep, thanks15:17
mlavalleobondarev thanks!15:18
mlavallemoving on15:18
mlavalleLast one up today is
openstackLaunchpad bug 1566383 in neutron "The creation fip does not endure restarting of l3-agent" [High,In progress] - Assigned to QingchuanHao (haoqingchuan-28)15:18
carl_baldwinI haven't looked at this one.  Will look.15:19
*** baoli has quit IRC15:19
mlavalleany other bugs from the team I may have missed?15:20
mlavalleok, moving on15:21
mlavalle#topic Routed Networks15:21
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:21
carl_baldwinI think we've made some progress on this one.15:22
carl_baldwinI updated the patch to associate segments and subnets.  Now have to go rework the extension and start on the IPAM changes.15:23
carl_baldwinWe've got some new owners for certain pieces like the DHCP work and the l2adjacency flag.15:23
carl_baldwinThat's all from me.  I think we're making very good progress overall.15:24
mlavalle#topic BGP dynamic routing15:24
*** openstack changes topic to "BGP dynamic routing (Meeting topic: neutron_l3)"15:24
*** neelashah has quit IRC15:25
*** ddieterly is now known as ddieterly[away]15:25
*** alex_xu has quit IRC15:25
tidwellr1not much to report this week15:25
tidwellr1at least from me...15:25
vikramworking on the repo creation patch15:25
vikramneeds review help ""15:26
Na_ZhuI think the new repo creation patch need more review15:26
*** yamahata has quit IRC15:26
*** kmartin has joined #openstack-meeting-315:27
mlavalleanything else on this topic?15:27
vikramcarl_baldwin: need your blessings15:27
Na_Zhu@Carl, can you take some time to review it? Really need your help.15:27
carl_baldwinI will15:27
*** cloudtrainme has quit IRC15:28
Na_Zhu@Carl, thanks15:28
vikramcarl_baldwin: thanks15:28
carl_baldwinvikram: Na_Zhu: have you addressed feedback from Andreas?15:28
*** Swami has joined #openstack-meeting-315:28
*** alex_xu has joined #openstack-meeting-315:29
Na_Zhucarl_baldwin: Vikram has addressed it15:29
vikramcarl_baldwin: yes15:29
*** stanzgy has quit IRC15:29
carl_baldwinI don't see a reply.  Could you add a reply?15:29
vikramok, i wil15:30
vikramcarl_baldwin: Ohh I didn't noticed the latest comment15:30
vikramcarl_baldwin: Will address15:30
*** armax has joined #openstack-meeting-315:30
carl_baldwinvikram: thanks15:31
*** cloudtrainme has joined #openstack-meeting-315:31
Na_Zhuvikram: that is comment from me15:31
mlavalleok, I think we can move on now...15:32
vikramNa_Zhu: Ok will address your's as well15:32
vikrammlavalle: that's it15:32
mlavalle#topic Open discussion15:32
*** openstack changes topic to "Open discussion (Meeting topic: neutron_l3)"15:32
Na_Zhuvikram: thanks, you really do a nice job about the repo creation15:33
mlavalleany topics that need to be raised to this team?15:33
*** Na_Zhu has quit IRC15:34
mlavalleok, I think this was a quick one. We will return 25 minutes to everybody's agenda15:34
steve_ruanmlavalle: there is bug need to be reviewed15:34
steve_ruanit's ready for sometime15:34
steve_ruan this patch is the spec of bug
openstackLaunchpad bug 1525059 in neutron "[RFE] Add support for external vxlan encapsulation to neutron router" [Wishlist,In progress] - Assigned to steve (ruansx)15:35
*** sc68cal has quit IRC15:36
*** iyamahat has quit IRC15:36
mlavallesteve_ruan: thanks for bringing this up. I encourage the team to review it.15:36
*** mtanino has joined #openstack-meeting-315:37
vikramcarl_baldwin: Addressed AJaeger comment ;)15:37
mlavalleany other topics?15:37
*** ddieterly[away] is now known as ddieterly15:37
*** galstrom_zzz is now known as galstrom15:37
yamamotoi want to ask opinion about this
openstackLaunchpad bug 1556884 in neutron "floating-ip association is allowed via router interface" [Medium,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)15:38
yamamoto(same as the last week)15:38
*** nelsnelson has joined #openstack-meeting-315:38
yamamotoand there's a related rfe
openstackLaunchpad bug 1566191 in neutron "Allow multiple networks with FIP range to be associated with Tenant router" [Medium,Confirmed]15:39
*** nelsnels_ has quit IRC15:39
mlavalleyamamoto: thanks15:40
mlavalleany other topics?15:40
yamamotoIMO the regression in validation should be fixed first.  and then we can consider the rfe. opinions?15:40
mlavalleyamamoto: looks reasonable to me15:42
pavel_bondarone more fix for reviewers to take a look: it fixes
openstackLaunchpad bug 1534625 in neutron "[Pluggable IPAM] Ipam driver is not called on update subnet if allocation pools are blank" [Medium,In progress] - Assigned to Pavel Bondar (pasha117)15:42
mlavallepavel_bondar: thanks15:43
*** spzala has joined #openstack-meeting-315:43
*** ddieterly is now known as ddieterly[away]15:44
mlavalleok, thanks for attending this week15:44
mlavallesee you in channel and gerrit :-)15:44
*** openstack changes topic to "OpenStack Meetings ||"15:44
openstackMeeting ended Thu Apr  7 15:44:38 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:44
openstackMinutes (text):
*** steve_ruan has quit IRC15:45
*** mickeys has quit IRC15:46
*** kzaitsev_mb has joined #openstack-meeting-315:46
*** ddieterly[away] is now known as ddieterly15:46
*** scheuran has quit IRC15:47
*** itxaka|lunch has quit IRC15:48
*** baoli has joined #openstack-meeting-315:49
*** matrohon has quit IRC15:49
*** janzian has left #openstack-meeting-315:50
*** mlavalle has left #openstack-meeting-315:51
*** pcaruana has quit IRC15:53
*** cdent has joined #openstack-meeting-315:54
*** numan_ has joined #openstack-meeting-315:54
*** mrmartin has quit IRC15:55
cdent#startmeeting api-wg16:00
openstackMeeting started Thu Apr  7 16:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at
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
* elmiko does 3 amigos salute16:01
cdentanybody else joining in for api-wg meeting?16:01
cdent#topic previous meeting action items16:01
*** openstack changes topic to "previous meeting action items (Meeting topic: api-wg)"16:01
cdentI reckon those are done. I made and started
*** mtanino has quit IRC16:02
*** armax has quit IRC16:02
*** armax has joined #openstack-meeting-316:02
cdentand etoews even made a bug: (gaining him ten points!)16:02
openstackLaunchpad bug 1562058 in openstack-api-wg "Links guideline" [Undecided,New]16:02
*** mtanino has joined #openstack-meeting-316:03
* etoews loves internet points16:03
cdentyou can do so much with them16:03
cdentokay, on to new biz16:03
cdent#topic etags and the lost update problem16:03
*** openstack changes topic to "etags and the lost update problem (Meeting topic: api-wg)"16:03
*** alexpilotti has joined #openstack-meeting-316:03
cdentIf you haven't already seen it, that guideline has gone quite long16:03
cdentand I have some questions/concerns about it16:04
*** mbound_ has quit IRC16:04
elmikoi thought the baldly thing was a joke at first XD16:04
cdentThough long it leaves out a lot of detail16:04
cdentbaldly as in: overly straightforward, without even being shy about it16:04
elmikoagreed about the length, but it seems like a great intro to someone who doesn't intimately understand etags16:05
cdentI had friend (from a similar we-love-http background) gaze over it and his first reaction was akin to "this is way dumbed down"16:05
*** julim has quit IRC16:05
cdent"why don't you talk about state more?"16:06
elmikobut as a guideline, how far do we drill down before recommending outside sources (which you did)16:06
cdent"shouldn't the term 'conflict' show up more often?"16:06
elmikoah, fair16:06
cdentyeah, exactly16:06
* etoews reading16:06
*** yamamoto has quit IRC16:06
*** marios_ has joined #openstack-meeting-316:06
*** toddjohn has quit IRC16:07
elmikoand, imo, the state talk starts to get into impl side of things16:07
*** tidwellr1 has left #openstack-meeting-316:07
*** vtech has quit IRC16:07
*** toddjohn has joined #openstack-meeting-316:07
cdentOn the flip side the prose pretty much just flowed out of me, so we can probably get me to write more like these if we think this form of document is a good idea (that is, the patented elmiko-driven notino of problem->solution->details)16:08
*** annegent_ has joined #openstack-meeting-316:08
*** vtech has joined #openstack-meeting-316:08
*** yamahata has joined #openstack-meeting-316:08
*** e0ne has quit IRC16:08
*** marios has quit IRC16:08
elmikoi'm glad to hear it flowed so well, i certainly thought it read well. i'm curious to hear if we have missed anything big with this style.16:08
*** e0ne has joined #openstack-meeting-316:09
cdentDo any existing openstack services already use etags? I think we decided "no".16:10
*** vtech has quit IRC16:10
cdentdoes swift count? :)16:10
*** marios_ is now known as marios16:10
elmikoyour words, not mine XD16:10
dstanekcdent: i just did a quick read and it looks like a good intro16:11
elmikobut, aside from that, i think no16:11
cdentthanks dstanek16:11
elmikodstanek: that's encouraging to hear16:11
*** toddjohn has quit IRC16:12
cdentetoews: still reading?16:12
* etoews making 1 comment16:12
cdentAre there additional "new topics" we should be talking about (stuff that won't be covered by guidelines and apiimpact further down the agenda)?16:15
etoewselmiko: are we going to prepare anything for the summit session?16:16
elmikodo we need to discuss the summit session any further?16:16
elmikoi have a couple proposals to bring to the group around PR for the guidelines, but i'd need at most like 15 minutes to present16:16
etoewsgo for it16:16
dstanekis there an etherpad for summit session content?16:17
elmikoi think we need to clean it up a little though16:17
*** rosmaita has joined #openstack-meeting-316:18
cdentetoews: you wanna talk about your comment on etags here or should we save it for the review?16:18
etoewselmiko: after you present we just forge out way through the session agenda?16:18
*** egallen has quit IRC16:18
dstanekelmiko: perfect, thanks16:18
*** egallen_ has joined #openstack-meeting-316:18
etoewscdent: save it for the review. i'm going to have to bounce at any minute.16:18
cdentI've got one more quick "new topic" that I forgot to put on the agenda16:19
cdent#topic tc candidates love api-wg16:19
*** openstack changes topic to "tc candidates love api-wg (Meeting topic: api-wg)"16:19
cdentI didn't make a close count but a lot of the candidates for TC mentioned the api-wg and how it is going to take a big role in the future16:19
*** jlanoux_ has quit IRC16:19
elmikoetoews: i'm making a few comments on the pad, but i see; state of the wg, upcoming activites, and promiting the guidelines16:19
cdentthat's either a cross to bear or an opportunity, but either way I guess we need to be aware of it16:20
etoewshah. agreed.16:20
elmikoalso, not directly api-wg related, but since we share a channel i absolutely love the work that is happening with the openstacksdk. big props to those folks16:20
etoewsi gotta run.16:20
etoewssee you later in irc16:20
*** egallen_ has quit IRC16:20
* cdent waves to etoews 16:20
*** vgridnev has quit IRC16:21
*** vgridnev has joined #openstack-meeting-316:21
*** mrmartin has joined #openstack-meeting-316:21
cdentYeah, I think one of the side effects of the big tent is that things that might have once have been thought of as on the edges are now become more central16:21
cdentbecause they links stuff up16:21
cdentBut yeah, just wanted to air that observation.16:22
cdentShall we move on?16:22
elmikowas sdk seen as on the edges before?16:22
elmikoor was that a comment about api-wg16:23
cdentWell one way to put it would be "it's not nova"16:23
*** ddieterly is now known as ddieterly[away]16:23
cdentand somewhat more politick: it's not a service16:23
elmikoso, this is like galileo declaring that openstack does not revolve around nova?16:23
cdentand the services tend to accumulate the gravity16:23
cdentsomething like that16:23
elmikoyea, definitely cool to see more projects growing16:24
cdentor maybe gravity trumps planets16:24
cdent#topic guidelines16:25
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"16:25
elmikohmm, when are we merging all those frozen ones?16:25
cdentprobably now16:25
elmikowe should merge this
elmikonot a guideline, so i went for the +216:26
elmikook, so aside from the redundancy one, you should merge the microversions and unexpected attr one (cdent)16:27
elmikowe did announce those on list right?16:28
cdentthe guidelines were clarified such that we only go to list when we have contention16:29
*** bpokorny has joined #openstack-meeting-316:29
elmikoah, ok. i thought we still announce when they freeze (which i think you did with those)16:29
cdentbecause the intro to the guidelines suggested we were supposed to be prioritizing velocity and forgiveness16:29
*** toddjohn has joined #openstack-meeting-316:30
cdentyeah, I still like the idea of emailing frequently16:30
cdentand usually do anyway16:30
cdentI've +w those 416:30
elmikoright, ok16:30
elmikosweet, cdent++16:30
cdentso we can send an announcement for them16:30
cdentshall I, or you wanna?16:30
*** neiljerram has quit IRC16:31
elmikoi thought we only email when we freeze, not merge?16:31
*** egallen has joined #openstack-meeting-316:31
cdentwhen I was teasing apart the guidelines (which were way confusing)16:31
cdentwhere it ended up was:16:31
cdent"An email should be sent to the openstack-dev mailing list containing the links to all of the guidelines that have recently merged. The finalized guidelines should be buffered such that a maximum of one announcement email is sent per week."16:31
cdentwhich is unchanged from the original16:32
elmikoahh, ok16:32
elmikowe may have been lax on that, but yes i will send an email16:32
cdentmind you, I agree with you that that's a bit weird16:32
cdentI would rather have this order:16:32
cdentwe review16:32
cdentcpls review16:32
cdentopened for wide review by email announcment16:32
elmikoi /think/ that is what we have been doing16:33
cdenthowever I think the concern was that this would be slow and invite input from crazies16:33
*** alexpilotti has quit IRC16:33
elmikomaybe we should just ammend the guidelines to remove the post-merge email16:34
elmikounless we decide to move to some sort of "api-wg status" type thing16:34
*** egallen has quit IRC16:35
cdentperhaps at summit you can talk with the people there about the feelings towards email and the risk of crazies16:35
cdentI think the guidelines were created by etoews and cyeoh16:35
elmikoi don't think it's been an issue though, we have always sent out an [all] email on the frozen guidelines16:36
cdentI think I've made my position pretty clear above? "more input from everybody, yay!"16:36
elmikoyea, and i don't see a deviation from our current proceedure16:36
cdent#action at summit elmiko will engage the people(tm) to see about how and when email16:36
*** david-lyle has quit IRC16:36
*** mfranc213 has joined #openstack-meeting-316:36
elmikoi'll add an agenda item to discuss the guideline process again16:36
cdentsome of the older guidelines seem a bit stalled16:37
elmikoi've been meaning to get back to the actions guideline, but i feel it's a massive can of worms16:38
elmikoand in need to send an email to help distill the thoughts16:38
*** spzala has quit IRC16:38
cdentyeah, it's difficult16:38
*** spzala has joined #openstack-meeting-316:39
*** toddjohn has quit IRC16:39
elmikomaybe we should codify something about stale guidelines?16:39
*** egallen has joined #openstack-meeting-316:39
elmiko(i'll add it as a topic for summit)16:39
cdentI'm hesitant to become too overloaded with process16:39
elmikogood point16:40
*** toddjohn has joined #openstack-meeting-316:40
elmikoi'll add something about creating a process to limit the process..... ;P16:40
*** egallen has quit IRC16:40
elmikomaybe just something to be aware of then (stale guidelines)16:40
*** neiljerram has joined #openstack-meeting-316:40
*** dslevin1 has quit IRC16:41
cdentreview handling/velocity in general is a bit of a chore, especially things with apiimpact (which I almost never look at :( )16:41
elmikoyea, that is very difficult16:41
*** egallen has joined #openstack-meeting-316:41
*** egallen has quit IRC16:41
elmikoi've tried to review the PRs that i've been pulled into. but it's tough to get them all16:42
elmikoi think we need to lean more on having good CPLs16:42
elmikopeople who can help determine when a project needs more outside assistance for api stuffs16:42
cdentother than dstanek there's nobody here16:42
cdentwe probably need to send reminder emails16:42
*** e0ne has quit IRC16:42
elmikoand don't get me started about the 0000UTC meeting...16:42
elmikoimo, we need to go back to weekly meetings16:43
cdentanother summit topic?16:43
elmikobiweekly just kills the cadence16:43
cdentI can do whenever16:43
elmikoyea, i'll ad it16:43
*** egallen has joined #openstack-meeting-316:43
cdentquiet revolution16:43
*** spzala has quit IRC16:43
*** toddjohn has quit IRC16:44
elmikoi mean, in the beginning i had a few nice private chats with cyeoh in 0000 slot16:44
*** johnbelamaric has left #openstack-meeting-316:44
elmikobut now it's just empty16:44
* cdent raises a glass16:45
* elmiko raises a glass16:45
*** spzala has joined #openstack-meeting-316:45
dstanekcdent: :-)16:45
*** egallen has quit IRC16:45
elmikoadded a topic for summit about CPL participation as well16:45
*** ddieterly[away] is now known as ddieterly16:46
cdentdstanek: did you have anything you wanted to bring up or did you show up because that's what you do?16:46
*** galstrom is now known as galstrom_zzz16:46
*** egallen has joined #openstack-meeting-316:47
*** spzala has quit IRC16:47
cdentwhat about you elmiko?16:48
*** spzala has joined #openstack-meeting-316:48
elmikoi've said my peace16:48
cdentIf not I think we can call it, we've sort of steamed out16:48
cdentOne final piece of noise: let's use email more16:48
cdentthank elmiko, etoews and dstanek.16:49
*** annegent_ has quit IRC16:49
elmikoagreed, i'll send something about the merged guidelines16:49
dstanekcdent: no not from me16:49
*** annegentle has joined #openstack-meeting-316:49
cdentNext week is the late night non-meeting and afer that do we want a meeting in the run up to summit?16:49
dstaneklooks like i have a bit of work to do to catchup before the summit :-)16:50
elmikoprobably a good idea16:50
*** openstack changes topic to "OpenStack Meetings ||"16:50
openstackMeeting ended Thu Apr  7 16:50:51 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:50
elmikothanks cdent16:50
openstackMinutes (text):
*** alexpilotti has joined #openstack-meeting-316:51
*** dabukalam has joined #openstack-meeting-316:51
*** mickeys has joined #openstack-meeting-316:52
*** jproulx has joined #openstack-meeting-316:53
*** dstanek has left #openstack-meeting-316:53
*** spzala has quit IRC16:53
*** julim has joined #openstack-meeting-316:53
*** marios_ has joined #openstack-meeting-316:53
*** marios has quit IRC16:54
*** marios_ is now known as marios16:55
*** mickeys has quit IRC16:56
*** mickeys has joined #openstack-meeting-316:57
*** cloudtrainme has quit IRC16:57
*** hdaniel has quit IRC16:58
*** singlethink has joined #openstack-meeting-316:58
docaedoCourtesy ping: kfox1111 kzaitsev_mb markvan spzala16:59
*** jpomeroy has quit IRC17:00
docaedo#startmeeting app-catalog17:00
openstackMeeting started Thu Apr  7 17:00:19 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:00
*** openstack changes topic to " (Meeting topic: app-catalog)"17:00
openstackThe meeting name has been set to 'app_catalog'17:00
docaedo#link Agenda17:00
docaedomorning (or evening I guess!) kzaitsev_mb17:00
*** lpetrut has quit IRC17:00
*** s3wong has joined #openstack-meeting-317:00
*** rosmaita has left #openstack-meeting-317:01
*** mickeys has quit IRC17:01
kzaitsev_mbevening, indeed =)17:01
*** cdent has left #openstack-meeting-317:02
docaedoMaybe just us today? Might as well follow the agenda for official record keeping :)17:02
docaedo#topic Status updates17:02
*** openstack changes topic to "Status updates (Meeting topic: app-catalog)"17:02
*** neelashah has joined #openstack-meeting-317:02
*** rossella_s has quit IRC17:03
docaedokzaitsev_mb: can you give a quick update on glare status? I have not checked in on the latest patches but sounds like runserver local works for glare testing?17:03
docaedowelcome markvan !17:03
*** rossella_s has joined #openstack-meeting-317:03
*** kfox1111 has joined #openstack-meeting-317:03
*** NikitaKonovalov_ has quit IRC17:03
*** iyamahat has joined #openstack-meeting-317:03
*** vgridnev has quit IRC17:04
docaedohey kfox1111 - this is turning into a real meeting all of a sudden ;)17:04
*** huichun has quit IRC17:05
kzaitsev_mbdocaedo: I've been away most of the prev week. As for the patches — kfox1111 updated them to work with run_tests and I've updated the angular ones to work on top of that17:05
kfox1111awesome. :)17:05
docaedoah great - kfox1111 is there anything to note about testing glare with runserver or is it pretty obvious from the patch?17:05
kzaitsev_mbunified them (more or less compliant with horizon's style-guide)17:05
kfox1111it should work the same way its worked in the past.17:05
docaedoawesome I will mess with it today17:06
kfox1111it will just be slower since it has to import all the entries to sqlite.17:06
*** yamahata has quit IRC17:06
*** david-lyle has joined #openstack-meeting-317:06
docaedosounds like we're in good shape to get to a point where we can demo this at the summit17:06
kzaitsev_mbthe one that's supposed to add assets to glare is still a WIP, but most of the code is already there, I hope to finish it off today/tomorrow.17:07
kzaitsev_mbWe still haven't started work on auth though17:07
*** yamamoto has joined #openstack-meeting-317:07
docaedoyeah I expect that one is going to be hairy17:07
kfox1111yeah. that'll be a fair amount of effort to get right.17:07
*** pcaruana has joined #openstack-meeting-317:08
docaedobut getting all the right parts lined up first at least so it'll be easy to focus on the auth piece17:08
*** ddieterly is now known as ddieterly[away]17:08
docaedoRegarding AppCatalog OSC plugin17:09
docaedoStill holding for repo creation but that should land shortly, then pvaneck can get that code in the official repo17:09
docaedofor the first pass/foundation I think it's great, does just what we'd want for v1 api and will be easy to build from17:10
docaedoright now just does list and show, but pretty cool start17:10
*** songole has joined #openstack-meeting-317:10
*** david-lyle has quit IRC17:11
kfox1111+1. :)17:11
docaedosome rough edges on formatting a little bit, but nice base17:12
kfox1111so, those are all components...17:12
*** salv-orlando has joined #openstack-meeting-317:12
kfox1111I'd suggest we rework it to be:17:12
kfox1111openstack catalog app list17:13
kfox1111openstack catalog component list17:13
*** ddieterly[away] is now known as ddieterly17:13
*** annegentle has quit IRC17:14
docaedothat could make sense though I figured we'd be narrowing down by type - but lots of time to tweak and adjust anyway17:14
*** MarkAtwood has joined #openstack-meeting-317:14
*** annegentle has joined #openstack-meeting-317:14
kzaitsev_mbdocaedo: those formatting issues can be worked around I believe. At least I believe my outreachy mentee managed to find a workaround =)17:14
*** hemanthravi has joined #openstack-meeting-317:14
kfox1111yeah. but I think our users will fall naturally into those two camps.17:14
kfox1111further filtering can be done in either case.17:15
*** annegentle has quit IRC17:15
kfox1111when I just want to launch an app, I really don't want to see all the little bits.17:15
*** annegentle has joined #openstack-meeting-317:15
*** salv-orlando has quit IRC17:15
*** yamamoto has quit IRC17:16
*** baoli has quit IRC17:16
kfox1111should be pretty easy to kergigger around though.17:16
*** baoli has joined #openstack-meeting-317:17
docaedoagreed - I'm hoping we'll get a conversation going *somewhere* about what an OpenStack App looks like some day17:17
*** fitoduarte has joined #openstack-meeting-317:17
*** david-lyle has joined #openstack-meeting-317:17
kfox1111+1. maybe we can talk more about it at the summit this time around.17:17
*** spzala has joined #openstack-meeting-317:17
docaedoyep - more on that in our next topic ;)17:18
kzaitsev_mbaren't those what the summits are for =)17:18
docaedomarkvan: any updates on the testing stuff? Need feedback/help on anything?17:18
markvanafter a few chats with the horizon folks, seems like there might a slight change in direction for int testing framework, but will have some discussions at the summit to clarify17:19
*** fitoduarte has quit IRC17:20
markvanbasically how to best go foward with something that makes it easy for new angular code17:20
docaedocool - I'm going to ask for time with the horizon team to talk about app catalog UI and horizon with them (maybe a portion of one of their sessions)17:21
kfox1111yeah. I've got some discussions with them on that too.17:21
kfox1111on a related note,17:21
kfox1111a stab at moving the horizon plugin over to share app-catalog-common.17:21
docaedooh yeah that counts as an update :)17:21
kfox1111found one hitch that I'm working around, but horizon never considered a plugin would need aditional xstatic deps.17:22
*** spzala has quit IRC17:22
kfox1111so a non hackish solution should be discussed with them.17:22
kfox1111also, we'd like to share some of their angular widgets on our webiste. so being able to pull them out more easily and have both parties depend on them would be nice to talk about too.17:22
*** baoli has quit IRC17:23
*** david-lyle has quit IRC17:23
docaedoyeah that would be a good conversation to have. I'm (as always) reluctant to tie the web site too closely to horizon project directly but when it solves more problems than it creates I'm in17:24
kfox1111yeah. we wouldn't be useing all of horizon. just using some of the stuff they already created/support.17:24
kfox1111so we don't have to write a clone ourselves.17:24
*** esikachev has quit IRC17:24
kfox1111their magic search angular plugin and smart table stuff make things much easier.17:25
docaedoyep, I think I follow and agree there17:25
kfox1111right now, I just copy'ed the raw files in.17:25
kfox1111it would be nice to have that be an external dep so bugs get fixed automatically.17:25
kzaitsev_mbwe just need to make them to publish it as some sort of xstatic package, right?17:25
docaedo#action docaedo to ask Horizon team for some work session time at summit17:25
docaedoI think the part that scares me is that they won't be considering the app catalog website when making changes, so we need to be very deliberate with the web site17:26
* docaedo notes we've already moved on to the next topic, so...17:27
kzaitsev_mbyeah, but if they publish it as some sort of package — we would be able to depend on specific package version17:27
docaedo#topic Summit workroom session topics17:27
*** openstack changes topic to "Summit workroom session topics (Meeting topic: app-catalog)"17:27
docaedoPlease everybody take a look at that etherpad and throw some stuff up there today.17:29
docaedoI want to update the summit schedule with some descriptions by end of the week17:29
kzaitsev_mbI've looked at the schedule — And I have a murano meeting, that conflicts with 1st app-catalogs one17:30
*** banix has joined #openstack-meeting-317:30
docaedoah that's a bummer17:30
kzaitsev_mbdocaedo: yep, I believe ttx mentioned, that end of next week is the dedaline for those, but always better to have it early17:30
docaedothe fishbowl session?17:30
*** sambetts is now known as sambetts|afk17:30
docaedoyeah I want to get the details up ASAP because people are already going through the schedule and figuring out where they're going to spend their time.17:31
docaedoHaving basically empty entries is not going to attract anyone :)17:31
kzaitsev_mbgotta dig up a schedule table. it was there in one of the letters17:32
*** tqtran has joined #openstack-meeting-317:33
kfox1111openstack cli has 'catalog' bound to the keystone catalog. :/17:33
kfox1111thats really unfortunate.17:34
*** spzala has joined #openstack-meeting-317:35
kfox1111shoudl we talk about the naming collision again at the summit?17:35
*** fitoduarte has joined #openstack-meeting-317:36
*** ddieterly is now known as ddieterly[away]17:36
docaedoI think appcatalog is ok - considering all the history around use of catalog with respect to keystone, that seems like a pointless battle17:36
kfox1111yeah, no I'm not arguing we try and get them to rename.17:37
kfox1111I'm saying the term 'catalog' itself is really overloaded and painful. :/17:37
*** pvaneck has joined #openstack-meeting-317:37
kfox1111should we rename ourselves 'app store' or some other, less contended word?17:37
kfox1111 grimoire or something? (I would have to hate to spell that though... :)17:38
docaedoI don't know, just publicizing the use of "openstack appcatalog list glance" or "appcatalog search Ubuntu" does not feel ambiguous to me17:38
kfox1111no, I'm talking a higher level.17:38
kfox1111I get questions all the time,17:38
kfox1111your talking about murano, right?17:38
kzaitsev_mbkfox1111: saw your discussions about all the 'naming hell' we're in. Seems like we'll have a chance to talk that one once more on summit17:39
kfox1111this is just yet another little case of using a term way too much.17:39
*** spzala has quit IRC17:39
*** mickeys has joined #openstack-meeting-317:39
kfox1111yeah, that.17:39
kfox1111I added a thing in the etherpad.17:40
docaedowell yeah, I don't think anyone benefits by us picking a name that obfuscates what we're doing but I would gladly discuss/debate as well17:40
*** vtech has joined #openstack-meeting-317:41
docaedo(I'm partial to Application Index, but that doesn't sound really classy :) )17:41
*** ihrachys has quit IRC17:41
*** vtech has quit IRC17:41
kfox1111time for a thesaurus. :)17:42
*** vtech has joined #openstack-meeting-317:42
kzaitsev_mbnaming things is haaard =(17:42
*** toddjohn has joined #openstack-meeting-317:42
kfox1111yeah. :/17:42
docaedoI think we have enough for the work sessions anyway, so I can add details to the schedule and we can always adjust later17:43
docaedo#action docaedo to update summit schedule with work room session topics17:43
kfox1111the openstack registry, the openstack app registry, etc?17:43
docaedonot bad17:43
markvanopenstack "warehouse" list glance  ;)17:44
kfox1111no need to figure it out today...17:44
kfox1111hmm... warehouse is good too...17:44
docaedoI'll bring some darts, we'll write them all on a board and see which one wins :D17:44
kfox1111k. added those 2 to the etherpad too.17:44
*** noggin143 has joined #openstack-meeting-317:44
docaedo#topic Open discussion17:45
*** openstack changes topic to "Open discussion (Meeting topic: app-catalog)"17:45
docaedothe floor is open :)17:45
*** mickeys has quit IRC17:46
kfox1111"exchange" maybe...17:46
kzaitsev_mbdocaedo: yeah, I have a murano work session at the same time as the app-catalog fishbowl, so I'll probably miss at least the first part of it. I'll try to pick the topics so that I'll be able to get to the 2d half of the fishbowl =)17:46
*** toddjohn has quit IRC17:47
kfox1111go to the openstack exchange and download...17:47
docaedokzaitsev_mb: cool, appreciate the scheduling gets really tough, appreciate whatever you can make17:47
*** mickeys has joined #openstack-meeting-317:47
*** noggin143 has left #openstack-meeting-317:48
*** spzala has joined #openstack-meeting-317:50
*** davidsha has joined #openstack-meeting-317:51
*** tbachman has joined #openstack-meeting-317:51
*** SumitNaiksatam has joined #openstack-meeting-317:51
docaedoAnything else?17:52
*** jpomeroy has joined #openstack-meeting-317:52
*** toddjohn has joined #openstack-meeting-317:52
docaedoThanks for coming, looking forward to seeing you all in a few weeks in Austin!17:52
*** e0ne has joined #openstack-meeting-317:53
*** openstack changes topic to "OpenStack Meetings ||"17:53
openstackMeeting ended Thu Apr  7 17:53:16 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:53
openstackMinutes (text):
*** mickeys has quit IRC17:54
*** mickeys has joined #openstack-meeting-317:55
*** kzaitsev_mb has quit IRC17:55
*** david-lyle has joined #openstack-meeting-317:56
*** david-lyle has quit IRC17:56
*** david-lyle has joined #openstack-meeting-317:58
*** tbachman has quit IRC17:58
*** vgridnev has joined #openstack-meeting-317:58
*** vikram has quit IRC18:00
SumitNaiksatamigordcard: hi18:01
*** cloudtrainme has joined #openstack-meeting-318:01
SumitNaiksatamhemanthravi: hi18:01
*** rkukura has joined #openstack-meeting-318:03
SumitNaiksatamwaiting for rkukura to join18:03
SumitNaiksatamah there he is18:03
rkukurahi - sorry I’m late18:03
SumitNaiksatam#startmeeting networking_policy18:03
openstackMeeting started Thu Apr  7 18:03:19 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
*** e0ne has quit IRC18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: networking_policy)"18:03
openstackThe meeting name has been set to 'networking_policy'18:03
SumitNaiksatam#info agenda
SumitNaiksatamrkukura: no worries18:03
SumitNaiksatamso just a quick heads up at the outset18:04
*** julim has quit IRC18:04
SumitNaiksatamthe gate is broken because of a new version of a dependency lib (fixtures)18:04
SumitNaiksatamits being fixed in neutron, and possibly in upper-constraints as well, but until then our py27 will fail18:05
*** singlethink has quit IRC18:05
SumitNaiksatamits failing on the stable branches as well18:05
SumitNaiksatamigordcard: yeah18:05
SumitNaiksatamand barring a few, most tests fail due to this18:06
SumitNaiksatamit might be possible to pin that dependency in your local repo but i havent tried it18:06
*** piet has quit IRC18:06
igordcardSumitNaiksatam: oh is that the same that is blocking my devstack patch?18:06
SumitNaiksatambut your devstack patch was failing on the previous day as well, right?18:07
SumitNaiksatamigordcard: let me check18:07
SumitNaiksatami rechecked yesterday18:07
SumitNaiksatamits fine now18:07
*** davidsha has left #openstack-meeting-318:07
SumitNaiksatami might have rechecked before this gate breakage18:07
SumitNaiksatamhemanthravi: still there?18:08
SumitNaiksatam#topic Design Spec - NFP18:08
*** openstack changes topic to "Design Spec - NFP (Meeting topic: networking_policy)"18:08
hemanthravihave couple of patches that failed.18:08
hemanthravinot sure if it's due to this18:08
SumitNaiksatamhemanthravi: ok, need to check18:08
SumitNaiksatamthe wierd thing is that my sanity job passed on our master (which is mitaka(18:09
SumitNaiksatamso perhaps mitaka is capped properly18:09
*** mrmartin has quit IRC18:09
SumitNaiksatamkilo and liberty are definitely failing for that same reason18:09
SumitNaiksatamhemanthravi: thanks for updating the spec in response to the last set of comments18:09
SumitNaiksatamigordcard: i believe you had +1’ed this earlier, and hemanthravi has responded to your pending comments post that18:10
hemanthraviaddressed all the comments so far, let me know if anyging is missing18:10
SumitNaiksatamigordcard: are you okay with the current state of the spec?18:11
SumitNaiksatamprobably igordcard has slow connection18:12
*** mfranc21_ has joined #openstack-meeting-318:12
SumitNaiksatami think most of my comments were answered18:12
SumitNaiksatamsince this is a large feature, it would have been good to have more details documented18:12
*** e0ne has joined #openstack-meeting-318:13
SumitNaiksatamhowever, the spec is place to facilitate the design discussion18:13
igordcardI didnt have major issues with it, no18:13
SumitNaiksatamand the implementation details should be captured in the devref documentation18:13
SumitNaiksatamigordcard: okay thanks18:13
SumitNaiksatamrkukura: did you get a chance at all to look at the spec?18:14
SumitNaiksatamhemanthravi: i believe osm has reviewed this spec?18:14
hemanthraviyes, he has18:14
rkukuranot recently18:14
SumitNaiksatamhemanthravi: and magesh?18:14
*** e0ne has quit IRC18:14
SumitNaiksatamhemanthravi: okay can you please get them to comment/vote?18:15
SumitNaiksatamrkukura: okay18:15
hemanthraviwill do18:15
songolewill do18:15
SumitNaiksatamsongole: ah there you are18:15
*** mfranc213 has quit IRC18:15
hemanthravihave also posted a number of patches for the impl18:15
SumitNaiksatamhemanthravi: right18:15
SumitNaiksatamrkukura: igordcard: at this point my proposal is that we move forward with this spec unless there are any major objections to anything particular18:16
*** annegentle has quit IRC18:16
SumitNaiksatamand expect that finer implemetation details will be documented in devref documents that will accompany the impl patches18:16
SumitNaiksatamdoes that sound okay?18:16
rkukuraSumitNaiksatam: OK - I will re-review it today if possible18:16
*** annegentle has joined #openstack-meeting-318:16
SumitNaiksatamrkukura: okay cool, thanks18:17
hemanthravirkukura, thanks18:17
igordcardSumitNaiksatam:  yeah18:17
SumitNaiksatamigordcard: okay, thanks18:17
SumitNaiksatam#topic GBP Devstack Plugin18:17
*** openstack changes topic to "GBP Devstack Plugin (Meeting topic: networking_policy)"18:17
SumitNaiksatamhemanthravi: thanks for the NFP discussion18:18
SumitNaiksatamigordcard: thanks for posting this patch18:18
SumitNaiksatamigordcard: i have tested it and it works well!18:18
SumitNaiksatamigordcard: i put a comment about the log confguration18:18
igordcardSumitNaiksatam: cool! I'll add some ocumentation and a few todos I have annoted18:19
SumitNaiksatamigordcard: i did notice that the logs were getting populated in /opt/stack/logs by default, but i didnt find the stack.sh18:19
SumitNaiksatamigordcard: hence i put that comment18:19
igordcardSumitNaiksatam: alright, I will check and see18:19
SumitNaiksatamits quite possible that i was looking through blurry eyes late in the night, and i might have missed it! :-)18:20
SumitNaiksatamplease add it if its required18:20
SumitNaiksatamigordcard: and yeah, TODOs sounds good18:20
SumitNaiksatamhemanthravi: can you or your team take a look at this devstack?18:21
SumitNaiksatamhemanthravi: my thinking is that we should build the NFP devstack (targeted for the summit) on top of this18:21
hemanthraviSumitNaiksatam, igordcard started looking at this18:21
SumitNaiksatamhemanthravi: yeah, the GBP devstack plugin is ready18:21
hemanthravifor the same to use it for nfp too18:21
hemanthravimean the same approach18:21
SumitNaiksatamhemanthravi: are you asking if igordcard  is looking at it, or are you saying that igordcard has already started looking at it?18:22
hemanthravii meant dhuldev who did the nfp devstack srcript is going to use igordcard patch to modify his script to follow the same approach18:23
SumitNaiksatamhemanthravi: perfect18:23
rkukuraHas there been any testing of this devstack plugin on CentOS yet? If not, I’ll try that.18:23
SumitNaiksatamhemanthravi: my estimate is that it should be a matter of just moving the scripts18:24
igordcardhemanthravi: it's probably only a change of 1 or 2 lines in the devstack plugin, to enable the additional nfp plugin and maybe some env vars18:24
SumitNaiksatamrkukura: no, and that would be awesome!18:24
SumitNaiksatamigordcard: yeah18:24
hemanthraviigordcard, thanks18:24
igordcardhemanthravi: we can either merge the devstack plugin now and then you/others create a new one on top, or we can delay this a little a bit and incorporate everything in my current patch18:25
hemanthravishould we merge the nfp script into gbp plugin or keep it separate for now18:25
SumitNaiksatamrkukura: just to be totally clear, i have only tested GBP devstack till date only on Ubuntu18:25
SumitNaiksatamigordcard: no, we first merge your patch18:25
igordcardrkukura: no, I've only tried in Ubuntu 14.04 with Liberty cloud archive and stable/mitaka devstack branch18:25
SumitNaiksatamhemanthravi: lets keep the NFP devstack part outside the tree for now18:26
*** sdake_ has joined #openstack-meeting-318:26
*** doug-fish has joined #openstack-meeting-318:26
*** sdake has quit IRC18:26
SumitNaiksatamhemanthravi: our you could add it to your patch series18:26
igordcardSumitNaiksatam: same here18:26
igordcardSumitNaiksatam: about ubuntu18:26
SumitNaiksatamigordcard: right18:26
SumitNaiksatamrkukura: also, igordcard is reusing most of the scripts we already had for the GBP devstack we were installing earlier18:27
SumitNaiksatamrkukura: he has put it into the right plugin hooks, so that we dont have to manually run those scripts and patch18:27
igordcard yes yes18:27
SumitNaiksatamrkukura: i say this to highlight that the scripts have mostly been already tested18:28
SumitNaiksatamso there should not be any big alarms here, this is not a totally new devstack18:28
SumitNaiksatam*devstack installation18:28
rkukuraSumitNaiksatam: right - there was an edit needed with the old scripts for them to work on CentOS, so I’m hoping that will get resolved18:28
SumitNaiksatamrkukura: ah ok18:28
*** dc_mattj has joined #openstack-meeting-318:29
igordcardSumitNaiksatam: I just think maybe some testing should be done around customizing other variables in local.conf, that might be necessary for some reason, and seeing if the devstack plugin still works well18:29
SumitNaiksatamigordcard: thanks a ton for getting this done18:29
SumitNaiksatamigordcard: okay18:29
SumitNaiksatamigordcard: i would prefer to merge this first, and then add fixes in follow up patches if required18:29
SumitNaiksatamassuming everyone else in the team is on board with taht18:30
SumitNaiksatamhemanthravi: will appreciate if you, songole, magesh can review/test this devstack plugin18:30
igordcardSumitNaiksatam: alright, I'll add basic doc on enabling the plugin today and then it will be ready to merge18:30
hemanthraviwill do18:31
SumitNaiksatamsince rkukura is testing on CentOS, i need one more core to do this on ubuntu18:31
igordcardSumitNaiksatam: I'll also investigate the log issue18:31
SumitNaiksatamigordcard: nice!18:31
SumitNaiksatamigordcard: thanks again for the update, and all the work18:31
SumitNaiksatam#topic Design Summit Prep18:31
*** openstack changes topic to "Design Summit Prep (Meeting topic: networking_policy)"18:31
SumitNaiksatamsorry this was not on the documented agends18:31
SumitNaiksatambut since we have a little more time18:32
*** s3wong has quit IRC18:32
*** salv-orlando has joined #openstack-meeting-318:32
SumitNaiksatamso regarding the workshop - i shared a high level script with the authors on the workshop18:32
SumitNaiksatamrkukura: i will share with you and others in the team as well, did not want to share it prematurely if there were going to be changes based on initial feedback18:33
SumitNaiksatamone of the things we really need to have heading into the summit is to beef up our devref documentation18:33
SumitNaiksatamso i requested igordcard to take a look a our existing specs and try to see if those can be massaged into devref documents18:34
*** tonytan4ever has quit IRC18:34
hemanthraviSumitNaiksatam, started working on the service developer workflow - will try to get that done by tue18:34
SumitNaiksatamas a first pass, mu proposal, was to merely translate the content from the specs to corresponding docs18:34
SumitNaiksatamhemanthravi: nice!18:34
*** tonytan4ever has joined #openstack-meeting-318:34
SumitNaiksatambut this is a general call to action to the entire team18:35
SumitNaiksatamigordcard: would you be willing to coordinate this activity?18:35
igordcardSumitNaiksatam: I don't know if I have enough time these next weeks to "coordinate" it, but I surely can port at least a part of the specs to devref18:36
*** ddieterly[away] has quit IRC18:36
SumitNaiksatamigordcard: nice, any progress we can make here, helps18:37
igordcardSumitNaiksatam: I can keep in touch with the rest of the folks involved so each one can focus on specific parts18:37
SumitNaiksatamigordcard: right, so if you can let us know which specs you are starting with, others can jump in as well18:38
SumitNaiksatamigordcard: dont have to decide now18:38
SumitNaiksatamigordcard: we can sync up offline on this18:38
igordcardyeah, but feel free to start first and tell me about it, as well18:38
*** salv-orlando has quit IRC18:38
SumitNaiksatamigordcard: sure18:38
SumitNaiksatam#topic Open Discussion18:39
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:39
SumitNaiksatamrkukura: i am guessing there wasnt much to discuss on the packaging topic, right?18:39
rkukuranothing noew18:39
SumitNaiksatamrkukura: okay18:39
SumitNaiksatamwe need to release mitaka18:40
SumitNaiksatami am just waiting to get feedback on the drivers, if they are working correctly18:40
SumitNaiksatamanything else for today?18:41
*** spzala has quit IRC18:42
*** ddieterly has joined #openstack-meeting-318:42
SumitNaiksatamalrighty, thanks all for joining18:42
*** sambetts|afk has quit IRC18:42
rkukurathanks SumitNaiksatam!18:42
hemanthravithanks, bye18:42
SumitNaiksatamhemanthravi: and igordcard, i know its late for you, good night!18:42
igordcardbye all18:43
*** hemanthravi has quit IRC18:43
*** openstack changes topic to "OpenStack Meetings ||"18:43
openstackMeeting ended Thu Apr  7 18:43:15 2016 UTC.  Information about MeetBot at . (v 0.1.4)18:43
openstackMinutes (text):
*** rkukura has left #openstack-meeting-318:43
*** ddieterly is now known as ddieterly[away]18:44
*** spzala has joined #openstack-meeting-318:44
*** sambetts has joined #openstack-meeting-318:46
*** mickeys has quit IRC18:46
*** ddieterly[away] is now known as ddieterly18:46
*** mickeys has joined #openstack-meeting-318:47
*** annegentle has quit IRC18:49
*** shamail has joined #openstack-meeting-318:49
*** njohnston has quit IRC18:49
*** songole has quit IRC18:50
*** annegentle has joined #openstack-meeting-318:50
*** spzala_ has joined #openstack-meeting-318:50
*** SumitNaiksatam has left #openstack-meeting-318:51
*** vtech has quit IRC18:51
*** mickeys has quit IRC18:51
*** salv-orlando has joined #openstack-meeting-318:52
*** annegentle has quit IRC18:52
*** spzala has quit IRC18:53
*** spzala has joined #openstack-meeting-318:53
*** spzala_ has quit IRC18:55
*** rstarmer has joined #openstack-meeting-318:56
*** neelashah has quit IRC18:56
*** neelashah has joined #openstack-meeting-318:56
*** spzala has quit IRC18:57
*** pfreund has joined #openstack-meeting-318:58
shamailping jproulx18:59
*** sambetts has quit IRC19:00
shamail#startmeeting nonatc19:00
openstackMeeting started Thu Apr  7 19:00:07 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:00
*** openstack changes topic to " (Meeting topic: nonatc)"19:00
openstackThe meeting name has been set to 'nonatc'19:00
*** e0ne has joined #openstack-meeting-319:00
*** MeganR has joined #openstack-meeting-319:00
*** ddieterly is now known as ddieterly[away]19:00
shamail#topic roll call19:00
*** openstack changes topic to "roll call (Meeting topic: nonatc)"19:00
shamailWelcome everyone to the first Non-ATC recognition WG meeting.  Can you please let us know if you're here to participate in this meeting?19:00
dc_mattjI am19:00
pfreundI am19:00
shamailPerfect, glad to see everyone!  Let's get started with the first item on our agenda.19:01
*** salv-orlando has quit IRC19:01
shamail#link is the agenda for today.19:01
shamailhi jproulx and dabukalam19:01
shamail#topic Review objective and what is "in scope"19:01
*** openstack changes topic to "Review objective and what is "in scope" (Meeting topic: nonatc)"19:01
*** maishsk has joined #openstack-meeting-319:01
shamail#chair maishsk19:01
openstackCurrent chairs: maishsk shamail19:01
maishskGood eveing all19:01
*** noggin143 has joined #openstack-meeting-319:02
shamailAll of this information is available in the wiki but we thought it would be good to start the first meeting by covering the scope of this WG.19:02
shamailWhenever we discuss recognition, the conversation tends to move towards the "what" (e.g. what will be provided: summit tickets, association on summit badges, voting rights, etc.) but that is out of scope for our WG.19:02
*** esikachev has joined #openstack-meeting-319:02
shamailThe user committee will be defining a charter and that will include the benefits given to its constituency and, therefore, they will be addressing the "what".19:02
shamailWe will be focusing on defining the "who" and "how": which community members should be recognized by the User Committee as its constituency and how will we check eligibility.19:02
*** emagana has joined #openstack-meeting-319:03
shamailAny questions or concerns about the scope?19:03
emaganahi all!19:03
dc_mattjhey edgar !19:03
shamailhi emagana and noggin14319:03
*** sambetts has joined #openstack-meeting-319:03
emaganajust joining but in another meeting as well...  double booked for this time..19:03
jproulxshamail good description of scope thanks, "who & how but not what"19:03
dc_mattjyup, fully agree19:04
shamailMoving on then...19:04
shamail#topic Review milestones from wiki19:04
*** openstack changes topic to "Review milestones from wiki (Meeting topic: nonatc)"19:04
shamailPlease take a moment to read/review the milestones that are defined on the wiki.  We'll pause for a minute while everyone reads...19:04
shamailAny questions or concerns with the milestones?19:05
* maishsk puts on his reading glasses19:05
shamailMilestone 1 (create WG) has been completed and we are now working on milestone 2 (identify community members for constituency)...19:05
MeganRMilestone #6: Create a model of estimated costs - can you explain the anticipated costs?19:06
shamailIn this phase, we need to identify all the various roles members in the community that we believe further the goals and objectives of the user committee.  We will revisit the topic in more detail during our next topic (reviewing the ACC proposal).19:06
dc_mattjquestion shamail - how do members get differentiated like that ? I have to admit it's been a long time since I registered as a Foundation member ..19:06
dc_mattjis there something to self-identify now in the sign up process ?19:06
*** nikhil has quit IRC19:07
shamailMeganR: good catch, milestone 6 was added to help determine the cost implications based on the number of constituents and planned benefits but that requires the “what” to be defined first19:07
maishskdc_mattj: one you register as foundation member - you are one for life19:07
shamailwe might need to move that milestone into something that the UC has to determine (versus this WG)19:07
pfreundAre Ops part of ACC ?19:07
maishskpfreund: define Ops?19:07
shamailWe’ll get to that shortly, but yes, they kind of were… the ACC proposal is a starting point for us but we can make changes.19:08
jproulxpfreund: that's part of milestoen 2 which is in progress19:08
pfreundsubmit defects, confirm bugs19:08
shamail#topic Review ACC proposal from board meeting19:08
*** openstack changes topic to "Review ACC proposal from board meeting (Meeting topic: nonatc)"19:08
pfreundfor me it's not the same profil for "organising meetups"19:08
dc_mattjI meant related to milestone 2, how you differentiate the different kind of community members19:08
shamailpfreund: +119:08
maishskI concur19:08
shamailIt is indeed dc_mattj19:08
shamailThe ACC proposal is something we can review and then modify as needed based on group feedback19:09
pfreundMaybe it's only my vision, but I see code contributors (ATC), Community contributors (ACC) and Ops19:09
shamailThe ACC proposal actually contains members and even metrics but those portions will be discussed in two separate milestones fo rus19:09
shamailI guess that is a broader question that we should clarify early on in milestone 219:09
jproulxI think a sub part of milestone 2 may be deciding how the different constituencies should be (want to be) grouped19:10
shamailDo we envision one recognition (e.g. ACC) for all roles that we identify or should we have differing recognition types based on roles?19:10
shamailread my mind jproulx19:10
dc_mattjI suspect most folks doing any of those things from the ACC proposal are more than likely operators anyway - although I may be wrong19:10
shamaildc_mattj: In the ACC proposal, it mentions activities associated with operators, user group organizers, working group members, bug submitters, ops-meetup moderators, and creating OpenStack-related content that promotes knowledge sharing (not counting submissions to docs since that would qualify for ATC already)19:10
maishskdc_mattj: they most probably are, but not exclusively19:11
shamail#action modify milestone 2 to also including grouping identified members19:11
fungikeep in mind that atc are not only contributing code (also documentation, translations, running servers for the community services, performing testing and quality assurance, release management, acting as gatekeepers for stable branches, doing security analysis and writing guidelines, et cetera)19:11
maishskSo the only one I have a slight issue with is mettup attendees - but then again - a topic for future discussions19:11
*** nikhil has joined #openstack-meeting-319:11
pfreundIn the french OpenStack user group, they are some none-technical people (so not Ops) who are actually participating to Community events. It can be business profiles for exemple. Si dc_mattj I don't afgree19:12
shamailYeah, wanted to use today to get everyone on the same page with objectives/milestones/logistics and then dive into milestone 2 at the next meeting19:12
shamailor this meeting if time is left after the other topics19:12
jproulxshamail +119:12
dc_mattjgood point pfreund, we have the same in the UK user groups19:12
maishsk@shamail agreed19:12
shamailSo some background on ACC for everyone..19:13
shamailaul and Lisa-Marie have been working on a proposal to gain recognition for the hard work that our community members do (run user group meetups, participate in working groups, file bugs, etc.) and this proposal was reviewed at the last board meeting.19:13
*** david-lyle_ has joined #openstack-meeting-319:13
maishskWhat was the feedback from the board meeting?19:13
shamailIt was well received and the feedback was for our WG to work with them to build a common plan.19:14
*** vgridnev has quit IRC19:14
shamail I think it is a great starting point and thank them for their (months of) effort.19:14
*** salv-orlando has joined #openstack-meeting-319:14
shamailWe can revisit different, relevant, sections of the ACC proposal during our milestones.19:14
shamailAny questions on the original ACC proposal?19:14
*** vtech has joined #openstack-meeting-319:14
jproulxAre the people involed with ACC here (or otherwise engaged)?19:15
noggin143I feel the key is common. It is important not to announce one set of recognitions without the others, if they are felt to be different.19:15
shamailnoggin143: +119:15
*** spzala has joined #openstack-meeting-319:15
shamailjproulx: they were invited, I don’t think they are on today but they are aware of this meeting19:15
*** david-lyle has quit IRC19:15
jproulxI'd hate to loose the thoughts behind the proposal as we go forward19:15
shamailI agree, I will reach out to them again19:15
maishskI agree it would be great to have them involved19:16
shamailnoggin143: I agree that we should build a common plan even if implementation is staggered (e.g. ops might get badge recognition in Austin since that was already in the works)19:16
shamail#topic Recap any other prior work19:17
*** openstack changes topic to "Recap any other prior work (Meeting topic: nonatc)"19:17
shamailgood segue :)19:17
*** sigmavirus24 is now known as sigmavirus24_awa19:17
shamailDoes anyone know of other work being done inside the community that would align with our scope/objective?19:17
jproulxWell as you mentioned there's the OPs badges for AUS19:17
shamailjproulx and emagana: What is the user committee plan for ops-recognition in Austin?  I had seen an email from Tom or Edgar on this topic a while ago19:17
dc_mattjshamail: so just to double check, this is the same stuff that tom was talking to me about in Manchester with regards to ops recognition, or something different ?19:17
maishskthere is the ops-tag team19:18
shamaildc_mattj: this is different, I was telling you about the contributor awards in Manchester19:18
*** iyamahat has quit IRC19:18
emaganashamail: we will have Ops tag19:18
shamailmaishsk: ops-tags-team isn’t working on recognition though19:18
*** hdaniel has joined #openstack-meeting-319:18
noggin143what is the criteria for ops recognition in Austin ?19:18
dc_mattjah ok shamail both worthwhile endeavours19:18
*** Sukhdev has joined #openstack-meeting-319:18
maishskshamail - that is correct19:18
shamailgood question noggin143, we should capture that criteria somewhere as well as we begin our work19:19
jproulxI have the criteria in email (though also not 100% final) I'll see if I can find a reference19:19
*** david-lyle_ has quit IRC19:19
maishskjproulx: that would be great19:19
shamail#action jproulx will share criteria used for ops recognition for the Austin summit19:19
shamailjproulx: Were you trying to find it right now or will you provide it at the next meeting?19:20
jproulxthere's a git repo being set up for scripts related to this19:20
jproulxwatch for it
jproulxI'll take it as a todo for next meeting as it will require some clean up19:21
shamailMoving on to the next topic…19:21
shamail#topic Determine communication/collaboration methods19:21
*** openstack changes topic to "Determine communication/collaboration methods (Meeting topic: nonatc)"19:21
shamailWe need to decide how we will be communicating between meetings and therefore need to identify a tag and mailing list to use.19:21
*** ddieterly[away] is now known as ddieterly19:21
*** clarkb has joined #openstack-meeting-319:21
maishskhow about [nonatc]19:22
jproulx+1 [nonatc]19:22
jproulxnow which list19:22
shamail#startvote which mailing list should we use? uc, ops, community19:22
openstackBegin voting on: which mailing list should we use? Valid vote options are uc, ops, community.19:22
openstackVote using '#vote OPTION'. Only your last vote counts.19:22
dabukalam#vote community19:22
maishsk#vote ops19:22
shamail#vote uc19:22
pfreund#vote uc19:23
fungiit would be nice if the group didn't indefinitely encode a name which identified itself as "not something else"19:23
pfreundops is 50%19:23
*** bpokorny_ has joined #openstack-meeting-319:23
emagana#vote uc19:23
noggin143fungi +1 - I would prefer a positive with recognition19:23
dabukalamfungi: I have to say, I agree19:23
shamailfungi: true, lol.19:23
maishsk@fungi point well made19:23
noggin143#vote ops19:23
shamailany more votes?19:23
pfreund+1 fungi19:23
fungiideally it should be a group defined as what it is, not as what it isn't19:23
shamailgoing once...19:23
openstackVoted on "which mailing list should we use?" Results are19:23
openstackuc (3): shamail, pfreund, emagana19:23
openstackcommunity (1): dabukalam19:24
openstackops (2): noggin143, maishsk19:24
jproulxfungi noggin143 untill we have milestoen 2 done we've not decided what though19:24
maishskuc it is19:24
* dabukalam signs up to uc19:24
*** ihrachys has joined #openstack-meeting-319:24
noggin143that's fine by me too19:24
pfreund[recognition] ?19:24
noggin143+1 [recognition]19:24
maishskor [acc]19:24
shamailThe challenge is that finding an identifer is hard for now since the only commonality so far is that all these contributors are not eligble for ATC based on critera19:24
jproulxI could get behind that19:24
shamail+1 for [recognition]19:25
jproulx+1 [recognition]19:25
*** klindgren has joined #openstack-meeting-319:25
maishsk+1 [recognition] as well19:25
jproulxI think [acc] encodes a choice we haven't yet made19:25
noggin143given that it's on the user committee list, it's clear what the recognition is for as well19:25
shamail#agree Non-ATC recognition WG will use user-committee with [recognition] for communication19:25
*** tbachman has joined #openstack-meeting-319:25
shamail#agree Non-ATC recognition WG will use user-committee mailing list with [recognition] for communication19:26
shamailWhat should we use for collaboration... some options that were raised are google docs, etherpads, a git repo.  What does everyone think?19:26
*** tbachman has left #openstack-meeting-319:26
maishskwhy a git repo?19:26
shamailjproulx and emagana: I was going to suggest creating an overall user-committee repository to eventually host things like the charter, etc.19:26
maishsk+1 for etherpad19:26
dabukalamdc_mattj: +1 etherpad makes sense19:26
MeganR+1 for etherpad19:26
*** bpokorny has quit IRC19:26
jproulx+1 for etherpad19:26
pfreund+1 etherpad19:26
dc_mattjsorry missed that last vote, was reviewing some anti-affinity checking code in python ;)19:26
shamailmaishsk: It might not be the ideal collaboration method but we should eventually post our outcomes in a rendered format19:27
dabukalamtrying to garner opinions from non-devs, a git repo isn't the way to go19:27
dc_mattj+1 for [recognition] anyway19:27
maishskfor collaboration - it is the Openstack way19:27
noggin143+1 etherpad … the git repo makes it more difficult to take part for those we are wanting to recognise19:27
shamail#agree Materials to be shared with the team should be posted using etherpad19:27
maishskand / or wiki?19:27
maishskthe only reason for that is becuase etherpads are impossible to find unless you have a direct link19:28
shamailmaishsk: Yes, the wiki will be used to share outcomes and information… etherpads for items that we need to collaborate on19:28
dc_mattjwiki is always good for info once it's fixed19:28
maishskand they are not indexed on google19:28
shamailWe will make sure to include etherpad links on the wiki19:28
dc_mattjI mean the info is fixed, not the wiki ;)19:28
maishskshamail: perfect19:28
shamailEventually, I’d like it if the user committee could setup a repository for maintaing information (WGs, charter, consitituency, etc) to closer emulate the TC19:29
*** david-lyle has joined #openstack-meeting-319:29
shamailoutside of scope/needs of this WG but I would like to see one in the broader UC context19:29
jproulxshamail: I agree but that's out of scope for this group19:29
shamailThat concludes the topics that were on the agenda19:30
shamailso we can dive in to milestone 219:30
shamail#topic roles recognized as user committee constituency19:30
*** openstack changes topic to "roles recognized as user committee constituency (Meeting topic: nonatc)"19:30
maishskI think the easiest one to start with is WG members19:30
shamailAgree maishsk19:30
*** david-lyle has quit IRC19:31
shamailACC mentions tasks associated with operators, user group organizers, working group members, bug submitters, ops-meetup moderators, and creating OpenStack-related content that promotes knowledge sharing19:31
shamailDo we think these roles are good or do we see obvious gaps?19:31
noggin143how is a WG member defined ? Is it just joining one IRC chat ?19:31
shamailbug submitters is a tough one in my mind19:31
*** david-lyle has joined #openstack-meeting-319:31
maishsktheir activity is logged - due to participation in meetings (which I hope all of these are held in IRC)19:31
shamailnoggin143: In ACC, they defined it as attending 10+ meetings19:31
dc_mattjthe one gap I see is potentially people who answer questions on lists a lot19:31
shamailwe will decide what metric makes sense in a future milestone19:32
dc_mattjbut then you get into the space of how effective answers are19:32
noggin143shamail: OK, reasonable.19:32
jproulxnoggin143 for OPs badge WG activity is being measured as attending at least 2 IRC meetings and saying 10 lines in the past 6 months19:32
shamailtrue dc_mattj19:32
dc_mattjdifficult to put metrics against19:32
jproulxthough that's really very arbitrary becuase we needed something fast19:32
emaganashamail: Tom has recently added a repo for some of this staff19:32
noggin143I think the bug submission should be for those which are accepted as valid.19:32
shamailIs there a dashboard for Ask OpenStack participation stats?19:32
rstarmerso you have to say a line to be considered here?19:33
maishskemagana: link to this repo?19:33
dc_mattjnoggin143: +119:33
rstarmerI'l remember to do that more then :)19:33
shamailemagana: jproulx shared the link earlier… we’ll be keeping an eye on it19:33
*** julim has joined #openstack-meeting-319:33
dc_mattjthere's loads of people who think they've hit bugs when they clearly haven't googled19:33
maishskrstarmer: that is active participation19:33
shamailnoggin143: +119:33
dc_mattjhello rstarmer :)19:33
noggin143I'd like to add some incentives around user stories for the product working group as well.19:34
shamailSo we do we want keep bug submissions (criteria TBD) and add Ask OpenStack participation (criteria TBD)?19:34
rstarmersorry I'm late19:34
shamailnoggin143: generating user stories versus participating in the WG itself?19:34
rstarmerIs there a process for capturing user stories?  I've seen some reference to confusion about the wishlist failure, but won't that just happen again?19:34
shamailright now, every user story has been submitted by people who also join the WG19:34
rstarmerI.e., if user stories become a contributions factor.19:34
shamailrstarmer: The Product WG is building a workflow for user stories but these are focused on multi-project, multi-release type things19:35
dc_mattjshamail: I don't hang out too much on Ask OpenStack as the same questions get asked a million times. Although maybe we should be rewarding people who've got the patience to not tell people to google ;)19:35
pfreundshamail: Is there any metric in ask that says the question has been already answered ?19:35
*** tonytan_brb has joined #openstack-meeting-319:35
jproulxI think we need a high level statement we can compare all the details to19:35
noggin143shamail: I'd like to expand the input beyond that. To be fair, people submitting user stories would almost certianly qualify on one of the other criteria also19:35
shamailnoggin143: +1 and product-wg would welcome that19:36
maishsknoggin143: +119:36
*** NikitaKonovalov_ has joined #openstack-meeting-319:36
rstarmerpfreund: I think it has to be like on serverfault: "that's been answered elsewhere: <link>"19:36
*** tonytan4ever has quit IRC19:36
pfreundI don't know enough Ask to know what kind of metrics are usable19:36
shamailjproulx: can you expand?19:36
shamaildetails for what?19:36
dc_mattjthere's certainly a bunch of people who answer questions on the ops list too, although perhaps they get covered by ops recognition19:36
shamailpfreund: I am in the same boat19:36
*** banix has quit IRC19:36
jproulxwe want to recognized "contibutors that improve openstack"19:37
shamailFor now, let’s identify of activities/roles we would like to recognize… When we discuss metrics then we can rule out ones that don’t have the right statistics to determine eligibility19:37
dc_mattjlast time I looked at Ask, it was endless questions of the 'I ran devstack and my networking doesn't work' calibre19:37
jproulxthen if "people who provide product-wg user stories" improve openstack tehn they shoudl be included some how19:37
*** david-lyle has quit IRC19:37
*** cloudtrainme has quit IRC19:37
noggin143Also ex-uc members should be recognised for life :-)19:37
shamailjproulx: +119:38
jproulxnoggin143 +1 :)19:38
shamailnoggin143: :D I second that19:38
rstarmerjproulx: I agree, how do you also capture the individual "If only Nova did X" stories too?19:38
dc_mattjshamail: +1, in principle folks who answer mailing list questions, however inane, should have some method for being recognised. I have no idea how you qualify or quantify that, but I think it's valid19:38
dc_mattjmaybe that's impossible, but it should be on the potential list19:39
shamailRecapping the list (without establishing criteria for eligibility): operators, user group organizers, working group members, bug submitters, ops-meetup moderators, creating OpenStack-related content that promotes knowledge sharing, Ask OpenStack contributors, user story contributors19:39
*** tonytan_brb has quit IRC19:39
* dabukalam would say it's worth extending to people that answer on #openstack-dev as well, but nobody is insane enough to do that19:39
shamailDoes that capture our ideas so far?19:39
noggin143dc_mattj: we can start with ask where it can be quantified, especially given the voting and then expand if we can find a way19:39
pfreundjproulx: for ATC, there is no difference between contributors that improve OpenStack, and people who don't19:39
*** baoli has joined #openstack-meeting-319:39
rstarmershamail: yes I think that's the top of mind list19:39
*** tonytan4ever has joined #openstack-meeting-319:39
maishskcan I make a suggestion? Lets first collect all the potential contributors19:39
jproulxI think we should get this on etherpad then we can expand and refine19:40
shamailmaishsk: thanks, that’s what I was hoping for as well19:40
MeganRjproulx +119:40
shamailI think we can leave the criteria conversation for a later milestone (and that might reduce our final list_19:40
jproulxfor now we should try and cast as broad a list as possible I think and refine from there19:40
maishskso far we have WG members, user story writers, people who answer on Ask19:40
* shamail creating etherpad… asks for 30 secs19:40
rstarmerpfreund: that's part of the problem, you can become an ATC by fixing a typo in a python module that likely no-one will ever read, or in fixing a documentation bug that actually helps make it easier to run OpenStack.19:40
dc_mattjjproulx: +1, that's what I was also suggesting, brain dump the list then refine19:40
*** bpokorny_ has quit IRC19:40
dabukalamjproulx: +119:40
maishskshamail: you got the moves !!!19:40
*** bpokorny has joined #openstack-meeting-319:41
pfreundrstarmer: I'm one of the fixing typo guy, because I have not choice today to be recognized ,)19:41
*** iyamahat has joined #openstack-meeting-319:41
shamailShould we also include people who present at user groups?19:42
rstarmerpfreund: I've done in the past, but haven't had bandwidth recently. But I've also re-written small sections of the docs to remove confusion (and had to go fix my typos before it got accepted :)19:42
dabukalamshamail: I thought about that earlier, the key problem is sales pitches19:42
shamail(again, I know this will be difficult to gather eligibility data but not worried about that yet)19:43
dabukalamyup, go ahead19:43
shamaildabukalam: good point19:43
rstarmershamail: dabukalam: sales pitches are likely the biggest issue, but at the same time, if the pitch enables someone to deploy OpenStack, or need to deploy OpenStack where they wouldn't have, then that's good for the community too.19:43
shamailDo spec contributions to projects directly normally qualify for ATC?  They are in the same repo right?19:43
shamailas the project*19:43
dabukalamrstarmer: there is a bit of that, but you don't want to encourage salespeople to run around from meetup to meetup trying to hit 10 pitches a cycle as well, needs more thought19:44
shamailThis list looks pretty good so far...19:44
rstarmershamail: I've never seen the filter, but I would imagine if it's in the repo, you get "XX" lines commited to project "YY"19:44
shamailLet’s continue to work on it through next week and revisit the etherpad next Thursday19:45
shamailrstarmer: I agree, that’s why I think that would count as ATC already19:45
shamailalright, another topic related to milestone 219:45
*** mfranc21_ has quit IRC19:45
shamail#topic grouping of roles: single or multiple recognition titles19:45
*** openstack changes topic to "grouping of roles: single or multiple recognition titles (Meeting topic: nonatc)"19:45
shamailAs we develop this list… do we anticipate everyone have a single designation or do we think different designations should be given based on roles (to be defined)19:46
shamailDo we have one group that is the UC constituency or multiple groups inside it?19:46
jproulxI think we shoudl get the full list before we start chopping it up19:46
dc_mattjI think there's a difference19:47
maishskThis could be a doubled edged sword - spreading out too wide and too far might be difficult - but ont he other hand - it might leave some participants out of the loop or group together groups which contibute in different ways19:47
dc_mattjsome of this also crosses over into OpenStack Ambassador territory though right ?19:47
shamailjproulx: fair point19:47
*** rbak_ has joined #openstack-meeting-319:48
rstarmerShamail: I think a single designation, unless someone is going to break ATC down as well, and I think additional designations just increase the complexity of figuring out if you get a mark or not.19:48
shamailIt does indeed dc_mattj19:48
maishskrstarmer: competely agree19:48
shamailA better question for now (until we have a full list) is whether we even think multiple designations is something we want to pursue?19:48
jproulxrstarmer: that's my initial feeling as well19:48
shamailSo far it seems like most people are saying one designation is good enough19:49
shamailrstarmer: +119:49
maishskshamail: I would say one designation - not multiple19:49
dc_mattjshamail: so I think it will depend on pruning of the full list, I don't think we can know that without doing that task first19:49
rstarmershamail: I still think not.  One designation, as an alternative to ATC.  Either you're a developer or your a "we are those who enable OpenStack in the greater world"19:49
shamailOkay, let’s defer this to next week’s meeting19:49
shamailwell put rstarmer19:49
shamailAlright, that’s all the agenda items for today!19:50
shamail#topic open19:50
*** openstack changes topic to "open (Meeting topic: nonatc)"19:50
rstarmer"We make OpenStack (ATC) or We help you use OpenStack (OTC)"19:50
dc_mattjgood meeting :)19:50
rstarmerQuite, looking forward to being on time next time :)19:50
jproulxthat felt shockingly productive for a 1st meeting19:50
shamailI can imagine the metrics/eligibility criteria milestone will be a fun one!19:50
*** rbak has quit IRC19:51
jproulxno doubt19:51
jproulxthanks all19:51
shamailAgreed jproulx, we made good progress today19:51
pfreundthanks :)19:51
shamailThank you everyone!  We’ll end the meeting a bit earlier if there are no other topics19:51
MeganRthank you for putting this together!19:51
*** openstack changes topic to "OpenStack Meetings ||"19:51
openstackMeeting ended Thu Apr  7 19:51:44 2016 UTC.  Information about MeetBot at . (v 0.1.4)19:51
openstackMinutes (text):
pfreundnext meeting is Austin ?19:51
maishskThanks shamail19:51
shamailit’s next Thursday (April 14th)19:52
shamailThanks maishsk19:52
shamailWe should definitely meet in Austin too19:52
pfreundof course19:52
shamailThere is a ops meetup session called “ops recognition: what is it” led by emagana19:52
*** mfranc213 has joined #openstack-meeting-319:52
shamailwe should use that session to have conversations as well19:52
* maishsk will not be attending Austin #sad #panda19:52
*** bpokorny has quit IRC19:52
shamailsorry to hear that maishsk19:52
*** bpokorny has joined #openstack-meeting-319:53
*** alex_xu has quit IRC19:54
*** noggin143 has left #openstack-meeting-319:54
*** alex_xu has joined #openstack-meeting-319:55
*** tonytan_brb has joined #openstack-meeting-319:55
*** MeganR has quit IRC19:57
*** tonytan4ever has quit IRC19:59
*** yamahata has joined #openstack-meeting-320:00
*** hdaniel has quit IRC20:00
*** esikachev has quit IRC20:01
*** jtomasek has quit IRC20:03
*** baoli has quit IRC20:03
*** baoli has joined #openstack-meeting-320:04
*** jtomasek has joined #openstack-meeting-320:05
*** hdaniel has joined #openstack-meeting-320:05
*** jproulx has left #openstack-meeting-320:06
*** cloudtrainme has joined #openstack-meeting-320:08
*** dc_mattj has quit IRC20:08
*** ddieterly is now known as ddieterly[away]20:10
*** galstrom_zzz is now known as galstrom20:13
*** jed56 has quit IRC20:13
*** lpetrut has joined #openstack-meeting-320:13
*** vishwanathj has quit IRC20:14
*** ddieterly[away] is now known as ddieterly20:15
*** bpokorny has quit IRC20:16
*** annegentle has joined #openstack-meeting-320:16
*** dc_mattj has joined #openstack-meeting-320:18
*** maishsk has quit IRC20:21
*** mrmartin has joined #openstack-meeting-320:21
*** sdake_ is now known as sdake20:23
*** maishsk has joined #openstack-meeting-320:23
*** tonytan_brb is now known as tonytan4ever20:26
*** rbak has joined #openstack-meeting-320:26
*** rbak_ has quit IRC20:27
*** numan_ has quit IRC20:28
*** shamail has quit IRC20:29
*** mickeys has joined #openstack-meeting-320:34
*** vtech has quit IRC20:36
*** mickeys has quit IRC20:36
*** julim has quit IRC20:36
*** mickeys has joined #openstack-meeting-320:36
*** vtech has joined #openstack-meeting-320:38
*** spzala has quit IRC20:40
*** baoli has quit IRC20:41
*** hdaniel has quit IRC20:41
*** alexpilotti has quit IRC20:43
*** baoli has joined #openstack-meeting-320:45
*** baoli_ has joined #openstack-meeting-320:46
*** vishwana_ has joined #openstack-meeting-320:47
*** Sukhdev has quit IRC20:47
*** ddieterly is now known as ddieterly[away]20:49
*** baoli has quit IRC20:50
*** baoli_ has quit IRC20:50
*** baoli has joined #openstack-meeting-320:51
*** ddieterly[away] has quit IRC20:52
*** rpjr__ has joined #openstack-meeting-320:56
*** david-lyle has joined #openstack-meeting-320:56
*** rpjr_ has quit IRC20:57
*** marios has quit IRC20:57
*** maishsk_ has joined #openstack-meeting-321:00
*** maishsk has quit IRC21:00
*** maishsk_ is now known as maishsk21:00
*** pcaruana has quit IRC21:01
*** bpokorny has joined #openstack-meeting-321:02
*** rossella_s has quit IRC21:03
*** rossella_s has joined #openstack-meeting-321:03
*** fitoduarte has quit IRC21:04
*** e0ne has quit IRC21:04
*** maishsk has quit IRC21:09
*** alexpilotti has joined #openstack-meeting-321:10
*** e0ne has joined #openstack-meeting-321:11
*** rstarmer has quit IRC21:13
*** maishsk has joined #openstack-meeting-321:13
*** Devon has joined #openstack-meeting-321:14
*** alexpilotti has quit IRC21:14
*** dc_mattj has quit IRC21:15
*** njohnston has joined #openstack-meeting-321:17
*** shakamunyi has joined #openstack-meeting-321:17
*** salv-orl_ has joined #openstack-meeting-321:18
*** e0ne has quit IRC21:18
*** rbak has quit IRC21:21
*** salv-orlando has quit IRC21:22
*** rbak has joined #openstack-meeting-321:22
*** markvan has quit IRC21:24
*** shakamunyi has quit IRC21:24
*** rbak has quit IRC21:24
*** mrmartin has quit IRC21:24
*** rbak has joined #openstack-meeting-321:25
*** Sukhdev has joined #openstack-meeting-321:25
*** Devon has quit IRC21:25
*** DevonBoatwright has joined #openstack-meeting-321:25
*** bpokorny has quit IRC21:25
*** bpokorny has joined #openstack-meeting-321:26
*** markvan has joined #openstack-meeting-321:27
*** alexpilotti has joined #openstack-meeting-321:27
*** rtheis has quit IRC21:31
*** njohnston has quit IRC21:31
*** njohnston has joined #openstack-meeting-321:31
*** njohnsto_ has joined #openstack-meeting-321:32
*** ShillaSaebi has joined #openstack-meeting-321:34
*** iyamahat has quit IRC21:34
ShillaSaebi#startmeeting OpsGuide21:34
openstackMeeting started Thu Apr  7 21:35:00 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:35
*** openstack changes topic to " (Meeting topic: OpsGuide)"21:35
openstackThe meeting name has been set to 'opsguide'21:35
DevonBoatwrightHello there~!21:35
ShillaSaebianyone here for the ops guide/arch guide specialty team meeting21:35
njohnstono/ <- but only partially21:35
*** galstrom is now known as galstrom_zzz21:36
*** klindgren has left #openstack-meeting-321:36
ShillaSaebiVic won't be joining us today21:36
ShillaSaebialright well it will be a light meeting then21:37
ShillaSaebi#topic reviews in progress21:37
*** openstack changes topic to "reviews in progress (Meeting topic: OpsGuide)"21:37
*** baoli has quit IRC21:37
*** baoli has joined #openstack-meeting-321:38
*** rstarmer has joined #openstack-meeting-321:38
ShillaSaebisorry ignore that last link21:38
ShillaSaebithe other 221:38
*** cartik has joined #openstack-meeting-321:39
ShillaSaebi#topic ops guide21:39
*** openstack changes topic to "ops guide (Meeting topic: OpsGuide)"21:39
ShillaSaebiso rst conversion is in progress21:40
ShillaSaebilook at those patches when/if you get a chance21:40
ShillaSaebifor reference #link
ShillaSaebiopen reviews #link,n,z21:41
*** cloudtrainme has quit IRC21:41
*** njohnston has quit IRC21:41
*** iyamahat has joined #openstack-meeting-321:41
DevonBoatwrightI think maybe we're the only two left here?21:45
ShillaSaebialright well i will post updates for our group21:46
ShillaSaebiyou and i can maybe sit together tomorrow and work on some of this stuff21:46
ShillaSaebii think we can adjourn the meeting21:46
DevonBoatwrightSounds good to me!21:47
DevonBoatwrightTo ajourning the meeting and to sitting with you and working on some of thise stuff21:47
*** openstack changes topic to "OpenStack Meetings ||"21:47
openstackMeeting ended Thu Apr  7 21:47:54 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:47
ShillaSaebithanks Devon!21:47
openstackMinutes (text):
DevonBoatwrightSee ya!21:48
*** ShillaSaebi has quit IRC21:48
*** DevonBoatwright has quit IRC21:49
*** Sukhdev has quit IRC21:52
*** alexpilotti has quit IRC21:56
*** rpjr_ has joined #openstack-meeting-321:57
*** rpjr__ has quit IRC22:00
*** bpokorny_ has joined #openstack-meeting-322:01
*** bpokorny_ has quit IRC22:01
*** ddieterly has joined #openstack-meeting-322:01
*** bpokorny_ has joined #openstack-meeting-322:02
*** pvaneck has quit IRC22:03
*** bpokorny has quit IRC22:04
*** ihrachys has quit IRC22:05
*** maishsk has quit IRC22:05
*** jpomeroy has quit IRC22:07
*** neiljerram has quit IRC22:10
*** s3wong has joined #openstack-meeting-322:13
*** rpjr_ has quit IRC22:14
*** lcazares has joined #openstack-meeting-322:14
*** shakamunyi has joined #openstack-meeting-322:18
*** mikal has quit IRC22:18
*** mikal has joined #openstack-meeting-322:18
*** ddieterly is now known as ddieterly[away]22:18
*** ddieterly[away] is now known as ddieterly22:19
*** NikitaKonovalov_ has quit IRC22:20
*** neelashah has quit IRC22:21
*** Sukhdev_ has joined #openstack-meeting-322:21
*** doug-fish has quit IRC22:23
*** shakamunyi has quit IRC22:24
*** Sukhdev_ has quit IRC22:26
*** hdaniel has joined #openstack-meeting-322:26
*** rpjr_ has joined #openstack-meeting-322:28
*** dimtruck is now known as zz_dimtruck22:28
*** ddieterly is now known as ddieterly[away]22:30
*** ddieterly[away] is now known as ddieterly22:30
*** cloudtrainme has joined #openstack-meeting-322:31
*** lpetrut has quit IRC22:32
*** rpjr__ has joined #openstack-meeting-322:32
*** cloudtrainme has quit IRC22:32
*** rpjr___ has joined #openstack-meeting-322:32
*** cloudtrainme has joined #openstack-meeting-322:32
*** hdaniel has quit IRC22:33
*** rpjr_ has quit IRC22:35
*** annegentle has quit IRC22:35
*** lcazares has quit IRC22:35
*** rpjr__ has quit IRC22:36
*** cloudtrainme has quit IRC22:37
*** tonytan4ever has quit IRC22:41
*** lcazares has joined #openstack-meeting-322:42
*** qwebirc92702 has joined #openstack-meeting-322:44
*** qwebirc92702 has quit IRC22:44
*** rpjr___ has quit IRC22:48
*** baoli has quit IRC22:52
*** rpjr_ has joined #openstack-meeting-322:54
*** sdake has quit IRC22:54
*** zz_dimtruck is now known as dimtruck22:56
*** sdague has quit IRC22:57
*** sdake has joined #openstack-meeting-322:58
*** rpjr_ has quit IRC23:06
*** rstarmer has quit IRC23:06
*** rbak_ has joined #openstack-meeting-323:07
*** rbak_ has quit IRC23:07
*** mickeys has quit IRC23:09
*** mickeys has joined #openstack-meeting-323:09
*** rbak has quit IRC23:10
*** banix has joined #openstack-meeting-323:11
*** sdake has quit IRC23:12
*** reedip__ has quit IRC23:16
*** mickeys has quit IRC23:19
*** mickeys has joined #openstack-meeting-323:21
*** lcazares has quit IRC23:22
*** salv-orl_ has quit IRC23:24
*** lcazares has joined #openstack-meeting-323:26
*** cartik has quit IRC23:27
*** banix has quit IRC23:27
*** tqtran has quit IRC23:27
*** lcazares has quit IRC23:27
*** markvoelker has quit IRC23:29
*** kenji-i has joined #openstack-meeting-323:32
*** ddieterly is now known as ddieterly[away]23:33
*** ddieterly[away] has quit IRC23:33
*** ddieterly has joined #openstack-meeting-323:37
*** vtech has quit IRC23:37
*** bpokorny has joined #openstack-meeting-323:40
*** bpokorny_ has quit IRC23:40
*** bpokorny has quit IRC23:46
*** bpokorny has joined #openstack-meeting-323:47
*** ddieterly is now known as ddieterly[away]23:48
*** egallen has quit IRC23:56
*** Sukhdev_ has joined #openstack-meeting-323:57
*** markvoelker has joined #openstack-meeting-323:59

Generated by 2.14.0 by Marius Gedminas - find it at!