Tuesday, 2015-09-08

*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-meeting00:01
*** dmacpher has joined #openstack-meeting00:02
*** dimsum__ has quit IRC00:03
*** Brian has joined #openstack-meeting00:05
*** pm90_ has quit IRC00:05
*** Brian is now known as Guest2128000:05
*** Guest21280 has quit IRC00:09
*** yamamoto has joined #openstack-meeting00:12
*** kebray has joined #openstack-meeting00:17
*** yamamoto has quit IRC00:17
*** sdake has joined #openstack-meeting00:18
*** zhhuabj has joined #openstack-meeting00:19
*** otter768 has joined #openstack-meeting00:22
*** oomichi has joined #openstack-meeting00:22
*** ivasev has quit IRC00:23
*** banix has joined #openstack-meeting00:23
*** ivasev has joined #openstack-meeting00:23
*** johnhunter has joined #openstack-meeting00:23
*** puranamr has quit IRC00:24
*** puranamr has joined #openstack-meeting00:26
*** otter768 has quit IRC00:27
*** otter768_ has joined #openstack-meeting00:27
*** otter768_ has quit IRC00:27
*** geoffarnold is now known as geoffarnoldX00:27
*** otter768 has joined #openstack-meeting00:27
*** banix has quit IRC00:27
*** ivasev has quit IRC00:27
*** yamamoto has joined #openstack-meeting00:28
*** asettle is now known as asettle-afk00:29
*** eliqiao has joined #openstack-meeting00:29
*** yamamoto has quit IRC00:32
*** lukebrooker has quit IRC00:32
*** tiswanso has joined #openstack-meeting00:35
*** haomaiwang has quit IRC00:36
*** lblanchard has joined #openstack-meeting00:36
*** xingchao has joined #openstack-meeting00:37
*** tiswanso has quit IRC00:38
*** tiswanso has joined #openstack-meeting00:39
*** otter768 has quit IRC00:41
*** esker has quit IRC00:42
*** yamamoto has joined #openstack-meeting00:43
*** xingchao has quit IRC00:44
*** yamamoto has quit IRC00:47
*** dimsum__ has joined #openstack-meeting00:48
*** puranamr has quit IRC00:49
*** esker has joined #openstack-meeting00:50
*** puranamr has joined #openstack-meeting00:51
*** aeng_ has quit IRC00:54
*** kencjohn_ has quit IRC00:57
*** armax has joined #openstack-meeting01:00
*** electrocucaracha has quit IRC01:02
*** aloga has quit IRC01:04
*** rossella_s has quit IRC01:06
*** aloga has joined #openstack-meeting01:06
*** Brian has joined #openstack-meeting01:06
*** rossella_s has joined #openstack-meeting01:06
*** Brian is now known as Guest9092001:06
*** baojg has joined #openstack-meeting01:07
*** xingchao has joined #openstack-meeting01:07
*** Guest90920 has quit IRC01:10
*** patchbot has quit IRC01:11
*** patchbot` has joined #openstack-meeting01:11
*** jd__ has quit IRC01:12
*** patchbot` is now known as patchbot01:12
*** ricolin has joined #openstack-meeting01:12
ricolin /msg NickServ identify suns040901:12
*** jd__ has joined #openstack-meeting01:12
*** ganeshna has joined #openstack-meeting01:14
*** galstrom_zzz is now known as galstrom01:15
*** claudiub|2 has quit IRC01:17
*** vivek-ebay has joined #openstack-meeting01:17
*** xingchao has quit IRC01:21
*** asettle-afk is now known as asettle01:22
*** vivek-ebay has quit IRC01:22
*** armax has quit IRC01:28
*** moha_hunt has quit IRC01:31
*** otter768 has joined #openstack-meeting01:32
*** esker has quit IRC01:32
*** galstrom is now known as galstrom_zzz01:33
*** ganeshna has quit IRC01:33
*** esker has joined #openstack-meeting01:33
*** haomaiwang has joined #openstack-meeting01:35
*** lukebrooker has joined #openstack-meeting01:36
*** pm90_ has joined #openstack-meeting01:36
*** eliqiao has quit IRC01:38
*** banix has joined #openstack-meeting01:39
*** dimsum__ has quit IRC01:40
*** adiantum has quit IRC01:41
*** nadya has joined #openstack-meeting01:42
*** pm90_ has quit IRC01:42
*** eliqiao has joined #openstack-meeting01:43
*** nadya has quit IRC01:46
*** sballe has quit IRC01:46
*** chenzeng has joined #openstack-meeting01:48
*** armax has joined #openstack-meeting01:51
*** david-ly_ has joined #openstack-meeting01:51
*** krtaylor has quit IRC01:52
*** bknudson has quit IRC01:52
*** FallenPegasus has quit IRC01:53
*** fzdarsky_ has joined #openstack-meeting01:54
*** baoli has joined #openstack-meeting01:54
*** Brian has joined #openstack-meeting01:54
*** david-lyle has quit IRC01:54
*** Brian is now known as Guest1262401:55
*** Guest12624 has quit IRC01:56
*** esker has quit IRC01:57
*** FallenPegasus has joined #openstack-meeting01:57
*** yamamoto has joined #openstack-meeting01:57
*** fzdarsky has quit IRC01:57
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-meeting02:01
*** yamamoto has quit IRC02:02
*** yamamoto has joined #openstack-meeting02:04
*** otter768 has quit IRC02:04
*** krtaylor has joined #openstack-meeting02:05
*** otter768 has joined #openstack-meeting02:06
*** esker has joined #openstack-meeting02:06
*** yamamoto has quit IRC02:10
*** xingchao has joined #openstack-meeting02:11
*** FallenPegasus has quit IRC02:13
*** baoli has quit IRC02:16
*** puranamr has quit IRC02:25
*** zhhuabj has quit IRC02:25
*** puranamr has joined #openstack-meeting02:27
*** dneary has joined #openstack-meeting02:28
*** puranamr has quit IRC02:30
*** esker has quit IRC02:31
*** puranamr has joined #openstack-meeting02:31
*** zhhuabj has joined #openstack-meeting02:37
*** noslzzp has quit IRC02:37
*** esker has joined #openstack-meeting02:38
*** gongysh has joined #openstack-meeting02:39
*** armax has quit IRC02:40
*** dimsum__ has joined #openstack-meeting02:40
*** JRobinson__ is now known as JRobinson__afk02:42
*** Brian has joined #openstack-meeting02:46
*** Brian is now known as Guest6983802:46
*** dimsum__ has quit IRC02:46
*** amotoki has joined #openstack-meeting02:48
*** vivek-ebay has joined #openstack-meeting02:49
*** wbhuber has quit IRC02:49
*** galstrom_zzz is now known as galstrom02:51
*** mattgriffin has joined #openstack-meeting02:51
*** dneary has quit IRC02:52
*** galstrom is now known as galstrom_zzz02:53
*** baoli has joined #openstack-meeting02:55
*** yamamoto has joined #openstack-meeting02:56
*** gongysh_ has joined #openstack-meeting03:00
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-meeting03:01
*** armax has joined #openstack-meeting03:03
*** puranamr has quit IRC03:04
*** gongysh has quit IRC03:04
*** armax has quit IRC03:04
*** puranamr has joined #openstack-meeting03:05
*** gongysh__ has joined #openstack-meeting03:05
*** esker has quit IRC03:05
*** zhhuabj has quit IRC03:08
*** gongysh_ has quit IRC03:09
*** tiswanso has quit IRC03:10
*** esker has joined #openstack-meeting03:10
*** epico has joined #openstack-meeting03:10
*** nijaba has joined #openstack-meeting03:10
*** nijaba has quit IRC03:10
*** nijaba has joined #openstack-meeting03:10
*** yingjun has joined #openstack-meeting03:11
*** yunpengli has joined #openstack-meeting03:14
*** sankarshan_away is now known as sankarshan03:15
*** luqas has joined #openstack-meeting03:15
*** JRobinson__afk has quit IRC03:16
*** lblanchard has quit IRC03:19
*** yunpengli has quit IRC03:20
*** VW_ has joined #openstack-meeting03:20
*** yingjun has quit IRC03:22
*** yingjun has joined #openstack-meeting03:22
*** VW_ has quit IRC03:22
*** VW_ has joined #openstack-meeting03:23
*** gongysh_ has joined #openstack-meeting03:25
*** esker has quit IRC03:26
*** puranamr has quit IRC03:26
*** yingjun has quit IRC03:27
*** VW_ has quit IRC03:28
*** codebauss has left #openstack-meeting03:28
*** gongysh__ has quit IRC03:29
*** persia has quit IRC03:30
*** baojg has quit IRC03:31
*** Guest69838 has quit IRC03:31
*** banix has quit IRC03:31
*** liusheng has joined #openstack-meeting03:32
*** persia has joined #openstack-meeting03:32
*** esker has joined #openstack-meeting03:35
*** otter768 has quit IRC03:35
*** otter768 has joined #openstack-meeting03:37
*** yunpengli has joined #openstack-meeting03:42
*** yunpengli has quit IRC03:42
*** mattgriffin has quit IRC03:45
*** yingjun has joined #openstack-meeting03:46
*** otter768 has quit IRC03:46
*** Brian has joined #openstack-meeting03:46
*** Brian is now known as Guest7404303:47
*** julim has quit IRC03:47
*** gongysh__ has joined #openstack-meeting03:50
*** esker has quit IRC03:54
*** gongysh_ has quit IRC03:54
*** puranamr has joined #openstack-meeting03:54
*** vivekd has joined #openstack-meeting03:54
*** baoli has quit IRC03:55
*** yingjun has quit IRC03:56
*** yingjun has joined #openstack-meeting03:57
*** armax has joined #openstack-meeting03:57
*** puranamr has quit IRC03:57
*** puranamr has joined #openstack-meeting03:58
*** haomaiwang has quit IRC04:01
*** esker has joined #openstack-meeting04:01
*** haomaiwang has joined #openstack-meeting04:01
*** Guest74043 has quit IRC04:01
*** yingjun has quit IRC04:04
*** baojg has joined #openstack-meeting04:04
*** gongysh_ has joined #openstack-meeting04:04
*** lazy_prince has joined #openstack-meeting04:05
*** oomichi has quit IRC04:05
*** yfried has quit IRC04:06
*** gongysh__ has quit IRC04:08
*** gongysh_ has quit IRC04:09
*** vivek-eb_ has joined #openstack-meeting04:10
*** JRobinson__afk has joined #openstack-meeting04:12
*** JRobinson__afk is now known as JRobinson__04:12
*** vivek-ebay has quit IRC04:13
*** vivek-eb_ is now known as vivek04:14
*** vivek is now known as Guest7918804:14
*** epico has quit IRC04:16
*** vivekd has quit IRC04:17
*** kebray has quit IRC04:18
*** aranjan has joined #openstack-meeting04:18
*** kebray has joined #openstack-meeting04:18
*** puranamr has quit IRC04:18
*** puranamr has joined #openstack-meeting04:19
*** resker has joined #openstack-meeting04:23
*** Guest79188 has quit IRC04:23
*** chenzeng has quit IRC04:23
*** esker has quit IRC04:24
*** epico has joined #openstack-meeting04:26
*** FallenPegasus has joined #openstack-meeting04:33
*** unicell1 has joined #openstack-meeting04:33
*** FallenPegasus has quit IRC04:34
*** unicell has quit IRC04:34
*** hrou has quit IRC04:35
*** FallenPegasus has joined #openstack-meeting04:35
*** FallenPegasus has quit IRC04:36
*** yamahata has joined #openstack-meeting04:37
*** vivekd has joined #openstack-meeting04:39
*** pm90_ has joined #openstack-meeting04:39
*** kebray_ has joined #openstack-meeting04:41
*** kebray has quit IRC04:43
*** pm90_ has quit IRC04:44
*** resker has quit IRC04:44
*** SridharG has joined #openstack-meeting04:46
*** esker has joined #openstack-meeting04:48
*** FallenPegasus has joined #openstack-meeting04:50
*** tfukushima has joined #openstack-meeting04:51
*** FallenPegasus has quit IRC04:51
*** ildikov has quit IRC04:53
*** xingchao has quit IRC05:00
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** ganeshna has joined #openstack-meeting05:09
*** nadya has joined #openstack-meeting05:14
*** numans has joined #openstack-meeting05:15
*** esker has quit IRC05:16
*** xingchao has joined #openstack-meeting05:18
*** vivek has joined #openstack-meeting05:20
*** vivek is now known as Guest4609505:20
*** esker has joined #openstack-meeting05:22
*** ganeshna has quit IRC05:22
*** xingchao has quit IRC05:23
*** armax has quit IRC05:24
*** Guest46095 has quit IRC05:24
*** mrmartin has joined #openstack-meeting05:25
*** ganeshna has joined #openstack-meeting05:30
*** armax has joined #openstack-meeting05:31
*** xingchao has joined #openstack-meeting05:32
*** yfried has joined #openstack-meeting05:32
*** yfried_ has joined #openstack-meeting05:35
*** yfried has quit IRC05:36
*** BharatK has joined #openstack-meeting05:39
*** esker has quit IRC05:45
*** vgridnev has joined #openstack-meeting05:45
*** yingjun has joined #openstack-meeting05:46
*** otter768 has joined #openstack-meeting05:47
*** xingchao has quit IRC05:48
*** armax has quit IRC05:48
*** elo has quit IRC05:49
*** esker has joined #openstack-meeting05:51
*** otter768 has quit IRC05:52
*** yfried_ is now known as yfried|afk05:54
*** vivek has joined #openstack-meeting05:54
*** vivek is now known as Guest107105:54
*** nadya has quit IRC05:55
*** yingjun has quit IRC05:55
*** nadya has joined #openstack-meeting05:57
*** nadya has quit IRC05:58
*** irenab has joined #openstack-meeting05:58
*** gampel has joined #openstack-meeting05:59
*** xingchao has joined #openstack-meeting06:00
*** xingchao has quit IRC06:00
*** haomaiwang has quit IRC06:01
*** mrunge has joined #openstack-meeting06:01
*** alexpilotti_ has joined #openstack-meeting06:01
*** haomaiwang has joined #openstack-meeting06:01
*** irenab has quit IRC06:01
*** chandankumar has joined #openstack-meeting06:02
*** yfried|afk is now known as yfried_06:03
*** lpetrut has joined #openstack-meeting06:05
*** xingchao_ has joined #openstack-meeting06:06
*** aranjan has quit IRC06:08
*** smeisner has quit IRC06:09
*** radez has quit IRC06:10
*** radez has joined #openstack-meeting06:10
*** lukebrooker has quit IRC06:11
*** smeisner has joined #openstack-meeting06:11
*** mattoliverau has quit IRC06:13
*** nadya has joined #openstack-meeting06:13
*** matrohon has quit IRC06:14
*** mattoliverau has joined #openstack-meeting06:14
*** Guest1071 has quit IRC06:17
*** garyk has joined #openstack-meeting06:21
*** lpetrut has quit IRC06:22
*** esker has quit IRC06:25
*** lukebrooker has joined #openstack-meeting06:25
*** elo has joined #openstack-meeting06:25
*** mpaolino has joined #openstack-meeting06:26
*** baoli has joined #openstack-meeting06:26
*** Brian has joined #openstack-meeting06:27
*** esker has joined #openstack-meeting06:27
*** Brian is now known as Guest7338906:27
*** yfried_ is now known as yfried|afk06:29
*** baoli has quit IRC06:31
*** JRobinson__ has quit IRC06:31
*** Murali has joined #openstack-meeting06:32
*** salv-orlando has joined #openstack-meeting06:33
*** puranamr has quit IRC06:35
*** baojg has quit IRC06:36
*** gampel1 has joined #openstack-meeting06:41
*** baigk has quit IRC06:42
*** gampel has quit IRC06:44
*** esker has quit IRC06:45
*** baigk has joined #openstack-meeting06:46
*** lsmola has joined #openstack-meeting06:47
*** sankarshan is now known as sankarshan_away06:48
*** sudipto has joined #openstack-meeting06:50
*** esker has joined #openstack-meeting06:50
*** irenab has joined #openstack-meeting06:53
*** pnavarro has joined #openstack-meeting06:55
*** pnavarro is now known as pnavarro|mtg06:58
*** kebray_ has quit IRC06:59
*** peristeri has joined #openstack-meeting07:00
*** SridharG has quit IRC07:00
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-meeting07:01
*** sankarshan_away is now known as sankarshan07:03
*** zz_ttrifonov is now known as ttrifonov07:03
*** ganeshna has quit IRC07:03
*** lukebrooker has quit IRC07:05
*** yamahata has quit IRC07:07
*** aranjan has joined #openstack-meeting07:09
*** ildikov has joined #openstack-meeting07:10
*** ianychoi has quit IRC07:10
*** fifieldt has joined #openstack-meeting07:13
*** alexschm has joined #openstack-meeting07:13
*** ianychoi has joined #openstack-meeting07:14
*** hashar has joined #openstack-meeting07:15
*** esker has quit IRC07:17
*** ijw_ has joined #openstack-meeting07:18
*** Jeffrey4l has joined #openstack-meeting07:20
*** aranjan has quit IRC07:22
*** hashar has quit IRC07:23
*** esker has joined #openstack-meeting07:23
*** liusheng has quit IRC07:23
*** hashar has joined #openstack-meeting07:24
*** park__ has quit IRC07:27
*** SridharG has joined #openstack-meeting07:28
*** jtomasek has joined #openstack-meeting07:28
*** dmacpher has quit IRC07:29
*** yassine__ has joined #openstack-meeting07:30
*** asettle has quit IRC07:32
*** Guest32267 is now known as d0ugal07:32
*** d0ugal has joined #openstack-meeting07:32
*** jtomasek has quit IRC07:37
*** jhenner has joined #openstack-meeting07:39
*** jlanoux has joined #openstack-meeting07:40
*** yfried|afk is now known as yfried_07:40
*** achanda has joined #openstack-meeting07:43
*** adahms has quit IRC07:43
*** irenab has quit IRC07:43
*** nagromlt has joined #openstack-meeting07:43
*** pnavarro|mtg has quit IRC07:45
*** phil_ has joined #openstack-meeting07:45
*** aranjan has joined #openstack-meeting07:48
*** jtomasek has joined #openstack-meeting07:48
*** otter768 has joined #openstack-meeting07:48
*** safchain has joined #openstack-meeting07:51
*** yfried_ is now known as yfried|afk07:51
*** ganeshna has joined #openstack-meeting07:51
*** esker has quit IRC07:52
*** otter768 has quit IRC07:53
*** ganeshna has quit IRC07:57
*** neeti has joined #openstack-meeting07:57
*** esker has joined #openstack-meeting07:59
*** ganeshna has joined #openstack-meeting07:59
*** ygbo has joined #openstack-meeting08:00
*** ganeshna has quit IRC08:00
*** aranjan has quit IRC08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Sep  8 08:00:50 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
anteayahello08:00
lennybHi08:01
*** haomaiwang has quit IRC08:01
*** rvasilets has joined #openstack-meeting08:01
anteayahey lennyb08:01
*** haomaiwang has joined #openstack-meeting08:01
*** baojg has joined #openstack-meeting08:01
*** lpetrut has joined #openstack-meeting08:01
anteayahow are you today?08:01
lennybok, thank you. how are you ?08:02
*** ijw_ has quit IRC08:02
anteayagood thank you08:03
anteayaanything to discuss in this meeting?08:03
lennybi have nothing to ask today, so ....08:03
anteayaokay thanks08:03
anteayawe will see if anyone else shows up08:03
anteayathanks for being here :)08:03
*** zeih has joined #openstack-meeting08:06
*** toscalix__ has joined #openstack-meeting08:06
*** matrohon has joined #openstack-meeting08:09
*** jcoufal has joined #openstack-meeting08:09
*** ganeshna has joined #openstack-meeting08:11
*** ociuhandu has quit IRC08:12
*** vgridnev has quit IRC08:12
*** yfried|afk is now known as yfried_08:14
anteayaanyone else here with anything to discuss?08:17
anteayaI think I will close the meeting08:17
lennybhave a good day...08:17
*** baojg has quit IRC08:18
anteayathanks for being here lennyb08:18
anteayathanks you too08:18
anteayasee you next week08:18
anteaya#endmeeting08:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:18
openstackMeeting ended Tue Sep  8 08:18:15 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-08-08.00.html08:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-08-08.00.txt08:18
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-08-08.00.log.html08:18
*** scinawa has quit IRC08:19
*** baigk has quit IRC08:20
*** ^Gal^ has joined #openstack-meeting08:21
*** baigk has joined #openstack-meeting08:21
*** Jeffrey4l has quit IRC08:23
*** Jeffrey4l has joined #openstack-meeting08:24
*** esker has quit IRC08:24
*** nagromlt has quit IRC08:25
*** achanda has quit IRC08:25
*** yfried_ is now known as yfried|afk08:25
*** SridharG has left #openstack-meeting08:26
*** aranjan has joined #openstack-meeting08:26
*** SridharG has joined #openstack-meeting08:27
*** jhenner has quit IRC08:27
*** neeti has quit IRC08:27
*** achanda has joined #openstack-meeting08:28
*** aranjan has quit IRC08:28
*** aranjan has joined #openstack-meeting08:28
*** yfried|afk is now known as yfried_08:28
*** pm90_ has joined #openstack-meeting08:29
*** esker has joined #openstack-meeting08:29
*** ganeshna has quit IRC08:29
*** neeti has joined #openstack-meeting08:29
*** zhhuabj has joined #openstack-meeting08:29
*** pedroalvarez has quit IRC08:30
*** pedroalvarez has joined #openstack-meeting08:31
*** elo has quit IRC08:33
*** pm90_ has quit IRC08:33
*** irenab has joined #openstack-meeting08:34
*** ganeshna has joined #openstack-meeting08:40
*** pnavarro has joined #openstack-meeting08:40
*** Venky has joined #openstack-meeting08:43
*** andreykurilin has quit IRC08:43
*** andreykurilin has joined #openstack-meeting08:44
*** pelix has joined #openstack-meeting08:44
*** baojg has joined #openstack-meeting08:46
*** derekh has joined #openstack-meeting08:46
*** vjay13 has joined #openstack-meeting08:48
*** bobmel has joined #openstack-meeting08:51
*** achanda has quit IRC08:52
*** yingjun has joined #openstack-meeting08:52
*** aix has quit IRC08:53
*** esker has quit IRC08:54
*** yingjun has quit IRC08:55
*** xingchao_ has quit IRC08:56
*** vjay13 has quit IRC08:57
*** vgridnev has joined #openstack-meeting08:58
*** ^Gal^ has quit IRC08:59
*** ganeshna has quit IRC09:00
*** aranjan has quit IRC09:00
*** haomaiwang has quit IRC09:01
*** haomaiwa_ has joined #openstack-meeting09:01
*** xingchao has joined #openstack-meeting09:02
*** ildikov has quit IRC09:02
*** ganeshna has joined #openstack-meeting09:03
*** esker has joined #openstack-meeting09:05
*** hoangcx has joined #openstack-meeting09:06
*** gampel has joined #openstack-meeting09:06
*** gampel1 has quit IRC09:07
*** zhhuabj has quit IRC09:09
*** hoangcx has quit IRC09:10
*** wuhg has quit IRC09:11
*** xingchao has quit IRC09:11
*** xingchao has joined #openstack-meeting09:11
*** hoangcx has joined #openstack-meeting09:11
*** Daisy has joined #openstack-meeting09:16
*** e0ne has joined #openstack-meeting09:16
*** yingjun has joined #openstack-meeting09:16
*** Guest73389 has quit IRC09:17
*** Brian has joined #openstack-meeting09:17
*** neeti has quit IRC09:18
*** Brian is now known as Guest5896409:18
*** aix has joined #openstack-meeting09:18
*** neeti has joined #openstack-meeting09:19
*** ^Gal^ has joined #openstack-meeting09:21
*** afazekas_ has joined #openstack-meeting09:22
*** afazekas_ has quit IRC09:22
*** nadya has quit IRC09:22
*** afazekas_ has joined #openstack-meeting09:23
*** Jeffrey4l has quit IRC09:24
*** esker has quit IRC09:25
*** armax has joined #openstack-meeting09:27
*** ganeshna has quit IRC09:31
*** ganeshna has joined #openstack-meeting09:32
*** yingjun has quit IRC09:33
*** esker has joined #openstack-meeting09:33
*** ganeshna has quit IRC09:34
*** salv-orlando has quit IRC09:36
*** Jeffrey4l has joined #openstack-meeting09:36
*** Daisy has quit IRC09:37
*** Venky has quit IRC09:37
*** Daisy has joined #openstack-meeting09:37
*** nadya has joined #openstack-meeting09:37
*** miyagishi_t has quit IRC09:39
*** ildikov has joined #openstack-meeting09:39
*** Daisy_ has joined #openstack-meeting09:41
*** e0ne has quit IRC09:41
*** Daisy has quit IRC09:42
*** sdake has quit IRC09:42
*** dimsum__ has joined #openstack-meeting09:46
*** Daisy_ has quit IRC09:46
*** ganeshna has joined #openstack-meeting09:48
*** otter768 has joined #openstack-meeting09:49
*** jlvillal has quit IRC09:50
*** jlvillal has joined #openstack-meeting09:50
*** dims_ has joined #openstack-meeting09:50
*** matrohon has quit IRC09:51
*** yamamoto has quit IRC09:53
*** otter768 has quit IRC09:54
*** honghui has joined #openstack-meeting09:54
*** dimsum__ has quit IRC09:55
*** baojg has quit IRC09:56
*** baojg has joined #openstack-meeting09:56
*** aranjan has joined #openstack-meeting09:57
*** jhenner has joined #openstack-meeting09:57
*** e0ne has joined #openstack-meeting09:57
*** ildikov has quit IRC10:00
*** baojg has quit IRC10:00
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-meeting10:01
*** IanGovett has joined #openstack-meeting10:02
*** esker has quit IRC10:05
*** tfukushima has quit IRC10:05
*** ociuhandu has joined #openstack-meeting10:07
*** esker has joined #openstack-meeting10:11
*** ildikov has joined #openstack-meeting10:14
*** lyanchih has joined #openstack-meeting10:20
*** jlvillal has quit IRC10:22
*** ricolin has quit IRC10:27
*** yfried_ is now known as yfried|afk10:27
*** Guest58964 has quit IRC10:28
*** jlanoux_ has joined #openstack-meeting10:28
*** irenab has quit IRC10:29
*** julim has joined #openstack-meeting10:29
*** aranjan has quit IRC10:30
*** jlanoux has quit IRC10:31
*** yfried|afk is now known as yfried_10:31
*** irenab has joined #openstack-meeting10:31
*** GB21 has joined #openstack-meeting10:32
*** julim has quit IRC10:33
*** esker has quit IRC10:33
*** irenab has quit IRC10:33
*** aix has quit IRC10:35
*** yamamoto has joined #openstack-meeting10:36
*** irenab has joined #openstack-meeting10:37
*** irenab has quit IRC10:37
*** lukebrooker has joined #openstack-meeting10:37
*** irenab has joined #openstack-meeting10:38
*** esker has joined #openstack-meeting10:39
*** baoli has joined #openstack-meeting10:42
*** adiantum has joined #openstack-meeting10:44
*** jlanoux has joined #openstack-meeting10:44
*** jtomasek has quit IRC10:45
*** epico has quit IRC10:45
*** jtomasek has joined #openstack-meeting10:45
*** hashar has quit IRC10:47
*** baoli has quit IRC10:47
*** jlanoux_ has quit IRC10:47
*** Brian has joined #openstack-meeting10:49
*** Brian is now known as Guest3475810:49
*** SridharG has quit IRC10:50
*** yfried_ is now known as yfried|afk10:52
*** Guest34758 has quit IRC10:53
*** ikhudoshyn has joined #openstack-meeting10:54
*** claudiub has joined #openstack-meeting10:57
*** SridharG has joined #openstack-meeting10:58
*** lyanchih has quit IRC10:58
*** yamamoto has quit IRC10:58
*** salv-orlando has joined #openstack-meeting11:00
*** lukebrooker has quit IRC11:00
*** gampel has quit IRC11:00
*** chenzeng has joined #openstack-meeting11:00
*** gampel has joined #openstack-meeting11:00
*** SridharG has left #openstack-meeting11:00
*** haomaiwang has quit IRC11:01
*** 92AAB1O7Y has joined #openstack-meeting11:01
*** SridharG has joined #openstack-meeting11:03
*** jlvillal has joined #openstack-meeting11:03
*** ildikov has quit IRC11:04
*** ganeshna has quit IRC11:05
*** yfried|afk is now known as yfried_11:05
*** ildikov has joined #openstack-meeting11:08
*** esker has quit IRC11:10
*** pnavarro is now known as pnavarro|lunch11:11
*** 92AAB1O7Y has quit IRC11:12
*** amrith is now known as _amrith_11:16
*** esker has joined #openstack-meeting11:18
*** xingchao has quit IRC11:20
*** hoangcx has quit IRC11:21
*** ikhudoshyn has quit IRC11:25
*** marcusvrn_ has joined #openstack-meeting11:25
*** yingjun has joined #openstack-meeting11:26
*** aranjan has joined #openstack-meeting11:27
*** yingjun has quit IRC11:28
*** yingjun has joined #openstack-meeting11:28
*** markd_ has quit IRC11:30
*** jaypipes has joined #openstack-meeting11:31
*** doug-fish has joined #openstack-meeting11:31
*** sudipto has quit IRC11:32
*** yingjun has quit IRC11:33
*** esker has quit IRC11:36
*** GB21 has quit IRC11:37
*** niska has quit IRC11:39
*** hashar has joined #openstack-meeting11:41
*** tochi has quit IRC11:41
*** yfried_ is now known as yfried|afk11:44
*** niska has joined #openstack-meeting11:45
*** esker has joined #openstack-meeting11:45
*** chandankumar has quit IRC11:46
*** pm90_ has joined #openstack-meeting11:46
*** dneary has joined #openstack-meeting11:50
*** pm90_ has quit IRC11:50
*** otter768 has joined #openstack-meeting11:50
*** pm90_ has joined #openstack-meeting11:50
*** dane_leblanc has joined #openstack-meeting11:51
*** mklyus has joined #openstack-meeting11:52
*** gmann_ has joined #openstack-meeting11:52
*** neeti has quit IRC11:52
*** rvasilets has quit IRC11:55
*** otter768 has quit IRC11:55
*** ebagdasa has joined #openstack-meeting11:55
*** chenzeng has quit IRC11:55
*** rfolco has joined #openstack-meeting11:56
*** jecarey has quit IRC11:56
*** Jeffrey4l has quit IRC11:57
*** cdub has quit IRC11:58
*** yfried|afk is now known as yfried_11:58
*** yamamoto has joined #openstack-meeting11:59
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Sep  8 12:00:04 2015 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho is here today?12:00
edleafeo/12:00
gmann_o/12:00
johnthetubaguyo/12:00
alex_xuhello everyone12:00
alex_xulet's start the meeting12:01
alex_xu#topic actions from last meeting12:01
*** openstack changes topic to "actions from last meeting (Meeting topic: nova api)"12:01
*** gampel1 has joined #openstack-meeting12:01
alex_xusdague to write up test plan for v2.x nova, alex_xu and gmann_ will work on patches12:01
*** aranjan has quit IRC12:01
*** gampel has quit IRC12:01
*** mwagner_lap has quit IRC12:01
alex_xuactually sdague did all the things :)12:01
gmann_yea12:01
alex_xu#link https://review.openstack.org/#/c/219370/12:01
alex_xu#link https://review.openstack.org/#/c/219347/12:01
*** e0ne has quit IRC12:01
alex_xuall of that are merged12:02
alex_xuthere is last one from gmann_12:02
alex_xu#link https://review.openstack.org/#/c/219553/12:02
alex_xuI think this is all for gate12:02
*** safchain has quit IRC12:02
*** codebauss has joined #openstack-meeting12:02
gmann_#link https://review.openstack.org/#/c/219555/12:03
alex_xugmann_: thanks12:03
*** alexpilotti_ has quit IRC12:03
*** cloudtrainme has quit IRC12:03
*** aysyd has joined #openstack-meeting12:03
alex_xuI guess this is all for v2 api on gate12:03
*** yamamoto has quit IRC12:04
alex_xusdague: ^ are you around? is there anything more on gate for v2 api?12:04
gmann_alex_xu: sdague : do we need v21 compatible job as experimental on tempest as discussed on https://review.openstack.org/#/c/219370/12:04
johnthetubaguyv21 compatible is now the default run right?12:04
*** e0ne has joined #openstack-meeting12:04
johnthetubaguygiven the paste-api.ini changes12:05
gmann_johnthetubaguy: v21 is default12:05
alex_xuyea12:05
johnthetubaguyhmm, so whats on the v21 jobs?12:05
*** jhenner has quit IRC12:05
gmann_johnthetubaguy: /v21 service catalog12:05
johnthetubaguycheck-tempest-dsvm-full vs check-tempest-dsvm-nova-v21-full12:05
gmann_and each job for /v2 and v21 compatible12:05
*** lblanchard has joined #openstack-meeting12:05
sdagueo/12:05
johnthetubaguyI thought the first would fire at /v2.0 and the second fires at /v2.1?12:06
gmann_johnthetubaguy: check-tempest-dsvm-nova-v21-full will be removed in https://review.openstack.org/#/c/219553/12:06
johnthetubaguywhat we are missing now are tests for leagacy_v2 code I thought?12:06
alex_xuyea, I think so12:06
*** dprince has joined #openstack-meeting12:06
sdaguejohnthetubaguy: so check-tempest-dsvm-full is now pointing at /v2.112:06
gmann_johnthetubaguy: for legacy v2 code we have one new job12:06
sdaguebecause devstack compute SC entry is now pointing at /v2.112:06
sdaguethere is a compute_legacy SC entry12:07
gmann_gate-tempest-dsvm-nova-v20-api12:07
johnthetubaguysdague: OK, gotcha12:07
sdaguewhich is the /v2.0 endpoint12:07
sdaguethere are 2 jobs testing it12:07
*** esker has quit IRC12:07
alex_xuwhat is for v2.1 legacy compat mode?12:08
sdaguegate-tempest-dsvm-nova-v20-api12:08
johnthetubaguyah, they on the experimental queue I guess12:08
sdaguewhich is v2.0 on v2.112:08
sdaguegate-tempest-dsvm-nova-v20-api-legacy12:08
sdaguev2.0 on old v2.012:08
sdaguejohnthetubaguy: no, they are in check queue, non-voting12:08
alex_xuah, yea12:08
gmann_johnthetubaguy: they are on check pipeline12:08
johnthetubaguyah, so thats nice and simple, cool12:08
sdaguethey only run the compute api tempest tests12:08
*** doug-fish has quit IRC12:08
alex_xuso we are good, right?12:09
johnthetubaguysdague: ah, so I am looking at runs that are too old, thinking about it12:09
johnthetubaguyalex_xu: sounds perfect to me12:09
sdaguejohnthetubaguy: yeh, they landed late last week12:09
sdaguemy intent is to look at the stats on those today12:09
sdagueand if the pass rate is high enough, make them voting12:09
johnthetubaguysweet12:09
alex_xucool12:09
gmann_sdague: do we need v21 comap job as experimental on tempest?12:09
gmann_sdague: +1 to make them voting12:10
sdaguegmann_: yeh, we should probably put both those jobs in tempest experimental as well12:10
gmann_sdague:  yea12:10
sdaguegmann_: you want to post the patch for that?12:10
gmann_sdague: yea, i can post tomorrow early12:10
*** doug-fish has joined #openstack-meeting12:10
*** baoli has joined #openstack-meeting12:11
alex_xu#action gmann_ post patch put v2.1 compat and v2 legacy jobs as experimental12:11
gmann_alex_xu: thanks12:11
alex_xugmann_: np12:11
alex_xulet's move on12:11
alex_xuedleafe will update https://review.openstack.org/#/c/217727/12:12
alex_xufor this, let's jump to next topic directly12:12
alex_xu#topic v2.0 on v2.112:12
*** openstack changes topic to "v2.0 on v2.1 (Meeting topic: nova api)"12:12
alex_xuThere are some patches we need discussion, and all  of them are about whether fix it for v2.1. Let's talk about them one by one12:12
alex_xu#link https://review.openstack.org/#/c/217727/12:12
*** raildo-afk is now known as raildo12:12
alex_xuI prefer fix it for v2.1 also. Otherwise when user switch to v2.1 the functionality of support out-of-tree filters is broken.12:12
alex_xuken'ichi change his mind also, he removed -112:13
*** Jeffrey4l has joined #openstack-meeting12:13
edleafeI haven't caught up on the discussion on that patchset yet.12:13
*** amakarov_away is now known as amakarov12:13
edleafeI'm recovering from a long US weekend. :)12:13
sdagueright, I thought we were generally agreed to let through scheduler filters12:13
alex_xuedleafe: the argument is more about whether we fix it in the v2.1 API12:13
gmann_alex_xu: oh, so we are not going with runtime discovery for hint?12:14
gmann_sdague: for v2.1 also12:14
sdaguegmann_: we still need to get to discovery, but if we don't let this through it means that rax won't use v2.112:14
sdaguewhich I'd like to avoid12:14
alex_xugmann_: we need think that more.12:14
sdaguethey need custom scheduler filters12:14
johnthetubaguywe certainly need some for the v2.0 compatibility mode12:15
gmann_sdague:  humm, yea that true12:15
sdagueyeh, but I also think that it's fine to be pragmatic on this one12:15
johnthetubaguywe could just hack the validation logic, but thats pretty aweful12:15
alex_xuto discover which hints enabled in the deployement, shouldn't be done by the json-schema. I think that is capabilites discovery. json-schema is part of our api contract12:15
sdaguelaski brought it up a bunch of times as a real issue, and I'm fine with that12:16
*** Kevin_Zheng has joined #openstack-meeting12:16
gmann_ohk12:16
sdagueso I'm conceptually +2 on https://review.openstack.org/#/c/217727/ - though I haven't reviewed the patch in detail12:16
johnthetubaguyyeah, so we need a "proper" way to do all this, but we don't have one right now, so it feels like 217727 is the best way forward12:16
sdagueagreed, especially if it means we'll get v2.1 deployed at RAX12:16
sdagueI'm happy with that trade off12:17
alex_xucool, looks like we get agreement12:17
*** esker has joined #openstack-meeting12:17
edleafe+1 from me conceptually12:17
alex_xulet's move on12:17
alex_xu#link https://bugs.launchpad.net/nova/+bug/149151112:17
openstackLaunchpad bug 1491511 in OpenStack Compute (nova) "Behavior change with latest nova paste config" [Critical,In progress] - Assigned to Alex Xu (xuhj)12:17
gmann_ok, for now looks good solution.12:17
alex_xuWe have three patches for this bug.12:17
alex_xu#link https://review.openstack.org/#/c/220386/12:17
alex_xuI think this is need fix for v2.1, otherwise the cell functionality is broken.12:17
sdagueright, so this is the catch all of issues we are finding12:17
johnthetubaguy(I have a new one, but its a separate issue)12:18
sdague#info https://review.openstack.org/#/c/220386/ - fixes for cell names - merged12:18
gmann_sdague: i was just wondering if server name can be used as hostname like for DNS entry etc?12:18
alex_xuso we are goodfor this?12:18
alex_xu#link https://review.openstack.org/22027912:18
sdaguegmann_: that's the next one12:18
alex_xugmann_: you are talk about this ^12:18
*** markvoelker has joined #openstack-meeting12:19
sdagueyeh, so it does get coerced into a hostname in dnsmasq some times12:19
gmann_sdague: yea12:19
sdaguehowever, in v2.0 there was no checking12:19
johnthetubaguyyeah, it does, but its primarily a display name12:19
alex_xuyea12:19
alex_xuso we are good for this in v2.1?12:19
sdagueand the v2.1 schema doesn't guaruntee a working hostname12:19
johnthetubaguy(updating the name doesn't change the hostname, for example, at least not usually)12:20
gmann_johnthetubaguy: yea agree it is for display name12:20
*** markvoelker has quit IRC12:20
sdagueso I think there should be a follow on bug to make a function that tries to make a safe dns name out of it12:20
sdaguefor when it gets written to dnsmasq12:20
*** markvoelker has joined #openstack-meeting12:20
alex_xusdague: I remember there is code take care of it12:20
johnthetubaguysdague: I think thats a good way to go (there is some stuff that trims the name somewhere, for windows)12:21
sdaguealex_xu: not that I found12:21
*** liusheng has joined #openstack-meeting12:21
sdaguethe only thing I found was it lowercasing things12:21
* alex_xu find the link12:21
johnthetubaguyhmm, maybe its inside the xenapi driver, oh dear12:21
sdaguebut it wasn't handling spaces or special characters12:21
johnthetubaguyso seems like we need to just deal with spaces12:21
alex_xu#link https://github.com/openstack/nova/blob/master/nova/compute/api.py#L64012:21
gmann_sdague: so you mean we allow server name as display name with relaxing much restriction on that and later something should make that a dns name out of it?12:22
sdaguejohnthetubaguy: there are a lot of other invalid characters in hostnames as well12:22
johnthetubaguysdague: +112:22
alex_xu#link https://github.com/openstack/nova/blob/master/nova/utils.py#L77412:22
sdagueThe Internet standards (Requests for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. However, a subsequent specification (RFC 1123) permitted hos12:22
sdaguetname labels to start with digits. No other symbols, punctuation characters, or white space are permitted.12:22
johnthetubaguyso I guess the consensus is merge the relax, and follow up with the above fix12:23
sdaguealex_xu: that regex looks wrong, but lets take that offline12:24
*** chandankumar has joined #openstack-meeting12:24
sdagueI'd like to see lots of unit tests for that12:24
alex_xusdague: ok12:24
johnthetubaguy+1 for the unit tests12:24
gmann_johnthetubaguy: +112:24
alex_xu#link #link https://review.openstack.org/22079112:24
alex_xuAnother part of relax validation for server name, actually I found some api allow leading/trailing spaces in the name.12:24
alex_xunot sure we want to fix this, as the leading/trailing spaces is useless use-case12:25
sdaguealex_xu: also, sanitize hostname is getting called in a weird place12:25
alex_xusdague: actually it convert from the name12:25
sdagueright, but it's changing the db entry12:25
*** noslzzp has joined #openstack-meeting12:25
alex_xuemm...yea, I didn't notice that12:26
alex_xuagree with you12:26
sdagueso, how about we open a new bug for getting the hostname bit right12:26
alex_xu+112:26
*** e0ne has quit IRC12:26
sdaguealex_xu: can you open that bug?12:26
alex_xusure12:26
alex_xu#action alex_xu open a bug for fix the hostname12:27
sdaguethanks12:27
alex_xunp12:27
alex_xuso back to https://review.openstack.org/22079112:27
*** liusheng has quit IRC12:27
alex_xuwhether we need fix ^12:27
*** armax has quit IRC12:27
sdaguealex_xu: that one I'm less sure, johnthetubaguy ?12:28
sdaguealex_xu: what was the v2.0 behavior here?12:28
*** rbowen has joined #openstack-meeting12:28
johnthetubaguyyeah, we should match v2.0 I feel, although I haven't checked what that is12:28
johnthetubaguyseems like we should strip the whitespace though, if we allow it12:29
gmann_sdague: it was mix in v2.0, some resource allow and strip and some does not strip only allow12:29
alex_xusdague:  a little mess if you see the commit message, server and flavor allow leading/trailing spaces and strip spaces and not allow all spaces string, other api with name didn't strip and allow all spaces string12:29
gmann_alex_xu: yea12:29
johnthetubaguyso I would go for allow and strip for all of them, would that work?12:29
*** safchain has joined #openstack-meeting12:29
gmann_johnthetubaguy: sdague: alex_xu : but do we need to do that for v2.1 also or only for v21 compatible mode?12:30
*** liusheng_ has joined #openstack-meeting12:30
alex_xujohnthetubaguy: that means we fix the server and flavor, but still strict for other apis12:30
johnthetubaguyalex_xu: how are the APIs restricted? you mean trailing whitespace is always ignored now?12:30
alex_xugmann_: yea, that also a question12:30
sdaguealex_xu: so if we allow and strip, do we need to go and clean up the data in the db for matching?12:30
sdaguefor the stuff that wasn't stripped before12:30
alex_xujohnthetubaguy: some of apis not, like aggregates12:30
johnthetubaguysdague: I am tempted to say no for that12:31
sdagueI think allow and strip is probably right12:31
johnthetubaguyalex_xu: I think I am OK with that12:31
*** yfried_ has quit IRC12:31
alex_xuso this is ok for v2.1?12:31
johnthetubaguyI am tempted to say yes, but it doesn't feel very clear cut12:31
gmann_alex_xu: i feel we should have clean way for v2.1 means do not allow12:31
*** phil_ has quit IRC12:32
johnthetubaguyso for the compat, we defiantly need strip and accept12:32
*** liusheng_ has left #openstack-meeting12:32
sdaguehow bad would it be to allow in v2.0 compat mode and be strict in v2.112:32
sdaguein terms of code?12:32
alex_xuthis patch can answer you https://review.openstack.org/22112912:33
johnthetubaguyso yeah, maintain our strictness for v2.1, I am happier with that approach12:33
gmann_sdague: you might need 2 set of schema looks like but may be sone common place change for name format12:33
sdaguealex_xu: so it's not just validation right, it's also a transform to do the strip12:33
alex_xusdague: indeed, we still need python code to strip12:34
sdaguewe'll still need the transform right?12:34
*** salv-orlando has quit IRC12:34
johnthetubaguyI guess we can always to the strip, and the schema stops that doing anything in some cases12:34
sdaguecan that be done as a decorator to transform12:34
alex_xuI think not12:34
sdaguejohnthetubaguy: oh, that's true12:34
johnthetubaguysdague: yeah, it just came to me, and suddenly felt more palatable12:35
sdaguealex_xu: yeh, so conceptual +2 on kenichi's patch, I'll review after meeting12:35
alex_xusdague: cool12:35
sdaguealso, he needs to not put these things in WF-1 :)12:35
alex_xuemm...that only can catch him tomorrow12:35
sdague#action everyone review kenichi's json schema for 2.0 patch - https://review.openstack.org/221129 as a way to enforce differently for v2.012:36
alex_xuat line 76 there is terrible regexp also https://review.openstack.org/#/c/220791/1/nova/api/validation/parameter_types.py12:36
sdagueyep12:36
* alex_xu hate regexp12:37
sdaguehonestly, these things are getting to the point where they should probably be enforced with a gramar and not regex12:37
* edleafe loves good regexp12:37
*** toscalix__ has quit IRC12:37
alex_xuto be clear https://review.openstack.org/220279 fix for v2 and v2.1, https://review.openstack.org/220791 only for v2?12:37
johnthetubaguysdague: its getting dam close12:37
* bauzas waves very late12:37
alex_xusdague: yea12:37
* bauzas scrolls back12:38
* alex_xu waves to bauzas12:38
*** esker has quit IRC12:38
gmann_sdague: yea12:38
sdagueanyway, that's for next cycle12:39
sdagueok, so we seem clear on all these patches in concept?12:39
sdaguenow it's just getting them into shape and landed, right12:39
gmann_sdague: yea12:39
alex_xucool12:39
*** dzamboni has joined #openstack-meeting12:39
alex_xulet's move...12:40
sdaguealex_xu: if you remove your -1 on this - https://review.openstack.org/#/c/220279 - I'll approve12:40
alex_xusdague: done!12:40
johnthetubaguydid we have a previous patch that bauzas was -1 one on, about the scheduler hints?12:41
bauzasjohnthetubaguy: I left -1 just for a placeholder until we have a convo12:41
sdagueyeh, as we went through that already, lets cycle on -nova after12:41
alex_xuwe already have convo for that...12:41
bauzasjohnthetubaguy: but looking at the discussion above, is there a consensus yet ?12:41
bauzasokay, move on to -nova then12:41
alex_xu#link https://bugs.launchpad.net/python-novaclient/+bug/149132512:42
openstackLaunchpad bug 1491325 in OpenStack Compute (nova) "nova api v2.1 does not allow to use autodetection of volume device path" [Critical,Fix committed] - Assigned to Davanum Srinivas (DIMS) (dims-v)12:42
bauzaswhen the meeting is ended12:42
alex_xuthis already fixed12:42
alex_xuso we are good for this?12:42
*** Jeffrey4l has quit IRC12:42
sdaguealex_xu: right, we fixed it in both nova and novaclient12:42
alex_xusdague: cool12:42
*** dane_leblanc has quit IRC12:42
*** vivekd_ has joined #openstack-meeting12:42
sdagueI responded with a long email to gmann_ on the list this morning about why we did it they way we did12:42
*** bswartz has quit IRC12:42
sdaguehopefully that has enough detail12:42
gmann_sdague: ohk, i will read your reply, i was on vacation today12:43
gmann_sdague: Thanks :)12:43
* alex_xu will read the email12:43
alex_xuI think that is all for v2 on v2.1.12:43
johnthetubaguyso I have a python-novaclient bug12:43
johnthetubaguyits a bit related12:43
johnthetubaguyits described here: https://review.openstack.org/#/c/221222/12:43
johnthetubaguyhttps://launchpad.net/bugs/149320712:44
openstackLaunchpad bug 1493205 in OpenStack Dashboard (Horizon) "duplicate for #1493207 Create Keypair failed on latest DevStack" [Undecided,New] - Assigned to Chung Chih, Hung (lyanchih)12:44
sdagueright, the fact that the API isn't defaulting to v2.0 if not specified?12:44
bauzasdid we discussed of https://bugs.launchpad.net/nova/+bug/1492925 ?12:44
openstackLaunchpad bug 1492925 in OpenStack Compute (nova) "Lack of API schema definition for different cell filter" [Undecided,In progress] - Assigned to Ken'ichi Ohmichi (oomichi)12:44
*** vivekd has quit IRC12:44
*** vivekd_ is now known as vivekd12:44
sdaguebauzas: yeh, we hit the cells bit already12:44
bauzasjohnthetubaguy: my bad, you're first12:44
*** esker has joined #openstack-meeting12:44
alex_xuwe said the novaclient default to latest12:44
*** salv-orlando has joined #openstack-meeting12:44
bauzassdague: coolness, thanks12:44
sdaguealex_xu: the CLI12:44
johnthetubaguyso python-novaclient seems to default in a broken way12:44
johnthetubaguythe client defaults to find the max version, but not sending version headers12:45
sdaguethe API should default back to oldest12:45
alex_xusdague: oops, that bug about api?12:45
sdaguealex_xu: yeh12:45
johnthetubaguyit should really default to the min version12:45
alex_xuI remember I coding like that12:45
alex_xujohnthetubaguy: agree12:45
sdaguejohnthetubaguy: yeh, so it seems like it was just only 1/2 implemented12:45
sdaguealso, that should be easy enough to test with the functional tests once it's right12:46
johnthetubaguyso the unit tests would have found this12:46
alex_xuyea12:46
johnthetubaguybut they were written so it was avoided12:46
alex_xujohnthetubaguy: do you need me take care that patch?12:46
sdagueheh12:46
*** matrohon has joined #openstack-meeting12:46
johnthetubaguythis reproduces the failure: https://review.openstack.org/#/c/221222/2/novaclient/tests/unit/v2/test_keypairs.py,cm12:46
johnthetubaguybeen fighting to find a fix12:47
alex_xucool12:48
*** mdavidson has joined #openstack-meeting12:48
alex_xuso that's all?12:49
johnthetubaguyanyways, seems like we have consensus on the correct behaviour12:49
alex_xuyea12:49
johnthetubaguyI might need a hand with the patch if this next attempt doesn't work12:49
alex_xujohnthetubaguy: yea, I can help12:49
edleafeme too12:49
johnthetubaguyOK, cool, just know I need to get back to reviews again12:50
*** dane_leblanc has joined #openstack-meeting12:50
sdagueok, so is there a way to target python-novaclient bugs?12:50
johnthetubaguythats all, thanks for the offers12:50
sdagueit was duped, so the new bug is - https://bugs.launchpad.net/python-novaclient/+bug/149320512:50
openstackLaunchpad bug 1493205 in python-novaclient "Create Keypair failed on latest DevStack" [Undecided,New]12:50
alex_xuok, so johnthetubaguy you can free to catch me or edleafe when you need a hand12:50
johnthetubaguysdague: good point, I guess not12:50
sdagueok, well so be it12:51
sdagueI marked it critical so hopefully it doesn't get lost12:51
alex_xusdague: cool, thanks12:51
*** ildikov has quit IRC12:51
alex_xuanything more for v2.1?12:52
*** esker has quit IRC12:52
alex_xuok, so let's move on12:52
alex_xu#topic Removal of v3 naming from source tree12:52
*** openstack changes topic to "Removal of v3 naming from source tree (Meeting topic: nova api)"12:52
*** esker has joined #openstack-meeting12:52
*** VanL has joined #openstack-meeting12:52
alex_xuedleafe: sorry I didn't follow that, any patch you still have?12:53
edleafeyes - looks like https://review.openstack.org/#/c/214290/ needs a rebase12:53
edleafeI can take care of that after the meeting12:53
johnthetubaguyedleafe: if you could take a look at this for me, that would be cool: https://review.openstack.org/#/c/221222/12:53
edleafeand a few small things for https://review.openstack.org/#/c/21431112:53
*** amotoki has quit IRC12:54
edleafejohnthetubaguy: will do12:54
* edleafe will need to make coffee first12:54
*** esker has quit IRC12:54
johnthetubaguyedleafe: agreed, I just -1ed my patch with why I don't like it, but it does seem to pass unit tests now12:55
alex_xuhttps://review.openstack.org/#/c/214311 looks like more important, it correct some log message, they are user faced thing12:55
alex_xuso just for this we just need update patch and review, right?12:56
*** esker has joined #openstack-meeting12:56
sdagueedleafe: yeh, I think the -1 on 214311 should be easy fix12:56
johnthetubaguyso the above patch is currently breaking horrizon12:56
*** esker has quit IRC12:56
johnthetubaguyand probably lots of other users12:56
gmann_johnthetubaguy: which one?12:56
johnthetubaguyI mean: https://review.openstack.org/#/c/221222 when I say above12:56
gmann_ohk12:57
bauzasjohnthetubaguy: +1 this is the far most critical12:57
alex_xuyea12:57
*** aranjan has joined #openstack-meeting12:57
sdaguejohnthetubaguy: yeh I've got some paper work to do today, but I'll take a look at that patch12:57
sdagueand see if I can sort out a working rev12:57
johnthetubaguycool, just wanted to make sure we all understood the impact there12:57
sdagueand make mriedem do more novaclient releases12:57
*** nelsnelson has joined #openstack-meeting12:58
johnthetubaguyI did give horizon folks I was talking to a hack, if needed12:58
*** MeganR has joined #openstack-meeting12:58
sdagueright, we should fix it, it's going to break other people as well12:58
johnthetubaguybut we have to fix it either way12:58
johnthetubaguysdague: yeah, +112:58
alex_xuagree12:58
sdagueso... next cycle, can we release novaclient every monday?12:58
sdaguebecause part of this issue is we had 4 months of changes all drop at once12:58
alex_xu4 months...12:59
gmann_sdague: nice point to catch those early12:59
johnthetubaguysdague: yeah, or every other, that would totally make sense12:59
*** Qiming__ has joined #openstack-meeting12:59
edleafe+1 to more frequent releases12:59
sdagueand I'd much rather flush out issues faster12:59
*** MeganR has left #openstack-meeting12:59
sdagueI think a weekly release for a library should be fine12:59
johnthetubaguysdague: I mean we should have done every milestone at a minimum, but it just didn't happen12:59
sdagueyep12:59
*** spotz_zzz is now known as spotz12:59
alex_xujump to open directly, avoid somebody need help12:59
alex_xu#topic open12:59
*** openstack changes topic to "open (Meeting topic: nova api)"12:59
bauzasI had a question13:00
bauzasbut 20 secs left13:00
bauzasso moving on to -nova instead13:00
alex_xuyea...13:00
johnthetubaguyhonestly, I was waiting for the microversion support to drop really, and that was recent, we should do time bound releases there13:00
alex_xuso...thanks all!13:00
edleafethanks alex_xu!13:00
sdaguethanks alex_xu13:00
alex_xu#endmeeting13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
gmann_Thanks all13:00
openstackMeeting ended Tue Sep  8 13:00:35 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-09-08-12.00.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-09-08-12.00.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-09-08-12.00.log.html13:00
Qiming__#startmeeting senlin13:01
openstackMeeting started Tue Sep  8 13:01:08 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
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
Qiming__hello13:01
*** glauco has joined #openstack-meeting13:01
*** xingchao has joined #openstack-meeting13:01
*** ildikov has joined #openstack-meeting13:02
*** xingchao has quit IRC13:02
*** armax has joined #openstack-meeting13:02
*** eduardo has joined #openstack-meeting13:03
*** lyanchih has joined #openstack-meeting13:03
*** bswartz has joined #openstack-meeting13:03
*** ganeshna has joined #openstack-meeting13:03
*** slagle_ is now known as slagle13:03
*** yamamoto has joined #openstack-meeting13:05
*** haiwei has joined #openstack-meeting13:07
haiweisorry be late13:07
*** Piet has quit IRC13:07
Qiming__hi13:07
*** shashank_hegde has joined #openstack-meeting13:07
haiweihi13:07
*** vgridnev has quit IRC13:07
*** vgridnev has joined #openstack-meeting13:07
*** e0ne has joined #openstack-meeting13:08
Qiming__yanyan has got some network problem13:08
Qiming__let's wait a few minutes13:08
haiweiok13:08
Qiming__anything new from your side?13:08
*** pnavarro|lunch is now known as pnavarro13:08
*** toscalix__ has joined #openstack-meeting13:08
*** yanyanhu has joined #openstack-meeting13:08
Qiming__not sure cindia is online or not13:08
yanyanhuhi, Qiming__ , sorry I'm late13:09
haiweinothing special13:09
yanyanhuusing web irc now13:09
haiweibut maybe another person of my team will join senlin13:09
Qiming__okay, let's do a quick update first13:09
Qiming__haiwei, great!13:09
*** tongli has joined #openstack-meeting13:10
Qiming__we have a looooooooot of things to do, really need more hands13:10
haiweiand also I have invited one to senlin-dushboard13:10
yanyanhucool :)13:10
*** xingchao has joined #openstack-meeting13:10
*** VanL has quit IRC13:10
Qiming__cool, please help link the UI guy to zhenguo13:10
*** haomaiwang has joined #openstack-meeting13:10
*** geoffarnoldX is now known as geoffarnold13:11
*** changbl has quit IRC13:11
haiweiin fact, recently i have done few jobs13:11
Qiming__looking at the work items etherpad now13:11
*** gmann_ has quit IRC13:11
*** mklyus has quit IRC13:11
Qiming__don't worry, you will catch up13:11
Qiming__;)13:11
*** edleafe has quit IRC13:11
haiweiI am trying to understand as much as possible about senlin13:11
Qiming__test cases for drivers ... em, we can remove them all today13:11
haiweigodd13:12
haiweigood13:12
Qiming__haiwei, we are sorry for making things so complicated, :P13:12
haiweino, that's where senlin is interesting13:12
Qiming__finally, we are about to clean the l-3 backlog13:12
Qiming__functional tests ... yanyanhu has done good job there, hopefully scaling test cases will pass soon, after some bug fixes13:13
*** ivar-lazzaro has joined #openstack-meeting13:13
*** ivasev has joined #openstack-meeting13:13
yanyanhuyep13:13
haiweipeople are interested in when to make an namespace shift13:13
*** _amrith_ is now known as amrith13:13
*** coreycb` is now known as coreycb13:14
*** ayoung has joined #openstack-meeting13:14
*** jecarey has joined #openstack-meeting13:14
Qiming__haiwei, we are in queue13:14
*** rvasilets has joined #openstack-meeting13:14
yanyanhuhopefully this can be done tomorrow13:14
Qiming__we won't be there when we are not proving the project's usefulness13:14
*** ganeshna has quit IRC13:15
*** gouthamr has joined #openstack-meeting13:15
haiweiyes, is there any risk that the namespace shift will be rejected?13:15
Qiming__shifting namespace tomorrow may and may not be a good thing, if we cannot get a few POCs up and running13:15
haiweiit seems kolla is still in stackforge13:15
Qiming__haiwei, we keep work hard, things will happen13:16
haiweiok13:16
*** vijendar has joined #openstack-meeting13:16
Qiming__just had a conf call with SUR team this afternoon13:16
*** hrou has joined #openstack-meeting13:16
*** neelashah has joined #openstack-meeting13:17
yanyanhushifting namespace is not the goal, making the project popular is :)13:17
Qiming__they are stuck by some problems13:17
haiweiwho is SUR team13:17
Qiming__yanyanhu, right13:17
Qiming__it's a shared university research program13:17
haiweiok13:17
haiweiwhat are the problems13:18
Qiming__they are helping us developing clusters of containers13:18
Qiming__in the framework of magnum13:18
Qiming__they have just shared with us the code they have developed, unfortunately, I cannot find the links at the moment13:19
Qiming__will share those with you later13:19
haiweiok13:20
Qiming__they are not only working on operating container clusters, but also on auto-scale, load-balance them13:20
yanyanhunice, then we can make some reviews about the code13:20
Qiming__yes13:20
haiweithe problems are?13:20
Qiming__I hope julio can play an important role there13:21
*** spzala has joined #openstack-meeting13:21
Qiming__how to make auto-scaling/load-balancing work between the two layers of entities: VMs, containers13:21
Qiming__that is an interesting topic to explore13:22
*** geoffarnold has quit IRC13:22
*** pradk has joined #openstack-meeting13:22
*** BharatK has quit IRC13:22
Qiming__they already have a prototype using Docker, now they have started playing with kubernetes13:22
*** yamamoto has quit IRC13:22
Qiming__#topic placement policy13:23
*** openstack changes topic to "placement policy (Meeting topic: senlin)"13:23
*** ganeshna has joined #openstack-meeting13:23
Qiming__Cindia has submitted a patch doing placement13:23
Qiming__it is based on vSphere DRS13:23
*** tiswanso has joined #openstack-meeting13:23
Qiming__but the idea is pretty generic13:23
Qiming__we can generalize that13:23
*** adahms has joined #openstack-meeting13:24
Qiming__basically, we have three layers to consider: hosts, availability-zones (aggregates) and regions13:24
*** Jeffrey4l has joined #openstack-meeting13:24
Qiming__for hosts, nova has different kinds of scheduler filters13:24
Qiming__we evaluated the server-group API extension, which has many problems13:25
Qiming__we may avoid using that13:25
*** banix has joined #openstack-meeting13:25
Qiming__the most significant problem is that you cannot add/remove members in a server-group13:26
Qiming__as for availability zones and regions, a generic policy can be designed, Cindia and I will look into that13:26
yanyanhuso you can just create/delete server-group as a batch13:27
haiweiwhat are the scheduler filters in nova?13:27
Qiming__haiwei, http://git.openstack.org/cgit/openstack/nova/tree/nova/scheduler/filters13:27
haiweithanks13:28
*** glauco has quit IRC13:28
*** bknudson has joined #openstack-meeting13:28
Qiming__if you are making good use of them, you can already do a good job managing the placement of your cluster nodes13:28
*** ivar-lazzaro has quit IRC13:28
Qiming__yanyanhu, yes, there is no update operation to a server-group13:28
*** ivar-lazzaro has joined #openstack-meeting13:29
yanyanhuunderstand13:29
Qiming__I'm thinking maybe we need to get the PRS team involved in the design13:29
haiweithis is the host layer?13:29
*** johnhunter has quit IRC13:29
*** Daisy has joined #openstack-meeting13:29
*** jlanoux_ has joined #openstack-meeting13:29
Qiming__haiwei, mostly host layer and also some support to availability zones13:29
Qiming__aggregates13:30
*** tellesnobrega is now known as tellesnobrega_af13:31
Qiming__maintaining the distribution of nodes is a challenge13:31
*** aranjan has quit IRC13:31
Qiming__any questions on placement policy?13:31
haiweithe first step of placement policy is in host layer?13:31
haiweiand also azs13:32
*** mrunge has quit IRC13:32
*** jlanoux has quit IRC13:32
Qiming__yep, haiwei, we are targeting a POC on that13:32
Qiming__some months ago, I saw a demo from PRS (platform computing) team doing various kinds of placement control13:33
haiweiI am not understand senlin generally well, does senlin can do autoscaling of vms in one host, don't consider the az13:33
haiweinow13:34
Qiming__generally speaking, we leave that scheduling decision to nova13:34
Qiming__when we are talking about VMs13:34
*** tellesnobrega_af is now known as tellesnobrega13:34
Qiming__however, we can provide some hints to Nova to gain a better control13:34
Qiming__that is what the 'filters'/scheduler is about13:35
haiweiso using nova scheduler the answer is yes13:35
Qiming__#topic summit planning13:36
haiweiok13:36
*** openstack changes topic to "summit planning (Meeting topic: senlin)"13:36
*** lazy_prince has quit IRC13:36
Qiming__for the coming summit, we need to schedule some discussions13:36
Qiming__it seems that the meeting rooms are pretty limited13:37
haiweiyes, tokyo is small13:37
Qiming__hopefully we can still find some places to have a discussion, for planning13:37
*** amitgandhinz has joined #openstack-meeting13:37
yanyanhuthat will be the best13:37
haiweiyou'd better reserve your hotel earlier13:38
Qiming__need to check who will/won't come13:38
yanyanhuhaiwei: we have booked the room :)13:38
*** john-davidge has joined #openstack-meeting13:38
haiweigreat13:38
yanyanhualthough not the nearest hotel...13:38
Qiming__sadly, our talk proposal wasn't accepted this time13:38
yanyanhuit's about 2.5 miles away from the conference hotel13:39
haiweiyes13:39
Qiming__totally confused about the voting and selection process13:39
Qiming__it is not transparent13:39
haiweia little far13:39
Qiming__last time in Vancouver, I know that an India company got 4 sessions accepted13:40
haiweii know some secrets about the voting13:40
Qiming__sigh ...13:40
yanyanhuanyway, we can plan a meetup I think13:40
Qiming__there should be no secrets at all13:40
haiweithey make some groups, for compute or network and so on,13:40
yanyanhuto discuss the road map for the coming cycle13:41
Qiming__surely we will schedule a meetup13:41
Qiming__prioritize things we want to complete during M cycle13:41
*** annp has joined #openstack-meeting13:41
*** hoangcx has joined #openstack-meeting13:41
yanyanhuyes13:41
Qiming__will check with julio and lisa and others13:42
*** haiwei_ has joined #openstack-meeting13:42
*** vjay13 has joined #openstack-meeting13:42
haiwei_I dropped, maybe someone found I am talking secret13:42
Qiming__:(13:43
Qiming__#topic open discussions13:43
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:43
haiwei_besides you two and me, are there other guys will join the senlin discussion13:43
yanyanhuhope xinhui can also join us13:43
Qiming__I think some guys from huawei, intel and vmware will join13:44
*** gouthamr has quit IRC13:44
*** gouthamr has joined #openstack-meeting13:44
*** haiwei has quit IRC13:45
Qiming__anyway, with the last pieces of test cases merged13:45
Qiming__we will focus on getting everything together and do some show case13:45
yanyanhunice13:46
*** VW_ has joined #openstack-meeting13:46
Qiming__anything else?13:46
*** ganeshna has quit IRC13:46
yanyanhunope from me13:46
*** blogan_ has joined #openstack-meeting13:46
haiwei_3:0 just now13:46
yanyanhusoccer?13:47
haiwei_you know it13:47
yanyanhu:)13:47
Qiming__okay, let's release the channel13:47
Qiming__do your small talks somewhere, ;)13:47
Qiming__thanks for joining13:47
Qiming__#endmeeting13:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:48
openstackMeeting ended Tue Sep  8 13:48:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-08-13.01.html13:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-08-13.01.txt13:48
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-08-13.01.log.html13:48
*** yanyanhu has quit IRC13:48
*** shz has joined #openstack-meeting13:48
*** VanL has joined #openstack-meeting13:48
*** vjay13 has quit IRC13:49
*** vjay13 has joined #openstack-meeting13:49
*** ricolin has joined #openstack-meeting13:49
*** mwagner_lap has joined #openstack-meeting13:49
*** vikram has joined #openstack-meeting13:49
*** balajiiyer has joined #openstack-meeting13:50
*** rbak has joined #openstack-meeting13:50
*** rbak has quit IRC13:50
*** changzhi has joined #openstack-meeting13:50
*** shashank_hegde has quit IRC13:50
*** glauco_ has joined #openstack-meeting13:50
*** otter768 has joined #openstack-meeting13:51
*** yamamoto has joined #openstack-meeting13:52
*** VanL has quit IRC13:54
*** gongysh has joined #openstack-meeting13:54
*** vikschw has joined #openstack-meeting13:54
*** vikschw has quit IRC13:54
*** vikram has quit IRC13:55
*** jlibosva has joined #openstack-meeting13:55
*** gouthamr has quit IRC13:55
*** vikram has joined #openstack-meeting13:56
*** gouthamr has joined #openstack-meeting13:56
*** otter768 has quit IRC13:56
*** dkranz has quit IRC13:57
*** galstrom_zzz is now known as galstrom13:58
*** VanL has joined #openstack-meeting13:58
*** korzen has joined #openstack-meeting13:58
mesteryWho's here for a Neutron meeting?13:59
akamyshnikovahi13:59
HenryGo/13:59
vikramHi13:59
*** ihrachys has joined #openstack-meeting13:59
*** johnsom has joined #openstack-meeting13:59
*** amuller has joined #openstack-meeting13:59
yamamotohi13:59
armaxI am?13:59
john-davidgehi13:59
amullerhiya13:59
ihrachys\o/13:59
jlibosva\o13:59
hichiharahi13:59
mesteryarmax: You're omniscient13:59
*** vjay13 has quit IRC13:59
*** jprovazn has joined #openstack-meeting14:00
*** jcoufal has quit IRC14:00
*** amotoki has joined #openstack-meeting14:00
mesteryLets get this party started14:00
mestery#startmeeting networking14:00
*** haiwei_ has quit IRC14:00
openstackMeeting started Tue Sep  8 14:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. 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
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:00
haleybhi14:00
russellbo/14:00
*** n00btube has joined #openstack-meeting14:00
xgermano/14:00
rossella_shi14:00
annphi14:00
mesteryBasically, today is 1) Announcements 2) Bugs 3) RC1 (with some yelling about only merging stuff approved to go in)14:00
*** ZZelle has joined #openstack-meeting14:00
*** emagana has joined #openstack-meeting14:00
mestery#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
amotokihi14:00
banixhi14:00
mesteryLiberty-3 is out!14:00
mestery#link https://launchpad.net/neutron/+milestone/liberty-314:00
*** haomaiwang has quit IRC14:01
ZZelleHello14:01
mestery#info Thanks to armax for going above and beyond last week14:01
emaganaBuenos Dias! (Good Morning)14:01
mesteryWe as a project are lucky to have armax around, and I wanted to thank him!14:01
ajoo/ :)14:01
*** johnbelamaric has joined #openstack-meeting14:01
amullerarmax++14:01
*** haomaiwang has joined #openstack-meeting14:01
emaganamestery: sorry I am late..14:01
ajoarmax^214:01
mesteryemagana: No worries14:01
ajo:-)14:01
* armax blushes14:01
* mestery thinks most people wish he was on vacation all the time after how awesome armax was last week14:01
mesterySeriously, nice work armax14:01
gongyshhi14:01
*** neiljerram has joined #openstack-meeting14:02
mesteryAnd nice work to the entire TEAM!14:02
armaxmestery: ok, now you’re pushing it14:02
mestery:)14:02
armax:)14:02
emaganaarmax: absolutely!14:02
mesteryLiberty-3 was a great team effort by all.14:02
mesteryWe should all be proud of that.14:02
mestery#link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Liberty_Release_Notes14:02
mestery#info Please keep updating Liberty release notes14:02
mesteryThat's all the announcements I had14:02
mesteryAnyone have anything else to share with the broader team this week?14:02
*** Qiming__ has left #openstack-meeting14:03
mesteryOK, lets slide along to bugs!14:03
mestery#topic Bugs14:03
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:03
*** yushiro has joined #openstack-meeting14:03
mesteryStarting at the top ...14:03
mestery#link https://bugs.launchpad.net/neutron/+bug/148414814:03
openstackLaunchpad bug 1484148 in neutron "neutronclient gate broken following VPNaaS infra changes" [Critical,Confirmed] - Assigned to Paul Michali (pcm)14:03
mesteryThis one belongs to pc_m, who doesn't appear to be here obviously :)14:04
*** cdub has joined #openstack-meeting14:04
mesteryI've posted some comments in the bug now, we'll move along unless someone else has an update here.14:04
*** eharney has joined #openstack-meeting14:04
mestery#link https://bugs.launchpad.net/neutron/+bug/148828214:04
openstackLaunchpad bug 1488282 in neutron "Gate failures with 'the resource could not be found'" [High,Confirmed] - Assigned to Salvatore Orlando (salvatore-orlando)14:04
mesteryThis one is assigned to salv-orlando :)14:05
*** pc_m has joined #openstack-meeting14:05
mesteryI believe 2 weeks ago he volunteered to triage it a bit more14:05
*** dane_leblanc has quit IRC14:05
mesteryReported by armax14:05
*** dane_leblanc has joined #openstack-meeting14:05
HenryGThere was a tempest fix for that I believe?14:06
* mestery looks at the logstash query14:06
salv-orlandomestery but I declared it as "non neutron"14:06
* pc_m sorry late14:06
ajomestery: comments by salvatore say it seems like a nova bug14:06
armaxHenryG: that was a different NotFound14:06
*** bobh has joined #openstack-meeting14:06
armaxHenryG: actually we had a few that hit at the same time14:06
ajohi salv-orlando  :)14:06
salv-orlandoI'm just waiting for a confirmation from the nova people to remove neutron from the affected list14:06
armaxone fix went into tempest14:06
mesterysalv-orlando: Awesome14:06
armaxthe other in neutron14:06
mesteryAlso, the logstash query shows no hits since 9-314:06
mesterySo ....14:06
armaxthis one, as salv-orlando points out14:07
armaxmight be noa14:07
armaxnova14:07
ajosalv-orlando: may be we should move neutron out from "confirmed" to something else?14:07
armaxajo: not so hasty14:07
ajoO:)14:07
mesterylol14:07
salv-orlandoajo: sure. will do. sir.14:07
armaxtypically when you do so, the bug reassert itself as neutron’s fault ;)14:07
*** cloudtrainme has joined #openstack-meeting14:07
pc_mmestery: I'm here14:07
armaxI proved with this one14:07
salv-orlandoonce armax says it's ok to do14:07
ajolol14:07
mesterypc_m: Once second14:07
ihrachysyeah, we like to close unfixed bugs14:07
armaxhttps://bugs.launchpad.net/neutron/+bug/149005114:07
openstackLaunchpad bug 1490051 in neutron "test_assert_pings_during_br_int_setup_not_lost fails with oslo_rootwrap.wrapper.NoFilterMatched" [High,In progress] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)14:07
*** lazy_prince has joined #openstack-meeting14:07
*** killer_prince has joined #openstack-meeting14:08
armaxI closed it and it showed up14:08
mesteryarmax: Silly you ;)14:08
armaxmestery: well that was part of the strategy to lure the bug out14:08
armaxbugs have souls you know?14:08
ajoarmax, we need another phantom state (not closed) ... not to disturb the bugs...14:08
mesteryOh for sure they do14:08
ihrachyshe assumed no logstash hits during weekend and labour day == no bug14:08
mesterylol14:08
mesteryihrachys: Doesn't the entire world get Labor Day off? ;)14:08
armaxihrachys: no hits during the weekend no14:08
mesteryOK14:08
mesteryLets leave it oipen14:08
mesterysalv-orlando looks to ahve this under hand14:09
ihrachysmestery: well, if entire world == NA, then yes14:09
mesterypc_m: This one was your's https://bugs.launchpad.net/neutron/+bug/148414814:09
openstackLaunchpad bug 1484148 in neutron "neutronclient gate broken following VPNaaS infra changes" [Critical,Confirmed] - Assigned to Paul Michali (pcm)14:09
*** esheffield has joined #openstack-meeting14:09
banixmestery: yes but on may 1st14:09
mesteryihrachys: lol14:09
mesterypc_m: Any updates there?14:09
pc_mI changed the project-config job and the neutron-client code. Infra indicated they want Neutron cores to review the project config change, before they will review.14:09
armaxihrachys: we had an occurence today  by the looks of it14:09
pc_m#link https://review.openstack.org/#/c/209887/14:09
ihrachysarmax: I debug it now, lots of weird stuff seen in logs14:09
*** scheuran has joined #openstack-meeting14:09
pc_mThe other change, needs this upstreamed, so it can be tested.14:09
*** glauco_ has quit IRC14:09
mesterypc_m: Thanks!14:09
mesteryarmax: Can you review 209887 today yet?14:10
*** zeih has quit IRC14:10
*** scheuran has quit IRC14:10
pc_mCurrently, VPN tests are skipped, so it works.14:10
mesterydougwig is out hunting this week with no access to cell or email (so we shoudl all fill up his inbox and voicemail) :)14:10
pc_mWorks as in, doesn't fail, but is not really tested.14:10
*** vikram has quit IRC14:11
mesteryOK, lets move to the next one I'd like to discuss14:11
mestery#link https://bugs.launchpad.net/neutron/+bug/149113114:11
openstackLaunchpad bug 1491131 in neutron kilo "Ipset race condition" [High,New]14:11
ajomestery, lol14:11
*** galstrom is now known as galstrom_zzz14:11
mesteryThis one appears to affect Kilo as well as master14:11
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** cloudtrainme has quit IRC14:11
ajoah, yes, the racy thing, I totally forgot14:11
mesteryshihanzhang has a patch out which may be related (https://review.openstack.org/#/c/122368/)14:12
ajoI will follow that up during this week , seems assigned to cedric14:12
mesteryIt was abandoned14:12
mesteryajo: Awesome, thanks!14:12
*** dguitarbite has quit IRC14:12
salv-orlandorelated in the sense that it acvoid triggering the bug14:12
salv-orlando*avoids triggering14:12
ajomestery, there's some previous patch which already got in that fixes some of the issues they see in kilo14:13
mesterysalv-orlando: Well, that's related isn't it? :)14:13
ajobut, there's something that triggers ipset delete when it's already gone (or may be never created...)14:13
mesteryajo: The patch got into master?14:13
salv-orlandoajo,: do you know if someone beyond the reporter managed to reproduce it?14:13
*** rbak has joined #openstack-meeting14:13
ajomestery, I will review the whole thread and link the right patches.14:13
ajosalv-orlando: not that I know14:13
*** mmedvede has joined #openstack-meeting14:14
mesteryajo: Thanks!14:14
ajosalv-orlando: I guess it could make sense to make ipset.delete("aaa") not fail, if the ipset didn't exist14:14
*** zeih has joined #openstack-meeting14:14
ajoit could hide some source of races, but at least, we wouldn't block the agent. A warning may work..14:14
*** rbak has quit IRC14:15
*** irenab has quit IRC14:15
mesteryThat's the last bug I wanted to discuss before we move along. Does anyone have any other bugs they want to highlight here?14:15
ZZellesalv-orlando, i am trying to reproduce it but at the moment i fail to reproduce it14:15
salv-orlandoajo: we could put in place measures to avoid triggering the bug, but we'd also be masking the underlying race condition. so we might not necessarily do something good14:15
salv-orlandoas at some point the race will explode in our face14:16
ajosalv-orlando, yeah, but the failure mode is horrendous: broken agent until agent restart14:16
salv-orlando(well in the face of the ref impl lieutenant)14:16
mestery*cough cough* kevinbenton *cough cough*14:16
ajosalv-orlando: at least, we could reduce the impact14:16
*** irenab has joined #openstack-meeting14:16
*** killer_prince has quit IRC14:16
*** lazy_prince has quit IRC14:16
armaxmestery: kevinbenton is surely still sleeping14:16
ajoand may be link the bug to a logstash query to look for ocurrences14:16
*** ajmiller has joined #openstack-meeting14:17
ajosaid that, salv-orlando , I couldn't find those ocurrences in logstash upstream14:17
*** lazy_prince has joined #openstack-meeting14:17
mesteryarmax: He's driving home from disneyland actually and told me he'd miss today's meeting14:17
*** killer_prince has joined #openstack-meeting14:17
ajo(for ipset trying to delete something not existing..)14:17
*** pm90_ has quit IRC14:17
armaxbut he did so last night14:17
armaxmestery: last time I checked LA is not that far14:17
*** carl_baldwin has joined #openstack-meeting14:17
armaxfrom SF14:17
armax:)14:17
mesteryarmax: Nope, he's on the road right now in fact :)14:18
mesteryHe must have not gotten enough Mickey Mouse14:18
ajo:-)14:18
mesteryOK, lets move on before we lost the meeting completely :)14:18
mesteryNExt up ...14:18
armaxmestery: um…he’s probably eating corn somewhere on the road14:18
mesterylol14:18
*** rbak has joined #openstack-meeting14:18
mestery#topic Docs14:18
*** openstack changes topic to "Docs (Meeting topic: networking)"14:18
* carl_baldwin sorry to be late14:18
mesteryemagana: What have you got for us today?14:18
emaganaHello!14:18
* mestery sends carl_baldwin to the back of the room14:18
emagana mestery: not much really14:18
mesteryemagana: That's ok :)14:18
emaganaI have not seen new review for us..14:18
* markmcclain gets in line behind carl_baldwin 14:19
emaganahowever, after release-3 is when we should invest even more in Documenting the new features14:19
mesterylol14:19
mesteryemagana: That sounds good!14:19
*** cdub has quit IRC14:19
*** toscalix__ has quit IRC14:19
mesteryemagana: Is there a plan, and does it involve Sam-I-Am as well? :)14:20
ajoemagana, me owes QoS stuff14:20
*** VanL has quit IRC14:20
emaganamestery: I should have more details next week, after our networking docs meeting on Friday14:20
mesteryemagana: Thanks!14:20
mestery#info Plan for documentation changes for new Liberty-3 items will be unveiled next week after networking docs meeting on Friday14:20
emaganaajo: Yeah.. I will help there14:20
emaganamestery: Always involves Sam-I-Am14:20
ajothanks emagana , may be a simple template or initial "empty" review on where to put things would help, then I can follow up adding the details14:20
mestery:)14:21
emaganaajo: sounds good.. You will have it14:21
ajoemagana++14:21
emaganaI will add you as reviewer14:21
*** balajiiyer has quit IRC14:21
*** yamahata has joined #openstack-meeting14:21
*** VanL has joined #openstack-meeting14:21
emaganamestery: all from me!14:21
*** cloudtrainme has joined #openstack-meeting14:21
mesteryemagana: Thanks!14:21
*** wbhuber has joined #openstack-meeting14:21
mestery#topic Liberty-RC114:22
*** openstack changes topic to "Liberty-RC1 (Meeting topic: networking)"14:22
mestery#link https://launchpad.net/neutron/+milestone/liberty-rc114:22
mesteryLets walk through what we have targeted and have a hard look at what realistically will make it14:22
mesteryBecause I still think what's there isn't realistic at this point14:22
mesteryFirst up14:22
mestery#link https://blueprints.launchpad.net/neutron/+spec/get-me-a-network14:22
mesteryhaleyb: This seems like it's Mitaka at this point, does that sound right?14:22
armaxmestery: yes, I simply let the stuff spill over RC114:23
mesteryarmax: I would have done the same :)14:23
haleybmestery: yes14:23
mesteryhaleyb: That was easy :)14:23
ajomestery: what's the deadline for the RC1 cut?14:23
armaxhaleyb: not even foundational work?14:23
mesteryajo: https://wiki.openstack.org/wiki/Liberty_Release_Schedule14:23
armaxhaleyb: that prepares it for an early land in M?14:24
mesteryWe'll start cutting RC candidates the week of Sept. 2114:24
ajoah, ok, so it's not fixed for RC, just between 21sept to 9oct14:24
haleybarmax: yes, possibly foundation work14:24
armaxhaleyb: well...by now we’d need a little more than possibly14:24
mesteryhaleyb: If you land a patch or two for this, we'll let them in pending review then.14:24
*** toscalix__ has joined #openstack-meeting14:25
armax:)14:25
mesteryOK14:25
mesteryNext up14:25
mestery#link https://blueprints.launchpad.net/neutron/+spec/lbaas-ref-octavia14:25
mesterydougwig is gone, so perhaps blogan or xgerman can give us an update here14:25
mesteryI believe this one is still targeted as being landable, though no code shows up there14:25
xgermanbrogan worked all weekend so we should be good for the RC14:25
blogan_mestery: yeah i believe it is still landable14:25
xgerman+!14:25
armaxmestery: that must require landing code in more than one repo, though right?14:25
xgerman+114:25
mesteryYay!14:25
armaxmestery: so stuff might be out of our control14:25
mesteryarmax: Right!14:25
blogan_armax: correct14:26
mesteryWhere did hte code land xgerman blogan_ ?14:26
mesteryarmax: Well, it's in our control as it's in the Stadium14:26
xgermanoctavia and lbaas repo14:26
*** balajiiyer has joined #openstack-meeting14:26
mesteryAwesome14:26
mestery#info Octavia as the default LBaaS implementation will make Liberty14:26
*** dims_ has quit IRC14:26
mesteryblogan_: Feel free to mark Implemented once you're done14:26
john-davidgenice!14:26
*** mattgriffin has joined #openstack-meeting14:26
armaxmestery: what about project-config changes, devstack changes etc14:26
xgermanwe got them covered14:27
*** dimsum__ has joined #openstack-meeting14:27
mesteryarmax: See, xgerman has it covered?14:27
armaxmestery: tight!14:27
xgermanyep, very tight14:27
*** aranjan has joined #openstack-meeting14:27
mesteryLets move on, we've got plenty of yak shaving to complete while painting the bike shed yet14:28
mestery#link https://blueprints.launchpad.net/neutron/+spec/wsgi-pecan-switch14:28
mesteryI spoke to kevinbenton today14:28
*** AlanClark has joined #openstack-meeting14:28
mesteryAnd he says we still have a shat at this one14:28
*** Daisy has quit IRC14:28
mesteryThough blogan_ said service plugins don't load with the current branch, which is sad14:28
mesterykevinbenton remains vigilant he can get this landed this week yet14:28
* mestery waits for armax 14:28
armaxmestery: that’s doable14:28
*** Daisy has joined #openstack-meeting14:28
blogan_mestery: well i would say most probably do work, but its not the same as the current wgi server14:28
armaxmestery: we have targeted code14:28
markmcclainmestery: I've got some time to help kevinbenton with any reviews/work needed to land it14:29
armaxmestery: so we have an idea of what to expect14:29
*** baoli has quit IRC14:29
mesterymarkmcclain: Awesome! Please have a look here: https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z14:29
mestery#link https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z14:29
mesteryarmax: We do14:29
mesteryblogan_: OK14:29
mesterySo, this one looks like it's covered14:29
salv-orlandomestery: blogan_ did a hack that forces the pecan app to load all plugins at startup14:29
*** electrocucaracha has joined #openstack-meeting14:29
mesterysalv-orlando: Nice14:29
salv-orlandolet's say that from an end user perspective it works14:29
mesteryrofl14:29
blogan_mestery: this is just discussing whether it should roll back into master correct? it's not going to replace the current wgi is it?14:29
mesteryblogan_: God no, not at this stage! :)14:30
mesteryWe're just rolling back to master14:30
salv-orlandomestery: but tell armax not to look at the code. He'll faint.14:30
mesterySo we can release it as experimental14:30
*** blogan_ has quit IRC14:30
*** blogan_ has joined #openstack-meeting14:30
*** baoli_ has joined #openstack-meeting14:30
armaxsalv-orlando: thanks for the warning14:30
*** killer_prince has quit IRC14:30
blogan_sorry got dc'ed14:31
mesteryarmax: Please, refrain from looking for a bit :)14:31
armaxI’ll make sure I have a cpr kit next to me when I do14:31
mesteryAwesome14:31
mesteryOK, lets move along14:31
mestery#link https://blueprints.launchpad.net/neutron/+spec/vm-without-l3-address14:31
mesteryarmax reverted this one, luckily he had a CPR kit close by14:31
mesteryThe author has reached out14:31
mesteryBut the new direction this one goes in requires an API change (yuck)14:31
mesteryI'm inclined to boot this one out14:31
mesteryThoughts?14:31
*** irenab has quit IRC14:31
armaxmestery: unfortunately I hadn't14:31
kevinbentonPort security is a work around IMO14:32
* mestery takes a note to get armax portable CPR kits to keep near his computer14:32
mesterykevinbenton: Sounds fair14:32
*** irenab has joined #openstack-meeting14:32
*** vishwanathj has joined #openstack-meeting14:32
armaxkevinbenton: is alive!14:32
mesteryShall we move this one out to Mitaka then?14:32
mesterykevinbenton armax: ^^^^14:32
*** Murali has quit IRC14:32
kevinbentonI think so. We need a more fine grained port security API14:32
kevinbentonWhich will take some time to develop14:33
mesteryAGreed14:33
mestery#info vm-without-l3-address is a Mitaka feature now!14:33
armaxkevinbenton: well, it depends on how fast we can get consensus on the approach14:33
*** unicell has joined #openstack-meeting14:33
*** alexschm has quit IRC14:33
armaxbut yeah, probably it’s safer than shipping a hole in the ship14:33
*** Daisy has quit IRC14:33
*** edtubill has joined #openstack-meeting14:33
armaxno-one wants neutron to sink14:33
*** unicell1 has quit IRC14:33
*** blogan_ has quit IRC14:33
armaxmestery: do you?14:33
kevinbentonThe only difference is that they won't have Mac spoofing protection14:33
mesteryarmax: Of course not my friend14:34
kevinbentonThey can still do the non L3 addressed VM14:34
salv-orlandoarmax: but almost everyone rocks the boat ;)14:34
mesteryIt's out of Liberty14:34
mesteryLets move along14:34
mestery#link https://blueprints.launchpad.net/neutron/+spec/external-dns-resolution14:34
amotokiagree. we may need to combine unaddress port/port security with rbac14:34
mesteryThis one looks close, mlavelle is working on it now14:34
mesteryI expect it to land this week once he re-spins to address current issues14:34
*** raildo is now known as raildo-afk14:34
carl_baldwinmestery: +1  This one is not intrusive.14:34
*** ed__ has joined #openstack-meeting14:34
mesterycarl_baldwin: Cool14:35
mesterySpeaking of carl_baldwin ....14:35
mestery#link https://blueprints.launchpad.net/neutron/+spec/address-scopes14:35
emaganaand some operators need this one14:35
* mestery calls carl_baldwin up to the front of the classroom14:35
*** ed__ is now known as edleafe14:35
emaganaI meant the dns resolution one14:35
mesterycarl_baldwin: Thoughts on this one making Liberty at this point?14:35
mesteryemagana: ++14:35
* carl_baldwin walks up…14:35
mesterycarl_baldwin: I know you've been pushing hard on this one for the past few weeks yet14:35
*** irenab has quit IRC14:35
carl_baldwinThe optimistic in me wants to say yes.  It is functional.  But...14:35
*** aranjan has quit IRC14:36
carl_baldwinIt needs tests to be completed.  I suspect some interaction with DVR and I need to look at what will happen with static routes.14:36
*** aranjan has joined #openstack-meeting14:36
*** irenab has joined #openstack-meeting14:36
mesterycarl_baldwin: OK, I can leave it in there for now and we can re-evaluate next week?14:36
mesterySound fair?14:36
*** raildo-afk is now known as raildo14:37
* salv-orlando thinks carl_baldwin deserves a wildcard as he was already mothballed for liberty with pluggable-ipam14:37
gongyshI can join the test team.14:37
carl_baldwinThough I really want it in I think it would be better to merge early in Mitaka.14:37
*** jcoufal has joined #openstack-meeting14:37
mesterycarl_baldwin: Well, if that's your thinking, lets just move it out now. Sound ok?14:37
carl_baldwinmestery: ok14:37
*** vivekd has quit IRC14:37
* carl_baldwin stashes away the wildcard for later.14:37
mesterylol14:37
*** rhagarty has quit IRC14:38
ajo:D14:38
mesteryNext up14:38
mestery#link https://blueprints.launchpad.net/neutron/+spec/better-quotas14:38
*** rhagarty_ has quit IRC14:38
mesterysalv-orlando: I think we just need to review and merge 3 more patches right?14:38
mesteryOr maybe it's 414:38
salv-orlandoI think it's 314:38
mesteryAwesome14:39
salv-orlandoI can add some more testing coverage during RC phase, I reckon that would be ok, wouldn't it?14:39
mesterysalv-orlando: ++14:39
mesteryThanks salv-orlando14:39
*** glauco has joined #openstack-meeting14:39
mesteryNext up14:39
mestery#link https://blueprints.launchpad.net/neutron/+spec/restructure-l2-agent14:39
mesteryrossella_s has been working on this one for quite a while now14:39
ajocarl_baldwin: take out that wildcard for salv-orlando  :P :)14:39
mestery9 outstanding patches still rossella_s?14:39
* carl_baldwin hands it to salv-orlando 14:39
rossella_smestery, 514:40
mesteryrossella_s: Not bad!14:40
*** sballe has joined #openstack-meeting14:40
mesteryrossella_s: Are you getting enough reviews for these?14:40
mesteryrossella_s: Or do you need more people to help focus on these?14:40
rossella_sin the last days I got more review. Reviewers are always very welcome anyway14:40
* carl_baldwin can jump in14:40
mesterycarl_baldwin: Please do!14:40
rossella_scarl_baldwin thanks!14:40
mestery#info 5 patches left for agent refactoring, please jump in and help rossella_s land these this week!14:41
mesteryThanks rossella_s!14:41
rossella_smestery, thank you14:41
mesteryNext up14:41
mestery#link https://blueprints.launchpad.net/neutron/+spec/add-availability-zone14:41
mesteryIf I'm not mistaken, I think russellb was reviewing these and testing htem recently14:41
mesteryarmax also had a pass on these ones14:42
armaxmestery: yes, I meant to continue14:42
russellbyeah i got the first patch to work14:42
russellbwanted to do another pass14:42
hichiharaamotoki said API patch is OK14:42
ajorossella_s: I will re-review them all, sorry for being a bit slow on that.14:42
mesteryrussellb: \o/14:42
hichiharaI'm waiting his review to Scheduler patch.14:42
*** clarkb has quit IRC14:42
mesterySo, looks like armax russellb and amotoki have this one covered14:42
amotokiperhaps we need to review them combined with the scheduler patch.14:42
mesteryamotoki: ++14:42
russellbok if it's targeted, i'll be sure to do another pass ... i'm traveling this week again though14:42
russellbhopefully can find some time in the evening14:42
rossella_sajo thanks a lot!14:42
ajoamotoki++ russellb++ armax++14:43
ajo:)14:43
mesteryrussellb: Thanks!14:43
amotokilets check it next week again14:43
mesteryAnd thanks to amotoki and armax and ajo too :)14:43
mesteryamotoki: ++14:43
hichiharaThanks!14:43
mesteryNext up14:43
mestery#link https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules14:43
mesteryblogan xgerman: Any update here?14:43
mesterydougwig made it sound like this one may be out of Liberty now14:43
*** clarkb has joined #openstack-meeting14:43
xgermanI think we deferred that to M14:43
mesteryxgerman: Cool, thanks!14:44
ajonot to me, I did nothing related :D14:44
mesteryNext up14:44
mestery#link https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms14:44
mesteryI haven't reviewed this patches, has anyone been looking at these ones?14:44
mesteryI know they landed only a few weeks ago14:45
armaxmestery: looks like they have not had any beefy review14:45
mesteryarmax: I figured14:45
armaxmestery: they were submitted too late in the cycle to get enough attention14:45
mesteryI'm inclined to give it one more week, but I don't remain optimistic these land in Liberty14:45
mesteryarmax: ++14:45
*** aranjan has quit IRC14:45
amullerI think they can be delayed to M14:46
amullerat this point14:46
*** aranjan has joined #openstack-meeting14:46
armaxtoo bad14:46
mesteryYup14:46
mesteryLast one14:46
mestery#link https://blueprints.launchpad.net/neutron/+spec/neutron-flavor-framework-templates14:46
mesterySince dougwig isn't here, I'm inclined to just move this to Mitaka14:46
armaxmestery: he’s not doing the work though14:47
xgermanwell, we have the CLI and are working on a flavor -> service type thingy14:47
armaxmestery: someone from xgerman is doing it14:47
mesteryI just moved it out, should I move it back in?14:47
mesteryxgerman: Are you saying htis has a shot now?14:47
xgermanthere is still a chance14:47
mesteryxgerman: Please move the assignee to the actual person doing the work :)14:47
mesteryxgerman: Ok ,letaving it in14:47
armaxmestery: so long as the server side is fairly complete yes14:47
xgermanok, will do14:47
armaxbut CLI is clearly blocked on the server side getting in shape14:48
*** ayoung_ has joined #openstack-meeting14:48
mesteryarmax: WEll14:48
mesteryAlso14:48
mesteryWe're releasing the Liberty client today14:48
mesteryWhich means we won't release another one until after the Liberty release I guess14:48
* ihrachys dances14:48
* mestery dances with ihrachys 14:48
xgermanmmh, maybe then we are out14:48
* ajo dances too14:48
mesteryxgerman: Please add the reviews to the BP as well: https://blueprints.launchpad.net/neutron/+spec/neutron-flavor-framework-templates14:49
*** rfolco has quit IRC14:49
armaxxgerman: the cli was ready to merge14:49
amotokiit is a race condition between CLI dependency freeze and RC features :-(14:49
mesteryYes14:49
xgermanwell, my powers don’t let me change much on the BP14:49
armaxxgerman: I only stopped it because I looked at hte server side code14:49
armax…and fainted14:49
mesteryxgerman: In the work area14:49
* mestery rushes the CPR kit to armax 14:49
mesteryOK14:49
mestery#topic Open Discussion14:50
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:50
armaxI am ok, I am ok14:50
mesteryReview review review ....14:50
armax…and review what’s relevant14:50
mesteryWe're nearing the end of Liberty14:50
mesteryYes14:50
mesteryPLEASE PLEASE PLEASE don't merge random stuff at this stage14:50
armaxpushing random stuff in teh gate is not helping anyone14:50
ihrachyswhat's about gate for functional? amuller ?14:50
mesteryIf you have "workflow +1", you have to pay attentiong now14:50
armaxespecially if the failure rate is high14:50
mesteryWe can't afford to merge random things14:50
emaganaI want to collect questions back to the Operators?14:50
*** baojg has joined #openstack-meeting14:50
HenryGCan vendor decomps continue to go in?14:51
emaganawe are preparing the agenda for the Tokyo operators meet-up and the topics are here: #link https://etherpad.openstack.org/p/TYO-ops-meetup14:51
mesteryemagana: Are you looking for input from folks?14:51
mesteryHenryG: Anything which removes code is a-ok14:51
mestery#link https://etherpad.openstack.org/p/TYO-ops-meetup14:51
armaxmestery: +114:51
emaganamestery: Yes, I want to know what this team wants to know from Operators  :-)14:51
armaxmestery: remove all the things14:51
amullerihrachys: TBH I've been utterly disconnected since Friday, but I noticed that you and Armando and a few others continued to work on it quite a bit! Thanks for that! I'm pleased with the progress since the last weekly meeting. It's good to see action around that area.14:51
mesteryemagana: Sounds fair.14:52
mestery#info Please add anything you want to understand or glean from operators to the etherpad here: https://etherpad.openstack.org/p/TYO-ops-meetup14:52
*** jhenner has joined #openstack-meeting14:52
neiljerramMay I ask when we'll start brainstorming the Neutron agenda for Tokyo?14:52
mesteryamuller: ++, ihrachys and armax thanks!14:52
mesteryneiljerram: It's in progress as we speak, but I'll create an etherpad14:52
armaxgate stability is top priority IMO14:52
neiljerramCool, thanks.14:52
ajogit rm ** ; git commit -m "remove all the things"; git review # O:)14:52
mestery#action mestery create Mitaka summit etherpad idea page14:52
mesteryneiljerram: Thanks for mentinoing it! With the end of Liberty, I almost forgot to mention that :)14:53
armaxgate resets make people unhappy, apparently14:53
mesteryarmax: ++14:53
*** david-ly_ is now known as david-lyle14:53
gongyshI found some patches on https://github.com/openstack/neutron-specs/blob/master/specs/liberty/bgp-dynamic-routing.rst14:53
neiljerramNot wanting to detract from the Liberty endgame focus, of course!14:53
gongyshdo we have plan for it in liberty?14:53
armaxthe more stable we are the more stuff we’re gonna merge14:53
mesterygongysh: Taht is not targeted for Liberty14:53
*** changzhi has quit IRC14:54
gongyshmestery: ok I will move my review to other spec related patches.14:54
mesterygongysh: Thanks!14:54
mesteryAnything else from anyone before we close?14:54
ZZellemestery, should we remove dead code associated to ebtables management?14:54
*** geoffarnold has joined #openstack-meeting14:55
*** tsekiyama has joined #openstack-meeting14:55
mesteryZZelle: Code removal sounds ok, assuming it passes reviews, etc.14:55
mesterySound ok?14:55
ZZellemestery, ok14:55
mesteryOK, lets keep the Liberty momentum going folks!14:56
*** dprince has quit IRC14:56
mesteryOnly a few weeks left!14:56
mesterySee you all on the ML, IRC, and in the ether!14:56
mestery#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:56
openstackMeeting ended Tue Sep  8 14:56:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-09-08-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-09-08-14.00.txt14:56
yushiro  bye14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-09-08-14.00.log.html14:56
*** yushiro has quit IRC14:56
armaxbye14:56
hoangcxBye14:56
hichiharabye14:56
*** johnbelamaric has left #openstack-meeting14:56
neiljerrambye14:56
*** johnsom has left #openstack-meeting14:56
yamamotobye14:56
amotokibye14:56
*** neiljerram has left #openstack-meeting14:56
gongyshbye14:56
akamyshnikovabye14:56
xgermanbye14:56
ajoo/14:56
emaganaadios..14:56
vichowardbye14:56
ajoadios ;)14:56
*** john-davidge has left #openstack-meeting14:57
*** pc_m has left #openstack-meeting14:57
gongyshajo: our qos is ready?14:57
rossella_sbye14:57
*** dprince has joined #openstack-meeting14:57
*** hoangcx has quit IRC14:57
ZZelleAdieu14:57
*** banix_ has joined #openstack-meeting14:58
*** amuller has left #openstack-meeting14:58
*** banix has quit IRC14:58
*** banix_ is now known as banix14:58
*** mattgriffin has quit IRC14:58
ajogongysh: just a couple of bugs and doc14:59
ajoand we're done14:59
ajoI'm working on the last right now, look-> (1sec)14:59
*** obondarev has quit IRC14:59
ajooh, an this one owed by you: https://bugs.launchpad.net/neutron/+bug/148660714:59
openstackLaunchpad bug 1486607 in neutron "tenants are able to detach admin enforced QoS policies from ports or networks" [Undecided,In progress] - Assigned to yong sheng gong (gongysh)14:59
*** glauco has quit IRC14:59
*** obondarev has joined #openstack-meeting15:00
gongyshthat is almost done. I will update a new patch set.15:00
*** zhipeng has joined #openstack-meeting15:00
*** jlibosva has left #openstack-meeting15:00
ajogongysh, me: https://review.openstack.org/#/c/220164/ and https://review.openstack.org/#/c/214218/515:00
*** fifieldt has quit IRC15:00
*** obondarev has quit IRC15:00
*** cbader has joined #openstack-meeting15:00
*** garyk1 has joined #openstack-meeting15:01
*** haomaiwang has quit IRC15:01
*** haomaiwang has joined #openstack-meeting15:01
*** haomaiwang has quit IRC15:01
*** mattgriffin has joined #openstack-meeting15:01
*** annp has quit IRC15:02
gongyshajo: I add myself into the reviewers for these two, I will do it later.15:02
*** garyk has quit IRC15:02
*** hodos has joined #openstack-meeting15:02
*** banix has quit IRC15:02
*** gampel1 has quit IRC15:03
*** geoffarnold is now known as geoffarnoldX15:04
*** geoffarnoldX is now known as geoffarnold15:04
*** nadya has quit IRC15:04
*** banix has joined #openstack-meeting15:04
*** rfolco has joined #openstack-meeting15:04
*** adahms has quit IRC15:04
*** stanchan has quit IRC15:04
*** lazy_prince has quit IRC15:05
*** chandankumar has quit IRC15:06
*** Daisy has joined #openstack-meeting15:06
*** ZZelle has left #openstack-meeting15:06
*** korzen has quit IRC15:07
*** aranjan has quit IRC15:07
*** baojg has quit IRC15:09
*** Piet has joined #openstack-meeting15:10
*** VanL has quit IRC15:11
*** pm90_ has joined #openstack-meeting15:11
*** carl_baldwin has quit IRC15:11
*** geoffarnold is now known as geoffarnoldX15:12
*** hashar has quit IRC15:12
*** rainya has joined #openstack-meeting15:12
*** geoffarnoldX is now known as geoffarnold15:12
*** VanL has joined #openstack-meeting15:13
*** ijw_ has joined #openstack-meeting15:14
*** changbl has joined #openstack-meeting15:14
*** ijw_ has quit IRC15:15
*** kencjohn_ has joined #openstack-meeting15:16
*** mattgriffin has quit IRC15:16
*** toscalix__ has quit IRC15:17
*** toscalix__ has joined #openstack-meeting15:17
*** ivar-lazzaro has quit IRC15:18
*** mattgriffin has joined #openstack-meeting15:18
*** wbhuber has quit IRC15:19
*** rhochmuth has joined #openstack-meeting15:20
*** salv-orlando has quit IRC15:20
*** mrmartin has quit IRC15:21
*** zeih has quit IRC15:22
*** mrmartin has joined #openstack-meeting15:22
*** fzdarsky_ is now known as fzdarsky15:23
*** wbhuber has joined #openstack-meeting15:24
*** yamahata has quit IRC15:24
*** dims_ has joined #openstack-meeting15:25
*** eantyshev has quit IRC15:26
*** cloudtrainme has quit IRC15:26
*** garyk has joined #openstack-meeting15:26
*** yamahata has joined #openstack-meeting15:26
*** garyk1 has quit IRC15:27
*** cloudtrainme has joined #openstack-meeting15:28
*** topol has joined #openstack-meeting15:28
*** afazekas_ has quit IRC15:28
*** bradjones has joined #openstack-meeting15:28
*** bradjones has quit IRC15:28
*** bradjones has joined #openstack-meeting15:28
*** janonymous_ has joined #openstack-meeting15:29
*** dimsum__ has quit IRC15:29
*** electrocucaracha has quit IRC15:29
*** sankarshan is now known as sankarshan_away15:29
*** dprince has quit IRC15:29
*** dprince has joined #openstack-meeting15:30
*** salv-orlando has joined #openstack-meeting15:30
*** Daisy has quit IRC15:31
*** pm90__ has joined #openstack-meeting15:31
*** electrocucaracha has joined #openstack-meeting15:31
*** jdurgin1 has joined #openstack-meeting15:31
*** Daisy has joined #openstack-meeting15:31
*** peristeri has quit IRC15:33
*** vgridnev has quit IRC15:33
*** balajiiyer has quit IRC15:33
*** pm90___ has joined #openstack-meeting15:33
*** baoli_ has quit IRC15:33
*** balajiiyer has joined #openstack-meeting15:34
*** baoli has joined #openstack-meeting15:34
*** pm90_ has quit IRC15:35
*** phil_ has joined #openstack-meeting15:36
*** niska has quit IRC15:36
*** pm90__ has quit IRC15:36
*** Daisy has quit IRC15:36
*** salv-orlando has quit IRC15:36
*** carl_baldwin has joined #openstack-meeting15:37
*** irenab has quit IRC15:38
*** irenab has joined #openstack-meeting15:39
*** dkranz has joined #openstack-meeting15:39
*** Swami has joined #openstack-meeting15:40
*** garyk has quit IRC15:42
*** devlaps has joined #openstack-meeting15:43
*** bobmel_ has joined #openstack-meeting15:43
*** niska has joined #openstack-meeting15:43
*** tiswanso has quit IRC15:44
*** edtubill has left #openstack-meeting15:45
*** tiswanso has joined #openstack-meeting15:45
*** bobmel has quit IRC15:45
*** safchain has quit IRC15:45
*** hodos has quit IRC15:46
*** doffm_ is now known as doffm15:46
*** alop has joined #openstack-meeting15:48
*** numans has quit IRC15:49
*** hichihara has quit IRC15:49
*** yassine__ has quit IRC15:51
*** otter768 has joined #openstack-meeting15:52
*** matrohon has quit IRC15:52
*** aimon has quit IRC15:53
*** barker has joined #openstack-meeting15:53
*** chandankumar has joined #openstack-meeting15:54
*** nadya has joined #openstack-meeting15:55
*** otter768 has quit IRC15:57
*** hemna_ is now known as hemna15:57
*** barker has quit IRC15:57
*** GB21_ has joined #openstack-meeting15:57
*** GB21 has joined #openstack-meeting15:57
*** GB21 has quit IRC15:58
*** GB21_ is now known as GB2115:58
*** mattgriffin has quit IRC15:59
*** glauco has joined #openstack-meeting16:00
*** tsekiyama has quit IRC16:00
*** jprovazn has quit IRC16:00
*** comay has joined #openstack-meeting16:00
*** mattgriffin has joined #openstack-meeting16:01
*** ygbo has quit IRC16:01
*** iben has joined #openstack-meeting16:02
*** gyee has joined #openstack-meeting16:03
*** pm90___ has quit IRC16:03
*** pm90_ has joined #openstack-meeting16:04
*** safchain has joined #openstack-meeting16:04
*** glauco has quit IRC16:04
*** annegentle has joined #openstack-meeting16:05
*** vivek has joined #openstack-meeting16:06
*** sdake_ has joined #openstack-meeting16:06
*** vivek is now known as Guest346016:06
*** irenab has quit IRC16:06
*** Apoorva has joined #openstack-meeting16:06
*** irenab has joined #openstack-meeting16:07
*** glauco_ has joined #openstack-meeting16:08
*** zhipeng has quit IRC16:08
*** vahidh has joined #openstack-meeting16:09
*** doug-fis_ has joined #openstack-meeting16:09
*** moha_hunt has joined #openstack-meeting16:09
*** doug-fish has quit IRC16:09
*** yamahata has quit IRC16:10
*** VikasC has joined #openstack-meeting16:10
*** ijw_ has joined #openstack-meeting16:10
*** rvasilets has quit IRC16:12
*** unicell has quit IRC16:12
*** cloudtrainme has quit IRC16:13
*** leeantho has joined #openstack-meeting16:15
*** ijw_ has quit IRC16:15
*** jlanoux_ has quit IRC16:16
*** yamahata has joined #openstack-meeting16:16
*** esker has joined #openstack-meeting16:16
*** gongysh has quit IRC16:18
*** garyk has joined #openstack-meeting16:18
*** Zhongjun_ has joined #openstack-meeting16:19
*** cdub has joined #openstack-meeting16:21
*** tiswanso has quit IRC16:22
*** pnavarro has quit IRC16:22
*** beagles_ has joined #openstack-meeting16:23
*** alexsyip has joined #openstack-meeting16:25
*** winston-d has joined #openstack-meeting16:25
*** ricolin has quit IRC16:25
*** nadya has quit IRC16:26
*** rhagarty has joined #openstack-meeting16:26
*** Guest3460 has quit IRC16:26
*** rhagarty_ has joined #openstack-meeting16:26
*** phil_ has quit IRC16:29
*** edleafe has quit IRC16:29
*** lyanchih has quit IRC16:29
*** kebray has joined #openstack-meeting16:31
*** pballand has joined #openstack-meeting16:31
*** edleafe has joined #openstack-meeting16:31
*** dims_ has quit IRC16:31
*** dimsum__ has joined #openstack-meeting16:32
*** whenry has quit IRC16:32
*** achanda has joined #openstack-meeting16:32
*** mpaolino has quit IRC16:34
*** kebray has quit IRC16:34
*** tiswanso has joined #openstack-meeting16:36
*** dannywilson has joined #openstack-meeting16:36
*** mattgriffin has quit IRC16:36
*** vgridnev has joined #openstack-meeting16:37
*** mattgriffin has joined #openstack-meeting16:37
*** andreykurilin__ has joined #openstack-meeting16:39
*** mdbooth has quit IRC16:39
*** aimon has joined #openstack-meeting16:41
*** kencjohn_ has quit IRC16:41
*** doug-fis_ has quit IRC16:41
*** aimon has quit IRC16:42
*** aimon has joined #openstack-meeting16:42
*** jdurgin1 has quit IRC16:42
*** derekh has quit IRC16:42
*** kebray has joined #openstack-meeting16:42
*** leeantho has quit IRC16:43
*** dflorea has joined #openstack-meeting16:44
*** amotoki has quit IRC16:46
*** winston-d has quit IRC16:46
*** leeantho has joined #openstack-meeting16:47
*** kencjohn_ has joined #openstack-meeting16:48
*** Jeffrey4l has quit IRC16:49
*** tsekiyama has joined #openstack-meeting16:50
*** ayoung has quit IRC16:52
*** ayoung_ has quit IRC16:53
*** Brian has joined #openstack-meeting16:54
*** FallenPegasus has joined #openstack-meeting16:54
*** Brian is now known as Guest8695616:54
*** dane_leblanc has quit IRC16:55
*** achanda has quit IRC16:56
*** achanda_ has joined #openstack-meeting16:56
*** lpetrut has quit IRC16:56
*** e0ne has quit IRC16:56
*** fitoduarte has joined #openstack-meeting16:57
*** earlephilhower has quit IRC16:57
*** Guest86956 has quit IRC16:58
*** davidjc has joined #openstack-meeting16:58
*** VW_ has quit IRC16:59
*** VW_ has joined #openstack-meeting17:00
*** tsekiyama has quit IRC17:00
*** VW_ has quit IRC17:00
*** mattgriffin has quit IRC17:00
*** doug-fish has joined #openstack-meeting17:00
*** VW_ has joined #openstack-meeting17:00
*** GB21 has quit IRC17:01
*** mattgriffin has joined #openstack-meeting17:01
*** barker has joined #openstack-meeting17:01
*** unicell has joined #openstack-meeting17:02
*** Jeffrey4l has joined #openstack-meeting17:02
*** harlowja has joined #openstack-meeting17:03
*** tfukushima has joined #openstack-meeting17:03
*** kebray has quit IRC17:04
*** afazekas_ has joined #openstack-meeting17:05
*** KunalGandhi has joined #openstack-meeting17:05
*** rossella_s has quit IRC17:06
*** rossella_s has joined #openstack-meeting17:06
*** dannywilson has quit IRC17:06
*** unicell has quit IRC17:06
*** unicell has joined #openstack-meeting17:06
*** tsymanczyk has joined #openstack-meeting17:08
*** achanda_ has quit IRC17:08
*** ijw_ has joined #openstack-meeting17:10
*** KunalGandhi has quit IRC17:10
*** yamahata has quit IRC17:11
*** davidjc has quit IRC17:11
*** vivek has joined #openstack-meeting17:12
*** vivek has quit IRC17:12
*** ayoung has joined #openstack-meeting17:13
*** ayoung_ has joined #openstack-meeting17:13
*** KunalGandhi has joined #openstack-meeting17:14
*** yamahata has joined #openstack-meeting17:14
*** tsekiyama has joined #openstack-meeting17:14
*** davidjc has joined #openstack-meeting17:14
*** barker has quit IRC17:17
*** sdake_ has quit IRC17:19
*** xingchao has quit IRC17:19
*** dabo- has joined #openstack-meeting17:20
*** dwalleck has joined #openstack-meeting17:20
*** achanda has joined #openstack-meeting17:21
*** electrocucaracha has quit IRC17:21
*** yfried_ has joined #openstack-meeting17:21
*** iurygregory has joined #openstack-meeting17:22
*** irenab has quit IRC17:22
*** vahidh has quit IRC17:23
*** stevemar has joined #openstack-meeting17:23
*** electrocucaracha has joined #openstack-meeting17:23
*** afazekas_ has quit IRC17:24
*** tsekiyama has quit IRC17:24
*** moha_hunt has quit IRC17:24
*** Apoorva has quit IRC17:25
*** Apoorva has joined #openstack-meeting17:26
*** ociuhandu has quit IRC17:26
*** earlephilhower has joined #openstack-meeting17:27
*** electrocucaracha has quit IRC17:28
*** dwalleck has quit IRC17:28
*** Swami has quit IRC17:28
*** lsmola has quit IRC17:29
*** dflorea has quit IRC17:29
*** barker has joined #openstack-meeting17:31
*** dflorea_ has joined #openstack-meeting17:31
*** pelix has quit IRC17:33
*** nelsnelson has quit IRC17:34
*** pelix has joined #openstack-meeting17:34
*** rvasilets has joined #openstack-meeting17:34
*** Jeffrey4l has quit IRC17:35
*** Swami has joined #openstack-meeting17:36
*** SridharG has left #openstack-meeting17:36
*** dabo- has quit IRC17:36
*** safchain has quit IRC17:37
*** vahidh has joined #openstack-meeting17:38
*** nelsnelson has joined #openstack-meeting17:39
*** dwalleck has joined #openstack-meeting17:39
*** neelashah has quit IRC17:41
*** mudassirlatif has joined #openstack-meeting17:42
*** gongysh has joined #openstack-meeting17:42
*** samueldmq has joined #openstack-meeting17:43
*** VanL has quit IRC17:43
*** sdake has joined #openstack-meeting17:44
*** dabo- has joined #openstack-meeting17:46
*** davidjc has quit IRC17:46
*** yamahata has quit IRC17:46
*** e0ne has joined #openstack-meeting17:47
*** glauco_ has quit IRC17:47
*** rbowen has quit IRC17:49
*** jamespage_ has joined #openstack-meeting17:51
*** glauco has joined #openstack-meeting17:52
*** markvan has joined #openstack-meeting17:52
*** otter768 has joined #openstack-meeting17:53
*** pabelanger has joined #openstack-meeting17:54
*** toscalix__ has quit IRC17:54
*** hamzy has joined #openstack-meeting17:56
*** beagles has quit IRC17:56
*** VanL has joined #openstack-meeting17:57
*** otter768 has quit IRC17:57
*** mattgriffin has quit IRC17:58
*** electrocucaracha has joined #openstack-meeting17:59
*** nelsnelson has quit IRC17:59
*** doug-fis_ has joined #openstack-meeting17:59
*** doug-fi__ has joined #openstack-meeting18:00
*** shaleh has joined #openstack-meeting18:00
*** SheenaG has joined #openstack-meeting18:00
*** cloudtrainme has joined #openstack-meeting18:00
*** baoli has quit IRC18:00
*** lhcheng has joined #openstack-meeting18:00
*** yamahata has joined #openstack-meeting18:00
dstanekpinging ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rharwood, rodrigods, roxanaghe, samueldmq, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub18:00
lbragstaddstanek: o/18:00
*** henrynash has joined #openstack-meeting18:00
tsymanczyko/18:00
*** banix has quit IRC18:00
lhchengo/18:00
*** davidjc has joined #openstack-meeting18:00
stevemaro/18:00
samueldmqhi o/18:00
*** vgridnev has quit IRC18:00
henrynashhello18:00
ayoung_I'm here18:00
raildoo_18:00
htrutao/18:00
samueldmqayoung_, hey18:00
SheenaGHi all18:00
ericksonsantoso/18:00
stevemarsenor dstanek hosting again :)18:00
dstanektoday will be busy - lots on the agenta!18:00
gyee\o18:00
* geoffarnold lurking - pulled into another mtg18:01
*** beagles has joined #openstack-meeting18:01
stevemarlets do it up!18:01
dstanek#startmeeting keystone18:01
openstackMeeting started Tue Sep  8 18:01:09 2015 UTC and is due to finish in 60 minutes.  The chair is dstanek. 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
dstanekwoot!18:01
dstanek#topic Keystoneclient v2 branch18:01
bknudsonhi18:01
*** openstack changes topic to "Keystoneclient v2 branch (Meeting topic: keystone)"18:01
*** beagles is now known as Guest7406818:01
*** Brian has joined #openstack-meeting18:01
*** baoli has joined #openstack-meeting18:01
*** mattgriffin has joined #openstack-meeting18:01
dstanekjamielennox you around?18:01
stevemarbknudson: hi18:01
*** cloudtrainme has quit IRC18:01
*** doug-fish has quit IRC18:01
*** Brian is now known as Guest3683018:01
*** pvaneck has joined #openstack-meeting18:01
claudiubo/18:02
*** VanL has quit IRC18:02
dstanekif not we can skip and defer until later...18:02
stevemardstanek: defer?18:02
dstanekstevemar: whatever jamie wanted to discuss18:02
bknudsonwe can't make big breaks.18:02
*** banix has joined #openstack-meeting18:02
ayoung_dstanek, he might still be waking up18:03
dstanekayoung_: yeah, i figured18:03
topolo/18:03
stevemarjust bump it to the end of the agenda18:03
ayoung_++18:03
*** nelsnelson has joined #openstack-meeting18:03
bknudsoncircle back18:03
*** doug-fis_ has quit IRC18:03
dstanek#topic Changing driver version numbers....looking for guidance on how this should work?18:03
*** openstack changes topic to "Changing driver version numbers....looking for guidance on how this should work? (Meeting topic: keystone)"18:03
dstanekhenrynash!18:04
henrynashok, so dstanek and I started to chat about this18:04
henrynashFirst…wasn’t celar to me if the driver versions are now released/frozen?18:04
*** rbowen has joined #openstack-meeting18:04
henrynash(I have this bug fix that wants to add three new driver methods)18:04
bknudsonI think they're frozen.18:05
bknudsonat feature freeze18:05
*** dflorea_ has quit IRC18:05
*** pabelanger has left #openstack-meeting18:05
gyeedidn't he have FFE?18:05
hogepodgeo/18:05
*** Guest36830 has quit IRC18:05
henrynashgyee: this is for a bug fix, not a new bp18:05
dstanekso does that mean that this particular bug needs to wait until M and can't be merged into L without a FFE?18:06
*** vgridnev has joined #openstack-meeting18:06
amakarovhenrynash, can you give a link please?18:06
*** egallen_ has quit IRC18:06
*** vgridnev has quit IRC18:06
*** KunalGandhi has quit IRC18:06
henrynashhttps://review.openstack.org/#/c/191976/18:06
gyeehenrynash, so these methods can't be implemented in the compatibility layer?18:07
henrynashgyee: so, no….but that raises a second question18:07
*** nadya has joined #openstack-meeting18:07
henrynashgyee: in our developing_drivers.rst we say that we will add naive implementaions to the “old driver”18:08
*** edleafe- has joined #openstack-meeting18:08
*** ihrachys has quit IRC18:08
henrynashgyee: which actually wasn’t what I was expecting….but that’s what I followed in teh patch I have submitted18:08
*** dabo- has quit IRC18:08
dstanekhenrynash: so here's how i was picturing this18:08
*** Guest74068 has quit IRC18:09
dstanekwe release L on V8 versions of drivers and M on V9. if things are added to V9 then they have to be added to V8 (via a method in core.py so a driver implementer is not required to do anything)18:09
dstaneksome people have differing ideas on when to version18:09
gyeeso anything you need at the atomic level, should be provided by the old drivers by now, and any optimization that the old drivers doesn't have at the moment should be implementd at the naive layer.18:10
dstaneki like per release because it's really easy to know what the current and supported versions actually are18:10
henrynashdstanek: I also like per release or I think we’ll all get confused18:10
*** dflorea has joined #openstack-meeting18:11
gyeesame argument apply to, say, adding a param to the public API in order to fix a bug18:11
dstanekhenrynash: yes, v8 or identity, v10 of assignments, etc... yes, can get very confusing18:11
*** dwalleck has quit IRC18:11
henrynashgyee, dstanek: so since I need a new sql table, looks like I can’t fix this in M18:11
henrynashsorry, I mean L18:11
dstanekwe should treat driver API changes like we to REST API changes now. so i'm assuming that means FFE at this point?18:11
gyeedstanek, ++18:12
*** carl_baldwin has quit IRC18:12
* morgan is lurking.18:12
*** b3nt_pin has joined #openstack-meeting18:12
morganYes i would say ffe or similar18:12
* bknudson also lurks18:12
* stevemar kicks out lurkers18:12
*** b3nt_pin is now known as Guest3643518:13
* gyee high fives stevemar18:13
lbragstadso all interfaces are locked down after milestone 3?18:13
henrynashdtsanek: and when we do add a new version, as you said on IRC…we add this to the same driver file…but how do we use config to load the right driver?18:13
stevemarunless they have an FFE18:13
*** cdub has quit IRC18:13
henrynashstevemar: would we allow an FFE that chanegd the interfaces?18:14
bknudsonif it's not changing interfaces is it a feature?18:14
*** browne has joined #openstack-meeting18:14
*** VanL has joined #openstack-meeting18:15
dstanekso i think FFE unless there are other thoughts here...18:15
bknudsonI guess a new backend would be considered a feature.18:15
*** dflorea has quit IRC18:15
stevemarhenrynash: i would think so18:16
*** cdub has joined #openstack-meeting18:16
gyeebut a feature doesn't mean it must change the interface18:16
dstanekbknudson: yeah, and we could do other things that add features using config, etc.18:16
morgandstanek: that would be my choice18:16
dstanekok, i want to keep us moving18:16
henrynashbknudson, stevemar, dtsanek: I imagined teh need for an FFE is just since we are landing code late taht is dangerous…if we are serious about supporting driver writers, I think we have to lock the interface at L318:16
gyeehenrynash, how about locking all interfaces by L2, both API and driver18:17
dstanekhenrynash: i say yes for now. we have to start the process sometime and in the future i think this will matter more and more18:17
stevemarlock all *existing* interfaces18:17
gyeeif we are treating driver interfaces like public APIs18:17
stevemarnot new ones18:18
henrynashgyee: I think L2 is too restrictive (now that we are saying we’l support teh old version for a full release)...18:18
dstanek#agreed we have frozen the v8 driver APIs as of L3 and require a FFE to make changes to them18:18
topolcan we document somewhere that driver interfaces are analogous to public APIs/18:18
topolif thats the way we go18:18
dstanek#action dstanek to follow up in the l2 vs l3 debate and write it in the docs18:19
gyeesure, I agree18:19
stevemartopol: we started to doc this18:19
henrynashdstanek: ….and i think we need a very good reason to allow an FFE that changes them18:19
bknudsonI missed V1-7.18:19
stevemartopol: http://docs.openstack.org/developer/keystone/developing_drivers.html18:19
topolstevemar awesome18:19
stevemarbknudson: we all did :(18:19
*** armax has quit IRC18:19
henrynashbknduson: they were great!18:19
*** xingchao has joined #openstack-meeting18:19
*** scinawa has joined #openstack-meeting18:19
dstanekbknudson: we let versioning slide! it was actually V*18:19
stevemarv1-v7 had no issues!18:20
dstanek#topic keystonemiddleware tests broken by keystoneclient release18:20
*** openstack changes topic to "keystonemiddleware tests broken by keystoneclient release (Meeting topic: keystone)"18:20
henrynashok, I’ll change with dstanek after on my otehr quetsions on versions18:20
dstanek#link https://bugs.launchpad.net/python-keystoneclient/+bug/1492600 (bug assigned to davechen)18:20
openstackLaunchpad bug 1492600 in python-keystoneclient "Session._send_request(...) doesnt catch the exception properly" [Critical,In progress] - Assigned to Dave Chen (wei-d-chen)18:20
henrynash(I’ll chat wth)18:20
bknudsonanybody have time to look at this?18:20
topolstevemar so it just needs to be updated with our stated direction then18:20
*** jamespage_ has quit IRC18:20
dstanek#link http://logs.openstack.org/13/208213/2/check/gate-keystonemiddleware-python27/3e14ede/console.html.gz#_2015-09-04_17_56_39_63118:20
dstanek#link https://review.openstack.org/#/c/220736/ Proposed change to ksc18:20
bknudsonotherwise it'll be my top priority after I get some other work done.18:20
stevemartopol: yep, sounds like something for you to do :P18:20
stevemar*delegate up!*18:20
bknudsonksm is blocked currently18:20
bknudsonmight be something I broke.18:20
topolstevemar, cool18:20
*** hashar has joined #openstack-meeting18:20
dstanekbknudson: is this the deprecation stuff?18:21
ayoung_#action blk-u fix KC18:21
bknudsonthat was it.18:21
* topol stevemar always throws me bones :-)18:21
gyeebknudson, link? which review is broken?18:21
bknudsonI don't know. I haven't looked at it.18:21
gyeenm18:21
bknudsonall recent keystonemiddleware changes are failing18:22
bknudsonsince the keystoneclient release.18:22
ayoung_raildo, don't -1 something that is a rollback...lets get it fixed, and investigate underlying cause second18:22
gyeeohhh! not exception mapping again18:22
ayoung_dstanek, bknudson do we need https://review.openstack.org/#/c/220736/2 to unblock?18:22
gyeewe went through that once18:23
bknudsonayoung_: I haven't looked at it enough to know if https://review.openstack.org/#/c/220736/2 is the fix.18:23
ayoung_k18:23
raildoayoung_: ok :)18:23
gyeeI don't like that fix18:23
*** shashank_hegde has joined #openstack-meeting18:24
gyeecatching ConnectionError twice18:24
*** banix has quit IRC18:24
ayoung_since it makes it through check, does that mean it fixes the issue?18:24
bknudsonif that change is necessary then we've made a backwards-incompatible change18:24
dstanekgyee: two different exceptions though18:24
bknudsonso we should revert the change if we can figure out which one it is.18:24
*** banix has joined #openstack-meeting18:24
stevemarwe will also need a ksc release18:24
dstanekbknudson: is this something that you have time for? or are you looking for someone to step up?18:25
gyeedstanek, I bet we mapped the ConnectionError somewhere18:25
gyeeredefined18:25
bknudsondstanek: I'll have time, but it won't be until tomorrow at the earliest.18:25
* stevemar didn't realize we releases a new ksc version yesterday....18:25
*** sdake_ has joined #openstack-meeting18:25
*** xingchao has quit IRC18:26
stevemarwhere was the ML announcement on that one18:26
dstanekgyee: if it were the same class, just "redefined" through imports it would be fine. this would appear to be a while new exception18:26
stevemarerr.. on friday18:26
bknudsonwho does releases on friday before labor day?18:26
morganbknudson: sorry :(18:26
stevemarit was anti-morgan, the evil one18:27
morganIt was supposed to go out on ... Uh thursday18:27
morganOr wednesday18:27
ayoung_they anti-morgan is the good one18:27
*** Zhongjun_ has quit IRC18:27
ayoung_otherwise my minion-to-evil-overlord contract is null18:27
lhchengagree with bknudson, we should rollback rather than just fixing the tests to pass.18:28
lhchengbknudson: I have some time later in the afternoon, I can start looking at it.18:28
bknudsonthat would be great, thanks lhcheng!18:28
dstanekok!18:28
*** carl_baldwin has joined #openstack-meeting18:28
dstanek#action lhcheng to start looking into the ksm issue caused by the ksc release.18:29
dstanek#topic python-keystoneclient uses socket attributes that do not exist in Windows18:29
dstaneksocket.TCP_KEEPCNT and socket.KEEPINTVL do not exist in windows. because of this, the nova-compute service running on Hyper-V is not able to create instances.18:29
*** openstack changes topic to "python-keystoneclient uses socket attributes that do not exist in Windows (Meeting topic: keystone)"18:29
*** e0ne has quit IRC18:29
claudiubo/18:29
dstanek#link https://review.openstack.org/#/c/211686/ proposed partial fix to make creating instances on Hyper-V possible18:29
*** sdake has quit IRC18:29
stevemarugh, who the heck is using windows18:29
dstanekclaudiub: all you18:29
morganUgh. Yah so we should fix that fast and release18:30
stevemaroh its claudiub i'll be nice :)18:30
claudiubty. so, we really want this...18:30
*** dane_leblanc has joined #openstack-meeting18:30
*** Apoorva_ has joined #openstack-meeting18:30
bknudsonif windows is important let's get some ci for it.18:30
claudiubwe've been hitting this more and more often18:30
morganbknudson: ++18:30
claudiubeven in the hyper-v ci18:30
dstaneki thought the change was OK based on the docs, but i have not tried to actually use it on windows18:31
claudiuband johnthetubaguy had the same problem with os x18:31
lbragstados x 10.10 i believe18:31
dstanekreally?18:31
claudiubyeah, he commented on the patch and the bug report18:31
*** zeih has joined #openstack-meeting18:32
stevemarthis fix seems completely reasonable to me18:32
ayoung_running the client from Windows seems reasonable.18:32
bknudsonthe bug is Medium importance.18:32
claudiubit won't break anything that already exists18:32
morganOs x is not officially supported18:32
*** dflorea has joined #openstack-meeting18:32
stevemarmorgan: not even for the clients?18:32
claudiubit just makes sure it won't die for windows and os x18:32
bknudsonthere's no ci for OS X either.18:32
stevemarand this doesn't change existing behaviour18:32
morganNot unless someone ci's it18:32
*** Apoorva has quit IRC18:33
morganWindows there is ci possible18:33
dstanekok, so we just need people to go look at the review18:33
*** elo has joined #openstack-meeting18:34
lbragstadamakarov: had some questions on it, but I think they've been answered...18:34
stevemareven on L941 we have OS specific handling18:34
stevemarthis seems like a no-brainer18:34
ayoung_he was asking if the CR is incomplete.18:34
dstaneksounds like nobody has objections so i'd like to move on18:34
stevemarerr, not OS-specific, but we have similar checks18:34
ayoung_I thin the answer is no;  they have a todo but it needs a requests change18:34
dstanekit would be nice to get sigmavirus24's opinion in there too if he hasn't already commented18:34
ayoung_and it is a "should" not a "must"18:34
*** cloudtrainme has joined #openstack-meeting18:34
amakarovlbragstad, ?18:35
ayoung_amakarov, care  to remove your -1?18:35
*** ivar-lazzaro has joined #openstack-meeting18:35
ayoung_https://review.openstack.org/#/c/211686/7/keystoneclient/session.py18:35
lbragstadamakarov: your comment here - https://review.openstack.org/#/c/211686/18:35
*** chandankumar has quit IRC18:35
amakarovlbragstad, aha, I see it18:36
*** zeih has quit IRC18:36
sigmavirus24dstanek: sorry waht's up?18:36
amakarovMy question is answered indeed? thank you18:36
amakarovs/?/,/18:36
claudiubok, so I only have to change the TODO to a NOTE?18:36
dstaneksigmavirus24: we're talking about https://review.openstack.org/#/c/21168618:36
sigmavirus24Yeah that's a reasonable review18:37
sigmavirus24I still need to find time to add ioctl support to urllib318:37
dstanekclaudiub: i also agree with jamie's comment about the link18:37
*** mudassirlatif has quit IRC18:37
sigmavirus24but that's something the author and I are in agreement about adding18:37
sigmavirus24Just a matter of me finding time to do it how we discussed18:37
*** dflorea has quit IRC18:37
*** novas0x2a|laptop has joined #openstack-meeting18:37
dstaneksigmavirus24: do you have an issue already created for it or would you like us to do it?18:38
sigmavirus24dstanek: we haven't created one yet, but I can create that18:38
ayoung_leave as a TODO18:38
claudiubk18:39
ayoung_it should be done, but can't be until the requests change is n18:39
ayoung_is in18:39
*** dflorea has joined #openstack-meeting18:39
dstanekclaudiub: we should link to the requests issue too18:39
*** VanL has quit IRC18:39
lbragstad++18:39
dstanekok, so we just need some minor things here including some eyeballs on the review18:39
*** ociuhandu has joined #openstack-meeting18:39
stevemartodo -> note + link to requests18:40
*** sdake_ is now known as sdake18:40
*** cloudtrainme has quit IRC18:40
bknudsonit's even got nice unit tests.18:40
claudiubcool, can you paste the link to requests?18:40
*** pabelanger has joined #openstack-meeting18:40
*** achanda has quit IRC18:40
lbragstadclaudiub: that will probably have to wait until the issue it created.18:40
lbragstads/it/is/18:41
*** cloudtrainme has joined #openstack-meeting18:41
dstaneklbragstad: ++18:41
dstanekok, moving on18:41
*** dflorea has quit IRC18:41
claudiubalso, seems to be mixed opinions on wheter it should be a todo or a note18:41
claudiubok18:41
claudiubty :)18:41
dstanek#topic Policies18:41
dstanekFFE has been requested?18:41
bknudsonlet's bikeshed it some more.18:41
*** openstack changes topic to "Policies (Meeting topic: keystone)"18:41
dstaneksamueldmq: you....18:41
samueldmqhello everybody :)18:41
dstanekclaudiub: they can debate in the review :-)18:41
*** achanda has joined #openstack-meeting18:41
samueldmqI basically want to discuss with you the need for FFE vs Postpone on this subject18:41
samueldmqall the code in the implementation now is < 600 lines, and need some reviews18:42
stevemarlol @ bknudson18:42
samueldmq#link Server: https://review.openstack.org/#/c/216851/18:42
samueldmq#link Middleware: https://review.openstack.org/#/c/205049/18:42
samueldmq#link Oslo: https://review.openstack.org/#/c/200257/18:42
*** dzamboni has quit IRC18:42
samueldmqonly the oslo.policy one is needing an update to deal with some lock, etc18:43
samueldmqwhen dealing with files18:43
samueldmq+ CacheControl support in ksclient, which is something dstanek was looking at18:43
dstaneksamueldmq: so what is the need for a FFE?18:43
*** baoli has quit IRC18:43
samueldmqdstanek, to get it merged this cycle we need a FFE, right ?18:44
samueldmqI wanted to know if someone is already for/against it as FFE, and if we go for it, we need some cores to signup for review18:44
dstaneksamueldmq: no, i mean what's the case for doing it? you have to persuade the voters18:45
*** vijendar has quit IRC18:45
*** dwalleck has joined #openstack-meeting18:45
samueldmqdstanek, k, so .. the feature everyone knows, we have relaxed the implementation which is much more consisntent and simpler for now18:45
samueldmqgyee put us in contact with some guys of HP public cloud (stackholders)18:46
samueldmqand we checked they won't be able to use it in L even if it's merged, because it'll be experimental18:46
bknudsonwe should always use the term "stackholders"18:46
*** sdake_ has joined #openstack-meeting18:46
samueldmqhowever to become stable, everything needs to be experimental previously (right morgan ?)18:47
samueldmqso that's my call for opening a FFE on it18:47
*** banix has quit IRC18:47
samueldmqwe have stackholders, we have the code, we need eyes on it18:47
morgansamueldmq: yes. Experimental first.18:47
samueldmqand would like to check whether the core team is for/against it18:47
gyeeanybody besides me are going to review it?18:47
*** vgridnev has joined #openstack-meeting18:48
dstaneksamueldmq: so you are making the case to wait? since nobody will use it is there a reward?18:48
samueldmqdstanek, no.. HP public cloud won't use it before it is stable, but it won't be stable before being experimental18:48
henrynashsamueldmq: so the argumetn taht we must put it in no simply becuase we think allowing a relase cycle to go by will make it stable is not a good arguemnt18:49
*** dwalleck has quit IRC18:49
*** etoews has joined #openstack-meeting18:49
samueldmqhenrynash, makes sense, because people have to use it to make it stable, not just waiting18:49
henrynashif something is good, solid and we really need it, we have said that it is possible to go from experimental to stable in a cycle18:49
bknudsonwe at least give them the opportunity to use it18:49
*** sdake has quit IRC18:49
*** garthb has joined #openstack-meeting18:49
dstaneksamueldmq: it also can't be stable until it's done. since we are building up to the real functionality will is be stable anytime soon?18:49
samueldmqhowever I do believe we have other stackholders as well, like good feedbacks we've received in the operators ML18:49
*** dflorea has joined #openstack-meeting18:50
bknudsonif they don't take advantage and then have complaints later it's their own fault18:50
* lbragstad 10 minutes left18:50
*** dflorea has quit IRC18:50
bknudsonthen again, they can cherry-pick the changes and try it that way.18:50
samueldmqdstanek, we'll have it all (the delivery) .. the implementation is simpler now18:50
dstaneksamueldmq: do they want HTTP policy or dynamic policy?18:50
gyeedynamic policy, but isn't HTTP a requirement?18:51
samueldmqdstanek, fetching is part of all the dynamic stuff18:51
samueldmqgyee, ++18:51
stevemarsamueldmq: looks like you are changing the response of an API18:51
*** mmmpork has joined #openstack-meeting18:51
samueldmqstevemar, we include a header: Cache-Control18:51
samueldmqstevemar, so yes, we're chaging it18:52
dstaneksamueldmq: so HTTP policy is experimental now and will be stable in M, dynamic policy would be experimental in M and stable in N?18:52
gyeeI can do dynamic and have them delivered by a bunch of mice18:52
henrynashI thought we agreed we would kill the phrase “dynamic policy”….it is centralised policy….peopl can be really dynamic today with their own cms18:52
samueldmqdstanek, the rest of the features in dynamc policies, possibly yes18:52
*** dflorea has joined #openstack-meeting18:52
samueldmqhenrynash, ++18:52
stevemarsamueldmq: not just that, but you add 'freshness' to http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-endpoint-policy.html#get-effective-policy-associated-with-endpoint18:52
*** yolanda has joined #openstack-meeting18:52
morgandstanek: not stable in M18:52
morganMight be stable in M18:52
lbragstadhenrynash: ++18:52
dstanekok, put it to a vote?18:52
samueldmqdstanek, that comes from controller, and is extracted in the wsgi level18:52
*** rbradfor has joined #openstack-meeting18:53
samueldmqdstanek, yes please18:53
*** KunalGandhi has joined #openstack-meeting18:53
samueldmqif that makes sense to everybody to make it a vote18:53
bknudsonif nobody's going to sign up to review it there's no point to the vote.18:53
ayoung_so...18:53
ayoung_HTTP policy would be really nice...18:53
dstanek#vote FFE for the policy over HTTP changes. allow it? yes,no18:53
dstanek#startvote FFE for the policy over HTTP changes. allow it? yes,no18:54
samueldmq#vote yes18:54
openstackBegin voting on: FFE for the policy over HTTP changes. allow it? Valid vote options are yes, no.18:54
openstackVote using '#vote OPTION'. Only your last vote counts.18:54
henrynashsamueldmq: however, we should be under no illusion that getting it in now as experiemtal means it will be made stable in M….that’s down to whether we think it is ready18:54
ayoung_#vote yes18:54
dstanekstarting would have helped18:54
samueldmq#vote yes18:54
bknudson#vote no18:54
morganhenrynash: ++18:54
samueldmqhenrynash, yes I agree, it can get experimental now, and stable in N or so, with the rest of policy stuff18:54
bknudsonI don't think it's worth the chance of instability.18:54
dstanek#vote no18:54
*** electrocucaracha has quit IRC18:54
ayoung_you guys are being short sighted18:55
*** ttrifonov is now known as zz_ttrifonov18:55
ayoung_this is what the operators want18:55
gyee#vote yes18:55
ayoung_at least give it to them experimental18:55
dstaneki'm worried about the new cache table and the logic surrounding refreshing18:55
morganayoung_: i disagree this is what "operators want" it was a "oh sure that18:55
*** banix has joined #openstack-meeting18:55
samueldmqdstanek, I removed that, we are accepting inconsistencies when updates occur18:55
amakarovayoung_, so we18:55
*** davidjc has quit IRC18:55
samueldmqdstanek, as we discussed before18:55
morganMight be nice" when asked at the ops midcycle18:55
ayoung_morgan, horsepocky18:55
morganBut not "omg we need that"18:55
stevemar#vote no18:55
amakarovwe'll have plenty bugs to solve and be respected for that ))18:55
ayoung_the number ofthings that are limited by our RBAC implementation are growing18:56
stevemarthere's still way too much disagreement about the direction here, and we would benefit from further discussion18:56
ayoung_we need to start making some progress18:56
morgan#vote no18:56
*** cdub has quit IRC18:56
*** pelix has quit IRC18:56
* ayoung_ ragequite18:56
ayoung_note not quit18:56
ayoung_just quite rageful18:56
stevemarayoung_: FWIF you are slowly convincing me18:56
samueldmqhenrynash, htruta sorry for the timing18:56
stevemarFWIW*18:56
dstanekayoung_: i thought that was supposed to be ragequiet18:56
henrynash#vote no18:57
stevemarquietly rage18:57
ayoung_FWTF18:57
htrutasamueldmq: that's ok18:57
topol#vote no18:57
ayoung_actually...I am starting to rethink deploying hierarchical roles in the token18:57
*** achanda has quit IRC18:57
ayoung_that might actually be the better solution18:57
lhcheng#vote no18:57
ayoung_implied roles18:57
lbragstad#vote no18:57
ayoung_but...I'll save that for later18:58
dstaneklast call for votes....18:58
samueldmqdstanek, k ... should be enough for now18:58
dstanek#endvote18:58
openstackVoted on "FFE for the policy over HTTP changes. allow it?" Results are18:58
openstackyes (3): ayoung_, gyee, samueldmq18:58
openstackno (8): dstanek, lhcheng, bknudson, lbragstad, topol, morgan, henrynash, stevemar18:58
samueldmqdstanek, would appreciate if we have some minutes to reseller18:58
samueldmqok guys, postpone was the decision18:58
dstanekwe have slightly less than 2...18:58
samueldmqthanks :)18:58
dstanek#topic Reseller18:58
*** openstack changes topic to "Reseller (Meeting topic: keystone)"18:58
dstanekif we have the time......18:58
htrutaI'd just like to question if it is reasonable to have an FFE18:59
dstanekhenrynash, htruta maybe we should move this to -keystone18:59
henrynashhtruta: it just seems TOO much code18:59
raildodstanek: ++18:59
*** electrocucaracha has joined #openstack-meeting18:59
htrutaif it isn't I suggest we decide a cut point at the reseller chain that does not break people18:59
htrutadstanek: sure18:59
dstanekok, we're out of time.... lets discuss in our own channel19:00
dstanek#endmeeting19:00
lbragstadthanks all19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Sep  8 19:00:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-08-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-08-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-08-18.01.log.html19:00
samueldmqthanks19:00
*** derekh has joined #openstack-meeting19:00
Clinto/19:00
*** amakarov is now known as amakarov_away19:00
*** dwalleck has joined #openstack-meeting19:00
jeblairhowdy infras19:00
*** SheenaG has left #openstack-meeting19:00
clarkbhello19:00
*** doug-fi__ has quit IRC19:00
fungiw00t!19:00
yolandao/19:00
jesusaurushullo19:00
docaedoo/19:01
mmedvedeo/19:01
pleia2o/19:01
rfolcohi19:01
pabelangero/19:01
ianwo/19:01
*** lhcheng has left #openstack-meeting19:01
*** doug-fish has joined #openstack-meeting19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Sep  8 19:01:30 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. 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
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-01-19.01.html19:01
*** doug-fish has quit IRC19:01
jeblair#topic Specs approval: Artifact Signing Toolchain (fungi)19:01
*** openstack changes topic to "Specs approval: Artifact Signing Toolchain (fungi) (Meeting topic: infra)"19:02
jeblair#link Artifact Signing Toolchain https://review.openstack.org/21329519:02
*** doug-fish has joined #openstack-meeting19:02
*** doug-fish has quit IRC19:02
mordredo/19:02
jhesketho/19:02
jeblairfungi warned us this would be coming up this week :)19:02
*** cloudtrainme has quit IRC19:02
fungii've addressed everyone's comments so far, so assumed it was time to punt it to a vote19:02
mordredI, for one, welcome our Artifact Signing overlords19:02
*** neelashah has joined #openstack-meeting19:02
*** doug-fish has joined #openstack-meeting19:02
fungijust a reminder, this is only securing one piece of the publication chain, but i'm trying to leave it open to flexible solutions for the other parts later19:03
*** shaleh has left #openstack-meeting19:03
jeblair++19:03
*** cloudtrainme has joined #openstack-meeting19:03
fungiprimarily this should make post-publication tampering obvious19:03
anteayayou are so accomodating that way19:03
*** cdub has joined #openstack-meeting19:04
jasondotstaro/19:04
* jhesketh has had it on his review radar but hasn't had a chance yet. I'll do that today (more than happy to see it go to vote) 19:04
fungianyway, i have nothing really to say which isn't already said in that change19:04
jeblairno one is screaming, so let's put it to a vote!19:04
mmmporko/19:04
jeblair#info Artifact Signing Toolchain voting open until 2015-09-10 19:00 UTC19:04
*** cloudtrainme has quit IRC19:04
fungithanks!19:05
anteayathank you19:05
jeblairfungi: thank you!19:05
jeblair#topic Schedule Project Renames19:05
*** openstack changes topic to "Schedule Project Renames (Meeting topic: infra)"19:05
*** adduarte has joined #openstack-meeting19:05
ociuhanduo/19:05
jeblairwe have some renames scheduled for friday19:05
anteayaI've created an etherpad to organize the patches for friday19:05
fungithanks anteaya!!!19:05
pleia2thanks anteaya19:05
fungilink?19:05
jasondotstarnice19:05
anteaya#link https://etherpad.openstack.org/p/project-renames-Septemeber-201519:05
anteayawho wants to drive the renames19:05
*** dwalleck has quit IRC19:06
pleia2oh good, ansible is on there this time :)19:06
anteayaI'll co-ordinate with whoever drives19:06
anteayaI can do the legwork and get them into shape19:06
anteayawhen are we no longer accepting additions to the list19:06
anteayaso I can start the rebases19:06
*** pabelanger has quit IRC19:06
*** neelashah has quit IRC19:06
fungiit went well the last time i wasn't involved, so i'm happy to see another infra root who isn't me take point, but can if there are no volunteers19:06
anteayafungi: ha ha ha19:07
anteayapleia2: I'm going with you are a bit frazzled with last week and zanata19:07
mordredI may be around - or I may be stupid jetlagged and asleep - or I may be stupid jetlagged and AWAKE19:07
mordredso consider me a wildcard bonus19:07
*** dane_leblanc has quit IRC19:07
* fungi doesn't want to steal maintenance opportunities from new recroots19:07
mordredfungi: ++19:07
anteayajhesketh: driven a rename yet?19:07
*** rbradfor has left #openstack-meeting19:07
anteayajhesketh: it's lots of fun19:07
*** davidjc has joined #openstack-meeting19:07
jasondotstardoes it have to be a root?19:07
*** rfolco has quit IRC19:07
anteayaand you will get help19:08
anteayajasondotstar: yes19:08
jeblairanteaya: we did schedule it for jhesketh's saturday morning19:08
pleia2anteaya: yeah, I can help but I probably shouldn't be driver this time19:08
jasondotstaranteaya: ack.19:08
anteayajhesketh: what a fun way to spend a saturday19:08
anteaya:)19:08
pleia2lol19:08
fungigo ahead and put me down to coordinate19:08
*** neelashah has joined #openstack-meeting19:08
pleia2thanks fungi19:08
anteayafungi: thanks19:08
anteayaI'll get it in shape so you can push go19:08
clarkbsorry I am here and intend on being there19:08
clarkbif fungi wants a break I can drive19:08
jeblairi will also be around19:08
jheskethNo I haven't yet. But I'll be travelling to the QA sprint from Friday19:09
anteayafungi: I'll will let you do your own etherpad with the db changes and steps and so on19:09
*** vgridnev has quit IRC19:09
anteayajhesketh: ah that's right19:09
jhesketh(everything takes so long to get to from here!)19:09
anteayaor clarkb19:09
anteayajhesketh: ha ha ha19:09
jheskethOtherwise would love to help19:09
*** baoli has joined #openstack-meeting19:09
anteayaso the expected renames, two are not in governance19:09
anteayamove them to the stackforge wikipage?19:10
anteayaother action?19:10
jeblairanteaya: sounds good to me19:10
fungii think we decided we don't want to incorporate non-big-tent renames in this maintenance, so yeah19:10
anteayaokey dokey I will move them19:10
anteayaand try to track down the patch author if possible19:10
anteayano promisies though19:11
anteayathat's all from me on this19:11
*** VanL has joined #openstack-meeting19:11
jeblairregarding oct 17; what needs to be done?  probably an analysis of how many projects are on the lists....19:11
jeblairand then writing some scripts to automate the actual change....19:11
anteayaI can start an etherpad on that to co-ordinate19:12
jeblairmordred: think we can ansible it?19:12
fungiwhich will become immediately out of date within hours, but is probably at least good for an estimate19:12
*** dwalleck has joined #openstack-meeting19:12
anteaya#link https://etherpad.openstack.org/p/Stackforge-Namespace-Retirement19:13
*** zehicle has joined #openstack-meeting19:13
mordredjeblair: we can ansible it19:13
*** isq_ has quit IRC19:13
jheskethWe can ansible anything? :-)19:13
mordredthere is a WIP patch up if anyone want to help me test it19:13
anteayamordred: link?19:13
jeblairmordred: should we try it friday?19:13
mordredone sec- link coming19:13
anteayaI'll add it to the etherpads19:13
fungii would like to see it at least get a test drive before we use it on potentially hundreds of repos at once19:14
* anteaya agrees with fungi19:14
jheskethI like the idea of the trying it19:14
jasondotstarfungi: +119:14
mordredhttps://review.openstack.org/#/c/105057/3/modules/openstack_project/files/ansible/rename.yaml19:14
jhesketh+119:14
fungithough that implies more mordred involvement in the maintenance window this week... were you planning to be around?19:14
mordredwould be great to get other eyes/hands on that _before_ friday19:14
anteaya#link https://review.openstack.org/#/c/105057/319:14
*** cloudtrainme has joined #openstack-meeting19:15
anteayaneeds a bit of love19:15
*** fitoduarte has quit IRC19:15
mordredfungi: _maybe_ - I will have just travelled to europe, so I'm not sure what my level of brain vs. jetlagbrain will be19:15
mordredso I'm not comfortable being counted on for important decision making19:15
*** fitoduarte has joined #openstack-meeting19:15
*** baoli has quit IRC19:15
fungimordred: sounds like your usual shrödinger's brain conundrum19:15
anteayaanyone able to spend time on this patch working with mordred before friday?19:16
*** vijendar has joined #openstack-meeting19:16
mordredbut if someone else is interested in the topic - I'd be thrilled to connect this week before friday on looking at the playbook and stuff19:16
jeblairthis is a good opportunity for a non-root to pitch in on the rename if they are familiar with ansible and/or can be around friday19:16
*** aorourke has joined #openstack-meeting19:16
mordred(also, I tink that playbook needs to be rewritten a little bit)19:16
*** baoli has joined #openstack-meeting19:16
*** VanL has quit IRC19:16
mordredas it should probably have several places where it iterates over a list of dicts - but whoever is interested we can chat about that19:17
Clinti'm intrigued by the juxtaposition of -rf and -fr19:17
anteayaI will if noone else will but not sure if I can finish it by friday19:17
clarkbmordred: its also easy enough to iterate in bash19:17
*** vgridnev has joined #openstack-meeting19:17
*** dwalleck has quit IRC19:17
clarkbmordred: in fact I find that is preferable to me based on the d-g work19:17
fungireally, the biggest benefit would be github automation19:17
clarkbansible is bad at branching logic19:17
anteayafungi: so focus on getting the github pieces to work first?19:18
jasondotstarjeblair: I can help w/ that (the non-root activities)19:18
fungimoving directories on the filesystem and updating database tables takes nearly 0 time and effort to custom-automate19:18
clarkbfungi: I don't think the current change talks to github19:18
*** aranjan has joined #openstack-meeting19:18
clarkbalso doesn't talk to the db19:18
mordredclarkb: actually no19:18
anteayabut github still requires renaming via the gui, yes?19:18
mordredI tink you want to iterate in ansible very specifically19:18
mordredbut we can have that argument later19:18
jeblairlast i checked the github api didn't expose the transfer function19:18
fungii've actually stopped generating database and filesystem update commands manually anyway19:19
mordred(there is no branching logic needed in this playbook)19:19
clarkbmordred: there is if its a transfer vs rename19:19
clarkbmordred: for github19:19
mordredthere is no github api support for renames19:19
clarkbbut I think thats the only place that cares19:19
mordredso it doesn't matter19:19
jeblairsomeone should double check that though19:19
mordred++19:19
anteayagreat, the biggest piece we need automated19:19
fungigot it. and yeah that's going to be the time-consuming part for "the big rename"19:19
clarkbthat really ruins the benefits of automating this imo19:19
clarkbright19:20
clarkbanyways19:20
*** kebray has joined #openstack-meeting19:20
mordredI feel like I have a much better version of that somewhere too19:20
*** rockyg has joined #openstack-meeting19:20
*** pabelanger has joined #openstack-meeting19:20
*** kebray has quit IRC19:20
jeblairi have no script to do any of this.  i think it's great that fungi has a script to do part of it.  but really it would be awesome if as much as possible were automated and checked into system-config.19:20
*** samuel-dmq has joined #openstack-meeting19:20
pabelangersorry, irc proxy died19:20
mordredjeblair: ++19:21
*** kebray has joined #openstack-meeting19:21
jeblairand yeah, a lot of it could be done in bash, but we know that there are cross-host coordination issues, so at least orchestrating it should be in ansible (even if it ends up calling bash)19:21
clarkbjeblair: I am not suggesting it be done in bash19:21
anteayaif folks can add bits to https://etherpad.openstack.org/p/Stackforge-Namespace-Retirement I will do my best to summarize19:21
clarkbjeblair: I was merely saying instead of passing in a giant hash of projects that ansible should do in one go we can exec ansible many times for each project19:21
jeblairclarkb: sure, as long as we only reindex once.19:22
*** samueldmq has quit IRC19:22
mordredand I'm saying that I believe that's missing the point of ansible and we might as well just use bash and some ssh commands19:22
mordredand that this is a bounded enough problem that learning how to actually use the tool would be great19:23
clarkbya we don't need to argue this here, its just a thing I have observed when trying to condense d-g further19:23
mordredagree19:23
clarkbit becomes almost unreadable as soon as ansible is encoding logic19:23
fungiyeah, the cross-host orchestration part does make this tempting19:23
jeblairwho wants to double check the github api?19:23
clarkbjeblair: I can look at that today19:24
mordredclarkb: I tnk the d-g mix gets worse as we do more complex playbook things for sure19:24
jeblair#action clarkb see if github api supports transfers yet19:24
jeblair#action mordred look into better version of https://review.openstack.org/105057 or improve it19:24
*** samuel-dmq has quit IRC19:24
jeblair#action jasondotstar help mordred with ansibly things19:24
jeblairanything else?19:25
anteayajust are we having a cut off for adding projects to friday's list19:25
jeblairanteaya: is friday morning enough time for you?19:26
anteayait will be19:26
anteayathank you19:26
anteayawhat utc time is friday morning?19:26
* mordred wishes he could find his better version he already wrote :(19:26
asselin_o/19:26
*** tfukushima has quit IRC19:26
*** isq_ has joined #openstack-meeting19:26
fungianteaya: i would just pick a time before you expect to sit down at your computer19:27
anteayabefore 1300 utc19:27
jeblair#info cutoff for friday renames friday 1300 utc19:27
anteayathank you19:27
*** aysyd has quit IRC19:27
jeblair#action anteaya prepare rename patches for friday renames19:27
*** adam_g` is now known as adam_g19:27
jeblairanteaya: thank you19:27
*** adam_g has quit IRC19:28
*** adam_g has joined #openstack-meeting19:28
jeblair#topic Priority Efforts (Migration to Zanata)19:28
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:28
*** dflorea has quit IRC19:28
jeblairthis is, like, imminent, yeah?19:28
fungiit's upon us19:28
*** aranjan has quit IRC19:28
anteayaa few hours from now I think19:28
*** aranjan has joined #openstack-meeting19:28
jeblairis there an etherpad or something?19:28
pleia2tonight! https://etherpad.openstack.org/p/zanata-deploy19:28
fungiit's now imminent and will soon be eminent19:28
jeblair#link https://etherpad.openstack.org/p/zanata-deploy19:29
anteayacan standers by be of any use?19:29
anteayaor should I stand back in awe?19:29
jeblairheh, stand by or stand back.19:29
pleia2we'll be doing some testing once we complete all the steps in the etherpad19:30
pleia2may be useful to have a few folks around to log in and poke at things a little, but not required19:30
*** aysyd has joined #openstack-meeting19:30
fungithat's verging into drinkytime for me, so i'll pitch in on anything i am unlikely to be able to break19:30
anteayaheh19:30
jeblairi have a meatspace commitment so probably can't be around for most of it :(19:31
pleia2always fun with time zones for translations things19:31
*** shashank_hegde has quit IRC19:31
anteayaI can do the poking at things19:31
anteayawooo time zones19:31
pleia2I think we're pretty much all set though19:31
anteayayay19:31
anteayagood work all19:31
clarkbit would likely be good for infra roots to login sometime soon so we can bump their privs19:31
jeblairpleia2: cool, thanks!19:31
clarkbby soon I mean after it all heppns19:31
jeblairoh ok.19:31
mordredclarkb: so not soon like right now19:31
* jeblair closes tab19:32
anteayaha ha ha19:32
* mordred backs away from the zanata19:32
pleia2mordred: it's ok, you have one :)19:32
*** mattgriffin has quit IRC19:32
clarkbwell now would be fine too since we are moving the users19:32
jheskethI'll be around if needed19:32
clarkbbut I don't think it needs to happen yet if you want to do other things19:32
pleia2thanks jhesketh19:32
anteayajhesketh: yay19:32
*** ianychoi has quit IRC19:33
*** pabelanger has quit IRC19:33
fungihuh... so its openid integration is... interesting19:33
fungianyway, done19:33
*** ianychoi has joined #openstack-meeting19:33
jheskethI'm hoping I'm not needed though because I'm not that familiar with the work19:33
jeblairfungi: ?19:33
*** mattgriffin has joined #openstack-meeting19:33
jeblairfungi: what's interesting about it?19:33
*** cdub has quit IRC19:33
fungiit doesn't actually ask the openid server for name, e-mail address, et cetera19:34
fungijust re-prompts for them19:34
*** moha_hunt has joined #openstack-meeting19:34
*** yamamoto has quit IRC19:34
fungisomething which can probably be improved later19:34
jeblairoh, interesting.  and indeed, you said it was interesting.19:34
*** dflorea has joined #openstack-meeting19:34
pleia2we were just satisfied with "it actually works" for now19:34
jeblairi shoulda just believed you.19:34
fungipleia2: totally19:35
fungii would have been too19:35
anteayapleia2: yay it works19:35
pleia2(it did require an openstackid patch to get this far)19:35
*** pabelanger has joined #openstack-meeting19:35
fungianyway, i seem to be account 43319:35
anteayalucky you19:35
fungiit's prime19:36
jeblairsounds like we're set; pleia2: thanks again!19:36
pleia2fungi: oh, translate or translate-dev?19:36
anteayaha ha ha19:36
fungiand has digits which add up to 1019:36
jeblair#topic Priority Efforts (Maniphest)19:36
*** openstack changes topic to "Priority Efforts (Maniphest) (Meeting topic: infra)"19:36
fungipleia2: oh, good point, i logged into production. i guess that won't do any good19:36
*** kebray has quit IRC19:36
jeblairmordred: what's the scoop here?19:36
pleia2fungi: right, we're moving stuff from -dev (and dropping all else)19:36
mordredso ...19:37
mordredI need some help19:37
* fungi just realized that when you asked19:37
mordrednext step on this is for $someone to stand up a maniphest $somewhere with cauth configured in apache in front of it19:37
mordredthis will involve $someamount of figuring out exactly what's needed to get that to happen19:38
Clintwhat happened to mhu?19:38
mordredbut is a pre-req for encoding that in puppet19:38
jeblairmordred: have the necessary changes to cauth itself to support openid happened?19:38
mordredClint: mhu wrote the openid support into cauth for us - is he also planning on helping with the puppeting of the cauth interation?19:38
mordredjeblair: yes19:38
Clintmordred: http://docs-draft.openstack.org/72/219372/5/check/gate-infra-specs-docs/625a32a//doc/build/html/status/maniphest.html19:38
*** achanda has joined #openstack-meeting19:38
Clintunless i halucinated that19:38
mordredoh! neat!19:38
mordredthen maybe I do _not_ need help19:39
Clintl19:39
jeblairmordred: or more correctly, maybe you already have it!19:39
mordredin any case- that is the current thing this is waiting on19:39
mordredjeblair: ++19:39
*** yamahata has quit IRC19:39
fungiyou already have that which you seek!19:39
anteayawho has contact with mhu?19:39
jeblairClint: what timezone is mhu in?  and do they irc?19:39
anteayadoes he know about infra meetings?19:39
anteayahe/she19:40
Clinti'm guessing he's in europe, and he's in #openstack-infra19:40
jeblaircool, we should ask him to lurk in -meeting19:40
anteayaI just pinged in -infra19:40
jeblairClint, mordred: i feel like "hey we linked to a web page that shows someone is working on this" is an outcome second only to "oh this has already been done".19:41
ttxmordred: hah, the death of your Phab instance means my mockup for task tracking is no longer up :/19:42
ttxThe one in case (3) at https://wiki.openstack.org/wiki/Phabricator19:42
jeblairClint, mordred: so... cool.  :)19:42
* ruagair is fashionably late19:42
Clintjeblair: to be fair, it shows that two other things aren't being worked on19:42
mordredttx: oops19:42
jeblairClint: yah.... #3 looks like it has #1 as a prereq, yeah?19:43
Clintpresumably19:43
jeblairmordred: ^?19:43
mordredyes19:43
mordred#3 has #1 as a prereq19:43
jeblair#2 is ripe for someone to pitch in on though.19:43
*** dwalleck has joined #openstack-meeting19:43
mordredor might wind up being part of #1 (unsure)19:43
mordred#2 is great - it may require rooter collaboration19:43
jeblairfor what?19:44
mordredsince it involves someone importing storyboard dbs into a db, then running the migration script19:44
jeblairmordred: ah, providing a sb dump?19:44
mordredyeah19:44
jeblairi would be happy to hand a sb db dump to someone wanting to work on that.19:44
*** Brian has joined #openstack-meeting19:45
jeblairprobably just need to omit the auth tokens table.19:45
Clintare there success criteria for migration accuracy?19:45
fungiyeah, that's the only remotely sensitive bit in there19:45
*** Brian is now known as Guest2074319:45
mordredClint: I'd _love 100% accuracy19:45
*** achanda has quit IRC19:45
*** andreykurilin__ has quit IRC19:46
clarkband if we can preserve the old bug numbers like we did with lp to sb that would be double awesome19:46
mordredso - honestly, this will involve the actor in question setting up a phab instance that they can run on top of the db (not that hard, there is puppet) so that the data in the UI can be verified19:46
mordredclarkb: the script currently does that19:46
clarkbyay19:46
fungijust like ragu... it's in there19:46
mordredthe script shoudl mostly work19:47
*** dflorea has quit IRC19:47
jeblairi think it would be swell if one of the new infra folk wanted to jump in on this.19:47
mordredhowever, last time I spot checked the UI, there seemed to be things missing - which might have been because I picked poor data to spot check - or that ther eis a bug in the script19:47
jeblairif you do, let me know.19:47
mordredthings to look at especially are things with mutliple tasks19:47
*** maishsk has joined #openstack-meeting19:48
jeblairanything else on this?19:49
*** sdake_ is now known as sdake19:49
*** Guest20743 has quit IRC19:50
*** dwalleck has quit IRC19:50
jeblair#topic Open discussion19:50
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:50
tchaypojeblair: If one of the new infra people wants to jump in on this, I’m guessing they should ask in -infra if they need help getting started?19:50
yolandaso, i need extra help with reviews of puppet changes19:50
*** dane_leblanc has joined #openstack-meeting19:50
fungitchaypo: yes19:50
yolandaseveral of them waiting with a +219:50
yolandaand the patches i submit, normally only have +119:50
clarkbthe git backends are now all centos719:50
anteayaclarkb: yay!19:51
*** banix has quit IRC19:51
yolandai'd like if more infra cores can give help on it, please19:51
clarkbjust a general FYI and do mention weirdness if yo usee an19:51
clarkbI should probably make a new git.o.o at some point so we can stop centos6ing there too19:51
mordredyolanda: sorry - I said i'd do that and then I didn't19:51
anteayaclarkb: just what eantshev (?) mentioned on monday after the third-party meeting19:51
yolandamordred, i was thinking about you, yes :)19:51
clarkbanteaya: unfortunately there really wasn't any info there and I was weekending19:51
anteayaclarkb: but fungi couldn't confirm weirdness in logs19:51
anteayaclarkb: /nod19:52
clarkbanteaya: the connection failed, but I didn't see any source IPs19:52
yolandaso more eyes are needed, so we can move these patches faster19:52
clarkbso hard to track down19:52
* ruagair is interested Jeblair, tchaypo, just not fully functional this early.19:52
anteayaclarkb: fair enough, that was all I have heard about though19:52
yolandai also normally cannot approve due to the timezones, so i'll need extra help for approval as well19:52
mmedvedere f21 job stability, would it be a good idea to ask for the f21 job to be made voting on devstack project? I want to make sure before bringing it up in qa. It has been relatively stable recently.19:52
*** henrynash has quit IRC19:52
jeblairruagair, tchaypo: cool, i think mordred or i can help you bootstrap; chat with one of us in -infra when you're ready19:53
clarkbmmedvede: I think thats purely a question for qa19:53
fungialso etherpad.openstack.org is running on ubuntu trusty with distro node.js packages, latest etherpad develop branch tip and websockets enabled. seems to be performing well now, but please report any strangeness there!19:53
*** ddieterly has joined #openstack-meeting19:53
clarkbmmedvede: we run the jobs, whether or not qa wants it voting is up to them19:53
anteayafungi jeblair thanks for fixing that this morning19:53
ruagairnoted jeblair.19:53
mordredjeblair, ruagair, tchaypo: ++19:53
fungitaron mentioned that there's a change in review which gets us closer to hound19:53
mmedvedeclarkb: cool. I remember there was discussion in infra about f21 stability, that is why my question, thanks19:53
fungi#link https://review.openstack.org/21164019:53
clarkbmmedvede: also I think ianw and pabelanger are working to replace f21 with f22 whihc may or may not be a thing to consider19:53
*** otter768 has joined #openstack-meeting19:54
pabelangeralso, centos7 firewalld is still failing. I think https://review.openstack.org/#/c/219031/ should fix that now19:54
*** amrith is now known as _amrith_19:54
clarkbpabelanger: ianw ya I need to test that on hpcloud again19:54
pabelangerYa, some dnf downloadonly issues still with fedora2219:55
*** mrmartin has quit IRC19:55
clarkbpabelanger: ianw I will try that today, but it may take time as I haveto figure ut netowkring there each time I do it19:55
*** neelashah has quit IRC19:55
ianwi think we can bring up f22 nodes, regardless of caching ATM, and work that out19:55
pabelangerYa, was going to suggest that too19:55
pabelangerdon't see many things using it right now19:56
mmedvedepabelanger: before f22 comes along, is it ok if I ask to make f21 voting (given it is stable)?19:56
ianwit would be better for us to be monitoring things like puppet4 compatability than waiting for perfection.19:56
ianwmmedvede: on what project?19:56
mmedvedeianw: on devstack19:56
*** dflorea has joined #openstack-meeting19:56
*** jecarey has quit IRC19:56
pabelangermmedvede: I wasn't tracking devstack specifically. This was for some other reasons, -infra jobs maybe puppet19:57
*** jmckind has joined #openstack-meeting19:57
mmedvedeianw: pabelanger: my interest here is that we use f21 for our third-party CI, and making it vote at least on devstack would prevent some regressions19:57
ianwso i do not think we want it voting on devstack, because i don't think there are enough people to fix issues.  if it breaks, and urgent devstack changes need to get through, we could be in a world of gate-pain19:58
mmedvedeianw: :(19:58
*** dwalleck has joined #openstack-meeting19:58
*** iben has quit IRC19:58
*** otter768 has quit IRC19:58
*** derekh is now known as derekh_afk19:58
*** dwalleck has quit IRC19:59
mmedvedeianw: I might still ask in qa, just in case19:59
sdaguemmedvede: also, f21 has been 100% fail on devstack for a while, so I'm not sure what your definition of stable is19:59
*** yamahata has joined #openstack-meeting19:59
ianwsdague: i believe afazekas has sorted that out20:00
mmedvedesdague: it has been good a couple of days #link http://ci-watch.tintri.com/project?project=devstack&time=7+days20:00
*** dwalleck has joined #openstack-meeting20:00
mmedvedesdague: more time needs to pass though20:00
jeblairtime is up20:00
jeblairthanks all!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Sep  8 20:00:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-08-19.01.html20:00
*** yolanda has left #openstack-meeting20:00
jheskethCheers20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-08-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-08-19.01.log.html20:00
mmedvedethank you20:00
sdaguemmedvede: http://tinyurl.com/nl6h752 - upstream20:00
ttxAnyone here for the TC meeting ?20:00
markmcclaino/20:00
lifelesso/20:00
sdaguettx: o/20:00
jaypipes...................o.../20:01
rhochmutho/20:01
*** pabelanger has left #openstack-meeting20:01
mordredo/20:01
mordredjaypipes: nice20:01
annegentlehere20:01
* edleafe admires jaypipes20:01
* jaypipes fell on floor and then raised hand.20:01
edleafeall that running!20:01
ttxrussellb, jgriffith, flaper87, dtroyer, jeblair, dhellmann: around ?20:01
flaper87o/20:01
jeblairttx: o/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Sep  8 20:01:37 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
* rockyg is shaking jaypipes' hand20:01
ttxAgenda for this Technical committee meeting lives at:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
*** mmmpork has left #openstack-meeting20:02
*** jkeen has joined #openstack-meeting20:02
ttx#topic Adding Monasca to OpenStack20:02
*** openstack changes topic to "Adding Monasca to OpenStack (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/21318320:02
ttxTwo weeks ago we decided to table Monasca application for two weeks20:02
ttxIn order for them to implement a few logistics change to further align with the OpenStack Way20:02
ttxBut also to give some TC members more time to investigate how closely Monasca worked with Ceilometer and/or API overlap issues20:02
jaypipes"some TC members"? :)20:02
ttx>=120:02
ttxAt this stage I'd say that while they were not exactly "one of us" in the past, they are now organized to be one of us in the future, and certainly feel responsive and motivated to do so20:02
* mordred looks at jaypipes20:02
jaypipesheh20:03
dhellmanno/20:03
*** gordc has joined #openstack-meeting20:03
ttxThat leaves jaypipes's objections20:03
edleafejaypipes: http://blog.leafe.com/establishing-apis/20:03
* dimsum__ sneaks in20:03
jaypipesttx: I agree that they are now organized to be one of us.20:03
ttxone is the question of compatible API between competing implementation of the same functionality, which arguably was never articulated before20:03
*** dimsum__ is now known as dims20:03
dtroyero/20:03
ttxtwo is fairness in comparison of how Fuel / GBP were treated, asking for the same kind of delay to assess cooperation20:04
*** geoffarnold has quit IRC20:04
jaypipesttx: it was indeed brought up in the GBP big tent proposal, which I brought up in my latest comment.20:04
*** dims is now known as Guest8007120:04
ttxSo I guess we should discuss both points20:04
dhellmannI tend to agree with jaypipes20:04
ttxdo we want compatible APIs for  competing implementation of the same functionality ?20:05
mordredfor one - I think I do not care about the API overlap if the two are not claiming the same key in the new keystone catalog20:05
dhellmannI read the logs from the first irc meeting, and noticed early on a discussion of an in-person whiteboarding session being scheduled, which seemed ironic20:05
edleafemordred: good point20:05
dhellmannbut I also agree with mordred in that I don't think API overlap is an issue20:05
mordredif monasca has a pile of ceilometer's API but is also different in some ways BUT calls itself by a different catalog key - Im fine with it20:05
flaper87mordred:++20:05
jaypipesmordred: the key being claimed by monasca in the projects.yaml patch is "telemetry"20:06
sdaguemordred: I agree with that, unless they are both trying to claim the same service catalog entry, same API seems weird20:06
*** davidjc has quit IRC20:06
*** dprince has quit IRC20:06
dhellmannthe problem with GBP wasn't the API, it was that they had not been able to work with the other teams working on networking, and that's a much lower-level feature than monitoring20:06
*** VanL has joined #openstack-meeting20:06
mordredjaypipes: is that the key they intend to have in the new world order of catalog with standards?20:06
annegentledo we have the Object Storage API implemented with ceph already?20:06
ttxdhellmann: so you would also ask for more time before reconsidering the application ?20:06
dhellmannttx: yes, to see how the community thing works out20:06
*** rbrndt has joined #openstack-meeting20:06
*** aeng_ has joined #openstack-meeting20:06
ttxPersonally I'm on the fence. I think waiting for mitaka is fine20:07
jaypipesdhellmann: there was also a number of points raised by me and mestery around the GBP API essentially supplanting the OpenStack Network API.20:07
flaper87dhellmann:++20:07
*** barker has quit IRC20:07
*** angdraug has joined #openstack-meeting20:07
mordredbecause if that is the case, I would like to say "no" to similar but also different things claiming the same catalog id - that seems like  road to insane20:07
rhochmuthi've left a lot of comments on why monasca isn't the same api as ceilometer20:07
* flaper87 is catching up on the topic since he didn't attend the meeting where this was first discussed20:07
jaypipesmordred: not sure. I suggested changing it to "monitoring" per rhochmuth's response to me about "what makes monasca different from ceilometer"20:07
*** dwalleck has quit IRC20:07
annegentlemordred: it would be crazy-making to have dupes in the catalog20:07
flaper87so mostly speaking based on generic cases, tbh20:07
rhochmuthalso, i've commented on the community and the number of organizations involved20:07
dhellmannjaypipes: right, if the rest of the community was not behind neutron, then I would support a competitor, but because there is support for neutron and it's a foundation piece I think the argument for duplication of feature set (not API, feature set) is a harder sell20:07
sdaguejaypipes: I agree that the service catalog entry should be changed20:08
ttxjaypipes: in the GBP case there was the question of diluting a pretty fundamental project, which had questionable value for our users20:08
rhochmuthi already think we are part of the openstack community20:08
mordredrhochmuth: so, in short- you think monasca and ceilomter API are same or different?20:08
*** Guest80071 is now known as dims__20:08
sdagueI also think that we should probably discuss monasca separate from GBP20:08
rhochmuththey are different20:08
ttxjaypipes: whereas in the monitoring game, multiple solutions are less likely to cause loss of value for our users20:08
dhellmannmordred, annegentle : yes, we can't allow dupes in the catalog, that would defeat the purpose of all of the consistency work being done there20:08
rhochmuthand the reasons have been documented20:08
mordredrhochmuth: great. are you planning on wanting the same keystone catalog id?20:08
*** hashar has quit IRC20:08
jaypipesttx dhellmann: sure, fair points both. I just thought there was enough similarity here for a pause before fast-tracking.20:08
dhellmannjaypipes: ++20:08
rhochmuthmonasca is more than about monitoring of openstack resources20:08
sdaguerhochmuth: the concern is L1194 here - https://review.openstack.org/#/c/213183/1/reference/projects.yaml,cm20:09
*** mudassirlatif has joined #openstack-meeting20:09
mordredrhochmuth: so you would not register in the keystone catalog as "telemetry" - but as "monitoring"?20:09
rhochmuthit is also highly performance and in production today at scale20:09
flaper87rhochmuth: I take that as a No to mordred's question20:09
*** dwalleck has joined #openstack-meeting20:09
ttxjaypipes: I'm fine with a pause, I see no reason for fast-tracking. But we need to address the question of compatible APIs or not20:09
rhochmuthi would register as monitoring20:09
* flaper87 phew20:09
mordredrhochmuth: awesome. I'm sold20:09
sdaguerhochmuth: ok, so you need to change L1194 then20:09
jaypipesrhochmuth: yes, that's what I figured, thus my comment on the projects.yaml file...20:09
rhochmuthoriginally when i wrote the submission i said monitoring20:09
mordredrhochmuth: I tink we need to ^^ that20:09
flaper87mordred: ditto20:09
rhochmuthand changed to telemetry20:09
rhochmuthdo be honest i don't know the difference20:09
mordredrhochmuth: sorry for the whiplash -let's change it back20:10
rhochmuthsure, i would chnage back20:10
jaypipesrhochmuth: thus my concern about overlapping APIs with the OpenStack Telemetry API ;)20:10
mordredrhochmuth: the thing is is related to a spec up by anne and sdague to get a consistent set of standards into the keystone catalog20:10
dhellmannrhochmuth: we don't want 2 projects using the same terminology there, because that's one of the key fields users have to tell projects apart20:10
rhochmuthi tend to use monitoring and telemetry interchangeably20:10
mordredrhochmuth: where we want to make sure we know what people are registering in the catalog as20:10
ttxok, so it seems we have a clear answer on the compatible APIs question20:10
annegentlerhochmuth: yeah don't do that :)20:10
jaypipesttx: :)20:10
rhochmuthok, will switch to monitoring20:10
dhellmannannegentle: ++20:10
lifelessrhochmuth: thank ou20:10
ttxthe question of timing remains20:10
*** dwalleck has quit IRC20:10
sdagueok, so if this gets sorted, are there other pressing concerns?20:10
*** VanL has quit IRC20:11
mordredrhochmuth: in this case, it means that someone saying keystone.session.get_session_endpoint('telemetry') gets a ceilomter endpoint and ...('monitoring') gets monasca20:11
jeblairttx: the answer is "we are okay with different apis for similar services as long as they have different names" ?20:11
rhochmuthsounds good to me20:11
annegentleI would like resolution on the multiple languages support and details of that scope before voting on monasca to be honest20:11
flaper87I seem to remember from the logs that there were some concerns about some Java code... Am I mixing up things?20:11
ttxjeblair: seems to be20:11
*** unicell has quit IRC20:11
rhochmuthwe actually want both ceilometer and monasca20:11
dhellmannsdague: well, I'd like to see the team actually be able to use the IRC meeting space, instead of immediately jumping to in-person and screen-sharing systems again (as was brought up in their first irc meeting)20:11
annegentleI'm not super comfortable with "we're Java now but we'll be Python on <timeline>"20:11
jaypipessdague: my final comment was this, which AFAIK, remains unaddressed: "Finally, another condition we asked the Fuel project to meet was alignment of the continuous integration systems used in Fuel development with those of the upstream infra CI. Does the Monasca community have a plan/roadmap for aligning with the upstream CI systems, particularly for the remaining Java parts of the Monasca project? We asked Fuel to put t20:11
jaypipeshis plan together. To not ask Monasca to do the same seems inconsistent to me."20:11
dhellmannrhochmuth: yes, I appreciate your comments clarifying that ceilometer is a source of input for monasca20:12
flaper87annegentle: ah-ha, so I'm not crazy. I did read that on the logs20:12
*** unicell has joined #openstack-meeting20:12
flaper87:D20:12
rhochmuthin the first irc meeting, we held it completely in irc20:12
rhochmuthwe had a performance issue that needed to follow-up20:12
rhochmuthwe discussed with all in irc how to do that20:12
mordredjaypipes: totally. but I believe monasca has been doing 100% of its CI in upstream CI, so I think that bit is already done, no?20:12
sdaguedhellmann: ok, I consider that a fair point20:12
dhellmannrhochmuth: yes, but one of the topics brought up was how to address an issue by having a separate meeting either in person or with screensharing, right?20:12
rhochmuthmany of us or local to the denver region20:13
mordredjaypipes: (I agree it's inconsistent, I just don't think it's the case)20:13
jaypipesmordred: our upstream CI supports testing Java components?20:13
mordredjaypipes: yes20:13
rhochmuthso we did a face to face and had cisco tele conference in20:13
jaypipesah, well awesome then.20:13
jeblairmordred, jaypipes, rhochmuth: it looks like there are both java and python unit tests, but i don't see integration tests, and of course the java tests hit the internet for deps.20:13
dhellmann"15:11:53 <rhochmuth> if it is just deklan and me, we could to a physical meeting, but if others want to be invovled, can do desktop sharing" from http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-09-02-15.00.log.html20:13
jaypipesjeblair: ty for that info, appreciated.20:13
sdaguejeblair: right, but so does diskimage-builder, for instance20:13
mordredjeblair, jaypipes: yah - there are places we need to flesh out the awesome for sure20:13
rhochmuthso we are completely in irc, unless we need to use teleconferencing20:13
annegentlerhochmuth: and are docs sphinx/rst/wadl (tobeswaggersoon)?20:13
mordredsdague: we need to flesh out the awesome there too20:13
flaper87does Monasca use rabbitmq ?20:13
rhochmuthwhich in this cases was required20:13
sdagueso not hitting the internet is not just a sin of this project20:13
rhochmuthmonasca doe not use rabbitmq20:14
* flaper87 should dig into this20:14
mordredsdague: we need tons more awesome :)20:14
jeblairso we've yet to have a java project volunteer to invest in fixing that20:14
ttxSO the remaining question is... do we consider that they are already "one of us" or could use more time to align, no need to hurry20:14
*** nadya has quit IRC20:14
jeblairsdague: yes, but dib folks are actively engaged in fixing that20:14
flaper87rhochmuth: any messaging technology?20:14
rhochmuthwe use kafka20:14
jaypipesjeblair: perhaps a member of the Monasca contributor team might provide that necessary help on the Java project front.20:14
mordredjaypipes: ++20:14
jeblairjaypipes: i think that would be swell20:15
rhochmuthrabbitmq can not sustaing the perofmrance we need, it is not durable, it does not handle ha well20:15
flaper87rhochmuth: gotcha20:15
* mordred has heard that there are humans who would like to discuss making an oslo.messaging backend for kafka20:15
flaper87rhochmuth: not judging, just looking for some info :D20:15
sdaguejaypipes: yeh, that would be the right place for that to come from, it sort of feeds into the lang support discussion20:15
ttxshould we do a quick show of hands to solve that remaining question ?20:15
dhellmann++20:15
flaper87mordred: yeah, there've been discussions since Atlanta20:15
lifeless++20:16
sdagueright, I've heard tons of rumble about kafka, so having something regularly poking that in upstream CI would be really interesting20:16
flaper87mordred: no one has step up for that yet20:16
gordcmordred: https://review.openstack.org/#/c/189006/20:16
mordredgordc: well then!20:16
jaypipesttx: you mean the question on CI alignment?20:16
*** dwalleck has joined #openstack-meeting20:16
jaypipesttx: or soemthing else? sorry, got lost here a bit.20:16
flaper87ttx: go20:16
sdaguettx: yes, I'm not sure which question you are asking about20:16
mordredI'm not sure what I'm showing my hands on20:16
* mordred waves hands just on general principle20:16
ttx<ttx> SO the remaining question is... do we consider that they are already "one of us" or could use more time to align, no need to hurry20:16
ttx<ttx> should we do a quick show of hands to solve that remaining question ?20:17
annegentlemore time seems helpfu20:17
flaper87gordc: oh, I had missed that20:17
annegentlehelpful even20:17
sdaguettx: well, I thought the hurry was whether or not they get any space in tokyo20:17
mordredttx: I am comfortable with their level of one of us20:17
annegentleyeah let's not hurry due to a summit20:17
rhochmuthi don't need space tor tokyo20:17
jaypipesttx: gotcha. well, I think it would be more consistent if we asked for a bit of a "prove yourselves" period, as we did with Fuel.20:17
gordcflaper87: it's been on and off. that said, i'm interested as well.20:17
ttxwell, space was allocated last week, so it's too late to get "regular" space now20:17
ddieterlywe are one of you20:17
jaypipesttx: 2 months, maybe.20:17
rhochmuthwill gladyl take spacei if available, but that isn't an issue to me20:17
mordredI'm not sure what I'd be asking them to do or how I'd judge it20:18
*** VanL has joined #openstack-meeting20:18
rhochmuthwhat is the action that i'm supposed to work on for 2 months?20:18
rhochmuthwould someone clarify this now?20:18
mordredrhochmuth: ++20:18
rhochmuth6 serious companies are working on this20:18
dhellmannrhochmuth: could you last 2 months with only video meetings?20:18
rhochmuthin is deployed in production20:18
dhellmannI mean only RIC20:18
dhellmannIRC20:18
jaypipesrhochmuth: I was looking for 8 unserious companies.20:18
rhochmuththere was no problems with last weeks irc20:18
annegentlerhochmuth: CI assignments, docs assignments?20:18
rhochmuthi actually enjoyed that20:19
rhochmuthhas some advantages20:19
*** davidjc has joined #openstack-meeting20:19
rhochmuthlike log files20:19
mordredlogging ++20:19
rhochmuthi think the meeting was productive20:19
ttxok, let me start a quick show of hands poll for the TC members20:19
ttx#startvote Can Monasca be considered "one of us" now or should it be given a couple months, waiting for Mitaka to further align to OpenStack ways? now, mitaka, dunno20:19
openstackBegin voting on: Can Monasca be considered "one of us" now or should it be given a couple months, waiting for Mitaka to further align to OpenStack ways? Valid vote options are now, mitaka, dunno.20:19
openstackVote using '#vote OPTION'. Only your last vote counts.20:19
mordred#vote now20:19
jaypipes#vote mitaka20:19
ttx#vote dunno20:19
annegentle#vote mitaka20:19
sdague#vote now20:19
lifeless#vote mitaka20:20
dhellmannrhochmuth: you haven't addressed my question about this part of the conversation: http://paste.openstack.org/show/450730/20:20
flaper87#vote mitaka20:20
dhellmann#vote mitaka20:20
markmcclain#vote mitaka20:20
lifeless#vote now20:20
*** GheRivero has joined #openstack-meeting20:20
ttx#endvote20:21
openstackVoted on "Can Monasca be considered "one of us" now or should it be given a couple months, waiting for Mitaka to further align to OpenStack ways?" Results are20:21
openstackmitaka (5): annegentle, jaypipes, dhellmann, flaper87, markmcclain20:21
openstacknow (3): mordred, lifeless, sdague20:21
openstackdunno (1): ttx20:21
ttxLooks like people are more comfortable tabling this for a couple months20:21
jeblairi think it would be good to see some engagement on the CI front -- both in supporting java infrastructure and some integration testing20:21
rhochmuthjeblair we are moving away from java20:21
jeblairthen that part isn't so important :)20:21
rhochmuthand monasca is already in the ci/cd systems20:21
jaypipesperhaps we might invite rhochmuth and ddieterly to the TC meeting on Monday in Tokyo and hold an in-person vote for Monasca?20:21
rhochmuthwe run unit tests20:21
rhochmuth...20:22
rhochmuthwhat are we waiting for20:22
*** topol has quit IRC20:22
rhochmuthnot sure what is actionable on my part20:22
dhellmannunit tests are good, but I'm not seeing any integration test jobs20:22
jeblairrhochmuth: but there are no integration tests, right?20:22
mordredrhochmuth: I think getting some devstack integration tests owuld be nice - especeially if you've got kafka stuff - that would actually likely be helpful for the oslo.messaging kafka folks to build on20:22
sdaguerhochmuth: right, integration tests seem kind of important20:22
ttxmaybe those who voted "mitaka" in the poll could detail what they would like to see in the coming months20:22
jaypipesrhochmuth: time. trust. patience.20:22
rhochmuthwe have an entire suite of tempest tests in a separate repo that we would merge20:22
jeblairprobably something with a keystone service catalog entry ought to have an integration test20:22
anteayajaypipes: well said20:23
flaper87I'd personally like to see more interactions with the rest of the community, perhaps better CI (integration tests)20:23
sdaguefull stack testing in some regard at least20:23
*** ayoung_ has quit IRC20:23
ttxPersonally I'd like to see if the OpenStack ways work for you -- it's one thing to be forced to use IRC, it's another to come to appreciate what it brings you20:23
dhellmannjeblair: ++20:23
jeblairrhochmuth: have a link to those tests or that repo?20:23
anteayattx agreed20:23
ttxit's perfectly fine to discover that it doesn't work for you20:24
flaper87I think nothing bad will happen in the next couple of months, if anything it's just some extra time to migrate more of the code to python, integrate with other parts of the ocmmunity and CI20:24
*** ayoung has quit IRC20:24
flaper87so, I believe waiting is just for the better20:24
flaper87other than that, I don't have anything against welcoming monasca in the big tent20:24
*** jprovazn has joined #openstack-meeting20:24
*** guest_____ has joined #openstack-meeting20:24
markmcclainright and I since there's not an immediate pressing working a bit wider with CI, meetings makes sense before adding into tent20:25
*** barker has joined #openstack-meeting20:25
ttxso it looks like it won't gather the required votes today anyway20:25
ttxand this should be tabled until Mitaka starts, when we'll reconsider Fuel as well20:25
*** xingchao has joined #openstack-meeting20:26
ttxanyone else wanting to detail what they expect from Monasca between now and then ?20:26
mordredso - it might be good for one person to write up a $something that summarizes the above thoughts for rhochmuth ?20:26
sdaguerhochmuth: do you feel like you have a handle on what's expected of your team?20:26
rhochmuthno, i do not know what you want20:26
rhochmuthmore irc meetings???20:27
rhochmuthmore community20:27
anteayarhochmuth: I think jaypipes made the point of patience20:27
dhellmannI think my concerns were included in those summaries: more meetings using tools the community can all use & integration test jobs20:27
rhochmuthdo all the project that you've accepted have 6 companies working on it20:27
markmcclain++20:27
jeblair* an integration test (likely based on devstack and tempest, using plugins)20:27
*** banix has joined #openstack-meeting20:27
jaypipesrhochmuth: nope, that doesn't have anything to do with this vote result.20:27
ttxrhochmuth: I'd like to feel that you're one of us. Not that you're forced to adopt our ways to pass a bar20:28
flaper87jeblair: ++20:28
lifelessso20:28
dhellmannrhochmuth: the criteria we use to evaluate a project are listed at http://governance.openstack.org/reference/new-projects-requirements.html20:28
lifelesswe don't have integration tests as a requirement in the governance20:28
*** edleafe has quit IRC20:28
rhochmuthdo all other projects have integration tests20:28
*** mpaolino has joined #openstack-meeting20:28
dhellmannlifeless: The project has core reviewers and adopts a test-driven gate in the OpenStack infrastructure for changes20:28
lifelesshave we uncovered another thing we should be requiring?20:28
rhochmuthanyway we have a suite of integration tests in a repo20:28
jeblairlifeless: it's true, however, this project, at the point it is in its development, should have one.20:28
lifelessdhellmann: yes, which it has20:28
jeblairlifeless: if it were a less mature project, i would not ask it to develop one first20:29
lifelessjeblair: so we wouldn't have asked for it if they'd become one-of-us earlier ?. I am confused.20:29
sdaguerhochmuth: right, but most projects run those on every commit20:29
rhochmuthhttps://github.com/hpcloud-mon/monasca-tempest20:29
sdaguedefinitely all the projects we consider mature20:29
jaypipeswhy is it so hard to ask for just time to pass so that we can see the new community processes/meetings/collaboration is not just all for show?20:29
dhellmannrhochmuth: are those in gerrit, too?20:30
rhochmuthno, we have not merged them with gerrit20:30
sdaguejaypipes: well I think that letting time pass was agreed20:30
dhellmannjaypipes: yeah, that's my bigger concern20:30
anteayajaypipes: I am really glad you have that position20:30
sdagueI think the question is on other more concrete things20:30
dhellmannrhochmuth: are there other parts of monasca not in gerrit?20:30
anteayajaypipes: you also mentioned trust earlier as well20:30
jeblairlifeless: i think for a project to get to this level of maturity and not have an uptream integration test shows that it was not developed as an openstack project.  this is something specific to this project that needs to be remedied.20:30
fungii have to concur, it seems odd for a "one of us" project to prefer to start developing their tests in a github repo20:30
sdaguewhich did get brought up, the point of critical bits not in gerrit is good20:30
flaper87jaypipes: dunno (?)20:30
rhochmuthall the source is in gerrit20:30
*** doug-fis_ has joined #openstack-meeting20:30
ttxOK, we really need to write a more explicit response here20:31
* flaper87 connection is lagging like crazy and he's not even on a plane20:31
rhochmuththere are a bunch of repos for Ansible and side project not part of the core submission20:31
ttxany volunteer to draft that over the coming week ?20:31
*** mpaolino has quit IRC20:31
dhellmannrhochmuth: why aren't those part of the project?20:31
flaper87I'm happy to collect it and report back to the review20:31
dhellmannI'll work with flaper8720:31
* flaper87 read ttx's mind20:31
jaypipesflaper87: ty.20:31
*** bobh has quit IRC20:31
*** xingchao has quit IRC20:31
*** mpaolino has joined #openstack-meeting20:31
flaper87dhellmann: danke!20:31
flaper87jaypipes: np20:31
rhochmutha tester developed the monasca tempest test and was unfamilier with next steps20:32
dhellmannand a late ++ to jeblair's comment20:32
ttxflaper87: awesome. Etherpad and -tc list should do20:32
dhellmannrhochmuth: ok. that does need to be addressed, though.20:32
rhochmuththe ansible is not part of gerrit, becuase it isn't really considered core20:32
ttxwe need to move on20:32
*** doug-fi__ has joined #openstack-meeting20:33
ttx#action flaper87 to draft a clearer response with TC expectations20:33
ttx#agreed Monasca application tabled until start of Mitaka cycle20:33
*** iben has joined #openstack-meeting20:33
ttx#topic Add team:danger-not-diverse tag20:34
*** openstack changes topic to "Add team:danger-not-diverse tag (Meeting topic: tc)"20:34
*** kencjohn_ has quit IRC20:34
ttx#link https://review.openstack.org/21872520:34
annegentlethanks flaper8720:34
*** raildo is now known as raildo-afk20:34
ttxjogo proposed a tag to describe project teams that are "dangerously" not diverse.20:34
flaper87annegentle: np :)20:34
*** doug-fish has quit IRC20:34
ttxI think that's a great data point to communicate out -- projects that rely on a single company or where only two companies are contributing are fragile20:34
annegentleI had a late "danger is judgemental" comment :)20:34
*** yamamoto has joined #openstack-meeting20:34
sdagueannegentle: I think judgemental is fine here20:35
ttxyeah, i think it's fine too20:35
sdaguebecause this is really not a state we want any project to be in20:35
ttxconsumers of the project should know that before they choose to invest in deliverables produced by that team20:35
ttxThere are fragile (or already dead) projects in the big tent today20:35
*** doug-fis_ has quit IRC20:35
dtroyera simple non-diverse would work too, but I agree the extra bit implied by danger is ok here20:35
sdaguepersonally I probably would have dropped the 2 orgs at 95% bit20:35
annegentlesdague: danger to whom? Might be a sign that the project should break up anyway? fragile might be better20:35
dhellmannI think it's fine to say "danger" but I'm less comfortable assuming that lack of diversity is associated with a lack of desire for diversity, as is implied by line 1420:35
sdagueannegentle: dangerous to adopters20:35
dhellmann(of draft 4)20:35
* jaypipes curious what benefit this explicit negative tag has versus just the absense of the diverse-affiliation tag20:36
*** rhochmuth has quit IRC20:36
ttxfragile-not-diverse ?20:36
annegentlesdague: ok20:36
dhellmannjaypipes: it identifies the other end of the spectrum20:36
ttxjaypipes: you may not have a divcerse affiliation, but still not be fragile20:36
dtroyerjaypipes: it's the red zone just before you run out of gas20:36
annegentleI think it's a valid measure20:36
jeblairdhellmann: i strongly endorse your objection.20:36
jaypipesdhellmann: by that token, should we add tags for "doesn't-assert-deprecation-policy"?20:36
*** mpaolino has quit IRC20:36
ttxjaypipes: well, that more binary20:37
dhellmannjaypipes: no, because that's a boolean. diversity is a float20:37
ttxdhellmann: ++20:37
*** doug-fi__ has quit IRC20:37
sdaguejaypipes: if you have a different set of labels to get 3 states here, those are welcomed20:37
sdaguebut this is a tristate, not a dual-state20:37
jaypipesdhellmann: I agree 100.0000028283 percent.20:37
jeblairjaypipes: and yes, i also wonder the same thing -- i thought when we added the 'diverse' tag that was sufficient.20:37
angdraugI thought tags were supposed to be boolean?20:38
jeblairsdague: what are the three states?20:38
ttxseriously, I think it's great that MagnetoDB gets the tag. It's pretty dead now that Mirantis seems to have pulled from it20:38
jaypipesangdraug: they were supposed to be, yes.20:38
ttxand if we had the tag before every consumer could have seen it coming20:38
sdaguediverse-affiliation, none, diversity-danger20:38
jaypipesangdraug: either you have the tag, or you don't.20:38
*** ekarlso has quit IRC20:38
*** isq_ has quit IRC20:38
*** nightfly has joined #openstack-meeting20:39
sdagueit is not possible for 1 project to have both tags, it is possible for a project to have neither tag20:39
*** jkeen has quit IRC20:39
angdraugwhy then should diversity be any special? either the project is diverse, or it's not, why add a third state of "kinda diverse but kinda not enough"?20:39
sdagueso they are 2 binary tags, that together represent a tristate20:39
jeblairsdague: i'm not sure "low, medium, high" diversity helps me decide that something is well supported as much as "almost none, some" diversity.20:39
jaypipesthis isn't quite like the ops "tags" stuff, where you have a value part like "packaged:76%" or something, but this is less than ideal, IMHO... more confusing than anything.20:39
*** yamamoto has quit IRC20:40
ttxthose tags answer different questions.20:40
*** vgridnev has quit IRC20:40
ttxOne says the project is produced by a diverse community20:40
*** jprovazn has quit IRC20:40
ttx$The other says the projecvt is at risk20:40
sdaguehonestly, I think this is hugely important to be explicit about the fact that we have a set of really healthy projects that clearly can handle one or more big players falling out20:40
*** rbrndt has left #openstack-meeting20:40
angdraugttx: what's the value of the first one if not to mitigate the risk represented by the second one?20:40
jeblairsdague: me too, i consider that the diversity tag.20:40
sdagueand on the other end a set of projects which are very clearly at the whim of a single orgs budge cycle20:40
ttxEvery project that the tag is applied to is in danger of not being there tomorrow20:40
*** oanufriev1 has joined #openstack-meeting20:40
jaypipesttx: I disagree. One says the project is diverse or a project is not diverse. The other doesn't say something positive at all.20:41
mordredI think it's a trinary state which our tags don't show20:41
jeblairsdague: i guess i don't see the middle road as being not in danger.  i think anything without the current diversity tag is in danger.20:41
jaypipesttx: couldn't you say the same thing about any project without the diverse-affiliation tag?20:41
mordredthe diversity tag has a much different threshold20:41
*** achanda has joined #openstack-meeting20:41
jeblairi think any project without the diversity tag is unhealthy.  i certainly thought that when infra lost it.20:42
ttxjaypipes: I think they are not indanger. They are not produced by a diverse community, but they shuold survive a given company pulling out20:42
angdraugjeblair: ++20:42
sdaguejeblair: infra is not going to collapse if a single org has a priority shift. cue will20:42
sdagueas a for instance20:42
sdaguethat's a really concrete one20:42
*** alexsyip has quit IRC20:42
jeblairsdague: i'm worried about it.20:42
ttxjeblair: unhealthy doesn't mean in immediate danger of dying.20:42
ttxwhich is what I mean by answering two different questions20:42
flaper87jeblair: ++20:42
mordredperhaps if the tag was named non-negatively20:42
ttxsdague: ++20:42
annegentlestill points to "danger" and "fragile" as not really describing this20:43
angdraugFuel is in no immediate danger of dying even though it's definitely a Mirantis monoculture20:43
mordredso that the meaning could be captured - but not with the negative voice?20:43
sdaguejeblair: I agree that it's a concern, but it won't literally cease to exist if one of the orgs changes priorities in their annual budget review20:43
jeblairttx: i think i'm starting to see where you and sdague are coming from.  i think this may be a matter of audience.20:43
ttxangdraug: Fuel can die is a single person decides it. That is what I call "danger";20:43
flaper87mordred: ++20:43
jaypipesangdraug: I think what folks are saying is that Fuel *is* in danger of dying if Mirantis goes belly up, simply because it is not a diverse affiliation.20:43
sdaguewe have a set of projects that will completely cease to exist if an exec at one org decides to move people around20:43
jeblairas a user, or even general observer of the project, i think my primary concern is whether a project is healthy (diverse) or not20:43
mordredjaypipes: yah. and we'd like for that not to be the case, beause fuel is pretty cool - as is cue20:44
jeblairsdague, ttx: i agree there is a further degree that you have articulated here, but what audience is that of use to?20:44
flaper87while I understand the points behind flags being booleans, I also see how, in this specific case, it's useful to have it describing something else other than yes/no20:44
mordredjaypipes: so I tihnk what I'd like to communicate is "opportunity for other people to make a difference by getting involved"20:44
sdaguejeblair: operators deciding to deploy a component20:44
ttxangdraug: MagnetoDB is in the bug tent, has the tag, was removed from Mirantis priorities apparently and is now a zombie project20:44
jeblairsdague, ttx: users should already have panicked based on not having diverse20:44
sdagueand thus taking on support20:44
*** raildo-afk is now known as raildo20:44
*** tongli has quit IRC20:44
sdaguethis is actually a question that gets asked20:44
angdrauggiven the amount of activity around Fuel and number of people using it, it's very likely that all that will be picked up by current users of Fuel even if Mirantis pulls out of it20:44
jeblairsdague: right, i guess i think that's the diverse tag.20:45
jaypipesmordred: well, branding a project with a negative "diverse-affiliation-danger" tag is unlikely to inventivize a project. negative incentives rarely work in the way that positive ones do, IME.20:45
flaper87mordred: that's exactly what I "not so diverse but could be" state would mean to me20:45
flaper87and I think we should have a way to express that20:45
ttxjeblair: I still think the projects the tag applies to are in more... immediate danger.20:45
mordredjaypipes: right. that's why I'm syaing we should hav ea better name20:45
mordredjaypipes: or whatnot20:45
jeblairsdague: are there really people willing to deploy something "somewhat non-diverse but not dangerously so"?20:45
sdaguejeblair: yes, I think so20:45
flaper87jeblair: I really hope there are20:45
mordredjaypipes: just I think the piece of information encoded is potentially useful in a positive way - I agree the name is incendiary20:45
flaper87otherwise there's close to no chance for new projects to evolve and improve20:45
flaper87i.e Zaqar20:45
sdaguejeblair: because the option is "implement it yourself"20:45
flaper87or Cue20:45
*** Brian has joined #openstack-meeting20:46
markmcclainteam:really-needs-contributors20:46
jaypipesheh20:46
ttxOK, looks like we can iterate a few times on the patch20:46
ttxWe ahve a few other items to cover today20:46
*** Brian is now known as Guest166420:46
dhellmannlooking at http://stackalytics.com/?project_type=all&module=monasca-group monasca would get this tag20:46
sdaguedhellmann: yep20:46
mordredit took sometihng like 3 years before infra had humans working on it who weren't on my team ... and during that time we _constantly_ sounded the danger gong20:46
jaypipesyeah, I'm not 100% opposed to this tag or anything... just would like it to be positive rather than negative if possible.20:46
dhellmannso they have 6 companies, but HP is doing 90% of the review work20:46
*** oanufriev1 has left #openstack-meeting20:46
sdaguein the old days we'd have rejected all these projects, in the new days I think it's fine to have them in, but just mark them as being really seriously in danger20:47
jeblairi'm okay with the negative but still wrapping my head around its utility.  :)20:47
ttxsdague: ++20:47
sdagueand I think negative connotation is good here, as it makes people want to make it a priority to get out of that zone20:47
jeblairsdague: oh!20:47
ttxOK, let's move on, please comment on the review and talk to jogo directly20:47
sdaguewhich hopefully leads them down a path to an actual diverse project20:47
jaypipessdague: we'll agree to disagree on that motivator :)20:47
markmcclainjeblair: I look at as grading risk severity20:47
jeblairsdague: i think my biggest disconnect is that this makes "lack of diversity" seem less negative than i think it is.20:47
mordredjaypipes: I disagree about agreeing20:47
jaypipeslol20:48
ttx#topic OpenStack programming languages resolution20:48
*** openstack changes topic to "OpenStack programming languages resolution (Meeting topic: tc)"20:48
jogottx: just leave comments on the review, I am more async these days20:48
ttx#link https://review.openstack.org/21771020:48
*** derekh_afk has quit IRC20:48
ttxWe discussed this one last week.20:48
ttxI tweaked the initial proposal to remove language that sounded preemptively negative to language addition ("silo", "convenience"...)20:48
mordredjogo: are you more pinsync?20:48
*** salv-orlando has joined #openstack-meeting20:48
jaypipesjogo: don't you mean "pinsync"?20:48
ttxTo cover annegentle's concerns I expanded on the "exception" clause, and to cover jeblair's concerns I removed the silly 2/3 vote clause20:48
annegentleheh you guys20:48
*** browne has left #openstack-meeting20:48
ttxI think it's pretty neutral now: it opens the door and says "there are benefits and drawbacks, we'll consider it when it comes"20:48
ttxI see annegentle left a few comments earlier today20:49
jogo:)20:49
jeblairttx: the requirement to use common sense seems daunting.20:49
jeblair;)20:49
flaper87I'm good with that resolution, I'm just waiting on the next version w/ fixes to annegentle's concerns20:49
annegentlettx: what about the other side's benefits and drawbacks, each time I review this I keep thinking there's soo much overhead to being an OpenStack project, we should also document expectations for ci/docs/test/etc20:49
mordredannegentle: I think I want SDKs to submit if they want to submit - I'm not sure this resolution to me is about incentivizing or not incentivzing people to want to be here20:49
sdaguettx: so I guess lines 25-28 seem to beg "where is the list of current supported languages"20:49
ttxI'm fine with Anne's language suggestion for line 2820:50
*** jecarey has joined #openstack-meeting20:50
ttxsdague: it's higher in the resolution20:50
mordredannegentle: but rather, for people who do want to be here, providing clarity on how we're going to think about that - and to let them know we welcome the theory but that there is work20:50
sdaguettx: so it should be probably called out directly20:50
mordredannegentle: (I agree, for a lot of them I bet they would not find it valuable and I do not expect to see them beating down our door)20:50
*** Guest1664 has quit IRC20:50
annegentleit's completely insane to keep up seven languages for docs, ci, test, translation (believe me I know the SDK work_20:50
sdagueThe currently supported languages in OpenStack are: bash, python, javascript20:50
*** achanda has quit IRC20:51
ttxOK, I can make a new patchset with that and Anne's new wording20:51
ttxsdague: could you please add it as a review comment so that I don't forget ?20:51
sdagueyep20:51
annegentlemordred: right, so why would we encourage sdks to submit, only to unfurl a list of requirements a mile long? (I'm exaggerating, sure)20:51
flaper87if we add a list of programming languages, we gotta make sure we keep it updated20:51
ttxannegentle: maybe cross that bridge when we get there ?20:51
annegentleand, how do we still encourage people to make SDKs for OpenStack20:51
*** balajiiyer has quit IRC20:52
flaper87I'm fined with either adding it or not, really.20:52
ttxflaper87: we'll probably have to have a reference document, this is a (dated) resolution20:52
EmilienMsdague: PuppetOpenStack + Infra modules are in Puppet+ruby20:52
ttx#action ttx to make another patchset20:52
mordredannegentle: I'm not sure we're doing that20:52
ttxEmilienM: they have an exception under the resolution20:52
sdaguettx: the exceptions should be called out explicitly as well then20:53
mordredannegentle: and we can't even get people to work on the existing python one inside of openstack - so I'm not even thinking about trying to get people to work on _other_ sdks in openstack20:53
*** ayoung has joined #openstack-meeting20:53
annegentlemordred: right20:53
*** ayoung_ has joined #openstack-meeting20:53
flaper87EmilienM: the resolution is about services specifically20:53
annegentleflaper87: I think it should be, but is the language that way now?20:53
flaper87mordred: true that20:53
ttxsdague: I don't think a resolution needs to call all the rules out. I added "let's use common sense", which means, we'll discuss it when it comes20:53
*** dwalleck has quit IRC20:53
*** vgridnev has joined #openstack-meeting20:54
*** dneary has quit IRC20:54
ttxanyway, no time so let's move on20:54
edleafe-ttx: which also means that this document doesn't provide much information20:54
*** jwang_ has joined #openstack-meeting20:54
*** Akis_ has joined #openstack-meeting20:54
flaper87annegentle: that's how I read it or at least I think I did :P20:54
flaper87annegentle: u messing with my weak brain?20:54
flaper87:D20:54
ttxedleafe-: sure, it's just saying "bring it on, we'll discuss it", which is better than "meh, no idea if it's ok"20:54
*** VW__ has joined #openstack-meeting20:54
ttx#topic Applies naming guidelines to service object20:54
*** openstack changes topic to "Applies naming guidelines to service object (Meeting topic: tc)"20:54
ttx#link https://review.openstack.org/20167020:54
sdaguettx: I guess, except I think we don't all agree on the costs vs. benefits here. common sense assumes we're all on the same page there20:54
annegentleflaper87: never :)20:54
*** dwalleck has joined #openstack-meeting20:54
*** VanL_ has joined #openstack-meeting20:54
*** achanda has joined #openstack-meeting20:54
*** shihanzhang has joined #openstack-meeting20:55
ttxThis one seems ready20:55
ttxI'll approve it now20:55
* flaper87 agrees20:55
flaper87ready, ship it. BAM!20:55
*** glauco has quit IRC20:55
annegentlewoo!20:55
ttx#topic Creates labs project20:55
*** openstack changes topic to "Creates labs project (Meeting topic: tc)"20:55
ttx#link https://review.openstack.org/21834620:55
ttxI added this one to the agenda because it raises an interesting question20:55
ttxWe said repo additions are fine as long as the PTL wants it20:55
*** glauco has joined #openstack-meeting20:55
edleafe-sdague: exactly20:55
ttxBut usage of generic names in a single namespace (like "openstack/labs") stretches it20:55
*** pm90__ has joined #openstack-meeting20:55
ttxI have two concerns: generic names can be a bit misleading: what if ceilometer wanted to get "openstack/documentation" for example ?20:55
annegentleyeah we have had multiple discussions :)20:55
* flaper87 agrees w/ ttx's comment20:56
*** raildo is now known as raildo-afk20:56
ttxthe other is the potential consequence: the risk of a repo rename when we realize that was not such a good idea20:56
annegentleand I personally am not a fan of labs20:56
annegentleso he has brought it back to the -docs mailing list for more naming ideas20:56
*** cdelatte has quit IRC20:56
*** patrickeast has quit IRC20:56
dhellmannthese are labs for use during training exercises?20:56
jeblairttx: i think bringing this for discussion was a good call, thank you.20:56
*** VanL has quit IRC20:57
*** VW_ has quit IRC20:57
*** patrickeast has joined #openstack-meeting20:57
anteayaI think jogo makes a good point20:57
*** Akis__ has quit IRC20:57
*** jwang has quit IRC20:57
*** pm90___ has joined #openstack-meeting20:57
*** ekarlso has joined #openstack-meeting20:57
*** ekarlso has quit IRC20:57
*** ekarlso has joined #openstack-meeting20:57
*** bswartz has quit IRC20:57
annegentledhellmann: these are labs that follow the install guide so that trainers can use them for training classes at say user group meetings20:57
*** shz has quit IRC20:57
dhellmannannegentle: ok. I suggest that the name include some form of "training" then, for enhanced clarity. :-)20:58
*** akiskourtis has joined #openstack-meeting20:58
sdagueannegentle: so what's going to be in this repo? is it docs, or is it code like vagrant scripts?20:58
*** SheenaG has joined #openstack-meeting20:58
annegentledhellmann: also what I wanted :)20:58
*** neelashah has joined #openstack-meeting20:58
anteayaprovide automated way of deploying a multi node OpenStack cluster20:58
annegentlesdague: it is scripts20:58
ttxannegentle: ok, so other names will be suggested ?20:58
anteayaautomated20:58
dhellmannsdague: this seems to be related: http://specs.openstack.org/openstack/docs-specs/specs/liberty/openstacklabs.html20:58
annegentlettx: already were :)20:58
*** geoffarnold has joined #openstack-meeting20:58
flaper87annegentle: cool20:58
annegentledhellmann: sdague: yes that's their blueprint20:58
*** VanL_ has quit IRC20:58
*** pm90_ has quit IRC20:58
*** jungleboyj has joined #openstack-meeting20:59
ttxok, cool, I think we are good then. i'll freeze that one until we are ok it's less of a rename wanabee20:59
sdagueannegentle: that doesn't have a lot of detail20:59
jeblairthis seems really similar to devstack's reason for existing20:59
sdagueyeh, or yet another installer.20:59
ttx#topic Open discussion20:59
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:59
ttxI skipped the workgroup reports, comms did a post last week20:59
flaper87#link http://www.openstack.org/blog/2015/09/technical-committee-highlights-september-2-2015/20:59
ttxand cross-project-track is still forming up21:00
*** pm90__ has quit IRC21:00
ttxand.. we are out of time21:00
annegentlesdague: agreed21:00
*** gouthamr has quit IRC21:00
flaper87o/21:00
EmilienMttx: as usual :P21:00
annegentletweet it!21:00
annegentle:)21:00
ttxSorry that was a bit rushed, but those were all valuable and important discussions21:00
*** dflorea has quit IRC21:00
dhellmann++21:00
ttxI should have seen they would overflow and schedule a little less21:00
ttxI guess I was fooled with how smooth difficult discussions have gone lately21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Sep  8 21:01:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-08-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-08-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-08-20.01.log.html21:01
dhellmannthanks, everyone21:01
*** Akis_ has quit IRC21:01
ttxjohnthetubaguy: floor is yours21:01
johnthetubaguy#startmeeting crossproject21:01
openstackMeeting started Tue Sep  8 21:01:38 2015 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: crossproject)"21:01
openstackThe meeting name has been set to 'crossproject'21:01
johnthetubaguycourtesy ping for david-lyle flaper87 dims dtroyer johnthetubaguy rakhmerov21:01
johnthetubaguycourtesy ping for smelikyan morganfainberg adrian_otto bswartz slagle21:01
johnthetubaguycourtesy ping for adrian_otto sdake kiall jeblair thinrichs stevebaker j^221:01
johnthetubaguycourtesy ping for docaedo mestery Daisy zigo Piet notmyname ttx mtreinish21:01
johnthetubaguycourtesy ping for isviridov gordc SlickNik cloudnull catherineD loquacities21:01
johnthetubaguycourtesy ping for thingee hyakuhei redrobot dirk TravT vipul emilienm21:01
johnthetubaguycourtesy ping for SergeyLukjanov devananda boris-42 nikhil_k21:01
*** glauco_ has joined #openstack-meeting21:01
*** _amrith_ is now known as amrith21:01
notmynamehere21:01
*** glauco has quit IRC21:01
lifelessALL THE PINGS21:01
gordco/21:01
EmilienMo/21:01
johnthetubaguy#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda21:01
SheenaGo/21:01
mesteryo/21:01
lifelessjohnthetubaguy: you missed me :)21:02
elmikoo/21:02
stevebaker\o21:02
edleafe-o/21:02
Piethere21:02
bknudsonpeople don't have alarms?21:02
dims__o/21:02
johnthetubaguylifeless: the tool missed you off, odd21:02
* rockyg waves from the back21:02
EmilienMlifeless: we always miss you, you must be absent from previous logs ;-)21:02
*** harshs has joined #openstack-meeting21:02
lifelessEmilienM: nope, I've been here many times21:02
bknudsonwe need an infra job for this.21:02
*** banix has quit IRC21:02
docaedoo/21:02
jungleboyjo/21:02
sdakeo/21:02
bknudsonbot should handle it21:02
*** dflorea has joined #openstack-meeting21:03
*** kencjohn_ has joined #openstack-meeting21:03
mordredbknudson: could we write an infra job that can write the infra jobs we need?21:03
jokke_o/21:03
johnthetubaguyI use a script, so its almost there21:03
johnthetubaguywell use the script21:03
johnthetubaguyanyways21:03
johnthetubaguy#topic Review past action items21:03
*** openstack changes topic to "Review past action items (Meeting topic: crossproject)"21:03
johnthetubaguydims to ping some nova cores about https://review.openstack.org/#/c/205931/ (change now approved)21:03
philipwo/o21:03
johnthetubaguywell merged actually21:04
*** dflorea has quit IRC21:04
johnthetubaguyshamail barrett1 to share the link and people will let us know if they disagree with the current "prioritized" user story list.21:04
johnthetubaguynot sure if I saw that on the ML?21:04
*** harshs has left #openstack-meeting21:04
johnthetubaguybut I did see #link http://specs.openstack.org/openstack/openstack-user-stories/21:04
johnthetubaguythe chair rotation list is full, so thats all good21:05
* jroll a couple minutes late, oops21:05
johnthetubaguy#topic Team announcements (horizontal, vertical, diagonal)21:05
*** openstack changes topic to "Team announcements (horizontal, vertical, diagonal) (Meeting topic: crossproject)"21:05
ttxOn the release management front21:05
ttxWe tagged liberty-3 last week, we are now in:21:05
ttx* FeatureFreeze (features, new config options, database schema changes need exception to merge)21:05
*** dwalleck has quit IRC21:05
bknudsonyeah!21:05
ttx* DepFreeze (addition of new dependencies or 3rd-party dependency bumps need exception to merge)21:05
ttx* StringFreeze (resist changing strings to facilitate the work of docs and I18N)21:05
jungleboyjYay!21:05
ttxWe also need to cut liberty release branches ("stable/liberty") for libraries asap21:06
*** rossella_s has quit IRC21:06
ttxThat means you should make releases for recent client features if you haven't already... and we should cut the branches from there21:06
bknudsoncap em!21:06
jokke_\\o \o/ o// o/721:06
*** banix has joined #openstack-meeting21:06
*** rossella_s has joined #openstack-meeting21:06
ttxThat doesn't mean it's the last liberty release for clients, you can still do bugfix releases if needed21:06
ttxBut all features should be there21:06
ttxdhellmann sent a reminder:21:06
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-September/073686.html21:06
johnthetubaguyttx: do you need the libs to help with the stable branch cutting, or are you just going to use the last tag?21:06
stevebakerI haven't seen a novaclient release for a while21:06
ttxjohnthetubaguy: I'll be using the last tag21:06
zigoo/21:07
johnthetubaguyttx: cool21:07
ttxbut that means you better do a tag if you want the current features in master to be used in the liberty line of the client21:07
*** changbl has quit IRC21:07
*** harshs has joined #openstack-meeting21:07
ttxotherwise that will make for a lot of backporting and exception fun21:07
johnthetubaguyttx +121:07
*** henrynash has joined #openstack-meeting21:07
jokke_ttx: when are you going to cut the branches? Tomorrow, by end of the week, something else?21:07
ttxsee that thread I just linked to, dhellmann explained in much more eloquent wording than me21:08
ttxjokke_: end of week at this stage21:08
jokke_thnx21:08
ttxwe are a bit behind schedule21:08
jokke_we try to get patch rel of glanceclient out before that then to avoid ton of backporting21:08
zigoIf possible, it'd be nice to have oslo.FOO libs completely frozen a bit earlier than last cycle.21:08
zigoOtherwise, it's quite difficult to do enough testing of packages (ie: too much update work to be done...)21:09
ttxzigo: yeah, as I said we are a bit behind21:09
dims__zigo: oslo.FOO with latest g-r is out this morning21:09
*** ayoung has quit IRC21:09
ttxoslo should be done now21:09
*** ayoung_ has quit IRC21:09
ttxanyway, that's all I had21:09
ttxquestions?21:09
mtreinishI actually have something for this topic this week21:10
*** ivasev has quit IRC21:10
ttxmtreinish: ooooh21:10
fungithe vmt coverage criteria are basically solidified after our -dev ml thread so i'll follow up with the governance addition in the next day or so21:10
johnthetubaguymtreinish: sounds good21:10
mtreinishthe tempest plugin interface is all ready to go now21:10
*** maishsk has quit IRC21:10
*** aysyd has quit IRC21:10
mesterymtreinish: Coolio!21:10
*** pm90___ has quit IRC21:10
mtreinishmanila started a gating job using tests via the plugin interface last week21:10
mtreinishand I pushed a tag to tempest to signify it's stability21:10
bknudsondo you want all projects using plugins?21:11
mtreinishso project can go and add external test suites and have them act like part of tempest21:11
bknudsone.g., keystone21:11
mtreinishbknudson: keystone support is in the tempest tree21:11
gordcmtreinish: you have review handy just for reference?21:11
mtreinishI'd rather see tests contributed to tempest for that21:11
mtreinishgordc: for the manila plugin usage?21:11
gordcmtreinish: yep21:11
mtreinishgordc: sure one sec21:12
mtreinishgordc: https://review.openstack.org/20195521:12
*** baoli has quit IRC21:12
mtreinishgordc: also: http://docs.openstack.org/developer/tempest/plugin.html21:12
gordcmtreinish: awesome. thanks very much!21:12
johnthetubaguy#link http://docs.openstack.org/developer/tempest/plugin.html21:12
*** tiswanso has quit IRC21:13
*** vgridnev has quit IRC21:13
johnthetubaguycool, any more for any more?21:13
mtreinishbknudson: fwiw, I have the list of what's supposed to be in the tempest tree here: https://wiki.openstack.org/wiki/QA/Tempest-test-removal#Tempest_Scope21:13
bknudsonso keystoneclient ?21:13
mtreinishbknudson: keystone client has it's own functional testing using tempest-lib already21:14
mtreinishtempest doesn't use the python-*clients21:14
stevebakermtreinish: do you see out-of-tree defcore tests being a thing?21:14
*** nadya has joined #openstack-meeting21:14
mtreinishstevebaker: the vision I had was things that were in defcore would be in the tempest tree, and we'd adjust the scope to match as things were added21:14
stevebakerok21:15
*** maishsk has joined #openstack-meeting21:15
mtreinishbut if we end up hitting the same scaling problems because defcore tries to tackle too many things (like we once did in tempest) then the plugin interface gives us a good crutch21:15
*** VanL has joined #openstack-meeting21:16
rockygthanks, mtreinish!  Can I invite you to give your vision to a defcore meeting?21:16
*** sdake_ has joined #openstack-meeting21:16
johnthetubaguyOK, lets move on21:17
johnthetubaguy#topic Base feature deprecation policy21:17
*** openstack changes topic to "Base feature deprecation policy (Meeting topic: crossproject)"21:17
mtreinishrockyg: sure you can invite me, but I'm not sure I'll be able to make it :)21:17
johnthetubaguy#link http://lists.openstack.org/pipermail/openstack-dev/2015-September/073576.html21:17
ttxI sent an email about our base feature deprecation policy last week21:17
ttxlink above21:17
ttxThe goal was to check if the proposed base policy was matching what was generally done in the field21:17
ttxI had a few answers, but far from the whole spectrum21:17
ttxThe current proposal says: "a feature deprecated during the M development cycle should21:17
ttxstill appear in the M and N releases and cannot be removed before the beginning of the O development cycle."21:17
ttxThat is what we call "a minimum of n+2 deprecation"21:18
ttxSome said we should do a minimum of n+1 instead.21:18
ttxSome said features should be n+2, but config options should be n+1 (as long as they don't remove a feature)21:18
ttxWhat would be acceptable ? What do you think you are currently enforcing in your projects, if anything ?21:18
bknudsonI could deprecate something today and remove it in a month.21:18
bknudsonif we went with n+121:18
johnthetubaguyI liked the points sdague was making on that thread21:19
jokke_.21:19
jokke_0321:19
jokke_.321:19
jungleboyjIn Cinder we generally shoot for n+1.  Doesn't always happen though.  We do at least n+121:19
jokke_sorry21:19
johnthetubaguyfor continues deployers, you kinda want a minimum time frame to some extent21:19
ttxbknudson: yeah, which is why the minimum propsoed would be n+221:19
*** nadya has quit IRC21:19
jokke_how about stating it full cycle, more like a calendar year?21:20
bknudsonn+2 makes more sense. slow but steady wins the race.21:20
ttxjohnthetubaguy: so n+1 with a minimum of 3 months, or something21:20
*** sdake has quit IRC21:20
johnthetubaguyttx: yes, although the simplicity of n+2 is quite nice, it feels a bit long as a baseline21:20
ttxjokke_: so one aspect of it is that to know that a feature is deprecated you need to experience it through one "release"21:21
ttxat least21:21
*** VanL has quit IRC21:21
johnthetubaguycertainly Nova is generally doing n+1 as a minimum, but when we are unsure/worried, we wait much longer, but thats not really a good policy statement21:21
ttxwe had unwritten common rules in the past, but they were so unwritten that everyone interpreted them differently :)21:21
ttxthe policy would be a minimum guarantee21:22
ttxIt's also fine is some projects are too young to follow it21:22
jungleboyjjohnthetubaguy: That sounds like our's.  :-)21:22
notmynameswift's policy is "don't break clients and operators must be able to upgrade with no cluster downtime)"21:22
ttxnotmyname: but would you remove a feature or a config option without marking it deprecated for some time ?21:23
fungithough also a good rule of thumb is that when projects are too young to follow normal deprecation, they should stick with 0.x.x version numbers21:23
*** doug-fish has joined #openstack-meeting21:23
*** bswartz has joined #openstack-meeting21:23
fungi(same as for inability to make guarantees on backward compatibility)21:23
ttxfungi: we may be able to enforce that at some point (when all the >=1.0.0 projects happen to follow the minimum rule)21:24
fungiyep, here's hoping the current crop of projects are already mature!21:24
johnthetubaguyttx: just for clarity, +1 your config statement, certainly Nova tried to ensure we don't force any config changes when doing an upgrade, assuming you dealt with all the deprecation messages in your logs from last time first, i.e. n+1 deprecation timeframe21:24
ttxnotmyname: "don't break clients" is a bit vague. Is removing a feature they depend on "breaking" them ?21:24
*** doug-fish has quit IRC21:24
fungialso, all clients? only clients you know exist? only clients developed in cooperation with the swift dev team?21:25
jokke_I'd say at least with config options, you should be able to upgrade to next version without breaking anything ... what I mean is that if config option changes you should be able to upgrade your running code first and after that if you don't need roll back you can go and upgrage your configs21:25
*** doug-fish has joined #openstack-meeting21:25
notmynamettx: matters most with operators. removing features breaks clients unless you bump the API version. for ops, removing a feature (normally one that's controlled by a config var) means that the new code must accept the old config file and still work. and document it extensively in release notes21:25
notmynamefungi: all clients. ie don't remove stuff from the api (or change existing functionality) without bumping the api version21:26
fungimad props for api versioning and stability21:26
*** dflorea has joined #openstack-meeting21:26
jokke_regarding that topic I'd like to hear wider opinion? How about defaults and how you deprecate them?21:27
ttxnotmyname: I guess the question becomes.. when you bump the API version, do you still support the previous API version ?21:27
*** mattgriffin has quit IRC21:27
*** VanL has joined #openstack-meeting21:27
notmynamettx: yes21:27
*** IanGovett has quit IRC21:27
bknudsonhow long would we need to continue to support keystoneclient 1.x if we released a 2.x?21:27
ttxnotmyname: and for how long ?21:27
clarkbso in theory grenade enforces that N -> N+1 work without config or api changes as long as we have coverage for those things21:27
notmynamettx: but, it hasn't happened yet. ;-)21:27
bknudsonand what support would the library get?21:27
jokke_This as example we moved to default images api v2 in glanceclient shell when we moved to 1.0.021:27
notmynamettx: we're still "supporting" clients written six years ago on the same API21:28
clarkbbut it does not currently hve a way to enforce that in N -> N+221:28
clarkbmaybe we can start with what grenade makes easy and work from there as its implementable?21:28
ttxnotmyname: right, so this is about setting expectations. If you were to stop supporting them, would you be OK with a minimum of n+2 deprecation warning.21:28
ttxI bet you would, in that hypothetical case21:28
fungiin the spirit of "if it's not tested it's broken" don't claim we do things if we can't test that we really do them21:29
notmynamettx: that presupposes that we would stop supporting them. there's no intention of that today21:29
ttxso you can assert that you would follow the minimum deprecation policy21:29
*** doug-fish has quit IRC21:29
notmynamettx: sure. I guess21:29
notmynamettx: or "at least" ;-)21:30
ttxnotmyname: right. So the original version of this change had a "never-deprecate-anything" assertion21:30
fungi∞>=221:30
ttxthat was mostly meant for swift21:30
ttxbut people told me that was a bit unrealistic and that we should only do a minimum assertion (but projects can obviously promise to do much better)21:30
*** amitgandhinz has quit IRC21:31
*** dflorea has quit IRC21:31
*** VanL has quit IRC21:31
*** vgridnev has joined #openstack-meeting21:31
ttxi.e. the tag says "you can expect that if this project ever deprecates something, you would have some advance notice through a deprecation warning for n cycles"21:31
notmynamejokke_: to your point about config values, we've changed defaults before. always respect explicit values, and defaults should always work.21:31
ttx(at the very least)21:32
notmynamejokke_: and be explicit in docs + release notes about what they are21:32
*** balajiiyer has joined #openstack-meeting21:32
johnthetubaguynotmyname: same experience in Nova21:32
jokke_notmyname: yes ... that far I do fully agree21:32
notmynamettx: yup. that seems reasonable.21:32
ttxok, anyway, no point in discussing that here, please answer to the thread and describe what you think you can assert you would at least follow21:33
*** dkranz has quit IRC21:33
fungithough worth admitting that there are always going to be implicit defaults you don't realize exist until you find you want to change some behavior and add a configuration knob, so having some warning period before tweaking that is always helpful21:33
ttxI'll take the whole feedback and cook up something we can communicate to our users21:33
notmynamettx: seems that it's more important that there *is* a deprecation policy. not as much what the N is. ie as a deployer know that config keys are good for a while. whatever the policy states21:33
ttxnotmyname: agreed21:33
johnthetubaguyfungi: we did that for our periodic tasks, they were mixed up with 0 or -1 turning things off or using the default period, we gave that a cycle of warnings21:33
jokke_notmyname: we bumped major version to try to make clear that this happened and documented it. The big cry that was raised was that someone who doesn't bother to read release notes might break their shellscripts if upgrading21:34
*** pm90_ has joined #openstack-meeting21:34
ttxthey need to know project X is past the crazy initial period wheer you can break users and deployers every other day. That's all this tag is meant to communicate21:34
*** dflorea has joined #openstack-meeting21:34
*** IlyaG has joined #openstack-meeting21:35
ttxwhich is why we want most mature projects to be able to assert it21:35
notmynamejokke_: yeah. that's tough. IMO that comes down to the client side again, not the ops side21:35
johnthetubaguyttx: +1 thats very very valuable21:35
*** achanda has quit IRC21:35
fungipeople who don't read might break things. this too is a universal constant21:35
jokke_well this happened with tripleO gate where the new version was just pulled in and surprise v1 and v2 apis are not the same, but the big outcry did not come from there21:35
*** achanda has joined #openstack-meeting21:35
*** n00btube has left #openstack-meeting21:35
jungleboyjfungi: ++21:35
*** pm90__ has joined #openstack-meeting21:35
ttxwe don't have incubation or experimental mùarks anymore, this is a way to comunicate the same type of information21:35
*** kencjohn_ has quit IRC21:35
notmynamefungi: and through no fault of their own, especially when considering transitive dependencies21:35
ttxanywa, thanks for listening, and please contribute to that thread with your project data21:36
notmynamefungi: (sometimes)21:36
*** cloudtrainme has quit IRC21:36
johnthetubaguycool, good topic21:36
johnthetubaguy#topic Open Discussion21:36
*** openstack changes topic to "Open Discussion (Meeting topic: crossproject)"21:36
notmynamettx: this seems to be a great fit with the new release tags. (semver)21:36
lifelesshi21:36
lifelessI want to pimp two things21:36
* fungi is unsure whether mùarks is a typo or new vocabulary to be assimilated21:36
lifelesshttps://review.openstack.org/#/c/218070/21:36
lifelessand21:36
jokke_thanks for bringing that up ttx I think it's ever more important topic now with big tent and lots of variety21:36
lifelesshttps://review.openstack.org/#/c/204073/21:36
*** doug-fish has joined #openstack-meeting21:37
lifelessthe first is moving testr to be run in a separate environment to the code-under-test21:37
*** henrynash has quit IRC21:37
* ttx stops correcting typos after a given time of the day21:37
lifelessIt should be straight forward; I think I've spoken to enough folk about it - plus the big thread - but please do comment21:37
lifelessthe second is gus' privsep blueprint, strictly speaking its an oslo blueprint, but it will affect everyone as they adopt it21:38
lifelessits in very-very-very fine tuning mode now IMO21:38
lifelessI'd like to be able to get both approved before the summit, so that we don't need summit time on them21:38
*** devlaps has quit IRC21:38
fungior so that we can use summit time to get a headstart putting them into place21:39
*** pm90_ has quit IRC21:39
ttxlifeless: thx for pointing that one out, I definitely need to read that one (the rootwrap replacement)21:39
lifelessfungi: for folk that get time to do stuff at summit, sure :)21:39
fungirather than arguing over the color21:39
johnthetubaguyor colour21:39
* johnthetubaguy hides21:39
timrczaro, I've been thinking some about your last comment to https://review.openstack.org/#/c/205097/ -- I'm not sure we should do any special handling / inference based on the API documentation this is expected behavior... http://javadoc.jenkins-ci.org/hudson/model/Node.html21:39
*** banix has quit IRC21:40
timrczaro, So I think the client should interpret a "" node_name as being "master" but that should not be the responsibility of the gearman-worker plugin.21:40
fungitimrc: cross-project or wrong channel?21:40
timrcdoh21:40
timrcSorry lol21:40
*** claudiub has quit IRC21:40
johnthetubaguyso I have been pondering Nova's current application of String Freeze21:41
johnthetubaguyto cut a long story short, I think we were being a bit too strict21:41
*** ayoung has joined #openstack-meeting21:41
johnthetubaguyforcing bug fixes to remove log messages, as not to violate freeze21:41
johnthetubaguywhere really users would probably prefer an untranslated log instead of a hidden error21:42
*** ayoung_ has joined #openstack-meeting21:42
mordredjohnthetubaguy: ++21:42
mordredas a user, I would prefer that21:42
johnthetubaguyat least, thats what I have been wondering21:42
johnthetubaguyanyways, I attempted to write that up here:21:42
johnthetubaguyhttps://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#String_Freeze21:42
mordredto be fair - I am an english speaking user, so my feelings on untranslated strings are likely not to be trusted21:42
lifelesstranslated ops logs have never made sense to me21:42
johnthetubaguyBeen talking to the folks over on #openstack-l18n and they seem quite receptive to the idea21:42
lifelessclient logs, different thing21:42
*** cloudtrainme has joined #openstack-meeting21:43
johnthetubaguymordred: I went through exactly the same thought process21:43
fungii would have interpreted the spirit of the freeze as "don't invalidate the work already completed by translators if you can help it" but adding to the pile seems fine21:43
johnthetubaguyfungi: yeah, thats basically what I put in that wiki page21:43
ttxjohnthetubaguy: adding strings is much less evil to translators to modifying one.21:43
ttxthan*21:43
rockygBetter a foreign symbol error/warning than silent fail.  ++ johnthetubaguy21:43
*** vgridnev has quit IRC21:44
*** achanda_ has joined #openstack-meeting21:44
clarkbbut if you do modify them do not change the interpolation stuff21:44
ttxmodifying an existing one they may have already translated is evil because it throws away translation work21:44
fungiyeah, they're unlikely to hit 100.00000% translated so a few added strings during the freeze ought not be harmful21:44
*** achanda has quit IRC21:44
johnthetubaguyttx: yes, I hadn't made the connection before talking with them today, for some reason, but I totally get that now21:44
ttxadding one is just adding another line to their work pile21:44
johnthetubaguyfungi: +121:44
ttxit's not evil unless you are one week before release21:44
johnthetubaguyttx: yeah, totally get that *now* I sat down and thought about it21:44
johnthetubaguyso we have been interpreting things a bit too literally, just wanted to share that incase others were doing something similar21:45
bknudsonthe guidelines https://wiki.openstack.org/wiki/StringFreeze aren't correct?21:45
*** cloudtrainme has quit IRC21:46
bknudson"String freeze means that we cannot add new strings"21:46
bknudsonthe wiki seems to be the opposite of what we discussed here.21:46
*** JRobinson__ has joined #openstack-meeting21:46
*** Brian has joined #openstack-meeting21:46
fungiyeah, i concur21:46
*** Brian is now known as Guest7057121:47
johnthetubaguybknudson: yeah, thats the old rules we were applying, and I noticed they seemed a bit crazy21:47
*** darrenc_ is now known as darrenc21:47
johnthetubaguyso should I update https://wiki.openstack.org/wiki/StringFreeze to reflect what we said above21:47
* ttx checks wiki21:47
fungian earlier version of that wiki said "proposed changes containing modifications in user-facing strings"21:48
fungibisecting now to see when/why that changed21:48
johnthetubaguywould that update look a bit like this (ideally with many less words): https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#String_Freeze21:48
ttxoh, that was "improved" a lot since I last touched it21:48
johnthetubaguyfungi: I guess we called logs user facing at some point21:48
ttxjohnthetubaguy: feel free to come to something more sensible with the I18n/Docs teams. All this is to facilitate their work, so they decide what matters to them and what doesn't21:49
johnthetubaguywhich was a bit silly21:49
*** dflorea has quit IRC21:49
* mordred once again points out that "user" is a TERRIBLE word in our world21:49
johnthetubaguyttx: yeah, I have an action to send them the above wiki, didn't get to that21:49
fungihttps://wiki.openstack.org/w/index.php?title=StringFreeze&diff=47151&oldid=4604921:49
ttxlike clarkb said, maybe modifying strings ar ok as long21:49
*** xyang1 has joined #openstack-meeting21:49
fungidid not include any explanation of why that was changed, unfortunately21:49
ttx...are ok as long as you keep the interpolation up21:49
johnthetubaguymordred: +1 needs diss-abiguation, and I need a dictionary21:50
bknudsonput that file in git/gerrit!21:50
mordredjohnthetubaguy: yah. and a thesaurus21:50
johnthetubaguymordred: yup21:50
* rockyg overloads another friendly word so it becomes meaningless in OpenStack....hah, take that!21:50
*** jungleboyj has quit IRC21:50
ttxjohnthetubaguy: if you manage to come up with something better that is OK with them, feel free to update the wiki page21:50
fungibknudson: yeah, lack of code review is the primary reason we've been moving so much from the wiki to git in the past year21:50
*** Guest70571 has quit IRC21:51
* jokke_ takes user as ops running their cloud and end-user as that poor fella clicking horizon21:51
ttxthis could be described in the project team guide somewhere21:51
johnthetubaguywhere do we want this to go, if I put it in gerrit?21:51
johnthetubaguyah, project team guide would work21:51
fungiwhen you have a project team guide hammer, problems like this certainly look like nails21:52
johnthetubaguyOK, is anyone jumping up and down to do that, or should I take that action?21:52
ttxjohnthetubaguy: yeah, even if some projects wouldn't follow those, describing that common community practice there sounds like the right place21:52
*** dwalleck has joined #openstack-meeting21:52
*** cloudtrainme has joined #openstack-meeting21:52
fungijohnthetubaguy: seems as good a home as any21:52
johnthetubaguycool21:52
*** dflorea has joined #openstack-meeting21:52
johnthetubaguy#action johnthetubaguy to add string freeze description into project team guide21:53
johnthetubaguythat version fungi found from dolph seems quite good, back in 201421:53
johnthetubaguycool, thats all for me21:53
*** njohnston is now known as nate_gone21:53
johnthetubaguyany more?21:53
*** eduardo has quit IRC21:53
rockygcan you remove the text from the wiki and put a pointer to the project guide when you're done?21:54
*** davidjc has quit IRC21:54
johnthetubaguyrockyg: totally will do, will update the wiki first21:54
rockygthanks!21:54
*** otter768 has joined #openstack-meeting21:55
*** marcusvrn_ has quit IRC21:55
johnthetubaguycool, thank you all21:55
jokke_big hand to ttx and dhellmann for herding us towards one more release and ttx being all around the place for one summit as well :)21:55
elmikohear hear21:55
*** sdake_ is now known as sdake21:55
ttxthx!21:55
johnthetubaguyenjoy your morning/afternoon/lunch/sleep all!21:55
jokke_thnx all21:55
johnthetubaguyjokke_ +121:55
ttxsleep!21:55
rockyghuzzah!21:55
jrolljokke_++21:55
johnthetubaguy#endmeeting21:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:55
openstackMeeting ended Tue Sep  8 21:55:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-08-21.01.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-08-21.01.txt21:56
*** gordc has left #openstack-meeting21:56
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-08-21.01.log.html21:56
elmikothanks johnthetubaguy21:56
jrollthanks all21:56
*** pm90__ has quit IRC21:56
rockyggood job, johnthetubaguy21:56
EmilienMthanks21:56
*** VW_ has joined #openstack-meeting21:56
Pietcheers!21:57
*** cloudtra_ has joined #openstack-meeting21:57
*** achanda_ has quit IRC21:58
*** pm90_ has joined #openstack-meeting21:58
*** otter768 has quit IRC21:59
*** VW__ has quit IRC22:00
*** jmckind has quit IRC22:00
*** doug-fish has quit IRC22:00
*** neelashah has quit IRC22:01
*** VW_ has quit IRC22:01
*** cloudtrainme has quit IRC22:01
*** neelashah has joined #openstack-meeting22:01
*** achanda has joined #openstack-meeting22:02
*** barker has quit IRC22:02
*** sdake_ has joined #openstack-meeting22:02
*** Daisy has joined #openstack-meeting22:02
*** balajiiyer has quit IRC22:03
*** derekh has joined #openstack-meeting22:03
*** sdake has quit IRC22:05
*** asettle has joined #openstack-meeting22:06
*** adahms has joined #openstack-meeting22:06
*** achanda has quit IRC22:09
*** achanda has joined #openstack-meeting22:09
*** bknudson has quit IRC22:11
*** Piet has quit IRC22:11
*** iben has quit IRC22:11
*** achanda_ has joined #openstack-meeting22:13
*** annegentle has quit IRC22:13
*** achanda has quit IRC22:13
*** davidjc has joined #openstack-meeting22:14
*** balajiiyer has joined #openstack-meeting22:16
*** spotz is now known as spotz_zzz22:16
*** ivar-lazzaro has quit IRC22:17
*** glauco_ has quit IRC22:17
*** iben has joined #openstack-meeting22:19
*** rockyg has quit IRC22:19
*** IlyaG has quit IRC22:20
*** tsymanczyk has left #openstack-meeting22:20
*** neelashah has quit IRC22:20
*** lukebrooker has joined #openstack-meeting22:22
*** pradk has quit IRC22:22
*** AlanClark has quit IRC22:23
*** derekh has quit IRC22:24
*** angdraug has left #openstack-meeting22:26
*** balajiiyer has quit IRC22:28
*** mwagner_lap has quit IRC22:28
*** alex_xu has quit IRC22:28
*** ayoung_ has quit IRC22:29
*** ayoung has quit IRC22:29
*** stevemar has quit IRC22:29
*** IlyaG has joined #openstack-meeting22:30
*** sigmavirus24 is now known as sigmavirus24_awa22:30
*** alex_xu has joined #openstack-meeting22:30
*** IlyaG_ has joined #openstack-meeting22:30
*** jecarey has quit IRC22:31
*** neelashah has joined #openstack-meeting22:31
*** IlyaG_ has quit IRC22:31
*** lblanchard has quit IRC22:31
*** dannywilson has joined #openstack-meeting22:32
*** dannywilson has quit IRC22:32
*** balajiiyer has joined #openstack-meeting22:33
*** dannywilson has joined #openstack-meeting22:33
*** IlyaG has quit IRC22:34
*** iben has quit IRC22:34
*** lblanchard has joined #openstack-meeting22:35
*** vijendar has quit IRC22:36
*** xyang1 has quit IRC22:36
*** Sukhdev_ has joined #openstack-meeting22:36
*** lblanchard has quit IRC22:36
*** lblanchard has joined #openstack-meeting22:38
*** lblanchard has joined #openstack-meeting22:39
*** wbhuber is now known as wbhuber_22:40
*** earlephilhower has quit IRC22:42
*** guest_____ has quit IRC22:43
*** lblanchard has quit IRC22:43
*** Daisy has quit IRC22:45
*** cloudtra_ has quit IRC22:45
*** Daisy has joined #openstack-meeting22:45
*** Brian has joined #openstack-meeting22:47
*** Brian is now known as Guest6251722:47
*** hrou has quit IRC22:48
*** balajiiyer has quit IRC22:49
*** Daisy has quit IRC22:49
*** krtaylor has quit IRC22:49
*** balajiiyer has joined #openstack-meeting22:50
*** janonymous_ has quit IRC22:51
*** Guest62517 has quit IRC22:52
*** wbhuber_ has quit IRC22:52
*** pballand has quit IRC22:54
*** lukebrooker has quit IRC22:54
*** achanda has joined #openstack-meeting22:55
*** achanda_ has quit IRC22:55
*** dflorea has quit IRC22:58
*** dwalleck has quit IRC22:59
*** dwalleck has joined #openstack-meeting22:59
*** Piet has joined #openstack-meeting23:00
*** Guest36435 is now known as beagles23:00
*** ddieterly has quit IRC23:01
*** achanda_ has joined #openstack-meeting23:01
*** achanda has quit IRC23:01
*** rbak has quit IRC23:02
*** dflorea has joined #openstack-meeting23:03
jaypipesedleafe-: allow comments on your blog :)23:04
*** lukebrooker has joined #openstack-meeting23:05
*** eharney has quit IRC23:06
*** stevemar has joined #openstack-meeting23:07
*** dflorea has quit IRC23:07
*** scinawa has quit IRC23:08
*** hemna is now known as hemnafk23:10
*** dwalleck has quit IRC23:10
*** isq has joined #openstack-meeting23:11
*** dwalleck has joined #openstack-meeting23:11
*** dwalleck has quit IRC23:14
*** novas0x2a|laptop has quit IRC23:14
*** asettle is now known as asettle-afk23:15
*** nadya has joined #openstack-meeting23:16
*** carl_baldwin has quit IRC23:17
*** Sukhdev_ has quit IRC23:17
*** glauco has joined #openstack-meeting23:18
*** erlon has quit IRC23:18
*** ivar-lazzaro has joined #openstack-meeting23:18
*** Sukhdev has quit IRC23:19
*** Sukhdev has joined #openstack-meeting23:19
*** nadya has quit IRC23:20
*** glauco has quit IRC23:22
*** achanda has joined #openstack-meeting23:23
*** achanda_ has quit IRC23:23
*** pm90_ has quit IRC23:25
*** banix has joined #openstack-meeting23:25
*** yamamoto has joined #openstack-meeting23:30
*** xingchao has joined #openstack-meeting23:31
*** yamamoto has quit IRC23:31
*** oomichi has joined #openstack-meeting23:32
*** tochi has joined #openstack-meeting23:33
*** cdelatte has joined #openstack-meeting23:34
*** VikasC has quit IRC23:35
*** vivek-ebay has joined #openstack-meeting23:36
*** emagana has quit IRC23:37
*** cdelatte has quit IRC23:37
*** ayoung has joined #openstack-meeting23:38
*** asettle-afk is now known as asettle23:38
*** ayoung_ has joined #openstack-meeting23:38
*** Sukhdev has quit IRC23:38
*** ijw_ has quit IRC23:40
*** Sukhdev has joined #openstack-meeting23:40
*** salv-orlando has quit IRC23:41
*** xingchao has quit IRC23:44
*** hrou has joined #openstack-meeting23:44
*** hichihara has joined #openstack-meeting23:48
*** asettle has quit IRC23:48
*** asettle has joined #openstack-meeting23:49
*** johnhunter has joined #openstack-meeting23:51
*** Swami has quit IRC23:52
*** ajmiller has quit IRC23:55
*** electrocucaracha has quit IRC23:55
*** otter768 has joined #openstack-meeting23:55
*** ddieterly has joined #openstack-meeting23:56
*** jungleboyj has joined #openstack-meeting23:58

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