Tuesday, 2016-03-15

*** haomaiwang has quit IRC00:01
*** 5EXAAEA3R has joined #openstack-meeting00:01
*** banix has joined #openstack-meeting00:02
*** Sukhdev has quit IRC00:05
*** Sukhdev has joined #openstack-meeting00:05
*** Sukhdev has quit IRC00:06
*** maurosr has joined #openstack-meeting00:07
*** Sukhdev has joined #openstack-meeting00:07
qeasHi everyone, after a recent change to devstack I am getting this error when trying to install http://paste.openstack.org/show/490443/. Using the same local.conf that worked previously, any suggestions what's wrong here? Thanks00:08
*** angdraug has quit IRC00:08
samueldmqqeas: you should probably ask in #openstack-qa which is the channel where devstack things are discussed00:08
samueldmqqeas: this is a channel used for meetings00:09
qeassamueldmq: oops, sorry, thought I was in manila channel00:10
samueldmqqeas: np, good luck00:10
*** qeas has quit IRC00:10
*** kencjohnston has joined #openstack-meeting00:12
*** kencjohnston has quit IRC00:12
*** iyamahat has joined #openstack-meeting00:13
*** unicell1 has quit IRC00:17
*** unicell has joined #openstack-meeting00:17
*** eharney has quit IRC00:18
*** john-davidge has joined #openstack-meeting00:20
*** Swami has quit IRC00:22
*** garthb_ has quit IRC00:22
*** dims has joined #openstack-meeting00:23
*** ian_ott has joined #openstack-meeting00:25
*** kei_ has quit IRC00:26
*** thorst_ has quit IRC00:28
*** thorst_ has joined #openstack-meeting00:29
*** oomichi has quit IRC00:30
*** ian_ott has quit IRC00:31
*** docaedo has quit IRC00:31
*** mordred has quit IRC00:31
*** phschwartz has quit IRC00:31
*** oomichi has joined #openstack-meeting00:31
*** afazekas_ has quit IRC00:32
*** afazekas has joined #openstack-meeting00:32
*** phschwartz has joined #openstack-meeting00:32
*** dims has quit IRC00:32
*** mordred has joined #openstack-meeting00:32
*** docaedo has joined #openstack-meeting00:32
*** asingh has joined #openstack-meeting00:33
*** yamamoto_ has quit IRC00:34
*** thorst_ has quit IRC00:37
*** lpetrut has joined #openstack-meeting00:38
*** timcline has joined #openstack-meeting00:38
*** markvoelker has joined #openstack-meeting00:40
*** timcline has quit IRC00:42
*** lpetrut has quit IRC00:42
*** asingh has quit IRC00:44
*** azbiswas has quit IRC00:48
*** iyamahat has quit IRC00:49
*** toddjohn has joined #openstack-meeting00:52
*** iceyao has joined #openstack-meeting00:53
*** sdake has joined #openstack-meeting00:55
*** dneary has quit IRC00:55
*** thorst_ has joined #openstack-meeting00:56
*** dims has joined #openstack-meeting00:56
*** toddjohn has quit IRC00:56
*** iyamahat has joined #openstack-meeting00:56
*** hoangcx has joined #openstack-meeting00:57
*** dimtruck is now known as zz_dimtruck00:59
*** 5EXAAEA3R has quit IRC01:01
*** haomaiwang has joined #openstack-meeting01:01
*** haomaiwang has quit IRC01:04
*** sdake has quit IRC01:10
*** thorst_ has quit IRC01:12
*** zz_dimtruck is now known as dimtruck01:12
*** thorst_ has joined #openstack-meeting01:13
*** unicell has quit IRC01:13
*** unicell1 has joined #openstack-meeting01:13
*** markvoelker has quit IRC01:14
*** Sukhdev has quit IRC01:17
*** pvaneck has quit IRC01:18
*** thorst_ has quit IRC01:21
*** comay has quit IRC01:21
*** zhurong_ has joined #openstack-meeting01:21
*** yarkot_ has joined #openstack-meeting01:24
*** alekseyruban has quit IRC01:24
*** gongysh has quit IRC01:24
*** dmacpher has joined #openstack-meeting01:25
*** ian_ott has joined #openstack-meeting01:26
*** ian_ott has quit IRC01:31
*** yarkot_ has quit IRC01:33
*** zhhuabj has quit IRC01:33
*** tongli has quit IRC01:34
*** s3wong has quit IRC01:34
*** yamamoto_ has joined #openstack-meeting01:34
*** kencjohnston_ has joined #openstack-meeting01:36
*** iceyao has quit IRC01:37
*** cshahani has quit IRC01:38
*** timcline has joined #openstack-meeting01:39
*** zhurong_ has quit IRC01:39
*** cshahani has joined #openstack-meeting01:39
*** rfolco has joined #openstack-meeting01:40
*** zhurong_ has joined #openstack-meeting01:41
*** comay has joined #openstack-meeting01:41
*** kencjohnston has joined #openstack-meeting01:41
*** azbiswas has joined #openstack-meeting01:42
*** kencjohnston_ has quit IRC01:42
*** harshs has quit IRC01:42
*** baojg has joined #openstack-meeting01:43
*** yamamoto_ has quit IRC01:43
*** timcline has quit IRC01:43
*** azbiswas has quit IRC01:45
*** zhhuabj has joined #openstack-meeting01:45
*** azbiswas has joined #openstack-meeting01:45
*** amrith is now known as _amrith_01:49
*** haomaiwang has joined #openstack-meeting01:49
*** azbiswas has quit IRC01:50
*** haomaiwang has quit IRC01:50
*** haomaiwang has joined #openstack-meeting01:50
*** unicell1 has quit IRC01:54
*** rockyg has joined #openstack-meeting01:54
*** cshahani has quit IRC01:55
*** john-davidge has quit IRC01:55
*** IlyaG has quit IRC01:57
*** apoorvad has quit IRC01:58
rockygo/01:58
*** iyamahat has quit IRC01:59
*** mASTEROFBUGS has quit IRC02:00
*** haomaiwang has quit IRC02:01
*** piet has joined #openstack-meeting02:01
*** haomaiwang has joined #openstack-meeting02:01
*** salv-orlando has joined #openstack-meeting02:02
*** SumitNaiksatam has joined #openstack-meeting02:03
*** salv-orl_ has quit IRC02:04
*** tfukushima has joined #openstack-meeting02:05
*** john-davidge has joined #openstack-meeting02:05
*** piet has quit IRC02:06
*** piet has joined #openstack-meeting02:06
*** yamamoto has joined #openstack-meeting02:07
*** gongysh has joined #openstack-meeting02:09
*** kencjohnston has quit IRC02:10
*** kencjohnston has joined #openstack-meeting02:10
*** fawadkhaliq has quit IRC02:12
*** novas0x2a|laptop has quit IRC02:13
*** ljxiash has joined #openstack-meeting02:13
*** fzdarsky_ has joined #openstack-meeting02:14
*** fzdarsky|afk has quit IRC02:18
*** ozstacker has quit IRC02:19
*** zhhuabj has quit IRC02:21
*** ivar-lazzaro has quit IRC02:22
*** yamamoto has quit IRC02:27
*** ian_ott has joined #openstack-meeting02:27
*** cshahani has joined #openstack-meeting02:28
*** ryu25 has joined #openstack-meeting02:30
*** ian_ott has quit IRC02:31
*** rockyg has quit IRC02:31
*** dmorita has quit IRC02:33
*** tellesnobrega_af is now known as tellesnobrega02:33
*** dmorita has joined #openstack-meeting02:34
*** cody-somerville has joined #openstack-meeting02:35
*** rfolco has quit IRC02:35
*** zhhuabj has joined #openstack-meeting02:36
*** asingh has joined #openstack-meeting02:37
*** jckasper has quit IRC02:38
*** dims has quit IRC02:38
*** armax has quit IRC02:38
*** dmorita has quit IRC02:39
*** cj has joined #openstack-meeting02:39
*** cartik has joined #openstack-meeting02:39
*** jckasper has joined #openstack-meeting02:39
*** dimtruck is now known as zz_dimtruck02:39
*** jckasper has quit IRC02:39
*** jckasper has joined #openstack-meeting02:40
*** timcline has joined #openstack-meeting02:40
*** iyamahat has joined #openstack-meeting02:40
*** gongysh has quit IRC02:41
*** bryan_att has quit IRC02:42
*** timcline has quit IRC02:44
*** xinwu has quit IRC02:46
*** neelashah has joined #openstack-meeting02:48
*** john-davidge has quit IRC02:48
*** kencjohnston_ has joined #openstack-meeting02:48
*** kencjohnston_ has quit IRC02:49
*** IlyaG has joined #openstack-meeting02:50
*** julenl has quit IRC02:51
*** julenl has joined #openstack-meeting02:51
*** unicell has joined #openstack-meeting02:54
*** cartik has quit IRC02:56
*** baoli_ has joined #openstack-meeting02:57
*** asselin_ has joined #openstack-meeting02:57
*** armax has joined #openstack-meeting02:58
*** azbiswas has joined #openstack-meeting03:00
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-meeting03:01
*** yamahata has joined #openstack-meeting03:02
*** doug-fish has joined #openstack-meeting03:03
*** IlyaG has quit IRC03:03
*** gcb has joined #openstack-meeting03:06
*** fawadkhaliq has joined #openstack-meeting03:06
*** irenab_ has joined #openstack-meeting03:06
*** jckasper has quit IRC03:06
*** irenab has quit IRC03:08
*** irenab_ is now known as irenab03:08
*** asingh has quit IRC03:08
*** yamamoto has joined #openstack-meeting03:09
*** merooney has quit IRC03:09
*** asingh has joined #openstack-meeting03:09
*** ajiang has left #openstack-meeting03:10
*** azbiswas has quit IRC03:11
*** markvoelker has joined #openstack-meeting03:11
*** esker has quit IRC03:13
*** mtanino has quit IRC03:17
*** dfflanders has joined #openstack-meeting03:18
*** ljxiash has quit IRC03:22
*** xiaohhui has quit IRC03:23
*** asettle has quit IRC03:23
*** lblanchard has quit IRC03:24
*** xiaohhui has joined #openstack-meeting03:26
*** ljxiash has joined #openstack-meeting03:26
*** erlon has quit IRC03:27
*** xinwu has joined #openstack-meeting03:31
*** tochi has quit IRC03:33
*** kaisers has quit IRC03:36
*** haukebruno has quit IRC03:38
*** links has joined #openstack-meeting03:38
*** haukebruno has joined #openstack-meeting03:40
*** timcline has joined #openstack-meeting03:40
*** tellesnobrega is now known as tellesnobrega_af03:41
*** markvoelker has quit IRC03:44
*** aswadr_ has joined #openstack-meeting03:44
*** jckasper has joined #openstack-meeting03:44
*** timcline has quit IRC03:45
*** epico has joined #openstack-meeting03:45
*** balajiiyer has joined #openstack-meeting03:48
*** kaisers has joined #openstack-meeting03:50
*** jckasper has quit IRC03:53
*** jckasper has joined #openstack-meeting03:53
*** balajiiyer has quit IRC03:55
*** ayoung has quit IRC03:57
*** haukebruno has quit IRC03:57
*** jckasper has quit IRC03:58
*** haomaiwang has quit IRC04:01
*** tochi has joined #openstack-meeting04:01
*** haomaiwang has joined #openstack-meeting04:01
*** neelashah has quit IRC04:01
*** IlyaG has joined #openstack-meeting04:04
*** keedya has quit IRC04:05
*** sdake has joined #openstack-meeting04:06
*** jckasper has joined #openstack-meeting04:07
*** john-davidge has joined #openstack-meeting04:08
*** ajmiller has joined #openstack-meeting04:08
*** sdake_ has joined #openstack-meeting04:09
*** IlyaG has quit IRC04:09
*** ajmiller_ has joined #openstack-meeting04:09
*** JRobinson__ is now known as JRobinson__afk04:10
*** sdake has quit IRC04:11
*** john-davidge has quit IRC04:11
*** cartik has joined #openstack-meeting04:13
*** ajmiller has quit IRC04:13
*** tfukushima has quit IRC04:14
*** iGene has joined #openstack-meeting04:14
*** esheffield has quit IRC04:15
*** azbiswas has joined #openstack-meeting04:15
*** amotoki has joined #openstack-meeting04:17
*** piet has quit IRC04:19
*** sdake_ has quit IRC04:19
*** piet has joined #openstack-meeting04:19
*** jckasper has quit IRC04:20
*** armax has quit IRC04:20
*** jckasper has joined #openstack-meeting04:20
*** ajmiller_ has quit IRC04:21
*** jckasper has quit IRC04:25
*** armax has joined #openstack-meeting04:25
*** ian_ott has joined #openstack-meeting04:29
*** piet has quit IRC04:30
*** piet has joined #openstack-meeting04:31
*** cartik has quit IRC04:32
*** asingh has quit IRC04:32
*** ian_ott has quit IRC04:33
*** piet has quit IRC04:44
*** Sukhdev has joined #openstack-meeting04:45
*** iyamahat has quit IRC04:46
*** hichihara has joined #openstack-meeting04:47
*** banix has quit IRC04:47
*** sridharg has joined #openstack-meeting04:49
*** baoli_ has quit IRC04:50
*** azbiswas_ has joined #openstack-meeting04:52
*** piet has joined #openstack-meeting04:53
*** novas0x2a|laptop has joined #openstack-meeting04:55
*** azbiswas has quit IRC04:56
*** ljxiash has quit IRC04:56
*** ljxiash has joined #openstack-meeting04:57
*** Ravikiran_K has quit IRC04:58
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** ljxiash has quit IRC05:01
*** JRobinson__afk is now known as JRobinson__05:01
*** singhj has joined #openstack-meeting05:03
*** singhj has quit IRC05:09
*** banix has joined #openstack-meeting05:12
*** iyamahat has joined #openstack-meeting05:14
*** singhj has joined #openstack-meeting05:15
*** sdake has joined #openstack-meeting05:15
*** amotoki has quit IRC05:21
*** roxanagh_ has quit IRC05:23
*** roxanagh_ has joined #openstack-meeting05:24
*** sridharg has quit IRC05:27
*** Poornima has joined #openstack-meeting05:27
*** armax has quit IRC05:29
*** ian_ott has joined #openstack-meeting05:30
*** amotoki has joined #openstack-meeting05:31
*** singhj has quit IRC05:33
*** askb has joined #openstack-meeting05:33
*** askb has quit IRC05:33
*** sdake has quit IRC05:33
*** askb has joined #openstack-meeting05:34
*** ian_ott has quit IRC05:35
*** amotoki has quit IRC05:35
*** _nadya_ has joined #openstack-meeting05:37
*** roxanagh_ has quit IRC05:40
*** roxanagh_ has joined #openstack-meeting05:41
*** markvoelker has joined #openstack-meeting05:41
*** anilvenkata has joined #openstack-meeting05:42
*** Sukhdev has quit IRC05:43
*** piet has quit IRC05:44
*** roxanagh_ has quit IRC05:45
*** amotoki has joined #openstack-meeting05:47
*** armax has joined #openstack-meeting05:48
*** ndipanov has quit IRC05:49
*** JRobinson__ has quit IRC05:52
*** salv-orl_ has joined #openstack-meeting05:54
*** ljxiash has joined #openstack-meeting05:54
*** amotoki has quit IRC05:55
*** toddjohn has joined #openstack-meeting05:57
*** salv-orlando has quit IRC05:57
*** haomaiwang has quit IRC06:01
*** toddjohn has quit IRC06:01
*** haomaiwang has joined #openstack-meeting06:01
*** _nadya_ has quit IRC06:03
*** banix has quit IRC06:04
*** akuznetsov has joined #openstack-meeting06:07
*** Daisy has joined #openstack-meeting06:07
*** sridharg has joined #openstack-meeting06:09
*** Daisy has quit IRC06:10
*** Daisy has joined #openstack-meeting06:11
*** wojdev has joined #openstack-meeting06:11
*** hoangcx has quit IRC06:11
*** Ravikiran_K has joined #openstack-meeting06:13
*** wojdev has quit IRC06:14
*** markvoelker has quit IRC06:14
*** hoangcx has joined #openstack-meeting06:15
*** Daisy_ has joined #openstack-meeting06:16
*** Daisy has quit IRC06:19
*** numans has joined #openstack-meeting06:22
*** IlyaG has joined #openstack-meeting06:22
*** askb has quit IRC06:24
*** jprovazn has joined #openstack-meeting06:24
*** IlyaG has quit IRC06:27
*** numans has quit IRC06:30
*** ian_ott has joined #openstack-meeting06:30
*** MarkAtwood has quit IRC06:33
*** novas0x2a|laptop has quit IRC06:33
*** ian_ott has quit IRC06:35
*** jcooley has quit IRC06:35
*** asettle has joined #openstack-meeting06:38
*** numans has joined #openstack-meeting06:41
*** roxanagh_ has joined #openstack-meeting06:42
*** akuznetsov has quit IRC06:42
*** asettle has quit IRC06:43
*** lpetrut has joined #openstack-meeting06:43
*** gcb has quit IRC06:45
*** Daisy_ has quit IRC06:49
*** Daisy has joined #openstack-meeting06:50
*** roxanagh_ has quit IRC06:51
*** Daisy_ has joined #openstack-meeting06:52
*** Daisy has quit IRC06:52
*** ildikov_ has quit IRC06:53
*** asettle has joined #openstack-meeting06:54
*** gcb has joined #openstack-meeting06:57
*** azbiswas has joined #openstack-meeting06:59
*** haomaiwang has quit IRC07:01
*** haomaiwa_ has joined #openstack-meeting07:01
*** azbiswas_ has quit IRC07:02
*** baoli has joined #openstack-meeting07:02
*** vishwana_ has joined #openstack-meeting07:07
*** baoli has quit IRC07:07
*** vishwanathj_away has quit IRC07:10
*** yuval has joined #openstack-meeting07:11
*** tesseract has joined #openstack-meeting07:13
*** tesseract is now known as Guest9751907:13
*** Daisy_ has quit IRC07:15
*** vishwana_ has quit IRC07:16
*** paul-carlton2 has joined #openstack-meeting07:16
*** ihrachys has joined #openstack-meeting07:17
*** gcb has quit IRC07:25
*** nkrinner has joined #openstack-meeting07:28
*** maishsk has joined #openstack-meeting07:29
*** fawadkhaliq has quit IRC07:30
*** neeti has joined #openstack-meeting07:30
*** ian_ott has joined #openstack-meeting07:32
*** evgenyf has joined #openstack-meeting07:32
*** scheuran has joined #openstack-meeting07:33
*** dmorita has joined #openstack-meeting07:34
*** azbiswas has quit IRC07:34
*** azbiswas has joined #openstack-meeting07:34
*** wojdev has joined #openstack-meeting07:35
*** ian_ott has quit IRC07:36
*** dmorita has quit IRC07:38
*** azbiswas has quit IRC07:39
*** gcb has joined #openstack-meeting07:42
*** Daisy has joined #openstack-meeting07:43
*** lpetrut has quit IRC07:45
*** iyamahat has quit IRC07:52
*** yamahata has quit IRC07:52
*** nmagnezi has joined #openstack-meeting07:53
*** asettle has quit IRC07:55
*** jlanoux has joined #openstack-meeting07:55
*** iceyao has joined #openstack-meeting07:55
*** iceyao has quit IRC07:56
*** iGene has quit IRC07:57
*** belmoreira has joined #openstack-meeting07:58
*** toddjohn has joined #openstack-meeting07:58
*** epico has quit IRC08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Mar 15 08:00:24 2016 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
anteayahello08:00
*** Guest97519 has quit IRC08:00
*** haomaiwa_ has quit IRC08:01
*** mhickey has joined #openstack-meeting08:01
*** haomaiwang has joined #openstack-meeting08:01
lennybhi08:01
anteayahey lennyb08:02
anteayayou have already seen this but putting it in the logs for this meeting08:02
*** toddjohn has quit IRC08:02
anteaya#info gerrit ip addresses is changing in April: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088985.html08:03
anteayawas there anything you wanted to talk about today?08:03
lennyb:). I know it's a late night or even early morning for you and I have nothing to discuss, so...08:03
anteayaI'm up08:04
*** jschwarz has joined #openstack-meeting08:04
anteayawilling to discuss if you have anything08:04
*** matrohon has joined #openstack-meeting08:04
anteayaand will keep the meeting open another few minutes in case of a drop in08:05
anteayabut won't keep you if you have other things08:05
*** tesseract has joined #openstack-meeting08:05
*** tesseract is now known as Guest9179408:06
*** _nadya_ has joined #openstack-meeting08:06
*** bvandenh has joined #openstack-meeting08:08
*** epico has joined #openstack-meeting08:11
*** markvoelker has joined #openstack-meeting08:12
*** pnavarro has joined #openstack-meeting08:12
*** paul-carlton2 has quit IRC08:15
*** rossella_ has joined #openstack-meeting08:17
*** salv-orl_ has quit IRC08:18
anteayaany objections to me closing the meeting?08:20
anteayathank you, see you next week08:21
anteaya#endmeeting08:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:21
openstackMeeting ended Tue Mar 15 08:21:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-15-08.00.html08:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-15-08.00.txt08:21
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-03-15-08.00.log.html08:21
*** yuval has quit IRC08:22
*** yuval has joined #openstack-meeting08:22
*** jichen has joined #openstack-meeting08:24
*** paul-carlton2 has joined #openstack-meeting08:25
*** pece has joined #openstack-meeting08:28
*** haukebruno has joined #openstack-meeting08:29
*** fzdarsky_ is now known as fzdarsky08:30
*** maishsk_ has joined #openstack-meeting08:31
*** fawadkhaliq has joined #openstack-meeting08:31
*** maishsk has quit IRC08:32
*** maishsk_ is now known as maishsk08:32
*** egallen has joined #openstack-meeting08:35
*** jlanoux has quit IRC08:36
*** neiljerram has joined #openstack-meeting08:38
*** JRobinson__ has joined #openstack-meeting08:38
*** spotz is now known as spotz_zzz08:40
*** kzaitsev_mb_ has joined #openstack-meeting08:40
*** spotz_zzz is now known as spotz08:43
*** markvoelker has quit IRC08:44
*** Guest91794 has quit IRC08:45
*** ndipanov has joined #openstack-meeting08:47
*** xinwu has quit IRC08:50
*** zeih has joined #openstack-meeting08:50
*** dixiaoli_ has joined #openstack-meeting08:54
*** dfflanders has quit IRC08:54
*** mbound has joined #openstack-meeting08:56
*** e0ne has joined #openstack-meeting08:57
*** lpetrut has joined #openstack-meeting08:58
*** Guest91794 has joined #openstack-meeting08:59
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-meeting09:01
*** zz_dimtruck is now known as dimtruck09:02
*** paul-carlton2 has quit IRC09:04
*** hashar has joined #openstack-meeting09:05
*** wojdev has quit IRC09:05
*** luisfdez1 has joined #openstack-meeting09:07
*** luisfdez has quit IRC09:07
*** ygbo has joined #openstack-meeting09:10
*** safchain has joined #openstack-meeting09:11
*** sc68cal has quit IRC09:11
*** dmacpher has quit IRC09:13
*** dixiaoli_ has quit IRC09:13
*** adiantum has joined #openstack-meeting09:14
*** ygbo has quit IRC09:16
*** zeih has quit IRC09:18
*** Daisy has quit IRC09:19
*** ygbo has joined #openstack-meeting09:20
*** salv-orlando has joined #openstack-meeting09:21
*** toscalix has joined #openstack-meeting09:22
*** hashar has quit IRC09:22
*** andymaier has joined #openstack-meeting09:23
*** hashar has joined #openstack-meeting09:25
*** jlanoux has joined #openstack-meeting09:25
*** wojdev has joined #openstack-meeting09:26
*** egallen has quit IRC09:28
*** salv-orlando has quit IRC09:29
*** salv-orlando has joined #openstack-meeting09:30
*** zhhuabj has quit IRC09:31
*** rcernin has joined #openstack-meeting09:31
*** paul-carlton2 has joined #openstack-meeting09:33
*** ian_ott has joined #openstack-meeting09:33
*** ljxiash has quit IRC09:34
*** ljxiash has joined #openstack-meeting09:34
*** yassine__ has joined #openstack-meeting09:35
*** egallen has joined #openstack-meeting09:37
*** zhurong_ has quit IRC09:37
*** ian_ott has quit IRC09:38
*** ljxiash has quit IRC09:39
*** maishsk has quit IRC09:40
*** akuznetsov has joined #openstack-meeting09:40
*** zhhuabj has joined #openstack-meeting09:45
*** ljxiash has joined #openstack-meeting09:48
*** hichihara has quit IRC09:52
*** mrmartin has joined #openstack-meeting09:53
*** claudiub has joined #openstack-meeting09:59
*** [1]evgenyf has joined #openstack-meeting09:59
*** haomaiwang has quit IRC10:01
*** sdague has joined #openstack-meeting10:01
*** haomaiwang has joined #openstack-meeting10:01
*** evgenyf has quit IRC10:02
*** [1]evgenyf is now known as evgenyf10:02
*** ociuhandu has quit IRC10:05
*** rossella_ has quit IRC10:07
*** rossella_s has joined #openstack-meeting10:08
*** sc68cal has joined #openstack-meeting10:08
*** e0ne has quit IRC10:08
*** e0ne has joined #openstack-meeting10:08
*** ljxiash has quit IRC10:11
*** luisfdez has joined #openstack-meeting10:11
*** ljxiash has joined #openstack-meeting10:12
*** sc68cal has quit IRC10:13
*** luisfdez1 has quit IRC10:14
*** sambetts|afk is now known as sambetts10:15
*** epico has quit IRC10:16
*** mrmartin has quit IRC10:17
*** luisfdez has quit IRC10:18
*** ljxiash has quit IRC10:18
*** klkumar has joined #openstack-meeting10:19
*** hoangcx has quit IRC10:21
*** electrofelix has joined #openstack-meeting10:21
*** jckasper has joined #openstack-meeting10:23
*** JRobinson__ has quit IRC10:26
*** jckasper has quit IRC10:27
*** wojdev has quit IRC10:28
*** wojdev has joined #openstack-meeting10:29
*** jlanoux_ has joined #openstack-meeting10:32
*** zhhuabj has quit IRC10:32
*** jlanoux has quit IRC10:32
*** ian_ott has joined #openstack-meeting10:34
*** rodrigods has quit IRC10:35
*** rodrigods has joined #openstack-meeting10:36
*** fwdit has joined #openstack-meeting10:37
*** azbiswas has joined #openstack-meeting10:38
*** merooney has joined #openstack-meeting10:39
*** ian_ott has quit IRC10:39
*** dimtruck is now known as zz_dimtruck10:40
*** zz_dimtruck is now known as dimtruck10:42
*** azbiswas has quit IRC10:42
*** markvoelker has joined #openstack-meeting10:42
*** andymaier has quit IRC10:47
*** luisfdez has joined #openstack-meeting10:47
*** ljxiash has joined #openstack-meeting10:47
*** ljxiash has quit IRC10:52
*** zhhuabj has joined #openstack-meeting10:52
*** yassine__ has quit IRC10:58
*** Ravikiran_K has left #openstack-meeting10:59
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-meeting11:01
*** maishsk has joined #openstack-meeting11:02
*** baojg has quit IRC11:05
*** dbite has joined #openstack-meeting11:06
*** nkrinner_ has joined #openstack-meeting11:06
*** nkrinner_ has quit IRC11:07
*** dguitarb1 has joined #openstack-meeting11:07
*** nkrinner_ has joined #openstack-meeting11:08
*** gcb has quit IRC11:08
*** dguitarbite has quit IRC11:09
*** nkrinner has quit IRC11:09
*** dbite has quit IRC11:11
*** dims has joined #openstack-meeting11:12
*** ityaptin has quit IRC11:12
-openstackstatus- NOTICE: Gerrit is going to be restarted11:13
*** markvoelker has quit IRC11:15
*** rbowen has joined #openstack-meeting11:16
*** paul-carlton2 has quit IRC11:18
*** gcb has joined #openstack-meeting11:19
*** dims has quit IRC11:20
*** paul-carlton2 has joined #openstack-meeting11:21
*** dims has joined #openstack-meeting11:21
*** dims has quit IRC11:21
*** dims has joined #openstack-meeting11:21
*** ujuc has joined #openstack-meeting11:21
*** cartik has joined #openstack-meeting11:24
*** paul-carlton2 has quit IRC11:28
*** akuznetsov has quit IRC11:28
*** mrunge has quit IRC11:28
*** rtheis has joined #openstack-meeting11:29
*** ihrachys has quit IRC11:31
*** ihrachys has joined #openstack-meeting11:31
*** mrmartin has joined #openstack-meeting11:32
*** paul-carlton2 has joined #openstack-meeting11:32
-openstackstatus- NOTICE: Gerrit had to be restarted because was not responsive. As a consequence, some of the test results have been lost, from 08:30 UTC to 10:30 UTC approximately. Please recheck any affected jobs by this problem.11:33
*** alyson_ has joined #openstack-meeting11:34
-openstackstatus- NOTICE: Gerrit had to be restarted because was not responsive. As a consequence, some of the test results have been lost, from 09:30 UTC to 11:30 UTC approximately. Please recheck any affected jobs by this problem.11:36
*** ihrachys has quit IRC11:36
*** weshay has joined #openstack-meeting11:39
*** merooney has quit IRC11:39
*** azbiswas has joined #openstack-meeting11:40
*** mrunge has joined #openstack-meeting11:40
*** thorst_ has joined #openstack-meeting11:41
*** azbiswas has quit IRC11:44
*** rfolco has joined #openstack-meeting11:45
*** merooney has joined #openstack-meeting11:46
*** aswadr1 has joined #openstack-meeting11:46
*** nmagnezi has quit IRC11:46
*** adahms has joined #openstack-meeting11:46
*** aswadr1 has left #openstack-meeting11:47
*** drankis has joined #openstack-meeting11:49
*** erlon has joined #openstack-meeting11:49
*** nmagnezi has joined #openstack-meeting11:49
*** dmacpher has joined #openstack-meeting11:50
*** aswadr1 has joined #openstack-meeting11:50
*** ian_ott has joined #openstack-meeting11:51
*** aswadr1 has left #openstack-meeting11:52
*** ryu25 has quit IRC11:52
*** jlanoux has joined #openstack-meeting11:53
*** _amrith_ is now known as amrith11:54
*** salv-orl_ has joined #openstack-meeting11:54
*** egallen has quit IRC11:55
*** ian_ott has quit IRC11:55
*** jlanoux_ has quit IRC11:56
*** maeca has joined #openstack-meeting11:57
*** salv-orlando has quit IRC11:57
*** cschulz has joined #openstack-meeting11:58
*** lbeliveau has joined #openstack-meeting11:59
*** cdent has joined #openstack-meeting12:00
*** haomaiwang has quit IRC12:01
*** maeca has quit IRC12:01
*** haomaiwang has joined #openstack-meeting12:01
*** yassine__ has joined #openstack-meeting12:02
cdentnova api meeting?12:02
*** yassine__ has quit IRC12:03
johnthetubaguycdent: thats what my calendar says, I can't remember if we said we were pausing them now12:03
*** neiljerram has quit IRC12:03
*** cschulz has quit IRC12:03
cdentseems reasonable to do so12:03
*** mrmartin has quit IRC12:04
*** ociuhandu has joined #openstack-meeting12:05
*** bvandenh has quit IRC12:06
*** zhurong_ has joined #openstack-meeting12:07
*** paul-carlton2 has quit IRC12:07
*** ihrachys has joined #openstack-meeting12:07
*** belmoreira has quit IRC12:07
*** salv-orl_ has quit IRC12:08
*** aysyd has joined #openstack-meeting12:08
*** Ravikiran_K has joined #openstack-meeting12:09
*** MaxPC has joined #openstack-meeting12:11
*** neiljerram has joined #openstack-meeting12:11
*** akuznetsov has joined #openstack-meeting12:15
*** raildo-afk is now known as raildo12:16
*** iceyao has joined #openstack-meeting12:17
jichencdent: it was changed ,http://lists.openstack.org/pipermail/openstack-dev/2016-March/089063.html12:17
cdentah, right thanks jichen12:17
cdentit hasn't been updated here yet: http://eavesdrop.openstack.org/#Nova_API_Meeting12:17
jichenyes  :)12:18
*** pnavarro has quit IRC12:18
*** zhurong_ has quit IRC12:18
*** cshahani has quit IRC12:21
*** spotz is now known as spotz_zzz12:23
*** ayoung has joined #openstack-meeting12:23
*** dims has quit IRC12:25
*** dims has joined #openstack-meeting12:26
*** merooney has quit IRC12:27
*** cartik has quit IRC12:28
*** piet has joined #openstack-meeting12:29
*** merooney has joined #openstack-meeting12:32
*** baoli has joined #openstack-meeting12:32
*** baoli_ has joined #openstack-meeting12:33
*** armax has quit IRC12:33
*** dneary has joined #openstack-meeting12:33
*** dmorita has joined #openstack-meeting12:35
*** hichihara has joined #openstack-meeting12:35
*** yassine__ has joined #openstack-meeting12:37
*** baoli has quit IRC12:37
*** dmorita has quit IRC12:40
*** balajiiyer has joined #openstack-meeting12:41
*** klkumar has quit IRC12:43
*** toddjohn has joined #openstack-meeting12:45
*** balajiiyer has quit IRC12:45
*** neelashah has joined #openstack-meeting12:46
*** asettle has joined #openstack-meeting12:46
*** cdent has left #openstack-meeting12:46
*** amrith is now known as _amrith_12:50
*** asettle has quit IRC12:51
*** dprince has joined #openstack-meeting12:52
*** ninag has joined #openstack-meeting12:53
*** markvoelker has joined #openstack-meeting12:53
*** wojdev has quit IRC12:56
*** mfranc213 has joined #openstack-meeting12:57
*** elynn has joined #openstack-meeting12:58
*** haomaiwang has quit IRC12:58
*** wojdev has joined #openstack-meeting12:58
*** yanyanhu has joined #openstack-meeting12:58
*** haiwei has joined #openstack-meeting12:59
*** janzian_ has joined #openstack-meeting12:59
*** Qiming has joined #openstack-meeting12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Mar 15 13:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** akaszuba has joined #openstack-meeting13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qiminggood evening13:00
*** lixinhui_ has joined #openstack-meeting13:00
elynnevening!13:00
*** cschulz has joined #openstack-meeting13:00
lixinhui_evening!13:00
*** Leo_ has joined #openstack-meeting13:00
Qiminghi, elynn, lixinhui_13:00
cschulzHi13:01
Qiminghi, chuck13:01
haiweihi13:01
Qimingmeeting agenda posted here: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:01
yanyanhuhi13:01
Qimingpls check if there are things to add13:01
Qiming#topic austin summit planning13:01
*** openstack changes topic to "austin summit planning (Meeting topic: senlin)"13:01
*** maeca has joined #openstack-meeting13:01
*** eharney has joined #openstack-meeting13:01
*** iyamahat has joined #openstack-meeting13:02
Qimingso we have three talks accepted13:02
Qimingelynn, yanyan and I had a discussion this noon, about the 'senlin deep dive' session13:02
Qimingwe are going to prepare the talk based on the deck I presented during the mitaka mid-cycle meetup13:03
*** Leom has joined #openstack-meeting13:03
Qimingthis session will be mainly focused on the why's and how's13:03
*** janzian_ has left #openstack-meeting13:03
cschulzis the midcycle meetup deck posted somewhere?13:03
Qimingit will walk the audience through the project's origin, its architecture, its use case and roadmap, possibly a comparison to aws scaling and heat-based scaling13:04
Qimingno, chuck, I can send you a copy if you are interested13:04
cschulzYes, thanks.13:04
*** armax has joined #openstack-meeting13:05
Qimingother than that 'deep dive' kind of overview, we won't have a lot time to dive into a particular theme, e.g. HA, AutoScaling, policies, profiles, drivers ...13:05
Qimingwe will need to start prepare the talk as early as possible13:05
*** yamamoto has quit IRC13:05
Qimingthe second one is mostly about autoscaling13:05
*** Leo_ has quit IRC13:06
*** ujuc has quit IRC13:06
Qimingit will talk about the requirements, the projects/services involved, the various usage scenarios and the senlin's solution13:06
Qiminghopefully, we can combine all the load-balancing, auto-scaling and high-availability things into a single Heat template13:07
Qiminglixinhui_ has been driving this work13:07
Qimingwe'll help her get this talk carefully prepared as well13:07
*** sdake has joined #openstack-meeting13:08
*** maishsk has quit IRC13:08
Qimingthe third one is more of an open discussion, creating and managing containers using senlin, thus making containers a first-class citizen on openstack13:08
*** maishsk has joined #openstack-meeting13:08
Qimingwe are supposed to do a good survey of all existing proposals/projects and articulate why we are doing this13:09
Qimingwhat are the specific problems we need to solve, and how are we planning to address them13:09
*** yanyanhu_ has joined #openstack-meeting13:09
haiweiyes, Qiming13:10
*** jlanoux has quit IRC13:10
haiweiI have updated the spec, hope you can review it13:10
Qimingthis one is the most visionary one, and we are really hoping we can get some constructive feedbacks from the community13:10
haiweiand also ask some magnum guys to review it13:10
Qimingeven if there are opponents, we will listen to what they say13:10
Qimingthat would be good haiwei13:10
*** jlanoux has joined #openstack-meeting13:10
Qimingbut one notion13:11
Qiminglast time we collaborated with magnum developers on autoscaling the VM clusters used to run containers13:11
Qimingthere was a proposal in magnum to do their own auto-scaling engine13:11
*** yamahata has joined #openstack-meeting13:12
*** yanyanhu has quit IRC13:12
Qimingwe are open to do all communication, but we are not planning to do stupid things13:12
*** toddjohn has quit IRC13:12
*** akaszuba has quit IRC13:12
Qimingany comments on the talk preparation?13:12
Qimingsuggestions?13:12
*** myoung|mobile has joined #openstack-meeting13:13
*** myoung|mobile is now known as myoung13:13
Qimingmoving on13:13
Qiming#topic mitaka work items13:13
*** openstack changes topic to "mitaka work items (Meeting topic: senlin)"13:13
Qiming#link https://etherpad.openstack.org/p/senlin-mitaka-workitems13:13
*** iyamahat has quit IRC13:14
*** jckasper has joined #openstack-meeting13:14
Qimingstress testing side, contacted xujun, they don't have bandwidth at the moment13:14
Qimingbut anyway, we are introducing tempest into senlin13:14
yanyanhu_ok13:14
lixinhui_Bran has gotten some data13:14
yanyanhu_we have a topic on this in summit13:14
*** egallen has joined #openstack-meeting13:14
Qimingoh, really?13:14
yanyanhu_lixinhui_, great13:14
lixinhui_I will send the document to all of you13:15
Qimingthank you madam13:15
lixinhui_need your help to improve13:15
lixinhui_very crude one13:15
Qimingthat would be a good starting point13:15
yanyanhu_sure, this will be a very good start point13:15
lixinhui_but we can do better with your suggestions and help13:15
Qimingyanyan and I talked about tempest, and elynn joined the discussion as well13:15
*** amitgandhinz has joined #openstack-meeting13:15
cschulzI have noticed that a heat stack will indicate create complete even though the senlin cluster create fails.13:16
yanyanhu_also, I will start to investigate rally to see whether there are something we can leverage13:16
*** salv-orlando has joined #openstack-meeting13:16
cschulzIs someone looking into this?13:16
Qimingthe plan is to introduce tempest test into senlin asap, since we are not planning to add new features until the newton development opens13:16
Qimingcschulz, bug filed?13:16
cschulzGood. thanks.13:17
elynnHi cschulz, is there any bug you open for it?13:17
*** akuznetsov has quit IRC13:17
Qimingthe api/functional/scenario tests will be driven by tempest, and we will decide later whether using rally to do stress test is viable13:17
cschulzNo I didn't since it wasn't causing any issues, but thought I'd bring it up in the area of testing.13:17
Qimingcschulz, it sounds like a bug to me, :)13:18
elynnoh... if so, I think it should be fixed in senlin...13:18
*** jckasper has quit IRC13:18
cschulzYes will open bug13:18
Qimingthanks, cschulz13:19
*** ig0r__ has joined #openstack-meeting13:19
Qiminghealth management/policy13:19
lixinhui_I believe API side check/recover has done13:19
Qimingnode status polling is labeld with 'need tests'13:19
Qimingfunctional tests?13:19
lixinhui_oh13:20
lixinhui_seems need to add some functional tests13:20
*** piet has quit IRC13:20
Qimingyep13:20
Qimingsome functional test for the health-manager13:20
yanyanhu_hi, xinhui, there has been a functional test case for node check/recover13:20
lixinhui_will refer to Yanyan's work and do it13:20
Qiminglixinhui_, still stuck by the lb errors?13:21
yanyanhu_but just for basic workflow13:21
*** armax has quit IRC13:21
*** asettle has joined #openstack-meeting13:21
lixinhui_yes, Qiming...13:21
lixinhui_yanyanhu_, we will read your work and add some tests for health-manager13:21
Qimingcan we switch back to haproxy instead of octavia for the moment?13:21
yanyanhu_haven't figured out how to test node/cluster check/recover with more complicated cases13:21
*** ig0r_ has quit IRC13:22
*** greghaynes has quit IRC13:22
yanyanhu_lixinhui_, any question, please just ping me13:22
lixinhui_thanks, yanyanhu.13:22
Qimingseems we need to emulate some node failures anyway13:22
lixinhui_yes, Qiming13:22
Qimingfor the robustness of all other apis, besides the health checking ones13:22
*** RuiChen has quit IRC13:22
yanyanhu_Qiming, yes, a feasible way is providing another test driver for this purpose13:23
*** ninag_ has joined #openstack-meeting13:23
Qiminginsert random failures?13:23
yanyanhu_but it's not a good way I think13:23
*** RuiChen has joined #openstack-meeting13:24
yanyanhu_Qiming, yes, that's what we want. But not sure how to support it13:24
Qiming"random" I mean, if it is really random, you can not verify you testing results13:24
Qimingshould be a quoted version, :)13:24
Qimingmaybe we can improve the fake driver to do things in a controlled way13:25
*** tochi has quit IRC13:25
yanyanhu_yes13:25
yanyanhu_this is what I'm thinking13:25
*** lblanchard has joined #openstack-meeting13:25
Qimingdefinitely not another set of drivers13:25
*** jlanoux has quit IRC13:25
*** dmorita has joined #openstack-meeting13:25
*** asettle has quit IRC13:25
*** jckasper has joined #openstack-meeting13:25
*** ninag has quit IRC13:26
*** ayoung has quit IRC13:26
*** jlanoux has joined #openstack-meeting13:26
yanyanhu_I also think so. That's really not a graceful way to solve this issue13:26
Qimingwe still need an etherpad to discuss the use cases13:26
Qimingfor HA13:26
*** merooney has quit IRC13:26
Qiminglixinhui_, you want to drive that?13:26
lixinhui_https://etherpad.openstack.org/p/senlin-ha-recover13:27
lixinhui_sure13:27
*** dingboopt has quit IRC13:27
lixinhui_collect some discussion last week into the etherpad13:27
Qiminggreat, you already created one, :)13:27
Qimingcool, will read and comment offline13:27
Qimingdocumentation side, just commited some more documents for review13:28
lixinhui_will extend it for use case discussion purpose13:28
Qimingstill need to add docs for the placement policy13:28
Qimingno progress on wiki site revision yet13:28
*** dimtruck is now known as zz_dimtruck13:29
Qimingthe autoscaling sample can be based on our current work for the summit talk, right?13:29
lixinhui_yes13:29
lixinhui_I think so13:29
*** dmorita has quit IRC13:30
*** haomaiwang has joined #openstack-meeting13:30
Qimingokay, just leave it there, it belongs to mitaka13:30
Qimingthe next one is container profile13:30
Qimingas a contrib it is okay13:30
cschulzIs that autoscale sample similar to the work Ethan has been doing there?13:30
Qimingcschulz, yes13:30
Qimingcschulz, https://www.openstack.org/summit/austin-2016/summit-schedule/events/746913:31
Qimingor, you can say, a more comprehensive one13:31
*** klkumar has joined #openstack-meeting13:31
Qimingit is a combination of auto-scaling, auto-healing and load-balancing13:31
Qimingstill no progress on the NODE_CREATE/DELETE action thing13:32
*** jmckind has joined #openstack-meeting13:32
QimingI'm adding an API microversioning item13:33
Qiminghopefully can be done by mitaka release13:33
*** rfolco has quit IRC13:33
Qimingthe idea will be borrowed from nova and cross-project specs13:33
*** rfolco has joined #openstack-meeting13:33
Qimingit is a prerequisite for any further revision to senlin api13:34
*** piet has joined #openstack-meeting13:34
Qimingwe are locking the version 1.0 api13:34
*** merooney has joined #openstack-meeting13:34
*** luisfdez has quit IRC13:34
*** piet has quit IRC13:34
Qimingany (user visible) changes to it will necesitate a 1.1 version bump13:34
Qimingbefore doing that, we will need a microversioning infra in place13:34
Qimingthat's pretty a heavy workload before final release13:35
Qimingcomments?13:35
haiweiis this micro version similar to nova micro version?13:35
*** luisfdez has joined #openstack-meeting13:35
Qiming[21:33] <Qiming> the idea will be borrowed from nova and cross-project specs13:35
*** galstrom_zzz is now known as galstrom13:35
haiweiok13:36
Qimingokay, moving on13:36
Qiming#topic stricter policy checking13:36
*** openstack changes topic to "stricter policy checking (Meeting topic: senlin)"13:36
Qimingso this problem come to my mind when I was reviewing the policy implementations and trying to document them down13:36
Qimingcurrently, a policy checks its TARGET against the actions to be (or already) executed13:37
Qimingthe problem is that we don't have a strict definition/realization of TARGET13:37
*** sdake has quit IRC13:38
*** greghaynes has joined #openstack-meeting13:38
yanyanhu_you mean the naming of TARGET?13:38
Qimingan action not listed in the TARGET may not trigger the policy checking, even if it may arouse some problems13:38
*** efried has joined #openstack-meeting13:38
yanyanhu_I think we have defined TARGET action list in some policies13:38
Qimingtake affinity policy as an example13:38
Qimingsupposed I have created a cluster and attached an affinity policy13:39
Qimingnow I want to do cluster_node_add13:39
Qimingand the node I want to add doesn't belong to the servergroup, it is from some other hosts13:39
Qimingcan I do it?13:39
yanyanhu_nope I think13:40
*** pradk has joined #openstack-meeting13:40
Qimingif we allow the policy check to succeed, the cluster violates the affinity setting13:40
yanyanhu_the affinity policy should reject this request13:40
*** ayoung has joined #openstack-meeting13:40
Qimingif we don't allow it, we should say NO in the affinity checking13:40
cschulzI think that the only way to be totally sure is to trigger all Policies for every action and have the policy decide if it is appropriate.13:40
Qimingright, that is the problem I'm talking about13:41
cschulzBut that is kind of heavy weight.13:41
QimingI'm creating a table with all actions as the columns and all policies as the rows13:41
yanyanhu_is cluster_node_add now in the target list of affinity policy?13:41
Qimingin each cell, we should fill in "CHECK", "IGNORE"13:42
Qimingyanyanhu_, no, it is not listed there13:42
yanyanhu_ok, so we should add it13:42
yanyanhu_I think this is more about managing policy target in a better way13:42
cschulzWe will also need to consider how to amend this table when a new policy plugin is added.13:42
Qimingyep. cschulz13:43
Qimingthe table should be documented13:43
*** vhoward has joined #openstack-meeting13:43
yanyanhu_can this table be revised dynamically?13:44
cschulzAnd probably a method in a plugin which amends the table, similar to how the plugin mapping occurs13:44
Qimingwhen filling in "IGNORE", we can save the action from the TARGET list, but we have to bear in mind, an "IGNORE" is equal to say "YES"13:44
*** banix has joined #openstack-meeting13:44
*** banix has quit IRC13:44
Qimingcschulz, that checking was done in the policy base class, IIRC13:44
*** banix has joined #openstack-meeting13:45
*** sigmavirus24_awa is now known as sigmavirus2413:45
Qimingwe can check if it can be made more flexible13:45
haiwei'IGNORE' means not check, right?13:45
Qiminghaiwei, exactly13:46
Qimingwhen you are checking, you can say "yes" or "no", when you are silent, it means a "yes", that is the difference we need to clarify13:46
yanyanhu_Qiming, a question is when those cell will be filled in13:47
yanyanhu_when a policy plugin is loaded?13:47
haiweiI think when the action is executed13:47
Qimingwe can start with a static one, and then try make it more flexible13:47
*** numans has quit IRC13:47
*** numans has joined #openstack-meeting13:48
haiweithere should be no check before some actions are executed13:48
Qimingfor example, we can load a policy and check that policies definition and determine when it should be checked ...13:48
yanyanhu_yes, this makes sense13:48
yanyanhu_just a little concerned about changing this target relationship dynamically13:49
*** yamamoto has joined #openstack-meeting13:49
Qimingyes, yanyanhu_ , we have been there13:49
yanyanhu_since it will influence all policy instances and action instances13:49
Qimingso, for builtin policies, we will use a static definition13:49
*** jckasper has quit IRC13:49
*** kzaitsev_mb_ is now known as kzaitsev_mb13:49
*** yamamoto_ has joined #openstack-meeting13:49
Qimingtoo much flexibility will lead the whole scenario unmanageable13:49
yanyanhu_yes13:50
yanyanhu_that is exactly what I mean13:50
Qiminglet's fill the holes one by one13:50
haiweicurrently the target relationship is changed dynamically?13:50
*** amuller has joined #openstack-meeting13:50
Qimingfor example, zone placement and region placement cannot handle cluster resize actions, but they should13:50
yanyanhu_haiwei, no, it is implemented by hard code in definition of each policy13:51
Qiminge.g.13:51
Qimingdeletion_policy.py:    TARGET = [13:51
Qimingdeletion_policy.py-        ('BEFORE', consts.CLUSTER_SCALE_IN),13:51
Qimingdeletion_policy.py-        ('BEFORE', consts.CLUSTER_DEL_NODES),13:51
Qimingdeletion_policy.py-        ('BEFORE', consts.CLUSTER_RESIZE),13:51
Qimingdeletion_policy.py-    ]13:51
haiweiok, by giving them some integers, yanyanhu_?13:51
yanyanhu_haiwei, actually some consts13:52
haiweiyes13:52
yanyanhu_just like what Qiming showed13:52
Qimingthese are the relationships between actions and policies13:52
*** toddjohn has joined #openstack-meeting13:52
Qimingand ... among policies, there is a priority checking13:52
*** dasm has joined #openstack-meeting13:52
*** iwamoto has joined #openstack-meeting13:53
Qimingso most of these can be treated as bugs13:53
Qimingand we can strive to fix them starting from now13:53
*** yamamoto has quit IRC13:53
*** jlibosva has joined #openstack-meeting13:53
Qimingyanyanhu_, since you are looking into rally13:54
yanyanhu_Qiming, you mean remove priority attr from policy?13:54
Qimingmaybe you can give team an assessment next week?13:54
cschulzCan the table be posted somewhere so we can all look at it and comment.13:54
Qimingyanyanhu_, no, I was pointing out that we are talking about different things13:54
Qimingyes, cschulz13:54
yanyanhu_Qiming, sure, will do some investigation in coming week13:55
Qiming#action Qiming to draft a table (action, policy) and post it online13:55
yanyanhu_Qiming, I see13:55
Qiming#topic open discussions13:55
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:55
*** ljxiash has joined #openstack-meeting13:56
haiweican we arrange a discussion sometime this week to talk about containers?13:56
*** rbak has joined #openstack-meeting13:56
Qimingsure13:56
Qimingmaybe a phone call?13:56
haiweimaybe Tuesday morning?13:56
cschulzI was wondering if there is a 'proof reading' policy for our web pages, wiki pages etc.  I've noticed quite a lot of typos and misspellings and it looks unprofessional.13:56
haiweiI am ok for phone call meeting13:56
Qimingcschulz, all docs, except for the wiki pages are generated from senlin source tree13:57
Qimingany helps are welcomed on polishing the docs13:57
yanyanhu_I think maybe we can start to post some items in the following etherpad about what we are doing for newton cycle13:57
yanyanhu_https://etherpad.openstack.org/p/senlin-newton-workitems13:57
yanyanhu_maybe just some draft13:58
haiweiyes13:58
Qimingcschulz, there is no native English speaker in the team13:58
*** fangzhen has joined #openstack-meeting13:58
cschulzWrong, there is me.13:58
*** keedya has joined #openstack-meeting13:58
Qimings/is/was13:58
Qiming:)13:58
yanyanhu_cschulz cool :)13:58
*** janzian has joined #openstack-meeting13:58
elynncschulz great!13:59
*** paul-carlton2 has joined #openstack-meeting13:59
haiweiI thought you were a Chinese too13:59
Qimingtime's up, guys, thanks for joining, until next week!13:59
haiweisee u13:59
yanyanhu_thanks13:59
Qiming#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Tue Mar 15 13:59:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-15-13.00.html13:59
*** askb has joined #openstack-meeting13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-15-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-03-15-13.00.log.html13:59
*** haiwei has quit IRC14:00
*** johnsom has joined #openstack-meeting14:00
*** lixinhui_ has quit IRC14:00
kevinbentonhello folks here for neutron meeting14:00
hichiharahi14:00
dasmo/14:00
kevinbenton#startmeeting networking14:00
haleybhi14:00
openstackMeeting started Tue Mar 15 14:00:38 2016 UTC and is due to finish in 60 minutes.  The chair is kevinbenton. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
iwamotoo/14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
rossella_shi14:00
johnsomo/14:00
jschwarz\o/14:01
*** haomaiwang has quit IRC14:01
kevinbentonThis will be a relatively short meeting, just a few announcements14:01
kevinbenton#topic Announcements/Reminders14:01
*** openstack changes topic to "Announcements/Reminders (Meeting topic: networking)"14:01
njohnstono/14:01
*** singhj has joined #openstack-meeting14:01
mhickeyhello14:01
*** elynn has quit IRC14:01
*** haomaiwang has joined #openstack-meeting14:01
kevinbentonToday the branch for stable/mitaka is going to be cut14:01
*** brad_behle has joined #openstack-meeting14:01
*** korzen has joined #openstack-meeting14:01
dasm\o/14:01
korzenhello14:01
salv-orlandoaloha14:02
kevinbentonso any fixes that need to go into mitaka after this will need to be back-ported like we would for any other stable branch14:02
ajoo/14:02
*** slunkad has joined #openstack-meeting14:02
ajoack14:03
vhowardo/14:03
kevinbentonI believe armax and ihrachys have narrowed the bugs down so there are no major blockers for RC-1 that we need to worry about14:03
*** jungleboyj has quit IRC14:03
kevinbentondoes anyone have any bugs that need to be brought to everyone's attention?14:03
*** pc_m has joined #openstack-meeting14:03
kevinbenton(that would be a major issue in Mitaka)14:04
hichiharahttps://bugs.launchpad.net/neutron/+bug/155688414:04
openstackLaunchpad bug 1556884 in neutron "floating-ip association is allowed via router interface" [Medium,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)14:04
kevinbentonhichihara: thanks, i saw this one as well and it looks like we accidentally added a feature :)14:04
hichiharaI'm not sure that is worth Mitaka. L3 folks should review it.14:04
*** mrmartin has joined #openstack-meeting14:05
kevinbentonhichihara: it may be worth considering because we don't want to accidentally ship a feature that looks like it works14:05
hichiharakevinbenton: I think so14:06
kevinbentonhichihara: probably something to propose as a back-port to the mitaka branch before the final release14:06
reedip__o/14:06
*** bobh has joined #openstack-meeting14:06
*** cloudrancher has quit IRC14:06
kevinbentonAlso, this week is the week to announce PTL candidacies, so if you are interested in being PTL, send an email to the list!14:07
irenabkevinbenton: The feature is indeed very useful14:07
hichiharakevinbenton: I'm OK.14:07
*** yanyanhu_ has quit IRC14:07
*** jckasper has joined #openstack-meeting14:07
*** azbiswas has joined #openstack-meeting14:08
*** piet has joined #openstack-meeting14:08
*** bryan_att has joined #openstack-meeting14:08
hichiharaI haven't seen Neutron candidacy yet.14:08
*** jckasper has quit IRC14:08
*** jckasper has joined #openstack-meeting14:08
kevinbentonhichihara: i don't think anyone has sent one yet14:08
amullerArmando is suspiciously quiet :)14:08
ihrachyshichihara: we still have hope Armando will lead the way ;)14:09
hichiharaihrachys: Of course! :)14:09
kevinbenton#link https://launchpad.net/neutron/+milestone/mitaka-rc114:09
salv-orlandoI've heard Cthulhu wants to run as neutron PTL...14:09
kevinbenton^^ that's the stuff targeted for RC1, keep an eye on anything still open in high or critical status14:09
ajosalv-orlando, is he friend with zuul?14:10
*** armax has joined #openstack-meeting14:10
*** paul-carlton2 has quit IRC14:10
salv-orlandoajo: they might know each other from some past work experience but I don't think they're friends14:10
* njohnston is highly amused14:10
rossella_slol14:10
kevinbenton#info hichihara is bug deputy this week!14:10
hichiharaYeah.14:10
rossella_sgood luck hichihara14:11
*** armax has left #openstack-meeting14:11
hichiharaI have already started14:11
mhickeyhichihara: ++14:11
*** neeti has quit IRC14:11
kevinbenton#link https://github.com/openstack/neutron/blob/master/doc/source/policies/bugs.rst#neutron-bug-deputy14:11
kevinbenton^^ bug deputy info14:12
kevinbenton#topic open discussion14:12
*** openstack changes topic to "open discussion (Meeting topic: networking)"14:12
kevinbentoni don't have anything else. does anyone have anything they would like to discuss?14:12
*** cshahani has joined #openstack-meeting14:12
iwamotothere are some restructure-l2-agent related bugs14:12
*** jckasper has quit IRC14:12
*** salv-orlando has quit IRC14:12
*** azbiswas has quit IRC14:12
iwamotobug/1528895 and bug/143099914:13
*** galstrom is now known as galstrom_zzz14:13
ajosalv-orlando: lol14:13
*** salv-orlando has joined #openstack-meeting14:13
iwamotoI wonder if we want a quick fix for the coming release14:13
*** jmckind has quit IRC14:13
ajohichihara++14:13
kevinbentoni don't think so on bug/1430999. we can advise timeout increases for that as a workaround14:14
*** bvandenh has joined #openstack-meeting14:14
*** jckasper has joined #openstack-meeting14:14
*** esheffield has joined #openstack-meeting14:14
iwamotothe bugs have been there for more than a release and affects only high density environments14:14
kevinbentoniwamoto: yes, i don't think we want to put together last minute chunking fixes for these14:15
*** boden has joined #openstack-meeting14:15
rossella_sI agree with you kevinbenton ...14:15
reedip__we can target such issues in N-1?14:16
*** jmckind has joined #openstack-meeting14:16
*** asingh has joined #openstack-meeting14:16
iwamotook14:16
kevinbentonyes, we need to clearly identify the bottlenecks anyway14:16
iwamotoI think reverting change is better than increasing timeouts14:17
rossella_swe need a more general approach to fix those issues...I think Kevin is working on that, right Kevinbenton?14:17
iwamotothe new RPCs don't scale14:17
kevinbentonrossella_s: yes14:17
*** ajmiller has joined #openstack-meeting14:17
kevinbentoniwamoto: wait, revert what?14:17
iwamotobatched agent RPC calls14:17
iwamotoor impose some limit on numbers of ports one RPC can send14:18
*** merooney has quit IRC14:18
*** jlanoux has quit IRC14:18
kevinbentoniwamoto: didn't that ship in liberty?14:18
ajoiwamoto, I think the former is better14:18
ajoiwamoto,  we could have a parameter for agents (max bulk ports objects call) or something like that14:19
ajoobjects per call14:19
iwamotoyes liberty has the bug. and at least one person had to increase timeout for workaround , it seems14:19
kevinbentonbreaking the calls into chunks it basically pointless though14:19
*** korzen has quit IRC14:20
kevinbentonwhen increasing the timeout acheives the same effect14:20
rossella_sajo we need something better than that14:20
*** jichen has quit IRC14:20
rossella_skevinbenton you were working at that right, can't find the patch right now14:20
*** korzen has joined #openstack-meeting14:20
kevinbentonrossella_s: yes, there is a spec14:20
kevinbentonhttps://review.openstack.org/#/c/225995/14:20
ajowhy is it pointless?14:20
*** jmckind has quit IRC14:20
kevinbentonajo: what does it acheive?14:20
kevinbentonajo: the agent still sits there and waits for all of the calls to return14:21
ajokevinbenton: smaller subsets that need to be completed14:21
kevinbentonajo: so waiting for 50 smaller calls to return instead of 1 big one doesn't improve anything on the agent size14:21
*** korzen has quit IRC14:21
iwamotoIMO agent should  not issue such a gigantic RPC call14:21
rossella_sthat could be backported when ready to fix these issues14:21
rossella_sthanks kevinbenton14:21
ajothe agent waits, but if some of the calls timeout the succeeded ones don't need to be retried14:21
amullerwhy don't we increase the timeout from 1 min? I've made that suggestion before14:21
*** korzen has joined #openstack-meeting14:21
amullerWe know 1 min is too low, we know the value is arbitrary anyway14:22
amullerLet's bump it up14:22
kevinbentonamuller: +114:22
ajowe can make the timeout dynamic14:22
ajoa factor per number of bulk call objects14:22
ajoif we can do that in oslo.messaging (not sure if we can dynamically control that per call)14:23
njohnstonamuller: +114:23
ajobut +1 to just bumping it a bit14:23
*** sshnaidm has quit IRC14:23
rossella_swe could avoid such gigantic calls when they are not needed and send only a diff to update the l2 agent14:23
kevinbentonwe are only chunking because for some reason people have been afraid to increase these timeouts14:23
reedip__I agree with Ajo of keeping the bump dynamic14:24
kevinbentonrossella_s: i think the only time we get the huge ones on startup anyway14:24
ajohow's timeout controlled?14:24
ajois there any way to set it per RPC call?14:24
kevinbentona configuration variable14:25
*** sshnaidm has joined #openstack-meeting14:25
rossella_skevinbenton, also on bulk create that might happen14:25
*** sdake has joined #openstack-meeting14:25
* ajo digs oslo_messaging14:25
*** ihrachys has quit IRC14:25
*** jlibosva has quit IRC14:25
*** jlibosva1 has joined #openstack-meeting14:25
iwamotois timeout a issue in other projects than neutron?14:25
amullerajo: yes it can be per call14:25
*** jlibosva1 is now known as jlibosva14:25
ajoiwamoto, it is, for example in cinder14:25
*** tfukushima has joined #openstack-meeting14:25
ajoI know they need to bump it in some deployments14:25
ajoamuller, if that's the case, I'd propose controlling it on bulk calls based on the amount of objects14:25
*** tfukushima has quit IRC14:26
amullerwe need something now for the Mitaka release14:26
ajoand we can have a rpc_bulk_call_timeout_factor14:26
kevinbentonthere is almost no reason to not have a high timeout14:26
ajoamuller, short term: just bump it14:26
*** mrmartin has quit IRC14:26
*** Poornima has quit IRC14:26
kevinbentonshort timeouts only protect against completely lost messages, that's it14:26
rossella_samuller, bump it ;)14:26
ajobump!14:26
reedip__lol14:26
ajo:)14:27
ajoKevinbenton, in fact, they don't even stop the server operation,14:27
kevinbentonno, they don't14:27
ajoso the impact for server load is even worse, as the operation would be retried14:27
ajoso yes14:27
kevinbentonfrom the server's perspective, processing a giant call is not much better than processing smaller calls14:28
iwamotodoes RPC  timeouts serve any positive purpose?14:28
ajoit makes sense to raise those timeouts by default, message loss is generally a non expected events, stuff could freeze for 3-4 minutes in such case and it'd be ok14:28
*** jlibosva has quit IRC14:28
kevinbentoniwamoto: detecting lost messages14:28
*** jlibosva has joined #openstack-meeting14:28
ajo"a non expected events" -> "a non expected event"14:28
iwamotokevinbenton: doesn't tcp and amqp supposed to handle that?14:29
kevinbentoniwamoto: a server can die after it takes the call message off the queue14:29
salv-orlandoajo: while your claim is questionable about system freeze a timeout should be set in a way that 99% of non-problematic calls typically finish within that time14:29
salv-orlandoso if a call takes over 5secs 50% of time as 5 sec timeout makes no sense, it must be increased14:30
iwamotoso it has some meaning in a active-active setup14:30
kevinbentoniwamoto: yes14:30
ajosalv-orlando, even 99.9% ? :)14:30
ajofailing 1 of 100 non-problematic calls also sounds problematic14:30
ajo:)14:30
*** Guest91794 has quit IRC14:31
salv-orlandoajo: whatever... nines are not my department14:31
salv-orlando;)14:31
ajo:)14:31
ajosalv-orlando, what timeout do we have now by default?14:31
kevinbentoneither 30 or 60 seconds14:31
kevinbentonit comes from oslo messaging i think14:31
salv-orlandokevinbenton: which we arbitrarily chose, didn't we?14:31
salv-orlandoright inherited14:31
salv-orlandoso arbitrary from our perspective14:32
kevinbentonyep14:32
*** merooney has joined #openstack-meeting14:32
amuller60 secs14:32
salv-orlandoI just think a timeout should be set a realistic value wrt to the call you're making14:32
ajoI keep thinking, a certain other number would always be arbitrary...14:32
ajobut for now, higher is better14:32
ajofrom bulk calls perspective14:33
*** bvandenh has quit IRC14:33
salv-orlandoajo: an "educated guess" timeout... not entirely arbitary, come on ;)14:33
ajosalv-orlando, yes that's why I say proportional timeouts could be a better approach looking at the long term14:33
*** xyang1 has joined #openstack-meeting14:33
kevinbentonwhat about one that grows everytime a timeout exception is encountered?14:33
kevinbentonand sleeps in between?!14:34
amullerkevinbenton: you mean like the patch you already have up for review? =D14:34
*** dmorita has joined #openstack-meeting14:34
kevinbentonyeah, that one :)14:34
amullerfunny you should mention it14:34
*** spotz_zzz is now known as spotz14:34
kevinbentonhttps://review.openstack.org/#/c/286405/14:34
ajo+1 for exponential backoffs (not only extra timeout)14:35
kevinbentonThis was all an elaborate setup to get everyone to look at unicode table flipping14:35
*** salv-orlando has quit IRC14:35
haleybthere's a lot of red on that one :)14:35
*** salv-orl_ has joined #openstack-meeting14:35
kevinbentonAdd exponential backoff to RPC client: https://review.openstack.org/#/c/280595/14:35
*** ujuc has joined #openstack-meeting14:36
ajohmm, Kevinbenton++14:36
*** garyk1 has joined #openstack-meeting14:36
* ajo reviews again14:36
iwamotowhat's the point in gradually increasing timeouts?14:36
ajogaryk1, about https://review.openstack.org/#/c/286405/14:37
*** ihrachys has joined #openstack-meeting14:37
kevinbentoniwamoto: to make them larger :)14:37
iwamotowe can have the max from the beginning14:37
ajoI think it could be beneficial now,14:37
ajoand later on that could be addited onto oslo messaging itself14:37
kevinbentoniwamoto: the idea is that you want a timeout still to be able to detect lost messages in a reasonably quick time14:37
*** vhoward has quit IRC14:38
*** dmorita has quit IRC14:38
kevinbentoniwamoto: this allows it to be increased for just calls that trigger timeouts if the configuration setting is too low (which will probably be the case for many deployers)14:38
kevinbentonLet's discuss on that patch14:39
kevinbentondoes anyone have anything else, or can we end the meeting?14:39
*** jproulx has left #openstack-meeting14:39
reedip__I agree with kevinbenton, timeout should be large so that small delays are ignored, but no large that it takes an eternity to get the mesage return back. Keeping it dynamic helps in having the timeout in an acceptble range for ifferent systems14:40
*** mtanino has joined #openstack-meeting14:41
salv-orl_kevinbenton: yay neutron as a learning system....14:41
salv-orl_eventually it will be able to play go14:41
kevinbentonsalv-orl_: i think we need a neural network to determine timeout values14:42
salv-orl_kevinbenton: I think you need some sleep14:42
reedip__kevinbenton: how many layers of neural network do u need??? ;)14:42
ajokevinbenton, I added you a nit comment: https://review.openstack.org/#/c/280595/7/neutron/common/rpc.py14:43
* haleyb buys stock in Skynet :)14:43
amullerkevinbenton: not interested unless it's running on containers14:43
ajoto really make the backoffs exponential too, as literacy suggest14:43
ajoI'm not an expert in fact, just a reader14:44
kevinbentonok14:44
*** yamahata has quit IRC14:44
*** mrmartin has joined #openstack-meeting14:44
kevinbentontime for meeting to be over i think :)14:44
*** synegy34 has joined #openstack-meeting14:44
kevinbentonthanks everyone!14:44
iwamotogood night14:44
kevinbenton#endmeeting14:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:44
openstackMeeting ended Tue Mar 15 14:44:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-15-14.00.html14:44
ajothanks for handling it this early for you!14:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-15-14.00.txt14:44
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-03-15-14.00.log.html14:44
dasmthanks14:44
*** johnsom has left #openstack-meeting14:44
*** keedya has quit IRC14:44
*** pc_m has left #openstack-meeting14:45
*** mrmartin has quit IRC14:45
hichiharakevinbenton: Nice chair! Thanks.14:45
*** zz_dimtruck is now known as dimtruck14:45
*** iwamoto has quit IRC14:45
hichiharabye14:45
mhickeybye, thxs14:45
*** singhj has quit IRC14:45
*** dasm has left #openstack-meeting14:45
*** janzian has left #openstack-meeting14:45
*** boden has left #openstack-meeting14:45
*** jreeves has joined #openstack-meeting14:45
*** zzxwill has joined #openstack-meeting14:47
*** baojg has joined #openstack-meeting14:47
*** gatekeep has quit IRC14:48
*** garyk1 has quit IRC14:49
*** akuznetsov has joined #openstack-meeting14:49
*** bvandenh has joined #openstack-meeting14:49
*** jlibosva has left #openstack-meeting14:50
*** askb has quit IRC14:51
*** dosaboy has quit IRC14:53
*** maishsk has quit IRC14:54
*** dosaboy has joined #openstack-meeting14:54
*** jorge_munoz has joined #openstack-meeting14:54
*** hichihara has quit IRC14:54
*** dosaboy has quit IRC14:55
*** dosaboy has joined #openstack-meeting14:56
*** maishsk has joined #openstack-meeting14:56
*** dosaboy has quit IRC14:57
-openstackstatus- NOTICE: Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue14:57
*** ChanServ changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"14:57
*** zzxwill has quit IRC14:58
*** dane_leblanc has joined #openstack-meeting14:58
*** merooney has quit IRC14:58
*** links has quit IRC14:59
*** ljxiash has quit IRC14:59
*** mlavalle has joined #openstack-meeting14:59
*** singhj has joined #openstack-meeting14:59
mlavalle#startmeeting neutron_routed_networks15:00
openstackMeeting started Tue Mar 15 15:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
*** markvoelker has quit IRC15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_routed_networks)"15:00
openstackThe meeting name has been set to 'neutron_routed_networks'15:00
mlavallehi15:00
xiaohhuihi15:00
reedip__hi15:00
*** bvandenh has quit IRC15:00
*** haomaiwang has quit IRC15:01
mlavalle#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_routed_networks)"15:01
*** mrmartin has joined #openstack-meeting15:01
*** haomaiwang has joined #openstack-meeting15:01
mlavalleAs you know, Neutron RC1 is over or very close to over15:01
mlavalleany other annoucements from the team?15:01
reedip__mlavalle : There are some bugs still left, but armax said it woud be over by tomorrow15:02
mlavalleyeah, I knew it was around today, but not the exact date. Thanks for the clarification :-)15:02
*** jward has joined #openstack-meeting15:02
*** roxanagh_ has joined #openstack-meeting15:02
mlavalleany other annoucements?15:02
*** jward is now known as Guest5282515:03
reedip__not from my end... anyone else?15:03
*** merooney has joined #openstack-meeting15:03
mlavalleok, let's move on15:03
mlavalle#topic Progress15:03
*** openstack changes topic to "Progress (Meeting topic: neutron_routed_networks)"15:03
mlavallereedip__: I think you are working on the client, right? Any progress since last week?15:04
*** azbiswas has joined #openstack-meeting15:04
rtheismlavalle: I have a couple patches for OSC client15:04
reedip__mlavalle : I have put up a WIP fo neutronclient15:04
*** Guest52825 is now known as jward_15:04
rtheishttps://review.openstack.org/#/c/290054/15:04
reedip__and rthies put up some for OSC15:04
rtheishttps://review.openstack.org/#/c/290138/15:04
reedip__for Neutronclient: https://review.openstack.org/#/c/290267/15:05
mlavalleI assume reviews are requested for those patchsets, correct?15:05
reedip__I was thinking of adding the name/description to the segment CRUD : https://review.openstack.org/#/c/284440/615:05
*** xinwu has joined #openstack-meeting15:05
rtheismlavalle: reviews are welcome15:05
*** jward_ has quit IRC15:05
reedip__Sorry, wrong link : http://paste.openstack.org/show/490455/15:06
rtheisBut maybe after reedip__ adds name/description to segment CRUD15:06
reedip__rtheis : ^^ something to check15:06
*** tesseract has joined #openstack-meeting15:06
*** todin has joined #openstack-meeting15:07
reedip__I have the PS ready but just a tad bit cautious of changing the provider_d b15:07
*** dosaboy has joined #openstack-meeting15:07
rtheisreedip__: thanks15:07
*** harshs has joined #openstack-meeting15:07
*** jward_ has joined #openstack-meeting15:07
*** roxanagh_ has quit IRC15:07
*** tesseract is now known as Guest7146715:07
mlavallereedip__: is that a change to Carl's patchset?15:07
reedip__mlavalle: yup15:07
reedip__adding the name/desc  parameter to the segment CRUD15:08
mlavalleI think he made a comment allowing for changes to low hanging fruit, right?15:08
*** IlyaG has joined #openstack-meeting15:09
*** dosaboy has quit IRC15:09
reedip__mlavalle: yup , so I will publsh the PS tomorrow. I also have to create a Migration script15:09
reedip__915:09
reedip__915:09
reedip__( attached in the paste link above)15:09
rtheisthank you reedip__15:09
reedip__as the provider_db has the NetworkSegment class and it needs two new columns for Name/Description ( sorry , the keyboard got stuck... )15:10
rtheisLooks like line 79 in paste link  has a copy/paste error (Add ip_version to AddressScope)15:10
reedip__Yes, it was an already created file, which I just modified for devstack to work15:11
rtheisok15:11
reedip__The migration script was not being generated ( some problem with neutron-db-manage)15:11
reedip__I will take a new checkout of neutron tomorrow and fix that15:11
reedip__anything else for progress?15:11
*** merooney has quit IRC15:11
mlavalleon my side, I have been working on rebasing https://review.openstack.org/#/c/285548/15:12
mlavalleit is not such a simple rebase because modules were deleted from the base patchset15:12
mlavalleso I am moving code around to the new module15:13
mlavalleI expect to push the revision later today15:13
reedip__ok , great ...15:13
*** IlyaG has quit IRC15:13
*** krtaylor has quit IRC15:13
mlavalleI will keep on eye on reedip__ changes becuase I think those will impact my patchsetr15:13
mlavalleI also had a good follow up with the nova team15:13
*** jward_ is now known as jward15:14
reedip__anything important to share with us mlavalle?15:14
mlavallespecifically, I had a conversation with edleafe about nova resource pools https://review.openstack.org/#/c/25318715:14
mlavalleand how it impacted by the roued networks spec on the nova side: https://review.openstack.org/#/c/26389815:15
mlavalleso he made already comments to both specs based on this conversation15:15
mlavalleI will also review both specs between today and tomorrow and will do my best to keep them in synch15:16
mlavalleI also intend to attend the weekly nova meeting this week to draw attention to all this15:16
mlavallethat's all I have as far as progress this week15:17
mlavalleanyone else?15:17
xiaohhuiFor the action in last meeting "Work on plugin interface for host mapping", I have some intial thoughts and send out a mail for discussion. But it is too early to make patch for it now.15:17
* neiljerram arrives late - sorry all!15:17
mlavallexiaohhui: yeah, I saw the email this morning. Thanks. I gave it a first read and looks good to me15:17
xiaohhuithanks15:18
*** vijendar has joined #openstack-meeting15:18
rtheisI have also been investigating the steps to allow neutronclient to support OSC plugin since the home for the CLI may move from OSC core to OSC plugin15:18
rtheisWhich is related to my previous WIP patch sets for the CLI15:18
*** _amrith_ is now known as amrith15:19
mlavallertheis: thanks!15:19
mlavalleany thing else as far as progress?15:19
*** dosaboy has joined #openstack-meeting15:19
reedip__rtheis: any documentation for OSC plugin?15:19
rtheisyes...15:20
*** piet has quit IRC15:20
rtheishttp://docs.openstack.org/developer/python-openstackclient/plugins.html15:20
reedip__rtheis : thanks :)15:20
rtheisI've also pushed a patch to clarify a few things on OSC side: https://review.openstack.org/#/c/292541/15:21
*** fwdit has quit IRC15:21
mlavallertheis: this is not specific to routed networks, right?15:22
rtheiscorrect15:22
mlavalleok, anything else as far as progress?15:22
rtheismlavalle: I think routed networks will just be the first to tackle OSC plugin for neutron15:22
mlavallertheis: ah, ok, that makes sense :-)15:23
mlavalleso, let's move on...15:23
*** vijendar has quit IRC15:23
mlavalle#topic OVN and routed networks15:23
*** openstack changes topic to "OVN and routed networks (Meeting topic: neutron_routed_networks)"15:23
*** azbiswas_ has joined #openstack-meeting15:23
*** yamahata has joined #openstack-meeting15:24
mlavallexiaohhui: I added a topic for OVN to the agenda. Is there anything that you want to add here?15:24
xiaohhuiWith my investigation, I think OVN needs some code change for routed network. I add them in the mail I sent out a litter earlier15:24
xiaohhuinothing else15:24
*** krtaylor has joined #openstack-meeting15:25
mlavallexiaohhui: thank you. If I understood correctly, you sent that email to Carl, Russel and me. If I am correct, I suggest sending it to the ML, so others can chime in...15:25
*** vijendar has joined #openstack-meeting15:26
rtheisyes, that would be good to see15:26
rtheisthanks15:26
*** azbiswas has quit IRC15:26
*** galstrom_zzz is now known as galstrom15:26
mlavalleIMO it always helps to get feedback from the community15:26
xiaohhuiOK, I will send in the mail list15:26
xiaohhuithanks for the suggestion15:26
reedip__m empty ... I agree15:27
mlavalle#topic Open Discussion15:27
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_routed_networks)"15:27
*** salv-orl_ has quit IRC15:27
mlavalleAnything else we should discuss with the team today?15:27
*** pvaneck has joined #openstack-meeting15:27
carl_baldwinHi15:27
reedip__oh hey... he is back15:28
mlavallecarl_baldwin: hey15:28
carl_baldwinJust getting off of D.C. Metro15:28
reedip__Arnold Shwarzennegger of Routed Networks...15:28
*** baojg has quit IRC15:28
rtheisI have a couple questions on user interface which may impact CLI and/or API15:28
carl_baldwinreedip__: wondering if you're creating a new patch set or updating mine.15:29
reedip__carl_baldwin : updating yours15:29
*** harshs has quit IRC15:29
*** armax has joined #openstack-meeting15:29
carl_baldwinreedip__: would you mind creating a follow on patch set?15:29
*** MarkAtwood has joined #openstack-meeting15:29
rtheisWill a segment always be tied to a single network and not standalone or scoped to another resource?15:29
*** akuznetsov has quit IRC15:30
reedip__carl_baldwin : yeah, I can, to keep your work and mine independent (??)15:30
carl_baldwinrtheis: yes15:30
*** jdurgin1 has joined #openstack-meeting15:30
rtheisIs it possible to update any aspects of a segment after created (besides possibly name and description)?15:30
rtheiscarl_baldwin: thank you15:30
carl_baldwinreedip__: minimize scope of each, mostly.15:30
-openstackstatus- NOTICE: Launchpad SSO is back to normal - happy hacking15:31
*** amuller has left #openstack-meeting15:31
*** xyang1 has quit IRC15:31
reedip__carl_baldwin : okay, will put a depends-on ,15:31
carl_baldwinreedip__: that way, they ought to merge earlier.15:31
carl_baldwinreedip__: just make mine the commit's parent.15:32
reedip__Yeah, will check out your code ( PS#6) , make changes and commit as a separate patch ( that would make your PS#6 the parent )15:32
*** askb has joined #openstack-meeting15:33
*** askb has quit IRC15:33
carl_baldwinmlavalle: thanks for running the meeting.  I'll read it all when I can.15:33
carl_baldwinreedip__: cool, thanks15:33
mlavallecarl_baldwin: np, enjoy your vacation :-)15:33
reedip__carl_baldwin: np15:33
*** askb has joined #openstack-meeting15:33
*** david8hu has quit IRC15:34
mlavallecarl_baldwin: rtheis also asked Is it possible to update any aspects of a segment after created (besides possibly name and description)?15:34
*** jlanoux has joined #openstack-meeting15:34
*** xinwu has quit IRC15:34
rtheisAnd finally, when creating a segment via CLI, are there any suggestions for default values?  Right now, all options are required.  Please comment in CLI patch sets if you believe a default makes sense.15:34
*** efried has quit IRC15:35
carl_baldwinrtheis: no, no defaults15:35
*** nmagnezi has quit IRC15:35
rtheiscarl_baldwin: thank you15:36
carl_baldwinrtheis: unless maybe for name when that's a thing15:36
rtheissure15:36
reedip__name as default ? or Update ?15:37
*** vijendar has quit IRC15:37
reedip__I think its for Update15:37
*** Qiming has quit IRC15:38
carl_baldwinreedip__: both, default could be none and it could be updated.15:38
reedip__carl_baldwin : Oh, ok ... but I think the API would be enough to handle it ?15:38
carl_baldwinreedip__: you're right15:38
reedip__I mean no need to define defaults in CLI if the API can handle it for name and description15:38
*** numans has quit IRC15:39
* carl_baldwin on vacation.15:39
*** efried has joined #openstack-meeting15:39
mlavalleok anything else?15:40
rtheismlavalle: I don't have anything else15:40
*** fawadkhaliq has quit IRC15:40
*** fawadkhaliq has joined #openstack-meeting15:40
*** kprabhu has joined #openstack-meeting15:41
mlavalleAll right, thank you for attending and for your updates. Will see you next week (1 hour earlier)15:41
mlavalle#endmeeting15:41
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"15:41
openstackMeeting ended Tue Mar 15 15:41:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
xiaohhuibye~15:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-15-15.00.html15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-15-15.00.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-03-15-15.00.log.html15:41
*** Swami has joined #openstack-meeting15:41
*** egallen has quit IRC15:41
mlavallebye15:42
*** jreeves has left #openstack-meeting15:42
*** baojg has joined #openstack-meeting15:43
*** vishwanathj has joined #openstack-meeting15:43
*** maishsk has quit IRC15:43
*** iceyao has quit IRC15:44
*** vijendar has joined #openstack-meeting15:45
*** fawadkhaliq has quit IRC15:45
*** yamahata has quit IRC15:45
*** sridharg has quit IRC15:46
*** baojg has quit IRC15:48
*** spzala has joined #openstack-meeting15:48
*** egallen has joined #openstack-meeting15:49
*** amrith is now known as _amrith_15:49
*** jungleboyj has joined #openstack-meeting15:49
*** absubram has joined #openstack-meeting15:50
*** tongli has joined #openstack-meeting15:51
*** mlavalle has left #openstack-meeting15:51
*** gyee has joined #openstack-meeting15:51
*** jdurgin1 has quit IRC15:52
*** anilvenkata has quit IRC15:52
*** maishsk has joined #openstack-meeting15:53
*** brucet has joined #openstack-meeting15:55
*** brucet has quit IRC15:55
*** brucet has joined #openstack-meeting15:56
*** asselin__ has joined #openstack-meeting15:57
*** salv-orlando has joined #openstack-meeting15:57
*** asselin_ has quit IRC15:57
*** nkrinner_ has quit IRC15:57
*** roxanaghe has joined #openstack-meeting15:58
*** bogdando has quit IRC15:58
*** links has joined #openstack-meeting15:58
*** adiantum has quit IRC15:59
*** IlyaG has joined #openstack-meeting15:59
jasondotstar#startmeeting openstack-salt16:00
openstackMeeting started Tue Mar 15 16:00:04 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
jasondotstar#topic roll call16:00
*** openstack changes topic to "roll call (Meeting topic: openstack-salt)"16:00
jasondotstaro/16:00
cznewt\o16:00
jasondotstarhi cznewt16:00
liqwo/16:00
*** yuval has quit IRC16:00
jasondotstarhi liqw16:01
*** haomaiwang has quit IRC16:01
cznewthello, last time I tried to chair, was fun, made a few errors though :o :)16:01
*** adahms has quit IRC16:01
cznewtlike wrong start command, luckily did not get recorded :D16:01
jasondotstaryou did a fine job, cznewt - thanks for stepping in! \o/16:01
*** fangzhen has quit IRC16:01
*** 21WAAF8UI has joined #openstack-meeting16:01
*** spzala has quit IRC16:01
jasondotstar#topic Introduction16:02
*** openstack changes topic to "Introduction (Meeting topic: openstack-salt)"16:02
*** mrmartin has quit IRC16:02
jasondotstar    This meeting for the openstack-salt team16:02
jasondotstarif you're interested in contributing to the discussion, please join #openstack-salt16:02
*** spzala has joined #openstack-meeting16:02
jasondotstarmeetings are here, Weekly on Tuesdays at 1600UTC16:02
jasondotstar#link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting16:02
jasondotstar#link https://wiki.openstack.org/wiki/Meetings/openstack-salt16:02
jasondotstar#topic Review past action items16:02
*** openstack changes topic to "Review past action items (Meeting topic: openstack-salt)"16:02
jasondotstarok, let's see... i took a look at last week's meeting notes16:03
*** maishsk has quit IRC16:03
*** asettle has joined #openstack-meeting16:03
jasondotstarhere's what we've got - 1) genunix to continue researching openstack packaging16:03
*** genunix has joined #openstack-meeting16:03
genunixo/16:03
*** _amrith_ is now known as amrith16:04
jasondotstarhi genunix16:04
jasondotstarany status on this item?16:04
*** singhj has quit IRC16:04
genunixno update16:05
jasondotstarnp, let's move it up - if you need someone to take a look at it in parallel, I can possibly help out16:05
genunixbusy with building Debian images+packages for Raspberry :-)16:05
jasondotstar#action genunix to continue researching openstack packaging (with help from jasondotstar)16:06
*** toddjohn has quit IRC16:06
jasondotstarok no worries16:06
*** spzala has quit IRC16:06
jasondotstarthis next one dovetails on it:16:06
jasondotstarcontinue to research building RPMs using the openstack-ci (unassigned)16:06
jasondotstaranyone want to take a look at this one?16:07
jasondotstarif not, I'll help out with this one as well.16:07
jasondotstar#action jasondotstar to research building RPMs using the openstack-ci16:07
jasondotstarok next one:16:08
*** wojdev has quit IRC16:08
jasondotstariceyao to test the centos aio deployment16:08
*** asettle has quit IRC16:08
*** zzxwill has joined #openstack-meeting16:08
*** ramishra has quit IRC16:08
jasondotstardon't see iceyao in chan16:08
*** ninag_ has quit IRC16:09
jasondotstarperhaps iceyao is offline now. one of the reasons we might need to reschedule this meeting to accommodate our far east team members16:09
*** xinwu has joined #openstack-meeting16:10
jasondotstar#action iceyao to continue testing the centos aio deployment16:10
jasondotstarnext:16:10
cznewtyes unfortunately lot of redhat guys is offline16:10
jasondotstaris iceyao from RH?16:10
*** bogdando has joined #openstack-meeting16:10
*** ramishra has joined #openstack-meeting16:10
jasondotstarcznewt: ^16:11
cznewtmeaning redhat salt deploying, not exactly from redhat16:11
jasondotstaroh i gotcha - I'm an RH alum :-)16:11
*** brucet has quit IRC16:11
cznewtfor redhat testing we have done a testing lab16:11
cznewtand most of the issues come from not-openstack related formulas - galera, gluster etc16:12
jasondotstari c16:12
*** maeca has quit IRC16:12
*** brucet has joined #openstack-meeting16:12
cznewtbut we're getting through16:12
jasondotstaryep, looks like it16:12
jasondotstarI'll have to get with you guys on it16:12
*** ninag has joined #openstack-meeting16:12
jasondotstarthere's a special place in my 'heart' for how things work from a RH perspective :->16:12
cznewt:D16:13
jasondotstarso this next one is => prepare the repositories for redhat deployments16:13
jasondotstaragain, along the same lines16:13
*** knikolla has joined #openstack-meeting16:13
cznewtgenunix is doing preliminary preparations16:13
cznewtfor rh repos16:13
jasondotstarok16:13
*** cbader has quit IRC16:13
*** vishwana_ has joined #openstack-meeting16:13
jasondotstargenunix: do you mind if i put your name on this one?16:14
*** spzala has joined #openstack-meeting16:14
*** cbader has joined #openstack-meeting16:14
genunixI think this was up to ali16:14
jasondotstarok16:14
genunixwe currently have RPM repo but only for taking third parties as is, etc.16:14
*** sc68cal has joined #openstack-meeting16:14
genunixno own CI yet16:14
*** mrmartin has joined #openstack-meeting16:14
cznewtyes to clear matter up, we are reusing 3rd parties packages [rdo and contrail]16:15
jasondotstar+116:15
cznewtand for the test lab we'll get these setup properly, I think we have ended up at contrail's gates16:15
jasondotstar#agreed we are currently reusing third party packages [rdo, contrail]16:16
*** armax has quit IRC16:16
*** vishwanathj has quit IRC16:16
cznewtthat except gluster,contrail everything looks fine16:16
jasondotstar#action arif-ali to continue the preparation of the RH repos16:17
jasondotstarok16:17
cznewt+116:17
*** emsomeoneelse has joined #openstack-meeting16:17
jasondotstaranother UNASSIGNED one => look at getting OVS networking working16:17
jasondotstarany takers?16:18
cznewtthis goes the our chinese friend from past meeting16:18
*** ninag has quit IRC16:18
jasondotstar+116:18
*** spzala has quit IRC16:18
*** kzaitsev_mb has quit IRC16:18
cznewtwe don't have capacity to get this working in near future, so anyone's help would be appreciated16:18
jasondotstar#action iceyao to look into getting OVS networking operational16:18
cznewtyes, +116:19
*** egallen has quit IRC16:19
cznewtthe same goes for the next issue16:19
*** ninag has joined #openstack-meeting16:19
*** amrith is now known as _amrith_16:19
jasondotstaragreed16:19
cznewtI think we can merge these 2, as they deal with the same issue16:19
jasondotstar#action iceyao to  get the neutron formula with OVS support ready16:20
*** spzala has joined #openstack-meeting16:20
jasondotstarok16:20
*** zzxwill has quit IRC16:20
*** vishwana_ is now known as vishwanathj16:20
jasondotstarany other items to discuss on the action items from last meeting?16:20
*** ramishra has quit IRC16:21
cznewtI think that's it, all important issues are in today's agenda16:21
*** hashar has quit IRC16:21
jasondotstarok16:21
jasondotstarlet's move on then16:21
jasondotstar#topic Today's Agenda16:21
*** openstack changes topic to "Today's Agenda (Meeting topic: openstack-salt)"16:21
jasondotstarso i guess we didn't have quorum last meeting16:21
*** garthb has joined #openstack-meeting16:21
jasondotstarto discuss: OpenStack summit at Austin develop session (there was no one to discuss this with during last week's meeting)16:21
*** roxanagh_ has joined #openstack-meeting16:22
jasondotstaris everyone attending the Austin Summit in April?16:22
cznewtyes for me16:22
genunixme and cznewt16:22
jasondotstarmy travel is currently pending approval16:22
cznewtI hope it will pass :)16:23
*** ramishra has joined #openstack-meeting16:23
cznewtyou don't have it that far16:23
jasondotstarI am scheduled (booked) to go but we'll see if it is approved16:23
cznewtfingers crossed :)16:23
jasondotstaryeah... the company has an approval process that takes some time so... we'll see16:23
*** mbound has quit IRC16:23
jasondotstarI was in Tokyo... that got approved16:23
jasondotstarbut we'll have to see about TX16:24
cznewtand how is the procedure to get the devel meetup16:24
*** singhj has joined #openstack-meeting16:24
cznewttexas is like 1/10th of the distance :)16:24
cznewtcomparing to japan16:24
jasondotstari know16:24
jasondotstar:-)16:24
*** spzala has quit IRC16:24
jasondotstarso are we thinking of doing a design summit session?16:24
cznewtyes16:24
jasondotstaris that what you mean by devel meetup?16:25
genunixfor sure16:25
jasondotstarwell, we can try to get a room for us16:25
cznewtyes design session16:25
jasondotstarbut I'm not exactly sure how that works16:25
*** drankis has quit IRC16:25
*** markvoelker has joined #openstack-meeting16:25
jasondotstari think there's a sign-up etherpad somewhere (or something)16:25
*** singhj1 has joined #openstack-meeting16:25
*** spzala has joined #openstack-meeting16:25
jasondotstarI hope the window hasn't closed for us though...16:25
jasondotstaranyone in channel know what the procedure is?16:26
cznewtwell, my colleague tells me, that we cannot get design session before we get oficially under openstack16:26
*** roxanaghe has quit IRC16:26
jasondotstarah16:26
jasondotstari c16:26
jasondotstarhave to be a big tent project first (i guess)16:26
jasondotstarin that case16:27
jasondotstarI did see in Tokyo that there were informal meetings16:27
jasondotstarthat were being held in hotel lobbies, and etc.16:28
cznewtbut we have propsed a "Bird of feather" session in which we want to describe real world usage of openstack-salt16:28
jasondotstarwe can look to see if there are any accommodations for that16:29
jasondotstarI know of another effort to put together a BoF16:29
jasondotstarwait, you're saying you've already proposed one16:29
jasondotstarcool16:29
jasondotstarhow much time is it? 45min?16:29
*** ramishra has quit IRC16:30
cznewtthis is Lithium/tcp cloud's usage of openstack-salt16:30
*** spzala has quit IRC16:30
cznewtyes, I think so16:30
*** dmorita has joined #openstack-meeting16:30
*** singhj1 has quit IRC16:30
cznewtWe can look at the informal meetings16:30
*** s3wong has joined #openstack-meeting16:30
jasondotstarright ok16:30
cznewtWhat BoF you were thinking of?16:30
jasondotstar#action Look into scheduling an informal openstack-salt session for our team16:30
jasondotstarcznewt: App Ecosystem WG16:30
*** s3wong has quit IRC16:31
*** tellesnobrega_af is now known as tellesnobrega16:31
jasondotstarthey are putting together a BoF as well - I assist with that team (now) as well.16:31
*** ramishra has joined #openstack-meeting16:31
cznewtWG stands for?16:31
jasondotstarWorking Group16:31
genunix"Working Girl; a call girl or a prostitue."16:31
jasondotstarnoooooooooooooo16:31
*** sdake_ has joined #openstack-meeting16:31
cznewt:D not exactly16:31
jasondotstarnot that.16:31
*** merooney has joined #openstack-meeting16:32
*** roxanagh_ has quit IRC16:32
jasondotstarcareful, sensitive ears here. :-)16:32
jasondotstarbut yes, the AppEcoWG is doing a BoF16:32
*** edtubill has joined #openstack-meeting16:33
cznewtfor the usage of openstack-salt?16:33
jasondotstarI think our best bet is to try and see if there's a place where we can meet informally16:33
*** roxanaghe has joined #openstack-meeting16:33
jasondotstarno not for salt, for their group/team16:33
*** sdake has quit IRC16:34
*** spzala has joined #openstack-meeting16:35
*** Zyric has joined #openstack-meeting16:35
*** vhoward has joined #openstack-meeting16:35
*** rcernin has quit IRC16:35
jasondotstarok16:35
jasondotstarany other discussion on this topic?16:36
cznewtI know the floorplans of the summit building, so it won't be problem to find a suitable place :)16:36
jasondotstarnice!!!16:36
*** Leom has quit IRC16:36
cznewtwe will be placing some environmental sensors there16:36
jasondotstarhehehe... cool16:36
cznewtiqrf mesh network :) yes a side project16:37
cznewtwith positive implications :)16:37
jasondotstarhehehehhe16:37
cznewtbut i think this topic is done16:37
jasondotstarok16:37
cznewtfor today16:37
jasondotstarnext one:16:37
jasondotstarMeeting time change to 14:00 gmt16:37
jasondotstargood thing is, we're expanding our team16:38
*** Zyric has left #openstack-meeting16:38
jasondotstarglad to have more ppl helping out with this effort16:38
cznewtbut it is harder to get 1 time to fit all16:38
jasondotstarperhaps we need to move the meeting time up16:38
jasondotstarcznewt: yep, that's true16:38
jasondotstara couple other teams alternate meeting times16:38
jasondotstarwhich is an option16:38
*** vijendar has quit IRC16:39
jasondotstarbut we have to take into consideration what meeting times are available here in the meeting channel(s)16:39
*** spzala has quit IRC16:39
*** wojdev has joined #openstack-meeting16:39
cznewtyes, we could do alternate times, how does it work? 2 meetings/week different times16:40
jasondotstaris everyone ok with the 1400UTC time slot?16:40
jasondotstarone meeting a week16:40
*** drankis has joined #openstack-meeting16:40
jasondotstaralternating the times each week16:40
cznewtEuropeans are fine, what about you? :)16:40
jasondotstarit's a only a couple hours earlier16:41
jasondotstarshould be fine16:41
*** vijendar has joined #openstack-meeting16:41
jasondotstar#action jasondotstar to check the irc meeting channels for an available meeting slot at 1400UTC16:41
jasondotstarwe may have to change the channel we're in16:41
cznewtit is fine with us, if there is free slot16:41
jasondotstarif not, I'll let you guys know what is avail.16:41
jasondotstarok next:16:42
jasondotstar    Continuing to push the SaltStack on formula integration resolution, e-mailed David Boucha directly for some kind of official reply (http://openstack-salt.tcpcloud.eu/develop/extending-ecosystem.html)16:42
jasondotstar#link http://openstack-salt.tcpcloud.eu/develop/extending-ecosystem.html)16:42
jasondotstar#link http://openstack-salt.tcpcloud.eu/develop/extending-ecosystem.html16:42
*** Guest71467 has quit IRC16:42
cznewtwe are in touch with saltstack (as a company to company) so I've used this channel to address salt internal staff16:43
*** harshs has joined #openstack-meeting16:43
*** piet has joined #openstack-meeting16:43
jasondotstarso we are looking to get these formulas added to the official list of saltstack formulas16:43
jasondotstaris that correct?16:44
jasondotstarmuch like PuppetForge16:44
*** baojg has joined #openstack-meeting16:44
*** scheuran has quit IRC16:44
cznewtyes, more precisely the way to integrate it16:44
jasondotstargotcha16:44
*** kzaitsev_mb has joined #openstack-meeting16:44
jasondotstarcan you keep us updated on the latest on this?16:44
cznewtI've sent something like this: "We are currently setting up the salt based deployment of openstack, however there are many more formulas outside of scope of openstack, which we would like to integrate/merge with official salt formulas. The complete formula ecosystem is summarized here: http://openstack-salt.tcpcloud.eu/develop/extending-ecosystem.html and it consists of about 50 formulas all sharing the same metadata layout. However the integration wi16:44
cznewtyes I will16:44
jasondotstarsounds good116:45
cznewtthis is rather difficult matter for both sides16:45
jasondotstarI'm sure16:45
*** neelashah has quit IRC16:45
jasondotstarlet us know what you need from the team16:45
*** toddjohn has joined #openstack-meeting16:46
*** jschwarz has quit IRC16:46
cznewtyes, exactly16:46
cznewthoping to get progress on this16:46
jasondotstar#action cznewt to update the team on the integration process of our salt formulas with saltstack16:46
*** ygbo has quit IRC16:46
jasondotstarok last topic:16:47
jasondotstarstatus of the CentOS based labs16:47
*** links has quit IRC16:47
jasondotstardoes this fall in iceyao's territory ?16:47
cznewtthis is something we have beeen progressing, from point of setting up metadata and testing if formulas work in general16:47
jasondotstarok16:48
cznewtthis will help iceyao to test his work16:48
jasondotstargotcha16:48
cznewtcan you place this action to 'Tux' user16:49
*** xinwu has quit IRC16:49
jasondotstarhehehe16:49
cznewtas he does all the stack adjustments :)16:49
cznewthe could not attend today's meeting, but has the job almost complete16:49
jasondotstar#action continue to report the status of the CentOS-based labs16:50
cznewtexcept the contrail repo and gluster service16:50
*** mrmartin has quit IRC16:50
jasondotstarcznewt: sounds good. anyone who can report on this feel free to do so16:50
cznewtjasondotstar: perfect :)16:50
*** vijendar has quit IRC16:50
jasondotstarok16:50
jasondotstarfinal 10 mins16:50
*** baojg has quit IRC16:50
jasondotstar#topic Open Discussion, Bug and Review triage (submit modules to triage here)16:50
*** openstack changes topic to "Open Discussion, Bug and Review triage (submit modules to triage here) (Meeting topic: openstack-salt)"16:50
*** apoorvad has joined #openstack-meeting16:51
jasondotstardo I need to list all of the commits that are currently up for review?16:51
*** merooney has quit IRC16:52
*** unicell has quit IRC16:52
*** SumitNaiksatam has quit IRC16:52
cznewtwe have some reviews stuck16:52
cznewtand we have encoutered some issues with new base image16:53
jasondotstarwhich reviews are held up?16:53
cznewthttps://review.openstack.org/#/c/276228/16:53
cznewtthis i cannot abandon at all16:53
cznewtit is completely off as it points to wrong branch16:54
cznewti suppose16:54
*** dprince has quit IRC16:54
jasondotstarhmm16:54
*** dmorita has quit IRC16:54
*** singhj has quit IRC16:54
jasondotstarwe'll have to look at it16:55
*** mbound has joined #openstack-meeting16:55
*** dmorita has joined #openstack-meeting16:56
*** merooney has joined #openstack-meeting16:56
jasondotstarok any others to bring up here?16:56
cznewtand this one16:56
cznewthttps://review.openstack.org/#/c/276353/16:56
cznewtthis does not go thru even though it has many +1s16:57
jasondotstarhmmm16:57
*** dmorita has quit IRC16:57
cznewtand I dont see reason why16:57
*** dmorita has joined #openstack-meeting16:57
*** vijendar has joined #openstack-meeting16:57
cznewtshould we ty to push it by new path set?16:57
jasondotstarwell, i'd like to figure out why it didn't get merged16:58
jasondotstarI +2 merged it16:58
*** e0ne has quit IRC16:58
jasondotstarbut it's not moving16:59
jasondotstaryeah, I don't see why either16:59
cznewtweird, it's minor fix16:59
jasondotstartrue16:59
jasondotstarok, we'll look into it...16:59
*** sc68cal has quit IRC16:59
jasondotstaralright, times up everyone16:59
jasondotstarthanks for joining16:59
jasondotstarsee you guys in channel17:00
jasondotstar#endmeeting17:00
cznewtsee you :)17:00
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"17:00
openstackMeeting ended Tue Mar 15 17:00:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-15-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-15-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_salt/2016/openstack_salt.2016-03-15-16.00.log.html17:00
*** rderose has joined #openstack-meeting17:00
gibi#startmeeting nova notification17:00
openstackMeeting started Tue Mar 15 17:00:23 2016 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova notification)"17:00
jasondotstarthanks cznewt :-)17:00
openstackThe meeting name has been set to 'nova_notification'17:00
gibihi!17:00
*** tsymanczyk has joined #openstack-meeting17:00
*** fawadkhaliq has joined #openstack-meeting17:00
*** 21WAAF8UI has quit IRC17:01
gibirlrossit wont join today due to Daylight Saving Time wonderfullness17:01
*** haomaiwa_ has joined #openstack-meeting17:01
gibianyhow I will summarize the situation for logging purposes17:02
gibiso the last piece of the planned notification work is merged to Mitaka.17:03
gibiNow we have the code in place that detects new legacy notifications in test17:03
*** lpeer has joined #openstack-meeting17:03
gibiand generate a warning runtime17:03
gibiAlso the main notification spec is up for review for Newton17:04
gibiIt already got decent feedback I think we are on the right track with that17:04
*** iyamahat has joined #openstack-meeting17:04
gibiI still have to think about the secondary spec to add jsonschema notifications for the payloads17:05
*** tellesnobrega is now known as tellesnobrega_af17:05
*** tellesnobrega_af is now known as tellesnobrega17:05
*** tellesnobrega is now known as tellesnobrega_af17:05
*** knikolla has quit IRC17:05
*** Leom has joined #openstack-meeting17:06
gibito solve the problem with the DST I will try to find you guys on irc tomorrow17:07
*** neelashah has joined #openstack-meeting17:08
gibilet's close this schizophrenic meeting17:09
gibi#endmeeting17:09
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"17:09
openstackMeeting ended Tue Mar 15 17:09:11 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-15-17.00.html17:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-03-15-17.00.txt17:09
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-03-15-17.00.log.html17:09
*** fawadkhaliq has quit IRC17:10
*** ljxiash has joined #openstack-meeting17:11
*** ivar-lazzaro has joined #openstack-meeting17:11
*** MarkAtwood has quit IRC17:11
*** asselin__ has quit IRC17:11
*** sambetts is now known as sambetts|afk17:12
*** ljxiash has quit IRC17:15
*** merooney has quit IRC17:15
*** henrynash has joined #openstack-meeting17:16
*** fawadkhaliq has joined #openstack-meeting17:18
*** s3wong has joined #openstack-meeting17:18
*** unicell has joined #openstack-meeting17:19
*** asettle has joined #openstack-meeting17:21
*** henrynash has quit IRC17:22
*** merooney has joined #openstack-meeting17:23
*** xinwu has joined #openstack-meeting17:23
*** evgenyf has quit IRC17:24
*** mrmartin has joined #openstack-meeting17:24
*** pcaruana has quit IRC17:24
*** SumitNaiksatam has joined #openstack-meeting17:25
*** fawadkhaliq has quit IRC17:25
*** fawadkhaliq has joined #openstack-meeting17:25
*** iyamahat has quit IRC17:26
*** asettle has quit IRC17:26
*** jlanoux has quit IRC17:27
*** Jezogwza has quit IRC17:27
*** jlanoux has joined #openstack-meeting17:28
*** cschulz has left #openstack-meeting17:28
*** lpeer has quit IRC17:28
*** jlanoux has quit IRC17:28
*** Sudhirverma has joined #openstack-meeting17:28
*** jlanoux has joined #openstack-meeting17:29
*** MaxPC has quit IRC17:30
*** yassine__ has quit IRC17:30
*** matrohon has quit IRC17:31
*** iyamahat has joined #openstack-meeting17:32
*** dprince has joined #openstack-meeting17:33
*** Sukhdev has joined #openstack-meeting17:34
*** knikolla has joined #openstack-meeting17:35
*** Leom has quit IRC17:35
*** spzala has joined #openstack-meeting17:35
*** pcaruana has joined #openstack-meeting17:36
*** lpetrut has quit IRC17:39
*** lhcheng has joined #openstack-meeting17:39
*** sc68cal has joined #openstack-meeting17:39
*** jlanoux has quit IRC17:41
*** vhoward has quit IRC17:41
*** akuznetsov has joined #openstack-meeting17:42
*** azbiswas_ is now known as azbiswas17:42
*** mrmartin has quit IRC17:42
*** ninag has quit IRC17:44
*** carolbarrett has joined #openstack-meeting17:44
*** korzen has quit IRC17:47
*** rossella_s has quit IRC17:47
*** akuznetsov has quit IRC17:48
*** sputnik13 has joined #openstack-meeting17:48
*** aswadr_ has quit IRC17:50
*** mhickey has quit IRC17:50
*** mrmartin has joined #openstack-meeting17:51
*** salv-orl_ has joined #openstack-meeting17:54
*** irenab has quit IRC17:55
*** salv-orlando has quit IRC17:56
*** irenab has joined #openstack-meeting17:56
*** irenab has quit IRC17:57
*** merooney has quit IRC17:57
*** ihrachys has quit IRC17:58
*** ninag has joined #openstack-meeting17:59
*** merooney has joined #openstack-meeting17:59
*** klkumar has quit IRC17:59
stevemarreminder ping for keystone meeting: 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_m17:59
stevemarunoz17:59
stevemarjorge_munoz: ^17:59
lbragstado/17:59
rodrigodshello :)17:59
lhchengo/17:59
ayoungHeh  we got long....17:59
stevemaro/18:00
gyee\o18:00
raildohello \o18:00
stevemarayoung: i think we can axe some of those names18:00
*** shaleh has joined #openstack-meeting18:00
ayoungI wonder if we can drop some of the notifications18:00
shaleh\o18:00
tjcocozzo/18:00
*** edmondsw has joined #openstack-meeting18:00
*** browne has joined #openstack-meeting18:00
claudiubo/18:00
*** Sukhdev has quit IRC18:00
browneo/18:00
ayoungor tell people to shortend their nicknames18:00
stevemarericksonsantos and geoffarnold haven't been around in a while18:00
topolo/18:00
ayoungI mean jamielennox?  really18:01
*** haomaiwa_ has quit IRC18:01
knikollao/18:01
stevemarnot sure who maxPC is either18:01
roxanagheo/18:01
ayoungstevemar, he's my Product Manager18:01
stevemarsounds like a computer repair company from the 90s18:01
*** paul-carlton2 has joined #openstack-meeting18:01
stevemarah18:01
*** haomaiwang has joined #openstack-meeting18:01
*** dmorita has quit IRC18:01
*** wojdev has quit IRC18:01
*** jamielennox has joined #openstack-meeting18:01
stevemari agree though, jamielennox is far too many characters18:02
bknudsonwe should get our product managers in here18:02
jamielennoxi disagree18:02
stevemarbknudson: zman18:02
jamielennoxi think18:02
*** slunkad has quit IRC18:02
jamielennoxi didn't see the original statement18:02
ayoungbknudson, jamielennox we need to compact the notifications line18:02
stevemarjamielennox: of course you didn't18:02
ayoungpoor jorge_munoz got cut in half18:02
samueldmqhello everyone18:02
stevemaralright, enough banter :)18:02
stevemar#startmeeting keystone18:02
ayoungnow xek is a nickname I can get behind18:02
openstackMeeting started Tue Mar 15 18:02:53 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
*** irenab has joined #openstack-meeting18:02
shalehstevebaker: geoffarnold is not coming back in a while. He went of to a IoT startup18:02
stevemarshaleh: coolio18:03
stevemari'll trim it18:03
*** _nadya_ has quit IRC18:03
stevemaragenda: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:03
stevemar#topic Keystone RC status18:03
*** openstack changes topic to "Keystone RC status (Meeting topic: keystone)"18:03
stevemar#link https://launchpad.net/keystone/+milestone/mitaka-rc118:03
*** dmorita has joined #openstack-meeting18:03
*** dims_ has joined #openstack-meeting18:03
*** dims has quit IRC18:03
ayounglove the number of non-core stepping up to fix bugs18:04
*** singhj has joined #openstack-meeting18:04
morganjust do cleanup on the ping notices at the start of the cycle18:04
morganeasiest way to do cleanup18:04
stevemari went ahead and marked a few bugs with rc1 target dates18:04
stevemari find that easier than the tags18:04
stevemari don't think any are show-stoppers, but a few would be nice to fix by end of week, then we can cut RC118:04
stevemarmost are in progress, and can be viewed here: https://review.openstack.org/#/dashboard/?foreach=&title=Keystone+Office+Hours&patches+that+don%27t+have+negative+feedback+and+close+a+bug=project%3A%22%5Eopenstack%2F%40keystone%40%22+%2Dproject%3Aopenstack%2Fpuppet%2Dkeystone+is%3Aopen+label%3AVerified%2B1+%2Dlabel%3ACode%2DReview%3C%3D%2B2%2Cself+%2Dlabel%3ACode%2DReview%3C%3D%2D1+%2Dlabel%3AVerified%2D1+%2Dlabel%3AWo18:06
stevemarrkflow%2D1+AND+%28message%3A%22Closes%2D%22+OR+message%3A%22closes%2D%22%29&bug+related+patches+that+don%27t+have+negative+feedback=project%3A%22%5Eopenstack%2F%40keystone%40%22+%2Dproject%3Aopenstack%2Fpuppet%2Dkeystone+is%3Aopen+label%3AVerified%2B1+%2Dlabel%3ACode%2DReview%3C%3D%2B2%2Cself+%2Dlabel%3ACode%2DReview%3C%3D%2D1+%2Dlabel%3AVerified%2D1+%2Dlabel%3AWorkflow%2D1+AND+%28message%3A%22Closes%2D%22+OR+messag18:06
stevemare%3A%22Partial%2D%22+OR+message%3A%22Related%2D%22+OR+message%3A%22closes%2D%22+OR+message%3A%22partial%2D%22+OR+message%3A%22related%2D%22%29&bug+related+patches+that+need+love=project%3A%22%5Eopenstack%2F%40keystone%40%22+%2Dproject%3Aopenstack%2Fpuppet%2Dkeystone+is%3Aopen+%2Dlabel%3ACode%2DReview%3C%3D%2B2%2Cself+label%3ACode%2DReview%3C%3D%2D1+AND+%28message%3A%22Closes%2D%22+OR+message%3A%22Partial%2D%22+OR+me18:06
stevemarssage%3A%22Related%2D%22+OR+message%3A%22closes%2D%22+OR+message%3A%22partial%2D%22+OR+message%3A%22related%2D%22%2918:06
bknudsonwow!18:06
stevemarwell that didn't work18:06
dstanekwhoa18:06
morganstevemar: yeah that wont work.18:06
samueldmqI am copying and pasting the bits together18:06
morganneed a url shortener or something18:06
samueldmqwait18:06
*** Shrews has joined #openstack-meeting18:06
samueldmq:-)18:06
stevemarhttps://goo.gl/d7yp6B18:06
stevemarthere we go18:06
samueldmqstevemar: ++18:06
rodrigodshaha18:06
stevemarsaving it as a bookmark doesn't quite help :P18:07
gyeestevemar, would love to see this one added to the list, https://bugs.launchpad.net/keystone/+bug/155723818:07
openstackLaunchpad bug 1557238 in OpenStack Identity (keystone) "mapping yield no valid identity result in HTTP 500 error" [High,New]18:07
shalehI have been beating up on the "need love" section. The dates are all fairly recent.18:07
stevemargyee: yep, that is a must fix18:07
*** kzaitsev_mb has quit IRC18:07
gyeestevemar, I am working on a fix18:07
*** dmorita has quit IRC18:07
stevemarwould also be nice to see bug 1526462 and bug 1555830 fixed too18:08
openstackbug 1526462 in OpenStack Identity (keystone) "Need support for OpenDirectory in LDAP driver" [Medium,In progress] https://launchpad.net/bugs/1526462 - Assigned to Andrey Grebennikov (agrebennikov)18:08
openstackbug 1555830 in python-openstackclient "'service provider show' returns a service provider when queried with wrong sp_id" [Medium,In progress] https://launchpad.net/bugs/1555830 - Assigned to Steve Martinelli (stevemar)18:08
*** dmorita has joined #openstack-meeting18:08
stevemari'll be poking people for reviews and fixes this week18:08
stevemarlooking forward to cutting rc118:08
stevemarany questions about rc1? any super important stuff we're not including?18:08
shalehif Jamie will drop his request password in CLI review and Boris drops his two reviews all of the "need love" are now current as of 201618:09
bknudsonthe gate's not broken so I think we're doing good18:09
shalehbknudson: ++18:09
stevemarbknudson: your bar is low18:09
samueldmqstevemar: when do you want to cut it?18:09
stevemarsamueldmq: any time before friday evening :P18:09
*** mrmartin has quit IRC18:10
topolbknudson is soooo snarky :-)18:10
stevemarwe could always cut rc2 next week18:10
samueldmqstevemar: ++18:10
stevemari think this week is march break for folks, so we might get impacted a bit18:10
gyeeeasy as cutting cheese18:10
morganshaleh: password in cli?18:10
bknudsonmarch break must be a canada thing18:11
stevemarbknudson: damn canucks18:11
bknudsonit's march madness here18:11
shalehmorgan: yes, his patch which added the password prompt which you and I poo'ed on.18:11
shalehmorgan: it was never abandoned.18:11
stevemarshaleh: that's not keystone server side though18:11
jamielennoxis that still open?18:11
morganshaleh: oh the one i hit with a -2? ;)18:11
*** terriyu has joined #openstack-meeting18:11
shalehjamielennox: yes18:11
ayoungspring break here.  Which is dumb as it is technically still winter18:12
shalehstevemar: it is on your list :-)18:12
stevemarshaleh: :O18:12
stevemarshaleh: must impact several projects then, doh18:12
stevemaranywho i'll be trying to close these out, help is appreciated :)18:13
stevemarnext topic18:13
stevemar#topic Devstack keystone deploy18:13
*** openstack changes topic to "Devstack keystone deploy (Meeting topic: keystone)"18:13
stevemarbknudson: your're up18:13
stevemarbknudson: this work has been freaking awesome18:13
bknudsonso I proposed a change to devstack to run keystone under uwsgi while apache proxies using mod_proxy_uwsgi18:13
bknudsonwe've got several deploy options now.18:14
topolbknudson that is very cool18:14
bknudsonwhich I'd like to whittle down once we've seen that things are stable18:14
bknudsonwe'll get rid of eventlet in N18:14
stevemarwe've got eventlet / apache / uwsgi / uwsgi_apache18:14
gyeebknudson, we have separate log files under uwsgi or that configurable?18:14
bknudsondevstack has separate log file under uwsgi18:14
*** Sudhirverma has quit IRC18:15
bknudsonlogging is almost infinitely configurable so you could set up syslog if you want18:15
gyeelike /var/log/apache218:15
bknudsonideally we'll eventually get to 1 server18:15
gyeeor now I have to look for stuff in say /var/log/uwsgi or something18:15
*** lpetrut has joined #openstack-meeting18:15
stevemarthis is great because we can show operators that keystone can is tested and can be deployed many ways, and it's safe to remove eventlet18:15
shalehbknudson: has that devstack change landed or do we still need to pull it?18:15
edmondswI'd really like to see this go in: https://bugs.launchpad.net/keystone/+bug/155321618:15
openstackLaunchpad bug 1553216 in OpenStack Identity (keystone) "keystone-manage bootstrap does not work for non-SQL identity drivers" [Medium,In progress] - Assigned to Kristi Nikolla (knikolla)18:15
stevemarshaleh: most are landed18:15
bknudsonshaleh: the devstack change has not landed18:16
*** askb has quit IRC18:16
ayoungunder uwsgi is there any SAML  support?  Can we test Federation in devstack?18:16
bknudsonso comments now are welcome18:16
stevemarshaleh and others: https://review.openstack.org/#/c/291817/18:16
bknudsonayoung: under uwsgi there would not be SAML support18:16
morganayoung: you would still use apache18:16
*** mrmartin has joined #openstack-meeting18:16
bknudsonayoung: but mod_proxy_uwsgi should work18:16
morganayoung: for saml, uwsgi replaces eventlet/mod_wsgi18:16
jamielennoxbknudson: why would there be no saml support?18:16
morganayoung: what bknudson said18:16
stevemarayoung: not when deployed only under uwsgi (which is a crummy stand alone web server anyway)18:17
*** _nadya_ has joined #openstack-meeting18:17
bknudsonjamielennox: you need some kind of plugin to accept the saml. uwsgi doesn't have it18:17
ayoungstevemar, I just want the testability18:17
morgannginx also could do saml now [it has a shib module]18:17
stevemarayoung: it should be testable under the uwsgi_apache configuration18:17
*** Leom has joined #openstack-meeting18:17
shalehayoung: try his patches and report success/fail :-)18:17
ayoungstevemar, fair enough18:17
morganand uwsgi is natively supported by nginx18:17
jamielennoxbknudson: yes, but mod_proxy_uwsgi should forward envs to the uwsgi application18:17
bknudsonjamielennox: right (I thought you were asking about uwsgi http)18:18
jamielennoxbknudson: i have confirmed this as far as doing SetEnvs in the apache config, but i don't have a real test yet18:18
*** ijw has joined #openstack-meeting18:18
bknudsonwe've got a uwsgi http deployment too18:18
jamielennoxoh, i just assumed we were talking behind apache because of $subject18:18
bknudsonanyway, the plan would be to get rid of the uwsgi http deployment and do the proxy instead of that one18:18
stevemaryep18:19
stevemarnice work on that stuff bknudson18:19
bknudsonand maybe we can even convince other api servers to work this way18:19
stevemarit provides me with the ammo i need to remove eventlet18:19
shalehbknudson: once we show it works....18:19
bknudsonwe've been running the uwsgi test for a while now and it seems stable18:19
jamielennoxit's a good solution for the mod_wsgi virtualenv problem18:19
jamielennoxfor the people stuck on eventlet18:20
bknudsonso I'll add a job for uwsgi-proxy once it's merged in devstack18:20
shalehthis is good work bknudson. I have been wanting to find time for this since I started hacking on keystone.18:20
stevemarbknudson: want to remove the regular uwsgi job?18:20
gyeeshaleh, works as somebody running it in production :-)18:20
bknudsonshaleh: take a look at the reviews and see if it's what you're were planning on18:20
shalehgyee: yeah, or at least closer to it.18:20
bknudsonstevemar: the regular uwsgi should go away once we've got uwsgi-proxy18:21
*** haukebruno has quit IRC18:21
shalehbknudson: shall do.18:21
stevemarbknudson: alrighty18:21
jamielennoxbknudson: so a problem i'm found is that the ubuntu 14.04 uwsg_proxy is really old and won't work with the one from pip18:21
bknudsonjamielennox: really? worked for me.18:21
stevemarso if you're interested look up bknudson's reviews18:21
bknudsonjamielennox: I noticed it was old and didn't support unix socket :(18:21
stevemarjamielennox: i pulled it down and it worked for me on 14.0418:21
*** terriyu has quit IRC18:22
jamielennoxstevemar: intsalling from pip or apt?18:22
jamielennoxapt has some 1.x version, and apache is too old for the unix socket thing18:22
bknudsonuwsgi_proxy is from apt, uwsgi is from pip18:22
stevemarjamielennox: whatever bknudson's patch doe18:22
stevemars18:22
jamielennoxdamn, i got super strange errors for that which i attributed to the difference18:22
jamielennoxmine is running via emperor, rather than directly but that shouldn't matter18:23
*** timcline has joined #openstack-meeting18:23
bknudsonunix socket would be ideal but we can live with localhost until the distro is newer18:23
morganbknudson: 14.04 supports the socket doesn't it?18:23
bknudsonemperor seemed like overkill18:23
*** _nadya_ has quit IRC18:23
morganoh wait uwsgi_proxy is weird.18:23
bknudsonmorgan: I assume the socket connection has been there since the beginning18:23
gyeeif you are doing proxying, why would you want to run on anything other than localhost?18:23
jamielennoxbknudson: for devstack it is because you want things in screen, for ~prod emperor seems right18:24
morgangyee: unix domain socket = better than localhost18:24
morganfor uwsgi/uwsgi_proxy18:24
stevemargetting a bit off topic, if you're having trouble with the patch we can talk about it in -keystone18:24
*** timcline has quit IRC18:24
stevemar#topic Keystone Client Functional tests -- samueldmq18:25
*** openstack changes topic to "Keystone Client Functional tests -- samueldmq (Meeting topic: keystone)"18:25
stevemarsamueldmq: sir18:25
*** timcline has joined #openstack-meeting18:25
tsymanczyk\o18:25
samueldmqhi18:25
samueldmqso, goal is to implement functional tests in ksclient18:25
samueldmqlater on, this will serve to improve our backward compatibility for client libraries18:26
*** MaxPC has joined #openstack-meeting18:26
samueldmq#link https://review.openstack.org/#/c/226157/18:26
*** safchain has quit IRC18:26
*** maeca has joined #openstack-meeting18:26
samueldmqwe've got the base stuff merged, which basically instatiates the ksclient instances based on os-cloud-config18:26
stevemarlooks like your changes are here: https://review.openstack.org/#/q/status:open+project:openstack/python-keystoneclient+branch:master+topic:client-functional-tests18:26
samueldmqwhich looks for clouds.yaml and envvars18:27
bknudsonare these tests in gate already?18:27
samueldmqstevemar: yes, the changes we have now are in that topi18:27
samueldmqbknudson: yes, we do have a gate job for functioanl ksclient tests18:27
stevemarbknudson: there is a functional test job that does the existing tempest tests18:27
*** baoli_ has quit IRC18:27
samueldmqe.g look at patch 29304818:27
*** IlyaG has quit IRC18:27
samueldmqand see gate-keystoneclient-dsvm-functional18:27
*** pabelanger has joined #openstack-meeting18:28
stevemarthe job does a dsvm setup18:28
*** piet has quit IRC18:28
stevemarsamueldmq: the tests are run as admin right?18:28
*** terriyu has joined #openstack-meeting18:28
samueldmqstevemar: afaik yes, that's the creds put in clouds.yaml18:28
*** e0ne has joined #openstack-meeting18:28
rodrigodssamueldmq, stevemar the job itself gets the env vars18:28
*** piet has joined #openstack-meeting18:28
bknudsonhere's an example running the new tests -- http://logs.openstack.org/06/289306/7/check/gate-keystoneclient-dsvm-functional/b86148a/console.html#_2016-03-14_18_16_59_74718:28
*** azbiswas has quit IRC18:28
*** mrmartin has quit IRC18:29
*** dims_ has quit IRC18:29
samueldmqbknudson: ++18:29
rodrigodshttps://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/tests/functional/hooks/post_test_hook.sh#L3318:29
stevemarso the benefit of this is testing real CRUD requests and responses18:29
rodrigodsadmin admin :)18:29
samueldmqrodrigods: nice, I haven't checked that yet18:29
stevemarand making sure the managers and client actually work properly18:29
samueldmqstevemar: yes, from a client perspective VS testing the http api itself18:29
rodrigodsstevemar, it is easier to test there18:30
rodrigodsthan having a devstack plugin and so on18:30
stevemarso this tests against the same setup every time18:30
rodrigodsthat's how i see it besides the client + API testing18:30
samueldmqstevemar: and also as I noted above, there is an ongoing effort for having backwards compat for libraries and clients18:30
stevemaryep18:30
samueldmqin which case it's super useful18:30
samueldmqand anyone can run it by just providing a clouds.yaml or envvars18:31
shalehsamueldmq: so this is run via tempest?18:31
rodrigodsshaleh, no18:31
stevemarshaleh: nope18:31
bknudsonI guess it's not too important to support different deployments if it's for verifying that the client API works.18:31
stevemartempest is read-only and black box18:31
stevemarbknudson: that's what i'm beginning to wonder18:31
samueldmqshaleh: and tempest has its own client, and its goal is to test the http api18:32
stevemarbknudson: cause on the server side, i always imagined different jobs setting up different keystone configurations and running functional tests there18:32
samueldmqstevemar: ours is to test the client18:32
*** carolbarrett has quit IRC18:32
rodrigodsstevemar, ++18:32
samueldmqbknudson: maybe, but we also allow for other to run the tests18:32
dstanekstevemar: exactly. that's where the value is on the server18:32
*** pece has quit IRC18:32
*** brucet has quit IRC18:33
stevemardstanek: but if we already have a suite of tests in ksc, why not add tests there18:33
raildostevemar: like setting different tokens types :)18:33
stevemaranyway, details18:33
*** Sudhirverma has joined #openstack-meeting18:33
bknudsongood to have though. The unit tests are fine but they can only mock the server response and we've made mistakes there18:33
rodrigods++18:33
stevemarbknudson: for sure18:33
samueldmqhmm, so the question is, what does this buy us?18:33
samueldmqdo real tests in the client, not just mocking18:33
stevemarsamueldmq: testing without mock18:33
dstanekstevemar: we could do that. the only thing i care about on the server side is the profiles18:34
samueldmqyes what bknudson said18:34
*** sdake_ has quit IRC18:34
stevemardstanek: profiles == different configurations?18:34
shalehso does this mean a review of current unit tests to consider which are truly unit and which should really be functional?18:34
bknudsonfunctional tests in keystone we will want to be able to run against any config18:34
dstanekstevemar: we initially made the decision to not write our functional tests using ksc so that we don't tie ourselves to it18:34
dstanekstevemar: yes18:34
navidpstevemar,18:35
stevemarnavidp:18:35
stevemar:)18:35
samueldmqwe could still ahve functional tests in keystone18:35
navidpstevemar, about this https://review.openstack.org/#/c/226157/ I am getting tempest error because it is not using ksa, is there a way to make tempest to use it or get a ksa release.18:35
samueldmqto test against the real HTTP API18:35
samueldmqthe client tests are for testing the client, not really into HTTP API details18:35
stevemardstanek: fair enough18:36
navidpstevemar, the modifications i need is in this patch : https://review.openstack.org/#/c/289472/18:36
dstanekstevemar: i don't know if that's completely valid, but that's what we decided18:36
stevemarnavidp: mind if i circle back to you in 25 minutes? i don't want to derail the meeting18:36
*** igorbelikov has joined #openstack-meeting18:36
samueldmqnavidp: looks like it's better to discuss off-topic in #keystone or in the open-discussion topic taht will come later on ?18:37
*** eil397 has joined #openstack-meeting18:37
stevemardstanek: i imagine we will talk about this at length at the summit18:37
samueldmqnavidp: yes, what stevemar said, thank you18:37
navidpstevemar, ok thanks18:37
stevemarnext topic18:37
stevemar#topic Revert change that removed the default domain creation -- stevemar18:37
*** openstack changes topic to "Revert change that removed the default domain creation -- stevemar (Meeting topic: keystone)"18:37
navidpstevemar, sorry18:37
stevemarnavidp: np!18:37
stevemari don't know about others, but i've seen quite a few questions surrounding this topic18:38
stevemarquite a few == 3 in one week18:38
*** carolbarrett has joined #openstack-meeting18:38
stevemarwhere folks are asking "wheres my default domain"18:38
dstanekstevemar: doesn't it get created on demand if it doesn't exist?18:38
stevemari guess they are installing and using the ADMIN token, and going right to the user create portion18:38
bknudsonwe never guaranteed there'd be a default domain18:38
*** merooney has quit IRC18:38
stevemarbknudson: it's a major change in behavior though -- guaranteed or not18:39
stevemardstanek: not entirely...18:39
gyeedstanek, will create it when migrating v2 data18:39
stevemardstanek: we made a change to include it in user/project show/list18:39
*** jichen has joined #openstack-meeting18:40
bknudsonit seems like all people use openstack for is deploying it18:40
stevemarlol18:40
ayoungso the error is that we are not creating it on demand in user create?18:40
stevemarayoung: or project create18:40
bknudsoncurrently it's only v2 operations that create on demand18:41
stevemarayoung: we used to create it after the first migration ran18:41
bknudsonI figured it was only backwards tools that would be affected18:41
ayoungOny in v2 operations....18:41
bknudsonwould be easy enough to create on demand for v3 ops, too. Although unfortunate.18:41
bknudsonwe could put out a deprecation message when created on demand18:41
gyeebknudon, how?18:42
stevemarbknudson: now you're thinking18:42
gyeeare we going to create every missing domain on v3 operations?18:42
stevemargyee: if we end up creating it, issue the message?18:42
bknudsonno, only the default domain (it's in the config file)18:42
*** iyamahat has quit IRC18:42
ayounggyee, no, only if it matches the default in the config file18:42
jamielennoxwhere would you put that message?18:42
*** terriyu has quit IRC18:42
bknudsonthe message goes to the keystone log18:42
jamielennoxif you do it once in the admin log it will get lost18:42
jamielennoxand you can't do it to the user18:43
ayoungmeans we will never be able to delete the default domain.18:43
ayoungIt will just get recreated18:43
bknudsonthis is for deploy so hopefully they're checking the keystone log at the end of their deploy18:43
gyeethat's dangerous18:43
gyeefor v3 APIs, user or project creation requires a domain_id18:43
*** jdob1 has joined #openstack-meeting18:43
gyeeand if domain doesn't exist, they have to create it18:44
*** haleyb_ has quit IRC18:44
gyeewhy make the exception for default domain?18:44
stevemari'm okay with no making a decision here, we can always wait til next week, maybe we just need better docs18:44
bknudsongyee: the exception is for backwards-compat until we can convince people to not rely on default domain existing18:44
samueldmqstevemar: maybe18:45
*** maeca has quit IRC18:45
samueldmqstevemar: if they want to sue v3, then create the domain18:45
gyeeexactly18:45
samueldmqdefault domain is only for v2 compatibility, as far as I understand it18:45
stevemarsamueldmq: yep, then deploy instructions should be updated as such18:45
gyeev3 is a major version bump, not meant for backward compatibility18:45
rodrigodsit is used for more stuff18:45
samueldmqstevemar: 100% agree we should check the docs18:45
stevemarsamueldmq: either create the default domain with ADMIN_TOKEN, or as part of bootstrap18:45
samueldmqstevemar: if you're going to use v3 (and we wnat you to)18:46
*** brucet has joined #openstack-meeting18:46
stevemaranywho, next topic18:46
stevemar#topic parent_id representation in Liberty vs Mitaka - rodrigods18:46
*** openstack changes topic to "parent_id representation in Liberty vs Mitaka - rodrigods (Meeting topic: keystone)"18:46
*** baojg has joined #openstack-meeting18:46
stevemarmy topic can wait, whats up rodrigods18:47
rodrigodso/18:47
rodrigodsok... so in Liberty (and Kilo), the absence of parent was presented by parent_id = None, today it is represented by the domain_id (since the "root" is a project acting as domain)18:47
rodrigodsso... this means that *probably*, the nested quota code is broken in Cinder18:47
rodrigodssee https://review.openstack.org/#/c/285541/18:47
samueldmqI though henrynash had worked with cinder to fix that18:48
*** Ravikiran_K has quit IRC18:48
*** paul-carlton2 has quit IRC18:48
samueldmqrodrigods: is that the issue that previous top-lvel projects had parent_id = None and now they point to their domain (which is also a project)?18:48
rodrigodsanyway... Cinder was just an example18:48
stevemarrodrigods: did cinder have full support for nested quotas in liberty?18:48
rodrigodssamueldmq, yes18:48
*** asettle has joined #openstack-meeting18:48
raildostevemar: yes18:48
*** _amrith_ is now known as amrith18:49
*** AJaeger has joined #openstack-meeting18:49
stevemarguess we need to compare the parent_id to the domain_id then?18:49
rodrigodsI can write a config in tempest to skip the tests in the stable tests18:49
rodrigodsjust want your opinion if this is ok, in a API stability point of view18:50
samueldmqhenrynash told me Cinder had fixed that18:50
dstanekrodrigods: so this was a backward incompatible change?18:50
rodrigodsdstanek, yes18:50
samueldmqat least that was a pre-requisite to merge reseller-118:50
stevemarhenrynash is away this week, should be back tomorrow18:50
samueldmqbecause gate was failing18:50
*** e0ne_ has joined #openstack-meeting18:50
samueldmqstevemar: yes, but reseller-1 couldn't merge without fixing it, anyways need to check with him18:50
ayoungraildo, you said this might  impact Quota, right?18:50
*** e0ne has quit IRC18:51
dstanekdo we need to roll it back?18:51
*** vijendar has quit IRC18:51
ayoungand we're going to get a test which shows that or not18:51
*** baojg has quit IRC18:51
raildoayoung: yes, I'm not sure that will impact, I need to test it.18:51
*** spzala has quit IRC18:51
ayoungLet's gate on that18:51
rodrigodsyou can try to run https://review.openstack.org/#/c/285640/18:51
*** julenl has quit IRC18:51
rodrigodsyou need to setup everything in devstack first18:51
ayoungif Cinder is OK with the change, we accept the new behavior. If Cinder breaks, we work with them to deal with it?18:51
samueldmqdstanek: that was a question I had ... if changing the content of an API was acceptable18:51
rodrigodsdidn't do that here yet, but since henrynash has fixed it18:52
raildoprobably this patch it is what samueldmq are saying: https://review.openstack.org/#/c/286775/18:52
rodrigodswe should be fine18:52
*** beekhof has quit IRC18:52
samueldmqraildo: yes I think that's it18:52
rodrigodsbut yes, the API in Mitaka incompatible with Liberty/Kilo18:52
dstaneksamueldmq: that's the thing. it may seem like just changing the value of a key, but we are changing the semantics of what the keys mean (at least that's what i get from the problem description)18:52
*** PsionTheory has joined #openstack-meeting18:52
*** asettle has quit IRC18:53
*** electrofelix has quit IRC18:53
stevemardstanek: that's how i understand it18:53
ayoungdstanek, the question is if we ever documented it18:53
ayoungand, if we did, what did we commit to supporting18:53
samueldmqdstanek: stevemar: I had that question when reviewing reseller-1, and I got convinced that this was acceptable somehow18:53
*** julenl has joined #openstack-meeting18:53
samueldmqmaybe we need to circle-back and re-analyze it18:53
samueldmqwe need henrynash on this I think18:54
ayoungin this case, I would say that HMT is early enough that we can accept some wiggle room here18:54
stevemarayoung: yep18:54
stevemarsamueldmq: i think we're okay here, like ayoung said it's early18:54
rodrigodsgreat18:54
stevemar#topic open discussion18:55
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:55
samueldmqstevemar: okay, just saying it sounded weird to me too, to change the return (the body) of an API18:55
dstanekis HMT declared to be experimental?18:55
ayoungraildo, can you own not only the test, but confirming with all quota folks that the issue is real or not?18:55
*** browne has left #openstack-meeting18:55
rodrigodsdstanek, it is not18:55
*** jdob1 has quit IRC18:55
rodrigodswas not too18:55
raildoayoung: sure, I'll do this, asap18:55
ayoungstevemar, so, the Rabbit MQ deployment setup sucks.18:55
ayoungThis is not strictly a Keystone issue18:55
stevemarayoung: what's so sucky about it?18:55
ayoungbut, it does mean that, say, audit events could be faked18:55
stevemarmfisch also didn't like rabbit18:56
ayoungstevemar, its not rabbit so much as what we don't do18:56
ayoungeverything runs as a single user, single password18:56
*** Sudhirverma has quit IRC18:56
dstanekrodrigods: should it be so that we can make breaking changes like this?18:56
ayoungIts not really our problem to solve, except maybe to look into how we could fix things from the Keystone side18:57
*** rcarrillocruz has joined #openstack-meeting18:57
rodrigodsdstanek, never was marked as experimental, but we never had HMT tests in tempest so...18:57
stevemarayoung: i'm not following you completely... but it doesn't sound good18:57
ayoungthere are config options for changing things, like where to publish notifications18:57
rodrigodsdstanek, i mean, never had any tests to alarm this18:57
rodrigodsin gate18:57
ayoungstevemar, so, it is not good, but it is a deployers problem.18:58
dstanekrodrigods: sure, but what i'm saying is that since this is an experimental feature, we should label it as experimental18:58
ayoungI have not run devstack in a while, but if what I am seeing is that everyone is following devstack's approach, then messaging is a very insecure18:58
bknudsonhard to be experimental when you change the project response18:58
ayoungstevemar, here's the crux18:59
stevemarayoung: you are probably seeing what everyone else is, so yeah, probably insecure18:59
ayoungwe really need to be able to identify all of the readers and writers in an openstack deployment18:59
stevemaryou can change the topic very easily18:59
ayoungand this is an identity problem18:59
gyeeayoung, we never said devstack is secured :-)18:59
ayoungwhich is basically a keystone bailywick18:59
stevemar<1 minute to go19:00
*** olaph has joined #openstack-meeting19:00
stevemardamn19:00
bknudsontokens for messages, too19:00
stevemar#endmeeting19:00
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"19:00
openstackMeeting ended Tue Mar 15 19:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-15-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-15-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-03-15-18.02.log.html19:00
fungiinfra team, assemble!19:00
*** yolanda has joined #openstack-meeting19:00
pabelangerp/19:00
*** tsymanczyk has left #openstack-meeting19:00
pabelanger fail19:00
Zarao/19:00
yolandao/19:00
crinkleo/19:00
*** shaleh has left #openstack-meeting19:00
olaphform of: gelatin desert!19:00
* stevemar puts on his best justice league costume19:00
*** haomaiwang has quit IRC19:01
stevemari've assembled19:01
rcarrillocruzo/19:01
Zarapabelanger: oh, I thought that was a special unique wave, since your name starts with 'p'19:01
*** brad_behle has left #openstack-meeting19:01
jeblairhi19:01
fungieveryone needs a personalized wave19:01
clarkbohai, I am actually not really here due to unexpected series of evemts that demand my attention19:01
anteayaclarkb: hope the family is okay19:01
ianwo/19:01
fungiclarkb: you do a remarkable imitation of the real clarkb19:01
*** haomaiwang has joined #openstack-meeting19:01
tristanChello!19:01
*** rderose has quit IRC19:01
* dougwig lurks.19:01
clarkbeveryone is well, just have to get some stuff done and it is time sensitive19:01
jeblairfungi: perhaps the unexpected events involve multiple clarkbs19:01
*** roxanaghe has left #openstack-meeting19:02
fungiwoah!19:02
eil397hi19:02
*** spzala_ has joined #openstack-meeting19:02
AJaegero/19:02
pabelangerZara: yes, that is true19:02
fungitopics with names include: pabelanger, AJaeger, anteaya, timothyb8919:02
anteayaI'm here19:02
fungialso a spec here from jhesketh and tonyb19:02
SotKo/19:02
anteayaclarkb: ah okay good19:02
fungiand action items for jeblair and yolanda19:03
pieto/19:03
fungilet's get rolling19:03
*** asingh has quit IRC19:03
fungi#startmeeting infra19:03
tonybo/19:03
openstackMeeting started Tue Mar 15 19:03:17 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
craigeO/19:03
fungipleia2 is awesome and started this for us:19:03
fungi#link https://etherpad.openstack.org/p/infra-newton-summit-planning Newton Summit Planning19:03
fungisome people have already begun brainstorming ideas but we should get rolling on this and have some decisions in next week's meeting19:03
*** bnemec has quit IRC19:03
*** brucet has quit IRC19:03
fungiit sounds like we'll get at least the space requested (4 workrooms, 3 fishbowls, a day of possibly shared sprint) but there may be more available if we know _very_ soon so i can still request it19:03
nibalizero/19:03
fungi#info Please add Infra team summit session ideas to the Etherpad19:04
fungi#topic Actions from last meeting19:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:04
Clinto/19:04
fungiwe have a couple!19:04
fungijeblair Give the TC a heads up on "Create elections.openstack.org" spec19:04
fungi#link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-08-20.01.log.html#l-9319:04
*** ivar-lazzaro has quit IRC19:04
jeblairi did it!19:04
fungilooks like that happened, they discussed it some and weighed in with positivity19:04
fungiwe have a moment to discuss this further down in the specs approval19:05
fungiyolanda Boot a replacement review.openstack.org and communicate the new IP address and maintenance window in an announcement E-mail19:05
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088985.html19:05
yolandait's done19:05
fungithat too happened19:05
fungiyes19:05
fungithank you both! we're back to a starting count of 0 action items!19:05
*** toscalix has quit IRC19:05
fungiyolanda: also not sure if you saw, but the extra gerritbot is probably on that server and should be shut down if you get a chance19:06
fungi#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
yolandai already stopped it19:06
fungi#link https://review.openstack.org/287577 PROPOSED: Create elections.openstack.org19:06
fungi#link https://review.openstack.org/292666 Amendment to elections spec to use governance.openstack.org instead19:06
fungitonyb: jhesketh: these seem ready to go for a council vote now?19:07
*** ebalduf has quit IRC19:07
tonybfungi: I believe so19:07
fungijeblair: the tc seemed generally approving of having this grafted into a subtree of the governance site?19:07
*** sdake has joined #openstack-meeting19:07
jeblairfungi: that was my interpretation of the meeting and review feedback19:07
jeblairso i'm happy to see both of those go to voting together19:07
fungi#info Voting is open on the "Create elections.openstack.org" spec and "Publish election data to governance.o.o" update for it until 19:00 UTC on Thursday, March 1719:08
fungi#topic Priority Efforts19:08
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:08
fungilooks like we don't have any urgent priority effort updates this week so i'll skip this and see how many of the general topics we can get through19:09
fungi#topic Upgrade servers from ubuntu precise to ubuntu trusty (pabelanger)19:09
*** openstack changes topic to "Upgrade servers from ubuntu precise to ubuntu trusty (pabelanger) (Meeting topic: infra)"19:09
rcarrillocruzi'd appreciate more reviews to https://review.openstack.org/#/c/239810/19:09
rcarrillocruzrelated to puppet-openstackci priority effort19:09
pabelangerohai19:09
pabelangerSo, we still have servers running precise, and I figure I can offer my service to upgrade them to trusty19:10
*** pvaneck has quit IRC19:10
pabelangerthis is mostly for some bindep stuff19:10
*** ivar-lazzaro has joined #openstack-meeting19:10
pabelangerbut also prep for 16.0419:10
pabelangerfor the most part they are 3 servers atm19:10
fungi#link https://review.openstack.org/#/q/status:open+topic:trusty-upgrades Review topic for server upgrades to Ubuntu Trusty19:10
pabelangerany low hanging fruit19:10
pabelangerI figure puppetdb.o.o could be the first one19:10
jeblairis there something applying pressure for us to do so?19:10
fungiyeah, one caught us by unfortunate surprise this morning19:10
pabelangerwith the other 2 lists.o.o and cacti.o.o requiring migration discussion19:11
fungithat is, we were unknowingly validating our zuul configuration on trusty while running zuul in produciton on precise19:11
pabelangerjeblair: no, it just came up when talking with fungi about bindep stuff for ubuntu precise19:11
pabelangerso we could remove bare-precise19:11
fungii know the openstackid-resources api split is also applying pressure to get openstackid-dev.o.o and openstackid.org upgraded from precise to trusty so that they can run a consistent framework with what the openstackid-resources.o.o server will need19:12
*** dims has joined #openstack-meeting19:12
jeblairdo we still need precise nodes for stable branches?19:12
fungibut yeah, right now our options for testing precise are basically either to only do that in rackspace or to make a precise ubuntu-minimal work for dib imagery19:12
fungiprecise hasn't been needed for stable testing since icehouse went eol almost a year ago19:13
*** ijw has quit IRC19:13
jeblairok, so we're the last users?19:13
*** bnemec has joined #openstack-meeting19:13
fungithat we are19:13
pabelangerYup19:13
jeblairthat seems reason enough19:13
jeblairi am now sufficiently motivated19:13
pabelangerSo, the changes up are minimal puppet changes19:13
pabelangerwhere puppetdb we could afford to lose data19:14
pabelangerbut lists and cacti we might need to migrate19:14
*** krotscheck is now known as kro_death_by_sin19:14
jeblairpabelanger: agreed (except s/might//)19:14
pabelangerfungi: suggested moving the data to cinder to help transfer it between server19:14
*** kro_death_by_sin is now known as kro_sinus_hell19:14
jeblairnot a bad idea19:14
fungiright, i was thinking cinder first, then move to new servers for those19:15
fungicinder and trove make upgrades like this a lot faster19:15
fungicacti is less of a problem in that a longish downtime is not critical19:15
jeblairdo we use trove with cacti?19:15
fungii don't recall if cacti needs mysql at all19:16
jeblairlists only has data in the filesystem; cacti has mysql and filesystem data19:16
pabelangerneed to check19:16
amrithdid someone say trove ;)19:16
fungiahh, so yeah may also want to trove the cacti server if so19:16
jeblairthere is a mysqld running on cacti19:16
*** bnemec has quit IRC19:16
jeblairi think that should be doable19:17
fungibut anyway, lengthy migration for cacti is not a serious problem. extended mailman outages on the other hand will be painful for the community19:17
pabelangerokay, I can look into that and get puppet code up19:17
pabelangerpuppetdb should be easy to test, stand up new one, validate reports post, then update dns19:17
fungiso at least putting mailman's persistent data on cinder would be awesome for keeping the cut-over shorter19:17
pabelangersuspend / delete old instance19:18
*** dprince has quit IRC19:18
fungianything else on this topic?19:18
craigephabricator.o.o would be a great test target too19:18
*** bnemec has joined #openstack-meeting19:18
pabelangernothing now, I'll follow up offline19:18
*** dims has quit IRC19:18
* craige would appreciate that :-)19:18
pabelangercraige: Yup, we should aim for trusty for that too19:18
fungiyeah, we have a lot of low-hanging fruit servers for this. a quick read of the global site manifest's testing platform comments will reveal which ones hopefully, or puppetboard facts view19:19
craigeIt's required.19:19
*** e0ne_ has quit IRC19:19
*** xyang1 has joined #openstack-meeting19:19
fungithanks pabelanger! i think this is a worthwhile effort and am looking forward to it19:19
craigeand a blocker to going live.19:19
pabelangerfungi: np19:19
rcarrillocruzfungi, pabelanger: i don't mind taking some of them, i'd need a root to make the vm spin tho19:19
*** trozet has joined #openstack-meeting19:20
fungircarrillocruz: yep, we'll make sure there's at least one infra-root on hand for these as a shepherd. we can divide them up as needed19:20
fungi#topic Constraints - next steps? (AJaeger)19:20
*** openstack changes topic to "Constraints - next steps? (AJaeger) (Meeting topic: infra)"19:20
*** cdub has joined #openstack-meeting19:20
*** Leom has quit IRC19:21
AJaegerWe have constraints enabled in gate and periodic jobs but not post and release jobs. To enable it everywhere, we need https://review.openstack.org/#/c/271585/ to enhance zuul-cloner. Thanks jesaurus for working on this.19:21
AJaegerI'm unhappy that the constraints changes did not finish so far and wanted to discuss next steps. Should we push this for Mitaka and have the projects that currently support constraints (at least cinder, glance, some neutron ones) full support? My preference is to declare this is a Newton target and get zuul-cloner enabled but do further work  - including proper announcements - only for Newton.19:21
fungi#link https://review.openstack.org/271585 Let zuul-cloner work in post and release pipelines19:21
*** sdake_ has joined #openstack-meeting19:21
AJaegerSo, what are your thoughts on direction here for Mitaka and Newton?19:21
anteayaI still find contraints confusing and have no thoughts to offer to this conversation19:23
*** sdake has quit IRC19:23
AJaegerBasically what needs to be done to finish this AFAIU: 1) Get 271585 pass the testsuite (too large logs); 2) Update post/release jobs; 3) Document setup and announce it so that projects can update their tox.ini files.19:23
fungiit does look like jesusaur is still working on it19:24
AJaegerWe could also make the current setup a bit more robust - so projects enabled it and use same environment (working fine) in gate but then had no tarballs (post queue).19:24
*** th3rt has joined #openstack-meeting19:24
fungijesusaur: do you need additional assistance debugging the job failures on 271585?19:25
AJaegerAFAIU jesusaur has it testing locally, it fails in our gate due too large logs19:25
fungithat seems like an odd reason for a job to fail19:25
*** kozhukalov has joined #openstack-meeting19:26
AJaegerthat's what I remember from some #openstack-infra discussion but I might have misread19:26
fungi#link http://logs.openstack.org/85/271585/5/check/gate-zuul-python27/75de99c/console.html.gz#_2016-03-10_20_52_55_179 testrepository.subunit was > 50 MB of uncompressed data!!!19:26
jeblair!!!19:26
openstackjeblair: Error: "!!" is not a valid command.19:26
AJaegerfungi, your incredible!19:26
*** dims has joined #openstack-meeting19:26
*** ivar-lazzaro has quit IRC19:26
fungiyeah, it's a remarkably emphatic error message19:27
AJaegerHearing the enthusiasm ;) here, I suggest to declare it a Newton target...19:27
fungiso i guess the questions this raises are, 1. is the subunit output from zuul's unit tests too verbose or possibly full of junk? 2. is 50mb uncompressed a sane cap for subunit data?19:28
jeblairthey are certainly too verbose except in the case of a test failure :(19:28
fungiif someone gets time, a git blame on that to find why the check for uncompressed subunit data size was introduced would be handy as a data point (e.g., was it for keeping the subunit2sql database sane?)19:29
jesusaurfungi: the tests pass locally for the change, but they fail in the check pipeline due to either the size of the resulting subunit file or they hit an alarm and time out19:29
jeblairfungi: istr it was actuall just for uploading to the logserver19:29
mordredo hai19:29
jeblairi think it's probably an appropriate limit for 'unit tests'.19:30
jeblairbut not so much for zuul's functional "unit" tests19:30
fungigranted, many of even our oldest projects' "unit" tests are more "functional" testing (i'm looking at you, oh great and venerable nova, performing database interactions)19:30
jeblairyeah, but zuul starts and reconfigures several hundred times during its tests19:31
jeblairthere's a lot of startup boilerplate in there, along with full gearman debug logs19:31
*** dprince has joined #openstack-meeting19:31
*** emagana has joined #openstack-meeting19:31
fungiAJaeger: mitaka integrated rc is already nearly upon us, it does seem like newton will be when we have constraints more widely in use for things besides devstack-based jobs19:32
*** trozet has quit IRC19:32
*** ociuhandu has quit IRC19:32
*** harshs has quit IRC19:32
jeblairi'm not sure what to do about the subunit cap.  i definitely need the logging information locally, and i need it in the gate when we get those occasional 'only fails in the gate' bugs.19:32
AJaegerfungi, yes.19:33
jeblairi don't need it in the gate on tests that pass19:33
jeblair(though i do need it locally on tests that pass)19:33
fungiAJaeger: and i also agree that declaring open season on constraints integration in tox configs opens us up to a potential risk of breaking things like tarball jobs (as already seen on at least one project recently)19:33
bkerocompress it, offer it up in the finished build artifacts?19:33
fungibkero: we already do19:33
jeblairso i wonder if we could prune the logs from tests that pass.  i have no idea if/how that would be possible with testr19:34
fungibkero: however the job checks the raw uncompressed size and complains, then fails on that, with the current implementation19:34
AJaegerfungi, so for Mitaka: Projects can use it but we advise against it - or if they do ask them to triple check ;)19:34
*** emsomeoneelse has quit IRC19:34
fungiAJaeger: yes, i think it's still mostly experimental until we can let them use it on more than just check/gate type jobs19:34
bkeroOh, that seems incorrect O_o19:34
jeblairbkero: what seems incorrect?19:35
AJaegerbut we can't control it anyway, they just change their tox.ini without us19:35
bkerojeblair: compressing data, but checking uncompressed size19:35
fungiAJaeger: agreed, but we can tell them that when it breaks they get to keep both pieces19:35
*** fawadkhaliq has quit IRC19:35
AJaegerfungi ;)19:35
jeblairbkero: if you check the compressed size, then it's not a check about how much output was produced, it's a check on how well the compression algorithm performed19:35
*** PsionTheory has quit IRC19:36
fungigranted, if your concern is how much storage you're using for your compressed logs, then checking compressed size does make more sense (which is why i suggested looking into the reason the check was introduced)19:36
bkeroYep, that's true. I don't know the context of what this check limitation is supposed to do. Not constrain resources, or check for discrepancies in the run19:37
jeblairoccasionally projects would output insane amounts of data into their subunit logs, this was to catch those occurences.  it's working.  zuul outputs an insane amount of data.  i find it useful.19:37
*** aysyd_ has joined #openstack-meeting19:37
fungiwithout better history of why we started checking that, i'm hesitant to suggest blindly altering it19:37
*** aysyd has quit IRC19:37
*** aysyd_ is now known as aysyd19:37
jesusaurcould we reduce the logging level of some of the modules, but keep DEBUG for zuul.* ?19:37
jeblairjesusaur: i think the bulk of the data are zuul debug lines19:38
jeblairjesusaur: gear.* might be significant19:38
jesusaurI think gear is also a contender for that top spot19:38
fungiare your primary concerns on this topic answered, AJaeger?19:39
*** hashar has joined #openstack-meeting19:39
AJaegerfungi, yes19:39
jeblairjesusaur: heh, yeah, gear might exceed zuul19:40
*** azbiswas has joined #openstack-meeting19:40
fungiwe can probably move zuul test log improvements to a review, ml thread or #openstack-infra19:40
jeblairwell, what would be useful...19:40
AJaegerthanks, fungi. we can move on. Unless you want to log that constraints are experimental besides devstack19:40
fungiunless anyone is finding it useful to continue brainstorming that in the meeting19:40
jeblairis to have someone who understands testrepository willing to pitch in19:40
fungi#agreed Constraints via zuul-cloner for jobs outside check and gate type pipelines is not currently supported, and general use of constraints in tox should be implemented with care to avoid risk to other non-constraints-using tox jobs until support is fully implemented19:42
fungianyone disagree with tat? i can #undo and rework if needed19:42
*** cody-somerville has quit IRC19:42
anteayaI do not disagree19:42
fungiotherwise we still have a couple more topics to fill the remaining 15 minutes19:43
AJaegernicely formulated, fungi. +119:43
*** cody-somerville has joined #openstack-meeting19:43
*** salv-orl_ has quit IRC19:43
fungi#topic Operating System Upgrades (anteaya)19:43
*** openstack changes topic to "Operating System Upgrades (anteaya) (Meeting topic: infra)"19:43
anteaya#link https://etherpad.openstack.org/p/infra-operating-system-upgrades19:43
fungi#link https://etherpad.openstack.org/p/infra-operating-system-upgrades precise -> trusty -> xenial19:43
*** lpetrut has quit IRC19:43
*** dmorita has quit IRC19:43
anteayathanks19:43
fungi#undo19:43
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0xac5ccd0>19:44
anteayaso this came up last meeting and this meeting already19:44
*** lhcheng has left #openstack-meeting19:44
anteayathis is mostly a place to track what operating systems we are running and what we want to upgrade19:44
fungithis does seem like an extension of pabelanger's earlier topic19:44
anteayawe have identified during pabelanger item19:44
anteayayes19:44
*** novas0x2a|laptop has joined #openstack-meeting19:44
fungithough including the forward-looking plans for ubuntu 16.0419:44
anteayathat precise servers are readyg to move to trusty19:45
anteayayes19:45
anteayaalso dib capabilities19:45
*** _nadya_ has joined #openstack-meeting19:45
anteayaand what nodes have available19:45
*** dims has quit IRC19:45
pabelangerAgreed. I think getting trusty is a good base for xenial19:45
pabelangerand don't mind helping anteaya where possible19:45
anteayaso I don't personally have anything to offer here, other than the etherpad19:45
anteayapabelanger: thanks19:45
anteayamostly trying to track decisions and statsu19:45
anteayaI felt I was less effective that I could ahve been helping AJaeger with bare-trusty to ubuntu-trusty19:46
fungihaving xenial for use in jobs is a definite first step. upgrading our servers from trusty to xenial (or from precise to xenial) should wait for at least a few months according to opinions expressed in earlier meetings19:46
anteayamostly becauase I didnt' understand the large picutre or status19:46
anteayafungi: yes19:46
* AJaeger is gratefull for everybody's help with that conversion19:46
*** mfranc213 has quit IRC19:46
anteayaalso clarkb has an item in the summit plannnig etherpad on operating systems19:46
anteayaso its a topic we are talking about19:47
anteayawould mostly like to aggregate if we can19:47
fungiand also, yes, having _one_ image for jobs running on trusty provides us with an easier starting point for the coming trusty->xenial support mogration in our jobs19:47
fungier, migration19:47
*** Leo_ has joined #openstack-meeting19:47
jeblairthe etherpad notes puppet 384 in xenial...19:47
anteayaand if we don't like this etherpad, that is fine, as long as we have something19:47
*** dmorita has joined #openstack-meeting19:47
jeblairdo we want to switch to distro packages for puppet?19:47
*** vijendar has joined #openstack-meeting19:47
jeblairor keep using puppetlabs?19:48
anteayajeblair: I got that from pabelanger's comment from last weeks meeting19:48
fungipart of the complexity in the precise->trusty job migration across different branches was complicated by having several precise images (bare, devstack, py3k/pypy) and a couple of trusty images (bare, devstack)19:48
*** dprince has quit IRC19:48
pabelangerjeblair: anteaya: Ya, I was surprised to see xenial still using puppet 3.x19:48
fungiso there was an element of many<->many mapping19:49
pabelangerI'll defer to nibalizer and crinkle for version to use on ubuntu19:49
crinkleuse latest 3.x from apt.puppetlabs.com until we're ready to migrate to 419:49
anteayacrinkle: can you add that to the etherpad?19:49
fungii'm pretty sure we're going to want to use puppetlabs packages for at least as long as we're puppeting multiple distros in production, so that we don't have to deal with keeping everything sane across multiple simultaneous puppet versions19:49
jeblairi think one of the advantages of using puppetlabs is that we can actually migrate os versions19:49
anteayaas your recommendation?19:50
jeblairfungi: right, that.19:50
nibalizeryep19:50
crinkleanteaya: sure19:50
anteayacrinkle: thanks19:50
*** baojg has joined #openstack-meeting19:50
AJaegerregarding puppet 4: We'Re not testing Infra puppet scripts for puppet 4 - should we start that?19:50
pabelangerAJaeger: no, we are. Fedora-2319:50
AJaegerpabelanger: ah...19:50
*** ebalduf has joined #openstack-meeting19:50
pabelangerso we get some coverage19:50
AJaegergreat19:50
nibalizerAJaeger: there is a spec for that sorta19:50
nibalizeri think its more about getting linting working19:51
*** timcline has quit IRC19:51
*** sdake_ has quit IRC19:51
pabelangerAJaeger: and part of the reason we missed fedora-22 in the gate19:51
nibalizerpabelanger: f23 doesnt test the majority of our codr19:51
pabelangernibalizer: right, but we could start to with puppet apply if needed19:51
*** timcline has joined #openstack-meeting19:52
*** dmorita has quit IRC19:52
*** pvaneck has joined #openstack-meeting19:52
nibalizerwe should get a nonvoting puppet four trusty apply test19:52
fungiso as for anteaya's etherpad, i think that makes a fine place to coordinate an overview of what changes are migrating what servers from precise to trusty. the trusty to xenial migration for servers is still a ways out and we may find new things we want/need to plan for on the road to xenial anyway19:53
pabelangerpuppet openstack team does some good testing around using straight gems, if we wanted to do that too19:53
*** amitry has quit IRC19:53
*** ociuhandu has joined #openstack-meeting19:53
anteayafungi: great thank you19:53
fungiwe still have a few more minutes to get to the final topic on the agenda19:53
fungiif this is mostly addressed19:53
anteayaalso in that etherpad mordred has made some notes about dib and xenial19:53
anteayayup, let's move on, thank you19:53
fungi#topic StackViz deployment spec (timothyb89)19:54
*** openstack changes topic to "StackViz deployment spec (timothyb89) (Meeting topic: infra)"19:54
fungi#link https://review.openstack.org/28737319:54
*** amitry has joined #openstack-meeting19:54
timothyb89right, so we're looking for preliminary feedback on the spec, particularly the change proposal and our build method19:54
timothyb89we've had some alternative methods suggested, so we'd like to know if there can be a consensus on the method in the spec (DIB) vs puppet vs something else19:54
*** gordc has joined #openstack-meeting19:55
fungireviewers so far who provided feedback on that spec seem to have been AJaeger and pabelanger19:55
pabelangerI left comments about puppet, but haven't heard anybody else have an opinion19:56
*** timcline has quit IRC19:56
fungiso the question is between adding puppetry to install stackviz and its dependencies, and pre-seed its data, vs using a dib element?19:56
timothyb89fungi: yes, exactly19:56
fungiit's true that we do similar things both ways currently19:57
*** baojg has quit IRC19:57
fungione long-term vision is to continue reducing the amoun of puppet we apply to our base images, in hopes of maybe eventually being able to not have to preinstall puppet on them at all19:57
*** rockyg has joined #openstack-meeting19:58
*** zaneb has joined #openstack-meeting19:58
*** cp16net has joined #openstack-meeting19:58
*** cdent has joined #openstack-meeting19:58
*** MaxPC has quit IRC19:58
fungiour reliance on puppet for our image builds is already pretty minor these days19:58
*** MarkAtwood has joined #openstack-meeting19:58
fungiwe have a lot of orchestration being done in dib elements themselves, by nodepool ready scripts, and at job runtime19:59
fungianyway, i guess people with a vested interest in seeing how this is done, please follow up on the spec19:59
pabelangermy only real concern, is if we use dib elements, we are looking gate testing of stackviz19:59
fungiwe're basically out of meeting time for this week19:59
*** iyamahat has joined #openstack-meeting20:00
*** wojdev has joined #openstack-meeting20:00
fungithanks everybody! time to make way for the tc20:00
fungi#endmeeting20:00
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"20:00
openstackMeeting ended Tue Mar 15 20:00:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
flaper87o/20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-15-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-15-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-03-15-19.03.log.html20:00
ttxo/20:00
mesteryo/20:00
dhellmanno/20:00
sdagueo/20:00
*** yolanda has left #openstack-meeting20:00
thingeeo/20:00
dtroyero/20:00
* gothicmindfood lurks20:00
ttxrussellb, annegentle, lifeless, mordred, markmcclain, jeblair, jaypipes: around ?20:00
jeblairhowdy20:00
markmcclaino/20:00
ttx#startmeeting tc20:00
openstackMeeting started Tue Mar 15 20:00:54 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
amrith./20:00
russellbhi20:00
*** openstack changes topic to " (Meeting topic: tc)"20:00
* rockyg tries to stay quiet in the back of the room20:00
openstackThe meeting name has been set to 'tc'20:01
*** haomaiwang has quit IRC20:01
*** annegentle has joined #openstack-meeting20:01
*** igordcar1_ has quit IRC20:01
*** pabelanger has left #openstack-meeting20:01
ttxHellllooo everyone!20:01
ttxOur agenda for today:20:01
flaper87yoooooooooo20:01
*** igordcard_ has joined #openstack-meeting20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
jaypipesI is here.20:01
ttx#topic Extra ATCs20:01
*** openstack changes topic to "Extra ATCs (Meeting topic: tc)"20:01
ttxWe have a couple extra ATCs requests to rubberstamp.20:01
*** haomaiwa_ has joined #openstack-meeting20:01
ttxNB: the governance repo was tagged for elections last week though, so those won't vote in upcoming elections20:01
ttxunless we start doing very funny things20:02
ttx* Adding Horizon extra-atc (https://review.openstack.org/290188)20:02
fungii'm not in favor of doing funny things with the election20:02
ttxthat one has enough to pass, will approve now20:02
ttx* Add dencaval to extra-atcs for Manila (https://review.openstack.org/289408)20:02
annegentleo/20:02
fungialready doing final testing on our roll generation tooling based on the existing tag20:02
ttxthis one is missing one20:02
annegentlewas there a deadline missed for dencaval to need extra atc?20:03
annegentleI don't see a need for it but maybe someone can explain20:03
ttxannegentle: start of PTL nomination period20:03
annegentlettx: ah for elections then?20:03
bswartzannegentle: I thought he deserved voting rights in Manila, as well as docs20:03
russellbannegentle: just commented20:03
ttxannegentle: that is when we tag the governance repo and start generating rolls20:03
annegentleI'm on spring break but popped in for this20:03
annegentlethanks russellb20:03
anteayaannegentle: dencaval has atc for docs, bswartz just wanted him in manilla too20:03
annegentleneeded to understand20:03
russellbannegentle: it's voting rights in manila as well20:03
annegentlegot it20:03
dhellmannbswartz : I think ttx and fungi just said it would be too late for this election anyway?20:03
ttxthat will be valid for the next20:04
bswartzyes that's my fault20:04
russellbstill reasonable for next time around20:04
david-lylevoting rights last two cycles20:04
dhellmannok, just making sure that's clear20:04
mesteryrussellb: ++20:04
bswartzI've already conveyed my apologies20:04
ttxalright both approved20:04
*** ig0r_ has joined #openstack-meeting20:04
david-lylethanks20:04
ttx#topic Update Kuryr mission statement20:04
*** openstack changes topic to "Update Kuryr mission statement (Meeting topic: tc)"20:04
fungiit will come into effect for ocata elections and summit passes for barcelona20:04
mordredo/20:04
*** th3rt has quit IRC20:04
ttx#link https://review.openstack.org/28999320:04
*** delattec has quit IRC20:05
ttxSo this is about extending the bridging mission of Kuryr to also include storage features20:05
ttxIt's a significant change but I think it makes sense20:05
russellbI still don't get it20:05
*** olaph has left #openstack-meeting20:05
russellbthese are really high level use cases, but it's not clear what actual code is to be written20:05
russellband where that code plugs into the overall system20:06
ttxrussellb: I'm not 100% sure what they will end up needing doing, yes20:06
*** neelashah has quit IRC20:06
ttxsince for example Kubernetes has a cinder plugin20:06
russellbi'd expect a bit more confidence in specific deliverables than this20:06
mesteryThe bit about persistent storage for containers sounds interesting, though not conrete20:06
*** ig0r__ has quit IRC20:06
ttxbut they seem convinced there are interesting things to do, and I'm fine with them exploring20:06
mestery*concrete20:06
ttxnow if only Gerrit would ah.20:07
mesteryttx: +1, to me I'm ok with it as well20:07
*** eglynn has joined #openstack-meeting20:07
russellbok, well recorded my -1 fwiw.  i'd rather just not rubber stamp these things20:07
flaper87I think it's fine to wait a bit longer and have a more specific mission statement20:08
ttxrussellb: I'm fine delying until we can get better answers from Gal20:08
mesteryrussellb: Agree20:08
ttxI raised the fuzziness first after all20:08
russellbttx: right20:08
dhellmannI'd be ok with that, too.20:08
mesteryrussellb: I meant, I agree with not rubber stamping20:08
lifelessttx: o/20:08
jeblairyeah, the answers so far are almost as broad as the proposed mission statement20:08
mesteryI'd be fine waiting a bit more, but I'm also ok trusting the team to move forward here and explore a bit20:09
jeblairand i'm struggling with making it concrete --20:09
russellbdon't need to update mission statement to explore20:09
ttxrussellb: can you take the action to reach out and get a cleaner explanation, or even (gasp) a ML thread about it ?20:09
russellbi've tried in gerrit20:09
*** IlyaG has joined #openstack-meeting20:09
mesteryrussellb: Fair point20:09
ttxrussellb: I think it warrants a ML thread to be fair20:09
russellbok20:09
russellbi can do that20:09
ttxif only so that the rest of the community sees it better20:09
jaypipes"Kuryr is the glue between the container world and OpenStack APIs"?20:09
ttxjaypipes: basically, no need to create glue if storage does not need glue20:10
jaypipesttx: docker has a Cinder plugin?20:10
russellbthe network case was clear, there are very clear plugin interfaces20:10
russellbi just want to know the equivalent for storage that they are targeting here20:10
*** dims has joined #openstack-meeting20:11
*** sdake has joined #openstack-meeting20:11
russellbbecause without that, it's not clear to me that openstack should have a project for it20:11
ttxjaypipes: no but (1) k8s has, and (2) that might point to the possibility of adding it in Docker rather than OpenStack20:11
russellbvs working upstream in container thingy projects20:11
ttxhence more precision needed20:11
jaypipesttx: fair enough points.20:11
ttxI'm not saying no (I actually still am a YEs on the proposal) but I agree with Russell this could use more clarity on the goals20:12
russellbyep, and i'm not upset if i'm overridden really :)20:12
annegentleI'm happy with the use case getting more discussion so we all understand more20:12
russellbbut "does this actually make sense" is a good question to ask :)20:12
ttxAlso it sounds like extending a team mission should at the very minimum cause a ML thread, if only to attract more contributors20:12
annegentlerussellb: yah20:12
flaper87I'm ok with waiting. More clarification is good and if the mission statement change is required then we better get it right otherwise it'll be upated again next cycle20:12
*** ijw has joined #openstack-meeting20:13
ttx#info waiting one more week for extra precision20:13
ttx#action russellb to follow up in a ML thread20:13
*** esker has joined #openstack-meeting20:14
ttx#topic Add a resolution for PTL Leave of Absence20:14
*** openstack changes topic to "Add a resolution for PTL Leave of Absence (Meeting topic: tc)"20:14
ttx#link https://review.openstack.org/29014120:14
*** ijw has quit IRC20:14
ttxanteaya posted a resolution to clarify TC communication expectations on PTLs leaves of absence20:14
* annegentle admits she hasn't read it yet20:14
ttxThe preferred option is of course public communication, but there are some cases where the PTL would rather not go public with the details, so there are backup solutions as well20:14
ttxThere was some opposition to the resolution, mostly about the "communicate to the TC" part if I read the comments correctly20:14
ttxI think that's partly a misunderstanding on what the resolution is trying to achieve -- this is not about the PTLs communication duties toward their teams20:15
russellbi'd rather assume PTLs use good judgement and work this out within their teams20:15
ttxIt's about clarifying the official projects PTLs communication duties toward the TC20:15
dhellmannyeah, the issue is all of the interface points outside of a team that also need to know about these changes20:15
ttxI think we can further document the PTLs communication duties toward their teams, but I see that as belonging in the Project Team Guide rather than governance20:15
russellbfeels like massive overkill in policy20:15
dtroyercan we clarify the requirements/desires without specifying implementation?20:15
mesteryrussellb: ++20:15
dhellmannrussellb : "Please tell folks if you're going to be gone for a long time and you lead a project" is overkill?20:16
russellbi don't think we need a resolution for it20:16
lifelessUbuntu has a code of leadership which speaks to this20:16
dhellmannrussellb : so how do we address it?20:16
lifelessI think the current proposal is overly proscriptive20:16
sdaguewe kind of already had the "step down gracefully" clause buried somewhere20:16
dtroyerI see two things to think about: 1) elected leaders have a responsibility to those who elected them20:16
ttxWe could just document it on the Project Team Guide. But I don't think a resolution is overkill either.20:16
lifelessI'd support something that just highlights the required outcome20:17
annegentleMy initial sense is that what you really want to have a policy for is PTL disappearence/non-communication. Also consider the case where a PTL is pregnant (hey, it can happen), would she need to not run in the time period?20:17
lifelesswhich is that folk don't go awol20:17
anteayasdague: that is the smooth tranistions expectation, but I don't know if this was a transisiton or not, hence the desire for more facts20:17
dtroyer2) the TC is the focal point for working across the other tehnical leaders in projects20:17
annegentlelifeless: that's my read of it too20:17
mesteryI like jaypipes's comments: Lets trust PTLs and project teams to handle this on their own, communicating with the TC. If the TC needs to step in to help, we can do that.20:17
sdagueso I think I'm on the side that we don't need another policy for this20:17
ttxdtroyer: yes that's it20:17
annegentlevacations, known predictable medical leave, those are having a life20:17
anteayaannegentle: this doesn't cover vactation20:18
anteayathis is unexpected events20:18
anteayanon planned20:18
*** singhj has quit IRC20:18
sdaguecommunity norms weren't followed, step down gracefully should cover this.20:18
dhellmannmestery : so this came about because of the situation with trove last week, in which a lot of people were surprised and up in arms because the ptl was out for a couple of weeks and only a few folks outside of the team knew.20:18
anteayasdague: should but didn't20:18
russellbwas there actually a problem with trove?20:18
ttxsdague: is it documented somewhere (the "step down gracefully" ?)20:18
russellbwe clearly had someone available to talk to and work with20:18
mesterydhellmann: OK, so what happened that was super bad during that time period?20:18
russellbit wasn't hard to figure out20:18
lifelesssure, but its too low level; we can't legislate every eventuality. Was this prompted by some PTL going awol ?20:18
mesteryDid the release for trove go bad or not happen (that would be bad)?20:18
dhellmannrussellb : no. he was out for a few weeks, he came back, everything was handled except for whatever happened in the meeting last week.20:18
flaper87As I mentioned in the spec, I'm also not in favor of having a policy for this. I'd rather rely on the common sense of PTLs and, most importantly, the community's20:18
ttxlifeless: yes, trove PTl was out but most didn't know20:18
mesteryOK, so sounds like common sense prevailed?20:19
sdagueI swore it was in our community standards somewhere, grepping20:19
ttxsdague: if it's already documented somewhere I'm fine not adding a layer20:19
jeblairsomeone from the project came to the tc meeting and told us that though.  i'm not upset.20:19
annegentlesdague: grep man grep20:19
*** mugsie has joined #openstack-meeting20:19
russellbjeblair: ++20:19
dhellmannif we look past the prescriptive language in this resolution, I'm having a hard time understanding why we wouldn't want to write down that we expect folks to announce this sort of thing20:19
*** banix has quit IRC20:20
anteayaespecially if they happen to be stressed20:20
dhellmannjeblair : yeah, it was the qa folks I think20:20
thingeesdague: https://wiki.openstack.org/wiki/PTL_Guide#Availability ?20:20
dhellmann(that were upset)20:20
flaper87and if we really want to add the resolution, I'd avoid mentioning all the steps and perhaps simplify it with: "let us know, please"20:20
anteayaand are trying to figure out the right thing to do20:20
russellbmore that it feels so heavyweight ... if we have to write this down, do we need formal policies for everything that seems like reasonable common sense20:20
dhellmannflaper87 : I agree with making this proposal simpler20:20
mesteryflaper87: ++20:20
mesteryResolution: IF as PTL you're going somewhere, let your project team and the TC know.20:20
mesterySeems pretty simple20:21
ttxhow about we turn it into something we add to the project team guide ?20:21
markmcclainflaper87: that's what I suggested in the comments20:21
dtroyerttx: +++20:21
russellbttx: sounds reasonable20:21
sdaguethingee: yeh, I think thwas was it20:21
dhellmannttx: that works20:21
anteayayou don't have to go anywhere to not be able to fulfill your obligations20:21
annegentlettx: that would work, and make sure you have a proxy assigned20:21
thingeettx: https://wiki.openstack.org/wiki/PTL_Guide#Availability20:21
anteayayou can still be at home/office20:21
dhellmannanteaya : figure of speach20:21
flaper87markmcclain: yeah, I did as well but...20:21
thingeejust move that from the wiki20:21
ttxthingee: that's not official doc anymore20:21
ttxthingee: right20:21
mesteryI'm not in favor of prescriptively documenting common sense in this case20:21
jeblairttx: if the bit thingee posted isn't in the guide, i think that's a great thing to include20:21
ttxsomeone needs to care enough to push that. That is why I was fine with the resolution model, whatever the author prefers basically20:22
flaper87To me, the most important part is for the team to know the PTL is not going to be around. IF they manage to nominate an interim PTL, that's more than awesome. IMHO20:22
flaper87An email to the ML is great20:22
ttxdo we have a volunteer to push that in the PTG instead ?20:22
thingeettx: I can do it20:22
mesteryflaper87: Agreed20:22
russellbthingee: thanks!20:22
dhellmannthanks, thingee20:22
sdaguethingee: awesome, thanks20:22
sdagueand good find on it :)20:23
ttxPersonally I think the PTG is more discoverable and less intimidating than a resolution, so I'm fine with it landing there20:23
jeblairthingee: there's some similar language in doc/source/open-community.rst ; so maybe an enhancement to that20:23
*** drankis has quit IRC20:23
*** kzaitsev_mb has joined #openstack-meeting20:23
*** rfolco has quit IRC20:23
russellbttx: ++20:23
*** matrohon has joined #openstack-meeting20:23
mesteryttx: ++20:23
*** ivar-lazzaro has joined #openstack-meeting20:24
*** elopez has quit IRC20:24
annegentleagreed let's not make it less appealing/possible to be PTL :)20:24
lifelessI think we have consensus, lets move on?20:24
*** rfolco has joined #openstack-meeting20:24
ttxyes20:24
jeblairthingee: http://docs.openstack.org/project-team-guide/open-community.html#technical-committee-and-ptl-elections20:24
ttx#agreed Push the thing to the PTG instead20:24
thingeejeblair: thanks20:24
ttx#action thingee to propose a PTG change to cover expectations on PTLs20:24
*** elopez has joined #openstack-meeting20:25
annegentlethanks anteaya for bringing it up; obviously needed some thoughtful discussion20:25
jeblairanteaya: ++20:25
lifeless++20:25
russellb++20:25
markmcclain++20:25
anteayawell brought you all together20:25
anteayawho else can do that?20:25
ttxAlrighty20:26
ttx#topic Open discussion20:26
* jeblair has an answer but keeps it to himself20:26
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:26
ttx* Status update on the testing interface conformance issues found in Trove20:26
amrithTo be respectful of everyone's time, and so you don't have to all watch me type this, I've put these comments on gist.20:26
amrith https://gist.github.com/amrith/343415cda4a937f78eac#file-trove-stable-liberty-txt20:26
ttxtl;dr is most issues were fixed ?20:26
* ttx reads20:26
amrithyes, the summary is this20:26
amrithIn summary, let me say that the stable/liberty gate is now working20:26
amrithagain and is reliable. More needs to be done, and there is a plan to20:26
amrithaddress it in stable/liberty, stable/mitaka and moving forward.20:26
amrithI would also like to thank Matt for escalating this issue.20:27
amrithand I'll be working with him to take care of some final 'cats and dogs' ...20:27
*** roxanagh_ has joined #openstack-meeting20:28
russellbthe cats and dogs that are raining down?20:28
ttxalright, it seems the issue is now closed and doesn't need TC follow-up20:28
flaper87amrith: thanks for working on that20:28
russellbthanks amrith !20:28
amrithrussellb, if you are near where I am, yes it is raining hard. they call it New England for a reason ;)20:28
ttxyes, thx amrith for jumping on the issue and fixing it20:28
amriththanks to all for the help getting the issues resolved.20:28
lifelessit is raining cats and dogs here, for sure20:28
russellbi'm in California today, very dry20:28
ttxdo we have both mordred and lifeless ?20:29
tristanCQuick update from elections: 51Hour left, 25 projects are missing candidates (which is about 47%)20:29
flaper87Just a heads up from the comm team: A blog post is being written. It started after our last meeting but there was not enough time. Hopefully will go out in the next couple of days20:29
*** azbiswas has quit IRC20:29
annegentlethanks flaper8720:29
lifelessttx: reporting for duty20:29
*** bswartz has quit IRC20:29
ttxmordred: around ? if yes I'd like to get deeper in the discussion we started two weeks ago20:29
mordredttx: I am here!20:29
ttx* Are GPL test-only Python library dependencies an issue or not ? (lifeless, mordred)20:29
ttxAbout lifeless comments on https://review.openstack.org/#/c/279999/20:30
lifelessmordred: was just about to ring you :)20:30
*** azbiswas has joined #openstack-meeting20:30
mordredI feel like lifeless and I got somewhere20:30
ttxThe question is... should GPL test-time library dependencies (like scapy or Mysql-Python) be considered ok or not20:30
annegentlethanks tristanC20:30
mordredwhen we chatted a couple of weeks ago20:30
*** dimtruck is now known as zz_dimtruck20:30
ttxlifeless seems to think they aren't ok, mordred seemed to think they are ok20:30
ttxfight!20:30
mordredI believe we've gotten to a middle ground20:30
flaper87ttx: lol20:30
*** piet has quit IRC20:30
ttxdammit20:30
lifelessttx: I think we agreed that we can't say yes or no to that question20:30
jeblairboring20:30
flaper87buuuu20:30
mordredyah.20:30
*** bswartz has joined #openstack-meeting20:30
* flaper87 yawns20:30
dimsboo20:30
thingeefrom cross-project land, I surfaced up some stale specs http://lists.openstack.org/pipermail/openstack-dev/2016-March/089115.html20:30
lifelessttx: sometimes they will. Sometimes they won't.20:30
mordredthat it depends on the dependency20:30
*** gordc has left #openstack-meeting20:30
mordredand we shoudl use human judgement20:30
ttxwhat sort of fight is this20:30
annegentleha20:30
*** piet has joined #openstack-meeting20:30
mordredttx: we fought in #openstack-dev20:30
mordredyou missed it20:30
lifelessttx: so -> the blanket rule is that we have to assess each one.20:30
thingeeI'd be interested in either someone interested in reviving these or the TC agreeing on some of these old specs being abandoned20:31
ttxlifeless: is there something we can add to the licensing requirements to make the rule clearer ?20:31
*** keedya has joined #openstack-meeting20:31
ttxor what we'd use to assess the rule ?20:31
lifelessttx: so its messy20:31
ttxbecause I'm not sure "asking mordred and lifeless about it" is scalable and durable20:31
flaper87thingee: gotta admit, it took me a bit longer to parse that last sentence20:31
*** keedya has quit IRC20:32
markmcclainttx: ++20:32
sdaguettx: well, it's infrequent enough, I'm actually comfortable with ask mordred and lifeless20:32
*** roxanagh_ has quit IRC20:32
sdagueI think it's more scalable than trying to define a process for it with everyone honestly :)20:32
ttxI'm ok with asking lifeless and mordred as long as they agree with my view of it20:32
lifelessttx: so, this specific proposal is invalid, because its making a blanket it's-ok rule.20:32
mordredyup20:32
*** azbiswas_ has joined #openstack-meeting20:32
dimssdague : ttx : my suggestion was that what's needed should be made available via infra (images?) and not added to *requirements.txt20:32
mordredbut a blanket it's-not-ok is also not the right thing20:32
lifelessttx: we can say something like 'invoking tools that are under any OSI approved license' is ok20:32
ttxlifeless: so since it merged we should post a clarification20:33
*** singhj has joined #openstack-meeting20:33
lifelessttx: because I think both mordred and I would agree that that is always ok, as far as it goes.20:33
*** dneary has quit IRC20:33
mordredyup20:33
* rockyg thinks maybe a set of questions to answer before submitting a patch to include in test reqs?20:33
lifelessits where things get into interface based derivation that it gets messy20:33
ttxright, calling tools is ok, everything else is more on a case-by-case basis of defining extension of work20:33
mordredyah20:33
ttxthat would be my take as well20:34
lifelessthe thing that provoked this was use of a python library20:34
*** fitoduarte has joined #openstack-meeting20:34
*** azbiswas has quit IRC20:34
ttxWe might want to kick Python-MySQL out then20:34
ttxand ask ourselves the question later ?20:34
mordredit has a specific carve-out20:34
sdaguepython-mysql has the foss exception, right?20:34
lifelesswhich is why it's ok ...20:34
dimsright20:34
mordredlibmysqlclient has the FOSS excpetion20:34
lifelessand why blanket rules are hard here20:34
ttxoh right20:34
mordredyah. turns out humans are good at assessing things and applying judgement20:34
ttxwe should probably add that to the # GPL comment20:34
*** jdurgin has quit IRC20:35
mordredin this case, we should call out that doing so is a good idea20:35
ttxmordred: nonsense!20:35
dimsttx : yep +120:35
*** cdelatte has joined #openstack-meeting20:35
*** ivar-lazzaro has quit IRC20:35
lifelessI'll add a tweak to requirements and propose a licensing.rst tweak20:35
jeblairi feel like there's a subtext that hasn't quite been said here...20:35
ttxlifeless, mordred: is one of you interested in proposing a new wording that outlines the OK scenario and the "we need to think about it" scenario ?20:35
lifelessto make it clearer that the blanket thing there is 'running things' not 'using libraries'20:36
ttxlifeless: ++20:36
*** MarkAtwood has quit IRC20:36
ttxlifeless: ++20:36
lifelessmordred: (and no, I know using is the wrong word, but in the absence of better ones :))20:36
ttx#action lifeless to propose a licensing.rst tweak20:36
*** maishsk has joined #openstack-meeting20:36
russellbwe could also identify a small group of people as the people that should be tagged on reviews where the licensing questions aren't clear20:36
jeblairwhich is that 'using libraries' is maybe not ok20:36
mordredlifeless: yah yah20:36
sdaguerussellb: yeh20:36
sdaguewhich is the mordred / lifeless solution20:36
russellbbecause it can't be solved completely with policy20:36
jeblairwhich i'm not convinced is the case20:36
sdaguerussellb: ++20:36
*** e0ne has joined #openstack-meeting20:37
jeblairi'm wondering, in the example of scapy -- do folks feel it's inappropriate?  if so, why?20:37
mesteryrussellb: ++20:37
dimswe still have no way to prevent test libs from leaking into runtime20:37
*** salv-orlando has joined #openstack-meeting20:37
mordredjeblair: I think lifeless point is that there might be cases where using a library would in fact be a case that a derived work would be the result20:37
*** jdurgin has joined #openstack-meeting20:37
lifelessdims: I don't see a difference between runtime and testtime20:37
lifelessdims: mechanically they are identical20:37
*** rockyg has quit IRC20:37
jeblairmordred: i agree it could happen.  but i see a difference between runtime and testtime :)20:38
mordredjeblair: and that looking at what the library is and how it's being used is the thing that's eventually going to be the deciding factor of that20:38
*** esker has quit IRC20:38
mordredjeblair: I do too20:38
lifelessdims: if the GPL has any relevance to Python code, the situations are identical20:38
dhellmannyeah, I'm not sure why we don't make a test/production distinction20:38
jeblair(who's distributing the binary that results when i run a test in the gate?)20:38
*** rockyg has joined #openstack-meeting20:38
mordredjeblair: but I think it's worth a specific discussion of each case20:38
mordredjeblair: becuase having the abstract discussion on it has so far been unsuccessful20:38
dimsjeblair : right20:38
lifelessdhellmann: from a distribution perspective (remember, GPL is a distribution license...)20:38
ttxand it's rare enough to make the cost of discussing it low20:38
*** esker has joined #openstack-meeting20:38
jeblairmordred: ok.  i can be down with that.20:38
gus(my personal relevant example here is pylint:  I wrote some openstack-specific pylint checks previously, but have nowhere to store them.  Clearly derived works from pylint (GPL), but also code that is easy to mentally separate from actual regular openstack deliverables)20:38
dimsgus : ++20:39
lifelessin the specific case of scapy, I want us to check with upstream20:39
jeblairlifeless: i think that's a fantastic idea.20:39
lifelessGPLv2 only is identified as ASLv2 incompatible by the FSF20:39
mordredif the author of scapy is fine with our use of it, then I tihnk we have no issue20:39
jeblairyeah, but "incompatible" doesn't begin to describe the nuance :)20:39
mordredyah20:40
lifelessIf their intent is to be incompatible, we shouldn't use it - we don't want to be the test case for 'The GPL is meaningless for Python programs'20:40
jeblairlifeless: agreed20:40
mordredif their intent is to be incomptible I want to have a discussion about it20:40
lifelessI mean, maybe we do - but it would be a fairly massive distraction20:40
mordredbecause I'm more of an ass20:40
mordredbut I do think checking first is the right move20:40
ttx<tristanC> Quick update from elections: 51Hour left, 25 projects are missing candidates (which is about 47%)20:40
mordredand depending on the feedback, it might be a very quick discussion20:40
lifelessI'd *love* to have that discussion, kindof.20:40
ttx#info Quick update from elections: 51Hour left, 25 projects are missing candidates (which is about 47%)20:40
ttxso hopefully we'll receive nominations and not have to appoint dozens of PTls in our next meeting20:41
*** baoli has joined #openstack-meeting20:41
flaper87++20:41
lifelessOmer has abandoned the scapy review20:41
lifelessso its a bit moot20:41
tristanCwell, we're going to send the 'last hours' announcement to motivate ptl-less project20:42
*** fawadkhaliq has joined #openstack-meeting20:42
ttxbtw some PTLs did not answer at all to our emails asking them for how much rooms they wanted at the design summit, if they don't have a PTL candidate either, I propose we fastrack their removal20:42
*** ivar-lazzaro has joined #openstack-meeting20:42
jeblairlifeless: did we succeed in killing it with bureaucracy?20:42
*** IlyaG has quit IRC20:43
*** beekhof has joined #openstack-meeting20:43
ttxdeath by review20:43
russellbttx: heh, which ones?  long list?20:43
jeblairttx: ++removal20:43
mesteryttx: ++20:43
annegentlettx: as many as are not running PTLs?20:43
ttxrussellb: no, short.20:43
sdaguettx: ++20:43
russellbthat's good to hear ...20:43
ttxThanks to thingee for being exceptionally persistent20:43
annegentlenice thingee20:43
lifelessjeblair: '20:44
lifelessFollowing Doug Hellmann's and @lifeless' comments, I will try and find another solution.'20:44
annegentleso our best guess is that most PTLs will stand again and just haven't sent in a patch?20:44
ttxSlot allocatiojn to be published tomorrow20:44
*** MarkAtwood has joined #openstack-meeting20:44
lifelessjeblair: so yes, I think.20:44
*** zz_dimtruck is now known as dimtruck20:44
cdentlifeless: can you link me to that review please?20:44
russellbopenstack governance garbage collection?  :)20:44
ttxannegentle: a lot submissions just drop on the last day20:44
lifelesshttps://review.openstack.org/#/c/277893/20:44
mesteryrussellb: lol20:44
annegentlettx: yah20:45
ttxrussellb: that is my TC election platform20:45
russellbnice20:45
*** SlickNik has joined #openstack-meeting20:45
russellbno summit slots, no PTL, the reference count for this project has reached 0 and will now be removed20:45
cdentthanks20:45
*** fzdarsky is now known as fzdarsky|afk20:45
*** dmorita has joined #openstack-meeting20:45
jeblairlifeless: that's a shame.  i honestly feel there is a very good argument for using it.20:45
sdaguerussellb: NullPointerException20:45
ttxWe got out of the way successfully, but we approved a lot of things by leaps of faith. I'd argue newton is cleanup time20:45
*** tongli has quit IRC20:46
* flaper87 likes that20:46
mesteryttx: Sounds like an 80s movie: "OpenStack Newton: It's payback time."20:46
jeblairlifeless: but i also agree it's not worth having if the question is moot.20:46
russellbyes, we should protect "in OpenStack" as having some real meaning20:46
annegentlettx: yeah20:46
dhellmannjeblair , lifeless : my -2 was procedural there for the freeze :-/20:46
ttxwe have 15 more minutes, any topic you'd like to discuss ?20:46
sdaguehttps://review.openstack.org/#/c/292918/20:46
sdaguewe seemed to have not had a testing clause in the asserts can upgrade tag20:46
sdaguewhich I think is an oversight we should fix up20:47
lifelessdhellmann: yes, I know20:47
ttxsdague: how about the same commit removes the tag from affected projects ? That would make the consequence clearer20:47
russellbsdague: ++20:47
dansmithttx: I can, if you like20:47
dhellmanndansmith : yeah, please do20:47
dansmithroger20:47
russellbthanks dane_leblanc20:48
sdagueit's the 2 non ceilometer telemetry projects I think20:48
russellberr, thanks dansmith20:48
ttxheh20:48
sdaguebut there might be something else complicated there about why they are getting tested because they are all very complicated in how they test20:48
lifelessjeblair: I think its a great testing tool to use; in C land it would be unambiguous about how it could be used20:48
dansmithI'll survey the project config, propose to remove the ones I think aren't right, and maybe we can get the PTLs to confirm20:48
*** IlyaG has joined #openstack-meeting20:49
*** ihrachys has joined #openstack-meeting20:50
*** sdake has quit IRC20:50
*** rtheis has quit IRC20:50
russellb*crickets*20:51
jeblairlifeless: yep.  with us not distributing scapy itself, i think only section 2b would be at issue, right?  and then that would be asking whether dragonflow was derived from scapy.  with it only being used as a test-time requirement, i think that would be a stretch.20:51
dhellmannmaybe the dragonflow test suite would have to be gpled20:52
jeblairlifeless: whether that then results in us laying a minefield for downstream packagers is an open question.  :)20:52
*** timcline has joined #openstack-meeting20:52
lifelessjeblair: in C land, there would be a separate binary for tests, and one could simply not distribute that binary20:52
sdaguelifeless: you can simply not distribute our tests20:52
*** sdake has joined #openstack-meeting20:53
lifelesssdague: as jeblair says - ?minefield20:53
*** timcline has quit IRC20:53
*** fzdarsky|afk has quit IRC20:53
*** _nadya_ has quit IRC20:53
lifelessI'm sure everyone here gets that one of the key things the GPL works on is totally missing in Python: there is no derivation or inclusion of an interface at compile time20:53
*** timcline has joined #openstack-meeting20:54
lifelessthe oracle case that made interface copyright a thing re-introduces that though20:54
*** baojg has joined #openstack-meeting20:54
lifelesssdague: so - practical consequence of 'simply not' - we'd need to teach pbr to exclude tests from wheels that we publish to pypi20:55
jrollsdague: upgrades tag thing is interesting, I thought there was a testing clause there before (which is why ironic hasn't asserted that tag)20:55
*** harshs has joined #openstack-meeting20:55
sdaguejroll: I did too20:55
sdagueand I think there should be20:55
jroll+120:56
lifelessanyhow, I still think the simplest thing is just to ask scapy - 'hey, if we used scapy in our test suite, would you consider that OK or not' ?20:56
sdaguejust because we've found so many issues when enabling it in projects, and it helps expose upgrade issues to devs they might not have thought about20:56
*** keedya has joined #openstack-meeting20:56
amritha question ... when's the next TC meeting? 2 weeks?20:56
jeblairlifeless, sdague: that's *if* dragonflow tests are considered derived works; there's an argument they may not be.20:56
lifelessif upstream don't have an issue, meh, move on.20:56
jeblairlifeless: but yes, that.  :)20:56
anteayaamrith: http://eavesdrop.openstack.org/#Technical_Committee_Meeting20:57
lifelessjeblair: I actually need to make time to read the oracle-google decision in detail w.r.t. interface copyright20:57
lifelessjeblair: I rather suspect it has significant bearing on that question20:57
amrithgood I asked, I thought it was 2 weeks ... thx anteaya20:57
anteayaamrith: welcome20:58
dtroyerlifeless: yes, also keep in mind that a single decision doesn't make it settled precedent yet, only in a single US Circuit…  still can't be ignored though20:58
*** neiljerram has quit IRC20:58
*** baoli has quit IRC20:58
jeblairlifeless: that will be interesting.  also, totally looking forward to the gpl behaving differently in the 9th circuit :)20:58
lifelessdtroyer: indeed20:59
jeblairdtroyer: yeah20:59
*** baoli has joined #openstack-meeting20:59
lifelessjeblair: its under appeal?20:59
jeblairlifeless: i don't know20:59
lifelessjeblair: oh - I don't get the 9th circuit ref then ?20:59
*** baojg has quit IRC20:59
* dtroyer still misses Groklaw20:59
lifelessdtroyer: ++ :(21:00
egon:-/21:00
dimslifeless : https://www.ca9.uscourts.gov/21:00
ttxoh well, time is up21:00
dtroyerlifeless: that's where the current decision was made, other curcuits do not have to necessarily follow it21:00
russellbthanks everyone!21:00
ttxThanks everyone!21:00
jeblairlifeless: i thought it was a 9th circuit decision21:00
flaper87o/21:00
ttx#endmeeting21:00
*** openstack changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"21:00
openstackMeeting ended Tue Mar 15 21:00:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-15-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-15-20.00.txt21:00
lifelessdtroyer: jeblair: ah ack.21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-03-15-20.00.log.html21:00
ttxcontinue in #openstack-ianal21:00
dtroyerjeblair: yes, it was21:01
*** haomaiwa_ has quit IRC21:01
*** haomaiwang has joined #openstack-meeting21:01
*** annegentle has quit IRC21:02
*** cdent has left #openstack-meeting21:02
*** sdake_ has joined #openstack-meeting21:02
lifelessttx: please no....21:02
*** neelashah has joined #openstack-meeting21:02
ttxheh21:02
*** thorst_ has quit IRC21:03
jeblairtoo late21:03
*** angdraug has joined #openstack-meeting21:03
rockygthingee, what's the cross project channel again?21:03
bswartz#openstack-meeting-cp21:03
thingeethanks bswartz21:03
*** rtheis has joined #openstack-meeting21:04
*** sdake has quit IRC21:05
*** MarkAtwood has quit IRC21:05
*** JRobinson__ has joined #openstack-meeting21:05
*** rtheis has quit IRC21:05
*** shamail has joined #openstack-meeting21:05
rockygthanks bswartz!21:05
*** keedya has quit IRC21:05
*** raildo is now known as raildo-afk21:05
*** todin has quit IRC21:05
*** AJaeger has left #openstack-meeting21:06
*** rfolco has quit IRC21:06
*** aysyd has quit IRC21:06
*** thorst_ has joined #openstack-meeting21:09
*** sdague has quit IRC21:09
*** eharney has quit IRC21:09
*** Shrews has left #openstack-meeting21:09
*** singhj has quit IRC21:10
*** keedya has joined #openstack-meeting21:11
*** tsandall has joined #openstack-meeting21:12
*** baoli has quit IRC21:13
*** thorst_ has quit IRC21:13
*** baoli has joined #openstack-meeting21:13
*** vishwanathj has quit IRC21:14
*** lblanchard has quit IRC21:15
*** maishsk has quit IRC21:15
*** maishsk_ has joined #openstack-meeting21:15
*** thorst_ has joined #openstack-meeting21:15
*** jtomasek has quit IRC21:16
*** Guest93664 is now known as med_21:17
*** med_ has joined #openstack-meeting21:17
*** jtomasek has joined #openstack-meeting21:18
*** thorst_ has quit IRC21:20
*** esker has quit IRC21:20
*** esker has joined #openstack-meeting21:20
*** kprabhu has quit IRC21:21
*** IlyaG has quit IRC21:21
*** iyamahat has quit IRC21:22
*** kprabhu has joined #openstack-meeting21:22
*** yamahata has joined #openstack-meeting21:22
*** wojdev has quit IRC21:23
*** keedya has quit IRC21:23
*** sdake_ is now known as sdake21:23
*** bobh has quit IRC21:25
*** esker has quit IRC21:26
*** vishwanathj has joined #openstack-meeting21:26
*** amitgandhinz has quit IRC21:26
*** spzala_ has quit IRC21:26
*** vijendar has quit IRC21:26
*** baoli has quit IRC21:27
*** baoli has joined #openstack-meeting21:27
*** jtomasek has quit IRC21:28
*** Leo_ has quit IRC21:29
*** Leo_ has joined #openstack-meeting21:29
*** spzala has joined #openstack-meeting21:30
*** jungleboyj has quit IRC21:32
*** jprovazn has quit IRC21:32
*** baoli has quit IRC21:32
*** Leo_ has quit IRC21:33
*** Leo_ has joined #openstack-meeting21:33
*** thorst_ has joined #openstack-meeting21:33
*** jichen has quit IRC21:34
*** thorst_ has quit IRC21:34
*** thorst_ has joined #openstack-meeting21:34
*** asettle has joined #openstack-meeting21:34
*** spzala has quit IRC21:34
*** amrith has quit IRC21:35
*** amrith has joined #openstack-meeting21:35
*** eglynn has quit IRC21:36
*** eharney has joined #openstack-meeting21:36
*** pcaruana has quit IRC21:38
*** keedya has joined #openstack-meeting21:38
*** Leom has joined #openstack-meeting21:38
*** pradk has quit IRC21:38
*** sc68cal has quit IRC21:39
*** Leo_ has quit IRC21:39
*** e0ne has quit IRC21:40
*** Leo_ has joined #openstack-meeting21:42
*** baoli has joined #openstack-meeting21:43
*** kprabhu has quit IRC21:43
*** cdelatte has quit IRC21:44
*** Leom has quit IRC21:45
*** maishsk_ has quit IRC21:45
*** cdelatte has joined #openstack-meeting21:45
*** baoli has quit IRC21:45
*** baoli has joined #openstack-meeting21:46
*** matrohon has quit IRC21:47
*** singhj has joined #openstack-meeting21:48
*** edtubill has quit IRC21:49
*** adahms has joined #openstack-meeting21:50
*** fawadkhaliq has quit IRC21:51
*** fawadkhaliq has joined #openstack-meeting21:51
*** pcaruana has joined #openstack-meeting21:52
*** timcline has quit IRC21:55
*** baojg has joined #openstack-meeting21:55
*** timcline has joined #openstack-meeting21:55
*** baoli has quit IRC21:59
*** baojg has quit IRC21:59
*** pvaneck has quit IRC21:59
*** xyang1 has quit IRC22:00
*** timcline has quit IRC22:00
*** yamahata has quit IRC22:00
*** fawadkhaliq has quit IRC22:00
*** haomaiwang has quit IRC22:01
*** fawadkhaliq has joined #openstack-meeting22:01
*** harlowja has joined #openstack-meeting22:01
*** MarkAtwood has joined #openstack-meeting22:01
*** kbyrne has quit IRC22:01
*** haomaiwa_ has joined #openstack-meeting22:01
*** baoli has joined #openstack-meeting22:02
*** vishwanathj has quit IRC22:02
*** raildo-afk is now known as raildo22:02
*** singhj has quit IRC22:02
*** shamail has quit IRC22:04
*** singhj has joined #openstack-meeting22:06
*** raildo is now known as raildo-afk22:06
*** galstrom is now known as galstrom_zzz22:09
*** sdake has quit IRC22:09
*** baoli has quit IRC22:10
*** rockyg has quit IRC22:10
*** baoli has joined #openstack-meeting22:10
*** dims_ has joined #openstack-meeting22:11
*** sigmavirus24 is now known as sigmavirus24_awa22:12
*** spotz is now known as spotz_zzz22:12
*** esheffield has quit IRC22:12
*** esheffield has joined #openstack-meeting22:12
*** david-lyle has quit IRC22:13
*** dims has quit IRC22:14
*** JRobinson__ is now known as JRobinson__afk22:14
*** iyamahat has joined #openstack-meeting22:15
*** piet has quit IRC22:16
*** dims has joined #openstack-meeting22:16
*** dims_ has quit IRC22:17
*** claudiub has quit IRC22:17
*** dimtruck is now known as zz_dimtruck22:18
*** singhj has quit IRC22:19
*** r-mibu has quit IRC22:20
*** r-mibu has joined #openstack-meeting22:20
*** absubram has quit IRC22:21
*** keedya has quit IRC22:22
*** spzala has joined #openstack-meeting22:28
*** piet has joined #openstack-meeting22:29
*** jorge_munoz has quit IRC22:30
*** MaxPC has joined #openstack-meeting22:30
*** tsandall has quit IRC22:31
*** shakamunyi has joined #openstack-meeting22:32
*** iyamahat has quit IRC22:32
*** neelashah has quit IRC22:32
*** asettle has quit IRC22:33
*** MarkAtwood has quit IRC22:34
*** pvaneck has joined #openstack-meeting22:35
*** asettle has joined #openstack-meeting22:35
*** iyamahat has joined #openstack-meeting22:37
*** knikolla has quit IRC22:42
*** cshahani has quit IRC22:44
*** baoli has quit IRC22:44
*** spzala has quit IRC22:44
*** edmondsw has left #openstack-meeting22:44
*** edmondsw has quit IRC22:44
*** spzala has joined #openstack-meeting22:45
*** JRobinson__afk is now known as JRobinson__22:47
*** ninag has quit IRC22:47
*** weshay has quit IRC22:48
*** hashar has quit IRC22:49
*** mbound has quit IRC22:50
*** jckasper has quit IRC22:51
*** spzala has quit IRC22:51
*** jorge_munoz has joined #openstack-meeting22:52
*** jorge_munoz has quit IRC22:54
*** baojg has joined #openstack-meeting22:56
*** timcline has joined #openstack-meeting22:56
*** Leo_ has quit IRC22:56
*** piet has quit IRC22:56
*** azbiswas_ has quit IRC22:58
*** azbiswas has joined #openstack-meeting22:59
*** baojg has quit IRC23:00
*** azbiswas has quit IRC23:00
*** MaxPC has quit IRC23:00
*** timcline has quit IRC23:00
*** haomaiwa_ has quit IRC23:01
*** haomaiwa_ has joined #openstack-meeting23:01
*** azbiswas has joined #openstack-meeting23:02
*** rbak has quit IRC23:04
*** yamamoto_ has quit IRC23:05
*** dims has quit IRC23:06
*** knikolla has joined #openstack-meeting23:10
*** bryan_att has quit IRC23:12
*** iyamahat has quit IRC23:12
*** iyamahat has joined #openstack-meeting23:13
*** roxanagh_ has joined #openstack-meeting23:18
*** banix has joined #openstack-meeting23:20
*** roxanagh_ has quit IRC23:22
*** carolbarrett has quit IRC23:25
*** azbiswas has quit IRC23:33
*** xinwu has quit IRC23:34
*** tochi has joined #openstack-meeting23:36
*** IlyaG has joined #openstack-meeting23:37
*** Qiming has joined #openstack-meeting23:39
*** jckasper has joined #openstack-meeting23:42
*** ihrachys has quit IRC23:45
*** sdake has joined #openstack-meeting23:45
*** kzaitsev_mb has quit IRC23:47
*** harlowja has quit IRC23:47
*** jckasper has quit IRC23:47
*** jckasper has joined #openstack-meeting23:48
*** eil397 has quit IRC23:48
*** salv-orlando has quit IRC23:49
*** cdub has quit IRC23:50
*** ivar-lazzaro has quit IRC23:50
*** mbound has joined #openstack-meeting23:51
*** yamamoto_ has joined #openstack-meeting23:51
*** toddjohn has quit IRC23:51
*** jckasper has quit IRC23:52
*** cshahani has joined #openstack-meeting23:56
*** mbound has quit IRC23:56
*** baojg has joined #openstack-meeting23:56
*** pabelanger has joined #openstack-meeting23:56
*** timcline has joined #openstack-meeting23:57
*** pabelanger has left #openstack-meeting23:57
*** sdake_ has joined #openstack-meeting23:59
*** xinwu has joined #openstack-meeting23:59

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