Tuesday, 2016-03-01

*** rbak has quit IRC00:00
*** haomaiwang has quit IRC00:01
*** thorst has quit IRC00:01
*** haomaiwang has joined #openstack-meeting00:01
*** zz_dimtruck is now known as dimtruck00:08
*** akuznetsov has joined #openstack-meeting00:11
*** cloudtrainme has quit IRC00:12
*** sdake has quit IRC00:14
*** dmacpher-afk has quit IRC00:16
*** akuznetsov has quit IRC00:16
*** Sukhdev has quit IRC00:22
*** merooney has joined #openstack-meeting00:25
*** trozet has quit IRC00:26
*** Leom_ has quit IRC00:32
*** mspreitz has joined #openstack-meeting00:32
*** ricolin has joined #openstack-meeting00:33
*** boris-42 has quit IRC00:34
*** evgenyf has quit IRC00:34
*** Keedya_ has joined #openstack-meeting00:35
*** Keedya_ has quit IRC00:36
*** markvoelker has quit IRC00:38
*** Sukhdev has joined #openstack-meeting00:38
*** hoangcx has joined #openstack-meeting00:42
*** toddjohn_ has quit IRC00:44
*** baoli has joined #openstack-meeting00:52
*** Sukhdev has quit IRC00:52
*** baoli has quit IRC00:58
*** zhurong has joined #openstack-meeting00:59
*** ajmiller has quit IRC00:59
*** arif-ali has joined #openstack-meeting01:00
*** thorst_ has quit IRC01:00
*** haomaiwang has quit IRC01:01
*** amotoki has joined #openstack-meeting01:01
*** thorst has joined #openstack-meeting01:01
*** haomaiwang has joined #openstack-meeting01:01
*** asselin__ has joined #openstack-meeting01:01
*** garthb has quit IRC01:03
*** dmacpher has joined #openstack-meeting01:03
*** asselin__ has quit IRC01:06
*** apoorvad has quit IRC01:06
*** aeng has quit IRC01:06
*** lblanchard has joined #openstack-meeting01:07
*** pvaneck has quit IRC01:07
*** penick has quit IRC01:08
*** sputnik13 has quit IRC01:09
*** thorst has quit IRC01:09
*** reedip has quit IRC01:10
*** manuel112 has joined #openstack-meeting01:11
*** banix has quit IRC01:11
*** emagana has quit IRC01:12
*** zzxwill has joined #openstack-meeting01:13
*** jorge_munoz has quit IRC01:14
*** merooney has quit IRC01:15
*** manuel112 has quit IRC01:16
*** azbiswas has quit IRC01:16
*** azbiswas has joined #openstack-meeting01:17
*** apoorvad has joined #openstack-meeting01:17
*** emagana has joined #openstack-meeting01:17
*** sigmavirus24 is now known as sigmavirus24_awa01:17
*** emagana has quit IRC01:18
*** merooney has joined #openstack-meeting01:20
*** pfallenop has quit IRC01:20
*** angdraug has quit IRC01:20
*** azbiswas has quit IRC01:21
*** yamamoto_ has quit IRC01:23
*** Daisy has joined #openstack-meeting01:23
*** aeng has joined #openstack-meeting01:23
*** haomaiwang has quit IRC01:26
*** yamamoto has joined #openstack-meeting01:26
*** emagana has joined #openstack-meeting01:26
*** ryu25 has joined #openstack-meeting01:27
*** Daisy has quit IRC01:27
*** ^Gal^ has quit IRC01:27
*** emagana has quit IRC01:31
*** ^Gal^ has joined #openstack-meeting01:32
*** sheel has joined #openstack-meeting01:36
*** markvoelker has joined #openstack-meeting01:38
*** bobh has joined #openstack-meeting01:39
*** trozet has joined #openstack-meeting01:41
*** donghao has joined #openstack-meeting01:43
*** apoorvad has quit IRC01:44
*** toddjohn_ has joined #openstack-meeting01:44
*** ninag has joined #openstack-meeting01:45
*** thorst has joined #openstack-meeting01:45
*** yamamoto has quit IRC01:45
*** baohua has joined #openstack-meeting01:46
*** Keedya_ has joined #openstack-meeting01:46
*** toddjohn_ has quit IRC01:49
*** watanabe_isao has joined #openstack-meeting01:50
*** ninag has quit IRC01:50
*** tfukushima has joined #openstack-meeting01:51
*** sarob has quit IRC01:51
*** arvinc_ has joined #openstack-meeting01:52
*** Pengfei has joined #openstack-meeting01:52
*** andreykurilin__ has quit IRC01:53
*** thorst has quit IRC01:53
*** Pengfei has quit IRC01:53
*** singhj has quit IRC01:54
*** Pengfei has joined #openstack-meeting01:54
*** Pengfei has quit IRC01:54
*** singhj has joined #openstack-meeting01:54
*** tfukushima has quit IRC01:54
*** Pengfei has joined #openstack-meeting01:54
*** mtanino has quit IRC01:55
*** yfujioka has joined #openstack-meeting01:55
*** yamamoto has joined #openstack-meeting01:57
*** yamamoto has quit IRC01:58
*** sarob has joined #openstack-meeting01:58
*** doug-fish has quit IRC01:58
*** donghao has quit IRC02:00
*** novas0x2a|laptop has quit IRC02:01
*** vishwanathj_ has joined #openstack-meeting02:02
*** aeng has quit IRC02:02
*** irenab_ has joined #openstack-meeting02:03
*** sarob has quit IRC02:04
*** irenab has quit IRC02:04
*** irenab_ is now known as irenab02:04
*** dims has quit IRC02:04
*** reed_ has quit IRC02:05
*** haomaiwa_ has joined #openstack-meeting02:07
*** trozet has quit IRC02:08
*** markvoelker has quit IRC02:08
*** merooney has quit IRC02:08
*** markvoelker has joined #openstack-meeting02:08
*** Sukhdev has joined #openstack-meeting02:08
*** dims has joined #openstack-meeting02:08
*** baojg has joined #openstack-meeting02:08
*** azbiswas has joined #openstack-meeting02:08
*** baoli has joined #openstack-meeting02:11
*** dims has quit IRC02:13
*** Sukhdev has quit IRC02:14
*** Pengfei_ has joined #openstack-meeting02:14
*** Pengfei has quit IRC02:16
*** akuznetsov has joined #openstack-meeting02:17
*** dims has joined #openstack-meeting02:17
*** baoli has quit IRC02:18
*** baoli has joined #openstack-meeting02:18
*** aeng has joined #openstack-meeting02:18
*** hemna_ has joined #openstack-meeting02:19
*** tfukushima has joined #openstack-meeting02:19
*** zhurong has quit IRC02:20
*** zhurong has joined #openstack-meeting02:21
*** akuznetsov has quit IRC02:21
*** bobh has quit IRC02:22
*** baoli has quit IRC02:22
*** tfukushima has quit IRC02:22
*** jmckind has quit IRC02:23
*** baoli has joined #openstack-meeting02:23
*** tfukushima has joined #openstack-meeting02:24
*** baojg has quit IRC02:24
*** tfukushima has quit IRC02:26
*** baojg has joined #openstack-meeting02:26
*** baojg has quit IRC02:26
*** fawadkhaliq has quit IRC02:27
*** Keedya_ has quit IRC02:28
*** Pengfei has joined #openstack-meeting02:28
*** singhj has quit IRC02:29
*** ninag has joined #openstack-meeting02:31
*** Pengfei_ has quit IRC02:32
*** blogan has quit IRC02:32
*** ptoohill has quit IRC02:32
*** Keedya_ has joined #openstack-meeting02:33
*** andymaier has quit IRC02:34
*** baojg has joined #openstack-meeting02:34
*** azbiswas has quit IRC02:35
*** armax has quit IRC02:35
*** tfukushima has joined #openstack-meeting02:35
*** azbiswas has joined #openstack-meeting02:35
*** s3wong has quit IRC02:36
*** gcb has joined #openstack-meeting02:36
*** azbiswas has quit IRC02:40
*** nisha has joined #openstack-meeting02:41
*** dixiaoli has quit IRC02:41
*** Pengfei has quit IRC02:41
*** yamamoto has joined #openstack-meeting02:42
*** epico has joined #openstack-meeting02:42
*** Pengfei has joined #openstack-meeting02:42
*** ijw has quit IRC02:43
*** ninag has quit IRC02:44
*** Keedya_ has quit IRC02:45
*** Keedya_ has joined #openstack-meeting02:46
*** Keedya_ has quit IRC02:51
*** thorst has joined #openstack-meeting02:51
*** tochi has quit IRC02:55
*** tochi has joined #openstack-meeting02:55
*** hemna_ has quit IRC02:57
*** thorst has quit IRC02:58
*** baoli has quit IRC03:00
*** haomaiwa_ has quit IRC03:01
*** rockyg has joined #openstack-meeting03:01
*** haomaiwang has joined #openstack-meeting03:01
*** donghao has joined #openstack-meeting03:01
*** dimtruck is now known as zz_dimtruck03:01
*** rockyg has quit IRC03:05
*** donghao has quit IRC03:06
*** ajmiller has joined #openstack-meeting03:08
*** zz_dimtruck is now known as dimtruck03:12
*** manuel112 has joined #openstack-meeting03:13
*** Keedya_ has joined #openstack-meeting03:15
*** Keedya_ has quit IRC03:17
*** Pengfei has quit IRC03:17
*** Pengfei has joined #openstack-meeting03:18
*** dims has quit IRC03:19
*** donghao has joined #openstack-meeting03:19
*** baojg has quit IRC03:19
*** jorge_munoz has joined #openstack-meeting03:21
*** baojg has joined #openstack-meeting03:21
*** jorge_munoz has quit IRC03:22
*** xinwu has quit IRC03:23
*** Keedya_ has joined #openstack-meeting03:23
*** baoli has joined #openstack-meeting03:25
*** jckasper has joined #openstack-meeting03:25
*** Keedya_ has quit IRC03:27
*** jckasper has quit IRC03:28
*** jckasper has joined #openstack-meeting03:28
*** Pengfei has quit IRC03:29
*** ninag has joined #openstack-meeting03:29
*** kencjohnston has joined #openstack-meeting03:29
*** Pengfei has joined #openstack-meeting03:30
*** Nakato has quit IRC03:31
*** rossella_s has quit IRC03:32
*** ninag has quit IRC03:33
*** rossella_s has joined #openstack-meeting03:33
*** jckasper has quit IRC03:33
*** ninag has joined #openstack-meeting03:33
*** Pengfei has quit IRC03:35
*** tochi has quit IRC03:35
*** zzxwill has quit IRC03:36
*** ninag has quit IRC03:37
*** lblanchard has quit IRC03:38
*** sarob has joined #openstack-meeting03:38
*** nisha_ has joined #openstack-meeting03:39
*** jckasper has joined #openstack-meeting03:40
*** prashantD has quit IRC03:40
*** sarob has quit IRC03:42
*** nisha has quit IRC03:43
*** donghao has quit IRC03:44
*** zzxwill has joined #openstack-meeting03:44
*** harshs has quit IRC03:45
*** Nakato has joined #openstack-meeting03:45
*** watanabe_isao has quit IRC03:46
*** watanabe_isao has joined #openstack-meeting03:46
*** manuel112 has quit IRC03:47
*** JRobinson__ is now known as JRobinson__afk03:48
*** baoli has quit IRC03:49
*** links has joined #openstack-meeting03:49
*** kebray has quit IRC03:49
*** xinwu has joined #openstack-meeting03:51
*** neelashah has joined #openstack-meeting03:51
*** zhiyuan has joined #openstack-meeting03:51
*** leeantho has joined #openstack-meeting03:52
*** bbzhao has quit IRC03:54
*** rhagarty_ has joined #openstack-meeting03:55
*** thorst has joined #openstack-meeting03:56
*** rhagarty has quit IRC03:58
*** tochi has joined #openstack-meeting04:00
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-meeting04:01
*** rhagarty_ has quit IRC04:02
*** zzxwill has quit IRC04:03
*** kencjohnston has quit IRC04:03
*** _amrith_ is now known as amrith04:03
*** thorst has quit IRC04:03
*** donghao has joined #openstack-meeting04:04
*** vishwanathj_ has quit IRC04:04
*** scinawa has quit IRC04:06
*** emagana has joined #openstack-meeting04:08
*** ivar-laz_ has joined #openstack-meeting04:09
*** tellesnobrega is now known as tellesnobrega_af04:12
*** ivar-lazzaro has quit IRC04:13
*** ivar-laz_ has quit IRC04:14
*** zzxwill has joined #openstack-meeting04:14
*** nisha_ has quit IRC04:14
*** armax has joined #openstack-meeting04:15
*** yamahata has joined #openstack-meeting04:16
*** fawadkhaliq has joined #openstack-meeting04:18
*** haomaiwang has quit IRC04:21
*** dimtruck is now known as zz_dimtruck04:22
*** JRobinson__afk is now known as JRobinson__04:23
*** sverma has joined #openstack-meeting04:24
*** haomaiwang has joined #openstack-meeting04:26
*** sheel has quit IRC04:27
*** donghao has quit IRC04:29
*** azbiswas has joined #openstack-meeting04:31
*** zzxwill has quit IRC04:32
*** baigk has quit IRC04:35
*** zzxwill has joined #openstack-meeting04:37
*** neelashah has quit IRC04:37
*** kei_ has quit IRC04:40
*** manuel112 has joined #openstack-meeting04:44
*** leeantho has quit IRC04:45
*** amrith is now known as _amrith_04:46
*** bbzhao has joined #openstack-meeting04:51
*** edtubill has joined #openstack-meeting04:54
*** jmckind has joined #openstack-meeting04:56
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** Pengfei has joined #openstack-meeting05:01
*** thorst has joined #openstack-meeting05:01
*** Pengfei has joined #openstack-meeting05:02
*** RuiChen has quit IRC05:02
*** nisha has joined #openstack-meeting05:02
*** RuiChen has joined #openstack-meeting05:03
*** edtubill has quit IRC05:06
*** edtubill has joined #openstack-meeting05:07
*** thorst has quit IRC05:08
*** jckasper has quit IRC05:13
*** jckasper has joined #openstack-meeting05:14
*** comay has quit IRC05:15
*** ajmiller has quit IRC05:16
*** manuel112 has quit IRC05:17
*** jckasper has quit IRC05:18
*** blogan_ has joined #openstack-meeting05:18
*** mspreitz has quit IRC05:18
*** salv-orl_ has joined #openstack-meeting05:19
*** nkrinner has joined #openstack-meeting05:19
*** ptoohill has joined #openstack-meeting05:20
*** zzxwill has quit IRC05:20
*** salv-orlando has quit IRC05:22
*** numans has joined #openstack-meeting05:23
*** dmacpher has quit IRC05:24
*** baojg has quit IRC05:25
*** comay has joined #openstack-meeting05:26
*** edtubill has quit IRC05:28
*** donghao has joined #openstack-meeting05:29
*** jmckind has quit IRC05:33
*** epico has quit IRC05:33
*** donghao has quit IRC05:35
*** baojg has joined #openstack-meeting05:37
*** jogo has quit IRC05:38
*** evgenyf has joined #openstack-meeting05:39
*** hdaniel has joined #openstack-meeting05:40
*** oomichi_ has joined #openstack-meeting05:40
*** oomichi_ has quit IRC05:40
*** jogo has joined #openstack-meeting05:41
*** sudipto has joined #openstack-meeting05:42
*** fawadkhaliq has quit IRC05:42
*** zzxwill has joined #openstack-meeting05:44
*** Pengfei has quit IRC05:44
*** haomaiwang has quit IRC05:45
*** sridharg has joined #openstack-meeting05:45
*** haomaiwang has joined #openstack-meeting05:45
*** epico has joined #openstack-meeting05:45
*** dixiaoli has joined #openstack-meeting05:49
*** esker has quit IRC05:49
*** irenab has quit IRC05:50
*** esker has joined #openstack-meeting05:50
*** emagana has quit IRC05:52
*** evgenyf has quit IRC05:54
*** Sukhdev has joined #openstack-meeting05:55
*** fawadkhaliq has joined #openstack-meeting05:58
*** adiantum has joined #openstack-meeting05:58
*** ricolin has quit IRC06:01
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-meeting06:01
*** dmacpher has joined #openstack-meeting06:01
*** Daisy_ has joined #openstack-meeting06:02
*** sheel has joined #openstack-meeting06:02
*** Daisy_ has quit IRC06:03
*** thorst has joined #openstack-meeting06:06
*** Kiall has quit IRC06:06
*** dmacpher_ has joined #openstack-meeting06:08
*** Kiall has joined #openstack-meeting06:08
*** rcernin has joined #openstack-meeting06:09
*** dmacpher has quit IRC06:10
*** sdake has joined #openstack-meeting06:11
*** thorst has quit IRC06:13
*** manuel112 has joined #openstack-meeting06:14
*** nisha_ has joined #openstack-meeting06:15
*** dmacpher_ has quit IRC06:16
*** ricolin has joined #openstack-meeting06:18
*** baojg has quit IRC06:18
*** nisha has quit IRC06:19
*** donghao has joined #openstack-meeting06:21
*** dmacpher_ has joined #openstack-meeting06:23
*** baojg has joined #openstack-meeting06:23
*** e0ne has joined #openstack-meeting06:23
*** donghao has quit IRC06:24
*** hoangcx has quit IRC06:24
*** Pengfei has joined #openstack-meeting06:24
*** Pengfei_ has joined #openstack-meeting06:25
*** hdaniel has quit IRC06:27
*** sdake has quit IRC06:27
*** Pengfei has quit IRC06:28
*** e0ne has quit IRC06:31
*** zzxwill_ has joined #openstack-meeting06:33
*** sdake has joined #openstack-meeting06:33
*** e0ne has joined #openstack-meeting06:33
*** e0ne has quit IRC06:34
*** dmellado has quit IRC06:34
*** whenry_ has quit IRC06:34
*** bdperkin has quit IRC06:35
*** adahms has joined #openstack-meeting06:35
*** dmellado has joined #openstack-meeting06:39
*** irenab has joined #openstack-meeting06:39
*** roxanaghe has quit IRC06:39
*** bdperkin has joined #openstack-meeting06:40
*** bdperkin has quit IRC06:40
*** bdperkin has joined #openstack-meeting06:40
*** akuznetsov has joined #openstack-meeting06:45
*** Sukhdev has quit IRC06:45
*** comay has quit IRC06:46
*** manuel112 has quit IRC06:47
*** akuznetsov has quit IRC06:49
*** toddjohn_ has joined #openstack-meeting06:50
*** iyamahat has joined #openstack-meeting06:51
*** azbiswas has quit IRC06:52
*** azbiswas has joined #openstack-meeting06:53
*** azbiswas has quit IRC06:53
*** azbiswas has joined #openstack-meeting06:53
*** maishsk has joined #openstack-meeting06:53
*** toddjohn_ has quit IRC06:54
*** Daisy has joined #openstack-meeting06:56
*** sverma_ has joined #openstack-meeting06:56
*** dmacpher_ has quit IRC06:56
*** Pengfei_ has quit IRC06:57
*** Pengfei has joined #openstack-meeting06:58
*** sverma has quit IRC06:58
*** Daisy has quit IRC06:58
*** achanda has quit IRC06:58
*** tfukushima has quit IRC07:00
yamamotohi07:00
*** tfukushima has joined #openstack-meeting07:00
*** haomaiwang has quit IRC07:01
yamamoto#startmeeting networking_midonet07:01
openstackMeeting started Tue Mar  1 07:01:19 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto. Information about MeetBot at http://wiki.debian.org/MeetBot.07:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:01
*** openstack changes topic to " (Meeting topic: networking_midonet)"07:01
openstackThe meeting name has been set to 'networking_midonet'07:01
*** haomaiwang has joined #openstack-meeting07:01
yamamoto#topic Agenda07:01
*** openstack changes topic to "Agenda (Meeting topic: networking_midonet)"07:01
yamamoto#link https://wiki.openstack.org/wiki/Meetings/NetworkingMidoNet07:01
*** nisha_ has quit IRC07:01
yamamoto#topic Announcements07:01
*** openstack changes topic to "Announcements (Meeting topic: networking_midonet)"07:01
yamamotoi have no announcements07:02
yamamoto#topic Bugs07:02
*** openstack changes topic to "Bugs (Meeting topic: networking_midonet)"07:02
yamamotobug deputy for the last week was ryu07:02
yamamotoryu25: ping07:03
*** maishsk has quit IRC07:03
*** dmacpher has joined #openstack-meeting07:04
*** sverma_ has quit IRC07:04
yamamoto#topic Open Discussion07:04
*** openstack changes topic to "Open Discussion (Meeting topic: networking_midonet)"07:04
*** zzxwill has left #openstack-meeting07:04
*** scheuran has joined #openstack-meeting07:05
yamamotoit seems i'm alone.07:05
*** sverma has joined #openstack-meeting07:05
yamamotoi'll take bug deputy for this week.07:05
*** jprovazn has joined #openstack-meeting07:05
yamamotobye!07:06
yamamoto#endmeeting07:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:06
openstackMeeting ended Tue Mar  1 07:06:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-03-01-07.01.html07:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-03-01-07.01.txt07:06
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-03-01-07.01.log.html07:06
*** Daisy_ has joined #openstack-meeting07:06
*** sdake has quit IRC07:10
*** thorst has joined #openstack-meeting07:11
*** Daisy_ has quit IRC07:11
*** hoangcx has joined #openstack-meeting07:11
*** sdake has joined #openstack-meeting07:12
*** paul-carlton2 has joined #openstack-meeting07:15
*** achanda has joined #openstack-meeting07:15
*** Pengfei_ has joined #openstack-meeting07:16
*** Pengfei has quit IRC07:17
*** thorst has quit IRC07:18
*** zzxwill has joined #openstack-meeting07:20
*** dmorita has joined #openstack-meeting07:20
*** dmacpher has quit IRC07:20
*** manuel112 has joined #openstack-meeting07:21
*** donghao has joined #openstack-meeting07:24
*** hoangcx has quit IRC07:26
*** mrmartin has joined #openstack-meeting07:27
*** donghao has quit IRC07:29
*** _matthias_ has joined #openstack-meeting07:32
*** bnemec has quit IRC07:36
*** bnemec has joined #openstack-meeting07:39
*** roxanaghe has joined #openstack-meeting07:39
*** neeti has joined #openstack-meeting07:43
*** roxanaghe has quit IRC07:44
*** sdake has quit IRC07:48
*** esker has quit IRC07:50
*** jtomasek has joined #openstack-meeting07:50
*** maishsk has joined #openstack-meeting07:52
*** esker has joined #openstack-meeting07:54
*** ryu25 has quit IRC07:58
*** ryu25 has joined #openstack-meeting07:59
*** haomaiwang has quit IRC07:59
*** haomaiwang has joined #openstack-meeting07:59
*** xingchao has joined #openstack-meeting08:00
*** haomaiwang has quit IRC08:01
*** belmoreira has joined #openstack-meeting08:01
*** haomaiwang has joined #openstack-meeting08:01
anteaya#startmeeting third-party08:01
openstackMeeting started Tue Mar  1 08:01:39 2016 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: third-party)"08:01
openstackThe meeting name has been set to 'third_party'08:01
anteayahello08:01
*** zzxwill has left #openstack-meeting08:01
lennybhi08:01
anteayasorry I missed last week, that was my fault08:02
*** achanda_ has joined #openstack-meeting08:02
anteayaI was traveling and my schedule was off08:02
anteayasorry about that08:02
anteayahow are you today lennyb?08:02
lennyblooks like noone was here anyway08:02
anteayawell you were here08:02
anteayasorry about that, lennyb08:02
lennybI am fine, thank you. How are you ?08:02
anteayagood thanks08:03
anteayaglad to be home08:03
anteayahave you anything you would like to discuss today?08:03
lennyblooks like it's just 2 of us, and I have nothing interesting to ask or tell...So feel free t o..08:04
*** dmorita has quit IRC08:04
*** emagana has joined #openstack-meeting08:04
anteaya:)08:04
anteayathanks lennyb08:04
*** achanda has quit IRC08:04
*** ricolin has quit IRC08:04
*** achanda_ has quit IRC08:04
anteayaI'll keep the meeting open for a bit08:04
*** slagle has quit IRC08:06
*** achanda has joined #openstack-meeting08:08
*** fawadkhaliq has quit IRC08:08
*** armax has quit IRC08:08
*** emagana has quit IRC08:09
*** pcaruana has joined #openstack-meeting08:09
*** jichen has joined #openstack-meeting08:11
*** yamahata has quit IRC08:11
*** iyamahat has quit IRC08:11
lennyb'see' you next week, anteaya08:13
*** dmorita has joined #openstack-meeting08:14
*** dmorita_ has joined #openstack-meeting08:15
*** dmorita_ has quit IRC08:15
*** dmorita has quit IRC08:15
anteayalennyb: see you08:16
anteayathanks lennyb08:16
anteayaguess I'll close up for now08:16
*** Pengfei has joined #openstack-meeting08:16
anteayahave a lovely day08:16
*** dmorita has joined #openstack-meeting08:16
*** Pengfei_ has quit IRC08:16
anteayaand thanks for being here08:16
*** thorst has joined #openstack-meeting08:16
anteaya#endmeeting08:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:16
openstackMeeting ended Tue Mar  1 08:16:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-01-08.01.html08:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-01-08.01.txt08:16
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-01-08.01.log.html08:16
*** amotoki has quit IRC08:18
*** amotoki has joined #openstack-meeting08:19
*** hdaniel has joined #openstack-meeting08:19
*** andymaier has joined #openstack-meeting08:19
*** sshnaidm has quit IRC08:22
*** takashi has joined #openstack-meeting08:22
*** ricolin has joined #openstack-meeting08:22
*** thorst has quit IRC08:23
*** xingchao has quit IRC08:23
*** dixiaoli_ has joined #openstack-meeting08:24
*** hichihara has quit IRC08:24
*** xingchao has joined #openstack-meeting08:24
*** takashi has quit IRC08:26
*** achanda has quit IRC08:27
*** yfujioka has quit IRC08:28
*** dmorita has quit IRC08:30
*** ociuhandu has quit IRC08:31
*** jlanoux has joined #openstack-meeting08:32
*** jschwarz has joined #openstack-meeting08:32
*** watanabe_isao has quit IRC08:34
*** sridharg has quit IRC08:38
*** _nadya_ has joined #openstack-meeting08:39
*** JRobinson__ has quit IRC08:40
*** roxanaghe has joined #openstack-meeting08:41
*** donghao has joined #openstack-meeting08:41
*** JRobinson__ has joined #openstack-meeting08:41
*** ndipanov has joined #openstack-meeting08:44
*** matrohon has joined #openstack-meeting08:45
*** xinwu has quit IRC08:45
*** donghao has quit IRC08:45
*** roxanaghe has quit IRC08:46
*** salv-orl_ has quit IRC08:47
*** salv-orlando has joined #openstack-meeting08:48
*** sridharg has joined #openstack-meeting08:49
*** novas0x2a|laptop has joined #openstack-meeting08:50
*** zeih has joined #openstack-meeting08:51
*** xingchao_ has joined #openstack-meeting08:53
*** sridharg has quit IRC08:53
*** xingchao has quit IRC08:53
*** sridharg has joined #openstack-meeting08:53
*** slavisa has joined #openstack-meeting08:57
*** xingchao_ has quit IRC08:57
*** xingchao has joined #openstack-meeting08:58
*** novas0x2a|laptop has quit IRC08:59
*** paul-carlton2 has quit IRC09:00
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-meeting09:01
*** andymaier has quit IRC09:01
*** baojg has quit IRC09:03
*** mbound has joined #openstack-meeting09:06
*** dmorita has joined #openstack-meeting09:07
*** ildikov has quit IRC09:08
*** adiantum1 has joined #openstack-meeting09:08
*** adiantum has quit IRC09:09
*** adiantum1 is now known as adiantum09:09
*** dmorita has quit IRC09:09
*** dmorita has joined #openstack-meeting09:10
*** xingchao has quit IRC09:10
*** salv-orlando has quit IRC09:11
*** toscalix has joined #openstack-meeting09:11
*** ndipanov has quit IRC09:11
*** xingchao has joined #openstack-meeting09:12
*** Pengfei has quit IRC09:12
*** xingchao has quit IRC09:12
*** ihrachys has joined #openstack-meeting09:13
*** phil has joined #openstack-meeting09:13
*** zhiyuan has quit IRC09:13
*** xingchao has joined #openstack-meeting09:13
*** phil is now known as Guest7756309:13
*** hashar has joined #openstack-meeting09:13
*** amotoki has quit IRC09:14
*** neiljerram has joined #openstack-meeting09:14
*** scheuran has quit IRC09:15
*** jckasper has joined #openstack-meeting09:15
*** xingchao has quit IRC09:16
*** adiantum has quit IRC09:17
*** andymaier has joined #openstack-meeting09:18
*** xingchao has joined #openstack-meeting09:18
*** sshnaidm has joined #openstack-meeting09:19
*** amotoki has joined #openstack-meeting09:19
*** baojg has joined #openstack-meeting09:19
*** jckasper has quit IRC09:20
*** ygbo has joined #openstack-meeting09:21
*** takashi has joined #openstack-meeting09:21
*** thorst has joined #openstack-meeting09:22
*** xingchao has quit IRC09:23
*** shaohe_feng has quit IRC09:23
*** shh_away has quit IRC09:25
*** shaohe_feng has joined #openstack-meeting09:25
*** scheuran has joined #openstack-meeting09:27
*** paul-carlton2 has joined #openstack-meeting09:28
*** e0ne has joined #openstack-meeting09:28
*** thorst has quit IRC09:28
*** keedya has quit IRC09:29
*** baohua has quit IRC09:31
*** yassine__ has joined #openstack-meeting09:32
*** ildikov has joined #openstack-meeting09:35
*** ociuhandu has joined #openstack-meeting09:35
*** vishwanathj_ has joined #openstack-meeting09:38
*** evgenyf has joined #openstack-meeting09:38
*** e0ne has quit IRC09:38
*** azbiswas has quit IRC09:38
*** derekh has joined #openstack-meeting09:39
*** hoangcx has joined #openstack-meeting09:40
*** slavisa has quit IRC09:40
*** slavisa has joined #openstack-meeting09:40
*** roxanaghe has joined #openstack-meeting09:42
*** ryu25 has quit IRC09:44
*** roxanaghe has quit IRC09:46
*** xingchao has joined #openstack-meeting09:46
*** zhurong has quit IRC09:47
*** hdaniel has quit IRC09:47
*** aarefiev has quit IRC09:48
*** aarefiev has joined #openstack-meeting09:49
*** ebagdasa has quit IRC09:50
*** ociuhandu has quit IRC09:59
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-meeting10:01
*** Pengfei has joined #openstack-meeting10:01
*** Pengfei_ has joined #openstack-meeting10:03
*** Pengfei has quit IRC10:06
*** akamyshnikova has joined #openstack-meeting10:06
*** e0ne has joined #openstack-meeting10:11
*** ricolin has quit IRC10:11
*** xingchao has quit IRC10:13
*** fzdarsky has joined #openstack-meeting10:14
*** adiantum has joined #openstack-meeting10:19
*** arvinc_ has quit IRC10:20
*** andymaier has quit IRC10:25
*** sambetts|afk is now known as sambetts10:26
*** ildikov has quit IRC10:26
*** JRobinson__ has quit IRC10:26
*** thorst has joined #openstack-meeting10:26
*** tfukushima has quit IRC10:27
*** dixiaoli_ has quit IRC10:28
*** ndipanov has joined #openstack-meeting10:29
*** Pengfei_ has quit IRC10:30
*** Pengfei has joined #openstack-meeting10:31
*** slavisa has quit IRC10:32
*** thorst has quit IRC10:33
-openstackstatus- NOTICE: Gerrit is going to be restarted due to poor performance10:36
*** ChanServ changes topic to "Gerrit is going to be restarted due to poor performance"10:36
*** azbiswas has joined #openstack-meeting10:39
*** ildikov has joined #openstack-meeting10:40
*** baojg has quit IRC10:41
*** baojg has joined #openstack-meeting10:41
*** epico has quit IRC10:42
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:42
-openstackstatus- NOTICE: gerrit finished restartign10:42
*** roxanaghe has joined #openstack-meeting10:42
*** azbiswas has quit IRC10:46
*** roxanaghe has quit IRC10:47
*** ihrachys has quit IRC10:48
*** yfujioka has joined #openstack-meeting10:55
*** pfallenop has joined #openstack-meeting10:56
*** akamyshnikova has quit IRC10:58
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-meeting11:01
*** baohua has joined #openstack-meeting11:01
*** pfallenop has quit IRC11:03
*** dims has joined #openstack-meeting11:03
*** emagana has joined #openstack-meeting11:04
*** hoangcx has quit IRC11:06
*** amotoki has quit IRC11:06
*** baojg has quit IRC11:07
*** manuel112 has quit IRC11:07
*** leunam112 has joined #openstack-meeting11:07
*** tellesnobrega_af is now known as tellesnobrega11:08
*** emagana has quit IRC11:09
*** dingboopt has joined #openstack-meeting11:14
*** yamamoto has quit IRC11:15
*** akamyshnikova has joined #openstack-meeting11:16
*** pfallenop has joined #openstack-meeting11:16
*** scinawa has joined #openstack-meeting11:23
*** takashi has quit IRC11:25
*** claudiub has joined #openstack-meeting11:25
*** scinawa has quit IRC11:27
*** rodrigods has quit IRC11:29
*** rodrigods has joined #openstack-meeting11:29
*** jlanoux_ has joined #openstack-meeting11:30
*** jlanoux has quit IRC11:30
*** thorst has joined #openstack-meeting11:31
*** zzxwill_ has joined #openstack-meeting11:32
*** rossella_s has quit IRC11:32
*** rossella_s has joined #openstack-meeting11:33
*** takashi has joined #openstack-meeting11:33
*** zzxwill_ has quit IRC11:34
*** tochi has quit IRC11:34
*** zzxwill has joined #openstack-meeting11:34
*** sudipto has quit IRC11:36
*** ildikov has quit IRC11:36
*** _amrith_ is now known as amrith11:38
*** thorst has quit IRC11:38
*** aysyd has joined #openstack-meeting11:39
*** ihrachys has joined #openstack-meeting11:39
*** esker has quit IRC11:40
*** ociuhandu has joined #openstack-meeting11:40
*** esker has joined #openstack-meeting11:40
*** salv-orlando has joined #openstack-meeting11:41
*** vishwanathj_ has quit IRC11:44
*** aysyd has quit IRC11:46
*** aysyd has joined #openstack-meeting11:46
*** jlanoux_ has quit IRC11:50
*** sdague has joined #openstack-meeting11:51
*** jlanoux has joined #openstack-meeting11:51
*** sarob has joined #openstack-meeting11:55
*** salv-orlando has quit IRC11:58
*** amotoki has joined #openstack-meeting11:58
*** gmann_ has joined #openstack-meeting11:59
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Mar  1 12:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho is here today?12:00
gmann_hi12:00
*** sarob has quit IRC12:00
sdagueo/12:00
*** haomaiwang has quit IRC12:01
alex_xutoday is quite12:01
alex_xu#topic API futures - patches for approved specs12:01
*** openstack changes topic to "API futures - patches for approved specs (Meeting topic: nova api)"12:01
*** haomaiwang has joined #openstack-meeting12:01
jicheno/12:01
alex_xuwe finish the goal we merge the LM patches \o/12:01
alex_xulast week12:02
*** yamamoto has joined #openstack-meeting12:02
alex_xuanything people want to bring up today?12:02
*** markus_z has joined #openstack-meeting12:02
alex_xusdague: we will freeze the client in Thursday also?12:03
sdaguealex_xu: yes, I think so, so probably we should get people to prioritize looking at the microversion lands in the clients12:03
sdagueso that we can actually have users have these features on the command line12:04
alex_xuyea, those LM API client patch didn't merge yet12:04
alex_xu#link https://review.openstack.org/28133512:05
alex_xuthere is the first one12:05
alex_xu#link https://review.openstack.org/#/c/260383/12:05
alex_xuthere is the last one12:05
alex_xuthen we won't have any more api patch landing in Mitaka12:06
sdagueright, I'm pretty sure we're done on API patches for Mitaka12:06
*** mhickey has joined #openstack-meeting12:06
alex_xusdague: https://review.openstack.org/281143 I changed this to the way you like, but I think it isn't hurry, it still can be merged after freeze12:07
*** rfolco_ has joined #openstack-meeting12:07
eliqiaoo/12:07
alex_xuI guess no more question, then let's move on12:07
Kevin_ZhengSorry to be late, internet connection very bad today in our office12:07
*** amotoki has quit IRC12:07
sdaguealex_xu: right, that patch looks good12:08
sdaguealex_xu: thanks for handling that12:08
gmann_sdague: how about https://review.openstack.org/#/c/248662/12:08
alex_xusdague: np12:08
gmann_sdague: as we are deprecating hook but still we should fix this issue?12:08
sdaguegmann_: let's come back to that in open discussion12:08
gmann_sdague: or not so critical12:08
gmann_sdague: sure12:08
alex_xu#topic Nova Microversion testing in Tempest12:09
*** openstack changes topic to "Nova Microversion testing in Tempest (Meeting topic: nova api)"12:09
alex_xugmann_: sdague your turn12:09
sdagueI believe we landed the change that gmann_ posted for that12:09
gmann_sdague: yea12:09
sdaguegmann_: where do we stand now?12:09
*** cdent has joined #openstack-meeting12:09
gmann_sdague: alex_xu i have posted other 2 patches to migrate to /lib and support microversion in all clients12:10
cdento/ sorry I'm late12:10
gmann_sdague: https://review.openstack.org/#/c/284387/ https://review.openstack.org/#/c/284414/12:10
gmann_sdague: after those we can implement any microversion tests12:10
gmann_sdague: if you can have look into those12:10
sdaguegmann_: sounds good12:11
gmann_sdague: do you link for v2.20 tests patch12:12
gmann_sdague: i can update that if you like12:12
sdaguegmann_: oh, right, that would be great12:12
*** phil_h has quit IRC12:13
alex_xusounds we are good at here, so let us move on?12:13
gmann_alex_xu: yea.12:14
alex_xu#topic open12:14
*** openstack changes topic to "open (Meeting topic: nova api)"12:14
alex_xu#link https://review.openstack.org/#/c/248662/12:14
alex_xugmann_: sdague ^ we can back to this12:14
sdagueright, so there is a mailing list thread about nova.hooks now12:15
*** rtheis has joined #openstack-meeting12:15
sdaguebasically, I think we should either be testing this or deprecate it12:15
sdagueif the deprecation patch lands, then I'm happy taking the fix without functional testing12:15
gmann_sdague: +1 for deprecate12:15
sdaguebecause spending a bunch of time functional testing a features we're going to remove in the near future is busy work12:15
gmann_humm, right12:16
alex_xuyes12:16
alex_xuit is a medium prority bug, so sounds ok, not critical for something12:17
alex_xuat least not critical for this point12:17
gmann_yea12:17
sdaguegmann_: I updated my review comment12:17
*** raildo-afk is now known as raildo12:18
gmann_sdague: i see. Thanks12:18
sdagueso there were a couple of other interesting API bits that cropped up12:19
sdaguehave people noticed the regression tests in tree?12:19
jichenyeah12:20
alex_xusdague: no, do you have link?12:20
sdaguehttps://github.com/openstack/nova/blob/10da208f02fee532171d1d9e4667d0b71c455b8a/nova/tests/functional/regressions/README.rst#L1312:20
sdagueI started building a little mini framework for building a functional test for a bug to verify behavior before a fix, and after12:20
sdagueit is most applicable to API bugs12:21
sdagueor, anythign you don't need actual libvirt for12:21
sdaguehttps://github.com/openstack/nova/blob/10da208f02fee532171d1d9e4667d0b71c455b8a/nova/tests/functional/regressions/test_bug_1522536.py12:21
gmann_sdague: oh, that's very nice12:21
sdagueanyway, I found it easier to think about some of the api bugs by actually building the reproduce in tree, then fixing the code for them12:22
alex_xusdague: is there clear rule which kind of bug need add that regssion test?12:22
gmann_sdague: it is written that, those can removed later if needed but should not we keep those as normal tests?12:22
sdaguegmann_: honestly, I figured we'd keep them unless they got in the way12:22
sdaguealex_xu: I think any bug is fine. We're not going to make this a requirement of any bug12:23
sdaguebut if you want to do that, it's a good way to go12:23
gmann_sdague: and keep moving those to functional tests if suitable?12:23
sdaguegmann_: I don't know, I think I'm fine if they are just in this directory12:23
gmann_ok12:23
*** irenab has quit IRC12:24
sdaguethis is not about covering every possible edge case, it's about covering issues that come up often enough that people bothered to report bugs on them12:24
gmann_sdague: those will run as functional tests gate job right12:24
sdaguegmann_: yes12:24
gmann_ok12:24
sdaguealex_xu: I'm actually surprised your patch is passing this - https://github.com/openstack/nova/blob/10da208f02fee532171d1d9e4667d0b71c455b8a/nova/tests/functional/regressions/test_bug_1541691.py12:25
sdaguewe should figure out what's happening there12:25
alex_xusdague: emm...that is interesting, I will take a look it12:25
sdaguewe should just look at the test run in detail after the meeting12:25
*** Pengfei has quit IRC12:26
alex_xusdague: ok, cool12:26
sdaguethe other thing of note is the case sensitivity issues on metadata12:26
*** takashi has quit IRC12:26
sdaguehttp://lists.openstack.org/pipermail/openstack-dev/2016-February/087404.html12:26
sdagueI think we've resolved that metadata keys are just going to be non case sensitive12:27
sdaguebecause of mysql12:27
sdaguebut that means some python code to deal with it12:27
cdentit is just keys that's the issue, not values?12:27
sdaguejust keys12:27
cdentthen yeah, that seems reasonable12:27
sdaguebecause of the way that lookups / deletes are processed12:27
sdaguethat has some api implications, and I guess the real question is should we be enforcing lower case in the jsonschema for these12:28
sdaguebecause the current behavior is all wonky12:29
sdaguealthough, I think, largely synthetic. They look like the kind of bugs a qa team finds when they are poking at the world. I haven't seen a bug that looks like an actual field issue yet.12:29
sdagueanyway, those were my API related things12:30
alex_xuyes, I didn't think any people depend on that also12:30
gmann_humm, yea12:30
*** andymaier has joined #openstack-meeting12:30
alex_xuit is ok for enforcing lower case in the jsonschema12:30
sdagueright, I don't know how much people might be setting upper case things today12:31
*** MaxPC has joined #openstack-meeting12:31
gmann_but will that be ok for DB support case sensitive keys?12:31
sdaguegmann_: it won't break there12:31
* gmann_ still need to read full mail12:31
gmann_sdague: but json schema will block upper case right12:32
sdagueoh, right, so the issue is if we are going to fully enforce at json schema, then we'll also probably need a data migration to force all the keys to lower in the db12:32
sdaguegmann_: right12:32
johnthetubaguyalex_xu: sdague: just to confirm on python-novaclient, we have to make the final release for Mitaka sometime before the end of Thursday, as I understand it12:32
sdagueI think something like that probably needs an ops email, just to figure out if anyone is using upper case12:32
sdaguejohnthetubaguy: yep12:32
alex_xujohnthetubaguy: thanks, got it12:32
gmann_sdague: yea12:32
johnthetubaguynot sure an Ops email helps though, isn't this an end user facing API?12:33
alex_xusdague: is it ok just using a python code to convert the data from the db, then needn't data migration?12:33
sdaguejohnthetubaguy: and I think any API team focus should be on landing microversions in the client to support these new LM features12:33
johnthetubaguysdague: +112:33
sdaguejohnthetubaguy: well, the first one is aggregate metadata12:33
sdaguethat's not user facing12:33
*** bobh has joined #openstack-meeting12:33
johnthetubaguyah, OK, true, I was thinking about server metadata12:33
sdagueserver metadata is also an issue12:33
*** amrith is now known as _amrith_12:34
sdagueand... I agree, that's more complicated12:34
johnthetubaguyI was thinking we should fix server metadata, and make the others match12:34
sdagueok, well aggregate metadata was the one we were working on first12:34
sdaguemostly because if we get push back on the fix once people deploy it, it's easier to unwind12:35
johnthetubaguyah, yeah, thats true12:35
*** Pengfei has joined #openstack-meeting12:35
johnthetubaguyany mess up there, is less impacting12:35
*** takashi has joined #openstack-meeting12:36
* eliqiao is still on line ?12:37
sdaguejohnthetubaguy: now that you are back up, the nova.hooks deprecation patch is updated12:37
sdagueI also looked through the thread, and am skeptical about the usefulness of taking this to the ops list, because I have no idea what we'd do with the feedback12:38
*** ildikov has joined #openstack-meeting12:38
sdagueas I don't think anyone has said that crytalizing the current interface is a good idea12:38
*** [1]evgenyf has joined #openstack-meeting12:39
*** lblanchard has joined #openstack-meeting12:39
*** baohua has quit IRC12:40
*** baohua has joined #openstack-meeting12:40
sdagueok, anything else today?12:40
sdaguewe seem to have stalled out12:40
eliqiaoyes12:40
eliqiaoI got one bug.12:40
sdagueeliqiao: ok, cool12:40
eliqiao#link https://bugs.launchpad.net/nova/+bug/153651312:40
openstackLaunchpad bug 1536513 in OpenStack Compute (nova) "os-getConsoleOutput fail with 500" [Medium,Confirmed] - Assigned to Eli Qiao (taget-9)12:40
eliqiaoThe thing is, we don't handler that exception in REST API layer.12:41
sdagueyeh, that seems like a thing we should fix12:41
eliqiaoAnd neither do compute api layer.12:41
sdaguealso, I think it should be a 404 not a 40012:41
sdaguebecause it's a console doesn't exist for that guest, right?12:41
alex_xuI think we should check more detail, ensure the virt driver raise a useful exception12:41
eliqiaosdague: not all drivers raise same exception for example  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L66712:42
eliqiaosdague: for others, they raise NovaException.12:42
sdagueeliqiao: ok, I would suggest making a standard exception for that12:42
*** evgenyf has quit IRC12:42
*** [1]evgenyf is now known as evgenyf12:42
sdagueand getting all the virt drivers use that12:42
cdentdrivers should cast to unified exception themselves and reraise yeah?12:42
sdaguemaybe a couple, depending on the failure modes12:42
alex_xusdague: sometime people just raise NovaException for unexpected error, and we should return 500 for unexpected error?12:43
sdaguecdent: right, some kind of detail that can be translated at the top layer12:43
sdaguealex_xu: I think that's probably ok in general12:43
eliqiaoyeah, I think we need to deep into driver case by case.12:43
sdagueas we see these issues, we should try to make them more defined behavior12:43
*** roxanaghe has joined #openstack-meeting12:44
*** azbiswas has joined #openstack-meeting12:44
eliqiaosdague: I am think that in compute api layer(or compute manager) catch exception then do a reraise?12:44
alex_xusdague: ok, just afriad that will hide some bug12:44
sdaguealex_xu: a 500 error is always a bug12:45
sdaguewe even tell people to report them all12:45
eliqiaohmm... yeah, we do have that information to remine them to report bug...12:45
alex_xusdague: so for RPC timeout, should we catch them?12:45
*** markus_z has left #openstack-meeting12:45
sdaguealex_xu: was that the root issue here? and RPC timeout?12:45
eliqiaobut somthime it's the driver itself's issue not of nova...12:45
sdaguethis is my first look at this bug12:45
alex_xusdague: maybe timeout just for huge load12:46
*** thorst has joined #openstack-meeting12:46
sdagueok, what do you believe the root issue is here?12:46
sdaguemaybe we can work backwards from there, because I think I've gotten myself turned around12:46
eliqiaosdague: alex_xu or other folks, can you help to leave some comments on that bug.12:47
alex_xusdague: ok12:47
*** vhoward has joined #openstack-meeting12:47
sdagueeliqiao: sure, yeh, lets just leave comments on the bug12:47
eliqiaosdague: thx.12:47
*** thorst_ has joined #openstack-meeting12:47
jichenhttps://github.com/openstack/api-wg/blob/master/guidelines/http.rst, API wg has some comments on the MessageQueueTimeout12:47
jichenseems in their guideline 500 is acceptable if timeout12:48
*** roxanaghe has quit IRC12:48
*** jaypipes has joined #openstack-meeting12:48
sdaguejichen: I think in some cases that's fine12:49
*** azbiswas has quit IRC12:49
jichensdague: ok12:49
jichenI got one issue if eli's is done12:49
sdague5xx is really supposed to mean "your servers are broken / breaking"12:49
jichenhttps://review.openstack.org/#/c/276144/12:49
sdaguehitting rpc timeouts seems to be in that camp12:49
jichenyeah12:49
alex_xusdague: yea, that is what i'm thinking, some exception raise because server broken12:50
sdaguejichen: what does neutron return in these cases?12:50
jichenmy question is whether we need microversion if change from 503 to 409 , our microversion document didn't mention it's aceeptable to do this without microversion12:51
eliqiaoalex_xu: does server mean nova?12:51
gmann_jichen: not needed in v2.1?12:51
eliqiaoalex_xu: what if lowlevel broken?12:51
alex_xueliqiao: yeah, or the component of nova12:51
*** macsz has joined #openstack-meeting12:51
*** thorst has quit IRC12:51
sdaguejichen: I think we ended up with not needed when downgrading a 500 error12:51
jichengmann_ : I changed v2.1 code12:51
jichensdague: you mean 5xx error?12:52
sdagueyes12:52
jichenok12:52
sdagueI can comment back on it12:52
*** amotoki has joined #openstack-meeting12:52
sdagueI was already +2 on it12:52
sdagueok, anything else?12:52
jichenI don't have chance to try neutron, will try and update it in the patch12:52
jichenalso, I will write a follow up to change the microversion doc12:52
johnthetubaguyI have a feeling we said no bump if its an existing error message, but yeah, removing a 500 seems like another case we shouldn't have to bump12:53
johnthetubaguywe wouldn't want to leave the 5xx error in the old API versions, thats the key bit12:53
cdentjohnthetubaguy++12:54
jichen+112:54
*** yanyanhu has joined #openstack-meeting12:54
gmann_i too +1 on not version bump for 500 fix, but we should update doc too12:54
*** baoli has joined #openstack-meeting12:54
*** toddjohn_ has joined #openstack-meeting12:55
jichenyeah12:55
alex_xu+112:55
eliqiao+112:55
*** salv-orlando has joined #openstack-meeting12:55
alex_xuI remember our devref said that12:55
*** haiwei has joined #openstack-meeting12:55
eliqiaoyeah, it's bug fixing, so no bump12:56
alex_xuok, anyway, no more from me12:56
johnthetubaguy" Fixing a bug so that a 400+ code is returned rather than a 500 does not require a microversion change."12:56
johnthetubaguyhttp://docs.openstack.org/developer/nova/api_microversion_dev.html12:56
alex_xujohnthetubaguy: cool, thanks12:56
sdagueok, anything else?12:57
alex_xunothing from me12:57
eliqiaonot from my side.12:57
alex_xu3...12:57
alex_xu2..12:57
*** andymaier has quit IRC12:57
alex_xu1.12:57
alex_xuthanks all!12:57
eliqiaobye12:57
alex_xu#endmeeting12:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:57
openstackMeeting ended Tue Mar  1 12:57:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-01-12.00.html12:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-01-12.00.txt12:57
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-01-12.00.log.html12:57
gmann_Thanks all12:57
jichenthanks !12:58
*** toddjohn_ has quit IRC12:59
*** gmann_ has quit IRC13:00
*** lixinhui has joined #openstack-meeting13:00
*** haomaiwang has quit IRC13:01
*** Pengfei has quit IRC13:01
*** haomaiwang has joined #openstack-meeting13:01
*** Pengfei has joined #openstack-meeting13:01
*** Qiming has joined #openstack-meeting13:02
*** dims has quit IRC13:02
Qiming#startmeeting senlin13:02
openstackMeeting started Tue Mar  1 13:02:25 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: senlin)"13:02
openstackThe meeting name has been set to 'senlin'13:02
Qimingsorry guys, a little bit late again13:02
yanyanhuhi13:02
zzxwillHello. It's fine.13:02
haiweihi13:03
Qimingwelcome, zzxwill13:03
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:03
Qimingplease review agenda and see if you have things to add13:03
Qiming#topic Austin summit planning13:03
*** openstack changes topic to "Austin summit planning (Meeting topic: senlin)"13:03
yanyanhuhi, Qiming, the etherpad link for summit is not added in agenda13:03
Qimingokay, pls help13:04
yanyanhujust can remeber the name13:04
yanyanhu...13:04
lixinhuihi13:04
Qimingnewton-senlin-sessions13:04
yanyanhutried several different ones, all failed...13:04
*** cdent has left #openstack-meeting13:04
Qiming#link https://etherpad.openstack.org/p/newton-senlin-sessions13:04
yanyanhuah, missed the last 's'13:04
Qimingfollowing previous convention on naming the etherpad13:05
*** ndipanov_ has joined #openstack-meeting13:05
Qimingas the summit is drawing near, we need to start brainstorm topics for discussion13:05
*** ndipanov has quit IRC13:06
Qimingthe above link is an etherpad for proposals13:06
*** lblanchard has quit IRC13:06
Qimingwe have a lot of things to discuss, especially those items from TODO.rst and FEATURES.rst13:07
yanyanhuyes13:07
*** links has quit IRC13:07
Qimingfor example, the node-create/delete actions handling could be a discussion topic13:07
*** sudipto has joined #openstack-meeting13:08
QimingI'm not sure we will figure that out by mitaka release13:08
haiweiso this time would be how long for senlin design summit?13:08
*** dims has joined #openstack-meeting13:08
QimingFishbow slots (Wed-Thu)13:08
QimingWorkroom slots (Tue-Thu)13:08
QimingContributors meetup (Fri)13:09
*** irenab has joined #openstack-meeting13:09
yanyanhujust as usual13:09
Qimingit is up to the team (you and me) to figure out how many sessions do we need13:09
Qimingif possible, I'm getting back to ttx after we have a rough estimation13:10
haiweiyes13:10
*** julim has joined #openstack-meeting13:10
Qimingin the past, for example, some projects have 2+12+213:10
*** yamamoto has quit IRC13:10
Qimingsome projects have 1+0+013:10
QimingSome projects have 12+0+213:11
*** yamamoto has joined #openstack-meeting13:11
Qimingjust focus on the topics you want to discuss13:11
*** yamamoto has quit IRC13:11
*** cloudtrainme has joined #openstack-meeting13:12
*** yamamoto has joined #openstack-meeting13:12
yanyanhujust added two topics13:12
Qiming#action Everyone please input your proposals by end of Thursday (Feb. 3)13:12
yanyanhuwill try to add more13:12
Qimingdoes that action item makes sense to everyone?13:12
yanyanhuI believe there will be many items we want to talk f2f :)13:13
yanyanhusure13:13
yanyanhutotally makes sense to me13:13
QimingOn Friday, we need to do a consolidation13:13
haiweiis it necessary to send a mail?13:13
*** jckasper has joined #openstack-meeting13:13
Qimingjust a side note13:13
yanyanhuok, so we have 2 days for input13:13
Qimingonce we have a schedule, we can send an email to the dev list13:14
*** pradk has joined #openstack-meeting13:14
Qimingthere will be someone collecting inputs from all projects and work out a summary like this: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads13:14
*** jckasper has quit IRC13:15
Qimingplease mark your session's type: fishbowl or working13:15
*** Aegil has quit IRC13:15
*** haomaiwang has quit IRC13:15
yanyanhuok13:15
*** sdake has joined #openstack-meeting13:16
*** bobh has quit IRC13:16
*** jckasper has joined #openstack-meeting13:16
Qiminglet's move on13:16
Qiming#topic Mitaka release schedule13:16
*** openstack changes topic to "Mitaka release schedule (Meeting topic: senlin)"13:16
Qiming#link http://releases.openstack.org/mitaka/schedule.html13:16
Qimingthis week is the m-3 milestone13:16
Qiming... time flies13:16
*** zeih has quit IRC13:17
Qimingit is a week for many things: feature freeze, requirements freeze, soft string freeze, final release of client libs13:17
*** haomaiwang has joined #openstack-meeting13:17
*** zeih has joined #openstack-meeting13:18
zzxwillAs for soft StringFreeze, does it affect our project?13:18
Qimingwe'll create a b3 tag this week13:18
Qimingthat one is just a few commands13:18
Qimingbut there are other things where helps are needed13:18
Qimingyes, zzxwill13:18
Qimingjust talked to Daisy today13:18
yanyanhuone thing that is still unclear is when should we rework our driver for sdk release 0.8.013:19
Qimingif we have a focal for i18n, they can help try put senlin translation into their agenda13:19
*** Daisy has joined #openstack-meeting13:19
QimingI'm seeing the translation to Japanese for senlin-dashboard is bumping back13:19
Qimingthat one is something I should have taken care of13:20
*** ninag has joined #openstack-meeting13:20
yanyanhuit will really cost some time to finish this job13:20
QimingI have pushed sdk team to cut a version13:20
zzxwillI am a translator for i18n, I wonder whether I can overtake the role. But I still have so many things to learn.13:20
*** andymaier has joined #openstack-meeting13:20
Qiminghowever, 0.8.0 is not ideal13:20
yanyanhuQiming, understand13:20
Qimingit still misses some patches13:20
*** jckasper has quit IRC13:20
yanyanhuoh, right, the path_arg patch is still hang there13:20
Qimingnot sure if we should push them to release a 0.8.113:20
*** sdake has quit IRC13:21
briancurtinQiming: if you have some that you want done i can easily do a 0.8.1 (path_arg is a part of a big refactoring, “path args” are going away)13:21
Qiminganother thing is the version bump at global requirements got blocked again and again, for no good reason13:21
*** sdake has joined #openstack-meeting13:21
Qiminghello, briancurtin, that would be REALLY REALLY helpful13:21
*** haomaiwang has quit IRC13:22
*** ninag has quit IRC13:22
*** ninag has joined #openstack-meeting13:22
Qimingthere is a workaround for that, briancurtin13:22
yanyanhuhi, briancurtin, I noticed Terry abandoned his patches about path_args, does that mean this problem has been resolved?13:22
briancurtinQiming: i don’t want to interrupt your meeting (my irc client just highlights on SDK) so if you want to send me some of the reviews you would need for a 0.8.113:22
Qimingwe only need a patch for neutron lb member I think13:22
Qimingyanyanhu, pls help work we brian and see if it makes sense13:23
briancurtinyanyanhu: no it’s very much still a problem, but i am refactoring the Resource class to eliminate it. the old ways were not enough13:23
Qimings/we/with13:23
yanyanhuunderstand13:23
Qimingthe good thing is SDK is really great, it helps us eliminate all dependencies to xxxclients13:23
briancurtinyanyanhu: it’s a pretty big change to the insides of the SDK, but the proxy interface so far is the same so the changes user experience should not be that much13:23
Qimingfinal release for senlinclient13:24
Qimingthat is very possible now13:24
yanyanhuI see. thank you so much, briancurtin.13:24
Qimingthanks to di xiaoli, we have all OSC plugin patches landed13:25
*** xingchao has joined #openstack-meeting13:25
Qimingnow you can do a 'openstack cluster list' for example13:25
*** dprince has joined #openstack-meeting13:25
Qimingas for string freeze, need to do an examination if there are things need fixes13:25
*** takashi has quit IRC13:26
Qimingstarting from m-3 release, we should be really careful about introducing new strings13:26
yanyanhucool13:26
Qimingmoving on13:26
Qiming#topic Mitaka work items review13:26
*** openstack changes topic to "Mitaka work items review (Meeting topic: senlin)"13:27
*** jschwarz has quit IRC13:27
Qiming#link https://etherpad.openstack.org/p/senlin-mitaka-workitems13:27
Qimingheat resource type support, it is done13:27
Qimingthanks for the great effort fro ethan13:27
*** jschwarz has joined #openstack-meeting13:27
yanyanhuso all resources are available now?13:27
Qimingyes, all resources we planned to expose via Heat resource types13:28
yanyanhugreat13:28
Qimingthat blueprint has been marked 'completed'13:28
yanyanhumay the next step is some example template13:28
yanyanhuok13:28
Qimingtesting side13:28
yanyanhus/may/maybe13:28
Qimingyep, I think ethan has already started some work13:29
Qimingthat could be our focus in coming weeks13:29
Qimingjust curious if something new to share, yanyanhu ?13:30
yanyanhufunctional test for cluster update is in progress now. Have done some preparation by reworking test driver.13:30
*** Pengfei has quit IRC13:30
yanyanhuyes, made some progress13:30
yanyanhuhope can propose the first patch tomorrow13:30
*** zeih has quit IRC13:30
yanyanhufor test of cluster update with flavor being changed13:30
Qimingokay, we may need to start some stress testing next week13:30
Qimingcool13:30
*** zeih has joined #openstack-meeting13:31
Qimingnext, health management13:31
yanyanhuactually, I just added stree test topic into etherpad13:31
Qimingxinhui has helped added db table and an initial version13:31
*** emagana has joined #openstack-meeting13:31
Qimingstill polishing it13:31
lixinhuiYes, Qiming13:31
yanyanhuI think we may need more discussion about it, from both developer and user point of view13:32
Qiminghopefully, we can get it stable by RC113:32
lixinhuiI will keep testing it and polish it13:32
*** yamamoto has quit IRC13:32
Qimingnot sure we can finish the LB based health detection13:32
lixinhuiyanyanhu, agree to you13:32
yanyanhuhealthmonitor supported has added for lb policy13:32
lixinhuiAlarm has been created successsfully based on status change13:33
yanyanhupatch is under review. It works in my env.13:33
lixinhuiyanyanhu, I will test it also13:33
yanyanhubut still need more tests13:33
Qimingomg, you all unbelievable13:33
*** slagle has joined #openstack-meeting13:33
yanyanhulixinhui, thanks :)13:33
lixinhuijust the bug is under resovling13:33
lixinhuiyanyanhu :) you work so quicly!13:34
Qimingsomehow, somewhere, we need to document this13:34
Qimingand we should warn users about the limitations of this naive solution13:34
*** cloudtrainme has quit IRC13:34
Qimingit is a starting point13:34
yanyanhulixinhui, my pleasure :)13:35
lixinhui:)13:35
yanyanhutry my best to clean the obstacle before you guys13:35
lixinhuiokay, Qiming13:35
Qimingmore advanced health monitoring is out of senlin's scope, we do provide some entry level support etc ...13:35
Qimingpolicy documentation, have to resume that thread next week13:35
Qimingthis week I'll focus on the jobs mandated by release schedule13:36
Qimingso far have documented deletion policy and scaling policy13:36
Qimingrevising the affinity is almost done, then I'll document it as well13:36
*** emagana has quit IRC13:36
Qimingwhen lb policy is finalized, we document it later13:36
lixinhuisuper start, yanyanhu13:36
lixinhuis/start/star13:37
Qimingprofile13:37
lixinhuiQiming is machine again13:37
lixinhui...13:37
Qimingmaybe should move disk update to TODO?13:37
*** ndipanov_ is now known as ndipanov13:37
*** dasm has joined #openstack-meeting13:37
yanyanhumaybe we should move the item of nova disk updating support back to TODO list13:38
Qimingcall me Machinagain13:38
*** takashi has joined #openstack-meeting13:38
yanyanhuyes, have the same feeling13:38
*** yamamoto has joined #openstack-meeting13:38
lixinhui:)13:38
Qimingyup, don't drop the ball at least13:38
QimingI'll keep the NODE_CREATE/DELETE item there, until I'm sure I cannot finish it13:38
*** aimeeU has joined #openstack-meeting13:39
yanyanhuok13:39
Qiminglock breaker, that one has been finished?13:39
*** yamamoto has quit IRC13:39
yanyanhuguess so13:39
Qimingyanyanhu, are you seeing the error logs again?13:39
yanyanhuthe db warning happened during engine starts has gone13:40
yanyanhunope13:40
*** haomaiwang has joined #openstack-meeting13:40
*** baoli has quit IRC13:40
yanyanhuahh, sorry, that's another problem13:40
*** haomaiwang has quit IRC13:40
yanyanhubut I really didn't see error logs again13:40
*** baoli has joined #openstack-meeting13:40
Qimingokay, killing that item13:41
*** haomaiwa_ has joined #openstack-meeting13:41
Qimingok13:41
Qimingadded a job for you13:41
*** toddjohn_ has joined #openstack-meeting13:41
Qimingyou are welcome, yanyanhu13:41
Qiminghaiwei, still there?13:41
yanyanhuthanks :)13:41
haiweiyes13:42
Qimingdo we have any progress on container support?13:42
*** takashi has quit IRC13:42
*** Pengfei has joined #openstack-meeting13:42
Qimingif we need more time to come up with a prototype, we can add a design summit session for this13:43
*** baoli has quit IRC13:43
Qimingit can be a fishbowl session13:43
haiweinot really, I was learning Magnum, and try to figure out a good solution for container cluster13:43
Qimingokay13:43
*** jtomasek_ has joined #openstack-meeting13:43
*** baoli has joined #openstack-meeting13:43
Qimingjust please keep the team posted when you have some ideas13:43
haiweicurrently there is not a clear image of container cluster for me13:44
*** neeti has quit IRC13:44
Qimingoh, missed some items13:44
Qiminghaiwei, that is something interesting13:44
yanyanhuhaiwei, any possible the bay can be built based on senlin cluster?13:44
haiweiok, I will try to update the spec file13:44
yanyanhu:)13:44
Qimingmy only big concern is that we still need to involve a global scheduler for placing containers13:45
Qimingother than that, bringing up container cluster over senlin is a piece of cake13:45
haiweiI think the problem we need to think about first is shall Senlin use Magnum or not for our container solution13:45
Qiminghaiwei, I would think from the other direction13:45
haiweiI think it depends on what kind of container service senlin will provide13:46
QimingI think Magnum should use senlin to create clusters13:46
Qimingthis topic has been brought up several times before13:46
yanyanhuhaiwei, I think magnum itself doesn't provide container management interfaces?13:46
*** cdelatte has joined #openstack-meeting13:46
haiweiI think it does, yanyanhu13:47
yanyanhuohh13:47
Qimingthe Magnum team was always saying no, because 'senlin is a stackforge project', 'senlin is not an official project' ... 'we don't want dependency to non-official services ...'13:47
haiweifrom magnum client, you can all create a container by 'magnum container-create'13:47
*** fwdit has joined #openstack-meeting13:47
yanyanhuso we can treat it as a container management service just as k8s or mesos?13:47
haiweibut we need a container cluster13:47
Qiminghaiwei, why I'm doing that?13:47
Qimingwhy don't we call docker api directly?13:48
*** claudiub|2 has joined #openstack-meeting13:48
Qimingany benefits users will get?13:48
haiweithat is a solution, but you need to handle the problems like scheduling, network and so on13:48
Qimingsuppose we are going down this path13:48
Qimingdoes magnum do scheduling?13:49
haiweiI am afraid senlin will have to do some jobs which has already done by other projects13:49
*** dkranz has joined #openstack-meeting13:49
*** yfujioka has quit IRC13:49
Qimingyes, senlin's scope is always limited13:49
*** baohua_ has joined #openstack-meeting13:49
haiweino, Magnum uses docker swarm things13:49
Qimingthen why we need magnum in the middle?13:49
haiweias I said, we should think about the use case first, what kind of container cluster senlin will provide13:50
*** akamyshnikova has quit IRC13:50
QimingI'm open to any use case13:50
*** sdake_ has joined #openstack-meeting13:50
*** baohua has quit IRC13:50
Qimingto any benefits we or the users can get by having senlin to invoke magnum13:50
*** Pengfei has quit IRC13:51
Qimingif I'm a user, I don't care there is a cluster at all13:51
*** claudiub has quit IRC13:51
Qimingthe thing I care is, I have a docker image, please help me deploy it to your cloud13:51
haiweiyes, we should make user feel by using Senlin they can manage container cluster better, or else, they will use Magnum or other things13:51
*** Pengfei has joined #openstack-meeting13:52
QimingI want the service capable of handling autoscaling, load-balancing, high-avaialbility etc. all those non-functional requirements13:52
Qiminghaiwei, I don't think so13:52
Qimingusers really don't care the name of your project13:53
lixinhuiagree to Qiming on this point13:53
*** yamamoto has joined #openstack-meeting13:53
*** annp has joined #openstack-meeting13:53
*** maishsk_ has joined #openstack-meeting13:53
*** maishsk has quit IRC13:53
*** maishsk_ is now known as maishsk13:53
*** jtomasek_ has quit IRC13:54
*** reedip__ has joined #openstack-meeting13:54
Qimingit is not the glue layer that matters to users13:54
*** sdake has quit IRC13:54
haiweiyes, I am not focusing on using which project, but on what kind of service13:54
Qimingit is the eventual user experience, service level you provide to users that matters13:54
*** banix has joined #openstack-meeting13:54
Qiminghow about a service that can deploy and manage container clusters, while capable of handling autoscaling, load-balancing, high-avaialbility13:55
*** akamyshnikova has joined #openstack-meeting13:55
haiweithat is great13:55
*** jlibosva has joined #openstack-meeting13:55
Qiminghow far are we from that goal?13:55
Qimingwhat are the specific feature gaps we need to fill?13:56
*** jckasper has joined #openstack-meeting13:56
*** mbound has quit IRC13:56
haiweiI can't give a clear answer now13:56
Qimingfor each feature missed, are there any existing OS-style service we can leverage so we can focus on the end goal?13:56
*** neelashah has joined #openstack-meeting13:57
Qimingthat is something we need to think about13:57
yanyanhuQiming, I think the problem is which layer we want to be located13:57
*** johnsom has joined #openstack-meeting13:57
Qimingthat is a good question13:57
lixinhuiyanyanhu13:57
yanyanhuwhether it's just a IaaS cluster management service13:57
yanyanhuor more13:57
lixinhuiI think that does not matter13:58
Qimingyanyanhu, to be honest, I don't care13:58
yanyanhuyes, but that will decide the interface you expose13:58
QimingI don't think any users care at all13:58
lixinhuiif senlin can provide XXXXX service for container13:58
yanyanhue.g. app/service-oriented13:58
*** wwriverrat has joined #openstack-meeting13:58
*** hdaniel has joined #openstack-meeting13:58
lixinhuithat will be good13:58
yanyanhuor just bare container management13:58
*** garyk has joined #openstack-meeting13:59
*** janzian has joined #openstack-meeting13:59
yanyanhuyes, but they are two different things13:59
Qimingbare container management is the corner stone13:59
*** adahms has quit IRC13:59
yanyanhuQiming, yes, I also think so13:59
Qimingthe upper layer interface is what users see13:59
Qimingas a service, you do all the labor13:59
yanyanhuright13:59
Qimingthat is why people call you a service13:59
*** hynekm has joined #openstack-meeting13:59
yanyanhuso we should be a service on PaaS layer14:00
Qimingdrawing a hard line between iaas and paas won't help solve the problem14:00
*** korzen has joined #openstack-meeting14:00
yanyanhuif we want to provide that kind of support14:00
Qimingsorry, time's up14:00
Qimingback to senlin channel pls14:00
yanyanhuok14:00
Qiming#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Mar  1 14:00:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-01-13.02.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-01-13.02.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-01-13.02.log.html14:00
zzxwillThanks.14:00
*** Sam-I-Am has joined #openstack-meeting14:00
*** mfranc213 has joined #openstack-meeting14:00
*** haomaiwa_ has quit IRC14:01
*** amuller has joined #openstack-meeting14:01
ihrachys#startmeeting networking14:01
*** haomaiwang has joined #openstack-meeting14:01
xgermano/14:01
openstackMeeting started Tue Mar  1 14:01:29 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
mesteryo/14:01
*** vikram_ has joined #openstack-meeting14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
amullerhiho14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
amotokio/14:01
annpHi14:01
openstackThe meeting name has been set to 'networking'14:01
ajoo/ :)14:01
johnsomo/14:01
scheurano/14:01
vikram_hi14:01
jschwarz\o/14:01
HenryGo/14:01
obondarevhi14:01
ihrachyshello my friends ;)14:01
haleybhi14:01
rossella_shi all14:01
dasmo/14:01
* amuller salutes supreme commander chair14:01
*** hichihara has joined #openstack-meeting14:02
ihrachyswe'll try to have it short today since everyone is deep into mitaka3 pieces ;)14:02
*** annegentle has joined #openstack-meeting14:02
Sam-I-Ammoo.14:02
salv-orlandoaloha14:02
hichiharahi14:02
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
* ajo unburies head from code14:02
*** rkukura has joined #openstack-meeting14:02
ihrachys#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
ihrachysok, first thing first, we are approaching Mitaka 3 cut-off day14:02
ihrachysif you wonder when it happens for neutron... it's some time this week14:03
mhickeyHello14:03
ihrachysno exact day known so far14:03
mesteryI just pushedt he patch14:03
mesteryOR am pushing14:03
*** takashi has joined #openstack-meeting14:03
mesterySo it happens today or tomorrow14:03
ihrachysour glorious PTL will make the final judgement14:03
mhickeymestery: hurry! :)14:03
mestery#link https://review.openstack.org/28660914:03
ihrachysright, it usually happens some time around Wed, and probably this time we'll stick to the tradition14:03
ajoplease wed ;)14:04
mesteryI see no reason we wouldn't ;)14:04
*** derekh is now known as ndipanov_14:04
ihrachysthough we may accommodate for a bit if there are patches in flight that may be better getting in before the cut-off14:04
*** ndipanov_ is now known as derekh14:04
garykhi14:04
reedip__so its Wednesday UTC ?14:04
ihrachysso long story short, you are short on time, so push harder if you want something in14:04
* Sam-I-Am chants mtu14:04
ihrachysanother thing to note is we not only release neutron server packages (neutron + *aas) but also the client14:05
ihrachysprobably this week14:05
*** mdorman has joined #openstack-meeting14:05
*** cdub has quit IRC14:05
*** rbowen has joined #openstack-meeting14:05
amotoki4.1.0 is preparing https://review.openstack.org/#/c/286585/14:05
ihrachysso if you have pieces in the client for features landed in server side, better hurry14:05
amotokijust waiting armando.14:05
ihrachysright. our glorious PTL will do the final call here too. :)14:06
amotokiperhaps 4.1.0 will be shipped soon and if needed we will release 4.2.0 too14:06
*** julen has joined #openstack-meeting14:06
amotokiarmax and mestery will take care of them :)14:06
ihrachysthat's fair. client patches are usually more safe-ish than server side14:06
mesteryamotoki: Some of the changes post 4.1.0 look like we may need to bump the version again, so yes, a 4.2.0 would be the one14:07
*** todin has joined #openstack-meeting14:07
ihrachysand the final announcement is...14:07
amotokiyeah. as far as i see, it is backward-compat.14:07
ihrachysas you all probably know, a lot of team members were gathering in Minnesota wilderness the previous week for a midcycle sprint14:07
*** amitgandhinz has joined #openstack-meeting14:07
*** takashi has quit IRC14:07
ihrachyswe have Armando report from the event on the ML:14:08
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087693.html14:08
ihrachysplease make yourself aware of that, and reply if you have questions14:08
ihrachysthanks everyone who got there and made progress14:08
*** baoli has quit IRC14:08
garykwhy was it not in europe? :)14:08
amotokiit seems very productive :)14:08
mesterygaryk: The mid-cycle?14:09
ihrachysgaryk: next time let's bug our PTL to get it somewhere in Europe ;)14:09
garykmestery: yes :)14:09
mesterygaryk: We were not even going to have a mid-cycle, but dougwig and armax decided at the last minute to go ahead with it14:09
mesterySo I scrambled to find a location on very short notice14:09
mesteryThat's why :)14:10
mhickeyihrachys: Lets see how Brno goes! :)14:10
ihrachysmestery: yeah, that's one bad thing about the latest midcycle: short notice :)14:10
*** baojg has joined #openstack-meeting14:10
mesteryYes14:10
dasmmestery: garyk: True. AFAIR, there was an email in mid-Dec or sth, that there will be no mid-cycle in this release14:10
ihrachysmhickey: Brno is limited in the scope and attendance, so it's not the same14:10
* mestery still thinks there should be no mid-cycles14:10
mhickeyRochester was very nice.14:10
mesterymhickey: It was!14:10
garyki agree with mestery14:10
amullermestery++14:10
Sam-I-Amit was nice to see everyone in person14:10
Sam-I-Amwe get to beat each other up in person14:11
ihrachysmestery: I bet then you take part in the thread on splitting the summit, don't you?14:11
*** berendt has joined #openstack-meeting14:11
mesteryihrachys: I'm too old to take part in that thread ;)14:11
mesteryBut yeah, split them up!14:11
garykyeah, it will be like the staidum, split them up and then get them back together and then split them up....14:11
mhickeyIt was good for me to meet people for the first time.14:11
xgermangrays +114:11
mesterylol14:12
xgermangaryk +114:12
reedip__garyk :+114:12
amullergaryk: it's "agile"14:12
salv-orlandosarcasm is great with garyk14:12
amuller"iterative"14:12
ihrachysgaryk: openstack: it's all about process14:12
garyk:)14:12
mesterygaryk: We have no idea what the next PTL will do, do we?14:12
*** baoli has joined #openstack-meeting14:12
xgermanhe might run on some stadium platform ;-14:12
garyki hope that she/he does the right thing14:12
salv-orlandoand indeed I'm sure mestery was very supportive of midcycles 2 years ago14:12
ihrachysmestery: unless we keep the one well known to us ;)14:12
* Sam-I-Am runs for PTL14:12
mesterysalv-orlando: I'm nothing if not a flip-flopper, that's for sure14:13
Sam-I-Ammestery: you should run for president14:13
garykgaryk: runs from the PTL....14:13
amullermestery: False, I've never once seen you wear flip flops14:13
salv-orlandomestery: nah it's just that since you had your 4th your wife has threathened you to not live home anymore14:13
salv-orlandoleave14:13
mesteryamuller: lol14:13
mesterysalv-orlando: ha!14:13
reedip__garyk : hehe...14:13
Sam-I-Amptl sounds like such a fun job lol14:13
mesteryamuller: Challenge accepted for Austin :)14:13
garyki think that it is cheaper to dye ones hair grey14:14
* ihrachys waits until people waste all their jokes for the week14:14
*** bobh has joined #openstack-meeting14:14
garyki think that we have digressed a little from the agenda14:14
*** lblanchard has joined #openstack-meeting14:14
ihrachysoh really? ok let's move on then ;)14:14
ihrachys#topic Bugs14:14
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:14
*** sbelous_ has joined #openstack-meeting14:15
Sam-I-Amwe never digress from anything14:15
*** ociuhandu has quit IRC14:15
xgerman+114:15
*** baoli has quit IRC14:15
Sam-I-Amits called agile meeting14:15
xgermanun conference14:15
ihrachyswe have two things here. one is dasm report for the prev week14:15
ihrachysdasm: anything mind blowing from the week you served?14:15
dasmihrachys: True. There was a very calm week.14:15
*** claudiub has joined #openstack-meeting14:15
dasmwe had just one big incident with api gate14:15
*** mbound has joined #openstack-meeting14:15
dasmwhere tempest_lib broke everything and glorious PTL(TM) fixed it14:16
ihrachysnow that's the Leader!14:16
dasmand second one, when by accident neutron-fwaas broke support for postgres14:16
*** ociuhandu has joined #openstack-meeting14:16
ihrachysdasm: ok I guess you tagged all bugs as per rules, and all went smooth14:16
dasmand, about this postgres thing. we lack gate for this, because it would be visible earlier14:16
dasmihrachys: i'm still buried under the pile of bugs :D14:17
dasmbut progressing14:17
ihrachysdasm: I think we had postgres jobs before, but they never got enough attention so were dissolved14:17
xgermanthey come and go14:17
xgermanI was for removing but...14:17
*** takashi has joined #openstack-meeting14:17
*** Daisy has quit IRC14:17
dasmmhm. in this case at least two different projects noticed problems with db. so, probably we should again think about it14:18
dasmjust my opinion14:18
*** claudiub|2 has quit IRC14:18
salv-orlandopostgres got "sacrificed" - I believe - to limit gate job sprawl14:18
ihrachysdasm: I guess as long as you drive the job and fix it quickly, no one would object more coverage14:18
*** berendt has quit IRC14:18
ihrachysif sprawl is the issue, periodic jobs are always there as a mid solution14:18
*** sdake_ is now known as sdake14:19
amulleras long as we don't have postgres-dvr, postgres-lb, postgres-*...14:19
ihrachysamuller: we should also add python34 to the matrix14:19
ihrachysand centos vs. ubuntu maybe14:19
ihrachysthat would be fun14:19
ihrachysok.14:19
HenryGthere is some patch out to restore a postgres job somewhere14:19
salv-orlandoihrachys: sure. The sacrified happened before people started moving jobs to the periodic queue. a postgres job is useful because there's always the odd failure due to the different default isolation level14:19
amotokiiirc there was an idea of a periodic job rather than gate jobs, but I don't know how it goes.14:20
salv-orlandoand why not batman vs superman?14:20
* salv-orlando disappears14:20
*** jmckind has joined #openstack-meeting14:20
ihrachysthe 2nd thing on bugs is... we don't have anyone as the bug deputy for the week, neither for the next one.14:20
HenryGPG is back in the check queue, non voting. https://review.openstack.org/28381214:20
ihrachysso if you feel like you want to please your glorious PTL and the team, it's time to make a step forward14:20
*** jmckind_ has joined #openstack-meeting14:21
ihrachysHenryG: oh cool! thanks for the link14:21
dasmHenryG: ++14:21
*** baojg has quit IRC14:21
*** edtubill has joined #openstack-meeting14:21
*** ociuhandu has quit IRC14:21
ihrachysanyone for the bug deputy thing?14:22
*** ajmiller has joined #openstack-meeting14:22
dasmplease, take it... it's fun!14:22
*** baoli has joined #openstack-meeting14:22
ihrachysyou heard that week was quiet. I bet it's the best time to get in, since I suspect this week to be as quiet as the previous one. ;)14:22
Sam-I-Ami cant take on any more stuff right now :/14:23
*** baoli has quit IRC14:23
ihrachysnote we have a table of people who already served the job for the project14:23
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy14:23
amotokiit is now a big table! too wide to my browser14:24
*** takashi has quit IRC14:24
scheuranihrachys, I can take over this week14:24
dasmamotoki: buy bigger monitor14:24
ihrachysI guess we reach the time when we should wrap up the list14:24
ihrachysscheuran: great!14:24
ihrachysscheuran: thanks a lot man.14:24
ihrachyswe also need to cover the next week.14:24
amotokidasm: right solution!14:24
HenryGscheuran rocks!14:24
ihrachysok, let me trigger the wrap up, I will take the next week after that.14:25
*** jmckind has quit IRC14:25
ajowe should probably think of reformating that table to something else :)14:25
*** jichen has quit IRC14:25
rossella_sajo++14:25
HenryGgo ihrachys!14:25
*** baojg has joined #openstack-meeting14:25
*** Daisy has joined #openstack-meeting14:25
dasmajo: so... you're a volunteer for reformatting?14:25
*** Daisy has quit IRC14:25
*** mrmartin has quit IRC14:25
ihrachys#topic Docs14:25
*** openstack changes topic to "Docs (Meeting topic: networking)"14:25
*** baoli has joined #openstack-meeting14:25
reedip__ Why do we need a matrix for the table ??14:26
Sam-I-Ami recommend a 3-d table :)14:26
*** Daisy has joined #openstack-meeting14:26
mhickeyscheuran:++14:26
ihrachysSam-I-Am: anything worth noting before Mitaka3 cut off?14:26
xgerman3d +114:26
ajodasm, :D next time I go for bug deputy I will fix it , I'll be happy to doit after FF14:26
reedip__scheuran:+114:26
Sam-I-Amihrachys: not much. trying to push some patches into the networking guide.14:26
mhickeyihrachys: ++14:26
Sam-I-Amgood to see a lot of contributions from neutrinos14:26
Sam-I-Amif we get MTU stuff merged, its probably fewer docs because it Just Works as it should14:27
Sam-I-Amrather than being a mess of workarounds14:27
Sam-I-Amso, removing docs is nice.14:27
ihrachyswe'll get there, seems like we are on good track with MTU work14:27
ihrachysok folks, one thing to note here is14:27
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087837.html14:27
Sam-I-Amyep14:27
*** mfranc213 has quit IRC14:27
*** aysyd has quit IRC14:27
ihrachys^ Armando posted a reminder on how to handle DocImpact tags14:27
*** aysyd has joined #openstack-meeting14:28
ihrachysbasically, we don't want to have the tag in each and every patch for a feature14:28
ihrachysa single commit with the tag is enough14:28
hichiharaAnd we shouldn't add the tag into spec14:28
ihrachysand also the tag should give brief clue which changes for docs are expected14:28
amotokiyou don't need to add DocImpact flag for both server and client changes.14:28
ihrachyshichihara: yes, adding it to specs patch is too early, since code may not land14:29
*** _amrith_ is now known as amrith14:29
*** jroll has quit IRC14:29
*** haiwei has quit IRC14:29
amotokias summary we don't need docimpact for -specs and (in most cases) -client14:30
*** jroll has joined #openstack-meeting14:30
*** jroll has quit IRC14:30
*** jroll has joined #openstack-meeting14:30
ihrachys#topic i18n liaisonship14:30
*** openstack changes topic to "i18n liaisonship (Meeting topic: networking)"14:30
*** mbound has quit IRC14:30
ihrachysone more thing to note is there was an email from i18n folks that they need a i18n liaison from all projects, including neutron14:30
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087757.html14:30
ihrachyswe already have amotoki serving for the role for several cycles14:30
*** nkrinner has quit IRC14:31
*** andymaier has quit IRC14:31
*** neiljerram has quit IRC14:31
*** jreeves has joined #openstack-meeting14:31
ihrachyswhile Akihiro is too kind to serve for more, neither he will be against someone stepping in and freeing him from the obligation14:31
ihrachysright amotoki ?14:31
*** yfujioka has joined #openstack-meeting14:31
amotokii am working as i18n team as well, so it is not an additional job... but if someone volunteers it, feel free to go!14:32
*** neiljerram has joined #openstack-meeting14:32
ihrachysgreat. so if someone is willing to share some burden there, please reach to amotoki or armax or me14:32
*** yanyanhu has quit IRC14:32
amotokiperhaps it would be small burden.14:32
ihrachys(just an idea) could be a good start for someone not yet too involved into the team business14:33
ihrachysok, moving on14:33
ihrachys#topic Open Discussion14:33
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:33
*** eharney has joined #openstack-meeting14:33
ihrachysamotoki: wanna reiterate on the client release? or we are good?14:33
*** mbound has joined #openstack-meeting14:34
amotokii don't want to discuss them again :)14:34
-amotoki- just cannot find a right place14:34
ihrachysok great :)14:34
*** ociuhandu has joined #openstack-meeting14:34
ihrachysanyone has anything to raise in this tight pre-release time?14:34
ihrachysok, I guess the answer is no and we can get back to reviews and coding and drinking coffee14:35
ihrachysthanks folks for attending, next time it will finally be US time, Monday14:35
*** sshnaidm has quit IRC14:35
dasmthanks all.14:36
ihrachyskeep up the good work ;)14:36
ihrachys#endmeeting14:36
dasmhave a nice day!14:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:36
openstackMeeting ended Tue Mar  1 14:36:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-01-14.01.html14:36
xgermano/14:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-01-14.01.txt14:36
rossella_sthanks ihrachys14:36
hichiharabye14:36
rossella_sbyt!14:36
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-01-14.01.log.html14:36
rossella_sbye14:36
annpBye14:36
amotokithanks14:36
Sam-I-Amthanks14:36
*** Sam-I-Am has left #openstack-meeting14:36
*** weshay has joined #openstack-meeting14:36
*** jlibosva has left #openstack-meeting14:36
reedip__o/14:36
*** johnsom has left #openstack-meeting14:36
*** janzian has left #openstack-meeting14:36
*** hynekm has left #openstack-meeting14:36
mhickeybye14:36
*** dasm has left #openstack-meeting14:38
*** wwriverrat has left #openstack-meeting14:38
*** reedip__ has quit IRC14:39
*** baoli has quit IRC14:39
*** ociuhandu has quit IRC14:39
*** ajmiller has quit IRC14:39
*** d0ugal has quit IRC14:39
*** d0ugal has joined #openstack-meeting14:40
*** d0ugal has quit IRC14:40
*** d0ugal has joined #openstack-meeting14:41
*** baoli has joined #openstack-meeting14:41
*** trozet has joined #openstack-meeting14:43
*** jreeves_ has joined #openstack-meeting14:43
*** Daisy has quit IRC14:44
*** jreeves has quit IRC14:44
*** zzxwill has quit IRC14:44
*** rbak has joined #openstack-meeting14:46
*** azbiswas has joined #openstack-meeting14:46
*** ociuhandu has joined #openstack-meeting14:47
*** jmckind_ has quit IRC14:47
*** jschwarz has quit IRC14:48
*** xyang1 has joined #openstack-meeting14:48
*** sdake has quit IRC14:49
*** akuznetsov has joined #openstack-meeting14:49
*** Pengfei has quit IRC14:50
*** yfujioka has quit IRC14:51
*** knikolla has joined #openstack-meeting14:51
*** azbiswas has quit IRC14:52
*** drankis has joined #openstack-meeting14:52
*** drankis has quit IRC14:52
*** iyamahat has joined #openstack-meeting14:52
*** akuznetsov has quit IRC14:54
*** takashi has joined #openstack-meeting14:54
*** harshs has joined #openstack-meeting14:55
*** doug-fish has joined #openstack-meeting14:55
*** zeih has quit IRC14:55
*** sdake has joined #openstack-meeting14:56
*** rkukura has left #openstack-meeting14:56
*** e0ne has quit IRC14:56
*** sverma has quit IRC14:57
*** mfranc213 has joined #openstack-meeting14:57
*** mlavalle has joined #openstack-meeting14:57
*** jmckind has joined #openstack-meeting14:58
*** iyamahat has quit IRC14:59
*** pl0pix has joined #openstack-meeting14:59
*** baojg has quit IRC14:59
jasondotstar#startmeeting openstack-salt15:00
openstackMeeting started Tue Mar  1 15:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-salt)"15:00
openstackThe meeting name has been set to 'openstack_salt'15:00
jasondotstar#topic Roll Call15:00
jasondotstaro/15:00
*** openstack changes topic to "Roll Call (Meeting topic: openstack-salt)"15:00
*** haomaiwang has quit IRC15:01
*** jschwarz has joined #openstack-meeting15:01
*** claudiub|2 has joined #openstack-meeting15:01
*** haomaiwa_ has joined #openstack-meeting15:01
vhowardo/15:02
jasondotstarwhoops sorry! I'm 1hr early i think :-015:02
*** amuller has left #openstack-meeting15:02
*** Pengfei has joined #openstack-meeting15:02
*** fawadkhaliq has joined #openstack-meeting15:02
*** harshs has quit IRC15:02
carl_baldwinOne minute.  Laptop not connecting...15:02
jasondotstaryes 1hr early.15:03
arif-alihi15:03
jasondotstar#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
openstackMeeting ended Tue Mar  1 15:03:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
carl_baldwinOkay, had to restart client.15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-15.00.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-15.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-15.00.log.html15:03
jasondotstararif-ali: we'll try this again in 1hr :-)15:03
carl_baldwinHi all.  I'm ready for the routed networks meeting.15:03
neiljerramhi15:03
obondarevo/15:03
carl_baldwin#startmeeting neutron_routed_networks15:04
jasondotstarcarl_baldwin: sorry, got hear 1hr early. your team has the floor.15:04
openstackMeeting started Tue Mar  1 15:04:00 2016 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
vikram_hi15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: neutron_routed_networks)"15:04
openstackThe meeting name has been set to 'neutron_routed_networks'15:04
carl_baldwinjasondotstar: No worries, it happens.  I did it last week.  ;)15:04
carl_baldwin#topic Announcements15:04
*** openstack changes topic to "Announcements (Meeting topic: neutron_routed_networks)"15:04
*** claudiub has quit IRC15:04
mlavallehi15:04
*** Daisy has joined #openstack-meeting15:04
carl_baldwinI think the latest version of the spec has general consensus.  At least, I haven't heard any arguments against it.15:05
carl_baldwinAnd there is good support for it.15:05
carl_baldwinI'll try to keep the agenda on the meetings page.15:05
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-Routed-Networks#March_1st.2C_201615:05
*** yfujioka has joined #openstack-meeting15:05
*** dane_leblanc has joined #openstack-meeting15:05
carl_baldwinminus the stuff after the #15:05
neiljerramBut I have at least a query...15:06
carl_baldwinneiljerram: Please, present it.  :)15:06
neiljerramIt's a bit long for here - I commented early Monday.15:07
neiljerramBut in summary, it's about how Segment objects relate (or not) to segment descriptions in the multi-provider extension15:07
carl_baldwinneiljerram: I will look for it.  I did not see it yesterday.  Though, yesterday was filled with other catching up.15:07
*** yamahata has joined #openstack-meeting15:07
*** manjeets has joined #openstack-meeting15:07
*** sneti has joined #openstack-meeting15:07
*** yfujioka has quit IRC15:07
*** cloudtrainme has joined #openstack-meeting15:08
neiljerramcarl_baldwin, Thanks - and I'm sorry for not getting to a full re-review earlier than I did.15:08
carl_baldwinneiljerram: They certainly relate.  They share a table.15:08
*** sbelous_ has left #openstack-meeting15:09
*** Daisy has quit IRC15:09
carl_baldwinneiljerram: The segments of the multi-provider extension are being "promoted" to a first class thing.  Both extensions will be different views to the same data.15:09
neiljerramSo how can there be independent CRUD for Segment objects then?  Surely the only Segment objects that should exist are those implied by the content of the multi-provider (or provider) extension?15:10
carl_baldwinI hope that one day we can consolidate the extensions.  The multi-provider extension has some usability drawbacks.15:10
*** azbiswas_ has joined #openstack-meeting15:11
carl_baldwinneiljerram: It is a single data model with different views.15:11
*** korzen has quit IRC15:12
*** zz_dimtruck is now known as dimtruck15:12
*** takashi has quit IRC15:12
*** vishwanathj_ has joined #openstack-meeting15:12
carl_baldwinThe announcement that I had is that we are beginning to collect code contributions on the gerrit topic.15:13
carl_baldwin#link https://review.openstack.org/#/q/status:open+topic:bp/routed-networks15:13
*** brad_behle has joined #openstack-meeting15:13
carl_baldwinThese are all WIP for now but will be fleshed out quickly.15:13
*** sridharg has quit IRC15:13
vikram_nice15:13
carl_baldwinI actually have another patch locally that I will put up soon.15:13
neiljerramcarl_baldwin, So, for example, if a Network was configured with multiprov seg1,seg2,seg3, three corresponding Segment objects would be auto-created.  And then if a fourth Segment object was added by the operator, it would be as though the Network had been reconfigured with seg1,seg2,seg3,seg4 ?15:14
carl_baldwinAnd, I'm going to pull in an existing patch to move the segments table out of ML2 and in to core.  Let me find a link.15:14
*** luzC has joined #openstack-meeting15:15
carl_baldwinneiljerram: That sounds about right.15:15
carl_baldwin#link https://review.openstack.org/#/c/242393/15:17
neiljerramcarl_baldwin, OK thanks.  I'll defer to continuing this in Gerrit now, so as not to derail the meeting here.15:17
carl_baldwin^ Patch to move segments table.15:17
*** ajmiller_ has joined #openstack-meeting15:17
*** ajmiller has joined #openstack-meeting15:17
*** dmacpher has joined #openstack-meeting15:17
*** luzC has quit IRC15:17
carl_baldwinneiljerram: Do you see something fundamentally wrong with this approach?15:17
*** rhagarty has joined #openstack-meeting15:18
mlavallecarl_baldwin: is this patchset going to be the head of the dependency chain?15:18
carl_baldwinmlavalle: Yes, once I get things rebased.15:18
*** takashi has joined #openstack-meeting15:18
mlavallecarl_baldwin: ++15:18
neiljerramcarl_baldwin, No; but I means that Calico can't use Segments to express its clustered IP allocation desires15:18
neiljerrams/I means/it means.15:19
*** ajmiller has quit IRC15:19
*** sdake_ has joined #openstack-meeting15:20
carl_baldwinneiljerram: That is a good point.  My impression of our past conversations was that it wasn't going to work for that use case and you were looking at host aware IPAM.15:20
*** sigmavirus24_awa is now known as sigmavirus2415:20
*** annp has quit IRC15:20
*** rhagarty_ has joined #openstack-meeting15:21
carl_baldwinmlavalle: I had started that work on the plane and made some progress.  I need to button it up and get it posted.15:21
mlavallecarl_baldwin: ok, i'll wait for you to post it and then align my patchset with it15:22
*** pradk has quit IRC15:22
*** pradk has joined #openstack-meeting15:22
carl_baldwinneiljerram: This is worth some more discussion.15:22
*** sdake has quit IRC15:23
carl_baldwin#topic Work items15:23
*** openstack changes topic to "Work items (Meeting topic: neutron_routed_networks)"15:23
carl_baldwin#link https://review.openstack.org/#/c/225384/18/specs/mitaka/routed-networks.rst15:23
neiljerramcarl_baldwin, Yes, more discussion.  (I guess you mean the difference between hard and soft boundaries.  But I think there are remaining migration questions for VMs in a genuinely segmented network too.)15:23
*** fwdit has quit IRC15:23
* carl_baldwin realizes he has some draft comments in reply to feedback from armax still on the spec. Needs to wrap that up.15:24
*** zzxwill has joined #openstack-meeting15:24
*** rhagarty has quit IRC15:24
carl_baldwinI laid out work items starting on line 44315:24
*** rhagarty_ has quit IRC15:25
carl_baldwinI got started on the first one and have a WIP patch up for that.15:25
*** emagana has joined #openstack-meeting15:25
carl_baldwinmlavalle: you have started, and made good progress, on the third.15:25
mlavallecarl_baldwin: yeah15:26
*** merooney has joined #openstack-meeting15:26
carl_baldwinBy the end of the week, I'll have patches up for the rest of the sub-items in the first bullet.15:26
carl_baldwinneiljerram: Not ignoring your comment.  Let's get to it in a few minutes.15:27
*** mtanino has joined #openstack-meeting15:27
carl_baldwinTo be honest, I may need someone to help contribute to the segments model.  I get pulled away from it a lot and so progress is slow.15:28
*** jdurgin1 has joined #openstack-meeting15:28
carl_baldwinWe also have a need for someone to start playing around with deferred IP allocation.15:28
*** sneti_ has joined #openstack-meeting15:28
*** sneti has quit IRC15:28
neiljerramcarl_baldwin, I am definitely interested in the latter.15:28
mlavallecarl_baldwin: I am available to help...... you tell me where you want me to help15:29
mlavallecarl_baldwin: besides what I am already doing15:29
*** singhj has joined #openstack-meeting15:30
carl_baldwinneiljerram: Great.  Let me know what you need to get going on that.15:30
neiljerramI could do with a good and exhaustive picture of what the Nova/Neutron interactions are at the moment.15:31
carl_baldwinneiljerram: You mean what they currently are, or what they will be?15:31
neiljerramcarl_baldwin, What they are now.15:32
*** rossella_s has quit IRC15:32
neiljerramcarl_baldwin, I suspect there are possibilities that I'm not yet aware of.15:32
carl_baldwinneiljerram: Have you had a chance to read the Nova spec that I have up?15:32
*** rossella_s has joined #openstack-meeting15:32
carl_baldwinmlavalle: Also, have you had a chance to review that one?15:33
neiljerramcarl_baldwin, Not yet; I'll do that.15:33
mlavallecarl_baldwin: yes, I gave it a first pass yesterday. I intend to go over it again today15:33
*** jorge_munoz has joined #openstack-meeting15:34
carl_baldwinneiljerram: It goes in to a little more detail.  It describes a few use cases for how an end user interactions.  For example, end user calls Nova boot with --net.  Or, end user calls Neutron to create a port with no IP address and calls boot with that port, etc.15:34
*** sshnaidm has joined #openstack-meeting15:34
carl_baldwin#link https://review.openstack.org/#/c/263898/15:35
carl_baldwinIt has gone without a meaningful review for a little while now and that concerns me.15:35
carl_baldwinAs for the current nova / neutron interactions, mlavalle is my goto guy.  :)15:36
neiljerramSorry!15:36
carl_baldwinI learned quite a bit about it by reviewing his DNS code.15:37
*** spotz_zzz is now known as spotz15:37
*** baohua_ has quit IRC15:37
mlavallecarl_baldwin: yes, that is why I drew attention to it yesterday in the nova scheduler meeting15:37
mlavallecarl_baldwin: I meant the spec15:37
mlavallecarl_baldwin: maybe also I will attend the nova meeting on Tursday to start bringing it up15:37
carl_baldwinmlavalle: I should have jumped in yesterday.  It was the end of an early meeting and I wasn't in a position to type.  But, I was surprised that they seemed to think it was new.15:38
mlavalleThursday^^^15:38
*** dmorita has quit IRC15:38
*** takashi has quit IRC15:38
carl_baldwinmlavalle: I wanted to tell them that this work was featured prominently at the Nova mid-cycle and was the subject of a rather long discussion.  Many of those guys were there.15:38
*** dmorita has joined #openstack-meeting15:39
carl_baldwinmlavalle: That would be great.  Let's not let them forget this spec is out there and is important to Neutron.15:39
carl_baldwin:)15:39
mlavallecarl_baldwin: let's remind them during the next their next meeting15:39
*** mbound has quit IRC15:40
*** andymaier has joined #openstack-meeting15:40
*** mbound has joined #openstack-meeting15:40
*** annegentle has quit IRC15:40
*** numans has quit IRC15:40
carl_baldwinneiljerram: So, back to deferred IP allocation.  I think what we need is for someone to try it out.  But, to try it out, we might need the work that I haven't posted yet to attach subnets to segments.15:40
*** keedya has joined #openstack-meeting15:40
carl_baldwin#action carl_baldwin will post work to link subnets and segments.15:41
carl_baldwinneiljerram: Then, we need to defer IP allocation when the segment is not known until host binding and see how Nova reacts to that.15:41
*** zeih has joined #openstack-meeting15:42
carl_baldwinmlavalle: ++15:42
neiljerramcarl_baldwin, Well I would hope that work on deferred IP allocation would _not_ be closely tied to segments.  So that it could be applicable to scenarios that don't use segments.15:42
*** ryanpetrello has quit IRC15:43
*** mrmartin has joined #openstack-meeting15:43
*** dmorita has quit IRC15:43
*** esker has quit IRC15:43
*** merooney has quit IRC15:43
carl_baldwinneiljerram: Yes.  We just need to know what triggers deferred IP allocation in the non-segments case.15:43
*** yamamoto has quit IRC15:43
neiljerramcarl_baldwin, Right.15:43
*** ryanpetrello has joined #openstack-meeting15:44
carl_baldwinneiljerram: Because I don't think we want to defer for every port create.15:44
*** esker has joined #openstack-meeting15:44
neiljerramcarl_baldwin, Agreed.15:44
neiljerramcarl_baldwin, That would be a big change for lots of existing situations15:44
carl_baldwinneiljerram: ++15:44
carl_baldwinneiljerram: Right now, one trigger for deferred allocation is that all of the subnets are tied to segments and the segment is not known.  That doesn't have to be the only trigger.15:45
neiljerramcarl_baldwin, So for me I think next step is to think what that trigger should be.15:45
carl_baldwinWe could have another mechanism where IPAM itself triggers deferred allocation.15:45
*** amotoki has quit IRC15:46
carl_baldwinneiljerram: I'm just thinking out loud here.15:46
*** zeih has quit IRC15:46
neiljerramYes, I was just thinking the same.  If a particular driver wants to be host-dependent, it should have a property that says 'that means I need deferred allocation'15:46
neiljerramIPAM driver, I meant there.15:46
carl_baldwinneiljerram: Something along those lines is what I'm thinking too.15:47
neiljerramAlthough I also wonder whether it might be interesting to look at Subnet/host mapping similar to the Segment/host mapping in the current spec.15:47
*** zzxwill has quit IRC15:47
*** azbiswas has joined #openstack-meeting15:48
neiljerramThat could allow host/Subnet affinity in the core, separately with the connectivity implications of being a segment.15:48
carl_baldwinneiljerram: I think you may be on to something.15:48
carl_baldwinmlavalle: Are you following?15:49
mlavallecarl_baldwin: yes15:49
*** jaypipes has quit IRC15:50
carl_baldwinneiljerram: So, a plugin / driver could provide an interface for host / subnet mapping?  It might go through segments and might not.  Is that kind of what you're thinking?15:50
*** akuznetsov has joined #openstack-meeting15:50
*** jlanoux has quit IRC15:50
neiljerramcarl_baldwin, yes, that's it.15:50
*** dmorita has joined #openstack-meeting15:50
carl_baldwinAnd, I think the hard vs soft boundaries may come in to play here.15:51
*** yamahata has quit IRC15:51
neiljerramcarl_baldwin, For Calico in particular that would work very nicely, because I guess much of the core code would be common with the segmented case, but we wouldn't have to write a pluggable IPAM driver.15:51
*** yamamoto has joined #openstack-meeting15:52
neiljerramThe boundaries question is interesting in the segmented case too, I think.  Can a VM on segment migrate to a host on another segment?15:53
carl_baldwinneiljerram: At the moment, no.15:53
*** azbiswas has quit IRC15:53
carl_baldwinMigration would be limited to same segment.15:53
carl_baldwins/would/will/15:53
*** azbiswas has joined #openstack-meeting15:53
mlavallecarl_baldwin: we need to tweak the spec, don't we?15:54
*** gokrokve has joined #openstack-meeting15:54
*** akuznetsov has quit IRC15:55
*** dmorita has quit IRC15:55
*** delattec has joined #openstack-meeting15:55
*** vijendar has joined #openstack-meeting15:55
carl_baldwinmlavalle: For the mapping part?  Let me think about it.  I don't want to stall the current spec.  This might just be a follow-on.15:55
*** cdelatte has quit IRC15:55
carl_baldwinmlavalle: I might want to consult with you later today to flesh this idea out.15:55
mlavallecarl_baldwin: yeah..... for the mapping part.... ok, let's talk later15:56
*** jward_ is now known as jward15:56
carl_baldwinmlavalle: It doesn't really change what we need around segment / host mapping in the short term.15:56
neiljerramcarl_baldwin, I'm sorry again for raising this so late - we've been focussing here on a release, for quite a while.  But I have time to help now.15:56
mlavallecarl_baldwin: agree15:56
mlavallecarl_baldwin: but is additional stuff that we need to do15:57
*** maishsk has quit IRC15:58
carl_baldwinmlavalle: Right.  I think I want to go look at the segment aware DHCP patch too in this context.15:58
*** brad_behle has left #openstack-meeting15:58
carl_baldwin#action carl_baldwin will work out host / subnet mapping interface.15:58
carl_baldwinWell, we're about out of time.  Anything else?15:58
mlavallecarl_baldwin: not from me.... actually I need to go to another meeting :-)15:59
carl_baldwinThanks vikram_ obondarev mlavalle and neiljerram (did I forget anyone?)15:59
neiljerramThanks!15:59
vikram_thanks15:59
mlavallethanks!15:59
carl_baldwinHope to see more next week.15:59
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Mar  1 16:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-01-15.04.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-01-15.04.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-01-15.04.log.html16:00
*** vikram_ has quit IRC16:00
*** mlavalle has left #openstack-meeting16:00
jasondotstar#startmeeting openstack-salt16:00
openstackMeeting started Tue Mar  1 16:00:40 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack-salt)"16:00
openstackThe meeting name has been set to 'openstack_salt'16:00
jasondotstarlet's try this again :-)16:00
jasondotstar#topic roll call16:00
*** openstack changes topic to "roll call (Meeting topic: openstack-salt)"16:00
jasondotstaro/16:00
arif-alihi16:00
*** haomaiwa_ has quit IRC16:01
cznewthi16:01
*** ilyashakhat has joined #openstack-meeting16:01
jasondotstarhi cznewt, arif-ali16:01
jasondotstaranother minute and we'll get going....16:01
*** haomaiwang has joined #openstack-meeting16:01
*** genunix has joined #openstack-meeting16:02
genunixo/16:02
jasondotstarhi genunix16:02
*** tellesnobrega is now known as tellesnobrega_af16:02
genunixHello :-)16:02
kevinbentonHi16:02
jasondotstarhi kevinbenton16:02
jasondotstar#topic Introduction16:03
*** openstack changes topic to "Introduction (Meeting topic: openstack-salt)"16:03
jasondotstarThis meeting for the openstack-salt team16:03
jasondotstarIf you're interested in contributing to the discussion, please join #openstack-salt16:03
jasondotstarMeetings are Weekly on Tuesdays at 1600UTC16:03
liqwhello ;)16:03
jasondotstar#link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting16:03
jasondotstar#link https://wiki.openstack.org/wiki/Meetings/openstack-salt16:04
jasondotstarok....16:04
jasondotstar#topic Review past action items16:04
*** openstack changes topic to "Review past action items (Meeting topic: openstack-salt)"16:04
*** Guest67668 has joined #openstack-meeting16:04
jasondotstarwe didn't have a meeting last week16:04
*** kevinbenton has quit IRC16:04
jasondotstarso everything we had on the board was carried over. with that let's see where we are16:05
jasondotstargenunix to continue openstack packaging research16:05
*** azbiswa__ has joined #openstack-meeting16:05
jasondotstarany updates?16:05
genunixjasondotstar: nope :-X16:05
*** merooney has joined #openstack-meeting16:05
genunixjasondotstar: too busy with contrail packaging for ARM16:06
jasondotstarno worries16:06
jasondotstarlet's move it up16:06
arif-alithis also ties in what I am doing, how are you proposing of hosting the formulas?16:06
*** ajmiller_ has quit IRC16:06
arif-aliand then to build? tarballs.openstack.org?16:06
*** ajmiller_ has joined #openstack-meeting16:06
jasondotstar#action genunix tlo continue researching openstack packaging16:06
carl_baldwinxiaohhui: ping16:07
*** azbiswas has quit IRC16:08
carl_baldwinjasondotstar: sorry wrong room16:08
genunixarif-ali: I don't know tarballs.openstack.org, what did you find regarding RPM packaging of formulas?16:08
*** cdub has joined #openstack-meeting16:08
jasondotstarcarl_baldwin: no worries16:08
arif-aliwell, all the projects in RDO, assume that the tarball of the project is hosted at tarball.openstack.org, (I think that is the URL)16:08
cznewtthe formula packages are now hosted at tcpcloud repo for debain, we can look how we could use the tarballs.os.org16:08
*** annp has joined #openstack-meeting16:09
genunixour repo (apt.tcpcloud.eu) + Launchpad PPA (launchpad.org/~tcpcloud)16:09
arif-aliand then they use that on their build server and spec files16:09
jasondotstarjust so that I understand....16:09
jasondotstaras an example16:09
*** azbiswas_ has quit IRC16:09
jasondotstarthe salt-formula-ceilometer project16:09
jasondotstarwhat will be in the pkg?16:10
jasondotstarwhat's the RPM or DEB comprised of?16:10
*** macsz has quit IRC16:10
arif-alithey are comprised of the actual formulas for the projects, I presume16:10
*** Pengfei has quit IRC16:11
*** dmacpher is now known as dmacpher-afk16:11
cznewtyes the content of service dir16:11
*** luzC has joined #openstack-meeting16:11
jasondotstarso we're simply packaging up the salt formulas we develop16:12
cznewtthe install is simple copying over to proper place16:12
cznewtyes16:12
jasondotstar+116:12
*** macsz has joined #openstack-meeting16:12
arif-aliI have an example of the RPMs in http://yum.ocf.co.uk/rh7/noarch/ for RPM packages16:12
jasondotstar#agreed the packages we build will be comprised of the actual salt formulas for each project16:12
jasondotstar#link http://yum.ocf.co.uk/rh7/noarch/16:12
cznewtthe ci is setup for building apt packages, not for rpm now16:12
jasondotstarcznewt: is that what you're working on figuring out?16:13
*** e0ne has joined #openstack-meeting16:13
cznewtwe can look into building rpms using openstack ci16:13
*** Guest67668 is now known as annegentl_16:13
*** jaypipes has joined #openstack-meeting16:13
*** xingchao has quit IRC16:13
jasondotstaryeah, we'll need someone to take a look at that16:14
jasondotstarany takers?16:14
cznewtand switching the apt building as well16:14
*** xingchao has joined #openstack-meeting16:14
*** hdaniel has quit IRC16:14
arif-aliok, I have spec files available, that's listed in the etherpad16:14
*** xingchao has quit IRC16:14
jasondotstarok16:15
jasondotstar#action Research building RPMs using the openstack-ci16:15
jasondotstarok let's keep moving16:15
jasondotstarjasondotstar to begin working on the launchpad integration (enlisting help from cznewt)16:16
jasondotstarso16:16
jasondotstari've created all the launchpad projects16:16
jasondotstarfor each of the salt projects we've got16:17
*** Qiming has quit IRC16:17
jasondotstarfrom a discussion that I had with -infra16:17
jasondotstarsince we've got the LP projects named the same as the git.o.o projects16:17
jasondotstarwe should be able to simply reference bug-IDs16:17
jasondotstarin our commit msgs16:17
jasondotstarso that they close bugs that are filed in LaunchPad16:18
jasondotstarin a nutshell, LP is simply used for bug tracking, and blueprint documentation16:18
*** snecker has joined #openstack-meeting16:18
jasondotstarall of our code and the review process is hosted on reviews.o.o16:19
jasondotstarthat's about where that tasks sits atm16:19
jasondotstarquestions?16:19
genunixgood, so LP is ready now?16:19
jasondotstaryes16:19
jasondotstarit is ready16:19
*** jlanoux has joined #openstack-meeting16:20
jasondotstareach of our core team members should be members of the LP groups16:20
*** jschwarz has quit IRC16:20
jasondotstarfor bug tracking 'OpenStack Salt Bugs Team' is the group you should join.16:20
cznewtfor the tasks, I'd use LP16:20
jasondotstarcznewt: true16:20
*** tellesnobrega_af is now known as tellesnobrega16:20
jasondotstartasks should go there as well.16:20
arif-ali+116:20
jasondotstarBlueprints are feature docs16:21
jasondotstarlike the RPM and DEB packaging16:21
*** yamamoto has quit IRC16:21
jasondotstarim wondering if we should create a blueprint doc for that16:21
jasondotstaris that a feature? or just part of the business?16:21
genunixand in which project then?16:21
cznewtThe first task https://bugs.launchpad.net/openstack-salt/+bug/155181716:21
openstackLaunchpad bug 1551817 in openstack-salt "Testing of lab environments [vagrant, heat] results" [Undecided,New]16:21
jasondotstareach project has its own bug tracker16:22
jasondotstarfor a common task16:22
jasondotstarwe'd have that task replicated across each LP bug site16:22
*** leunam112 has quit IRC16:22
genunixso for RPM packaging you need to create one task for every formula?16:23
cznewtor use openstack-salt project?16:23
*** garthb has joined #openstack-meeting16:23
*** yamamoto has joined #openstack-meeting16:23
cznewtfor extra formula tasks16:23
genunixyes I would also preffer using openstack-salt for common formula-independent tasks16:23
*** singhj has quit IRC16:23
jasondotstarhmmmm16:23
jasondotstari guess we could16:23
jasondotstaris that the general consensus here?16:23
jasondotstarany -infra team ppl listening in care to advise?16:24
jasondotstarok for now, i'm good with that idea16:25
egonseems reasonable.16:25
jasondotstar#agreed For common forumula-independent tasks, those will be filed under the openstack-salt LP project16:25
*** yamahata has joined #openstack-meeting16:26
jasondotstar#agreed For more specific tasks, those will be filed under its associated salt-formula-* LP project16:26
jasondotstarok next:16:26
jasondotstarcznewt to look at beaker gates and how to fold in a similar process into the openstack-salt workflow16:27
cznewtI've looked up a few solustions, I don't know which is best16:27
*** xinwu has joined #openstack-meeting16:27
*** belmoreira has quit IRC16:28
cznewtwe'd use jenkins and heat to automate lab tests16:28
*** _nadya_ has quit IRC16:28
jasondotstar+116:28
cznewtdoes anyone have experience with beaver?16:28
*** _nadya_ has joined #openstack-meeting16:29
jasondotstarbeaver or beaker?16:29
*** cdub has quit IRC16:29
cznewtbeaker of course :)16:29
genunixsidenote: if we want to do lab tests, we should move all required formulas under openstack big tent (nginx/apache and so)16:29
*** ddecapit has joined #openstack-meeting16:29
*** ddecapit is now known as DuaneDeC716:30
jasondotstar+116:30
cznewtyes it on the roadmap16:30
*** kevinbenton has joined #openstack-meeting16:30
jasondotstarI've tried out beaker for puppet stuff in the past, but I probably need to play with it more :-/16:30
genunixI would create an action to make a list of these formulas and proceed with it16:30
*** armax has joined #openstack-meeting16:31
jasondotstargenunix: proceed with implementing beaker tests with each formula?16:31
cznewtYes, but there's discussion whether to host generic formulas in salt ecosystem rather that openstack16:31
jasondotstar+116:31
jasondotstari think the openstack specific ones should be under big tent, and any supporting formulas should be under salt16:32
*** absubram has joined #openstack-meeting16:32
genunixBut there are not any common salt formulas or sort-of salt big tent or anything. We would need to create such "tent" first :-)16:33
cznewtthe formulas we have are generally more functional than official ones, but the metadata definition is very much different for some seamless integration with official salt formulas16:33
*** _nadya_ has quit IRC16:33
*** fawadkhaliq has quit IRC16:33
*** absubram_ has joined #openstack-meeting16:33
*** ajmiller__ has joined #openstack-meeting16:33
jasondotstari c16:34
*** rhagarty has joined #openstack-meeting16:34
cznewtBut preferably i'd have all essential formulas for openstack-salt managed from one place16:34
*** yamamoto has quit IRC16:34
genunix..also try to standarize some things in community (btw still no response to my mailing list post)16:34
*** yamamoto has joined #openstack-meeting16:34
*** yamamoto has quit IRC16:34
arif-aliI agree, that have everything the openstack-salt depends on, should be under one place16:34
jasondotstarone place = one project?16:35
genunixone place = openstack big tent?16:35
jasondotstaror one place = projects hosted in one place (big tent)16:35
*** ajmiller_ has quit IRC16:35
*** garyk has quit IRC16:36
cznewtyes this is big tent question :)16:36
*** yamahata has quit IRC16:36
*** paul-carlton2 has quit IRC16:37
cznewtI prefer separation of formulas as it help integration with custom formulas and better reusability16:37
*** Leom has joined #openstack-meeting16:37
*** absubram has quit IRC16:37
*** absubram_ is now known as absubram16:37
jasondotstarcznewt: agreed. each service should have it's own formula project16:37
jasondotstarthen we can figure out which ones belong under big tent16:37
jasondotstarand which ones don't.16:37
cznewtit is not the simplest way, but given the complexity and growing number of services to manage16:37
*** cloudtrainme has quit IRC16:38
jasondotstarright. plus it's nice to have the ability to have self contained services16:38
*** e0ne has quit IRC16:38
jasondotstaras much as we can 'box' them16:38
cznewtwell some of the essential formulas are listed for the regular discussion, and will remain still, but at the end we should end up having formula for each openstack service16:39
*** eharney has quit IRC16:39
jasondotstar+116:39
*** apoorvad has joined #openstack-meeting16:39
arif-ali+116:39
cznewtnow it's like 10 formulas, with core it's like 20-25, and with extra openstack services we can go up to 5016:39
*** prashantD has joined #openstack-meeting16:39
*** singhj has joined #openstack-meeting16:40
cznewtand that is for start16:40
jasondotstar#action Research big tent.  Determine which of our salt-formula-* projects should fall under the big tent umbrella, and which of the more host-generic formulas should be pushed up to the salt community16:40
jasondotstarok let's keep moving:16:40
*** e0ne has joined #openstack-meeting16:40
jasondotstarcznewt to work on getting the cloud-based labs for openstack-salt testing fully operational16:40
cznewtand from this some 10 formulas are supplemetal not strictly openstack and the growing number will be openstack ones16:40
*** eharney has joined #openstack-meeting16:41
cznewt#link http://openstack-salt.tcpcloud.eu/develop/quickstart-heat.html16:41
cznewtThe documentation for running the heat and vagrant based has been updated16:41
jasondotstar\o/16:41
jasondotstarnice16:42
cznewtthe updates are tested, on linux for no16:42
cznewtnow16:42
*** leunam112 has joined #openstack-meeting16:42
*** DuaneDeC7 has quit IRC16:42
jasondotstarcool.16:42
*** DuaneDeC7 has joined #openstack-meeting16:42
jasondotstarok next:16:42
jasondotstarUNASSIGNED => continue monitoring the salt mailing list for a response16:42
jasondotstarthink we just heard that we've still had no response on this16:42
*** leunam112 is now known as Manuel_11216:43
cznewtyes16:43
jasondotstarok16:43
jasondotstarnext: jasondotstar to write a blog post that illustrates how to setup the openstack-salt local dev environment16:43
jasondotstarI've yet to write this. :-X16:43
cznewtI can help with this16:43
jasondotstarso, I'll move this one up16:43
jasondotstarcznewt: ok cool.16:43
jasondotstarI'll get with you on it16:44
cznewtYes16:44
jasondotstarbasically it's rewriting the steps you've got16:44
jasondotstarbut I want to add a short terminal vid too.16:44
cznewtYes, cool I liked that16:44
jasondotstaranyway, we'll work on this this week16:44
jasondotstarnext:  jasondotstar to coordinate 'sunsetting' of the salt formula repos under the stackforge/ namespace16:45
cznewtand a little copy-pasting for steps16:45
jasondotstarcznewt: right :-)16:45
jasondotstarok this one is COMPLETE16:45
*** mdorman has left #openstack-meeting16:45
jasondotstarall of the old stackforge repos have been marked as RETIRED via the process laid out by -infra16:46
jasondotstarand they are marked as RO16:46
jasondotstarso we shouldn't have dual salt efforts16:46
*** mrmartin has quit IRC16:46
jasondotstarwith what we have under the openstack/ namespace and the stackforge/ namespace16:46
jasondotstarany questions on this?16:47
*** azbiswa__ has quit IRC16:47
jasondotstarok next: arif-ali to confirm where the tarballed pkgs for the openstack salt formulas should be hosted16:47
cznewtyes, I've audited the formulas and found no additional functionality16:47
*** thorst_ is now known as thorst_afk16:47
*** azbiswas has joined #openstack-meeting16:47
jasondotstarmost of those old ones didn't have much in them at all.16:47
arif-aliso, this, I think we have already discussed, and maybe there is another route we need to create the RPMs, i.e. via openstack-ci16:48
*** pfallenop has quit IRC16:48
*** jmckind has quit IRC16:48
arif-aliSo, I need to understand how to do it via that, and can move the spec files into the relevant places to get them built16:48
*** pfallenop has joined #openstack-meeting16:48
cznewt+116:49
*** scheuran has quit IRC16:49
jasondotstaryep, i think we covered this - we just need to know how to use the openstack ci16:49
arif-alidoes anyone here know?16:50
cznewtnot for building tarballs, we'll have to go to -infra guys16:50
jasondotstartrue16:51
*** rvasilets has left #openstack-meeting16:51
*** adiantum has quit IRC16:51
jasondotstar#action talk to the  -infra team about using the openstack ci pipeline for building RPMs16:51
*** sneti_ has quit IRC16:51
jasondotstarok running short on time16:51
*** gokrokve has quit IRC16:52
jasondotstarwe've had quite a bit of discussion for topics from last meeting16:52
*** azbiswas has quit IRC16:52
jasondotstaranything else before we give the last 8 mins over to today's agenda?16:52
cznewtlet's go16:52
*** ilyashakhat has quit IRC16:52
cznewt#topic Today's Agenda16:53
*** sneti has joined #openstack-meeting16:53
cznewtOpenstack-salt RedHat test stacks16:53
jasondotstar#topic todays agenda16:53
*** openstack changes topic to "todays agenda (Meeting topic: openstack-salt)"16:53
jasondotstargo for it16:53
*** brucet has joined #openstack-meeting16:53
cznewtwhat is the centos version required for testing redhat stack?16:54
jasondotstar7 at this point i think16:54
arif-aliI am using centos 7.2 in most of my installations, so makes sense to 716:54
jasondotstarwe can target 7 and if we find out otherwise16:55
jasondotstarwe can add 616:55
cznewtwe have the stack for single and cluster, the question is, do we make config node (salt-master) run centos for the begging as well16:55
*** rcernin has quit IRC16:55
cznewtor do we wait until the packages are ready, or work with git based salt master?16:55
*** jmckind has joined #openstack-meeting16:55
arif-alithere is already salt-master for el716:56
arif-alifrom epel16:56
jasondotstar+116:56
*** ygbo has quit IRC16:56
jasondotstarwe can use that16:56
*** fawadkhaliq has joined #openstack-meeting16:56
arif-alithat's what I am using in my test environments16:56
jasondotstar#action more discussion neede on testing the RH stack16:57
cznewtyes, delivering the formulas i was thinking16:57
jasondotstar#action more discussion needed on testing the RH stack16:57
jasondotstarhow about this one? Testing lab: Schedule testing, prepare rules16:58
cznewtNow access to the testing lab16:58
cznewtlet us know at #openstack-salt channel16:58
jasondotstar+116:58
*** evgenyf has quit IRC16:58
jasondotstar    Discuss the Beaker-gate implementation possibilities, real experience16:58
jasondotstar    Discussion about adding new formulas under openstack: Swift, Linux, OpenSSH, Salt, Reclass, Rabbit, Galera16:58
cznewtwe'll have to figure rotating passwords and distributing them among team members16:58
jasondotstarlet's move these two to the #openstack-salt channel16:59
cznewtyes this was tackled at tha beginning16:59
*** rlrossit has joined #openstack-meeting16:59
cznewtok16:59
jasondotstarright, we can continue there16:59
jasondotstarfinally we've got to reviews that need to be addressed16:59
jasondotstar#link https://review.openstack.org/#/c/276353/17:00
*** cdent has joined #openstack-meeting17:00
jasondotstar#link https://review.openstack.org/#/c/276228/17:00
*** DuaneDeC7 has quit IRC17:00
jasondotstarlet's look at these as well17:00
jasondotstarok... times up :-/17:00
jasondotstaranything else?17:00
jasondotstarok.... lost track of time, but good discussion17:01
*** haomaiwang has quit IRC17:01
*** annegentl_ has quit IRC17:01
jasondotstarlet's continue in channel17:01
jasondotstarthanks team17:01
jasondotstar#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Tue Mar  1 17:01:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-01-16.00.log.html17:01
gibi#startmeeting nova notification17:01
*** mbound has quit IRC17:01
openstackMeeting started Tue Mar  1 17:01:29 2016 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** genunix has left #openstack-meeting17:01
*** openstack changes topic to " (Meeting topic: nova notification)"17:01
openstackThe meeting name has been set to 'nova_notification'17:01
rlrossito/17:01
*** haomaiwa_ has joined #openstack-meeting17:01
* rlrossit actually remembered to be on time today17:01
gibirlrossit: hi!17:01
cdento/17:02
gibicdent: hi!17:02
gibi#topic open reviews17:02
*** openstack changes topic to "open reviews (Meeting topic: nova notification)"17:02
*** matrohon has quit IRC17:02
gibicdent: thanks for the review on https://review.openstack.org/#/c/276363/17:03
*** gyee has joined #openstack-meeting17:03
gibirlrossit: if you have time to check ^^17:03
cdentgibi: seems like a great start17:03
*** david8hu has joined #openstack-meeting17:03
rlrossitI will put it on my TODO list, though I cannot guarantee when I will get to it17:03
gibirlrossit: thanks :)17:03
gibibesides that patch I started working on the Newton spec17:04
*** annegentl_ has joined #openstack-meeting17:04
gibiI've just pushed the first version17:04
gibiwith TODOs17:04
gibihttps://review.openstack.org/#/c/286675/1/specs/newton/approved/versioned-notification-transformation.rst17:04
gibiIt think I can sort out the TODOs this week17:05
gibiany early feedback is appreciated17:05
*** yamamoto has joined #openstack-meeting17:05
* rlrossit also puts that on his TODO list17:05
* rlrossit feels bad about shirking community responsibilities lately17:06
gibiI share the feeling. I had bad weeks internall too17:06
*** maishsk has joined #openstack-meeting17:06
gibianyhow that is the current state17:07
*** pcaruana has quit IRC17:07
gibiif you have no questions then I won't hold you here17:08
*** jorge_munoz has quit IRC17:08
* gibi aims for the shortest meeting ever17:08
rlrossityeah nothing from me17:08
rlrossitand I know cdent is busy building inventories and whatnot17:08
*** Guest77563 has quit IRC17:09
cdentyeah, pretty much17:09
*** brucet has quit IRC17:09
gibiOK. Thanks for dropping by.17:09
cdentI got nothing to add17:09
gibiSee you around :)17:09
cdent\o/17:09
gibi#endmeeting17:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:09
openstackMeeting ended Tue Mar  1 17:09:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-03-01-17.01.html17:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-03-01-17.01.txt17:09
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-03-01-17.01.log.html17:09
*** brucet has joined #openstack-meeting17:09
*** rlrossit has left #openstack-meeting17:09
*** Swami has joined #openstack-meeting17:10
*** cdent has left #openstack-meeting17:10
*** yamamoto has quit IRC17:10
*** achanda has joined #openstack-meeting17:10
*** hashar has quit IRC17:10
*** fzdarsky is now known as fzdarsky|afk17:13
*** Leom has quit IRC17:14
*** Leom has joined #openstack-meeting17:14
*** maishsk_ has joined #openstack-meeting17:16
*** dims_ has joined #openstack-meeting17:17
*** zeih_ has joined #openstack-meeting17:17
*** maishsk has quit IRC17:17
*** maishsk_ is now known as maishsk17:17
*** banix has quit IRC17:17
*** xinwu has quit IRC17:18
*** hemna has quit IRC17:18
*** dims has quit IRC17:19
*** salv-orl_ has joined #openstack-meeting17:19
*** hemna has joined #openstack-meeting17:19
*** neelashah has quit IRC17:20
*** timcline has joined #openstack-meeting17:20
*** salv-orlando has quit IRC17:22
*** jdurgin1 has quit IRC17:24
*** erlon has joined #openstack-meeting17:27
*** notmorgan is now known as morgan17:28
*** Leom has quit IRC17:29
*** paul-carlton2 has joined #openstack-meeting17:29
*** banix has joined #openstack-meeting17:29
*** neelashah has joined #openstack-meeting17:32
*** cloudtrainme has joined #openstack-meeting17:32
*** cloudtrainme has quit IRC17:33
*** mrmartin has joined #openstack-meeting17:34
*** thorst_afk has quit IRC17:35
*** thorst_afk has joined #openstack-meeting17:36
*** sneti_ has joined #openstack-meeting17:36
*** thorst_afk is now known as thorst_17:36
*** annegentl_ has quit IRC17:38
*** sneti has quit IRC17:39
*** brucet has quit IRC17:39
*** mhickey has quit IRC17:40
*** jlanoux has quit IRC17:41
*** numans has joined #openstack-meeting17:41
*** navidp has joined #openstack-meeting17:42
*** ihrachys has quit IRC17:42
*** ihrachys has joined #openstack-meeting17:43
*** derekh has quit IRC17:43
*** lhcheng has joined #openstack-meeting17:45
*** brucet has joined #openstack-meeting17:46
*** ihrachys has quit IRC17:47
*** absubram has quit IRC17:48
*** claudiub|2 has quit IRC17:49
*** merooney has quit IRC17:49
*** StefanPaetowJisc has joined #openstack-meeting17:51
*** comay has joined #openstack-meeting17:51
*** sdake_ has quit IRC17:51
*** sneti_ has quit IRC17:53
*** roxanaghe has joined #openstack-meeting17:53
*** piet has joined #openstack-meeting17:54
*** merooney has joined #openstack-meeting17:57
*** gema has joined #openstack-meeting17:57
*** shaleh has joined #openstack-meeting17:57
*** baoli has quit IRC17:58
*** numans has quit IRC17:59
*** samleon has joined #openstack-meeting17:59
*** harshs has joined #openstack-meeting18:00
*** tsymanczyk has joined #openstack-meeting18:00
*** krtaylor has quit IRC18:00
*** brucet has quit IRC18:00
*** sc68cal has joined #openstack-meeting18:00
*** henrynash has joined #openstack-meeting18:00
*** haomaiwa_ has quit IRC18:01
stevemaro/18:01
*** haomaiwang has joined #openstack-meeting18:01
raildoo/18:01
*** StefanPaetowJi-1 has joined #openstack-meeting18:01
shaleh\o18:01
tsymanczyk\o18:01
topolo/18:01
lhchengo/18:01
lbragstado/18:01
*** rderose has joined #openstack-meeting18:01
tjcocozz\o/18:01
henrynashlet’s make keystone great again18:01
stevemarcourtsey keystone meeting ping for ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, edmondsw, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rodrigods, roxanaghe, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub, rderose, samleon, xek, MaxPC, tjcocozz, jorge_mu18:01
stevemarnoz18:01
ayoungWoot!18:01
gemao/18:01
henrynashoh, it is great18:01
stevemarhenrynash: you are having too much fun :)18:01
bknudsonforeigners think this is funny18:02
samueldmqhi all18:02
stevemar#startmeeting keystone18:02
openstackMeeting started Tue Mar  1 18:02:18 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Main_Agenda18:02
henrynashjust using teh ammunition he’s givin’ us18:02
stevemarnot much on the agenda today!18:02
dstaneko/18:02
roxanaghe\o18:02
StefanPaetowJi-1Evening :-)18:02
stevemar#topic mitaka-3 release countdown18:02
henrynashbknudson: actually we’re pretty much all in a state of disbelief18:02
*** openstack changes topic to "mitaka-3 release countdown (Meeting topic: keystone)"18:02
stevemarwelcome StefanPaetowJi-1 :)18:03
bretono/18:03
amakarovhi!18:03
stevemarbknudson: we think it's down right hilarious18:03
stevemaranyyywho18:03
stevemarmitaka-3 is in good shape!!! https://launchpad.net/keystone/+milestone/mitaka-318:03
gyee\o18:03
*** zeih_ has quit IRC18:03
bknudsonjust wait til we build that wall18:03
stevemarshadow users and reseller landed yesterday18:03
raildostevemar: yay \o/18:04
rderoseo/18:04
stevemarand we bumped cascade project detele/update since we couldn't decide on authorization for it18:04
henrynashstevemar: as indicated on irc, it would be nice to let https://review.openstack.org/#/c/286452/1 merge (51 mins away)18:04
*** timcline has quit IRC18:04
*** ajmiller__ is now known as ajmiller18:04
stevemarhuge thanks to everyone involved :)18:04
* topol looking fwd to those renegotiated trade deals with Canada and Great Britain...18:05
*** timcline has joined #openstack-meeting18:05
*** StefanPaetowJisc has quit IRC18:05
stevemari know i've been pestering everyone about reviewing, but i think it paid off18:05
*** StefanPaetowJi-1 is now known as StefanPaetowJisc18:05
*** penick has joined #openstack-meeting18:05
stevemarboth features look solid18:05
stevemarhenrynash: yep, that'll go in18:05
topolexcellent!!!18:05
*** ndipanov has quit IRC18:05
henrynashgreat job by all18:05
stevemari'm waiting til bug 1549705 is fixed/merged18:06
openstackbug 1549705 in OpenStack Identity (keystone) "migrate DB failed due to password cannot be null" [High,In progress] https://launchpad.net/bugs/1549705 - Assigned to Dave Chen (wei-d-chen)18:06
samueldmqeverybody happy :)18:06
*** sarob has joined #openstack-meeting18:06
gyeehappy on Super Tuesday!18:06
henrynash(does dance in clogs of the seven army blankets)18:06
stevemarhenrynash: 286452 should merge soon, and i'll tag keystone when 285152 merges :)18:06
morgangyee: lets leave politics out of this today :P18:06
gyeemorgan, they started it :-)18:07
henrynashstevemar: excellent18:07
*** baoli has joined #openstack-meeting18:07
*** yamamoto has joined #openstack-meeting18:07
henrynashgyee: oh, “politics”, that’s what it is….18:07
*** xinwu has joined #openstack-meeting18:07
stevemar#topic mitaka-rc118:07
*** openstack changes topic to "mitaka-rc1 (Meeting topic: keystone)"18:07
stevemar#link https://launchpad.net/keystone/+milestone/mitaka-rc118:08
bknudsondo we get a stable branch?18:08
samueldmqstevemar: when is mitaka-rc1 due date?18:08
*** sudipto has quit IRC18:08
*** Leo_ has joined #openstack-meeting18:08
stevemarsamueldmq: http://releases.openstack.org/mitaka/schedule.html18:08
samueldmqhenrynash: maybe get is_domain in the token in mitaka rc-1?18:08
*** e0ne has quit IRC18:08
stevemarsamueldmq: Mar 14-1818:08
samueldmqhenrynash: well, discuss here with others ? :)18:08
stevemarbknudson: a stable for mitaka?18:09
samueldmqstevemar: thx18:09
bknudsonstevemar: yes, a stable branch for mitaka18:09
*** ivar-lazzaro has joined #openstack-meeting18:09
henrynashsamueldmq: not sure we want to add anything to the token after m318:09
bknudsonso we can merge N features.18:09
stevemarbknudson: not yet, i assume those aren't created until after mitaka-3 is tagged, or rc118:09
stevemardhellmann: ^18:09
*** Leom has joined #openstack-meeting18:10
bknudsonyou going to -2 reviews that propose new features?18:10
*** timcline has quit IRC18:10
stevemarbknudson: yep, all cores are welcomed to -2 new features that are proposed18:10
stevemarthis should strictly be bug fixing18:10
samueldmqstevemar: ++18:10
henrynashstevemar: I’m working on a fix for https://bugs.launchpad.net/keystone/+bug/1517038, but it would need a driver interface change (i.e. moving yo a V9 interface for the domain_config)……although it is debatable as to whether an experimental driver interface is frozen or not18:10
openstackLaunchpad bug 1517038 in OpenStack Identity (keystone) "API-based Domain config method could temporarily show partial update" [Medium,New]18:10
*** manjeets has left #openstack-meeting18:11
stevemarhenrynash: hmm18:11
rodrigodso/ late18:12
stevemarhenrynash: i would say not18:12
*** yamamoto has quit IRC18:12
stevemarnow is a great time to go through the bug list if anyone has spare cycles and try to fix minor bugs during the rc1 period18:12
sheeprinequit18:13
henrynashstevemar: we have label it V8 (when they all got labled)….but the whole domain_config feature is marked as experimental still18:13
*** Leo_ has quit IRC18:13
*** pauloewerton has joined #openstack-meeting18:13
samueldmqstevemar: just added another topic to agenda18:13
*** Zyric has joined #openstack-meeting18:13
lbragstadalso - keeping up on the newly opened bugs will be important too18:13
henrynashif we are cool with keeping it at V8, then that maxes teh fix easier!18:14
*** baoli has quit IRC18:14
*** macsz has quit IRC18:14
stevemarhenrynash: yeah, let's milk the experimental status for all it's worth :)18:14
henrynashstevemar: spoken like a true leader18:14
stevemargyee: raildo lbragstad i'm assuming you all have a handle on bug 1376937 and bug 154162118:14
openstackbug 1376937 in OpenStack Identity (keystone) "No way to prevent duplicates in endpoints" [Medium,In progress] https://launchpad.net/bugs/1376937 - Assigned to Raildo Mascena de Sousa Filho (raildo)18:14
openstackbug 1541621 in OpenStack Identity (keystone) "Invalid fernet X-Subject-Token token should result in 404 instead of 401" [Medium,In progress] https://launchpad.net/bugs/1541621 - Assigned to Guang Yee (guang-yee)18:14
gyeestevemar, working on it18:14
*** vishwanathj_ has quit IRC18:14
stevemargyee: thank you18:14
*** Zyric has left #openstack-meeting18:15
raildostevemar: working on it too18:15
stevemarsamueldmq: your topic is not showing up, what is it?18:15
*** cznewt has quit IRC18:15
*** tongli has joined #openstack-meeting18:15
samueldmqstevemar: looks like I should press 'Save PAge'18:16
samueldmqstevemar: * Add is_domain in the token for rc1 <code>henrynash, samueldmq</code>18:16
stevemar#topic Add is_domain in the token for rc118:16
*** openstack changes topic to "Add is_domain in the token for rc1 (Meeting topic: keystone)"18:16
stevemarhenrynash  samueldmq go for it18:16
henrynashsamueldmq: I’ll let you argue this one18:16
samueldmqhenrynash: k18:16
stevemaralso, if editing the wiki page, it looks like there is a new security measure -- they have a "question" before saving the page, this is due to the spam attacks18:17
samueldmqso, projects now can act as domains18:17
samueldmqstevemar: yep18:17
samueldmqwhat we buy from it is to make it easier for other projs to adopt domain scoped tokens18:17
rodrigodssamueldmq, can you point to the changes? middleware, client and keystone18:17
samueldmqthat are project scoped tokens + is_domain flag18:18
raildorodrigods: https://review.openstack.org/#/c/197331/18:18
bknudsonsince no other projects are going to pick up a new feature now I don't see the need to put this in keystone in M.18:18
samueldmqraildo: thanks18:18
rodrigodsraildo, thx18:18
rodrigodsraildo, is that all?18:18
samueldmqbknudson: is this considered new feature? I mean, the feature is there, we have merged the API18:19
samueldmqit's just about making our change more complete18:19
raildorodrigods: no, the topic will be better to get all patches18:19
raildo#link https://review.openstack.org/#/q/topic:bp/add-isdomain-to-token18:19
bknudsonsamueldmq: for another project to use this would be a new feature for them.18:19
rodrigodsthanks raildo18:19
ayoungmorgan, I think removing the cache exposed some leak over between tests18:19
rodrigodsbknudson, not really...18:19
rodrigodsit should be just a tweak in the policy file18:20
bknudsonrodrigods: is any other project waiting on this for M?18:20
henrynashbknudson, samuedlmq: so no new project will use this in their M release, the only reason to cnsider this is to allow early work on N for other projects18:20
ayoungmorgan, if I rebase my patch on top of master a bunch of the cache tests fail in setup18:20
ayoungRROR: InvocationError: '/usr/bin/bash tools/pretty_tox.sh keystone.tests.unit.test_backend_sql.SqlTokenCacheInvalidation.test_delete_unscoped_token'18:20
ayoung    keystone.exception.ProjectNotFound: Could not find project: 91078ffd3935441f8fc0e7d3674472f118:20
samueldmqhenrynash: ++18:20
bknudsonwe can merge it when N opens18:20
samueldmqand iirc we have told hrizon guys about this feature18:21
*** azbiswas has joined #openstack-meeting18:21
rodrigodshenrynash, bknudson, deployers can use the feature by only changing the policy file18:21
rodrigodsright?18:21
rodrigodsif it lands in middleware18:21
rodrigodsfor other projects18:21
samueldmqbknudson: yes, I got your point; we may work together with them in our side + their side to merge all in a single cycle18:21
david-lylehorizon's not going to take advantage in M even if it's there18:21
samueldmqrodrigods: interesting; but in the case of horizon what bknudson is saying makes sense18:22
samueldmqand maybe changing token format is risky this late18:22
ayoungdavid-lyle, let's be hones,t Horizon won't take advantage of it in 'S' if  it is there in 'M'18:22
samueldmqstevemar: ^18:22
henrynashsmaueldmq: I’ve had a look at the changes needs this morning, and while teh basic fucntionality is pretty straightforward, there are (in my mind) still some question about auth requests etc. (e.g. can you use project name + domain_id=None ?)18:22
*** jmckind has quit IRC18:22
samueldmqhenrynash: yes, so looks like there are others questions and corner cases to be thought18:23
samueldmqN is safer18:23
samueldmqimo18:23
stevemari don't see the harm in adding it in M to keystone, but there is no rush18:23
henrynashsamueldmq: agreed… I think this deserves extra thought18:24
rodrigodsif it is the case, where it lands in M18:24
rodrigodsand in the beginning of N everyone notices the design is wrong18:24
rodrigodsits better to not rush than imo18:24
samueldmqstevemar: yes; my single point was that now, is_domain projects is just an alternate API to domains one18:24
rodrigodshave been a while that i don't look the changes18:24
*** sputnik13 has joined #openstack-meeting18:24
samueldmqstevemar: but that's okay, it's a step anyways18:24
david-lyleayoung ?18:25
henrynashsamueldmq: it’s a huge step!18:25
*** whenry_ has joined #openstack-meeting18:25
bknudsonone small step for samueldmq, a giant leap for henrynash18:25
samueldmqhenrynash: yes, I am not saying it wassn't something great18:25
*** jichen has joined #openstack-meeting18:25
samueldmqhenrynash: sorry didn't mean that :)18:25
htrutathe basics of is_domain in token was tested a few weeks ago. But I do agree that we might be more careful on that18:25
henrynashbknudson: I can’r keep up with the real men….18:25
*** haneef has joined #openstack-meeting18:26
raildoI think it's a good idea discuss this topic with the phase 2 from reseller in a design session18:26
samueldmqhenrynash: bknudson I meant it'd be still better, but not that it alone isn't good already :(18:26
*** azbiswas has quit IRC18:26
henrynashsamueldmq: we know…we’re just ribbing you18:26
*** serverascode has quit IRC18:26
samueldmqhenrynash: :'(18:27
StefanPaetowJiscAwwwww18:27
*** toscalix has quit IRC18:27
ayoungdavid-lyle, for examplem, Horizon really needs to only use password to get an unscoped token, then use that to get a scoped token, and then Keystone should defautl on the "unscoped to scoped only" rule18:27
*** zhiyan has quit IRC18:27
samueldmqstevemar: cool, so looks like we have an agreement, let's discuss more at the summit :)18:27
samueldmqand get this in N18:27
ayoungthat has been there a few releases now.18:27
henrynashsamueldmq: yep18:27
*** cznewt has joined #openstack-meeting18:27
*** weshay has quit IRC18:27
stevemarsamueldmq: good call18:27
*** blogan_ is now known as blogan18:27
ayoungwe have an explicit_unscoped  flag18:28
stevemarno need to rush18:28
stevemarlet's allow the storm that was mitaka-3 settle a little bit ;)18:28
samueldmqstevemar: ++ just would like to get more agreement and eyes on it :)18:28
*** serverascode has joined #openstack-meeting18:28
htrutastevemar: cascade operations is also punted to N, right?18:28
samueldmqstevemar: yes it ws, but we won18:28
*** zhiyan has joined #openstack-meeting18:28
samueldmqhtruta: yep; as anounced earlier by stevemar18:28
stevemarhtruta: yep - couldn't come up with a good policy / authz for it18:28
stevemarhtruta: all the work is there, just not the route18:29
stevemarhtruta: it wasn't gating as of monday, so it didn't make the cut :(18:29
gyeeayoung, david-lyle, yeah the least privilege design came up a few times at yesterdays CSA Summit18:29
StefanPaetowJiscstevemar: probably stupid q; when does N open?18:29
*** azbiswas_ has joined #openstack-meeting18:29
htrutastevemar: cool. That might be fast in N18:29
htrutais there any FFE ?18:29
samueldmqhtruta: and safer, and better :)18:30
stevemarStefanPaetowJisc: should be soon! i don't have the exact day/time, but any week now18:30
htrutasamueldmq: ++18:30
ayounggyee, have you hunted down nkinder yet?  He's there18:30
StefanPaetowJiscOk, ta18:30
stevemarStefanPaetowJisc: i think it's just after milestone-3 or just after rc-1, i always forget18:30
gyeeayoung, no, too many people there yesterday, room was full18:30
stevemarStefanPaetowJisc: the release managers do that for us :)18:31
*** ashtokolov_ has joined #openstack-meeting18:31
stevemar#topic open discussion18:31
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:31
*** htruta has left #openstack-meeting18:31
StefanPaetowJiscOk, will keep an eye on that re: my *ahem* request ;-)18:31
*** roaet- has joined #openstack-meeting18:31
*** htruta has joined #openstack-meeting18:31
bknudsonwhat do you think about test refactoring during this rc phase?18:32
ayoungcommit e8ac71f0360b88772044ac2638d161aa00ec5b5518:32
ayoungAuthor: Adam Young <ayoung@redhat.com>18:32
ayoungDate:   Wed Dec 17 12:40:54 2014 -050018:32
gyeestevemar, bknudson, https://review.openstack.org/#/c/277436, should I backout the v2 changes?18:32
ayoungwow18:32
stevemarbknudson: please do so!18:32
*** j^2_ has joined #openstack-meeting18:32
bknudsonI think samueldmq had some test refactoring lined up.18:32
gyeestevemar, bknudson, I thought correcting the return code is allowed, no?18:32
stevemarbknudson: i think samueldmq had some major test refactoring ready18:32
stevemarbknudson: yep..18:32
ayounghttp://git.openstack.org/cgit/openstack/keystone/commit/?id=e8ac71f0360b88772044ac2638d161aa00ec5b55  david-lyle18:32
bknudsongyee: correcting return codes is not allowed.18:32
bknudsongyee: unless it was a 500 error18:32
samueldmqstevemar: bknudson yes, just need to rebase18:33
gyeealrighty then, I'll back out the v2 changes18:33
samueldmqit's the split of the huge test_backend.py18:33
samueldmqwhich now has up to 7k lines iirc18:33
stevemarsamueldmq: nice :)18:33
*** sambetts is now known as sambetts|afk18:33
stevemarlooking forward to it18:33
*** lekha_ has joined #openstack-meeting18:33
stevemarwe also released a new keystoneclient version: https://pypi.python.org/pypi/python-keystoneclient/2.3.1 , this should be the last one for M18:33
bknudsonsamueldmq: I've also got https://review.openstack.org/#/c/283822/ so maybe there's some overlap18:33
samueldmqstevemar: bknudson: I will rebase all that still this week18:33
stevemarbknudson: there is likely some overlap with samueldmq's work18:34
*** paul-carlton2 has quit IRC18:34
samueldmqbknudson: nice, I will look at that too, and see if we're going through the same approach18:34
stevemarthe rackers are quiet today :)18:35
bknudsonthe test_backend_* should be testing the driver and not the manager.18:35
*** jorge_munoz has joined #openstack-meeting18:36
samueldmqdstanek: henrynash and I also discussed about where to put the new tests, we decided to put in (e.g) resource/test_backends.py18:36
raildostevemar: lbragstad ayoung I believe that we can find a way to finish the fernet default token provider (https://review.openstack.org/#/c/258650/) on mitaka, we only have 8 failed tests, right now...18:36
stevemarbknudson: i'll go through a lot of the open changes today and -2 a bunch18:36
samueldmqbknudson: hmm, but yes that makes sense too, backends should test the drivers, tests for manager should have another name, I agree18:36
samueldmqbknudson: we can discuss more details in -keystone later :)18:36
ayoungraildo, raildo need the trust patch, too18:37
stevemarraildo: i'm in no rush to push, it's a default, a deployer can change what they don't want to use18:37
ayoungraildo, and..I need to get back to that...let's see18:37
*** roaet_ has quit IRC18:37
*** ashtokolov has quit IRC18:37
*** lekha has quit IRC18:37
*** j^2 has quit IRC18:37
stevemarraildo: bugs only, and tests for the remainder of mitaka18:37
*** j^2_ is now known as j^218:37
*** ashtokolov_ is now known as ashtokolov18:37
raildostevemar: hum.. got it, thanks :)18:37
samueldmqstevemar: will there be any release for ksclient yet ?18:38
*** merooney has quit IRC18:38
*** lekha_ is now known as lekha18:38
stevemarsamueldmq: we just had one yesterday :)18:38
stevemarsamueldmq: https://pypi.python.org/pypi/python-keystoneclient/2.3.118:38
samueldmqstevemar: oh, I will try to get some functional tests in18:38
raildoayoung: if you want, I can help you :D18:38
stevemarthe libraries are finalized at this point18:38
samueldmqstevemar: but that can easily come in the next cycle18:38
ayoungraildo, let me see if I can repro on my machine:18:38
stevemarsamueldmq: go ahead, tests are more than welcomed, and encouraged at this point of the cycle18:39
samueldmqstevemar: we're already benefiting from it if it's on master anyways18:39
stevemarsamueldmq: yep18:39
StefanPaetowJiscSwitching devices...18:39
*** StefanPaetowJisc has quit IRC18:39
stevemartests and bug fixes should be the only things merging in all our repos for the next little while, until N opens18:39
*** StefanPaetowJisc has joined #openstack-meeting18:40
* samueldmq still has a ton of work to do; he's commited to do a bunch of things this cycle :p18:40
ayoungraildo, for example: tox -e py34 -- keystone.tests.unit.test_auth.FernetAuthWithTrust.test_delete_trust_revokes_token18:40
samueldmqstevemar: nice, thanks for clarifying18:40
raildoayoung: running18:40
ayoungrunning testr18:40
ayoungdb type could not be determined18:40
ayounghmmm18:40
stevemarany other things to discuss? i think we're rambling on at this point :)18:40
bknudsonayoung: rm -r .testrepository18:40
ayoungbknudson, ah18:41
ayoungnot just rebuild venv18:41
stevemarbknudson: =+18:41
stevemarbknudson: ++18:41
stevemarayoung: yeah, if you run py27 before py34, there's a weird issue and you have to remove .testrepository18:41
bknudsonI had a problem running py34 after py27 last time I tried18:41
bknudsongdbm wasn't installed or something18:42
stevemarif no one else has anything i think i'll stop the meeting here18:42
*** krtaylor has joined #openstack-meeting18:42
ayoungI totally forgot we were having a meeting18:42
*** ijw has joined #openstack-meeting18:42
stevemarayoung: i'm just that memorable :)18:43
stevemaralright, let's go back to our home in -keystone18:43
ayoungstevemar, just getting work done...18:43
stevemar#endmeeting18:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:43
openstackMeeting ended Tue Mar  1 18:43:35 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-01-18.02.html18:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-01-18.02.txt18:43
rderose:)18:43
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-01-18.02.log.html18:43
*** gema has left #openstack-meeting18:43
samueldmqthanks18:43
*** merooney has joined #openstack-meeting18:44
*** Leo_ has joined #openstack-meeting18:45
*** dims has joined #openstack-meeting18:45
*** akuznetsov has joined #openstack-meeting18:48
*** dmellado has quit IRC18:48
*** ^Gal^ has quit IRC18:48
*** shamail has quit IRC18:48
*** itsuugo has quit IRC18:50
*** Leom has quit IRC18:50
*** wolsen has quit IRC18:50
*** mdenny has quit IRC18:52
*** kashyap has quit IRC18:52
*** dims_ has quit IRC18:52
*** knikolla has quit IRC18:52
*** kashyap has joined #openstack-meeting18:52
*** ociuhandu has quit IRC18:52
*** finchd has quit IRC18:52
*** afazekas has quit IRC18:52
*** john5223 has quit IRC18:52
*** peluse has quit IRC18:52
*** ^Gal^ has joined #openstack-meeting18:52
*** fzdarsky|afk has quit IRC18:54
*** aeng has quit IRC18:54
*** myoung|mobile has quit IRC18:54
*** SpamapS has quit IRC18:54
*** openstack has joined #openstack-meeting19:14
*** ChanServ sets mode: +o openstack19:14
fungicraige: that looks very detailed19:14
*** ihrachys has joined #openstack-meeting19:14
anteayawoooo19:14
fungioh, we have meetbot back19:14
fungijust a sec while i rewind all those for the log19:14
fungi#startmeeting infra19:15
openstackMeeting started Tue Mar  1 19:15:04 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:15
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:15
*** openstack changes topic to " (Meeting topic: infra)"19:15
openstackThe meeting name has been set to 'infra'19:15
*** adiantum has quit IRC19:15
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:15
*** shaleh has left #openstack-meeting19:15
fungi#topic Announcements19:15
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:15
*** myoung|mobile has quit IRC19:15
fungi#info Huge thanks to crinkle, yolanda, rcarrillocruz, greghaynes, nibalizer, SpamapS and jeblair for their hard work and planning on infra-cloud prior to our event last week.19:15
fungi#info Thanks to pleia2, jhesketh, wendar, purp and Hewlett-Packard Enterprise for logistics/sponsoring of the infra-cloud sprint.19:15
fungi#info Also thanks to HPE and IBM for picking up the group tab at dinner a couple nights in beautiful Fort Collins.19:15
fungi#link http://princessleia.com/journal/?p=11335 pleia2's awesome event summary19:15
fungi#topic Actions from last meeting19:15
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:15
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-02-16-19.03.html19:15
fungi"1. (none)"19:15
*** SpamapS has joined #openstack-meeting19:15
fungi#topic Specs approval19:15
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:15
*** myoung|mobile has joined #openstack-meeting19:15
funginothing new this week19:15
fungi#topic Priority Efforts: maniphest migration (craige)19:15
*** openstack changes topic to "Priority Efforts: maniphest migration (craige) (Meeting topic: infra)"19:15
fungi#link https://etherpad.openstack.org/p/maniphest-migration Created the maniphest-migration etherpad to track issues and progress19:15
*** RuiChen has quit IRC19:16
fungiokay, now we're caught up19:16
*** myoung|mobile has quit IRC19:16
fungicraige: that looks nice and detailed19:16
*** myoung|mobile has joined #openstack-meeting19:16
fungicraige: anything specific you need to call out on that list you need help with next?19:16
*** openstackstatus has joined #openstack-meeting19:17
*** ChanServ sets mode: +v openstackstatus19:17
*** samleon has quit IRC19:17
*** dfflanders has joined #openstack-meeting19:17
fungii'm taking the silence here as a "no"19:18
fungii guess we can come back to this one if craige returns19:18
jheskethfungi: craige was after a new db dump but not sure if he got it yet19:18
fungicraige: get up with one of our infra-root admins to get you an updated database dump19:18
fungi#topic Stackviz deployment options (timothyb89, austin81)19:19
*** openstack changes topic to "Stackviz deployment options (timothyb89, austin81) (Meeting topic: infra)"19:19
fungi#link https://etherpad.openstack.org/p/BKgWlKIjgQ19:19
fungi#link https://review.openstack.org/27931719:19
fungi#link https://review.openstack.org/21220719:19
fungicare to catch us up on the current state there?19:19
timothyb89sure, basically, we're looking for some high-level feedback on the two linked patches19:19
anteayathe both have wip in the title of the commit message19:20
timothyb89our goal is to get stackviz running during gate cleanup, and we're hoping that what we've got can accomplish that without impacting anything else19:20
AJaegertimothyb89: what is stackviz and what makes it that special?19:20
anteayawould you care to remove that in case they gather enough reviews to be merged?19:20
austin81anteaya: Sure, we just wanted to make sure they were in a close-to-merge state first19:21
* AJaeger misses the context for this19:21
timothyb89stackviz is a visualization utility for tempest runs19:21
fungiprobably what's special is that they want to have it run in/after every devstack-based job19:21
greghaynesI think there is a freenode split which is killing our meeting, FYI19:21
timothyb89for example, https://stackviz.timothyb89.org/s/5a325c4c-be4d-463f-b282-c313c0d987b0/#/19:21
*** Manuel_112 has quit IRC19:21
fungioh, or maybe just the ones that use tempest at least19:21
greghaynessome folks are complaining about "meeting is silent" in another channel19:21
anteayagreghaynes: which channel?19:21
greghaynesa private one19:22
anteayagreghaynes: I thought I had checked them all19:22
* craige returns19:22
*** Manuel_112 has joined #openstack-meeting19:22
*** vijendar has quit IRC19:22
fungia meeting in a private channel? weird19:22
AJaegerSo, stackviz just visualizes tempest runs?19:22
timothyb89AJaeger: currently, yes, and hopefully other items in the future19:22
AJaegera meeting in a private channel where they miss logging? Really weird19:22
bkeroWe think it's a netsplit19:22
austin81AJaeger: It's primary purpose is to help devs get to the root of the problem when their patch fails and see what caused it19:23
greghaynesheh ;) in a social channel, just wanted to let youall know the likely reason for the silence19:23
pabelangerwithout diving into stackviz, I feel moving it out of dib elements and into puppet-stackviz is more inline with how we manage dependencies.19:23
anteayaline 7 and 8 of the etherpad has demo links19:23
pabelangerthat's my only real comments atm19:23
greghaynespabelanger: is the goal to bake this in to our test images?19:23
*** nibz has joined #openstack-meeting19:23
timothyb89pabelanger: would moving it into a puppet module still allow it to run on build nodes?19:24
* nibz returns from the wrong side of the netsplit19:24
bkeronibz: wb19:24
*** vhoward has quit IRC19:24
pabelangergreghaynes: I am not sure the goal to be honest19:24
anteayaI really like the details page: https://static.timothyb89.org/stackviz/#/0/timeline19:24
greghaynespabelanger: ok. Asking because the future for images we buld is more dib less puppet AFAIK19:24
fungiwe do have a longer-term goal of possibly dropping image-build-time puppet from our workers since we're in teh process of drastically simplifying what puppet does for us on them19:24
pabelangertimothyb89: yes, we manage all of our jenkins slave mostly with puppet, which runs after we do image builds19:24
*** fzdarsky|afk is now known as fzdarsky19:25
pabelangergreghaynes: right. but this would be the first time where we don't manage with puppet.  Just confirming if we are okay with that19:25
greghaynespabelanger: ah, good question to ask19:25
*** bryan_att has quit IRC19:25
*** amitry has quit IRC19:25
*** CaptTofu has quit IRC19:25
*** markmcclain has quit IRC19:25
*** navidp has quit IRC19:25
*** odyssey4me has quit IRC19:25
*** yantarou has quit IRC19:25
*** siva_krishnan has quit IRC19:25
*** briancurtin has quit IRC19:25
*** Adri2000 has quit IRC19:25
*** philipw has quit IRC19:25
*** niska has quit IRC19:25
*** nibalizer has quit IRC19:25
*** alaski has quit IRC19:25
*** bauzas has quit IRC19:25
*** tdasilva has quit IRC19:25
*** johnthetubaguy has quit IRC19:25
timothyb89so, our requirements are to build our repository, and then make the output available on build nodes during devstack-gate host cleanup - would that be possible to do with puppet?19:25
fungii'm curious why this isn't baked into devstack19:26
fungiit seems like a natural fit19:26
*** maishsk has quit IRC19:26
fungie.g. add a script to the devstack libs dir which pulls in and sets up stackvis before you run tempest19:26
*** sc68cal has quit IRC19:27
fungier, stackviz19:27
timothyb89fungi: that's been discussed before, but I believe the verdict was that it made more sense for performance to do it during image build19:27
*** singhj has quit IRC19:27
timothyb89the build process is fairly time consuming so we wanted to cache the output19:27
*** merooney has quit IRC19:27
fungisetup takes a while then? would add too much run-time repetition to devstack?19:27
timothyb89it takes ~10 minutes19:27
nibzis that because of npm install?19:27
timothyb89nibz: yes19:28
austin81nibz: yup19:28
fungiahh, okay, i recall you saying something about it pulling reference data from our subunit2sql database?19:28
greghaynesinstall? or js minimizing/lint?19:28
timothyb89greghaynes: all of the above19:28
nibzwe didn't deploy npm mirrors yet? or did we?19:28
timothyb89fungi: its similar to subunit2sql, but it reads test repositories directly19:28
greghaynesthe typical pattern for solving that is to make a package OOB from installation, so installation happens quickly...19:28
fungiokay, so npm-provided dependencies are the time-consuming part19:29
*** neelashah has joined #openstack-meeting19:29
timothyb89fungi: yes, exactly19:29
fungiand yeah, being able to pre-cache your node.js deps locally isn't an option? you need to fully install them on the worker images?19:29
AJaegerHaving reviewed earlier https://review.openstack.org/#/c/279317 - that did not include any reference on other patches or what stackviz what doing - I was very confused.19:29
* AJaeger is now getting more what you intent to do - and suggest you write a spec for this19:30
*** StefanPaetowJisc has quit IRC19:30
bkeroThey should be cacheable in ~/.npm/$PACKAGE/$VER/19:30
fungitimothyb89: how do you see this potentially interacting with other job payloads that use packages from npm? is there good sandboxing/isolation in node.js to prevent cross-dependency interactions?19:30
timothyb89fungi: afaik node dependencies are local to the directory you run 'npm install' from19:31
nibzfungi: yes, npm install creates a dir node_modules where you run it19:31
greghaynesfungi: I am still unclear if its just installing deps or js minimization (apparently its both?)19:31
*** nibalizer has joined #openstack-meeting19:31
*** navidp has joined #openstack-meeting19:31
*** bryan_att has joined #openstack-meeting19:31
*** amitry has joined #openstack-meeting19:31
*** CaptTofu has joined #openstack-meeting19:31
*** markmcclain has joined #openstack-meeting19:31
*** odyssey4me has joined #openstack-meeting19:31
*** yantarou has joined #openstack-meeting19:31
*** siva_krishnan has joined #openstack-meeting19:31
*** briancurtin has joined #openstack-meeting19:31
*** Adri2000 has joined #openstack-meeting19:31
*** philipw has joined #openstack-meeting19:31
*** niska has joined #openstack-meeting19:31
*** alaski has joined #openstack-meeting19:31
*** bauzas has joined #openstack-meeting19:31
*** tdasilva has joined #openstack-meeting19:31
*** johnthetubaguy has joined #openstack-meeting19:31
*** wolfe.freenode.net changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
greghaynesfungi: since those two need to be solved differently19:31
*** jrist has quit IRC19:31
timothyb89greghaynes: it does both, we need to install the dependencies required to run the build process19:31
*** CaptTofu has quit IRC19:31
fungiokay, so it's preinstalling rather than simply caching, but inherent isolation with npm in theory makes that safe19:31
timothyb89greghaynes: it's basically 2 commands: 'npm install' and then 'gulp prod' to build19:31
greghaynestimothyb89: yea, but I am curious which one consumes most of the time19:32
anteayaumm meetbot seems to be taking the helm regarding the topic19:32
austin81greghaynes: npm install by far19:32
greghaynesaustin81: ah, ty19:32
timothyb89greghaynes: 'npm install' is the time consuming one, 'gulp prod' takes maybe 15 seconds19:32
bkeronpm caches things in ~/.npm, and if not there it fetches it from the internet19:32
greghaynestimothyb89: awesome19:32
*** singhj has joined #openstack-meeting19:32
fungileguin apparently unsplit and reset our topic, but that's fine19:32
*** roaet has left #openstack-meeting19:32
bkeroSo if you throw them in there they should be immutable, useful, and fast19:32
*** merooney has joined #openstack-meeting19:32
fungiit'll get updated on next topic change unless something goes terribly wrong with the meetbot19:32
fungitimothyb89: so is most of the time in npm install spend downloading, or unpacking/building?19:33
*** CaptTofu has joined #openstack-meeting19:33
timothyb89bkero: npm may cache things, but the install process is still time consuming because it will check remotely to verify package versions19:33
austin81AJaeger: So with your added context, what do you think of https://review.openstack.org/#/c/279317 now?19:33
timothyb89fungi: downloading19:33
*** sripriya_ has joined #openstack-meeting19:34
AJaegeraustin81: Please write a spec ;)19:34
fungitimothyb89: so in that case, if we pre-cache them it should speed that up tremendously? or are you saying that it's actually the link checking/remote indexing  which is the time-consuming part of the download process?19:34
AJaegeraustin81: with the questions here, there's too much unknown and unusual going on, so we should document this properly19:35
*** StefanPaetowJisc has joined #openstack-meeting19:35
timothyb89fungi: in my experience, pre-caching npm packages doesn't help much, you have to run a full 'npm install' on the project directory to see a real benefit19:35
fungiyeah, i'm mostly trying to nail down what aspect of this makes it necessary to fully install components into the workers when it will only be used by a subset of jobs19:35
austin81AJaeger: Absolutley. Any helpful links to get us started?19:35
*** nibz has quit IRC19:36
AJaegeraustin81: see the infra-specs repository19:36
fungisince that seems to be a major part of the design thrust19:36
anteaya#link http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/template.rst19:36
fungi#link https://git.openstack.org/cgit/openstack-infra/infra-specs/tree/README.rst19:36
fungihas instructions19:36
*** taron1 has quit IRC19:37
*** sigmavirus24 is now known as sigmavirus24_awa19:37
AJaegerthanks fungi and anteaya for the links19:37
anteayaAJaeger: welcome19:37
fungitimothyb89: i'm also wondering if the npm install phase gets considerably faster when krotscheck's npm mirrors get deployed19:37
*** StefanPaetowJisc has quit IRC19:37
austin81fungi, anteaya: Thanks guys.19:37
timothyb89fungi: I think it would!19:37
anteaya<-- female19:38
anteayaand you are welcome19:38
*** singhj has quit IRC19:38
*** StefanPaetowJisc has joined #openstack-meeting19:38
ianwfwiw i'd also like to see a spec, because we've gone through having in devstack, having a specialised worker, installing via nodepool, but now have better mirroring infrastructure and other options around puppet19:38
austin81anteaya: My mistake :)19:38
fungibecause we have jobs already which npm install a lot of stuff (horizon functional test, i'm looking at you) which make improving that experience during job run-time imperative anyway19:38
anteayaaustin81: no worries19:38
* david-lyle blushes19:38
timothyb89a proper spec seems like a good plan :)19:38
*** ajmiller_ has joined #openstack-meeting19:39
austin81I think we've taken up enough of yalls time? Thanks for all the help19:39
fungisounds great--thanks timothyb89, austin81!19:39
timothyb89thanks everyone!19:39
fungi#topic Spec review : dib from git for nodepool (ianw / 2016-03-01)19:39
*** openstack changes topic to "Spec review : dib from git for nodepool (ianw / 2016-03-01) (Meeting topic: infra)"19:39
fungi#link https://review.openstack.org/28387719:39
ianwjust a request for review on this spec, i don't have much to say that isn't in the spec19:39
fungiwhat's the current contention on this one?19:40
anteayadavid-lyle: thanks for sharing19:40
anteaya:)19:40
fungioh, i see. new spec just as most of our reviewers disappeared to spring on infra-cloud19:40
nibalizerianw: i haven't read this but ill add it to the list19:40
ianwthere was some contention in the reviews that the extra flag was not great19:40
jeblairi confess, i'm surprised19:41
greghaynesfungi: The fear I would have is the general tightly-coupled projects issue, rather than nodepool breaking when someone who releases is around itll be whenever we merge something19:41
fungiso this goes back to the conversation we were having a couple weeks ago about whether or not installing dib from git vs having to wait for a dib release to have new features in image builds was desirable19:41
greghayneswhich is fine by me, but its something the folks who run nodepool should be aware of19:41
jeblairwhy is dib changing so fast this matters?19:41
greghaynesjeblair: mostly fedora releases IME19:41
mordredI'm not crazy about running from git on projects that infra-core does not have +2 on19:41
jeblairis dib encoding too much image building logic in itself?19:41
fungiit sounded like there was disdain at the up-to-several-day wait times for dib to tag a new release19:41
*** ajmiller has quit IRC19:41
jeblairfungi: yeah, but i feel like i expected dib to be a mostly static dependency19:42
*** winston-d_ has quit IRC19:42
ianwi don't know if distain is the word, but it can really slow things down19:42
mordredthere are some elements we use19:42
ianwjeblair: it is, until it isn't ... especially if you're brining up something new19:42
mordredlike simple-init19:42
*** akuznetsov has joined #openstack-meeting19:42
mordredthat are in the dib repo19:42
jeblairfor me the problem is not that it doesn't change fast enough, but rather that it changes at all19:42
mordredand if we need to update it - it means that we have to update it in dib and then get a release19:42
fungiinfra-specific needs should probably be in our nodepool elements rather than wrapped up in dib's default element set, yeah?19:42
mordredwell19:42
jeblairianw: could we solve this with better dib testing?19:42
mordredbut simple-init and ubuntu-miniaml are generally applicable elements19:43
mordredwe just happen to be their primary user, so we find the errors before other people19:43
greghaynesI don't think we have ever really had any desire for new dib changes beyond 1) random bugfix which IME isnt too common 2) something were not in a rush to get or 3) new distro release which is what we seem to hit a lot19:43
ianwjeblair: better dib testing will not hurt.  but when you've fixed an issue, and then it takes literally up to a week to get out there, it can be a real pain19:43
*** abregman has joined #openstack-meeting19:43
*** vijendar has joined #openstack-meeting19:43
*** Sukhdev has joined #openstack-meeting19:43
fungiso i guess the real push here is to find a way to be able to consume fixes for issues in dib elements more quickly?19:44
*** neelashah has quit IRC19:44
jeblairianw: right, so i'm thinking a change of focus: it's *dib* that should support a new distro release, and we should find a way to make that work happen in dib19:44
greghaynesjeblair: ianw re: better dib testing - I think testing of the images infra builds would help with this a lot, especially if we can test dib from git in those tests19:44
jeblairgreghaynes: yeah, so maybe if we put a job on dib that builds the images specified in project-config?19:44
*** delattec has quit IRC19:44
ianwwe are working on that19:44
greghaynesjeblair: or a job in project-config?19:44
*** pauloewerton has left #openstack-meeting19:44
fungiis simply building them sufficient, or do we need to try to boot and exercise them to turn up most of the errors in question?19:44
jeblairgreghaynes: i think we wanted that too19:45
*** singhj has joined #openstack-meeting19:45
fungimostly curious where the split between build-time and boot-time falls for the bulk of the issues encountered19:45
jeblairfungi: good q19:45
*** shamail has joined #openstack-meeting19:45
ianwwhen you're bringing up a new platform, a lot of the issues are build time19:46
greghaynesAs for dib testing - theres a large patch series I have been getting slowly merged about adding more functional testing, the issue we seem to hit most often is integration between dib and services it installs (simple-init being the great example)19:46
greghayneswhich is harder to test in dib19:46
ianwfor stable platforms, not so much19:46
ianwbut if you get a change into project-config, it is there on the next build19:47
fungimy primary concern with this suggestion is that we're trading bugs in new stuff we want to try but take time to get working for potentially hitting more bugs in stuff we already rely on19:47
*** delattec has joined #openstack-meeting19:47
ianwbut once a change is in dib, it's not like it gets any more testing until release19:48
*** jprovazn has quit IRC19:48
greghaynesthe main thing holding back the fuctional dib testing is just work hours, but I also worry it won't help us as much as we want since those tests are good at determining if a build can succeed and if it can boot, but not so much 'does glean run at the correct time to set up networking'19:48
fungiof course, my theory is based on the (possibly baseless) assumption that dib releases get more testing than just merged commits in master19:48
*** gyee has quit IRC19:48
*** dane_leblanc has quit IRC19:49
*** hashar has joined #openstack-meeting19:49
*** Leom has joined #openstack-meeting19:49
ianwfungi: that is kind of my point, as described in the spec19:50
*** neiljerram has quit IRC19:50
hasharhello o/19:50
abregmanhello \o19:50
jeblairi don't want nodepool to be the last line of dib's ci19:50
dougwiggreghaynes: just throwing this out there, but octavia jobs use dib from master to build their service vms, boot them, and then do load balancy tests through them. they've been fairly breaky due to that, and might be a reasonable short-term stand in for functional tests.19:50
jeblairi agree about the problem, but i'd like the solution to head the other direction19:50
fungiso on the issue of consuming unreleased code of deps not maintained by infra-core, i suppose that concern is also driven by an assumption that dib releases are better tested than dib's master branch state at any given point in time?19:51
*** Leom_ has joined #openstack-meeting19:51
greghaynesdougwig: Yea, we have some dib tests which build and boot images and ping them, but theres a hard question of to what level dib should be testing the services it installs (since dib's just is really just to install them)19:51
*** jmckind has joined #openstack-meeting19:51
fungior is it that we can more easily downgrade to an earlier dib release if a new one is broken, but figuring out what arbitrary commit to pin ourselves to is harder?19:51
greghaynesfungi: They arent better tested, no19:51
greghaynesMy main concern as dib-core would be firefighting19:52
*** sigmavirus24_awa is now known as sigmavirus2419:52
greghaynesI try to release when I am around to solve issues19:52
greghaynesbut I don't necessarially merge with that mindset19:52
*** ajmiller_ is now known as ajmiller19:52
ianwnodepool is quite tolerant to failures, and many of us watch the builds19:52
greghaynesfungi: er, sorry, thery *arent19:52
fungiso release time is a controlled breakage window, as opposed to having to be careful not to merge a change unless you're around to see whether it breaks your downstream consumers19:52
greghaynesyep19:53
ianwi'd say it's better for us to fix any issue that affects nodepool the day after it hits, rather than wait until more changes are behind it19:53
*** neelashah has joined #openstack-meeting19:53
*** cdent has joined #openstack-meeting19:53
fungithat definitely turns nodepool into a post-merge ci test of dib though19:53
*** sc68cal has joined #openstack-meeting19:53
jeblairperhaps what mordred was getting at was an expansion of dib-core to include nodepool-core to mitigate that19:53
mordredyah19:53
*** terryw is now known as otherwiseguy19:54
fungithat's worth bringing up to the tripleo team i guess19:54
mordredthat's my concern - not being able to react swiftly to a production outage19:54
*** Leom has quit IRC19:54
mordredif we're running from pip, we can always pin back at a previous pip revision if a release happens that breaks the world19:54
*** thingee has joined #openstack-meeting19:54
*** rromans has quit IRC19:54
mordrednow - it's image builders19:54
mordredso breaking isn't QUITE breaking the gate19:54
mordredand there is more buffer19:54
greghaynesIts a good thing to talk about, dib *really* needs more cores. I don't know how wide infra-core is so that might be a bit overkill19:54
fungibut it _can_ be if the issue is one which causes a run-time problem rather than build-time/boot-time19:55
mordredgreghaynes: there's 8 of us right now19:55
*** StefanPaetowJisc has quit IRC19:55
mordredplus ianw on nodepool-core19:55
jeblairwhat i want is for dib to be solid and unchanging.  if that's not possible, then if we are going to consider tighter integration, i think we need to consider *much* tighter integration.  like, shared cores and shared change queues so we have working cross-testing.19:55
fungithough in that case we have the option of deleting the current images if we catch it within a day19:55
*** rromans has joined #openstack-meeting19:55
*** jrist has joined #openstack-meeting19:55
greghaynesI feel like dib has been pretty solid everywhere except adding new features which infra wants, which is something that can't be solved dib side19:55
*** s3wong has joined #openstack-meeting19:55
*** rockyg has joined #openstack-meeting19:56
greghaynesspecifically supporting new dristros19:56
ianwjeblair: definitely better testing, and as mentioned, focus for dib currently.  but speed of working with infra is not always great, and this can be a pain point19:56
greghaynesmordred: Yea, so we should bring that up, I am pretty sure I would be +1 on that19:57
ianwespecially for new distros19:57
ianwanyway, maybe it's just me :)  not sure what other distros are being worked on19:57
jeblairianw: yeah, which is why i think the solution is to not do all of this work in openstack's production nodepool.  get it out on the edges in dib.19:57
fungialso, we're down to 2 minutes, so i'm going to need to punt the last several agenda topics to next week. i hope that's okay pabelanger, yorkisar, zaro, AJaeger? if not, we can try to cover stuff in #-infra between now and next week19:58
jeblairat least, the *ideal* solution :)19:58
*** sridhar_ram1 has joined #openstack-meeting19:58
AJaegerfungi, I'll paste my prepared lines to #openstack-infra ;)19:58
pabelangerall good here19:58
ianwsorry, didn't expect so much conversation on that :)19:58
*** maishsk has joined #openstack-meeting19:58
fungiso... nodepool-dev where we run the same config as production but with master dib instead of releases?19:58
greghaynesYea, I think I didn't word it too correctly, dib should definitely be sure that a newly supported distro works, but using a new distro as a downstream consumer will always be a matter of pulling in some change so there has to be some level of integration testing19:58
*** david-lyle has quit IRC19:59
funginodepool does have namespacing for its alien cleanup now, so in theory production and dev can share an environment as long as we tweak max-servers to accommodate a small slice of quota dedicated to dev19:59
jeblairi wasn't suggesting that19:59
jeblairand i don't like the idea of maintaining 2 nodepools19:59
jeblairone is hard enough20:00
fungii know, i was throwing out another idea between drinking from the firehost in production and only being able to use dib releases20:00
fungianyway, we're out of time, but can continue in the review or #-infra20:00
*** natarajk has joined #openstack-meeting20:00
fungithanks everybody!20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Mar  1 20:00:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-01-19.15.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-01-19.15.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-01-19.15.log.html20:00
ttxo/20:00
mesteryo/20:00
dhellmanno/20:00
fungisorry ttx, all yours now20:00
*** haomaiwang has quit IRC20:01
*** yolanda has left #openstack-meeting20:01
mordredo/20:01
jeblairo/20:01
russellbhi20:01
ttxfungi: you were not really late :)20:01
flaper87o/20:01
ttxannegentle, lifeless, dtroyer, markmcclain, jaypipes, sdague: around ?20:01
sdagueo/20:01
*** haomaiwang has joined #openstack-meeting20:01
*** olaph has left #openstack-meeting20:01
markmcclaino/20:01
ttx#startmeeting tc20:01
jaypipeso/20:01
openstackMeeting started Tue Mar  1 20:01:47 2016 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
abregmano/20:01
openstackThe meeting name has been set to 'tc'20:01
*** ivar-lazzaro has joined #openstack-meeting20:02
ttxGood $timeofday everyone20:02
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
ttx#topic Add a "stable:follows-policy" tag20:02
*** openstack changes topic to "Add a "stable:follows-policy" tag (Meeting topic: tc)"20:02
*** ivar-lazzaro has quit IRC20:02
ttx#link https://review.openstack.org/27791820:02
* edleafe hides in the shadows20:02
* rockyg squeezes into the back of the room20:02
ttxSo this is a tag that the stable maintenance team can use to certify that a given deliverable stable branches are following the common stable branch policy20:02
*** ivar-lazzaro has joined #openstack-meeting20:02
* sridhar_ram1 lurks20:02
ttxThat is made necessary because in the big tent there are a lot of stable/* branches that do not really follow policy those days20:02
ttx(and we still want to call them stable/* for other reasons)20:03
ttxSo it is a pretty important piece of information to communicate to those who consume our deliverables20:03
ttxmissing a few votes20:03
ttxI think mriedem addressed anne's remark20:03
ttxquestions ?20:03
sdaguelgtm20:03
flaper87lgtm20:03
* dhellmann wonders if we want to start migrating to series/* instead of stable/*20:04
ttxdhellmann: there are lots of things that encode stable/*20:04
dhellmannyeah20:04
sdaguedhellmann: there would be a pretty big cost to all our tooling for that20:04
ttx(hardcode)20:04
ttxdhellmann: but yes you are right, that's what it means today, hence the need for the tag20:04
*** taron1 has joined #openstack-meeting20:04
* thingee lurks20:04
jeblairstill something about this seems wrong20:04
*** merooney has quit IRC20:04
*** amitgandhinz has quit IRC20:04
jeblairi don't like a tag that says something follows a policy20:04
*** sdake has quit IRC20:05
amrithhello ... is this the TC meeting? (https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee)20:05
russellbamitry: yes.20:05
flaper87amrith: yes20:05
russellboops.20:05
dhellmannjeblair : we have the tag for following the deprecation policy, too. isn't this the same?20:05
mesterydhellmann: ++20:05
thingeedhellmann: +120:05
sdagueremembering the 3 weeks of trying to get the ceilometer grenade bits into a passing state because gnocchi had a custom branch structure20:05
*** xinwu has quit IRC20:05
ttxdhellmann: slightly different, the other one is an assertion by the project itself20:05
*** amitgandhinz has joined #openstack-meeting20:05
jaypipesjeblair: isn't that what the assert:XXX tags are?20:06
jaypipeskinda? :)20:06
dhellmannttx: I suppose that's a reasonable distinction to make.20:06
ttxhere the stable team grants it, so it is indeed a bit of a carrot/stick for the stable team to encourage policy following20:06
ttxnot sure that is what jeblair objects to20:06
jeblairthe reason we hardcoded stable in many places was because it meant the same thing20:07
sdaguehonestly, the stable team job is one of the more thankless jobs out there. If they feel this helps them accomplish it, I'm all for it.20:07
*** julim has quit IRC20:07
ttxjeblair: currently in infra it means "series"20:07
dtroyero/20:07
ttxsdague: ++20:07
flaper87sdague: ++20:07
annegentl_sdague: yep20:07
jeblairwhy not say "stable/" means this thing, and if you do something that doesn't mean that, call your branch something else?20:07
dhellmannyeah, we have a conflict between the way it has ended up being used and the way it was intended to be used20:07
*** ijw has quit IRC20:07
ttxjeblair: I proposed that but that would break a lot of things apparently20:08
jaypipesjeblair: I could definitely get behind that.20:08
jeblairttx: what does it break?20:08
*** julim has joined #openstack-meeting20:08
dhellmanncould we rename existing branches?20:08
ttxjeblair: I think I raised it at an infra meeting and you shot it down20:08
jeblairat least i'm consistent ;)20:08
flaper87lol20:08
*** henrynash has quit IRC20:08
sdagueI also think the lever there is weird20:08
jeblairttx: i'm still trying to understand this though20:08
ttxjeblair: if not you, maybe fungi20:09
jeblair(i'm exploring, not advocating)20:09
sdaguebecause project/foo thinks they are following stable branch policy20:09
dhellmannwe have 3 types of stable branches: actually stable, using stable/$series for convenience, and using stable/$version20:09
sdagueso they have stable/mitaka20:09
sdaguestable maint team notices they aren't20:09
*** david-lyle has joined #openstack-meeting20:09
*** maishsk has quit IRC20:09
sdaguestable maint team has authority to delete project/foo stable/mitaka branch?20:09
flaper87It'd be better for stable/* to actually be stable, fwiw.20:10
*** julim has quit IRC20:10
dhellmannso yeah, even if we don't rename things we want to give the stable team a flag to say "yes, we agree that this is stable"20:10
jeblairmaybe instead of deleting the branch, we remove the project20:10
sdaguedhellmann: right, which is that20:10
sdaguejeblair: o_O20:10
flaper87not all projects must follow the stable policy20:10
sdaguethe only project we've removed before was one that was dead for 2 cycles20:10
ttxas if we could remove a project20:10
dhellmannjeblair : rename to openstack-not-actually-stable/$project ?20:10
fungii think i didn't so much object, as express that devstack-gate's current branch mapping would get waaaay more complex if you needed to try to assert that your stable/1.3.0 or foo/bar branch should be tested against stable/liberty of some other project20:10
annegentl_wobbly/1.1.020:10
sdagueright, I don't believe removing a project is a thing that actually exists as a TC power20:10
ttxfungi: right20:11
dhellmannannegentl_ : ++20:11
jeblairfungi: absolutely20:11
russellbsure it is20:11
russellb(removing a project)20:11
jeblairsdague: oh it definitely does20:11
jeblairif we can add, we can remove20:11
russellbwe just never do it20:11
sdagueok, I'll believe it when it happens20:11
jaypipesstable-but-having-experimental-feature-backports/$project is too long of a branch name.20:11
russellbheh, right20:11
dhellmannsdague : I think he just means as an official project, not from gerrit?20:11
ttxI'm not saying this can't be implemented differently, I'm just saying a tag is the most convenient way to fix it for now20:11
dhellmannjaypipes : abbreviate it?20:11
jaypipesdhellmann: :)20:11
jeblairto try to get back onto the topic --20:11
sdaguedhellmann: it is an un-unit tested piece of policy20:11
flaper87I like the tag as an immediate solution20:11
fungithe last time i remember it coming up was when some project (maybe an oslo lib) wanted more than one stable/x.y.z that would cross-test against a specific stable branch of other repos in devstack20:11
flaper87if we find a better solution, we can always remove the tag20:11
dhellmannttx: I agree. I think we want this tag regardless, because there's the "we're trying to be stable" state to consider.20:11
ttxand I'd like to fix it now before we cut stable/mitaka all around20:11
ttxstarting tomorrow20:12
*** gokrokve has joined #openstack-meeting20:12
jeblairthe thing that's sticking with me is that we're giving our users an inconsistent story20:12
flaper87I like the idea of renaming fake stable branches, fwiw20:12
mordredjeblair: ++20:12
annegentl_jeblair: or is it quality checking for truth?20:12
*** austin81 has quit IRC20:12
mordredit's bad enough that people think that "stable/liberty" is some how "more hardend"20:12
ttxjeblair: I get your point. I think we can fix it better tomorrow, but it's more work20:12
jeblairwe're saying "stable/*" may or may not be stable20:12
annegentl_jeblair: I mean, I see it either way, yeah.20:12
flaper87jeblair: it's inconsistent now, anyway. The benefit of this tag is that it's provided by a team we trust20:12
mordredrather than "has a different policy for landing patches"20:12
sdaguejeblair: we are admitting the truth20:12
mordredbut as soon as we even step away from _that_ with things that have the openstack title on it20:13
ttxIf we decide to replace the tag with some ownership of a branch space, we can do that another day20:13
sdaguebecause the truth is stable/* may or may not be that today, which is what triggered it20:13
ttxBut I expect that would run into a lot of implementation issues20:13
*** abregman has quit IRC20:13
sdagueso, step 1 - acknowledge the state of the world, write it down20:13
*** piet has quit IRC20:13
*** dane_leblanc has joined #openstack-meeting20:13
ttxlike... projects can create branches20:13
russellbsdague: ++20:13
dhellmannright, it would be useful to be able to declare what is actually stable and then go through the exercise of fixing the things that aren't20:13
sdaguestep 2 - figure out how you want to change it20:13
flaper87I also proposed in the review that we could find a way to tag each stable branch individually20:13
ttxsdague: yep, baby steps20:13
flaper87but again, I think the current proposal is fine for now20:14
flaper87and we should evolve from there20:14
mesteryNicely put sdague, +120:14
jeblairsdague: sure, i'm just more aspirational and would like us to describe what we want things to be, rather than to follow the project and try to clean things up behind it.20:14
jeblairi typed that a while ago20:14
jeblairsdague: i guess i'm jumping to step 2 :)20:14
*** AJaeger has left #openstack-meeting20:14
ttxOK, let's approve step 1 and then someone can propose step 220:15
sdaguejeblair: right, and if stable maint wasn't already such a giant thankless job, that would be fine20:15
flaper87Ideally, I'd like each stable branch to actually be stable and follow the stable policy but that's not the goal right now20:15
*** KuDeMi has joined #openstack-meeting20:15
sdaguebut I think it needs a lot more people piled into helping on stable maint before step 2 is doable20:15
ttxI agree with that long-term goal20:15
jeblairsdague: yeah.  i don't think a -1 from me will help step 2 happen.20:15
ttxsdague: exxxactlk20:15
ttxy20:15
sdaguejeblair: right20:15
ttxok, let's move on20:15
ttxwe have 9 YES20:16
ttxjeblair: want to write down your aspirational next step on the review before I approve ?20:16
*** sdake has joined #openstack-meeting20:16
annegentl_jeblair: ayup20:16
jeblairttx: done20:16
ttxalrighty approved20:17
ttx#topic Clarify test-only license requirements20:17
*** openstack changes topic to "Clarify test-only license requirements (Meeting topic: tc)"20:17
ttx#link https://review.openstack.org/27999920:17
*** jorge_munoz has quit IRC20:17
ttxSo this is definitely a good clarification to add, and it now has enough votes to be approved20:17
ttxdo we have lifeless around20:17
dhellmannI'd like lifeless to expand on his point, if we have a minute for that?20:17
ttxlifeless mentions that this does not help with Scapy (being considered at https://review.openstack.org/#/c/277893/)20:18
*** ihrachys has quit IRC20:18
dhellmannbecause even with this clarification, I'm not comfortable approving gpl additions to the requirements list20:18
ttxI suspect his argument being we can't import libraries without creating derivative work, be it test-time or run-time code ?20:18
ttxdhellmann: right, or leaving MySQL-python in20:18
dhellmannright20:18
*** maishsk has joined #openstack-meeting20:19
ttxIt appears to still be used in trove:20:19
ttxhttp://git.openstack.org/cgit/openstack/trove/tree/requirements.txt#n3820:19
ttxAlthough I couldn't find an import so it might just be a leftover20:19
dhellmanndid you look in oslo.db?20:19
mordredI do not htink lifeless point is relevant20:19
ttxdhellmann: I'd say that the clarification is still a clarification, although it doesn't really clarify whether test-only deps are ok20:19
dhellmannmordred : not relevant to this, or not relevant to the patch adding scapy to the requirements list?20:20
mordredthe license terms are about terms for cpoying20:20
mordrednot relevant to the patch adding scapy20:20
mordredI do not think that openstack projects using scapy in testing produces any license violations20:20
mordredimho20:20
dhellmannok, I'm not really worried about that case per se20:20
ttxmordred: that is where I was too20:20
dhellmannI'm worried about the fact that we have no way to enforce it going further than that20:20
dimsmordred : yes, if it's in the base infrastructure itself. not in the project requirements20:20
jeblairmordred: i agree (regardless of where you fall on the import==derivative question)20:21
*** yamahata has quit IRC20:21
sdaguemordred: I would agree, we don't however have any mechanism for keeping things out of requirements.txt once it's in global-requirements.txt20:21
ttxI think that's another discussion though. Difficult to have without lifeless to sustain his argument20:21
sdaguegr had been a bit more of a firewall up until this point20:21
mordredI think if people have not read the recent article by eben related to the ubuntu+zfs case20:21
mordredyou should20:21
ttxsdague: taht's another technical issue20:21
mordredbecause eben makes some REALLY execellent points hwich are analogously relevant here20:21
sdagueI'm still +2 on that, but it's a thing people concerned about this should raise20:21
*** xyang1 has quit IRC20:21
annegentl_mordred: linkety?20:22
ttxOK, I propose we approve this and raise that discussion on another forum, like legal-discuss, with lifeless around20:22
flaper87ttx: ++20:22
annegentl_ttx: sounds good20:22
mordredhttps://www.softwarefreedom.org/resources/2016/linux-kernel-cddl.html20:22
jeblair#link https://www.softwarefreedom.org/resources/2016/linux-kernel-cddl.html20:22
annegentl_thanks!20:22
fungiworth noting that if the unified global requirements list remains our sole gatekeeping tool for this, then it's not actually effective if we start comingling test-time dependencies not held to the same standard in that list and we'll need to come up with a more fine-grained solution20:22
jeblairfungi: yes, that's the point dims raised20:23
*** cdub has joined #openstack-meeting20:23
fungioh, yep, i missed that comment20:23
*** carolbarrett has joined #openstack-meeting20:23
ttxyes, we should have one at some point. For the moment I'll probably do due diligence on problematic deps20:23
jeblairi don't actually think we intended it to be that, however20:23
*** vhoward has joined #openstack-meeting20:23
dhellmannfungi : yeah, we'll have to talk about that at some point soon, I think.20:23
ttxok, approving now, and deferring taht discussion for when lifeless and mordred are here at the same time20:23
ttxdone20:24
ttx#topic Applying Tacker for Big Tent20:24
*** openstack changes topic to "Applying Tacker for Big Tent (Meeting topic: tc)"20:24
ttx#link https://review.openstack.org/27641720:24
ttxRound 3... As I said in the meeting reminder, would be good if we could come to a final decision here20:25
ttxAll stated objections hinge on whether we trust Tacker can become a generally-useful OpenStack glue service rather than an NFV-infeodated purpose-built narrow application20:25
ttxWe can either trust that they will become that and approve them now20:25
ttxOr we can apply caution and ask that they demonstrate being generally-useful first, and delay the application20:25
ttx(or assert that they can't become that and reject them outright)20:25
ttxI'm slightly leaning on the "trusting" side because I fear the catch-22 (not being able to truly be generally useful until it's officially adopted)20:26
ttxThat said, the lack of TC member votes and enthusiasm around it should push us to caution20:26
mesteryI think we should in general lean to trust20:26
ttxStill missing 6 votes, current expressed votes lean towards including it20:26
mesterySo I agree with you ttx20:26
*** jorge_munoz has joined #openstack-meeting20:26
flaper87I'm on the trusting side. We've applied the same logic on other projects and we can evaluate again later20:26
annegentl_generally trust as well20:27
jaypipesI have not changed my mind on Tacker. I continue to see it as a purpose-built application for telco that consumes a variety of OpenStack APIs and services.20:27
dhellmannI'm OK with trusting them, but would like to understand what it means if they don't?20:27
dtroyerI think they have shown good intentions and practice, I think we can trust the team so far20:27
dtroyerBut I am still not certain this needs to be an OpenStack project.  It looks like an application layer to me.20:27
ttxmissing lifeless, mordred, dtroyer, jeblair, sdague, dhellmann20:27
*** pabelanger has left #openstack-meeting20:27
mordredyah. you are missing me20:28
ttxmordred: I do.20:28
annegentl_dtroyer: I feel like that's the case for trove then too20:28
dhellmanndo we set a time-frame? do we revisit this at some point?20:28
russellbit sounds like we should have a more general conversation about where we'd like to draw an upper scope bound20:28
*** clarkb has joined #openstack-meeting20:28
mordredI'm having trouble developing enough of an opinion on this to vote, tbh20:28
russellband write that down20:28
annegentl_russellb: yeah20:28
dhellmannrussellb : ++20:28
dtroyerannegentl_: maybe?  although Trove is more general.20:28
russellbbecause other than that, this is fine to me20:28
sdaguemordred: same20:28
annegentl_I'd like to separate that discussion about scopes/bounds from this review though.20:28
mordredhere are my thoughts, in no particular order20:28
ttxmordred: and I feel bad for voting as well. I have not nearly the same conviction as jaypipes has, yet my vote carries the same weight20:28
ttxand yet we need to, that's what we were elected for20:29
mordreda) in the big tent, I care most about humans who are like us doing development on things kind of like we do development on things20:29
mordredI don't particularly pass a lot of judgement on the validity of the thing itself20:29
* jeblair expands voting scale 10x for ttx to register a 1/10 vote20:29
bswartz+1 (with conviction) ?20:29
jaypipesttx: the weight of one's conviction has never been a good indicator of correctness :)20:29
ttx+020:29
*** KuDeMi has quit IRC20:29
mordredb) there is obviously an upper bound where things are just apps on top of openstack ... but I'm not sure if I have a good basis to judge that at th emoment20:29
*** akuznetsov has quit IRC20:29
russellbi've tried to balance out jaypipes' conviction with equal and opposite conviction, to make it totally unclear where to go next20:30
annegentl_jaypipes: heh20:30
jeblairrussellb: my hero20:30
mesteryheh20:30
dhellmannrussellb : helping!20:30
ttxrussellb: and then I summarized it with plenty of doubts and registered my +020:30
russellbthis is in an upper bound grey area, but it's far from alone there20:31
ttxrecipe for success and quick decision20:31
mordredc) I would like to do things to help our opnfv friends20:31
russellbIMO..20:31
russellbttx: :)20:31
*** adiantum has joined #openstack-meeting20:31
russellb¯\_(ツ)_/¯20:31
mesterymordred: teamwork!20:31
*** sdake has quit IRC20:31
*** _nadya_ has quit IRC20:31
ttxwe can totally decide that we need to think about it a lot more and defer the decision to next cycle20:31
mordredso, I thinkn I'm leaning towards a yes20:31
mordredlargely because I think that to reject something from the big tent I need to have a specific reason for the no20:32
ttxwe can also say yes but with the damocles sword of being removed based on that future discussion on scope20:32
russellbi'd propose yes for now, with an increased priority for discussing scope20:32
*** iyamahat has joined #openstack-meeting20:32
markmcclainI still think caution is warranted and we should defer... would give team time to implement the integrations they've committed to20:32
russellband an understanding that we may revisit the projects in the grey area based on the outcome20:32
mesteryrussellb: +120:32
dtroyerrussellb: that is to me a reason to either defer or decide no20:32
jaypipesI'm not at ALL against helping out our OPNFV friends. I'm just saying I don't believe a purpose-built Telco MANO application "is OpenStack" and furthers the mission of OpenStack to be the ubiquitous cloud computing infrastructure for private and public clouds.20:32
*** ivar-lazzaro has quit IRC20:33
* flaper87 will learn all the acronyms before this discussion ends... promised!20:33
ttxrussellb: "provisionally approved pending further discussion on scope" ?20:33
jeblairmordred's *rousing* speech seems to have gathered a few votes20:33
*** hashar has quit IRC20:33
sdagueI'm formally abstaining20:34
*** austin81 has joined #openstack-meeting20:34
mesteryI tend to agree with mordred that under the big tent I'm not seeing how I'd vote no on this one.20:34
ttxremember Donald Trump will soon be POTUS and the end of the world is near anyway20:34
dougwigThis bike shed is starting to look like a psychedelic barber pole.  That was lit on fire.20:34
sdagueI did register it as such20:34
anteayattx: cory booker is in the wings20:34
anteayattx: I have hope for him post trump20:34
mordredjaypipes: I think that if it helps NFV folks use openstack as their cloud, then it helps that. I do not know if it will help that, but I do not think it will explicitly hurt that20:34
*** tongli has quit IRC20:35
mordredjaypipes: so worst case it seems to hurt no more than any of the other margianlly helpful things we have, and best case maybe it helps a little?20:35
russellbmordred: that's my feeling20:35
mestery8 rollcall +1 votes now20:35
ttxOK, we have 8 votes yes at this stage, probably because it's easier to say yes than no.20:35
rockygmordred:  ++ makes ubiquitous openstack more ubiquitous20:35
mesteryttx: Isn't that the big tent's premise?20:35
ttxI'm fine with making it clear this is provisional approval20:35
ttxpending more discussion20:35
mesteryttx: Have we done a provisional approval before?20:35
ttxno20:36
mesteryOK20:36
ttxall approvals are proviosnal20:36
russellbwelcome to big tent era20:36
mesterylol20:36
mesteryTrue20:36
ttxit's just that we need to psychologically prepare projects to be kicked out20:36
*** myoung|mobile has quit IRC20:36
ttxI have my list20:36
jaypipesrockyg: or does it make NFV architecture and ETSI more ubiquitous?20:36
rockygjaypipes, Both?20:36
ttxsome projects are going horribly wrong and should definitely not be openstack20:37
jaypipesrockyg: one is not the other20:37
russellbthese folks are rallying around openstack, and i think we should be supporting that20:37
jaypipesrockyg: and it is that equivocy that I see as dangerous.20:37
markmcclainrussellb: but they're rallying around openstack on their terms20:37
mesteryRight, this makes openstack AND NFV/ETSI more ubiquitous IMHO20:37
ttxso we might not have kicked out anyone but it may happen. Especially now that we don't even have to rename the repos20:37
russellbmarkmcclain: huh?20:37
anteayattx: so happy to hear you say that20:37
jaypipesrockyg: the whole-hog consumption of OPenStack by the telco industry consortium is a real danger.20:37
* dhellmann can't wait to see ttx's list20:37
flaper87dhellmann: ++20:38
rockygjaypipes, very true.20:38
*** e0ne has joined #openstack-meeting20:38
*** penick has quit IRC20:38
ttxdhellmann: projects without an install guide are up there on my list20:38
sdaguettx: if it's not tested it's broken?20:38
dhellmannttx: ++20:38
ttxanyway, back on topic20:38
flaper87should we move on? I think there are enough votes to make a decision20:39
mesteryflaper87: ++20:39
markmcclainrussellb: basically what japypipes said... telcos want a very specific vision for OpenStack20:39
*** akamyshnikova has quit IRC20:39
ttxdtroyer: you should register your vote as RollCall20:39
jaypipesrockyg: if you don't see the danger that a single industry driving feature requests and product direction is, please have a chat with any nova core contributor about how NUMA, CPU pinning, SR-IOV and PCI functionality has gone.20:39
rockygjaypipes, can enterprise world adoption help balance the scales?20:39
russellbmarkmcclain: everyone has a vision20:39
dtroyerttx: thanks, done20:39
russellbanyway, moving on20:39
*** yamahata has joined #openstack-meeting20:39
*** redixin has left #openstack-meeting20:40
ttx8 vs. 3, one abstain20:40
*** myoung|mobile has joined #openstack-meeting20:40
ttxI think that means yes20:40
flaper87it's missing lifeless' vote but that won't change the result20:40
flaper87Unless lifeless convinces all +1's to be -1's20:41
ttxAlthough I agree with dtroyer's point. We are creating a larger grey mess we'll have to fix one day20:41
flaper87:D20:41
flaper87I think it's fair to say we'll revisit that grey mess in Newton20:41
flaper87why not? Or every cycle20:41
ttxI think revisiting that grey mess should be our priority in Newton20:42
*** francois1 has quit IRC20:42
mesteryttx: ++20:42
flaper87ttx: I'd agree with that20:42
mesterySpring cleaning20:42
flaper87:)20:42
ttxWe had two grey things being submitted recently20:42
russellbfine with me.20:42
*** merooney has joined #openstack-meeting20:42
ttxpreviously that was easier20:42
annegentl_grey matter for grey mess20:42
*** maishsk_ has joined #openstack-meeting20:42
russellbi'm sure we'll have plenty to argue around that20:42
ttxalright, closing the vote now20:42
*** iyamahat has quit IRC20:43
*** maishsk has quit IRC20:43
*** sdake has joined #openstack-meeting20:43
*** maishsk_ is now known as maishsk20:43
ttxIt is in20:43
ttx#topic Open discussion20:43
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:43
ttx* OpenStack CI resources vs. project growth (sdague)20:43
ttxsdague: floor is yours20:43
*** pcaruana has joined #openstack-meeting20:44
sdaguesure, this is something I wanted to bring up in looking at the delays and turn around time we're hitting as we hit milestones20:44
sdaguewe've got project growth20:44
sdaguegrowth of testing on projects20:44
sdagueand are actually currently down on cloud resources from the last 3 releases20:44
sdagueand while that last one may get addressed, I think the growth is always going to be pushing boundaries20:45
sdaguefor instance, there was a nodepool issue over the weekend, which basically put an 8 hour delay into everything yesterday until it could grind overnight20:45
annegentl_sdague: so so true20:45
*** roxanaghe has quit IRC20:45
annegentl_for other cross project concerns also20:45
ttxannegentl_: I think infra is where the growth is creating the most impact though20:46
dhellmannwe've even been hampered a bit with releases because of the check queue depth20:46
sdagueso any hiccup in the system can trigger a cascade that taks a couple of days to clear20:46
annegentl_ttx: yeah except for lack of install guides will cause longer-term delay in adoption. CI resources are easier to measure direct hit20:46
sdagueI think it's too late to address anything for mitaka, but I wanted to get a conversation going around this20:47
dhellmannsdague : are you building up to a proposal, or just starting the conversation?20:47
*** e0ne has quit IRC20:47
fungiyeah, the real shame is that the nodepool issue was addressed hours before we got into peak usage. it could have been far worse if it were just a little later in the day20:47
annegentl_not saying one's more "valuable" but that one's easier to visualize on a timeline20:47
*** xinwu has joined #openstack-meeting20:47
sdaguedhellmann: just the conversation20:47
ttxannegentl_: sure, "most visible impact"20:47
*** yamahata has quit IRC20:47
ttxsdague: so... solutions include: more test hosts, less tests/project, less projects20:48
ttxany other solution ?20:48
sdaguemore guidance on use of test resources?20:48
fungior finding a way to deprioritize jobs for some projects and prioritize others20:48
sdagueright, prioritization on peaks20:48
sdaguethat's a 5th thing20:48
jeblairfungi: interestingly we looked at that a long time ago, and the use of ci resources by non "core" projects was almost negligible20:48
ttxFOr example, non-voting jobs seem to be completely ignored by most, yet consume a lot of resources20:48
dhellmannyeah, I was thinking if we reserved CI for official projects during peak times that might help, but only during those times and we'd move the peaks from other projects to other times20:48
jeblairi actually doubt it is that much different now20:49
dhellmannjeblair : does that still hold?20:49
fungigearman hampers us there a bit since the protocol has a designed-in 3-level precedence implementation20:49
annegentl_one question I have is, has anyone measured 3rd party impact20:49
*** hashar has joined #openstack-meeting20:49
mordredannegentl_: what do you mean20:49
mordred?20:49
annegentl_and would more 3rd party testing help with resources?20:49
anteayaannegentl_: what impact20:49
sdagueso, again, I think we come back to step 1 - do we have a real problem?20:49
anteayahow would you invision?20:49
jeblairdhellmann: my gut says it mostly still holds.  but actual measurement might be useful.  :)20:49
fungijeblair: yeah, i suspect not much has changed there but it would be interesting to see updated numbers20:49
dhellmannjeblair, fungi : yeah20:50
anteayaannegentl_: the testing is different, proprietary vs open20:50
annegentl_anteaya: wondering if we look at all testing as a pie, is 3rd party testing able to take on more of a large pie?20:50
*** gyee has joined #openstack-meeting20:50
anteayaonly to benefit themselves20:50
annegentl_anteaya: ok20:50
anteayathird party testing has no benefit to openstack trunk code20:50
ttxsdague: I think we do have a problem yes. We could ramp up CI resources to accommodate growth before, and we are struggling to do that currently20:50
jeblairsdague: i think this is timely -- we are basically at capacity right now (where my definition of at capacity means our ability to finish 24h worth of jobs in 24h)20:50
jbrycewhen we have these periodic bottlenecks, how under-resourced are we? (ballpark)20:50
*** vijendar has quit IRC20:51
fungiannegentl_: anteaya: right, the "third-party" solution is additional parties with available cloud resources donating quota to us so we can use that to run first-party (upstream) jobs there20:51
jbryce10%? 50%? 100%?20:51
annegentl_jeblair: time machine?20:51
ttxI would say 50%, but fungi should know better20:51
sdaguejeblair: right, I think we have different definitions of at capacity, because if you can't turn around results on your patch in a timely manner it hampers the ability to address issues only seen in our gate20:52
anteayajbryce: we would use any resources given to us to their maximum quota20:52
russellband do you think paying some subset of providers for extra capacity would hurt our ability to get resources donated?20:52
mordredjbryce: we were hitting capacity before HP sunset20:52
sdaguemordred: we were, it's definitely a lot more cramped since then though20:52
fungijbryce: it's hard to put a hard number on, because the impact is "how much longer does it take to get certain kinds ofg job results"20:52
jbryceanteaya: i understand that, but i’m wondering at what level of additional resources we would not be hitting capacity20:52
mordredjbryce: so, I'd say we're at least under capacity by 600 VMs at peak times - but probably more. we are obviously working on finding more capacity20:52
jbrycemordred: ok cool20:52
sdaguemordred: yeh, that's about as good an estimate as any20:52
jbrycehow predictable is the arrival of peak times? it seems at least some of them we can see coming, eh?20:53
fungiwe have graphs20:53
anteayajbryce: every milestone and feature freeze20:53
fungithat can be trended fairly accurately20:53
jeblairwe can define it more precisely if we agree on a service expectation (jobs report in 24h?  8h?  2h?)20:53
anteayayou can set a watch by it20:53
*** vijendar has joined #openstack-meeting20:53
anteayajeblair: right, we have never set service expecations20:53
* jbryce is mulling over some way to get temporary quota increases from providers within an agreed upon timeframe20:53
russellbjbryce: i think it's the kind of thing worth spending $ on20:53
sdaguejeblair: right, maybe that's part of the conversation20:53
anteayawe just live with what we have and communicate it20:54
jbryceyeah exactly20:54
flaper87russellb: ++20:54
jeblaircurrently, lacking any other metric, we've been going by 24h20:54
sdaguebecause once we get past 2 hrs turn around, it definitely negative impacts development20:54
annegentl_might as well do 24 hours, not sure smaller increments is meaningful for global work20:54
fungithere are daily, weekly and release cycle patterns which each have their own envelope20:54
annegentl_any link to graphs?20:54
dhellmannjbryce: it would be useful to have more capacity around the 2nd and 3rd milestones, and during the RC1 period.20:54
anteayasdague: 2 hours turn around for what?20:54
anteayafor the gate?20:54
sdagueespecially with global teams where you are only getting a couple of hrs of overlap to solve things20:54
sdagueanteaya: check queue20:54
anteayaokay check queue20:55
*** piet has joined #openstack-meeting20:55
markmcclainwhen we have peak demand can we not automatically disable non-voting jobs? for instance neutron 8 of 18 and manilla 10 of 16 are non voting20:55
*** e0ne has joined #openstack-meeting20:55
anteayamarkmcclain: every project uses non-voting jobs to mean different things20:55
fungi#link http://grafana.openstack.org/dashboard/db/zuul-status the zuul job queue is probably the best indicator of demand20:55
dhellmannthat seems like a high % even during non-peak times20:55
dhellmannboth to20:55
dhellmanndo20:55
*** julim has joined #openstack-meeting20:55
anteayadespite what we would like, folks interpret them differently within their group20:55
jeblairmarkmcclain: i guess the question is -- are non-voting jobs valuable?  if they are, we should run them; if they are not, we should not run them in check.20:56
*** merooney has quit IRC20:56
anteayanon-voting is supposed to be a step towards voting, but that isn't the reality for some20:56
ttxsome/most20:56
sdagueanyway, this was an intent not to solve the issue right here, because I think seeing our growth curves it's an important conversation to be having over the next cycle, with the TC folks being part of it20:56
*** sdake has quit IRC20:56
ttxsdague: and thanks for raising it20:56
*** amrith is now known as _amrith_20:56
annegentl_sdague: yep thanks20:56
dhellmannanteaya : do you have any idea what % of the jobs we run are non-voting overall?20:56
jeblairit's also worth noting that we have recently onlined some more clouds, and have others in the pipelin20:57
*** hichihara has quit IRC20:57
sdaguejeblair: yep, which definitely helps20:57
fungialso prioritization is hard to tweak, because as soon as we prioritize one thing (say, gating) then we discover how much people relied on faster turn-around on others (check results, post-merge publication)20:57
anteayadhellmann: I do not, but I bet AJeager would have those numbers quickly20:57
mordredsdague: I love everyone on the TC - but do you have ideas of which ways are you thinking the TC can be helpful?20:57
anteayadhellmann: can I get back to you on that?20:57
jeblairincluding infra-cloud (which ran 1 some jobs last week!)20:57
dhellmannanteaya : sure, I expect this is going to be a topic of discussion for a while20:57
sdaguebut our project and test growth rates seem to be accellerating faster than that20:57
anteayadhellmann: I'll take that as an action item20:57
dhellmannmordred : I expect we're going to need to set some usage policies, don't you?20:58
sdaguemordred: honestly, this feels like a more important issue to get a hold of than new tags. Maybe that's just me :)20:58
dhellmannsdague : no, I'm on board with that, too20:58
*** maishsk has quit IRC20:58
mordredsdague: I agree it's super important - but I also just want to make sure we have an idea of how we think productive looks. perhaps usage policies for sure20:58
flaper87sdague: dhellmann count me in20:58
*** sigmavirus24 is now known as sigmavirus24_awa20:58
*** sigmavirus24_awa is now known as sigmavirus2420:58
ttxNo more time to discuss stale reviews, we can do that next week20:59
sdaguemordred: usage policies and norms20:59
sdagueand leadership back in projects we're a part of20:59
dhellmannit would be interesting to look at things like whether we could combine any of the shorter jobs so they run together, in parallel with the longer jobs, to use fewer nodes20:59
ttxSmall heads-up, please review project team guide changes ! We have a number of changes stuck in that queue20:59
*** e0ne has quit IRC20:59
ttx#link https://review.openstack.org/#/q/status:open+project:openstack/project-team-guide20:59
mordredsdague: k. that's also helpful in infra being able to prepare/provide input data that can help those20:59
sdagueyep, for sure20:59
mordredlike, depending on the quality of te discussion, different reports and data might be useful20:59
*** sdake has joined #openstack-meeting20:59
dhellmannwill this be the subject of an infra session at the summit?21:00
dhellmannor cross-project?21:00
rockyg++21:00
*** jckasper_ has quit IRC21:00
jeblairdhellmann: that suggestion feels more like a technical infra suggestion than a tc topic?21:00
flaper87jeblair: ++21:00
jeblairdhellmann: (your combining jobs idea)21:00
ttxok we are out of time21:00
ttxThanks everyone21:00
*** jckasper has joined #openstack-meeting21:00
*** haomaiwang has quit IRC21:01
flaper87o/21:01
dhellmannjeblair : yeah, definitely21:01
flaper87cheers21:01
flaper87tty next week21:01
mesterythanks ttx21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Mar  1 21:01:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-01-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-01-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-01-20.01.log.html21:01
russellbbye all21:01
thingeereminder cross-project meeting is SKIPPED this week http://lists.openstack.org/pipermail/openstack-dev/2016-March/087871.html21:01
*** haomaiwang has joined #openstack-meeting21:01
*** maishsk has joined #openstack-meeting21:02
*** cdub has quit IRC21:02
dhellmannthingee : thanks for the reminder, I couldn't find that email21:02
*** cdent has left #openstack-meeting21:03
*** mrmartin has quit IRC21:03
*** sneti has quit IRC21:04
*** IvanNieto has joined #openstack-meeting21:04
*** weshay has joined #openstack-meeting21:04
*** natarajk has left #openstack-meeting21:04
*** jckasper has quit IRC21:05
*** cdub has joined #openstack-meeting21:05
*** IvanNieto has quit IRC21:06
*** raildo is now known as raildo-afk21:07
*** david-lyle has quit IRC21:08
*** sripriya_ has left #openstack-meeting21:09
*** rromans has left #openstack-meeting21:12
*** bobh has quit IRC21:13
*** korzen has joined #openstack-meeting21:13
*** jdurgin has quit IRC21:15
*** dfflanders has quit IRC21:15
*** neelashah has quit IRC21:17
*** david-lyle has joined #openstack-meeting21:17
*** macsz has quit IRC21:20
lifelessflaper87: ttx: so fwiw I'm -1 at this point :/21:21
*** hdaniel has joined #openstack-meeting21:22
ttxlifeless: on Tacker ? oh well, still a majority I guess21:24
lifelessyah21:25
*** annegentl_ has quit IRC21:25
*** jmckind has quit IRC21:26
*** jichen has quit IRC21:28
*** jmckind has joined #openstack-meeting21:28
*** annegentl_ has joined #openstack-meeting21:28
*** dims_ has joined #openstack-meeting21:31
*** sridhar_ram has joined #openstack-meeting21:32
*** korzen has quit IRC21:32
*** yamahata has joined #openstack-meeting21:32
*** jorge_munoz has quit IRC21:33
*** jckasper has joined #openstack-meeting21:33
*** dims has quit IRC21:33
*** sridhar_ram1 has quit IRC21:33
*** ivar-lazzaro has joined #openstack-meeting21:34
*** mmandel has joined #openstack-meeting21:36
*** jdurgin has joined #openstack-meeting21:38
*** ivar-lazzaro has quit IRC21:39
*** derekh has joined #openstack-meeting21:41
*** Sukhdev has quit IRC21:43
*** baoli has joined #openstack-meeting21:43
*** jckasper has quit IRC21:44
*** jckasper has joined #openstack-meeting21:44
*** baoli_ has joined #openstack-meeting21:44
*** adahms has joined #openstack-meeting21:45
*** neelashah has joined #openstack-meeting21:46
*** Leom_ has quit IRC21:47
*** luzC has quit IRC21:47
*** maishsk has quit IRC21:47
*** adahms has quit IRC21:48
*** baoli has quit IRC21:48
*** jckasper has quit IRC21:49
*** ivar-lazzaro has joined #openstack-meeting21:50
*** sdague has quit IRC21:50
*** ivar-lazzaro has quit IRC21:50
*** ivar-lazzaro has joined #openstack-meeting21:51
*** novas0x2a|laptop has joined #openstack-meeting21:51
*** fawadkhaliq has quit IRC21:54
*** austin81 has left #openstack-meeting21:55
*** annegentl_ has quit IRC21:56
*** annegentl_ has joined #openstack-meeting21:57
*** hdaniel has quit IRC21:59
*** ivar-lazzaro has quit IRC22:00
*** haomaiwang has quit IRC22:01
*** pcaruana has quit IRC22:01
*** ivar-lazzaro has joined #openstack-meeting22:01
*** haomaiwang has joined #openstack-meeting22:01
*** dims_ has quit IRC22:02
*** ivar-lazzaro has quit IRC22:03
*** fawadkhaliq has joined #openstack-meeting22:04
*** Sukhdev has joined #openstack-meeting22:04
*** knikolla has quit IRC22:04
*** JRobinson__ has joined #openstack-meeting22:06
*** ivar-lazzaro has joined #openstack-meeting22:07
*** dprince has quit IRC22:08
*** banix has quit IRC22:08
*** rtheis has quit IRC22:09
*** thorst_ has quit IRC22:09
*** ijw has joined #openstack-meeting22:09
*** dims has joined #openstack-meeting22:10
*** jckasper has joined #openstack-meeting22:10
*** francois has joined #openstack-meeting22:11
*** vhoward has quit IRC22:13
*** dkranz has joined #openstack-meeting22:13
*** sridhar_ram has quit IRC22:16
*** penick has joined #openstack-meeting22:16
*** jorge_munoz has joined #openstack-meeting22:18
*** sarob has quit IRC22:18
*** Sukhdev has quit IRC22:19
*** gcb has quit IRC22:19
*** sridhar_ram has joined #openstack-meeting22:19
*** gcb has joined #openstack-meeting22:19
*** dimtruck is now known as zz_dimtruck22:20
*** lblanchard has quit IRC22:21
*** keedya has quit IRC22:21
*** timcline has joined #openstack-meeting22:23
*** achanda has quit IRC22:23
*** sarob has joined #openstack-meeting22:25
*** henrynash has joined #openstack-meeting22:27
*** sneti has joined #openstack-meeting22:27
*** sarob has quit IRC22:27
*** krtaylor has quit IRC22:27
*** david-lyle has quit IRC22:29
*** tsymanczyk has left #openstack-meeting22:30
*** yamahata has quit IRC22:30
*** vhoward has joined #openstack-meeting22:31
*** annegentl_ has quit IRC22:32
*** Leo_ has joined #openstack-meeting22:33
*** Leom has joined #openstack-meeting22:34
*** prashantD_ has joined #openstack-meeting22:35
*** prashantD has quit IRC22:35
*** achanda has joined #openstack-meeting22:36
*** angdraug has quit IRC22:36
*** vijendar has quit IRC22:36
*** Leo_ has quit IRC22:38
*** hashar has quit IRC22:38
*** aysyd has quit IRC22:38
*** jckasper has quit IRC22:39
*** prashantD_ has quit IRC22:39
*** jckasper has joined #openstack-meeting22:40
*** jckasper has quit IRC22:41
*** jckasper has joined #openstack-meeting22:41
*** jtomasek has quit IRC22:41
*** luzC has joined #openstack-meeting22:42
*** piet has quit IRC22:43
*** annegentl_ has joined #openstack-meeting22:44
*** zz_dimtruck is now known as dimtruck22:45
*** spzala has joined #openstack-meeting22:46
*** amitgandhinz has quit IRC22:48
*** trozet has quit IRC22:49
*** neelashah has quit IRC22:51
*** dane_leblanc has quit IRC22:52
*** spzala has quit IRC22:54
*** baoli_ has quit IRC22:54
*** baoli has joined #openstack-meeting22:54
*** edtubill has quit IRC22:54
*** andymaier has quit IRC22:55
*** dims has quit IRC22:55
*** timcline has quit IRC22:56
*** delattec has quit IRC22:57
*** baoli has quit IRC22:58
*** baoli has joined #openstack-meeting22:59
*** whenry_ has quit IRC23:00
*** sc68cal has quit IRC23:00
*** delattec has joined #openstack-meeting23:00
*** baoli has quit IRC23:00
*** david-lyle has joined #openstack-meeting23:00
*** sridhar_ram has quit IRC23:00
*** dims has joined #openstack-meeting23:00
*** haomaiwang has quit IRC23:01
*** yassine__ has quit IRC23:01
*** baoli has joined #openstack-meeting23:01
*** haomaiwang has joined #openstack-meeting23:01
*** sridhar_ram has joined #openstack-meeting23:02
*** singhj has quit IRC23:03
*** ianw has quit IRC23:07
*** intr1nsic has quit IRC23:08
*** doug-fis_ has joined #openstack-meeting23:09
*** doug-fis_ has quit IRC23:09
*** doug-fis_ has joined #openstack-meeting23:09
*** MaxPC has quit IRC23:11
*** rfolco_ has quit IRC23:11
*** baoli has quit IRC23:11
*** zhurong has joined #openstack-meeting23:11
*** dmorita has joined #openstack-meeting23:12
*** doug-fish has quit IRC23:13
*** ivar-lazzaro has quit IRC23:13
*** mmandel has quit IRC23:13
*** ivar-lazzaro has joined #openstack-meeting23:13
*** zhurong has quit IRC23:14
*** doug-fis_ has quit IRC23:14
*** jmckind has quit IRC23:15
*** krtaylor has joined #openstack-meeting23:16
*** sheel has quit IRC23:17
*** Sukhdev has joined #openstack-meeting23:18
*** novas0x2a|lapto1 has joined #openstack-meeting23:19
*** novas0x2a|laptop has quit IRC23:19
*** salv-orl_ has joined #openstack-meeting23:19
*** jckasper has quit IRC23:20
*** jckasper has joined #openstack-meeting23:20
*** fzdarsky is now known as fzdarsky|afk23:22
*** salv-orlando has quit IRC23:22
*** sneti has quit IRC23:23
*** singhj has joined #openstack-meeting23:24
*** annegentl_ has quit IRC23:24
*** jckasper has quit IRC23:25
*** annegentl_ has joined #openstack-meeting23:25
*** singhj has quit IRC23:25
*** harshs has quit IRC23:26
*** jckasper has joined #openstack-meeting23:29
*** jorge_munoz has quit IRC23:29
*** annegentl_ has quit IRC23:30
*** lblanchard has joined #openstack-meeting23:30
*** merooney has joined #openstack-meeting23:30
*** reedip_ is now known as reedip23:31
*** azbiswas has quit IRC23:31
*** intr1nsic has joined #openstack-meeting23:32
*** azbiswas has joined #openstack-meeting23:32
*** darrenc is now known as darrenc_afk23:33
*** azbiswas_ has joined #openstack-meeting23:34
*** azbiswas has quit IRC23:36
*** harshs has joined #openstack-meeting23:37
*** rbak has quit IRC23:39
*** tochi has joined #openstack-meeting23:39
*** julen has quit IRC23:40
*** banix has joined #openstack-meeting23:40
*** david-lyle has quit IRC23:41
*** vhoward_ has joined #openstack-meeting23:41
*** iyamahat has joined #openstack-meeting23:41
*** Qiming has joined #openstack-meeting23:41
*** vhoward has quit IRC23:42
*** dimtruck is now known as zz_dimtruck23:44
*** annegentl_ has joined #openstack-meeting23:46
*** doug-fish has joined #openstack-meeting23:46
*** sdake has quit IRC23:47
*** doug-fish has quit IRC23:47
*** MaxPC has joined #openstack-meeting23:47
*** spotz is now known as spotz_zzz23:47
*** banix has quit IRC23:48
*** dkranz has quit IRC23:49
*** salv-orlando has joined #openstack-meeting23:50
*** salv-orlando has quit IRC23:50
*** salv-orl_ has quit IRC23:50
*** jckasper has quit IRC23:50
*** darrenc_afk is now known as darrenc23:50
*** salv-orlando has joined #openstack-meeting23:50
*** jckasper has joined #openstack-meeting23:51
*** iyamahat has quit IRC23:53
*** jckasper has quit IRC23:55
*** unicell has joined #openstack-meeting23:55
*** dmorita has quit IRC23:56
*** zzxwill has joined #openstack-meeting23:58
*** delattec has quit IRC23:59
*** harshs has left #openstack-meeting23:59

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