Monday, 2015-12-07

*** mbound_ has joined #openstack-meeting-300:06
*** kzaitsev_mb has joined #openstack-meeting-300:09
*** alexpilotti has quit IRC00:16
*** kzaitsev_mb has quit IRC00:22
*** alexpilotti has joined #openstack-meeting-300:23
*** dims has quit IRC00:25
*** dims has joined #openstack-meeting-300:26
*** dims has quit IRC00:35
*** salv-orlando has joined #openstack-meeting-300:37
*** kzaitsev_mb has joined #openstack-meeting-300:38
*** mestery_ has joined #openstack-meeting-300:40
*** mestery has quit IRC00:41
*** mestery_ is now known as mestery00:41
*** salv-orlando has quit IRC00:44
*** kzaitsev_mb has quit IRC00:51
*** kzaitsev_mb has joined #openstack-meeting-300:52
*** hoangcx has joined #openstack-meeting-300:58
*** kzaitsev_mb has quit IRC00:59
*** shaohe_feng has joined #openstack-meeting-301:00
*** mestery has quit IRC01:01
*** mestery has joined #openstack-meeting-301:02
*** shaohe_feng has quit IRC01:10
*** hoangcx has left #openstack-meeting-301:12
*** kzaitsev_mb has joined #openstack-meeting-301:15
*** kzaitsev_mb has quit IRC01:22
*** kzaitsev_mb has joined #openstack-meeting-301:24
*** annp has joined #openstack-meeting-301:29
*** kzaitsev_mb has quit IRC01:29
*** kebray has joined #openstack-meeting-301:30
*** mestery has quit IRC01:30
*** kebray has quit IRC01:31
*** sdake has quit IRC01:31
*** jed56 has quit IRC01:32
*** jed56 has joined #openstack-meeting-301:32
*** tfukushima has joined #openstack-meeting-301:33
*** sdake has joined #openstack-meeting-301:33
*** sweston has quit IRC01:35
*** kebray has joined #openstack-meeting-301:35
*** mestery has joined #openstack-meeting-301:36
*** mestery has quit IRC01:37
*** stanzgy has joined #openstack-meeting-301:37
*** mestery has joined #openstack-meeting-301:38
*** sweston has joined #openstack-meeting-301:40
*** mestery has quit IRC01:40
*** mestery has joined #openstack-meeting-301:40
*** tfukushima has quit IRC01:41
*** mestery_ has joined #openstack-meeting-301:42
*** tfukushima has joined #openstack-meeting-301:44
*** sdake has quit IRC01:50
*** msambol has joined #openstack-meeting-301:54
*** sdake has joined #openstack-meeting-301:55
*** baoli has joined #openstack-meeting-302:06
*** hoangcx has joined #openstack-meeting-302:10
*** hoangcx has left #openstack-meeting-302:10
*** mbound_ has quit IRC02:13
*** ajmiller has quit IRC02:18
*** mestery has quit IRC02:23
*** mestery_ is now known as mestery02:23
*** baoli has quit IRC02:24
*** baoli has joined #openstack-meeting-302:25
*** baoli has quit IRC02:31
*** baoli has joined #openstack-meeting-302:35
*** gcb has joined #openstack-meeting-302:45
*** baoli has quit IRC02:50
*** baoli has joined #openstack-meeting-302:51
*** shwetaap has joined #openstack-meeting-302:52
*** tfukushima has quit IRC02:52
*** klkumar has joined #openstack-meeting-302:53
*** msambol_ has joined #openstack-meeting-302:57
*** msambol has quit IRC02:58
*** shwetaap has quit IRC03:00
*** shwetaap has joined #openstack-meeting-303:00
*** baoli has quit IRC03:01
*** shaohe_feng has joined #openstack-meeting-303:06
*** msambol_ has quit IRC03:07
*** baoli has joined #openstack-meeting-303:19
*** bpokorny has joined #openstack-meeting-303:23
*** baoli has quit IRC03:27
*** Poornima has joined #openstack-meeting-303:27
*** yamamoto has joined #openstack-meeting-303:35
*** gcb has quit IRC03:38
*** gcb has joined #openstack-meeting-303:42
*** btully has joined #openstack-meeting-303:46
*** gcb has quit IRC03:48
*** banix has quit IRC03:48
*** shaohe_feng has quit IRC03:50
*** gcb has joined #openstack-meeting-303:51
*** gcb has quit IRC03:56
*** btully has quit IRC03:56
*** dims has joined #openstack-meeting-304:03
*** lazy_prince has joined #openstack-meeting-304:06
*** msambol has joined #openstack-meeting-304:08
*** gcb has joined #openstack-meeting-304:09
*** msambol has quit IRC04:12
*** dims has quit IRC04:34
*** sdake has quit IRC04:35
*** sdake has joined #openstack-meeting-304:35
*** tfukushima has joined #openstack-meeting-304:37
*** tfukushima has quit IRC04:43
*** kzaitsev_ws has quit IRC04:45
*** sdake has quit IRC04:54
*** sdake has joined #openstack-meeting-304:55
*** sdake has quit IRC04:56
*** btully has joined #openstack-meeting-305:03
*** shaohe_feng has joined #openstack-meeting-305:04
*** shaohe_feng1 has joined #openstack-meeting-305:06
*** shaohe_feng has quit IRC05:09
*** vahidh has joined #openstack-meeting-305:11
*** vahidh has quit IRC05:15
*** shaohe_feng has joined #openstack-meeting-305:23
*** shaohe_feng1 has quit IRC05:24
*** dims has joined #openstack-meeting-305:24
*** tfukushima has joined #openstack-meeting-305:35
*** tfukushima has quit IRC05:37
*** shaohe_feng1 has joined #openstack-meeting-305:39
*** shaohe_feng has quit IRC05:42
*** numans has joined #openstack-meeting-305:45
*** dims has quit IRC05:46
*** amotoki_ has joined #openstack-meeting-305:54
*** sdake has joined #openstack-meeting-305:57
*** tfukushima has joined #openstack-meeting-306:00
*** bpokorny has quit IRC06:01
*** hoangcx has joined #openstack-meeting-306:01
*** stanzgy has quit IRC06:01
*** hoangcx has left #openstack-meeting-306:01
*** killer_prince has joined #openstack-meeting-306:03
*** killer_prince has quit IRC06:05
*** killer_prince has joined #openstack-meeting-306:05
*** lazy_prince has quit IRC06:06
*** irenab has quit IRC06:08
*** lazy_prince has joined #openstack-meeting-306:09
*** msambol has joined #openstack-meeting-306:11
*** killer_prince has quit IRC06:11
*** msambol has quit IRC06:16
*** lpetrut has joined #openstack-meeting-306:26
*** stanzgy has joined #openstack-meeting-306:29
*** amotoki has quit IRC06:30
*** amotoki_ is now known as amotoki06:30
*** dims has joined #openstack-meeting-306:32
*** evgenyf has joined #openstack-meeting-306:35
*** lpetrut has quit IRC06:44
*** dims has quit IRC06:45
*** irenab has joined #openstack-meeting-306:48
*** dims has joined #openstack-meeting-306:52
*** kebray has quit IRC06:55
*** killer_prince has joined #openstack-meeting-307:05
*** lazy_prince has quit IRC07:06
*** lazy_prince has joined #openstack-meeting-307:08
*** jtomasek has quit IRC07:10
*** killer_prince has quit IRC07:10
*** nkrinner has joined #openstack-meeting-307:13
*** dedery has joined #openstack-meeting-307:17
*** jaypipes has joined #openstack-meeting-307:18
*** sdake has quit IRC07:23
*** ifat_afek has joined #openstack-meeting-307:26
*** shaohe_feng1 has quit IRC07:27
*** shaohe_feng has joined #openstack-meeting-307:42
*** btully has quit IRC07:43
*** safchain has joined #openstack-meeting-307:45
*** vahidh has joined #openstack-meeting-307:54
*** klkumar has quit IRC07:54
*** shaohe_feng1 has joined #openstack-meeting-307:55
*** klkumar has joined #openstack-meeting-307:55
*** shaohe_feng has quit IRC07:57
*** vahidh has quit IRC07:59
*** itxaka has joined #openstack-meeting-307:59
*** ttx has joined #openstack-meeting-308:09
*** salv-orlando has joined #openstack-meeting-308:09
*** salv-orlando has quit IRC08:12
*** dedery has quit IRC08:13
*** shakamunyi has quit IRC08:14
*** JeanBriceCombebi has joined #openstack-meeting-308:25
*** MattMan has quit IRC08:26
*** MattMan has joined #openstack-meeting-308:26
*** iyamahat has joined #openstack-meeting-308:26
*** matrohon has joined #openstack-meeting-308:26
*** e0ne has joined #openstack-meeting-308:31
*** klkumar has quit IRC08:31
*** iyamahat has quit IRC08:33
*** klkumar has joined #openstack-meeting-308:34
*** igordcard has joined #openstack-meeting-308:37
*** yamahata has joined #openstack-meeting-308:40
*** evgenyf has quit IRC08:43
*** evgenyf has joined #openstack-meeting-308:53
*** e0ne has quit IRC08:55
*** [1]evgenyf has joined #openstack-meeting-308:57
*** evgenyf has quit IRC08:59
*** [1]evgenyf is now known as evgenyf08:59
*** e0ne has joined #openstack-meeting-309:00
*** egallen has joined #openstack-meeting-309:03
*** e0ne has quit IRC09:03
*** sdake has joined #openstack-meeting-309:11
*** tfukushima has quit IRC09:16
*** tfukushima has joined #openstack-meeting-309:16
*** tfukushima has quit IRC09:17
*** tfukushima has joined #openstack-meeting-309:17
*** egallen has quit IRC09:19
*** egallen has joined #openstack-meeting-309:20
*** salv-orlando has joined #openstack-meeting-309:22
*** shaohe_feng1 has quit IRC09:28
*** shaohe_feng has joined #openstack-meeting-309:29
*** mbound_ has joined #openstack-meeting-309:33
*** jtomasek has joined #openstack-meeting-309:37
*** mbound_ has quit IRC09:39
*** mbound_ has joined #openstack-meeting-309:41
*** mbound_ has quit IRC09:43
*** mbound_ has joined #openstack-meeting-309:43
*** btully has joined #openstack-meeting-309:45
*** dims has quit IRC09:48
*** e0ne has joined #openstack-meeting-309:56
*** MarkAtwood has joined #openstack-meeting-309:58
*** zhenguo has quit IRC10:03
*** evgenyf has quit IRC10:04
*** evgenyf has joined #openstack-meeting-310:05
*** vgridnev has joined #openstack-meeting-310:05
*** JeanBriceCombebi has quit IRC10:11
*** annp has quit IRC10:13
*** egallen has quit IRC10:15
*** salv-orlando has quit IRC10:23
*** evgenyf has quit IRC10:28
*** jlanoux has joined #openstack-meeting-310:29
*** mbound_ has quit IRC10:30
*** mbound_ has joined #openstack-meeting-310:30
*** shwetaap has quit IRC10:33
*** klkumar has quit IRC10:34
*** vahidh has joined #openstack-meeting-310:37
*** jaypipes has quit IRC10:39
*** jaypipes has joined #openstack-meeting-310:40
*** sambetts-afk has quit IRC10:40
*** mbound_ has quit IRC10:41
*** mbound_ has joined #openstack-meeting-310:41
*** vahidh has quit IRC10:41
*** kzaitsev_mb has joined #openstack-meeting-310:43
*** sambetts has joined #openstack-meeting-310:43
*** tellesnobrega_af is now known as tellesnobrega10:43
*** johnthetubaguy has quit IRC10:43
*** klkumar has joined #openstack-meeting-310:46
*** stanzgy has quit IRC10:48
*** johnthetubaguy has joined #openstack-meeting-310:49
*** matrohon has quit IRC11:07
*** sdake has quit IRC11:07
*** neiljerram has joined #openstack-meeting-311:07
*** mbound_ has quit IRC11:07
*** mbound_ has joined #openstack-meeting-311:08
*** igordcard_ has joined #openstack-meeting-311:09
*** igordcard has quit IRC11:11
*** masterbound has joined #openstack-meeting-311:12
*** mbound_ has quit IRC11:12
*** evgenyf has joined #openstack-meeting-311:15
*** davidsha has joined #openstack-meeting-311:16
*** calbers has joined #openstack-meeting-311:18
*** mbound_ has joined #openstack-meeting-311:19
*** yamamoto has quit IRC11:21
*** masterbound has quit IRC11:21
*** shaohe_feng has quit IRC11:21
*** johnthetubaguy has quit IRC11:21
*** johnthetubaguy has joined #openstack-meeting-311:21
*** jed56 has quit IRC11:27
*** tfukushima has quit IRC11:28
*** jed56 has joined #openstack-meeting-311:28
*** masterbound has joined #openstack-meeting-311:31
*** masterbound has quit IRC11:33
*** masterbound has joined #openstack-meeting-311:34
*** Poornima has quit IRC11:34
*** igordcard__ has joined #openstack-meeting-311:35
*** mbound_ has quit IRC11:35
*** ifat_afek_ has joined #openstack-meeting-311:35
*** ifat_afek has quit IRC11:35
*** masterbound has quit IRC11:36
*** mbound_ has joined #openstack-meeting-311:37
*** igordcard_ has quit IRC11:37
*** jtomasek has quit IRC11:42
*** sdake has joined #openstack-meeting-311:45
*** jtomasek has joined #openstack-meeting-311:45
*** jtomasek has quit IRC11:46
*** btully has quit IRC11:46
*** jtomasek has joined #openstack-meeting-311:48
*** klkumar has quit IRC11:51
*** Poornima has joined #openstack-meeting-311:52
*** klkumar has joined #openstack-meeting-311:53
*** alexus is now known as alex_xu11:57
*** salv-orlando has joined #openstack-meeting-312:03
*** salv-orlando has quit IRC12:03
*** salv-orlando has joined #openstack-meeting-312:04
*** yamamoto has joined #openstack-meeting-312:05
*** kzaitsev_mb has quit IRC12:05
*** EvgenyF_ has joined #openstack-meeting-312:07
*** dims has joined #openstack-meeting-312:08
*** EvgenyF__ has joined #openstack-meeting-312:11
*** jaypipes has quit IRC12:12
*** Poornima has quit IRC12:13
*** sdake has quit IRC12:13
*** EvgenyF_ has quit IRC12:14
*** ^Gal^ has quit IRC12:17
*** flaper87 has quit IRC12:17
*** flaper87 has joined #openstack-meeting-312:17
*** doug-fish has joined #openstack-meeting-312:19
*** kzaitsev_mb has joined #openstack-meeting-312:20
*** banix has joined #openstack-meeting-312:22
*** tellesnobrega is now known as tellesnobrega_af12:24
*** tellesnobrega_af is now known as tellesnobrega12:27
*** banix has quit IRC12:29
*** itxaka is now known as itxaka|food12:30
*** baoli has joined #openstack-meeting-312:41
*** rtheis has joined #openstack-meeting-312:41
*** andymaier has joined #openstack-meeting-312:42
*** baoli_ has joined #openstack-meeting-312:43
*** baoli_ has quit IRC12:45
*** baoli_ has joined #openstack-meeting-312:46
*** andymaier has quit IRC12:46
*** baoli has quit IRC12:46
*** andymaier has joined #openstack-meeting-312:47
*** yamamoto has quit IRC12:47
*** pavel_bondar has joined #openstack-meeting-312:47
*** hoangcx has joined #openstack-meeting-312:48
*** hoangcx has quit IRC12:51
*** jed56 has quit IRC12:52
*** jed56 has joined #openstack-meeting-312:52
*** hoangcx has joined #openstack-meeting-312:54
*** hoangcx has quit IRC12:55
*** yamamoto has joined #openstack-meeting-312:57
*** gcb has quit IRC12:58
*** yamamoto_ has joined #openstack-meeting-312:58
*** yamamoto has quit IRC13:02
*** ifat_afek_ has quit IRC13:05
*** sergek_ has joined #openstack-meeting-313:05
*** sergek has quit IRC13:06
*** sergek_ is now known as sergek13:06
*** dedery has joined #openstack-meeting-313:09
*** davidsha has quit IRC13:11
*** calbers has quit IRC13:14
*** davidsha has joined #openstack-meeting-313:20
*** ifat_afek has joined #openstack-meeting-313:21
*** davidsha has quit IRC13:22
*** jed56 has quit IRC13:25
*** jed56 has joined #openstack-meeting-313:26
*** jaypipes has joined #openstack-meeting-313:30
*** matrohon has joined #openstack-meeting-313:36
*** klkumar has quit IRC13:40
*** klkumar has joined #openstack-meeting-313:40
*** calbers has joined #openstack-meeting-313:43
*** neelashah has joined #openstack-meeting-313:45
*** neelashah has quit IRC13:51
*** jaypipes_ has joined #openstack-meeting-313:55
*** jaypipes_ has quit IRC13:58
*** peristeri has joined #openstack-meeting-313:58
*** Chaozhe has joined #openstack-meeting-313:58
*** julim has joined #openstack-meeting-313:59
*** yamamoto_ has quit IRC14:03
*** yamamoto has joined #openstack-meeting-314:04
*** itxaka|food is now known as itxaka14:08
*** yamamoto has quit IRC14:09
*** neelashah has joined #openstack-meeting-314:14
sheeprineSorry guys late to the meeting14:16
*** dims has quit IRC14:16
sheeprineAre there anyone available for the CK meeting ?14:16
sheeprinehuats: gpocentek: ?14:16
*** hogepodge has quit IRC14:17
*** yamahata has quit IRC14:17
*** alaski has quit IRC14:17
ChaozheHi, It`s my first time to attend the CK meeting.14:20
*** neelashah has quit IRC14:21
*** klkumar has quit IRC14:21
*** klkumar has joined #openstack-meeting-314:22
*** mdbooth_ has joined #openstack-meeting-314:22
*** irenab has quit IRC14:22
*** mdbooth has quit IRC14:23
*** bauzas has quit IRC14:23
*** matrohon has quit IRC14:23
*** ttx has quit IRC14:23
*** bauzas has joined #openstack-meeting-314:23
*** mdbooth_ is now known as mdbooth14:23
*** mounica has joined #openstack-meeting-314:24
*** matrohon has joined #openstack-meeting-314:24
*** ttx has joined #openstack-meeting-314:24
*** banix has joined #openstack-meeting-314:25
ChaozheI'm trying to figure out every details about CK and wanna take an active part in it.  :- )14:26
*** lblanchard has joined #openstack-meeting-314:26
*** rbak has quit IRC14:26
*** pballand has quit IRC14:29
*** lazy_prince has quit IRC14:31
*** kashyap has left #openstack-meeting-314:31
*** yamahata has joined #openstack-meeting-314:32
*** superdan is now known as dansmith14:32
*** dims has joined #openstack-meeting-314:34
*** msambol has joined #openstack-meeting-314:35
sheeprineChaozhe: Nice14:39
sheeprineFirst I've got a question for you, is the current meeting time fine for you or should it be rescheduled?14:39
sheeprineBecause most of the core contributors are near UTC time, so the meeting time was defined according to this14:40
sheeprineBut most of the new contributors seems to be situated in Asia.14:40
ChaozheIt's fine for me, that's ok.14:40
*** kebray has joined #openstack-meeting-314:41
*** yamamoto has joined #openstack-meeting-314:41
*** ajmiller has joined #openstack-meeting-314:42
sheeprineWhat's your current time?14:42
*** masterbound has joined #openstack-meeting-314:42
Chaozhe22:40 in night14:43
*** mbound_ has quit IRC14:43
sheeprineOk, I'll send a mail on the ML to see if we need to change the meeting hour14:44
sheeprinebecause we can easily move it to something like 10 UTC14:44
*** evgenyf has quit IRC14:44
sheeprinewhich will be easier for you to attend14:44
ChaozheOther weekly meeting like nova is later 2 hours, CK's meeting time is better for me.14:44
sheeprineI see ;)14:44
*** baohua has joined #openstack-meeting-314:45
*** EvgenyF__ has quit IRC14:45
sheeprineSince we are only two, maybe we can continue on #cloudkitty?14:45
Chaozheok14:45
*** numans has quit IRC14:47
*** mounica has quit IRC14:47
*** EvgenyF__ has joined #openstack-meeting-314:48
*** vhoward has joined #openstack-meeting-314:48
*** ajmiller has quit IRC14:48
*** evgenyf has joined #openstack-meeting-314:48
*** ctlaugh has joined #openstack-meeting-314:49
*** gcb has joined #openstack-meeting-314:50
*** dedery has quit IRC14:53
*** alaski has joined #openstack-meeting-314:55
*** mwagner_lap has quit IRC14:57
*** neelashah has joined #openstack-meeting-314:57
*** masterbound has quit IRC14:58
*** nelsnelson has joined #openstack-meeting-314:58
*** mbound_ has joined #openstack-meeting-314:58
*** yamamoto has quit IRC14:59
*** carl_baldwin_ has joined #openstack-meeting-315:00
*** dims has quit IRC15:02
*** yamamoto has joined #openstack-meeting-315:03
*** sdake has joined #openstack-meeting-315:04
*** irenab has joined #openstack-meeting-315:05
*** absubram has quit IRC15:08
*** sdake has quit IRC15:09
*** kzaitsev_mb has quit IRC15:11
*** btully has joined #openstack-meeting-315:12
*** yamamoto has quit IRC15:13
*** banix has quit IRC15:13
*** hogepodge has joined #openstack-meeting-315:14
*** kebray has quit IRC15:15
*** sdake has joined #openstack-meeting-315:15
*** baohua has quit IRC15:16
*** jpomeroy has joined #openstack-meeting-315:16
*** kebray has joined #openstack-meeting-315:16
*** galstrom_zzz is now known as galstrom15:18
*** shwetaap has joined #openstack-meeting-315:20
*** rbak has joined #openstack-meeting-315:20
*** vijendar has joined #openstack-meeting-315:20
*** sigmavirus24_awa is now known as sigmavirus2415:22
*** zz_dimtruck is now known as dimtruck15:31
*** kzaitsev_mb has joined #openstack-meeting-315:31
*** ifat_afek has quit IRC15:33
*** julim has quit IRC15:37
*** nkrinner has quit IRC15:37
*** shwetaap has quit IRC15:38
*** smoriya_ has joined #openstack-meeting-315:40
*** julim has joined #openstack-meeting-315:40
*** shwetaap has joined #openstack-meeting-315:40
*** jaypipes has quit IRC15:41
*** vgridnev has quit IRC15:44
*** Sukhdev has joined #openstack-meeting-315:45
*** ifat_afek has joined #openstack-meeting-315:45
*** iyamahat has joined #openstack-meeting-315:48
*** galstrom is now known as galstrom_zzz15:55
*** EvgenyF__ has quit IRC15:59
*** evgenyf has quit IRC15:59
jklare#startmeeting openstack_chef16:00
openstackMeeting started Mon Dec  7 16:00:08 2015 UTC and is due to finish in 60 minutes.  The chair is jklare. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_chef)"16:00
openstackThe meeting name has been set to 'openstack_chef'16:00
jklarehi16:00
calberso/16:00
jklarei have no topics for today, so if you guys want to discuss anything, just go ahead16:01
*** galstrom_zzz is now known as galstrom16:04
sc`i don't have anything. the queue looks light, aside from the ongoing refactoring16:05
jklareyeah, we hope to get alle the patches up before christmas16:06
*** mwagner_lap has joined #openstack-meeting-316:06
jklareso everybody can use their holiday to review them ;)16:06
sc`\o/16:06
jklareok, i guess we can end the meeting now and discuss in our channel if anything important comes up16:07
jklare#endmeeting16:08
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:08
openstackMeeting ended Mon Dec  7 16:08:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-12-07-16.00.html16:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-12-07-16.00.txt16:08
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-12-07-16.00.log.html16:08
sc`short and sweet :)16:08
*** pballand has joined #openstack-meeting-316:09
*** Fdaisuke has joined #openstack-meeting-316:10
*** absubram has joined #openstack-meeting-316:13
*** jaypipes has joined #openstack-meeting-316:15
markvanhi16:17
*** devananda has quit IRC16:18
*** kzaitsev_mb has quit IRC16:20
*** devananda has joined #openstack-meeting-316:21
*** kzaitsev_mb has joined #openstack-meeting-316:24
*** kzaitsev_mb has quit IRC16:25
*** kzaitsev_mb has joined #openstack-meeting-316:25
*** bpokorny has joined #openstack-meeting-316:30
*** armax has quit IRC16:31
*** kevinbenton has quit IRC16:31
*** kevinbenton has joined #openstack-meeting-316:31
*** neiljerram_bb has joined #openstack-meeting-316:34
*** calbers has quit IRC16:35
*** alex_xu has quit IRC16:35
*** vgridnev has joined #openstack-meeting-316:36
*** rbak has quit IRC16:37
*** ajmiller has joined #openstack-meeting-316:38
*** eliqiao has quit IRC16:39
*** eliqiao has joined #openstack-meeting-316:39
*** neiljerram_bb has quit IRC16:39
*** Guest18099 is now known as redrobot16:43
*** alex_xu has joined #openstack-meeting-316:43
*** Swami has joined #openstack-meeting-316:45
*** jtomasek has quit IRC16:46
*** rloo|afk has joined #openstack-meeting-316:47
*** rloo|afk is now known as rloo16:48
*** carl_baldwin_ is now known as carl_baldwin16:48
*** david-lyle has joined #openstack-meeting-316:49
*** jlanoux has quit IRC16:50
*** lucasagomes has joined #openstack-meeting-316:51
*** sinval has joined #openstack-meeting-316:52
*** calbers has joined #openstack-meeting-316:54
*** rbak has joined #openstack-meeting-316:54
*** calbers has quit IRC16:54
*** mariojv has joined #openstack-meeting-316:56
*** masterbound has joined #openstack-meeting-316:57
*** dtantsur has joined #openstack-meeting-316:58
*** kzaitsev_mb has quit IRC16:58
*** yuriyz has joined #openstack-meeting-316:59
*** mjturek1 has joined #openstack-meeting-316:59
*** vahidh has joined #openstack-meeting-317:00
*** pc_m has joined #openstack-meeting-317:00
jroll#startmeeting ironic17:00
openstackMeeting started Mon Dec  7 17:00:23 2015 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
*** pas-ha has joined #openstack-meeting-317:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
mjturek1\o17:00
openstackThe meeting name has been set to 'ironic'17:00
pas-hao/17:00
vdrok\o/17:00
jrollhey there everyone :)17:00
lucasagomeso/17:00
cinerama\o17:00
*** mbound_ has quit IRC17:00
yuriyzo/17:00
devanandao/17:00
smoriya_o/17:00
jrollas always our agenda is here:17:00
dtantsuro/17:00
jroll#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting17:00
Fdaisukeo/17:00
rlooo/17:00
*** liliars has joined #openstack-meeting-317:00
mariojv\o17:01
NobodyCamo/17:01
jrolllet's jump right in!17:01
jroll#topic Announcements / Reminders17:01
*** openstack changes topic to "Announcements / Reminders (Meeting topic: ironic)"17:01
rloosplash...17:01
jrolla couple of things here:17:01
*** wanyen has joined #openstack-meeting-317:01
jroll1) ironic 4.2.2 was released friday with a very important security fix, thanks to brad morgan for reporting that17:01
sambettso/17:01
jroll2) ironic 4.3.0 was released today with a whole bunch of awesomeness, including that bug fix17:02
jrollemail announcements coming today for those17:02
*** [1]cdearborn has joined #openstack-meeting-317:02
lucasagomesnice17:02
*** rpioso has joined #openstack-meeting-317:02
[1]cdearborno/17:02
jroll3) tripleo CI jobs are coming back - please do pay attention to those17:02
rpiosoo/17:02
rlooclap clap. (what took so long?)17:02
jrollanyone have other announcements or questions on those?17:02
rloojroll: ^ question on 217:02
rloojroll: anything we could have done to speed up the release?17:03
*** mtanino has joined #openstack-meeting-317:03
rloojroll: i mean from the time the security bug patch was out etc. not sure what happened.17:03
devanandaI didn't push the release button until after the security fix had merged, and that got stuck on a devstack change for about 24hrs17:03
jrollah.17:03
krtayloro/17:03
sambettsI have a question on 2) too, where is that going to be stored, stable/4.3.0 ??17:04
jrollyeah, we had a bug in devstack where the erase_devices clean step (which is SUPER SLOW in devstack) wasn't configured to not run17:04
jrolland so when we fixed the bug to actually run clean steps, it blew up in the gate17:04
rloojroll: oh, i thought that devstack-turn-off-clean-step got merged last Thurs. guess it took longer :-(17:04
jrollsambetts: no stable branch for the intermediate releases, just a tag. stable/mitaka will be a thing at the end of the cycle17:04
lucasagomesyeah, and we need to figure out a way to test the clean steps on gate so we don't have another bug like that sneaking in the code again17:05
lucasagomesdo we have a bug opened for that ^ ?17:05
krotschecko/17:05
jrollrloo: well, the gate was slow, so the patch merged friday. and then release team had questions about the version number, so release got there today17:05
rloolucasagomes: ++ i was just going to ask!17:05
devanandarloo: the gate queue was fairly long and some rechecks for other issues wre needed17:05
jrolllucasagomes: I don't believe so, mind filing one?17:05
yuriyz+1 maybe partial cleaning on DS17:05
*** thrash has joined #openstack-meeting-317:05
lucasagomesjroll, I will do17:05
rloojroll, devananda: ok, not much we could have done then. should be smoother next time :)17:05
jrollthanks dude17:05
lucasagomesno problemo!17:06
jrollrloo: hope so :D17:06
jrollanything else here?17:06
jroll#topic subteam status reports17:06
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"17:06
jrollas always, reports are here:17:06
jroll#link https://etherpad.openstack.org/p/IronicWhiteBoard17:06
*** marcusrafael has joined #openstack-meeting-317:06
jrollI'll give folks a minute to review those, or fill them out :P17:07
davidlenwello/17:07
rloowhat's the critical bug?17:07
*** kzaitsev_mb has joined #openstack-meeting-317:07
dtantsurrloo, IPA gate breakage17:07
dtantsurhttps://bugs.launchpad.net/ironic-python-agent/+bug/152275617:08
openstackLaunchpad bug 1522756 in ironic-python-agent "pyudev 0.18 changed exception for from_device_file, breaking backward compatibility (and IPA unit tests)" [Critical,In progress] - Assigned to Dmitry Tantsur (divius)17:08
rloodtantsur: ok, thx. does it 'just' need reviews?17:08
jrollI've got a +2 on ^17:08
dtantsurrloo, yes, and backport to liberty17:08
jrollsimple change, we should get that landed17:08
dtantsurI'm trying to communicate to upstream person that this thing should not repeat too often17:08
jroll\o/ for tempest plugin stuff in ironic17:09
rloodtantsur: guess that's why we have tests :)17:09
jrollI'm also excited to see grenade and devstack code move to our tree17:09
jroll\o/ for bifrost inspection support17:10
jrollkrtaylor: updating the third party CI spec this week? I'd like to land that asap17:10
JayFdtantsur: I added a comment to the github issue asking him not to move the discussion to email. Hopefully having >1 person paying attention will help them understand how much we don't want that to break us again :)17:10
rlooi think nova spec freeze was last week? does anyone know which nova specs got approved that are related to ironic?17:10
krtaylorjroll, me too, I have been very sick17:10
krtaylorjroll, I'll have a new one within the hour17:11
dtantsurJayF, yeah, I've reached him/her via email just because I expected an internal email to speed the process a bit (and it really did)17:11
jrollkrtaylor: oh, I'm sorry :( I could update it too if you aren't better yet17:11
krtaylorI'm almost done17:11
dtantsurJayF, I also suggested my help, if needed17:11
lucasagomesrloo, yes the freeze was last week... I will check the ironic spec17:11
jrollrloo: nova-specs that we care about right now are 1) multiple compute host, and 2) the networking support stuff17:11
rloowrt CI requirements being communicated with vendor teams -- all the vendors that have intree drivers in ironic?17:11
jrollrloo: all of them that we could find contact info for (and it also went to dev list)17:12
krtaylorrloo, all that are listed in the ci etherpad17:12
* krtaylor finds that link17:12
jrollrloo: thingee will be keeping on top of that to make sure they are notified - voicemails and all. doing everything he can short of serving them court papers :P17:13
rloojroll, krtaylor: ok, that's what i wanted to know. thx!17:13
jrollnp :)17:13
jrollso, looking at these, we still have a ton of work to do this cycle. we're making good progress but need to keep going hard on all of our priorities17:13
jrollthanks to everyone for the great work so far, and please do keep it up :)17:14
jrolllet's be sure to stay on track and not get distracted by all the other shiny things17:14
*** peristeri has quit IRC17:14
jrollanything else on the subteam reports?17:15
dtantsur.. and shiny gate breakages :D17:15
lucasagomeshope not17:15
krotscheckAll the webclient things are in the etherpad if anyone has questions :)17:15
rloowrt docs, i'm curious to know what 'not in the scope for official page'. i hope they are thinking about how to include docs from all projects...17:15
*** gcb has quit IRC17:15
jrollrloo: I'm going to send a nice long email about that today - sounds like they are meant to cover the "base" openstack services17:16
rloojroll, liliars: thx for looking into it and pushing for them to think of the rest of the noncore services17:16
dtantsurthen "developer" in http://docs.openstack.org/developer/ironic/ is not entirely true, right?17:16
liliarsrloo: apparently only 'core projects'17:17
jrolldtantsur: right, need to re-org and re-think some things17:17
liliarsrloo: yeah np, will keep digging :)17:17
lucasagomesouch17:17
dtantsurditto for http://docs.openstack.org/developer/ironic-inspector/17:17
rloodtantsur: no, developer is not entirely true. when we put together our docs, it was meant to be temporary until we graduated and our docs were included with 'the rest' of the docs :-(17:17
jrollI think the real issue here is that the docs project hasn't fully embraced the big tent yet (and with good reason, it's hard)17:17
dtantsurthey'll have to double the number of people, I guess...17:18
devanandaI had some conversations with docs team in vancouver, but we haven't followed through much from either side on those changes17:18
rloooooo, i see a cross-project spec coming out of this :D17:18
devanandathey don't plan to grow support within the docs group to write or maintain docs for every project in the big tent17:18
jrollrloo: yeah, basically :)17:18
devanandabut like other cross project things ,they intend(ed) to grow tooling to enable other projects17:18
jrollshall we move on? we aren't going to solve this problem today :P17:19
rlooi don't expect the docs team to write the docs but i would like some way to get our stuff integrated.17:19
rlooyup, let's move on :)17:19
jrollyeah, that's my goal as well17:19
*** matrohon has quit IRC17:19
jrollcools17:19
devanandarloo: agreement on that was basically the outcome 8mo ago17:19
jroll#topic notifications spec - use cases and configurability17:19
*** openstack changes topic to "notifications spec - use cases and configurability (Meeting topic: ironic)"17:19
jroll#link https://review.openstack.org/#/c/248885/17:19
jrollmariojv: this is you17:19
jrollfor folks listening, this is a stuck spec17:19
rloowhat's the 'stuck' part?17:19
mariojvhi, yes - there was a discussion brought up in irc friday about the different use cases that people would use when notifications are added to ironic17:20
jrollthat's what mariojv is going to tell us :)17:20
mariojvthe important part we were discussing is the payload section (L94)17:20
*** Chaozhe has quit IRC17:20
mariojvthe question is basically what we would want to send in the payload of a notification for something like node state changes17:20
*** aarefiev22 has joined #openstack-meeting-317:21
devanandaeg, the entire (santized) node object vs. merely the fields relevant to that event17:21
mariojvright ^ and there are 2 different use cases that we've considered so far17:21
rloomariojv: for state changes, original prov/target_prov states, new prov/target_prov states. do we need to send the entire node object?17:21
lucasagomesI thought we would send only the relevant fields (previous state, new state, datetime etc)17:21
* jroll apologizes for not having a chance to catch up on context here17:22
* lucasagomes does the same as jroll17:22
jrollbtw, the friday discussion is here:17:22
jroll#link http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2015-12-04.log.html#t2015-12-04T21:32:3417:22
devanandaI think it boiled down to who the intended consumer is. A) a logging or debugging system; B) another service that will take some action based on the event17:22
mariojvone case is where we would want to keep a point in time snapshot of a node as it goes through changes, so that we could store that and keep it in something like elasticsearch to track anomalous behavior17:22
JayFThe crux is: If you want to use the notification for debugging, you want as much of the node object as possible (with secrets hidden)17:22
rloowhat's the purpose of notification. to notify. not to contain all info needed for debugging?17:23
mariojvanother cases is B, like devananda mentioned17:23
jrolldevananda: I agree with that assertion17:23
JayFif you're using the notification as a "trigger" for other services, you want to keep it slim and only include desired fields17:23
rloodoes it make sense to make it configurable? (the payload info?)17:23
dtantsurI'd say that for production we need as small payload as possible, so that we don't overload anything (both queue and consumers)17:24
jrollI'd prefer if the payload wasn't configurable, that feels like a world of pain17:24
devanandamy assertion is that our primary consumers of this feature are ironic-inspector and nova, and therefor it is (B)17:24
devanandajroll: ++17:24
devanandadtantsur: ++17:24
lucasagomesyeah configuring the payload can be painful because of the versioning etc17:24
*** mounica has joined #openstack-meeting-317:24
devanandascaling rabbit is one of hte biggest challenges operators have17:25
rloook, nix on configurability.17:25
*** zz_john5223 is now known as john522317:25
devanandalet's not put more large objects on that bus17:25
rloothen I agree with dtantsur, small payload.17:25
mariojv++17:25
lucasagomesbut I think that as for notification we should keep it small as possible17:25
*** salv-orl_ has joined #openstack-meeting-317:25
dtantsure.g. for state change I'd send 1. UUID, 2. previous state, 3. new state, or something like that (maybe even without #2)17:25
jrollso "small payload" means just the relevant changes to a given object?17:25
rloofor debugging, one should look at the logs, no?17:25
lucasagomesdtantsur, yeah, and time that occurred17:25
vdrokB makes more sense to me too17:25
lucasagomesjroll, IMO yes17:25
dtantsurlucasagomes, time is always included in the notification IIRC17:25
mariojvdtantsur: i think we would want #217:26
lucasagomesright yeah it should17:26
jrollto be clear, there are debugging tools that people use today that rely on nova notifications17:26
jrollthat are SUPER useful17:26
jrolland those have a ton of data17:26
devanandadtantsur: old and new state are both important to include. we can't assume a listener has processed every message sequentially17:26
lucasagomesjroll, nova sends the whole object?17:26
mariojvjroll: that's right. something like instance.create has a lot of data17:26
jrolllucasagomes: I'm not sure if it's the whole object, but it's a significant amount17:26
devanandaso instance.create is an interesting example. it makes sense for that to include a lot of data about the instance that was created17:27
rloomariojv had provided this link wrt what nova does: https://wiki.openstack.org/wiki/SystemUsageData#compute.instance.create..7Bstart.2Cerror.2Cend.7D:17:27
*** e0ne has quit IRC17:27
mariojvi don't think it's the entire object (would have to check), but it has things like host, image url, tenant, flavor id17:27
devanandawhat abour instance.pause ?17:27
devanandamariojv: all of that is related to the instance creation, so that makes sense17:27
jrollmariojv: got an example instance.create handy?17:27
lucasagomesdevananda, right, yeah it sounds like it should send the whole instance as it was created17:27
jrollmariojv: sorry, instance.update17:27
*** pc_m has quit IRC17:27
lucasagomesbut for things smaller, actions, suchs as instance is now deployed17:27
mariojvjroll: not a raw one, would have to sanitize a bunch of things17:27
lucasagomesnova does send almost everything ?17:27
mariojvthis is another interesting example: https://wiki.openstack.org/wiki/SystemUsageData#compute.instance.exists:17:28
jrollmariojv: PM it to me and I'll scrub real quick?17:28
mariojvjroll: sure17:28
jrolloh, there's the schema17:28
*** salv-orlando has quit IRC17:28
mariojvif you look in instance.exists, i think there are a lot of fields that an operator may find useful that aren't directly related to just notifying external services that instances exist17:28
jrollright, so instance.update has a decent amount of data17:28
jrollBUT17:29
jrollwe don't need to be the same as nova17:29
jrollif we can provide the diff, so to speak, that may be good enough17:29
rloomariojv: but does instance.exists provide 'everything' that is available about the instance?17:29
*** pc_m has joined #openstack-meeting-317:29
mariojvi agree with jroll that we don't need to be the same as nova - i just wanted to bring up the point that it's much more than the minimal needed info in a lot of cases17:29
mariojvrloo: i don't think it's everything, but i would have to check more in depth17:30
jrollso I agree we should try to keep it small, but relevant17:30
jrolland not the entire node object17:30
rloomariojv: i am wondering if what we return for an eg 'ironic-node-show' would be enough + any other info pertaining to the event17:30
jrolland I think what is relevant depends on each notification17:30
jrolleach notification type*17:30
jrollso maybe we handle these case by case17:31
mariojvrloo: i think that would be enough, and i agree it depends on the notification17:31
lucasagomesjroll, ++ yeah it sounds like we should see what notifications are we going to start sending at first17:31
jrolland if a user finds it lacking, we talk about adding to it17:31
mariojvfor .error notifications, we would probably want more than a common notification that occurs when things are normla17:31
lucasagomesand see what fields are relevant to each17:31
rlooright, so we always return a minimum set.17:31
*** msambol has quit IRC17:31
jrollwe have versions for a reason \o/17:31
jrollmariojv: ++17:31
jrollso, does anyone violently disagree with NOT having the entire node object in the payload?17:32
rlooi mean, we're talking about emitting events, but an eg 'ironic node-show' you should be able to know what is going on with that node from that info.17:32
*** amotoki has quit IRC17:32
mariojvso in the spec, we can outline some guidelines. 1) for "normal events", send a minimal amount of data that indicates what changed 2) for anomalous events, send enough information to allow debugging with an external tool to occur17:32
jroll+117:32
sambettssounds good to me17:32
rloowho wanted the entire node object and are they here/ok with what we've discussed?17:32
mariojvi think it would be painful to have every notification outlined beforehand in a spec. rloo: i think that's enough information - it's not really "minimal" but it's not everything either17:33
jrollI feel like mariojv was the one that wanted the entire node object :)17:33
rlooha ha. ok, we're good then!17:33
*** Sukhdev has quit IRC17:34
mariojvjroll: yeah, i put it there initially because then notification versions would update automatically if additional fields we wanted were added to the node object17:34
devanandamariojv: by 'anomalous' you mean an error state?17:34
jrollmhm17:34
mariojvbut i think the disadvantages like overloading a rabbit queue would outway having to maintain notification and node object versions separately17:34
mariojvdevananda: yes17:34
mariojv*outweigh17:34
devanandamariojv: that isn't good -- it will break consumers if a single notification class sometimes has different information17:34
devanandaeg, the notification for provision state change: it must always have the same payload (for the same version)17:35
jrolldevananda: this would be something like bearmetal.node.error17:35
devanandait can't have more data if the new state is error17:35
dtantsuraren't errors actually part of node transitions?17:35
devanandajroll: there isn't an "error" notification proposed, afaik17:35
devanandadtantsur: exactly17:35
mariojvdevananda: it can still be versioned, we could have different versioned objects (with version included in payload) for .error and .state_change or whatever we call the normal one17:35
jrolldevananda: there isn't a node state transition proposed, either17:35
devanandamariojv: nooo :(17:35
devanandamariojv: versions are not a way to indicate type17:36
dtantsurdevananda, we can have "error_text" field with None value is the transition is not an error17:36
jrolla "deploy error" would be, AIUI, a state_change notification and an error notification17:36
*** yamahata has quit IRC17:36
jrollnot one with extra data17:36
*** klkumar has quit IRC17:36
devanandajroll: that doesn't seem to  be what mariojv was proposing, though17:36
*** iyamahat has quit IRC17:36
jrolldevananda: that's how I interpreted it17:36
mariojvdevananda's right, i was thinking we just send different data in different cases17:37
*** rbak_ has joined #openstack-meeting-317:37
rloomariojv: you mean like what nova does?17:37
jrolloh17:37
jrollin the interest of time, can we solve the anomalous case in the spec?17:37
jrollwhere we have more than 30 minutes to flesh it out?17:37
mariojvi do prefer the idea of having a separate error notification though17:37
mariojvrloo: yes17:37
devanandafwiw, I do not feel that error is an anomalous case17:37
devanandabut let's continue in the spec, I guess17:37
mariojvi'm fine with that jroll17:37
jrollcool17:38
jrollthank you17:38
jrollwe're mostly agreed here, I'm going to move on because this next topic is fun even if I haven't formed all my thoughts on it yet17:38
dtantsur:)17:38
jroll#topic stop using milestones and/or blueprints?17:39
*** openstack changes topic to "stop using milestones and/or blueprints? (Meeting topic: ironic)"17:39
jroll#link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081435.html17:39
* jroll hands dtantsur the microphone17:39
dtantsurthanks17:39
*** rbak has quit IRC17:39
dtantsurtl;dr: we're on our own with blueprints, release team does not do anything with them any more17:39
dtantsurs/blueprints/milestones17:39
dtantsurcreate, close, target - we have to do it ourselves, if we feel like17:40
dtantsurI personally don't (for ironic-inspector), and I'm not sure we want it for ironic17:40
dtantsurnext thought is if we don't use milestones, it reduces value for blueprints17:40
rlooI'd actually like to see all/most projects doing a similar thing, whatever 'similar' is.17:40
dtantsurI've heard that neutron has replaced blueprints with bugs with "RFE" in title17:41
dtantsursambetts, right ^^17:41
*** rbak_ has quit IRC17:41
dtantsurso we have to decide, whether we continue doing the same thing without any motivation from the release team17:41
JayFjroll: mariojv rloo: I was the one who originally was supporting full node objects -- I'm very OK with this outcome just wanted to make sure we acknowledged the use cases we were supporting/rejecting17:41
jrollhave they fully replaced BPs with RFEs, or only some?17:41
lucasagomesrloo, right, and if there's no standard yet we should at least try to do the same between ironic projects (inspector, ironic, bifrost etc...)17:41
rloolucasagomes: ++17:42
rlooJayF: great!17:42
*** rbak has joined #openstack-meeting-317:42
lucasagomesI think the release liasons for the projects should talk and decide what would be best?17:42
lucasagomeswould it be possible to have meeting with all/most of them?17:42
dtantsurlucasagomes, well, as to inspector, I'd like to stop doing it, as it consumes my time without a big benefit17:43
dtantsurunless someone from inspector team would volunteer, which I doubt17:43
* rloo never could figure out (or probably didn't care) what the blueprint/milestones/etc were for and how necessary they were.17:43
dtantsurjroll, not sure, that's what sambetts told me. I still see some mitaka blueprints on their page17:43
jrollso, I agree, I don't think blueprints or milestones in launchpad add any value, and they are a pain17:43
lucasagomesdtantsur, right, we are aiming to have a standard across project right?17:43
lucasagomesI think you guys should push this idea forward since it's time consuming with no real benefits17:44
*** rbak has quit IRC17:44
jrollbut there is value in doing the same thing as other projects17:44
dtantsurlucasagomes, well... release team used to set such standard, now they stopped doing that17:44
dtantsurlucasagomes, jroll, re doing the same thing: we're not following the same release pattern, for example..17:44
dtantsur(we only match swift)17:44
jrolldtantsur: I'm thinking from a contributor's perspective - someone wants to propose a feature, how do they do so?17:45
devanandaBP have provided a few benefits, with a lot of overhead, but the only one left seems to be the link between gerrit reviews and a BP17:45
dtantsurjroll, but with RFE in the title, which is want they already do, by the way17:45
rlooOne thing that was useful?( or what it) was that at at release, there was a link where you could see which bps were completed. now we have reno, which doesn't contain links to anything like specs17:45
dtantsurs/want/what/17:45
devanandaeg, if I put "blueprint: foo" in a commit message, a link to that review gets added to the BP page17:45
dtantsurdevananda, the same works for bugs17:45
devanandadtantsur: totally does :)17:45
lucasagomesdevananda, yeah that's useful, but I'm ok not having it if that's the only benefit17:46
dtantsurrloo, it's out fault that we don't put links to specs in reno notes ;)17:46
cineramawe (bifrost) use blueprints17:46
devanandajust saying that's the only thing we're using it for right now, I think17:46
devanandacinerama: are you using specs as well?17:46
cineramano17:46
jrolldtantsur: do you mean that casual contributors already propose a feature by filing a bug? (I agree, many do)17:46
rloodtantsur: oh, yes, i just want to make sure we recognize what we 'got' with the old/existing system, and what we'll get with the new way.17:46
dtantsurjroll, yes, they do17:46
jrollright, ok17:46
*** rbak has joined #openstack-meeting-317:47
rlooit is true that it isn't always clear if something is a feature or a bug. and then, whether it is a big enough feature that requires a spec or not.17:47
devanandajroll: I have seen many new contributors start with a very small BP proposal and get "stuck" at that point17:47
pc_mFYI, here is what Neutron is doing  http://lists.openstack.org/pipermail/openstack-dev/2015-December/081458.html17:47
jrolldevananda: yeah, I see both17:47
dtantsurright, we get a lot of bugs with title "XXX does not support YYY" or "XXX does not have YYY"17:47
lucasagomespc_m, thanks17:47
lucasagomes#link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081458.html17:47
dtantsurpc_m, thanks a lot, that matches what I was told17:48
pc_mThey've been doing RFEs and if it is complex, follow up with blueprint.17:48
*** armax has joined #openstack-meeting-317:49
jrollright, so I don't see much reason not to do that same thing - does anyone disagree?17:49
lucasagomesI think it worth trying17:49
dtantsur++17:50
lucasagomesbut also talk to the neutron release liason see how it's going for them17:50
devanandajroll: what do we do with all the currently-registered BPs?17:50
pc_m#link http://docs.openstack.org/developer/neutron/policies/blueprints.html for details on RFEs and BPs17:50
jrolldevananda: move them? kill with fire?17:50
dtantsurI'd convert them to RFE's and CC the original reporter17:50
devanandayou've been cleaning those up, I htink17:50
devanandabut there are still 144 open BPs17:51
jrolldevananda: I started to and lost most of my hope for the world17:51
devanandajroll: welcome to my world :)17:51
lucasagomes144 damn17:51
dtantsurO_o17:51
*** alexpilotti has quit IRC17:51
rloohow did neutron xsition to the new way?17:51
jrollidk, I can chat more about it with mestery and armax17:52
lucasagomes++17:52
pc_mIIRC, they started to do RFEs and BPs were optional. Did it at the start of a release.17:53
*** shwetaap1 has joined #openstack-meeting-317:53
devanandajroll: fyi, we can disable blueprints in LP, if or when some transition is complete17:53
jrollindeed17:53
pc_mSo was a period of time where you could have BPs.17:53
devanandagrace / deprecation period makes sense17:54
jrollok, so should we agree to give it a try?17:54
devanandapc_m: about how long was that? a full cycle, or ..?17:54
* dtantsur will also disable blueprints for inspector eventually, if nobody from the team volunteers for keeping them17:55
jrollor I should talk to neutron folks more, or?17:55
pc_mdevananda: I think they started the RFEs in Liberty.17:55
*** banix has joined #openstack-meeting-317:55
pc_mTalk to mestery. He'll know.17:55
jrollcool17:55
jrollthanks for the info pc_m :)17:56
pc_mjroll: sure17:56
*** shwetaap has quit IRC17:56
jrollok, cool, I'll talk to people and reply to dtantsur17:56
jrollto dtantsur's email, I should say17:57
dtantsurthanks! :)17:57
jrollthank you for bringing it up :)17:57
jroll#topic open discussion17:57
jrollhave about two minutes left if anyone has something quick17:57
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:57
smoriya_I have one thing17:57
dtantsurjroll, any updates on the virtual midcycle planning?17:57
dtantsurhmm, go ahead, smoriya_17:58
jrolldtantsur: nope, nothing yet17:58
*** sdake has quit IRC17:58
smoriya_thanks, dantsur17:58
*** iyamahat has joined #openstack-meeting-317:58
smoriya_I'd like ask you to review https://review.openstack.org/#/c/200496/17:58
smoriya_This is the spec for boot from volume support17:58
lucasagomesquick request, we need to make the json fields indexable in the database to build the filter/claim api etc... So if you are interested on that please take a look https://review.openstack.org/#/c/253605/17:58
smoriya_To support boot from volume, we need to enhance both Ironic and Nova(ironic driver)17:58
*** shwetaap1 has quit IRC17:58
smoriya_That means we need to get the blueprint in Nova approved.17:59
dtantsursmoriya_, on my list, will try to get to it tomorrow (it's evening for me)17:59
smoriya_as you know nova-spec freeze is last week17:59
* lucasagomes needs input from people that understand databases better17:59
smoriya_but there is an exception process that close 12/11.17:59
smoriya_dtantsur: great! thanks!17:59
smoriya_I'd like to propose nova's blueprint as an exception17:59
*** kzaitsev_mb has quit IRC17:59
*** shwetaap has joined #openstack-meeting-317:59
jrollI don't think we'll be able to finish that feature in nova this cycle, even if the ironic spec lands today17:59
smoriya_I talked with johnthetubaguy and he said that we don't need spec for it in Nova but need blueprint approved.18:00
jrollbut I'd love to get that spec done anyway and start working on it18:00
mariojvfg18:00
jrollalright, out of time. thanks everyone!18:00
jroll#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Dec  7 18:00:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-12-07-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-12-07-17.00.txt18:00
*** yuriyz has left #openstack-meeting-318:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-12-07-17.00.log.html18:00
*** lucasagomes has left #openstack-meeting-318:00
*** sinval has left #openstack-meeting-318:01
*** dtantsur has left #openstack-meeting-318:01
*** pas-ha has left #openstack-meeting-318:01
*** [1]cdearborn has left #openstack-meeting-318:01
*** pc_m has left #openstack-meeting-318:01
*** rbak has quit IRC18:02
*** ifat_afek has quit IRC18:02
*** alexpilotti has joined #openstack-meeting-318:02
*** rbak has joined #openstack-meeting-318:03
*** thrash has left #openstack-meeting-318:03
*** wanyen has quit IRC18:04
*** masterbound has quit IRC18:05
*** iyamahat has quit IRC18:05
*** safchain has quit IRC18:05
*** iyamahat has joined #openstack-meeting-318:05
*** alexpilotti has quit IRC18:07
*** msambol has joined #openstack-meeting-318:08
*** julim has quit IRC18:08
*** yamahata has joined #openstack-meeting-318:09
*** neelashah has quit IRC18:09
*** smoriya_ has quit IRC18:12
*** yamamoto has joined #openstack-meeting-318:14
*** aarefiev22 has quit IRC18:15
*** dims has joined #openstack-meeting-318:16
*** andymaier has quit IRC18:16
*** yamamoto has quit IRC18:18
*** sambetts is now known as sambetts-afk18:20
*** rbak has quit IRC18:24
*** e0ne has joined #openstack-meeting-318:24
*** rbak has joined #openstack-meeting-318:26
*** sdake has joined #openstack-meeting-318:27
*** MarkAtwood has quit IRC18:29
*** vahidh has quit IRC18:31
*** s3wong has joined #openstack-meeting-318:34
*** salv-orlando has joined #openstack-meeting-318:35
*** salv-orl_ has quit IRC18:35
*** dconde has joined #openstack-meeting-318:37
*** dconde has quit IRC18:37
*** rbak has quit IRC18:38
*** alexpilotti has joined #openstack-meeting-318:44
*** rbak has joined #openstack-meeting-318:47
*** markvan has quit IRC18:48
*** rbak has quit IRC18:48
*** alexpilotti has quit IRC18:49
*** markvan has joined #openstack-meeting-318:50
*** jaypipes has quit IRC18:52
*** vahidh has joined #openstack-meeting-318:53
*** julim has joined #openstack-meeting-318:53
*** neiljerram has quit IRC18:54
*** aarefiev22 has joined #openstack-meeting-318:58
*** jpomeroy has quit IRC19:00
*** alexpilotti has joined #openstack-meeting-319:02
*** jpomeroy has joined #openstack-meeting-319:04
*** sigmavirus24 is now known as sigmavirus24_awa19:04
*** sigmavirus24_awa is now known as sigmavirus2419:05
*** rbak has joined #openstack-meeting-319:06
*** neelashah has joined #openstack-meeting-319:06
*** mestery has quit IRC19:06
*** alexpilotti has quit IRC19:07
*** aarefiev22 has quit IRC19:07
*** mestery has joined #openstack-meeting-319:07
*** vahidh has quit IRC19:08
*** aarefiev22 has joined #openstack-meeting-319:08
*** vahidh has joined #openstack-meeting-319:10
*** peristeri has joined #openstack-meeting-319:16
*** aarefiev22 has quit IRC19:23
*** jtomasek has joined #openstack-meeting-319:26
*** neelashah has quit IRC19:33
*** neelashah has joined #openstack-meeting-319:34
*** mbound_ has joined #openstack-meeting-319:37
*** e0ne has quit IRC19:45
*** pballand has quit IRC19:47
*** sdake has quit IRC19:47
*** pballand has joined #openstack-meeting-319:48
*** spzala has joined #openstack-meeting-319:49
*** bklei has joined #openstack-meeting-319:52
*** jtomasek has quit IRC19:53
*** pballand has quit IRC19:54
*** e0ne has joined #openstack-meeting-319:59
*** e0ne has quit IRC20:02
*** alexpilotti has joined #openstack-meeting-320:03
*** woodster_ has joined #openstack-meeting-320:05
*** alexpilotti has quit IRC20:08
*** e0ne has joined #openstack-meeting-320:19
*** e0ne has quit IRC20:19
*** e0ne has joined #openstack-meeting-320:19
*** e0ne has quit IRC20:20
*** Sukhdev has joined #openstack-meeting-320:20
*** baoli_ has quit IRC20:24
*** kzaitsev_mb has joined #openstack-meeting-320:27
*** matrohon has joined #openstack-meeting-320:30
*** shwetaap has quit IRC20:37
*** kzaitsev_mb has quit IRC20:38
*** liliars has left #openstack-meeting-320:46
*** baoli has joined #openstack-meeting-320:48
*** baoli has quit IRC20:48
*** baoli has joined #openstack-meeting-320:49
*** kzaitsev_mb has joined #openstack-meeting-320:49
*** lblanchard has quit IRC20:50
*** rbak has quit IRC20:51
*** matrohon has quit IRC20:51
*** njohnston has joined #openstack-meeting-320:51
*** hoangcx has joined #openstack-meeting-320:52
*** rbak has joined #openstack-meeting-320:52
*** igordcard__ has quit IRC20:52
*** ski1 has joined #openstack-meeting-320:53
*** galstrom is now known as galstrom_zzz20:54
*** Eva-i has joined #openstack-meeting-320:56
*** hichihara has joined #openstack-meeting-320:56
*** yamamoto has joined #openstack-meeting-320:58
flwang#startmeeting zaqar20:59
openstackMeeting started Mon Dec  7 20:59:25 2015 UTC and is due to finish in 60 minutes.  The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot.20:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:59
*** openstack changes topic to " (Meeting topic: zaqar)"20:59
openstackThe meeting name has been set to 'zaqar'20:59
*** gutbuster has left #openstack-meeting-320:59
flwang#topic roll call :)20:59
*** openstack changes topic to "roll call :) (Meeting topic: zaqar)"20:59
Eva-iHello20:59
flwangEva-i: hi20:59
flwangwhat's your time now?20:59
flwangEva-i: if there is only you and me, this could be a short meeting :)21:00
*** ryansb has joined #openstack-meeting-321:00
Eva-imy time is 00:0021:00
flwangryansb: o/21:01
ryansbhey folks21:01
flwangEva-i: oh, thanks for joining21:01
Eva-iBut I'm awake till 06:0021:01
flwangryansb: thanks for joining21:01
Eva-i=)21:01
flwangEva-i: you must be young, i can't do that after 30 :)21:02
Eva-iflwang: yep21:03
flwangok, let's start, i will miss vkmc and kick flaper8721:03
flwang#topic code review21:03
*** openstack changes topic to "code review (Meeting topic: zaqar)"21:03
*** alexpilotti has joined #openstack-meeting-321:04
flwangwe made a great progress in Mitaka-121:04
flwangthank you very much for everyone, especiall ryansb, vkmc, Eva-i and MD21:04
ryansbnot quite code review, but we have lots of patches in merge conflict21:04
*** mwagner_lap has quit IRC21:04
flwangryansb: haha21:04
flwangryansb: and gate failure :)21:04
ryansbyeah, I haven't had a chance to look at that yet21:05
flwangbut we made it, though we still have some patches in the air21:05
flwangnow the v1 client support is almost 'done', still missing the flavor list and create, pls blame /me21:06
ryansbmy point was, if you have patches out, please rebase them21:06
flwangryansb: sorry, yep21:06
flwangryansb: yep, i know you did a lot rebase for MD's patches21:06
ryansbhey, no worries. You made *tons* of progress anyways21:06
Eva-iflwang: thank you too, you are MVP21:07
Eva-iIMO21:07
flwangryansb: i hope we can complete the client work in this week21:07
*** stanchan has joined #openstack-meeting-321:08
flwangi will upload new patchset for flavor list/create and v2 subscription/claim21:08
*** alexpilotti has quit IRC21:08
flwangpls review them :)21:08
* vkmc is attending another meeting21:09
ryansbwill do21:09
* vkmc waves to the zaqar team21:09
flwangvkmc: i miss you21:09
*** kzaitsev_mb has quit IRC21:09
*** baoli has quit IRC21:09
flwanganything we need to highlight for code review?21:10
*** baoli has joined #openstack-meeting-321:10
*** pballand has joined #openstack-meeting-321:10
flwang#topic  docs21:10
*** openstack changes topic to "docs (Meeting topic: zaqar)"21:10
ryansbI'd like to highlight https://review.openstack.org/#/c/253731/21:10
ryansbbasically want feedback on how folks expect the CLI to be used for signedurls21:11
*** baoli has quit IRC21:11
ryansb(flwang and Eva-i, thanks for your feedback so far)21:11
*** baoli has joined #openstack-meeting-321:11
* ryansb stops trampling over the docs topic with code review stuff21:11
flwangryansb: i think for now21:11
flwangwhat we can do is print all the information to end user21:11
ryansbmakes sense21:12
flwangand we can improve it if we can any feedback21:12
ryansbcool21:12
Eva-iokay21:12
flwangryansb: if user has the permission to see it, show it21:12
flwangok, cool21:14
flwanglet's talk about the docs21:14
flwangnow the spec of config ref has been merged21:14
flwangso we can start to contribute the config ref for zaqar21:14
flwangit's great21:14
ryansbyeah, so what's the format for the API ref, will we be able to use swagger?21:15
flwangfor the api ref, we need to contribute to here https://github.com/openstack/api-site/blob/master/api-ref21:16
flwanganne is proposing to use swagger, but i think it's not now21:16
flwangfor now, we still need to follow the common way, like ^21:16
flwangif anybody can take it, it would be super awesome21:17
flwangsince the rest api of zaqar is the critical part21:17
*** neiljerram_bb has joined #openstack-meeting-321:17
Eva-iI think I can take it as well21:17
flwangEva-i: are you sure you have enough bandwidth?21:18
flwangEva-i: based on my discussion with lana, we(zaqar) are allowed only focus on one doc21:19
flwangmeans one of config ref, api ref and user guide21:19
Eva-iflwang: yes, I'm sure. I have a proposal21:19
flwangbut i'm always greedy, i want to do 2 or more21:19
flwangi would like to see config doc for sure, and i will do that21:20
Eva-iflwang: only on one doc? Let me do config ref then.21:20
flwanghaha21:20
flwangwe can argue with docs team21:20
*** bradjones has quit IRC21:20
*** dedery has joined #openstack-meeting-321:20
flwangi think they just worry about the reviewing21:20
Eva-iflwang: also https://blueprints.launchpad.net/openstack-manuals/+spec/zaqar-user-guide is too wide. We should narrow it to one type of all guide types.21:20
*** baoli has quit IRC21:21
flwangif we prepare everything and just need a +2 from them, then i think it shouldn't be too hard for them21:21
flwangEva-i: then how about let's focus on ap-ref in M-221:21
flwangand we can work together in M-3 for user guide21:22
flwangIMO, ap-ref needs a big effort21:22
Eva-iM-2 just started, right?21:22
ryansbyeah21:22
ryansbwell, last week21:22
*** bradjones has joined #openstack-meeting-321:22
*** bradjones has quit IRC21:22
*** bradjones has joined #openstack-meeting-321:22
Eva-iflwang: what about config ref that is already created?21:23
Eva-i*spec approved21:24
*** alexpilotti has joined #openstack-meeting-321:24
flwangEva-i: what did you mean?21:24
flwangEva-i: i mean i will take care the config ref21:25
flwangand if you want, i think ap-ref has a higher priority than user guide21:25
Eva-iflwang: alright, lets argue with doc team and based on the result we'll be working on config ref only or on both config ref and api ref.21:25
flwangryansb: how do you think?21:26
flwangEva-i: i would suggest, write a spec and submit it, and meanwhile, start to coding/writing the api-ref21:26
Eva-iflwang: okay21:26
flwangdon't wait for the result from doc team21:26
ryansbyeah, you can always write it and submit it later21:27
flwangso even we can't make it happen in Mitaka, at least it will be merged at early of N21:27
Eva-iflwang: I'll start coding api-ref then. I'll convert existing api-ref into appropriate format and add new things.21:27
flwangEva-i: awesome, before that, i think we just need to confirm with doc team if we still need to follow current way, like https://github.com/openstack/api-site/blob/master/api-ref21:28
*** Swami has quit IRC21:28
*** Swami has joined #openstack-meeting-321:29
Eva-iflwang: yes21:30
flwangEva-i: awesome, thanks21:31
flwanganything else under this topic?21:31
*** bpokorny has quit IRC21:31
flwang#topic UI21:32
*** openstack changes topic to "UI (Meeting topic: zaqar)"21:32
Eva-iflwang: so what to do with https://blueprints.launchpad.net/openstack-manuals/+spec/zaqar-user-guide ? Doc team doesn't understand what type of user guide this mean21:32
*** bpokorny has joined #openstack-meeting-321:32
flwangEva-i: that's the feedback from doc team?21:32
Eva-iflwang: yes.21:32
flwangthen i will leave a comments on that blueprint21:32
flwangand figure out21:32
Eva-iflwang: it should be either api-ref or something. Or "admin-guide-cloud". We have to use their terminology.21:33
flwangpersonally, i would like to see the most important one, but i'm not sure if we have the resource, and i'm not a native english speaker :(21:33
flwangadmin-guide-cloud21:33
flwangbut i need to figure out the workload and our bandwidth21:34
flwangwe can discuss it offline21:34
Eva-iokay21:34
flwangi know it's complex21:34
flwangreally appreciate for your effort on this domain21:34
flwangas for UI, now we have a repo and my goal is having a queue panel in M-221:35
flwangand complete the pool (and flavor?) panel in M-321:35
flwangor the subscription/notification panel for M-321:36
flwanggiven the pool and flavor are admin only actions21:37
flwangnot used too much21:37
flwangany comments?21:37
Eva-iI remember exploreshafali was working on pool and flavor design21:37
Eva-iDid she worked on queue desing?21:37
Eva-i*design21:37
flwangEva-i: shafali is busy now, she won't work on the UI21:38
flwangi will try to make a basic shape of UI project and any help is welcome21:39
flwangthat's basically my plan21:39
Eva-iflwang: I know she's busy, I was just asking if she might already invented something for queue panel21:40
flwangEva-i: i'm afraid no21:41
flwanggiven there is no repo :)21:41
flwangthere was21:41
Eva-iflwang: she made some sketches21:41
*** kzaitsev_mb has joined #openstack-meeting-321:41
flwanganyway, when I propose the first commit for zaqar ui, i will add you guys as reviewer21:41
Eva-iflwang: okay21:42
flwangEva-i: the sketches is some graph design, not code21:42
flwangwe have reviewed it on tokyo summit21:42
*** rloo has left #openstack-meeting-321:42
Eva-iflwang: so we already have graph designs?21:43
flwangEva-i: you can say that :)21:43
*** mwagner_lap has joined #openstack-meeting-321:43
flwangit's very simple i would say21:43
Eva-iokay =)21:44
*** alexpilotti has quit IRC21:45
flwangEva-i: but we also don't need a very complex UI21:45
flwangit's a normal panel just like images :)21:45
Eva-iflwang: yep21:46
flwang#topic integration with other projects21:46
*** openstack changes topic to "integration with other projects (Meeting topic: zaqar)"21:46
flwang1. Sahara21:46
flwangi just checked with ethan from sahara team, seems sahara team is not keen to use zaqar for their agent, at least for now21:47
flwangso we shouldn't expect to see the integration in Mitaka21:47
flwang2. Searchlights21:47
flwangthe integration with searchlight is in progress, see https://review.openstack.org/24622021:48
flwang3. Horizon21:48
flwangthe integration of horizon may depend on the integration with searchlight21:48
flwangsince we need to get the notifications/messages into zaqar queues, then notify horizon to refresh panels21:49
*** alexpilotti has joined #openstack-meeting-321:49
*** vgridnev has quit IRC21:49
flwanghere is the PoC if you're interested in https://review.openstack.org/#/c/246009/21:49
flwangi have talked with mrunge, but haven't get any feedback yet21:50
flwangany comments?21:50
*** spzala has quit IRC21:50
flwangso my plan is supporting searchlight team to get a good integration, and workable version by the end of M-221:51
flwangmeanwhile, interlock with horizon team to see how to leverage that work for horizon21:52
flwangnot sure if we can make it happen in Mitaka21:52
flwangsometimes, something out of control21:52
*** itxaka has quit IRC21:53
Eva-iyour plan is good21:55
Eva-iso far I saw no one from searchlight team asking for help in zaqar chat21:55
flwangEva-i: haha, plan is always good, progress is always surprising :)21:55
flwangEva-i: lei-zhi1 is the guys from searchlight team21:56
flwangi have some talks with him21:56
flwanghe is a chinese, so we talked in Chinese in private channel, sorry about that21:56
flwangi just want to make it faster21:56
flwangi will ask him speak up in zaqar channel next time :)21:57
flwangin Chinese21:57
flwangok, 2 mins left21:57
flwanganything we need to discuss?21:58
ryansbI don't think so21:58
flwangotherwise, let's back to our channel and rock on :)21:58
flwangcool21:58
Eva-iyes, I want21:58
flwangEva-i: ok, listening...21:58
Eva-iI'd like this to implement during mitaka https://blueprints.launchpad.net/zaqar/+spec/websocket-binary-support21:59
Eva-iIt'll be great if you check it out.21:59
Eva-iThanks21:59
*** ski1 has quit IRC21:59
flwangok, sure21:59
flwang#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Mon Dec  7 21:59:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-12-07-20.59.html21:59
*** ryansb has left #openstack-meeting-321:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-12-07-20.59.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-12-07-20.59.log.html21:59
flwangthanks guys21:59
*** alexpilotti has quit IRC22:02
*** dedery has quit IRC22:08
*** dedery has joined #openstack-meeting-322:09
*** yamamoto has quit IRC22:14
*** e0ne has joined #openstack-meeting-322:15
*** hoangcx has quit IRC22:15
*** hoangcx has joined #openstack-meeting-322:18
*** hoangcx has quit IRC22:20
*** alexpilotti has joined #openstack-meeting-322:23
*** mounica has quit IRC22:24
*** rtheis has quit IRC22:25
*** eliqiao_ has joined #openstack-meeting-322:27
*** alexpilotti has quit IRC22:27
*** eliqiao has quit IRC22:28
*** neiljerram_bb has quit IRC22:38
*** neelashah has quit IRC22:46
*** jpomeroy has quit IRC22:46
*** dedery has quit IRC22:49
*** Sukhdev has quit IRC22:50
*** vijendar has quit IRC22:52
*** vhoward has quit IRC22:55
*** alexpilotti has joined #openstack-meeting-323:01
*** mariojv has left #openstack-meeting-323:03
*** e0ne has quit IRC23:04
*** alexpilotti has quit IRC23:05
*** alexpilotti has joined #openstack-meeting-323:05
*** msambol has quit IRC23:10
*** kzaitsev_mb has quit IRC23:12
*** rpioso has quit IRC23:17
*** alexpilotti has quit IRC23:19
*** absubram has quit IRC23:23
*** yamamoto has joined #openstack-meeting-323:25
*** salv-orl_ has joined #openstack-meeting-323:25
*** banix has quit IRC23:28
*** salv-orlando has quit IRC23:28
*** alex_xu has quit IRC23:29
*** yamamoto has quit IRC23:31
*** alex_xu has joined #openstack-meeting-323:31
*** bklei has quit IRC23:32
*** spzala has joined #openstack-meeting-323:36
*** kzaitsev_mb has joined #openstack-meeting-323:47
*** rbak has quit IRC23:50
*** dimtruck is now known as zz_dimtruck23:54
*** sigmavirus24 is now known as sigmavirus24_awa23:57
*** rbak has joined #openstack-meeting-323:58

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