Thursday, 2016-05-05

*** shaohe_feng has quit IRC00:02
*** rockyg has quit IRC00:03
*** shaohe_feng has joined #openstack-meeting-400:04
*** gangil has joined #openstack-meeting-400:09
*** fawadkhaliq has quit IRC00:09
*** gangil has quit IRC00:10
*** yamamoto has joined #openstack-meeting-400:11
*** adduarte has quit IRC00:11
*** shaohe_feng has quit IRC00:12
*** piet has quit IRC00:12
*** shaohe_feng has joined #openstack-meeting-400:13
*** minwang2 has quit IRC00:13
*** emagana has quit IRC00:16
*** raddaoui has quit IRC00:17
*** uck has quit IRC00:17
*** yamamoto has quit IRC00:17
*** thorst has joined #openstack-meeting-400:18
*** shaohe_feng has quit IRC00:22
*** shaohe_feng has joined #openstack-meeting-400:23
*** SimonChung1 has quit IRC00:31
*** shaohe_feng has quit IRC00:32
*** shaohe_feng has joined #openstack-meeting-400:33
*** Sukhdev has quit IRC00:35
*** thorst has quit IRC00:36
*** thorst has joined #openstack-meeting-400:36
*** baoli has quit IRC00:37
*** thorst has quit IRC00:41
*** amit213 has quit IRC00:42
*** shaohe_feng has quit IRC00:43
*** bobh has quit IRC00:43
*** shaohe_feng has joined #openstack-meeting-400:43
*** May-meimei has joined #openstack-meeting-400:44
*** thorst has joined #openstack-meeting-400:45
*** pvaneck has quit IRC00:47
*** bobh has joined #openstack-meeting-400:50
*** shaohe_feng has quit IRC00:53
*** banix has joined #openstack-meeting-400:53
*** gb21 has quit IRC00:55
*** shaohe_feng has joined #openstack-meeting-400:56
*** bobh has quit IRC01:00
*** baoli has joined #openstack-meeting-401:01
*** shaohe_feng has quit IRC01:03
*** shaohe_feng has joined #openstack-meeting-401:04
*** piet has joined #openstack-meeting-401:04
*** zhurong has joined #openstack-meeting-401:04
*** gb21 has joined #openstack-meeting-401:07
*** yamamoto has joined #openstack-meeting-401:07
*** Jeffrey4l has joined #openstack-meeting-401:07
*** baoli has quit IRC01:09
*** baoli has joined #openstack-meeting-401:12
*** yamamoto has quit IRC01:12
*** amit213 has joined #openstack-meeting-401:13
*** shaohe_feng has quit IRC01:13
*** shaohe_feng has joined #openstack-meeting-401:14
*** amit213 has quit IRC01:16
*** ddieterly has quit IRC01:18
*** daneyon has joined #openstack-meeting-401:19
*** sdake has joined #openstack-meeting-401:22
*** shaohe_feng has quit IRC01:24
*** shaohe_feng has joined #openstack-meeting-401:25
*** unicell1 has quit IRC01:25
*** daneyon_ has joined #openstack-meeting-401:25
*** unicell has joined #openstack-meeting-401:25
*** baoli has quit IRC01:25
*** unicell1 has joined #openstack-meeting-401:26
*** unicell has quit IRC01:26
*** daneyon has quit IRC01:28
*** gb21 has quit IRC01:28
*** dims has quit IRC01:30
*** shaohe_feng has quit IRC01:34
*** dims has joined #openstack-meeting-401:35
*** shaohe_feng has joined #openstack-meeting-401:35
*** daneyon_ has quit IRC01:36
*** gb21 has joined #openstack-meeting-401:43
*** yamamoto has joined #openstack-meeting-401:43
*** shaohe_feng has quit IRC01:44
*** julim has joined #openstack-meeting-401:45
*** shaohe_feng has joined #openstack-meeting-401:45
*** yamamoto has quit IRC01:50
*** bpokorny has joined #openstack-meeting-401:54
*** shaohe_feng has quit IRC01:54
*** shaohe_feng has joined #openstack-meeting-401:55
*** zhurong has quit IRC01:55
*** piet has quit IRC01:56
*** mkaushik has joined #openstack-meeting-401:56
*** yamamoto has joined #openstack-meeting-401:59
*** thorst has quit IRC02:01
*** thorst has joined #openstack-meeting-402:01
*** klamath has quit IRC02:01
*** klamath has joined #openstack-meeting-402:01
*** klamath has quit IRC02:02
*** unicell1 has quit IRC02:02
*** klamath has joined #openstack-meeting-402:03
*** bpokorny has quit IRC02:03
*** shaohe_feng has quit IRC02:05
*** shaohe_feng has joined #openstack-meeting-402:06
*** salv-orlando has joined #openstack-meeting-402:08
*** sdake_ has joined #openstack-meeting-402:08
*** thorst has quit IRC02:09
*** sdake has quit IRC02:11
*** mkaushik has quit IRC02:11
*** mkaushik has joined #openstack-meeting-402:12
*** banix has quit IRC02:12
*** mkaushik has quit IRC02:13
*** mkaushik has joined #openstack-meeting-402:14
*** shaohe_feng has quit IRC02:15
*** zhurong has joined #openstack-meeting-402:15
*** bobh has joined #openstack-meeting-402:15
*** shaohe_feng has joined #openstack-meeting-402:16
*** salv-orlando has quit IRC02:17
*** mkaushik has quit IRC02:21
*** mkaushik has joined #openstack-meeting-402:21
*** yamamoto has quit IRC02:21
*** mkaushik has quit IRC02:24
*** mkaushik has joined #openstack-meeting-402:25
*** mkaushik has quit IRC02:25
*** shaohe_feng has quit IRC02:25
*** shaohe_feng has joined #openstack-meeting-402:26
*** mkaushik has joined #openstack-meeting-402:26
*** mkaushik has joined #openstack-meeting-402:27
*** sdake_ has quit IRC02:27
*** mkaushik has quit IRC02:27
*** mkaushik has joined #openstack-meeting-402:28
*** salv-orlando has joined #openstack-meeting-402:30
*** salv-orlando has quit IRC02:31
*** salv-orlando has joined #openstack-meeting-402:31
*** fawadkhaliq has joined #openstack-meeting-402:32
*** bobh has quit IRC02:33
*** shaohe_feng has quit IRC02:35
*** bobh has joined #openstack-meeting-402:37
*** spzala has quit IRC02:37
*** spzala has joined #openstack-meeting-402:38
*** mkaushik has quit IRC02:38
*** mkaushik has joined #openstack-meeting-402:38
*** bobh has quit IRC02:38
*** shaohe_feng has joined #openstack-meeting-402:39
*** fitoduarte has joined #openstack-meeting-402:39
*** bobh has joined #openstack-meeting-402:40
*** banix has joined #openstack-meeting-402:41
*** iyamahat has quit IRC02:41
*** yamahata has quit IRC02:42
*** spzala has quit IRC02:42
*** salv-orlando has quit IRC02:45
*** shaohe_feng has quit IRC02:46
*** shaohe_feng has joined #openstack-meeting-402:49
*** gb21 has quit IRC02:52
*** pav0 has joined #openstack-meeting-402:52
*** banix has quit IRC02:52
*** zhurong has quit IRC02:53
*** akijak has joined #openstack-meeting-402:55
*** shaohe_feng has quit IRC02:56
*** vtech has quit IRC02:56
*** shaohe_feng has joined #openstack-meeting-402:57
*** bobh has quit IRC02:59
*** rstarmer has joined #openstack-meeting-403:00
*** spzala has joined #openstack-meeting-403:03
*** cdelatte has quit IRC03:03
*** gb21 has joined #openstack-meeting-403:04
*** Jeffrey4l has quit IRC03:05
*** Jeffrey4l has joined #openstack-meeting-403:05
*** shaohe_feng has quit IRC03:06
*** shaohe_feng has joined #openstack-meeting-403:07
*** thorst has joined #openstack-meeting-403:07
*** spzala has quit IRC03:08
*** thorst has quit IRC03:15
*** shaohe_feng has quit IRC03:16
*** shaohe_feng has joined #openstack-meeting-403:17
*** salv-orlando has joined #openstack-meeting-403:20
*** cwolferh has quit IRC03:26
*** shaohe_feng has quit IRC03:27
*** shaohe_feng has joined #openstack-meeting-403:27
*** gongysh has joined #openstack-meeting-403:30
*** shaohe_feng has quit IRC03:37
*** shaohe_feng has joined #openstack-meeting-403:37
*** fawadkhaliq has quit IRC03:41
*** salv-orlando has quit IRC03:42
*** shaohe_feng has quit IRC03:47
*** shaohe_feng has joined #openstack-meeting-403:48
*** cwolferh has joined #openstack-meeting-403:48
*** nmadhok has quit IRC03:50
*** nmadhok has joined #openstack-meeting-403:51
*** piet has joined #openstack-meeting-403:51
*** pleia2 has quit IRC03:51
*** bpokorny has joined #openstack-meeting-403:51
*** armax has quit IRC03:52
*** armax has joined #openstack-meeting-403:53
*** nmadhok has quit IRC03:53
*** bpokorny has quit IRC03:57
*** shaohe_feng has quit IRC03:57
*** armax has quit IRC03:58
*** shaohe_feng has joined #openstack-meeting-403:58
*** bpokorny has joined #openstack-meeting-403:59
*** spzala has joined #openstack-meeting-404:04
*** cartik has joined #openstack-meeting-404:04
*** shaohe_feng has quit IRC04:08
*** shaohe_feng has joined #openstack-meeting-404:08
*** spzala has quit IRC04:09
*** unicell has joined #openstack-meeting-404:11
*** thorst has joined #openstack-meeting-404:13
*** iyamahat has joined #openstack-meeting-404:13
*** rstarmer has quit IRC04:15
*** sdake has joined #openstack-meeting-404:18
*** shaohe_feng has quit IRC04:18
*** shaohe_feng has joined #openstack-meeting-404:19
*** thorst has quit IRC04:19
*** zhurong has joined #openstack-meeting-404:24
*** unicell1 has joined #openstack-meeting-404:24
*** unicell has quit IRC04:26
*** shaohe_feng has quit IRC04:28
*** shaohe_feng has joined #openstack-meeting-404:29
*** rstarmer has joined #openstack-meeting-404:30
*** cartik has quit IRC04:34
*** bpokorny has quit IRC04:35
*** shaohe_feng has quit IRC04:38
*** irenab has quit IRC04:39
*** piet has quit IRC04:39
*** shaohe_feng has joined #openstack-meeting-404:41
*** dave-mccowan has quit IRC04:45
*** sdake has quit IRC04:47
*** sdake has joined #openstack-meeting-404:47
*** shaohe_feng has quit IRC04:49
*** shaohe_feng has joined #openstack-meeting-404:52
*** vishnoianil has quit IRC04:52
*** shaohe_feng has quit IRC04:59
*** shaohe_feng has joined #openstack-meeting-404:59
*** gb21 has quit IRC05:01
*** spzala has joined #openstack-meeting-405:03
*** spzala has quit IRC05:08
*** unicell has joined #openstack-meeting-405:09
*** unicell1 has quit IRC05:09
*** shaohe_feng has quit IRC05:09
*** shaohe_feng has joined #openstack-meeting-405:10
*** zehicle has quit IRC05:11
*** thorst has joined #openstack-meeting-405:18
*** irenab has joined #openstack-meeting-405:18
*** fawadkhaliq has joined #openstack-meeting-405:18
*** shaohe_feng has quit IRC05:19
*** shaohe_feng has joined #openstack-meeting-405:20
*** thorst has quit IRC05:25
*** SimonChung has joined #openstack-meeting-405:26
*** javeriak has joined #openstack-meeting-405:28
*** shaohe_feng has quit IRC05:30
*** shaohe_feng has joined #openstack-meeting-405:31
*** zenoway has joined #openstack-meeting-405:38
*** shaohe_feng has quit IRC05:40
*** shaohe_feng has joined #openstack-meeting-405:41
*** shaohe_feng has quit IRC05:50
*** shaohe_feng has joined #openstack-meeting-405:51
*** armax has joined #openstack-meeting-405:55
*** javeriak has quit IRC05:56
*** numans has joined #openstack-meeting-405:57
*** cwolferh has quit IRC05:58
*** shaohe_feng has quit IRC06:00
*** armax has quit IRC06:01
*** shaohe_feng has joined #openstack-meeting-406:01
*** SimonChung1 has joined #openstack-meeting-406:03
*** spzala has joined #openstack-meeting-406:03
*** SimonChung has quit IRC06:06
*** daneyon has joined #openstack-meeting-406:08
*** spzala has quit IRC06:09
*** daneyon_ has joined #openstack-meeting-406:09
*** shaohe_feng has quit IRC06:11
*** shaohe_feng has joined #openstack-meeting-406:12
*** daneyon has quit IRC06:13
*** paul-carlton2 has joined #openstack-meeting-406:20
*** shaohe_feng has quit IRC06:21
*** shaohe_feng has joined #openstack-meeting-406:22
*** unicell1 has joined #openstack-meeting-406:23
*** thorst has joined #openstack-meeting-406:23
*** iyamahat has quit IRC06:23
*** unicell has quit IRC06:24
*** daneyon_ has quit IRC06:24
*** daneyon has joined #openstack-meeting-406:24
*** paul-carlton2 has quit IRC06:26
*** anilvenkata has joined #openstack-meeting-406:30
*** thorst has quit IRC06:30
*** shaohe_feng has quit IRC06:31
*** shaohe_feng has joined #openstack-meeting-406:32
*** sdake has quit IRC06:32
*** daneyon has quit IRC06:37
*** paul-carlton2 has joined #openstack-meeting-406:38
*** zenoway has quit IRC06:40
*** shaohe_feng has quit IRC06:41
*** shaohe_feng has joined #openstack-meeting-406:42
*** paul-carlton2 has quit IRC06:42
*** cartik has joined #openstack-meeting-406:46
*** cwolferh has joined #openstack-meeting-406:47
*** hdaniel has joined #openstack-meeting-406:48
*** shaohe_feng has quit IRC06:52
*** shaohe_feng has joined #openstack-meeting-406:53
*** paul-carlton2 has joined #openstack-meeting-406:55
*** shaohe_feng has quit IRC07:02
*** shaohe_feng has joined #openstack-meeting-407:03
*** spzala has joined #openstack-meeting-407:05
*** paul-carlton2 has quit IRC07:09
*** spzala has quit IRC07:10
*** duvarenkov_ has joined #openstack-meeting-407:12
*** duvarenkov has quit IRC07:12
*** shaohe_feng has quit IRC07:12
*** shaohe_feng has joined #openstack-meeting-407:13
*** vishnoianil has joined #openstack-meeting-407:20
*** zenoway has joined #openstack-meeting-407:21
*** paul-carlton2 has joined #openstack-meeting-407:22
*** shaohe_feng has quit IRC07:22
*** shaohe_feng has joined #openstack-meeting-407:23
*** thorst has joined #openstack-meeting-407:27
*** hdaniel has quit IRC07:27
*** shaohe_feng has quit IRC07:33
*** shaohe_feng has joined #openstack-meeting-407:34
*** thorst has quit IRC07:35
*** hdaniel has joined #openstack-meeting-407:42
*** javeriak has joined #openstack-meeting-407:43
*** shaohe_feng has quit IRC07:43
*** shaohe_feng has joined #openstack-meeting-407:44
*** paul-carlton2 has quit IRC07:52
*** shaohe_feng has quit IRC07:53
*** shaohe_feng has joined #openstack-meeting-407:54
*** armax has joined #openstack-meeting-407:58
*** partner has quit IRC07:59
*** rstarmer has quit IRC08:01
*** hdaniel has quit IRC08:01
*** armax has quit IRC08:03
*** shaohe_feng has quit IRC08:03
*** shaohe_feng has joined #openstack-meeting-408:04
*** spzala has joined #openstack-meeting-408:06
*** fawadkhaliq has quit IRC08:06
*** mbound has joined #openstack-meeting-408:10
*** spzala has quit IRC08:11
*** pav0 has left #openstack-meeting-408:13
*** shaohe_feng has quit IRC08:14
*** dshakhray has joined #openstack-meeting-408:15
*** vishnoianil has quit IRC08:15
*** shaohe_feng has joined #openstack-meeting-408:17
*** rstarmer has joined #openstack-meeting-408:19
*** obondarev has quit IRC08:20
*** obondarev has joined #openstack-meeting-408:21
*** shaohe_feng has quit IRC08:24
*** shaohe_feng has joined #openstack-meeting-408:24
*** gongysh has quit IRC08:27
*** javeriak has quit IRC08:29
*** thorst has joined #openstack-meeting-408:32
*** shaohe_feng has quit IRC08:34
*** shaohe_feng has joined #openstack-meeting-408:35
*** thorst has quit IRC08:40
*** hdaniel has joined #openstack-meeting-408:44
*** shaohe_feng has quit IRC08:44
*** shaohe_feng has joined #openstack-meeting-408:45
*** shaohe_feng has quit IRC08:55
*** shaohe_feng has joined #openstack-meeting-408:55
*** leo_wang has quit IRC08:59
*** shaohe_feng has quit IRC09:05
*** shaohe_feng has joined #openstack-meeting-409:06
*** spzala has joined #openstack-meeting-409:07
*** spzala has quit IRC09:12
*** numans has quit IRC09:14
*** numans has joined #openstack-meeting-409:14
*** shaohe_feng has quit IRC09:15
*** shaohe_feng has joined #openstack-meeting-409:16
*** prithiv has joined #openstack-meeting-409:19
*** javeriak has joined #openstack-meeting-409:20
*** rstarmer has quit IRC09:22
*** pbourke has joined #openstack-meeting-409:23
*** sdake has joined #openstack-meeting-409:24
*** shaohe_feng has quit IRC09:25
*** shaohe_feng has joined #openstack-meeting-409:26
*** shaohe_feng has quit IRC09:36
*** shaohe_feng has joined #openstack-meeting-409:36
*** thorst has joined #openstack-meeting-409:38
*** vishnoianil has joined #openstack-meeting-409:39
*** sambetts|afk is now known as sambetts09:40
*** thorst has quit IRC09:45
*** shaohe_feng has quit IRC09:46
*** shaohe_feng has joined #openstack-meeting-409:47
*** shaohe_feng has quit IRC09:56
*** shaohe_feng has joined #openstack-meeting-409:57
*** armax has joined #openstack-meeting-410:00
*** zhurong has quit IRC10:01
*** alexchadin has joined #openstack-meeting-410:04
*** armax has quit IRC10:04
*** alexchadin has quit IRC10:05
*** sdague has joined #openstack-meeting-410:06
*** shaohe_feng has quit IRC10:06
*** shaohe_feng has joined #openstack-meeting-410:08
*** spzala has joined #openstack-meeting-410:08
*** amotoki has quit IRC10:10
*** amotoki has joined #openstack-meeting-410:11
*** spzala has quit IRC10:13
*** oomichi_ has joined #openstack-meeting-410:15
*** Jeffrey4l has quit IRC10:15
*** shaohe_feng has quit IRC10:17
*** Jeffrey4l has joined #openstack-meeting-410:17
*** shaohe_feng has joined #openstack-meeting-410:18
*** oomichi_ has quit IRC10:25
*** shaohe_feng has quit IRC10:27
*** shaohe_feng has joined #openstack-meeting-410:28
*** sdake has quit IRC10:29
*** zenoway has quit IRC10:31
*** oomichi_ has joined #openstack-meeting-410:31
*** shaohe_feng has quit IRC10:37
*** shaohe_feng has joined #openstack-meeting-410:38
*** thorst has joined #openstack-meeting-410:41
*** yamamoto has joined #openstack-meeting-410:46
*** zenoway has joined #openstack-meeting-410:46
*** shaohe_feng has quit IRC10:47
*** prithiv has quit IRC10:49
*** thorst has quit IRC10:50
*** shaohe_feng has joined #openstack-meeting-410:51
*** javeriak has quit IRC10:51
*** yamamoto has quit IRC10:52
*** cartik has quit IRC10:57
*** shaohe_feng has quit IRC10:58
*** yamamoto has joined #openstack-meeting-410:58
*** shaohe_feng has joined #openstack-meeting-410:59
*** prithiv has joined #openstack-meeting-411:00
*** javeriak has joined #openstack-meeting-411:04
*** prithiv has quit IRC11:04
*** prithiv has joined #openstack-meeting-411:06
*** shaohe_feng has quit IRC11:08
*** shaohe_feng has joined #openstack-meeting-411:09
*** spzala has joined #openstack-meeting-411:09
*** alexchadin has joined #openstack-meeting-411:09
*** alexchadin has quit IRC11:09
*** yamamoto has quit IRC11:10
*** yamamoto has joined #openstack-meeting-411:10
*** yamamoto has quit IRC11:11
*** yamamoto has joined #openstack-meeting-411:12
*** yamamoto has quit IRC11:13
*** yamamoto has joined #openstack-meeting-411:13
*** spzala has quit IRC11:14
*** yamamoto has quit IRC11:15
*** prithiv has quit IRC11:16
*** yamamoto has joined #openstack-meeting-411:16
*** shaohe_feng has quit IRC11:18
*** shaohe_feng has joined #openstack-meeting-411:19
*** prithiv has joined #openstack-meeting-411:21
*** prithiv has quit IRC11:22
*** ddieterly has joined #openstack-meeting-411:25
*** rtheis has joined #openstack-meeting-411:26
*** shaohe_feng has quit IRC11:28
*** shaohe_feng has joined #openstack-meeting-411:29
*** shaohe_feng has quit IRC11:39
*** shaohe_feng has joined #openstack-meeting-411:39
*** thorst has joined #openstack-meeting-411:40
*** brucet has quit IRC11:41
*** woodard has joined #openstack-meeting-411:45
*** woodard has quit IRC11:45
*** woodard has joined #openstack-meeting-411:45
*** yamamoto has quit IRC11:45
*** yamamoto has joined #openstack-meeting-411:46
*** yamamoto has quit IRC11:46
*** baoli has joined #openstack-meeting-411:46
*** yamamoto has joined #openstack-meeting-411:46
*** woodard has quit IRC11:47
*** baoli_ has joined #openstack-meeting-411:47
*** woodard has joined #openstack-meeting-411:47
*** yhvh- is now known as yhvh11:48
*** shaohe_feng has quit IRC11:49
*** shaohe_feng has joined #openstack-meeting-411:49
*** baoli has quit IRC11:51
*** oomichi_ has quit IRC11:52
*** dave-mccowan has joined #openstack-meeting-411:53
*** dave-mcc_ has joined #openstack-meeting-411:56
*** dave-mccowan has quit IRC11:58
*** yamamoto has quit IRC11:58
*** shaohe_feng has quit IRC11:59
*** yamamoto has joined #openstack-meeting-412:00
*** shaohe_feng has joined #openstack-meeting-412:00
*** ddieterly is now known as ddieterly[away]12:02
*** xiaohhui has joined #openstack-meeting-412:02
*** prithiv has joined #openstack-meeting-412:04
*** ekarlso has quit IRC12:06
*** ekarlso has joined #openstack-meeting-412:06
*** brucet has joined #openstack-meeting-412:07
*** shaohe_feng has quit IRC12:09
*** spzala has joined #openstack-meeting-412:10
*** shaohe_feng has joined #openstack-meeting-412:12
*** zhurong has joined #openstack-meeting-412:13
*** spzala has quit IRC12:15
*** brucet has quit IRC12:19
*** shaohe_feng has quit IRC12:20
*** krtaylor has quit IRC12:20
*** shaohe_feng has joined #openstack-meeting-412:21
*** scsnow has joined #openstack-meeting-412:22
*** ddieterly[away] is now known as ddieterly12:26
*** prithiv has quit IRC12:27
*** shaohe_feng has quit IRC12:30
*** ddieterly is now known as ddieterly[away]12:30
*** shaohe_feng has joined #openstack-meeting-412:31
*** javeriak has quit IRC12:31
*** zehicle has joined #openstack-meeting-412:33
*** prithiv has joined #openstack-meeting-412:33
*** prithiv has quit IRC12:34
*** prithiv has joined #openstack-meeting-412:36
*** ninag has joined #openstack-meeting-412:37
*** ddieterly[away] is now known as ddieterly12:37
*** prithiv has quit IRC12:37
*** prithiv has joined #openstack-meeting-412:39
*** shaohe_feng has quit IRC12:40
*** shaohe_feng has joined #openstack-meeting-412:43
*** yamamoto has quit IRC12:44
*** yamamoto has joined #openstack-meeting-412:44
*** jmckind has joined #openstack-meeting-412:44
*** yamamoto has quit IRC12:44
*** yamamoto has joined #openstack-meeting-412:45
*** ddieterly has quit IRC12:46
*** ido_ has joined #openstack-meeting-412:47
*** ido_ is now known as Guest5050612:47
*** spzala has joined #openstack-meeting-412:48
*** Guest50506 has quit IRC12:48
*** ddieterly has joined #openstack-meeting-412:48
*** ddieterly has quit IRC12:49
*** banix has joined #openstack-meeting-412:50
*** shaohe_feng has quit IRC12:50
*** shaohe_feng has joined #openstack-meeting-412:51
*** bapalm has joined #openstack-meeting-412:54
*** prithiv has quit IRC12:57
*** mbound has quit IRC12:59
*** prithiv has joined #openstack-meeting-412:59
*** rstarmer has joined #openstack-meeting-413:00
*** iyamahat has joined #openstack-meeting-413:00
*** shaohe_feng has quit IRC13:01
*** shaohe_feng has joined #openstack-meeting-413:01
*** tonytan4ever has joined #openstack-meeting-413:01
*** tsymanczyk has joined #openstack-meeting-413:01
*** yamamoto has quit IRC13:03
*** piet has joined #openstack-meeting-413:05
*** nmadhok has joined #openstack-meeting-413:05
*** rtheis has quit IRC13:07
*** rtheis has joined #openstack-meeting-413:08
*** tonytan4ever has quit IRC13:08
*** sshnaidm_ is now known as sshnaidm13:08
*** shaohe_feng has quit IRC13:11
*** shaohe_feng has joined #openstack-meeting-413:12
*** pmesserli has joined #openstack-meeting-413:13
*** jmckind has quit IRC13:14
*** tonytan4ever has joined #openstack-meeting-413:15
*** bobh has joined #openstack-meeting-413:18
*** yamahata has joined #openstack-meeting-413:19
*** shaohe_feng has quit IRC13:21
*** shaohe_feng has joined #openstack-meeting-413:22
*** ddieterly has joined #openstack-meeting-413:22
*** antonyfm has joined #openstack-meeting-413:25
*** jmckind has joined #openstack-meeting-413:25
*** mbound has joined #openstack-meeting-413:28
*** rtheis_ has joined #openstack-meeting-413:29
*** piet has quit IRC13:30
*** yamahata has quit IRC13:30
*** krtaylor has joined #openstack-meeting-413:30
*** yamahata has joined #openstack-meeting-413:30
*** hvprash has joined #openstack-meeting-413:31
*** rtheis has quit IRC13:31
*** shaohe_feng has quit IRC13:31
*** irenab has quit IRC13:32
*** shaohe_feng has joined #openstack-meeting-413:32
*** hvprash_ has joined #openstack-meeting-413:33
*** antonyfm has quit IRC13:33
*** hvprash has quit IRC13:35
*** hvprash has joined #openstack-meeting-413:36
*** hvprash_ has quit IRC13:40
*** shaohe_feng has quit IRC13:42
*** shaohe_feng has joined #openstack-meeting-413:42
*** hvprash_ has joined #openstack-meeting-413:44
*** sigmavirus24_awa is now known as sigmavirus2413:45
*** ddieterly is now known as ddieterly[away]13:45
*** hvprash has quit IRC13:47
*** abhishek has joined #openstack-meeting-413:52
*** shaohe_feng has quit IRC13:52
*** ddieterly[away] is now known as ddieterly13:52
*** shaohe_feng has joined #openstack-meeting-413:53
*** antonyfm has joined #openstack-meeting-413:55
*** mclaren has joined #openstack-meeting-413:55
*** bunting has joined #openstack-meeting-413:56
*** minwang2 has joined #openstack-meeting-413:57
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, kairat14:00
nikhil#startmeeting glance14:00
openstackMeeting started Thu May  5 14:00:08 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
rosmaitao/14:00
nikhil#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
tsymanczyk\o14:00
nikhilhey guys14:00
abhisheko/14:00
nikhillet's wait another min14:01
mclareno/14:01
dshakhrayo/14:01
buntingo/14:01
wxyo/14:01
nikhillet's get started14:01
nikhil#topic agenda14:01
*** openstack changes topic to "agenda (Meeting topic: glance)"14:01
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
nikhilI'd set a few items. Shouldn't take full hour so we can have some open discussion.14:02
nikhil#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: glance)"14:02
*** shaohe_feng has quit IRC14:02
*** klamath has quit IRC14:02
nikhil#info Updates, upcoming events and more awareness http://lists.openstack.org/pipermail/openstack-dev/2016-May/093703.html14:02
*** shaohe_feng has joined #openstack-meeting-414:02
nikhilThat;s the ML thread describing our checkpoints through the first part of cycle14:03
*** klamath has joined #openstack-meeting-414:03
*** klamath has quit IRC14:03
nikhilI wanted to give people a chance to raise concerns, if any14:03
*** yamamoto has joined #openstack-meeting-414:03
*** armax has joined #openstack-meeting-414:03
nikhilcalling 114:03
nikhilcalling 214:03
*** klamath has joined #openstack-meeting-414:03
nikhilcalling 314:03
nikhilok, none14:04
nikhilSo, let's think about our spec freeze14:04
nikhilI wanted to try out a spec-soft-freeze on R16 (midcycle)14:04
nikhilbasically at this point we will filter out the specs that are likely going to be completed in newton14:05
nikhilthen a spec-hard-freeze on R-1014:05
kragnizo/14:05
nikhilthat will require any outstanding specs to request FFE and we will likely have none but sometimes one or two14:05
nikhilit should give 5 weeks for reviewing the code, bug fixing, release stuff14:06
mclarenwhat's r10?14:06
nikhilany concerns on that?14:06
rosmaitasounds reasonable14:06
nikhil#link http://releases.openstack.org/newton/schedule.html14:06
tsymanczykr10 is jul 25-2914:06
nikhilthe weeks are listed in that schedule using a number 'n' against release weeks14:07
nikhilagain, the code can still get in till newton-3 where we will have a code-hard-freeze14:07
nikhilas a standard openstack practice14:07
*** armax has quit IRC14:08
nikhilthen use RCs as a way to strengthen the release14:08
* sigmavirus24 apologizes for being late14:08
nikhilif nothing, I will move on and get those dates listed on the release schedule14:08
nikhilone more thing:14:09
*** xenogear has joined #openstack-meeting-414:09
nikhilplease let me know soon on your mid-cycle plans as the logitical, travel, etc. planning is not trivial14:09
nikhilmoving on14:10
nikhil#topic Finalize process for lite-specs14:10
*** openstack changes topic to "Finalize process for lite-specs (Meeting topic: glance)"14:10
nikhilour current process is not documented14:10
nikhilalso, people are proposing against the lite specs repo14:10
nikhiland we currently have no way to refer back to those lite specs14:11
nikhilI wanted to propose this:14:11
nikhil1. move lite specs under their separate folder in glance-specs repo14:11
nikhil2. each lite spec has it's own file14:11
nikhil3. code patches for those specs refer the lite-spec url optimistically14:12
nikhilfor example14:12
*** shaohe_feng has quit IRC14:12
nikhilwhen someone is proposing a lite-spec they will choose the file name for it14:12
nikhilso they can anticipate where the spec is going to land14:13
*** prithiv has quit IRC14:13
*** rbak has joined #openstack-meeting-414:13
nikhilin this case the proposal was "buffered-reader-for-swift-driver"14:13
nikhilso the spec showed up on http://specs.openstack.org/openstack/glance-specs/specs/newton/approved/glance_store/buffered-reader-for-swift-driver.html14:13
*** shaohe_feng has joined #openstack-meeting-414:13
*** yamamoto has quit IRC14:13
nikhilobjections?14:13
rosmaita(need a few minutes to think)14:14
nikhilsure14:14
buntingSo what makes this any different to a full spec?14:14
hemanthmjust the content I believe14:14
nikhilyep14:14
nikhilhaving a separate file removes merge conflicts14:15
hemanthmI like it better than the current process14:15
mclarenI'm kinda -1 on lite-specs in general (but I realise that's not what's being asked)14:15
nikhilmclaren: 😃14:15
rosmaitamclaren: say some more14:15
nikhilmclaren: how about we try to make the process faster (with a few experiments)14:16
rosmaitanikhil: my charset can't disply whatever symbol you typed14:16
rosmaita(unless it was a question mark inside a diamond)14:16
nikhilok, yeah. I'd ask for info rather than presume based on implicit input!14:16
nikhilrosmaita: it was a smiley14:16
nikhil:)14:16
mclarenwe're going to end up with release notes, commit messages, docs and lite-specs which will probably have a fair amount of duplication14:17
nikhil(but with extra semi-colon)14:17
*** hvprash_ has quit IRC14:17
*** hvprash has joined #openstack-meeting-414:17
nikhilrelease notes are bit independent from the lite-specs14:17
mclarenbut I'm happy to trial whatever folks want, I don't mind14:17
nikhilbut I agree there is a likelihood of duplication14:18
buntingJust to get this clear, if I have a spec i want to propose, there would be no difference except the amount of boxes I have to fill in?14:18
nikhilto faster things up was one of the idea for a drivers' meeting but I guess that did not work (ETOOMANTMEETINGS)14:18
rosmaitabunting: are you anticipating that everyone will file lite specs from now on?14:19
nikhilbunting: for lite-spec you do not need a BP, you need may be feedback from just 2 cores whereas the specs are about feedback from as many cores as possible and then +W from PTL/liaison14:19
buntingIt just seems the process is basicly the same, why don't we just make more option optional on a regular spec?14:20
nikhilwe have redacted on the process for specs already14:20
*** prithiv has joined #openstack-meeting-414:20
nikhilat this point only API impact, security oriented and new functionalities are required to have specs14:21
*** sdague has quit IRC14:21
*** sdague has joined #openstack-meeting-414:22
nikhillite-specs are about making sure the service behavior is consistent with it's constructs, original use cases (so that stakeholders inproduction are not affected), and to help those who don't have access to a large scale infra for testing, CI or staging/prod environments where things behave tenatively14:22
*** xenogear has quit IRC14:22
*** shaohe_feng has quit IRC14:23
nikhilbottom line -- lite specs are knowledge sharing, awareness for across openstack ecosystem and ability to understand the direction of a program without diving into commit messages14:23
nikhilok, we've spent enough time on this topic14:23
*** shaohe_feng has joined #openstack-meeting-414:23
nikhilwe can continue during open discussion or after the meeting on #openstack-glance14:24
buntingnikhil: sure14:24
nikhilmoving on14:24
nikhil#topic What is this config option intended for https://github.com/openstack/glance/blob/master/glance/scrubber.py#L36-L38 ? (hemanthm)14:24
*** openstack changes topic to "What is this config option intended for https://github.com/openstack/glance/blob/master/glance/scrubber.py#L36-L38 ? (hemanthm) (Meeting topic: glance)"14:24
hemanthmyep, that's me14:24
hemanthmI was working on config opts and I just wanted to get a better feel of why that opt was introduced14:25
hemanthmdoes anyone remember/know?14:25
mclarenmy guess14:25
hemanthmoperators being able to recover image data for customers who delete images accidentally is one I could think of14:25
mclarenis the amount of time which needs to elapse before an image in pending_delete is deleted14:25
hemanthmmclaren: +1 but do you know what purpose is it serving?14:26
nikhilmclaren: was someone actually using it?14:26
*** sbog has quit IRC14:26
mclarenyeah, we switched it on in our cloud14:26
mclarenI think everything is probably deleted by this point :-)14:26
*** spotz_zzz is now known as spotz14:27
*** krotscheck has quit IRC14:27
hemanthmsimply put, as an operator why would I want to use this config opt?14:27
nikhilah, what would be a ideal/average delay you would say?14:27
mclarenwe did have an idea that we could recover mistakenly deleted images14:27
mclarenI'm not sure we ever actually did such a recovery14:27
nikhilI see14:28
rosmaitaalso, isn't the image record deleted at this point, i.e., all the additionalProperties are non-recoverable?14:28
rosmaitai mean by normal API means14:28
nikhilmy guess was that if you had a volume attached or a NFS system you could do a routine maintanence for the system to preserve the images14:28
rosmaitathe stuff is in the DB, but you have to muck around in there to resurrect the full image record14:28
nikhilmclaren: should we assume that people are not using it?14:29
mclarenright so the data and metadata experience would be equivalent14:29
hemanthmnikhil: we use it too14:29
nikhiloh ok14:29
hemanthmI don't know how many folks are actually using scrubber14:30
nikhilok, do we have all the answers?14:30
nikhilhemanthm: ?14:31
hemanthmhmmm, not sure14:31
nikhilwe're running short of time, btw14:31
hemanthmok, we can take it offline14:31
rosmaitahemanthm: maybe propose to deprecated that option in your patch14:31
nikhilhemanthm: if we have specific questions, I think that would help14:31
rosmaitaguess that should be a different patch, though14:32
mclarenwhat's the motivation to deprecate?14:32
*** zhurong has quit IRC14:32
nikhilno use14:32
rosmaitawell, it seems pretty useless14:32
rosmaitawe should remove, or add more support14:32
hemanthmsimply put, as an operator why would I want to use this config opt?14:32
hemanthmnikhil: ^ that was my question14:32
nikhilhemanthm: ok. so, we need to take that to the operators' ML. we are likely not to get answers here.14:33
rosmaitai think fei long floated the idea of an undelete admin call a few cycles ago, but it was voted down14:33
*** shaohe_feng has quit IRC14:33
*** nmadhok has quit IRC14:33
*** krotscheck has joined #openstack-meeting-414:33
nikhilhemanthm I can ask IBM folks, next week14:33
hemanthmthanks nikhil14:33
nikhilok, moving on14:33
nikhil#topic Image upload to specific backend https://review.openstack.org/#/c/310970/ (wxy or nikhil)14:33
*** emagana has joined #openstack-meeting-414:33
*** openstack changes topic to "Image upload to specific backend https://review.openstack.org/#/c/310970/ (wxy or nikhil) (Meeting topic: glance)"14:34
*** shaohe_feng has joined #openstack-meeting-414:34
nikhilso, we decided during the summit that we are not going to expose "which glance stores are configured for glance deployment"14:34
mclarenif someone hacks your db to set pending_delete it may be useful to not delete everything straight away?14:34
rosmaitamclaren: you already have the scrubber interval14:34
*** nmadhok has joined #openstack-meeting-414:35
rosmaitathis is in addition to that14:35
mclarenok, but this is per image? the scrubber interval could fire straight away14:35
hemanthm++ mclaren14:35
rosmaitai really think zhi added this for the undelete call that didn't happen14:35
*** rtheis has joined #openstack-meeting-414:36
nikhilguys we need to take this offline14:36
nikhil(the topic has changed btw)14:36
rosmaitasorry14:36
nikhilso, as per agreement: how will I know which stores (are configured and thus) to upload the image to14:37
*** piet has joined #openstack-meeting-414:37
nikhilalso, the store configuration are supposed to be opaque from users' perspective14:37
nikhiland that could potentially change indeterministically14:37
*** rtheis_ has quit IRC14:38
nikhilthe feedback asks for admin only way14:38
*** mageshgv has joined #openstack-meeting-414:38
nikhilwhat's the feeling here?14:38
hemanthmis there a specific use-case for uploading to a particular store?14:38
*** emagana has quit IRC14:39
mclarenthere seemed to be interest at the summit14:39
nikhilI asked for it on the lite spec14:39
*** emagana has joined #openstack-meeting-414:39
nikhilmclaren: from ops?14:39
rosmaitahemanthm: maybe snapshots to cheap slow store, public images to fast store14:39
mclarenI'm a bit uncomfortable with the leaky abstraction side of this14:39
rosmaitamclaren: +114:39
*** djkonro has joined #openstack-meeting-414:39
mclarenDo swift have something like storage policies?14:39
nikhilmclaren: +1M14:39
hemanthm++ mclaren14:39
mclarenwhich expose the idea of different backends, but without exposing the 'internals'?14:40
nikhilgood point14:40
*** hdaniel has quit IRC14:40
nikhilmclaren: do you mind starting discussion on that thread on the lite-spec?14:41
*** MarkAtwood has joined #openstack-meeting-414:41
nikhil(as I do not see wxy here today)14:41
nikhil(or he's hiding)14:41
djkonronikhil: Hello14:42
nikhildjkonro: hello14:42
*** anilvenkata has quit IRC14:42
nikhilaight, let's take this on the spec. (no movement on the question here)14:43
mclarenI think it's possible I may not have any upstream cycles for the forseable future14:43
nikhilwat!14:43
wxyI'm here. But for my poor English, I don't want waste your guys time. Just as nikhil said, point out this question and we can't discuess it through the lite-spec.:)14:43
*** shaohe_feng has quit IRC14:43
wxys/ can't/can14:43
mclarensome internal stuff going on14:44
nikhilwxy: ah hey, yeah let's chat more on lite-spec. we're a bit short on time too.14:44
*** shaohe_feng has joined #openstack-meeting-414:44
nikhilmclaren: that's a bummer. we need to chat offline on this!14:44
mclarensure14:44
nikhilbut for wxy's concern , I can start that discussion on the lite spec proxy mclaren14:45
nikhilmoving on14:45
nikhil#topic     community_images_newton.__init__(assigned=tsymancz1k, cores_involved=[rosmaita, nikhil])14:45
*** openstack changes topic to "community_images_newton.__init__(assigned=tsymancz1k, cores_involved=[rosmaita, nikhil]) (Meeting topic: glance)"14:45
nikhiltsymanczyk: rosmaita : floor is yours14:45
rosmaitatsymanczyk has been working on updating the spec14:45
tsymanczykat this point i'm working on incorporating the existing feedback to the spec.14:45
tsymanczyki'm afraid i don't have an overall understanding that's ... sufficient to have opinions of my own. yet.14:46
rosmaitai guess my main question is whether the hierarchical stuff affects what we do here14:46
nikhilI see14:46
nikhilMy main design point on hierarchical stuff was visibility14:47
nikhilso, the answer is 'may be'14:47
mclarendoes the hierarchical stuff affect community sharing more that the existing peer-to-peer sharing?14:47
mclarenthat/than14:47
*** emagana has quit IRC14:47
rosmaitamclaren: i think so, in that we introduce these new visibility values14:48
nikhilI doubt that, but depends on how keen and in what way we plan to clean visibility semantics14:48
*** cdelatte has joined #openstack-meeting-414:48
rosmaitathe problem i see is that you could have public, private, protected14:49
nikhilrosmaita: I see. so the refactor around visibility is something that may affect.14:49
nikhil(rosmaita: please keep going)14:49
rosmaitai may need to write this up in an etherpad14:50
rosmaitai don't think i have a one-minute explanation of what's bothering me14:50
*** sdake has joined #openstack-meeting-414:50
nikhilok :)14:50
rosmaitai will take an action item to do tha14:50
rosmaitat14:50
*** hvprash has quit IRC14:51
nikhiltsymanczyk: we (all of us) can chat offline on the architecture stuff14:51
nikhilrosmaita: ok, thanks.14:51
tsymanczykok14:51
*** hvprash has joined #openstack-meeting-414:51
nikhil#action rosmaita to open a etherpad to discuss changes for visibilty flags14:51
nikhilmoving on14:52
nikhil#topic image import: implementation feedback ( mclaren )14:52
*** openstack changes topic to "image import: implementation feedback ( mclaren ) (Meeting topic: glance)"14:52
nikhilmclaren: we are short of time, so we can go with your topic first14:52
mclarenok, thanks14:52
*** SimonChung1 has quit IRC14:52
mclarenhttps://review.openstack.org/#/c/312653/14:53
mclarenI've a bunch of questions on that patch14:53
mclarenit might be a bit moot, but if folks can have a look and comment that would be appreciated14:53
nikhilthanks for breaking them down!14:53
*** shaohe_feng has quit IRC14:53
*** jmckind has quit IRC14:54
mclarennp, it's the easy stuff so far...14:54
nikhilso my main worry with re-using existing task stuff is that the admin API and import API overlap at some point14:54
*** shaohe_feng has joined #openstack-meeting-414:55
mclarenwhat's the admin api?14:55
nikhilbasically, an can start running a task for an image (say stored in users' container)14:55
nikhilmclaren: the task api is the admin (task) API14:56
nikhilas it used to be the (former) import API, I want to avoid overloading that term14:56
rosmaitamclaren: the default is admins only use it in mitaka, i believe14:56
nikhilcorrect14:56
nikhils/an can/ an admin can/14:57
*** lei-zh has joined #openstack-meeting-414:57
nikhil3 mins to go14:57
mclarenI'm done14:57
nikhilthanks!14:57
nikhil#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:57
nikhilI'd a chat with flwang yday on14:58
nikhil    https://bugs.launchpad.net/glance/+bug/152845314:58
openstackLaunchpad bug 1528453 in Glance "Provide a ranking mechanism for glance-api to order locations" [Wishlist,Triaged] - Assigned to Jake Yip (waipengyip)14:58
nikhilI need some input on: do people this this is a good idea or bad? is someone else using it in production?14:58
nikhilmy feeling was that glance shouldn't bother with the values of the metadata14:59
*** TravT has joined #openstack-meeting-414:59
nikhilas it does not bother with values of the build_flags or licensing info14:59
nikhilthat should be done on the user side14:59
*** jmckind has joined #openstack-meeting-414:59
rosmaitai thought there was already some kind of strategy for this?14:59
nikhilthe patch associated with it is linked in the bug in my comment14:59
rosmaitathat you can configure?14:59
nikhilrosmaita: good point, I do not know if there's overlap though15:00
nikhilworth investigating15:00
nikhiland we're out of time15:00
nikhilthanks all for joining!15:00
*** antonyfm has quit IRC15:00
nikhil#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu May  5 15:00:55 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-05-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-05-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-05-14.00.log.html15:01
*** sjmc7 has joined #openstack-meeting-415:01
*** abhishek has quit IRC15:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu May  5 15:01:31 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
*** tsymanczyk has left #openstack-meeting-415:01
TravTo/15:01
*** raj_singh has joined #openstack-meeting-415:01
lei-zho/15:02
rosmaitao/15:02
sjmc7morning15:02
TravTlight crowd today15:02
*** yingjun has joined #openstack-meeting-415:02
rosmaitabut high-quality15:02
*** lakshmiS_ has joined #openstack-meeting-415:03
yingjunHi15:03
TravTyes15:03
*** mbound has quit IRC15:03
*** prithiv has quit IRC15:03
TravTagenda: https://etherpad.openstack.org/p/search-team-meeting-agenda15:03
lakshmiS_o/15:03
TravT#topic summit notes15:03
*** openstack changes topic to "summit notes (Meeting topic: openstack search)"15:03
TravTin case you didn't see15:04
TravTi sent out notes to the ml15:04
TravT#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093861.html15:04
*** shaohe_feng has quit IRC15:04
TravTI forgot to mention the most critical part... rosmaita brought pie15:04
*** shaohe_feng has joined #openstack-meeting-415:05
*** adreznec has joined #openstack-meeting-415:05
*** prithiv has joined #openstack-meeting-415:05
sjmc7:)15:05
TravTIt was really great to meet you in person yingjun15:05
yingjunme too15:05
TravTi feel quite honored to have bought you your first american beer15:06
yingjun:)15:06
*** prithiv has quit IRC15:06
yingjunnice beer, thank you15:06
TravTokay, so, out of those notes, there are a couple things to talk about, i think.15:06
TravT#topic Nova Cells v2 List API Proposed to be backed by Searchlight15:07
*** openstack changes topic to "Nova Cells v2 List API Proposed to be backed by Searchlight (Meeting topic: openstack search)"15:07
TravT#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093716.html15:07
TravTjump to the section on pagination15:07
*** vhoward has joined #openstack-meeting-415:08
TravTitem 4 under the pagination section15:08
TravTi'll paste here15:08
TravT4. Use the OpenStack Searchlight project for doing massive queries like15:08
TravTthis. This would be optional for a cell of one but recommended/required15:08
TravTfor anyone running multiple cells. The downside to this is it's a new15:08
TravTdependency, and requires Elasticsearch (but many deployments are15:08
TravTprobably already running an ELK stack for monitoring their logs). It's15:08
TravTalso unclear at an early stage how easy this would be to integrate into15:08
TravTNova. Plus deployers would need to setup Searchlight to listen to15:08
TravTnotifications emitted from Nova so the indexes are updated in ES. It is,15:09
TravThowever, arguably a better tool for the job than Nova trying to deal15:09
TravTwith filtering and sorting with python. There is general agreement15:09
TravTwithin the core team that this is the path forward, but it's going to15:09
TravTrequire investigation and testing before we get a better idea of how15:09
TravTfeasible this is.15:09
*** daneyon has joined #openstack-meeting-415:09
*** mbound has joined #openstack-meeting-415:09
TravTi think this is really important for us to support this effort15:10
sjmc7yep15:11
TravTand a big part / perhaps the main thing is for us to work on the versioned notifications15:12
yingjungreat, but not sure how will cell v2 integration with searchlight15:12
TravTwell, that's essentially the task in front of us15:13
TravTto help figure that out15:13
TravTi sent a response to the ML15:13
rosmaitai am kind of concerned about the mix of internal and user-facing data here15:13
rosmaitabut maybe i am missing hte point15:14
TravTthis is only meant for instances15:14
* david-lyle shuffles in late15:14
sjmc7take a seat, lyle. at the front.15:14
*** shaohe_feng has quit IRC15:14
TravTif you look at this message at the very bottom15:14
TravThttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093657.html15:14
TravT4) Have all instance listing operations in the Compute API proxy to a15:14
TravTcall to Project Searchlight and ElasticSearch to handle the cross-cell15:14
TravTqueries against the instance and instance update (task) information.15:14
*** shaohe_feng has joined #openstack-meeting-415:15
rosmaitai guess the idea is that the api db won't have a lot of hte data, and instead of calling out to hte cell dbs, just let searchlight listen to notifications, and then use the searchlight index15:15
rosmaita(ok, you already answered while i was typing)15:15
*** pleia2 has joined #openstack-meeting-415:15
sjmc7i think yeah, there are now multiple DBs and they don’t want to have to aggregate them15:15
rosmaitaok, concern withdrawn15:15
david-lyleall list API calls or just cells?15:16
TravTyes, they don't have a solution for querying across them that supports sorting, filtering, pagination15:16
*** regXboi has joined #openstack-meeting-415:16
* david-lyle reads email15:16
sjmc7it would be unnecessary for single cell, but depends how they want to do it i guess15:16
sjmc7they will have to support *something* for both single and cross cell cases in the absence of SL, it just might not be as good15:17
TravTdavid-lyle: this one is the better one to read15:17
TravT09:07 TravT: #link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093716.html15:17
TravT09:07 TravT: jump to the section on pagination15:17
TravTthis youtube video was helpful: https://www.youtube.com/watch?v=Sieza5iMBXY15:18
david-lylewell that would help adoption :)15:18
*** mat128 has left #openstack-meeting-415:18
TravTdavid-lyle: yeah, i would think so15:18
TravTbut basically, the direction they are going is that they want cells to be THE way that nova is deployed15:19
*** TravT has quit IRC15:19
*** TravT has joined #openstack-meeting-415:20
TravTgot dropped15:20
*** antonyfm has joined #openstack-meeting-415:20
* TravT taps mic15:20
sjmc7:)15:21
sjmc7tough audience15:21
TravT:)15:21
*** julim has quit IRC15:22
*** geseib007 has joined #openstack-meeting-415:22
TravTSo, sjmc7 and I think that the most critical part of us supporting this is the versioned notifications15:22
TravTthere is an ML thread on that15:22
TravThttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093962.html15:22
sjmc7more accurately, i think it’s really important we stop hitting the API every notification15:23
*** basilAB has quit IRC15:23
*** Swami has joined #openstack-meeting-415:23
TravTyes (our whole fishbowl session) :)15:23
sjmc7and versioned notifications seem tio be the way we can get extra data into the notifications15:23
*** basilAB has joined #openstack-meeting-415:23
*** med_ has quit IRC15:23
TravTbut as a part of that, we also need to make sure we have the ability to return the correct version of the data15:23
TravTas nova has a versioned api15:24
*** med_ has joined #openstack-meeting-415:24
david-lyleso we'll have to map the object to the requested version?15:24
TravTnot entirely sure yet...15:24
*** shaohe_feng has quit IRC15:24
*** julim has joined #openstack-meeting-415:24
*** med_ is now known as Guest8250615:24
sjmc7*shudder*15:24
TravTdon't know if we'll just index 1 version15:24
david-lyleand also support specifying a version filter per request15:24
TravTor need to index more than one15:24
TravTso, part of the versioned notification work is a schema that nova will provide15:25
*** Guest82506 is now known as medberry15:25
*** medberry has quit IRC15:25
*** medberry has joined #openstack-meeting-415:25
TravTthat in theory will allow us to drive data mapping15:25
*** shaohe_feng has joined #openstack-meeting-415:25
TravTand can be used for creating the object version15:25
*** geseib has quit IRC15:25
*** armax has joined #openstack-meeting-415:25
david-lyleso nova does the object version munging ?15:25
TravTso, i got slammed with a bunch of things early this week and haven't been able to go through all the related specs yet15:26
david-lylerequest -> nova -> searchlight -> nova -> object versioning -> reply15:26
TravTyeah, that's the question to be answered.15:27
david-lylethat would be best rather than duplicate logic15:27
TravTif they expect all versions to be supported15:27
TravTthat's interesting david15:27
TravTif multiple versions are to be supported, i like that concept15:28
sjmc7yeah, that’s an interesting option. that might require us to index exactly as nova does in its DB15:28
lakshmiS_Which will have security implications if user goes to SL for same data15:29
sjmc7or at least exactly as a particular version (probably the latest one) looks. but that might be much better than us doing it15:29
sjmc7i guess we need to talk to them more15:29
david-lylesjmc7: or just provide the relevant fields and nova translates15:29
sjmc7but first thing is supporting the versioned stuff at all15:29
sjmc7yeah15:29
TravTyeah, i attended the nova cells meeting yesterday, but stayed invisible15:29
TravTtoo many things going on15:29
TravTbut my impression was that everybody is catching up from the summit and discussions can begin in earnest next week15:30
TravTI think there are several possibilities15:30
TravT1) david's idea15:30
TravT2) we configure to index a certain version15:30
TravT3) we index multiple versions and store the version as a field we filter on15:31
TravTwe have a blueprint now15:32
TravThttps://blueprints.launchpad.net/searchlight/+spec/nova-versioned-notifications15:32
TravTfrom our side15:32
TravTi think i'll turn that into a spec15:32
TravTbecause this got complicated15:32
*** iyamahat has quit IRC15:32
*** yamahata has quit IRC15:33
TravTi'm also curious if we should make this higher priority (currently high)... maybe essential?15:34
*** minwang2 has quit IRC15:34
sjmc7it is dependent on nova actually implementing it15:34
TravTyes, that is true15:34
*** shaohe_feng has quit IRC15:34
TravTbut, we should do everything on our part to support it, i think15:35
yingjundoes sl support listening multiple notification topics at the same time? cause the versioned notification topic is hard coded15:35
*** shaohe_feng has joined #openstack-meeting-415:35
sjmc7it can do15:36
TravThttps://github.com/openstack/searchlight/blob/725862a637d4cdf09901a52929453bdde02e3558/searchlight/elasticsearch/plugins/base.py#L4215:36
*** djkonro has left #openstack-meeting-415:36
TravTeach plugin can configure its own.15:36
sjmc7we’d need to support pools i think15:37
yingjunbut for nova plugin, can i config both versioned_notification and searchlight_indexer?15:37
sjmc7i haven’t tested it, but in theory yes. it might get a bit confusing15:37
TravTmaybe we'd actually have two plugins15:37
TravTyou can enable versioned or you can enable legacy15:37
sjmc7urgh15:38
sjmc7maybe in that case we should fix the issue we currently have (not slamming the API) with the existing notifications15:39
TravTbecause I'm not sure versioned notifications are guaranteed to be enabled either.15:39
*** galstrom_zzz is now known as galstrom15:39
yingjunactually when i was testing the hypervisor plugin, i have to make this to notifications_topic to versioned_notification, so it only listen the versioned one15:39
yingjunso the instance notifications are not received at all15:40
*** nmadhok has quit IRC15:40
TravTsjmc7 i'm okay with that.15:41
TravTyou have a blueprint it seems and i also filed something.15:41
sjmc7yeah, there’s no legacy notifications going forward15:41
sjmc7we could just make the call that we only support versioned ones15:42
sjmc7so deployers should set it to versioned or both15:42
sjmc7little bit wary of us unnecessarily complicating testing15:42
TravTsjmc7, i'd rather first consider marking it deprecated until we understand all the ramifications of dropping the old15:42
sjmc7well right now we can’t drop it :)15:43
TravTso, we don't have to "support" it15:43
TravTbut it is available for deployers who want to say upgrade horizon and use SL....15:43
TravTi don't know15:43
sjmc7if it’s in the 1.0 release it becomes a burden15:43
TravTneed to think about it as part of this work with versioned notifications15:43
TravTsee what comes of them15:43
sjmc7the only reason i bring it up is that if we are gonna support it we need to decide how to cope with the missing data15:43
sjmc7if we put oureggs in the versioned basket we maybe don't15:44
*** davidsha has joined #openstack-meeting-415:44
TravTyeah, fair point15:44
sjmc7dunno how we decide :)15:44
TravTi think we need to dig into the versioned notifications more15:44
TravTyingjun15:44
TravTwasn't ignoring what you said above15:45
*** shaohe_feng has quit IRC15:45
sjmc7just to be clear right now they aren’t written for instances (nor is the spec approved yet)15:45
yingjunyeah15:45
sjmc7but yeah, we can gaze into the future a little15:45
*** minwang2 has joined #openstack-meeting-415:46
*** shaohe_feng has joined #openstack-meeting-415:46
TravTi know... jay was insistent that it will get done this release.  which he can't guarantee, but i'd like to work optimistically towards that direction since it will happen at some point.15:46
sjmc7yep15:46
*** gangil has joined #openstack-meeting-415:46
TravTyingjun: you have the most direct investigation at this point due to your hypervisor work15:46
sjmc7so one conversation we can have is what we do to avoid hammering the API with the existing notifications, because there’s no guarantee we’ll get more fields in newton even with versioned notifications15:46
TravTyingjun would you be able to also look at the15:47
TravThttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093962.html15:47
yingjunsure15:47
TravTand regarding the dual listener thing, if that is a bug or needs a blueprint, please file and let's figure it out15:47
sjmc7i’ll need some convincing on that15:48
*** minwang2 has quit IRC15:48
*** sridhar_ram has joined #openstack-meeting-415:48
*** numans has quit IRC15:48
TravTsjmc7: looks like i filed a twin bug to your bp15:49
TravThttps://bugs.launchpad.net/searchlight/+bug/157794715:49
openstackLaunchpad bug 1577947 in OpenStack Search (Searchlight) "Disable intermediate instance action callbacks in Nova" [Undecided,New]15:49
*** salv-orlando has joined #openstack-meeting-415:49
*** jmckind_ has joined #openstack-meeting-415:50
sjmc7the more the merrier15:50
TravTrosmaita: lakshmiS_ yingjun david-lyle any thoughts on15:50
TravThttps://bugs.launchpad.net/searchlight/+bug/1577947 & https://blueprints.launchpad.net/searchlight/+spec/optionally-disable-some-events15:50
openstackLaunchpad bug 1577947 in OpenStack Search (Searchlight) "Disable intermediate instance action callbacks in Nova" [Undecided,New]15:50
TravTsjmc7, i think what you suggest makes sense.  just a simple config for events to ignore.15:51
sjmc7yeah, that only halfway solves it though15:52
TravTthen it can be tuned in the field.15:52
rosmaitamy feedback is that this can be independent of the versioned notification payloads15:52
david-lyleso 1577947 you just ignore certain events?15:52
sjmc7ultimately i still feel pretty strongly we need to not hit APIs at all15:52
TravTi think that possibly would be another configurable option15:52
TravTnotification_data_only15:53
sjmc7yeah, we’ve argued it forever :)15:53
david-lyleseems reasonable as long as error states are caught and updated15:53
*** jmckind has quit IRC15:53
TravTwe could first implement as a nova only thing15:53
TravTthen generalize if needed15:53
rosmaitamakes sense, nova is the most chatty of the services15:54
*** uck has joined #openstack-meeting-415:54
TravTalright should i delete the bug of the BP?15:55
TravTany preference?15:55
yingjunagree with the configurable option15:55
sjmc7i would still like (we’re out of time now, but sometime) to see what it looks like if we cut out API calls entirely. the reason i’m so against it is that it makes deployment configuration much harder15:55
*** shaohe_feng has quit IRC15:55
sjmc7but i will say no more now15:55
*** shaohe_feng has joined #openstack-meeting-415:56
TravTokay, i'll prioritize one of the two up and delete the other.15:56
TravTalso, given this is all around pagination15:57
TravTi was previously blocked on using server side pagination in the searchlight-ui due to the magic search widget's integration with smart table (horizon stuff).  I think that is out of the way now, so i'm going to look at making that change.15:57
sjmc7that’ll be a good change15:58
*** eil397 has joined #openstack-meeting-415:58
*** fitoduarte has quit IRC15:58
TravThttps://blueprints.launchpad.net/searchlight/+spec/searchlight-ui-pagination-scrolling15:58
TravTokay, we are out of time.15:58
*** gangil has quit IRC15:59
TravTplease if you have time look into the versioned notifications to understand it better so we can work towards this effectively.15:59
TravTi appreciate all your time today!15:59
rosmaitago team!15:59
TravTand comment on the specs already up if you can15:59
TravT:)15:59
TravTrosmaita might even bring more pie in the future16:00
*** iyamahat has joined #openstack-meeting-416:00
TravTokay, adios!16:00
TravT#endvote16:00
*** ametts has joined #openstack-meeting-416:00
TravTor something like that16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May  5 16:00:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-05-15.01.html16:00
*** jmccrory_ has joined #openstack-meeting-416:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-05-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-05-15.01.log.html16:00
*** lakshmiS_ has left #openstack-meeting-416:00
*** sjmc7 has left #openstack-meeting-416:00
*** lei-zh has left #openstack-meeting-416:00
*** gangil has joined #openstack-meeting-416:01
*** yingjun has left #openstack-meeting-416:02
odyssey4me#startmeeting OpenStack-Ansible16:03
openstackMeeting started Thu May  5 16:03:40 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:03
openstackThe meeting name has been set to 'openstack_ansible'16:03
odyssey4me#topic Rollcall & Agenda16:03
*** openstack changes topic to "Rollcall & Agenda (Meeting topic: OpenStack-Ansible)"16:03
spotz\o/16:03
*** Zucan has joined #openstack-meeting-416:04
mrhillsman\o/16:04
d34dh0r53o/16:04
*** b3rnard0 has joined #openstack-meeting-416:04
*** evrardjp has joined #openstack-meeting-416:04
evrardjpo?16:05
evrardjpo/16:05
jmccrory_o/16:05
*** prometheanfire has joined #openstack-meeting-416:05
prometheanfireo716:05
b3rnard0\o/16:05
amettso/16:05
*** shaohe_feng has quit IRC16:05
eil397o/16:06
*** shaohe_feng has joined #openstack-meeting-416:06
* mhayden woots16:06
spotzb3rnard0: !!!!:)16:06
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:07
odyssey4meWelcome back everyone - hope you all enjoyed the summit and have sufficiently recovered. :)16:07
odyssey4me#link http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-04-21-16.02.html16:08
odyssey4me^ minutes from the last meeting16:08
odyssey4me#action carried item: odyssey4me to add review for the collection of IRR job logs16:08
odyssey4meThe rest of the action items were completed.16:08
odyssey4me#topic Cleanup of Appendix section in docs16:09
*** openstack changes topic to "Cleanup of Appendix section in docs (Meeting topic: OpenStack-Ansible)"16:09
odyssey4meevrardjp over to you16:09
evrardjpthanks16:09
*** TravT has left #openstack-meeting-416:09
evrardjpit's simple: this page http://docs.openstack.org/developer/openstack-ansible/install-guide/app-configfiles.html16:09
evrardjpbrought confusion in the past16:09
*** michaelgugino has joined #openstack-meeting-416:10
evrardjpbecause the configuration explained in openstack_user_config.yml isn't  what was fully described in the rest of the docs page16:10
*** yamahata has joined #openstack-meeting-416:10
evrardjpMy suggestion: Stop using these examples16:10
evrardjpActions points on this: Remove these examples, and adapt (when necessary) the doc16:11
evrardjpImpact: We don't have to worry about these useless files that we carry16:11
*** stevelle has joined #openstack-meeting-416:12
evrardjpNo other impact, at least for now? What's your opinion?16:12
palendaeSo I think having example files is useful in order to give full context16:12
palendaeIn-line snippets in docs can lose stuff like indentation, which people have had problems with before16:12
ZucanI wonder if it needs to be tailored more towards "use cases" with some example configs associated with use scases.16:12
palendaee.g. network information being under global_ovrrides16:13
palendaeBut I agree that carrying *two* things is a bad idea16:13
odyssey4meI fully agree. I've made my thoughts on duplicated documentation quite clear previously. A previous discussion about this resulted in https://review.openstack.org/291310 which removed the networking config example and moves it into docs. I would like to see more of that.16:13
michaelgugino++16:13
palendaeThis did come up at summit, that we carry example files for specfic gate scenarios16:13
evrardjppalendae the context for examples is already a part of another of my commits, however insisting on the indentation wasn't16:13
evrardjpgood point there16:13
odyssey4mepalendae with use-cases defined properly I will support example configs - but those examples will be used by the gate and therefore properly maintained16:14
palendaeevrardjp: If the examples can provide at least the headers that the secction is indented under, that's good16:14
evrardjpso if I push this goog practice, are we ok for removing the files from the doc ?16:14
odyssey4mealso the config files should not explain things, that's what docs are for - they're simply samples16:14
*** medberry is now known as med_16:14
palendaeodyssey4me: Sure, I'm not for having prose in example configs, or full configs in prose16:14
evrardjpok16:14
odyssey4meanother point of context is that we discussed much of this at length in the summit session https://etherpad.openstack.org/p/openstack-ansible-newton-role-docs16:15
palendaeAnd if they're maintained configs, that's cool16:15
*** bpokorny has joined #openstack-meeting-416:15
palendaePeople learn in different ways, and having only the prose with isolate segments would be confusing for me16:15
*** shaohe_feng has quit IRC16:15
odyssey4mebut for the moment, evrardjp if you'd like to move ahead then please do - it'll take some time for the docs work to come to fruition and the changes you put in will likely merge before they really take full effect16:16
evrardjpthat's why we have a conversation palendae , good to know16:16
palendaeYeah, I won't/can't block it, just sharing my view16:16
evrardjplet's try and we'll see, nobody seems against the principle16:16
*** shaohe_feng has joined #openstack-meeting-416:16
odyssey4mepalendae the general drive is that the roles should largely be self documenting by good commenting in the defaults files16:16
palendaeodyssey4me: Yeah, that's fair16:16
odyssey4methe docs then simply include the defaults files16:16
palendaeYep16:17
palendaeI liked that example16:17
palendaeI seem to be in the minority, worth hearing a different view of it at least16:17
spotzWorst comes to worse we do a few folks don't like it and we try something new16:17
odyssey4mealso the tests done in the roles are supported by documentation which describes the design implemented, and provides included config files to show the example16:17
odyssey4methat's the bit we need to work on asap16:17
odyssey4mewe need to figure out how practical it is to do that16:18
evrardjpwe took 16% of the meeting with this conversation, let's move on :D16:18
odyssey4melol, ok - moving on16:19
odyssey4me#topic Newton Summit Retrospective16:19
*** openstack changes topic to "Newton Summit Retrospective (Meeting topic: OpenStack-Ansible)"16:19
spotzI thought it went well, lot of new faces16:19
*** unicell1 has quit IRC16:19
odyssey4meI'll try to put my thoughts together and publish a blog post before the next meeting.16:20
odyssey4meAny comments/thoughts/questions?16:20
michaelguginono16:21
evrardjpI'll wait for the blog post then16:22
odyssey4mealright, moving on16:22
odyssey4me#topic Release Planning and Decisions16:22
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: OpenStack-Ansible)"16:22
odyssey4meKilo 11.2.15 has just been tagged16:22
odyssey4meDoes anyone know of any reason not to tag Mitaka 13.0.2 and Liberty 12.0.12 today?16:23
evrardjpNone16:23
*** salv-orlando has quit IRC16:23
*** prithiv has joined #openstack-meeting-416:23
odyssey4meI mean, besides https://review.openstack.org/309511 not merging yet. :p16:24
*** janki91 has joined #openstack-meeting-416:24
odyssey4menow that it's passed the gate, please can I get some core reviews on that16:24
prometheanfire:P16:24
*** bpokorny has quit IRC16:24
odyssey4mejmccrory automagically cloudnull d34dh0r53 stevelle mattt hughsaunders andymccr ^16:24
*** shaohe_feng has quit IRC16:26
cloudnullodyssey4me: done16:26
odyssey4meok, moving on - I'll request the tags later16:27
odyssey4me#topic Ubuntu 16.04 LTS Support16:27
*** openstack changes topic to "Ubuntu 16.04 LTS Support (Meeting topic: OpenStack-Ansible)"16:27
*** shaohe_feng has joined #openstack-meeting-416:27
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-newton-ubuntu16-0416:27
odyssey4meneed another review on https://review.openstack.org/#/c/286282/16:28
michaelguginoI'm working on galera_server as we speak16:28
odyssey4memichaelgugino thanks - please assign it to yourself under the 'SystemD Support work item16:28
*** sdake_ has joined #openstack-meeting-416:28
cloudnullI've got much of the systemd init bits worked out, i'd be happy to throw up an initial review for the os.* roles.16:29
michaelguginook.  I plan on doing galera_client this week (as it will be needed by galera_server)16:29
cloudnullif someone already has something on that too, maybe we can combine efforts and tackle it across the OS roles16:29
odyssey4mecloudnull cool - can you assign yourself to the roles in the etherpad to ensure that everyone else is aware that you're on it16:30
michaelguginorabbitmq 16.04 support after jimmy's patch hits16:30
evrardjpFYI I'm trying to contact keepalived package maintainers for 16.04 support16:30
odyssey4meor assign one on it as you start work on it16:30
evrardjpno news yet16:30
*** daneyon has quit IRC16:30
*** sdake has quit IRC16:31
*** sridhar_ram1 has joined #openstack-meeting-416:31
michaelguginookay, I put my name next to a couple items there16:32
cloudnulli'll tackle glance first.16:32
*** LouisF has joined #openstack-meeting-416:32
cloudnulli think keystone we'll get for free because it uses apache16:33
michaelguginocloudnull: keystone would be useful as other roles depend on it working16:33
michaelguginothat's why I'm trying to hit galera_server and client first16:33
*** sridhar_ram has quit IRC16:33
cloudnullindeed. i think its just a change in the apache layout for multi-distro, so ill bang on that too16:34
michaelguginocloudnull: I have tested the new container_create locally, it's working great.16:34
odyssey4mecloudnull alright, please note which ones you're taking on in the ether pad and add review links once you have them up16:35
cloudnullawesome16:35
*** salv-orlando has joined #openstack-meeting-416:35
odyssey4melol, I see you're aiming right at the bootom section16:35
odyssey4mewho needs interim steps when you can do it all at once :p16:35
spotzhehe16:35
*** shaohe_feng has quit IRC16:36
cloudnullthe bulk of the work will need to be done in the systemd detection and unit files16:36
cloudnullthe infra section is largely done by the packages we install16:36
cloudnullso i'd  like to get a pattern up for us to all agree on and follow in the bulk of the os_* roles16:37
odyssey4meyeah, agreed - it would be nice to have a sample to work from16:37
spotz+116:37
*** lakshmiS has joined #openstack-meeting-416:37
*** bpokorny has joined #openstack-meeting-416:38
*** gangil has quit IRC16:38
odyssey4meif anyone's looking for things to do there are still roles outstanding for the simple application of the pattern to implement different var sets fot different os's16:38
odyssey4methe first set in the work breakdown has around 10 roles left16:38
*** shaohe_feng has joined #openstack-meeting-416:39
stevelleI might pick up a few of those16:39
spotzodyssey4me: I'm good at simple hacking let me go look16:39
odyssey4megreat, thanks - we need to get that done in the next two weeks or so16:40
odyssey4mealright, moving on16:41
odyssey4me#topic Ansible 2.1 Support16:41
*** openstack changes topic to "Ansible 2.1 Support (Meeting topic: OpenStack-Ansible)"16:41
odyssey4mejmccrory are you around?16:41
jmccroryyep16:41
odyssey4mewe discussed at the summit running the rc for 2.1 but maintaining compatibility to ensure that we could fall back if it doesn't release this cycle16:42
odyssey4mewhat do you think the best way to go about doing this would be?16:42
jmccrorycould an experimental 2 job be added for integrated gate?16:42
odyssey4mewe could add a non-voting Ansible 2.1 job for the integrated gate16:42
odyssey4meheh, snap - although I think it better that we do a non voting check so that we see the results for every patch16:43
michaelguginowe also mentioned 2.1 in a venv16:43
jmccroryah even better16:43
evrardjpthat's interesting to have a view of the 2.1 status16:43
odyssey4mewell, for the gate check it's not relevant whether it's in a venv or not16:44
michaelguginowe discussed supporting the venv via the openstack-ansible command, IIRC.  I agree, let's not hold up the gate check for such a reason.16:45
*** uck has quit IRC16:45
odyssey4meI'm trying to find cloudnull's patch to make ansible go into a venv16:45
jmccroryhttps://review.openstack.org/#/c/304840/ - venv patch16:46
odyssey4methanks jmccrory16:46
*** uck has joined #openstack-meeting-416:46
*** shaohe_feng has quit IRC16:46
*** prometheanfire has left #openstack-meeting-416:46
*** shaohe_feng has joined #openstack-meeting-416:47
odyssey4meI think that's a great developer tool, but I am a little concerned about perpetuating that into production.16:47
odyssey4meIt seems like we're moving away from using Ansible in the way Ansible is typically used. That causes confusion.16:48
cloudnullodyssey4me:  ++ it takes away the root ansible command .16:49
*** fsunaval has joined #openstack-meeting-416:49
cloudnullwell it puts it into a venv16:49
cloudnullyou cant really have it both ways16:49
odyssey4meyeah, I'm inclined to say that this is better than our current scenario16:49
cloudnullyou can activate the venv if you want to run stock ansible commands16:50
cloudnullor pass the --adhoc, --galaxy, --playbook (default) if you want to execute using the helper16:50
michaelguginovenv's are not that complicated and are pretty ubiquitous in the Python world.  I think it will be helpful overall.16:51
cloudnull++16:52
evrardjpmichaelgugino venvs already work without the need of this wrapper tool16:52
evrardjpit's just convenient for our dev work16:52
cloudnullwell no. openstack-ansible is how we run all of the commands.16:52
evrardjpI think the principle isn't bad, I just think we need to properly explain what's behind the seen to not make it a obscure way of doing16:52
cloudnullso openstack-ansible needs to be able to execute the venv16:52
palendaeevrardjp: That was my first response too :p16:53
palendaehttps://review.openstack.org/#/c/304840/24/doc/source/developer-docs/scripts.rst talks about that fwiw16:53
cloudnullI did update the docs16:53
michaelguginoI'm not sure I like the idea of bind mounting16:53
palendaeComments on the review could go on the review itself; will help track down discussion around it in the future :)16:54
odyssey4memichaelgugino it's optional16:54
michaelguginoI think that is a fix for dynamic inventory, perhaps we can have dynamic inventory read an env variable if set16:54
odyssey4meyeah, so I think this needs some review attention please16:54
*** paul-carlton2 has joined #openstack-meeting-416:54
odyssey4melet's discuss it all in there16:54
michaelguginok16:54
*** daneyon has joined #openstack-meeting-416:54
cloudnullyea, michaelgugino im not a fan of that but i wanted to provide something for the multi-deployment / config scenario.16:54
evrardjpI don't disagree on this commit, I'm just afraid of splitting the community from ansible's a little more16:54
cloudnullsadly we have a lot of hard coded references to /etc/openstack_deploy16:55
cloudnullif we can fix that ^ i'd be happy to see that code never see the light of day16:55
evrardjpcloudnull maybe this is what should be solved, be more flexible with user changes16:55
*** raj_singh has left #openstack-meeting-416:56
cloudnulli think we could spend an entire cycle on just that.16:56
evrardjp:D16:56
*** csun has joined #openstack-meeting-416:56
cloudnullwhich wouldnt be bad16:56
cloudnullIMHO16:56
*** igordcar1 has quit IRC16:56
*** shaohe_feng has quit IRC16:56
*** igordcard has joined #openstack-meeting-416:57
*** cathy_ has joined #openstack-meeting-416:57
*** nmadhok has joined #openstack-meeting-416:57
palendaeI started down cleaning some of that up in the dynamic_inventory.py file yesterday, but it was making my patch set too big and unfocused16:57
*** shaohe_feng has joined #openstack-meeting-416:57
palendaeWon't completely remove the hard coding, but will clarify things16:57
michaelguginoI don't think that much run-time code is referencing /etc/openstack_deploy, definitely setup scripts, but that's outside the scope of adding an additional env.16:57
palendaeYeah16:58
cloudnulli think dynamic_inventory is the key to releasing our dependency on  a lot of that.16:58
odyssey4meagreed16:58
evrardjpagreed16:58
palendaeIndeed16:59
*** prithiv has quit IRC16:59
evrardjp40 seconds!16:59
odyssey4meshould we isolate some time in the next meeting to discuss and put together some sort of basic idea of the things we want out of the dynamic inventory next version?16:59
spotzhehe16:59
*** fitoduarte has joined #openstack-meeting-416:59
palendaeodyssey4me: I would like to hear specific proposals around changes for multiregion16:59
palendaeI think automagically was going to put something together for that, but not sure17:00
odyssey4meok, we're out of time17:00
palendaeI'll be out so I'll have to catch the notes17:00
*** daneyon has quit IRC17:00
odyssey4methanks all for coming17:00
odyssey4me#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu May  5 17:00:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-05-16.03.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-05-16.03.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-05-16.03.log.html17:00
*** sdake_ has quit IRC17:00
cathy_#startmeeting service_chaining17:00
*** gangil has joined #openstack-meeting-417:00
openstackMeeting started Thu May  5 17:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** evrardjp has left #openstack-meeting-417:00
*** michaelgugino has left #openstack-meeting-417:00
cathy_hi everyone17:00
LouisFhi17:00
yamahatahello17:00
* regXboi wanders in and finds a seat in the corner17:00
igordcardhi17:01
*** Zucan has left #openstack-meeting-417:01
*** doonhammer has joined #openstack-meeting-417:01
*** eil397 has left #openstack-meeting-417:01
*** unicell has joined #openstack-meeting-417:01
*** stevelle has left #openstack-meeting-417:01
*** janki91 has quit IRC17:01
*** davidsha has quit IRC17:01
scsnowhi17:01
*** mbound has quit IRC17:01
fsunavalhi17:02
*** mohankumar__ has joined #openstack-meeting-417:02
*** janki91 has joined #openstack-meeting-417:02
cathy_let's start17:02
*** mbound has joined #openstack-meeting-417:02
mohankumar__Hi cathy_17:03
cathy_#topic Confirm the CI maintenance ownership17:03
*** openstack changes topic to "Confirm the CI maintenance ownership (Meeting topic: service_chaining)"17:03
cathy_hi mohankumar__17:03
cathy_In last meeting, this ownership is assigned to you, mohankumar__ . Is this OK with you?17:03
*** pvaneck has joined #openstack-meeting-417:03
mohankumar__Okay cathy_17:03
cathy_mohankumar__: Thank you!17:04
pcarverhi. sorry I'm going to be in  voice meeting simultaneous with this IRC17:04
cathy_#topic Consistent Repository rule for networking-sfc related drivers: Northbound Tacker driver and Southbound ONOS driver, ODL driver, OVD driver17:04
*** openstack changes topic to "Consistent Repository rule for networking-sfc related drivers: Northbound Tacker driver and Southbound ONOS driver, ODL driver, OVD driver (Meeting topic: service_chaining)"17:04
*** javeriak has joined #openstack-meeting-417:05
*** daneyon has joined #openstack-meeting-417:05
*** numans has joined #openstack-meeting-417:06
cathy_I am thinking we should have a consistent rule as to where the SFC driver located.17:06
cathy_Since the SFC driver is a piece connecting networking-sfc with another project, so it could reside in either repo.17:07
*** shaohe_feng has quit IRC17:07
cathy_Currently OVS driver resides in networking-sfc17:07
mohankumar__cathy_:  agree17:07
*** shaohe_feng has joined #openstack-meeting-417:07
yamahataas FYI, networking-odl includes drivers for other services like fwaas, lbaas, l2gw etc.17:08
cathy_yamahata: thanks for the info17:08
LouisFnetworking-onos has a separate repo17:08
mohankumar__Sfc Onos driver code kept n networking-onos17:09
LouisFmohankumar__: correct17:09
*** daneyon_ has joined #openstack-meeting-417:09
LouisFmohankumar__: networking-onos repo also has the ml2 support - right?17:10
mohankumar__LouisF:  yes17:10
doonhammerThe prototype I did for OVN could all live under networking-sfc but I needed some extensions in networking-ovn not part of the OVN/SFC driver but an interface to OVN17:10
cathy_doonhammer: OK, we can discuss the extension for OVN17:11
regXboiso... that doesn't quite make sense - I would argue that networking-sfc should be the API and a reference implementaiton on ovs and let the other projects handle their own thing17:11
doonhammerThe sfc driver model worked very well - but perhaps we need another abstraction for the actual mechanism OVN, ONOS, ODL etc ?17:11
regXboibecause for example, networking-ovn is likely going to split into an ML2 and L3 service drivers17:11
regXboiand having the SFC specific driver code in yet another project could slow velocity17:12
LouisFregXboi: will that work be in separate repo?17:12
doonhammeryes - not sure of the best approach17:12
regXboiI believe that is planned for the networking-ovn repo17:12
*** unicell has quit IRC17:12
regXboiat least for now17:12
*** SimonChung has joined #openstack-meeting-417:12
*** unicell has joined #openstack-meeting-417:12
*** hvprash_ has joined #openstack-meeting-417:12
LouisFregXboi: does having separate repos affect packaging?17:13
vishnoianilregXboi, i agree with your thoughts17:13
regXboifor our operations to date, no17:13
regXboibut I won't speak for other folks there17:13
*** zenoway has quit IRC17:13
cathy_I think probably the rule is that the repo team for the driver should be responsible for making sure to update the driver accordingly if there is any new update in either repo17:13
*** daneyon has quit IRC17:13
cathy_For example, if there is a change in networking-sfc, then networking-sfc team will update the OVS driver if needed, but ODL team will be responsible for updating the SFC driver in ODL accordingly17:15
LouisFcathy_: +117:15
mohankumar__cathy_:  yes +117:15
regXboithat makes sense17:15
yamahatacathy_: that's quite reasonable.17:15
vishnoianilcathy_, yes17:15
*** hvprash_ has quit IRC17:15
*** hvprash has quit IRC17:16
mohankumar__We should document it somewhere , may with the driver owners17:16
* regXboi now surfs OVN IRC meeting in parallel ... moves to multi-tasking mode17:16
cathy_#agreed we agreed on the rule that the repo team for the driver should be responsible for making sure to update the driver accordingly if there is any new update in either repo17:16
cathy_mohankumar__: yes, we should add this in the driver spec17:17
*** shaohe_feng has quit IRC17:17
*** hvprash has joined #openstack-meeting-417:17
yamahataIf major/big change is expected, I expect it will be communicated in advance before merge.17:17
cathy_mohankumar__: could you add this to the ONOS driver spec?17:17
cathy_yamahata: yes, we will always discuss the change in the networking-sfc meeting17:18
mohankumar__Yes cathy_ , will add17:18
cathy_yamahata: could you add this rule to the ODL driver spec?17:18
yamahatavishnoianil: can you do it?17:18
*** zeih has joined #openstack-meeting-417:18
*** shaohe_feng has joined #openstack-meeting-417:19
yamahatacathy_: he seems away. Anyway I'll take care of it somehow.17:19
*** hvprash_ has joined #openstack-meeting-417:19
*** Sukhdev has joined #openstack-meeting-417:20
cathy_#action mohankumar__ will add the driver updating rule to the ONOS sfc driver spec, yamahata will add the driver updating rule to the ODL sfc driver spec17:20
cathy_Let's go to next topic17:20
vishnoianilyamahata, sure17:20
cathy_#topic Requriement for reference Implementation on OVS driver and OVS Agent path for any API extension17:20
*** openstack changes topic to "Requriement for reference Implementation on OVS driver and OVS Agent path for any API extension (Meeting topic: service_chaining)"17:20
*** ddieterly is now known as ddieterly[away]17:21
cathy_We do not want an API extension without corresponding implementation. But I understand that it might take long for the implementation to be completed. And we should not block merge of an API change for a long time.17:22
cathy_Any suggestion on how to resolve this?17:22
*** hvprash has quit IRC17:23
pcarvercathy_: I think we should start with a spec17:23
scsnowI think it's better to add spec and blueprint to pass API change17:23
LouisFcathy_: are you refering to adding say the symmetric attribute?17:23
cathy_LouisF: yes17:23
fsunavalor l2 option for that matter ?17:23
cathy_pcarver: Yes, spec and BP are fine17:23
*** thorst has quit IRC17:23
pcarverIf we discuss and merge a spec for a new API extension then we can figure out who's going to add the API and implemetation code17:23
igordcardcathy_: but is that an API change?17:23
*** thorst has joined #openstack-meeting-417:24
pcarverThe change to the API code and dataplane implementation should be close in time, but perhaps don't have to be simultaneous17:24
LouisFigordcard: depends on the definition of an api change17:24
cathy_pcarver: but my concern is that once we approve the spec for the API extension, but no implementation is done17:24
cathy_I mean no reference implementation is done17:24
*** fedruantine has quit IRC17:24
pcarvercathy_: we should try to model after Neutron process17:25
*** regXboi has quit IRC17:25
cathy_pcarver: Yes, could you clarify the process?17:25
pcarvertargetting blueprints but bumping them out if it doesn't look like implemnetation will meet a milestone17:25
cathy_fsunaval: yes, l2/l3 is another extension that is being proposed by people17:25
fsunavalcathy_ : Sometimes we might not be able to do the reference implementation with OVS or it would take a lot more effort with OVS than with OVN (for example)17:25
pcarvercathy_: blueprints are targetted at milestones17:25
*** regXboi has joined #openstack-meeting-417:25
pcarverthey can slip and get bumped out to a later milestone or to a later release17:26
*** jmckind_ has quit IRC17:26
*** mbound has quit IRC17:27
mohankumar__pcarver:  exactly +117:27
*** paul-carlton2 has quit IRC17:27
*** shaohe_feng has quit IRC17:27
*** balajin has left #openstack-meeting-417:28
*** shaohe_feng has joined #openstack-meeting-417:28
*** mbound has joined #openstack-meeting-417:28
*** mbound has quit IRC17:28
cathy_pcarver: yes, I am thinking the same when we merge a spec for a new API extension, we should make sure someone is going to add the API and reference implementation code on the OVS driver path17:28
*** thorst has quit IRC17:28
pcarvercathy_: the spec would be tied to a blueprint I think17:29
cathy_pcarver: what specific mechanism do you mean by "the spec tied to the BP"?17:29
*** hvprash has joined #openstack-meeting-417:30
*** tonytan4ever has quit IRC17:31
*** nikhil has quit IRC17:31
pcarverThe BP usually references a spec review17:31
pcarveras well as implementation reviews17:31
mohankumar__One BP can have multiple spec17:32
pcarverI'm not sure if there's a rule on when a spec can be merged vs when code is merged17:32
*** nikhil has joined #openstack-meeting-417:32
*** hvprash_ has quit IRC17:33
pcarverI think Neutron also maintains different spec directories for each cycle unless that has changed17:34
*** tonytan4ever has joined #openstack-meeting-417:34
pcarverI believe that a spec can be moved out of the Mitaka directory to Newton directory for example17:34
cathy_pcarver: I think what we can do to enforce the reference implementation is to identify the owner of the API spec and related implementation. If an implementation is not in place at the targeted milestone, the spec will be moved out to a later release.17:35
LouisFyes https://github.com/openstack/neutron-specs/tree/master/specs/newton17:35
*** hvprash_ has joined #openstack-meeting-417:36
*** zeih has quit IRC17:37
cathy_LouisF: looks like a spec can be moved from one release to another release, right?17:37
regXboiit not only can, it should17:37
*** shaohe_feng has quit IRC17:37
*** gangil has quit IRC17:38
LouisFcathy_: separate release dirs exist - its up to the team on their usage17:38
LouisFregXboi: +117:38
*** shaohe_feng has joined #openstack-meeting-417:38
*** hvprash has quit IRC17:39
cathy_#agreed to enforce the reference implementation for an API extension, the owner of the API spec and related implementation needs to be identified before the spec can be merged. If the implementation is not in place at the targeted milestone, the spec will be moved to the next release17:40
*** gangil has joined #openstack-meeting-417:41
cathy_#topic Add support for Querying Driver capability for SFC functionality support17:41
*** openstack changes topic to "Add support for Querying Driver capability for SFC functionality support (Meeting topic: service_chaining)"17:41
cathy_This is a good suggestion by Paul Carver. Anyone would like to own this?17:43
scsnowAny details what is that?17:43
LouisFpcarver: can you give an example?17:43
pcarverThis is related to the idea that not all drivers may be able to implement all capabilities of the API17:43
pcarvere.g. symetric reverse flow hashing17:44
regXboiso... isn't this microversioning and GET / ?17:44
pcarverThere ought to be a mechanism for a driver to indicate that it can't provide a capability so that the API can let the client know17:44
*** javeriak_ has joined #openstack-meeting-417:44
pcarverand it would be better to be able to discover capabilities in advance rather than by just trying to make an API call and getting a failure response17:45
cathy_pcarver: 100% agree17:45
LouisFpcarver: does neutron support this currently?17:45
regXboiI repeat... isn't this microversioning and GET / ?17:45
regXboiand IIRC, not yet - I'm looking for the LP bug17:45
pcarverLouisF: I'm not sure in general, but something along this line was discussed specifically around VLAN transparency17:45
igordcarda question, all these capabilities to be queried to the driver - will they be capabilities already standardized inside chain_parameters, or could it be any other "string" passed to chain_parameters?17:46
*** javeriak has quit IRC17:46
regXboiall... see https://bugs.launchpad.net/neutron/+bug/1577410 for the test against Neutron17:46
openstackLaunchpad bug 1577410 in neutron "Neutron needs a test for GET /" [Low,Triaged] - Assigned to Mark T. Voelker (mvoelker)17:46
pcarverigordcard: I think we'd probably need to enumerate somewhere. I don't know if it could be totally open to runtime17:46
igordcardthat would then be queried to the driver (which might my own homebrewed driver)17:47
*** shaohe_feng has quit IRC17:48
*** vishwanathj has joined #openstack-meeting-417:48
scsnowDo we have a list of capabilities, that driver should report?17:49
*** unicell has quit IRC17:49
scsnowPer my understanding that's something different to microversions17:50
*** dshakhray has quit IRC17:50
cathy_regXboi: from reading https://bugs.launchpad.net/neutron/+bug/1577410, it seems the GET is for a specific release version's API capability, not a specific  backend driver capability. My understanding may be wrong.17:51
openstackLaunchpad bug 1577410 in neutron "Neutron needs a test for GET /" [Low,Triaged] - Assigned to Mark T. Voelker (mvoelker)17:51
cathy_scsnow: yes, I think the same17:51
regXboiYes, but I'm asking why that same idea can't be leveraged17:51
*** janki91 has quit IRC17:51
igordcardin my opinion the capabilities reported should be up to what different possible chain_parameters are supported in the API itself17:52
LouisFthere should be a general solution for all apis not just networking-sfc17:52
*** shaohe_feng has joined #openstack-meeting-417:53
cathy_regXboi: Yes, it is similar idea. But we need some ownership to implement this idea (could leverage whatever available in Openstack).17:53
*** sbog has joined #openstack-meeting-417:53
regXboiThere was a design session on the Neutron API in ATX that included microversioning, but I don't remember how it came out...17:54
scsnowI could help with implementation, but currently I don't fully understand the idea17:54
scsnowSo I expect that someone could help with spec17:55
cathy_scsnow: I don't think we will define what API capability a driver should support as long as it supports the basic chain capability17:55
regXboiI agree with LouisF that the solution should be general17:55
cathy_scsnow: sure, I can hep you with the spec.17:56
*** prithiv has joined #openstack-meeting-417:56
igordcardcathy_: so is the correlation type mpls part of the basic chain capability?17:56
*** minwang2 has joined #openstack-meeting-417:56
cathy_scsnow: thanks for taking this ownership. You may need to do some investigation on microversioning that regXboi mentioned to see if there is any work we can leverage17:57
cathy_igordcard: no17:57
*** Sukhdev has quit IRC17:57
igordcardok17:57
regXboiare we to the open mike part of the agenda yet?17:57
*** shaohe_feng has quit IRC17:58
scsnowI familiar with nova microversioning and know how to deal with it. So I'll take a look how things are done in neutron.17:58
*** prithiv has quit IRC17:59
cathy_regXboi: not yet. We are going through the topics listed in the meeting agenda of the project wiki page.17:59
*** Sukhdev has joined #openstack-meeting-417:59
*** shaohe_feng has joined #openstack-meeting-417:59
regXboiscsnow: be warned - afaik, it's not *there* yet17:59
cathy_scsnow: great! thanks17:59
scsnowregXboi, yes, I see18:00
cathy_#agreed scsnow will take ownership of the "Add support for Querying Driver capability for SFC functionality support" work. Cathy will help with the spec.18:00
cathy_time us up. We will continue our discussion next week.18:00
cathy_Thanks everyone. bye now18:00
LouisFbye18:00
scsnowbye18:00
igordcardbye18:00
mohankumar__Bye18:00
yamahatabye18:01
doonhammerbye18:01
cathy_#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Thu May  5 18:01:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-05-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-05-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-05-17.00.log.html18:01
*** fsunaval has quit IRC18:01
*** cathy_ has quit IRC18:01
*** regXboi has left #openstack-meeting-418:01
*** Jeffrey4l has quit IRC18:01
*** antonyfm has quit IRC18:03
*** thorst_ has joined #openstack-meeting-418:04
*** vishnoianil has quit IRC18:05
*** shaohe_feng has quit IRC18:08
*** coolsvap has quit IRC18:08
*** jmckind has joined #openstack-meeting-418:09
*** shaohe_feng has joined #openstack-meeting-418:09
*** salv-orlando has quit IRC18:11
*** Sukhdev has quit IRC18:12
*** Sukhdev has joined #openstack-meeting-418:12
*** gangil has quit IRC18:13
*** csun has left #openstack-meeting-418:15
*** zenoway has joined #openstack-meeting-418:17
*** ddieterly[away] is now known as ddieterly18:18
*** shaohe_feng has quit IRC18:18
*** jmccrory_ has quit IRC18:19
*** shaohe_feng has joined #openstack-meeting-418:19
*** antonyfm has joined #openstack-meeting-418:19
*** sridhar_ram1 is now known as sridhar_ram18:20
*** zenoway has quit IRC18:21
*** unicell has joined #openstack-meeting-418:22
*** gangil has joined #openstack-meeting-418:23
*** irenab has joined #openstack-meeting-418:23
*** unicell has quit IRC18:23
*** unicell1 has joined #openstack-meeting-418:23
*** ddieterly is now known as ddieterly[away]18:23
*** gangil has quit IRC18:28
*** shaohe_feng has quit IRC18:29
*** shaohe_feng has joined #openstack-meeting-418:29
*** ninag has quit IRC18:30
*** ninag has joined #openstack-meeting-418:30
*** sambetts is now known as sambetts|afk18:31
*** qwebirc28577 has quit IRC18:31
*** ninag_ has joined #openstack-meeting-418:32
*** ninag_ has quit IRC18:32
*** ninag_ has joined #openstack-meeting-418:33
*** Sukhdev has quit IRC18:34
*** ninag has quit IRC18:35
*** ninag_ has quit IRC18:38
*** shaohe_feng has quit IRC18:39
*** shaohe_feng has joined #openstack-meeting-418:40
*** ddieterly[away] is now known as ddieterly18:44
*** sdake has joined #openstack-meeting-418:48
*** shaohe_feng has quit IRC18:49
*** shaohe_feng has joined #openstack-meeting-418:49
*** geseib007 has quit IRC18:50
*** ninag has joined #openstack-meeting-418:53
*** sdake_ has joined #openstack-meeting-418:55
*** zenoway has joined #openstack-meeting-418:56
*** ninag has quit IRC18:56
*** sdake has quit IRC18:57
*** pmesserli has quit IRC18:59
*** hdaniel has joined #openstack-meeting-418:59
*** mastermind has joined #openstack-meeting-418:59
*** shaohe_feng has quit IRC18:59
*** piet has quit IRC19:00
*** shaohe_feng has joined #openstack-meeting-419:00
*** zenoway has quit IRC19:01
*** piet has joined #openstack-meeting-419:01
*** pmesserli has joined #openstack-meeting-419:01
*** bpokorny_ has joined #openstack-meeting-419:07
*** bpokorny_ has quit IRC19:08
*** bpokorny_ has joined #openstack-meeting-419:08
*** javeriak_ has quit IRC19:09
*** shaohe_feng has quit IRC19:10
*** bpokorny has quit IRC19:10
*** shaohe_feng has joined #openstack-meeting-419:10
*** piet has quit IRC19:12
*** vishnoianil has joined #openstack-meeting-419:15
*** mastermind has quit IRC19:19
*** zenoway has joined #openstack-meeting-419:20
*** shaohe_feng has quit IRC19:20
*** shaohe_feng has joined #openstack-meeting-419:20
-openstackstatus- NOTICE: Gerrit is restarting to address performance issues related to a suspected memory leak19:21
*** ninag has joined #openstack-meeting-419:29
*** shaohe_feng has quit IRC19:30
*** zeih has joined #openstack-meeting-419:30
*** shaohe_feng has joined #openstack-meeting-419:31
*** ninag has quit IRC19:36
*** ninag has joined #openstack-meeting-419:37
*** shaohe_feng has quit IRC19:40
*** shaohe_feng has joined #openstack-meeting-419:42
*** blogan is now known as trollgan19:43
*** antonyfm has quit IRC19:43
*** trollgan is now known as blogan19:43
*** avarner has joined #openstack-meeting-419:44
*** antonyfm has joined #openstack-meeting-419:44
*** avarner is now known as MistySkies19:45
*** MistySkies has left #openstack-meeting-419:45
*** shaohe_feng has quit IRC19:51
*** shaohe_feng has joined #openstack-meeting-419:52
*** zeih has quit IRC19:56
*** piet has joined #openstack-meeting-419:57
*** piet has quit IRC19:57
*** antonyfm has quit IRC19:58
*** gangil has joined #openstack-meeting-420:00
*** shaohe_feng has quit IRC20:01
*** shaohe_feng has joined #openstack-meeting-420:02
*** bpokorny_ has quit IRC20:02
*** bpokorny has joined #openstack-meeting-420:03
*** uck has quit IRC20:06
*** Sukhdev has joined #openstack-meeting-420:06
*** antonyfm has joined #openstack-meeting-420:09
*** shaohe_feng has quit IRC20:11
*** shaohe_feng has joined #openstack-meeting-420:12
*** mohankumar__ has quit IRC20:12
*** piet has joined #openstack-meeting-420:13
*** alex_xu has quit IRC20:18
*** shaohe_feng has quit IRC20:21
*** shaohe_feng has joined #openstack-meeting-420:22
*** alex_xu has joined #openstack-meeting-420:22
*** mrittika has joined #openstack-meeting-420:22
*** nmadhok has quit IRC20:28
*** banix has quit IRC20:28
-openstackstatus- NOTICE: Gerrit is restarting to revert incorrect changes to test result displays20:29
*** tonytan4ever has quit IRC20:31
*** shaohe_feng has quit IRC20:32
*** tonytan4ever has joined #openstack-meeting-420:32
*** shaohe_feng has joined #openstack-meeting-420:33
*** cdelatte has quit IRC20:34
*** sdake has joined #openstack-meeting-420:35
*** numans has quit IRC20:36
*** sdake_ has quit IRC20:36
*** sdague has quit IRC20:37
*** antonyfm has quit IRC20:39
*** DevonBoatwright has joined #openstack-meeting-420:41
*** DevonBoatwright has left #openstack-meeting-420:41
*** shaohe_feng has quit IRC20:42
*** shaohe_feng has joined #openstack-meeting-420:42
*** thorst_ has quit IRC20:46
*** piet has quit IRC20:46
*** daneyon_ has quit IRC20:47
*** amit213 has joined #openstack-meeting-420:50
*** shaohe_feng has quit IRC20:52
*** shaohe_feng has joined #openstack-meeting-420:53
*** thorst_ has joined #openstack-meeting-420:53
*** rbak_ has joined #openstack-meeting-420:57
*** thorst_ has quit IRC20:57
*** numans has joined #openstack-meeting-420:58
*** amotoki has quit IRC20:58
*** gangil has quit IRC20:59
*** piet has joined #openstack-meeting-420:59
*** rbak has quit IRC21:00
*** mbound has joined #openstack-meeting-421:01
*** vhoward has quit IRC21:02
*** gangil has joined #openstack-meeting-421:02
*** shaohe_feng has quit IRC21:02
*** rtheis has quit IRC21:03
*** shaohe_feng has joined #openstack-meeting-421:03
*** fawadkhaliq has joined #openstack-meeting-421:04
*** uck has joined #openstack-meeting-421:06
*** numans has quit IRC21:08
*** raddaoui has joined #openstack-meeting-421:09
*** hdaniel has quit IRC21:10
*** uck has quit IRC21:11
*** thorst_ has joined #openstack-meeting-421:12
*** shaohe_feng has quit IRC21:13
*** yamahata has quit IRC21:13
*** shaohe_feng has joined #openstack-meeting-421:13
*** thorst_ has quit IRC21:17
*** ddieterly is now known as ddieterly[away]21:17
*** yamahata has joined #openstack-meeting-421:19
*** xingchao has joined #openstack-meeting-421:19
*** rbak_ has quit IRC21:23
*** shaohe_feng has quit IRC21:23
*** shaohe_feng has joined #openstack-meeting-421:24
*** mbound has quit IRC21:24
*** rbak_ has joined #openstack-meeting-421:24
*** cdelatte has joined #openstack-meeting-421:24
*** andymaier has joined #openstack-meeting-421:25
*** andymaier has quit IRC21:31
*** lakshmiS has quit IRC21:32
*** shaohe_feng has quit IRC21:33
*** fawadkhaliq has quit IRC21:33
*** shaohe_feng has joined #openstack-meeting-421:34
*** ametts has quit IRC21:34
*** xingchao has quit IRC21:36
*** ddieterly[away] is now known as ddieterly21:41
*** shaohe_feng has quit IRC21:43
*** shaohe_feng has joined #openstack-meeting-421:44
*** unicell1 has quit IRC21:48
*** cwolferh has quit IRC21:48
*** sdake has quit IRC21:50
*** piet has quit IRC21:50
*** sdake has joined #openstack-meeting-421:51
*** shaohe_feng has quit IRC21:54
*** shaohe_feng has joined #openstack-meeting-421:55
*** woodard has quit IRC21:56
*** sdake has quit IRC21:56
*** woodard has joined #openstack-meeting-421:56
*** bobh has quit IRC21:58
*** gangil has quit IRC22:00
*** spzala has quit IRC22:04
*** shaohe_feng has quit IRC22:04
*** spzala has joined #openstack-meeting-422:04
*** shaohe_feng has joined #openstack-meeting-422:04
*** ninag has quit IRC22:05
*** cwolferh has joined #openstack-meeting-422:06
*** ninag has joined #openstack-meeting-422:06
*** Sukhdev has quit IRC22:08
*** scsnow_ has joined #openstack-meeting-422:09
*** spzala has quit IRC22:09
*** hdaniel has joined #openstack-meeting-422:10
*** scsnow has quit IRC22:10
*** ninag has quit IRC22:10
*** gangil has joined #openstack-meeting-422:11
*** pvaneck has quit IRC22:11
*** Sukhdev has joined #openstack-meeting-422:11
*** unicell has joined #openstack-meeting-422:12
*** nmadhok has joined #openstack-meeting-422:12
*** sigmavirus24 is now known as sigmavirus24_awa22:14
*** shaohe_feng has quit IRC22:14
*** shaohe_feng has joined #openstack-meeting-422:14
*** yamamoto has joined #openstack-meeting-422:15
*** mageshgv has quit IRC22:15
*** galstrom is now known as galstrom_zzz22:20
*** banix has joined #openstack-meeting-422:20
*** cdelatte has quit IRC22:22
*** Sukhdev has quit IRC22:24
*** shaohe_feng has quit IRC22:24
*** shaohe_feng has joined #openstack-meeting-422:25
*** hdaniel has quit IRC22:28
*** mrittika has quit IRC22:29
*** yamamoto has quit IRC22:31
*** Sukhdev has joined #openstack-meeting-422:33
*** ninag has joined #openstack-meeting-422:35
*** shaohe_feng has quit IRC22:35
*** shaohe_feng has joined #openstack-meeting-422:35
*** yamamoto has joined #openstack-meeting-422:36
*** yamamoto has quit IRC22:36
*** yamamoto has joined #openstack-meeting-422:37
*** yamamoto has quit IRC22:37
*** yamamoto has joined #openstack-meeting-422:37
*** nmadhok has quit IRC22:39
*** ninag has quit IRC22:39
*** nmadhok has joined #openstack-meeting-422:40
*** daneyon has joined #openstack-meeting-422:40
*** yamamoto has quit IRC22:42
*** thorst_ has joined #openstack-meeting-422:43
*** shaohe_feng has quit IRC22:45
*** shaohe_feng has joined #openstack-meeting-422:48
*** Sukhdev has quit IRC22:49
*** cdelatte has joined #openstack-meeting-422:51
*** david-lyle has quit IRC22:51
*** thorst_ has quit IRC22:52
*** david-lyle has joined #openstack-meeting-422:53
*** salv-orlando has joined #openstack-meeting-422:53
*** salv-orlando has quit IRC22:54
*** salv-orlando has joined #openstack-meeting-422:54
*** shaohe_feng has quit IRC22:55
*** shaohe_feng has joined #openstack-meeting-422:55
*** zeih has joined #openstack-meeting-422:57
*** david-lyle has quit IRC22:58
*** rbak_ has quit IRC22:59
*** nmadhok has quit IRC22:59
*** nmadhok has joined #openstack-meeting-422:59
*** fitoduarte has quit IRC23:01
*** zeih has quit IRC23:01
*** LouisF has quit IRC23:02
*** shaohe_feng has quit IRC23:05
*** shaohe_feng has joined #openstack-meeting-423:08
*** uck has joined #openstack-meeting-423:08
*** vishnoianil has quit IRC23:08
*** ddieterly has quit IRC23:08
*** zenoway has quit IRC23:09
*** zenoway has joined #openstack-meeting-423:10
*** GB21 has joined #openstack-meeting-423:10
*** daneyon has quit IRC23:11
*** uck has quit IRC23:13
*** spotz is now known as spotz_zzz23:15
*** zenoway has quit IRC23:15
*** shaohe_feng has quit IRC23:16
*** shaohe_feng has joined #openstack-meeting-423:19
*** MarkAtwood has quit IRC23:23
*** pmesserli has quit IRC23:24
*** salv-orlando has quit IRC23:26
*** shaohe_feng has quit IRC23:26
*** shaohe_feng has joined #openstack-meeting-423:26
*** GB21 has quit IRC23:28
*** krotscheck has quit IRC23:31
*** krotscheck has joined #openstack-meeting-423:31
*** GB21 has joined #openstack-meeting-423:32
*** cdelatte has quit IRC23:34
*** shaohe_feng has quit IRC23:36
*** shaohe_feng has joined #openstack-meeting-423:36
*** sridhar_ram has quit IRC23:37
*** klamath has quit IRC23:38
*** shaohe_feng has quit IRC23:46
*** shaohe_feng has joined #openstack-meeting-423:48
*** liqw has quit IRC23:49
*** bobh has joined #openstack-meeting-423:51
*** nmadhok has quit IRC23:52
*** shaohe_feng has quit IRC23:57
*** shaohe_feng has joined #openstack-meeting-423:58
*** woodard has quit IRC23:59

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