Tuesday, 2014-12-16

*** zz_avozza is now known as avozza00:00
*** bradjones has joined #openstack-meeting00:01
*** noelbk has quit IRC00:02
*** IlyaE has joined #openstack-meeting00:02
*** colinmcnamara has quit IRC00:03
*** yeungp has joined #openstack-meeting00:03
*** Tross has quit IRC00:04
*** dboik has quit IRC00:05
*** alex_xu has quit IRC00:05
*** dboik has joined #openstack-meeting00:05
*** zz_zz_zz_sabari is now known as sabari00:06
*** Tross has joined #openstack-meeting00:06
*** aranjan has joined #openstack-meeting00:06
*** mdenny has quit IRC00:07
*** yamamoto has joined #openstack-meeting00:08
*** padkrish has quit IRC00:09
*** avozza is now known as zz_avozza00:10
*** aranjan has quit IRC00:11
*** zz_avozza is now known as avozza00:11
*** dannywilson has quit IRC00:12
*** Masahiro has joined #openstack-meeting00:12
*** dannywilson has joined #openstack-meeting00:12
*** SridharRamaswamy has joined #openstack-meeting00:13
*** ddieterly has quit IRC00:14
*** dannywilson has quit IRC00:17
*** Masahiro has quit IRC00:17
*** rm_work is now known as rm_work|away00:21
*** sbalukoff has quit IRC00:24
*** sabari is now known as zz_sabari00:27
*** mtanino has quit IRC00:27
*** padkrish has joined #openstack-meeting00:29
*** annegent_ has joined #openstack-meeting00:29
*** markvoelker has quit IRC00:30
*** mudassirlatif has quit IRC00:31
*** mudassirlatif has joined #openstack-meeting00:32
*** annegent_ has quit IRC00:34
*** david-lyle is now known as david-lyle_afk00:35
*** sorrison has quit IRC00:36
*** sorrison has joined #openstack-meeting00:36
*** comay has quit IRC00:36
*** dims has joined #openstack-meeting00:38
*** padkrish has quit IRC00:40
*** oomichi has joined #openstack-meeting00:41
*** noelbk has joined #openstack-meeting00:46
*** hemna_ is now known as hemnafk00:49
*** alex_xu has joined #openstack-meeting00:49
*** dpaterson has quit IRC00:51
*** emagana has joined #openstack-meeting00:51
*** Masahiro has joined #openstack-meeting00:51
*** kebray has quit IRC00:52
*** emagana has quit IRC00:56
*** alexpilotti has joined #openstack-meeting00:58
*** sbalukoff has joined #openstack-meeting00:58
*** kebray has joined #openstack-meeting00:59
*** otter768 has joined #openstack-meeting01:00
*** markvoelker has joined #openstack-meeting01:01
*** otter768 has quit IRC01:05
*** ChuckC has quit IRC01:05
*** rmoe has quit IRC01:05
*** avozza is now known as zz_avozza01:06
*** mtanino has joined #openstack-meeting01:06
*** markvoelker has quit IRC01:07
*** markmcclain has quit IRC01:07
*** dsetia has quit IRC01:09
*** tsekiyama has joined #openstack-meeting01:10
*** padkrish has joined #openstack-meeting01:10
*** kebray has quit IRC01:11
*** sarob has quit IRC01:13
*** tsekiyama has quit IRC01:14
*** IlyaE has quit IRC01:15
*** padkrish has quit IRC01:19
*** AlanClark has quit IRC01:19
*** suro_ has quit IRC01:20
*** padkrish has joined #openstack-meeting01:20
*** padkrish has quit IRC01:21
*** padkrish has joined #openstack-meeting01:22
*** Alexandra_ has joined #openstack-meeting01:22
*** asettle has quit IRC01:22
*** Alexandra_ is now known as asettle01:23
*** noelbk has quit IRC01:25
*** annegent_ has joined #openstack-meeting01:30
*** che-arne|2 has joined #openstack-meeting01:31
*** dboik has quit IRC01:32
*** Mandell has joined #openstack-meeting01:32
*** che-arne has quit IRC01:33
*** prad has quit IRC01:33
*** leeantho has quit IRC01:33
*** yaguang has joined #openstack-meeting01:34
*** annegent_ has quit IRC01:35
*** julim has quit IRC01:36
*** rmoe has joined #openstack-meeting01:37
*** DrBacchus has joined #openstack-meeting01:38
*** Riddhi has quit IRC01:40
*** markvoelker has joined #openstack-meeting01:40
*** rbowen has quit IRC01:41
*** ChuckC has joined #openstack-meeting01:42
*** padkrish has quit IRC01:44
*** killer_prince is now known as lazy_prince01:45
*** bdpayne has quit IRC01:46
*** alexpilotti has quit IRC01:47
*** sbalukoff has quit IRC01:47
*** emagana has joined #openstack-meeting01:52
*** marcoemorais has joined #openstack-meeting01:53
*** xuhanp has joined #openstack-meeting01:54
*** marcoemorais2 has joined #openstack-meeting01:55
*** marcoemorais1 has quit IRC01:56
*** emagana has quit IRC01:56
*** marcoemorais1 has joined #openstack-meeting01:57
*** haomaiwang has joined #openstack-meeting01:57
*** marcoemorais has quit IRC01:58
*** marcoemorais3 has joined #openstack-meeting01:58
*** marcoemorais1 has quit IRC01:58
*** marcoemorais2 has quit IRC02:00
*** marcoemorais3 has quit IRC02:02
*** Apoorva has quit IRC02:03
*** marcoemorais has joined #openstack-meeting02:04
*** mtanino has quit IRC02:05
*** dims has quit IRC02:06
*** dims has joined #openstack-meeting02:06
*** sarob has joined #openstack-meeting02:06
*** marcoemorais has quit IRC02:07
*** Riddhi has joined #openstack-meeting02:08
*** gyee has quit IRC02:09
*** penick_ has joined #openstack-meeting02:10
*** Riddhi has quit IRC02:10
*** yaguang has quit IRC02:10
*** penick has quit IRC02:10
*** penick_ is now known as penick02:10
*** yaguang has joined #openstack-meeting02:11
*** Riddhi has joined #openstack-meeting02:11
*** dims has quit IRC02:11
*** zhhuabj has quit IRC02:13
*** shashankhegde has quit IRC02:13
*** spzala has joined #openstack-meeting02:14
*** zhhuabj has joined #openstack-meeting02:14
*** ZiGMaX has quit IRC02:16
*** oomichi has quit IRC02:16
*** sarob has quit IRC02:19
*** adalbas has quit IRC02:19
*** zz_avozza is now known as avozza02:27
*** yaguang has quit IRC02:29
*** annegent_ has joined #openstack-meeting02:29
*** haleyb has quit IRC02:29
*** yaguang has joined #openstack-meeting02:31
*** annegent_ has quit IRC02:34
*** novas0x2a|laptop has quit IRC02:35
*** penick has quit IRC02:35
*** ptoohill_ has joined #openstack-meeting02:35
*** ptoohill_ has quit IRC02:36
*** ptoohill_ has joined #openstack-meeting02:36
*** avozza is now known as zz_avozza02:38
*** ebalduf has joined #openstack-meeting02:39
*** alop has quit IRC02:39
*** emagana has joined #openstack-meeting02:43
*** ivar-laz_ has joined #openstack-meeting02:45
*** whayutin_ has quit IRC02:46
*** ioram_ has joined #openstack-meeting02:47
*** ioram has quit IRC02:47
*** emagana has quit IRC02:48
*** wuhg has joined #openstack-meeting02:48
*** ivar-lazzaro has quit IRC02:49
*** emagana has joined #openstack-meeting02:50
*** jaypipes has joined #openstack-meeting02:50
*** emagana has quit IRC02:54
*** neelashah has joined #openstack-meeting02:56
*** yalie__ has quit IRC02:58
*** dims has joined #openstack-meeting02:59
*** yapeng has quit IRC02:59
*** SridharRamaswamy has quit IRC02:59
*** KanagarajM has joined #openstack-meeting02:59
*** eghobo has quit IRC03:01
*** otter768 has joined #openstack-meeting03:01
*** Masahiro has quit IRC03:02
*** Masahiro has joined #openstack-meeting03:02
*** annegent_ has joined #openstack-meeting03:03
*** jyuso has quit IRC03:03
*** madskier has joined #openstack-meeting03:04
*** annegent_ has quit IRC03:05
*** epico has joined #openstack-meeting03:06
*** otter768 has quit IRC03:06
*** ebalduf has quit IRC03:07
*** rwsu has quit IRC03:09
*** yalie__ has joined #openstack-meeting03:10
*** mchalla has quit IRC03:15
*** JRobinson__ is now known as JRobinson__afk03:16
*** madskier has quit IRC03:21
*** ebalduf has joined #openstack-meeting03:21
*** zz_avozza is now known as avozza03:30
*** boris-42 has quit IRC03:33
*** KanagarajM has quit IRC03:33
*** jyuso has joined #openstack-meeting03:34
*** lazy_prince is now known as killer_prince03:34
*** hemna has joined #openstack-meeting03:37
*** bauzas has quit IRC03:38
*** SridharRamaswamy has joined #openstack-meeting03:39
*** avozza is now known as zz_avozza03:40
*** emagana has joined #openstack-meeting03:41
*** anish_ has joined #openstack-meeting03:42
*** Mandell has quit IRC03:43
*** SridharRamaswamy has quit IRC03:44
*** kebray has joined #openstack-meeting03:45
*** zz_sabari is now known as sabari03:46
*** mchalla has joined #openstack-meeting03:46
*** madskier has joined #openstack-meeting03:47
*** ebalduf has quit IRC03:47
*** dims has quit IRC03:49
*** sbalukoff has joined #openstack-meeting03:49
*** mchalla has quit IRC03:51
*** bauzas has joined #openstack-meeting03:52
*** marun has quit IRC03:52
*** madskier has quit IRC03:52
*** anish_ has quit IRC03:52
*** oomichi has joined #openstack-meeting03:53
*** oomichi has quit IRC03:54
*** ebalduf has joined #openstack-meeting03:54
*** varora has joined #openstack-meeting04:00
*** liusheng has quit IRC04:00
*** bauzas has quit IRC04:00
*** liusheng has joined #openstack-meeting04:01
*** Mandell has joined #openstack-meeting04:02
*** bauzas has joined #openstack-meeting04:03
*** funzo has quit IRC04:04
*** funzo has joined #openstack-meeting04:05
*** anish_ has joined #openstack-meeting04:06
*** radez is now known as radez_g0n304:06
*** armax has joined #openstack-meeting04:08
*** wanghong has quit IRC04:10
*** ebalduf has quit IRC04:11
*** JRobinson__afk is now known as JRobinson__04:14
*** ivar-laz_ has quit IRC04:17
*** IlyaE has joined #openstack-meeting04:17
*** neelashah has quit IRC04:18
*** IlyaE has quit IRC04:18
*** ebalduf has joined #openstack-meeting04:18
*** shankar has joined #openstack-meeting04:19
*** IlyaE has joined #openstack-meeting04:21
*** haomaiwang has quit IRC04:22
*** wanghong has joined #openstack-meeting04:23
*** haomaiwang has joined #openstack-meeting04:23
*** sabari is now known as zz_sabari04:29
*** jecarey has joined #openstack-meeting04:30
*** BharatK has joined #openstack-meeting04:30
*** rajeshr has joined #openstack-meeting04:31
*** zz_avozza is now known as avozza04:31
*** jwcroppe_ has quit IRC04:33
*** aweeks has quit IRC04:34
*** daneyon_ has joined #openstack-meeting04:34
*** jwcroppe has joined #openstack-meeting04:34
*** lbragstad has quit IRC04:35
*** daneyon has quit IRC04:35
*** baoli has quit IRC04:35
*** vishy has quit IRC04:35
*** wuhg has quit IRC04:36
*** jraim_ has quit IRC04:36
*** sileht has quit IRC04:36
*** fungi has quit IRC04:36
*** gus has quit IRC04:36
*** wuhg has joined #openstack-meeting04:38
*** lbragstad has joined #openstack-meeting04:38
*** jraim has joined #openstack-meeting04:38
*** aweeks has joined #openstack-meeting04:39
*** ebalduf has quit IRC04:39
*** gus has joined #openstack-meeting04:39
*** sileht has joined #openstack-meeting04:40
*** fungi has joined #openstack-meeting04:40
*** vishy has joined #openstack-meeting04:40
*** avozza is now known as zz_avozza04:41
*** killer_prince has quit IRC04:41
*** SridharG has joined #openstack-meeting04:43
*** ebalduf has joined #openstack-meeting04:45
*** rajeshr has quit IRC04:49
*** ebalduf has quit IRC04:51
*** ayoung has quit IRC04:52
*** kebray has quit IRC04:52
*** kebray has joined #openstack-meeting04:53
*** mudassirlatif has joined #openstack-meeting04:55
*** ebalduf has joined #openstack-meeting04:57
*** aranjan has joined #openstack-meeting04:58
*** jamespage has quit IRC05:00
*** jamespage has joined #openstack-meeting05:01
*** wanghong has quit IRC05:01
*** yaguang has quit IRC05:02
*** achanda has joined #openstack-meeting05:02
*** ebalduf has quit IRC05:02
*** otter768 has joined #openstack-meeting05:02
*** yaguang has joined #openstack-meeting05:03
*** luis_fdez has quit IRC05:04
*** shashankhegde has joined #openstack-meeting05:05
*** epico has quit IRC05:05
*** ebalduf has joined #openstack-meeting05:06
*** otter768 has quit IRC05:07
*** sarob has joined #openstack-meeting05:08
*** epico has joined #openstack-meeting05:09
*** Mandell has quit IRC05:09
*** madskier has joined #openstack-meeting05:15
*** ebalduf has quit IRC05:17
*** jacer_huawei has joined #openstack-meeting05:17
*** madskier has quit IRC05:23
*** tris has quit IRC05:25
*** reed has quit IRC05:25
*** SridharG has quit IRC05:26
*** tris has joined #openstack-meeting05:26
*** reed has joined #openstack-meeting05:28
*** mudassirlatif has quit IRC05:28
*** jacer_huawei has quit IRC05:29
*** ebalduf has joined #openstack-meeting05:29
*** zz_avozza is now known as avozza05:32
*** jacer_huawei has joined #openstack-meeting05:32
*** aranjan_ has joined #openstack-meeting05:32
*** shashankhegde has quit IRC05:34
*** ebalduf has quit IRC05:35
*** nelsnelson has quit IRC05:35
*** aranjan has quit IRC05:36
*** oomichi has joined #openstack-meeting05:38
*** Mandell has joined #openstack-meeting05:38
*** jacer_huawei has quit IRC05:39
*** ebalduf has joined #openstack-meeting05:41
*** jacer_huawei has joined #openstack-meeting05:41
*** marcoemorais has joined #openstack-meeting05:41
*** avozza is now known as zz_avozza05:41
*** harlowja is now known as harlowja_away05:42
*** asettle has quit IRC05:43
*** marcoemorais1 has joined #openstack-meeting05:43
*** noelbk has joined #openstack-meeting05:43
*** marcoemorais has quit IRC05:46
*** ebalduf has quit IRC05:47
*** mchalla has joined #openstack-meeting05:48
*** sarob has quit IRC05:52
*** mchalla has quit IRC05:53
*** achanda has quit IRC05:53
*** ebalduf has joined #openstack-meeting05:54
*** JRobinson__ has quit IRC05:57
*** boris-42 has joined #openstack-meeting05:59
*** sarob has joined #openstack-meeting05:59
*** IlyaE_ has joined #openstack-meeting06:00
*** IlyaE has quit IRC06:00
*** aranjan_ has quit IRC06:01
*** oomichi has quit IRC06:02
*** achanda has joined #openstack-meeting06:03
*** SridharRamaswamy has joined #openstack-meeting06:05
*** anish_ has quit IRC06:05
*** noelbk has quit IRC06:06
*** anish_ has joined #openstack-meeting06:06
*** bradjones has quit IRC06:07
*** bradjones has joined #openstack-meeting06:10
*** jacer_huawei is now known as wanghong06:10
*** SridharG has joined #openstack-meeting06:12
*** vigneshvar has joined #openstack-meeting06:12
*** nshaikh has joined #openstack-meeting06:13
*** dannywilson has joined #openstack-meeting06:14
*** hemna has quit IRC06:15
*** wanghong has quit IRC06:16
*** chandankumar has joined #openstack-meeting06:17
*** fwdit_ has joined #openstack-meeting06:18
*** aepifanov has joined #openstack-meeting06:19
*** markvoelker has quit IRC06:20
*** markvoelker has joined #openstack-meeting06:20
*** fwdit has quit IRC06:21
*** mrmartin has joined #openstack-meeting06:22
*** emagana has quit IRC06:23
*** gcb has joined #openstack-meeting06:25
*** markvoelker has quit IRC06:25
*** dannywilson has quit IRC06:27
*** dannywilson has joined #openstack-meeting06:28
*** vigneshvar has quit IRC06:28
*** wanghong has joined #openstack-meeting06:28
*** whenry has quit IRC06:31
*** rajeshr has joined #openstack-meeting06:31
*** IlyaE_ has quit IRC06:32
*** dannywilson has quit IRC06:32
*** bradjones has quit IRC06:35
*** reed has quit IRC06:35
*** neeti has joined #openstack-meeting06:36
*** adahms has quit IRC06:38
*** killer_prince has joined #openstack-meeting06:41
*** killer_prince has quit IRC06:41
*** zz_avozza is now known as avozza06:41
*** shashankhegde has joined #openstack-meeting06:41
*** lazy_prince has joined #openstack-meeting06:42
*** lazy_prince has quit IRC06:42
*** kopparam has joined #openstack-meeting06:42
*** aepifanov has quit IRC06:42
*** lazy_prince has joined #openstack-meeting06:43
*** whenry has joined #openstack-meeting06:43
*** mchalla has joined #openstack-meeting06:43
*** jecarey has quit IRC06:45
*** stevemar has quit IRC06:46
*** imsurit has joined #openstack-meeting06:46
*** IlyaE has joined #openstack-meeting06:47
*** whenry has quit IRC06:48
*** mchalla has quit IRC06:48
*** zz_sabari is now known as sabari06:48
*** bobmel has joined #openstack-meeting06:49
*** SridharRamaswamy has quit IRC06:49
*** markvoelker has joined #openstack-meeting06:51
*** bobmel_ has quit IRC06:51
*** Salman has joined #openstack-meeting06:52
*** Salman has left #openstack-meeting06:53
*** vigneshvar has joined #openstack-meeting06:54
*** emagana has joined #openstack-meeting06:54
*** markvoelker has quit IRC06:56
*** emagana has quit IRC06:58
*** pnavarro has joined #openstack-meeting06:59
*** kopparam has quit IRC07:00
*** gcb has quit IRC07:00
*** gcb has joined #openstack-meeting07:00
*** niclem has quit IRC07:01
*** niclem has joined #openstack-meeting07:02
*** sballe has quit IRC07:02
*** doron_afk has joined #openstack-meeting07:03
*** kopparam has joined #openstack-meeting07:03
*** otter768 has joined #openstack-meeting07:03
*** kopparam has quit IRC07:03
*** shashankhegde has quit IRC07:03
*** mrda is now known as mrda-away07:05
*** sarob has quit IRC07:06
*** yamamoto has quit IRC07:06
*** pnavarro has quit IRC07:06
*** otter768 has quit IRC07:08
*** avozza is now known as zz_avozza07:08
*** nshaikh has quit IRC07:10
*** achanda has quit IRC07:10
*** _nadya_ has joined #openstack-meeting07:11
*** achanda has joined #openstack-meeting07:11
*** aranjan has joined #openstack-meeting07:12
*** anish_ has quit IRC07:13
*** achanda has quit IRC07:16
*** aranjan has quit IRC07:17
*** gongysh has quit IRC07:17
*** garyk has joined #openstack-meeting07:18
*** marcoemorais1 has left #openstack-meeting07:20
*** nshaikh has joined #openstack-meeting07:20
*** Longgeek has joined #openstack-meeting07:24
*** pnavarro has joined #openstack-meeting07:26
*** e0ne has joined #openstack-meeting07:26
*** sweston is now known as sweston_away07:27
*** aranjan has joined #openstack-meeting07:29
*** gongysh has joined #openstack-meeting07:30
*** achanda has joined #openstack-meeting07:34
*** pnavarro has quit IRC07:34
*** yamamoto has joined #openstack-meeting07:35
*** nuritv has joined #openstack-meeting07:37
*** nuritv has left #openstack-meeting07:37
*** Nuritv_ has joined #openstack-meeting07:38
*** sahid has joined #openstack-meeting07:39
*** penick has joined #openstack-meeting07:40
*** Nuritv_ is now known as nuritv07:40
*** lpeer__ has quit IRC07:45
*** bvandenh has joined #openstack-meeting07:48
*** shankar has quit IRC07:49
*** aepifanov has joined #openstack-meeting07:50
*** e0ne has quit IRC07:51
*** liusheng has quit IRC07:51
*** jyuso has quit IRC07:52
*** luis_fdez has joined #openstack-meeting07:52
*** liusheng has joined #openstack-meeting07:52
*** emagana has joined #openstack-meeting07:55
*** IlyaE has quit IRC07:56
*** jyuso has joined #openstack-meeting07:57
*** yamamoto has quit IRC07:58
*** emagana has quit IRC07:59
*** trinaths has joined #openstack-meeting07:59
trinathsHi08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Dec 16 08:00:03 2014 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
anteayahello trinaths08:00
trinathshi anteaya08:00
jhesketh Howdy08:00
anteayahey jhesketh08:00
anteayaanyone else here for the third-party meeting?08:01
*** sarob has joined #openstack-meeting08:01
*** garyk has quit IRC08:01
anteayaheyongli jyuso are you about?08:01
sarobwhos here for the ambassador meeting?08:01
jyusoanteaya: hello08:01
nuritvanteaya: Hi08:02
heyonglihi, anteaya , hi08:02
anteayahello all08:02
trinathshi all08:02
mrmartinsarob I guess we need to move the ambassador meeting to #openstack-meeting-308:02
jyusohi,everyone08:02
*** itzikb has joined #openstack-meeting08:02
*** egallen has joined #openstack-meeting08:02
anteayaso as we are just getting our group started and getting to know each other, right now we don't have an agenda08:03
anteayadoes anyone have a place which they would like to begin?08:03
*** Yingxin has joined #openstack-meeting08:03
trinathsI have some doubts in CI.08:03
nuritvanteaya: yes, just want to get attention the a review by omrim for FAQ08:03
anteayagreat08:04
*** Murad has joined #openstack-meeting08:04
anteayawho wants to go first?08:04
*** kopparam has joined #openstack-meeting08:04
nuritvtrinaths: go ahead08:04
trinathsnuritv: thank you.08:04
anteayaMurad: there you are08:04
Muradyes I am08:04
MuradHi everybody08:04
jyusohi Murad08:05
*** sergef has joined #openstack-meeting08:05
anteayatrinaths: okay so whenever you are ready08:06
*** yamamoto has joined #openstack-meeting08:06
trinathsI installed CI wil jaypipes documentation. In the CI Jenkins node, there are several git repos. and the same repos are existing with in the job nodes. Zuul-merger updates with the commit. how is that updated commit trasfered to job node?08:06
*** Murad has quit IRC08:06
*** Mandell has quit IRC08:07
anteayaokay good question08:07
*** Murad has joined #openstack-meeting08:07
trinathstypo error: transfered08:07
anteayadoes anyone have a response to trinaths' question?08:07
jheskethtrinaths: the zuul-merger reports back a ref to zuul that is then passed to the job08:08
jheskethso zuul then requests a worker to do a job with these params: http://ci.openstack.org/zuul/launchers.html#zuul-parameters08:08
*** achanda has quit IRC08:08
jheskeththe Jenkins gearman plugin exposes those params as environment variables08:08
*** whenry has joined #openstack-meeting08:08
jheskeththe gerrit-git-prep.sh script looks for those params and sets up a working directory for the test08:09
trinathsjhesketh: okay.08:09
*** zz_avozza is now known as avozza08:09
trinathsthen why a git checkout is required in jenkins node?08:10
trinathsi mean the master node08:10
*** yamamoto has quit IRC08:10
jheskethtrinaths: hmm, it should only be the slave node.. but I don't run Jenkins so I'm not sure08:10
jheskethmy best guess is that it's not needed and there from a legacy setup08:10
*** kopparam has quit IRC08:11
trinathsjhesketh: okay. I will refer again.08:11
jheskethsorry I haven't got a specific answer there08:11
trinathsjhesketh: I missed to answer you08:12
anteayatrinaths: do you need anything more here?08:13
anteayaor is it nuritv's turn?08:13
trinathsanteaya: no. I have a que [2] When ever a job is trigger, devstack-gate updates all the projects, like, nova, neutron, cinder etc..08:14
*** lpeer__ has joined #openstack-meeting08:14
trinathsthis takes more time for the actual build to hapen and the test to run. How to simplify this? any suggestions08:14
anteayatrinaths: shall we let nuritv have a turn?08:14
*** achanda has joined #openstack-meeting08:15
*** yamamoto has joined #openstack-meeting08:15
trinathsanteaya: yes. Please go ahead08:15
anteayathank you08:15
anteayanuritv: let's hear from you now please08:15
nuritvanteaya: thanks. i have several issues i would like to raise :)08:15
* anteaya listens08:16
nuritvfirst of all, i would like to get everyone attention to the FAQ section by omrim08:16
*** nellysmitt has joined #openstack-meeting08:16
nuritvthere is still alot to do, but any more reviews will be helpful08:16
nuritvhttps://review.openstack.org/#/c/141817/308:16
anteaya#link https://review.openstack.org/#/c/141817/308:16
anteayathank you to omrim for offering this patch08:17
anteayapleia2 gave a pretty through review08:17
nuritvso, if anyone has other FAQ that are worth mentioning - please post a comment08:18
nuritvanteaya: yes, we all keep learning :)08:18
anteaya:D08:18
nuritvanteaya: can i continue to the next topic?08:18
anteayaoh yes08:19
*** mrunge has joined #openstack-meeting08:19
nuritvthanks. so, i am concern about the big change happening on Neutron (spliiting the plugins), and wonder how it is going to affect CI and what we should do in advance08:20
anteayathat is a good question08:20
anteayaI don't think there is anyone here from Neutron right now08:20
*** yamamoto has quit IRC08:20
anteayaso I will go ahead and respond to that one08:20
anteayaI don't know exactly how the plugin split will affect CI systems08:21
*** yamamoto has joined #openstack-meeting08:21
anteayahowever I was at the Neutron mid-cycle when the advanced services were split out08:21
*** rushiagr_away is now known as rushiagr08:21
anteayaand the immediate effect of that split was that all CIs that tested advanced services were suggested to turn themselves off until the new advanced services were running again08:22
*** xek has joined #openstack-meeting08:22
anteayasince one of the consequences of the split was that right afterwards the testing on the split out advanced services would not work08:22
*** Guest24100 has joined #openstack-meeting08:22
trinaths"new advanced services"08:23
anteayaso tests needed to be modified within openstack to get the infra jobs running again08:23
anteayaand to be honest I have now lost track and I don't know if the tests on advance services are working yet08:23
*** ajo has joined #openstack-meeting08:23
anteayathey were expected to be down until sometime this week08:23
anteayaso it is possible that during the split itself the plugins might not be able to be tested08:24
anteayawhich should not be a problem since new code to the plugins should be frozen for the duration of the split08:24
*** phil__ has joined #openstack-meeting08:24
trinathsI heard tempests test will also be splitted.08:24
anteayaas for how to prepare08:24
anteayaI would suggest ensuring you read the meeting logs of any meetings that discuss the split08:25
anteaya#link http://eavesdrop.openstack.org/08:25
anteayathis is where all openstack channel and meeting logs are accessed08:25
*** yamamoto has quit IRC08:25
anteayahelp yourself08:26
anteayaalso, I would find Edgar Magma in #openstack-neutron08:26
nuritvanteaya: my concern is more about ml2 md that will be out of tree. this would need us,as vendors, change code, git branch, etc.08:26
anteayait very well might require all of that08:26
anteayahave you been able to attend the ml2 meetings at all?08:26
*** xek has quit IRC08:26
nuritvanteaya: not yet. will start this week08:27
anteayaokay, I would definitely suggest that08:27
*** IlyaE has joined #openstack-meeting08:27
anteayahave you had a chance to look at the ml2 meeting logs?08:27
nuritvanteaya: not yet. will start this week also :)08:27
anteayaokay08:28
anteayaso start there08:28
*** anish_ has joined #openstack-meeting08:28
anteayaalso talk to Edgar08:28
anteayahe answers a lot of third party CI questions for Neutron08:28
anteayahe is emagma in irc08:28
anteayahe might have some specifics08:29
*** SridharG has quit IRC08:29
anteayadoes that help?08:29
*** anish_ has quit IRC08:29
nuritvyes! . will do. i guess it now just to  keep track on what will be the decision.08:29
anteayaokay great08:29
*** anish_ has joined #openstack-meeting08:29
nuritvand that brings me to my last Q08:29
*** vijaykodam has joined #openstack-meeting08:30
nuritvwhen ever our CI is down. is it better to turn it off and not vote at all, or jut mark it down at the Wiki.08:30
anteayaboth08:30
nuritvanteaya:ok. thanks.08:30
anteayaif your CI is not functioning as expected turn it off08:30
anteayathere is nothing worse for your CI that to be non-functioning yet commenting on patches08:31
*** nikil22 has joined #openstack-meeting08:31
anteayaas you train developers to ignore your system08:31
anteayasince you are not monitoring when you are posting quality information or noise08:31
*** vijaykodam has left #openstack-meeting08:31
anteayaso they will just assume you always post noise08:31
anteayahowever08:32
trinathsnuritv: This the latest log of the last ML2 meeting http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-12-03-16.03.log.html held on Dec-3rd08:32
anteayaif you monitor your system and its quality08:32
anteayaand only post comments when your system is actually working08:32
*** aloga has joined #openstack-meeting08:32
anteayathen developers will soon learn that your system can be trusted08:32
anteayaand updating the wikipage helps people to find accurate status information on your system08:33
nuritvgot it! thanks08:33
anteayaso again, it shows you are paying attention to how the output from your system is percieved by those using it08:33
nuritvtrinaths: thanks08:33
anteayathank you08:33
anteayanuritv: anything else right now?08:34
*** matrohon has joined #openstack-meeting08:34
nuritvanteaya: no. thanks08:34
anteayagreat08:34
anteayadoes anyone else have anything they wish to discuss?08:34
Guest24100I always found this in zuul log:  zuul.Gearman: Looking for lost builds08:35
anteayahello Guest2410008:35
Guest24100Hi08:35
anteayaare you able to introduce yourself?08:35
anteayaI don't believe I know you08:35
Guest24100You can call me bob08:35
*** bobmel has quit IRC08:35
anteayaokay bob, welcome08:35
Guest24100So what does that mean?08:36
anteayaso you have a question about gearman08:36
trinathsmy question [2]08:36
Guest24100yes08:36
*** bobmel has joined #openstack-meeting08:36
anteayadoes anyone have a response to bob's question?08:36
Guest24100zuul.Gearman: Looking for lost builds08:36
trinathsGuest24100: I too have this log in my merger-debug.log08:36
*** rakesh_hs has joined #openstack-meeting08:36
nikil22bob : have you tried to stop zuu and zuul-merger service and then rm -rf /var/log/zuul/* then restart the service and checked08:37
anteayahello nikil22, glad you made it08:37
Guest24100Yes, i have tried that08:37
Guest24100if i restart it, it will be ok08:38
Guest24100But I don't want always restart it08:38
*** shankar has joined #openstack-meeting08:38
nikil22bob : oh ok , yes can't restart all time . I just got few errors similar and i just did above step and it worked08:39
Guest24100Thanks, I have not yet do the "rm -rf /var/log/zuul/*"08:40
Guest24100And i will try it08:40
nikil22bob: thats just to clear logs but i guess it wont help08:40
Guest24100:-)08:40
nikil22And I have questions related to devstack-gate. when does the function pre_test_hook works? Basically In CI system i want to enable the driver in neutron.conf and then start the service08:40
anteayalet's ensure bob is statisfied before we move on08:41
anteayabob are we okay to move on, or do you have more?08:41
Guest24100No more, thanks!08:41
anteayagreat, thank you08:41
Guest24100:-)08:41
anteayanikil22: okay so your turn I believe08:41
anteayayou have a question about the pre_test_hook funtion in devstack-gate08:42
anteayais that correct?08:42
nikil22yes08:42
*** Krast has joined #openstack-meeting08:42
anteayadoes anyone have a reply to nikil22's question?08:43
nikil22i guess that is the function to enable drivers and modify other configuration files related to specify plugin insted of default one08:43
anteayaor perform any other commands to set up a specific environment08:44
anteayabefore the tests run08:44
*** Tross has quit IRC08:44
*** jlanoux has joined #openstack-meeting08:44
anteayaso it sounds like the pre_test_hook is a good place to begin your experiments in what you want to accomplish08:45
anteayadid anyone else have anything more to add in response to this question?08:45
anteayanikil22: are you statisfied or do you need more?08:46
*** Tross has joined #openstack-meeting08:46
* anteaya waits for nikil22 to reply08:47
nikil22will the pre_test_hook will run before starting the porcess or after starting the neutron-server process. Because if we change the settings then we need to restart the services right08:47
*** IlyaE has quit IRC08:47
*** k4n0 has joined #openstack-meeting08:47
*** liusheng has quit IRC08:48
*** IlyaE has joined #openstack-meeting08:48
anteayanikil22: I don't know exactly08:48
anteayabut I would guess that the pre_test_hook runs before the services start08:48
nikil22ok thanks i will do expriments then :-)08:48
anteayathat sounds like a good way forward08:48
anteayanikil22: all done for this question?08:48
*** che-arne|2 has quit IRC08:49
*** liusheng has joined #openstack-meeting08:49
*** Longgeek has quit IRC08:49
* anteaya waits for nikil22 to reply08:49
anteayanikil22: can we move on?08:50
nikil22yes08:50
*** kopparam has joined #openstack-meeting08:50
anteayathank you08:50
nikil22thanks08:50
anteaya10 minutes remaining08:50
*** Longgeek has joined #openstack-meeting08:50
anteayawho has something else they would like to discuss?08:50
*** IlyaE has quit IRC08:51
*** safchain has joined #openstack-meeting08:51
anteayaif noone else does, I have a question08:51
anteayaMurad: hello08:51
*** jcoufal has joined #openstack-meeting08:51
*** akira-y has joined #openstack-meeting08:51
MuradHello08:51
nikil22bob : have you ever tried to restart your jenkins-master machine and tried . so that it would restart the jenkins server also and all other services08:51
nikil22Murad: hii08:52
MuradHi08:52
anteayalast week we discussed how to get your server to serve files in the browser without being prompted to download them08:52
Muradyes08:52
anteayaMurad: do you know how to access the logs of the third-party meetings?08:52
anteayasince I believe I saw you asking this exact same question in the -infra channel this week08:52
Muradyes I have a link for the previous meeting08:52
anteayaand I was curious as to why that was08:52
anteayasince we discussed it last week08:53
anteayaand I wondered if perhaps you don't know where to find the meeting logs to read them08:53
MuradThat was because I was using wrong way to compress files08:53
MuradI have to use "gzip"08:53
anteayaoh, can you explain?08:53
*** armax has quit IRC08:53
anteayawhy do you have to use "gzip"?08:53
MuradI was using "tar" to produce gz files08:53
anteayawhat is making you do that?08:53
*** SridharG has joined #openstack-meeting08:53
Muradin order to compress log files08:54
anteayawell you use the tar command with the flag to output gziped files08:54
anteayato produce gzipped files08:54
Muradyes but that didn't work until I used "gzip"08:55
anteayaokay so what was the question to -infra (which I am redirecting to this meeting)08:55
*** asalkeld has joined #openstack-meeting08:55
*** emagana has joined #openstack-meeting08:55
Muradwhen I was compressing files with TAR, it only worked on firefox. So I though that I might using wrong apache configurations08:56
Muradand that was my question08:56
Muradafter investigation, I used gzip and it worked08:56
anteayaokay so you discoverd the answer to your own question08:57
Muradyes08:57
anteayagreat08:57
anteayathank you08:57
Muradthanks08:57
anteayadoes anyone have anything else?08:57
*** kopparam has quit IRC08:57
anteayawell time to wrap up then08:58
jyusoanteaya: Our CI log server is online now.If you have free time,could you help to point out the ssl-cert issue of our logs:)08:58
*** yobber has quit IRC08:58
anteayajyuso: you can pm me the ip address so I can view the logs08:59
jyusoanteaya: OK08:59
anteayathank you08:59
*** akira-y has quit IRC08:59
*** kopparam has joined #openstack-meeting08:59
anteayaso thank you everyone for attending this week08:59
anteayasee you next week08:59
anteaya#endmeeting08:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:59
jyusoanteaya: thanks,see you08:59
openstackMeeting ended Tue Dec 16 08:59:34 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2014/third_party.2014-12-16-08.00.html08:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2014/third_party.2014-12-16-08.00.txt08:59
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2014/third_party.2014-12-16-08.00.log.html08:59
heyonglianteaya, bye08:59
anteayabye08:59
*** trinaths has left #openstack-meeting09:00
*** emagana has quit IRC09:00
*** sarob has quit IRC09:00
*** jgallard_ has joined #openstack-meeting09:00
*** nuritv has left #openstack-meeting09:00
*** nikil22 has left #openstack-meeting09:01
*** yamamoto has joined #openstack-meeting09:01
*** Murad has quit IRC09:02
*** otter768 has joined #openstack-meeting09:04
*** lpeer__ has quit IRC09:04
*** zz_johnthetubagu is now known as johnthetubaguy09:05
*** yamamoto has quit IRC09:06
*** kopparam has quit IRC09:07
*** sabari is now known as zz_sabari09:07
*** Guest24100 has left #openstack-meeting09:07
*** lpeer__ has joined #openstack-meeting09:07
*** xuhanp has quit IRC09:07
*** otter768 has quit IRC09:08
*** kopparam has joined #openstack-meeting09:09
*** lpeer has joined #openstack-meeting09:09
*** derekh has joined #openstack-meeting09:10
*** yobber has joined #openstack-meeting09:10
*** ygbo has joined #openstack-meeting09:12
*** lpeer__ has quit IRC09:12
*** garyk has joined #openstack-meeting09:13
*** asalkeld has quit IRC09:17
*** stannie has joined #openstack-meeting09:18
*** shankar has quit IRC09:19
*** jlibosva has joined #openstack-meeting09:22
*** JRobinson__ has joined #openstack-meeting09:24
*** bvandenh has quit IRC09:27
*** mpaolino has joined #openstack-meeting09:27
*** kopparam_ has joined #openstack-meeting09:28
*** MaxV has joined #openstack-meeting09:29
*** kopparam has quit IRC09:29
*** martines_ has quit IRC09:30
*** penick has quit IRC09:31
*** andreaf has joined #openstack-meeting09:32
*** achanda has quit IRC09:32
*** achanda has joined #openstack-meeting09:32
*** shankar has joined #openstack-meeting09:33
*** SridharG has quit IRC09:33
*** sandywalsh has joined #openstack-meeting09:34
*** ioram_ has quit IRC09:36
*** sandywalsh_ has quit IRC09:36
*** achanda has quit IRC09:37
*** JRobinson__ has quit IRC09:40
*** achanda has joined #openstack-meeting09:41
*** ociuhandu has quit IRC09:41
*** tochi has quit IRC09:43
*** alex_xu has quit IRC09:44
*** achanda has quit IRC09:44
*** mtanino has joined #openstack-meeting09:44
*** achanda has joined #openstack-meeting09:44
*** bvandenh has joined #openstack-meeting09:45
*** _nadya_ has quit IRC09:46
*** SridharG has joined #openstack-meeting09:49
*** achanda has quit IRC09:50
*** achanda has joined #openstack-meeting09:50
*** Fdot has joined #openstack-meeting09:50
*** nellysmitt has quit IRC09:51
*** aranjan has quit IRC09:53
*** mtanino is now known as mtanino_zzz09:54
*** e0ne has joined #openstack-meeting09:55
*** emagana has joined #openstack-meeting09:56
*** shankar has quit IRC09:57
*** cody-somerville has quit IRC09:57
*** kopparam_ has quit IRC10:00
*** emagana has quit IRC10:01
*** luqas has quit IRC10:02
*** martines has joined #openstack-meeting10:02
*** ekarlso- has quit IRC10:07
*** ekarlso- has joined #openstack-meeting10:07
*** garyk has quit IRC10:10
*** shankar has joined #openstack-meeting10:11
*** cody-somerville has joined #openstack-meeting10:11
*** nikil22 has joined #openstack-meeting10:12
*** nikil22 has left #openstack-meeting10:12
*** mfedosin has quit IRC10:17
*** pelix has joined #openstack-meeting10:20
*** andreaf has quit IRC10:21
*** nellysmitt has joined #openstack-meeting10:25
*** avozza is now known as zz_avozza10:29
*** evgenyf has joined #openstack-meeting10:33
*** e0ne has quit IRC10:34
*** e0ne has joined #openstack-meeting10:38
*** lpeer_ has joined #openstack-meeting10:38
*** Fdot has quit IRC10:39
*** achanda has quit IRC10:40
*** garyk has joined #openstack-meeting10:41
*** Fdot has joined #openstack-meeting10:41
*** lpeer has quit IRC10:42
*** dulek has joined #openstack-meeting10:43
*** liusheng has quit IRC10:44
*** niclem has quit IRC10:44
*** liusheng has joined #openstack-meeting10:45
*** che-arne has joined #openstack-meeting10:46
*** aranjan has joined #openstack-meeting10:50
*** lpeer_ is now known as lpeer10:52
*** garyk has quit IRC10:53
*** andreaf has joined #openstack-meeting10:53
*** aranjan has quit IRC10:55
*** zz_avozza is now known as avozza10:55
*** ociuhandu has joined #openstack-meeting10:56
*** luqas has joined #openstack-meeting10:56
*** emagana has joined #openstack-meeting10:57
*** anish_ has quit IRC10:57
*** jgallard_ has quit IRC10:57
*** kopparam has joined #openstack-meeting11:00
*** emagana has quit IRC11:01
*** Fdot has quit IRC11:04
*** otter768 has joined #openstack-meeting11:05
*** adalbas has joined #openstack-meeting11:06
*** Fdot has joined #openstack-meeting11:06
*** e0ne has quit IRC11:09
*** otter768 has quit IRC11:10
*** epico has quit IRC11:10
*** haomaiwang has quit IRC11:14
*** bradjones has joined #openstack-meeting11:15
*** kopparam has quit IRC11:16
*** kopparam has joined #openstack-meeting11:16
*** SridharG has quit IRC11:17
*** alex_xu has joined #openstack-meeting11:20
*** Masahiro has quit IRC11:23
*** e0ne has joined #openstack-meeting11:24
*** gongysh has quit IRC11:24
*** evgenyf has quit IRC11:25
*** jlanoux_ has joined #openstack-meeting11:26
*** moha_hunt has joined #openstack-meeting11:26
*** jlanoux has quit IRC11:28
*** egallen has quit IRC11:30
*** SridharG has joined #openstack-meeting11:31
*** aysyd has joined #openstack-meeting11:32
*** masayukig has quit IRC11:33
*** marcusvrn has quit IRC11:38
*** bvandenh has quit IRC11:38
*** Masahiro has joined #openstack-meeting11:39
*** masayukig has joined #openstack-meeting11:39
*** berendt has joined #openstack-meeting11:41
*** marcusvrn has joined #openstack-meeting11:42
*** dulek has quit IRC11:46
*** rajeshr has quit IRC11:46
*** zz_ttrifonov is now known as ttrifonov11:47
*** gcb has quit IRC11:48
*** jlanoux has joined #openstack-meeting11:51
*** jlanoux_ has quit IRC11:53
*** infotection has quit IRC11:53
*** Riddhi has quit IRC11:54
*** jlanoux has quit IRC11:55
*** markvoelker has joined #openstack-meeting11:56
*** emagana has joined #openstack-meeting11:58
*** jlanoux has joined #openstack-meeting11:59
*** infotection has joined #openstack-meeting11:59
*** moha_hunt has quit IRC11:59
*** kopparam has quit IRC12:00
*** markvoelker has quit IRC12:01
*** ddieterly has joined #openstack-meeting12:02
*** rakesh_hs has quit IRC12:02
*** emagana has quit IRC12:02
*** yamamoto has joined #openstack-meeting12:04
*** mpaolino has quit IRC12:04
*** jamespage_ has joined #openstack-meeting12:04
*** kopparam has joined #openstack-meeting12:05
*** jamespage_ has quit IRC12:05
*** Masahiro has quit IRC12:07
*** dims has joined #openstack-meeting12:07
*** Mandell has joined #openstack-meeting12:07
*** yamamoto has quit IRC12:09
*** infotection has quit IRC12:09
*** yamamoto has joined #openstack-meeting12:10
*** yamamoto_ has joined #openstack-meeting12:11
*** yamamoto has quit IRC12:11
*** infotection has joined #openstack-meeting12:11
*** marcusvrn has quit IRC12:11
*** marcusvrn has joined #openstack-meeting12:11
*** Mandell has quit IRC12:11
*** spredzy|afk is now known as spredzy12:11
*** jraim_ has joined #openstack-meeting12:12
*** dougwig_ has joined #openstack-meeting12:12
*** erw_ has joined #openstack-meeting12:13
*** s0mik_ has joined #openstack-meeting12:13
*** gcb has joined #openstack-meeting12:14
*** jraim has quit IRC12:14
*** jraim_ is now known as jraim12:14
*** dougwig has quit IRC12:14
*** otoolee has quit IRC12:14
*** erw has quit IRC12:14
*** s0mik has quit IRC12:14
*** sileht has quit IRC12:14
*** luqas has quit IRC12:14
*** anish_ has joined #openstack-meeting12:14
*** dougwig_ is now known as dougwig12:14
*** s0mik_ is now known as s0mik12:14
*** zeddii has quit IRC12:14
*** kopparam has quit IRC12:15
*** ptoohill_ has quit IRC12:15
*** zeddii has joined #openstack-meeting12:15
*** ptoohill_ has joined #openstack-meeting12:15
*** Fdot has quit IRC12:16
*** sileht has joined #openstack-meeting12:16
*** garyk has joined #openstack-meeting12:16
*** EmilienM is now known as EmilienM|afk12:17
*** Fdot has joined #openstack-meeting12:17
*** egallen has joined #openstack-meeting12:19
*** egallen has quit IRC12:19
*** kevinbenton has quit IRC12:20
*** egallen has joined #openstack-meeting12:20
*** otoolee has joined #openstack-meeting12:21
*** _nadya_ has joined #openstack-meeting12:21
*** pelix has quit IRC12:22
*** kevinbenton has joined #openstack-meeting12:22
*** pelix has joined #openstack-meeting12:22
*** _nadya_ has quit IRC12:23
*** e0ne has quit IRC12:23
*** _nadya_ has joined #openstack-meeting12:24
*** baoli has joined #openstack-meeting12:24
*** baoli has quit IRC12:25
*** baoli has joined #openstack-meeting12:25
*** kopparam has joined #openstack-meeting12:25
*** mtanino_zzz has quit IRC12:26
*** amotoki has joined #openstack-meeting12:26
*** cgoncalv1s has joined #openstack-meeting12:26
*** Tross1 has joined #openstack-meeting12:29
*** yamamoto_ has quit IRC12:30
*** Tross has quit IRC12:30
*** moha_hunt has joined #openstack-meeting12:30
*** bauzas has quit IRC12:31
*** cgoncalves has quit IRC12:31
*** joehuang has joined #openstack-meeting12:32
*** joehuang has quit IRC12:33
*** yamamoto has joined #openstack-meeting12:33
*** stannie has quit IRC12:34
*** kevinbenton has quit IRC12:37
*** yamamoto has quit IRC12:37
*** unicell has joined #openstack-meeting12:38
*** aranjan has joined #openstack-meeting12:39
*** johnthetubaguy is now known as zz_johnthetubagu12:40
*** kevinbenton has joined #openstack-meeting12:40
*** luqas has joined #openstack-meeting12:41
*** luqas has quit IRC12:41
*** yamamoto has joined #openstack-meeting12:43
*** aranjan has quit IRC12:44
*** itzikb has left #openstack-meeting12:45
*** yamamoto has quit IRC12:46
*** bauzas has joined #openstack-meeting12:49
*** bvandenh has joined #openstack-meeting12:52
*** che-arne|2 has joined #openstack-meeting12:54
*** che-arne has quit IRC12:56
*** IanGovett has joined #openstack-meeting12:56
*** dprince has joined #openstack-meeting12:57
*** weshay has joined #openstack-meeting12:57
*** markvoelker has joined #openstack-meeting12:58
*** adahms has joined #openstack-meeting12:58
*** yamamoto has joined #openstack-meeting12:59
*** che-arne|2 has quit IRC12:59
*** che-arne has joined #openstack-meeting12:59
*** che-arne|2 has joined #openstack-meeting13:00
*** niclem has joined #openstack-meeting13:01
*** imsurit has quit IRC13:01
*** markvoelker has quit IRC13:02
*** alexpilotti has joined #openstack-meeting13:02
*** che-arne has quit IRC13:03
*** _nadya_ has quit IRC13:05
*** otter768 has joined #openstack-meeting13:06
*** doude has quit IRC13:06
*** alexpilotti_ has joined #openstack-meeting13:06
*** mtanino has joined #openstack-meeting13:07
*** aepifanov has quit IRC13:07
*** dims has quit IRC13:07
*** alexpilotti has quit IRC13:07
*** alexpilotti_ is now known as alexpilotti13:07
*** jckasper has joined #openstack-meeting13:07
*** aepifanov has joined #openstack-meeting13:07
*** doude has joined #openstack-meeting13:07
*** dims has joined #openstack-meeting13:07
*** dkranz has joined #openstack-meeting13:07
*** Masahiro has joined #openstack-meeting13:07
*** dulek has joined #openstack-meeting13:07
*** hashar has joined #openstack-meeting13:08
*** varora has left #openstack-meeting13:08
*** bauzas has quit IRC13:08
*** e0ne has joined #openstack-meeting13:09
*** otter768 has quit IRC13:10
*** bauzas has joined #openstack-meeting13:11
*** Masahiro has quit IRC13:12
*** mchalla has joined #openstack-meeting13:12
*** SridharG has quit IRC13:14
*** markvoelker has joined #openstack-meeting13:15
*** kopparam has quit IRC13:16
*** mchalla has quit IRC13:17
*** avozza is now known as zz_avozza13:17
*** jdurgin has quit IRC13:18
*** BrianShang has joined #openstack-meeting13:18
*** amitry has joined #openstack-meeting13:18
*** kopparam has joined #openstack-meeting13:19
*** yapeng has joined #openstack-meeting13:20
*** kopparam has quit IRC13:20
*** anish_ has quit IRC13:21
*** MeganR has joined #openstack-meeting13:22
*** berendt has quit IRC13:22
*** e0ne is now known as e0ne_13:25
*** raildo has joined #openstack-meeting13:26
*** oanufriev has joined #openstack-meeting13:28
*** EmilienM|afk is now known as EmilienM13:28
*** chandankumar has quit IRC13:29
*** SridharG has joined #openstack-meeting13:30
*** sweston_away has quit IRC13:31
*** doude has quit IRC13:31
*** doude has joined #openstack-meeting13:31
*** jdurgin has joined #openstack-meeting13:31
*** lifeless_ has joined #openstack-meeting13:33
*** sweston_away has joined #openstack-meeting13:34
*** sweston_away is now known as sweston13:35
*** lifeless has quit IRC13:35
*** e0ne_ has quit IRC13:35
*** jgallard_ has joined #openstack-meeting13:38
*** aranjan has joined #openstack-meeting13:40
*** mrmartin has quit IRC13:41
*** ddieterly has quit IRC13:42
*** vigneshvar has quit IRC13:42
*** aranjan has quit IRC13:44
*** mrmartin has joined #openstack-meeting13:47
*** e0ne has joined #openstack-meeting13:48
*** julim has joined #openstack-meeting13:49
*** mrmartin has quit IRC13:49
*** nati_ueno has joined #openstack-meeting13:50
*** dane_leblanc has joined #openstack-meeting13:51
*** SridarK_ has joined #openstack-meeting13:54
*** mtanino has quit IRC13:56
*** marun has joined #openstack-meeting13:57
*** dane_leblanc has quit IRC13:57
*** lukasa has joined #openstack-meeting13:58
*** ihrachyshka has joined #openstack-meeting13:58
mesteryhi13:59
*** dane_leblanc has joined #openstack-meeting13:59
nati_uenoHi13:59
russellbhi!13:59
swestongood morning!13:59
yamamotohi13:59
lukasahi13:59
obondarevo/13:59
*** emagana has joined #openstack-meeting13:59
HenryG\o13:59
*** markmcclain has joined #openstack-meeting13:59
marunHi14:00
markmcclainhi14:00
amotokihi14:00
*** whenry has quit IRC14:00
*** bvandenh has quit IRC14:00
ihrachyshkao/14:00
*** pc_m has joined #openstack-meeting14:00
* dougwig yawns hi14:00
* mestery hands dougwig a red bull14:00
*** mpaolino has joined #openstack-meeting14:01
*** MeganR has left #openstack-meeting14:01
*** bradjones has quit IRC14:01
*** rkukura has joined #openstack-meeting14:01
*** whenry has joined #openstack-meeting14:02
ajohi ;)14:02
rkukurahi14:02
mestery#startmeeting networking14:02
openstackMeeting started Tue Dec 16 14:02:18 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: networking)"14:02
openstackThe meeting name has been set to 'networking'14:02
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
mestery#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** zz_johnthetubagu is now known as johnthetubaguy14:02
*** erikmoe has joined #openstack-meeting14:02
mesteryThe Neutron mid-cycle was last week in Lehi, Utah.14:02
salv-orlandoaloha14:03
mesteryThanks to all who attended, I think it was very succesful and we accomplished a lot!14:03
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/052715.html Mid-cycle report14:03
*** dane_leblanc_ has joined #openstack-meeting14:03
*** dane_leblanc has quit IRC14:03
*** Riddhi has joined #openstack-meeting14:03
*** mrunge is now known as mrunge_gone14:03
*** dane_leblanc_ has quit IRC14:03
mesteryNeutron SAD was yesterday14:03
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/050958.html14:03
*** dane_leblanc_ has joined #openstack-meeting14:03
*** emagana has quit IRC14:04
mesteryThe neutron-drivers team is still pouring through some remaining specs, we had so many it's taking longer than expected14:04
mesteryI expect we'll be done with this process by the end of the week at the latest14:04
mesteryIn the meantime, I'm yak shaving LP and putting approved specs into either Kilo-2 or Kilo-3, if I've placed yours wrong, please let me know.14:05
*** bradjones has joined #openstack-meeting14:05
*** Riddhi has quit IRC14:05
*** _nadya_ has joined #openstack-meeting14:05
mesteryAlso, we've already granted a few specs an extension until Friday, so if you've gotten one, please iterate quickly on it this week14:05
mesteryAny questions on SAD or specs in general?14:05
*** lpeer_ has joined #openstack-meeting14:05
*** Riddhi has joined #openstack-meeting14:05
*** SridharG has quit IRC14:06
mesteryOne more announcement: Kilo-1 is this week14:06
mesteryI have a 1:1 with ttx after this meeting, we'll likely cut Kilo-1 Wednesday14:06
mesterySince we accomplished the services split, it will be great to have people test the tarballs and ensure things are smooth there14:07
mesteryAny other announcements for the team?14:07
*** niclem has quit IRC14:07
*** TomHoltzen has joined #openstack-meeting14:07
*** xuhanp has joined #openstack-meeting14:07
mestery#topic Bugs14:08
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:08
*** lpeer has quit IRC14:08
mesteryenikanorov enikanorov__: Hi, are you around?14:08
*** juzuluag has joined #openstack-meeting14:08
mesteryOK, in lieu of enikanorov__ enikanorov not being here, does anyone have a bug they'd like to bring up with the broader team?14:09
ihrachyshka#link https://bugs.launchpad.net/python-neutronclient/+bug/1401555 ? that's a regression in client14:09
uvirtbotLaunchpad bug 1401555 in python-neutronclient "subnet: --enable-dhcp=False/True syntax is not accepted since 2.3.5" [High,In progress]14:09
mesteryihrachyshka: Is this the one we discussed last week?14:10
ihrachyshkayes14:10
mesteryihrachyshka: I'll review this one ASAP once hte meeting concludes, I looked at the review last week already, thanks!14:10
*** niclem has joined #openstack-meeting14:11
mesteryihrachyshka: As we discussed, once this one merges, I'll roll a new version of the client and push to pypi.14:11
ihrachyshkathanks14:11
*** nshaikh has quit IRC14:11
obondarevmestery: I know enikanorov wanted to bring up https://bugs.launchpad.net/neutron/+bug/1382064 again14:11
uvirtbotLaunchpad bug 1382064 in neutron "Failure to allocate tunnel id when creating networks concurrently" [High,In progress]14:11
obondarevit showed up in https://review.openstack.org/#/c/140493/14:12
*** lintan_ has joined #openstack-meeting14:12
obondarevlast time IIRC the desision was to try make READ_COMMITED globally14:12
mesteryobondarev: I recall that discussion14:13
obondarevtrying to find that patch...14:13
marunDidn't enikanorov find that the global fix didn't work?14:13
marunAnd was working on a localized fix?14:13
*** emagana has joined #openstack-meeting14:14
marunHe didn't give any details as to why the global fix was a non-starter though.14:14
*** skraynev_ has joined #openstack-meeting14:14
*** mfedosin has joined #openstack-meeting14:14
obondarevAFAIK there were lots of lock wait timeout failures14:14
obondarevso READ_COMMITED globally seems tot to be the right way to goy14:15
obondarevgo*14:15
ihrachyshkaobondarev: was it the same with mysql-connector?14:15
obondarevihrachyshka: don't know about that14:16
obondarevso the current fix is https://review.openstack.org/#/c/129288/814:16
obondarevwhich seems working , at least here https://review.openstack.org/#/c/140493/ there are no such failures14:16
*** wznoinsk_ has joined #openstack-meeting14:17
*** lpeer_ has quit IRC14:17
*** wznoinsk_ has quit IRC14:17
mesterymarun: Looks like you've been actively reviewing these, can you work with enikanorov on a path forward here? Do you have time for that?14:18
obondarevI think the discussion may be continued on gerrit though14:18
marunCan do14:18
mesterymarun: Thanks!14:18
mesteryOK, any other bugs for the team to discuss this week?14:19
*** neeti has quit IRC14:19
lintan_I have one https://launchpad.net/bugs/138457714:19
lintan_It's about to Enable adding new tag with options14:20
*** jwang__ has joined #openstack-meeting14:20
*** BrianB__ has joined #openstack-meeting14:20
*** haleyb has joined #openstack-meeting14:20
mesterylintan_: Looking14:20
lintan_here is detail https://review.openstack.org/#/c/130498/14:20
*** markvoelker_ has joined #openstack-meeting14:21
*** ajo_ has joined #openstack-meeting14:21
mesterylintan_: Thank you for adding the unit tests to this one, I'll look at this in detial post meeting as well.14:21
*** Shohei has joined #openstack-meeting14:21
lintan_OK thanks14:22
*** bvandenh has joined #openstack-meeting14:22
*** sfineberg_ has joined #openstack-meeting14:22
matrohonI still have this bug : https://bugs.launchpad.net/neutron/+bug/136154014:22
*** yeungp1 has joined #openstack-meeting14:22
matrohon#link https://bugs.launchpad.net/neutron/+bug/136154014:22
*** daneyon has joined #openstack-meeting14:22
*** mtreinish_ has joined #openstack-meeting14:22
*** gibi_ has joined #openstack-meeting14:23
*** johnbelamaric has joined #openstack-meeting14:23
mesterymatrohon: Looks like this one is in review now, you have some comments from arosen in there too14:23
*** pelix1 has joined #openstack-meeting14:23
*** pelix has quit IRC14:23
*** doron has joined #openstack-meeting14:23
*** emagana has quit IRC14:23
*** otherjon_ has joined #openstack-meeting14:24
swestonI also have one I'd like to get some input on, I have written the unit tests for it, https://review.openstack.org/#/c/109848/14:24
matrohonmestery : yes, I'm not sure to understand his proposal...14:24
*** VW_ has joined #openstack-meeting14:24
matrohonI was haoping to find arosen here :)14:24
mesterymatrohon: I don't see arosen here, so lets sort it out either on the ML or in gerrit :)14:24
mesterysweston: Looking14:24
sweston#link https://review.openstack.org/#/c/109848/14:24
*** marcusvrn1 has joined #openstack-meeting14:25
*** VW__ has joined #openstack-meeting14:25
*** jeblair_ has joined #openstack-meeting14:25
*** changbl has quit IRC14:25
*** yalie_ has joined #openstack-meeting14:26
*** ddieterly has joined #openstack-meeting14:26
marunsweston: I'll provide some feedback post-meeting about the testing on that patch14:26
mesterymarun sweston: Thanks!14:26
*** VW__ has quit IRC14:26
*** VW___ has joined #openstack-meeting14:26
*** VW_ has quit IRC14:26
*** xuhanp_ has joined #openstack-meeting14:26
*** dane_leblanc_ has quit IRC14:26
swestonmarun mestery: excellent, thank you! this is my first unit test, so be gentle14:26
*** xyang1 has joined #openstack-meeting14:27
mesterylol14:27
marunsweston:  :)14:27
*** dane_leblanc_ has joined #openstack-meeting14:27
mesteryOK, lets move on now.14:27
mestery#topic Docs14:27
*** openstack changes topic to "Docs (Meeting topic: networking)"14:27
mesteryI'm not sure if emagana is here, but he has updated the wiki for this section14:27
*** lpeer_ has joined #openstack-meeting14:27
mesteryso I'll link some things here for the record14:27
mestery#link https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-dvr/scenario-dvr.md New networking diagram for DVR14:28
*** HenryG_ has joined #openstack-meeting14:28
mestery#link https://wiki.openstack.org/wiki/NetworkingGuide/TOC Networking Guide TOC14:28
mestery#link https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide Docs gerrit for the networking guide14:28
mestery#topic On Demand Agenda14:28
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:28
mesteryI'll encourage folks to read the pluggable devstack spec14:28
mestery#link https://review.openstack.org/#/c/137054/14:28
mesteryThis is close to landing, and will affect neutron drivers in devstack14:29
mestery#topic Services Split Update14:29
*** openstack changes topic to "Services Split Update (Meeting topic: networking)"14:29
*** absubram has joined #openstack-meeting14:29
mesterydougwig: Around?14:29
dougwigsort of.  :)14:29
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/052713.html14:29
dougwigthis is the final split update.  it should all be working now, and devstack should be happy.14:29
mesterydougwig: Want to fill folks in, or I can if the red bull hasn't kicked in ;)14:29
*** dboik has joined #openstack-meeting14:30
*** xuhanp has quit IRC14:30
*** markvoelker has quit IRC14:30
*** marcusvrn has quit IRC14:30
*** k4n0 has quit IRC14:30
*** ajo has quit IRC14:30
*** doron_afk has quit IRC14:30
*** daneyon_ has quit IRC14:30
*** yalie__ has quit IRC14:30
*** yeungp has quit IRC14:30
*** Shohei_ has quit IRC14:30
*** uvirtbot has quit IRC14:30
*** HenryG has quit IRC14:30
*** mtreinish has quit IRC14:30
*** jeblair has quit IRC14:30
*** juice has quit IRC14:30
*** mrodden has quit IRC14:30
*** jwang_ has quit IRC14:30
*** sfineberg has quit IRC14:30
*** xxj has quit IRC14:30
*** otherjon has quit IRC14:30
*** n0ano has quit IRC14:30
*** bdperkin has quit IRC14:30
*** gibi has quit IRC14:30
*** otherjon_ is now known as otherjon14:30
*** mtreinish_ is now known as mtreinish14:30
dougwigbroken 3rd party CI's, excepting vmware, should be updated as necessary.  devstack-gate CI's should've picked up changes automatically.14:30
*** juice_ has joined #openstack-meeting14:30
mestery*sigh*14:30
ihrachyshkadougwig: how about upgrade for Juno users? ;)14:30
*** juice_ is now known as juice14:30
dougwigif you've got service reviews, please re-submit against the new repos.14:30
dougwigMoving extensions, config files/items, and separating tempest tests remain and will be part of Kilo14:30
*** moha_hunt has quit IRC14:30
dougwigplease file bugs for any issues that you see at this point.14:30
*** che-arne has joined #openstack-meeting14:31
marunWhat about specs?14:31
dougwigoh, a net split.14:31
*** emagana has joined #openstack-meeting14:31
mesteryyeah, net split. meh14:31
*** dougwig has left #openstack-meeting14:31
*** che-arne|2 has quit IRC14:31
*** k4n0 has joined #openstack-meeting14:31
amotokidougwig: do we still use neutron launchpad for lbaas bugs? just a confirmation.14:31
mesteryamotoki: Yes14:32
mesteryWe have a single LP project and specs repo for all these new repos14:32
amotokithanks for the clarification14:32
mesteryAny other split questions?14:32
*** dougwig has joined #openstack-meeting14:32
ihrachyshkawhether we are going to fix upgrade before kilo-114:33
*** esker has joined #openstack-meeting14:33
ihrachyshkaI have a bug assigned to me, but probably little capacity right now14:33
ihrachyshka#link https://bugs.launchpad.net/neutron/+bug/140189514:33
dougwigihrachyshka: current plan was that driver paths must be updated in neutron.conf, and kilo-1's neutron package will include all four repo's travels.14:33
ihrachyshkaso if anyone wants to handle that before kilo-1, cool :)14:33
*** lintan_ has quit IRC14:33
dougwig /travels/tarballs/14:33
*** xxj has joined #openstack-meeting14:34
*** bdperkin has joined #openstack-meeting14:34
*** mattgriffin has joined #openstack-meeting14:34
mesteryihrachyshka: armax committed a fix for the grenade issue already?14:34
mesteryihrachyshka: Are you talking about a cleaner fix?14:34
ihrachyshkadougwig: I don't think it's anything but short-term fix. upgrade should work without messing with config files14:34
mesteryihrachyshka: Got it14:34
ihrachyshkayes, we need smooth upgrade14:34
*** lpeer_ has quit IRC14:34
mesteryihrachyshka: It's unlikely that will get fixed before Kilo-1, which is Wednesday, unless someone else jumps on this.14:34
jlibosvamestery: ihrachyshka: I volunteer14:35
*** lpeer_ has joined #openstack-meeting14:35
jlibosvaI will try to send patches today14:35
ihrachyshkajlibosva++14:35
ihrachyshkacoooool14:35
mesteryjlibosva: Awesome! Include me, armax and dougwig on the reviews please14:35
mesterythanks jlibosva!14:35
ihrachyshkame too14:35
jlibosvawill do14:35
ihrachyshkaassigning bug to Jakub14:35
dougwigthanks jlibosva14:35
*** che-arne has quit IRC14:35
mesteryGreat!14:35
mesteryAnything else services split related?14:36
pc_mmestery: grenade issue fix? Is that for the current oslo.db issue?14:36
pc_mmestery: Seeing pretty much all grenade tests failing right now.14:36
ihrachyshkapc_m: no, that's for service_provider entries requiring update after moving to split repos14:36
ihrachyshkaanother split thing:14:37
ihrachyshka#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/052972.html14:37
mesterypc_m: Link to a bug for the issue you're looking at? Or did you just see this now?14:37
salv-orlandodougwig, mestery: I hope you can forgive the vmware ci for being still broken. I only have two hands, two eyses, and one brain (well just more than half)14:37
*** jang1 has quit IRC14:37
*** kebray has quit IRC14:37
ihrachyshkaI encourage people to check whether current plan to manage oslo-incubator stuff is ok14:37
mesterysalv-orlando: lol14:37
pc_mmestery: just saw now that my (and many other commits are failing). Saw some chatter on infra this morning.14:37
dougwigsalv-orlando: no worries, i know that kobis is working on getting the vmware plugin working again as well14:37
jlibosvamestery: pc_m it's an issue with sqlalchemy version required by oslo.db, leading to swift not starting14:38
mesteryjlibosva: Thanks!14:38
jlibosvaI think https://review.openstack.org/#/c/141927/1 is the patch that is supposed to fix it14:38
mesterySince we've moved here at this point ...14:38
mestery#topic Open Discussion14:38
pc_mjlibosva: I hoipe so. Thanks!14:38
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:38
salv-orlandokobis is doing part of that yes.14:38
mestery#link https://review.openstack.org/#/c/141927/114:38
*** balajiiyer has joined #openstack-meeting14:39
*** evgenyf has joined #openstack-meeting14:39
*** jang has joined #openstack-meeting14:39
*** Masahiro has joined #openstack-meeting14:40
mesteryOK, thanks again for everyone's efforts!14:40
mesteryI encourage folks to test the Kilo-1 tarballs once they land this week from a services perspective, it will be our first time post-split to release so testing is critical.14:40
mesteryWe'll see you all on the ML and in-channel!14:40
*** lazy_prince is now known as killer_prince14:40
mestery#endmeeting14:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:40
openstackMeeting ended Tue Dec 16 14:40:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-12-16-14.02.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-12-16-14.02.txt14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-12-16-14.02.log.html14:40
salv-orlandoadieuuu14:40
nati_ueno Bye14:41
lukasao/14:41
jlibosvabye14:41
marioso/14:41
dougwigbye14:41
obondarevo/14:41
markmcclainbye14:41
ihrachyshkabye14:41
amotokibye14:41
*** pc_m has left #openstack-meeting14:41
swestono/14:41
rkukurabye14:41
*** lukasa has left #openstack-meeting14:41
marunCaio14:41
yamamotobye14:42
*** rkukura has left #openstack-meeting14:42
*** e0ne is now known as e0ne_14:43
*** ChrisPriceAB has joined #openstack-meeting14:43
*** Masahiro has quit IRC14:44
*** uvirtbot has joined #openstack-meeting14:45
*** Riddhi has quit IRC14:46
*** e0ne_ is now known as e0ne14:47
*** marun has quit IRC14:47
*** nati_ueno has quit IRC14:47
*** dane_leblanc_ has quit IRC14:48
*** yeungp1 has quit IRC14:48
*** ndipanov has quit IRC14:49
*** ndipanov has joined #openstack-meeting14:49
*** Salman_ has joined #openstack-meeting14:49
*** vhoward has left #openstack-meeting14:49
*** Riddhi has joined #openstack-meeting14:50
*** Mandell has joined #openstack-meeting14:51
*** TomHoltzen has quit IRC14:52
*** n0ano has joined #openstack-meeting14:52
*** yaguang has quit IRC14:53
*** nati_ueno has joined #openstack-meeting14:53
*** Salman_ has quit IRC14:53
*** ayoung has joined #openstack-meeting14:53
*** KLevenstein has joined #openstack-meeting14:53
*** dpaterson has joined #openstack-meeting14:55
*** carl_baldwin has joined #openstack-meeting14:56
*** mrodden has joined #openstack-meeting14:57
*** adahms has quit IRC14:57
*** che-arne has joined #openstack-meeting14:57
*** daneyon has quit IRC14:57
*** dane_leblanc has joined #openstack-meeting14:57
*** daneyon has joined #openstack-meeting14:58
*** aveiga has joined #openstack-meeting14:58
bauzastik tak tok15:00
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Dec 16 15:00:36 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
alex_xu\o15:00
* bauzas waves15:00
*** dprince has quit IRC15:00
bauzas\o15:00
*** aveiga has left #openstack-meeting15:01
edleafeo/15:01
n0anobauzas, you always beat me by about 10 seconds :-)15:01
*** dprince has joined #openstack-meeting15:01
bauzasn0ano: eh, my middle name is Tag Heuer15:01
n0anobauzas, mine is `whenever` :-)15:02
n0anoanyway, let's start15:02
*** PaulMurray has joined #openstack-meeting15:02
n0ano#topic code clean up status15:02
*** openstack changes topic to "code clean up status (Meeting topic: gantt)"15:02
PaulMurrayhi15:02
n0anoI saw you had a long IRC converstation with jaypipes , did you work everything out?15:02
bauzasby you, whose you're talking ? :)15:02
*** rbak has joined #openstack-meeting15:03
* bauzas likes long convos with jaypipes15:03
*** Mandell has quit IRC15:03
n0anoyou == bauzas , I think you were talking about the isolate scheduler DB15:03
bauzass/whose/whom (darn French !)15:03
bauzasn0ano: oh15:03
n0anobauzas, sorry, s/whom/who (I can be pedantic about grammar too)15:03
bauzasn0ano: well, everything is normal, he doesn't like my proposal, I consequently hassled him15:04
bauzasn0ano: nah, enough kidding15:04
*** neelashah has joined #openstack-meeting15:04
bauzasn0ano: so, my former proposal was about to persist aggregates information in a separate table held by the Scheduler15:04
bauzasn0ano: as I had many reviews saying it was a bad idea, I consequently changed my spec to only provide an in-memory update15:05
*** mtanino_p has joined #openstack-meeting15:05
bauzasn0ano: there are still some concerns about how to populate that cache, so I still expect further feedback15:05
* edleafe is glad he didn't update his spec for table persistence15:05
*** mtanino_p has quit IRC15:05
n0anoahh, that was the memory cache you two were talking about, is that in the updated spec I just saw the notic for?15:05
*** Mandell has joined #openstack-meeting15:05
bauzasedleafe: hence my comment to wait the aggregate spec to be at least one +2'd ;)15:05
edleafebauzas: exactly :)15:06
bauzasn0ano: correct15:06
bauzaswith the link, it's better15:06
bauzas#link https://review.openstack.org/#/c/89893/15:06
*** KLevenstein has left #openstack-meeting15:06
bauzasabove is the updated spec taking in account all previous comments15:06
*** mchalla has joined #openstack-meeting15:07
*** otter768 has joined #openstack-meeting15:07
n0anoso, definitely reviewable but sounds like you expect at least one more update on it15:07
bauzasthat's not perfect IMHO, as the Scheduler is still calling the Aggregate API once in its lifetime, but that's a good path till we split the scheduler15:07
bauzasn0ano: well, you know that the devil is in the details...15:07
bauzasanyway, I'm preparing to request an exception for the freeze if we can't make it for Thursday15:08
bauzasthat's a very old spec and still necessary for the split15:08
n0anobauzas, good plan, i'm guessing we'll need it but we should be close15:09
bauzasn0ano: yeah, the main problem is to define how to do this15:09
*** SridharRamaswamy has joined #openstack-meeting15:09
bauzasn0ano: once we agree on the plan for updating the Scheduler view and all the tradeoffs, then we can quickly iterate15:09
*** ddieterly has quit IRC15:09
alex_xubauzas, how can remove the aggregate api calling when we split scheduler?15:09
*** dkranz has quit IRC15:10
*** ddieterly has joined #openstack-meeting15:10
alex_xupull data instead of push data?15:10
bauzasalex_xu: well, that's something which can be discussed15:10
bauzasalex_xu: I wrote in the alternatives sections that it's possible to persist the dataz15:10
alex_xubauzas, ok, I will read it15:10
*** numan has joined #openstack-meeting15:11
bauzasalex_xu: but it would require a separate nova scheduler service15:11
*** absubram has quit IRC15:11
*** mchalla has quit IRC15:11
alex_xubauzas, looks like our api is push data, this won't changed15:11
bauzasanyway, that actually comes to the fact that we plan to ship first a library15:11
bauzasif we consider a library, that doesn't work well with the concept of having its own DB15:12
*** thangp has joined #openstack-meeting15:12
*** otter768 has quit IRC15:12
bauzasanyway, I think it's a bit early for discussing this - at least until this 89893 spec merges15:12
*** andreaf has quit IRC15:12
alex_xuok, think about it later15:12
bauzasbecause that spec is necessary for thinking about how we can ship the scheduler15:13
n0anobauzas, I agree, get the overall design approved and then work out the details15:13
bauzasn0ano: so, that's it for this specific BP15:13
n0anocool, tnx15:13
bauzasn0ano: that's good we targeted it for K3 anywauy15:13
bauzasbecause it seems it will probably a couple of weeks still to get it merged15:14
*** vhoward has joined #openstack-meeting15:14
n0anolooking at our dashboard, https://wiki.openstack.org/wiki/Gantt/kilo#Tasks15:14
n0anothe isolate scheduler DB is open but we have line of sight for approval,15:15
n0anojaypipes, his object model spec is the big open15:15
bauzasagreed15:15
bauzas+1 too15:15
bauzasand I have some concerns about what he's planning to do15:15
*** niclem_ has joined #openstack-meeting15:15
*** yeungp has joined #openstack-meeting15:15
n0anounfortunately, he doesn't seem to be responding today15:16
bauzasI actually required many review iterations to understand what the spec was doing, so that's my bad if I'm giving -1 so late15:16
*** yeungp has quit IRC15:16
*** yeungp has joined #openstack-meeting15:16
n0anobauzas, no worries, that's just part of the process15:16
*** shakamunyi has joined #openstack-meeting15:16
*** shakamunyi has quit IRC15:16
*** nelsnelson has joined #openstack-meeting15:17
*** jecarey has joined #openstack-meeting15:17
bauzasI'm not a logical person, that means I need sometimes more time to understand some concepts :)15:17
*** niclem has quit IRC15:17
n0anoI think I'll try and find jaypipes on IRC later and see if we can get an update on his plans for that spec15:17
*** flaper87 has quit IRC15:18
*** flaper87 has joined #openstack-meeting15:18
n0anoof course, I'm kind of avoiding the issue that now we have to implement the specs that have been approved15:18
bauzasPaulMurray: did you get updates from jaypipes about his spec ?15:18
bauzasPaulMurray: I saw you were discussing about it, even by the big G hangout stuff15:19
*** ebalduf has joined #openstack-meeting15:19
*** jcoufal_ has joined #openstack-meeting15:19
bauzassounds like we also lost PaulMurray15:19
n0anoyep (I've had network issues in the past myself)15:20
bauzasnetsplit ?15:20
n0anowe'll just have to ping jaypipes later15:20
bauzasagreed15:20
*** Riddhi has quit IRC15:20
*** SridarK_ has quit IRC15:21
n0anowe've kind of covered the specs let's move on15:21
n0ano#topic opens15:21
*** openstack changes topic to "opens (Meeting topic: gantt)"15:21
*** david-lyle has joined #openstack-meeting15:21
n0anoanything else we want to discuss today?15:21
*** jcoufal has quit IRC15:21
bauzasnothing really for me15:21
edleafenor me15:22
n0anoshort meeting works for me15:22
bauzas\o/15:22
alex_xunothing from me15:22
n0anowe still have reviews so let's all do that15:22
edleafesounds like a plan15:22
*** madskier has joined #openstack-meeting15:22
n0anoBTW, I'll be around next week (big holiday coming up I hear) do we still want a meeting next week?15:22
bauzasn0ano: oh good point15:23
edleafeI'll be around15:23
bauzaslemme check the date15:23
*** dkranz has joined #openstack-meeting15:23
edleafebut yeah, a lot of people will be off15:23
bauzassounds feasible15:23
n0anoChristmas day is Thurs so Tues is fine by me15:23
* n0ano has all his shopping done for the first time ever15:23
bauzasI should be off by end of Tues till 5th Jan15:24
n0anobauzas, NP, enjoy, I'll still run a meeting next week, it could be `very` short15:24
bauzasn0ano: ack15:24
*** stevemar has joined #openstack-meeting15:24
PaulMurraybauzas, I was pulled into something by my manager - I can update at the end if you like15:24
*** BrianB__ has quit IRC15:24
*** BrianB__ has joined #openstack-meeting15:24
n0anoPaulMurray, go for it15:24
*** pelix1 has quit IRC15:25
*** pelix1 has joined #openstack-meeting15:25
*** doron has quit IRC15:25
*** doron has joined #openstack-meeting15:25
*** yalie_ has quit IRC15:25
*** yalie_ has joined #openstack-meeting15:25
*** VW___ has quit IRC15:25
*** VW___ has joined #openstack-meeting15:25
*** HenryG_ has quit IRC15:25
*** HenryG_ has joined #openstack-meeting15:25
*** dboik has quit IRC15:25
*** dboik has joined #openstack-meeting15:25
*** PaulMurray has quit IRC15:25
*** PaulMurray has joined #openstack-meeting15:25
*** k4n0 has quit IRC15:25
*** k4n0 has joined #openstack-meeting15:25
*** ebalduf has quit IRC15:25
*** ChrisPriceAB has quit IRC15:25
*** ChrisPriceAB has joined #openstack-meeting15:25
PaulMurraybauzas, ok15:25
*** ndipanov has quit IRC15:25
*** ndipanov has joined #openstack-meeting15:25
*** ayoung has quit IRC15:25
*** ayoung has joined #openstack-meeting15:25
*** che-arne has quit IRC15:25
*** che-arne has joined #openstack-meeting15:25
*** dane_leblanc has quit IRC15:25
*** dane_leblanc has joined #openstack-meeting15:25
*** neelashah has quit IRC15:25
*** neelashah has joined #openstack-meeting15:25
*** madskier has quit IRC15:25
PaulMurrayI have a discussion with jaypipes about his spec for resource object models15:25
*** yeungp has quit IRC15:25
*** yeungp has joined #openstack-meeting15:25
bauzasright15:26
*** jecarey has quit IRC15:26
*** jecarey has joined #openstack-meeting15:26
PaulMurrayThe basic point was making sure that two things are covered that were requirements for ERT15:26
*** jcoufal_ has quit IRC15:26
*** jcoufal_ has joined #openstack-meeting15:26
*** dkranz has quit IRC15:26
*** dkranz has joined #openstack-meeting15:26
*** amitry has quit IRC15:26
PaulMurray1) ability to select resources for different virt drivers15:26
PaulMurray2) making sure it is easy to develop and contribute new resource objects15:26
PaulMurrayI also noted a bug in the resource tracker to do with ironic15:27
n0anoPaulMurray, good goals, I approve15:27
PaulMurrayIronic uses resources differently to other virt drivers15:27
PaulMurrayand that is not accounted for at the moment15:27
*** xuhanp has joined #openstack-meeting15:27
bauzasPaulMurray: I agree, I had many troubles with Ironic when implement detach-service15:27
PaulMurrayso this is an opportunity to make sure those kind of things are easy to deal with in the future15:28
PaulMurrayI can find the link for the bug - hold on15:28
*** yamamoto has quit IRC15:28
PaulMurrayhttps://bugs.launchpad.net/nova/+bug/140265815:28
uvirtbotLaunchpad bug 1402658 in nova "resource tracking is incorrect for ironic" [Undecided,New]15:29
*** doron has quit IRC15:29
*** yamamoto has joined #openstack-meeting15:29
*** afazekas has joined #openstack-meeting15:29
*** aranjan has joined #openstack-meeting15:29
PaulMurrayThat can be dealt with as a bug fix, but dealing with resources that behave differently should be inherent in the solution15:29
*** afazekas is now known as afazekas_pto15:29
PaulMurrayAnyway - Jay is going to do a revision to day I think15:29
*** IlyaE has joined #openstack-meeting15:30
*** prazumovsky has joined #openstack-meeting15:30
*** IlyaE has quit IRC15:30
bauzasPaulMurray: I was also having some concerns about how he's planning to update the stats15:30
bauzasPaulMurray: IIUC, he was planning to update the UsageSpec classes, but not the ComputeNode object15:31
*** ebalduf has joined #openstack-meeting15:31
PaulMurraybauzas, I got a little lost on that part - I need to get more familiar with the proposed code15:31
n0anobauzas, as long as you indicate that in your review that should make jaypipes address those issues15:32
bauzasPaulMurray: I think that's the main problem I had15:32
*** madskier has joined #openstack-meeting15:32
*** erlon has joined #openstack-meeting15:32
bauzasPaulMurray: I was a little lost of what was the actual plan15:32
*** xuhanp_ has quit IRC15:32
bauzasbut let's jaypipes clarify that in his spec15:33
PaulMurraybauzas, I know that some of it looks confused because it deals with legacy around the ComputeNode object15:33
bauzasPaulMurray: my main problem is that there are many set of classes and I was still having some problems with seeing the relationship with the ComputeNode object15:34
*** ebalduf_ has joined #openstack-meeting15:34
*** aranjan has quit IRC15:34
PaulMurraybauzas, I'm not sure its done cleanly enough yet, but the path from legacy to being clean is not quite there for me15:34
bauzasPaulMurray: agreed15:34
PaulMurrayhence my concerns about ease of use15:34
*** mpaolino has quit IRC15:34
PaulMurrayor rather ease of extension15:34
bauzasPaulMurray: yeah, I just want to make sure it's quite understandable and readable by most of us15:34
n0anoI'm concerned about timing, even with an extension we don't have much time to get this right15:34
PaulMurrayn0ano, yes, I said would make myself available to help get it right15:35
*** ebalduf has quit IRC15:35
n0anoPaulMurray, tnx, anything to help15:35
PaulMurrayn0ano, it might need a restricted scope and a statement about where it intends to go15:35
PaulMurrayn0ano, can't really say much in jaypipes absense15:36
*** yamamoto has quit IRC15:36
n0anoyeah, understood, we'll try and get him later on IRC15:36
*** ItSANgo_ has quit IRC15:36
bauzasagreed15:36
n0anoso, unless there's anything else15:36
n0anoI'll thank everyone and we'll talk again next week15:37
*** madskier has quit IRC15:37
bauzassure thing15:37
n0ano#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
openstackMeeting ended Tue Dec 16 15:37:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-12-16-15.00.html15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-12-16-15.00.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-12-16-15.00.log.html15:37
*** sbalukoff has quit IRC15:37
*** PaulMurray has left #openstack-meeting15:37
*** jtomasek has quit IRC15:39
*** dulek has quit IRC15:40
*** emagana has quit IRC15:41
*** xuhanp has left #openstack-meeting15:41
*** ebalduf_ has quit IRC15:42
*** matiu has quit IRC15:42
*** mpaolino has joined #openstack-meeting15:43
*** phil__ has quit IRC15:43
*** sicarie has joined #openstack-meeting15:44
*** mpaolino has quit IRC15:44
*** vijendar has joined #openstack-meeting15:45
*** mpaolino has joined #openstack-meeting15:45
*** Riddhi has joined #openstack-meeting15:46
*** gmatefi has joined #openstack-meeting15:48
*** carl_baldwin has quit IRC15:49
*** chandankumar has joined #openstack-meeting15:51
*** david-lyle has quit IRC15:52
*** penick has joined #openstack-meeting15:53
*** SridharRamaswamy has quit IRC15:54
*** balajiiyer has left #openstack-meeting15:55
*** Mandell has quit IRC15:56
*** numan has quit IRC15:56
*** topol has joined #openstack-meeting15:56
*** reed has joined #openstack-meeting15:57
*** achanda has joined #openstack-meeting15:57
*** gholler has joined #openstack-meeting15:58
*** jtomasek has joined #openstack-meeting15:59
*** sergef has quit IRC15:59
*** nati_ueno has quit IRC16:00
*** B_Smith has joined #openstack-meeting16:00
*** MeganR has joined #openstack-meeting16:00
*** marrusl has quit IRC16:00
*** markmcclain has quit IRC16:00
*** sergef has joined #openstack-meeting16:00
*** dane_leblanc has quit IRC16:01
*** sballe has joined #openstack-meeting16:01
*** dane_leblanc has joined #openstack-meeting16:01
*** emagana has joined #openstack-meeting16:01
*** timello_ is now known as timello16:02
*** johnbelamaric has left #openstack-meeting16:05
*** isviridov is now known as isviridov_away16:05
*** achanda has quit IRC16:05
*** erikmoe has quit IRC16:06
*** tbarron has joined #openstack-meeting16:07
*** kebray has joined #openstack-meeting16:08
*** ItSANgo has joined #openstack-meeting16:09
*** chandankumar has quit IRC16:10
*** aepifanov has quit IRC16:15
*** achanda has joined #openstack-meeting16:15
*** jmontemayor has joined #openstack-meeting16:15
*** gmatefi has quit IRC16:16
*** dannywilson has joined #openstack-meeting16:16
*** ityaptin has quit IRC16:17
*** msdubov_ has joined #openstack-meeting16:17
*** rushiagr is now known as rushiagr_away16:18
*** dannywil_ has joined #openstack-meeting16:18
*** hashar has quit IRC16:19
*** dannywilson has quit IRC16:20
*** ihrachyshka has quit IRC16:20
*** jprovazn has joined #openstack-meeting16:20
*** mdenny has joined #openstack-meeting16:21
*** niclem has joined #openstack-meeting16:21
*** penick has quit IRC16:21
*** niclem_ has quit IRC16:22
*** dannywil_ has quit IRC16:23
*** dannywilson has joined #openstack-meeting16:24
*** samuelms-away is now known as samuelms16:25
*** lsmola has quit IRC16:26
*** kragniz is now known as kragwhale16:26
*** pelix1 is now known as pelix16:27
*** ndipanov has quit IRC16:28
*** aloga has quit IRC16:28
*** Masahiro has joined #openstack-meeting16:29
*** ndipanov has joined #openstack-meeting16:29
*** david-lyle has joined #openstack-meeting16:30
*** Apoorva has joined #openstack-meeting16:30
*** jdurgin1 has joined #openstack-meeting16:31
*** shankar has quit IRC16:32
*** matrohon has quit IRC16:32
*** david-lyle has quit IRC16:33
*** chandankumar has joined #openstack-meeting16:34
*** Masahiro has quit IRC16:34
*** EmilienM is now known as EmilienM|afk16:34
*** pballand has joined #openstack-meeting16:35
*** dwalleck has joined #openstack-meeting16:35
*** sergef has quit IRC16:35
*** yamamoto has joined #openstack-meeting16:36
*** reed has quit IRC16:36
*** reed has joined #openstack-meeting16:37
*** MarkAtwood has joined #openstack-meeting16:37
*** alex_xu has quit IRC16:38
*** vishwanathj has joined #openstack-meeting16:39
*** skraynev_ has quit IRC16:41
*** yamamoto has quit IRC16:41
*** IanGovett has quit IRC16:42
*** noelbk has joined #openstack-meeting16:43
*** prazumovsky has quit IRC16:43
*** david-lyle_afk is now known as david-lyle16:44
*** andreaf has joined #openstack-meeting16:45
*** aloga has joined #openstack-meeting16:45
*** scinawa has joined #openstack-meeting16:46
*** bvandenh has quit IRC16:46
*** VW___ has quit IRC16:47
*** ajiang has joined #openstack-meeting16:48
*** anish_ has joined #openstack-meeting16:48
*** VW_ has joined #openstack-meeting16:49
*** changbl has joined #openstack-meeting16:49
*** IanGovett has joined #openstack-meeting16:50
*** vigneshvar has joined #openstack-meeting16:51
*** chandankumar has quit IRC16:51
*** mrmartin has joined #openstack-meeting16:52
*** zeddii is now known as ddez16:53
*** ddez is now known as zeddii16:53
*** e0ne is now known as e0ne_16:53
*** alop has joined #openstack-meeting16:53
*** e0ne_ is now known as e0ne16:53
*** alop has quit IRC16:54
*** niclem has quit IRC16:54
*** ebalduf has joined #openstack-meeting16:54
*** alop has joined #openstack-meeting16:54
*** comay has joined #openstack-meeting16:55
*** alexpilotti has quit IRC16:55
*** rm_work|away is now known as rm_work16:55
*** MaxV has quit IRC16:56
*** niclem has joined #openstack-meeting16:57
*** dane_leblanc_ has joined #openstack-meeting16:58
*** amaretskiy has joined #openstack-meeting16:58
*** markmcclain has joined #openstack-meeting16:58
*** olkonami has joined #openstack-meeting16:58
*** garyk has quit IRC16:58
*** sarob has joined #openstack-meeting16:59
*** ebalduf has quit IRC16:59
*** ajiang38740_ has joined #openstack-meeting17:00
*** rvasilets has joined #openstack-meeting17:00
msdubov_#startmeeting Rally17:01
openstackMeeting started Tue Dec 16 17:01:01 2014 UTC and is due to finish in 60 minutes.  The chair is msdubov_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: Rally)"17:01
openstackThe meeting name has been set to 'rally'17:01
msdubov_rediskin rvasilets amaretskiy olkonami k4n0 oanufriev Good evening17:01
amaretskiyhi17:01
rvasiletsHi17:01
oanufrievhi17:01
*** dane_leblanc has quit IRC17:02
*** egallen has quit IRC17:02
olkonamihi17:02
*** MeganR has left #openstack-meeting17:02
*** vijendar1 has joined #openstack-meeting17:03
msdubov_Let's start!17:03
*** thomasem has joined #openstack-meeting17:03
msdubov_#topic NetworkContext17:03
*** openstack changes topic to "NetworkContext (Meeting topic: Rally)"17:03
msdubov_amaretskiy How are things with it, can we expect it being merged today/tommorow?17:03
msdubov_amaretskiy Sorry for still not reviewing it :)17:04
*** hashar has joined #openstack-meeting17:04
amaretskiywe have a working patch, but there are some changes requested by reviewers17:04
amaretskiyi hope we can merge in this week17:04
*** _sunil has joined #openstack-meeting17:04
amaretskiy*it17:05
amaretskiyeom17:05
*** rushiagr_away is now known as rushiagr17:05
*** vijendar has quit IRC17:06
*** kebray has quit IRC17:06
*** ygbo has quit IRC17:06
*** jlanoux has quit IRC17:06
*** ChuckC_ has joined #openstack-meeting17:06
*** kebray has joined #openstack-meeting17:07
*** ChuckC has quit IRC17:07
*** msdubov_ has quit IRC17:07
*** otter768 has joined #openstack-meeting17:08
*** msdubov_ has joined #openstack-meeting17:08
*** sarob has quit IRC17:08
msdubov_Sorry I got disconnected17:08
*** evgenyf has quit IRC17:09
*** sweston is now known as _sweston17:09
msdubov_#topic Tenant resources refactoring in context17:09
*** openstack changes topic to "Tenant resources refactoring in context (Meeting topic: Rally)"17:09
msdubov_oanufriev Hi, please tell us what you've done here, and why this refactoring step was important17:10
*** nellysmitt has quit IRC17:10
oanufrievso17:10
*** hareeshp has joined #openstack-meeting17:10
*** sarob has joined #openstack-meeting17:11
*** BharatK has quit IRC17:11
oanufrievbefore this change resources in context were look like context[resource_name][tenant_id][some_useful_thing]17:11
*** carl_baldwin has joined #openstack-meeting17:12
*** otter768 has quit IRC17:12
*** leeantho has joined #openstack-meeting17:12
*** markmcclain1 has joined #openstack-meeting17:12
oanufrievthat was difficult to search valid resource item for current context (usually that was implemented in for cycle)...17:13
*** markmcclain has quit IRC17:13
oanufrieveither, we had to pass whole context[resource] tree to every process and thread17:14
*** vigneshvar has quit IRC17:14
msdubov_oanufriev, Okay, so a nice improvement really17:14
oanufrievnow it looks like context[tenants][tenant_id][resource_name][some_useful_thing]17:15
*** sweston has joined #openstack-meeting17:15
*** sbalukoff has joined #openstack-meeting17:15
*** hemna has joined #openstack-meeting17:15
*** rmoe has quit IRC17:16
msdubov_oanufriev Anything to add?17:16
oanufrievand we pass only resources related to actual tenant which saves memory and simpler to map resource to current tenant17:17
*** dsetia has joined #openstack-meeting17:17
*** enikanorov has quit IRC17:17
msdubov_oanufriev Okay, thanks. Let's move further17:17
oanufrievEOF17:17
msdubov_#topic Scenario runners refactoring17:18
*** openstack changes topic to "Scenario runners refactoring (Meeting topic: Rally)"17:18
*** mtanino has joined #openstack-meeting17:18
msdubov_olkonami Could you please tell us what is your task here and what is your progress so far?17:18
*** dsetia has quit IRC17:19
*** ChuckC_ has quit IRC17:19
*** dsetia has joined #openstack-meeting17:19
*** ivar-lazzaro has joined #openstack-meeting17:20
*** ndipanov has quit IRC17:20
olkonaminow I am working on improvement constant runner - refactor it like it done in rpc to start processes count according to cpu count and then use threads into the processes17:20
*** achanda has quit IRC17:21
olkonamithe first step is take out general logic from rpc runner to some base class17:22
*** bvandenh has joined #openstack-meeting17:22
*** carl_baldwin has quit IRC17:22
*** sarob has quit IRC17:23
*** dims has quit IRC17:23
*** sarob_ has joined #openstack-meeting17:23
*** dims has joined #openstack-meeting17:23
*** yamamoto has joined #openstack-meeting17:24
olkonaminow I am working on it, but I didn't have anything to show now, I'm just in process to understend how rewrite code to make it reusable17:24
*** daneyon_ has joined #openstack-meeting17:24
*** hareeshp has quit IRC17:24
*** achanda_ has joined #openstack-meeting17:24
*** dwalleck has quit IRC17:24
*** niclem has quit IRC17:25
*** niclem has joined #openstack-meeting17:25
msdubov_olkonami Okay, thanks. Sound like a plan, hope you get it soon17:25
*** mudassirlatif has joined #openstack-meeting17:26
*** colinmcnamara has joined #openstack-meeting17:27
*** daneyon has quit IRC17:27
*** derekh has quit IRC17:27
*** shashankhegde has joined #openstack-meeting17:27
*** sarob_ is now known as sarob17:27
*** alexpilotti has joined #openstack-meeting17:27
*** jcoufal_ has quit IRC17:27
*** dims_ has joined #openstack-meeting17:28
*** achanda_ has quit IRC17:28
*** dims has quit IRC17:28
*** sarob_ has joined #openstack-meeting17:29
*** achanda has joined #openstack-meeting17:29
msdubov_#topic Murano benchmarks17:29
*** openstack changes topic to "Murano benchmarks (Meeting topic: Rally)"17:29
msdubov_rvasilets Thanks for taking this patch, how was your progress with it today?17:29
*** rwsu has joined #openstack-meeting17:29
msdubov_#link https://review.openstack.org/#/c/137650/17:29
rvasiletsI have Rebased patch https://review.openstack.org/#/c/137650/ and I think it's ready for review17:30
*** tsekiyama has joined #openstack-meeting17:30
*** ihrachyshka has joined #openstack-meeting17:30
rvasiletsThis patch is added murano context and murano client to osclient17:31
*** rmoe has joined #openstack-meeting17:32
*** yamamoto has quit IRC17:32
rvasiletsAlso thare is added python client validation17:32
*** sarob has quit IRC17:32
rvasiletseom17:32
msdubov_rvasilets, Thanks!17:32
*** marun has joined #openstack-meeting17:32
*** marcusvrn1 has quit IRC17:33
msdubov_#topic New decorator syntax in Rally (samples, deprecated stuff)17:33
*** openstack changes topic to "New decorator syntax in Rally (samples, deprecated stuff) (Meeting topic: Rally)"17:33
*** bdpayne has joined #openstack-meeting17:33
*** ndipanov has joined #openstack-meeting17:33
*** achanda has quit IRC17:33
msdubov_oanufriev, olkonami, Any updates on this?17:33
*** vigneshvar has joined #openstack-meeting17:33
*** IanGovett has quit IRC17:33
oanufrievI'm working on 'sample' decorator17:34
oanufrievhere https://review.openstack.org/#/c/140033/17:34
oanufrievfor now it's working, but only 2 items are decorated17:35
*** carl_baldwin has joined #openstack-meeting17:35
oanufrieveom17:35
*** zeddii has quit IRC17:36
*** safchain has quit IRC17:36
olkonamimsdubov, I realized deprecated reason, but haven't fix your last comments yet17:36
*** _nadya_ has quit IRC17:37
*** garyk has joined #openstack-meeting17:37
*** padkrish has joined #openstack-meeting17:37
msdubov_Okay17:37
msdubov_#topic Rally documentations17:38
*** openstack changes topic to "Rally documentations (Meeting topic: Rally)"17:38
olkonamibecose boris-42 said there are too many copy-pasting in that code and it should be rewrited17:38
boris-42olkonami: yep17:38
*** zeddii has joined #openstack-meeting17:38
boris-42olkonami: i will make advices today a bit latter17:38
msdubov_So two quick updates from my side17:39
olkonamiboris-42, ok, wait for any proposals from you17:39
*** Fdot has quit IRC17:39
msdubov_1. Patch with Rally docstrings is on review, but it will be merged after NetworkContext17:39
*** andreaf has quit IRC17:40
msdubov_2. Currently working on Rally ReadTheDocs, hoping to simplify the overall structure of our docs and also rewrite a bit the tutorial so that it treats first really simple examples and then moves to more involved ones17:40
*** andreaf has joined #openstack-meeting17:40
msdubov_#topic Free discussion17:40
*** openstack changes topic to "Free discussion (Meeting topic: Rally)"17:40
msdubov_boris-42 rediskin rvasilets amaretskiy olkonami k4n0 oanufriev Anything to add?17:40
*** aranjan has joined #openstack-meeting17:40
amaretskiynothing from my side17:41
*** Haneef has joined #openstack-meeting17:41
*** jdurgin1 has quit IRC17:41
rediskinnope17:41
oanufrievno17:41
rvasiletsno17:41
*** IanGovett has joined #openstack-meeting17:42
*** elo has quit IRC17:43
*** kragwhale is now known as kragniz17:43
*** s3wong has joined #openstack-meeting17:44
*** armax has joined #openstack-meeting17:45
msdubov_Okay thanks to all17:45
msdubov_#endmeeting17:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:46
openstackMeeting ended Tue Dec 16 17:46:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-12-16-17.01.html17:46
*** amaretskiy has left #openstack-meeting17:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-12-16-17.01.txt17:46
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-12-16-17.01.log.html17:46
*** rvasilets has left #openstack-meeting17:46
*** olkonami has left #openstack-meeting17:46
*** ChuckC_ has joined #openstack-meeting17:47
*** e0ne has quit IRC17:50
*** padkrish has quit IRC17:51
*** dwalleck has joined #openstack-meeting17:52
*** lhcheng_ has joined #openstack-meeting17:53
*** ChuckC_ has quit IRC17:54
*** marcusvrn has joined #openstack-meeting17:54
*** zeddii is now known as ddez17:55
*** sarob_ is now known as sarob17:55
*** ddez is now known as zeddii17:55
*** shashankhegde has quit IRC17:55
*** shashankhegde has joined #openstack-meeting17:56
*** achanda has joined #openstack-meeting17:56
*** breton has joined #openstack-meeting17:56
*** ChuckC_ has joined #openstack-meeting17:56
*** shashankhegde has quit IRC17:57
*** padkrish_ has joined #openstack-meeting17:57
*** elo has joined #openstack-meeting17:57
*** amakarov has joined #openstack-meeting17:58
*** mchalla has joined #openstack-meeting17:58
*** henrynash has joined #openstack-meeting17:59
stevemaro/17:59
bretongood evening18:00
morganfainbergsoooo18:00
*** lhcheng_ is now known as lhcheng18:00
stevemarmorganfainberg, soooo18:00
morganfainbergdolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods, amakarov, ajayaa, hogepodge, breton, lhcheng, nonameentername, samuelms, htruta18:00
morganfainberghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
raildoo/18:01
bknudsonhi18:01
*** dwalleck has quit IRC18:01
henrynashzipedee doodah...18:01
rharwoodhallo18:01
*** nkinder has joined #openstack-meeting18:01
morganfainbergthat list gets longer and longer each week i think18:01
rodrigodso/18:01
lhchengo/18:01
*** mchalla_ has joined #openstack-meeting18:01
samuelms\o18:01
nkindero/18:01
dstaneko/18:01
stevemarahoy18:01
ayoungHey Ho Lets go!18:01
henrynash\o/18:01
morganfainberg#startmeeting Keystone18:01
openstackMeeting started Tue Dec 16 18:01:47 2014 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. 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
gabriel-bezerrao/18:01
raildoayoung, \,,,/18:01
* morganfainberg resists urge to startmeeting keystoners18:01
*** garyk has quit IRC18:02
morganfainberg#topic Kilo-1 on Dec 1818:02
*** openstack changes topic to "Kilo-1 on Dec 18 (Meeting topic: Keystone)"18:02
morganfainbergthats right, in a couple days18:02
morganfainbergk1 will be cut18:02
morganfainbergwe're very close, 3-4 outstanding bugs that are actively being worked on18:02
morganfainberg#link https://launchpad.net/keystone/+milestone/kilo-118:02
morganfainbergmake sure we get reviews on them, lets get them in by tomorrow so ttx can cut k1 keystone for us!18:03
lbragstado/18:03
*** suro_ has joined #openstack-meeting18:03
morganfainberg#topic Review Specs18:03
*** openstack changes topic to "Review Specs (Meeting topic: Keystone)"18:03
*** garyk has joined #openstack-meeting18:03
morganfainberg#link https://review.openstack.org/#/q/status:open+project:openstack/keystone-specs,n,z18:03
*** kebray has quit IRC18:03
morganfainbergreminder, specs have a hard dealine of k218:03
*** hashar has quit IRC18:03
morganfainberganything comeing in post k2 will need an explicit exception granted18:04
*** egallen has joined #openstack-meeting18:04
*** jeblair_ is now known as jeblair18:04
amakarovhi!18:04
morganfainbergnow that the house keeping is out of the way18:04
morganfainberg#topic Dynamic Policy Specs18:04
*** openstack changes topic to "Dynamic Policy Specs (Meeting topic: Keystone)"18:04
morganfainbergayoung, o/18:04
*** comay has quit IRC18:04
ayoungAh18:04
*** mchalla has quit IRC18:04
*** penick has joined #openstack-meeting18:04
nonameenternameo/18:04
henrynashthe man of many specs....18:05
ayoungOK...so I wanted to make sure people understood the concept18:05
ayoungthe many specs are the result of tryung to break it down to consumable concepts18:05
ayoungso...18:05
henrynashayoung: ++18:05
ayoungWe've got the ball rolling by promoting policy to an oslo library18:05
*** mchalla_ has quit IRC18:06
*** k4n0 has quit IRC18:06
samuelmsrodrigods, o/18:06
ayoungthere is some confusion over that and the next one: enforce policy in a library18:06
ayoungand there is somet question about where that should live18:06
*** mchalla has joined #openstack-meeting18:06
ayoungI recently posted a refactoring of the keystone code that shows the difference in intention, though, between the oslo stuff and this18:06
henrynashayoung: you mean where the actualy code taht calles the policy engine lives?18:06
rodrigodsregarding the policy lib, the repo is here https://github.com/rodrigods/oslo.policy18:06
ayoungthe distinction is that the oslo policy library is a rules engine, and not keystone specific18:07
rodrigodsthe spec is in the meeting wiki18:07
morganfainbergayoung, as it should be.18:07
ayoungso while it is "necessary" it is not "sufficient"18:07
ayoungthe next step is to common-ize the code for enforcing policy from a server...and to make sure that keystone is not treated differently than the other services18:07
ayoungok,  so I post this today:18:07
ayounghttps://review.openstack.org/#/c/141969/   policy refactoring18:08
*** jamielennox has joined #openstack-meeting18:08
ayoungit is still inside the keystone server  but the code that is pulled into authorize.py needs to be made available to a wider audience:  either KC or middleware18:08
topolo/18:09
ayoungthere needs to be more cleanup on this code before that happens, too, as there is a lot of duplication18:09
*** msdubov_ has quit IRC18:09
jamielennoxo/18:09
*** aloga has quit IRC18:09
ayounghenrynash, so to address your question : yes, where the actually code that calls the policy engine lives?18:10
ayounger.. ? -> .18:10
henrynashayoung: lookd the right approach to me18:10
*** marcoemorais has joined #openstack-meeting18:10
henrynashayoung: and, yes, that code could do with some cleanup :-)18:10
ayounghenrynash, to be more specific, to standardize how we pull values out of the token and enforce policy on them18:10
ayoung++18:10
*** ebalduf has joined #openstack-meeting18:10
ayoungnow, raildo samuelms and company have been working on the actual policy files themselves in a parallel effort18:11
*** comay has joined #openstack-meeting18:11
jamielennoxI would like a certain amount of that code to live inside the upcoming oslo.policy library18:11
henrynashayoungL so feel free to lean on my for reviews of that stuff18:11
ayoungjamielennox, yeah, I think that there will be logicial splits in the code, and anything that is common to all rules engines would move to oslo.policy18:11
*** afaranha has joined #openstack-meeting18:12
jamielennoxspecifically the object that i pass out of auth_token middleware i want people to pass directly to oslo.policy so that essentially keystone controls "ends" of the information required to enforce policy18:12
ayounghenrynash, will do. and I think you and I are on the same course,  but from different starting points18:12
henrynashayoung: ++18:12
*** achanda has quit IRC18:12
jamielennoxboth "ends"18:12
*** harlowja_away is now known as harlowja18:12
ayoungjamielennox,   OK, I think we are on the same page18:12
morganfainbergjamielennox, that makes sense to me.18:12
*** dwalleck has joined #openstack-meeting18:12
morganfainbergayoung, i haven't seen anything that looks wildly off in the weeds being proposed here.18:13
*** achanda has joined #openstack-meeting18:13
ayoungin order to enforce policy, we want to standardize the auth context.  that starts with the token, but then goes on18:13
morganfainbergor anything that surprised me, mostly what we've discussed summit and up to this point :)18:13
jamielennox(this may not be new ground i just only caught the last part of the conversation)18:13
ayoungI first rewrote it in the keystone server, but moved the rewrite to the KC code:18:13
morganfainbergjamielennox, you caught on very early in the conv.18:13
ayounghttps://review.openstack.org/#/c/138519/  is the "Access Info" and is based on design guidance from morganfainberg18:14
*** openstac_ has joined #openstack-meeting18:14
ayoungI happen to really like his guidance18:14
*** achanda has quit IRC18:14
*** achanda has joined #openstack-meeting18:14
ayoungit is a type of coding that some might find odd, but it enforces, as much as possible, that we have the right "types" for enforcing the policy18:14
ayoungthat review has a wider implication18:14
ayoungit is also to be used in building the token18:15
ayoungand will be part of morganfainberg 's effort to clean up the token provider18:15
morganfainbergayoung, and that code is a bit easier to read than using python descriptors18:15
ayoungits rally the hear of the data as managed by Keystone18:15
ayoungreally18:15
ayoungreally the heart18:15
morganfainbergayoung, which is likely what i would have tried to use (easier to read = better in this case)18:15
ayoungone goal is to be able to make a call into keystone without a token, build up an AccessInfo object, and use it to enforce policy for tokenless operations18:16
ayoungthat should make gyee happy...18:16
*** sahid has quit IRC18:16
*** jrist has quit IRC18:16
ayoungok...so that is all rfactoring, no new behavior yet18:16
ayoungon to new behavior18:16
*** anish_ has quit IRC18:17
ayoungonce the endpoints can agree on how to enforce policy, we want them to be able to get their policy files from the keystone server18:17
ayoungthuis has been on the roadmap for years18:17
*** amitry has joined #openstack-meeting18:17
*** Masahiro has joined #openstack-meeting18:17
topolwhy would they need to agree on how to enforce policy?18:17
*** ksavich_ has joined #openstack-meeting18:18
ayoungthe policy API as origianly specified was lackignthe ability to fetch the "right"policy file until henrynash got the endpoint stuff working18:18
ayoungtopol, good question, lets make it explicit18:18
*** s3wong_ has joined #openstack-meeting18:18
*** s3wong has quit IRC18:18
*** s3wong_ has quit IRC18:18
ayoungtopol, the policy mechanism is really RBAC18:18
ayoungand RBAC is an engineering effort to simpligfy access control18:18
*** s3wong has joined #openstack-meeting18:18
dolphmayoung: what's the value of enforcing authorization on unauthenticated calls?18:18
topolall true18:18
ayoungwe've made it a point that all of openstack shares the token infra18:18
ayoungdolphm, good point...I'll come back to that18:19
ayoungtopol, so we want to make sure that a role is a reusable concept across two or more services18:19
morganfainbergdolphm, thanks for asking, i actually was going to ask that.18:19
ayoungwe've seen the abuse of "is admin"18:19
ayoungwhat we want is to have agreement on what it means to have a role18:20
topolayoung, so  the interesting question is how much if any policy re-work the projects *must* do as opposed to this is a better option should you choose to leverage it?18:20
ayoungtopol, so, one thing dolphm showed me last year is thathe policy approach was designed such that we could have  single policuy file for all known enforcement points18:20
ayoungtopol, the goal is to minimize the amount of work18:21
bknudsonI don't think the other projects want to think about policy, so if we propose something they would be happy18:21
lbragstad++18:21
topolayoung, agreed.  Im tweaking your sales pitch18:21
*** markmcclain1 has quit IRC18:21
ayoungand to get it so that instead we identify the assumptions that they are building into their policy enforcement, and either incorporate those assumptions or remove them as appropriate18:21
topolbknudson++18:21
ayoungyeah...glad to make this explicit18:21
*** joesavak has joined #openstack-meeting18:21
*** s3wong has quit IRC18:21
*** markmcclain has joined #openstack-meeting18:21
ayoungok,  dolphm back to your question18:21
morganfainbergbknudson, i know no other projects want to think about policy18:21
ayoungI would not say "unauthenticated" calls are what I want here18:21
morganfainbergbknudson, well... except one but that doesn't count.18:21
ayoungI want to enforce policy on calls without gettnig a token first, but that are authenticated somehow18:22
ayoungthe most common need is for long term agreements with services18:22
topolTo sell this we need to deliver free gifts to the other projects. That being the better way of how to do policy. If they have to figure it out on their own you wont get traction18:22
*** Masahiro has quit IRC18:22
morganfainbergayoung, in what context? on endpoints or just to keystone?18:22
ayoungfor example, when Nova etc does a token validation, they need to first get a token themselves, which is a second round trip18:22
morganfainbergtopol, if it just works or requires minor tweaks thats a pretty easy sell i think.18:22
*** shashankhegde has joined #openstack-meeting18:23
morganfainbergayoung, ok so just when interacting with keystone18:23
*** b0d0nne11 has joined #openstack-meeting18:23
morganfainbergnot a user talking to nova18:23
lbragstadPolicy-Management-as-a-Gift?18:23
ayoungmorganfainberg, yeah,18:23
bknudsonnova only gets a token when its old token is expiring.18:23
bknudsonor has expired.18:23
ayoungbknudson, right18:23
henrynashlbradstad: it is Christmas, after all18:23
morganfainbergbknudson, he's saying we should allow something like x509 for that18:23
topolayoung, why this extra hoop? Sounds scary.  Why not just say you can now pull your policy from keystone and we have a better sample for you to consider for your policy file.?18:23
ayoungyep18:23
*** ChuckC_ is now known as ChuckC18:23
morganfainbergbknudson, rather than needing a username/password18:23
*** ebalduf has quit IRC18:23
ayoungtopol, two reasons18:24
morganfainbergbknudson, not that a username/password wouldn't *also* work, but it wouldn't be required.18:24
*** yamamoto has joined #openstack-meeting18:24
ayoungone, so we can updated it if there is a CVE18:24
ayoung2.  to build toward dynamically generating rules for the policy file...let me address that one18:24
bknudsonok, but if the argument is that nova needs to do 2 requests for each token that's not a good argument.18:24
ayoungOK,  if you look at the rules, they are often things like "admin or owner"18:24
ayoungbknudson, yes it is18:25
topolI agree the rules are not granular18:25
morganfainbergbknudson, no thats not the only argument, the main argument is that deployers don't want usernames/passwords in config files - and encrypting that is a separate issue18:25
bknudsonbecause nova doesn't need to do 2 requests for each token.18:25
*** Mandell has joined #openstack-meeting18:25
morganfainbergbknudson, nova not needing an extra round-trip every now and again is a benefit, but not the sole story18:25
ayoungbknudson, but,  was a goal.  The rest of the design stands on its own even if we don't do it18:25
morganfainbergbknudson, it's a kill few birds with one stone.18:26
ayoungOK  so back to rules:18:26
ayoungthe idea is that our roles are really collections of capabilities18:26
ayounghenrynash, I think that is one of your key points18:27
topolayoung whats not coming through is how this benefits the projects. Benefits beyond them getting the policy file from keystone and beyond a more granular RBAC policy sample (gift) for them to use... There seems to be another catch that I am not understanding18:27
samuelmsayoung, henrynash ++18:27
*** AJaeger has joined #openstack-meeting18:27
ayoungso the smalles thing we have right now are the rules themselves, which are mapped to APIs.18:27
samuelmswhat about introduce capabilities on keystone ?18:27
ayoungthings like18:27
ayoungidentity:check_token18:27
ayoungor compute:boot18:28
henrynashayoung: indeed….I think we should separate service capabilities (which are kind of our roles today) and the “real roles” which are collections of those capabilities18:28
ayounghenrynash, so that is what I am driving towards18:28
*** jrist has joined #openstack-meeting18:28
samuelmshenrynash, ++18:28
samuelmshenrynash, domain-roles18:28
morganfainbergsamuelms, i think that comes down to further work on this thought path.18:28
ayoungso we also need to "not break things"18:28
morganfainbergsamuelms, this would be the start and wouldn't preclude moving to much more granular stuff18:28
ayoungand that is what lead to this approach geting so granular18:28
topolNeeds to be clear what extra work the projects need to do to take advantage (more pep points?)   and needs to be clear what benefits they will see18:28
ayoungso,  look at the rules, los of them assume "user has some role on the project"18:29
morganfainbergtopol, ++ clear additional PEP benefits is key18:29
samuelmsmorganfainberg, k18:29
ayoungand we used to have the idea of "user is a member of a proejct" as a separate concept from roles...which we changed into :"uuser has the member role on a projct"18:29
dolphmtopol: ++ i'm not clear on what we're asking of other projects, if anything18:29
ayoungso  we could look at the existing roles as  admin and member18:29
ayoungthere are few other one offs,18:29
*** openstac_ is now known as amolock18:29
morganfainbergdolphm, i think the goal is we're aiming to make it so other projects don't really need to "do" much of anything except maybe removing is_admin18:30
ayounglike server etc, but really  the other projects care about admin  (can do anything) and member(can do something)18:30
ayoungso...lets say that "admin" is composed of "member"  p[lus other capabilites18:30
ayoungwe can reflect this in the policy file rules like this:18:30
ayoung...18:31
*** gyee has joined #openstack-meeting18:31
ayoung "owner"                                      : "( user_id:%(user_id)s or user_id:%(target.token.user_id)s ) or rule:domain_admin",18:31
*** leonchio_ has joined #openstack-meeting18:31
ayoungyeah, that is not member18:31
ayoungbut the rule is composed of "( user_id:%(user_id)s or user_id:%(target.token.user_id)s )  and domain admin18:31
ayoungand then domain admin is defined as18:32
*** niclem_ has joined #openstack-meeting18:32
ayoung"domain_admin"                               : "(role:admin and rule:domain_matches and scope:domain) or rule:cloud_admin",18:32
ayoungand yes, henrynash you have concerns about domain matches.18:32
ayounglets put them aside for the moment18:32
*** shashankhegde has quit IRC18:32
ayoungand then cloud_admin is our power user18:32
*** zz_avozza is now known as avozza18:33
*** jgallard_ has quit IRC18:33
ayoung"cloud_admin": "role:admin and domain_id:admin_domain_id and scope:domain",18:33
*** shashankhegde has joined #openstack-meeting18:33
dolphmso you're basically just rewriting the rules to compose roles together as much as possible?18:33
*** niclem has quit IRC18:33
ayoungdolphm, yes18:33
ayoungdolphm, the goal is this:18:33
dolphm++18:33
*** colinmcnamara has quit IRC18:33
henrynashayoung: yes, right now I’m tryingto make sure I grasp the essence of this change to the policy file…I’m always with you up to this point…then the little doubting bird starts chipring in my ear18:33
*** wuhg has quit IRC18:33
ayoungat the API level, the writer should specify as little as possible, hopefully just the role18:33
bknudsonwhere does scope come from?18:34
dolphmhenrynash: it might help if there was a diagram of the hierarchy that ayoung is producing? ayoung: sorry to make you diagram.18:34
bknudsonI don't think we have that now.18:34
ayoungbknudson, it was something I added to the rules enforcement, but its in the token18:34
ayoungdolphm, I have that18:34
dolphmooh18:34
ayoung1 sec18:34
ayoungpauses due to gerrit slowness18:34
lbragstad(cloud-admin) -> (domain_admin) -> (owner)?18:35
*** EmilienM|afk is now known as EmilienM18:35
*** marcoemorais has left #openstack-meeting18:35
ayoungdolphm, https://review.openstack.org/#/c/125704/7/specs/kilo/hierarchical-roles.rst,cm18:35
ayoungthe diagrams start at line 7818:35
*** noelbk has quit IRC18:35
ayounglbragstad, yes18:35
* dolphm needs to review specs.18:36
lbragstadso, each project would need to define what their 'admin' can do18:36
ayounglbragstad, right18:36
ayounglbragstad, so we have a unified policy file18:36
topolso whats gonna really help here is a sample of a new policy file where we can see the benefits of the new approach (composability, whatever)  and then once the value is clear selling it will be easier18:36
morganfainbergdolphm, hehe this is why there was a housekeeping item at the start of the meeting18:36
ayoungsamuelms, you have that?18:36
morganfainbergdolphm, :)18:36
stevemartopol, i think thats in the patch chain18:36
ayounghttps://github.com/samuel-ms/os.unified.policy/blob/master/src/policy.json18:36
samuelmsayoung, the unified policy?18:37
ayoungso that will need to be rewritten once we have the  basic rules cleaned up18:37
topolstevemar, thanks. is it annotated so its new benefits are clear?18:37
ayoungbut,  then the goal is to be able to go more granular18:37
dolphmbut that's up to the projects18:37
ayoungtopol, read the hierarchical spec, its the centerpiece18:37
henrynashayoung: so I guess my real issue with this is that I don’t see teh defintion of “logical” roles (i.e roles that specify some meangful role to a domain admin) as being something that exists in the policy file…18:37
dolphmor you mean more granular roles?18:37
jamielennoxayoung: so last i heard was that you wanted to do all this within policy.json - is that no longer the case?18:38
ayoungdolphm, up to the project to go more granular?  Well, the default is, yes18:38
ayoungjamielennox, ok...so the end state is this18:38
stevemartopol, nope, it's all json so no comments18:38
ayoungwe have in the keystone roles database the relationships between the roles.  That info is used to generate a section at the top of the policy.json file18:38
ayoungthat shows the inheritance chain18:39
stevemartopol, i think this is it: https://review.openstack.org/#/c/123509/18:39
jamielennoxbecause you should be able to define a rule that says one role is composed of these others and have that recursive18:39
ayoungstevemar, we can find some way to make comments if we need to18:39
ayoung"comment": "This is not really a rule"18:39
jamielennoxthe concept of parent shouldn't need to be stored18:39
topolthanks stevemar18:39
*** timcline has joined #openstack-meeting18:39
morganfainbergayoung, ok i think we need to continue this in -keystone and on the specs [we have some other topics we need to hit today here], but this i think has helped a lot socialize the concepts and what you're aiming for (so wrap up if you don't mind)18:39
morganfainbergayoung, i know it's helped me understand the bigger goals as well.18:40
henrynashayoung: unless we are going to have domain-specific policy files….then surely the policy file is “owned” by a service and might have a) a set of raw capabilities, and (optionally) some generic groups of those capabilities….(although I always struggle with the later since I always feel these groups will end up domain-specific)18:40
ayoungmorganfainberg, thanks for the time.  I just wanted people to be aware of the scope of what I was proposing, and the relationship between all this mini specs18:40
dolphmhenrynash: ++18:40
morganfainbergayoung, exactly18:40
samuelmshenrynash, ++18:40
ayounghenrynash, a service should specify just the cpabailites and the roles for that capability18:40
ayoungits up to Keystone to manage the higher level of composition18:40
morganfainbergayoung, we need to add comment logic to the policy rules engine anyway18:41
ayoungideally, a user should be able to delegate to someone else only a subset of their capabilities18:41
morganfainbergayoung, something the rules engine *should* support cleanly18:41
samuelmsayoung, , with domain-roles being defined at domain level, and the fact that domain_roles contains other roles or capabilities18:41
samuelmsaysyd, make it possible to define access control at domain level18:41
samuelmsayoung, without the need of having one policy file per domain18:42
*** niclem_ has quit IRC18:42
ayounghenrynash, samuelms I'm not certain if domain roles fall 100% into the same mechanisms as what I am proposing.  It seems to me that domain roles should be expanded prior to token creation18:42
morganfainbergsamuelms, i think that is more forward looking than this cycle, but something to keep in mind.18:42
ayoungOK, I surrender the conch18:42
morganfainberg#topic New Cloud Policy on Keystone18:42
*** openstack changes topic to "New Cloud Policy on Keystone (Meeting topic: Keystone)"18:42
ayoungfeel free to corner me for more questions18:42
henrynashayoung: (agreed)18:42
morganfainberg#link https://review.openstack.org/#/q/status:open+branch:master+topic:bp/modify-policy,n,z18:42
morganfainbergsamuelms, afaranha o/18:42
*** _sunil has quit IRC18:42
samuelmsmorganfainberg, ++18:42
samuelmso/18:43
ayoungI've butchered the hell out of their patch18:43
morganfainbergas a heads up i'm going to keep this moving so we can cover the last couple topics, but these look to be straightforward.18:43
samuelmsso basically we're proposing spliting the global admin we have in cloud_admin, domain_admin, project_admin18:43
ayoung++18:43
samuelmswe have a spec and a patch proposing policy changes18:43
samuelmshttps://review.openstack.org/#/q/status:open+branch:master+topic:bp/modify-policy,n,z18:43
samuelmsayoung is working with us on this18:44
samuelmsand we just need more reviews on that stuff18:44
bknudsondeployers can use whatever policy they want to or provide their own.18:44
bknudsonwhat difference does it make what the default one is?18:44
*** VW_ has quit IRC18:44
samuelmsbknudson, yes, sure .. and they're doing this today18:44
henrynashsamulems: so the one conceptual change between this and the previous v3policsample is that in the one I origionally wrote I think cloud_admin was a superset of domain_admin…18:44
morganfainbergbknudson, it matters so we show best practices18:44
samuelmsbknudson, we have something more 'real' as default18:44
afaranhawe are now working on policy refactor with Adam Young https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:policy-refactor,n,z18:44
samuelmsmorganfainberg, ++18:44
*** johnthetubaguy is now known as zz_johnthetubagu18:44
morganfainbergbknudson, the current model people use in production... because deployers don't want to or dont get (as per the summit session) how to write policy18:45
morganfainbergwith some rare exceptions18:45
ayounghenrynash, so, one thing I was wondering was how to communicate the admin domain ID.18:45
raildobknudson, another this is this will be very useful for hierarchical multitenancy implementation18:45
dolphmbknudson: i'd rather see something more powerful as the default starting point - i have my gripes with v3cloudpolicy but they're not resolvable in the short term.18:45
ayoungif the file was autogenerated, we'd inject it18:45
samuelmsdolphm, ++18:45
henrynashayoung: could od18:45
bknudsonseems like a large spec for just saying we feel like the default policy should change.18:45
henrynashdo18:45
bknudsongit mv18:46
*** vishwanathj has quit IRC18:46
ayoungWe could do this: upload of policy file allows for template replacement, and then keystone gets its policy out of its store as opposed to from etc18:46
morganfainbergbknudson, there is actually a chunk of work for tests and whatnot i think18:46
dolphmbknudson: is it really a git mv? or did the policy need to change to become the default? i'm surprised there's no impact on tests.18:46
morganfainbergdolphm, fairly certain there is.18:46
morganfainbergand quite a bit actually18:47
samuelmsbknudson, well, after keystone accepts that , we plan to put such policies on every service18:47
samuelmsbknudson, and make that spec global18:47
bknudsonthey'll need their own spec, or put it in the common specs.18:47
*** oanufriev has quit IRC18:47
henrynashwe can’t just use v3policsample as is…it does need some changes18:47
morganfainbergsamuelms, you should propose this to the cross-project repo18:47
*** shashankhegde has quit IRC18:47
ayoungI might well have messed up their tests.  Look at older revisions of the patch to see the degree of churn18:47
lbragstadsamuelms: do you know if the testing impact is documented in the spec?18:47
*** shashankhegde has joined #openstack-meeting18:47
samuelmsmorganfainberg, will do, we just want to have as much feedbacks as we can on keystone (at home)18:47
dolphmthere are also dependent patches that touch v3 cloud policy18:47
morganfainbergsamuelms, fair enough.18:48
dolphmrather, required patches18:48
samuelmslbragstad, will check18:48
morganfainbergso i think we need eyes on the spec - please provide feedback18:48
*** HenryG_ has quit IRC18:48
*** HenryG has joined #openstack-meeting18:49
bknudsonthe cloud policy file requires hardcoding the admin domain id.18:49
morganfainbergand offer to help solve issues with the v3 policy file as you see them ( dolphm, please vocalize your gripes if possible there with that policy file )18:49
samuelmslbragstad, just a small subsection, need to make it clearer. please leave a review :)18:49
lbragstadsamuelms: will do18:49
samuelmsmorganfainberg, ++18:49
morganfainbergbknudson, something we should figure out if can be fixed with this process18:49
morganfainbergok since we have two more topics i'm going to say we continue on18:49
samuelmsyep18:49
morganfainberg#topic Third-Party Dashboard Spec18:49
*** openstack changes topic to "Third-Party Dashboard Spec (Meeting topic: Keystone)"18:49
dolphmmorganfainberg: my gripe is mainly the dependency on another magical domain - because we don't have a better way to express service-level authorization18:49
morganfainberg_sweston, o/18:50
morganfainberg#link https://review.openstack.org/#/c/135170/18:50
morganfainberg_sweston may not be here at the oment, so we can circle back if he does show up.18:50
ayoungwhat is a Third Party Dashboard?18:51
morganfainbergi think he wants some people to take a look at the spec, i don't have much more info18:51
*** aranjan has quit IRC18:51
morganfainbergso, we can try again next week or i'll ask him to come to #openstack-keystone to discuss18:51
ayoungCI18:51
henrynashwhat is CI?18:51
*** mattgriffin has quit IRC18:51
bknudsoncontinuous integration18:51
morganfainbergmoving on18:51
bknudsonjenkins and stuff18:51
samuelmsk18:51
dolphmwhat does this have to do with keystone?18:51
*** _nadya_ has joined #openstack-meeting18:51
morganfainberg#topic Assignment Split18:51
ayoungOK..this is a Gerrit workflow issue...got it18:51
*** openstack changes topic to "Assignment Split (Meeting topic: Keystone)"18:51
*** egallen has quit IRC18:51
morganfainberg#link https://review.openstack.org/#/c/130954/18:51
morganfainberghenrynash, o/18:51
morganfainbergayoung, we'll get him to explain it in -keystone or next week.18:52
ayoungso if we were to introduce external LDAP tests, for example18:52
morganfainbergayoung, and give details.18:52
ayoung++18:52
ayounggood to go18:52
henrynashok, so question has been raised as to whether teh current patch is correct in having the split of roles into their own backend18:52
topol130954, also known as the beast :-)18:52
*** noelbk has joined #openstack-meeting18:52
morganfainberg(8min)18:52
ayounghenrynash, I vote yes for roles in their own backend18:52
henrynashmorganfainberg and I have laid down a couple of arguments on each side in teh review commens18:52
bknudsoncan we get a better name than "resource" for the backend? everything is a resource.18:52
samuelmshenrynash, ++ from me18:53
henrynashreally want others to weight in with theie views18:53
morganfainbergas do i18:53
topolbknudson+++ great point18:53
*** gokrokve has joined #openstack-meeting18:53
*** timrc has joined #openstack-meeting18:53
ayoungquestion was whether to split projects and domains into two different backends, and then name the backends appropriately18:53
*** grue_pm has joined #openstack-meeting18:53
henrynashbknudson: my only defence is a) noone coudl come up witha  better name and b) in fedration language “resource” is the object you act on18:53
*** _nadya_ has quit IRC18:54
gabriel-bezerrabknudson: ++18:54
ayoungleave the actual role assignements in assignements, everything else gets its own backend based on its name18:54
morganfainbergayoung, this question is do roles split from assignment, where assignment is the engine doing the <attr> -> role mapping, and roles would be isolated from that18:54
henrynashayoung: that’s a seperate discussion (I hope….)18:54
ayounghenrynash, lets have it now18:54
*** egallen has joined #openstack-meeting18:54
ayoungwe suggested it back when splitting identity and assignements18:54
morganfainbergayoung, i think that is the next conversation18:54
topolit would seem that roles and assignemnts would fit well together. whats the counter argument?18:55
ayoungif we are having trouble with names, then lest call "resourece" the project backend18:55
*** vigneshvar has quit IRC18:55
henrynashtopol: see the latets commnest in the patch set18:55
*** che-arne has quit IRC18:55
ayoungand if we end up splitting it, we'll put domains into their own.  K?18:55
dstanekdoes splitting roles have to be in this patch anyway - seems like a follow on patch for splitting assignment and identity18:55
morganfainbergayoung, more splitting is def. on the table, but we've got this already in line - name of the backends for the context of this disucssion is bikeshedding18:55
*** afaranha has quit IRC18:55
morganfainbergso ignore name complaints for now, put those on the review.18:55
*** AlanClark has joined #openstack-meeting18:55
ayoungmorganfainberg, the question was whether to split roles from projects and domains, right?18:56
morganfainbergayoung, no, roles from assignment, the mapping part18:56
dolphmi'm just going to remind everyone that i regret making roles a first class resource in the API. i wish they were just arbitrary strings owned by the policy files and using as mappings in the assignment backend. </digression>18:56
morganfainbergayoung, domains and project split would be different.18:56
morganfainbergdolphm, that is mostly my point18:56
samuelmsthe main idea was to keep assignment.mapper and assignment.connector (what we need to do the assignment itrself, i.e the actual roles)18:56
bknudsondolphm: if roles were their own backend you could do that.18:56
morganfainbergdolphm, and arguments against splitting role from assignment (new assignment)18:56
dolphmit's hard to find a place for them in keystone because they don't belong in keystone :(18:56
*** ianw has joined #openstack-meeting18:56
ayoungdolphm, they start meaning something with the autogenerated policy,18:57
ayoungthey really are part of the policy language18:57
lbragstad~3 minutes left18:57
morganfainbergsamuelms, but that is just adding another abstraction that does what we do today - meaning the assignment backend needs to then be mapped pretty much like today18:57
henrynashdolphm, morganfainberg: and my argument for having them separte is that they will eventually disappear…but while we have them as first class resoruces, we shouldn’t require an assignment mapping engine to be responsile for their management18:57
dolphmayoung: they're an artifact of the policy files18:57
samuelmshenrynash, ++18:58
morganfainbergmy only other point is extra splitting down the line is easier than unsplitting things18:58
samuelmshenrynash, I think having an example of how easy it should be to plug a new assignment backend would be help18:58
*** aranjan has joined #openstack-meeting18:58
morganfainbergi've posted my views as comments on the review, please read them, and weigh in on it.18:58
dstanekmorganfainberg: ++18:58
ayounghenrynash, OK,  I'd argue that we should change "resource" to "proejct" and then if anything needs to be split off of that, they get their own backends18:58
samuelmshenrynash, like a simple poc18:58
morganfainbergfurther splitting such as domains and projects will be a different conversation.18:59
ayoungI'd like roles to be split, but I can work with it either way18:59
henrynashmy main goal is that i REALLY want to get the split patch merged immediately after we cut K1…it’s a huge rebase to maintain…and my fingers are tired!18:59
ayoungI don't really need assignments split, but again, won't hurt to do it18:59
rodrigodshenrynash, ++19:00
dolphmayoung: that's kind of where i'm at19:00
ayoungmy feeling is that nay argument for splitting assignments really will be replicated in splitting the other pieces off.  But I'm not going to hold anything up19:00
morganfainbergi am of the opinion this is a topic that no one person can answer - so everyone, core or not, should weigh in and we'll see where the conversation goes. this is a big shift19:00
morganfainbergand has wide implications on what we're supporting in the future19:00
morganfainbergand that's time19:00
morganfainbergwe'll keep this conversation going in -keystone and on that review19:00
dolphmdun dun DUN.19:00
*** amitry has quit IRC19:00
morganfainberg#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
dolphm#lunch19:00
openstackMeeting ended Tue Dec 16 19:00:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-12-16-18.01.html19:00
bknudsoncliff-hanger19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-12-16-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-12-16-18.01.log.html19:00
anteayadolphm: enjoy19:00
*** amitry has joined #openstack-meeting19:01
*** jamielennox has left #openstack-meeting19:01
jeblairhowdy infra folks19:01
dolphm#startlunch19:01
*** sarob has quit IRC19:01
morganfainbergNext time in #openstack-meeting, we'll see whether henrynash can convince the keystone-core team ...19:01
fungihowdy yourself!19:01
morganfainberg /soap opera19:01
anteayao/19:01
*** ksavich_ has quit IRC19:01
henrynashlive on national tv...19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Dec 16 19:01:46 2014 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
SergeyLukjanovjeblair, hey, mostly ok,  /me monitoring the USD-RUB :)19:01
pleia2o/19:01
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
*** timcline has left #openstack-meeting19:01
AJaeger\o/19:02
mmedvedeo/19:02
jeblair#link last meeting http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-09-19.02.html19:02
swestono/19:02
asselino/19:02
clarkbohai19:02
nibalizero/19:02
krtayloro/19:02
jeblair#topic  Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
ianwo/19:02
*** penick has quit IRC19:02
jeblairclarkb add DENY Email Third-Party CI rule to gerrit ACLs, giev Third-Party Coordinators ownership of Third-Party CI, seed Third-Party Coordinators with third party meeting attendees19:02
clarkbjeblair: done19:02
anteayayay19:02
*** noelbk has quit IRC19:03
*** sarob has joined #openstack-meeting19:03
jeblairrock on.  does that more or less conclude the self-service 3pci project?19:03
*** b0d0nne11 has quit IRC19:03
mordredo/19:03
*** marcoemorais has joined #openstack-meeting19:03
clarkbjeblair: I think so. Haven't heard screaming and things seems to still be getting tested19:03
anteayajust the patch to remove -requests from the servers19:03
clarkboh right the mail list19:03
pleia2the patch is in, we need manual disabling19:03
anteayawhich is an artifact19:03
anteayacool19:03
jeblairpleia2: can/will you do that?19:03
*** sicarie has quit IRC19:04
pleia2jeblair: can't, I think rmlist on the server will be needed19:04
jeblairoh i thought we were going to leave the archives19:04
jeblairare they interesting?19:04
anteayathe plan was to leave the archives19:04
pleia2we should confirm though, rmlist in the man page says it won't remove archives, but I don't know where the archives end up19:04
pleia2you need rmlist -a19:04
anteayanot terribley but they are history19:04
pleia2but we don't want that :)19:04
*** lhcheng has left #openstack-meeting19:04
zaroo/19:05
anteayaand we did at one point reference them19:05
*** amolock has quit IRC19:05
jeblairokay, so rmlist without -a?19:05
*** SridharRamaswamy has joined #openstack-meeting19:05
jeblairseems like they might be hard to find if that's the case19:05
pleia2might just keep them on the filesystem, which is sub-optimal19:05
*** marrusl has joined #openstack-meeting19:05
anteayaif they aren't discoverable no point in keeping them19:05
*** thangp has quit IRC19:06
pleia2anyone else know anything about mailman's rmlist? :)19:06
anteayaI just was hoping to avoid a blackhole if someone found an old breadcrumb trail19:06
jeblairyeah.  probably we should either: a) put the list defn back and just disable subscription, etc.  or b) remove everything.19:06
clarkb+1 to disabling subscription19:06
fungialternatively, just switch the list to reject19:06
fungier, that19:06
anteayaI'd rather disable than reject19:06
pleia2so, the list sort of stays alive19:06
anteayatoo much confusion in this space as it is19:07
anteayapleia2: :(19:07
jeblairi don't actually think the archives are interesting, so i'm okay with either.19:07
anteayathey aren't interesting19:07
*** yamamoto has quit IRC19:07
pleia2we can put notes up everywhere about how it's dead, but it'll still show up on lists.openstack.org and people can try to subscribe (it'll just discard them)19:07
*** vigneshvar has joined #openstack-meeting19:07
anteayawhat happens if we remove everything?19:08
fungiis this something consensus from the third-party working group would be helpful to solicit?19:08
*** Rockyg has joined #openstack-meeting19:08
jeblairi don't think so19:08
*** henrynash has quit IRC19:08
*** bswartz has joined #openstack-meeting19:08
fungiin that case, i'm fine seeing it just removed, archives and all19:08
*** otter768 has joined #openstack-meeting19:08
clarkbya I guess the archives aren't particularly interesting19:08
clarkbjust requests and calrification of requests19:09
anteayaokay looks like the tendency is for it to go19:09
clarkbI can see them being removed19:09
jeblairi don't think we would do that with most lists, but i think this is an unusual circumstance19:09
anteayaso I am fine with it going19:09
jeblair#action jeblair rmlist -a third-party-requests19:09
*** bernardo-silva has joined #openstack-meeting19:09
jeblair#topic  Priority Specs19:09
*** openstack changes topic to "Priority Specs (Meeting topic: infra)"19:09
pleia2thanks19:09
jeblair Migrate to Zanata: https://review.openstack.org/#/c/133222/19:09
clarkbI reviewd that one +219:09
pleia2who wants to +A? :)19:10
jeblairthis is ready to merge; anyone have any last minute requests to hold off on +A for approval, otherwise it's going in19:10
*** nkinder has left #openstack-meeting19:10
anteayagreat work pleia219:10
jeblairsorry, hold off on +A for additional review19:10
AJaegerpleia2: thanks a lot!19:10
pleia2woo, my first spec19:11
*** nellysmitt has joined #openstack-meeting19:11
jeblairdone.  yaaay!19:11
anteaya\o/19:11
pleia2thanks all19:11
fungilet the games begin19:11
fungigreat spec, pleia219:11
jeblairthis one isn't really a priority spec, but again i just want to call it out for infra review because i think we have considerable interest in the area:19:12
jeblair Storyboard streaming API: https://review.openstack.org/#/c/105252/19:12
jeblair#topic  Priority Efforts (Swift logs)19:12
*** openstack changes topic to "Priority Efforts (Swift logs) (Meeting topic: infra)"19:12
jeblairoh, so we had that rax issue last week; did that get resolved?19:12
fungiseems like it19:13
fungii was able to browse recently uploaded logs there19:13
clarkbyes I think it resolved, but I didn't track down the bug to see what they had to say19:13
*** otter768 has quit IRC19:13
jeblairThank you for the update. I was able to do a little more digging into the issue and did notice that the container in question 'infra-files' does not have the header 'X-Container-Read: infra-files-ro' associated to it. You will need to make sure that the header is added to this container.19:14
clarkbalso there is a proposal to add this to the dg-tempest- jobs so that we can throw a bit more load at it19:14
jeblairthat only prompts more questions, in my mind.19:14
anteayaclarkb: I merged that patch last night I do believe19:14
clarkbjeblair: hrm how did it ever work then19:14
clarkbanteaya: awesome19:14
anteayaif we are thinking of the same patch19:14
jeblairlet's debug more later19:14
jeblair#topic Priority Efforts (Puppet module split)19:15
*** openstack changes topic to "Priority Efforts (Puppet module split) (Meeting topic: infra)"19:15
jeblairasselin: ping19:15
asselinHi, I wrote some patches to accelerate module splits19:15
asselin#link https://review.openstack.org/#/c/140523/19:15
AJaegerthere're two "unusual" patches: https://review.openstack.org/140523 and https://review.openstack.org/14054819:15
asselin#link https://review.openstack.org/#/c/140548/19:16
*** mattgriffin has joined #openstack-meeting19:16
AJaegerasselin: sorry, for interrupting ;)19:16
*** nellysmitt has quit IRC19:16
asselinwould like to get ppl's opinions. It is a bit 'different'19:16
nibalizerim for it19:16
asselinbut we can go much faster by pre-approving changes19:16
asselinthan doing the same review one by one * 5019:17
* anteaya notes she still has a problem with hyphens and underscores in the same repo name19:17
AJaegerThese patches add all the infrastructure for the projects in one bulk to make the real imports easier.19:17
clarkbso I disagree with the assertion that it is easier to review them all at once19:17
nibalizeri left some comments that i think elasticsearch is gonna split before the big patch lands so might as well rebase on it and intentionally do that19:17
clarkbthat change is ~800 lines and that is hard to erview19:17
nibalizeri actually agree with clarkb19:17
jeblairnibalizer: elasticsearch is split19:17
nibalizeraha so i was right!19:18
*** elo has left #openstack-meeting19:18
nibalizerone of the issues i've seen is that git doesn't diff/merge the yaml files very well19:18
mmedvedeI expressed my concerns in the patch comments19:18
anteayaeven if the resultant patches end up being fewer edits19:18
nibalizerso if you have 3 or more 'split outs' in flight and one lands the rest need rebases which slows everything down19:18
anteayaI still need to check the foundation is there and spelled correctly during my review19:18
jeblairmmedvede: i don't see your comments19:18
fungidiff/patch algorithms generally have problems with files containing lots of repetition19:18
anteayaso while it seems like less work for the patch owner, the work for the reviewer is actually more19:19
mmedvedejeblair: https://review.openstack.org/#/c/140548/19:19
jeblairah the other one :)19:19
anteayasince the jobs I have to confirm aren't in the patch19:19
*** jtomasek has quit IRC19:19
jeblairanteaya: what jobs?19:20
anteayawhen I review a patch for a new repo creation, any jobs that are run on it19:20
fungii don't think 140548 solves anything. you'll still hit merge conflicts (probably much more often)19:20
anteayaI confirm the name and the job name in jenkins/jobs19:20
jeblairanteaya: confirm it against what?19:21
anteayaif the group decides they want this then fine, I'm just sharing my workflow when I review repo creation patches19:21
anteayathe zuul/layout.yaml jobs19:21
anteayaand the project.yaml files19:21
anteayaI compare them19:21
anteayaand make sure there is a jenkins job  and taht it does what is expected19:22
jeblairanteaya: there is a job that automatically ensures that every job listed in layout.yaml is defined by jjb19:22
fungianteaya: we have a job which confirms that the jobs added in layout.yaml are actually configured for jenkins-job-builder19:22
*** fnaval has joined #openstack-meeting19:22
fungithat19:22
jeblairanteaya: so the only thing missing from 523 is the repo itself19:22
fungiit doesn't analyze the operation of the job itself, but it does at least make sure it exists19:22
anteayaright19:22
*** weshay has quit IRC19:23
anteayalike I said if the group wants this then I will review as required19:23
jeblairso when the repo is added, you can then double check that the (already defined) jobs match19:23
anteayaI still am not a fan of hyphens and underscores in the repo name19:23
anteayaright19:23
*** VW_ has joined #openstack-meeting19:23
anteayawhich I do in new repo creation patches19:23
jeblairis there a technical reason for hyphens/underscores?19:23
*** weshay has joined #openstack-meeting19:23
nibalizeruh kinda19:24
anteayait can lead to errors19:24
*** weshay is now known as weshay_bbiab19:24
nibalizerwe went throught this with apache19:24
anteayawhich is why we came up with puppet-httpd19:24
nibalizera class in puppet, openstack_project for example, has to be letters and underscores19:24
nibalizerby convention we have the repos named puppet-thing19:24
asselinfyi, I kept the name the same as in module.19:24
nibalizerso that leads to puppe-thing_thing19:24
anteayaasselin: I know19:24
nibalizeri am super strongly against trying to wedge a module rename into a split out19:25
anteayanibalizer: me too19:25
AJaegerIt's 54 repositories that asselin tries to add (if my math is right). Do we want 54 single patches? Or how do we want to do it?19:25
nibalizerwe can rename it inside of system-config before we split it out if we really need this19:25
anteayanibalizer: that would work for me19:25
jeblairwhat would we rename them to?19:26
nibalizerim not sure what the offending modules are named19:26
nibalizerlet me look19:26
funginames without underscores in them presumably19:26
asselinyes, this is just 'base work'. We can still adjust special cases, or delete some we don't want to split out in follow up patches.19:26
*** achanda has quit IRC19:26
jeblairpuppet-elastic_recheck for example19:26
mmedvedeI think the dash might be puppet module naming thing19:27
mmedvede#link https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#a-note-on-module-names19:27
*** marcoemorais has quit IRC19:27
*** thangp has joined #openstack-meeting19:27
*** marcoemorais has joined #openstack-meeting19:27
swestonthis would also be easy to do in the split script that I am building, so if anyone thinks this is a good candidate for automation, I can include it.19:28
fungifor reference, the full list of affected modules is elastic_recheck, devstack_host, etherpad_lite, log_processor, mysql_backup, openstack_project, project_config, remove_nginx, ssl_cert_check, unattended_upgrades19:28
nibalizeri dont want to split out openstack_project or project_config19:29
anteayaso I am for asselin's suggestion to remove those from this patch19:29
funginibalizer: which the proposed change does, fwiw19:29
jeblairasselin: did you get the list from the spec?19:29
*** dwalleck has quit IRC19:29
nibalizerfungi: yea i noticed that and -1'd19:29
*** NobodyCam has left #openstack-meeting19:29
asselinjeblair, no, but can update it to the spec19:30
*** garyk has quit IRC19:30
asselinif we get agreement on the direction19:30
jeblairasselin: yeah, let's work from the spec if we decide to do this19:31
fungii'm generally not a fan of commented out functional content in revision control systems, but can get over it if the proposal has general support19:31
asselinwill we decide now? or later?19:32
jeblairi think it's going to take too much time to hash out the details in this meeting19:32
jeblairasselin: can you work with nibalizer and anteaya to resolve remaining issues19:32
* nibalizer nods19:32
asselinjeblair, yes19:32
jeblairalso clarkb and fungi :)19:33
fungialso be aware that new modules end up getting incubated in system-config rather than started separate (perhaps that needs more consideration for future direction too)19:33
clarkbfungi: yes I think we need to start starting separate in the near future19:33
anteayafungi: oh I didn't know that19:33
jeblairfungi: yeah, i think we can establish policy on that once the split is done.19:33
*** padkrish_ has quit IRC19:33
clarkbfungi: we had been doing it that way, but now there is enough momentum behind splitting we can talk about what the future looks like19:33
jeblairright now it would just be a distraction19:33
fungia plan like this will quickly become disjoint and out of sync if we continue with that process19:33
* nibalizer agrees with most of this ^19:34
jeblairfungi: well, if we merge everything quickly, it won't have much time to get out of sync.19:34
fungithis is true19:34
*** Mandell has quit IRC19:34
jeblair#topic Priority Efforts (Nodepool DIB)19:34
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:34
*** dprince has quit IRC19:34
fungithough "merge everything quickly" would mean finish the module split quickly19:35
asselinjeblair, sorry, regarding merging everything quickly19:35
clarkbthanks to the debugging efforst of jeblair nodepool is running on trusty now19:35
mordredthe images all work now19:35
jeblairso i guess we can resume work on nodepool contos?19:35
asselinI was proposing (also in agenda) for a mini sprint19:35
mmedvedethat reminds me, asselin - you mentioned maybe doing module-split sprint in 3rd party meeting  yesterday19:35
anteayayay19:35
mordrednodepool centos works19:35
clarkbjeblair: yup19:35
mordredat least dib nodepool centos works19:35
mordredand boots and everything19:35
clarkbI think next steps in this space are reviewing and deploying the various bug fixes that have been pushed to nodepool19:35
mordrednow I'm writing the python version of the bash scripts I've been using to do this19:36
clarkbthen figuring out why hpcloud didn't want to boot the images we built19:36
mordredso that I can make some patches to nodepool19:36
*** padkrish has joined #openstack-meeting19:36
*** Mandell has joined #openstack-meeting19:36
*** noelbk has joined #openstack-meeting19:36
*** Mandell has quit IRC19:36
mordredit seems those want to go on top of the various bugfixes clarkb mentions19:36
*** mchalla has quit IRC19:36
clarkbI am also currently cleaning up old nodepool so that it can be deleted19:37
*** ihrachyshka has quit IRC19:37
mordredwoot19:37
clarkband just found a new nodepool bug in the process :)19:37
jeblairokay, so nothing blocking there?  just resume speed and try to catch up on nodepool reviews?19:37
clarkbwill file that on storyboard post meeting19:37
clarkbjeblair: yup19:37
mordredyup19:37
jeblairwho put "Explore idea of upgrading Gerrit to ver 2.9.x" on the agenda?19:37
*** SridharRamaswamy has quit IRC19:37
zarome19:38
jeblair#topic Explore idea of upgrading Gerrit to ver 2.9.x (zaro)19:38
*** openstack changes topic to "Explore idea of upgrading Gerrit to ver 2.9.x (zaro) (Meeting topic: infra)"19:38
zaroso a few people suggested we upgrade.  i wanted to get feedback on that.19:38
zarover 2.9.3 now19:38
clarkbzaro: I am on board with it as long as ssh stream events works19:38
anteayaI am in favour since it allows us to use a plugin that will list all users in gerrit19:39
*** _nadya_ has joined #openstack-meeting19:39
clarkbprobably put it on review-dev and attach a bunch of event stream readers19:39
*** jtomasek has joined #openstack-meeting19:39
zaro#link https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.9.3.html19:39
anteayacurrently we can't list all users, so I can't search for all users with CI at the end19:39
anteayanow under 2.9 I still won't be able to, but an admin can19:39
mordredzaro: is the old change screen still existing on 2.9?19:39
zaronew reports coming that it has been fixed.19:39
*** mpaolino has quit IRC19:40
zaroyes it is19:40
mordredcool19:40
zaroeven available in 2.10 & 2.1119:40
jeblairclarkb: known bug with ssh stream events?19:40
clarkbjeblair: yup it was beingworked and 2.9.3 was supposed to fix it. Just proposing we actually test that specific thing19:40
fungii am wholly in favor of keeping in sync with latest releases of gerrit when our dev cycle activity allows (e.g. not in the middle of release crunch) and if there are no breaking bugs we know about19:40
mordredsounds like it's worthwhile to explore19:40
fungiso, yes, with old review screen still available in it and that stream bug supposedly fixed, now seems like a good time to press forward19:41
jeblairthe new change screen is looking _better_ than last time.  i think the comments display is still too wide to read comfortably, but that's relatively minor.19:41
*** ivar-lazzaro has quit IRC19:41
jeblairzaro: can you get review-dev up to 2.9?19:42
*** marcoemorais has quit IRC19:42
zarojeblair: yeah stream events stopped working for some people after a few days.  but latest repors seems to indicate that it's actually the jenkins gerrit trigger that was the cause.19:42
jeblairshould we consider 2.10?19:42
*** vijendar1 has quit IRC19:42
*** marcoemorais has joined #openstack-meeting19:42
zaro#link https://groups.google.com/d/msg/repo-discuss/4va1DH520to/pDGmY7pNUG4J19:42
*** SridharRamaswamy has joined #openstack-meeting19:42
*** marcoemorais has quit IRC19:42
zaro2.10 is not released yet.19:42
clarkbzaro: well people do use the jenkins trigger19:42
jeblairgerrit itself is running 2.10-rc1-938-gd3591cd19:42
zaroclarkb: ahh yeah, that's true.19:42
*** marcoemorais has joined #openstack-meeting19:43
*** vijendar has joined #openstack-meeting19:43
fungiand having the stream events processes pile up on on our gerrit because of their use of the plugin would be not-so-great19:43
jeblairzaro: you mean jenkins gerrit-trigger alone is the cause, or jenkins-gerrit-trigger is incompatible with 2.9?19:43
*** aranjan has quit IRC19:43
zarojeblair: jenkins gerrit-trigger alone is the cuase.19:43
*** marcoemorais has quit IRC19:44
jeblairalso, to be fair, i think we may have seen this once with our current version19:44
zaroi think clarkb and i both like the idea of using same version as gerrit-review.googlesource.com19:44
fungithis might then explain the hung stream events process pile-ups we've seen in the past (though it's been a while since i last spotted on)19:44
fungiyeah19:44
*** amolock has joined #openstack-meeting19:44
*** marcoemorais has joined #openstack-meeting19:44
*** mchalla has joined #openstack-meeting19:45
fungithat would imply much more frequent upgrades19:45
clarkbthe biggest downside with it is we would quickly suck down the latest weirdness that they do19:45
clarkband we seem to have a very different use case19:45
mordredyah - and we have a different set of primary use cases19:46
mordredyah19:46
*** hemna has quit IRC19:46
*** BrianB__ has quit IRC19:46
zarosorry about that last link. this one has latest reports: #link https://groups.google.com/d/msg/repo-discuss/NuFti4SVNQM/Ks8FN6xmW9AJ19:46
*** egallen has quit IRC19:47
jeblairi need more time to read about the ssh issue; let's pick this up later19:47
*** vijendar has quit IRC19:47
jeblair#topic Create plugins for Gerrit <-> Storyboard integration instead of using jeepyb (zaro)19:47
*** openstack changes topic to "Create plugins for Gerrit <-> Storyboard integration instead of using jeepyb (zaro) (Meeting topic: infra)"19:47
zarome again.19:47
* krotscheck lurks19:47
jeblairzaro: can you tell us about "its" plugins briefly19:48
jeblairthat's probably new to most of us19:48
zaroits is short of issue tracking system19:48
fungialso, for clarification, you're talking about the update_bug.py script specifically? or something else19:48
jeblairfungi: yeah, that i believe19:48
zaroits-storyboard is gerrit storyboard integration19:48
jeblair#link https://storyboard.openstack.org/#!/story/200001219:48
jeblair#link https://gerrit-review.googlesource.com/#/c/6059019:49
*** markmcclain has quit IRC19:49
jeblairzaro: what can an its plugin do?19:49
zaroits-storyboard will allow users to configure updates to storyboard from updates to gerrit change (via gerrit stream events_19:49
*** markmcclain has joined #openstack-meeting19:49
zaroso it can add comments to storybaord and update status19:50
fungiif there's a plugin, why would gerrit stream-events come into play?19:50
fungithat seems less robust than using gerrit hooks19:50
zaroit gets the info to update from info in the stream events19:51
mordredlike, from the inside-of-gerrit stream events interface, right? not by having a thing parsing stream-events over ssh19:51
fungiit's using the same info as what stream-events sends, but not directly subscribing to the event stream socket?19:51
fungiokay, that's a little more sane19:51
*** marcoemorais has left #openstack-meeting19:51
zaroyes, you are both correct.19:52
*** hemna has joined #openstack-meeting19:52
*** kebray has joined #openstack-meeting19:52
mordredzaro: just out of curiosity - what does its stand for? (looking at the code)19:52
zaroi'm basically done with the plugin.  just need to make a change to add it to system-config19:52
jeblairmordred: 'issue tracking system'19:52
jeblairmordred: it seems to be a class of plugins which are beginning to appear in gerrit19:53
mordredcool19:53
mordredthat makes sense19:53
*** emagana has quit IRC19:53
*** adahms has joined #openstack-meeting19:53
*** markmcclain has quit IRC19:53
jeblairzaro: so maybe you could send an email to the -infra list describing the plugin and why that approach is better than jeepyb and hooks19:53
zaroi'm just finishing up with documentation and some tests. probably one final push.19:53
zarojeblair: sure, can do.19:54
mordredone final thing - zaro, it seems that you're writing a java storyboard client library inside of that plugin - should we make a java-storyboard repo somewhere that we can release to maven and have this plugin depend on it? (in case other people want to write storyboard integration too)19:54
fungithat seems like an excellent idea. basically it could be the seed for a java storyboard sdk19:54
zaroyeah, i thought about that. would be a good idea.19:54
mordredit doesn't look like the StoryboardClient class is aware of gerrit at all19:54
mordred++19:54
* mordred thinks this is neat19:55
*** mchalla has quit IRC19:55
zaromordred: it's actually just used in the StoryboardItsFacade.java class19:55
jeblairzaro: yep, sounds very cool.  next time, be sure to let us know the cool things you're working on before they're done.  :)19:55
fungii am thrilled to see some of our hackish glue replaced by sane interfaces between consenting applications19:55
*** markmcclain has joined #openstack-meeting19:56
zaroaha, i don't finish every cool thing i start :)19:56
* mordred is going to be amused when we have a java client lib before we have a python client lib19:56
clarkbmordred: clearly we should rewrite everything in java19:56
jeblair#topic  Strategy for upstreaming Gerrit command to ls-members of 'Registered Users' group   (also zaro?)19:56
*** openstack changes topic to "Strategy for upstreaming Gerrit command to ls-members of 'Registered Users' group (also zaro?) (Meeting topic: infra)"19:56
* fungi starts a version of git-review in java19:56
zarome once again.19:56
*** pfalleno1 has quit IRC19:56
*** jwcroppe has quit IRC19:57
*** pfallenop has joined #openstack-meeting19:57
* mordred declares today as national zaro day19:57
anteayaI think this one came from my request19:57
zaroso anteaya was interested in having an ls-members command that would list all users in gerrit.19:57
anteayaagain to be able to search all users19:57
*** jwcroppe has joined #openstack-meeting19:57
anteayawhich we currently can't do19:57
anteayaor I can't19:57
zarothere's a could of avenues to maybe get this just wanted to explore before i start something.19:57
fungiwell, you could via the rest api... enumerate all user ids19:58
fungibut that would be slow and ugly19:58
anteayaso I would like this but does anyone else care?19:58
zarothe command laready exists in a plugin.  #link https://gerrit.googlesource.com/plugins/admin-console/+/master/src/main/resources/Documentation/cmd-ls-users.md19:58
jeblairanteaya: what's the use case?19:58
*** dims_ has quit IRC19:58
anteayafind the CI account that the owner can't remember the name19:59
anteayahappened all the time19:59
anteayawith bouncing ci's back to all users, I can't search that19:59
anteayasince it is a virtual group19:59
*** dims has joined #openstack-meeting19:59
zarobut clarkb and fungi suggested that it should be in Gerrit core so we should propose a change there.19:59
jeblairanteaya: why do you care about the name?19:59
*** jtomasek has quit IRC19:59
*** novas0x2a|laptop has joined #openstack-meeting19:59
*** bernardo-silva has quit IRC19:59
anteayaif we disable or reenable them19:59
clarkbzaro: ya, that suggestion came from the command already existing it just doesn't work right on that group19:59
anteayato find the account20:00
anteayaI used to search third party group often20:00
clarkbzaro: so ideally we can fix the existing command to work on the meta group thing20:00
zaroclarkb: i agree.20:00
*** eglynn has joined #openstack-meeting20:00
fungimore specifically, just suggested that virtual groups should have read api behaviors similar to configured groups20:00
zaroclarkb: yep.  good suggestion.20:00
jeblairanteaya: but i mean you have something to go on, right?20:00
anteayasometimes20:00
anteayasometimes not20:00
jeblairanteaya: either a comment in a change, or an email address?20:00
anteayaI never used to20:00
jeblairanteaya: how can you be interested in an account but start with nothing?20:00
*** SridharRamaswamy has quit IRC20:01
anteayareenable me from trinaths20:01
anteayawould be all I would get20:01
fungianteaya: when disabling a ci account, we can use e-mail address, ssh username, account id number...20:01
anteayaright20:01
anteayabut I don't ahve those now20:01
jeblairanteaya: trinaths does20:01
anteayathis was what I used to get frm the command20:01
*** VW_ has quit IRC20:01
anteayajeblair: ha ha ha20:01
fungihis ci system uses a specific ssh account name20:01
anteayayou havn't worked with him much20:01
*** aranjan has joined #openstack-meeting20:01
anteayaokay well if I don't need this fine with me20:01
anteayajust to let you know I used to have it and don't now20:02
anteayaand we are over time20:02
jeblairanteaya: i would suggest insisting on requests with correct information20:02
jeblairthanks all20:02
jeblair#endmeeting20:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:02
openstackMeeting ended Tue Dec 16 20:02:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-16-19.01.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-16-19.01.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-12-16-19.01.log.html20:02
ttxAlright! Anyone here for the TC meeting ?20:02
jaypipeso/20:02
jeblairo/20:02
markmcclaino/20:02
sdagueo/20:03
ttxrussellb, jgriffith, annegentle, mikal, mordred, devananda, vishy, dhellmann : around ?20:03
mordredo/20:03
devanandao/20:03
* ttx is hit by a cold, so please bear with me while I repeatedly blow my nose20:03
jgriffitho/20:03
*** grue_pm has left #openstack-meeting20:03
*** gholler has quit IRC20:03
ttx#startmeeting tc20:03
russellbo/20:03
openstackMeeting started Tue Dec 16 20:03:25 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
ttxOur agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttxerr.20:03
*** dims has quit IRC20:03
*** dkranz has quit IRC20:03
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:04
ttxone should redierct to the other20:04
ttx#topic Project structure reform specification20:04
*** openstack changes topic to "Project structure reform specification (Meeting topic: tc)"20:04
*** SridharRamaswamy has joined #openstack-meeting20:04
ttx#link https://review.openstack.org/#/c/138504/20:04
mikalMorning20:04
vishyo/20:04
ttxSo... I posted patchset4 early on Friday, most of the discussion since then have been minor comments, not objections20:04
*** IanGovett has quit IRC20:04
ttxSo I think this is ready for us to vote on -- would be great to come to a decision before the holiday break20:04
jaypipesttx: ++20:05
ttxAny last minute question we can address in-meeting ?20:05
*** e0ne has joined #openstack-meeting20:05
dhellmanno/20:05
*** MaxV has joined #openstack-meeting20:05
*** aranjan has quit IRC20:06
*** matrohon has joined #openstack-meeting20:06
ttxIf none, will approve when/if that reaches a majority, or we'll discuss it again next week :)20:06
*** Masahiro has joined #openstack-meeting20:06
dhellmannI have some reservations about how far we are lowering the bar for new projects. I like that we're lowering it, but I'd also like to include some things in this list like having an active team and such.20:06
*** sweston has quit IRC20:07
ttxdhellmann: I'd say that's for another review, when we start drafting governance documents to drive that new thing.20:07
dhellmannI'll leave some more detailed comments on this draft, but I wanted to raise the issue because I'm worried we're pushing the pendulum too far.20:07
*** sweston has joined #openstack-meeting20:07
*** neelashah has quit IRC20:07
sdaguedhellmann: that's this work item, right?20:07
sdague* Define new objective OpenStack project requirements (to replace old20:07
sdague  new-programs-requirements.rst) (kilo-2 milestone, assignee tbd)20:07
dhellmannttx: I would agree, except that this spec specifically calls out a list of things and then lists implementing that list as a work item20:07
dhellmannI'm looking at the list on line 10920:08
ttxdhellmann: the rules for accepting new projects will be defined in a specific document. This is just defining the direction ,20:08
*** yamamoto has joined #openstack-meeting20:08
russellbin "Recognizing all our community is a part of OpenStack"20:08
*** aysyd has quit IRC20:08
russellbso we're all looking at the same thing20:08
jaypipesdhellmann: how does one define "active" team?20:08
sdagueyeh, I guess I took the bits in this document as high level guidance20:08
dhellmannjaypipes: I'm not sure. How did we define it before?20:08
ttxright, it's more the general direction we are planning to go20:08
mikalSo, talk me through the ATC bit again20:09
jaypipesdhellmann: I don't know. :)20:09
russellbi'd agree with dhellmann that the guidance listed seems to make a point about how low the bar is20:09
dhellmannsdague: ok, I did not take the wording that way: "we propose that those should [be] considered 'OpenStack project' ..., as long as"20:09
mikalI read it as saying that only projects formerly in the openstack namespace grant atc status?20:09
sdaguedhellmann: yeh, I can see that20:09
ttxmikal: only projects in the openstack*/* namespace grant ATC status yes20:09
*** IanGovett has joined #openstack-meeting20:09
dhellmannmikal: this section is talking about new base rules for bringing projects into that namespace20:09
jaypipesmikal: I read it as "any project in the openstack/ code namespace grants ATC status"20:10
jaypipesmikal: not "formerly"20:10
mikalI think "those projects" is ambigious then20:10
anteayaI am reading the same as jaypipes20:10
mikalAnd perhaps should be "those projects in the OpenStack git namespaces"20:10
anteayamikal: I added a comment to that effect20:10
mikalanteaya: oh yeah, look at that!20:10
anteaya:D20:10
anteayamikal: I got ya20:10
dhellmannand what I'm worried about is that by dropping the bar *too* low, we dilute what "openstack" so far that it is meaningless20:10
*** Masahiro has quit IRC20:11
mikalI definitely parse that para as saying that projects from the former program structure grant atc status20:11
*** ChrisPriceAB has quit IRC20:11
dhellmannthis brings us way closer to my understanding of how the apache foundation works than I think we should go20:11
mordredwell, I think definition of the word openstack is a bit multifaceted20:11
ttxdhellmann: but you agree that this resolution is not forcing us to vote in one way or another in the future, right ?20:11
sdagueok, so can we do 1 of these at a time :)20:11
dhellmannttx: slippery slope20:11
markmcclaindhellmann: +120:11
ttxthis resolution describes our intent20:11
russellbdhellmann: or at least punting to let other groups decide it20:11
russellbdistros/products, and defcore, depending on how you look at it20:11
sdaguettx: I think a slight amount of word smithing20:11
ttxdhellmann: I'm fine with changing a blurb if you can propose something else20:12
ttxbeen doing that all week20:12
dhellmannyeah, I think if we clarify that this list is a set of principles, and that the actual rules to be developed later should be based on but not limited to these things, I could be happy with this20:12
*** yamamoto has quit IRC20:12
dhellmannttx; yeah, sorry, I've been fighting with setuptools all week20:12
ttxdhellmann: propose wording and I'll integrate it20:12
dhellmannok20:12
*** shashankhegde has quit IRC20:13
sdagues/ as long as:/ as long as they meet an objective criteria for inclusion (one of the work items below). This might include items such as:/20:13
sdaguedhellmann: do you think that would match the intent correctly?20:13
*** marcoemorais has joined #openstack-meeting20:14
dhellmannyeah, I like that20:14
dhellmanncan I steal it to add to the comment I'm writing?20:14
sdaguedhellmann: absolutely20:14
ttxmikal/anteaya: if you can give me the diff around "those projects" I can take the opportunity to clarify there too20:14
russellbthough maybe it's worth clarifying ... how much more do folks see being added to that list?20:14
jaypipesrussellb: not much, honestly.20:14
russellbmaybe not defined in the spec, but curious what folks are thinking20:14
anteayattx I did offer a comment with a suggested phrase20:15
mikalttx: I put alternate words in my comment, is that sufficient?20:15
ttxreading20:15
sdaguerussellb: I'm not sure I see much more being added, mostly clarification and specifics on 'the openstack way'20:16
markmcclainrussellb: I could envision us placing some kind of viability of the proposal20:16
ttxmikal: sure20:16
* ttx rev5s20:16
russellblike, "we think this is sane" ?20:16
sdaguemarkmcclain: it's got to be objective though20:16
*** MaxV_ has joined #openstack-meeting20:16
dhellmannI think it will be a big mistake for us to not have any criteria beyond that current list.20:17
markmcclainsdague: right it is objective, but if we don't do that then the results will be dictated to us20:17
*** esker has quit IRC20:17
russellbyeah, this is the disagreement i was trying to expose ..20:17
dhellmannunless by "openstack way" you mean our code review, test, requirements management, etc. policies20:17
jaypipeswhat are the things that people suggest to add to that list?20:17
*** dims has joined #openstack-meeting20:18
jaypipesmarkmcclain: the idea is to have a completely objective set of requirements; i.e. the opposite of what we have today.20:18
dhellmannjaypipes: what items from http://governance.openstack.org/reference/incubation-integration-requirements.html would you suggest we remove?20:18
ttxanything else while I'm at it ?20:18
*** DaveChen has quit IRC20:19
ttxbah, pushed20:19
jaypipesdhellmann: not having a major architectural rewrite. Project's scope should represent a measured progression for OpenStack as a whole. Project should have a clear plan to prevent long-term scope duplication.20:19
ttxhttps://review.openstack.org/#/c/138504/520:19
markmcclainjaypipes: I think objective is ideal but honestly if we set teh bar so low then the board and distros will apply the subjective criteria and we're left powerless to change it20:19
*** MaxV has quit IRC20:19
jaypipesdhellmann: the stuff about Programs.20:19
*** emagana has joined #openstack-meeting20:19
jeblairwell, that's the point of tags -- to help the board and distros and users sort through the large number of projects that are/will-be part of our community20:20
russellbi agree with what markmcclain is saying20:20
dhellmannjaypipes: I agree on the duplication item. I think I'm +0 on dropping the architectural rewrite. I'm less sure about the scope question; that probably should be reworded some.20:20
*** MaxV_ has quit IRC20:20
*** penick has joined #openstack-meeting20:20
jaypipesmarkmcclain: I don't see that happening. I just don't. We are the ones that are recommending tags for the board regarding maturity, trademarks, etc20:20
dhellmannjaypipes: yeah, programs go away, but some of that may apply to the teams20:20
*** MaxV has joined #openstack-meeting20:20
jeblairbecause it's a problem now that we don't actually have a good solution for20:20
devanandadhellmann: major integrated projects have and continue to go through architectural rewrites often20:21
devanandadhellmann: i don't see how that should be a bar to entry20:21
dhellmannjeblair: we can add tags without changing anything else20:21
ttxBefore discussing the next step, could we vote on the first one ?20:21
jaypipesttx: ++20:21
ttxI agree that's a far more contentious item20:21
zanebdhellmann: I'd like to see things like using oslo (where appropriate) and the global requirements list and that sort of thing20:21
devanandazaneb: ++20:22
dhellmanndevananda: yeah, that's why I'm +0 on dropping it20:22
mordredttx: I'm mildly concerned that we we wind up not having a definition for how horizontal teams are managed20:22
markmcclainjaypipes: I wonder if our signaling via tag will be interpreted correctly when more folks live in teh openstack git namespace20:22
mordredttx: not, mind you, that I expect us to grow any in the near future20:22
ttxmordred: most of them are code-backed those days, so I'd say, same as others20:23
devanandafollowing common/expected processes (oslo, pbr, sphinx doc, etc) - this is not explicitly called out20:23
mordredttx: it's possible we don't need codification there20:23
jaypipesmarkmcclain: I don't think it can get much worse than the existing binary integrated-release stuff, frankly.20:23
devanandabut is what part of "follow the OpenStack way", in my opinion20:23
sdaguemarkmcclain: so here's the thing, distros and others are making those calls already20:23
jaypipesmordred: why do we have to have a definition of how horizontal teams are managed>?20:23
russellbwell ... they're generally based on the integrated release, that's the base guidance20:24
mordredjaypipes: not saying we do - only that we might20:24
jaypipesmordred: why does the TC need to micromanage that?20:24
zanebdevananda: ++ maybe the "OpenStack way" and the "four Opens" should be separate entries in that list20:24
jeblairttx, mordred: some of them currently have scope beyond "what lands in their repos"20:24
jeblairjaypipes: ^20:24
markmcclainjaypipes: agreed…I just want to make sure we're not abdicating power that we wont be able to get back if we realize we're wrong20:24
*** mudassirlatif has quit IRC20:24
mordredbut largely, if we have: "will let multiple different teams potentially address the same problems" - what about when that's not desirable (we don't really want to grow two docs teams or two infra teams)20:24
*** VW_ has joined #openstack-meeting20:24
russellbmordred: i noted that on the review20:24
mordredcool. I'll go look at that20:25
markmcclainsdague: agreed, but we do box them in a bit because of how clear we designate stuff (even if we all agree needs work)20:25
jaypipesmordred: because ... common sense and communication?20:25
devanandazaneb: it gets tricky if we codify all of those. example: should every project use flask or pecan? this is not obvious. should they all use oslo? probably less contentious.20:25
russellbmordred: i haven't gone back to respond to ttx's response though20:25
ttxmordred: that was addressed in one of the comments. When we say "open development" that also means "collaborating"20:25
devanandazaneb: so while it's worth describing the expectation, I don't think it's good to state specific tools20:25
sdaguemarkmcclain: distros and ops are going to adopt parts of openstack because we stamp it,  but because it's actually good stuff20:25
mordredjaypipes: yah - it's entirely possible the answer is "we don't think it's a problem and will dael with it when it is"20:25
devanandazaneb: otherwhise we'll just end up with a meta requirements list20:25
ttxmordred: which is most cases would prevent duplicate horizontal teams if useless20:25
*** andreykurilin_ has joined #openstack-meeting20:25
devanandazaneb: and have to change it later20:25
ttxmordred: and yes20:26
zanebdevananda: yeah, I'd be happy with something vague ('follow the OpenStack way'), but I gather a lot of folks want only objective criteria20:26
*** wenlock has joined #openstack-meeting20:26
*** mudassirlatif has joined #openstack-meeting20:26
ttxwell, since now those are more inspirational than a final list of criteria, I think we should be good20:26
sdaguezaneb: I think mostly we'll want to call out what that is in the follow up20:26
ttxsdague: ++20:26
zaneb+120:27
*** mudassirlatif has quit IRC20:27
dhellmannright, I just want to leave room for actual discussion in that, and not paint ourselves into a corner with *this* spec20:27
ttxI think it's appropriately vague now :)20:28
sdagueyep20:28
markmcclainsdague: right that's what we want ops deploying it because it is good stuff, I'm wondering if tagging is delays our decision proces until too late20:28
*** bvandenh has quit IRC20:29
*** KLevenstein has joined #openstack-meeting20:29
ttxso please cast your vote and we can start discussing what level the bar should exactly be set at.20:29
*** igordcard has joined #openstack-meeting20:29
russellbi want to give it another in depth read and consideration, i'll vote tomorrow20:29
ttxbecause yes, while everyoen agrees there shoud be some bar, your mileage may vary20:29
ttxrussellb: ack20:29
ttxI'll leave it open today anyway to give annegentle a chance to register her vote20:30
ttxsince she +1ed the previous rev and couldn't attend the meeting20:31
*** noslzzp has quit IRC20:31
ttxSo, assuming this is approved, next step here is to communicate about the proposed way forward more heavily, so that it doesn't take anyone by surprise.20:32
mikalI think we'll need to do that both sides of the holiday break obviously20:32
ttxThen we'll probably tackle the bar height20:32
mikalIf we do it this week and next we'll miss a bunch of people20:32
*** prad has joined #openstack-meeting20:32
dhellmannmikal: ++20:32
ttxmikal: yes20:32
*** prad has quit IRC20:33
ttxwork item says end of dec / start of jan20:33
*** wenlock has left #openstack-meeting20:33
mikalttx: oh, fair point20:33
mikalWhat about ttx doing an openstack hour youtube thing explaining it?20:33
mikal(in addition to email etc etc)20:33
ttxew20:33
fungiyou could wear a fun hat20:33
mordredfungi: I was going to say that20:34
mikalSock puppets?20:34
ttxmore likely a giant handkerchief20:34
Rockyg+1 for ttx on youtube20:34
mordredfungi: although I was going to say pointy20:34
ttxwell, we could certainly do some IRC town hall thing20:34
fungiresurrect the irc all-hands20:34
jeblairi think email is quite enough20:34
ttxso that people can throw tomatoes at me20:34
mordredjeblair: ++20:34
*** Mandell has joined #openstack-meeting20:35
fungiyeah, an ml thread should be fine20:35
ttxbut yeah, blog+email is probably the most async20:35
jeblairparticularly because it can be drafted and comments solicited20:35
*** mudassirlatif has joined #openstack-meeting20:35
ttxLast questions/ comments on this topic ?20:35
*** ddieterly has quit IRC20:35
ttxWe can go back to it in Open Discussion, time permitting20:36
ttx#topic A look at proposed openstack-specs20:36
*** openstack changes topic to "A look at proposed openstack-specs (Meeting topic: tc)"20:36
sdaguettx: thanks for all your efforts here20:36
ttxsdague: thx!20:36
ttxThere are two openstack-specs proposals up for review:20:37
ttx#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-specs+branch:master,n,z20:37
ttxSo far I wouldn't describe them as heavily reviewed yet20:37
*** mudassirlatif has quit IRC20:37
ttxTC members have +2/APRV on that repo20:37
ttxso we definitely should20:37
* mikal adds those to his review queue20:37
ttxthat said, we need PTLs to review those (TC is mostly there to collect votes)20:38
ttxnot sure on the way forward there20:38
Rockygcan you/we socialize the hog guidelines to the ops ml for a couple of weeks before finalled?20:38
ttxI thihn the fly below radar of most teams20:38
* mordred has added to watch list20:38
Rockygs/hog/log/20:38
ttx"I think they fly" I mean20:38
dhellmannttx: should we bring it up at the project meeting?20:38
mikalttx: mention those reviews in the release meeting perhaps?20:38
mikaldhellmann: jinx!20:38
ttxdhellmann, mikal: yes, was thinking we could have some recurring item20:39
dhellmannmikal: thought thief!20:39
dhellmannttx: I like that.20:39
*** mrda-away is now known as mrda20:39
*** ddieterly has joined #openstack-meeting20:40
ttxOK, I'll make that happen, mention it in open discussion in meeting today and start doing that more regularly in futur emeetings20:40
mikalttx: sounds like a plan to me20:40
*** rosmaita_ is now known as rosmaita20:40
Rockygthanks!20:40
ttxThat brings us post-holiday season probably on those.20:40
ttxIs any of those so urgent they can't wait until new year ?20:41
*** marcoemorais has quit IRC20:41
*** marcoemorais has joined #openstack-meeting20:42
ttxI guess not20:42
ttx#action Cross-project meeting chair (so far ttx) shall put openstack-specs on the Cross-project meeting agenda as a recurring item20:43
ttx#topic Housekeeping changes20:43
*** openstack changes topic to "Housekeeping changes (Meeting topic: tc)"20:43
ttx* sort oslo libraries (https://review.openstack.org/140934)20:43
ttxFor that one, I'd say, whatever is the most convenient for updates. Will approve tomorrow morning unless someone -1s20:43
*** pelix has quit IRC20:44
*** rushiagr is now known as rushiagr_away20:44
*** mrunge_gone has quit IRC20:44
ttx#topic Open discussion20:44
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:44
ttxAnything else, anyone ?20:45
ttxSomething we should be doing that we didn't do ?20:45
zehicleo/20:45
ttxzehicle: go for it20:45
*** ChuckC has quit IRC20:46
zehiclethanks - a reminder that for the bylaws changes, we have need for people to vote to get quorum20:46
zehicledoes not matter if they are for or against really, we need votes or everyone is effectively "against"20:46
zehicleand the voice of the people who bother to show up will not be heard20:46
zehicleso, please remember to "rock the vote" or similar as we get closer20:47
* zehicle ends PSA20:47
ttxindeed, that vote will need significant publicity to reach quorum20:48
zehiclepart of this vote includes lowering quorum based on historical data20:48
ttxFor the next steps of the project structure reform, from my various discussions with people I expect the most contentious item will be the definition (or lack thereof) of a compute-{core,base,thing,layer,ring}. The spec only says we will define tags, and leaves that question for the future20:48
dhellmannzehicle: do you have a link handy to the published version of the final proposed bylaws change?20:49
* dhellmann has a local meetup this week20:49
russellbthose word docs were so hard to read ...20:49
*** ddieterly has quit IRC20:49
*** mdorman has joined #openstack-meeting20:49
*** klindgren_ has joined #openstack-meeting20:49
ttxI expect the exact definition of the bar to entry to not be that contentious (famous last words)20:49
dhellmannrussellb: yeah20:49
russellbshould have been plain text, reviewed via gerrit :)20:50
sdaguerussellb: who knew that ms word is a bad revision control system :)20:50
russellbikr?20:50
dhellmannttx: I think I probably want that bar a fair bit higher than a lot of other people20:50
*** asalkeld has joined #openstack-meeting20:50
*** vijendar has joined #openstack-meeting20:50
devanandattx: I commend your optimism :)20:50
ttxdhellmann: higher than Jay, as far as I can tell20:50
dhellmannttx: I suspect others, too, but I may be less optimistic than you :-)20:51
*** shashankhegde has joined #openstack-meeting20:51
devanandaI probably want the bar higher than some, too.20:51
ttxIt will be easier to tackle those issues once we have an idea of where we are going (the spec) and we cut the problems into smaller pieces20:51
sdagueso, probably a worth while part of the setting the bar conversation is to make sure we keep the "why" around20:51
*** unicell has quit IRC20:51
devanandattx: do you have a format in mind for that discussion?20:51
dhellmannhttps://review.openstack.org/#/c/131422/1/reference/incubation-integration-requirements.rst was my earlier stab at lowering the bar a little20:52
*** carl_baldwin has quit IRC20:52
ttxdevananda: I think we can work from proposals and counter-proposals20:52
dhellmannsdague: ++20:52
devanandattx: I think seeing a few new tags in a concrete proposal would help set the conversation20:52
ttxdevananda: first ML thread, then opiniojnated proposals, then consensual proposal, then vote20:52
*** ajo_ has quit IRC20:52
*** mudassirlatif has joined #openstack-meeting20:52
*** mudassirlatif has quit IRC20:53
ttxdevananda: basically what we followed for the the spec. Except we had to insert a face-to-face-or-video explanation as step 2.520:53
*** mchalla has joined #openstack-meeting20:53
ttxso that we get a better idea of what was consensual and what was not20:53
russellbwhich i think in the spirit of openness, we may want to try to avoid that if we can20:54
ttxagreed20:54
*** Salman_ has joined #openstack-meeting20:54
*** mchalla has quit IRC20:54
ttxsdague: yes, in the end all that's left of this spec document might just be the "why" :)20:55
sdagueyeh20:55
sdaguedhellmann: I'm going to throw onto your review20:55
*** carl_baldwin has joined #openstack-meeting20:55
dhellmannsdague: comments, and not rotten tomatoes, I hope20:56
*** _nadya_ has quit IRC20:57
ttxOK, if nobody else has a comment, we can close early. I'd welcome chairing help for the next meeting if some of you can stay around. Not in the best shape to have a difficult discussion right now20:57
*** breton has left #openstack-meeting20:57
sdaguedhellmann: yep20:58
dhellmannttx: I'll be there20:58
ttxdhellmann: cool. If I pass out, just continue and ignore me20:58
*** mchalla has joined #openstack-meeting20:58
ttx#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Tue Dec 16 20:58:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-12-16-20.03.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-12-16-20.03.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-12-16-20.03.log.html20:59
*** Rockyg has quit IRC20:59
*** Rockyg has joined #openstack-meeting21:00
*** salv-orlando has quit IRC21:00
*** chuckC_ has joined #openstack-meeting21:00
ttxcourtesy PTL ping: dhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov, mikal: around ?21:00
*** salv-orlando has joined #openstack-meeting21:01
morganfainbergo/21:01
notmynamehere21:01
dhellmanno/21:01
eglynno/21:01
ttxnot forgetting mikal today21:01
jogoo/21:01
asalkeldo/21:01
mesteryo/21:01
mfischo/21:01
morganfainberghehe21:01
notmynamettx: thanks. your courtesy ping is very helpful21:01
mesterynotmyname: ++21:01
swestono/21:01
mesterythanks ttx!21:01
mikalHi21:01
* fungi waves21:01
ttx#startmeeting crossproject21:01
openstackMeeting started Tue Dec 16 21:01:49 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
*** SridharRamaswam1 has joined #openstack-meeting21: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
SergeyLukjanovo/21:01
ttxOur agenda for today:21:01
*** SridharRamaswamy has quit IRC21:01
*** marcoemorais has left #openstack-meeting21:01
*** maishsk has joined #openstack-meeting21:02
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:02
ttxDo we have joehuang around21:02
*** padkrish has quit IRC21:02
*** ryansb has joined #openstack-meeting21:02
*** aranjan has joined #openstack-meeting21:02
ttxLet's invert the two agenda items then to give him a chance to join21:03
*** MaxV has quit IRC21:03
*** balajiiyer has joined #openstack-meeting21:03
ttx#topic Providing an alternative to shipping default config file (ttx)21:03
*** openstack changes topic to "Providing an alternative to shipping default config file (ttx) (Meeting topic: crossproject)"21:03
*** balajiiyer has left #openstack-meeting21:03
ttxThere was a recent thread on the operators ML complaining about the removal of default config files from git:21:03
ttx#link http://lists.openstack.org/pipermail/openstack-operators/2014-December/005658.html21:03
ttxThat thread was derailed to talk about packaging, but I think the original concern is valid: default config files have value to operators and we removed them21:04
ttxNow, we removed them for a reason: it was pretty painful to keep them in sync and often resulted in various failures21:04
*** padkrish has joined #openstack-meeting21:04
dhellmanncan we build them in the docs, instead of the source tree? that would make them available but not gum up the git repos with more automated changes or files that are out of date21:04
ttxSo my question is, what can we offer (ideally a standard solution) to give operators those files back, while not restoring the original problem21:04
ttxdhellmann: fung i suggested something of that vein yes21:04
ttxfungi*21:04
dhellmannand by docs, I mean the developer docs so they are updated on every commit21:04
ttx generate and post the sample as part of dev docs21:05
dhellmannalthough it certainly wouldn't hurt to add them to the other docs as well21:05
notmynamearen't more docs moving into the source tree?21:05
asalkeld+121:05
fungiahh, yes zigo said he wasn't going to be around for the meeting, but wanted to pass along a recommendation of having the sdist step generate sample configs to include in the tarballs21:05
mfischthat would work for me for what I need the sample files for21:05
morganfainbergfungi, that was my view, if sdist can do that, i'd like it there21:05
dhellmannmfisch: which solution would work for you?21:05
ildikovdhellmann: I would suggest to add it OS-manuals21:05
ttxso the problem with the "just have sdist run tools/config/generate_sample.sh -b . -p nova -o etc/nova" is that the result heavily depends on the env it's being run on21:05
dhellmannildikov: the problem there is that isn't rebuilt on every merge into a project21:05
ildikovdhellmann: I think that would be clearer as we have already a whole config reference there21:05
mfischdhellmann: anywhere in a tree I can get to21:05
ttxI like the docs post because we run it21:06
fungiand while i agree, i think having the code doc build step also generate them and include them somewhere would be a useful addition21:06
morganfainbergi'm fine with either solution21:06
toabctlsome projects have a tox genconfig env for building the config sample21:06
mfischwhich sometimes works21:06
morganfainbergi'd like to evict the sample config from keystone if we had a better alternative21:06
morganfainbergsuch as docs21:06
ildikovdhellmann: yes, I know, it just messes up a bit the purpose of each docco we have21:06
*** AJaeger has quit IRC21:06
dhellmannfungi: having the sdist build it might be challenging, since the tool uses entry points to find the options so the code has to be "installed" for it to work21:06
morganfainbergbut i know until we have that alternative keystone will continue to do the manual updates prior to releases.21:07
russellbone sucky thing is after you've run it, you have a file sitting around that may or may not be accurate anymore21:07
dhellmannalso it needs the dependencies installed21:07
ttxdhellmann: ++21:07
fungittx: we control the environment for the sdist built in our post jobs which generates our tarballs21:07
russellband having to run tox every time you want to look at a config reference is annoying21:07
mfisch+1 russellb21:07
bknudsonhaving the sample config in tree is kind of handy since it's easier to see what the output will look like in a review.21:07
*** mudassirlatif has joined #openstack-meeting21:07
ttxfungi: right, but encouraging others to run it might be counterproductive21:07
jogowould having 'tox -egenconfig' be a standard help at all?21:07
fungidhellmann: we already do when we run sdist21:07
*** jlk has joined #openstack-meeting21:07
mfischand keeping your mac up to date on 10 different requirements files from 10 projects daily is not cool21:07
ildikovdhellmann: maybe we can refer the developer docs from manuals21:07
*** KLevenstein has left #openstack-meeting21:07
dhellmannfungi: oh, because we're running it under "tox -e venv"?21:07
mfischI look at these about once every few weeks21:07
fungidhellmann: yep21:07
morganfainbergbknudson, if it was generated like docs - and visble that would be fine as well, -edocs instead of -egenconfig vs in-tree21:07
*** Mandell has quit IRC21:07
ttxjogo: that would add a bit of predictability for sure21:07
fungittx: i took the recommendation not as suggesting consumers rerun sdist21:08
*** aranjan has quit IRC21:08
dhellmannfungi: ok, in that case as long as we're doing it in our build and not when someone checks out the source and runs "python setup.py sdist" I think it's ok21:08
fungittx: but rather that the sdist _we_ build could include those files21:08
ttxIdeally we would adopt a common solution, so that ops don't have to find out the way each project decided to make that default config file available21:08
fungivia whatever mechanism21:08
*** SridharRamaswam1 has quit IRC21:08
morganfainbergttx +1 for common solution21:08
mfisch+1 for common too21:09
dhellmannfungi: I wonder if that would require any manifest trickery, but that's an implementation detail21:09
morganfainbergthat doesn't require gating on a static file in the tree.21:09
fungiand yes, that's what i took as the reason for discussing it in the cross-project meeting. standardizing on a mechanism and location21:09
dhellmannttx: ++21:09
*** Haneef has quit IRC21:09
ildikovjogo: for instance in Ceilometer we have it21:09
ttxfungi: I know zigo runs sdist to rebuild tyarballs from git, that's why I mentioned it21:09
*** otter768 has joined #openstack-meeting21:09
dhellmannfungi: fwiw, some projects have not adopted the new config generator, and that needs project-specific args, so we probably want a tox.ini or shell script interface21:10
fungittx: actually he said he doesn't21:10
*** colinmcnamara has joined #openstack-meeting21:10
fungittx: he tars up the contents from git plus files added to create the debian source packages21:10
ttxfungi: ah. pretty sure he used to though21:10
dhellmannfungi: in fact, probably a shell script called by tox, so you can "tox -e venv -- tools/genconfig.sh" and other devs can "tox -e genconfig"21:10
fungidhellmann: agreed, but i think where the opposition on the ops list is coming from is "i don't want to have to run something to generate sample configs, just tell me where to get them from"21:11
ttxSo I think tox -e genconfig + inclusion in dev docs sounds like the way to go21:11
*** nellysmitt has joined #openstack-meeting21:11
*** ChuckC has joined #openstack-meeting21:11
dhellmannfungi: right, I'm just proposing the common API for our infrastructure to use to build them when packaging21:11
sdaguefungi: also, it's not always simple to set up the env21:12
fungidhellmann: sure, that works for me as a solution21:12
dhellmannupdate the package job to call "tox -e venv -- tools/genconfig.sh" before "tox -e venv -- python setup.py sdist"21:12
fungisdague: agreed, that's probably the largest reason why they don't want to have to run something to generate them21:12
fungidhellmann: yep. and add a similar step to the doc build job for the individual projects too21:12
dhellmannright21:13
ttxI'd say the next step is a openstack-specs spec21:13
fungiand then hyperlink those files in the template or something21:13
*** amitry has quit IRC21:13
dhellmannor literalinclude21:13
ttxso that we can get ops and PTLs +1s on it21:13
*** egallen has joined #openstack-meeting21:13
RockygOps need to be able to get previous versions, too.21:13
Rockygnot just current and release21:14
dhellmannRockyg: previous versions with what granularity?21:14
jeblairare we sure it's a good idea to make building an sdist more complicated?21:14
fungiRockyg: we'd need a definition of "previous versions"21:14
ttxjeblair: I suggested having tox -e genconfig + inclusion in dev docs21:14
dhellmannjeblair: this would be an optional step our build job would do, and that wouldn't be done by someone building an sdist by hand elsewhere21:14
RockygSo, if a team is running say a month behind the head of tree...21:14
jlkthings with stable/<versoin> ?21:14
sdaguejeblair: how much more complicated is sdist made by it?21:14
*** otter768 has quit IRC21:14
jeblairi mean, everyone knows how to build an sdist, right?  except we're proposing that _openstack_ have a different way of building them, so if you want to build it and get the same content, you have to do something extra21:14
dhellmannjeblair: well, that's a fair point21:15
toabctlRockyg: previous versions are always buildable from git. and the doc changes are already documented between openstack releases.21:15
ttxRockyg: that's a good argument in favor of storing them in tarballs21:15
jeblairdhellmann: what's the reason not to generate them in the sdist step?21:15
Rockygright.  and the ops are saying they don't want to build the sample configs from git21:15
dhellmannjeblair: in order for the config generator to work the code for the project and all of its dependencies need to be installed so the entry points work21:16
*** weshay_bbiab is now known as weshay21:16
RockygYes.  Tarballs will probably satisfy most of the devops and the ones it doesn't are likely very capable of rebuilding from git21:16
ttxjeblair: it's because random people running python setup.py sdist will end up with a partial config file21:16
dhellmannjeblair: if I check out a git tree and run "python setup.py sdist" it shouldn't install anything21:16
fungiif someone wanted to build a service that generated all the iterated changes for sample configs for each project and stored them in a git repository, that would be one solution to the "history" problem i guess21:16
sdaguedhellmann: hmph, is there a way around that ?21:16
jeblairdhellmann: got it21:16
mfischsorry catching up but previous versions are awesome21:16
dhellmannsdague: nothing reliable21:16
mfischthat way I can see when an item was added or a default changed21:16
*** nellysmitt has quit IRC21:17
mdorman+1 on prev. versions21:17
mdormanon some granularity21:17
Rockygfungi: that was what one ops guy proposed21:17
fungiwe just don't want to be including autogenerated sample configs into project git repos if we can help it. and if we do it would need to be something along the lines of the reqs/tx proposal changes21:17
ttxso to have previous versions, the easiest is to store it in tarball21:17
sdagueso... is milestone level granular enough?21:17
dhellmannjeblair: what if we publish the files with a version number matching the sdist, but not *in* the sdist?21:17
mdormani like the idea of a sample configs git repo21:17
ryansb+121:17
mfischthat would work for us21:17
dhellmannmdorman: I think that's a reasonable idea, but it's orthogonal to publishing the default config21:18
ildikovmfisch: the os-manuals config reference has sections for each project which show changes21:18
mdormansdague: i would think milestone level would be good, assuming there aren’t config changes w/in a milestone (which i would hope not)21:18
fungiand something anyone can generate and publish as an advisory dataset with or without our assistance21:18
*** joehuang has joined #openstack-meeting21:18
sdaguemdorman: well there are config changes all the time21:18
dhellmannmdorman: all config changes happen between milestones, that's when the development happens :-)21:19
sdaguecan you explain "assuming there aren’t config changes w/in a milestone"21:19
mdormanmaybe i misunderstand what milestone means21:19
mfischildikov: thats been discussed in the thread, its wrong many times, Ive filed bugs21:19
ttxmdorman: it's a tag21:19
eglynnmdorman: we've no way of holding back config changes from master until the milestone is cut21:19
fungimdorman: config changes happen when libraries get updated which provide new config options into the servers, for example21:19
sdagueso we have 3 milestones (roughly ever 7 weeks) then a release21:19
mdormanoh, ok. i thoguht milestone == icehouse, juno,kilo, etc.21:19
sdagueso if at the milestones we had samples out, would that be granluar enough21:19
ildikovmfisch: it can happen that it's not perfectly up to date, but then we should improve that process how it is updated21:19
dhellmannah, no, those are releases21:19
jeblairdhellmann: interesting; at least there's a clear delivery artifact and process, though perhaps less convenient to consume?  actually i don't know about that last part.  maybe it's more convenient.21:20
Rockygmaybe a notification on each merge that modifies the config?  That's really waht ops needs.  What changed and which build it changed in.21:20
joehuanghello, joehuang is just being able to logon the irc. the network is not stable to connect to freenode.21:20
mfischildikov: not perfectly up to date does not explain the bugs. sorry21:20
fungimdorman: this is part of where the development workflow pain is coming from... new oslo lib has new config options which suddenly cause teh sample configs on every project on multiple branches to be out of date21:20
dhellmannjeblair: yeah, as a separate file you can curl or whatever. And we can link to the directory full of them from the docs, and not have to make the docs build more complex either21:20
notmynameit seems like all the things being asked for (by users of the config files) are solved by "keep a config file in the source tree". the pain point is devs keeping it up to date?21:20
*** colinmcnamara has quit IRC21:20
fungiRockyg: the changes which alter sample configuration aren't in the same projects which need the sample configs21:20
ttxjoehuang: we inverted the two agenda topics. Currently discussing default config files21:21
mdormanfungi:  understood, thanks21:21
ildikovmfisch: ok, I will check the bugs21:21
russellbthe pain came from the config file including options from other libs21:21
russellb(the pain for devs)21:21
Rockygfungi yeah, it's a bitch;-)21:21
ttxjoehuang: should be back on cascading in 10-&5min21:21
dhellmannnotmyname: some of the configuration options are defined in libraries, not under the control of the app, and so the file can become out of date without the app devs realizing it21:21
jeblairnotmyname: perhaps -- we could have robots keep it up to date, though there's also the idea that autogenerated content shouldn't be in vcs.21:21
russellbotherwise it's straight forward to auto generate it21:21
sdaguenotmyname: right the pain is because libraries can define options21:21
harlowjaklindgren_ pinnnng21:21
*** andreaf has quit IRC21:21
sdagueso the valid config for a project depends on the library versions21:21
jogoRESTful config-files-as-a-service21:21
mfischwould it be a problem to generate it into another repo to not pollute yours?21:21
joehuangsorry it takes half an hour for me to connect to the channel21:21
mfischa cronjob that generates them into github solves most of my needs21:22
mfischbut not everyone21:22
mdorman+1 yeah it seems like a separate sample config repo is a goodsolution for both sides?21:22
jeblairbut we could certainly have the proposal bot keep it up to date for each project-branch combo21:22
*** jprovazn has quit IRC21:22
sdagueso that would be the post merge publish21:22
morganfainbergjeblair, we could just have proposal bot put the configs into the main trees as well21:22
sdaguejeblair: yeh, though if we did that we need to make it so it's basically a noop test job21:22
sdaguebecause these are going to change *a lot*21:22
jeblairmorganfainberg: yeah, that's what i was thinking; the 'other git repo' convo started mid stream in my response :)21:23
fungijeblair: i wonder what we'd trigger that on... or just a periodic job like we do for translation updates?21:23
dhellmannmorganfainberg: adding them to the tree after the merge means they are out of date if you check out the version with the merge21:23
morganfainbergand while i know it's not a snappy turn around (instantaneous) it does meet our current needs.21:23
dhellmannexcept that the config in any given repo will be wrong after an option is changed or added21:23
sdagueit's also only accurate if you have the same library versions21:23
dhellmannand that21:23
dhellmannthe sample config is not based on the application; it does not belong inside the application21:23
jeblairisn't that true for making it a release artifact as well?21:24
bknudsonsame library versions as what?21:24
morganfainbergi think it would be accurate enough, maybe even add a "last updated <XXXX>" line?21:24
fungidhellmann: yeah, i think it's never really up to date necessarily anyway, and the only way we enforced it mostly before was to bring development on a project to a halt until it got corrected21:24
sdaguebknudson: as the build21:24
dhellmannbknudson: if oslo.messaging adds an option, your config file is out of date21:24
morganfainbergso you know what the range that change spans?21:24
mfischgiven a time reference I can go back to the project repo and see the change21:24
dhellmannfungi: yeah, it was easier when all of the options were inside the app because of the incubated code21:24
mfisch"why guy changed this default from A to B and whats the commit log say as to why"21:24
jeblairsdague, fungi: i was proceeding under the assumption that infrequent repo updates of the config file would be okay, based on the idea that publishing them with tarballs was okay.21:24
sdaguebknudson: the version of all the libraries that have options is also needed in addition to the version of the project source21:24
bknudsonseems like that would always be the case since a range of library versions are supported21:24
*** VW_ has quit IRC21:25
morganfainbergso mfisch, as long as you know when they were updated and you have timeframes on the updates - that meets your needs?21:25
*** SlickNik has joined #openstack-meeting21:25
fungijeblair: that seems fine to me too. i'm not convinced that up-to-the-minute sample configs were part of the request21:25
dhellmannbknudson: true, which is why the most accurate way to get a sample file is to make it yourself using the versions of all of the libs you're running on your system -- but that's much less convenient21:25
mfischideally I'd have every single change but I could deal with a time reference21:25
morganfainbergX change spans commit aef123 to fff34221:25
toabctlhm. if ops are running code from git they *must* generate their config by their own.because the combination of config options is different depending what you have installed. so even if there is a repository with the config files for the different projects I think it's very unlikely that the libs used to generated the configs have the same version than in the ops environemtn21:25
fungimfisch: also, again, there's no discrete mapping from a sample configuration back to a commit in a particular git repo21:26
dhellmanntoabctl: right. I thought the separate repository was for hand-crafted examples of specific use cases ("here's nova with qpid" and "here's nova with rabbit")21:26
ttxso the config has b21:26
morganfainbergtoabctl, remember these are strictly sample configs - an example reference. you don't need them to configure a service. most ops/deployers run from a stable release afaik21:26
ttxer21:26
asalkeldmaybe the libraries need their own config files21:26
russellbasalkeld: +121:26
dhellmannfungi: we could have the config generator put version strings at the top in comments21:26
bknudsonhaving the library versions in the sample config would be good.21:27
mdorman+121:27
jogodo we have a clear idea of what the constraints of the issue are. What specific cases are we trying to address. As there may not be a one size fits all answer21:27
morganfainbergbknudson +121:27
*** dkranz has joined #openstack-meeting21:27
fungidhellmann: does that get you info on where each config option came from and the history of the code which determined it?21:27
toabctlbknudson: +121:27
ildikovjogo: +121:27
ttxjogo: yes, I feel like we won't find the solution here, the problem space is more complex than it seems21:27
dhellmannfungi: not entirely, no, but we know where each option comes from so I think we can include that in the output if we don't already21:27
dhellmannby "know" I mean we know which entry point21:28
Rockyguse case:  bug in library.  want to update.  Does it change the config?21:28
dhellmannttx: so, someone should work up a spec?21:28
fungidhellmann: i was referring to mfisch's request to be able to figure out why a config option changed by looking at the sample config itselg21:28
ttxAnyone volunteering to summarize the problem and the perveived solutions ?21:28
fungiitself21:28
ttxdhellmann: yes21:28
jogoRockyg: that is a great example of a use case, thanks21:28
*** MaxV has joined #openstack-meeting21:29
dhellmannfungi: yeah, that would require a much much smarter config generator that pulled in git commit messages or something21:29
ttxdhellmann: or at least an ML thread if there is not enough meat for a spec yet21:29
dhellmannttx: I'd rather go ahead and start with a skeleton spec and have some use cases proposed there21:29
Rockygdhellmann ++21:29
dhellmannbut as I'm not going to write it, I'll leave that decision up to the author :-)21:29
fungiso i think as a takeaway we can at least summarize some of these options as doable and take the temperature on the ml thread>?21:29
ttxdhellmann: is that a rhetorical "I" or are you volunteering ? :)21:29
dhellmannfungi: ++21:30
mfischMay I request a CC to the operators list on this discussion?21:30
fungimfisch: that was the ml thread i was talking about21:30
mfischok21:30
mfischI thought you meant -dv21:30
mfisch-dev21:30
fungimfisch: the one mentioned in the meeting agenda21:30
ttxfungi: you up for that ?21:30
Rockygmfisch:  it will most likely move to dev, but when it does, it will get announced on the ops list as moving21:31
mfischperfect21:31
*** neelashah has joined #openstack-meeting21:31
fungittx: sure. i'll take a crack at ml as next step, then see if someone else wants to step up for a spec if people can agree on one particular solution as better than the others for the requested purpose21:31
ttx#agreed summarize some of these options as doable and take the temperature on the ops ml thread?21:31
ttx#action fungi to take a crack at ml as next step, then see if someone else wants to step up for a spec if people can agree on one particular solution as better than the others for the requested purpose21:32
ttxfungi: many thx21:32
Rockygfungi: ask for use cases that can be included in spec.21:32
fungiRockyg: great idea--will make sure i do21:32
RockygFungi: and thanks for taking this on21:32
fungiyw21:32
ttxok, back to the first agenda item21:32
mfischthanks for the discussion this has been a thorn for sometime21:32
joehuangthanks21:32
ttx#topic Next steps for cascading (joehuang)21:32
*** openstack changes topic to "Next steps for cascading (joehuang) (Meeting topic: crossproject)"21:32
ttxSo... a bit of history first21:32
ttxjoehuang posted about his "cascading" approach to scaling OpenStack back in October21:32
ttxThere was a thread back then, mostly asking about the difference with the "Cells" approach21:33
ttxThen it was discussed as part of the "scaling approaches" cross-project session in Paris21:33
ttxNow joehuang is wondering about the next steps, which prompted a new thread21:33
ttxThat thread mostly questioned the need and priority for another scaling approach21:33
ttxIf I had to summarize I'd say that:21:33
bknudsonhttps://etherpad.openstack.org/p/kilo-crossproject-scale-out-openstack ?21:33
notmyname"scaling openstack" == functional code or the organization?21:33
ttx(1) the cascading approach requires important changes and is heavily cross-project: therefore it requires strong buy-in from everyone in order to be successful21:33
russellbnotmyname: code21:34
ttx(2) nobody (except its promoter) was really excited by the idea of spending any time on this21:34
*** emagana has quit IRC21:34
ttx...so I don't really see this effort as succeeding, unless the tide turns21:34
bknudsonwhich effort? cells?21:34
*** bdpayne has quit IRC21:34
ttxbknudson: cascading21:34
russellbbknudson: cascading ...21:34
* ttx shall post a few links21:34
russellbttx: i agree with that summary, that's my take as well21:35
dansmithttx: same21:35
joehuangbut it's not scaling out for cascading21:35
Rockygttx: it's on telco-NFV todo list, but it needs lots of architecting and design.21:35
RockygIt's a big issue in telco.21:35
mesteryttx: Ack21:35
joehuangit's about multi-clouds intergation21:35
ttxhttp://lists.openstack.org/pipermail/openstack-dev/2014-September/047470.html21:35
dansmithI think that's the key bit: the real goal is integrating multiple-vendor openstack, not really scaling21:36
ttxoriginal post ^21:36
dansmithand that is the heart of why there is little interest, IMHO21:36
jogodansmith: yeah, that part scares me21:36
russellbor even if it was all the same vendor, it's still a huge scope21:36
jogodansmith: there be dragons to support multi vendor21:36
*** esker has joined #openstack-meeting21:36
russellband i don't think that's a smart next step for us to try to tackle21:36
*** julim has quit IRC21:36
ttxI just want joehuang to have a clear answer21:36
ttxbecause we may not have been clear enough in the past21:36
ttxon interest/priority/effort21:37
joehuangbut the implementation is not hard, just add new driver.agent for OpenStack it self. PoC only about 15K source code21:37
alaskirussellb: agreed.  the pre cells solution of zones was very similar to this and was abandoned due to many obstacles that couldn't be overcome at the time21:37
dansmithttx: what format do you want that in, and from who?21:37
sdaguerussellb: agreed, I think it's something that comes after a cells model is well established21:37
*** MaxV has quit IRC21:37
RockygSo, too much work to start building.  The work should go into getting a design and architecture that addresses the dragons21:37
*** ddieterly has joined #openstack-meeting21:37
joehuangeach one service may have a driver about 2~4k source code21:37
russellbjoehuang: i strongly disagree that this is not hard or complicated :-)21:37
sdagueRockyg: well, more importantly, there are existing scaling efforts that we should get nailed down21:37
sdaguefirst21:37
ttxdansmith: ideally that meeting would put everyone on same page21:37
morganfainbergjoehuang, 15k is a large amount of additional code.21:38
joehuangand the driver/agent can be decoupled from the tree21:38
sdagueand once that's a solved problem, and cross project, then something like this could be considered21:38
morganfainbergimo21:38
mesterymorganfainberg: ++21:38
russellbif you want to maintain some out of tree drivers, by all means, have at it, it's open source :)21:38
RockygCan those scaling issues be addressed so that they inform the multi cloud effort?21:38
jogojoehuang: showing a proof of concept is not hard doesn't mean a full implementation is easy21:38
sdaguejogo: exactly, see: cells v1 and the attempts to make it feature complete in Nova21:39
russellbi fundamentally don't see the "multiple cloud effort" as something we should make a priority right now (if ever)21:39
jogosdague: great example21:39
Rockygsdague: like get the architecture of the scaling firmed up so Joe's effort has a reasonable base to build on21:39
fungii assume that's 15k lines of code, not 15k bytes of code21:39
joehuangit's already opensource in stackforge/tricircle21:39
dansmithrussellb: I agree, it's just not a thing we need to concentrate on right now, hard or not (even though we know it's hard)21:39
sdaguerussellb: agreed, at least in the short term21:39
morganfainbergfungi, that was my assumption21:39
joehuangfor cinder, the driver is about only 2k source code21:40
jogojoehuang: have you gotten this running and passed tempest-full in a multi cloud deployment?21:40
ttxjoehuang: you mention the possibility to run cascading as an incubated project. How would that work ? Could this be implemented completely outside the existing projects ?21:40
anteayajoehuang: you might get further if you talked about impact of teh changes and less about size of them21:40
*** thingee has joined #openstack-meeting21:40
russellbif I thought every project totally rocked its scalability and such within a single region, then i think we could talk about this as a possible next step21:41
russellbbut we're not there21:41
ttxI think everyone agrees that even if this was a good idea, now is not the time to implement it. The question is, what can joehuang do as a next step21:41
sdaguerussellb: ++21:41
jogolink https://github.com/stackforge/tricircle21:41
joehuangto ttx, yes. the different is that the test environment needs at least 3 openstacks21:41
russellbso i think it's a premature, very large distraction21:41
thingeeo/ sorry late21:41
Rockygttx: I susupect that the project would need to track integrated and ensure that a scaling solution doesn't brake them.  Negotiate for shared solution21:41
mesteryrussellb: ++21:41
ttxjoehuang: having complex test needs doesn't prevent it from being developed out of tree21:41
*** emagana has joined #openstack-meeting21:42
mikalhttps://github.com/stackforge/tricircle/blob/master/novaproxy/nova/compute/manager_proxy.py seems to have a lot of copied code from nova?21:42
joehuangthe test use case suit for current openstack can reused for cascading21:42
dhellmannrussellb: ++21:42
sdagueso I think that the fastest path to getting to this, is not spending any time on it, but instead for people interested in multi cloud stuff to actively help with the existing scalability21:42
sdagueand help make that solid21:42
*** VW_ has joined #openstack-meeting21:42
sdaguethen it opens up the discussion in the future21:42
joehuangit's inherited from nova-manager21:42
Rockygrussellb: distraction for folks already working on openstack scaling projects, but not for Joe.  But Joe would need to coordinate with those others.21:42
joehuangand some unused code not been removed completelt21:42
russellbRockyg: it requires significant buy-in and coordination across all projects21:43
russellb*signficant* design and code review time21:43
sdagueRockyg: yeh, there is tons of overhead for any feature of this scope21:43
*** dprince has joined #openstack-meeting21:43
russellbit hugely impacts what will get done in openstack overall21:43
sdaguerussellb: ++21:43
*** baoli has quit IRC21:43
Rockygrussellb: yup.  But at least don't design current openstack to make cascading impossible.21:43
*** yeungp has quit IRC21:43
ttxI'm with sdague and russellb on this one. I don't think we can afford the distraction, even if driven by a new group21:43
*** yeungp has joined #openstack-meeting21:43
russellbRockyg: don't think we are/have21:44
dansmithttx: agreed21:44
morganfainbergand to be honest, i'm still unclear on some details of it - it has had some mixed messaging. without a bit more clarity the distraction gets worse.21:44
morganfainbergttx, russellb, sdague: +121:44
fungiuntil very recently it was positioned much more as a scalability solution rather than an interoperability solution21:44
dansmithfungi: indeed, and that's the summit session it was slated for: scale-out21:44
fungihence a lot of the confusion i think21:45
RockygHow about joe uses his repository to build a POC.  When ready to show, then have a session to discuss where it is limited/broken and where it will likely work.21:45
*** Mandell has joined #openstack-meeting21:45
dansmithRockyg: that's the distraction21:45
joehuangredhat openstack can be integreted with original opensrack with cascading21:45
dansmithRockyg: if this isn't a thing we need to work on right now, then that review of the gaps is taking away from other work21:45
ttxRockyg: sure, we won't (can't, actually) prevent him from developing the solution21:45
russellbto be honest, i'm not interested in that as a problem to solve21:45
russellbat all21:45
*** neelashah has quit IRC21:46
russellband to be clear, that's with my upstream hat on21:46
russellbi just don't think we should be trying to build complex technical solutions for something that's a business issue like that21:46
russellbso i don't think it should be in the discussion21:46
joehuangsorry, too much message, not been able to answer one by one21:46
sdaguelike I said, I think the fastest path to ever working on a thing like this is *not working on it now*, and instead focussing efforts on the scaling priorities already in the projects21:46
Rockygdansmith, russellb:  just because you aren't interested or have time, doesn't mean joe can't work on it.  the nature of Open Source.  You don't have to participate.21:46
joehuangmaybe something not been exaplained21:46
sdagueincluding reviewing those changes21:47
russellbRockyg: there is a difference between "you can't work on it" and "OpenStack doesn't want to integrate it any time soon"21:47
*** mrmartin has quit IRC21:47
mesteryI don't think we can prevent people from working on this, but I haven't heard much support for this in the short term during this meeting yet.21:47
dansmithRockyg: no, of course not, but you said "have a session to discuss the gaps"21:47
*** Salman_ has quit IRC21:47
jogorussellb: ++. on the other hand I do like things like Globally Distributed OpenStack Swift Cluster21:47
dhellmannRockyg: yeah, I think it's fine for joehuang to work on it, but you're asking for help and participation and not hearing the "we don't have time this cycle" response21:47
ttxRockyg: sure, you just can't expect people to dedicate cycles to that21:47
dansmithRockyg: he can do whatever he wants, but expecting us to circle around in X months to revisit isn't a thing there seems to be any support for here21:47
morganfainbergRockyg, and no one is disagreeing. what the disagreement is that we may or may not afford the time as the OpenStack project/PTLs/TC to review it/dedicate cycles to it21:47
mesterydansmith: ++21:47
edleafeThis sounds like a great third party product built on top of OpenStack and sold to telcos who need it21:48
* morganfainberg left Core teams out of that21:48
ttxI haven't heard a single PTl (or even a single existing dev) supporting that idea yet21:48
RockygNot the gaps, the POC.  It could be a BoF at the summit for that matter.  Anyone who wants to, comes, otherwise, it's noise.21:48
ttxGiven thatn I just don't think it will be successfully integrated21:48
sdagueRockyg: sure, but expectations need to be set correctly21:48
anteayaRockyg: you can apply for a session but don't be surprised if you don't get the space21:48
jogojoehuang: it sounds like you think we are missing something. What are we missing?21:48
ttxso it's better developed separately as a POC and trying to prove itself useful.. At this moment there is a mindshare problem21:49
russellb"a mindshare problem" is a good way to capture it21:49
sdaguebecause, working off on a fork out of tree on stuff people aren't interested in, just means expect to rewrite it from scratch if there is future interest.21:49
joehuangmany people have questions, maybe because I did not answer his question21:49
fungigood outcomes which could arise from this as a separate effort among the interested parties would be for them to file bugs they identify in projects which need fixing and are preventing their effort from working as well as it should. things which are legitimately bugs in existing openstack features21:49
Rockygsdague:  yes.  Expectations: joe gets his own team if he wants it to happen.  the team is responsible for a POC and addressing whatever questions come up.21:49
morganfainbergfungi, huge +1 on that21:49
ttxit's not a technical problem, and joe thinks it's technical. Not yet, at least.21:49
sdaguefungi: ++21:49
jogoRockyg: https://github.com/stackforge/tricircle  is the POC21:50
jogoits there already21:50
dansmithjogo: right :)21:50
RockygFungi:  ++  the responsibility is on Joe21:50
joehuangso many messages, I can't answer each one,21:50
Rockyg and his team.21:50
mesteryI think you shouldn't expect that the POC will merge as is either.21:50
jogojoehuang: so I think one of the big questions is, is this a technical solution to a pure business problem?21:51
russellbso is this a fair summary?  feel free to continue your POC work, but right now, there seems to be no support from any existing devs, so it may not ever  be something accepted21:51
ttxOK, let's slow down thge discussion, so that the message is clearer21:51
RockygI wouldn't expect it to merge.  Especially as a POC.  It's once those other scaling things happen so that the stage is set, and the POC has been exercised to fix real world problems.21:51
sdagueif people want to parcipate in OpenStack, they should participate in OpenStack, and look at the priorities that projects have already set, and help. If they want to do their own thing, that's cool, just don't expect it to become part of OpenStack.21:51
russellbthings of course may change in some future release cycle21:51
*** Slower has joined #openstack-meeting21:51
jogo(the multi vendor / making several unique  deployments look like one)21:51
mesterysdague: +21:52
russellbjogo: and is it even a problem (they can be separate regions, of course)21:52
ttxI like russell summary21:52
joehuangnetworking automation across openstack is very important21:52
russellbnetworking automation across a globally distributed tree of openstack clouds?21:52
russellbumm21:52
jogojoehuang: why and can you clarify that21:52
russellbis a good example of why i think this should be considered out of scope for right now21:53
mesterynetworking automation? I'm sure that won't be contentious at all ;)21:53
russellbthat's a huge effort21:53
joehuangrefer VDF use case21:53
russellbhow about we make neutron work really well for one region first21:53
RockygYup.  I think the key info for joe here, is OpenStack isn't ready for the project, and if he want's it ready sooner than later, he needs to help make it ready by working on scaling being coded now.21:53
mesteryrussellb: ++21:53
ttxRockyg: ++21:53
dhellmannRockyg: yes, that's what I'm hearing, too21:53
*** Longgeek has quit IRC21:53
*** matrohon has quit IRC21:53
ttxok, let's spell it out21:53
morganfainbergRockyg, dead on21:53
ttx#agreed OpenStack isn't ready for the project, and if he want's it ready sooner than later, joehuang needs to help make it ready by working on scaling being coded now.21:54
* jogo googles VDF and finds Virginia Defense Force21:54
mesteryjogo: lol21:54
ttx#info feel free to continue your POC work, but right now, there seems to be no support from any existing devs, so it may not ever  be something accepted21:54
ttxI think that's a fair summary ?21:54
dansmith+121:54
russellb++21:54
morganfainberg+121:54
asalkeld+121:55
dhellmann+121:55
jogo++21:55
edleafe+121:55
*** Masahiro has joined #openstack-meeting21:55
markmcclain +121:55
joehuangnot support from the meeting?21:55
mestery+121:55
alaski+121:55
russellbjoehuang: in Paris?  No, I did not detect any support in that meeting21:55
sdague+121:55
*** pballand has quit IRC21:56
ttxjoehuang: I have yet to find an existing core dev in any of the affected project ready to back the idea21:56
joehuangso we continue our work, and ignite a discussion later wen new progress comes21:56
jogojoehuang: what is VDF? link21:56
dhellmannjoehuang: that sounds like the best plan for right now21:56
joehuangVodafone21:56
ttxjoehuang: also, if you encounter sclaing issues in getting your POC to work (and you will) file them as bugs, and help fixing them21:57
morganfainbergjoehuang, and please help contirbute to solving the issues with the scaling in the current projects.21:57
Rockygjoehuang: ++ and help on openstack work that leads to what you want on cascading21:57
morganfainbergas ttx just said21:57
ttx#topic Open discussion & announcements21:57
*** openstack changes topic to "Open discussion & announcements (Meeting topic: crossproject)"21:57
ttxWe had 1:1 syncs today, kilo-1 tags are getting out as we speak. Logs at:21:57
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-16-09.00.html21:57
*** mpaolino has joined #openstack-meeting21:58
dhellmannIt looks like the issue with oslo.db and sqlalchemy triggered by the setuptools release this weekend is fixed. Please let me know if you are seeing failures still in your projects.21:58
*** mpaolino has quit IRC21:58
ttxAlso note that we'll discuss openstack-specs as a recurring iteml in future meetings:21:58
dhellmannthere is one more patch to land in juno to pin oslo.db <1.121:58
ttx#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-specs+branch:master,n,z21:58
ttxPTLs, ops, eveyone shall review those ^21:58
asalkeldk21:59
morganfainbergjust a minor note, keystoneclient is going to be bumped to 1.0.0 this next release - it's been stable for a looong time, we're just marking it as stable version # (no incompat changes going in, etc) - if anyone has any concerns, let me know [e.g. infra side, etc].21:59
ttxcurrently one on log guidelines and one on OSProfiler21:59
*** KLevenstein_ has joined #openstack-meeting21:59
*** KLevenstein_ is now known as KLevenstein21:59
ttxAnything else, anyone ?21:59
*** Masahiro has quit IRC22:00
eglynnttx: meeting scheduling for next 2 weeks?22:00
russellbhope you all have happy holidays, if you're taking any time off :)22:00
ttxeglynn: probably skip next 222:00
eglynnttx: cool, sounds reasonable22:00
ttxanyone wanting to have a cross-project on Dec 23 or Dec 30 ?22:01
ttx(there is a trick hidden in that question)22:01
*** jmontemayor has quit IRC22:01
Rockygmy projects would be very cross if they had to meet then;-)22:01
*** suro_ has quit IRC22:01
ttxAlright, have a great holiday season everyone! Next meeting January 622:02
ttx#endmeeting22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Dec 16 22:02:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2014/crossproject.2014-12-16-21.01.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2014/crossproject.2014-12-16-21.01.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2014/crossproject.2014-12-16-21.01.log.html22:02
*** ryansb has left #openstack-meeting22:02
*** bswartz has quit IRC22:02
*** mdorman has left #openstack-meeting22:03
*** asalkeld has left #openstack-meeting22:03
*** thangp has quit IRC22:04
*** SridharRamaswamy has joined #openstack-meeting22:04
*** ayoung has quit IRC22:04
*** aranjan has joined #openstack-meeting22:04
*** thingee has left #openstack-meeting22:05
*** eglynn has quit IRC22:05
*** leonchio_ has quit IRC22:05
*** colinmcnamara has joined #openstack-meeting22:05
*** Mandell has quit IRC22:06
*** ivar-lazzaro has joined #openstack-meeting22:07
*** ivar-lazzaro has quit IRC22:07
*** ivar-lazzaro has joined #openstack-meeting22:08
*** aranjan has quit IRC22:09
*** kebray has quit IRC22:11
*** maishsk has quit IRC22:11
*** VW_ has quit IRC22:15
*** rmoe has quit IRC22:16
*** pballand has joined #openstack-meeting22:18
*** pballand has quit IRC22:19
*** neelashah has joined #openstack-meeting22:20
*** joehuang has quit IRC22:20
*** hashar has joined #openstack-meeting22:21
*** Mandell has joined #openstack-meeting22:21
*** adahms has quit IRC22:22
*** markmcclain has quit IRC22:22
*** markmcclain has joined #openstack-meeting22:22
*** thomasem has quit IRC22:23
*** markmcclain has quit IRC22:24
*** markmcclain has joined #openstack-meeting22:24
*** alex7376 has joined #openstack-meeting22:25
*** asettle has joined #openstack-meeting22:25
*** jmontemayor has joined #openstack-meeting22:25
*** markmcclain has quit IRC22:25
*** asettle has quit IRC22:25
*** markmcclain has joined #openstack-meeting22:26
*** vigneshvar has quit IRC22:27
*** alex7376 is now known as asettle22:27
*** pballand has joined #openstack-meeting22:27
*** rmoe has joined #openstack-meeting22:29
*** pballand has quit IRC22:30
*** KLevenstein has left #openstack-meeting22:33
*** marcoemorais has joined #openstack-meeting22:35
*** tsekiyam_ has joined #openstack-meeting22:36
*** Rockyg has quit IRC22:39
*** amolock has quit IRC22:39
*** tsekiyama has quit IRC22:39
*** esker has quit IRC22:40
*** JRobinson__ has joined #openstack-meeting22:40
*** tsekiyam_ has quit IRC22:41
*** dprince has quit IRC22:41
*** tsekiyama has joined #openstack-meeting22:43
*** changbl has quit IRC22:43
*** topol has quit IRC22:45
*** Mandell has quit IRC22:45
*** ociuhandu has quit IRC22:46
*** VW_ has joined #openstack-meeting22:46
*** dboik has quit IRC22:46
*** VW_ has quit IRC22:46
*** niclem has joined #openstack-meeting22:47
*** VW_ has joined #openstack-meeting22:47
*** tsekiyama has quit IRC22:47
*** jmontemayor has quit IRC22:48
*** carl_baldwin has quit IRC22:48
*** carl_baldwin has joined #openstack-meeting22:49
*** chuckC_ has quit IRC22:49
*** alexpilotti_ has joined #openstack-meeting22:49
*** alexpilotti_ has quit IRC22:49
*** pballand has joined #openstack-meeting22:50
*** alexpilotti has quit IRC22:50
*** jmontemayor has joined #openstack-meeting22:52
*** jmontemayor_ has joined #openstack-meeting22:53
*** spzala has quit IRC22:53
*** carl_baldwin has quit IRC22:54
*** jmontemayor has quit IRC22:56
*** gokrokve has quit IRC22:57
*** yamamoto has joined #openstack-meeting22:58
*** neelashah has quit IRC22:59
*** carl_baldwin has joined #openstack-meeting23:00
*** baoli has joined #openstack-meeting23:01
*** Mandell has joined #openstack-meeting23:02
*** gokrokve has joined #openstack-meeting23:02
*** aranjan has joined #openstack-meeting23:05
*** hashar has quit IRC23:06
*** gokrokve has quit IRC23:06
*** dims has quit IRC23:07
*** gokrokve has joined #openstack-meeting23:07
*** dims has joined #openstack-meeting23:07
*** dims has quit IRC23:08
*** dims has joined #openstack-meeting23:08
*** yamamoto has quit IRC23:09
*** suro_ has joined #openstack-meeting23:10
*** aranjan has quit IRC23:10
*** otter768 has joined #openstack-meeting23:10
*** e0ne has quit IRC23:11
*** nellysmitt has joined #openstack-meeting23:12
*** marcoemorais has left #openstack-meeting23:13
*** colinmcnamara has quit IRC23:13
*** emagana has quit IRC23:13
*** Mandell has quit IRC23:13
*** krtaylor has quit IRC23:13
*** tbarron has quit IRC23:14
*** otter768 has quit IRC23:15
*** Mandell has joined #openstack-meeting23:15
*** ddieterly has quit IRC23:17
*** nellysmitt has quit IRC23:17
*** ddieterly has joined #openstack-meeting23:17
*** zaneb has quit IRC23:18
*** emagana has joined #openstack-meeting23:19
*** IanGovett has quit IRC23:21
*** ddieterly has quit IRC23:22
*** Slower has quit IRC23:22
*** penick has quit IRC23:23
*** bdpayne has joined #openstack-meeting23:23
*** mdenny has quit IRC23:24
*** pballand has quit IRC23:24
*** SridharRamaswamy has left #openstack-meeting23:26
*** krtaylor has joined #openstack-meeting23:26
*** shashankhegde has quit IRC23:27
*** ajiang38740_ has quit IRC23:27
*** ajiang has quit IRC23:27
*** pballand has joined #openstack-meeting23:28
*** shashankhegde has joined #openstack-meeting23:28
*** gokrokve has quit IRC23:28
*** pballand has quit IRC23:30
*** andreykurilin_ has quit IRC23:30
*** VW_ has quit IRC23:34
*** VW_ has joined #openstack-meeting23:35
*** AlanClark has quit IRC23:36
*** dane_leblanc_ has quit IRC23:37
*** Slower has joined #openstack-meeting23:38
*** adahms has joined #openstack-meeting23:38
*** jecarey has quit IRC23:39
*** VW_ has quit IRC23:40
*** padkrish has quit IRC23:40
*** e0ne has joined #openstack-meeting23:41
*** tochi has joined #openstack-meeting23:43
*** padkrish has joined #openstack-meeting23:44
*** Masahiro has joined #openstack-meeting23:44
*** penick has joined #openstack-meeting23:44
*** pballand has joined #openstack-meeting23:44
*** MarkAtwood has quit IRC23:46
*** e0ne has quit IRC23:47
*** jmontemayor_ has quit IRC23:47
*** amotoki has quit IRC23:47
*** Masahiro has quit IRC23:48
*** dboik has joined #openstack-meeting23:49
*** yamamoto has joined #openstack-meeting23:50
*** andreaf has joined #openstack-meeting23:52
*** pballand has quit IRC23:52
*** yeungp has quit IRC23:53
*** yeungp has joined #openstack-meeting23:53
*** yeungp has quit IRC23:54
*** yeungp has joined #openstack-meeting23:54
*** rbak has quit IRC23:55
*** mattgriffin has quit IRC23:57
*** jlibosva has quit IRC23:57

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