Tuesday, 2015-07-28

*** jwang has quit IRC00:00
*** jwang has joined #openstack-meeting00:00
*** penick has quit IRC00:01
*** amitgandhinz has joined #openstack-meeting00:01
*** stanchan has quit IRC00:01
*** Sukhdev has quit IRC00:01
*** harshs has joined #openstack-meeting00:02
*** adahms has joined #openstack-meeting00:04
*** adahms has quit IRC00:04
*** adahms has joined #openstack-meeting00:05
*** vishwanathj has quit IRC00:05
*** penick has joined #openstack-meeting00:06
*** topol has quit IRC00:08
*** markvoelker has joined #openstack-meeting00:09
*** okrieg has quit IRC00:10
*** davidjc has quit IRC00:10
*** xingchao has joined #openstack-meeting00:14
*** andreykurilin__ has quit IRC00:14
*** penick has quit IRC00:19
*** vivek-ebay has quit IRC00:20
*** jasondotstar has quit IRC00:21
*** jasondotstar has joined #openstack-meeting00:22
*** _amrith_ is now known as amrith00:22
*** amitgandhinz has quit IRC00:22
*** dims has quit IRC00:22
*** yapeng has quit IRC00:23
*** shadower has quit IRC00:23
*** shadower has joined #openstack-meeting00:23
*** sridhar_ram has quit IRC00:23
*** banix has quit IRC00:24
*** mtanino_ has joined #openstack-meeting00:25
*** vivek-ebay has joined #openstack-meeting00:26
*** mtanino has quit IRC00:26
*** jmckind has joined #openstack-meeting00:27
*** tsekiyam_ has joined #openstack-meeting00:27
*** pvaneck has quit IRC00:28
*** tsekiyama has quit IRC00:31
*** banix has joined #openstack-meeting00:32
*** dims has joined #openstack-meeting00:32
*** salv-orlando has joined #openstack-meeting00:33
*** cdub has quit IRC00:34
*** rbak has joined #openstack-meeting00:36
*** DericHorn-HP has quit IRC00:37
*** salv-orlando has quit IRC00:37
*** PrashantS has joined #openstack-meeting00:39
*** dolpher has joined #openstack-meeting00:41
*** Brian has joined #openstack-meeting00:41
*** Brian is now known as Guest9724000:42
*** padkrish has joined #openstack-meeting00:43
*** jasondotstar is now known as jasondotstar|afk00:43
*** MarkAtwood has quit IRC00:43
*** glauco has joined #openstack-meeting00:44
*** xingchao has quit IRC00:44
*** xingchao has joined #openstack-meeting00:45
*** ildikov has joined #openstack-meeting00:46
*** Guest97240 has quit IRC00:46
*** padkrish has quit IRC00:47
*** aimon has joined #openstack-meeting00:47
*** harshs has quit IRC00:47
*** xingchao has quit IRC00:48
*** glauco has quit IRC00:48
*** kebray has quit IRC00:49
*** sbalukoff has quit IRC00:50
*** ricolin has joined #openstack-meeting00:51
*** elo1 has joined #openstack-meeting00:51
*** amitgandhinz has joined #openstack-meeting00:52
*** rbak has quit IRC00:53
*** markmcclain has quit IRC00:53
*** elo has quit IRC00:54
*** kevinbenton has quit IRC00:54
*** rbak has joined #openstack-meeting00:55
*** frank_young has joined #openstack-meeting00:56
*** kevinbenton has joined #openstack-meeting00:57
*** markmcclain has joined #openstack-meeting00:57
*** puranamr has quit IRC00:57
*** Jeffrey4l has quit IRC01:00
*** frank_young has quit IRC01:00
*** novas0x2a|laptop has quit IRC01:01
*** crc32 has quit IRC01:03
*** dmacpher-afk has quit IRC01:03
*** frank_young has joined #openstack-meeting01:04
*** jmckind has quit IRC01:05
*** jmckind has joined #openstack-meeting01:07
*** dneary has quit IRC01:07
*** bobh has joined #openstack-meeting01:08
*** jmckind has quit IRC01:09
*** sbalukoff has joined #openstack-meeting01:11
*** tangchen has quit IRC01:11
*** s3wong has quit IRC01:12
*** tangchen has joined #openstack-meeting01:12
*** Jeffrey4l has joined #openstack-meeting01:12
*** Apoorva has quit IRC01:14
*** Sukhdev has joined #openstack-meeting01:14
*** vivek-ebay has quit IRC01:14
*** vnod has joined #openstack-meeting01:16
*** jasondotstar|afk has quit IRC01:17
*** absubram has quit IRC01:18
*** PrashantS has quit IRC01:19
*** bobh has quit IRC01:22
*** haomaiwang has quit IRC01:22
*** haomaiwang has joined #openstack-meeting01:23
*** rbak has quit IRC01:24
*** rbak has joined #openstack-meeting01:24
*** Sukhdev has quit IRC01:25
*** vnod has quit IRC01:28
*** topol has joined #openstack-meeting01:28
*** jwcroppe has quit IRC01:30
*** jwcroppe has joined #openstack-meeting01:30
*** ivasev has joined #openstack-meeting01:33
*** carl_baldwin has joined #openstack-meeting01:33
*** Brian has joined #openstack-meeting01:34
*** okrieg has joined #openstack-meeting01:34
*** Brian is now known as Guest7673101:34
*** ivasev_ has joined #openstack-meeting01:34
*** jwcroppe has quit IRC01:35
*** ianw has quit IRC01:37
*** ianw has joined #openstack-meeting01:37
*** ivasev has quit IRC01:38
*** dane_leblanc has joined #openstack-meeting01:42
*** leeantho has quit IRC01:43
*** rbak has quit IRC01:43
*** padkrish has joined #openstack-meeting01:43
*** salv-orlando has joined #openstack-meeting01:44
*** pm90_ has joined #openstack-meeting01:47
*** padkrish has quit IRC01:48
*** salv-orlando has quit IRC01:48
*** spzala has joined #openstack-meeting01:50
*** dmacpher has joined #openstack-meeting01:51
*** spzala has quit IRC01:51
*** carl_baldwin has quit IRC01:51
*** lexholden has quit IRC01:51
*** okrieg has quit IRC01:52
*** yamamoto has joined #openstack-meeting01:53
*** frank_young has quit IRC01:57
*** sbalukoff has quit IRC01:58
*** bauzas has quit IRC01:58
*** Piet has quit IRC01:58
*** jlvillal has quit IRC01:58
*** yingjun has joined #openstack-meeting01:59
*** jlvillal has joined #openstack-meeting01:59
*** xingchao has joined #openstack-meeting02:00
*** bauzas has joined #openstack-meeting02:00
*** ganeshna has joined #openstack-meeting02:01
*** pm90__ has joined #openstack-meeting02:02
*** renjiesun has joined #openstack-meeting02:03
*** funzo has quit IRC02:03
*** tsekiyam_ has quit IRC02:03
*** funzo has joined #openstack-meeting02:04
*** pm90_ has quit IRC02:05
*** okrieg has joined #openstack-meeting02:06
*** unicell has quit IRC02:06
*** mtanino_ has quit IRC02:06
*** okrieg has quit IRC02:06
*** stevemar has joined #openstack-meeting02:07
*** dolphm has quit IRC02:07
*** d34dh0r53 has quit IRC02:07
*** sigmavirus24 has quit IRC02:07
*** eglute has quit IRC02:07
*** renjiesun has quit IRC02:07
*** d34dh0r53 has joined #openstack-meeting02:08
*** d34dh0r53 has quit IRC02:08
*** d34dh0r53 has joined #openstack-meeting02:08
*** funzo has quit IRC02:08
*** okrieg has joined #openstack-meeting02:09
*** eglute has joined #openstack-meeting02:09
*** dolphm has joined #openstack-meeting02:09
*** d34dh0r53 has quit IRC02:09
*** dolphm has quit IRC02:09
*** eglute has quit IRC02:09
*** d34dh0r53 has joined #openstack-meeting02:10
*** dolphm has joined #openstack-meeting02:10
*** eglute has joined #openstack-meeting02:10
*** jasondotstar|afk has joined #openstack-meeting02:12
*** gongysh has joined #openstack-meeting02:14
*** ganeshna has quit IRC02:18
*** huangtianhua has joined #openstack-meeting02:18
*** renjiesun has joined #openstack-meeting02:21
*** dane_leblanc has quit IRC02:26
*** bobh has joined #openstack-meeting02:27
*** xingchao has quit IRC02:34
*** Daisy has joined #openstack-meeting02:35
*** dims has quit IRC02:35
*** changbl has quit IRC02:37
*** xingchao has joined #openstack-meeting02:38
*** Murali has joined #openstack-meeting02:38
*** renjiesun has quit IRC02:42
*** padkrish has joined #openstack-meeting02:44
*** amitgandhinz has quit IRC02:47
*** padkrish has quit IRC02:49
*** banix has quit IRC02:49
*** okrieg has quit IRC02:51
*** okrieg has joined #openstack-meeting02:52
*** okrieg has quit IRC02:57
*** ganeshna has joined #openstack-meeting02:57
*** dolpher has quit IRC02:58
*** stevemar has quit IRC03:01
*** PrashantS has joined #openstack-meeting03:02
*** chmouel_ has joined #openstack-meeting03:03
*** chmouel- has joined #openstack-meeting03:04
*** chmouel| has joined #openstack-meeting03:04
*** chmouel^ has joined #openstack-meeting03:05
*** pm90_ has joined #openstack-meeting03:07
*** Apoorva has joined #openstack-meeting03:07
*** Murali has quit IRC03:07
*** baoli has joined #openstack-meeting03:08
*** pm90__ has quit IRC03:10
*** sajeesh has quit IRC03:10
*** chmouel^ has quit IRC03:10
*** chmouel- has quit IRC03:10
*** chmouel_ has quit IRC03:10
*** chmouel| has quit IRC03:10
*** chmouel has quit IRC03:10
*** chmouel has joined #openstack-meeting03:11
*** PrashantS has quit IRC03:11
*** vivek-ebay has joined #openstack-meeting03:11
*** harshs has joined #openstack-meeting03:11
*** PrashantS has joined #openstack-meeting03:11
*** baoli has quit IRC03:13
*** otter768 has quit IRC03:14
*** larainema has joined #openstack-meeting03:14
*** PrashantS has quit IRC03:16
*** tochi has joined #openstack-meeting03:18
*** xingchao has quit IRC03:18
*** BharatK has joined #openstack-meeting03:19
*** xingchao has joined #openstack-meeting03:20
*** Sukhdev has joined #openstack-meeting03:21
*** bobh has quit IRC03:21
*** epico has joined #openstack-meeting03:22
*** sbalukoff has joined #openstack-meeting03:22
*** jasondotstar|afk has quit IRC03:24
*** DericHorn-HP has joined #openstack-meeting03:25
*** balajiiyer has joined #openstack-meeting03:25
*** epico has quit IRC03:28
*** VW_ has joined #openstack-meeting03:29
*** jwcroppe has joined #openstack-meeting03:30
*** edtubill has joined #openstack-meeting03:30
*** edtubill has left #openstack-meeting03:31
*** coolsvap|away is now known as coolsvap03:32
*** Daisy has quit IRC03:33
*** Daisy has joined #openstack-meeting03:34
*** epico has joined #openstack-meeting03:35
*** ivar-lazzaro has quit IRC03:35
*** Daisy has quit IRC03:36
*** Daisy has joined #openstack-meeting03:36
*** Jeffrey4l has quit IRC03:37
*** vivek-ebay has quit IRC03:42
*** Daisy has quit IRC03:45
*** amrith is now known as _amrith_03:45
*** glauco has joined #openstack-meeting03:45
*** Daisy has joined #openstack-meeting03:45
*** julim has quit IRC03:46
*** Daisy has quit IRC03:50
*** glauco has quit IRC03:50
*** stevemar has joined #openstack-meeting03:50
*** htruta_ has quit IRC03:50
*** harshs has quit IRC03:51
*** Jeffrey4l has joined #openstack-meeting03:51
*** stevemar has quit IRC03:52
*** yingjun has quit IRC03:56
*** vivek-ebay has joined #openstack-meeting03:57
*** Jeffrey4l has quit IRC03:57
*** amitgandhinz has joined #openstack-meeting03:57
*** ayoung has quit IRC03:58
*** gongysh has quit IRC04:00
*** gongysh has joined #openstack-meeting04:01
*** vivek-ebay has quit IRC04:01
*** amitgandhinz has quit IRC04:01
*** jwcroppe has quit IRC04:02
*** vivek-ebay has joined #openstack-meeting04:02
*** jwcroppe has joined #openstack-meeting04:03
*** Guest76731 has quit IRC04:03
*** moha_hunt has quit IRC04:04
*** VW_ has quit IRC04:04
*** markvoelker has quit IRC04:04
*** VW_ has joined #openstack-meeting04:04
*** jamespage has quit IRC04:05
*** jwcroppe_ has joined #openstack-meeting04:06
*** PrashantS has joined #openstack-meeting04:07
*** jwcroppe has quit IRC04:08
*** xingchao has quit IRC04:08
*** AzherKhan has joined #openstack-meeting04:09
*** VW_ has quit IRC04:09
*** Jeffrey4l has joined #openstack-meeting04:09
*** harshs has joined #openstack-meeting04:10
*** nelsnelson has quit IRC04:13
*** BharatK has quit IRC04:15
*** JRobinson__ is now known as JRobinson__afk04:15
*** comay has quit IRC04:16
*** jwcroppe_ has quit IRC04:16
*** jwcroppe has joined #openstack-meeting04:17
*** ivar-lazzaro has joined #openstack-meeting04:20
*** funzo has joined #openstack-meeting04:20
*** jwcroppe has quit IRC04:22
*** SumitNaiksatam has joined #openstack-meeting04:27
*** padkrish has joined #openstack-meeting04:28
*** padkrish has quit IRC04:28
*** padkrish has joined #openstack-meeting04:29
*** padkrish_ has joined #openstack-meeting04:30
*** padkrish has quit IRC04:30
*** Brian has joined #openstack-meeting04:31
*** Brian is now known as Guest8256204:31
*** Apoorva has quit IRC04:32
*** Guest82562 has quit IRC04:32
*** BharatK has joined #openstack-meeting04:33
*** SumitNaiksatam has left #openstack-meeting04:33
*** gongysh_ has joined #openstack-meeting04:34
*** pm90__ has joined #openstack-meeting04:34
*** padkrish_ has quit IRC04:35
*** padkrish has joined #openstack-meeting04:35
*** DericHorn-HP has quit IRC04:37
*** padkrish has quit IRC04:37
*** pm90_ has quit IRC04:37
*** gongysh has quit IRC04:37
*** padkrish has joined #openstack-meeting04:37
*** BharatK has quit IRC04:38
*** harshs has quit IRC04:40
*** DericHorn-HP has joined #openstack-meeting04:41
*** comay has joined #openstack-meeting04:41
*** BharatK has joined #openstack-meeting04:43
*** PrashantS has quit IRC04:45
*** funzo has quit IRC04:46
*** DericHorn-HP has quit IRC04:46
*** PrashantS has joined #openstack-meeting04:46
*** BharatK has quit IRC04:47
*** balajiiyer has quit IRC04:48
*** BharatK has joined #openstack-meeting04:49
*** padkrish has quit IRC04:50
*** PrashantS has quit IRC04:50
*** padkrish has joined #openstack-meeting04:51
*** lpeer has joined #openstack-meeting04:51
*** PrashantS has joined #openstack-meeting04:53
*** jwcroppe has joined #openstack-meeting04:56
*** jwcroppe has quit IRC04:58
*** jwcroppe has joined #openstack-meeting04:58
*** yamahata has joined #openstack-meeting04:59
*** MarkAtwood has joined #openstack-meeting04:59
*** jwcroppe_ has joined #openstack-meeting05:01
*** PrashantS has quit IRC05:03
*** jwcroppe has quit IRC05:03
*** PrashantS has joined #openstack-meeting05:03
*** markvoelker has joined #openstack-meeting05:05
*** Daisy has joined #openstack-meeting05:05
*** ub has quit IRC05:06
*** PrashantS has quit IRC05:07
*** markvoelker has quit IRC05:10
*** ivar-lazzaro has quit IRC05:11
*** doude has quit IRC05:13
*** ganeshna has quit IRC05:13
*** ganeshna has joined #openstack-meeting05:13
*** unicell has joined #openstack-meeting05:14
*** e0ne has joined #openstack-meeting05:14
*** otter768 has joined #openstack-meeting05:15
*** aimon has quit IRC05:18
*** JRobinson__afk is now known as JRobinson__05:19
*** huangtianhua has quit IRC05:19
*** otter768 has quit IRC05:19
*** Sukhdev has quit IRC05:20
*** DericHorn-HP has joined #openstack-meeting05:21
*** Brian has joined #openstack-meeting05:23
*** padkrish has quit IRC05:23
*** Brian is now known as Guest6185105:24
*** Guest61851 has quit IRC05:25
*** hrou has quit IRC05:27
*** padkrish has joined #openstack-meeting05:27
*** renjiesun has joined #openstack-meeting05:27
*** renjiesu_ has joined #openstack-meeting05:29
*** PrashantS has joined #openstack-meeting05:29
*** renjiesun has quit IRC05:33
*** PrashantS has quit IRC05:33
*** PrashantS has joined #openstack-meeting05:34
*** harshs has joined #openstack-meeting05:35
*** PrashantS has quit IRC05:35
*** pnavarro has joined #openstack-meeting05:35
*** PrashantS has joined #openstack-meeting05:35
*** SridharG has joined #openstack-meeting05:38
*** ivasev_ has quit IRC05:38
*** renjiesu_ has quit IRC05:39
*** renjiesun has joined #openstack-meeting05:40
*** e0ne has quit IRC05:42
*** DericHorn-HP has quit IRC05:43
*** e0ne has joined #openstack-meeting05:44
*** renjiesun has quit IRC05:44
*** PrashantS has quit IRC05:44
*** PrashantS has joined #openstack-meeting05:45
*** Murali has joined #openstack-meeting05:45
*** mrmartin has joined #openstack-meeting05:45
*** jprovazn has joined #openstack-meeting05:46
*** numan has joined #openstack-meeting05:48
*** yamamoto has quit IRC05:48
*** PrashantS has quit IRC05:49
*** e0ne has quit IRC05:51
*** yapeng has joined #openstack-meeting05:53
*** topol has quit IRC05:54
*** PrashantS has joined #openstack-meeting05:55
*** salv-orlando has joined #openstack-meeting05:55
*** e0ne has joined #openstack-meeting05:55
*** yamamoto has joined #openstack-meeting05:56
*** harshs has quit IRC05:56
*** unicell1 has joined #openstack-meeting05:58
*** unicell has quit IRC05:59
*** albertom has quit IRC06:01
*** ganeshna has quit IRC06:02
*** vivek-ebay has quit IRC06:05
*** albertom has joined #openstack-meeting06:09
*** zeih has joined #openstack-meeting06:10
*** zeih has quit IRC06:11
*** yingjun has joined #openstack-meeting06:12
*** e0ne has quit IRC06:13
*** yapeng has quit IRC06:13
*** hichihara has quit IRC06:14
*** lukebrooker has quit IRC06:14
*** Jeffrey4l has quit IRC06:14
*** _nadya_ has joined #openstack-meeting06:16
*** tiantian has joined #openstack-meeting06:18
*** JRobinson__ has quit IRC06:18
*** ganeshna has joined #openstack-meeting06:19
*** _nadya_ has quit IRC06:20
*** lukebrooker has joined #openstack-meeting06:22
*** Brian has joined #openstack-meeting06:24
*** jamespage has joined #openstack-meeting06:24
*** Brian is now known as Guest3836706:24
*** MarkAtwood has quit IRC06:24
*** belmoreira has joined #openstack-meeting06:25
*** Jeffrey4l has joined #openstack-meeting06:27
*** doude has joined #openstack-meeting06:27
*** doude has quit IRC06:27
*** doude has joined #openstack-meeting06:27
*** vishwanathj has joined #openstack-meeting06:28
*** PrashantS has quit IRC06:29
*** MarkAtwood has joined #openstack-meeting06:31
*** ub has joined #openstack-meeting06:33
*** liusheng has quit IRC06:36
*** tiantian has quit IRC06:37
*** liusheng has joined #openstack-meeting06:37
*** xingchao has joined #openstack-meeting06:37
*** tiantian has joined #openstack-meeting06:37
*** rossella_s has quit IRC06:37
*** xingchao has quit IRC06:38
*** rossella_s has joined #openstack-meeting06:38
*** jamespage_ has joined #openstack-meeting06:39
*** oanufriev has quit IRC06:40
*** xingchao has joined #openstack-meeting06:40
*** afazekas has joined #openstack-meeting06:44
*** pm90__ has quit IRC06:45
-openstackstatus- NOTICE: zuul is stuck and about to undergo an emergency restart, please be patient as job results may take a long time06:46
*** ChanServ changes topic to "zuul is stuck and about to undergo an emergency restart, please be patient as job results may take a long time"06:46
*** MarkAtwood has quit IRC06:46
*** _nadya_ has joined #openstack-meeting06:47
*** jamespage_ has quit IRC06:48
*** jwcroppe_ has quit IRC06:48
*** qwebirc236 has joined #openstack-meeting06:50
*** nmagnezi has joined #openstack-meeting06:52
*** xingchao has quit IRC06:52
*** xingchao has joined #openstack-meeting06:53
*** _nadya_ has quit IRC06:53
*** sahid has joined #openstack-meeting06:53
*** _nadya_ has joined #openstack-meeting06:53
*** ganeshna has quit IRC06:57
*** xingchao has quit IRC06:57
*** ganeshna has joined #openstack-meeting06:58
*** _nadya_ has quit IRC06:58
*** salv-orlando has quit IRC06:59
*** SumitNaiksatam has joined #openstack-meeting07:00
*** zehicle_IRL has quit IRC07:00
*** Berezin has joined #openstack-meeting07:03
*** ganeshna has quit IRC07:04
*** xingchao has joined #openstack-meeting07:04
*** scheuran has joined #openstack-meeting07:05
*** ganeshna has joined #openstack-meeting07:05
*** lukebrooker has quit IRC07:06
*** markvoelker has joined #openstack-meeting07:06
*** sdake has joined #openstack-meeting07:07
*** pnavarro has quit IRC07:08
*** zehicle_IRL has joined #openstack-meeting07:08
*** zeih has joined #openstack-meeting07:10
*** markvoelker has quit IRC07:11
*** achanda has quit IRC07:11
*** ganeshna has quit IRC07:14
*** lpeer_ has joined #openstack-meeting07:15
*** lpeer has quit IRC07:16
*** otter768 has joined #openstack-meeting07:16
*** elo1 has quit IRC07:17
*** achanda has joined #openstack-meeting07:18
*** renjiesun has joined #openstack-meeting07:20
*** zeih has quit IRC07:21
*** otter768 has quit IRC07:21
*** devvesa has joined #openstack-meeting07:22
*** elo has joined #openstack-meeting07:22
*** phil has joined #openstack-meeting07:24
*** safchain has joined #openstack-meeting07:25
*** phil is now known as Guest3364407:25
*** dmacpher has quit IRC07:27
*** mpaolino has joined #openstack-meeting07:29
*** atuvenie has joined #openstack-meeting07:30
*** renjiesun has quit IRC07:32
*** sahid has quit IRC07:35
*** ^Gal^_ has joined #openstack-meeting07:35
*** achanda has quit IRC07:35
*** ^Gal^_ has quit IRC07:36
*** ^Gal^_ has joined #openstack-meeting07:36
*** sahid has joined #openstack-meeting07:36
*** sahid has quit IRC07:36
*** qwebirc236 has quit IRC07:36
*** e0ne has joined #openstack-meeting07:37
*** sahid has joined #openstack-meeting07:38
*** Jeffrey4l has quit IRC07:40
*** ajayaa has joined #openstack-meeting07:40
*** qwebirc28348 has joined #openstack-meeting07:41
*** qwebirc20415 has joined #openstack-meeting07:41
*** qwebirc2486 has joined #openstack-meeting07:42
*** mrmartin has quit IRC07:42
*** lpeer_ has quit IRC07:43
*** ^Gal^ has quit IRC07:43
*** ^Gal^_ is now known as ^Gal^07:43
*** jlanoux has joined #openstack-meeting07:44
*** yamahata has quit IRC07:44
*** ^Gal^_ has joined #openstack-meeting07:45
*** ganeshna has joined #openstack-meeting07:45
*** achanda has joined #openstack-meeting07:46
*** glauco_ has joined #openstack-meeting07:47
*** zeih has joined #openstack-meeting07:47
*** salv-orlando has joined #openstack-meeting07:50
*** glauco_ has quit IRC07:51
*** lpeer_ has joined #openstack-meeting07:53
*** Jeffrey4l has joined #openstack-meeting07:53
*** oanufriev has joined #openstack-meeting07:54
*** pnavarro has joined #openstack-meeting07:54
*** coolsvap is now known as coolsvap|away07:57
*** sdake has quit IRC07:57
*** jhenner has quit IRC07:57
*** jhenner has joined #openstack-meeting07:58
tangchen Hi guys, is the third party meeting going to be held here ?07:58
*** zeih has quit IRC07:58
*** padkrish has quit IRC07:59
anteayaI'm not a guy08:00
*** hashar has joined #openstack-meeting08:00
anteayaand yes there will be a meeting here, at 0800 as I stated in the -infra channel several hours ago08:00
*** achanda has quit IRC08:00
*** achanda has joined #openstack-meeting08:01
*** aloga has quit IRC08:02
*** jwcroppe has joined #openstack-meeting08:02
*** aloga has joined #openstack-meeting08:02
*** ChanServ changes topic to "BP (Meeting topic: tricircle)"08:02
tangchenI'm sorry. UTC 0800, what's the time now ?08:02
-openstackstatus- NOTICE: zuul has been restarted and queues restored. It may take some time to work through the backlog.08:02
tangchenI thought now it is UTC 0800......08:03
anteayayes it is08:03
kaisersHi08:03
tangchenOK.08:03
tangchenIf I want to say something, should I say it here, or move to #openstack-infra08:03
*** achanda has quit IRC08:04
anteayacan you please exercise a bit of patience08:04
anteayathe topic needs to be fixed08:04
anteayathen I will start the meeting08:04
tangchenSure. thx08:04
*** adahms has quit IRC08:04
*** topol has joined #openstack-meeting08:06
anteayahopefully it will be fixed after the meeting08:07
anteaya#startmeeting third-party08:07
openstackMeeting started Tue Jul 28 08:07:16 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:07
*** openstack changes topic to " (Meeting topic: third-party)"08:07
openstackThe meeting name has been set to 'third_party'08:07
anteayaso tangchen do go ahead08:07
*** eantyshev has joined #openstack-meeting08:07
tangchenOK08:07
eantyshevhello!08:08
tangchenPlease take a look at here. http://paste.openstack.org/show/406017/08:08
anteayatangchen: why08:08
anteayadon't just tell me to click a link08:08
anteayagive me context08:08
tangchenI'm now working on setting up CI system for Fujitsu. I met a proxy issue when using zuul.08:08
anteayathank you08:09
tangchenI explained the context in the link.08:09
anteayathat is less helpful in a meeting08:09
anteaya#link http://paste.openstack.org/show/406017/08:09
anteayabut that you for trying to be clear08:10
anteayaso you are asking permission to post patches to zuul?08:10
anteayaanyone can post patches to zuul08:10
tangchenYes, so this kind of topic should not be discussed in a meeting, right?08:10
*** topol has quit IRC08:10
*** achanda has joined #openstack-meeting08:11
anteayaoh no it can be discussed08:12
anteayabut your goal is to post patches to zuul, is it not?08:12
tangchenYes it is.08:12
*** ndipanov has quit IRC08:12
anteayayou don't need anyone's permission to do that08:12
anteayanow if you had a patch to zuul and were asking for reviews08:12
anteayathat would be something wonderful to bring to a meeting08:12
anteayaas we can see what code you would like to introduce08:13
anteayaand possibly review08:13
anteayadoes that make sense08:13
tangchenOK. I can bring a patch here when I finished it. But before that, I also want some advice about how to make zuul work behind a proxy.08:14
tangchenHas anyone met the same problem before ?08:15
kaisersSry, no exp with zuul / proxy08:15
anteayamost of the people who are encountering this are in china08:16
anteayaas china sets up a firewall08:16
anteayaall infra tools were actually designed to not have to think about a firewall08:16
anteayaas open source doesn't need one08:16
anteayaand these are open source tools being used with an open source project08:17
tangchenOh no, I think it has nothing to do with the firewall in China. I set up the CI system on a machine in Japan.08:17
tangchenThe proxy is set by the company.08:17
*** zhhuabj_ has quit IRC08:17
tangchenfor some security reasons08:18
anteayaoh08:18
anteayathey really need security on throw away nodes?08:19
anteayaall of the infra tools need their own servers08:19
anteayathey should be on their own network08:19
anteayaand not share server space with anything else08:19
anteayathey aren't good neighbours08:19
anteayaand most folks don't have zuul behind a firewall08:21
anteayaso there will be fewer operators in the same situation08:21
tangchenIn my environment, servers cannot connect to internet directly. They should pass a proxy to limit which site can be accessed and which one cannot.08:21
eantyshevtangchen: May I ask a small question regarding your CI setup: how do you provide logs of your CI?08:22
lennyb_hi, sorry I am late08:22
tangchen<anteaya>: The zuul server is in the private environment. And it has to connect to Gerrit. So I want zuul to support a proxy.08:23
anteayalennyb_: no problem08:23
anteayatangchen: I understand08:23
*** ygbo has joined #openstack-meeting08:23
anteayatangchen: you asked if anyone else had the same issue, I'm saying it will be harder to find operators who have the same issue08:24
anteayatangchen: the folks from china are all behind a firewall, so might have some experience08:24
tangcheneantyshev: I'm trying to set up a log server. But the logs may not be shared in the internet.08:24
eantyshevtangchen: that's what I mean, you will need public server to export logs08:25
tangchenanteaya: OK. I understood. :)08:26
anteayaeantyshev: thanks for bringing that point up08:27
anteayatangchen: the point of the logs is for them to be shared on the internet08:27
anteayatangchen: if you don't share them, you can't comment on patches08:27
*** vishwanathj has quit IRC08:27
tangcheneantyshev: Yes. If the servers are public, it is OK. But now, what I'm trying to patch is: add an interface for users to set a proxy for zuul.08:27
*** Daisy has quit IRC08:28
*** PrashantS has joined #openstack-meeting08:28
*** vishwanathj has joined #openstack-meeting08:28
*** Daisy has joined #openstack-meeting08:29
clarkbyou can already do tgat...08:29
clarkbrequests honors http_proxy and for ssh point zuul at a port forward or corkscrew or run with tsocks etc08:30
*** Berezin has quit IRC08:30
tangchenI tried something similar before. It was proxychain.08:31
tangchenBut it doesn't work.08:31
*** achanda has quit IRC08:32
anteayaclarkb: hi, thank you08:32
tangchenI'm not sure if it was because zuul is running background.08:32
*** alexpilotti has joined #openstack-meeting08:33
*** Daisy has quit IRC08:33
*** zhhuabj_ has joined #openstack-meeting08:34
*** egallen has joined #openstack-meeting08:34
tangchenOK, I think it would be better to post a patch first, and then ask for review. :)08:34
tangchenThank you very much. :)08:34
clarkbI dont think you need to patch anythibg is my point08:34
clarkbproxyibg is already doable in a variety of ways08:35
*** MarkAtwood has joined #openstack-meeting08:35
*** ub has quit IRC08:36
tangchenBut what if I want to construct the CI system automatically ?  If I use the community version tools, and it does not support proxy, I have to maintain a tool for myself, right ?08:37
clarkbwell you dont need to maintain the tool just use it08:38
clarkband that way you can choose an appropriate proxy for your local situation.08:38
*** Berezin has joined #openstack-meeting08:38
*** vishwanathj has quit IRC08:39
*** Berezin has quit IRC08:39
*** Berezin has joined #openstack-meeting08:39
*** ub has joined #openstack-meeting08:39
*** MarkAtwood has quit IRC08:39
*** ajmiller has quit IRC08:40
*** yassine__ has joined #openstack-meeting08:40
*** ajmiller has joined #openstack-meeting08:40
anteayatangchen: does that help?08:40
kaisers:q08:40
kaiserssry08:41
anteayatangchen: clarkb reviews zuul patches, so knows far more about zuul than I08:41
anteayakaisers: no problem08:41
anteayadid anyone else have anything they wanted to discuss today?08:41
tangchenWell, I mean the community may offer a tool to construct the CI system automatically. Just like os-ext-test. And it starts zuul without any tool, like corkscrew...08:41
tangchenSo I have to do it myself.08:42
eantyshevOur CI occasionally reports merge failures: http://paste.openstack.org/show/406023/08:42
tangchenIf I can configure it in zuul, then it will be much easy to do.08:42
lennyb_eantyshev: we had a discussion about it yesterday08:42
lennyb_eantyshev: I will prepare a patch for third_party.html08:43
eantyshevlennyb_: do you mean yesterday 3rd party meeting?08:44
lennyb_eantyshev: http://paste.openstack.org/show/40593008:44
anteayaeantyshev: basically akerr offered a configuration that emailed the operator on a merge failure08:44
anteayaeantyshev: it didn't post to gerrit08:44
anteayatangchen: O08:45
anteayaI'm not sure how much more help I can be to you, tangchen08:45
*** zeih has joined #openstack-meeting08:45
anteayaI do believe that clarkb is saying you can already do what you need to do08:45
lennyb_eantyshev: you can update akerr's sample to your needs, I am just evaluation this in our setup08:45
tangchenanteaya: That's all right. :)08:45
tangchenvery helpful. Thanks.08:46
eantyshevanteaya, lennyb_: I do it already, our CI won't report merge failures, but it skips some changes08:46
anteayatangchen: okay good, you are welcome to come back and share what you learned if you wish, it might help other operators08:46
tangchenOK :)08:47
lennyb_eantyshev: you said you have a merge commenting issue08:47
anteayaeantyshev: can you expand on what you would like help with?08:48
eantyshevlennyb_: my problem seems that our CI fails to merge something that looks like is able to be merged08:48
anteayahave you tried manually merging the same tip, patch combination?08:49
anteayalooks like and does can be very different08:49
eantyshevanteaya: I disabled commenting merge failures, if it is what you mean08:49
eantyshevanteaya: no, didn't do that manually :(08:50
anteayawell it might not actually be able to merge08:50
anteayain which case it is working as expected08:50
*** achanda has joined #openstack-meeting08:51
anteayaanything more here?08:51
kaisersI have a q: does anybody here have exp with a manila devstack / tempest setup?08:51
anteayaI do not08:51
anteayaanyone else have experience with a manila setup?08:51
*** PrashantS has quit IRC08:52
kaisersok, then i'll carry this to the manila channel afterwards.. :)08:52
anteayakaisers: is there a reason why you ask?08:52
kaisersyep got issues with the network setup08:52
anteayahave a paste?08:52
kaisersI'm getting network errors and wondered if i missed something in the setup. Ex:  ShareNetworkNotFound: Share network wrong_id could not be found08:52
*** PrashantS has joined #openstack-meeting08:52
kaisersNot sure where 'wrong_id' is coming from. :)08:52
anteayahave you grepped the relevant repos?08:53
lennyb_eantyshev: is it something specific? maybe you need to clean your git cache.08:53
*** vishwanathj has joined #openstack-meeting08:53
kaisersanteaya: not so far, will do that, thnx08:53
eantysheveven providing our CI is triggered by "Build succeeded" comments from Openstack Jenkins, we have probability that something will be merged in between08:53
anteayakaisers: it is coming from manila: http://hound.openstack.org/?q=wrong_id&i=nope&files=&repos=08:53
anteayaeantyshev: I didn't fully understand your last sentence08:54
kaisersanteaya: ok, i'll dig into that08:54
eantyshevanteaya: lennyb_: I will follow your suggestions, thank you! Just hoped somebody faced the same problem08:54
anteayaeantyshev: ah okay thanks08:54
anteayakaisers: thanks08:54
anteayaanything more anyone wants to discuss?08:55
anteayaany reason why I should not end the meeting?08:55
lennyb_eantyshev: we had a problem, when git was constantly failing with merge failure, looked like we killed zuul in the 'bad timing'. So we had to remove all git repos that zuul caches in the server08:56
*** coolsvap|away is now known as coolsvap08:56
lennyb_anteaya: nothing more to discuss from me08:56
anteayathanks lennyb_08:56
eantyshevlennyb_: ok, seen the same, but not this time08:56
*** PrashantS has quit IRC08:57
anteayaanything more?08:57
*** doude_ has joined #openstack-meeting08:57
*** doude_ has quit IRC08:57
lennyb_eantyshev: btw, there was some script to 'clean' git repo and removed all unused staff...maybe this will help08:57
anteayalennyb_: do you have a link to the script?08:58
anteayaor is it a git command?08:58
*** xingchao has quit IRC08:59
lennyb_anteaya: it was a tool I think, it was discussed here a month ago08:59
* lennyb_ trying to look for a tool08:59
anteayathanks08:59
* anteaya waits08:59
*** doude has quit IRC08:59
*** achanda has quit IRC09:00
lennyb_anteaya: I will try to find it offline and send to you.eantishev09:00
*** mdavidson has joined #openstack-meeting09:01
eantyshevlennyb_: Thank you!09:01
anteayalennyb_: and perhaps link in a future meeting09:01
*** matrohon has joined #openstack-meeting09:01
eantyshevI'll wait in #openstack-infra09:01
anteayathanks all for your kind attendance and participation today09:01
anteayasee you next week09:01
kaisersthnx & bye09:01
anteaya#endmeeting09:02
*** openstack changes topic to "BP (Meeting topic: tricircle)"09:02
openstackMeeting ended Tue Jul 28 09:02:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-07-28-08.07.html09:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-07-28-08.07.txt09:02
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-07-28-08.07.log.html09:02
*** jwcroppe has quit IRC09:02
*** ub has quit IRC09:06
*** ub has joined #openstack-meeting09:07
*** zeih has quit IRC09:07
*** markvoelker has joined #openstack-meeting09:07
*** zhhuabj_ has quit IRC09:07
*** larainema has quit IRC09:09
*** yamamoto has quit IRC09:09
*** larainema has joined #openstack-meeting09:09
*** vishwanathj has quit IRC09:10
*** boris-42 has quit IRC09:10
*** markvoelker has quit IRC09:11
*** vishwanathj has joined #openstack-meeting09:12
*** ndipanov has joined #openstack-meeting09:12
*** eantyshev has left #openstack-meeting09:14
*** PrashantS has joined #openstack-meeting09:14
*** jwcroppe has joined #openstack-meeting09:16
*** xingchao has joined #openstack-meeting09:16
*** jwcroppe has quit IRC09:16
*** achanda has joined #openstack-meeting09:17
*** otter768 has joined #openstack-meeting09:17
*** zhhuabj_ has joined #openstack-meeting09:21
*** yamamoto has joined #openstack-meeting09:21
*** atuvenie has quit IRC09:21
*** otter768 has quit IRC09:21
*** PrashantS has quit IRC09:21
*** _nadya_ has joined #openstack-meeting09:23
*** zeih has joined #openstack-meeting09:26
*** jasondotstar|afk has joined #openstack-meeting09:29
*** achanda has quit IRC09:33
*** Berezin has quit IRC09:34
*** yingjun has quit IRC09:34
*** sridhar_ram has joined #openstack-meeting09:34
*** zeih has quit IRC09:34
*** atuvenie has joined #openstack-meeting09:35
*** PrashantS has joined #openstack-meeting09:37
*** GB21 has joined #openstack-meeting09:38
*** GB21_ has joined #openstack-meeting09:38
*** jwcroppe has joined #openstack-meeting09:38
*** redixin has quit IRC09:41
*** GB21_ has quit IRC09:41
*** jwcroppe has quit IRC09:42
*** Daisy has joined #openstack-meeting09:45
*** Daisy has joined #openstack-meeting09:45
*** tochi has quit IRC09:46
*** tochi has joined #openstack-meeting09:46
*** doude has joined #openstack-meeting09:49
*** Daisy has quit IRC09:50
*** PrashantS has quit IRC09:53
*** atuvenie has quit IRC09:53
*** jasondotstar|afk has quit IRC09:54
*** Zhongjun has joined #openstack-meeting09:57
*** yamamoto has quit IRC09:58
*** DaveJ__ has joined #openstack-meeting10:03
*** lexholden has joined #openstack-meeting10:03
*** jwcroppe has joined #openstack-meeting10:04
*** okrieg has joined #openstack-meeting10:09
*** toscalix has joined #openstack-meeting10:11
*** _nadya_ has quit IRC10:12
*** jasondotstar|afk has joined #openstack-meeting10:12
*** _nadya_ has joined #openstack-meeting10:13
*** okrieg has quit IRC10:14
*** zeih has joined #openstack-meeting10:17
*** epico has quit IRC10:19
*** jwcroppe has quit IRC10:19
*** okrieg has joined #openstack-meeting10:23
*** zeih has quit IRC10:27
*** dims has joined #openstack-meeting10:31
*** salv-orl_ has joined #openstack-meeting10:34
*** okrieg has quit IRC10:36
*** salv-orlando has quit IRC10:37
*** rossella_s has quit IRC10:37
*** rossella_s has joined #openstack-meeting10:38
*** xingchao has quit IRC10:38
*** okrieg has joined #openstack-meeting10:38
*** yamamoto has joined #openstack-meeting10:39
*** yamamoto_ has joined #openstack-meeting10:40
*** okrieg has quit IRC10:40
*** bradjones has quit IRC10:41
*** claudiub has joined #openstack-meeting10:42
*** yamamoto has quit IRC10:44
*** Jeffrey4l has quit IRC10:45
*** doude has quit IRC10:46
*** salv-orl_ has quit IRC10:47
*** yamamoto_ has quit IRC10:48
*** glauco has joined #openstack-meeting10:48
*** numan has quit IRC10:51
*** glauco has quit IRC10:52
*** scheuran has quit IRC10:55
*** mpaolino has quit IRC10:59
*** mpaolino has joined #openstack-meeting11:00
*** salv-orlando has joined #openstack-meeting11:00
*** salv-orl_ has joined #openstack-meeting11:01
*** MarkAtwood has joined #openstack-meeting11:03
*** mpaolino has quit IRC11:03
*** salv-orlando has quit IRC11:05
*** MarkAtwood has quit IRC11:07
*** markvoelker has joined #openstack-meeting11:08
*** AzherKhan has quit IRC11:08
*** ganeshna has quit IRC11:13
*** markvoelker has quit IRC11:13
*** otter768 has joined #openstack-meeting11:18
*** sridhar_ram has quit IRC11:19
*** marcusvrn has joined #openstack-meeting11:21
*** otter768 has quit IRC11:22
*** _nadya_ has quit IRC11:23
*** _nadya_ has joined #openstack-meeting11:24
*** rbak has joined #openstack-meeting11:25
*** amakarov_away is now known as amakarov11:25
*** Guest38367 has quit IRC11:27
*** _nadya_ has quit IRC11:29
*** rbak has quit IRC11:29
*** zeih has joined #openstack-meeting11:31
*** Murali_ has joined #openstack-meeting11:31
*** zeih has quit IRC11:32
*** Murali has quit IRC11:32
*** Murali_ is now known as Murali11:32
*** numan has joined #openstack-meeting11:36
*** coolsvap is now known as coolsvap|away11:37
*** Murali has quit IRC11:38
*** banix has joined #openstack-meeting11:40
*** mwagner_lap has quit IRC11:44
*** dguitarbite has quit IRC11:45
*** Brian has joined #openstack-meeting11:45
*** Brian is now known as Guest3058611:46
*** banix has quit IRC11:46
*** jasondotstar|afk has quit IRC11:46
*** VW_ has joined #openstack-meeting11:47
*** okrieg has joined #openstack-meeting11:50
*** Daisy has joined #openstack-meeting11:51
*** jwcroppe has joined #openstack-meeting11:51
*** yamamoto has joined #openstack-meeting11:52
*** tochi has quit IRC11:53
*** PrashantS has joined #openstack-meeting11:53
*** ^Gal^ has quit IRC11:54
*** ^Gal^ has joined #openstack-meeting11:54
*** nmagnezi has quit IRC11:54
*** nmagnezi has joined #openstack-meeting11:55
*** Daisy has quit IRC11:56
*** ricolin has quit IRC11:56
*** Murali has joined #openstack-meeting11:56
*** BobBall_AWOL is now known as BobBall11:56
*** glauco has joined #openstack-meeting11:58
*** PrashantS has quit IRC11:58
*** zeih has joined #openstack-meeting11:58
*** tiantian has quit IRC11:59
*** weshay has joined #openstack-meeting11:59
*** glauco has quit IRC11:59
*** zeih has quit IRC12:08
*** rbak has joined #openstack-meeting12:08
*** markvoelker has joined #openstack-meeting12:09
*** topol has joined #openstack-meeting12:11
*** Zhongjun has quit IRC12:12
*** raildo has joined #openstack-meeting12:13
*** markvoelker has quit IRC12:14
*** _nadya_ has joined #openstack-meeting12:14
*** baoli has joined #openstack-meeting12:18
*** pm90_ has joined #openstack-meeting12:19
*** jwcroppe has quit IRC12:19
*** yamamoto has quit IRC12:19
*** doude has joined #openstack-meeting12:19
*** MaxPC has joined #openstack-meeting12:20
*** jwcroppe has joined #openstack-meeting12:20
*** kylek3h has joined #openstack-meeting12:22
*** baoli has quit IRC12:23
*** jruano has joined #openstack-meeting12:23
*** baoli has joined #openstack-meeting12:24
*** kylek3h has quit IRC12:26
*** zeih has joined #openstack-meeting12:26
*** mestery has joined #openstack-meeting12:27
*** aysyd has joined #openstack-meeting12:27
*** scheuran has joined #openstack-meeting12:27
*** eharney has joined #openstack-meeting12:28
*** markvoelker has joined #openstack-meeting12:29
*** mwagner_lap has joined #openstack-meeting12:29
*** bknudson has joined #openstack-meeting12:30
*** dmacpher has joined #openstack-meeting12:31
*** zeih has quit IRC12:31
*** stevemar has joined #openstack-meeting12:31
*** pm90_ has quit IRC12:31
*** slong_ has joined #openstack-meeting12:34
*** ianw has quit IRC12:34
*** slong__ has joined #openstack-meeting12:34
*** ianw has joined #openstack-meeting12:35
*** bswartz has quit IRC12:35
*** MeganR has joined #openstack-meeting12:35
*** slong has quit IRC12:36
*** hashar has quit IRC12:36
*** jmckind has joined #openstack-meeting12:36
*** rfolco has joined #openstack-meeting12:37
*** jasondotstar|afk has joined #openstack-meeting12:37
*** stevemar has quit IRC12:38
*** slong_ has quit IRC12:38
*** dkranz has joined #openstack-meeting12:38
*** jschwarz has joined #openstack-meeting12:38
*** haiwei has joined #openstack-meeting12:39
*** Yanyan has joined #openstack-meeting12:40
*** VW_ has quit IRC12:41
*** bobh has joined #openstack-meeting12:41
*** VW_ has joined #openstack-meeting12:41
*** BharatK has quit IRC12:42
*** radez is now known as radez_g0n312:42
*** lpeer_ has quit IRC12:43
*** martines has quit IRC12:43
*** funzo has joined #openstack-meeting12:43
*** stevemar has joined #openstack-meeting12:45
*** coolsvap|away is now known as coolsvap12:45
*** zhhuabj_ has quit IRC12:46
*** lkarm has joined #openstack-meeting12:46
*** VW_ has quit IRC12:46
*** Yanyanhu has joined #openstack-meeting12:46
*** glauco has joined #openstack-meeting12:48
*** Yanyan has quit IRC12:48
*** neelashah has joined #openstack-meeting12:49
*** jasondotstar|afk is now known as jasondotstar12:49
*** Yanyan has joined #openstack-meeting12:50
*** oanufriev has quit IRC12:50
*** changbl has joined #openstack-meeting12:50
*** Yanyanhu has quit IRC12:51
*** ccavanna has quit IRC12:52
*** nfedotov has joined #openstack-meeting12:52
*** hichihara has joined #openstack-meeting12:53
*** mpaolino has joined #openstack-meeting12:53
*** julim has joined #openstack-meeting12:55
*** pm90_ has joined #openstack-meeting12:55
*** xingchao has joined #openstack-meeting12:55
*** changbl has quit IRC12:55
*** BharatK has joined #openstack-meeting12:56
*** pm90__ has joined #openstack-meeting12:56
*** martines has joined #openstack-meeting12:56
*** merooney has joined #openstack-meeting12:57
*** Qiming has joined #openstack-meeting12:58
*** bknudson has quit IRC12:59
*** lixinhui has joined #openstack-meeting13:00
*** bobh has quit IRC13:00
*** pm90_ has quit IRC13:00
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Jul 28 13:00:38 2015 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
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qiminghello13:00
haiweihi13:00
Yanyanhi13:00
lixinhuihello13:01
jruanohi13:01
Qiming#topic add agenda items13:01
*** openstack changes topic to "add agenda items (Meeting topic: senlin)"13:01
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:01
Qimingplease add topics if you have things for discussion13:02
*** lexholden has quit IRC13:02
*** afazekas has quit IRC13:02
Qiminglet's get started13:03
*** zhhuabj_ has joined #openstack-meeting13:03
Qiming#topic liberty-2 milestone targets13:03
*** openstack changes topic to "liberty-2 milestone targets (Meeting topic: senlin)"13:03
Qimingplease review the work items and see if there are things missing13:03
Qiming#link https://etherpad.openstack.org/p/senlin-liberty-workitems13:03
*** regXboi has joined #openstack-meeting13:03
QimingI have just removed those items we have finished13:04
*** zeih has joined #openstack-meeting13:04
*** hashar has joined #openstack-meeting13:04
*** oanufriev has joined #openstack-meeting13:04
jruanoI have a couple I am still working on. will have them in for review today13:04
Qimingsounds great, jruano13:05
YanyanI think we have all there13:05
*** amitgandhinz has joined #openstack-meeting13:05
Yanyanalthough some of them could be deferred to liberty-313:05
haiweiI newly assigned to heat_v1 driver, but not started yet13:06
Qimingokay, we may have to13:06
Qimingmaybe it's time to work out a plan for liberty-313:06
*** zeih_ has joined #openstack-meeting13:06
*** MeganR has left #openstack-meeting13:06
jruanowere we going to try and have a release or wait for lib 3?13:06
Yanyanyep13:07
Qimingjruano, we may need to wait for liberty 313:07
Qimingthere are quite some known defects to be ironed out13:07
jruanothat makes sense. stable is best :)13:08
Yanyanyes13:08
Qimingbesides that, we have some high priority todos here: http://git.openstack.org/cgit/stackforge/senlin/tree/TODO.rst13:08
*** amotoki has joined #openstack-meeting13:08
Qimingsome of the issues have been solved13:09
Qimingneed an update on that to find out what are left13:09
*** PrashantS has joined #openstack-meeting13:10
jruanoah yes, looking it over now13:10
*** zeih has quit IRC13:10
Qimingbasically, for lib-3, we will need to have the engine/action/event modules stable13:10
Qimingthe nova server and heat stack profile completely debugged13:10
YanyanQiming, I think maybe we should also implement a basic placement policy which provides cross-region node creation13:11
Qimingyes, please add that to the TODO.rst file13:11
Yanyanmaybe also cross-az/cloud13:11
Yanyanok13:11
*** jmckind has quit IRC13:11
Qimingalso we will need some funtional tests13:11
*** xyang1 has joined #openstack-meeting13:12
Qimingwe will aslo need to promote some middle-priority ones to high-priority13:12
Yanyanyes, and I think the work item of workflow cleasing should be replaced by adding functional test13:12
Yanyanok13:13
Qimingsounds reasonable13:13
*** nelsnelson has joined #openstack-meeting13:13
QimingI'm reading the FEATURES.rst file: http://git.openstack.org/cgit/stackforge/senlin/tree/FEATURES.rst13:13
*** nelsnelson has quit IRC13:13
*** nelsnelson has joined #openstack-meeting13:14
jruanoa lot of work :)13:14
*** VW_ has joined #openstack-meeting13:14
Qimingmost of the items in FEATURES.rst are nice-to-have kind of features13:14
Qimingeach of them would need some time for design, some more time for implement and testing13:15
*** prad has joined #openstack-meeting13:15
Qimingyip, jruano13:15
Qimingit would be a long journey to make things realy useful13:15
Qiming:)13:15
*** bswartz has joined #openstack-meeting13:15
*** hrou has joined #openstack-meeting13:15
jruanomaybe if we can just identify any that need to be a part of lib 3, that would be helpful13:15
Qimingagreed13:15
lixinhuiI think the functional test and placement policy is the most important13:16
lixinhuimay help some if time permits13:16
*** xyang has joined #openstack-meeting13:17
*** etoews has joined #openstack-meeting13:17
Qimingexception handling13:17
haiweiin the Tokyo summit, will be a demo in our presentation?13:17
Yanyanright13:17
Qiminglet's get it done right, once for all13:17
*** lpeer_ has joined #openstack-meeting13:17
YanyanI think we may want to complete the basic framework of exception handling13:17
*** lexholden has joined #openstack-meeting13:17
*** xyang1 has quit IRC13:17
Qiminghaiwei, jruano and some university students are working on that13:18
Yanyancool13:18
Qiminghopefully we can give a live demo of something really useful13:18
Yanyanthat will be very nice :)13:18
haiweiyes13:18
*** otter768 has joined #openstack-meeting13:19
*** glauco has quit IRC13:19
Qiminglet's spend some time prioritizing the TODO items for liberty-313:19
Qiming#action Qiming to create a etherpad for everyone to prioritize L3 items13:20
*** yamamoto has joined #openstack-meeting13:20
*** okrieg has quit IRC13:20
Qiminglet's move on13:20
Qiming#topic update on complex (scaling) policy and triggers13:20
*** openstack changes topic to "update on complex (scaling) policy and triggers (Meeting topic: senlin)"13:20
*** bknudson has joined #openstack-meeting13:20
Qimingwell, I didn't expect it to be such a painful process13:20
*** okrieg has joined #openstack-meeting13:21
QimingI have spent almost 2 weeks on this13:21
*** Zhongjun has joined #openstack-meeting13:21
*** annp has joined #openstack-meeting13:21
Qimingthe original idea was to compile all information into a single scaling policy13:21
Yanyan:) more complicated than we imagined before13:21
Qimingin that policy, you will specify the properties for the triggers (alarm, queue notification), schedule (when to enable/disable) and handlers (different actions)13:22
Qimingwhen writing the spec, I found it too (unnecessarily) complicated to squeeze everything into a single YAML13:23
*** otter768 has quit IRC13:23
*** nelsnelson has quit IRC13:23
*** hashar_ has joined #openstack-meeting13:24
Qimingthe second issue is that it makes the policy inflexible: any single property change necessitates a new policy spec13:24
*** yamamoto has quit IRC13:24
*** nelsnelson has joined #openstack-meeting13:24
Qimingthe third issue is that it is does not conform to our original design of "policy", which was meant to be some rules that will be checked when actions are about to take place13:25
Qimingafter some brainstorming with Yanyan, I have now switched to a different approach13:25
Qimingwe abstract external signals using a concept "Trigger"13:26
Qimingwe create/update/delete it as a separate resource in Senlin13:26
Qimingwe link Triggers to webhooks or other "endpoints" to build an auto-scaling solution13:27
Qimingwe can also link Triggers to webhooks or other receiving points to build HA solution13:27
*** hashar has quit IRC13:28
Qimingso ... basically, we are again developing some primitives, leaving more complicated use cases to users13:28
*** dguitarbite has joined #openstack-meeting13:28
QimingI'd like to hear your comments on this13:28
*** xyang1 has joined #openstack-meeting13:28
*** dguitarbite is now known as Guest1185913:28
jruanosounds almost like you are building a workflow using triggers?13:29
Qimingusers will build them or we can help build such kind of a workflow13:29
Qimingsome sample triggers are here for review/comments: https://review.openstack.org/#/c/206526/13:29
*** dane_leblanc has joined #openstack-meeting13:30
QimingA patch for modeling various ceilometer alarm types is here: https://review.openstack.org/#/c/206527/13:30
*** singlethink has joined #openstack-meeting13:31
*** hashar has joined #openstack-meeting13:31
Qimingtake ceilometer alarms as an example, there are too many variants to be incorporated into a single policy13:31
Qimingthese alarms can be used for whatever use cases13:32
*** dboik has joined #openstack-meeting13:32
*** hoangcx has joined #openstack-meeting13:32
*** yushiro has joined #openstack-meeting13:33
Qimingcomments?13:34
Qimingquestions?13:34
Qimingor you would like to review the patchs, ;)13:34
Yanyanso we hope to keep the flexibility by just providing primitives13:34
*** hashar_ has quit IRC13:34
lixinhuiI will try this in next few days for demo purpose13:34
Yanyanof course this will also reduce the complication13:34
Qiminglixinhui, it is not working yet13:34
lixinhui...13:35
Qimingit is just a design by code13:35
*** ccavanna has joined #openstack-meeting13:35
jruanoi think its a good approach. let the user design the workflow using these base alarms13:35
Yanyanwill give feedback about the patch ASAP13:35
Qimingjruano, if needed, we can provide some sample "workflows" to get autoscaling up13:36
jruanoyep, some "templates"13:36
Qimingright13:36
Qiming#topic clusters of containers13:37
*** openstack changes topic to "clusters of containers (Meeting topic: senlin)"13:37
Qimingjruano, how are things going on there?13:37
jruanoi spent some time working on this. i have coreos running within openstack13:37
jruanopretty straightforward13:37
jruanodocker is natively supported within coreos, so that should be relatively easy13:38
Qimingwith VM clusters created?13:38
jruanokubernetes is more challenging under coreos13:38
Qimingyep13:38
jruanonot yet... i am still debugging a little within magnum13:38
Qimingcool, pls keep the team posted13:39
*** zehicle_IRL has quit IRC13:39
jruanorunning into some issues creating docker bays within magnum, so this is what i am working on now13:39
QimingI traveled to Shanghai last weekend to meet some students from Tongji University13:39
Qimingwe have a SUR project with them13:39
jruanoi will have more information on this shortly13:39
Qimingthey are working on this container cluster topic as well13:40
Qimingthey are moving pretty slow13:40
Qimingjust get themselves familiarized with Magnum and Senlin13:40
Qimingjruano, if you have some ideas for experimentation, they are your interns13:41
Qiming:)13:41
jruanolol, np13:41
jruanoi will write up some notes to share13:41
Qimingthat would be cool13:42
Qimingsome of the students are already trying to modify Magnum to call Senlin APIs13:42
Qiminghope we can get some POCs soon13:43
jruanoah ok... that is a little putting the cart before the horse, but thats fine13:43
Qiminganyway, they will need to understand Senlin APIs first13:44
Qiming#topic open discussions13:45
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:45
*** zeih_ has quit IRC13:45
*** rkukura has joined #openstack-meeting13:45
lixinhuiI wanna check if cluster-polict-list problems fixed or not13:45
Qiminglixinhui, it is fixed13:45
lixinhuiplease point me to the patch, thanks13:46
Qimingit is an issue related to environment configuration13:46
Qimingseems we should change this line to "project:%(project)s": http://git.openstack.org/cgit/stackforge/senlin/tree/etc/senlin/policy.json#n313:47
Qimingwe don't have project_id in the context structure13:47
Qimingneed to dig more on the impact on other code13:48
Yanyanyes13:48
Yanyanotherwise, that rule will not take effect13:48
*** nelsnelson has quit IRC13:48
*** banix has joined #openstack-meeting13:48
Qimingright, you can do almost nothing if the project doesn't match13:49
Yanyanyes13:49
Qimingany outstanding issues met?13:49
*** GB21 is now known as GB21-away13:50
*** stevemar has quit IRC13:50
*** thangp has joined #openstack-meeting13:50
Qimingjruano, we may need to work out a draft design for container clusters13:50
jruanoi think so13:50
Qiminga design that will be applicable to both docker and k8s13:51
jruanolet me compile some notes as a starting point13:51
*** belmoreira has quit IRC13:51
Qimingit is perfectly okay if we only have docker clusters implemented by l313:51
Yanyancool, I think that will help all of us to understand it more clearly13:51
*** PrashantS has quit IRC13:52
*** yapeng has joined #openstack-meeting13:52
Qiminganything else?13:52
jruanoyes... the metadata for k8s is significant13:52
*** PrashantS has joined #openstack-meeting13:52
Yanyannope from me13:52
haiweinothing for me13:53
*** glauco has joined #openstack-meeting13:53
*** zeih has joined #openstack-meeting13:53
Qiminglixinhui, still around?13:53
lixinhuiyes13:53
lixinhuinothing except the policy list13:54
Qimingsince you are more interested into placement policy, could you help take a look at the cross-region implementation in heat?13:54
lixinhuiyes, I am looking at it13:54
Qimingwe need to move that to Senlin -- a concensus from heat team back in Vancouver13:54
Qimingcool13:54
Yanyanand I just proposed a patch to add this work item, you can add you name behind it if it's ok for you :)13:54
*** balajiiyer has joined #openstack-meeting13:54
Qimingshout out if you need help13:55
*** fawadkhaliq has joined #openstack-meeting13:55
lixinhuidefinitly, I will13:55
Qiminglast call13:55
jruanonothing else from me13:55
Qiming413:55
Qiming313:55
Qiming#endmeeting13:56
*** openstack changes topic to "BP (Meeting topic: tricircle)"13:56
openstackMeeting ended Tue Jul 28 13:56:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-07-28-13.00.html13:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-07-28-13.00.txt13:56
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-07-28-13.00.log.html13:56
*** miyagishi_t has joined #openstack-meeting13:56
*** lkarm has left #openstack-meeting13:56
*** PrashantS has quit IRC13:56
*** cbouch has joined #openstack-meeting13:56
*** sigmavirus24_awa has joined #openstack-meeting13:57
*** stevemar has joined #openstack-meeting13:57
*** sigmavirus24_awa is now known as sigmavirus2413:57
*** Gerald_K has joined #openstack-meeting13:57
*** glauco has quit IRC13:57
*** bobh has joined #openstack-meeting13:58
*** ajayaa has quit IRC13:58
*** john-davidge has joined #openstack-meeting13:58
mesteryhi13:59
*** ihrachyshka has joined #openstack-meeting13:59
annphi13:59
rkukurahi13:59
jschwarzhi13:59
hoangcxHi all13:59
yushiro Hi!13:59
regXboimoo13:59
*** johnsom has joined #openstack-meeting13:59
amotokihi14:00
hichiharahi14:00
miyagishi_thi14:00
scheuranhi14:00
*** adreznec has joined #openstack-meeting14:00
*** shihanzhang has joined #openstack-meeting14:00
mesteryOK, lets get started, we have a packed agenda today14:00
mestery#startmeeting networking14:01
openstackMeeting started Tue Jul 28 14:01:01 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
openstackThe meeting name has been set to 'networking'14:01
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:01
mestery#topic Announcements14:01
*** Murali has quit IRC14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** nanguyen has joined #openstack-meeting14:01
mestery#link https://wiki.openstack.org/wiki/Liberty_Release_Schedule Liberty Release Schedule14:01
mestery#info Liberty-2 will be released this week14:01
mesteryUnless there is a bug blocking this, we'll likely cut it later today or tomorrow.14:01
*** yunpengli has joined #openstack-meeting14:02
*** stevemar has quit IRC14:02
mestery#info The DVR Job is now voting14:02
mestery#link https://review.openstack.org/#/c/180230/1514:02
*** mlavalle has joined #openstack-meeting14:02
mesteryHopefully this will help us grind out any additional issues that are lurking in DVR.14:02
*** neiljerram has joined #openstack-meeting14:02
*** bryan_att has joined #openstack-meeting14:02
*** ivasev has joined #openstack-meeting14:02
mesteryThanks to Swami for driving this and to ihrachyshka for his work to remove the job from stable branches14:02
*** martines has quit IRC14:03
mestery#info Voting for the Tokyo Conference is open now14:03
mestery#link https://www.openstack.org/summit/tokyo-2015/vote-for-speakers14:03
mesteryGo forth and vote14:03
*** martines has joined #openstack-meeting14:03
ihrachyshkaI would be glad if there is no work to remove each new voting job from stable...14:03
mesteryihrachyshka: You and me both14:03
*** yunpengli has quit IRC14:03
*** haiwei has quit IRC14:03
anteayahow do you concieve of that happening?14:03
jroll\o14:04
mesteryWe stabilize something during a cycle and make any new job voting during that cycle.14:04
*** Piet has joined #openstack-meeting14:04
anteayaah I'm all for stablity14:04
ihrachyshkaanteaya, nothing except review attention and maybe heads-up for potentially affected parties.14:04
anteayaokay thanks14:04
*** radez_g0n3 is now known as radez14:04
mestery#info For networking sub-projects (networking-foo), please remember to follow code merge requirements (e.g. 2 +2 votes)14:05
mestery#link http://docs.openstack.org/infra/manual/developers.html#code-review14:05
mesteryIf you're in the Neutron Stadium, you need to be following those guidelines14:06
mesteryIf you have questions, please reach out to me, anteaya, ihrachyshka or anyone else who has been merging code for a while for help14:06
*** zeih has quit IRC14:06
mesteryAny other announcements for the team from anyone else before we move along?14:06
*** zeih has joined #openstack-meeting14:07
*** MarkAtwood has joined #openstack-meeting14:08
mestery#topic Liberty-3 and our giant backlog of things to merge14:08
*** openstack changes topic to "Liberty-3 and our giant backlog of things to merge (Meeting topic: networking)"14:08
mestery#link https://launchpad.net/neutron/+milestone/liberty-314:08
*** amuller has joined #openstack-meeting14:08
mesteryAs is typically the case, we have a lot of things to merge in Liberty-3.14:08
mesteryI would strongly, highly beg of reviewers to focus on things that are on that list14:09
mesteryInstead of just opening gerrit and reviewing what's at the top14:09
mesteryThere are many things in there that need some review love and the earlier we can merge many of these, the better14:09
*** yamahata has joined #openstack-meeting14:09
*** boris-42 has joined #openstack-meeting14:10
* HenryG thought we no longer had deadlines ;)14:10
*** vikram_ has joined #openstack-meeting14:10
* mestery slaps HenryG 14:10
ihrachyshka(I don't see qos there at all)14:10
mestery#action ihrachyshka to add QoS LP BPs to Liberty-3 milestone14:10
mestery:)14:10
ihrachyshkaouch :)14:10
mesterylol14:10
mlavallemestery: what is L3 date?14:10
ihrachyshkaslapping party!14:10
*** mpaolino has quit IRC14:10
neiljerramAny prioritization between bugs and non-bugs?14:11
*** Yanyan has quit IRC14:11
mesterymlavalle: Liberty-3 date is week of August 3114:11
mesteryThat's also FF14:11
mesteryneiljerram: I'd encourage reviewing of critical and high priority bugs in parallel with those specs14:11
*** ozstacker has joined #openstack-meeting14:11
*** VanL has joined #openstack-meeting14:11
mesteryAs you can see, Liberty-3 is going to drop on us very fast. :)14:12
mesteryAny other questions on Liberty-3?14:12
*** johnbelamaric has joined #openstack-meeting14:12
HenryGI wonder if all vendors will get their code out in time?14:12
*** mrmartin has joined #openstack-meeting14:12
* regXboi grabs the popcorn and program14:12
mesteryHenryG: They won't14:12
neiljerramHenryG: what does that refer to?14:13
mesteryHenryG: You, me and armax need to send an email to the ML on that14:13
*** Daisy has joined #openstack-meeting14:13
mestery#action mestery HenryG and armax to email list about the impending purge of drivers from neutron during mitaki14:13
HenryGOK, and should we relax the wording in the contrib devref?14:13
*** pratap has joined #openstack-meeting14:13
mesteryHenryG: If you submit a patch, add me there and I'll reveiw :)14:13
HenryGneiljerram: http://docs.openstack.org/developer/neutron/devref/contribute.html14:14
*** jmckind has joined #openstack-meeting14:14
amotokiI prepared the decomp for my one and the good news is it was easy :-)14:14
mesteryamotoki: Nice! :)14:14
mesteryAny other Liberty-3 questions from folks before we move on?14:14
*** pratap1 has joined #openstack-meeting14:14
*** jecarey_ has joined #openstack-meeting14:15
mestery#topic Where should Macvtap agent land14:15
mesteryscheuran: You're up! :)14:15
*** openstack changes topic to "Where should Macvtap agent land (Meeting topic: networking)"14:15
mestery#link https://review.openstack.org/#/c/195907/14:15
scheuranthanks14:15
mesteryThat's the review in question for folks who are not following along here14:15
scheuranThe plan is to have a ml2 driver & l2 agent for supporting macvtap guest attachments (independent form sriov)14:16
mesteryscheuran: Can you summarize for the team?14:16
scheuranThe big question is, where such code should land14:16
scheuranThe agent reuses a lot of code of the linuxbridge agent - especially the main loop, mechanism for detecting pluged tap (macvtap) devices.14:16
scheuranand so on14:16
mesteryscheuran: So one option is to add the code into the existing LB agent, right?14:16
scheuranright14:16
mesterysc68cal: ^^^14:16
mesterysc68cal: Bringing you in because this is LB related14:16
mesteryscheuran: If you do that, you don't need a repo and you just do it in-tree.14:17
scheuranright14:17
*** banix has quit IRC14:17
* sc68cal looks14:17
neiljerramIn case it helps: this sounds similar to my current situation with the DHCP agent14:17
ihrachyshkaextension drivers for agents? in qos, we have that: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/l2/extensions?h=feature/qos14:17
*** Daisy has quit IRC14:17
scheuranbut that would mean extracting new superclasses and moving methods up and down between themn14:17
ihrachyshkanot sure whether fully applicable14:17
scheuranso a larger restructuring14:17
*** banix has joined #openstack-meeting14:18
*** tongli has joined #openstack-meeting14:18
*** pratap has quit IRC14:18
amullerthe LB agent has no tests, a "large restructuring" scares me14:18
ihrachyshkait's several lines in your base agent (lb) and then you are free to do whatever you want with port updates in your extension.14:18
*** gsagie has joined #openstack-meeting14:18
mesteryihrachyshka: That sounds like the best option forward.14:18
mesteryamuller: Dually noted on the LB testing situation :)14:18
ihrachyshkait obviously depends on whether you replace or extend the agent.14:18
mesteryscheuran: So, it sounds like perhaps you should work offline to understand the approach ihrachyshka is extending to you here.14:19
mesteryBecause that sounds like it may be the best way forward14:19
*** arajagopal has joined #openstack-meeting14:19
scheuranok, I'll talk to ihrachyshka and having a look at his approach14:19
sc68calamuller: that's not true14:19
*** janonymous_ has joined #openstack-meeting14:20
amullersc68cal: oh?14:20
sc68calamuller: https://github.com/openstack/neutron/blob/master/neutron/tests/unit/plugins/ml2/drivers/linuxbridge/agent/test_linuxbridge_neutron_agent.py14:20
mesteryamuller sc68cal: Shall we take the LB test situation to #openstack-neutron post meeting?14:20
*** Tross has quit IRC14:21
*** tsekiyama has joined #openstack-meeting14:21
mesteryI'd hate to bog down the already packed meeting with that here, because I sense it could go south quickly.14:21
*** shihanzhang has quit IRC14:21
*** yingjun has joined #openstack-meeting14:21
mesteryFair?14:21
amullersure14:21
*** harshs has joined #openstack-meeting14:21
mesteryCool :)14:21
mesteryscheuran: So, you have what you need to move forward here?14:21
mesteryscheuran: And if so, you can mark your governance patch as WIP for now and reference the meeting once it's on eavesdrop (or I can do that for you post meeting too)14:21
scheuranyes, I'll talk to ihrachyshka and then I'll come back to you14:22
scheuranok14:22
mesteryGreat! Thanks scheuran and ihrachyshka.14:22
*** yingjun has quit IRC14:22
mesteryNext up on our weekly smorgasboard of an agenda14:22
mestery#topic Ironic Provider Networks14:23
*** openstack changes topic to "Ironic Provider Networks (Meeting topic: networking)"14:23
mesteryI am not sure who added this to the agenda14:23
mesteryDoes anyone want to step forward to claim their topic?14:23
mestery#link https://review.openstack.org/#/c/152703/14:23
*** ganeshna has joined #openstack-meeting14:23
mesteryOh wait, now I recall!14:23
mesteryThis was Josh14:23
mesteryFrom the nova mid-cycle last week14:23
*** Guest11859 has quit IRC14:23
mesteryI don't recall his IRC handle though ....14:23
sc68callet's shelve it and move on - i'll ping the ironic channel14:24
sc68calif they get someone to come in before end of meeting we'll pull it back in14:24
jrollmestery: hi14:24
jrolljim, not josh14:24
mesteryjroll: Sorry about that :)14:24
jrollno worries14:24
jrollso!14:25
mesteryjroll: OK, so lets get everyone up to speed14:25
med_JoshNang ping14:25
jrollat the midcycle, and on the list, we basically decided that neutron's provider network plugin thing should indicate if the vlan should be passed to the host14:25
jrollbut never decided how that should actually work14:25
*** bobh has quit IRC14:26
* med_ should have listened in on that discussion...14:26
*** annegentle has joined #openstack-meeting14:26
*** weshay has quit IRC14:26
*** zehicle_IRL has joined #openstack-meeting14:27
mesteryjroll: I'm still digesting the patch in question a bit, by chance do you also have a link to the ML discussion?14:27
sc68caljroll: that starts to sound like vlan transparent to me - http://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html14:27
jrollso I'm thinking only the ML2 mechanism can really know14:27
jrollmestery: http://lists.openstack.org/pipermail/openstack-dev/2015-July/069783.html14:27
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2015-July/069783.html14:28
*** ganeshna has quit IRC14:28
mesteryThanks jroll14:28
mesterysc68cal: Elaborate further please :)14:28
*** esker has joined #openstack-meeting14:28
jrollsc68cal: yeah, it sounds like it... there are ML2 (or maybe not ml2?) plugins that require this today14:28
jrollhttps://github.com/rackerlabs/ironic-neutron-plugin14:28
jrollso maybe we do want to wait for that, maybe we don't, I'm not entirely sure14:29
mesterysc68cal: I see it now, NM14:29
sc68calmestery: :)14:29
*** jaypipes has joined #openstack-meeting14:29
mesteryjroll: The VLAN transperency was released as a part of Kilo already, so it's there, the issue is what driver/plugin you want supports how you want to use it I guess14:29
neiljerramI'm aware of the ML controversy on this - but no idea as yet about what _this_ meeting is being asked to decide or discuss14:29
*** fawadk has joined #openstack-meeting14:30
*** fawadkhaliq has quit IRC14:30
jrollmestery: oh, I thought this was a liberty thing14:30
*** yapeng has quit IRC14:30
jrollneiljerram: so as someone who uses that nova patch and the above neutron plugin in production today, I would like to upstream this work14:30
mesteryjroll: Nope, it's already in Kilo, made it at the very end14:30
amullerjroll: I wish http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/metadata-service-network-info.html explained the use case better, why an Ironic host needs this information in the first place and what does it want to do with it14:30
jrollneiljerram: and I don't know a ton about neutron and so trying to figure out the best way to do this.14:30
*** pm90__ has quit IRC14:31
jrollamuller: it's not just ironic hosts that might use this, it's really any instance in a dhcp-less context14:31
mesteryjroll: You just want to know the VLAN tag so you can set the guest/host up to use that tag, right?14:31
jrollcorrect.14:31
neiljerramjroll: OK, cool.  The discussion appeared quite contentious to me, so hopefully someone can see a way to bring the sides together...14:32
mesterySo, that's what VLAN transparency was for :)14:32
jrollwelp14:32
jrollmestery: this is the first time I'm seeing this14:32
mesteryI think there mayb e some gaps here14:32
*** VW__ has joined #openstack-meeting14:32
jrollI'll have to look at it, I suppose14:32
mesteryI think what you need is in addition to the indication you can handle passing VLAN traffic you want the actual tag as well14:32
mesteryjroll: Yes, please :)14:33
*** fawadkhaliq has joined #openstack-meeting14:33
jrollmestery: oh, right, the instance needs to know the vlan to tag14:33
*** yamahata has quit IRC14:33
*** fawadk has quit IRC14:33
*** weshay has joined #openstack-meeting14:34
jrollI think it's more like the vlan-aware-vms spec14:34
jrollwhich is why I was thinking liberty.14:34
mesteryjroll: o_O14:34
mesteryYes, I think a bit like that too14:34
mesteryjroll: OK, let me try and see where things are here and work with you on this to see what we can do14:34
amotokijroll: does such insntace want to send multiple networks based on vlan tags?14:34
mesteryThis reminds me I need to try and understand where the vlan-aware-vms work is ....14:34
jrollamotoki: sometimes :)14:34
amullerthere's been no progress on vlan aware VMs AFAIK since the spec was merged (So, no code proposed), it's pretty much guaranteed to miss L I think at this point14:35
amotokijroll: if so, it looks like vlan-aware-vms work as mestery said.14:35
*** VW_ has quit IRC14:35
sc68calsounds like we have at least a way forward though14:35
*** vivek-ebay has joined #openstack-meeting14:35
mestery++14:35
mesteryamuller: I agree, and to be honest, it was questionable even with code already proposed, so it's not looking good.14:36
mestery#action mestery to try and dig out some status on the vlan-aware-vms spec14:36
mesteryjroll: We'll sort this and get back to you soon, sound good?14:36
amullermestery: exactly, even with a full set of patches proposed today it'll probably not make it14:36
jrollmestery: cool, thank you sir14:36
sc68calmestery: loop me in since I suggested it too14:37
mesteryamuller: I like to think of myself as an optimist against a constant backlog of challenges, so lets see. :)14:37
*** VW__ has quit IRC14:37
mesterysc68cal: ++14:37
*** ZZelle has joined #openstack-meeting14:37
*** ZZelle has left #openstack-meeting14:37
*** ZZelle has joined #openstack-meeting14:37
*** rossella_s has quit IRC14:37
mesteryOK, lets move on to the next topic with 23 minutes left14:37
mestery#topic Neutron Mitaki mid-cycle14:37
*** openstack changes topic to "Neutron Mitaki mid-cycle (Meeting topic: networking)"14:37
mesteryThis has come up recently14:37
*** rossella_s has joined #openstack-meeting14:37
mesteryFrom a few folks14:37
mesteryThe reason for discussion this now is that a plan has been floated to have this in Galway, Ireland14:38
*** dthakkar has joined #openstack-meeting14:38
mesteryI wanted input from everyone on a few things:14:38
amotokinot Mtaki but Mitaka (which ends with "a")14:38
mestery1) Is Galway ok?14:38
hichiharaMitaki -> Mitaka? : )14:38
mestery2) Do we even need a mid-cycle still?14:38
mesteryhichihara amotoki: Thank you for your correction :)14:38
*** stevemar has joined #openstack-meeting14:38
ihrachyshkamestery, at least for drinking Irish beer, so yes14:38
mesteryihrachyshka: lol :)14:39
regXboimestery: going forward, I believe need to figure out a way to make mid-cycles more remote friendly14:39
neiljerram1) It's nice and close to me; 2) Don't know as I haven't been to one yet, but would like to.14:39
regXboiihrachyshka: +1 many times14:39
sc68cali like ireland :)14:39
mesteryregXboi: Exactly my point! If we did a virtual sprint, it may make it better for everyone, but less personal for those who attend ... in person.14:39
ihrachyshkathere are better chance I join that one; that said, those gatherings are sometimes painful for outsiders.14:39
john-davidgemestery: What dates are being considered for the mid-cylcle?14:40
mesteryjohn-davidge: We're looking at either early December, or early January14:40
regXboijohn-davidge brings up a great point14:40
mesteryWhich is another point.14:40
xgermanit will be cold in Ireland that time!14:40
mesteryI guess I want the team to really think about whether or not we want to keep doing mid-cycles14:40
mesteryBefore we move forward with planning the next one.14:40
*** vivek-ebay has quit IRC14:40
neiljerramEarly Jan would be better for me14:40
amullerIreland in January, fantastic14:41
mesteryamuller: lol ;)14:41
regXboiamuller: more reason to hold the midcycle in a pub14:41
mesteryIf someone can get us a place in Cuba in January, I'm all for that too.14:41
neiljerramHow many people typically attend?14:41
mesteryneiljerram: 20-3014:41
john-davidgeI’ve personally never attended a mid-cycle as they’ve been too far away (and ireland will be as well), but I can see the value. I feel like the Liberty mid-cycle was a bit soon after the summit though14:42
mesteryWe've made our mid-cycles coding sprints14:42
ihrachyshkafor my taste, we are good to keep everyone on the same level of participation, which suggests online is fine. summits are already quite frequent to get together14:42
mesteryihrachyshka: Exactly my thinking too14:42
ihrachyshka(but I haven't been to any)14:42
neiljerramInteresting, sounds like that's enough to be considered a strategic part of the dev cycle - as opposed to mostly a social thing14:42
mesteryMy otehr suggestion is to try a 3 day virtual-sprint for Mitaka14:42
mesteryAnd see how that goes14:42
mesteryneiljerram: Actually, it's a coding sprint, nothing strategic14:43
mesteryWe've worked hard to make it only a coding sprint14:43
mesterySo attendance not required14:43
regXboimestery: hmm... could we try the virt sprint first and if that doesn't work, fall back to the mid-cycle coding sprint?14:43
mesteryThere is too much travel already14:43
*** glauco has joined #openstack-meeting14:43
neiljerramAh, OK.14:43
mesteryregXboi: We'd lose all the benefits of skipping the mid-cycle as we'd have to plan it, but may be worth thinking about14:43
mlavallemestery: let's ask Fidel14:43
amullera virtual-only coding sprint would be a really interesting experiment, like Ihar and Kyle said, travelling twice a year to the summits is already a lot14:43
mesterymlavalle: lol :)14:43
mesteryamuller: ++14:43
*** nmagnezi has quit IRC14:43
neiljerramIn that case, sounds like it would be very interesting to see if can get the same group dynamic virtually14:43
regXboiamuller: ++14:43
mesteryI think getting the team used to collaborating more on IRC and online woudl be a good move personally14:44
mesteryOK14:44
regXboimestery: are you thinking a 3 day coding sprint or a 72 hour coding sprint?14:44
mesteryI'll email the ML to get broader participation from folks not at this meeting14:44
regXboii.e. run the coding sprint round the globe14:44
mesteryregXboi: 72 hours :P14:44
*** vivek-ebay has joined #openstack-meeting14:44
mestery#action mestery to solicit input from everyone on the Neutron mid-cycle coding sprint from the ML14:44
regXboimestery: got it14:45
mesteryAnything else on the mid-cycle from anyone?14:45
*** jmckind has quit IRC14:45
HenryGWe could also have per-feature sprints?14:45
*** Gerald_K has quit IRC14:45
mesteryHenryG: If they're virtual, yes. In person, no way :)14:45
ihrachyshkahemna, we did have for qos, it was a nice one14:45
*** ajayaa has joined #openstack-meeting14:45
HenryGyep, virtual is what I meant.14:45
mesteryihrachyshka: QoS was special14:46
mesteryI'd like to keep feature specific things virtual14:46
mesteryOr this will get out of hand really quickly14:46
*** stevemar has quit IRC14:46
regXboiit isn't aleady?14:46
mesteryOK, I have 2 more items to cover (including neiljerram's work), so lets move on.14:46
mestery#topic Concrete plan to merge back pecan and QoS work14:46
*** openstack changes topic to "Concrete plan to merge back pecan and QoS work (Meeting topic: networking)"14:46
mesteryI'm time-boxing this for 4 minutes14:46
mestery:)14:46
sc68calqos was in person though, remote was tough tz14:46
mesteryihrachyshka blogan kevinbenton: We need a plan to bring these back14:46
mesteryAnd as soon as possible.14:47
mesteryI think QoS is more ready than pecan at this point14:47
mesterySo I propose we bring back QoS first, followed by pecan.14:47
mesteryThoughts?14:47
ihrachyshkamestery, well, we collecting pieces, but we are not exactly there yet.14:47
ihrachyshkaas for order, yay for that14:47
mesterycool14:47
*** jmckind has joined #openstack-meeting14:47
ihrachyshkawe work hard to get there sometime next week though14:47
mestery#info QoS to merge back to master first, followed by pecan14:47
ihrachyshkahow bad is pecan?14:48
mesteryihrachyshka: Lets keep this on the agenda for Monday next week14:48
mesteryihrachyshka: It just needs reviews :(14:48
ihrachyshkaold story14:48
ryanpetrellocan somebody point me at the pecan review(s)?14:48
mesteryyes14:48
ryanpetrelloI've held off while tests stabilized14:48
mesteryryanpetrello: https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z14:48
mestery:)14:48
ryanpetrellobut I'd like to take another look14:48
ryanpetrellothanks!14:48
mesteryryanpetrello: Your reviews there would be AWESOME! Thanks!14:48
ryanpetrellok, I'll take a look over this today14:49
mesterythanks!14:49
regXboimestery: I'll put it on my list to look tomorrow am14:49
mesteryOK14:49
mesteryregXboi: Thanks!14:49
mesteryLets move on to the last item14:49
mestery#topic neiljerram's routed network and DHCP changes14:49
*** openstack changes topic to "neiljerram's routed network and DHCP changes (Meeting topic: networking)"14:49
mesteryneiljerram: The floor is yours for 10 minutes ;)14:49
*** erlon has joined #openstack-meeting14:49
neiljerramThanks - https://review.openstack.org/19843914:49
*** GB21-away is now known as GB2114:49
mestery#link https://review.openstack.org/19843914:50
neiljerramOK, so on the one hand there's lots of great discussion about how best to model routed networking14:50
neiljerramThanks to everyone participating there - in review and ML threads.14:50
neiljerramIt's looking, though, that that will take lots more time to think through.14:51
*** Adriano__ has joined #openstack-meeting14:51
neiljerramSomewhat independently, though, there's a set of DHCP agent changes that I've put up for review, and I'll really like to get a general feeling on those.14:51
*** jwcroppe has quit IRC14:52
regXboineiljerram: do these DHCP agents changes stand independently of the spec?14:52
sc68callink?14:52
neiljerramhttps://review.openstack.org/206078, plus its 3 prerequisites14:52
mestery#link https://review.openstack.org/20607814:52
mesteryneiljerram: Same question as regXboi14:52
*** jwcroppe has joined #openstack-meeting14:52
neiljerramTechnically yes - because variation in the DHCP agent is driven by an interface_driver config14:52
*** sudipto has joined #openstack-meeting14:52
neiljerramLong term, I wonder if that's correct - seems that maybe it should be dynamic based on network_type.  But for now we have interface_driver.14:53
*** stevemar has joined #openstack-meeting14:54
mesteryneiljerram: I think you've stumbled into a quagmire here, as this also relates to the work that carl_baldwin is doing, as you know :)14:54
neiljerramTherefore, given a few meaningful customization points in the DHCP agent, I can write a custom interface_driver that uses a certain combination of those to produce the behaviour that I'm looking for.14:54
mesteryAt this point in the cycle, it's looking like this may end up being shelved for Mitaka, but lets see14:54
neiljerrammestery: Oh, absolutely, yes.  But that's all on the modelling side, which I think can be separated from the DHCP agent14:54
mesteryneiljerram: The DHCP changes may end up being ok, but lets see what happens during review14:54
mesteryneiljerram: Exactly, we're on the same page :)14:55
amotokiI think an interface driver should represent how to connect to a network and it should not represent a different behavior....14:55
neiljerramCool, thanks.14:55
neiljerramThe big practical benefit, for my project, if we could get the DHCP changes agreed, would be working with vanilla upstream Neutron...14:55
*** ddieterly has joined #openstack-meeting14:55
*** sdake has joined #openstack-meeting14:55
mesteryneiljerram: Yup, agreed, and I think that helps you out, so lets see if we can figure those out.14:56
mestery:)14:56
neiljerramI have a lot of detail work to do on the DHCP reviews, but it's nice to have a somewhat positive feeling, so thanks.14:56
mesteryI encourage folks to review neiljerram's patches he posted above14:56
mesteryneiljerram: Absolutely :)14:56
mesteryOK14:56
mestery3 minutes or so left14:56
neiljerramI'm done - thanks for attention!14:56
mestery#topic Open Discussion14:56
*** jwcroppe has quit IRC14:56
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:56
*** achanda has joined #openstack-meeting14:56
mesteryJust one final note to encourage reveiws of Liberty-3 specs alongside Critical/High priority bugs14:57
adreznecWe have a neutron ml2 agent for powervm out in stackforge (https://github.com/stackforge/neutron-powervm). At the nova mid-cycle meetup it was brought up that we should look at moving it under openstack/networking-powervm to fit the new third-party drivers decomp model. How should we handle proposing the change? Are there steps beyond the required changes to governance, project-config, and working with the infra team on the14:57
adreznecrename we should be aware of?14:57
*** sudipto has quit IRC14:57
mesteryHenryG: Do you have a link for adreznec off hand?14:57
*** mrmartin has quit IRC14:58
mesteryadreznec: You basically need to propose a project-config change to move it to openstack namespace, and make that dependent on a governance change adding it to the lsit of neutron repos14:58
mesteryAdd me as a reviewer to both of those and I'll ACK them.14:58
mesteryIt's that simple :)14:58
*** ddieterly has quit IRC14:58
*** mdenny has joined #openstack-meeting14:58
adreznecmestery: awesome, I have the patches already written up. Just wanted to make sure I brought it up here first. I'll get those proposed here today14:58
miyagishi_tkevinbenton: I have a question about implementation plan of Distributed SNAT. Could you talk after the meeting?14:59
yushiromestery, thank you for your great ACK and review for my ML2 plugin patch.14:59
mesteryadreznec: Awesome!14:59
john-davidgemestery: Would love to see #link https://review.openstack.org/#/c/158697 merge soon. Recent reviews have been largely positive and/or nit-picking. Getting this patch in will help us concentrate on the agent-side changes during the L-3 timeframe.14:59
mesteryyushiro: yw14:59
mesteryOK, thanks folks!14:59
yushiromestery, I've posted the patch for updating sub_project.rst.  https://review.openstack.org/#/c/206293/ Would you please review it?14:59
mesteryWe'll see you all in #openstack-neutron14:59
mesteryyushiro: Will look, yes.14:59
mestery#endmeeting14:59
*** openstack changes topic to "BP (Meeting topic: tricircle)"14:59
openstackMeeting ended Tue Jul 28 14:59:39 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
*** sudipto has joined #openstack-meeting14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-28-14.01.html14:59
neiljerramBye all!14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-28-14.01.txt14:59
*** mlavalle has left #openstack-meeting14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-28-14.01.log.html14:59
fawadkhaliqbye!14:59
regXboioom15:00
* regXboi wanders to next meeting15:00
yushirobye bye...15:00
*** regXboi has left #openstack-meeting15:00
hoangcxBye15:00
miyagishi_tbye15:00
hichiharabye15:00
annpbye15:00
*** ddieterly has joined #openstack-meeting15:00
*** yushiro has quit IRC15:00
*** rkukura has left #openstack-meeting15:00
*** banix has quit IRC15:01
adreznecexit15:01
*** adreznec has left #openstack-meeting15:01
*** yamamoto has joined #openstack-meeting15:01
*** yamamoto has quit IRC15:01
*** yamamoto has joined #openstack-meeting15:01
*** gsagie has left #openstack-meeting15:01
*** ddieterl_ has joined #openstack-meeting15:02
*** johnsom has left #openstack-meeting15:02
*** johnbelamaric has left #openstack-meeting15:02
*** dthakkar has quit IRC15:04
*** dkranz has quit IRC15:05
*** miyagishi_t has left #openstack-meeting15:05
*** ddieterl_ has quit IRC15:05
*** hoangcx has quit IRC15:05
*** ddieterly has quit IRC15:05
*** john-davidge has left #openstack-meeting15:07
*** pm90_ has joined #openstack-meeting15:08
*** pm90__ has joined #openstack-meeting15:09
*** achanda has quit IRC15:09
*** VW_ has joined #openstack-meeting15:10
*** amakarov is now known as amakarov_away15:11
*** nanguyen has quit IRC15:12
*** glauco has quit IRC15:12
*** okrieg1 has joined #openstack-meeting15:12
*** okrieg has quit IRC15:12
*** ccavanna has quit IRC15:12
*** pm90_ has quit IRC15:13
*** edtubill has joined #openstack-meeting15:15
*** dkranz has joined #openstack-meeting15:17
*** jschwarz has quit IRC15:18
*** mtanino has joined #openstack-meeting15:18
*** otter768 has joined #openstack-meeting15:20
*** vishwanathj has quit IRC15:20
*** ayoung has joined #openstack-meeting15:20
*** mestery has quit IRC15:20
*** dannywilson has joined #openstack-meeting15:22
*** ddieterly has joined #openstack-meeting15:22
*** mpaolino has joined #openstack-meeting15:24
*** otter768 has quit IRC15:24
*** jasondotstar has quit IRC15:25
*** harshs has quit IRC15:26
*** ddieterly has quit IRC15:26
*** alop has joined #openstack-meeting15:27
*** dkranz has quit IRC15:28
*** tongli_ has joined #openstack-meeting15:28
*** VanL has quit IRC15:29
*** jdurgin1 has joined #openstack-meeting15:31
*** padkrish has joined #openstack-meeting15:31
*** padkrish has quit IRC15:31
*** tongli has quit IRC15:31
*** Qiming has quit IRC15:32
*** padkrish has joined #openstack-meeting15:32
*** bobh has joined #openstack-meeting15:32
*** topol has quit IRC15:33
*** mestery has joined #openstack-meeting15:34
*** topol has joined #openstack-meeting15:34
*** topol has quit IRC15:34
*** sdake has quit IRC15:35
*** VanL has joined #openstack-meeting15:36
*** aimon has joined #openstack-meeting15:38
*** Apoorva has joined #openstack-meeting15:39
*** VW_ has quit IRC15:40
*** cdub has joined #openstack-meeting15:40
*** VW_ has joined #openstack-meeting15:40
*** pballand has joined #openstack-meeting15:40
*** bobh has quit IRC15:41
*** ijw has joined #openstack-meeting15:42
*** VW__ has joined #openstack-meeting15:43
*** ccavanna has joined #openstack-meeting15:43
*** VW_ has quit IRC15:43
*** stevemar has quit IRC15:44
*** PrashantS has joined #openstack-meeting15:45
*** devvesa has quit IRC15:46
*** vijendar has joined #openstack-meeting15:46
*** alexpilotti has quit IRC15:47
*** xingchao has quit IRC15:47
*** claudiub has quit IRC15:47
*** elo has quit IRC15:47
*** PrashantS has quit IRC15:49
*** hichihara has quit IRC15:49
*** PrashantS has joined #openstack-meeting15:49
*** dkranz has joined #openstack-meeting15:49
*** jlanoux has quit IRC15:50
*** SridharG has left #openstack-meeting15:50
*** kebray has joined #openstack-meeting15:52
*** scheuran has quit IRC15:52
*** numan has quit IRC15:52
*** changbl has joined #openstack-meeting15:52
*** Prashan__ has joined #openstack-meeting15:53
*** PrashantS has quit IRC15:53
*** dane_leblanc has quit IRC15:53
*** vivek-ebay has quit IRC15:53
*** SumitNaiksatam has quit IRC15:54
*** padkrish has quit IRC15:54
*** whenry has quit IRC15:54
*** BharatK has quit IRC15:55
*** sahid has quit IRC15:55
*** breitz has joined #openstack-meeting15:56
*** BharatK has joined #openstack-meeting15:56
*** unicell has joined #openstack-meeting15:57
*** unicell1 has quit IRC15:58
*** SumitNaiksatam has joined #openstack-meeting15:59
*** ygbo has quit IRC16:00
*** SumitNaiksatam has quit IRC16:00
*** KunalGandhi has joined #openstack-meeting16:02
*** lexholden has quit IRC16:02
*** Guest33644 has quit IRC16:02
*** okrieg1 has quit IRC16:02
*** zeih has quit IRC16:03
*** annp has quit IRC16:03
*** padkrish has joined #openstack-meeting16:03
*** BharatK has quit IRC16:06
*** coolsvap is now known as coolsvap|dinner16:06
*** okrieg has joined #openstack-meeting16:06
*** ihrachyshka has quit IRC16:06
*** penick has joined #openstack-meeting16:06
*** okrieg has quit IRC16:06
*** cdub has quit IRC16:07
*** baoli has quit IRC16:07
*** ^Gal^__ has joined #openstack-meeting16:07
*** okrieg has joined #openstack-meeting16:07
*** safchain has quit IRC16:08
*** Tross has joined #openstack-meeting16:08
*** merooney has quit IRC16:09
*** unicell has quit IRC16:09
*** ^Gal^_ has quit IRC16:10
*** nfedotov has left #openstack-meeting16:11
*** annegentle has quit IRC16:11
*** padkrish has quit IRC16:11
*** Prashan__ has quit IRC16:12
*** ub2 has joined #openstack-meeting16:18
*** janonymous_ has quit IRC16:18
*** ub has quit IRC16:19
*** leeantho has joined #openstack-meeting16:19
*** e0ne has quit IRC16:20
*** sdake has joined #openstack-meeting16:22
*** Zhongjun has quit IRC16:22
*** larainema has quit IRC16:25
*** larainema has joined #openstack-meeting16:26
*** sridhar_ram has joined #openstack-meeting16:26
*** Tross has quit IRC16:26
*** vikram_ has quit IRC16:27
*** Apoorva has quit IRC16:27
*** glauco has joined #openstack-meeting16:28
*** matrohon has quit IRC16:28
*** etoews has quit IRC16:28
*** Daisy has joined #openstack-meeting16:29
*** padkrish has joined #openstack-meeting16:31
*** Alexey_nexenta has joined #openstack-meeting16:32
*** glauco has quit IRC16:32
*** jdurgin1 has quit IRC16:32
*** Daisy has quit IRC16:33
*** jasondotstar has joined #openstack-meeting16:34
*** hodos has joined #openstack-meeting16:38
*** vivek-eb_ has joined #openstack-meeting16:39
*** thangp has quit IRC16:40
*** thangp has joined #openstack-meeting16:41
*** amitgandhinz has quit IRC16:42
*** padkrish has quit IRC16:42
*** unicell has joined #openstack-meeting16:43
*** bryan_att has quit IRC16:43
*** balajiiyer has quit IRC16:44
*** glauco_ has joined #openstack-meeting16:45
*** _nadya_ has quit IRC16:45
*** _nadya_ has joined #openstack-meeting16:45
*** xingchao has joined #openstack-meeting16:47
*** rbak has quit IRC16:48
*** KunalGandhi has quit IRC16:49
*** _nadya_ has quit IRC16:50
*** dneary has joined #openstack-meeting16:51
*** dims has quit IRC16:52
*** xingchao has quit IRC16:52
*** dims has joined #openstack-meeting16:52
*** dims has quit IRC16:52
*** rbak has joined #openstack-meeting16:52
*** dims has joined #openstack-meeting16:53
*** rbak has quit IRC16:54
*** jaypipes has quit IRC16:54
*** puranamr has joined #openstack-meeting16:54
*** witek has joined #openstack-meeting16:54
*** jaypipes has joined #openstack-meeting16:55
*** whenry has joined #openstack-meeting16:57
*** dkranz has quit IRC16:58
*** witek has quit IRC16:59
*** hashar has quit IRC16:59
*** BobBall is now known as BobBall_AWOL17:00
*** ub2 has quit IRC17:00
*** bobh has joined #openstack-meeting17:01
*** armax has joined #openstack-meeting17:01
*** coolsvap|dinner is now known as coolsvap|mt17:01
*** coolsvap|mt is now known as coolsvap|mtg17:01
*** dboik has quit IRC17:01
*** amitgandhinz has joined #openstack-meeting17:03
*** ivar-lazzaro has joined #openstack-meeting17:04
*** elo has joined #openstack-meeting17:04
*** topol has joined #openstack-meeting17:05
*** vivek-ebay has joined #openstack-meeting17:05
*** Tross has joined #openstack-meeting17:05
*** rbak has joined #openstack-meeting17:06
*** harshs has joined #openstack-meeting17:06
*** vivek-e__ has joined #openstack-meeting17:07
*** vivek-ebay has quit IRC17:07
*** vivek-eb_ has quit IRC17:07
*** eliqiao has quit IRC17:08
*** KunalGandhi has joined #openstack-meeting17:09
*** eliqiao has joined #openstack-meeting17:09
*** KunalGandhi has quit IRC17:09
*** jamespage_ has joined #openstack-meeting17:09
*** mpaolino has quit IRC17:10
*** KunalGandhi has joined #openstack-meeting17:10
*** balajiiyer has joined #openstack-meeting17:11
*** neelashah has quit IRC17:11
*** ub has joined #openstack-meeting17:12
*** doude has quit IRC17:14
*** breitz has left #openstack-meeting17:14
*** rbak has quit IRC17:14
*** ivar-laz_ has joined #openstack-meeting17:16
*** jamespage_ has quit IRC17:18
*** ivar-lazzaro has quit IRC17:19
*** bobh has quit IRC17:20
*** MarkAtwood has quit IRC17:20
*** boris-42 has quit IRC17:20
*** neiljerr` has joined #openstack-meeting17:20
*** sudipto has quit IRC17:20
*** llu has quit IRC17:20
*** mestery has quit IRC17:20
*** otter768 has joined #openstack-meeting17:20
*** alex_xu has quit IRC17:21
*** llu has joined #openstack-meeting17:21
*** stevemar has joined #openstack-meeting17:21
*** neiljerram has quit IRC17:21
*** jamespage_ has joined #openstack-meeting17:22
*** boris-42 has joined #openstack-meeting17:22
*** AzherKhan has joined #openstack-meeting17:23
*** alex_xu has joined #openstack-meeting17:23
*** merooney has joined #openstack-meeting17:23
*** Apoorva has joined #openstack-meeting17:25
*** otter768 has quit IRC17:25
*** neiljerr` has quit IRC17:26
*** neelashah has joined #openstack-meeting17:26
*** annegentle has joined #openstack-meeting17:30
*** balajiiyer has quit IRC17:31
*** iurygregory has joined #openstack-meeting17:33
*** jamespage_ has quit IRC17:34
*** balajiiyer has joined #openstack-meeting17:34
*** annegentle has quit IRC17:35
*** ayoung has quit IRC17:36
*** yassine__ has quit IRC17:36
*** ivar-laz_ has quit IRC17:38
*** ivar-lazzaro has joined #openstack-meeting17:38
*** glauco_ has quit IRC17:41
*** baoli has joined #openstack-meeting17:41
*** achanda has joined #openstack-meeting17:42
*** janonymous_ has joined #openstack-meeting17:43
*** eliqiao has quit IRC17:45
*** dneary has quit IRC17:46
*** eliqiao has joined #openstack-meeting17:47
*** markvoelker has quit IRC17:47
*** tsymanczyk has joined #openstack-meeting17:48
*** david8hu has joined #openstack-meeting17:48
*** amotoki has quit IRC17:48
*** MarkAtwood has joined #openstack-meeting17:49
*** ub has quit IRC17:49
*** pvaneck has joined #openstack-meeting17:50
*** stanchan has joined #openstack-meeting17:51
*** ub has joined #openstack-meeting17:51
*** haomaiwang has quit IRC17:51
*** haomaiwang has joined #openstack-meeting17:52
*** baoli has quit IRC17:52
*** glauco has joined #openstack-meeting17:53
*** baoli has joined #openstack-meeting17:53
*** mestery has joined #openstack-meeting17:54
*** armax has quit IRC17:54
*** jmckind has quit IRC17:55
*** fawadkhaliq has quit IRC17:55
*** mestery has quit IRC17:55
*** browne has joined #openstack-meeting17:56
*** lhcheng_ has joined #openstack-meeting17:56
*** changbl has quit IRC17:57
*** dboik has joined #openstack-meeting17:57
*** jasondotstar has quit IRC17:58
*** Piet has quit IRC17:58
*** qwebirc34569 has joined #openstack-meeting17:59
*** fzdarsky has joined #openstack-meeting17:59
*** jmckind has joined #openstack-meeting17:59
*** henrynash has joined #openstack-meeting17:59
*** roxanaghe_ has joined #openstack-meeting17:59
*** kylek3h has joined #openstack-meeting18:00
henrynashhi18:01
*** neiljerr` has joined #openstack-meeting18:01
*** padkrish has joined #openstack-meeting18:01
*** amuller has left #openstack-meeting18:01
marekdhello18:01
lbragstado/18:01
htrutao/18:01
roxanaghe_hi18:01
topolo/18:01
tsymanczykhello18:01
david8huo\18:01
morganfainbergso stevemar o/18:01
*** neelashah has quit IRC18:01
*** haneef has joined #openstack-meeting18:02
*** achanda has quit IRC18:02
raildoこんにちは18:02
*** achanda has joined #openstack-meeting18:02
morganfainbergajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rharwood, rodrigods, roxanaghe, samueldmq, stevemar, topol, wanghong18:02
marekdo/18:02
dstaneko/18:02
rodrigodso/18:03
lhcheng_o/18:03
samueldmqhey18:03
*** sridhar_ram has quit IRC18:03
morganfainberghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:03
samueldmqI am ready for the battle18:03
*** shaleh has joined #openstack-meeting18:03
*** jamielennox has joined #openstack-meeting18:03
qwebirc34569o/18:03
morganfainbergit's that time of the week...18:03
brownehi18:03
jamielennox...18:03
ericksonsantos\o18:03
morganfainbergjamielennox: Hi!18:03
*** fawadkhaliq has joined #openstack-meeting18:04
morganfainbergok i think we have enough cores for a quorum18:04
* morganfainberg looks for an ayoung, stevemar, lhcheng_, and henrynash18:04
morganfainbergoh i see henrynash18:04
marekdhenrynash was here18:04
*** alex_xu has quit IRC18:04
morganfainberg#startmeeting keystone18:04
openstackMeeting started Tue Jul 28 18:04:56 2015 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:04
*** openstack changes topic to " (Meeting topic: keystone)"18:04
openstackThe meeting name has been set to 'keystone'18:05
morganfainbergHi and stuff18:05
*** penick has quit IRC18:05
bknudsonhi18:05
*** llu_linux has joined #openstack-meeting18:05
*** fawadkhaliq has quit IRC18:05
*** llu has quit IRC18:05
henrynashyep, I;m here18:05
morganfainberg#topic Reviews needed for List Role Assignments Performance patch18:05
*** openstack changes topic to "Reviews needed for List Role Assignments Performance patch (Meeting topic: keystone)"18:05
*** VanL has quit IRC18:05
morganfainberghenrynash: lead on18:05
henrynashok, So this is something that samueldmq worked on during Kilo, but we bumped it18:05
henrynashhttps://review.openstack.org/#/c/137202/18:05
samueldmqhenrynash: it has almost 1 year now :)18:05
*** xyang1 has quit IRC18:05
henrynashalthough it is great for performance…we really want to do this as well so we can base all code that needs to workout group and inheritance roles on this18:06
henrynashso just a plea for some review time so ew can get it into L2 hopefully18:06
morganfainbergwont land for L2 unless it's gating today18:06
morganfainbergFYI18:06
henrynashok, so if not L2, then L3 !18:07
morganfainbergso assume it's an L318:07
*** ayoung has joined #openstack-meeting18:07
henrynashthere are a whole string of patches that follow this that start using this backend filtering18:07
*** MarkAtwood has quit IRC18:07
ayoungoyez18:07
* morganfainberg waves ayoung to the front of the room.18:07
*** fzdarsky has quit IRC18:07
henrynashno need to take up more time here, unless anyone has specific questions18:08
ayounghenrynash, we have hard numbers oin the perf issues?18:08
*** pauloewerton has joined #openstack-meeting18:08
dolphmI can probably help validate performance18:08
morganfainberghenrynash: if it's a "perf" reason to do the work, I'd like to see numbers validating the gain/benefit18:08
dolphmBeen doing a lot of that lately18:08
morganfainbergdolphm: ++ thanks.18:08
samueldmqdolphm: ++ it'd be great ot have some benchmarking on that :)18:08
*** pnavarro has quit IRC18:08
dstaneki have not looked at this review since last week, but i'll get through it after this meeting18:08
henrynashayoung: no…but the current code is that any list of role assignments  means we retrieve ALL role assignmenst i the whole system, and tehn filter them in teh controller18:09
*** alex_xu has joined #openstack-meeting18:09
samueldmqdolphm: let me know if you need a hand on that front18:09
samueldmqdstanek: thanks18:09
ayoungwe probably should make sure to include LDAP in there.  I had a data set for a large user list...we should probably build up a "to scale" data set18:09
bknudsontarget https://blueprints.launchpad.net/keystone/+spec/list-role-assignments-performance to l3?18:09
samueldmqldap assignment is dying a terrible death (cc morganfainberg )18:09
*** josdotso has joined #openstack-meeting18:09
samueldmqayoung: ^18:10
morganfainbergsamueldmq: this is identity not assignment18:10
ayoungyeah,  solemente LDAP for Identity18:10
henrynashayoung: the current code works for both ldap and sql (even thouse assignent ldap is a lower priority)18:10
morganfainbergbknudson: target for l3 when it lands. lets not try and predict it landing.18:10
ayoungusers and groups in LDAP,  role assignments in SQL is my primary use case18:10
samueldmqthis is assignment, list_role_assignments18:10
*** changbl has joined #openstack-meeting18:10
morganfainbergbknudson: or if you feel strongly, go ahead and target it - i'll work w/ relmngmnt to untarget if needed down the line18:11
ayoungmorganfainberg, bknudson ++18:11
*** MarkAtwood has joined #openstack-meeting18:11
samueldmqI don't even touch the identity code18:11
*** tellesnobrega has quit IRC18:11
ayoungdstanek, I still owe you an LDAP functional test, too18:11
bknudsonI don't feel strongly either way... wasn't sure how we're tracking.18:11
morganfainbergbknudson: i'm at the point we should target when it lands if we cna18:12
morganfainbergcan*18:12
morganfainbergrather than saying "this will land at X" and then untargeting later18:12
dstanek++ makes it easier to see what's going on in a glance18:12
*** okrieg has quit IRC18:12
samueldmqmorganfainberg: and that could be done automatically by our tools18:12
*** armax has joined #openstack-meeting18:13
morganfainbergok so, from my perspective - if we have clear numbers [since this claimed to be perf] i'm fine with this landing in l318:13
*** VanL has joined #openstack-meeting18:13
bknudsonapparently it's not just perf since a bunch of other stuff is depending on it18:13
ayoungdolphm, you've been testing speed, but not memory usage, right?18:14
samueldmqbknudson: yes, it moves the expasion logic to the manager level18:14
bknudsonand I assume the stuff that depends on it isn't needing it just for perf18:14
dolphmCorrect18:14
*** olaph has joined #openstack-meeting18:14
henrynashbknduson: ++18:14
dolphmOur memory usage is generally not alarming18:14
ayoungthis might be more of a memory perf issue, if all those lists are duplicated.  Might be worth considering for future perf issues18:14
ayoungwe might hit memory management thresholds18:15
morganfainbergmemory usage is mostly fine in keystone atm18:15
ayounggood to know18:15
*** tellesnobrega has joined #openstack-meeting18:15
ayounglist users had some issues that way, IIRC18:15
morganfainbergit's worth evaluating - but not in this context18:15
ayoungbefore limiting results18:15
morganfainbergas a separate specific evaluation18:15
samueldmqif we have lots of group/inherited assingments, that would be toooo bad18:15
morganfainbergsince we haven't really done this for keystone in the past18:15
samueldmq++18:16
morganfainberglets not make that a requirement here [since we've mostly been fine]18:16
ayoungmorganfainberg, "for future ..."18:16
morganfainbergayoung: yes.18:16
henrynashmorganfainberg: Ok, that’s probably enough on that one18:16
*** rfolco has quit IRC18:17
morganfainbergi see no issue with this landing in l3, please review it18:17
bknudsonI starred it.18:17
morganfainbergunless someone has a concern18:17
*** breton has joined #openstack-meeting18:17
morganfainberg#topic Request from nova meetup: Document what other projects need to know about keystone18:17
*** openstack changes topic to "Request from nova meetup: Document what other projects need to know about keystone (Meeting topic: keystone)"18:17
morganfainbergbknudson: o/18:17
bknudsonthe nova midcycle was in rochester last week18:17
bknudsonso I went to it since it's just on the other side of the facility18:18
bknudsonthey had a few questions, so I suggested I'd write up a doc so they'd be able to refer to it in future18:18
bknudsonmostly about what's v3.18:18
*** okrieg has joined #openstack-meeting18:18
bknudsonrather than try to do everything in a review I started an etherpad: https://etherpad.openstack.org/p/keystone-info18:18
bknudsonwhich I'll copy into a review for our docs next week.18:19
ayoungI think that is split into two pieces;  auth token (which is all Nova should care about) and stuff like what Heat and more workflow related projects need18:19
bknudsonso if you have anything to add just do it.18:19
ayoungV3 auth token needs to be well supported.18:19
*** penick has joined #openstack-meeting18:19
jamielennoxfor auth_token i almost just need to start again on the docs18:20
topolnice writeup bknudson18:20
jamielennoxthere's so much that's been deprecated or otherwised moved that it gets confusing18:20
ayoungnice.18:20
*** singleth_ has joined #openstack-meeting18:20
ayoungdolphm, this kindof gets at why I wrote up that V2.0 bug18:21
jamielennoxbut i agree, there are very few services that should know anything more than what auth_token provides18:21
*** vishwanathj has joined #openstack-meeting18:21
ayounglink in a sec18:21
morganfainbergjamielennox: ++ yep, pretty much auth_token and auth [keystoneauth] is the real limit of what services need to know unless they are heat18:22
morganfainbergor similar orchestration18:22
morganfainbergauth if they need to do independant $things18:22
morganfainbergand most don't18:22
ayoungbut there is there ever a case where a V2 token needs to be properly converted to a V3 token, to inlcude domain values?18:22
samueldmqor they need to know, let's say, a given project's hierarhcy to do quota enforcement18:22
samueldmq:)18:23
jamielennoxand that would be what i would add to that etherpad, yes we explain domains but be explicit that nova should never care about it18:23
*** baoli has quit IRC18:23
jamielennoxwe have lots of requests saying how should i handle domains and the answer is to ignore them18:23
morganfainbergok so lets get that info added to the etherpad18:23
ayounghttps://bugs.launchpad.net/keystone/+bug/147737318:23
openstackLaunchpad bug 1477373 in Keystone "No way to convert V2 tokens to V3 if domain id changes" [Undecided,New]18:23
uvirtbotLaunchpad bug 1477373 in keystone "No way to convert V2 tokens to V3 if domain id changes" [Undecided,New]18:23
uvirtbotLaunchpad bug 1477373 in keystone "No way to convert V2 tokens to V3 if domain id changes" [Undecided,New] https://launchpad.net/bugs/147737318:23
morganfainbergayoung: wait what?18:23
bknudsonbots are taking over18:23
*** singlethink has quit IRC18:23
morganfainbergayoung: that doesn't make sense at all18:23
morganfainbergayoung: if domain id changes?!18:24
ayoungmorganfainberg, we discussed at the midcycle.18:24
*** yamamoto has quit IRC18:24
ayoungmorganfainberg, from "default" to some UUID18:24
ayoungif the default domain changes...18:24
morganfainbergif they are changing the default domain...18:24
morganfainbergthings are going to get weird18:24
ayoungok...lets say we have a setup where there is a lot of V2 tooling18:24
ayoungbut they are switching over to LDAP for end users18:24
ayoungso the LDAP goes into a domain specific backend18:24
samueldmqand we allow that https://github.com/openstack/keystone/blob/master/etc/keystone.conf.sample#L79118:25
*** vishwana_ has joined #openstack-meeting18:25
*** Swanson has joined #openstack-meeting18:25
*** vishwanathj has quit IRC18:25
bknudsonget rid of your v2 tooling18:25
ayoungare we saying that the default domain always *MUST* have a domain ID of _default_?18:25
morganfainbergayoung: i'd say default domain needs to have an id that isn't changed post deployment18:26
samueldmqayoung: we can't as we provide a config option for it18:26
ayoungbknudson, people have been building to V2 for a while.  Getting rid of it will take a while18:26
morganfainbergunless you're really willing to do all sorts of insane things18:26
ayoungmorganfainberg, "isn't changed post deployment" doesn't quite cut it18:26
ayoungwe don't communitate the domain id in any manageable way18:26
morganfainbergayoung: honestly i want to push people towards v3 more and more18:26
ayoungthe two options we discussed at the mid cycle were "query the config options via a web api" and "put hints in the v2 tokens"18:27
*** vishwana_ has quit IRC18:27
*** xyang1 has joined #openstack-meeting18:27
*** rbak has joined #openstack-meeting18:27
ayoungbut...maybe the "hints" part is no longer an issue...18:27
* morganfainberg doesn't remember this convo18:27
dolphmBecause v2 clients are not domain aware, and the default domain is bit special in v318:27
dolphmNot*18:27
ayoungI was thinking PKI, but with Fernet, it is not really a problem...we can always tell them to get v3 tokens...18:27
*** ub has quit IRC18:28
brownesome v2 tooling is still necessary from my experience.  i've tried to use OSC but it does not have all commands available in the older CLIs18:28
morganfainbergbrowne: ok so v2 keystone should have no impact on the other CLIs18:28
dolphmBrowne, like what?18:28
ayoungbrowne, I saw that with neutron, but neutron CLI should work with V3 auth18:28
bknudsonso you're going to switch the domain_id for a couple of operations and then switch it back?18:28
ayoungbknudson, neutron misses routers...maybe even subnets18:28
brownelike creating provider networks in OSC.  you can do it in neutron CLI but not OSC18:28
morganfainbergbrowne: this sounds like a bug in OSC18:29
*** olaph has quit IRC18:29
*** haomaiwang has quit IRC18:29
shalehOSC has not been updated to support all commands from the project CLIs18:29
ayoungok...so are we finally at the point where we can say "deprecate V2.0" and we will have an aswer for all use cases?18:29
haneef neutron CLI supports v318:29
brownemorganfainberg: agree, but becomes an inhibitor to going to keystone v3.  i was trying to utilize the multi-domain backend feature18:29
shalehmake bugs, people will close it18:29
morganfainbergso lets fix the bug in OSC18:29
morganfainbergbrowne: this is not a reason we should be holding onto v2 keystone --18:30
ayoungif so, and we can honestly kill v2.0 tokens, I'll be very happy18:30
*** olaph has joined #openstack-meeting18:30
* morganfainberg is really getting tired of the auth is tied to the crud interface18:30
bknudsonif the CLIs aren't deprecated then they need to support v3 auth18:30
lifelessmorganfainberg: does it feel dirty?18:30
*** haomaiwang has joined #openstack-meeting18:30
morganfainberglifeless: i am going to avoid a reaaaaaaly long rant on that here ;)18:30
*** _nadya_ has joined #openstack-meeting18:31
bknudsonwhat doesn't work with users in ldap domain?18:31
ayoungOK, so we can tell all of the other services "forget that v2.0 token API exists."  right?18:31
morganfainbergayoung: that is what we should do.18:31
dstanekare the other CLIs not deprecated? i haven't been paying attention18:31
ayoungbknudson, ah,  so if you do an install, the default domain gets all the service users18:32
morganfainbergdstanek: i think we're the only one officially saying "no really stop using it and go to osc"18:32
dstanekmorganfainberg: bummer18:32
bknudsondstanek: I haven't seen any other project deprecate their CLI18:32
ayoungand then you creata new domain, put ldap in there, and make that the default domain for all the V2 tooling out there18:32
bknudsonesssentially you've got service users in your default domain18:32
ayoungits more than just the osc thing.  Its the keystone.rc files18:32
morganfainbergso lets work on making v2 auth die.18:33
haneefbrowne: multi-domain backend will have problems with few apis.  if you are using  list_users ( all users), there is no such operation in  multi_domain_backend.  It is always list_user for a domain18:33
samueldmqmaybe we should move on .. otherwise we won't cover the other topics in the meeting :(18:33
morganfainberghaneef: that isn't really a reason to hang onto v218:33
samueldmqat least the ones listed in the meeting page :)18:33
morganfainberghaneef: in fact, i'd say that has no real bearing on v2 vs v318:33
jamielennoxthe only people that need service users in the default domain now are the projects that mix their keystone_authtoken parameters and if you switch it over to v3 auth then the service doesn't work18:33
jamielennoxthere aren't many of those left (none off the top of my head)18:33
ayoungbknudson, but if you have a thrid party app, that only knows about V2 auth, and your LDAP users will want to use that app, you make the default domain other thanthe one setup by the installer with the domain id of _default_18:33
dstaneksamueldmq's waiting to be grilled :-)18:33
morganfainbergjamielennox: and i just sent another email to the ML asking people to avoid doing that again18:34
samueldmqdstanek: eheh18:34
jamielennoxmorganfainberg: i saw18:34
morganfainbergi saw some more cases it was being implemented18:34
ayoungthat was the context behind that bug.  I'll try to make it clearer18:34
morganfainbergok18:34
bknudsonayoung: I think you're going to have problems anyways... what if I have 2 LDAP domains?18:34
ayoungbknudson, I'm just trying to solve common case18:34
morganfainbergok i think we're kind of off the topic here and into the weeds18:35
ayoungobviosuly won't work for everyone18:35
bknudsonupdate https://etherpad.openstack.org/p/keystone-info with more info18:35
bknudsonand it'll eventually go in keystone developer docs18:35
morganfainbergbknudson: ++18:35
bknudsonthen you can update it there18:35
morganfainbergplease update the etherpad18:35
morganfainbergok lets move on18:35
morganfainberg#topic keystoneauth release? K2K in Horizon is waiting for the K2KAuthPlugin, should we add it in python-keystoneclient so we can speed up things?18:35
*** openstack changes topic to "keystoneauth release? K2K in Horizon is waiting for the K2KAuthPlugin, should we add it in python-keystoneclient so we can speed up things? (Meeting topic: keystone)"18:35
morganfainbergjamielennox: this is a question for you -- how soon can we get keystoneauth ready to go?18:36
ayoungare there library deps?  thought that needed saml218:36
bknudsonis this 1.0 release ?18:36
morganfainbergwe need to dump oslo.config and there were a couple minor things left18:36
bknudsonor 0.1 or something?18:36
marekdayoung: nope18:36
morganfainbergbknudson: this depends on keystoneauth 1.0 *or* needs to go into keystoneclient18:36
bknudsonhow do the docs look?18:36
jamielennoxi haven't been active on it for a week or two, but i posted a review the other day18:36
jamielennoxumm18:36
ayoungcool18:36
jamielennoxhttps://review.openstack.org/#/c/205753/18:36
morganfainbergso the biggest blocker is oslo.config18:36
morganfainbergprobably #2 is docs18:37
jamielennoxthat review just removes everything to do with plugin loading and so removes the stevedore and oslo.config dep18:37
morganfainbergah18:37
morganfainbergcool18:37
bknudsonneutron is being a real stick in the mud with keystoneauth reviews recently18:37
*** rossella_s has quit IRC18:37
jamielennoxthis would mean that to do all the automated plugin loading for now you would still need to use keystoneclient18:37
morganfainbergjamielennox: we need to find out how to do automated plugin loading without keystoneclient and without oslo.config18:38
jamielennoxbut it would mean we could unblock the k2k stuff and the federation stuff that doesn't have a great story around automatic loading anyway18:38
*** rossella_s has joined #openstack-meeting18:38
*** _nadya_ has quit IRC18:38
morganfainbergjamielennox: lets not walk backwards to requring ksc for things18:38
jamielennoxand figure out what we want to do about loading as a seperate step18:38
bknudsonmake it a separate project18:38
*** olaph has quit IRC18:38
*** _nadya_ has joined #openstack-meeting18:38
bknudsonkeystoneauth-config18:38
morganfainbergi don't want to force people back to keystonelcient which is what that would do18:38
jamielennoxmorganfainberg: right - i'm not saying we keep it in ksc permanently, just get ksa moving along18:38
morganfainbergjamielennox: we can't release a 1.0 if everyone keeps using keystoneclient and has no path forward18:39
morganfainbergwe need a path forward for 1.z18:39
morganfainberg1.x*18:39
jamielennoxbknudson: the failure isn't actually neutrons fault, there is some issue with git cloning the project i haven't figured out yet18:39
dstanekjamielennox: is that the job failure i keep seeing?18:39
bknudsonjamielennox: thanks for looking into it18:39
rodrigodsif we still need to use ksc, what your opinion regarding k2k plugin?18:39
*** fawadkhaliq has joined #openstack-meeting18:39
morganfainbergrodrigods: we aren't going to require keystoneclient18:40
jamielennoxmorganfainberg: particularly if the auth loading stuff is going into anotherproject then it would be fine to release 1.0 without it18:40
morganfainbergjamielennox: then i want that other project ready as well18:40
morganfainbergjamielennox: i am not willing to do a "we might or might not do this but we don't know and we aren't fixing anything but depending on this other thing"18:40
morganfainbergsorry i'd rather scrub keystoneauth completly18:40
marekdmorganfainberg: how about rodrigods just depend on exiting ksa with some red flag in mind?18:40
marekdrodrigods: k2k plugin will not change ....18:41
dstaneki asked about http://logs.openstack.org/88/201088/5/check/gate-tempest-dsvm-neutron-src-keystoneauth/4439cd5/logs/devstacklog.txt.gz#_2015-07-28_13_55_04_277 in infra earlier today, but haven't gotten a chance to follow up on their hint18:41
marekdso i don't expet your patches would change one day18:41
marekdrodrigods: and we will just wait for ksa release18:41
marekdmorganfainberg: stevemar same could be with moving osc to ksa.18:41
*** Piet has joined #openstack-meeting18:41
marekdmorganfainberg: stevemar cause right now federated plugins are quite messy and it's just better to start using ksa.18:41
marekdor ksa-saml2 repo even18:42
*** markvoelker has joined #openstack-meeting18:42
morganfainbergif all we're doing is moving logic out but everyone has to keep doing it the old way and we have no real knowledge of where loading is going18:42
morganfainbergwe're doing it wrong.18:42
ayounganything else the rest of us need to do?18:42
morganfainbergso lets solve where loading is18:42
morganfainbergand break the dep on oslo.config *and* not force keystoneclient18:42
bknudsonI kind of like the separate project for config / loading since then it would shield users from having to know which keystoneauth version they need.18:42
*** pelix has quit IRC18:43
morganfainbergbknudson: i'd support it18:43
jamielennoxok, i'll look at getting another project spun up for the loading as i've had mutliple people suggest it18:43
morganfainbergjamielennox: ++18:43
morganfainbergthankx18:43
jamielennoxOSC is very keen on seperate project18:43
*** puranamr has quit IRC18:43
jamielennoxwell dtroyer anyway18:43
*** _nadya_ has quit IRC18:43
morganfainberg#topic Reseller18:43
*** openstack changes topic to "Reseller (Meeting topic: keystone)"18:43
morganfainberghtruta: o/18:43
htrutamorganfainberg: o/18:43
rodrigodsplease review18:43
rodrigods^18:43
htrutathat should be quick18:43
htrutayes, please18:43
raildo++18:43
htrutashould we set a target to L3 ?18:43
rodrigodshttps://review.openstack.org/#/c/157427/18:44
htrutawe don't have it yet18:44
rodrigodsstart from here18:44
morganfainbergagain18:44
morganfainbergdon't target until landing18:44
morganfainbergdon't try and predict landing, target when it has landed18:44
htrutamorganfainberg: k18:44
morganfainberganything else on reseller?18:44
*** Daisy has joined #openstack-meeting18:44
htrutathat's all18:45
ayoungsamueldmq, your up18:45
morganfainberg#topic Dynamic Policies18:45
*** openstack changes topic to "Dynamic Policies (Meeting topic: keystone)"18:45
ayoungor you're up18:45
samueldmqhi18:45
ayoungeither way18:45
morganfainbergwhere is the spec?18:45
morganfainbergagain?18:45
david8huWe need to cut the policy overlay piece and go straight to centralize complete policy files in Keystone.  Most deployers are not changing their policy files, but if they do, they want to test out locally with the local policy files.  Deployers might as well submitt the entire tested policy file to keystone.18:45
*** sridhar_ram has joined #openstack-meeting18:45
samueldmq#link https://review.openstack.org/#/c/197980/18:45
samueldmqand18:45
samueldmq#link https://review.openstack.org/#/c/134655/18:45
*** DaveJ__ has quit IRC18:45
samueldmqthose 2 are the remaining ones, one for ksmiddleware and another for keystone controlling the cache mechanism18:46
ayoungI think 80 should be non-contraversial;  using HTTP properly18:46
*** markvoelker_ has joined #openstack-meeting18:46
samueldmqwe've got reviews, I updated the spec, everything looked good but dstanek has some concerns on it18:46
ayoungit is the 55 one that is the client side that needs the SFE18:46
*** puranamr has joined #openstack-meeting18:47
marekddstanek: ?18:47
ayounghenrynash, so :endpoint_ids" are just the first hack.  eventually, we will resolve the urls to endpoint_ids, but we can do it in steps18:47
ayoungendpoint_ids are already implemented by the server.18:47
*** markvoelker has quit IRC18:48
*** egallen has quit IRC18:48
*** pauloewerton has left #openstack-meeting18:48
samueldmqbasically dstanek's concerns are that, in our current endpoint model, we allow an effective service endpoint to have multiple policies (since multiple interfaces mean multiple ids)18:48
dstaneksamueldmq and i were discussing today how we could possibly use a list of endpoint ids and pick one for the service18:48
*** stevemar has quit IRC18:48
samueldmqdstanek: please go ahead18:48
ayoungdstanek, "hard than you think" we are aware of how hard it can be, which is why we are going to do endpoint_id first18:48
*** Daisy has quit IRC18:49
dstanekayoung: if you allow the service to specify a list of endpoints, which policy do they get if each has a policy defined?18:49
ayoungdstanek, are any of your concerns "stop ship" type concerns18:49
ayoungdstanek, I would limit it to 1 endpoint id to start in the authtoken config section18:50
dstanekayoung: i think the model in fundamentally wrong :-(  i guess it's possible that we can document and exact setup that would work18:50
*** egallen has joined #openstack-meeting18:50
ayounga service could, in theory have multiple config files, one per endpoint on the same server.  In practice, they will share a config fi;e18:50
david8huBTW, did anyone chk with nova and others to see if the proposal meet their needs?18:51
samueldmqdavid8hu: this work of policy distribution is independent of what they have/want18:51
samueldmqdavid8hu: we allow policy definition/associoation, just putting the distribution together now18:51
david8husamueldmq, but they are ultimately the consumers.18:52
ayoungdavid8hu, we've had a distinct lack of response from the other projects on Dynamic policy, with the exception of Horizon, that really needs it18:52
dstaneki would rather know if it handles deployer needs/concerns18:52
*** baoli has joined #openstack-meeting18:52
samueldmqdavid8hu: our consumers here are the deployers18:52
ayoungdstanek, horizon is currently caching the policy files.  It would be most useful to UIs18:52
ayoungto know that the policy file they had matched the one the endpoint is using18:52
samueldmqdstanek: so I've an email draft, but ayoung had some concerns about sending this out at this point18:53
samueldmq#link https://etherpad.openstack.org/p/centralized-policy-delivery-operators18:53
david8husamueldmq, all other services still need changes to pick this up don't they?18:53
ayoungdavid8hu,  no, that is the point18:53
samueldmqdavid8hu: no that will be a change in ksmiddleware18:53
samueldmqayoung: ++18:53
ayoungthey do not need to change, they inherit the config option from keystone18:53
dstanekthe right thing to do would be to allow the endpoint id (only 1 and not a list) to be specified for each instance of middleware18:53
*** olaph has joined #openstack-meeting18:53
david8hunot even minor changes?18:54
ayoungdstanek, ++18:54
samueldmqdstanek: ayoung so we don't do url -> discovery ?18:54
henrynashayoung: endpoint_ids are my concern as well…..reading the spec doesn’t explain to me how endpoint_ids wrok in this context, what the limitations/complexities might be for a deployer etc.  So I have a hard time supporting this as spec’d18:54
samueldmqand let the deployer choose the id ?18:54
ayoungdavid8hu, they need to change to use the oslo.poliyc library anyway.  Beyond that, it is all middleware18:54
dstaneksamueldmq: i've always said that you have to have a single ID for the middleware to use. i'd rather it just be a policy id, but any id would fix the ambiguity we keep creating18:55
ayounghenrynash, I am asusming you are thinking that a singe server is backing multiple endpoints with multiple policy files, so how do we get the right one?   Short answer, we don't support that to start18:55
*** baoli has quit IRC18:55
ayoungwe support "you get one for this server.  Pick one"18:55
*** baoli has joined #openstack-meeting18:55
morganfainbergdstanek: the only concern with the policy id is if it's a uuid meaning you need to upload the data to know what the id is... bad bad bad for deployers18:56
*** rfolco has joined #openstack-meeting18:56
ayoungdstanek, if we go with the policy ID, we can't update the policy for an endpoiint without restarting the endpoint18:56
henrynashayoung: we just don’t eplain this in the spec…..other than saying “the deployer can set the endpoing_ids"18:56
dstanekayoung: if the middleware just knows about an id a service can deploy with muliple pipelines including that middleware with different Ids, right?18:56
samueldmqmorganfainberg: another point is that we aren't holding the endpoint/policy association in keystone server that way18:56
samueldmqmorganfainberg: and changign the policy id would require a restart18:56
dstanekmorganfainberg: endpint id has the same issue18:56
ayounghenrynash, becasue the goal was to not have to do this... morganfainberg was pushing for a completely automated discovery...we want to support that. but please stop asking for us to boil the ocean...we are shooting for "actually implementable" here18:57
dstaneksamueldmq: that's a good point18:57
*** Shrews has joined #openstack-meeting18:57
*** fzdarsky has joined #openstack-meeting18:57
ayoungdstanek, right, the goal here is to migratethe policy management from static files/ansible/config file to centralize in the keystone server18:58
henrynashayoung: I’m just asking for a clear spec….if the answer one endpoint, fine…just say so….what’s tough to support is a spec that isn;t clear about what is and isn’t supported18:58
ayoungif that goal is not acceptable to the team...please speak up now.  This has been my concern, that we are arguing about details, but have not agreed on the big picture18:58
samueldmqmorganfainberg: should we continue in #keystone ? I think we're out of time .. infra folks should start they meeting18:58
morganfainbergwe have 1-2min18:58
*** AJaeger has joined #openstack-meeting18:58
samueldmqok18:58
*** yolanda has joined #openstack-meeting18:59
*** radez is now known as radez_g0n318:59
dstanekayoung: i could see having a service_id or endpoint_id in the config (but if would be nice to support having multiple instances of middleware) - no lists because that can't work18:59
ayoungdstanek, I agree18:59
ayoungwe'll make that modification18:59
henrynashayoung: I support the principle of a Keysteone Polciy CMS (that’s what this is)….so it IS the detail for me18:59
dstanekayoung: i'm just wondering if any deployer cares18:59
morganfainberg#endmeeting18:59
*** openstack changes topic to "BP (Meeting topic: tricircle)"18:59
openstackMeeting ended Tue Jul 28 18:59:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
*** ianw has quit IRC18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-07-28-18.04.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-07-28-18.04.txt18:59
morganfainbergand to -keystone18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-07-28-18.04.log.html18:59
ayoungok...so, assuming we make that change, any other showstoppers?18:59
ayoungand...I just turned into a pumpkin19:00
*** qwebirc34569 has quit IRC19:00
*** ayoung has quit IRC19:00
clarkbo/19:00
*** ianw has joined #openstack-meeting19:00
jeblairhowdy infras19:00
pleia2o/19:00
*** lhcheng_ has left #openstack-meeting19:00
Zarao/19:00
nibalizeryay infra!19:00
*** adreznec has joined #openstack-meeting19:00
*** etoews has joined #openstack-meeting19:00
yolandao/19:00
mmedvedeo/19:00
* olaph lurks19:01
* Shrews stabs olaph, then lurks19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Jul 28 19:01:35 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
openstackThe meeting name has been set to 'infra'19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-07-21-19.02.html19:01
*** browne has left #openstack-meeting19:01
jheskethMorning19:01
ianwo/19:01
jeblair#topic Specs approval19:01
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:01
jeblair#topic Specs approval: Zuul v3 (jeblair)19:01
*** openstack changes topic to "Specs approval: Zuul v3 (jeblair) (Meeting topic: infra)"19:01
jeblair#link zuulv3 spec https://review.openstack.org/16437119:02
jeblairi wrote a spec19:02
jeblairi think we should do it19:02
jeblairi confess that it does not hold all the answers19:02
jeblairbut i think it describes enough that several people can work on aspects of the problem in parallel19:03
*** e0ne has joined #openstack-meeting19:03
jheskethI'm a fan and I'm looking forward to it. I'm sure we can figure it out what's left as we go19:03
jeblairit's certainly been hammered on for a while19:04
*** tsymanczyk has left #openstack-meeting19:04
yolandai'm willing to have some bits of that spec19:04
yolandaas a downstream consumer, i'm worried about others19:04
yolandaspecially about jenkins replacement19:04
*** ijw has quit IRC19:05
jeblairyeah, that will be some work19:05
*** rbak has quit IRC19:05
jeblairbut it beats hiring a bunch of people to restart jenkins all the time19:05
*** Piet has quit IRC19:05
clarkb+1000 as th eperson that did that yesterday19:06
clarkbmy upstream bug is still DOA fwiw19:06
yolandayes, we have jenkins problems as well19:06
jeblairanyway, anyone think it's not ready for voting, or shall we vote on it?19:06
* fungi is fashionably late19:07
pleia2I think it's as far as it'll get in this phase, voting sounds good19:07
fungiapologies19:07
*** ub has joined #openstack-meeting19:07
*** hemna is now known as hemnalunch19:07
jeblair#info zuulv3 spec voting open until 2015-07-30 19:00 UTC19:07
fungiyes, please open voting on the zuul v3 spec ;)19:07
jeblairwoot19:07
jeblair#topic Priority Efforts19:07
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:07
*** ijw has joined #openstack-meeting19:08
*** hashar has joined #openstack-meeting19:08
jeblairi'd like to take a break from our typical "never do status reports" and instead "do status reports" this week19:08
*** singlethink has joined #openstack-meeting19:08
jeblairmostly because a lot of us have been out and about recently, and it'll be good to try to resync on where we are now that most of us are back19:08
*** harshs has quit IRC19:09
jeblairand i'd love to remove some from the list :)19:09
*** armax has quit IRC19:09
jeblair#topic Priority Efforts (Swift Logs)19:09
*** openstack changes topic to "Priority Efforts (Swift Logs) (Meeting topic: infra)"19:09
jeblairwho knows what's up here?19:09
*** ivar-lazzaro has quit IRC19:09
clarkbjhesketh ^ otherwise I can fill in what I know19:09
*** cdub has joined #openstack-meeting19:09
*** ivar-lazzaro has joined #openstack-meeting19:10
*** witek has joined #openstack-meeting19:10
clarkbthe os loganalyze changes to support configurable file passthrough from swift are in place19:10
jeblairthat gets us "host binary files" ?19:10
jheskethYep so now the next part is just changing more jobs over19:10
jheskethYes19:10
clarkbso now we just need to deploy config that says pass through anything that isn't a log so that js and disk images etc work properly19:10
clarkbI think pleia2 and mtreinish discoverd a traceback today in the swift upload script which we should look at too19:11
*** fawadk has joined #openstack-meeting19:11
*** singleth_ has quit IRC19:11
jheskethYeah so part of changing the jobs over is figuring out what needs to be passed through or not too19:11
pleia2yeah, I can dig up the link if needed19:11
jheskethOh?19:11
jheskethThat's be handy19:12
*** fawadkhaliq has quit IRC19:12
clarkbjhesketh: our existing apache mod rewrite rules can be used as the basisi19:12
clarkbwe already decide for on disk stuff19:12
*** ijw has quit IRC19:12
fungipleia2: and possibly copying that traceback into paste.o.o before jenkins expires it in the next day19:12
jheskethclarkb: yep :-)19:12
pleia2fungi: good idea, I can share this over in -infra since we don't need to debug during the meeting19:13
clarkbjhesketh: do you want to write that change? I can give it a go if you are busy19:13
fungithanks!19:13
jheskethpleia2: okay thanks19:13
jeblair#action pleia2 provide swift log upload traceback19:13
jheskethclarkb: I can do the config change today but I don't think I'll have time to look at jobs until next week19:14
*** jprovazn has quit IRC19:14
clarkbjhesketh: ok19:14
jeblair#action jhesketh update os-loganalyze to use pass-through rules19:14
mtreinishclarkb: yeah we did19:14
mtreinishit was the same one from before, about hitting a timeout19:14
jeblairwhat's the status of the index problem we ran into?  (where you can't explore jobs that have run for a change)19:15
*** dneary has joined #openstack-meeting19:15
mtreinishjhesketh, clarkb: https://jenkins03.openstack.org/job/gate-tempest-pep8/3690/console19:15
jeblair(basically, there was no autogen index of things like logs.o.o/PATH_TO_CHANGE/gate/)19:15
clarkbjeblair: thats still not addressed, it requires knowledge of all the jobs that have run or will run in order to upload an index.html19:15
*** rbak has joined #openstack-meeting19:16
jeblairclarkb: or it requires os_loganalyze to ask swift, right?19:16
clarkbwe can probably have os-loganalyze generate it on the fly? do a swift list of that prefix19:16
clarkbjeblair: ya19:16
jheskethjeblair: ah I wasn't aware of that, but yes that's right19:16
jeblairanyone want to write that?19:16
jheskethWhich makes os-loganalyze more complex19:16
*** aeng has joined #openstack-meeting19:16
jheskethBut yeah, I can take a look19:16
*** ijw has joined #openstack-meeting19:17
jhesketh(but again not this week unless somebody else wants it)19:17
*** Piet has joined #openstack-meeting19:17
clarkbif I hvae time to poke at it I will let you know19:17
clarkbI am still in weird state of not knowing how much time I actually have t oget things done19:18
jheskethAlso there were a few tricky parts which is why we generated the indexes at upload time rather than on the fly19:18
jeblairanyone else want it?  relatively standalone python hacking thing19:18
jeblairjhesketh: yeah, i think that makes sense for the jobs, but outside of that, i'm pretty sure we need osla to do it19:18
jheskethFor example how to things that are half on disk and swift19:18
jeblairat least, this is one of the big questions we had for swift folks early on -- would it be able to handle these kinds of queries19:18
jeblairand i think the answer from them was "try it, it should work"19:19
jeblairjhesketh: yep; i think osla can figure that out too19:19
*** henrynash has quit IRC19:20
jheskethYeah there's a few things we can do19:20
jeblair#action jhesketh/clarkb have os-loganalyze generate indexes for directories which lack them19:20
*** iurygregory has left #openstack-meeting19:21
jeblairi'd still love it if someone else volunteered for that ^ :)  talk to jhesketh and clarkb if you want it19:21
*** baoli has quit IRC19:21
jeblair#topic Priority Efforts (Nodepool DIB)19:21
*** ijw has quit IRC19:21
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:21
*** harshs has joined #openstack-meeting19:21
*** otter768 has joined #openstack-meeting19:21
jeblairwho knows about this one?19:22
fungithe bindep bits of this are basically ready i think19:22
clarkbI'm not sure where the larger state of things is here but I want to note that I had a 100% image upload failure rate to rax when I tried to do that recently. Get an error 396 from the api in a jsob blob19:22
fungithough i discovered that diskimage-builder really, really doesn't like to preserve distro package caches19:22
jeblairfungi: awesome!19:22
jeblairfungi: has that been solved?19:22
fungigreghaynes apparently solved it a while back for the dpkg provider by giving us a toggle to turn off cache cleanup which i enabled a week or two ago, but this is still unsolved for the yum element19:23
*** aeng has quit IRC19:23
*** Berezin has joined #openstack-meeting19:23
fungii haven't had time to refactor its avoid-package-caching-at-all-costs bits so that they can hide behind an envvar19:23
fungibut that would be consistent with the fix in the dpkg element at least19:23
clarkb(I find this slighly funny because yum is so slow >_>)19:24
clarkbfungi: do we hvae to do it for the new fedora package manager too?19:24
jeblairfungi: do you still want to do that or see if anyone else wants it?19:24
clarkbwe should get someone familiar with that to weigh in and make sure we don't have yum preserving cahces just to have dnf nuke it19:24
fungiif someone else has time that would be a pretty trivial patch, it's all bourne shell19:24
*** yamamoto has joined #openstack-meeting19:24
jeblairanyone ^?19:24
ianwi can take a look19:25
fungiwell, s/trivial patch/neatly self contained task/19:25
jeblairwoo!19:25
fungithanks ianw!19:25
*** matrohon has joined #openstack-meeting19:25
jeblair#action ianw update yum dib element to support disabling cache cleanup19:25
*** vivek-e__ has quit IRC19:25
fungianyway, i have nova unit tests passing with the bindep fallback list on our minimal ubuntu-trusty workers via an experimental job19:26
jeblairfungi: what else do we need to do to start using bindep?19:26
*** vivek-ebay has joined #openstack-meeting19:26
fungiand am testing the addition of a custom bindep list in nova itself just to confirm that bit of the macro workes19:26
fungier, works19:26
*** harshs has quit IRC19:26
*** otter768 has quit IRC19:26
fungiwe still need minimal workers for anything we have bare-.* right now (precise is all that's left i think?)19:27
jeblair#info fungi testing bindep machinery with nova19:27
fungiand should do some similar tests on one of our centos-6 dib-built workers19:27
fungiand then we need to migrate/replace the jobs19:27
fungii believe mordred demonstrated an experimental job with devstack/tempest working on ubuntu-trusty instead of devstack-trusty19:28
fungibut last i heard multinode was still in a questionable state on those?19:28
fungiare the glean/hostname issues ironed out now?19:28
clarkbiirc they got smoke jobs working19:28
clarkbso need to switch to the full tempest runs and retest then we can switch19:29
*** ub has quit IRC19:29
*** markvoelker_ has quit IRC19:29
clarkbI cna write the patch to do that switch19:29
*** armax has joined #openstack-meeting19:29
*** yamamoto has quit IRC19:29
*** singleth_ has joined #openstack-meeting19:29
clarkbsorry the switch to full tempest19:29
mordredo hai19:30
jeblairwhat's the delta for us being fully-dib (regardless of whether we're using minimal or traditional images)19:30
fungibut yeah, moving jobs off devstack-.* is apparently a step for this now, unless someone can get dib-built devstack-.* images uploading into rax successfully19:30
clarkbthe glean/hostname issues should all be worked out as of yesterday (thank you pleia2 for approving that change)19:30
*** mestery has joined #openstack-meeting19:30
*** harshs has joined #openstack-meeting19:30
jeblairfungi: oh i guess that's a partial answer to my question? :)19:30
mordredfungi: I recommend against that19:30
mordredthe second thing19:30
mordredmoving jobs off devstack-* and on to the others is the next step19:30
fungiso i think it's either get glean integration for our devstack-.* images or move devstack-.* based jobs to the new glean-using images19:30
*** ub has joined #openstack-meeting19:30
*** radez_g0n3 is now known as radez19:30
clarkbmordred: fungi ewll the rax dib built image issue is a problem in either case right?19:31
jeblairwe are uploading minimial images to rax, right?19:31
mordredclarkb: yes19:31
clarkbjeblair: not reliably no19:31
*** singlet__ has joined #openstack-meeting19:31
*** pabelanger has joined #openstack-meeting19:31
fungii think the raw image size is biting us19:31
clarkbjeblair: and by not reliably I mean when I tried it I got 100% failure rate19:31
jeblairokay, so we're getting way ahead of ourselves19:31
*** vivek-ebay has quit IRC19:31
jeblairstep 1 is: get images uploaded to rax19:32
fungiand apparently transparent image conversion in glance was a fakeout. the facade is there but the plumbing was missing (i think that's in the process of being nailed down now?)19:32
jeblair(that's the end of my list)19:32
*** crc32 has joined #openstack-meeting19:32
*** singlethink has quit IRC19:32
*** KunalGandhi has quit IRC19:32
fungidib image uploads to rax _were_ working last i checked19:32
fungiwe just need glean instead of cloud-init and nova-agent19:33
mordredyah - I'm confused as to what broke - but I've been on vacation - I'll try to engage on that again tomorrow19:33
*** baoli has joined #openstack-meeting19:33
*** armax has quit IRC19:33
fungiyeah, i see ubuntu-trusty images ready in rax as of ~4.5 hours ago19:33
clarkbwe are anywhere from one hour to 24 days old on those images19:33
fungiabd centos-6 as well19:33
fungier, and19:33
clarkbfungi: its highly unreliable19:33
fungiokay, i haven't been watching it closely so i don't know whether today's a fluke19:34
*** armax has joined #openstack-meeting19:34
clarkbcentos6 is 1-3 days old19:34
*** singleth_ has quit IRC19:34
*** rbak has quit IRC19:35
clarkbmordred: retty sure its error 39619:35
clarkbwhich means rax failed19:35
*** numan has joined #openstack-meeting19:35
*** VanL has quit IRC19:35
fungiclarkb: oh, yep, i keep forgetting the age column format changed to include days19:35
jeblair1) investigate problem uploading images to rax 2) ensure we have minimal images of all operating systems 3) move jobs to use those images 4) drop snapshot and non-minimal-dib images from nodepool19:36
fungiso these images are random numbers of days old19:36
*** Piet has quit IRC19:36
jeblairis that the plan ^19:36
*** radez is now known as radez_g0n319:36
clarkbjeblair: sounds good to me19:36
*** numan has quit IRC19:36
jeblair#info a plan: 1) investigate problem uploading images to rax 2) ensure we have minimal images of all operating systems 3) move jobs to use those images 4) drop snapshot and non-minimal-dib images from nodepool19:36
fungiand yeah, i think the last theory i heard is that we're possibly either overhwelming the nodepool.o.o interface when uploading them all in parallel or we're running afoul of some upload throttle on the provider end19:37
*** armax has quit IRC19:37
jeblair#action mordred investigate problem uploading images to rax19:37
jeblairfungi: i thought we uploaded in series19:37
fungibecause when i test manually i can upload, but that's just one upload19:37
jeblairoh19:37
clarkbjeblair: we do19:37
jeblairgreghaynes was going to look into the nodepool dib worker....?19:37
clarkbbut its 16GB/chunk size uploaded in parallel iirc19:37
jeblairam i remembering correctly?19:37
clarkbmaybe we can force that to be serial too?19:37
fungihrm, then i guess it's not parallel uploads, unless something's gone wrong with our upload serialization19:38
mordredjeblair: if it's error 396 - we just need to retry the glance import19:38
mordredjeblair: and I either wrote a patch for that or thought about it19:38
clarkbjeblair: yes he is vacationing but has a working poc that runs worker on same host as nodepool daemon19:38
fungioh, right, chunk parallelization not image parallelization19:38
clarkbjeblair: iirc next step or that is to make it not depend on the database19:38
jeblairclarkb: cool19:38
fungiit's funny how all these seemingly unrelated projects are so intertwined19:38
jeblair#info greghaynes working on nodepool image build worker, poc in progress19:38
jeblairokay, i think we've synced up enough on this, at least, enough to know where we need to sync up more later.19:39
jeblair#topic Priority Efforts (Migration to Zanata)19:39
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:39
*** funzo has quit IRC19:39
jeblairhow's it going with the i18n team?19:39
*** ivasev has quit IRC19:39
AJaegerteam is slowly signing up.19:39
*** funzo has joined #openstack-meeting19:40
pleia2and they've been providing feedback that we19:40
pleia2're processing: https://etherpad.openstack.org/p/zanata-feedback19:40
*** annegentle has joined #openstack-meeting19:40
*** VanL has joined #openstack-meeting19:40
*** rbak has joined #openstack-meeting19:40
pleia2most of it is not really infra-specific, the service seems to run well, just evaluation of zanata itself and expectations around what it's supposed to do19:40
jeblairpleia2: any (a) infra potential-blockers or (b) zanata-itself potential-blockers?19:41
*** cbouch has quit IRC19:41
pleia2I think it's generally going well, I hope to sync up with people on list about the issues that have been raised to make sure we're closing all the feedback loops19:41
pleia2there are two major infra things outstanding19:41
*** funzo_ has joined #openstack-meeting19:41
pleia21. the upstream wildfly module is in heavy development on github, we should look at upgrading ours before a solid launch of the service19:42
jeblair#info zanata trial underway with i18n team19:42
*** funzo has quit IRC19:42
jeblair#link https://etherpad.openstack.org/p/zanata-feedback19:42
clarkbpleia2: the upstream puppet module?19:42
pleia22. thanks to nibalizer we now have the puppet-community/archive module on all our servers, which makes handling download, unzip, install a less horrible process, so we should use this for installing the server and client19:42
*** neelashah has joined #openstack-meeting19:42
pleia2clarkb: yep19:43
jeblairpleia2: those both sound tractable!19:43
pleia2#1 just needs testing of our deployment with the newer version, #2 needs me to rewrite our module to use archive19:43
pleia2totally, we're doing well19:43
fungii wonder if we could reapply that method to some other modules we have installing things from tarballs19:43
*** ayoung has joined #openstack-meeting19:44
jeblairwhat's the status of the "admins can make languages but we want our scripts to do it and not have admins" issue?19:44
pleia2fungi: yes19:44
*** jasondotstar has joined #openstack-meeting19:44
jeblairfungi: i read that as 'installing from terribles'19:44
mordredpleia2, nibalizer: should we take that archive work back out in to our other things that do a similar process?19:44
mordredoh19:44
mordredfungi: jinx19:44
fungijeblair: i thought it as "memories of slackware"19:44
pleia2jeblair: not "fixed" but our infra user now creates things and ultimately it's not a blocker, we're trying to just ignore it for now and tell the admins to behave19:45
*** sridhar_ram has quit IRC19:45
nibalizermordred: yes19:45
*** sridhar_ram has joined #openstack-meeting19:45
pleia2and infra user uses the api via scripts19:45
jeblairpleia2: what do we still have admins for?19:45
*** fzdarsky has quit IRC19:45
nibalizergetting away from exec { 'curl something': unless => 'something } is nice19:45
nibalizermuch more robust code19:45
clarkbworth noting I saw an email from transifex about some largish changes on their end. This may affect us. Does anyone know if we ar eaffected?19:45
*** angdraug has joined #openstack-meeting19:45
pleia2jeblair: adding new users to translations teams, admins have all kinds of powers that aren't grandular19:45
pleia2the translations team doesn't yet have a coordinator for every language, so an admin is needed to get people added where they belong19:46
jeblairok19:46
AJaegerclarkb: I looked at it and it looked not related to us at all. let's see19:46
pleia2AJaeger just brought that up to Daisy in an email earlier today19:46
fungipleia2: are those things that could conceivably driven from configuration management eventually?19:46
pleia2that == list of coordinators19:46
*** dneary has quit IRC19:46
clarkbAJaeger: they said paths were changing which I think may affect our use of the client and api?19:46
pleia2fungi: not sure yet19:46
*** rbak has quit IRC19:47
AJaegerclarkb: I thought it was only for the glossary which we do not use19:47
crinkle++ for archive instead of exec19:47
clarkbAJaeger: oh gotcha19:47
*** mpaolino has joined #openstack-meeting19:47
*** radez_g0n3 is now known as radez19:47
AJaegerclarkb: but if *every* path changes, we might need a new transifex - since we only communicate with the client.19:48
*** VW__ has quit IRC19:48
AJaegernew transifex *client* I mean19:48
jeblairi mean, we do need a new transifex, we just call it zanata19:48
jeblair;)19:48
pleia2hehe19:48
*** VW_ has joined #openstack-meeting19:48
jeblairon that note19:48
jeblair#topic Priority Efforts (Downstream Puppet)19:48
*** openstack changes topic to "Priority Efforts (Downstream Puppet) (Meeting topic: infra)"19:48
yolandanibalizer, i wanted to talk with you about the boilerplate changes19:49
nibalizeryolanda: okay19:49
yolandai see too much code repeated on each puppet project19:49
AJaegerjeblair: for sure!19:49
yolandacan we have it on a better way?19:49
jeblairasselin isn't here to talk about the openstackci part; but last i heard, it was pretty close and needed a sample manifest19:49
*** sridhar_ram has quit IRC19:49
nibalizerjeblair: thats correct19:49
nibalizerthere is a sample manifest up for review from asselin19:49
nibalizerthe puppet-httpd stuff is done or almost done19:50
jeblairand elsewhere, tons of changes in flight to refactor stuff out of system-config19:50
nibalizerI have a big set of simple patches https://review.openstack.org/#/q/status:open+puppet+message:beaker,n,z19:50
yolandafor nodepool, there is a chain of patches pending to land as well19:50
nibalizerfollow-on from puppet-httpd stuff will remove conditional logic added to make the transition possible19:50
*** ozstacker has quit IRC19:50
jeblairnibalizer: are we ready to start doing any public hiera stuff?19:50
yolandathere is some -1 for puppet_os_client_config19:50
nibalizerjeblair: ya19:50
nibalizerand I'd like to enable beaker tests on all infra modules (nonvoting) right now they don't run19:51
*** ijw has joined #openstack-meeting19:51
clarkb(did we get zuul cloner + beaker figured out?)19:51
*** novas0x2a|laptop has joined #openstack-meeting19:51
pabelangerI would mind some help reviewing open patches for fedora22: https://review.openstack.org/#/c/20372919:51
*** ozstacker has joined #openstack-meeting19:51
nibalizerclarkb: we did19:51
pabelangerbumping puppet-ntp to newer version19:51
jeblairare the openstackci patches19:52
jeblairer19:52
jeblairare the openstackci beaker jobs working again?19:52
nibalizerjeblair: no I think we have NOT_REGISTERED again/still19:52
pabelangerI have fixes for some of that19:52
nibalizerpabelanger: jeblair an explicit goal for us should be to update our versions of common libraries: mysql, stdlib, ntp, postgres etc19:52
jeblairnibalizer: they were registered, but they were failing because we were missing a build-dep; i made a patch for that which merged19:53
pabelangerthe NOT_REGISTERED is for a centos / fedora node. Which, is just waiting for +A19:53
*** VW_ has quit IRC19:53
jeblairnibalizer: why do we want to upgrade those libraries now?19:53
pabelangerhttps://review.openstack.org/#/c/205668/ is review19:53
jeblairnibalizer: can that wait until we accomplish some of the other outstanding work?19:53
nibalizerjeblair: yea we can wait on it19:54
AJaegerjeblair: gate-infra-puppet-apply-devstack-centos7  is still NOT_REGISTERED19:54
*** mpaolino has quit IRC19:54
nibalizerjeblair: I feel a need, to be 'ready' for infra cloud19:54
pabelangerAJaeger: patchset I linked fixes that19:54
*** Berezin has quit IRC19:54
*** Berezin has joined #openstack-meeting19:54
jeblairpabelanger: that's puppet-apply, not beaker19:54
nibalizerI expect at some point crinkle or spamaps will be like 'okay lets add the puppet-openstack stuff to system-config' and we'll run into module incompatiblity on those libraries19:54
jeblairwhich is still important19:55
crinkleif we have masterless puppet working then there's less need to have modules updated for infra cloud19:55
pabelangerAJaeger: you linked the puppet-apply job19:55
*** julim has quit IRC19:55
pabelangerAJaeger: oops19:55
nibalizernow we've discussed this before, and a number of workarounds have been suggested, but I think the best thing is to just get our stuff current19:55
crinkleand iirc mordred was hoping to have masterless puppet first/soonish19:55
mordredyes. I want masterless puppet. I got busy. I'm sorry!19:55
pabelangerjeblair: right. I looked at a beaker today, seemed like it worked19:55
*** elo1 has joined #openstack-meeting19:55
*** ijw has quit IRC19:56
*** topol has quit IRC19:56
crinklenibalizer: even if we get modules updated there are bound to be some kind of incompatibility with the openstack modules and the infra modules19:56
jeblair#action nibalizer add beaker jobs to modules19:56
jeblair#action nibalizer make openstackci beaker voting if it's working (we think it is)19:56
jeblairnibalizer: ^ i took a liberty there :)19:56
*** pnavarro has joined #openstack-meeting19:56
pabelangernibalizer: Ya, I want to get them upgraded too.19:56
greghaynesWhile im doing a bad job of vacationing - yep, ive been messing with nodepool dib workers, ive gotten it pretty far along with nodepool spawning workers when it launches and having upload and build triggered by gearman. I also noticed that out ubuntu-trusty images in rax are not resizing to use the fool disk space which was causing our devstack tests to fail on them.19:57
nibalizerjeblair: right now the testing is quite cowardly... I'm not sure if you'd rather a coward vote or a hero nonvote19:57
pabelangernibalizer: maybe a periodic job to test master modules too (or something)19:57
jeblairi don't think upgrading for the sake of upgrading is our highest priority19:57
greghaynes(sorry for the out of context)19:57
*** elo has quit IRC19:57
clarkbjeblair: I agree19:57
nibalizerjeblair: thats fair19:57
*** KunalGandhi has joined #openstack-meeting19:57
*** olaph has quit IRC19:58
jeblairi'd much rather get things like masterless puppet, in-tree hiera, real testing, etc. in place, then upgrade either when we need to or run out of other things to do :)19:58
nibalizeryea19:58
yolanda++19:58
*** KunalGandhi has quit IRC19:58
jeblairnibalizer: coward vote and expand as it becomes less... cowardly19:58
pabelangerupgrade for me, are to add fedora22 support. Mind you, only a few modules right now that are lacking it19:58
nibalizer#action nibalizer create first in-tree hiera patchset19:58
nibalizeroh i cant do that19:58
*** olaph has joined #openstack-meeting19:58
*** Berezin has quit IRC19:58
jeblair#undo19:58
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0xad8f290>19:58
jeblairnibalizer: why not?19:59
yolandai could take it if i get some background19:59
jeblair(that made me really happy)19:59
nibalizeroh i thouht no-response from the bot meant I didn't have bot-acls to add it19:59
jeblair(and undoing it made me really sad)19:59
pabelangerif mordred has script going, I can help with masterless puppet launcher.19:59
nibalizeri'm happy to do that work it only about ~5 minutes19:59
jeblairnibalizer: oh, you can totally do that19:59
jeblair#action nibalizer create first in-tree hiera patchset19:59
jeblairit never responds to actions, links, infos19:59
nibalizerahhh20:00
jeblaircool, we're out of time, but i think we got through all the priority things20:00
nibalizerwoot20:00
jeblairbacklog next week20:00
jeblairthanks everyone, especially those i put on the spot today! :)20:00
jeblair#endmeeting20:00
*** openstack changes topic to "BP (Meeting topic: tricircle)"20:00
openstackMeeting ended Tue Jul 28 20:00:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-07-28-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-07-28-19.01.txt20:00
*** yolanda has left #openstack-meeting20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-07-28-19.01.log.html20:00
*** AJaeger has left #openstack-meeting20:00
flaper87o/20:00
markmcclaino/20:01
*** pabelanger has left #openstack-meeting20:01
jeblairttx: pls hold on meeting start20:01
*** olaph has left #openstack-meeting20:01
ttxholding20:01
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
*** mrmartin has joined #openstack-meeting20:01
jeblairttx: all clear, thx20:01
ttxAnyone here for the TC meeting ?20:01
*** adreznec has left #openstack-meeting20:02
mordredo/20:02
flaper87o/20:02
jeblairo/20:02
* mordred is also in board meeting - so will be laggy20:02
dhellmanno/20:02
lifelesso/20:02
russellbo/ kind of20:02
edleafeo/20:02
annegentlehere20:02
fungijeblair: i fixed the topic in -3 just now as well20:02
sdagueo/20:02
fungiso they're all set again20:02
jeblairfungi: thx20:02
annegentlehow are you kind of here russellb :)20:02
*** VW_ has joined #openstack-meeting20:02
* flaper87 wonders where long-arms-jaypipes is20:02
redroboto/20:03
dougwigflaper87: long-arms?20:03
*** neelashah has quit IRC20:03
ttxjgriffith, dtroyer, markmcclain, jaypipes: around ?20:03
edleafeflaper87: he said he had an all-day meeting today20:03
markmcclainstill here :)20:03
ttx#startmeeting tc20:03
*** rbak has joined #openstack-meeting20:03
openstackMeeting started Tue Jul 28 20:03:30 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
flaper87edleafe: aww :(20:03
ttxmarkmcclain: doh!20:03
* flaper87 is back20:03
ttxOur agenda for today:20:03
edleafeflaper87: maybe he'll peek in at some point20:03
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:03
*** gordc has joined #openstack-meeting20:04
ttx#topic Add Stackforge Namespace Retirement resolution20:04
*** openstack changes topic to "Add Stackforge Namespace Retirement resolution (Meeting topic: tc)"20:04
ttx#link https://review.openstack.org/19201620:04
ttxI think we are getting nearer with the latest version of this resolution20:04
ttxNo more objections from my side... anyone else ?20:04
ttxif not, review could use MOAR votes20:04
jeblair++votes20:04
sdague+R20:05
ttx2 more and we can pass it in-meeting20:05
*** witek has quit IRC20:05
sdagueok, so moving on? seems like votes can tally when they tally20:05
* devananda lurks20:05
*** Shrews has left #openstack-meeting20:06
jeblairbtw, the pecan folks have decided to leave regardless of this (related to CLA issues and our platform support)20:06
ttxsure20:06
jeblairit's a friendly parting20:06
*** alexpilotti has joined #openstack-meeting20:06
ttxbut we are at 7 so I guess we can approve it now20:06
sdagueI guess that's a question, does everything in openstack need CLA check box?20:06
jeblairsdague: pecan actually does not20:06
jeblairhave it now20:06
sdaguejeblair: right, we never required it on stackforge20:06
jeblairbut it's pretty impossible to convey that to a contributor20:07
ttxapproved20:07
*** _nadya_ has joined #openstack-meeting20:07
ttx#topic Introduce the "deliverables" concept20:07
*** openstack changes topic to "Introduce the "deliverables" concept (Meeting topic: tc)"20:07
sdaguejeblair: I was more thinking after the namespace is gone20:07
dhellmannjeblair: is it possible to activate a gerrit account without signing the cla?20:07
ttx#link https://review.openstack.org/20258320:07
jeblairsdague: ack dhellmann: yes20:07
ttxI refreshed this one yesterday based on the current repository status20:07
flaper87jeblair: cool!20:07
dhellmannjeblair: ok, cool, I never tried :-)20:07
ttxAnd added the related tooling changes so that it passes tests20:07
ttxSo it should be ready for adoption, before it gets into further merge conflicts20:07
ttx(Note that I'll update the other changes that will get wedged by this change merging)20:07
ttxso that would be great to mertge it now before it gets out of date again, if you agree with it20:08
dhellmann++20:08
* flaper87 has no objections20:08
sdaguettx: so... that seems like a giant list to be kept accurate by TC, I think my only concern is I'd like to figure out a way that we're not handling 4 updates to projects.yaml every meeting20:08
*** mestery has quit IRC20:08
ttxmore updates to projects.yaml happen off-meeting20:09
dhellmannI think we really only need to approve additions or removals to the list, right?20:09
lifelessI'd like to make project based updates to project.yaml be single-+2A20:09
ttxlifeless: they are "one week, no objection"20:09
sdaguelike, what's there is fine, but I'm mostly not going to vote on random changes on project.yaml in the future20:09
lifeless'neutron added a repo' isn't something we conceptually vote on20:09
annegentlesdague: yeah20:09
*** KunalGandhi has joined #openstack-meeting20:09
dhellmannlifeless: we have to be careful, because adding repos == adding voters, and we want to make sure we're doing that appropriately20:09
ttxlifeless: you don't20:09
lifelessttx: k20:09
jeblair20:09
jeblairOnce a project has joined OpenStack, it may create additional source code repositories as needed at the discretion of its Project Team Lead (PTL) without prior approval from the TC as long as the additional source code repositories fall within the scope of the approved project mission statement.20:09
jeblairlifeless: ^ http://governance.openstack.org/reference/new-projects-requirements.html20:10
flaper87didn't we agree on letting some of this addition mature for a week and approve without meeting if no objections were raised ?20:10
ttxsdague: I actually handle most projects.yaml changes after letting them mature for a week unless there are objections20:10
lifelessjeblair: yes, exactly20:10
ttx(as long as the PTL approves it)20:10
sdaguettx: so... can you tag all those procedural ones with ProceduralChange or something20:10
*** ivar-lazzaro has quit IRC20:10
lifelessjeblair: what I mean is that the land-the-metadata-change-mechanics shouldn't require multiple votes from the TC20:10
sdagueso that I can filter it out of my reviews20:10
ttxsdague: tag them ?20:10
lifelessjeblair: and it sounds like we've already established that20:10
sdagueadd a thing to the commit message20:10
flaper87ttx: commit-tag20:10
*** rbak has quit IRC20:11
*** ivar-lazzaro has joined #openstack-meeting20:11
ttxsdague: sure, I could do that20:11
jeblairwell, 202583 is worth voting on, right?  we're introducing a concept?20:11
sdaguettx: cool20:11
ttxjeblair: yes20:11
sdaguejeblair: yes20:11
lifelessjeblair: yes, of course20:11
sdaguebut now there is a ton of data in there, so I wanted to make sure keeping that data fresh is more expedited in the future20:12
jeblairttx, sdague: how about a topic so it doesn't require a patchset update?20:12
flaper87jeblair: that works too20:12
sdagueanything I can build a gerrit filter for, I'm happy20:12
dhellmannjeblair: ++20:12
*** alexpilotti has quit IRC20:12
ttxjeblair: something like project-update20:12
sdaguemechanism unimport to me beyond that20:12
ttxor not-a-vote20:12
ttx#action ttx to pick a topic name to tag all things that don't require a formal TC vote20:13
sdaguettx: thanks20:13
ttx(a.k.a. "project list updates")20:13
ttxsdague: we already had those, there was just no way to quickly tell them apart20:13
*** KunalGandhi has quit IRC20:13
ttxthat will help with building the meeting agenda too.20:13
*** baoli has quit IRC20:14
lifelesssdague: devstack tags - how about 'internal/external' or someting ?20:14
*** ijw has joined #openstack-meeting20:14
ttxlifeless: next topic20:14
lifelessttx: yes :)20:14
ttxSince we generate a giant merge conflict with that one anyway, I propose we fast-track the alphabetical reorder20:14
*** baoli has joined #openstack-meeting20:14
ttx#link https://review.openstack.org/#/c/206460/20:14
ttxit's a no-vote change20:14
dhellmann+120:14
ttxwill approve now unless someone screams BAD IDEA20:14
* flaper87 voted anyway20:15
lifelessdoit20:15
jeblairgood idea.  i'm pretty much just going to trust that's right.20:15
sdaguettx: it would be good to add tooling to enforce it stats alphabetic later20:15
sdagueandreas did some of that for infra files20:15
jeblairsdague, ttx: there's some tooling in project-config you can borrow20:15
ttxsdague: good idea20:15
sdaguejeblair: yep ++20:15
*** ub2 has joined #openstack-meeting20:15
*** Apoorva has quit IRC20:15
*** pm90__ has quit IRC20:15
*** MarkAtwood has quit IRC20:15
*** pm90_ has joined #openstack-meeting20:16
ttx#action ttx to rebase all current patches on top of his giant change20:16
*** igordcard has joined #openstack-meeting20:16
ttxthere might be off-governance tooling that will be caught unaware of the projects.yaml format change. Let me know if you spot any20:16
dhellmannthere are a couple of scripts in release-tools, but I can fix those tomorrow20:16
ttxfungi: the election roll tooling will likely need an update20:16
ttxok, next topic20:17
ttx#topic Add devstack tags20:17
*** openstack changes topic to "Add devstack tags (Meeting topic: tc)"20:17
*** rbak has joined #openstack-meeting20:17
ttx#link https://review.openstack.org/20378520:17
fungithanks ttx20:17
ttxsdague: care to introduce this/these ?20:17
*** ub has quit IRC20:17
sdaguesure, so basically it seemed useful to actually annotate what projects have facilities to come up in devstack20:17
sdaguebe it in the devstack tree, or via our published plugin interface20:18
sdaguethe whole conversation started on the mailing list earlier this month20:18
annegentleI like the integration:thing-its-integrating-with20:18
sdagueI think the tag(s) are pretty self explanatory, naming is a thing20:18
*** merooney has quit IRC20:19
ttxsdague: there is the open question of the value of having seperate tags for mainline and plugin20:19
sdagueyeh, integration: seems fine20:19
flaper87would it be enough to just have devstack:plugin-name ?20:19
*** e0ne has quit IRC20:19
flaper87instead of distinguishing between upstream/downstream20:19
ttxbased on the rationale ("Knowing which components are easily brought up in [devstack] environment") I'm not sure it needs the distinction20:20
sdagueflaper87: how would you tag keystone in that way?20:20
jeblairso the one-tag variant is something like: "integration:devstack" says "this thing works with devstack", and if you want to know how, you can check the docs...20:20
flaper87sdague: plugin-name would be whatever you use to enable it in devstack20:20
lifelessI quite like that20:20
lifelessdo people actually ask about *how* ?20:20
ttxjeblair: I fear that it puts pressure on devstack people to get things mainline, while we push the other way around20:20
*** jaypipes has quit IRC20:20
sdagueflaper87: so, for nova, you don't have a single thing like that20:20
jeblairttx: oh, but "integration:devstack" applies to plugins too20:21
lifelessas-in, do we negatively affect people if we don't document the plugin/included status ?20:21
flaper87sdague: could we have one? AFAIK (please correct me) most projects do20:21
*** e0ne has joined #openstack-meeting20:21
flaper87s/we/it/20:21
sdaguehonestly, specifying it's a plugin20:21
sdagueis kind of useful to people20:21
ttxjeblair: right20:21
sdaguebut, that's from a devstack support perspective20:21
sdagueand I also imagined who acks the patch is different in the 2 cases20:21
*** e0ne has quit IRC20:21
sdaguebecause project cores should be able to ack the fact that they have a bit now20:22
flaper87I kinda think we should now have a repo to keep track of devstack plugins + urls (or something like that)20:22
lifelesswell20:22
dhellmannhow about one tag that means there is any form of integration, and another tag that says the integration is not built into devstack itself?20:22
flaper87but that's basically what this tag is for20:22
annegentlelifeless: the negative effect being what though?20:22
ttxI could go either way20:22
* flaper87 just thought this through a bit better20:22
*** julim has joined #openstack-meeting20:22
lifelessmaybe devstack could lookup the repo based on the name and pull it in automagically. But thats a devstack dev question.20:23
lifelessannegentle: well - like sdague said20:23
*** mtanino has quit IRC20:23
jeblairlifeless: it just about already does that20:23
markmcclainttx: I've got to head out for a presentation... if a real time vote pops up today... dhellmann can proxy for me20:23
ttxmarkmcclain: ack20:24
* dhellmann gets out a second keyboard20:24
*** topol has joined #openstack-meeting20:24
sdagueright, personally, I'd feel more comfortable if it was 2 tags because of the support question. Because the amount of devstack plugins exceeds the number of things in the devstack tree, and would like to prevent tears prematurely when people ask me why their opendaylight doesn't work in devstack (for instance)20:25
annegentle"There's no crying in baseball!"20:25
annegentleright sdague I see what you mean.20:25
ttxIf we get the plugins discoverable from devstack, I don't think the extra information saying "as a plugin" is worth it20:25
lifelessbut they aren't todau20:25
dhellmannI see this as sort of parallel to the release tags, where we have a "managed" tag and several "model" tags20:25
lifelessso lets refactor if/when it is20:25
sdagueright, but that then means that devstack needs to maintain an authoritative registry20:25
sdaguewhich, sort of goes against the whole big tent thing20:26
*** pm90_ has quit IRC20:26
*** funzo_ has quit IRC20:26
lifelesssdague: well no - it could infer from the name20:26
sdagueI was actually trying to push this out to the edges20:26
sdaguelifeless: some times20:26
ttxsdague: if it doesn't (or won't in the near future) then I agree that "as a plugin" is valuable piece of info20:26
flaper87and which is part of what this tag tries to address20:26
dhellmannso if there's an "integration:devstack" tag to indicate support at all, and then a "devstack:external-plugin" tag to indicate that the code doesn't live in devstack, I think we'd express everything20:26
*** baoli has quit IRC20:26
jeblairi'm just thinking back to the "tags replacing docs" thing, and documenting the specific mechanism you use to devstack something seems to have crossed the line from "new user browsing the software site" to "deployer actually trying to run commands"20:26
flaper87I think it's a valuable info now20:26
flaper87it might not be needed anymore in the future20:26
sdaguejeblair: maybe20:26
ttxjeblair: yeah20:27
sdague*a lot* of people bring up devstack to test things20:27
sdagueit's actually the first experience a lot of users have with openstack20:27
*** rbak has quit IRC20:27
ttxjeblair: maybe "there is a way to run in devstack" is enough as far as tags are concerned20:27
*** pm90_ has joined #openstack-meeting20:27
sdaguettx and then when they ask "and that way is... "20:28
sdaguewhere do they go?20:28
annegentledoes devstack integration indicate any test integration?20:28
ttxsdague: if they don't find it mainline, they look for a plugin?20:28
sdaguettx: and how do they look for that?20:28
flaper87the thing is that even when the 'as-plugin' info, they won't know exactly20:28
dhellmannttx: I'm not sure new users would know about plugins as a thing20:28
jeblairannegentle: hopefully?  most of the projects with plugins should run devstack tests on them20:28
flaper87because there are plugins outside repos anyway20:28
ttxsdague: devstack:as-plugin doesn't exactly point to a repo either20:28
flaper87I mean, devstack plugins in their own repos20:28
sdaguettx: yes it does, it's the repo that's tagged20:29
annegentlejeblair: ok20:29
dhellmannsdague: if I was looking, frankly I would look at the devstack docs, so I wonder if there should just be a registry there20:29
ttxsdague: is it ?20:29
sdaguettx: yes20:29
annegentledhellmann: sdague: you could also look at the tag list and say, "Oh, I should work on devstack integration"20:29
sdaguesorry if that wasn't clear20:29
dhellmannI'm not sure it's any more of a burden to keep the docs up to date than the governance list20:29
* ttx reads deeper20:29
flaper87sdague: how would that tag work for  https://github.com/openstack/devstack-plugin-zmq ?20:29
* flaper87 confused now20:30
sdagueI'm so knee deep in this, I forget what people don't know20:30
dhellmannannegentle: yeah, that's why I think it's useful to have an integration:devstack tag20:30
*** Apoorva has joined #openstack-meeting20:30
sdaguelike openstack/trove => integration:devstack-plugin20:30
dhellmannsdague: we just approved a patch that moved tags from repos to deliverables20:30
ttxsdague: ok, I thought they might live in a specific repo, but if they are always bundled with the code... that works20:31
flaper87how would that tag work for  https://github.com/openstack/devstack-plugin-zmq ?20:31
sdaguettx: they can also live off in other repos20:31
dhellmannsdague: is that always true? I thought the oslo.messaging stuff ended up in its own repository?20:31
lifelessso is each neutron aas plugined separately?20:31
dhellmannflaper87: right, that20:31
sdaguelifeless: yes, they will be20:31
*** salv-orlando has joined #openstack-meeting20:31
ttxsdague: then the tag applies to the devstack plugin ? or the code that has devstack integration ?20:31
*** jaypipes has joined #openstack-meeting20:31
lifelessso this tag is going to be repo then, not deliverable20:31
flaper87oslo.messaging has several drivers and plugins for each20:31
flaper87these plugins live outside the repo20:32
*** glauco has quit IRC20:32
ttxlifeless: there are no such things anymore20:32
flaper87and there's also an in-repo plugin, IIRC20:32
lifelessttx: and yet20:32
*** glauco has joined #openstack-meeting20:32
*** armax has joined #openstack-meeting20:32
sdagueso, for stuff that lives outside the repo, I don't know. I was thinking about this in terms of "I want to use designate, does it come up"?20:32
*** stanchan has quit IRC20:32
ttxlifeless: hence my question, I think the "has devstack integration" tag should apply to the thing that has devstack integration, which may be multiple repos20:32
ttxnot to the thing that contains devstack plugin code20:33
dhellmannI understand that we need a registry of where those plugins are, but I'm starting to doubt that the governance project list is that registry.20:33
flaper87I'd say, lets just say it has support for devstack for now and forget about the plugin bit until we find a good solution for that20:33
dhellmannI like integration:devstack for the deliverable, and then more details in the deliverable docs or the devstack docs (or both)20:33
ttxflaper87: ++20:33
dhellmannflaper87: ++20:33
ttxsounds like a good first step anyway20:33
lifelessttx: but neutron having devstack integration doesn't mean that all the aas's are enabled20:33
lifelessfor instance20:33
lifelessso I guess I'm wondering if thats going to mislead20:34
sdagueok, I'm fine just tagging the devstack in tree bits20:34
dhellmannlifeless: right, figuring out how to express that is more than a tag20:34
sdaguethat's a step 120:34
ttxlifeless: they should, otherwise publishing them as a single "thing" may be confusing anyway20:34
dhellmannsdague: no, I think we want a tag that says "has some devstack integration" and does not distinguish here20:34
*** salv-orl_ has quit IRC20:34
flaper87dhellmann: ++20:34
sdagueok, well I don't want that20:34
sdaguebecause of support issues20:34
lifelessttx: should doesn't make it actually happen though20:34
lifelessso its seeming to me that either we need to bring back per repo tags20:35
ttxlifeless: we could say the tag doesn't apply if only part of the deliverable gets devstack-integrated20:35
dhellmannsdague: can that not be solved by documentation within devstack itself?20:35
*** cp16net has joined #openstack-meeting20:35
lifelessor find some other way of communicating what (I think) sdague wants to communicate20:35
*** MarkAtwood has joined #openstack-meeting20:35
dhellmannsdague: i.e., list what is in tree, and describe how to find the out-of-tree stuff20:35
dhellmannwithout making an exhaustive list ("look for a directory named foo" or "look at the contributor docs for the project")20:36
sdaguedhellmann: that then implies that it is the role of the devstack team to categorize the universe, vs. the project registry to be a place for information about that to be stored20:36
dhellmannsdague: no, you only have to list the things you support in your tree, which you could do automatically20:36
*** puranamr has quit IRC20:36
flaper87sdague: just tell people what's in-tree20:36
fungihrm, that means maybe we should remove the vulnerability:managed tag from, e.g., the neutron deliverable. it was applied to the openstack/neutron repo previously but not the other repos which just got glommed on today20:36
lifelesssdague: is it possible to write an oracle that takes git tree in and returns 'has devstack plugin:TRUE|FALSE' ?20:36
jeblairyeah, i also don't think that only tagging things in devstack is a good idea -- it could increase pressure (and of all the things we have discussed, that's the thing that could be _most_ served by a devstack-maintained list)20:37
flaper87each project should do its best to let others know where to find the devstack plugin20:37
dhellmannand then give general guidance for how to find the other stuff by directing them to ask the project team20:37
*** _nadya_ has quit IRC20:37
flaper87if I need a plugin for X, I'd probably look in devstack -> project repo -> wherever the project repo tells me to go20:37
ttxfungi: maybe the -*aas should be split if they are so different20:37
fungisort of sad i missed the implication of the deliverables discussion now20:37
sdaguelifeless: I could probably20:37
*** _nadya_ has joined #openstack-meeting20:37
flaper87that's something that the 'is-plugin' bit doesn't fix anyway20:37
sdaguelifeless: to a 95% accuracy at least20:37
lifelesssdague: so I'm wondering if something could take teh repo list in, scan all the repos, and provide data back to governance (or wherever) automatically20:37
sdaguesure20:38
ttxfungi: technically they were once in openstack/neutron and got split though20:38
fungiwell, thinking in terms of "tag only applies to a deliverable if all repos within the deliverable are covered" suggestion20:38
*** penick has quit IRC20:38
flaper87lifeless: there are plugins outside repos that wouldn't be listed20:38
jeblairttx, fungi: i think the model is good; we probably need to reconcile whether we fix this by supporting more repos or saying that "neutron" isn't supported because it's so complex20:38
flaper87unless they use submodules20:38
fungibut similar concerns as qa will have with devstack support i think20:38
flaper87or some sort of agreed listing model20:38
annegentlejeblair: yeah that's the concern, complexity drowning20:38
sdagueright, qa will not support vpnaas20:38
lifelessflaper87: would they be able to move to being in repos?20:38
sdaguebut does support neutron20:38
sdagueif that is not an expressible thing20:39
sdaguethat's kind of problematic20:39
flaper87lifeless: in some cases, maybe. In other cases, it's unlike (vendor specific plugins)20:39
ttxsdague: it is if we split neutron-*aas from the neutron deliverable20:39
sdagueI guess I also missed this issue on the deliverable side20:39
ttxsdague: since it looks like it's a different "thing"20:39
jeblairi think our side-track is getting side-tracked20:39
*** lexholden has joined #openstack-meeting20:39
ttxyep20:39
flaper87jeblair: lol20:39
sdaguejeblair: sure, but I think this is part of the confusion about what kind of information shows up here20:40
ttxOK, I suggest we give it some thought and comment on the review20:40
flaper87ok, I think this need more work/discussion20:40
annegentleagreed20:40
flaper87I'll comment on the review with my thoughts20:40
flaper87lets move on20:40
lifelessflaper87: vendor specific plugin wouldn't be in vendor specific codebase?20:40
sdaguebecause things like upgrade modes get impacted as well20:40
ttxno point is running for 10 more minutes in circles20:40
* zaneb was bout to comment but will take it to the review20:40
fungiwell, applicability of previously per-repo tags is coming into question, so seems on-topic to the devstack tag discussion20:40
*** MarkAtwood has quit IRC20:40
*** GB21 has quit IRC20:40
*** TravT has joined #openstack-meeting20:40
fungibut agreed probably better in review20:40
ttx#topic Add and apply guidelines for project and service names20:40
*** openstack changes topic to "Add and apply guidelines for project and service names (Meeting topic: tc)"20:40
sdagueyeh, we can collect there, figure out what questions to ask for next week20:41
ttx#link https://review.openstack.org/20116020:41
flaper87lifeless: yes but they are still plugins that I might want to use and therefore I'd like to find easily. An automated tool would ignore those plugins. For example: https://github.com/openstack/devstack-plugin-zmq20:41
ttx#link https://review.openstack.org/20167020:41
ttxannegentle: where are we now with this one ?20:41
*** mtanino has joined #openstack-meeting20:41
* flaper87 stays on topic20:41
*** alexpilotti has joined #openstack-meeting20:41
annegentleI'll have to rebase after the alphabetization20:41
annegentlebut I updated today with the key management v key manager update20:41
*** _nadya_ has quit IRC20:41
*** Tross has quit IRC20:41
*** gordc has quit IRC20:41
annegentledocs team is informed.20:41
annegentlethat's about it20:42
lifelessflaper87: that looks like it would be discovered actually20:42
dhellmannannegentle: I'm still a little worried that the zaqar description is too terse, but we can iterate on that separately20:42
flaper87lifeless: ah ok, lets talk about it offline (or in 2 days :P)20:42
lifelessflaper87:kk20:42
dhellmannannegentle: specifically, differentiating zaqar and cue20:42
annegentledhellmann: yeah I get it.20:42
*** baoli has joined #openstack-meeting20:42
flaper87dhellmann: yeah, I was worried about that as well but I didn't comment because that would require changing cue as well20:42
*** zzz_pczesno has joined #openstack-meeting20:43
flaper87and probably other projects20:43
annegentledhellmann: ayup20:43
dhellmannunfortunately, I don't have a constructive suggestion right now :-/20:43
*** wznoinsk1 has joined #openstack-meeting20:43
flaper87I  was thinking to propose a follow up patch with a better descriptio20:43
*** mestery has joined #openstack-meeting20:43
flaper87description20:43
annegentleflaper87: do the rules generally work except for messaging queues?20:43
flaper87one for each project so we can track the change20:43
annegentleflaper87: sure20:43
*** wznoinsk has quit IRC20:43
annegentleany other naming concerns?20:44
flaper87annegentle: If we all imagine there's 'Service' at the end, I believe it does. Otherwise, it's a bit terse for every project.20:44
sdague'Governance'20:44
*** MarkAtwood has joined #openstack-meeting20:44
flaper87my main worry right now is that Message and Message broker will cause confusion20:44
sdaguejust because http://governance.openstack.org/20:44
ttxsdague: yeah that one is pretty bad20:44
*** pczesno has quit IRC20:44
annegentleflaper87: yeah the idea is to add service everywhere.20:44
*** puranamr has joined #openstack-meeting20:44
dhellmannsdague: yeah20:44
sdaguewhich, you know, is in no way related20:44
dhellmannsdague: maybe we can get the congress team to review the minor projects.yaml changes?20:45
jeblairyeah, actually, i'm pretty sure the TC is reposnsible for implementing governance as a service20:45
annegentleDelta faucets, Delta airlines20:45
dhellmannannegentle: note that you needed 2 words to differentiate those companies :-)20:45
lifelessGaas20:45
annegentle:)20:45
*** elmiko has joined #openstack-meeting20:46
*** okrieg has quit IRC20:46
ttxso.. let's accumulate reviews and patchset on that one ?20:46
annegentlettx: yep, I'll rebase and keep asking people to take a look20:47
ttx#topic Add a release model for all projects20:47
*** openstack changes topic to "Add a release model for all projects (Meeting topic: tc)"20:47
ttx#link https://review.openstack.org/20172420:47
*** funzo has joined #openstack-meeting20:47
ttxWe are still gathering information on this one20:47
ttxdhellmann: Starting to wonder if smaller incremental patches would not lead to faster improvements there20:47
ttxnot sure we have anything TC to discuss about it20:47
dhellmannttx: yeah, I'll split that up next week20:47
ttxcool20:47
ttx#topic Diversity script improvements20:47
*** openstack changes topic to "Diversity script improvements (Meeting topic: tc)"20:47
ttxWe have two improvements around the diversity script20:48
ttx#link https://review.openstack.org/20437220:48
ttx#link https://review.openstack.org/20477020:48
ttxI propose to approve those "code" reviews once they get two rollcall+1 votes20:48
ttxsince they are not governance either20:48
flaper87++20:48
ttxand not spend meeting time on them20:48
ttx#topic Workgroup reports20:48
*** openstack changes topic to "Workgroup reports (Meeting topic: tc)"20:48
ttx* Project team guide20:48
ttxSo we have almost everything we need to publish in20:49
ttxOnly missing the open development chapter20:49
flaper87I swear I'll get my part done20:49
flaper87I'll do it on my flight tomorrow20:49
flaper87and plublish it20:49
ttxflaper87: sounds good -- post what you have20:49
* flaper87 is so ashamed20:49
ttxjeblair: will you be working on the publication jobs ? Maybe you have already and I missed them20:49
jeblairttx: i will20:49
ttxjeblair: thx!20:49
ttx* Next-tags20:49
jeblairttx: i'm currently hiding behind flaper87.  ;)20:49
ttxTeam will gradually post new tags over the coming weeks.20:50
ttxThe devstack tags proposed by sdague are an early manifestation of that20:50
* flaper87 starts jumping20:50
ttxsdague is just faster than us slackers20:50
ttx* Communications20:50
ttxannegentle, flaper87: maybe we should include this TC in the next blog post ?20:50
flaper87yeah20:50
ttxi.e. the conclusion of the stackforge thing20:50
flaper87and do a single post20:50
flaper87the stackforge thing is important20:50
annegentlesure, next week ok?20:50
ttxwell, next week we might have more to post :)20:51
dhellmannflaper87: the stackforge thing might be worth a separate post entirely20:51
ttxrelease early, release often!20:51
annegentleyeah, I'm thinking stackforge is a separate post, not a highlights one20:51
ttxdhellmann: not sure20:51
annegentleI can think of questions about it that someone could answer for the post20:51
ttxannegentle: the change is a technical one, not a governance one20:51
flaper87we can make a longer post this time that gives enough information about stackforge20:52
*** alexpilotti has quit IRC20:52
*** amitgandhinz has quit IRC20:52
ttxI'm not sure we need to make a separate post... we just rename repos20:52
* dhellmann shrugs20:52
annegentleHow will I be notified of the move? What's the timeline for renames? What if no one is maintainer, what happens?20:52
ttxi don't want people to start making up their own idea of what "moving under openstack namespace" means20:52
annegentle(I have a no-one-is-maintainer repo in there)20:53
*** fzdarsky has joined #openstack-meeting20:53
edleafeI tried explaining this to people. They are confused about it20:53
jeblairannegentle: i expect the infra team to come up with a plan that addresses that20:53
*** IlyaG has joined #openstack-meeting20:53
annegentlejeblair: I think that a blog post should be part of that comm plan20:53
edleafeI tried explaining this to people. They are confused about it20:53
dhellmannannegentle: ++20:53
edleafeugh20:53
annegentleedleafe: heh20:53
ttxannegentle: I guess as long as the post clearly says it's just a repo rename, it's not "moving all of Stackforge into OpenStack" that's good20:54
edleafetyping in two windows == bad20:54
dhellmannttx: ++20:54
ttxI have enough big-tent haters sending me things20:54
lifelessttx: orly?20:54
dhellmannwe have a nice shiny yaml file to point to as the list of official projects20:54
ttxlifeless: it's more of a "hit me at conference about how much the whole idea sucks" kind of thing20:54
zanebI really don't understand big-tent haters20:54
lifelessttx: totes20:55
annegentleso, do you think we need a highlights post this week or is next ok?20:55
ttxzaneb: it's mostly that they don't get it, but misinformed people / press will make headlines out of small things20:55
*** glauco has quit IRC20:55
zanebyeah, I know20:55
zanebbut how hard can it be to just ignore the parts you don't care about?20:56
sdagueit's a less informed version of the same pov that wanted a starter kit. If openstack is 100 projects, people feel intimidated about where to start20:56
*** ccavanna has quit IRC20:56
*** tpatil has joined #openstack-meeting20:56
sdaguehopefully compute starter kit helps offset that20:56
ttxyep, fear of getting lost20:56
edleafezaneb: some felt that incubation meant better quality20:56
edleafezaneb: and we know that wasn't always true20:56
dhellmannedleafe: +20:57
dhellmann+20:57
*** fawadk has quit IRC20:57
ttxso whatever we write, must clearly state that we still have official projects on one side and stackforge on th other, just the line doesn't use git repo prefixes anymore20:57
zanebedleafe: yeah, that's fair, and that's why we're putting these tags in place to make sure people can still get that info20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
jeblairttx: ++20:57
flaper87ttx: ++20:57
lifelessttx: lets not say 'official + stackforge' - thats just confusing :)20:57
lifelessttx: but yes, there are two sets20:57
*** rockyg has joined #openstack-meeting20:57
sdaguettx: is there a date scheduled for TC / Board joint meeting in Tokyo yet?20:57
*** okrieg has joined #openstack-meeting20:57
sdaguebecause... travel planning20:57
ttxsdague: Monday i'm told, no confirmation20:58
*** esker has quit IRC20:58
sdagueok, monday is an acceptable answer20:58
ttxThe Debian packaging team proposal was updated, we'll review it next week20:58
ttx#link https://review.openstack.org/18518720:58
*** hrou has quit IRC20:58
*** SlickNik has joined #openstack-meeting20:58
ttxWe are at about the middle of the cycle at this point, so I'd like to take a step back for 2 minutes20:58
*** glauco has joined #openstack-meeting20:58
ttxIs there any major problem we should be collectively working on fixing and that we aren't ?20:58
ttxI'm still deep in the big tent aftermath20:59
ttxI fear I'm losing the bigger picture20:59
sdaguethe dynamic policy bits are kind of gummed up20:59
sdagueI feel like we need to come together as a community around what's going on there in Tokyo20:59
sdaguebecause it's pretty cross project cutting21:00
ttxI think we have a few projects losing it (culture, not getting anything done, deadlocked...) and me and my team will focus on exploring them over the coming months21:00
flaper87I honestly don't have an answer OTOH but I'll put thoughts on this21:00
*** ijuwang has joined #openstack-meeting21:00
*** esker has joined #openstack-meeting21:00
annegentleit's a great question, necessary to ask.21:00
*** glauco has quit IRC21:00
*** glauco has joined #openstack-meeting21:00
*** Daisy has joined #openstack-meeting21:00
ttxso please, this week, take some time steppîng back and see if we are working on what we should be working on21:00
annegentlesounds good21:01
ttxI'm very happy with the project team gudie21:01
flaper87+121:01
ttxbut that's not the only thing21:01
dhellmannsdague: I just started a list of cross-project topics for the summit: https://etherpad.openstack.org/p/mitaka-cross-project-session-planning21:01
sdaguehonestly, I was thinking as we go into the cross project day in Tokyo, we should instead treat it as a TC priorities day, and be a little top down about the top things we think need some extra eyes21:01
*** raildo has quit IRC21:01
sdaguedhellmann: ok, great21:01
edleafesdague: +121:01
thingee#link https://etherpad.openstack.org/p/mitaka-cross-project-session-planning21:01
dhellmannwe should do the spreadsheet thing again for submissions, but this is good for notes for now21:01
ttxsdague: yeah, we should work ahead of that day and come up with the full agenda at this point21:01
ttxor that21:02
ttxanyway, time is up21:02
flaper87o/21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Tue Jul 28 21:02:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-07-28-20.03.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-07-28-20.03.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-07-28-20.03.log.html21:02
*** jungleboyj has joined #openstack-meeting21:02
ttxjohnthetubaguy: sorry for overflow21:02
fungii do sort of feel like if we don't report _accurately_ on the stackforge is in the openstack git namespace topic immediately, misinformed people will21:02
johnthetubaguyttx: no worries, looked like good stuff21:02
dhellmannfungi: ++21:02
johnthetubaguy#startmeeting crossproject21:03
openstackMeeting started Tue Jul 28 21:03:08 2015 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: crossproject)"21:03
edleafefungi: +121:03
openstackThe meeting name has been set to 'crossproject'21:03
jokke_o/21:03
SergeyLukjanovo/21:03
tpatilHi21:03
johnthetubaguycourtesy ping for david-lyle flaper87 dims dtroyer johnthetubaguy rakhmerov21:03
johnthetubaguycourtesy ping for smelikyan morganfainberg adrian_otto bswartz slagle21:03
johnthetubaguycourtesy ping for adrian_otto mestery kiall jeblair thinrichs j^2 stevebaker21:03
johnthetubaguycourtesy ping for mtreinish Daisy Piet notmyname ttx isviridov gordc SlickNik21:03
johnthetubaguycourtesy ping for cloudnull loquacities thingee hyakuhei redrobot dirk TravT21:03
EmilienMo/21:03
johnthetubaguycourtesy ping for vipul emilienm SergeyLukjanov devananda boris-42 nikhil_k21:03
elmikoheyo/21:03
dimso/21:03
david-lyleo/21:03
fungimmm hot cross projects21:03
mtreinisho/21:03
edleafeo/21:03
bknudsonhi21:03
johnthetubaguyhello all21:03
stevebaker\o21:03
thingeeo/21:03
dhellmanno/21:03
johnthetubaguyfungi: I am hungry now :)21:03
fungiindeed21:03
elmikolol21:03
SlickNiko/21:03
morganfainbergIm mostly just lurking. bknudson can speak on keystone's behalf if i miss something.21:03
fungiit's already dinner time here21:03
ttxo/21:04
*** okrieg has quit IRC21:04
jungleboyjo/21:04
*** jaypipes has quit IRC21:04
* mestery lurks while at the board meeting in person21:04
ttxit's way past dinner time here21:04
johnthetubaguyso looking that the agenda page21:04
*** okrieg has joined #openstack-meeting21:04
johnthetubaguy#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting21:04
jokke_ttx: it's past bed time for you ;)21:04
TravTo/21:04
johnthetubaguyseems like we need someone for August 11th21:04
redroboto/21:04
johnthetubaguyif people are keen21:04
devananda\o21:04
*** esker has quit IRC21:04
johnthetubaguyanyways, lets get cracking...21:04
johnthetubaguy#topic Team announcements (horizontal, vertical, diagonal)21:05
*** openstack changes topic to "Team announcements (horizontal, vertical, diagonal) (Meeting topic: crossproject)"21:05
ttxOn the release management side, this week is liberty-2 week21:05
*** Daisy has quit IRC21:05
ttxSo for projects that do development milestones, we'll be tagging that between today and Thursday21:05
ttxIf you haven't yet, ping dhellmann or me ASAP on #openstack-relmgr-office21:05
johnthetubaguy#info its liberty-2 week reach out on #openstack-relmgr-office21:05
ttxEOF21:05
*** ianw has quit IRC21:05
*** ianw has joined #openstack-meeting21:06
*** DericHorn-HP has joined #openstack-meeting21:06
*** rfolco has quit IRC21:06
*** Berezin has joined #openstack-meeting21:06
dhellmannif you're managing your own milestone, the checklist we use is:21:06
dhellmann#link https://wiki.openstack.org/wiki/Release_Cycle_Management/Milestone_Checklist21:06
*** aysyd has quit IRC21:06
* johnthetubaguy pokes the crowd for more announcements, maybe everyone is busy with liberty-2?21:06
*** vijendar has quit IRC21:07
ttxor not21:07
*** jamielennox has left #openstack-meeting21:07
fungifor those who missed the excitement, we had a security advisory for a non-vulnerability:managed deliverable today, whose vmt basically followed the vmt's documented process. kudos to kiall (who is apparently not with us)21:07
fungier, whose ptl21:07
*** stanchan has joined #openstack-meeting21:07
*** bswartz has quit IRC21:07
*** jruano has quit IRC21:07
dhellmannnice!21:08
johnthetubaguyso on the Nova side, we are doing a non-priority feature freeze on Thursday, in case thats on interest to other project21:08
*** okrieg has quit IRC21:08
fungi#link http://lists.openstack.org/pipermail/openstack-announce/2015-July/000482.html21:08
*** okrieg has joined #openstack-meeting21:08
*** VanL has quit IRC21:08
fungianyway, that's a piece of the vmt's bigtop scaling plan21:08
fungihelp project-teams help themselves21:08
johnthetubaguyfungi: sweet, good stuff21:08
*** s3wong has joined #openstack-meeting21:09
johnthetubaguyOK, so I sense a lack of updates, lets move on then...21:09
*** DericHorn-HP has quit IRC21:09
elmikoapi-wg has four new guidelines up for review21:09
johnthetubaguy#topic API Guidelines21:09
*** openstack changes topic to "API Guidelines (Meeting topic: crossproject)"21:09
elmikolol21:10
johnthetubaguy#link http://lists.openstack.org/pipermail/openstack-dev/2015-July/069765.html21:10
elmiko#link http://lists.openstack.org/pipermail/openstack-dev/2015-July/069765.html21:10
elmikojinx!21:10
johnthetubaguyelmiko: jinx!21:10
*** KunalGandhi has joined #openstack-meeting21:10
johnthetubaguydamm I was too slown21:10
thingee#undo21:10
*** VanL has joined #openstack-meeting21:10
johnthetubaguythingee: thanks for the fix, good call21:10
elmikowe can each owe each other a beverage johnthetubaguy ;)21:10
fungi(the chair has to #undo)21:10
johnthetubaguyso yeah, any of those people want to disucss21:10
thingeedon't think it registered21:10
johnthetubaguy#undo21:10
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0xae8c1d0>21:10
thingeefungi: heh thanks21:10
funginp21:10
johnthetubaguyfungi: ah, cool21:10
elmikothese have actually been up for 2 weeks now, but we haven't had any negative feedback yet. iirc21:11
johnthetubaguyso yeah, anything we need to discuss on there?21:11
elmikoalthough i will need to get etoews to remove the -221:11
jokke_elmiko: one of them had at least this afternoon couple of -1s21:11
*** jasondotstar has quit IRC21:11
elmikojokke_: ack, thank you21:11
*** armax has quit IRC21:11
*** okrieg has quit IRC21:12
johnthetubaguyjokke_: is it worth talking about the -1s here?21:12
jokke_I think it is21:12
elmikoi think the api-wg needs to review our freeze process as well. -2 seems to be not working for us21:12
*** okrieg has joined #openstack-meeting21:12
jokke_it's the header namings21:12
bknudsonall of these seem reasonable...21:12
elmiko#link https://review.openstack.org/#/c/186526/21:12
johnthetubaguy#link https://review.openstack.org/#/c/186526/21:12
bknudsonnote that keystone also uses the PATCH operation that has a body21:12
johnthetubaguy#undo21:12
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0xa76b910>21:12
jokke_I think it would be nice to agree on them and move on21:12
johnthetubaguyso missing a meeting last week was a bad slow down I guess21:13
johnthetubaguyI like giving people time to see them I suppose, but yeah, don't want to always enforce the slow down all the time I guess21:14
elmikothe real issue seems to come down to using project name or service name in the headers21:14
*** cdub has quit IRC21:14
*** KunalGandhi has quit IRC21:14
bknudsonnow we need to switch to OS-Identity-Token instead.21:15
*** delatte has quit IRC21:15
elmikoi think we'd like to recommend project name as it provides more resolution21:15
*** thangp has quit IRC21:15
johnthetubaguyelmiko: you mean if two projects have a compute API, or something like that?21:15
*** padkrish has quit IRC21:16
jokke_elmiko: ++ with big tent I think we might start seeing bit more overlapping21:16
elmikojohnthetubaguy: right, we could recommend Nova-someheader and NotNova-someheader ..21:16
*** yamamoto has joined #openstack-meeting21:16
*** padkrish has joined #openstack-meeting21:16
edleafethat would be confusing for end-users21:17
johnthetubaguyunsure if etoews is around21:17
elmikoi think he is still on vacation21:17
edleafeif the backend implements a different project for compute21:17
johnthetubaguyif the API working group owned the API name list, that would help21:17
johnthetubaguyelmiko: ah, no worries21:17
*** KunalGandhi has joined #openstack-meeting21:17
elmikoi'm not sure we want to "own" something like that21:17
*** penick has joined #openstack-meeting21:17
johnthetubaguylike have a registry of API names, so the registry would help deal with clashes in the big tent21:18
*** vivek-ebay has joined #openstack-meeting21:18
johnthetubaguyelmiko: true, maybe it goes in the projects.yaml?21:18
elmikoi agree it would be helpful, but the main thrust of the api-wg is to provide guideance and learning on creating sensible apis21:18
johnthetubaguylike API-service-name: XYZ21:18
jokke_that would be nice including current version of that API21:19
*** neelashah has joined #openstack-meeting21:19
johnthetubaguyjokke_: I guess it could21:19
fungihoping once the theory-of-api-design discussions die down within the api-wg, we might also see more suggestions on fixing bad api user experiences we have in existing implementations21:19
elmikoand remember this specific guidance is about adding new headers, we recommend that projects use more specific headers and to not necessarily use X-....21:19
elmikofungi: we have talked about creating advice for developers wishing to migrate their apis, this is something that is still very much in the design phase though.21:20
jokke_one thing that concerns me around that proposal is consistency21:20
*** padkrish has quit IRC21:21
sigmavirus24jokke_: the header proposal?21:21
jokke_now we will have N APIs using X- headers and soon enough N+1 that does not21:21
thingeefungi: +121:21
jokke_consistency ... that gremlin21:21
devanandafungi: ++ on api-wg helping to improve UX21:21
thingeefungi: Somehow things moved away from this idea.21:21
elmikojokke_: a valid concern, not sure we can really help more than to instruct developers on the best path out of the tangled forest ;)21:21
edleafejokke_: yeah, but when the standard shifts from underneath you...21:21
devanandare: the "X-" in the header -- I'm of the mind that we should keep it there because it's an evolving thing. but either way, it should be consistent across all projects21:22
jokke_edleafe: no-one told that the X- is not allowed it's just not the one that is insisted21:22
jrollquestion: is someone actually going to go register all of these headers in the IANA message headers registry?21:22
*** neelashah has quit IRC21:22
sigmavirus24jokke_: consistency, the thing OpenStack doesn't have21:22
elmikojroll: that is a good question21:22
*** otter768 has joined #openstack-meeting21:22
devanandaand my counter argument to the api-wg would be: if we drop the X- from that header, should'nt we drop the X- from all the othre headers too?21:22
*** vivek-ebay has quit IRC21:22
edleafejokke_: it is discouraged for new headers, but with full recognition that existing headers, well, *exist*.21:23
sigmavirus24devananda: not existing APIs21:23
jrollelmiko: and if nobody is going to register them, things like "Compute-API-Version" will almost certainly conflict with other things out there21:23
elmikodevananda: if the goal is to work towards consistency, then yes. i'm not sure that is the goal at this point though.21:23
sigmavirus24devananda: it should be dropped when authoring new versions of APIs21:23
jokke_sigmavirus24: that's why I'm surprised that the api_wg is suggesting to break the one thing we had it even remotely ;)21:23
sigmavirus24jokke_: we're suggesting you follow API best practices21:23
jroll(I'm not sure if registration is a SHOULD or MUST or MAY, though)21:23
sigmavirus24which, promotes good user experience21:23
jokke_edleafe: ah, might be that I misunderstood the point there then, sorry21:23
elmikoi think registering the header names, and moving towards consistency are excellent points for our forthcoming migration guidance21:23
*** baoli has quit IRC21:24
devanandasigmavirus24: authoring new service projects? new major versions of APIs of existing projects? or something else?21:24
sigmavirus24jokke_: also don't get me started on which services use headers for things they absolutely shouldn't21:24
sigmavirus24devananda: yes21:24
devanandasigmavirus24: and would it be dropped from all headers returned in those cases, or just the "established" ones?21:24
*** matrohon has quit IRC21:25
jrollanother question: does consistency in header names actually benefit users? do people really expect to be able to look for "X-%(service_type)-Version" or whatever?21:25
jokke_I would thing that major version is the only acceptable place to change those?21:25
*** yamamoto has quit IRC21:25
*** sridhar_ram has joined #openstack-meeting21:25
*** neelashah has joined #openstack-meeting21:25
*** balajiiyer has quit IRC21:25
edleafedevananda: if a service has 'X-Foo-Bar', they could continue to support that, and also add 'Foo-Bar' for the future21:25
*** vivek-ebay has joined #openstack-meeting21:25
*** mestery has quit IRC21:25
sigmavirus24jroll: given that people don't all use the command-line clients and some are writing them from scratch, that helps users, yes21:26
devanandaedleafe: mm, indeed21:26
edleafedevananda: and all new APIs would not use 'X-'21:26
*** neelashah1 has joined #openstack-meeting21:26
*** rockyg has quit IRC21:26
*** VanL has quit IRC21:26
* sigmavirus24 wonders if he even needs to participate given how well edleafe is explaining this on his own21:26
elmikoedleafe: +121:26
bknudsonwould be nice to see an example for X-Auth-Token , since that's pretty common.21:26
jrollsigmavirus24: I don't think anyone reasonably building an application against an API would just wildly guess at header names, but that might just be me21:26
devanandabknudson: ++21:27
sigmavirus24jroll: so given some services use it to transmit arbitrary metadata, that's exactly how some clients work21:27
edleafejroll: you don't? I do that for fun all the time!  :)21:27
*** MarkAtwood has quit IRC21:27
elmikoagreed, bknudson +121:27
*** otter768 has quit IRC21:27
sigmavirus24jroll: this won't change that for existing APIs, but will improve that in the future in general21:27
elmikothese are some great comments, would folks mind capturing some of these in the review please =)21:27
fungidefinitely in favor of having solid examples of these relevant to our current services21:27
johnthetubaguyso I have a feeling I should call time on this21:27
*** mrmartin has quit IRC21:28
johnthetubaguyelmiko: +1 lets get these in to review comments I guess21:28
sigmavirus24fungi: we've been trying not to do that to avoid pointing fingers or appearing to "shame"21:28
jrollsigmavirus24: ok, just asking the question :)21:28
jokke_johnthetubaguy: +1 move on :D21:28
elmikothanks johnthetubaguy21:28
fungithere's enough shame to go around21:28
sigmavirus24fungi: don't disagree ;)21:28
johnthetubaguycools21:28
johnthetubaguyso lets assume the other ones are all good, unless someone pipes up real soon21:28
dstaneksigmavirus24: i'd love to see keystone examples, i don't mind the finger pointing at us21:28
sigmavirus24dstanek: hah, fair enough21:29
johnthetubaguy#topic Cross Project Specs21:29
*** openstack changes topic to "Cross Project Specs (Meeting topic: crossproject)"21:29
*** esker has joined #openstack-meeting21:29
johnthetubaguyso I have looked up some of the cross project specs that are up21:29
johnthetubaguyand need a look21:29
johnthetubaguy#link https://review.openstack.org/#/c/20562921:29
johnthetubaguythat is about no global admin21:29
*** padkrish has joined #openstack-meeting21:30
*** neelashah has quit IRC21:30
johnthetubaguythat seems like a sound concept21:30
elmikoyea, +121:30
*** pnavarro has quit IRC21:30
johnthetubaguythere is one that looks like it gets replaced by the SDK work:21:30
johnthetubaguy#link https://review.openstack.org/#/c/20258621:30
johnthetubaguycalled: Uniform public methods for clients21:31
*** resker has joined #openstack-meeting21:31
johnthetubaguyanyways, here is the general link if you fancy a dig into some old ones21:31
johnthetubaguy#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-specs,n,z21:31
*** vishwanathj has joined #openstack-meeting21:31
johnthetubaguyalthough you all new that, but a link can be easier21:31
dstanek++ to no global admin21:31
*** esker_ has joined #openstack-meeting21:32
johnthetubaguyanyways, tpatil I think you added your request-id work to the agenda?21:32
tpatilHi21:32
tpatilWe have analyzed return types of each of the public method from 5 different python client libraries21:32
tpatilpython-glance, python-cinder, python-nova, python-neutron, python-keystone21:32
johnthetubaguy#topic Return request-id to caller21:32
*** openstack changes topic to "Return request-id to caller (Meeting topic: crossproject)"21:32
tpatilAll information is available in the google spreadsheet and etherpad21:32
*** zehicle_IRL has quit IRC21:32
johnthetubaguy#link https://etherpad.openstack.org/p/request-id21:32
tpatil#link: https://docs.google.com/spreadsheets/d/1al6_XBHgKT8-N7HS7j_L2H5c4CFD0fB8xT93z6REkSk21:32
tpatilWe have identified 3 more additional return types (string,boolean,generator) compared to the ones reported earlier21:32
tpatilHad a issue with returning request id in generator return type, Doug suggested a solution to overcome this problem by writing a new wrapper class and implementing iterator protocol21:33
*** esker__ has joined #openstack-meeting21:33
tpatilWe have solutions to all issues identified so far to return request id to the caller21:33
*** MaxPC has quit IRC21:33
johnthetubaguytpatil: I know this is a lot more work, but it seems like it is a viable solution then?21:33
*** esker___ has joined #openstack-meeting21:33
*** esker has quit IRC21:34
tpatiljohnthetubaguy: Yes, all concerns are addressed it seems21:34
bknudsonwrapt provides a object proxy -- http://wrapt.readthedocs.org/en/latest/wrappers.html -- was just looking at this today21:34
*** cp16net has left #openstack-meeting21:34
tpatilAnother thing I would like to bring to your attention is that request id is most needed when api returns anything >= 400 error code21:34
tpatilpython-cinderclient already has a mechanism to return request id in exception21:34
tpatil#link: https://github.com/openstack/python-cinderclient/blob/master/cinderclient/exceptions.py#L8721:34
tpatilIMO, we should first add request id in exception class in the rest of the python client libraries before start making changes to the rest of the return types21:34
tpatilBased on all information available to date, we will modify the specs and upload it for review by end of this week21:34
johnthetubaguytpatil: sounds like a very good plan to me, at least, sounds like a great place to start21:34
*** esker has joined #openstack-meeting21:34
jokke_sounds like reasonable place to start21:34
bknudsonis adding request_id to the exception in the spec?21:34
tpatilbknudson: Not yet, we will modify specs and upload it soon21:35
*** resker has quit IRC21:35
johnthetubaguy#action tpatil to update request id spec with latest details21:35
*** resker has joined #openstack-meeting21:35
bknudsonthanks!21:35
johnthetubaguycool, sounds like we have got a good path forward here21:36
johnthetubaguytpatil: any more questions?21:36
*** esker_ has quit IRC21:36
*** vishwanathj has quit IRC21:36
tpatiljohnthetubaguy: That’s all I wanted to update you at the moment21:36
johnthetubaguytpatil: awesome stuff, thank you for pushing on this :)21:36
johnthetubaguy#topic Open discussion21:36
*** openstack changes topic to "Open discussion (Meeting topic: crossproject)"21:36
* jokke_ is happy - this topic gets shorter each time :)21:36
johnthetubaguyjokke_: +121:36
johnthetubaguyhey, so time to go wild, if you are feeling that way :)21:37
*** esker_ has joined #openstack-meeting21:37
*** esker__ has quit IRC21:37
jokke_Horizon, glance, searchlight having midcycles this week ... some x-proj collaboration going on there21:37
jungleboyjjokke_: ++21:38
johnthetubaguygood stuff21:38
*** esker___ has quit IRC21:38
*** jamespage_ has joined #openstack-meeting21:38
jokke_and just if someone missed21:38
jungleboyjCinder's meet-up is the 8/4 to 8/6 if anyone wants to come collaborate with us in Fort Collins!21:38
*** neelashah1 has quit IRC21:39
jokke_we're removing that experimental Catalog & Index service api from glance21:39
jungleboyjFort Collins is awesome!21:39
*** esker has quit IRC21:39
jokke_as in the one that became searchlight21:39
*** esker has joined #openstack-meeting21:39
*** topol has quit IRC21:39
bknudsonhow was the api marked experimental?21:39
thingeeWould like to bring up that Cinder, like Nova is having issues with Glance v2 http://lists.openstack.org/pipermail/openstack-dev/2015-July/070714.html21:40
*** resker has quit IRC21:40
*** resker has joined #openstack-meeting21:40
*** jamespage_ has quit IRC21:40
dstanekjungleboyj: sounds like fun, but too far of a drive for me21:41
thingeeI'm not sure if there is someone from the glance team that is available actively looking at cross project integration issues?21:41
*** esker_ has quit IRC21:42
*** tpatil has quit IRC21:42
*** dims has quit IRC21:42
*** gordc has joined #openstack-meeting21:42
jokke_bknudson: It's status was marked EXPERIMENTAL instead of SUPPORTED or CURRENT ... enabling it also needed ack in config that it's experimental IIRC21:42
fungi#link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons21:42
fungithingee: ^21:42
thingeenikhil_k: ^21:42
fungii think that's the closest list we have to such a thing21:43
*** tpatil has joined #openstack-meeting21:44
thingeefungi: yeah johnthetubaguy just actually showed me that today. that's pretty neat. I was hoping we could discuss a cross with glance and cinder.21:44
*** esker has quit IRC21:44
thingeealright, I guess I'll go to the glance meeting then.21:44
johnthetubaguyyeah, Nova side we don't really have v2 support, but there were some bugs reported when we used v1 and users used v2, although I have not dug deep into that21:44
jokke_thingee: Thu 1400 ... welcome21:44
johnthetubaguyI should head over there at some point soon too21:45
*** lukebrooker has joined #openstack-meeting21:45
*** resker has quit IRC21:45
*** eharney has quit IRC21:45
*** sridhar_ram has quit IRC21:45
jokke_https://etherpad.openstack.org/p/glance-team-meeting-agenda21:45
johnthetubaguythingee: the cross project thing is only really just getting going, help getting the most out of that would be great, not sure we have great patterns yet21:46
jokke_if you wanna add yourselves into the agenda21:46
johnthetubaguycool, so I think we are about done21:46
johnthetubaguythanks for your time all21:46
*** esker has joined #openstack-meeting21:46
jungleboyjjohnthetubaguy: Hopefully it can gain more momentum.21:46
johnthetubaguymarkmcclain is our host next week, I believe21:46
jokke_thanks johnthetubaguy21:46
elmikothanks johnthetubaguy21:46
*** niska has quit IRC21:46
johnthetubaguyjungleboyj: yeah, I want to push a bit further on the Nova related ones again soon21:47
johnthetubaguythanks all21:47
johnthetubaguy#endmeeting21:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:47
openstackMeeting ended Tue Jul 28 21:47:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:47
*** resker has joined #openstack-meeting21:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-07-28-21.03.html21:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-07-28-21.03.txt21:47
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-07-28-21.03.log.html21:47
jungleboyjThanks!21:47
tpatilThanks everyone!21:47
*** padkrish has quit IRC21:48
* johnthetubaguy sleep time me thinks, since I am out of hot cross buns21:48
*** esker_ has joined #openstack-meeting21:48
elmikolol21:48
*** gordc has left #openstack-meeting21:49
*** bobh has joined #openstack-meeting21:49
*** padkrish has joined #openstack-meeting21:50
*** esker has quit IRC21:50
*** jruano has joined #openstack-meeting21:51
*** niska has joined #openstack-meeting21:51
*** esker has joined #openstack-meeting21:51
*** angdraug has left #openstack-meeting21:51
*** resker has quit IRC21:52
*** jwcroppe has joined #openstack-meeting21:52
*** vishwanathj has joined #openstack-meeting21:52
*** esker_ has quit IRC21:52
*** changbl has quit IRC21:53
*** resker has joined #openstack-meeting21:53
*** JRobinson__ has joined #openstack-meeting21:53
*** hashar has quit IRC21:53
*** edtubill has left #openstack-meeting21:54
*** esker_ has joined #openstack-meeting21:54
*** padkrish has quit IRC21:55
*** esker has quit IRC21:56
*** arajagopal has quit IRC21:56
*** esker has joined #openstack-meeting21:56
*** eghobo has joined #openstack-meeting21:57
*** resker has quit IRC21:57
*** bobh has quit IRC21:57
*** sridhar_ram has joined #openstack-meeting21:58
*** resker has joined #openstack-meeting21:58
*** cing has joined #openstack-meeting21:59
*** esker_ has quit IRC21:59
*** bknudson has quit IRC21:59
*** Alexey_nexenta has quit IRC22:00
*** vishwanathj has quit IRC22:00
*** coolsvap|mtg is now known as coolsvap|away22:00
*** eghobo has left #openstack-meeting22:01
*** esker has quit IRC22:01
*** dims has joined #openstack-meeting22:02
*** resker has quit IRC22:02
*** josdotso has quit IRC22:03
*** pm90_ has quit IRC22:03
*** vishwanathj has joined #openstack-meeting22:04
*** jruano has quit IRC22:05
*** okrieg has quit IRC22:06
*** jungleboyj has quit IRC22:06
*** jecarey_ has quit IRC22:08
*** hemnalunch is now known as hemna22:09
*** vishwanathj has quit IRC22:09
*** eliqiao1 has joined #openstack-meeting22:11
*** elmiko has left #openstack-meeting22:11
*** eliqiao has quit IRC22:12
*** mdenny has quit IRC22:13
*** jruano has joined #openstack-meeting22:13
*** sridhar_ram has quit IRC22:15
*** lukebrooker has quit IRC22:15
*** haomaiwang has quit IRC22:15
*** VW_ has quit IRC22:16
*** haomaiwang has joined #openstack-meeting22:17
*** VW_ has joined #openstack-meeting22:17
*** glauco has quit IRC22:18
*** annegentle has quit IRC22:18
*** jmckind has quit IRC22:18
*** dboik has quit IRC22:19
*** lukebrooker has joined #openstack-meeting22:19
*** MaxPC has joined #openstack-meeting22:20
*** VW_ has quit IRC22:21
*** kylek3h has quit IRC22:22
*** mwagner_lap has quit IRC22:23
*** cing has quit IRC22:25
*** glauco has joined #openstack-meeting22:25
*** yamamoto has joined #openstack-meeting22:26
*** padkrish has joined #openstack-meeting22:26
*** padkrish has quit IRC22:27
*** padkrish has joined #openstack-meeting22:28
*** egallen has quit IRC22:28
*** Berezin has quit IRC22:29
*** Berezin has joined #openstack-meeting22:29
*** bswartz has joined #openstack-meeting22:30
*** yamamoto has quit IRC22:30
*** JRobinson__ has quit IRC22:31
*** JRobinson__ has joined #openstack-meeting22:34
*** Piet has joined #openstack-meeting22:34
*** glauco has quit IRC22:36
*** slong__ has quit IRC22:36
*** padkrish has quit IRC22:37
*** rossella_s has quit IRC22:37
*** padkrish has joined #openstack-meeting22:37
*** rossella_s has joined #openstack-meeting22:37
*** igordcard has quit IRC22:39
*** topol has joined #openstack-meeting22:40
*** singlet__ has quit IRC22:40
*** jungleboyj has joined #openstack-meeting22:43
*** fzdarsky has quit IRC22:44
*** topol has quit IRC22:44
*** marcusvrn has quit IRC22:45
*** jruano has quit IRC22:46
*** tpatil has quit IRC22:47
*** elo has joined #openstack-meeting22:48
*** garthb has joined #openstack-meeting22:50
*** garthb_ has joined #openstack-meeting22:50
*** garthb_ has quit IRC22:50
*** VW_ has joined #openstack-meeting22:51
*** elo1 has quit IRC22:52
*** okrieg has joined #openstack-meeting22:53
*** Guest47142 is now known as dan22:56
*** hrou has joined #openstack-meeting22:57
*** jruano has joined #openstack-meeting22:59
*** dannywilson has quit IRC23:00
*** penick has quit IRC23:01
*** haomaiwang has quit IRC23:01
*** haomaiwang has joined #openstack-meeting23:02
*** puranamr has quit IRC23:02
*** cdub has joined #openstack-meeting23:05
*** dims has quit IRC23:05
*** sigmavirus24 is now known as sigmavirus24_awa23:07
*** okrieg has quit IRC23:08
*** echoingumesh has joined #openstack-meeting23:09
*** jruano has quit IRC23:09
*** VW_ has quit IRC23:09
*** VW_ has joined #openstack-meeting23:10
*** ^Gal^__ has quit IRC23:11
*** kebray has quit IRC23:12
*** eliqiao has joined #openstack-meeting23:14
*** xingchao has joined #openstack-meeting23:15
*** eliqiao1 has quit IRC23:16
*** xek has quit IRC23:18
*** padkrish has quit IRC23:18
*** sorrison has left #openstack-meeting23:19
*** xingchao has quit IRC23:20
*** xek has joined #openstack-meeting23:21
*** otter768 has joined #openstack-meeting23:23
*** timrc has quit IRC23:24
*** stanchan has quit IRC23:24
*** Piet has quit IRC23:25
*** Piet has joined #openstack-meeting23:26
*** otter768 has quit IRC23:28
*** mattoliverau has quit IRC23:29
*** mattoliverau has joined #openstack-meeting23:29
*** ijw has quit IRC23:29
*** timrc has joined #openstack-meeting23:30
*** Qiming has joined #openstack-meeting23:31
*** rhagarty_ has quit IRC23:33
*** rhagarty has quit IRC23:33
*** neiljerr` has quit IRC23:34
*** dims has joined #openstack-meeting23:34
*** esker has joined #openstack-meeting23:34
*** ijw has joined #openstack-meeting23:34
*** timrc has quit IRC23:34
*** fzdarsky has joined #openstack-meeting23:34
*** cdub has quit IRC23:35
*** Qiming has quit IRC23:36
*** esker has quit IRC23:36
*** elo1 has joined #openstack-meeting23:36
*** crc32 has quit IRC23:36
*** esker has joined #openstack-meeting23:36
*** jmckind has joined #openstack-meeting23:37
*** merooney has joined #openstack-meeting23:37
*** rhagarty has joined #openstack-meeting23:38
*** elo has quit IRC23:38
*** rhagarty_ has joined #openstack-meeting23:39
*** tochi has joined #openstack-meeting23:40
*** jasondotstar has joined #openstack-meeting23:41
*** VW_ has quit IRC23:41
*** kaisers has quit IRC23:42
*** VW_ has joined #openstack-meeting23:42
*** erlon has quit IRC23:43
*** kaisers has joined #openstack-meeting23:44
*** toscalix has quit IRC23:44
*** timrc has joined #openstack-meeting23:44
*** IlyaG has quit IRC23:44
*** wznoinsk1 has quit IRC23:45
*** wznoinsk1 has joined #openstack-meeting23:46
*** pczesno has joined #openstack-meeting23:46
*** VW_ has quit IRC23:46
*** albertom has quit IRC23:46
*** zzz_pczesno has quit IRC23:47
*** albertom has joined #openstack-meeting23:48
*** salv-orlando has quit IRC23:52
*** okrieg has joined #openstack-meeting23:53
*** harshs has quit IRC23:55
*** ivar-lazzaro has quit IRC23:55
*** sdake has quit IRC23:56
*** echoingumesh has quit IRC23:56
*** Berezin has quit IRC23:58
*** hichihara has joined #openstack-meeting23:59

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