Tuesday, 2015-11-24

*** sacharya has quit IRC00:00
*** Sukhdev has quit IRC00:02
*** apoorvad has quit IRC00:03
*** otter768 has joined #openstack-meeting00:04
*** Sukhdev has joined #openstack-meeting00:04
*** _ntata_ has joined #openstack-meeting00:06
*** ntata_ has quit IRC00:06
*** dane_leblanc has quit IRC00:07
*** sgundur has quit IRC00:07
*** apoorvad has joined #openstack-meeting00:08
*** boris-42 has joined #openstack-meeting00:09
*** hichihara has joined #openstack-meeting00:10
*** pradk has joined #openstack-meeting00:10
*** mdenny has quit IRC00:11
*** tej has quit IRC00:12
*** galstrom is now known as galstrom_zzz00:14
*** Leom has quit IRC00:14
*** Sukhdev has quit IRC00:14
*** _ntata_ has quit IRC00:17
*** mbound_ has quit IRC00:18
*** jang has quit IRC00:19
*** Sukhdev has joined #openstack-meeting00:20
*** sacharya has joined #openstack-meeting00:21
*** jang has joined #openstack-meeting00:22
*** otter768 has quit IRC00:23
*** rossella_s has quit IRC00:23
*** sacharya has quit IRC00:23
*** rossella_s has joined #openstack-meeting00:23
*** ivar-laz_ has joined #openstack-meeting00:26
*** ivar-lazzaro has quit IRC00:26
*** otter768 has joined #openstack-meeting00:26
*** pots has joined #openstack-meeting00:27
*** pots2 has quit IRC00:29
*** J_Robinson has joined #openstack-meeting00:31
*** J_Robinson has quit IRC00:31
*** JRobinson__ has joined #openstack-meeting00:32
*** Sukhdev has quit IRC00:33
*** dmacpher-afk has quit IRC00:36
*** electroc_ has joined #openstack-meeting00:37
*** spzala_ has joined #openstack-meeting00:37
*** ashutoshn has joined #openstack-meeting00:38
*** rebase has quit IRC00:39
*** electroc_ has quit IRC00:39
ashutoshnHello folks, this is Ashutosh Narayan from India00:40
*** iyamahat has joined #openstack-meeting00:40
*** adahms has quit IRC00:40
*** electroc_ has joined #openstack-meeting00:41
anteayaashutoshn: you are in a meeting channel, try #openstack-dev00:41
*** spzala_ has quit IRC00:42
ashutoshnI suppose regular meeting is scheduled today at 00:30 UTC. Joe mentioned00:42
anteayaregular meeting for what?00:42
*** salv-orlando has quit IRC00:43
anteayathe only meeting I see going on right now is translations00:43
ashutoshnAPAC OpenStack docs meeting00:43
ashutoshnJoseph Robinson from Rackspace mentioned about it00:44
anteayahttp://eavesdrop.openstack.org/#Documentation_Team_Meeting this one?00:44
*** johnhunter has joined #openstack-meeting00:45
*** sdake_ has joined #openstack-meeting00:45
*** otter768 has quit IRC00:45
*** sdake has quit IRC00:45
*** electroc_ has quit IRC00:47
anteayahttp://lists.openstack.org/pipermail/openstack-docs/2015-November/007916.html00:47
ashutoshnYes00:48
anteayaashutoshn: you are correct, but I don't see that the channel has been booked00:48
anteayaand noone else is here00:48
*** ricolin has joined #openstack-meeting00:48
samueldmqanteaya: ashutoshn: looks like those meetings happen on Wednesdays ?00:49
anteayayes I saw that too00:49
ashutoshnYes..00:49
anteayain another post00:49
anteayaashutoshn: is your meeting on wednesday?00:50
*** zhhuabj has joined #openstack-meeting00:50
anteayaah so it is it is on the schedule on wednesday00:50
anteayaashutoshn: you are a day early00:50
anteayasamueldmq: thank you00:50
ashutoshnYes.. It's on Wednesday. Joined by mistake.. Time zones :(00:50
samueldmqanteaya: ashutoshn: np, perhaps try again in ~24 hours ? :)00:51
anteayaashutoshn: no worries00:51
anteayaashutoshn: nice to see keen participation00:51
*** okrieg has joined #openstack-meeting00:51
*** miyagishi_t has joined #openstack-meeting00:52
ashutoshn@samueldmq , @anteaya thank you ! Will join tomorrow morning IST00:52
anteayahave a good day00:52
samueldmqashutoshn: good luck, have a good day00:53
ashutoshnYou too.00:53
*** ashutoshn has left #openstack-meeting00:53
*** Swami has quit IRC00:53
*** electroc_ has joined #openstack-meeting00:54
*** lsell has left #openstack-meeting00:54
*** xyang1 has quit IRC00:58
*** cwolferh has quit IRC00:58
*** johnhunter has quit IRC01:01
*** yamamoto has joined #openstack-meeting01:02
*** tellesnobrega_af is now known as tellesnobrega01:03
*** elo has joined #openstack-meeting01:03
*** okrieg has quit IRC01:03
*** neelashah has joined #openstack-meeting01:06
*** neelashah1 has quit IRC01:07
*** yamamoto has quit IRC01:07
*** okrieg has joined #openstack-meeting01:08
*** nelsnelson has quit IRC01:09
*** neelashah1 has joined #openstack-meeting01:09
*** neelashah has quit IRC01:10
*** sdake_ is now known as sdake01:12
*** glauco_ has quit IRC01:13
*** glauco has joined #openstack-meeting01:13
*** sputnik13 has quit IRC01:15
*** ijw_ has quit IRC01:15
*** galstrom_zzz is now known as galstrom01:15
*** ljxiash has joined #openstack-meeting01:15
*** rebase has joined #openstack-meeting01:15
*** iyamahat has quit IRC01:16
*** apoorvad has quit IRC01:17
*** tfukushima has joined #openstack-meeting01:17
*** aranjan has quit IRC01:18
*** sambetts-afk has quit IRC01:18
*** mbound_ has joined #openstack-meeting01:19
*** pratikmallya has joined #openstack-meeting01:20
*** electroc_ has quit IRC01:23
*** mbound_ has quit IRC01:24
*** galstrom is now known as galstrom_zzz01:26
*** jgriffith_away is now known as jgriffith01:30
*** ivar-lazzaro has joined #openstack-meeting01:32
*** sankarshan_away is now known as sankarshan01:34
*** ivar-laz_ has quit IRC01:36
*** ivar-lazzaro has quit IRC01:36
*** okrieg has quit IRC01:36
*** baoli has quit IRC01:38
*** baoli has joined #openstack-meeting01:39
*** thorst has joined #openstack-meeting01:40
*** thorst has quit IRC01:40
*** thorst has joined #openstack-meeting01:41
*** leeantho_ has quit IRC01:43
*** julim has joined #openstack-meeting01:43
*** dmacpher has joined #openstack-meeting01:48
*** okrieg has joined #openstack-meeting01:48
*** iyamahat has joined #openstack-meeting01:48
*** LiuNanke has joined #openstack-meeting01:49
*** edtubill has joined #openstack-meeting01:49
*** shihanzhang has joined #openstack-meeting01:50
*** fitoduarte has quit IRC01:50
*** baohua has joined #openstack-meeting01:50
*** ijw has joined #openstack-meeting01:52
*** zhurong has joined #openstack-meeting01:52
*** okrieg has quit IRC01:56
*** LiuNanke has quit IRC01:58
*** glauco has quit IRC01:59
*** hoangcx has joined #openstack-meeting01:59
*** hoangcx has left #openstack-meeting02:00
*** cwolferh has joined #openstack-meeting02:00
*** 17SAD4YI2 has joined #openstack-meeting02:00
*** glauco has joined #openstack-meeting02:00
*** 17SAD4YI2 has quit IRC02:01
*** haomaiwa_ has joined #openstack-meeting02:01
*** ijw has quit IRC02:03
*** thorst has quit IRC02:04
*** glauco has quit IRC02:04
*** baohua has quit IRC02:05
*** thorst has joined #openstack-meeting02:08
*** shashank_hegde has quit IRC02:09
*** zhhuabj has quit IRC02:11
*** zhhuabj has joined #openstack-meeting02:11
*** amotoki has joined #openstack-meeting02:13
*** yamamoto has joined #openstack-meeting02:17
*** gcb has joined #openstack-meeting02:18
*** yamamoto has quit IRC02:21
*** thorst has quit IRC02:22
*** apoorvad has joined #openstack-meeting02:23
*** baohua has joined #openstack-meeting02:23
*** kencjohnston has joined #openstack-meeting02:27
*** beekhof has joined #openstack-meeting02:32
*** beekhof has joined #openstack-meeting02:32
*** david-ly_ has quit IRC02:36
*** tellesnobrega is now known as tellesnobrega_af02:36
*** glauco has joined #openstack-meeting02:38
*** houming has joined #openstack-meeting02:39
*** dims has joined #openstack-meeting02:40
*** novas0x2a|laptop has quit IRC02:41
*** shashank_hegde has joined #openstack-meeting02:45
*** otter768 has joined #openstack-meeting02:46
*** salv-orlando has joined #openstack-meeting02:47
*** SridharG has joined #openstack-meeting02:47
*** otter768 has quit IRC02:50
*** annp has joined #openstack-meeting02:51
*** sacharya has joined #openstack-meeting02:53
*** s3wong has quit IRC02:54
*** yfujioka has joined #openstack-meeting02:56
*** rebase has quit IRC02:56
*** tochi has quit IRC02:58
*** salv-orlando has quit IRC02:59
*** bobh has joined #openstack-meeting03:00
*** haomaiwa_ has quit IRC03:01
*** haomaiwang has joined #openstack-meeting03:01
*** yamamoto has joined #openstack-meeting03:04
*** lazy_prince has joined #openstack-meeting03:04
*** annp has quit IRC03:06
*** neelashah1 has quit IRC03:07
*** neelashah has joined #openstack-meeting03:08
*** harshs has quit IRC03:08
*** neelashah1 has joined #openstack-meeting03:11
*** klkumar has joined #openstack-meeting03:11
*** neelashah has quit IRC03:12
*** tochi has joined #openstack-meeting03:14
*** jhesketh has joined #openstack-meeting03:14
*** pradk has quit IRC03:15
*** yfujioka has quit IRC03:15
*** topol has joined #openstack-meeting03:16
*** yfujioka has joined #openstack-meeting03:16
*** dims has quit IRC03:17
*** annp has joined #openstack-meeting03:18
*** vivek-ebay has quit IRC03:19
*** vivek-ebay has joined #openstack-meeting03:20
*** topol has quit IRC03:20
*** vivek-ebay has quit IRC03:21
*** dims has joined #openstack-meeting03:22
*** apoorvad has quit IRC03:27
*** klkumar has quit IRC03:28
*** iyamahat has quit IRC03:29
*** xingchao has joined #openstack-meeting03:34
*** kencjohnston has quit IRC03:34
*** dims has quit IRC03:35
*** ricolin_ has joined #openstack-meeting03:36
*** tfukushima has quit IRC03:36
*** ricolin has quit IRC03:36
*** tfukushima has joined #openstack-meeting03:37
*** ricolin_ has quit IRC03:37
*** ricolin has joined #openstack-meeting03:38
*** tfukushima has quit IRC03:39
*** tfukushima has joined #openstack-meeting03:40
*** tfukushima has quit IRC03:42
*** tfukushima has joined #openstack-meeting03:42
*** tfukushima has quit IRC03:44
*** klkumar has joined #openstack-meeting03:44
*** tfukushima has joined #openstack-meeting03:45
*** tfukushima has quit IRC03:47
*** tfukushima has joined #openstack-meeting03:47
*** kencjohnston has joined #openstack-meeting03:48
*** tochi has quit IRC03:48
*** tfukushima has quit IRC03:49
*** tfukushima has joined #openstack-meeting03:50
*** asselin has joined #openstack-meeting03:51
*** asselin_ has joined #openstack-meeting03:52
*** tfukushima has quit IRC03:52
*** tochi has joined #openstack-meeting03:55
*** Kevin_Zheng has joined #openstack-meeting03:56
*** sgundur has joined #openstack-meeting03:57
*** pratikmallya has quit IRC03:57
*** haomaiwang has quit IRC04:01
*** haomaiwa_ has joined #openstack-meeting04:01
*** spzala has quit IRC04:01
*** asselin_ has quit IRC04:05
*** asselin has quit IRC04:05
*** spzala has joined #openstack-meeting04:06
*** bobh has quit IRC04:06
*** david-lyle has joined #openstack-meeting04:08
*** thorst has joined #openstack-meeting04:11
*** otter768 has joined #openstack-meeting04:13
*** thorst has quit IRC04:15
*** spzala_ has joined #openstack-meeting04:16
*** sgundur has quit IRC04:17
*** sacharya has quit IRC04:18
*** ayoung has quit IRC04:20
*** spzala_ has quit IRC04:21
*** edtubill has quit IRC04:22
*** edtubill has joined #openstack-meeting04:24
*** zhhuabj has quit IRC04:25
*** iyamahat has joined #openstack-meeting04:26
*** edtubill has quit IRC04:29
*** novas0x2a|laptop has joined #openstack-meeting04:29
*** iyamahat has quit IRC04:32
*** shashank_hegde has quit IRC04:32
*** tochi has quit IRC04:33
*** pratikmallya has joined #openstack-meeting04:33
*** tfukushima has joined #openstack-meeting04:37
*** annp has quit IRC04:38
*** annp has joined #openstack-meeting04:38
*** dmowrer has joined #openstack-meeting04:39
*** SridharG has quit IRC04:40
*** sacharya has joined #openstack-meeting04:40
*** epico has joined #openstack-meeting04:41
*** tfukushima has quit IRC04:43
*** dmowrer has quit IRC04:43
*** cwolferh has quit IRC04:44
*** spzala has quit IRC04:44
*** akuznetsov has joined #openstack-meeting04:47
*** egallen has joined #openstack-meeting04:49
*** akuznetsov has quit IRC04:52
*** tomoe_ has joined #openstack-meeting04:53
*** klkumar has quit IRC04:54
*** ddieterl_ has quit IRC04:55
*** maishsk has quit IRC04:56
*** maishsk has joined #openstack-meeting04:56
*** aranjan has joined #openstack-meeting04:58
*** otter768 has quit IRC04:59
*** tochi has joined #openstack-meeting04:59
*** maishsk has quit IRC04:59
*** electroc_ has joined #openstack-meeting04:59
*** haomaiwa_ has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** tfukushima has joined #openstack-meeting05:05
*** bobh has joined #openstack-meeting05:07
*** klkumar has joined #openstack-meeting05:07
*** neelashah1 has quit IRC05:07
*** maishsk has joined #openstack-meeting05:08
*** neelashah has joined #openstack-meeting05:08
*** lazy_prince has quit IRC05:08
*** sdake_ has joined #openstack-meeting05:09
*** tfukushima has quit IRC05:10
*** sdake has quit IRC05:10
*** neelashah1 has joined #openstack-meeting05:11
*** bobh has quit IRC05:11
*** neelashah has quit IRC05:12
*** tfukushima has joined #openstack-meeting05:12
*** neelashah has joined #openstack-meeting05:14
*** novas0x2a|laptop has quit IRC05:14
*** neelashah1 has quit IRC05:15
*** haomaiwang has quit IRC05:19
*** kebray has joined #openstack-meeting05:20
*** kebray has quit IRC05:20
*** gcb has quit IRC05:24
*** Sukhdev has joined #openstack-meeting05:24
*** sdake_ has quit IRC05:26
*** haomaiwa_ has joined #openstack-meeting05:27
*** achanda has joined #openstack-meeting05:29
*** kencjohnston has quit IRC05:32
*** baohua has quit IRC05:34
*** irenab has quit IRC05:38
*** maishsk has quit IRC05:41
*** achanda has quit IRC05:41
*** gcb has joined #openstack-meeting05:41
*** akuznetsov has joined #openstack-meeting05:45
*** Sukhdev has quit IRC05:45
*** klkumar has quit IRC05:46
*** aukhan has joined #openstack-meeting05:51
*** numans has joined #openstack-meeting05:52
*** electroc_ has quit IRC05:54
*** ddieterly has joined #openstack-meeting05:55
*** salv-orlando has joined #openstack-meeting05:56
*** roxanaghe has joined #openstack-meeting05:56
*** nelsnelson has joined #openstack-meeting05:58
*** roxanaghe has quit IRC05:59
*** ddieterly has quit IRC06:00
*** salv-orlando has quit IRC06:01
*** haomaiwa_ has quit IRC06:01
*** haomaiwa_ has joined #openstack-meeting06:02
*** klkumar has joined #openstack-meeting06:02
*** hughhalf has quit IRC06:04
*** SridharG has joined #openstack-meeting06:04
*** zhurong_ has joined #openstack-meeting06:05
*** egallen_ has joined #openstack-meeting06:06
*** JRobinson__ has quit IRC06:07
*** egallen has quit IRC06:08
*** egallen_ is now known as egallen06:08
*** zhurong has quit IRC06:09
*** shashank_hegde has joined #openstack-meeting06:11
*** nadya_ has joined #openstack-meeting06:11
*** wznoinsk has quit IRC06:11
*** hughhalf has joined #openstack-meeting06:12
*** wznoinsk has joined #openstack-meeting06:12
*** pasquier-s has quit IRC06:13
*** thorst has joined #openstack-meeting06:13
*** pasquier-s has joined #openstack-meeting06:14
*** thorst has quit IRC06:17
*** singhj has quit IRC06:18
*** electroc_ has joined #openstack-meeting06:21
*** electroc_ has quit IRC06:24
*** electroc_ has joined #openstack-meeting06:27
*** electroc_ has quit IRC06:28
*** electroc_ has joined #openstack-meeting06:29
*** egallen has quit IRC06:30
*** mrmartin has joined #openstack-meeting06:31
*** irenab has joined #openstack-meeting06:32
*** nadya_ has quit IRC06:33
*** tfukushima has quit IRC06:35
*** mrmartin has quit IRC06:35
*** vahidh has quit IRC06:37
*** lazy_prince has joined #openstack-meeting06:38
*** e0ne has joined #openstack-meeting06:40
*** rvasilets has joined #openstack-meeting06:43
*** cfriesen__ has quit IRC06:45
*** electroc_ has quit IRC06:46
*** numans has quit IRC06:48
*** aranjan has quit IRC06:48
*** boris-42 has quit IRC06:48
*** tfukushima has joined #openstack-meeting06:52
*** amrith is now known as _amrith_06:54
*** akuznetsov has quit IRC06:56
*** ddieterly has joined #openstack-meeting06:57
*** nadya_ has joined #openstack-meeting06:59
*** adiantum has quit IRC07:00
*** haomaiwa_ has quit IRC07:01
*** haomaiwang has joined #openstack-meeting07:01
*** ddieterly has quit IRC07:01
*** neeti has joined #openstack-meeting07:02
*** akuznetsov has joined #openstack-meeting07:02
*** akuznetsov has quit IRC07:06
*** dmowrer has joined #openstack-meeting07:06
*** gampel has joined #openstack-meeting07:06
*** e0ne has quit IRC07:08
*** neeti has quit IRC07:09
*** aranjan has joined #openstack-meeting07:09
*** neeti has joined #openstack-meeting07:09
*** dmowrer has quit IRC07:10
*** otter768 has joined #openstack-meeting07:11
*** egallen has joined #openstack-meeting07:12
*** neelashah1 has joined #openstack-meeting07:13
*** egallen has quit IRC07:14
*** neelashah has quit IRC07:14
*** jgriffith is now known as jgriffith_away07:15
*** otter768 has quit IRC07:15
*** neelashah has joined #openstack-meeting07:16
*** neelashah1 has quit IRC07:17
*** numans has joined #openstack-meeting07:21
*** vahidh has joined #openstack-meeting07:22
*** egallen has joined #openstack-meeting07:22
*** vahidh has quit IRC07:26
*** sacharya has quit IRC07:27
*** bvandenh has joined #openstack-meeting07:34
*** akuznetsov has joined #openstack-meeting07:35
*** spzala has joined #openstack-meeting07:38
*** topol has joined #openstack-meeting07:39
*** topol has quit IRC07:41
*** dmacpher has quit IRC07:41
*** ajo has quit IRC07:42
*** spzala has quit IRC07:42
*** scheuran has joined #openstack-meeting07:43
*** egallen has quit IRC07:44
*** hauntsWLI has joined #openstack-meeting07:45
*** aranjan has quit IRC07:45
*** ajo has joined #openstack-meeting07:46
*** Tango has quit IRC07:46
*** nmagnezi has joined #openstack-meeting07:47
*** hauntsWLI is now known as achatterji07:47
*** tfukushima has quit IRC07:47
*** tfukushima has joined #openstack-meeting07:48
*** matrohon has joined #openstack-meeting07:49
*** achatterji has quit IRC07:51
*** egallen has joined #openstack-meeting07:53
*** gongysh_ has joined #openstack-meeting07:54
*** sacharya has joined #openstack-meeting07:56
*** ddieterly has joined #openstack-meeting07:58
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Nov 24 08:00:39 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
*** otter768 has joined #openstack-meeting08:00
anteayahello08:00
*** haomaiwang has quit IRC08:01
*** jyuso1 has joined #openstack-meeting08:01
*** haomaiwa_ has joined #openstack-meeting08:02
*** ddieterly has quit IRC08:02
*** nmagnezi has quit IRC08:02
*** sacharya has quit IRC08:03
*** pratikmallya has quit IRC08:04
*** matrohon1 has joined #openstack-meeting08:05
*** matrohon1 has quit IRC08:05
*** otter768 has quit IRC08:05
*** rdopiera has joined #openstack-meeting08:09
*** egallen_ has joined #openstack-meeting08:10
anteaya#endmeeting08:10
*** openstack changes topic to "swiftclient (Meeting topic: swift)"08:10
openstackMeeting ended Tue Nov 24 08:10:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-08.00.html08:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-08.00.txt08:10
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-08.00.log.html08:10
*** ildikov has quit IRC08:11
*** egallen has quit IRC08:12
*** egallen_ is now known as egallen08:12
*** salv-orlando has joined #openstack-meeting08:13
*** wuhg has joined #openstack-meeting08:13
*** bvandenh has quit IRC08:16
*** lennyb has joined #openstack-meeting08:16
*** jichen has joined #openstack-meeting08:17
*** salv-orlando has quit IRC08:21
*** neeti has quit IRC08:21
*** neeti has joined #openstack-meeting08:24
*** mrmartin has joined #openstack-meeting08:25
*** kaisers1 has left #openstack-meeting08:25
*** akuznetsov has quit IRC08:26
*** salv-orlando has joined #openstack-meeting08:29
*** lennyb has quit IRC08:30
*** nmagnezi has joined #openstack-meeting08:32
*** salv-orlando has quit IRC08:33
*** subscope has joined #openstack-meeting08:36
*** iyamahat has joined #openstack-meeting08:37
*** jyuso1 has left #openstack-meeting08:38
*** aranjan has joined #openstack-meeting08:42
*** iyamahat has quit IRC08:42
*** shashank_hegde has quit IRC08:43
*** ildikov has joined #openstack-meeting08:43
*** sdake has joined #openstack-meeting08:45
*** numans has quit IRC08:47
*** numans has joined #openstack-meeting08:47
*** aranjan has quit IRC08:47
*** jlanoux has joined #openstack-meeting08:48
*** sdake has quit IRC08:48
*** subscope has quit IRC08:48
*** sdake has joined #openstack-meeting08:48
*** e0ne has joined #openstack-meeting08:49
*** subscope has joined #openstack-meeting08:52
*** neeti has quit IRC08:53
*** berendt has joined #openstack-meeting08:54
*** ddieterly has joined #openstack-meeting08:58
*** haomaiwa_ has quit IRC09:01
*** sdake has quit IRC09:01
*** haomaiwa_ has joined #openstack-meeting09:01
*** ddieterly has quit IRC09:03
*** bobh has joined #openstack-meeting09:09
*** subscope has quit IRC09:09
*** fitoduarte has joined #openstack-meeting09:09
*** subscope has joined #openstack-meeting09:10
*** mattoliverau has quit IRC09:10
*** derekh has joined #openstack-meeting09:10
*** mbound_ has joined #openstack-meeting09:10
*** gampel1 has joined #openstack-meeting09:11
*** yamahata has quit IRC09:11
*** matt6434 has joined #openstack-meeting09:11
*** bobh has quit IRC09:13
*** adduarte has joined #openstack-meeting09:13
*** gampel has quit IRC09:14
*** vgridnev has joined #openstack-meeting09:15
*** ygbo has joined #openstack-meeting09:16
*** fitoduarte has quit IRC09:16
*** yassine__ has joined #openstack-meeting09:18
*** claudiub has joined #openstack-meeting09:19
*** zhurong_ has quit IRC09:22
*** zeih has joined #openstack-meeting09:25
*** ndipanov has quit IRC09:25
*** ndipanov has joined #openstack-meeting09:26
*** mdbooth has joined #openstack-meeting09:27
*** neeti has joined #openstack-meeting09:27
*** claudiub has quit IRC09:33
*** dmowrer has joined #openstack-meeting09:33
*** oomichi has quit IRC09:34
*** claudiub has joined #openstack-meeting09:34
*** achanda has joined #openstack-meeting09:35
*** subscope has quit IRC09:37
*** dmowrer has quit IRC09:37
*** xingchao has quit IRC09:40
*** ociuhandu has quit IRC09:42
*** aranjan has joined #openstack-meeting09:44
*** bvandenh has joined #openstack-meeting09:44
*** tomoe_ has quit IRC09:48
*** neeti has quit IRC09:52
*** andymaier has joined #openstack-meeting09:54
*** bogdando has joined #openstack-meeting09:54
*** maishsk has joined #openstack-meeting09:55
*** neeti has joined #openstack-meeting09:55
*** alexschm has joined #openstack-meeting09:55
*** ddieterly has joined #openstack-meeting10:00
*** haomaiwa_ has quit IRC10:01
*** otter768 has joined #openstack-meeting10:01
*** neiljerram has joined #openstack-meeting10:01
*** haomaiwa_ has joined #openstack-meeting10:02
*** adiantum has joined #openstack-meeting10:05
*** ddieterly has quit IRC10:05
*** vahidh has joined #openstack-meeting10:05
*** otter768 has quit IRC10:06
*** aranjan has quit IRC10:06
*** sacharya has joined #openstack-meeting10:08
*** vahidh has quit IRC10:09
*** gcb has quit IRC10:11
*** sacharya has quit IRC10:12
*** nmagnezi has quit IRC10:13
*** neelashah has quit IRC10:14
*** achanda has quit IRC10:14
*** neelashah1 has joined #openstack-meeting10:14
*** thorst has joined #openstack-meeting10:15
*** ricolin has quit IRC10:15
*** neelashah has joined #openstack-meeting10:18
*** neelashah1 has quit IRC10:18
*** ildikov has quit IRC10:19
*** numans has quit IRC10:19
*** thorst has quit IRC10:20
*** houming has quit IRC10:21
*** tomoe_ has joined #openstack-meeting10:23
*** epico has quit IRC10:24
*** nmagnezi has joined #openstack-meeting10:24
*** tomoe_ has quit IRC10:27
*** tfukushima has quit IRC10:27
*** fzdarsky|afk has joined #openstack-meeting10:28
*** jlanoux_ has joined #openstack-meeting10:29
*** numans has joined #openstack-meeting10:30
*** subscope has joined #openstack-meeting10:30
*** fzdarsky|afk is now known as fzdarsky10:31
*** glauco has quit IRC10:32
*** glauco has joined #openstack-meeting10:32
*** jlanoux has quit IRC10:32
*** ildikov has joined #openstack-meeting10:32
*** adduarte has quit IRC10:33
*** tellesnobrega_af is now known as tellesnobrega10:34
*** toscalix has joined #openstack-meeting10:35
*** annp has quit IRC10:37
*** salv-orlando has joined #openstack-meeting10:38
*** subscope has quit IRC10:41
*** salv-orlando has quit IRC10:42
*** aspiers has quit IRC10:43
*** sankarshan is now known as sankarshan_away10:47
*** aukhan has quit IRC10:48
*** Liuqing has joined #openstack-meeting10:50
*** tomoe_ has joined #openstack-meeting10:53
*** matt6434 has quit IRC10:54
*** matt6434 has joined #openstack-meeting10:55
*** toscalix has quit IRC10:55
*** tomoe_ has quit IRC10:58
*** maishsk has quit IRC10:59
*** haomaiwa_ has quit IRC11:01
*** adiantum has quit IRC11:01
*** haomaiwang has joined #openstack-meeting11:01
*** amotoki has quit IRC11:01
*** ddieterly has joined #openstack-meeting11:02
*** aranjan has joined #openstack-meeting11:03
*** dims has joined #openstack-meeting11:06
*** _amrith_ is now known as amrith11:06
*** ddieterly has quit IRC11:06
*** houming has joined #openstack-meeting11:08
*** dgonzalez has joined #openstack-meeting11:08
*** bobh has joined #openstack-meeting11:10
*** yamamoto has quit IRC11:10
*** aysyd has joined #openstack-meeting11:10
*** bobh has quit IRC11:15
*** bzhao has joined #openstack-meeting11:16
*** Daisy_ has joined #openstack-meeting11:19
*** ociuhandu has joined #openstack-meeting11:21
*** rbowen has joined #openstack-meeting11:25
*** jlanoux_ has quit IRC11:27
*** jlanoux has joined #openstack-meeting11:28
*** tochi has quit IRC11:28
*** rbowen has quit IRC11:32
*** aranjan has quit IRC11:36
*** Daisy_ has quit IRC11:37
*** amrith is now known as _amrith_11:37
*** Daisy has joined #openstack-meeting11:38
*** achanda has joined #openstack-meeting11:39
*** Daisy has quit IRC11:41
*** Daisy has joined #openstack-meeting11:41
*** Daisy has quit IRC11:43
*** Daisy has joined #openstack-meeting11:46
*** jlanoux_ has joined #openstack-meeting11:46
*** ildikov has quit IRC11:48
*** egallen has quit IRC11:48
*** jlanoux has quit IRC11:49
*** Daisy has quit IRC11:51
*** neeti has quit IRC11:51
*** Daisy has joined #openstack-meeting11:51
*** gcb has joined #openstack-meeting11:53
*** Daisy has quit IRC11:53
*** ihrachys has joined #openstack-meeting11:53
*** Daisy has joined #openstack-meeting11:53
*** adahms has joined #openstack-meeting11:56
*** oomichi has joined #openstack-meeting11:57
*** yamamoto has joined #openstack-meeting11:57
*** baoli has quit IRC11:58
*** gmann_ has joined #openstack-meeting11:58
*** sdake has joined #openstack-meeting11:58
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Nov 24 12:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho is here today?12:00
Kevin_Zhenghi12:00
gmann_hi12:00
oomichihi12:00
alex_xuhello everyone12:00
*** subscope has joined #openstack-meeting12:00
*** haomaiwang has quit IRC12:01
alex_xulet's start the meeting12:01
alex_xu#topic actions from last meeting12:01
edleafeo/12:01
*** openstack changes topic to "actions from last meeting (Meeting topic: nova api)"12:01
* oomichi all kids still wake up even now 9pm..12:01
alex_xusdague ask docs team about approval rights by api subteam on our wadl12:01
alex_xuoomichi: heh12:01
jicheno/12:01
alex_xusdague: are you around?12:01
gmann_alex_xu: cool12:01
*** haomaiwa_ has joined #openstack-meeting12:02
* johnthetubaguy waves hello12:02
alex_xuI guess not, let me check with him, when he is up12:02
edleafealex_xu: this is more or less a holiday week in the US12:02
alex_xugmann_: yea, if we get right, that will more easy for us12:02
edleafehe might not be around12:02
*** otter768 has joined #openstack-meeting12:02
alex_xuedleafe: ah, thanks12:02
*** ddieterly has joined #openstack-meeting12:02
alex_xuedleafe: why you are still working :)12:02
gmann_alex_xu: yes, that will be helpful to fast the things12:02
alex_xuso let's move on12:03
alex_xu#topic content patches up for review12:03
edleafealex_xu: I keep asking myself that :)12:03
*** openstack changes topic to "content patches up for review (Meeting topic: nova api)"12:03
*** sdake has quit IRC12:03
gmann_edleafe: heh :)12:03
alex_xu#link https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking12:03
alex_xuwe have a set of patches ready for review12:03
alex_xuso please review them12:03
alex_xuI'm thinking for the service and live-migration I can ask scheduler and live-migration team members help to take a look at.12:04
oomichinice progress :)12:04
gmann_alex_xu: i will start allocating my time from tomorrow, was busy in tempest things.12:04
alex_xugmann_: thanks12:04
*** alexschm has quit IRC12:04
alex_xuAnd there is api-ref patch up https://review.openstack.org/24853412:04
alex_xuI hope this can be an example of what api-ref expected, so please help me!12:04
alex_xuBasically as my understand the api-ref is focus on the API behavior. The concept doc is focus on the use-case12:05
edleafealex_xu: I'll try to find time today for that12:05
alex_xuedleafe: thanks12:05
*** Daisy has quit IRC12:05
*** alexschm has joined #openstack-meeting12:05
gmann_alex_xu: how about giving ref of concept guide in API description in api-ref ?12:05
*** Daisy has joined #openstack-meeting12:06
alex_xugmann_: yea, maybe on the top of api ref, we needn't link which api to one concept guide12:06
alex_xus/which/each12:06
*** otter768 has quit IRC12:06
johnthetubaguywe could, but that does feel like overkill I guess12:07
*** ddieterly has quit IRC12:07
gmann_johnthetubaguy: but that gives benefit of reading all from one place12:07
johnthetubaguywould be nice to link to the live-migrate use cases, etc, in the concept guide from the complete ref, I supose12:07
gmann_yea otherway around also helps12:08
*** dmowrer has joined #openstack-meeting12:08
johnthetubaguyI think it will become clearer once we fill out one in full12:08
alex_xuyea, just keep fill the doc12:09
johnthetubaguyI know how alex_xu is doing just that, lets give live-migrate looking good, and see how it looks12:09
*** sdake has joined #openstack-meeting12:09
johnthetubaguys/I know how/I like how/12:09
gmann_ok.12:09
alex_xuyea, please help me make it better, them we have template for api ref12:09
alex_xuso let's move on12:10
alex_xu#topic most needed next content patches12:10
*** openstack changes topic to "most needed next content patches (Meeting topic: nova api)"12:10
alex_xuSo how about we select topic for people focus on next week? For example we focus on this one https://github.com/openstack/nova/blame/master/api-guide/source/general_info.rst#L11512:10
*** Daisy has quit IRC12:11
jichen+112:11
johnthetubaguythe alternative, I guess, is to all pick different bits, like with the API ref, but either way should work12:11
alex_xuyea, based on people flavor12:12
gmann_yea12:13
alex_xuI just thought if people can focus one area, then review quick, feedback quick.12:13
alex_xubut anyway either way works12:13
*** subscope has quit IRC12:13
edleafewe should pick the parts to work on so that we don't duplicate effort12:14
*** subscope has joined #openstack-meeting12:14
alex_xuedleafe: put the part you work on in concept doc section at https://etherpad.openstack.org/p/nova-v2.1-api-doc12:14
alex_xumost of time we use this way to sync work.12:15
*** sacharya has joined #openstack-meeting12:15
edleafealex_xu: great!12:15
*** thorst has joined #openstack-meeting12:15
* alex_xu just quck add note to etherpad12:16
*** paul-carlton1 has joined #openstack-meeting12:16
jichenalex_xu: there is a section in https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking12:16
* edleafe just signed up for a couple12:16
alex_xuedleafe: ah, I see you take the host one, thanks :)12:16
*** salv-orlando has joined #openstack-meeting12:17
alex_xujichen: that is just for patch ready for review I think, we shouldn't put too much our work detail to confuse other review12:17
johnthetubaguyshould we not be sure to only take the ones we are working on?12:17
alex_xus/other review/other reviewer/12:17
jichenalex_xu: ok,12:18
alex_xujohnthetubaguy: yea, one or two, not two much, release timely when you aren't work on anymore12:18
alex_xus/not two much/not too much/12:18
johnthetubaguyalex_xu: cool, sounds like we are agreed12:18
johnthetubaguywell, if you have patches up for seven, thats cool, but yeah12:19
alex_xuyea12:19
alex_xuso let's move on12:19
alex_xu#topic API futures - specs12:19
*** tellesnobrega is now known as tellesnobrega_af12:19
*** openstack changes topic to "API futures - specs (Meeting topic: nova api)"12:19
alex_xuany spec people want to bring up, I didn't get time select some12:19
oomichican I ?12:20
*** sacharya has quit IRC12:20
alex_xuoomichi: sure, please12:20
*** miyagishi_t has quit IRC12:20
oomichi#link https://review.openstack.org/#/c/249167/12:20
*** thorst has quit IRC12:20
oomichiwe have api-wg guideline and some specs don't fit to the guideline12:20
johnthetubaguyyeah, need to agree the way forward for the pause and cancel live-migrate12:20
oomichis/and/but/12:21
alex_xuoomichi: good catch!12:21
oomichithe above patch fixes one12:21
gmann_oomichi: ahh, yea12:21
johnthetubaguyoomichi: which spec from API working group is that in?12:21
oomichiI am wondering how about containing the part of the guideline on spec template.12:22
oomichiit is difficult to know the guideline by all people12:22
*** salv-orlando has quit IRC12:22
oomichijohnthetubaguy: sorry, cannot understand the comment12:22
alex_xu#link https://github.com/openstack/api-wg/blob/master/guidelines/naming.rst12:22
alex_xuI guess this one ^12:22
johnthetubaguyoomichi: sorry, I was meaning which API WG doc tells us about the rules we need to follow, is it this one? http://specs.openstack.org/openstack/api-wg/guidelines/naming.html12:22
*** rossella_s has quit IRC12:23
johnthetubaguyah, yeah, looking at the same thing12:23
oomichijohnthetubaguy: yeah, you are right12:23
oomichialex_xu: you also12:23
alex_xujohnthetubaguy: yea, that's one, at the bottom of doc12:23
*** rossella_s has joined #openstack-meeting12:23
johnthetubaguyhmm, that is messy, its the opposite to most of our current action names, but agreed with the approach12:24
oomichithis kind of violation seems common, I feel12:24
gmann_johnthetubaguy: yea, many action names we changed back to v2 style in v2.112:24
alex_xujohnthetubaguy: nvm....we have a lot of still in nova. like 'os-liveMigrate'12:25
oomichijohnthetubaguy: yeah, right. nova api is nice practice for getting better api design :)12:25
alex_xus/still/style/12:25
johnthetubaguydo we have any that follow the new style yet?12:25
*** tellesnobrega_af is now known as tellesnobrega12:25
johnthetubaguyaction names that is12:25
*** neelashah has quit IRC12:26
alex_xujohnthetubaguy: sorry, I didn't get you12:26
oomichijohnthetubaguy: I'm fixing the api on nova-spec reviews, and trigger_crash_dump is one12:26
*** neelashah has joined #openstack-meeting12:26
johnthetubaguyI am just looking at the current API12:26
johnthetubaguywe don't seem to have any server actions that follow the API WG rules12:26
johnthetubaguyso following the rules is going to make our API even more inconsistent, which seems like a worry12:27
jichenyeah, do a quick look and seems no12:27
*** zeih has quit IRC12:27
johnthetubaguywe seem to have camalCase or os-camalCase12:27
gmann_johnthetubaguy: yea, we changed those back in v2.1 (in v3 all of them were corrected :))12:27
johnthetubaguygmann_: well v2.1 == v2.0 yes12:28
edleafejohnthetubaguy: we could accept 'os-liveMigrate' and 'os_live_migrate' to do the same thing. Then change the docs to only mention the latter12:28
*** zeih has joined #openstack-meeting12:28
gmann_yea12:28
johnthetubaguyedleafe: we could, yes12:28
gmann_how about changing those in single microversion? but we need to support old also.12:29
johnthetubaguyI am just worried we are making the API worse by following the new rules, anyways12:29
*** neelashah1 has joined #openstack-meeting12:29
oomichiI found three12:29
oomichidisassociate_host disassociate_project and associate_host12:29
alex_xuwe said we will correct api as api-wg guide in next release in one microversion12:29
edleafejohnthetubaguy: sometimes you need to move backwards before moving forwards :)12:29
*** rbowen has joined #openstack-meeting12:30
oomichion the current APIs12:30
johnthetubaguyedleafe: agreed, just asking the question12:30
johnthetubaguyoomichi: I guess they are missing from the complete ref?12:30
oomichijohnthetubaguy: nice point :)12:30
oomichijohnthetubaguy: I feel so12:30
edleafejohnthetubaguy: of course - it's an excellent point that has come up frequently in the api-wg12:30
johnthetubaguyanyways, seems like we are going into this eyes open, so I am fine with it12:30
*** neelashah has quit IRC12:31
johnthetubaguyneed to go back and fix some of this next release, and add some alias bits into action and parameter names12:31
alex_xuyea12:32
*** neelashah has joined #openstack-meeting12:32
oomichijohnthetubaguy: nice way12:32
*** rtheis has joined #openstack-meeting12:32
alex_xuoops, I have one want to ask at here again12:32
alex_xu#link https://review.openstack.org/24554312:32
*** aranjan has joined #openstack-meeting12:33
alex_xuso there is opinion said, we should deprecated the feature before we remove the feature from the API12:33
alex_xumy answer is no, because we have microversion, the old version api always give people chance to upgrade12:33
*** neelashah1 has quit IRC12:33
alex_xuand asked oomichi, we agreed on the same thing. But want to ask this again in api team.12:34
oomichialex_xu: +112:34
johnthetubaguyalex_xu: we can remove it now in the microversion12:34
edleafealex_xu: agree12:34
johnthetubaguythe problem, is we can't really ever remove it from the old version, but thats a different issue12:34
alex_xujohnthetubaguy: yea12:35
oomichijohnthetubaguy: yeah, completely same thing we discussed today12:35
gmann_looks fine with microversion.12:35
oomichidifficult to bump minimum microversion12:35
*** bzhao has quit IRC12:36
alex_xuok, thanks all, this looks like clear, let me bring this to live-migrate meeting after few hours12:36
edleafeoomichi: why do we need to bump the minimum?12:36
gmann_oomichi: yup, but that's should be fine as we provide better API in latest version :)12:37
oomichiedleafe: for removing maintenance cost on the community12:37
*** bzhao has joined #openstack-meeting12:37
alex_xuedleafe: drop some burden?12:37
alex_xubut that won't happen12:37
edleafeoomichi: ah, I see. I don't think it'll ever happen12:37
oomichiedleafe: for us ;)12:38
oomichiedleafe: actually as you said12:38
alex_xuok, so any more want to bring up?12:38
*** yanyanhu has joined #openstack-meeting12:38
alex_xuok, let's move on12:38
alex_xu#topic API futures - patches for approved specs12:38
*** openstack changes topic to "API futures - patches for approved specs (Meeting topic: nova api)"12:38
alex_xuI guess this one is no also, as people focus on nova-spec recently12:39
johnthetubaguydo we have any API concept guide stuff that needs discussing?12:39
alex_xuI guess no12:40
oomichi#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/complete-todo-in-api-concept-doc,n,z12:40
oomichi^^^ api-concept patches on the gerrit12:41
*** wolsen has quit IRC12:41
*** ildikov has joined #openstack-meeting12:41
alex_xuso let's move on12:42
*** zhipeng has joined #openstack-meeting12:42
alex_xu#topic open12:42
*** openstack changes topic to "open (Meeting topic: nova api)"12:42
alex_xuany open? if not, we will have short meeting today12:42
zhipengdo we have time for new specs ?12:42
zhipengjust arrived12:42
zhipengsorry12:43
alex_xuzhipeng: sure, please go ahead12:43
zhipengthx alex_xu, we have i think 3 specs in Nova that deals with API in Mitaka12:43
alex_xuzhipeng: do you have link?12:44
zhipengI'm trying to find them :)12:44
*** subscope has quit IRC12:44
zhipengin a minute12:44
alex_xuzhipeng: no problem :)12:44
*** maishsk has joined #openstack-meeting12:45
zhipenghttps://www.google.com/url?q=https%3A%2F%2Freview.openstack.org%2F%23%2Fc%2F241066%2F&sa=D&sntz=1&usg=AFQjCNExQRyhLq36c0GptMBn3qQo1oCcHQ12:46
zhipengah sorry12:46
zhipenghttps://review.openstack.org/#/c/241066/12:46
*** Administrator__ has joined #openstack-meeting12:46
*** subscope has joined #openstack-meeting12:46
zhipenghttps://review.openstack.org/#/c/241065/12:46
zhipenghttps://review.openstack.org/#/c/241063/12:47
*** adiantum has joined #openstack-meeting12:47
jichenI also have one ... https://review.openstack.org/#/c/219431/12:47
*** yamamoto has quit IRC12:47
zhipengso basically we want to enable running storage functions in VM or container, that requires Nova supports attach with options that deals with high speed bus type12:48
johnthetubaguyzhipeng: we have rejected blueprints to similar to those suggested in the past, but I will need to go through each one, one by one and understand what is wanted12:48
zhipengjohnthetubaguy no problem12:49
johnthetubaguyzhipeng: the problem I am facing right now, is we have around 100 in review right now12:49
alex_xuyea, need take a look at more.12:49
johnthetubaguyzhipeng: been accepting them since the end of july, and its proving hard work getting through them all12:50
zhipengyes totally understodd, and I just want to raise awareness :)12:50
zhipengjohnthetubaguy understodd12:50
alex_xujichen one looks like ok for me12:50
alex_xubut anyway let review them offline12:51
alex_xuif no more question, I will close the meeting early12:51
*** gcb has quit IRC12:51
johnthetubaguy+112:51
zhipengthanks alex_XU, we already faced BP dropped in L due to lack of review resource12:52
zhipeng+112:52
alex_xuthanks all12:52
oomichialex_xu: nice leading12:52
jichenok, thanks12:52
alex_xuzhipeng: np12:52
alex_xu#endmeeting12:52
*** openstack changes topic to "swiftclient (Meeting topic: swift)"12:52
openstackMeeting ended Tue Nov 24 12:52:18 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-11-24-12.00.html12:52
gmann_Thanks all12:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-11-24-12.00.txt12:52
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-11-24-12.00.log.html12:52
oomichithanks all12:52
johnthetubaguyzhipeng: which was the blueprint in L? is that up for mitaka now?12:52
zhipengyes the BPs I mentioned earlier12:52
zhipengthey were all raised back in L, but CR just kinda stopped12:53
*** aranjan has quit IRC12:53
zhipengin a early stage couple of months ago12:53
johnthetubaguyzhipeng: you should restore the old reviews, rather than create new ones12:53
zhipengso we resubmit the BPs in M now12:53
johnthetubaguyzhipeng: that way are tracking tools can tell you restored them12:53
zhipengok I will note this :) and feedback to my team12:53
zhipenggot it12:53
*** gmann_ has quit IRC12:54
*** dewsday has joined #openstack-meeting12:54
*** dprince has joined #openstack-meeting12:54
johnthetubaguyzhipeng: its worth trying to get specs up for review well before the design summit, in general, we are more likely to get to them that way.12:54
*** dewsday has left #openstack-meeting12:55
*** Qiming has joined #openstack-meeting12:55
*** baoli has joined #openstack-meeting12:55
zhipengjohnthetubaguy we tried but there was also priority issue, so most of time we were backlogged12:56
zhipengbut we will definitely try to get it done before design summit next time :)12:56
johnthetubaguyzhipeng: yeah, understand, things get in the way very often, just a heads up for next time really12:56
zhipengjohnthetubaguy thx and duly noted :)12:56
*** haiwei_ has joined #openstack-meeting12:58
*** yamamoto has joined #openstack-meeting12:59
*** okrieg has joined #openstack-meeting12:59
*** andymaier has quit IRC12:59
*** lazy_prince has quit IRC12:59
*** elynn has joined #openstack-meeting13:00
*** cfriesen__ has joined #openstack-meeting13:00
*** haomaiwa_ has quit IRC13:01
*** egallen has joined #openstack-meeting13:01
*** lvdongbing has joined #openstack-meeting13:01
Qiming?13:01
*** haomaiwang has joined #openstack-meeting13:01
Qimingsomeone endmeeting?13:01
haiwei_hi13:01
haiwei_it seems nova api meeting is not held today13:02
*** oomichi has quit IRC13:02
Liuqingalex_xu had end the meeting.13:02
Liuqing\o13:02
yanyanhuseems meeting topic is swift now13:02
Qiming#startmeeting senlin13:02
openstackMeeting started Tue Nov 24 13:02:35 2015 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: senlin)"13:02
openstackThe meeting name has been set to 'senlin'13:02
alex_xuLiuqing: no, we have, but end early....13:02
Qimingokay, seems the topic remained unchanged, :)13:03
yanyanhualex_xu, :)13:03
elynno/13:03
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:03
Qimingpls review agenda and see if you have topics for discussion13:03
*** ddieterly has joined #openstack-meeting13:03
*** lvdongbing has quit IRC13:04
*** gcb has joined #openstack-meeting13:04
*** houming has quit IRC13:04
*** lvdongbing has joined #openstack-meeting13:04
Qiming#topic Mitaka work items13:04
*** openstack changes topic to "Mitaka work items (Meeting topic: senlin)"13:04
Qiming#link https://etherpad.openstack.org/p/senlin-mitaka-workitems13:05
*** salv-orl_ has joined #openstack-meeting13:05
*** marcusvrn_ has quit IRC13:05
Qimingwith recent changes, we are enforcing an implicit rule for claiming todo items13:05
*** ljxiash has quit IRC13:06
Qimingwhenever someone claims a work item, pls make sure an item is recorded in the etherpad so that we can review it on weekly meetings13:06
*** rbowen has quit IRC13:06
yanyanhuyes, a description of it can be found in the first paragraph of TODO.rst13:06
Qimingheat resource type support13:06
*** jhesketh has quit IRC13:06
elynnyes, I'm working on it.13:06
Qimingelynn, any help needed?13:06
elynnabout profile attrs13:07
elynnI saw your comment, do you mean we should remove them all?13:07
*** jhesketh has joined #openstack-meeting13:07
Qimingokay, I don't see those are useful attributes13:07
Qimingif the profile has a 'name' property, usually we don't need a 'name' attribute for it13:08
elynnyes, it's not useful for now...13:08
*** ddieterly has quit IRC13:08
*** lkarm has joined #openstack-meeting13:08
*** jckasper has quit IRC13:08
elynnok, I will remove them all in next patch.13:08
Qimingmy suggestion would be keep the attributes set a minimum, add them later when needed13:08
Qimingonce things are there, you will never get a chance to remove it13:09
Qimingbut if it is missing, we can always fix it, ;)13:09
*** egallen has quit IRC13:09
elynngot it, seem 'name' & 'metadata' attrs in cluster should be removed too.13:09
Qimingsenlinclient tests13:09
Qimingelynn, yep, just follow heat's convention there13:10
*** bobh has joined #openstack-meeting13:10
elynnok13:10
Qiminghaiwei has submitted some patches for client test cases13:10
haiwei_yes, will continue to do it13:11
*** egallen has joined #openstack-meeting13:11
Qiminggreat13:11
haiwei_the pace is a little slow13:11
*** haomaiwang has quit IRC13:11
Liuqingi could help improve the unit test  of senlinclient13:13
*** yanyan has joined #openstack-meeting13:13
*** Qiming has quit IRC13:13
haiwei_thanks, Liuqing13:13
Liuqingmy pleasure,13:14
Liuqing Qiming  seems offline13:14
*** wolsen has joined #openstack-meeting13:14
yanyanyes, I also dropped13:15
yanyannetwork issue I think13:15
elynnwhat's the problem...13:15
yanyannot sure, let me ping him13:16
elynnseems Qiming haven't back13:16
*** zhaobo0825 has joined #openstack-meeting13:16
*** yanyanhu has quit IRC13:16
haiwei_should we continue?13:17
*** Qiming_ has joined #openstack-meeting13:17
Qiming_sigh13:17
elynnwelcome back :)13:17
Qiming_network very unstable these days13:17
Qiming_anywhere in China13:18
Qiming_f* the gvmt13:18
zhipenghaha13:18
zhipengvpn is not stable any more13:18
Qiming_nothing is stable13:18
Liuqingi use shadow socket13:18
Qiming_okay, back to agenda13:19
Qiming_I am working on fixing the 400/404 status code issues13:19
Qiming_it turned out to be a huge task13:19
Qiming_will continue to work on that13:19
Qiming_health policy13:20
Qiming_still not sure wether we should do polling by ourselves13:20
Qiming_talked with xinhui (still at San Francisco this week)13:20
elynnIf we don't, what project can?13:20
Liuqingone question, how we define failure of node?13:21
Qiming_elynn: no answer13:21
Qiming_Liuqing: good question13:21
Qiming_even if we provide some polling operations, it will be the last resort13:21
Qiming_I'd really prefer some external monitoring software/service to do that13:22
yanyanhi, Qiming_, as liuqing's question, maybe we should let the implementer of profile to decide it I think13:22
Qiming_if we are to do it, we need to have all profile types support a do_check() method13:22
Qiming_yep, it would be a per-profile-type thing13:23
Qiming_even with that, it may and may not be useful13:23
yanyanthat is true13:23
Qiming_even nova tells you a server is still there, does it mean anything at all?13:23
*** bvandenh has quit IRC13:24
Qiming_your service inside that server may have already crashed13:24
elynnif we do monitoring, that would be too big for this project...13:24
Qiming_elynn: that is true13:24
yanyanelynn, we won't touch monitoring itself I think13:24
Qiming_we are very very cautious on this13:25
yanyanwe just try to find a way to help user leverage existing monitoring service to decide the health status of a node13:25
Qiming_need to discuss with julio on the receiver design13:25
Liuqingbut if we implement that , it will be very very cool for OpenStack ecosystem13:25
Qiming_hopefully we can hook senlin to any external monitoring13:25
elynnI think there's also two levels of health monitor here, vm level and software level.13:26
Qiming_that is where I have been struggling13:26
*** paul-carlton1 has left #openstack-meeting13:26
Qiming_maybe we still need to provide some very basic health management, but for advanced features, you will have to turn to other monitoring services/software13:27
yanyanQiming_, sure13:27
Qiming_before we have a clear vision/design13:27
*** spzala has joined #openstack-meeting13:27
Liuqingagree13:27
Qiming_you won't see any code, :)13:27
Qiming_triggers, emm13:28
Qiming_do we want to keep them ?13:28
Qiming_or we delete them completely from senlin?13:28
haiwei_why not13:28
Qiming_"why not" means?13:29
haiwei_I mean why not keep them13:29
Qiming_senlin trigger-create -t os.aodh.alarm -s some_spec alarm113:29
*** bobh has quit IRC13:30
Qiming_why are we doing this?13:30
yanyanhmm, IMHO, it is not necessary to keep it in senlin13:30
elynnWhat's the benefit if we keep them?13:30
*** doug-fish has joined #openstack-meeting13:30
Qiming_why don't we tell the user to use ceilometer/aodh alarm-create directly?13:30
*** jhesketh has quit IRC13:30
yanyansince there are many ways user can define an alarm, e.g. using ceilometer/aodh/monasca API, or using heat13:31
yanyanyea13:31
*** Liuqing_ has joined #openstack-meeting13:31
Liuqing_is that the reason for deleting triggers?13:31
Qiming_the original thought is that we will support complex policies13:31
elynnagree to remove them before anyone aware of them13:31
*** bobh has joined #openstack-meeting13:31
*** bobh has quit IRC13:31
elynnor hide the apis for triggers.13:32
Qiming_by 'complex policies', I mean a policy that contains the trigger source, trigger condition and the handler13:32
Liuqing_yep, i got it13:32
Qiming_there is no real meat even if we support such a concept in senlin13:32
*** MaxPC has joined #openstack-meeting13:32
*** banix has joined #openstack-meeting13:32
*** Liuqing has quit IRC13:32
Qiming_it looks sexy, but it also looks very inflexible13:33
Qiming_you won't be able to support monitoring solutions other than the one you started with13:33
Qiming_so ... remove it?13:33
yanyan+1 from me13:34
Liuqing_+113:34
*** weshay_xchat is now known as weshay13:34
elynnno doubt +113:34
haiwei_honestly I have no idea, removing is OK i think13:34
Qiming_okay, I'll copy them to some secret place before removing them13:34
*** markvoelker has quit IRC13:35
*** banix has quit IRC13:35
Qiming_I spent a lot time trying to figure out the commonalities among the so many different flavors of 'ceilometer alarms'13:35
*** pradk has joined #openstack-meeting13:35
Qiming_then we don't have todos about monasca, :)13:35
yanyanyes13:35
*** thorst has joined #openstack-meeting13:36
Qiming_what a relief!13:36
elynnless is more13:36
Qiming_update operation for profiles13:36
*** tej has joined #openstack-meeting13:36
Qiming_elynn: +10013:36
yanyanok, this is in good progress I think13:36
Qiming_we can always add them back when there are justifications13:36
Qiming_cool13:37
yanyanbut we need to add some support to sdk before we start some work in senlin side13:37
Qiming_but I'm still seeing a long way to go13:37
*** thorst_ has joined #openstack-meeting13:37
yanyanyep13:37
Qiming_update to flavor is a 'resize' ?13:37
yanyannetwork and image update support is just a start13:37
yanyanI guess so13:37
Qiming_sigh...13:38
haiwei_what is the flavor?13:38
yanyanbut that really depends on Nova's support on it13:38
haiwei_instance flavor?13:38
yanyanneed do more investigation on related Nova API13:38
yanyanhaiwei_, yes13:38
Qiming_nova client say one thing, nova server says another, nova api doc says several other things13:38
Qiming_no idea where we are regarding the 'receiver' design, will catch up with julio later13:39
yanyanumm, this is a thing we need to be careful about...13:39
haiwei_updating is really difficult13:39
yanyanto ensure the implementation is correct13:39
Qiming_lock breaker13:40
yanyanhaiwei_, yes13:40
elynnsince last meeting13:40
elynnhaven't got time to update the patches.13:40
Qiming_need some careful reviews, it is related to the stability of the core engine13:41
elynnI will add a function to set actions to fail if they attach to dead engine.13:41
Qiming_don't want to push this13:41
*** thorst has quit IRC13:41
Qiming_okay13:41
yanyanelynn, I just updated the etherpad to add some in-progress patches about lock breaker13:41
elynnMaybe need a functional tests for them13:42
yanyanelynn, sure13:42
Qiming_okay, moving on13:42
elynnyanyan: Thanks!13:42
*** vahidh has joined #openstack-meeting13:42
Qiming_#topic api and docs13:42
yanyansince the patch about pre_test_hook just got merged, I will refactor the functional test to make it work in one or two days13:42
*** Qiming has joined #openstack-meeting13:42
*** yanyan is now known as yanyanhu13:43
haiwei_cool13:43
Qiming_I have spent some time going through the so many sources of info about documenting apis, api guidelines13:43
Qiming_won't be able to go through every detail in this meeting13:43
Qiming_there are things still under discussion13:44
haiwei_I have confirmed the 'location header' from the api-wg guy, he said it mean 'response header'13:44
*** thorst_ has quit IRC13:44
Qiming_for example, the format of 'links' to be returned to client13:44
Qiming_'with_count' query string13:45
Qiming_'POST' for actions13:45
Qiming_'Cache-Control'13:45
*** thorst_ has joined #openstack-meeting13:45
Qiming_constraints: max/min values13:45
yanyanhumany issues need to fix13:45
elynndo you know where I can see the docs for senlin in openstack website? is there any?13:45
Qiming_there are new specs about rewriting api docs using Swagger13:45
Qiming_there are many destinations for publish/gating13:46
*** claudiub|2 has joined #openstack-meeting13:46
*** claudiub has quit IRC13:46
Qiming_docs.o.o, developer.o.o, specs.o.o ...13:46
Qiming_still working on that13:46
elynnall I know is the wiki page for senlin.13:47
*** vahidh has quit IRC13:47
*** adiantum has quit IRC13:47
Qiming_there is still release notes thing13:47
*** adiantum1 has joined #openstack-meeting13:47
yanyanhujust as ethan said, can we find a way to let user read senlin doc in an easier way?13:47
*** pkoniszewski has joined #openstack-meeting13:47
yanyanhusome colleagues also asked us this question13:47
Qiming_so, after the initial learning phase, we would need some liaisons for jobs13:47
Qiming_https://wiki.openstack.org/wiki/CrossProjectLiaisons13:48
Qiming_yanyanhu: we have docs for users, docs for developers, just need to figure out how to publish them13:48
Qiming_which site, how to set up gate to do this13:48
yanyanhuQiming_, yes13:48
yanyanhuwe have them there actually, just need to figure out a way to let user check it easily13:49
*** haomaiwang has joined #openstack-meeting13:49
*** thorst_ has quit IRC13:49
Qiming_if any of you have interests on any of these cross-project topics13:49
yanyanhuyea13:49
Qiming_please let me know13:49
elynnok, I got what you mean.13:49
haiwei_for senlin, it mainly means SDK?13:50
yanyanhuwill check this page13:50
haiwei_the cross-project13:50
*** aranjan has joined #openstack-meeting13:50
haiwei_and oslo?13:50
yanyanhuhaiwei_, also some other services who want to talk with us or we want to talk with13:50
Qiming_haiwei_: no, it means release management, api workgroup, product working group ...13:50
*** adiantum has joined #openstack-meeting13:51
*** pkoniszewski has quit IRC13:51
*** dmowrer has quit IRC13:51
Qiming_and hopefully, a liaison for magnum13:51
*** dmowrer has joined #openstack-meeting13:51
*** adiantum1 has quit IRC13:51
Qiming#topic blueprints and bugs13:52
*** openstack changes topic to "blueprints and bugs (Meeting topic: senlin)"13:52
Qimingany high priority items?13:52
yanyanhuI think we need to recheck all of them and set them to proper status13:52
*** Administrator__ has quit IRC13:52
haiwei_yanyan's bug?13:53
Qimingseems we have already covered bluepints on the etherpad page13:53
haiwei_can we decide the priority by ourselves?13:53
*** ayoung has joined #openstack-meeting13:53
*** markvoelker has joined #openstack-meeting13:53
yanyanhuI mean all of those existing bugs and bps, especially some ones have been done13:53
Qiming29 bugs13:54
*** tej has quit IRC13:54
haiwei_i know, I mean your bug reported today is a high priority?13:54
Qiming10 medium importance13:54
elynnI think it's good to set priority for this bugs and BPs, at least let others outside knows that what we are working on.13:55
yanyanhuoh, haiwei_ I guess so13:55
Qimingsome are outdated13:55
yanyanhuyes13:55
yanyanhuwe should cleanse them13:55
haiwei_I think the bugs related to node creation should be high priority13:55
elynnsince they may not know where the etherpad is.13:55
*** dmowrer has quit IRC13:55
yanyanhuand mark those ones have been done to Fix released?13:55
Qiming_yes, that is something we need to do, review them all13:55
*** Administrator__ has joined #openstack-meeting13:56
Qiming_fix-released won't be manual13:56
yanyanhuoh13:56
Qiming_it will be taken care of by some ci scripts13:56
*** pkoniszewski has joined #openstack-meeting13:57
yanyanhusince I found no any bug is closed in Senlin bug list13:57
*** ljxiash has joined #openstack-meeting13:57
Qiming_that is because we haven't create a formal release13:57
yanyanhuok, understand13:57
*** achanda has quit IRC13:57
*** houming has joined #openstack-meeting13:57
Qiming_#action review bug list and reset status13:58
yanyanhuthanks13:58
haiwei_and again, any bug fix should contain a bug report, will be strict about that in the coming review13:58
*** maishsk has quit IRC13:58
*** topol has joined #openstack-meeting13:58
yanyanhuhaiwei_, agree13:58
yanyanhuand also set the priority as elynn suggested13:59
elynnyea, let's be formal ;)13:59
Qiming_need to work hard13:59
Qiming_we are not making a lot of progress recently, to be honest13:59
haiwei_the benefit is when we make a release, we can say we have fixed how many bugs in this cycle13:59
*** salv-orl_ has quit IRC14:00
Qiming_haiwei_: that can be solved using releasenotes14:00
Qiming_okay, time is up, thx for joining14:00
Qiming_#endmeeting14:00
haiwei_yes, if we have reported it14:00
*** adarazs has joined #openstack-meeting14:00
*** subscope has quit IRC14:00
*** haomaiwang has quit IRC14:01
Qiming#endmeeting14:01
yanyanhuQiming_, you need to switch nickname first14:01
*** openstack changes topic to "swiftclient (Meeting topic: swift)"14:01
openstackMeeting ended Tue Nov 24 14:01:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-11-24-13.02.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-11-24-13.02.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-11-24-13.02.log.html14:01
*** dmacpher has joined #openstack-meeting14:01
*** Qiming has quit IRC14:01
*** yanyanhu has left #openstack-meeting14:01
*** haomaiwa_ has joined #openstack-meeting14:01
*** maishsk has joined #openstack-meeting14:01
*** elynn has left #openstack-meeting14:01
*** adarazs has left #openstack-meeting14:01
*** Qiming has joined #openstack-meeting14:02
*** Qiming_ has left #openstack-meeting14:02
*** Qiming has quit IRC14:02
*** otter768 has joined #openstack-meeting14:03
*** ddieterly has joined #openstack-meeting14:04
*** haiwei_ has quit IRC14:04
*** subscope has joined #openstack-meeting14:04
*** aranjan has quit IRC14:04
*** zhipeng has quit IRC14:04
*** LimorStotland has left #openstack-meeting14:05
*** ^Gal^ has quit IRC14:05
*** dandruta has joined #openstack-meeting14:05
*** achanda has joined #openstack-meeting14:06
*** jhesketh has joined #openstack-meeting14:08
*** otter768 has quit IRC14:08
*** rbowen has joined #openstack-meeting14:08
*** ddieterly has quit IRC14:08
*** subscope has quit IRC14:10
*** dmowrer has joined #openstack-meeting14:10
*** ricolin has joined #openstack-meeting14:10
*** banix has joined #openstack-meeting14:10
*** subscope has joined #openstack-meeting14:11
*** jckasper has joined #openstack-meeting14:12
*** dmowrer has quit IRC14:13
*** subscope has quit IRC14:13
*** dmowrer has joined #openstack-meeting14:13
*** subscope has joined #openstack-meeting14:13
*** subscope has quit IRC14:16
*** subscope has joined #openstack-meeting14:17
*** eharney has joined #openstack-meeting14:19
*** hichihara has quit IRC14:20
*** jckasper has quit IRC14:24
*** jichen has quit IRC14:24
*** zz_dimtruck is now known as dimtruck14:25
*** jckasper has joined #openstack-meeting14:31
*** amotoki has joined #openstack-meeting14:32
*** bobh has joined #openstack-meeting14:35
*** bvandenh has joined #openstack-meeting14:36
*** mtanino has joined #openstack-meeting14:37
*** ddieterly has joined #openstack-meeting14:38
*** nate_gone is now known as njohnston14:38
*** manjeets has joined #openstack-meeting14:38
*** gmmaha has joined #openstack-meeting14:40
*** kencjohnston has joined #openstack-meeting14:40
*** banix has quit IRC14:41
*** banix has joined #openstack-meeting14:42
*** banix has quit IRC14:43
*** goodygum_ is now known as noqa_v_qoovnie14:44
*** sacharya has joined #openstack-meeting14:45
*** jgriffith_away is now known as jgriffith14:47
*** sacharya has quit IRC14:49
*** oanufriev1 has joined #openstack-meeting14:51
*** irenab has quit IRC14:51
*** rbak has joined #openstack-meeting14:53
*** achanda has quit IRC14:53
*** adahms has quit IRC14:54
*** achanda has joined #openstack-meeting14:54
*** xingchao has joined #openstack-meeting14:54
*** ntata has joined #openstack-meeting14:55
*** korzen has joined #openstack-meeting14:55
*** achanda_ has joined #openstack-meeting14:56
*** houming has quit IRC14:58
*** achanda has quit IRC14:59
* mestery looks around for armax 15:00
HenryGpoke armax15:00
armaxhere15:00
amotokio/15:00
*** aranjan has joined #openstack-meeting15:00
njohnstono/15:00
dougwigo/15:00
*** oanufriev1 has left #openstack-meeting15:00
armaxcarl_baldwin: ping15:00
neiljerramo/15:01
*** haomaiwa_ has quit IRC15:01
armaxkevinbenton: ping15:01
carl_baldwinarmax: pong15:01
armax#startmeeting neutron_drivers15:01
openstackMeeting started Tue Nov 24 15:01:13 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
mesteryarmax: You need MOAR COFFEE15:01
kevinbentonhi15:01
*** openstack changes topic to " (Meeting topic: neutron_drivers)"15:01
openstackThe meeting name has been set to 'neutron_drivers'15:01
*** haomaiwa_ has joined #openstack-meeting15:01
*** bobh has quit IRC15:01
armaxmestery: tons of it, I just fell out of bed15:02
*** boris-42 has joined #openstack-meeting15:02
*** temujin_ has joined #openstack-meeting15:02
mesteryarmax: slacker ;)15:02
armaxok, let’s try to squash the triaged list a bit15:02
armax#link https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=Triaged&field.tag=rfe15:02
armaxor do we want over the list of comments that amotoki put together on the wiki page?15:03
*** ljxiash has quit IRC15:03
armaxand HenryG15:03
mesteryarmax: Lets start with amotoki's comments15:03
mesteryand HenryG15:03
mesterySince they put the time in :)15:03
*** temujin_ is now known as oanufriev__15:03
armaxsounds good15:03
mestery#awesomesauce15:03
HenryGshould go quick, just double-check our work15:04
*** dane_leblanc has joined #openstack-meeting15:04
*** salv-orlando has joined #openstack-meeting15:04
*** Tango has joined #openstack-meeting15:04
kevinbentonarmax: link to wiki?15:04
*** ljxiash has joined #openstack-meeting15:04
*** thorst_ has joined #openstack-meeting15:04
amotokihttps://wiki.openstack.org/wiki/Meetings/NeutronDrivers15:05
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers15:05
armaxlet’s start with bug 137366015:05
openstackbug 1373660 in neutron "[RFE] An in-use dhcp port can be deleted" [Wishlist,Triaged] https://launchpad.net/bugs/137366015:05
*** dkranz has joined #openstack-meeting15:05
*** spotz_zzz is now known as spotz15:05
*** houming has joined #openstack-meeting15:05
*** thorst_ has quit IRC15:05
*** okrieg has quit IRC15:05
*** thorst_ has joined #openstack-meeting15:06
armaxI think the issue here is: some ports should not be deleted15:06
armaxmanually by the tenant15:06
*** lvdongbing has quit IRC15:07
kevinbentonwhy? it's their network15:07
amotokithe problem is that dhcp-agent runs but a user can delete the port15:07
armaxand the port will be recreated by the agent15:08
dougwigas long as we're consistent api-wide, and either cleanup the resources behind the port, or refuse to delete it until those resources have been deleted/unassigned, i'm happy.15:08
Administrator__as I know, dhcp-agent will recreate a new dhcp port15:08
kevinbentonyes, the agent should try to recreate the port15:08
russellbdougwig: +115:08
armaxI’d rather not special case the treatment of certain ports15:08
*** dims_ has joined #openstack-meeting15:08
dougwigkevinbenton: then it's just kinda silly to let them delete it in the first place, isn't it?15:08
kevinbentondougwig: no, it's their network. do what they want15:09
*** dims has quit IRC15:09
russellbmeh, it's not a user managed port though15:09
kevinbentonotherwise we have to special case the port15:09
amotokiI think you all are interested in this. more comments to the bug would be appreciated.15:09
mesteryamotoki: ++15:09
armaxthen special ports should be invisble to them15:09
kevinbentonand now we have to check user context in the API for deleting ports15:09
russellbimo, it's weird that this port is visible, yes15:09
dougwigkevinbenton: if you delete it and it magically reappears, then we're not giving "their network" any special delete powers. :)15:10
amotokiwe have several possible approaches. let's comment!15:10
kevinbentonit would be stranger to have an invisible IP address that you contact for DNS15:10
armaxlet’s start from the fact that the problem is not well stated to be honest15:10
Administrator__armax, I agree with you that special ports should be invisble to user and not consume port quota15:10
*** thorst_ has quit IRC15:10
*** pcarver_ is now known as pcarver15:10
dougwighiding it would cause real problems. i've lost count of the times that dhcp has failed and it's come down to an agent race startup condition and the dhcp port is just down, and needed flapping.15:11
HenryGAdministrator__: can you id yourself please?15:11
kevinbentonthis port is like any other network participant. it's wired by the agent, it gets its IP from IPAM, etc15:11
mesterydougwig: ++15:11
armaxdougwig: if the system worked correctly you wouldn’t even need to know about it15:11
armaxdougwig: come on15:11
Administrator__sorry, I will change15:11
*** Administrator__ has quit IRC15:11
amotoki:)15:11
mesteryarmax: Huh? That sounds just plain silly15:11
dougwigarmax: sure, but...15:11
mesteryWe're gonna hide and it and make it harder to debug issues?15:12
mesteryBecause it should just work?15:12
kevinbentonif we hide it, then the same logic should be used to hide all router interfaces as well15:12
armaxdougwig: no, I am not saying that15:12
* mestery hands armax more coffee15:12
armaxI am just saying that preventing deletion is equivalent to hiding them15:12
amotokiagree with mestery and kevinbenton15:12
armaxand that’s bad15:12
russellbshowing them leaks the backend implementation a bit, but *shrug*15:12
dougwigarmax: no, because you can still see status, make it up/down, notice that it's part of your topology. it's always seemed obvious that it should be listed to me.15:12
mesteryWe need to make this thing easier to use and operate, not harder15:12
mesteryHiding things doesn't help15:12
mesterydougwig: ++15:13
carl_baldwinI tend to think this is pretty low priority.15:13
amotokifrom my comment: One idea is to clear device_id/owner of a port before allowing to delete the port. It achieves a kind of "force delete".15:13
kevinbentonrussellb: same can be said for router interfaces15:13
neiljerramFWIW, preventing deletion seems to me different from hiding15:13
russellbkevinbenton: agree..15:13
*** balajiiyer has joined #openstack-meeting15:13
*** aranjan has quit IRC15:13
russellbbut that ship has sailed :)15:13
*** hanzhang has joined #openstack-meeting15:13
*** okrieg has joined #openstack-meeting15:13
armaxsame can be said for all ports that are used to do crazy stuff15:13
armaxlike subports15:13
armax:)15:13
* mestery waits for this meeting to devolve to tags15:14
armaxdvr, floating ips, etc15:14
russellbi think that one is a bit different actually, but let's stay off topic here15:14
armaxif this bug reads like: prevent the deletion of service ports15:14
*** manjeets has quit IRC15:14
amotokiyes. it is not specific to dhcp ports. we need to discuss as a whole.15:14
amotokiarmax: ++15:14
armaxoh I forgot ha ports15:14
dougwigit's like the port where IT has said, "don't touch this one".  it's obvious that it's there, it will cause serious pain if you pull the wire, and it makes things go.  you can't hide it. and if the user pulls it, bad stuff happens, but hey, people are people. now do we try to duct tape over it, or lock it in, or...?  my analogy-foo is weak this morning.15:14
kevinbentonand lbaas ports15:14
*** peristeri has joined #openstack-meeting15:15
mesterydougwig: You're making sense to me, you must have had a few redbulls this morning already15:15
armaxin the case of dhcp the port is reprovisioned15:15
*** ntata has quit IRC15:15
armaxso the system is resilient to failures15:16
ihrachysI guess the whole hiding discussion could be postponed to after we don't experience any issues with the implementation :)15:16
carl_baldwindougwig: I agree with that.  There are all kinds of things that are necessary for operation and we don't babysit them all.15:16
*** okrieg has quit IRC15:16
mesteryIs anyone in favor of hiding?15:16
mesteryBecause if not15:16
armaxI personally vote to “wont-fix”, ports have been exposed since the beginning15:16
mesteryLets just move on15:16
mesteryarmax: Right, +115:16
armaxthat’s how we work15:16
carl_baldwinarmax: +115:16
dougwigarmax: +115:16
amotokican we use #action to remember what still need to be visited/discussed in the next meeting.15:16
hanzhang+115:17
armaxamotoki: I usually take action right after the meeting15:17
amotokiI think it is worth discussed for better UX.15:17
armaxamotoki: I think it’s a waste of time15:17
mesteryarmax: No do #agreed here15:17
mesterySo we can lock it in15:17
mesterylol15:17
asadoughihas it been considered to allow this to be enforced by poicy.json?15:17
*** gcb has quit IRC15:17
*** thangp has joined #openstack-meeting15:18
*** markvoelker has quit IRC15:18
armax#action armax to follow up on bug 137366015:18
openstackbug 1373660 in neutron "[RFE] An in-use dhcp port can be deleted" [Wishlist,Triaged] https://launchpad.net/bugs/137366015:18
armaxnext15:18
armaxbug #141617915:18
*** markvoelker has joined #openstack-meeting15:18
openstackbug 1416179 in neutron "[RFE] API to set & get list of provider network types" [Wishlist,Incomplete] https://launchpad.net/bugs/141617915:18
*** sgundur has joined #openstack-meeting15:18
russellbi don't think this should be configurable for interop reasons.  i also think "this is the way it has always been, waste of time to discuss changing it" is a good point.15:18
mesteryrussellb: ++15:18
*** gmmaha has left #openstack-meeting15:18
*** manjeets has joined #openstack-meeting15:18
amotokirussellb: agree on 'set' side.15:19
armaxI believe this bug is also another time waster, unless something else happens first15:19
amotokion the other hand, I think 'get' side is useful15:19
mesteryarmax: ++15:19
dougwigi'm not seeing a use case listed.15:19
amotokithat's all15:19
dougwigjust "we want to get".15:19
dougwigwhy?15:19
*** vgridnev has quit IRC15:19
*** sneti has joined #openstack-meeting15:20
dougwigdon't need to list it here.15:20
amotokidougwig: see my comment in the bug.15:20
russellbamotoki: i was actualyl referring to the last one about dhcp heh15:20
armaxwe’re talking about bug 141617915:20
openstackbug 1416179 in neutron "[RFE] API to set & get list of provider network types" [Wishlist,Incomplete] https://launchpad.net/bugs/141617915:20
armaxnow15:20
*** ntata has joined #openstack-meeting15:20
russellbget is useful if it's different per backend15:20
mesterylol15:20
dougwigamotoki: right. why is horizon maintaining that list? what's it doing in the UI?15:20
*** okrieg has joined #openstack-meeting15:20
russellbif it's hard coded then meh15:20
ihrachysarmax: on the other side, it is also a no brainer assuming we have folks to tackle it.15:21
armaxprovider networks are provisioned ahead of time15:21
amotokidougwig: horizon has a network creation form for admin. we need provider net type list.15:21
armaxunless we make their management entirely dynamic15:21
russellb+115:21
kevinbentonthis sounds fine to me, especially since it's different in different ML2 deployments, let alone other plugins15:21
armaxI can’t see what retrivieving them does15:21
russellboptimizing this thing which is largely very static doesn't seem like a good use of time15:21
*** ricolin has quit IRC15:21
mesteryrussellb: ++15:22
kevinbentonthere is no way to discover enabled type drivers IIRC15:22
dougwigamotoki: you can't just offer a list of names, and if the operator wants to expose their backend, they can do it there?15:22
armaxthe use case of making provider networks dynamic is not an easy thing to do15:22
hanzhangfor provider network, I think it should support paging list15:22
*** okrieg has quit IRC15:22
kevinbentonnot even paging or filtering, just a plain list should be plenty15:23
kevinbentonget-only15:23
hanzhangagree15:23
kevinbentonit's going to be like 1-5 items15:23
amotokiit is not exposed to users, so it is not so important, but we have similar requests several times so far. I am okay with either in this case.15:24
kevinbentonyeah, exposed to admins though15:24
amotokiI can just say neutron team rejected to expose it to horizon team.15:24
armaxjust so that we’re clear15:24
*** vijendar has joined #openstack-meeting15:24
kevinbentonno, not reject!15:24
armaxare we saying we should expose the networks that are currently hard coded here:15:24
armaxhttps://github.com/openstack/neutron/blob/master/etc/neutron/plugins/ml2/ml2_conf.ini#L6215:24
armaxthe physnet ones?15:25
kevinbentonarmax: no. i thought this was to expose which types are avialable: https://github.com/openstack/neutron/blob/master/etc/neutron/plugins/ml2/ml2_conf.ini#L615:25
amotokisorry for misunderstanding.15:25
*** bobh has joined #openstack-meeting15:26
*** subscope has quit IRC15:26
armaxkevinbenton: ok so the type drivers supported15:26
kevinbentoni think this has some value for admins needing to configure provider networks15:26
kevinbentonarmax: yes15:26
*** johnbelamaric has joined #openstack-meeting15:26
kevinbentonjust makes it a little easier for horizon or other guis15:26
armaxnot all type drviers can be applied to provider networks15:26
*** pratikmallya has joined #openstack-meeting15:27
*** maishsk has quit IRC15:27
neiljerramIt seems to me there's a general move from implementation config into the API (e.g. also bridge_mappings).  Is that really right?15:27
kevinbentonarmax: provider networks are just networks15:27
armaxfrankly I think it’s another waste of time15:27
kevinbentonarmax: of course they can15:27
armaxkevinbenton: I have never seen a vxlan provider network, but sure15:27
kevinbentonneiljerram: in ML2 the type is in the API already15:27
*** maishsk has joined #openstack-meeting15:27
*** maishsk has quit IRC15:27
armaxkevinbenton: it’s just a network15:27
neiljerramYes, that also seems not obviously right, to me15:28
kevinbentonneiljerram: file a bug15:28
kevinbentonneiljerram: the entire provider network workflow is based on it15:28
armaxsetting type drivers doesn’t make sense either15:28
armaxas they are stevedore entrypoints15:28
neiljerramkevinbenton, it possibly means I haven't understood one of the meanings of the API....15:29
kevinbentonarmax: i agree setting via the API is not necessary15:29
armaxwhy would we want to ever prevent certain types to be used I don’t understand15:29
amotokiagree settings is unnecessary15:29
armaxto me this bug is a classic example of overenginering for the sake of it15:29
armaxbah15:29
armaxI do need coffe15:29
armaxcoffee15:29
*** electrocucaracha has joined #openstack-meeting15:30
kevinbentonneiljerram: http://docs.openstack.org/networking-guide/scenario_provider_ovs.html#create-initial-networks15:30
neiljerramit's potentially worse than that, as it will also constrain us in future15:30
*** maishsk has joined #openstack-meeting15:30
dougwigamotoki: can you maybe include a screenshot of what you're trying to accomplish? i just fired up a juno horizon and can't see it on the create network dialog.15:30
kevinbentonneiljerram: these are already in the API under the network15:30
amotokidougwig: sure tomorrow.15:30
armaxwe’d be going through the trouble of creating an api endpoint, etc etc just to expose a list type drivers15:30
kevinbentondougwig: make sure you are on the admin network API15:30
kevinbentondougwig: not the tenant one15:30
*** vijendar has left #openstack-meeting15:30
armaxnow granted that the ones chosen may depend by the deployment15:31
armaxso get Horizon to have a config option as well15:31
armaxand the admin must know to set both15:31
armaxdone15:31
armaxcan we move on pleasE?15:31
russellbno!15:31
armax(facepalm)15:32
kevinbentondougwig: admin network API = admin network page15:32
njohnstonfacepalm +115:32
dougwigat 15 minutes per bug, we should be done with this meeting about... oh, is that the turkey burning?15:32
armaxrussellb: it’s a no with a reason? or no, that’s it15:32
kevinbentonnext bug15:32
russellb(yes)15:32
dougwigkevinbenton: thanks, but i'm not seeing it there either?15:32
kevinbentonthis RFE is ML2 specific15:32
kevinbentonwe can discuss it there15:32
kevinbentonon the bug report15:32
mesteryML2 ILLUMANTI!15:32
mesteryI knew it15:32
armax#action armax comment on bug 1416179 to mark it won’t fix15:33
openstackbug 1416179 in neutron "[RFE] API to set & get list of provider network types" [Wishlist,Incomplete] https://launchpad.net/bugs/141617915:33
armaxok?15:33
ihrachysconfigdb would help here.aye15:33
mesteryDid we just spend almost 20 minutes on that last bug? Wow.15:33
ihrachyssorry, disregard ^15:33
ihrachyslet's move on15:33
armax#link 151314415:33
armaxbug 151314415:33
openstackbug 1513144 in neutron "[RFE] Allow admin to mark agents down" [Wishlist,Incomplete] https://launchpad.net/bugs/151314415:33
armax#undo15:34
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x9077c50>15:34
kevinbenton(that was a good example of why ML2 should be a different project)15:34
armax#nundo15:34
armax#undo15:34
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x94b3f50>15:34
armax#link https://bugs.launchpad.net/neutron/+bug/151314415:34
mesterykevinbenton: Your thinly veiled plot at a power grab with ML2 is noted15:34
armaxI see two meetings going on here15:34
*** electrocucaracha has quit IRC15:34
amotokiwe have only <30mins. please check it after the meeting. I think it is good now.15:34
armaxamotoki: what is?15:35
amotokisorry for confusing comment.15:35
amotokii just want to say let's check bug  later 151314415:35
*** salv-orlando has quit IRC15:36
*** subscope has joined #openstack-meeting15:36
armaxamotoki: ok15:36
kevinbentonamotoki: still working out the use case?15:36
dougwigso they want to be able to mark an agent down, so things don't get scheduled to that node, and an operator can look into it manually later15:36
*** asselin_ has joined #openstack-meeting15:36
armaxamotoki: yours was a long comment, I need time to read it15:36
*** asselin has joined #openstack-meeting15:36
*** maishsk has quit IRC15:36
dougwig?15:36
kevinbentondougwig: not quite. admin_stte_false already does that15:36
dougwigthen i failed to grok the use case yet again. can someone ELI5 it?15:37
kevinbentondougwig: they need to  mark down to force rescheduling or other failover IIUC15:37
kevinbentondougwig: because admin_state_up=False prevents future scheduling15:37
*** kmARC has quit IRC15:37
dougwigso it's a "down, but do some extra goo" action?15:37
kevinbenton"mark dead"15:37
kevinbentonwould be a short description i think15:38
*** kmARC has joined #openstack-meeting15:38
amotokikevinbenton: but it prevents manual scheudling for agent with admin-state-down...15:38
armaxlet’s follow amotoki’s suggestion15:38
*** Leom has joined #openstack-meeting15:38
armaxhave a look at the bug report offline and make sure we’re prepared for the conversation next week15:38
kevinbenton+115:38
armax#action drivers to look at https://bugs.launchpad.net/neutron/+bug/1513144 offline15:38
openstackLaunchpad bug 1513144 in neutron "[RFE] Allow admin to mark agents down" [Wishlist,Incomplete]15:38
armaxnext15:38
armaxnext: bug 146479315:38
openstackbug 1464793 in neutron "[RFE] Add a driver for isc-dhcpd" [Wishlist,Triaged] https://launchpad.net/bugs/1464793 - Assigned to Shraddha Pandhe (shraddha-pandhe)15:38
mesteryIs that within scope for Mitaka?15:39
kevinbentoncan that be completely developed as a sub-project?15:39
kevinbentonor is that overkill for a subproject15:39
mesterykevinbenton: ++15:39
neiljerramdhcp_driver config should allow that, I believe15:39
armaxkevinbenton: it’s possible, but there might be adjustement to the dhcp interface15:39
dougwigwhy would we block that if someone was willing to do the work?15:39
ihrachyskevinbenton: + dhcp agent is pluggable so far15:39
armaxhaving said that, would I promote such an efforrt?15:39
*** dprince has quit IRC15:39
amotokiI think we need high level decision on this. perhaps subproject.15:39
kevinbentondougwig: nobody to review15:40
armaxpersonally I wouldn't15:40
mesteryRigth15:40
mesteryIf no one reviews, why give them false hope?15:40
*** subscope has quit IRC15:40
mesteryAlso, have you seen what is already on the list for reviewing?15:40
kevinbentonso i'm leaning towards subproject15:40
armaxbecause running processes to deliver network services is problematic15:40
armaxand we all know that15:40
mesteryWe're gonna collapse under our own weight if we're not careful15:40
*** salv-orlando has joined #openstack-meeting15:40
dougwigi like the subproject idea.15:40
armaxI don’t :)15:41
kevinbentonarmax: why not. it's a pluggable interface?15:41
dougwighaha. pistols at dawn!15:41
*** asselin_ has left #openstack-meeting15:41
mesteryI with dougwig on that one15:41
armaxnot until we fix the stadium15:41
ihrachysI believe we should be happy to review infra changes for dhcp agent pluggable interface for the subproject15:41
*** asselin has quit IRC15:41
mesteryThat's a bigger discussion armax15:41
armaxright15:41
armaxit is15:41
*** dprince has joined #openstack-meeting15:41
mesteryIt's not as dire as you frame it, but meh15:41
dougwigwhich part of the stadium are you referring to? the co-gate nastiness? or something else?15:41
kevinbenton#topic demolition of the stadium :)15:41
armaxbut I wouldn’t want to promote anyone to go on a time water15:41
armaxwaster15:41
armaxdougwig: all of the above and beyond15:42
kevinbentonarmax: so what do you propose?15:42
armaxkevinbenton: for this bug?15:42
*** asselin has joined #openstack-meeting15:42
kevinbentonyes15:42
*** okrieg has joined #openstack-meeting15:42
armaxwon’t fix :)15:42
kevinbentonwhat's wrong with a subproject?15:42
armaxbecause no-one should use it?15:42
kevinbentonnobody should use subprojects?15:43
armaxhaving centralized dhcp services is bad as it is15:43
armaxthank you very much15:43
dougwigok, we've got two religious objections going on here. can we table the stadium one, unless we make that the main topic and tackle it?15:43
kevinbentoni have a wild list of opinions about many of our subprojects but I don't think they should be blocked :)15:43
ihrachysarmax: technically, how is it different from current dnsmasq implementation?15:43
armaxdougwig: no, I am not objecting the statidum right now15:44
armaxI am only saying that we should promote healthy initiatives that benefit the project as a whole15:44
*** houming has quit IRC15:44
dougwigso is it that you don't like how dnsmasq is doing dhcp and don't want another one? or you just hate freedom of choice?  :-)  what's your ideal of how we do dhcp?15:44
armaxhaving another driver for dhcp, doesn’t seem like that useful15:44
armaxespecially if it promoted a usage pattern that is gonna cause more trouble than it’s worth15:44
ihrachysarmax: should we kill pluggable interface then? if we don't allow folks to use it, then there is no reason to keep it.15:45
mesteryI don't understand the usage pattern that a new DHCP dirver in a sub-project would cause15:45
mesteryihrachys: ++15:45
armaxwe should either invest in distributed dhcp or moving away from the model of running dhcp process altoghether15:45
*** houming has joined #openstack-meeting15:45
*** SridharG has left #openstack-meeting15:45
dougwigarmax: isn't that just another dhcp driver, though?15:45
armaxihrachys: they can use it, I just don’t want to endorse it15:45
garykwith distributed DHCP there is the issue of metadata proxies15:46
dougwigarmax: why would we pick and choose for them? isn't that the point of the stadium? letting folks do their own thing if they want?15:46
* mestery is really confused15:46
ihrachysarmax: is a comment suggesting there is a pluggable interface for them to use if they feel like an endorsement?15:46
neiljerramMy suggestion: "feel free to experiment with implementing this, but not clear yet if and how it will be integrated into core Neutron"15:46
armaxthen this ties to the shape the stadium currently is15:46
mesteryarmax: What are you talking about?15:46
armaxnm15:47
*** okrieg has quit IRC15:47
kevinbentonnext bug. i think that should be tabled until we define the stadium requirements15:47
armax#action approve yet another dhcp driver15:47
armaxwhatever15:47
mesteryWe have the stadium requirements defined15:47
mesteryI tend to think people are not happy with them15:47
mesteryWhich is fine15:47
dougwigmestery: if i understand, he's suggesting that the current model of dhcp is wonky and we should be fixing that, instead of adding another driver doing the same brokennness.15:47
mesterydougwig: That part I understood15:48
armaxbug 145755615:48
openstackbug 1457556 in neutron "[RFE] [LBaaS] ssh connection timeout" [Wishlist,Triaged] https://launchpad.net/bugs/1457556 - Assigned to Reedip (reedip-banerjee)15:48
garykare you guys talking about the agent or the dhcp pluggable driver15:48
garykcause the dnsmasq is pluggable and that can be replaced15:48
neiljerramgaryk, I think that has already been said15:48
kevinbentondougwig: i'll defer to you on that one15:49
kevinbentondougwig: it sounds reasonable15:49
*** haomaiwa_ has quit IRC15:49
amotokiI just want to pass bug 1457556 to dougwig :-)15:49
openstackbug 1457556 in neutron "[RFE] [LBaaS] ssh connection timeout" [Wishlist,Triaged] https://launchpad.net/bugs/1457556 - Assigned to Reedip (reedip-banerjee)15:49
armax#action move bug 1457556 to rfe-approved15:49
dougwigit sounds reasonable to me, except not as just exposing haproxy options directly.15:49
kevinbentondougwig: +115:50
armaxdougwig: right, they would need to be abstracted15:50
amotokidougwig: good point. do we suggest a spec?15:50
dougwigagree to approve. i don't need a spec, just a clarifying comment on the bug, similar to what blogan suggested.15:50
armaxsounds good15:50
armaxnext15:50
amotoki+115:50
armaxbug #149670515:50
openstackbug 1496705 in neutron "[RFE] A common description field for Neutron resources" [Wishlist,Confirmed] https://launchpad.net/bugs/1496705 - Assigned to Li Ma (nick-ma-z)15:50
*** salv-orlando has quit IRC15:51
russellbthe tags proposal accomplishes the same thing imo15:51
armaxweird I thought I had commented on this one15:51
armaxhang on15:51
armaxI think we have a duplicate here15:51
dougwigrussellb: spoken like a dev. :)15:52
armaxhttps://bugs.launchpad.net/neutron/+bug/148348015:52
openstackLaunchpad bug 1483480 in neutron "[RFE] Allow annotations on Neutron resources" [Wishlist,Triaged]15:52
*** banix has joined #openstack-meeting15:52
dougwigi'm pretty sure they want something wordier than a tag.15:52
ihrachysdo tags have attributes attached? if not, it's not completely the same.15:52
russellbdougwig: make a wordy tag?15:52
armaxwe should have the conversation in one place15:52
armaxwe can’t afford to talk twice :)15:52
armaxI think tags != descriptions15:52
kevinbentonyeah, they explicity say they think tags suck because you don't know which one is the description15:52
ihrachysmaybe it's easier to come up with a tag prefix concept15:52
dougwigrussellb: let's remove all the db columns and do it all with tags then?  :)15:52
russellbdougwig: sure why not15:53
russellbbut fair ... description = human readable thingy15:53
russellbfair enough.15:53
armaxlet’s have one giant table15:53
dougwigJSON STORE!15:53
ihrachyslike 'description:Whatever nice text you may want to add' tags15:53
*** achanda_ has quit IRC15:53
armaxand return the entire content in a single API response15:53
armaxdone15:53
kevinbenton'GET /neutron_state'15:53
armaxkevinbenton: get /all15:53
dougwigi feel the pacific timezone affecting my snark level.  :)15:53
amotoki:)15:53
armaxjokes aside15:54
garyki think that tags are super useful and helpful15:54
armaxI think we have a duplicate here15:54
*** Liuqing_ has quit IRC15:54
kevinbentonright, i don't think anyone is saying tags don't work15:54
*** pratikmallya has quit IRC15:54
armaxI marked https://bugs.launchpad.net/neutron/+bug/149670515:54
openstackLaunchpad bug 1483480 in neutron "duplicate for #1496705 [RFE] Allow annotations on Neutron resources" [Wishlist,Triaged]15:54
armaxduplicate15:54
kevinbentonwhat they want is a named field for the description though15:54
armaxof https://bugs.launchpad.net/neutron/+bug/148348015:54
openstackLaunchpad bug 1483480 in neutron "[RFE] Allow annotations on Neutron resources" [Wishlist,Triaged]15:54
dougwiggaryk: this is not a tag discussion. this is a discussion of whether other new fields are new fields are just specialty tags, which i don't tend to agree with.15:54
dougwig /are just/or just/15:54
armaxI think adding a description field may be handy15:55
dougwigarmax: +115:55
russellbdesc seems fine15:55
ihrachysthen should we define tags as attributes with no value attached?15:55
amotokiarmax: +115:55
kevinbentonarmax: then why did you mark as duplicate?15:55
armaxbecause as a user I may want to add my grocery shopping list to my dhcp port in use15:55
armaxbecasue it’s two of them that are saying the same thing?15:55
armaxkevinbenton: ^15:55
dougwigarmax: lol15:55
neiljerramnot a good idea if the port is then deleted15:55
armaxneiljerram: oh right15:55
garykdolphm:15:55
kevinbentonarmax: no, one was saying they still need description even with tags15:55
armaxkevinbenton: right15:56
armaxkevinbenton: we have two bugs that both are about description15:56
garykdougwig: yeah, i got that. i just think that if we do go down the road for tags and defer or duplicate other stuff in favor of that then we should make sure that have the correct priority for tags15:56
armax#action make description the new black15:56
kevinbentonarmax: oh, whoops. i thought you made description a dup of tags15:56
armaxbtw I think from now on15:57
armaxwe should review bugs in order of submission15:57
armaxfrom the oldest to the youngest15:57
kevinbentonarmax: +115:57
armaxjust an opinion15:57
njohnstonwhat is the current ordering?15:57
kevinbentonand this meeting should be extended to 4 hours15:57
*** subscope has joined #openstack-meeting15:57
armaxnjohnston: it depends15:57
dougwigwe should timebox each bug at like 5 minutes.15:57
ihrachysI also think if drivers don't keep up in 1h, maybe 2h per week would be a better deal.15:57
kevinbentonwe hardly get the paint out before it's over15:58
mesterynjohnston: The current order is defined by a user pluggalbe scheduler, today's scheduler plugin was from amotoki and HenryG15:58
armaxihrachys: let’s have a week retreat in the caymans15:58
-amotoki- 's sleeping time will be stealed...15:58
ihrachysarmax: you pay15:58
ihrachysamotoki: sleeping time is overrated15:58
njohnstonarmax: got it, thanks15:58
armaxihrachys: I thought you’d cover with the gift card I gave you yesterday15:58
kevinbentonwe need a pluggable drivers meeting scheduler that receives vectors of RFE attribute weights and...15:58
armaxok, folks thanks for the very entertaining discussion, I love you all15:58
ihrachysarmax: I will, virtual caymans with that virtual card15:58
armax#endmeeting15:58
*** openstack changes topic to "swiftclient (Meeting topic: swift)"15:59
kevinbentonnext bug!15:59
openstackMeeting ended Tue Nov 24 15:58:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-11-24-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-11-24-15.01.txt15:59
kevinbentonwe still had a minute15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-11-24-15.01.log.html15:59
dougwighmm, did ihrachys just hint at the usefulness of a... MID-CYCLE?15:59
dougwig:)15:59
* dougwig runs.15:59
amotokitoday's scheduler shows random order of bugs :(15:59
amotokithanks15:59
*** pratikmallya has joined #openstack-meeting15:59
kevinbentondougwig: armax doesn't like mid-cycles because he flies united15:59
*** subscope has quit IRC15:59
ihrachyskevinbenton: lol15:59
mesterylol15:59
*** achanda has joined #openstack-meeting15:59
dougwigkevinbenton: ahh, so he likes being treated like human garbage.15:59
armaxkevinbenton: I am not even going to entertain a response to that15:59
njohnstonlol15:59
dougwigarmax: probably because united charges by the word.16:00
* armax walks aways in disdain16:00
*** aspiers has joined #openstack-meeting16:00
kevinbenton:P16:00
*** salv-orlando has joined #openstack-meeting16:00
*** vthapar has joined #openstack-meeting16:00
*** vthapar has left #openstack-meeting16:00
*** zhipeng has joined #openstack-meeting16:01
*** pratikma_ has joined #openstack-meeting16:03
*** sgundur has left #openstack-meeting16:03
*** juggler has joined #openstack-meeting16:04
*** otter768 has joined #openstack-meeting16:04
*** salv-orlando has quit IRC16:04
*** amitgandhinz has joined #openstack-meeting16:05
*** pratikmallya has quit IRC16:05
*** numans has quit IRC16:06
*** ericksonsantos has joined #openstack-meeting16:07
*** klkumar has quit IRC16:08
*** lazy_prince has joined #openstack-meeting16:08
*** klkumar has joined #openstack-meeting16:08
*** aranjan has joined #openstack-meeting16:09
*** okrieg has joined #openstack-meeting16:09
*** otter768 has quit IRC16:09
*** okrieg has quit IRC16:09
*** edgar__ has joined #openstack-meeting16:09
*** whenry_ has joined #openstack-meeting16:10
*** nmagnezi has quit IRC16:10
*** vgridnev has joined #openstack-meeting16:11
*** amitgandhinz has quit IRC16:12
*** egallen has quit IRC16:16
*** matrohon has quit IRC16:16
notmynamemordred: can you reset the channel topic please?16:16
*** egallen has joined #openstack-meeting16:16
notmynamemordred: meeting bot died in the middle of the swift meeting last week, and the topic toggle got out of sync16:16
*** okrieg has joined #openstack-meeting16:16
*** rossella_s has quit IRC16:17
*** egallen has quit IRC16:17
*** rossella_s has joined #openstack-meeting16:18
*** dneary has quit IRC16:18
*** okrieg has quit IRC16:20
*** alexschm has quit IRC16:20
*** okrieg has joined #openstack-meeting16:20
*** okrieg has quit IRC16:21
*** rossella_s has quit IRC16:21
*** hanzhang has quit IRC16:21
*** rossella_s has joined #openstack-meeting16:22
*** wbhuber_ has joined #openstack-meeting16:22
*** Guest72939 has quit IRC16:22
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:23
*** achanda_ has joined #openstack-meeting16:23
*** rods has joined #openstack-meeting16:23
*** harshs has joined #openstack-meeting16:24
*** rromans is now known as rromans_afk16:26
*** _amrith_ is now known as amrith16:26
*** wbhuber_ has quit IRC16:26
*** achanda has quit IRC16:26
*** okrieg has joined #openstack-meeting16:26
*** wbhuber_ has joined #openstack-meeting16:27
*** navneet has joined #openstack-meeting16:29
*** lazy_prince has quit IRC16:29
*** rebase has joined #openstack-meeting16:30
*** navid_ has joined #openstack-meeting16:30
*** dims_ has quit IRC16:30
*** xingchao has quit IRC16:31
*** wbhuber_ has quit IRC16:31
*** rebase_ has joined #openstack-meeting16:31
*** zaneb has quit IRC16:32
*** matrohon has joined #openstack-meeting16:32
*** jdurgin1 has joined #openstack-meeting16:32
*** iyamahat has joined #openstack-meeting16:33
*** korzen has quit IRC16:33
*** zaneb has joined #openstack-meeting16:34
*** okrieg has quit IRC16:34
*** rebase has quit IRC16:34
*** vahidh has joined #openstack-meeting16:34
*** bobh has quit IRC16:35
*** navneet has quit IRC16:36
*** sgundur has joined #openstack-meeting16:36
*** vivek-ebay has joined #openstack-meeting16:36
*** xingchao has joined #openstack-meeting16:40
*** salv-orlando has joined #openstack-meeting16:41
*** salv-orlando has quit IRC16:41
*** salv-orlando has joined #openstack-meeting16:41
*** aranjan has quit IRC16:42
*** xingchao has quit IRC16:42
*** dims has joined #openstack-meeting16:46
*** dmowrer_ has joined #openstack-meeting16:47
*** jdurgin1 has quit IRC16:48
*** zhipeng has quit IRC16:48
*** bobh has joined #openstack-meeting16:49
*** adiantum has quit IRC16:49
*** dmowrer has quit IRC16:49
*** scheuran has quit IRC16:50
*** bnemec has quit IRC16:50
*** Swami has joined #openstack-meeting16:51
*** kbyrne has quit IRC16:53
*** dprince has quit IRC16:54
*** vivek-ebay has quit IRC16:56
*** dandruta has quit IRC16:56
*** e0ne has quit IRC16:58
*** dprince has joined #openstack-meeting16:59
*** dmowrer_ has quit IRC16:59
asselin#startmeeting third-party16:59
openstackMeeting started Tue Nov 24 16:59:48 2015 UTC and is due to finish in 60 minutes.  The chair is asselin. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: third-party)"16:59
openstackThe meeting name has been set to 'third_party'16:59
asselinHI, who's here for 3rd party ci working group meeting?17:00
mmedvedeo/17:00
asselinhi mmedvede17:01
mmedvedehi asselin17:01
*** johnbelamaric has left #openstack-meeting17:01
asselin#link agenda https://wiki.openstack.org/wiki/Meetings/ThirdParty17:01
krtayloro/17:01
asselinhi krtaylor17:02
krtaylorhey everybody17:02
asselin#topic announcements17:02
*** openstack changes topic to "announcements (Meeting topic: third-party)"17:02
asselinJenkins security issue (for those with publicly accessible Jenkins setups)17:02
asselin#link https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli17:03
asselin#link https://review.openstack.org/#/c/242787/ (merged)17:03
*** brucet has joined #openstack-meeting17:03
asselinany other announcements?17:03
asselin#Topic CI Watch17:04
*** openstack changes topic to "CI Watch (Meeting topic: third-party)"17:04
*** s3wong has joined #openstack-meeting17:04
*** gampel1 has quit IRC17:04
asselinmmedvede, and apporva (sp?) have been making a lot of progress on this17:05
*** shihanzhang has quit IRC17:05
asselinmmedvede, want to give a quick update?17:05
*** ja3 has joined #openstack-meeting17:05
mmedvedeasselin: sure17:05
*** liusheng has quit IRC17:05
*** shihanzhang has joined #openstack-meeting17:05
*** liusheng has joined #openstack-meeting17:06
*** jlanoux_ has quit IRC17:06
mmedvedeI have been working on a couple of bugs that would have prevented it from working smoothly once deployed17:06
mmedvedethe most recent one is gerrit event listener not recovering after connection loss17:06
*** kcalman has joined #openstack-meeting17:06
mmedvede#link https://review.openstack.org/24891917:07
*** dmacpher is now known as dmacpher-afk17:07
*** sdake_ has joined #openstack-meeting17:07
mmedvedeOverall, I'd like to concentrate on getting some unit tests implemented17:07
mmedvederight now there are zero :)17:07
kcalmano/17:07
*** sdake has quit IRC17:07
asselin+117:08
mmedvedeActive work is tracked under ci-dashboard topic17:08
mmedvede#link https://review.openstack.org/#/q/status:open+%28topic:ci-dashboard%29,n,z17:08
*** okrieg has joined #openstack-meeting17:09
mmedvedeasselin: that is a gist of it17:09
mmedvedeoh, and there is a lunchpad bugs for it as well17:09
asselinmmedvede, yeah, was looking at that patch. reuse is definitely a good thing!17:09
*** leeantho has joined #openstack-meeting17:09
mmedvede#link ciwatch bugs  https://bugs.launchpad.net/ciwatch17:10
Swansonhi17:11
*** notmorgan has joined #openstack-meeting17:11
mmedvedethis is all I have on ciwatch for now17:11
asselinmmedvede, thanks for working on this.17:12
asselinanything else anyone wants to add re ci-watch?17:12
*** ayoung has quit IRC17:13
asselin#topic Common-CI Solution17:13
*** openstack changes topic to "Common-CI Solution (Meeting topic: third-party)"17:13
*** ShillaSaebi has joined #openstack-meeting17:13
asselinSo we have a "working" solution merged: Merged! http://lists.openstack.org/pipermail/openstack-dev/2015-November/080058.html17:14
asselin#link Merged! http://lists.openstack.org/pipermail/openstack-dev/2015-November/080058.html17:14
*** dmowrer has joined #openstack-meeting17:14
mmedvede\o/17:14
asselinthere were a few issues found regarding integrating the log server17:14
asselin#link Allow external Jenkins Plugins https://review.openstack.org/24822317:14
asselin#link Install custom OpenStack scp jenkins plugin https://review.openstack.org/24822617:14
asselinI think just those 2 patches left not yet merged ^^17:15
*** ShillaSaebi has quit IRC17:15
asselinSwanson, how is your setup going?17:15
*** rdopiera has left #openstack-meeting17:16
SwansonI got everything running.  Just doesn't work yet.  If you get my meaning.17:16
asselinSwanson, not sure I get your meaning....17:16
*** nadya_ has quit IRC17:17
*** sdake_ has quit IRC17:17
SwansonJenkins is up.  Nodepool is up.  Log server is up.  Devstack is up.  Having merge issues and nothing is spinning off nodes.17:17
ja3sounds like all the components are "running", just not correct output yet17:17
asselinSwanson, do you want to discuss your issues now or later/offline?17:18
*** dmowrer has quit IRC17:18
*** dims has quit IRC17:18
*** dims_ has joined #openstack-meeting17:18
SwansonWhere is the best place to look for the failure17:19
Swanson(To start to look for the failure.)17:19
asselinI see...a troubleshooting section is needed17:19
*** david-ly_ has joined #openstack-meeting17:19
*** matrohon has quit IRC17:19
Swanson2015-11-24 09:25:11,686 INFO zuul.MergeClient: Merge <gear.Job 0x7f00383a4b50 handle: H:127.0.0.1:44 name: merger:merge unique: 89e15a9ff54a478fa17ad1136d428a4c> complete, merged: False, updated: False, commit: None17:19
SwansonThat's the sort of thing I'm wondering about.17:20
asselinSwanson, that looks like zuul-merger pulled down a patch.17:21
asselinSwanson, in /var/log/zuul/debug.log you should see more details17:21
asselinperhaps search for those ids 89e15a9ff54a478fa17ad1136d428a4c17:22
*** ihrachys has quit IRC17:22
SwansonThat would be the lone line.17:23
*** aspiers_ has joined #openstack-meeting17:23
Swanson(At least with that Id17:23
*** bobh has quit IRC17:23
asselinSwanson, anything in the /var/log/zuul/merger-debug.log file?17:23
*** david-l__ has joined #openstack-meeting17:23
*** david-ly_ has quit IRC17:23
*** david-lyle has quit IRC17:23
*** ygbo has quit IRC17:24
SwansonWell, based on the fact I don't see a merger-debug.log file I'm going to guess that that is my problem.17:24
*** cwolferh has joined #openstack-meeting17:24
asselinSwanson, there should be 3 processes running: https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md#n22117:24
SwansonNope, there it is.  Too many windows and fingers aren't working...  sigh.17:25
SwansonCould not read from remote repository.17:26
*** harshs has quit IRC17:26
Swansonhost key verification failed.17:26
*** aranjan has joined #openstack-meeting17:26
*** aspiers has quit IRC17:26
*** kylek3h has quit IRC17:26
*** ayoung has joined #openstack-meeting17:26
asselinSwanson, you're using the default? review.openstack.org?17:26
SwansonYep17:27
asselinok....let's take it offline17:27
mmedvedeI would try manually cloning any repo on zuul. Puppet does setup review.o.o host key, but it does not always work17:27
*** ddeja has left #openstack-meeting17:28
asselin#action asselin investigate host key verification failed issue with Swanson17:28
*** yamamoto has quit IRC17:29
asselinyeah, I'd like to see why it doesn't always work. I think I remember someone else having a similar issue17:29
SwansonIt wouldn't be as simple as me needing to accept the RSA fingerprint would it?17:29
*** david-l__ has quit IRC17:30
*** bogdando has quit IRC17:30
asselinSwanson, yes, as zuul user17:30
mmedvedeSwanson: it might be. But you might need to 'su zuul' first17:30
asselinor sudo su - zuul17:30
asselinSwanson, but that should be setup correctly17:31
asselinSwanson, you can take a look at /home/zuul/.ssh/known_hosts17:31
*** banix has quit IRC17:32
SwansonI see no keys.  Guessing that would be my issue.  :)17:32
*** dmowrer has joined #openstack-meeting17:33
asselinSwanson, if you rerun puppet apply /etc/puppet/manifests/site.pp does it create it?17:33
asselin(run as root)17:33
asselinpuppet apply -v17:33
asselin(verbose)17:33
*** scinawa has joined #openstack-meeting17:34
*** houming has quit IRC17:34
asselinkcalman, hi, I don't think we met. While Swanson checks his system, would you like to introduce yourself?17:35
*** derekh has quit IRC17:35
SwansonIt ccreates a known host.  No other keys, however.17:36
SwansonAnd we can take this offline.17:36
asselinok17:36
asselin#topic open discussion17:37
*** openstack changes topic to "open discussion (Meeting topic: third-party)"17:37
asselinany other topics to discuss?17:37
*** mbound_ has quit IRC17:37
mmedvedeI can add on ciwatch - I am running a personal VM with the most recent ciwatch deployed http://52.23.200.77:5000/, if people want to test it. No guarantees, can go down any time17:38
asselin#link mmedvede's public test ci watch deployment  http://52.23.200.77:5000/17:39
mmedvedethx asselin17:40
asselinok, if there's nothing else we can end the meeting.17:40
*** banix has joined #openstack-meeting17:40
asselin#endmeeting17:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:40
openstackMeeting ended Tue Nov 24 17:40:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-16.59.html17:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-16.59.txt17:40
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-11-24-16.59.log.html17:40
asselinSwanson, you want to meeting in -cinder or -infra?17:41
Swansonasselin, cinderr17:41
Swansonasselin, cinder17:41
asselinok17:41
*** bobh has joined #openstack-meeting17:42
*** xingchao has joined #openstack-meeting17:43
*** david-lyle has joined #openstack-meeting17:44
*** electrofelix has joined #openstack-meeting17:46
*** zehicle has quit IRC17:48
*** xingchao has quit IRC17:48
*** maishsk has joined #openstack-meeting17:49
*** shashank_hegde has joined #openstack-meeting17:50
*** ijw has joined #openstack-meeting17:50
*** yamahata has joined #openstack-meeting17:51
*** klkumar has quit IRC17:51
*** ja3 has quit IRC17:51
*** xingchao has joined #openstack-meeting17:54
*** davechen has joined #openstack-meeting17:54
*** pratikmallya has joined #openstack-meeting17:54
*** pratikmallya has quit IRC17:54
*** pratikmallya has joined #openstack-meeting17:54
*** pratikma_ has quit IRC17:56
*** maishsk has quit IRC17:56
*** nmagnezi has joined #openstack-meeting17:57
*** xingchao has quit IRC17:58
*** ihrachys has joined #openstack-meeting17:59
stevemarhello!17:59
stevemar#startmeeting keystone17:59
openstackMeeting started Tue Nov 24 17:59:40 2015 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.17:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:59
*** openstack changes topic to " (Meeting topic: keystone)"17:59
openstackThe meeting name has been set to 'keystone'17:59
lbragstadstevemar o/17:59
stevemarping ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rodrigods, roxanaghe, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub, rderose, samleon, xek, MaxPC17:59
davecheno/17:59
raildoolá o/18:00
*** breton has joined #openstack-meeting18:00
*** henrynash has joined #openstack-meeting18:00
amakarovhey!18:00
bretono/18:00
marekdhi18:00
*** ajayaa has joined #openstack-meeting18:00
navid_o/18:00
henrynash’tis the season to be merry....18:00
*** sacharya has joined #openstack-meeting18:00
henrynashoh, no, that’s later18:00
*** samleon has joined #openstack-meeting18:00
*** roxanaghe_ has joined #openstack-meeting18:00
*** ivar-lazzaro has joined #openstack-meeting18:00
ajayaao/18:00
dstanekhenrynash: this season makes me grumpy18:00
*** david8hu has joined #openstack-meeting18:00
*** xek_ has joined #openstack-meeting18:01
samueldmqoi :)18:01
*** e0ne has joined #openstack-meeting18:01
henrynashdstanek: you be grumpy, I’ll be sneezy18:01
stevemar#topic Mid-cycle survey18:01
*** openstack changes topic to "Mid-cycle survey (Meeting topic: keystone)"18:01
xek_o/18:01
david8hu\o18:01
*** manjeets has left #openstack-meeting18:01
stevemarcheck the mailing list http://lists.openstack.org/pipermail/openstack-dev/2015-November/080299.html18:01
*** brucet has quit IRC18:01
stevemartheres a survey please fill it ou!t!18:01
*** irenab has joined #openstack-meeting18:01
*** clayg has left #openstack-meeting18:01
stevemarany questions about mid cycle?18:02
bknudsonsorry to tell you this, but Winterfell has been destroyed18:02
stevemarbknudson: shhh spoilers!18:02
lbragstadspoiler alert!18:02
dstaneki should have written in Cleveland for location18:02
*** navneet has joined #openstack-meeting18:02
stevemarso no questions :)18:02
davechenhas filled.18:03
henrynashstevemar: filed18:03
stevemarty davechen and henrynash18:03
*** david-lyle has quit IRC18:03
stevemargonna skip the next topic18:03
stevemar#topic Backend driver versioning18:03
*** openstack changes topic to "Backend driver versioning (Meeting topic: keystone)"18:03
stevemarhenrynash: its all you18:03
henrynashok18:03
*** navneet has left #openstack-meeting18:03
henrynashso i happen to have to be the person to write the first new driver version18:03
henrynash https://review.openstack.org/#/c/242853/18:04
*** pratikmallya has quit IRC18:04
henrynashbut dtsanek and I have been debating exaclty how this should work…and more importantly what the goals18:04
henrynashare18:04
*** sacharya has quit IRC18:04
henrynashsee his thoughts here: https://gist.github.com/dstanek/756337141e5e0066ebce18:04
*** otter768 has joined #openstack-meeting18:05
henrynashquestion 1: Is the main goal of driver versioning to ensure we can update to a release and someones customer driver still works?18:05
*** vahidh has quit IRC18:05
dstaneksome of this we knowingly deferred because of time constraint to get versioning into the L release and we didn't know all the issues that would come up18:05
bknudsonthat's the goal18:05
bknudsonwhy was there a time constraint to get versioning into L?18:06
bknudsonwe'd rather get some code in rather than get the right code in?18:06
*** aimon_ has quit IRC18:06
henrynashbknudson: I don’t the code was necessarily wrong, just that I don’t think anyone fully thought out eactly HOW we would create a new version!18:07
dstanekbknudson: no, it's not about right code. these are things that need to be decided when creating the first updated version18:07
henrynashI’ll lay out the two extremes18:08
dstanekbknudson: we talked about some of the things i listed in my gist, but decided we could defer since they don't change the overall stragegy18:08
dstanekor strategy18:08
henrynashextreme support says:18:08
henrynash1) We keep the current driver and the n-1 driver in tree, all the code etc.18:08
bknudsonwe're going to need the n-1 driver for testing18:09
henrynash2) We support different SQL models between the drivers, if teh new one has changed18:09
bknudsonSQL model assumes the driver is SQL... not sure what that has to do with it18:09
henrynash3) we (somehow) allow db_sync to be directed to upgrade to the right model based on driver version choice18:09
*** otter768 has quit IRC18:09
dstanekbknudson: the current review copies the old SQL driver (including model) so that someone can use it if they wanted18:10
bknudsonhow did SQL get mixed in with this?18:10
henrynashbknudson: so I am assuming (maybe incorrectly) that custom drivers are not necessarily just differnet backend technologies, but could be a modified version of our own SQL driver, say18:11
*** shaleh has joined #openstack-meeting18:11
dstanekbknudson: essentially all of our V8 assignment drivers are being supported for one more release; i would rather not do this and just support the V8 interface18:11
*** david-lyle has joined #openstack-meeting18:11
bknudsonthe database schema is for the keystone sql driver. If someone wants a custom driver that uses their own database schema then they need to write their own migrations and models18:11
bknudsony, it's just the interface that we say is supported18:11
lbragstadbut what if we change the shema and the new version wants to use the new schema?18:11
bknudsonthat implies the old drivers will still work.18:12
*** ayoung has quit IRC18:12
bknudson(in the SQL case, the old drivers with our old schema)18:12
dstaneklbragstad: i address that in the gist18:12
*** hemna has quit IRC18:12
dstanekadapt the old driver18:12
*** ayoung has joined #openstack-meeting18:12
* stevemar is back18:12
lbragstaddstanek ah, gotcha18:12
notmorganthe versioned drivers was really about the interface itself that keystone communicates to.18:12
*** claudiub|2 has quit IRC18:12
notmorganif the backend datastore has to change, you need to adapt t it. but the driver interface keystone expects would remain consistent18:13
*** shashank_hegde has quit IRC18:13
henrynashbknudson, notmorgan: Ok, so that’s a useful clarification….and I think this get’s much simpler in thatcase18:13
notmorganif somoene is subclassing the SQL driver and we change the schema... thye kindof are on their own there - there be dragons18:13
ayounghenrynash, its to keep people from me doing things like breaking Dreamhost's custom in house Identity driver18:13
*** achanda has joined #openstack-meeting18:13
ayoungagain18:14
notmorganbut in reality, i expect someone to write their own (mongo?) data store for this, and therefore wouldn't hit the "the schema changed" issue18:14
notmorganor the like18:14
dstaneksounds like most agree with the concepts from my gist then.... if that's the case i'll put the content into our documentation to clarify this18:15
henrynashnotmorgan: and I agree with that….and if we are all agreed that we are NOT trying to ensure someons sub-classed n-1 SQL driver will magically work, then I think we have a clearer way forward18:15
henrynashdtsanek: agreed18:15
ayoungnotmorgan, henrynash so, to make explicit;  we will start a new version of a driver at the start of a cycle (or when required) and that version will stay open for changes for the durecation of that release, to be closed to modification upon RC1?18:15
bknudsonso the manager is going to have to check if the driver is V8 and if so insert the adapter18:15
notmorganhenrynash: aboslutely on point - never try and be magical with the datastore. if they subclass they take on the risks of subclassing18:15
henrynashbknudson: yes18:16
dstanekbknudson: i think that's the best approach. otherwise you'd sprinkle in versioned code all over the manager18:16
shalehnotmorgan: we should be clear about that in comments and documentation18:16
topolo/18:16
notmorganshaleh: yes18:16
dstanekwhen V8 isn't supported then delete the V8 adapter18:16
notmorgandstanek: ++18:16
*** achanda_ has quit IRC18:17
dstanekshaleh: yes, post meeting i'll work on that18:17
henrynashok, I think we have agreement on direction…dstanek and I can take it from here18:17
dstanek#action dstanek to update the documentation18:17
samueldmqso all we need to have is a v(X-1) -> vX adapter (where X is the current version)18:17
samueldmqbut we also need to keep a copy of the old drivers (as you're doing) so tht we can test the adapter, right ?18:18
samueldmqhenrynash:  ^18:18
*** vivek-ebay has joined #openstack-meeting18:18
*** neelashah has quit IRC18:18
henrynashsamueldmq: yes, that is probably true…..18:18
stevemarhenrynash and dstanek thanks for championing this effort18:18
samueldmqhenrynash: nice18:18
samueldmqstevemar: ++18:18
dstaneksamueldmq: keeping the copy is a case by case, i think. we need enough to guanarantee the adapter works to fulfill the contract18:18
*** neelashah has joined #openstack-meeting18:19
stevemarnext topic time18:19
dstaneki'd rather not over constrain because that may stop good ideas from appearing18:19
ayoung notmorgan, henrynash so, to make explicit;  we will start a new version of a driver at the start of a cycle (or when required) and that version will stay open for changes for the durecation of that release, to be closed to modification upon RC1?18:19
*** kebray has joined #openstack-meeting18:19
ayoungI'd like a yay/nay on tyhat18:19
ayoungthat18:19
samueldmqdstanek: I agree... if we are just removing some methods (this case) perhaps we don't need a copy, but I'd take that as the general rule for simplicity18:19
henrynashayoung: yes (although RC1 or M3 might be debatable)18:19
ayoungagreed18:20
dstanekayoung: yes18:20
ayoungthanks18:20
stevemarayoung: i think that is agreeable18:20
*** kevinbenton has quit IRC18:20
stevemar#topic Call for keystone-spec reviews18:20
*** openstack changes topic to "Call for keystone-spec reviews (Meeting topic: keystone)"18:20
ayoungHMT time?18:20
ayoungAh...18:20
stevemarayoung: this will be quick18:20
dstanekhyper multi threading?18:21
stevemarplease review specs! if you do, i will buy you beer and puppies18:21
notmorgandstanek: hypercube magical time?18:21
dstaneksold!18:21
stevemarMitaka-1 ends around Dec 1-318:21
lbragstadstevemar i'll hold you to that!18:21
* notmorgan throws peanuts at stevemar18:21
henrynashstevemar: action: stevemar to buy beer and puppies18:21
stevemarnotmorgan: i think we usually have a spec freeze after m1?18:22
xek_lbragstad, I think I addressed your comments in the online schema migration spec18:22
dstanekstevemar: is that 1 beer per review (or 2)?18:22
lbragstadI'll take a chocolate lab and a IPA, please18:22
*** kebray has quit IRC18:22
notmorganstevemar: i always drove for that freeze18:22
marekddstanek: depending if you voted abs(1) or abs(2)18:22
lbragstadxek_ awesome, I'll be sure to take another look today18:22
*** achanda has quit IRC18:22
stevemar*amounts of beer and puppies are up for debate later18:22
notmorganstevemar: but you're the PTL you get to make policy here :)18:22
stevemarnotmorgan: cool18:22
stevemarso we'll keep it the same :)18:22
dstanekstevemar: there are lots of old specs18:22
stevemarm1 is spec freeze18:22
*** kebray has joined #openstack-meeting18:22
stevemardstanek: there are18:22
ayoungM1 Will work for me, but then, I've pushed my specs through already, so that would be selfish of me18:22
stevemari've tried to highlight ones here: https://gist.github.com/stevemart/46d664e486e2edce497218:23
* notmorgan is not submitting specs...sooo18:23
topolstevemar when is m1 again?18:23
* notmorgan has no horse in this race18:23
marekddec 318:23
stevemartopol: dec 1-318:23
dstanekshould we abandon without prejudice?18:23
notmorgandstanek: i like abandoning with predjudice18:23
stevemardstanek: if you feel the need, go ahead18:23
topolwell now I know how I am spemding my thanksgiving... reviewing!18:23
ayoungdstanek, all specs should be proposed against backlog.  We can always approve backlogged specs, just they don't get commitmnet for Mitaka18:23
stevemari would like it if we concentrated on ones we spoke about at the summit18:23
dstanekstevemar: great. i'll go ahead to walk you gist and get reviewing18:23
notmorgantopol: you know you'd do it anyway (and you like it)18:24
*** lhcheng_ has joined #openstack-meeting18:24
topolnotmorgan :-)18:24
stevemarprioritize specs that are targeting mitaka and not backlog18:24
ayoungBTW. Can I get a vote on https://review.openstack.org/#/c/244694/  and, if the team agrees to it, I willremove the -218:24
dstanekayoung: yeah, we just have to decide if it's something that we'd want to support18:24
bretonstevemar: that's a freeze for mitaka/, not for backlog, right?18:25
stevemarbreton: yep18:25
bretongreat18:25
dstanektopol: i have family stuff. so yeah, reviewing will keep me sane18:25
stevemarthank you for your reviews in advance :)18:25
lbragstadayoung dstanek I had a bunch of questions on that one18:26
davechenis the spec from backlog approved , still can get the code in?18:26
topolbuckeyes lost, yellow jackets stink.   football season is over anyway18:26
stevemarokay, HMT time, i'll give you guys a heads up when it's wrap up time, there is a lot on the list18:26
ayoungok18:26
ayoungshort bit on HMT:18:26
stevemar#topic Hierarchical Naming18:26
*** openstack changes topic to "Hierarchical Naming (Meeting topic: keystone)"18:26
ayoungWe make it possible to make URLS out of the names18:26
stevemardavechen: depends on the impact18:27
davechengotcha.18:27
ayoungto do that, a domain (and  possibley prject) name is URL safe18:27
marekdayoung: ++18:27
stevemardavechen: functional testing, np. huge function, mehh, we'll have to discuss :)18:27
henrynashSee proposal:  https://review.openstack.org/#/c/248083/18:27
ayoungno / no @ no characters that mess up a URL scheme18:27
ayoungwe make it a config option to go strict18:27
ayoungif you go strict, then all non-complying domains get disabled18:28
ayoungits an opt in18:28
shalehayoung: why not support &entity; style escaping?18:28
*** bobh has quit IRC18:28
ayoungbut you need to opt in in order to get HTM naming18:28
samueldmqhenrynash: ayoung: what's the advantage of making names URL-safe ?18:28
bknudsonURLs use %xx18:28
samueldmqis that we can easily pick a separator for representing the hierarhcy ?18:28
ayoungshaleh, we can make that a potential porting technique, but the short is we don'18:28
shalehbknudson: right, thanks18:28
henrynashsamueldmq: so we can, eventually, say: auth on domain/projectA/projectB18:28
henrynashor something liek that18:29
*** dmowrer has quit IRC18:29
ayoungt want to chage OS_DOMAIN_NAME, OS_PROJECT_DOMAIN_NAME env vras and the like, so the integration with everything else still works18:29
samueldmqhenrynash: so yes, we can easily pick / as the separator for representing the hierarchy18:29
marekdhenrynash: so a separator would be  hardcoded, say '/'18:29
ayoungso if I have a domain named customers18:29
samueldmqhenrynash: that was my only remaining question  on that18:29
ayoungI can make a domain named customers/pepsi and customers/coke18:29
*** yamamoto has joined #openstack-meeting18:29
shalehin general I like this proposal. But, there are sure to be people out there that it impacts. Which is why some form of escaping for existing coupled with checks on new would be a good idea.18:29
ayoungand use that full name in the env vars etc18:29
dstanekhaving a / as a separator feels like it would make routes hard to write18:29
henrynashmarekd: the current proposal does not specifiy what separator we use, just that we enbale that support in the future18:30
marekdhenrynash: i am talking long term - we would eventually choose something, probably '/'18:30
henrynashmarekd: sure18:30
raildoI'd rather choose the separator as a config option18:30
ayoungshaleh, since it would be a top level name...we might be able to work out some escaping, but the user would have to only use the escaped version18:30
*** harshs has joined #openstack-meeting18:30
notmorgani like using the ASCII Bell character as the delimiter...18:30
notmorgan>.>18:30
shalehayoung: agreed18:30
henrynashraildo: thats fine, but not part of this spec18:30
ayoungso  if they had red/hat  it would become red%whateverhat18:31
marekda dot is acceptable?18:31
*** fitoduarte has joined #openstack-meeting18:31
shalehayoung: we could provide library assistance for that easily enough18:31
raildohenrynash: yeap, I know but I'm just saying :P18:31
ayoungmarekd, I think it is18:31
henrynashthe only thing this spec does is provide a path to get domains and projects to NOT use anu url reserved charcacters18:31
ayoungyou can do http://hostname/this.is.my.url18:31
samueldmqhenrynash: +1 from me18:31
*** zeih has quit IRC18:31
topolraildo would making the separator a config option make interoperability more problematic?18:32
ayoungand a relatvie url with this.is.my.url/test.html18:32
marekdayoung: ++ i like dot as it more reflects dns18:32
ayoungtopol, its not the separateo that is up for discussion18:32
marekdayoung: ++18:32
ayoungthe domain nesting will be URL based18:32
henrynashI would suggest, in the interests of time, we defere debate on teh separator itself…it is not part of the spec up for review here18:32
topolayoung  agreed but a question to ponder over turkey18:32
topolagreed18:32
samueldmqhenrynash: ++18:32
dstanekhenrynash: ++18:33
raildotopol: we can discuss later about it :)18:33
stevemarso why was this not included in the initial HMT stuff?18:33
marekdhenrynash: ayoung ok, so i think it was not super clear from the spec that enabling this naming convention (names url safe) automatically disable non compliant domains/projects18:33
ayounghenrynash, so, it sounds like you and I are in sync?  Let me know if  htere are any other goblins hiding that you've spirited out, ok?18:33
shalehas voice for the end-user, I like this spec we just need to make it easy on ops and users to comply18:33
ayoungmarekd, if not, we need to put it in bold and underline it18:33
stevemarwhy are we just bringing it up now?18:33
ayoungstevemar, we tried back then18:34
dstanekhenrynash: so are you wanting to encode names or force the name to be urlsafe?18:34
marekdayoung: that's my observation18:34
henrynashmarekd: it states that you can’t issue any tokens scoped by name to url-unsafe named projects/domains if you opt in18:34
ayoungbut I think we were thinking about it backwards...the realization was that it woudl be opt in, not that all current domains would work18:34
raildostevemar: he have discussed about it a lot of times here... and right now, we have a patch to handle with clash names,18:34
marekdhenrynash: maybe i missed it then.18:34
marekdthanks18:34
*** yamamoto has quit IRC18:34
henrynashdtsanek: we make them only use url-safe names18:34
*** mrmartin has quit IRC18:34
stevemarso the point of this is so i can specify a nested project?18:34
marekdhierarchy18:35
ayoungmarekd, I think we also need to make it explicit that domain nesting only works with url-safe names enabled18:35
marekdayoung: sure18:35
ayoungstevemar, a nested domain18:35
topolayoung +++18:35
henrynashstevemar: yes (or maybe even a nested domain, if we ever do that)18:35
samueldmqstevemar: because we hadn't thought about it ? maybe the same case as we hand't tought about the inherited assignments and hierarchical projects properly18:35
dstanekso basically something like: [a-zA-Z0-9\-_] and a few other chars?18:35
ayoungstevemar, it might be extensible to nesting projcts, too, but that is a longer reach18:35
samueldmqstevemar: maybe just a lack of eyes on that at the time :/18:35
ayoungdstanek, I think so18:35
ayoungwe can start cautious, and then open it up18:35
*** shashank_hegde has joined #openstack-meeting18:35
ayoungeasier than being to permissive, as we've found18:35
topolayoung +++18:36
dstanekiirc there are a lot of urlsafe chars18:36
stevemari'm just concerned about all these changes to our base API18:36
davechendstanek: ++18:36
dstanekayoung: totally agree18:36
ayoungstevemar, no API changes here by default18:36
henrynashdtsanek: yes, we exclude those specifed as reserved chars in the URL spec18:36
dstanekstevemar: are there api changes or just new constraints for the data?18:36
ayoungits opt in18:36
*** pots2 has joined #openstack-meeting18:36
topolhopefully just new constraints18:36
stevemarayoung: OK, not new API changes, but additional logic in the controller that handles those APIs18:37
henrynashstevemar: not with the spec, no18:37
ayoungsounds like we have a plan.  We can work the rest out in the review process. please prioritize.18:37
ayoungI'm going to ask for a spec review exception for this right now.18:37
*** ddieterly has quit IRC18:37
dstanekFYI rfc3986 says: unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"18:38
henrynashstevemar: if we chose to extent auth to accept a hierarchy name, then yes, but only in trh processing of teh name field18:38
ayoungI think we can parallelize the implementation with the spec, but don't want to rush it18:38
henrynashdstanek: yep18:38
raildodstanek: nice18:38
ayoungdstanek, I'm ok with starting with just those characters.18:38
*** sgundur has quit IRC18:38
shalehthat brings us back to '/' as a separator. Is that an issue with routes?18:38
stevemarshaleh: probably18:39
shaleh'.' is an allowed character so we cannot use that18:39
ayoungshaleh, yes, but we can make it work.18:39
dstanekwe could use ,18:39
topolayoung how?18:39
shalehdstanek: eeewww, visually hard to make out18:39
*** pots has quit IRC18:39
topolshaleh, I agree eeeww18:40
ayoungtopol, its python code.  Its only going to be one API.  I don't know *how* but I know we *can*18:40
dstanekshaleh: then ..,.?18:40
shaleh'|' is always popular18:40
ayoungbut we can make the mapper code deal with a/b/c/d18:40
dstanekshaleh: we'd have to encode that18:40
stevemardefer the conversation about the delimiter18:40
stevemarwe've got a full list18:40
shalehfair18:41
henrynashagain, let’s not debate the separator….we get to chose any url reserverd cahr18:41
* notmorgan votes ಠ_ಠ as the delimiter18:41
dstanekwe should debate this with the spec that proposes the delimiter!18:41
topolagreed18:41
notmorgan(that was commentary on the convo needs to move on btw)18:41
ayoungwhat do you guys mean delimeter?18:41
stevemar#topic filtering service providers with endpoint filter18:41
*** openstack changes topic to "filtering service providers with endpoint filter (Meeting topic: keystone)"18:41
ayoung(continue after meeting in #Keystone)18:41
bknudsonwe don't have nested domains really so no need for delimiter18:41
stevemarmarekd: ^18:41
stevemaris there something that needed to be hashed out here instead of the spec?18:42
notmorganbknudson: ++ no nested domains.18:42
marekdok18:42
stevemaris marekd online?18:42
henrynashbknudson: there are plentt of reasons to do this, ignoring the domain issue18:42
marekdi am18:42
marekdhttps://review.openstack.org/#/c/188534/8/specs/backlog/service-providers-filters.rst so for this spec18:42
stevemarmarekd: the podium is yours18:42
dstanekwith HMT don't we get nested domains?18:43
*** ihrachys has quit IRC18:43
marekdsome reviewers inclined endpoint filtering might be not "ready to use" as service_providers are not in the service catalog. Just wanted to hear your opinions - maybe we should just add another api and make it work as we would like to from the beginning?18:43
*** ihrachys has joined #openstack-meeting18:43
dstanekoh, wait no.. nm me18:44
stevemarhmm, they aren't in the service catalog are they18:44
marekdthey arent18:44
notmorgandidn't we add them to the top level?18:44
marekdnotmorgan: we did18:45
* notmorgan might be misremembering18:45
stevemarthey are in the token body, at the same level as the service catalog, i think18:45
shalehmarekd: I like the idea of a filter for them. I am just not sold that endpoint filtering is the way to go.18:45
marekdshaleh: cool, so this is the perfect timing for a discussion :)18:45
*** nadya_ has joined #openstack-meeting18:46
*** s3wong has quit IRC18:46
shalehmarekd: agreed :-)18:46
bknudsonunscoped tokens don't include the service providers?18:46
marekdi personally thin an admin should be able to tie a service provider with a project, domain (for domain scoped token) but also "all projects in a domain"18:46
dstanekseems like a new service provider filtering concept18:46
*** lkarm has quit IRC18:47
marekdbknudson: notremembering now, but today we simply fetch all service providers and return them in the token response.18:47
*** bnemec has joined #openstack-meeting18:47
marekdso this might also be athe case for unscoped token18:47
*** mtanino has quit IRC18:47
bknudsonso for unscoped tokens there's nothing to filter on.18:47
*** aimon has joined #openstack-meeting18:47
ayoungmarekd, only list SPs for Unscoped?18:47
bknudsonmaybe the projects that the user has roles on18:47
marekdayoung: you don't want to list all sps to everyone18:47
marekdyou don't want your pepsi clients expose that coke is your client too18:48
ayoungcorrect.  So unscoped seems like the wrong abstraction18:48
lbragstad++18:48
marekdyou dont want them think they may burst there...18:48
*** dmowrer has joined #openstack-meeting18:48
ayoungits public vs private Idps, just for K2K18:48
shalehayoung: ++18:48
stevemarayoung: seems like it18:48
*** jichen has joined #openstack-meeting18:48
marekdayoung: more or less....(less)18:48
ayoungso...they should be associated with proejcts18:49
marekdyes18:49
ayoungwhich is what endpoint filtering is doing18:49
marekdbut also domains and "all projects in a domain"18:49
ayoungso...lets expand that API to handle SPs seems like the most sane approach?18:49
shalehbut how are you associating a SP's endpoint with an IdP's project?18:49
bknudsondid endpoint filtering ever get expanded to domains?18:49
stevemarmarekd: i'm okay with abusing endpoint filtering for service providers18:49
*** bobh has joined #openstack-meeting18:49
ayounglets not expand anything to domains that we don't have to18:50
marekdstevemar: so extending it, right?18:50
stevemarmarekd: yeah18:50
bknudsonit might happen automatically when we change domains to projects18:50
marekdstevemar: cool18:50
*** ijw has quit IRC18:50
marekdah, pity samuel is not here18:50
lbragstad~ 10 minutes left18:50
stevemarmarekd: are the API changes and spec changes in the same patch?18:50
marekdstevemar: not yet18:50
stevemarthanks lbragstad18:50
*** pratikmallya has joined #openstack-meeting18:50
*** pratikmallya has quit IRC18:50
ayoungbknudson, ++18:51
marekdstevemar: i can add18:51
*** bobh has quit IRC18:51
marekdok, dont want to use more tim.e18:51
stevemarmarekd: start writing them out, i'd be curious to see what happens as you go18:51
marekdstevemar: OK18:51
*** pratikmallya has joined #openstack-meeting18:51
stevemari think we might be mis-remembering something18:51
stevemaranywho18:51
*** garyk has quit IRC18:51
marekdlike?18:51
stevemarmarekd: not sure!18:51
stevemar#topic Dropping python 2.6 support18:51
*** openstack changes topic to "Dropping python 2.6 support (Meeting topic: keystone)"18:51
stevemarbknudson18:51
dstanekmarekd: i'd love to see the documentation changes earlier than the code if possible...18:51
notmorganyes! drop it!18:52
bknudsonin case you missed the mailing list discussion18:52
notmorganmake it go away18:52
notmorgan>.>18:52
shalehdie die die py2618:52
bknudsoninfra stopped testing with py2618:52
stevemarthis seems like an easy one18:52
bknudsonand oslo libs already stopped advertising support for it18:52
*** apoorvad has joined #openstack-meeting18:52
bknudsonso there's some work to do in the repos to stop advertising support for 2.618:52
stevemar1) get rid of the job, 2) clean tox.ini 3) clean up any py26 specific code we have (we probably have a lot)18:52
bknudsonif anybody wants to sign up to do it ...18:52
ayoungDIE PYTHON2.6 DIE18:53
bknudsonotherwise I'll add it to my list18:53
davechenis there anything left in keystone?18:53
notmorganstevemar: open a tracking bug for cleanup of this stuff i think18:53
stevemarany takers? give bknudson a break to eat some turkey18:53
notmorganand then anyone can do it18:53
stevemarnotmorgan: that would be great18:53
dstanekbknudson: i'll do some18:53
lbragstadnotmorgan ++18:53
davecheniirc, py26 has been removed from dependency list.18:53
shalehbknudson: I can help out18:53
lbragstadi can give a hand too18:53
bretondavechen: nope, keystone is py26-free18:53
notmorganand it can just have bits done at a time. i'll open the bug shortly18:53
lbragstadnavid_ around?18:53
navid_yea18:53
bknudsonok, I'll assume people are going to work on it. Add me to the reviews18:53
lbragstadnavid_ would that be something you're interested in, too?18:54
stevemarjust remember to use Partial-Bug: blah18:54
dstanekbknudson: consider yourself added18:54
shalehstevemar: do we have a bug yet?18:54
stevemartjcocozz might be interested too :P18:54
stevemarshaleh: not yet, notmorgan is opening one as we speak... err type18:54
navid_@lbragtad: sure, we can discuss afterwards18:54
bknudsonthere's plenty of examples in oslo repos18:54
stevemarnext!18:54
stevemar#topic Reno for other repos18:54
*** openstack changes topic to "Reno for other repos (Meeting topic: keystone)"18:54
stevemari don't want this18:54
stevemarthis is overkill for libraries18:55
stevemaris oslo doing this? dhellmann dims_ ?18:55
*** jprovazn has joined #openstack-meeting18:55
bknudsonyes, oslo is doing this as far as I know18:55
stevemarughhhhhhh18:55
*** dmowrer has quit IRC18:55
dims_stevemar : we were talking about it. haven't decided yet18:55
stevemarbut i dont wannnaaaaa18:55
ayoungIf you kill a man in Reno, they don't send yo to Folsom St. Penn...yougo to jail in Nevada18:55
bknudsone.g., https://review.openstack.org/#/c/249329/18:55
*** ihrachys has quit IRC18:55
notmorganstevemar: https://bugs.launchpad.net/keystone/+bug/151944918:55
openstackLaunchpad bug 1519449 in OpenStack Identity (keystone) "Remove Python 2.6 Support" [Low,In progress] - Assigned to Keystone Drivers (keystone-drivers)18:56
lbragstadstevemar we only want to use reno for keystone server?18:56
bknudsonoh, the discussion is ongoing18:56
dims_bknudson : see the -W18:56
dims_y18:56
*** dmowrer has joined #openstack-meeting18:56
stevemarthanks notmorgan18:56
ayounglink to "why reno?" please.18:56
*** sacharya has joined #openstack-meeting18:56
stevemarbknudson: let's wait and see what comes out from the oslo discussion18:56
stevemari'd really prefer to not have to do reno for libraries18:56
notmorganlbragstad: reno doesn't make sense (i think) for the libs.18:56
bknudsonreno is to generate release notes, so that users will know what changed18:56
*** xek_ has quit IRC18:57
stevemarbut we'll go with the flow18:57
bknudsone.g., what new features have been added18:57
topolso um who was pushing reno?18:57
stevemartopol: release mgnt ream18:57
*** ihrachys has joined #openstack-meeting18:57
stevemarteam*18:57
dstaneknotmorgan: use that bug for all of the libs?18:57
dims_topol : release team is trying to evaluate18:57
notmorgandstanek: yeah will add the libs now18:57
stevemartopol: it's great for the server stuff, instead of a wiki18:57
*** achanda has joined #openstack-meeting18:57
topolanyone else actually really using it18:57
*** banix has quit IRC18:57
stevemartopol: it just started18:57
dstaneknotmorgan: cool. thx18:58
dims_topol Nova has18:58
stevemartopol: we get pretty release notes like: http://docs.openstack.org/releasenotes/keystone/unreleased.html18:58
stevemarbknudson:  we can chat about libraries in -keystone18:58
*** pots has joined #openstack-meeting18:58
stevemarbknudson: sorry we didn't get to that last topic18:58
bknudsonok, we'll see where the rest of openstack goes18:58
ayoungplease lock the python-keystoneclient repo, but leave it a round since old versions of the code will point to it18:58
notmorgandstanek: did I miss any?18:58
ayoungsame with SAML18:58
ayoungdon;t delete the repos.18:59
stevemarayoung: we won't, they'll go in the attic18:59
notmorgandstanek: ok added pycadf too18:59
ayoungso long as the links still work, I'm OK18:59
dstaneknotmorgan: do pycadf, ks-auth policy have 2.6?18:59
ayoungwith it18:59
stevemarayoung: links may not work...18:59
davechenstevemar: the release note is a little confusion, you put a bug link there but say it's a feature.18:59
stevemardavechen: new options are available19:00
*** adduarte has joined #openstack-meeting19:00
davechenand properly, we will has lot of features in the releasenote after the end of the cyle.19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Nov 24 19:00:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-11-24-17.59.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-11-24-17.59.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-11-24-17.59.log.html19:00
fungiinfra team, assemble!19:00
*** AJaeger has joined #openstack-meeting19:00
*** shaleh has left #openstack-meeting19:00
*** pradk has quit IRC19:00
*** garyk has joined #openstack-meeting19:00
AJaeger\o/19:00
crinkleo/19:00
* mordred self-assembles19:00
*** dmowrer has quit IRC19:00
clarkbhello19:00
*** dmowrer_ has joined #openstack-meeting19:00
*** dmowrer_ has quit IRC19:00
*** roxanaghe_ has quit IRC19:00
* fungi suspects mordred is a replicator19:00
*** pots2 has quit IRC19:00
* mordred assembles self?19:00
stevemarhi infra!19:00
stevemarkeystone team, disassemble!19:00
*** dmowrer has joined #openstack-meeting19:00
notmorganstevemar: minions!19:01
jeblairo/19:01
* mordred assemblet sich?19:01
fungi#startmeeting infra19:01
openstackMeeting started Tue Nov 24 19:01:05 2015 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
zaroo/19:01
openstackThe meeting name has been set to 'infra'19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
SotKo/19:01
*** breton has left #openstack-meeting19:01
fungi#info Many thanks to pleia2 for chairing last week!19:01
fungi#topic Announcements19:01
* mordred mach sich doch gern19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** yolanda has joined #openstack-meeting19:01
mordreds/mach/macht/19:01
fungi#info The gerrit 2.11 upgrade scheduled for last Wednesday (November 18) was indefinitely postponed pending completion of a thorough rollback plan and one pending OpenID redirect URL fix.19:01
*** wuhg has quit IRC19:01
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/079769.html19:01
yolandao/19:01
fungi#link https://review.openstack.org/24559819:01
*** samleon has quit IRC19:01
*** lhcheng_ has left #openstack-meeting19:01
fungi#link https://code.google.com/p/gerrit/issues/detail?id=336519:01
*** vahidh has joined #openstack-meeting19:01
ianwo/19:01
jeblairoh good, someone told fungi we didn't upgrade :)19:02
fungiany other announcements before i move on to other topics?19:02
*** pradk has joined #openstack-meeting19:02
mordredjeblair: wait, we didn't?19:02
*** pradk has quit IRC19:02
jesusauruso/19:02
mordredfungi: ansible 2.0 is in rc1 now19:02
jeblairmordred: (new gerrit looks _a lot_ like the old gerrit)19:02
fungimordred: neat--what are the implications for us?19:02
mordredfungi: so, it's a thing to keep our eyes on, as I believe our servers will upgrade when it releases19:02
pleia2o/19:02
mordredfungi: it SHOULD have zero effect19:02
mordredfungi: I've poked at our playbooks and everything _should_ be solid19:03
*** hemna has joined #openstack-meeting19:03
fungiso implication is something other than massively broken, we hope19:03
mordredbut still - just keep eyes out19:03
mordredyah19:03
mordredthey've done a good job with it19:03
*** tellesnobrega is now known as tellesnobrega_af19:03
*** fitoduarte has quit IRC19:03
notmorganyay ansible 2.0 being good!19:03
clarkbI had a tes tchange in d-g to make sure d-g won't break either19:03
*** kozhukalov_ has joined #openstack-meeting19:03
fungi#info Be on the lookout for ansible 2.0 release in case we see any automation fallout resulting.19:03
fungi#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
fungi#link http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-11-17-19.00.html19:04
fungithere were none, all executed successfully!19:04
fungi#topic Specs approval19:04
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:04
fungiphschwartz has a spec to extend openstackci, but i've taken its proposal off the current agenda since it seems to still have some unaddressed comments19:04
fungi#link https://review.openstack.org/23981019:04
*** banix has joined #openstack-meeting19:04
fungiadd it back to the agenda when it's ready for council voting again'19:04
phschwartzfungi: correct, I am addressing the last comments currently19:04
*** pratikmallya has quit IRC19:05
fungithanks for bearing with us!19:05
fungi#topic Priority Efforts: Gerrit 2.11 Upgrade19:05
*** openstack changes topic to "Priority Efforts: Gerrit 2.11 Upgrade (Meeting topic: infra)"19:05
*** pratikmallya has joined #openstack-meeting19:05
funginow is the time on sprockets when we dance...19:05
fungizaro: mordred: any status on fixing the rollback plan, and guesses at a timeline for a fix/workaround to the openid url bug?19:05
* mordred has not touched it - zaro - any luck in getting a happy reproduction of the rollback with changes past the data overlap?19:06
asselino/19:06
anteayazaro has a test instance up that I am playing with19:06
zaroyeah, i got a working post rollback site.19:06
anteayaI have no conclusions as of yet, just getting oriented19:06
zaroanteaya is testing it now19:06
mordredcool!19:06
anteayaanyone else want to help test?19:07
zarothe only issue is in regards to sortkey getting removed in 2.919:07
clarkbzaro: thats an issue with the rollback?19:07
fungisounds like we probably want to put off discussions of a rescheduled window until these last known details are ironed out19:07
anteaya#link explaination of sortkey getting removed in this patch https://review.openstack.org/#/c/245598/19:07
zaroI think that's just used to put changes in some order from a query.19:07
zaroclarkb: yes19:07
zaroI'm not sure what we want to do there.19:08
fungisame change i linked in the announcements, fwiw19:08
anteayasorry19:08
zarothere are probably a few things we can do to fix it19:08
zaroor make it work19:08
clarkbzaro: _david_'s suggestion seems like the most correct?19:09
jeblairclarkb: ++19:09
clarkbbasically make sort keys for any new changes19:09
zaroyes, i believe so19:09
*** xek_ has joined #openstack-meeting19:09
*** ddieterly has joined #openstack-meeting19:09
zarowhat i did was just put a duplicate key in the table and reindex worked.19:09
*** unicell has joined #openstack-meeting19:09
cody-somerville\o19:10
*** kevinbenton has joined #openstack-meeting19:10
jeblairhttps://gerrit.googlesource.com/gerrit/+/e800b1e0f3452e5be1537a67f1fa3e44a58c6dda/gerrit-server/src/main/java/com/google/gerrit/server/ChangeUtil.java#18119:10
jeblairoh that looks like we could probably even make a quick python script to do it?19:10
mordredoh19:10
jeblairmaybe even a sql query?19:10
mordredI could do that in sql19:10
mordredyea19:10
mordredin the downgrade script19:10
mordredit's just a simple data manipulation19:11
fungiyep, my only objection was to the suggestion that we could consider not writing it until we discover we need to use it19:11
zarocool!19:11
jeblairmordred: sql++19:11
mordred"The encoding uses minutes since Wed Oct 1 00:00:00 2008 UTC."19:11
mordredWHAT????19:11
mordredcome on guys19:11
clarkbmordred: yay19:11
fungiit's the "new epoch!"19:11
jheskethMorning19:11
* mordred cries19:11
*** ihrachys has quit IRC19:11
jesusaurusepoch 2.0?19:11
jeblairi measure time from when sortkey was removed19:11
* jhesketh joins a little late19:11
fungialso known as "gerrit crazypants time"19:11
anteayahey jhesketh19:11
clarkbfungi: Gerrit Standard Time19:12
*** ihrachys has joined #openstack-meeting19:12
zaromordred: would you like to come up with something? then i can test it?19:13
*** zehicle has joined #openstack-meeting19:13
*** zehicle has quit IRC19:13
*** zehicle has joined #openstack-meeting19:14
mordredzaro: yes. I will writ eyou some lovely sql19:14
*** zehicle has quit IRC19:14
zarolovely then..19:14
*** zehicle has joined #openstack-meeting19:14
fungiokay, so it _sounds_ like we'll probably have that sorted and retested by next week's meeting19:15
*** zehicle has quit IRC19:15
zaroregarding the other issue.. gerrit url redirect19:15
fungithe openid redirect issue was also brought up as an upgrade blocker though, roght?19:15
fungiyeah that19:15
clarkbI am not sure it has to be a blocker but it is quite annoying19:15
*** zehicle has joined #openstack-meeting19:15
clarkbI am happy with revert of change that breaks it until upstream figures it out19:15
*** zehicle has quit IRC19:15
krotschecko/19:15
Clinto/19:15
anteayaI also can live with revert of change that breaks it19:16
*** zehicle has joined #openstack-meeting19:16
zarothe info is up on the bug #link https://code.google.com/p/gerrit/issues/detail?id=336519:16
*** zehicle has quit IRC19:16
fungi(also #link'd in the announcements part of the meeting, for reference_19:16
*** zehicle has joined #openstack-meeting19:16
zaromy lack of knowledge regarding apache rewrite config is shining thru here.19:16
*** zehicle has quit IRC19:16
zaroi'm hoping hugo either reverts or finds some sort of fix in the current code.19:17
*** neelashah1 has joined #openstack-meeting19:17
*** zehicle has joined #openstack-meeting19:17
*** lkarm has joined #openstack-meeting19:17
*** zehicle has quit IRC19:17
zaroi'm we are open to changing our apache config, that might be an option as well.19:17
zaro*i'm/we19:17
fungiso as a way forward, we would backport a revert of that change and build our custom war with the revert in place if it ends up being the only blocker and we can't fix it in apache?19:17
*** zehicle has joined #openstack-meeting19:18
clarkbwe are open to changing our config but not at the expense of those features19:18
*** mtanino has joined #openstack-meeting19:18
*** zehicle has quit IRC19:18
clarkbI have attempted to fix in apache19:18
anteaya+1 what fungi said19:18
fungias have i19:18
*** zehicle has joined #openstack-meeting19:18
zarocan we change our config while keeping the rewrite rules?19:18
clarkbthe trouble there appears to be that http://foo.openstack.org// is treated as foo.openstack.org/ in many situations19:18
*** zehicle has quit IRC19:18
fungii hacked on possible workarounds for a while back when we first encountered it last may19:19
clarkbzaro: that is what we have tried and nothing works and I think its due to ^19:19
*** neelashah has quit IRC19:19
*** zehicle has joined #openstack-meeting19:19
clarkbI turned on rewrite debug logging and it wasn't 100% clear but it seemed like we weren't matching // because raisins19:19
*** zehicle has quit IRC19:19
clarkband its possibly my apache regex foo was just bad19:19
*** zehicle has joined #openstack-meeting19:20
fungiso i guess due diligence should include testing review-dev with a custom-built 2.11.x war with that commit reverted just to make sure it's not hiding other problems19:20
*** sgundur has joined #openstack-meeting19:20
*** zehicle has quit IRC19:20
anteayamakes sense19:20
zarois there a way to use both 'ProxyPass / http://127.0.0.1:8081/ nocanon' with our current rewrite rules?19:20
*** neelashah has joined #openstack-meeting19:20
zarofungi: ++19:20
anteayazaro: happy to keep testing things you serve up19:20
*** zehicle has joined #openstack-meeting19:20
clarkbzaro: no19:20
notmorganclarkb: if you need any help with apache regex i'm happy to take a gander - but i trust your regex foo.19:20
*** zehicle has quit IRC19:20
*** achanda has quit IRC19:21
clarkbthe ProxyPass rule is going to proxy everything19:21
*** zehicle has joined #openstack-meeting19:21
*** neelashah1 has quit IRC19:21
*** zehicle has quit IRC19:21
zarook. i'll install a revert of that change 57800  on review-dev.o.o for testing.19:21
funginotmorgan: i think it's more dealing with apache's selective application of regular expressions19:21
*** zehicle has joined #openstack-meeting19:21
anteayazaro: thanks19:21
*** adduarte has quit IRC19:22
*** zehicle has quit IRC19:22
notmorganfungi: ++19:22
*** zehicle has joined #openstack-meeting19:22
fungii was also getting tripped up on the stacking order of rewrites and proxying in apache when i was trying to work around that19:22
notmorganfungi: probably, but if i can help, lmk - happy to dust off my apache skills if it will mkae a difference :)19:22
*** zehicle has quit IRC19:22
* notmorgan used to do tons of rewrite/proxy/etc stuff for webhosting.19:23
*** penick has joined #openstack-meeting19:23
*** zehicle has joined #openstack-meeting19:23
funginotmorgan: i believe we have an easy reproducer if you get bored and want to stand up a vm to play around with19:23
*** liusheng has quit IRC19:23
*** zehicle has quit IRC19:23
notmorganfungi: cool will ping you post meeting / zaro and look into it19:23
*** liusheng has joined #openstack-meeting19:23
notmorgan:)19:23
zaroreverted 57800 is now on review-dev.o.o19:23
fungi(same goes for anyone who wants to take a crack at leveraging their apache-fu)19:23
fungithanks zaro!19:23
*** zehicle has joined #openstack-meeting19:23
*** zehicle has quit IRC19:24
zarodimtruck: has graciously volunteer to help repro it.19:24
dimtruck+119:24
*** mbound_ has joined #openstack-meeting19:24
anteayadimtruck: thank you19:24
*** zehicle has joined #openstack-meeting19:24
fungiokay, so we're agreed we'll defer scheduling of the 2.11 upgrade until at least next tuesday's meeting?19:24
anteayaagreed19:24
zarosure19:24
fungirather, REscheduling19:24
*** zehicle has quit IRC19:24
*** zehicle has joined #openstack-meeting19:25
*** achanda has joined #openstack-meeting19:25
fungi#agreed Rescheduling of the Gerrit 2.11 upgrade is deferred to the next meeting while final details are worked out and suggested fixes tested.19:25
*** zehicle has quit IRC19:25
fungianything else on this topic (almost typed tapioca) before we move on?19:26
*** zehicle has joined #openstack-meeting19:26
anteayaha ha ha19:26
*** zehicle has quit IRC19:26
zaroredirect on review-dev.o.o seems to work great for me now.19:26
*** zehicle has joined #openstack-meeting19:26
fungigreat news19:26
fungiokay, next topic!19:26
fungi#topic Priority Efforts: maniphest migration19:26
*** openstack changes topic to "Priority Efforts: maniphest migration (Meeting topic: infra)"19:27
*** zehicle has quit IRC19:27
fungiruagair has a comment in the agenda about maniphest early adopters which i didn't spot discussed in last week's log--any details on who and why?19:27
fungithis is more for my edification/education19:27
* anteaya has no details on who and why19:27
yolandai got a beta access for maniphest19:27
fungiif he's not around and nobody knows i won't waste meeting time on it19:27
yolandaand GheRivero as well, to work on infra cloud19:27
yolandamay be that?19:27
fungihe says "There are a number of users already using Manifest in anger, as guinea pigs."19:27
jeblairoh19:28
yolandamaybe?19:28
fungii take that to mean as (semi?)production location for tracking bugs in their projects19:28
jeblairi wish we'd talked about that before doing it?19:28
fungisame19:28
*** pots has quit IRC19:28
yolandai just created a project, and Ghe poked a bit, but nothing on production at the moment19:28
yolandatopic was raised last week on meeting19:28
anteayaI don't think anything was discussed about anyone using it though19:29
fungiokay, i'll try to sync up with him when he's awake and get some details on what that comment means19:29
clarkbI'm still just trying to get working mod auth openid with apache19:29
yolandai would not say we use on production, but got access to poke a bit19:29
*** zehicle has joined #openstack-meeting19:29
*** ajayaa has quit IRC19:29
jeblairyolanda: that's fine19:29
*** zehicle has quit IRC19:29
fungithat would make perfect sense, of course. i'm hopefully just misinterpreting the agenda comment there19:29
jeblairi just don't think any project should start using it for real until we think it's ready for that19:29
yolandayes, he even may not be talking of us19:30
*** aranjan has quit IRC19:30
fungi#agreed Maniphest test deployment is for testing the feasibility of Maniphest, not for production use.19:30
*** aspiers_ has quit IRC19:30
*** hashar has joined #openstack-meeting19:30
mordredyolanda: is the openid thing there and working?19:31
yolandamordred,not, just a user/pass19:31
mordredkk19:31
*** ijw has joined #openstack-meeting19:31
*** IlyaG has joined #openstack-meeting19:31
fungi#topic Enable Tempest for Magnum (dimtruck)19:31
*** openstack changes topic to "Enable Tempest for Magnum (dimtruck) (Meeting topic: infra)"19:31
fungi#link https://review.openstack.org/24812319:31
dimtruckwoo hoo!  yes please :) yolanda already +2'ed ... this is needed to add tempest to magnum19:32
fungidimtruck: can you explain what's unusual about this change?19:32
*** rebase_ has quit IRC19:32
dimtrucknothing unusual.  Just wanted to get it in front of cores :)19:32
*** zehicle has joined #openstack-meeting19:32
fungimostly just trying to figure out why it's a meeting topic19:32
*** banix has quit IRC19:32
jeblairdimtruck: this was not the way to do that19:32
*** zehicle has quit IRC19:32
dimtruckoh, sorry about that19:32
anteayadimtruck: yeah, adding it to the meeting topic isn't a good choice19:32
hasharo/19:32
dimtruckthat was one of the suggestions proposed to me.  won't do it again.19:32
*** zehicle has joined #openstack-meeting19:33
anteayadimtruck: can you also give that feedback to whoever proposed it to you19:33
dimtrucki will.19:33
anteayaand thanks19:33
*** zehicle has quit IRC19:33
fungiyep, i thought maybe there was something happening with that change we needed to discuss as a group, but i didn't check it at all before starting the meeting. sorry about that!19:33
fungi#topic Translations check website (pleia2)19:33
*** openstack changes topic to "Translations check website (pleia2) (Meeting topic: infra)"19:33
pleia2hi there19:33
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-November/003465.html19:33
pleia2so Daisy sent an email to the list ^^19:33
*** zehicle has joined #openstack-meeting19:33
*** ijw_ has joined #openstack-meeting19:33
*** ihrachys has quit IRC19:33
*** ijw has quit IRC19:33
pleia2I replied, but I'd really like to see others chime in to help make it possible for Daisy to get this to the finish line19:34
*** zehicle has quit IRC19:34
*** brucet has joined #openstack-meeting19:34
*** brucet has quit IRC19:34
pleia2if there's anything I missed, references that may be helpful, etc19:34
*** zehicle has joined #openstack-meeting19:34
*** zehicle has quit IRC19:34
pleia2I also wanted to mention that we never decided upon a URL for accessing this service, and none is defined in the spec, so it would be great to get some ideas19:34
*** mrmartin has joined #openstack-meeting19:35
*** zehicle has joined #openstack-meeting19:35
anteayapleia2: what do you think is appropriate?19:35
pleia2#link http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_check_site.html19:35
*** henrynash has quit IRC19:35
*** zehicle has quit IRC19:35
clarkbi18n-devstack.openstack.org ?19:35
*** zehicle has joined #openstack-meeting19:35
pleia2daisy suggested translation-test.openstack.org19:35
anteayapleia2: what do you like?19:36
pleia2but i18n-devstack.openstack.org or translation-devstack.o.o works too19:36
*** zehicle has quit IRC19:36
anteayawhy devstack in the url?19:36
*** zehicle has joined #openstack-meeting19:36
fungiyeah, i'd prefer not to bikeshed too much. but i'm also not keen on embedding the names of tools in domain names (in case we change the tools we use to provide them later). that said, we're pretty inconsistent between naming servers after the services they provide and naming them for the software they run19:36
*** navid_ has quit IRC19:36
*** zehicle has quit IRC19:36
*** zehicle has joined #openstack-meeting19:37
clarkbit seems very specific to the tool hence my suggestion19:37
clarkbwhereas translation-test could be anything19:37
*** zehicle has quit IRC19:37
* pleia2 nods19:37
clarkbbut I don't care strongly enogh to want one over the other that strongly19:37
clarkbeither will work19:37
*** zehicle has joined #openstack-meeting19:37
clarkbso daisy's suggestion works for me19:37
* fungi wonders if it's there to test anything besides horizon... do we have translated api responses for example?19:37
*** zehicle has quit IRC19:38
AJaegerfungi, no we don't have.19:38
AJaegerglance is currently working on something in this area.19:38
*** zehicle has joined #openstack-meeting19:38
pleia2and their focus for this has been horizon19:38
*** zehicle has quit IRC19:38
AJaegerfungi, https://review.openstack.org/232304 is related to the glance work19:39
fungianyway, at the end of the day, i don't care to much what we call it. pick something that seems appropriate19:39
*** zehicle has joined #openstack-meeting19:39
fungier, too much19:39
AJaegerpleia2: throw a dice ;)19:39
pleia2ok, I'll propose a change to the spec once I decide on one19:39
*** zehicle has quit IRC19:39
fungiuse the turbo-hipster model of naming things ;)19:39
*** zehicle has joined #openstack-meeting19:39
fungithanks pleia2!19:39
pleia2that's all19:40
*** zehicle has quit IRC19:40
fungi#topic Open discussion19:40
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:40
*** zehicle has joined #openstack-meeting19:40
fungilooks like we blew through this week's agenda with 20 minutes to spare19:40
yolandaok, infra-cloud19:40
*** zehicle has quit IRC19:40
yolandawe got nearly the 100 nodes up on east19:40
*** xek_ has quit IRC19:40
funginice!19:40
yolandawanted to check with greghaynes, crinkle, about status of west19:40
clarkbdo they cloud?19:40
*** dmowrer_ has joined #openstack-meeting19:40
*** dmowrer has quit IRC19:40
mordredwoot!19:40
*** zehicle has joined #openstack-meeting19:41
crinklehiya19:41
yolandaclarkb, mordred, we are pending on a glean fix19:41
*** zehicle has quit IRC19:41
mordredoh - which one/19:41
rcarrillocruzyeah19:41
mordred?19:41
crinklei'm still working out some issues automating the baremetal deployment in west19:41
rcarrillocruzhttps://review.openstack.org/#/c/244625/319:41
*** salv-orlando has quit IRC19:41
clarkbyolanda: rcarrillocruz so what does up mean?19:41
*** zehicle has joined #openstack-meeting19:41
yolandaclarkb, they are correctly deployed with bifrost19:41
*** zehicle has quit IRC19:41
anteayayolanda crinkle is the hardware entirely different on east and west is that why you are working in two groups?19:41
yolandawe had some blockers with ilos, disk problems, network19:42
crinkleanteaya: there are different network setups19:42
anteayacrinkle: ah thanks19:42
yolandaanteaya , Ricky and myself joined recently, so we got agreement to work on Easts19:42
*** zehicle has joined #openstack-meeting19:42
mordredI'm going to approve that change unless someone else wants to scream19:42
*** zehicle has quit IRC19:42
anteayayolanda: right but yeah if different networks you would have different issues19:42
rcarrillocruzit's the vlan interfaces bug for debian in glean we discussed last week19:42
fungimordred: what change?19:42
clarkbmordred: no that appears to be what we agreed on after the discussion19:42
yolandaanteaya, that's right. networking is different, as well as hardware19:43
clarkbmordred: interface.vlan19:43
rcarrillocruzcrinkle: anything we can assist on? we have some playbooks on ansible we've been using ad-hoc in east19:43
*** zehicle has joined #openstack-meeting19:43
rcarrillocruznot sure what you're at19:43
anteayayolanda: okay thanks19:43
clarkboh wait19:43
clarkbmordred: hold on19:43
*** zehicle has quit IRC19:43
mordredclarkb: kk19:43
clarkbthe tests are still broken19:43
yolandaso yes, crinkle, we can help on network, hard problems... we had to open a few tickets19:43
clarkbrcarrillocruz: ^ I pointed that out to somewhere I thought19:43
clarkbrcarrillocruz: there is no eth419:43
*** zehicle has joined #openstack-meeting19:43
crinklercarrillocruz: i've been working from the patches in gerrit, if you have ad hoc playbooks that aren't pushed up that's not really good19:43
clarkbright?19:43
*** zehicle has quit IRC19:44
mordredfungi: https://review.openstack.org/#/c/24462519:44
fungithanks!19:44
fungimordred: also, mind if i de-op you in here?19:44
mordredfungi: sure thing19:44
yolandacrinkle, we consume same playbooks19:44
rcarrillocruzcrinkle: pending push, yep19:44
yolandabut we have additional tools19:44
*** zehicle has joined #openstack-meeting19:44
rcarrillocruzi wonder what automation issues are those19:44
crinklefungi: i'm wondering if there are plans for an infra midcycle?19:44
clarkbrcarrillocruz: or did we end up deciding if that was correct?19:44
*** ChanServ sets mode: -o mordred19:44
clarkbI need to find the input to the tests to figure out if outputs look good19:45
*** zehicle has quit IRC19:45
rcarrillocruzclarkb: not sure19:45
fungicrinkle: i need to circle back around with pleia2, she was looking into logistics for one good option19:45
*** zehicle has joined #openstack-meeting19:45
pleia2yeah, vmbrasseur just followed up again internally for me19:45
*** zehicle has quit IRC19:45
pleia2so hopefully we'll know something soon19:45
*** claudiub has joined #openstack-meeting19:45
fungithe short answer is that we're hoping to do something in mid february and focus on driving whatever's left to knock out for infra-cloud19:45
crinklecool, i think some puppet-apply things could get knocked out too19:46
*** zehicle has joined #openstack-meeting19:46
fungior turn it into a get-to-know-you session for infra-cloud perhaps, if there's nothing left to knock out ;)19:46
*** zehicle has quit IRC19:46
*** zehicle has joined #openstack-meeting19:46
rcarrillocruzcrinkle: what we have pending push is some helper scripts to wipe servers on ironic and doing rebuilds19:46
rcarrillocruzthat help us re-test deployments19:46
rcarrillocruzi'll push up tomorrow19:46
*** zehicle has quit IRC19:47
yolandafungi, ++ on mid cycle for that19:47
mordredcrinkle: I'm _hoping_ to finish puppet-apply  this week :)19:47
crinklemordred: oooh19:47
*** zehicle has joined #openstack-meeting19:47
yolandacrinkle, so you got an operational cloud in west right?19:47
crinkleyolanda: not currently19:47
*** zehicle has quit IRC19:47
fungicrinkle: yep, it's risky coming up with an agenda this far in advance since we don't know what we'll have finished when, but that seemed like a good time and when the other infra core reviewers/root admins where discussing in tokyo we concluded we'll probably have something worthy of an in-person sprint19:47
*** mrmartin has quit IRC19:47
mordred++19:47
rcarrillocruzclarkb: it was not clear to me why having 5 interfaces on the config drive fixture glean doesn't produce eth4 no19:48
rcarrillocruz:/19:48
yolandacrinkle, i connected to controller node last week and saw some services up, what's missing?19:48
*** zehicle has joined #openstack-meeting19:48
clarkbrcarrillocruz: it is making an eth419:48
rcarrillocruzcrinkle: yeah, we can assist19:48
clarkbrcarrillocruz: but the old change wasn't iirc19:48
*** zehicle has quit IRC19:48
*** xingchao has joined #openstack-meeting19:48
* mordred wants to point out that LCA is late this year, so mid-feb is potentially weird timing-wise19:48
crinkleyolanda: there weren't static ips assigned at the time, and now i've restarted dnsmasq enough that the ips they had are lost19:48
*** kebray has quit IRC19:48
clarkbrcarrillocruz: so I am just trying to reconcile the two in my head and ifgure out if the current make an eth4 is correct19:48
*** zehicle has joined #openstack-meeting19:48
crinkleyolanda: rcarrillocruz are you using static dhcp ip assignments in east?19:49
rcarrillocruzclarkb: k, looking forward for your input in the change19:49
mordredalso, AnsibleFest London is Feb 18 and they're talking about having a one-day contributors summit the day before which Shrews and I probably want to be in19:49
*** zehicle has quit IRC19:49
*** fzdarsky has quit IRC19:49
rcarrillocruzcrinkle: no, to speed up testing we are using dynamic dhcp19:49
yolandacrinkle, no19:49
crinkleah that's what i'm working on19:49
rcarrillocruzcos we really needed to know what's broken and what not from HW perspective19:49
*** mbound_ has quit IRC19:49
anteayamordred: feb 1-5: http://lcabythebay.org.au/19:49
*** zehicle has joined #openstack-meeting19:49
*** sdake has joined #openstack-meeting19:49
fungiyep, we can try to work the date so it's at least not overlapping or hopefully too back-to-back with lca19:49
rcarrillocruzand concurrently i've pushed that glean fix i mentioned earlier, cos vlan in glean is broken19:49
anteayamordred: so if mid-feb = week of feb 15th we sould be okay19:49
*** zehicle has quit IRC19:49
anteayamordred: depending on how much time after lca you want to be in geelong19:50
clarkbrcarrillocruz: looks lik there are 5 mac addrs so should be 5 interfaces. eth0-eth419:50
clarkbrcarrillocruz: I think its correct19:50
clarkbmordred: ^ if you want to approve19:50
*** zehicle has joined #openstack-meeting19:50
rcarrillocruz\o/19:50
*** zehicle has quit IRC19:50
yolandawoot!19:50
rcarrillocruzcrinkle: if you need help or split the work on testing the HW, let us know19:50
mordreddone19:50
*** zehicle has joined #openstack-meeting19:50
jesusaurusi've split the log_processor python scripts out of the puppet module and into the new project openstack-infra/log_processor, interested persons should add it to their watched projects list19:50
rcarrillocruzhappy to help19:51
*** Sukhdev has joined #openstack-meeting19:51
*** zehicle has quit IRC19:51
crinkleyolanda: rcarrillocruz do y'all sometimes have problems with glean not writing out /etc/network/interfaces or /etc/network/interfaces.d/<iface>.cfg on boot?19:51
rcarrillocruzheh19:51
rcarrillocruzhmm, yeah19:51
*** zehicle has joined #openstack-meeting19:51
rcarrillocruzBUT19:51
*** zehicle has quit IRC19:51
rcarrillocruzi need to see if that happens on our vlans when the fix merges19:51
rcarrillocruznot sure what's that coming from, if legit or not19:51
*** sdake_ has joined #openstack-meeting19:52
rcarrillocruzmaybe a race19:52
anteayaif we did feb 10-12 wed-fri that should fit in between lca and ansiblefest19:52
crinklei think it's unrelated to the vlan change, i think it's an issue with the upstart script19:52
*** zehicle has joined #openstack-meeting19:52
rcarrillocruzyeah, unrelated19:52
*** zehicle has quit IRC19:52
rcarrillocruzi mean i didn't want to go that rabbit hole before fixing the vlan thing19:52
rcarrillocruzand see if we hit that on the vlan interfaces, since it's the one we will care about19:52
yolandain these weeks we've been mostly focused on hardware problems19:52
rcarrillocruzi also think it's about upstart19:52
*** zehicle has joined #openstack-meeting19:52
rcarrillocruzi hit similar races in the past in gozer19:53
*** zehicle has quit IRC19:53
rcarrillocruzwhere glean would run before network interfaces would come up, but iirc clarkb fixed that19:53
rcarrillocruzso not sure, anyway, we'll let you know what we get19:53
*** dims has joined #openstack-meeting19:53
rcarrillocruzi think we really should stress test the deployments19:53
*** zehicle has joined #openstack-meeting19:53
mordredfungi, clarkb, jhesketh, yolanda, pleia2: whie we're here and talking - could I get a +A on https://review.openstack.org/#/c/241495/ so that I can move forward with puppet apply?19:53
rcarrillocruzand document failures19:53
*** xingchao has quit IRC19:53
*** zehicle has quit IRC19:53
*** pots has joined #openstack-meeting19:53
yolandarcarrillocruz, i agree. We've been bringing up machines slowly, but we need to be sure that it's repeatable19:54
*** zehicle has joined #openstack-meeting19:54
*** zehicle has quit IRC19:54
clarkbrcarrillocruz: the only problem is if you do that too much you end up having no nodes left19:54
*** sdake has quit IRC19:54
clarkbbecause ILO bugs and motherboards die19:54
*** achanda has quit IRC19:54
*** zehicle has joined #openstack-meeting19:54
rcarrillocruzreally? you are scaring me... :-)19:55
*** mrmartin has joined #openstack-meeting19:55
*** zehicle has quit IRC19:55
*** rockyg has joined #openstack-meeting19:55
*** zehicle has joined #openstack-meeting19:55
jeblairwe're still on the short-term hardware, right?19:55
*** zehicle has quit IRC19:55
yolandaclarkb, we had several ilo problems, but were fixed resetting ilos at the moment19:56
rcarrillocruzjeblair: yeah, thing is we have to make a 'inventory' of what's working , what not19:56
clarkbrcarrillocruz: aiui that was part of the problems in west19:56
*** dims_ has quit IRC19:56
yolandajeblair, yes19:56
*** zehicle has joined #openstack-meeting19:56
rcarrillocruzthen come up to purp with that info19:56
jeblairwhere the plan is "continue working on this to get the framework in place and identify potential problems, but don't spend too much time worrying about this particular hardware"19:56
crinklejeblair: we won't see additional hardware until at least january19:56
krotscheckWhat's the status on the wheel mirror patches? I've got a patch chain that's waiting on it.19:56
*** zehicle has quit IRC19:56
crinklekrotscheck: greghaynes is awaiting reviews on it19:56
clarkbkrotscheck: they are up and in review with passing CI results now I think19:56
*** dcaro has joined #openstack-meeting19:56
*** lkarm has quit IRC19:57
*** achanda has joined #openstack-meeting19:57
krotscheckclarkb, crinkle: Thanks. The last activity I see is on the 17th, one week ago.19:57
krotscheckI'm guessing this is not super high priority when compared to the other infra goals?19:58
jheskethmordred: yep, lgtm19:58
*** zehicle has joined #openstack-meeting19:59
mordredjhesketh: thank you!19:59
*** zehicle has quit IRC19:59
clarkbkrotscheck: compared to last week and gerrit pgrade correct19:59
*** zehicle has joined #openstack-meeting19:59
krotscheckIf I could solicit some reviews on greghaynes's behalf, it'd be much appreciated :)19:59
fungiwe're just about out of time--thanks everyone!19:59
*** zehicle has quit IRC20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Nov 24 20:00:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-11-24-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-11-24-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-11-24-19.01.log.html20:00
crinkleo/20:00
jheskethThank you, fungi!20:00
yolandao/20:00
rcarrillocruzalright folks, nice to chat with you20:00
*** yolanda has left #openstack-meeting20:00
rcarrillocruzlaterz o/20:00
ttxAnyone here for the TC meeting ?20:00
flaper87o/20:00
markmcclaino/20:00
mesteryo/20:00
*** zehicle has joined #openstack-meeting20:00
jeblairayup20:00
* edleafe hides in the back20:00
*** zehicle has quit IRC20:00
*** bswartz has joined #openstack-meeting20:00
*** pots2 has joined #openstack-meeting20:00
ttxrussellb, annegentle, lifeless, mordred, dtroyer, jaypipes, sdague, dhellmann: around ?20:00
*** rfolco_ has quit IRC20:00
dhellmanno/20:01
*** alexpilotti has joined #openstack-meeting20:01
flaper87mordred: we know you're there. We saw your messages in the infra meeting20:01
flaper87:P20:01
*** zehicle has joined #openstack-meeting20:01
* flaper87 trolls mordred because thanksgiving is almost here20:01
*** rebase has joined #openstack-meeting20:01
mordredo/20:01
*** zehicle has quit IRC20:01
ttxmakes 720:01
* mordred too busy thinking about turkey20:01
claudiubo/20:01
*** penick has quit IRC20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Nov 24 20:01:46 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
ttxHi everyone20:01
openstackThe meeting name has been set to 'tc'20:01
ttxShort agenda for today:20:01
*** zehicle has joined #openstack-meeting20:01
alexpilottio/20:01
mesteryYay to short agenda! :)20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
*** zehicle has quit IRC20:02
ttxShould leave plenty of time for open discussion at the end, if you have anything you'd like us to discuss20:02
ttxI miss you all, you know that20:02
ttx#topic Adding os-win to OpenStack20:02
* flaper87 hugs ttx20:02
*** openstack changes topic to "Adding os-win to OpenStack (Meeting topic: tc)"20:02
*** sgundur has left #openstack-meeting20:02
ttx#link https://review.openstack.org/24702220:02
ttxLooks like this is pretty close, we just need to bikeshed on the name20:02
*** dcaro has left #openstack-meeting20:02
*** pots has quit IRC20:02
ttxto decouple the team name from its first deliverable a bit more20:02
* mestery gets out the red paintbrush20:03
ttxand also make it a bit less horrible-sounding20:03
ttxSo bring on the window analogies20:03
dhellmannyeah, I'd like to avoid the ceilometer/telemetry/ceilometer/telemetry dance with this team20:03
* flaper87 gets the black one20:03
alexpilottittx: looks like "winstackers" got overwhelming support :-)20:03
*** thingee has joined #openstack-meeting20:03
ttxyeah, it's deliciously cheesy20:03
mesteryttx: ++20:03
flaper87I don't mind winstackers, fwiw20:03
alexpilotti:)20:03
russellbhi, sorry20:04
ttxAlright, with the expanded scope i'm fine with this20:04
flaper87actually, it fits quite nicely20:04
*** kencjohnston has quit IRC20:04
* flaper87 is fine with it too20:04
*** zehicle has joined #openstack-meeting20:04
ttxAny other question on that ?20:04
*** zehicle has quit IRC20:04
ttxI think it's a team, it's in openstack community and since oslo doesn't want it it warrants its own team20:05
russellbwfm20:05
alexpilottittx: since oslo does not want us we though about "stockholm"20:05
lifelesso/20:06
*** sgundur has joined #openstack-meeting20:06
*** otter768 has joined #openstack-meeting20:06
*** sacharya has quit IRC20:06
dimsalexpilotti ouch :)20:06
ttxalexpilotti: it definitely sounds like a syndrome20:06
mordredwow20:06
mordredthe TC meeting is fun today20:06
ttxmordred: short and fun, the way it should always be20:07
dhellmannalexpilotti, :-)20:07
flaper87Oslo wants you... in a separate project/team <3 :D20:07
dhellmannflaper87 : ++20:07
*** zehicle has joined #openstack-meeting20:07
*** zehicle has quit IRC20:07
markmcclainwe've got 7 now20:07
rockygflaper87, ++20:07
ttxclaudiub: how many projects are expected to use os-win ?20:07
*** zehicle has joined #openstack-meeting20:08
*** fitoduarte has joined #openstack-meeting20:08
*** zehicle has quit IRC20:08
ttxoh, RTFCM20:08
claudiubttx: for now, it's going to be used in nova, cinder, networking-hyperv. the next one on the list would be os-brick.20:08
ttxnova, cinder, ceilometer, networking-hyperv20:08
ttxclaudiub: nice20:08
*** zehicle has joined #openstack-meeting20:08
* ttx likes deduplication20:08
*** zehicle has quit IRC20:09
alexpilotticlaudiub: manila20:09
ttxalright, we have a winner20:09
alexpilotticeilometer20:09
*** kebray has joined #openstack-meeting20:09
*** zehicle has joined #openstack-meeting20:09
ttxWill approve in 30 seconds unless someone screams another question20:09
*** zehicle has quit IRC20:09
bswartzanother question!20:09
ttxbswartz: nice try20:10
*** zehicle has joined #openstack-meeting20:10
edleafebswartz: next time try all caps20:10
mesterylol20:10
ttxAlright, it's in20:10
*** zehicle has quit IRC20:10
mesterywoot!20:10
flaper87w000t20:10
dhellmannwelcome, winstackers20:10
alexpilottiyeiiii20:10
flaper87mestery: 0 are more meaningful20:10
* flaper87 ducks20:10
*** otter768 has quit IRC20:10
*** zehicle has joined #openstack-meeting20:10
* mestery shakes his fist at flaper87 20:10
mestery;)20:10
ttx#topic Open discussion20:10
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:10
claudiubthanks folks for your support. :)20:11
*** zehicle has quit IRC20:11
ttxAlright, I had a few things to discuss20:11
ttxFirst we have a number of asserts in the governance review queue, you might want to check them out before I approve them20:11
*** zehicle has joined #openstack-meeting20:11
* flaper87 watches ttx take his hidden agenda out20:11
ttxsince a few of them just passed the age requirement20:11
*** zehicle has quit IRC20:11
ttxSecond... Shall we move this meeting to #openstack-meeting-cp ?20:11
*** changbl has quit IRC20:11
ttx(starting next week, obviously)20:12
*** zehicle has joined #openstack-meeting20:12
*** zehicle has quit IRC20:12
flaper87mmh, I'm fine either way, tbh. If that helps freeing up a slot for some other project, fine.20:12
dhellmannI suppose that would make sense20:12
*** zehicle has joined #openstack-meeting20:12
ttxIt's also to give a bit of publicity to that other channel,and make sure nobody holds a cross-project meeting at the same time as the TC meeting20:13
lifelessttx: did we declare bankrupytcy or something?20:13
*** zehicle has quit IRC20:13
lifelessttx: my backwards compat change is perhaps worth talking about20:13
markmcclainWe've also been in this venue for so long would we actually make it harder for those not tracking every detail harder to find us?20:13
*** zehicle has joined #openstack-meeting20:13
*** ociuhandu has quit IRC20:13
* dhellmann hands zehicle a better network connection20:13
* russellb looks at the 4 meeting channels he already has open20:13
*** zehicle has quit IRC20:13
jeblairi think the main reason to do it would be publicity as ttx says and to _create_ conflicts for #openstack-meeting-cp (so that cp meetings don't get scheduled over this one)20:13
jeblairthat said, i'm ambivalent :)20:13
dhellmannjeblair : +020:14
*** zehicle has joined #openstack-meeting20:14
ttxlifeless: yeah, we buried everyone under piles of bureaucracy and now nobody proposes anything :) Or as I like to think of it, we have caught up with the big tent backlog20:14
lifelesshttps://review.openstack.org/#/c/226157/20:14
*** zehicle has quit IRC20:14
*** neiljerram has quit IRC20:14
mordred+020:14
*** zehicle has joined #openstack-meeting20:14
lifelessmordred: +0 on the spec or +0 on ttx's comment?20:15
*** zehicle has quit IRC20:15
*** sdake_ has quit IRC20:15
ttxOK, I'll clartify with thingee (cross project master) and sdague (inventor of #openstack-meeting-cp) where they prefer it20:15
mordredthe moving the meeting20:15
ttxI think everyone is +0 on that one20:15
*** zehicle has joined #openstack-meeting20:15
ttxI assume everyone is20:15
*** sdake has joined #openstack-meeting20:15
*** AJaeger has quit IRC20:15
lifelessoh, there's another channel to add?20:15
lifelesssigh20:15
*** zehicle has quit IRC20:15
lifelessI can see why, but :/20:16
*** amrith is now known as _amrith_20:16
*** zehicle has joined #openstack-meeting20:16
* mordred has 165 open IRC windows currently, one more will have zero effect20:16
flaper87For the sake of publicity and avoid ppl scheduling cp meetings on the slot used for the TC meeting, then Im +120:16
*** zehicle has quit IRC20:16
lifelessmordred: it'll certainly get zero attention :)20:16
rockygSo, an announcement should turn up in this channel at the regular time, pointing folks to the other channel...20:16
mordredlifeless: most things I do fall into that category20:16
rockygIf it moves20:16
ttxlifeless: I'll admit my TODO to reread that spec is planned for tomorrow.20:16
*** zehicle has joined #openstack-meeting20:16
ttxrockyg: sure20:16
*** bvandenh has quit IRC20:17
*** zehicle has quit IRC20:17
*** banix has joined #openstack-meeting20:17
lifelessttx: and here I got it up a week ahead of this meeting to give you time :)20:17
*** zehicle has joined #openstack-meeting20:17
*** zehicle has quit IRC20:17
rockygA heads up on another topic.  Product WG started discussing stable and the stable project.20:17
ttxlifeless: been on my "tomorrow" list for a few days already20:17
lifelessso, AIUI the TC approves such specs20:17
* flaper87 feels bad for not reading lifeless' spec20:17
lifelesshow do I get actual attention, since its not a governence change20:18
rockygSeems there is interest in providing more "resources" for the stable project20:18
*** zehicle has joined #openstack-meeting20:18
ttxlifeless: yes, but the TC seeks consensus across the community first, we just recognize the consensus20:18
lifelessperhaps all cross projects specs should be automatically in our agenda20:18
lifelessttx: we do20:18
*** zehicle has quit IRC20:18
lifelessttx: but we try to do that broadly anyhow20:18
ttxbasically we don't vote, we summarize the community opinion20:18
*** otter768 has joined #openstack-meeting20:18
ttxWe vote, but just as someone else20:18
dhellmannI'd like to see some oslo-core +1 votes on that spec, for example20:18
*** zehicle has joined #openstack-meeting20:18
ttxusually we seek at least the affected PTLs +120:19
dhellmannthe keystone team has several libs, too, so that would be another good place to go for input20:19
ttxhere it's quite broad20:19
*** zehicle has quit IRC20:19
rockygFWIW, I like lifeless20:19
*** thangp has quit IRC20:19
*** zehicle has joined #openstack-meeting20:19
rockygSorry his spec.  Him.. Eehhh ;-)20:19
lifelessrockyg: o/20:19
*** zehicle has quit IRC20:19
ttxIt's a good test for the new cross-project process, which thingee and annegentle have been pushing20:20
*** zehicle has joined #openstack-meeting20:20
rockygSchedule a discussion, advertise its time, then give a week for comments?20:20
*** zehicle has quit IRC20:20
ttxrockyg: something like that20:20
*** zehicle has joined #openstack-meeting20:21
lifelessjeblair: / mordred: how do I look up notmyname in th gerrit add reviewer widget?20:21
*** zehicle has quit IRC20:21
*** apoorvad has quit IRC20:21
*** zehicle has joined #openstack-meeting20:21
ttxlifeless: Type John D and select Dickinson20:21
*** zehicle has quit IRC20:21
*** aranjan has joined #openstack-meeting20:22
ttx(I realize that's not really the answer to your question)20:22
*** zehicle has joined #openstack-meeting20:22
ttxOh, in other news...20:22
*** zehicle has quit IRC20:22
ttxI got some recent feedback from lawyers on the licensing question (triggered by the Juju charms application a few weeks ago)20:22
lifelessttx: there is no dickinson listed20:22
ttxSection 7.1(b) clearly makes ASLv2 mandatory for anything we'd want to put in tc-approved-release (or defcore).20:22
ttxlifeless: weird, there is on mine20:22
*** zehicle has joined #openstack-meeting20:23
lifelessttx: after a space it doesn't pipop20:23
lifelessttx: pop up20:23
ttxWe could make ASLv2 generally mandatory for type:service things just to make sure we do not hit a problem later on...20:23
*** zehicle has quit IRC20:23
dhellmannlifeless : try me@not.mn20:23
ttxBeyond services that we might want to cinlude in defcore one day, section 7.1(a) would allow ASLv2 + licenses which permit distribution under Apache 2 (MIT, BSD) for big-tent projects20:23
lifelessttx: ... its case sensitive. I did not see that coming20:23
ttxI'm trying to get clarification on the list of licenses that would be OK. If the interpretation above holds, it appears pretty clear that GPL* would not be an option20:23
ttxThought on that ? Questions I could channel back ?20:24
*** thangp has joined #openstack-meeting20:24
*** navid_ has joined #openstack-meeting20:24
russellbttx: thanks for following up on that :)20:25
jeblairttx: can you clarify 'big-tent'?20:25
mordredyah20:25
dhellmannttx: so both MIT and BSD can be re-distributed under Apache2?20:25
*** IlyaG has quit IRC20:25
russellbi wonder if we already violate what you just said though20:25
jeblairttx: cause earlier you said "tc-approved-release (or defcore)"20:25
russellbright20:26
dimsdhellmann : yes20:26
*** ayoung has quit IRC20:26
*** ayoung has joined #openstack-meeting20:26
mordredwe've previously gotten the explicit ok from legal to have GPL things be in our circle of things we work on as long as they weren't "part of the release"20:26
*** novas0x2a|laptop has joined #openstack-meeting20:26
ttxjeblair: released deliverables from an official project team ?20:26
ttxyeah, I need to get clarification that it wouldn't affect things we don't "release"20:27
dhellmannyeah, I thought we already had GPL projects from infra, if not other teams20:27
*** aranjan has quit IRC20:27
mordredwe do20:27
ttxor distribute20:27
flaper87we do have GPL things20:27
* flaper87 can't remember OTOH20:27
flaper87... can't remember which ones...20:27
ttxjeblair: so a Gerrit local fork would be fine -- a Puppet recipe for deploying openstack, not so sure20:28
*** dmowrer_ has quit IRC20:28
ttxI'll take that question back. A list of those GPL things might be helpful20:28
russellbmakes sense20:28
*** navid_ has quit IRC20:28
ttxusage vs. distribution I guess20:28
ttxalthough it's a bit of a fine line20:28
ttxI'll ask for clarification20:28
jeblairusage was never in question20:29
russellbhaving a git repo is kinda distribution20:29
lifelessright, 30 odd reviewers added20:29
russellbprobably not even kinda, just is20:29
lifelessI'm not sure this is the right mechanism :)20:29
lifelessjeblair: is gerrit able to make that index lookup case insensitive, do you know?20:29
jeblairwe certainly create,author,distribute gpl code though -- with the understanding it's not impacted by the bylaws because it's not part of the official openstack release20:29
* ttx reread 7.1(a)20:29
lifelessrockyg: if you like it you should put a vote on it20:29
ttxjeblair: maybe we could exempt release:independent things altogether20:30
mesteryttx: That would be interesting20:30
lifelessttx: that would imply they can never be defcore20:30
dhellmannttx: I don't think we should tie this to the release model. There's enough confusion about that as it is.20:31
ttxlifeless: no, that implies non-ASLv2 things can't be defcore20:31
jeblairlifeless: i think that matches my understanding of the intentent of 7.1a20:31
mordredyah20:31
ttxright20:31
*** changbl has joined #openstack-meeting20:31
mordredinfra does not release software that is intended to be part of defcore20:31
rockyglifeless, I now plan to, but I have to read it more closely to see if I have specific comments, first20:32
mordredso whie we're clearly "humans who are working on openstack" - our output is not generally confused with "software that is openstack"20:32
ttx7.1(a) is quite clear though20:32
lifelessttx: you're saying its a one-way thing: release-indepednedent '*may*' be suitable for defcore20:32
ttxThe Foundation shall generally accept contributions under ASLv2, or on a license on terms which will permit distribution under the Apache License 2.020:32
ttx(if teh BoD approves it)20:32
lifelessttx: 7.1 is *may*20:33
ttxyeah, shall generally accept contributions under ASLv2, and *may* accept a license on terms which will permit distribution under the ASLv220:33
lifelessok thats bad, the governance docs link to the cla now goes to a random how to contribute wiki page20:33
*** edtubill has joined #openstack-meeting20:34
lifeless(the links from the bottom of https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/)20:34
ttxheh20:35
lifelessttx: 7.1a does not say 'accept under ASLv2'20:35
lifelessttx: it says 'accept pursuant to the cla'20:35
ttxit says "under the CLA"20:35
lifelessand I can't find the CLA20:35
ttxand teh CLa says Apache v220:35
lifelessto verify20:35
ttxlifeless: you should keep copies of stuff you sign :)20:35
lifelessthe us government one *does not* say Apache V2 as a data point20:35
dhellmannlifeless : https://review.openstack.org/static/cla.html20:35
*** ociuhandu has joined #openstack-meeting20:35
ttxhttps://review.openstack.org/#/settings/agreements20:35
dhellmannvia ^^20:36
lifelessthanks20:36
lifelessso the icla is gone right? DCO now20:36
ttxheh, doesn't even mention Apache20:36
*** dmowrer has joined #openstack-meeting20:36
lifelessthe corporate CLA is not accessible from there in gerrit20:36
lifelessand thats relevant to most of us20:36
jeblairttx: amusingly enough, the cla is permissive enough to permit the foundation to license openstack under the gpl.20:36
*** neelashah1 has joined #openstack-meeting20:36
jeblairttx: (with a bylaws change)20:37
ttxjeblair: fun!20:37
lifelessttx: and yes, the cla does not say asl20:37
lifelessttx: thank you for bearing with my detail concerns :)20:37
lifelessicla20:37
jeblairi think the operative thing here is actually 7.1b20:37
lifelessis there a copy of the corporate cla around we can check ?20:37
* ttx just can't read legalese20:38
lifelesshttps://secure.echosign.com/public/hostedForm?formid=56JUVGT95E78X520:38
jeblairwhich is what causes the foundation to take all the contributions it has received under its super-broad cla and then turn around and license them to the world under the asl220:38
lifeless ^ corporate cla20:38
*** neelashah has quit IRC20:38
*** e0ne has quit IRC20:38
jeblairwhen it "distributes software"20:38
mordredI agree. this is all for the purposes of talking about the release we make20:38
dhellmannfor those following at home, the CCLA on echosign.com is linked from https://wiki.openstack.org/wiki/How_To_Contribute#Contributor_License_Agreement20:39
*** Swami has quit IRC20:39
lifelessjeblair: but only the software in 'OpenStack Technical Committee Approved Release'20:39
ttxjeblair: so there could be an argument that only the tc-approved release needs to limit choice of license20:39
jeblairso i guess the question is, when is it distributing software?  the approved release, or any git repo we host?  our understanding from previous lawyer conversations was more along the lines of 'the approved release'20:39
lifelessjeblair: not all distribution of software20:39
dhellmannjeblair : "the software in the OpenStack Technical Committee Approved Release"20:39
*** neelashah has joined #openstack-meeting20:39
ttxjeblair: ok, I'll go back to lawyers with additional questions. Thanks for your comments!20:40
*** penick has joined #openstack-meeting20:40
*** jprovazn has quit IRC20:40
ttxdhellmann: you had something else ?20:40
dhellmannyes, do we want to talk about https://review.openstack.org/#/c/244782/ -- the defcore test flagging from the nova driver team at oracle20:40
ttx#action ttx to clarify with lawyers what "distribution" means20:40
dhellmannseveral of you have already commented on the review20:40
lifelessttx: we probably want to check about the board's expectations here, even if the foundations are copacetic20:40
lifelesswe don't want to surprise anyone20:40
mordreddhellmann: it seems pretty unanimous feedback on the review20:41
ttxlifeless: we won't, this is at early stages20:41
*** neelashah1 has quit IRC20:41
rockygdhellmann, I think the flag issue is a resounding "no" but the linux VM issue is being separated.20:41
* flaper87 hasn't read that defcore review20:41
dhellmannrockyg : the two issues are pretty intimately tied together20:41
*** nadya_ has quit IRC20:41
lifelessflaper87: its very interesting20:41
dhellmannmordred : I wonder if it would help the defcore committee if we said something officially? or at least all voted.20:42
rockygYes.  But the second one needs *lots* more discussion.  First one is easier and so I believe it will be rejected shortly.20:42
ttxIt's actually a very good question being discussed there20:42
flaper87lifeless: I'll go through it, I just saw your latest comment and it's quite lengthy20:42
mordreddhellmann: I would be more than happy to help put together a resolution to that effect if it's unclear20:42
lifelessflaper87: :) all the good bits are the comments, not the actual review diff itself ;)20:42
*** yamahata has quit IRC20:42
rockygI think there might be a discussion scheduled for the next TC meeting?20:43
ttxrockyg: not on my agenda20:43
rockygMark Voelker indicated some such20:43
ttxyou mean next defcore meeting ?20:43
*** neelashah1 has joined #openstack-meeting20:43
*** achanda has quit IRC20:43
markvoelkeractually that was hogepodge...he mentioned he might put it on the agenda for next TC meeting20:43
ttxok, he didn't yet ;)20:43
rockygOK.  How does the next meeting look for that?  Plus what is discussed here, now, for prep.20:43
mordredthe number of things that linux DOESN'T run on these days is so small20:44
mordredthat trying to carve out it being ok to not be able to run linux20:44
ttxwell, next meeting agenda is pretty empty right now :)20:44
flaper87I'd appreciate some time to read through it, fwiw20:44
*** sacharya has joined #openstack-meeting20:44
flaper87so, yeah, next meeting ++20:44
dhellmannyeah, I think it's fine for the nova team to say drivers must support running linux20:44
*** neelashah has quit IRC20:44
rockygKewl20:44
mordredseems like a solution in search of a problem20:44
ttxAlright, next meeting20:45
dhellmannwfm20:45
ttx(if someone posts it to openstack-tc)20:45
ttxAnything else, anyone ?20:45
*** cfriesen__ has quit IRC20:46
ttxAnything we should be actively working on ? Anything you promised to get elected that you haven't delivered on yet ?20:46
rockygttx, I'll eat some turkey and drink lots of good wine in your honor at the Thanksgiving dinner ;-)20:46
*** neelashah has joined #openstack-meeting20:46
lifelessttx: the things I discussed two weeks back20:46
lifelessttx: I'm turning them into prose bit by bit20:46
ttxrockyg: if i don't drink it myself it's like it doesn't really exist20:46
flaper87we promissed to get a post out and we didn't20:47
flaper87we = comm wg20:47
ttxflaper87: boo20:47
flaper87I'll get to that20:47
flaper87:D20:47
lifelessttx: the leadership training stuff - gothicmindfood is looking into concrete details to help make it an actual specific proposal not a handwavy thing20:47
mordredrockyg: ++20:47
mordredlifeless: ++20:47
rockygNext time you're in the bay area.  You can drink some of ours...20:47
ttxlifeless: yes she's been in touch with my skeptical side20:47
lifelessttx: *side* implies no more than half...20:47
ttxlifeless: I always have two sides.20:47
flaper87ttx: just 2 ?20:47
ttxflaper87: sssh20:48
rockygflaper87,  ++20:48
* dhellmann imagines flaper87 as a dodecahedron20:48
*** neelashah1 has quit IRC20:48
ttxI can always be convinced by good arguments :)20:48
* rockyg thinks he might be a tesseract20:48
ttxone thing is sure flaper87 is always moving20:48
* flaper87 can't even see his sibling side20:48
flaper87ttx: lol, that's true20:48
flaper87:D20:48
rockygHence, the name...20:48
* dhellmann wonders how we devolved into discussing the wave/particle duality of flaper87 20:49
* flaper87 flaps everywhere20:49
flaper87omg, that's bad20:49
ttxalright, I guess that's all for today then20:49
ttxI'm fine with 11 minutes of my evening back20:49
* flaper87 gives ttx 1020:49
ttxAlso will use the time to contact a few folkds to advance stalled efforts20:49
flaper87there's a 1 min fee20:49
*** kencjohnston has joined #openstack-meeting20:50
ttxAre we done ?20:50
flaper87nothing here20:50
dhellmanndone20:50
ttx#endmeeting20:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:50
openstackMeeting ended Tue Nov 24 20:50:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-11-24-20.01.html20:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-11-24-20.01.txt20:50
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-11-24-20.01.log.html20:50
ttxHave a great thanksgiving all20:50
ttx-flaper87 -lifeless I guess20:50
lifelessI'll haev a normal work week :)20:51
ttxlifeless: yeah, same here. Time to get serious work done20:51
jeblairlifeless, ttx, flaper87: but you'll enjoy the quiet productiveness of thanksgiving :)20:51
ttxjeblair: exactly20:51
jeblairit's our gift to you20:51
ttxno more crazy threads to answer to20:51
lifelessif only we didn't need 2x+2A's :)20:52
flaper87lol20:52
*** matt6434 is now known as mattoliverau20:52
flaper87jeblair: stop making fun of ppl w/ holidays20:52
flaper87:P20:52
*** aysyd has quit IRC20:52
*** kebray has quit IRC20:54
jrollis cross-project meeting happening today? I didn't see an email indicating either way20:55
*** IlyaG has joined #openstack-meeting20:56
thingeejroll: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080400.html20:56
thingeeno meeting today20:56
jrollthingee: doh, thanks :)20:57
thingeejroll: enjoy a longer lunch ;)20:57
jroll:P20:57
*** kzaitsev_mb has joined #openstack-meeting20:57
*** rockyg has quit IRC20:58
*** maishsk has joined #openstack-meeting20:58
*** sdake has quit IRC20:59
*** sdake has joined #openstack-meeting20:59
*** salv-orlando has joined #openstack-meeting21:00
*** mrmartin has quit IRC21:01
*** salv-orl_ has joined #openstack-meeting21:01
*** raildo is now known as raildo-afk21:01
*** kebray has joined #openstack-meeting21:02
*** baoli has quit IRC21:02
smcginnisFree time!21:02
thingeeIn case folks missed it, the cross project meeting is being skipped http://lists.openstack.org/pipermail/openstack-dev/2015-November/080400.html21:02
thingeeseeya next week21:02
thingeelifeless: ack on agenda for next time :)21:03
*** Sukhdev has quit IRC21:04
*** salv-orlando has quit IRC21:05
*** kebray has quit IRC21:06
*** banix has quit IRC21:06
*** otter768 has quit IRC21:08
*** kzaitsev_mb has quit IRC21:10
*** dprince has quit IRC21:11
lifelessthingee: thanks21:11
*** kzaitsev_mb has joined #openstack-meeting21:13
*** penick has quit IRC21:14
*** rossella_s has quit IRC21:14
*** rossella_s has joined #openstack-meeting21:14
*** RuiChen has quit IRC21:16
*** RuiChen has joined #openstack-meeting21:16
*** davechen has left #openstack-meeting21:17
*** balajiiyer has left #openstack-meeting21:17
*** kzaitsev_mb has quit IRC21:21
*** penick has joined #openstack-meeting21:23
*** aranjan has joined #openstack-meeting21:24
*** henrynash has joined #openstack-meeting21:26
*** aranjan has quit IRC21:27
*** aranjan has joined #openstack-meeting21:27
*** otter768 has joined #openstack-meeting21:29
*** kebray has joined #openstack-meeting21:35
*** okrieg has quit IRC21:35
*** aorourke is now known as aorourke-afk21:36
*** dmowrer has quit IRC21:36
*** dmowrer has joined #openstack-meeting21:37
*** dims has quit IRC21:37
*** dims has joined #openstack-meeting21:38
*** gjayavelu has joined #openstack-meeting21:40
*** pratikmallya has quit IRC21:40
*** dmowrer has quit IRC21:41
*** kebray has quit IRC21:41
*** sacharya has quit IRC21:41
*** zaneb has quit IRC21:42
*** wbhuber_ has joined #openstack-meeting21:42
*** sacharya has joined #openstack-meeting21:43
*** pratikmallya has joined #openstack-meeting21:46
*** elo has quit IRC21:46
*** jaypipes has quit IRC21:47
*** sacharya has quit IRC21:47
*** ayoung has quit IRC21:48
*** otter768 has quit IRC21:48
*** dimtruck is now known as zz_dimtruck21:48
*** boris-42 has quit IRC21:48
*** nmagnezi has quit IRC21:49
*** adahms has joined #openstack-meeting21:50
*** yamahata has joined #openstack-meeting21:50
*** xingchao has joined #openstack-meeting21:51
*** ijw_ has quit IRC21:52
*** Swami has joined #openstack-meeting21:53
*** elo has joined #openstack-meeting21:54
*** maishsk has quit IRC21:55
*** wbhuber_ has quit IRC21:55
*** xingchao has quit IRC21:55
*** glauco has quit IRC21:58
*** glauco_ has joined #openstack-meeting21:58
*** glauco_ has quit IRC21:58
*** MaxPC has quit IRC22:00
*** topol has quit IRC22:00
*** kencjohnston has quit IRC22:02
*** ijw has joined #openstack-meeting22:02
*** gjayavelu has quit IRC22:02
*** dmowrer has joined #openstack-meeting22:02
*** kencjohnston has joined #openstack-meeting22:03
*** _amrith_ is now known as amrith22:03
*** gjayavelu has joined #openstack-meeting22:03
*** hashar has quit IRC22:04
*** dmowrer has quit IRC22:06
*** JRobinson__ has joined #openstack-meeting22:08
*** apoorvad has joined #openstack-meeting22:08
*** Sukhdev has joined #openstack-meeting22:12
*** baoli has joined #openstack-meeting22:12
*** edtubill has quit IRC22:13
*** njohnston is now known as nate_gone22:14
*** pratikmallya has quit IRC22:14
*** SotK has quit IRC22:16
*** Piet has quit IRC22:16
*** SotK has joined #openstack-meeting22:17
*** paul-carlton has joined #openstack-meeting22:18
*** gjayavelu has quit IRC22:19
*** baoli has quit IRC22:19
*** zaina has joined #openstack-meeting22:20
*** thorst_ has joined #openstack-meeting22:21
*** kzaitsev_mb has joined #openstack-meeting22:21
*** thorst__ has joined #openstack-meeting22:22
*** vgridnev has quit IRC22:24
*** iyamahat has quit IRC22:24
*** thorst_ has quit IRC22:25
*** kzaitsev_mb has quit IRC22:26
*** thorst__ has quit IRC22:26
*** thorst_ has joined #openstack-meeting22:27
*** s3wong has joined #openstack-meeting22:27
*** aranjan_ has joined #openstack-meeting22:27
*** cwolferh has quit IRC22:27
*** cwolferh has joined #openstack-meeting22:28
*** jckasper has quit IRC22:29
*** aranjan has quit IRC22:29
*** thorst_ has quit IRC22:31
*** achanda has joined #openstack-meeting22:31
*** thangp has quit IRC22:31
*** unicell1 has joined #openstack-meeting22:32
*** achanda has quit IRC22:33
*** iyamahat has joined #openstack-meeting22:34
*** unicell has quit IRC22:34
*** IlyaG has quit IRC22:36
*** glauco_ has joined #openstack-meeting22:36
*** IlyaG has joined #openstack-meeting22:38
*** kcalman has quit IRC22:39
*** IlyaG has quit IRC22:39
*** zaina has quit IRC22:43
*** zaina has joined #openstack-meeting22:45
*** zaina has quit IRC22:45
*** jichen has quit IRC22:45
*** pratikmallya has joined #openstack-meeting22:46
*** unicell1 has quit IRC22:49
*** doug-fis_ has joined #openstack-meeting22:49
*** unicell has joined #openstack-meeting22:49
*** kencjohnston has quit IRC22:49
*** doug-fish has quit IRC22:53
*** doug-fis_ has quit IRC22:53
*** hemna is now known as hemnafk22:55
*** wuhg has joined #openstack-meeting22:57
*** peristeri has quit IRC22:57
*** sacharya has joined #openstack-meeting22:57
*** rohit_ has joined #openstack-meeting22:58
*** FallenPegasus has joined #openstack-meeting22:59
*** sneti has quit IRC23:00
*** topol has joined #openstack-meeting23:01
*** sgundur has quit IRC23:02
*** harshs has quit IRC23:03
*** aranjan_ has quit IRC23:03
*** mestery has quit IRC23:04
*** doug-fish has joined #openstack-meeting23:04
*** mestery has joined #openstack-meeting23:05
*** topol has quit IRC23:05
*** spotz is now known as spotz_zzz23:06
*** ddieterly has quit IRC23:07
*** aranjan has joined #openstack-meeting23:08
*** otter768 has joined #openstack-meeting23:08
*** doug-fish has quit IRC23:08
*** harshs has joined #openstack-meeting23:08
*** boris-42 has joined #openstack-meeting23:10
*** ddieterly has joined #openstack-meeting23:11
*** baoli has joined #openstack-meeting23:11
*** dkranz has quit IRC23:12
*** rbak has quit IRC23:12
*** aranjan_ has joined #openstack-meeting23:13
*** baoli has quit IRC23:13
*** dane_leblanc has quit IRC23:14
*** bvandenh has joined #openstack-meeting23:14
*** baoli has joined #openstack-meeting23:14
*** baoli has quit IRC23:16
*** aranjan has quit IRC23:16
*** aranjan_ has quit IRC23:18
*** Leom has quit IRC23:19
*** henrynash has quit IRC23:20
*** FallenPegasus has quit IRC23:22
*** aimon has quit IRC23:23
*** apoorvad has quit IRC23:25
*** dims_ has joined #openstack-meeting23:28
*** dims has quit IRC23:29
*** thorst has joined #openstack-meeting23:29
*** zehicle has joined #openstack-meeting23:31
*** IlyaG has joined #openstack-meeting23:31
*** aranjan has joined #openstack-meeting23:32
*** claudiub has quit IRC23:33
*** ijw has quit IRC23:35
*** bvandenh has quit IRC23:35
*** ntata has quit IRC23:36
*** thorst has quit IRC23:36
*** alexpilotti has quit IRC23:38
*** Swami has quit IRC23:40
*** aranjan has quit IRC23:40
*** tochi has joined #openstack-meeting23:41
*** iyamahat has quit IRC23:45
*** aimon has joined #openstack-meeting23:46
*** lkarm has joined #openstack-meeting23:51
*** apoorvad has joined #openstack-meeting23:51
*** neelashah1 has joined #openstack-meeting23:52
*** ijw has joined #openstack-meeting23:52
*** aranjan has joined #openstack-meeting23:52
*** neelashah has quit IRC23:52
*** otter768 has quit IRC23:53
*** neelashah1 has quit IRC23:56
*** neelashah has joined #openstack-meeting23:57
*** Swami has joined #openstack-meeting23:59

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