Tuesday, 2015-03-31

*** sreshetn2 has quit IRC00:00
*** Tango|2 has quit IRC00:02
*** xingchao has joined #openstack-meeting00:02
*** annegentle has quit IRC00:02
*** achanda_ has joined #openstack-meeting00:03
*** yamamoto has joined #openstack-meeting00:04
*** baoli_ has quit IRC00:06
*** achanda has quit IRC00:07
*** achanda_ has quit IRC00:08
*** ddieterly has joined #openstack-meeting00:08
*** yamamoto has quit IRC00:09
*** sigmavirus24 is now known as sigmavirus24_awa00:09
*** nati_ueno has quit IRC00:10
*** banix has joined #openstack-meeting00:10
*** carl_baldwin has quit IRC00:12
*** weshay has joined #openstack-meeting00:13
*** aimon has joined #openstack-meeting00:13
*** baoli has joined #openstack-meeting00:15
*** ibiris_away is now known as ibiris00:18
*** unicell has quit IRC00:19
*** unicell1 has joined #openstack-meeting00:19
*** jruano has joined #openstack-meeting00:19
*** rossella_s has quit IRC00:20
*** rossella_s has joined #openstack-meeting00:20
*** asettle has joined #openstack-meeting00:25
*** nati_ueno has joined #openstack-meeting00:25
*** tsekiyam_ has joined #openstack-meeting00:26
*** eliqiao has joined #openstack-meeting00:26
*** dims has joined #openstack-meeting00:27
*** mtanino_ has joined #openstack-meeting00:27
*** tiswanso has joined #openstack-meeting00:28
*** ibiris is now known as ibiris_away00:28
*** banix has quit IRC00:28
*** mtanino has quit IRC00:29
*** mwagner_lap has joined #openstack-meeting00:29
*** tsekiyama has quit IRC00:30
*** noslzzp has joined #openstack-meeting00:30
*** nati_ueno has quit IRC00:30
*** ijw has quit IRC00:31
*** nati_ueno has joined #openstack-meeting00:31
*** tsekiyam_ has quit IRC00:31
*** epico has joined #openstack-meeting00:34
*** xingchao has quit IRC00:35
*** mattgriffin has quit IRC00:36
*** comay has quit IRC00:38
*** tiswanso has quit IRC00:38
*** tiswanso has joined #openstack-meeting00:39
*** sorrison has quit IRC00:40
*** yamamoto_ has joined #openstack-meeting00:43
*** otter768 has joined #openstack-meeting00:43
*** varora has joined #openstack-meeting00:47
*** nati_uen_ has joined #openstack-meeting00:52
*** nati_ueno has quit IRC00:52
*** Longgeek has joined #openstack-meeting00:54
*** jruano has quit IRC00:56
*** xingchao has joined #openstack-meeting00:58
*** annegentle has joined #openstack-meeting00:58
*** nati_uen_ has quit IRC00:59
*** nati_ueno has joined #openstack-meeting01:00
*** emagana has quit IRC01:01
*** rfolco has joined #openstack-meeting01:02
*** ChuckC has quit IRC01:08
*** sballe has quit IRC01:08
*** jruano has joined #openstack-meeting01:08
*** baoli has quit IRC01:12
*** amotoki has joined #openstack-meeting01:12
*** annegentle has quit IRC01:12
*** j05h has quit IRC01:12
*** annegentle has joined #openstack-meeting01:13
*** j05h has joined #openstack-meeting01:13
*** leeantho has quit IRC01:13
*** amotoki has quit IRC01:13
*** asomya has quit IRC01:13
*** Longgeek has quit IRC01:17
*** Longgeek has joined #openstack-meeting01:17
*** yamamoto_ has quit IRC01:17
*** banix has joined #openstack-meeting01:18
*** mitz has quit IRC01:26
*** asselin has joined #openstack-meeting01:28
*** Leonr has joined #openstack-meeting01:29
*** Daisy has joined #openstack-meeting01:30
*** unicell1 has quit IRC01:31
*** unicell has joined #openstack-meeting01:31
*** ebalduf has joined #openstack-meeting01:32
*** jruano has quit IRC01:32
*** Leo_ has quit IRC01:32
*** kaisers has joined #openstack-meeting01:33
*** ChuckC has joined #openstack-meeting01:34
*** xyang1 has quit IRC01:35
*** kaisers1 has quit IRC01:35
*** mitz has joined #openstack-meeting01:36
*** xingchao has quit IRC01:36
*** tsekiyama has joined #openstack-meeting01:37
*** ebalduf has quit IRC01:37
*** novas0x2a|laptop has quit IRC01:38
*** weshay has quit IRC01:38
*** stevemar has joined #openstack-meeting01:39
*** xingchao has joined #openstack-meeting01:40
*** baoli has joined #openstack-meeting01:40
*** tsekiyama has quit IRC01:41
*** amotoki has joined #openstack-meeting01:42
*** annegentle has quit IRC01:42
*** baoli has quit IRC01:47
*** amotoki has quit IRC01:47
*** yamahata has joined #openstack-meeting01:47
*** amotoki has joined #openstack-meeting01:47
*** carl_baldwin has joined #openstack-meeting01:47
*** yamamoto_ has joined #openstack-meeting01:49
*** asettle has quit IRC01:49
*** IanGovett has quit IRC01:49
*** unicell has quit IRC01:49
*** chandankumar has joined #openstack-meeting01:50
*** xingchao has quit IRC01:50
*** amotoki has quit IRC01:52
*** eghobo has quit IRC01:53
*** j05h has quit IRC01:56
*** j05h has joined #openstack-meeting01:58
*** j05h has quit IRC01:58
*** Apoorva has quit IRC01:59
*** j05h has joined #openstack-meeting02:00
*** j05h has quit IRC02:01
*** JRobinson__ has quit IRC02:01
*** chandankumar has quit IRC02:04
*** Leo_ has joined #openstack-meeting02:06
*** dims has quit IRC02:07
*** amrith is now known as _amrith_02:07
*** dims has joined #openstack-meeting02:08
*** Leonr has quit IRC02:09
*** Longgeek has quit IRC02:09
*** Longgeek_ has joined #openstack-meeting02:09
*** padkrish has joined #openstack-meeting02:12
*** padkrish has quit IRC02:12
*** padkrish has joined #openstack-meeting02:12
*** dims has quit IRC02:14
*** banix has quit IRC02:14
*** carl_baldwin has quit IRC02:14
*** SumitNaiksatam has quit IRC02:14
*** annegentle has joined #openstack-meeting02:15
*** nati_ueno has quit IRC02:16
*** marun has quit IRC02:16
*** haomaiwang has joined #openstack-meeting02:17
*** baoli has joined #openstack-meeting02:18
*** Longgeek_ has quit IRC02:20
*** carl_baldwin has joined #openstack-meeting02:21
*** Longgeek_ has joined #openstack-meeting02:23
*** eghobo has joined #openstack-meeting02:25
*** amotoki has joined #openstack-meeting02:28
*** eghobo has quit IRC02:29
*** otter768 has quit IRC02:30
*** carl_baldwin has quit IRC02:31
*** ebalduf has joined #openstack-meeting02:33
*** kebray has quit IRC02:33
*** achanda has joined #openstack-meeting02:34
*** banix has joined #openstack-meeting02:34
*** jruano has joined #openstack-meeting02:35
*** garyh has quit IRC02:38
*** ebalduf has quit IRC02:38
*** jruano has quit IRC02:39
*** otter768 has joined #openstack-meeting02:39
*** carl_baldwin has joined #openstack-meeting02:41
*** amotoki has quit IRC02:43
*** crc32 has quit IRC02:44
*** achanda has quit IRC02:44
*** yamahata has quit IRC02:44
*** achanda has joined #openstack-meeting02:45
*** mtanino_ has quit IRC02:50
*** nati_ueno has joined #openstack-meeting02:50
*** xingchao_ has joined #openstack-meeting02:50
*** shwetaap has joined #openstack-meeting02:51
*** carl_baldwin has quit IRC02:51
*** rbak has joined #openstack-meeting02:53
*** dannywilson has joined #openstack-meeting02:54
*** hichihara has quit IRC02:59
*** dannywilson has quit IRC02:59
*** xingchao_ has quit IRC02:59
*** nati_ueno has quit IRC02:59
*** hichihara has joined #openstack-meeting02:59
*** hichihara has quit IRC02:59
*** erlon has quit IRC03:01
*** rbak has quit IRC03:02
*** marcusvrn1 has quit IRC03:06
*** marcusvrn has joined #openstack-meeting03:06
*** ddieterly has quit IRC03:07
*** harlowja_ is now known as harlowja_away03:07
*** amotoki has joined #openstack-meeting03:10
*** banix has quit IRC03:11
*** noslzzp has quit IRC03:12
*** padkrish has quit IRC03:12
*** noslzzp has joined #openstack-meeting03:14
*** noslzzp has quit IRC03:14
*** otter768 has quit IRC03:15
*** sorrison has joined #openstack-meeting03:15
*** bknudson has quit IRC03:16
*** amotoki has quit IRC03:16
*** unicell has joined #openstack-meeting03:20
*** spzala has quit IRC03:22
*** esker has joined #openstack-meeting03:25
*** unicell has quit IRC03:27
*** unicell has joined #openstack-meeting03:28
*** sorrison has quit IRC03:30
*** sorrison has joined #openstack-meeting03:30
*** AmirBaleghi114 has quit IRC03:30
*** xingchao_ has joined #openstack-meeting03:32
*** sbalukoff has quit IRC03:32
*** carl_baldwin has joined #openstack-meeting03:32
*** ebalduf has joined #openstack-meeting03:34
*** ajmiller__ has joined #openstack-meeting03:34
*** Daisy has quit IRC03:35
*** baoli has quit IRC03:36
*** xingchao_ has quit IRC03:37
*** ajmiller_ has quit IRC03:37
*** SumitNaiksatam has joined #openstack-meeting03:38
*** ebalduf has quit IRC03:38
*** rbak has joined #openstack-meeting03:38
*** esker has quit IRC03:42
*** amotoki has joined #openstack-meeting03:43
*** rfolco has quit IRC03:46
*** rbak has quit IRC03:46
*** j05h has joined #openstack-meeting03:46
*** ayoung has quit IRC03:48
*** Murali has joined #openstack-meeting03:49
*** topol has joined #openstack-meeting03:52
*** mattgriffin has joined #openstack-meeting03:55
*** ajayaa has joined #openstack-meeting03:56
*** asettle has joined #openstack-meeting03:56
*** rfolco has joined #openstack-meeting03:58
*** pballand has joined #openstack-meeting03:59
*** anish_ has joined #openstack-meeting04:00
*** armax has quit IRC04:00
*** carl_baldwin has quit IRC04:05
*** ddieterly has joined #openstack-meeting04:08
*** Daisy has joined #openstack-meeting04:09
*** krtaylor has quit IRC04:11
*** ddieterly has quit IRC04:12
*** achanda has quit IRC04:12
*** krtaylor has joined #openstack-meeting04:13
*** BrianShang_ has quit IRC04:13
*** BrianShang has joined #openstack-meeting04:15
*** yatin has joined #openstack-meeting04:16
*** ajayaa has quit IRC04:19
*** Tango|2 has joined #openstack-meeting04:19
*** achanda has joined #openstack-meeting04:19
*** eghobo has joined #openstack-meeting04:19
*** kebray has joined #openstack-meeting04:19
*** kebray has quit IRC04:19
*** kebray has joined #openstack-meeting04:20
*** shankarprasad has joined #openstack-meeting04:20
*** JRobinson__ has joined #openstack-meeting04:21
*** achanda has quit IRC04:27
*** winston-d has left #openstack-meeting04:27
*** achanda has joined #openstack-meeting04:30
*** oomichi_ has joined #openstack-meeting04:33
*** Daisy has quit IRC04:33
*** aranjan has joined #openstack-meeting04:35
*** Longgeek_ has quit IRC04:35
*** shankarprasad has quit IRC04:39
*** achanda has quit IRC04:40
*** annegentle has quit IRC04:40
*** achanda has joined #openstack-meeting04:40
*** goodes has quit IRC04:41
*** carl_baldwin has joined #openstack-meeting04:41
*** Michalik has quit IRC04:42
*** Longgeek has joined #openstack-meeting04:42
*** goodes has joined #openstack-meeting04:43
*** Michalik has joined #openstack-meeting04:44
*** aranjan_ has joined #openstack-meeting04:45
*** annegentle has joined #openstack-meeting04:46
*** Apoorva_ has joined #openstack-meeting04:46
*** chandankumar has joined #openstack-meeting04:47
*** aranjan has quit IRC04:48
*** annegentle has quit IRC04:49
*** Murali has quit IRC04:50
*** achanda has quit IRC04:51
*** ildikov has quit IRC04:55
*** mrmartin has joined #openstack-meeting04:56
*** ibiris_away is now known as ibiris04:56
*** Leo_ has quit IRC04:57
*** sbalukoff has joined #openstack-meeting04:58
*** Daisy has joined #openstack-meeting05:01
*** j05h has quit IRC05:01
*** lpeer has joined #openstack-meeting05:02
*** eghobo has quit IRC05:03
*** ajo has joined #openstack-meeting05:06
*** ddieterly has joined #openstack-meeting05:09
*** ddieterly has quit IRC05:13
*** rpodolyaka1 has joined #openstack-meeting05:15
*** carl_baldwin has quit IRC05:15
*** aepifanov has joined #openstack-meeting05:15
*** otter768 has joined #openstack-meeting05:16
*** ajo has quit IRC05:16
*** mattgriffin has quit IRC05:17
*** otter768 has quit IRC05:20
*** achanda has joined #openstack-meeting05:22
*** Mandell has joined #openstack-meeting05:22
*** fawadkhaliq has joined #openstack-meeting05:23
*** rajeshr has joined #openstack-meeting05:27
*** dulek has joined #openstack-meeting05:29
*** oomichi_ has quit IRC05:29
*** pballand has quit IRC05:29
*** shwetaap has quit IRC05:33
*** Apoorva_ has quit IRC05:36
*** garyk has joined #openstack-meeting05:37
*** rpodolyaka1 has quit IRC05:38
*** rpodolyaka1 has joined #openstack-meeting05:38
*** vigneshvar has joined #openstack-meeting05:43
*** vigneshvar_ has joined #openstack-meeting05:43
*** ajo has joined #openstack-meeting05:44
*** reed has quit IRC05:47
*** ildikov has joined #openstack-meeting05:47
*** topol has quit IRC05:47
*** markvoelker has quit IRC05:48
*** nati_ueno has joined #openstack-meeting05:51
*** watanabe_isao has joined #openstack-meeting05:51
*** pradipta has joined #openstack-meeting05:52
*** nshaikh has joined #openstack-meeting05:52
*** nati_uen_ has joined #openstack-meeting05:55
*** annegentle has joined #openstack-meeting05:58
*** yatin has quit IRC05:58
*** nati_ueno has quit IRC05:59
*** annegentle has quit IRC06:02
*** mmedvede has quit IRC06:04
*** anish_ has quit IRC06:05
*** aranjan_ has quit IRC06:05
*** aranjan has joined #openstack-meeting06:06
*** chandankumar has quit IRC06:06
*** Daisy has quit IRC06:07
*** achanda has quit IRC06:08
*** achanda has joined #openstack-meeting06:08
*** ddieterly has joined #openstack-meeting06:10
*** rpodolyaka1 has quit IRC06:11
*** ijw has joined #openstack-meeting06:13
*** ddieterly has quit IRC06:14
*** yatin has joined #openstack-meeting06:15
*** eghobo has joined #openstack-meeting06:15
*** anish_ has joined #openstack-meeting06:15
*** Tango|2 has quit IRC06:16
*** rpodolyaka1 has joined #openstack-meeting06:16
*** anish_ has quit IRC06:19
*** markvoelker has joined #openstack-meeting06:19
*** anish_ has joined #openstack-meeting06:19
*** JRobinson__ has quit IRC06:20
*** neeti has joined #openstack-meeting06:22
*** BharatK has joined #openstack-meeting06:24
*** markvoelker has quit IRC06:26
*** yatin has quit IRC06:27
*** sahid has joined #openstack-meeting06:27
*** amotoki has quit IRC06:27
*** eghobo_ has joined #openstack-meeting06:28
*** SridharG has joined #openstack-meeting06:29
*** sreshetn2 has joined #openstack-meeting06:29
*** shankarprasad has joined #openstack-meeting06:29
*** scheuran has joined #openstack-meeting06:29
*** sergef has joined #openstack-meeting06:30
*** eghobo has quit IRC06:31
*** BrianShang has quit IRC06:35
*** eghobo has joined #openstack-meeting06:35
*** fzdarsky|afk has joined #openstack-meeting06:35
*** BrianShang has joined #openstack-meeting06:36
*** eghobo_ has quit IRC06:37
*** sreshetn2 has quit IRC06:38
*** fzdarsky|afk has quit IRC06:40
*** eghobo has quit IRC06:40
*** fzdarsky|afk has joined #openstack-meeting06:40
*** fzdarsky|afk is now known as fzdarsky06:40
*** yatin has joined #openstack-meeting06:41
*** BrianShang_ has joined #openstack-meeting06:41
*** xingchao_ has joined #openstack-meeting06:43
*** chandankumar has joined #openstack-meeting06:43
*** Mandell has quit IRC06:43
*** sreshetn2 has joined #openstack-meeting06:44
*** BrianShang has quit IRC06:44
*** nati_uen_ has quit IRC06:46
*** nati_ueno has joined #openstack-meeting06:46
*** jtomasek has joined #openstack-meeting06:48
*** marun has joined #openstack-meeting06:50
*** nati_ueno has quit IRC06:51
*** xingchao_ has quit IRC06:51
*** kzaitsev has joined #openstack-meeting06:51
*** amotoki has joined #openstack-meeting06:53
*** dguitarbite has joined #openstack-meeting06:54
*** SridharG has left #openstack-meeting06:54
*** marun has quit IRC06:55
*** sdake has quit IRC06:56
*** lennyb has joined #openstack-meeting06:56
*** jichen has joined #openstack-meeting06:57
*** evgenyf has joined #openstack-meeting06:58
*** annegentle has joined #openstack-meeting06:58
*** adahms has quit IRC07:00
*** BrianShang_ has quit IRC07:00
*** asettle has quit IRC07:01
*** amotoki has quit IRC07:01
*** Murali has joined #openstack-meeting07:02
*** amotoki has joined #openstack-meeting07:02
*** BrianShang has joined #openstack-meeting07:02
*** Daisy has joined #openstack-meeting07:03
*** annegentle has quit IRC07:04
*** yamamoto_ has quit IRC07:04
*** liusheng has joined #openstack-meeting07:04
*** achanda has quit IRC07:05
*** nati_ueno has joined #openstack-meeting07:06
*** ajo_ has joined #openstack-meeting07:07
*** numan has joined #openstack-meeting07:09
*** ajo has quit IRC07:10
*** ddieterly has joined #openstack-meeting07:10
*** yatin has quit IRC07:13
*** ddieterly has quit IRC07:15
*** stevemar has quit IRC07:16
*** otter768 has joined #openstack-meeting07:16
*** rpodolyaka1 has quit IRC07:17
*** vigneshvar has quit IRC07:17
*** vigneshvar_ has quit IRC07:17
*** kzaitsev has quit IRC07:19
*** Fdot has joined #openstack-meeting07:21
*** otter768 has quit IRC07:21
*** markvoelker has joined #openstack-meeting07:22
*** bobmel has joined #openstack-meeting07:23
*** matrohon has joined #openstack-meeting07:23
*** rfolco has quit IRC07:24
*** kzaitsev has joined #openstack-meeting07:25
*** MaxV has joined #openstack-meeting07:25
*** markvoelker has quit IRC07:27
*** MaxV has quit IRC07:30
*** MaxV has joined #openstack-meeting07:30
*** yatin has joined #openstack-meeting07:30
*** rushiagr_away is now known as rushiagr07:30
*** SridharG has joined #openstack-meeting07:32
*** dkusidlo has joined #openstack-meeting07:32
*** mpaolino has joined #openstack-meeting07:32
*** liusheng has quit IRC07:33
*** liusheng has joined #openstack-meeting07:34
*** phil has joined #openstack-meeting07:34
*** aranjan has quit IRC07:34
*** phil is now known as Guest8668107:35
*** MaxV has quit IRC07:35
*** eugene_bag has joined #openstack-meeting07:36
*** rfolco has joined #openstack-meeting07:36
*** kzaitsev has quit IRC07:37
*** jlanoux has joined #openstack-meeting07:37
*** nati_ueno has quit IRC07:38
*** nati_ueno has joined #openstack-meeting07:39
*** zz_ttrifonov is now known as ttrifonov07:39
*** eugene_bag1 has joined #openstack-meeting07:40
*** eugene_bag has quit IRC07:41
*** evgenyf has quit IRC07:42
*** evgenyf has joined #openstack-meeting07:42
*** nati_ueno has quit IRC07:43
*** yatin has quit IRC07:44
*** rushiagr is now known as rushiagr_away07:47
*** nati_ueno has joined #openstack-meeting07:47
*** safchain has joined #openstack-meeting07:49
*** aranjan has joined #openstack-meeting07:50
*** xingchao_ has joined #openstack-meeting07:51
*** nati_ueno has quit IRC07:52
*** evgenyf has quit IRC07:52
*** aranjan has quit IRC07:55
*** sergef has quit IRC07:56
*** yamamoto_ has joined #openstack-meeting07:57
*** xingchao_ has quit IRC07:57
*** yamamoto_ has quit IRC07:59
*** annegentle has joined #openstack-meeting07:59
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Mar 31 08:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
*** MaxV has joined #openstack-meeting08:00
anteayaraise your hand if you are here for the third party meeting08:00
lennybHi08:00
anteayahello lennyb08:00
anteayanice to see you08:01
anteayahow are you today?08:01
lennybyou too. It looks like only you and me again :)08:01
anteayait happens08:01
*** yatin has joined #openstack-meeting08:01
anteayahow are you doing at responding to the email thread?08:01
anteayaI don't think i have seen your response yet08:02
lennybI found a great feature in outlook - 'time zones' for setting recursive meetings with no effect of local summer/winter time.08:02
anteayawell that is great08:02
anteayaI'm glad you found something that works for you08:03
*** liusheng has quit IRC08:03
lennybRegarding email, I did not respond yet, since we had some issues with showing html reports (it was shown as plain text ) and recent Nova failures that I am fixing.08:03
*** zz_johnthetubagu is now known as johnthetubaguy08:04
*** liusheng has joined #openstack-meeting08:04
*** jlibosva has joined #openstack-meeting08:04
*** annegentle has quit IRC08:05
anteayaokay08:05
anteayawhat is wrong with plain text reports for now?08:05
lennybnow it works as html according to community policy and jogo's comment08:06
*** sreshetn2 has quit IRC08:06
*** Fdot has quit IRC08:07
anteayawhere is the community policy that it has to be in html?08:07
*** ygbo has joined #openstack-meeting08:07
anteayaand where is jogo's comment to that effect08:08
anteayaif people are saying that your logs have to be in html that is news to me08:08
anteayaand would like to see where you have seen that stated08:08
anteayayou have to have logs, yes08:08
anteayathe closer they are to what jenkins provides, the better it is for everyone concerned, yes08:09
anteayathey have to be in html? I haven't seen that anywhere08:09
lennyb"I couldn't find the equivalent of: http://logs.openstack.org/68/135768/9/check/check-tempest-dsvm-full/f6c95de/logs/testr_results.html.gz"08:09
anteayatestr_results08:10
*** Daisy has quit IRC08:10
anteayahad you provided the output of testr_results in any format?08:10
lennybThis is his quote and my understanding of it. The link he opens as html, our ones were shown as plain text08:10
anteayathat wasn't a request for html that was a request for testr_results output08:10
anteayahad you shown testr_results prior to his comment?08:11
*** ddieterly has joined #openstack-meeting08:11
*** sreshetn2 has joined #openstack-meeting08:11
lennybyes, but was also not in root folder. so it's fixed now08:12
anteayacan I see a link to one of your runs08:12
anteayaand we can look at your logs08:12
*** kebray has quit IRC08:13
*** shankarprasad has quit IRC08:14
*** fawadkhaliq has quit IRC08:14
*** Fdot has joined #openstack-meeting08:14
*** ndipanov has joined #openstack-meeting08:15
lennyb1sec08:15
*** ddieterly has quit IRC08:15
lennybI done have runs after the fix, yet. This is before the fix.  http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/08:16
anteayaokay08:16
anteayacan we agree that http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/console.html.gz is useless in its current format?08:17
anteaya#link http://imgur.com/6MXyRQ408:18
lennybyes. will be fixed as well08:18
anteayais what I see08:18
*** sreshetn2 has quit IRC08:19
*** KrustyB has joined #openstack-meeting08:19
anteayatestr_results is the only log that does seem readable: http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/logs/testr_results.html.gz08:19
anteayait doesn't provide much information but the format is readable08:20
lennybIt was smoke run with 2 tests08:20
anteayayes08:20
anteayaI see that08:20
*** jlibosva has quit IRC08:21
anteayaso you have a ways to go, yes?08:21
anteayaso personally right now, I wouldn't be supportive of you leaving comments anywhere but on a sandbox repo08:21
*** pnavarro|off has quit IRC08:22
lennybI believe so.08:22
anteayabecause the artifacts you are providing are not useful for anyone08:22
anteayaokay good08:22
anteayaso going forward, use your judgement08:22
anteayaif you can't read what you provide, chances are noone else can either08:22
anteayadoes that make sense?08:23
*** markvoelker has joined #openstack-meeting08:23
anteayaso here is my question08:23
anteayamellanox is leaving comments on other repos, right?08:23
anteayatheir logs must be in some kind of readable shape, I am assuming08:24
anteayawhy are you on your own with this?08:24
lennybyes, neutron and cinder08:24
anteayawhy isn't anyone at mellanox helping you get your logs in shape08:24
anteayacertainly someone at mellanox must have figured out log formatting by now08:24
anteayawhy aren't they supporting you?08:25
lennybI am not on my own, I am just the one who represents Mellanox CI08:25
anteayahttp://144.76.193.39/ci-artifacts/143297/30/Check-MLNX-Neutron-ML2-driver/08:26
anteayaand this is from a neutron patch08:26
anteayaand the logs are in terrible shape08:26
*** shankarprasad has joined #openstack-meeting08:27
lennybI see, It will be fixed a.s.a.p as well08:27
anteayaMellanox CI is commenting and leaving this on Neutron patches08:27
anteayahow?08:27
*** markvoelker has quit IRC08:27
anteayais there anyone at Mellanox that has figured out log formatting?08:27
anteayathis was Kyle's and my concern we outlined on the third-party-announce mailing list thread08:28
anteayaMellanox CI is the account that comments on Neutron patches08:28
anteayayou are just learning, which is fine08:28
anteayaeveryone has to learn08:28
anteayabut this CI has voting privledges in Neutron08:29
anteayado you understand what that means?08:29
anteayacan you understand our concerns here?08:29
lennybas I said it will be fixed.08:29
*** derekh has joined #openstack-meeting08:29
*** e0ne has joined #openstack-meeting08:29
anteayacan you understand our concerns?08:29
lennybyes, I do understand your concern, We are very responsive on every issue of Mellanox CI failure08:31
anteayado you understand that you are new08:31
anteayaand that the reason we don't start off with systems voting right away anymore is that we have seen the mistakes that new people make when they are learning how to operate a ci system?08:32
anteayathis is for your protection as much as for neutron's08:32
*** xuhanp has joined #openstack-meeting08:32
lennybyes, I understand and I do have full support of Mellanox team.08:32
*** xuhanp_ has joined #openstack-meeting08:32
*** JRobinson__ has joined #openstack-meeting08:33
anteayahow can they leave a new person solely responsible for a voting ci system?08:33
anteayaat the very least you should request yourself that for neutron voting permissions be removed until you learn what you are doing08:33
anteayaif anythign this will be seen as a very responsible move on your part08:34
*** rushiagr_away is now known as rushiagr08:34
anteayathis isn't your fault08:35
anteayaci operators are routinely expected to accomplish tasks that they have no idea how to do08:35
anteayabut this approach has a cost08:35
anteayaand you pay it08:35
anteayaand so does the community08:35
*** watanabe_isao has quit IRC08:36
anteayawhereas management just thinks it is your fault08:36
anteayait is far better to be honest with yourself, and with us08:36
*** wojdev has joined #openstack-meeting08:36
anteayaand have the permissions on the account set in such a way that the operator is cognizant of the ramifications of their actions08:36
anteayaand new people just aren't08:37
anteayahence we learned to restrict accounts run by new ci operators08:37
anteayawhich usually is new ci accounts08:37
anteayaI don't know if I have other examples of a running ci account that is just handed off to a new person08:38
lennybAs I said, I have enough experience in the field and enough support of the team and of the community ( as I see ) to continue running our CIs. logs will be fixed. Nova CI will be updated and appropriate email will be sent to the list08:41
anteayaI don't know as you heard anything I said08:41
anteayasigh08:41
anteayaI guess we just have to do this the hard way08:42
anteayaas you see fit08:43
anteayaanything else I can help you with today?08:43
*** wojdev has quit IRC08:44
*** e0ne has quit IRC08:45
*** ibiris is now known as ibiris_away08:45
*** pelix has joined #openstack-meeting08:46
*** wojdev has joined #openstack-meeting08:46
*** wojdev has quit IRC08:46
*** sreshetn2 has joined #openstack-meeting08:47
*** wojdev has joined #openstack-meeting08:48
*** rajeshr has quit IRC08:50
*** SridharGaddam has joined #openstack-meeting08:50
*** lennyb_ has joined #openstack-meeting08:50
*** aranjan has joined #openstack-meeting08:51
lennybanteaya, we are currently disabling all our CIs untill this formatting issue is solved.08:51
anteayalennyb: good call08:51
anteayathanks for listening08:51
*** roeyc has joined #openstack-meeting08:51
*** epico has quit IRC08:51
anteayacan you update your system on this page: https://wiki.openstack.org/wiki/ThirdPartySystems08:52
anteaya#link https://wiki.openstack.org/wiki/ThirdPartySystems08:52
anteayaand this08:52
anteaya#link https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI08:52
anteayawith your current status please?08:52
anteayathank you so much08:52
anteayaI'm grateful08:52
anteayaif you are around in a few hours I suggest pinging asselin, he is active in the cinder channel and in the infra channel08:53
anteayaasselin he may have some suggestions about how you can get a readable format in your logs08:53
-openstackstatus- NOTICE: CI Check/Gate pipelines currently stuck due to a bad dependency creeping in the system. No need to recheck your patches at the moment.08:53
*** ChanServ changes topic to "CI Check/Gate pipelines currently stuck due to a bad dependency creeping in the system. No need to recheck your patches at the moment."08:54
anteayahe is on pacific time so should be around in 7 hours08:54
*** ibiris_away is now known as ibiris08:54
lennybthis issue was caused yesterday, when I added html support to the server that stores our logs.08:54
anteayaah08:54
anteayaokay that is making more sense now, thank you08:55
anteayaI personally have never seen this issue before08:55
anteayabut check with asselin or perhaps patrickeast08:55
anteayaone of them might have seen it previously08:55
anteayathanks for being proactive08:55
anteayaI appreciate it08:55
lennybthe logs are ok, just trying to show plain txt as html. it has nothing to do with CI itself.08:55
anteayaright I know08:56
anteayabut artifacts that are useful is important08:56
*** flcn___ has joined #openstack-meeting08:56
*** xingchao_ has joined #openstack-meeting08:56
anteayaand being proactive in ensuring what you provide is consumable goes a long way to folks recognizing that you take responsiblity for your actions08:57
*** rushiagr is now known as rushiagr_away08:57
anteayawhich translates to how they view your entire system08:57
anteayaso thank you08:57
lennybI know. Thanks for the meeting, tips and guidance08:57
*** epico has joined #openstack-meeting08:57
anteayathanks for showing up08:58
*** rushiagr_away is now known as rushiagr08:58
anteayashowing up is really _my_ only requirement08:58
anteayaanything else can be learned08:58
anteayabut you can't learn it if you don't show up08:58
anteayaso thanks08:58
anteayaand yeah looks like we are at the end08:58
anteayasee you next week, I hope, lennyb08:59
*** flcn___ has quit IRC08:59
*** kzaitsev has joined #openstack-meeting08:59
anteaya#endmeeting08:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:59
openstackMeeting ended Tue Mar 31 08:59:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-03-31-08.00.html08:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-03-31-08.00.txt08:59
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-03-31-08.00.log.html08:59
lennyb_next week I have vacation08:59
anteayaah thanks for letting me know08:59
anteayaenjoy your vacation08:59
*** flcn___ has joined #openstack-meeting08:59
*** kzaitsev has quit IRC09:00
anteayaso just as a reminder the nova-net to neutron meetings are on hold pending the outcome of the discussion started on the ml09:00
*** kzaitsev has joined #openstack-meeting09:00
*** annegentle has joined #openstack-meeting09:00
anteaya#link https://wiki.openstack.org/wiki/Meetings/Nova-nettoNeutronMigration09:00
*** xingchao_ has quit IRC09:02
*** Fdot has quit IRC09:03
*** jhenner has quit IRC09:03
*** jhenner has joined #openstack-meeting09:04
*** annegentle has quit IRC09:06
*** ildikov has quit IRC09:06
*** Fdot has joined #openstack-meeting09:07
*** tochi has quit IRC09:07
*** afazekas has joined #openstack-meeting09:11
*** yamamoto has joined #openstack-meeting09:12
*** ddieterly has joined #openstack-meeting09:12
*** sreshetn2 has quit IRC09:12
*** fawadkhaliq has joined #openstack-meeting09:14
*** Longgeek has quit IRC09:16
*** wojdev has quit IRC09:16
*** ddieterly has quit IRC09:16
*** otter768 has joined #openstack-meeting09:17
*** mpaolino has quit IRC09:18
*** ChrisPriceAB has joined #openstack-meeting09:18
*** fawadkhaliq has quit IRC09:19
*** ildikov has joined #openstack-meeting09:19
*** amotoki_ has joined #openstack-meeting09:20
*** pradipta has quit IRC09:20
*** otter768 has quit IRC09:22
*** ajmiller_ has joined #openstack-meeting09:23
*** markvoelker has joined #openstack-meeting09:23
*** pradipta has joined #openstack-meeting09:24
*** wojdev has joined #openstack-meeting09:24
*** sreshetn2 has joined #openstack-meeting09:24
*** aranjan has quit IRC09:25
*** ajmiller__ has quit IRC09:26
*** markvoelker has quit IRC09:28
*** fzdarsky is now known as fzdarsky|afk09:31
*** eugene_bag has joined #openstack-meeting09:32
*** sreshetn2 has quit IRC09:33
*** eugene_bag1 has quit IRC09:34
*** fawadkhaliq has joined #openstack-meeting09:37
*** e0ne has joined #openstack-meeting09:39
*** ajo_ is now known as ajo09:42
*** flcn___ has quit IRC09:45
*** jlibosva has joined #openstack-meeting09:46
*** ildikov has quit IRC09:54
*** moha_hunt has joined #openstack-meeting09:57
*** fawadkhaliq has quit IRC09:57
*** epico has quit IRC10:00
*** liusheng has quit IRC10:00
*** yamamoto has quit IRC10:01
*** xingchao_ has joined #openstack-meeting10:01
*** liusheng has joined #openstack-meeting10:01
*** annegentle has joined #openstack-meeting10:01
*** saneax has joined #openstack-meeting10:03
*** dims has joined #openstack-meeting10:03
*** lpeer has quit IRC10:04
*** fawadkhaliq has joined #openstack-meeting10:05
*** achanda has joined #openstack-meeting10:06
*** xingchao_ has quit IRC10:06
*** annegentle has quit IRC10:06
*** pradipta has quit IRC10:09
*** sreshetn2 has joined #openstack-meeting10:09
*** ildikov has joined #openstack-meeting10:09
*** jcoufal has joined #openstack-meeting10:09
*** wojdev_ has joined #openstack-meeting10:09
*** achanda has quit IRC10:10
*** wojdev has quit IRC10:12
*** wojdev_ is now known as wojdev10:12
*** ominakov has joined #openstack-meeting10:13
*** ddieterly has joined #openstack-meeting10:13
*** ominakov has quit IRC10:13
*** IanGovett has joined #openstack-meeting10:14
*** dhritishikhar_ has joined #openstack-meeting10:15
*** moha_hunt has quit IRC10:15
*** Longgeek has joined #openstack-meeting10:17
*** ddieterly has quit IRC10:17
*** yamamoto has joined #openstack-meeting10:17
*** moha_hunt has joined #openstack-meeting10:18
*** e0ne is now known as e0ne_10:19
*** topol has joined #openstack-meeting10:20
*** aranjan has joined #openstack-meeting10:21
*** pnavarro|off has joined #openstack-meeting10:21
*** e0ne_ is now known as e0ne10:23
*** markvoelker has joined #openstack-meeting10:24
*** dhritishikhar_ has quit IRC10:28
*** jlanoux_ has joined #openstack-meeting10:28
*** KrustyB has quit IRC10:28
*** lpeer has joined #openstack-meeting10:28
*** JRobinson__ has quit IRC10:29
*** markvoelker has quit IRC10:29
*** pdb has quit IRC10:29
*** Longgeek has quit IRC10:30
*** pdb has joined #openstack-meeting10:30
*** jlanoux has quit IRC10:31
*** eugene_bag has quit IRC10:31
*** shankarprasad has quit IRC10:35
*** haomaiwang has quit IRC10:36
*** e0ne is now known as e0ne_10:37
*** yamamoto has quit IRC10:37
*** eugene_bag has joined #openstack-meeting10:40
*** e0ne_ is now known as e0ne10:40
*** j05h has joined #openstack-meeting10:41
*** jlanoux has joined #openstack-meeting10:43
*** jlanoux_ has quit IRC10:46
*** eugene_bag1 has joined #openstack-meeting10:47
*** eugene_bag has quit IRC10:47
*** jprovazn has joined #openstack-meeting10:49
*** jtomasek has quit IRC10:49
*** chandankumar has quit IRC10:50
*** claudiub has joined #openstack-meeting10:52
*** haomaiwang has joined #openstack-meeting10:54
*** aranjan has quit IRC10:56
*** nsaje_ has quit IRC10:57
*** BrianB has quit IRC10:58
*** mmedvede has joined #openstack-meeting11:00
*** annegentle has joined #openstack-meeting11:02
*** yatin has quit IRC11:02
*** chandankumar has joined #openstack-meeting11:04
*** jtomasek has joined #openstack-meeting11:05
*** xingchao_ has joined #openstack-meeting11:06
*** ildikov has quit IRC11:06
*** BharatK has quit IRC11:07
*** annegentle has quit IRC11:07
*** jcoufal has quit IRC11:08
*** ujuc has joined #openstack-meeting11:08
*** jcoufal has joined #openstack-meeting11:08
*** jcoufal has quit IRC11:10
*** flaper87 has quit IRC11:10
*** vkmc has quit IRC11:10
*** rajeshr has joined #openstack-meeting11:11
*** _amrith_ is now known as amrith11:12
*** xingchao_ has quit IRC11:13
*** ddieterly has joined #openstack-meeting11:13
*** wojdev_ has joined #openstack-meeting11:13
*** wojdev has quit IRC11:14
*** wojdev_ is now known as wojdev11:14
*** Longgeek has joined #openstack-meeting11:17
*** fzdarsky|afk is now known as fzdarsky11:17
*** ddieterly has quit IRC11:18
*** otter768 has joined #openstack-meeting11:18
*** _nadya_ has joined #openstack-meeting11:19
*** nshaikh has quit IRC11:20
*** eugene_bag1 has quit IRC11:20
*** ildikov has joined #openstack-meeting11:22
*** flaper87 has joined #openstack-meeting11:22
*** prazumovsky has joined #openstack-meeting11:23
*** otter768 has quit IRC11:23
*** mpaolino has joined #openstack-meeting11:24
*** markvoelker has joined #openstack-meeting11:25
*** j05h has quit IRC11:26
*** flaper87 has quit IRC11:26
*** flaper87 has joined #openstack-meeting11:26
*** salv-orlando has quit IRC11:26
*** hogepodge has quit IRC11:27
*** sc68cal has quit IRC11:27
*** sc68cal has joined #openstack-meeting11:28
*** markvoelker has quit IRC11:29
*** changbl has quit IRC11:30
*** nshaikh has joined #openstack-meeting11:31
*** yatin has joined #openstack-meeting11:32
*** qwebirc66783 has joined #openstack-meeting11:34
*** qwebirc66783 has quit IRC11:35
*** chandankumar has quit IRC11:38
*** salv-orlando has joined #openstack-meeting11:40
*** rushiagr is now known as rushiagr_away11:42
-openstackstatus- NOTICE: Check/Gate unstuck, feel free to recheck your abusively-failed changes.11:49
*** wojdev_ has joined #openstack-meeting11:49
*** fawadkhaliq has quit IRC11:50
*** aranjan has joined #openstack-meeting11:52
*** wojdev has quit IRC11:52
*** wojdev_ is now known as wojdev11:52
*** weshay has joined #openstack-meeting11:53
*** MaxV has quit IRC11:53
*** sreshetn2 has quit IRC11:54
*** britthouser has quit IRC11:54
*** rushiagr_away is now known as rushiagr11:54
*** britthouser has joined #openstack-meeting11:55
*** tiswanso has quit IRC11:55
*** sreshetn2 has joined #openstack-meeting11:56
*** jjmb has quit IRC11:56
*** fawadkhaliq has joined #openstack-meeting11:57
*** fawadkha_ has joined #openstack-meeting11:57
*** mpaolino has quit IRC11:57
*** mpaolino has joined #openstack-meeting11:59
*** aepifanov1 has joined #openstack-meeting12:00
*** pnavarro|off has quit IRC12:01
*** fawadkhaliq has quit IRC12:01
*** oanufriev has joined #openstack-meeting12:02
*** aepifanov has quit IRC12:02
*** annegentle has joined #openstack-meeting12:03
*** ndipanov has quit IRC12:03
*** ildikov has quit IRC12:03
*** noslzzp has joined #openstack-meeting12:03
*** dneary has joined #openstack-meeting12:04
*** rajeshr has quit IRC12:04
*** rajeshr has joined #openstack-meeting12:06
*** annegentle has quit IRC12:08
*** xuhanp_ has quit IRC12:08
*** xuhanp has quit IRC12:08
*** dprince has joined #openstack-meeting12:09
*** erlon has joined #openstack-meeting12:09
*** MaxV has joined #openstack-meeting12:10
*** eliqiao has quit IRC12:10
*** raildo|away is now known as raildo12:11
*** nsaje_ has joined #openstack-meeting12:11
*** _nadya_ has quit IRC12:12
*** dkranz has joined #openstack-meeting12:12
*** aysyd has joined #openstack-meeting12:13
*** pnavarro|off has joined #openstack-meeting12:14
*** ddieterly has joined #openstack-meeting12:14
*** anish_ has quit IRC12:15
*** mpaolino has quit IRC12:16
*** yamamoto has joined #openstack-meeting12:16
*** wojdev has quit IRC12:17
*** markvoelker has joined #openstack-meeting12:17
*** fawadkhaliq has joined #openstack-meeting12:18
*** fawadkha_ has quit IRC12:18
*** ildikov has joined #openstack-meeting12:18
*** ddieterly has quit IRC12:19
*** amotoki_ has quit IRC12:20
*** amrith is now known as _amrith_12:21
*** jruano has joined #openstack-meeting12:23
*** dims has quit IRC12:25
*** adalbas has joined #openstack-meeting12:25
*** dims has joined #openstack-meeting12:25
*** aranjan has quit IRC12:25
*** fawadkha_ has joined #openstack-meeting12:26
*** claudiub has quit IRC12:27
*** claudiub has joined #openstack-meeting12:27
*** chandankumar has joined #openstack-meeting12:27
*** wojdev has joined #openstack-meeting12:28
*** mpaolino has joined #openstack-meeting12:28
*** fawadkhaliq has quit IRC12:30
*** nati_ueno has joined #openstack-meeting12:32
*** varora has left #openstack-meeting12:33
*** banix has joined #openstack-meeting12:33
*** amotoki_ has joined #openstack-meeting12:34
*** eugene_bag has joined #openstack-meeting12:34
*** amotoki_ has quit IRC12:34
*** tiswanso has joined #openstack-meeting12:38
*** yatin has quit IRC12:38
*** jruano has quit IRC12:38
*** yamamoto has quit IRC12:39
*** eugene_bag1 has joined #openstack-meeting12:39
*** jecarey has quit IRC12:40
*** eugene_bag has quit IRC12:41
*** e0ne is now known as e0ne_12:42
*** bknudson has joined #openstack-meeting12:42
*** radez_g0n3 is now known as radez12:43
*** e0ne_ is now known as e0ne12:43
*** kzaitsev has quit IRC12:44
*** jruano has joined #openstack-meeting12:45
*** smccully has joined #openstack-meeting12:47
*** shwetaap has joined #openstack-meeting12:49
*** ebalduf has joined #openstack-meeting12:49
*** tongli has joined #openstack-meeting12:49
*** dane_leblanc has joined #openstack-meeting12:50
*** kzaitsev has joined #openstack-meeting12:51
*** neeti has quit IRC12:53
*** ebalduf has quit IRC12:54
*** kzaitsev has quit IRC12:55
*** eugene_bag1 has quit IRC12:55
*** eugene_bag has joined #openstack-meeting12:56
*** rprakash has joined #openstack-meeting12:58
*** ildikov_ has joined #openstack-meeting12:58
*** ddieterly has joined #openstack-meeting12:58
*** Tango|2 has joined #openstack-meeting12:59
*** ildikov has quit IRC13:00
*** ajo has quit IRC13:01
*** rajeshr has quit IRC13:01
*** ajo has joined #openstack-meeting13:01
*** ajo has quit IRC13:01
*** annegentle has joined #openstack-meeting13:02
*** smccully_ has joined #openstack-meeting13:05
*** eugene_bag1 has joined #openstack-meeting13:05
*** hogepodge has joined #openstack-meeting13:05
*** eugene_bag has quit IRC13:05
*** baoli has joined #openstack-meeting13:05
*** e0ne is now known as e0ne_13:08
*** petertr7 has joined #openstack-meeting13:10
*** eharney has joined #openstack-meeting13:10
*** banix has quit IRC13:11
*** radez is now known as radez_g0n313:11
*** rbak has joined #openstack-meeting13:12
*** e0ne_ is now known as e0ne13:13
*** ddieterly has quit IRC13:16
*** xingchao_ has joined #openstack-meeting13:16
*** ddieterly has joined #openstack-meeting13:17
*** j05h has joined #openstack-meeting13:17
*** xingchao_ has quit IRC13:17
*** andrey-mp has joined #openstack-meeting13:19
*** otter768 has joined #openstack-meeting13:19
*** xingchao_ has joined #openstack-meeting13:20
*** nshaikh has quit IRC13:21
*** ddieterly has quit IRC13:21
*** aranjan has joined #openstack-meeting13:22
*** ayoung has joined #openstack-meeting13:23
*** chandankumar has quit IRC13:23
*** fawadkha_ has quit IRC13:24
*** otter768 has quit IRC13:24
*** fawadkhaliq has joined #openstack-meeting13:25
*** unicell1 has joined #openstack-meeting13:26
*** unicell has quit IRC13:26
*** jruano has quit IRC13:27
*** rushiagr is now known as rushiagr_away13:29
*** jaypipes has quit IRC13:29
*** xyang1 has joined #openstack-meeting13:30
*** banix has joined #openstack-meeting13:30
*** spzala has joined #openstack-meeting13:31
*** rbak has quit IRC13:32
*** prazumovsky has quit IRC13:33
*** saneax has quit IRC13:33
*** j05h1 has joined #openstack-meeting13:33
*** j05h has quit IRC13:35
*** sreshetn2 has quit IRC13:35
*** j05h1 has quit IRC13:36
*** j05h has joined #openstack-meeting13:36
*** sreshetn2 has joined #openstack-meeting13:36
*** Murali has quit IRC13:37
*** neelashah has joined #openstack-meeting13:39
*** garyh has joined #openstack-meeting13:41
*** dhritishikhar_ has joined #openstack-meeting13:42
*** jaypipes has joined #openstack-meeting13:42
*** alevine has joined #openstack-meeting13:44
*** topol has quit IRC13:44
*** ddieterly has joined #openstack-meeting13:45
*** topol has joined #openstack-meeting13:45
*** sreshetn2 has quit IRC13:45
*** amitgandhinz has joined #openstack-meeting13:46
*** sreshetn2 has joined #openstack-meeting13:49
*** ebalduf has joined #openstack-meeting13:50
*** mwagner_lap has quit IRC13:51
*** _amrith_ is now known as amrith13:51
*** amotoki_ has joined #openstack-meeting13:51
*** balajiiyer has joined #openstack-meeting13:52
*** banix has quit IRC13:53
*** shwetaap1 has joined #openstack-meeting13:53
*** sahid has quit IRC13:53
*** ftersin has joined #openstack-meeting13:53
*** balajiiyer has quit IRC13:54
*** ddieterly has quit IRC13:54
*** sahid has joined #openstack-meeting13:54
*** armax has joined #openstack-meeting13:55
*** FJB has joined #openstack-meeting13:55
*** ebalduf has quit IRC13:55
*** zeddii has quit IRC13:55
*** fawadkhaliq has quit IRC13:56
*** fawadkhaliq has joined #openstack-meeting13:56
*** aranjan has quit IRC13:57
*** shwetaap has quit IRC13:57
*** ildikov_ has quit IRC13:57
*** eugene_bag1 has quit IRC13:59
*** sigmavirus24_awa is now known as sigmavirus2413:59
*** rushiagr_away is now known as rushiagr13:59
*** jecarey has joined #openstack-meeting13:59
*** murugang-brcd has joined #openstack-meeting14:00
*** haleyb_ has joined #openstack-meeting14:01
*** rpodolyaka1 has joined #openstack-meeting14:01
*** rpodolyaka1 has quit IRC14:01
*** rpodolyaka1 has joined #openstack-meeting14:01
*** balajiiyer has joined #openstack-meeting14:02
lxslio/ ?14:03
lxslioh DST14:03
*** absubram has joined #openstack-meeting14:04
*** andrey-mp has left #openstack-meeting14:04
*** rbak has joined #openstack-meeting14:05
*** mrmartin has quit IRC14:05
*** ayoung has quit IRC14:05
*** gokrokve has joined #openstack-meeting14:06
*** sreshetn2 has quit IRC14:06
*** sreshetn2 has joined #openstack-meeting14:06
*** BrianB_ has joined #openstack-meeting14:07
*** rpodolyaka1 has quit IRC14:07
*** Tross has quit IRC14:07
*** Tross has joined #openstack-meeting14:07
*** spradeepv has joined #openstack-meeting14:08
*** dkranz has quit IRC14:08
*** spradeepv has left #openstack-meeting14:09
*** ChuckC has quit IRC14:09
*** mpaolino has quit IRC14:10
*** nelsnelson has joined #openstack-meeting14:10
*** _nadya_ has joined #openstack-meeting14:11
*** baoli has quit IRC14:12
*** Mandell has joined #openstack-meeting14:12
*** carl_baldwin has joined #openstack-meeting14:13
*** ildikov_ has joined #openstack-meeting14:13
*** VW_ has joined #openstack-meeting14:13
*** wojdev_ has joined #openstack-meeting14:16
*** wojdev has quit IRC14:17
*** wojdev_ is now known as wojdev14:17
*** dhritishikhar_ has quit IRC14:18
*** ayoung has joined #openstack-meeting14:18
*** Mandell has quit IRC14:21
*** timcline has joined #openstack-meeting14:21
*** Mandell has joined #openstack-meeting14:21
*** alevine has quit IRC14:21
*** dkranz has joined #openstack-meeting14:21
*** banix has joined #openstack-meeting14:21
*** carl_baldwin has quit IRC14:22
*** ftersin has quit IRC14:22
*** enikanorov has quit IRC14:23
*** mpaolino has joined #openstack-meeting14:23
*** timcline has quit IRC14:24
*** timcline has joined #openstack-meeting14:24
*** jruano has joined #openstack-meeting14:25
*** banix has quit IRC14:26
*** timcline_ has joined #openstack-meeting14:26
*** mattgriffin has joined #openstack-meeting14:27
*** enikanorov has joined #openstack-meeting14:27
*** sdake has joined #openstack-meeting14:29
*** timcline has quit IRC14:30
*** absubram has quit IRC14:31
*** zz_jgrimm is now known as jgrimm14:31
*** baoli has joined #openstack-meeting14:33
*** xingchao_ has quit IRC14:34
*** Tango|2 has quit IRC14:36
*** haleyb_ has quit IRC14:38
*** nati_ueno has quit IRC14:39
*** ChuckC has joined #openstack-meeting14:39
*** esheffield has joined #openstack-meeting14:40
*** haleyb_ has joined #openstack-meeting14:40
*** banix has joined #openstack-meeting14:40
*** hemnafk is now known as hemna14:44
*** haleyb_ has quit IRC14:45
*** Mandell has quit IRC14:47
*** haleyb_ has joined #openstack-meeting14:48
*** haleyb_ has quit IRC14:48
*** amotoki_ has quit IRC14:49
*** amakarov_away is now known as amakarov14:50
*** chandankumar has joined #openstack-meeting14:50
*** eugene_bag has joined #openstack-meeting14:50
*** ebalduf has joined #openstack-meeting14:51
*** ayoung has quit IRC14:51
*** ndipanov has joined #openstack-meeting14:51
*** aranjan has joined #openstack-meeting14:52
*** jaypipes has quit IRC14:53
*** carl_baldwin has joined #openstack-meeting14:54
*** FJB has quit IRC14:55
*** ttrifonov is now known as zz_ttrifonov14:56
*** ebalduf has quit IRC14:56
*** marun has joined #openstack-meeting14:56
*** AlkaD has joined #openstack-meeting14:57
*** jungleboyj_afk has quit IRC14:57
*** eugene_bag1 has joined #openstack-meeting14:57
*** juzuluag has joined #openstack-meeting14:58
*** dulek has quit IRC14:58
*** juzuluag has quit IRC14:58
bauzas#startmeeting gantt15:00
openstackMeeting started Tue Mar 31 15:00:01 2015 UTC and is due to finish in 60 minutes.  The chair is bauzas. 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
*** eugene_bag has quit IRC15:00
bauzasaloha, anyone here ?15:00
edleafe\o15:00
alex_xuo/15:00
bauzasn0ano is having a meeting conflict so I'm chairing for this week15:00
*** AmirBaleghi114 has joined #openstack-meeting15:00
bauzasokay, waiting a few mins and then we begin15:01
lxslio/15:01
*** PaulMurray has joined #openstack-meeting15:01
*** baoli has quit IRC15:01
*** claudiub has quit IRC15:01
*** rushil has quit IRC15:01
*** rpothier has joined #openstack-meeting15:02
*** wojdev has quit IRC15:03
bauzasokay, let's begin and people will come15:03
bauzasso15:03
bauzas#link https://etherpad.openstack.org/p/nova-scheduler-meeting15:03
bauzassorry I had no time for sending out an email15:03
bauzasfeel free to add your points in there15:04
*** ayoung has joined #openstack-meeting15:04
bauzas#topic meeting name15:04
*** openstack changes topic to "meeting name (Meeting topic: gantt)"15:04
bauzasso, perhaps some of you already saw http://lists.openstack.org/pipermail/openstack-dev/2015-March/060179.html15:04
bauzas#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/060179.html15:04
*** dims has quit IRC15:05
bauzasthat's bad to not have n0ano today but would like to get your views15:05
bauzassoooooo15:05
*** zz_ttrifonov is now known as ttrifonov15:05
edleafeI always thought of Gantt related to scheduler like Cinder related to nova-volume15:05
*** baoli has joined #openstack-meeting15:05
bauzasI would like to see this meeting the last time I'm calling it Gantt15:05
bauzasuntil we really spin off Gantt15:05
*** kvidvans_ has joined #openstack-meeting15:06
*** rpothier has left #openstack-meeting15:06
edleafebauzas: +1 on calling this nova-scheduler15:06
bauzasedleafe: agreed but we're now in the same state than Cinder :)15:06
bauzas*not15:06
bauzasdammit, stupid fingers15:06
*** BrianShang_ has joined #openstack-meeting15:06
edleafebauzas: exactly, which is why it is premature to call this Gantt15:07
bauzasok, anyone else ? feel free to give your point at the thread15:07
alex_xubut we discussion what will look like for gantt at future at here also?15:07
bauzasalex_xu: that's not actually bad15:07
bauzasalex_xu: we can still discuss on the next features and the target15:07
bauzasalex_xu: it will just help newcomers to join us15:08
*** AlkaD has quit IRC15:08
*** annegentle has quit IRC15:08
*** dims_ has joined #openstack-meeting15:08
bauzasand my point goes to jay's comments about doubts of the legal issues we could raise15:08
*** mrmartin has joined #openstack-meeting15:08
*** BrianShang has quit IRC15:08
bauzasbefore actually being sure that Gantt is the right codename, we should also ask the Foundation if that's correct for a project name15:08
bauzasI know how it's painful to rewrite the namespace...15:09
PaulMurraywasn't gantt french?15:09
bauzas(for teasers, just look at Climate/Blazar repo)15:09
edleafeNot sure about legal problems. The name 'Gantt' for scheduling is over 100 years old15:09
*** xingchao_ has joined #openstack-meeting15:09
edleafepretty generic at this point15:09
bauzasPaulMurray: everything good is French, don't you know, English man ?15:10
bauzasedleafe: yeah, but I would like to be sure we're not wrong15:10
*** kvidvans_ has quit IRC15:10
bauzasso, back to the topic, feel free to leave your comments on the thread15:11
bauzason the mean time...15:11
bauzas#action bauzas to check with Foundation about possible legal issues with the "Gantt" codename15:11
*** eugene_bag has joined #openstack-meeting15:11
*** eugene_bag1 has quit IRC15:11
*** MaxV has quit IRC15:11
*** lennyb has quit IRC15:11
bauzasokay, let's continue, I just would like to see all your point before the next meeting15:12
bauzas#info Comments appreciated on http://lists.openstack.org/pipermail/openstack-dev/2015-March/060179.html15:13
*** ajmiller has joined #openstack-meeting15:13
bauzas#topic Patch status15:13
*** openstack changes topic to "Patch status (Meeting topic: gantt)"15:13
bauzasanyone ? I'm passing15:13
*** annegentle has joined #openstack-meeting15:13
bauzasI'm quite busy with the cells fixable stuff15:13
*** reed has joined #openstack-meeting15:13
edleafeSaw that PaulMurray's first patch in the series finally merged. Congrats!15:14
bauzasyay !15:14
PaulMurraysee what happens when your not looking !15:14
bauzasat least we're in a better shape than before even if I wanted to have the RT objectified by Kilo :(15:14
PaulMurrayWell, we actually got 5 patches in a few days - including lxsli migration patches15:15
*** ajmiller_ has quit IRC15:15
bauzasPaulMurray: if that's a matter of *not* reviewing your changes, let me know and I'll make you a pleasure with this :)15:15
*** MaxV has joined #openstack-meeting15:15
bauzasPaulMurray: indeed, kudos to lxsli too15:16
PaulMurraybauzas, you need to be careful with you language there - that sounded a bit .... wrong15:16
bauzasPaulMurray: French joker card15:16
*** claudiub has joined #openstack-meeting15:16
PaulMurraybauzas, it was about core reviews....15:16
bauzasPaulMurray: then I missed your point15:17
bauzas:)15:17
PaulMurrayno, I mean we lacked core reviews until last minute - your language was still almost rude15:17
PaulMurray:)15:17
*** emagana has joined #openstack-meeting15:18
*** MarkAtwood has joined #openstack-meeting15:18
ndipanovlol15:18
PaulMurrayndipanov, thanks for your help with the patches15:18
ndipanovPaulMurray, I am very sad that stuff didn;t make it for kilo15:18
ndipanovawesome work15:18
*** carl_baldwin has quit IRC15:19
bauzasindeed15:19
bauzasthere are some -1s IIRC15:19
PaulMurrayonly you15:19
bauzas(from me probably)15:19
bauzasyay, shall I iterate over those still ?15:19
PaulMurrayand jenkins15:19
PaulMurrayI will rebase soon15:20
bauzasman, I don't know who this Jenkins guy is, but he's quite rude too15:20
bauzasanyway15:20
*** otter768 has joined #openstack-meeting15:20
bauzasany other scheduler-related stuff that we should discuss ?15:20
*** carl_baldwin_ has joined #openstack-meeting15:20
ndipanovbauzas, 2 things I'd like to mention15:21
bauzasndipanov: go on15:21
ndipanovthat became apparent to me only lately15:21
ndipanov1 is that pci tracker as it stands now is reasonably buggy15:21
bauzaswell...15:22
bauzasndipanov: you know my opinion on that15:22
ndipanovI am not sure how easy that is to fix, but I know what the main cause of it is15:22
ndipanovyeah...15:22
*** tsekiyama has joined #openstack-meeting15:22
bauzasndipanov: again, it's not a design problem15:22
ndipanovI think it actually is15:22
bauzasndipanov: it's about the integration with the existing15:22
ndipanovyes15:23
ndipanovtrye15:23
ndipanovtrue15:23
bauzasndipanov: yeah I had a discussion with sean dague and dansmith about the PCI optionnality15:23
*** aranjan has quit IRC15:23
*** pballand has joined #openstack-meeting15:23
ndipanovso expect work going into that as soon as we are using objects in RT (Paul's patches land)15:23
bauzasndipanov: well, the problem is also that PCI is always tracking stuff while filters are perhaps not enabled15:23
*** zigo__ is now known as zigo15:23
*** dannywilson has joined #openstack-meeting15:24
ndipanovthat's a whole other story15:24
bauzastrue15:24
bauzasand too broad for discussing it there15:24
*** dannywilson has quit IRC15:24
ndipanovsecond is that there have been several issues with "resources" such as pci and numa15:25
bauzasndipanov: so yeah, I expect PaulMurray's work on objectifying the RT could help us a lot15:25
*** otter768 has quit IRC15:25
ndipanovthat I feel are basically the same class of errors15:25
*** dannywilson has joined #openstack-meeting15:25
bauzasndipanov: any precise issues that you could share with us ?15:25
ndipanovyes15:25
* ndipanov looks for bugs15:25
bauzasndipanov: in the meantime, could we jump onto the next topic and come back to your point for the open discussion ?15:26
bauzasthe next topic is Vancouver summit talks15:26
bauzasokay, guessing it's a yes15:27
ndipanovhttps://bugs.launchpad.net/nova/+bug/141766715:27
openstackLaunchpad bug 1417667 in OpenStack Compute (nova) "migration/evacuation/rebuild/resize of instance with dedicated cpus needs to recalculate cpus on destination" [Medium,In progress] - Assigned to Bart Wensley (bartwensley)15:27
bauzas#topicVancouver discussion ideas15:27
ndipanovyes15:27
bauzaserm15:27
bauzas#topic Vancouver discussion ideas15:27
*** openstack changes topic to "Vancouver discussion ideas (Meeting topic: gantt)"15:27
ndipanovping me once open-discussion happens15:27
*** chandankumar has quit IRC15:27
bauzasndipanov: sure thing15:27
bauzasso, any ideas so far ?15:27
bauzasjust to be clear, I have no precise information about how the Design Summit will be held, only that we'll have a nice sightseeing from the place we'll be :)à15:28
*** wicope has joined #openstack-meeting15:29
*** mrmartin has quit IRC15:29
bauzasttx proposed a discussion about the Design Summit format and talks for today's cross-project meeting15:29
bauzas#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/060258.html15:29
*** stevemar has joined #openstack-meeting15:29
*** jlibosva has quit IRC15:30
bauzasI shouldn't be able to attend today's meeting (damn DST) but feel free to attend15:30
*** maurosr has quit IRC15:30
*** elo1 has quit IRC15:31
*** Tango|2 has joined #openstack-meeting15:31
edleafeI'll try to make it15:31
*** kebray has joined #openstack-meeting15:31
*** jdurgin1 has joined #openstack-meeting15:31
bauzascool15:31
bauzasanyway, I propose to defer our discussions until next week15:31
edleafeI have another call then, but I can lurk15:31
bauzasso that we should get a better picture about that15:31
bauzasalso15:31
bauzasmikal proposed an etherpad for tracking *nova related* discussions http://lists.openstack.org/pipermail/openstack-dev/2015-March/060024.html15:32
*** garyk has quit IRC15:32
bauzas#link https://etherpad.openstack.org/p/liberty-nova-summit-ideas15:32
bauzasfeel free to point out any point about our concerns that are related to Nova15:32
bauzasat the moment, the only related point to the scheduler is about the split, but I guess we should have more to discuss15:33
*** banix has quit IRC15:34
bauzasokay, last but not least topic unless someone's screaming in the next minute15:34
*** scheuran has quit IRC15:35
*** maurosr has joined #openstack-meeting15:35
bauzaslet's openly open the open discussion15:35
*** atiwari has joined #openstack-meeting15:35
bauzas#topic open discussion15:35
*** openstack changes topic to "open discussion (Meeting topic: gantt)"15:35
*** BrianShang has joined #openstack-meeting15:36
bauzasso, ndipanov had some bugs to provide us related to the PCI and NUMA resource tracking15:36
bauzasndipanov: ping15:36
*** BrianShang_ has quit IRC15:37
*** asselin has quit IRC15:38
*** jlanoux has quit IRC15:38
edleafepinged him in openstack-nova15:39
bauzaswe can wait a few more mins, he's possibly afk15:40
*** thedodd has joined #openstack-meeting15:40
*** eugene_bag has quit IRC15:40
bauzasany other subject people are wanting to discuss meanwhile ?15:40
bauzasoh15:40
bauzasthat reminds me one big thing I forgot to mention15:40
bauzas#link https://review.openstack.org/#/c/168682/15:41
bauzas#link https://review.openstack.org/#/c/168883/15:41
bauzasboth are related to the existing Gantt repo15:41
bauzaswhich is actually just a wrong thing15:42
*** xingchao_ has quit IRC15:42
bauzas(speaking of the existing repo)à15:42
*** Apoorva has joined #openstack-meeting15:42
edleafebauzas: I wasn't involved in that Gantt work. Is there value in keeping it?15:42
edleafebauzas: or should we start clean?15:43
bauzasedleafe: honestly, nothing but a trace15:43
*** ttrifonov is now known as zz_ttrifonov15:43
*** moha_hunt has quit IRC15:43
bauzasedleafe: the real problem is how painful it is to remove a repo or rename it15:43
*** elo has joined #openstack-meeting15:43
*** MaxV has quit IRC15:43
*** MaxV has joined #openstack-meeting15:44
ndipanovbauzas, right15:44
bauzasedleafe: so we keep it as a reference but with a big disclaimer saying that the code is just messy15:44
edleafebauzas: ok, but these are simply to get them out of infra, right?15:44
bauzasedleafe: not really15:44
ndipanov https://bugs.launchpad.net/nova/+bug/141766715:44
openstackLaunchpad bug 1417667 in OpenStack Compute (nova) "migration/evacuation/rebuild/resize of instance with dedicated cpus needs to recalculate cpus on destination" [Medium,In progress] - Assigned to Bart Wensley (bartwensley)15:44
ndipanovis the bug15:44
bauzasedleafe: all of the decisions would require a manual intervention15:44
*** comay has joined #openstack-meeting15:44
bauzasanyway15:44
bauzasback to ndipanov's point15:44
ndipanovright15:45
ndipanovso these kind of problems15:45
ndipanovexist with15:45
bauzasoh this15:45
ndipanovwhat I can only describe as15:45
ndipanov"stateful" resources15:45
*** mestery has quit IRC15:45
bauzasmmm15:45
ndipanovwhere next allocation is the function of previous allocations15:45
ndipanovnot only thieir count15:45
ndipanovtwo of those that we have are numa and pci stuff15:46
*** dprince has quit IRC15:46
bauzasndipanov: I see, the problem being that's a bucket of instances, and not a single instance boot, right ?15:46
ndipanovno15:46
bauzasokay, then I misunderstood15:46
ndipanovso the problem is when migrating/resizing15:47
ndipanovand evacuating (although I am not sure how that should work)15:47
bauzasoooooh understood15:47
bauzaspolicies are not enforced15:47
ndipanovem15:47
ndipanovno15:47
bauzasare we sure that the reporter didn't ask for a destination host ?15:47
*** MaxV has quit IRC15:48
bauzasby saying "policies", I was meaning that the filters were not taken in account ( not the nova policy thing)15:48
ndipanovwell that's one thing15:48
alex_xundipanov: because the request spec and status after boot was stored in single object?15:48
bauzasndipanov: you know that migrations are able to bypass the scheduler if a dest host is specified ?15:48
*** ildikov_ has quit IRC15:49
ndipanovso the thing is15:49
ndipanovthe other thing15:49
bauzasndipanov: we totally get rid of the scheduler when we're migrating to a specified dest host15:49
ndipanovis that we track migrations via flavor15:49
bauzasyup15:49
ndipanovbut you can't do that for pci/numa15:49
ndipanovand similar resources15:50
ndipanovbecause it is not only the "count"15:50
ndipanovthat is important15:50
ndipanovbut the actual allocation15:50
ndipanovat the time of claim15:50
PaulMurrayits not the fact that there is a device - its which one15:50
bauzasndipanov: but claims are reported as usage right ?15:50
ndipanovbecause it may be different at the time of the RT loop because it is a function of all previous allocations on the host15:51
ndipanovyes PaulMurray that's exactly it15:51
ndipanovthis likely means that we have to keep a record of said allocations with the migration row15:51
ndipanovwhich is fine15:51
ndipanovI guess15:51
*** ebalduf has joined #openstack-meeting15:52
*** sreshetn2 has quit IRC15:52
ndipanovbut 1) it needs to be written 2) I wonder if there is a more general API we could have15:52
*** numan has quit IRC15:52
ndipanovonce we actually have resources15:52
bauzasndipanov: I'm quite blind on the NUMA stuff (with much regret)15:52
ndipanovso my question is15:52
ndipanovwould it be ok to sprinkle these 2 special cases as columns15:53
bauzasndipanov: but I was thinking that we were tracking that for example pCPU0 was pinned as an usage15:53
ndipanovwe are15:53
ndipanovbut you can't recreate which one from just the flavor15:53
*** fawadkhaliq has quit IRC15:53
ndipanovyou have to store the actual allocation somewhere15:53
bauzasndipanov: oh I see, that's not persisteed15:54
ndipanovfor boot - we store it on the instance15:54
ndipanovbut for migration...15:54
PaulMurrayndipanov, if claims become a first class object, would that be the place?15:54
ndipanovPaulMurray, maybe15:54
ndipanovyes15:54
bauzasI tend to say that we definitely miss bp/resource-objects15:54
ndipanovyes15:54
ndipanovso my question was15:54
ndipanovshould we hack on fixing it and hope to generalize it later with Claim/resource objects15:55
ndipanovor the other way around15:55
*** chandankumar has joined #openstack-meeting15:55
bauzaswell, bp/resource-objects was expected to be worked during Kilo15:55
*** leeantho has joined #openstack-meeting15:55
bauzasso we should loop back with jaypipes15:55
ndipanovbauzas, the thing is that it's a bug15:56
ndipanovbut one that seems to be easily generalizable15:56
ndipanovif there were a place to generalize it15:56
*** ebalduf has quit IRC15:56
bauzasndipanov: agreed, but I think the generalization has to be done alas bp/resource-objects15:56
ndipanovright15:57
ndipanovok well15:57
bauzasndipanov: that said, I would appreciate your bugfix15:57
ndipanovthere is a patch that proposes this for numa already15:57
bauzasndipanov: because it gives us a path for fixing it15:57
ndipanovI will look into the pci side of things as well15:58
bauzasndipanov: oh right, the bug is mentioning it15:58
ndipanovand then hopefully we'll meet in the middle with resource objects15:58
bauzasndipanov: https://review.openstack.org/163440 is the one about NUMA ?15:58
bauzascaution : not having yet reviewed the change15:58
ndipanovyes!!15:58
bauzaswoaw, fat one then15:59
bauzasbut that sounds doable15:59
bauzasndipanov: do you think we should target it for RC1 ?15:59
bauzasndipanov: I haven't yet reviewed the change so I don't know if it's landable yet15:59
*** neelashah has quit IRC16:00
bauzasdamn, we're running out of time16:00
*** aepifanov1 has quit IRC16:00
ndipanovbauzas, with db migrations...16:00
bauzaslet's discuss that offline and free up the lock16:00
*** emagana has quit IRC16:00
ndipanovI think not16:00
edleafebauzas: it hasobject version bumps16:00
bauzasndipanov: edleafe: ooooh16:00
ndipanovI don't think it's that critical16:00
bauzasthen yes, it will be fixed in Liberty16:00
ndipanovworth a relnote for sure16:00
bauzasok guys, take care16:00
bauzas#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
edleafeyes16:01
openstackMeeting ended Tue Mar 31 16:01:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-31-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-31-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-31-15.00.log.html16:01
*** claudiub has quit IRC16:01
*** Guest86681 has quit IRC16:01
*** SridharG has left #openstack-meeting16:02
*** rpothier has joined #openstack-meeting16:03
*** eghobo has joined #openstack-meeting16:03
*** mestery has joined #openstack-meeting16:03
*** e0ne is now known as e0ne_16:03
*** rpothier has left #openstack-meeting16:04
*** emagana has joined #openstack-meeting16:04
*** neelashah has joined #openstack-meeting16:05
*** arnaud___ has joined #openstack-meeting16:08
*** unicell1 has quit IRC16:08
*** aimon has quit IRC16:08
*** e0ne_ has quit IRC16:08
*** carl_baldwin_ has quit IRC16:09
*** dflorea has joined #openstack-meeting16:09
*** Sukhdev has joined #openstack-meeting16:11
*** Clint has joined #openstack-meeting16:11
*** matrohon has quit IRC16:11
*** jruano has quit IRC16:12
*** anish_ has joined #openstack-meeting16:13
*** dprince has joined #openstack-meeting16:14
*** sreshetn2 has joined #openstack-meeting16:14
*** e0ne has joined #openstack-meeting16:14
*** nati_ueno has joined #openstack-meeting16:15
*** ivar-lazzaro has joined #openstack-meeting16:16
*** Fdot has quit IRC16:16
*** ivar-lazzaro has quit IRC16:17
*** nati_ueno has quit IRC16:17
*** leeantho has quit IRC16:17
*** ivar-lazzaro has joined #openstack-meeting16:17
*** zeddii has joined #openstack-meeting16:18
*** claudiub has joined #openstack-meeting16:19
*** xingchao_ has joined #openstack-meeting16:19
*** nati_ueno has joined #openstack-meeting16:20
*** derekh has quit IRC16:21
*** ildikov_ has joined #openstack-meeting16:22
*** garyk has joined #openstack-meeting16:24
*** fbo has joined #openstack-meeting16:25
*** esheffield has quit IRC16:26
*** mtanino has joined #openstack-meeting16:27
*** redixin has joined #openstack-meeting16:27
*** ivar-laz_ has joined #openstack-meeting16:27
*** xingchao_ has quit IRC16:27
*** ygbo has quit IRC16:29
*** yamahata has joined #openstack-meeting16:29
*** ivar-lazzaro has quit IRC16:30
*** dhritishikhar_ has joined #openstack-meeting16:32
*** arnaud___ has quit IRC16:32
*** carl_baldwin has joined #openstack-meeting16:33
*** unicell has joined #openstack-meeting16:34
*** aranjan has joined #openstack-meeting16:35
*** ujuc has quit IRC16:35
*** baoli has quit IRC16:35
*** rprakash has quit IRC16:35
*** PaulMurray has left #openstack-meeting16:36
*** wojdev has joined #openstack-meeting16:36
*** baoli has joined #openstack-meeting16:37
*** annegentle has quit IRC16:40
*** mpaolino has quit IRC16:40
*** marrusl has quit IRC16:41
*** pritesh has joined #openstack-meeting16:42
*** aimon has joined #openstack-meeting16:42
*** marrusl has joined #openstack-meeting16:43
*** murugang-brcd has quit IRC16:44
*** chandankumar has quit IRC16:44
*** harlowja_away is now known as harlowja_16:45
*** SumitNaiksatam has quit IRC16:46
*** Swami has joined #openstack-meeting16:46
*** dkusidlo has quit IRC16:46
*** absubram has joined #openstack-meeting16:47
*** jaypipes has joined #openstack-meeting16:48
*** jlanoux has joined #openstack-meeting16:48
*** chandankumar has joined #openstack-meeting16:48
*** bobmel has quit IRC16:49
*** dims_ has quit IRC16:51
*** dims_ has joined #openstack-meeting16:51
*** mwagner_lap has joined #openstack-meeting16:52
*** PerfBeing has joined #openstack-meeting16:53
*** MaxV has joined #openstack-meeting16:54
*** mpaolino has joined #openstack-meeting16:54
*** MarkAtwood has quit IRC16:54
*** amaretskiy has joined #openstack-meeting16:54
*** fawadkhaliq has joined #openstack-meeting16:56
*** neelashah has quit IRC16:56
*** e0ne is now known as e0ne_16:56
*** sridhar_ram has joined #openstack-meeting16:57
*** xingchao_ has joined #openstack-meeting16:57
*** PerfBeing is now known as prashantS16:57
*** meteorfox has joined #openstack-meeting16:58
*** mattgriffin has quit IRC17:00
*** welldannit has quit IRC17:00
*** s3wong has joined #openstack-meeting17:01
*** psd has joined #openstack-meeting17:02
*** msdubov has joined #openstack-meeting17:02
boris-42#startmeeting Rally17:02
openstackMeeting started Tue Mar 31 17:02:51 2015 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: Rally)"17:02
openstackThe meeting name has been set to 'rally'17:02
boris-42meteorfox: ping17:02
*** rvasilets has joined #openstack-meeting17:02
boris-42msdubov: ping17:02
rvasiletso/17:03
meteorfoxboris-42: hey17:03
msdubovboris-42: hi!17:03
boris-42andreykurilin: rvasilets oanufriev ping17:03
boris-42hey hey everybody17:03
boris-42=)17:03
*** xingchao_ has quit IRC17:03
prashantSboris-42: hey! I'm here for my first meeting@Rally. Work at Rackspace with meteorfox17:04
meteorfoxboris-42: prashantS  will also join us today, we are from the same team here at Rackspace, and he wants to start contributing to Rally :)17:04
boris-42prashantS: hi there17:04
boris-42prashantS: nice to meet you=)17:04
prashantShi boris-42. Same here :)17:04
oanufrievhi17:04
*** wojdev has quit IRC17:04
boris-42So let's start17:05
*** andreykurilin_ has joined #openstack-meeting17:05
*** claudiub has quit IRC17:05
boris-42#topic Rally proposal to add to OpenStack17:05
*** openstack changes topic to "Rally proposal to add to OpenStack (Meeting topic: Rally)"17:05
andreykurilin_hi all)17:05
boris-42I made proposal https://review.openstack.org/#/c/169357/17:05
boris-42andreykurilin_: hi hi17:05
boris-42So probably rally will be moved from stackforge to openstack space17:05
boris-42at least I hope so=)17:06
meteorfoxboris-42: nice!17:06
*** yfried has joined #openstack-meeting17:06
yfriedhi17:06
boris-42yfried: hi hi17:06
andreykurilin_it would be great!17:06
boris-42yfried: as you didn't see I made a proposal https://review.openstack.org/#/c/169357/17:06
*** e0ne_ is now known as e0ne17:06
boris-42yfried: to move rally from stackforge to openstack space17:06
*** chandankumar has quit IRC17:06
yfriedboris-42: too late to get us all ATC discount :)17:07
boris-42yfried: lol=017:07
*** jlibosva has joined #openstack-meeting17:07
boris-42yfried: so next time next time=)17:08
meteorfoxboris-42: where can I read more about the process to proposing a project to move from stackforge to openstack proper?17:08
boris-42meteorfox: mabye this https://github.com/openstack/governance/blob/master/reference/new-projects-requirements.rst ?17:08
*** baoli has quit IRC17:08
meteorfoxboris-42: thanks17:08
*** nati_ueno has quit IRC17:09
yfriedboris-42: where can I find mtg log?17:09
boris-42yfried: oh there are somewhere17:09
yfriedboris-42: later then17:10
boris-42yfried: http://eavesdrop.openstack.org/irclogs/17:10
*** radez_g0n3 is now known as radez17:10
yfriedtnx17:10
meteorfoxboris-42: heh. wouldn't this be too much noise in the ML? "The project uses the openstack-dev ML to discuss issues"17:10
meteorfoxboris-42:  that's one the requirements for an OS project17:10
*** kzaitsev has joined #openstack-meeting17:10
*** pritesh has quit IRC17:11
boris-42meteorfox: hm?17:11
*** eghobo has quit IRC17:11
boris-42meteorfox: and we are using sometimes mailing list for dicussion17:11
*** kzaitsev has left #openstack-meeting17:11
meteorfoxboris-42: oh ok. I should subscribe to openstack-dev then17:11
*** eghobo has joined #openstack-meeting17:12
boris-42meteorfox: but I am trying to discuss stuff in more constructive ways17:12
*** bvandenh has joined #openstack-meeting17:12
boris-42meteorfox: e.g. specs/irc/google docs17:12
meteorfoxboris-42: yeah I know, I do like Rally's approach better17:12
boris-42meteorfox: so mailing list should be for something more urgent and important updates17:13
meteorfoxboris-42: gotcha17:13
boris-42so next TC meeting should be on 7th april17:14
boris-42It will be nice if you guys ^ meteorfox yfried could join it17:14
*** baoli has joined #openstack-meeting17:14
yfriedboris-42: Is this an IRC mtg? I'll try to attend17:15
boris-42yfried: yep IRC meeting17:15
boris-42yfried: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee17:15
meteorfoxboris-42: sure, I will17:15
*** SumitNaiksatam has joined #openstack-meeting17:16
yfriedboris-42: anything else on this subject?17:16
boris-42yfried: I don't think so =)17:16
boris-42except well done guys=)17:16
*** eugene_bag has joined #openstack-meeting17:17
boris-42okay let's move to next topic17:17
boris-42#topic Support existing users17:18
*** openstack changes topic to "Support existing users (Meeting topic: Rally)"17:18
*** haneef has joined #openstack-meeting17:18
boris-42So this was VERY VERY OLD task17:18
*** johnthetubaguy is now known as zz_johnthetubagu17:18
boris-42and I had to refactor whole Rally many times=)17:18
yfriedboris-42: also very very important in benchmarking production clouds17:18
*** bvandenh has quit IRC17:18
boris-42https://review.openstack.org/#/c/168524/17:18
*** funzo has joined #openstack-meeting17:18
*** BrianB_ has quit IRC17:18
boris-42yfried: yep that is why I was working on it17:18
boris-42yfried: and now it is finished in that patch ^17:19
boris-42I need to improve a bit cleanup mechanism17:19
boris-42I hope to do it today17:19
*** baoli has quit IRC17:19
boris-42and that is all=)17:19
boris-42so We don't drop admin requirements for now,17:19
yfriedboris-42: how come it doesn't have a bp tracker?17:19
*** baoli has joined #openstack-meeting17:20
boris-42yfried: it had a long long ago17:20
*** baoli has quit IRC17:20
*** dflorea has quit IRC17:20
yfriedboris-42: ok.17:20
boris-42so it's great that it is finished=)17:21
*** dflorea has joined #openstack-meeting17:21
boris-42any questions?17:21
*** otter768 has joined #openstack-meeting17:21
boris-42andreykurilin_: yfried meteorfox ^17:21
meteorfoxboris-42: the way to specify users seems a little verbose17:21
yfriedboris-42: will review17:21
boris-42meteorfox: what do you mean?17:22
meteorfoxboris-42: but, besides that, all I can think is reading the user accounts from a CSV, or an SQL database17:22
*** chandankumar has joined #openstack-meeting17:22
*** rushil has joined #openstack-meeting17:22
boris-42meteorfox: hm you are specifing users when you are creating deployment17:23
*** achanda has joined #openstack-meeting17:23
boris-42meteorfox: like now you are specifing just admin17:23
boris-42meteorfox: you are able to specify users as well17:23
boris-42meteorfox: so you don't need to do this for every task17:23
boris-42just 1 per deployment creation17:23
meteorfoxboris-42: so, when using predefined users, you might 50+ users17:24
meteorfoxI know this can be done programmatically17:24
meteorfoxboris-42: anyway, it's fine17:24
boris-42meteorfox: so you can extend ExistingUsers17:24
boris-42meteorfox: ExistingCloud17:25
boris-42meteorfox: plugin to accept one more argument17:25
boris-42meteorfox: path to csv file with existing users17:25
yfriedboris-42: if users are defined in deployment creation, we should also be able to update (add/remove users) an existing deployment17:25
meteorfoxboris-42: that's a good idea17:25
*** dflorea has quit IRC17:25
*** otter768 has quit IRC17:26
meteorfoxboris-42: it just the static JSON file, can cause some pain when updating passwords and users17:26
boris-42yfried: meteorfox you can alwasy recreate deployment17:26
*** rvasilets__ has joined #openstack-meeting17:27
yfriedboris-42: seems a bit excessive. also - will it keep dep data (old tests, etc)17:27
yfried?17:27
meteorfoxboris-42: so, having someway to load from a SQL table dynamically, could be useful.17:27
*** dflorea has joined #openstack-meeting17:27
boris-42yfried: meteorfox let's dicuss this in separated topic17:27
meteorfoxboris-42: ok17:28
boris-42besides that do we have something regarding to this feature?17:28
yfriedboris-42: ok17:28
boris-42so any other questions?17:29
boris-42or we are moving to "deployment update" command?17:29
boris-42msdubov: amaretskiy redixin ^17:30
boris-42yfried: meteorfox ^17:30
oanufrievhave no questions17:30
amaretskiyno questions17:30
yfriednone17:30
boris-42#topic deployment update functionality17:30
*** openstack changes topic to "deployment update functionality (Meeting topic: Rally)"17:30
*** bvandenh has joined #openstack-meeting17:30
meteorfoxnone17:31
boris-42okay now let's discuss it here17:31
*** banix has joined #openstack-meeting17:31
boris-42meteorfox: yfried amaretskiy ping17:31
amaretskiypong17:31
boris-42so we can support updating credentials of cloud by "rally deployment update" command17:31
yfriedboris-42: ?17:32
*** roeyc has quit IRC17:32
*** jprovazn has quit IRC17:32
yfriedboris-42: is this related to updating users for deployment, or is this a standalone topic?17:32
boris-42it's standalone topic17:32
boris-42would we provide the way to update information of deployment or not17:33
yfriedboris-42: what's the downside?17:33
*** e0ne has quit IRC17:33
*** Tango|2 has quit IRC17:33
meteorfoxboris-42: is this related to our previous discussion, updating predefined users for a deployment?17:33
boris-42the main contra-versional thing here  is that Rally can deploy OpenStack as well17:33
boris-42meteorfox: it is a bit17:33
meteorfoxok17:34
boris-42so if we will support this feature will it affect too much plugins that deploys openstack?17:34
yfriedboris-42: I'm not sure that I understand the issue17:35
yfriedboris-42: what changes if we update admin password (for example)?17:35
boris-42yfried: nothing more or less17:35
*** Sukhdev has quit IRC17:35
yfriedboris-42: so where are the effects?17:35
*** safchain has quit IRC17:36
*** psd has quit IRC17:36
boris-42hm17:36
*** leeantho has joined #openstack-meeting17:36
*** henrynash has joined #openstack-meeting17:37
*** rvasilets__ has quit IRC17:37
boris-42yfried: so actually yep17:37
*** sdake_ has joined #openstack-meeting17:37
boris-42yfried: if we allow just to change credentials then no issues17:38
boris-42yfried: okay let's make this happen17:38
*** mattgriffin has joined #openstack-meeting17:38
boris-42okay moving to next topics17:38
boris-42if there is no questions17:38
yfriedboris-42: if you have problematic attributes, make them readonly until you solve the problem17:38
*** jichen has quit IRC17:38
yfriedboris-42: lots of resources have readonly attributes17:38
*** rhe00 has quit IRC17:39
boris-42yfried: ya17:39
boris-42yfried: makes sense17:39
boris-42#topic Free discussion17:39
*** openstack changes topic to "Free discussion (Meeting topic: Rally)"17:39
boris-42you no need to pay to talk=)17:40
boris-42so ok17:40
*** esheffield has joined #openstack-meeting17:40
yfriedhttps://review.openstack.org/#/q/status:open+project:stackforge/rally+branch:master+topic:IPv6_Tests,n,z17:40
yfriedcan I?17:40
*** annegentle has joined #openstack-meeting17:41
*** doude has quit IRC17:41
*** sdake has quit IRC17:41
msdubovboris-42: You told yesterday that we should make some changes to our docs structure?17:42
boris-42yfried: ya sure17:42
boris-42msdubov: so yfried first=)17:42
yfried^ this topic introduces infra and scenario that tests IPv6 over v4 infra ("dual-stack")17:42
*** ayoung is now known as hopig17:43
*** baoli has joined #openstack-meeting17:43
*** hopig is now known as ayoung17:43
boris-42yfried: ok I will review them17:43
yfriedI think it's very nice addition to existing code17:43
boris-42when I find some free time to do that17:43
meteorfoxyfried: cool17:44
yfriedboris-42: point is, it helps to review it in the full context, instead of as independent patches17:44
yfriedboris-42: and the guy the wrote it is leaving our team and would like to have it merged before he can no longer work on it17:44
*** psd has joined #openstack-meeting17:45
boris-42yfried: oh ok17:45
boris-42yfried: I will try to review them more often17:45
yfriedboris-42: we need more eyes, as I am too close the this to find the real problems17:45
yfriedboris-42: tnx17:45
*** sreshetn2 has quit IRC17:46
yfriedboris-42: I'm available for questions if he's offline17:46
boris-42yfried: ok great thanks17:46
*** pritesh has joined #openstack-meeting17:46
boris-42yfried: anything else?)17:46
*** annegentle has quit IRC17:46
yfriedboris-42: nope17:47
boris-42okay let's move to refactoring docs17:47
boris-42#topic Refactoring docs17:47
*** openstack changes topic to "Refactoring docs (Meeting topic: Rally)"17:47
*** samueldmq has joined #openstack-meeting17:48
boris-42so they looks great17:48
boris-42but the code is in some kind of terrible state17:48
boris-42=)17:48
boris-42https://github.com/stackforge/rally/tree/master/doc/source to many files on top dir17:48
boris-42and it's hard to understand structure of it17:48
*** melwitt has joined #openstack-meeting17:48
*** sdake has joined #openstack-meeting17:48
*** neelashah has joined #openstack-meeting17:48
*** lennyb_ has quit IRC17:48
meteorfoxboris-42: do you have a structure in mind for it?17:49
*** VW_ has quit IRC17:49
boris-42meteorfox: nope I don't but we can look at other projects17:49
msdubovboris-42: So your wish is basically to change the structure of the code, not of the documentation contents?17:49
boris-42msdubov: I would like to change documentation as well17:50
boris-42at least to discuss future steps17:50
meteorfoxboris-42: how about if it mirrors the menu in rally.readthedocs.org17:50
meteorfox?17:50
*** pelix has quit IRC17:50
boris-42meteorfox: ya that will be nice17:50
boris-42meteorfox: I think it can be organized with symlinks17:51
boris-42like we have for future_request/specs and so on17:51
boris-42at least I woudl recomend to take a look at other projects17:51
boris-42https://github.com/openstack/nova/tree/master/doc/source17:52
boris-42meteorfox: msdubov ^ for example Nova17:52
boris-42they don't have hell in source dir17:52
*** sdake_ has quit IRC17:52
*** doude has joined #openstack-meeting17:52
yfriedboris-42: msdubov: re doc - can we get the "rally info" uploaded to docs as well?17:53
boris-42yfried: I would wait for switching to plugin base17:53
yfriedboris-42: well - is this actually a blocker for that?17:54
boris-42yfried: after that we can use custom extensions for read the docs to generate such page17:54
boris-42yfried: yep it is blocker17:54
yfriedboris-42: ok17:54
boris-42yfried: if you take a look at info code17:54
*** penick has joined #openstack-meeting17:54
boris-42yfried: it is terrible17:54
boris-42yfried: this will double amount of terrible cloud17:54
*** doude has quit IRC17:54
boris-42yfried: work with various plugins is not unfifed17:54
yfriedboris-42: because I'm trying to get ppl to look at rally but they have to install rally to browse its content17:54
boris-42wiich produce a lot of nasty code17:54
boris-42yfried: i understand why we need this but I dislike writting code that shoul be fully rewritten17:55
yfriedboris-42: I agree17:55
yfriedI'll wait for you17:55
boris-42yfried: it's better to concentrate on plugins17:55
boris-42anf after that simplify rally info code and make this page17:55
boris-42for docs17:56
*** eghobo has quit IRC17:56
boris-42so this is another interesting question17:56
boris-42actually what we need is to17:56
*** adalbas has quit IRC17:56
boris-42replace Rally Plugins -> Plugins Reference17:56
boris-42and add one more page API reference17:56
*** mtanino has quit IRC17:56
boris-42where we will have for now only CLI reference17:56
boris-42and in future rally lib reference17:56
boris-42msdubov: ^17:57
*** fzdarsky is now known as fzdarsky|afk17:57
*** rhe00_ has joined #openstack-meeting17:57
*** pritesh_ has joined #openstack-meeting17:58
*** david8hu has joined #openstack-meeting17:59
boris-42ok I hope msdubov agree with us=)17:59
boris-42but we are out of the time17:59
boris-42#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Mar 31 17:59:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-31-17.02.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-31-17.02.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-31-17.02.log.html17:59
* ayoung sneaks in and takes the good seat18:00
morganfainbergdolphm, ayoung, 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, samueldmq, htruta, amolock, wanghong, fmarco76, davechen, dims18:00
morganfainberghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Main_Agenda18:00
dstaneko/18:00
rodrigodso/18:00
*** oanufriev has quit IRC18:00
amakarovo/18:00
henrynashand happy DST to all18:00
bknudsonyo18:00
*** rhe00_ has left #openstack-meeting18:00
bknudsonbeen there for a while.18:00
henrynashyep, we’re late to the party as usual18:00
*** timcline_ has quit IRC18:01
*** pritesh has quit IRC18:01
lbragstado/18:01
stevemaro/18:01
raildo\o/18:01
ayoung    \m/(>.<)\m/18:01
samueldmqo/18:01
henrynash(ayoung should get out more)18:01
*** timcline has joined #openstack-meeting18:01
ayoung    \m/_  d(>.<)b _\m/18:01
*** ericksonsantos has joined #openstack-meeting18:01
rodrigodslol18:01
*** amaretskiy has left #openstack-meeting18:01
*** yolanda has joined #openstack-meeting18:01
*** xingchao_ has joined #openstack-meeting18:02
morganfainberg#startmeeting keystone18:02
openstackMeeting started Tue Mar 31 18:02:29 2015 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
*** yolanda has left #openstack-meeting18:02
*** sridhar_ram has quit IRC18:02
morganfainbergHello everyone!18:02
samueldmq:-)18:02
morganfainbergSo a couple quick things18:03
morganfainbergRc is next week. Please focus on bugs and bps that need review /code18:03
*** sridhar_ram has joined #openstack-meeting18:03
morganfainbergThe domain sql bp needs to be done by Thursday.18:03
morganfainbergThis Thursday.18:03
ayounglink henrynash ?18:03
*** jlibosva has quit IRC18:03
henrynashit’s  in the meeting agenda18:04
morganfainbergIt's later in the agenda specifically ayoung18:04
ayoungcool18:04
*** topol has quit IRC18:04
*** johnpur has joined #openstack-meeting18:04
henrynash#link https://review.openstack.org/#/c/163322/18:04
*** dflorea has quit IRC18:04
morganfainberg#topic Hierarchical Projects support on Horizon18:04
*** openstack changes topic to "Hierarchical Projects support on Horizon (Meeting topic: keystone)"18:04
morganfainbergsamueldmq: ericksonsantos o/18:04
samueldmqo/18:04
ericksonsantos:)18:04
samueldmqhello, so ...18:04
samueldmqericksonsantos and I have been working on adding support for hierarchical projects on Horizon18:04
bknudsonguis are fancy!18:04
*** dflorea has joined #openstack-meeting18:04
samueldmqwe then decided to add a point to this meeting to let you know what is going on18:05
ayoungThis is for Kilo?18:05
samueldmqfirst, a blog post explaining what was implemented18:05
*** prashantS has quit IRC18:05
*** baoli has quit IRC18:05
david-lylenot Kilo18:05
ayoungOk18:05
samueldmqayoung, unfortunately no18:05
*** jamielennox has joined #openstack-meeting18:05
samueldmq#link www.samueldmq.com/hierarchical-projects-on-horizon/18:05
*** yfried has left #openstack-meeting18:05
*** prashantS has joined #openstack-meeting18:05
samueldmqthere we explain the approach we took for this first implementation18:06
samueldmqin which basically we show projects with their hierarchical name18:06
samueldmqwhich is its own name + parents names, separated by slashes18:06
samueldmqe.g GrandParent / Parent / Child18:06
samueldmqand we have some screenshots :)18:06
bknudsonwhat if someone does hmt today, does horizon go crazy?18:06
ayoungnah, it just ignores what it doesn't know about.18:07
*** aranjan has quit IRC18:07
*** gabriel-bezerra has joined #openstack-meeting18:07
ayoungYou can;t create a nested project in Horizon today, right?18:07
bknudsonI like the \ for the separator, just like windows.18:07
samueldmqayoung, ++ no you cant18:07
*** xingchao_ has quit IRC18:07
samueldmqif you guys want to try it out ...18:07
*** jruano has joined #openstack-meeting18:07
samueldmq we have a demo running on 150.165.15.68, with Horizon credentials admin/nomoresecrete18:07
*** MarkAtwood has joined #openstack-meeting18:08
morganfainbergbest kind of feature. The kind that can be ignored if you don't want to use it ;)18:08
samueldmqwe will keep it open until Saturday, and then change the password18:08
*** pritesh has joined #openstack-meeting18:08
ayoungI assume you are working with UX type people to make sure that the choices you are making are sane?18:08
samueldmqand if someone still wants to have access, can ask myself or ericksonsantos18:08
*** adalbas has joined #openstack-meeting18:08
samueldmqayoung, yeah we already worked with some horizon guys, but this is a first implementation18:09
samueldmqayoung, which means it can be changed18:09
*** dflorea has quit IRC18:09
*** e0ne has joined #openstack-meeting18:09
samueldmqayoung, that's the reason we are requesting your feedback18:09
samueldmqso feel free to try it out and give some feedback :)18:09
morganfainbergs/can/will be (but because it'll evolve)18:09
samueldmqmorganfainberg, that's all I think18:09
samueldmqmorganfainberg, sure18:09
ayoungsamueldmq, we're Keystoners.  We are not UX people.  We make UGLY UI18:09
bknudsonneat18:09
*** prashantS has quit IRC18:10
samueldmqayoung, some ppl may have some ux background18:10
ayoungdavid-lyle, who from the Horizon side has provided input?18:10
samueldmqayoung, I'm a keystoner and was able to make it happen :)18:10
*** pritesh_ has quit IRC18:10
ayoungsamueldmq, my point exactly18:10
morganfainbergsamueldmq: don't advertise too loudly, you'll get roped in on more stuff. ;)18:10
ayoungI know better than to write UI18:10
*** esker has joined #openstack-meeting18:10
david-lyleI have and I think samueldmq is working with Piet18:10
*** esker has quit IRC18:10
morganfainbergIf you write good UI.18:10
samueldmqmorganfainberg, k :)18:11
david-lyleat least I hope18:11
samueldmqayoung, didnt intend to be annoying, sorry :)18:11
ayoungno, not at all18:11
samueldmqdavid-lyle, yes we are working with Piet's team18:11
david-lylePiet is cordinateing most of the UX work in horizon these days18:11
samueldmqdavid-lyle, ++18:11
* morganfainberg tosses samueldmq at david-lyle "he says he can do UI. I'm sure he can do UI design for horizon and all the keystone stuff he is doing today too!" /snark18:11
ayoungsamueldmq, and it is great you are doing this.  I just want to make sure you are getting feedback fromthe right folks18:11
morganfainberg;)18:11
samueldmqayoung, yeah getting feedback from ppl from UX (Piet's team, as david-lyle said)18:12
ayounggood18:12
samueldmqayoung, and yours as well, just to add18:12
*** MarkAtwood has quit IRC18:12
samueldmqmorganfainberg, not that much :p18:13
* morganfainberg can complain about ux, but can't design a UI to save a life (and that is the story I am sticking to...)18:13
samueldmqmorganfainberg, our implementation is simple and we worked hard (even if it was simple )18:13
ayoungOK...we have the link.  we'll beat on it.  Next?18:13
* morganfainberg hides graphic arts portfolio and previous UI design under the rug.18:13
morganfainbergYes next topic.18:13
samueldmqk thanks :)18:13
morganfainberg#topic Domain-SQL, final reviews18:14
*** openstack changes topic to "Domain-SQL, final reviews (Meeting topic: keystone)"18:14
morganfainberghenrynash: o/18:14
henrynashok, so this is the last (server) piece of domain-specific sql18:14
morganfainberghenrynash: I have feedback on fixing the race. But I'll step in after you speak18:14
henrynash#link https://review.openstack.org/#/c/163322/18:14
ayoungLDAP only makes sense to me.  Any need for SQL?18:14
henrynashayoung: ?18:14
*** kzaitsev has joined #openstack-meeting18:14
*** kzaitsev has quit IRC18:14
morganfainberghenrynash: a comment I made on the review.18:14
bknudsonI'm ok with documenting limitations for an experimental feature.18:14
*** banix has quit IRC18:15
*** aepifanov has joined #openstack-meeting18:15
ayounghenrynash, is there a demand for sql idenityt in a domain specific config?18:15
bknudsonneeds to be fixed to get rid of experimental.18:15
morganfainbergbknudson: ++ that might be the way to land it all in kilo vs the fix I am thinking.18:15
*** banix has joined #openstack-meeting18:15
henrynashmorganfainberg: yes, I saw that…although I think we have seen demand for the sql driver specification…ayoung, didn’t you see ause for this18:15
henrynashbknudson: agreed18:15
ayounghenrynash, wasn't me, but I can see it if I squint18:15
ayoungtwo caompnies want to keep their users in separeate databases for SOX or some other reason18:16
henrynashmorganfainberg: I’ll investigate18:16
ayoungbut, I thought LDAP was the primary driver.18:16
morganfainberghenrynash: until we support multiple sql pools/connections it is fair to say the main driver is sql vs a domain specific. But that's my view.18:16
*** Longgeek has quit IRC18:16
ayoungSo, talking practial, is there any real demand for sql, or are we just being thorough?18:16
morganfainbergAnd override any domain (even default) to use ldap if you want something like that.18:16
henrynashayoung: I thought we saw a use of haveing a specific domain (sql) for service users18:16
*** Longgeek has joined #openstack-meeting18:17
ayounghenrynash, that is different.  That would still be in the main identity backend18:17
henrynashayoung: it *could* be18:17
morganfainberghenrynash: I'm just saying we invert the use-case, override default domain to be ldap, all domains without a specific driver are sql.18:17
morganfainbergSo you don't even have to check if there are multiple sqls, just "you don't" do it at all.18:18
*** aepifanov has quit IRC18:18
henrynashmorganfainberg: I think we test that exact case in the unit tetss18:18
ayounghenrynash, I thought the expectation was  sql for the main one,  supporting multiple domains.  LDAP in domain specific backends,  to allow for live deployment of new LDAP servers in B2B cases18:18
*** e0ne is now known as e0ne_18:18
morganfainberghenrynash: we could just say sql isn't domain specific. *shrug* it would solve the sql driver check.18:19
ayoungmorganfainberg, I think that is a good approach, at least for Kilo.  If we do that, and it proves to limiting, we do more in Liberty18:19
henrynashok, so action is for me to confirm wheteher we can bypass the problem in this fashion18:19
bknudsonayoung: I think that is the expectation but it's not how it's implemented now.18:19
ayoungbknudson, yeah, that was my understanding18:19
morganfainberghenrynash: for the race: document it, *or* use optimistic locking.18:19
henrynashmorganfainberg: agreed18:20
bknudsonI'm fine with documenting it.18:20
morganfainberghenrynash: if optimistic locking is easy do that. Documentation is minimum for Thursday this week.18:20
bknudsonplease update the review with the known limitation18:20
henrynashmorganfainberg: ++18:20
morganfainbergWe can fix the locking in liberty if it is too much to do by Thursday.18:20
*** _nadya_ has quit IRC18:21
*** lhcheng has joined #openstack-meeting18:21
henrynashmorganfainberg: and when you say the race/locking…you mean the sql issue or teh get/update of configs not being atomic18:21
morganfainbergYep18:21
*** VW_ has joined #openstack-meeting18:21
morganfainbergYou make the workflow update where thing = what you have now18:21
morganfainbergAnd if that doesn't update any rows, you know the data has changed.18:22
morganfainbergIt's the same way we handle consuming trusts with limited uses.18:22
bknudsonthe code now updates every row in a separate transaction18:22
bknudsonI think?18:22
henrynashsorry, for clarity which issue are you referring to….teh get/update issue?18:23
henrynashbknudosn: yes18:23
morganfainbergYes the get/update18:23
bknudsoneach config option is a row18:23
henrynashmorganfainberg: yes, I look at what we did for trusts etc.18:23
*** e0ne_ has quit IRC18:23
henrynashmorganfainger: ok, thx18:23
henrynashok, I think I got what I need to do by Thursday18:23
ayounghenrynash, shout if you need help18:24
henrynashayoung: thx18:24
morganfainberghenrynash: don't worry too much about get/update by thurs. Like I said liberty we can work on that.18:24
morganfainberg#Topic rc bugs18:25
*** openstack changes topic to "rc bugs (Meeting topic: keystone)"18:25
henrynashmorganfainberg: agreed…and I’ll buy a coconut to to any customer taht finds that in Kilo anyway18:25
morganfainbergPlease do not assign bugs to the rc milestone unless they are really a blocker for release. When in doubt, bug me.18:25
henrynashmorganfainberg: apologies, guilty…but couldn’t work out how to use teh rc.potential tag?18:26
bknudsonare there any blockers?18:26
morganfainbergAt this point unless it is a show stopper we aren't adding it to the rc list.18:26
morganfainberghenrynash: lp was being dumb I couldn't set it either.18:26
morganfainbergbknudson: the critical security one, the high prio ones. The others should all be in progress and easy-ish to land.18:26
morganfainbergbknudson: there is also an index on a sql table that should land if at all possible.18:27
ayoungDo we have a link/query for RC bugs18:27
lbragstadhttps://launchpad.net/keystone/+milestone/kilo-rc118:27
lbragstad#link https://launchpad.net/keystone/+milestone/kilo-rc118:27
*** msdubov has quit IRC18:28
bknudsonprobably shouldn't be wishlist bugs on here...18:28
morganfainbergOh the trustor disabled =403 not 404. That is  not api breaking to fix. And should be fixed.18:28
dstanekbknudson: maybe someone really, really wants it18:28
bknudsonif you wish hard enough...18:28
morganfainberghenrynash: hey that bug got back on the milestone! :P18:29
henrynashwhich one?18:29
*** mpaolino has quit IRC18:29
*** dflorea has joined #openstack-meeting18:29
morganfainbergOr lp is dumb18:29
morganfainbergThe wish list one.18:29
bknudsonseems like release-blocking should be limited to something that is really critical or can't be backported.18:29
henrynashI never touched it, guv18:29
morganfainbergbknudson: wish list removed. The other bugs are like I said in progress and should land for "ux/this would suck but if it doesn't land by Friday I'm ok punting them"18:30
morganfainbergExcept the high prio ones.18:30
ayoungmorganfainberg, I'll take https://bugs.launchpad.net/keystone/+bug/1430951  which was triaged but unassigned18:31
openstackLaunchpad bug 1430951 in Keystone "Revocation causes duplicate (and overly broad?) events in revocation table" [High,Triaged] - Assigned to Adam Young (ayoung)18:31
henrynashis there a kilo-rc-potential tag?18:31
morganfainbergayoung: thanks.18:31
*** chandankumar has quit IRC18:31
morganfainberghenrynash: there is. Just tag the bug. But to be fair I don't want to add more to that list.18:31
lbragstadI think there are only a couple that don't have patches proposed for review18:31
morganfainbergUnless it is really a show-stopper.18:31
bknudsonI think there's already a review for https://bugs.launchpad.net/keystone/+bug/143095118:31
stevemarbknudson, link it in the bug?18:32
bknudsoncan't find it now.18:32
morganfainbergOk let's move on, I have one more item and we can be done early ;)18:33
bknudsonfound it? https://review.openstack.org/#/c/141854/18:33
ayoungI'll make sure it is covered, either by existing review or new code18:33
*** dkranz has quit IRC18:33
bknudsonoh, that was similar but not the same.18:33
*** garyh has quit IRC18:33
ayoungNope, that is a different issue18:33
ayoungI think I actually like his approach there18:33
*** dflorea has quit IRC18:33
stevemarsimilar18:33
morganfainberg#topic Summit planning18:34
*** openstack changes topic to "Summit planning (Meeting topic: keystone)"18:34
lbragstadwhoop whoop!18:34
stevemarohhh summit planning... neat18:34
*** dflorea has joined #openstack-meeting18:34
lbragstadget ready Canada18:34
ayoungSo, instead of hanging out at the Hotel bar buying expensive scotch, we each pick up a bottle and share.18:34
ayoungThat's really all I've got.18:34
*** prashantS has joined #openstack-meeting18:34
morganfainberg#link https://etherpad.openstack.org/p/Keystone-liberty-summit-brainstorm18:35
lbragstadayoung: are we getting Chocolate stout shakes?18:35
morganfainbergI will send the link via the ml as well.18:35
ayoungI really didn't care too much for them18:35
morganfainbergFeel free to toss ideas there.18:35
ayoungSo...let's come up with something else.18:35
morganfainbergI don't have the specifics on how many slots fishbowl or otherwise we will get.18:35
morganfainbergIn general I want this summit to be more like what our mid cycle has been.18:35
morganfainbergSo, unless the next PTL changes that idea (if I'm not ptl next cycle) let's roll with that plan.18:36
*** e0ne has joined #openstack-meeting18:36
morganfainbergGet specs hashed out, etc.18:36
ayoungmorganfainberg, you keep hoping....18:37
*** eharney has quit IRC18:37
*** anish_ has quit IRC18:37
morganfainbergI also would like to see next cycle a stability / performance cycle with very low numbers of features. (Again subject to change with potential alternative PTL)18:37
morganfainbergOk that's all I have18:37
morganfainberg#topic open discussion18:37
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:37
morganfainbergAny thing else?18:37
*** dane_leblanc has quit IRC18:38
jamielennoxi have a small one, henrynash -1ed me on https://review.openstack.org/#/c/162525/ because we don't do it in keystone18:38
jamielennoxis there a reason we don't, or just because i haven't written it yet18:38
lbragstadmorganfainberg: when do you want to have ideas hashed out based on the etherpad?18:38
henrynashquilty as charged, mlud18:38
*** dflorea has quit IRC18:38
*** dflorea has joined #openstack-meeting18:38
*** psd has left #openstack-meeting18:38
henrynashmy -1 was about whether our test apis are part of out api documentation18:39
bknudsonthe client libs are different than keystone server wrt docs, so I don't think they both need to be the same.18:39
morganfainberglbragstad: start now. We will circle up on it all on subsequent meetings and elsewhere.18:39
lbragstadmorganfainberg: ok, cool. Then group into buckets accordingly?18:39
jamielennoxbknudson: there's also no reason to do it in server docs either18:39
morganfainberglbragstad: it'll be open till we have a schedule. ;). Yep18:39
bknudsondoes keystoneclient provide fixtures?18:39
jamielennoxhenrynash: IMO tests are not public api, we can change, rename at will18:39
henrynashbknudson: agreed they are different, but not sure why we would make it different in this particular case18:39
jamielennoxbknudson: yes, but they are in the public area, not the tests dir18:40
*** leonchio_ has joined #openstack-meeting18:40
bknudsonI'm fine with skipping the tests in docs.18:41
morganfainbergThe official line is tests are public in that they exist. But nothing guaranteed beyond that.18:41
morganfainbergSo yeah we could skip the docs.18:41
jamielennoxwe just renamed ksc/tests/* ksc/tests/unit/* so there's no compat guarantee18:41
bknudsonwe don't keep them up to date anyways.18:41
morganfainbergjamielennox: no tests do not have a compat guarantee.18:41
henrynashjamielennox: ok, I’ll remove my -1 and I’ll submita patch for the server to remove the tests from teh api docs as well18:42
jamielennoxhenrynash: cheers18:42
henrynashgood to have raised18:42
*** afazekas has quit IRC18:43
jamielennoxactually on that dstanek did you ever figure out moving the apidoc ext to oslo - or what the pbr issue was that needs it in each repo?18:43
*** prashantS has quit IRC18:43
jamielennoxi see notes all through there about various bugs and they mostly seem fixe18:43
jamielennoxd18:43
dstanekjamielennox: for my two api doc reviews?18:43
bknudsonI tried to turn on warnings are errors in oslo.config and ran into that apidoc issue.18:43
*** prashantS has joined #openstack-meeting18:43
bknudsonthere was a thread on the mailing list recently about pbr release.18:44
dstanekmy understanding is that the issue isn't fixed yet in the released pbr; my changed was merged, but because of other brokeness they have been releasing pbr from a branch18:44
jamielennoxfor example https://github.com/openstack/keystone/blob/master/doc/ext/apidoc.py#L1518:44
bknudsonhttps://bugs.launchpad.net/pbr/+bug/1260495 -- we need fix released.18:45
openstackLaunchpad bug 1260495 in python-keystoneclient "Setting autodoc_tree_index_modules makes documentation builds fail" [Low,Confirmed] - Assigned to David Stanek (dstanek)18:45
jamielennoxah ok, i guess i just saw the age and assumed it would be out, i only poked around it briefly and then just c&p the extension18:46
dstanekyeah, maybe i'll look at pbr and see if i can help fix the issues they are having18:46
jamielennoxbut it's now in most repos i set up18:46
*** dkranz has joined #openstack-meeting18:46
morganfainbergAnything else? Before we call it a bit early?18:47
morganfainberg3...18:47
dstanekjamielennox: the fix i did? in what repos?18:48
jamielennoxdstanek: i copy the doc/ext/apidoc.py file to other repos18:48
jamielennoxrecently ksc-kerberos doa-kerberos and something else i can't remember18:48
dstanekjamielennox: ah, that can be deleted after pbr is fixed18:48
jamielennoxyep18:48
jamielennoxdidn't know about there release issues18:48
dstanekwe were the only project effected by the fix since we were the only ones using the feature18:49
ayoungjamielennox, do I need an updated client to test the last DOA Federation code?18:49
*** achanda has quit IRC18:49
jamielennoxayoung: no i don't think so18:49
stevemarshouldn't18:49
ayoungOK18:50
morganfainbergLet's move these18:50
morganfainbergConvos to -keystone18:50
stevemark18:50
morganfainbergThey aren't needed for the whole team.18:50
morganfainbergthanks all! Rc next week! Review code!18:50
morganfainberg#endmeeting18:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:50
openstackMeeting ended Tue Mar 31 18:50:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:50
samueldmqyep, thanks18:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-31-18.02.html18:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-31-18.02.txt18:50
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-31-18.02.log.html18:50
*** padkrish has joined #openstack-meeting18:51
*** Rockyg has joined #openstack-meeting18:51
*** jamielennox has left #openstack-meeting18:51
*** dkranz has quit IRC18:51
*** annegentle has joined #openstack-meeting18:52
*** dhritishikhar_ has quit IRC18:52
*** fbo has quit IRC18:52
*** shwetaap1 has quit IRC18:52
*** stevemar has quit IRC18:54
*** TheJulia has joined #openstack-meeting18:54
*** isviridov has joined #openstack-meeting18:54
*** jruano has quit IRC18:54
*** henrynash has quit IRC18:55
*** sreshetn2 has joined #openstack-meeting18:56
*** GheRivero has joined #openstack-meeting18:56
tchaypoInfra time!18:57
*** ianw has joined #openstack-meeting18:58
*** yolanda has joined #openstack-meeting18:58
*** amakarov is now known as amakarov_away18:58
*** novas0x2a|laptop has joined #openstack-meeting18:59
cineramahi folks18:59
clarkbhello18:59
*** lhcheng has left #openstack-meeting18:59
samueldmqhi18:59
*** pcrews has joined #openstack-meeting19:00
anteayao/19:00
*** rdopiera has joined #openstack-meeting19:00
*** dflorea has quit IRC19:00
jeblairhowdy infra folks19:00
rdopierahi19:00
TheJuliao/19:00
nibalizero/19:00
yolandao/19:00
mordredo/19:00
fungihowdy19:00
jeblair#startmeeting infra19:00
openstackMeeting started Tue Mar 31 19:00:43 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** jlanoux has quit IRC19:00
*** primemin1sterp is now known as primeministerp19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
pcrewso/19:00
openstackThe meeting name has been set to 'infra'19:00
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:00
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-24-19.00.html19:00
jeblair#topic Actions from last meeting19:00
ianwo/19:00
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:00
*** dflorea has joined #openstack-meeting19:00
jeblairanteaya cause a problem statement and requirements regarding election tooling to be sent to the infra list so various solutions can be discussed19:00
jeblair#link https://etherpad.openstack.org/p/XU4qRouXIH19:00
jeblairanteaya: thanks for that19:01
GheRiveroo/19:01
anteayawelcome19:01
tristanCHello!19:01
*** greghaynes has joined #openstack-meeting19:01
zaroo/19:01
krtayloro/19:01
*** Sukhdev has joined #openstack-meeting19:01
jeblairanteaya: i think you are expecting some input on that.  and i think i promised to give you some.19:01
anteayaso unless we have some more edtis to that or any objections I'll send that out this afternoon19:01
anteayajeblair: you mentioned it yes19:01
jeblairso i should do that before then, then.  :)19:01
anteayajeblair: thanks, that would be most welcome, thank you19:01
anteayaand tristanC not sure if you have had a chance to review the etherpad yet19:02
anteayatristanC: let me know what you think19:02
jeblairand anyone else, pitch in soon.  i think the point was to try to make the requirements clear so we can effectively propose and evaluate solutions19:02
anteayayes19:02
*** padkrish has quit IRC19:02
jeblairclarkb make sure bandersnatch is being updated19:02
jeblair#link https://review.openstack.org/#/c/167382/19:02
clarkbanteaya: don't forget to clean up my comment about self editing19:03
anteayaclarkb: will do19:03
*** Shrews has joined #openstack-meeting19:03
*** padkrish has joined #openstack-meeting19:03
jeblairclarkb: did a thing^ yay! :)19:03
jeblairi think that's self-explanator19:03
jeblairy19:03
clarkbI did, it just needs another +2 then either I can approve or someone else19:03
*** jruano has joined #openstack-meeting19:03
jeblairfungi send announcement email for renames19:03
jeblair#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/059948.html19:03
fungihappened19:03
jeblairfungi did that and more!19:03
fungiand how19:03
jeblairjeblair document openstack id deployment mechanism in http://ci.openstack.org/openstackid.html19:04
jeblair#action jeblair document openstack id deployment mechanism in http://ci.openstack.org/openstackid.html19:04
jeblairjeblair did not do that thing19:04
jeblair:(19:04
asselin_o/19:04
anteayathat is okay, we have this week19:04
*** fbo has joined #openstack-meeting19:04
jeblair#topic Schedule next project renames19:04
*** openstack changes topic to "Schedule next project renames (Meeting topic: infra)"19:04
*** dkranz has joined #openstack-meeting19:04
*** stevemar has joined #openstack-meeting19:04
jeblairso there's murano; no further communication on that change19:04
jeblairare any murano people around?19:04
fungiif someone comes up with a bit more time to test the utf8 conversion, we could consider doing it along with the murano move19:04
mordred++19:05
*** dflorea has quit IRC19:05
*** peristeri has joined #openstack-meeting19:05
*** bswartz has joined #openstack-meeting19:05
jeblairzaro: are you still working on that?19:05
clarkbalso did we get the xstatic package rename correct and the fallout yesterday was unrelated to the new name?19:05
fungiserg_mel seems to not be in here19:05
*** Sukhdev has quit IRC19:05
jeblairclarkb: we got it correct.  someone deleted the old name from pypi.19:05
clarkbaiui that is the case but may be worth following up on to make sure that doesn't need more changes19:05
zarojeblair: sorry i dropped the ball on that.  will do it this week.19:05
clarkbjeblair: gotcha19:05
jeblairzaro: np19:05
jeblairokay, we'll wait for the murano folks to re-engage19:06
anteayaclarkb: as fungi explained to me we have no control over someone deleting a package from pypi that is in global requirements19:06
*** neelashah has quit IRC19:06
fungiother than to ask them to please put it back19:06
clarkbanteaya: yup I was worried that we didn't get the rename correct19:06
jeblairi don't think anyone knows what's going on with gantt yet.19:06
fungior to stop depending on it19:06
*** tiswanso has quit IRC19:07
jeblairi don't actually know the motivation for the gantt discussion?19:07
anteayaclarkb: yup19:07
*** xingchao_ has joined #openstack-meeting19:07
jeblairis it just cleaning up the openstack namespace?19:07
*** adalbas has quit IRC19:07
fungiyes19:07
*** padkrish has quit IRC19:07
anteayajeblair: yes it appears to be19:07
anteayaandereas likes things in order19:07
jeblairif so, i'd prefer to just let it sit until someone decides to either do something with it or that nothing will ever be done with it19:07
bauzashey19:07
mordredjeblair: ++19:07
bauzas\o19:07
fungi"it's a seemingly abandoned effort in an ostensibly official repo namespace" seems to be the entirety of the concern19:07
jeblairit seems like folks are saying 'this might still happen in the future'19:07
anteayajeblair: I agree19:08
* mordred has submitted a patch to gantt to delete all the files19:08
mordredfwiw19:08
bauzasmordred: and I +2'd it19:08
mordredbauzas: woot!19:08
*** stevemar has quit IRC19:08
jeblairmordred: that should provide more data :)19:08
anteayathere is a thread on the mailing list about what to call the effort so they can't yet agree on naming19:08
mordredoh - it failed the docs job19:08
bauzasso yeah, agreed on the plan to clean up the repo19:08
*** stevemar has joined #openstack-meeting19:08
*** sridhar_ram1 has joined #openstack-meeting19:08
bauzasmordred: saw that, probably needs a recheck19:09
*** sridhar_ram has quit IRC19:09
jeblairbauzas: are you okay leaving it there for now until there's a plan to move forward?19:09
fungianteaya: well, i think that's more around avoiding using the gantt name to refer to other activities related to scheduler decomposition19:09
bauzasjeblair: I like mordred's idea to clean up19:09
bauzasjeblair: and keep it as it is19:09
anteayafungi: okay well in any case, there is lack of agreement19:09
jeblairok.19:09
bauzasfungi: I sent an email about that19:09
fungiyep, i read it19:09
* fungi probably spends too much time trying to read a lot of what crosses the -dev ml19:10
bauzashttp://lists.openstack.org/pipermail/openstack-dev/2015-March/060179.html19:10
jeblair#agreed merge mordred's change to delete all content from gantt repo, but otherwise, leave as-is until there is a more substantive plan to move forward with the effort or it is truly abandoned19:10
jeblairanyone disagree with that ^ ?19:10
* fungi agrees19:10
* anteaya has no problem with that19:10
clarkbsounds like a plan to me19:10
jesusauruso/19:10
bauzasI also have to check with the Foundation about the legals for the codename19:10
bauzas+119:10
jeblair(i can undo it if we do, fwiw)19:10
jeblaircool, sounds like we're okay then, and there are no pending project renames19:11
jeblairbauzas: thanks! :)19:11
*** salv-orl_ has joined #openstack-meeting19:11
*** padkrish has joined #openstack-meeting19:11
jeblair#topic Priority Efforts (Swift logs)19:11
jeblair#link https://review.openstack.org/#/q/status:open+topic:enable_swift,n,z19:11
*** openstack changes topic to "Priority Efforts (Swift logs) (Meeting topic: infra)"19:11
*** garyh has joined #openstack-meeting19:11
jeblairlooks like the footer changes are still outstanding and could use a review19:12
clarkbjeblair: we are waiting on your response to jhesketh at https://review.openstack.org/#/c/167158/219:12
clarkbjeblair: I think the footer changes all have the necessary +2s though19:12
jeblairi think jhesketh is back from leave so we can progress there19:12
jeblaircool, will review19:12
jeblair#topic Priority Efforts (Nodepool DIB)19:12
jeblair#link https://review.openstack.org/#/q/status:open+topic:dib-nodepool,n,z19:12
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:13
*** xingchao_ has quit IRC19:13
jeblairmordred: have your etherpad link handy?19:13
mordredyeah - one sec19:13
jeblair#link https://etherpad.openstack.org/p/dib-nodepool-merges19:13
jeblairfound it19:13
mordredhttps://etherpad.openstack.org/p/dib-nodepool-merges19:13
mordredoh19:13
*** salv-orlando has quit IRC19:13
mordredso - this is pretty darned near close19:13
mordredall of the pieces now exist, pending code review and bug finding19:13
jeblairand the etherpad provides some nice narrative structure so we can see how it will all fall in to place19:14
*** sreshetn2 has quit IRC19:14
*** vishwanathj has quit IRC19:14
mordredgiven the nature of the thing, it still make take a week or two to finish landing, as some of these changes we'll want to watch19:14
mordredand as clarkb has pointed out, we'll need to test that devstack runs properly on the -minimal based images19:14
*** rushiagr is now known as rushiagr_away19:14
mordredbut I think we'd have to do that if we modifed the cloud images to remove cloud-init as well, because $unknown_knockon_effects19:15
mordredbut we're quite close19:15
jeblairmordred: i reviewed all the infra changes in there yesterday, i can probably do another pass to catch updates today or tomorrow19:15
mordredjeblair: I've rebased a few things since then19:15
clarkbI am trying to review the related changes and get my nodepool changes for multiple image types up to par19:16
mordredclarkb: we shoudl add that change to the etherpad19:16
*** padkrish_ has joined #openstack-meeting19:16
jeblairi think it's there19:16
mordredif we haven't already19:16
mordredcool19:16
*** balajiiyer has quit IRC19:17
clarkbyup I added it19:17
jeblairanything else to talk about here?19:17
yolandaso it will be affecting in some way to that: https://etherpad.openstack.org/p/Nodepool_benchmarks . Shall i add this to that etherpad as well?19:17
fungiworking through comparing the results of 164447 on various devstack-.* sample nodes from our providers and comparing the result to the equivalent bare-.* samples19:17
fungioh, we were going to briefly bikeshed on new-world-order platform identifiers19:17
mordredoh yeah19:17
mordredI'd like to suggestion we name our things $distro-$release once there is no bare/trusty distinction19:18
clarkbwe could do ubuntu14.04-timestamp and centos7-timestamp19:18
jeblairyolanda: i think they are separate efforts19:18
mordredclarkb: I'd say trusty not 14.0419:18
fungisince we don't have an equivalent devstack-centos6 worker to move bare-centos6 jobs onto, i need to make something. best not to call it "devstack-centos6" since we won't likely run devstack on it19:18
*** padkrish has quit IRC19:18
mordredbasically, I don't thin kwe should have things named centos6 and centos7 if we don't also have ubuntutrusty19:19
mordredit's a small bikeshed19:19
*** jichen has joined #openstack-meeting19:19
fungiand because i patterned dib's release/version support on the idea i could match it to our node labels, i'll want to tweak that too if we want to use something different than we do now19:19
*** aimon has quit IRC19:19
mordredand then I think because ubuntutrusty looks weird, we should add a -19:19
fungier, s/dib/bindep/19:19
mordredso centos-7, centos-6, ubuntu-trusty, fedora-2119:19
fungithough dib also has something similar apparently. so converging our identifier format would be good, i think19:19
jeblairwhat's the dib thing that is similar?19:20
greghaynesthat maps to DIB's $DISTRO_NAME-$DIB_RELEASE,19:20
fungianyway, if there are no objections to mordred's proposal, i'll go with centos-6 as the new node label19:20
greghaynesthe list mordred wrote maps to that19:20
* anteaya doesn't object19:20
jeblairgreghaynes: does that match what mordred is sugg...19:20
jeblaircool :)19:20
jeblairclarkb: okay with $distro-$release?19:21
mordredok - now what color trusty do we want?19:21
clarkbjeblair: sure19:21
greghaynestheres a caveat with centos7 actually, but thats a dib bug19:21
clarkbI only suggested numbers for consistency ut I don't care19:21
mordredgreghaynes: and it's fine with the centos-minimal element :)19:21
fungiwith the expectation that we'll do ubuntu-something as well (i don't care if we mix release codenames and version numbers personally)19:21
clarkbits all going to get grepped and sed'd the same either way19:21
jeblairmordred: numbers or names?19:21
mordredI think trusty is the common form for ubuntu, and 7 is the common for centos19:21
mordredso I think we shoudl use those19:21
mordredif we have debian images, I think we shoudl use names too19:22
jeblairmordred: and numbers for fedora?19:22
mordredbecause I _CERTAINLY_ have no idea what number jessieis19:22
*** otter768 has joined #openstack-meeting19:22
fungiyeah, it's more that centos just doesn't have good release names19:22
jeblaircause fedora does have names19:22
mordredjeblair: yes19:22
mordredI don't hear people use them as much - but I could be very wrong about that19:22
greghaynesDIB is all name based fwiw19:22
*** sarob has joined #openstack-meeting19:22
fungigreghaynes: what does dib call centos 6 and 7?19:22
greghayneser, no19:22
jeblairgreghaynes: so it uses fedora-beefy-miracle?19:23
mordredso ... fedora uses numbesr for fedora-minimal19:23
* fungi loves that name19:23
greghaynesthats wrong, yea ;) its name based for ubuntu, number for everything else19:23
mordredyou have to pass in 21 to $DIB_RELEASE19:23
mordredotherwise the chroot building will not work19:23
greghaynesbut we can incorporate beefy-miracle19:23
mordredit really has to do with mirror paths19:23
fungiso maybe "gravitate toward current dib behavior, whatever that is" is what we're suggesting?19:23
mordredwe cannot, sadly, use beefy-miracle19:23
jeblair#agreed use $distro-$release (eg 'ubuntu-trusty', and 'fedora-21') for image names, matching usage in dib where possible19:23
jeblairlook good ^ ?19:24
mordredjeblair: ++19:24
ianwwe don't use the names for fedora, but then they use things like "Schrödinger" which introduces other types of fun19:24
greghaynesjeblair: ++19:24
fungigreat! thanks for suffering through the bikeshed19:24
mordredfungi: should we paint our trusty purple?19:24
jeblair#topic Priority Efforts (Migration to Zanata)19:24
jeblair#link https://review.openstack.org/#/q/status:open+topic:zanata,n,z19:24
*** adalbas has joined #openstack-meeting19:24
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:24
cineramaoh hi there19:25
jeblairare the changes ready for widespread review now?19:25
*** thinrichs has joined #openstack-meeting19:25
clarkbI have reviewed a few of them and I would say they are ready19:25
cineramajeblair: so we landed the base change. i think we can start reviewing and landing what i've got up on the board now19:25
cineramai've also reviewed stevenk's fine work on the client19:25
clarkbcinerama: oh that merged, awesome19:25
cineramaand now i'm doing some testing with that to see what we'll need to add to it.19:26
*** pritesh_ has joined #openstack-meeting19:26
jeblaircool; should we, oh, spin up a server?19:26
cineramajeblair: bit nervous there19:26
*** otter768 has quit IRC19:26
cineramajeblair: but i think we're close. i'd like to test a couple more things here19:27
jeblaircinerama: cool, no prob19:27
*** achanda has joined #openstack-meeting19:27
cineramamaybe before EOW or early next week tho19:27
anteayacinerama: if you say yes now it will probably take that long anyway19:27
cineramaanteaya: hey that's a good point19:27
jeblairalso we should see if pleia2 wants to do most of the work there19:28
anteayanever turn down teh offer of a server19:28
cineramaanteaya (& others) this is my first rodeo so any advice is really helpful19:28
fungii'm happy to volunteer to try and boot a server running that when you're satisfied that it's time19:28
anteayacinerama: it is dev only anyway19:28
anteayanot much can go wrong19:28
fungiand feed you details on whatever puppet errors end up preventing it, if any19:28
jeblairfungi: (psst, volunteer to backup pleia2 booting a server so she can gain xp)19:29
cineramajeblair: yeah i was thinking for pairing & stuff waiting for pleia2 before we set up might be good19:29
fungior help pleia2 through it, yes! i missed that comment above ;)19:29
*** pritesh has quit IRC19:29
*** Sukhdev has joined #openstack-meeting19:29
jeblairshe's out for a bit, right?  will she be back next week?19:30
* fungi didn't pay close attention to when she said she was getting back19:30
anteayayes next week19:30
jeblairso that will probably work with cinerama's timetable anyway19:30
anteayaand she has been wanting a server for some time19:31
cineramathat sounds good19:31
anteayafwiw19:31
*** dflorea has joined #openstack-meeting19:31
*** sdake_ has joined #openstack-meeting19:31
jeblairanything else?19:31
jeblair#topic Priority Efforts (Downstream Puppet)19:31
jeblair#link https://review.openstack.org/#/q/status:open+topic:downstream-puppet,n,z19:31
*** openstack changes topic to "Priority Efforts (Downstream Puppet) (Meeting topic: infra)"19:31
yolandafrom my side, i couldn't progress so much there but there are some changes with pending reviews, and some others i answered the reviews19:32
asselin_I have log server puppet scripts refactored and waiting on reviews19:32
nibalizernothing from me19:32
yolandaeverything with topic downstream-puppet from my side19:32
anteayaasselin_: I said I would review and didn't sorry about that19:32
jeblaircool, plenty of stuff to review this week :)19:33
*** SumitNaiksatam has quit IRC19:33
jeblair#topic Priority Efforts (Askbot migration)19:33
jeblair#link https://review.openstack.org/#/q/status:open+topic:askbot-site,n,z19:33
*** openstack changes topic to "Priority Efforts (Askbot migration) (Meeting topic: infra)"19:33
mordredyay reviewing19:33
jeblairthe pgsql module should be accepted into governance today and we can create that19:33
jeblairi think that's the big thing here, right?  anything else?19:34
fungioh, right, mrmartin is unavailable today19:34
*** sdake__ has joined #openstack-meeting19:35
fungiyeah, once we get that created, we can move forward safely19:35
*** sdake has quit IRC19:35
fungiwe could in theory move forward without it and add it later19:35
clarkbthe solr stuff got in right? so indexing is working19:35
fungireed sent an e-mail to the -community ml about scheduling the cut-over19:35
* fungi finds a link19:35
reedfungi, thanks19:36
*** sahid has quit IRC19:36
*** reed has quit IRC19:36
fungi#link http://lists.openstack.org/pipermail/community/2015-March/001102.html19:36
jeblairdid reed just drop off?19:36
fungiseems so19:36
jeblairbad timing :(19:36
*** reed has joined #openstack-meeting19:36
*** Sukhdev has quit IRC19:36
*** fawadkhaliq has quit IRC19:37
mordredmaybe san francisco got hit by an comet19:37
anteayaapril 6 is easter monday19:37
*** Sukhdev has joined #openstack-meeting19:37
fungianyway, the migration steps in the spec are confirmed working from my initial test, so the maintenance should be brief19:37
*** dflorea has quit IRC19:37
*** shwetaap has joined #openstack-meeting19:37
fungii loosely timed all the steps and should be able to finish within half an hour19:37
jeblairis that date set?19:38
anteayafungi: how many people to do the work, just one or a group?19:38
*** sdake_ has quit IRC19:38
fungianteaya: i can do the maintenance steps since i've already done them once19:38
*** neelashah has joined #openstack-meeting19:38
clarkbfungi: when you set up the dev instance?19:38
fungijust one person, plus some people to do usage tests to make sure it's still doing what it is supposed to19:38
jeblairi expect i'll be around then to pitch in if needed19:39
jeblairmonday is an interesting choice though19:39
anteayafungi: so I guess it is up to you, when do you want to do it?19:39
*** dflorea has joined #openstack-meeting19:39
fungiclarkb: it's not a dev instance, it's the new server, we just haven't switched dns over pending a second database dump19:39
clarkbfungi: gotcha19:39
*** Rockyg has quit IRC19:39
clarkbMy only monday restriction is I have to afk about 6pm PDT19:39
anteayaI see 2 choices on the linked email19:39
clarkbwhich should be fine19:39
fungiyeah, reed what was the motivation for monday? because a lot of people won't be trying to use it on a common international holiday?19:40
jeblairif those are the choices, i think we should go with monday so that we can land the puppet changes beforehand19:41
fungii'm guessing it was more that he looked at browser analytics to find weekly low-points in traffic volume19:41
*** alexpilotti has joined #openstack-meeting19:41
anteayaI can be around to help test19:41
anteayaso monday?19:41
*** mscohen has joined #openstack-meeting19:42
fungiwfm19:42
jeblair#info ask.o.o migration probably happening on Monday April 6th, 10am PDT19:42
jeblair:)19:42
jeblair#topic Puppet Testing19:42
jeblair#link https://review.openstack.org/#/c/164908/19:42
*** openstack changes topic to "Puppet Testing (Meeting topic: infra)"19:42
fungii'll follow up to the ml thread19:42
jeblairoops19:42
jeblair#topic Priority Efforts (Upgrading Gerrit)19:42
jeblair#link https://review.openstack.org/#/q/status:open+topic:gerrit-upgrade,n,z19:42
*** openstack changes topic to "Priority Efforts (Upgrading Gerrit) (Meeting topic: infra)"19:42
reedfungi, because monday is the first available day for me19:42
fungireed: oh, okay great!19:43
reedfridays are bad at doing complex things, if they fail the weekend is damaged :)19:43
jeblairso we're waiting on utf8 testing19:43
jeblairare we still targeting 2.9, or is it worth looking at 2.10 yet?19:43
*** sreshetn2 has joined #openstack-meeting19:43
jeblairi believe we have > 1 month, so even that should be doable19:43
anteayazaro: are you about?19:43
clarkb2.11 is already in rc19:44
zaroyes19:44
clarkbso it may be good to 2.10 if nothing bad comes up in testing just to get us closer?19:44
anteayazaro: 2.10? thoughts?19:44
*** SumitNaiksatam has joined #openstack-meeting19:44
mordred2.10 may get us WIP plugin, yeah?19:44
zarono. it won't19:44
*** jruano has quit IRC19:44
zaroi'm fine with trying 2.1019:44
*** rkukura has joined #openstack-meeting19:45
jeblair#action zaro to continue utf8 testing19:45
*** padkrish_ has quit IRC19:45
jeblair#action zaro test gerrit 2.1019:45
jeblairzaro: what does wip plugin need?19:45
anteayazaro: I'd like close connection functionality whichever one we select19:46
zarouhmm, lots of stuff i think.19:46
*** vishwanathj has joined #openstack-meeting19:46
zaroREST endpoints don't seem to work19:46
jeblairwip plugin requires >=2.11 according to http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-02-10-19.01.html19:46
zarosome core stuff needs to get approved as well. still sitting in review19:46
zaroi took yesterday to test it more deeply and entered some issues in to the gerrit issue tracker.19:47
jeblairzaro: what's 'it' ^ ?19:47
*** Rockyg has joined #openstack-meeting19:47
zarohttps://code.google.com/p/gerrit/issues/list?can=2&q=WIP+plugin19:47
jeblairah, wip plugin19:47
jeblairzaro: anything else we should be working on?19:48
zaroone change would ike to merge soon is19:48
zarohttps://review.openstack.org/#/c/155448/19:49
*** jruano has joined #openstack-meeting19:49
*** prasadv has joined #openstack-meeting19:49
zarootherwise just reviews on gerrit-upgrade topic19:49
jeblairzaro: thanks!19:50
jeblair#topic Zuul layout split using (tristanC)19:50
jeblair#link https://review.openstack.org/#/c/152290/19:50
*** openstack changes topic to "Zuul layout split using (tristanC) (Meeting topic: infra)"19:50
jeblairtristanC: around?19:50
*** padkrish has joined #openstack-meeting19:50
tristanCyes!19:50
*** thingee has joined #openstack-meeting19:50
clarkbzaro: is that change in 2.10?19:50
*** matrohon has joined #openstack-meeting19:50
zarowhich one?19:50
jeblairtristanC: you have a change to implement that!  :)19:50
tristanCso well, the spec is up for review since sometime already...19:50
*** aepifanov has joined #openstack-meeting19:50
clarkbzaro: 15544819:50
zaroclarkb: ohh, not sure.  i can check19:50
jeblairtristanC: yeah the spec merged: http://specs.openstack.org/openstack-infra/infra-specs/specs/zuul_split.html19:50
*** annegentle has quit IRC19:51
jeblairtristanC: i want to try to let jhesketh's connection changes land soon19:51
tristanCand I experiment with a split of openstack current layout here: https://review.openstack.org/#/c/163243/19:51
jeblairtristanC: it's getting close and the rebases for that are becoming troublesome19:52
jeblairtristanC: would it be okay to defer merging this until after that merges?19:52
tristanCjeblair: it should be easy to refactor/rebase though, not sure about the design though... I put the code in the layoutvalidator and it could be somewhere more meaningfull19:52
jeblairtristanC: okay, i'll try to review it before then to give you some feedback while we wait19:53
tristanCjeblair: that would be awesome :)19:53
jeblair#topic Puppet Testing19:53
jeblair#link https://review.openstack.org/#/c/164908/19:53
*** openstack changes topic to "Puppet Testing (Meeting topic: infra)"19:53
*** Sukhdev has quit IRC19:54
jeblairso there's a proposed change that added some puppet rspec tests to one of our puppet modules19:54
jeblairand it struck some of us as being unecessary19:54
jeblairi wonder if we can articulate a policy on puppet testing19:54
anteayarspec is a whole ruby testing framework19:54
clarkbin particular about half of the tests essentially rewrite the module19:54
jeblairclarkb: indeed19:55
anteayawhich if you are doing a lot of ruby is worthwhile19:55
clarkbwhich to me is redundant and does not add much value19:55
anteayamy sense of the crowd is you will find rspec more effort that is is worth19:55
jeblairi'm much more interested in functional tests; the puppet apply tests are really useful i think19:55
jeblairand since we have nodes with sudo, i bet we can do more19:55
yolandai find that tests useful, but it's quite hard to find real problems there and discriminate from the others19:55
*** markmc has joined #openstack-meeting19:56
fungiyeah, "will this break" is more helpful to me than "is this right"19:56
jeblairyolanda: absolutely.  but problems do cause it to fail at least.  it's kept _so many_ things from breaking production19:56
jeblairso i wonder if we could functionally test each module on a node?19:57
yolandai know, i'd like if some efforts can be dedicated to cleanup the error logs there. Some are just warnings , or incorrect settings19:57
jeblairhave a simple manifest that uses the module and runs for real on a node?19:57
*** gokrokve_ has joined #openstack-meeting19:57
clarkbjeblair: we could probably ship a tiny site.pp/node def for each module and run that then do specific sanity cheks19:57
clarkbjeblair: ya that19:57
fungiyolanda: i fear that most of those errors are entirely because of running with --noop19:57
yolandajeblair, i'm doing sort of a thing with vagrant actually19:57
jeblairfungi: i think you may be right19:57
nibalizer++ to func tests19:57
tchaypoWhen I've looked at puppet-rspec before, my sense has always been that it's not worth the hassle - it's a whole nother language to learn and seems to largely result in you having to write your change twice in unrelated languages19:57
zaroclarkb: yes, https://review.openstack.org/#/c/155448/ is in gerrit stable-2.10  branch.19:58
clarkbjeblair: I like the idea, it should be simple and help us determine where the boundary between openstack_project and everything else is19:58
anteayatchaypo: yes, that is rspec19:58
clarkbjeblair: then test that interface19:58
tchaypoOther people I know have used them successfully but they spent a lot more time writing ruby/puppet than I did19:58
yolandaso the changes i write, are tested functionally on a node, we could do something like that but using nodepool19:58
jeblairso is there an existing pattern/framework for "run a simple manifest and do some checks"?  should we just write a manifest, and use something like envassert after it runs?19:58
anteayait is written for tdd19:58
mordredanteaya: I agree - it seems like more hassle than it's worth19:58
anteayamordred: for us, oh yes19:58
anteayawe don't tdd19:58
mordredfor us. yes19:58
nibalizermy concern is do we want to spend 60 nodes per change to anything19:58
mordredwell, not in that way19:58
tchaypoI get the feeling they're useful for people who spend a lot of time writing puppet but they raise the barrier for entry19:58
mordredtchaypo: ++19:59
clarkbnibalizer: just one19:59
jeblairnibalizer: we could do this just on the modules19:59
clarkbjeblair: right, we would test the interfaces modules expose individually19:59
fungiright, functional test, not integration test19:59
*** gokrokve_ has quit IRC19:59
clarkbinstead of the entire thing composed together19:59
jeblairnibalizer: so a puppet-httpd change would consume one node to run the single test to test the httpd module19:59
nibalizerya okay19:59
mordred++19:59
jeblairnibalizer: and we would not run these on the system-config repo19:59
*** gokrokve_ has joined #openstack-meeting19:59
nibalizerim super down for this19:59
jeblairreserving the puppet apply as the 'integration' test19:59
jeblairnibalizer: want to hack out a POC for one of the modules?20:00
nibalizeri took the gerrit module out the other day and it was rough using it standalone without prebuilt hiera20:00
nibalizerjeblair: yea its on my list20:00
nibalizerim thinking envassert20:00
nibalizeror beaker but :sigh:20:00
anteayaoh look at the time20:00
jeblaircool.  i'll leave the feedback on 164908 about not wanting rspec20:00
jeblairthanks everyone!20:00
jeblair#endmeeting20:00
nibalizerty ty20:00
*** BadCub has joined #openstack-meeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Mar 31 20:00:33 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-31-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-31-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-31-19.00.log.html20:00
*** rdopiera has left #openstack-meeting20:00
tchaypoDo we have cross project in an hour?20:00
*** yolanda has left #openstack-meeting20:00
*** gokrokve has quit IRC20:00
ttxtchaypo: yes20:00
fungitchaypo: yes20:00
jeblairttx: o/20:00
tchaypoI see items on the agenda20:00
ttxAnyone here for the TC meeting ?20:00
markmcclaino/20:00
tchaypoCool. See you then20:01
*** BadCub has left #openstack-meeting20:01
* mestery lurks20:01
sarobo/20:01
mordredo/20:01
*** hemanthravi has joined #openstack-meeting20:02
ttxrussellb, jgriffith, annegentle, mikal, devananda, vishy, jaypipes, sdague, dhellmann : around ?20:02
vishyo/20:02
sdagueo/20:02
russellbo/20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Mar 31 20:02:27 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
mikalHi20:02
*** ibiris is now known as ibiris_away20:02
mordredhi mikal20:02
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** pcrews has left #openstack-meeting20:02
ttx#topic Final rubberstamp on "Add library stable release procedures/policy"20:03
*** openstack changes topic to "Final rubberstamp on "Add library stable release procedures/policy" (Meeting topic: tc)"20:03
ttx#link https://review.openstack.org/#/c/155072/20:03
*** dflorea has quit IRC20:03
jaypipeso/20:03
ttxOK, I think it's time to approve it now, unless someone objects.20:03
ttxIt's short of one vote but there are no objections, and we had the same discussion last week20:03
ttxso I'll count that as "consensus"20:03
*** dflorea has joined #openstack-meeting20:03
mordreddo it20:03
*** j05h has quit IRC20:03
*** isviridov has quit IRC20:04
ttxdone20:04
ttxDoug will be happy20:04
ttx#topic Add the Congress project20:04
*** openstack changes topic to "Add the Congress project (Meeting topic: tc)"20:04
ttx#link https://review.openstack.org/16520420:04
ttxBig tent, level 320:04
mikalI just -1'ed that one if you need to refresh your gerrit tab20:04
*** sridhar_ram has joined #openstack-meeting20:04
*** sridhar_ram1 has quit IRC20:04
vishyyou got my vote so that should be enough20:05
*** dflorea_ has joined #openstack-meeting20:05
*** dkranz has quit IRC20:05
*** dflorea has quit IRC20:05
ttxGot some nework issues right now, please discuss without waiting for me20:05
mordredsarob: you still working on this?20:06
mikalOk, shall we talk about my -1 then?20:06
*** aimon has joined #openstack-meeting20:06
sarobYup20:06
sarobMy patch20:06
mikalSo, sarob just replied to my comment (I assume)20:06
jeblairmikal: i don't think a release should be a requirement -- i would like us to be able to handle projects that even _start_ within our structure20:06
sarobMikal: yup20:06
mordredawesome20:06
*** andreykurilin_ has quit IRC20:06
ttxjeblair: I tend to agree with that20:06
mikaljeblair: so, I worry about everyones random ideas ending up being openstack projects and never releasing20:06
russellbttx: jeblair agree20:06
ttxI noted my small concern in a comment -- I know we are not supposed to judge maturity but more of a cultural fit, but I have a hard time seeing the current status and future of this project20:07
mikaljeblair: that's not the case with congress, but I worry about the precident20:07
russellbi dunno, this seems far enough along though that i'm not worried20:07
mordredsarob: btw - there is a stackalytics feature called corrections.json where you can remote unnatural commits from the calculations ...20:07
russellbit's not an empty repo or something20:07
*** dneary has quit IRC20:07
sarobMordred: roger that20:07
mordred(in response to tim hinrichs comment about that one commit)20:07
ttxbut then the comments I got in answer to my comment were reassuring20:07
mikalrussellb: Agreed20:07
mikalAs I said, I'm mostly concerned about the precident, not congress itself20:08
russellbmikal: interesting point though worth considering ... is "empty repo" enough?  or if not, what is the line?20:08
ttxmikal: I guess if it goes nowhere and dies we could remove them20:08
anteayattx have we ever?20:08
mesteryttx: Is there a process for removing things defined yet?20:08
russellbnot a process, but stuff has been killed20:08
ttxanteaya, mestery when "'things" were only the integrated release, we couldn't realease easily20:08
sdagueyeh, honestly, I'm with mikal on the fact that I'd really like to see software release before we include them20:08
mesteryBecause if not, letting things in and trying to remove them will be challenging.20:08
ttxerr.. remove easily20:08
mikalIts also not super onerous to ask Congress to do a release when ready and then come back20:08
* mordred submitted a patch to kill gantt earlier today in fact20:08
ttxIn a big tent setting it's slightly easier to do20:09
mikalThat's probably only a couple of weeks delay at this point20:09
*** Shrews has left #openstack-meeting20:09
anteayamordred: you just removed the code, the repo lives on20:09
sdaguemordred: yeh, gantt is a good instance of a repo that has generated huge confusion in it still existing20:09
sarobPlanning on a kilo release good enough for concern?20:09
ttxmikal: if they enter now they get summit space though20:09
russellbttx: unless it's in the tc approved release, and we have to follow a process with the board around removals20:09
mordredanteaya: the repo will always live on :)20:09
ttxrussellb: yes20:09
*** dkranz has joined #openstack-meeting20:09
* mestery doesn't like that we're dangling summit space as incentive to bring projects onboard20:09
mordredmikal: we regularly start projects in infra from completely blank repos20:09
jeblairi'm coming to terms with the fact that git repos are free, and we are building a structure around navigating a lot of git repos and filtering out the important ones20:09
anteayamordred: right that is the point20:09
mikalttx: seriously? We can't just grant an exception for summit space?20:09
anteayajeblair: but are we filtering them out20:10
mikalttx: surely we could recognize this as an unusual situation and handle that...20:10
mordredmikal: and I'd like for the big tent to allow us to keep doing that20:10
anteayajeblair: see I think the filtering out thing is where some folks (me) are having an problem20:10
jeblairi think a benefit of that structure is that we can actually _start_ projects within it20:10
sdaguemordred: I think that's a bit different as it's under an existing team structure20:10
ttxmikal: well, waiting for them to push a tag is about as silly20:10
*** annegentle has joined #openstack-meeting20:10
sarobNoting that summit space is a big deal20:10
sdaguewe're talking about a new team that's never demonstrated a release on anything20:10
morganfainbergjeblair, ++ i like the attitude that repos are free ;)20:10
mikalRepos inside projects are free20:10
mikalProjects are not20:10
russellbsarob: quick, go push a tag :-p20:11
markmcclainexcept that the bar for making a release is so20:11
mordred:)20:11
jeblairit's always seemed strange to me that we don't have a good way of starting a new project from scratch within openstack.  i see the opportunity to correct that in the big tent20:11
mordred++20:11
sarobWell congress did push m220:11
jeblairanteaya: that's what the project tags effort is about -- helping to navigate that20:11
markmcclainjeblair: +120:11
*** redixin has quit IRC20:11
sarobAnd plans to push kilo too20:11
ttxmikal: We can certainly give exceptions out -- but in that precise case saying "you will be in once you push a tag" is unnecessary wait imho20:11
anteayajeblair: well hopefully that will help me then20:12
anteayathe concern I'm hearing is about clutter20:12
* markmcclain waits for a project to tag a release entitled the tc_requires_this20:12
*** xingchao_ has joined #openstack-meeting20:12
anteayawhat do we do with the clutter20:12
mikalttx: you are welcome to disagree with me20:12
russellblack of any release tags helps communicate "doesn't do releases yet" i suppose20:12
mesteryrussellb: ++20:12
mordredrussellb: ++20:13
* annegentle looks for a jumping in spot20:13
jeblairannegentle: here's one!20:13
anteayaannegentle: sharpen your elbows20:13
annegentlesarob: how did congress discuss last summit?20:13
mordredor maybe "has chosen to not believe in releases and instead only targets CD style"20:13
russellbmordred: touche20:13
sdaguewhat about the concern that policy already means something in openstack, which is not this?20:13
sarobAnnegentle: congress got a design space20:13
sdaguebecause I'm not looking forward to that becoming more confusing20:13
sarobFloor 2 and 3/420:13
sarobAbout 80 people20:14
annegentlesdague: with ya on that one20:14
mesterysdague: That's a valid concern IMHO20:14
jaypipessdague: ++20:14
mordredsdague: that is a fair point ... I've been meaning to write something up about resource names20:14
sarobWith 3 follow up sessions20:14
*** eharney has joined #openstack-meeting20:14
sarobIn the Dev lounge20:14
* mordred glares at keystone domains20:14
jaypipessdague: that is something I raised with the GBP folks last year as well.20:14
mordredotoh - keystone has a thing called domains which are not part of the domain name system20:14
russellbfair point20:14
sdagueyeh, I have the same fundamental issue with GBP20:15
mesteryjaypipes: Except GBP isn't policy, it's a networking API :)20:15
* morganfainberg apologizes for the poor naming from before he worked on the project20:15
russellbi have bigger issues with GBP :)20:15
mordredso, if we're going to start in on that, I'd really like to see the TC ask keystone to rename domains to realm20:15
morganfainbergkeystone domains should have been called Realms (we basically are KRB anyway...)20:15
sdaguemordred: well, lets sort out a deprecation path to get sane naming20:15
ttxback on topic please20:15
* mordred starts working on a spec20:15
ttxLooks like we have two camps20:15
mordredttx: I think it's on topic20:15
mikalOMG, let's focus on congress for now please20:15
sdaguebut the reality is that reusing a const pointer for a name for a different thing is terribly confusing20:15
anteayasdague: ++20:16
mordredsdague had an excellent point about the generic concept that congress implements20:16
jeblairso can we ask congress to describe it as "Non-domain specific regulatory policy enforcement" ?20:16
russellbsdague: is the pointer const, or the contents it points to const?20:16
russellbsorry, been writing C ...20:16
ttxcamp 1 says project teams should at least have a release, otherwise how do they actually contribute to the openstack mission20:16
sdaguerussellb: :P20:16
ttxcamp 2 says project teams should be able to start from nothing as long as their intentions are pure20:16
mordredttx: camp 3 says that project teams shoudl be able to start frmo nothing even if they never intend on making a release20:17
mordredbut also counts itself in camp 2 for the purposes of talying20:17
mesterylol20:17
dtroyerdoes camp 2/3 have any sort of idea _who_ can do this?  anyone at all?20:17
ttxmordred: that is camp 220:17
dtroyeror just people we 'know'20:17
annegentledtroyer: it's people we 'like'20:17
jeblairanyone20:17
annegentledtroyer: :P20:17
*** ayoung has quit IRC20:17
mordredjeblair: ++20:17
mikalttx: so... this is what gerrit is for right?20:17
*** xingchao_ has quit IRC20:17
*** henrynash has joined #openstack-meeting20:18
ttxyes20:18
mikalttx: can't people just vote, and if I am the only -1, then merge it20:18
*** matrohon has quit IRC20:18
dtroyerso why do we continue to need stackforge in that world?20:18
jeblairwhich is the status quo for projects that join stackforge, which is part of openstack20:18
mesteryIf it's anyone, why are you even debating this? :)20:18
russellbsarob says they did milestone 220:18
mesteryJust let them all in! :)20:18
russellband will be doing kilo20:18
ttxmikal: fwiw I was on camp 1 until I realized that a tag is cheap and doesn't carry any meaning of maturity20:18
russellbi'm sympathetic to camp 1, just see it as largely addressed20:18
annegentlettx: +120:18
jeblairdtroyer: i don't think we do.  i'd like to remove "rename repostories" as part of our software lifecycle20:18
ttxrussellb: they don't have tarball jobs though :)20:18
russellbheh20:18
zanebmikal: consensus >> voting20:18
mikalttx: it is unproven that our users and the community will interpret the git namespace in the way we hope they will20:18
*** tiswanso has joined #openstack-meeting20:19
ttxso the tag doesn't create a release20:19
russellbwell i'm still in camp 2, i don't think it's required20:19
dtroyerok, cool.  then we're removed that barrier to resource allocation in corporations.20:19
russellbno releases is a valid choice MIO20:19
russellbIMO*20:19
mikalttx: they have certainly done strange things we didn't intend with that stuff in the past20:19
dtroyerthey'll find anoher one to use unless we give them one we like20:19
mordredzaneb: I'm not sure what bitshifting consensus and voting does ...20:19
jeblairmikal: i feel certain they will as soon as we have enough things in there to make it clear where the bar is set20:19
anteayadtroyer: is there one we like?20:19
mordredzaneb: :)20:19
sdagueok, so I'm fine with no release if we've got some reasonable way to have someone outside of a project realize it's dead and get it killed off20:19
*** jruano has quit IRC20:19
dtroyeranteaya: unknown, except we haven't particularly cared for the two previous ones20:20
*** achanda has quit IRC20:20
*** padkrish has quit IRC20:20
ttxOne more +1 and this passes now, otherwise we have to wait for final vote next week20:20
anteayasdague: me too20:20
sdaguebut that still doesn't address 'Policy as a Service' being confusing20:20
anteayadtroyer: yes I agree to that20:20
*** tiswanso has quit IRC20:20
*** padkrish has joined #openstack-meeting20:20
ttxAny other question on Congress ?20:20
jeblairttx: +120:20
mordredsdague: I agree - I'd love to see either a different word or maybe an adjective added20:20
jeblairi'm going to write a patch20:21
*** tiswanso has joined #openstack-meeting20:21
ttxOK, we have 720:21
mordredsince I believe we're expecting keystone to start offering access to policy files soon20:21
russellbmordred: sdague ++20:21
sarobSweet20:21
mordredsarob: ^^20:21
ttxLast call before I approve it20:21
zanebmordred: tbh, to this day I have no idea what congress is20:21
*** alexpilotti has quit IRC20:21
morganfainbergmordred, fwiw, I expect that to be a big focus in liberty [if that weighs in anywhere]20:21
mordredsarob: it would be a friendly if you could figure out a better word than "policy"20:21
morganfainbergmordred, for the conversation20:21
russellbzaneb: it's less scary if you really look into what it does :)20:21
mordredsarob: I have no suggestions20:21
sdaguemordred: it's compliance20:21
sdagueCompliance Enforcement20:22
zanebafter reading the wiki page multiple times, being pitched on IRC about it and attending an unrelated summit session that was hijacked by congress devs20:22
sdaguethat's what it should be called20:22
mordredsarob: perhaps compliance as a service then?20:22
jeblairi proposed https://review.openstack.org/16948020:22
sarobI think policy is sticky20:22
jeblairsdague, sarob: ^ maybe we can take that as a strawman to bikeshed on20:22
sdaguesarob: ?20:22
*** balajiiyer has joined #openstack-meeting20:22
ttxOK, it's in20:22
mordredsarob, sdague, jeblair: let's find a cage and fight it out outside of the TC meeting20:22
sdaguesure20:23
sarob;)20:23
ttxnext topic20:23
jeblairmordred: agreed, yeah, that's what i intended to do with that change20:23
ttxsarob: welcome20:23
ttx#topic Apply release:* tags to current projects20:23
*** openstack changes topic to "Apply release:* tags to current projects (Meeting topic: tc)"20:23
ttx#link https://review.openstack.org/16768220:23
sarobTtx: thanks!20:23
ttxThis is describing the release model for each of the code repositories in the yaml file (if they do releases)20:23
annegentleoh he's capital Ttx now!20:23
ttxI think it's pretty straightforward and a base we can iterate on.20:24
ttxIt's got 7 YES so I can approve it now20:24
ttxLast minute questions ?20:24
russellbyay20:24
*** BrianShang_ has joined #openstack-meeting20:24
*** padkrish has quit IRC20:25
annegentleI think it's great it's already bringing in good questions.20:25
ttxRight, that exercise raised two interesting questions (which I would consider orthogonal to the patch)20:25
ttx(Approved)20:25
annegentleit being tag application20:25
ttxThe first one is the need for a "release:has-stable-branches" tag to differentiate between a project that just merely has a stable branch cut from their last release (which may have been months away), like an Oslo library20:25
ttxand a project that consciously tries to align with the 6-month release cycle end (like Swift)20:25
ttxI'll propose that new tag in a subsequent patch20:25
ttxThe second question is more general, and is about how to provide the most useful information to our downstream users20:25
ttxShould we tag every git repository, or just "deliverables" (OpenStack software git repositories) ?20:26
*** maishsk has joined #openstack-meeting20:26
ttxI think our users, when they will browse the catalog of OpenStack projects, only want to see things they might actually consume ('Neutron') and not necessarily every git repo in OpenStack-land20:26
ttxSo it feels like we could use an abstraction layer between project teams and git repositories and apply tags to that new layer20:26
ttxBear with me while I illustrate with a few examples20:26
*** baoli has joined #openstack-meeting20:26
ttxNova currently has 3 repositories (nova, nova-specs and python-novaclient). I'd argue that as far as our users are concerned, it produces two deliverables (Nova and the Nova python client library), and apply tags only to those20:26
russellbi had a variation on that question ... whether it makes sense to tag the team in some cases (like diversity)20:26
*** ibiris_away is now known as ibiris20:27
ttxIt is an abstraction layer, because in some cases deliverables can contain more than one code repository20:27
ttxFor example, Neutron currently produces a "Neutron" deliverable out of openstack/neutron, openstack/neutron-fwaas, openstack/neutron-lbaas and openstack/neutron-vpnaas, since they are always released at the same time.20:27
*** ijw has quit IRC20:27
ttxThe users consume "Neutron", the fact that it's technically separated into 4 code repositories is a technical implementation detail20:27
*** varora has joined #openstack-meeting20:27
*** BrianShang has quit IRC20:27
ttxNow... there are corner cases. Should we consider libraries "deliverables" ? For example should Cinder have an "os-brick" deliverable ?20:27
ttxShould we tag individual infrastructure projects ? Or not tag them at all, since they are a supporting cast and not really a part of the IaaS platform ?20:28
ttxOr should we consider that all infra forms a single "deliverable" ?20:28
ttxIs docs a deliverable ?20:28
ttxetc.20:28
*** banix has quit IRC20:28
*** dflorea_ has quit IRC20:28
mordredI'm pretty sure all of infra is not a single deliverable, for whatever that is worth20:28
jeblairttx: that makes sense, especially with projects collecting more component repos, that people may not need to see the components listed separately when evaluating what the project produces.20:28
*** adalbas has quit IRC20:28
*** dflorea has joined #openstack-meeting20:29
ttxtrying to see what would make the most sen,se for a consumer of the tag system (a downstream user)20:29
russellbthe components of the Neutron deliverable likely have different maturity levels20:29
anteayawould you ask individual projects to answer that question?20:29
anteayawhat is your deliverable?20:29
jaypipesrussellb: that was *exactly* my thought.20:29
jeblairmordred: depends on what a deliverable is.  in some ways, yes, in others, no.20:29
mesteryMaybe also ask downstream consumers what they'd prefer?20:29
russellbso maybe they're separate deliverables and the model holds20:29
ttxrussellb, jaypipes: in the neutron example above, they are released as a single "thing"20:29
mordredjeblair: fair20:29
zanebcrazy idea: TC assigns tags to projects, projects decide for themselves which of their repos the approved tags are applied to20:29
ttx(maybe deliverable is not the right term for this)20:29
russellbbut they're different enough to consider them separately :)20:29
zaneb(thinking out loud here)20:30
anteayattx: no I think it is20:30
russellbthey are optional bits of significant functionality with vastly different maturity levels, AFAICT20:30
anteayathe problem is the variety20:30
jaypipesttx: well, yes, but python-neutronclient and neutron (the 4 repos) have different release cycles.20:30
sdaguerussellb: ++20:30
*** henrynash has quit IRC20:30
ttxzaneb: right, that was my point. Nova produces "nova" and the python nova client... how many repos they split Nova into is not really significant20:30
*** annegentle has quit IRC20:30
ttxjaypipes: that's two difefrent deliverables though20:30
jaypipesok20:30
jeblairttx, mordred: regarding infra specifically, i don't want to get too hung up on it because we are here to support the overall effort, not make it more difficult.  however, we do want to participate in it as much as possible.  so if tags are being applied for diversity, etc., i would like them to be applied to infra in some way.  but i also don't think we need 160 entries in the openstack project browser.20:30
mikalI can see the projects with many hundreds of repos being very confusing to consumers20:30
ttxOne team, two deliverables, 7 repos20:30
mikalTripleo for example20:30
zanebttx: yeah, it would be really nice for the TC not to have to care at the repo level20:31
*** banix has joined #openstack-meeting20:31
mordredjeblair: +10020:31
sdaguettx: I think the fact that neutron advanced services are on the same deliverable schedule is just a bug of the current split being only partial20:31
sdagueI assume they will become more independent over time20:31
jeblairsdague: maybe they become separate deliverables then, but are one now?20:31
*** padkrish has joined #openstack-meeting20:31
russellbi think i like the deliverables concept to create a more natural place to apply some tags20:32
ttxjeblair: hmm.. maybe we can filter the project browser on some other data -- like a relevant-for-the-browser tag.20:32
russellbjust ... details to work out, i guess20:32
ttxanyway, I was thinking out loud. Blame devananda20:32
sdaguejeblair: yeh, but I think it's important to consider them separately, because as many folks have said, they are vastly different maturities20:32
*** sarob has quit IRC20:32
ttxjust wanted to throw it out there and see what you thought20:32
russellbtentative optimism20:32
jeblairsdague: and people may choose not to deploy some of them based on that maturity level, even now?20:33
russellbjeblair: yes20:33
russellbfor sure20:33
sdaguejeblair: yes20:33
*** ayoung has joined #openstack-meeting20:33
russellbi'd say most people don't deploy any of them, in fact20:33
jeblairyeah, so that feels like multiple deliverables then,20:33
*** annegentle has joined #openstack-meeting20:33
*** annegentle is now known as agentle_20:33
ttxright maybe that was not the right example20:34
markmcclainrussellb: I've have LBaaS in the wild20:34
agentle_whacky internets, catching up now20:34
ttxI think everyone agrees we should not tag nova-specs20:34
ttxor openstack/governance20:34
russellbmarkmcclain: cool :)20:34
ttxso *some* repos do not make sense being tagged20:34
*** annegentle has joined #openstack-meeting20:34
anteayattx I agree with that20:34
dougwigit's almost as if you need a TC managed integrated-release tag, which defines what is "openstack".20:34
jaypipesttx: are we *specifically* referring to release:* tags here?20:34
russellbttx: i also agree that for some projects split into repos, tagging individually doesn't make good sense20:34
jeblairttx: but should contributing to nova-specs feed into the contributions we look at when we evaluate diversity of nova?20:34
ttxjaypipes: no20:35
jaypipesdougwig: very funny.20:35
russellbdougwig: just wait until we get back to defining the "TC Approved Release"20:35
ttxfull circle completed!20:35
russellbpretty much20:35
jeblairwe do, of course, have exactly that tag.  it is deprecated.20:35
dougwigisn't that what you're doing right now?   re-arranging the deck chairs notwithstanding.20:35
jaypipesttx: then I'm -1 on this. I want to tag repos with fine-grained information about that repo, not broad tags that may or may not accurately represent individual repos within a project space.20:35
*** leonchio_ has quit IRC20:35
ttxjaypipes: ok20:36
jaypipesdougwig: no.20:36
ttxOK, I propose we move on. I'lml give the idea some more thought and propose a strawman change if I think the idea has value20:36
ttxThanks for the feedback though20:37
vishyor we could elect someone to tag the release with their name20:37
ttx#topic Projects list housekeeping20:37
*** openstack changes topic to "Projects list housekeeping (Meeting topic: tc)"20:37
jeblairttx: thanks; there are definitely some good things in there20:37
vishy“jaypipes certified openstack”20:37
vishy:p20:37
ttx* Adds the openstack/os-cloud-management to TripleO... (https://review.openstack.org/166723)20:37
ttxMikal raised an interesting point on the name of the lib being a bit too generic20:37
* jaypipes remarks that it's easy to aggregate fine-grained data. Not so easy to go the other way round.20:37
*** thinrichs has quit IRC20:37
*** sreshetn1 has joined #openstack-meeting20:38
* jaypipes still waiting for the os-on-os-on-os-on-os repo.20:38
mikalI fear we might not have been all that consistent with generic names in the past20:38
sdaguettx: it's at least better than os-cloud-middleware20:38
ttxsdague: lol20:38
jaypipesheh20:38
jaypipestru nuf20:38
jeblairmikal, ttx: i agree it's too generic, but matches the level of descriptiveness we have in other similar projects.  :/20:38
vishyseptuple-o20:38
vishynice20:38
*** baoli has quit IRC20:38
jeblairi feel like the ship has sailed20:38
*** agentle_ has left #openstack-meeting20:38
mikaljeblair: its never too late to be grumpy about it though20:38
mordredmikal: I'm grumpy about plenty of things all day long :)20:39
*** thinrichs has joined #openstack-meeting20:39
sdagueyeh, until we dissallow the words middleware and lib  in projects, it seems overly harsh to be grumpy of generic names20:39
*** baoli has joined #openstack-meeting20:39
jeblairwe could suggest the tripleo folks mass-rename s/os-/tripleo-/ in their project names20:39
ttxwe could20:39
mikalOMG, I was just thinking that20:39
annegentlejeblair: the naming ship?20:39
mikaljeblair: let's do it20:39
ttxmikal: that is orthogonal to that patch though20:39
russellbwhat if they change the number of Os20:39
ttxCan I approve this one ?20:39
mikalttx: true dat20:39
annegentles/os-/ooo-20:39
mikalttx: and probably also a dick move20:39
*** sreshetn2 has quit IRC20:39
ttxwell os-* is not a great prefix anyway20:40
russellbSeveralO20:40
*** agentle_ has joined #openstack-meeting20:40
* zaneb can provide more info on what this lib will do if anyone has questions20:40
ttxSo I'll approve all of thoise unless a -1 is posted (in which case we'll discuss it next week20:40
ttx* Add os-testr repo to QA (https://review.openstack.org/167244)20:40
russellbzaneb: what?  the name is the important part20:40
mikalzaneb: can I use it outside of the context of tripleo?20:40
ttx* Add ansible-puppet repo to infra (https://review.openstack.org/166820)20:40
ttx* Add ansible-build-image to infra (https://review.openstack.org/166821)20:40
*** david-lyle has quit IRC20:40
ttx* Add bashate to the QA program (https://review.openstack.org/168012)20:40
ttx* Add puppet-diskimage-builder to Infra (https://review.openstack.org/167612)20:40
ttx* Move os-client-config to openstack namepsace (https://review.openstack.org/167730)20:41
*** bernardo-silva has joined #openstack-meeting20:41
jaypipesttx: cool with me.20:41
ttxI'll collect that tomorrow morning. So if you really think os-cloud-management is too generic, -1 it20:41
zanebmikal: not really, the idea is for it to be the common part for things that need to be done by both the Tuskar UI and CLI users, but which are not in the Tuskar API20:41
ttxand we'll continue that interesting discussion next week20:42
*** e0ne has quit IRC20:42
mikalzaneb: ok, in that case I am -1 on that name20:42
*** e0ne has joined #openstack-meeting20:42
annegentlezaneb: gotta go with mikal on that one too20:42
ttx#topic Open discussion20:42
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:42
ttxA few topics I wanted us to discuss20:42
ttx* Neutron renaming "core reviewers" to "maintainers" (https://review.openstack.org/164208)20:42
* mikal seems to be the grumpy one this week20:43
ttxThis was proposed in parallel to https://review.openstack.org/#/c/163660/ which we rejected20:43
ttxmikal: I have a damn cold so I am also grumpy20:43
russellbmikal: we all get a turn :)20:43
ttxThe main objections raised (by TC members, not really by Neutron devs) are:20:43
ttx(1) the bundling of review duties with other project duties to form a single super-developer status20:43
ttx(2) the choice of the "maintainers" term which is a bit overloaded and far away from "reviewing"20:43
ttxNow Neutron devs (and others) claim it's none of our business since we are not Neutron devs, and that you can't dictate culture by committee20:43
mordredI believe my objection here is going to be that I do not think this is a project level thing20:43
mordredand I do believe that we can do that20:43
ttxThat said, TC members judge OpenStack projects inclusion in the big tent by the sharing of common community and development values (the "are you one of us" test)20:43
*** pritesh has joined #openstack-meeting20:43
russellbmordred: ++20:44
mesteryWhat? We're not creating a super developer, we're acknowldeging those already exist. I've broken the patch in two.20:44
mordredand I believe taht if they want me to butt out they have another thing coming20:44
ttxAnd we have oversight as long as they are called openstack/neutron and not stackforge/neutron20:44
annegentleI'm with mordred on consistency in names and understanding.20:44
mesteryI think that's not a fair characterization of hte patch to be honest20:44
annegentlebut I do like doing what I want with my specialty teams :)20:44
marunI don't think it should be the place of the TC to define culture at the project level.20:44
mordred I do not believe that it is appropriate for neutron to try to rename a concept that exists across openstack20:44
mordredmarun: I believe it is exactly the place of the TC20:44
ttxmestery: ok, you're defining a super-developer class, not creating it because it already exists in Neutron20:44
marunmordred: Really?20:44
mordredmarun: yes20:44
mesteryttx: Nope, I'm not saying that.20:44
dougwigttx: it exists everywhere in openstack.  that most refuse to admit that does not make it less true.20:45
mesteryttx: I'm documenting what existing core reviewers do20:45
russellbmy main objection was changing the name, honestly20:45
mordredmestery: I agree with documenting what exisitng core reviewers do20:45
mesteryHow did you interpret the first patch as "defining a super developer class in neutron"?20:45
marunmordred: Tell me, where have you ever seen design-by-committee be applied to defining culture?20:45
mesterymordred: thank you20:45
annegentlemarun: we try to be the resolvers of conflict while representing the contributors20:45
mordredthe name change is troubling because it creates a schism in terminology between one of our projects and another20:45
mordredand in the world of the big tent20:45
marunmordred: sure20:45
mordredone of the few things we have remaining is a common culture20:46
marunmordred: design-by-committee is the way forward, gotcha20:46
annegentlemarun: it's not design by committee, more like representation20:46
* mestery thinks maintainers better reflects what core reviewers do and was hopeful that jogo'20:46
marunannegentle: if you say so.20:46
mesterypatch would have been better received20:46
marunannegentle: kind of potayto, potahto to me20:46
jeblairmordred: i agree20:46
marunmordred: there isn't common culture20:46
marunnews flash20:46
mordredmarun: what i'm saying is that if there is a term, called "core reviewer" that is used across openstack, and neutron choses to abandon it20:46
ttxmestery: I think you bundle a number of duties together -- that prevents for example non-reviewers from being a "maintainer"20:46
maruneach project is different and unique20:46
mordredmarun: believe me, as a consumer of all of them, that is clear20:47
marunand we need to be results oriented instead of process oriented20:47
mesteryttx: Yes, that's the current reality. All that patch does is reflect that.20:47
russellbmordred: lol20:47
annegentlemarun: happy to deep dive on it with you esp. where you see actions aren't reflecting that representation. As we grow, culture remaining meaningful is the hardest part.20:47
mesteryttx: I'd like to change that, but thought that documenting what exists now is better to start with20:47
* jogo is still planning to follow up with ttx's suggestion of 'We should probably be having that discussion on the ML'20:47
marunwhere is the TC in defining what results we're trying to achieve?20:47
mordredmarun: what are you even talking about right now/20:47
annegentlejogo: probably best20:47
marunas opposed to defining seemingly arbitrary ways we have to achieve it?20:47
mordredmarun: we are talking about a patch that was proposed to change a name of a group of people20:47
*** pritesh_ has quit IRC20:47
mesteryjogo: ++20:47
russellbso if mestery just updates the docs and leaves the name alone, is there objection?20:47
sdaguerussellb: I'd have no objection to documentation of existing role without a name change20:48
marunmordred: yes, to change how we perceive ourselves in the project so we can forment change in how we achieve results20:48
russellbsame here20:48
ttxjogo: yes, I don't expec that discussion to go anywhere, just wanted to raise it to the collective attention20:48
sdagueI think terminology changes need to be global20:48
russellbsdague: agree20:48
mordredsdague: ++20:48
marunsure, design-by-commiitte it is20:48
annegentlemarun: if you don't want seemingly arbitrary I would think you'd want tc representatives to be able to debate this uncovered naming issue respectfully and honestly.20:48
marunyay for the TC, arbiter of all that is right and good20:48
sdaguebecause it's too f-ing confusing for people to interface otherwise20:48
marunright20:48
marunculture is messy, let's simplify20:48
dougwigcan we dial ourselves back to duties within mystery's change that the TC has a problem with?20:49
ttxmarun: some people in openstack work on multiple projects20:49
mesteryrussellb: Abandoned20:49
marunttx: some people in the world paricipate in different social realities, too20:49
marunttx: and somehow, they manage20:49
anteayadougwig: I don't think the duties were the issue20:49
marunbut sure, openstack is special20:49
ttxmarun: I envy the simplicity of your life20:50
russellbi think this whole thing is being blown way out of proportion20:50
russellbmestery abandoned the name change portion20:50
marunttx: I think that's my line20:50
mordredrussellb: I agree20:50
*** david-lyle has joined #openstack-meeting20:50
mesteryIt's gone20:50
russellbwhat other concern remains?20:50
*** sridhar_ram has quit IRC20:50
mordredrussellb: none from me20:50
russellbthat was my only concern20:50
*** ibiris is now known as ibiris_away20:50
russellbissue resolved from my side20:50
mordredI think the clarification is awesome20:50
zanebmarun: I think we should be differentiating where that adds real value. renaming stuff like this is not one of those places imho20:50
mordredzaneb: ++20:50
marunzaneb: you are certainly entiteld to your opinion20:50
jeblairmestery: ++20:51
marunlanguage matters20:51
ttxmestery: I like it20:51
annegentlethanks mestery20:51
jaypipesmarun: everyone is entitled to my opinion.20:51
mordredjaypipes: :)20:51
mesteryThanks mordred!20:51
mesteryThanks for the discussion here folks!20:51
russellbthanks, mestery20:51
mesteryI do look forward to jogo's ML thread on the same :)20:51
ttxmestery: I think we actually disagreed on different things20:51
mordredthanks mestery !20:51
mesteryttx: lol :)20:51
*** claudiub has joined #openstack-meeting20:51
ttxok, next fun discussion20:52
ttx* WIP: Add Group Based Policy Project (https://review.openstack.org/161902)20:52
annegentlematrixed disagreement20:52
ttxSince we have some time left we could discuss the GBP addition20:52
SumitNaiksatamttx: hi20:52
*** e0ne is now known as e0ne_20:52
*** e0ne_ is now known as e0ne20:52
ttxThey have removed it from the agenda because someone raised a question on the review and to give them time to address it20:52
SumitNaiksatamttx: just about to say that20:52
ttxMaybe we should see how much of a common concern that raised question is20:52
sdagueso objection #0, beyond all other objections, we *can not* have 3 things in openstack that use policy to mean different things20:52
SumitNaiksatamwe felt that putting the patch in WIP would give some more time for discussions20:52
ttxI for one share russellb's concern about diluting Neutron20:53
sdaguethat's just super crazy pants clown car20:53
markmcclainsdague: ++20:53
anteaya++ to both sdague and ttx20:53
mordredsdague: ++20:53
russellbi just don't want a 3rd competing networking API20:53
SumitNaiksatamsdague: i agree20:53
mesterysdague: ++20:53
anteayarussellb: agreed20:53
mesteryrussellb: STRONG ++20:53
sdaguerussellb: also, I agree strongly with you on that20:53
dougwigso if nova-net and neutron both suck, we still won't let competition find a better solution?  isn't that the opposite of big tent?20:53
mesteryWe already have two20:53
markmcclainI share the same concern about having yet another api20:53
anteayadougwig: competition here isn't wan't our users want20:53
russellbdougwig: no, if there seemed to be strong consensus and support that GBP was the future, it'd be a different conversation20:54
SumitNaiksatamttx: i dont think it dilutes Neutron20:54
anteayadougwig: we have some things they like20:54
russellba very messy situation, but we'd work through it20:54
ttxI basically question the "positive contribution to the OpenStack Mission" when we circumvent such a basic component20:54
prasadvrussellb: I dont think it is competing network api. It is aapplication oriented api that uses neutron20:54
*** eglynn has joined #openstack-meeting20:54
ivar-laz_prasadv: +120:54
anteayattx: ++20:54
*** ayoung has quit IRC20:54
SumitNaiksatamrussellb: the intention is definitey not to create a 3rd competing API for networking20:54
russellbi know you keep saying that20:54
russellbi heard it20:54
ttxprasadv: is it purely building on top of Neutron ? Or has it its own network hardware plugins ?20:54
russellbbut that's not what i see20:54
dougwigi'm more commenting on how big tent could lead to this sort of issue becoming common.  it's open for all, except for sub-clause a, b, and subsection d.20:54
mesteryIt's a networking API20:54
markmcclainSumitNaiksatam: that is contrary to statement made by the GBP team last summer20:54
*** asalkeld has joined #openstack-meeting20:54
SumitNaiksatamttx: we dont circumvent any of the components20:55
ivar-laz_russellb: I've tried to answer your concern on the review. At any point GBP can or will circumvent Neutron's API20:55
mesteryLook at the "hands on lab" session in vancouver, and at the ODL Summit20:55
markmcclainSumitNaiksatam: at the time it was stated the intent was to be the v3 API20:55
mesteryLook at the fact it exists in OpenDaylight ... an SDN controller project ... focused on networking20:55
mordreddougwig: I think we shoudl be clear with people that there are some things, probably things that have made their way into defcore, where we're not particularly looking for competition20:55
mordredcompetition is GREAT20:55
mesterymarkmcclain: ++20:55
*** auld has joined #openstack-meeting20:55
SumitNaiksatammarkmcclain: absolutely yes, but the project has evolved20:55
anteayanetworking needs to fix the problems we have, we aren't lacking here, and we don't need more20:55
mordredbut after a point, it becomes noise20:55
russellbmordred: ++20:55
ttxSumitNaiksatam: I think that's the bottom of the question -- are we having network hardware plugins in two difefrent places20:55
jeblairthere was a lot of positive reception to the idea that the big tent would enable us to consider alternative approaches and implementations of functionality.  this seems to be that, so how do we exclude gbp on that basis?20:55
SumitNaiksatammarkmcclain: you are referring to the patch that was posted in neutron20:55
SumitNaiksatamanteaya: agree 100%20:56
*** mrmartin has joined #openstack-meeting20:56
anteayajeblair: it doesn't help us achieve the openstack mission?20:56
*** sridhar_ram has joined #openstack-meeting20:56
markmcclainSumitNaiksatam: ok.. that evolution in thinking wasn't very clear20:56
ttxjeblair: I think that competition becomes more costly the further down the layers you go20:56
mordredjeblair: oh, I'm not saying we should say no to gbp - I'm just saying that I don't necessarily think that competition in the area of networking APIs for openstack is good for our users20:56
*** rbowen has quit IRC20:56
*** amrith is now known as _amrith_20:56
ivar-laz_ttx: which plugin are you referring?20:56
ttxjeblair: for example, keystone competition makes no sense20:56
jeblairwould it be okay to accept ceph-based object storage?20:56
ttxjeblair: and actively hurts the openstack mission20:56
jeblairlots of people use and want that20:56
mordredjeblair: I would have no problem with that20:56
russellbi look it at as competition is more welcome the higher we go in the stack, or the less mature its "competitors" are ... basically we should use our heads and evaluate whether competition makes sense20:57
ivar-laz_ttx: all the existing drivers, vendor or not, must use Neutron for their data path to work20:57
SumitNaiksatammarkmcclain: happy to clarify, thanks fo asking20:57
* jogo finds this whole exercise of difficult because all of the GBP documentation seems to be self contradicting and very out of date20:57
jeblairmordred: i struggle to see the difference20:57
mordredjeblair: I do not believe there is one20:57
jeblairmordred: so this is a gut thing?20:57
mordredjeblair: I believe we are talking about two different things ...20:57
mordredjeblair: one of them is "do we let a project into the big tent"20:57
annegentleSumitNaiksatam: agree with jogo that docs would help provide evidence for your stated cause20:57
mikalSo, we used competing with nova as an example in the original discussions, and we liked that idea then. I'm confused about the distinction here to be honest.20:57
jaypipesjeblair: I think the difference is that, at least from my perspecitve (and I know SumitNaiksatam is updated docs and stuff) GBP isn't an alternative implementation of the Neutron API. It's a whole different networking API that essentially makes the Neutron API irrelevant (and is pretty much just a passthru to ACI-like vendor APIs.20:57
ttxivar-laz_: my question is.. will GBP forever act as a proxy API on top of Neutron API, or is it prone to plug directly into networking hardware features, and therefore use plugins20:57
mikalI'm not saying we should replace Neutron20:57
mordredjeblair: another is "do we consider the output of that project an essential part of the deliverable called OpenStack"20:57
mordredjeblair: I believe that letting someone in the tent does not imply the second thing20:58
russellbjaypipes: ++20:58
ttxivar-laz_: my understanding is that the goal is the latter20:58
mikalBut this "less competition at lower layers" thing wasn't discussed during the original votes20:58
SumitNaiksatamannegentle: sure, perhaps we were not clear, and we should do a better job20:58
mesteryjaypipes: ++20:58
mesteryjaypipes: Nailed it!20:58
ivar-laz_ttx: the Mission statement is to act on top of Openstack, by *using* it20:58
jeblairmordred: okay, i follow you and agree with you there20:58
annegentleSumitNaiksatam: believe me I know it's hard to find all the corners of the 'net :)20:58
jeblairmordred: so which question are we discussing? :)20:58
ivar-laz_ttx: that's the commitment, and today code base shows it.20:58
mordredjeblair: we SHOULD be discussing letting them into the party20:58
mordredjeblair: we seem to be forgetting that we are not defcore20:59
ttxivar-laz_: exactly. So GBP will forver be a proxy API on top of Neutron API ? In which case +120:59
*** rbowen has joined #openstack-meeting20:59
russellbttx: it's not that today20:59
*** thumpba has joined #openstack-meeting20:59
mesteryttx: I wouldn't bank on that down the road20:59
mordredso a) I think GBP is a bad idea. b) I support it being added to the openstack tent because I do not think inclusion in that tent should carry meaning20:59
SumitNaiksatamttx: thats how it works for networking constructs today20:59
jeblairmordred: so i'm with you on 1) +1 and 2) -1 (or really n/a -- see defcore)20:59
*** ibiris_away is now known as ibiris20:59
ttxOK, no time left -- I suspect Sumit will clarify the points we raised, in time for next week discussion21:00
SumitNaiksatamrussellb: why do you think its not like that today?21:00
ivar-laz_ttx: that's the mission :)21:00
SumitNaiksatamttx: sure21:00
*** s3wong has quit IRC21:00
zanebmordred: bad idea or bad implementation?21:00
SumitNaiksatamthanks all for the time21:00
SumitNaiksatamand the disscussion21:00
mordredzaneb: the idea of having a competing networking API approach21:00
ttxThanks everyone, closing the meeting to make room for next21:00
mordredzaneb: I think it serves nobody well21:00
mordredhowever21:00
mordredI don't think I should make that call right now21:00
ivar-laz_Thanks people for showing your concerns! join us on #openstack-gbp for more questions21:00
ttxFeel free to continue this discussion on #openstack-dev :)21:00
mordredand I think it's fine for GBP to play in our sandbox21:00
mesterylol21:00
zanebmordred: agreed, I would prefer to fix the neutron api in a future rev21:00
ivar-laz_ttx: or there!21:01
sdagueI think an important question is how open the api design process was here, and will be in the future21:01
annegentlethanks SumitNaiksatam!21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
russellbi think it violates at least one of the criteria in our new project guidelines21:01
openstackMeeting ended Tue Mar 31 21:01:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-31-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-31-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-31-20.02.log.html21:01
mesterysdague: That is a good question, I look forward to hearing that answer21:01
anteayarussellb: ++21:01
sdagueor is that basically locked because of the vendor back ends that it is optimized for21:01
*** annegentle has quit IRC21:01
russellbsdague: that.21:01
russellbthat too, i mean21:01
ttxok, next meeting21:01
*** agentle_ has quit IRC21:01
mesterysdague: Last I heard, it was, yes.21:01
ttxcourtesy PTL ping: devananda, dhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov, mikal: around ?21:01
eglynno/21:01
mesteryo/21:01
notmynamehere21:01
mikalHi21:01
*** annegentle has joined #openstack-meeting21:01
asalkeldo/21:01
david-lyleo/21:02
nikhil_ko/21:02
*** rkukura has left #openstack-meeting21:02
eglynndontcha just hate DST?21:02
*** adrian_otto has joined #openstack-meeting21:02
*** serg_melikyan has joined #openstack-meeting21:02
adrian_ottoirc://irc.freenode.net:6667/#startmeeting Solum Team Meeting21:02
ttxI hate time21:02
* mestery shakes his fast at DST21:02
ttx#startmeeting crossproject21:02
openstackMeeting started Tue Mar 31 21:02:26 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: crossproject)"21:02
openstackThe meeting name has been set to 'crossproject'21:02
adrian_ottoirc://irc.freenode.net:6667/#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-03-31_2100_UTC Our Agneda21:02
ttxadrian_otto: don't steal my meeting21:02
mesterylol21:02
mesteryMeeting theft!21:02
ttxOur agenda for today:21:02
*** prasadv has quit IRC21:02
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:02
adrian_ottouh, wait?21:03
ttxadrian_otto: wait what21:03
fungiadrian_otto: wrong channel?21:03
adrian_ottosorry guys21:03
morganfainbergadrian_otto, hi adrian :)21:03
ttx#topic PTL election season21:03
morganfainbergttx, o/21:03
*** openstack changes topic to "PTL election season (Meeting topic: crossproject)"21:03
ttxAdri2000: you can stay here21:03
ttxadrian_otto: I mean you21:03
*** mrmartin has quit IRC21:03
ttxOur meeting is more interesting21:03
ttxThe PTL election season is coming up:21:04
ttx#link https://wiki.openstack.org/wiki/PTL_Elections_April_201521:04
morganfainbergthat time of year again!21:04
ttxIf you don't plan to stand for reelection, it's more than time to encourage people in your teams to step up21:04
ttxSelf-nomination period starts end of week21:04
*** maishsk_ has joined #openstack-meeting21:04
ttxFeel free to reach out to the election officials if you have any questions21:04
fungias before, we'll also want the governance repo tagged so that our tools aren't hitting a master branch moving target21:04
*** rbowen has quit IRC21:05
mikal6am UTC is a weird time to start21:05
ttxfungi: sure I'll be around21:05
mikalJust sayin'21:05
*** rbowen has joined #openstack-meeting21:05
ttxdamn round planet21:05
mikalWhy not just midnight?21:05
fungimikal: it's more that i can generate the electorate rolls first thing when i wake up, and 0600 utc is well before i roll out of bed21:05
mikalNot that it matters21:05
ttxmikal: must carry some US-centricity21:05
morganfainbergmikal, i vote 0623UTC ... :P21:05
morganfainbergmikal, my vote doesn't matter though21:06
fungiand for whatever reason previous elections did 0600 utc21:06
ttxok, no question on that topic ?21:06
mikalfungi: ahhh, fair enough21:06
*** barrett1 has joined #openstack-meeting21:06
anteayanothing starts at 6 utc21:06
eglynnmidnight in US mountain time areas that don't do DST?21:06
anteayait was the utc equivalent of pacific time21:06
*** annegentle has quit IRC21:07
fungi0600 utc is merely the cut-off for contributions counting you into the electorate21:07
anteayafor midnight on the thursday21:07
anteayaand for the self-nomination period21:07
*** maishsk has quit IRC21:07
ttxnot that anyone cares anyway21:07
ttx#topic Design Summit content21:07
*** openstack changes topic to "Design Summit content (Meeting topic: crossproject)"21:07
*** ayoung has joined #openstack-meeting21:07
ttxOK, time to talk about the Design Summit in Vancouver21:07
*** ebalduf has joined #openstack-meeting21:07
ttxIn theory the content will be set by the newly-elected PTLs, but nothing prevents to start the discussion early21:08
eglynnanteaya: PDT is UTC-7:00 surely?21:08
anteayaeglynn: we have moved topics21:08
mesteryttx: Ack, starting early is well advised!21:08
ttxAs far as slot allocation is concerned, we don't have that many new projects after all, so we should be able to give everyone what they requested21:08
ttxFinal slot allocation and proposed slot layout should be available around April 10, once we know the final list of projects to be considered21:08
eglynnanteaya: ... yet the timezones stay the same21:08
ttxeglynn: I don't think anybody cares what hour the nomination week starts21:09
ttxQuestions on slot allocation ?21:09
tchaypoo/21:09
*** markmc has quit IRC21:09
bknudsondo we have some idea if everybody wants fishbowl or conference rooms?21:09
ttxbknudson: let me see21:09
bknudsonor are we getting a mix21:09
ttxeveryone getting what their PTL asked for when I polled them21:10
ttxgenerally a mix21:10
nikhil_kttx: How about cross project ones?21:10
bknudsongreat21:10
morganfainbergttx, good news!21:10
ttxcross-project is all fishbowl21:10
*** rfolco has quit IRC21:10
nikhil_kAll remaining slots ? or do we have min, max on that?21:10
ttxCurrently 133 fishbowls requested, 173 workrooms and 29 half-days21:11
nikhil_kThanks21:11
eglynnttx: what's the story on for scheduling the Friday afternoon?21:11
ttxnikhil_k: once the allocation is confirmed we may have scraps to share for the needy21:11
nikhil_kThat would be great21:11
ttxFriday afternoon is contributors meetups21:11
ttxlike Friday nmorning21:12
*** ebalduf has quit IRC21:12
bknudsonis there a feedback session on fri aft?21:12
eglynnttx: any projects who requested half day contrib meetup getting allocated the afternoon slot?21:12
bknudsonI'd like some info on how the economy is going.21:12
ttxbknudson: yes, last slot21:12
*** hemanthravi has quit IRC21:12
ttxbknudson: we invited the same speaker21:12
bknudsonwonderful!21:12
morganfainbergttx, was going to ask about that :P21:13
ttxbknudson: the economy is not getting better21:13
eglynnI ask because Friday afternoon == graveyard21:13
david-lylecan we talk economy in it?21:13
morganfainbergttx, you typed it out before i could ask.21:13
ttxeglynn: most projects requested full day21:13
*** aysyd has quit IRC21:13
eglynna-ha, k21:13
*** tiswanso has quit IRC21:13
anteayabknudson: the Canadian economy? straight down21:13
ttxeglynn: we might be able to schedule all the single half-day ones in the mornings21:14
notmynamewhat economy are you talking about?21:14
mesteryeglynn: I share your concern about friday afternoon being a graveyard :)21:14
eglynnttx: excellent, that would be wise I think21:14
ttxOK, next subtopic... session proposals21:14
*** achanda has joined #openstack-meeting21:14
ttxnotmyname: you missed a historic moment in Paris21:14
ttxAs far as session proposals go, we let everyone use their own tooling (mostly etherpads)21:14
notmynameoh yeah. I heard about it21:14
ttxIt would be great to reference those in:21:14
*** johnpur has quit IRC21:14
ttx#link https://wiki.openstack.org/wiki/Design_Summit/Planning21:15
notmynameI wouldn't say I missed it, Bon21:15
notmyname*bob21:15
ttxso if you already have a design summit suggestion etherpad, please add it there21:15
ttxso that people can find them21:15
ttxOne team asked that we make an ODSREG instance (the system we used for session proposals pre-kilo) available to them for session suggestion collection21:15
ttxODSREG code lives at https://git.openstack.org/cgit/openstack-infra/odsreg/ but I guess for those I'll set up team-dedicated instances of the tool21:15
ttxIt's not totally impossible we'll use ODSREG for suggesting cross-project sessions as well21:15
*** raildo is now known as raildo|away21:15
ttxMost other projects seemed happy with etherpads21:15
mestery++ to etherpads21:16
mtreinish+121:16
ttxyou can also use Google forms, whatever works best for you21:16
eglynngoogledocs sheets for the win21:16
eglynn... much easier to tally votes21:16
*** adrian_otto has left #openstack-meeting21:17
ttxeglynn: you do votes ? What kind of a dictatorship do you live in ?21:17
*** jruano has joined #openstack-meeting21:17
asalkeldhah21:17
eglynnttx: we vote, but North Korea stylee ;)21:17
ttxok.. questions on session proposals ?21:17
*** baoli has quit IRC21:17
mesterylol21:18
* morganfainberg already setup an etherpad for keystone21:18
nikhil_kttx: more info on the dates to come later?21:18
* morganfainberg is happy w/ etherpads.21:18
ttxmorganfainberg: please add link21:18
*** ndipanov has quit IRC21:18
morganfainbergalready done21:18
*** baoli has joined #openstack-meeting21:18
ttxnikhil_k: dates ?21:18
*** xingchao_ has joined #openstack-meeting21:18
* morganfainberg also made sure to be the weird project that didn't follow the naming convention for the etherpad :P21:18
nikhil_kUntil which people can do proposals21:18
morganfainberg[not on purpose]21:18
nikhil_kttx: people like to have meetings before slots can be allocated21:19
*** bswartz has quit IRC21:19
ttxnikhil_k: you can communicate your own. there will be a deadline to fill the schedule, but otherwise you're on your own21:19
*** mscohen has quit IRC21:19
ttxwhich brings us to our next subtopic21:19
*** david-lyle_ has joined #openstack-meeting21:19
nikhil_kand that deadline to fill the schedule should be close to the main event like the previous time right?21:19
ttxyes21:19
ttxAs far as scheduling goes, we won't use ODSREG this time, mostly because the sched.org constraints changed (we share the sched with the main conference now)21:19
nikhil_kthanks21:19
ttxSo I created a new tool that lets you directly edit a few things on sched in the slots that are allocated to your teams, I'll send you link to a demo soon21:20
ttxCode currently lives at https://github.com/ttx/summitsched for the curious21:20
mesteryttx: Cool!21:20
ttxit's basically a sched proxy21:20
ttxsince shced has a pretty simple idea of ACLs21:20
*** banix has quit IRC21:20
ttx(stores it in a binary)21:21
ttxWe still have a decision to make though. Cheddar enforces a number of things, like making sure all sessions on a track are prefixed by the track name, for clarity21:21
* morganfainberg wonders how many ways we can break sched this time :P21:21
*** henrynash has joined #openstack-meeting21:21
*** _nadya_ has joined #openstack-meeting21:21
ttxIt also enforces boring titles and descriptions for "work sessions" and the "contributors meetups", in order to make them as unattractive as possible for the general attendance21:21
ttxYou can see the results at: http://testingsiteforfutureevents2015.sched.org/21:21
mesterynice!21:22
*** Sukhdev has joined #openstack-meeting21:22
morganfainbergttx, i want to go to the "Ops: cake is amazing" session21:22
asalkeldwith "food not provided in the title" ;)21:22
ttxSo basically you can give fishbowl sessions a title, but work sessions and contributors meetups have set titles21:22
*** dflorea has quit IRC21:22
*** atiwari has quit IRC21:22
ttxsince they have such limited room you don't want everyone to show up because tyou mentioned "docker" in title21:22
ttxOne question I still had is whether to allow custom descriptions in work sessions. Currently you only can customize a link, which looks like this:21:22
ttxhttp://sched.co/2wp821:22
ttxThat may be a bit impractical for design summit attendees (having to click the link to see what the work session is actually about)21:23
*** dflorea has joined #openstack-meeting21:23
*** adahms has joined #openstack-meeting21:23
ttxIt's a balance between making it unattractive to conference attendees and making it a pain to design summit attendees21:23
*** otter768 has joined #openstack-meeting21:23
*** xingchao_ has quit IRC21:23
ttxSo maybe boring title is enough and we should allow custom descriptions for work sessions ? What would be your take ?21:23
morganfainbergI'd allow a link to an etherpad, add a boring description "see etherpad for me"21:23
morganfainberg"more"*21:23
asalkeldmaybe a very short description?21:23
*** e0ne has quit IRC21:23
asalkeldas a reminder21:23
ttxmorganfainberg: that is what we have for work sessions right now21:23
*** annegentle has joined #openstack-meeting21:23
SergeyLukjanov++ for very short description asalkeld21:24
tchaypoFWIW it seems like it should be possible to work around some of this by creating an etherpad for “here are our project’s work sessions” and putting descriptions there21:24
*** atiwari has joined #openstack-meeting21:24
*** david-lyle has quit IRC21:24
ttxgeneric description looks like  http://sched.co/2wp821:24
tchaypopossible, but slightly annoying21:24
*** mscohen has joined #openstack-meeting21:24
morganfainbergttx, i'm a fan of that. it means that it's easy to change the work session topic if suddenly everyone is busy elsewhere for that topic21:24
bknudsonthe work group titles are hopefully going to have the project name ?21:24
ttxthat basically means you need to train your teams to click on the etherpads21:24
morganfainbergttx, i'd rather just keep the boring description and the link.21:24
serg_melikyanI think it's pretty nice - at the end working session are for contributors and they know what they plan to discuss21:25
morganfainbergbut i'm not going to vote strongly against a short description21:25
*** ibiris is now known as ibiris_away21:25
ttxso let's do a quick poll21:25
*** _nadya_ has quit IRC21:25
asalkeld(was just thinking if you are on a phone, short description is nice)21:26
*** peristeri has quit IRC21:26
ttx#startmeeting should work sessions have custom descriptions, or just a boring description and a link ? custom, boring, don't care21:26
openstackttx: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.21:26
ttx#startvote should work sessions have custom descriptions, or just a boring description and a link ? custom, boring, don't care21:26
openstackBegin voting on: should work sessions have custom descriptions, or just a boring description and a link ? Valid vote options are custom, boring, don, t, care.21:26
openstackVote using '#vote OPTION'. Only your last vote counts.21:26
morganfainberg#vote boring21:26
eglynn#vote custom21:26
david-lyle_#vote boring21:26
notmyname#vote custom21:26
*** SumitNaiksatam has quit IRC21:26
edleafe#vote boring21:26
mestery#vote boring21:26
*** jgrimm is now known as zz_jgrimm21:26
asalkeld#vote custom21:26
*** mscohen has quit IRC21:26
morganfainbergactually... if we can just have it default to boring, and allow an override...21:26
nikhil_k#vote custom21:27
morganfainbergi think that solves the use for everyone21:27
mesterymorganfainberg: ++21:27
david-lyle_morganfainberg, +121:27
ttxhmm, yes.21:27
ttx#endvote21:27
openstackVoted on "should work sessions have custom descriptions, or just a boring description and a link ?" Results are21:27
openstackboring (4): david-lyle_, edleafe, mestery, morganfainberg21:27
*** dflorea has quit IRC21:27
openstackcustom (4): nikhil_k, eglynn, notmyname, asalkeld21:27
ttxLet's make it custom, but encourage boring21:27
mesterylol21:27
morganfainberg;)21:27
ttxyou can come with your own flavor of boring21:27
morganfainbergi like it!21:27
asalkeldhaha21:27
eglynnI wouldn't like to see "boring" used as a means of realtime rescheduling of sessions21:27
*** otter768 has quit IRC21:27
mesteryA tie ... but it doesn't matter anywya because morganfainberg had a better solution :)21:27
ttxthe vote was a rhetorical trick21:28
eglynn(hard enough to manage the clashes between multiple tracks in parallel)21:28
morganfainberg"this is a boring work session, don't come here... we're going to be quiet and not doing performance art... we swear... and definitely not docker"21:28
eglynnLOL :)21:28
david-lyle_haha21:28
mesteryNo! You said Docker! ;)21:28
eglynnopen the floodgates!21:28
bknudsonput a sign that says docker on a room.21:28
morganfainbergLOL21:29
ttx"10 things you won't believe about Docker"21:29
sdaguewe just need that nfv docker honeypot session21:29
morganfainbergttx, this one amazing trick about docker...21:29
mestery"Docker and OpenStack: Better Together!"21:29
* morganfainberg apologizes for derailing21:29
mesterylol21:29
mesterysdague: lol21:29
anteayasdague: in another building21:29
ttxOh, and Cheddar (the sched proxy) also supports a session showing up in multiple tracks!21:29
dansmithI bet those folks are as easy to trap as ... LEMMINGS21:29
* dansmith runs21:30
ttxSo it has a main track, but you may also make it appear in other tracks21:30
mikaldansmith: lol21:30
morganfainbergoh thats cool.21:30
ttxexample at:21:30
mesterylol21:30
*** atiwari has quit IRC21:30
ttxhttp://sched.co/2vhQ21:30
*** atiwari has joined #openstack-meeting21:31
ttxThat's an Ops session, but it also appears in swift21:31
notmynamenice. swift + cake == awesome21:31
ttxso that when your contributor go to: http://testingsiteforfutureevents2015.sched.org/type/design+summit/Swift they still see it21:31
*** pritesh_ has joined #openstack-meeting21:31
ttxThat should facilitate multi-project work21:31
* devananda sneaks in, tries to catch up on scrollback21:31
russellbdevananda: well that's not sneaky at all21:32
mesterydevananda: Summary is: NFV Docker honeypot!21:32
ttxIf someone wants to beta-test Cheddar, I can set up access to the demo instance21:32
ttxjust send me some email so that I remember to do it21:32
ttxAlright, any question on design summit ?21:33
asalkeldall good, thanks ttx21:33
ttx#topic Open discussion & announcements21:33
*** openstack changes topic to "Open discussion & announcements (Meeting topic: crossproject)"21:33
ttxWe had 1:1s syncs today in #openstack-relmgr-office, logs at:21:34
eglynnttx: is there a list of the per-project slot allocations anywhere?21:34
*** asselin has joined #openstack-meeting21:34
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-31-08.04.html21:34
devanandattx: i would have voted boring :)21:34
sdaguettx: for open discussion, question on string freeze and string freeze exceptions21:34
*** pritesh has quit IRC21:34
ttxeglynn: not yet, but the google doc I colected answers on is still up21:34
sdaguewhen we need to change a string for bugs at this point, what are we supposed to do to alert i18n teams21:34
*** samueldmq has quit IRC21:34
eglynnttx: a-ha, cool, ta21:34
nikhil_kttx: What seem to be the community plan for the smaller release cycle in L?21:35
*** dprince has quit IRC21:35
ttxsdague: so that is a good question21:35
nikhil_kto be community's general plan*21:35
*** SlickNik has joined #openstack-meeting21:35
ttxsdague: we generally do a thread on -dev, but I have no idea if that reaches the right people21:35
*** mwagner_lap has quit IRC21:35
morganfainbergsdague. we should do a i18nImpact  tag?21:35
devanandattx: i ma have missed it in my skim - is the ops track taking suggestions and/or having project-specific discussions?21:35
sdagueyeh, this seems like a very non closed loop, as I never have any idea what the i18n progress is21:36
ttxActually, I have no evidence that string freeze exceptions get seen by translators21:36
morganfainbergttx, i use the i18n mailing list.21:36
morganfainbergttx, got a response from andreas about it.21:36
ttxI know they appreciate us not gratuitously changing strings after FF, but that's about all the feedback I got21:36
sdaguemorganfainberg: there's a separate mailing list?21:36
morganfainbergttx, so that seems to work.21:36
morganfainbergsdague, yes.21:36
*** dflorea has joined #openstack-meeting21:36
*** sreshetn1 has quit IRC21:36
* mestery didn't know of the separate ML either21:36
Rockygdevananda: there's an etherpad for ops21:36
*** balajiiyer has left #openstack-meeting21:36
*** dkranz has quit IRC21:36
* morganfainberg has had to do this a few times in the past.21:36
devanandaRockyg: link isn't on https://wiki.openstack.org/wiki/Design_Summit/Planning yet :)21:36
* devananda adds ironic to ^21:37
morganfainbergopenstack-i18n@lists.openstack.org21:37
sdaguettx: so it seems like it would be good to get i18n leadership to be banging appropriate drums on -dev list around this21:37
* Rockyg is looking21:37
barrett1Here's the etherpad for the Ops topics:   https://etherpad.openstack.org/p/YVR-ops-meetup21:37
ttxsdague: yes21:37
sdaguebecause otherwise we're just going to fail a lot21:37
*** dflorea has quit IRC21:38
Rockygops summit ether pad:  #link https://etherpad.openstack.org/p/YVR-ops-meetup21:38
morganfainbergwe tend to be good w/ closes-bug, and docimpact (not as good as closes bug), so maybe a tag in the commit message is the right approach... maybe it's just a bad idea as well.21:38
ttxmorganfainberg: you seem to know your way around there, care to introduce that topic ?21:38
*** asselin has quit IRC21:38
*** dflorea has joined #openstack-meeting21:38
*** sdake has joined #openstack-meeting21:38
ttxwe just ened to make sure the i18n leadership shows up21:39
morganfainbergttx, uhm.. what needs to be introduced? or you mean for a session?21:39
sdaguemorganfainberg: we need to know what to do now21:39
ttxno I mean <sdague> ttx: so it seems like it would be good to get i18n leadership to be banging appropriate drums on -dev list around this21:39
sdagueon -dev21:39
ttxmorganfainberg: you seem to know who to reach to21:39
morganfainbergsdague, i mean i'll bug andraes and send a message to the i18n list :)21:40
ttxi18n is a black box to me. To reach it I usually dial fifieldt21:40
sdagueyou even knew there was a list21:40
*** thumpba_ has joined #openstack-meeting21:40
sdaguemorganfainberg: so I think the point is this needs to be on -dev21:40
sdaguebecause few people know that list is a thing21:40
sdagueso clearly won't be getting info out to the review teams that need it21:40
morganfainbergsdague, right, the point is getting them in on the convo.21:40
ttxand the current process involved [stringfreeze] on dev list21:40
*** maishsk_ has quit IRC21:40
morganfainbergttx, oh i didn't know that :P21:40
*** thumpba has quit IRC21:40
sdaguettx: ok, news to me21:40
* morganfainberg did something totally different.21:41
ttxwell, that is what I replied to people who asked me21:41
morganfainbergso i'll try and chase someone (some i18n folks) down and get them to make some noise on -dev about.21:41
ttxnot sure that qualifies as "process"21:41
morganfainbergnot guarantees that i'll be successful.21:41
*** thumpba has joined #openstack-meeting21:41
morganfainbergbut i'll try21:41
sdaguewhen we get to these parts of the release I think the [all] emails need to go out with "x is frozen, to get an except do Y"21:41
morganfainbergthe only way i knew someone read i18n list is because someone responded this time (i think this is the 4th or 5th string freeze i've sent out)21:42
sdaguebecause there has been a ton of confusion with code review where everyone's trying to guess the rules21:42
morganfainbergsdague, ++ i'll chase some people down and get them to send something to -dev.21:42
ttxsdague: but but but difference in culture is good right ?21:42
sdaguewhich means they are so inconsistently applied, it's not clear they are useful at all21:42
*** sdake__ has quit IRC21:42
* sdague walks away slowly21:42
morganfainbergsdague, at least we have some direction then.21:42
*** dflorea has quit IRC21:43
*** david-lyle_ is now known as david-lyle21:43
sdaguemorganfainberg: yep, thanks21:43
ttxmorganfainberg: thx!21:43
ttxnikhil_k: you had a question ?21:43
*** slong has joined #openstack-meeting21:44
*** serg_melikyan has quit IRC21:44
nikhil_kttx: What seems to be community's general plan for the smaller release cycle in L?21:44
*** pritesh_ has quit IRC21:44
ttxnikhil_k: I don't think we'll do a smaller release cycle in L21:44
ttxbut we'll dsicuss release cycle lengths in Vancouver21:44
nikhil_kso not 6 weeks then?21:45
nikhil_kThere was some proposal for abandoning older PS21:45
*** thumpba_ has quit IRC21:45
* fungi votes for a 6-minute release cycle21:45
ttxwell, the cycle will still be 6 months. You may release more often though21:45
bknudsonwe'll run out of letters.21:45
ttxnikhil_k: don't believe everything you read on MLs21:45
nikhil_kI thought the rhythm matches well with our 6 weeks style21:45
* morganfainberg believes everything on the internet21:45
fungii really didn't get the impression that the "release more often but less thoroughly" discussion really went anywhere except in a circle back to describing why we have milestones that aren't releases21:46
david-lylewe could use Liberty, Lemming and Lizard21:46
nikhil_kttx: I kinda like that idea :)21:46
nikhil_k(of abandoning older PS)21:46
morganfainbergdavid-lyle, and love. don't forget love21:46
morganfainberg>.>21:46
ttxAll you need is Love21:46
mikalAll I need is a nap21:46
ttxnikhil_k: I'll invite you to that session :)21:47
ttxOK... Anything else, anyone ?21:47
morganfainbergttx, does that mean we move to semver?21:47
morganfainbergttx, releasing more often that is?21:48
morganfainbergor is that just a rabbit hole not worth talking about right now21:48
nikhil_kmikal: http://www.tumblr.com/tagged/i-need-a-nap21:48
*** dflorea has joined #openstack-meeting21:48
david-lylewhere are cross-project session topics being collected?21:48
ttxmorganfainberg: rabbit hole21:48
ttxdavid-lyle: nowhere yet21:48
morganfainbergttx, sold. happy to merrily go on my way21:48
nikhil_kttx: heh21:48
ttxdavid-lyle: the etherpad ended up a bit messy last time21:48
ttxrussellb: ^21:48
russellbwe need to get started on that soon21:49
*** slong_ has joined #openstack-meeting21:49
ttxI was wondering if we should not use something less messy, like ODSREG of some google form21:49
russellbone problem was that we started kinda late, IIRC21:49
*** ivar-laz_ has quit IRC21:49
russellbttx: that too, yes21:49
russellbsubmission by completely freeform text is kind of difficult21:49
ttxworks well for teams brainstorming, not so much for random individuals posting21:50
david-lylehow many cross-project tracts concurrently running?21:50
russellbyeah21:50
ttxlet me see21:50
russellbis it a cross project day again?21:50
ttx2 sessions in parallel21:50
ttxyes, Tuesday21:50
russellbok21:50
david-lyleok21:50
russellbODSREG is fine with me21:50
ttxOps track runs in parallel though21:51
ttxso we'll have to choose where to go21:51
*** erlon has quit IRC21:51
*** stevemar has quit IRC21:51
russellbusually the case ..21:51
*** slong has quit IRC21:51
ttxright21:51
russellblet's just add more days!21:51
* russellb headdesks21:51
*** JRobinson__ has joined #openstack-meeting21:51
russellbi think i might collapse21:52
russellbok so, cross-project track.  we should do somethign about that.21:52
ttxOK, I think we are done for today, unless someone has a last-minute question/topic21:52
russellbttx: ODSREG++21:52
ttxrussellb: ok, will set up an instance for cross-project21:52
russellbawesome21:52
ttxnotmyname asked for one for swift too21:52
*** markvan has quit IRC21:52
ttxnotmyname: still interested ?21:53
notmynameyes, i think so21:53
notmynameI prefer it to etherpads21:53
ttxnotmyname: some people use Google forms21:53
ttxnotmyname: maybe discuss with team and let me know what you need21:53
notmynameok21:53
russellbwould be nice if it was consistent21:54
russellboh well21:54
*** MaxV has quit IRC21:54
ttxok, let's close this21:54
*** markvan has joined #openstack-meeting21:54
ttx#endmeeting21:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:54
openstackMeeting ended Tue Mar 31 21:54:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-31-21.02.html21:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-31-21.02.txt21:54
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-31-21.02.log.html21:54
mesterythanks ttx!21:54
ttxThanks everyone21:54
*** auld has left #openstack-meeting21:54
*** eglynn has quit IRC21:55
*** barrett1 has left #openstack-meeting21:55
*** padkrish has quit IRC21:56
*** padkrish has joined #openstack-meeting21:57
*** pritesh has joined #openstack-meeting21:57
*** baoli has quit IRC21:58
*** eugene_bag has quit IRC21:58
*** baoli has joined #openstack-meeting21:58
*** sdake_ has joined #openstack-meeting21:59
*** jruano has quit IRC22:00
*** prashant_ has joined #openstack-meeting22:00
*** slong__ has joined #openstack-meeting22:00
*** slong_ has quit IRC22:01
*** amitgandhinz has quit IRC22:01
*** padkrish has quit IRC22:01
*** david-lyle has quit IRC22:02
*** fzdarsky|afk has quit IRC22:02
*** sdake has quit IRC22:03
*** rhe00_ has joined #openstack-meeting22:03
*** igordcard_ has joined #openstack-meeting22:03
*** prashantS has quit IRC22:03
*** nelsnelson has quit IRC22:04
*** pritesh has quit IRC22:04
*** harlowja_ is now known as harlowja_away22:04
*** prashant_ has quit IRC22:04
*** absubram has quit IRC22:05
*** bvandenh has quit IRC22:06
*** thinrichs has quit IRC22:07
*** harlowja_away is now known as harlowja_22:07
*** VW_ has quit IRC22:09
*** salv-orl_ has quit IRC22:09
*** neelashah has quit IRC22:12
*** salv-orlando has joined #openstack-meeting22:13
*** dflorea has quit IRC22:14
*** SumitNaiksatam has joined #openstack-meeting22:14
*** dflorea has joined #openstack-meeting22:14
*** slong__ has quit IRC22:14
*** mtanino has joined #openstack-meeting22:15
*** pritesh has joined #openstack-meeting22:15
*** slong has joined #openstack-meeting22:16
*** jwang_ has joined #openstack-meeting22:17
*** jlvillal_ has joined #openstack-meeting22:19
*** thumpba has quit IRC22:20
*** jwang__ has quit IRC22:21
*** xingchao_ has joined #openstack-meeting22:21
*** harlowja_ has quit IRC22:21
*** kzaitsev has joined #openstack-meeting22:22
*** penick has quit IRC22:23
*** asettle has joined #openstack-meeting22:23
*** bernardo-silva has quit IRC22:23
*** bernardo-silva has joined #openstack-meeting22:24
*** JRobinson__ has left #openstack-meeting22:25
*** JRobinson__ has joined #openstack-meeting22:25
*** eugene_bag has joined #openstack-meeting22:26
*** harlowja has joined #openstack-meeting22:26
*** sorrison has left #openstack-meeting22:27
*** xingchao_ has quit IRC22:27
*** kzaitsev has quit IRC22:28
*** kzaitsev has joined #openstack-meeting22:28
*** bernardo-silva has quit IRC22:28
*** ayoung has quit IRC22:29
*** carl_baldwin has quit IRC22:31
*** penick has joined #openstack-meeting22:31
*** carl_baldwin has joined #openstack-meeting22:32
*** sreshetn1 has joined #openstack-meeting22:33
*** johnpur has joined #openstack-meeting22:34
*** padkrish has joined #openstack-meeting22:35
*** jecarey has quit IRC22:35
*** timcline has quit IRC22:35
*** kzaitsev has quit IRC22:35
*** weshay has quit IRC22:35
*** sreshetn1 has quit IRC22:37
*** Rockyg has quit IRC22:37
*** jlvillal_ has quit IRC22:38
*** annegentle has quit IRC22:38
*** ebalduf has joined #openstack-meeting22:38
*** aepifanov has quit IRC22:40
*** dflorea has quit IRC22:41
*** dflorea has joined #openstack-meeting22:41
*** agentle_ has joined #openstack-meeting22:41
*** annegentle has joined #openstack-meeting22:41
*** sigmavirus24 is now known as sigmavirus24_awa22:42
*** ebalduf has quit IRC22:42
*** prashantS has joined #openstack-meeting22:43
*** marcusvrn has quit IRC22:43
*** andreykurilin_ has joined #openstack-meeting22:45
*** dflorea has quit IRC22:46
*** agentle_ has quit IRC22:47
*** marcusvrn has joined #openstack-meeting22:47
*** rbak has quit IRC22:47
*** jlvillal_ has joined #openstack-meeting22:48
*** prashantS has quit IRC22:49
*** jlvillal_ has quit IRC22:49
*** prashantS has joined #openstack-meeting22:49
*** prashantS has quit IRC22:50
*** devlaps has joined #openstack-meeting22:50
*** prashantS has joined #openstack-meeting22:50
*** henrynash has quit IRC22:51
*** salv-orlando has quit IRC22:51
*** devlaps1 has joined #openstack-meeting22:53
*** banix has joined #openstack-meeting22:53
*** prashantS has quit IRC22:54
*** devlaps has quit IRC22:54
*** devlaps1 has quit IRC22:54
*** prashantS has joined #openstack-meeting22:55
*** devlaps has joined #openstack-meeting22:55
*** salv-orlando has joined #openstack-meeting22:59
*** darrenc is now known as darrenc_afk22:59
*** prashantS has quit IRC22:59
*** flwang has quit IRC23:00
*** eugene_bag has quit IRC23:00
*** _amrith_ is now known as amrith23:01
*** mattgriffin has quit IRC23:03
*** claudiub has quit IRC23:04
*** tsekiyam_ has joined #openstack-meeting23:04
*** baoli has quit IRC23:05
*** thedodd has quit IRC23:07
*** pritesh_ has joined #openstack-meeting23:07
*** tsekiyama has quit IRC23:07
*** dflorea has joined #openstack-meeting23:08
*** tsekiyam_ has quit IRC23:08
*** jaypipes has quit IRC23:09
*** ijw has joined #openstack-meeting23:10
*** ijw has quit IRC23:10
*** pritesh has quit IRC23:10
*** pritesh_ has quit IRC23:11
*** igordcard_ has quit IRC23:13
*** annegentle has quit IRC23:13
*** flwang has joined #openstack-meeting23:13
*** dims_ has quit IRC23:14
*** atiwari1 has joined #openstack-meeting23:16
*** dims_ has joined #openstack-meeting23:17
*** pritesh has joined #openstack-meeting23:17
*** atiwari has quit IRC23:18
*** jichen has quit IRC23:18
*** IanGovett has quit IRC23:20
*** carl_baldwin has quit IRC23:20
*** mwagner_lap has joined #openstack-meeting23:21
*** petertr7 has quit IRC23:21
*** Sukhdev has quit IRC23:22
*** marun has quit IRC23:22
*** darrenc_afk is now known as darrenc23:22
*** jaypipes has joined #openstack-meeting23:23
*** otter768 has joined #openstack-meeting23:24
*** hichihara has joined #openstack-meeting23:24
*** asettle has quit IRC23:24
*** xingchao_ has joined #openstack-meeting23:27
*** otter768 has quit IRC23:28
*** aranjan has joined #openstack-meeting23:29
*** melwitt has quit IRC23:30
*** tongli has quit IRC23:30
*** thinrichs has joined #openstack-meeting23:31
*** andreykurilin_ has quit IRC23:31
*** padkrish has quit IRC23:32
*** xingchao_ has quit IRC23:33
*** padkrish has joined #openstack-meeting23:33
*** penick has quit IRC23:33
*** unicell has quit IRC23:34
*** sreshetn1 has joined #openstack-meeting23:34
*** unicell has joined #openstack-meeting23:34
*** padkrish_ has joined #openstack-meeting23:34
*** padkrish has quit IRC23:37
*** changbl has joined #openstack-meeting23:38
*** sreshetn1 has quit IRC23:38
*** noslzzp has quit IRC23:39
*** achanda has quit IRC23:41
*** tochi has joined #openstack-meeting23:43
*** hemna is now known as hemnafk23:45
*** dflorea has quit IRC23:48
*** marrusl has quit IRC23:48
*** dflorea has joined #openstack-meeting23:49
*** sridhar_ram has quit IRC23:51
*** zhhuabj has quit IRC23:51
*** dflorea has quit IRC23:53
*** dannywilson has quit IRC23:54
*** wicope has quit IRC23:54
*** kebray has quit IRC23:54
*** achanda has joined #openstack-meeting23:55
*** smccully has quit IRC23:56
*** smccully_ has quit IRC23:57
*** ayoung has joined #openstack-meeting23:57
*** thinrichs has quit IRC23:58

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