Thursday, 2016-05-19

*** mbound has quit IRC00:00
*** zenoway has quit IRC00:00
*** gangil has joined #openstack-meeting-400:02
*** shaohe_feng has quit IRC00:03
*** shaohe_feng has joined #openstack-meeting-400:04
*** gangil has quit IRC00:04
*** xingchao has quit IRC00:05
*** ddieterly has joined #openstack-meeting-400:06
*** bobh has quit IRC00:07
*** minwang2 has quit IRC00:10
*** banix has quit IRC00:12
*** sdake has quit IRC00:13
*** shaohe_feng has quit IRC00:13
*** markvoelker has quit IRC00:13
*** shaohe_feng has joined #openstack-meeting-400:14
*** bpokorny_ has joined #openstack-meeting-400:14
*** bpokorny_ has quit IRC00:15
*** bpokorny_ has joined #openstack-meeting-400:15
*** bpokorn__ has joined #openstack-meeting-400:17
*** bpokorny_ has quit IRC00:17
*** iurygregory has quit IRC00:18
*** bpokorny has quit IRC00:18
*** bpokorn__ has quit IRC00:18
*** bpokorny has joined #openstack-meeting-400:19
*** shaohe_feng has quit IRC00:23
*** shaohe_feng has joined #openstack-meeting-400:24
*** gangil has joined #openstack-meeting-400:24
*** ajmiller_ has joined #openstack-meeting-400:25
*** raddaoui has quit IRC00:27
*** thorst_ has joined #openstack-meeting-400:27
*** ajmiller has quit IRC00:29
*** bobh has joined #openstack-meeting-400:33
*** shaohe_feng has quit IRC00:33
*** shaohe_feng has joined #openstack-meeting-400:34
*** julim has joined #openstack-meeting-400:35
*** rajen-liyuanzhen has quit IRC00:43
*** shaohe_feng has quit IRC00:44
*** sigmavirus24 is now known as sigmavirus24_awa00:45
*** shaohe_feng has joined #openstack-meeting-400:47
*** julim has quit IRC00:49
*** xingchao has joined #openstack-meeting-400:50
*** xingchao has quit IRC00:52
*** xingchao has joined #openstack-meeting-400:52
*** vhoward has quit IRC00:52
*** shaohe_feng has quit IRC00:54
*** shaohe_feng has joined #openstack-meeting-400:55
*** pvaneck has quit IRC00:55
*** ninag has joined #openstack-meeting-400:57
*** bpokorny has quit IRC00:57
*** errr has joined #openstack-meeting-400:57
*** zhurong has joined #openstack-meeting-400:58
*** xingchao has quit IRC00:58
*** ninag has quit IRC01:02
*** Kevin_Zheng has joined #openstack-meeting-401:03
*** xingchao has joined #openstack-meeting-401:03
*** shaohe_feng has quit IRC01:04
*** shaohe_feng has joined #openstack-meeting-401:05
*** gangil has quit IRC01:06
*** spzala has joined #openstack-meeting-401:08
*** spzala has quit IRC01:08
*** spzala has joined #openstack-meeting-401:08
*** shaohe_feng has quit IRC01:14
*** shaohe_feng has joined #openstack-meeting-401:17
*** Sukhdev has quit IRC01:22
*** shaohe_feng has quit IRC01:25
*** shaohe_feng has joined #openstack-meeting-401:25
*** Jeffrey4l has joined #openstack-meeting-401:30
*** ddieterly is now known as ddieterly[away]01:32
*** ddieterly[away] has quit IRC01:32
*** baoli has joined #openstack-meeting-401:35
*** shaohe_feng has quit IRC01:35
*** shaohe_feng has joined #openstack-meeting-401:36
*** Sukhdev has joined #openstack-meeting-401:39
*** thorst_ has quit IRC01:42
*** thorst_ has joined #openstack-meeting-401:42
*** Sukhdev has quit IRC01:45
*** shaohe_feng has quit IRC01:45
*** shaohe_feng has joined #openstack-meeting-401:46
*** May-meimei has left #openstack-meeting-401:50
*** baoli has quit IRC01:51
*** baoli has joined #openstack-meeting-401:51
*** thorst_ has quit IRC01:51
*** s3wong has quit IRC01:54
*** yamahata has joined #openstack-meeting-401:55
*** shaohe_feng has quit IRC01:55
*** shaohe_feng has joined #openstack-meeting-401:56
*** baoli has quit IRC01:57
*** bobh has quit IRC01:57
*** gangil has joined #openstack-meeting-401:57
*** xiaohhui has quit IRC02:03
*** yamamoto_ has joined #openstack-meeting-402:06
*** shaohe_feng has quit IRC02:06
*** vishwanathj has quit IRC02:09
*** shaohe_feng has joined #openstack-meeting-402:09
*** xingchao has quit IRC02:13
*** v1k0d3n has quit IRC02:13
*** v1k0d3n has joined #openstack-meeting-402:14
*** xingchao has joined #openstack-meeting-402:14
*** shaohe_feng has quit IRC02:16
*** shaohe_feng has joined #openstack-meeting-402:17
*** mbound has joined #openstack-meeting-402:18
*** sdake has joined #openstack-meeting-402:19
*** unicell has quit IRC02:20
*** unicell has joined #openstack-meeting-402:22
*** mbound has quit IRC02:22
*** unicell has quit IRC02:22
*** sdake has quit IRC02:23
*** sacharya_ has joined #openstack-meeting-402:26
*** shaohe_feng has quit IRC02:26
*** shaohe_feng has joined #openstack-meeting-402:27
*** sacharya has quit IRC02:29
*** yamahata has quit IRC02:34
*** baoli has joined #openstack-meeting-402:35
*** bobh has joined #openstack-meeting-402:35
*** iyamahat has quit IRC02:35
*** shaohe_feng has quit IRC02:36
*** shaohe_feng has joined #openstack-meeting-402:37
*** baoli has quit IRC02:39
*** baoli has joined #openstack-meeting-402:39
*** reedip has joined #openstack-meeting-402:41
*** baoli has quit IRC02:42
*** spzala has quit IRC02:43
*** baoli has joined #openstack-meeting-402:43
*** spzala has joined #openstack-meeting-402:43
*** spzala has quit IRC02:44
*** spzala has joined #openstack-meeting-402:44
*** shaohe_feng has quit IRC02:47
*** shaohe_feng has joined #openstack-meeting-402:47
*** thorst_ has joined #openstack-meeting-402:48
*** banix has joined #openstack-meeting-402:52
*** lakshmiS has quit IRC02:52
*** daneyon has joined #openstack-meeting-402:54
*** xingchao has quit IRC02:56
*** thorst_ has quit IRC02:57
*** shaohe_feng has quit IRC02:57
*** xingchao has joined #openstack-meeting-402:57
*** shaohe_feng has joined #openstack-meeting-402:58
*** bobh has quit IRC02:58
*** bobh has joined #openstack-meeting-402:58
*** ajmiller has joined #openstack-meeting-402:59
*** ajmiller_ has quit IRC03:02
*** spzala has quit IRC03:03
*** bobh has quit IRC03:04
*** xiaohhui has joined #openstack-meeting-403:06
*** shaohe_feng has quit IRC03:07
*** shaohe_feng has joined #openstack-meeting-403:08
*** baoli has quit IRC03:09
*** JRobinson__ is now known as JRobinson__afk03:17
*** coolsvap has joined #openstack-meeting-403:17
*** shaohe_feng has quit IRC03:17
*** shaohe_feng has joined #openstack-meeting-403:21
*** yamamoto_ has quit IRC03:26
*** shaohe_feng has quit IRC03:28
*** shaohe_feng has joined #openstack-meeting-403:28
*** ajmiller has quit IRC03:33
*** shaohe_feng has quit IRC03:38
*** shaohe_feng has joined #openstack-meeting-403:38
*** ajmiller has joined #openstack-meeting-403:38
*** minwang2 has joined #openstack-meeting-403:43
*** banix has quit IRC03:43
*** shaohe_feng has quit IRC03:48
*** shaohe_feng has joined #openstack-meeting-403:49
*** reedip has quit IRC03:53
*** thorst_ has joined #openstack-meeting-403:54
*** reedip has joined #openstack-meeting-403:55
*** JRobinson__afk is now known as JRobinson__03:58
*** shaohe_feng has quit IRC03:58
*** shaohe_feng has joined #openstack-meeting-403:59
*** thorst_ has quit IRC04:01
*** coolsvap has quit IRC04:04
*** ninag has joined #openstack-meeting-404:06
*** evgenyf has joined #openstack-meeting-404:06
*** amotoki has joined #openstack-meeting-404:06
*** yamamoto_ has joined #openstack-meeting-404:09
*** shaohe_feng has quit IRC04:09
*** shaohe_feng has joined #openstack-meeting-404:10
*** ninag has quit IRC04:10
*** evgenyf has quit IRC04:10
*** Jeffrey4l has quit IRC04:16
*** shaohe_feng has quit IRC04:19
*** shaohe_feng has joined #openstack-meeting-404:20
*** ajmiller has quit IRC04:20
*** Sukhdev has joined #openstack-meeting-404:20
*** Sukhdev has quit IRC04:24
*** Sukhdev has joined #openstack-meeting-404:24
*** cartik has joined #openstack-meeting-404:26
*** shaohe_feng has quit IRC04:29
*** shaohe_feng has joined #openstack-meeting-404:30
*** shaohe_feng has quit IRC04:39
*** coolsvap has joined #openstack-meeting-404:40
*** shaohe_feng has joined #openstack-meeting-404:40
*** armax has quit IRC04:40
*** GB21 has joined #openstack-meeting-404:46
*** xingchao has quit IRC04:48
*** minwang2 has quit IRC04:49
*** shaohe_feng has quit IRC04:50
*** GB21 has quit IRC04:51
*** shaohe_feng has joined #openstack-meeting-404:53
*** kinapa has joined #openstack-meeting-404:53
*** gongysh has joined #openstack-meeting-404:53
*** vishnoianil has quit IRC04:54
*** armax has joined #openstack-meeting-404:54
*** padkrish has joined #openstack-meeting-404:58
*** thorst_ has joined #openstack-meeting-404:59
*** shaohe_feng has quit IRC05:00
*** shaohe_feng has joined #openstack-meeting-405:01
*** armax has quit IRC05:01
*** armax has joined #openstack-meeting-405:03
*** gongysh has quit IRC05:04
*** thorst_ has quit IRC05:06
*** GB21 has joined #openstack-meeting-405:06
*** cemason has joined #openstack-meeting-405:08
*** shaohe_feng has quit IRC05:10
*** shaohe_feng has joined #openstack-meeting-405:11
*** coolsvap has quit IRC05:20
*** coolsvap has joined #openstack-meeting-405:20
*** shaohe_feng has quit IRC05:20
*** coolsvap has quit IRC05:21
*** coolsvap_ has joined #openstack-meeting-405:21
*** coolsvap_ is now known as coolsvap05:21
*** shaohe_feng has joined #openstack-meeting-405:21
*** iyamahat has joined #openstack-meeting-405:24
*** irenab has joined #openstack-meeting-405:25
*** markvoelker has joined #openstack-meeting-405:27
*** iyamahat has quit IRC05:29
*** shaohe_feng has quit IRC05:31
*** shaohe_feng has joined #openstack-meeting-405:31
*** markvoelker has quit IRC05:34
*** javeriak has joined #openstack-meeting-405:35
*** unicell has joined #openstack-meeting-405:36
*** GB21 has quit IRC05:37
*** shaohe_feng has quit IRC05:41
*** mohankumar__ has joined #openstack-meeting-405:41
*** vishnoianil has joined #openstack-meeting-405:42
*** shaohe_feng has joined #openstack-meeting-405:42
*** yamahata has joined #openstack-meeting-405:44
*** shaohe_feng has quit IRC05:51
*** salv-orlando has joined #openstack-meeting-405:51
*** shaohe_feng has joined #openstack-meeting-405:52
*** javeriak has quit IRC05:53
*** fawadkhaliq has joined #openstack-meeting-405:57
*** Sukhdev has quit IRC05:57
*** Jeffrey4l has joined #openstack-meeting-405:58
*** armax has quit IRC06:00
*** padkrish has quit IRC06:01
*** shaohe_feng has quit IRC06:01
*** shaohe_feng has joined #openstack-meeting-406:02
*** ricolin has joined #openstack-meeting-406:03
*** dshakhray has joined #openstack-meeting-406:03
*** thorst_ has joined #openstack-meeting-406:04
*** xingchao has joined #openstack-meeting-406:05
*** reedip_ has joined #openstack-meeting-406:09
*** reedip has quit IRC06:10
*** thorst_ has quit IRC06:10
*** shaohe_feng has quit IRC06:12
*** shaohe_feng has joined #openstack-meeting-406:12
*** GB21 has joined #openstack-meeting-406:14
*** Jeffrey4l has quit IRC06:18
*** unicell has quit IRC06:20
*** unicell has joined #openstack-meeting-406:20
*** itisha has joined #openstack-meeting-406:22
*** shaohe_feng has quit IRC06:22
*** shaohe_feng has joined #openstack-meeting-406:25
*** numans has joined #openstack-meeting-406:27
*** salv-orlando has quit IRC06:32
*** shaohe_feng has quit IRC06:32
*** majklkcz has joined #openstack-meeting-406:35
*** shaohe_feng has joined #openstack-meeting-406:35
*** tfukushima has joined #openstack-meeting-406:41
*** shaohe_feng has quit IRC06:42
*** anilvenkata has joined #openstack-meeting-406:43
*** nkrinner_afk is now known as nkrinner06:43
*** shaohe_feng has joined #openstack-meeting-406:45
*** belmoreira has joined #openstack-meeting-406:45
*** ricolin has quit IRC06:45
*** shaohe_feng has quit IRC06:53
*** shaohe_feng has joined #openstack-meeting-406:53
*** sacharya_ has quit IRC06:57
*** dshakhray has quit IRC06:59
*** ricolin has joined #openstack-meeting-407:02
*** shaohe_feng has quit IRC07:03
*** shaohe_feng has joined #openstack-meeting-407:03
*** thorst_ has joined #openstack-meeting-407:08
*** jichen has joined #openstack-meeting-407:09
*** seanmurphy has joined #openstack-meeting-407:13
*** shaohe_feng has quit IRC07:13
*** shaohe_feng has joined #openstack-meeting-407:13
*** thorst_ has quit IRC07:15
*** javeriak has joined #openstack-meeting-407:20
*** shaohe_feng has quit IRC07:23
*** shaohe_feng has joined #openstack-meeting-407:27
*** ahale has joined #openstack-meeting-407:31
*** ninag has joined #openstack-meeting-407:32
*** shaohe_feng has quit IRC07:34
*** shaohe_feng has joined #openstack-meeting-407:35
*** irenab_ has joined #openstack-meeting-407:36
*** ninag has quit IRC07:37
*** irenab has quit IRC07:38
*** irenab_ is now known as irenab07:38
*** fawadkhaliq has quit IRC07:39
*** fawadkhaliq has joined #openstack-meeting-407:39
*** fwdit has joined #openstack-meeting-407:40
*** matrohon has joined #openstack-meeting-407:40
*** alexchadin has joined #openstack-meeting-407:41
*** vincentfrancoise has joined #openstack-meeting-407:43
*** shaohe_feng has quit IRC07:44
*** shaohe_feng has joined #openstack-meeting-407:45
*** salv-orl_ has joined #openstack-meeting-407:47
*** salv-orl_ has quit IRC07:47
*** salv-orlando has joined #openstack-meeting-407:48
*** zenoway has joined #openstack-meeting-407:50
*** iyamahat has joined #openstack-meeting-407:51
*** zeih has joined #openstack-meeting-407:53
*** shaohe_feng has quit IRC07:54
*** shaohe_feng has joined #openstack-meeting-407:55
*** GB21 has quit IRC07:55
*** sacharya has joined #openstack-meeting-407:58
*** sacharya has quit IRC08:03
*** shaohe_feng has quit IRC08:04
*** ricolin has quit IRC08:07
*** shaohe_feng has joined #openstack-meeting-408:08
*** gangil1 has joined #openstack-meeting-408:08
*** Niham has joined #openstack-meeting-408:09
*** Niham has quit IRC08:10
*** gangil has quit IRC08:10
*** Niham has joined #openstack-meeting-408:10
*** Niham has quit IRC08:10
*** thorst_ has joined #openstack-meeting-408:14
*** shaohe_feng has quit IRC08:15
*** Niham has joined #openstack-meeting-408:15
*** shaohe_feng has joined #openstack-meeting-408:16
*** iyamahat has quit IRC08:17
*** yamahata has quit IRC08:17
*** ricolin has joined #openstack-meeting-408:19
*** thorst_ has quit IRC08:21
*** GB21 has joined #openstack-meeting-408:21
*** shaohe_feng has quit IRC08:25
*** shaohe_feng has joined #openstack-meeting-408:28
*** shaohe_feng has quit IRC08:35
*** zhurong has quit IRC08:36
*** shaohe_feng has joined #openstack-meeting-408:36
*** zhurong has joined #openstack-meeting-408:37
*** pbourke has quit IRC08:39
*** pbourke has joined #openstack-meeting-408:39
*** gangil has joined #openstack-meeting-408:44
*** gangil1 has quit IRC08:45
*** shaohe_feng has quit IRC08:45
*** shaohe_feng has joined #openstack-meeting-408:46
*** shaohe_feng has quit IRC08:56
*** shaohe_feng has joined #openstack-meeting-408:57
*** zeih has quit IRC09:00
*** shaohe_feng has quit IRC09:06
*** gangil1 has joined #openstack-meeting-409:07
*** gangil has quit IRC09:08
*** kinapa has quit IRC09:08
*** shaohe_feng has joined #openstack-meeting-409:09
*** gangil1 has quit IRC09:14
*** gangil has joined #openstack-meeting-409:14
*** shaohe_feng has quit IRC09:16
*** shaohe_feng has joined #openstack-meeting-409:17
*** sambetts|afk is now known as sambetts09:17
*** gangil1 has joined #openstack-meeting-409:18
*** gangil has quit IRC09:18
*** thorst_ has joined #openstack-meeting-409:19
*** fawadkhaliq has quit IRC09:24
*** fawadkhaliq has joined #openstack-meeting-409:24
*** thorst_ has quit IRC09:26
*** gangil1 has quit IRC09:26
*** shaohe_feng has quit IRC09:26
*** ricolin has quit IRC09:27
*** shaohe_feng has joined #openstack-meeting-409:28
*** GB21 has quit IRC09:30
*** Niham has quit IRC09:32
*** javeriak has quit IRC09:34
*** zeih has joined #openstack-meeting-409:36
*** nmadhok1 has quit IRC09:36
*** shaohe_feng has quit IRC09:37
*** shaohe_feng has joined #openstack-meeting-409:38
*** zeih has quit IRC09:40
*** zhurong has quit IRC09:43
*** zhurong has joined #openstack-meeting-409:44
*** shaohe_feng has quit IRC09:47
*** shaohe_feng has joined #openstack-meeting-409:48
*** eslamelhusseiny has joined #openstack-meeting-409:50
*** dshakhray has joined #openstack-meeting-409:56
*** tfukushima has quit IRC09:57
*** shaohe_feng has quit IRC09:57
*** tfukushima has joined #openstack-meeting-409:57
*** shaohe_feng has joined #openstack-meeting-409:58
*** GB21 has joined #openstack-meeting-409:59
*** eslamelhusseiny has quit IRC09:59
*** zeih has joined #openstack-meeting-410:03
*** dshakhray has quit IRC10:03
*** matrohon has quit IRC10:04
*** dshakhray has joined #openstack-meeting-410:06
*** shaohe_feng has quit IRC10:07
*** zeih has quit IRC10:08
*** shaohe_feng has joined #openstack-meeting-410:08
*** Niham has joined #openstack-meeting-410:11
*** javeriak has joined #openstack-meeting-410:12
*** alexchadin has quit IRC10:13
*** salv-orl_ has joined #openstack-meeting-410:14
*** xingchao has quit IRC10:15
*** salv-orlando has quit IRC10:17
*** shaohe_feng has quit IRC10:18
*** shaohe_feng has joined #openstack-meeting-410:18
*** alexchadin has joined #openstack-meeting-410:20
*** Niham has quit IRC10:20
*** alexchadin has quit IRC10:21
*** alexchadin has joined #openstack-meeting-410:22
*** alexchadin has quit IRC10:24
*** d0ugal has quit IRC10:24
*** d0ugal has joined #openstack-meeting-410:28
*** shaohe_feng has quit IRC10:28
*** shaohe_feng has joined #openstack-meeting-410:29
*** d0ugal has quit IRC10:31
*** tfukushima has quit IRC10:31
*** d0ugal has joined #openstack-meeting-410:31
*** rtheis has joined #openstack-meeting-410:35
*** sdague has joined #openstack-meeting-410:37
*** shaohe_feng has quit IRC10:38
*** shaohe_feng has joined #openstack-meeting-410:39
*** Niham has joined #openstack-meeting-410:40
*** Niham has quit IRC10:40
*** Niham has joined #openstack-meeting-410:41
*** javeriak has quit IRC10:41
*** Niham has quit IRC10:42
*** Niham has joined #openstack-meeting-410:42
*** Niham has quit IRC10:43
*** Niham has joined #openstack-meeting-410:44
*** Niham has quit IRC10:45
*** Niham has joined #openstack-meeting-410:46
*** shaohe_feng has quit IRC10:48
*** shaohe_feng has joined #openstack-meeting-410:49
*** njohnston has quit IRC10:54
*** njohnston has joined #openstack-meeting-410:55
*** yamamoto_ has quit IRC10:56
*** javeriak has joined #openstack-meeting-410:58
*** shaohe_feng has quit IRC10:59
*** seanmurphy has quit IRC10:59
*** shaohe_feng has joined #openstack-meeting-410:59
*** zhurong has quit IRC11:04
*** yuli_s has joined #openstack-meeting-411:06
*** shaohe_feng has quit IRC11:09
*** shaohe_feng has joined #openstack-meeting-411:10
*** shaohe_feng has quit IRC11:19
*** shaohe_feng has joined #openstack-meeting-411:20
*** iurygregory has joined #openstack-meeting-411:26
*** thorst_ has joined #openstack-meeting-411:27
*** shaohe_feng has quit IRC11:29
*** shaohe_feng has joined #openstack-meeting-411:30
*** fawadkhaliq has quit IRC11:30
*** javeriak has quit IRC11:31
*** zeih has joined #openstack-meeting-411:31
*** ninag has joined #openstack-meeting-411:34
*** ninag has quit IRC11:38
*** zeih has quit IRC11:38
*** shaohe_feng has quit IRC11:40
*** shaohe_feng has joined #openstack-meeting-411:40
*** seanmurphy has joined #openstack-meeting-411:42
*** fwdit has quit IRC11:45
*** fwdit has joined #openstack-meeting-411:46
*** shaohe_feng has quit IRC11:50
*** shaohe_feng has joined #openstack-meeting-411:51
*** zeih has joined #openstack-meeting-411:59
*** sacharya has joined #openstack-meeting-412:00
*** shaohe_feng has quit IRC12:00
*** shaohe_feng has joined #openstack-meeting-412:01
*** ddieterly has joined #openstack-meeting-412:03
*** sacharya has quit IRC12:06
*** alexchadin has joined #openstack-meeting-412:08
*** shaohe_feng has quit IRC12:10
*** alexchadin has quit IRC12:12
*** nmadhok has joined #openstack-meeting-412:12
*** shaohe_feng has joined #openstack-meeting-412:13
*** markvoelker has joined #openstack-meeting-412:16
*** javeriak has joined #openstack-meeting-412:20
*** shaohe_feng has quit IRC12:21
*** javeriak_ has joined #openstack-meeting-412:21
*** shaohe_feng has joined #openstack-meeting-412:21
*** markvoelker has quit IRC12:21
*** piet has joined #openstack-meeting-412:22
*** woodard has joined #openstack-meeting-412:22
*** markvoelker has joined #openstack-meeting-412:24
*** GB21 has quit IRC12:24
*** ddieterly is now known as ddieterly[away]12:25
*** javeriak has quit IRC12:25
*** cartik has quit IRC12:29
*** shaohe_feng has quit IRC12:31
*** shaohe_feng has joined #openstack-meeting-412:31
*** sdague has quit IRC12:32
*** julim has joined #openstack-meeting-412:34
*** piet has quit IRC12:36
*** piet has joined #openstack-meeting-412:37
*** ninag has joined #openstack-meeting-412:38
*** banix has joined #openstack-meeting-412:39
*** vincentfrancoise has left #openstack-meeting-412:40
*** nmadhok has quit IRC12:40
*** shaohe_feng has quit IRC12:41
*** markvoelker has quit IRC12:41
*** markvoelker has joined #openstack-meeting-412:42
*** shaohe_feng has joined #openstack-meeting-412:42
*** sdague has joined #openstack-meeting-412:43
*** ninag has quit IRC12:43
*** kylek3h has joined #openstack-meeting-412:44
*** markvoelker_ has joined #openstack-meeting-412:46
*** ninag_ has joined #openstack-meeting-412:47
*** baoli has joined #openstack-meeting-412:48
*** ddieterly[away] is now known as ddieterly12:48
*** markvoelker_ has quit IRC12:48
*** baoli_ has joined #openstack-meeting-412:49
*** markvoelker_ has joined #openstack-meeting-412:49
*** markvoelker has quit IRC12:50
*** salv-orl_ has quit IRC12:50
*** mbound has joined #openstack-meeting-412:51
*** shaohe_feng has quit IRC12:51
*** shaohe_feng has joined #openstack-meeting-412:52
*** klamath has joined #openstack-meeting-412:52
*** baoli has quit IRC12:52
*** markvoelker_ has quit IRC12:55
*** markvoelker has joined #openstack-meeting-412:55
*** klamath has quit IRC12:57
*** ddieterly has quit IRC12:57
*** klamath has joined #openstack-meeting-412:57
*** shaohe_feng has quit IRC13:02
*** shaohe_feng has joined #openstack-meeting-413:02
*** dshakhray has quit IRC13:05
*** sdague has quit IRC13:07
*** pmesserli has joined #openstack-meeting-413:09
*** sdague has joined #openstack-meeting-413:10
*** markvoelker_ has joined #openstack-meeting-413:12
*** markvoelker_ has quit IRC13:12
*** shaohe_feng has quit IRC13:12
*** dave-mccowan has joined #openstack-meeting-413:12
*** markvoelker_ has joined #openstack-meeting-413:12
*** shaohe_feng has joined #openstack-meeting-413:13
*** markvoelker has quit IRC13:15
*** sshnaidm has quit IRC13:18
*** hvprash has joined #openstack-meeting-413:18
*** bobh has joined #openstack-meeting-413:19
*** sshnaidm has joined #openstack-meeting-413:20
*** rbak has quit IRC13:22
*** shaohe_feng has quit IRC13:22
*** shaohe_feng has joined #openstack-meeting-413:25
*** irenab has quit IRC13:26
*** alexchadin has joined #openstack-meeting-413:29
*** dshakhray has joined #openstack-meeting-413:30
*** ddieterly has joined #openstack-meeting-413:32
*** shaohe_feng has quit IRC13:32
*** shaohe_feng has joined #openstack-meeting-413:33
*** jichen has quit IRC13:33
*** javeriak_ has quit IRC13:34
*** cemason1 has joined #openstack-meeting-413:35
*** cemason has quit IRC13:37
*** rbak has joined #openstack-meeting-413:38
*** javeriak has joined #openstack-meeting-413:38
*** alexchadin has quit IRC13:42
*** shaohe_feng has quit IRC13:43
*** javeriak has quit IRC13:44
*** markvoelker_ has quit IRC13:44
*** ddieterly is now known as ddieterly[away]13:45
*** shaohe_feng has joined #openstack-meeting-413:45
*** Niham has quit IRC13:45
*** anilvenkata has quit IRC13:47
*** jmckind has joined #openstack-meeting-413:48
*** JRobinson__ has quit IRC13:48
*** piet has quit IRC13:48
*** spotz_zzz is now known as spotz13:50
*** zhurong has joined #openstack-meeting-413:52
*** ddieterly[away] is now known as ddieterly13:52
*** shaohe_feng has quit IRC13:53
*** shaohe_feng has joined #openstack-meeting-413:54
*** bpoulos has joined #openstack-meeting-413:54
*** piet has joined #openstack-meeting-413:55
*** abhishek has joined #openstack-meeting-413:55
*** belmoreira has quit IRC13:55
*** belmoreira has joined #openstack-meeting-413:55
*** kairat has joined #openstack-meeting-413:57
*** tsymanczyk has joined #openstack-meeting-413:57
*** tsymanczyk has left #openstack-meeting-413:58
nikhilCourtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat13:58
*** tsymanczyk has joined #openstack-meeting-413:58
hemanthmo/13:58
tsymanczyk\o13:58
jokke_o/13:58
abhisheko/13:58
dshakhrayo/13:58
*** mfedosin has joined #openstack-meeting-413:58
kairato/13:59
wxyo/13:59
rosmaitai think we are running early!13:59
mfedosino/13:59
jokke_rosmaita: 1min to go13:59
tsymanczyktoo exciting to wait14:00
rosmaita:)14:00
nikhil#startmeeting glance14:00
openstackMeeting started Thu May 19 14:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
nikhilWelcome everyone14:00
*** sudipto has joined #openstack-meeting-414:00
bpouloso/14:00
nikhilwe've a small agenda today14:00
sudiptoo/14:00
nikhilohai bpoulos14:00
nikhilwelcome back14:00
bpouloshello, thanks!14:00
nikhilcongrats!!!14:00
jokke_bpoulos: \o14:00
bpoulosthank you :)14:01
rosmaitao/14:01
nikhilhow's your 'boy?'?14:01
jokke_bpoulos: all good?14:01
bpoulosdoing very well, 15 pounds already!14:01
mfedosinhow did you call him?14:01
tsymanczykmazel tov14:01
bpoulosGregory14:01
nikhilnice! good news indeed :)14:01
*** ninag_ has quit IRC14:02
nikhilso, here's the agenda for today:14:02
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
nikhilPlease be mindful of the dates when you propose the agenda14:02
nikhilI usually keep next week's agenda open in case this week's full14:03
*** ninag has joined #openstack-meeting-414:03
nikhilWe have decided to limit the agenda to only 4 items per meeting (besides updates and open discussion)14:03
*** shaohe_feng has quit IRC14:03
nikhil#action nikhil update the etherpad with more info on adding items to agenda14:03
nikhilLet's get started.14:04
*** shaohe_feng has joined #openstack-meeting-414:04
nikhil#topic Updates14:04
*** openstack changes topic to "Updates (Meeting topic: glance)"14:04
nikhil#info Glare updates ( mfedosin )14:04
mfedosinhello again14:04
mfedosintwo main things14:04
mfedosin1. api spec14:05
mfedosinI think we are ready to public discussion14:05
*** ninag_ has joined #openstack-meeting-414:05
*** user154752_ has joined #openstack-meeting-414:05
mfedosinfor that reason I'll update the spec, add API examples that Darja made and upload new PS today14:05
mfedosinthen I'm going to send a message to ML and ask for review14:06
*** Niham has joined #openstack-meeting-414:06
mfedosinI hope it will be done early tomorrow14:06
mfedosin2. Glare code14:06
*** salv-orlando has joined #openstack-meeting-414:07
mfedosinKairat and Darja are fixing bugs14:07
*** piet has quit IRC14:07
mfedosin6 of known 7 are done14:07
*** cemason1 has quit IRC14:07
mfedosinthat means that code is pretty stable at the moment14:07
jokke_nice14:07
nikhilmfedosin: this is good news indeed14:07
*** ninag has quit IRC14:07
nikhilwe're getting to discussion early in cycle14:07
mfedosinwe still have to add several features14:08
nikhilok14:08
mfedosinbut my proposal, that in early June we'll start to prepare the code for merging14:08
mfedosinkairat: dshakhray correct me if I'm wrong14:08
kairatI hope so14:09
*** avarner has quit IRC14:09
mfedosinbut now, we need to concentrate on the spec14:09
mfedosinif API is agreed, then we can start implementing glare client14:10
mfedosinI think this is all the updates at the moment.14:11
nikhilmfedosin: I think we need next meeting to decide on the features later (including more code like client). we agreed to a skeleton patch first, just to make sure that the team can focus on the bare minimum code.14:11
nikhilmfedosin: and on the note to ML please link all tags that were interested. we need everyone on same page when it comes to the API!14:11
mfedosinyeah, sure14:11
*** spotz is now known as spotz_zzz14:11
nikhil#info Nova v1, v2 ( mfedosin , sudipto )14:11
*** salv-orlando has quit IRC14:11
nikhil#link https://review.openstack.org/#/c/301741/14:11
mfedosinhooray14:12
nikhilSO, great news14:12
*** yamamoto has joined #openstack-meeting-414:12
mfedosinthanks sudipto and flaper8714:12
nikhilwe have 3 different people +2 on it already14:12
nikhilgreat job all three!14:12
sudiptocheers mfedosin nikhil14:13
nikhil(Acutally let's inclde Eddie on this good news too)14:13
nikhilSO, what remains?14:13
nikhilsudipto: mfedosin  ?14:13
mfedosinemm, I think we need some clarification about v2 gate14:13
*** shaohe_feng has quit IRC14:13
nikhilmfedosin: I can update that later14:14
sudiptofrom the coding front, i think we are sorted.14:14
*** jmckind_ has joined #openstack-meeting-414:14
nikhilthere was a mention about some code changes required in sudipto 's later spec patches?14:14
mfedosinbecause it blocks me from writing the code14:14
*** shaohe_feng has joined #openstack-meeting-414:14
nikhilk14:15
mfedosinalso I updated sudipto's second patch14:15
mfedosinand fixed unit tests there14:15
mfedosinwill upload new PS in a moment14:15
nikhilthx mfedosin14:15
mfedosinalso, as I mentioned, code is done14:16
mfedosinit's WIP but anyway14:16
mfedosin#link https://review.openstack.org/#/c/316440/14:16
*** jmckind has quit IRC14:17
mfedosinunit tests will be fixed in sudipto's commit14:17
sudiptoyeah14:17
sudiptoSo i am in sync with mfedosin and we should be able to put out all the reviews shortly after the spec is merged.14:17
*** zhurong has quit IRC14:18
mfedosinthe main point is that all tempests are good :)14:18
mfedosinsudipto: even earlier :)14:18
sudiptomfedosin, sure. Also I will work on the driver changes - that still use v1 - like i discussed with you.14:18
sudiptomfedosin, i think we might be able to merge the spec today :)14:19
nikhilok, great stuff.14:19
mfedosinwhat driver again?14:19
mfedosinah14:19
nikhilLet's focus on the spec first14:19
mfedosinnow spec is not our job14:19
mfedosinlet's nova team review and merge it :)14:20
nikhilThat should be our priority, but looks good for now. Just keep an eye out for any last minute reviews :/14:20
mfedosin*let14:20
sudiptonikhil, sure.14:20
mfedosinalso I have related question...14:20
mfedosinbut let's postpone it to Open Discussion14:20
nikhilmfedosin: this is openstack, we can only talk about merge only after the release. there are no guarantees until then.14:20
*** unicell1 has joined #openstack-meeting-414:20
nikhillet14:21
nikhillet's move on, we need to have this detailed sync 30 mins before artifacts meeting on monday14:21
*** unicell has quit IRC14:21
nikhillet's keep our thursday updates small14:21
nikhilThanks much sudipto  mfedosin14:21
nikhil#info Releases14:21
nikhilSo, we're approaching newton-114:22
nikhilnewton-1 Thursday June 2:14:22
mfedosinoh... so fast14:22
nikhilhttp://releases.openstack.org/newton/schedule.html14:22
nikhilyes, so just one more week and the week after we will tag newton 114:22
*** fwdit has quit IRC14:23
nikhilalthough the release page says thursdays are generally the dates when the release is cut14:23
nikhillet14:23
nikhillet's make sure that we get things done by Monday so that release team can cut the same on Tuesdays14:23
nikhilThat means all reviews to be done by Friday and keeping Monday for gate, last minute additions, etc. reviews14:24
*** shaohe_feng has quit IRC14:24
nikhilThanks!14:24
nikhil#info Announcements14:24
nikhil1) Should we cancle the mid-cycle or there's last minute interest developed? Last time I checked there were 4 who were almost confirmed.14:24
* nikhil waits for feedback14:25
*** shaohe_feng has joined #openstack-meeting-414:25
tsymanczykthings have changed slightly here. i don't know that i could get approved anymore.14:25
mfedosinunfortunately I won't be able to come :(14:25
jokke_same here14:25
rosmaitaby "cancel" i assume you mean "make into a virtual meeting" ?14:26
*** iyamahat has joined #openstack-meeting-414:26
mfedosinright14:26
nikhilrosmaita: surely. but the plan is to have regular (~monthly) virtual meetings so, not exactly substitution.14:26
nikhilI was going to propose a virtual one right after newton 114:27
nikhiland the one after can be around our midcycle dates.14:27
rosmaitaworks for me14:27
*** belmoreira has quit IRC14:27
kairat+1 to virtual only14:27
nikhilAtleast for a few things, so that we're not proposing another 4 hour slots everytime.14:28
nikhilok, thanks all.14:28
nikhil#agreed Glance midcycle meetup to be cancelled cc/ sabari14:28
nikhil#info Priorities14:28
*** fawadkhaliq has joined #openstack-meeting-414:29
nikhilI started a WIP review last week but due to ML discussions it is in delay.14:29
nikhilhere's a patch up:14:29
nikhil#link https://review.openstack.org/#/c/315752/14:29
nikhilI've also sent announcement email on the priorities and processes. Will be taking that into account before this is final.14:30
nikhilGood points brought up by a few people over last few weeks, something that's been communicated in different threads:14:30
nikhilSide-priorities (in Mitaka it was called priorities w/o clear plan)14:30
mfedosinnikhil: just curious about Glare there14:30
nikhilElements that will need more baby sitting, are non-controvertial and less research or dependencies.14:31
nikhilThey should be considered side-priorities.14:31
mfedosinI think we have to say several words about artifacts in this doc, right?14:31
nikhilCurrently, we've Glare, registry and v1 deprecation and part of categorization effort. Also, we should include lite-specs.14:31
*** galstrom_zzz is now known as galstrom14:32
nikhilmfedosin: correct, this is all as per what we agreed at the summit.14:32
hemanthmcan we document them as well?14:32
*** ninag_ has quit IRC14:32
nikhilmfedosin: the more info we can provide the better it will be.14:32
mfedosinalso I think we must include sudipto in Nova v1-v2 work14:33
nikhilhemanthm: yes, I plan to include as much info on that review. you can provide feedback on gerrit while we work on them collaboratively. BUT we need to stay very close to what has been agreed at the summit.14:33
mfedosinnikhil: currently only me, you and flaper87 are listed there14:33
hemanthmnikhil: +114:33
*** fawadkhaliq has quit IRC14:33
nikhilmfedosin: noted14:33
nikhilmfedosin: you not giving me any cake for all my reviews on your spec ;-) (jk)14:34
nikhilanything else?14:34
*** shaohe_feng has quit IRC14:34
nikhilmoving on, then..14:34
*** shaohe_feng has joined #openstack-meeting-414:34
nikhil#topic Lite-specs process finalizing14:34
*** openstack changes topic to "Lite-specs process finalizing (Meeting topic: glance)"14:34
mfedosinnick-ma: in Barselona14:34
mfedosin*nikhil:14:34
nikhilmfedosin: ?14:35
nikhilmfedosin: if not on lite-specs we need to discuss later. running short of time atm.14:35
sudiptonikhil, guess he means the cake. :)14:36
*** zeih has quit IRC14:36
nikhilsudipto: mfedosin : gotcha. I am looking forward to it. you said it now ;)14:36
mfedosinsudipto: correct :)14:36
nikhil#link https://review.openstack.org/#/c/315339/14:36
jokke_there was lots of good comments in the review for lite-spec doc change14:36
nikhilyes, thanks!14:36
nikhilSo, we need the following:14:37
nikhil1) use-case, very good problem statement14:37
nikhil2) all the affected domains (notification, security, operator, end user, etc)14:37
*** banix has quit IRC14:37
jokke_if we're using the same template, it's quite self explanary14:37
nikhil3) scope of the implementation, hurdles or any workarounds that we need to do14:37
*** belmoreira has joined #openstack-meeting-414:38
*** dtardivel has joined #openstack-meeting-414:38
nikhilAs of current proposal by flaper87 , there's no enforcement on using that template.14:38
hemanthmI think that was implied14:38
nikhilthere's loose coupling with what we need and what's expected.14:38
hemanthmuse the template for the content on the commit message14:39
jokke_I did read that ... I'd like to see us enforcing renos and proper commit messages before we agree using them as lite-specs14:39
nikhil#action all interested on lite-specs: please explicitly state what your thougts are on the proposal(s)14:39
jokke_no-one is writing them currently14:39
nikhilok, good point jokke_14:39
kairatok14:40
kairatI am also in favor of reno and cm only14:40
nikhillet's make sure that we get that in the reviewer's guide14:40
kairatwe don't have enough review bandwidth for specs14:40
nikhilI don't mind as long as:14:40
hemanthmalthough I'm not sure if we can drop indexing like flaper87 mentioned in his latest comment14:40
nikhil1) they are discoverable14:40
nikhil2) they can be used for referencing outside of glance or code14:40
nikhil3) people won't have to click on 15 pages underneath the doc page to look for them14:41
nikhilwe're getting a lot of heat on documentation so we need to ensure we increase docs at least two folds14:41
*** irenab has joined #openstack-meeting-414:41
nikhilkairat: having them in specs makes us aware of the review bandwidth we can commit to them in a cycle14:42
*** cloudtrainme has joined #openstack-meeting-414:42
*** piet has joined #openstack-meeting-414:42
nikhilthe point I'm tring to make is we get specs and lite-specs done first in cycle (before 15th June on soft freeze and early July on hard freeze)14:42
jokke_that's the second problem there ... the drivers to move lite-specs to the glance-specs repo were following: 1) no-one is writing the renos 2) we need to document out new features at least somewhere where they are all easily findable 3) amendments to the old specs like Niall's deactivation stuff14:42
nikhilthat way we know what's in the pipe and what we can actually tackle14:42
*** yamahata has joined #openstack-meeting-414:43
jokke_yes bandwith planning was the number 414:43
hemanthmwith what flaper87 proposed, we don't have to do spec reviews separately for lite-specs14:43
kairatHmm, I am not sure review for specs will give us enough info about planning14:43
kairatbecause usually it just doubles review time for me14:44
*** sdake_ has joined #openstack-meeting-414:44
kairatwill describe that in spec14:44
nikhilbut we don't know how much we need to review and how much we can ignore in a cycle14:44
nikhilI don't want proposers thinking and pushing before newton-3 that it's possible for them to propose something and get it merged14:44
*** shaohe_feng has quit IRC14:44
nikhilwe need a way to avoid many behavior changes in one cycle14:44
nikhiland we need to do that early14:45
hemanthm+114:45
nikhilok, we can keep this discussion going on the review14:45
hemanthmI guess having the lite-spec and code in the same commit doesn't help with planning much14:45
*** yamamoto has quit IRC14:45
*** shaohe_feng has joined #openstack-meeting-414:45
nikhilright14:45
nikhilSo, there are good points raised here, please make sure you jot them down completely on that review patch.14:45
jokke_sure I retype my points there as gerrit was so nice and wiped my last round earlier today14:45
nikhil(please do not be implicit)14:46
*** unicell1 has quit IRC14:46
nikhilok, moving on for now.14:46
*** raddaoui has joined #openstack-meeting-414:47
nikhil#topic Codec can't encode characters14:47
*** openstack changes topic to "Codec can't encode characters (Meeting topic: glance)"14:47
nikhil#link https://review.openstack.org/#/c/316054/14:47
nikhildshakhray: floor is yours14:47
mfedosinokay, it's dshakhray's fix14:47
mfedosinI thinks she wants you to review the code14:47
*** sigmavirus24_awa is now known as sigmavirus2414:48
nikhilk14:48
dshakhrayyes, only review)14:48
mfedosinheaders were encoded in HTTPclient14:48
*** dandruta has joined #openstack-meeting-414:48
mfedosinbut when we started to use SessionClient they are not14:49
mfedosinso Darja fixed it :)14:49
*** salv-orlando has joined #openstack-meeting-414:49
*** tonytan4ever has joined #openstack-meeting-414:49
nikhilcool14:49
*** majklkcz has quit IRC14:49
nikhillet's get that reviewed then14:49
nikhil#topic open discussion14:50
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:50
nikhilthere's another request for review here:14:50
mfedosinI wanted to ask one thing...14:50
nikhilReturn request-id to caller14:50
jokke_dshakhray: change itself seems to make sense. Please be bit more verbal on the commit message. Currently the commit message and the change are not telling the same story14:50
abhishekhi, need reviews for return request id to caller, have proposed two solutions, https://review.openstack.org/#/c/261288/ and https://review.openstack.org/#/c/316052/14:50
nikhilhttps://review.openstack.org/#/c/261288/14:50
nikhilhttps://review.openstack.org/#/c/316052/14:50
abhishek2nd one is proposed by Brant and Cao, please provide your feedback on it as per time permits14:51
nikhil+1 to jokke_  on commit message14:51
nikhilmfedosin: please go ahead14:51
mfedosinin Nova for some deployments we have to enable show_multiple_locations14:51
mfedosinand if you read message from Heat in ML they always need it to use Glance v214:52
jokke_abhishek: do those overlap with 7150ceee1ac72361f75b3a4187e10a884166870d that I noticed had been merged lately14:52
nikhilwell14:52
mfedosinbut this option has a vulnerability14:52
abhishekjokke_: let me have a look14:52
nikhilmfedosin: for long term this is what we want to do https://review.openstack.org/#/c/313936/14:53
*** spotz_zzz is now known as spotz14:53
mfedosinso, I propose to change image_location_quota default from 10 to 114:53
*** fesp has joined #openstack-meeting-414:53
mfedosinnikhil: doesn't matter14:53
nikhilthat does reduce it a bit14:54
mfedosinfor Heat and Nova we have to allow to set custom locations for all users14:54
jokke_that is really really problematic14:54
nikhilmfedosin: I don't know why we need to allow for all users14:54
kairatmfedosin, it may break some templates after glance upgrade14:54
abhishekjokke_: could you please provide a link14:54
*** shaohe_feng has quit IRC14:54
mfedosinnikhil: to make snapshot, for example14:55
jokke_the whole locations code is really really problematic as long as we do not have service tokens14:55
*** shaohe_feng has joined #openstack-meeting-414:55
mfedosinif this option is disabled...14:55
jokke_abhishek: I don't have one ... that's commit id from glanceclient git log14:55
*** unicell has joined #openstack-meeting-414:55
abhishekjokke: ok I will have a look and let you know14:56
*** julim has quit IRC14:56
wxyHere is one situation: Heat want to use Glance v2 instead of v1. But we can't set locations as v1 did by default.14:56
mfedosinthis won't work https://github.com/openstack/nova/blob/824c3706a3ea691781f4fcc4453881517a9e1c55/nova/virt/libvirt/imagebackend.py#L96714:56
*** julim has joined #openstack-meeting-414:56
mfedosinhttps://github.com/openstack/nova/blob/824c3706a3ea691781f4fcc4453881517a9e1c55/nova/virt/libvirt/driver.py#L151714:56
jokke_mfedosin: are you saying that currently every deployment is changing that locations option on?14:56
*** ninag_ has joined #openstack-meeting-414:56
nikhilmfedosin: I thought that driver was already using v2 and image locations ?14:56
*** hvprash_ has joined #openstack-meeting-414:56
kairatyes, because it uses v114:56
mfedosinno, it uses v1 to set location14:57
nikhilmfedosin: and our scope should not increase beyond that driver14:57
kairatwxy, thanks, i forgot about that14:57
nikhilmfedosin: nova folks need to be more aware apparently14:57
nikhilmfedosin: ok14:57
wxyHeat team want to upgrade to v214:57
nikhilwxy: I am aware of that14:57
*** jmckind has joined #openstack-meeting-414:57
nikhilwxy: and I have responded very clearly. but no response back !14:57
jokke_nikhil: ++14:58
mfedosinso, reducing this parameter from 10 to 1 will prevent a lot of bad issues14:58
nikhilmfedosin: so for the 'lot' part, please start a email thread with the glance-core-sec for now14:58
nikhilmfedosin: we can then involve people who have more to say14:58
mfedosinikay14:59
mfedosinokay14:59
nikhilrosmaita: you got a min14:59
jokke_2min14:59
jokke_1 left :P14:59
rosmaitamore like 30 sec14:59
*** TravT has joined #openstack-meeting-414:59
nikhil:)14:59
jokke_type faster14:59
rosmaitahave a nice day, everyone14:59
nikhilTravT: is generous in not kicking us out :)14:59
rosmaitai will bug people individually in glance channel14:59
nikhilok15:00
TravT:)15:00
nikhilThanks all!15:00
*** hvprash has quit IRC15:00
mfedosinthanks15:00
jokke_thanks all15:00
nikhil#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
*** bpoulos has left #openstack-meeting-415:00
openstackMeeting ended Thu May 19 15:00:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.txt15:00
*** tsymanczyk has left #openstack-meeting-415:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.log.html15:00
*** jmckind_ has quit IRC15:00
*** kairat has left #openstack-meeting-415:00
rosmaitaTravT: sorry about the -2 on your https://review.openstack.org/#/c/318365/, but i need some negative grades for my stats15:01
*** ddieterly is now known as ddieterly[away]15:01
TravTlol15:01
*** ddieterly[away] is now known as ddieterly15:01
*** abhishek has quit IRC15:01
*** lei-zh has joined #openstack-meeting-415:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu May 19 15:01:39 2016 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
TravTrosmaita: thanks for looking at it with a close eye!15:02
rosmaitanp15:02
*** sjmc7 has joined #openstack-meeting-415:02
sjmc7ello15:02
TravTo/15:02
lei-zho/15:02
TravTsjmc7 i think Rick-A was supposed to be back today15:03
TravTbut he's not showing online yet15:03
TravTanyway, let's get going. maybe yingjun is sleeping tonight.... :)(15:04
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:04
TravT#topic Lei Zhang core nomination15:04
*** openstack changes topic to "Lei Zhang core nomination (Meeting topic: openstack search)"15:04
TravTFYI http://lists.openstack.org/pipermail/openstack-dev/2016-May/095270.html15:04
TravTlei-zh has been doing a great job, i think.15:05
*** shaohe_feng has quit IRC15:05
TravTshould be able to finalize by end of day tomorrow or Monday.15:05
*** shaohe_feng has joined #openstack-meeting-415:05
TravT#topic Backport 0.2.115:06
*** openstack changes topic to "Backport 0.2.1 (Meeting topic: openstack search)"15:06
TravTwe only have a couple more candidates for backport which are already landed on master15:06
TravTsjmc7: can you propose this for backport?15:07
TravThttps://review.openstack.org/#/c/311834/15:07
sjmc7yes indeedy15:07
TravTand then i was wondering if we should go ahead and backport this one from lei-zh15:07
TravThttps://review.openstack.org/#/c/30929015:07
*** yingjun has joined #openstack-meeting-415:07
TravThi yingjun15:07
sjmc7i don’t think we need to do that one15:07
*** jaimguer has joined #openstack-meeting-415:07
*** avarner has joined #openstack-meeting-415:07
* yingjun late for meeting15:07
david-lyleo/15:07
TravThi david-lyle15:08
sjmc7it’s not clear when they’ll actually remove the ‘count’ search type15:08
jaimguero/15:08
TravThi jaimguer15:08
lei-zhit's deprecated in 2.x, but don't know when it doesn't work15:08
*** spzala has joined #openstack-meeting-415:08
sjmc7i suspect it’ll be a long time; it would make sense that they could translate that into a size=0 search internally rather than cause client issues15:09
sjmc7otoh it’s not a huge patch to backport15:09
TravTit is rather small.15:09
sjmc7i’m just wary of backporting too much because we start getting conflicts15:09
sjmc7but i could go either way15:10
TravTso, how about if it is a clean cherry pick we backport it?15:10
TravTotherwise we don't?15:10
TravTfyi yingjun talking about this one: https://review.openstack.org/#/c/30929015:10
yingjunTravT, thanks15:10
sjmc7it makes it more likely to get conflicts down the line too. i guess it’s ok to pick it15:11
*** user154752_ has quit IRC15:11
TravTokay, well, if we do backport it, i'll have to add to the release notes15:12
TravTi went ahead and posted a release notes patch on master (which we'll backport) that has notes for all the fixes since mitaka released15:12
TravThttps://review.openstack.org/#/c/318365/15:12
TravTso, let's try to get that done by end of day tomorrow.15:13
*** alex_xu has quit IRC15:13
david-lylewhat's the max e-s supported in 0.2.1 ?15:13
*** user154752 has joined #openstack-meeting-415:13
TravTwell, originally we were thinking 1.x, but ES changed their support for 1.x15:14
david-lylebut at release time, it was 1.x, correct?15:14
TravTyes.15:14
*** user154752_ has joined #openstack-meeting-415:14
TravTby the time some deployers get to deploying mitaka, es 1.x will be problematic for some deployers15:15
david-lylejust wondering why 2.0 support in a branch that won't upgrade E-S versions15:15
sjmc7and this option is still supported, just deprecated15:15
david-lyleseemingly searchlight and E-S will upgrade in tandem15:15
TravTthe changes for es 2.x were pretty minor for us15:15
*** shaohe_feng has quit IRC15:15
david-lyleright, but backporting them seems unnecessary15:16
TravTwell, for example david-lyle HP's deployment of mitaka will only include es 2.x15:16
*** avarner has quit IRC15:16
david-lylejust trying to apply stable policy15:16
david-lyleor analyze based on that criteria15:16
TravTwell, i was looking at that15:17
TravThttp://docs.openstack.org/project-team-guide/stable-branches.html15:17
sjmc7we won’t be using bleeding edge ES though15:17
TravTi believe all these patches apply while in phase 115:17
sjmc7it seems you’re set on backporting it, and i’m ok with that, dunno if we need to argue it too much15:17
TravTsjmc7: this particular patch i don't care too much15:17
TravTit was the others which actually prevent usage of es 2.x15:18
sjmc7e-s is a bit weird in that it’s not goign to be deployed via system packages like mysql would be15:18
*** user154752 has quit IRC15:18
sjmc7yeah, those i am definitely onboard with15:18
*** Niham has quit IRC15:18
TravTdavid-lyle: hp had to make a decision to upgrade to es 2.x for mitaka late in the game because of es support contracts going away for 1.x15:19
david-lyleI'm not trying to be difficult, but unless > 2.0 is supported in 0.2.1, I don't see the justification to backport15:19
sjmc7it is supported in a sense that we decided not to exclude it15:19
*** itisha has quit IRC15:19
sjmc7since it had been released for over 6 months15:20
david-lylesjmc7: by >2.0 I guess I'm meaning >=3.0 when the deprecation is removed15:20
*** yamahata has quit IRC15:20
TravTahh, on this patch.15:20
sjmc7that might be the case, yeah - they don’t specify15:20
*** iyamahat has quit IRC15:20
david-lyleI'll drop it, I know the stable team is trying to be more vigilant on what goes in to stable15:21
TravTokay, well, my arm is twisted on this patch15:21
TravThttps://review.openstack.org/#/c/30929015:21
TravTwe don't need to backport that one specifically15:21
sjmc7ok. other one’s got a backport review https://review.openstack.org/#/c/318729/15:21
*** ninag_ has quit IRC15:21
TravTso a few other items to discuss today15:22
TravT    upcoming changes to glance that will affect the searchlight plugin15:23
TravT#topic upcoming changes to glance that will affect the searchlight plugin15:23
*** openstack changes topic to "upcoming changes to glance that will affect the searchlight plugin (Meeting topic: openstack search)"15:23
TravTrosmaita put up a few BPs15:23
TravTi just wanted to check with people on the priority we should put on them15:23
TravThttps://blueprints.launchpad.net/searchlight/+spec/glance-visibility-changes-shared-community15:23
TravTthis seems like we should approve it and should consider giving it a high15:24
*** fawadkhaliq has joined #openstack-meeting-415:24
TravTthoughts?15:25
sjmc7yeah, agree15:25
rosmaitaspec isn't approved yet, but there's a dev dedicated to it, so the implementation should land15:25
*** hvprash has joined #openstack-meeting-415:26
rosmaitabut you won't have aything to work with for a while15:26
TravTyeah, we might need to mark it as blocked15:26
*** hvprash_ has quit IRC15:26
TravTso approve, but blocked until glance further along15:26
sjmc7ok. so keep an eye on it. if we don’t support it, worst case is some stuff is invisible when it shouldn’t be?15:26
TravTseems that way15:27
rosmaitamy real motivation was to get y'all to look at the spec in case there's anything bad for searchlight in the design15:27
sjmc7i don’t think so, long as we continue to get notifications on changes15:27
rosmaitaok15:27
sjmc7little bit curious how it’ll actually work :)15:27
TravTokay, the other one is this one: https://blueprints.launchpad.net/searchlight/+spec/glance-visibility-changes-inherited15:28
*** belmoreira has quit IRC15:28
rosmaitathat's fairly speculative at this point15:29
sjmc7your favourite subject, david-lyle - hierarchial tenants!15:29
rosmaitait's another heads-up to make sure what glance does is searchlight-friendly15:29
rosmaitaalthough, i don't think there's a detailed proposal yet15:29
TravTdavid-lyle probably goes home and writes songs about it, he loves it so much15:29
sjmc7i think the multitenant stuff may be a bit wait-and-see15:30
TravT;)15:30
TravTyeah, we can leave it as is for now15:30
sjmc7it’s definitely gonna cause us some problems15:30
sjmc7though i am hoping the request context will have the parent tenant id as well15:30
david-lyleTravT: :)15:30
TravTi suppose we really should look over that spec15:30
sjmc7which just leaves the problem of determining conceptually who should be able to see a resource (like extra ‘visibility’ flags)15:31
TravTrosmaita can you let us know if it looks like it is going to make it into newton for glance?15:31
rosmaitayes, i will keep you posted15:31
*** hvprash_ has joined #openstack-meeting-415:31
TravTi'll add myself as reviewer on the spec, but i have so many review notifications come in that it is easy to miss some15:32
david-lylerosmaita: no assignee15:32
david-lylethe odds seem long15:32
rosmaitaexcept the PTL is a fan15:32
david-lyleis he doing it?15:33
rosmaitanot sure15:33
yingjunWe were very interested in the hierarchial tenants thing here in our company year ago.15:33
david-lylewon't go far without an implementer15:33
rosmaitabut yeah, there is already a lot of stuff happening in newton for glance15:33
*** sudipto has quit IRC15:33
david-lyleI think HMT is going to be a 30' onion15:33
*** hvprash has quit IRC15:34
rosmaitai am not familiar with that expression15:34
david-lyleheck we couldn't even successfully use domains, but now we're going to handle deeper hierarchy15:34
david-lylerosmaita: large onion15:34
david-lyleso many layers to uncover15:35
TravTwell, i'll just mark it as drafting for now15:35
TravTbut not prioritize it15:35
TravTlet's move along a bit if we can15:35
* david-lyle remains a sceptic15:35
TravT#topic nova notifications updates15:35
*** openstack changes topic to "nova notifications updates (Meeting topic: openstack search)"15:35
TravTFYI, went to the versioning meeting yesterday15:36
TravTcomments from meeting were reflected on bottom of spec15:36
TravT https://review.openstack.org/#/c/286675/15:36
TravTbut basically15:36
TravTwith 1.0 of versioned notifications they are simply looking to get current notification data in15:36
TravTso there is compatibility of payload from current notifications to versioned notifications on existing types15:37
TravTfrom there, they'd like feedback on what additional data they should add after 1.0 for instances15:37
*** ninag has joined #openstack-meeting-415:37
sjmc7the comments from most people on there don’t leave me tremendously hopeful we’ll get what we want; consensus seems to be they want to reduce rather than add, and not much appetite for standardizing between notificaitons and the API15:37
TravTyeah, they said this is for technical reasons15:38
sjmc7i guess we’ll see. hopefully they can implement it reasonably quickly15:38
sjmc7and then we’ll find out what direction they take it15:38
TravTand to try to get 1.0 versioned notifications out in newton.15:38
TravTfor net new notifications, not so problematic15:38
TravTso, we'll keep watching there...15:39
TravTbut versioned notifications won't be a panacea in newton15:39
TravTwhich is why we all previously decided to try to reduce callbacks15:39
TravTsjmc7 started on that15:39
sjmc7yes. my patch is hideous!15:39
TravThttps://review.openstack.org/#/c/317100/15:39
sjmc7i will tidy it up some, but the overall hideousness will remain15:40
*** Swami has joined #openstack-meeting-415:40
sjmc7the primary option to reduce hideousness is not trying to keep track of status changes15:40
TravTsjmc7, i think your logic works15:41
TravTit is just hard to follow...15:41
TravTbecause nova notification flow is hard to follow15:41
sjmc7it really is. i’ll tidy it up; it kind of evolved as i went though it15:41
sjmc7the basic issue is that there can be conditions under which all the notifications arrive at once, which means requiring lots of special case conditions15:42
TravTturning on the option to only have a single listener thread and using pycharm debugger really helped with that one.15:42
sjmc7if we do that in production it becomes much simpler :)15:42
TravThahahaha15:42
TravTanyway, anything else to say or any questions from anybody or can we move on. just wanted to give status update15:43
*** minwang2 has joined #openstack-meeting-415:44
TravT#topic use pools15:44
*** openstack changes topic to "use pools (Meeting topic: openstack search)"15:44
TravT    https://bugs.launchpad.net/searchlight/+bug/158321515:44
openstackLaunchpad bug 1583215 in OpenStack Search (Searchlight) "Enable oslo.messaging pools support " [Medium,New] - Assigned to Steve McLellan (sjmc7)15:44
sjmc7aside from the 2 hours i spent tracking down a configuration issue with cinder, it looks like pools work and make deployment much easier; no need for multiple messaging topics15:45
*** automagically has joined #openstack-meeting-415:45
TravTthat would make deployment easier15:45
*** yamamoto has joined #openstack-meeting-415:46
TravTbut, does this mean configuration changes still in cinder or other services?15:46
sjmc7nope, nothing15:46
TravTthat's great15:46
*** numans has quit IRC15:46
TravTso, i'd like to prioritize this high, then15:46
sjmc7yeah, i’m gonna work on it this week15:47
*** jmckind_ has joined #openstack-meeting-415:47
TravTso basically, as long as services are already emitting notifications, no additional changes to deploy searchlight.15:47
sjmc7right15:48
TravTvery cool15:48
yingjunso with this change, we will no need to add a specific topic for sl ?15:48
sjmc7correct15:48
yingjunawesome15:48
sjmc7the ‘pool’ becomes a rabbitmq queue rather than the topic itself15:49
TravTwhen we first tried this in liberty, oslo messaging pools had bugs15:49
TravTbut that got sorted out since then15:49
sjmc7yeah. nobody seems to remember what the problem was :)15:50
TravTokay, one last thing on agenda, then open discussion.15:50
*** jmckind has quit IRC15:50
TravT#topic searchlight ui changes15:50
*** openstack changes topic to "searchlight ui changes (Meeting topic: openstack search)"15:50
*** sacharya has joined #openstack-meeting-415:51
TravTthere has been a lot of work going on in horizon to enable registration of views / actions / etc for various resource types15:51
*** jmccrory_ has joined #openstack-meeting-415:51
TravTfor the new angular work.15:51
*** IlyaG has joined #openstack-meeting-415:51
TravTtyr and matt-borland have been working together to do things that allow searchlight ui to best consume that work15:51
TravTso tyr has a number of patches up on searchlight ui15:52
*** cbits has joined #openstack-meeting-415:52
TravTi'll try to get other horizon reviewers to look at them as well15:52
sjmc7they’re all a bit over my head15:52
TravTbut one net affect is that you might have to go through a gyration or two to update horizon from master and update searchlight-ui with re-install a few times this cycle15:53
TravTto keep them in sync15:53
TravTokay... that's all on that.15:54
*** zenoway has quit IRC15:54
TravT#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:54
*** seanmurphy has quit IRC15:54
TravTFYI i will be out next week.15:54
TravTany volunteers to run the meeting?15:54
sjmc7yeah, i can do it15:54
TravTthanks15:54
TravTi'll be out thursday / friday15:55
TravTokay, lei-zh yingjun anything you want to bring up?15:55
*** prometheanfire has joined #openstack-meeting-415:56
*** thingee has joined #openstack-meeting-415:56
yingjunhttps://review.openstack.org/318432, please review15:56
TravTok15:56
*** zenoway has joined #openstack-meeting-415:56
*** trozet has quit IRC15:56
yingjunsimple fix15:56
lei-zhnope, just want to say I'm honored to join the team:)15:57
sjmc7:) welcome!15:57
TravTlei-zh: we're honored to have you!15:57
rosmaita+115:57
*** bpokorny has joined #openstack-meeting-415:57
david-lylewelcome15:57
*** yamamoto has quit IRC15:57
lei-zhthanks : )15:57
TravTokay, well thanks everybody!15:58
TravT#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Thu May 19 15:58:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-19-15.01.html15:58
*** sjmc7 has left #openstack-meeting-415:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-19-15.01.txt15:58
*** lei-zh has left #openstack-meeting-415:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-19-15.01.log.html15:58
*** yingjun has left #openstack-meeting-415:58
david-lylethanks TravT15:58
prometheanfireodyssey4me: hi15:59
*** armax has joined #openstack-meeting-415:59
*** trozet has joined #openstack-meeting-415:59
odyssey4me#startmeeting OpenStack-Ansible16:00
openstackMeeting started Thu May 19 16:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:00
openstackThe meeting name has been set to 'openstack_ansible'16:00
odyssey4me#topic Rollcall & Agenda16:00
*** openstack changes topic to "Rollcall & Agenda (Meeting topic: OpenStack-Ansible)"16:00
automagicallyo/16:00
spotz\o/ - But I'm also in the diversity meeting so please tag if really needed:)16:00
d34dh0r53o/16:00
errro/16:00
*** TravT has left #openstack-meeting-416:00
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:01
*** ametts has joined #openstack-meeting-416:01
*** evrardjp has joined #openstack-meeting-416:01
* mhayden woots16:01
*** sdake_ is now known as sdake16:01
evrardjpo?16:01
andymccro/16:01
amettso/16:01
*** mattt has joined #openstack-meeting-416:01
spotzmhayden damn you're quick16:01
*** michaelgugino has joined #openstack-meeting-416:01
michaelguginohere16:01
*** lakshmiS has joined #openstack-meeting-416:01
prometheanfire\o16:01
mattt\o16:02
mhaydenspotz: i move fast!16:02
jmccrory_o/16:02
*** jmckind has joined #openstack-meeting-416:02
*** julim has quit IRC16:02
*** thingee has left #openstack-meeting-416:03
*** iyamahat has joined #openstack-meeting-416:03
cloudnullo/16:03
*** flaviodsr has joined #openstack-meeting-416:03
*** gangil has joined #openstack-meeting-416:03
*** marcusvrn_ has quit IRC16:03
*** gregfaust has joined #openstack-meeting-416:03
odyssey4me#topic Tests Repo16:04
*** openstack changes topic to "Tests Repo (Meeting topic: OpenStack-Ansible)"16:04
*** rromans has joined #openstack-meeting-416:04
odyssey4meandymccr how's that going?16:04
andymccrso16:04
andymccrworking through it hopefully have something tangible up next week16:04
cloudnull++ nice!16:04
andymccrthere are some things around repo cloning/role inclusion and what we want to keep in the separate roles16:04
rromans.16:04
andymccrwhich will be up for discussion after the PoC16:04
*** hvprash_ has quit IRC16:05
andymccrbut got a pretty good idea of how it will look (in a rough sense) and we can clean thatup16:05
*** jmckind_ has quit IRC16:05
*** hvprash has joined #openstack-meeting-416:05
*** eil397 has joined #openstack-meeting-416:05
*** bpokorny has quit IRC16:05
evrardjpthanks for the work already :)16:06
*** igordcard has quit IRC16:06
*** unicell has quit IRC16:07
andymccrso tl;dr its progressing, will have something next week - right now nothing specific!16:07
odyssey4meok cool - are there any challenges you'd like some help with, or are you happy to keep going on your own for now?16:08
*** unicell has joined #openstack-meeting-416:08
*** smatzek has joined #openstack-meeting-416:08
odyssey4meandymccr ^ ?16:08
andymccrhappy for now . i'll be able to get a working thing going - we may need to refine a lot thought :)16:09
andymccr*though16:09
odyssey4mecool, thanks for working on it16:09
odyssey4me#topic Action items from last week16:09
*** openstack changes topic to "Action items from last week (Meeting topic: OpenStack-Ansible)"16:09
odyssey4me#link http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-12-16.01.html16:09
odyssey4meI am due most of them, and am behind in doing them. Some of these take time, but I'll keep going.16:10
odyssey4me#topic Mid Cycle Planning16:10
*** openstack changes topic to "Mid Cycle Planning (Meeting topic: OpenStack-Ansible)"16:10
odyssey4meWe didn't get to discuss this last time around and we need to make a call.16:10
prometheanfirewhere is it going to be this time?16:10
spotzSan Antonio!:)16:11
*** hvprash has quit IRC16:11
odyssey4meLast time we tried a co-located mid cycle, along with remote access. It didn't really work - so in my view it's either we're all using video conferencing, or we're all co-locating.16:11
*** fawadkhaliq has quit IRC16:11
*** ninag has quit IRC16:11
cloudnullSAT would certainly make my life easier :)16:11
automagicallyIf its in San Antonio, I’m likely to be able to attend in-person16:11
odyssey4meAll using video conferencing means that we'll have to figure out how to facilitate a mid cycle across time zones.16:11
prometheanfireya, sat is easier for me16:11
odyssey4meAll co-locating excludes many of us from participating.16:11
*** ninag has joined #openstack-meeting-416:12
matttbut in person 100% more productive also16:12
*** nkrinner has quit IRC16:12
*** nkrinner has joined #openstack-meeting-416:12
*** nkrinner is now known as nkrinner_afk16:12
*** stevelle has joined #openstack-meeting-416:13
odyssey4meI was thinking that we could certainly try out a video conf mid cycle across time zones such that we work out the work items ahead of time, then do sprint groups in each major time zone and hand over to each other at the end of the work day.16:13
prometheanfirehangouts?16:13
odyssey4meBut yes, co-locating does allow us to have very different discussions - and allows us to discuss, think about it, then discuss again.16:13
spotzodyssey4me: I will say with use of etherpad the global bugsquash worked pretty well coordinating the groups in different timezones/locations16:13
*** bpokorny has joined #openstack-meeting-416:14
*** avarner has joined #openstack-meeting-416:14
odyssey4meprometheanfire The tool for video conferencing isn't the issue - the issue is that working across time zones all together doesn't work, and nor does a mix of in-person and remote.16:14
automagicallyI like your proposal for structuring the video only odyssey4me16:15
evrardjp+116:15
odyssey4mejmccrory_ cloudnull d34dh0r53 stevelle mattt hughsaunders andymccr mhayden your input especially please16:15
automagicallyI’d prefer to be co-located, but understand that may not be possible16:15
cloudnullI like a co-located midcycle16:16
stevellein person and remote mixed is how we work all the time16:16
prometheanfirewe could probaby semi-colocate16:16
d34dh0r53^16:16
*** ninag has quit IRC16:16
cloudnullwe dont really need a midcycle to continue doing what we already do16:16
stevelleI'd agree with cloudnull on that16:16
prometheanfireheh, true16:17
mhaydeni'd prefer something in-person16:17
stevelleit's nice if it can work16:17
jmccrory+1 semi-colocate if possible16:17
odyssey4meyeah, the focal point for the mid cycle is to continue design discussions we may not have completed at the summit, and to ensure that we can put the right people together to unblock any work that is critical to deliver this cycle16:17
mhaydenperhaps we do two in-person rooms that are linked via VC?16:17
mhayden(as an alternative)16:17
prometheanfiremhayden: that's what I was thinking16:18
mhaydenperhaps a north american and a european one16:18
mhaydenthen link them16:18
odyssey4meso the trouble with semi colocation, or any sort of mix where everyone isn't in the same room, is that we inevitably end up with side discussions that not everyone can hear16:18
*** user154752_ has quit IRC16:18
spotz+1 mhayden16:18
spotzodyssey4me: I think that's always a risk16:18
odyssey4methat's why I thought of the sprint groups - allowing localised co-location, but handovers between time zones16:18
andymccrid love to be optimistic, but i agree with odyssey4me - the logistics of it are tough and ive genuinely never seen it work.16:19
mhaydenodyssey4me: there would just need to be ground rules for that16:19
cloudnullfor folks who cant make the mid-cycle we could do a recorded hangout so folks can watch and participate via IRC. but i agree the logistics are hard.16:19
andymccrotherwise we need to have day 1 of midcycle be the "fix all the ridiculous issues with VC meetings" day16:19
evrardjpsummary + vote?16:19
odyssey4melol16:19
mhaydenevrardjp and i talked, and we should have the midcycle in belgium16:20
*** AdmiralQi has joined #openstack-meeting-416:20
* mhayden winks16:20
odyssey4mebasically I was thinking that we forgo the trying to work together across time zones and instead work seperately, but hand over the work in a brief discussion16:20
palendaecloudnull, discussions aren't the same as a talk; not sure recording would be super valuable16:20
evrardjp:D16:20
odyssey4me(with the applicable code review)16:20
*** vishwanathj has joined #openstack-meeting-416:20
*** woodard has quit IRC16:21
*** woodard has joined #openstack-meeting-416:21
cloudnullpalendae: +116:22
palendaeAppreciate the sentiment, just not sure enough people would view/listen to make it worth the hassle16:22
d34dh0r53so IHMO side discussions happen just as much when we're all together as when co-located so that is sort of a non issue for me, we have to be more disciplined about sharing the results of those discussions (I myself am very guilty of not sharing)16:22
cloudnullit makes sense to have this  next one in the US.16:22
*** yamahata has joined #openstack-meeting-416:23
odyssey4meyeah, recordings are not the point16:23
cloudnullwe had the last one in the UK16:23
cloudnullmaybe philly :) -cc automagically16:23
palendaed34dh0r53, true, but it gets more garbled with video conferencing16:23
andymccrcloudnull: but the UK is the center of the world. so that just makes sense.16:23
spotzautomagically and I discussed and we pick Aachen16:23
d34dh0r53time starts in the UK16:23
automagicallyWe could host, I’m sure16:23
automagicallyha!16:23
cloudnullandymccr: it was once. now no longer.16:23
evrardjpandymccr: technically brussels is16:23
andymccrd34dh0r53: exactly.16:23
andymccrcloudnull: GMT - its where time begins.16:24
cloudnulland ends16:24
cloudnull:p16:24
automagicallySufficiently bike shedded yet?16:24
d34dh0r53cool, let's have the mid-cycle in Brussels16:24
andymccr+1 automagically16:24
andymccrso vote or more ideas? or how are we gonna decide on this16:24
odyssey4meok, ok - we don't absolutely have to decide right now - I agree that it's fair to have it in the US if we all co-locate, but there are some other factors to discuss before we finalise that discussion.16:24
mhaydenthe yaks are bare16:24
odyssey4meThe next things to think about is how long it should be.16:25
cloudnullto echo automagically im sure RAX at the castle would have no issues hosting16:25
odyssey4meThen finally where it should be, assuming co-location.16:25
sigmavirus24mhayden: that's the good thing about yaks, their pelts grow back very quickly16:25
automagicallyWas it 3 days last time16:25
andymccrautomagically: only 1, it was not nearly enough16:25
odyssey4mePreviously we tried one day, and IMO it wasn't enough time.16:25
matttfigure out who can go, if most people are coming from SAT then naturally SAT16:25
sigmavirus24midcycles are typically 3 days in the rest of openstack16:25
palendaeYeah, 1 day is too little, especially when having people travel to co-locate16:26
d34dh0r533 days sounds good to me16:26
automagically2-3 days seems reasonable16:26
*** ninag has joined #openstack-meeting-416:26
odyssey4meI have had 3 days of time recommended - generally the first day for discussion, the next day for follow-on and starting actual sprint work, then the last day to finalise work.16:26
sigmavirus24y'all should try to get a room with video conferencing built-in to allow remotes though16:26
odyssey4mesigmavirus24 we tried that last time and it was terrible16:26
sigmavirus24what was terrible about it?16:26
andymccrsigmavirus24: yeah i mean we will do that i think - we tried last time, but yeah its quite hard. and the nature of mid-cycles doesn't really go well with vc's etc imo.16:26
sigmavirus24it worked for the openstack security midcycle16:26
odyssey4mein fact it was quite disruptive16:26
mhaydeni thought it was on someone's laptop last year16:26
mhaydenor last time, i mean16:27
matttthe setup was poor, which is why it didn't work out16:27
odyssey4memhayden nope, it was a VC in the room with the whole big camera, mic and all16:27
matttbut the room was crazy loud which didn't help16:27
mhaydenweird16:27
errrtry booking the room by the nda lab at the bottom of the stairs to the toy store16:28
*** tonytan4ever has quit IRC16:28
andymccrok i think we should move on. we have an idea of the logistics/issues/ideas etc.16:28
mattt+116:29
andymccrthere are some outstanding questions we need answers to before we can decide anyway.16:29
*** fesp has quit IRC16:29
automagically+116:29
cloudnull+116:29
evrardjp+116:29
odyssey4meyeah, agreed andymccr - let's think on it and discuss it again next week - I'd like very specific feedback about who would be able to come if we colocate in the US, where we could colocate, and what dates would be suitable for that colocation (for those offering venues)16:29
automagically^ Makes sense16:30
odyssey4me#action Finalise discussion about mid-cycle next week16:30
michaelguginowhat time frame are we talking about?  July?16:30
*** piet has quit IRC16:30
*** eil397 has quit IRC16:31
*** piet has joined #openstack-meeting-416:31
odyssey4memichaelgugino we can choose when, and we'll have to look into other mid cycle dates and try not to clash with any other mid cycles our contributors are attending16:32
odyssey4me#topic Release Planning and Decisions16:32
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: OpenStack-Ansible)"16:32
odyssey4meWe're scheduled to do releases for Liberty & Mitaka today - is there anything specific that's a blocker on any of those?16:33
*** tonytan4ever has joined #openstack-meeting-416:33
*** LouisF has joined #openstack-meeting-416:33
odyssey4meFor Kilo note that we've done a SHA bump to the EOL tags for Kilo and will release our EOL late next week. If you have anything you need in Kilo, now's the time to get the patches done and justify why they should be included.16:33
odyssey4meAnyone got any blockers?16:34
stevelleI believe there is 1 change that could go into liberty but needs me to submit a known issue doc16:34
stevellewould be nice to get it in but isn't critical16:35
automagicallyI believe all the stuff I was concerned about has been merged into stable/mitaka16:35
*** ninag has quit IRC16:35
*** ninag has joined #openstack-meeting-416:36
*** ninag has quit IRC16:36
evrardjpstevelle: link or scope?16:36
odyssey4mestevelle Can it wait for the next tag?16:36
*** ninag has joined #openstack-meeting-416:36
stevelleodyssey4me: it can wait, it made it this far with only one person asking in irc for the fix16:37
*** paul-carlton2 has joined #openstack-meeting-416:37
odyssey4meok, thanks16:37
odyssey4me#action odyssey4me to request releases for Liberty, Mitaka today16:37
odyssey4me#topic Ubuntu 16.04 LTS Support16:38
*** openstack changes topic to "Ubuntu 16.04 LTS Support (Meeting topic: OpenStack-Ansible)"16:38
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-newton-ubuntu16-0416:38
odyssey4meI think we're doing quite well so far.16:38
odyssey4meThank you all for pitching in!16:38
odyssey4meYou may have noticed that all non-openstack roles now have a non-voting xenial gate check - that merged this morning.16:38
odyssey4meI'll do the same for CentOS.16:39
cloudnull+1 woot!16:39
automagicallySome really good progress there16:39
jmccrorynice16:39
*** jmckind_ has joined #openstack-meeting-416:39
odyssey4meFor those that are passing both CentOS and Xenial checks, I'll promote them to voting checks next week or ASAP afterwards.16:40
mattti've been a bit tied up and haven't spent much time on the memcached role, if anyone is itching to take it over feel free16:40
matttjmccrory left some good feedback which needs addressing16:40
spotzmine's not:(16:40
odyssey4meOne note I've been warned about is that there aren't yet wheel mirrors for CentOS/Xenial, so the gate builds will be slower.16:40
*** ninag has quit IRC16:41
odyssey4meThere is a local pypi mirror, so it'll still be reasonably fast.16:41
michaelguginorunning into lots of fun quirks with xenial builds during gates16:42
odyssey4meAny questions/comments/thoughts?16:42
michaelguginoI don't feel we're getting consistent container builds16:42
automagicallyHow so?16:42
odyssey4memichaelgugino after the patch merge this morning, that should be better.16:42
*** jmckind has quit IRC16:43
michaelguginothis was passing:  https://review.openstack.org/#/c/312602/16:43
odyssey4mehttps://review.openstack.org/315114 / https://review.openstack.org/318571 should have fixed up much of the container build weirdness that had been bugging us for around a week16:43
michaelguginowell, it was technically passing because the check was running two passes; one for the actual install, and one for the upgrade steps.  The initial install was working, and it was failing on the upgrade steps16:43
michaelguginoI removed the upgrade steps, now we can't install pip due to what looks like an ssl error.  I tweaked the test script to install ca-certificates, hopefully that helps.16:44
jmccroryssl errors like that seem to be cropping up randomly recently16:44
odyssey4methe ssl error may be completely unrelated and may instead have to do with comms issues16:44
michaelguginothat's what is making me think inconsistent containers16:44
odyssey4meevrardjp was digging into some of that, as was mattt16:44
odyssey4mewe may have a container IP range clashing with the cloud provider ranges16:45
odyssey4mewe had that before, and it caused the same kind of random failures16:45
michaelguginoI'm seeing u'Connection failure: unknown error (_ssl.c:2829)'}16:45
odyssey4meI would suggest checking the cloud providers to see if there's some consistency16:45
*** hvprash has joined #openstack-meeting-416:45
evrardjpmichaelgugino: could you check if you have connectivity?16:45
michaelguginothat error usually means invalid certs.  Invalid certs means outdated ca-certificates package.16:46
*** fawadkhaliq has joined #openstack-meeting-416:46
evrardjpbecause what I started with nova is definitely not done all over16:46
michaelguginoevrardjp: conn to what?16:46
odyssey4mewe need to know if it's all providers, or some - if it's specific to the platform (trusty/xenial/centos) or not16:46
evrardjp+1 odyssey4me16:46
michaelguginolooks like it's just xenial atm16:46
evrardjpmichaelgugino: I meant network connectivity working fine in the container, just to make sure16:47
evrardjpI can only track what I can see :p16:47
*** hvprash has quit IRC16:47
odyssey4memichaelgugino FYI https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/vars/ubuntu-16.04.yml#L61 is run on the container cache/image and therefore the containers have fully up to date package levels16:47
michaelguginohow do I check network connectivity in the container?16:47
odyssey4methat's why we had issues when we switched from the ubuntu archive to the rackspace mirror16:47
*** hvprash has joined #openstack-meeting-416:47
odyssey4meyou'll have to implement something in the tasks to output to the console - we have no access into the instances that run the thing16:48
*** eil397 has joined #openstack-meeting-416:48
odyssey4metroubleshooting this stuff in openstack-ci is a pain... that's why the integrated gate has so much diagnostic information16:48
michaelguginowe should run apt-get update before we run apt-get upgrade16:49
odyssey4memichaelgugino that's done in line 6016:50
michaelguginoI see that now16:50
michaelguginoodyssey4me: that's for the lxc_hosts.  The failures seem to be in the containers themselves16:51
odyssey4meanyway - the point is that all you have for logs is the console, so to diagnose issues you have to put a WIP patch in which gives you the info you want on the console, then wait for the job to run16:51
evrardjpshould we continue this outside the meeting?16:51
michaelguginosure16:52
odyssey4memichaelgugino yep, I was just trying to tell you that the containers are up to date when they're built16:52
*** hvprash has quit IRC16:52
*** sambetts is now known as sambetts|afk16:52
odyssey4meok, we can continue in the channel16:52
odyssey4me#topic Open Discussion16:52
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack-Ansible)"16:52
odyssey4meWe have 5 mins available for general discussion16:52
odyssey4meDoes anyone want to raise something specific?16:52
errrI have a question that fits here16:52
errrI made a blueprint for cloudkitty: https://blueprints.launchpad.net/openstack-ansible/+spec/role-cloudkitty16:53
errrand Im wondering how to proceed16:53
errrI had to make changes to os_horizon and added a playbook to osa so I wasnt sure what to do with all this..16:53
evrardjpdo you have a role we can already check?16:54
errryes16:54
evrardjpgood start :D16:54
*** ninag has joined #openstack-meeting-416:54
logan-Posted in the channel yesterday but easy to miss in the scrollback.. here's updated task/gate profiling: https://gist.github.com/Logan2211/6e3160c7d28d3886ba9d212c780e191816:54
errrhttps://github.com/michaelrice/openstack-ansible-os_cloudkitty16:54
*** user154752_ has joined #openstack-meeting-416:54
odyssey4meerrr if you're ready to import then let me know and I'll request the import, then we can work on it from there16:55
*** bpokorny has quit IRC16:55
errrodyssey4me: Im ready to import16:55
odyssey4meerrr with regards to edits on other roles, I'd suggest that you temporarily note them or include shortcut things for them in an 'extras' folder16:55
*** zenoway has quit IRC16:55
errrodyssey4me: Im not sure I understand what you mean by that16:56
odyssey4meyou can see an example here: https://github.com/flaviodsr/os_sahara/16:56
errrah ok16:56
*** zenoway has joined #openstack-meeting-416:56
odyssey4mefrom there we can setup the tests, then work towards patching things into the other roles and the integrated repo16:56
flaviodsrabout it odyssey4me any news on the sahara import?16:56
*** tung_doan has joined #openstack-meeting-416:57
odyssey4meI'll put in the request for the import16:57
odyssey4meflaviodsr https://review.openstack.org/31793116:57
evrardjpthanks logan- :D16:57
*** doonhammer has joined #openstack-meeting-416:57
flaviodsrgood thanks odyssey4me!16:57
prometheanfireI guess I'll just update and say that working to add a distro to nodepool is not fun and takes forever16:57
odyssey4methanks logan- I haven't had a chance to look at it yet16:57
*** avarner has quit IRC16:58
*** yamahata has quit IRC16:58
*** hvprash has joined #openstack-meeting-416:58
logan-yep np16:58
odyssey4meflaviodsr I'll add a request to also have a core team for the sahara role and include you there, because you know how it works.16:58
evrardjprepo as usual :D16:58
odyssey4meerrr I'll do the same for the cloudkitty role.16:58
*** piet has quit IRC16:58
*** dandruta has quit IRC16:58
*** yamahata has joined #openstack-meeting-416:58
*** ninag has quit IRC16:59
errrok thanks16:59
flaviodsrok odyssey4me, I am about to finish the install-guide entry16:59
odyssey4meWe're out of time, so any further discussion can happen in #openstack-ansible.16:59
*** nmadhok has joined #openstack-meeting-416:59
*** michaelgugino has left #openstack-meeting-416:59
odyssey4meThanks all for your time and continued contributions!16:59
odyssey4me#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu May 19 16:59:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-19-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-19-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-19-16.00.log.html16:59
*** igordcard has joined #openstack-meeting-417:00
*** zenoway has quit IRC17:01
LouisF#startmeeting service_chaining17:02
openstackMeeting started Thu May 19 17:02:02 2016 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: service_chaining)"17:02
openstackThe meeting name has been set to 'service_chaining'17:02
pcarverhi17:02
LouisFhi all17:02
doonhammerHI17:02
yamahatahello17:02
igordcardhi17:02
*** prometheanfire has left #openstack-meeting-417:02
*** piet has joined #openstack-meeting-417:02
*** flaviodsr has left #openstack-meeting-417:02
LouisFcathy is out today17:02
*** ninag_ has joined #openstack-meeting-417:02
mohankumar__hi17:02
*** mohankumar__ has quit IRC17:03
LouisFshe posted an agenda17:03
*** mohankumar__ has joined #openstack-meeting-417:03
*** mohankumar__ has quit IRC17:03
*** mohankumar has joined #openstack-meeting-417:03
LouisFhttps://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting17:03
*** pvaneck has joined #openstack-meeting-417:04
LouisF#topic use-case documentation17:04
*** openstack changes topic to "use-case documentation (Meeting topic: service_chaining)"17:04
*** minwang2 has quit IRC17:04
LouisFpcarver: i believe you were going to provide some input here?17:04
LouisFdoonhammer: do you have a use-case to share?17:05
pcarverLouisF: unfortunately I haven't collected anything yet. It's on my todo list.17:05
*** ninag_ has quit IRC17:05
doonhammer<LouisF> Working on them will have something by Monday17:05
*** ninag has joined #openstack-meeting-417:05
LouisFgreat - can you add a page to the wiki17:06
*** bpokorny has joined #openstack-meeting-417:06
*** s3wong has joined #openstack-meeting-417:06
LouisFok moving on17:06
igordcardtalking about use cases, I would like to inquiry about how the team is planning to support SFC encapsulation (since NSH is in the plans)17:06
doonhammerLouisF: Sure17:06
s3wonghello --- sorry, a bit late17:07
LouisFigordcard: currently the ovs driver uses mpls to encapsulate the nsp, nsi17:08
LouisFthe nsp uses the mpls.label and nsi uses mpls.ttl17:08
igordcardLouisF: yes, but doesn't actually achieve sfc-encap17:08
vishnoianilLouisF, i am double shifting with opendaylight tsc meeting,so my response will be slow17:08
LouisFvishnoianil: ok17:08
igordcardLouisF: I can send an email to the ML after, or there won't be enough time at the meeting17:08
LouisFigordcard: ok17:09
scsnowhi17:09
igordcardbut in the context of use cases, let me share this etherpad link for further analysis and discussion: https://etherpad.openstack.org/p/networking-sfc-and-sfc-encapsulation17:09
LouisFregarding ovs support for nsh - patches exist but it may be some time before is makes into an official ovs release17:10
LouisFigordcard: thanks17:10
*** julim has joined #openstack-meeting-417:10
pcarverThe MPLS encap is really just a temporary thing. At least that was how I understood it.17:10
LouisFpcarver: that is correct17:11
pcarverIt's not true MPLS, it's just using an MPLS tag to identify a chain.17:11
LouisFpcarver: exactly17:11
pcarverwhen OvS supports NSH we do expect to use it17:11
*** jmckind has joined #openstack-meeting-417:12
*** ddieterly is now known as ddieterly[away]17:12
LouisFpcarver: that is the plan17:12
igordcardmy concern here is that simply adding NSH doesn't add anything else besides metadata support, since the advantage of having multiple SFPs cannot be exploited with the current networking-sfc model17:13
*** gangil has quit IRC17:13
LouisFthe usage of nsp, nsi is per the ietf nsh draft17:13
*** gangil has joined #openstack-meeting-417:13
*** paul-carlton2 has quit IRC17:13
*** pbourke has quit IRC17:14
*** paul-carlton2 has joined #openstack-meeting-417:14
LouisFigordcard: can you elaborate17:14
*** jmckind_ has quit IRC17:14
pcarverigordcard: on the subject of use cases above, can you provide any use cases that can't be represented by the current networking-sfc API?17:14
LouisFa port chain is an sfp17:14
igordcardLouisF: essentially, how can you link port-chains together to form, essentially, a graph? (not like the ETSI's VNFFG though)17:15
pcarverIf we had a use case that we can't handle then we could figure out what changes would be needed in order to support it17:15
LouisFpcarver: +117:15
igordcardpcarver: in the etherpad above I present the reasons for having sfc-encap, and the n-sfc model bottlenecks it17:16
igordcardand how the n-sfc*17:16
LouisFigordcard: sfc-encap is currently supported by the ovs driver17:17
igordcardLouisF: that was my initial understanding, but after further analysis it is a mix between SFP and RSP17:17
igordcardLouisF: it is an SFP because, indeed, you specify a path and you can have multiple possible instances for a PPG (for a single SPI/SI)17:17
igordcardLouisF: but, it is also not fully an SFP since you can't link it to other SFPs to form an SFC17:17
*** gangil has quit IRC17:18
igordcardLouisF: so it falls back to an RSP (you define your chain from the beginning to the end, function by function)17:18
LouisFigordcard: the port-chain abstraction is an SFP, that actual path taken (RSP) is detemined in the data-plane17:19
igordcardLouisF: when I say sfc-encap, I'm talking about the concept, not the act of inserting an SFC header17:20
LouisFigordcard: i don't follow17:21
igordcardLouisF: correct, but if you look at it from an SFC perspective, the SFP is incomplete or there an additional resource to "glue" SFPs needs to exist17:21
igordcardSFCs are made up of SFPs, if we can't connect SFPs to form an SFC, then there is a gap in the model17:21
LouisFport-chains can be joined to make more complex graphs as necessary17:22
igordcardLouisF: as in ETSI VNFFG?17:23
LouisFigordcard: yes17:23
igordcardLouisF: then it means networking-sfc is an RSP API17:23
LouisFthe port-chain maps directly to an ETSI MANO network forwarding path (NFP)17:23
igordcardVNFFG is made up of RSPs, you classify once in the beginning of the RSP, and then hop function by function until the end. The graph is the list of all of these possible RSPs17:24
*** anilvenkata has joined #openstack-meeting-417:24
LouisFthe concept of rsp is not mentioned in the ETSI MANO doc17:24
LouisFrsps are only mentioned in the ietf nsh draft17:25
*** banix has joined #openstack-meeting-417:25
igordcardhow many times can we classify after entering a VNFFG?17:26
LouisFigordcard: the ETSI MANO spec does not mention classification17:27
LouisFcorrect me if i'm wrong17:28
doonhammerIt might help if igordcard could contribute some use cases and then we can design to the use cases?17:29
LouisFigordcard: can you add a use-case description in the wikie17:29
igordcardLouisF: yes when I said RSP it was actually NFP, which maps nicely to IETF's RSP17:29
doonhammerotherwise we have an infinity of possibilities - hard to design for17:29
igordcardpossible use cases are covered by RFC 7498 and 7665, but I can try to get some more besides the one at the etherpad17:30
LouisFigordcard: ok thanks17:30
*** paul-carlton2 has quit IRC17:30
igordcarddoonhammer: yes, which is why I'm trying to keep it close to standardization efforts17:30
LouisF#action paul, john igor to add use-cases to wiki17:30
*** minwang2 has joined #openstack-meeting-417:30
*** spotz is now known as spotz_zzz17:30
*** evrardjp has left #openstack-meeting-417:31
igordcardand since there is interest in NSH, it should be usable to its full extent (at the networking layer)17:31
doonhammerigordcard the IETF use cases need more detail - they are fairly weak (IMHO)17:31
*** minwang2 has quit IRC17:32
LouisFlets come back to this next week after we have the use-cases documented, i'd like to move on17:32
igordcardLouisF: sure, I'll send an email too17:32
LouisFigordcard: thanks17:32
*** cbits has quit IRC17:32
LouisF#topic flow-classifier priority17:32
*** openstack changes topic to "flow-classifier priority (Meeting topic: service_chaining)"17:32
LouisFmohankumar: you have a blueprint i think?17:33
mohankumarLouisF,  Filled a bug for it17:33
mohankumarhttps://bugs.launchpad.net/networking-sfc/+bug/158223817:33
openstackLaunchpad bug 1582238 in networking-sfc "Add "priority” field in flow-classifier" [Undecided,In progress]17:33
LouisFok bug17:33
*** fawadkhaliq has quit IRC17:33
mohankumarplease add your comments17:33
*** spotz_zzz is now known as spotz17:34
scsnowwho will work on implementation of this spec?17:34
mohankumarit help to prioritize fc when multiple FC are added in chain17:34
LouisFi think we can fold this into the common classifier work17:34
s3wongLouisF: we probably want to experiment this on the SFC classifier first, right?17:35
LouisFs3wong: we can certainly do that17:35
s3wongLouisF: the common classifier discussion on Tuesday was mostly on creating a new channel :-)17:35
LouisFs3wong: has that meeting date been finalized?17:36
s3wongLouisF: the first one was, then TBD :-)17:36
mohankumarLouisF ,  SFC needs it . Although  can be extend to common classifier17:36
*** anilvenkata has quit IRC17:37
LouisFmohankumar: ok all please review the bug17:37
s3wongLouisF, mohankumar: the idea is SFC classifier would come in consideration alongside with QoS, FWaaS...etc; so nothing is preventing you from adding existing one first, and we can put that on the table when discussing common classifier with the wider community17:37
LouisFwho is interested on working on the implementation?17:37
LouisFs3wong: +117:38
mohankumarLouisF : i  take it17:38
LouisFmohankumar: will you also to the ovs driver work?17:38
*** ddieterly[away] is now known as ddieterly17:39
mohankumarLouisF , For the ovs driver i may need some help if someone help can be share and do17:39
scsnowI think I can help with ovs driver17:40
mohankumarscsnow , thanks !17:40
LouisFscsnow: great thanks17:40
s3wongLouisF, mohankumar: what is the ovs driver work? OVS driver work pertaining to adding priority to classifier?17:40
LouisFs3wong: yes17:40
LouisFthe flow classifier priority need to be mapped to ovs flow rule priority17:41
s3wongLouisF: sure, makes sense17:42
*** javeriak has joined #openstack-meeting-417:42
LouisFmohankumar: scsnow need to add unit test cases also17:42
scsnowsure17:42
mohankumarYes Louisf : sure17:42
scsnowis that correct, that currently multiple flow classifiers can be assigned to port chain and it's handled correctly by ovs driver?17:43
LouisFscsnow: yes17:44
mohankumarscsnow : yes17:44
scsnowok, good17:44
igordcardAND or OR logic?17:44
LouisF#action mohan pavel to work on flow-classifier priority17:44
scsnowigordcard, and17:45
*** tonytan4ever has quit IRC17:45
igordcardscsnow: thanks17:45
*** degorenko is now known as _degorenko|afk17:46
LouisFok moving on17:46
*** sarob has joined #openstack-meeting-417:46
LouisF#topic move chain id generation from ovs driver to port chain plugin17:47
*** openstack changes topic to "move chain id generation from ovs driver to port chain plugin (Meeting topic: service_chaining)"17:47
LouisFcurrently the chain id (nsp) is generated in  the ovs driver but it should really be in  the plugin as it is common functionality for all backend drivers17:48
s3wongLouisF: I don't think anyone would argue against that17:48
LouisFwe are working on a patch to do this work17:48
igordcardfully agree with it, but I have a question: besides NSH do you plan to support other encap protos?17:49
LouisFigordcard: the focus is on nsh17:49
LouisFexpect a patch for review soon17:50
igordcardLouisF: okay, if it wasn't then stuff like length constraints for SPIs/SIs would be something to keep in mind when generating these IDs17:50
LouisFmoving  on17:50
LouisFigordcard: agree17:51
*** jmckind has quit IRC17:51
LouisF#topic SF insertion type/mode17:52
*** openstack changes topic to "SF insertion type/mode (Meeting topic: service_chaining)"17:52
s3wongigordcard: but it still isn't driver specific, right? So what we are doing here still makes sense, correct?17:52
igordcards3wong: not driver specific, no, since if they claim to support NSH, they should do it in a standard way17:52
s3wongigordcard: OK. Cool.17:53
LouisFigordcard: +117:53
LouisFthis next topic will take some discussion so best if we hold this for next week17:53
s3wongLouisF: insertion type/mode?17:54
LouisFs3wong: whether it is bump-in-wire, l2, l317:54
mohankumarLouisF , the topic about dynamic SF insertion to chain ?17:54
*** vhoward has joined #openstack-meeting-417:55
LouisFmohankumar: no17:55
s3wongLouisF: good topic. I am working with FWaaS folks, and am urging them to go with an insertion "plugin" with networking-sfc as default backend driver17:55
scsnowcan someone help with reviewing https://review.openstack.org/#/c/311509/ -- that's because we force openflow13 protocol for all commands when using ovs-ofctl17:56
mohankumarLouisF , okay17:56
scsnowwe need to determine acceptable approach how to fix that correctly17:56
s3wongscsnow: sure. Just added myself as reviewer17:56
doonhammers3wong coming from a ngfw vendor that seems the best approach for most use cases17:57
LouisFscsnow: ok will review17:57
*** tonytan4ever has joined #openstack-meeting-417:57
LouisFok lets discuss more next week17:57
igordcardis the insertion type feature only for a "legacy mode", i.e. only when sfc encap is disabled?17:57
s3wongdoonhammer: yep... as vendor also, FWaaS insertion method is just directly writing L2agent extension themselves with iptables/Linux-bridge as backend, very inflexible17:57
doonhammers3wong: agreed does not solve customer problems17:58
*** gangil has joined #openstack-meeting-417:58
*** AdmiralQi has quit IRC17:59
LouisFigordcard: for non-sfc aware SFs17:59
s3wongLouisF: is there an insertion spec or idea/email-thread to lay groundwork for discussion?17:59
igordcardLouisF: thanks17:59
LouisFalso new driver capability discovery spec https://review.openstack.org/#/c/31763517:59
*** jichen has joined #openstack-meeting-417:59
LouisFplease review17:59
LouisFthanks all17:59
*** SumitNaiksatam has joined #openstack-meeting-418:00
LouisFbye18:00
scsnowbye18:00
LouisF#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
*** dtardivel has quit IRC18:00
openstackMeeting ended Thu May 19 18:00:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-19-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-19-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-19-17.02.log.html18:00
s3wongbye18:00
igordcardbye18:00
doonhammerbye18:00
*** stevelle has left #openstack-meeting-418:02
*** ddieterly is now known as ddieterly[away]18:02
*** tung_doan has quit IRC18:05
*** automagically has left #openstack-meeting-418:05
*** hvprash has quit IRC18:13
*** hvprash has joined #openstack-meeting-418:14
*** mbound has quit IRC18:14
*** cbits has joined #openstack-meeting-418:14
*** mohankumar has quit IRC18:15
*** ninag has quit IRC18:15
*** mohankumar has joined #openstack-meeting-418:15
*** ninag has joined #openstack-meeting-418:16
*** mfedosin has quit IRC18:16
*** ninag has quit IRC18:17
*** ninag has joined #openstack-meeting-418:18
*** jmccrory_ has quit IRC18:19
*** mohankumar has quit IRC18:22
*** jwagner is now known as jwagner[away]18:23
*** hvprash_ has joined #openstack-meeting-418:23
*** ninag has quit IRC18:24
*** ninag has joined #openstack-meeting-418:25
*** zaneb has quit IRC18:26
*** jaimguer has quit IRC18:26
*** zz_zz_ja has quit IRC18:26
*** _degorenko|afk has quit IRC18:26
*** crinkle has quit IRC18:26
*** lifeless has quit IRC18:26
*** Daviey has quit IRC18:26
*** bogdando has quit IRC18:26
*** mfisch has quit IRC18:26
*** klindgren has quit IRC18:26
*** edleafe has quit IRC18:26
*** degorenko has joined #openstack-meeting-418:26
*** Daviey has joined #openstack-meeting-418:26
*** mfisch has joined #openstack-meeting-418:26
*** bogdando has joined #openstack-meeting-418:26
*** hvprash has quit IRC18:26
*** klindgren has joined #openstack-meeting-418:26
*** zz_ja has joined #openstack-meeting-418:26
*** lifeless has joined #openstack-meeting-418:27
*** crinkle has joined #openstack-meeting-418:27
*** mfisch is now known as Guest7626818:27
*** ninag has quit IRC18:27
*** ninag has joined #openstack-meeting-418:28
*** jaimguer has joined #openstack-meeting-418:28
*** doonhammer has quit IRC18:28
*** zaneb has joined #openstack-meeting-418:29
*** hayatb has quit IRC18:30
*** hvprash has joined #openstack-meeting-418:31
*** sweston has quit IRC18:31
*** edleafe has joined #openstack-meeting-418:31
*** zhiyan has quit IRC18:31
*** vdrok has quit IRC18:31
*** hvprash_ has quit IRC18:33
*** _sarob has joined #openstack-meeting-418:34
*** hayatb has joined #openstack-meeting-418:34
*** vdrok has joined #openstack-meeting-418:34
*** sweston has joined #openstack-meeting-418:34
*** zhiyan has joined #openstack-meeting-418:34
*** sarob has quit IRC18:37
*** nmadhok has quit IRC18:42
*** baoli_ has quit IRC18:42
*** ninag has quit IRC18:42
*** smatzek has quit IRC18:49
*** jmckind has joined #openstack-meeting-418:52
*** Sukhdev has joined #openstack-meeting-418:55
*** mbound has joined #openstack-meeting-418:56
*** avarner has joined #openstack-meeting-418:59
*** ninag has joined #openstack-meeting-419:01
*** _sarob has quit IRC19:01
*** salv-orlando has quit IRC19:01
*** ddieterly[away] has quit IRC19:02
*** dshakhray has quit IRC19:02
*** user154752 has joined #openstack-meeting-419:03
*** sarob has joined #openstack-meeting-419:03
*** user154752_ has quit IRC19:04
*** dshakhray has joined #openstack-meeting-419:05
*** jmckind_ has joined #openstack-meeting-419:06
*** avarner has quit IRC19:06
*** sdague has quit IRC19:08
*** zenoway has joined #openstack-meeting-419:09
*** jmckind has quit IRC19:09
*** sdague has joined #openstack-meeting-419:09
*** salv-orlando has joined #openstack-meeting-419:10
*** zenoway has quit IRC19:13
*** SumitNaiksatam has left #openstack-meeting-419:16
*** javeriak has quit IRC19:16
*** iberezovskiy is now known as iberezovskiy_afk19:25
*** ddieterly has joined #openstack-meeting-419:26
*** SumitNaiksatam has joined #openstack-meeting-419:28
*** Guest76268 is now known as mfisch19:30
*** baoli has joined #openstack-meeting-419:30
*** mfisch has quit IRC19:30
*** mfisch has joined #openstack-meeting-419:30
*** SumitNaiksatam has quit IRC19:32
*** banix has quit IRC19:33
*** jwagner[away] is now known as jwagner19:34
*** mbound has quit IRC19:36
*** ninag has quit IRC19:37
*** rbak has quit IRC19:38
*** ninag has joined #openstack-meeting-419:38
*** mbound has joined #openstack-meeting-419:38
*** jmckind_ has quit IRC19:42
*** ninag has quit IRC19:42
*** dshakhray has quit IRC19:47
*** vishnoianil has quit IRC19:49
*** rbak has joined #openstack-meeting-419:51
*** cbits has quit IRC19:51
*** ddieterly is now known as ddieterly[away]19:51
*** doonhammer has joined #openstack-meeting-419:52
*** zenoway has joined #openstack-meeting-419:52
*** cartik has joined #openstack-meeting-419:53
*** hvprash_ has joined #openstack-meeting-419:59
*** daneyon_ has joined #openstack-meeting-419:59
*** woodard_ has joined #openstack-meeting-420:00
*** daneyon__ has joined #openstack-meeting-420:00
*** daneyon has quit IRC20:01
*** hvprash__ has joined #openstack-meeting-420:01
*** hvprash has quit IRC20:02
*** woodard has quit IRC20:03
*** sarob has quit IRC20:03
*** woodard_ has quit IRC20:04
*** daneyon_ has quit IRC20:04
*** hvprash_ has quit IRC20:04
*** Sukhdev has quit IRC20:06
*** ddieterly[away] is now known as ddieterly20:06
*** sarob has joined #openstack-meeting-420:07
*** sacharya_ has joined #openstack-meeting-420:08
*** sachary__ has joined #openstack-meeting-420:11
*** sacharya has quit IRC20:11
*** banix has joined #openstack-meeting-420:13
*** matrohon has joined #openstack-meeting-420:13
*** sacharya_ has quit IRC20:15
*** markvoelker has joined #openstack-meeting-420:15
*** markvoelker has quit IRC20:20
*** jichen has quit IRC20:21
*** cbits has joined #openstack-meeting-420:25
*** ddieterly is now known as ddieterly[away]20:30
*** Sukhdev has joined #openstack-meeting-420:32
*** DevonBoatwright has joined #openstack-meeting-420:33
*** DevonBoatwright has left #openstack-meeting-420:33
*** piet has quit IRC20:35
*** jaimguer has left #openstack-meeting-420:39
*** ninag has joined #openstack-meeting-420:39
*** hemanthm is now known as hemanthm|afk20:40
*** julim has quit IRC20:42
*** julim has joined #openstack-meeting-420:42
*** yamamoto has joined #openstack-meeting-420:44
*** mattt has left #openstack-meeting-420:44
*** salv-orl_ has joined #openstack-meeting-420:48
*** baoli has quit IRC20:50
*** tonytan4ever has quit IRC20:51
*** salv-orlando has quit IRC20:51
*** barmaley has joined #openstack-meeting-420:52
barmaleyhello20:52
*** rromans has left #openstack-meeting-420:58
*** cartik has quit IRC21:00
*** ddieterly[away] is now known as ddieterly21:00
*** vhoward has quit IRC21:02
*** hvprash has joined #openstack-meeting-421:03
*** smatzek has joined #openstack-meeting-421:03
*** rtheis has quit IRC21:06
*** hvprash__ has quit IRC21:06
*** yamahata has quit IRC21:11
*** smatzek has quit IRC21:11
*** dshakhray has joined #openstack-meeting-421:13
*** ninag has quit IRC21:14
*** julim has quit IRC21:20
*** thorst_ has quit IRC21:23
*** piet has joined #openstack-meeting-421:23
*** matrohon has quit IRC21:25
*** thorst_ has joined #openstack-meeting-421:25
*** thorst_ has quit IRC21:29
*** vishnoianil has joined #openstack-meeting-421:31
*** baoli has joined #openstack-meeting-421:36
*** sdake has quit IRC21:39
*** hvprash has quit IRC21:44
*** hvprash has joined #openstack-meeting-421:44
*** thorst_ has joined #openstack-meeting-421:45
*** lakshmiS has quit IRC21:45
*** nmadhok has joined #openstack-meeting-421:48
*** thorst_ has quit IRC21:49
*** hvprash has quit IRC21:52
*** Sukhdev has quit IRC21:53
*** Sukhdev has joined #openstack-meeting-421:56
*** doonhammer has quit IRC21:57
*** Swami has quit IRC22:01
*** IlyaG has quit IRC22:03
*** hvprash has joined #openstack-meeting-422:06
*** ddieterly is now known as ddieterly[away]22:07
*** hvprash_ has joined #openstack-meeting-422:08
*** cbits has quit IRC22:09
*** hvprash has quit IRC22:11
*** galstrom is now known as galstrom_zzz22:14
*** sigmavirus24 is now known as sigmavirus24_awa22:20
*** dshakhray has quit IRC22:21
*** zenoway has quit IRC22:25
*** zenoway has joined #openstack-meeting-422:26
*** markvoelker has joined #openstack-meeting-422:27
*** markvoelker has quit IRC22:29
*** ddieterly[away] is now known as ddieterly22:29
*** markvoelker has joined #openstack-meeting-422:29
*** sdake has joined #openstack-meeting-422:30
*** zenoway has quit IRC22:30
*** kylek3h has quit IRC22:32
*** spotz is now known as spotz_zzz22:33
*** hvprash_ has quit IRC22:34
*** user154752 has quit IRC22:34
*** hvprash has joined #openstack-meeting-422:35
*** hvprash_ has joined #openstack-meeting-422:35
*** bobh has quit IRC22:37
*** ninag has joined #openstack-meeting-422:38
*** sdague has quit IRC22:39
*** hvprash has quit IRC22:39
*** ninag has quit IRC22:41
*** sdake has quit IRC22:45
*** IlyaG has joined #openstack-meeting-422:47
*** IlyaG has quit IRC22:48
*** IlyaG_ has joined #openstack-meeting-422:48
*** ddieterly has quit IRC22:51
*** banix has quit IRC22:52
*** markvoelker has quit IRC22:58
*** mbound has quit IRC22:59
*** zenoway has joined #openstack-meeting-422:59
*** padkrish has joined #openstack-meeting-423:01
*** doonhammer has joined #openstack-meeting-423:01
*** IlyaG_ has quit IRC23:03
*** klamath has quit IRC23:03
*** ametts has quit IRC23:04
*** zenoway has quit IRC23:04
*** sdake has joined #openstack-meeting-423:04
*** LouisF has quit IRC23:05
*** Sukhdev has quit IRC23:05
*** pmesserli has quit IRC23:07
*** Sukhdev has joined #openstack-meeting-423:08
*** cloudtrainme has quit IRC23:11
*** salv-orl_ has quit IRC23:12
*** sdake has quit IRC23:14
*** sdake has joined #openstack-meeting-423:15
*** amotoki has quit IRC23:21
*** sdake has quit IRC23:21
*** amotoki has joined #openstack-meeting-423:21
*** Swami has joined #openstack-meeting-423:23
*** zenoway has joined #openstack-meeting-423:23
*** amotoki has quit IRC23:26
*** Sukhdev has quit IRC23:27
*** zenoway has quit IRC23:28
*** JRobinson__ has joined #openstack-meeting-423:30
*** padkrish has quit IRC23:36
*** padkrish has joined #openstack-meeting-423:37
*** padkrish has quit IRC23:42
*** baoli has quit IRC23:44
*** zenoway has joined #openstack-meeting-423:48
*** sdake has joined #openstack-meeting-423:52
*** zenoway has quit IRC23:52
*** hvprash_ has quit IRC23:54
*** hvprash has joined #openstack-meeting-423:54
*** hvprash has quit IRC23:56
*** hvprash has joined #openstack-meeting-423:56
*** kylek3h has joined #openstack-meeting-423:56

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