Tuesday, 2014-10-21

*** VijayB_ has joined #openstack-meeting00:00
*** gokrokve_ has quit IRC00:01
*** vikas has joined #openstack-meeting00:03
*** vikasd has quit IRC00:03
*** zigo has quit IRC00:07
*** jecarey has quit IRC00:07
*** rmoe has quit IRC00:07
*** carl_baldwin has quit IRC00:10
*** ebalduf has quit IRC00:12
*** david-lyle has quit IRC00:12
*** alexandra has joined #openstack-meeting00:12
*** ebalduf has joined #openstack-meeting00:13
*** mattgriffin has joined #openstack-meeting00:13
*** annegent_ has quit IRC00:13
*** emagana_ has quit IRC00:13
*** zigo has joined #openstack-meeting00:13
*** emagana has joined #openstack-meeting00:14
*** asettle has quit IRC00:15
*** david-lyle has joined #openstack-meeting00:15
*** ebalduf has quit IRC00:17
*** comay has quit IRC00:18
*** emagana has quit IRC00:18
*** mchalla has quit IRC00:20
*** mchalla has joined #openstack-meeting00:21
*** dimsum_ has joined #openstack-meeting00:21
*** weshay has joined #openstack-meeting00:22
*** mchalla has quit IRC00:23
*** rmoe has joined #openstack-meeting00:24
*** comay has joined #openstack-meeting00:24
*** yeungp has joined #openstack-meeting00:27
*** annegent_ has joined #openstack-meeting00:29
*** mattgriffin has quit IRC00:29
*** annegent_ has quit IRC00:30
*** dboik has joined #openstack-meeting00:30
*** bdpayne has quit IRC00:31
*** tsekiyama has quit IRC00:33
*** nelsnels_ has joined #openstack-meeting00:36
*** andreaf has quit IRC00:37
*** dsetia has joined #openstack-meeting00:37
*** nelsnelson has quit IRC00:38
*** andreaf has joined #openstack-meeting00:38
*** dsetia_ has joined #openstack-meeting00:39
*** dsetia_ has quit IRC00:41
*** gokrokve has joined #openstack-meeting00:42
*** dsetia_ has joined #openstack-meeting00:42
*** markvan_ has quit IRC00:43
*** tsekiyama has joined #openstack-meeting00:44
*** leeantho has quit IRC00:44
*** markvan has joined #openstack-meeting00:44
*** baoli has joined #openstack-meeting00:45
*** dsetia_ has quit IRC00:46
*** marcoemorais has quit IRC00:48
*** VijayB_ has quit IRC00:50
*** mmedvede has quit IRC00:51
*** aysyd has quit IRC00:51
*** colinmcnamara has joined #openstack-meeting00:56
*** padkrish has quit IRC00:57
*** arnaud has quit IRC00:57
*** arnaud__ has quit IRC00:57
*** alexandra is now known as asettle00:57
*** dboik has quit IRC00:59
*** markwash__ has quit IRC00:59
*** padkrish has joined #openstack-meeting01:00
*** sdake_ has joined #openstack-meeting01:01
*** gokrokve has quit IRC01:02
*** gokrokve has joined #openstack-meeting01:03
*** amotoki has joined #openstack-meeting01:04
*** yamahata has joined #openstack-meeting01:04
*** vikas has quit IRC01:06
*** gokrokve has quit IRC01:07
*** js1123 has quit IRC01:08
*** yaguang has joined #openstack-meeting01:10
*** sdake_ has quit IRC01:11
*** ebalduf has joined #openstack-meeting01:12
*** s3wong has quit IRC01:12
*** yaguang has quit IRC01:13
*** weshay has quit IRC01:13
*** yaguang has joined #openstack-meeting01:13
*** otter768 has joined #openstack-meeting01:18
*** mberlin1 has joined #openstack-meeting01:18
*** mberlin has quit IRC01:19
*** topol has joined #openstack-meeting01:21
*** Longgeek has joined #openstack-meeting01:21
*** Mandell has quit IRC01:22
*** tsekiyama has quit IRC01:22
*** dane_leblanc has joined #openstack-meeting01:23
*** tsekiyam_ has joined #openstack-meeting01:23
*** tsekiyam_ has quit IRC01:23
*** VijayB has joined #openstack-meeting01:24
*** radez_g0n3 is now known as radez01:24
*** rushiagr_away is now known as rushiagr01:24
*** colinmcnamara has quit IRC01:25
*** rushiagr is now known as rushiagr_away01:26
*** andreaf has quit IRC01:27
*** Longgeek has quit IRC01:27
*** andreaf has joined #openstack-meeting01:27
*** mtanino has quit IRC01:28
*** dane_leblanc has quit IRC01:29
*** gokrokve has joined #openstack-meeting01:29
*** dane_leblanc has joined #openstack-meeting01:30
*** dsetia has quit IRC01:31
*** gokrokve has quit IRC01:31
*** gokrokve has joined #openstack-meeting01:31
*** xuhanp has joined #openstack-meeting01:36
*** padkrish has quit IRC01:38
*** otter768 has quit IRC01:40
*** sdake_ has joined #openstack-meeting01:40
*** otter768 has joined #openstack-meeting01:42
*** SumitNaiksatam has joined #openstack-meeting01:42
*** neelashah has joined #openstack-meeting01:44
*** novas0x2a|laptop has quit IRC01:48
*** Murali has quit IRC01:48
*** vivek-ebay has quit IRC01:49
*** SumitNaiksatam has quit IRC01:49
*** vivek-ebay has joined #openstack-meeting01:50
*** esker has joined #openstack-meeting01:51
*** tgraf has quit IRC01:52
*** vivek-ebay has quit IRC01:54
*** mchalla has joined #openstack-meeting01:55
*** alex_xu has joined #openstack-meeting01:55
*** tgraf has joined #openstack-meeting01:59
*** mchalla has quit IRC01:59
*** shivharis has quit IRC02:00
*** nosnos has joined #openstack-meeting02:02
*** alexandra has joined #openstack-meeting02:04
*** fnaval has quit IRC02:05
*** eghobo has quit IRC02:06
*** asettle has quit IRC02:07
*** vivek-ebay has joined #openstack-meeting02:08
*** matiu has joined #openstack-meeting02:11
*** bdpayne has joined #openstack-meeting02:19
*** sbalukoff has quit IRC02:20
*** ebalduf has quit IRC02:23
*** balajiiyer1 has left #openstack-meeting02:24
*** wuhg has joined #openstack-meeting02:25
*** stevemar has quit IRC02:25
*** stevemar has joined #openstack-meeting02:25
*** VijayB has quit IRC02:28
*** sdake_ has quit IRC02:32
*** alex_xu has quit IRC02:34
*** tsekiyama has joined #openstack-meeting02:34
*** tsekiyama has quit IRC02:39
*** salv-orlando has quit IRC02:40
*** david-lyle_ has joined #openstack-meeting02:42
*** alex_xu has joined #openstack-meeting02:43
*** david-lyle has quit IRC02:44
*** carl_baldwin has joined #openstack-meeting02:44
*** yaguang has quit IRC02:47
*** yaguang has joined #openstack-meeting02:47
*** padkrish has joined #openstack-meeting02:49
*** ramishra has joined #openstack-meeting02:52
*** padkrish has quit IRC02:54
*** vivek-ebay has quit IRC02:54
*** dimsum_ has quit IRC02:58
*** dimsum_ has joined #openstack-meeting02:59
*** otherwiseguy has joined #openstack-meeting03:00
*** epico has joined #openstack-meeting03:00
*** radez is now known as radez_g0n303:01
*** amotoki_ has joined #openstack-meeting03:01
*** ebalduf has joined #openstack-meeting03:02
*** dimsum_ has quit IRC03:03
*** shivharis has joined #openstack-meeting03:04
*** elo has joined #openstack-meeting03:06
*** dane_leblanc has quit IRC03:06
*** shivharis has quit IRC03:06
*** sdake_ has joined #openstack-meeting03:06
*** elo has quit IRC03:07
*** amotoki has quit IRC03:09
*** amotoki_ is now known as amotoki03:10
*** Longgeek has joined #openstack-meeting03:10
*** ebalduf_ has joined #openstack-meeting03:11
*** ebalduf has quit IRC03:13
*** kebray has quit IRC03:13
*** KanagarajM has joined #openstack-meeting03:14
*** ebalduf_ has quit IRC03:14
*** kebray has joined #openstack-meeting03:14
*** Longgeek has quit IRC03:15
*** peluse has quit IRC03:17
*** peluse has joined #openstack-meeting03:17
*** kebray has quit IRC03:17
*** kebray has joined #openstack-meeting03:18
*** mchalla has joined #openstack-meeting03:21
*** vivek-ebay has joined #openstack-meeting03:21
*** ivar-laz_ has joined #openstack-meeting03:21
*** otter768 has quit IRC03:22
*** otter768 has joined #openstack-meeting03:23
*** esker has quit IRC03:25
*** ivar-lazzaro has quit IRC03:25
*** mchalla has quit IRC03:25
*** ivar-laz_ has quit IRC03:26
*** nosnos has quit IRC03:26
*** bdpayne has quit IRC03:27
*** nosnos has joined #openstack-meeting03:27
*** yaguang has quit IRC03:28
*** vivek-ebay has quit IRC03:28
*** kebray has quit IRC03:28
*** kebray has joined #openstack-meeting03:29
*** armax has quit IRC03:30
*** nosnos has quit IRC03:32
*** otter768 has quit IRC03:33
*** vivek-ebay has joined #openstack-meeting03:33
*** ayoung has quit IRC03:35
*** ChuckC has quit IRC03:35
*** spzala has quit IRC03:36
*** vivek-ebay has quit IRC03:37
*** JRobinson__ is now known as JRobinson__afk03:39
*** JRobinson__afk is now known as JRobinson__lunch03:39
*** sbalukoff has joined #openstack-meeting03:41
*** Riddhi has joined #openstack-meeting03:42
*** Mandell has joined #openstack-meeting03:43
*** elo has joined #openstack-meeting03:54
*** kebray has quit IRC04:01
*** kebray has joined #openstack-meeting04:02
*** kebray has quit IRC04:02
*** gokrokve_ has joined #openstack-meeting04:02
*** kebray has joined #openstack-meeting04:03
*** jamespd has quit IRC04:04
*** jamespd has joined #openstack-meeting04:04
*** bradjones has quit IRC04:05
*** alexandra is now known as asettle04:05
*** gokrokve has quit IRC04:06
*** gokrokve_ has quit IRC04:07
*** JRobinson__lunch is now known as JRobinson__04:07
*** bradjones has joined #openstack-meeting04:07
*** garyh has quit IRC04:09
*** elo has quit IRC04:11
*** rajeshr has joined #openstack-meeting04:12
*** ramishra has quit IRC04:13
*** nosnos has joined #openstack-meeting04:16
*** emagana has joined #openstack-meeting04:18
*** SridharRamaswamy has joined #openstack-meeting04:21
*** kebray has quit IRC04:21
*** ramishra has joined #openstack-meeting04:21
*** vkmc has quit IRC04:21
*** kebray has joined #openstack-meeting04:23
*** bth- has quit IRC04:25
*** jang1 has joined #openstack-meeting04:26
*** jang1 has quit IRC04:27
*** elo has joined #openstack-meeting04:29
*** ngoswami has joined #openstack-meeting04:32
*** otherwiseguy has quit IRC04:40
*** garyh has joined #openstack-meeting04:40
*** rakesh_hs has joined #openstack-meeting04:46
*** timrc is now known as timrc-afk04:49
*** changbl has joined #openstack-meeting04:49
*** armax has joined #openstack-meeting04:50
*** rajeshr has quit IRC04:51
*** ajo_ has joined #openstack-meeting04:52
*** jang1 has joined #openstack-meeting04:52
*** ngoswami has quit IRC04:53
*** kebray has quit IRC04:54
*** jang1 has quit IRC04:54
*** ajo_ has quit IRC04:55
*** s3wong has joined #openstack-meeting04:58
*** aepifanov has joined #openstack-meeting04:59
*** vishwanathj has joined #openstack-meeting04:59
*** Riddhi has quit IRC04:59
yamahatahello!05:00
s3wonghello05:00
vishwanathjhi05:00
SridharRamaswamyHi05:00
yamahata#startmeeting servicevm-device-manager05:00
openstackMeeting started Tue Oct 21 05:00:40 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:00
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:00
openstackThe meeting name has been set to 'servicevm_device_manager'05:00
yamahatatoday Bob is absent unfortunately05:01
yamahata#topic Announcement05:01
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:01
yamahatasummit schedule is available. but Neutron schedule isn't fixed at this moment.05:01
yamahata#link http://kilodesignsummit.sched.org/05:01
yamahata#link https://openstacksummitnovember2014paris.sched.org/05:02
yamahataany other announcement?05:02
*** wendar_ is now known as wendar05:03
SridharRamaswamyyamahata: all: This is Sridhar Ramaswamy.   I'd like to actively participate in Tacker going forward.05:04
*** topol has quit IRC05:04
yamahataSridharRamaswamy: very cool.05:04
s3wongSridharRamaswamy: cool05:04
SridharRamaswamys3wong: yamahata: thanks!05:05
*** daneyon has quit IRC05:05
*** padkrish has joined #openstack-meeting05:05
*** daneyon has joined #openstack-meeting05:05
yamahataWill you go to paris? We are planning to have meeting(s) or BoF there.05:05
SridharRamaswamyI've met some of you in the last summit. Looking forward to meet you all in Paris05:05
yamahataI plan to discuss it later today.05:05
SridharRamaswamyyamahata: sounds good.. looking forward for the summit agenda for this subgroup05:06
yamahata#topic Action Items from the last week05:07
*** openstack changes topic to "Action Items from the last week (Meeting topic: servicevm-device-manager)"05:07
yamahataI contacted Karthik and he goes to Paris. Thesedays he has a conflict with this irc meeting.05:07
yamahata#topic summit logistics05:08
*** openstack changes topic to "summit logistics (Meeting topic: servicevm-device-manager)"05:08
yamahataI think we have enough people to have Bof/Meeting(s).05:08
yamahataThe issues is when/where.05:08
yamahataAccording to schedule, neutron session taks place on Wed, Tue, Fri.05:09
yamahataOops, Wed, thu, fir05:09
yamahataOn Tuesday, cross project will take place.05:09
*** padkrish has quit IRC05:10
yamahataOn Monday, opendaylight session on morning.05:10
*** padkrish has joined #openstack-meeting05:10
yamahataFor conference, Mainly session will take place on Mon, Tue(+ Wed morning)05:11
yamahataDo you have any preference for time?05:11
yamahataProbably another options would be morning or lunch time to avoid conflict05:12
yamahataOr evening before evening event.05:12
SridharRamaswamyyamahata: last time some of the BoF events like the NFV BoF took place around Lunch05:13
s3wongyamahata: also, today Steve Gordon talked about having a NFV subgroup BoF session05:13
*** kopparam has joined #openstack-meeting05:13
yamahata#link https://openstacksummitnovember2014paris.sched.org/event/f5bcb6033064494390342031e48747e3#.VEXnTnWUd1w win the telco BoF05:13
yamahataSure, we'd like to avoid NFV related sessions/BoFs.05:14
s3wongyamahata: naturally :-)05:14
SridharRamaswamyagree05:14
yamahata#action yamahata create poll page like NFV05:15
yamahataMaybe monday evening sounds good candidate. Anyway I'll create arbitration page on doodle or somewhere05:16
s3wongyamahata: +105:16
SridharRamaswamyyamahata: will we have an etherpad for this project05:17
yamahataSridharRamaswamy: +1 good idea.05:17
SridharRamaswamyreuse the current one ? https://etherpad.openstack.org/p/servicevm05:17
SridharRamaswamynot sure about the convention05:18
*** markwash__ has joined #openstack-meeting05:18
*** chandankumar has joined #openstack-meeting05:18
*** lazy_prince has quit IRC05:18
yamahataAdded the section for logistics of Kilo summit05:20
yamahata#action anyone add possible date/room and topics05:20
s3wongyamahata: assuming we don't get a Neutron design summit, we should look to book a time for the Neutron pod05:21
yamahatas3wong: sure. Do you know how to do it? For now, I'm not sure about booking room/pod TBH05:22
s3wongyamahata: normally it is signing up when we are there05:22
s3wongyamahata: also, it makes sense, since we have enough interested participants, to send an email to the ML05:23
*** mchalla has joined #openstack-meeting05:23
yamahatas3wong: sounds reasonable.05:23
s3wonglike how Steve Gorden does it with NFV BoF05:23
yamahata#action yamahata send an email to the ML on servicevm BoF/meeting05:24
*** gokrokve has joined #openstack-meeting05:25
yamahataOn Oct 28 next meeting, we would be fixing schedule05:25
s3wongyamahata: yes, it would be great to finalize schedule prior to the summit05:26
yamahataOkay, 3 mins left05:27
*** mchalla has quit IRC05:27
yamahata#topic Open Discussion05:27
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"05:27
yamahataanything else to discuss?05:28
*** emagana has quit IRC05:29
yamahataseems none.05:29
*** ngoswami has joined #openstack-meeting05:29
yamahatathank you everyone.05:29
*** emagana has joined #openstack-meeting05:30
s3wongthanks05:30
yamahatasee you next week and in Paris the next-next week.05:30
*** Sukhdev has joined #openstack-meeting05:30
SridharRamaswamythanks.. see you all next week05:30
*** harlowja is now known as harlowja_away05:30
vishwanathjbye05:30
yamahata#endmeeting05:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:30
openstackMeeting ended Tue Oct 21 05:30:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-21-05.00.html05:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-21-05.00.txt05:30
*** vishwanathj has quit IRC05:30
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-10-21-05.00.log.html05:30
*** otherwiseguy has joined #openstack-meeting05:31
*** gokrokve has quit IRC05:34
*** gokrokve has joined #openstack-meeting05:34
*** emagana has quit IRC05:34
*** SridharRamaswamy has quit IRC05:37
*** ildikov has joined #openstack-meeting05:37
*** BharatK has joined #openstack-meeting05:38
*** rakesh_hs2 has joined #openstack-meeting05:41
*** rakesh_hs has quit IRC05:41
*** Longgeek has joined #openstack-meeting05:41
*** s3wong has quit IRC05:44
*** JRobinson__ has quit IRC05:46
*** Longgeek has quit IRC05:47
*** reed has quit IRC05:47
*** david-lyle_ has quit IRC05:48
*** carl_baldwin has quit IRC05:49
*** ngoswami has quit IRC05:50
*** k4n0 has joined #openstack-meeting05:50
*** ngoswami has joined #openstack-meeting05:50
*** doron_afk has joined #openstack-meeting05:53
*** gokrokve has quit IRC05:57
*** gokrokve has joined #openstack-meeting05:58
*** andreaf has quit IRC05:58
*** andreaf has joined #openstack-meeting05:58
*** killer_prince has joined #openstack-meeting06:00
*** killer_prince is now known as lazy_prince06:00
*** neelashah has quit IRC06:01
*** gokrokve has quit IRC06:02
*** otherwiseguy has quit IRC06:02
*** mrunge has joined #openstack-meeting06:04
*** alex_xu has quit IRC06:06
*** lazy_prince is now known as killer_prince06:06
*** mrunge has quit IRC06:08
*** mrunge has joined #openstack-meeting06:08
*** pradipta_away is now known as pradipta06:12
*** SridharG has joined #openstack-meeting06:12
*** killer_prince is now known as lazy_prince06:12
*** SridharG has left #openstack-meeting06:13
*** Longgeek has joined #openstack-meeting06:15
*** chandankumar has quit IRC06:15
*** ramishra has quit IRC06:18
*** sileht has quit IRC06:19
*** armax has quit IRC06:19
*** alex_xu has joined #openstack-meeting06:20
*** evgenyf has joined #openstack-meeting06:20
*** adahms has quit IRC06:21
*** gokrokve has joined #openstack-meeting06:28
*** bagackiz has quit IRC06:30
*** hockeynut has quit IRC06:30
*** bagackiz has joined #openstack-meeting06:32
*** hockeynut has joined #openstack-meeting06:32
*** gokrokve has quit IRC06:33
*** alex_xu has quit IRC06:36
*** chandankumar has joined #openstack-meeting06:38
*** flaper87|afk is now known as flaper8706:39
*** skarn has quit IRC06:47
*** rm_work has quit IRC06:48
*** alex_xu has joined #openstack-meeting06:48
*** tris has quit IRC06:49
*** rm_work has joined #openstack-meeting06:49
*** rm_work has quit IRC06:49
*** rm_work has joined #openstack-meeting06:49
*** tris has joined #openstack-meeting06:50
*** skarn has joined #openstack-meeting06:51
*** comay has quit IRC06:53
*** Adri2000 has quit IRC06:54
*** padkrish has quit IRC06:54
*** markwash__ has quit IRC06:55
*** _nadya_ has joined #openstack-meeting06:56
*** Fdot has joined #openstack-meeting06:56
*** jtomasek has joined #openstack-meeting06:56
*** markwash__ has joined #openstack-meeting06:57
*** sseverson has quit IRC06:59
*** _nadya_ has quit IRC06:59
*** _nadya_ has joined #openstack-meeting07:00
*** _nadya_ has quit IRC07:00
*** Adri2000 has joined #openstack-meeting07:01
*** hashar has joined #openstack-meeting07:02
*** luqas has joined #openstack-meeting07:02
*** neeti has joined #openstack-meeting07:04
*** Sukhdev has quit IRC07:08
*** _nadya_ has joined #openstack-meeting07:08
*** noelbk has quit IRC07:08
*** andreykurilin_ has joined #openstack-meeting07:11
*** e0ne has joined #openstack-meeting07:12
*** amcrn has quit IRC07:20
*** MaxV has joined #openstack-meeting07:23
*** kopparam has quit IRC07:23
*** zz_ttrifonov is now known as ttrifonov07:24
*** kopparam has joined #openstack-meeting07:24
*** changbl has quit IRC07:24
*** mchalla has joined #openstack-meeting07:24
*** gokrokve has joined #openstack-meeting07:28
*** jgallard has joined #openstack-meeting07:28
*** mchalla has quit IRC07:28
*** elo has quit IRC07:29
*** markwash__ has quit IRC07:30
*** ttrifonov is now known as zz_ttrifonov07:31
*** mrmartin has joined #openstack-meeting07:32
*** gokrokve has quit IRC07:33
*** zz_ttrifonov is now known as ttrifonov07:33
*** kopparam has quit IRC07:33
*** kopparam has joined #openstack-meeting07:34
*** ttrifonov is now known as zz_ttrifonov07:36
*** shohel02 has joined #openstack-meeting07:37
*** dimsum_ has joined #openstack-meeting07:37
*** afazekas has joined #openstack-meeting07:38
*** andreaf has quit IRC07:38
*** kopparam has quit IRC07:38
*** SridharG has joined #openstack-meeting07:38
*** andreykurilin_ has quit IRC07:41
*** dimsum_ has quit IRC07:41
*** pnavarro has joined #openstack-meeting07:45
*** rajeshr has joined #openstack-meeting07:45
*** jlanoux has joined #openstack-meeting07:45
*** zz_ttrifonov is now known as ttrifonov07:45
*** ttrifonov is now known as zz_ttrifonov07:49
*** stevemar has quit IRC07:50
*** zz_johnthetubagu is now known as johnthetubaguy07:50
*** jcoufal has joined #openstack-meeting07:50
*** mitz has quit IRC07:52
*** safchain has joined #openstack-meeting07:52
*** johnthetubaguy is now known as zz_johnthetubagu07:53
*** stannie has joined #openstack-meeting07:54
*** alexpilotti has joined #openstack-meeting07:54
*** zz_ttrifonov is now known as ttrifonov07:54
*** lazy_prince is now known as killer_prince07:55
*** mitz has joined #openstack-meeting07:55
*** yamamoto has quit IRC07:56
*** ttrifonov is now known as zz_ttrifonov07:59
*** killer_prince is now known as lazy_prince07:59
*** zz_ttrifonov is now known as ttrifonov08:00
*** elo has joined #openstack-meeting08:03
*** pnavarro has quit IRC08:03
*** daneyon has quit IRC08:03
*** daneyon has joined #openstack-meeting08:04
*** zz_johnthetubagu is now known as johnthetubaguy08:04
*** padkrish has joined #openstack-meeting08:05
*** ygbo has joined #openstack-meeting08:05
*** pnavarro has joined #openstack-meeting08:05
*** daneyon has quit IRC08:07
*** ndipanov_gone is now known as ndipanov08:07
*** daneyon has joined #openstack-meeting08:08
*** mpaolino has joined #openstack-meeting08:09
*** padkrish has quit IRC08:09
*** berendt has joined #openstack-meeting08:10
*** kopparam has joined #openstack-meeting08:14
*** js1123 has joined #openstack-meeting08:17
*** kopparam has quit IRC08:18
*** yamahata has quit IRC08:21
*** pradipta is now known as pradipta_away08:22
*** nshaikh has joined #openstack-meeting08:24
*** jlibosva has joined #openstack-meeting08:27
*** nellysmitt has joined #openstack-meeting08:27
*** _nadya_ has quit IRC08:28
*** gokrokve has joined #openstack-meeting08:28
*** kopparam has joined #openstack-meeting08:30
*** e0ne has quit IRC08:30
*** lpeer has joined #openstack-meeting08:31
*** gokrokve has quit IRC08:33
*** markvoelker has quit IRC08:33
*** lsmola has quit IRC08:33
*** enikanorov has quit IRC08:34
*** markvoelker has joined #openstack-meeting08:34
*** sileht has joined #openstack-meeting08:35
*** mrmartin has quit IRC08:41
*** davidhadas has quit IRC08:43
*** igordcard has joined #openstack-meeting08:46
*** lsmola has joined #openstack-meeting08:46
*** hashar has quit IRC08:47
*** bradjones has quit IRC08:53
*** bradjones has joined #openstack-meeting08:53
*** igordcard has quit IRC09:03
*** oanufriev has quit IRC09:04
*** lsmola has quit IRC09:05
*** igordcard has joined #openstack-meeting09:07
*** JRobinson__ has joined #openstack-meeting09:08
*** pelix has joined #openstack-meeting09:09
*** yamamoto has joined #openstack-meeting09:09
*** alex_xu has quit IRC09:10
*** andreaf_ is now known as andreaf09:10
*** yamamoto has quit IRC09:15
*** hashar has joined #openstack-meeting09:16
*** lsmola has joined #openstack-meeting09:20
*** mpaolino has quit IRC09:21
*** mchalla has joined #openstack-meeting09:26
*** gokrokve has joined #openstack-meeting09:28
*** xuhanp has quit IRC09:29
*** mchalla has quit IRC09:30
*** salv-orlando has joined #openstack-meeting09:32
*** gokrokve has quit IRC09:33
*** Wiscontiy has joined #openstack-meeting09:35
*** e0ne has joined #openstack-meeting09:37
*** KanagarajM has quit IRC09:38
*** 1JTAAQZNO has joined #openstack-meeting09:40
*** yingjun has joined #openstack-meeting09:43
*** oanufriev has joined #openstack-meeting09:48
*** kingia has joined #openstack-meeting09:51
*** kingia is now known as iain_king09:51
*** evgenyf has quit IRC09:53
*** yamamoto has joined #openstack-meeting09:54
*** hashar_ has joined #openstack-meeting09:56
*** Wiscontiy has quit IRC09:58
*** hashar has quit IRC09:59
*** nosnos has quit IRC10:02
*** nosnos has joined #openstack-meeting10:03
*** _nadya_ has joined #openstack-meeting10:05
*** nosnos has quit IRC10:08
*** jgallard has quit IRC10:09
*** jcoufal has quit IRC10:10
*** evgenyf has joined #openstack-meeting10:12
*** ramishra has joined #openstack-meeting10:13
*** yamahata has joined #openstack-meeting10:13
*** colinmcnamara has joined #openstack-meeting10:17
*** JRobinson__ has quit IRC10:22
*** adahms has joined #openstack-meeting10:27
*** hashar_ is now known as hashar10:28
*** gokrokve has joined #openstack-meeting10:28
*** jlanoux_ has joined #openstack-meeting10:28
*** gokrokve has quit IRC10:29
*** gokrokve has joined #openstack-meeting10:30
*** jlanoux has quit IRC10:31
*** elo has quit IRC10:33
*** gokrokve has quit IRC10:35
*** ramishra has quit IRC10:36
*** jcoufal has joined #openstack-meeting10:38
*** rajeshr has quit IRC10:38
*** jcoufal has quit IRC10:39
*** jcoufal has joined #openstack-meeting10:39
*** bradjones has quit IRC10:45
*** bradjones has joined #openstack-meeting10:47
*** jlanoux has joined #openstack-meeting10:47
*** virmitio has joined #openstack-meeting10:48
*** jlanoux_ has quit IRC10:49
*** kopparam has quit IRC10:52
*** kopparam has joined #openstack-meeting10:53
*** ramishra has joined #openstack-meeting10:54
*** aepifanov has quit IRC10:56
*** ityaptin has quit IRC11:01
*** baoli has quit IRC11:02
*** IanGovett has joined #openstack-meeting11:03
*** doron_afk has quit IRC11:05
*** yamamoto has quit IRC11:11
*** BharatK has quit IRC11:12
*** ramishra has quit IRC11:14
*** mwagner_lap has quit IRC11:14
*** kopparam has quit IRC11:14
*** ddieterly has joined #openstack-meeting11:15
*** kopparam has joined #openstack-meeting11:16
*** ildikov has quit IRC11:20
*** ddieterl_ has joined #openstack-meeting11:20
*** dimsum_ has joined #openstack-meeting11:21
*** epico has quit IRC11:23
*** ddieterly has quit IRC11:23
*** miqui has quit IRC11:24
*** yingjun has quit IRC11:24
*** hashar has quit IRC11:25
*** BharatK has joined #openstack-meeting11:26
*** pnavarro has quit IRC11:27
*** mchalla has joined #openstack-meeting11:28
*** pnavarro has joined #openstack-meeting11:28
*** gokrokve has joined #openstack-meeting11:28
*** weshay has joined #openstack-meeting11:28
*** aysyd has joined #openstack-meeting11:29
*** mmedvede has joined #openstack-meeting11:29
*** adahms has quit IRC11:31
*** isviridov_away is now known as isviridov11:31
*** adahms has joined #openstack-meeting11:31
*** gokrokve has quit IRC11:32
*** mchalla has quit IRC11:33
*** kopparam has quit IRC11:37
*** _nadya_ has quit IRC11:37
*** BharatK has quit IRC11:37
*** pelix has quit IRC11:37
*** afazekas has quit IRC11:37
*** k4n0 has quit IRC11:37
*** asettle has quit IRC11:37
*** tgraf has quit IRC11:37
*** vijendar has quit IRC11:37
*** rwsu has quit IRC11:37
*** sunil_ has quit IRC11:37
*** ozamiatin has quit IRC11:37
*** jseutter has quit IRC11:37
*** coasterz has quit IRC11:37
*** larsks has quit IRC11:37
*** mrda has quit IRC11:37
*** tonyb has quit IRC11:37
*** obondarev has quit IRC11:37
*** tgraf has joined #openstack-meeting11:37
*** tonyb has joined #openstack-meeting11:37
*** mrda has joined #openstack-meeting11:37
*** sunil_ has joined #openstack-meeting11:37
*** vijendar has joined #openstack-meeting11:37
*** asettle has joined #openstack-meeting11:37
*** larsks has joined #openstack-meeting11:37
*** ozamiatin has joined #openstack-meeting11:37
*** afazekas has joined #openstack-meeting11:37
*** BharatK has joined #openstack-meeting11:37
*** jseutter has joined #openstack-meeting11:37
*** rwsu has joined #openstack-meeting11:37
*** coasterz has joined #openstack-meeting11:38
*** pelix has joined #openstack-meeting11:38
*** k4n0 has joined #openstack-meeting11:38
*** obondarev has joined #openstack-meeting11:38
*** flaper87 has quit IRC11:40
*** flaper87 has joined #openstack-meeting11:40
*** colinmcnamara has quit IRC11:41
*** Longgeek has quit IRC11:42
*** kopparam has joined #openstack-meeting11:42
*** luqas has quit IRC11:43
*** mrmartin has joined #openstack-meeting11:44
*** afazekas has quit IRC11:46
*** afazekas has joined #openstack-meeting11:46
*** k4n0 has quit IRC11:46
*** k4n0 has joined #openstack-meeting11:46
*** BharatK has quit IRC11:46
*** BharatK has joined #openstack-meeting11:46
*** pelix has quit IRC11:46
*** pelix has joined #openstack-meeting11:46
*** Longgeek has joined #openstack-meeting11:50
*** yamamoto has joined #openstack-meeting11:51
*** cbouch has joined #openstack-meeting11:51
*** dprince has joined #openstack-meeting11:52
*** baoli has joined #openstack-meeting11:53
*** yamamoto has quit IRC11:57
*** virmitio has quit IRC12:00
*** nati_ueno has joined #openstack-meeting12:00
*** cdub has quit IRC12:03
*** gholler has joined #openstack-meeting12:06
*** BharatK has quit IRC12:07
*** jgallard has joined #openstack-meeting12:09
*** mwagner_lap has joined #openstack-meeting12:11
*** adahms has quit IRC12:12
*** mrmartin has quit IRC12:12
*** hashar has joined #openstack-meeting12:15
*** mrmartin has joined #openstack-meeting12:16
*** dkranz has joined #openstack-meeting12:19
*** ildikov has joined #openstack-meeting12:20
*** BharatK has joined #openstack-meeting12:21
*** jungleboyj has joined #openstack-meeting12:23
*** rajeshr has joined #openstack-meeting12:23
*** fnaval has joined #openstack-meeting12:24
*** lpeer has quit IRC12:24
*** yamamoto has joined #openstack-meeting12:28
*** k4n0 has quit IRC12:28
*** gokrokve has joined #openstack-meeting12:28
*** yamamoto has quit IRC12:29
*** yamamoto has joined #openstack-meeting12:30
*** gokrokve has quit IRC12:33
*** MeganR has joined #openstack-meeting12:33
*** lpeer has joined #openstack-meeting12:34
*** yamamoto has quit IRC12:35
*** vkmc has joined #openstack-meeting12:35
*** topol has joined #openstack-meeting12:35
*** chandankumar has quit IRC12:37
*** neelashah has joined #openstack-meeting12:37
*** dimsum_ has quit IRC12:38
*** dimsum_ has joined #openstack-meeting12:39
*** timrc-afk is now known as timrc12:46
*** spzala has joined #openstack-meeting12:47
*** neeti has quit IRC12:47
*** doron has joined #openstack-meeting12:48
*** topol has quit IRC12:49
*** mchalla has joined #openstack-meeting12:51
*** kopparam has quit IRC12:52
*** kopparam has joined #openstack-meeting12:53
*** fnaval has quit IRC12:54
*** mchalla has quit IRC12:55
*** kopparam has quit IRC12:57
*** lazy_prince is now known as killer_prince12:57
*** julim has joined #openstack-meeting12:57
*** jckasper has joined #openstack-meeting12:58
*** doron is now known as doron_afk12:58
*** mcr-credil has left #openstack-meeting13:03
*** Sukhdev has joined #openstack-meeting13:04
*** iain_king has quit IRC13:05
*** mrunge has quit IRC13:06
*** luqas has joined #openstack-meeting13:06
*** rook has joined #openstack-meeting13:07
*** dkranz has quit IRC13:07
*** salv-orlando has quit IRC13:09
*** sdake_ has quit IRC13:09
*** sdake_ has joined #openstack-meeting13:09
*** sdake_ has quit IRC13:09
*** sdake_ has joined #openstack-meeting13:09
*** esheffield has joined #openstack-meeting13:10
*** jehb has joined #openstack-meeting13:11
*** yamahata has quit IRC13:11
*** amotoki has quit IRC13:11
*** yamahata has joined #openstack-meeting13:12
*** dane_leblanc has joined #openstack-meeting13:16
*** radez_g0n3 is now known as radez13:17
*** ddieterl_ has quit IRC13:17
*** bagackiz has quit IRC13:18
*** bagackiz has joined #openstack-meeting13:20
*** bagackiz has joined #openstack-meeting13:21
*** erlon_ is now known as erlon13:22
*** varora has joined #openstack-meeting13:22
*** bagackiz has joined #openstack-meeting13:22
*** nelsnels_ has quit IRC13:23
*** bagackiz has joined #openstack-meeting13:24
*** bagackiz has quit IRC13:24
*** nelsnelson has joined #openstack-meeting13:24
*** bagackiz has joined #openstack-meeting13:25
*** bagackiz has joined #openstack-meeting13:26
*** bagackiz has joined #openstack-meeting13:27
*** bagackiz has quit IRC13:27
*** _nadya_ has joined #openstack-meeting13:28
*** yamamoto has joined #openstack-meeting13:28
*** bagackiz has joined #openstack-meeting13:28
*** bagackiz has joined #openstack-meeting13:29
*** bknudson has joined #openstack-meeting13:29
*** bagackiz has joined #openstack-meeting13:30
*** bagackiz has joined #openstack-meeting13:31
*** bagackiz has joined #openstack-meeting13:32
*** jlanoux has quit IRC13:32
*** jckasper has quit IRC13:32
*** yamamoto has quit IRC13:33
*** 1JTAAQZNO has quit IRC13:33
*** jungleboyj has quit IRC13:35
*** amotoki has joined #openstack-meeting13:37
*** MeganR has left #openstack-meeting13:39
*** masayukig has quit IRC13:40
*** radez is now known as radez_g0n313:41
*** BharatK has quit IRC13:41
*** topol has joined #openstack-meeting13:43
*** Munish has joined #openstack-meeting13:44
*** obondarev_ has joined #openstack-meeting13:45
*** ddieterly has joined #openstack-meeting13:46
*** balajiiyer has joined #openstack-meeting13:46
*** masayukig has joined #openstack-meeting13:46
*** thangp has joined #openstack-meeting13:47
*** emagana has joined #openstack-meeting13:48
*** shadower has quit IRC13:49
*** jckasper has joined #openstack-meeting13:50
*** jckasper_ has joined #openstack-meeting13:51
*** armax has joined #openstack-meeting13:51
*** nelsnelson has quit IRC13:51
*** marun has joined #openstack-meeting13:51
*** shadower has joined #openstack-meeting13:51
*** nelsnelson has joined #openstack-meeting13:52
*** jschwarz has joined #openstack-meeting13:52
*** carl_baldwin has joined #openstack-meeting13:54
jschwarzhi carl_baldwin :)13:54
*** rajeshr has quit IRC13:54
carl_baldwinjschwarz: hi13:54
*** Murali has joined #openstack-meeting13:55
*** jckasper has quit IRC13:55
*** xuhanp has joined #openstack-meeting13:55
*** chandankumar has joined #openstack-meeting13:56
*** juzuluag has joined #openstack-meeting13:56
*** rkukura has joined #openstack-meeting13:56
*** stevemar has joined #openstack-meeting13:57
nati_uenohi13:57
rkukurahi13:57
mesterynati_ueno: Yo!13:57
jlibosvahi13:57
marunhi!13:57
marios_o/13:57
nati_uenomestery: yo!13:57
jschwarzhi!13:58
obondarev_o/13:58
armaxHi13:58
yamahatahi13:58
*** BrianB__ has joined #openstack-meeting13:58
*** ayoung has joined #openstack-meeting13:59
*** ihrachyshka has joined #openstack-meeting13:59
emaganaholas!14:00
*** rpothier has joined #openstack-meeting14:00
SukhdevHello14:00
ihrachyshkao/14:00
*** adrian-hoban has joined #openstack-meeting14:00
*** sambetts has joined #openstack-meeting14:00
carl_baldwinhi14:00
mestery#startmeeting networking14:00
openstackMeeting started Tue Oct 21 14:00:44 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
amotokihi14:00
openstackThe meeting name has been set to 'networking'14:00
*** absubram___ has joined #openstack-meeting14:00
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:00
mestery#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** gokrokve has joined #openstack-meeting14:01
mesteryOpenStack Juno is out! Yay!14:01
mestery#link http://lists.openstack.org/pipermail/openstack-announce/2014-October/000295.html14:01
*** dt_os has joined #openstack-meeting14:01
*** pc_m has joined #openstack-meeting14:01
mesteryAnd with it is Neutron:14:01
mestery#link https://launchpad.net/neutron/juno/2014.214:01
*** mchalla has joined #openstack-meeting14:01
*** erik____ has joined #openstack-meeting14:01
mesteryThanks to everyone for all your efforts for the past cycle.14:01
mesteryI know it was rought at times, but we pulled through as a team. Nice work everyone!14:01
*** mlavalle has joined #openstack-meeting14:01
SukhdevCongrats to the team!!!14:02
*** markmcclain has joined #openstack-meeting14:02
amotokiThanks all!!14:02
markmcclaino/14:02
nati_uenoCongrats!14:02
* marios_ looks forward to raising a beer with folks in a couple weeks14:02
mesteryNow that Juno is out, the ball keeps moving forward: On to Kilo!14:02
mesteryThe Kilo release schedule is available on the wiki here:14:02
mestery#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule14:02
*** ngoswami has quit IRC14:02
mesteryI also wanted to update folks that I'm working to settle on a mid-cycle location with the neutron-drivers team now.14:03
*** cody-somerville has quit IRC14:03
mesteryWe should be able to announce that next week.14:03
mesteryStay tuned for more details!14:03
emaganawow.. summit in Vancouver!14:03
mesteryemagana: Indeed, pretty awesome!14:03
emaganaI just noticed that!14:03
mesteryAny other announcements for the team?14:04
*** rbak has joined #openstack-meeting14:04
rkukuramestery: I don’t see anything on the agenda regarding the kilo design summit. Can you explain how session topics are being chosen, and where we are in that process?14:04
mesteryrkukura: Yes: We've had the public etherpad out there for the past 5 weeks, now that we've collected items there, the neutron-drivers team is putting the schedule together and it should be finalized by later this week.14:04
mesteryWe'll talk more about it next week during the meeting.14:04
rkukuraoh, the drivers14:04
*** jecarey has joined #openstack-meeting14:04
*** esker has joined #openstack-meeting14:04
jschwarzRegarding the release schedule, until when are we accepting new specs? when is the deadline to get them approved?14:05
mesteryjschwarz: I haven't proposed SPD/SAD yet, but it will be much earlier than it was in Juno.14:05
rkukuramestery: ML2 has been working on input for this14:05
mesteryStay tuned, I'll have those dates next week.14:05
jschwarzack, thanks14:05
mesteryrkukura: We only have 11 slots this time, and 2 half day round table sessions.14:05
*** esker has quit IRC14:06
mesteryrkukura: We're constrained severly. If you have input which is not on the etherpad, please let mek now.14:06
*** irenab has joined #openstack-meeting14:06
*** mchalla has quit IRC14:06
*** esker has joined #openstack-meeting14:06
mesteryOK, moving on in the agenda.14:06
mestery#topic Bugs14:06
rkukuramestery: there is way too much on the etherpad. We need an open process to narrow it down14:06
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:06
mestery#undo14:06
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x31aa2d0>14:06
mesteryrkukura: Exactly, this was brought up many weeks ago in this very meeting, something from salv-orlando on the fact we had 20 years worth of work there. :)14:07
marunrkukura: I think the point of the drivers team is to provide leadership when it comes to choosing priorities.14:08
*** bobmel has joined #openstack-meeting14:08
rkukuraI was expecting some communication as part of that process14:08
marunrkukura: I don't think anybody is preventing you from talking to the drivers team.14:08
rkukuralet move on14:08
*** boden has joined #openstack-meeting14:08
mesteryThe communication is coming, yes.14:08
amotokiI agree the driver team make things more transparency and need to explain how the schedule is decided.14:08
rkukuraDo they have an email list?14:09
emaganadrivers team: Please, take into consideration cross functional work such Third-party CI and Documentation!!!14:09
mesteryNo email list, we're just normal people with addresses.14:09
marunrkukura: you have working relationships with all of them.  Are you not able to use irc or the ml to raise issues?14:09
*** lzachery has joined #openstack-meeting14:09
rkukuraI was not aware the drivers were determining the summit schedule. I should have guessed that.14:09
marunrkukura: ah, fair enough.14:10
marunrkukura: That raises a good point - that should have been communicated better.14:10
*** jdurgin has quit IRC14:10
marunrkukura: I thought it was, but if you're unaware you may not be the only one.14:11
SukhdevI am assuming amotoki will be representing ML2 in the driver team when choosing priorities14:11
*** salv-orlando has joined #openstack-meeting14:11
mesteryI don't think there is any representing a specific team, we're all representing Neutron, and not just the drivers team, but each one of us.14:12
emaganawho are the drivers members again?14:12
mesteryWith all of that work proposed, the hard choices around what requires F2F time and can fill those 11 slots are usually made by the PTL.14:12
mesteryNow with the drivers team we're spreading this load a bit, so it's a net win IMHO.14:13
*** dboik has joined #openstack-meeting14:13
Sukhdevmestery: we have been discussing Kilo themes in ML2 meeting -14:13
*** ityaptin has joined #openstack-meeting14:13
*** chandankumar has quit IRC14:13
mesteryAlso, I hope everyone keeps this in mind:14:14
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2014-October/047954.html14:14
*** FJB has joined #openstack-meeting14:14
*** FJB has quit IRC14:14
mesteryNeutron priorities for Kilo, I sent this email weeks back14:14
mesteryJust refreshing folks memory here14:14
pc_memagana: #link https://wiki.openstack.org/wiki/Neutron-drivers14:14
amotokimestery: can we have an IRC meeting dedicated for summit planning if necessary? we can explain what's discussed among the driver team and everyone have chance to input.14:14
emaganapc_m: Thanks!14:14
mesteryamotoki: That's fine, lets do it during the drivers team slot this week,.14:14
amotokiweekly neutron meetng may be too short to discuss.14:14
mesteryamotoki: +114:15
*** ramishra has joined #openstack-meeting14:15
marunamotoki: +114:15
mesteryOK, we'll continue what should bea lively Summitt planning discussion on Wednesday during the Neutron drivers meeting.14:15
* mestery notes everyone should bring plenty of rotten tomatoes14:15
mestery#topic Bugs14:16
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:16
*** cody-somerville has joined #openstack-meeting14:16
marios_i spent some time poking at the criticals, for https://bugs.launchpad.net/neutron/+bug/1381617 I'd be grateful for any input on my proposal there (will likely start trying that tomorrow)14:16
uvirtbotLaunchpad bug 1381617 in neutron "Check for FIP status in scenario tests cause instability in neutron gate jobs" [Critical,Confirmed]14:16
mesteryI don't see our bug czar here, so I'm going to leave this open for bugs people want to discuss.14:16
mesteryAnd marun beat me to it :)14:16
mesterymarios_14:16
mesterynot marun14:16
*** irenab has quit IRC14:16
*** bradjones has quit IRC14:16
marios_also for https://bugs.launchpad.net/neutron/+bug/132365814:17
uvirtbotLaunchpad bug 1323658 in nova "Nova resize/restart results in guest ending up in inconsistent state with Neutron" [Critical,Confirmed]14:17
marios_wondering if anyone has a good repro?14:17
marios_logstash says it is indeed a thing. but can't hit it on my devstack box14:17
*** Mandell has quit IRC14:17
mesterymarios_: I used to be able to hit that one fairly regularly, but it's been a while.14:17
markmcclaindidn't salv-orlando do some digging into this one14:17
markmcclain?14:17
mesteryThat one has been around for a while.14:18
mesterymarkmcclain: Yes, he did14:18
*** dkranz has joined #openstack-meeting14:18
armaxThat last one bug is nasty14:18
mesteryThe findings are documented in the bug I believe14:18
armaxI can help with the FIP one14:18
marios_armax: yes thanks, my apologies i attributed your question to salvatore14:19
*** rmoe has quit IRC14:19
salv-orlandothere is no repro for that folks14:19
marios_armax: (on the comment)14:19
salv-orlandoI mean at least not one that you can easily reproduce. Mostly because it’s yet another bug with multiple root causes14:19
armaxWe are the Aliases of the same person14:19
*** glebo has joined #openstack-meeting14:19
armaxthat's OK14:19
armax:)14:19
salv-orlandowe slashed it when we pushed the fix for bug 1349617, then it periodically comes back.14:19
marios_:)14:19
uvirtbotLaunchpad bug 1349617 in tempest "SSHException: Error reading SSH protocol banner[Errno 104] Connection reset by peer" [Critical,Fix released] https://launchpad.net/bugs/134961714:20
glebolo. /me sorry bout being late14:20
salv-orlandotroubles is that it’s not just the network. This bug basically means: I dd an action to my instance, and when it came back I was not able to access it anymore14:20
*** jungleboyj has joined #openstack-meeting14:20
mesteryAny other bugs the team should be aware of today?14:21
marios_i also looked at https://bugs.launchpad.net/neutron/+bug/127403414:21
uvirtbotLaunchpad bug 1274034 in neutron "Neutron firewall anti-spoofing does not prevent ARP poisoning" [High,In progress]14:21
amotokiI would like to raise the ML thread: http://lists.openstack.org/pipermail/openstack/2014-October/010055.html14:21
marios_mestery: this one imo is a good 'technical debt' candidate and it has existing work14:21
*** ramishra has quit IRC14:21
amotokithe one I raised is not a real bug, but it is worth mentioned in the release note and the docs.14:22
marios_(Still marked 'in progress'. So the proper fix is to introduce ebtables. Some pushback in it being introduced here, perhaps needs to be stand alone etc)14:22
marios_but the headline for that particular bug is "no tenant isolation in neutron"14:22
mesterymarios_: Are you working with Juergen on that one?14:22
marios_mestery: no i didn't get that far i saw recent work so assumed it was between dev cycles stalled14:22
mesteryamotoki: Can you update the release notes with the output of that thread? That would be great!14:22
mesterymarios_: The issue with that one was the gigantic patch which was proposed at the end of Juno.14:23
marios_https://wiki.openstack.org/wiki/OSSN/OSSN-002714:23
amotokimestery: sure. I can cover the docs too.14:23
*** ramishra has joined #openstack-meeting14:23
mesteryAnd the fact it needed to be refactored to work with both iptables and ipset I believe.14:23
mesteryamotoki: Thanks!14:23
glebo"no tenant isolation in neutron" . That's a pretty rough pill to swallow for the operator community.14:23
marios_mestery: yes that was my take-away from reading the various threads there14:23
marios_glebo: yes of course. its of course a sensasionalist headline and is not all that bad14:23
*** marun has quit IRC14:24
*** balajiiyer has left #openstack-meeting14:24
*** rmoe has joined #openstack-meeting14:24
marios_glebo: no sorry, it is pretty bad but not like the headline suggests :)14:24
*** yaguang has joined #openstack-meeting14:24
mesterymarios_: Can you ping Jeurgen on this one and see where he's at with this? I'm concerned he hasn't popped up on the ML or meeting to discuss the solution here, nor has he worked with you on the ipset/iptables refactor to include the ebtables work here.14:24
glebomarios_: ha14:24
marios_mestery: sure will make a note of that14:25
mesterymarios_: Thanks!14:25
mesteryOK, lets move on in the agenda then.14:26
mestery#topic Docs14:26
*** openstack changes topic to "Docs (Meeting topic: networking)"14:26
mesteryemagana: Hi there!14:26
emaganaHello!14:26
*** reed has joined #openstack-meeting14:26
*** armax has quit IRC14:26
emaganamestery: This morning I updated the wiki with some progress on the bugs related to Docs14:26
mesteryemagana: Fantastic, thanks!14:26
*** armax has joined #openstack-meeting14:26
amotoki#link https://wiki.openstack.org/wiki/Network/Meetings#Docs_.28emagana.2914:27
*** jdurgin has joined #openstack-meeting14:27
mesteryemagana: Anything else on docs for this week?14:27
emaganaI also notified the Docs team that is working on Networking the agreement of last week about having DVR and L3 HA as new features within the Docs14:27
mesteryVery good!14:28
emaganamestery: Very few bugs have been opened by this team, we should review more the Documentation of our own staff!!!14:28
*** yamamoto has joined #openstack-meeting14:28
amotokiemagana: will stable/juno on docs repo be cut about a month later?14:28
*** mpaolino has joined #openstack-meeting14:28
*** gokrokve has quit IRC14:28
*** bradjones has joined #openstack-meeting14:29
emaganaamotoki: Actually not all of them, for instance install guide is cut tomorrow14:29
*** gokrokve has joined #openstack-meeting14:29
*** chandankumar has joined #openstack-meeting14:29
*** atiwari has joined #openstack-meeting14:29
emaganathe rest of the documentation will be14:29
*** nshaikh has quit IRC14:29
amotokiemagana: thanks. If we find docs bugs, let's fix them.14:29
emaganaamotoki: Yes!14:30
emaganamestery: Nothing else!14:30
mesteryemagana: Thank you sir!14:30
mesteryOK, moving on.14:30
emaganamestery: }=)14:30
mestery#topic Non-NSX VMware Driver Discussion14:31
*** openstack changes topic to "Non-NSX VMware Driver Discussion (Meeting topic: networking)"14:31
mesteryThis may be a short topic14:31
mesterySince garyk isn't here :)14:31
mesteryI had proposed to have this discussion during this slot as there are 3 BPs for non-NSX drivers in neutron-specs14:31
mesteryAnd armax and garyk have been working to figure out overlap14:31
salv-orlandoit’s funny I work for vmware and I hardly know what we’re talking about14:31
mesterysalv-orlando: You must not talk to garyk much ;)14:31
*** mattgriffin has joined #openstack-meeting14:31
armaxmestery: I’ll sync up with gary14:31
mesteryarmax: Yes, please do, and we can add this to next week's agenda if gary wants, since he proposed this to me. :)14:32
*** fnaval has joined #openstack-meeting14:32
salv-orlandomestery: we talk, but about other stuff14:32
mestery#topic Neutron Peer Review Process14:32
armaxmestery: we need to figure out whether this stuff will live in neutron or outside14:32
*** openstack changes topic to "Neutron Peer Review Process (Meeting topic: networking)"14:32
mestery#undo14:32
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x31379d0>14:32
*** yaguang has quit IRC14:32
*** yamamoto has quit IRC14:32
mesteryarmax: Yes, that was one of gary's concerns too14:32
mesteryAnd waht could be reused across the drivers, etc.14:32
*** yaguang has joined #openstack-meeting14:33
*** markwash__ has joined #openstack-meeting14:33
armaxmestery: right, we’ll get it sorted this cycle14:33
ihrachyshkaweren't we going to nuke all drivers from the tree?14:33
mesteryarmax: Cool, thanks!14:33
armaxihrachyshka: that remains to be discussed at the summit14:33
mesteryihrachyshka: We didn't say which tree this would live in ;)14:33
armaxihrachyshka: but if that was true, the moment is ripe for having the esx stuff happens out of tree14:33
*** davidhadas_ has joined #openstack-meeting14:33
*** andreaf has quit IRC14:33
armaxmestery, ihrachyshka: we’ll work that out this cycle14:34
mesteryOK, thanks armax!14:34
mestery#topic Neutron Peer Review Process14:34
*** openstack changes topic to "Neutron Peer Review Process (Meeting topic: networking)"14:34
mesteryPer last week's discussion, I'll be rolling this out this week.14:34
gleboihrachyshka: thta's what I have been hearing consensus around, and maestry: I haven't really heard the "here's what we do now that they are out" plan14:34
mesteryI'm close to having the Google Forms stuff sorted out, expect this to happen by tomorrow.14:35
ihrachyshkamestery: what's that process about? link?14:35
mesteryI just wanted to note this in the meeting for folks.14:35
mestery#link https://etherpad.openstack.org/p/neutron-peer-review14:35
ihrachyshkatnx14:35
mesteryihrachyshka: ^^^14:35
emaganamestery: You are implementing a review process with just a couple of weeks of being annouced?14:35
mesteryemagana: Indeed sir. If it takes people more than 10 minutes than they shoudl ask for help. :)14:36
mesteryemagana: The idea is to collect the data before the Summit.14:36
rkukura?14:36
emaganamestery: which data?  I am confused, what are these google forms about exactly?14:36
*** bradjones has quit IRC14:37
mesteryBackground was discussed last week during the meeting, emagana I think you were here even:14:38
mestery#link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-13-21.02.log.html14:38
*** eharney has joined #openstack-meeting14:38
*** salv-orlando has quit IRC14:38
*** ChuckC has joined #openstack-meeting14:38
glebomestery:  the discussion on this topic last week was very good, and certainly there were several points of input and suggestion14:38
gleboI haven't seen much comment14:39
gleboon the etherpad about it yet14:39
emaganamestery: If everybody understands these forms and the reason behind them and the conclusion about last week I shut my mounth..14:39
mesteryglebo: Right, no one commented at all.14:39
* glebo guilty for not commenting my review, as promised14:39
rkukuraemagana: I had no clue we were considering implementing this prior to the summit14:39
* mestery notes no one commented on the etherpad after last week's meeting.14:39
*** derekh has joined #openstack-meeting14:39
mesteryDid people just not have enough time?14:39
glebobut there are some pretty strong views about how this could be done effectively14:39
glebomestery: for me, yes.14:40
* Sukhdev I thought the discussion was to continue in this week's meeting14:40
gleboI fully intend to review and comment with some of the input I gave in last week's mtg.14:40
emaganarkukura: Ni neither! but it seems mestery has made a decision14:40
gleboon the epad14:40
jschwarzI didn't see a ML thread about it and wasn't even aware this was in the works. Looks good btw14:40
*** ramishra has quit IRC14:40
amotokiin my understand, the peer review proposed is our big challenge on how to manage a core team of a project.14:40
emaganaSukhdev: Same here but same comment that before!14:40
mesteryFolks, I'm on IRC everyday,, all the time, I read email, etc.14:40
mesteryPlease don't be afraid to reach out to me14:40
* glebo feels strongly that the process needs to be more open and less "closed network of hand picked reviewers" type of thing14:41
emaganamestery: I am reaching you out now! In the right forum. What is wrong with that?14:41
*** vijendar has quit IRC14:41
glebotoo much oppty for things to go sideways, as currently stands14:41
mesteryemagana: Nothing at all.14:41
*** marun has joined #openstack-meeting14:41
*** AlanClark has joined #openstack-meeting14:41
mesteryIn fact, I'm willing to delay this to address your concerns :)14:41
*** vijendar has joined #openstack-meeting14:41
*** rmoe has quit IRC14:41
glebobut, to reiterate, I'm 100% in support of a review process overall. GREAT leadership step14:41
mesteryWe have 19 minutes :P14:41
mesteryglebo: Thanks.14:41
amotokiAs etherpad says, the first round is a kind of trial. we are exploring the process.14:42
mesteryamotoki is spot on.14:42
markmcclainglebo: I don't think that until the we've run a sample run that attempting at a wide scale is wise14:42
emaganamestery: It seems and I am not the only one confused about it. I am supportive of the peer review but I want to find more clarity. Please, tell me what to do?14:42
mesteryemagana: How about this: Can you comment on that etherpad? We can also discuss now and in-channel today.14:42
* marun wishes he hadn't joined this conversation late14:43
marunI'm also confused as to why concerns weren't raised this past week.14:43
*** rmoe has joined #openstack-meeting14:43
glebomarkmcclain: sorry, mark, attempting what?14:43
emaganamestery: Ok!14:43
marunIt was made clear that feedback was appreciated.14:43
*** reed has quit IRC14:43
marunAnd zero feedback was provided.14:43
marunWhat gives?14:43
emaganamarun: +114:43
*** reed has joined #openstack-meeting14:43
marunIf nobody actually cared, I could understand.14:43
marunBut if you cared and didn't raise your voice, who's fault is that?14:44
gleboemagana: I also understood last week that the action item for those of us with input was to comment on epad,14:44
markmcclainglebo: wide feedback vs a smaller sample14:44
*** SridharG has quit IRC14:44
*** zz_jgrimm is now known as jgrimm14:44
amotokithe discussion just starts. if you have a question, don't hesitate to raise :-)14:44
glebobut I also think we need to promote and advertise this process a bit more on the mail list14:44
mesteryFolks, I am obviously VERY OPEN to feedback, but when we ask for it and get none, that leads me to believe people are ok with what is proposed.14:44
nati_uenoI thought I did feedback, but I found actually I didn't. I'm +1 for this process.14:44
marunglebo: I'm curious as to what your stake in this, frankly.14:44
glebomestery: how would u feel about a bit more advert on the ml?14:44
marunglebo: The point is to try to get feedback to the cores so they can improve.14:45
emaganamarun: I care but I am also in the top of many things! CI, Docs and My current job!  I am investing time on this meeting expressing my concerns and now I have been asked to spend more time in commenting in a different time14:45
amotokiemagana: you are leading cross project topics MUCH!14:45
glebomestery: understandable reaction to a week of total silence. for me, just been busy. SHould have at least told u that so's u didn't take silence as consensus14:45
emaganamarun: I find it unfair!14:45
marunemagana: why?14:45
glebomestery: my bad14:45
emaganaglebo: +1 I second that!14:46
marunSo, you have concerns.14:46
marunAnd then stay silent.14:46
marunMust have been important concerns14:46
marun?14:46
*** Riddhi has joined #openstack-meeting14:46
emagananot silent just busy and I did not know it will be implemented right away!  I am expresing concerns not believing that this is the right forum14:46
marunemagana: What exactly is your concern?14:47
armaxcould these concerns be so serious that they cannot be addressed while we see how this thing actually works in motion?14:47
marunemagana: It's a feedback mechanism.14:47
* glebo thinks maybe for a step this big a two or three weeks is an acceptable comment period. 14:47
mesterymarun: +100014:47
emaganamestery: I asked last week how much time was expected per week per core in NEutron, what was the response?14:47
*** kebray has joined #openstack-meeting14:47
marunemagana: It's not a tool to push anyone off core.14:47
mesteryemagana: The response is it's not something which we can document like that.14:47
gleboI just never expected the whole comment and discussion window to be 1 week long. And we all know what they say about when I assume...14:48
mesteryemagana: It's different for each person, for each week, etc.14:48
marunemagana: If anyone of us is not meeting each other's expectations, that's just information.14:48
marunemagana: If the consensus is, we need to do more, we'll all know it.14:48
marunemagana: If the consensus is, we're doing enough or we can do less, we can decide that too.14:48
emaganamarun: I understand that part and I agree with that, performance feedback is needed!14:48
*** Mandell has joined #openstack-meeting14:48
*** SridharG has joined #openstack-meeting14:48
marunemagana: I'm still not clear on your concern, then.14:48
emaganamestery: But we all need to know the expectation!14:49
marunemagana: You are unwilling to have us all deliver feedback as to whether we are meeting each other's expectations?14:49
mesteryemagana: Expecatation on what? How much time you need to spend reviewing patches? Specs? Interacting on IRC? I'm confused.14:49
gleboand the summary of my input is that the process needs to be more open, and more self selecting. i.e.14:49
emaganamestery: Yes, that is one of them14:49
marunemagana: If there is a perceived issue for any one of us, the goal is finding ways to get better.14:49
marunemagana: I'm not sure why that would be contentious.14:50
mesteryemagana: Like I said, htere is no hard minimum or limit on that.14:50
emaganamarun: I am open to feedback14:50
amotokiI understand there are several ways to contributing the community and core status motivates persons!14:50
marunemagana: I am having a hard time understanding your desire for 'a number of hours'14:50
marunemagana: Constructive participation is not something you can measure in hours.14:50
marunemagana: That's the whole point of the proposal...14:50
gleboif leaders are hand picking specific "in the club" other leaders to provide "unbiased performance reviews" then the tool is really just for leaders to get the opinions of people they want to listen to, and not to genuinely open up to community feedback14:51
marunemagana: To get a more holistic view of what we all think about being core.14:51
marunemagana: Rather than relying on numbers like review stats or number of hours.14:51
glebothat process is fine for a corp. It's laden with issues for an open community, like OpenSource or Standards14:51
amotokiemagana: there are many ways to express "community leadership". no worries. we know!14:51
mesteryglebo: I don't follow that, and why would you think that's what's happening here? That's a baseless accusation which isn't adding anything to the discussion.14:51
marunglebo: Uh...14:51
emaganamarun: Maybe I am overreacting here. I just want to be sure that peer review is well understood by everybody14:51
marunglebo: I'm having a hard time accepting your criticism.14:51
mesteryglebo: Have you read the etherpad>14:51
*** noelbk has joined #openstack-meeting14:51
mestery?14:51
marunglebo: Have you been reviewing code and I haven't noticed?14:52
glebomestery:  whoa, that was a pretty strong reaction, m.14:52
mesteryglebo: Indeed, that was a strong accusation.14:52
gleboI don't recall making an accusation, least i didn't mean to, not in the least.14:52
mesteryglebo: Please re-read the etherpad and comment there if you have concerns.14:52
amotokiI hope you all who are interested in this topics read the whole content on the epad. After reading the whole, you will see various metrix.14:52
gleboAs stands, the process is that a leader hand picks people they trust to provide feedback on another person, no?14:52
marunglebo: We're a group of people who are overburdened.14:52
marunglebo: The goal is figuring out how to be more effective.14:52
*** hashar has quit IRC14:53
marunglebo: It's not something we intend to use to deny bonuses or promotion.14:53
glebomarun:  100% agree with that14:53
*** Mandell has quit IRC14:53
emaganamestery: It is not my intention to slow down the progress of this excellent initiative! On the contrary I am onboard. With the caveat that I don't understand many things!14:53
*** absubram___ has quit IRC14:53
mesteryglebo: Someone has to pick the reviewers, we'll iterate on this, but yes, initially it's the PTL. I'm sure you coudl see the issues with opening voting for who reviews who.14:53
mesteryAnd eveyrone reviewing everyone isnt' scalable.14:53
*** mrmartin has quit IRC14:53
*** kebray has quit IRC14:53
nati_uenomarun: oh I thought person with good score get some beers from PTL14:54
marunemagana: Feel free to ask questions, then.  There are no secrets here.14:54
glebomarun:  in the spirit of being more effective, is a small, closed group of reviewers the most effective, or is an open, provide feedback as you have interactions more effective?14:54
emaganamarun: Is not what have been doing for the last 10 minutes?14:54
glebomarun: if we look at models that are WILDLY successful in the industry,14:54
marunglebo: uh.14:54
*** david-lyle_ has joined #openstack-meeting14:54
glebomarun:  the reputation systems are doing a FANTASTIC job of helping communities self police14:54
marunglebo: I don't know what you're talking about.14:55
glebo, and self guide and self shape behaviors in line with the goals of the system14:55
glebomarun: you've never heard of a reputation system?14:55
marunglebo: We have a reputation system.14:55
*** stevemar has quit IRC14:55
glebomarun: every used ebay?14:55
marunglebo: ffs14:55
* ihrachyshka noting: 5 mins left14:55
mesteryFolks14:56
mesteryLets move on from this now.14:56
-amotoki- good reminder14:56
mesteryPlease provide feedback on the etherpad14:56
marunglebo: You're seriously going to point to some kind of gamification to support an open source community.14:56
*** stevemar has joined #openstack-meeting14:56
marunglebo: Just stop.14:56
mesteryAnd ML if you want.14:56
armaxglebo: you mean, like LP karma points?14:56
markmcclainmestery: +1000 … Open Discussion please14:56
glebomarun:  every read comments on a mobile app you were thinking about loading?14:56
ihrachyshkaI don't see how discussion here moves the process forward. let's move to etherpad.14:56
mestery#topic Open Discussion14:56
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:56
mesteryFolks lets move on14:56
mesteryWe're degraded now.14:56
marios_mestery: you mentioned opening up this week's drivers meeting (wednesday?) for the summit planning discussion. but i can't see time @ https://wiki.openstack.org/wiki/Network/Meetings or https://wiki.openstack.org/wiki/Neutron-drivers14:56
* mestery looks14:56
markmcclain2pm UTC14:57
mesterymarios_: https://wiki.openstack.org/wiki/Meetings#neutron-drivers_weekly_IRC_meeting14:57
mestery#link https://wiki.openstack.org/wiki/Meetings#neutron-drivers_weekly_IRC_meeting14:57
glebomarun: u r way out of line, sir14:57
mesteryglebo and marun: We've moved on, please discontinue this discussion.14:57
*** cdub has joined #openstack-meeting14:57
marios_mestery: markmcclain: thanks14:58
ihrachyshkaI have one thing to note: during kilo, we need to migrate to multiple graduated oslo libraries, and the sooner the better, so I will appreciate if people start reviewing the following pieces. For the start, this patch and its two dependencies: https://review.openstack.org/#/c/127257/ (especially the policy thing that blocks several further patches)14:58
mesteryAnything else here folks?14:58
*** otherwiseguy has joined #openstack-meeting14:58
* markmcclain needs to get better at TZ math14:58
*** jdandrea has joined #openstack-meeting14:58
mesteryihrachyshka: thanks for the reminder! I see amotoki has a similar patch for python-neutronclient as well.14:58
ihrachyshkamarkmcclain: google is great at it14:58
rkukuramestery: Please put a link the drivers meeting logs on https://wiki.openstack.org/wiki/Meetings/NeutronDrivers14:58
markmcclainihrachyshka: thanks for working on this14:58
ihrachyshkamestery: yes, https://review.openstack.org/12889614:59
amotokiI think ihrachyshka and me are in the same page. the policy one needs careful reviews.14:59
mesteryrkukura: Ack14:59
markmcclainihrachyshka: sadly I was trying to do math before drinking coffee… never ends well :)14:59
ihrachyshkaamotoki: indeed it requires care, not a mechanical change14:59
*** virmitio has joined #openstack-meeting14:59
mesteryOK folks, we're at the end.14:59
*** eharney has quit IRC14:59
mesteryHope to see folks back next week for another lively discussion!14:59
mesteryThanks!14:59
mestery#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Oct 21 14:59:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-21-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-21-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-10-21-14.00.log.html15:00
*** pnavarro has quit IRC15:00
*** mlavalle has left #openstack-meeting15:00
*** david-lyle_ has quit IRC15:00
*** rkukura has left #openstack-meeting15:00
Sukhdevmarkmcclain: the link says the driver meeting is at 1500 UTC - you mentioned 2pm UTC15:00
*** pc_m has left #openstack-meeting15:00
nati_uenobye15:00
Sukhdevthanks folks15:00
amotokiSukhdev: 3pm is correct.15:00
*** padkrish has joined #openstack-meeting15:00
markmcclainSukhdev: I was wrong… hence my comment on bad TZ math15:00
Sukhdevamotoki: Thanks for clarifying15:01
*** stevemar has quit IRC15:01
*** obondarev_ has quit IRC15:01
*** stevemar has joined #openstack-meeting15:01
Sukhdevmarkmcclain: BTW, that makes two of us I am terrible with TZ math as well - hence, have to always double check :-)15:01
*** padkrish has quit IRC15:02
*** eharney has joined #openstack-meeting15:02
*** mattgriffin has quit IRC15:02
*** padkrish has joined #openstack-meeting15:02
*** carl_baldwin has quit IRC15:03
*** markwash__ has quit IRC15:04
*** Sukhdev has quit IRC15:04
edleafeAre we having a Gantt meeting today?15:04
*** virmitio has left #openstack-meeting15:04
*** marun has quit IRC15:05
*** marun has joined #openstack-meeting15:05
*** nati_ueno has quit IRC15:06
*** dt_os has quit IRC15:06
*** david-lyle has joined #openstack-meeting15:06
*** Sukhdev has joined #openstack-meeting15:08
timelloo/15:08
*** thedodd has joined #openstack-meeting15:09
edleafetimello: Looks like it's just us...15:10
*** glebo has left #openstack-meeting15:11
*** mattgriffin has joined #openstack-meeting15:11
*** neelashah has quit IRC15:11
*** enikanorov has joined #openstack-meeting15:12
*** vijendar1 has joined #openstack-meeting15:12
*** ramishra has joined #openstack-meeting15:14
timellomaybe n0ano is not around15:14
*** vijendar has quit IRC15:15
*** padkrish has quit IRC15:16
edleafeNor bauzas, I assume15:16
*** jcoufal has quit IRC15:16
*** Mandell has joined #openstack-meeting15:17
*** ramishra has quit IRC15:21
*** mtanino has joined #openstack-meeting15:21
*** pnavarro has joined #openstack-meeting15:22
*** dpaterson has joined #openstack-meeting15:22
*** radez_g0n3 is now known as radez15:22
*** yaguang has quit IRC15:24
*** chandankumar has quit IRC15:24
*** pnavarro has quit IRC15:24
*** jlibosva has quit IRC15:25
*** neelashah has joined #openstack-meeting15:25
*** rakesh_hs2 has quit IRC15:25
*** cdub has quit IRC15:26
*** enikanorov has quit IRC15:26
*** cody-somerville has quit IRC15:26
*** padkrish has joined #openstack-meeting15:26
*** Mandell has quit IRC15:27
*** tsekiyama has joined #openstack-meeting15:27
*** IanGovett has quit IRC15:27
*** dprince has quit IRC15:27
*** dprince has joined #openstack-meeting15:27
*** eyald has joined #openstack-meeting15:27
*** yamamoto has joined #openstack-meeting15:28
*** pnavarro has joined #openstack-meeting15:28
*** igordcard has quit IRC15:29
*** hemna has joined #openstack-meeting15:30
*** padkrish has quit IRC15:31
*** igordcard has joined #openstack-meeting15:31
*** padkrish has joined #openstack-meeting15:31
*** rpothier has left #openstack-meeting15:31
*** IanGovett has joined #openstack-meeting15:32
*** yamamoto has quit IRC15:33
*** jschwarz has quit IRC15:34
*** berendt has quit IRC15:36
*** yamamoto has joined #openstack-meeting15:36
*** alexpilotti has quit IRC15:38
*** gyee has joined #openstack-meeting15:39
*** hashar has joined #openstack-meeting15:40
*** marcoemorais has joined #openstack-meeting15:40
*** sseverson has joined #openstack-meeting15:40
*** yamamoto has quit IRC15:41
*** primeministerp has joined #openstack-meeting15:41
*** primemin1sterp has joined #openstack-meeting15:41
*** primemin2sterp has joined #openstack-meeting15:41
*** primemin2sterp has quit IRC15:42
*** primemin1sterp has quit IRC15:42
*** primeministerp has quit IRC15:42
*** 14WAADG9C has joined #openstack-meeting15:43
*** 7GHAAEFQK has joined #openstack-meeting15:43
*** primeministerp has joined #openstack-meeting15:43
*** mchalla has joined #openstack-meeting15:43
*** changbl has joined #openstack-meeting15:43
*** nonameentername has joined #openstack-meeting15:45
*** otherwiseguy has quit IRC15:47
*** pradk has joined #openstack-meeting15:47
*** rmoe has quit IRC15:47
*** jdurgin1 has joined #openstack-meeting15:47
*** jdurgin1 has quit IRC15:47
*** mchalla has quit IRC15:48
*** Sukhdev has quit IRC15:48
*** otherwiseguy has joined #openstack-meeting15:48
*** mfedosin has joined #openstack-meeting15:50
*** pnavarro has quit IRC15:51
*** bobmel has quit IRC15:51
*** gokrokve has quit IRC15:52
*** padkrish has quit IRC15:55
*** emagana has quit IRC15:55
*** padkrish has joined #openstack-meeting15:55
*** emagana has joined #openstack-meeting15:56
*** oanufriev has quit IRC15:56
*** ilyashakhat has quit IRC15:57
*** SridharRamaswamy has joined #openstack-meeting15:57
*** aarefiev has quit IRC15:58
*** padkrish_ has joined #openstack-meeting15:58
*** padkrish has quit IRC15:58
*** virmitio has joined #openstack-meeting15:59
*** xuhanp has quit IRC16:00
*** emagana has quit IRC16:00
*** ociuhandu has joined #openstack-meeting16:01
*** alexpilotti has joined #openstack-meeting16:01
*** Tufin has joined #openstack-meeting16:02
*** SridharG has left #openstack-meeting16:02
*** ildikov has quit IRC16:02
*** cjellick has joined #openstack-meeting16:02
primeministerp#startmeet openstack16:02
primeministerp#startmeet hyper-v16:02
primeministerphmm16:03
primeministerpno bot today16:03
primeministerpalexpilotti: ping16:03
*** yamahata has quit IRC16:03
*** markmcclain has quit IRC16:03
*** emagana has joined #openstack-meeting16:03
*** SridharRamaswamy has quit IRC16:04
*** alexpilotti_ has joined #openstack-meeting16:04
primeministerpalexpilotti_: ping16:04
*** shohel02 has quit IRC16:04
alexpilotti_hey there16:05
ociuhanduhi all :)16:05
primeministerpalexpilotti_: ready?16:06
*** jhenner has quit IRC16:06
primeministerpalexpilotti_: blueprint updates?16:06
primeministerpluis can't make it today16:07
alexpilotti_yep16:07
primeministerpwe can make it quick16:07
*** alexpilotti has quit IRC16:07
*** alexpilotti_ is now known as alexpilotti16:07
*** MarkAtwood has joined #openstack-meeting16:07
alexpilottitopic? :-)16:07
primeministerpno bot16:07
primeministerpblueprint status?16:07
alexpilottireally? wow16:08
primeministerp#topic blueprints16:08
alexpilottiok, listing BPs16:08
primeministerpalexpilotti: don't list them16:08
primeministerpalexpilotti: not worth it16:08
primeministerpw/o the bot16:08
primeministerpalexpilotti: you stated the proposed ones got accepted16:09
alexpilottiin short: life is good16:09
primeministerpalexpilotti: good enough16:09
primeministerpalexpilotti: installer update?16:09
alexpilotti8 BPs approved16:09
primeministerpall on track for paris?16:09
*** rmoe has joined #openstack-meeting16:09
alexpilottiand 2 with specs which already had a +216:09
alexpilottiParis is all good16:09
primeministerpperfecto16:10
*** MarkAtwood has quit IRC16:10
primeministerpthings are looking up on my end16:10
primeministerptoo16:10
primeministerp;)16:10
*** cody-somerville has joined #openstack-meeting16:10
*** MarkAtwood has joined #openstack-meeting16:10
alexpilottiheh16:10
primeministerpso on that note16:10
primeministerpI think we can end quick and reconvienne next week16:10
*** jmontemayor has joined #openstack-meeting16:11
primeministerpalexpilotti: ociuhandu thx for the time16:11
alexpilottisee you! :)16:11
*** evgenyf has quit IRC16:11
ociuhandusee you :)16:11
*** jlibosva has joined #openstack-meeting16:11
*** VijayTripathi has joined #openstack-meeting16:11
*** carl_baldwin has joined #openstack-meeting16:12
*** adrian-hoban has quit IRC16:13
*** afazekas has quit IRC16:13
*** kebray has joined #openstack-meeting16:14
*** dboik has quit IRC16:14
*** nati_ueno has joined #openstack-meeting16:15
*** jhenner has joined #openstack-meeting16:16
*** comay has joined #openstack-meeting16:16
*** igordcard has quit IRC16:16
*** nati_ueno has quit IRC16:17
*** nati_ueno has joined #openstack-meeting16:18
*** ihrachyshka has quit IRC16:18
*** SridharRamaswamy has joined #openstack-meeting16:18
*** Murali has quit IRC16:19
*** isviridov is now known as isviridov_away16:19
*** rook has left #openstack-meeting16:20
*** cjellick has quit IRC16:20
*** sambetts has left #openstack-meeting16:21
*** cjellick has joined #openstack-meeting16:25
*** mpaolino has quit IRC16:25
*** gokrokve has joined #openstack-meeting16:25
*** jehb has quit IRC16:26
*** yamamoto has joined #openstack-meeting16:28
*** ttrifonov is now known as zz_ttrifonov16:31
*** thedodd has quit IRC16:31
*** leeantho has joined #openstack-meeting16:32
*** thedodd has joined #openstack-meeting16:32
*** yamamoto has quit IRC16:33
*** leeantho has quit IRC16:33
*** leeantho has joined #openstack-meeting16:34
*** aepifanov has joined #openstack-meeting16:34
*** ygbo has quit IRC16:34
*** mpaolino has joined #openstack-meeting16:35
*** yeungp has quit IRC16:39
*** otherwiseguy has quit IRC16:41
*** cdub has joined #openstack-meeting16:42
*** dimsum_ is now known as dims16:45
*** jgallard has quit IRC16:47
*** mpaolino has quit IRC16:47
*** ihrachyshka has joined #openstack-meeting16:47
*** derekh has quit IRC16:47
*** shohel02 has joined #openstack-meeting16:49
*** dsetia has joined #openstack-meeting16:49
*** sdake_ has quit IRC16:50
*** s3wong has joined #openstack-meeting16:50
*** otherwiseguy has joined #openstack-meeting16:50
*** Mandell has joined #openstack-meeting16:52
*** markwash__ has joined #openstack-meeting16:52
*** pballand has joined #openstack-meeting16:52
*** Fdot has quit IRC16:55
*** Fdot has joined #openstack-meeting16:55
*** mchalla has joined #openstack-meeting16:56
*** Fdot has quit IRC16:56
*** ndipanov is now known as ndipanov_gone16:57
*** davidhadas_ has quit IRC16:57
*** sarob has joined #openstack-meeting16:57
*** mwagner_lap has quit IRC16:58
*** mrmartin has joined #openstack-meeting16:59
*** ivar-lazzaro has joined #openstack-meeting16:59
*** cjellick has quit IRC16:59
*** cjellick has joined #openstack-meeting17:00
*** jehb has joined #openstack-meeting17:00
*** mchalla has quit IRC17:00
*** enikanorov has joined #openstack-meeting17:00
*** dane_leblanc has quit IRC17:01
edleafeprimeministerp: The bot needs '#startmeeting'. You were 3 letters short. :)17:02
*** _nadya_ has quit IRC17:02
*** nati_ueno has quit IRC17:02
*** kebray has quit IRC17:02
*** nati_ueno has joined #openstack-meeting17:02
*** aepifanov has quit IRC17:05
*** aepifanov1 has joined #openstack-meeting17:05
*** colinmcnamara has joined #openstack-meeting17:05
*** zigo has quit IRC17:08
*** BrianB__ has quit IRC17:08
*** zigo has joined #openstack-meeting17:08
*** dane_leblanc has joined #openstack-meeting17:08
*** hashar has quit IRC17:08
*** luqas has quit IRC17:10
*** dboik has joined #openstack-meeting17:10
*** padkrish_ has quit IRC17:10
*** padkrish has joined #openstack-meeting17:12
*** virmitio has left #openstack-meeting17:13
*** mudassirlatif has joined #openstack-meeting17:14
*** eyald has left #openstack-meeting17:14
*** aepifanov1 has quit IRC17:14
*** dboik has quit IRC17:15
*** boden has quit IRC17:15
*** harlowja_away is now known as harlowja17:15
*** doron_afk has quit IRC17:15
*** mrmartin has quit IRC17:15
*** boden has joined #openstack-meeting17:16
*** padkrish has quit IRC17:16
*** markmcclain has joined #openstack-meeting17:18
*** nati_ueno has quit IRC17:19
*** nati_ueno has joined #openstack-meeting17:19
*** thedodd has quit IRC17:21
*** chandankumar has joined #openstack-meeting17:21
*** boden has quit IRC17:22
*** killer_prince is now known as lazy_prince17:22
*** yeungp has joined #openstack-meeting17:23
*** dboik has joined #openstack-meeting17:24
*** radez is now known as radez_g0n317:24
*** cbouch has quit IRC17:25
*** radez_g0n3 is now known as radez17:26
*** rajeshr has joined #openstack-meeting17:27
*** amcrn has joined #openstack-meeting17:27
*** colinmcnamara has quit IRC17:28
*** yamamoto has joined #openstack-meeting17:28
*** s3wong has quit IRC17:28
*** s3wong has joined #openstack-meeting17:29
*** chris- has joined #openstack-meeting17:29
*** markmcclain1 has joined #openstack-meeting17:31
*** markmcclain has quit IRC17:31
*** chandankumar has quit IRC17:31
*** s3wong has quit IRC17:32
*** yamamoto has quit IRC17:33
*** markmcclain1 has quit IRC17:33
*** markmcclain has joined #openstack-meeting17:33
*** markmcclain1 has joined #openstack-meeting17:34
*** balajiiyer has joined #openstack-meeting17:34
*** markmcclain has quit IRC17:34
*** pballand has quit IRC17:34
*** thedodd has joined #openstack-meeting17:35
*** dane_leblanc has quit IRC17:35
*** cbouch has joined #openstack-meeting17:37
*** pballand has joined #openstack-meeting17:38
*** MaxV has quit IRC17:39
*** davidhadas_ has joined #openstack-meeting17:40
*** shashankhegde has joined #openstack-meeting17:41
*** colinmcnamara has joined #openstack-meeting17:41
*** zigo has quit IRC17:41
*** amotoki has quit IRC17:41
*** zigo has joined #openstack-meeting17:41
*** mwagner_lap has joined #openstack-meeting17:42
*** wuhg has quit IRC17:43
*** matiu_ has joined #openstack-meeting17:44
*** VijayB has joined #openstack-meeting17:46
*** matiu has quit IRC17:47
*** lazy_prince is now known as killer_prince17:48
*** spzala has quit IRC17:48
*** emagana has quit IRC17:48
*** cbouch has quit IRC17:48
*** jlibosva has quit IRC17:48
*** emagana has joined #openstack-meeting17:49
*** david-lyle has quit IRC17:49
*** VijayTripathi has quit IRC17:49
*** david-lyle has joined #openstack-meeting17:49
*** dane_leblanc has joined #openstack-meeting17:50
*** rajeshr has quit IRC17:51
*** mrmartin has joined #openstack-meeting17:51
*** jprovazn has joined #openstack-meeting17:52
*** berendt has joined #openstack-meeting17:52
*** ivar-lazzaro has quit IRC17:52
*** emagana has quit IRC17:53
*** ivar-lazzaro has joined #openstack-meeting17:53
*** emagana has joined #openstack-meeting17:54
*** nati_ueno has quit IRC17:54
*** mchalla has joined #openstack-meeting17:54
*** nati_ueno has joined #openstack-meeting17:54
*** s3wong has joined #openstack-meeting17:55
*** ivar-lazzaro has quit IRC17:56
*** viktors has joined #openstack-meeting17:56
*** ivar-lazzaro has joined #openstack-meeting17:56
*** bdpayne has joined #openstack-meeting17:58
*** safchain has quit IRC17:58
*** lhcheng has joined #openstack-meeting17:58
*** spzala has joined #openstack-meeting17:58
*** bobt has joined #openstack-meeting17:59
*** henrynash has joined #openstack-meeting18:00
*** colinmcnamara has quit IRC18:00
*** johnthetubaguy is now known as zz_johnthetubagu18:00
*** nkinder has joined #openstack-meeting18:00
*** sarob has quit IRC18:00
stevemaro/18:01
*** jamielennox has joined #openstack-meeting18:01
lbragstadstevemar: \o18:01
stevemarkeystones assemble!18:01
dstaneko/18:01
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods, amakarov, ajayaa, hogepodge, breton: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
nkindero/18:01
*** padkrish has joined #openstack-meeting18:01
dolphmthat's getting to be a long list18:01
raildoo/18:01
*** padkrish has quit IRC18:01
*** amakarov has joined #openstack-meeting18:01
morganfainbergO/ mobile:)18:01
*** marcoemorais has quit IRC18:01
bknudsonhi18:01
gyee\o18:01
henrynashtop o’the day t’all18:01
*** sarob has joined #openstack-meeting18:01
*** sarob has quit IRC18:01
topolo/18:01
nonameenternameo/18:01
marekdhello18:01
*** marcoemorais has joined #openstack-meeting18:01
dolphm#startmeeting keystone18:01
amakarovhi18:01
openstackMeeting started Tue Oct 21 18:01:51 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. 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
lhchenghello18:01
openstackThe meeting name has been set to 'keystone'18:01
*** padkrish has joined #openstack-meeting18:02
dolphmso, morganfainberg asked me to skip the blueprint review for the moment, which is at the top of the agenda18:02
dolphmso i'm going to jump straight into nkinder's topic18:02
dolphm#topic Additional LDAP Attribute Mappings18:02
rharwoodo/18:02
*** openstack changes topic to "Additional LDAP Attribute Mappings (Meeting topic: keystone)"18:02
dolphmnkinder: o/18:02
*** marcoemorais has quit IRC18:02
*** erik____ has quit IRC18:02
*** marcoemorais has joined #openstack-meeting18:02
nonameenternameo/18:02
*** carl_baldwin has quit IRC18:02
*** dane_leblanc has quit IRC18:02
nkinderSo a recent simple patch to update some doc comments in the config file uncovered some things I wanted to discuss18:03
*** marcoemorais has quit IRC18:03
nkinderWe need to determine how the additional LDAP attribute mapping code should work18:03
nkinderLet me grab some links...18:03
*** marcoemorais has joined #openstack-meeting18:04
dolphmnkinder: i was about to ask - the meeting agenda mentions "a change" in juno and icehouse, have a link to that specifically?18:04
*** colinmcnamara has joined #openstack-meeting18:04
nkinder#link https://bugs.launchpad.net/keystone/+bug/129369818:04
uvirtbotLaunchpad bug 1293698 in keystone/icehouse "Can't map user description using LDAP" [Wishlist,Fix released]18:04
*** juzuluag has quit IRC18:04
topolnkinder whata dditional attrribute maapings are we missing?18:04
nkinderSo that was a bug that was fixed in Juno and backported to stable/icehouse18:04
*** Haneef has joined #openstack-meeting18:04
*** VijayTripathi has joined #openstack-meeting18:04
*** colinmcnamara has quit IRC18:04
nkinderWell, let's step back and talk about the purpose of the mappings18:04
ayounghttps://review.openstack.org/#/c/118590/18:04
*** _nadya_ has joined #openstack-meeting18:04
nkinderWhen creating an entry in LDAP, there are going to be certain required attributes based on the objectclass used18:05
nkinderSo a user might require cn, sn, and uid18:05
*** _jamielennox has joined #openstack-meeting18:05
*** erik____ has joined #openstack-meeting18:05
nkinderThe LDAP entry requirements might hve more attributes that Keystone's definition of a user does (id,name,mail,description,enabled)18:06
*** balajiiyer has left #openstack-meeting18:06
henrynashnkinder: so this if for R/W LDAP?18:06
ayoungnkinder, I'm wondering if this really should be LDAP specific.  I could see an argument that a SQL backend, not the one managed by Keystone, could be used for Authentication as well, like the mod_authn_mysql approach18:06
nkinderhenrynash: Yes, exactly18:06
ayoungand in that case, it might have this same restriction18:06
nkinderayoung: don't cloud matters here (yet)18:06
ayoungwell, it does argue that both should be done via the same  mapping mechanism as we are using for Federation18:06
*** jmontemayor_ has joined #openstack-meeting18:06
*** jsavak has joined #openstack-meeting18:06
ayoungandthat ties in with the LDAP rewrite that bknudson wants to do18:07
ayoungright bknudson ?18:07
ayoungHeh18:07
*** arnaud__ has joined #openstack-meeting18:07
morganfainbergThis is an artifact of keeping r/o and rw leap the same driver. It sounds like.18:07
gyeeare the non-standard attributes got stashed into 'extra' when it returns?18:07
*** jmontemayor has quit IRC18:07
nkinderso if Keystone needs to create a user in LDAP for the R/W case, we might need to supply some additional attributes to satisfy the objectclass requirements18:07
ayoungmorganfainberg, its a non issue for r/o18:07
bknudsonayoung: it might be better to use middleware for r/o LDAP rather than what we're doing.18:07
*** samuelms has joined #openstack-meeting18:07
gyeeso as long as we don't break the API spec we should be fine18:07
morganfainbergRight. In. R/w config we could provide a schema18:07
*** e0ne has quit IRC18:07
bknudsonayoung:  it is an issue for r/o ldap. The change that I made to fix the bug was only for reading... write wasn't involved.18:08
ayoungbknudson, additional attribute mapping?18:08
topolI thought r/w LDAP had serialization issues18:08
morganfainbergAnd not be constrained by ldap schema requirements like this.18:08
bknudsonayoung: yes, in https://review.openstack.org/#/c/81041/6/keystone/tests/test_backend_ldap.py18:08
*** Mandell has quit IRC18:08
nkinderyes, bknudson is correct18:08
bknudsonhttps://review.openstack.org/#/c/81041/6/keystone/common/ldap/core.py18:08
nkinderSo, back to the main issue...18:08
bknudsonr/w ldap isn't all that interesting imo.18:09
nkinderThe additional mapping code was designed to only be used when adding a new entry to LDAP (for the objectclass requirements I mentioned)18:09
topolbknudson+++18:09
bknudsonother than it makes our impl more complicated.18:09
ayoungbknudson, that is not an "additional attribute"  but rather a core attribute18:09
ayoungdescription is a required field18:09
*** hashar has joined #openstack-meeting18:09
*** AJaeger_ has joined #openstack-meeting18:09
nkinderThe fix that bknudson made causes us to pull in any other LDAP attribute and map it to on-the-fly additional attributes in the keystone user object18:10
dolphmbknudson: ++18:10
nkinderThis leads towards things like adding "employeeNumber" to a keystone user object, which is returned by a user get18:10
*** sdake_ has joined #openstack-meeting18:10
nkinderI really think that's the wrong direction18:10
gyeereturn in where? 'extra'?18:10
ayoungright, which is why the check was there in the first place18:10
*** marcoemorais has quit IRC18:10
dolphmgyee: extra is not an API attribute18:11
nkinderIt starts to promote keystone as a general user/group management solutiuon (which it's not)18:11
gyeedolphm, it we return employeeId in user ref, we would break the API spec isn't it?18:11
lbragstadwe're trying to move away from that18:11
dolphmgyee: no, that would be backwards compatible, but also useless18:11
ayoungldap_attr, attr_map = item.split(':') was supposed to be a reverse mapping, from the LDAP attribute to the Keystone, if I recall correctly18:12
dolphmnkinder: yeah, none of that stuff is necessary for openstack18:12
morganfainbergnkinder: ++18:12
nkinderSo, I'd like to rip it out18:12
nkinderThe question is is we need tpo go through a deprecation cycle18:12
jamielennoxyou want to rip out the entire concept of having 'extra' data for users? or just the LDAP bit/18:13
nkinderbknudson and I had some discussion on this here - https://review.openstack.org/#/c/118590/18/keystone/tests/test_backend_ldap.py18:13
morganfainbergnkinder, i think there is a better way - avoiding breaking people18:13
jsavakother openstack services enable meta data (see http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html) which contains stuff not exactly necessary for openstack but helps with integration & user experience18:13
* morganfainberg is back to desk18:13
nkinderjamielennox: I think we need to leave it in for the "create" case only18:13
*** VijayB has quit IRC18:13
nkinderjamielennox: or come up with a suitable replacement18:13
morganfainbergnkinder, i think this is where we look at splitting r/w ldap from r/o18:13
dolphmnkinder: can you clarify what you want to rip out?18:13
dolphmnkinder: a patch would be ideal :P18:13
morganfainbergwe can then really optimise the r/o ldap [most people don't use r/w]18:13
gyeemorganfainberg, ++18:14
dolphmmorganfainberg: +++18:14
*** leonchio__ has joined #openstack-meeting18:14
henrynashmorganfainberq: + * shoesize18:14
*** Mandell has joined #openstack-meeting18:14
gyeeheh18:14
morganfainbergthe r/w ldap can start looking like something we can migrate to a custom schema being provided as well18:14
ayoungmorganfainberg, the code that does this kind of logic is core to LDAP.  I really don't think splitting the driver will fundamentally help.18:14
bknudsonI guess the question is do we need a solution for Juno?18:14
dolphmhenrynash wins18:14
morganfainbergwhich then *solve* the extra attr wierdness18:14
dolphm(i did the math)18:14
*** radez is now known as radez_g0n318:14
*** s3wong has quit IRC18:14
bknudsonand I would assume that changing the functionality for juno isn't going to be possible18:14
*** VijayB has joined #openstack-meeting18:14
morganfainbergbknudson, thats the point of my recommendation18:15
henrynashdolphm: you know that they say big shoes big…..18:15
henrynashdolphm: feet18:15
bknudsonright, so I think morganfainberg and others are saying rather than a patch we want to rewrite ldap18:15
gyeeyou really have to go there?18:15
*** jmontemayor has joined #openstack-meeting18:15
morganfainberghenrynash, exactly18:15
nkinderdolphm: searching for the link...18:15
*** _jamielennox is now known as jamielennox_18:15
*** radez_g0n3 is now known as radez18:15
morganfainbergbknudson, and that is because we are going to have a hard time "fixing" juno. so to speak18:15
ayoungbknudson, what criteria are we going to use for the new design?18:16
henrynashsl18:16
lbragstadso we are still going to keep r/o ldaP, right?18:16
jamielennox_we've hated the 'extra' stuff in the API for a while now though - is it time we can put it in aflag and kill it off?18:16
dolphmlbragstad: yes18:16
nkinder#link https://git.openstack.org/cgit/openstack/keystone/commit/?id=ebfdab034f2b35074f1645b70c1f07d0c4dfd33718:16
morganfainbergayoung, i was even open to looking at SSSD as a migration path.18:16
ayoungwe can't kill r/w LDAP, can we?18:16
morganfainbergayoung, among other options.18:16
*** dane_leblanc has joined #openstack-meeting18:16
dolphmjamielennox_: we're pretty close to being able to do that with jsonschema validation18:16
ayoungI'm assuming that even if Identity is read only WRT LDAP, assignment needs to be R/W18:17
dolphmjamielennox_: a bunch of booleans get flipped and you raise 400's everwhere18:17
henrynashso what’s the argument *against* creating two ldap backends….other than we’d want to try and make the common code shared18:17
lbragstadjamielennox_: right now we allow additionalAttributes on requests.18:17
jamielennox_dolphm: kind of, we're not changing the schema with jsonschema at all18:17
henrynash(one r/o, one r/w)18:17
morganfainbergwe can't kill it, we can work to make most deployments better. and if we're able to convince the hold outs that there are better options (read: split Identity into it's own API that can manage LDAP w/ a schema and a migration path) down the line, we could make r/o ldap the *only* keystone deployment mode that we care about from assignmenty18:17
dolphmlbragstad: additionalAttributes=False ftw18:17
ayoungjsavak, you guys use LDAP for Identity in R/W or R/O mode?18:17
jamielennox_dolphm: ++18:17
lbragstaddolphm: yep18:17
jsavakayoung r/w18:17
jsavakfor now18:17
*** jmontemayor_ has quit IRC18:17
morganfainbergdolphm, and i'd like that option *across* the board18:18
nkinderdolphm: it's pretty much backing out the fixes for https://bugs.launchpad.net/keystone/+bug/1293698 (with the exception of introducing a new config setting to allow mapping of the description attr)18:18
uvirtbotLaunchpad bug 1293698 in keystone/icehouse "Can't map user description using LDAP" [Wishlist,Fix released]18:18
morganfainbergdon't want it in sql either.18:18
ayoungjsavak, thanks18:18
dolphmmorganfainberg: yeah, i'd want one global control for that18:18
*** marcoemorais has joined #openstack-meeting18:18
dolphmstrict_api = true # the new defaultness18:18
jamielennox_yea, this doesn't work if it's backend specific18:18
ayoungLDAP has a very nice replication story, which makes it the preferred multi-site Identity solution18:18
ayoungLets not do this18:18
bknudsonso what if we were to split out the identity provider into its own service?18:18
*** marrusl has quit IRC18:19
ayoungleave LDAP as a single driver18:19
ayounglets fix what is broken with it18:19
bknudsonthen the identity part can evolve in its own way (become a full user solution) and keystone can keep evolving with federation18:19
lbragstadbknudson: I think gyee had a nice list at the summit on that process?18:19
morganfainbergso, how likely is it someone is going to use the new functionality that bknudson 's patch provided?18:19
*** Tufin has quit IRC18:19
ayoungbknudson, that is fine, again except for CERN and Assignments in LDAP18:20
morganfainbergbknudson, i am thinking that is the long term goal18:20
topolwhatever we do please lets end up with a better user experience and not a worse user experience in the next release18:20
ayoungBut....18:20
gyee++ for identity separation18:20
bknudsonmorganfainberg: one of our products requested the fix... not sure if they're using it or not.18:20
nkindermorganfainberg: I think it's pretty unlikely since you can't use the keystone or openstack CLI to actually see those additional attributes18:20
morganfainbergbknudson, then i think we can't *fix* this, we shipped it.18:20
ayoungand that is, I think, a mess worth addressing in its own right18:20
*** kebray has joined #openstack-meeting18:20
jamielennox_gyee: ++ you were keen on it in atlanta - did you ever get anywhere?18:20
nkinderbknudson: I think they needed to map the description attribute though, right?18:20
nkinderbknudson: that part is valid18:20
morganfainbergnkinder, cli isn't that important on that front.18:20
bknudsonthese products don't use the cli.18:20
dolphmbknudson: the bug report is just for description18:20
gyeejamielennox_, haven't found the time18:20
jamielennox_gyee: thought so18:21
ayoungthe issue with LDAP assignment, though, is that it assumes it is in the same LDAP server as identity.  Can we change that without breaking it?  We don't have LDAP migrations18:21
nkinderbknudson: The fact that we had no config setting to allow that led to an attempt to use the additional mappings to map the description attribute18:21
dolphmbknudson: http api, then, i hope?18:21
bknudsondolphm: yes, they use the REST API.18:21
morganfainbergmy concern is we shipped this capability. *waves hands* implicit contract *more hand waving*18:21
topoluser experience *waves hand*18:21
morganfainbergtopol, shhh :)18:21
* jsavak waves back18:21
jamielennox_topol: i'm not sure we ever shipped that18:22
* gyee wave his fingers18:22
topolbreaking contract kills user experience18:22
ayoungIf we can make the LDAP assignment case work without breaking things, I think having Identity as a separate service  from Assignment would work fine18:22
nkindergyee: how many fingers....?18:22
gyeeha18:22
*** kopparam has joined #openstack-meeting18:22
morganfainbergayoung, i think we can avoid breaking that. it's a *very* special case.18:22
ayoungmorganfainberg, and...I think we can actually do that.  So long as they both talk to the same LDAP, assignemtn should be fine with Identity in a separate service18:23
*** thedodd has quit IRC18:23
nkinderbknudson: would you be able to find out if the driver for that fix was only the need to map the description attribute?18:23
morganfainbergi think we need to know how many people actually use ldap assignment, if it's just cern... I am happy to say lets work with them to help them out [if there is anything we can do to make life better for them]18:23
ayoungits little things like assuming the "pointers" to users is the users DN in the members attribute of the Role18:23
bknudsonnkinder: I'll find out and get back to you.18:23
nkinderbknudson: thanks18:24
ayoungmorganfainberg, lets assume it is CERN plus one other site that we won't ever hear from unless we break it18:24
ayoung but we'd hear from CERN first anyway18:25
dolphmmarekd: you're up ^18:25
bknudsonmove it into stackforge.18:25
morganfainbergbknudson, that was kindof the next thought i had.18:25
bknudsonI don't think it's even tested by tempest18:25
marekddolphm: yep, but for ldap matters  you'd better hit jose.18:25
morganfainbergbut we need to make our internal API a stable contract then.18:25
morganfainbergi think we should be moving that direction18:26
dolphmmarekd: doesn't look like he's on now, right?18:26
morganfainbergbut it is an added concern18:26
*** Sukhdev has joined #openstack-meeting18:26
*** breton has joined #openstack-meeting18:26
ayoungUgh...LDAP works.  Why break it.  These are minute deatils.18:26
ayoungdetails even18:26
marekddolphm: i doubt it.18:26
jamielennox_morganfainberg: i don't think this is an internal API right? it'd be some sort of federated deal18:26
*** baoli has quit IRC18:26
morganfainbergjamielennox_, identity_api18:26
bretonhi. Sorry, I'm late.18:26
morganfainbergjamielennox_, assignment_api18:26
ayoungCern would be OK with Identity in a separate service18:26
ayoungthey need LDAP due to scale and replication18:26
*** carl_baldwin has joined #openstack-meeting18:26
marekdayoung: through 'federation18:26
marekd' ?18:27
ayoungmarekd, yep18:27
marekdayoung: yes, that would rather be fine18:27
gyeeayoung, separate identity service back by LDAP make a lot of sense18:27
morganfainbergthe other *big* win about moving identity to a separate service we can explicitly avoid PII data leakage into openstack18:27
ayoungmarekd, its rather the assignment side in LDAP that is the sticking point18:27
ayoungand Rack using LDAP in R/W mode18:27
jsavakmorganfainberg +118:27
dolphmmorganfainberg: =D18:27
morganfainbergnever ask for the data (which is a very very large win hooking up to a corp ldap or even in rax use case)18:27
ayoungpretty sure CERN is using AD for LDAP, and not writing user data into it...due to the whole additional_attributes issue18:27
topolmorganfainberg great point!!!18:28
*** yamamoto has joined #openstack-meeting18:28
marekdayoung: afair we use ro ldap.18:28
*** pelix has quit IRC18:28
morganfainbergand then r/w for ldap assignment marekd ?18:29
amakarovmarekd, some still use rw18:29
ayoungmarekd, except for role assignments18:29
morganfainbergnkinder, unfortunately, i realyl don't think we can back out bknudson's change [even parts of it]. i want to get back on topic18:30
marekdmorganfainberg: ayoung: i don't work on that so i'd better not talk too much as i may simply lie to you. I don't know detailed ocnfiguration18:30
ayoungLDAP  follows the two laws of thermo-dynamics.  1. We can't win, the best we can do is break even. 2.  We can't break even.18:30
morganfainbergnkinder, we shipped it, i am sure we're going to run into bad (very bad) UX issues if we do.18:30
nkindermorganfainberg: do we want to deprecate it though?18:30
marekdmorganfainberg: ayoung: we had some constraints when openstack was deployed and some parts are non standard.18:30
morganfainbergnkinder, because someone is going to use it in Juno "cause it's there"18:30
ayoungmaybe?18:31
bknudsonSo what I'm not sure about is what is the bug that's being fixed now?18:31
dolphmand juno will be supported for a long while18:31
ayoungmorganfainberg, I think we can limit the LDAP fetch to the attributes we know about18:31
morganfainbergnkinder, i think we need to say "HEY DONT DO THIS" but i am very concerned about removing it. i think we should work on the overall UX and as we improve identity use cases it might fall to the wayside with better options18:31
ayoungnever fetch all attributes18:31
bknudsonHere's the bug: https://bugs.launchpad.net/keystone/+bug/133676918:31
uvirtbotLaunchpad bug 1336769 in keystone "LDAP additional attribute mappings description do not specify that they are for creation only" [Low,In progress]18:31
morganfainbergayoung, thats fine. only fetch "known" attributes, that is a change i think we can get away with (classify it as a backport and get it in stable asap)18:31
*** shashankhegde has quit IRC18:32
nkindermorganfainberg: ok, makes sense.  I just don't want to see it expanded to start covering update operations, CLI changes to show additional attrs, etc.18:32
morganfainbergbut we can't rip all of it out18:32
ayoungthat would be a change on get and list...18:32
bknudsonbut we still support additional attributes in SQL?18:33
*** marcoemorais has quit IRC18:33
*** yamamoto has quit IRC18:33
bknudsonwhy is sql / ldap special?18:33
morganfainbergbknudson, i think we should put a toggle in to disable that.18:33
*** marcoemorais has joined #openstack-meeting18:33
bknudsonclients don't know what the backend is so they don't know what will be accepted or rejected.18:33
lbragstadtoggle or deprecate and move towards not supporting additional attributes?18:33
morganfainberglbragstad, thats my thought18:33
nkinderlbragstad++18:34
morganfainberglbragstad, or come up with a better story for it18:34
* topol getting depressed. thought we had LDAP integration covered a few releaseas ago :-)18:34
bknudsonI'd rather we moved towards moving identity into its own service18:34
morganfainbergas in.. identity split, look at shipping a schema that can support extra attrs18:34
morganfainbergfor ldap18:34
morganfainbergsql can stay the same18:34
bknudsonthen we can deprecate identity in keystone18:34
morganfainbergr/o ldap .. hah no updates anyway who cares.18:34
henrynashmorganfainberg: so we will need to signal that strongly if we take that approach…I know of a number of products that rely on storing additional attributes with users, for instance18:34
jamielennox_i think even in a new service we don't expose extra mappings - i don't think they are a benefit as no other service can rely on them anyway18:35
morganfainbergbknudson, it should be easy to proxy keystone identity -> new service [i'd do it in middleware]18:35
morganfainberghenrynash, yes.18:35
morganfainbergjamielennox_, in new service if there is a *real* demand for it we can make it really work, not be a weird bolt-on18:35
*** s3wong has joined #openstack-meeting18:36
*** marcoemorais has quit IRC18:36
morganfainbergjamielennox_, the issue is we're trying to make 2 use cases work in a "standard" schema way in LDAP, if we're doing read-write ldap, we are in our rights to say "use our schema" which would solve that issue rather than needing to do custom weird mappings18:36
dstanekwhen we say new service we are talking about another executable running on another port right?18:36
*** marcoemorais has joined #openstack-meeting18:36
bknudsondstanek: yes18:36
morganfainbergdstanek, yes.18:36
*** markwash__ has quit IRC18:37
morganfainbergjamielennox_, making read-only ldap and r/w ldap work like they do has resulted in compromises on both sides.18:37
ayounghttp://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/ldap/core.py#n142618:37
ayoungdoesn't look like it takes an attribute list18:37
jamielennox_morganfainberg: would be a discussion for if and when we get it split18:37
*** Mandell has quit IRC18:37
morganfainbergjamielennox_, yes. it would be a "if we need this, we can really support it" vs. "oh this hack to make it work"18:37
jamielennox_but i'd say lowest common denominator - and it's very low18:37
ayoungbut http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/ldap/core.py#n1438  sure enough, it does.18:37
*** jamielennox has quit IRC18:38
morganfainbergdstanek, and if you don't support read/write identity in theory you could avoid running it all together [something to explore]18:38
ayoungnkinder, so,  how are we returning values other than those that are explicitly mapped?  I don't see it18:38
nkinderayoung: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/ldap/core.py#n145918:38
nkinderayoung: those are the additional mapped attributes18:38
dstanekmorganfainberg: i'd love to see a good write up on what the proposed split looks like - architecturally it just seems like it will complicate things18:39
*** markwash__ has joined #openstack-meeting18:39
nkinderayoung: do you mean in terms of shoving them into the user object on the keystone side?18:39
morganfainbergdstanek, fair enough.18:39
bknudsondstanek: the goal is to eventually simplify by using federation for all users.18:39
ayoungnkinder, so they have to be explicitly added in order to be fetched, right?18:39
nkinderayoung: probably best to discuss more after the meeting18:39
morganfainbergbknudson, ++18:39
ayoung++18:39
*** kebray has quit IRC18:39
*** brich1 has joined #openstack-meeting18:40
dolphm(20 min left)18:40
ayoung1.2.1 Review of Keystone Blueprints for "Trivial" Status  ?18:40
dstanekbknudson: that i like; i guess the split is fuzzy to me18:40
morganfainbergayoung, skip till next week.18:40
*** erik____ has quit IRC18:40
ayoungDeal18:40
morganfainbergayoung, i'm still cleaning up the bp list18:41
dolphmmorganfainberg: schedule then?18:41
dstanekbknudson: 2 ports -> 1 port and back to 218:41
morganfainbergdolphm, just a note: review the schedule, let me know if there are any issues with time/descriptions/etc18:41
*** ajo_ has joined #openstack-meeting18:41
dolphm#topic Tentative Schedule on Sched.org for Kilo Design summit18:41
morganfainbergor if we *want* to drop one of the sessions18:41
*** openstack changes topic to "Tentative Schedule on Sched.org for Kilo Design summit (Meeting topic: keystone)"18:41
dolphm#link http://kilodesignsummit.sched.org/type/keystone18:41
morganfainbergplease review it18:41
morganfainberglet me know if anything is "wrong"18:41
bknudsondo other projects have their schedules?18:41
morganfainbergwe might get a session back18:42
morganfainbergdepending on the "ops summit" stuff18:42
dolphmbknudson: http://kilodesignsummit.sched.org/18:42
morganfainbergif we get a dedicated session back i'll swap our ops one over to ops summit and add the split identity (seems like a reasonable topic) in it's place?18:42
dolphmlots of TBD slots18:42
ayounghard to say without http://kilodesignsummit.sched.org/type/horizon18:43
*** radez is now known as radez_g0n318:43
morganfainbergayoung, the horizon session right before our SSO one should be a cross-project session too18:43
morganfainbergayoung, already talked to david-lyle about that18:43
ayoungI know of at least three things that will need Horizon buy in18:43
morganfainbergand our SSO one will have horizon folks at it (it doesn't overlap with their sessions)18:43
*** marcoemorais has quit IRC18:44
ayoungmorganfainberg, jamielennox_ and I have been discussing the KC DOA integration, too18:44
*** marcoemorais has joined #openstack-meeting18:44
marekdmorganfainberg: ++18:44
ayoungHorizon right now is the limiting factor on a lot of the stuff we do18:44
morganfainbergso in short, keep your eyes on the schedule, let me know if anything needs to be changed (i'm also looking)18:44
*** comay has quit IRC18:44
morganfainbergit doesn't have to be during this irc meeting :)18:44
*** leonchio__ has quit IRC18:44
bknudsonwe shouldn't have to design anything around horizon18:45
dolphmhopefully by friday this schedule will be totally fleshed out, so everyone should check in later this week and look for conflicts (plan your days!)18:45
bknudsonjust use the standard rest stuff and any client can use it18:45
bknudsonhorizon isn't the only UI18:45
morganfainbergbknudson, in an ideal world, but we should make sure our APIs make sense for horizon and/or provide them any support they need18:45
morganfainbergother UIs will likely benefit18:45
*** varora has left #openstack-meeting18:45
topolare stuff really needs to work with horizon. its embarassing when it doesnt18:46
lhchengmorganfainberg ++18:46
bknudsonwell, let's not assume everyone is using django18:46
* topol *User experience*18:46
dolphmbknudson: ++18:46
gyeebkundson, API and UX, Horizon is just a side-effect :)18:46
morganfainbergbknudson, DoA is only one mechanism.18:46
morganfainbergthis is more about "do our REST APIs work for this, if not, what needs to change"18:46
morganfainbergnot "how do we make DOA work"18:46
morganfainbergthat former topic can be in the horizon side of the session(s)18:47
morganfainbergerm latter18:47
gyeemorganfainberg, speaking of which, ain't they just form a API working group or something?18:47
morganfainberggyee, yes. there is a thread on ML on the meeting(s)18:47
stevemargyee, meetings are thursdays at 0000 utc (likely) for api working group18:48
morganfainberg#link http://lists.openstack.org/pipermail/openstack-dev/2014-October/048144.html18:48
morganfainbergit's long18:48
*** padkrish has quit IRC18:48
gyeeI am guessing we'll have to throw in our fifty cents18:48
morganfainbergyes18:48
bknudsonhere comes v4.18:48
gyeestevemar, thanks18:48
*** balajiiyer has joined #openstack-meeting18:48
morganfainbergbknudson, unlikely.18:48
morganfainbergbknudson, microversioning [yes]18:49
gyeeya think? :)18:49
lbragstadstevemar: gyee in #openstack-meeting-318:49
*** jmontemayor has quit IRC18:49
morganfainbergbut v3 has been enough hassle to get support, lets not do v4... ever* ... [ *= anytime soon ]18:49
*** padkrish has joined #openstack-meeting18:49
bknudsonwe keep changing the api but we don't ever update the version, even minor version.18:49
jamielennox_i'm sceptical that microversioning will work, we've not successully actually removed any api calls18:50
bknudsonat least in a way that clients can get at18:50
gyeelbragstad, thanks, on my cal now18:50
morganfainbergbknudson, i think we need to solve that. but i don't think we can major version rev.18:50
morganfainbergbknudson, tbh.18:50
bknudsonjamielennox_: they really don't seem to be thinking about the APIs.18:50
jamielennox_bknudson: found that today - a whole bunch of my session stuff assumed that i could rely on the minor version18:50
jamielennox_bknudson: what are they thinking then?18:50
lbragstadgyee: #link https://wiki.openstack.org/wiki/API_Working_Group18:51
bknudsonjamielennox_: they're thinking about how to implement it in the server18:51
ayoungaccepts header with the micro version?18:51
jamielennox_by a whole bunch i have a couple of calls that i know don't exist in early versions of keystone so i can not make the call if the minor version is correct18:51
bknudsonI meant they're not thinking about the python sdks.18:51
dolphmjamielennox_: that should be a safe client side behavior18:51
*** balajiiyer has left #openstack-meeting18:51
jamielennox_dolphm: yet i checked and we still advertise v3.018:52
jamielennox_but don't change that cause we'll break auth_token18:52
*** jmontemayor has joined #openstack-meeting18:52
dolphmjamielennox_: oooh, right.18:52
morganfainbergso, lets rev the minor version per release18:52
* jamielennox_ needs a holiday18:52
*** mchalla has quit IRC18:52
morganfainbergsimple for now.18:52
dolphmjamielennox_: auth_token needs a patch asap :(18:52
*** gduan has quit IRC18:52
ayounglets open a bug in Auth token saying v 3.X  at least18:52
dstanekjamielennox_: this highlights the problem we have in general - we don't advertise capabiltiies in our APIs yet18:52
dolphmmorganfainberg: we do, in the api doc18:52
dolphmmorganfainberg: but auth_token is hardcoded to look for .018:52
dolphmmorganfainberg: so the server has been stuck for several releases18:52
morganfainbergdolphm, sure, but we need to fix the server too.18:52
bknudsonthat's what json-home can do18:53
dolphmadvertising .018:53
morganfainbergbknudson, ++18:53
morganfainbergyay json-home!18:53
dolphmbknudson: ++18:53
ayoung  version >=  3.0  && version < 4.018:53
*** wenlock has joined #openstack-meeting18:53
* ayoung opening bug now18:53
jamielennox_morganfainberg: so the auth_version param in auth_token only checks that the value is v3.0, and so it will revert to v2 if we update the minor version :'(18:53
*** garyduan has joined #openstack-meeting18:53
morganfainbergjamielennox_, so lets fix that18:53
lbragstad~ 7 minutes left18:53
jamielennox_morganfainberg: yea, was looking at it just a few hours ago18:53
gyeeouch18:54
morganfainbergjamielennox_, i'm willing to cut a new middleware *asap* if we get that fixed to do like 3.0 <= KS API version <= 4.018:54
bknudsonmorganfainberg: there's a revert that should get in before a new middleware18:54
ayoung#link https://bugs.launchpad.net/keystonemiddleware/+bug/138385318:54
uvirtbotLaunchpad bug 1383853 in keystonemiddleware "auth_token middleware hard coded to check for version 3.0" [Undecided,New]18:54
morganfainbergbknudson, lets make sure it lands then.18:54
bknudsonhttps://review.openstack.org/#/c/129551/ is the revert (from jamielennox_ ).18:55
bknudsonjamielennox_ is going to fix it for real.18:55
morganfainbergbknudson, +3 on that one18:55
jamielennox_i've been looking at it this afternoon and it's a PITA but it'll work somehow18:55
morganfainbergbknudson, easy sell since there wasn't a realse with it18:56
*** jckasper_ has quit IRC18:56
*** jckasper has joined #openstack-meeting18:56
*** thedodd has joined #openstack-meeting18:57
morganfainbergoh, last quick note: Check for untriaged bugs - please triage them if you can18:57
morganfainbergi'll run the report to the #openstack-keystone channel here post meeting.18:57
* morganfainberg hasn't setup a cron job for this yet18:57
*** nati_ueno has quit IRC18:57
*** ianw has joined #openstack-meeting18:58
*** nati_ueno has joined #openstack-meeting18:58
dolphm\o/18:59
dolphm#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Oct 21 18:59:18 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-10-21-18.01.html18:59
*** padkrish has quit IRC18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-10-21-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-10-21-18.01.log.html18:59
morganfainbergdolphm, thanks for chairing the meeitng today18:59
dolphmmorganfainberg: of course18:59
*** padkrish has joined #openstack-meeting18:59
jeblairinfra folks?19:00
anteayao/19:00
wenlocko/19:00
fungii think so!19:00
*** amakarov has left #openstack-meeting19:00
mmedvedeo/19:00
*** pcrews has joined #openstack-meeting19:00
krotscheckwat?19:00
jeblair#startmeeting infra19:00
openstackMeeting started Tue Oct 21 19:00:44 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
ianwgo giants19:00
openstackThe meeting name has been set to 'infra'19:00
*** ajo_ has quit IRC19:00
AJaeger_o/19:00
*** Haneef has quit IRC19:00
*** lhcheng has left #openstack-meeting19:00
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-14-19.03.html19:01
*** jamielennox_ has left #openstack-meeting19:01
jheskethMorning19:01
jeblair#topic  Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:01
anteayajhesketh: yay19:01
jeblairACTION: pleia2 to create etherpad with infra-facing pros/cons on zanata vs pootle19:01
anteayashe is on a plane19:01
jeblairneat19:01
AJaeger_was done19:01
*** brich1 has quit IRC19:01
anteayaI think this and a ml thread are in progress19:02
clarkbo/19:02
AJaeger_anteaya: correct19:02
*** emagana has quit IRC19:02
jeblair#topic  Priority Efforts19:02
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:02
jeblairswift logs19:02
*** nkinder has left #openstack-meeting19:02
jeblair#link https://etherpad.openstack.org/p/swift_logs_next_steps19:02
jeblairjhesketh: can you link your blog post?19:02
*** emagana has joined #openstack-meeting19:02
jeblairah, is in etherpad19:03
jheskethhttp://josh.people.rcbops.com/2014/10/openstack-infrastructure-swift-logs-and-performance/19:03
jeblair#link http://josh.people.rcbops.com/2014/10/openstack-infrastructure-swift-logs-and-performance/19:03
jeblairi have not had a chance to read it yet19:03
nibalizero/19:03
jeblairit looks like it will be very informative :)19:03
*** ajo_ has joined #openstack-meeting19:04
krtayloro/19:04
*** Longgeek has quit IRC19:04
jeblairit makes my firefox slow19:04
anteayamine too19:04
anteayaI didn't want to say anything though19:04
anteayabecause tables and graphs19:04
jheskethAll good. I don't have a lot more to add. I think my conclusion is let's keep moving with switching things over but I want other input19:04
*** nati_uen_ has joined #openstack-meeting19:04
*** sarob has joined #openstack-meeting19:04
jeblairjhesketh: you had some ideas for what might be causing some slowness (authn issues was one, i think?)19:05
jheskethHeh, yeah, I had to make all those graphs in Firefox. Sorry. :-(19:05
*** Duane has joined #openstack-meeting19:05
jeblairjhesketh: did you have a chance to look into that?19:05
clarkbya I skimmed it and I agree with the plan to keep going19:05
clarkbwe should look into fixing the intermittent 404s too19:05
jeblairjhesketh: could you put instructions in the etherpad for how to request swift versions of logs for those of us who haven't tried it out yet?19:06
jheskethjeblair: I list the auth stuff as a source of error and a few vague options for avoiding it, but I don't think it's huge19:06
*** Mandell has joined #openstack-meeting19:06
*** derekh has joined #openstack-meeting19:06
jheskethThe 404s I didn't look into19:06
clarkbpath?source=swift19:07
clarkbjeblair: ^19:07
jeblair(basically, i'm not familiar with the auth problems or the 404s and don't know how to become more familiar)19:07
jeblairclarkb: for what jobs?19:07
*** jamielenz has joined #openstack-meeting19:07
jheskethclarkb: yep, that's it19:07
*** emagana has quit IRC19:07
clarkband you should be able to do it on config jobs19:07
clarkbwhich are now system-config jobs19:07
jheskethFor project-config19:07
jeblairpretend i was in china for two weeks :)19:07
*** stannie has quit IRC19:07
*** jamielenz is now known as jamielennox19:07
clarkbI was using the pupet-apply tests19:07
jheskethAh yeah they'll work too19:08
*** nati_ueno has quit IRC19:08
jeblairso like this: http://logs.openstack.org/01/130001/1/check/gate-infra-puppet-apply-precise/77509cd/console.html?source=swift19:08
*** novas0x2a|laptop has joined #openstack-meeting19:08
jeblairthat's a 40419:08
clarkbya now refresh19:08
clarkbeventually you should get the file19:08
*** dpaterson has quit IRC19:08
*** nati_uen_ has quit IRC19:08
*** andreykurilin_ has joined #openstack-meeting19:08
jeblairnot so much19:09
jheskethThat may not be recent enough?19:09
clarkbit is from today19:09
jeblairi don't see any log entries about a swift upload19:09
jeblairhttp://logs.openstack.org/01/130001/1/check/gate-infra-puppet-apply-precise/77509cd/console.html19:10
clarkbhrm we don't seem to apply the swift stuff in that job19:10
clarkbya so in the change of everything we may have broken that19:10
*** sarob has quit IRC19:10
fungioh, possibly broken when we renamed?19:10
*** viktors has left #openstack-meeting19:10
*** bobt has quit IRC19:10
clarkbya that is my initial guess19:10
*** sarob has joined #openstack-meeting19:11
jeblairhttp://logs.openstack.org/36/128736/5/check/gate-infra-puppet-apply-precise/80a3ead/console.html19:11
jeblairbut that works (is on a project-config change)19:11
anteayaso I guess that is feedback for the next agenda item19:11
jheskethHmm, I might have a look at what jobs are still running then. I only used the layout one19:11
*** VijayTripathi has left #openstack-meeting19:11
jheskethIt could be due to the job failing it doesn't get to the upload swift part19:11
jeblairokay, so folks think it's working well enough that we should proceed to ... adding it to a devstack-gate job?19:12
clarkbjeblair: we should probably sort out the apply centos6 problem first19:12
clarkbjust to be sure it won't interfere with d-g19:12
jeblairjhesketh: ah, yep.  we'll need to run it regardless of result19:12
clarkbbut ya I think that is the next big test as it will give us bigger files and lots of them19:12
*** padkrish has quit IRC19:13
jheskethjeblair: actually I think the next step should be to disable storing on disk for a job or two so we can find issues like this one19:13
*** leonchio__ has joined #openstack-meeting19:13
jeblairthat might require changes to some job configs, or the use of a plugin that lets you run things after failure19:13
*** leonchio__ has quit IRC19:13
*** cody-somerville has quit IRC19:13
*** cdub has quit IRC19:13
jeblair(in this case, i think we can add a plugin if needed since this is something we can bake into turbo-hipster post-jenkins)19:14
jheskethYeah I'll need to investigate this case as probably the very next thing to do19:14
*** radez_g0n3 is now known as radez19:14
jhesketh(turbo hipster has support)19:14
jeblairso i think we can _also_ upload to swift on devstack immediately, but we do need to solve the failure issue before we have any jobs that _don't_ upload to static.o.o19:14
jheskethAgreed19:15
*** ayoung has quit IRC19:15
*** otherwiseguy has quit IRC19:15
jeblaircool, anything else on this?19:15
*** SridharRamaswamy has quit IRC19:15
jeblair#topic  Config repo split19:16
*** openstack changes topic to "Config repo split (Meeting topic: infra)"19:16
anteayamy understanding is that we are done19:16
jeblairso this is done, and i think all that remains is moving the spec to implemented.  and we'll drop this from future meetings.19:16
jeblairyaay!19:16
anteayawith the possible exception that swift upload on system-config jobs may be broken19:16
anteayayay19:16
jeblair#topic  Nodepool DIB19:16
*** openstack changes topic to "Nodepool DIB (Meeting topic: infra)"19:16
jeblairare there any outstanding nodepool dib patches/issues we should discuss?19:17
clarkbyes19:17
clarkbthe dib mutliple outputs change merged \o/19:17
clarkbshoudl release tomorrow if dib sticks to their schedule19:17
jeblairclarkb: you have a change to start using that, right?19:17
clarkband I still intend on upgrading nodepool to trusty and have a change I need to update in order to use the new dib feature19:17
clarkbjeblair: ya let me get a link there are some -1's I need to address that I have ignored until the dib change merged19:18
*** emagana has joined #openstack-meeting19:18
*** padkrish has joined #openstack-meeting19:18
*** hashar has quit IRC19:18
*** emagana has quit IRC19:18
clarkb#link https://review.openstack.org/#/c/126747/19:18
clarkbso as soon as grenade and jenkins are happy again I will probably context switch to the nodepool things19:18
jeblaircool.  anything else?19:19
clarkband thats about it19:19
jeblair Docs publishing19:19
jeblairso this is waiting on us being happy with swift logs...19:19
fungiagreed, since it will rely on similar mechanisms19:19
jeblair...or us considering the use of afs.19:19
jeblairwhich, honestly, fits docs publishing pretty well.19:20
anteayaawesome19:20
*** sdake_ has quit IRC19:20
fungiagreed, and is much closer than it was last week ;)19:20
jeblaireither way, still in a holding pattern19:20
jeblairfungi: indeed :)19:20
jeblair Jobs on trusty19:20
anteayado we need #topic19:21
jeblairi probably should start doing that, yeah19:21
jeblairanyway, who knows about the trusty move?19:21
anteayayou did for nodepool dib19:21
fungi#link https://etherpad.openstack.org/p/py34-transition19:21
jeblairoh, huh19:21
*** ajo_ has quit IRC19:21
fungithe list of blockers is getting shorter19:21
jeblair#topic Jobs on trusty19:22
*** openstack changes topic to "Jobs on trusty (Meeting topic: infra)"19:22
*** jtomasek has quit IRC19:22
fungiglanceclient and to a lesser extent heatclient are problems19:22
*** rudrarugge has joined #openstack-meeting19:22
*** lzachery has quit IRC19:22
anteayayou punted nicely to the ml on glancelient19:22
fungimostly problems with using unordered data types to build urls and json for fake api servers19:23
zaroo/19:23
jeblairfungi: is anyone working on the heat problems?19:23
fungii was starting to look into that one, and they inherit their fake server from oslo incubator19:23
fungiso i think i need to fix it there19:24
fungibut may also end up punting to them19:24
jeblairi kind of feel like you shouldn't have to be fixing all of the things, unless you really feel like it :)19:24
clarkb++19:24
anteayaI agree19:24
fungii'd personally rather not, but at least giving them some heads up on where the issues seem to be can help19:24
fungialso stackforge/heat-translator seems to have issues, but it's stackforge so they'll need to look into that when i get around to letting them know19:25
jeblairfungi: so at some point, you plan on notifying heat they have trusty problems, yeah?19:25
fungijeblair: yeah, today i think19:26
jeblairat that point, maybe we can bring it up in the project meeting19:26
*** dboik has quit IRC19:26
fungiwell, it's not that heat is broken on trusty, it's that it's untestable on trusty19:26
fungiso could also be broken, who knows19:26
jeblairfungi: yeah, i think you just said the same thing twice :)19:26
fungier, heatclient i mean19:26
fungiand yeah, basically if it's not tested...19:26
*** thedodd has quit IRC19:27
clarkband the SRU stuff is all in19:27
jeblairfinally, if we don't see progress we might suggest a deadline to the tc19:27
clarkbhopefully ubuntu pcisk that up after they release unicorn19:27
fungithe two outstanding ubuntu bugs, yeah. blocked on their release freeze i believe19:27
clarkbfungi: ya that is my understanding19:27
jeblairbut hopefully we won't get to that point19:27
fungijeblair: sounds good19:27
fungii've been pushing not-as-hard yet because we're also waiting on ubuntu19:28
fungibut that does seem just over the horizon now19:28
*** ajo_ has joined #openstack-meeting19:28
jeblaircool.  a plan.  anything else?19:28
*** yamamoto has joined #openstack-meeting19:28
*** MaxV has joined #openstack-meeting19:28
*** dprince has quit IRC19:28
jeblair#topic  Kilo summit topic brainstorming pad (fungi)19:28
*** openstack changes topic to "Kilo summit topic brainstorming pad (fungi) (Meeting topic: infra)"19:28
jeblairwhee this got bigger19:29
*** ptoohill_ has quit IRC19:29
fungi#link https://etherpad.openstack.org/p/kilo-infrastructure-summit-topics19:29
*** mchalla has joined #openstack-meeting19:29
fungithe items there seem to be getting fleshed out and discussed19:29
jeblairare we ready to try to finalize it?19:30
anteayaI told mtreinish about using the bottom part for the friday sessions19:30
*** thedodd has joined #openstack-meeting19:30
*** padkrish has quit IRC19:30
fungii think we've had plenty of time to regurgitate our collective brains into it19:30
anteayaso qa knows to add stuff to this etherpad19:30
anteayadoes afs still need an etherpad item?19:31
krotscheckjeblair and I talked at the storyboard meeting, and having storyboard get a slot seemed a little superfluous.19:31
krotscheckMy goal at the summit is to actually get people to pay attention to StoryBoard. Most of the roadmap things are still pretty well known.19:32
jeblairwhat do you think about voting on these?  add votes to the etherpad next to items you think would be good for sessions?19:32
jeblairthis would be a non-binding vote :)19:32
fungiheh19:32
anteayalines 22-25 can be removed19:32
fungithat seems reasonable. maybe as a first order effort people should remove topics which they've decided aren't needed19:32
anteayaso I will remove them19:33
*** yamamoto has quit IRC19:33
anteayasomeone in brown beat me to it, thank you19:33
AJaeger_an unnamed brown ;)19:33
fungiand yeah, voting in here is likely a poor waste of meeting time19:33
anteayaI'm guessing that is jeblair19:33
*** mchalla has quit IRC19:34
AJaeger_so, should we add in the etherpad "+1 AJaeger" (or -1) ?19:34
fungibut we should probably set the 24-hour clock to people voting for their preferences19:34
*** Mandell has quit IRC19:34
fungior something along those lines19:34
jeblairyep, i'm brown, i named myself19:34
nibalizerjeblair: maybe give everyone a number of votes (3?) so they can vote for multiple things19:34
*** ildikov has joined #openstack-meeting19:34
*** moha_hunt has joined #openstack-meeting19:35
*** VijayB has quit IRC19:35
jeblairi think just leave a positive vote next to things you think are useful19:35
*** VijayB_ has joined #openstack-meeting19:35
jeblairi left a sample vote next to infra-manual19:35
nibalizerok19:35
jeblairso if that's clear, we can probably move on and vote asynchronously19:36
AJaeger_Also on the QA topics?19:36
jeblairoh good question19:36
jeblairi was mostly thinking we need this for the 4 infra session slots we have, so just the top section19:36
AJaeger_jeblair: ok19:36
jeblairthe bottom i think we can leave for the actual meetup at the summit19:36
zaroughh! my cursor keeps moving on me!19:36
fungiagreed. just the session slots topics19:37
*** kopparam has quit IRC19:37
jeblair#topic  Kilo cycle Infra liaisons... should we have them? (fungi)19:37
*** openstack changes topic to "Kilo cycle Infra liaisons... should we have them? (fungi) (Meeting topic: infra)"19:37
*** neelashah has quit IRC19:38
jeblairso i think we mostly decided we don't need formal project liasons right now; the informal contact we have is working okay19:38
fungiqa, oslo, release management, docs, vulnerability management, stable maintenance are all starting to organize liaison lists19:38
*** jamielennox has quit IRC19:38
AJaeger_for liasions, the first question is what do we expect from them19:38
fungii agree in general we don't have much need19:38
jeblairhowever, this morning fungi and anteaya discussed the idea of formal third-party ci liasons19:38
jeblairwhich i think is a fabulous idea19:39
AJaeger_Are those people that we would ask for a +1 for patches in their projects?19:39
AJaeger_jeblair: +1 on 3rdparty liasons19:39
clarkbjeblair: anteaya so I was thinking about that again today because it came up19:39
jeblairso projects would nominate people to represent nova when working with third-party ci system operators19:39
fungieach project which has decided they are requiring third-party testing for parts of their codebase would identify points of contact19:39
fungidefaulting to the ptl19:39
clarkband couldn't we delegate CI voting to each project?19:39
clarkband get out of the business completely? seems like we talked about that in atlanta19:39
anteayaI'm hoping that during the course of the summit those folks already playing those roles become more willing to be public about it19:40
clarkbit would require some gerrit group magic but should work19:40
jeblairclarkb: yes.  you brought it up along with making the gerrit accounts self service.19:40
fungirighht, i think if we tweak to project-specific acls for third-party testing, these would be the people with control over that group19:40
clarkbya that too :) but I think they are orthogonal things if we want to solve them separately that may be easier19:40
anteayaI would be in favour19:40
jeblairi think that's a great idea.  does someone want to make a formal proposal and do the acl testing?19:40
anteayaif we have the gerrit features to do that19:40
jeblairclarkb: i kind of think they are tied.19:40
clarkbI can sign up for the testing of said stuff19:41
anteayaI would except I don't know if I can get it done this week19:41
clarkbsince I have suggested it I might as well own it :)19:41
anteayaand I'm off next19:41
anteayathanks clarkb19:41
fungii can write up something for the project-wide liaisons page19:41
clarkb#action clarkb figure out gerrit per project third party voting ACLs and third party accounts via openid19:41
anteayacan we let cinder have their meeting first?19:41
fungias a draft before we make it official on the wiki19:41
*** gyee has quit IRC19:42
anteayaso maybe write that stuff up thursday fungi19:42
anteayasince thingee was supportive19:42
jeblairhypothetically, if we made everything self-service and put projects in control of their own third-party ci voting... should there still be project third-party ci liasons?19:42
fungi#action fungi draft third-party testing liaisons section for wiki19:42
anteayabut I do kind of want to let cinder own it, rather than it being a directive from us19:42
*** shashankhegde has joined #openstack-meeting19:42
anteayawell in matters of what to do if and education19:42
fungijeblair: well, did we have a solution to projects being able to disable commenting from accounts, or are we still the go-to for that?19:42
*** otherwiseguy has joined #openstack-meeting19:42
anteayaI would like to deal with one person per project19:43
clarkbjeblair: ya we may still need that rol19:43
clarkber role19:43
jeblairfungi: i think that's why we need a proposal :)19:43
anteayarather than the hoard19:43
*** tbarron has quit IRC19:43
fungiif we're stuck disabling the misbehaving systems, i'd like there to be representatives from projects letting us know when to reenable19:43
jeblairfungi: (because i don't know the answer to that)19:43
fungigot it19:43
jeblairfungi: i kind of suspect it would end up being projects can disable voting, but really bad misbehavior may require us to disable an account19:43
clarkbjeblair: ya that is what I am thinking19:44
anteayathat would be great19:44
anteayaand projects are in charge of the steps to become reenabled19:44
fungibut beyond that, the liaisons idea acts as a rallying point for the third-party testers on those projects in place of our infra team19:44
krtaylorthird-party liaisons would also be helpful for third-party systems, a point of contact for systems with questions19:44
*** ptoohill_ has joined #openstack-meeting19:44
jeblairso it sounds like liasons may still be useful even if we go to self-service, both for us (disabling for abuse, and facilitating onboarding of new ci systems with the projects themselves)19:44
jeblairkrtaylor: good point19:45
*** Duane has quit IRC19:45
jeblairso i think both of our action items here sound good.19:45
*** ptoohill_ has joined #openstack-meeting19:45
jeblairanything else on the topic?19:45
rainyafungi, anteaya, jeblair: i am late to the meeting, but this type of liasoning thing sounds right up my ally so would like to consider being part of it19:45
fungiright. at the moment many of them assume they need to come to us because there's no other published point of contact, when we're not actually the people seting this policy for the projects in question19:45
*** Duane has joined #openstack-meeting19:45
fungiand yeah, nothing else on this topic19:46
fungiother than thanks rainya!19:46
*** comay has joined #openstack-meeting19:46
jeblairrainya: cool, clarkb and fungi have action items, so hopefully we can review those at the next meeting and figure out what needs doing19:46
* fungi nods19:47
jeblair#topic  Publish devstack.org content under infra (anteaya)19:47
*** openstack changes topic to "Publish devstack.org content under infra (anteaya) (Meeting topic: infra)"19:47
*** sarob has quit IRC19:47
anteayaI think this is done19:47
anteayafungi: did the redirect happen from devstack.org?19:47
jeblairooh, is there a direct url you can share?19:47
fungi#link https://review.openstack.org/#/c/130001/19:47
*** Mandell has joined #openstack-meeting19:47
*** hashar has joined #openstack-meeting19:47
*** sarob has joined #openstack-meeting19:47
fungineeds reviews19:47
AJaeger_#link http://docs.openstack.org/developer/devstack/19:47
jeblairhow cool!19:48
rainyaoooooh, nice!19:48
funginot quite sure yet why my change is failing19:48
anteayano kidding19:48
anteayabut there it is19:48
jeblairso once fungi solves all the problems, we should be able to set up a redirect from devstack.org19:48
rainya(i am ETO today for grad school assignments and know what I will be playing with between papers)19:49
fungibut anyway, yeah, once the redirect is in place on static.o.o we should be done19:49
clarkbwoot19:49
anteayafungi: yay19:49
jeblairbtw, i'm assuming we made a decision somewhere to do a redirect rather than continuing to host on devstack.org directly?19:49
anteayaAJaeger_: thanks for the publish jobs!19:49
anteayalast meeting or the one before?19:49
fungijeblair: yeah, i believe dtroyer came out in favor of that19:49
AJaeger_And mordred fixed devstack so that we could publish easily19:50
fungihe can chime in if he's around, but i'll add him to the redirect review too19:50
*** Duane has quit IRC19:50
jeblairwfm19:50
jeblair#topic  Drop gate-{name}-python26 from python-jobs template and specify it explicitly - and python2.6 deprecation (krotscheck, fungi, ajaeger)19:50
*** openstack changes topic to "Drop gate-{name}-python26 from python-jobs template and specify it explicitly - and python2.6 deprecation (krotscheck, fungi, ajaeger) (Meeting topic: infra)"19:50
krotscheckhttps://review.openstack.org/#/c/128736/ is waiting on clarkb19:50
clarkbI am going to review that change as soon as I have a moment19:50
clarkbto double check the thing from my last -119:51
clarkband will merge so we should be moving on that19:51
*** e0ne has joined #openstack-meeting19:51
* AJaeger_ is confused with the other reviews - I've added links to the meeting page.19:51
*** terryw has joined #openstack-meeting19:51
krotscheckThe other reviews seem to be in a weird merge conflict.19:51
AJaeger_I see mixed messages on the removal of python26 jobs from projects - how do we want to conintue here?19:51
*** sarob has quit IRC19:52
AJaeger_krotscheck: I'll fix the merge conflicts tomorrow - thanks for doing it last night!19:52
krotscheckAJaeger_: Anytime!19:52
clarkbfor projects with stable icehouse and or juno we will only run py26 on those two branches19:52
*** tbarron has joined #openstack-meeting19:52
clarkbif a project is a lib project of those projects with stable branches but does not have stable branches we will continue to py26 on master19:52
clarkbthat list is basically anything in the oslo program and the python-*clients19:52
clarkbeverything else should stop with py26 testing19:53
fungiAJaeger_: on 129433 dhellmann did say to stop running it on oslo-incubator as i suspected we should19:53
pleia2clarkb: stackforge projects stop too?19:53
AJaeger_fungi, ok, I'll update 129433.19:53
krotscheckIf the PTL or a project member expresses a strong dislike (-1) for running only on branches, what do we do? Ignore them?19:53
clarkbfungi: oslo-incubator has stable branches iirc19:53
*** dane_leblanc has quit IRC19:53
*** otherwiseguy has quit IRC19:53
*** adahms has joined #openstack-meeting19:53
clarkbfungi: so we should test on their stable branches19:53
dhellmannfungi: actually, we may need to wait until we graduate the bits that are used in the client libs19:53
fungiclarkb: based on weird decisions between ttx and dhellmann some libs do have stable/icehouse and stable/juno branches where they backported out-of-order fixes19:53
clarkbkrotscheck: for openstack*/ projects yesish we should explain why19:53
dhellmannfungi: we expect that to happen this cycle19:53
*** eglynn has joined #openstack-meeting19:53
clarkbso not complete ignoring19:54
* dhellmann adopts hurt expression19:54
clarkbfor stackforge projects I think we remove py26 and let projects add it back19:54
* anteaya pats dhellmann colsolingly19:54
clarkbwe should get this done early so that no one screams in a year19:54
* ttx looks positively shocked19:54
pleia2ok19:54
clarkbscreaming now is better than screaming then19:54
jeblairyep19:54
*** amcrn has quit IRC19:54
ttx"in stable/icehouse, no one hears you scream"19:55
AJaeger_So, ignore any -1 on https://review.openstack.org/129434 and ask them to send a patch?19:55
fungidhellmann: oh, stable servers are going to depend on incubated libs from master?19:55
clarkbAJaeger_: yes I think that will help us track it better via git history19:55
*** tbarron has left #openstack-meeting19:55
clarkbAJaeger_: if they propose soonish we can merge it all together so that there is not period of not testing19:55
*** changbl has quit IRC19:55
AJaeger_should we send an email to openstack-dev pointing these changes out?19:56
*** neelashah has joined #openstack-meeting19:56
clarkbAJaeger_: ya we should probably do that once we have a set of changes we are happy with19:56
dhellmannfungi: there are parts of the client libs in the incubator, and the client libs need to work with 2.6, so the incubator needs to work with 2.619:56
clarkb(maybe that is now?)19:56
*** dboik has joined #openstack-meeting19:56
fungidhellmann: yeah, i still have no idea what that means exactly, so i'm just going to take your word for it for now19:57
jeblairsomeone want to volunteer to write that email?19:57
*** JRobinson__ has joined #openstack-meeting19:57
AJaeger_clarkb: I need to rebase everything and address the comments on oslo first - should be ready tomorrow (unless somebody takes over the patch)19:57
rainyaI'd like clarification since it will impact current projects i'm working on (everything is 2.6 still in the public cloud) is "this cycle" Kilo or Juno?19:57
AJaeger_rainya: kilo19:57
dhellmannfungi: there's an incubator module called "apiclient" that is synced into some of the client libraries, and there's another called something like "cliutils" that is the same19:58
fungirainya: kilo19:58
AJaeger_rainya: juno is out and finished19:58
*** Duane has joined #openstack-meeting19:58
*** Duane has quit IRC19:58
*** changbl has joined #openstack-meeting19:58
fungidhellmann: oh, and the stable servers are going to start using those (directly or indirectly) from somewhere other than syncing from the incubator?19:58
rainyaAJaeger_, thank you; I knew juno was finished, but wanted to be explicit as I had heard it go back and forth earlier this month19:58
clarkbI can write that email if no one else wants to be the endpoint for responses :)19:58
fungianyway, we can take the oslo-incubator design details discussion for later19:59
*** boris-42 has quit IRC19:59
clarkb#action clarkb write py26 deprecation email19:59
* AJaeger_ shares the blame since he wrote the patches ;)19:59
*** dane_leblanc has joined #openstack-meeting19:59
*** markmcclain1 has quit IRC19:59
AJaeger_thanks, clarkb19:59
*** markmcclain has joined #openstack-meeting19:59
jeblairwe're at time.  thanks everyone!19:59
anteayathanks jeblair19:59
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Oct 21 20:00:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-21-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-21-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-10-21-19.00.log.html20:00
jeblairoh one second over20:00
vishyyou and your extra seconds20:00
ttxAnyone here for the TC meeting ?20:00
vishyo/20:00
mikalYep20:00
markmcclaino/20:00
russellbo/20:00
redroboto/20:00
jeblairo/20:01
*** dboik has quit IRC20:01
ttxjgriffith, annegentle, mordred, devananda, jaypipes, sdague, dhellmann : around ?20:01
jaypipeso.20:01
*** AJaeger_ has left #openstack-meeting20:01
jaypipeso/20:01
*** pcrews has left #openstack-meeting20:01
jgriffitho/20:01
ttxI think sdague is still parenting or planting LEDs20:01
annegentlehere20:01
*** ociuhandu has left #openstack-meeting20:01
anteayajaypipes: the low 520:01
jaypipesindeed.20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Oct 21 20:01:53 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
*** derekh has quit IRC20:01
dhellmanno/20:02
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
ttxFirst meeting of the Kilo season ! woohoo20:02
devanandao/20:02
*** baoli has joined #openstack-meeting20:02
russellb\o/20:02
*** wenlock has left #openstack-meeting20:02
ttx#topic Welcome new Kilo TC members20:02
*** openstack changes topic to "Welcome new Kilo TC members (Meeting topic: tc)"20:02
ttxwelcome back jgriffith20:02
jaypipeswelcome jgriffith20:02
ttx#link https://review.openstack.org/12927420:02
dhellmannjgriffith: o/20:02
jeblairwelcome jgriffith!20:02
ttxThis is housekeeping, will approve now unless someone complains20:02
jgriffith:)  Thanks!!!!20:02
*** zz_ttrifonov is now known as ttrifonov20:03
*** joesavak has joined #openstack-meeting20:03
ttx#topic Election of the Kilo TC chair20:03
*** openstack changes topic to "Election of the Kilo TC chair (Meeting topic: tc)"20:03
ttxIs anyone else interested in chairing the TC ?20:03
ttxI pushed as a candidacy:20:03
*** chris-_ has joined #openstack-meeting20:03
ttx#link https://review.openstack.org/12927520:03
mordredo/20:04
*** nshaikh has joined #openstack-meeting20:04
mordrednot really here, but I support ttx20:04
annegentlemordred: heh I thought you were volunteering yourself20:04
*** david-lyle has quit IRC20:04
ttxIf you don't want to propose yourself as alternative, just vote on that one20:04
annegentlettx: keep on keeping on20:04
ttxwell, it's now part of my job description, so I guess my employer agrees20:05
russellbttx: you've done an awesome job, thanks :)20:05
* dhellmann imagines "stay calm, and thierry on" t-shirts20:05
ttxdhellmann: lol20:05
jaypipeslol20:05
annegentledhellmann: nice20:05
mikalCafe press someone?20:05
* devananda lurks in this meeting while lurking in a f2f meeting20:05
markmcclainttx: congrats looks like you have enough votes20:05
ttxyep, approved20:06
devanandattx: grats!20:06
ttxThanks everyone!20:06
*** jsavak has quit IRC20:06
dhellmannttx: thank you for signing up for another round :-)20:06
ttxI won't stop now that it's becoming fun20:06
ttx#topic Cross-project workshops track scheduling20:06
*** openstack changes topic to "Cross-project workshops track scheduling (Meeting topic: tc)"20:06
ttxSo... We need to work this week on selecting the cross-project workshops20:07
ttxWe have 18 40-min slots available20:07
ttxAnd a lot of proposals @20:07
ttx#link https://etherpad.openstack.org/p/kilo-crossproject-summit-topics20:07
ttxWho is interested in working on the final selection ? Last time I did it with Russell, wouldn't mind rotating20:07
markmcclainI'd be happy to help work on it20:07
*** f13of13o has joined #openstack-meeting20:07
*** chris- has quit IRC20:07
russellbhappy to help20:07
annegentleI can too20:07
russellblast time really everyone participated20:07
*** zehicle has joined #openstack-meeting20:07
russellbor most at least20:07
russellbetherpad, where everyone left a -2/-1/0/1/2 score and comments20:08
russellband that got us most of the way there20:08
jeblairi would like to help20:08
jeblairi thought the process last time worked well20:08
dhellmannI'd like to be involved, too20:08
ttxHmm, ok, so we could etherpad it into shape20:08
jaypipesI've added my thoughts and interested in tags in there...20:08
annegentledo we know how many are on there? I scanned it earlier today20:08
russellbyeah, let's etherpad it up20:08
*** kebray has joined #openstack-meeting20:08
anteayaline 71 can be removed unless you want to keep it for tracking purposes20:08
ttxand then who wants to work on the synthesis ? russell & mark ?20:08
*** topol has quit IRC20:08
vishydespite all the discussion of big-tent openstack on the ml20:09
russellbjust need someone to organize the etherpad, and then collect results, help figure out things in the grey area, figure out the proposed schedule20:09
vishythere is only one session about fixing testing: Implications of moving functional tests to projects20:09
russellbttx: works for me20:09
vishyseems like we need more there20:09
annegentleAPI working group also got a slot20:09
markmcclainttx: sure20:09
jgriffithvishy: +120:09
mikalvishy: makes a good point20:09
jgriffithI've been away, so not clear n if/what plan there might be20:09
ttxvishy: could also be done as a QA session20:09
*** cody-somerville has joined #openstack-meeting20:09
annegentledocs does not have a separate track so cross-project is it for docs20:09
ttx#action all TC members to weigh in on therpad20:09
jeblairvishy: i don't think the big tent is about fixing testing; that's one very small part.20:10
jgriffithttx: but if the proposal is moving some of it to projects it's kinda "anti-QA" :)20:10
russellbttx: what kind of timeline do we have for this20:10
russellbi'm actually traveling the rest of this week ...20:10
ttx#action russellb and markmcclain to crystallize it into a schedule near the end of week20:10
russellbha20:10
jeblairttx: i think the functional testing cross-project item is important20:10
*** mrmartin has quit IRC20:10
jeblairttx: i'm hoping you are not suggesting scheduling that as a qa session20:10
ttxwe need final schedule by Tuesday next week20:10
ttxjeblair: that was not my suggestion20:10
jeblairttx: okay; what were you suggesting be a qa session?20:11
ttxjeblair: vishy was saying only one session was proposed about testing -- I expect there to be plenty of QA sessiona bout testing.20:11
vishyjeblair: that is one part that will require a lot of cross-project discussion, but my point was that there are no other sessions about other parts (that I could find)20:11
annegentleoh maybe API working group didn't get a separate session.20:11
*** aysyd has quit IRC20:11
jeblairvishy: *nod* do you think something is missing?20:12
ttxAPI wg definitely needs a slot20:12
markmcclain+120:12
annegentleyep ttx20:12
russellbso how about everyone go through and give some -2/-1/0/+1/+2 votes by the end of the week?20:12
ttxrussellb: so you can't really work on it by the end of week ?20:12
annegentleand honestly the API docs/specs could go in API working group.20:13
russellband then we can make the schedule monday/tuesday?20:13
annegentlemostly it's about consolidation agreement20:13
russellbor you think we should expedite further?20:13
ttxrussellb: wfm20:13
ttxno, scheduling on Monday/Tuesday sounds good to me20:13
annegentleCan someone guesstimate a count?20:13
russellbannegentle: count?20:13
*** ajo_ has quit IRC20:13
vishyjeblair: I don’t have any specific topics offhand, but maybe a general big-tent topic to discuss changes20:14
dhellmannannegentle: we have 32 proposals20:14
ttx<ttx> We have 18 40-min slots available20:14
vishymaybe it will be clearer after we discuss/vote on the dhellman proposals20:14
annegentlethanks dhellmann (nice way to apply technology to that question)20:14
dhellmannannegentle: automate everything20:14
ttxrussellb: oh and we have some time periods where only two run in parallel, and some time priods when 3 run in parallel20:15
russellbfun20:15
ttxthe idea being to give the slots where only 2 sessions run in parallel to topics we want to maximize attendance for20:15
russellbwe can sort that out monday once we have a list20:15
*** david-lyle has joined #openstack-meeting20:15
annegentleoh criminey20:15
ttxyep, fun20:15
ttxOK, I think we have a plan for this20:15
ttxworst case scenario we close it at the TC meetign next week20:15
russellbk20:16
russellbso we just need votes on the etherpad by friday20:16
annegentleayup20:16
russellbto start20:16
*** ayoung has joined #openstack-meeting20:16
ttxyes20:16
zehicleo/20:16
annegentlettx: is there pod room for cross-project spillover?20:16
ttx#undo20:16
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x319cf10>20:16
ttx#action russellb and markmcclain to crystallize it into a schedule on Monday/Tuesday next week20:16
ttxannegentle: there are pods.20:17
ttxok, next topic...20:17
ttx#topic TC-owned repositories20:17
*** openstack changes topic to "TC-owned repositories (Meeting topic: tc)"20:17
ttxWe have a few governance changes related to TC-owned git repositories20:17
*** jamielenz has joined #openstack-meeting20:17
*** jamielenz is now known as jamielennox20:17
ttxThose currently appear nowhere, and don't technically belong to programs.yaml20:18
ttx* Add list of repositories owned by the TC (https://review.openstack.org/125733)20:18
*** jecarey has quit IRC20:18
ttxThis review ^ adds the file describing those.20:18
ttxThe next two are adding two repos:20:18
ttx* Add a new openstack-specs repo under the control of the TC (https://review.openstack.org/125509)20:18
ttx* Adds a new api-wg repo under the control of the TC (https://review.openstack.org/129188)20:18
*** emagana has joined #openstack-meeting20:18
jeblair20:17 < clarkb> jeblair hrm I can probably swing something later in afternoon. maybe 3ish?20:18
ttxI'm fine with considering them part of the openstack mission and justifying their presence in the openstack/* namespace with a TC stamp for the time being20:18
jeblair(oops)20:19
ttxsince that's what our current governance mandates20:19
jeblairi think that's a swell idea20:19
ttxsounds like a good workaround20:19
jeblairi think giving the api wg a tc charter is a good idea too20:19
dhellmannwe should document it to make it official20:19
markmcclainjeblair: ++20:20
dhellmannit == the ownership plan20:20
anteayaso when reviewing patches to create new tc repos20:20
ttxApproving the first one since it has enough20:20
anteayawhere do I look for the mandate?20:20
anteayathe tc meeting logs?20:20
annegentleso the tc is ultimately accountable, or the tc is ultimately governing?20:20
russellbso, api wg proposes content, but TC reviews/approves?20:20
ttxanteaya: in the governance repo ?20:20
dhellmannanteaya: the new file created by https://review.openstack.org/12573320:21
anteayattx okay I shall refer to the governance repo20:21
*** colinmcnamara has joined #openstack-meeting20:21
ttxrussellb: personally I see it more as a working group ,they build recommendations20:21
*** rockyg has joined #openstack-meeting20:21
annegentleI was thinking of it like api-wg proposes guidelines, TC or api-wg can +1, with one person being the final +1 like how ttx serves on TC voting20:21
anteayadhellmann: awesome20:21
ttxthen we'll see if we should force it down anyone throat20:21
ttxbut I'd rather not ti20:21
ttxto*20:21
annegentlehow do we know how many votes are sufficient on reviews?20:22
ttxI'd let the wg organize itself20:22
jaypipesannegentle: would be up to the API WG to determine a policy.20:22
annegentlejaypipes: ok that's fair20:22
russellbi guess my only concern is that we're empowering a group, without the group having done work yet to build their credibility20:22
ttxFrankly, it's not the first time this working group is created20:22
ttxso I'd ratrher let them start producing something20:22
annegentleyeah I'd rather support success :)20:22
russellbwe don't bless a project the day they create a wiki page, we expect them to write a bunch of code and build a community around it20:23
ttxwe have had API czars before.20:23
jaypipesrussellb: well, we're empowering a group to create guidelines, not enforce those guideliens.20:23
ttxthey just never took off20:23
russellbjaypipes: fair, though it's implied everyone should follow them, right?20:23
jeblairrussellb: if they come up with something we think is a good idea?20:23
ttxrussellb: at this point, I wouldn't say that20:23
ttxI want to let them create something20:24
dhellmannmaybe the policies in this specs repo aren't what people should follow, but it gives them a place to create those policies?20:24
ttxIf we like it, we can push it forward20:24
jeblairdhellmann, ttx: ++20:24
russellbif we're just creating a repo that's fine20:24
jaypipesrussellb: eventually I would like the guidance from the WG to be enforceable, but the guidelines should stand on their own merit. the problem is, who decides if the guidelines have merit?20:24
ttxAt this point it's just "creating a repo" yes20:24
russellbjaypipes: we do, i suppose20:24
ttxand let them produce awesome recommendations20:24
*** e0ne has quit IRC20:25
dhellmannright, we'll have to make a decision about what to do with the policies after they exist20:25
jaypipesrussellb: right, which is why it's proposed to go under the purview of the TC's repos.20:25
russellbwhich is why my first question was, who approves the contents of the repo20:25
jaypipesrussellb: frankly, I'd just be happy to have an agreed-upon place to put API guidance proposals :)20:25
annegentlerussellb: right, that's what I was wondering too20:25
annegentleThe repo is a step up from the wiki page20:25
ttxrussellb: they build the recommendation. Then we see if we like it enough to push it20:25
annegentlewith reviews, etc.20:26
dhellmannrussellb: the working group will approve them, though I'd like the TC to have voting rights in all working groups. after the proposed policies are defined we should probably put them in the governance repo20:26
*** Sukhdev has quit IRC20:26
*** sarob has joined #openstack-meeting20:26
anteayain addition to the name of the repo that can be created, should we also have the name of someone infra can seed the core group for the repo? https://review.openstack.org/#/c/125733/1/reference/technical-committee-repos.yaml20:26
russellbok, the end goal workflow just isn't totally clear to me20:26
ttxanteaya: how about the owner of the change, unless specified otherwise in the commit message ?20:27
dhellmannrussellb: I agree, we're still figuring that out20:27
anteayattx if we like that, that is fine with me20:27
*** jecarey has joined #openstack-meeting20:27
ttxrussellb: at this point they need a git repo to experiment the process20:28
russellbfair enough.20:28
dhellmannanteaya: please also add the tc group (whatever it's actually called) to the new groups that can vote +2/-2 on these new repos20:28
jeblairso how about we let the wg work on creating something, they come back to us when they are done, and we approve it.  we try to keep in touch in the meantime.  but we make it clear that a commit landing in that repo at this point does not make it policy.20:28
*** VijayB_ has quit IRC20:28
*** yamamoto has joined #openstack-meeting20:28
*** nellysmitt has quit IRC20:28
dhellmannjeblair: ++20:28
russellbjeblair: wfm20:28
ttxIt's ultimately under our control, so we can "fix" it if we don't like how the organize20:28
*** jordandh has quit IRC20:28
*** VijayB_ has joined #openstack-meeting20:28
ttxAny TC member volunteering to keep track of where this is going ? jaypipes maybe ?20:29
annegentlettx: that's a bit... unsettling or demotivating for the wg20:29
jaypipesanything other than a wiki page works for me. :)20:29
jaypipesttx: yes, I will take point on it.20:29
anteayadhellmann: does the tc group consist of the members of the tc?20:29
ttxannegentle: I think it's less demotivating than waiting before giving them a git repo :)20:29
anteayadhellmann: I'm guessing yes, but would like to be sure20:29
russellbthe suggestion of just using openstack-specs kinda makes sense too20:29
russellbbut i don't care much either way20:29
dhellmannanteaya: yes, there must be a group in gerrit somewhere that has all of the tc members in it, and that's the one I mean20:29
jeblairmaybe we should propose a commit to governance chatering the api wg and recording this intent?20:30
annegentlerussellb: that might be a good way to look at it also20:30
ttx#info jaypipes volunteers to report back on TC with API WG progress20:30
dhellmannanteaya: whoever can +1/-1 on the governance repo20:30
russellbjaypipes: thanks20:30
*** jordandh has joined #openstack-meeting20:30
dhellmannjeblair: ++20:30
jaypipesno problemo.20:30
anteayadhellmann: https://review.openstack.org/#/admin/groups/205,members20:30
jgriffithjeblair: +120:30
* ttx looks at vote counts on that repo20:30
annegentleapi working group is basically a specialty for cross-project20:30
dhellmannanteaya: that's it20:30
anteayagreat, thanks20:30
*** ayoung has quit IRC20:30
ttxWe have 8 YES there, so I'll approve it now20:30
ttxunless someone screams20:31
ttxok done20:31
ttxthat should unblock the repo creation20:31
ttx#topic Other governance changes20:31
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"20:31
ttx* Move config to system-config in the infra program (https://review.openstack.org/129438)20:31
ttxThis one is housekeeping, will approve unless someone disagrees20:32
jeblairwe're totally not renaming it back ;P20:32
ttxgood to know!20:32
*** boris-42 has joined #openstack-meeting20:32
ttx* Add heat-translator to the Heat program (https://review.openstack.org/127349)20:32
*** carl_baldwin has quit IRC20:32
ttxThis one has Heat PTL's +1 on it, will approve unless someone complains now20:32
*** yamamoto has quit IRC20:32
*** changbl has quit IRC20:32
*** julim has quit IRC20:33
ttx#topic Stalled changes20:33
*** openstack changes topic to "Stalled changes (Meeting topic: tc)"20:33
ttx* Remove support for vendor extensions from our code (https://review.openstack.org/122968)20:33
mikalI abandoned my one of those20:33
ttxNot a lot of progress there...20:33
*** _nadya_ has quit IRC20:33
*** varora has joined #openstack-meeting20:33
ttxmikal: yes, I cleaned it up from list20:33
jeblairoh, this has been revised20:34
ttxyes20:34
jeblairit's no longer a flame but a serious suggestion20:34
mikalOh, interesting20:34
mikalI was avoiding the flame20:34
ttxlooks less like a flame yes20:34
*** padkrish has joined #openstack-meeting20:34
*** nati_ueno has joined #openstack-meeting20:34
zanebless flamey, still quite woolly20:34
jeblairi will take a look at it again, because i think the idea merits consideration20:35
* dhellmann wonders who dared mordred to use whereas20:35
zanebdhellmann: I believe it was vishy20:35
ttxso, let's keep this one active ?20:35
dhellmannzaneb: that sounds like something he'd do20:35
*** carl_baldwin has joined #openstack-meeting20:35
vishy+120:35
ttx* Add a docs environment to the testing interface (https://review.openstack.org/119875)20:35
ttxThis one also failed to pick up support... what's the next step there ?20:35
*** mchalla has joined #openstack-meeting20:35
* jaypipes might have to reconsider that review just because of the use of the phrase "incent the vendor to align with gusto."20:36
jeblairttx: poke mordred and see if he has further thoughts on it?20:37
dhellmannttx: I think we mostly agreed with jeblair to leave the "docs" target as optional20:37
ttxyes, I guess...20:37
annegentleI'm okay with docs target as optional20:37
*** Riddhi has quit IRC20:37
ttx#action ttx to reach to mordred to check for further thoughts or abandon on https://review.openstack.org/11987520:37
jgriffithif it had one more "Whereas" line I would've been +120:37
annegentleI cna change my vote20:37
ttx* Naive script to verify extra-atc foundation status (https://review.openstack.org/121696)20:38
dhellmannand if it's optional we don't have to include it in the guidelines20:38
dhellmannttx: I just abandoned that one20:38
ttxwas abandoned20:38
*** nati_uen_ has joined #openstack-meeting20:38
*** jordandh has quit IRC20:38
dhellmannI'll try to find time to resubmit it to the other suggested repo20:38
annegentleI support that tox -edocs exists20:38
ttxalrighty. I feel like we are much more efficient in Kilo, we processed like 12 chnages in 39 minutes20:38
*** padkrish has quit IRC20:39
*** jordandh has joined #openstack-meeting20:39
ttxNow for a funnier topic20:39
jeblairannegentle: ++ (and i use it!); i just want to make sure our deliverables are consistently generated20:39
*** Murali_ has joined #openstack-meeting20:39
ttx#topic Governance structure reform20:39
*** openstack changes topic to "Governance structure reform (Meeting topic: tc)"20:39
ttxSo we obviously don't have the time to thoroughly discuss those proposals in the remaining 20min20:40
ttxwe have two things up for review:20:40
ttx* Doug's series (https://review.openstack.org/#/q/status:open+topic:big-tent,n,z)20:40
ttx* Jay's alternative (https://review.openstack.org/126582)20:40
dhellmannwould everyone prefer to continue reviewing my series as a series, or should I squash them into one commit?20:40
ttxPersonally I feel like they are both going in the same direction, but from opposite ends20:40
ttxdhellmann: I don't mind the series, personally20:40
devanandadhellmann: squash please. perhaps 2 changes20:40
*** Mandell has quit IRC20:40
jeblairi really like that dhellman (and then jaypipes) put those changes up for review; i do think that was the natural next step20:41
jeblairbut in my mind it has exposed that we may still have some big-picture ideas to agree on20:41
jeblairso maybe we can discuss those at the summit to agree on high level "requirements" and then further refine them in review?20:41
ttxwouldn't mind squash either20:41
mikalI'd like to discuss the premise of dhellmann's if we have time for that20:41
*** markwash__ has quit IRC20:41
dhellmannjeblair: yes, that's exactly why I put the changes together :-)20:41
ttxjeblair: ++20:41
devanandajeblair: ++20:41
*** jamielennox has quit IRC20:41
ttxDoug's incrementally changes the governance to introduce big-tent things in20:41
ttxJay's rips off the charter first and then rebuilds20:41
ttxBut the end result is not that different.20:41
*** jprovazn has quit IRC20:41
zanebjeblair: why not discuss on the mailing list?20:41
ttx(imho)20:41
dhellmannttx: do we have a formal in-person meeting of the tc scheduled for any time during the summit?20:42
*** nati_ueno has quit IRC20:42
ttxI think I have an empty slot on Wednesday at 4am20:42
mikalI feel like face to face is going to go better than yet another 100 email thread20:43
devanandattx: lol20:43
markmcclainmikal: +120:43
mikalBut yeah, I don't know when that would happen20:43
dhellmannmikal: yeah, but if we don't actually have a scheduled meeting it's going to be 100 f2f meetings20:43
mikalBut I think my underlying concern here is this:20:43
*** mattgriffin has quit IRC20:43
devanandaf2f ++, with follow up being changes to (or new) patches to governance repo20:43
ttxI think we need to converge to a single proposal and then expose it to ML20:43
zanebmikal: maybe for you, but shouldn't the whole community be involved?20:43
mikalWe're trying to solve our own failure of leadership with yet more governance20:43
jgriffithsounds like great dinner conversation :)20:43
mikalThat's wrong20:43
jgriffithFoood fight!!20:43
mikalWe should just lead more effectively20:43
mikalzaneb: maybe, we certainly shouldn't exclude them20:44
anteayamikal: I don't see it as failure of leadership20:44
ttxmikal: I wouldn't say "more governance" tbh20:44
anteayaI see is as incredbile growth20:44
mikalzaneb: however, the TC needs to work out waht they think first20:44
anteayaresulting from great leadership20:44
devanandamikal: we are evolving our govnernance in response to growth.20:44
devanandamikal: I dont know whether it's more or less gov20:44
jeblairzaneb: i generally consider that summit sessions do not exclude our community20:44
jgriffithttx: I like your proposal of solidifying a bit and going to ML20:44
devanandabut it's different20:44
annegentleI think requirements first is a good discussion to have.20:44
ttxI think the general issue was discussed on ML threads already20:44
jgriffithttx: but going to ML with structure and boundaries :)20:44
ttxthe next step is a formal proposal20:45
dhellmannmikal: I largely agree, but think some of the proposals will also make that easier.20:45
jaypipesmikal: actually, my proposal rips away governance, not adds to it.20:45
*** dboik has joined #openstack-meeting20:45
ttxthat can be reviewed on Gerrit/discussed on ML20:45
jaypipesrather, rips away rigid structure, rather than adds to it.20:45
dhellmannjeblair: interesting, should we put this on the cross-project session schedule?20:45
ttxbecause another round of talking generally about the problem won't really help20:45
*** ayoung has joined #openstack-meeting20:45
ttxI'd say that both of the proposals on the table today remove governance20:46
mikalI like the idea of a cross project session20:46
jeblairdhellmann: sounds like a good idea20:46
markmcclaindhellmann: +120:46
* dhellmann adds to the etherpad20:46
ttxI think I suggested such a workshop20:46
ttxalready20:46
* ttx checks20:46
*** radez is now known as radez_g0n320:46
dhellmannttx: #12?20:47
*** ayoung has quit IRC20:47
dhellmann"growth challenges"20:47
ttxyes, including 12.520:47
*** ayoung has joined #openstack-meeting20:47
jaypipes"13 kids and counting"?20:47
*** asalkeld has joined #openstack-meeting20:48
jeblairjaypipes: you mean 120 kids?20:48
*** noelbk has quit IRC20:48
ttxdhellmann: so maybe just +1 that? Or build upon it ?20:48
annegentlewe're up to 20 rest api definitions if you include incubating20:48
dhellmannttx: OK20:49
*** VijayB_ has quit IRC20:49
ttxAt this point it's also fine of others want to push solid proposals up for review, like Doug and Jay did20:49
ttxGood to see what the various options are20:49
*** VijayB has joined #openstack-meeting20:49
jaypipes13 was referring to the TC membership :)20:49
ttxSo plan is like this20:49
ttx1. Big ML thread about the problem (done)20:50
ttx2. Formal suggestions up on review (in progress)20:50
ttx3. Workshop on potential convergence (Paris)20:50
*** nshaikh has left #openstack-meeting20:50
ttx4. Converged plan proposed on review/ML for further discussion (if we converge)20:51
*** jmontemayor has quit IRC20:51
ttxSounds good to me20:51
*** neelashah has quit IRC20:51
jeblair++20:51
dhellmannI'll try to address all of the comments on my patch series and squash it together into a smaller number of changes before the summit20:51
ttxrevolution is difficult, but Paris is the right place to do it.20:52
annegentledhellmann: thanks, I'll find it easier as well20:52
annegentlettx: +120:52
*** neelashah has joined #openstack-meeting20:52
ttx#topic Open discussion20:52
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:52
*** noelbk has joined #openstack-meeting20:52
ttxI have one question (which I'll also ask the PTLs in the next meeting)20:52
ttxThe M design summit time span20:53
ttxThat's the one after Vancouver, located in APAC20:53
ttxThe main conference will happen Tuesday - Thursday20:53
ttxMonday will have Ops Summit, analyst day, and other smallish pre-summit things20:53
ttxFoundation staff needs to close on the contract and asks when should design summit be ?20:53
annegentleFriday off? :)20:53
ttxWe can do Tuesday - Friday, but then we fully overlap with the conference, which may impact the PTLs ability to present at the conference20:53
*** VijayB has quit IRC20:54
*** akuznetsova has quit IRC20:54
ttxWe can do Wednesday - Saturday, but then... Saturday. Long week.20:54
ttxWe can do Monday, Wednesday-Friday (break on Tuesday), too. But feels weird.20:54
dhellmannwhat did we do in hong kong?20:54
ttxWhat is your general preference on that ?20:54
* dhellmann can't remember yesterday20:54
*** markwash__ has joined #openstack-meeting20:54
devanandawed-fri20:54
annegentleall-cross-project by M :)20:54
vishycan we do monday - thursday? just to try the opposite?20:54
annegentleonly mid-cycles for the six months prior20:54
ttxvishy: I don't like that, because everyone shows up on the design summit20:54
russellbmon-thurs, or tues-fri20:54
vishyi guess that doesn’t really help20:54
ttxwe diud that once (oin POrtland)20:55
russellbbasically, anything but making the week 6 days20:55
devanandai've just accepted that conferences are basically going to be sun-fri20:55
annegentlerussellb: yup20:55
jgriffithrussellb: +120:55
vishyi like the monday, w-f idea20:55
annegentleI'll keep pushing for four days20:55
*** kebray has quit IRC20:55
zanebdhellmann: iirc we did Tue-Fri in HK20:55
annegentleaccept the overlap20:55
*** gyee has joined #openstack-meeting20:55
jgriffithcuz in APAC for many of us it's 6-7 days as is20:55
russellband joint tc+board meeting on sunday20:55
vishydo they have any candidate cities yet?20:55
russellbso that's another day20:55
russellbsooo long20:55
ttxrussellb: I guess the board thing could be on the Monday there20:56
dhellmannannegentle: do you think if the sessions were all cross-project that would make it easier for ptls to present?20:56
ttxvishy: yes, but won't say until contract is signed20:56
russellbttx: true, but lots of people want to join the ops meetup and stuff ..20:56
russellbwhich is probably more valuable as a day off than a main conf day honestly20:56
ttxSoo. not Wed-Sat20:56
annegentledhellmann: more solving for why have a design summit at all20:56
anteayatuesday-friday20:56
russellbso my vote is tues-fri20:56
dhellmannannegentle: ah20:56
anteayattx can we pick a city that has some M options?20:56
annegentlewith the growth, etc.20:56
ttxyeah, I think Tue-Fri is the less wrong solution20:56
anteayalike Melbourne?20:56
dhellmannyeah, I think tue-fri is best20:57
markmcclainTues-Fri20:57
russellbttx: ++20:57
*** VijayB has joined #openstack-meeting20:57
devananda++20:57
dhellmannanteaya: ++20:57
asalkeldanteaya, ++20:57
anteayattx or like not japan20:57
anteayaI want to go to japan20:57
anteayabut not many M's there20:57
*** akuznetsova has joined #openstack-meeting20:57
ttxMitsubishi ?20:57
russellbthe amount of answers i expect ttx to give about possible locations: 020:57
*** jehb has quit IRC20:57
mikalSo...20:57
ttxrussellb: you would be right20:57
anteayattx I smell a trademark issue20:57
mikalDid we just decide anything with the L summit?20:57
annegentleheh20:57
*** Mandell has joined #openstack-meeting20:58
*** padkrish has joined #openstack-meeting20:58
mikalTues - Fri was popular last time the community was asked20:58
*** SlickNik has joined #openstack-meeting20:58
*** SridharRamaswamy has joined #openstack-meeting20:58
ttxmikal: I think Vancouver is traditional iirc Mon-Thu conference Tue-Fri Design Summit20:58
ttxI wasn't asked any question about it20:58
mikalOh sorry20:58
mikalI have misunderstood20:58
mikalYou're asking for M?20:58
ttxonly thing I know iss that "I'll love the Design Summit area"20:59
ttxyes20:59
mikalAhhh, ok20:59
mikalWell, I vote for the same as L then20:59
mikalCause its what people are used to now20:59
jeblairanteaya: there are _tons_ of cities in japan that start with M20:59
*** VijayB has quit IRC20:59
ttxok, anything else, anyone ?20:59
anteayajeblair: great, I'm glad my geography is poor20:59
mikalOn more important issues, can we call the L release "Lemming"?20:59
ttxOh, that's true, we can pick the L name20:59
dhellmannmikal: do they have those in vancouver?20:59
anteayamikal: find a canadian city named lemming and you have a chance21:00
russellbLemons21:00
russellbLiger21:00
anteayadhellmann: no no lemmings in vanvouver21:00
mikalLa di da21:00
jeblairanteaya: 75 according to wikipedia (and that's just cities)21:00
anteayalauier21:00
anteayajeblair: cool21:00
mikalNo releases I can't pronounce please21:00
ttxok, time is up21:00
anteayalaval21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Oct 21 21:00:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-21-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-21-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-10-21-20.01.log.html21:00
mikalHeh, ttx rage quit21:00
ttxThanks everyone21:00
ttxI know to stop a meeting when we start discussing names21:01
mikalHeh21:01
markmcclainhaha21:01
annegentlehee21:01
dhellmannheh21:01
mikalVote 1 Lemming!21:01
jogoany progress about finding a home for governance docs to be published21:01
jeblair"maple ridge" -> maple21:01
*** jmontemayor has joined #openstack-meeting21:01
jeblairttx: you failed ^21:01
mikalGiven I was denied for "Herp Derp"21:01
* dhellmann rushes over the cliff behind mikal 21:01
jogottx: ^21:01
jeblairttx: http://en.wikipedia.org/wiki/Maple_Ridge,_British_Columbia21:01
*** rudrarugge has quit IRC21:01
jeblairoh, oops, 'l'21:01
zanebjeblair: off by one error21:01
jeblairquick we need to swap locations21:01
ttxdhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:01
mikalAlthough I consider Kilo a win for sarcastic release names21:02
dhellmanno/21:02
notmynamehere21:02
eglynno/21:02
mesteryo/21:02
asalkeldo/21:02
nikhil_ko/21:02
morganfainbergttx, o/21:02
devananda\o21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Oct 21 21:02:22 2014 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
anteayajeblair: yeah I wanted maple too21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttxOur agenda for today:21:02
SergeyLukjanovo/21:02
dimso/21:02
ttx(maple works because it's an element in the state flag)21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxWe didn't have 1:1 syncs today (and won't have them next week either)21:03
ttxThose will be back after the summit.21:03
*** mchalla has quit IRC21:03
ttx#topic M Design summit time span21:03
*** openstack changes topic to "M Design summit time span (Meeting topic: project)"21:03
ttxFirst same question as I just asked TC21:03
ttxThe M summit time span21:03
ttxThat's the one after Vancouver, located in APAC, one year from now21:03
ttxThe main conference will happen Tuesday - Thursday21:03
*** mchalla has joined #openstack-meeting21:04
ttxMonday will have Ops Summit, analyst day, and other pre-summit things21:04
*** dsetia has quit IRC21:04
ttxFoundation staff needs to close on the contract and asks when should design summit be ?21:04
ttxWe can do Tuesday - Friday, but then we fully overlap with the conference, which may impact the PTLs ability to present at the conference21:04
ttxWe can do Wednesday - Saturday, but then... Saturday. Long week. TC didn't like that option that much21:04
asalkeldit's still the best option21:04
ttxWe can do Monday, Wednesday-Friday (break on Tuesday), too. But feels weird.21:04
mestery-1 for Wed-Sat21:04
*** kebray has joined #openstack-meeting21:04
morganfainbergagreed -1 for wed-sat21:05
ttxasalkeld: yes, Tc concluded Tue-Fri was probably best21:05
anteayattx ha ha ha (state flag)21:05
eglynnbleeding into the Sat will make it a long trip from Europe or the US21:05
*** ChuckC has quit IRC21:05
*** mchalla has quit IRC21:05
dhellmannstandardizing on tue-fri seems like a good system21:05
*** mchalla has joined #openstack-meeting21:05
asalkeldttx, another option is the dev sessions are m-f but just some mornings21:05
mtreinishI think Tues-Fri works fine21:05
mestery+1 for tue-fri21:06
*** VijayB_ has joined #openstack-meeting21:06
eglynnso +1 that we just live with the overlap and go with tue-fri21:06
asalkeldso have some half days21:06
dhellmannasalkeld: interesting21:06
SergeyLukjanov-1 for wed-sat21:06
ttxasalkeld: I fear we would end up doing a 5-day design summit21:06
SergeyLukjanovand IMO the tue-fri works good21:06
dhellmannasalkeld: I think the counter arg to that is monday is usually the operators day21:06
*** adahms has quit IRC21:06
dhellmannalso what ttx said21:07
ttxi.e. we'd fill the "holes" with more design summit pods or off-discussions21:07
ttxand be dead on friday21:07
eglynnagreed on the hole filling21:07
asalkeldok, just an idea21:07
ttxnature abhors void :)21:07
asalkeldyou could lock the pods;)21:07
*** emagana has quit IRC21:07
SergeyLukjanovttx, ++ for hole filling21:07
ttxI'll bring the feedback back to Lauren and Claire. not saturday, slight preference for Tue-Fri21:08
SlickNik+1 for hole filling as well.21:08
*** emagana has joined #openstack-meeting21:08
ttxok, moving on21:08
ttx#topic Juno release postmortem21:08
*** openstack changes topic to "Juno release postmortem (Meeting topic: project)"21:08
ttxSo... the release went generally well.21:08
ttxThere were a bit more late respins than usual, with 5 projects doing a RC3 in the last days21:08
*** padkrish has quit IRC21:09
ttxThere was also a bit of a f*up in Glance, which started identifying release-critical bugs only after their RC1 drop21:09
ttxbut this did not seriously affect the release21:09
ttxOne interesting exercise is to look back at the "critical" bugs which justified the late respins, and ask why those were not detected by testing21:09
ttxIf the issue is critical enough to justify a late respin, it usually should have been tested in gate in the first place21:09
ttxSo those may just uncover significant gaps in testing... for example:21:10
asalkeldwe are moving the functional tests in-tree (in Heat) - I am hopefully this will help our coverage21:10
ttxCinder CHAP Authentication in LVM iSCSI driver: https://review.openstack.org/#/c/128507/21:10
ttxCinder Unexpected cinder volumes export: https://review.openstack.org/#/c/128483/21:10
ttxCinder re-attach a volume in VMWare env: https://review.openstack.org/#/c/128431/21:10
ttxCeilometer recording failure for system pollster: https://review.openstack.org/#/c/128249/21:10
ttxTrove restart_required field behavior: https://review.openstack.org/#/c/128352/21:10
ttxTrove postgresql missing cluster_config argument: https://review.openstack.org/#/c/128360/21:11
*** mdenny has quit IRC21:11
SlickNikYes, this helped uncover some 3rd party testing holes for Trove, and we're looking to address those in Kilo.21:11
*** mattgriffin has joined #openstack-meeting21:11
ttxSo in general, please have a look at your late proposed/juno backports and see if anything could have been done to detect that earlier21:11
*** mdenny has joined #openstack-meeting21:11
*** ChuckC has joined #openstack-meeting21:11
eglynnfair point21:11
asalkeldok21:11
jogohow many of those were 3rd party tested?21:11
mesteryttx: Sounds good21:12
SergeyLukjanovttx, in sahara we're already working on adding a bunch of tests to cover it (doing it after each release)21:12
ttxjogo: maybe the reattac21:12
ttxar21:12
nikhil_kgood point, we've set up a plan for kilo to avoid this21:12
jogottx: as it sounds like we have a 3rd party CI quality control issue21:12
ttxthe reattach volume in VMware env would belong in 3rd party, but the others were pretty much mainline tests imho21:12
*** emagana has quit IRC21:13
jogottx: ahh, reattach21:13
ttxAnother theme which emerged are issues with default configuration files -- although I'm not sure how we can avoid those:21:13
ttxCeilometer missing oslo.db in config generator: https://review.openstack.org/#/c/127962/21:13
ttxGlance not using identity_uri yet: https://review.openstack.org/#/c/127590/21:13
jogottx: maybe devstack tests? or something21:13
jogotesting the config files21:14
asalkelddo these project not have a sample config anymore?21:14
ttxjogo: in the glance case they were just using the deprecated options21:14
eglynnasalkeld: now generated (as opposed to static)21:14
*** jungleboyj has quit IRC21:14
asalkeldi still like the review capablity that gives you21:14
jogottx: oslo-config has a error on deprecated config option21:14
asalkeld(of having it in the tree)21:14
jogobut I last I checked it broke21:14
dhellmannjogo: ?21:14
*** padkrish has joined #openstack-meeting21:15
jogodhellmann: cause service to halt if a deprecated config option is used21:15
*** padkrish has quit IRC21:15
eglynnasalkeld: yeah, definitely pros and cons to having it as static content in-tree21:15
*** terryw has quit IRC21:15
dhellmannjogo: I don't know about that one, is there a bug?21:15
*** rockyg has quit IRC21:15
jogodhellmann: I think so, let me lok21:15
ttxnot sure how much of the "default config" we actually consume in tests21:15
*** padkrish has joined #openstack-meeting21:15
*** markmcclain1 has joined #openstack-meeting21:15
*** markmcclain1 has quit IRC21:15
*** markmcclain has quit IRC21:15
*** markmcclain1 has joined #openstack-meeting21:15
*** emagana has joined #openstack-meeting21:16
ttxanyway, that's the only "themes" I could see in the late issues in RCs21:16
jogodhellmann: https://bugs.launchpad.net/oslo-incubator/+bug/121860921:16
uvirtbotLaunchpad bug 1218609 in oslo-incubator "Although CONF.fatal_deprecations=True raises DeprecatedConfig it is not fatal" [Low,Triaged]21:16
eglynnBTW how did the gate hold up during the RC period?21:16
eglynn... flow rate seemed better behaved than during the milestones21:16
ttxIs there a significant issue that we just missed completely and is an embarassment in the release ?21:16
eglynn... clearly the patch proposal rate was way down21:17
*** cdub has joined #openstack-meeting21:17
dhellmannjogo: that bug makes it sound like apps are not correctly dying, but your comment earlier made it sound like they were dying when they should not21:17
dimsright21:17
ttxI'm not aware of any really critical issue that we let pass in the release21:17
ttxbut then, I'm no longer spending my days on Launchpad reports21:18
*** chris-_ has quit IRC21:18
ttxanything you know about ?21:18
asalkeldnothing major21:18
*** otherwiseguy has joined #openstack-meeting21:18
SlickNikeglynn: The gate seemed to hold up fairly well — didn't notice any significant delays during the RC period.21:18
jogodhellmann: yeah IMHO the fatal_deprecation should make things die21:18
jogoand they don't21:19
SlickNiknothing that I'm aware of either.21:19
dhellmannjogo: is the app catching that exception?21:19
dhellmannjogo: or are we just logging and not throwing an error?21:19
eglynnttx: nope ... we have a known issue release noted, but not critical21:19
eglynnSlickNik: agreed21:19
ttxAnything else you want to report on the release process ? Something we did and we shouldn't have done ? Something we didn't do and should have done ?21:19
dhellmannjogo: looks like the traceback in the log in that bug is showing the exception being caught by the app21:20
*** jckasper has quit IRC21:20
dimsdhellmann: jogo: we should probably take that back to oslo channel :)21:20
dhellmanndims: yeah21:20
eglynna question I've always wanted to ask about the release process21:20
asalkeldttx to my newbie eyes it seemed to work well21:20
* ttx braces for the shock21:20
eglynn... do the milestones have to be synchronized across all projects?21:20
jogodims: yup21:21
* eglynn asks in terms of mitigating the gate rush that kills us at every milestone21:21
ttxso that would be a development cycle question21:21
ttxThe idea behing it is to have a common rhythm21:21
ttxbut then if we can't handle the load this community management artifact generates...21:21
ttxwe could certainly get rid of it21:22
asalkeldeglynn to spread them you would have to release one every 2 to 3 days21:22
asalkeldlots of projects21:22
ttxIt's important for virtual/global communities to have the same rites and rhythms, it's what makes us one21:22
SlickNikAlso useful for things like dep freezes, and common freezes in general.21:22
ttxbut it's always a tradeoff21:22
eglynnyeah just probing as to how "embedded" the synchronized milestone concept is21:22
eglynn(... in the release management culture)21:22
ttxand if the drawbacks outweigh the benefits...21:23
ttxfrankly, it's only feature freeze which generates load issues21:23
ttxthe first two milestones are pretty calm21:23
asalkeldttx needs a holiday some time too21:23
*** VijayB_ has quit IRC21:23
*** markmcclain1 has quit IRC21:23
ttxWe could stagger FF, but I'm not sure that would cure the load21:23
eglynnyeah, maybe better to mitigate that FF rush by more strictly enforcing the FPF21:24
*** VijayB has joined #openstack-meeting21:24
ttxthat would certainly increase load on release management :)21:24
ttxeglynn: ++21:24
*** dkranz has quit IRC21:24
ttxanyway, let's move on21:24
ttx#topic Design Summit scheduling21:24
*** openstack changes topic to "Design Summit scheduling (Meeting topic: project)"21:24
eglynncool enough, looks like on balance it best to keep21:24
ttxAt this point we only have Keystone schedule up on kilodesignsummit.sched.org21:24
devanandaironic schedule is basically done, i jus thaven't had time to post it yet21:25
mikalttx: what's the deadline for that?21:25
mikalttx: nova is basically done too21:25
asalkeldwe are going through Heat's tomorrow this time21:25
ttxThe deadline for pushing a near-final agenda is Tuesday next week (Oct 28)21:25
ttxSo you should abuse your weekly meetings this week to come up with a set of sessions21:25
*** jmontemayor has quit IRC21:25
*** emagana has quit IRC21:25
*** terryw has joined #openstack-meeting21:25
nikhil_kwe've a virtual/online mini-summit for glance, summit session finalizing would be done in there as well (Thurs 23/Fri 24)21:26
morganfainbergi need to check on the Ops summit details one of keystone's sessions might change.21:26
*** emagana has joined #openstack-meeting21:26
ttxAs far as the release management track goes, we don't have a specific meeting, so I'll discuss it here and now21:26
ttxwe only have 2 sessions, and only two themes proposed21:26
mesteryttx: Neutron is almost done, we'll finalize tomorrow.21:26
ttxSo we'll likely have one session on stable branch maintenance, and one on vulnerability management21:26
ttxNo session on release schedule, since we decided that already on-list21:26
ttx(I know, we lose a traditional design summit slot)21:26
*** hashar has quit IRC21:27
ttxEverything else will get covered at the Infra/QA/RelMgt meetup on Friday.21:27
ttxI'll push the agenda for that tomorow probably21:27
*** ttrifonov is now known as zz_ttrifonov21:27
ttxQuestions on the scheduling ?21:27
david-lyleany idea about per service operator session requests?21:28
ttxmorganfainberg: any issue wrangling the scheduling website ?21:28
morganfainbergttx, i've had no issues21:28
morganfainbergit's "just worked" for the most part21:28
*** yamamoto has joined #openstack-meeting21:28
ttxdavid-lyle: they are definitely a good thing to have. Avoid overlap with Ops Summit session to maximize attendance21:28
david-lyleI have not seen any requests, Horizon found it valuable last time, so just schedule and hope they come?21:28
*** otherwiseguy has quit IRC21:28
*** VijayB has quit IRC21:29
ttxdavid-lyle: yes. Amybe brag about that session at the Ops Summit on Monday ?21:29
ttxthere is a "Ops Summit: How to get involved in Kilo " session that sounds appropriate21:30
asalkeldwhen / how will the cross project session be descided21:30
*** berendt has quit IRC21:30
eglynnby the TC I think21:30
*** emagana has quit IRC21:30
ttxasalkeld: TC members are voting on the etherpad this week, feel free to add your opinion there as well21:31
ttxthen Russellb and MarkMCClain were mandated to build the final schedule21:31
asalkeldyeah, i have added some things there21:31
dhellmann#link https://etherpad.openstack.org/p/kilo-crossproject-summit-topics21:31
ttxshall be all set when we meet again next week21:31
ttxanything else on that topic ?21:32
*** sarob has quit IRC21:32
asalkeldall good21:32
ttx#topic Global Requirements, a practical case21:32
*** openstack changes topic to "Global Requirements, a practical case (Meeting topic: project)"21:32
ttxAt a previous meeting we had a discussion on global-requirements, and agreed that it was for integrated projects requirements and integrated-project-wanabee solving checken-and-egg issues21:32
ttxBut dims raised the following review: https://review.openstack.org/#/c/128746/21:32
ttxSounds like a good practical example of a corner case21:32
ttxnova-docker driver was split out to stackforge but still wants to do nova-like testing to be able to merge back21:33
*** yamamoto has quit IRC21:33
dimshere's a long writeup - https://etherpad.openstack.org/p/managing-reqs-for-projects-to-be-integrated21:33
ttxIs that a valid requirements update case or not ?21:33
mikalSo...21:33
dhellmannisn't the idea that they would sync on their own, not gate on requirements, and then seek to add any new requirements to the global list when they are re-integrated?21:34
mikalironic has the same problem right?21:34
dimsessentially we need a way to allow requirements jobs and dsvm jobs to work21:34
mikalOr is python-ironicclient in global reqs?21:34
asalkeldseems to me that docker is super important to openstack21:34
devanandamikal: ?21:34
dhellmanndims: no, I think you want to turn off the requirements gating for your repo21:34
dimsdhellmann: dsvm jobs?21:34
dhellmanndims: do those fail, too?21:34
dimsdhellmann: yep21:34
dhellmanndims: what's the failure condition? can't install something?21:34
mikaldevananda: I'm trying to work out why this didn't come up for ironic21:34
*** esker has quit IRC21:34
*** emagana has joined #openstack-meeting21:34
dimsdhellmann: requirements/update.py just exits21:35
*** jmontemayor has joined #openstack-meeting21:35
devanandamikal: I'm not sure what the problem is (poorly tracing this meeting, sorry)21:35
dhellmanndims: does solum run dsvm jobs?21:35
*** alexpilotti has quit IRC21:35
dhellmanndevananda: non-integrated project with extra requirements21:35
asalkeldsolum had this issue - solution: remove the project from project.txt21:36
devanandaironic has chosen not to list our 3rd party libs in requirements21:36
dhellmannasalkeld: does that fix the dsvm issue?21:36
devanandawhich leaves it up to operators/installers to pull those packages separately from requirements.txt21:36
asalkelddhellmann, it then uses upstream pypi21:36
devanandaand within each driver's __init__, it checks and gracefully fails if its lib isn't present21:36
asalkeldnot the openstack restricted one21:36
mikaldevananda: yeah, this is what drivers in nova do too21:37
dhellmannasalkeld: our ci mirror is fulll, so I think you're actually using the local mirror now21:37
dhellmanndevananda: yeah, we do something like that in oslo.messaging, too21:37
devanandaso far it has been fine for us21:37
* dims notes that docker-py is an essential not optional dependency21:37
asalkelddhellmann, yeah - the logic could have changed21:37
devanandadims: essential for that driver. not for the whole project. right?21:37
dimsdevananda: right21:37
mikaldims: so is python-ironicclient if you want a working ironic in nova though21:37
dhellmanndims: that's fine, if you uncouple your project from the global requirements list fully it ought to work21:37
devanandadims: so it fals in the same category21:38
devanandadims: that makes it not a requirement, since what driver you use is a deploy-time option21:38
*** shohel02 has quit IRC21:38
devanandait's an external dependency of that particular configuration21:38
asalkelddevananda, well if docker-py was in requirements the heat could maybe put the container resource from contrib into heat proper21:38
dimsdhellmann: unforunately the tempest-dsvm jobs fail21:38
dimsdevananda: not asking nova's requirement to have docker-py21:38
*** alexpilotti has joined #openstack-meeting21:38
dimsdevananda: asking global requirements to have docker-py21:39
dimswhich is different21:39
devanandadims: ahh ok21:39
asalkeldin this particular case i am suprised we dont' just add it21:39
dhellmanndims: ok, that's disconcerting, they shouldn't care about the requirements now. Do you have a log?21:39
devanandadims: i have no objection to projects that want to depend on docker syncing which version of docker-py they depend on21:39
dimsdhellmann: there's a customer http client which is not good in nova-docker trying to use a well thoughtout library21:39
devanandathat's the function of global req's -- syncing version deps21:39
dhellmannasalkeld: we could, but this is supposed to be working already, I think, and we will have other cases where that's not the right solution21:39
devanandaI don't see a reason to reject a submission to global req's when projects want to use that to sync the version dep. but maybe I'm missing something?21:40
asalkeldsure21:40
dimsdhellmann: there was an aborted attempt in february to switch to docker-py documented in the url above21:40
*** zz_ttrifonov is now known as ttrifonov21:40
*** chris_ has joined #openstack-meeting21:40
dhellmanndevananda: I may be misrepresenting sdague, but AIUI, he also wants that list to be an actual list of dependencies for openstack21:41
dhellmannof course that may change under a big-tent model21:41
*** alexpilotti has quit IRC21:41
*** Murali_ has quit IRC21:41
dimsdhellmann: i've also documented a proposal to avoid adding to g-r using a flag sdague introduced21:41
dimsin update.py21:41
dhellmannok21:42
dims43-49 lines21:42
dhellmannI'm a little lost because some of those comments seem unrelated and I'm only just now seeing this issue.21:42
dimsapologies21:43
dhellmannwhere should I start reading to catch up? is there a ML thread, or bug or something?21:43
*** alexpilotti has joined #openstack-meeting21:43
*** rudrarugge has joined #openstack-meeting21:43
*** ttrifonov is now known as zz_ttrifonov21:43
dimsdhellmann: https://etherpad.openstack.org/p/managing-reqs-for-projects-to-be-integrated21:43
asalkeldcan we go off line on this?21:43
* dims nods21:44
*** henrynash has quit IRC21:44
dhellmannyeah, I think the issue there is the dsvm jobs should not be failing on extra requirements, but let's talk about it on the ML21:44
dimsdhellmann: ack, will get the ball rolling21:44
ttxok, so the take here is that they shouldn't need the global-requirements update ?21:44
mtreinishdhellmann: I think it should only fail if the project is tracked in g-r21:45
mtreinishat least that was my understanding21:45
asalkeldyes21:45
*** VijayB has joined #openstack-meeting21:45
dhellmannmtreinish: yeah, so it may be a configuration issue then21:45
dimsmy only "requirement" is project be allowed to move forward till it gradutes :)21:45
dhellmannfor the job21:45
* dhellmann snorts at dims' pun21:46
dims:)21:46
ttx#topic Open discussion21:46
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:46
ttxAnything else, anyone ?21:46
asalkeldttx do we have nice big white board in paris?21:46
asalkeldfor the dev sessions21:47
notmynameo/21:47
asalkeldand esp. the friday session21:47
eglynnyeah good point21:47
ekarlsoa/j openstack-meeting-321:47
* eglynn hates little flip charts21:47
notmynamettx: I'm not particularly happy with how http://lists.openstack.org/pipermail/openstack/2014-October/010059.html was handled. who do I talk to about it?21:47
ttxasalkeld: the whiteboards are not "big" but there are several of them21:49
asalkeldok thanks ttx21:49
asalkeldthat's something21:49
ttxeglynn: the Flip charts double as whiteboards21:49
ttxnotmyname: reading21:49
* nikhil_k find Glance in the email topic21:49
ttxnotmyname: that would be the OSSG group. They are having a pTL election this week21:50
notmynamettx: probably not enough time to read/digest in this meeting. but I'd like to address it21:50
ttxnotmyname: so whovever wins shall get a nice email from you21:50
*** jmontemayor has quit IRC21:50
dhellmannnotmyname: was the swift team not involved or something? what's the background?21:50
ttxyou can cc me. I don't technically oversee that grouyp though21:50
funginotmyname: alternatively you can follow up on the openstack-security ml21:51
funginotmyname: i gather the people who drafted and approved that text all gather there21:51
notmynameok, the -security ML seems like a good starting place (rather than a response to the general ML for now)21:51
*** andreykurilin_ has quit IRC21:51
notmynamedhellmann: only a little. and mostly I don't think the right issue was addressed21:52
* dhellmann nods21:52
ttxanything else before we close ?21:53
notmynamethat, and that a resolution of "just use ceph instead of swift" was given as official openstack recommendation is annoying21:53
* ttx reads again21:53
*** amcrn has joined #openstack-meeting21:54
dhellmannthat was one of several options, right? and it seemed like the most heavy-weight21:54
ttxThat was indeed tactful21:54
ttxdhellmann: "Implementing an alternative back end (such as Ceph) will also remove the issue" feels a bit loaded21:54
dhellmannyeah21:54
ttxnotmyname: yes, openstack-security sounds like the right avenue to discuss that21:55
notmynameespecially since I think the issue is simply the different definition of "public" between glance and swift. not a security issue21:55
*** gholler has quit IRC21:55
*** MaxV has quit IRC21:55
notmynamethanks. I'll follow uo on the -security ML21:56
ttxok then, let's close this21:56
ttx#endmeeting21:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:56
openstackMeeting ended Tue Oct 21 21:56:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-21-21.02.html21:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-21-21.02.txt21:56
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-10-21-21.02.log.html21:56
ttxThanks everyone!21:56
*** mspreitz has joined #openstack-meeting21:58
*** chris_ has quit IRC21:58
*** terryw has quit IRC21:58
*** mmedvede has quit IRC21:59
*** cdub has quit IRC21:59
*** spzala has quit IRC21:59
*** SlickNik has left #openstack-meeting21:59
*** padkrish has quit IRC21:59
*** mchalla_ has joined #openstack-meeting22:00
*** mchalla has quit IRC22:00
*** rudrarugge has quit IRC22:01
*** jungleboyj has joined #openstack-meeting22:04
*** thangp has quit IRC22:05
*** khaldrogox has joined #openstack-meeting22:05
*** gokrokve has quit IRC22:05
*** shohel02 has joined #openstack-meeting22:09
*** novas0x2a|laptop has quit IRC22:09
*** kebray has quit IRC22:10
*** cody-somerville has quit IRC22:10
*** Mandell has quit IRC22:10
*** shohel02 has quit IRC22:11
*** shohel02_ has joined #openstack-meeting22:11
*** pradk has quit IRC22:11
*** novas0x2a|laptop has joined #openstack-meeting22:11
*** jecarey has quit IRC22:11
*** bknudson has quit IRC22:12
*** eglynn has quit IRC22:13
*** jckasper has joined #openstack-meeting22:13
*** david-lyle has quit IRC22:13
*** dboik has quit IRC22:14
*** jckasper has quit IRC22:14
*** jckasper has joined #openstack-meeting22:14
*** cody-somerville has joined #openstack-meeting22:14
*** david-lyle has joined #openstack-meeting22:15
*** atiwari has quit IRC22:16
*** shohel02_ has quit IRC22:16
*** kebray has joined #openstack-meeting22:17
*** s3wong has quit IRC22:18
*** asalkeld has quit IRC22:18
*** erlon has quit IRC22:19
*** noslzzp has quit IRC22:19
*** emagana has quit IRC22:19
*** emagana has joined #openstack-meeting22:20
*** moha_hunt has quit IRC22:21
*** AlanClark has quit IRC22:21
*** nati_uen_ has quit IRC22:22
*** mspreitz has quit IRC22:22
*** Mandell has joined #openstack-meeting22:23
*** mmedvede has joined #openstack-meeting22:24
*** Riddhi has joined #openstack-meeting22:24
*** eharney has quit IRC22:24
*** emagana has quit IRC22:25
*** adahms has joined #openstack-meeting22:25
*** nati_ueno has joined #openstack-meeting22:25
*** s3wong has joined #openstack-meeting22:25
*** yamamoto has joined #openstack-meeting22:28
*** f13of13o has quit IRC22:30
*** asalkeld has joined #openstack-meeting22:31
*** yamamoto has quit IRC22:32
*** ptoohill_ has quit IRC22:34
*** dims_ has joined #openstack-meeting22:35
*** dims_ has quit IRC22:36
*** dims_ has joined #openstack-meeting22:36
*** chris- has joined #openstack-meeting22:37
*** dims has quit IRC22:38
*** markwash__ has quit IRC22:39
*** Mandell has quit IRC22:39
*** neelashah has quit IRC22:39
*** kebray has quit IRC22:40
*** nelsnelson has quit IRC22:44
*** hemna has quit IRC22:44
*** mattgriffin has quit IRC22:45
*** thedodd has quit IRC22:46
*** ddieterly has quit IRC22:47
*** khaldrogox has quit IRC22:47
*** chris- has quit IRC22:48
*** gokrokve has joined #openstack-meeting22:48
*** chris_ has joined #openstack-meeting22:48
*** VijayB has quit IRC22:49
*** jgrimm is now known as zz_jgrimm22:49
*** marun has quit IRC22:50
*** chris_ has quit IRC22:50
*** doblerone has joined #openstack-meeting22:50
*** markwash__ has joined #openstack-meeting22:51
*** Guest90847 has quit IRC22:52
*** alexpilotti has quit IRC22:52
*** carl_baldwin has quit IRC22:53
*** doblerone has quit IRC22:53
*** doblerone has joined #openstack-meeting22:53
*** VijayB_ has joined #openstack-meeting22:55
*** mmedvede has quit IRC22:56
*** padkrish has joined #openstack-meeting22:58
*** padkrish has quit IRC22:58
*** padkrish has joined #openstack-meeting22:59
*** dsetia has joined #openstack-meeting22:59
*** emagana has joined #openstack-meeting22:59
*** Mandell has joined #openstack-meeting23:01
*** baoli has quit IRC23:01
*** dane_leblanc has quit IRC23:03
*** derekh has joined #openstack-meeting23:05
*** joesavak has quit IRC23:05
*** MaxV has joined #openstack-meeting23:06
*** rbak has quit IRC23:07
*** MarkAtwood has quit IRC23:08
*** huats_ has quit IRC23:09
*** noslzzp has joined #openstack-meeting23:09
*** MaxV has quit IRC23:10
*** dsetia has quit IRC23:10
*** dsetia has joined #openstack-meeting23:11
*** shohel02 has joined #openstack-meeting23:11
*** huats_ has joined #openstack-meeting23:12
*** huats_ has quit IRC23:12
*** huats_ has joined #openstack-meeting23:12
*** noslzzp has quit IRC23:14
*** padkrish has quit IRC23:15
*** shohel02 has quit IRC23:16
*** yamahata has joined #openstack-meeting23:16
*** marun has joined #openstack-meeting23:19
*** erlon has joined #openstack-meeting23:20
*** comay has quit IRC23:20
*** padkrish has joined #openstack-meeting23:21
*** sarob has joined #openstack-meeting23:23
*** js1123 has quit IRC23:26
*** nsaje has quit IRC23:28
*** yamamoto has joined #openstack-meeting23:28
*** david-lyle has quit IRC23:30
*** bdpayne_ has joined #openstack-meeting23:31
*** ihrachyshka has quit IRC23:32
*** bdpayne has quit IRC23:33
*** yamamoto has quit IRC23:33
*** mmedvede has joined #openstack-meeting23:36
*** VijayB_ has quit IRC23:41
*** zz_jgrimm is now known as jgrimm23:46
*** enikanorov has quit IRC23:50
*** dboik has joined #openstack-meeting23:53
*** jamielennox has joined #openstack-meeting23:53
*** sarob has quit IRC23:53
*** IanGovett has quit IRC23:54
*** doblerfarious has joined #openstack-meeting23:54
*** doblerfarious has quit IRC23:57
*** rmoe has quit IRC23:58
*** doblerone has quit IRC23:58

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