Tuesday, 2015-12-01

*** otter768 has joined #openstack-meeting00:01
*** Fdaisuke has joined #openstack-meeting00:02
*** dimtruck is now known as zz_dimtruck00:02
*** arcee has quit IRC00:08
*** penick has quit IRC00:10
*** sacharya has joined #openstack-meeting00:12
*** emagana_ has quit IRC00:13
*** belmoreira has quit IRC00:15
*** rebase has quit IRC00:15
*** sacharya has quit IRC00:17
*** alexpilotti has joined #openstack-meeting00:22
*** zz_dimtruck is now known as dimtruck00:23
*** openstackstatus has quit IRC00:24
*** otter768 has quit IRC00:24
*** openstackstatus has joined #openstack-meeting00:25
*** ChanServ sets mode: +v openstackstatus00:25
*** alexpilotti has quit IRC00:27
*** JRobinson__ is now known as JRobinson__afk00:28
*** sgundur has joined #openstack-meeting00:29
*** baoli has quit IRC00:29
*** raildo is now known as raildo-afk00:30
*** otter768 has joined #openstack-meeting00:30
*** tej has joined #openstack-meeting00:32
*** Swami has quit IRC00:34
*** rebase has joined #openstack-meeting00:34
*** tej has quit IRC00:39
*** ajmiller has quit IRC00:43
*** alexpilotti has joined #openstack-meeting00:43
*** dmacpher has joined #openstack-meeting00:44
*** sdake has joined #openstack-meeting00:46
*** sgundur has left #openstack-meeting00:47
*** thorst has joined #openstack-meeting00:47
*** alexpilotti has quit IRC00:47
*** thorst has quit IRC00:48
*** thorst has joined #openstack-meeting00:48
*** hoangcx has joined #openstack-meeting00:50
*** rebase has quit IRC00:51
*** hoangcx has left #openstack-meeting00:51
*** galstrom is now known as galstrom_zzz00:55
*** ricolin has joined #openstack-meeting00:55
*** francois_ has quit IRC00:56
*** francois has joined #openstack-meeting00:56
*** salv-orl_ has joined #openstack-meeting00:57
*** salv-orl_ has quit IRC00:59
*** salv-orlando has quit IRC01:00
*** thorst has quit IRC01:00
*** thorst has joined #openstack-meeting01:01
*** aranjan has quit IRC01:04
*** aimon has quit IRC01:05
*** thorst has quit IRC01:05
*** aranjan has joined #openstack-meeting01:06
*** sdake has quit IRC01:06
*** epico has joined #openstack-meeting01:07
*** dimtruck is now known as zz_dimtruck01:07
*** peterlisak has quit IRC01:11
*** arvinchou_ has joined #openstack-meeting01:11
*** peterlisak has joined #openstack-meeting01:12
*** epico has quit IRC01:12
*** alop has quit IRC01:14
*** pvaneck has quit IRC01:14
*** JRobinson__afk is now known as JRobinson__01:15
*** baoli has joined #openstack-meeting01:17
*** sdake has joined #openstack-meeting01:19
*** FallenPegasus has joined #openstack-meeting01:21
*** annp has joined #openstack-meeting01:27
*** novas0x2a|laptop has quit IRC01:28
*** novas0x2a|laptop has joined #openstack-meeting01:28
*** banix has joined #openstack-meeting01:29
*** kjorgensen has quit IRC01:29
*** kencjohnston has joined #openstack-meeting01:29
*** penick has joined #openstack-meeting01:29
*** dzimine has quit IRC01:30
*** dzimine_ has quit IRC01:30
*** tfukushima has joined #openstack-meeting01:31
*** f13o has quit IRC01:31
*** sdake has quit IRC01:32
*** ktrmzn has quit IRC01:34
*** aranjan has quit IRC01:37
*** mudassirlatif has quit IRC01:38
*** aimon has joined #openstack-meeting01:40
*** thorst has joined #openstack-meeting01:42
*** novas0x2a|laptop has quit IRC01:44
*** dilip has quit IRC01:45
*** markvoelker has quit IRC01:46
*** haomaiwang has joined #openstack-meeting01:46
*** dilip has joined #openstack-meeting01:47
*** yamamoto has joined #openstack-meeting01:51
*** annp has left #openstack-meeting01:51
*** kjorgensen has joined #openstack-meeting01:51
*** ricolin has quit IRC01:52
*** baohua has joined #openstack-meeting01:52
*** dilip has quit IRC01:53
*** julim has joined #openstack-meeting01:53
*** kjorgensen has quit IRC01:56
*** leeantho has quit IRC01:57
*** tochi has quit IRC01:59
*** salv-orlando has joined #openstack-meeting02:00
*** shashank_hegde has quit IRC02:00
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-meeting02:01
*** ober37 has joined #openstack-meeting02:03
*** s3wong has quit IRC02:03
*** ober37 has left #openstack-meeting02:04
*** p0rtal has quit IRC02:06
*** penick has quit IRC02:06
*** salv-orlando has quit IRC02:07
*** aleksandr_null_ has quit IRC02:09
*** ricolin has joined #openstack-meeting02:10
*** aleksandr_null has joined #openstack-meeting02:10
*** xingchao has joined #openstack-meeting02:13
*** bobh has joined #openstack-meeting02:17
*** bobh has quit IRC02:17
*** rfolco has joined #openstack-meeting02:21
*** ricolin has quit IRC02:26
*** shashank_hegde has joined #openstack-meeting02:28
*** aleksandr_null has quit IRC02:29
*** aleksandr_null has joined #openstack-meeting02:30
*** mtanino has quit IRC02:30
*** haomaiwang has quit IRC02:33
*** sacharya has joined #openstack-meeting02:36
*** liusheng has joined #openstack-meeting02:40
*** thorst has quit IRC02:41
*** MaxPC has quit IRC02:41
*** thorst has joined #openstack-meeting02:41
*** unicell1 has quit IRC02:42
*** sacharya_ has joined #openstack-meeting02:43
*** aleksandr_null has quit IRC02:45
*** sacharya has quit IRC02:46
*** aleksandr_null has joined #openstack-meeting02:48
*** banix has quit IRC02:48
*** thorst has quit IRC02:50
*** rfolco has quit IRC02:51
*** pm90_ has quit IRC02:55
*** sputnik13 has quit IRC02:56
*** fawadkhaliq has joined #openstack-meeting02:57
*** yamahata has quit IRC02:58
*** red_trela has quit IRC02:59
*** xingchao has quit IRC03:01
*** salv-orlando has joined #openstack-meeting03:01
*** xingchao has joined #openstack-meeting03:02
*** houming has joined #openstack-meeting03:04
*** red_trela has joined #openstack-meeting03:07
*** salv-orlando has quit IRC03:09
*** kzaitsev_mb has joined #openstack-meeting03:10
*** gcb has joined #openstack-meeting03:13
*** tochi has joined #openstack-meeting03:17
*** yfujioka has quit IRC03:19
*** alexpilotti has joined #openstack-meeting03:21
*** alexpilotti has quit IRC03:26
*** zhaobo0825 has quit IRC03:26
*** zhaobo0825 has joined #openstack-meeting03:27
*** sacharya_ has quit IRC03:28
*** sacharya has joined #openstack-meeting03:29
*** gcb has quit IRC03:32
*** thorst has joined #openstack-meeting03:32
*** thorst has quit IRC03:33
*** thorst has joined #openstack-meeting03:34
*** houming has quit IRC03:35
*** ayoung has quit IRC03:35
*** yamahata has joined #openstack-meeting03:36
*** thorst has quit IRC03:42
*** MaxPC has joined #openstack-meeting03:42
*** xingchao has quit IRC03:43
*** houming has joined #openstack-meeting03:43
*** xingchao has joined #openstack-meeting03:44
*** kzaitsev_mb has quit IRC03:45
*** baoli has quit IRC03:46
*** baoli has joined #openstack-meeting03:47
*** spzala has joined #openstack-meeting03:50
*** spzala has quit IRC03:54
*** liusheng has quit IRC03:56
*** liusheng has joined #openstack-meeting03:56
*** zhaobo0825 has quit IRC04:00
*** pballand has quit IRC04:02
*** irenab_ has joined #openstack-meeting04:03
*** aspiers has quit IRC04:04
*** irenab has quit IRC04:05
*** irenab_ is now known as irenab04:05
*** aranjan has joined #openstack-meeting04:06
*** kebray has joined #openstack-meeting04:07
*** kebray has quit IRC04:09
*** JRobinson__ is now known as JRobinson__afk04:11
*** kzaitsev_mb has joined #openstack-meeting04:14
*** xingchao has quit IRC04:15
*** kebray has joined #openstack-meeting04:15
*** aranjan has quit IRC04:16
*** kebray has quit IRC04:18
*** pballand has joined #openstack-meeting04:20
*** kebray has joined #openstack-meeting04:20
*** kencjohnston has quit IRC04:21
*** tfukushima has quit IRC04:25
*** kzaitsev_mb has quit IRC04:25
*** mudassirlatif has joined #openstack-meeting04:25
*** aranjan has joined #openstack-meeting04:27
*** tfukushima has joined #openstack-meeting04:28
*** pballand has quit IRC04:28
*** baoli has quit IRC04:30
*** aranjan has quit IRC04:32
*** epico has joined #openstack-meeting04:33
*** roxanaghe has joined #openstack-meeting04:34
*** otter768 has quit IRC04:35
*** sacharya has quit IRC04:37
*** zhhuabj has quit IRC04:37
*** sacharya has joined #openstack-meeting04:38
*** thorst has joined #openstack-meeting04:41
*** tfukushima has quit IRC04:42
*** houming has quit IRC04:42
*** mudassirlatif has quit IRC04:47
*** thorst has quit IRC04:49
*** houming has joined #openstack-meeting04:51
*** achanda has joined #openstack-meeting04:51
*** zhhuabj has joined #openstack-meeting04:52
*** gyee has quit IRC04:52
*** MaxPC has quit IRC04:55
*** pots has quit IRC04:57
*** pradipta has joined #openstack-meeting04:57
*** sdake has joined #openstack-meeting05:00
*** adahms has quit IRC05:00
*** zhhuabj has quit IRC05:00
*** kebray_ has joined #openstack-meeting05:03
*** sdake_ has joined #openstack-meeting05:03
*** aeng has quit IRC05:04
*** sdake has quit IRC05:04
*** kebray has quit IRC05:05
*** dixiaoli has joined #openstack-meeting05:05
*** changbl has quit IRC05:07
*** haomaiwa_ has joined #openstack-meeting05:08
*** sdake_ has quit IRC05:10
*** yamahata has quit IRC05:10
*** kebray_ has quit IRC05:11
*** haomaiw__ has joined #openstack-meeting05:11
*** kebray has joined #openstack-meeting05:13
*** haomaiwa_ has quit IRC05:14
*** zhhuabj has joined #openstack-meeting05:17
*** gcb has joined #openstack-meeting05:18
*** arcee has joined #openstack-meeting05:18
*** JRobinson__afk is now known as JRobinson__05:19
*** gcb has quit IRC05:19
*** gcb has joined #openstack-meeting05:20
*** arcee_ has joined #openstack-meeting05:20
*** aranjan has joined #openstack-meeting05:20
*** arcee has quit IRC05:23
*** yfried_ has joined #openstack-meeting05:24
*** aeng has joined #openstack-meeting05:25
*** whenry_ has quit IRC05:25
*** FallenPegasus has quit IRC05:26
*** amotoki has joined #openstack-meeting05:26
*** FallenPegasus has joined #openstack-meeting05:26
*** numans has joined #openstack-meeting05:27
*** pradipta has quit IRC05:27
*** baohua has quit IRC05:29
*** arcee_ has quit IRC05:29
*** haomaiw__ has quit IRC05:30
*** fawadkhaliq has quit IRC05:36
*** p0rtal has joined #openstack-meeting05:36
*** sacharya_ has joined #openstack-meeting05:38
*** houming has quit IRC05:39
*** jdurgin1 has joined #openstack-meeting05:39
*** jdurgin1 has quit IRC05:39
*** emagana has joined #openstack-meeting05:40
*** sacharya has quit IRC05:40
*** arcee has joined #openstack-meeting05:43
*** tfukushima has joined #openstack-meeting05:44
*** arcee_ has joined #openstack-meeting05:45
*** tfukushima has quit IRC05:45
*** vgridnev has joined #openstack-meeting05:45
*** irenab has quit IRC05:46
*** tfukushima has joined #openstack-meeting05:46
*** thorst has joined #openstack-meeting05:47
*** arcee has quit IRC05:48
*** houming has joined #openstack-meeting05:48
*** berendt has joined #openstack-meeting05:52
*** tfukushi_ has joined #openstack-meeting05:52
*** thorst has quit IRC05:54
*** tfukushima has quit IRC05:56
*** kozhukalov_ has joined #openstack-meeting05:57
*** fawadkhaliq has joined #openstack-meeting05:58
*** fawadkhaliq has quit IRC05:58
*** fawadkhaliq has joined #openstack-meeting05:59
*** emagana has quit IRC06:02
*** yfried_ has quit IRC06:03
*** mrmartin has joined #openstack-meeting06:04
*** dixiaoli has quit IRC06:05
*** dixiaoli has joined #openstack-meeting06:05
*** xingchao has joined #openstack-meeting06:07
*** JRobinson__ has quit IRC06:08
*** salv-orlando has joined #openstack-meeting06:09
*** arcee_ has quit IRC06:09
*** dims has quit IRC06:09
*** Kevin_Zheng has joined #openstack-meeting06:10
*** ildikov has quit IRC06:12
*** sdake has joined #openstack-meeting06:12
*** dims has joined #openstack-meeting06:14
*** salv-orlando has quit IRC06:14
*** emagana has joined #openstack-meeting06:18
*** ihrachys has joined #openstack-meeting06:18
*** ihrachys has quit IRC06:20
*** bzhao0825 has joined #openstack-meeting06:20
*** pm90_ has joined #openstack-meeting06:21
*** emagana has quit IRC06:22
*** klkumar has joined #openstack-meeting06:22
*** irenab has joined #openstack-meeting06:24
*** mhickey has joined #openstack-meeting06:25
*** sacharya_ has quit IRC06:28
*** otter768 has joined #openstack-meeting06:36
*** sdake has quit IRC06:38
*** sc68cal has quit IRC06:40
*** otter768 has quit IRC06:40
*** mrmartin has quit IRC06:43
*** sc68cal has joined #openstack-meeting06:44
*** aeng has quit IRC06:45
*** dmacpher has quit IRC06:45
*** jprovazn has joined #openstack-meeting06:49
*** yamahata has joined #openstack-meeting06:50
*** FallenPegasus has quit IRC06:51
*** thorst has joined #openstack-meeting06:52
*** gcb has quit IRC06:53
*** amit213 has quit IRC06:55
*** amit213 has joined #openstack-meeting06:55
*** aeng has joined #openstack-meeting06:57
*** thorst has quit IRC06:59
*** achanda_ has joined #openstack-meeting07:00
*** hoangcx has joined #openstack-meeting07:02
*** hoangcx has left #openstack-meeting07:02
*** achanda has quit IRC07:03
*** vgridnev has quit IRC07:06
*** nadya_ has joined #openstack-meeting07:07
*** vahidh has quit IRC07:09
*** neeti has joined #openstack-meeting07:12
*** nadya_ has quit IRC07:12
*** kebray has quit IRC07:15
*** egallen has joined #openstack-meeting07:20
*** roxanaghe has quit IRC07:20
*** alexschm has joined #openstack-meeting07:22
*** tochi has quit IRC07:22
*** egallen_ has joined #openstack-meeting07:23
*** egallen_ has quit IRC07:24
*** egallen has quit IRC07:24
*** vgridnev has joined #openstack-meeting07:31
*** egallen has joined #openstack-meeting07:34
*** pm90_ has quit IRC07:34
*** kozhukalov_ has quit IRC07:35
*** achanda_ has quit IRC07:36
*** spzala has joined #openstack-meeting07:38
*** yfried_ has joined #openstack-meeting07:40
*** spzala has quit IRC07:43
*** lennyb has joined #openstack-meeting07:45
*** mosinut has left #openstack-meeting07:48
*** egallen has quit IRC07:51
*** fawadkhaliq has quit IRC07:52
*** fawadkhaliq has joined #openstack-meeting07:53
*** tfukushi_ has quit IRC07:53
*** fawadkhaliq has quit IRC07:53
*** aburmashev has joined #openstack-meeting07:54
*** fawadkhaliq has joined #openstack-meeting07:54
*** fawadkhaliq has quit IRC07:57
*** fawadkhaliq has joined #openstack-meeting07:57
*** thorst has joined #openstack-meeting07:57
*** fawadkhaliq has quit IRC07:57
*** pots has joined #openstack-meeting07:57
*** fawadkhaliq has joined #openstack-meeting07:58
*** egallen has joined #openstack-meeting07:58
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Dec  1 08:00:46 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
anteayahow are you aburmashev08:01
aburmashevgood, followed mmedvede advice and got nodepool installed. Now working on zuul + proxy )08:02
*** pots has quit IRC08:02
*** fawadkhaliq has quit IRC08:02
*** fawadkhaliq has joined #openstack-meeting08:03
anteayadid you see the link to the patch asselin shared?08:03
*** fawadkhaliq has quit IRC08:03
aburmashevthanks. No, i did not see any link08:04
*** alexpilotti has joined #openstack-meeting08:04
*** fawadkhaliq has joined #openstack-meeting08:04
anteaya#link https://review.openstack.org/#/c/240131/08:04
*** thorst has quit IRC08:04
aburmashevanteaya: Great! thanks a lot08:05
anteayaseems it is just you and I so far today08:05
*** reedip has quit IRC08:05
anteayais there anything else you would like to discuss today?08:05
*** fzdarsky has joined #openstack-meeting08:06
aburmashevwell, no )08:06
aburmasheveverything else is either working, or i have not yet moved far enough to face new problems )08:07
*** p0rtal has quit IRC08:08
anteayagood news08:08
anteayano problems for the moment!08:08
*** alexpilotti has quit IRC08:08
*** coolsvap has quit IRC08:09
aburmashevindeed )08:10
*** FallenPegasus has joined #openstack-meeting08:10
*** jlanoux has joined #openstack-meeting08:10
lennybHi all. I have nothing to discuss today as well08:11
anteayahi lennyb thanks for saying so08:12
*** bvandenh has joined #openstack-meeting08:12
anteayanice to see you08:12
*** safchain has joined #openstack-meeting08:12
lennybanteaya: you too. I tried to connect yesterday, but freenode was probably down08:13
*** ildikov has joined #openstack-meeting08:13
*** jichen has joined #openstack-meeting08:13
*** zeih has joined #openstack-meeting08:13
*** aranjan has quit IRC08:14
anteayawell freenode wasn't happy yesterday08:15
anteayathat is true08:15
anteayatoday it is happier08:15
*** irenab has quit IRC08:17
*** irenab has joined #openstack-meeting08:20
*** nadya_ has joined #openstack-meeting08:20
*** roxanaghe has joined #openstack-meeting08:20
anteayawell if we don't have any more items to discuss08:20
anteayaany objection to me closing the meeting?08:21
*** reedip has joined #openstack-meeting08:22
*** nmagnezi has joined #openstack-meeting08:22
lennybhave a good day...08:22
anteayathanks you too08:23
*** achanda has joined #openstack-meeting08:23
anteayasee you next week08:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:23
openstackMeeting ended Tue Dec  1 08:23:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-12-01-08.00.html08:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-12-01-08.00.txt08:23
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-12-01-08.00.log.html08:23
*** MattMan has quit IRC08:23
*** MattMan has joined #openstack-meeting08:24
*** yfried_ has quit IRC08:24
*** yfried_ has joined #openstack-meeting08:24
*** lennyb has quit IRC08:25
*** mhickey has quit IRC08:25
*** roxanaghe has quit IRC08:26
*** kjorgensen has joined #openstack-meeting08:26
*** berendt has quit IRC08:27
*** hichihara has quit IRC08:27
*** nadya__ has joined #openstack-meeting08:28
*** nadya_ has quit IRC08:28
*** kjorgensen has quit IRC08:31
*** dbite has joined #openstack-meeting08:33
*** nadya_ has joined #openstack-meeting08:34
*** pm90_ has joined #openstack-meeting08:35
*** nadya__ has quit IRC08:36
*** rcernin has joined #openstack-meeting08:37
*** otter768 has joined #openstack-meeting08:37
*** mrmartin has joined #openstack-meeting08:37
*** sankarshan_away is now known as sankarshan08:39
*** pm90_ has quit IRC08:39
*** phil__ has joined #openstack-meeting08:40
*** otter768 has quit IRC08:41
*** aspiers has joined #openstack-meeting08:41
*** emagana has joined #openstack-meeting08:42
*** tochi has joined #openstack-meeting08:44
*** nadya_ has quit IRC08:45
*** jlanoux has quit IRC08:45
*** rossella_s has joined #openstack-meeting08:45
*** nadya_ has joined #openstack-meeting08:45
*** emagana has quit IRC08:46
*** qwebirc60969 has joined #openstack-meeting08:46
*** kzaitsev_mb has joined #openstack-meeting08:47
*** ricolin has joined #openstack-meeting08:47
*** qwebirc60969 has quit IRC08:48
*** jlanoux has joined #openstack-meeting08:48
*** dmowrer has joined #openstack-meeting08:52
*** egallen has quit IRC08:53
*** egallen has joined #openstack-meeting08:54
*** yfried_ has quit IRC08:56
*** tfukushima has joined #openstack-meeting08:56
*** kozhukalov_ has joined #openstack-meeting08:56
*** dmowrer has quit IRC08:56
*** yfried_ has joined #openstack-meeting08:57
*** dguitarbite has quit IRC08:58
*** dbite has quit IRC08:58
*** dguitarbite has joined #openstack-meeting08:58
*** toscalix has joined #openstack-meeting08:59
*** egallen has quit IRC08:59
*** nadya__ has joined #openstack-meeting08:59
*** belmoreira has joined #openstack-meeting09:00
*** egallen has joined #openstack-meeting09:00
*** gmann has quit IRC09:01
*** derekh has joined #openstack-meeting09:02
*** fawadkhaliq has quit IRC09:03
*** nadya_ has quit IRC09:03
*** fawadkhaliq has joined #openstack-meeting09:03
*** ildikov has quit IRC09:04
*** thorst has joined #openstack-meeting09:04
*** nadya__ has quit IRC09:04
*** coolsvap has joined #openstack-meeting09:04
*** ildikov has joined #openstack-meeting09:06
*** kzaitsev_mb has quit IRC09:07
*** xek has joined #openstack-meeting09:07
*** thorst has quit IRC09:09
*** itzdilip has joined #openstack-meeting09:09
*** mbound_ has joined #openstack-meeting09:09
*** aranjan has joined #openstack-meeting09:11
*** ygbo_ has joined #openstack-meeting09:11
*** ygbo has joined #openstack-meeting09:11
*** ygbo_ has quit IRC09:13
*** ygbo has quit IRC09:13
*** nadya_ has joined #openstack-meeting09:13
*** ygbo has joined #openstack-meeting09:14
*** itzdilip has quit IRC09:17
*** roxanaghe has joined #openstack-meeting09:23
*** ndipanov has quit IRC09:23
*** ndipanov has joined #openstack-meeting09:24
*** mbound_ has quit IRC09:27
*** itzdilip has joined #openstack-meeting09:27
*** roxanaghe has quit IRC09:28
*** miyagishi_t has quit IRC09:29
*** zhhuabj has quit IRC09:30
*** ricolin has quit IRC09:30
*** ricolin has joined #openstack-meeting09:31
*** itzdilip has quit IRC09:32
*** adiantum has joined #openstack-meeting09:33
*** hashar has joined #openstack-meeting09:34
*** salv-orlando has joined #openstack-meeting09:35
*** salv-orlando has quit IRC09:35
*** mbound_ has joined #openstack-meeting09:35
*** berendt has joined #openstack-meeting09:35
*** salv-orlando has joined #openstack-meeting09:35
*** achanda has quit IRC09:38
*** vikram_ has joined #openstack-meeting09:41
*** mhickey has joined #openstack-meeting09:41
*** Ramanjaneya has joined #openstack-meeting09:41
*** kozhukalov_ has quit IRC09:44
*** zhhuabj has joined #openstack-meeting09:45
*** aranjan has quit IRC09:45
*** sudipto has joined #openstack-meeting09:45
*** bzhao0825 has left #openstack-meeting09:46
*** houming has quit IRC09:50
*** Ramanjaneya has quit IRC09:58
*** kozhukalov_ has joined #openstack-meeting09:58
*** nmagnezi has quit IRC09:59
*** megm has quit IRC10:02
*** dilip has joined #openstack-meeting10:02
*** tfukushima has quit IRC10:03
*** megm has joined #openstack-meeting10:04
*** neiljerram has joined #openstack-meeting10:04
*** thorst has joined #openstack-meeting10:07
*** nmagnezi has joined #openstack-meeting10:07
*** wuhg has joined #openstack-meeting10:09
*** dilip has quit IRC10:11
*** dilip has joined #openstack-meeting10:11
*** paul-carlton1 has joined #openstack-meeting10:13
*** thorst has quit IRC10:14
*** pm90_ has joined #openstack-meeting10:15
*** changzhi has joined #openstack-meeting10:16
*** rfolco has joined #openstack-meeting10:19
*** Ramanjaneya has joined #openstack-meeting10:23
*** pm90_ has quit IRC10:23
*** berendt has quit IRC10:24
*** epico has quit IRC10:25
*** roxanaghe has joined #openstack-meeting10:25
*** kzaitsev_mb has joined #openstack-meeting10:27
*** jlanoux has quit IRC10:29
*** roxanaghe has quit IRC10:30
*** dixiaoli has quit IRC10:31
*** jlanoux has joined #openstack-meeting10:32
*** weshay_xchat has joined #openstack-meeting10:33
*** jlanoux_ has joined #openstack-meeting10:37
*** e0ne has joined #openstack-meeting10:37
*** otter768 has joined #openstack-meeting10:38
*** jlanoux has quit IRC10:39
*** eduardo___ has joined #openstack-meeting10:41
*** scheuran has joined #openstack-meeting10:41
*** aranjan has joined #openstack-meeting10:41
*** xingchao has quit IRC10:42
*** otter768 has quit IRC10:42
*** alexpilotti has joined #openstack-meeting10:43
*** dilip has quit IRC10:43
*** dilip has joined #openstack-meeting10:43
*** aranjan has quit IRC10:46
*** GheRivero has quit IRC10:47
*** GheRivero has joined #openstack-meeting10:47
*** timrc has quit IRC10:47
*** hughhalf has quit IRC10:47
*** ricolin has quit IRC10:47
*** mdavidson has joined #openstack-meeting10:48
*** toscalix has quit IRC10:48
*** dilip has quit IRC10:48
*** dilip has joined #openstack-meeting10:48
*** safchain has quit IRC10:48
*** shashank_hegde has quit IRC10:48
*** hughhalf has joined #openstack-meeting10:48
*** toscalix has joined #openstack-meeting10:48
*** safchain has joined #openstack-meeting10:49
*** timrc has joined #openstack-meeting10:49
*** ihrachys has joined #openstack-meeting10:49
*** spzala has joined #openstack-meeting10:50
*** egallen_ has joined #openstack-meeting10:51
*** e0ne has quit IRC10:51
*** egallen has quit IRC10:52
*** egallen_ is now known as egallen10:52
*** spzala has quit IRC10:55
*** egallen has quit IRC10:57
*** mbound_ has quit IRC10:58
*** sankarshan is now known as sankarshan_away10:59
*** sputnik13 has joined #openstack-meeting11:00
*** mbound_ has joined #openstack-meeting11:03
*** marekd has joined #openstack-meeting11:04
*** ihrachys has quit IRC11:06
*** egallen has joined #openstack-meeting11:07
*** Ramanjaneya has quit IRC11:07
*** zeih has quit IRC11:07
*** vikram_ has quit IRC11:07
*** sputnik13 has quit IRC11:07
*** nadya_ has quit IRC11:11
*** yamahata has quit IRC11:12
*** thorst has joined #openstack-meeting11:13
*** dguitarbite has quit IRC11:14
*** emagana has joined #openstack-meeting11:14
*** nadya_ has joined #openstack-meeting11:15
*** claudiub has joined #openstack-meeting11:16
*** JRobinson__ has joined #openstack-meeting11:17
*** electrofelix has joined #openstack-meeting11:18
aburmashevgreat, zuul is now working through proxy for me :)11:18
*** thorst has quit IRC11:18
*** emagana has quit IRC11:19
*** dmowrer has joined #openstack-meeting11:19
*** yamamoto has quit IRC11:20
*** korzen has quit IRC11:21
*** dmowrer has quit IRC11:24
*** dilip has quit IRC11:26
*** roxanaghe has joined #openstack-meeting11:26
*** tochi has quit IRC11:27
*** Ramanjaneya has joined #openstack-meeting11:27
*** dzamboni has joined #openstack-meeting11:30
*** flaper87 has quit IRC11:30
*** flaper87 has joined #openstack-meeting11:30
*** roxanaghe has quit IRC11:30
*** aysyd has joined #openstack-meeting11:31
*** jlanoux_ has quit IRC11:31
*** jlanoux has joined #openstack-meeting11:31
*** asselin has quit IRC11:34
*** asselin has joined #openstack-meeting11:35
*** aysyd has quit IRC11:36
*** rhagarty has quit IRC11:37
*** mwagner_lap has quit IRC11:39
*** ankurgupta has quit IRC11:39
*** flaper87 has quit IRC11:39
*** jckasper has quit IRC11:39
*** n0ano has quit IRC11:39
*** rhagarty has joined #openstack-meeting11:40
*** jlanoux has quit IRC11:40
*** adahms has joined #openstack-meeting11:41
*** aranjan has joined #openstack-meeting11:42
*** mdbooth has joined #openstack-meeting11:42
*** ankurgupta has joined #openstack-meeting11:44
*** flaper87 has joined #openstack-meeting11:47
*** flaper87 has quit IRC11:47
*** flaper87 has joined #openstack-meeting11:47
*** changzhi has quit IRC11:48
*** jckasper has joined #openstack-meeting11:48
*** mdbooth has quit IRC11:48
*** houming has joined #openstack-meeting11:49
*** mdbooth has joined #openstack-meeting11:49
*** aysyd has joined #openstack-meeting11:49
*** egallen has quit IRC11:50
*** jdurgin has quit IRC11:53
*** jdurgin has joined #openstack-meeting11:54
*** erlon has joined #openstack-meeting11:56
*** lazy_prince has joined #openstack-meeting11:57
*** gmann_ has joined #openstack-meeting11:57
*** ihrachys has joined #openstack-meeting11:57
*** PaulMurray has joined #openstack-meeting11:58
*** ddeja has quit IRC11:59
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Dec  1 12:00:05 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
*** andrearosa has joined #openstack-meeting12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho's here today?12:00
alex_xuhello everyone!12:00
alex_xulet's wait on more minutes for more people join in12:01
*** sudipto has quit IRC12:01
alex_xuok, let's start the meeting12:02
alex_xu#topic actions from last meeting12:02
*** openstack changes topic to "actions from last meeting (Meeting topic: nova api)"12:02
alex_xusdague ask docs team about approval rights by api subteam on our wadl12:02
*** rtheis has joined #openstack-meeting12:02
alex_xusdague: do you have update for this ^ this is action before US holiday12:02
*** MaxPC has joined #openstack-meeting12:02
sdagueI did talk with annegentle about that, and she was going to ponder, I don't think we had real resolution on it12:03
sdagueI'll follow up again this week12:03
alex_xusdague: ok, thanks a lot12:03
alex_xuok, only on action, let's move on12:03
alex_xu#topic content patches up for review12:03
*** openstack changes topic to "content patches up for review (Meeting topic: nova api)"12:03
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/complete-todo-in-api-concept-doc,n,z12:03
alex_xulast week, we have topic for admin concepts12:04
*** MaxPC has quit IRC12:04
alex_xuthanks jichen and edleafe help on that :)12:04
alex_xu#link https://review.openstack.org/#/c/24994312:04
*** yamamoto has joined #openstack-meeting12:04
alex_xuthis is for host. This is pretty good from me, although there is some discussion about deprecated host maintenance. As service and host have some overlap, that confuse user. But we can improve the doc next step.12:04
alex_xu#link https://review.openstack.org/24845412:04
alex_xuthe service one was wrote by me, but I think it just need more feedback12:05
alex_xu#link https://review.openstack.org/25073712:05
alex_xuthe last one is aggregate, hypervisor and migration.12:05
alex_xuPretty good we have devref about aggregate, but I'm a little concern that is for developer, not api user.12:05
sdagueyeh, I can write something on the agregates front12:06
*** jckasper has quit IRC12:06
*** yfried_ has quit IRC12:06
*** yfried has joined #openstack-meeting12:06
*** clayton has quit IRC12:06
alex_xusdague: thanks :)12:06
sdaguenice job so far, I'll do some reviews here later today12:07
alex_xuThe one we said want to be an example for api-ref already merged12:07
gmann_alex_xu: sdague its worth to use devref one as ref also12:07
alex_xu#link https://review.openstack.org/#/c/248534/12:07
alex_xugmann_: yea, agree, keep the ref is good also12:08
sdaguegmann_: sure, but this is a concept guide. Footnotes are fine to learn more, but this has to have the high level concepts in here12:08
alex_xufor the api-ref one, I'm afraid people didn't get chance take a look at. But please feel free submit patch to correct it12:08
*** achanda has joined #openstack-meeting12:09
* johnthetubaguy is happy to see so many patches up for those API docs now12:09
gmann_sdague: yea, i was thinking high level concept + ref for more details which we already have12:09
alex_xuif no more question for those patches, let's move on12:10
johnthetubaguyas a heads up, I did attempt to get our new guide linked from the complete reference: http://developer.openstack.org/api-ref-compute-v2.1.html12:11
*** dmowrer has joined #openstack-meeting12:11
*** kaisers has quit IRC12:11
johnthetubaguyI suspect we can do better, but its a start12:11
alex_xujohnthetubaguy: thanks :)12:11
alex_xuI'm just a little worry about most of wadl patch didn't get chance for our guys' review12:12
sdaguehonestly, we can fix it later if it's an issue12:13
alex_xuor we can just continue with patch to improve it if we find problem12:13
alex_xusdague: yea, that also works12:13
*** jckasper has joined #openstack-meeting12:13
alex_xuanyway, let's move on12:13
*** clayton has joined #openstack-meeting12:13
alex_xu#topic most needed next content patches12:13
*** openstack changes topic to "most needed next content patches (Meeting topic: nova api)"12:13
alex_xuWe have good servers action, good user and admin concepts.12:13
alex_xuI checked the doc, for servers, we can something more for scheduler-hints, bdm, servers query, consoles.12:14
alex_xuwe also can put more stuff about extension and microversions, version.12:15
alex_xuwhat is people prefered topic for next?12:15
alex_xus/we can something more/we can add something more/12:15
paul-carlton1can we talk about https://review.openstack.org/22882812:16
sdagueI'm going to have to go stare at this later. I haven't had my coffee yet today, so still a little slow on it12:16
alex_xuand next week is our virtual doc sprint12:16
gmann_alex_xu: yea12:16
alex_xupaul-carlton1: sorry, I put that in next topic12:16
*** thorst has joined #openstack-meeting12:16
gmann_alex_xu: for microversion we will add here right?  http://developer.openstack.org/api-guide/compute/microversions.html12:16
gmann_or any other preferred structure?12:17
*** aranjan has quit IRC12:17
*** jlanoux has joined #openstack-meeting12:17
johnthetubaguygmann_: I intended that to talk about how microversions work, not to document them all12:17
*** salv-orlando has quit IRC12:18
gmann_johnthetubaguy: yea, as all description we have in https://github.com/openstack/nova/blob/master/nova/api/openstack/rest_api_version_history.rst12:18
alex_xugmann_: that is for developer, need to check it first. the concept for normal api user12:18
gmann_johnthetubaguy: mainly the usage part12:18
johnthetubaguyright, just the usage bit really12:18
johnthetubaguyand contrasting that with extensions for older versions of the aPI12:18
gmann_alex_xu: with ref of that may be12:18
johnthetubaguyI think covering the use cases sdague had in his blog are a good idea12:19
gmann_johnthetubaguy: yea12:19
alex_xujohnthetubaguy: +112:19
johnthetubaguylike these are the ways we expect people to use our API, etc12:19
*** Akis_ has joined #openstack-meeting12:19
*** Daisy has joined #openstack-meeting12:20
alex_xuok, for this week, people can just focus on review, and free to pick other task.12:21
alex_xusdague: maybe we should check the existed doc to list some points need to improvement, then we can leave those for next virtual doc sprint12:21
sdaguealex_xu: yeh, that sounds reasonable12:21
*** raildo-afk is now known as raildo12:21
*** akiskourtis has quit IRC12:22
alex_xuok, I will help on go through the doc again, to find something worth improvement12:22
*** obondarev_afk has joined #openstack-meeting12:22
*** jaypipes has joined #openstack-meeting12:22
alex_xuso if you find something, you can submit a patch add some todo note12:22
alex_xuok, if no more question, let's move on12:23
alex_xu#topic API futures - specs12:23
*** openstack changes topic to "API futures - specs (Meeting topic: nova api)"12:23
alex_xu#link https://review.openstack.org/22882812:23
alex_xupaul-carlton1: your turn12:24
*** thorst has quit IRC12:24
paul-carlton1sdague, proposed an approach which I have updated the spec to accommodate12:24
*** skraynev has quit IRC12:24
sdagueright, so I think we're all agreed that we need the functionality proposed in the spec. There seems to be disagreements on how we surface that to the user.12:25
*** e0ne has joined #openstack-meeting12:25
paul-carlton1but others did not want this and another spec  has already been approved using instance action approach instead12:25
* edleafe wanders in half-awake12:25
*** obondarev has quit IRC12:25
paul-carlton1#link https://review.openstack.org/#/c/22904012:25
alex_xuthe only point I have is migration resource is for all the migration. the delete also can means we cancel resize, evacaute?12:25
paul-carlton1I'm happy with either approach but we should be consistent?12:25
johnthetubaguysdague: +1 that12:26
*** kaisers has joined #openstack-meeting12:26
*** skraynev has joined #openstack-meeting12:26
paul-carlton1so delete on a migration stops it, in some cases the driver cannot do this so we get a not supported outcome in instance actions for the deletion of migrtion12:26
johnthetubaguyis this a new migration resource, or the existing one?12:27
*** roxanaghe has joined #openstack-meeting12:27
*** gmann__ has joined #openstack-meeting12:27
sdaguejohnthetubaguy: it's the sub resource of servers12:27
*** pm90_ has joined #openstack-meeting12:27
paul-carlton1it is an existing resource12:27
sdaguethe approachI suggested12:27
*** gmann_ has quit IRC12:28
johnthetubaguywe don't currently have a sub resource of services that lists migrations though, just wanted to be clear on that12:28
paul-carlton1GET /servers/{id}/migration returns the id of a migration object12:28
sdaguejohnthetubaguy: right, it's a new resource12:28
johnthetubaguyyep, thats cool, just wanted to make sure we were talking about the same thing12:29
*** claudiub has quit IRC12:29
*** yanyanhu has joined #openstack-meeting12:30
johnthetubaguyso my gut tells me, follow the old pattern, and eventually we replace all actions with a more async task focused API, with common patterns12:30
*** achanda has quit IRC12:31
johnthetubaguybut having said all that, maybe this is a good first attempt at the "new" pattern, so we should probably just try it, and see if it works12:31
sdaguedo I'm actually confused on what - https://review.openstack.org/#/c/229040/14/specs/mitaka/approved/pause-vm-during-live-migration.rst,cm really is12:31
sdaguewhich is the other one that got approved12:31
*** claudiub has joined #openstack-meeting12:31
johnthetubaguyjust to be clear, migrations will list: migrate calls, live-migrate calls, and resizes?12:31
*** roxanaghe has quit IRC12:32
alex_xuyea, GET /servers/{id}/migration just for in-progress live-migration sounds like strange12:32
gmann__yea list migrations list all type of migration for all the instances.12:32
PaulMurraysdague, that one became the action live-migrate-force-end12:32
johnthetubaguysdague: its the force live-migrate to complete by pausing the VM, rather than cancelling the live-migrate12:32
johnthetubaguyyeah, thats what it was called12:32
PaulMurraysdague, it pauses a VM so it completes the migration quickly12:32
PaulMurraysdague, but resumes it on completion12:32
sdaguelive-migrate-force-end is massively confusing set of words12:32
sdaguehow did that ever get approved12:32
johnthetubaguywe totally need to have them both consistent, whatever we pick12:33
johnthetubaguysdague: it seemed less confusing that all the suggestions before it12:33
PaulMurraysdague, the change of name was to indicate it should not be viewed as a pause12:33
paul-carlton1so following the approach recommended by sdague  that would be a POST on /server/{id}/migration/{id}12:33
PaulMurraysdague, it is an algorithm to speed up the migration that impacts the user12:33
PaulMurraysdague, another that does not cause a pause could be introduced12:34
sdagueyeh, ok, I feel like that name is evacuate all over again12:34
PaulMurraysdague, another algorithm that is12:34
paul-carlton1The name is misleading, we are thinking of it as an action on a migration to expedite it12:34
sdaguewe're going to be explaining what that is, forever12:34
*** e0ne has quit IRC12:34
PaulMurraysdague, feel free to come up with a better one :)12:34
*** mbound_ has quit IRC12:35
PaulMurraysdague, its not set in stone just yet12:35
sdagueok, well it got approved12:35
PaulMurraysdague, do we need that one and the cancel to be consistent12:35
PaulMurrayin use of migrations or actions12:35
sdagueI feel like they should be consistent12:36
*** kaisers has quit IRC12:36
PaulMurrayme too12:36
johnthetubaguysdague: totally agreed they should be consistent12:36
PaulMurrayso we are looking at deciding how both should look12:36
PaulMurrayin the api12:36
johnthetubaguysdague: I would -2 any code review where they are not consistent, regardless of the spec12:36
sdaguejohnthetubaguy: ok, well, maybe the problem is this is all ending up very soda straw12:37
*** yfried_ has joined #openstack-meeting12:37
*** e0ne_ has joined #openstack-meeting12:37
sdaguethere should have been a single spec with all the live migration API changes so they look whole12:37
PaulMurraysdague, we can still consider doing an update to the first spec - lets do the right thing here12:37
PaulMurraysdague, I would rather get the migrations vs actions sorted and then make them consistent12:38
sdagueok, so the resource model for cancel seems to me to be really natural REST12:38
sdaguebecause it's litterally DELETE that thing12:38
*** achanda has joined #openstack-meeting12:38
*** otter768 has joined #openstack-meeting12:38
sdagueand whenever that is so natural, we should use it, or just give up and redo our interface as soap12:39
sdaguePOST /server/{id}/migration/{id} - action {"complete-now"}12:40
*** zhipeng has joined #openstack-meeting12:40
alex_xuwhy that is POST?12:40
sdague"Do whatever is needed to most quickly complete the migration, this may mean turning off the live VM earlier than it would otherwise"12:40
paul-carlton1some seem to want migrations and it to return a list?12:40
*** yfried has quit IRC12:41
*** ogelbukh1 is now known as ogelbukh12:41
sdaguealex_xu: yeh, maybe it's a put with some attributes, I don't know. It does fee like we should hang it off migration subresource12:41
sdaguepaul-carlton1: well, conceptually, all our resources have been collections12:41
paul-carlton1in this case, yes but in the future we may add other POST operations on the /server.. migration to tweak it in other ways12:42
sdaguethis is the first time one would not be12:42
paul-carlton1I'll update the cancel spec accordingly and deal with Michalik comment too then we should be good to go!12:42
sdaguejohnthetubaguy: are you ok with this?12:43
*** sbelous_ has joined #openstack-meeting12:43
pkoniszewskibut why do we need to provide migration ID in API call? there can only be one on-going migration for particular VM12:43
*** otter768 has quit IRC12:43
alex_xudo we want to implement cancel cold migration/evacuate in the future?12:43
paul-carlton1we may do12:43
sdaguealex_xu: possibly12:44
sdaguepkoniszewski: because it's consistent, and that has an id12:44
johnthetubaguysdague: yes, using this as a first attempt of making our actions more REST like and task-ey, it makes sense I think12:44
alex_xusdague: ok, if we want to that, we can keep the sub-resource of servers12:44
gmann__alex_xu: sdague can we have something like redo action for any migration of server, like live as of noe and evacuate, cold-migration later12:44
sdagueand because if that id is returned some other time, and you follow it back, you want to make sure you are interacting witht he same migration as before12:44
*** JRobinson__ has quit IRC12:45
gmann__may be REDO for any action on server ?12:45
sdagueok, so who has the pen to write up how all of these become consistent ?12:46
alex_xuemm....that another huge work12:46
sdaguepaul-carlton1: is going to update his spec12:46
sdaguehowever there is the already approved spec12:46
gmann__and keep implementing for actions as per need.12:46
pkoniszewskii can update my spec (force-end) basing on paul-carlton1 update12:46
PaulMurraypkoniszewski, wrote the first spec12:46
PaulMurraycool pkoniszewski - thanks12:47
johnthetubaguysdague: +1 for the action being on the {id}, anything else would be fighting way too many conventions12:47
*** sileht has joined #openstack-meeting12:47
sdaguepkoniszewski: ok12:47
pkoniszewskiyes, race condition sounds like a good reason to operate on id12:47
*** dguitarbite has joined #openstack-meeting12:47
PaulMurraymaybe we should stick an agreement in the minutes?12:48
alex_xuyea, the time is tight12:48
pkoniszewskiwould be good to have this written down somewhere12:48
sdaguepkoniszewski: also, given that it's a separate actions namespace, how about "force-complete"12:48
sdagueend sounds too much like cancel12:48
sdaguethat is going to confuse people a lot12:49
pkoniszewskisdague: as far as I remember johnthetubaguy had some concerns with "force-complete"12:49
sdaguejohnthetubaguy: what are those concerns?12:49
pkoniszewskidon't remember exactly what the point was12:49
*** jaypipes has quit IRC12:49
sdaguewe're going to regret the word "end" for years here12:49
pkoniszewskipersonally I prefer "force-complete"12:49
*** Daisy has quit IRC12:49
*** zeih has joined #openstack-meeting12:50
alex_xu+1 from me, sounds good12:50
johnthetubaguysdague: it wasn't from me the concern, it should be in the gerrit review, I think it was something about the errors12:50
*** kaisers has joined #openstack-meeting12:50
johnthetubaguysdague: I prefer complete12:50
alex_xuok, do we have all the deal at here, we need move on, as we have next topic12:51
PaulMurrayI think it was that it might not complete, so coming to some kind of end ?12:51
PaulMurrayeither complete or give up12:51
*** akamyshnikova has joined #openstack-meeting12:51
*** sbelous_ has left #openstack-meeting12:51
sdagueend means stop12:51
edleafeI think 'complete' by itself implies that it won't finish otherwise12:51
*** egallen has joined #openstack-meeting12:51
PaulMurraynot in a 100m race12:51
paul-carlton1what abut something like modify, so we can use it to do various actions relating to the migration but we can discuss this in migration sub team meeting later?12:51
edleafe'force-complete' seems clear12:51
johnthetubaguyI am happy with force-complete, I would need to read through the gerrit comments to work out the previous issue12:52
sdaguePaulMurray: I think that the dialect differences is how we ended up with evacuate, and we've spent more time explaining misconceptions on that, then took to write the feature12:52
PaulMurrayjohnthetubaguy, +!12:52
*** Qiming has joined #openstack-meeting12:52
PaulMurray+1 even12:52
sdagueI'm so going to +! from now on :)12:52
gmann__or force_finish otherwise force_complete looks good12:53
pkoniszewskithe decision has been made there to use "force-end" instead of "force-complete" - https://review.openstack.org/#/c/229040/13/specs/mitaka/approved/pause-vm-during-live-migration.rst12:53
*** 32NAACGR7 has joined #openstack-meeting12:53
sdaguefinish also means stop12:53
edleafe+! == 'force-approve'12:53
sdaguethese words need to not mean stop, otherwise people with think this is cancel12:53
johnthetubaguyI think it was andrearosa who didn't like complete12:53
edleafesd +!12:53
johnthetubaguytrying to remember why now12:53
edleafesdague: +!12:53
* edleafe needs coffee!12:54
PaulMurrayI think alex_xu said lets move on12:54
alex_xuyea, 5 mins left12:54
paul-carlton1if you use modify the body can contain a pause to pause the instance12:54
johnthetubaguyso I think it was "we can't guarantee that the live migration finish"12:54
pkoniszewskiyes, we should move on, let's discuss it later on LM subteam meeting12:54
sdagueyeh, honestly, this was probably the most important thing to get nailed down12:54
johnthetubaguybut I think we should ignore that12:54
*** jaypipes has joined #openstack-meeting12:54
sdaguejohnthetubaguy: yeh, we should ignore that12:54
sdaguewe don't guaruntee anything in the api12:54
alex_xuanother thing is about oslo-policy. which we mention in the irc last week, and suggestion add to meeting agenda12:54
johnthetubaguysdague: right, error happen, worry about the intent12:55
*** baoli has joined #openstack-meeting12:55
sdaguejohnthetubaguy: right12:55
alex_xusdague: do you know what's going on for the discussion about oslo-policy in nove?12:55
sdaguealex_xu: nothing at this point12:55
*** dprince has joined #openstack-meeting12:56
alex_xuso we keep use the old policy.py?12:56
sdagueis there something more specific that you are asking about?12:56
johnthetubaguythis is more about, should we move to oslo.polcy, and what is stopping us12:56
alex_xu#link https://review.openstack.org/#/c/198065/12:56
sdaguethere were some grand discussions at summit, but nothing concrete has emerged as far as I know12:56
alex_xu^ and I saw this patch12:56
*** klkumar has quit IRC12:57
sdagueyeh, so, that's probably fine. I was hoping we'd get policy in code before doing that12:57
sdaguebut that doesn't seem high on anyone's radar12:57
*** akuznetsov has joined #openstack-meeting12:57
johnthetubaguywell, we dropped it for docs right?12:57
alex_xuyea, I remember those discussion12:58
sdaguewe dropped it for not being able to get enough people to understand why it was important12:58
sdaguethere was dramatic pushback from some quarters12:58
johnthetubaguysdague: true, thats more accurate12:58
*** MaxPC has joined #openstack-meeting12:58
sdagueso, that's fine, it's dropped, might as well synchronize here12:59
*** lixinhui has joined #openstack-meeting12:59
* johnthetubaguy cries a little inside12:59
dimssdague : "I'm happy to write specs here" :) http://markmail.org/message/objf6ht572b5fnza12:59
alex_xuok, it's time to close13:00
*** fawadkhaliq has quit IRC13:00
alex_xulet's move to openstack-nova13:00
sdaguedims: yeh, then the whole thread was - "we hate this"13:00
dimsack sdague13:00
*** andrearosa has left #openstack-meeting13:00
sdagueso it didn't seem a good use of time13:00
alex_xuthanks all, sorry have to end the meeting13:00
*** egallen has quit IRC13:00
sdagueyep, thanks alex_xu13:00
gmann__Thanks all13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Tue Dec  1 13:00:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-12-01-12.00.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-12-01-12.00.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-12-01-12.00.log.html13:00
edleafethanks alex_xu!13:01
alex_xusdague: edleafe np13:01
Qiming#startmeeting senlin13:01
openstackMeeting started Tue Dec  1 13:01:23 2015 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
*** julim has quit IRC13:01
*** achanda has quit IRC13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: senlin)"13:01
openstackThe meeting name has been set to 'senlin'13:01
*** elynn has joined #openstack-meeting13:01
*** mwagner_lap has joined #openstack-meeting13:01
*** fawadkhaliq has joined #openstack-meeting13:01
Qimingplease check the agenda and see if you have got things to add13:02
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:02
*** weshay_xchat has quit IRC13:02
*** gmann__ has quit IRC13:02
*** fawadkhaliq has quit IRC13:02
Qiming#topic mitaka work items13:02
*** openstack changes topic to "mitaka work items (Meeting topic: senlin)"13:02
*** baoli has quit IRC13:02
Qiminglet's start with the etherpad, :)13:02
Qimingas always13:02
*** weshay_xchat has joined #openstack-meeting13:02
Qiming#link https://etherpad.openstack.org/p/senlin-mitaka-workitems13:02
Qimingheat resource types13:03
*** jckasper has quit IRC13:03
*** zhipeng_ has joined #openstack-meeting13:03
*** fawadkhaliq has joined #openstack-meeting13:03
*** fawadkhaliq has quit IRC13:03
*** haiwei has joined #openstack-meeting13:03
Qimingelynn, yours13:03
*** baoli has joined #openstack-meeting13:04
elynnI just update one patch for it and unittests are passed.13:04
QimingI think the patches were blocked somehow by the bugs introduced into senlinclient13:04
*** fawadkhaliq has joined #openstack-meeting13:04
elynnI will continue to update other patches ASAP.13:04
*** jruano has joined #openstack-meeting13:04
Qimingwe will be doing more code churn to the client code as we are revising the apis13:05
elynnWill it affact senlin  resources?13:05
Qimingelynn, I believe there will be some impact13:05
*** zhipeng has quit IRC13:05
Qimingfor example, when you do a cluster-create, we plan to return a 202 (request accepted)13:06
Qimingin that response body, I'm not sure whether we should include a representation of the cluster13:06
*** achanda has joined #openstack-meeting13:06
elynnDoes it return 202 now?13:07
QimingI have checked HTTP spec and api-wg, so far no guidance there13:07
Qimingcurrently not13:07
*** haiwei_ has joined #openstack-meeting13:07
Qimingbut in theory, we should return 202, because the cluster creation may take a long time13:07
Qimingit is simply wrong to return 200, i.e. to pretend the cluster has been created13:08
haiwei_what is the topic now, sorry, missed a lot13:08
Qiminghaiwei_, heat resource type support13:08
elynnWill it return at least a cluster id?13:08
jruanohmmm... i don't think a representation of the cluster is necessary on a 20213:08
*** bzhao0825 has joined #openstack-meeting13:09
Qimingin an 202 response, we will add a 'Location' header, where you can get a link to the cluster resource being created13:09
QimingI'm still not sure if we should teach SDK to parse the response header and then do a GET again13:10
elynnok, I will slow down, after you finish revise APIs, I need do more tests.13:10
*** haiwei has quit IRC13:10
haiwei_it seems the 'Location' header is the http response header13:10
haiwei_I confirmed it with the api-wg guys13:11
elynnAll the resource creation will return 202 only? like profile13:11
Qimingyes, most http related packages used today allow you to check the header and behave accordingly13:11
*** egallen has joined #openstack-meeting13:11
Qimingno, elynn, profile-create will return a 20113:11
Qimingthat creation is for real13:11
Qimingthis is the revision, a first step13:12
elynnIf SDK don't continue to parse the response header, it might be difficult to handle in heat13:12
Qimingthat is a big concern13:12
QimingI'd propose something into SDK so that the heat side code doesn't have to look a lot different13:13
elynnIf I remember correctly , instance creation only returns 202.13:13
*** aranjan has joined #openstack-meeting13:13
*** salv-orlando has joined #openstack-meeting13:13
Qimingelynn, if that is true, we can check how heat gets instance id today13:13
*** sbelous_ has joined #openstack-meeting13:13
*** 32NAACGR7 is now known as thorst13:14
Qimingif necessary, we may have to cap the senlinclient version13:14
*** weshay_xchat is now known as weshay13:14
Qimingcurrent version 0.1.8 looks good?13:14
*** mbound_ has joined #openstack-meeting13:14
elynnhaven't test it yet.13:15
Qimingelynn, that code is not telling you the real things happened behind the scene13:15
Qimingmay need to check novaclient code13:15
*** pm90_ has quit IRC13:15
elynnQiming: yes, I think novaclient handles the location.13:15
Qimingokay, if that is the case ...13:16
Qimingwe may need to check with SDK team to come up with a workaround13:16
Qimingpersonally, I hate all xyzclient packages13:16
*** sudipto has joined #openstack-meeting13:16
Qimingmoving on13:17
Qimingsenlinclient, one of the things I hate, :)13:17
Qiminghaiwei_ just proposed test case part 213:17
*** persia has joined #openstack-meeting13:18
Qimingplease help13:18
haiwei_yes, jenkins failed13:18
*** yfried_ is now known as yfried13:18
haiwei_will check it later13:18
*** egallen has quit IRC13:18
*** fawadkhaliq has quit IRC13:18
QimingAPI response modification13:18
*** fawadkhaliq has joined #openstack-meeting13:19
Qimingpatch #251771 is a global revision13:19
patchbotQiming: https://review.openstack.org/#/c/251771/ - Fix status code returned from API13:19
Qimingneed eyes on them too13:19
*** egallen has joined #openstack-meeting13:19
Qiming404 vs 400 return code, I think we are done with it13:19
Qiminghealth policy13:20
jruanoi will have a look today13:20
QimingI believe lixinhui is looking into that as well13:20
Qimingthx, jruano13:21
Qimingwe at least need a bp for this13:21
*** gcb has joined #openstack-meeting13:21
elynnWhat will health policy do exactly?13:21
QimingTriggers are history now13:22
jruanoah... yep, i figured that was coming13:22
*** stevemar has quit IRC13:22
jruanolooking at monasca, and thats what it felt like13:22
yanyanhuelynn, I think that's what we need to discuss in BP :)13:22
Qiminghealth policy is basically a Senlin inherent mechanism to detect node status and take proper actions to fix node failures if told so13:23
*** stevemar_znc has joined #openstack-meeting13:23
Qimingyanyanhu, agreed13:23
elynnoh, I C.13:23
*** kylek3h has joined #openstack-meeting13:23
yanyanhuah, my job13:24
yanyanhuI spent some times on completing related support in sdk side13:24
yanyanhucurrently, server rebuild and server resize related function calls has been added13:24
haiwei_is there a bp for profile?13:24
Qimingboth merged?13:25
*** dguitarbite has quit IRC13:25
yanyanhuso it can meet the requirement of supporting property update of flavor and some basic properties of os.nova.server prfile I think13:25
Qimingupdate of flavor is working too?13:26
yanyanhuand network and image propety update support has been done in senlin13:26
yanyanhuI'm still working on it13:26
yanyanhubut related support in sdk has been there13:27
Qimingokay, network and image update are not on the etherpad, so I guess they are all solved13:27
yanyanhuyea, I removed them :)13:27
Qimingcool, you may want to paste the patch link into etherpad13:27
yanyanhusure, will add it13:27
Qimingjruano, we need a bp on this13:27
jruanoim working on the bluprint for receiver13:27
jruanoi was out last week. i have a design that im working on now13:28
Qimingokay, be it a webhook or a message queue, the parameters are almost the same I think13:28
Qimingjruano, happy thanksgiving holidays, to you and your family, :)13:29
jruanoyes. i am going to lay out a class hierarchy that abstracts webhook13:29
yanyanhuyea, happy thanksgiving :)13:29
jruanothen we can extend additional implementations from that as needed13:29
Qimingjruano, it doesn't have to be a complex class hierarchy I think13:29
jruanoyep, i think it is pretty simple13:29
Qimingwe just need a generalized interface that will be accommodating to future extensions13:29
jruanowebhook has probably everything there13:30
*** klkumar has joined #openstack-meeting13:30
jruanoworking on that today13:30
Qiminglock breaker13:30
elynnThe patches are merged.13:30
Qimingall of them?13:30
yanyanhuyes, this afternoon.13:30
elynnIs it better to add functional test for it?13:31
Qiminggreat, that means some bugs on launchpad can be labeled 'invalid' now?13:31
yanyanhuelynn, that will be great13:31
Qimingelynn, good idea13:31
elynnI will start to work on them ;)13:31
yanyanhuBTW, there still some failures in current functional test. I will spend some time on it in coming week13:31
yanyanhuto ensure you have a clean basement for new test cases13:32
elynnWill we enable them by default?13:32
yanyanhuelynn, hmm, maybe not now I think13:32
yanyanhubut we do recommand check it manually before merge new patches13:33
yanyanhurecommend, sorry13:33
elynnThe command is check experiment?13:33
Qimingyep, haiwei_ is still seeing some weird errors from keystoneauth113:33
yanyanhucheck experimental13:33
elynncool, got it.13:33
*** sdake has joined #openstack-meeting13:34
yanyanhuQiming, great, the recent change about authentication caused some trouble :)13:34
Qiminganything else about items on etherpad?13:34
haiwei_Qiming, the error I said this afternoon is my own fault, sorry13:34
Qiminghaiwei_, so happy you made mistakes13:34
QimingI mean it is not the code's problem, :)13:35
haiwei_I often made it13:35
Qimingmoving on13:35
Qiminghaiwei_, keep on good habits then13:35
Qiming#topic bug clearance13:35
*** openstack changes topic to "bug clearance (Meeting topic: senlin)"13:35
Qiming#link https://bugs.launchpad.net/senlin/?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&fiel13:36
haiwei_btw, does anyone notice that when creating/deleting a node TIMEOUT error will happen first and then creation/deletion will still succeed13:36
Qiminghaiwei_, I didn't13:36
yanyanhume neither...13:36
Qimingsuch a long url13:36
*** tej has joined #openstack-meeting13:37
Qiminganyway, we still have 1 critical bug, 3 medium (1 in progress), all others are to be revisited13:37
haiwei_ok, if you meet that error just share to us, maybe something wrong there13:37
*** aranjan has quit IRC13:37
Qimingin total we have 19 bugs, including 3 already marked 'incomplete'13:37
yanyanhuless than 20 bugs are in open status13:38
Qimingseems we need bugs13:38
jruanomine should have a patch checked in today. i was almost done with it heading into last week13:38
*** zhipeng_ has quit IRC13:38
Qimingjruano, no worry13:38
Qimingwe will need more bugs13:38
*** mrmartin has quit IRC13:39
Qimingelynn, test and find bugs, certainly13:39
*** gongysh has joined #openstack-meeting13:39
elynnHa~ Or we can buy some from store ;)13:39
Qiming#action Qiming to go through the bug list and triage/confirm bugs13:40
*** yamamoto has quit IRC13:40
haiwei_the critical one is not one bug I think, it should be many  bugs, but most are fixed now13:40
yanyanhuelynn, :P13:40
*** dasm has joined #openstack-meeting13:40
Qiminghaiwei_, the problem is we were not linking back those patches to the bug13:40
Qimingmoving on13:41
Qiming#topic Mitaka release schedule13:41
*** openstack changes topic to "Mitaka release schedule (Meeting topic: senlin)"13:41
elynnSeems patch will not automatically link to bug.13:41
haiwei_yes, it'S better not report this kind of bugs13:41
Qiming#link https://wiki.openstack.org/wiki/Mitaka_Release_Schedule13:41
elynnEven I write bug number in commit message.13:41
Qimingmaybe you are aware of it, mitaka-1 release is happening now13:41
jruanoyou have to add the Close-bug in commit message13:41
*** emagana has joined #openstack-meeting13:41
*** sdake has quit IRC13:42
Qimingthis is week 'R-18' for the mitaka cycle13:42
QimingI don't think we are ready to do a release13:42
Qimingso far, in project config, senlin is tag as "release:independent"13:43
*** hoangcx has joined #openstack-meeting13:43
Qimingthat is buying us some time to catch up, but not for ever13:43
QimingI hope we can catch up soon13:43
Qimingonce the API is stable, we can start the formal release and apply for "release:whatever-official" tags13:44
yanyanhuI think maybe we can try to give the first release after API rework is done13:44
Qimingmaybe by mitaka-2, we can start practicing a formal release13:44
Qimingyes, it will be Jan 19-21, 201613:45
Qimingwe won't miss next milestone13:45
*** cbouch has joined #openstack-meeting13:45
Qimingmoving on13:45
*** munish has joined #openstack-meeting13:45
Qiming#topic recheck blueprints13:46
*** openstack changes topic to "recheck blueprints (Meeting topic: senlin)"13:46
*** emagana has quit IRC13:46
*** akuznetsov has quit IRC13:46
Qimingokay, we need some approvals to the bps13:46
Qimingsome are outdated13:47
Qimingem ... we need more cores13:47
yanyanhuyes. And set some of them to obsolete status13:47
Qimingcore team please keep your eyes on commits and reviews13:47
jruanoyep... the trigger one for monasca i have can be removed now13:48
Qimingwe need more people13:48
Qimingyep, jruano13:48
Qiming#action review blueprints and approve/obsolete them as needed13:49
*** markvoelker_ has joined #openstack-meeting13:49
Qiming#topic open discussions13:49
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:49
*** sdake has joined #openstack-meeting13:50
*** yamamoto has joined #openstack-meeting13:50
lixinhuican I leverage some functional tests13:50
lixinhuifor the scalability testing?13:50
yanyanhuoh, plz remeber to use reno to generate release note related info when proposing new patch which adds new feature13:50
haiwei_is there a guideline of how to use reno?13:51
*** maishsk has joined #openstack-meeting13:51
*** wuhg has quit IRC13:51
yanyanhulixinhui, sure. That will be great.13:51
elynnyanyanhu: Is there any example for how to use it?13:51
jruanoah... where can we get the info on that tool?13:51
Qimingyep, yanyanhu that is a good habit to develop among the team13:51
yanyanhuhaiwei_, there is a sample patch qiming propose to illustrate how to use it13:51
yanyanhulet me find it for you13:52
haiwei_i remembered it13:52
yanyanhuyea, this one13:52
*** sdake_ has joined #openstack-meeting13:53
jruanoah ok... looks pretty straightforward13:54
*** sdake has quit IRC13:54
*** annp has joined #openstack-meeting13:54
*** gsagie has joined #openstack-meeting13:54
yanyanhujruano, for first step, maybe just know how to use it to generate release note info with the patch :)13:54
Qimingit is spreading the last minute report writing work into daily jobs13:54
*** gsagie has left #openstack-meeting13:55
*** e0ne_ has quit IRC13:55
*** neeti_ has joined #openstack-meeting13:55
*** vikram has joined #openstack-meeting13:55
Qimingby the way, I'm studying how to publish our docs (user and developer) to the official site13:55
*** hichihara has joined #openstack-meeting13:55
*** e0ne has joined #openstack-meeting13:55
elynnGreat news13:55
Qimingall those docs are very verbose ... believe me13:56
haiwei_you are a robot  Qiming13:56
*** achanda_ has joined #openstack-meeting13:56
yanyanhuQiming, this is very very important :)13:56
*** gsagie has joined #openstack-meeting13:56
*** ankurgupta has left #openstack-meeting13:56
*** neeti has quit IRC13:57
*** yamamoto has quit IRC13:57
*** yamamoto has joined #openstack-meeting13:57
Qiminganything else?13:57
yanyanhunope from me13:58
jruanonot from me13:58
*** achanda has quit IRC13:59
*** kzaitsev_mb has quit IRC13:59
Qimingin case you want to take a look13:59
Qimingjust pasted the generated doc page13:59
*** pc_m has joined #openstack-meeting13:59
*** regXboi has joined #openstack-meeting13:59
jruanovery nice13:59
Qiminglet's get back to #senlin13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Tue Dec  1 13:59:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-12-01-13.01.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-12-01-13.01.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-12-01-13.01.log.html13:59
hoangcxHi all :-)14:00
sbelous_hi there14:00
* regXboi finds a chair in the back of the room and goes back to sleep14:00
*** dkranz has joined #openstack-meeting14:00
*** korzen has joined #openstack-meeting14:00
*** jlibosva has joined #openstack-meeting14:00
*** haiwei_ has quit IRC14:00
*** yanyanhu has quit IRC14:00
*** dkranz has quit IRC14:00
armax#startmeeting networking14:00
openstackMeeting started Tue Dec  1 14:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** dkranz has joined #openstack-meeting14:00
*** elynn has left #openstack-meeting14:00
ajomorning / afternoon / night ;)14:01
ihrachysobondarev_afk: using special psycho technics to connect to the channel?14:01
*** diltram has joined #openstack-meeting14:01
*** obondarev_afk is now known as obondarev14:01
ajoihrachys : obondarev  lol14:01
armaxhello folks14:01
obondarevihrachys: yep :-)14:01
dasmihrachys: worked :)14:01
*** Sam-I-Am has joined #openstack-meeting14:01
* regXboi marvels at armax's ability to function at this hour 14:01
* HenryG attends from a seat in the sky14:02
*** garyk1 has joined #openstack-meeting14:02
* armax wonders too14:02
garyk1is the neutron meeting now?14:02
armaxwelcome to this fine Neutron meeting14:02
* ajo hands over some coffee to armax, thanks for joining this soon btw ;)14:02
armaxtoday’s agenda:14:02
regXboiHenryG: morning - where exactly are you in the sky?14:02
armax#link https://wiki.openstack.org/wiki/Network/Meetings14:02
* Sam-I-Am has a bowl of coffee14:02
*** jschwarz has joined #openstack-meeting14:02
armaxlet’s dive in before I fall asleep on the keyboard14:02
armax#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
armax#link https://wiki.openstack.org/wiki/Network/Meetings#Announcements_.2F_Reminders14:03
garyk1neutronlbaas gate is borke14:03
* regXboi is already asleep in the back of the room, this is just an AI chat-bot :)14:03
*** wwriverrat has joined #openstack-meeting14:03
armaxgaryk: yay!14:03
armaxgaryk: is that because of pep8?14:03
armaxgaryk: right, ok14:03
garyk1i am trying to change import order (resolved pylint stuff). but that is just a deadend14:03
armaxgaryk: someone ought to fix it!14:03
armaxgaryk: best would be to pin astroid14:04
xgermansomeone ought to fix pep814:04
pc_mI've been doing work on the pep8 issue14:04
HenryGregXboi: 30,000 ft up :)14:04
dougwigi forgot how much i hate daylight savings.14:04
pc_mWorked with infra last night.14:04
armaxgaryk: that was caused by a release of both pylint and astroid14:04
Sam-I-Amdougwig: you mean standard time? its just earlier now.14:04
*** ayoung has joined #openstack-meeting14:05
armaxon Nov 2914:05
pc_marmax: new astroid (not pinned) incompatible with pylint 1.4.414:05
ihrachysI still don't get why we don't skip the check, but meh.14:05
*** tej has quit IRC14:05
garyk1its odd that it does not break any other repos.14:05
*** jckasper has joined #openstack-meeting14:05
pc_mit breaks vpn14:05
garyk1anyways, i have digressed14:05
armaxgaryk: that’s because their imports are not the same14:05
ihrachysgaryk: no one uses pylint? :D14:05
armaxgaryk: besides, Neutron is unaffected because we have constrained jobs in force14:05
ihrachysyay for constraints14:06
ihrachysarmax: but not for *aas14:06
pc_marmax: right14:06
* ihrachys has some patches for *aas, still WIP14:06
pc_marmax: looks like kilo/juno in neutron are affected.14:06
armaxihrachys: right, someone ought to switch14:06
armaxpc_m: yes, that’s true14:06
* ihrachys rolls his eyes around the room14:06
pc_marmax: I have patches out for neutron juno/kilo14:06
pc_mjuno failing. need to see if we drop that fix14:07
armaxpc_m: I’ll look14:07
pc_m#info http://lists.openstack.org/pipermail/openstack-dev/2015-December/080939.html14:07
pc_mCaptured some info on issue,14:07
armaxok, mestery you had something you wanted to share?14:07
mesteryarmax: I did?14:07
armaxthis week is Milestone week14:07
pc_mand some proposals for fix.14:07
mesteryAh yes14:08
armaxmestery: yes you did14:08
regXboimestery, do you have donuts?14:08
Sam-I-Ammmm donuts14:08
mesteryIf it's milestone related, we'll be proposing the patches to openstack/release to tag those today/tomorrow, but I guess we need to wait for lbaas to work again first :)14:08
ajoihrachys : that look for "someone" means we need sombody handling pinnings for stable branches?14:08
*** mbound_ has quit IRC14:08
garyk1chanuka and donuts are two weeks times. but miracales may always occur14:08
pc_majo: I've pinned for neutron14:09
armaxmestery: that, plus invite people to get familiar with the new release process :)14:09
ajopc_m , sorry, right I just finished reading your link14:09
mesteryarmax: Heh, yes.14:09
pc_majo: and pinning on VPN (kilo so far)14:09
regXboiis there a link to the new release process?14:09
mestery#info The new release process is we propose a patch to openstack/release, and the release team cuts the release14:09
mesteryIt's much more efficient this way14:09
armaxwhere they are supposed to add release notes for patches that are meant to deliver functionality that is worth release noting about14:09
mesteryWhy, in the releasenotes of course :)14:10
mesteryNow, I think we'll have to sort some things out there as we go14:10
mesteryBut that's what the milestone releases are for14:11
armaxI am sure we’ll forget a few times14:11
mesteryForget and misformat14:11
mesteryAlmost guaranteed14:11
armaxbut we’ll get better and more trained over time14:11
*** lixinhui has quit IRC14:11
mesteryWe'll see :)14:11
*** mdorman has joined #openstack-meeting14:11
armaxthere’s also another change to the release process14:12
ihrachysreviewers should enforce it until it becomes general habit.14:12
armax#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/080288.html14:12
*** gongysh has quit IRC14:12
*** pots has joined #openstack-meeting14:12
*** zeih has quit IRC14:12
dougwigthis is a new meeting format we have today, i see.  :)14:13
armaxwhere it’s being proposed to skip the ‘Fix Committed’ phase and go straight to ‘Fix released’ when a patch targeting the bug merges14:13
*** PaulMurray has left #openstack-meeting14:13
armaxdougwig: how so?14:13
*** amuller has joined #openstack-meeting14:13
dougwigdid we skip announcements and all the usual?14:13
kevinbentondougwig: no, you just slept through them14:13
regXboii thought this *was* the announcements14:13
Sam-I-Ami think the announcement was 'its early'14:13
armaxI believe we’re announcing stuff, even though I am only functioning at 25% of my abilities14:14
armaxanother change worth raising awareness for is this one:14:14
armax#link https://review.openstack.org/#/c/226157/14:14
*** barrett1 has joined #openstack-meeting14:14
armaxthat discusses how to ensure backwards compatibility for clients and libraries14:14
regXboidoes going directly to fix released have any serious impact on our workflow? I'm not seeing it this morning...14:15
*** Daisy has joined #openstack-meeting14:15
armaxregXboi: I don’t think so14:15
regXboiarmax: that's why I'm asking, I don't see any either14:15
garyk1armax: i have a concern related to that and the decomposition of the neutron client - how do we support backwards compatibility14:15
armaxregXboi: I have asked when the process change would be in force, but no-one cared to reply to miss or I missed the response14:15
garyk1say a user is running client X and they upgrade and some support has been moved out - then they need to install additional packages14:16
regXboiarmax: you missed the response: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080372.html14:16
regXboiarmax: Doug is talking next week14:16
regXboier *targeting*14:17
armaxregXboi: I knew it I wouldn’t be ignored :)14:17
armaxregXboi: thanks14:17
regXboiarmax: yw14:17
armaxgaryk1: I think the proposal in the table is to prevent such scenarios from occurring in the first place14:17
armaxgaryk1: but I’ll have to digest more what the patch is dicussing14:17
*** baoli has quit IRC14:18
*** baoli has joined #openstack-meeting14:18
armaxok, let’s wrap up this section with two latest announcements/reminders14:19
armaxwe started a thread to discuss the Neutron and its evolution14:20
armax http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html14:20
armax#link   http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html14:20
*** neelashah has joined #openstack-meeting14:20
armaxyou’re welcome to share the opinion on the ML14:20
*** ajmiller has joined #openstack-meeting14:20
armaxthis week is M-1 week14:20
ihrachysthe 'move most RFEs to M2' week14:20
armaxso we’ll cut the milestone sometime mid-week, gate permitting14:21
armaxihrachys: yes14:21
armaxthere are a few things in flight that are likely to be complete by M-114:21
armaxwhoever is assigned here:14:21
armax#link https://blueprints.launchpad.net/neutron/mitaka/+assignments14:21
*** peristeri has joined #openstack-meeting14:21
armaxshould know what can wrap up in the next day or two14:21
*** arcee has joined #openstack-meeting14:21
armaxespecially for those that were Liberty backlog items14:22
armaxthis link brings me to the section of the meeting14:22
armaxdougwig: wait for it14:22
regXboithe gate?14:22
armax#topic Blueprints14:22
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:22
*** manjeets has joined #openstack-meeting14:22
armax#link https://launchpad.net/neutron/+milestone/mitaka-114:22
armaxright now we are at 30-odd blueprints and 20-odd RFE14:23
*** jmckind has joined #openstack-meeting14:23
*** ajmiller has quit IRC14:23
ihrachysI know three we can safely move to M214:23
pc_marmax: Are there any that are not odd?14:24
armaxihrachys: for everything that has not been marked complete, I’ll move to M214:24
* regXboi listens for the rim shot14:24
*** topol has joined #openstack-meeting14:24
armaxpc_m: I am sure there are14:24
armaxhaleyb: ping14:24
*** amotoki_ has joined #openstack-meeting14:24
haleybarmax: pong14:24
* haleyb knows the question...14:25
*** arcee_ has joined #openstack-meeting14:25
armaxhaleyb: well, it’s more of a stamtenet14:25
*** jichen has quit IRC14:25
armaxHenryG is going to help you with https://blueprints.launchpad.net/neutron/+spec/get-me-a-network14:25
amotoki_sorry for late14:25
Sam-I-Amalso one that needs some docs14:26
haleybyes, he pinged me last week, i will follow up with him today14:26
armaxI believe that HenryG has cycles to take over some of the work that you started14:26
kevinbentonSam-I-Am: which one needs docs?14:26
armaxso perhaps you may want to switch roles on the spec14:26
armaxhim being the assignee and you becoming the approver14:26
Sam-I-Amat least make sure we're tracking them14:27
armaxbut more eyes on the efforts are always welcome14:27
kevinbentonSam-I-Am: it doesn't exist yet though14:27
armaxbut please not everyone at once14:27
kevinbentonSam-I-Am: ah14:27
*** Daisy has quit IRC14:27
*** zeih has joined #openstack-meeting14:27
armaxlet’s not smother our two beloved developers14:27
haleybarmax: i think HenryG can definitely add some momentum14:27
*** Daisy has joined #openstack-meeting14:27
armaxthat’s the hope14:27
armaxihrachys: this one14:28
armax#link https://blueprints.launchpad.net/neutron/+spec/l2-api-extensions14:28
armaxdoesn’t have an approver14:28
ihrachysarmax: thanks for getting it targeted14:28
armaxdo you have anyone in mind that can help you with?14:28
ihrachysarmax: rossella maybe?14:28
*** arcee has quit IRC14:28
rossella_sarmax, ihrachys I was going to volunteer, you were faster ;)14:28
armaxrossella_s: if rossella_s can take it, let’s do it14:29
*** topol has quit IRC14:29
ajoI will track it too, it seems that QoS / DSCP is going to need it.14:29
*** roxanaghe has joined #openstack-meeting14:29
ihrachysI just read your mind and decided to be quicker than you type. rossella_s, thanks.14:29
ihrachysyeah, it turned out it's a blocker for QoS DSCP14:29
*** topol has joined #openstack-meeting14:29
rossella_sI am happy to help14:29
armaxdasm: ping14:29
*** sankarshan_away is now known as sankarshan14:29
armaxlast time or so we talked about14:29
armax#link https://blueprints.launchpad.net/neutron/+spec/rename-tenant-to-project14:29
dasmarmax: pong14:30
ajoQoS OVS/DSCP specifically, other implementations may not need any integration back to the L2 agent (may be LinuxBridge)14:30
rossella_sajo you are welcome too if you want to join the effort14:30
armaxI wonder if you had given it any thought14:30
dasmyeah. basically API seems to be pretty straight forward14:30
dasmbut for everything else.. we have about 1.6k places where tenant_id is used14:30
armaxfo you have anything in writing that is worth sharing?14:30
dasmyesterday started spec. didn't have time to wrap it up and send to review14:31
dasmstill working on it14:31
kevinbentoneven API will be a bit annoying because we have to support filtering and policy on both14:31
dasmbut i see it as (at least) two-step process.14:31
dasmkevinbenton: true14:31
armaxdasm: ok thanks for the effort14:31
armaxdasm: so let’s give you more time and we’ll figure out who can help you on reviewing the code etc14:32
dasmarmax: np. i'll send spec + probably some ML info about it.14:32
dasmarmax: +114:32
Sam-I-Amplenty of docs probably need changing too14:33
Sam-I-Ami think the networking guide already uses project, but most of the earlier docs do not14:33
*** roxanaghe has quit IRC14:33
*** aranjan has joined #openstack-meeting14:33
dasmone thing i'm wondering is support for all external projects.14:33
dasmi do not know how it will interfere with others14:33
dasm"external" i mean: all drivers, etc.14:34
armaxdasm: let’s take this offline, but the objective is that it would not14:34
armax#topic Bugs14:34
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:34
armaxrossella_s: you’re up14:34
*** markvoelker has joined #openstack-meeting14:34
armaxthis was also a semi-quite week I noticed14:34
rossella_sso this week was quite14:34
*** eharney has joined #openstack-meeting14:35
rossella_snothing to highlight apart from the lbaas thing14:35
*** Qiming has quit IRC14:35
ihrachyswhich thing?14:35
*** haomaiwa_ has joined #openstack-meeting14:35
*** markvoelker_ has quit IRC14:35
pc_marmax: For pinning do we need to do this for Juno?14:35
armaxok, so it’s either that we’re become rock solid, people have given up reporting burning issues?14:36
pc_marmax: Looks like Kilo pinning patch is working. Juno has issues.14:36
ihrachysJuno is dead, we should dig it deep and forget.14:36
*** Piet has quit IRC14:36
rossella_ssomething worth noticing is that there were changes in the DocImpact flag. Now if a neutron commit has a DocImpact flag the bug is filed to Neutron directly, no more to the doc team. I was confused when I found the first doc bug. More info here http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html14:36
Sam-I-Amtrying to fix the docs problem14:37
armaxrossella_s: good point, I noticed it too14:37
ajoihrachys , may be we can put some roses on the gravestone14:37
ajofor our long loved june... ;)14:37
Sam-I-Amdocimpact changes things a bit14:38
armaxrossella_s: anything else?14:38
*** amotoki has quit IRC14:38
armaxwe have dougwig as deputy for next week14:38
armaxany taker for the after that?14:38
armaxand please, pretty please…do not rush at all once to get tht eweek of christmas14:39
mesteryarmax: Has everyone done it at least once?14:39
rossella_sarmax there's a proposal upstream to use a special tag for bugs for new contributors http://lists.openstack.org/pipermail/openstack-dev/2015-November/080482.html14:39
*** amitgandhinz has joined #openstack-meeting14:39
mesteryarmax: You should know the answer to that14:39
garyk1i can take the week of xmas14:39
*** dmowrer has quit IRC14:39
amotoki_the week of Dec 7?14:39
* dougwig is quivering in anticipation.14:39
HenryGI can do it after dougwig14:39
*** otter768 has joined #openstack-meeting14:39
mesteryDid I scare armax?14:40
kevinbentonthen i can go after HenryG14:40
armaxrossella_s: ok, I’ll read through, but we do have the low-hanging-fruit tag in Neutron bugs for some time now14:40
armaxok, so HenryG goes next14:40
kevinbentondougwig, HenryG, kevinbenton, garyk1 and we have Dec covered!14:40
armaxgaryk1: you did it once already, let’s give someone else the opportunity to step up14:40
dougwigwhen i was a newbie, low-hanging-fruit was useless, btw. but that's a tangent.14:40
rossella_sarmax, yes it's just a proposal, it's still being discussed. I can watch it and report if any action from us is needed14:40
kevinbentondougwig: take your paint elsewhere! :)14:41
*** Daisy has quit IRC14:41
Sam-I-Amthe bug itself might be easy to fix - its the process thats more complicated14:41
mhickeydougwig: I agree14:41
*** achanda_ has quit IRC14:41
armaxdougwig: I never remember you coming to me and bitch about it thought14:41
rossella_sdougwig, that's what the proposal tries to fix14:41
*** Daisy has joined #openstack-meeting14:41
dougwigarmax: i was a newbie, how would i know who to complain to?14:42
armaxrossella_s: ok, so the thread is deflinitely worth reading14:42
rossella_sI didn't want to start a discussion here, let's discuss using the thread then :)14:42
armaxdougwig: aw14:42
*** weshay has quit IRC14:42
armaxnext section up14:42
armax#topic Docs14:42
*** openstack changes topic to "Docs (Meeting topic: networking)"14:42
Sam-I-Amyay docs14:43
armaxemagana or edgar doesn’t seem to be here14:43
armaxSam-I-Am: yo14:43
armaxanything worth sharing?14:43
Sam-I-Amsure. docs spec for ovn in the networking guide was approved.14:43
Sam-I-Am#link http://specs.openstack.org/openstack/docs-specs/specs/mitaka/networkguide-ovn.html14:43
Sam-I-Amnow just to find time for adding content14:44
*** otter768 has quit IRC14:44
Sam-I-Amedgar is supposedly restarting the networking guide meeting this or next week14:44
Sam-I-Amthe times are a little sketchy still14:44
*** mbound_ has joined #openstack-meeting14:44
Sam-I-Amwhen that happens, we're going to discuss how to improve the scenarios in the networking guide (mostly around how to make it possible to connect VMs to ext/public networks for all cases)14:44
armaxSam-I-Am: how do I land on the OVN spec site?14:45
armaxSam-I-Am: from http://specs.openstack.org/ I mean14:45
Sam-I-Amwell, the neutron specs are here - http://specs.openstack.org/openstack/neutron-specs/14:45
Sam-I-Ami dont see ovn stuff there14:46
*** brad_behle has joined #openstack-meeting14:46
russellbthere is no ovn specs site14:46
armaxwell, that’s a docs spec as far as I can tell14:46
salv-orlandoI don't think ovn specs get submitted there14:46
*** mdorman has quit IRC14:46
russellbthe doc spec is what Sam-I-Am was reporting on14:46
salv-orlandoans should there be a neutron counterpart to it? I don't think so but I know nothing about this.14:47
Sam-I-Amthe key here is trying to get usable docs before a large feature becomes available14:47
armaxsorry, let me rephrase14:47
armaxthe spec states: Add OVN content to the networking guide in coordination with the development process14:48
*** adahms has quit IRC14:48
russellbadd content about features as they become available?14:48
russellbwords are hard14:48
armaxhow is someone going to access this content14:48
Sam-I-Amyeah, they are hard :)14:48
russellbthe networking guide14:48
*** kozhukalov_ has quit IRC14:49
Sam-I-Amdevs+docs people munge content from a variety of sources into official docs as it becomes available14:49
armaxyes but where!14:49
armaxnever mind14:49
armaxlet’s move on14:49
armax#topic Open Discussion14:49
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:49
salv-orlandoI think Sam-I-Am was just looking for a place for said content in neutron-specs14:49
*** mtanino has joined #openstack-meeting14:50
Sam-I-Amarmax: i havent figured out where the content goes in that guide yet14:50
*** leifz has joined #openstack-meeting14:50
*** jreeves has joined #openstack-meeting14:50
ihrachysI had something on tempest gating for qos14:50
ihrachysarmax: ping me when slot is up^14:50
armaxihrachys: go ahead14:50
gsagieSam-I-Am : i think what armax is wondering, and so am i, where in this guide do you have a section for the various different backends, or OVN is going to be the first one besides the reference implementation (OVS) ?14:50
ihrachysok, so we are looking at getting qos tempest scenarios in gate14:51
ihrachysand we have some patches to add new job with qos enabled: https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-tempest-gate-hook,n,z14:51
ihrachysthe question that amuller asked me lately is why separate job14:51
ihrachysmaybe we want to have it in existing jobs?14:51
amullerTiny bit of context: The Neutron API job is running QoS tests, Ihar is talking about Tempest scenario tests right now14:51
Sam-I-Amgsagie: the guide covers linuxbridge and conventional ovs now. ovn will be added to that list either as something that uses ovs, or completely new mechanism because it deprecates the conventional l3 and dhcp agents14:51
ihrachysthe problem with that is that infra does not allow to use devstack plugins in integrated jobs14:51
ihrachysso then we would need to move devstack plugin that currently configures qos into devstack repo14:52
ihrachyswhich is fine for me, but we got some resistance in the past against doing it14:52
armaxihrachys: no, I believe we should be able to keep the qos stuff in neutron14:52
gsagieSam-I-Am : and if i or anyone else would like to add documentation for any other backend solution, is that possible? if yes, would love if you can elaborate how14:52
amullerarmax: The question is how do we do that but not create a new job for 'advanced configurations', first one being QoS14:53
ihrachysor maybe we want to have some kind of 'advanced' job that will enable all the random things we may want to test out of integrated14:53
dougwigthis review is also related to the greater issue here, btw: https://review.openstack.org/#/c/221143/14:53
hichiharaI agree with armax. devstack don't have qos configure14:53
armaxihrachys: I wonder if mordred had a chance to review the latest comment/question posted on https://review.openstack.org/#/c/247697/14:53
ajothe scenario tests are important not just to validate our behaviour but to validate other vendor plugins behaviour when implementing QoS14:53
salv-orlandofwiw I too do not thing QoS is of specific interest for the integrated gate14:53
dougwigthere is also armax's idea of putting the new dsvm jobs into the post-merge queue instead of check/gate14:53
armaxI have a draft mail to propose a solution about this14:54
armaxthat’s long overdue14:54
armaxif nothing distracts me, I shall be able to send it out today14:54
* mordred goes to look14:54
Sam-I-Amgsagie: right now the guide supports reference arch (read: non-vendor) backends, so i'd need to know what you were thinking.14:54
salv-orlandoajo: what you say make sense - but as a vendor I can ran those tests even if they're not part of the integrated way. As long as you write them enough black-ish that I can use them with my backend14:54
ihrachysso whatever works for you folks. I am good either way.14:54
mordredoh! whoops. removing -2 now14:54
amullerarmax: so no problem with another new job that will run on every patch?14:55
mordreddone - thanks!14:55
russellbSam-I-Am: "non-vendor" is a complicated line to draw :-)14:55
amullersorry, every patchset14:55
*** tej has joined #openstack-meeting14:55
armaxmordred: thanks for keeping us in check!14:55
armaxamuller: it depends14:55
sc68calI don't think the networking guide benefits from having 10+ backends14:55
ajosalv-orlando , it could be available and disabled by default in config, if that's what you mean, true14:55
gsagieSam-I-Am: if you allow OVN to have docs there then you should allow it for any other Open Source project (and in my mind also non Open Source ones)14:55
armaxI am getting lost14:56
salv-orlandothe "networking encyclopedia"14:56
armaxpeople are still talking about docs14:56
ihrachysarmax: maybe having a single job for advanced stuff? qos, flavors, ponnies14:56
armaxa single job for docs?14:56
armaxihrachys: :)14:56
armaxor a doc to rule them all?14:56
ajoboth.. :)14:56
salv-orlandounicorns. I want unicorns too.14:56
ajosalv-orlando : not without rainbows14:57
Sam-I-Amwhat about rainbows?14:57
ihrachyssalv-orlando: I will put it into todo list for Apr 114:57
kevinbentonrussellb: right. especially when a lot of the vendor plugins are also open source ...14:57
dougwigoh jeez, this early meeting gets off the rails fast.14:57
armaxamuller, ihrachys: let’s make sure we make progress on that topic you raised this week14:57
kevinbentondougwig: just wait until the one after this! :)14:57
armaxI’ll give you guys 3 minutes back14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Tue Dec  1 14:57:51 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-12-01-14.00.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-12-01-14.00.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-12-01-14.00.log.html14:57
dasmthanks all14:58
*** amuller has left #openstack-meeting14:58
ajobye :)14:58
ajoand thanks14:58
Sam-I-Amlater all14:58
mhickeybye, thanks14:58
manjeetsbye, thanks14:58
*** Sam-I-Am has left #openstack-meeting14:58
russellbkevinbenton: could be some sort of diversity of contributor criteria ... but meh, sounds complicated14:58
gsagieSam-I-Am : so can you please let me know what is the criteria for adding docs? because as i mentioned there are other open source solutions that implement the Neutron API and could deserve there documents like Midonet and ODL14:58
*** pc_m has left #openstack-meeting14:58
gsagieproject Calico?14:59
*** shz has joined #openstack-meeting14:59
*** absubram has joined #openstack-meeting14:59
russellbsomeone should propose a doc spec14:59
*** Daisy has quit IRC14:59
russellbif it's not obvious, we'll work through it and maybe land on some criteria14:59
*** Daisy has joined #openstack-meeting14:59
*** baoli has quit IRC14:59
russellbOVN seems a bit more obvious ... it's an evolution of OVS itself, from the OVS project, several different companies contributing15:00
russellbOpenDaylight is another obvious one15:00
russellbi don't know enough about midonet's community15:00
*** regXboi has left #openstack-meeting15:00
*** neeti_ has quit IRC15:00
*** diltram has left #openstack-meeting15:00
armax#startmeeting neutron_drivers15:00
openstackMeeting started Tue Dec  1 15:00:47 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
*** sbelous_ has left #openstack-meeting15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"15:00
openstackThe meeting name has been set to 'neutron_drivers'15:00
*** wwriverrat has left #openstack-meeting15:00
*** hichihara has quit IRC15:00
*** njohnston has joined #openstack-meeting15:00
armaxwelcome back to some of you15:01
*** kozhukalov_ has joined #openstack-meeting15:01
*** baoli has joined #openstack-meeting15:01
*** amotoki_ is now known as amotoki15:01
* kevinbenton thinks mestery is doing yoga15:01
*** fzdarsky has quit IRC15:01
mesterykevinbenton: That's one interpretation15:01
armax#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers15:01
dougwigwelcome to the uncaffeinated drivers meeting!15:02
armaxwe have 10 triaged bugs to go through and deliberate on15:02
armax#link https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=Triaged&field.tag=rfe&orderby=datecreated&start=015:02
*** angdraug has joined #openstack-meeting15:02
*** phil__ has quit IRC15:02
*** dmowrer has joined #openstack-meeting15:03
armax#bug 102315615:03
openstackbug 1023156 in neutron "[RFE] QuantumDbPluginV2 should support extended attributes on core resources" [Wishlist,Triaged] https://launchpad.net/bugs/1023156 - Assigned to Ihar Hrachyshka (ihar-hrachyshka)15:03
*** Daisy has quit IRC15:03
*** kencjohnston has joined #openstack-meeting15:03
*** vhoward has joined #openstack-meeting15:03
*** cbits has joined #openstack-meeting15:03
*** mlavalle has joined #openstack-meeting15:03
dougwigcan we timebox at max 5 mins per bug?15:03
armaxihrachys: you care to comment on this one?15:03
*** jlibosva has left #openstack-meeting15:03
armaxdougwig: we should15:03
ihrachysarmax: aye15:03
armaxdougwig: if we could15:03
ihrachysso the bug is to make ml2 extensions not ml2 specific15:03
*** Daisy has joined #openstack-meeting15:04
ihrachysto have some core resource extension manager that can consume extensions like ml2 extensions and can be integrated into any plugin15:04
*** annp has quit IRC15:04
ihrachysintegrate once, get more extensions automagically15:04
*** rvasilets_ has joined #openstack-meeting15:04
*** manjeets_ has joined #openstack-meeting15:04
*** achanda has joined #openstack-meeting15:04
russellbi like the goal, at least15:04
ihrachysf.e. for now qos is ml2 specific for that reason15:04
*** yamamoto_ has joined #openstack-meeting15:04
*** sankarshan is now known as sankarshan_away15:04
russellbthat's been a problem for networking-ovn15:04
ihrachyswell, plugins can dup the code to support it, but it's not ideal15:05
dougwigisn't this an end run around the ORM?15:05
armaxdo we really want to ml2-fy the core plugins?15:05
*** hoangcx has quit IRC15:05
*** yamamoto has quit IRC15:05
ihrachysarmax: how is it ml2-ying anything? it's just making some existing features working for all other plugins.15:05
mesteryMy vote is to not ml2-fy the core plugins15:05
ihrachysif anything, it's un-ml2-fying neutron15:05
garyk1so now ml2 has become a verb?15:06
ihrachysmestery: you vote for each plugin to be updated for any 3rd party service plugin?15:06
*** spotz_zzz is now known as spotz15:06
armaxihrachys: you’ll have to call methods in a loop don’t you15:06
*** fzdarsky has joined #openstack-meeting15:06
*** mbound_ has quit IRC15:06
*** Daisy has quit IRC15:06
amotokidoes ml2-ying mean to allow to dsiable  extensions by config?15:06
ihrachysarmax: inside the manager, yes. but in the plugin, you just call to the manager once and it makes the magic.15:06
armaxnot that there’s anything wrong with that per se15:06
armaxihrachys: did you do any PoC investigation on how that would look like?15:07
mesteryihrachys: Nope, not what I want.15:07
*** sgundur has joined #openstack-meeting15:07
ajoo/ sorry, I got distracted and wanted to join15:07
ihrachysarmax: no, and probably I won't have time for that in M due to... you know... stuff15:07
armaxihrachys: stuff, we all love *the* stuff15:07
markmcclainmagic is bad because it's easily misunderstood/abused15:07
armaxihrachys: you should be careful15:07
ihrachys1 min...15:07
ihrachysarmax: our own stuff especially15:08
*** aranjan has quit IRC15:08
armaxihrachys: ok, right now no staffing, plus some concern on the complexity of the resulting implementation15:08
*** dims has quit IRC15:08
armaxI’ll capture this on the bug report15:08
*** dguitarbite has joined #openstack-meeting15:08
armax#bug 143815915:08
openstackbug 1438159 in neutron "[RFE] Make neutron agents less chatty on AMQP" [Wishlist,Triaged] https://launchpad.net/bugs/143815915:08
dougwigso, reading it again, this is enabling filtering across an extension mechanism that already exists, right?15:08
*** mbound_ has joined #openstack-meeting15:09
armaxihrachys, kevinbenton you both commented on this one15:09
ihrachysarmax: I suspect that one is (partial?) dup for kevin's rpc refactoring15:09
armaxkevinbenton: you have the push notification discussion going on15:09
armaxihrachys: right15:09
ajolooks like a dup15:09
kevinbentonyeah, i think this is already basically going to be covered by RPC callbacks and the stuff i am doing15:10
ihrachysnot exactly a dup, since some stuff there is on top of it, like per agent topic for pushing updates.15:10
armaxok, I’ll make sure I capture that and clean up any loose end15:10
armaxbut it’s definitely related15:10
armaxihrachys: is it not?15:10
ihrachysbut I don't believe we need RFE for that now until we settle on kevin's work and assess it15:10
ihrachysarmax: it is related15:11
kevinbentonihrachys: +115:11
ihrachysarmax: and it should be reassessed after we have rpc refactored15:11
*** mrmartin has joined #openstack-meeting15:11
ihrachyscan be closed/postponed for now15:11
*** emagana has joined #openstack-meeting15:12
armax#bug 148638815:12
openstackbug 1486388 in neutron "use timestamp of resources to reduce the agent sync load" [Wishlist,Triaged] https://launchpad.net/bugs/148638815:12
armaxthis is also related, in that it’s proposign a different approach to deal with loadd15:12
dougwigis this introducing a dependency on ntp, or do we alrady require that?15:12
armaxbut I think it’s one or the other15:12
dougwigbecause if your clocks are out of sync...15:13
kevinbentonusing timestamps for sync is a workaround for other innefficiencies imo15:13
mesteryWe don't require NTP15:13
armaxkevinbenton: agreed15:13
mesteryBut we should15:13
kevinbentonwe should be able to fetch 500 things from a DB in short order15:13
ihrachysyes, should not be an issue after switching to rpc callbacks (assuming we handle raciness for the latter)15:13
dougwigif we do this at all, i'd think it should be with sequence numbers, not time.15:13
armaxrunning a cloud without NTP is a disaster waiting to happen15:13
*** werunthenight has joined #openstack-meeting15:13
markmcclainout-of-sync clocks can create other problems too15:14
ajodougwig : +1 for seqnumbers15:14
russellbntp is effectively required already15:14
markmcclaindougwig: lamport clock15:14
ajoeven if synced they can drift15:14
kevinbentonyes, time is unreliable as to what is 'newest' without distributed locking that can account for drift15:14
armaxI think this proposal is effectively clashing with some of the things that kevinbenton and ihrachys were talking about eralier15:14
kevinbenton(ala google's spanner paper)15:15
ihrachysit does. it won't apply once kevinbenton does... stuff15:15
dougwigok, off with it's head.15:15
armaxso for that reason, I’d say ‘wonfix’15:15
armaxbug 150824315:15
openstackbug 1508243 in neutron "Store Private Key Passphrase in Neutron-LBaaS for TLS Terminations" [Wishlist,Triaged] https://launchpad.net/bugs/1508243 - Assigned to Doug Wiegley (dougwig)15:15
kevinbentondefer to dougwig :)15:15
armaxeveryone wants a pony but no-one is willing to pay for it15:16
armaxthat’s the gist on this bug?15:16
salv-orlandoare we even considering storing a private key in neutron?15:16
armaxsorry RFE15:16
*** dguitarbite has quit IRC15:16
dougwigthey were debating this one internally, and i can't say i'm thrilled with the idea of storing passwords in the db.15:16
kevinbentonstore it in the description field or as a tag :)15:16
armaxwhat’s wrong with storing passowrds in clear?15:16
*** werunthenight has quit IRC15:16
dougwigi'd like to talk with adam/rm_work about this one.15:16
armaxjust use simple ones15:17
armaxlike mysecret12315:17
dougwigsex or money or password15:17
salv-orlandoif you have nothing to hide, you have nothing to worry15:17
*** werunthenight has joined #openstack-meeting15:17
* neiljerram heads off to armax's Gerrit account...15:17
* ihrachys makes notes15:17
armaxsalv-orlando: said the man who’s hiding something15:17
ihrachysneiljerram: exactly15:17
armaxdougwig: ok, I think this needs a spec to say the least15:17
armaxbut if no-one is willing/able to staff it…this is dying ‘incomplete’15:18
dougwigarmax: ack, but let me vet it first.  i'll put it on my list for today.15:18
*** sgundur has quit IRC15:18
armaxis that a fair assessement?15:18
armaxwhat’s the existing workaround today, dougwig?15:18
*** manjeets has quit IRC15:18
*** sgundur has joined #openstack-meeting15:18
werunthenightgood question15:19
dougwigdon't use a passphrase on your tls cert, or it's in barbican.15:19
dougwigand i'm not certain why that's not enough.15:19
amotokiif so, it is better to be clarified.15:20
*** ricolin has joined #openstack-meeting15:20
*** pm90_ has joined #openstack-meeting15:20
*** banix has joined #openstack-meeting15:20
armax#bug 150838415:21
openstackbug 1508384 in neutron "QoS proxy functions" [Wishlist,Triaged] https://launchpad.net/bugs/150838415:21
armaxthis might be quick15:21
dougwigthat sounds like a challenge.15:21
armaxI personally don’t see much of an issue to add client support as server capability increases15:21
ihrachyswith no huge benefit for those who add support for new qos rule types15:22
armaxthat’s not where the bulk of the cost lies15:22
*** weshay_xchat has joined #openstack-meeting15:22
ajoIt makes neutron client more usable15:22
ajobut, it increases the amount of server queries we need to do15:22
ihrachysajo: how so, assuming client is updated with new CLI?15:22
*** pm90__ has joined #openstack-meeting15:23
ajomay be I got it wrong15:23
*** harlowja_at_home has joined #openstack-meeting15:23
ihrachysalso it's something new for neutron to maintain API schema accessible thru REST15:23
ajobut my understanding was that the proxy functions lived on the python-neutronclient15:23
dougwigif the qos client support was part of the neutron package, as an extension, couldn't it be updated with the same commit that makes the api change, too?15:23
*** ajmiller has joined #openstack-meeting15:23
*** f13o has joined #openstack-meeting15:23
ihrachysajo: see comment #5, David proposes to inspect API schema.15:24
amotokiwe made similar discussions on finding capabilities.15:24
ajoahh, ok, I missed that update15:24
* ajo is outdated :(15:24
*** mrmartin has quit IRC15:24
amotokiexposing API schema sounds good to me.15:24
ajoIf we expose the API schema, probably isn't something we'd like to do neutron-wise?15:25
ihrachysamotoki: I can consider it, but then not just for QoS.15:25
armaxI appreciate that there’s the neat way of doing things and the dull way of doing things15:25
salv-orlandoajo: maybe...15:25
*** fawadkhaliq has quit IRC15:25
amotokiif a client library can expose this kind of information, we can use it from CLI, horizon or other stuff.15:25
dougwigsince you can dynamically extend the client, isn't a better model to put new client feature support where the feature lives, instead of a workaround like api introspection?15:25
*** pm90_ has quit IRC15:25
*** korzen has quit IRC15:25
armaxif someone wants to go on a quest to rewrite every possible framework we rely on to embrace this working model, sure that’s a possibility15:26
*** arvinchou_ has quit IRC15:26
ihrachysarmax: +1 who's paying?15:26
*** FallenPegasus has quit IRC15:26
amotokia client library has two options: define them inside it or fetch them from neutron.15:26
salv-orlandoihrachys: Don Quixote, Inc.15:26
*** fawadkhaliq has joined #openstack-meeting15:26
*** dane has joined #openstack-meeting15:27
armaxihrachys: that’s one quesiton, the other question is: what’s the long term gain, and how it related to the short-term one?15:27
armaxhow frequently does functionalitiy have to evolve for this working model to be worthwhile15:28
dougwigi don't have a strong opinion here, beyond not liking jamming every little thing inside the monolithic client, which doesn't affect this rfe. (though client extensions did exist before qos.)15:28
armaxthe initial investment of getting qos capabilities in the client is done already15:28
ihrachysno idea why we did it in core :)15:28
*** zz_dimtruck is now known as dimtruck15:28
*** werunthenight has quit IRC15:28
*** markvoelker_ has joined #openstack-meeting15:28
ihrachyswe could move it away, but it's irrelevant to rfe15:28
armaxand if we had resources to spare I’d rather have someone work on the openstack client for a bit15:29
*** whenry_ has joined #openstack-meeting15:29
armaxas a matter of fact there’s an rfe on it too…but that’s much newer and I am going chronologically15:29
ajoarmax : +115:29
*** e0ne has quit IRC15:29
armaxok, let me capture the conversation that we had here and we’ll see15:29
ihrachysso can we move forward then? or people feel strongly we need API schema right now?15:30
*** roxanaghe has joined #openstack-meeting15:30
armaxihrachys: I’d say hold it for now15:30
armaxbug #151157415:30
openstackbug 1511574 in neutron "[RFE] Support cleanup of all resources associated with a given tenant with a single API call" [Wishlist,Triaged] https://launchpad.net/bugs/1511574 - Assigned to John Davidge (john-davidge)15:30
armaxamuller is not the room15:31
armaxhe’s the one who had some concern about this15:31
ihrachysshould it really be API, or local db crawling tool is enough?15:31
*** thangp has joined #openstack-meeting15:31
armaxihrachys: it’s gotta be API I think15:31
armaxbecxause cleaning up the DB is not enough15:31
armaxyou may want to issue RPC messages and all15:32
*** markvoelker has quit IRC15:32
amotokii think crawling db is not enough. we need to clean up on nodes.15:32
*** edtubill has joined #openstack-meeting15:32
dougwigi'd be in favor of adding a purge, and if the eventual cross project definition differs, support that as well. punting a real ops concern for some unicorn definition later seems like just passing the buck.15:32
* ajo asks armax for a slot on 1512587 (QoS/RBAC) and 1461000 (OVS/CT Firewall -status update-) when other priorities are sorted out15:32
armaxdougwig: how bad can they differ?15:32
ihrachysarmax: ok. not that we cannot issue RPC without API calls.15:32
armaxin the simplest of cases the API call should be15:32
dougwigarmax: agree.  purge(tenant).15:33
*** mdorman has joined #openstack-meeting15:33
*** amuller has joined #openstack-meeting15:33
*** markvoelker_ has quit IRC15:33
armaxand if not, then we logic is not going to change that dramaatically15:33
armaxhi amuller15:33
armaxsomeone must have pulled you in15:33
armaxwe’re talking about 151157415:33
armaxbug 151157415:33
openstackbug 1511574 in neutron "[RFE] Support cleanup of all resources associated with a given tenant with a single API call" [Wishlist,Triaged] https://launchpad.net/bugs/1511574 - Assigned to John Davidge (john-davidge)15:33
amulleryeah Miguel pinged me15:33
*** mrmartin has joined #openstack-meeting15:33
amullerI worked on tenant deletion a yearish ago15:34
armaxI remember you had done some work on this already15:34
* ajo whistles...15:34
armaxdidn’t you?15:34
ihrachysI remember those patches; they were -2'd15:34
*** gcb has quit IRC15:34
*** roxanaghe has quit IRC15:34
armaxthey were ahead of their time15:34
*** john-davidge has joined #openstack-meeting15:34
armaxamuller: you were a visionary15:34
ajolol :)15:34
amullerarmax: I get that literally every never15:34
amullerso, there's lots of ways of going about that15:35
armaxin the end something like os-purge does the job15:35
armaxright, plenty15:35
amullerwe can say it's not Neutron's problem and use an external tool (like ospurge)15:35
salv-orlandooh well some guy tried that a year before amuller I think15:35
*** zeih has quit IRC15:35
*** belmoreira has quit IRC15:35
armaxoh amuller sorry you’re no longer a visionary, I take it back15:35
ajosalv-orlando : seems like a hard wall15:35
amullerwe can listen on the RPC bus for keystone tenant (sorry, project) deletion15:35
ihrachyssalv-orlando: that one was genius, not visionary15:35
*** mdorman has quit IRC15:35
amullerbut neutron-server may be down when that notification goes out15:36
amullerso you need a 'sync' mechanism15:36
amulleryou expose it via  the API15:36
*** sdake_ has quit IRC15:36
amullereither way we need a consistent story across openstack15:36
armaxI think there are three positions here15:36
dougwigit's a straight-forward definition, it has a volunteer, why would we just punt it?15:36
amullerdougwig: I'm not saying that15:36
salv-orlandodougwig: strongly agree with you15:37
armaxyou either have the whole pruning/purging all integrated and fully managed end-to-end15:37
armaxthat’s one end of the sprecturm15:37
armaxthe other end of the sprectrum is what we have today15:37
armaxthe admin is on his/her own15:37
amullerI don't think we should go with the API approach without getting cross-project agreement with Nova and Cinder at the least15:37
armaxthe middle ground is, neutron gives you a short-cut to clear tenant resources at once15:37
armaxat a push of a button15:37
ihrachysamuller: but we can go with a tool that triggers the operation inside neutron-server15:38
armaxamuller: I don’t understand why we’d preclude ourselves the ability to provide the shortcut based on what other projects might do15:38
salv-orlandoI mean API wise, even if Neutron does not own tenants, it is fair to assume it manages a TENANT resource on which you can only do GET and DELETE15:38
armaxI can talk to the Nova and Cinder PTL to see where they are on this15:38
dougwigamuller: what's the risk of adding one sooner?  maybe there's a slightly different cross-project signature, and we support both with the same code for awhile? that seems better to me than leaving ops in the cold.15:38
*** neiljerram has quit IRC15:39
salv-orlandoamuller is probably bringing up a reasonable problem of API consistency15:39
amullerdougwig: I don't know why you assume that other projects would be against this?15:39
*** lazy_prince has quit IRC15:39
amullerit's reasonable to it via the API15:39
*** aleksandr_null has quit IRC15:39
amullerHopefully other projects would arrive at the same conclusion15:39
amullerdoing it via RPC has its shortcomings15:39
dougwigamuller: i'm just assuming that going cross-project punts it a cycle.15:39
armaxI agree with amuller that consistency will be nice15:39
amullerdougwig: so be it15:40
armaxbut other projects had tags on teh api15:40
armaxand they didn’t wait for all projects to ocmply15:40
armaxthat begs the question if we need to file a spec to openstack-specs15:40
salv-orlandoamuller:  correct. For instance a REST API is way easier to integrate into whatever tools ops use than a RPC over AMQP call15:40
armaxand then proceed from there15:40
amullerthis has been a problem for years, putting some arbitrary time limit on this and saying screw quality or what's right is misguided15:40
amullerwe should do what's right for all of openstack15:40
amullernot just an rfe in neutron15:41
amotokiamuller: totally agree15:41
*** aleksandr_null has joined #openstack-meeting15:41
armaxamuller: right, one can proceed with a spec in http://specs.openstack.org/openstack/openstack-specs/15:41
amullerarmax: that sounds great15:41
armaxbut work can happen regardless in neutron15:41
dougwigamuller: you're right, but this isn't an argument of absolutes.15:41
armaxas the effort to reconcile the two15:41
armaxwon’t be hard15:42
armaxthere’s really not much to go wrong here IMO15:42
amullerarmax: if we introduce an API in Neutron and the cross project effort dies we've screwed ourselves and the entire openstack community15:42
ihrachysarmax: is it a way to say we will 'follow up' on it (never happens)?15:42
armaxthe simplest purge(tenant_id) would suffice15:42
armaxand I shall say15:42
amullerarmax: dougwig: What if John writes the code without the API endpoint15:42
*** neiljerram has joined #openstack-meeting15:42
amullerfor example a CLI tool would invoke it15:42
amulleras first step15:42
armaxamuller: that wouldn’t be the first time something like that happens15:43
amullera later step would add an API endpoint that would invoke the exact same code15:43
*** neiljerram has quit IRC15:43
dougwigor maybe we steal a play from other protocols, and let him implement /x-purge, saving the real /purge for the cross project effort, and knowing that one will likely silently call the other.15:43
armaxopenstack is not exactly renowned for consistency15:43
amullerarmax: and we should do our part to combat that, not accept it as some axiom15:43
ajoat least now we're conscious about it15:43
ajoas a first step15:44
armaxamuller: agree, but that’s the nature of the beast15:44
armaxamuller: you can fight it, but you’ll never kill it15:44
salv-orlandodougwig: whatever... I'd just release note the API as experimental and warn all users that its syntax and/or semantics could change over time15:44
ihrachysI am for unblocking RFE as long as API is not included in first iteration, and we bring the API topic in cross project specs15:44
salv-orlandowe've done that before too.15:44
armaxhaving code that’s unreachable?15:44
armaxwhat’s the point?15:45
amullerarmax: you would reach it via CLI15:45
ihrachysarmax: how is it unreachable? it's avail thru ssh :)15:45
salv-orlandoihrachys: I can bring that up with the API WG, but I'm not sure if that is the right place, since it also involves interactions between keystone and everybody else15:45
dougwigsalv-orlando: the point of an experimental namespace is that you don't break backwards compatibility, but still get to say, "this might change". i hate backwards incompatibiliy.15:45
*** Ramanjaneya has quit IRC15:45
ihrachysamuller: even /usr/sbin/neutron-tenant-cleanup15:45
amullerihrachys: true15:45
amullerihrachys: you mean project :)15:45
amullerihrachys: tenant is a bad word now15:45
armaxI am not sure I fully understand15:45
*** achanda has quit IRC15:45
armaxamuller: can you make your proposal on the bug report please?15:46
* ihrachys hits himself hard15:46
salv-orlandodougwig: yeah, I think we're on the same page. I was just pointing out that being the API not so well organized at the moment you might not bother with the exp namespace15:46
ihrachysarmax: we have neutron-linuxbridge-cleanup; we don't expose it thru API15:46
amullerthe bad part of having an opinion is action items15:46
armaxihrachys: but that’s different15:46
dougwigi think we're past our timebox on this one.15:46
amullerarmax: I'll try to come up with something concrete15:47
ihrachysyeah, let's give amuller a chance to comment there.15:47
armaxihrachys: here we have stuff that spans a lot more than one agent15:47
*** e0ne has joined #openstack-meeting15:47
armaxamuller: thanks amuller15:47
ihrachysarmax: hence server side tool15:47
amullerplease do move on15:47
armaxyes sir15:47
armaxbug 151258715:47
openstackbug 1512587 in neutron "[RFE] Role-based Access Control for QoS policies" [Wishlist,Triaged] https://launchpad.net/bugs/1512587 - Assigned to Haim Daniel (hdaniel)15:47
*** claudiub has quit IRC15:48
*** manjeets has joined #openstack-meeting15:48
ajoarmax , why do you believe this needs an spec?15:48
openstackLaunchpad bug 1512587 in neutron "[RFE] Role-based Access Control for QoS policies" [Wishlist,Triaged] - Assigned to Haim Daniel (hdaniel)15:48
ajoyes, armax , but I didn't fully understand that15:48
ajoit's partly of what the bug is going to fix15:49
dougwigthe use case sounds more like flavors than rbac.15:49
armaxthis is going to provide API changes etc15:49
ajoarmax: not finally, we talked about it on the QoS meeting15:49
ajowe were considering the drop of --shared in favor of using rbac directly15:49
ajoinstead of --shared on policy, doing rbac access_as_shared *15:50
armaxok, so where is this design discussion being captured? :)15:50
ihrachysas I told before, you can't drop, it's not compat.15:50
ajothe call was not to introduce api changes15:50
armaxeither spec of devref, someone has to explain how this is going to work15:50
*** baoli has quit IRC15:51
ajoarmax , isn't the rfe good enough?, I will go over it and make sure there won't be any api changes15:51
*** baoli has joined #openstack-meeting15:51
ajoI see the rfe is now unconsistent with what we said on the meeting15:51
armaxajo: the chance doesn’t sound trivial enough to warrant no information being captured in some forme or another15:52
*** mrmartin has quit IRC15:52
amotokiajo: i think RFE is a place to discuss what feature we want. it is betetr to discuss how in spec or devref.15:52
ajoarmax, ok, I will get it specced then15:52
armaxI am ok with the use case, but I think we need to document somehow the work involved15:52
ajook, as long as we're all on the same page,15:53
armaxspec or devref 15:53
ajoI didn't fully understand your comment at #8, but now it's clear to me :)15:53
armaxbut spec seems the most natural thing as this is very user visible15:53
armaxajo: sorry, most of the times I talk with my eyes closed15:53
ajoack, let's go for a spec with the high level details15:53
armaxand type like a monkey15:53
ajoarmax : nope, the RFE details were outdated and missleading, I must admit15:54
ihrachysok, so ajo updates the RFE bug and provides a spec.15:54
armaxok next15:54
armaxbug 151790315:54
openstackbug 1517903 in neutron "[RFE] Add agent specific API for l2 agent extensions" [Wishlist,Triaged] https://launchpad.net/bugs/1517903 - Assigned to Ihar Hrachyshka (ihar-hrachyshka)15:54
armaxthis actually shows as approved in the list of blueprints15:54
armaxfor mitaka-115:54
*** dims has joined #openstack-meeting15:54
ihrachysyeah, saw you approved for M1 already. I agree spec is probably needed.15:55
armaxbut I wanted to give the opportunity to talk15:55
armaxbefore doing the state transition15:55
*** banix has quit IRC15:55
ihrachysit's a blocker for qos, sfc, bgpvpn. that's what we know so far.15:55
armaxto rfe-approved15:55
*** mbound_ has quit IRC15:55
armaxihrachys: yes we need to execute based on some of the discussions that happened on the summit too15:56
ihrachysbasically, features need access to br-int/br-tun and friends15:56
ihrachysand do it in l2 agent extensions15:56
*** garyk has quit IRC15:56
ihrachyswhich currently lack access to those bridges15:56
*** vijendar has joined #openstack-meeting15:56
yamamoto_ihrachys: tap-as-a-service will likely want to use it too15:56
armaxif many efforts do rely on the ovs agents for delivering functionality15:56
ihrachysso there is a plan to provide extensions with per agent type API objects that will expose some agent details without exposing too much15:56
armaxit’s only fair to provide some extensibility mechanism15:56
ajoihrachys , wouldn't a devref be more appropriate?15:57
armaxeven though I fundamentally believe there’s a better more radical way to dealing with this15:57
ihrachyswe have etherpad and some oral tales about how it will look like. I need spec/devref to document / notify folks15:57
ajoit's not a user facing feature, but an implementer feature/api15:57
armaxajo: it could be both :)15:57
ihrachysajo: I am fine with devrefs. I like them.15:57
*** irenab has quit IRC15:57
ihrachyslet's do both and steal from spec to devref15:58
ihrachysunless someone is against extensions, we can move15:58
ihrachysI gues15:58
ajothat's fine too :) as long as we end with a good documentation for developers, and make it clear it has to be an stable api :)15:58
armax2 mins left15:59
shzi have one #146823615:59
armaxI’ll capture the latest discussion on teh bug reports we talked about15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Dec  1 15:59:24 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-12-01-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-12-01-15.00.txt15:59
amotokiI will followup rtheis's client RFE.15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-12-01-15.00.log.html15:59
ihrachysshz: will need to wait for the next week I guess15:59
*** mlavalle has left #openstack-meeting15:59
*** harlowja_at_home has quit IRC15:59
ajoshz: ask armax to priorize it for the next one :)15:59
kevinbentonshz: we're going in order of creation time now so we'll eventually get there15:59
shzok, i got it16:00
ajokevinbenton ahh :)16:00
ajoarmax , kevinbenton , btw , jlibosva making advance on the OVS firewall thing16:00
*** markvoelker has joined #openstack-meeting16:00
ajowe've managed to get it more prioritized :)16:00
*** n0ano has joined #openstack-meeting16:01
kevinbentonajo: cool!16:01
ajobut eventually we're going to face the ubuntu distro not shipping the latest ovs bits,16:01
kevinbentonajo: yeah, just need to make sure we can configure using the firewall_driver option16:01
ajoI wonder if we could do like OVN and install OVS from sources to an specific version (like we do with pip and requirements..)16:01
*** nadya_ has quit IRC16:03
*** mbound_ has joined #openstack-meeting16:03
*** achanda has joined #openstack-meeting16:03
*** achanda has quit IRC16:03
*** nadya_ has joined #openstack-meeting16:03
*** jschwarz_ has joined #openstack-meeting16:04
*** wshao has joined #openstack-meeting16:04
*** egallen has left #openstack-meeting16:04
*** aranjan has joined #openstack-meeting16:04
*** rcernin has quit IRC16:04
*** egallen has joined #openstack-meeting16:04
*** kebray has joined #openstack-meeting16:05
*** jschwarz has quit IRC16:06
*** cbits has left #openstack-meeting16:07
*** nadya_ has quit IRC16:07
*** dims_ has joined #openstack-meeting16:08
*** neiljerram has joined #openstack-meeting16:08
*** FallenPegasus has joined #openstack-meeting16:08
*** vikram has quit IRC16:08
*** sputnik13 has joined #openstack-meeting16:09
*** changbl has joined #openstack-meeting16:09
*** dims has quit IRC16:10
*** IgorYozhikov has quit IRC16:10
*** achanda has joined #openstack-meeting16:11
*** kzaitsev_ws has quit IRC16:11
*** sdake has joined #openstack-meeting16:11
*** dteselkin has quit IRC16:11
*** akuznetsova has quit IRC16:11
*** jruano has quit IRC16:12
*** kzaitsev_ws has joined #openstack-meeting16:13
*** aranjan has quit IRC16:14
*** nmagnezi has quit IRC16:15
*** numans has quit IRC16:15
*** kebray has quit IRC16:16
*** IgorYozhikov has joined #openstack-meeting16:18
*** pots2 has joined #openstack-meeting16:19
*** akuznetsova has joined #openstack-meeting16:19
*** pots2 has quit IRC16:20
*** alexschm has quit IRC16:20
*** pots has quit IRC16:21
*** dprince has quit IRC16:25
*** apoorvad has joined #openstack-meeting16:25
*** john-davidge has quit IRC16:26
*** dteselkin has joined #openstack-meeting16:27
*** changbl has quit IRC16:27
*** kebray has joined #openstack-meeting16:28
*** kebray has quit IRC16:28
*** yamamoto_ has quit IRC16:28
*** kebray has joined #openstack-meeting16:28
*** spzala has joined #openstack-meeting16:29
*** dims has joined #openstack-meeting16:30
*** roxanaghe has joined #openstack-meeting16:30
*** sdake has quit IRC16:30
*** john-davidge has joined #openstack-meeting16:32
*** john-davidge has quit IRC16:32
*** dims_ has quit IRC16:33
*** FallenPegasus is now known as MarkAtwood16:34
*** roxanaghe has quit IRC16:35
*** lblanchard has joined #openstack-meeting16:36
*** p0rtal has joined #openstack-meeting16:39
*** sacharya has joined #openstack-meeting16:39
*** otter768 has joined #openstack-meeting16:40
*** changbl has joined #openstack-meeting16:42
*** dprince has joined #openstack-meeting16:43
*** otter768 has quit IRC16:45
*** vishwanathj has joined #openstack-meeting16:47
*** sgundur has quit IRC16:47
*** sgundur has joined #openstack-meeting16:48
*** dmowrer has quit IRC16:49
*** arcee_ has quit IRC16:49
*** fawadkhaliq has quit IRC16:50
*** bobh has joined #openstack-meeting16:51
*** arvinchou_ has joined #openstack-meeting16:51
*** alop has joined #openstack-meeting16:51
*** vahidh has joined #openstack-meeting16:51
*** arvinchou_ has quit IRC16:52
*** arvinchou_ has joined #openstack-meeting16:53
*** amuller is now known as amuller_afk16:53
*** sripriya has joined #openstack-meeting16:55
*** amotoki has quit IRC16:55
*** mbound_ has quit IRC16:55
*** matrohon has joined #openstack-meeting16:56
*** sdake has joined #openstack-meeting16:57
*** xek_ has joined #openstack-meeting16:57
*** houming has quit IRC16:58
*** kjorgensen has joined #openstack-meeting16:58
*** mbound_ has joined #openstack-meeting16:59
*** hemnafk is now known as hemna16:59
*** afv has joined #openstack-meeting16:59
*** baoli has quit IRC17:00
*** kebray has quit IRC17:00
*** haomaiwa_ has quit IRC17:00
*** matrohon has quit IRC17:01
*** wshao has quit IRC17:01
*** brucet has joined #openstack-meeting17:01
*** afv has quit IRC17:02
*** baoli has joined #openstack-meeting17:02
*** kjorgensen has quit IRC17:02
*** scinawa has joined #openstack-meeting17:02
*** kjorgensen has joined #openstack-meeting17:02
*** brucet has quit IRC17:03
*** brucet has joined #openstack-meeting17:03
*** rajinir_ has joined #openstack-meeting17:03
*** banix has joined #openstack-meeting17:04
*** masterbound has joined #openstack-meeting17:04
*** xyang1 has joined #openstack-meeting17:05
*** kebray has joined #openstack-meeting17:05
*** arvinchou_ has quit IRC17:06
*** dmowrer has joined #openstack-meeting17:06
*** jschwarz__ has joined #openstack-meeting17:06
*** mrmartin has joined #openstack-meeting17:07
*** jlanoux has quit IRC17:07
*** mrunge has quit IRC17:07
*** mbound_ has quit IRC17:08
*** jschwarz_ has quit IRC17:10
*** mrunge has joined #openstack-meeting17:10
*** brucet has quit IRC17:11
egonajo: That's not a bad idea, because it can be such a critical piece of the infrastructure. You need to make sure you have the right kernel, though.17:11
*** brucet has joined #openstack-meeting17:12
*** sgundur has quit IRC17:12
*** sgundur has joined #openstack-meeting17:13
*** pots has joined #openstack-meeting17:13
*** gyee has joined #openstack-meeting17:14
*** mudassirlatif has joined #openstack-meeting17:15
*** yamahata has joined #openstack-meeting17:15
*** rossella_s has quit IRC17:15
*** aspiers has quit IRC17:16
*** Swami has joined #openstack-meeting17:16
*** purp has quit IRC17:16
*** ricolin has quit IRC17:17
*** s3wong has joined #openstack-meeting17:18
*** purp has joined #openstack-meeting17:19
*** nelsnelson has joined #openstack-meeting17:20
*** ildikov has quit IRC17:20
*** mrmartin has quit IRC17:21
*** egallen has quit IRC17:21
*** egallen_ has joined #openstack-meeting17:21
*** garyk1 has quit IRC17:21
*** mrmartin has joined #openstack-meeting17:22
*** fawadkhaliq has joined #openstack-meeting17:22
*** brucet has quit IRC17:23
*** leeantho has joined #openstack-meeting17:24
*** brucet has joined #openstack-meeting17:24
*** doug-fish has joined #openstack-meeting17:25
*** stevemar_znc is now known as stevemar17:25
*** yfried has quit IRC17:26
*** ayoung has quit IRC17:28
*** ygbo has quit IRC17:28
*** jschwarz__ has left #openstack-meeting17:28
*** e0ne has quit IRC17:30
*** roxanaghe has joined #openstack-meeting17:31
*** pots has quit IRC17:31
*** scheuran has quit IRC17:32
*** pballand has joined #openstack-meeting17:33
*** roxanaghe has quit IRC17:35
*** sgundur has quit IRC17:36
*** krtaylor has quit IRC17:37
*** hashar has quit IRC17:37
*** nadya_ has joined #openstack-meeting17:37
*** masterbound has quit IRC17:37
*** nadya_ has quit IRC17:37
*** nadya_ has joined #openstack-meeting17:38
*** nadya_ has quit IRC17:38
*** nadya_ has joined #openstack-meeting17:39
*** janonymous has joined #openstack-meeting17:41
*** dzamboni has quit IRC17:43
*** pm90__ has quit IRC17:43
*** bswartz has joined #openstack-meeting17:43
*** aranjan has joined #openstack-meeting17:44
*** yamahata has quit IRC17:44
*** shashank_hegde has joined #openstack-meeting17:44
*** achanda has quit IRC17:45
*** nadya_ has quit IRC17:46
*** gr720e has joined #openstack-meeting17:46
*** vahidh has quit IRC17:47
*** egallen has joined #openstack-meeting17:50
*** egallen_ has quit IRC17:50
*** toscalix has quit IRC17:50
*** achanda has joined #openstack-meeting17:52
*** klkumar has quit IRC17:52
*** sgundur has joined #openstack-meeting17:54
*** lhcheng_ has joined #openstack-meeting17:56
*** mhickey_ has joined #openstack-meeting17:56
*** sudipto has quit IRC17:58
stevemarkeystone time!17:59
*** shaleh has joined #openstack-meeting17:59
stevemarkeystoners assemble!17:59
*** mhickey_ has quit IRC17:59
stevemarcourtesy ping for 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, MaxPC, tjcocozz18:00
stevemarahoy hoy18:00
*** notmorgan has joined #openstack-meeting18:00
*** haneef has joined #openstack-meeting18:00
*** breton has joined #openstack-meeting18:00
stevemarlets get the show on the road!18:01
stevemar#startmeeting keystone18:01
openstackMeeting started Tue Dec  1 18:01:16 2015 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
stevemaragenda: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
*** ayoung has joined #openstack-meeting18:01
lbragstadstevemar o/18:01
*** sdake has quit IRC18:01
stevemari'm guessing the agenda is light since most folks saw my mailing list post18:01
*** henrynash has joined #openstack-meeting18:01
*** kebray has quit IRC18:02
*** krtaylor has joined #openstack-meeting18:02
stevemarmitaka-1 is ending, i wanted to have a roll call on the specs, make sense?18:02
*** amakarov has joined #openstack-meeting18:02
*** ayoung_ has joined #openstack-meeting18:02
stevemarthis way we don't have to file FFE at the beginning of mitaka-218:02
lbragstadstevemar it doesn't just make sense... it makes dollars...18:02
bknudsonwhat's a roll call on specs?18:02
* lbragstad wins pun-of-the-day award18:02
dolphmbknudson: basically to make sure there's someone here to champion each spec18:02
bknudsona spec needs a champion and 2 core reviewers to get merged18:03
stevemarbknudson: dolphm and to make sure we have a majority of support18:03
*** sripriya has left #openstack-meeting18:03
*** ayoung has quit IRC18:03
*** ayoung_ is now known as ayoung18:03
* notmorgan lurks but refuses to commit to more than lurking18:03
stevemarbknudson: 2 cores may not have the same opinion as the rest :P18:03
* gyee make sure his magic 8 ball still works18:04
ayoungShould we vote on the remaining short list to see if we are OK with them?18:04
stevemarayoung: there's also that18:04
stevemarthe intention is to and speed up the process in getting specs merged18:04
ayoungstevemar, I missed the link you had with the short list18:04
ayoungor shoudl we go by gerrit?18:04
* topol lbragstad is someone I have huge respect for... But his puns are terrible18:04
bknudsondo we have the review bandwidth to take on any more work?18:05
*** amuller_afk is now known as amuller18:05
lbragstadtopol :)18:05
*** derekh has quit IRC18:05
stevemarayoung: the ones i want to bring up are here: http://paste.openstack.org/show/480545/18:05
ayounghttps://review.openstack.org/#/c/240595/  Shadow users is, to me, the most importanat outstanding spec.18:05
stevemarbknudson: it's more about targeting18:05
marekdayoung: ++18:05
ayoungits got an array of -1s, and a +2 from stevemar18:06
*** davechen1 has joined #openstack-meeting18:06
topolayoung, I saw that...18:06
topolmade me notwant to review :-)18:06
shalehayoung: ++18:06
stevemarayoung: i was going to set the topic and vote for each one18:06
*** sdake has joined #openstack-meeting18:06
lbragstadi believe ron is planning on picking that spec up.. and/or respinning it18:07
bknudsonI don't think we should be targeting to m when we don't have the review bandwidth for it to land in m18:07
*** e3du5 has joined #openstack-meeting18:07
*** brucet has quit IRC18:07
*** p0rtal has quit IRC18:07
marekdbknudson: bandwidth was good (look at the number of reviews), response time not really :(18:07
*** unicell has joined #openstack-meeting18:07
marekdbknudson: wrt shadow users18:07
ayoungstevemar, vote away, please18:07
stevemarbknudson: we currently have 6 reviews targeted for all of M http://specs.openstack.org/openstack/keystone-specs/#identity-program-specifications18:07
bknudsony, looks like the submitter has abandoned shadow users.18:08
topolstevemar what is the vote for?18:08
bretonsubmitter abandoned shadow users???18:08
marekdlbragstad: ^^ beware, you have a competitor for today's pun-of-a-day contest :P18:08
*** ivar-lazzaro has joined #openstack-meeting18:08
marekdbreton: it was a joke18:08
henrynashok, let’s get to it…..8  minutes gone18:08
stevemartopol: the vote is for "do we want this to appear in M"18:08
topolgot it18:09
stevemarhenrynash: it's the first time doing this, i expect questions18:09
*** aimon has quit IRC18:09
stevemar#startvote Target "Shadow users: unified identity" to Mitaka? Yes, No, Abstain18:09
openstackBegin voting on: Target "Shadow users: unified identity" to Mitaka? Valid vote options are Yes, No, Abstain.18:09
openstackVote using '#vote OPTION'. Only your last vote counts.18:09
ayoungvote yes18:09
lbragstad#vote yes18:09
stevemar#vote Yes18:09
marekdstevemar: in a shape "as is" ?18:09
*** bobh has quit IRC18:09
ayoung#vote Yes18:09
dstanek#vote yes18:09
shaleh#vote yes18:09
gyee#vote Yes18:09
breton#vote yes18:09
notmorgan#vote abstain18:10
lhcheng_#vote yes18:10
topol#vote yes18:10
marekd#vote Yes18:10
dolphm#vote yes18:10
bknudson#vote Abstain18:10
henrynash#vote Abstain18:10
davechen1#vote Abstain18:10
*** bobh has joined #openstack-meeting18:10
davechen1since i didn't get a chance to take a look18:10
stevemarmarekd: not necessarily in it's current shape, but a yes means it's important to project plans and we'll help it out if it's not in good shape18:10
ayoungmarekd, to answer your question, I would say " if it went in as is, things would be ok, but we can still submit minro tweaks to the spec until M218:10
*** brucet has joined #openstack-meeting18:10
stevemarayoung: yes, i think you understand the intention i'm trying for here18:11
marekdstevemar: oh, yes, so it's important. just need somebody to take care of it. dolphm, i though you were going to do it.18:11
bknudsonI'm not sure why the vote... all it should require is for 2 cores and owner to sign up to get it done for M.18:11
stevemarbknudson: 2 does not reflect the majority18:11
dolphmmarekd: only championing it18:11
*** yamahata has joined #openstack-meeting18:11
bretonbknudson: because there will be a freeze this week and we want to know which patches not to freeze18:11
bretonI guess18:11
dstanekbknudson: want to make sure that there is no reason not to do it18:11
ayoungput my +2 on it.  Anyone daring enough to +A is welcome to do so18:11
topolstevemar, is  this  a prioritization effort?18:12
stevemarbknudson: if tis is a pointless exercise we'll find out in 48 minutes :)18:12
stevemardstanek: ++18:12
stevemartopol: yes18:12
openstackVoted on "Target "Shadow users: unified identity" to Mitaka?" Results are18:12
openstackYes (11): gyee, dstanek, ayoung, marekd, shaleh, lbragstad, dolphm, topol, lhcheng_, breton, stevemar18:12
openstackAbstain (4): henrynash, bknudson, davechen1, notmorgan18:12
*** lhcheng_ is now known as lhcheng18:12
*** vahidh has joined #openstack-meeting18:12
marekdallright, how about everbody take a look at https://review.openstack.org/#/c/188534 ?18:12
*** eduardo___ has quit IRC18:13
*** ivar-lazzaro has quit IRC18:13
stevemarmarekd: the list is here: http://paste.openstack.org/show/480545/18:13
*** neelashah has quit IRC18:13
shalehmarekd: I supprt the idea, not sold on the current solution18:13
henrynashlet’s let stevemar drive the list here18:13
*** ivar-lazzaro has joined #openstack-meeting18:13
stevemaralright, next one18:13
marekdshaleh: so, review :-)18:13
*** kebray has joined #openstack-meeting18:13
stevemar#startvote Target "Domain Specific Roles" to Mitaka? Yes, No, Abstain18:13
openstackBegin voting on: Target "Domain Specific Roles" to Mitaka? Valid vote options are Yes, No, Abstain.18:13
openstackVote using '#vote OPTION'. Only your last vote counts.18:13
marekd#vote yes18:13
notmorgan#vote abstain18:14
ayounghenrynash, do you think you can accomplish this in Mitaka?18:14
gyee#vote on the fence18:14
openstackgyee: on the fence is not a valid option. Valid options are Yes, No, Abstain.18:14
henrynashayoung: abolutely18:14
*** davechen1 is now known as davechen18:14
*** jckasper has quit IRC18:14
ayoung#vote Yes18:14
raildo#vote yes18:14
gyeeI like the idea, but not the design18:14
bknudson#vote Abstain18:14
davechen#vote abstain18:14
gyee#vote abstain18:14
lbragstad#vote abstain18:14
lhcheng#vote abstain18:14
topol#vote yes18:14
dstanek#vote abstain18:14
ayounggyee, I think it is a subset of what we will have eventually, and, to be honest, needs HMT to be truely useful, but will be a good step forward18:14
breton#vote abstain18:14
notmorgannot sure, is this vote the "design is ok as well"?18:14
notmorgancause if the idea is this is "close-ish" then i would say "vote no" if you don't like the design18:15
henrynash: #vote I’m not voting, since you shouldn;t vote for your own proposal18:15
stevemar#vote yes18:15
htruta#vote Yes18:15
*** nmagnezi has joined #openstack-meeting18:15
stevemarmy vote is more of a yes-ish18:15
gyeethe design is confusing from UX standpoint18:15
*** ivar-lazzaro has quit IRC18:15
stevemarwith gyee, i like the idea18:15
dolphm#vote yes18:15
*** manjeets has quit IRC18:15
david8hu#vote abstain18:15
dolphmthis is one of those things i get asked about on a regular basis18:16
henrynashgyee: originally we had two different APIs, everyone said…NO…combine with imlied roles…so I dod18:16
notmorganhenrynash: who is asking?18:16
*** sdake has quit IRC18:16
stevemardolphm: can you elaborate?18:16
*** ivar-lazzaro has joined #openstack-meeting18:16
notmorganhenrynash: who is the driving force behind that request?18:16
openstackYes (7): ayoung, marekd, htruta, topol, dolphm, raildo, stevemar18:16
henrynashnotmorgan: for domain roles? sever al customers18:17
openstackAbstain (9): gyee, lbragstad, notmorgan, lhcheng, bknudson, dstanek, david8hu, davechen, breton18:17
notmorganhenrynash: like "this would be nice" or "OMG WE MUST HAVE"?18:17
dolphmstevemar: i get questions about why roles aren't owned by domains, why domain administrators aren't able to write their own policy, etc18:17
notmorganhenrynash: i'm trying to get a read on this18:17
ayounghenrynash, any last changes you want to make before I +A?18:17
henrynashayoung: no18:17
henrynashno changes18:17
*** kebray has quit IRC18:17
stevemarayoung: hold off on +A'ing until after please18:17
ayoungtoo late18:18
henrynashnotmorgan: it’s someone peopel are strating to hit…as we grow our public cloud18:18
openstackVoted on "Target "Domain Specific Roles" to Mitaka?" Results are18:18
openstackYes (7): ayoung, marekd, htruta, topol, dolphm, raildo, stevemar18:18
openstackAbstain (9): gyee, lbragstad, notmorgan, lhcheng, bknudson, dstanek, david8hu, davechen, breton18:18
gyeewe are overloading the same APIs for implied roles, but those are NOT implied roles18:18
stevemarnotmorgan: i think ti's a real problem18:18
ayounggyee, yes they are18:18
notmorganstevemar: i blocked the merge btw18:18
notmorgani'll unblock it after meeting18:18
gyeethey don't get included in token response18:18
ayoungnotmorgan, thanks18:18
ayounggyee, implied roles *are* the ones that get into the token response.18:19
ayoungDomain specifi roles are explicit roles18:19
gyeeright, but not the domain specific roles18:19
*** gissi has joined #openstack-meeting18:19
gyeeso that's hard to explain from UX standpoint18:19
ayoung...actually, I just realized that they don't need to be...you could have a domain-specific-implicit-role18:19
*** ildikov has joined #openstack-meeting18:19
ayounghenrynash, ^^ make sure that we don't mess that up, OK?18:19
gyeeusing the same API, but behave differently18:19
stevemarsounds like there is still some confusion here henrynash and ayoung18:19
stevemar#todo henrynash and ayoung to convince notmorgan and gyee in -keystone18:20
ayoungstevemar, just a realization that there is something subtle to not mess up in henrynash 's implementation18:20
stevemarhash it out, but not here18:20
stevemarnext one18:20
henrynashstevemar: so with 7 cores voting yes and no NOs we aren;t done?18:20
shalehayoung: we have a lot of subtle. We should work harder at explicit18:20
*** shashank_hegde has quit IRC18:20
henrynashthat be a high bar we are setting18:21
bknudsonwith 7 people signing up to get it done that should be good enough18:21
stevemarhenrynash: i'll look at the result in the meeting logs18:21
bknudsonwork out the details in the reviews18:21
stevemarbknudson: yes18:21
stevemarnext one18:21
stevemar#startvote Target "Enable retrieval of default values of domain config options" to Mitaka? Yes, No, Abstain18:21
openstackBegin voting on: Target "Enable retrieval of default values of domain config options" to Mitaka? Valid vote options are Yes, No, Abstain.18:22
lbragstad#link https://review.openstack.org/#/c/185650/18:22
openstackVote using '#vote OPTION'. Only your last vote counts.18:22
gyeeI absolutely for the idea of domain-specific roles, just need to make it usable18:22
stevemar#vote yes18:22
stevemari think this is an easy one18:22
bknudson#vote Abstain18:22
marekd#vote abstain18:22
dolphm#vote abstain18:22
davechen#vote abstain18:22
gyee#vote yes18:22
lbragstad#vote abstain18:22
notmorgan# #vote i'dvotenobutidon'thaveagoodalternativeanswer18:22
*** aranjan has quit IRC18:22
gyeeI like templates better, but hey, baby steps right18:22
*** vishwana_ has joined #openstack-meeting18:22
dstaneki like the idea, but i'm not sure i like the impl described18:23
ayoungthis one mine?18:23
lhcheng#vote abstain18:23
stevemarayoung: no, henrynash's18:23
david8hu#vote abstain18:23
*** aranjan has joined #openstack-meeting18:23
stevemargetting the default configuration from /domain-config18:23
notmorganlike, i kinda want to vote no, but without an alternative to present... -- i can't even in good concience vote abstain18:23
*** brucet has quit IRC18:23
topol#vote yes18:23
ayoung#vote yes18:23
stevemarsounds like there is work to do here18:24
dstanek#vote yes18:24
openstackVoted on "Target "Enable retrieval of default values of domain config options" to Mitaka?" Results are18:24
openstackYes (4): gyee, ayoung, topol, stevemar18:24
openstackAbstain (7): lbragstad, lhcheng, bknudson, marekd, david8hu, dolphm, davechen18:24
*** vishwanathj has quit IRC18:24
dstanekif we can fix the API18:24
stevemardstanek comment on the spec with your concerns18:24
shalehthe review is all positive currently18:24
dstanekstevemar: will do18:24
henrynashdstanek: yep happy to work with you18:24
ayoungOK...if any of you abstaining cowards want to hold this up, -2 it now or live with it18:24
stevemarhenrynash: you are creating as many specs as ayoung!18:24
stevemar#startvote Target "Allow url-safe project and domain names to be optionally enforced" to Mitaka? Yes, No, Abstain18:24
openstackBegin voting on: Target "Allow url-safe project and domain names to be optionally enforced" to Mitaka? Valid vote options are Yes, No, Abstain.18:24
openstackVote using '#vote OPTION'. Only your last vote counts.18:24
lbragstad#link https://review.openstack.org/#/c/248083/18:25
shaleh#vote yes18:25
ayoungstevemar, we've lived with the same broken windows for the same length of time18:25
notmorganayoung: see my previous statement. i wont block it cause i really can't offer something better18:25
henrynashone has to aim high, right?18:25
davechen#vote yes18:25
ayoungwell, I've been here marginally longer, but...18:25
dolphmlbragstad: thank you18:25
*** bobh has quit IRC18:25
bknudson#vote Abstain18:25
topol#vote Abstain18:25
dolphm#vote yes18:25
lhcheng#vote yes18:25
gyee#vote yes18:25
dstanek#vote yes18:25
lbragstad#vote yes18:25
notmorganhenrynash: is unicode/utf-8 handled here?18:25
ayoung#vote yes-but-I-am-a-coauthor18:25
openstackayoung: yes-but-I-am-a-coauthor is not a valid option. Valid options are Yes, No, Abstain.18:25
notmorganbefore i vote?18:25
*** arcee has joined #openstack-meeting18:26
ayoungnotmorgan, no18:26
notmorgan#vote no18:26
ayoungnotmorgan, we are saying to start just alpha-num18:26
shalehnotmorgan: I called it out in my review18:26
marekd#vote yes18:26
notmorganthat's fine.18:26
ayoungwe start off strict, make less strict over time18:26
notmorgani'm happy to be a dissenter here18:26
bretonyay, the first one "no" for today18:26
ayoungnotmorgan, you would say yes if it accepted unicode?18:26
stevemarnotmorgan: is that your only concern18:26
*** manjeets has joined #openstack-meeting18:26
notmorganstevemar: that is my only concern18:26
stevemar#vote yes18:26
notmorganmany deployments use unicode/utf-818:26
shalehnot allowing users to use umlauts is a pretty big deal18:27
*** edtubill has quit IRC18:27
*** sputnik13 has quit IRC18:27
*** maishsk has quit IRC18:27
bknudsonDNS doesn't support umlauts as far as I know18:27
*** brucet has joined #openstack-meeting18:27
stevemardamn umlauts18:27
notmorganand i don't want us to start on a path that relies on url-safe w/o that included18:27
shalehBUT, users with unicode can choose not to enable thise18:27
marekdbknudson: i think it does support special chars18:27
notmorganso, interop will suck.18:27
bknudsonyou'd have to do punycode or whatever.18:27
*** jichen has joined #openstack-meeting18:27
notmorganthis is an end-user impacting thing as well.18:27
ayoungnotmorgan, we are talking about using this to create URLs18:27
ayoungso, the end result needs to be passed, as is, into the URL18:28
*** neelashah has joined #openstack-meeting18:28
notmorganayoung: and afaict this is backwards incompat18:28
ayoungan umlauted chracter can be escaped and used that way, its just not what Keystone would store18:28
ayoungNo it does not18:28
ayoungit is a optional feature for moving forward18:28
notmorganexcept if we *have* this we will build on it18:28
ayoungit explicitly is opt in, and for netst projects to be built into an URL scheme18:28
notmorganand it will become defacto-required for other things18:28
notmorganso, i stand by the #no until that is addressed18:29
ayoungnotmorgan, it is addressed18:29
notmorganlike i said, i am happy to be the dissenter here18:29
dolphmwhy not just make the regex configurable, and default it to something relaxed. we can recommend a very strict regex, and people can write regex that accepts unicode if they want.18:29
notmorgani wont -2 block it18:29
ayoungthe same way you would have it in an exisint URL18:29
ayoungdolphm, same reason:18:29
ayoungwhat gets saved has to be composable into a nesting , HTTP safe URL scheme18:29
* notmorgan stands by this. but again, wont -2 or hard block it.18:30
shalehso the user at some point will need to use %843 or the like18:30
dstanekthis reminds be of blogging software that have a name for a post and also a slug that is url safe18:30
ayoungthe idea is that, in the future, we will do OS_PROJECT_DOMAIN_NAME=a/b/c/d  and that becomes https://hostname/keystone/v3/domains/a/b/c/d18:30
*** unicell has quit IRC18:30
shalehdstanek: agreed18:30
*** egallen has quit IRC18:30
stevemarsounds like theres still some issues here too :(18:30
ayoungso...a utility to make sure that a non -url safe one becoems URL safe would be fine18:30
openstackVoted on "Target "Allow url-safe project and domain names to be optionally enforced" to Mitaka?" Results are18:31
openstackYes (9): gyee, dstanek, lhcheng, davechen, marekd, shaleh, lbragstad, dolphm, stevemar18:31
openstackAbstain (2): bknudson, topol18:31
openstackNo (1): notmorgan18:31
ayoungbut we need to ensure the post-processed value is URL safe.18:31
notmorganclearly addressing this for end-user interop as well as deployments moving forward is important.18:31
shalehnotmorgan: ++18:31
stevemarso though overwhelmingly yes, we should address the concerns in the specs18:31
shalehusers will complain18:31
gyeeyes understood, interop is important18:31
notmorganso i stand by my dissent. feel free to approve if you wish to override it.18:32
dstanekthat's the way i do it when writing similar things in django18:32
stevemar7 more to go!18:32
stevemar#startvote Target "Public/Private IdPs" to Mitaka? Yes, No, Abstain18:32
shalehwe aint gonna make it18:32
openstackBegin voting on: Target "Public/Private IdPs" to Mitaka? Valid vote options are Yes, No, Abstain.18:32
openstackVote using '#vote OPTION'. Only your last vote counts.18:33
lbragstad#link https://review.openstack.org/#/c/209941/18:33
ayoung#vote no18:33
marekd#vote yes18:33
stevemarthanks for the links lbragstad18:33
stevemar#vote yes18:33
ayoungI am not going to implement18:33
stevemarpending we can get resources....18:33
*** yamahata has quit IRC18:33
marekdayoung: why?18:33
*** DavidGF has joined #openstack-meeting18:33
shalehI am willing to work on it, but the current spec needs a lot of love18:33
bknudson#vote abstain18:33
ayoungmarekd, I don't have the time or the driving need to.18:33
marekdshaleh: so go for it!18:33
gyee#vote abstain18:33
marekdayoung: fair enough18:33
dolphm#vote yes18:33
gyeethat spec needs a lot of work18:33
shalehI'd like to see if we can work this together with marek's proposal for SP18:33
topol#vote abstain18:33
lhcheng#vote abstain18:34
davechen#vote abstain18:34
dstanek#vote yes18:34
dolphmthere's a totally valid problem to be solved here18:34
ayounglets approve in backlog, and, if we get it done,  great18:34
stevemardolphm: yep18:34
dolphmgyee: agree18:34
shalehayoung: ++18:34
notmorgan#vote no18:34
ayoungagreed, which is why I did not abandon it18:34
stevemari'm okay with this going to backlog18:34
topoldolphm, agree but the spec needs work18:34
notmorganmy no is "the spec feels like it is missing a lot"18:34
henrynash#vote no18:34
notmorgannot because i dislike the idea18:34
dstanekwho will actually implement it?18:34
shalehnotmorgan: you are not wrong18:34
topolwhat notmorgan said18:34
*** garyk has joined #openstack-meeting18:34
henrynash(based on spec needs much more work)18:34
ayoungshaleh, you want to take it over, just leave me on as co-author and it is yours18:34
shalehdstanek: if we can get the spec hammered out I should be able to help18:34
stevemarit's also missing API changes18:35
dolphmwhoever implements this needs to start by taking over the spec18:35
stevemar#vote no18:35
stevemardolphm: yeah18:35
ayoungif you can get it into shape by friday, and commit to implementing it in mitaka, I will gladly let it go forward18:35
lbragstad#vote abstain18:35
shalehstevemar: is that no becuase the current spec sucks or no because the idea is wrong?18:35
gyeedolphm, I think shaleh wants to volunteer :)18:35
*** unicell has joined #openstack-meeting18:35
stevemarshaleh: the idea is pretty easy, we've had it around for a while18:35
shalehno, spec hammered out by Friday is not happening18:35
shalehsimple as that18:35
bretonwhy do we vote for it? It's targeted to the backlog.18:35
ayoungok, then backlog it for now18:35
shalehthis spec is reallty too simplistic18:35
*** unicell has quit IRC18:36
*** yamahata has joined #openstack-meeting18:36
*** whenry_ has quit IRC18:36
*** unicell1 has joined #openstack-meeting18:36
stevemaroh shoot, i didn't mean to include backlog specs18:36
openstackVoted on "Target "Public/Private IdPs" to Mitaka?" Results are18:36
openstackYes (3): dstanek, dolphm, marekd18:36
openstackAbstain (6): gyee, lbragstad, lhcheng, davechen, topol, bknudson18:36
openstackNo (4): henrynash, ayoung, notmorgan, stevemar18:36
shalehmarekd: sync up with me afterwards18:36
ayoungcan we do Make keystone fully fledged SAML2 Service Provider  last18:36
stevemarayoung: yes18:36
ayoungI think that will have some discussion18:36
stevemar#startvote Target "Expand endpoint filters to service providers" to Mitaka? Yes, No, Abstain18:36
openstackBegin voting on: Target "Expand endpoint filters to service providers" to Mitaka? Valid vote options are Yes, No, Abstain.18:36
openstackVote using '#vote OPTION'. Only your last vote counts.18:36
lbragstad#link https://review.openstack.org/#/c/188534/18:36
lbragstadI think the idea is fine, most of my comments were nits18:37
stevemari'd be happy to review this one18:37
ayoungdoes anyone have a strenuous objection to this one?18:37
*** vishwana_ has quit IRC18:37
*** ssancheztrujillo has joined #openstack-meeting18:37
*** dmowrer has quit IRC18:37
bknudson#vote abstain18:37
lbragstadi don't think it needs to be it's entirely own API though18:37
stevemari think there is concern about the fact that 'service providers' aren't in the catalog to begin with18:37
*** baoli has quit IRC18:37
shalehI am not sold on wedging it into endpoint filter18:37
*** rcernin has joined #openstack-meeting18:37
marekdlbragstad: it is not...18:37
*** eharney_ has joined #openstack-meeting18:37
*** bobh has joined #openstack-meeting18:38
marekdshaleh: lol, last time stevemar advised on extending OS-EP-FILTER18:38
notmorganthis needs to happen somehow.18:38
notmorgani think18:38
marekdnotmorgan: yes.18:38
notmorganbut how, i don't really care.18:38
dstanekshaleh: ++18:38
notmorganso i fthis is the best way, we do it this way18:38
ayoungHow do we list Service providers now?  Its a deliberate API call, right?18:38
lbragstad#vote abstain18:38
marekdayoung: no, it's in the token response18:38
*** eharney has quit IRC18:38
lbragstadonly because I don't have very many suggestions on how to fix it18:38
ayoungoh..then this is the right way18:38
*** baoli has joined #openstack-meeting18:39
breton#vote abstain18:39
henrynash#vote yes18:39
ayoungah...is it becasue we consider that p[ortion of the token response "not the service catalog" that this is up for debate?18:39
marekdayoung: it's in the token response, not in the service catalog. that's why it's not a pure reuse of endpoint filtering, rather extension.18:39
davechen#vote abstain18:39
stevemarayoung: yep18:39
topol#vote yes18:39
ayoung#vote yes18:39
gyeewe still have an issue to hash out18:39
shaleh#vote yes18:39
gyeedo we care about inheritance18:39
stevemargyee: it may be an implementation detail18:40
lhcheng#vote abstain18:40
gyeethat's an important one18:40
gyee#vote yes, only if we include inheritance18:40
openstackgyee: yes, only if we include inheritance is not a valid option. Valid options are Yes, No, Abstain.18:40
ayounggyee, does it effect the decisions on endpoint filtering?18:40
shalehmarekd: I would prefer it to have its own filter system or that we expand endpoint filter to be "filter things"18:40
dolphm#vote abstain18:40
*** Shrews has joined #openstack-meeting18:40
*** vishwanathj has joined #openstack-meeting18:40
gyeeayoung, it does, if we don't support inheritance, that's a big UX gap18:40
stevemarsounds like this may need some tweaking18:40
*** IlyaG has joined #openstack-meeting18:41
openstackVoted on "Target "Expand endpoint filters to service providers" to Mitaka?" Results are18:41
openstackYes (4): henrynash, shaleh, topol, ayoung18:41
openstackAbstain (6): lbragstad, lhcheng, bknudson, dolphm, davechen, breton18:41
marekdstevemar: like tweaking what?18:41
ayounggyee, is it something that can be solved during the dev process?18:41
gyeeSP usually tight to a domain/top level project18:41
gyeeayoung, no, we need to be clear on the API design18:41
*** otter768 has joined #openstack-meeting18:41
ayounggyee, but that is also the general case with Endpoint filtering18:41
stevemara few more to go18:41
*** galstrom_zzz is now known as galstrom18:41
stevemar#startvote Target "Online schema migration" to Mitaka? Yes, No, Abstain18:41
openstackBegin voting on: Target "Online schema migration" to Mitaka? Valid vote options are Yes, No, Abstain.18:41
openstackVote using '#vote OPTION'. Only your last vote counts.18:41
stevemarthis one is interesting18:41
lbragstad#link https://review.openstack.org/#/c/245186/18:41
marekd#vote abstain18:42
gyeeayoung, endpoint filter is per project, not domain18:42
xek_I'm championing it18:42
stevemari like the intention and xek_ seems to have the bandwidth18:42
davechen#vote Yes18:42
stevemarhi xek_!18:42
shaleh#vote abstain18:42
stevemar#vote yes18:42
henrynash#vote yes18:42
*** safchain has quit IRC18:42
stevemarit's well scoped and mostly tests that we don't shoot ourselves in the foot18:42
notmorganif there are enginerring resources comitted to it18:42
lbragstadI had a lot of questions on that spec18:42
notmorgani'm a stong yes for this18:42
lbragstadbut it looks like a new version was pushed,18:42
notmorganbut... i need to see commitment for the resources18:43
gyeelbragstad, yeah, that spec still need more work18:43
ayoungI like it, but he needs more lead time for discussion18:43
gyeeI can't comprehend most of it18:43
bknudson#vote abstain18:43
lbragstadif xek_ has the time, i'll be happy to review18:43
dstanekcan this actually be completed and reviewed this cycle?18:43
lbragstad#vote yes18:43
notmorganstevemar: is xek_ committed to make it a thing?18:43
xek_I have time18:43
gyee#vote abstain18:43
lhcheng#vote abstain18:43
ayoung#vote no18:43
*** neelashah1 has joined #openstack-meeting18:43
xek_I also want to help reviewing patchsets with schema changes18:43
stevemarnotmorgan: no idea, i have no idea who xek_ is :)18:43
topol#vote yes18:43
ayoungand submit it to back log18:43
gyeeplus, this is not a Keystone thing, this is a OpenStack thing18:44
notmorganstevemar: then i'm a no18:44
stevemarayoung: disagree, submitter is willing to do the work18:44
ayoungxek_, are you here?18:44
notmorgan#vote no18:44
gyeewhat good does it do we can only rolling upgrade Keystone18:44
bretonI am a little meh about it, especially for Mitaka18:44
xek_ayoung, yes18:44
notmorgangyee:  it is important18:44
dstanekstevemar: but will it be reviewed?18:44
davechenthe impl is just a testcase and the code is up for review. notmorgan18:44
notmorgangyee: no-downtime upgrade is good.18:44
ayoungxek_, you have a working impl already?18:44
stevemardstanek: sure, i'll review it18:44
gyeemy point is this needs to work holistically18:44
xek_breton, nova also supports it18:44
bknudsonnova and other projects already have rolling upgrade18:44
notmorgandavechen: that isn't clear from the spec to me18:44
notmorgandavechen: that it's really *ready to go*18:44
xek_ayoung, yes, the unit test is in review already18:44
*** aleksandr_null has quit IRC18:44
ayoung#vote Yes18:44
*** Leom has joined #openstack-meeting18:44
ayoungOK, we can do this18:44
notmorgani can change the vote.18:44
*** munish has quit IRC18:45
notmorgan#vote yes18:45
stevemarvote ending soon...18:45
notmorganIF we have resources comitted to making it happen18:45
openstackVoted on "Target "Online schema migration" to Mitaka?" Results are18:45
openstackYes (7): lbragstad, ayoung, notmorgan, davechen, topol, henrynash, stevemar18:45
notmorganearly in this cycle18:45
openstackAbstain (5): lhcheng, bknudson, gyee, marekd, shaleh18:45
stevemarbknudson clearly wants no new work this cycle :)18:45
bknudsonvoting yes means you're pledging resources to make it happen.18:45
xek_notmorgan, I have the resources :)18:45
*** neelashah has quit IRC18:45
ayoungnotmorgan, yeah, that was my concern, but I think this is a good thing...18:45
stevemar#startvote Target "Unified delegation spec" to Mitaka? Yes, No, Abstain18:45
openstackBegin voting on: Target "Unified delegation spec" to Mitaka? Valid vote options are Yes, No, Abstain.18:45
openstackVote using '#vote OPTION'. Only your last vote counts.18:45
stevemar#vote abstain18:45
marekd#vote abstain18:45
notmorganbknudson: nope. i'm voting yes as a "i'm a spec-core and think this is good"18:46
lbragstad#link https://review.openstack.org/#/c/189816/18:46
dstaneki'm a little worried about the cruft that will accumulate18:46
lbragstad#vote abstain18:46
*** otter768 has quit IRC18:46
notmorgan#vote abstain18:46
stevemari am woefully uneducated about this spec, and that's my fault18:46
topolnotmorgan +++18:46
notmorgani really don't have enough info to weigh in18:46
ayoungI think, also, that our migrations are mature enough we should not be hitting too many column drops.  Being safe about them is sane18:46
davechen#vote abstain18:46
dstanek#vote abstain18:46
bretonstevemar: it is targeted to backlog18:46
lhcheng#vote abstain18:46
bknudson#vote abstain18:46
*** shashank_hegde has joined #openstack-meeting18:46
stevemarbreton: thanks!18:46
ayoung#vote Yes18:46
henrynash#vote no18:46
topol#vote abstain18:46
breton#vote abstain18:47
notmorganjust end the vote if it's backlog and lets move on18:47
*** aleksandr_null has joined #openstack-meeting18:47
henrynash(baed on spec needs too much work)18:47
ayoungnotmorgan, it was submitted to backlog a while back, but he's been working on it for two releases now18:47
stevemarbreton: and it's showing... looks like i'm not along in not reviewing it18:47
dolphm#vote yes18:47
stevemarending vote early, it's backlogged18:47
openstackVoted on "Target "Unified delegation spec" to Mitaka?" Results are18:47
openstackYes (2): dolphm, ayoung18:47
openstackAbstain (10): dstanek, notmorgan, lhcheng, davechen, marekd, lbragstad, topol, bknudson, breton, stevemar18:47
openstackNo (1): henrynash18:47
ayoungamakarov, presented at the midcycle18:47
stevemargetting some useful data out of this18:47
stevemarthanks for putting up with it guys18:47
stevemar#startvote Target "Spec for optional Project ID via the Project creation API." to Mitaka? Yes, No, Abstain18:48
openstackBegin voting on: Target "Spec for optional Project ID via the Project creation API." to Mitaka? Valid vote options are Yes, No, Abstain.18:48
openstackVote using '#vote OPTION'. Only your last vote counts.18:48
amakarovayoung, it's still in design stage18:48
dolphmstevemar: i expect to see a pie chart on my desk tomorrow18:48
gyeewhat are we voting on now?18:48
stevemardolphm: along with the TPS report18:48
topollbragstad hook us up18:48
gyeethings scroll too fast on my screen18:48
ayoungamakarov, so do you think you can have it done in Mitaka anyway?18:48
lbragstad#link https://review.openstack.org/#/c/241346/18:48
*** ssancheztrujillo has quit IRC18:48
gyeethat or my IRC client is broken18:48
stevemartopol: lol18:48
shalehthe submitter has not been responding18:48
*** alex_xu has quit IRC18:48
*** mhickey has quit IRC18:48
amakarovayoung, if such hurry is necessary I can focus on that, of course18:49
henrynash#vote no18:49
stevemarshaleh: but do we agree that this is something we should try and get into mitaka?18:49
stevemar#vote no18:49
bknudson#vote abstain18:49
gyee#vote I don't know wtf I am voting18:49
openstackgyee: I don't know wtf I am voting is not a valid option. Valid options are Yes, No, Abstain.18:49
*** kebray has joined #openstack-meeting18:49
notmorganthe spec needs work. the idea i dislike, i think we (unfortunately) need it18:49
*** aranjan has quit IRC18:49
stevemargyee: lol18:49
ayounggyee, optional project ID18:49
topol#vote no18:49
dolphm#vote no18:49
dstanek#vote no18:49
*** aranjan has joined #openstack-meeting18:49
notmorganand i would like it to be something we can lock-down to say cloud-admin18:49
lbragstad#vote no18:49
*** roxanaghe has joined #openstack-meeting18:49
notmorganso... with that18:49
gyee#vote no18:49
stevemari think it needs a more dedicated resource and thought out spec18:49
dolphmall of hte impact sections are blank here, which is not acceptable for something so much potential for introducing bugs18:49
notmorgan#vote no18:49
ayoungdolphm, you were the one that initially balked at the idea.  I think it is a good idea, but don't *need* it in Mitaka18:49
notmorganbecause we need a resource on it18:50
shalehnotmorgan: ++ to everything you said18:50
*** mbound_ has joined #openstack-meeting18:50
dolphmayoung: agree18:50
notmorgannot because it's a bad idea.18:50
dolphmayoung: we just need to think through it, which this spec has not demonstrated yet18:50
stevemarwell this was helpful, i tohught there were stronger supporters for this idea18:50
openstackVoted on "Target "Spec for optional Project ID via the Project creation API." to Mitaka?" Results are18:50
openstackAbstain (1): bknudson18:50
openstackNo (8): gyee, lbragstad, notmorgan, dstanek, dolphm, topol, henrynash, stevemar18:50
notmorganstevemar: i hate the idea. we need something like it.18:50
*** pabelanger has joined #openstack-meeting18:50
stevemar2 more! we can make it18:50
notmorganfor at least the cloud admin.18:50
ayoungdolphm, would really appreciate having your concerns about it in acomment on the review.18:50
ayoungWould not be willing to go forward without that18:50
stevemar#startvote Target "Basic API spec for managing Policy rules in a database" to Mitaka? Yes, No, Abstain18:50
openstackBegin voting on: Target "Basic API spec for managing Policy rules in a database" to Mitaka? Valid vote options are Yes, No, Abstain.18:50
openstackVote using '#vote OPTION'. Only your last vote counts.18:50
lbragstad#link https://review.openstack.org/#/c/184903/18:50
stevemar#vote no18:51
ayoung#vote no18:51
henrynash#vote no18:51
ayoungthat should not be Mitaka18:51
ayoungit is backlog18:51
stevemardoes this even align with what we're doing?18:51
lbragstad#vote no18:51
bknudsonthis one depends on https://review.openstack.org/#/c/133814/2318:51
openstackVoted on "Target "Basic API spec for managing Policy rules in a database" to Mitaka?" Results are18:51
openstackNo (4): henrynash, lbragstad, ayoung, stevemar18:51
gyee#vote no18:51
topol#vote no18:51
stevemarlast one18:51
dolphm#vote belatedly18:51
stevemar#startvote Target "Make keystone fully fledged SAML2 Service Provider" to Mitaka? Yes, No, Abstain18:51
openstackBegin voting on: Target "Make keystone fully fledged SAML2 Service Provider" to Mitaka? Valid vote options are Yes, No, Abstain.18:51
openstackVote using '#vote OPTION'. Only your last vote counts.18:51
dolphm#vote yes18:51
stevemar#vote no18:51
stevemardolphm: why?18:51
gyee#vote yes18:51
notmorganso, this is anothe rone of those we *probably* need at this point18:51
bknudson#vote abstain18:52
*** eharney_ is now known as eharney18:52
davechen#vote abstain18:52
breton#vote abstain18:52
lhcheng#vote abstain18:52
notmorganbut i don't feel strongly about it.18:52
stevemarwhoa, i was not expecting any yes'es18:52
dolphmstevemar: because it's a pain point for operators and we knew that going into icehouse18:52
notmorgan#vote abstain18:52
ayoungcan someone voice why we need this before we stop the vote?18:52
dolphmoperators are now feeling that pain18:52
notmorgan#vote yes18:52
*** alex_xu has joined #openstack-meeting18:52
gyeeayoung, dynamic configuration via API18:52
*** kebray has quit IRC18:52
*** SotK has joined #openstack-meeting18:52
henrynash#vote no18:52
marekd#vote yes18:52
gyeefree ourselves from CMS18:52
henrynash(but willing to be convinced)18:53
notmorgangyee: ok hold up18:53
topolI could use more context on what the pain points are how this resolves them18:53
gyeehenrynash, why do we need API on per-domain config management?18:53
*** john-davidge has joined #openstack-meeting18:53
gyeehenrynash, same deal18:53
dolphmhenrynash: because when your domain admins each have their own idp, then you need self-service18:53
samueldmqgyee: wasn't this the reson we didn't want dynamic policies ? keystone shouldn't do cms work ?18:53
lbragstad7 minutes left18:53
notmorganwe have a baaaad ux on admin vs cms already18:53
*** MaxPC has quit IRC18:53
shalehdolphm: ++18:53
notmorganis this making it better or worse?18:53
ayoungI fear that this pushes us back toward "keystone is an identituy provider"18:53
dolphmhenrynash: are you going to bounce your keystone cluster every time one of your domain admins once to give you fresh certs?18:53
ayoung#vote no18:53
* ayoung willing to change with good argument18:54
notmorganayoung: i don't think it does.18:54
stevemarwhua? we're voting on saml2 spec18:54
shalehshibboleth is not presenting a solid UX18:54
notmorganayoung: keystone *can* provide a proxy to Identity for other things, but it doesn't make keystone an identity provider18:54
shalehwe need a reasonable alternative18:54
*** amuller has left #openstack-meeting18:54
notmorgansubtle difference18:54
gyeewe don't need the entire shibd, we only use a fraction of it18:54
shalehthis spec offers one18:54
ayoungnotmorgan, Then what does this spec mean?18:54
*** kebray has joined #openstack-meeting18:54
marekd#vote no18:54
notmorganshaleh: i also don't think that is the same thing.18:54
dolphmgyee: true18:55
lbragstadthis is still the policy vote,18:55
topol#vote Abstain18:55
shalehnotmorgan: agreed, but it is driving this18:55
marekdgyee: oh, we do need whole shibd18:55
openstackYes (3): gyee, dolphm, notmorgan18:55
dolphmayoung: that we won't depend on shib or mellon18:55
openstackAbstain (5): lhcheng, bknudson, topol, davechen, breton18:55
openstackNo (4): henrynash, ayoung, marekd, stevemar18:55
*** MaxPC has joined #openstack-meeting18:55
notmorganshaleh: then we need to go back to the drawing board18:55
*** MaxPC has quit IRC18:55
stevemarmarekd: you are voting no? it's your spec18:55
notmorgan#changevote no18:55
gyeemarekd, no, do you do policy validations?18:55
*** MaxPC has joined #openstack-meeting18:55
topolmarekd, the self hating core18:55
dstanekmarekd: voting no?18:55
lbragstadhow does everyone feel about the alternative in the spec?18:55
shalehthere is confusion over what is the active vote apparently18:56
marekdlbragstad: i actually think it should be enough18:56
*** paul-carlton has joined #openstack-meeting18:56
*** ssancheztrujillo has joined #openstack-meeting18:56
marekdstevemar: ^^18:56
*** banix has quit IRC18:56
ayoungAm I misunderstanding what we mean by "Service provider" here?18:56
*** banix has joined #openstack-meeting18:56
lbragstad#link https://review.openstack.org/#/c/244694/18:56
*** adiantum1 has joined #openstack-meeting18:56
dolphmmarekd: this is also something big enough that it might be worthwhile to pursue the implementation and demo it working *before* pursuing the spec.18:56
shalehdolphm: ++18:56
stevemardolphm: ++18:57
topoldolphm ++18:57
marekddolphm: poc king of thing on my own keystone fork18:57
topol#vote no18:57
dstanek#vote no18:57
dolphmmarekd: poc in a gerrit review :)18:57
*** adiantum has quit IRC18:57
*** adiantum1 is now known as adiantum18:57
openstackVoted on "Target "Make keystone fully fledged SAML2 Service Provider" to Mitaka?" Results are18:57
openstackYes (3): gyee, dolphm, notmorgan18:57
openstackAbstain (4): lhcheng, bknudson, davechen, breton18:57
openstackNo (6): dstanek, ayoung, marekd, topol, henrynash, stevemar18:57
stevemarokay, i'll write up a summary of this18:57
gyeemarekd, we have an inhouse POC, without relay state management18:57
stevemari hope you guys found it useful18:57
gyeemarekd, let me write you an email later18:57
bknudsonwe should do this every week18:58
marekdstevemar: we did, but next time we should do this 1-2 weeks before the freeeze18:58
*** salv-orl_ has joined #openstack-meeting18:58
*** aranjan_ has joined #openstack-meeting18:58
marekdgyee: sure.18:58
topolspeed dating specs, Keystone stylke18:58
*** aranjan has quit IRC18:58
*** kebray has quit IRC18:58
stevemarbknudson: your sarcasm is seeping through18:58
shalehbknudson: we would need a 90 min meeting :-)18:58
shalehtopol: ++18:58
stevemarmarekd: next time :)18:58
stevemarthanks for putting up with my crazy idea18:58
dstanekbknudson: i can see you writing an '#abstain' bot18:58
stevemardolphm: pie charts are coming18:58
marekdstevemar: i am serious18:58
dolphmstevemar: better be18:59
stevemarthanks everyone, now review patches and specs! :)18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Dec  1 18:59:17 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-12-01-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-12-01-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-12-01-18.01.log.html18:59
*** yolanda has joined #openstack-meeting18:59
topolwe still have t review the specs???? :-)18:59
stevemarnooo, i meant to end it with:18:59
*** dmowrer has joined #openstack-meeting18:59
stevemarkeystoners disassemble!18:59
*** shaleh has left #openstack-meeting19:00
fungiinfra team disassemble keystoners!19:00
Clintassemble m.a.s.k.19:00
*** baoli has quit IRC19:00
stevemarfungi: \o/19:00
fungiClint: that's an even better reference than voltron19:00
*** salv-orlando has quit IRC19:00
Clintfor assembly, sure19:00
* jeblair removes a keystone and everything collapses19:00
ruagair+1 jeblair19:01
*** lhcheng has left #openstack-meeting19:01
fungithose pesky keystones and their load-bearing nature19:01
clarkbI will have to pop out about 20 minutes before 2000UTC fwiw19:01
fungiokay, let's get started19:01
fungi#startmeeting infra19:01
openstackMeeting started Tue Dec  1 19:01:36 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
openstackThe meeting name has been set to 'infra'19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
fungi#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** gyee has quit IRC19:02
*** pvaneck has joined #openstack-meeting19:02
*** olaph has joined #openstack-meeting19:02
fungii'm not aware of any important announcements. anyone have anything pressing here?19:02
jesusauruslog_processor has been split out into its own project19:02
fungi#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
fungi#link http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-11-24-19.01.html19:02
fungithere were none19:02
*** aranjan_ has quit IRC19:03
fungi#topic Specs approval19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
*** aranjan has joined #openstack-meeting19:03
*** baoli has joined #openstack-meeting19:03
fungialso none for this week, though dhellmann has a release automation one which will likely be on the proposed list next week19:03
*** brucet has quit IRC19:03
*** dmowrer_ has joined #openstack-meeting19:03
*** dmowrer has quit IRC19:03
fungi#topic Priority Efforts: Nodepool provider status (jeblair)19:03
*** openstack changes topic to "Priority Efforts: Nodepool provider status (jeblair) (Meeting topic: infra)"19:03
*** patchbot has quit IRC19:03
fungithis is our specless/ongoing priority effort19:04
jeblairso we have ovh providing 160 nodes now...19:04
jeblairthey're still hoping to add more as they are able19:04
fungithat's an impressive addition19:04
fungithanks ovh!19:04
jeblairfrom what i can see, runtimes are generally between rax and hpcloud, but occasionally worse than hpcloud19:04
*** amitgandhinz has quit IRC19:04
fungi#info OVH nodepool worker count is now up to 16019:04
*** tej has quit IRC19:05
jeblairprobably due to our oversubscription19:05
*** paul-carlton1 has quit IRC19:05
*** neelashah has joined #openstack-meeting19:05
*** paul-carlton has quit IRC19:05
jeblairso my questions for the group are: are we happy with that level of performance so far?  and do we want to consider them in production?19:05
fungisigns point to yes19:05
*** brucet has joined #openstack-meeting19:06
clarkbother clouds have variance as well so the occasional job being slower isn't abnormal19:06
fungii haven't heard any complaints about jobs which have run there, at least19:06
anteaya+1 yes19:06
clarkbthe only complaints I hvae seen have been related to disk size iirc19:06
*** neelashah1 has quit IRC19:06
fungithis is 160 nodes between a couple regions in ovh, yeah?19:06
nibalizerjeblair: can you point us to a graphite/grafana graph showing this data?19:06
jeblairclarkb: i think we got a larger disk along the way19:06
clarkbas there is no large ephemeral drive for the jobs to rely on19:06
jeblairwe're up to 80 now19:06
clarkbjeblair: I believe it was the ansible folks assuming that a large ephemeral drive was mountable19:07
fungiyeah, i think we determined that was plenty for grenade at least19:07
jeblairnibalizer: not yet, i'm working on asking our providers for permission to make such a thing public19:07
jeblairnibalizer: so far that's looking promising19:07
*** john-davidge has quit IRC19:07
jeblairso i hope we'll have that soon19:07
*** manjeets_ has quit IRC19:08
jeblair(having said that, the data *are* in graphite)19:08
pabelangerjeblair: impressive19:08
nibalizerjeblair: fair19:08
*** penick has joined #openstack-meeting19:08
*** tej has joined #openstack-meeting19:08
*** vijendar has quit IRC19:08
fungiso sounds like we're agreed ovh is successfully in production in nodepool for us?19:08
jeblaircool, i'll let them know...19:09
jeblairquick update on the others:19:09
fungi#agreed OVH nodepool implementation is successfully in production19:09
*** john-davidge has joined #openstack-meeting19:09
jeblairwe just got enough floating ips from bluebox to use the full cpu capacity; we might see runtimes drop there, but we're also expecting to get replacement hardware which is faster so expect them to increase afterwords19:09
anteayaagain yay!19:10
*** patchbot has joined #openstack-meeting19:10
fungiwhat's the total number of ip addresses/anticipated capacity for that deployment?19:10
jeblairthat's 39 nodes; i'm also hoping that will increase, but that's at the "desire" stage rather than "implementation"19:10
fungigot it19:10
*** egallen has joined #openstack-meeting19:10
clarkbfungi: 316 vcpus/ 8 per VM19:10
jeblairand i think we're about ready to dip our toes into internap, waiting to be able to confirm my changes to nodepool work there19:11
nibalizerthanks bluebox, ovh, and internap!19:11
*** brucet has quit IRC19:11
fungi#info Nodepool use of Bluebox is progressing19:11
fungi#info Nodepool use of Internap resources is on the way soon19:12
*** patchbot has quit IRC19:12
fungi#topic Priority Efforts: Gerrit 2.11 Upgrade (zaro, et al)19:12
*** openstack changes topic to "Priority Efforts: Gerrit 2.11 Upgrade (zaro, et al) (Meeting topic: infra)"19:12
*** aranjan_ has joined #openstack-meeting19:12
*** aranjan has quit IRC19:12
* notmorgan is here too.19:12
*** tej has quit IRC19:13
fungimostly want to make sure we hammer at this and don't let the reschedule slip any further than we can help19:13
zaro#link https://etherpad.openstack.org/p/test-gerrit-2.1119:13
clarkbnotmorgan: you said you had an apache workaround for the openid thing?19:13
*** patchbot has joined #openstack-meeting19:13
notmorganclarkb: for the double-slash thing19:13
anteayafungi: yes19:13
notmorganthe redirections are not really fixable in apache19:13
clarkbnotmorgan: right19:13
clarkbnotmorgan: can you link it here?19:13
notmorganthey seem to be missing important data from the query-string19:13
anteayatwo patches up for the double slash redirect issue are at the bottom of the etherpad zaro linked to19:13
notmorgan#link https://review.openstack.org/#/c/249714/19:13
zaroredirect seems pretty minor though. it's only when user is not logged in.19:14
notmorganthat removes the double slashes19:14
*** kozhukalov_ has quit IRC19:14
*** tej has joined #openstack-meeting19:14
fungiyeah, while it's an annoying regression i'm of the opinion we could go forward and just let the dev community know it's a rough patch while upstream works through a fix19:14
notmorganthe only option to restore redirect (afaict) is to use proxypass instead of mod_rewrite+mod_proxy19:14
clarkbnotmorgan: or fix gerrit19:15
notmorganand that would hurt a lot of offload we do19:15
notmorganclarkb: that was assuming not getting a fix from upstream :)19:15
*** pm90_ has joined #openstack-meeting19:15
fungior rather as an interim workaround while upstream gerrit continues the debate on how they want it fixed19:15
zarorevert #link https://review.openstack.org/248411 would fix both19:15
*** neelashah1 has joined #openstack-meeting19:16
*** armax has quit IRC19:16
clarkbI think reverting the breaking change in our gerrit makes sense as long as we are confident that the issue (what was it by the way) the breaking change fixes won't affect us19:16
notmorganzaro: ++19:17
fungii agree it's always good to try to help fix these things, though at the moment the delay seemed (from the upstream bug) more one of deciding what was an acceptable solution rather than the actual writing it19:17
notmorganclarkb: agree. a more complete fix as long as it doesn't cause major issues is better.19:17
jeblairif we think it's going to get fixed upstream, sure; but otherwise, we'll just have this conversation again in a year when we've forgotten everything.  :)19:17
anteayafungi: from what zaro tells me the redirect double // issue is the last work item, if you feel it isn't a blocker perhaps we can move to discussing a time for the upgrade and contine to discuss the fix in the interm19:17
zarobreaking change was supposed to fix dropped tokens.  it like it keeps the tokens in other situations but drops it for our situation.19:17
zaroI haven't noticed any bad side affects from the revert.19:18
*** neelashah has quit IRC19:18
fungirunning with backport fixes from newer upstream releases is one thing, running with our guess as to how upstream will fix an outstanding bug is a lot further down the road to running a fork again19:19
fungiso just want to make sure we consider that situation carefully19:19
clarkbI don't think we expect upstream to revert do we?19:19
zaroclarkb: very unlikely19:19
notmorganclarkb: i wouldn't expect it, i would expect a further-down-the-road fix that takes a stab at addressing this new case19:20
anteayathey have -2 the revert patch have they not?19:20
*** john5223 is now known as zz_john522319:20
zaro-1 from one of the cores (hugo) i think.19:20
* anteaya tries to find19:21
zaroattempted revert at bottome of ehterpad19:21
jeblairbasically, i really don't want to ask notmorgan to spend another holiday doing this again next year, so if we have a workaround that isn't the revert, i have a slight preference for that; unless we're really sure it's going to get fixed upstream for realz by the next time we upgrade.19:21
notmorganjeblair: i appreciate the sentiment :)19:22
zaroi agree with jeblair, notmorgan workaround would be preferable atm.19:22
fungii too am inclined to take notmorgan's partial workaround and just make it clear in the upgrade announcement that redirects on login aren't quite how they're supposed to be19:22
clarkbfungi: well its worse than that19:22
clarkbfungi: they don't work at all19:23
clarkbyou will end up back at /19:23
clarkbregardless of where you started19:23
notmorganclarkb: correct.19:23
jeblairthat's :(19:23
clarkbwhich to me as a user of the web interface that logs in a bnuch because gerrit likes to log me out will make me very unhappy19:23
*** nmagnezi has quit IRC19:23
notmorgani have an approach that could fix it, but it requires layering in another proxy point.19:23
*** ihrachys has quit IRC19:23
clarkbwhich is why my preference is the revert19:23
*** aimon has joined #openstack-meeting19:23
anteaya#link of zaro's revert patch that is -1'd by hugo (the author of the breaking patch) https://gerrit-review.googlesource.com/#/c/72720/19:23
notmorganbecause it's the only way to address a QSA19:23
notmorganin mod_rewrite post proxy19:24
notmorganit's not pretty19:24
notmorgan(or using something that can act on L7 like HAProxy)19:24
notmorganbut i could add the correct token back in that way19:24
notmorgani would *prefer* to not go down that path19:24
*** edtubill has joined #openstack-meeting19:24
*** rajinir_ has quit IRC19:25
zaroanteaya: hugo was not the author19:25
*** p0rtal has joined #openstack-meeting19:25
anteayazaro: wasn't this the patch that created the problem? https://gerrit-review.googlesource.com/#/c/5780019:26
notmorgananteaya: that looks like the right number19:26
*** kozhukalov_ has joined #openstack-meeting19:26
*** egallen has quit IRC19:26
zaroyes. owner is hugo, author is simon19:27
anteayasorry don't mean to create noise19:27
anteayazaro: ah sorry19:27
clarkbso sounds like we should maybe push upstream a bit more on this and maybe offer our own fix or strategy for one that isn't a revert?19:27
fungii didn't consider that gerrit has a tendency to logout some users often. it tends to leave me logged in pretty consistently but my case may not be representative19:27
*** roxanaghe has left #openstack-meeting19:27
clarkbfungi: I get logged out probably 20 times a day19:27
ruagair+1 clarkb19:28
notmorganfungi: i am regularly logged out19:28
*** yfried has joined #openstack-meeting19:28
*** rderose has joined #openstack-meeting19:28
anteayawell no redirect will be a pain for me as I often have several patches open before I am logged in19:28
*** e3du5 has left #openstack-meeting19:28
anteayabut once logged in I'm logged in for the day19:28
notmorganif you want me to spin a patch that will re-add the token back in, i can do that on top of my current one19:28
notmorganjust to show how it would work19:28
nibalizerclarkb: ouch how?19:28
notmorganbut i really don't think you'll like it19:28
notmorganthere is a 3rd option19:29
clarkbnibalizer: when you switch between tabs it decides the new tab needs to log in and the old tab is logged out19:30
notmorganwe can layer in L7 routing and handle the offload there instead of direct in mod_rewrit e(aka haproxy or another proxy tier like i have been describing) then proxypass to gerrit directly19:30
notmorganit seems proxypass handles the querystring correctly fwiw.19:30
fungiclarkb: ahh, yeah i work around that by backing up to the original page again and doing a refresh before retrying to click something on it19:30
fungithat seems to then notice it's logged in anew19:31
fungirather than logging me out19:31
notmorganfungi: interesting.19:31
anteayayes if I have one tab open and log in with that tab then all other tabs have me logged in19:31
anteayaif I don't it logs me out all the time19:32
* SotK is also rarely logged out automatically19:32
SotKit tends to only happen if I log in on a different machine19:32
zarocan i ask what's everybody's concern regarding the revert?19:32
pabelangerclarkb: nibalizer: Yup, learned that the hard wall long ago.  It stinks19:32
jeblairzaro: it's technical debt that makes it harder for us to upgrade.  we can accept that, but someone needs to pay it down before the next time we upgrade.19:32
notmorganzaro: i think the biggest concern is "what is the real upstream fix going to be down the line? and will this revert make it significantly harder to follow future releases"19:32
notmorganzaro: jeblair said it better ;)19:33
*** devananda has quit IRC19:33
*** roxanagh_ has joined #openstack-meeting19:33
fungizaro: concern being that we don't know (and have reason to expect) that's not how upstream will fix it if ever, so we're carrying a divergence for an indeterminate/indefinite timeframe19:33
anteayafwiw the gerrit folks said they would like to help us but they can't reproduce the issue19:33
zarodo you mean to the gerrit 2.12? or 2.11.x?19:33
*** hashar has joined #openstack-meeting19:33
anteayain the comments on https://gerrit-review.googlesource.com/#/c/5780019:33
clarkbanteaya: I thought it was reproduceable using our mod rewrite rules?19:33
zaroif i had to guess it  should be fixed in 2.1219:33
anteayaclarkb: they cant' reproduce19:34
fungianteaya: reproduction was clarified in the bug19:34
fungi#link https://code.google.com/p/gerrit/issues/detail?id=336519:34
notmorgani was unable to reproduce complete broken-ness locally19:34
anteayaaccording to the comments on https://gerrit-review.googlesource.com/#/c/57800 they can't reproduce, unless that is old information19:34
notmorganbut i could repro the // issue, it just worked.19:34
zarofwiw, i'm going to work on it and it seems like hugo is willing to help19:34
fungiat least david commented that he was able to reproduce19:34
fungi(in the bug)19:35
*** krtaylor has quit IRC19:35
*** mbound_ has quit IRC19:35
*** p0rtal_ has joined #openstack-meeting19:35
anteayabug date is more recent than comments on 5780019:36
zarodimtruck is able to repro.  i'm working on setting up the same ENV19:36
*** ssancheztrujillo has quit IRC19:36
*** arcee has quit IRC19:36
*** julim has joined #openstack-meeting19:36
*** p0rtal has quit IRC19:36
*** sdake has joined #openstack-meeting19:36
zarofrom what i hear, hugo is on paternatify leave for next few weeks19:37
*** neelashah has joined #openstack-meeting19:37
fungiso anyway, i guess we need to arrive at a decision on how we're addressing the login redirect, or continue to defer the upgrade maintenance19:37
*** roxanagh_ has quit IRC19:37
*** kebray has joined #openstack-meeting19:38
zaroi'm +1 for notmorgan workaround, but sounds like ppl are unhappy with that so +1 for revert as well.19:38
fungiwe have carrying a fork with the broken change reverted as option 1, leaving login redirects broken as option 2, or switching to something with mod_proxy as option 319:39
jeblairi'm okay with the revert if zaro's going to continue to work on the real fix19:39
*** neelashah1 has quit IRC19:39
*** kebray has quit IRC19:39
anteayaI'm fine with whatever is decided19:39
jeblairwe didn't really discuss option 3 much, but i feel like adding in haproxy for this is maybe a bit heavyweight19:39
fungiaccording to hugo's reply on the proposed revert there are other dependent commits which also need reverting?19:40
zaroi think there was only 1 and i don't think it affects us.19:40
*** breton has left #openstack-meeting19:40
*** dmacpher has joined #openstack-meeting19:41
notmorganping me if any further apache work is needed, happy to dig in on that front.19:41
zarois option 3 a no go either?19:41
fungii was more asking whether we need to rever that too, or if it'll still build sanely19:41
notmorgancan we afford to lose the mod_rewrite offload?19:41
fungier, to revert19:41
notmorganif we can, then... the proxypass is the lowest impact change.19:41
*** vishwanathj has quit IRC19:42
zarofungi: still builds no problem, it's on review-dev.o.o now19:42
fungii guess the /p/ rewrite is the main thing we get there. /fakestore is really only relevant to review-dev and we could probably live without a robots.txt19:42
*** vishwanathj has joined #openstack-meeting19:42
jeblairthe /p/ rewrite is heavily used19:42
fungiby zuul?19:43
pleia2and people19:43
* mordred waves - apologizes for blow calendar timezones somehow19:43
fungiwe've tried really hard to get people to stop using that local mirror, if memory serves19:43
notmorganso maybe i can maintain the /p/ rewrite and still mod_proxy19:44
notmorgannow that i think about it19:44
pleia2fungi: I suppose breaking it may get them to stop for good :)19:44
fungialso now it's unable to serve shallow clones because of git smart http on trusty19:44
*** jingyizhaobo has joined #openstack-meeting19:44
*** yfried has quit IRC19:44
jeblairnotmorgan: oh that would be neat19:44
*** cdelatte has quit IRC19:44
notmorganjeblair: i'll circle up on that here shortly.19:44
notmorganit might be less pretty but it might be workable. i think a couple spare <location> blocks will suffice19:45
*** cdelatte has joined #openstack-meeting19:45
notmorganbut let me 2x check, if i can't lets fall back to the revert or punt while zaro works on this.19:45
notmorgani'll have an answer on if i can do this by tomorrow-ish fwiw19:45
*** ssanchez_ has joined #openstack-meeting19:45
jeblairfungi: i'm not sure what's using it19:46
fungiso it sounds like maybe the consensus is that we'd like to do option 3 (mod_proxy) if it can still support our needs, but that a fallback to option 2 (revert the breaking change and work upstream on a real fix) is still preferable to option 1 (leave it broken and work with upstream on a real fix)19:46
*** kebray has joined #openstack-meeting19:46
anteayafungi: I can live with that19:46
*** baoli has quit IRC19:46
*** baoli has joined #openstack-meeting19:47
fungiin that case i'd be inclined to try to pick a maintenance window and assume we'll do 3 if possible otherwise 219:47
*** devananda has joined #openstack-meeting19:47
anteayaI'm for that too19:47
*** aranjan has joined #openstack-meeting19:47
*** bzhao0825 has quit IRC19:47
anteayato stay away from a christmas rollback I think we should do something prior to the 19th19:48
*** kebray has quit IRC19:48
fungiassuming no other objections, when do people like for the window. another wednesday like the last one (so that we can have fairly immediate confirmation under load rather than waiting two days to find load breaks us)?19:48
notmorganok i'll commit to having an answer/update tomorrow then19:48
notmorganso we have windows ASAP for the way forward19:48
*** fzdarsky has quit IRC19:48
anteayaI'm available any day between now and the 19th19:48
anteayaany day is fine with me19:48
*** adiantum1 has joined #openstack-meeting19:48
jeblair< dec 19 seems to work with the release schedule19:49
*** yfried has joined #openstack-meeting19:49
fungialso, one thing i want to keep in mind is that we still have the openstack-attic/akanada typo to clean up. i have a feeling that needs to be fixed before our cruft repo cleanup step in the maintenance19:49
jeblairwe don't really have anything big there until mid-jan19:49
zaroi'm available, except new years weekend.19:49
nibalizerso december 16th?19:49
*** nmagnezi has joined #openstack-meeting19:49
*** cdelatte has quit IRC19:49
pleia2I'm around all month19:49
*** aranjan_ has quit IRC19:50
anteayathe 16th is two weeks from tomorrow19:50
*** cdelatte has joined #openstack-meeting19:50
jeblairdec16 wfm19:50
anteayaI'm fine with that19:50
notmorganzaro: is your proxypass review still up?19:50
fungi16th works for me. what was the start time for the previously scheduled maintenance? we could just shoot for that again19:50
notmorganzaro: so i don't need to go re-creating from scratch19:50
jeblairmordred: how's dec16 for you?19:50
*** john-davidge has quit IRC19:50
funginibalizer: you want to have another go at the maintenance announcements for this?19:51
jeblairmordred: (hopefully your rollback is self-sufficient at this point, but in case we need some of your brain, would be nice to have)19:51
nibalizerfungi: i do19:51
mordredjeblair: I may be driving/roadtrip - but I may also be available - or could make myself so19:51
nibalizerwhat time are we gonna do it19:51
mordredjeblair: oh. wait. you may want my BRAIN?19:51
fungi#action nibalizer send announcement about rescheduled gerrit upgrade maintenance19:51
jeblairmordred: i can volunteer to call you and tell you to pull over19:51
zaronotmorgan: #link https://review.openstack.org/#/c/243879/19:51
notmorganzaro: thnx19:51
anteaya1700 utc: http://lists.openstack.org/pipermail/openstack-dev/2015-November/078113.html19:51
*** armax has joined #openstack-meeting19:51
*** aranjan has quit IRC19:51
fungithanks anteaya19:52
funginibalizer: so starting at 1700 utc on wednesday december 16th19:52
mordredjeblair: sandy can drive - I can tether19:52
zaronibalizer: same time as last time19:52
*** john-davidge has joined #openstack-meeting19:52
fungi#agreed Gerrit 2.11 upgrade rescheduled to 17:00 UTC Wednesday December 16th19:52
*** adiantum has quit IRC19:52
*** adiantum1 has quit IRC19:53
fungii think krotscheck/greghaynes have one topic on the agenda as well, if we can switch to that for the remaining few minutes19:53
anteayatc meeting is also canceled today19:53
krotscheckI put it on the agenda without checking with greghaynes.19:53
greghaynesI do?19:53
fungi#topic Mirror efforts (krotscheck, greghaynes)19:53
*** openstack changes topic to "Mirror efforts (krotscheck, greghaynes) (Meeting topic: infra)"19:53
* ruagair has maniphest updates too.19:53
*** annegentle has joined #openstack-meeting19:53
jeblairgreghaynes: okay what's this all about?19:54
krotscheckWe've got a bunch of mirror things in queue. First is greghaynes's wheel-mirror work.19:54
fungiwhat's all this then?!?19:54
mordred(the TC meeting isn't happening, so if we go over, we won't break anything)19:54
jeblair(i quickly replaced the tc meeting with another meeting so will be half-here)19:54
fungii think i'm +2 on all the wheel mirror patches for whatever that's worth19:54
krotscheckIs there any coordination that needs to be done to land that other than landing the patches, jobs, and spinning up the instances?19:55
*** rockyg has joined #openstack-meeting19:55
*** sdake_ has joined #openstack-meeting19:55
greghaynesThe instances exist, hiera data needs to get added for ssh host keys though19:55
fungii can help spin up the mirror build instances for that, though more than happy for someone else to volunteer19:55
*** sdake has quit IRC19:55
krotscheck#link https://review.openstack.org/#/q/status:open+branch:master+topic:feature/wheel-mirror,n,z19:55
fungioh, we have the instances? even better19:55
*** jckasper has joined #openstack-meeting19:55
greghaynesI thought you made them ;)19:55
krotscheckYay meetings!19:56
fungier, heh19:56
*** neelashah has quit IRC19:56
krotscheckgreghaynes: The one patch I seem to be msising is one that actually starts using our wheel mirrors, is that somewhere?19:56
mordredwhat are they called?19:56
*** maishsk has joined #openstack-meeting19:56
fungigreghaynes: if i made them, then they should respond to ping via whatever the dns names are19:56
krotscheckmordred: /.*wheel-mirror-.*\.openstack\.org/19:57
mordredno. they do not exist19:57
mordredI can help make them19:57
greghaynesfungi: ya, I might have misinterpreted something we chatted about when we were figuring out host keya19:57
fungikrotscheck: i believe using the wheel mirrors is automagical, or seemed to be last time we tried to do this19:57
*** amitgandhinz has joined #openstack-meeting19:57
* krotscheck likes magic.19:58
fungisome magicsauce in pip that knows to check specific paths for possible wheels?19:58
*** electrofelix has left #openstack-meeting19:58
krotscheckdstufft would know19:58
fungiwheelpeople presumably know more than i do about this, yeah19:58
greghayneskrotscheck: there isn't one AFAIK19:58
* nibalizer has to bounce right at noon, sorry19:58
greghaynesIs what you want19:58
krotscheckIn the interest of coordination, can we schedule a date/time to babysit these patches through and make sure the world doesn't explode? I'm available before noon PDT most days.19:58
fungioh, so we do need an extra-index-url with the platform name encoded?19:59
*** jprovazn has quit IRC19:59
greghaynesfungi: yep19:59
krotscheckUnless someone has a major issue with them, that is.19:59
* krotscheck spends the rest of the day sitting on actual babies.19:59
mordredmmm. sitting19:59
fungiseems like they're pretty much all in shape last i looked, though i and other reviewers could certainly have missed something19:59
* mordred can help with the root portions of this - is also availabe in mornings19:59
krotscheckmordred, greghaynes: How does tomorrow morning around 10AM PDT sound?20:00
*** bookwar has joined #openstack-meeting20:00
fungido we have a volunteer to build the instances who isn't me? otherwise i'll try to do that after the meeting now that i don't have a tc meeting to lurk20:00
*** aysyd has quit IRC20:00
* krotscheck is assuming mordred is that volunteer.20:00
fungiand also sounds like we need to update hiera for ssh keys20:00
greghayneskrotscheck: works for me20:00
mordredfungi: yes. I will do that20:01
mordredkrotscheck: tomorrow morning I will be on an aeroplane20:01
mordredkrotscheck: can we do friday morning?20:01
fungithanks mordred. in that case i'll work on the stable maintenance electorate list stuff instead since that's also urgent20:01
anteayayes I want to vote20:01
greghaynesFriday also works20:02
fungias it turns out we do have >1 candidate for ptl20:02
krotscheckgreghaynes, mordred: Ditto. 10AM PDT Friday20:02
*** kencjohnston has quit IRC20:02
mordredfungi: also, I need electorate lists for N and O name elections while you're at it20:02
Clintkrotscheck: i think you mean PST20:02
*** weshay_xchat has quit IRC20:02
* mordred stabs daylight savings time in the face20:02
fungimordred: get up with me after this and remind me what i gave you last time (or whether you got it from the foundation site admins instead)20:03
krotscheckClint: You are correct.20:03
krotscheck10AM PST Friday20:03
krotscheck1800 UTC Friday20:03
*** Shrews has left #openstack-meeting20:03
*** sdake_ is now known as sdake20:03
krotscheckI'll leave the remaining mirror things on the agenda for next week.20:03
krotscheckI figure that we'll do a similar coordination thing there.20:04
*** banix_ has joined #openstack-meeting20:04
fungisounds good20:04
mordredkrotscheck, fungi: do we have a doc of what server(s) we need?20:04
* krotscheck defers to greghaynes 20:05
*** gr720e has quit IRC20:05
fungimordred: theu20:05
fungithey're in one of the changes but yes get greghaynes to point you to the list20:05
fungii don't recall the exact one20:06
fungiwe're over time, but if people want to stick around ruagair had some maniphest things to mention since we have the room what with there being no tc meeting this week20:06
greghaynesmordred: Not a doc, should be findable in the change but I need to mentally re-page in where20:06
*** neelashah has joined #openstack-meeting20:06
*** baoli has quit IRC20:06
* anteaya is willing to stick around to listen to ruagair20:06
krotscheckEOT for me.20:06
krotscheckGo go maniphest things20:06
fungi#topic Priority Efforts: maniphest migration (ruagair)20:06
*** openstack changes topic to "Priority Efforts: maniphest migration (ruagair) (Meeting topic: infra)"20:06
*** fzdarsky has joined #openstack-meeting20:07
ruagairLot's of updates.20:07
ruagairPhab + OpenID (login.ubuntu.com) works nicely using mod_auth_openid20:07
*** banix has quit IRC20:07
*** banix_ is now known as banix20:07
*** salv-orl_ has quit IRC20:07
ruagairOnly snag is #link https://github.com/bmuller/mod_auth_openid mod_auth_openid is abandonware.20:07
*** kencjohnston has joined #openstack-meeting20:08
ruagairSo we'd need to consider whether we want to adopt it.20:08
ruagairI'm currently working on the last piece of the migration process:20:09
*** erlon has quit IRC20:09
*** dmowrer_ has quit IRC20:09
ruagairScraping OpenIDs from launchpad to insert into Pah.20:09
*** fawadkhaliq has quit IRC20:09
fungiit's too bad clarkb had to drop out, but sync up with him since i know he's looked at it too20:10
ruagairOnce I've completed that, I'm happy to open up instance more broadly that I already have.20:10
fungion mod_auth_openid being abandonware that is20:10
ruagairI think clarkb promised to adopt it for fun, fungi :-)20:10
*** baoli has joined #openstack-meeting20:10
*** pabelanger has left #openstack-meeting20:10
yolandahi, wanted to show a change for glean, for infra-cloud efforts: https://review.openstack.org/#/c/252037/20:11
ruagairII'm re-writing this #link https://review.openstack.org/#/c/240795/ into python to have a more complete process.20:11
yolandasorry ruagair, i interrupted :(20:11
ruagairSome of it will get spun off into ansible and puppet, of course.20:11
fungiyeah, no updates of substance for 18 months, and no real activity for over 2 years20:11
ruagairNo probs yolanda :-D20:11
anteayawasn't that one of the questions from last week about phabricator use?20:11
ruagairThere was anteaya.20:12
anteayaas in who is currently using it and what is their understanding for doing so?20:12
ruagairCurrently I have two users, yolanda and GheRivero who are using a stable instance I have up.20:12
yolandaruagair, no much activity for that on the latest weeks20:12
yolandai believe GheRivero was poking a bit more20:12
ruagairsdague is rather keen to use Phab as soon as I think OpenID is integrated in a prod fashion.20:13
ruagairWhich is not far off.20:13
fungiaside from the lack of activity or upstream maintenance on mod_auth_openid were there any other concerns with it? does it have any missing features/bugs that you found?20:14
ruagairNot that I have found.20:14
ruagairIt worked rather trivialy.20:15
fungiif not, then we could just use it and revisit adopting it if it still lacks an upstream once we find something we need to improve with it20:15
ruagairThat's what my thoughts were.20:15
*** weshay_xchat has joined #openstack-meeting20:15
ruagairIt's time I put up an etherpad on this I think.20:15
ruagairList off the status and issues.20:16
fungisounds good. anything else on this topic before i give yolanda the floor for infra-cloud needs?20:16
yolandafungi, i have fat fingers, the interruption was not intented... so now, infra-cloud: https://review.openstack.org/#/c/252037/20:16
jeblairi just wanted to make sure we're on the same page about usage --20:16
jeblairthat we definitely want people to be able to poke at test instances and stuff20:17
fungiyolanda: jeblair still had a point for the current topic20:17
fungii'll switch the topic once we're ready20:17
jeblairbut that we don't want to do ad-hoc hosting projects in phab20:17
ruagairI agree jeblair.20:17
fungiright, there was a question last week on that20:17
ruagairYes, I was fighting kangaroos at that time :-/20:18
fungisomething in an earlier status update about people already using maniphest in anger because of not wanting to continue on lp any longer20:18
*** vijendar has joined #openstack-meeting20:18
jeblairright, i don't think that was happening but we were jumping to conclusions based on lack of data :)20:18
fungicrocodile wrestling is no longer the national pasttime? it's roofights now?20:18
* fungi updates his notes20:18
*** spzala has quit IRC20:19
fungi#topic Priority Efforts: infra-cloud (yolanda)20:19
*** openstack changes topic to "Priority Efforts: infra-cloud (yolanda) (Meeting topic: infra)"20:19
ruagairNo, that's not a reality fungi. We have yolands and GheRivero poking and that's it. sdague *wants* to use it seriously but is not at this point.20:19
fungi#link https://review.openstack.org/25203720:19
yolandaok so we got some races on glean20:19
yolandarelated on the events where glean was executed20:20
yolandarcarrillocruz created that fix, we have tested that intensively on our environment, and we got rid of the races20:20
*** sputnik13 has joined #openstack-meeting20:20
*** alexpilotti has quit IRC20:20
yolandai wanted to show that, and ask for reviews20:20
yolandagreghaynes, can you add more details to that review?20:21
sdaguefungi: fwiw, my declared desire for maniphest is to get the kanban board for visualizing and tracking cross project efforts, which launchpad is not really suitable for. And our current approach is ghetto kanban in etherpad.20:21
fungiokay, so that addresses a bug which is impeding infra-cloud deployment in one of our regions20:21
fungithanks for the info and the fix rcarrillocruz, yolanda20:21
rcarrillocruzin other news, we consistently deploy 90 out of 93 machines in East20:21
*** dmowrer has joined #openstack-meeting20:21
greghaynesyolanda: I dont remember all the details - I just put a review asking for them ;)20:22
lifelesssdague: fwiw have you looked at the lp->kanban thing ?20:22
lifelesssdague: which renders bugs as cards ?20:22
yolandagreghaynes, so the issue is that glean was executed when a network interface was detected20:22
yolandain our deployments, it showed a constant race, causing the vlan information to don't be created if that interface was not detected20:23
*** fzdarsky has quit IRC20:23
greghaynesyolanda: ah, right, it wasnt a race - we just dont do the dependency detection20:23
rcarrillocruzgreghaynes: no, it's not about the vlan interfaces. The fix i pushed and got merged already created vlan interfaces attached to physical interfaes20:23
greghaynesthen I am confused20:23
yolandaswitching that event, to start networking event, and configuring all interfaces there at same time , proved to solve our issue20:23
greghaynesanyhow, we can chat out of meeting?20:24
rcarrillocruzi can stay a bit online20:24
SotKsdague: we've also merged a first pass of kanban board stuff in SB now, with patches to make it more usable in review, that you could check out if you like20:24
fungiokay, so seems like we've made good use of our extra meeting time. anything else we need to cover this week before i #endmeeting?20:25
SotK(its not very discoverable yet though, since its not entirely merged)20:25
*** emagana has quit IRC20:25
anteayathanks fungi20:25
*** ssanchez_ has quit IRC20:25
*** alexpilotti has joined #openstack-meeting20:26
fungithanks everybody!20:26
*** kozhukalov_ has quit IRC20:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:26
openstackMeeting ended Tue Dec  1 20:26:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-01-19.01.html20:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-01-19.01.txt20:26
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-01-19.01.log.html20:26
*** yolanda has left #openstack-meeting20:26
fungireminder to those lurking, there is no tc meeting this week20:26
Clintand now 34 minutes of silence20:26
*** cbouch has quit IRC20:27
*** baoli has quit IRC20:28
*** alexpilotti has quit IRC20:29
*** dmowrer has quit IRC20:30
*** tej has quit IRC20:30
*** baoli has joined #openstack-meeting20:30
*** dmowrer has joined #openstack-meeting20:30
*** penick has quit IRC20:31
*** rfolco has quit IRC20:31
*** neelashah has quit IRC20:32
*** olaph has left #openstack-meeting20:32
*** jmckind has quit IRC20:32
*** iyamahat has joined #openstack-meeting20:33
*** roxanagh_ has joined #openstack-meeting20:34
*** dmowrer_ has joined #openstack-meeting20:34
*** dmowrer has quit IRC20:35
*** dmowrer has joined #openstack-meeting20:35
*** rpioso has joined #openstack-meeting20:36
*** roxanagh_ has quit IRC20:38
*** novas0x2a|laptop has joined #openstack-meeting20:38
*** dmowrer_ has quit IRC20:38
*** rajinir_ has joined #openstack-meeting20:40
*** nmagnezi has quit IRC20:41
*** otter768 has joined #openstack-meeting20:42
*** kozhukalov_ has joined #openstack-meeting20:42
*** neelashah has joined #openstack-meeting20:44
*** mudassirlatif has quit IRC20:45
*** otter768 has quit IRC20:47
*** aranjan has joined #openstack-meeting20:48
*** alexpilotti has joined #openstack-meeting20:50
*** achanda has quit IRC20:50
*** rderose has quit IRC20:51
*** rderose has joined #openstack-meeting20:51
*** emagana has joined #openstack-meeting20:51
*** emagana has quit IRC20:52
*** emagana has joined #openstack-meeting20:52
*** aranjan has quit IRC20:52
*** maishsk has quit IRC20:53
*** aranjan has joined #openstack-meeting20:53
*** gordc has joined #openstack-meeting20:54
*** alexpilotti has quit IRC20:54
*** annegentle has quit IRC20:55
*** dane_leblanc_ has joined #openstack-meeting20:57
*** baoli has quit IRC20:57
*** john-davidge has quit IRC20:57
*** dane has quit IRC20:58
*** john-davidge has joined #openstack-meeting20:59
*** neiljerram has quit IRC20:59
*** john-davidge has quit IRC20:59
thingeeREMINDER, cross-project meeting is in openstack-meeting-cp21:00
*** raildo is now known as raildo-afk21:01
elmikothingee: thanks!21:04
*** Piet_ has joined #openstack-meeting21:04
*** penick has joined #openstack-meeting21:04
*** SpamapS is now known as TheKettle21:04
*** TheKettle is now known as SpamapS21:04
*** sdake has quit IRC21:06
*** salv-orlando has joined #openstack-meeting21:07
*** sdake has joined #openstack-meeting21:08
*** changbl has quit IRC21:12
*** dprince has quit IRC21:12
*** sdake has quit IRC21:12
*** vhoward has quit IRC21:14
*** sdake has joined #openstack-meeting21:14
*** gordc has left #openstack-meeting21:15
*** bvandenh has quit IRC21:15
*** maishsk has joined #openstack-meeting21:16
*** neelashah has quit IRC21:18
*** salv-orlando has quit IRC21:19
*** kozhukalov_ has quit IRC21:19
*** john-davidge has joined #openstack-meeting21:21
*** alexpilotti has joined #openstack-meeting21:21
*** mhickey has joined #openstack-meeting21:21
*** edtubill has quit IRC21:23
*** alexpilotti has quit IRC21:25
*** jmckind has joined #openstack-meeting21:25
*** dulek has quit IRC21:26
*** maishsk_ has joined #openstack-meeting21:27
*** maishsk has quit IRC21:27
*** maishsk_ is now known as maishsk21:27
*** dulek has joined #openstack-meeting21:27
*** harlowja has quit IRC21:27
*** apoorvad has quit IRC21:28
*** harlowja has joined #openstack-meeting21:28
*** amitgandhinz has quit IRC21:29
*** amitgandhinz has joined #openstack-meeting21:29
*** hemna is now known as hemnafk21:29
*** MaxPC has quit IRC21:30
*** sdake has quit IRC21:30
*** salv-orlando has joined #openstack-meeting21:31
*** rcernin has quit IRC21:31
*** scinawa has quit IRC21:34
*** sdake has joined #openstack-meeting21:34
*** roxanagh_ has joined #openstack-meeting21:34
*** salv-orl_ has joined #openstack-meeting21:35
*** dmowrer has quit IRC21:35
*** salv-orl_ has quit IRC21:35
*** dmowrer has joined #openstack-meeting21:36
*** salv-orlando has quit IRC21:36
*** salv-orl_ has joined #openstack-meeting21:37
*** TravT has joined #openstack-meeting21:39
*** roxanagh_ has quit IRC21:39
*** xek_ has quit IRC21:39
*** salv-orl_ has quit IRC21:40
*** dmowrer has quit IRC21:40
*** sdake has quit IRC21:41
*** dasm has left #openstack-meeting21:41
*** salv-orlando has joined #openstack-meeting21:41
*** scinawa has joined #openstack-meeting21:43
*** krtaylor has joined #openstack-meeting21:44
*** salv-orlando has quit IRC21:45
*** john-davidge has quit IRC21:45
*** salv-orlando has joined #openstack-meeting21:46
*** rpioso has quit IRC21:46
*** mrmartin has quit IRC21:50
*** thangp has quit IRC21:50
*** bswartz has quit IRC21:51
*** topol has quit IRC21:51
*** adahms has joined #openstack-meeting21:52
*** neelashah has joined #openstack-meeting21:52
*** dmowrer has joined #openstack-meeting21:53
*** dmowrer has quit IRC21:53
*** salv-orlando has quit IRC21:54
*** dmowrer has joined #openstack-meeting21:54
*** JRobinson__ has joined #openstack-meeting21:55
*** salv-orlando has joined #openstack-meeting21:55
*** rtheis has quit IRC21:56
*** thorst has quit IRC21:57
*** dmowrer has quit IRC21:58
*** kebray has joined #openstack-meeting21:59
*** mudassirlatif has joined #openstack-meeting22:00
*** njohnston has quit IRC22:00
*** weshay_xchat has quit IRC22:00
*** apoorvad has joined #openstack-meeting22:00
*** thorst has joined #openstack-meeting22:02
*** Sukhdev has joined #openstack-meeting22:02
*** alexpilotti has joined #openstack-meeting22:02
*** hashar has quit IRC22:03
*** tej has joined #openstack-meeting22:04
*** thorst has quit IRC22:06
*** john-davidge has joined #openstack-meeting22:06
*** alexpilotti has quit IRC22:07
*** vgridnev has quit IRC22:11
*** baoli has joined #openstack-meeting22:11
*** davechen has left #openstack-meeting22:12
*** dmowrer has joined #openstack-meeting22:12
*** salv-orlando has quit IRC22:12
*** salv-orlando has joined #openstack-meeting22:13
*** weshay_xchat has joined #openstack-meeting22:13
*** zz_john5223 has quit IRC22:13
*** tej has quit IRC22:14
*** baoli has quit IRC22:14
*** dtroyer has quit IRC22:14
*** dtroyer has joined #openstack-meeting22:15
*** rderose has quit IRC22:15
*** kencjohnston has quit IRC22:16
*** jichen has quit IRC22:16
*** dmowrer has quit IRC22:16
*** zz_john5223 has joined #openstack-meeting22:16
*** sacharya has quit IRC22:18
*** salv-orl_ has joined #openstack-meeting22:18
*** baoli has joined #openstack-meeting22:18
*** lblanchard has quit IRC22:18
*** alexpilotti has joined #openstack-meeting22:19
*** egallen has joined #openstack-meeting22:19
*** thorst has joined #openstack-meeting22:19
*** harlowja has quit IRC22:19
*** maishsk_ has joined #openstack-meeting22:19
*** dwalleck has joined #openstack-meeting22:20
*** maishsk has quit IRC22:20
*** maishsk_ is now known as maishsk22:20
*** ayoung has quit IRC22:21
*** harlowja has joined #openstack-meeting22:21
*** dwalleck has quit IRC22:22
*** gyee has joined #openstack-meeting22:22
*** dwalleck_ has joined #openstack-meeting22:23
*** salv-orlando has quit IRC22:23
*** thorst has quit IRC22:24
*** baoli has quit IRC22:24
*** mwagner_lap has quit IRC22:24
*** alexpilotti has quit IRC22:25
*** baoli has joined #openstack-meeting22:25
*** Sukhdev has quit IRC22:26
*** dwalleck_ has quit IRC22:27
*** kebray has quit IRC22:27
*** dwalleck has joined #openstack-meeting22:29
*** dwalleck has quit IRC22:29
*** maishsk has quit IRC22:29
*** maishsk has joined #openstack-meeting22:29
*** dwalleck has joined #openstack-meeting22:30
*** kebray has joined #openstack-meeting22:31
*** galstrom is now known as galstrom_zzz22:31
*** baoli has quit IRC22:34
*** roxanagh_ has joined #openstack-meeting22:35
*** peristeri has quit IRC22:38
*** absubram has quit IRC22:39
*** roxanagh_ has quit IRC22:40
*** amitgandhinz has quit IRC22:40
*** otter768 has joined #openstack-meeting22:43
*** megm has quit IRC22:44
*** dmacpher has quit IRC22:44
*** megm has joined #openstack-meeting22:45
*** hemnafk is now known as hemna22:45
*** adiantum has joined #openstack-meeting22:46
*** mhickey has quit IRC22:46
*** sgundur has quit IRC22:46
*** thorst has joined #openstack-meeting22:47
*** otter768 has quit IRC22:48
*** thorst_ has joined #openstack-meeting22:48
*** thorst has quit IRC22:52
*** kebray has quit IRC22:53
*** chmouel has quit IRC22:55
*** chmouel has joined #openstack-meeting22:56
*** salv-orl_ has quit IRC22:56
*** harlowja has quit IRC22:57
*** bobh has quit IRC22:57
*** alop has quit IRC22:57
*** Leom has quit IRC22:59
*** jmckind has quit IRC23:01
*** pm90_ has quit IRC23:01
*** harlowja has joined #openstack-meeting23:01
*** dmacpher has joined #openstack-meeting23:02
*** dkranz has quit IRC23:02
*** alexpilotti has joined #openstack-meeting23:02
*** alexpilotti has quit IRC23:06
*** neelashah has quit IRC23:08
*** TravT has quit IRC23:10
*** dimtruck is now known as zz_dimtruck23:10
*** scinawa has quit IRC23:10
*** MaxPC has joined #openstack-meeting23:10
*** scinawa has joined #openstack-meeting23:12
*** eharney has quit IRC23:15
*** kebray has joined #openstack-meeting23:16
*** sdake has joined #openstack-meeting23:16
*** mudassirlatif has quit IRC23:16
*** rockyg has quit IRC23:16
*** dwalleck has quit IRC23:16
*** manjeets has quit IRC23:19
*** alexpilotti has joined #openstack-meeting23:19
*** alexpilotti has quit IRC23:23
*** kebray has quit IRC23:24
*** david-lyle has quit IRC23:25
*** emagana has quit IRC23:26
*** emagana has joined #openstack-meeting23:27
*** mwagner_lap has joined #openstack-meeting23:27
*** xyang1 has quit IRC23:29
*** emagana_ has joined #openstack-meeting23:29
*** darrenc is now known as darrenc_afk23:31
*** penick has quit IRC23:31
*** emagana has quit IRC23:31
*** emagana_ has quit IRC23:33
*** spotz is now known as spotz_zzz23:34
*** e0ne has joined #openstack-meeting23:34
*** kebray has joined #openstack-meeting23:34
*** iyamahat has quit IRC23:35
*** kebray has quit IRC23:35
*** iyamahat has joined #openstack-meeting23:35
*** iyamahat has quit IRC23:35
*** iyamahat has joined #openstack-meeting23:36
*** kebray has joined #openstack-meeting23:36
*** e0ne has quit IRC23:36
*** kebray has quit IRC23:36
*** roxanagh_ has joined #openstack-meeting23:36
*** sdake has quit IRC23:36
*** e0ne has joined #openstack-meeting23:36
*** ayoung has joined #openstack-meeting23:37
*** MaxPC has quit IRC23:38
*** sdake has joined #openstack-meeting23:39
*** e0ne_ has joined #openstack-meeting23:39
*** Guest28145 has quit IRC23:39
*** egarbade- has joined #openstack-meeting23:39
*** tochi has joined #openstack-meeting23:40
*** roxanagh_ has quit IRC23:41
*** e0ne has quit IRC23:41
*** dstanek has quit IRC23:41
*** dstanek has joined #openstack-meeting23:41
*** MarkAtwood has quit IRC23:42
*** topol has joined #openstack-meeting23:43
*** penick has joined #openstack-meeting23:46
*** jruano has joined #openstack-meeting23:46
*** amitgandhinz has joined #openstack-meeting23:47
*** topol has quit IRC23:48
*** e0ne has joined #openstack-meeting23:49
*** e0ne_ has quit IRC23:51
*** weshay_xchat has quit IRC23:51
*** amitgandhinz has quit IRC23:51
*** darrenc_afk is now known as darrenc23:52
*** e0ne_ has joined #openstack-meeting23:52
*** jingyizhaobo has quit IRC23:52
*** jingyizhaobo has joined #openstack-meeting23:53
*** e0ne has quit IRC23:54
*** tej has joined #openstack-meeting23:55
*** pballand has quit IRC23:56
*** jklare has quit IRC23:57
*** jklare has joined #openstack-meeting23:58
*** salv-orlando has joined #openstack-meeting23:59

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