Tuesday, 2015-03-03

*** david-lyle has quit IRC00:00
*** thumpba__ has joined #openstack-meeting00:00
*** thumpba has quit IRC00:01
*** vivek-ebay has quit IRC00:03
*** VijayB has quit IRC00:03
*** markvoelker has quit IRC00:03
*** thumpba_ has quit IRC00:04
*** otter768 has joined #openstack-meeting00:04
*** SridharRamaswamy has quit IRC00:04
*** aimon has joined #openstack-meeting00:06
*** yamamoto has joined #openstack-meeting00:06
*** tiswanso has quit IRC00:07
*** ignacio-scopetta has joined #openstack-meeting00:08
*** otter768 has quit IRC00:09
*** ignacio-scopett1 has quit IRC00:10
*** rbak has quit IRC00:10
*** vivek-ebay has joined #openstack-meeting00:10
*** SridharRamaswamy has joined #openstack-meeting00:11
*** annegentle has quit IRC00:14
*** marun has joined #openstack-meeting00:15
*** VijayB has joined #openstack-meeting00:16
*** unicell1 has quit IRC00:17
*** unicell has joined #openstack-meeting00:17
*** iymht has joined #openstack-meeting00:17
*** stevemar has joined #openstack-meeting00:18
*** unicell has quit IRC00:18
*** unicell1 has joined #openstack-meeting00:18
*** dane_leblanc has quit IRC00:22
*** cdub has joined #openstack-meeting00:23
*** Riddhi has quit IRC00:24
*** xingchao has joined #openstack-meeting00:24
*** dims has quit IRC00:27
*** ebalduf has joined #openstack-meeting00:27
*** mtanino_ has joined #openstack-meeting00:28
*** mtanino has quit IRC00:29
*** eghobo has joined #openstack-meeting00:29
*** e0ne is now known as e0ne_00:33
*** e0ne_ is now known as e0ne00:33
*** e0ne has quit IRC00:34
*** marun has quit IRC00:35
*** alop has quit IRC00:36
*** bknudson has joined #openstack-meeting00:37
*** VijayB has quit IRC00:38
*** VijayB has joined #openstack-meeting00:44
*** markmcclain has quit IRC00:48
*** ignacio-scopett1 has joined #openstack-meeting00:48
*** IanGovett has quit IRC00:48
*** ignacio-scopetta has quit IRC00:48
*** markmcclain has joined #openstack-meeting00:48
*** MaxV has quit IRC00:51
*** dane_leblanc has joined #openstack-meeting00:52
*** xuhanp has joined #openstack-meeting00:53
*** hareeshp has quit IRC00:56
*** thomasem has quit IRC00:59
*** JRobinson__ has joined #openstack-meeting00:59
*** jdurgin has quit IRC00:59
*** Riddhi has joined #openstack-meeting01:00
*** jaypipes has quit IRC01:03
*** dannywil_ has quit IRC01:03
*** s3wong has quit IRC01:03
*** vivek-ebay has quit IRC01:04
*** markvoelker has joined #openstack-meeting01:04
*** otter768 has joined #openstack-meeting01:06
*** s3wong has joined #openstack-meeting01:08
*** dimsum__ has joined #openstack-meeting01:08
*** david-lyle has joined #openstack-meeting01:09
*** rmoe has quit IRC01:09
*** noelbk has quit IRC01:12
*** unicell1 has quit IRC01:12
*** unicell has joined #openstack-meeting01:12
*** markvoelker has quit IRC01:13
*** unicell has quit IRC01:13
*** unicell1 has joined #openstack-meeting01:14
*** ebalduf has quit IRC01:14
*** VW_ has quit IRC01:14
*** ebalduf has joined #openstack-meeting01:15
*** Mandell has quit IRC01:15
*** baoli has joined #openstack-meeting01:16
*** ebalduf has quit IRC01:16
*** Mandell has joined #openstack-meeting01:17
*** Sukhdev has quit IRC01:17
*** annegentle has joined #openstack-meeting01:17
*** nsaje_ has joined #openstack-meeting01:18
*** tiswanso has joined #openstack-meeting01:18
*** krtaylor has quit IRC01:20
*** jyuso1 has joined #openstack-meeting01:20
*** nsaje has quit IRC01:21
*** tomoe_ has joined #openstack-meeting01:21
*** VijayB has quit IRC01:22
*** xuhanp has quit IRC01:22
*** tiswanso has quit IRC01:23
*** nellysmitt has joined #openstack-meeting01:25
*** rmoe has joined #openstack-meeting01:25
*** ebalduf has joined #openstack-meeting01:26
*** xuhanp has joined #openstack-meeting01:27
*** bobmel has quit IRC01:27
*** bobmel has joined #openstack-meeting01:28
*** ivar-laz_ has joined #openstack-meeting01:28
*** annegentle has quit IRC01:29
*** sbalukoff has quit IRC01:29
*** ebalduf has quit IRC01:30
*** nellysmitt has quit IRC01:30
*** ivar-lazzaro has quit IRC01:31
*** watanabe_isao has joined #openstack-meeting01:31
*** dneary has joined #openstack-meeting01:31
*** ignacio-scopetta has joined #openstack-meeting01:31
*** ivar-laz_ has quit IRC01:32
*** krtaylor has joined #openstack-meeting01:33
*** ignacio-scopett1 has quit IRC01:33
*** zehicle_ has joined #openstack-meeting01:36
*** khaldrogox has quit IRC01:37
*** achanda has quit IRC01:38
*** zehicle_ has quit IRC01:41
*** ebalduf has joined #openstack-meeting01:41
*** zehicle_ has joined #openstack-meeting01:41
*** ddieterly has joined #openstack-meeting01:44
*** ebalduf has quit IRC01:44
*** bdpayne has quit IRC01:45
*** annegentle has joined #openstack-meeting01:45
*** zehicle_ has quit IRC01:45
*** asselin_ has joined #openstack-meeting01:46
*** dneary has quit IRC01:46
*** ddieterl_ has joined #openstack-meeting01:47
*** zehicle_ has joined #openstack-meeting01:47
*** ddieterly has quit IRC01:47
*** sarob has joined #openstack-meeting01:50
*** zz_johnthetubagu has quit IRC01:52
*** adalba has quit IRC01:52
*** david-lyle has quit IRC01:52
*** david-lyle has joined #openstack-meeting01:53
*** claudiub has quit IRC01:55
*** Longgeek has joined #openstack-meeting01:57
*** epico has joined #openstack-meeting01:58
*** carl_baldwin has quit IRC02:00
*** vivek-ebay has joined #openstack-meeting02:01
*** asselin_ has quit IRC02:02
*** kmartin has quit IRC02:03
*** annegentle has quit IRC02:03
*** zehicle_ has quit IRC02:06
*** rwsu is now known as rwsu-afk02:06
*** amitgandhinz has joined #openstack-meeting02:07
*** zehicle_ has joined #openstack-meeting02:07
*** leeantho has quit IRC02:08
*** SridharRamaswamy has quit IRC02:08
*** sigmavirus24 is now known as sigmavirus24_awa02:08
*** ayoung-lunx is now known as ayoung02:09
*** dmacpher is now known as dmacpher-afk02:09
*** zehicle_ has quit IRC02:09
*** zehicle_ has joined #openstack-meeting02:10
*** zehicle_ has quit IRC02:12
*** ChrisPriceAB has quit IRC02:13
*** zhhuabj has joined #openstack-meeting02:13
*** zehicle_ has joined #openstack-meeting02:13
*** thumpba__ has quit IRC02:15
*** aranjan has quit IRC02:15
*** tiswanso has joined #openstack-meeting02:16
*** thumpba has joined #openstack-meeting02:18
*** tiswanso has quit IRC02:19
*** zehicle_ has quit IRC02:19
*** zehicle_ has joined #openstack-meeting02:20
*** tiswanso has joined #openstack-meeting02:20
*** dmellado has quit IRC02:21
*** Mandell has quit IRC02:22
*** dmellado has joined #openstack-meeting02:22
*** VW_ has joined #openstack-meeting02:22
*** VW_ has quit IRC02:23
*** VW_ has joined #openstack-meeting02:23
*** david-lyle has quit IRC02:23
*** mtanino_ has quit IRC02:24
*** zehicle_ has quit IRC02:25
*** tomoe__ has joined #openstack-meeting02:25
*** zehicle_ has joined #openstack-meeting02:26
*** markvoelker has joined #openstack-meeting02:26
*** tsekiyama has quit IRC02:27
*** zehicle_ has quit IRC02:27
*** zehicle_ has joined #openstack-meeting02:27
*** tomoe_ has quit IRC02:28
*** annegentle has joined #openstack-meeting02:30
*** amotoki has joined #openstack-meeting02:32
*** zehicle_ has quit IRC02:32
*** zehicle_ has joined #openstack-meeting02:32
*** NarenNarendra has joined #openstack-meeting02:33
*** NarenNarendra has quit IRC02:33
*** VijayB has joined #openstack-meeting02:34
*** zehicle_ has quit IRC02:35
*** zehicle_ has joined #openstack-meeting02:36
*** annegentle has quit IRC02:36
*** mattgriffin has joined #openstack-meeting02:39
*** mattgriffin has quit IRC02:39
*** thumpba has quit IRC02:45
*** lazy_prince has quit IRC02:46
*** zehicle_ has quit IRC02:47
*** thangp has joined #openstack-meeting02:48
*** amitgandhinz has quit IRC02:49
*** crc32 has joined #openstack-meeting02:49
*** novas0x2a|laptop has quit IRC02:49
*** ivar-lazzaro has joined #openstack-meeting02:49
*** s3wong has quit IRC02:53
*** dane_leblanc has quit IRC02:57
*** eghobo has quit IRC02:59
*** ndipanov_gone has quit IRC03:01
*** Murali has joined #openstack-meeting03:02
*** Longgeek has quit IRC03:02
*** vivek-eb_ has joined #openstack-meeting03:04
*** vivek-ebay has quit IRC03:05
*** zehicle_ has joined #openstack-meeting03:05
*** dane_leblanc has joined #openstack-meeting03:05
*** ijw has quit IRC03:07
*** bdpayne has joined #openstack-meeting03:07
*** ivar-lazzaro has quit IRC03:10
*** ivar-lazzaro has joined #openstack-meeting03:10
*** baoli has quit IRC03:11
*** jckasper has quit IRC03:15
*** Longgeek has joined #openstack-meeting03:15
*** unicell1 has quit IRC03:15
*** thangp has quit IRC03:16
*** VijayB has quit IRC03:16
*** iymht has quit IRC03:16
*** jehb has quit IRC03:19
*** jungleboyj has joined #openstack-meeting03:20
*** yamahata has quit IRC03:20
*** asettle is now known as asettle-lernch03:21
*** bdpayne has quit IRC03:21
*** ujuc has joined #openstack-meeting03:24
*** baoli has joined #openstack-meeting03:26
*** nellysmitt has joined #openstack-meeting03:26
*** jckasper has joined #openstack-meeting03:28
*** xuhanp has quit IRC03:29
*** nellysmitt has quit IRC03:31
*** vozcelik has joined #openstack-meeting03:31
*** nelsnelson has joined #openstack-meeting03:33
*** vozcelik has quit IRC03:34
*** dmellado_ has joined #openstack-meeting03:36
*** zehicle_ has quit IRC03:36
*** Murali has quit IRC03:36
*** dmellado has quit IRC03:37
*** dmellado_ is now known as dmellado03:37
*** asettle-lernch is now known as asettle03:39
*** unicell has joined #openstack-meeting03:45
*** dimsum__ has quit IRC03:45
*** ddieterl_ has quit IRC03:48
*** ivar-lazzaro has quit IRC03:49
*** ayoung has quit IRC03:50
*** Apoorva has quit IRC03:54
*** jpeeler has quit IRC04:01
*** amotoki has quit IRC04:02
*** antoniom has quit IRC04:03
*** JRobinson__ is now known as JRobinson__afk04:06
*** Longgeek has quit IRC04:06
*** yamamoto has quit IRC04:07
*** yamamoto has joined #openstack-meeting04:08
*** thedodd has joined #openstack-meeting04:08
*** harlowja_ is now known as harlowja_away04:13
*** jamespage has quit IRC04:14
*** jamespage has joined #openstack-meeting04:14
*** killer_prince has joined #openstack-meeting04:18
*** killer_prince is now known as lazy_prince04:18
*** Longgeek has joined #openstack-meeting04:18
*** tomoe__ has quit IRC04:19
*** armax has joined #openstack-meeting04:21
*** crc32 has quit IRC04:22
*** dmacpher-afk has quit IRC04:26
*** tiswanso has quit IRC04:28
*** JRobinson__afk is now known as JRobinson__04:29
*** coolsvap_ is now known as coolsvap04:37
*** thumpba has joined #openstack-meeting04:41
*** armax has quit IRC04:45
*** dimsum__ has joined #openstack-meeting04:46
*** nelsnelson has quit IRC04:47
*** armax has joined #openstack-meeting04:47
*** oomichi_ has joined #openstack-meeting04:48
*** fnaval has quit IRC04:48
*** ddieterly has joined #openstack-meeting04:48
*** dimsum__ has quit IRC04:51
*** ddieterly has quit IRC04:53
*** neeti has joined #openstack-meeting04:54
*** comay has quit IRC04:55
*** epico has quit IRC04:56
*** sandywalsh_ has quit IRC04:56
*** epico has joined #openstack-meeting04:57
*** sandywalsh has joined #openstack-meeting04:58
*** Riddhi has quit IRC04:58
*** Riddhi has joined #openstack-meeting04:59
*** markvoelker has quit IRC04:59
*** markvoelker has joined #openstack-meeting05:00
*** armax has quit IRC05:00
*** sbalukoff has joined #openstack-meeting05:03
*** tomoe_ has joined #openstack-meeting05:03
*** markvoelker has quit IRC05:04
*** david-lyle_afk has joined #openstack-meeting05:06
*** pradipta has joined #openstack-meeting05:06
*** Mandell has joined #openstack-meeting05:06
*** baoli has quit IRC05:06
*** jhenner has joined #openstack-meeting05:06
*** jckasper has quit IRC05:08
*** ajayaa has joined #openstack-meeting05:08
*** neeti_ has joined #openstack-meeting05:09
*** garyh has quit IRC05:09
*** Murali has joined #openstack-meeting05:11
*** neeti has quit IRC05:12
*** jhenner has quit IRC05:13
*** neillc is now known as neillc_uni05:16
*** Riddhi_ has joined #openstack-meeting05:17
*** jhenner has joined #openstack-meeting05:17
*** Riddhi has quit IRC05:18
*** akuznetsov has joined #openstack-meeting05:19
*** Murali has quit IRC05:21
*** jhenner has quit IRC05:23
*** nellysmitt has joined #openstack-meeting05:27
*** lazy_prince has quit IRC05:28
*** killer_prince has joined #openstack-meeting05:29
*** killer_prince is now known as lazy_prince05:29
*** fnaval has joined #openstack-meeting05:30
*** markvoelker has joined #openstack-meeting05:30
*** nellysmitt has quit IRC05:31
*** aranjan has joined #openstack-meeting05:34
*** thedodd has quit IRC05:34
*** markvoelker has quit IRC05:35
*** thedodd has joined #openstack-meeting05:37
*** mrmartin has joined #openstack-meeting05:39
*** jecarey has quit IRC05:39
*** eghobo has joined #openstack-meeting05:39
*** eghobo has quit IRC05:40
*** eghobo has joined #openstack-meeting05:41
*** anish_ has joined #openstack-meeting05:42
*** comay has joined #openstack-meeting05:43
*** david-lyle_afk has quit IRC05:44
*** pradipta has quit IRC05:45
*** hrao has joined #openstack-meeting05:47
*** zehicle has quit IRC05:47
*** cdub has quit IRC05:48
*** yatin has joined #openstack-meeting05:49
*** ddieterly has joined #openstack-meeting05:49
*** JRobinson__ has quit IRC05:51
*** vivek-eb_ has quit IRC05:51
*** ddieterly has quit IRC05:55
*** Sukhdev has joined #openstack-meeting05:56
*** otter768 has quit IRC05:56
*** unicell has quit IRC05:57
*** unicell1 has joined #openstack-meeting05:57
*** esker has joined #openstack-meeting06:01
*** zehicle has joined #openstack-meeting06:01
*** resker has quit IRC06:01
*** iymht has joined #openstack-meeting06:05
*** Riddhi_ has quit IRC06:05
*** xyang1 has quit IRC06:06
*** ildikov has quit IRC06:07
*** BharatK has joined #openstack-meeting06:09
*** adahms has quit IRC06:09
*** killer_prince has joined #openstack-meeting06:10
*** lazy_prince has quit IRC06:10
*** killer_prince is now known as lazy_prince06:10
*** chandankumar has joined #openstack-meeting06:14
*** achanda has joined #openstack-meeting06:14
*** shankarprasad has joined #openstack-meeting06:19
*** adahms has joined #openstack-meeting06:19
*** eharney has quit IRC06:19
*** eharney has joined #openstack-meeting06:20
*** eghobo has quit IRC06:20
*** redrobot has quit IRC06:21
*** gyee has quit IRC06:22
*** aranjan has quit IRC06:23
*** tr3buchet1 has quit IRC06:23
*** redrobot has joined #openstack-meeting06:25
*** redrobot is now known as Guest3254406:25
*** thedodd has quit IRC06:31
*** markvoelker has joined #openstack-meeting06:31
*** eghobo has joined #openstack-meeting06:32
*** jhenner has joined #openstack-meeting06:32
*** jhenner has quit IRC06:32
*** fungi has quit IRC06:34
*** russellb has quit IRC06:34
*** SridharG has joined #openstack-meeting06:34
*** markvoelker has quit IRC06:36
*** pnavarro has joined #openstack-meeting06:38
*** russell_h has quit IRC06:38
*** ildikov has joined #openstack-meeting06:40
*** anish__ has joined #openstack-meeting06:41
*** nellysmitt has joined #openstack-meeting06:42
*** anish_ has quit IRC06:44
*** david-lyle_afk has joined #openstack-meeting06:44
*** ivar-lazzaro has joined #openstack-meeting06:47
*** thumpba_ has joined #openstack-meeting06:48
*** jroll has quit IRC06:49
*** ddieterly has joined #openstack-meeting06:50
*** thumpba has quit IRC06:52
*** thumpba_ has quit IRC06:52
*** pnavarro has quit IRC06:53
*** ddieterly has quit IRC06:55
*** xuhanp has joined #openstack-meeting06:58
*** reed has quit IRC06:58
*** jroll has joined #openstack-meeting06:59
*** ivar-lazzaro has quit IRC07:00
*** ivar-lazzaro has joined #openstack-meeting07:01
*** adahms has quit IRC07:01
*** mrda is now known as mrda-away07:04
*** dulek has joined #openstack-meeting07:04
*** jtomasek has joined #openstack-meeting07:06
*** ibiris_away is now known as ibiris07:11
*** rajeshr has joined #openstack-meeting07:18
*** oomichi_ has quit IRC07:18
*** aranjan has joined #openstack-meeting07:20
*** irenab has joined #openstack-meeting07:21
*** yamahata has joined #openstack-meeting07:21
*** sergef has joined #openstack-meeting07:24
*** yamamoto has quit IRC07:24
*** aranjan has quit IRC07:25
*** Murali has joined #openstack-meeting07:26
*** fnaval has quit IRC07:26
*** scheuran has joined #openstack-meeting07:26
*** mrunge has joined #openstack-meeting07:27
*** cdub has joined #openstack-meeting07:28
*** markvoelker has joined #openstack-meeting07:32
*** VW_ has quit IRC07:33
*** VW_ has joined #openstack-meeting07:33
*** VW_ has quit IRC07:35
*** ndipanov_gone has joined #openstack-meeting07:35
*** VW_ has joined #openstack-meeting07:35
*** hrao has quit IRC07:36
*** markvoelker has quit IRC07:37
*** akuznetsov has quit IRC07:38
*** yatin has quit IRC07:40
*** hrao has joined #openstack-meeting07:41
*** luis_fdez1 has joined #openstack-meeting07:41
*** yatin has joined #openstack-meeting07:42
*** luis_fdez has quit IRC07:43
*** Sukhdev has quit IRC07:45
*** ajo has quit IRC07:48
*** VW_ has quit IRC07:48
*** VW_ has joined #openstack-meeting07:49
*** ddieterly has joined #openstack-meeting07:51
*** yatin has quit IRC07:52
*** yatin has joined #openstack-meeting07:53
*** VW_ has quit IRC07:53
*** zhhuabj has quit IRC07:53
*** VW_ has joined #openstack-meeting07:54
*** ddieterly has quit IRC07:56
*** otter768 has joined #openstack-meeting07:57
*** ajo has joined #openstack-meeting07:57
*** krtaylor has quit IRC07:58
*** eharney has quit IRC07:58
*** ndipanov_gone has quit IRC07:59
*** zhhuabj has joined #openstack-meeting07:59
*** armax has joined #openstack-meeting07:59
*** VW_ has quit IRC08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Mar  3 08:00:58 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:01
*** openstack changes topic to " (Meeting topic: third-party)"08:01
openstackThe meeting name has been set to 'third_party'08:01
*** VW_ has joined #openstack-meeting08:01
anteayasay hello if you are here for the third-party meeting08:01
*** otter768 has quit IRC08:01
*** VW_ has quit IRC08:03
*** VW_ has joined #openstack-meeting08:04
*** fzdarsky has joined #openstack-meeting08:05
*** sahid has joined #openstack-meeting08:05
*** nshaikh has joined #openstack-meeting08:06
*** nikhil has quit IRC08:07
*** jcoufal has joined #openstack-meeting08:07
*** krtaylor has joined #openstack-meeting08:08
*** VW_ has quit IRC08:09
*** eharney has joined #openstack-meeting08:09
*** VW_ has joined #openstack-meeting08:09
*** VW_ has quit IRC08:11
*** lennyb has joined #openstack-meeting08:11
*** VW_ has joined #openstack-meeting08:11
*** armax has quit IRC08:12
*** JRobinson__ has joined #openstack-meeting08:14
*** stevemar has quit IRC08:15
*** lsmola has joined #openstack-meeting08:16
*** ajo has quit IRC08:17
*** hareeshp has joined #openstack-meeting08:18
*** VW_ has quit IRC08:19
*** matrohon has joined #openstack-meeting08:19
*** VW_ has joined #openstack-meeting08:19
*** mtanino has joined #openstack-meeting08:21
*** aranjan has joined #openstack-meeting08:21
*** numan has joined #openstack-meeting08:22
*** hrao has quit IRC08:23
*** hareeshp has quit IRC08:23
*** dimsum__ has joined #openstack-meeting08:24
*** mtanino has quit IRC08:26
*** yatin has quit IRC08:26
*** sigmavirus24_awa has quit IRC08:26
*** e0ne has joined #openstack-meeting08:26
*** chandankumar has quit IRC08:26
*** dolphm has quit IRC08:27
*** d34dh0r53 has quit IRC08:27
*** akuznetsov has joined #openstack-meeting08:27
*** dimsum__ has quit IRC08:29
*** VW_ has quit IRC08:30
*** VW_ has joined #openstack-meeting08:30
*** ItSANgo has quit IRC08:30
*** d34dh0r53 has joined #openstack-meeting08:30
*** ItSANgo has joined #openstack-meeting08:31
*** ItSANgo has quit IRC08:31
*** 5EXAAM0AM has joined #openstack-meeting08:31
*** dolphm has joined #openstack-meeting08:31
*** chandankumar has joined #openstack-meeting08:32
*** pnavarro has joined #openstack-meeting08:32
*** markvoelker has joined #openstack-meeting08:33
*** zhhuabj has quit IRC08:33
*** e0ne has quit IRC08:34
*** VW_ has quit IRC08:35
*** claudiub has joined #openstack-meeting08:35
*** VW_ has joined #openstack-meeting08:35
*** zhhuabj has joined #openstack-meeting08:36
*** MaxV has joined #openstack-meeting08:36
*** evgenyf has joined #openstack-meeting08:37
*** eghobo has quit IRC08:38
*** dulek has quit IRC08:38
*** neillc_uni is now known as neillc08:39
*** markvoelker has quit IRC08:39
*** e0ne has joined #openstack-meeting08:39
*** dulek has joined #openstack-meeting08:39
*** watanabe_isao has quit IRC08:39
*** MaxV has quit IRC08:41
*** epico has quit IRC08:42
*** BrianShang has joined #openstack-meeting08:44
*** yatin has joined #openstack-meeting08:44
*** jlanoux has joined #openstack-meeting08:45
*** Mandell has quit IRC08:45
*** hareeshp has joined #openstack-meeting08:48
*** vivek-ebay has joined #openstack-meeting08:48
*** ajo has joined #openstack-meeting08:49
*** epico has joined #openstack-meeting08:50
*** MaxV has joined #openstack-meeting08:50
*** mpaolino has joined #openstack-meeting08:50
*** dulek_ has joined #openstack-meeting08:50
*** ddieterly has joined #openstack-meeting08:52
*** vivek-ebay has quit IRC08:53
*** dulek has quit IRC08:53
*** achanda has quit IRC08:55
*** mpaolino has quit IRC08:55
*** mpaolino has joined #openstack-meeting08:55
*** aranjan has quit IRC08:55
*** ddieterly has quit IRC08:56
*** jjmb 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 Mar  3 08:58:38 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-03-03-08.00.html08:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-03-03-08.00.txt08:58
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-03-03-08.00.log.html08:58
*** e0ne is now known as e0ne_08:59
*** ygbo has joined #openstack-meeting08:59
*** dulek_ has quit IRC09:00
anteaya#startmeeting nova-net-to-neutron-migration09:00
openstackMeeting started Tue Mar  3 09:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.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
obondarevhi09:00
anteayahello09:00
anteayahow are you oleg?09:00
anteayagus are you around?09:00
anteayamikal ping09:00
obondarevI'm great! Thank you :)09:00
*** ivar-lazzaro has quit IRC09:00
anteayaI don't see belmoria in channel09:00
anteayaobondarev: glad to hear it09:00
anteayamight just be you and I09:00
*** VW_ has quit IRC09:01
*** ivar-lazzaro has joined #openstack-meeting09:01
obondarevanteaya: I see09:01
anteayashall we get started?09:01
*** VW_ has joined #openstack-meeting09:01
obondarevanteaya: is there some conference or smth?09: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
*** e0ne_ is now known as e0ne09:01
obondarevanteaya: sure we can09:01
*** JRobinson__ has quit IRC09:01
*** jjmb has quit IRC09:01
anteayaobondarev: no I think we are just close to feature freeze for kilo09:01
anteayaso folks are otherwise occupied09:02
anteayait will pick up again09:02
mikalHi09:02
anteayaso any change on spec status this week?09:02
anteayamikal: you are here09:02
obondarevok, I see09:02
anteayayay09:02
obondarevno updates on the specs side again09:02
anteayamoving on09:02
obondarevso probably we should move to implementation topic09: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
anteayago ahead09:02
obondarevI tested jlibosva's db migration patch a little bit on devstack09:02
obondarevit seems working fine for flat (and flatdhcp, no floating ips) for my really simple data09:03
anteayawonderful09:03
anteayaterrific09:03
obondarevthere is a couple of nits which I'll comment on review09:03
anteayawould you be able to make a comment on the patch stating under what conditions it worked for you?09:03
anteayaand yes, thank you09:03
obondarevanteaya: sure09:03
obondarevwill comment that09:03
*** dulek has joined #openstack-meeting09:03
obondarevfor nova-net proxy I've uploaded new patch set last week09:04
*** dulek has quit IRC09:04
obondarevso in its current state it should allow to handle allocate/deallocate_for_instance in proxy mode09:04
anteayaI see that thank you09:04
anteayaso far no reviews09:04
anteayawere you able to read the logs from the last nova meeting?09:04
obondarevI think I red09:05
anteayaso you caught that dan smith is still not sold that this is the best direction?09:05
obondarev*read09:05
obondarevyeah09:05
*** iymht has quit IRC09:05
anteayaokay09:05
*** akuznetsov has quit IRC09:05
*** lifeless has quit IRC09:05
obondarevI know he thinks that the best is to not do it at all09:05
anteayanot to do a proxy at all?09:06
*** mpaolino has quit IRC09:06
obondarevyes09:06
*** lifeless has joined #openstack-meeting09:06
anteayawhat do you think he would support as a direction?09:06
*** mpaolino has joined #openstack-meeting09:06
*** aepifanov has joined #openstack-meeting09:06
*** andreykurilin_ has joined #openstack-meeting09:06
*** e0ne is now known as e0ne_09:06
obondarevI don't know09:06
anteayamikal: any insight here?09:06
*** JoshNang has quit IRC09:07
*** VW_ has quit IRC09:07
anteayawhat do you think dan and nova would support as a direction, since we don't seem to be getting support for a proxy09:07
mikalSo the short answer is I am not sure09:07
mikalI need ti sit down and tlak with Dan about it more09:07
mikalBut I haven't found the time for that09:08
*** VW_ has joined #openstack-meeting09:08
obondarevI feel Dan's main concern is that with the proposed approach we'll not be able to handle complex cases09:08
mikalI accept this is a thing I need to find time for though09:08
obondarevcurrently I'm debugging proxy on devstack, found several issues there09:08
obondarevgoing to fix them and upload a working version09:08
obondarevtoday or tomorrow09:08
anteayaokay so if we don't have support for the current direction, then perhaps we can work on finding support for some direction to be determined09:09
anteayayes?09:09
*** e0ne_ is now known as e0ne09:09
obondarevI guess so09:09
mikalanteaya: remind me of the review number for the nova proxy?09:10
obondarevotherwise I don't know what's the way forward09:10
anteayasorry09:10
anteaya#link https://review.openstack.org/#/c/150490/09:10
anteayaproxy09:10
mikalTa09:10
anteaya#link https://review.openstack.org/#/c/148260/09:10
anteayadb migration09:10
anteayathanks for asking09:10
obondarevI'll also add a comment with an instruction on how it can be tested together with db migration patch09:10
obondarevwith what to do and what to expect09:10
obondarevhope this will be enough to prove that the approach does its job09:11
mikalSo, re-reading that Dan'09:11
mikals concern is quite specific09:11
mikalHe doesn't want to fake out the sqlalchemy layer09:11
mikal"I feel like doing this at the nova/network/base_api.py layer is the proper place, probably subclassing the nova-net one and re-using a lot of what is there. I guess that I don't believe that just replacing the persistence layer is going to be enough to cover more than just the most simple of cases."09:11
obondarevyeah09:12
*** andreykurilin_ has quit IRC09:12
obondarevthat's why I prefer that all the discussion should happen on the review09:12
mikalBut yeah, let me chat with Dan and let you know what I can find out from a high bandwidth conversation next week09:12
obondarevwe discussed that with Dan on irc09:12
*** andreykurilin_ has joined #openstack-meeting09:12
mikalOh, ok09:12
mikalWhere did that end up?09:12
*** yamahata has quit IRC09:13
obondarevso he said he can't come up with a better approach09:13
obondarevrather that don't do it09:13
obondarevin my comments I tried to explain why proxying at api layer is not simpler and clearer09:14
mikalBut what about the base_api comment09:14
mikalIs that his proposed better approach?09:14
*** ivar-lazzaro has quit IRC09:14
obondarevthat was before our conversation09:15
*** e0ne has quit IRC09:15
*** enterprisedc has quit IRC09:15
obondarevprobably I convinced him09:15
obondarevnot sure however09:15
mikalOk09:15
anteayaobondarev: you didn't convince him09:15
mikalLike I said, let me chat to him and see what I can learn09:15
anteayasince his feeling at the nova meeting remained the same09:16
obondarevbut he seem not advocating api approach any more09:16
obondarevanteaya: from what I saw his only suggestion was not do it09:17
anteayaright09:17
anteayawhich means we need to find out what to do09:17
obondarevanteaya: he didn't mention any other approach, did he?09:17
mikalSo, I think we should table this until I can chat with Dan09:17
mikalWe seem to now be trying to guess what he thinks09:17
*** jyuso1 has quit IRC09:17
anteayaI didn't ask, since i knew you wanted to keep working on the proxy09:17
mikalWhich seems unproductive09:17
anteayamikal: good point09:17
obondarevanteaya: tha't why I thought I probably convinced him that api approach isn't better09:18
anteayamoving on09:18
anteayayou didn't09:18
anteaya#topic documentation09:18
*** openstack changes topic to "documentation (Meeting topic: nova-net-to-neutron-migration)"09:18
anteayaso nothing new here09:18
anteayawe have a patch up to docs but it is on hold while they go from xml to rst09:19
anteaya#topic testing09:19
*** openstack changes topic to "testing (Meeting topic: nova-net-to-neutron-migration)"09:19
anteayaso we have the db migration if anyone wants to test it09:19
anteayaanything more in testing?09:19
anteayaokay moving on09:20
anteaya#topic open discussion09:20
*** openstack changes topic to "open discussion (Meeting topic: nova-net-to-neutron-migration)"09:20
*** enterprisedc has joined #openstack-meeting09:21
anteayaanyone have anything here?09:21
anteayaokay let's call it then09:21
anteayaobondarev mikal thanks for your attendance, I'm grateful09:21
anteayamikal: have fun tomorrow on your visit to the salt mines09:21
obondarevanteaya: thank you for organizing09:21
anteayasure09:21
anteayaI look forward to seeing where we are next week09:21
* gus shuffles in quietly and hopes no-one notices his tardiness...09:22
anteayahopefully we can have some directional guidance09:22
anteayagus: hi09:22
anteayawe are just finished09:22
mikalanteaya: thanks!09:22
anteayagus: do you have anything you wish to add before we close out?09:22
mikalgus: well timed!09:22
gusheh, no I have nothing to add this week either.09:22
anteayaokay thanks09:23
anteayahave a good rest of time of day to you09:23
anteayasee you next week09:23
anteaya#endmeeting09:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:23
openstackMeeting ended Tue Mar  3 09:23:18 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-03-03-09.00.html09:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-03-03-09.00.txt09:23
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-03-03-09.00.log.html09:23
*** enterprisedc has quit IRC09:25
*** andreykurilin_ has quit IRC09:26
*** enterprisedc has joined #openstack-meeting09:26
*** andreykurilin_ has joined #openstack-meeting09:27
*** ibiris is now known as ibiris_away09:27
*** hareeshp has quit IRC09:27
*** pdb has joined #openstack-meeting09:27
*** safchain has joined #openstack-meeting09:28
*** yatin has quit IRC09:28
*** enterprisedc has quit IRC09:32
*** oanufriev has joined #openstack-meeting09:33
*** VW__ has joined #openstack-meeting09:33
*** zhhuabj has quit IRC09:34
*** markvoelker has joined #openstack-meeting09:35
*** ibiris_away is now known as ibiris09:36
*** mpaolino has quit IRC09:37
*** VW_ has quit IRC09:37
*** mpaolino has joined #openstack-meeting09:38
*** che-arne has joined #openstack-meeting09:38
*** VW__ has quit IRC09:38
*** claudiub has quit IRC09:38
*** ajayaa has quit IRC09:38
*** markvoelker has quit IRC09:39
*** ajayaa has joined #openstack-meeting09:40
*** mpaolino has quit IRC09:40
*** mpaolino has joined #openstack-meeting09:40
*** claudiub has joined #openstack-meeting09:45
*** shankarprasad has quit IRC09:46
*** mpaolino has quit IRC09:48
*** mpaolino has joined #openstack-meeting09:48
*** ajayaa has quit IRC09:50
*** coolsvap is now known as coolsvap_09:52
*** aranjan has joined #openstack-meeting09:52
*** yatin has joined #openstack-meeting09:53
*** ddieterly has joined #openstack-meeting09:53
*** tomoe_ has quit IRC09:56
*** dzimine has quit IRC09:57
*** ddieterly has quit IRC09:57
*** otter768 has joined #openstack-meeting09:58
*** Longgeek has quit IRC10:01
*** otter768 has quit IRC10:02
*** hareeshp has joined #openstack-meeting10:05
*** afazekas has joined #openstack-meeting10:05
*** cdub has quit IRC10:07
*** cdub has joined #openstack-meeting10:08
*** ajayaa has joined #openstack-meeting10:09
*** cdub has quit IRC10:12
*** mpaolino has quit IRC10:16
*** jyuso1 has joined #openstack-meeting10:16
*** mpaolino has joined #openstack-meeting10:16
*** ajo has quit IRC10:19
*** ajo has joined #openstack-meeting10:19
*** dguitarbite has quit IRC10:26
*** aranjan has quit IRC10:26
*** mpaolino has quit IRC10:30
*** mpaolino has joined #openstack-meeting10:30
*** ajo has quit IRC10:30
*** chandankumar_ has joined #openstack-meeting10:30
*** ajo has joined #openstack-meeting10:31
*** chandankumar has quit IRC10:33
*** amotoki has joined #openstack-meeting10:34
*** hareeshp has quit IRC10:34
*** dguitarbite has joined #openstack-meeting10:34
*** dguitarbite has joined #openstack-meeting10:34
*** markvoelker has joined #openstack-meeting10:35
*** jyuso1 has quit IRC10:36
*** hareeshp has joined #openstack-meeting10:36
*** Murali_ has joined #openstack-meeting10:37
*** Murali has quit IRC10:38
*** Murali_ is now known as Murali10:38
*** markvoelker has quit IRC10:40
*** Longgeek has joined #openstack-meeting10:41
*** e0ne has joined #openstack-meeting10:43
*** Longgeek has quit IRC10:43
*** Longgeek has joined #openstack-meeting10:44
*** matrohon has quit IRC10:44
*** andreykurilin_ has quit IRC10:46
*** tochi has quit IRC10:47
*** mpaolino has quit IRC10:47
*** mpaolino has joined #openstack-meeting10:47
*** scheuran_ has joined #openstack-meeting10:49
*** scheuran has quit IRC10:52
*** mpaolino has quit IRC10:52
*** epico has quit IRC10:52
*** mpaolino has joined #openstack-meeting10:53
*** ddieterly has joined #openstack-meeting10:53
*** mpaolino has quit IRC10:57
*** mpaolino has joined #openstack-meeting10:58
*** ddieterly has quit IRC10:58
*** BobBall_AWOL is now known as BobBall11:00
*** yatin has quit IRC11:02
*** pelix has joined #openstack-meeting11:03
*** e0ne is now known as e0ne_11:09
*** xuhanp has quit IRC11:14
*** yatin has joined #openstack-meeting11:16
*** dimsum__ has joined #openstack-meeting11:16
*** coolsvap_ is now known as coolsvap11:17
*** flwang has quit IRC11:18
*** e0ne_ has quit IRC11:20
*** ajayaa has quit IRC11:20
*** irenab has quit IRC11:20
*** e0ne has joined #openstack-meeting11:21
*** hareeshp has quit IRC11:21
*** aranjan has joined #openstack-meeting11:22
*** kairat_kushaev has quit IRC11:26
*** flwang has joined #openstack-meeting11:28
*** jlanoux_ has joined #openstack-meeting11:30
*** mpaolino has quit IRC11:30
*** mpaolino has joined #openstack-meeting11:31
*** ajayaa has joined #openstack-meeting11:31
*** mpaolino has quit IRC11:33
*** jlanoux has quit IRC11:33
*** mpaolino has joined #openstack-meeting11:33
*** markvoelker has joined #openstack-meeting11:36
*** yatin has quit IRC11:38
*** mpaolino has quit IRC11:40
*** mpaolino has joined #openstack-meeting11:40
*** markvoelker has quit IRC11:41
*** jhenner has joined #openstack-meeting11:44
*** jlanoux has joined #openstack-meeting11:49
*** cdub has joined #openstack-meeting11:50
*** jlanoux_ has quit IRC11:52
*** kairat_kushaev has joined #openstack-meeting11:52
*** ajayaa has quit IRC11:53
*** e0ne is now known as e0ne_11:53
*** ddieterly has joined #openstack-meeting11:54
*** hareeshp has joined #openstack-meeting11:57
*** aranjan has quit IRC11:57
*** Longgeek has quit IRC11:58
*** ddieterly has quit IRC11:58
*** otter768 has joined #openstack-meeting11:59
*** e0ne_ is now known as e0ne12:01
*** otter768 has quit IRC12:03
*** BharatK has quit IRC12:03
*** IanGovett has joined #openstack-meeting12:04
*** cdub has quit IRC12:04
*** EmilienM|afk is now known as EmilienM12:05
*** evgenyf has quit IRC12:06
*** prazumovsky has joined #openstack-meeting12:06
*** yatin has joined #openstack-meeting12:06
*** killer_prince has joined #openstack-meeting12:06
*** wojdev has joined #openstack-meeting12:07
*** lazy_prince has quit IRC12:07
*** killer_prince is now known as lazy_prince12:07
*** russellb has joined #openstack-meeting12:08
*** rajeshr has quit IRC12:08
*** baoli has joined #openstack-meeting12:10
*** evgenyf has joined #openstack-meeting12:11
*** yamamoto has joined #openstack-meeting12:12
*** wojdev has quit IRC12:18
*** adalbas has joined #openstack-meeting12:19
*** wojdev has joined #openstack-meeting12:19
*** mpaolino has quit IRC12:19
*** mpaolino has joined #openstack-meeting12:20
*** irenab has joined #openstack-meeting12:22
*** mpaolino has quit IRC12:23
*** mpaolino has joined #openstack-meeting12:23
*** ChrisPriceAB has joined #openstack-meeting12:24
*** rfolco has joined #openstack-meeting12:25
*** yamamoto has quit IRC12:26
*** weshay has joined #openstack-meeting12:30
*** amakarov_away is now known as amakarov12:31
*** IanGovett has quit IRC12:34
*** aysyd has joined #openstack-meeting12:35
*** spredzy is now known as spredzyafk12:36
*** tomoe_ has joined #openstack-meeting12:37
*** markvoelker has joined #openstack-meeting12:38
*** yatin has quit IRC12:39
*** dmacpher has joined #openstack-meeting12:40
*** IanGovett has joined #openstack-meeting12:41
*** baoli has quit IRC12:42
*** markvoelker has quit IRC12:42
*** baoli has joined #openstack-meeting12:43
*** Longgeek has joined #openstack-meeting12:43
*** dimsum__ is now known as dims12:46
*** yassine has joined #openstack-meeting12:47
*** Mandell has joined #openstack-meeting12:47
*** jang1 has quit IRC12:48
*** jang has joined #openstack-meeting12:49
*** GeraldK has joined #openstack-meeting12:50
*** _nadya_ has joined #openstack-meeting12:50
*** Mandell has quit IRC12:51
*** BharatK has joined #openstack-meeting12:53
*** aranjan has joined #openstack-meeting12:53
*** esker has quit IRC12:53
*** ddieterly has joined #openstack-meeting12:55
*** yatin has joined #openstack-meeting12:57
*** AmirBaleghi13 has joined #openstack-meeting12:57
*** ddieterly has quit IRC12:59
*** dane_leblanc has quit IRC12:59
*** GeraldK has quit IRC13:01
*** Gerald_K has joined #openstack-meeting13:01
*** yamamoto has joined #openstack-meeting13:02
*** tongli has joined #openstack-meeting13:03
*** markvoelker has joined #openstack-meeting13:04
*** hareeshp has quit IRC13:05
*** yamamoto_ has joined #openstack-meeting13:06
*** mpaolino has quit IRC13:06
*** jroll has quit IRC13:07
*** jroll has joined #openstack-meeting13:07
*** mpaolino has joined #openstack-meeting13:07
*** yamamoto has quit IRC13:09
*** stefan_amann has joined #openstack-meeting13:14
*** dims has quit IRC13:14
*** dims has joined #openstack-meeting13:15
*** spredzyafk is now known as spredzy13:15
*** numan has quit IRC13:18
*** mwagner_lap has quit IRC13:19
*** sarob has quit IRC13:20
*** sarob has joined #openstack-meeting13:21
*** doude has joined #openstack-meeting13:21
*** sarob has quit IRC13:26
*** dprince has joined #openstack-meeting13:26
*** bobmel has quit IRC13:27
*** aranjan has quit IRC13:27
*** bobmel has joined #openstack-meeting13:28
*** banix has joined #openstack-meeting13:32
*** banix has quit IRC13:34
*** dkranz has quit IRC13:37
*** dneary has joined #openstack-meeting13:37
*** dane_leblanc has joined #openstack-meeting13:38
*** ddieterly has joined #openstack-meeting13:38
*** banix has joined #openstack-meeting13:39
*** mpaolino has quit IRC13:44
*** mpaolino has joined #openstack-meeting13:45
*** fawadkhaliq has joined #openstack-meeting13:46
*** nshaikh has quit IRC13:49
*** jprovazn has joined #openstack-meeting13:49
*** wojdev has quit IRC13:53
*** sankarshan_away is now known as sankarshan13:54
*** jehb has joined #openstack-meeting13:54
*** FJB has joined #openstack-meeting13:55
*** absubram has joined #openstack-meeting13:55
*** akuznetsov has joined #openstack-meeting13:55
*** radez_g0n3 is now known as radez13:57
*** hareeshp has joined #openstack-meeting13:58
*** mpaolino has quit IRC13:59
*** mpaolino has joined #openstack-meeting13:59
*** otter768 has joined #openstack-meeting13:59
*** bill_az has joined #openstack-meeting14:00
*** sreshetnyak has joined #openstack-meeting14:00
*** yamamoto_ has quit IRC14:01
*** yamamoto has joined #openstack-meeting14:02
*** yamamoto has quit IRC14:02
*** julim has joined #openstack-meeting14:03
*** esker has joined #openstack-meeting14:03
*** asettle has quit IRC14:03
*** wojdev has joined #openstack-meeting14:03
*** changbl has quit IRC14:04
*** otter768 has quit IRC14:04
*** jjmb has joined #openstack-meeting14:04
*** ddieterly has quit IRC14:08
*** mwagner_lap has joined #openstack-meeting14:08
*** rprakash has joined #openstack-meeting14:08
*** sarob has joined #openstack-meeting14:09
*** jjmb has quit IRC14:10
*** adalbas has quit IRC14:12
*** neeti_ has quit IRC14:12
*** SridharG has left #openstack-meeting14:15
*** asettle has joined #openstack-meeting14:15
*** IanGovett has quit IRC14:17
*** neelashah has joined #openstack-meeting14:17
*** IanGovett has joined #openstack-meeting14:17
*** lazy_prince has quit IRC14:19
*** sergef has quit IRC14:20
*** wojdev has quit IRC14:20
*** zehicle_ has joined #openstack-meeting14:21
*** wojdev has joined #openstack-meeting14:21
*** yatin has quit IRC14:21
*** AlanClark has joined #openstack-meeting14:23
*** aranjan has joined #openstack-meeting14:23
*** killer_prince has joined #openstack-meeting14:24
*** killer_prince is now known as lazy_prince14:24
*** thangp has joined #openstack-meeting14:25
*** spzala has joined #openstack-meeting14:25
*** yamamoto has joined #openstack-meeting14:26
*** adalbas has joined #openstack-meeting14:26
*** absubram has quit IRC14:28
*** joesavak has joined #openstack-meeting14:28
*** eharney has quit IRC14:30
*** david-lyle has joined #openstack-meeting14:31
*** anish__ has quit IRC14:32
*** jungleboyj has quit IRC14:35
*** VW_ has joined #openstack-meeting14:35
*** tongli has quit IRC14:36
*** yamamoto has quit IRC14:36
*** ebalduf has joined #openstack-meeting14:36
*** gholler has joined #openstack-meeting14:36
*** banix has quit IRC14:36
*** ddieterly has joined #openstack-meeting14:37
*** banix has joined #openstack-meeting14:37
*** sarob_ has joined #openstack-meeting14:37
*** ndipanov has joined #openstack-meeting14:38
*** anish__ has joined #openstack-meeting14:38
*** sarob has quit IRC14:39
*** Mandell has joined #openstack-meeting14:40
*** Murali has quit IRC14:40
*** zz_jgrimm is now known as jgrimm14:43
*** salv-orlando has joined #openstack-meeting14:43
*** coolsvap is now known as coolsvap_14:43
*** ayoung has joined #openstack-meeting14:43
*** chandankumar_ has quit IRC14:43
*** ebalduf has quit IRC14:46
*** tiswanso has joined #openstack-meeting14:49
*** topol has joined #openstack-meeting14:50
*** fnaval has joined #openstack-meeting14:55
*** banix has quit IRC14:55
*** Mandell has quit IRC14:55
*** amitgandhinz has joined #openstack-meeting14:56
*** aranjan has quit IRC14:57
*** Riddhi has joined #openstack-meeting14:58
*** garyh has joined #openstack-meeting14:59
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Mar  3 15:00:35 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
bauzasclock ?15:00
*** che-arne has quit IRC15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
alex_xuo/15:00
bauzas\o15:00
edleafeo/15:00
*** SridharG has joined #openstack-meeting15:01
* n0ano notes that meetbot commands work better in a window running meetbot15:01
*** _nadya_ has quit IRC15:01
bauzassounds like we definitely lost jay because of his prom :)15:01
*** PaulMurray has joined #openstack-meeting15:01
n0anoanyway, edleafe congratulations on the spec, it's finally in15:01
edleafe\o/15:02
PaulMurrayo/15:02
*** jecarey has joined #openstack-meeting15:02
n0anoso, to business (hopefully short)15:02
n0ano#topic patch status15:02
*** openstack changes topic to "patch status (Meeting topic: gantt)"15:02
*** fawadkhaliq has quit IRC15:02
n0anoall the specs are approved so now we just have to implement them15:02
n0anoI guess I'll throw it open, anyone have any problems they need help with?15:03
*** yassine has quit IRC15:03
bauzasn0ano: we can circle on the blueprints15:03
edleafeI do15:03
n0anoedleafe, go ahead15:03
edleafeI'm getting strange RPC version mismatch from the ec2 tests15:03
bauzasbefore digging into details, we should just provide a quick reminder to all15:04
edleafeIf you see the Jenkins logs for py27 in https://review.openstack.org/#/c/160513/15:04
bauzasFeature Proposal Freeze is this Thursday 5th15:04
*** Riddhi has quit IRC15:04
*** eharney has joined #openstack-meeting15:04
bauzasso, no new patches unless exceptional circumstances15:04
bauzasthat said, now back to edleafe's problem15:05
*** xuhanp has joined #openstack-meeting15:05
edleafeI'm not sure why these tests are failing now15:05
*** Riddhi has joined #openstack-meeting15:05
* bauzas checking15:05
edleafeFrom what I've traced, it looks as though the compatibility check says that 3.x is not compatible with 4.015:05
edleafeIOW if the major version is newer, it assumes that the endpoint can't handle it15:06
edleafewhich makes no sense to me15:06
bauzasedleafe: I think that's probably a side-effect of your change15:06
edleafeespecially since the old version for scheduler was 4.0, and I bumped it to 4.115:06
n0anoedleafe, indeed, you would think that would be a greater than rather than an equal test15:07
*** wwallnrr__ has joined #openstack-meeting15:07
edleafebauzas: I don't see how I changed anything in the path for ec2's stop_instance calls15:07
bauzasedleafe: by reading the trace, I can see some path by the compute.api15:07
n0anoedleafe, did you change any common code15:07
edleafen0ano: not that I can see15:08
lxslioops o/15:08
*** Riddhi has quit IRC15:08
bauzasedleafe: I think that needs further verifications, have you tested on your local devstack ?15:08
*** vijendar has joined #openstack-meeting15:08
bauzasedleafe: because even Tempest is red15:09
* n0ano bauzas beats me again15:09
edleafebauzas: yes - it fails there too15:09
*** eharney has quit IRC15:09
edleafen0ano: the one thing is in compute.rpcapi.py15:09
edleafeI tried bumping the version there, and it just makes different ec2 tests fail15:09
edleafebut all due to incompatible versions15:10
*** rbak has joined #openstack-meeting15:10
n0anowell, if it's failing locally we have to fix that first15:10
bauzasedleafe: I seriously need to review your code before saying anything15:10
edleafebauzas: sure15:10
*** egallen has quit IRC15:10
bauzasedleafe: at least try to identify on your local machine15:10
edleafeI'm just wondering if there is any magic rpc version juju that I don't know about15:11
bauzasedleafe: well, see my patch about upgrading the RPC version if you need help15:11
*** rbak has quit IRC15:11
edleafebauzas: ok, will do15:11
*** esheffield has quit IRC15:11
alex_xuec2 unittest like a function..... running all the service...15:11
bauzasat the moment, the gate is in a pretty bad shape so I'm rechecking consistently but I'm sure about my code15:11
*** absubram has joined #openstack-meeting15:11
*** nelsnelson has joined #openstack-meeting15:12
bauzasalex_xu: you mean it's a functional test ? indeed15:12
*** thedodd has joined #openstack-meeting15:12
n0anobauzas, yeah, but if it's failing locally then the gate status doesn't really matter15:12
edleafen0ano: yeah, this isn't a gate issue15:12
*** nelsnelson has quit IRC15:12
alex_xubauzas: yea, I just found that, but I didn't find out anything can help edleafe15:12
*** ebalduf has joined #openstack-meeting15:13
*** rbak has joined #openstack-meeting15:13
*** sarob_ is now known as sarob15:13
bauzasn0ano: I was mentioning my own series which is done but has various -1s15:13
edleafeI was hoping that someone had a quick answer that could save me hours of searching15:13
bauzasbut agreed, let's fix first locally before sending it back to gerrit15:13
n0anobauzas, but yours passes locally I assume so it would be a good template15:13
bauzasedleafe: it does need hours of reviewing before giving a quick answer :)15:14
edleafebauzas: heh15:14
n0anoedleafe, looks like there's no magic bullet for this one15:14
edleafeI'll let everyone know what the problem was when I figure it out15:14
bauzasthe good news is that something so tomato red just means that you made a huge mistake15:14
n0anoedleafe, keep me posted, I'm free most of today so I'll look at this also15:14
bauzasand huge mistakes are the easiest to fix15:15
n0anobauzas, and more likely a single problem that impacts everything15:15
bauzasprobably15:15
n0anoOK, since we're all here, let's do a quick cycle through the specs15:16
edleafebauzas: yeah, it is something with the interaction between compute and scheduler RPC version numbers15:16
edleafegotta keep playing around with it15:16
bauzasedleafe: both are unrelateed15:16
n0anoPaulMurray, how's your resource tracker use objects coming?15:16
PaulMurraygreat15:16
bauzasedleafe: you can bump a version without touching the other15:16
PaulMurrayn0ano, I have one more patch to put up for compute nodes - just fixing some tests15:17
edleafebauzas: that's what I thought, but the ec2 tests started failing15:17
*** xuhanp has quit IRC15:17
*** prad has joined #openstack-meeting15:17
n0anoPaulMurray, cool, we'll mark you as green, let us know if you need any help15:17
PaulMurrayn0ano, I think there are one or two places where instances are still using conductor calls gut don't need to - so will sort that15:17
PaulMurrayn0ano, will do15:17
n0anoPaulMurray, great15:17
*** nelsnelson has joined #openstack-meeting15:18
n0anobauzas, next is detach service from compute node15:18
bauzasn0ano: I'm in15:18
bauzasn0ano: so basically, 95% of code is merged, only a few patches missing - basically about the service field on the DB side15:18
n0anobauzas, excellent, mark that as bright green15:19
bauzasso I'm still beating with last outstanding bugs but I have core reviewers support15:19
bauzasn0ano: yeah I'm considering this blueprint as done for Kilo, the rest can be done in Liberty15:19
edleafebauzas: anything we can do to help push it across the finish line?15:19
*** mattvd has left #openstack-meeting15:20
n0anojay doesn't appear to be on line, I'll manually go over his patch series after the meeting15:20
bauzasedleafe: not really, that's quite simple but I had to deal with side effects15:20
*** eghobo has joined #openstack-meeting15:20
n0anobauzas, next 2 are you, model request spec and cahnge select_destinations15:20
bauzasI'm planning to deliver a last iteration by today15:20
edleafebauzas: k15:20
*** eghobo has quit IRC15:21
bauzasn0ano: yeah, so let's consider these 2 specs are not targetable for Liberty15:21
bauzasn0ano: because even the spec was wrong - based on reviews15:21
*** eghobo has joined #openstack-meeting15:21
bauzasn0ano: so I'll focus on *one* spec (will merge both) by L-1 once the trunk opens15:22
bauzasthat should be quick15:22
*** bobmel_ has joined #openstack-meeting15:22
bauzastargeting this spec for L-1 as you understand15:22
n0anoI'm a little confused, even though they were accepted you're saying they are wrong?15:22
bauzasn0ano: right15:22
bauzasn0ano: ndipanov and I agreed on the fact it was better to add new RPC method instead of managing the hydradation on the same method, ie. select_dest()15:23
n0anobummer, I hope we don't have an infinite review process on them during Liberty15:23
*** Tross has quit IRC15:23
bauzasalso, the RequestSpec proposed object is probably wrong, we don't need all the Instance object15:24
bauzasn0ano: I don't think so, we had good feedback on Kilo for this spec15:24
bauzasn0ano: and as it was an approved spec, it will be short for L15:24
*** eharney has joined #openstack-meeting15:24
n0anoOK, my worry is will this cause issues with splitting out gantt15:25
*** msdubov_ has joined #openstack-meeting15:25
bauzasn0ano: I have a plan :)15:25
*** bobmel has quit IRC15:25
n0anowe're all listening15:25
bauzasn0ano: but that requires to be discussed on Vancouver15:25
*** alexpilotti has joined #openstack-meeting15:25
bauzasn0ano: I mean, we know that we have lots of things to do for splitting out Gantt, not only fixing tech deby15:26
bauzasn0ano: so I'm in favor of identifying the work for the migration path and do it for L15:26
*** ebalduf has quit IRC15:26
ndipanovbauzas, are we talking about request_spec object one?15:26
n0anoOK, maybe an outline in one of the future IRC meeings would be good so we have an idea of what you are thing of15:26
bauzasn0ano: I have ideas again, I need to drop them off15:26
bauzasndipanov: yup15:26
*** AmirBaleghi13 has quit IRC15:26
bauzasn0ano: sure, let's outline that next week - but ideally I would expose it once FF is there15:27
bauzasn0ano: because we don't exactly know what's missing15:27
bauzaslike the resource-objects BP is currently stale15:27
*** esheffield has joined #openstack-meeting15:27
*** mpaolino has quit IRC15:28
n0anoI don't want to put you on the spot right now but I don't want to hit everyone with new stuff at Vancouver so yeah, let's talk on this next week15:28
*** nelsnelson has quit IRC15:28
*** prazumovsky has quit IRC15:28
*** mpaolino has joined #openstack-meeting15:28
bauzasn0ano: agreed15:29
*** jungleboyj has joined #openstack-meeting15:29
*** wuhg has quit IRC15:29
n0anoI think that's everything for the current patches (mostly green except for those that aren't :-)15:29
bauzasnext BP ?15:29
bauzasn0ano: nope, you forgot one15:29
bauzasn0ano: and I have excellent news15:29
*** yassine has joined #openstack-meeting15:30
*** tiswanso has quit IRC15:30
bauzasso, bp/isolate-sched-db for aggregates is up for code-review15:30
bauzasfull completion of the spec, only waiting feedback15:30
n0anobauzas, that is good news, hopefully it'll merge soon15:30
bauzasn0ano: yeah, I was targeting to be uploading it before FPF15:31
bauzasit will become very hard to propose new patches by next week15:31
bauzasbtw. edleafe our patch about fixing the cast_as_call fixture got merged, you can rebase on top of master15:32
*** tiswanso has joined #openstack-meeting15:32
*** jhenner has quit IRC15:32
*** eghobo has quit IRC15:33
n0anoso, anything else on patches?15:33
bauzasfolks, think about updating the nova priorities etherpad if you want core support15:33
*** fawadkhaliq has joined #openstack-meeting15:33
*** fawadkhaliq has quit IRC15:34
n0anobauzas, good point although we can push at the nova IRC meeting also15:34
*** fawadkhaliq has joined #openstack-meeting15:34
n0anothen, moving on15:34
n0ano#topic opens15:34
*** openstack changes topic to "opens (Meeting topic: gantt)"15:34
edleafeoh, and the isloate-sched-db for instances is up for code review too15:34
*** dkranz has joined #openstack-meeting15:34
n0anoedleafe, excellent15:35
n0anoanyone have anything new for today?15:35
*** sigmavirus24 has joined #openstack-meeting15:35
* edleafe hears crickets15:35
*** wojdev has quit IRC15:35
* n0ano also15:36
n0anothen tnx everyone, we'll talk next week15:36
n0ano#endmeeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:36
openstackMeeting ended Tue Mar  3 15:36:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-03-15.00.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-03-15.00.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2015/gantt.2015-03-03-15.00.log.html15:36
alex_xuthanks all, see you15:36
bauzasthanks15:36
*** prometheanfire has left #openstack-meeting15:36
*** aepifanov has quit IRC15:37
*** annegentle has joined #openstack-meeting15:42
*** carl_baldwin has joined #openstack-meeting15:42
*** sahid has quit IRC15:43
*** mpaolino has quit IRC15:43
*** mpaolino has joined #openstack-meeting15:44
*** hemnafk is now known as hemna15:45
*** egallen has joined #openstack-meeting15:45
*** claudiub has quit IRC15:45
*** jaypipes has joined #openstack-meeting15:46
*** claudiub has joined #openstack-meeting15:46
*** lazy_prince has quit IRC15:47
*** Mandell has joined #openstack-meeting15:47
*** xingchao has quit IRC15:48
*** Riddhi has joined #openstack-meeting15:48
*** xingchao has joined #openstack-meeting15:48
*** BobBall has left #openstack-meeting15:50
*** mpaolino has quit IRC15:50
*** sahid has joined #openstack-meeting15:52
*** sahid has quit IRC15:52
*** ddieterly has quit IRC15:52
*** sahid has joined #openstack-meeting15:52
*** ddieterly has joined #openstack-meeting15:52
*** fnaval has quit IRC15:52
*** sballe__ has joined #openstack-meeting15:53
*** stevemar has joined #openstack-meeting15:53
*** aranjan has joined #openstack-meeting15:53
*** unicell has joined #openstack-meeting15:54
*** unicell1 has quit IRC15:56
*** sahid has quit IRC15:56
*** pnavarro has quit IRC15:57
*** wojdev has joined #openstack-meeting15:57
*** thangp has quit IRC15:58
*** spzala has quit IRC15:58
*** _nadya_ has joined #openstack-meeting15:59
*** barclaac has joined #openstack-meeting15:59
*** thangp has joined #openstack-meeting15:59
*** spzala has joined #openstack-meeting15:59
*** otter768 has joined #openstack-meeting16:00
*** crinkle has quit IRC16:01
*** rpothier has joined #openstack-meeting16:01
*** Mandell has quit IRC16:01
*** crinkle has joined #openstack-meeting16:01
*** Mandell has joined #openstack-meeting16:01
*** fzdarsky has quit IRC16:02
*** ildikov has quit IRC16:02
*** Tross has joined #openstack-meeting16:02
*** jdurgin has joined #openstack-meeting16:02
*** fouxm has quit IRC16:03
*** ekarlso has quit IRC16:03
*** egallen has quit IRC16:03
*** SpamapS has quit IRC16:03
*** rpothier has left #openstack-meeting16:04
*** SpamapS has joined #openstack-meeting16:04
*** otter768 has quit IRC16:05
*** banix has joined #openstack-meeting16:05
*** annegentle has quit IRC16:06
*** kmartin has joined #openstack-meeting16:06
*** fnaval has joined #openstack-meeting16:06
*** annegentle has joined #openstack-meeting16:06
*** fouxm has joined #openstack-meeting16:07
*** mrunge has quit IRC16:08
*** ekarlso has joined #openstack-meeting16:08
*** ChuckC has joined #openstack-meeting16:08
*** bobmel_ has quit IRC16:09
*** bobmel has joined #openstack-meeting16:10
*** thumpba has joined #openstack-meeting16:11
*** tomoe_ has quit IRC16:12
*** egallen has joined #openstack-meeting16:13
*** JoshNang has joined #openstack-meeting16:14
*** atiwari has joined #openstack-meeting16:14
*** sahid has joined #openstack-meeting16:14
*** irenab has quit IRC16:16
*** amotoki has quit IRC16:16
*** fzdarsky has joined #openstack-meeting16:16
*** carl_baldwin has quit IRC16:16
*** thumpba_ has joined #openstack-meeting16:17
*** ildikov has joined #openstack-meeting16:18
*** egallen has quit IRC16:18
*** changbl has joined #openstack-meeting16:19
*** egallen has joined #openstack-meeting16:19
*** ChuckC has quit IRC16:20
*** thumpba has quit IRC16:20
*** rushil has joined #openstack-meeting16:21
*** ddieterly has quit IRC16:22
*** ddieterly has joined #openstack-meeting16:22
*** carl_baldwin has joined #openstack-meeting16:24
*** aranjan has quit IRC16:25
*** ebalduf has joined #openstack-meeting16:25
*** SridharG has left #openstack-meeting16:25
*** nelsnelson has joined #openstack-meeting16:26
*** nelsnelson has quit IRC16:27
*** enikanorov has quit IRC16:28
*** nelsnelson has joined #openstack-meeting16:28
*** enikanorov has joined #openstack-meeting16:28
*** thumpba has joined #openstack-meeting16:30
*** alexpilotti has quit IRC16:31
*** unicell1 has joined #openstack-meeting16:32
*** che-arne has joined #openstack-meeting16:32
*** bill_az has quit IRC16:32
*** unicell has quit IRC16:32
*** thumpba_ has quit IRC16:33
*** yamahata has joined #openstack-meeting16:33
*** FJB has quit IRC16:34
*** SridharRamaswamy has joined #openstack-meeting16:36
*** otoolee has quit IRC16:36
*** ildikov has quit IRC16:37
*** david-lyle_afk has quit IRC16:37
*** david-lyle has quit IRC16:37
*** reed has joined #openstack-meeting16:38
*** MaxV has quit IRC16:39
*** FJB has joined #openstack-meeting16:40
*** tsekiyama has joined #openstack-meeting16:41
*** alop has joined #openstack-meeting16:42
*** FJB has quit IRC16:42
*** otoolee has joined #openstack-meeting16:44
*** MarkAtwood has joined #openstack-meeting16:45
*** MarkAtwood has quit IRC16:45
*** MarkAtwood has joined #openstack-meeting16:45
*** stefan_amann has quit IRC16:47
*** ebalduf has quit IRC16:47
*** rajeshr has joined #openstack-meeting16:47
*** ebalduf has joined #openstack-meeting16:48
*** mtanino has joined #openstack-meeting16:49
*** Mandell has quit IRC16:49
*** moha_hunt has joined #openstack-meeting16:49
*** rmoe has quit IRC16:50
*** thedodd has quit IRC16:51
*** Guest32544 is now known as redrobot16:51
*** killer_prince has joined #openstack-meeting16:51
*** killer_prince is now known as lazy_prince16:51
*** varora has joined #openstack-meeting16:51
*** annegent_ has joined #openstack-meeting16:54
*** moha_hunt has quit IRC16:54
*** jcoufal has quit IRC16:54
*** xingchao has quit IRC16:55
*** aepifanov has joined #openstack-meeting16:56
*** kmartin has quit IRC16:56
*** unicell1 has quit IRC16:57
*** scheuran_ has quit IRC16:57
*** jhenner has joined #openstack-meeting16:57
*** annegentle has quit IRC16:58
*** evgenyf has quit IRC16:58
*** gyee has joined #openstack-meeting16:58
*** olkonami has joined #openstack-meeting17:00
*** redixin has joined #openstack-meeting17:01
*** amaretskiy has joined #openstack-meeting17:01
*** paboldin has joined #openstack-meeting17:01
*** MaxV has joined #openstack-meeting17:02
*** Gerald_K has quit IRC17:02
*** andreykurilin_ has joined #openstack-meeting17:03
*** nellysmitt has quit IRC17:03
boris-42msdubov_: ping17:04
boris-42andreykurilin_: ping17:04
andreykurilin_pong)17:04
boris-42oanufriev: ping17:04
msdubov_boris-42:hi!17:04
oanufrievpong, boris-4217:04
andreykurilin_boris-42: I just came home.17:04
*** meteorfox has joined #openstack-meeting17:05
amaretskiyhi17:05
e0nehi17:05
*** david-lyle has joined #openstack-meeting17:05
*** NarenNarendra has joined #openstack-meeting17:05
*** rmoe has joined #openstack-meeting17:05
*** psd has joined #openstack-meeting17:05
boris-42e0ne: hi17:06
*** echoingumesh has joined #openstack-meeting17:06
*** shwetaap has joined #openstack-meeting17:06
boris-42#startmeeting Rally17:06
openstackMeeting started Tue Mar  3 17:06:17 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:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:06
*** noelbk has joined #openstack-meeting17:06
*** openstack changes topic to " (Meeting topic: Rally)"17:06
openstackThe meeting name has been set to 'rally'17:06
boris-42hello everbody17:06
*** exploreshaifali has joined #openstack-meeting17:06
boris-42let's start from e0ne17:06
boris-42#topic Cinder benchmarks17:06
*** openstack changes topic to "Cinder benchmarks (Meeting topic: Rally)"17:06
e0nehi17:06
boris-42e0ne: any updates  ?17:06
e0nei've got a few17:07
e0nehttps://review.openstack.org/#/c/152670/ - is blocked by ci17:07
e0neit's too hard to investigate issues w/o logs17:07
*** khaldrogox has joined #openstack-meeting17:08
*** thumpba has quit IRC17:08
*** VijayB has joined #openstack-meeting17:08
e0neand we'll continue to work on others banchmarks after cinderclient release17:08
boris-42redixin: ping17:08
redixinpong17:08
boris-42redixin: this patch is blocekd by CI17:09
boris-42redixin: Mirantis CI17:09
boris-42redixin: maybe you can take a look why it fails ?17:09
redixinsure17:09
boris-42redixin: thank you17:09
*** kmartin has joined #openstack-meeting17:09
boris-42e0ne: so redixin is going to help you because it's Mirantis Rally CI god17:09
*** ygbo has quit IRC17:10
e0neboris-42, redixin: thanks17:10
boris-42e0ne: anything else?17:10
e0neno, thats all from my side17:10
e0neexcept17:10
boris-42e0ne: ?17:10
e0newe started investigation on cinder performance. rally on gates helps us. i'll post update next week17:11
*** alexpilotti has joined #openstack-meeting17:11
e0neactully, it was found with rally17:11
*** andreykurilin_ has quit IRC17:12
*** Longgeek has quit IRC17:12
*** andreykurilin_ has joined #openstack-meeting17:13
amaretskiymaybe submit a user story about that?17:13
*** ildikov has joined #openstack-meeting17:13
boris-42e0ne: yep17:13
boris-42e0ne: we have in rally/doc/user_stories17:13
boris-42e0ne: so it will be nice to contribute to it17:13
boris-42e0ne: could you do it?17:13
e0neboris-42: need to take a look on it first17:14
msdubov_e0ne https://github.com/stackforge/rally/tree/master/doc/user_stories17:14
msdubov_e0ne: And then it is included in our docs http://rally.readthedocs.org/en/latest/user_stories.html17:14
*** changbl has quit IRC17:14
*** russell_h has joined #openstack-meeting17:14
*** russell_h has quit IRC17:14
*** russell_h has joined #openstack-meeting17:14
msdubov_e0ne: So it will be very nice if you add a user story17:15
e0nei won't promice anything except i'll take a look on it17:15
*** moha_hunt has joined #openstack-meeting17:15
msdubov_e0ne: Anyway, if you have no time to write long texts, you can just send the data and the main points to me and I'll make a user story out of it.17:16
boris-42okay17:16
e0nemsdubov_: thanks17:16
boris-42#topic Mirantis CI updates17:17
*** openstack changes topic to "Mirantis CI updates (Meeting topic: Rally)"17:17
boris-42redixin: please share updates to Mirantis CI17:17
redixinwe have a new job ecli-py34-postgres, so rally will support py34 soon17:18
*** Longgeek has joined #openstack-meeting17:18
*** gabrielbezerra has joined #openstack-meeting17:18
redixinalso we will see "logs of all services" soon17:19
boris-42redixin: so we need to merge patch from andreykurilin_ ?17:19
redixinnot yet17:19
boris-42redixin: or we are blocked by publishing results?17:19
*** sahid has quit IRC17:20
redixinhe wants to see command'd output, and this will be done soon too17:20
boris-42redixin: great, could you concentrate on this stuff ^17:20
boris-42redixin: so we will get support of py34 soon?17:20
andreykurilin_yes, I want to be sure that all rally commands work as expected:)17:20
andreykurilin_in py34 env17:20
*** Longgeek has quit IRC17:21
redixinwe will got py34 after this job show us that everything works as expected17:21
*** ChuckC has joined #openstack-meeting17:23
*** akuznetsov has quit IRC17:23
redixinthats all i think17:24
*** thomasem has joined #openstack-meeting17:24
*** jpeeler has joined #openstack-meeting17:26
*** wojdev has quit IRC17:27
*** VijayB has quit IRC17:27
*** lpeer__ has quit IRC17:28
*** melwitt has joined #openstack-meeting17:29
*** claudiub has quit IRC17:29
boris-42uh sry17:30
boris-42#topic New Rally input format17:30
*** openstack changes topic to "New Rally input format (Meeting topic: Rally)"17:30
boris-42Okay guys I see a lot of reviews17:30
boris-42they are all quite small17:30
boris-42https://review.openstack.org/#/c/159065/17:31
boris-42redixin: ^ what do you think17:31
boris-42echoingumesh: as well what do you think=)17:31
*** tiswanso has quit IRC17:31
boris-42msdubov_: what do you think is it good engouh?17:31
msdubov_boris-42: What do you think about my proposal about task modes (consequent/parallel)?17:32
msdubov_boris-42: That's the main point I had17:32
redixini will take a look17:32
boris-42msdubov_: so I think it's valid case17:32
msdubov_boris-42: As for the rest, seems ok17:32
*** tiswanso has joined #openstack-meeting17:32
boris-42msdubov_: so like we can have scenario that will create image17:32
msdubov_boris-42: by 'valid' you mean that we can implement it this way?17:32
*** e0ne has quit IRC17:32
boris-42msdubov_: then scenario that will delete them17:32
*** jlanoux has quit IRC17:32
msdubov_boris-42: Yep17:32
boris-42msdubov_: or just list()17:32
boris-42msdubov_: so yep I will add that in new version17:33
boris-42msdubov_: of review17:33
*** wojdev has joined #openstack-meeting17:33
msdubov_boris-42: And with this modes the task would be a bit more readable, because now it's not obvious that the scenario are run in parallel...17:33
*** sarob has quit IRC17:33
*** david8hu has joined #openstack-meeting17:33
msdubov_boris-42: Great17:33
*** unicell1 has joined #openstack-meeting17:33
boris-42others?17:34
echoingumeshI think i like it17:34
boris-42echoingumesh: do you find it simpler then previous one?17:34
echoingumeshYes17:34
boris-42echoingumesh: if something is unclear it's better to change it now=)17:34
*** lpeer__ has joined #openstack-meeting17:35
boris-42echoingumesh: ok it's great the end users find format simpler17:35
*** Apoorva has joined #openstack-meeting17:35
boris-42echoingumesh: it was as well one of the goal of refactoring format17:36
*** vivek-ebay has joined #openstack-meeting17:37
boris-42okay let's move17:37
boris-42#topic Open Discussion17:37
*** openstack changes topic to "Open Discussion (Meeting topic: Rally)"17:37
boris-42Does somebody would like to discuss anything?17:37
*** aranjan has joined #openstack-meeting17:37
amaretskiyno17:37
msdubov_I'd like just once again to point to the update in docs: https://review.openstack.org/15609317:38
msdubov_Maybe we can have it in the next release as well17:38
msdubov_That would be nice17:38
boris-42msdubov_: uuuuu17:38
boris-42msdubov_: big one17:38
boris-42msdubov_: I will take a look17:38
msdubov_boris-42: Actually not =) Mostly pictures + copy-paste of your blog post17:39
boris-42msdubov_: ok I will take a look17:39
boris-42msdubov_: btw we should add as well step17:39
boris-42msdubov_: related to using templated task17:39
boris-42msdubov_: maybe I will put some kind of new blogpost17:39
msdubov_boris-42:Agree17:39
boris-42msdubov_: and you will just port it=)17:39
msdubov_boris-42: But let's not have too many steps17:40
msdubov_boris-42: Better no more than 1017:40
*** dannywilson has joined #openstack-meeting17:40
*** jprovazn has quit IRC17:42
*** leeantho has joined #openstack-meeting17:43
*** IanGovett has quit IRC17:43
*** fzdarsky has quit IRC17:43
*** msdubov_ has quit IRC17:43
boris-42So regarding to steps I think we should have17:44
boris-42guide for various stuss17:45
boris-42"rally verfiy step by step" "rally benchmarking step by step"17:45
boris-42and so on17:45
boris-42#topic new Reports17:46
*** openstack changes topic to "new Reports (Meeting topic: Rally)"17:46
boris-42#topic new reports generation stuff17:46
*** openstack changes topic to "new reports generation stuff (Meeting topic: Rally)"17:46
boris-42amaretskiy: hi17:46
boris-42amaretskiy: any updated to graphs?17:46
boris-42amaretskiy: where they will be?17:46
amaretskiyI have submitted new patches regarding reports last week17:47
boris-42amaretskiy: they were -1 by me17:47
andreykurilin_link please)17:47
amaretskiyso big work was splitted into 2 patches17:47
boris-42andreykurilin_: or?17:47
amaretskiyhttps://review.openstack.org/#/c/159458/17:47
amaretskiyhttps://review.openstack.org/#/c/146814/17:47
boris-42amaretskiy: when you are going to do it normal way?)17:47
*** IanGovett has joined #openstack-meeting17:47
amaretskiythis week17:47
amaretskiyi'm currently finishing another patch + reviewing17:48
*** pdb has quit IRC17:48
boris-42amaretskiy: okay please try to avoid unclear stuff in code17:48
boris-42amaretskiy: if it is possible17:48
amaretskiyso I'm going to update these patches till friday17:48
amaretskiyokay17:48
boris-42amaretskiy: ok17:48
andreykurilin_boris-42: I hava a one question)17:49
boris-42andreykurilin_: regarding to reports?17:49
andreykurilin_no17:49
*** yamahata has quit IRC17:49
boris-42andreykurilin_: ok17:49
boris-42#topic Open Discussion17:49
*** openstack changes topic to "Open Discussion (Meeting topic: Rally)"17:49
boris-42andreykurilin_: so?17:49
*** sarob has joined #openstack-meeting17:49
andreykurilin_boris-42: Am I right thath we are waiting for https://review.openstack.org/#/c/155225/ ? After this patch will be merged, new veriosn of rally will be released?17:50
andreykurilin_or what additional changes you want to see in 0.2.0 ?17:50
boris-42andreykurilin_: this one is the most important17:51
boris-42andreykurilin_: others are just nice to have17:51
*** dmacpher has quit IRC17:51
andreykurilin_:)17:51
boris-42andreykurilin_: so when we merge that patch17:51
boris-42andreykurilin_: I will cut new version17:51
andreykurilin_boris-42: ok, I'll start reviewing it, right now:)17:51
*** eghobo has joined #openstack-meeting17:52
boris-42andreykurilin_: great I am going to re-review it as well17:52
*** _nadya_ has quit IRC17:52
boris-42andreykurilin_: I need to test it one more time by hands17:52
boris-42=)17:52
andreykurilin_heh17:52
boris-42andreykurilin_: by the way it will be nice to fix py34 as well17:53
*** wojdev has quit IRC17:53
boris-42=)17:53
andreykurilin_boris-42: yes17:53
andreykurilin_but this change need more time17:53
boris-42andreykurilin_: okay then in next release17:53
andreykurilin_I want to test Rally in py31,py32,py33 envs17:53
boris-42andreykurilin_: I think that can be done in next release17:54
boris-42andreykurilin_: for now just add support for py3417:54
boris-42step by step17:54
andreykurilin_boris-42: okey17:54
boris-42andreykurilin_: so okay17:54
boris-42any other questions?17:54
andreykurilin_boris-42: btw, how we can automate checking py31,py32,py33 ?17:54
*** pnavarro has joined #openstack-meeting17:54
boris-42andreykurilin_: we can use Rally Mirantis CI for that17:55
andreykurilin_imo, there are no reasons to have separate jobs for each env17:55
boris-42andreykurilin_: so we can have one job that has everything17:55
boris-42andreykurilin_:  but actually we don't need17:55
boris-42andreykurilin_: because redixin is using lxc containers17:56
boris-42andreykurilin_: so it's similar to create new job or run everything inside one job17:56
andreykurilin_boris-42: okey17:56
*** exploreshaifali has quit IRC17:56
*** tmcpeak1 has joined #openstack-meeting17:56
boris-42okay17:57
boris-42let's end meeting cause I have to go=)17:57
boris-42see you guys17:57
boris-42#endmeeting17:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:57
openstackMeeting ended Tue Mar  3 17:57:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:57
*** amaretskiy has left #openstack-meeting17:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-03-17.06.html17:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-03-17.06.txt17:57
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-03-03-17.06.log.html17:57
*** markvan_ has quit IRC17: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, wanghong, fmarco76 https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting17:58
ayoungHeyo17:58
raildoo/17:58
marekdo/17:58
morganfainbergit's that time of the week again.17:58
*** VijayB has joined #openstack-meeting17:58
amakarovo/17:58
tmcpeak1o/17:58
*** psd has left #openstack-meeting17:58
*** chandankumar has joined #openstack-meeting17:58
*** oanufriev has quit IRC17:58
morganfainberglots of people on that list not in this channel.17:59
*** lhcheng_ has joined #openstack-meeting17:59
gyee\o17:59
marekdmorganfainberg: could do some cleaning17:59
*** lhcheng_ is now known as lhcheng17:59
*** markvan has joined #openstack-meeting17:59
*** goalotc has quit IRC17:59
rodrigodso/17:59
topolo/17:59
*** ljfisher has joined #openstack-meeting17:59
*** xingchao has joined #openstack-meeting17:59
marekdmorganfainberg: is the agenda up to date?17:59
bknudsonhi18:00
morganfainbergmarekd, it is now18:00
morganfainbergok so. here we go18:00
tmcpeak1I had added a Bandit item18:00
tmcpeak1I think it might have just been removed18:00
*** henrynash has joined #openstack-meeting18:00
morganfainbergtmcpeak1, i moved it to the main agenda18:00
*** echoingumesh has left #openstack-meeting18:00
henrynashhi18:00
tmcpeak1cool, gotcha18:00
*** bdpayne has joined #openstack-meeting18:00
*** SridharRamaswamy has quit IRC18:00
morganfainberg#Startmeeting Keystone18:00
morganfainbergoh..18:00
morganfainberg#atartmeeting Keystone18:01
marekd:)18:01
morganfainberg#startmeeting Keystone18:01
openstackMeeting started Tue Mar  3 18:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: Keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
amakarovmorganfainberg, you made it!18:01
morganfainberg#topic Bandit - a security focused static code analysis tool18:01
*** aimon has quit IRC18:01
*** openstack changes topic to "Bandit - a security focused static code analysis tool (Meeting topic: Keystone)"18:01
bknudsonhi18:01
morganfainberglets just get right into it18:01
morganfainbergtmcpeak1 o/18:01
*** otter768 has joined #openstack-meeting18:01
*** shardy has quit IRC18:01
*** goalotc has joined #openstack-meeting18:01
*** haneef has joined #openstack-meeting18:01
tmcpeak1hi all, I'm tmcpeak - I usually hang out in #openstack-security18:01
ayoungCan you do Static analysis on Python?18:01
*** htruta has joined #openstack-meeting18:01
tmcpeak1sure18:01
ayoungtmcpeak1, lies18:01
ayoungHa18:02
tmcpeak1lmao18:02
tmcpeak1well18:02
* ayoung jaded18:02
tmcpeak1kinda18:02
tmcpeak1:D18:02
*** SridharRamaswamy has joined #openstack-meeting18:02
*** lhcheng_ has joined #openstack-meeting18:02
morganfainbergayoung, i can look at code in python... thats the same thing right? :P18:02
tmcpeak1so for those that haven't heard of Bandit, it's here18:02
gyeejust use the @deprecation tag :)18:02
* stevemar sneaks in late18:02
* morganfainberg quiets up for tmcpeak1 to continue.18:02
tmcpeak1https://github.com/stackforge/bandit18:02
topolstatic analysis for python must be tough with all the dynamic binding18:02
tmcpeak1#link https://github.com/stackforge/bandit18:02
*** aimon has joined #openstack-meeting18:02
tmcpeak1and #link https://wiki.openstack.org/wiki/Security/Projects/Bandit18:03
*** goalotc has quit IRC18:03
tmcpeak1so basically the idea here is to call attention to low hanging fruit in code that is checked in18:03
*** VijayB has quit IRC18:03
tmcpeak1we have about 40 tests18:03
*** goalotc has joined #openstack-meeting18:03
ayoungtmcpeak1, I assume that this is being run against Keystone, and any weaknesses found will be treated as a security bug until triaged?18:03
tmcpeak1so far, many of them are very very noisy18:03
* lbragstad walks in late18:03
tmcpeak1yes, so the reason I'm here is that I'd like Keystone to volunteer to run Bandit in a gate18:03
*** meteorfox has left #openstack-meeting18:04
tmcpeak1bknudson expressed some interest in this18:04
dolphmtmcpeak1: as in, false positives?18:04
*** lhcheng has quit IRC18:04
ayoungtmcpeak1, hmmm18:04
ayoungGate is the wrong place18:04
joesavako/ : )18:04
*** marcusvrn has quit IRC18:04
ayoungwe don't want to publically announce any problems18:04
tmcpeak1so the profile that I've made for Keystone is conservative and currently doesn't have any results18:04
bknudsonI've been working on a tox env -- https://review.openstack.org/#/c/157930/18:04
*** timcline has joined #openstack-meeting18:04
ayounghere's the issue18:04
tmcpeak1ayoung: these are publicly available anyway, Bandit is opensource18:04
*** changbl has joined #openstack-meeting18:04
bknudsonthe point of putting it in the gate is to stop bad code getting in to begin with.18:04
ayounglets say Bandit gets smart about some new problem18:04
tmcpeak1you can just pull it down and find the same thing the gate test finds18:04
*** gmurphy has joined #openstack-meeting18:05
ayoungand the gate now announces to the world :Keystone has vuln X18:05
*** anish__ has quit IRC18:05
tmcpeak1yeah, but that is very publicly available anyway18:05
ayoungtmcpeak1, not really18:05
dolphmtmcpeak1: it sounds like you're implying we have violations against the full suite of tests?18:05
tmcpeak1any attacker would already have access to that information18:05
marekdafter the vuln is fixed and commited18:05
ayoungtmcpeak1, this should be run, but....18:05
tmcpeak1dolphm: yeah, the full suite of tests include some very noisy ones that need to be tuned18:05
*** otter768 has quit IRC18:06
ayoungOK...so it would be something like this:18:06
lbragstadwhat about publishing those results to a private page?18:06
*** marun has joined #openstack-meeting18:06
ayoung1.  run it privately, file bugs, get Keystone as secure as Bandit can say18:06
tmcpeak1I've created a bandit config file for use with Keystone18:06
tmcpeak1http://pastebin.com/SeBkRvCS18:06
tmcpeak1#link http://pastebin.com/SeBkRvCS18:06
bknudsonthe plan is to have bandit work very similar to pep818:06
tmcpeak1please check out that link18:06
ayoung2.  No upgrades to Bandit in Gate until private runs have the same level of fix18:06
bknudsonas with pep8, a new bandit wouldn't be run against keystone in the gate without a requirements bump.18:06
ayoungtmcpeak1, you understand my concern?18:07
tmcpeak1ayoung: absolutely18:07
*** jaypipes has quit IRC18:07
ayoungWe do things like this internally, too.  We run tools like Valgrind etc.  And this is fantastic18:07
*** sicarie has joined #openstack-meeting18:07
morganfainbergthis means bandit would need to be locked separately from requirements18:07
tmcpeak1so with what in my opinion is a sensible profile, Keystone already has no vulnerabliities18:07
tmcpeak1here's output of recentish Keystone18:07
morganfainbergsince global reqs overrides requirements.txt18:07
ayoungbut we don't publish the results.  We consume them internally and fix18:07
tmcpeak1#link http://pastebin.com/U0Fpjar118:07
morganfainbergtmcpeak1, i'm running it locally right now on keystone fwiw18:07
morganfainberg;)18:07
dstaneksorry - here now. traffic was a killer18:07
tmcpeak1morganfainberg: oh cool, you're already using it?18:08
tmcpeak1so yeah, some of the tests in the full suite generate *tons* of false positives18:08
*** jorge_munoz has joined #openstack-meeting18:08
morganfainbergtmcpeak1, just ran it18:08
morganfainbergtmcpeak1, took me 30 seconds to enable18:08
tmcpeak1the idea with the profile I pasted above is that it will really only flag things you don't want in your code18:08
morganfainbergso, i see sqla issues and complaining about popen18:08
morganfainbergmostly18:08
tmcpeak1morganfainberg: use the above linked profile please18:09
ayoungpopen is awesome!18:09
tmcpeak1sql tests are noisy18:09
morganfainbergand binding to all interfaces (desired)18:09
dolphmtmcpeak1: please be clear - you're suggesting that there's no value in reporting the violations that bandit is currently seeing in keystone?18:09
bknudsonearlier it found a problem where regular random was used, so I posted a fix for that: https://review.openstack.org/#/c/157990/18:09
tmcpeak1dolphm: no, not at all.  I'd like to see folks using Bandit on a regular (manual) basis to close bugs18:09
tmcpeak1I also see value in an automated gate process which prevents egregious checkins18:09
tmcpeak1please see this18:09
bknudsonand it also complained about the use of 0.0.0.0 for default bind host: https://review.openstack.org/#/c/157975/18:09
tmcpeak1(before I put this, please note this is all publicly available info, I'm not disclosing 0 days)18:10
bknudsonbut I didn't have tmcpeak1's profile.18:10
*** jaypipes has joined #openstack-meeting18:10
tmcpeak1#link http://pastebin.com/G7iVFGZD18:10
tmcpeak1bknudson: I just made it this morning :)18:10
tmcpeak1we'd like to prevent this kind of code from getting into Keystone18:10
bknudsonjust be glad we're not trove.18:10
raildol18:11
*** khaldrogox has quit IRC18:11
ljfisherayoung, so presumably something real caught in a gate test wouldn’t actually get merged until fixed. Would you still consider that a vulnerability in Keystone even if it hasn’t been merged? (I’ve also been hacking on Bandit)18:11
morganfainbergso tmcpeak1 , with that profile i see no violations?18:11
tmcpeak1yeah, here's an output of Keystone with that profile18:11
morganfainbergljfisher, the concern isn't new code. we agree that is fine18:11
tmcpeak1command to run Bandit against Keystone with verbose profile: bandit -c keystone.yaml -p keystone_verbose ~/Documents/projects/keystone/ -r18:11
tmcpeak1Keystone Bandit conservative run: http://pastebin.com/U0Fpjar118:11
morganfainbergljfisher, the issue is old code when bandit gets smarter18:12
ayoungljfisher, so my concern is that we need to know about new vulnerabilities before they show up in the gate.  My concner is not with changes, but existing code.  So...I think this is OK...18:12
tmcpeak1morganfainberg: for the gate we are pinning a version18:12
ayoungbut we need to have additional review done when Bandit gets update18:12
tmcpeak1new Bandit functionality won't change your gate18:12
tmcpeak1you'll pin to a version, and chose when to update18:12
tmcpeak1same as you do with other dependancies18:12
ayoungpinning version is good18:12
morganfainbergtmcpeak1, pins in requirements.txt are overriden by global requirements18:12
*** harlowja_away is now known as harlowja_18:12
morganfainbergFYI18:12
nonameenternameo/18:12
morganfainbergyou can't pin in requirements.txt18:12
tmcpeak1the pin will go into global requirements18:12
ayoungM y concern is not Keystone, but Bandit.  Before Bandit posts a new update...we'd want to know what it caught.18:13
bknudsonthe pin for hacking is handled differently.18:13
bknudsonit's not automatically updated.18:13
morganfainbergbknudson, we'd need this to fall into that same category then18:13
ayoungOK...Gate is a red herring.  I have no problem with running Bandit in gate18:13
tmcpeak1cool :)18:14
tmcpeak1ayoung: you still concerned about vulns though?18:14
morganfainbergtmcpeak1, yeah i'd be fine with this being an additional check - i'd like this to not be lumped into pep8 though18:14
morganfainbergtmcpeak1, if infra doesn't mine i'd like to see this as a specific job18:14
tmcpeak1morganfainberg: same, I'd like it to be a separate job18:14
tmcpeak1yeah18:14
morganfainbergif there are concerns from infra we can put it in pep818:14
ayoungWhat we do need is to know about new classes of vulnerabilities before we make the tool general available.  And that is not just a Keystone issue18:14
morganfainbergbut my opinion is 1st go w/ separate job18:14
bknudsonthe requirements for this job are different than pep818:14
morganfainbergbknudson, exactly18:15
bknudsonsince bandit doesn't need all the test-requirements like pep8 does.18:15
morganfainbergand having it clearly be a separate failure would be very good.18:15
ayoung++18:15
dolphmtmcpeak1: have you successfully used bandit to identify and fix actual vulnerabilities?18:15
*** sankarshan is now known as sankarshan_away18:15
tmcpeak1ayoung: I definitely hear what you're saying.  Another piece which I'm not mentioning here because it isn't directly related to my gate test mission is getting people  to use it against their own projects18:15
morganfainbergtmcpeak1, so i'm not opposed to this being enabled for keystone.18:15
tmcpeak1dolphm: absolutely.  One place I've had great success is trove18:15
*** khaldrogox has joined #openstack-meeting18:16
*** alexpilotti_ has joined #openstack-meeting18:16
tmcpeak1let me dig up one for you18:16
*** ivar-lazzaro has joined #openstack-meeting18:16
morganfainbergtmcpeak1, i assume the .yaml will be hosted in keystone's tree [for sanity sake]18:16
tmcpeak1https://bugs.launchpad.net/trove/+bug/134993918:16
openstackLaunchpad bug 1349939 in Trove "Multiple vulnerabilities in Couchbase implementation of restore strategy" [Critical,Fix released] - Assigned to Amrith (amrith)18:16
tmcpeak1so this bug in Trove was… really bad18:16
*** alexpilotti has quit IRC18:16
*** alexpilotti_ is now known as alexpilotti18:16
morganfainbergnot that i expect ot be changing it a bunch, but to save you a headache of updating.18:16
*** erlon has joined #openstack-meeting18:17
tmcpeak1I found this using Bandit and then tracing through the code18:17
morganfainbergfor every project in the future.18:17
ayoungtmcpeak1, this has the potential to be a Pandora's box.  But the box is already open I guess.18:17
tmcpeak1this would have resulted in VMT process if Trove had been in production already18:17
*** lhcheng has joined #openstack-meeting18:17
bknudsonno OSSA only because it was in master.18:17
bknudsonso it caught a bug before release.18:17
tmcpeak1morganfainberg: yes, I'd really like for each project to maintain their own profile18:17
bknudsonso... thanks!18:17
morganfainbergtmcpeak1, cool18:17
tmcpeak1ayoung: yeah, box is open :)18:18
morganfainbergtmcpeak1, so step 1 for Keystone, - experimental job in gate, lets get the keystone tree in shape for this, step 2 - non-vote, once we're happy - voting18:18
tmcpeak1cool, so I didn't want to take up all your time18:18
amrithtmcpeak1, the bug you mention has been fixed in trove, yes?18:19
amrithI remember doing it a while ago.18:19
tmcpeak1morganfainberg: perfect18:19
tmcpeak1amrith: yeah, you fixed it18:19
morganfainbergtmcpeak1, ping me when you have the reviews to change project-config up, i'll +1 them as needed18:19
amrithtmcpeak1, thx18:19
*** s3wong has joined #openstack-meeting18:19
bknudsonwe need an official release of bandit, also.18:19
tmcpeak1morganfainberg: perfect, thank you18:19
*** lhcheng_ has quit IRC18:19
morganfainberglets make sure bandit is released/in pypi etc18:19
tmcpeak1yeah, there are a couple of more steps we need, but I'll be reaching out to a few of you to push this along when we're ready18:20
*** yamahata has joined #openstack-meeting18:20
tmcpeak1want to make sure the user (your) experience is rock-solid18:20
*** crc32 has joined #openstack-meeting18:20
bknudsonso it's going to be clean to begin with18:20
dolphmtmcpeak1: i just hope it doesn't prove to be a noisey tool spewing false positives at every contributor & reviewer18:20
bknudsonany new changes will eventually go through bandit18:20
morganfainbergtmcpeak1, thanks. and make sure you get the experimental stuff in infra first, so we can do "check expirimental" as we implement the yaml etc in our tree18:20
bknudsonand if it's flagging things we need to decide if it's a false positive.18:20
tmcpeak1dolphm: if it is, we (Bandit team) have completely failed.  We're going to test the crap out of it before we ask you guys to use it18:21
dolphmtmcpeak1: is there a feature similar to # noqa for flake8 ?18:21
bknudsonThere's a #nosec comment you can put on a line to tell bandit to ignore it.18:21
tmcpeak1^ :)18:21
tmcpeak1our goal is not to have you guys using #nosec to get it to shut up18:21
*** leonchio_ has joined #openstack-meeting18:21
*** yamahata has quit IRC18:21
tmcpeak1nosec should basically be like "yeah we understand this isn't good from security but it's really ok because xyz"18:22
*** VijayB_ has joined #openstack-meeting18:22
*** andreykurilin_ has quit IRC18:22
morganfainbergthere are cases we need to noqa18:22
*** yamahata has joined #openstack-meeting18:22
morganfainbergthere will be limited cases to nosec18:22
dolphmtmcpeak1: i'd expect a small handful of legitimate # nosec with explanations18:22
tmcpeak1I've found bugs like that before too.. In nova they were generating a session ID in an uncryptographically safe way, turns out it didn't matter18:22
morganfainbergbut those will be the exception to the rule18:22
*** _nadya_ has joined #openstack-meeting18:22
tmcpeak1so that's a perfect use for #nosec followed by a comment about why it doesn't matter18:22
morganfainbergtmcpeak1, ok i look forward to seeing this become available.18:23
*** andreykurilin_ has joined #openstack-meeting18:23
*** aranjan has quit IRC18:23
*** achanda has joined #openstack-meeting18:23
tmcpeak1the Nova guys actually had pushed a comment explaining why it isn't a security risk, so next guy doesn't come and panic about uncrypto session ID18:23
tmcpeak1cool, sounds good!18:23
*** narenhn has joined #openstack-meeting18:23
dolphmtmcpeak1: # nosec should require an inline comment at least!18:23
tmcpeak1definitely18:24
morganfainbergtmcpeak1, yeah was just going to suggest that18:24
dolphmtmcpeak1: # nosec: {why}18:24
morganfainbergmake it so #nosec can't be just bare on the line18:24
dolphmmorganfainberg: ++18:24
tmcpeak1yeah, that's an awesome idea18:24
dolphmmorganfainberg: although you probably need more than just an inline comment to justify such a "why"18:24
tmcpeak1I'll add that to our dev list :)18:24
tmcpeak1yeah, they're probably going to be somewhat involved18:25
tmcpeak1honestly with current #nosec handling I'm not sure the best way to do it, but I agree we should require something18:25
dolphmtmcpeak1: maybe # nosec requires a comment on the preceeding line?18:25
tmcpeak1we're dealing with AST and tying together multi-line comments is… at least a little challenging18:25
tmcpeak1I'll throw it on our backlog though18:26
dolphmtmcpeak1: that's the fun!18:26
morganfainbergtmcpeak1, dolphm throws down the gauntlet... ;)18:26
tmcpeak1and in the mean time we can have project reviewers throw liberal -1's for promiscuous #nosec usage18:26
tmcpeak1it shall be done :D18:26
morganfainbergok so we'll look for the infra changes and then the stuff to make bandit a reality18:26
morganfainbergtmcpeak1, thanks!18:27
tmcpeak1sounds great!18:27
tmcpeak1thanks all18:27
morganfainberg#topic Specs that will need Feature Freeze Exceptions (FFE) and/or be delayed until Liberty18:27
*** openstack changes topic to "Specs that will need Feature Freeze Exceptions (FFE) and/or be delayed until Liberty (Meeting topic: Keystone)"18:27
*** tmcpeak1 has left #openstack-meeting18:27
morganfainbergSo, it's that sad time of the cycle18:27
*** NarenNarendra has quit IRC18:27
bknudson:(18:27
rodrigods:(18:27
raildo:(18:27
morganfainbergtime to punt things to either FFE or next cycle18:27
*** rbowen has quit IRC18:27
morganfainberg#link https://launchpad.net/keystone/+milestone/kilo-318:27
*** radez is now known as radez_g0n318:27
stevemari never understood why this is a sad time... it'll go in a few week later is all :P18:28
*** rprakash has quit IRC18:28
morganfainbergcurrently on the chopping block [for FFE unless it is gating today, no particular order]: x509, Domain-SQL, Reseller, Improve list role assignments filtering performance18:28
henrynashSo I really want to keep domain specific configs in Kilo….we are doing pretty well on reviews…but not sure all will get in by the 5th18:28
morganfainbergif those are not gating today, they are getting a -2 (procedural) and require a FFE after k3 cuts, or a delay to liberty18:29
stevemarfwiw i do think the domain-sql stuff is close18:29
morganfainbergi think domain-sql is the best option for FFE, reseller is a close second18:29
*** rbowen has joined #openstack-meeting18:29
morganfainbergthe others i'm not optimistic they will be accepted for FFE18:30
morganfainbergremember FFE isn't just us, keystone-core18:30
marekdthere is also this https://blueprints.launchpad.net/openstack/?searchtext=idp-id-registration18:30
morganfainbergit's also rel-mngmt18:30
marekdand review that is held off by a bug.18:30
rodrigodsfor reseller, we need more eyes on it though, 0 reviews so far18:30
rodrigodswe are about to send the last change of the chain18:31
morganfainbergmarekd, and that one i think will be pushed18:31
*** _nadya_ has quit IRC18:31
morganfainbergmarekd, as much as i'd like to see it.18:31
henrynashmorganfainberg: assuming the reviewers are happy with my updates, the core underpinnings of domain-SQL may well be gating today, not just the “switch on” at the top18:31
morganfainberghenrynash, and thats why i said gating today18:31
morganfainbergif it's gating actively, we'll make sure it lands18:32
marekdmorganfainberg: me too, i wanted to discuss it later (post-meeting)18:32
henrynashmorganfainberg: ok, agreed18:32
morganfainbergif it isn't lets plan a FFE18:32
morganfainbergthat one the FFE would be "yeah we couldn't land this in k3, but it's ready to go"18:32
henrynashmorganfainberg: agreed18:32
stevemarhenrynash, i'll take another look at your stuff today, but i looked at the comments you had made and i think you addressed all my concerns18:33
henrynashstevemar: great, thx18:33
morganfainbergother than that.18:33
morganfainbergi have nothing else for the meeting18:33
morganfainberg#topic Open Discussion18:33
*** openstack changes topic to "Open Discussion (Meeting topic: Keystone)"18:33
marekdok, so maybe i can use some of this time?18:33
morganfainberggo for it18:34
ayounghenrynash, https://review.openstack.org/#/c/160872/3  make a stand alone patch and I'd be ahppy to +2A it18:34
ayoungif depends on Add API support for domain config  and there is no need for that18:34
stevemarayoung, i'll rebase it on master and we can push it through?18:34
marekdhttps://review.openstack.org/#/c/152156/ this review is actually kind of blocked, it passes the unittests but will probably explode with mysql18:34
ayoungstevemar, go for it18:34
henrynashayoung: true..but then the follow on patches can’t depend on two things18:34
marekddo every devstack installation following master18:34
marekdthe bug is here:18:34
ayounghenrynash, reverse the order18:35
marekd#link https://bugs.launchpad.net/keystone/+bug/142633418:35
openstackLaunchpad bug 1426334 in Keystone "DB migration problem with federation extension" [Undecided,In progress] - Assigned to Marco Fargetta (marco-fargetta)18:35
ayoungput the trivial changes at the front of the patch-stack18:35
*** SridharRamaswamy has quit IRC18:35
henrynashayoung: ok….yes, I’ll push it to the front, ++18:35
marekdand as i talked with Marco, adding a migration script will not help18:35
ayoungthanks18:35
stevemarhenrynash, hit that cherry pick button18:35
marekdas sanity_check in oslo_db will raise an exception.18:35
raildoIf someone want review the reseller patches :)18:35
raildo#link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/reseller,n,z18:35
morganfainbergmarekd, and marco has done some work there.18:36
henrynashstevemar: it’s standalne, justa reorder of dependant pacthes18:36
*** che-arne has quit IRC18:36
morganfainbergmarekd, i think we need docstrings for his fix and a bug against oslo to reference18:36
morganfainbergmarekd, my major complaint with his patch18:36
marekdhttps://review.openstack.org/#/c/159803/5/keystone/common/sql/migration_helpers.py ?18:36
marekdmorganfainberg: ^^18:36
morganfainbergthough the code could probably be claeaned up some18:36
morganfainbergmarekd, yeah18:36
bknudsonI wonder why the db migration problem doesn't show up in the gate?18:36
*** markvan has quit IRC18:37
marekdsqlite maybe ?18:37
stevemarbknudson, ^18:37
marekdor theu use mysql?18:37
*** MaxV has quit IRC18:37
*** jamielennox has joined #openstack-meeting18:37
marekdmorganfainberg: oh, i see, he is esentually recreating all the tables18:38
morganfainbergbknudson, because the gate default assumes utf-8 iinodb18:38
morganfainbergthis is a case where someone has misconfigured their mysql then pushed in keystone18:38
morganfainbergthen get wedged18:38
marekdbut if healthy actually? it may move lots of data in some rare cases.18:38
bknudsonmorganfainberg: I thought they changed the gate defaults just to catch this18:38
* jamielennox sneaks in the back18:38
morganfainbergbknudson, clearly not :P18:38
morganfainbergor we did something wonky18:39
bknudsonwe've made fixes in the past to set tables to InnoDB18:39
morganfainbergthe issue here is it related to FKs. so it's ugly18:40
bknudsonI don't think we've tried to fix the charset.18:40
morganfainbergbknudson, we did, migraiton 3718:40
marekdmorganfainberg: for the utf-8 patch we would then need to remove 001, 002 files18:40
morganfainbergmigration*18:40
*** gmurphy has left #openstack-meeting18:40
morganfainbergmarekd, no, we fix them in-place as we have then we do the exceptional case when it's broken to catch anyone who's run them18:40
morganfainbergmarekd, look at the _Fix_migration_37 example18:40
stevemarthis is all sorts of ugly18:40
morganfainbergit's not pretty but it unwedges the deployer18:41
morganfainbergbut we need to figure out how to catch this earlier.18:41
morganfainbergmaybe a hacking check to ensure table definitions in migrations have innodb/utf8?18:41
*** Mandell has joined #openstack-meeting18:41
morganfainbergor a way to make the sanity check less sane in an exceptional case so it can be fixed.18:41
bknudsonwe do have test already for table structure18:41
morganfainbergbknudson, but not in migration.18:42
bknudsonand I think there's a "live" test for innodb.18:42
morganfainbergyeah. anyway this needs some eyes to maek sure we solve it this time ;)18:42
*** Mandell has quit IRC18:42
*** Mandell has joined #openstack-meeting18:43
*** markvan has joined #openstack-meeting18:43
marekdmorganfainberg: where is that _Fix_migration_37 ?18:43
morganfainbergin migration_helpers18:43
bknudsonmarekd: line 14218:43
bknudsonhttps://review.openstack.org/#/c/159803/5/keystone/common/sql/migration_helpers.py18:43
*** ijw has joined #openstack-meeting18:44
morganfainbergmarekd, https://github.com/openstack/keystone/blob/master/keystone/common/sql/migration_helpers.py#L142-L18118:44
marekdmorganfainberg: ok, i will add a docstring18:45
morganfainbergso i think we could make that code in marco's patch better by dropping the FK constraints and, fixing the table, and re-adding the constraints18:45
morganfainbergrather than recreating the tables18:45
morganfainbergless data mangling involved18:45
marekdthis need to be done all today?18:46
morganfainbergmarekd, that is a bug18:46
morganfainbergthat can happen anytime it lands18:46
morganfainbergthe dependant BP can't land until afterwards and might be FFE *or* just pushed until liberty18:46
morganfainbergso i'd say fix the bug, ask for FFE if we want that in kilo18:47
marekd++18:47
morganfainbergbut start with the bug fix, which can land anytime before rc [sooner *is* better]18:47
morganfainberganything else?18:48
*** ijw has quit IRC18:48
morganfainbergbefore we close up the meeting and let infra have the channel early?18:48
marekdhow do i ask for FFE? ml-thread?18:48
marekdwith some explanation18:48
morganfainbergmarekd, yeah18:48
morganfainbergwhy this should land in Kilo, why it wasn't able to land before FF, what the status of the code is18:49
morganfainbergetc18:49
marekdsure.18:49
morganfainbergok enjoy your spare 10minutes!18:49
morganfainberggo get a cup of coffee :)18:49
henrynashmorganfainberg: remind me, do we ship python-keystoneclient with the serber or separately?18:49
morganfainbergjamielennox, you probably need the coffee18:49
henrynash(server even)18:49
morganfainberghenrynash, separate, but we try and do a final release around RC18:49
jamielennoxmorganfainberg: i could have stayed in bed :)18:49
*** SumitNaiksatam has joined #openstack-meeting18:50
henrynashmorganfainberg: ok18:50
morganfainbergthat is the releasr that ships with the named integrated release18:50
marekdjamielennox: it's....4am now?18:50
morganfainbergalso expect a new ksm / ksc to go out shortly into march here18:50
jamielennoxno, nearly 6 - sydney time now18:50
morganfainbergi'll be bugging people for ksc reviews and ksm stuff if we have something to release.18:50
morganfainbergpost k3 that is18:50
morganfainbergthanks everyone!18:50
morganfainberg#endmeeting18:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:50
openstackMeeting ended Tue Mar  3 18:50:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-03-18.01.html18:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-03-18.01.txt18:51
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-03-03-18.01.log.html18:51
*** sicarie has left #openstack-meeting18:51
*** lhcheng has left #openstack-meeting18:51
*** AJaeger_ has joined #openstack-meeting18:53
*** achanda has quit IRC18:57
*** Sukhdev has joined #openstack-meeting18:57
*** achanda has joined #openstack-meeting18:57
tchaypoWoo18:58
GheRiveroo/18:58
*** amakarov is now known as amakarov_away18:58
*** yamahata has quit IRC18:59
*** tiswanso has quit IRC18:59
*** SridharRamaswamy has joined #openstack-meeting18:59
*** yamahata has joined #openstack-meeting18:59
*** Tross has quit IRC18:59
jeblairhowdy infra folks19:00
pleia2o/19:00
nibalizero/19:00
*** lazy_prince has quit IRC19:00
mrmartino/19:00
clarkbhi19:00
mmedvedeo/19:00
ianwo/19:00
asselino/19:00
AJaeger_o/19:00
TheJuliao/19:01
jeblair#startmeeting infra19:01
*** tiswanso_ has joined #openstack-meeting19:01
openstackMeeting started Tue Mar  3 19:01:10 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
jeblairi'm listening to mordred speak at the board meeting right now, so i expect limited input from him...19:01
anteayao/19:01
* jeblair turns down the volume19:01
timrco/19:01
greghaynesO/19:01
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-02-24-19.01.html19:01
jeblair#topic Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:01
jeblairmordred create openstackinfra account on puppetforge19:01
*** yassine has quit IRC19:01
jeblairso, anyone know if that happened? :)19:02
anteayaI do not19:02
*** bswartz has joined #openstack-meeting19:02
jesusauruso/19:02
jeblairyes it has!19:03
anteayayay19:03
*** marcusvrn has joined #openstack-meeting19:03
jeblairthe password is recorded in hiera19:03
*** changbl has quit IRC19:03
nibalizerwoot19:03
jeblairso we can proceed with publishing our puppet modules via that account19:03
*** SridharRamaswam1 has joined #openstack-meeting19:03
jeblairnibalizer: i think that means a bunch of little patches to each of the puppet repos, right?19:04
*** SridharRamaswamy has quit IRC19:04
nibalizercouple things19:04
krtayloro/19:04
nibalizerwe need to manually create the module on the forge web app, and we need to enable the publishing job on each of the modules19:04
nibalizerI think the metadata.json in each of our modules is good enough that we don't have to make changes there19:05
nibalizerwe shall see19:05
anteayacan we decide on a module to test this workflow?19:05
jeblairnibalizer: okay, how about we work through one of the modules first, then go from there19:05
nibalizersounds good19:05
*** browne has joined #openstack-meeting19:05
jesusaurus++19:05
jeblairhttp?19:05
nibalizeri nominate openstackinfra-httpd19:05
jeblairnibalizer: excellent ;)19:05
nibalizeroh, yes, if we're changing to openstackinfra then we need a small change to each module19:05
jeblair#action jeblair nibalizer work through openstackinfra-httpd publishing19:06
*** noelbk has quit IRC19:06
jeblair#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
*** BharatK has quit IRC19:06
jeblairso one thing i was thinking we should do to streamline the priority efforts part of this is to nominate a gerrit topic for each effort and use that for all related changes19:07
jeblairwe've been doing this partially and ad-hoc recently....19:07
anteayaoh I like that19:07
jeblairand asselin actually put that in some of his specs19:07
*** joesavak has quit IRC19:07
jeblairwhich i also think is a good idea19:07
jesusaurusthat makes a lot of sense19:07
*** joesavak has joined #openstack-meeting19:07
jeblairso maybe as we go through these today, let's pick a topic, and i'll make sure it's in the wiki for reference19:07
asselincool. I can add that to the spec template then19:07
jeblairasselin: ++ thanks19:07
jeblair#topic Priority Efforts (Swift logs)19:08
*** openstack changes topic to "Priority Efforts (Swift logs) (Meeting topic: infra)"19:08
*** noelbk has joined #openstack-meeting19:08
*** andreykurilin_ has quit IRC19:08
*** jtomasek has quit IRC19:08
jeblairit looks like "enable_swift" is being used as a topic for this19:09
clarkbI got the concurrent swift uploads change merged and onto our images. d-g log uploads take ~2 minutes now which is much better than before19:09
*** jsavak has joined #openstack-meeting19:09
jeblair#info Gerrit topic: enable_swift19:09
*** pcrews has joined #openstack-meeting19:09
jeblairclarkb: how does that compare to scp?19:09
jeblair#link https://review.openstack.org/#/q/status:open+topic:enable_swift,n,z19:10
clarkbjeblair: they are about equal now. I think scp may take a bit longer actually19:10
clarkbthough scp is doing all the uploads serially so could be made faster if necesary19:10
*** browne has left #openstack-meeting19:10
jeblairso it seems like there should be no reason to hold off on approving those changes to start rolling this out more widely19:11
jeblairyeah?19:11
anteayaI don't have a reason to hold off19:12
AJaeger_go for it!19:12
clarkbya I think we can start making it more widely available19:12
clarkbthere is a change to support globbing though we will need that for some of the jobs iirc19:12
*** joesavak has quit IRC19:13
jeblair#link https://review.openstack.org/#/c/158514/19:13
jeblaircool, so let's land that, then continue19:13
*** tomoe_ has joined #openstack-meeting19:13
jeblair#topic Priority Efforts (Nodepool DIB)19:13
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:13
*** egallen has quit IRC19:13
jeblairlooks like 'dib-nodepool' is being used here, at least partially19:13
*** Rockyg has joined #openstack-meeting19:14
jeblair#info Gerrit topic: dib-nodepool19:14
jeblair#link https://review.openstack.org/#/q/status:open+topic:dib-nodepool,n,z19:14
jeblairthough nothing there atm19:14
clarkbnext steps are fungi's bindep change to condense the number of images we need and the move of nodepool to using shade19:15
clarkbboth are in progress but not quite ready aiui19:15
jeblairah, and we should also see about adopting bindep into infra19:15
*** topol has quit IRC19:15
anteayaI asked about that19:15
jeblairhow was the reception?19:15
anteayaneither fungi or lifeless wanted to move forward on that19:15
anteayathe reception was a decided meh19:15
*** markstur has joined #openstack-meeting19:15
anteayaso I left it19:15
jeblairoh, i thought lifeless was okay with it?19:16
anteayaif you want it, I can write the patch19:16
anteayaoh no obstacle19:16
tchaypodoes “wanted to move forward” mean they didn’t want to spend the effort personally19:16
anteayathey jsut weren't going to do the work or support me if I did19:16
tchaypoor did they think it was a bad idea?19:16
*** amitgandhinz has quit IRC19:16
anteayaneight thought it was a bad idea19:16
anteayaor a good one19:16
anteayasince it wasn't mine to decide I walked away at that point19:17
anteayaif you want it jeblair I can write the patch19:17
*** tomoe_ has quit IRC19:17
jeblairi think it's a good one since right now, there is only one core reviewer (who is not particularly engaged), and we're talking about making this a fairly important piece19:17
jeblairso i think we can give it a good home :)19:17
anteayathat was my thinking19:17
anteayawith your support, I will compose the patch19:18
anteayafeel free to toss me an action item to that effect19:18
jeblairsounds good19:18
anteayaor shall I?19:18
jeblair#action anteaya write patch to have infra adopt bindep; lifeless would remain in bindep-core, infra-core would be added; ask lifeless to review19:19
anteayawill do, thanks19:19
jeblairany other nodepool-dib things to discuss?19:19
jeblair#topic Priority Efforts (Migration to Zanata)19:20
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:20
*** radez_g0n3 is now known as radez19:20
*** VW_ has quit IRC19:20
pleia2so, we made some progress this week on the module19:20
jeblair#info Gerrit topic: zanata19:20
mrmartinI had a quick review on the new patch19:21
jeblair#link https://review.openstack.org/#/q/status:open+topic:zanata,n,z19:21
mrmartinso it has better dependencies now, but I still need to allocate some time for testing19:21
pleia2and I realized I needed more help, so I'm meeting with cinerama tomorrow in person to get her up to speed with it (she's got a vagrant VM with the puppet stuff to test so far, woo)19:21
anteayacongrats pleia2 on having a unique one work gerrit topic19:21
jeblairpleia2, mrmartin: that's excellent news!19:21
pleia2StevenK has also signed up to get the zanata client packaged19:21
*** dim_ has joined #openstack-meeting19:21
mrmartinpleai2: would you like to share this vagrant somewhere?19:21
pleia2mrmartin: you'll want to talk to cinerama19:22
mrmartinI also have some vagrant scripts under the hood19:22
pleia2I don't have it :)19:22
*** fawadkhaliq has quit IRC19:22
mrmartinpleia2: I can put this out somewhere (github) and later we can merge it into the puppet module19:22
pleia2mrmartin: I think that would be helpful19:22
mrmartinbecause actually it is not nice, but works some way :)19:22
jeblairthat's our motto!19:22
*** chandankumar has quit IRC19:23
*** amrith is now known as _amrith_19:23
pleia2I have been working with cloud VMs, but since there's now two people using vagrant to test it makes more sense to share19:23
anteayathat's our motto?19:23
* anteaya takes notes19:23
pleia2so with the client packaging we're now trying to push forward on more fronts than just the puppet+server thing, which is good19:23
pleia2that's all :)19:24
jeblairthat's great!19:24
jeblair#topic Priority Efforts (Downstream Puppet)19:24
*** openstack changes topic to "Priority Efforts (Downstream Puppet) (Meeting topic: infra)"19:24
mrmartinyou can use vagrant with cloud vm19:24
jeblairthere were two specs for this, both approved now19:24
pleia2great19:24
jeblair#link https://review.openstack.org/#/c/137471/19:24
jeblair#link https://review.openstack.org/#/c/139745/19:25
*** markstur has left #openstack-meeting19:25
*** VW_ has joined #openstack-meeting19:25
jeblairhow about 'downstream-puppet' for a topic?19:25
jeblairor openstackinfra-puppet?19:25
jeblairor perhaps openstackci-puppet?19:26
anteayaI vote for downstream-puppet19:26
jeblair#info Gerrit topic: downstream-puppet19:26
nibalizercool19:26
*** jorge_munoz has left #openstack-meeting19:26
nibalizeroh cool these have merged19:26
nibalizerill spin up an example implementation of 137471 this week19:27
jeblairoh19:27
jeblairactually the spec said "openstackci" as a topic19:27
nibalizerhardly specific, taht19:28
anteayajeblair: okay19:28
anteayawhat the spec said19:28
* asselin pays attention19:28
jeblairmaybe let's change the spec19:28
jesusaurusi like downstream-puppet as a topic19:29
jeblairi'll do that19:29
asselinthere are 2 specs. same topcic for both?19:29
*** whenry has quit IRC19:29
anteayaasselin: yeah, so we can address them in the same meeting topic19:29
jeblairasselin: i think so -- i think they are related enough that i'd like to treat them as one effort and try to get the same people reviewing them at the same time19:29
*** whenry has joined #openstack-meeting19:30
asselinok, no objection. just to be clear.19:30
jeblairi could be wrong about that, and if so, we can split it up later, but i think it's worth trying :)19:30
asselin+119:30
jeblairasselin: so is step 1 to create the new repo?19:31
asselinyes19:31
*** rajeshr has quit IRC19:31
jeblairsounds good.  anything else to help get these started?19:31
*** jckasper has joined #openstack-meeting19:32
*** aranjan has joined #openstack-meeting19:32
anteayajeblair: write the govenance patch?19:32
asselinI think we can start with that19:32
jeblairanteaya: yeah, all part of 'create the repo' now :)19:32
jeblair#topic Priority Efforts (Askbot migration)19:32
*** openstack changes topic to "Priority Efforts (Askbot migration) (Meeting topic: infra)"19:32
anteayaokay19:32
mrmartinfor askbot, I assigned the tasks for storyboard to track progress: https://storyboard.openstack.org/#!/story/200015819:33
jeblair#info Gerrit topic: askbot-site19:33
jeblairmrmartin: yay! thanks! :)19:33
*** Mandell has quit IRC19:33
mrmartinand and wrote some additional info to spec required for migration: https://review.openstack.org/16069319:33
mrmartinand that's all, if https://review.openstack.org/140043 gets an approval, than19:34
jeblair#link https://review.openstack.org/#/q/status:open+topic:askbot-site,n,z19:34
*** sdake_ has joined #openstack-meeting19:34
mrmartinsome involvment required from a core member, because most of the tasks requires some manual work19:34
jeblairthat has a +2 from me, needs another infra-core to aprv19:34
mrmartinlike instance launch, hiera setup, backup / recovery etc.19:34
jeblairmrmartin: yeah, once that lands, we'll find an infra-root to help with that19:35
mrmartinok, so shortly this is the status19:35
mrmartincan I do anything to move forward things?19:35
clarkbI will try to do spec review after cleaning up new gerrit server19:35
*** killer_prince has joined #openstack-meeting19:35
*** killer_prince is now known as lazy_prince19:35
jeblairfyi https://review.openstack.org/140043 is a system-config change to actually add the server19:36
*** ivar-laz_ has joined #openstack-meeting19:36
*** lsmola has quit IRC19:36
mrmartinok, so just a review of hiera variables required before approval19:37
jeblairmrmartin: if another infra-core hasn't reviewed it by the end of the week, let me know19:37
mrmartinok, thnx19:37
jeblair#topic Priority Efforts (Upgrading Gerrit)19:37
*** openstack changes topic to "Priority Efforts (Upgrading Gerrit) (Meeting topic: infra)"19:37
jeblairpleia2: did you set up the netcat?19:37
*** ijw has joined #openstack-meeting19:38
clarkbno, pleia2 doesn't have a user on the system yet do to a puppet race during user creation that led to groups being wrong and overlapping for some users in bad ways19:38
clarkbI am going to fix that after the meeting19:38
pleia2thanks clarkb :)19:38
jeblairoh ok.  so real soon now.  :)19:38
pleia2yep19:38
jeblair#action pleia2 set up netcat hello-world on new gerrit port 2941819:38
jeblairwe should probably defer discussion of the upgrade date until next week19:39
jeblair#info april 11 and may 9 suggested as gerrit upgrade dates19:39
jeblair(just continuing that from last time)19:39
anteayaagreed would be nice to pick a time fungi can participate19:39
*** ivar-lazzaro has quit IRC19:39
clarkbjeblair: you don't have a user either :P19:39
jeblairzaro: anything else?19:39
*** AmirBaleghi13 has joined #openstack-meeting19:39
jeblairclarkb: you don't know what a relief that is19:40
pleia2haha19:40
jeblair#topic Governance changes (jeblair)19:40
*** openstack changes topic to "Governance changes (jeblair) (Meeting topic: infra)"19:40
jeblair#link https://review.openstack.org/#/c/159936/ Remove py26 add py34 to PTI19:41
jeblair#link https://review.openstack.org/#/c/159935/ Remove reference to Jenkins19:41
jeblair#link https://review.openstack.org/#/c/159930/ IRC channel policies19:41
jeblairthese are all probably worth a look and of some interest to infra folks19:41
*** dteselkin_ is now known as dteselkin19:41
jeblairthe first two are quite trivial19:41
*** dim_ has quit IRC19:41
jeblairthe third i wrote at the request of the tc in response to the recent community thread...19:42
nibalizerjeblair: are you going so far as to set the 'on join' message in chanserv?19:42
jeblairi think a lot of folks think that it would be simplest/best if all the irc channels are logged19:42
jeblairso that's a resolution to have the tc say that they think it should be the case19:42
anteayaI agree with the patches as written19:42
*** ijw has quit IRC19:42
jeblairand i've written somewhat vaguely so that we have some discretion about how to implement it19:42
anteayaI'm for vague at this point19:43
jeblairi think at a minimum we should enforce logging in project-config (could probably make it a gate check, but at least a human check for now)19:43
anteayasince more detail just means more policing/follow up for us19:43
jeblairand yes..19:43
jeblairnibalizer: i think we should also do on join messages, and possibly figure out a way to get the log location into all the topics automatically19:43
AJaeger_jeblair: in project-config? Logging is configured in system-config19:43
anteayayeah that statement lost me as well19:44
jeblairAJaeger_: ha, indeed.  :)19:44
*** cinerama has joined #openstack-meeting19:44
anteayaI thought we were discussing logging of irc channels19:44
*** barclaac has quit IRC19:44
* AJaeger_ cleaned up recently channels so that all channels in gerritbot get accessbot as well - that's one part of the story19:44
anteayaAJaeger_: nice job19:45
AJaeger_there're a couple of review - and I've learned from clarkb to check this during reviews ;)19:45
*** ijw has joined #openstack-meeting19:45
jeblairi'm hoping to fix the fact that logging is not in project-config, but i don't have a plan written up yet, sorry.19:45
anteayaah now I can follow that statement19:45
jeblairso yeah, we may need to do some cross-checking for a while19:45
AJaeger_jeblair: once we move it over, we could gate that a channel is configured in all three places19:45
*** khaldrogox has quit IRC19:46
anteayado we care about channels that use openstack- but aren't represented in project-config in any way?19:46
jeblairAJaeger_: yeah.  i'm hoping to make one config file19:46
AJaeger_jeblair: What's the order? Merge in project-config only if change has been proposed for system-config?19:46
anteayaor system-config either19:46
jeblairAJaeger_: that sounds like a good starting point19:47
*** amitgandhinz has joined #openstack-meeting19:48
jeblairand we'll work on making it simpler19:48
* AJaeger_ reviews proposed changes again...19:48
jeblairAJaeger_: heh, we could wait until the governance change lands before we start enforcing it19:49
*** lsmola has joined #openstack-meeting19:49
jeblair#topic Infra-cloud (jeblair)19:49
*** openstack changes topic to "Infra-cloud (jeblair) (Meeting topic: infra)"19:49
*** ijw has quit IRC19:49
jeblairso i briefly linked to the artifacts from this last week, but we ran out of time19:49
*** cebruns has quit IRC19:49
*** MaxV has joined #openstack-meeting19:49
jeblair#link summary email https://etherpad.openstack.org/p/kBPiVfTsAP19:50
jeblair#link story https://storyboard.openstack.org/#!/story/200017519:50
jeblair#link etherpad https://etherpad.openstack.org/p/InfraCloudBootcamp19:50
jeblairthis is just getting started, but i think the next step here is to write up the design documentation based on what we talked about in person19:50
jeblairand get that up for review19:50
jeblairis anyone interested in doing that?19:51
*** Tross has joined #openstack-meeting19:51
anteayayou would need someone from the in person meeting to do that, yeah?19:51
jeblairanteaya: it would make the most sense.  there's a lot of detail captured on the etherpad, but they would have more context to tie it together and fill in blanks19:51
tchaypoInterested, but wouldn’t be able to start on it until about the 16th, which is going to be almost a month after the midcycle19:52
AJaeger_will that cloud be accessable for translators and documentation as reference?19:52
pleia2re: Bikeshedding about ansible and puppet <-- did we actually decide?19:52
pleia2installing and maintaining openstack is hard :)19:52
greghaynesheh, you dont have to tell the tripleoers that19:52
tchaypopleia2: from memory, that wasn’t a “which should we use?” discussion, it was a “how do they mesh?” discussion19:52
jeblairpleia2: i think the consensus was strongly in favor of using the openstack puppet modules from stackforge19:52
pleia2greghaynes: yep, that's where I got my experience19:53
tchaypowith perhaps a bit of ansible to kick off puppet runs19:53
tchaypoand orchestrate things19:53
jeblairtchaypo: right19:53
jeblairwhich is the general direction we're already heading19:53
pleia2jeblair: so I spoke with crinkle about the puppet modules over the weekend (unrelated) and puppet-openstack isn't really a thing anymore, you sort of cobble together your own central openstack module and pull in the nova, neutron, etc19:53
jeblairAJaeger_: not sure i understand the question19:53
crinkleI don't recall in-depth discussion on puppet vs ansible, would like to see that hashed out a bit19:53
zaroo/19:53
pleia2crinkle: ++19:54
AJaeger_jeblair: the translation team has setup a "reference server" so that translators can look at horizon and figure out where and how strings are used and then write the proper translation19:54
AJaeger_Suchc a reference would be usefull for documentation sometimes as well.19:54
greghaynescrinkle: ++ - I think we also had some false assumptions about the state of ansible openstack deploy tooling (which I discovered after playing with them this week). Maybe an ML thread is in order19:54
jeblairpleia2: makes sense; i imagine we will have machines that use the nova module, others that use glance, etc...19:54
annegent_AJaeger_: ++19:55
pleia2anyway, I'd like to be involved with this19:55
AJaeger_So, my question is whether translators and documentation writers will be able to access the cloud - or whether that's something totally different?19:55
pleia2but I wasn't at the in person meeting, so maybe someone else leads here19:55
jeblairAJaeger_: it's not our primary goal, but if we get it up and running, perhaps we can figure out a way to do that later on.  it's a good idea.19:55
annegent_AJaeger_: jeblair: I often use Trystack and saw a similar possibility here.19:56
jeblairpleia2: i want you to be as well :)19:56
tchaypoWhat would translators and doc writers want to do in the cloud?19:56
tchaypo(I’m not questioning why they’d get access, I’m wanting to make sure we’re clear about how it would be useful so we can keep that in mind as we design)19:56
mrmartintchaypo: testing use cases?19:56
pleia2tchaypo: checking the state of translations in the horizon interface, how complete they are from a UI perspective19:57
AJaeger_tchaypo: see http://docs.openstack.org/user-guide/ - that guide has a horizon section19:57
AJaeger_Documentation editors need to verify that19:57
jeblairgreghaynes: i'd like to get a proposal written up first before we start a list thread on something like that19:57
AJaeger_And translators see a random string in horizon and need to figure out how to translate it19:57
*** eharney has quit IRC19:57
*** jorge_munoz_ has joined #openstack-meeting19:57
jeblairgreghaynes: let's have a think we can specifically point to and change19:57
annegent_tchaypo: for checking if horizon changed release-to-release19:57
AJaeger_tchaypo: best to reach out to the openstack-i18n list19:57
tchaypowould they be wanting “go build a horizon for me with this new patchset” access, or just “let me see a recent horizon"19:57
annegent_tchaypo: six month releases only19:58
AJaeger_tchaypo: current horizon19:58
annegent_tchaypo: otherwise I have to run a devstack on stable/release branches19:58
tchaypookay19:58
greghaynesjeblair: Agreed, theres also a lot of things to do before we get to a point where we need to decide too19:58
annegent_tchaypo: just to see the dashboard19:58
tchaypothanks :)19:58
AJaeger_tchaypo: the i18n team just deploys head daily AFAIK19:58
annegent_tchaypo: thanks for asking about the use case :)19:58
*** MaxV has quit IRC19:58
pleia2jeblair: design documentation == spec?19:59
jeblairpleia2: normally i would say yes, however, in this case i think we could actually just write the documentation patch for system-config...19:59
*** MaxV has joined #openstack-meeting20:00
jeblairi think that will save some effort in the long run20:00
jeblairwe can treat it like a spec in that we don't have to approve it until we agree that the documentation matches what we want :)20:00
*** MarkAtwood has quit IRC20:00
pleia2makes sense20:00
tchaypoI’ve added a note to the bottom of https://etherpad.openstack.org/p/kBPiVfTsAP summarsing what I understand of what we just said20:00
tchaypofeel free to make what I wrote match reality if it’s wrong20:01
*** jorge_munoz_ has quit IRC20:01
jeblairanyway, we have failed to get a volunteer for this.  i will move on to alternate means unless someone pings me in channel.  :)20:01
jeblairtime's up, thanks all20:01
jeblair#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
openstackMeeting ended Tue Mar  3 20:01:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-03-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-03-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-03-03-19.01.log.html20:01
ttxHola!20:01
devanandao/20:01
ttxAnyone here for the TC meeting ?20:01
markmcclaino/20:01
ttxWe have a number of members half-present due to concurrent board meeting20:02
russellbo/ (but distracted by board meeting)20:02
dhellmanno/20:02
*** otter768 has joined #openstack-meeting20:02
annegent_here20:02
jeblairi would feel okay if we did not meet quorum under the circumstances...20:02
ttxjgriffith, mikal, mordred, vishy, jaypipes, sdague : around ?20:02
vishyo/ here but also in the board meeting20:03
jgriffith0/20:03
ttxwe have quorum already20:03
sdagueo/20:03
ttx#startmeeting tc20:03
annegent_no one else wrote such an eloquent rsvp as mikal20:03
openstackMeeting started Tue Mar  3 20:03:17 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
*** tchaypo has left #openstack-meeting20:03
*** pcrews has left #openstack-meeting20:03
*** dboik_ has joined #openstack-meeting20:03
ttxI must admit that was an eloquent absence note20:03
ttxOur agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:03
ttx#topic openstack-specs final rubberstamping20:04
*** openstack changes topic to "openstack-specs final rubberstamping (Meeting topic: tc)"20:04
jeblaircan i put forward a motion to postpone the meeting?20:04
*** VW_ has quit IRC20:04
*** joesavak has joined #openstack-meeting20:04
*** SridharRamaswam1 has quit IRC20:04
*** tiswanso_ has quit IRC20:04
dhellmannjeblair: grounds?20:04
jeblair20:02 < ttx> We have a number of members half-present due to concurrent board meeting20:04
ttxjeblair: err... I guess? But next week is the ops summit which a few of us will attend as well20:04
ttxjeblair: even counting half-present memebrs as absent we do have quorum though20:05
*** VW_ has joined #openstack-meeting20:05
*** dboik_ has quit IRC20:05
ttxeven if we don't count you20:05
*** ChuckC has quit IRC20:05
annegent_quorum is quorum is quorum20:05
jeblairokay.  i just wanted to throw it out there for discussion.20:05
*** ivar-laz_ has quit IRC20:05
*** tiswanso_ has joined #openstack-meeting20:06
jeblairi see how it is, thanks20:06
* russellb certainly ok with skipping, but biased20:06
dhellmannperhaps we can try to avoid this sort of overlap in the future20:06
*** ivar-lazzaro has joined #openstack-meeting20:06
*** matrohon has joined #openstack-meeting20:06
*** jsavak has quit IRC20:06
ttxdhellmann: it's not as if that meeting occurred at this hour for the first time20:06
dhellmannI'd be ok with skipping, but I'm not sure we want to go 2 weeks without meeting20:06
dhellmannttx: do we have anything pressing?20:06
jgriffithsilly BOD, they know when we meet :)20:06
markmcclainjeblair: is there something on the agenda that perhaps we should delay if we feel that slim quorum is not representative enough for discusssion?20:06
ttxdhellmann: well, I'd like to make progress on a number of items, yes, especially if we skip next week20:07
jeblairmarkmcclain: perhaps not20:07
russellbwhat's next week20:07
ttxrussellb: ops summit20:07
russellbah20:07
dhellmannttx: yes, and to be fair the folks on both committees could have raised that but we are where we are so I'm ok with discussing a delay20:07
ttxI think we have things to rubberstamp and we don't really need all members 100% attention to so that20:07
*** otter768 has quit IRC20:07
ttxwe have quorum so I'd prefer if we proceeded20:08
dhellmannttx: sure, let's do the easy things first :-)20:08
jeblairokay.  i'm okay with meeting today and next week.20:08
ttxso, rubberstamping20:08
ttxjeblair: if there is anything you think where the decision should be postponed, I'm fine doing thatr20:08
ttxBut I seriously doubt there will be20:08
jeblairttx: sounds like a plan20:08
ttx* Add TRACE definition to log guidelines (https://review.openstack.org/#/c/145245)20:08
ttxI'd say this one has reached consensus and can be approved.20:08
*** rbowen has quit IRC20:09
ttxfeel free to pile up a few more +2s20:09
ttxwe have 6 if sdague posts his20:09
*** MaxV has quit IRC20:10
sdaguettx: well I wrote it20:10
ttxand 7 if markmcclain reposts his20:10
sdagueso it seems rude to +220:10
markmcclaindone20:10
*** MarkAtwood has joined #openstack-meeting20:10
*** liusheng has quit IRC20:10
dhellmannsdague: I think your +2 is assumed there :-)20:10
*** egallen has joined #openstack-meeting20:10
ttxAny last votes or comments before I +1 it ?20:10
*** liusheng has joined #openstack-meeting20:11
ttxok, approved20:11
*** e0ne has joined #openstack-meeting20:11
ttx#topic Definition of the release:* tags20:11
*** openstack changes topic to "Definition of the release:* tags (Meeting topic: tc)"20:11
ttx#link https://review.openstack.org/15732220:11
ttxSo.. there are divergent views on what the tags should be named, and I'd like to converge on one20:11
ttxOriginal proposal was release:common, release:coordinated, release:compatible, release:free20:11
ttxannegentle suggested release:independent instead of release:free20:11
annegent_ttx: jaypipes asked about audience, downstream or upstream priority would be a good discussion to have here20:11
ttxI agree with that and pushed a new patchset with it20:12
ttxannegent_: getting to it20:12
annegent_ttx: ok cool20:12
ttxdevananda suggested release:managed instead of release:coordinated20:12
ttxI also agree with that20:12
annegent_+1 on that too20:12
ttxdevananda / notmyname suggested we change release:common to something more descriptive or that doesn't imply majority share or anything20:12
* notmyname lurks20:12
ttxYesterday jaypipes suggested we switch from a release model category approach (where you belong to only one) to an release model attribute approach (where you can combine multiple attributes)20:12
*** SridharRamaswamy has joined #openstack-meeting20:12
ttxrelease-managed, release-periodic-6mo, release-with-milestones, release-independent20:12
ttxSome of the one-liner proposed definitions for them appear to be exclusive while they are not meant to, so they probably need a bit of work20:13
ttxI would also rename "with-milestones" to "with-shared-milestones" or "standard-cycle" or something, since that's the only milestones we currently have20:13
ttxannegent_: to answer your question, I think they should be used primarily downstream20:13
*** MaxV has joined #openstack-meeting20:13
jgriffithttx: so thoughts on dhellmann 's proposal for synchronzied vs jaypipes 's changes?20:13
annegent_I like that rename too. -with-shared-milestones probably slightly better for the avoidance of "value" in "standard"20:14
ttxbut they should be precise enough so that upstream can use them to describe or organize their work too20:14
* dhellmann wonders if it wouldn't be simpler to just let projects describe their release process in their own projects20:14
jgriffithdhellmann: +120:14
jgriffithdhellmann: but you'd have to have consistent tags IMO20:14
ttxdhellmann: that would make my job a bit difficult20:14
ttxI need to put projects into buckets, I handle a lot20:15
dhellmannttx: in what way? just communicating downstream?20:15
dhellmannah20:15
*** jsavak has joined #openstack-meeting20:15
*** adalbas has quit IRC20:15
devanandadhellmann: + to describing how their teams work, - to not having any consistency across projects when it comes to release cadense20:15
ttxI need to remember which one I handle, which ones use which model20:15
devanandadhellmann: this also informs distro packagers in a significant way20:15
*** hareeshp has quit IRC20:15
ttxHow do you all feel about an attribute based approach vs. a model based approach ?20:16
ttxi.e. jaypipes AND style rather than my OR style20:16
jgriffithttx: can you expand just a little20:16
dhellmanndevananda: this goes back to my argument that we don't need a lot of these tags at all if we just go write things down in documentation20:16
ttxjgriffith: so my approach was to dscribe a set of release models and ask projects to pick20:16
*** hareeshp has joined #openstack-meeting20:16
ttxI would have one tag per model20:17
devanandattx: I can see benefits to both, but I'm still leaning towards the OR style20:17
annegent_I think AND style is pretty accurate.20:17
annegent_does put some cognitive burden on the tag reader20:17
ttxJay's approach is to describe attributes of release models (like "does a release every 6 months")20:17
dhellmannttx: are there a set of tags using Jay's approach that would meet your needs for bucketing?20:17
ttxand then let projects dsecribe what they do by combining those attributes20:17
jgriffithttx: so I'm always a sucker for the simpler approach that still works20:18
ttxdhellmann: I need to chefck that all the combinations are a supportable bucket :)20:18
jgriffithttx: in other words IMHO the OR model is a bit more clear and still gives benefit20:18
*** joesavak has quit IRC20:18
ttxjgriffith: I'd not sure which is simpler, tbh20:18
annegent_I think docs has a similar bucketing need20:18
jgriffithttx: well, only in terms of "me" having it in my head :)20:19
ttxI'm fine taking Jay's proposal and checking that it works, and proposing definitions for those20:19
*** AJaeger_ has left #openstack-meeting20:19
dhellmannif we can identify the facets, the AND style seems simpler but if it produces combinations we don't want to support maybe that's reason enough to stick with OR20:19
ttxjust want to make sure that's your preferred solution20:19
*** sdake_ has quit IRC20:19
notmynamettx: how is your tag bucket method (OR) different than "integrated" "incubated" etc?20:19
ttxdhellmann: we could also describe exceptions to the OR rule20:19
devanandattx: I could see a project needing to have 3 of those 4 tags though20:19
notmynamethe AND method allows for more precise descriptions and flexible buckets20:20
jgriffithdevananda: that's where things get convoluted for me20:20
ttxrelease-with-milestones and release-independent are exclusive for example20:20
jgriffithbut that could be just me20:20
*** topol has joined #openstack-meeting20:20
devanandattx: no they're not?20:20
ttxdevananda: describe a project that would follow that ?20:20
notmynamejgriffith: aren't tags AND anyway? ie if there are multiple tags on a project, they are AND20:20
devanandattx: a project could release its own milestones independelty from the sycnrhonized cycle, not managed by you20:20
devanandattx: stackforge/ironic-discoverd20:21
notmynamejgriffith: IOW you'll always be composing tags in your head, even with the proposed OR release tags20:21
ttxdevananda: oh, I meant the with-shared-milestones renamed variant20:21
devanandaand python clients20:21
jgriffithnotmyname: sure, but I guess I might be viewing this wrong20:21
ttxdevananda: python clients do not follow milestones20:21
jgriffithnotmyname: the OR to me means "it's this one or that one"20:21
*** hareeshp has quit IRC20:22
devanandaah - of course20:22
jgriffithnotmyname: the AND means, there's this collection that all have different implications20:22
jgriffithnotmyname: and I have to decode what the end result means20:22
ttxdevananda: agree that you could invent a project that has milestones but not the shared ones20:22
ttxnot sure that would need a tag though (original-milestones)20:22
jgriffithmaybe not a big deal20:22
annegent_devananda: ttx: yeah it's the commonality that matters due to assuming integrated testing?20:23
jgriffithnotmyname: could be the I'm over-complicating it :)20:23
lifelessjeblair: I'm entirely happy with moving it20:23
lifelessbah, sorry20:23
ttxso what's your general feeling ? Should I scrap myu version and start again by iterating on  Jay's list20:23
ttx?20:23
devanandai think we have two (maybe more?) orthogonal dimensions here: who manages the release? how often are releases (and their related artefacts) tagged?20:24
*** Mandell has joined #openstack-meeting20:24
ttxdevananda: that sounds simpler, since we ahve a tag for describing that20:24
ttxrelease:managed means release management is handled by the release mgmt team20:24
ttxif you don't have the tag, then you do it yourself20:24
*** yassine has joined #openstack-meeting20:25
devanandawe don't need two sets of tags20:25
devanandait reduces to (A || B) && (C || D)20:25
ttxdevananda: ?20:25
dhellmannunder ttx's definition, release:managed implies some of the other settings, though20:25
ttxdhellmann: release:managed is the pet tag for the release management team describing projects we agree to handle20:26
dhellmannright, and those follow the 6 month cycle, use milestones, etc.20:26
*** radez is now known as radez_g0n320:26
ttxyes20:26
devanandarelease mgmt (manages || does not manage) the release && release is (synchronized || not synchronized)20:26
dhellmannso you wouldn't have a managed project not using milestones, but you might have an unmanaged project using them20:26
notmynametiming is differnet than releasing right? as devananda said20:26
*** jckasper has quit IRC20:26
notmyname*who is releasing20:27
dhellmannnotmyname: they are only separate if the release team is not managing the release, I think20:27
devanandadhellmann: right. of the 4 possible combinations, only 3 are actually sensible20:27
ttxnotmyname: in theory yes, in practice, no20:27
devanandadhellmann: and we dont need two sets of tags to represent that20:27
dhellmannright20:27
*** gyee has quit IRC20:28
*** kmartin has quit IRC20:28
devanandattx: I have convinced myself that we dont need the AND approach here20:28
*** lpeer__ has quit IRC20:28
jaypipessorry all, reading back...20:28
ttxdevananda: ah, interesting20:28
*** sbalukoff has quit IRC20:29
ttxdevananda: not sure how to proceed now. Whatever the direction I take, everyone seems to be unhappy20:29
devanandaheh20:29
devanandanames are hard20:29
*** e0ne is now known as e0ne_20:29
*** kebray has joined #openstack-meeting20:29
dhellmannttx, devananda : I think you want a combination. A project is either managed, or it gets to pick a la carte from the other tags20:29
*** e0ne_ has quit IRC20:30
devanandadhellmann: you'd have non-managed projects pick >1 tag to self-apply/20:30
devananda?20:30
ttxdhellmann: although I guess we should support the corner case that the relmgmt team can opt to support an outlier20:30
ttxheck, I did it for the last 4 years20:30
devanandadhellmann: that seems more confusing20:30
annegent_ttx: I think it's difficult not just for naming but for integrated release management being a limited resource?20:30
*** e0ne has joined #openstack-meeting20:31
*** sbalukoff has joined #openstack-meeting20:31
jaypipes"there's a tag for that" <-- new OpenStack motto.20:31
ttxdevananda: I don't think the AND approach (Jay's approach) is more confusing20:31
devanandattx: i meant the combination of OR + AND that i think dhellmann just proposed20:31
devanandaeither(release:managed) or(pick from list of other tags)20:32
ttxdevananda: consider handled-by-relmgt-team separately20:32
dhellmannhow about release:managed; release:periodic with attribute for period in months; release:independent (xor with release:periodic); release:uses-stable-branches20:32
ttxit is separate from the others20:32
* devananda ponders20:32
ttxnot sure what you mean by release:uses-stable-branches20:33
*** e0ne has quit IRC20:33
ttxcommon stable branches like the 6-month ones ?20:33
devanandadhellmann: so oslo would be release:independent + release:usesstable-branches ?20:33
dhellmannttx: some independent projects won't use stable branches20:33
dhellmanndevananda: right20:33
dhellmannI don't know if swift uses stable branches, but if not it would just be release:independent20:34
ttxdhellmann: I think it fails to describe the swift model20:34
ttxit's not really periodic but they releae at the end of the cycle20:34
jaypipesttx: that is periodic, no?20:34
dhellmannttx: so add release:synchronized to account for that case?20:34
dhellmannjaypipes: no, because they also release in between20:35
jaypipesdhellmann: ah.20:35
dhellmannswift might be release:independent, release:synchronized, release:uses-stable-branches20:35
dhellmannoslo would be release:independent, release:uses-stable-branches20:35
jaypipesdhellmann: what would release-synchronized denote?20:35
ttxI prefer Jay's list, tbh20:35
dhellmanna release at the end of a cycle20:35
* dhellmann shrugs20:36
dhellmannttx: nothing on jaypipes' list describes oslo20:36
ttxI'll think about it and propose a new one. jaypipes, dhellmann: I might get your a draft proofread20:36
dhellmannttx: sure20:37
jaypipesdhellmann: release:independent describes oslo projects, no?20:37
annegent_I think the cognitive overload is on independent AND synnchronized :)20:37
sdaguedhellmann: the stable branches for oslo are sort of an accident of our current test system though, right?20:37
ttxannegent_: I blame swift20:37
dhellmannjaypipes: we produce many releases during a cycle and one stable release at the end of each, so not realy20:37
ttx(as always)20:37
dhellmannsdague: no, we were doing them before this cycle20:37
sdaguedhellmann: right, but we weren't testing releases before this cycle20:38
sdaguethe libs were all from git20:38
dhellmannsdague: we were using alpha tags to avoid the problem that caps are  now being used to avoid20:38
*** achanda has quit IRC20:38
jaypipesdhellmann: gotcha. so perhaps release:periodic-6mo + release:as-needed?20:38
*** e0ne has joined #openstack-meeting20:39
dhellmannjaypipes: that 6month thing feels forced, but that's probably closer20:39
jaypipesdhellmann: /me trying to come up with a pithy way of denoting "releases versions of libraries as needed"20:39
ttx#action ttx to propose a new set of tags based on an release model attribute (AND) approach, and make sure that all projects can be acurately described in it20:39
*** timcline has quit IRC20:39
ttxLet's move on20:40
ttxAnd I thought those ones were piece of cake20:40
ttx#topic Other governance changes20:40
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:40
ttx* Add ironic-lib to Ironic program (https://review.openstack.org/157757)20:40
ttxWe have 7 YES here and I think we can overrule mikal's objection since it's been addressed in further comments20:41
*** AmirBaleghi13 has quit IRC20:41
*** kebray has quit IRC20:41
ttxso... approving after meeting unless someone else objects20:41
*** MaxV has quit IRC20:41
ttx* Add dib-utils as part of TripleO (https://review.openstack.org/158365)20:41
ttxThis one looks good to go, could use another +120:41
ttxapproving after meeting unless someone else objects20:42
ttx* Add mission statement for project 'Heat' (https://review.openstack.org/154049)20:42
ttxOne mission is better than no mission, so this one looks good to go too20:42
ttxIt has Heat PTL blessing, so will approve after meeting unless someone else objects20:42
ttx* Adding Piet Kruithof as Horizon ATC (https://review.openstack.org/154271)20:43
*** egallen_ has joined #openstack-meeting20:43
ttx8 YES &I think we can overrule mikal's objection here as well since it's been addressed in further comments20:43
ttxso will approve after meeting unless someone else objects20:43
*** yassine has quit IRC20:43
ttx#topic Housekeeping20:43
*** openstack changes topic to "Housekeeping (Meeting topic: tc)"20:43
ttxEven more intersting20:43
ttx* Build list of teams from YAML file (https://review.openstack.org/125788)20:43
ttxThis is rendering the teams list for governance.o.o, not really a TC decision. I'll approve this postmeeting as housekeeping, unless someone posts a valid -120:44
*** jecarey has quit IRC20:44
ttx* Update the Infrastructure project homepage URL (https://review.openstack.org/158371)20:44
*** mrda-away is now known as mrda20:44
jeblairi'm not opposed to this, but i sort of feel weird being the odd project out; i'd like to ask fungi more about his intent when he gets back from vacation20:44
*** MaxV has joined #openstack-meeting20:44
ttxThis one could use jeblair's +1, but since it's housekeeping i'll also approve it post-meeting unless there is an objection20:44
dhellmannthat sounded like an objection?20:44
ttxoh20:44
dhellmannor at least a request to have it tabled20:45
ttxI thought that was an objection on the Heat mission one20:45
jeblairyeah, can we table it?20:45
jeblairoh sorry20:45
ttxsure, no hurry20:45
jeblairwas suggesting tabling the infra homepage change20:45
*** MaxV has quit IRC20:45
ttxHeh, infra actually *has* a mission20:45
ttxjeblair: sure, no pb20:45
*** ijw has joined #openstack-meeting20:46
ttx#info tabling this one until we get PTL ack20:46
ttx* Improve the doc build process (openstack-specs) (https://review.openstack.org/#/c/156715/)20:46
ttxThis one is housekeeping on the openstack-specs repo, will approve unless somone objects20:46
ttx#topic Open discussion20:46
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:46
*** achanda has joined #openstack-meeting20:46
ttxI wanted to mention I don't get a lot of support from TC members to push the new governance model20:47
*** egallen has quit IRC20:47
*** egallen_ is now known as egallen20:47
zanebfun fact: the verb 'to table' has opposite meanings in English and American20:47
ttxI know we all have our battles, but I kind of hoped we'd get more tag definitions proposed20:47
dhellmannttx: did you have some other tags in mind?20:48
ttxdhellmann: well, Jay had a very long list20:48
jeblairttx: i was also wondering what's next for the change20:48
*** VW_ has quit IRC20:49
ttxI'll work with Ops to make progress on maturity-description tags20:49
ttxjeblair: I think we need to continue to decontruct the various meanings of integrated-release into separate tags20:49
devanandattx: I'll be happy to work with you on some more tags20:49
ttxSo what does integarted-release currently mean ?20:49
ttxIt does mean released-together, and we have a thread to cover that20:49
jeblairttx: it looks like most of the work items in http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html are largely complete, except for tag related things20:50
ttxIt does mean tested-together20:50
jaypipesttx: sorry mate, I can try to submit some tag definitions in the next week or so. Apologies, I've been so swamped with other stuff :(20:50
ttxIt does mean kind-of-mature20:50
devanandattx: in particular, I'm interested in tags around the layers that mordred and I have talked about previously, but I haven't tried to write them up formally yet20:50
ttxIt does mean kind-of-produced-the-openstack-way20:50
*** asalkeld has joined #openstack-meeting20:50
ttxwe cover "kind-of-produced-the-openstack-way" with the new project teams requirements20:50
dhellmannttx: "mature" is too subjective and "openstack-way" is still a rule for all projects, right?20:50
dhellmanndevananda: the layers can be discovered by looking at the test matrix, can't they? do we need tags for those?20:51
ttxdhellmann: sure "mature" (or "stable") is too subjective20:51
ttxdhellmann: My plan is to reach out to ops tand see how we could describe that20:51
jogodhellmann: yeah I don't think we need 'formal' tags for layers20:51
*** ijw has quit IRC20:51
*** mrmartin has quit IRC20:51
annegent_is anyone at the ops meetup to test usability of tags?20:51
devanandadhellmann: the test matrix is evolving currently. in an ideal world, yes, it could be discovered from that, though I think having tags to self-describe is helpful20:52
annegent_next week I think?20:52
*** MaxV has joined #openstack-meeting20:52
zanebdhellmann++20:52
dhellmannttx: I hope they will blog or something. I don't know if it's a good idea for us to be trying to express that here.20:52
dhellmanndevananda: ok. I'm -1 on that because I don't want to have to have this conversation every time the project-config repo is updated. :-)20:52
devanandadhellmann: ++ on not having "mature" or "openstack-way" tags20:52
ttxI think we need to, though. Thats' what our downstream users want us to express20:52
devanandaalso -- if a project isn't following "the openstack way" it shouldn't be in openstack/* namespace. so we dont need a separate tag for that20:53
ttxwe can't on one private side say "this thing is crap" and then leave our users discover that by themselves20:53
dhellmannttx: I understand the need to have the information. I'm not convinced this body is the right group to produce it. Isn't that the whole issue that led to the Big Tent discussion in the first place?20:53
*** che-arne has joined #openstack-meeting20:53
devanandattx: ++20:53
annegent_devananda: but stackforge could be construed as "opesntack way-ish"20:53
ttxdhellmann: I'm not saying we would apply those tags ourselves20:53
devanandaannegent_: sure. ish :)20:54
annegent_:)20:54
*** timcline has joined #openstack-meeting20:54
ttxdhellmann: how about tags that describe adoption, based on user committee surveys and research they conduct20:54
ttxthey would apply that tag, not us20:54
jeblairyes, projects are in stackforge because they want to operate the openstack way.  i think in the long run that means that there should not be a stackforge, and all of them should be in the tent20:54
dhellmannttx: why wouldn't people just read the user surveys?20:54
jogottx: I have questions about the quality of the user survey data20:54
devanandadhellmann: we could (and IMO should) delegate the application of tags to the bodies of people (outside the TC) who represent that sort of knowledge20:54
*** e0ne has quit IRC20:55
ttxjeblair: not all of them fill all the boxes20:55
ttxjeblair: the only box they fill is "use Gerrit"20:55
dhellmanndevananda: we don't need to give anyone permission to go write up what they think the state of projects are20:55
jeblairttx: they test, use the mailing list, irc meetings, etc...20:55
devanandadhellmann: no, but providing a single point of reference is very helpful for people ...20:55
jeblairttx: they are there because they want to be part of the community20:55
ttxjeblair: they don't all use the ML, far from it20:55
dhellmanndevananda: certainly. Is that really project governance, though?20:56
jeblairttx: there are easier code hosting systems out there, they aren't just here for gerrit :)20:56
ttxjeblair: same with IRC meetings20:56
dhellmannwe're spending a lot of time on taxonomy that could be spent on negotiating some of the technical issues we have20:56
devanandadhellmann: the providing of that location? yes. the curation of the content? nope.20:56
ttxjeblair: a LOT of them use private calls/meetings/hangouts20:56
jogodhellmann: ++20:56
devanandadhellmann: indeed20:56
jeblairttx: right, so projects that need nothing more than git repo hosting can find it elsewhere, and the folks that want to be part of the community can be20:56
devanandaI'd love to, for example, discuss out of tree drivers20:56
devanandaand how that's working really well for some projects, while others resist it20:56
*** dzimine has joined #openstack-meeting20:56
*** eglynn_ has joined #openstack-meeting20:57
dhellmanndevananda: most of the operators I'm familiar with look to their distro for the kind of information we've been talking about, not upstream to us.20:57
* jogo wonders whats going on with neutron, and how nova-network isn't deprecated yet20:57
dhellmanndevananda: ++ to discussing how to manage drivers20:57
ttxdhellmann: I still think it's our responsibility to describe our ecosystem of projects for our downstream consumers20:57
devanandadhellmann: and distros look where?20:57
anteayadevananda: the only project I know of doing it so far is neutron, and others are watching20:57
*** Sukhdev has quit IRC20:57
devanandaanteaya: ironic20:57
dhellmanndevananda: they test and make their own decisions, no?20:57
ttxwe can't just dump pioles of code and say it's someone else problem to figure it out20:57
devanandaanteaya: though our model is somewhat different than neutron's, it seems to be working quite well for us20:58
devanandattx: ++20:58
*** VW_ has joined #openstack-meeting20:58
anteayadevananda: then that is another data point for me20:58
*** ijw has joined #openstack-meeting20:58
ttxsomeone has to do it, and we can't escape our responsibilities20:58
ttxAnyway... I'll be at the Ops Summit in PHL next week. Anyone else joining ?20:58
dhellmannI would whole-heartedly support someone creating a product guide or something that had this information in it. I do not think the TC should do it ourselves. We're not the only ones who can do it, and we have other things to address for which we *are* the only group who can address them.20:58
ttxsdague is, I know that20:59
annegent_ttx: oh good.20:59
ttxannegent_: you're coming ?20:59
sdaguettx: yep, I'll be there. mordred will as well.20:59
devanandaanteaya: ironic has explicitly supported out of tree drivers, though to my knowledge only a few exist, and they're not posted in obvious places yet20:59
*** jichen has joined #openstack-meeting20:59
ttxdhellmann: the tags are the guide. We create the framework and people fill the blanks / apply tags21:00
devanandaanteaya: but the email re stackforge/proliantutils is a great example of what our interface enables21:00
annegent_ttx: sadly, no. Matt Kassawara will be there for docs21:00
ttxI'll lead a session on ops-driven tags definition.21:00
*** noslzzp has quit IRC21:00
annegent_ttx: great21:00
ttxplan to discuss novanet vs. neutron, EC2 API support, DB downgrades, default config files and other upstream/ops pain points21:00
*** kebray has joined #openstack-meeting21:00
ttxSince a number of us will be there I'd rather skip the TC meeting next week.21:00
ttxIf something comes up and a meeting is urgently needed, I'll fish for replacement chair to run it21:00
devanandattx: i wish i could make it, but E_RECOVERING_FROM_TRAVEL21:00
*** echoingumesh has joined #openstack-meeting21:00
ttxLast words ?21:00
dhellmann"it'll be easy"21:01
jeblairi think we should have the meeting next week21:01
*** BadCub has joined #openstack-meeting21:01
annegent_"words are hard"21:01
devanandadhellmann: there's a tag for that21:01
ttxjeblair: ok, we'll discuss that on the tc list21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Mar  3 21:01:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-03-20.03.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-03-20.03.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-03-03-20.03.log.html21:01
*** olkonami has left #openstack-meeting21:01
*** _nadya_ has joined #openstack-meeting21:01
ttxcourtesy PTL ping: dhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov, mikal: around ?21:02
*** novas0x2a|laptop has joined #openstack-meeting21:02
eglynn_o/21:02
notmynamehere21:02
david-lyleo/21:02
mestery\o/21:02
nikhil_ko/21:02
asalkeldo/21:02
jungleboyjo/21:02
*** SridharRamaswamy has quit IRC21:02
ttx#startmeeting crossproject21:02
openstackMeeting started Tue Mar  3 21:02:32 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
dhellmanno/21:02
*** openstack changes topic to " (Meeting topic: crossproject)"21:02
*** SridharRamaswamy has joined #openstack-meeting21:02
ttxOur agenda for today:21:02
openstackThe meeting name has been set to 'crossproject'21:02
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:02
harlowja_\o21:02
* morganfainberg is lurking here.21:02
ttx#topic OpenStack developer doc vs. cross-project Specs21:02
*** openstack changes topic to "OpenStack developer doc vs. cross-project Specs (Meeting topic: crossproject)"21:02
ttxSo... The suggestion of writing an OpenStack coding guide was first raised on the "Eventlet best practices" openstack-spec:21:03
ttx#link https://review.openstack.org/#/c/154642/21:03
bknudsonI'd like the developer docs to look like docs rather than specs.21:03
harlowja_i think dhellmann should write another book that we can use21:03
*** VijayB_ has quit IRC21:03
*** echoingu_ has joined #openstack-meeting21:03
harlowja_^ joke21:03
ttxBasically it appeared more as a reference set of coding guidelines than as a clear problem to solve with a beginning and an end21:03
*** jpeeler has quit IRC21:03
ttxdhellmann raised the following thread to discuss the idea:21:03
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/057816.html21:03
ttxReaction was generally positive21:03
annegent_bknudson: what does look like mean21:03
ttxbut then there was the question of when guidelines should be spec material and when should they be coding guide material21:03
ttxAnd it's true that guidelines tend to start their lives as specs (as we make sure the exiting code catches up with the new guidelines)21:04
ttxexisting*21:04
ttx...and end their lives as guidelines for future code being written21:04
bknudsonannegent_: the specs look like a list of short docs, whereas a doc is something you can read through.21:04
ttxSo I guess there are 3 approaches:21:04
ttx1- Use specs for everything, no coding guide (and expect people to find rules for future code in the specs repo)21:04
*** SlickNik has joined #openstack-meeting21:04
*** echoingumesh has quit IRC21:04
ttx2- Use spec for drafting rules and the initial effort of converting existing code, then copy relevant parts of the spec to the coding guide so that future code is more likely to follow the rules21:04
ttx3- Draft rules in the coding guide, then create spec to track the effort of converting the existing code to the newly-defined rules (if any)21:05
annegent_bknudson: ok, thanks for the explanation21:05
*** echoingu_ has quit IRC21:05
ttxPersonally I find (1) not really future-proof21:05
notmynameisn't this why we have hacking?21:05
asalkeld+1 to 3, but same repo as the specs21:05
ttxwe can't expect future developers to sift through specs to find which ones happen to contain guidelines that they should apply to code they'll write21:05
dhellmannnotmyname: some things are easier to explain in prose21:05
*** echoingumesh has joined #openstack-meeting21:05
ttxI think (3) makes more sense process-wise than (2)21:06
harlowja_ttx sounds like we just need to organize specs more like a 'book' ?21:06
*** radez_g0n3 is now known as radez21:06
ttxThey could technically live in the same repository, although the "openstack-specs" name feels a bit misleading then21:06
nikhil_k== ttx21:06
ttxharlowja_: well, specs tend to be implemented and "completed", while rules live forever21:06
asalkeldttx: we have docs in code repos21:06
*** _nadya_ has quit IRC21:06
annegent_yeah I'd personally like to see a centralized cross-project coding guide separate from specs21:07
harlowja_well i hope rules don't live forever, the python community seems to change python drastically every few years, lol21:07
ttxso I'd argue they are different beasets, aven if there can be specs about implementing rules (especially the first time to catch up)21:07
*** thingee has joined #openstack-meeting21:07
sdagueannegent_: yeh, this seems like a development handbook that would be in the openstack manuals constellation21:07
thingeeo/21:07
sdaguebecause things like "eventlet best practices" are one of the proposed bits21:07
asalkeldexcept, having it in the same repo might make it easier to convert specs into docs21:08
ttxsdague: bnemec argues that "eventlet best practices" is the same animal as the "Log guidelines"21:08
annegent_sdague: except for the reviewers should be experts (not necessarily all doc team members)21:08
dhellmannsdague: the testing guidelines and logging guidelines could easily be moved over to that doc, too21:08
sdaguettx: I'm unconvinced21:08
dhellmannthis feels a bit bikesheddy - we've had pretty good luck so far with a "policy" subsection of the oslo-specs repo, and that feels like it would be a much easier route than creating a whole new document21:08
*** Mandell has quit IRC21:08
ttxi.e. a set of guidelines with a spec to describe catch-up phase21:08
* devananda notes the existence of a similar-ish guide in oslo.db for using sessions21:09
dhellmannsdague: the guidelines parts of those documents would move, but the "to do" list wouldn't21:09
annegent_dhellmann: guess it depends on the goals -- getting agreement across projects? Or helping contributors?21:09
sdagueannegent_: right, it's a different audience21:09
dhellmanndevananda: sure, we do have docs for the libs, too. bnemec's thing on eventlet could go into oslo.concurrency, except I'm not sure anyone would find it there because it's about eventlet not oslo.concurrency21:09
sdaguespecs are about agrement21:09
ttxdhellmann: so you would follow option 2 ?21:09
notmynamemaybe it's because this started with eventlet, but I'm not a big fan of a central set of guidelines (rules) for 500+ openstack repos to follow. syntax/hacking stuff is fine, but "here's how to use this 3rd party library" doesn't seem like a good idea for rules21:09
bknudson#link http://specs.openstack.org/openstack/openstack-specs/21:10
*** noslzzp has joined #openstack-meeting21:10
bknudsonthere's the repo now21:10
devanandanotmyname: except for when it is21:10
dhellmannttx: I prefer option 1 actually21:10
dhellmannnotmyname: it's not prescriptive, it's advice21:10
sdaguea developer handbook is a contributor onboarding would be kind of handy. Not everyone has been around these things for ever21:10
notmynamedevananda: my point is that I don't know when that happens, if ever21:10
*** echoingumesh has quit IRC21:10
*** echoingu_ has joined #openstack-meeting21:10
devanandanotmyname: plenty of libraries produce docs on how to use them well21:10
* harlowja_ also prefers they not be called rules (software changes folks, practices change, ...); but i guess thats just my personal feeling21:10
ttxdhellmann:  but moving spec to a specific directory under specs ?21:11
dhellmannsdague: sure, and that's different than what we've had proposed so far as specs21:11
devanandanotmyname: eg, sqlalchemy21:11
jungleboyjsdague: +221:11
dhellmannttx: yeah, in oslo-specs we just have a "policy" dir but we could use "devref" or something here21:11
notmynamedevananda: nope. not gonna fly. that's not how openstack works. every "guideline" that starts optional has turned into something that is strongly pressured to conform to21:11
notmynamedhellmann: ^^ (sorry not devananda)21:12
bknudsonso what's the argument for having a separate repo?21:12
dhellmannnotmyname: do you think that's the case for the existing guidelines?21:12
devanandaI'd be happy to see shared guides // devref material, but I agree that the audience is different from our cross-project specs21:12
ttxnotmyname: I guess you object to the concept of cross-project specs anyway ?21:13
devanandahowever the set of folks who should review it is not all that different21:13
notmynamedevananda: I'm fine with a library producing docs on how to use it well. that's good. I'm not ok with having a prescription for every openstack repo21:13
notmynamettx: no, I don't21:13
annegent_bknudson: one argument pro separate repo would be for a review group21:13
ttxnotmyname: they sometimes contain guidelines, too21:13
notmynamedhellmann: I'd point to last years "TC gap analysys" as a way to get projects to conform to guidelines21:13
*** BrianShang_ has joined #openstack-meeting21:13
dhellmannnotmyname: in the case of the eventlet thing, it's more about saying "if you do this you're going to have bugs, but this other thing works" isn't it?21:13
morganfainbergnotmyname: if we have learned lessons "this is bad because x" hat is t bad documentation. Doesn't mean there are exceptions to it.21:13
devanandanotmyname: sure. I do not think it should be proscriptive and mandated across all projects21:13
bknudsonannegent_: that's a good one.21:13
*** sergef has joined #openstack-meeting21:14
devanandanotmyname: however, the eventlet discussion, aiui, originally started because folks want to mandate a change21:14
dhellmannnotmyname: I don't think that's a bad thing.21:14
notmynameit touches a nerve because I've seen it many times. ;-)    /me feels the same way about the api working group21:14
morganfainbergBut having reasonable guidelines that a lib let's you do but we know causes issues unless you work around it isn't negative.21:14
*** apevec has joined #openstack-meeting21:14
devanandagotta step away for 5 min21:14
asalkeldnotmyname: there are user's that don't like that each project does things in different ways21:15
*** BrianShang has quit IRC21:15
bknudsonfor developers it's also confusing when you switch between projects.21:15
RockygThere are operators who don't like that projects aren21:15
*** VijayB has joined #openstack-meeting21:15
harlowja_thinks we should just have guidelines/lessons learned (don't call them rules, things that people must follow); if people still want to shoot there feet off, thats there choice21:15
*** _amrith_ is now known as amrith21:15
Rockygt consistenet in the OpenStack "space"21:16
notmynameharlowja_: that's better21:16
*** jecarey has joined #openstack-meeting21:16
jungleboyjbknudson: +121:17
harlowja_Rockyg imho to facilatate a healthy opensource community thats just going to have to be one of the balances that may not always be perfect (conformity via rules, vs innovation)21:17
dhellmannthe eventlet document was created after someone wanted to patch an oslo library to do something custom with eventlet because their app was not properly initializing eventlet21:17
RockygA developer ref gives newbies a good set of guidelines to follow that are from lessons learned.  If you're senior and really good, you can judge when exceptions are reasonable21:17
*** hareeshp has joined #openstack-meeting21:17
dhellmannthe oslo team rejected that patch, and started trying to provide more guidance for using eventlet21:17
*** sdake_ has joined #openstack-meeting21:17
*** aysyd has quit IRC21:18
asalkeldso the devref if for newbies, and we need a thing that is more aimed at experts21:18
dhellmannthey're not rules, per se, but if you're not following them then there will be problems with using libs that expect you to be following them (not just from oslo)21:18
RockygJarlowja: if the community finds it too hard to manage, they go elsewhere.  Then the projects become just for developers21:18
dhellmannasalkeld: yeah, it sounds like we have 2 audiences21:18
notmynamedhellmann: which goes to what harlowja_ said.21:18
Rockygmanage in use.21:18
*** rbowen has joined #openstack-meeting21:18
harlowja_Rockyg sure, thus the balance that is not easy to maintain21:19
* devananda returns21:19
* harlowja_ afaik the same thing happened with hadoop21:19
bknudsoneven the openstack-specs repo says it's for "Cross-Project Specifications and Policies" -- but there are no policies yet.21:19
ttxnotmyname: so you'd prefer solution (1) ?21:19
*** thumpba has joined #openstack-meeting21:20
harlowja_'Policies' sounds to much like rules imho21:20
*** thedodd has joined #openstack-meeting21:20
asalkeldyeah21:20
ttx"Guidelines" sounds better21:20
RockygThe cross-project specs should be used to create devref.  If a spec supersedes old spec, it gets deprecated and the doc gets modified.21:20
jungleboyjSeems like we need to stay away from anything that sounds like 'rules'.21:20
*** kebray has quit IRC21:20
asalkeld"Implementation suggestions"21:20
dhellmannRockyg: I would like to avoid a bunch of busy work moving things around21:20
jungleboyjttx: +221:20
bknudsonwe do have rules -- e.g., api stability guidelines.21:21
harlowja_u just called that guidelines, not rules, lol21:21
bknudsonhttps://wiki.openstack.org/wiki/Governance/Approved/APIStability21:21
thingeettx: +121:21
notmynamettx: I think "Specs" should be for pieces of work that are defined and get merged to a specific repo (or set of repos). if we want advice for libraries somewhere, then I don't think it should be in a specs repo21:21
morganfainbergYou could do the same thing that is the API ref docs. Publish the devref from the same repo. Like keystone has for the api spec vs specs for features.21:21
eglynn_well "guidelines" is certainly friendlier than hard rules21:21
ttxWe could do (1) the other way around. Move completed, irrelevant specs to a "completed" directory once they are done. If a spec is in the "active" directory it's still "current". Solves the discoverability issue21:21
morganfainbergIf you want to have the same repo with devref in it.21:21
morganfainbergThat way you kind of strike middle ground.21:22
Rockygnotmyname ++21:22
notmynamettx: that's what we do in swift actually (have a "done" folder for finished specs"21:22
ttxnotmyname: but you don't want them in a coding guide either21:22
* bnemec wanders in late21:22
Rockygttx:  that's what I intended ;-)21:22
*** JRobinson__ has joined #openstack-meeting21:22
bknudsonhaving the devref and spec in the same repo means that you can update the devref along with the spec (in the same review), so when the spec is approved/merged the devref is, too.21:23
notmynamettx: perhaps it's the "guide" word. it depends on how that document is done. I do not want it with eg pep8 rules. I'm completely ok with "here's what we've learned about the best way to use evenlet or to [not] do DB migrations etc"21:23
asalkeldcan we publish this stuff differently, even though they live in the same repo?21:23
RockygOK.  Developer's Guide21:24
morganfainbergnotmyname: I think that is what is being pitched here. That was my understanding.21:24
ttxmorganfainberg: +121:24
bnemecYeah, it's eventlet best practices, not eventlet commandments. :-)21:24
morganfainbergHere is what we know/learned. Don't do x unless you are aware of y because $reason21:24
Rockygmorganfainberg ++21:25
*** rbowen has quit IRC21:25
dhellmannI thought using the same repo would let us actually produce something useful quickly, but if it's just going to mean more arguing then let's create a separate reference guide repository.21:25
*** eghobo has quit IRC21:25
morganfainbergbnemec: I like there eventlet commandments better (as a name) :P21:25
*** sdake_ has quit IRC21:25
notmynamemorganfainberg: yup, that's great. just not in a "this is how you must code in an openstack project"21:26
bnemecdhellmann: +1.  I'd prefer to go with the one repo thing like oslo-specs, but not so much that I want to endlessly bikeshed over it.21:26
dhellmannwe have spent more time talking about it than it would have taken me to set up a new repo, so let's not waste any more time21:26
*** ChuckC has joined #openstack-meeting21:26
morganfainbergdhellmann: or a separate directory in the same repo. Like the API spec would work. Just can't be a "spec" as in "work to be done". Because that is not meaningful or easy to parse for someone looking for reference.21:26
SlickNikdhellmann: ++21:26
ttxbnemec: how about writing a blogpost instead21:27
asalkeldttx: there is no review or acceptance then21:27
morganfainbergWe should just make it an easy way to search/find/reference regardless of where it is. A blog post is as good as a repo to start.21:27
devanandablog post --21:28
ttxasalkeld, devananda : that was sarcasm21:28
bnemecIt would have hurt this document a lot to have me do it as a blog post.21:28
devanandattx: oh :)21:28
bnemecHeh21:28
morganfainbergBut just pick a place for it ;). I think we have over discussed this.21:28
ttxno kidding21:28
* asalkeld not stressed about this, do *something* and it will probably be fine21:29
morganfainbergIt doesn't belong as a "work to be done"-spec. That is all that needed to be said.21:29
dhellmann#action dhellmann create openstack/developer_reference repository21:29
devanandadhellmann: how about oslo/developer-guides (or change name as appropriate) to host developer-contributed-and-reviewed reference material21:29
*** Shamail has joined #openstack-meeting21:29
bknudsonif we have a separate repo are there different rules for appoval?21:29
devanandahah21:29
RockygCool thing about spec and doc in same repository is that you can have spec=chapter where appropriate21:29
dhellmannttx: let's move on21:29
ttxdhellmann: ++21:29
devananda++21:29
morganfainbergbknudson: start with the same rules as we have for the current repo. Update as needed.21:29
ttxWe have reached the end of my timebox (and patience) for this anyway21:29
bnemec+121:29
ttx#topic Replacing eventlet: how to make progress (or not)21:29
*** openstack changes topic to "Replacing eventlet: how to make progress (or not) (Meeting topic: crossproject)"21:30
ttxSo we have two specs for separate approaches in getting rid of eventlet:21:30
harlowja_sooooo21:30
ttx#link https://review.openstack.org/#/c/153298/21:30
ttx#link https://review.openstack.org/#/c/156711/21:30
asalkeldgroan21:30
ttxand I feel like those are getting nowhere21:30
ttxand I'd like to set a constructive next step for those21:30
dhellmannasalkeld: if you all don't pick, oslo is going to pick for you because eventlet is a constant source of trouble for us21:31
ttxbut then I'm not sure we are on the right day for that21:31
*** wojdev has joined #openstack-meeting21:31
ttxI feel like we are stagnating on this, in particular with two specs diluting the essential question of why we should even consider moving off eventlet at this point21:31
ttxTo unblock ourselves, I suggested that the two proposers actually collaborate to answer that essential question21:31
*** jsavak has quit IRC21:31
ttxBecause having two parallel specs answering that question in slightly different terms doesn't really help making progress imho21:31
harlowja_well they are fundamentally different solutions ;)21:31
asalkeldout of those 2, i pick asyncio21:31
ttxWhich is why I proposed that the two specs should converge on a single spec with two implementation alternatives (a metaspec)21:31
dhellmannharlowja_: the premise of wanting to move is the same, though21:31
ttxDescribe the problem with eventlet once, and propose solutions in comparable terms21:31
ttxRather than separately stating that your approach is superior and sending everyone away, wondering why we even want to change eventlet in the first place21:32
asalkeldbut after using yield for ~year for scheduling - i still am not a fan21:32
ttxBut then neither author seems interested in that approach21:32
eglynn_ttx: have you run the metaspec idea past haypo?21:32
harlowja_sure, seems fair, although there will still be the my approach is different better than yours part, lol21:32
ttxeglynn_: I did. He prefers to prove his point with code21:32
harlowja_due to the fundametnally different ways these work21:32
harlowja_lifeless wants CSP instead :-P21:33
eglynn_ttx: yeah, I suspected that might be the case21:33
ttxI just fear he will pile up a lot of code and get stopped after wasting a lot of work21:33
devanandattx: I would appreciate the clear description of why we need to move off of eventlet21:33
ttxdevananda: me too21:33
devanandaand why now()21:33
dhellmannharlowja_: "CSP"?21:33
sdaguedevananda: ++21:33
lifelesscommunicating sequential processes21:33
dhellmannlifeless: thanks21:33
*** pnavarro has quit IRC21:34
devanandadhellmann: i will object strongly to oslo making a change that forces projects to fundamentally change their implementation / threading model21:34
ttxdevananda: I mean, we used to have a Python3 long-term issue motivating the change and kind of balancing its high cost21:34
harlowja_dhellmann http://goless.readthedocs.org/en/latest/  (ya, what lifeless said)21:34
lifelessI linked to several sources in my review comment21:34
devanandadhellmann: i'm not sure if that's what you meant, but that's how I read it21:34
sdaguelifeless: isn't that basically the rewrite in go approach?21:34
dhellmanndevananda: then it's best to get involved in this discussion :-)21:34
lifelesssdague: no21:34
*** eghobo has joined #openstack-meeting21:34
lifelesssdague: I'm not a fan of go in general, but the concurrency model stuff is really nice21:34
*** kmartin has joined #openstack-meeting21:34
devanandattx: right. _used_to_. also that didn't motivate us strongly enough over the last two years, so why now() ?21:35
harlowja_lifeless +1 the concept is nice and would be great to make happen; i'm just not sure the practicality of it happening21:35
dhellmanndevananda: ftr, I'm opposed to approaches that require major changes in the applications21:35
*** sergef has quit IRC21:36
lifelesssdague: one of the ways in which it is nice is that it is very similar to what we do now (since we do relatively little synchronised workloads anywa)21:36
dhellmanndevananda: part of this is looking ahead to python 3, where eventlet continues to be only mostly supported21:36
devanandadhellmann: I thought so. hence my uncertainty in my interpretation above21:36
lifelesseventlet has been a source of bugs21:36
sdaguedhellmann: I thought the python3 situation was rapidly improving21:36
*** egallen has quit IRC21:36
lifelesssome major and very hard to diagnose ones21:36
lifelessthats the why, I don't think there is disagreement over this, is there?21:37
sdaguelifeless: so has sqlalchemy21:37
dhellmannsdague: it is improving, but I don't know about rapidly or completely21:37
*** egallen has joined #openstack-meeting21:37
harlowja_lifeless and then u can get into the concurrency model taskflow uses/enables (which isn't CSP but is more like concurrent dataflow-like), ha21:37
*** vivek-ebay has quit IRC21:37
lifelesssdague: yup, and there are folk muttering about that long-term too, but lets pick one battle at a time21:37
ttxFWIW I am having network issues21:37
*** jpeeler has joined #openstack-meeting21:38
*** jpeeler has quit IRC21:38
*** jpeeler has joined #openstack-meeting21:38
devanandawhen we use a library this heavily and then find issues, is abandoning it better than fixing it?21:38
ttxdevananda: exactly. I fear that harlowja_  and haypo are moving to solutions and failed to convince anyone there was a problem21:38
sdagueyeh, I mean libvirt has had monster hard to diagnose bugs21:38
dhellmanndevananda: do we have volunteers to go work on fixing it?21:38
lifelessdevananda: depends if the issues are due to implementation or concept - eventlets issues are arguably not implementation21:38
harlowja_i'm just proposing a spec, with ideas, i leave it up to the community to pick the solution ;)21:38
dhellmannit's fine to say we should work upstream, but if we have no one actually interested in doing that then it's not actually a solution21:39
devanandadhellmann: do we have confidence that the proposed alternatives don't *also* have problems that we'll only find when every project is using it at openstack-levels of scale?21:39
ttxAnd each spec presents a slightly different view on what "the problem" is21:39
notmynameswift contributors have often made upstream patches to eventlet and haven't had a problem getting them accepted21:39
*** ndipanov has quit IRC21:39
dhellmanndevananda: I agree, that's part of the discussion we should be having21:39
lifelessdevananda: the scale thing confuses me; any one python process is still very limited in size in Openstack21:39
sdaguelifeless: the developer scale21:40
dhellmannnotmyname: the issue isn't with eventlet's willilngness to take patches, it's with the lack of people to make the patches in the first place21:40
lifelessdevananda: do you mean 'many contributors that don't grok the library' ?21:40
devanandalifeless: IIRC some of the issues we've had only showed up intermittently, ie, in the gate21:40
harlowja_ttx so i think i can work with haypo on creating the unified 'what is the issue' part; and then i guess have huge sections for  the different ways to 'solve' it21:40
sdagueif you have super awesome developers that don't make mistakes, your underlying implementation doesn't matter21:40
*** eharney has joined #openstack-meeting21:40
ttxharlowja_: I /think/ that would be more likely to succeed21:41
notmynamedhellmann: I'm saying that in that when we need something for eventlet, we've made patches and they've been accepted. and swift hasn't seen any scale problems with it21:41
*** neelashah has quit IRC21:41
sdagueif you have 1000+ contributors + 2 million lines of extant code... things are different21:41
harlowja_ttx the ways to solve it list will not be comprehensive ( lifeless could for example add a CSP section, i could add another section for taskflow dataflow concurrency...)21:41
*** wojdev has quit IRC21:41
devanandalifeless: i still haven't seen a compelling reason to switch off of eventlet -- as much as I personally would prefer to have proper threading21:41
devanandasdague: exactly21:41
ttxharlowja_: I'd very much want to see a CSP section21:41
harlowja_and a taskflow dataflow one to, and ... (there are alot of models that could work, ha)21:41
dhellmannnotmyname: yes, and I'm saying that I don't have anyone willing to help with the python 3 port and so that's going to become an issue if the eventlet team doesn't actually finish it -- I'm trying to ensure we have a path into the future21:41
*** stevemar has quit IRC21:41
*** egallen has quit IRC21:42
*** wojdev has joined #openstack-meeting21:42
notmynamedhellmann: didn't their latest release fishing that up? 0.17 IIRC21:42
sdague0.17.0, which is in the gate, passes their python 3 tests21:42
dhellmannnotmyname: they've claimed support before21:42
sdagueit would probably be interesting to find a project which we could light up on it and see if it passes our tests21:42
devanandaharlowja_: thanks - I'd really like to understand the justification for even considering mandating a change that would affect all the projects like this21:42
harlowja_http://en.wikipedia.org/wiki/Dataflow_programming (for those who wonder wtf dataflow is, lol); taskflow is something like this21:42
dhellmannbut they were missing some monkeypatching or had installation issues or some other thing21:42
ttxharlowja_: but then, that's only my suggestion in incvreasing chances -- feel free to go your own way :)21:42
harlowja_ttx well this is a cross-project thing, i can't go and make projects do it (and thats not even possible, i am only 1 man, lol)21:43
devanandadhellmann: also, just to make sur ei'm on the same page, what is the impact if oslo were to support both eventlet and asyncio? has that been discussed and I just missed it?21:43
ttxOK, 3 more minutes and we'll cover misc other specs21:43
dhellmanndevananda: asyncio will require a level of code change to actually be useful that means we don't want to support both21:43
*** thangp has quit IRC21:43
lifelessdhellmann: won't we have to to enable migration ?21:43
*** eharney has quit IRC21:43
dhellmannwe would have to support converting things to coroutines21:44
lifelessdhellmann: /whatever/ we choose?21:44
devanandalifeless: exactly ..21:44
harlowja_devananda supporting native threads, and eventlet threads is do-able imho (but then eventlet...)21:44
dhellmannlifeless: this is why I don't think asyncio is a reasonable approach21:44
harlowja_but asyncio throws a wrench in21:44
asalkelddo we have a port of eventlet that works on top of asyncio?21:44
*** redixin has quit IRC21:44
lifelessyes21:44
dhellmannharlowja_: right, I think moving directly to regular threads is more realistic21:44
*** EmilienM has quit IRC21:44
*** EmilienM has joined #openstack-meeting21:44
lifelesshaypo has done that21:44
*** gyee has joined #openstack-meeting21:44
lifelessand its in the spec21:44
harlowja_afaik its asyncio ontop of eventlet, not the reverse21:45
asalkeldlifeless: does that have the same issues?21:45
dhellmannit runs on the eventlet loop, but does not do the monkeypatching part, right? so you still have to convert application code to coroutines to actually achieve any concurrency21:45
lifelessAIUI he has a eventlet mainloop that is an asyncio adapter21:45
lifelessas part of the migration strategy21:45
asalkeldo, we need it the other way around21:45
bknudsonkeystone has solved the problem already... deprecate eventlet.21:45
harlowja_https://github.com/1st1/greenio i thought right?; i thought that just plugged eventlet/greenlet into asyncio21:46
morganfainbergbknudson: that works for api surface but not for conductor etc21:46
sdaguebknudson: that's only possible for things that *only* have an API service21:46
harlowja_so u still need asyncio21:46
dhellmannright, the problem we have with eventlet is mostly caused by the use of the monkeypatching and not by eventlet's underlying code21:46
lifelessdhellmann: except the race conditions around closed fd's21:46
ttxI don't really expect us to come to a conclusion here :)21:46
dhellmannsdague: oslo.messaging has a threading executor, so apps that have no wsgi interface could port to threads21:47
*** SridharRamaswamy has quit IRC21:47
ttxLet's move on to cover a few other topics21:47
sdaguedhellmann: sure21:47
morganfainbergBut I would love to see eventlet and custom wsgi layers go away for the API surface across all of OpenStack (personal preference). Conductor, compute, etc different issue.21:47
sdaguedhellmann: but keystone doesn't do that  :)21:47
dhellmannlifeless: I don't know the background there21:47
lifelessdhellmann: which I think *may* be fixed. Assuming no more occurences21:47
ttxbut I feel a cross-project design summit session to discuss this21:47
harlowja_or was it http://aioeventlet.readthedocs.org/ i can't remember, ha21:47
*** sdake_ has joined #openstack-meeting21:47
*** egallen has joined #openstack-meeting21:47
ttx#topic Other openstack-specs discussion21:48
harlowja_lifeless afaik it was eventlet/greenlet under asyncio; so u still need to be using asyncio concepts (or triolloius concepts)21:48
*** openstack changes topic to "Other openstack-specs discussion (Meeting topic: crossproject)"21:48
dhellmannttx: we should have a lot more discussion online first, and get harlowja_ and haypo to pull together the justification for changing at all so we can at least reach some agreement on that21:48
sdaguettx: well, if we can't get folks to write the meta spec, I don't think that that sesssion will be productive either21:48
ttx#undo21:48
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f41590>21:48
harlowja_dhellmann i'll see what i can do21:48
dhellmannharlowja_: thanks21:48
ttxsdague: right21:48
harlowja_np21:48
ttx#topic Other openstack-specs discussion21:48
*** openstack changes topic to "Other openstack-specs discussion (Meeting topic: crossproject)"21:48
ttx* Add library stable release procedures/policy (https://review.openstack.org/#/c/155072/)21:48
ttxWe discussed that one last week, but it didn't really trigger a lot of new reviews21:48
ttxI suspect it's more lack of interest or opinion, than a problem with the spec, though21:48
lifelessharlowja_: I'll help, ping me?21:48
harlowja_lifeless sure21:49
*** dprince has quit IRC21:49
ttxSo I propose we keep it there for another week then consider moving on to rubberstamping21:49
*** hareeshp has quit IRC21:49
ttxRead and review if you care!21:50
ttx* Managing stable branch requirements (https://review.openstack.org/#/c/159249)21:50
dhellmannfiguring out the right approach for stable releases of libraries is going to be more important now that we're capping (and eventually possibly pinning) dependencies in stable branches21:50
ttxThis one is the outcome of a discussion that happened on the ML at:21:50
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-February/057367.html21:50
ttxBusiness summary:21:50
ttx- Only a handful of people work on stable branches21:50
ttx- Stable branches get broken all the time due to their code being incompatible with a new version of a dependency being published on the Internet (abcd>=1.0)21:50
ttx- Recently we added version caps (abcd>=1.0,<=1.1.7) so that stable branches would not pull recent crap, and all was awesome21:50
ttx- That can still fail due to uncapped dependencies of dependencies though21:51
ttx- jogo's proposal is to compute pinned versions all of dependencies, record that in stable branches (as requirements.gate) and use that in stable branch gating21:51
adam_gi've picked up 159249 from jogo and have started a new draft just this afternoon. there are some technical challenges to figure out but i think the idea is solid21:51
ttx- master branches are unaffected by this change and continue to potentially consume new crap, to make sure we don't get stuck with stale deps in future development21:51
*** wojdev has quit IRC21:52
ttxI think it's pretty straightforward, and I wonder if we really needed to go through the openstack-specs process for this21:52
ttxit just neds someone to JFDI21:52
devanandattx: everything you just said seems good to me21:52
ttxbut then we want to document things we do21:52
* ttx blames dhellmann kilo motto21:52
adam_gttx, we need to think carefully about it. this introduces new ways we can wedge ourselves21:53
*** ChrisPriceAB has quit IRC21:53
jungleboyjJust as long as we stop breaking the stable branches.21:53
dhellmannttx: I asked jogo for a spec so we could work out the details before making changes, because a big part of the reason we had so much trouble this cycle was making changes to how requirements work without understanding the side-effects21:53
ttxadam_g: any example ?21:53
*** mtanino has quit IRC21:53
*** SridharRamaswamy has joined #openstack-meeting21:53
dhellmannwe could have done that within the requirements group, but since it also affects stable-maint and eventually the projects producing client libraries I thought an XP spec made sense21:53
ttxdhellmann: ok21:53
adam_gttx, specifically, how we manage and sync the .gate files. these will end up being  more explicit than anything we've used in the past, and we risk making things even more restrictive21:54
dhellmannadam_g: the ability to wedge ourselves is why I prefer caps over pins; it's easy to add a != entry to the file21:54
jogoadam_g: thanks for taking over21:54
*** julim has quit IRC21:54
ttxadam_g: if that introduces new way we can wedge ourselves, those should be documented in the spec ?21:54
*** eharney has joined #openstack-meeting21:54
ttxadam_g: should we consider it still WIP ?21:54
*** JRobinson__ has quit IRC21:54
bknudsonare we expecting lots of changes in the pins after the initial one?21:55
adam_gttx, the spec is still a WIP, yes. im in favor of the spec process for this change21:55
ttxWe can make progress on patchsets in a smaller circle (stable/relmgmt/QA)21:55
*** jichen has quit IRC21:55
ttxI thought jogo unWIPped it21:55
ttxwhich signals it's ready for others to review/approve21:55
adam_gbknudson, the version pins are generated based on caps (or other constraints) in requirements.txt21:55
dhellmannbknudson: that depends on how many backports we have21:56
ttxmaybe we should reWIP it21:56
*** dmacpher has joined #openstack-meeting21:56
*** SridharRamaswamy has quit IRC21:56
*** jgrimm is now known as zz_jgrimm21:57
*** JRobinson__ has joined #openstack-meeting21:57
*** egallen has quit IRC21:57
adam_gttx, sorry. ive been out for the last week, was trying to pick this spec up today.  will hopefully have something ready for broader  next week21:57
adam_g*broader review21:57
ttxadam_g: I sugegst you re-WIP it while you analyze consequences21:58
adam_gttx, sure21:58
ttxyou might need jogo's help to do that21:58
adam_gjogo, ya ^21:58
ttxOK, We'll reconsider when it's unWIPped21:58
ttx#topic Open discussion & announcements21:58
*** pelix has quit IRC21:58
*** openstack changes topic to "Open discussion & announcements (Meeting topic: crossproject)"21:58
ttxWe had 1:1s syncs today in #openstack-relmgr-office, logs at:21:58
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-03-09.00.html21:58
ttxNext week I'll be at the Ops Summit, so if someone wants to pick up chairing this meeting, let me know21:59
ttxBased on the agenda we might just skip it anyway21:59
ttxAnyone else coming to the Ops Summit ?21:59
dhellmannI can do it, if we need a meeting21:59
ttxdhellmann: thx!21:59
morganfainbergYay dhellmann!21:59
* notmyname will be at the ops summit21:59
*** mtanino has joined #openstack-meeting21:59
* morganfainberg will not be at the ops summit.21:59
ttxI know sdague and mordred will be too22:00
ttxand thingee22:00
sdagueand mtreinish22:00
*** thingee has quit IRC22:01
*** SridharRamaswamy has joined #openstack-meeting22:01
*** wojdev has joined #openstack-meeting22:01
*** erlon has quit IRC22:01
ttxalright, we should be able to conspire^Wdrink together22:01
*** achanda has quit IRC22:01
ttxand that is the end22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
*** ivar-laz_ has joined #openstack-meeting22:01
openstackMeeting ended Tue Mar  3 22:01:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-03-21.02.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-03-21.02.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-03-03-21.02.log.html22:01
*** BadCub has left #openstack-meeting22:01
*** ivar-laz_ has quit IRC22:02
*** narenhn has quit IRC22:03
*** andreykurilin_ has joined #openstack-meeting22:03
*** ivar-laz_ has joined #openstack-meeting22:03
*** otter768 has joined #openstack-meeting22:03
*** zz_jgrimm is now known as jgrimm22:03
*** doude has quit IRC22:03
*** ivar-lazzaro has quit IRC22:04
*** topol has quit IRC22:05
*** mwagner_lap has quit IRC22:06
*** achanda has joined #openstack-meeting22:07
*** otter768 has quit IRC22:08
*** eglynn_ has quit IRC22:09
*** safchain has quit IRC22:09
*** Mandell has joined #openstack-meeting22:10
*** Mandell has quit IRC22:10
*** aranjan_ has joined #openstack-meeting22:11
*** adahms_ has joined #openstack-meeting22:12
*** dmellado has left #openstack-meeting22:13
*** gyee has quit IRC22:13
*** devlaps has joined #openstack-meeting22:13
*** devlaps has quit IRC22:13
*** aranjan has quit IRC22:13
*** Guest47 has joined #openstack-meeting22:14
*** adahms_ has quit IRC22:14
*** wojdev has quit IRC22:16
*** jckasper has joined #openstack-meeting22:17
*** aepifanov has quit IRC22:17
*** jungleboyj has quit IRC22:17
*** tiswanso_ has quit IRC22:18
*** MaxV has quit IRC22:18
*** dkranz has quit IRC22:22
*** wojdev has joined #openstack-meeting22:23
*** Mandell has joined #openstack-meeting22:24
*** moha_hunt has quit IRC22:24
*** ibiris is now known as ibiris_away22:25
*** e0ne has joined #openstack-meeting22:26
*** vijendar has quit IRC22:30
*** thingee has joined #openstack-meeting22:31
*** Shamail has quit IRC22:31
*** rushil has quit IRC22:31
*** sarob has quit IRC22:31
*** tr3buchet has joined #openstack-meeting22:32
*** neelashah has joined #openstack-meeting22:33
*** gyee has joined #openstack-meeting22:33
*** sdake_ has quit IRC22:37
*** AlanClark has quit IRC22:37
*** Mandell has quit IRC22:38
*** vivek-ebay has joined #openstack-meeting22:38
*** jckasper has quit IRC22:39
*** Rockyg has quit IRC22:39
*** jckasper has joined #openstack-meeting22:39
*** esker has quit IRC22:39
*** banix has quit IRC22:39
*** thomasem has quit IRC22:41
*** timcline has quit IRC22:42
*** Guest47 is now known as adahms22:42
*** vivek-ebay has quit IRC22:42
*** stevemar has joined #openstack-meeting22:44
*** ayoung has quit IRC22:45
*** annegent_ has quit IRC22:49
*** noslzzp has quit IRC22:50
*** wojdev has quit IRC22:53
*** mwagner_lap has joined #openstack-meeting22:53
*** asalkeld has left #openstack-meeting22:53
*** asalkeld has joined #openstack-meeting22:55
*** aranjan_ has quit IRC22:55
*** aranjan has joined #openstack-meeting22:55
*** andreykurilin_ has quit IRC22:55
*** wojdev has joined #openstack-meeting22:57
*** ijw has quit IRC22:57
*** vivek-ebay has joined #openstack-meeting22:59
*** ijw has joined #openstack-meeting23:00
*** zehicle_ has quit IRC23:00
*** ijw_ has joined #openstack-meeting23:01
*** gholler has quit IRC23:02
*** jpeeler has quit IRC23:02
*** ivar-laz_ has quit IRC23:02
*** ivar-lazzaro has joined #openstack-meeting23:03
*** ebalduf has quit IRC23:03
*** ivar-lazzaro has quit IRC23:04
*** aranjan has quit IRC23:04
*** dneary has quit IRC23:04
*** ijw has quit IRC23:05
*** ivar-lazzaro has joined #openstack-meeting23:05
*** neelashah has quit IRC23:06
*** egallen has joined #openstack-meeting23:06
*** VijayB has quit IRC23:06
*** absubram has quit IRC23:08
*** VijayB_ has joined #openstack-meeting23:08
*** VijayB_ has quit IRC23:08
*** vivek-ebay has quit IRC23:09
*** vivek-ebay has joined #openstack-meeting23:09
*** aranjan has joined #openstack-meeting23:10
*** yamamoto has joined #openstack-meeting23:11
*** sarob has joined #openstack-meeting23:12
*** sgordon has joined #openstack-meeting23:14
*** zehicle_ has joined #openstack-meeting23:15
*** adahms has quit IRC23:17
*** adahms has joined #openstack-meeting23:17
*** thingee has quit IRC23:19
*** matrohon has quit IRC23:19
*** alexpilotti has quit IRC23:19
*** aranjan has quit IRC23:20
*** Mandell has joined #openstack-meeting23:20
*** amitgandhinz has quit IRC23:24
*** aranjan has joined #openstack-meeting23:24
*** jungleboyj has joined #openstack-meeting23:25
*** jckasper has quit IRC23:26
*** hichihara has joined #openstack-meeting23:28
*** stevemar has quit IRC23:29
*** e0ne has quit IRC23:30
*** mmedvede_ has joined #openstack-meeting23:32
*** e0ne has joined #openstack-meeting23:34
*** prad has quit IRC23:36
*** yamamoto has quit IRC23:36
*** ddieterly has quit IRC23:36
*** sigmavirus24 is now known as sigmavirus24_awa23:36
*** noslzzp has joined #openstack-meeting23:38
*** alop has quit IRC23:38
*** VijayB_ has joined #openstack-meeting23:42
*** noslzzp has quit IRC23:42
*** rromans has quit IRC23:43
*** VijayB_ has quit IRC23:43
*** tiswanso has joined #openstack-meeting23:44
*** eghobo_ has joined #openstack-meeting23:44
*** tochi has joined #openstack-meeting23:44
*** eghobo has quit IRC23:45
*** e0ne has quit IRC23:47
*** tiswanso has quit IRC23:49
*** achanda has quit IRC23:49
*** Sukhdev has joined #openstack-meeting23:49
*** annegentle has joined #openstack-meeting23:49
*** jgrimm is now known as zz_jgrimm23:50
*** nelsnelson has quit IRC23:52
*** achanda has joined #openstack-meeting23:56
*** watanabe_isao has joined #openstack-meeting23:57
*** MarkAtwood has quit IRC23:59
*** yamamoto has joined #openstack-meeting23:59

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