Tuesday, 2015-02-24

*** rbak has quit IRC00:02
*** ijw has joined #openstack-meeting00:02
*** sarob has joined #openstack-meeting00:04
*** thomasem has quit IRC00:05
*** melwitt has joined #openstack-meeting00:05
*** penick has joined #openstack-meeting00:06
*** sbalukoff has joined #openstack-meeting00:07
*** lpmulligan has quit IRC00:07
*** dims has quit IRC00:08
*** marcusvrn has quit IRC00:08
*** thomasem has joined #openstack-meeting00:10
*** baoli has joined #openstack-meeting00:13
*** dneary has quit IRC00:13
*** amitgandhinz has joined #openstack-meeting00:15
*** Apoorva_ has quit IRC00:17
*** Apoorva has joined #openstack-meeting00:17
*** sarob has quit IRC00:22
*** tsekiyam_ has joined #openstack-meeting00:24
*** Apoorva_ has joined #openstack-meeting00:25
*** dmacpher has joined #openstack-meeting00:26
*** yamamoto_ has quit IRC00:26
*** ebalduf has joined #openstack-meeting00:28
*** VW_ has quit IRC00:28
*** tsekiyama has quit IRC00:28
*** VW_ has joined #openstack-meeting00:28
*** Apoorva has quit IRC00:28
*** nelsnelson has quit IRC00:29
*** jhesketh has quit IRC00:31
*** jhesketh has joined #openstack-meeting00:32
*** aranjan has quit IRC00:32
*** marcusvrn has joined #openstack-meeting00:32
*** ebalduf has quit IRC00:32
*** aranjan has joined #openstack-meeting00:34
*** aranjan_ has joined #openstack-meeting00:38
*** aranjan has quit IRC00:38
*** VW_ has quit IRC00:39
*** Apoorva_ has quit IRC00:40
*** erlon has quit IRC00:41
*** Apoorva has joined #openstack-meeting00:41
*** dims has joined #openstack-meeting00:42
*** mtanino has joined #openstack-meeting00:42
*** asselin_ has joined #openstack-meeting00:43
*** VW_ has joined #openstack-meeting00:44
*** ibiris is now known as ibiris_away00:45
*** amitgandhinz has quit IRC00:47
*** marun has joined #openstack-meeting00:47
*** niclem has quit IRC00:48
*** asselin_ has quit IRC00:48
*** DaveJ__ has quit IRC00:50
*** zul has quit IRC00:51
*** zul has joined #openstack-meeting00:52
*** yamamoto has joined #openstack-meeting00:53
*** ChuckC has quit IRC00:56
*** dannywil_ has quit IRC00:57
*** IanGovett has quit IRC00:57
*** RudWolf_ has joined #openstack-meeting00:59
*** MaxV has joined #openstack-meeting01:00
*** lpmulligan has joined #openstack-meeting01:00
*** MaxV has quit IRC01:05
*** RudWolf_ has quit IRC01:05
*** MaxV has joined #openstack-meeting01:06
*** baoli has quit IRC01:07
*** atiwari has quit IRC01:07
*** penick has quit IRC01:07
*** ayoung has joined #openstack-meeting01:09
*** MaxV has quit IRC01:09
*** adam_g is now known as adam_g_out01:09
*** MaxV has joined #openstack-meeting01:09
*** sigmavirus24 is now known as sigmavirus24_awa01:10
*** SridharRamaswamy has quit IRC01:10
*** rmoe has quit IRC01:10
*** devlaps has quit IRC01:11
*** melwitt has quit IRC01:14
*** ddieterly has joined #openstack-meeting01:15
*** hemna is now known as hemnafk01:17
*** MaxV has quit IRC01:18
*** thomasem has quit IRC01:18
*** david-lyle is now known as david-lyle_afk01:19
*** MaxV has joined #openstack-meeting01:19
*** baoli has joined #openstack-meeting01:19
*** rfolco has quit IRC01:19
*** MaxV has quit IRC01:20
*** rfolco has joined #openstack-meeting01:20
*** MaxV has joined #openstack-meeting01:20
*** achanda has quit IRC01:21
*** garthb_ has quit IRC01:21
*** garthb has quit IRC01:21
*** radez_g0n3 is now known as radez01:22
*** otter768 has joined #openstack-meeting01:24
*** rmoe has joined #openstack-meeting01:25
*** etoews has joined #openstack-meeting01:26
*** MaxV has quit IRC01:27
*** MaxV has joined #openstack-meeting01:28
*** ebalduf has joined #openstack-meeting01:28
*** otter768 has quit IRC01:28
*** JRobinson__ has quit IRC01:29
*** MaxV has quit IRC01:31
*** MaxV has joined #openstack-meeting01:31
*** ebalduf has quit IRC01:33
*** MaxV_ has joined #openstack-meeting01:33
*** VW_ has quit IRC01:33
*** MaxV__ has joined #openstack-meeting01:35
*** MaxV has quit IRC01:36
*** novas0x2a|laptop has quit IRC01:36
*** bill_az has quit IRC01:36
*** Mandell_ has quit IRC01:36
*** bdpayne has quit IRC01:37
*** MaxV_ has quit IRC01:37
*** MaxV has joined #openstack-meeting01:37
*** MaxV has quit IRC01:38
*** MaxV has joined #openstack-meeting01:39
*** watanabe_isao has quit IRC01:39
*** cdub has quit IRC01:39
*** noelbk has quit IRC01:39
*** MaxV__ has quit IRC01:39
*** MaxV has quit IRC01:42
*** otter768 has joined #openstack-meeting01:42
*** MaxV has joined #openstack-meeting01:42
*** Mandell has joined #openstack-meeting01:43
*** krtaylor has quit IRC01:43
*** novas0x2a|laptop has joined #openstack-meeting01:43
*** MaxV has quit IRC01:43
*** MaxV has joined #openstack-meeting01:44
*** MaxV has quit IRC01:45
*** MaxV has joined #openstack-meeting01:46
*** Mandell has quit IRC01:46
*** ijw has quit IRC01:48
*** asselin_ has joined #openstack-meeting01:48
*** tsekiyam_ has quit IRC01:48
*** tiswanso has joined #openstack-meeting01:49
*** aranjan_ has quit IRC01:49
*** MaxV has quit IRC01:49
*** asselin_ has quit IRC01:49
*** MaxV has joined #openstack-meeting01:50
*** jecarey has quit IRC01:50
*** amitgandhinz has joined #openstack-meeting01:51
*** MaxV has quit IRC01:53
*** MaxV has joined #openstack-meeting01:53
*** tiswanso_ has joined #openstack-meeting01:53
*** adalbas has quit IRC01:55
*** gyee has quit IRC01:55
*** krtaylor has joined #openstack-meeting01:55
*** amitgandhinz has quit IRC01:56
*** tiswanso has quit IRC01:56
*** Murali has joined #openstack-meeting01:58
*** MaxV has quit IRC01:58
*** MaxV has joined #openstack-meeting01:59
*** balajiiyer has joined #openstack-meeting01:59
*** MaxV has quit IRC02:00
*** MaxV has joined #openstack-meeting02:01
*** MaxV has quit IRC02:02
*** Murali has quit IRC02:03
*** MaxV has joined #openstack-meeting02:04
*** MaxV has quit IRC02:04
*** balajiiyer has quit IRC02:04
*** MaxV has joined #openstack-meeting02:04
*** leeantho has quit IRC02:05
*** MaxV has quit IRC02:05
*** MaxV has joined #openstack-meeting02:06
*** cdub has joined #openstack-meeting02:06
*** lpmulligan has quit IRC02:07
*** Riddhi has quit IRC02:07
*** MaxV has quit IRC02:07
*** MaxV has joined #openstack-meeting02:08
*** otter768 has quit IRC02:09
*** MaxV has quit IRC02:11
*** MaxV has joined #openstack-meeting02:11
*** niclem has joined #openstack-meeting02:13
*** MaxV has quit IRC02:13
*** marun has quit IRC02:13
*** MaxV has joined #openstack-meeting02:13
*** dims has quit IRC02:14
*** asettle is now known as asettle-luncheon02:14
*** MaxV_ has joined #openstack-meeting02:15
*** MaxV has quit IRC02:19
*** xingchao has quit IRC02:19
*** xingchao has joined #openstack-meeting02:19
*** MaxV_ has quit IRC02:20
*** MaxV has joined #openstack-meeting02:21
*** SumitNaiksatam has quit IRC02:22
*** vivek-ebay has quit IRC02:22
*** MaxV has quit IRC02:22
*** MaxV has joined #openstack-meeting02:23
*** MaxV has quit IRC02:24
*** kebray has quit IRC02:24
*** MaxV has joined #openstack-meeting02:24
*** marun has joined #openstack-meeting02:25
*** markvoelker has quit IRC02:25
*** markvoelker has joined #openstack-meeting02:26
*** chandankumar has joined #openstack-meeting02:27
*** ebalduf has joined #openstack-meeting02:29
*** markvoelker has quit IRC02:30
*** MaxV has quit IRC02:33
*** MaxV has joined #openstack-meeting02:33
*** ebalduf has quit IRC02:34
*** carl_baldwin has quit IRC02:34
*** MaxV has quit IRC02:35
*** britthouser has joined #openstack-meeting02:35
*** MaxV has joined #openstack-meeting02:35
*** xingchao has quit IRC02:37
*** xingchao has joined #openstack-meeting02:37
*** MaxV has quit IRC02:38
*** britthou_ has quit IRC02:38
*** Riddhi has joined #openstack-meeting02:39
*** xingchao has quit IRC02:39
*** xingchao has joined #openstack-meeting02:39
*** MaxV_ has joined #openstack-meeting02:41
*** cdub has quit IRC02:45
*** kaisers1 has joined #openstack-meeting02:45
*** kaisers has quit IRC02:46
*** mestery has joined #openstack-meeting02:48
*** novas0x2a|laptop has quit IRC02:49
*** MaxV_ has quit IRC02:49
*** MaxV has joined #openstack-meeting02:50
*** MaxV has quit IRC02:55
*** MaxV has joined #openstack-meeting02:55
*** nelsnelson has joined #openstack-meeting02:55
*** carl_baldwin has joined #openstack-meeting02:56
*** MaxV has quit IRC02:56
*** chandankumar has quit IRC02:57
*** armax has quit IRC02:57
*** MaxV has joined #openstack-meeting02:57
*** MaxV has quit IRC02:58
*** MaxV has joined #openstack-meeting02:59
*** JRobinson__ has joined #openstack-meeting02:59
*** MaxV has quit IRC03:00
*** MaxV has joined #openstack-meeting03:01
*** sarob has joined #openstack-meeting03:01
*** unicell1 has quit IRC03:02
*** MaxV has quit IRC03:02
*** MaxV has joined #openstack-meeting03:02
*** sbalukoff has quit IRC03:05
*** yamahata has quit IRC03:06
*** markvoelker has joined #openstack-meeting03:08
*** Apoorva_ has joined #openstack-meeting03:08
*** paragan has joined #openstack-meeting03:09
*** paragan has joined #openstack-meeting03:09
*** kebray has joined #openstack-meeting03:10
*** Apoorva has quit IRC03:11
*** chandankumar has joined #openstack-meeting03:13
*** Apoorva_ has quit IRC03:13
*** MaxV has quit IRC03:13
*** MaxV has joined #openstack-meeting03:13
*** marcusvrn has quit IRC03:15
*** MaxV_ has joined #openstack-meeting03:15
*** ivar-laz_ has joined #openstack-meeting03:16
*** MaxV has quit IRC03:17
*** carl_baldwin has quit IRC03:18
*** rfolco has quit IRC03:19
*** ivar-lazzaro has quit IRC03:20
*** aepifanov has joined #openstack-meeting03:20
*** ivar-laz_ has quit IRC03:21
*** Sukhdev has joined #openstack-meeting03:21
*** armax has joined #openstack-meeting03:22
*** ddieterly has quit IRC03:23
*** carl_baldwin has joined #openstack-meeting03:23
*** aepifanov has quit IRC03:24
*** MaxV_ has quit IRC03:25
*** juhp has quit IRC03:26
*** armax has quit IRC03:26
*** MaxV has joined #openstack-meeting03:26
*** MaxV has quit IRC03:27
*** MaxV has joined #openstack-meeting03:28
*** ebalduf has joined #openstack-meeting03:30
*** etoews has quit IRC03:32
*** etoews has joined #openstack-meeting03:33
*** marun has quit IRC03:34
*** nelsnelson has quit IRC03:34
*** sarob has quit IRC03:34
*** ebalduf has quit IRC03:34
*** MaxV has quit IRC03:35
*** carl_baldwin has quit IRC03:37
*** etoews has quit IRC03:37
*** vivek-ebay has joined #openstack-meeting03:38
*** killer_prince has quit IRC03:40
*** amitgandhinz has joined #openstack-meeting03:40
*** etoews has joined #openstack-meeting03:41
*** oomichi has quit IRC03:41
*** niclem has quit IRC03:43
*** egallen has joined #openstack-meeting03:43
*** amitgandhinz has quit IRC03:45
*** AmirBaleghi has quit IRC03:46
*** tomoe_ has joined #openstack-meeting03:50
*** armax has joined #openstack-meeting03:50
*** kebray has quit IRC03:51
*** dmacpher has quit IRC03:52
*** fnaval has quit IRC03:52
*** kaisers1 has quit IRC03:52
*** Riddhi has quit IRC03:53
*** asettle-luncheon is now known as asettle03:53
*** dannywilson has joined #openstack-meeting03:53
*** stevemar has quit IRC03:55
*** amotoki has joined #openstack-meeting03:55
*** stevemar has joined #openstack-meeting03:55
*** claudiub has quit IRC03:56
*** balajiiyer has joined #openstack-meeting03:57
*** dannywilson has quit IRC03:57
*** Riddhi has joined #openstack-meeting03:58
*** dmacpher has joined #openstack-meeting03:59
*** aepifanov has joined #openstack-meeting04:00
*** armax has quit IRC04:02
*** fnaval has joined #openstack-meeting04:02
*** armax has joined #openstack-meeting04:03
*** Sukhdev has quit IRC04:04
*** watanabe_isao has joined #openstack-meeting04:06
*** narenhn has quit IRC04:09
*** britthouser has quit IRC04:09
*** nelsnelson has joined #openstack-meeting04:09
*** Apoorva has joined #openstack-meeting04:10
*** otter768 has joined #openstack-meeting04:10
*** harlowja is now known as harlowja_away04:14
*** otter768 has quit IRC04:14
*** harlowja_away is now known as harlowja04:15
*** devlaps has joined #openstack-meeting04:17
*** armax has quit IRC04:17
*** ajayaa has joined #openstack-meeting04:17
*** yatin has joined #openstack-meeting04:21
*** ddieterly has joined #openstack-meeting04:23
*** armax has joined #openstack-meeting04:23
*** radez is now known as radez_g0n304:24
*** sbalukoff has joined #openstack-meeting04:24
*** dmacpher has quit IRC04:25
*** dmacpher has joined #openstack-meeting04:25
*** xingchao has quit IRC04:25
*** Tross has quit IRC04:27
*** ajayaa has quit IRC04:28
*** chandankumar has quit IRC04:28
*** ddieterly has quit IRC04:29
*** neillc is now known as neillc_uni04:31
*** ebalduf has joined #openstack-meeting04:31
*** chandankumar has joined #openstack-meeting04:31
*** spzala has quit IRC04:31
*** fnaval has quit IRC04:33
*** imsurit has joined #openstack-meeting04:34
*** ebalduf has quit IRC04:35
*** garyh has quit IRC04:36
*** anish_ has joined #openstack-meeting04:37
*** xingchao has joined #openstack-meeting04:38
*** balajiiyer has quit IRC04:38
*** markvoelker has quit IRC04:39
*** markvoelker has joined #openstack-meeting04:39
*** egallen has quit IRC04:40
*** lpmulligan has joined #openstack-meeting04:42
*** ayoung has quit IRC04:43
*** markvoelker has quit IRC04:44
*** lpmulligan has quit IRC04:44
*** nelsnelson has quit IRC04:49
*** krtaylor has quit IRC04:55
*** AmirBaleghi has joined #openstack-meeting04:56
*** vivek-ebay has quit IRC04:58
*** armax has quit IRC05:00
*** ajayaa has joined #openstack-meeting05:04
*** killer_prince has joined #openstack-meeting05:05
*** killer_prince is now known as lazy_prince05:06
*** akuznetsov has joined #openstack-meeting05:06
*** krtaylor has joined #openstack-meeting05:07
*** armax has joined #openstack-meeting05:07
*** dmacpher has quit IRC05:09
*** SumitNaiksatam has joined #openstack-meeting05:09
*** SumitNaiksatam has quit IRC05:10
*** markvoelker has joined #openstack-meeting05:10
*** Watanabe has joined #openstack-meeting05:13
*** watanabe_isao has quit IRC05:14
*** aranjan has joined #openstack-meeting05:14
*** krtaylor has quit IRC05:14
*** jckasper has joined #openstack-meeting05:16
*** devlaps has quit IRC05:17
*** jckasper has quit IRC05:17
*** markvoelker has quit IRC05:17
*** jckasper has joined #openstack-meeting05:17
*** Riddhi has quit IRC05:17
*** MaxV has joined #openstack-meeting05:19
*** MaxV has quit IRC05:23
*** ddieterly has joined #openstack-meeting05:25
*** aepifanov has quit IRC05:25
*** Mandell has joined #openstack-meeting05:26
*** krtaylor has joined #openstack-meeting05:26
*** baoli has quit IRC05:27
*** etoews has quit IRC05:28
*** eghobo has joined #openstack-meeting05:29
*** ddieterly has quit IRC05:29
*** lazy_prince has quit IRC05:29
*** BharatK has joined #openstack-meeting05:30
*** killer_prince has joined #openstack-meeting05:31
*** killer_prince is now known as lazy_prince05:31
*** ebalduf has joined #openstack-meeting05:31
*** achanda has joined #openstack-meeting05:34
*** jrist is now known as jrist-afk05:35
*** ebalduf has quit IRC05:36
*** Murali has joined #openstack-meeting05:37
*** garyh has joined #openstack-meeting05:37
*** killer_prince has joined #openstack-meeting05:40
*** lazy_prince has quit IRC05:40
*** killer_prince is now known as lazy_prince05:40
*** chandankumar has quit IRC05:40
*** xingchao has quit IRC05:41
*** tomoe_ has quit IRC05:41
*** zehicle has quit IRC05:44
*** tiswanso has joined #openstack-meeting05:44
*** tomoe_ has joined #openstack-meeting05:45
*** ibiris_away is now known as ibiris05:46
*** tiswanso_ has quit IRC05:47
*** zehicle_ has quit IRC05:48
*** SridharRamaswamy has joined #openstack-meeting05:49
*** JRobinson__ has quit IRC05:50
*** tiswanso has quit IRC05:52
*** SridharRamaswam1 has joined #openstack-meeting05:53
*** SridharRamaswamy has quit IRC05:53
*** coolsvap_ is now known as coolsvap05:57
*** zehicle_ has joined #openstack-meeting05:58
*** ildikov has quit IRC06:00
*** irenab has joined #openstack-meeting06:01
*** etoews has joined #openstack-meeting06:02
*** otter768 has joined #openstack-meeting06:11
*** harlowja is now known as harlowja_away06:11
*** markvoelker has joined #openstack-meeting06:13
*** SridharRamaswamy has joined #openstack-meeting06:13
*** doude has quit IRC06:13
*** SridharRamaswam1 has quit IRC06:14
*** andreykurilin_ has joined #openstack-meeting06:14
*** otter768 has quit IRC06:15
*** markvoelker has quit IRC06:17
*** eghobo has quit IRC06:19
*** tomoe_ has quit IRC06:21
*** sdake__ has joined #openstack-meeting06:23
*** tomoe_ has joined #openstack-meeting06:24
*** chandankumar has joined #openstack-meeting06:25
*** MarkAtwood has joined #openstack-meeting06:25
*** ddieterly has joined #openstack-meeting06:26
*** sdake_ has quit IRC06:26
*** ddieterly has quit IRC06:30
*** SridharRamaswamy has quit IRC06:31
*** ebalduf has joined #openstack-meeting06:32
*** tomoe_ has quit IRC06:33
*** numan has joined #openstack-meeting06:34
*** sarob has joined #openstack-meeting06:35
*** tomoe_ has joined #openstack-meeting06:37
*** ebalduf has quit IRC06:37
*** eghobo has joined #openstack-meeting06:38
*** eghobo has quit IRC06:38
*** Mandell has quit IRC06:39
*** sarob has quit IRC06:39
*** BharatK has quit IRC06:40
*** BharatK has joined #openstack-meeting06:41
*** eghobo has joined #openstack-meeting06:41
*** pradipta has joined #openstack-meeting06:42
*** SridharG has joined #openstack-meeting06:43
*** andreykurilin_ has quit IRC06:44
*** tomoe_ has quit IRC06:44
*** reed has quit IRC06:45
*** tomoe_ has joined #openstack-meeting06:46
*** eghobo has quit IRC06:46
*** ildikov has joined #openstack-meeting06:46
*** adahms has quit IRC06:47
*** mrunge has joined #openstack-meeting06:47
*** eghobo has joined #openstack-meeting06:48
*** rushiagr_away is now known as rushiagr06:49
*** tomoe_ has quit IRC06:50
*** tomoe_ has joined #openstack-meeting06:51
*** akuznetsov has quit IRC06:52
*** lazy_prince has quit IRC06:54
*** irenab has quit IRC06:55
*** noslzzp has joined #openstack-meeting06:56
*** killer_prince has joined #openstack-meeting06:58
*** killer_prince is now known as lazy_prince06:58
*** sdake_ has joined #openstack-meeting06:58
*** tomoe_ has quit IRC06:59
*** tomoe_ has joined #openstack-meeting07:00
*** Apoorva has quit IRC07:00
*** sdake__ has quit IRC07:01
*** moha_hunt has joined #openstack-meeting07:03
*** jcoufal has joined #openstack-meeting07:03
*** etoews has quit IRC07:05
*** MaxV has joined #openstack-meeting07:07
*** doron_afk has joined #openstack-meeting07:09
*** MaxV has quit IRC07:12
*** xuhanp has joined #openstack-meeting07:17
*** neeti has joined #openstack-meeting07:18
*** xyang1 has quit IRC07:19
*** eghobo has quit IRC07:23
*** ddieterly has joined #openstack-meeting07:26
*** irenab has joined #openstack-meeting07:26
*** irenab has quit IRC07:27
*** irenab has joined #openstack-meeting07:27
*** aranjan has quit IRC07:30
*** ddieterly has quit IRC07:31
*** jcoufal_ has joined #openstack-meeting07:32
*** akuznetsov has joined #openstack-meeting07:33
*** ebalduf has joined #openstack-meeting07:33
*** jcoufal has quit IRC07:35
*** coolsvap is now known as coolsvap_07:36
*** ebalduf has quit IRC07:37
*** rajeshr has joined #openstack-meeting07:37
*** belmoreira has joined #openstack-meeting07:38
*** coolsvap_ is now known as coolsvap07:39
*** sdake_ has quit IRC07:40
*** FallenPegasus has joined #openstack-meeting07:41
*** rushiagr is now known as rushiagr_away07:42
*** sergef has joined #openstack-meeting07:42
*** scheuran has joined #openstack-meeting07:43
*** MarkAtwood has quit IRC07:44
*** FallenPegasus is now known as MarkAtwood07:44
*** sahid has joined #openstack-meeting07:44
*** akuznetsov has quit IRC07:44
*** fzdarsky has joined #openstack-meeting07:46
*** armax has quit IRC07:47
*** shengjiemin has joined #openstack-meeting07:48
*** e0ne has joined #openstack-meeting07:50
*** nshaikh has joined #openstack-meeting07:50
*** mrmartin has joined #openstack-meeting07:50
*** aepifanov has joined #openstack-meeting07:53
*** evgenyf has joined #openstack-meeting07:53
*** MarkAtwood has quit IRC07:56
*** dulek has joined #openstack-meeting07:59
*** vivek-ebay has joined #openstack-meeting07:59
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Feb 24 08:00:31 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
anteayaraise your hand if you are here for the third-party meeting08:00
*** unicell has joined #openstack-meeting08:01
*** akuznetsov has joined #openstack-meeting08:01
*** jcoufal has joined #openstack-meeting08:01
*** etoews has joined #openstack-meeting08:02
*** vivek-ebay has quit IRC08:03
*** pkoniszewski has joined #openstack-meeting08:04
*** VW_ has joined #openstack-meeting08:04
*** MaxV has joined #openstack-meeting08:04
*** jtomasek has joined #openstack-meeting08:05
*** jcoufal_ has quit IRC08:05
*** etoews has quit IRC08:06
*** ndipanov has joined #openstack-meeting08:08
*** aepifanov has quit IRC08:08
*** ttrifonov is now known as zz_ttrifonov08:09
*** luqas has joined #openstack-meeting08:09
*** otter768 has joined #openstack-meeting08:11
*** VW_ has quit IRC08:13
*** MaxV has quit IRC08:13
*** mrmartin has quit IRC08:13
*** luqas has quit IRC08:14
*** aepifanov has joined #openstack-meeting08:14
*** hichihara has quit IRC08:15
*** otter768 has quit IRC08:16
*** akuznetsov has quit IRC08:17
*** phil__ has joined #openstack-meeting08:21
*** imsurit has quit IRC08:21
*** matrohon has joined #openstack-meeting08:23
*** ddieterly has joined #openstack-meeting08:27
*** egallen has joined #openstack-meeting08:30
*** aranjan has joined #openstack-meeting08:30
*** ddieterly has quit IRC08:31
*** ebalduf has joined #openstack-meeting08:34
*** mpaolino has joined #openstack-meeting08:34
*** aranjan has quit IRC08:35
*** lpeer has joined #openstack-meeting08:36
*** dguitarbite has joined #openstack-meeting08:36
*** ebalduf has quit IRC08:38
*** enterprisedc has quit IRC08:39
*** oomichi_ has joined #openstack-meeting08:40
*** jlibosva has joined #openstack-meeting08:40
*** shankar has joined #openstack-meeting08:42
*** achanda has quit IRC08:42
*** zz_ttrifonov is now known as ttrifonov08:45
*** MaxV has joined #openstack-meeting08:45
*** jlanoux has joined #openstack-meeting08:45
*** achanda has joined #openstack-meeting08:49
*** bauzas has joined #openstack-meeting08:50
*** ajo has joined #openstack-meeting08:51
*** pnavarro has joined #openstack-meeting08:51
*** iymht has joined #openstack-meeting08:51
*** xingchao has joined #openstack-meeting08:53
*** vigneshvar has joined #openstack-meeting08:53
*** akuznetsov has joined #openstack-meeting08:53
*** iymht has quit IRC08:57
*** iymht has joined #openstack-meeting08:57
anteaya#endmeeting08:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:58
openstackMeeting ended Tue Feb 24 08:58:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-24-08.00.html08:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-24-08.00.txt08:58
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-24-08.00.log.html08:58
*** pradipta has quit IRC08:59
*** tomoe_ has quit IRC08:59
*** iymht has left #openstack-meeting08:59
anteaya#startmeeting nova-net-to-neutron-migration09:00
openstackMeeting started Tue Feb 24 09:00:03 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: nova-net-to-neutron-migration)"09:00
openstackThe meeting name has been set to 'nova_net_to_neutron_migration'09:00
anteayahello folks09:00
mikalHi09:00
obondarevo/09:00
anteayahey mikal obondarev09:00
*** jawed has joined #openstack-meeting09:00
anteayagus jlibosva ping09:00
anteayabelmoreira: hello09:00
jlibosvahi09:00
gushi09:00
anteayagreat09:00
anteayaour agenda: https://wiki.openstack.org/wiki/Meetings/Nova-nettoNeutronMigration09:01
anteayalet's get started09:01
anteaya#topic the state of the Neutron spec (obondarev)09:01
*** openstack changes topic to "the state of the Neutron spec (obondarev) (Meeting topic: nova-net-to-neutron-migration)"09:01
obondarevok, this one will be short :)09:01
anteayaI don't think anything has changed here from last week09:01
anteaya:)09:02
*** iymht has joined #openstack-meeting09:02
obondarevas there are no updates on the spec this week09:02
anteayagreat09:02
*** gilliard has left #openstack-meeting09:02
anteayaanyone have anything on the spec?09:02
gusnothing this week.09:02
*** iymht has quit IRC09:02
anteayawonderful09:02
anteayanext09:02
anteaya#topic the state of implementation (obondarev)09:02
*** openstack changes topic to "the state of implementation (obondarev) (Meeting topic: nova-net-to-neutron-migration)"09:02
obondarevok09:03
obondarevI saw new patchset on db migration from Jacub09:03
obondarevdidn't have a chance to review yet09:03
obondarevjlibosva: can you please give an update?09:03
anteaya#link https://review.openstack.org/#/c/148260/09:03
jlibosvayep09:03
jlibosvaso I tested the simplest case of migrating flat network09:04
jlibosvarealized that flat manager doesn't support floating ips09:04
*** yobber has quit IRC09:04
anteayais the patch in a state of non-crashing now?09:04
jlibosvano09:04
anteayaah09:04
jlibosvaShould be able to migrate flat network09:04
jlibosvaI obtained a dataset from real nnet deployment with vlans09:05
jlibosvaso I'm gonna do some test/debugging for vlan managers09:05
*** omrim has quit IRC09:05
anteayasorry I'm going to ask a stupid question09:05
* anteaya displays her ignorance09:05
anteayais vlan a flat manager?09:05
obondarevjlibosva: can you please add some test instructions to the patch (in a comment)09:05
jlibosvaobondarev: yeah, that would be good idea09:06
jlibosvaanteaya: vlan is a type of manager09:06
*** achanda has quit IRC09:06
*** armax has joined #openstack-meeting09:06
jlibosvathere are three in nova net09:06
anteayaokay09:06
jlibosvaflat, flatdhcp and vlan09:06
anteayaah ha09:06
anteayaokay so no vlan is not a flat manager09:06
anteayaso how do we solve the flat manager situation09:06
jlibosvaright09:06
*** VW_ has joined #openstack-meeting09:06
anteayaas that is the simplest, yes?09:06
jlibosvaflat manager is the simplest case09:06
jlibosvaright09:07
jlibosvaso I'm not sure if anyone is really using this type of manager09:07
anteayaso it sounds like we have solved that yet09:07
jlibosvaanyway this should be covered by script nowadays09:07
anteayahaven't09:07
mikalI would think its used in some private clouds09:07
anteayaif it is the simplest to solve, let's solve it09:07
anteayaso what do we need to solve it?09:07
jlibosvawell, as I said. I did some tests and it migrates successfully09:08
anteayaoh I thought you said it didn't09:08
mikalanteaya: this might be helpful by the way -- http://docs.openstack.org/admin-guide-cloud/content/section_networking-options.html09:08
*** rpodolyaka_afk is now known as rpodolyaka09:08
jlibosvadid I? maybe typo09:08
anteayaalso how did it migrate, as you said the patch still crashes09:08
anteayamikal: thanks :)09:08
jlibosvaanyway, I except to break it once I start implementing the other two :) as we don't have any testing yet09:09
jlibosvaanteaya: aaah, sorry09:09
anteayawe seem to hoping all over the place09:09
jlibosvamy bad, I read "is patch crashing?"09:09
anteayadoes this patchset cause a crash09:09
jlibosvaso no, the patch is not crashing09:09
anteayais the patch crashing?09:09
anteayaokay thank you09:09
jlibosvamy apologies09:09
*** pkoniszewski has quit IRC09:09
*** ygbo has joined #openstack-meeting09:09
anteayaand you have tested this patchset in a flat network migration?09:10
jlibosvaright, very small one09:10
anteayacan you post any kind of artifact for others to see that it worked?09:10
obondarevI think test instructions should be fine09:11
jlibosvayes, I can push some results somewhere, maybe gist09:11
anteayajlibosva: that will do09:11
anteayajust for someone else to take a look09:11
anteayaand have you been in contact with spadhe?09:11
anteayahas she had a chance to test your patch?09:11
jlibosvano, I haven't reached her last week09:12
anteayacan you try this week?09:12
*** jang has quit IRC09:12
anteayaand you are away for a month starting the end of this week, yes/09:12
jlibosvaanteaya: do you have her email address?09:12
anteayaI don't know, I will check09:13
jlibosvamaybe email correspondence will be more sufficient as we have 8 hrs TZ difference09:13
jlibosvaor 909:13
jlibosvaright, I'll be gone since Friday till April09:13
anteayano, I don't, do you mikal she was at the nova meetup09:13
anteayaokay so let's get this patchset in a state that it can be tested with flat networks for the month of march09:14
anteayaso post some artifacts and any tests you can come up with09:14
jlibosvawill do09:14
anteayaand then after you return we can work on getting it working with vlan09:14
anteayais that fair?09:14
mikalanteaya: sorry, who are we after?09:15
jlibosvaok, I was already working on vlan so I'll see what's missing after tests today. I got the dataset yesterday evening09:15
jlibosvamikal: spandhe09:15
anteayamikal a yahoo dev named spadhe09:15
mikalanteaya: do you know her real name, I can look her up09:15
*** jang has joined #openstack-meeting09:15
anteayagus: do you still have a link to her github account?09:15
*** zz_johnthetubagu is now known as johnthetubaguy09:15
gus(looking ..)09:15
anteayajlibosva: okay that is fine, I just want to make sure we are in a state where we can do something such as test while you are away09:16
jlibosvaI see09:16
mikalNo one by that name registered for the mid-cycle...09:16
anteayamikal: hmmm, I saw her there, shame she didn't register09:16
jlibosvamaybe https://launchpad.net/~shraddha-pandhe ?09:16
mikalOh wait, the eventbrite UI defeated me09:17
mikalPlease hold09:17
anteayajlibosva: I think that was it09:17
* anteaya imagines hold music09:17
*** xuhanp has quit IRC09:17
*** markvoelker has joined #openstack-meeting09:17
anteayaokay so hoping to test the db migration while jlibosva is away09:17
anteayaany more on the db migration patch?09:17
mikalNup, no one by that name09:17
anteayamikal: thanks for looking, markmcclain knows her so maybe he can help find her email09:18
anteayajlibosva: can you ask him?09:18
anteayaso let's move onto obondarev's patch09:18
mikalYeah, we could also ask Mel Witt if she knows this person09:18
anteayathat too09:18
obondarevok, moving to nova-net proxy09:18
jlibosvaanteaya: ack09:18
anteaya#link https://review.openstack.org/#/c/150490/09:18
anteayajlibosva: thanks09:18
obondarevwe had an irc conversation with dansmith on it09:18
*** SridharGaddam has joined #openstack-meeting09:19
obondarevI think we agreed that it won't be simpler and less messy to proxy at API level09:19
anteayawas taht in the nova channel or neutron?09:19
obondarevso his words were "I don't have any other suggestions other than "don't do it at all""09:19
*** Watanabe has quit IRC09:19
anteayaI could find the logs for it09:19
obondarevanteaya: nova channel09:19
anteayathanks I'll look again09:19
*** sdake_ has joined #openstack-meeting09:19
anteayaobondarev: don't do what at all, migrate?09:19
obondarevanteaya: proxy09:20
obondarevI guess he still has concerns regarding more complex cases with the approach I'm advocating09:20
anteayaso if we don't proxy, what do we do?09:20
anteayaand what day did this conversation take place?09:20
gusAha, found it (that took a while):09:20
gus#link https://github.com/shraddha-pandhe/Tools/tree/master/NovaNetToNeutronMigration09:20
anteayagus: awesome thank you09:20
*** derekh has joined #openstack-meeting09:20
obondarevanteaya: let me check..09:21
anteayaobondarev: thanks09:21
*** salv-orlando has joined #openstack-meeting09:21
anteayabecause I talked to dan at the nova meeting last week, so I am just trying to figure out who has the most recent information09:21
obondarevanteaya: it was after out conversation09:22
obondarevanteaya: I mean nova meeteng09:22
anteayaoh okay09:22
obondarevanteaya: I read the logs09:22
*** markvoelker has quit IRC09:22
anteayawell do finish your thought then09:22
anteayawhat do you want to do now?09:22
obondarevanteaya: probably the day before nova meeting09:22
anteayaokay thanks09:22
*** VW_ has quit IRC09:22
obondarevand I'm working on allocate_for_instance case now09:22
obondarevI think this is complex enough to serve some kind of proof09:22
obondarevthat the approach is working09:23
anteayawhen might you have something to offer to gerrit?09:23
obondarevI'm going to get it ready this week09:23
obondarevI'm sure I'll have much fun with testing :)09:23
jlibosvaobondarev: I think allocate_for_instance is being refactored, are you aware of that?09:23
anteayaat the nova meeting, I learned you had talked to dan (thank you for that) and that dan said you were going to offer something this week09:23
obondarevjlibosva: when did that happen?09:23
anteayawhich is great, so we agreed to look at what you offered and go from there09:24
jlibosvaobondarev: not sure, I talked with Brent ~2weeks ago and he said he was working on some refactoring09:24
jlibosvamaybe it will worth to sync with him09:24
obondarevjlibosva: thanks for the info, will look09:24
anteayaobondarev: might you have something by the end of today to look at on gerrit?09:25
obondarevanteaya: I think no09:25
anteayawe are slowing down in momentum, which is understandable since we are in k-3 and core reviewers are tied up with reviews on things that will get into this release09:25
obondarevas it will be part of work, no real value to look and try it09:25
anteayawell except to get feedback09:26
anteayaif you want to continue on this route that is fine09:26
anteayajust keep in mind that we soon need to make a decision if this is going to get into kilo or not09:26
anteayafor other people to make decisions on things09:26
obondarevanteaya: understood09:26
obondarevI'm also going to try Jacub's patch as well as part of testing09:27
anteayaright now it feels to me that it won't and we should just say so and focus on L09:27
anteayaobondarev: good idea09:27
*** neeti_ has joined #openstack-meeting09:27
anteayaare we ready as a group to say refocus on L?09:27
*** anish_ has quit IRC09:27
anteayait won't change what we are doing, we just need to communicate to others that care09:27
jlibosva+1 for L09:27
obondarevgiven that even db migration and proxy is only half of work I guess we can say so09:28
anteayagus: your thoughts?09:28
*** ddieterly has joined #openstack-meeting09:28
anteayahe got pulled away09:28
anteayaokay let's wait for him09:29
gusagree with the above - it will be too much of a stretch to make it into K09:29
anteayaokay L it is09:29
anteayamikal: you can help communicate that agreement?09:29
anteaya#agreed we will refocus on L release09:29
mikalSure09:29
anteayathanks09:29
mikalWe can put that on the agenda for the next nova meeting09:29
*** dguitarbite has quit IRC09:29
anteayaokay so obondarev when do you think you might have something to look at?09:29
anteayamikal: thanks09:30
*** ndipanov has quit IRC09:30
obondarevanteaya: by the next nova meeting?09:30
*** neeti has quit IRC09:30
anteayaobondarev: it would be nice to have something up prior to that09:30
obondarevanteaya: sorry, when will it be?09:30
*** ndipanov has joined #openstack-meeting09:30
anteayaso folks have had a chance to review before the meeting09:30
anteayathursday at 2100 I think09:31
anteayathe later of the two times09:31
mikalFor nova, yeah09:31
mikalIts the later version this week09:31
*** aranjan has joined #openstack-meeting09:31
*** doude has joined #openstack-meeting09:31
obondarevanteaya: ok, I'll update patch by thursday09:32
anteayaso obondarev please put something up as soon as you are able, so folks can look at it09:32
anteayaokay thank you09:32
anteayaanything more on implementation?09:32
*** ddieterly has quit IRC09:32
obondarevnot from my side09:32
anteayaokay next09:32
anteaya#topic documentation (emagana)09:32
*** openstack changes topic to "documentation (emagana) (Meeting topic: nova-net-to-neutron-migration)"09:32
anteayaedgar won't ever make the meetings09:33
anteayaI'm still looking for a docs person to help edgar who will attend meetings09:33
anteayain the mean time09:33
anteayathe doc patch that edgar has been working on09:33
anteaya#link https://review.openstack.org/#/c/15594709:33
anteayahas been put on hold09:33
anteayadocs team is moving from xml to rst09:34
anteayaand wonders if the patch has any use before the guide is published09:34
obondarevand at least the spec is not finished yet09:34
anteayamy main request was to have something for sdague to take to the ops mid-cycle09:34
*** stevemar has quit IRC09:34
obondarevwhich I guess is a blocker as well09:34
*** ebalduf has joined #openstack-meeting09:34
anteayabut he feels that he can use the spec which has been published so far09:35
anteayaI do need to find out from edgar what the timing is on the guide publication09:35
*** xingchao has quit IRC09:35
anteayathe migration section may not make it into the k release of the guide09:35
anteayawhich is fine since the migration code won't09:35
anteayaso for now work on that patch is on hold09:36
anteayaany questions or thoughts?09:36
*** xingchao has joined #openstack-meeting09:36
anteayanext topic09:36
anteaya#topic testing09:36
*** openstack changes topic to "testing (Meeting topic: nova-net-to-neutron-migration)"09:36
anteayaso we don't really have anything for this section09:37
anteayaand that is okay09:37
anteayaso we will work on getting folks to test jlibosva's patch with flat network managers09:37
obondarevanteaya: but we now have db migration for flat to test ;)09:37
anteayaanything else we have ready to test09:37
anteayaobondarev: yes!09:38
anteayaanything more for testing?09:38
anteaya#topic Open Discussion09:38
*** openstack changes topic to "Open Discussion (Meeting topic: nova-net-to-neutron-migration)"09:38
anteayaanyone have anything here?09:38
*** akiskourtis has joined #openstack-meeting09:38
anteayaokay09:39
*** cody-somerville has joined #openstack-meeting09:39
*** cody-somerville has quit IRC09:39
*** cody-somerville has joined #openstack-meeting09:39
jlibosvanope09:39
anteayawell thanks everyone for your attendance and participation09:39
*** ebalduf has quit IRC09:39
anteayahave a good holiday jlibosva09:39
jlibosvathanks :)09:39
anteayasee you when you return09:39
anteayasee everyone else next week09:39
obondarevthanks everyone09:39
anteayathank you09:39
anteaya#endmeeting09:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:39
openstackMeeting ended Tue Feb 24 09:39:39 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-02-24-09.00.html09:39
jlibosvasee you09:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-02-24-09.00.txt09:39
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-02-24-09.00.log.html09:39
*** xingchao has quit IRC09:41
*** bvandenh has joined #openstack-meeting09:41
*** etoews has joined #openstack-meeting09:41
*** Akis__ has quit IRC09:41
*** nellysmitt has joined #openstack-meeting09:44
*** etoews has quit IRC09:46
*** VW_ has joined #openstack-meeting09:46
*** egallen has quit IRC09:50
*** neeti has joined #openstack-meeting09:51
*** doron_afk has quit IRC09:52
*** neeti_ has quit IRC09:54
*** anish_ has joined #openstack-meeting09:54
*** egallen has joined #openstack-meeting09:58
*** jcoufal has quit IRC09:59
*** jcoufal has joined #openstack-meeting09:59
*** fzdarsky has quit IRC09:59
*** jang has quit IRC10:00
*** _nadya_ has joined #openstack-meeting10:00
*** pelix1 has joined #openstack-meeting10:03
*** yamamoto has quit IRC10:03
*** jang has joined #openstack-meeting10:03
*** harlowja_away has quit IRC10:04
*** pelix1 is now known as pelix10:04
*** shengjiemin has quit IRC10:05
*** aranjan has quit IRC10:05
*** otter768 has joined #openstack-meeting10:12
*** dguitarbite has joined #openstack-meeting10:13
*** psedlak_clone has joined #openstack-meeting10:14
*** psedlak_clone has quit IRC10:16
*** _nadya_ has quit IRC10:16
*** otter768 has quit IRC10:17
*** markvoelker has joined #openstack-meeting10:18
*** markvoelker has quit IRC10:23
*** sdake__ has joined #openstack-meeting10:25
*** armax has quit IRC10:26
*** sdake___ has joined #openstack-meeting10:27
*** sdake_ has quit IRC10:28
*** fzdarsky has joined #openstack-meeting10:28
*** marcusvrn has joined #openstack-meeting10:28
*** ddieterly has joined #openstack-meeting10:29
*** sdake__ has quit IRC10:30
*** jang has quit IRC10:31
*** paragan has quit IRC10:31
*** armax has joined #openstack-meeting10:32
*** ndipanov has quit IRC10:32
*** marcusvrn1 has joined #openstack-meeting10:32
*** paragan has joined #openstack-meeting10:33
*** ddieterly has quit IRC10:33
*** ibiris is now known as ibiris_away10:34
*** ebalduf has joined #openstack-meeting10:35
*** marcusvrn has quit IRC10:35
*** chandankumar_ has joined #openstack-meeting10:37
*** chandankumar has quit IRC10:38
*** fzdarsky has quit IRC10:40
*** ebalduf has quit IRC10:40
*** shengjiemin has joined #openstack-meeting10:41
*** jang1 has joined #openstack-meeting10:41
*** etoews has joined #openstack-meeting10:42
*** xingchao has joined #openstack-meeting10:43
*** ibiris_away is now known as ibiris10:43
*** ndipanov has joined #openstack-meeting10:46
*** etoews has quit IRC10:46
*** cody-somerville has quit IRC10:50
*** xingchao has quit IRC10:50
*** jang1 has quit IRC10:52
*** jang1 has joined #openstack-meeting10:53
*** tochi has quit IRC10:54
*** doron_afk has joined #openstack-meeting10:55
*** jawed has quit IRC10:56
*** tnurlygayanov has joined #openstack-meeting10:58
*** aranjan has joined #openstack-meeting11:02
*** subscope has quit IRC11:05
*** fzdarsky has joined #openstack-meeting11:12
*** shardy is now known as shardy_afk11:13
*** ildikov has quit IRC11:15
*** subscope has joined #openstack-meeting11:17
*** Riddhi has joined #openstack-meeting11:17
*** fzdarsky has quit IRC11:18
*** salv-orlando has quit IRC11:18
*** markvoelker has joined #openstack-meeting11:19
*** dims has joined #openstack-meeting11:20
*** jang1 has quit IRC11:20
*** jang1 has joined #openstack-meeting11:23
*** markvoelker has quit IRC11:24
*** yamamoto has joined #openstack-meeting11:29
*** ddieterly has joined #openstack-meeting11:29
*** cody-somerville has joined #openstack-meeting11:31
*** bobmel has joined #openstack-meeting11:32
*** ddieterly has quit IRC11:34
*** mrmartin has joined #openstack-meeting11:34
*** paragan has quit IRC11:35
*** bobmel_ has quit IRC11:35
*** VW_ has quit IRC11:36
*** aranjan has quit IRC11:36
*** ebalduf has joined #openstack-meeting11:36
*** chandankumar_ has quit IRC11:38
*** chandankumar has joined #openstack-meeting11:38
*** rajeshr has quit IRC11:38
*** shankar has quit IRC11:40
*** oanufriev has joined #openstack-meeting11:40
*** ebalduf has quit IRC11:40
*** GheRivero has quit IRC11:41
*** etoews has joined #openstack-meeting11:43
*** jang1 has quit IRC11:43
*** britthouser has joined #openstack-meeting11:44
*** jang has joined #openstack-meeting11:46
*** doron_afk is now known as Guest9746411:47
*** etoews has quit IRC11:47
*** spredzy is now known as spredzy|afk11:56
*** enterprisedc has joined #openstack-meeting11:57
*** mrmartin has quit IRC11:58
*** ildikov has joined #openstack-meeting11:59
*** tomoe_ has joined #openstack-meeting12:00
*** Guest97464 is now known as doron_afk12:03
*** britthouser has quit IRC12:04
*** markvoelker has joined #openstack-meeting12:05
*** rfolco has joined #openstack-meeting12:07
*** salv-orlando has joined #openstack-meeting12:10
*** markvoelker has quit IRC12:11
*** otter768 has joined #openstack-meeting12:13
*** yamamoto has quit IRC12:15
*** tomoe_ has quit IRC12:15
*** tomoe_ has joined #openstack-meeting12:15
*** otter768 has quit IRC12:18
*** oomichi_ has quit IRC12:21
*** yamamoto has joined #openstack-meeting12:23
*** VW_ has joined #openstack-meeting12:25
*** IanGovett has joined #openstack-meeting12:27
*** jang has quit IRC12:28
*** aysyd has joined #openstack-meeting12:29
*** yamamoto has quit IRC12:29
*** ddieterly has joined #openstack-meeting12:30
*** ajayaa has quit IRC12:31
*** VW_ has quit IRC12:32
*** aranjan has joined #openstack-meeting12:32
*** colinmcnamara has joined #openstack-meeting12:33
*** ddieterly has quit IRC12:35
*** amakarov_away is now known as amakarov12:35
*** jang1 has joined #openstack-meeting12:35
*** ebalduf has joined #openstack-meeting12:37
*** doron_afk is now known as Guest9746412:38
*** Guest97464 is now known as doron_afk12:39
*** ebalduf has quit IRC12:41
*** _nadya_ has joined #openstack-meeting12:43
*** adalbas has joined #openstack-meeting12:44
*** akuznetsov has quit IRC12:44
*** adalbas has quit IRC12:50
*** jang1 has quit IRC12:50
*** jang has joined #openstack-meeting12:51
*** yamamoto has joined #openstack-meeting12:51
*** jang has quit IRC12:55
*** armax has quit IRC12:56
*** fzdarsky has joined #openstack-meeting12:56
*** adalbas has joined #openstack-meeting12:57
*** Mandell has joined #openstack-meeting12:58
*** balajiiyer has joined #openstack-meeting12:58
*** jang has joined #openstack-meeting12:58
*** mwagner_ has quit IRC12:58
*** mwagner_lap has quit IRC12:59
*** lazy_prince is now known as killer_prince12:59
*** doron_afk is now known as Guest9746413:00
*** yamamoto has quit IRC13:01
*** Mandell has quit IRC13:03
*** yatin has quit IRC13:04
*** Guest97464 is now known as doron_afk13:05
*** Tross has joined #openstack-meeting13:05
*** aranjan has quit IRC13:06
*** markvoelker has joined #openstack-meeting13:06
*** Riddhi has quit IRC13:07
*** varora has joined #openstack-meeting13:10
*** jckasper has quit IRC13:11
*** markvoelker has quit IRC13:11
*** Longgeek has joined #openstack-meeting13:12
*** vigneshvar has quit IRC13:13
*** lpmulligan has joined #openstack-meeting13:14
*** spredzy|afk is now known as spredzy13:14
*** jang has quit IRC13:16
*** doude has quit IRC13:17
*** Adri2000 has quit IRC13:17
*** Adri2000 has joined #openstack-meeting13:17
*** doude has joined #openstack-meeting13:17
*** sreshetnyak has joined #openstack-meeting13:18
*** dprince has joined #openstack-meeting13:18
*** chandankumar has quit IRC13:20
*** amotoki has quit IRC13:21
*** tomoe_ has quit IRC13:21
*** jang has joined #openstack-meeting13:24
*** Murali_ has joined #openstack-meeting13:24
*** armax has joined #openstack-meeting13:24
*** radez_g0n3 is now known as radez13:25
*** salv-orlando has quit IRC13:25
*** britthouser has joined #openstack-meeting13:25
*** salv-orlando has joined #openstack-meeting13:26
*** Murali has quit IRC13:26
*** adalbas has quit IRC13:26
*** Murali_ is now known as Murali13:26
*** edleafe has quit IRC13:26
*** edleafe has joined #openstack-meeting13:28
*** jang has quit IRC13:28
*** xingchao has joined #openstack-meeting13:30
*** ddieterly has joined #openstack-meeting13:31
*** BharatK has quit IRC13:31
*** jang has joined #openstack-meeting13:32
*** ddieterly has quit IRC13:35
*** ddieterly has joined #openstack-meeting13:35
*** jaypipes has quit IRC13:36
*** ebalduf has joined #openstack-meeting13:38
*** rbowen has joined #openstack-meeting13:38
*** _nadya_ has quit IRC13:40
*** xyang1 has joined #openstack-meeting13:40
*** ebalduf has quit IRC13:42
*** rushiagr_away is now known as rushiagr13:43
*** unicell1 has joined #openstack-meeting13:44
*** ChuckC has joined #openstack-meeting13:45
*** cbouch has joined #openstack-meeting13:46
*** unicell has quit IRC13:46
*** balajiiyer has left #openstack-meeting13:46
*** mwagner_lap has joined #openstack-meeting13:47
*** SridharG has left #openstack-meeting13:47
*** mwagner_ has joined #openstack-meeting13:47
*** kylek3h has joined #openstack-meeting13:49
*** doron_afk is now known as Guest9746413:49
*** rkukura has joined #openstack-meeting13:50
*** xingchao has quit IRC13:51
*** amuller has joined #openstack-meeting13:51
*** dkranz has joined #openstack-meeting13:52
*** yamamoto has joined #openstack-meeting13:52
*** watanabe_isao has joined #openstack-meeting13:52
*** jckasper has joined #openstack-meeting13:54
*** thangp has joined #openstack-meeting13:55
*** zhhuabj has quit IRC13:55
*** paragan has joined #openstack-meeting13:55
*** amitgandhinz has joined #openstack-meeting13:55
*** amitgandhinz has quit IRC13:55
*** colinmcnamara has quit IRC13:55
*** amitgandhinz has joined #openstack-meeting13:55
*** jckasper has quit IRC13:56
*** roaet has joined #openstack-meeting13:56
*** jckasper has joined #openstack-meeting13:56
*** emagana has joined #openstack-meeting13:56
*** akiskourtis has quit IRC13:57
*** bknudson has joined #openstack-meeting13:57
*** akiskourtis has joined #openstack-meeting13:57
*** carl_baldwin has joined #openstack-meeting13:57
*** Sam-I-Am has joined #openstack-meeting13:57
*** neeti has quit IRC13:58
mesteryhi13:58
Sam-I-Amhowdy13:58
roaethiyo13:58
jlibosvahi13:58
yamamotohi13:58
armaxyello13:58
marioso/13:58
carl_baldwinhi13:59
bloganhi13:59
emaganabuenos dias!13:59
*** radez is now known as radez_g0n313:59
amullerheya13:59
rkukurahi13:59
*** sdake_ has joined #openstack-meeting13:59
*** rackertom has joined #openstack-meeting13:59
*** vigneshvar has joined #openstack-meeting13:59
enikanorov__hello13:59
*** lpmulligan has quit IRC13:59
*** tomoe_ has joined #openstack-meeting13:59
rackertomo/14:00
emaganaI am barely awake! I am not responsible for my comments!!14:00
*** pc_m has joined #openstack-meeting14:00
*** ihrachyshka has joined #openstack-meeting14:00
*** mwagner_ has quit IRC14:00
mesteryemagana: lol14:00
HenryGo/14:00
ihrachyshkao/14:00
roaet+114:00
*** spradeepv has joined #openstack-meeting14:00
Sam-I-Amalso barely awake14:00
pc_mhi14:00
*** xuhanp has joined #openstack-meeting14:00
watanabe_isaohello14:00
mesterymarkmcclain salv-orlando dougwig: Courtesy ping14:00
mestery#startmeeting networking14:00
openstackMeeting started Tue Feb 24 14:00:55 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** niclem has joined #openstack-meeting14:01
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:01
mestery#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
mesteryWe continue our march towards the Kilo release.14:01
mesteryDates of importance:14:01
mestery#info Feature Proposal Freeze: March 514:01
mestery#info Feature, String, and Dependency Freeze: March 1914:01
mestery#info RCs: April 9-2314:01
*** jckasper has quit IRC14:01
mestery#info Kilo release: April 3014:01
markmcclaino/14:02
mestery#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule14:02
obondarevo/14:02
mesteryAny questions on the upcoming Kilo dates?14:02
mesteryI encourage people to continue focusing on reviewing code targeted for Kilo-314:02
mestery#link https://launchpad.net/neutron/+milestone/kilo-314:03
*** aranjan has joined #openstack-meeting14:03
salv-orlandoaloha folks14:03
mesteryAny other announcements from anyone?14:03
anteayao/14:03
dougwigO/14:03
sc68calo/14:03
*** britthouser has quit IRC14:03
*** sdake___ has quit IRC14:03
mesteryOK, lets move on now14:03
mestery#topic Bugs14:03
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:03
mesteryenikanorov__: Hi!14:03
enikanorov__mestery: hi14:03
enikanorov__not much news on bugs side14:04
enikanorov__https://bugs.launchpad.net/neutron/+bug/142123214:04
openstackLaunchpad bug 1421232 in neutron "Restarting neutron openvswitch while having broadcast/multicast traffic going into br-tun makes a broadcast storm over the tunnel network" [Critical,Fix committed] - Assigned to Miguel Angel Ajo (mangelajo)14:04
enikanorov__this one was critical and now committed14:04
enikanorov__https://bugs.launchpad.net/neutron/+bug/132365814:04
openstackLaunchpad bug 1323658 in OpenStack Compute (nova) "Nova resize/restart results in guest ending up in inconsistent state with Neutron" [Critical,Confirmed]14:04
*** britthouser has joined #openstack-meeting14:04
enikanorov__and this still requires someone to dig in14:04
mesteryenikanorov__: Is that a new one? Looking now14:05
enikanorov__not really, it has been hanging in critical for a few weeks now14:05
salv-orlandomestery: suspect it's still another version of "the something went wrong with networking" bug14:05
mesteryenikanorov__: Yeah, I moved it out of Kilo-1 and no one has signed up for it yet14:05
mesterysalv-orlando: It is indeed14:05
*** rob__ has joined #openstack-meeting14:06
mesterysalv-orlando: Your last comments on it indicated it was a tempest issue not a neutron issue14:06
mesterywait14:06
enikanorov__salv-orlando: that's what most of us get salary for14:06
mesterythat was a different bug14:06
*** amitgandhinz has quit IRC14:06
*** rob__ is now known as zehicle14:06
salv-orlandoenikanorov__: are you paid for making neutron now work?14:06
anteayajogo asked me to help get someone assigned, I hadn't been able to help with that yet14:06
*** markvoelker has joined #openstack-meeting14:07
salv-orlandoOr as long as neutron doesn't work, we have job?14:07
*** amitgandhinz has joined #openstack-meeting14:07
anteayaso thanks for bringing it up enikanorov__14:07
enikanorov__salv-orlando: somewhat in between14:07
mesteryanteaya: I'll see if I can look into it a bit after the meeting14:07
*** mrmartin has joined #openstack-meeting14:07
anteayamestery: thank you14:07
enikanorov__ok, the last one i'd like to mention is14:07
*** ddieterly has quit IRC14:07
markmcclainmestery, anteaya: I get the feeling this is going to require pairing between Nova and Neutron devs14:07
ajoI want to mention another one when you finish ;)14:07
ajohi ;D14:07
mesterymarkmcclain: Highly likely ;)14:07
enikanorov__https://bugs.launchpad.net/neutron/+bug/135952314:07
openstackLaunchpad bug 1359523 in neutron "Security group rules errorneously applied to all ports having same ip addresses in different networks" [High,In progress] - Assigned to shihanzhang (shihanzhang)14:07
anteayamarkmcclain: fair enough14:08
enikanorov__this has a patch on review but apparently the author has abandoned it14:08
*** lpmulligan has joined #openstack-meeting14:08
enikanorov__i think this is really important to be fixed in K14:08
ajohmmm14:08
anteayamarkmcclain: if we can get a neutron dev, we can ask jogo to help or help find a nova dev14:08
ajoenikanorov__: I can review that as I'm familiar with the SG code14:08
*** zhhuabj has joined #openstack-meeting14:08
mesteryajo: Thank you!14:08
*** dboik has joined #openstack-meeting14:08
enikanorov__ajo: i think we'll need someone to drive code through, not just review it...14:09
ajoenikanorov__, I can talk to hanzhang and drive it myself if he can't14:09
enikanorov__ajo: wold be great, thanks14:09
ajo:-), sure, np14:09
ajohttps://bugs.launchpad.net/neutron/+bug/141098214:09
openstackLaunchpad bug 1410982 in neutron "test_slaac_from_os frequent failures" [High,Confirmed]14:09
ajoThis bug is a bit of a mess,14:09
armaxanother bug that’s hurting is this bug #142448214:09
openstackbug 1424482 in tempest "AttributeError: 'module' object has no attribute 'MismatchError'" [Undecided,In progress] https://launchpad.net/bugs/1424482 - Assigned to Armando Migliaccio (armando-migliaccio)14:09
*** dboik has joined #openstack-meeting14:10
armaxmtreinish: ^^^14:10
ajoit was exacerbated by a patch I submitted, and the original problem I'm unsure if it's still happening14:10
salv-orlandowell but 124482 is assigned so I'm not worried ;)14:10
*** dane_leblanc has joined #openstack-meeting14:10
ajo:-)14:10
enikanorov__any question on bugs?14:11
ajofor 1410982, I couldn't find current test_slaac_from_os failures not associated to other massive failures14:11
mesteryajo: Looks like 1410982 has a healthy discussion in there between you, carl_baldwin, armax, and others14:11
*** amitgandhinz has quit IRC14:11
ajoso I'm unsure if the bug is valid anymore14:11
ajobut...14:11
*** sdake_ has quit IRC14:11
ajowhat I couldn't find it, doesn't mean it doesnt exist... may be I'm not proficient enough with kibana (that for sure)14:11
*** sdake_ has joined #openstack-meeting14:12
armaxajo: I’ll look into it, I haven’t had the chance lately though14:12
*** jang has quit IRC14:12
ajoarmax, thanks, if you could do it, I tried 2 times lately without finding the issue anymore,14:12
ajobtw,14:12
ajoI find the netlink interface errors sometimes in well passed tests14:13
*** dims has quit IRC14:13
salv-orlandoajo: that's normal14:13
*** baoli has joined #openstack-meeting14:13
*** changbl has quit IRC14:13
salv-orlandoit might because it is an API test which spins off some dhcp action as a side effect but does not validate it14:13
*** dims has joined #openstack-meeting14:13
ajosalv-orlando, yes, I found reasonable explanations for that,14:13
*** _nadya_ has joined #openstack-meeting14:14
*** otter768 has joined #openstack-meeting14:14
mesteryOK, thanks for the updates on bugs enikanorov__ and others!14:14
mesteryAny other bugs the team shoudl discuss today?14:14
*** hichihara has joined #openstack-meeting14:14
mesteryIf not, we'll move on to ...14:15
*** britthouser has quit IRC14:15
mestery#topic Docs14:15
*** openstack changes topic to "Docs (Meeting topic: networking)"14:15
mesteryemagana: Hi!14:15
emaganamestery: Hello!14:15
*** cdub has joined #openstack-meeting14:15
*** jang1 has joined #openstack-meeting14:15
emaganaThe first commit for the nova-net to neutron has been committed14:16
mesteryemagana: Matt Kassawara put an item in "On Deman" which I think we shoudl discuss here, so after your update, lets discuss that one.14:16
mesteryemagana: Cool!14:16
emaganaI will let Sam-I-Am to comment14:16
Sam-I-Amim here, but a little slow14:16
mesterySam-I-Am: :)14:16
emagana#link https://review.openstack.org/#/c/155947/14:17
*** chandankumar has joined #openstack-meeting14:17
emaganaSam-I-Am: Do you want to share about the networking guide14:17
*** navid__ has joined #openstack-meeting14:17
Sam-I-Amemagana: sure14:17
Sam-I-Amits moving along. i'm trying to fiish the L3HA+OVS scenario... writing it in rst from the start14:18
Sam-I-Amthe docs crew has been trying to get rst working for the networking guide14:18
amullerSam-I-Am: Sounds cool - Add me as a reviewer. Also, you can use information from: https://review.openstack.org/#/c/150918/14:18
Sam-I-Amonce the build system works, we'll try to get the scenarios uploaded into the official repo14:18
Sam-I-Ami am looking for l3ha SMEs :)14:19
mesterySam-I-Am: Start with amuller :)14:19
*** otter768 has quit IRC14:19
Sam-I-Amthats what i just found out :)14:19
Sam-I-Amwe're writing instructions for both linuxbridge and ovs14:19
emaganaThe rest of the .rst links are on the wiki if anyone is interested in the current work!14:20
mesteryemagana: Awesome, thanks!14:20
Sam-I-Ami think thats it for the networking guide. i'll probably try to get more feedback at mid-cycle in a few weeks.14:20
*** swamireddy is now known as swamireddy_afk14:20
Sam-I-Ammestery: want me to go on about the other thing?14:21
mesteryOK, thanks for the docs updates folks!14:21
*** vigneshvar has quit IRC14:21
emaganaThanks Sam-I-Am!14:21
mesterySam-I-Am: Yes, lets move there.14:21
Sam-I-Ami added an on-demand topic about confusion around the location of ovs/linuxbridge agent configuration after ML2 deprecated the plugins14:22
*** zul has quit IRC14:23
Sam-I-Amthe install guide moved the agent config into ml2_conf.ini14:23
ihrachyshkaoh14:23
ihrachyshkaI think it's wrong14:23
Sam-I-Amhowever, i see periodic bugs filed by mostly distro packagers who insist on ising ovs_neutron_plugin.ini and linuxbridge_conf.ini still14:24
ihrachyshkathere is still ovs_neutron_plugin.ini file14:24
*** amotoki has joined #openstack-meeting14:24
Sam-I-Amyes, there is, but it is not for a plugin anymore14:24
ihrachyshkathough the name is bad, it's still reused by the agent14:24
Sam-I-Amthis causes lots o confusion with newbies14:24
ihrachyshkawe can't just rename the file for backwards compat reasons14:24
ihrachyshkayes, we had bugs reported in RDO for that14:24
*** salv-orlando has quit IRC14:24
ihrachyshkabut we stand our ground and use the file for the agent14:24
*** zul has joined #openstack-meeting14:24
markmcclainihrachyshka: why can't we rename the file for new installations?14:24
rkukurawhy should the agent config be in the plugin ini file?14:24
markmcclainor sym link?14:24
ihrachyshkasince that's where we maintain those conf values in the tree14:25
*** joesavak has joined #openstack-meeting14:25
ihrachyshkamarkmcclain, we can. though it opens doors to upgrade issues. we would need to read from both files14:25
ihrachyshkaideally, agents would read from conf-dir, not conf-file14:25
Sam-I-Amthe linuxbridge_conf.ini file is a little less misleading, but if we do continue to use separate files, they should have better names (suggestions on the wiki)14:25
ihrachyshkaand we would have more freedom with the file names14:25
markmcclainihrachyshka: yes.. conf dir would be a bit cleaner except that we have overlapping options in some agents14:26
ihrachyshkaalso, it would help in the world of *aas repos split from main repo14:26
markmcclainihrachyshka: that said I'm all for conf dir :)14:26
ihrachyshkaf.e. before kilo, we read fwaas conf by l3 agent14:26
ihrachyshkabut now that we have no guarantees to have fwaas conf installed, we can't14:26
ihrachyshkaconf-dir would solve that14:26
ihrachyshkaSam-I-Am, do you see how to handle upgrade for existing users without grenade hook?14:27
ihrachyshkawe could obviously rename the file, putting burden on deployers/packagers14:27
*** sdake__ has joined #openstack-meeting14:28
ihrachyshkame being lazy, I vote for leaving as-is, but if people see it a huge problem, ok, let's rename in start of the next cycle14:28
ihrachyshkanot now14:28
*** britthouser has joined #openstack-meeting14:28
*** nellysmitt has quit IRC14:28
Sam-I-Amihrachyshka: iirc, neutron just concatenates a bunch of config files when it loads14:29
*** nshaikh has left #openstack-meeting14:29
ihrachyshkaso short story, admin guide is currently wrong14:29
*** nellysmitt has joined #openstack-meeting14:29
*** navid__ has left #openstack-meeting14:29
Sam-I-Amyou can include anything in the init scripts14:29
*** nellysmitt has quit IRC14:29
*** bill_az has joined #openstack-meeting14:29
ihrachyshkaSam-I-Am, you need to pass all conf files as --conf-file arguments14:29
Sam-I-Amyes14:29
*** nellysmitt has joined #openstack-meeting14:29
amotokiihrachyshka: what's the difference between we change them now and keep them now in this cycle?14:29
ihrachyshkaSam-I-Am, right, but I'm not sure it plays nice with non-existent files14:29
Sam-I-Amtouch the new file and tell people to migrate their config to it?14:30
ihrachyshkaamotoki, packagers are not forced to apply yet another change to packaging this cycle which is already beyond normal in terms of disruptions14:30
mesteryihrachyshka: Fair point14:30
Sam-I-Ami'm just trying to fix a repeat confusion problem14:30
ihrachyshkaSam-I-Am, yeah, everything is possible, but reading ml2 conf is just wrong in any case14:30
amotokiihrachyshka: fair enough.14:30
Sam-I-Ammaybe create another config file and let people decide when they move to it?14:31
*** openstack-meetin has joined #openstack-meeting14:31
*** Sukhdev has joined #openstack-meeting14:31
mesterySam-I-Am: I think that woudl lead to more confusion14:31
ihrachyshka+14:31
amotokiin my understanding all of existing conf files are examples and all have default values,14:31
*** sdake_ has quit IRC14:31
Sam-I-Ami'm just bringing this up as a pain point14:32
Sam-I-Amit should have been fixed a long time ago14:32
*** SridharG has joined #openstack-meeting14:32
*** markvoelker has quit IRC14:32
Sam-I-Amiirc, ubuntu packages dont include an ovs_neutron_plugin.ini file unless you installl the defunct plugin14:32
mesterySam-I-Am: It's a fair point, lets discuss this offline and see what we can do perhaps.14:33
Sam-I-Amso i have to create it anyway14:33
*** markvoelker has joined #openstack-meeting14:33
amotokieven though most distributions use them as an initial conf files, so I think moving them in upstream tree only affects packagers.14:33
ihrachyshkaamotoki, not completely. afaik neutron.conf has state_path defined14:33
ihrachyshkaSam-I-Am, so that's something to fix in ubuntu packaging14:33
Sam-I-Ami have to maintain an install guide for all distros :/14:33
*** adalbas has joined #openstack-meeting14:33
amotokiihrachyshka: right. i know we have some exceptions and hopefully they should be clean-up.14:33
Sam-I-Ammestery: sounds like a good plan14:33
mesteryOK, thanks for the discussion here Sam-I-Am!14:34
*** ChrisPriceAB has joined #openstack-meeting14:34
*** mtanino has quit IRC14:34
mesteryLets move on now.14:34
mestery#topic Plugin Decomposition Status Update14:34
*** openstack changes topic to "Plugin Decomposition Status Update (Meeting topic: networking)"14:34
mesteryihrachyshka has offered to provide an update from a packaging perspective here on the changes plugin decomposition will make for packagers.14:35
mesteryihrachyshka: Ready?14:35
ihrachyshkaright14:35
mesteryihrachyshka: thanks!14:35
ihrachyshkaso I'm packaging neutron for RDO/RHOSP. status on our side is that no vendor libraries are actually packaged. :)14:35
mesterylol14:35
ihrachyshkaand that's partly because of no pypi releases14:36
*** hareeshp has joined #openstack-meeting14:36
*** chandankumar_ has joined #openstack-meeting14:36
ihrachyshkathere is no clear message from upstream on what is considered to be ready14:36
*** yamahata has joined #openstack-meeting14:36
ihrachyshkaalso no clear list that tracks the progress (there is google doc from armax, but that's all)14:36
*** chandankumar has quit IRC14:36
*** sdake_ has joined #openstack-meeting14:36
ihrachyshkaI saw more patches to decomp plugins coming in14:37
armaxihrachyshka: what do you consider something to be ready? pypy release available?14:37
mesteryihrachyshka: I can give you perspective from the decomposed ODL driver.14:37
*** ayoung has joined #openstack-meeting14:37
*** aranjan has quit IRC14:37
ihrachyshkait would be great to have some kind of a list of what's actually ready14:37
mesteryihrachyshka: We're working on a few last bugs before releasing to pypi the first version.14:37
mesteryUnsure if others are also fixing bugs before releasing14:37
Sukhdevihrachyshka: Arista is ready14:37
ihrachyshkaarmax, right, I would consider pypi release as an indication of library being ready14:37
mesterySukhdev: You've released to pypi?14:38
Sukhdevmestery: yes14:38
*** markvoelker has quit IRC14:38
mesterySukhdev: Nice work!14:38
HenryGWhat does "release to pypi" entail? We have 0.0.1 there.14:38
*** ebalduf has joined #openstack-meeting14:38
ihrachyshkacool. that would be great to have some periodic update to downstreams on the progress.14:38
armaxihrachyshka: ok, so it sounds to me that your readiness checklist would be to determine whether for each tracked effort we have a pypi package supplied14:39
anteaya#link https://pypi.python.org/pypi/networking_arista/2015.1.1.dev1214:39
ihrachyshkaHenryG, well, at least something to package. it's better if it actually works.14:39
Sukhdevarmax has a list we can use that14:39
*** doude has quit IRC14:39
anteayais having dev in the release name compliant with semver?14:39
*** _nadya_ has quit IRC14:39
mesteryHenryG: https://wiki.openstack.org/wiki/GerritJenkinsGit#Tagging_a_Release14:39
mestery#link https://wiki.openstack.org/wiki/GerritJenkinsGit#Tagging_a_Release14:39
rkukurait would seem distros will need some mapping from neutron release (including stable branches) to specific library versions, right?14:39
*** sdake__ has quit IRC14:40
ihrachyshkarkukura, I think there is one, per plugin requirements.txt14:40
Sukhdevanteaya: this is the correct one - https://pypi.python.org/pypi/networking_arista/2015.1.114:40
amotokirkukura: i think requirements.txt in plugins/drviers dir should declare it.14:40
ihrachyshkarkukura, they should point to proper versions14:40
dougwigrkukura: the requirements files in the shim directories should have that.14:40
dougwigsuper jinx14:41
ihrachyshka:)14:41
*** joesavak has quit IRC14:41
mesterylol14:41
amotokibut one question is when we should update requirements in shim plugin dir. version cap?14:41
ihrachyshkaamotoki, when we absolutely need it?14:41
ihrachyshkathere is one question about vendor split. what do we do with upgrade for existing juno users?14:42
mesteryihrachyshka: ++14:42
rkukuraso if a vendor pushes an update to fix a critical bug in their library, vendors should be able to package that update without a new version of neutron referencing the new version in requirements.txt, right?14:42
ihrachyshkarkukura, right14:42
rkukura2nd vendors should be distros14:42
mesteryrkukura: Yes, neutron doesn't reference the shims, it's the other way around14:42
*** ebalduf has quit IRC14:42
rkukuraneutron contains the shims14:43
ihrachyshkamestery, though neutron packages may actually reference vendor libs for upgrade purpose14:43
mesteryrkukura: replace shims with backends14:43
rkukuramestery: ok14:43
mesteryin my comment14:43
*** rbak has joined #openstack-meeting14:44
mesteryihrachyshka: Where do they reference the vendor libs?14:44
rkukuraso in kili, requirements.txt for a driver will reference a specific backend lib version, right?14:44
ihrachyshkaon second thought, if a distro properly splits plugins now into separate packages, then it's fine to add dependencies to vendor libraries14:44
rkukurakilo14:44
ihrachyshkamestery, a openstack-neutron-arista package should depend on vendor lib14:44
mesteryihrachyshka: Got it14:44
Sukhdevihrachyshka: Please look at Arista directory - there is a requirements.txt in the drivers directory and it is released to pypi - what else needs to be done for it to be picked up?14:44
*** ddieterly has joined #openstack-meeting14:44
rkukuraIf the vendor updates the backend lib, no change to neutrron is likely needed, except the update to the version in requirements.txt.14:44
ihrachyshkaSukhdev, I think it's done your side, and packagers should start their job. plus maybe there should be some public status update from armax about plugins ready for that.14:45
amotokirkukura: right. if we have "<x.y.z" in req file, requiremnt upadte is also unnecessary.14:45
mesteryamotoki: ++14:46
rkukuraamotoki: ok14:46
Sukhdevihrachyshka: ah OK - so, time to bug armax :-)14:46
armaxihrachyshka: let’s agree on the degrees of readiness and we can revise the doc\14:46
ihrachyshkaarmax, 'it works' and 'it's published somewhere other than git'?14:46
dougwigugh, pinning may be a necessary evil, but i'd hate to see it become the norm.  it means the library sucks at backwards compatibility.14:46
armaxihrachyshka: but it’s probably best to take this offline14:46
amotokiin my understanding requirements fiel in plugins/drives are just reference for packages and users.14:46
ihrachyshkaarmax++14:46
armaxihrachyshka: docs too14:46
mesteryarmax: ++14:46
armaxihrachyshka: CI, etc… :)14:47
mesteryamotoki: I thought so too.14:47
armaxihrachyshka: so it sounds to me we’re reinventing the wheel14:47
armaxas to what we need to document :)14:47
amotokiless than 15mins left. do we have more items to discuss?14:47
armaxbut let’s circle back so that we don’t lose focus on what you and distros really needs14:47
mesteryamotoki: Yes, I propose we move on and continue this discussion later.14:48
mesteryarmax ihrachyshka: Sound ok?14:48
openstack-meetintest14:48
*** eliqiao has joined #openstack-meeting14:48
*** tiswanso has joined #openstack-meeting14:48
ihrachyshkamestery++14:48
mestery#topic nova-network to neutron migration14:48
*** openstack changes topic to "nova-network to neutron migration (Meeting topic: networking)"14:48
mesteryanteaya: Want to provide an update for the group?14:48
anteayasure14:48
mesteryanteaya: thank you!14:49
*** fzdarsky has quit IRC14:49
anteaya#link https://review.openstack.org/#/q/topic:bp/migration-from-nova-net,n,z14:49
*** openstack-meetin has quit IRC14:49
anteayaso no movement on the spec this week, which is to be expected14:49
anteayathe patch for the db migration works with flat networks14:49
*** openstack-meetin has joined #openstack-meeting14:49
anteayais anyone able to test that out and provide some feedback on the patch?14:49
*** openstack-meetin has left #openstack-meeting14:50
anteayaand obondarev is going to have a new patchset for the proxy patch by thursday14:50
obondarevanteaya: I will as part of my tests for proxy patch14:50
mesteryobondarev: awesome, thanks!14:50
anteayaalso we have agreed that we are refocusing on the L release now14:50
anteayaso we won't be expecting any more merges for K14:50
*** PaulMurray has joined #openstack-meeting14:51
anteayaobondarev: great and hopefully we can get some others to test as well14:51
anteayathe more the merrier14:51
mestery#info migration work focusing on Liberty release, no more merges expected for Kilo14:51
anteayaI think that is if for me14:51
*** amsaha has joined #openstack-meeting14:51
mesteryanteaya: Thanks! Any questions from anyone?14:51
mesteryOK lets move on14:51
mestery#topic neutron as default in devstack14:51
*** openstack changes topic to "neutron as default in devstack (Meeting topic: networking)"14:51
mesterysc68cal: You're working on this, want to provide an update for the group?14:51
sc68calSure14:52
mesterysc68cal: Thanks!14:52
sc68calCurrently I'm just doing some preliminary work on taking PUBLIC_INTERFACE and adding it to the OVS_PHSYICAL_BRIDGE14:52
sc68calthen updating the IP address of the bridge and fixing up the routing table14:52
mesterysc68cal: ++, nice!14:52
sc68calBash is not my first, second, or even third language, so please bear with me - it's pretty ugly14:52
mesterysc68cal: We'll grade you on a courve ;)14:53
dougwigIt's ugly even when you know it well14:53
roaetdougwig: +114:53
ajo+1 :D14:53
sc68calbut I know the way forward - i've done it manually, now it's just automating it14:53
*** britthouser has quit IRC14:53
*** joesavak has joined #openstack-meeting14:53
sc68calkeep an eye on this link https://review.openstack.org/15842414:54
sc68calthat14:54
sc68calis it for me14:54
mesterysc68cal: Thanks!14:54
mestery#topic Open Discussion14:54
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:54
mesteryA note from dims: Dims needs Project Ideas, Mentors for GSoC 201514:54
*** xingchao has joined #openstack-meeting14:54
mestery#link https://wiki.openstack.org/wiki/GSoC201514:54
mesteryGo and submit your project ideas!14:55
*** nellysmitt has quit IRC14:55
*** sdake__ has joined #openstack-meeting14:55
mesteryAnything else this week from anyone?14:55
ajofinal bits of this for this cycle: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/agent-child-processes-status,n,z14:55
dimsthanks mestery14:55
ajomkolesnik and I proposed a total change of the process monitor api14:55
anteayajust a poll14:55
*** Mandell has joined #openstack-meeting14:55
*** thomasem has joined #openstack-meeting14:55
ajowe thought it would be good before finishing the cycle14:55
anteayaI have been making it clear that driver testing isn't allowed in the gate14:56
anteayawhat is neutron's stance on that?14:56
ajothe previous one was totally coupled to ProcessManager...14:56
mesteryajo: Nice!14:56
mesteryanteaya: In the Neutron gate?14:56
anteayais has become a topic of discussion in infra14:56
ajoand also, this is ready for review / merge (if we like it) : https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/refactor-iptables-firewall-driver,n,z14:56
anteayawell the example is cinder14:56
anteayabut anything we do for one project the rest want as well14:56
anteayaso there will be spill over14:56
mesteryanteaya: For the open source decomposed plugins, we're doing driver testing for their own stackforge repositories (at least for ODL and soon for OVN as well)14:56
ajomestery++14:57
ajo:-)14:57
*** irenab has quit IRC14:57
mesteryanteaya: But for vendor plugins, not so much.14:57
anteayado you want the opensource plugins in the gate?14:57
*** britthouser has joined #openstack-meeting14:57
anteayacontext: http://lists.openstack.org/pipermail/openstack-dev/2015-February/057472.html14:57
mesteryanteaya: Maybe for the neutron gate, it's possible down the road.14:58
anteayaokay thanks14:58
mesteryWe'll likely discuss this in Vancouver14:58
mesteryanteaya: Thanks for bringing it up here!14:58
anteayaI was going with no, but if I'm wrong then speakk up14:58
*** killer_prince is now known as lazy_prince14:58
mesteryOK, anything else in the last 80 seconds?14:58
mesteryIf not, thanks for everyone's hard work on Kilo!14:58
mesteryLets finish strong! :)14:58
amullerThe hard work is ahead of us...14:59
ajothanks everyone , yes :)14:59
mesteryamuller: :)14:59
emaganaciao14:59
mestery#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
rkukurabye14:59
amotoki:)14:59
openstackMeeting ended Tue Feb 24 14:59:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-02-24-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-02-24-14.00.txt14:59
*** sdake_ has quit IRC14:59
yamamotobye14:59
armaxbye14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-02-24-14.00.log.html14:59
*** rkukura has left #openstack-meeting14:59
*** amuller has left #openstack-meeting14:59
ajohasta la vista ;D14:59
*** phil__ has quit IRC14:59
*** rackertom has left #openstack-meeting14:59
*** rprakash has joined #openstack-meeting14:59
*** dneary has joined #openstack-meeting14:59
markmcclainbye14:59
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Feb 24 15:00:04 2015 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
*** pc_m has left #openstack-meeting15:00
edleafe\o15:00
*** daneyon has quit IRC15:00
lxslio/15:00
*** ihrachyshka has left #openstack-meeting15:01
n0anoedleafe, are you a lefty too or are you just being ironic?15:01
PaulMurray\o/15:01
*** nelsnelson has joined #openstack-meeting15:01
*** hichihara has quit IRC15:01
edleafeI'm ambidextrous, actually15:01
*** amsaha has quit IRC15:01
n0anoeven better15:01
edleafewrite with right hand, mouse with left15:01
*** Sam-I-Am has left #openstack-meeting15:01
n0anomy mother claims I started life as a lefty and then bowed to peer pressure and switched, before I remember things15:02
eliqiaolefty is smarter then righty :)15:02
*** sdake_ has joined #openstack-meeting15:02
eliqiaos/then/than :)15:03
n0anoeliqiao, arguable :-)\15:03
*** jrist-afk is now known as jrist15:03
n0anoanyway, let's get started15:03
n0ano#topic Remove direct nova DB/API access by Scheduler Filters15:03
edleafeOnly left-handed people are in their right minds!15:03
*** openstack changes topic to "Remove direct nova DB/API access by Scheduler Filters (Meeting topic: gantt)"15:03
n0anoedleafe, I see you're finally getting all +'s on the spec, anything to talk about it?15:03
edleafeok, so bauzas finally added his +1 to the spec15:03
bauzas\o15:03
edleafeso I ran it by ndipanov and johnthetubaguy15:03
* bauzas waves late15:03
*** j05h has joined #openstack-meeting15:04
edleafegot a +2 from John15:04
n0anoedleafe, saw that, good news15:04
edleafenick is still reviewing15:04
*** emagana has quit IRC15:04
n0anoI think it should be approved (finally) shortly so, unless you have anything, we can move on15:05
edleafeOnce that spec is approved, the WIP code can be changed to actual reviewable code15:05
ndipanovedleafe, fwiw I don't have +2 on that repo15:05
*** emagana has joined #openstack-meeting15:05
edleafepatch series starting at https://review.openstack.org/#/c/14943015:05
ndipanovedleafe, but am unlikely to protest the spec now... as for the code... :D15:05
n0anondipanov, you're not core for Nova?15:06
edleafendipanov: I assume you're just being thorough :)15:06
ndipanovI am on nova15:06
ndipanovnot on nova specs15:06
*** SridharRamaswamy has joined #openstack-meeting15:06
ndipanovthat is the job of nova-drivers15:06
bauzasnova-drivers are only +2'ing specs15:06
edleafendipanov: ah, I thought you were core for specs, too15:06
ndipanovfirst among equals15:06
*** Murali has quit IRC15:06
edleafeguess I'm going to have to bug dansmith15:06
*** sdake__ has quit IRC15:06
ndipanovedleafe, yeah15:07
* n0ano thinks the beaurocracy is getting a little large15:07
edleafen0ano: getting? :)15:07
bauzasn0ano: ssssht15:07
ndipanovthou I think if he sees +1s from me and jay you'd have to bug him a bit less15:07
*** adalbas has quit IRC15:07
*** spradeepv has quit IRC15:07
n0anoif need be we can bring it up at the nova meeting this week, let's hope we don't have to wait until then15:07
*** alexpilotti has quit IRC15:07
edleafendipanov: but it's fun to bug Dan!15:07
ndipanovn0ano, yathink?15:07
ndipanovedleafe, that it is15:08
ndipanov:)15:08
n0anoOK, let's move on15:08
n0ano#topic Status on cleanup work15:08
*** openstack changes topic to "Status on cleanup work (Meeting topic: gantt)"15:08
*** sarob has joined #openstack-meeting15:08
n0anobauzas, I believe your patches are under control, need any help:?15:08
*** joesavak has quit IRC15:08
*** tidwellr has joined #openstack-meeting15:08
*** Mandell has quit IRC15:09
bauzasn0ano: bp/detach-services is taking the most of my time15:09
bauzasn0ano: but I'm rushing to provide bp/isolate-sched-db15:09
*** jungleboyj has joined #openstack-meeting15:10
*** dkranz has quit IRC15:10
bauzasn0ano: bp/detach-service deserves reviews15:10
bauzasn0ano: and bp/isolate-sched-db is WIP15:10
bauzas(once I'll fix all the demands on bp/detach-service)15:10
*** emagana has quit IRC15:10
bauzasn0ano: bp/requestspec-object is planned to be done on Liberty15:11
n0ano#action review patches for https://blueprints.launchpad.net/nova/+spec/detach-service-from-computenode15:11
bauzasbecause FF is Mar 3rd15:11
*** fzdarsky has joined #openstack-meeting15:11
edleafeMarch 5, no?15:11
alex_xubauzas: 5?15:11
bauzasedleafe: not exactly15:11
*** eliqiao has quit IRC15:11
bauzasbranches are done on Thursdays but code has to be merged on Tuesdays in general15:12
PaulMurrayjohnthetubaguy, said 5th to me15:12
*** joesavak has joined #openstack-meeting15:12
bauzasthat's a matter of trusting Zuul for merging all patches close to a FF15:12
johnthetubaguyhttps://wiki.openstack.org/wiki/Kilo_Release_Schedule15:12
johnthetubaguysays 5th March for Feature Proposal Freeze15:12
bauzasI'm usually targeting Tuesdays for deliveries, even if branching is done by Thursdays15:13
bauzasanyway, you got the idea15:13
PaulMurraybauzas, nothing has to be merged - just uyp for review15:13
PaulMurrays/uyp/up15:13
n0anobottom line, early next week15:13
bauzasyuy15:14
*** mfedosin has quit IRC15:14
*** Guest97464 is now known as doron_afk15:14
*** watanabe_isao has quit IRC15:14
*** mfedosin has joined #openstack-meeting15:14
bauzaseh, hold on15:14
johnthetubaguybauzas: there is no branching or tagging for FeatureProposalFreeze, but thats true for FeatureFreeze15:14
PaulMurraybauzas, FF is 19th15:14
bauzasjohnthetubaguy: right, I confounded FPF and FF15:14
bauzasso yeah, let's plan to rush on the patches by mid-next week15:15
*** tidwellr has left #openstack-meeting15:15
*** Watanabe has joined #openstack-meeting15:15
lxsliTime for an update from PaulMurray ?15:16
n0anosure, go for it15:16
*** sigmavirus24_awa is now known as sigmavirus2415:16
bauzasbtw. I'm taking the opportunity here to ask people to amend https://etherpad.openstack.org/p/kilo-nova-priorities-tracking and set the correct statuses on their ownerships for Launchpad BPs15:16
ndipanovhey n0ano - I have one patch I hacked to bring up (sorry not following along fully) is it appropriate now15:16
ndipanovafter paul that is15:16
n0anondipanov, sure, no fast rules here, but PaulMurray has the floor for now15:17
PaulMurraythere are a few patches for review here: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/make-resource-tracker-use-objects,n,z15:17
PaulMurrayI have one ready for review that starts a (small) series on changing compute node to object15:17
*** salv-orlando has joined #openstack-meeting15:17
*** nellysmitt has joined #openstack-meeting15:18
PaulMurraylxsli, has some migration object patches that could do with rebase and work15:18
lxslithose are in a chain, starting with Jay's numa patch going through sahid's15:18
PaulMurraythanks - just havin trouble typing that15:18
n0anoPaulMurray, lxsli do you need help with that rebase/work or are reviews sufficient?15:18
bauzaslxsli: but jaypipes seems to have problems with his own patch15:18
*** prad has joined #openstack-meeting15:19
lxsliyes getting hay's patch merged is prio #115:19
bauzaslxsli: so I guess it's impacting your chain, right ?15:19
lxslihe mentioned some issue in nova room, sahid said he'd look at that15:19
*** fzdarsky has quit IRC15:19
bauzaslxsli: yeah, I understand it but Jenkins seems to be a badass by sending continously red tomatoes15:19
lxsliI'm working on rebasing sahid's patch to master atm so he has an easier time rebasing it onto jay's patch when it's ready15:20
bauzaslxsli: cool15:20
*** Watanabe has quit IRC15:20
lxsliI have quite some IRC lag atm so apologies for typos15:20
n0anolxsli, NP, the typos are minor so far15:20
PaulMurrayas https://review.openstack.org/#/c/148904/ is sitting ready it would be good to get it through - it moves a couple of methods around so it tends to get hit by rebases15:21
PaulMurraythere are two more follow-ons fro that then compute node will be done15:21
PaulMurrayMy aim is to get rid of references to conductor api with everything going through objects so online updates can work15:22
PaulMurrayNot worry so much about making all the code perfect as it will get changed soon anyway with changes comming to RT15:22
PaulMurrayand scheduler etc.15:22
*** Riddhi has joined #openstack-meeting15:23
*** Riddhi has quit IRC15:23
n0anoPaulMurray, I agree not to worry, we'll just change in future as needed15:23
*** mtanino has joined #openstack-meeting15:23
*** jsavak has joined #openstack-meeting15:23
*** Riddhi has joined #openstack-meeting15:23
PaulMurrayBut of course, my code will be perfrect.... :)15:24
*** devlaps has joined #openstack-meeting15:24
bauzasPaulMurray: seen some patches from Hans Lindgren ?15:24
bauzasPaulMurray: lemme find those15:24
*** devlaps has quit IRC15:24
n0anoPaulMurray, so, in general, sounds like you're making good progress, anything else?15:24
*** dkranz has joined #openstack-meeting15:25
PaulMurrayn0ano, actually - been on vacation - so progress will be better than was15:25
*** ddieterl_ has joined #openstack-meeting15:25
bauzasPaulMurray: https://review.openstack.org/#/c/149224/15:25
*** ddieterly has quit IRC15:25
n0anovacation - I've heard of that, I should try one sometime :-)15:25
bauzasn0ano: take a French resident passport15:25
lxslibauzas: that is abandoned15:25
bauzaslxsli: orly ?15:25
PaulMurraybauzas, that's out of date by the look of it - should be abandoned.15:26
lxsliare there others which are active?15:26
bauzaslxsli: indeed, I missed that point15:26
PaulMurraylxsli, oh -your right - is abandoned15:26
bauzaslxsli: https://review.openstack.org/#/c/133663/ also15:26
*** moha_hunt has quit IRC15:26
lxslibauzas: because it was covered by one of your patches no less :)15:26
bauzaslxsli: right15:27
*** joesavak has quit IRC15:27
bauzaslxsli: I probably made 15 patches in my series, so I'm sometimes loosing memory15:27
PaulMurraybauzas, thanks - I had better keep an eye out for things comming from left field15:27
n0anoOK, let's move on a bit...15:28
bauzasPaulMurray: I have severe delays in reviewing15:28
n0anondipanov, you wanted to say something?15:28
ndipanovah yes15:28
*** adalbas has joined #openstack-meeting15:28
ndipanovso I was working on the bug15:28
ndipanovwhere we don't consider the right flavor for migrating with NUMA15:29
ndipanovhttps://bugs.launchpad.net/nova/+bug/137039015:29
openstackLaunchpad bug 1370390 in OpenStack Compute (nova) "Resize instace will not change the NUMA topology of a running instance to the one from the new flavor" [Medium,In progress] - Assigned to Nikola Đipanov (ndipanov)15:29
ndipanovand came up with this https://review.openstack.org/#/c/158245/15:29
*** cbouch has quit IRC15:29
ndipanovwhich kinda steps into request_spec teritory15:29
ndipanovbut is only relevant inside the filter code15:30
bauzasndipanov: right, I quickly reviewed your patch15:30
ndipanovI mean I CAN fix the bug without it15:30
bauzasndipanov: anyway, I think that we need to rework on the RequestSpec BP, because there was some good comments on the implementation15:30
ndipanovbut this would be a nice cheap win for moving all the filters to use flavor objects15:30
ndipanovbauzas, this really makes no assumptions about that other than it will be an object at one point15:31
ndipanovthat will expose this one method15:31
ndipanovthe reason I need this one method that tells me if the flavor is changing15:31
*** pkoniszewski has joined #openstack-meeting15:32
*** nellysmitt has quit IRC15:32
ndipanovis that we can tell when we don't need to recalculate stuff15:32
ndipanovlike I said - not critical to go this route15:32
*** nellysmitt has joined #openstack-meeting15:32
bauzasndipanov: right, the problem is that we're dehydrating the Flavor object when sending it to the wire15:32
bauzasndipanov: we should just pass to the Scheduler what we already have15:33
ndipanovyeah that's not a problem for me for now but agreed15:33
ndipanovit should all be objects15:33
bauzasndipanov: cool that you found a workaround15:33
*** aranjan has joined #openstack-meeting15:33
ndipanovso basically15:33
ndipanovI'd like a review and ack that this is not insane from sched folks and dansmith if possible15:34
ndipanovbut not sure if I can put up the whole series this week since I am a bit swamped15:34
ndipanovif not - ah well, but I think moving to flavor objects in the scheduler with this is an easy win unless I missed an angle15:34
n0anondipanov, so you're asking for a review of your patch 158245, right?15:35
*** _nadya_ has joined #openstack-meeting15:35
*** SridharRamaswam1 has joined #openstack-meeting15:35
ndipanovwell more like -15:35
*** jang1 has quit IRC15:35
ndipanovtry to see the approach15:35
ndipanovand tell me if it;s OK to land it for a bugfix15:35
ndipanovand get some refactoring early and cheap15:35
bauzasndipanov: ack, will give you my voice15:36
*** SridharRamaswamy has quit IRC15:36
ndipanovnext patch in that series moves all use of flavor in filters to objects15:36
n0anoat this point I am hesitant about refactoring at this late stage in Kilo, even if it's easy15:36
ndipanovbut still failing tests so not posted15:36
ndipanovn0ano, that is reasonable15:36
* PaulMurray has to drop off now - sorry 15:36
bauzasndipanov: +115:36
*** dprince has quit IRC15:36
*** jsavak has quit IRC15:36
n0anoPaulMurray, NP, just read the logs15:36
ndipanovbut we;re still not that late from priorities pov15:37
ndipanovso think about it15:37
*** jcoufal has quit IRC15:37
*** jsavak has joined #openstack-meeting15:37
n0anondipanov, OK, we'll check it out15:37
*** jcoufal has joined #openstack-meeting15:37
n0anomoving on...15:37
*** absubram has joined #openstack-meeting15:37
n0ano#topic opens15:37
*** openstack changes topic to "opens (Meeting topic: gantt)"15:37
n0anoanything new for today?15:38
*** xuhanp has quit IRC15:38
n0anohearing crickets...15:38
*** kebray has joined #openstack-meeting15:39
bauzasI got one15:39
n0anobauzas, go ahead15:39
*** jang1 has joined #openstack-meeting15:39
*** ebalduf has joined #openstack-meeting15:39
bauzasbasically, restating what I said in the crowd15:39
bauzas(16:16:28) bauzas: btw. I'm taking the opportunity here to ask people to amend https://etherpad.openstack.org/p/kilo-nova-priorities-tracking and set the correct statuses on their ownerships for Launchpad BPs15:39
bauzasie. NeedsCodeReview, Slow Progress or In Progress15:40
n0anobauzas, +115:41
*** britthouser has quit IRC15:41
*** britthouser has joined #openstack-meeting15:41
*** Murali has joined #openstack-meeting15:41
n0anoanything else?15:41
bauzasnothing really much15:42
*** jsavak has quit IRC15:42
n0anoOK, so, as always, lots of reviews needed, everyone sharpen your pens and we'll talk next week.15:42
n0anotnx for attending15:42
n0ano#endmeeting15:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:42
openstackMeeting ended Tue Feb 24 15:42:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-02-24-15.00.html15:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-02-24-15.00.txt15:42
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-02-24-15.00.log.html15:42
* bauzas grabbing popcorn for reading the ML15:42
edleafebauzas: I'd recommend strong coffee :)15:43
*** stevemar has joined #openstack-meeting15:43
bauzasedleafe: I'm already at my 4th of the day15:43
bauzasand it's 4.40pm15:43
n0anobauzas, he said `strong`, not lots15:43
bauzasthat would be my 5th, severe hits expected15:43
*** ebalduf has quit IRC15:44
* bauzas trying not to turn into a psychopath15:44
edleafebauzas: too late15:45
edleafe:)15:45
*** numan has quit IRC15:45
*** yamamoto has quit IRC15:45
*** chandankumar_ has quit IRC15:45
*** david-lyle_afk is now known as david-lyle15:47
*** chandankumar has joined #openstack-meeting15:48
*** mrunge is now known as mrunge_afk15:49
*** mrunge_afk has quit IRC15:49
*** markvoelker has joined #openstack-meeting15:49
*** kebray has quit IRC15:50
*** zul has quit IRC15:50
*** rushiagr is now known as rushiagr_away15:50
*** zul has joined #openstack-meeting15:50
*** kebray has joined #openstack-meeting15:50
*** carl_baldwin has quit IRC15:50
*** Riddhi has quit IRC15:51
*** carl_baldwin has joined #openstack-meeting15:51
*** jang1 has quit IRC15:52
*** sarob has quit IRC15:54
*** jang has joined #openstack-meeting15:54
*** chandankumar has quit IRC15:54
*** BharatK has joined #openstack-meeting15:56
*** carl_baldwin has quit IRC15:56
*** kebray has quit IRC15:57
*** annegent_ has joined #openstack-meeting15:58
*** ddieterl_ has quit IRC16:01
*** ddieterly has joined #openstack-meeting16:02
*** Sukhdev has quit IRC16:02
*** coolsvap is now known as coolsvap_16:02
*** dboik has left #openstack-meeting16:02
*** shengjiemin has quit IRC16:03
*** jecarey has joined #openstack-meeting16:03
*** sarob has joined #openstack-meeting16:04
*** Riddhi has joined #openstack-meeting16:05
*** shengjiemin has joined #openstack-meeting16:05
*** Mandell has joined #openstack-meeting16:06
*** SridharRamaswam1 has quit IRC16:07
*** aranjan has quit IRC16:07
*** fnaval has joined #openstack-meeting16:08
*** hodos has joined #openstack-meeting16:08
*** hodos has left #openstack-meeting16:08
*** carl_baldwin has joined #openstack-meeting16:09
*** reed has joined #openstack-meeting16:09
*** doron_afk has quit IRC16:10
*** emagana has joined #openstack-meeting16:12
*** dprince has joined #openstack-meeting16:13
*** mdenny has joined #openstack-meeting16:13
*** otter768 has joined #openstack-meeting16:15
*** mpaolino has quit IRC16:15
*** changbl has joined #openstack-meeting16:16
*** rhe00 has quit IRC16:18
*** otter768 has quit IRC16:20
*** BrianB has joined #openstack-meeting16:20
*** BrianB has quit IRC16:20
*** vigneshvar has joined #openstack-meeting16:21
*** j05h has quit IRC16:22
*** dannywilson has joined #openstack-meeting16:23
*** j05h has joined #openstack-meeting16:23
*** tsekiyama has joined #openstack-meeting16:25
*** tsekiyama has quit IRC16:26
*** tsekiyama has joined #openstack-meeting16:26
*** Mandell has quit IRC16:27
*** amitgandhinz has joined #openstack-meeting16:27
*** amitgandhinz has quit IRC16:27
*** mpaolino has joined #openstack-meeting16:28
*** jdurgin1 has joined #openstack-meeting16:28
*** sdake__ has joined #openstack-meeting16:29
*** lpeer has quit IRC16:30
*** jcoufal has quit IRC16:30
*** noslzzp has quit IRC16:30
*** jtomasek has quit IRC16:31
*** sarob has quit IRC16:31
*** sdake_ has quit IRC16:33
*** unicell1 has quit IRC16:34
*** lazy_prince is now known as killer_prince16:35
*** jang has quit IRC16:35
*** dkranz has quit IRC16:36
*** SridharG has left #openstack-meeting16:36
*** jcoufal has joined #openstack-meeting16:37
*** che-arne has joined #openstack-meeting16:37
*** yamahata has quit IRC16:38
*** ebalduf has joined #openstack-meeting16:40
*** scheuran has quit IRC16:40
*** belmoreira has quit IRC16:42
*** radez_g0n3 is now known as radez16:42
*** spzala has joined #openstack-meeting16:44
*** vigneshvar has quit IRC16:44
*** adalbas has quit IRC16:44
*** ebalduf has quit IRC16:44
*** amitgandhinz has joined #openstack-meeting16:46
*** amitgandhinz has quit IRC16:46
*** msdubov_ has joined #openstack-meeting16:46
*** amitgandhinz has joined #openstack-meeting16:46
*** jcoufal has quit IRC16:47
*** dkranz has joined #openstack-meeting16:47
*** jang has joined #openstack-meeting16:47
*** paragan has quit IRC16:48
*** Murali has quit IRC16:48
*** Riddhi has quit IRC16:49
*** sergef has quit IRC16:52
*** jlanoux has quit IRC16:53
*** oanufriev has quit IRC16:54
*** msdubov_ has quit IRC16:55
*** msdubov_ has joined #openstack-meeting16:56
*** spredzy is now known as spredzy|afk16:56
*** jcoufal has joined #openstack-meeting16:57
*** shengjie_ has joined #openstack-meeting16:58
*** shengjiemin has quit IRC16:58
*** shengjie_ is now known as shengjiemin16:58
*** emagana has quit IRC16:58
*** MaxV has quit IRC16:59
*** emagana has joined #openstack-meeting16:59
*** amitgandhinz has quit IRC16:59
*** Swami has joined #openstack-meeting17:01
*** imsurit has joined #openstack-meeting17:01
*** scinawa has quit IRC17:01
*** yamahata has joined #openstack-meeting17:02
*** BaconIsKing has joined #openstack-meeting17:02
*** rmoe has quit IRC17:03
*** kebray has joined #openstack-meeting17:03
*** esker has joined #openstack-meeting17:03
*** emagana has quit IRC17:03
*** shengjiemin has quit IRC17:03
*** shengjiemin has joined #openstack-meeting17:04
boris-42#startmeeting Rally17:04
openstackMeeting started Tue Feb 24 17:04:54 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:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: Rally)"17:04
openstackThe meeting name has been set to 'rally'17:04
boris-42msdubov_: rvasilets__ ping17:05
*** emagana has joined #openstack-meeting17:05
*** yeungp has joined #openstack-meeting17:05
boris-42meteorfox: ping17:05
msdubov_boris-42:hi!17:05
meteorfoxboris-42: hi17:05
rvasilets__hi17:06
*** annegent_ has quit IRC17:06
*** absubram has left #openstack-meeting17:06
*** Riddhi has joined #openstack-meeting17:06
boris-42let's wait for others17:07
msdubov_ok17:07
*** amaretskiy has joined #openstack-meeting17:08
*** _nadya_ has quit IRC17:08
boris-42amaretskiy: ping17:08
amaretskiyhi17:08
boris-42okay let's start17:08
amaretskiysorry for my being late17:08
boris-42#topic Weekly updates17:09
*** openstack changes topic to "Weekly updates (Meeting topic: Rally)"17:09
boris-42We removed ALL oclo-incubator code WOOT17:09
msdubov_-3K SLOC!17:09
boris-42We add bunch of tests related to NovaKeyPairs17:09
*** Apoorva has joined #openstack-meeting17:09
*** annegent_ has joined #openstack-meeting17:10
boris-42I fixed a quite nasty bug related to warnings (we shouldn't display any warnings in commands that prints ouput in special format json/...)17:10
meteorfoxnice17:10
*** vigneshvar has joined #openstack-meeting17:10
meteorfoxalso I saw, the *aas is out too?17:11
*** mpaolino has quit IRC17:11
meteorfoxwas that part of the oclo-incubator code?17:11
boris-42meteorfox: let's disccuss this a bit later17:11
boris-42meteorfox: let me just finish overview=)17:11
boris-42meteorfox: and then this will be first topic17:11
meteorfoxalright sounds good17:12
boris-42So we add new script for Rally gates it's written in python and supprots tags17:12
boris-42Which will allow to use one job with multple tasks17:12
*** amotoki has quit IRC17:12
boris-42that are testing keystone v3 / with existing users / various version of python17:13
boris-42and so on17:13
boris-42As well we set jobs for Mirantis OpenStack17:13
*** evgenyf has quit IRC17:13
boris-42and now we are testing every patch against *real* deployment17:13
boris-42multinode=)17:13
boris-42so we will be able to test VM migration stuff17:14
boris-42in gates17:14
boris-42So we are going to cut version 0.0.2 of Rally during this week17:14
*** ttrifonov is now known as zz_ttrifonov17:14
boris-42Okay let's discuss in details17:14
boris-42#topic Rally AAS stuff17:14
*** openstack changes topic to "Rally AAS stuff (Meeting topic: Rally)"17:15
boris-42meteorfox: hey17:15
meteorfoxboris-42: hey17:15
boris-42meteorfox: so that AAS code was non working17:15
boris-42meteorfox: it was written in pecan17:15
boris-42meteorfox: and used oslo-incubator17:15
*** noelbk has joined #openstack-meeting17:15
boris-42we decided to chose another direction17:15
boris-42use flask17:15
meteorfoxboris-42: ah I see17:15
boris-42and make AAS on top of rally.api17:15
boris-42like a smart* code that adds 1-1 aas on top of rally.api17:16
boris-42msdubov_: refactored it a bit17:16
boris-42meteorfox: https://github.com/stackforge/rally/blob/master/rally/api.py so we will continue this work17:16
meteorfoxawesome17:16
*** khaldrogox has joined #openstack-meeting17:17
boris-42meteorfox:  so the idea is to avoid duplication of code17:17
*** nellysmitt has quit IRC17:17
meteorfoxboris-42: awesome, this looks good. I'm exited for this feature17:17
boris-42meteorfox: as well to reuse rally.cmd for bot (rally as cli tool and rally as a service)17:17
boris-42meteorfox: you can help and work on it)17:17
meteorfoxboris-42: :) sure17:18
*** nellysmitt has joined #openstack-meeting17:18
*** carl_baldwin has quit IRC17:18
*** rwsu-afk is now known as rwsu17:18
*** samueldmq has joined #openstack-meeting17:19
boris-42so let's to move to next topics17:19
*** erlon has joined #openstack-meeting17:19
boris-42#topic new constant runner17:19
*** openstack changes topic to "new constant runner (Meeting topic: Rally)"17:19
boris-42msdubov_: any news  ?17:19
*** vivek-ebay has joined #openstack-meeting17:19
msdubov_boris-42 yes17:19
*** emagana has quit IRC17:19
msdubov_I believe I have written all the unit tests I wanted for the patch: https://review.openstack.org/#/c/155225/17:19
msdubov_And it's no longer a WIP-patch17:20
msdubov_So boris-42 amaretskiy redixin You're welcome to review & test it17:20
amaretskiyok17:20
msdubov_I have also removed a functional test that checked that the number of iterations always grows17:20
*** coolsvap_ is now known as coolsvap17:20
*** rmoe has joined #openstack-meeting17:21
msdubov_Because actually with the constant runner it may be the case that the iteration No. (i+1) starts before iteration No. i17:21
msdubov_(Not actually starts, but is logged)17:21
msdubov_So the iteration numbers in logs are not always strictly increasing17:21
*** rhe00_ has joined #openstack-meeting17:21
boris-42msdubov_: yep they are not17:22
*** jang has quit IRC17:22
msdubov_boris-42: it seems though that for the RPS runner they are often in-order :)17:22
msdubov_boris-42:Just an observation17:22
*** jungleboyj has quit IRC17:23
msdubov_boris-42: Basically that's it for the constant runner17:23
msdubov_the constant for duration runner, as discussed, will be modified later17:23
*** matrohon has quit IRC17:23
boris-42msdubov_: ok17:23
boris-42msdubov_: I will try to review it17:23
*** shengjiemin has quit IRC17:23
boris-42#topic Murano patches17:23
*** openstack changes topic to "Murano patches (Meeting topic: Rally)"17:23
boris-42rvasilets__: hey hey17:23
*** jang has joined #openstack-meeting17:23
rvasilets__Hi17:24
*** bill_az has quit IRC17:25
*** ibiris is now known as ibiris_away17:25
rvasilets__How i have separating from Murano base another patch its about refactor ImageGenarator and Validation17:25
rvasilets__Just Murano stuff is okey now and its only wait to be separated from ImageGenerator17:26
rvasilets__eom17:26
*** penick has joined #openstack-meeting17:26
*** afazekas has quit IRC17:26
boris-42rvasilets__: okay I hope you will separate it soon17:27
rvasilets__I hope too17:27
boris-42rvasilets__: it acutally doens't require any code changes17:27
boris-42rvasilets__: just git 80lvl skills17:27
boris-42=)17:27
rvasilets__yes, just copy paste17:27
boris-42rvasilets__: no there is no need to copy paste =(17:27
rvasilets__and delete)17:27
*** aepifanov has quit IRC17:27
*** penick has quit IRC17:27
boris-42rvasilets__: nope..17:27
boris-42rvasilets__: I will tell you how to do it after meeting17:28
*** emagana has joined #openstack-meeting17:28
boris-42okay let's move to next topic17:28
boris-42#topic Scalable graphs17:28
*** openstack changes topic to "Scalable graphs (Meeting topic: Rally)"17:28
*** afazekas has joined #openstack-meeting17:28
boris-42amaretskiy: how is your patch? realted to graphs?17:28
amaretskiylast week i removed WIP from https://review.openstack.org/#/c/146814/17:28
amaretskiythis patch is working17:28
amaretskiyhowever today it appeared in merge conflict17:29
amaretskiyso I'm going to fix conflict + fix some tests (reviewed) tomorrow17:29
*** baoli has quit IRC17:29
amaretskiyso reviews are welcome17:29
amaretskiyalso there are >1k loc17:29
*** shengjiemin has joined #openstack-meeting17:29
amaretskiyso maybe i should split thi spatch17:30
amaretskiyinto 2 parts?17:30
amaretskiywhat do you think?17:30
*** bill_az has joined #openstack-meeting17:30
*** leeantho has joined #openstack-meeting17:30
*** tiswanso has quit IRC17:30
*** baoli has joined #openstack-meeting17:30
*** fzdarsky has joined #openstack-meeting17:31
*** cdub has quit IRC17:31
*** hemnafk is now known as hemna17:31
*** markstur has joined #openstack-meeting17:31
boris-42amaretskiy: I think it will be great17:31
boris-42amaretskiy: to split it to 2 parts17:31
amaretskiyokay17:31
*** markstur has left #openstack-meeting17:31
*** tiswanso_ has joined #openstack-meeting17:31
amaretskiyagreed17:31
amaretskiyeom17:31
*** Riddhi has quit IRC17:32
boris-42amaretskiy: maybe as first step is deleting chart/histogram17:32
boris-42amaretskiy: and moving it to charts (with refactoring) + tests17:32
amaretskiythis is not a simple question17:32
boris-42amaretskiy: it iwll help a lot17:32
boris-42amaretskiy: why it is not simple question? it will be simple to do17:32
*** amrith has joined #openstack-meeting17:33
amaretskiyi think sthis split should not take a lot of time, but i do not see if this possible17:33
*** tomoe_ has quit IRC17:33
amaretskiyi will consider if it is possible to split thi spatch with minimal work17:33
amaretskiymaybe it is a good idea to just add new charts classes + tests17:34
amaretskiywithout touching plot.py at all17:34
*** femto has joined #openstack-meeting17:34
amaretskiysince charts/histogram.py is completely rewritten17:35
boris-42amaretskiy: yep you can make first charts17:35
amaretskiyso i guess the first patch will simply add new charts classes17:35
boris-42amaretskiy: with tests17:35
amaretskiyyes17:35
boris-42amaretskiy:  and the remove old processing stuff and switch to new charts17:35
boris-42amaretskiy: yep that makes sense17:35
amaretskiysure17:35
boris-42amaretskiy: okay let' move to next stuff17:36
boris-42#topic Rally Plugins17:36
*** openstack changes topic to "Rally Plugins (Meeting topic: Rally)"17:36
*** unicell has joined #openstack-meeting17:36
*** marun has joined #openstack-meeting17:36
boris-42Okay I am working on unification of plugins17:36
boris-42Finally I start seeing full picture17:36
boris-42so I am going soon to push new patch17:36
*** tnurlygayanov has quit IRC17:37
boris-42that changes plugin base17:37
*** femto has quit IRC17:37
boris-42and allow to make from functions plugins17:37
boris-42so this thing was the very last blocking thing that I didn't know how to resolve17:37
boris-42as well I won't touch bese.context()17:37
*** annegent_ has quit IRC17:37
boris-42and instead of removing name I will just call plugin decorator inside it17:37
boris-42so at least scenarios, context will be backward compbale17:38
*** ibiris_away is now known as ibiris17:38
*** adalbas has joined #openstack-meeting17:38
boris-42SLA stuff have to be refactored one more time17:38
boris-42as well runners, deploy engines and server provides17:38
boris-42but as far as I know nobody is writing those plugins so it's not a big deal to change them17:39
boris-42After we switch to plugin base I will work on moving validation mechanism to plugin Base17:39
boris-42this will allow us to use the same validation mechanism for all plugins that we have17:39
msdubov_boris-42, What will be the changes to SLA?17:40
*** rhe00_ is now known as rhe0017:40
boris-42msdubov_: I will introduce @sla decorator17:40
boris-42msdubov_: and remove option_name17:40
*** ebalduf has joined #openstack-meeting17:41
msdubov_boris-42: okay, thanks17:41
*** david8hu has joined #openstack-meeting17:42
boris-42so okay17:43
boris-42#topic Open Discussion17:43
*** openstack changes topic to "Open Discussion (Meeting topic: Rally)"17:43
boris-42anybody wants to discuss anything?17:43
amaretskiyno17:43
meteorfoxno17:43
msdubov_nope17:43
*** lhcheng_afk has joined #openstack-meeting17:43
*** banix has joined #openstack-meeting17:44
rvasilets__no17:44
*** derekh has quit IRC17:44
*** moha_hunt has joined #openstack-meeting17:44
*** ebalduf has quit IRC17:45
*** aranjan has joined #openstack-meeting17:45
boris-42Okay I don't have as well =)17:45
boris-42Have a nice day=)17:45
boris-42#endmeeting17:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:45
openstackMeeting ended Tue Feb 24 17:45:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-02-24-17.04.html17:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-02-24-17.04.txt17:45
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-02-24-17.04.log.html17:45
*** msdubov_ has quit IRC17:45
*** amaretskiy has left #openstack-meeting17:46
*** meteorfox has left #openstack-meeting17:46
*** browne has joined #openstack-meeting17:46
*** carl_baldwin has joined #openstack-meeting17:47
*** ygbo has quit IRC17:48
*** jungleboyj has joined #openstack-meeting17:49
*** sahid has quit IRC17:49
*** chandankumar has joined #openstack-meeting17:52
*** ksavich has joined #openstack-meeting17:54
*** shengjiemin has quit IRC17:55
*** etoews has joined #openstack-meeting17:56
*** cody-somerville has quit IRC17:56
*** SridharRamaswamy has joined #openstack-meeting17:57
*** haneef has joined #openstack-meeting17:58
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, wanghong17:58
morganfainberghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting17:58
morganfainbergIt's that time again :)17:58
rodrigodso/17:58
ayoungWeee!17:58
morganfainberg(Will start about 2mins late fyi)17:58
amakarovo/17:58
raildo_awayo/17:59
*** henrynash has joined #openstack-meeting17:59
stevemaro/17:59
marekdWelcome17:59
dstaneko/17:59
stevemar\o/17:59
lbragstadhey17:59
lhcheng_afko/17:59
*** pnavarro has quit IRC17:59
* lbragstad is ready for Vancouver 18:00
*** lhcheng_afk is now known as lhcheng18:00
jogoo/18:00
*** ibiris is now known as ibiris_away18:00
marekdlbragstad: how come?18:00
*** coolsvap is now known as coolsvap_18:00
*** bdpayne has joined #openstack-meeting18:01
henrynashhi18:01
morganfainbergI'm getting coffee. Will be starting a minute or so more before we start.18:01
*** carl_baldwin has quit IRC18:01
lbragstadmarekd: itchin' for a summit!18:01
*** britthouser has quit IRC18:01
*** annegent_ has joined #openstack-meeting18:01
*** pritesh has joined #openstack-meeting18:01
*** roampune has joined #openstack-meeting18:01
marekd:D18:01
samueldmqo/18:01
marekdwhat's that 'short lived feature branch' ?18:01
*** etoews has quit IRC18:02
morganfainbergOk18:02
morganfainbergWelcome!18:02
morganfainberg#startmeeting keystone18:02
openstackMeeting started Tue Feb 24 18:02:33 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
morganfainbergMorning all!18:02
marekdyeah..morning :-)18:03
*** sbalukoff has quit IRC18:03
*** ignacio-scopett1 has joined #openstack-meeting18:03
morganfainbergGoing to get started wth the agenda and then move on to things like what bps we need to push to liberty.18:03
morganfainberg#topic Using short lived feature branchs18:03
*** openstack changes topic to "Using short lived feature branchs (Meeting topic: keystone)"18:03
morganfainbergjogo: o/18:04
*** jcoufal has quit IRC18:04
*** dulek has quit IRC18:04
*** jcoufal has joined #openstack-meeting18:04
jogomorganfainberg: you want to explain it? most of the notes are in the agenda18:04
*** SridharRamaswamy has quit IRC18:04
*** ignacio-scopetta has quit IRC18:04
morganfainbergI'm going to let you present it. You did a great job summarizing it yesterday.18:05
*** htruta has joined #openstack-meeting18:05
jogosure18:05
morganfainbergThe notes are there. But just a quick summary and then open for discussion.18:05
*** SridharRamaswamy has joined #openstack-meeting18:05
* morganfainberg drinks coffee.18:05
*** bvandenh has quit IRC18:05
jogoquick summary: a keystone-core can sponsor the creation of a feature branch for a blueprint18:06
*** qwebirc80846 has joined #openstack-meeting18:06
*** Mandell has joined #openstack-meeting18:06
jogothe big difference with what happened previously with HMT is, the keystone core sponsor can nominate anyone they want to be core on the feature branch18:06
morganfainbergThis is a new concept to try, btw. So, open comments on it as well.18:06
*** kmartin has quit IRC18:06
morganfainbergBefore we try it that is.18:07
*** britthouser has joined #openstack-meeting18:07
*** dane_leblanc has quit IRC18:07
jogoso the standard 2 +2 applies to the feature branch, except one of the +2s can come from a feature-branch core18:07
ayoungOnce the feature branch is "complete"  it takes standard core to merge as per normal18:07
*** armax has quit IRC18:07
rodrigodsI have one question: how the branch rebase against master will work? In a regular feature branch we'd need to ask a specific group to perform it18:07
*** dane_leblanc has joined #openstack-meeting18:07
dstanekinteresting - so a +2 from a core and a +2 from someone else?18:07
jogoayoung: yup, although the merge review should not be a full code review18:07
*** jamielennox has joined #openstack-meeting18:07
*** ndipanov has quit IRC18:07
*** breton has joined #openstack-meeting18:07
lbragstadthe other +2 has to be a core on the feature branch though, right?18:08
marekdjogo: one +2 who can be a master in tat particular topic, but no necessaarilly is a Keystone core, right?18:08
*** doude has joined #openstack-meeting18:08
jogolbragstad: or a regular keystone core18:08
*** dane_leblanc has quit IRC18:08
*** britthouser has quit IRC18:08
ayoungand then we do a merge of the feature branch, not just a rebase18:08
*** britthouser has joined #openstack-meeting18:08
jogomarekd: yes, so instead of requiring two keystone core +2s, the feature branch patches require one keystone-core +2 and another +218:08
morganfainbergrodrigods: any feature branch core or keystone core can do the merge from master to the topic branch , but that is a documentation / training thing to help make that easy18:08
lbragstadso are we intending that this process takes place of our experimental phase?18:08
amakarovinteresting concept, so we want branch-owners to compete for core'ship in the future :)18:09
*** prad has quit IRC18:09
morganfainberglbragstad: no.18:09
*** jcoufal has quit IRC18:09
morganfainberglbragstad: this would be to land the code initially. Nothing else changes.18:09
*** dane_leblanc has joined #openstack-meeting18:09
*** jang has quit IRC18:09
dstaneki think this is probably a good idea, but we need to be careful at first18:10
jogothe motivation here, is to empower people who keystone-core considers domain experts and trusts them, but who don't have enough bandwidth general keystone knowledge to be a full keystone-core at the moment18:10
lbragstaddoes every spec have to follow this criteria?18:10
morganfainbergayoung: merge (final) to master is keystone-core only.18:10
jogolbragstad: no, this is a new idea and I am looking for a guinea pig18:10
lbragstadjogo: ok18:10
marekdjogo: makes sense.18:10
*** jang1 has joined #openstack-meeting18:11
raildo_awayjogo I dont like this term :( haha18:11
stevemarwhat the kind of work that would be proposed to a feature branch?18:11
rodrigodsjogo, makes sense. [2]18:11
jogofeature branches don't make sense for things that: touch a lot of code all over the place (rebase hell) etc18:11
ayoungjogo, you just ruled out Keystone18:11
lbragstadI think that work flow worked well with the HTM stuff because the people maintaining it stayed on top of it18:11
*** devlaps has joined #openstack-meeting18:11
*** baoli has quit IRC18:11
*** jacorob has left #openstack-meeting18:11
marekdstevemar: HTM for instance I think18:11
jogoayoung: so morganfainberg had a blueprint in mind18:11
rodrigodsthe problem with the HMT feature branch was mainly the lack of reviews18:11
morganfainbergThe ae token work would be a great target (if we had this concept earlier). Ae token will not use this though.18:11
rodrigodsso it took too long to start merging18:11
*** raildo_away is now known as raildo18:12
rodrigodsso this short term feature branch seems a nice approach to try to improve this18:12
amakarovrodrigods, ++18:12
*** leonchio_ has joined #openstack-meeting18:12
raildorodrigods, ++18:12
morganfainbergBut the kind of work that ae token is, relatively isolated is the type of work that this makes sense for. The hmt reseller stuff might be a good one as well.18:12
*** jacorob has joined #openstack-meeting18:12
rodrigodswho are the keystone-cores interested in working in it?18:13
amakarovwe need criteria how not to drown in a heap of branches18:13
rodrigods(reseller)18:13
lbragstadamakarov: ++18:13
jogoamakarov: well for now the idea is to just try this once and see how it goes18:13
dstanekjogo: so just pick one new feature branch for the initial process?18:14
marekdlike hmt18:14
jogodstanek: yup18:14
amakarovjogo, I think we need at least 2, better 3 branches to see how it'll go and, more important - merge18:15
ayoungKeystone client policy work18:15
*** Longgeek has quit IRC18:15
dstaneki don't see any reason not to try this then; we can just be extra careful on the merge for those that would be worried18:15
morganfainbergayoung: ++18:15
*** vigneshvar has quit IRC18:15
ayoungaccess info18:15
jogoamakarov: well just because one works doesn't mean its a good idea. but figure starting with 1 branch and take it slow18:15
ayounglets do this in the client18:15
rodrigodsthis would worked with assignments split too18:15
*** marcusvrn1 has quit IRC18:16
*** adalbas has quit IRC18:16
ayoungyep...would have18:16
lbragstadjogo: have some other projects started this workflow?18:16
morganfainbergrodrigods: unfortunately no. Touched too much stuff.18:16
jogolbragstad: no, your the first :)18:16
lbragstad\o/18:16
amakarovjogo, ++ for step-by-step approach18:16
*** otter768 has joined #openstack-meeting18:16
*** baoli_ has joined #openstack-meeting18:16
*** ignacio-scopetta has joined #openstack-meeting18:16
morganfainbergSo the biggest concern with using a keystone server bp is we are 10 days from milestone. So I think we can't do it with server this cycle.18:16
marekdmorganfainberg: ++18:17
rodrigods:(18:17
ayoungClient makes more sense anyway18:17
amakarovjogo, I just want to remind that 1 branch is not enough to approve entire concept - it's just 1st step18:17
morganfainbergjogo: but we can do client/middleware easily.18:17
jogomorganfainberg: good idea18:17
rodrigodspolicy stuff18:17
*** ignacio-scopett1 has quit IRC18:17
*** changbl has quit IRC18:17
rodrigods^18:17
ayoungjamielennox, anything you can think of that would make a good topic branch in client?18:18
*** marcusvrn1 has joined #openstack-meeting18:18
jamielennoxayoung: i have a whole bunch of splitting up auth_token middleware that is isolated and in queue - it's fairly trivial though18:18
*** qwebirc80846 has quit IRC18:18
lbragstadthat sounds like a good candidate...18:19
rodrigodsk2k support?18:19
dstanekwe would need something that is being worked on my a non-core. do we have anything like that in the client?18:19
morganfainbergdstanek: ++18:19
jamielennoxthere is some HMT stuff that i need to get back to reviewing18:20
bretonAlembic ;)18:20
*** harlowja has joined #openstack-meeting18:20
lbragstadayoung: was there anyone else driving the access info stuff?18:20
bretonI think there will be 4-5 patches regarding it18:20
ayounglbragstad, it was under pressure from morganfainberg , but he hasn't been actively coding it18:20
*** ChuckC has quit IRC18:20
morganfainbergAlso if someone wants to do the sql migration collapse this cycle besides me, that can land post k3 and might be a good candidate for this.18:20
*** ChuckC has joined #openstack-meeting18:21
bretono/18:21
* breton wants18:21
ayoungI'd be willing to hand over +2 on the access info to at least one non core18:21
morganfainbergayoung: yes. We still need it but we are addressing the klwt first.18:21
*** otter768 has quit IRC18:21
morganfainbergayoung: but that is still really important.18:21
lbragstadayoung: I thought david8hu was waiting on that stuff for the token provider cleanup stuff18:21
ayoungyes, he is18:22
*** annegent_ has quit IRC18:22
*** jang1 has quit IRC18:22
morganfainbergSo it doesn't make sense unless there is more than 1 non-core interested as well. If 1-non core is coding it and no one else is interested, we are limited back to core reviewers only.18:23
morganfainbergBut I think we have some candidates to work from.18:23
rodrigods++18:24
*** joesavak has joined #openstack-meeting18:24
lbragstadis there going to be a rebase criteria or is it just as the committer sees fit?18:24
*** harlowja has quit IRC18:24
*** harlowja has joined #openstack-meeting18:24
morganfainbergIt will need to be in sync with master before t can be merged back in. Frequent rebase/ / syncs make that easier, but it would be up to the branch core team to determine.18:24
morganfainbergSince merge commits still need review.18:25
*** lpmulligan has quit IRC18:25
morganfainbergRemember ff-only does not work to sync things.18:25
rodrigodsmorganfainberg, having it in the reseller stuff would somehow ease our internal process here, but we have the milestone concern18:25
marekdrodrigods: you are a big team.18:26
marekdand could more work face2face18:26
rodrigodsmarekd, ++18:26
*** Swami has quit IRC18:26
morganfainbergrodrigods: correct and that is why I don't want to push it for server topics. 10 days is very limited. But I'd be willing to let it be used if you guys feel confident about it.18:26
morganfainbergBut I want to be clear we aren't jeapordiIng that code for this cycle based on trying this out.18:26
ayounglets stick to client for now18:27
*** changbl has joined #openstack-meeting18:27
ayoungand use it for the server in LizardLove18:27
amakarovayoung, ++18:27
morganfainbergayoung: sure. We should have a lot more lead time on features with an earlier spec proposal time.18:27
rodrigodsmorganfainberg, yes, I'm just not that confident that it would merge if stayed in master as well :)18:27
rodrigodsanyway...18:28
morganfainbergWe could do this for the hmt pieces of client as well (if any are still needed)18:28
*** marcusvrn has joined #openstack-meeting18:28
morganfainbergWhich still puts a larger team in the driver seat for tying this out.18:28
marekdclient is mostly about auth, and big parts we move to separate repos (like kerberos, federation etc)18:28
rodrigodsmorganfainberg, there is a couple of changes under review from the first HMT steps18:28
*** adalbas has joined #openstack-meeting18:29
morganfainbergmarekd: yeah I'm fighting pypi on that atm. Something is broken.18:29
rodrigodsmarekd, I think k2k auth support would be nice18:29
*** marcusvrn1 has quit IRC18:29
rodrigodsand could be a nice candidate for the feature branch18:29
marekdrodrigods: we have keystoneclient_federation repo and this would very likely go there.18:29
rodrigodsmarekd, ahh, true18:29
morganfainbergmarekd: ++18:29
marekdwell...we could add a feature branch in ksc_fdr but...18:29
stevemarrodrigods, yeah we are missing a few bits for k2k support for ksc(-fed)18:29
*** jang1 has joined #openstack-meeting18:30
morganfainbergjogo: sorry this is hard to figure out the best starting one ;). Since we have to eliminate keystone server. Unless we pick something like the testing spec.18:30
morganfainbergThat can land post k318:30
*** jungleboyj has quit IRC18:31
jogomorganfainberg: no worries, the timing for trying this idea is not ideal18:31
*** gyee has joined #openstack-meeting18:31
ayoungmorganfainberg, I'll volunteer the access info for the client.  Can we accept that and move on?18:32
jamielennoxthe problem is there are generally not that many long running branches on client or middleware18:32
ayoungespecially if it means I get more eyes18:32
lbragstadwe need another non core who is interested in it thought, right?18:32
morganfainbergayoung: find some non-cores interested and we can use that18:32
rodrigodsayoung, morganfainberg you can add me18:33
morganfainbergAnyway I think we will need to look over some options and get back to you jogo   For sure in liberty we will look at this for server.18:33
ayoungdavid8hu, you here?18:33
jogomorganfainberg: sounds like a solid plan18:33
ayoungrodrigods, thanks18:33
david8huI am here18:33
morganfainbergProvided we don't have anything craaaaazy happen before that that makes this an awful idea.18:33
ayoungdavid8hu, we want to do a topic branch for access info.  Interested in being able to review it18:33
ayoung?18:33
*** baoli_ has quit IRC18:33
david8huYes, I can help review it.18:34
ayoungmorganfainberg, there you go18:34
ayoungmake those two core, and I can post code, too18:34
ayoungor...topic-core?18:34
morganfainbergOk so moving on (will circle up with jogo after the meeting on this)18:34
ayoungwhatever the term is18:34
ayoungtopicore18:34
ayoungManticore18:35
*** penick has joined #openstack-meeting18:35
morganfainberg#topic pushing bps / specs to liberty and beyond18:35
*** openstack changes topic to "pushing bps / specs to liberty and beyond (Meeting topic: keystone)"18:35
morganfainberg#link https://launchpad.net/keystone/+milestone/kilo-318:35
ayoungbacklog all the specs18:35
morganfainbergSo we have things that are really unlikely to land.18:35
ayoungI think we should drop the juno. kilo subdirs18:35
morganfainbergayoung: no.18:36
ayoungand ju8st have all specs submitted to keystone.  It will keep the urls consistent18:36
ayoungmorganfainberg, yes18:36
morganfainbergayoung: no18:36
ayounglet me finish18:36
marekdthere are some specs moved to backlog, is it desired to simply +2 em so they get merged there?18:36
lbragstadI like the subdirs because they help keep track of what happened and when18:36
ayoungthe BP process tracks where they land.  we are confusing things18:36
morganfainbergI need to have an idea what is targeted for the specs for a cycle18:36
ayoung having them in one dfir means:  there are approved...18:36
*** lpmulligan has joined #openstack-meeting18:36
morganfainbergBps are broken. Still do not make me deal with LP more.18:36
ayoungwe do that for KC and middleware anyway18:36
morganfainbergSeriously LP is a reason enough to keep the dirs.18:36
dstaneki was planning on putting any of my open specs in the backlog - would that be a good idea?18:37
morganfainbergdstanek: yes.18:37
*** adalbas has quit IRC18:37
ayoungmake a file that says which specs are in which release and put it in the specs repo then18:37
ayoungseriously, make it simpler18:37
morganfainbergayoung: when we can ditch LP we can look at other workflows.18:37
ayoungfor now...everytiing goes in backlog18:37
*** jang1 has quit IRC18:37
morganfainbergayoung: are you dealing with release management? Please let's not make this worse right now.18:38
ayoungmorganfainberg, I thought the K3 page linked to the BPs, not the specs?18:38
ayoungDidn;'t thinkm you were capable of ignoring BPs yet18:38
*** jang has joined #openstack-meeting18:38
morganfainbergA little more work on the specs is easier for me for now.18:38
ayounghttps://launchpad.net/keystone/+milestone/kilo-318:38
morganfainbergIf the next ptl wants to change this they can.18:38
ayounganyway...it is not for Kilo18:38
ayoungit is for Limabean and beyond18:39
*** ivar-lazzaro has joined #openstack-meeting18:39
morganfainbergThis is enough of a headache that please leave this bit of it to the ptl to manage how that workflow looks. Seriously the directories help.18:39
morganfainbergAt least me18:39
morganfainbergFor now.18:39
* gyee is here to write code only18:40
ayoungIt means that we get a slew of -2s that mean nothing.   I'm all for letting Kilo go throuigh, just that all  bumped specs go to backlog, right?18:40
*** rfolco has quit IRC18:40
ayoungcan git do symlinks....?18:41
morganfainbergBack to the topic at hand. Anything that is not likely to land in k, abfab ldap filtering. Sql extra attrs etc will be bumped18:41
morganfainbergThis also likely means the provider cleanup will be pushed.18:41
henrynashmorganfainberg: ldap filtering is done (just marked it so)18:41
morganfainbergWe need that cleanup, but it can land first thing in liberty. The klwt will land first in either case.18:41
*** ebalduf has joined #openstack-meeting18:41
gyeewait, AE have a dependency on provider cleanup18:41
morganfainberghenrynash: thanks.18:41
gyeeisn't it?18:41
*** baoli has joined #openstack-meeting18:42
morganfainberggyee: no we broke that because klwt has a higher priority. We really need it now.18:42
*** cody-somerville has joined #openstack-meeting18:42
*** jdurgin1 has quit IRC18:42
morganfainbergThe provider cleanup needs to happen. We can make that hard dep and land klwt18:42
gyeemorganfainberg, that means both needs to land or none at all for kilo18:43
morganfainbergSo inverting the order. The added overhead for cleaning up a new provider is relatively low. :(18:43
morganfainbergNo.18:43
morganfainbergKlwt will land. Provider cleanup could land next cycle first off. As soon as rc is cut.18:43
*** moha_hunt has quit IRC18:43
gyeek, I need to re-read that code then18:43
*** rfolco has joined #openstack-meeting18:43
morganfainbergThis is because we are at a hard ff deadline in 10 days.18:43
morganfainbergIf provider lands (blocking on client stuff) we can land both. But j expect provider to land 1st thing in l18:44
*** chandankumar has quit IRC18:44
gyeethat's fine, less moving part is better18:44
morganfainbergdavid8hu: we will get you working with Adam to help unblocking the provider cleanup as well.18:44
morganfainbergSo please review the bps on the kilo-3 milestone. If they are complete mark them as such.18:45
stevemarmorganfainberg, so we're going to bump 1) token provider cleanup, 2) remove extra attrs, 3) abfab18:45
morganfainbergYep for sure the last two stevemar18:45
david8husure.  I am able to make progress without the new access info so far.18:45
bretonit'd be great to hide non-kilo specs somehow18:45
*** carl_baldwin has joined #openstack-meeting18:45
gyeereviews, reviews, and mo reviews18:45
stevemarhenrynash, ^ bumping 2 is all you, you good with that?18:46
bretonor make a list of really-high-priority changesets18:46
marekdbreton: from keystone-specs repo ?18:46
morganfainbergdavid8hu: and that work will still be super important.18:46
*** jang has quit IRC18:46
henrynashstevemar:18:46
*** ebalduf has quit IRC18:46
bretonmarekd: from everywhere on keystone-related review.openstack.org18:46
morganfainbergdavid8hu: it likely won't be too bad to rebase pose rc18:46
henrynashyes, remove extra attrs can be bumped (I think I already did!)18:46
*** roaet has left #openstack-meeting18:46
morganfainbergbreton: there is a link in the topic of the keystone channel for high prio reviews.18:46
marekd++18:46
david8humorganfainberg:  ok18:47
bretonmorganfainberg: yes, and we are going to move some of them to L, right?18:47
bknudsonhttp://status.openstack.org/reviews/ sorts reviews by a score if that helps to prioritize reviews.18:47
marekdmorganfainberg: so,  shall we +1/+2 specs that were moved to backlog, or -2 them for until L cycle is open?18:47
morganfainbergAll -2 specs proposed (gerrit only ) will be either abandoned or need to be reproposed against backlog.18:47
*** moha_hunt has joined #openstack-meeting18:47
*** vigneshvar has joined #openstack-meeting18:48
*** krtaylor has quit IRC18:48
morganfainbergmarekd: I'll take care of -2s for non backlog specs. Any that are backlog should already have -2 cleared18:48
morganfainbergBut please propose them to backlog. It is lower cost to18:48
*** cody-somerville has quit IRC18:48
bretonthere are almost 30 high-priority reviews. Are they all really-really high priority for the next 10 days?18:48
morganfainbergRename a file than deal with massive lists.18:48
morganfainbergbreton: that will be cleaned up as I push specs beyond to l.18:49
marekdaha, cause i did a bunch of +1 of keystone-specs/backlog specs cause it was polluting my next-review list.18:49
morganfainbergThat is the current list slated for k.18:49
lbragstadthose reviews will have to be unstarred too,18:49
lbragstadmorganfainberg: I can help with that one your clean up is done18:49
morganfainbergmarekd: perfectly fine to +1/+2 backlog specs.18:49
lbragstadonce*18:49
marekdmorganfainberg: will change.18:49
morganfainbergIf they are good we should approve them for backlog :)18:49
rodrigods++18:50
morganfainbergIt means anyone can grab them and know we like the idea.18:50
morganfainbergIt lowers the barrier to entry for new developers / contributors to work on features.18:50
*** sdake_ has joined #openstack-meeting18:50
ayoungaccording to https://launchpad.net/keystone/+milestone/kilo-3  the only thing marked essentila is marekd 's  Keystone to Keystone Service Providers18:50
ayoungthen 3 high18:50
morganfainbergayoung: and that is still essential.18:51
ayoung Allow for mapping to existing user in federated workflow18:51
ayoungalso marekd18:51
ayoung Improve list role assignments filtering performance18:51
ayoungand18:51
ayoungraildo, Implementing Reseller Use Case with the Hierarchical Multitenancy.18:51
morganfainbergYep.18:51
ayoungso.. I would say priority goes to reviews for those features18:51
*** SumitNaiksatam has joined #openstack-meeting18:51
ayoungkindof hard to tell from the BP page which are still  outstanding18:51
morganfainbergAnyway. I'll have the high priority review list cleaned up today.18:51
bretonk, great18:52
*** marcusvrn1 has joined #openstack-meeting18:52
morganfainbergLast item and the. We are done.18:52
ayoungK2k  has several reviews, most of which are merged18:52
raildoayoung, ++18:52
*** marcusvrn has quit IRC18:52
*** zul has quit IRC18:52
rodrigodswe need k2k in kc18:52
*** SridharRamaswamy has quit IRC18:52
marekdayoung: service provider in service catalog was problematic18:52
*** achanda has joined #openstack-meeting18:52
*** zul has joined #openstack-meeting18:52
ayoungrodrigods, not a Keystone server/M3 deadline though18:52
marekdand that's why it is stalled18:52
rodrigodsayoung, ++18:52
morganfainbergSo moving on18:52
ayoungmarekd, as I said, we had considered that years ago and discarded it18:52
ayounglets talk in #openstack-keystone afterwards...move on morganfainberg18:53
morganfainberg#topic bps that do not need specs18:53
*** openstack changes topic to "bps that do not need specs (Meeting topic: keystone)"18:53
morganfainberg#link https://blueprints.launchpad.net/keystone/+spec/assignment-manager-cleanup18:53
lbragstad~ 7 minutes left18:53
samueldmqmorganfainberg, was from last week ... sorry18:53
*** penick has quit IRC18:53
*** zul has quit IRC18:53
*** johnthetubaguy is now known as zz_johnthetubagu18:53
*** penick_ has joined #openstack-meeting18:53
morganfainbergDid we decide?18:53
morganfainbergI don't remember.18:53
*** zul has joined #openstack-meeting18:53
samueldmqno ...18:54
morganfainbergSo then this week is when we talk it through :)18:54
morganfainbergIf it wasn't talked about.18:54
samueldmqstevemar told me to work and see what happens ... to change it to wip :p18:54
*** sdake__ has quit IRC18:54
samueldmqanyway ..18:54
samueldmqthe idea is to have several methods that honor inheritance and grouping in role assignments18:54
*** rprakash has quit IRC18:55
morganfainbergSo we can take a look. Does that need a spec? Please look it over quickly. If it isn't quick/ we have concerns it can require a spec18:55
samueldmqusing the new list_role_assignments ... that correctly honor everything needed18:55
morganfainbergA spec requires liberty cycle though.18:55
*** kmartin has joined #openstack-meeting18:55
*** dane_leblanc has quit IRC18:55
*** MarkAtwood has joined #openstack-meeting18:55
samueldmqit's quite simple ... for each method which honor inheritance and grouping membership, re-use list_role_assignments instead of implementing it by itself18:56
samueldmqand that's done18:56
samueldmqno changing in the behavior18:56
morganfainbergAt a glance it looks like something that doesn't need a spec and doesn't change behavior n18:56
samueldmqexactly18:56
rodrigods++ reuse code :)18:56
morganfainbergSo I'd be ok with this landing anytime. But anyone else have thoughts / concerns?18:56
gyee++ for improving the role assignment stuff18:57
*** adalbas has joined #openstack-meeting18:57
henrynashsamueldmq: my only concern is we have a long line of patches queued up….so this has to go on the end., no?18:57
samueldmqin addition, this is strictly related to removing the old style metadata ... that re-uses list_role-assignments as well :)18:57
henrynashsamueldmq: but as you kno, I’ve been puching this re-use, so conceptually I’m all for it18:58
morganfainberghenrynash: yes. But it looks to be more tech debt pay down than anything else and probably could land even post k318:58
bknudsonI think a bp is adequate for this.18:58
samueldmqhenrynash, well, we have the list role assignments improvement as priority18:58
samueldmqand that should land18:58
samueldmqwe just need more reviews on it ...18:58
henrynashfine18:58
*** Riddhi has joined #openstack-meeting18:58
*** changbl has quit IRC18:58
*** VW_ has joined #openstack-meeting18:58
gyeebut that role-assignment test code was pretty tough to read though18:58
*** jungleboyj has joined #openstack-meeting18:58
gyeetook awhile to review that stuff18:58
*** AJaeger_ has joined #openstack-meeting18:58
morganfainbergOk so we're out of time.18:59
morganfainbergAny reasons not to say this can go w/o a spec.18:59
*** VW_ has quit IRC18:59
morganfainbergGoing in 2....18:59
henrynashnope18:59
samueldmq#https://review.openstack.org/#/c/137202/18:59
henrynash(i mean nope, no reason it needs a spec)18:59
*** olaph has joined #openstack-meeting18:59
morganfainbergOk call it no spec needed.18:59
samueldmqplease review the top of the chain18:59
*** VW_ has joined #openstack-meeting18:59
*** ksavich has quit IRC18:59
samueldmq#link https://review.openstack.org/#/c/137202/18:59
samueldmqmorganfainberg, k thanks19:00
morganfainberghenrynash: can you update the bp to reflect this info and reference this meeting?19:00
*** krtaylor has joined #openstack-meeting19:00
morganfainberg#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Feb 24 19:00:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-02-24-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-02-24-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-02-24-18.02.log.html19:00
henrynashmorganfainberg: will do19:00
*** jang1 has joined #openstack-meeting19:00
clarkbohai19:00
anteayao/19:00
*** riwinters has joined #openstack-meeting19:00
fungiheyhey!19:00
mrmartino/19:01
*** aepifanov has joined #openstack-meeting19:01
jeblairhello infra peoples19:01
pleia2o/19:01
mordredo/19:01
asselinHi19:01
*** pcrews has joined #openstack-meeting19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Feb 24 19:01:45 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** lhcheng has left #openstack-meeting19:01
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-02-17-19.01.html19:01
ianwhello19:01
*** ignacio-scopett1 has joined #openstack-meeting19:01
jeblair#topic Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
jeblairAJaeger update infra manual with info on setting up depends on for CRD between new openstack/* project changes and the governance change accepting that project19:02
jeblairi think that just merged a few minutes ago19:02
jeblairso yay!19:02
jheskethMorning19:02
*** ignacio-scopetta has quit IRC19:02
krtayloro/19:02
*** yolanda has joined #openstack-meeting19:02
AJaeger_evening19:02
anteayathanks AJaeger_19:02
jeblairthe rest of the actions i think will fit into later topics19:02
SpamapSo/19:02
*** pritesh has quit IRC19:02
jeblair#topic Priority Efforts (Swift logs)19:02
*** openstack changes topic to "Priority Efforts (Swift logs) (Meeting topic: infra)"19:02
jeblairso i guess it's good we haven't quite gotten around to deploying this everywhere yet19:03
mordredbah.19:03
jeblairsince the requests release broke us19:03
*** browne has quit IRC19:03
anteayadiversity ftw19:03
jeblairis this running in a venv?19:03
mordredwhat's this you say? a python library made a release that breaks things?19:03
*** emagana has quit IRC19:03
*** yeungp has quit IRC19:03
*** annegent_ has joined #openstack-meeting19:03
*** dank_ has joined #openstack-meeting19:03
fungiyeah, it's in a venv19:04
clarkbjeblair: yes it is19:04
*** amakarov is now known as amakarov_away19:04
*** emagana has joined #openstack-meeting19:04
*** dane_leblanc has joined #openstack-meeting19:04
nibalizero/19:04
*** bill_az has quit IRC19:04
jeblairok.  so we're currently fixing it by rolling forward on image updates with the new, fixed, version19:04
clarkbwe could just pin to a specific version of all the deps in the venv today with a working set and never update. We would have to pay attention to security updates19:04
*** leonchio_ has quit IRC19:04
*** auld has joined #openstack-meeting19:04
jheskethouch, I missed that :-(19:04
jeblairbut if this had been deployed everywhere, we could have killed images and fallen back to the previous working version19:04
jesusauruso/19:04
*** browne has joined #openstack-meeting19:04
*** britthouser has quit IRC19:05
*** narenhn has joined #openstack-meeting19:05
fungivery true19:05
jeblairso it's good to know that if something like this happens again (please no), we have a workable coping strategy19:05
*** breton has left #openstack-meeting19:05
clarkb+119:05
*** britthouser has joined #openstack-meeting19:05
jeblairat any rate, this should be running again soon... jhesketh, any blocking reviews?19:05
clarkbthere is the change jhesketh and I co wrote to do uploads ocncurrently19:06
jheskethjeblair: https://review.openstack.org/#/q/status:open+project:openstack-infra/project-config+branch:master+topic:enable_swift,n,z19:06
clarkband the zuul change to fix layout handling of integer vals19:06
jeblair#link https://review.openstack.org/#/q/status:open+project:openstack-infra/project-config+branch:master+topic:enable_swift,n,z19:06
*** browne has left #openstack-meeting19:06
jheskethgives the uploader glob support like Jenkins19:06
clarkbjhesketh: I should update those two changes to use that topic, I will do so now19:06
*** tchaypo has joined #openstack-meeting19:06
jeblaircool, so everything related will show up there soon.19:06
tchaypoThat's better19:06
jheskethhttps://review.openstack.org/#/c/156788/19:07
jeblairanything else on this?19:07
jheskethyep, I'll update a couple of other non-important reviews to that topic too then19:07
jheskethjust incremental improvements really19:07
*** fzdarsky has quit IRC19:07
clarkb#link https://review.openstack.org/#/q/status:open+branch:master+topic:enable_swift,n,z19:07
clarkbneeded to drop the project restriction to get the zuul change in19:07
jheskeththe main thing is moving more jobs over, which is in that topic19:07
jeblaircool, thanks.  (best to avoid merging that one until we have the all-clear on the new image builds)19:08
*** etoews has joined #openstack-meeting19:08
jeblair#topic Priority Efforts (Nodepool DIB)19:09
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:09
jheskethagreed19:09
*** sbalukoff has joined #openstack-meeting19:09
jeblairmordred, clarkb, SpamapS: anything on this topic?19:09
clarkboh ya, the grub thing19:10
fungi#link https://review.openstack.org/15841319:10
clarkbwe are not currently setting kernel boot parameters in the grub2 configs in a way that properly restricts our instances to 8GB of memory19:10
SpamapSclarkb: regarding your thoughts that update-grub may be required... you may be right. I think a simple experiment is in order. :)19:10
mordredyolanda has some work on the nodepool-shade done19:10
mordredshade could really use reviews on: 153623 156247 156088 157509 15695419:10
yolandayes, i started working on it, but i've been evolving shade in the meantime19:11
clarkbgreghaynes is looking into fixing that in dib and we can probably limp along by explicitly calling update-grub in our element19:11
yolandareally using shade in context reveals the weak points19:11
greghaynesYep19:11
jeblairmordred: can you make that into #links for the record?19:11
yolandalatest thing i did is the caching layer, that will be useful for nodepool19:11
yolandait's pending review19:11
clarkbSpamapS: ya I basically confirmed it after grepping around, the only place update-grub is called is in the finalize.d/51-bootloader script which is before we make our changes and it is also where grub is installed so we don't have a place to slip edits in currently19:11
jeblairmordred: (ideally a topic link)19:11
mordredthey don't all have the same topic - I could go edit the topic on them though if you like19:12
fungiafter some heavy consideration of the image collapsing work, i've determined that the best path forward involves leveraging bindep to provide usable cross-platform manifests of what we want installed in such a way that individual projects can also override them, so i have several patches proposed to stackforge/bindep in service of that goal19:12
clarkbI think we solve the grub thing by first manually running update-grub for now then when dib is fixed update dib and update our element to take advantage of dib fix19:12
tchaypoCould you hashtag that so it shows in the minutes?19:12
SpamapS#hashtag ?19:12
*** bswartz has joined #openstack-meeting19:12
tchaypoBlah. That was a response to mordred's list of bugs19:13
tchaypoTrain wifi is laggy :(19:13
* mordred working on it19:13
*** FallenPegasus has joined #openstack-meeting19:13
*** TheJulia has joined #openstack-meeting19:13
*** crc32 has joined #openstack-meeting19:13
fungioh, also i have a mostly complete bindep manifest which covers the things we install today on bare-centos6, bare-precise and bare-trusty which should make the devstack-.* versions of those behave similarly19:14
clarkbfungi: nice19:14
tchaypoThanks. I saw jeblair beat me too it19:14
fungibut didn't get a chance to finish it before the meeting19:14
jeblair#link bindep for image collapsing: https://review.openstack.org/#/q/project:stackforge/bindep+status:open,n,z19:14
*** baoli has quit IRC19:14
fungithanks19:14
*** darx0n has joined #openstack-meeting19:14
mordred#link https://review.openstack.org/#/q/status:open+project:openstack-infra/shade+branch:master+topic:dib-nodepool,n,z19:15
*** SridharRamaswamy has joined #openstack-meeting19:15
fungi#link other-requirements.txt for bindep http://paste.openstack.org/show/18137819:15
*** Longgeek has joined #openstack-meeting19:15
fungithe mostly-complete example19:15
darx0ni19:15
*** egallen has quit IRC19:16
mordredwho is core on bindep?19:16
fungilifeless:19:16
fungiis core on it19:16
*** darx0n has left #openstack-meeting19:16
fungihe may welcome help, i haven't asked yet19:16
fungiit sort of sat abandoned for a couple years until i decided to use it19:16
*** moha_hunt has quit IRC19:17
jeblairwe could also adopt it into infra if lifeless is okay with that19:17
mordredlifeless: ^^19:17
fungibut it really already has the framework to do most of what we want (hence my relatively trivial patches)19:17
fungisome of which might warrant me adding a few tests for coverage19:17
*** jlibosva has quit IRC19:17
*** rockyg has joined #openstack-meeting19:18
jeblair#topic Priority Efforts (Migration to Zanata)19:18
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:18
jeblairpleia2: istr you are still iterating on the big "run zanata" patch?19:18
pleia2yeah, didn't make progress last week because travel+bad internet19:19
tchaypoDo we have a specific topic for the vanilla cloud coming up?19:19
jeblairtchaypo: yep19:19
pleia2mrmartin has been helping me with testing, so I have a change pending to incorporate his comments19:19
mrmartinI did a review on the patch, and tested it, and found only one dependency issue.19:19
mrmartinwith fixing that, the puppet will run well without errors.19:20
jeblairthat's my favorite way of puppet running19:20
mrmartinthe bad news, need to check the deployment, because something is still broken with zanata.war deployment19:20
mrmartinI'll try to allocate some time to trace it.19:20
pleia2once this is done, the fun part is writing the system-config file to setup mysql, exim and whatever else we end up meeding19:21
tchaypoOr needing19:21
pleia2yeah, that too ;)19:21
mrmartinwhy exim? don't we using postfix?19:21
jeblairmrmartin, pleia2: cools, also even thought they don't use puppet, remember the zanata folks might be able to help figure out what's wrong19:21
jeblairmrmartin: we have some exim experts here19:21
fungiso zanata has a specific smtp api?19:21
pleia2yeah, I've been in touch with carlos throughout, he's helped with standalone.xml problems more than once so far19:22
fungior notifications or what?19:22
pleia2fungi: notifications19:22
fungiif it just needs to be able to send outbound, there's pretty much no extra config needed for that19:22
*** anish_ has quit IRC19:22
*** Mandell has quit IRC19:23
mrmartindo we have any limitation on outbound emails?19:23
*** annegent_ has quit IRC19:23
jeblairmrmartin: nope19:23
fungimrmartin: in hpcloud i think, but not in rackspace19:23
*** ChuckC_ has joined #openstack-meeting19:23
fungior did hpcloud finally fix their source port 25 block?19:23
mrmartinok, I've the same experience with hpcloud.19:23
jeblair(one of the reasons we run all our servers in rackspace)19:23
mordredyup19:23
fungier, egress to destination port 25 block i guess19:23
jeblairmrmartin: in hpcloud the rate limit should be such that you can at least test it with a few emails19:23
jeblairfungi: more of a rate limit than block, i thought19:24
pleia2yeah, rate limit, emails come eventually19:24
fungigot it, i think i never knew the details around it19:24
mrmartinyep, but sending out bulk emails can hit those limits.19:24
fungiright, enough that lists.o.o or review.o.o would never fly19:24
*** eharney has joined #openstack-meeting19:24
*** jang1 has quit IRC19:24
clarkbnot even stackforge.o.o flew19:24
jeblairpleia2, mrmartin: thanks!19:24
*** penick_ has quit IRC19:24
fungianyway, we're building it in rax-dfw alond with our other servers, so should be fine19:24
clarkband that was in the before times :)19:24
fungier, along19:24
jeblair#topic Priority Efforts (Downstream Puppet)19:24
*** openstack changes topic to "Priority Efforts (Downstream Puppet) (Meeting topic: infra)"19:25
jeblair#link last call on: https://review.openstack.org/#/c/137471/19:25
*** etoews has quit IRC19:25
jeblairthat spec looks ready to merge to me.  last chance to look it over.19:25
jeblair#link needs updates: https://review.openstack.org/#/c/139745/19:25
*** vigneshvar has quit IRC19:25
jeblairasselin: ^ that spec needs another revision, but i think we're all really excited about it19:25
*** rushil has quit IRC19:25
asselinyes, i got good feedback. will update soon19:25
nibalizerthanks pleia for helping me with the last yard on that one19:25
*** ChuckC has quit IRC19:25
*** ChuckC has joined #openstack-meeting19:26
jeblairand finally, we are poised to publish our modules to the forge as "openstackci-foo"...19:26
jeblairexcept i think we actually want it to be "openstackinfra-foo"19:26
*** moha_hunt has joined #openstack-meeting19:26
mordredoh right19:26
mordredI was supposed to make that19:26
jeblairdoes that change sound good to everyone?19:26
clarkbwhat were peoples' thoughts on thirdpartyci module vs runanopenstackci module?19:26
*** annegent_ has joined #openstack-meeting19:26
clarkbjeblair: wfm19:27
anteayajeblair: yes19:27
nibalizerjeblair: sounds good to me19:27
asselinbased on jeblair's feedback where -infa uses it also, I prefer not to use 'thirdparty'. I plan to adjust the spec with that19:27
anteayaclarkb: what is in the module?19:27
*** jamielennox has left #openstack-meeting19:27
fungireusable openstack infra19:28
mordredjeblair: what email should I use for the openstackinfra accoutn19:28
*** ChuckC_ has quit IRC19:28
*** aranjan has quit IRC19:28
jeblair#agreed use openstackinfra for puppetforge19:28
jeblair#action mordred create openstackinfra account on puppetforge19:28
clarkbanteaya: its the proposed thing in https://review.openstack.org/#/c/139745/ one of my comments was don't make this specific to running third party ci since other people may want it too19:28
nibalizerclarkb: i'm not entirely sure what the difference in setups is between something like what we do, and what a thirdparty tester does19:28
clarkbnibalizer: third party tester usually isn't scaling out like we are, its a different opinion on how to run the same software.19:28
jeblairmordred: infra-root@o.o?19:28
clarkbnibalizer: asselin does it with jenkins, zuul, nodepool on a single node iirc19:29
funginibalizer: fewer components, running more services on a smaller number of machines, et cetera19:29
*** j05h has quit IRC19:29
anteayaI'm for as generic a name as we can find19:29
nibalizersome of the services are just slaved to infra though right?19:29
nibalizere.g. gerrit?19:29
anteayafor folks who what any part of the structure of what we run19:29
jeblairnibalizer: infra's CI system is also slaved to infra's gerrit19:29
mordredjeblair: k. account created - there will be a confirmation email19:29
clarkbnibalizer: yes so no gerrit here19:29
nibalizermy gut instinct, and this is promising a lot, is that we could have two new modules, one for running thirdparty ci for infra and one for running your own19:30
clarkbnibalizer: but why do they need to be different?19:30
nibalizerbut that might be crazytalk19:30
anteayanibalizer: my sense is the point of this is to _not_ have two modules19:30
clarkbis basically what I am saying, if we call it thirdpartyci that implies it should only be used for talking to our gerrit, but maybe you have a gerrit and just want some CI, I dunno19:31
jeblairthe more that infra and the third-party ci can share, the better, i think.19:31
anteayabut to have one that is really reusable for many situations19:31
*** sdake_ has quit IRC19:31
nibalizerclarkb: well if you know you're not gonna run gerrit, and gerrit will always be at review.o.o you can make it simpler19:31
clarkbI also mentioned maybe that is too much to chew off right now and we can converage later on the more idealistic thing19:31
clarkbjeblair: +119:31
*** sdake_ has joined #openstack-meeting19:31
asselinI like to keep the name generic, and start with the parts listed in the spec19:31
*** prad has joined #openstack-meeting19:31
nibalizerwhat were talking about here is composition layers, and generally making new ones is easy and good, but ofc syncing them is hard19:31
*** carl_baldwin has quit IRC19:31
*** marcusvrn has joined #openstack-meeting19:32
nibalizerhere is my concern19:32
*** Riddhi has quit IRC19:32
*** Sukhdev has joined #openstack-meeting19:32
jeblairnibalizer: gerrit is not in the scope of the current spec19:32
nibalizerif we keep the 'thirdparty' label then it has defined and limited scope, even though that scope is pretty big19:32
nibalizerif we rename it 'run your own infra module' it has enormous scope19:32
clarkbasselin: yup I think the content of the things is good as far as what is included. I just want to avoid making it seem that we aren't also possibly solving the problem of running your own regardless of intent19:32
*** VW__ has joined #openstack-meeting19:33
*** achanda has quit IRC19:33
jeblairnibalizer: clarkb's actual suggestion was "openstackci", which i think captures the intent19:33
nibalizerjeblair: yea i get the sense that clarkb wanted to expand scope, im okay with calling it openstackci and we mean 'thirdparty'19:33
*** devlaps has quit IRC19:33
clarkbnibalizer: well the thing is I don't think its expanded scope19:34
jeblairnibalizer: third-party + first-party19:34
clarkbnibalizer: what we are giving people is a run your own19:34
asselinI have the spec updated now (not yet submitted to review) to use 'openstackci'19:34
*** BharatK has quit IRC19:34
clarkbnibalizer: so why not just call it that19:34
*** sdake__ has joined #openstack-meeting19:34
jeblairclarkb: i think "all of infra" is a larger scope. and i don't think we want to do that.19:34
*** britthouser has quit IRC19:34
clarkbjeblair: I am not suggestion all of infra19:34
*** britthouser has joined #openstack-meeting19:34
jeblairclarkb: great, i think we're all agreed.19:35
*** marcusvrn1 has quit IRC19:35
*** aepifanov has quit IRC19:35
*** carl_baldwin has joined #openstack-meeting19:35
jeblairasselin: thanks, it sounds like the spec is just about ready then19:35
*** dprince has quit IRC19:35
jeblair#topic Priority Efforts (Askbot migration)19:35
*** openstack changes topic to "Priority Efforts (Askbot migration) (Meeting topic: infra)"19:35
*** VW_ has quit IRC19:36
mrmartinok, so nothing exciting here19:36
jeblairthe spec merged :)19:36
mrmartinthe spec approved, and we need an approve on the main patch19:36
mrmartinyeap19:36
mrmartinand after that somebody need to launch the instance19:36
jeblairand i think add some things to hiera19:36
mrmartinI'll add all of the migration tasks to storyboard19:36
jeblairbut mostly just making up new passwords; no real coordination needed for those19:36
mrmartinmake new passwords19:36
fungiyeah, the ssl bits are in hiera, but the stuff that can be randomly generated has not been added yet19:37
* fungi meant to and hadn't gotten around to it19:37
mrmartinand when this is ready, we can pass it for extra testing before opening up to the public19:37
*** sdake_ has quit IRC19:37
jeblairmrmartin: can you #link the main patch?19:37
mrmartin#link https://review.openstack.org/14004319:38
fungimrmartin: you were going to write up the actual commands we need to use to extract and import the data it needs, right? i think that's what i originally wanted to see, but may have been lost in the shuffle when you wrote a spec about it19:38
mrmartinfungi, yes I've this somewhere, I'll add it to the spec19:39
fungii'm cool with there being a spec, but was really just looking for the basic commands we'll need19:39
mrmartinnothing extra, just need to do postgresql backup / recovery and reindex the solr db19:39
fungiokay, sounds simple enough19:39
jeblairmrmartin: or you could add it to the system documentation (in case we need to reference it in the future)19:39
jeblaireither way19:39
mrmartinthat's all, but I'll add those commands, I did those tasks in test vm several times19:40
mrmartin#action mrmartin add operation tasks to askbot system documentation19:40
jeblairmrmartin: thanks!19:40
jeblair#topic Priority Efforts (Upgrading Gerrit)19:40
*** openstack changes topic to "Priority Efforts (Upgrading Gerrit) (Meeting topic: infra)"19:40
jeblairzaro proposed a date for the gerrit upgrade: proposed date Fri April 10, 201519:40
*** imsurit has quit IRC19:41
*** achanda has joined #openstack-meeting19:41
jeblairthat's in the middle of pycon, and i will be unable to help then19:41
anteayame too19:41
clarkbI won't be pyconning and assuming nothing pops up between now and then is fine with me19:41
pleia2wfm19:42
fungiyeah, i wasn't planning to be at pycon (didn't get around to submitting any talks) so i'll be aroud19:42
jeblairhowever, might we want to do it on a saturday?19:42
asselinQuestion: will there be 'something' available to test firewall updates?19:42
fungiaround too19:42
*** ebalduf has joined #openstack-meeting19:42
jeblairasselin: i don't think we were planning on it, but maybe we could run netcat or something on that port?19:42
fungii can also do that saturday if we'd rather, no problem19:42
pleia2fwiw, I try to take saturdays off because sanity19:43
tchaypoMaybe a web server with a static "future gerrit" page?19:43
*** prad has quit IRC19:43
fungiheh, yeah netcat running to serve a "you can reach us!" banner and some instructions on how to test19:43
zaroo/19:43
*** jang1 has joined #openstack-meeting19:43
*** e0ne has quit IRC19:43
jeblairpleia2: normally, yes, and we do a lot of light gerrit maintenance on fridays.  but this has the potential for significant downtime if something goes wrong.19:43
asselinIt would be very helpful to have something so we can telnet to the ip & port and make sure connectively is good. Especially w/ coorporate requests. we have a window to test, after which you need a new request if there's a mistake.19:43
fungiweb page might be less accurate because people may have browsers set up to proxy arbitrarily19:43
pleia2jeblair: *nod*19:44
fungiso instructions to test ought to not involve "go to this url in a browser"19:44
asselinours is supposed to be implemented soon (Planned Start: 02/24/2015 08:00:00 Planned End: 03/03/2015 16:00:00)19:44
jeblairpleia2: want to set that up?  i don't think we need to puppet it...19:45
jeblair(but can if you really feel like it :)19:45
*** khaldrogox has quit IRC19:45
*** carl_baldwin has quit IRC19:45
fungiyeah, i wouldn't bother to puppet it19:45
pleia2jeblair: sure, I'll collude with zaro19:45
*** eharney has quit IRC19:46
mordredcollusion is good19:46
jeblair#action pleia2 set up netcat hello-world on new gerrit port 2941819:46
fungiour software is built on collusion and beer19:46
jeblairzaro: how's saturday sound?19:46
*** pkoniszewski has quit IRC19:46
zarosounds good19:46
jeblairzaro: you'll have clarkb and fungi on hand at least19:46
*** ebalduf has quit IRC19:46
clarkbshould be fun, is that after release?19:47
jeblairftr, i can do either of the next two saturdays19:47
clarkbI should pull up the release chart19:47
jeblairit's in the RC period19:47
zaroi believe its release candidate week19:47
*** jang1 has quit IRC19:47
asselinjeblair, pleia2 thanks!19:47
jeblairgenerally the period where ttx asks us to please be slushy.19:47
anteaya#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule19:48
jeblairperhaps we should move it to may 9?19:48
anteayaI like may 919:48
fungii might be travelling then, but not sure19:49
clarkbya I think gerrit upgrade isn't very slushy19:49
clarkbmay 9 should also work for me19:49
zaroisn't that summit time?19:49
jeblairzaro: https://wiki.openstack.org/wiki/Kilo_Release_Schedule19:49
anteayasummit is the week of may 2119:49
clarkbya summit starts on the 19th19:49
clarkber 18th19:50
zaro5/9 wfm too19:50
jeblairokay, everyone look at your calendars and next week we'll decide on a date19:50
*** matrohon has joined #openstack-meeting19:50
*** zz_johnthetubagu is now known as johnthetubaguy19:50
jeblair#info april 11 and may 9 suggested as gerrit upgrade dates19:50
*** etoews has joined #openstack-meeting19:50
jeblair#topic Fedora/Centos progress (ianw 2/24)19:50
*** openstack changes topic to "Fedora/Centos progress (ianw 2/24) (Meeting topic: infra)"19:50
*** Riddhi has joined #openstack-meeting19:51
ianwi'd like to get the image build logs much easier to use so i'm more confident keeping on top of issues with these builds19:51
clarkbthe log config gen script lgtm last I looked at it19:51
ianwi've been through several iterations of this with https://review.openstack.org/#/c/153904/19:51
jeblairianw: soon we're only going to do one image build per-type.  i think when that's the case, we could just specify those types in the logging config file manually, right?19:52
clarkbjeblair: we could, though the script to do it is pretty handy, and maybe its a manual check into git to use it19:52
clarkbrather than auto gen on nodepool restart19:52
*** johnthetubaguy is now known as zz_johnthetubagu19:52
fungiright, we're getting much closer to just having images named "centos" and "trusty" and so on, and building them once then uploading to all providers19:53
jeblairi've said this elsewhere -- i don't like having openstack's production logging config in the nodepool source code19:53
fungiso manually handling the log targets for them seems tractable19:53
jeblairi think any solution that includes that is not one i'm in favor of19:53
clarkbjeblair: can you add that to the change?19:53
mordredjeblair: ++19:53
clarkbI don't think I had caught you saying that19:53
ianwi would argue that it's not openstack's logging configuration, it's a generic configuration that is useful to anyone using nodepool19:54
jeblairlet's handle that in the change19:54
*** annegent_ has quit IRC19:54
jeblairianw: anything else needs discussion with the whole group?19:54
ianwi'd like to promote devstack centos to voting, any issues here?19:55
mordredoh - I guess I should say ...19:55
*** jang1 has joined #openstack-meeting19:55
jeblairianw: i don't think so, but the devstack folks will need to weigh in on that19:55
mordredI believe I've been convinced on just running cloud-init which should make centos/fedora work for dib-nodepool better19:55
clarkbalso may be worth swapping out a trusty job rather than doing a pure add?19:56
mordredalthough I need to get an element built that will install it into a venv with the rax patches19:56
ianwyes, i'll propose change but as long as everyone is happy with that general idea19:56
clarkbbut that needs larger consensus probably19:56
*** ddieterly has quit IRC19:56
ianwalso the f21 job needs to update it's kernel19:56
clarkbI am not opposed to centos devstack voting19:56
ianwi guess the answer is use a dib built f2119:57
*** narenhn has quit IRC19:57
jeblairianw: that should happen in image builds, right?19:57
fungiianw: also thanks for helping the glusterfs cinder driver folks with their centos7 testing issues19:57
*** SridharRamaswamy has quit IRC19:57
clarkbianw: we can't do dib with rackspace just yet, but when we can this would avoid that problem19:57
clarkbjeblair: ianw started a thread about why it tries but fails19:57
clarkbin the -infra list19:58
jeblairok19:58
jeblair#topic Infra-cloud (jeblair)19:58
*** openstack changes topic to "Infra-cloud (jeblair) (Meeting topic: infra)"19:58
jeblairso we're nearly out of time19:58
*** etoews has quit IRC19:58
jeblair#link summary email https://etherpad.openstack.org/p/kBPiVfTsAP19:58
jeblair#link story https://storyboard.openstack.org/#!/story/200017519:58
jeblair#link etherpad https://etherpad.openstack.org/p/InfraCloudBootcamp19:58
*** ddieterly has joined #openstack-meeting19:58
*** yolanda has left #openstack-meeting19:58
jeblairi'll send out an email about this soon (see that first link)19:58
jeblairbut the short version is that we have some folks that want to join us and help us run a cloud19:59
jeblairas part of infra.  and help out with infra-ish things too.19:59
*** rm_work is now known as rm_work|away19:59
mordredyay!19:59
tchaypoI'll follow up on the email19:59
jeblairi think it's pretty exciting19:59
tchaypoAnd figure out who I should be giving access to those servers and how19:59
tchaypoSo that we can. I've forward20:00
jeblairso anyway, yeah, we'll follow up in email, and talk about this more next week20:00
mrmartinawesome20:00
jeblairthanks everyone!20:00
cebrunsThat is cool.20:00
tchaypoMove20:00
jheskethseeya20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Feb 24 20:00:36 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-02-24-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-02-24-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-02-24-19.01.log.html20:00
*** SridharRamaswamy has joined #openstack-meeting20:00
ttxAnyone here for the TC meeting ?20:01
devanandao/20:01
vishyo/20:01
jeblairo/20:01
amritho/20:01
mikalHi20:01
vishyi have to head out at 12:30 so lets go fast :)20:01
ttxrussellb, jgriffith, annegentle, mordred, markmcclain, jaypipes, sdague : around ?20:01
*** pcrews has left #openstack-meeting20:01
sdagueo/20:01
*** casusbelli has joined #openstack-meeting20:01
markmcclaino/20:01
ttxdhellmann has an unexpected family matter to attend and will likely miss20:01
mordredo/20:01
*** markstur has joined #openstack-meeting20:01
ttxok, we have quorum20:01
ttx#startmeeting tc20:02
openstackMeeting started Tue Feb 24 20:02:00 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
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** olaph has left #openstack-meeting20:02
ttx#topic openstack-specs approval rules20:02
*** openstack changes topic to "openstack-specs approval rules (Meeting topic: tc)"20:02
ttxI put this one first since we'll need to use the decision here on the next topic20:02
*** novas0x2a|laptop has joined #openstack-meeting20:02
ttxCurrent state (once https://review.openstack.org/158666 lands) is:20:02
*** rm_work|away is now known as rm_work20:02
ttxAnyone can +1, TC members can +2, TC chair can tally votes (and workflow+1)20:02
ttxDoes that work for everyone ?20:03
mordred++20:03
vishy+120:03
devananda+120:03
*** ChrisPriceAB has quit IRC20:03
sdaguesure20:03
markmcclain+120:03
jeblairyep20:03
*** barrett has joined #openstack-meeting20:03
*** Riddhi has quit IRC20:03
mordredbest. thing. evar20:03
mikalWorks for me20:03
sdagueis there a quorum issue?20:03
ttx#agreed openstack-specs approval rules: Anyone can +1, TC members can +2, TC chair can tally votes (and workflow+1)20:03
russellbo/20:03
ttxsdague: it's part of the "tally votes" thing20:03
russellb++20:03
sdaguettx: ok, sounds good20:03
mikalWe should do that for the governance repo too20:03
ttxsdague: ideally chair should only wiorkflow+1 when there is "consensus"20:03
*** sandywalsh_ is now known as sandywalsh20:04
*** annegent_ has joined #openstack-meeting20:04
mikali.e. let anyone +1 / -120:04
ttxmikal: I guess.. we could20:04
jeblairmikal: did you read my mail to the list?20:04
mikaljeblair: it depends when you sent it... its 7am here20:04
ttxISTR there was a reason not to20:04
jeblairmikal: like 2 weeks ago20:04
mikalI do not recall it then20:05
*** BaconIsKing has quit IRC20:05
russellbttx: the need to differentiante between TC -1 vs. general -1 i think?20:05
annegent_color coding?20:05
annegent_(kidding)20:05
ttxrussellb: right, that one.20:05
*** PaulMurray is now known as ptm_away20:05
jeblair#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/056788.html20:06
jeblairso anyway, there are some options20:06
jeblairthey are described in that email20:06
ttxlet's follow up there20:06
sdaguerussellb: so... we all know who is in the TC right? We can read the votes :)20:06
*** dane_leblanc has quit IRC20:06
*** dboik has joined #openstack-meeting20:06
ttxjeblair: since that review to use the right group is blocked, could you add me to https://review.openstack.org/#/admin/groups/573,members so that we can proceed with approvals today ?20:07
mikalAhhh, I see20:07
russellbsdague: sure, just trying to recall the reasoning way back when20:07
mikalIts also about avoiding a TC member vetoing20:07
*** zehicle has quit IRC20:07
jeblairttx: done20:08
ttxthx20:08
ttx#topic Final rubberstamp on CLI Sorting Argument Guidelines20:08
*** openstack changes topic to "Final rubberstamp on CLI Sorting Argument Guidelines (Meeting topic: tc)"20:08
*** VijayTripathi has joined #openstack-meeting20:08
anteayasorry ttx did want to have that in before the meeting20:08
ttx#link https://review.openstack.org/#/c/145544/20:08
*** tiswanso_ has quit IRC20:08
*** _nadya_ has joined #openstack-meeting20:08
ttxanteaya: np, we worked around it20:08
*** SlickNik has joined #openstack-meeting20:08
ttxSo I'm about to approve this review. Any last comments before I do ?20:08
anteayayep20:08
ttxI still see unanimous support from where I stand20:09
ttxand support from all the PTLs impacted20:09
annegent_looks completely approvable to me20:10
ttxok, will take that as a yes20:10
ttxapproved20:10
ttx#topic M+ Release naming process20:10
*** openstack changes topic to "M+ Release naming process (Meeting topic: tc)"20:10
ttx#link https://review.openstack.org/15060420:10
*** dboik has quit IRC20:11
ttxThis proposal is still a bit short on approval20:11
ttxTechnically if I call for final voting it can pass if it gets 5 YES and less than 5 NO20:11
*** dboik has joined #openstack-meeting20:11
jeblairi think we should ask people to vote asap and do last-call on this.20:11
*** irenab has joined #openstack-meeting20:11
*** sigmavirus24 is now known as sigmavirus24_awa20:11
ttxjeblair: in meeting or before next week ?20:12
jeblairi don't thing we should drag it out; if there are minor changes (like moving the date around) we can do those as followup ammendments20:12
*** _nadya_ has quit IRC20:12
*** noslzzp has joined #openstack-meeting20:13
ttxok, vote asap, let's try to close this one during the meeting20:13
*** sigmavirus24_awa is now known as sigmavirus2420:13
ttxI'd like to make sure we have volunteers to run this process if it's approved, too20:13
markmcclainso my biggest concern is that the discussion is separate from the vote20:13
ttx(since I think it will result in more pain that the current system, I'd rather not drive that train)20:13
*** carl_baldwin has joined #openstack-meeting20:13
ttxjeblair, mordred: would you be ok to drive the M one ?20:13
jeblairttx: i think mordred has previous volunteered20:13
mordredttx: sure20:13
ttx#indo mordred volunteered to drive the M release naming train on the new process, should it be accepted20:14
ttxerr20:14
*** khaldrogox has joined #openstack-meeting20:14
ttx#info mordred volunteered to drive the M release naming train on the new process, should it be accepted20:14
* mordred puts the indo in his pocket for later20:14
ttxmarkmcclain: discussion on ?20:14
markmcclainthe names20:14
jeblairmarkmcclain: yeah, i think there's an attempt to tie them together though -- with the process for annotating names with discussion about them20:14
markmcclainjeblair: cool.. that will work20:15
ttxone issue I has in the past naming contests was that nobody would add names to the wiki page20:15
ttxso names were randomly thrown out and never really "proposed"20:15
ttxyou'll probably have to make stronger calls20:16
russellbhas 6 YES now20:16
*** dane_leblanc has joined #openstack-meeting20:16
mordredttx: I will attempt to use my annoying voice20:16
ttxok, will approve if it has less than 5 NO by the end of the meeting (as it should)20:16
ttxunless it gets a 7th YES right now20:16
ttx#topic Projects using private communication channels20:16
markmcclainit has 7 now20:17
*** openstack changes topic to "Projects using private communication channels (Meeting topic: tc)"20:17
ttxmarkmcclain: ok approving20:17
*** doude has quit IRC20:17
*** AmirBaleghi has quit IRC20:17
*** otter768 has joined #openstack-meeting20:17
ttxnot sure I can approve the vote without voting +2 on it though20:17
ttxlet's see20:17
jeblairttx: yeah, that's one of the points i addressed in my email.  we should be able to fix that too.20:17
ttxI'll mùake my abstention known with a note then20:18
jeblairttx: in the mean time, i suggest you leave a comment indicating your +2 is procedural and you are actually (abstaining/voting no/etc)20:18
*** doude has joined #openstack-meeting20:18
mordredjeblair, ttx: we could force-merge it so that ttx doesn't have to +2 vote20:18
*** eglynn-afk has joined #openstack-meeting20:18
annegent_mordred: oh dear the power.20:18
mordredit is an awkward position to put him in20:18
ttxIt's fine, I commented20:19
mordredkk20:19
jeblaircool. we'll fix this in the acl overhaul.20:19
mordred++20:19
ttx#undo20:19
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xa360f10>20:19
ttx#topic Projects using private communication channels20:19
*** openstack changes topic to "Projects using private communication channels (Meeting topic: tc)"20:19
ttxback on topic20:19
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/056551.html20:19
reedo/20:19
ttxreed: o/20:19
reedI have tracked down the story of the private channel established within one of our project20:19
ttxreed has been serving as ombudsman and contact point for the various parties on this issue20:19
*** zehicle has joined #openstack-meeting20:20
* mordred hands reed a cookie20:20
reedthe channel was created at one point in time with the specific intention to discuss a delicate issue that required privacy20:20
reedthe team that created it was very careful and made it +i +s20:20
ttxjust to confirm, I'm actually fine with private temporary channels created to gather people temporarily on an issue. I don't agree with protected / invite-only channels, or permanent private channels20:21
mordred++20:21
russellbyeah, agree20:21
jeblairttx: i think that describes my feeling as well20:21
reedthe channel remained active *after* the crisis was over20:21
ttxand making *not* protected actually ensures that they are temporary20:21
ttxand using funny names20:21
amrithcould we let reed finish first please.20:21
*** otter768 has quit IRC20:21
reedbut the team using it wasn't really using it for anything but a convenient place where to discuss other topics that rquired privacy20:22
reedthis has happend once or twice only20:22
reedi was also reassured that the team was not 'hanging out' in that private team20:22
*** marun has quit IRC20:23
reedmeaning that the channel was not used much and the group was self-policing it so that public topics were addressed on the public channels20:23
annegent_reed: or anyone really, can you give more info on the meaning of +i and +s?20:23
vishyso it kind of sounds like someone made a mountain out of a molehill20:23
reedvishy, sort of...20:23
ttxwell, the trick is... permanent private channels always degenrate20:24
reedas I mentioned on email, I think that a *permanent* private channel develops bad habits20:24
reedand they should not be used20:24
reedtemporary private channels I'm ok with them20:24
amrithannegent_, IRC channel flags (https://www.alien.net.au/irc/chanmodes.html), +i invite only, +s secret20:24
ttxdiscussing things is so much more convenient when the crowd is controlled that you end up discussing stuff there that you shouldn't20:25
annegent_reed: do you have any analysis on the "internet jury/public shaming" aspect of the mailing list thread? What I mean is, how can we ensure the mountain doesn't rise up again from some other misunderstanding?20:25
annegent_how can we encourage trust rather than distrust?20:25
mikalSo, in the interests of full disclosure, the group now known as nova-specs-core had a private channel which we used while navigating the early days of how specs would work. That channel appears to have been used between 22 April 2014 and 18 June 2014, but has been idle since. We never did get around to deleting it though.20:25
ttxit's one thing to have company-private channels (like everyone has)20:25
annegent_thanks for that mikal20:25
reedannegent_, the email thread was not about an IRC channel only20:25
ttxiit's another to have a channel in the openstack community exclusing another part of the community permanently20:26
*** nellysmitt has quit IRC20:26
ttxexcluding*20:26
ttxSo I guess we can consider the issue closed on the particular issue that raised this thread. Should we write a resolution to avoid that kind of "issue" in the future ?20:26
anteayaI think annegent_ brings up a good question, how do we encourage trust20:26
mikalFrankly, I see that happening a lot more with company channels than I do with private channels based on available data20:26
devanandamikal: ty. I have been wondering what all this was actually referring to, and while I love talking in the abstract, it's good to know20:26
ttxOr was the current noise about it enough to prevent it in the future ?20:26
russellbdevananda: i think this was actually in reference to another case20:27
mikalIts relatively common for me to hear that somehting has been discussed in a private company channel and that a subgroup has formed an opinion that way20:27
devanandarussellb: oh ...20:27
mikaldevananda: the channel I am disclosing is not the one which caused the complaint (to my knowledge)20:27
russellbi'm sure in both cases, the channels were mostly idle, but if you know it exists but aren't there, it becomes a trust issue20:27
devanandaI'll just settle for being in the dark then20:27
devanandarussellb: right20:27
* eglynn-afk eglynn20:28
*** eglynn-afk is now known as eglynn20:28
ttxdoes the TC think further action needs to be taken on this ?20:28
mikalSo, that's kind of where I was going...20:29
mikalI think we should make some sort of blanket statement encouraging peopel to work in the open20:29
anteayaI think the larger question of how to encourage trust still could use some thought20:29
russellbi think our stance on openness is already clear enough20:29
devanandamikal: groups of people who work together often form collective opinions, whether that grouping is by-project, by-company, or what ever -- and I think that's normal and acceptable behavior20:29
russellbdon't see a need for resolution20:29
mikalSpecifically not use corporate channels to pre-bake ideas20:29
ttxThere also was an #openstack-social channel -- at some point we realized we started having the wrong discussions on it and we killed it20:29
russellbpeople should just continue calling things out that don't seem right20:29
ttxrussellb: is that a fair assessment ^ ?20:29
russellblet it be culturally enforced20:29
reedttx, I think that a resolution is not necessary20:29
devanandarussellb: ++20:29
russellbttx: right, and killed it20:29
mordred++20:29
reedjust a reminder from the TC on the mailing list would be enough20:29
markmcclain++20:29
ttxrussellb: it's my texbook exampel on why permanent invite-only channels are bad :)20:30
mordredalso - I think the underlying thing about fostering trust amongst the community is very important20:30
ttxAlso the whole "core is not special" point needs to be reinforced20:30
mordred++20:30
ttxwhich I think was half of the original thread20:30
devananda++20:30
markmcclain+120:31
jeblairi think the project's principals of open development and decision making are already well stated, and i think the end of that thread reinforced many of these things20:31
sdague+120:31
jeblairi don't feel like a resolution is _necessary_20:31
ttx*if the channel had been about left-handed people I'm pretty sure it would have been less of an issue20:31
russellbi wouldn't oppose one if someone feels up to writing one20:31
annegent_I think reed's handling of the further investigation helped immensely and is part of resolutions for these concerns when brought to the ML.20:31
*** unicell has quit IRC20:31
jeblairreed: however, if you would like a reminder from the tc on the mailing list, in order for the tc to speak, i think we should have a resolution so we can vote on it.  then someone can forward that to the list.20:31
sdaguehonestly, I think the more interesting questions that arose from it were the inconsistencies around logging of project channels, which continues to confuse new contributors20:31
russellbyeah, should address that too20:32
jeblairsdague: i feel like many folks are thinking we should just blanket-log every channel we know about20:32
jeblairperhaps we should take a tc resolution to make that a policy?20:32
russellbmight be easier to have TC set logging policy than deal with tracking down consensus for every project channel20:32
russellbyes :)20:32
zanebin #heat it's announced in the topic that it's logged. do other channels not do the same?20:32
sdagueyeh, I'm fine with that20:32
reedjeblair, I would like to avoid formalities because they end up taking time20:32
ttxjeblair: should we address the logging question in the same run ?20:32
jeblairthen infra can make that happen and perhaps set up appropriate channel announcements, topics, etc.20:32
ttxzaneb: I think it's a good thing to have (logging notification in topic)20:33
markmcclainconsistency there would be a good idea20:33
jeblairreed: i think if you want a statement from the tc, we should pass a resolution.  i expect this one to be quick.  :)20:33
sdaguezaneb: so there are multiple inconsistencies, #1 which channels are logged, #2 which channels tell you they are logged that are20:33
reedI feel like there is enough consensus that if ttx or you or anyone from the TC writes a #info here I can use that and close the incident20:33
*** garyh has quit IRC20:33
zanebyeah, I can't think of an excuse not to have it in the topic for all of them20:33
reedjeblair, I leave that up to you then20:33
* ttx can't draft anything after 9pm20:33
zanebthough I confess that #heat was logged for about 6 months before I noticed20:33
ttxzaneb: heh20:34
devananda++ to announcing logging, ++ to enforcing it in all official project channels20:34
*** tomoe_ has joined #openstack-meeting20:34
zanebluckily I don't think I said anything too outrageous ;)20:34
ttx++ to announce where it's logged too20:34
*** garyh has joined #openstack-meeting20:34
reedsdague, yes, that's another topic I'd like to discuss20:34
anteayadevananda: define official20:34
*** j05h has joined #openstack-meeting20:34
ttxanteaya: channels about an official project ?20:34
russellband don't you grant -infra ownership of channels?20:35
ttxas in an "openstack project team" ?20:35
mordredanteaya: I'd say "ones that are registered with infra as channels?"20:35
russellbthat seems like an easy trigger20:35
anteayamordred: that one is easier to track20:35
devanandaanteaya: eg, the project info on LP states "the channel is X" -- or in infra/project-config, there's an infra bot already managing in the channel20:35
*** melwitt has joined #openstack-meeting20:35
devanandaI think mordred said it better20:35
ttxso.. anyone up to propose a text, or should we just draft a resolution off-meeting ?20:35
sdaguettx: I think take it off meeting20:36
devanandattx: I feel like a resolution is unnecessary ...20:36
russellboff meeting probably ... need to get right definition of what channels are included20:36
russellb(for the logging part)20:36
devanandattx: oh, you mean w.r.t. logging. yah, that's fine20:36
ttxdevananda: two birds one stone ?20:36
anteayatwo birds in a stone20:36
jeblairif we have resolutions for both, let's have two resolutions20:36
sdaguejeblair: ++20:36
ttxjeblair: up for drafting the IRC policy ?20:37
jeblairttx: will do20:37
sdaguethey are related, but separate things.20:37
ttx#action jeblair to draft IRC policy resolution20:37
jeblairsdague: and they have bikesheds of completely different colors20:37
*** etoews has joined #openstack-meeting20:37
mordredjeblair: can we also discuss the colors of the bikes?20:37
sdaguebut what if I want to store my snowblower in it?20:37
mordred++20:38
ttxcurrent issue considered closed, will use a closing email referencing said IRC policy when passed20:38
russellbi think all channels should change to proper capitalization of OpenStack20:38
jeblairsdague: isn't your snowblower in constant use? :)20:38
sdaguewell... it will be may eventually20:38
ttx#topic Definition of the release tags20:38
*** openstack changes topic to "Definition of the release tags (Meeting topic: tc)"20:38
ttx#link https://review.openstack.org/15732220:38
*** tomoe_ has quit IRC20:38
ttxthis proposal introduces tags to describe the release model that each code repository uses (if any)20:38
ttxThose are pretty objective and would be maintained by the release management team20:39
ttxmikal: replied to your objection, let me know if it makes sense20:39
mikalYep, I read it just now20:39
mikalI do wonder if we should clarify what the meaning of those tags is in the context of defcore20:39
mikalEven if its "nothing"20:39
mikalBecause previously the integrated release was a requirement20:40
ttxit is "nothing". defcore may say they would only consider release:common projects for example20:40
russellbthat detail needs to be worked out20:40
russellbthere hasn't been anything from defcore to say what is even needed20:40
ttxbut until the tag exists... they use "integrated-release" as of Kilo20:40
mikalWell, haven't they effectively said they want to use release:integrated20:40
mikalWhich doesn't exist?20:40
*** prad has joined #openstack-meeting20:40
ttxonce we replaced it by series of tags they will pick20:40
russellblike, do they want something for separate trademark programs?  just one big group?20:40
zehicleo/20:40
ttxmikal: exists for kilo20:41
russellbmikal: note that defcore also is on icehouse and juno right now20:41
russellbnot even kilo20:41
russellbso we've got some time to sort it20:41
ttxanyway, I expect defcore to ask us "what is the list of projects that you think will fit program Y"20:41
russellbbefore "integrated release" doesn't work20:41
ttxand we'll have to define a specific tag to answer that20:41
russellbttx: that was my thinking20:41
mikalWell, I'm asking in the context of some epople wanting to change the release cycle for nova20:41
ttxrather than overloading an existign tag20:41
zehiclerussellb, FWIW it looks like we're trying to move DefCore away from release ties to date ties20:41
mikalAnd seeking to understand if the defcore process would even allow that20:41
ttxotherwise it's integarted-reelase all over again20:41
mikal(But not saying I think we should change the nova release cycle if that makes sense)20:41
russellbzehicle: ok20:41
russellbmikal: i sure hope if it does change, it's still coordinated with a major set of projects ... another topic though i suppose :)20:42
mikalYeah20:42
ttxmikal: that's a sane question -- the answer is not in the definition of that tag though20:42
devanandazehicle: does defcore have any intrinsic dependency on a project's release cadence?20:42
mikalWhat I want from this bit of the conversation is just a clear statement of if release:coordinated is a requirement for defcore20:42
zehiclewe're reviewing it tomorrow @ 9 PT20:42
mikalBut it sounds like I am asking the wrong people20:42
sdaguemikal: yeh, it feels like that other conversation is a bit premature. Of all the projects to move into release:free state, nova would not be my first pick20:43
devanandazehicle: or was it the dependency previously that trademark usage was pinned to integration status?20:43
ttxmikal: that's upto defcore, not us20:43
devananda*just that ..20:43
*** ebalduf has joined #openstack-meeting20:43
mikalttx: I thought defcore was about certifying the contents of the integrated release?20:43
mikalttx: which is a thing the TC has historically designated?20:43
ttxmikal: err... no?20:43
zehiclesorry - did not mean to distract the agenda.20:44
ttxdefcore is about what you need to implement to claim a trademark program usage20:44
annegent_mikal: capabilities are defined by defcore20:44
*** tiswanso has joined #openstack-meeting20:44
ttxi.e. what you need to do to call your stuff "openstack Compute powered"20:44
*** aranjan has joined #openstack-meeting20:44
annegent_zehicle: I think it's important we all understand20:44
ttxthey ask us for lists of projects, we provide said list. And they pick within it20:44
mikalSure20:44
zehiclewe recognize that DefCore is trailing20:44
mikalAnd isn't that list the integrated release?20:44
russellbwhat ttx said20:44
devanandattx: defcore / the board has the responsibility to inform us / the TC of what we can change. ie, we can't remove an integrated project that defcore has already approved w/o their consent20:44
devanandattx: so it would make sense IFF defcore cares about release cadence that they might have some input there. but I don't actually see why defcore would care about that yet.20:45
ttxdevananda: "remove"20:45
ttx?20:45
*** rbowen has quit IRC20:45
ttxdevananda: I totally agree that defcore needs to take a stance on what release model they would actually consider for theiur trademark programs20:46
rockygMikal: Defcore is about mature (*cough*), well adopted capabilities within the context of the OpenStack projects20:46
devanandattx: not that we're discussing removing projects, but IIRC that was the only constraint defcore is able to place on the TC's integration (or non-integration) of projects20:46
ttxI just think this is orthogonal to the definition of tags20:46
ttxwhich are just an objective description of a curent situation20:46
mikalttx: agreed20:46
devanandattx: so it stands to me to reason that, IFF defcore cares about release cadence, we may both want their input and need to respect their requirements, should they have some20:46
devanandahowever that discussion is really premature20:46
mikalttx: I am happy to handle my question elsewhere20:46
*** VW__ has quit IRC20:46
devanandabecause so far they haven't expressed any such requirements20:46
ttxbut yes, clarifying the various release models makes us realize there is a question that needs to be answered20:47
*** VijayTripathi has left #openstack-meeting20:47
devanandattx: yup20:47
ttxfor example, swift would be release:compatible20:47
ttxand it never bothered defcore so far20:47
*** rushil has joined #openstack-meeting20:47
*** VW_ has joined #openstack-meeting20:47
ttxrelease:free ? maybe they would object to that  (I would)20:47
ttxI think at the very minimum release:compatible should be required20:47
ttxbut then, not my decision to make20:48
*** ebalduf has quit IRC20:48
ttxI just want to provide the classification20:48
ttxand apply it to projects20:48
ttxso that they actually have that information :)20:48
devananda++20:48
ttxI'm pretty sure a lot of defcore people didn't even know that swift was different.20:48
*** faizan has joined #openstack-meeting20:48
*** aranjan has quit IRC20:48
*** asalkeld has joined #openstack-meeting20:48
*** jang1 has quit IRC20:49
ttxanyway, we can iterate on the review20:49
*** rbowen has joined #openstack-meeting20:49
ttxanother hot question, or should we move on ?20:49
*** ddieterly has quit IRC20:50
mikalMove on20:50
annegent_I had one20:50
mikalDoh, sorry20:50
* ttx reads comments from anne20:50
*** jang has joined #openstack-meeting20:50
annegent_oh I can keep commenting in the review20:50
*** ddieterly has joined #openstack-meeting20:50
annegent_s'okay to move on20:50
ttxannegent_: as-needed might exclude time-based-however-I-want-it20:50
*** pnavarro has joined #openstack-meeting20:51
mikalHow about "unrestrained"?20:51
annegent_ttx: ok, does only the common and compatible tag holders get to pick dates?20:51
ttxI felt "free" was more open, as-needed seems to imply "only when necessary", which implied feature-based20:51
*** narenhn has joined #openstack-meeting20:51
*** adalbas has quit IRC20:51
ttxcommon = you follow the common cycle, whatever that ends up being20:51
annegent_ttx: once you earn a tag, how long do you hold it?20:52
ttxannegent_: as long as that project chooses to use that release model20:52
annegent_ttx: dates picked by common?20:52
*** pritesh_ has joined #openstack-meeting20:52
ttxThis tag is not earned, it's just a factual dedc20:52
ttxdesc20:52
annegent_sure, should have written "apply"20:52
annegent_what's the cycling for tag reapplication20:52
ttxIf mikal tells me he switches nova to release:free and/or tags whenever he wants, tags will switch to release:free20:53
*** pritesh_ is now known as pritesh20:53
ttxannegent_: it changes to reflect the current situation, whenever it changes20:53
*** britthouser has quit IRC20:53
annegent_ttx: should these details be documented in this patch?20:54
ttxit's not a badge, it's more like a box20:54
*** tiswanso has quit IRC20:54
annegent_ttx: it's a sticker :)20:54
*** etoews has quit IRC20:54
*** BaconIsKing has joined #openstack-meeting20:54
ttxI think I make it pretty clear that it's a factual tag, but feel free to suggest alternate wording20:54
devanandaannegent_: one doesnt 'apply for' these tags, and no one needs to vote on their application.20:54
annegent_ttx: just making sure I understand20:54
*** britthouser has joined #openstack-meeting20:54
ttxannegent_: happy to talk to you off-meeting to clarify isf needed20:54
devanandaannegent_: sticker could have the connotation of something you earn for meeting a certain criteria, which I dont think is the intent here20:54
* ttx moves on20:55
ttxfollow-up on review20:55
ttx#topic Other governance changes20:55
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:55
annegent_devananda: badge doesnt?20:55
ttx* Add Cinder's os-brick library to cinder (https://review.openstack.org/153673)20:55
ttxThis one has 7 YES -- not a big fan of the os- prefix but I'm fine to be outnumbered20:55
ttxactually 8 YES20:55
ttxApproving now unless someone has a last-minute objection20:55
ttx* Adding Piet Kruithof as Horizon ATC (https://review.openstack.org/154271)20:55
annegent_devananda: ah sorry, nevermind my words are not working :)20:55
ttxmikal spotted that Piet is not a Foundation member, which is a requirement to be an ATC (not a requirement to contribute, just a requirement to be an ATC and get a vote)20:55
devanandaannegent_: np. happy to discuss postmeeting20:56
mikalWell he might be20:56
mikalBut I can't find him20:56
mikalWe should ask him20:56
ttxdavid-lyle: you mightj want to suggest him to join, or drop the request20:56
russellbnice attention to detail :)20:56
*** rushil_ has joined #openstack-meeting20:56
ttx* Add board-owned openstack/defcore repository (https://review.openstack.org/155738)20:56
david-lyleI will track down20:56
ttxI'd like 7 YES on this one since it defines the concept of board-owned repositories to mirror the tc-owned ones20:56
ttxI think we should encourage the BoD to use git and Gerrit more, so I'm all +1 on this20:56
mikaldavid-lyle: I think him joining would be sufficient for my emotional needfs20:56
*** rushil has quit IRC20:56
russellbttx: +120:57
ttx6.. one more ?20:57
ttx7, thx20:58
russellbotherwise this stuff will live in google docs20:58
russellbor private docs20:58
sdagueyep, gerrit ftw20:58
ttxin hell!20:58
*** baoli has joined #openstack-meeting20:58
mikalAs long as those docs aren't in a private irc channel...20:58
russellblol20:58
mikal:P20:58
ttx* Add ironic-lib to Ironic program (https://review.openstack.org/157757)20:58
ttxThat one still could use some details on how ironic-specific those utilities are20:58
*** thingee has joined #openstack-meeting20:58
ttxto make sure they aren't a better match for Oslo20:58
mikalI feel Jim's second argument there is weak20:58
mikalBut yeah, all I want is some due dilligence there20:59
*** Mandell has joined #openstack-meeting20:59
devanandaI should follow up between jroll and dhellmann on this20:59
ttxso let's keep that one up a bit more20:59
mikalPerhaps we could ask dhellmann to take a look?20:59
ttx#topic Housekeeping changes20:59
*** openstack changes topic to "Housekeeping changes (Meeting topic: tc)"20:59
sdagueyeh, though, honestly this has been a direction tons of projects are headed down20:59
ttx* Change TripleO PTL to James Slagle (https://review.openstack.org/157216)20:59
*** BaconIsKing has quit IRC20:59
ttx^ obvious repo housekeeping, so I'll approve it now20:59
ttx* openstack-spec housekeeping (https://review.openstack.org/#/c/156717/)20:59
lifelessttx: they can always move later, lets not let become too hidebound20:59
ttx^ That one is on openstack-specs, not governance, will approve it now too20:59
ttxsceram if you disagree20:59
sdaguewe have keystonemiddleware, ceilometeremiddleware, for instance. Might be nice to name things better the *middlerware or *lib21:00
ttx* Build list of teams from YAML file (https://review.openstack.org/125788)21:00
ttxThere was a nit on boilerplate there, maybe we can fast-fix it21:00
devanandasdague: short version is, I think, folks in Ironic just want to iterate on a lib that we use, without the process overhead of oslo, or waiting on oslo-incubator when none of us have core status there21:00
ttxWill approve later in the week once that's addressed21:00
lifelesssdague: now I want to have a bette-middlerware repo, just because21:00
ttxNo time for open discussion21:00
sdaguelifeless: :)21:00
mordredlifeless: wins21:00
sdaguettx: why do you hate open!?!?!21:01
sdague:)21:01
annegent_:)21:01
jeblairlib is short for liberty, right?21:01
ttxok, closing this one, thx everyone21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
mikalBye!21:01
openstackMeeting ended Tue Feb 24 21:01:36 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-02-24-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-02-24-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-02-24-20.02.log.html21:01
ttxcourtesy PTL ping: dhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov, mikal: around ?21:02
eglynno/21:02
morganfainbergo/21:02
david-lyleo/21:02
mesteryo/21:02
sdaguettx if there is time in the next meeting, I think client library semver might be a good discussion21:02
jungleboyjo/21:02
asalkeldo/21:02
ttxsdague: ... maybe?21:02
thingeeo/21:02
bknudsonhi21:02
sdaguegiven the just broken icehouse tree on python-ceilometerclient21:02
*** vivek-ebay has quit IRC21:02
ttxsounds like a good PSA. If you can keep it short I can let you go first21:03
ttx#startmeeting crossproject21:03
openstackMeeting started Tue Feb 24 21:03:09 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: crossproject)"21:03
sdaguesure21:03
openstackThe meeting name has been set to 'crossproject'21:03
ttxOur agenda for today:21:03
jogosdague: ++21:03
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:03
*** tiswanso has joined #openstack-meeting21:03
ttx#topic PSA from the Gatekeepers21:03
*** openstack changes topic to "PSA from the Gatekeepers (Meeting topic: crossproject)"21:03
ttxsdague: open fire21:03
notmynamehere21:03
sdagueso semver: X.Y.Z21:03
sdaguethe Z is meant to be extremely minor, guarunteed compatible changes21:04
sdaguenot just the next release21:04
SergeyLukjanovo/21:04
mtreinishsdague:21:04
*** annegent_ has quit IRC21:04
*** SridharRamaswam1 has joined #openstack-meeting21:04
sdaguedefinitely not a new release that has non Z bumps of dependencies  :)21:04
mtreinishwell that's a paste buffer fail21:04
ttxyes, adding a dep is NOT minor21:04
* devananda steps afk for a few minutes21:04
mtreinishthere it is: http://semver.org/21:04
sdagueor bumping keystoneclient a Y21:04
*** SridharRamaswamy has quit IRC21:04
lifelessits also in our pbr docs :)21:05
bknudsonwe're going to have a lot of Y.0s.21:05
sdaguemtreinish: yep, good reference21:05
ttxlifeless: damn people don't read21:05
lifelessthats fine21:05
morganfainbergbknudson, keystonelcient and middleware does have a lot of Y.0's21:05
sdaguebknudson: fortunately, there is an infininite number of numbers21:05
morganfainbergbknudson, for that reason.21:05
sdagueso we have some room21:05
mtreinishbknudson: and that's fine21:05
mikal.21:06
clarkbsdague: thankfully they are countably infinite21:06
ttxsdague: more on that topic ?21:06
sdaguettx: just that a lot of library releases recently have been defaulting to Z bumps21:06
sdagueand broken things pretty badly in the process21:06
ttxquestion is... is that just a mistake, or were they thinking it really was only worth a Z ?21:07
sdagueso please really think about that, python-ceilometerclient was the latest one21:07
mtreinishttx: probably worth point out: http://lists.openstack.org/pipermail/openstack-dev/2015-February/057699.html21:07
sdagueright, I don't know21:07
lifelessI might up-prioritise teh pbr semver finalisation21:07
lifelesswhich will go a long way to fixing this21:07
ttxbecause it feels like 75% of them are wrong21:07
bknudsonthere's no review of release #s... just update the tag... seems easy to make a mistake.21:07
ttxif only we could review the proposed tag21:07
* eglynn puts hand up ... the python-ceiloclient was a thought-fail on my part21:07
sdagueanyway, mostly a PSA, so we try to do less of it in the future21:07
sdagueand I'm done21:08
*** jokke_ has joined #openstack-meeting21:08
lifelessI think its worth a -dev mail21:08
lifelesswould you like me to send one?21:08
*** salv-orlando has quit IRC21:08
sdaguelifeless: sure21:08
ttxlifeless: can't hurt21:08
ttxalright, back to our regular schedule21:08
*** faizan has left #openstack-meeting21:08
ttx#topic Proposed evolution in release management tracking for Liberty21:08
*** openstack changes topic to "Proposed evolution in release management tracking for Liberty (Meeting topic: crossproject)"21:08
ttx#link https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking21:08
* devananda returns from afk21:08
ttxSo this is the result of a long discussion I had with various PTLs and release liaisons over the Kilo cycle21:08
ttxBasically, we spend a lot of time and 1:1 syncs trying to craft a prediction of what will land in the next milestone21:09
ttxAnd most of the time that prediction is blatantly false (we postpone a lot of stuff) and useless (nobody really consumes it)21:09
ttxIn particular, product managers appear to be more interested in a general idea of what's being worked on and its completion rate21:09
ttx...rather than a failed attempt at listing milestone we hope that will land21:09
ttxSo as far as release tracking is concerned, the idea would be to focus on communicating what landed at each milestone / release21:09
ttxAnd then, encourage assignees to directly update the completion rate of their features on the blueprint page21:09
*** rfolco has quit IRC21:10
ttxThat doesn't prevent teams from having cycle goals and specifically track those21:10
ttxBut as far as release management is concerned I would only focus on what actually landed21:10
ttx...since my influence on what gets done everywhere appears to have... diluted21:10
ttxAlso note that this proposed change is orthogonal to the idea of reorganizing development cycles which is the new ML hotness21:10
ttxEven if we switched to releasing more often, release management would still focus on what was done and what people are working on21:10
ttx...leaving goal setting and prioritization to each project team21:11
ttxThat should all free up more time to provide project teams with useful tools to facilitate their own tracking21:11
asalkeldttx: sounds like a great direction IMO21:11
*** aysyd has quit IRC21:11
ttxHow does that evolution sound ?21:11
devananda+10021:11
zaneb+1 I never understood how being able to predict accurately what would be in the release the day before the release was helpful to anyone21:11
morganfainbergwfm21:11
ttxzaneb: we used to be good at prediction21:11
rockygttx: ++21:11
*** baoli has quit IRC21:11
ttxwhen I was more deeply involved in each project21:12
nikhil_k+121:12
ttxbut that doesn't scale21:12
ttxAlso I originally thought downstream users were consuming our per-milestone predictions, but apparently they are not21:12
morganfainbergwe need ttx clones for that to scale :P21:12
ttxMaybe it's because those are unreliable, maybe that was never an interesting piece of info21:12
*** andreykurilin_ has joined #openstack-meeting21:12
*** baoli has joined #openstack-meeting21:12
ttxAnyway, focusing on setting goals/priorities, listing what's being worked on and tracking what actually landed sounds like a better use of our collective time21:12
jokke_+121:12
jungleboyjttx +121:12
zanebttx ++21:12
jroll+121:12
david-lyle+121:12
devanandafwiw, I've started dragging BadCub into doing PM work for us (Ironic)21:12
eglynn+121:12
devanandamorganfainberg: ++ for ttx clones21:13
ttxAlso we'd still track RC bugs the same way we always did. This is just about meilstone targeting of stuff and keeping that accurate all the time21:13
ttxanyway, we'd start that for Liberty21:13
notmynamettx: on that linked wiki page, you propose dropping 1:1s. but you didn't mentione that just now21:13
jokke_ttx: getting too big to be fully up to date with everything? :P21:14
ttxright... 1:1s were mostly used to make sure the milestoen page is up to date21:14
ttxnotmyname: I think two of them differed21:14
nikhil_kI see a lot of value in 1:1 or some place to be able to do so21:14
ttxThe oslo one where I would actually coordinate release processes with Doug21:14
*** ibiris_away is now known as ibiris21:14
*** changbl has joined #openstack-meeting21:14
ttxThe swift one where we would exchange on what's going on in swift21:14
notmynameI have found the weekly 1:1s to be useful and helpful21:15
devanandattx: I get value out of our 1:1's - but it's not in keeping the milestone page up to date ahead of time.21:15
ttxNot exactly sure yet but I'll probably keep syncing with oslo and other delegated release teams21:15
rockygHaving the equivalent of 1:1s with the PMs of any project that has them would go a long ways21:15
thingeettx: +121:15
*** lpmulligan has quit IRC21:15
ttxnotmyname: I feel like it's the wrong forum to communicate though21:15
ttxI see value in regular touch points on project status21:16
ttxas a lightweight way to give a general idea of where you stand, without formal status reports21:16
rockygRelease/PM liasons21:16
notmynamettx: the regularly scheduled time was the most helpful part. if we're going to regularly communicate, that's hard without a formal time. in part because we're in such different time zones21:16
ttxbut i'm not sure that has much to do with release management vs. general comm21:16
ttxMost of the 1:1s end up being completely useless21:17
notmynameI'd agree it's general communication more than release managerment (for me/swift)21:17
*** andreykurilin_ has quit IRC21:17
*** andreykurilin__ has joined #openstack-meeting21:17
ttxlike .. let's see your milestona page, hmm.. keep up the good work... next21:17
notmynamewell, I do like the rest of the proposal to track reality instead of predictions :-)21:17
ttxswift version: "any idea when your next release will be ? no... ok next21:18
david-lyleinformation that used to be covered in the project meeting was relegated to the 1:1, where now?21:18
ttxanyway, not totally sure how i'll evolve the format of 1:1s21:18
notmynameto be fair, very few swift 1:1s have been like that :-)21:18
ttxbut I note that some of you like them enough to ask that they stay21:18
*** BadCub has joined #openstack-meeting21:18
thingeeGenerally I've communicated in these meetings deadline dates to ttx. Advice on actions or how courageous I want to be in a milestone have came from chats with previous PTL's or TC21:19
ttxthey just are vbery costly in time for me21:19
*** vivek-ebay has joined #openstack-meeting21:19
notmynamettx: realize that you've got a bunch of tech people actually asking for regular meetings. this is crazy!21:19
ttxmaybe we could mix several projects and do them at the same time21:19
ttxlike a morning slot and an end of day slots21:19
jokke_ttx is using some kind of black magic21:19
ttx(would avoid me repeating the same "warning, kilo-3 coming up" to 12 different projects)21:20
mesteryttx: ++ to that idea!21:20
jokke_ttx: you should be able to write really simple script to do that :D21:20
ttx#action ttx to think about evolving 1:1 sync rather than removing them21:20
rockygInstead of project meeting, have a release meeting slot and anyone who wants to discuss the release schedule/status shows up21:21
notmynameI'd worry about bystander effect where something isn't said because of other people talking or waiting for someone else to say something (if they became 1:*s instead of 1:1s)21:21
rockygBut leave project meeting.21:21
notmynamebut that can probably be dealt with21:21
*** jang has quit IRC21:21
ttxOK, let's move on, i'll think about it and propose on the ML21:21
david-lyleI'm ok with their removal, I would like to have perhaps some common reminders at the beginning of this meeting21:21
SergeyLukjanovprobably all ptls could prepare a weekly report weekly to share status21:21
ttxjust wanted to see if the general direction was good or not21:21
SergeyLukjanovttx, like moving part of the responsibility to ptls21:21
notmyname1:1s not as a release thing but as a "communicate with the chair of the TC" thing21:22
*** sandywalsh has quit IRC21:22
devanandanotmyname: ++21:22
*** andreykurilin_ has joined #openstack-meeting21:22
*** andreykurilin__ has quit IRC21:22
ttxcould do formlal offie hours21:22
devanandaalso as a collective body of notes afterwards of what each PTL thought worth sharing21:22
ttxformal* office*21:22
notmynamePTLs responsible (more) for releases and release tracking. 1:1s for communicating that to the rest of the openstack org21:22
morganfainbergttx, that probably is a good compromise21:22
morganfainbergit lets us quickly sync up as needed but not mandate it if nothing needs ot be said21:23
notmynamedevananda: +121:23
ttxack21:23
*** sandywalsh has joined #openstack-meeting21:23
rockygAnd if there are no updates for the week, PTL responsible for cancelling 1:121:23
*** novas0x2a|laptop has quit IRC21:23
ttxok, moving on21:24
ttx#topic openstack-specs discussion21:24
*** openstack changes topic to "openstack-specs discussion (Meeting topic: crossproject)"21:24
ttx* Add TRACE definition to log guidelines (https://review.openstack.org/#/c/145245)21:24
*** Longgeek has quit IRC21:24
*** novas0x2a|laptop has joined #openstack-meeting21:24
ttxThis one should be ready to move to final approval at next week TC meeting21:24
ttxMinor nits can be fixed on subsequent patches21:24
ttxso if you disagree, file your -1 asap21:24
ttxotherwise I'll have it rubberstamped by the tc next sweek21:24
ttxor week21:24
*** bknudson has left #openstack-meeting21:24
ttx* Cross-Project spec to eliminate SQL Schema Downgrades (https://review.openstack.org/#/c/152337/)21:25
*** bknudson has joined #openstack-meeting21:25
ttxThis one may be ready too. Just needs to pile up approvals on the latest patchset. If it gets enough I'll put it on next week TC agenda as well21:25
*** jcoufal has joined #openstack-meeting21:25
ttxmikal: if you still ahve an objection you might want to repost it21:25
ttx* Eventlet Best Practices (https://review.openstack.org/#/c/154642/)21:26
ttxSo for this one, some people are wondering if openstack-specs is the right place21:26
ttxSounds like development tips and tricks rather than an actionable change or transition21:26
ttxwhat do you all think ?21:26
morganfainbergthis feels like a devleoper doc? not a "things for people to do"21:26
morganfainbergso. -specs is a little odd imo21:26
ttxdo we have a place for general development tips ?21:26
bknudsonwiki21:26
ttxapart from undiscoverable wiki pages ?21:27
mtreinishttx: blog posts?21:27
ttxmtreinish: maybe21:27
dhellmannI think the source of this is in Oslo where we've started moving some of our "policies" that don't correspond to direct actions into the specs repo where we can vote on them, rather than just having them in the wiki.21:27
jokke_ttx: I think that should be in wiki not in the OS-specs21:27
dhellmannbnemec may just move this to the oslo.concurrency docs, but wanted a little more visibility to start21:28
sdaguenova has a devref section, it might be a good thing to propose a wider version of that21:28
dhellmannbut in general Oslo is not adding a lot of content to the wiki these days, because we're finding lib and spec repos better at hosting them21:28
dhellmannsdague: good idea, maybe you can leave that comment on the spec if you haven't already?21:29
devanandattx: on the sql downgrades spec, do we actually have sufficient feedback from operators to know that they aren't going to rage when we do that?21:29
rockygThe results belong in developer docs, including reviewer checklists, but the discussion and final resolution that leads to the docs needs a home21:29
*** noslzzp has quit IRC21:29
bknudsonso openstack-specs becomes a cross-project developer docs?21:29
sdaguedhellmann: yeh, will do21:29
dhellmannsdague: thanks21:29
ttxhrm, looks like I have network issues21:29
jokke_rockyg & all: do we need devdocs repo?21:29
*** MarkAtwood has quit IRC21:29
*** FallenPegasus is now known as MarkAtwood21:29
*** garyh has quit IRC21:30
ttxIf I disappear, someone can take over the meeting agenda and finish it21:30
*** MarkAtwood has quit IRC21:30
sdaguebknudson: no, I'm suggesting there is something else that we need. devref at a global level21:30
morganfainbergdevananda, i would like to hold off until post operator summit in philly (cc ttx) for the downgrade thing21:30
morganfainbergsee if we can get some more feedback directly21:30
*** aranjan has joined #openstack-meeting21:30
sdaguemorganfainberg: good idea21:30
*** jang1 has joined #openstack-meeting21:30
morganfainbergif someone who is going to be there can poke at people21:30
dhellmannbknudson: maybe? since they were sort of "guidelines" we thought this would be a good place to get reviews21:30
morganfainbergsince i will not be at the operator summit21:30
rockyglike sdague said, devref for all O.O projects21:30
sdaguemorganfainberg: I can bring it up21:30
morganfainbergs/summit/midcycle21:30
morganfainbergsdague, thanks21:30
*** garyh has joined #openstack-meeting21:30
sdaguemorganfainberg: can you poke Tom about it, so he can figure out where on the agenda it should go21:31
*** garyh has quit IRC21:31
morganfainbergyes will do21:31
ttxmorganfainberg: ok, could you annotate the review as such ? like -1ing it so that I don't miss it ?21:31
bknudsonI feel like a cross-project devref has been discussed before...21:31
morganfainberghe's usually awake late pacific time, right?21:31
morganfainbergttx, will do.21:31
*** garyh has joined #openstack-meeting21:31
devanandamorganfainberg: ++. or even until post-summit21:31
*** Sukhdev has quit IRC21:32
ttxSo back to central devref... I'll kick off a thread on that21:32
morganfainbergdevananda, i think this is a case where the operator focused thing at philly will be easier to get clear feedback that an the summit. but in either case.21:32
ttx#action ttx to start thread on central devref for "Eventlet Best Practices" like things21:32
dhellmannttx: if we think that's a good idea, I can propose creating a repository21:32
morganfainbergdevananda, a minor delay would be good *kicks that enter key*21:33
ttxdhellmann: you take the action ?21:33
dhellmannttx: sure21:33
ttxI'd rather have athread first21:33
*** vivek-ebay has quit IRC21:33
dhellmann#action dhellmann start thread on publishing a central developer reference21:33
ttxto check if the idea is good before moving to implementation21:33
ttx* Add library stable release procedures/policy (https://review.openstack.org/#/c/155072/)21:33
*** femto has joined #openstack-meeting21:34
ttxdhellmann: up to introducing that one ?21:34
bknudsonI like the idea of a cross-project devref... would make it easier to see where projects have diverged and could consolidate.21:34
dhellmannttx: sure21:34
dhellmannthis spec is related to the requirements management changes we've made, where we are now capping libraries in stable branches21:34
dhellmannin the past, we've not had stable branches for the clients and we've only had them for some oslo libraries21:35
dhellmannmy proposal  is that since we are now capping all libraries, we should have stable branches for all of them and do backports21:35
*** lpmulligan has joined #openstack-meeting21:35
ttxrare backports21:35
*** AJaeger_ has left #openstack-meeting21:35
dhellmannsdague brought up semver earlier in the meeting, and this assumes we're all following the semver rules21:35
ttxas in security-fix-backports21:35
dhellmannright, or serious crashes or something21:35
dhellmannnot features21:35
ttxor OMG-that-bug-eats-my-data-backport21:36
*** ijw has joined #openstack-meeting21:36
jogodhellmann: would these stable branches be lazy created, as on only made when needed?21:36
dhellmannjogo: in order for some of the CI jobs to work correctly, we need to create them all proactively21:36
bknudsonwe haven't done security fix backports for clients... also I'm not sure that packagers would pick the same version # for their packages...21:36
dhellmannjogo: some of the jobs do things like check out stable/foo and fall back to master21:36
morganfainbergdhellmann, i've been thinking that stable client branches might need to occur in general.21:36
*** noslzzp has joined #openstack-meeting21:37
dhellmannmorganfainberg: right, that would be part of this, too21:37
bknudsonif we did happen to pick the same version to ship with the release then having security backports would be nice.21:37
*** JRobinson__ has joined #openstack-meeting21:37
morganfainbergit would actually solve an issue i have with keystoneclient21:37
dhellmannbknudson: well, the idea is we would start saying "inside your cloud, use these versions of the client; outside of your cloud use whatever you want"21:37
ttxbknudson: distros increment their side of the version number, not ours21:37
*** sdake has quit IRC21:37
morganfainbergbecause then we could easily remove things that are moribund / bit rotting after a reasonable time21:37
jogodhellmann: hmm, it may be easier to change the tests versus creating all those branches when most wont be used21:37
morganfainbergrather than carrying it indefinitely21:37
morganfainbergit changes how clients can be viewed overall21:38
dhellmannjogo: most of this can be automated, and the work is distributed among all of the teams, so I don't think it's going to be that much work21:38
*** femto has quit IRC21:38
rockygmorganfainberg: +121:38
dhellmannif we delay creating the branches, then fixing a critical bug becomes a big infra push instead of just a patch in the right place21:38
jogodhellmann: true21:38
dhellmannfewer people have the ACLs to create branches than approve backports21:39
jokke_how about <next minor and the next lib/client release after RC1 needs to bump minor?21:39
dhellmannso it just becomes part of our end-of-cycle release process, and most teams only have one or two anyway -- oslo is going to be impacted the most21:39
*** SridharRamaswam1 has quit IRC21:40
dhellmannjokke_: I have some timing details in the proposal21:40
lifelessmail sent on semver21:40
*** marun has joined #openstack-meeting21:40
jokke_that would leave the X.Y.<what-ever-needed> as "stable" branch of lib21:40
dhellmannwe'll synchronize using the global requirements caps21:40
dhellmannjokke_: yes, that's the idea21:40
dhellmannoslo has been doing this, so the proposal is just to expand it to everyone else now, too21:41
sdagueso, I actually think the issue is g-r sync with libraries21:41
jokke_dhellmann: ++21:41
sdaguebecause g-r works really well when everything releases all at once21:41
sdaguebut with adhoc releasing, we can see how it breaks down21:41
*** matrohon has quit IRC21:41
sdagueand the adhoc releasing has been really good for other reasons, but put new strains on the old system that didn't anticipate it21:42
bknudsondhellmann: have you had a security backport? I don't think I've seen one.21:42
jokke_dhellmann: although that saves us only on OS ... wish we could expand that to 3rd parties as well :P21:42
dhellmannbknudson: we haven't had a security issue, but we did have some backports of bug fixes into juno21:42
jogosdague: and g-r artificially bumps minimums for a lot of things21:42
ttxso.. please provide comments on that review if you care21:42
dhellmannright21:43
*** SridharRamaswam1 has joined #openstack-meeting21:43
ttxunless there are more pressing questions/comments on this one, I propose we move on ?21:43
ttxtaking silence as yes21:44
ttx* Replace eventlet with asyncio (https://review.openstack.org/#/c/153298/) vs. Replace eventlet + monkey-patching with threads (https://review.openstack.org/#/c/156711)21:44
*** ebalduf has joined #openstack-meeting21:44
ttxSo those are two competing way forward on how to move from eventlet21:44
ttxeven if we did not formally decide to move on21:44
ttxI think it's not bad to lay the options out there21:44
asalkeldoption 3 == stay with eventlet21:44
devanandattx: on this, I'm not yet convinced that there's significant enough benefit for us to mandate a whole bunch of work when, yea, we haven't even agreed that we need to move on right now21:45
ttxI think both are missing an analysis of the switching cost and a perf analysis21:45
bknudsonkeystone went to running server in apache httpd... instead.21:45
morganfainbergasalkeld, option 4 == mod_wsgi/uwsgi/unicorns21:45
dhellmannthe issues with eventlet that caused us to start this discussion (the python 3 support) are getting better, but are still not 100% resolved afaik21:45
morganfainbergbknudson, ++ and we're slating a deprecation of eventlet this cycle and complete removal in M21:45
*** pnavarro has quit IRC21:46
sdaguemorganfainberg: mod_wsgi works less well for non API services21:46
ttxdevananda: yes, I agree with you21:46
morganfainbergsdague, fair point21:46
ttxjust wondering what to do with those21:46
devanandasdague: ++21:46
dhellmannttx: ++ on the performance analysis. I think haypo is working on a version of ceilometer that doesn't need eventlet as a demo of the scale of changes that need to be made.21:46
sdaguethe fact that keystone has no workers makes it special in that way21:46
SergeyLukjanov++ for perf analysis21:46
ttxI liked zzzek(sp?) analysis21:46
devanandaironic-api works fine in apache mod_wsgi, but the bulk of our work (like nova) is not in the API service21:46
morganfainbergttx, a few more eees in there but close enough.21:46
eglynnone clear difference between the options IIUC is that the asyncio plan involves limiting the initial change to oslo-messaging and ceilometer21:46
eglynn(or some subset thereof)21:46
dhellmannyeah, we recognize that any solution has to support WSGI, SQLAlchemy, and the message bus21:47
eglynnwhereas the threads apprach would require an audit across all projects21:47
devanandais this actually about performance at all?21:47
* asalkeld not crazy about asyncio21:47
devanandaor just about py3 support (or lack thereof)21:47
eglynnmore correctness than perf21:47
*** unicell has joined #openstack-meeting21:47
ttxThe only benefit I see to syncio is that it's the "future in Python"21:47
ttxasyncio*21:47
*** sdake has joined #openstack-meeting21:47
dhellmanneglynn: well, that initial proposal is just to give people an idea of the changes, but would eventually apply to all projects21:47
dhellmanndevananda: mostly py3 and developer issues, but we don't want performance to degrade heavily21:48
eglynndhellmann: true, once proven out to some extent presumably21:48
morganfainbergif eventlet grows py3 support - there is no reason we can't stay with it. It does obscure things in wierd ways because of the monkey patching, where asyncio is explicit development [afaict]21:48
dhellmanneglynn: right21:48
*** sdake has quit IRC21:48
morganfainbergso, it becomes the question of "which way do we want to go"21:48
eglynnunfortunately haypo doesn't seem to be around to represent the asyncio case21:48
*** ebalduf has quit IRC21:48
dhellmannmorganfainberg: the monkey-patching is starting to cause conflicts with import order in some of the applications21:48
morganfainbergdhellmann, aye.21:48
sdagueeventlet 0.17.0 (released yesterday) is passing all it's tests on py321:48
sdaguefwiw21:48
morganfainbergdhellmann, as said because monkeypatching is wierd.21:48
dhellmannwe had a bug filed against oslo.concurrency, let me see if I can find that21:48
morganfainbergdhellmann, actually we hit something in keystone regarding log stuff and threading.lock issues21:49
devanandamoving away from monkey patching would be great. but is it worth a massive amount of work? I dunno -- seems like a per-project decision21:49
ttxI don't expect us to settle it in the next 10 minutes... I just wonder what to exactly do with those21:49
devanandanot something we should be mandating21:49
jogoso this sounds like something that we may not need to have a openstack wide decision on21:49
dhellmannsdague: yeah, I haven't looked yet to see if their py3 support now monkeypatches everything. At one point it didn't.21:49
morganfainbergdhellmann, it has a lot of subtle pitfalls21:49
jokke_devananda: ++21:49
jogonot sure what the risk is for projects each doing there own thing.21:49
dhellmann#link https://bugs.launchpad.net/oslo.concurrency/+bug/141854121:50
openstackLaunchpad bug 1418541 in neutron "processutils checks whether stdlib is monkey patched during import" [Undecided,Fix committed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)21:50
bknudsonif it works really great for ceilometer or whoever picks it then that can convince others.21:50
sdaguejogo: that was one of the reasons I think there should be a higher level statement of some sort21:50
dhellmannjogo: well, for one thing we don't want to have to support all of the various options in oslo21:50
eglynnjogo: difficulty in on-boarding devs moving between projects for one thing21:50
jokke_jogo: I guess we will see in a while after we get the feedback from keystone apache trial ;)21:50
sdagueeglynn: yes, exactly21:50
devanandadhellmann: if oslo switches, what is the immediate impact to projects?21:50
dhellmannbecause we don't want to have to have forks of libs for eventlet, asyncio, and threading support21:50
ttxyeah, I'm not very excited at the prospect to learn 5 different async models21:50
*** mrmartin has quit IRC21:50
SergeyLukjanovttx, ++21:50
sdagueeglynn: also, the difficulty for ops to track down issues21:50
morganfainbergjokke_, we have recommended apache be used for 4 cycles now, and most scaled up deployments use it. so i think the feedback has been "yep this is working" ;)21:51
jogoeglynn: I would be really surprised if having multiple options would make moving between projects harder21:51
notmynameis anyone else concerned that the 2 projects that are proposing to be test cases for dropping eventlet have plugins (middleware) for every other project?21:51
*** irenab has quit IRC21:51
jogodhellmann: yeah that is fair21:51
ttxthink about those of us that are cross-project, and how to facilitate their work rather than complicate it21:51
dhellmanndevananda: I want Oslo to push for a decision, but follow the overall project on this.21:51
devanandadhellmann: I'm guessing it would break them. which means coordinating the roll-out of that change in oslo becomes a support headache21:51
morganfainbergjokke_, and devstack defaults to apache for keystone too21:51
sdagueif every project has different concurrency models21:51
devanandadhellmann: which means oslo can't make the change unless every project agrees?21:51
devanandaI hope I'm wrong on that21:51
ttxi mean, I'm fine with migrating from one to another, but not very thrilled at the idea of encouraging everyone to pick21:51
eglynnjogo: a lot of the perceived problem is the subtle bugs that arise, and each approach has a different class of subtle pitfalls IIUC21:51
dhellmanndevananda: oslo.messaging already supports both threads and eventlet, but the application has to invoke it differently21:51
*** jang1 has quit IRC21:51
*** marun has quit IRC21:51
bknudsondoes having keystone running in httpd cause cross-project problems?21:51
jogowell we are really taking about 3 models? thread based (putting mod_wsgi in here), eventlet, asynicio21:52
bknudsonwe're kind of stuck since we need apache for federation.21:52
dhellmannso we're not going to just say "oslo is doing this" and start breaking things -- that's why we're having this as a cross-project discussion instead of an oslo spec21:52
morganfainbergbknudson, as far as i know there are minor issues with docs and questions about restarting keystone. but largely no.21:52
bknudsonI know it makes the test logs kind of iffy.21:52
sdaguejogo: mod_wsgi really is a 4th thing, as it's process forks21:52
devanandadhellmann: gotcha21:52
morganfainbergbknudson, and logging is ... well logging.21:52
ttxjogo: so we'd say "one of those" rather than "whatever you want" ?21:52
*** vishwanathj has joined #openstack-meeting21:52
jogottx: sure21:52
devanandasdague: mod_wsgi is orthogonal since it doesn't address non-API services21:52
ttxjogo: sounds slightly better21:52
sdaguedevananda: sure21:53
dhellmannsdague, jogo : I'm lumping "wsgi" into one thing, since it really shouldn't matter to the code which container it's running in21:53
*** sdake has joined #openstack-meeting21:53
sdaguebknudson: wsgi should be fine for API surfaces21:53
morganfainbergsdague, i would say wsgi would be a good choice for api surfaces. typically would be my choice if I could encourage all the projects to move that way.21:53
morganfainbergsdague, but that is a tall order as well21:53
devanandamorganfainberg: ++ for api surfaces21:54
*** narenhn has quit IRC21:54
dhellmannmorganfainberg: all of our rest APIs are WSGI now, served with the eventlet WSGI container. We should be able to plug them into something else if we stop using eventlet.21:54
dhellmannunless you found out otherwise in keystone?21:54
ttxhmm, so rather than dive more into details... what is the way forward for these specs ? Iterate until they ahve a clearer cost/benefit analysis ?21:54
*** jang1 has joined #openstack-meeting21:54
devanandadhellmann: you probably already said it, but what's the impact on oslo to (continue) support(ing) both eventlet and asyncio?21:54
morganfainbergdhellmann, i meand mod_wsgi sorry missed a 'mod_' in there. mod_wsgi/uwsgi/unicorns21:54
bknudsonwe've got separate launchers, one for eventlet-server and one for apache.21:55
jogottx: I like sdague's idea of a higher level spec of some sort21:55
morganfainbergdhellmann, but yeah there is some magic needing in some cases because things are... well.. odd with eventlet21:55
dhellmannttx: yeah, it would be good if folks would post some of these questions on the specs so the authors know what sort of additional research is needed21:55
ttxjogo: agree -- the need to change and the options21:55
morganfainbergdhellmann, so there is a bit of extra wrapping needed in most cases.21:55
dhellmannmorganfainberg: right, that's why we want to stop using eventlet :-)21:55
jogohaving a single spec with all the recommended options, along with tradeoffs, would be a nice end result21:55
*** sgordon is now known as steveg21:55
morganfainberg:-)21:55
dhellmannsdague: what higher level spec would you want to see?21:56
bknudsonhere's the keystone launchers: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/server21:56
ttxsdague: would you take the action of suggesting a meta spec and/or merging the options into a metaspec ?21:56
sdaguedhellmann: well, a statement of direction of where we are headed21:56
*** sdake_ has joined #openstack-meeting21:56
sdaguebecause "in all the directions" seems ... unproductive21:56
ttxdhellmann: I think both options need to tackle the cost/benefit analysis for change21:56
dhellmannsdague: we have 2 competing proposals and we want folks to express opinions between them. Does a meta-spec make that easier?21:57
sdaguettx: honestly, I'm not sure I'm a good person to do that, I'm mostly just asking questions.21:57
*** wojdev has joined #openstack-meeting21:57
ttxok, I'll take it21:57
*** wojdev has quit IRC21:57
sdaguedhellmann: oh, I'm fine with the existing proposals to flesh this out21:57
ttx#action ttx to suggest some metaspec on the various async potential plans21:57
sdaguesorry, I didn't mean we needed a 3rd thing to explore that21:57
lifelessdhellmann: so I'd like to get rid of the message bus as it stands today; its a source of bugs (they way we use it, not it per se)21:57
sdagueI think we need to be driving to a set of project wide guidelines at the end of the day21:57
dhellmannyeah, ok, I think ttx misunderstood? or maybe he wants it?21:57
ttxI think they can all work on the same spec with options21:57
dhellmannlifeless: that is a whole different spec21:58
sdagueand a whole different set of bugs :)21:58
lifelessjogo: the risk is having different constraints placed on oslo21:58
dhellmannttx: ok, the template has a single proposal section, so I suggested the two camps write separate specs21:58
*** sdake_ has quit IRC21:58
ttxdhellmann: I'm fine with bending the template on that specific case21:58
lifelessdhellmann: yes, I know it is. Just catching up as quickly as I can w/backlog21:58
ttxstill a long way to go anyway21:59
dhellmannI thought we'd roll the rejected one into the approved one as a proposed alternative, at the end, but whatever you like is fine21:59
dhellmannlifeless: ok21:59
ttxThere was a last spec on the docker:21:59
ttxdocket*21:59
ttxfreudian slip21:59
dhellmannheh21:59
ttx* Return request ID to caller (https://review.openstack.org/156508) -- proposer not able to attend, please provide feedback on spec21:59
ttx#topic Open discussion & announcements21:59
*** openstack changes topic to "Open discussion & announcements (Meeting topic: crossproject)"21:59
ttxWe had 1:1s syncs today in #openstack-relmgr-office, logs at:21:59
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-02-24-09.04.html21:59
*** tsekiyama has quit IRC22:00
*** sdake__ has quit IRC22:00
ttx(that last spec above is about cross-project request ID tracking)22:00
*** tsekiyama has joined #openstack-meeting22:00
ttx(which is definitely a good thing to have)22:00
notmynamettx: seems to be cinder-specific22:00
rockygOperators really need something in that area22:00
ttxnotmyname: yeah, I was a bit confused at first read22:00
ttxseems to start general and then be only cinder22:01
mtreinishttx: there was previous work on that at some point22:01
jokke_who ever is attending to that ops meetup ... get them to comment in as well22:01
*** thangp has quit IRC22:01
*** shashankhegde has joined #openstack-meeting22:01
sdaguedo we have some history for why that was landed here?22:01
rockygjokke_: good point22:01
sdaguethingee: ?22:01
ttxsdague: nope22:01
jungleboyjnotmyname: It started in Cinder, I believe, but as it has been further investigated it is broader.22:01
*** Sukhdev has joined #openstack-meeting22:02
*** mwagner_lap has quit IRC22:02
ttxprobably needs to be less cindery22:02
rockygI think it was because a change in one project would cascade to others22:02
ttxanyway, time is up22:02
*** barrett has left #openstack-meeting22:02
jungleboyjRequires changes in Nova and anyone else using cinder22:02
ttxthx everyone!22:02
ttx#endmeeting22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Feb 24 22:02:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
jokke_thnx22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-02-24-21.03.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-02-24-21.03.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-02-24-21.03.log.html22:02
jungleboyjThanks!22:02
*** jokke_ has left #openstack-meeting22:02
sdaguejungleboyj: I think that's just a do it sort of thing, honestly22:02
jungleboyjsdague: I agree.  I think it needs to be done.22:03
*** banix has quit IRC22:03
jungleboyjsdague: Multiple moving parts to coordinate though.22:03
sdagueactually, I'm not even sure what needs to be done. I'd assume cinderclient would do the request id logging, which would be in the consumer22:03
sdaguemaybe I'm missing something22:04
rockygYeah a general spec that all projects agree to would keep all the efforts synced22:04
*** carl_baldwin has quit IRC22:04
jungleboyjsdague: I haven't looked in a while.  I think the problem is that we need to change the format of the body so that the request-id is sent along.22:05
*** BadCub has left #openstack-meeting22:06
jungleboyjsdague: The question is how to coordinate things so that we can do that without breaking other projects.22:06
*** eglynn has quit IRC22:07
*** tsekiyama has quit IRC22:08
*** tsekiyama has joined #openstack-meeting22:09
*** gyee has quit IRC22:09
*** pelix has quit IRC22:10
*** pkoniszewski has joined #openstack-meeting22:10
*** dboik has left #openstack-meeting22:10
*** narenhn has joined #openstack-meeting22:13
*** ijw has quit IRC22:13
*** hareeshp has quit IRC22:14
*** adahms has joined #openstack-meeting22:14
*** rm_work is now known as rm_work|away22:16
*** radez is now known as radez_g0n322:16
*** gyee has joined #openstack-meeting22:17
*** stevemar has quit IRC22:17
*** changbl has quit IRC22:17
*** xingchao has quit IRC22:17
*** marun has joined #openstack-meeting22:17
*** otter768 has joined #openstack-meeting22:18
*** gyee has quit IRC22:18
*** jungleboyj has quit IRC22:19
*** jang1 has quit IRC22:19
*** hareeshp has joined #openstack-meeting22:20
*** carl_baldwin has joined #openstack-meeting22:21
*** markstur has left #openstack-meeting22:21
*** neillc_uni is now known as neillc22:21
*** otter768 has quit IRC22:22
*** Riddhi has joined #openstack-meeting22:23
*** hareeshp has quit IRC22:25
*** jang1 has joined #openstack-meeting22:25
*** hareeshp has joined #openstack-meeting22:25
*** gyee has joined #openstack-meeting22:26
*** pkoniszewski has quit IRC22:28
*** SlickNik has left #openstack-meeting22:28
*** cody-somerville has joined #openstack-meeting22:29
*** hareeshp has quit IRC22:29
*** darrenc is now known as darrenc_afk22:29
*** Riddhi has quit IRC22:30
*** tiswanso has quit IRC22:31
*** Riddhi has joined #openstack-meeting22:31
*** erlon has quit IRC22:31
*** jang1 has quit IRC22:31
*** salv-orlando has joined #openstack-meeting22:33
*** gyee has quit IRC22:34
*** jcoufal has quit IRC22:35
*** dkranz has quit IRC22:35
*** scinawa has joined #openstack-meeting22:36
*** unicell has quit IRC22:37
*** garyh has quit IRC22:39
*** Riddhi has quit IRC22:39
*** vivek-ebay has joined #openstack-meeting22:40
*** VW_ has quit IRC22:40
*** baoli has quit IRC22:41
*** Riddhi has joined #openstack-meeting22:41
*** baoli has joined #openstack-meeting22:41
*** scinawa has quit IRC22:42
*** ebalduf has joined #openstack-meeting22:44
*** jang has joined #openstack-meeting22:45
*** henrynash has quit IRC22:47
*** nelsnelson has quit IRC22:47
*** Riddhi has quit IRC22:48
*** ebalduf has quit IRC22:49
*** achanda has quit IRC22:54
*** egallen has joined #openstack-meeting22:55
*** darrenc_afk is now known as darrenc22:56
*** rm_work|away is now known as rm_work23:00
*** moha_hunt has quit IRC23:01
*** harlowja is now known as harlowja_away23:02
*** harlowja_away is now known as harlowja23:05
*** bknudson has quit IRC23:07
*** mestery has quit IRC23:07
*** emagana has quit IRC23:08
*** Longgeek has joined #openstack-meeting23:09
*** kylek3h has quit IRC23:09
*** thomasem has quit IRC23:10
*** shashankhegde has quit IRC23:11
*** achanda has joined #openstack-meeting23:13
*** comay has quit IRC23:13
*** emagana has joined #openstack-meeting23:17
*** vivek-ebay has quit IRC23:17
*** aranjan has quit IRC23:18
*** marun has quit IRC23:19
*** comay has joined #openstack-meeting23:19
*** aranjan has joined #openstack-meeting23:20
*** lpmulligan has quit IRC23:20
*** egallen has quit IRC23:20
*** salv-orl_ has joined #openstack-meeting23:20
*** dane_leblanc has quit IRC23:20
*** lpmulligan has joined #openstack-meeting23:20
*** salv-orlando has quit IRC23:22
*** baoli has quit IRC23:23
*** baoli has joined #openstack-meeting23:23
*** hichihara has joined #openstack-meeting23:24
*** rbak has quit IRC23:25
*** sdake_ has joined #openstack-meeting23:25
*** cody-somerville has quit IRC23:25
*** jungleboyj has joined #openstack-meeting23:27
*** gyee has joined #openstack-meeting23:27
*** Watanabe has joined #openstack-meeting23:28
*** andreykurilin_ has quit IRC23:28
*** jecarey has quit IRC23:30
*** bobmel_ has joined #openstack-meeting23:32
*** kebray has quit IRC23:32
*** thingee has quit IRC23:33
*** jungleboyj has quit IRC23:34
*** bobmel has quit IRC23:35
*** ijw has joined #openstack-meeting23:38
*** henrynash has joined #openstack-meeting23:40
*** Longgeek has quit IRC23:42
*** ayoung has quit IRC23:42
*** ijw has quit IRC23:44
*** j05h has quit IRC23:45
*** ebalduf has joined #openstack-meeting23:45
*** jungleboyj has joined #openstack-meeting23:47
*** emagana has quit IRC23:47
*** emagana has joined #openstack-meeting23:48
*** achanda has quit IRC23:48
*** ibiris is now known as ibiris_away23:49
*** ebalduf has quit IRC23:49
*** emagana has quit IRC23:52
*** DaveJ__ has joined #openstack-meeting23:52
*** achanda has joined #openstack-meeting23:53
*** Apoorva_ has joined #openstack-meeting23:56
*** salv-orlando has joined #openstack-meeting23:56
*** Watanabe has quit IRC23:57
*** prad has quit IRC23:57
*** salv-orl_ has quit IRC23:57
*** lpmulligan has quit IRC23:58
*** joesavak has quit IRC23:58
*** bdpayne has quit IRC23:58
*** Apoorva has quit IRC23:59
*** xuhanp has joined #openstack-meeting23:59
*** baoli has quit IRC23:59

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