Thursday, 2016-06-02

*** sabari has left #openstack-meeting-400:02
*** woodard_ has joined #openstack-meeting-400:10
*** woodard has quit IRC00:10
*** zeih has joined #openstack-meeting-400:11
*** Swami has quit IRC00:11
*** amotoki has joined #openstack-meeting-400:12
*** zeih has quit IRC00:15
*** sdake_ is now known as sdake00:19
*** zenoway has quit IRC00:19
*** fitoduarte has quit IRC00:20
*** stanchan has quit IRC00:30
*** xingchao has quit IRC00:30
*** zenoway has joined #openstack-meeting-400:31
*** amotoki has quit IRC00:32
*** zenoway has quit IRC00:36
*** thorst has joined #openstack-meeting-400:46
*** bpokorny_ has joined #openstack-meeting-400:51
*** bpokorny_ has quit IRC00:54
*** bpokorny has quit IRC00:56
*** bryan_att has quit IRC01:03
*** pvaneck has quit IRC01:04
*** zhurong has joined #openstack-meeting-401:05
*** xingchao has joined #openstack-meeting-401:11
*** amotoki has joined #openstack-meeting-401:15
*** v1k0d3n has quit IRC01:17
*** raddaoui has quit IRC01:17
*** fitoduarte has joined #openstack-meeting-401:20
*** amotoki_ has joined #openstack-meeting-401:24
*** amotoki has quit IRC01:26
*** Niham has joined #openstack-meeting-401:31
*** Niham has quit IRC01:32
*** Niham has joined #openstack-meeting-401:33
*** cwolferh has quit IRC01:33
*** amit213 has joined #openstack-meeting-401:39
*** zeih has joined #openstack-meeting-401:39
*** amit213 has quit IRC01:41
*** zeih has quit IRC01:43
*** amit213 has joined #openstack-meeting-401:44
*** sdake has quit IRC01:49
*** xenolog has quit IRC01:50
*** mattymo has quit IRC01:51
*** elemoine has quit IRC01:51
*** iberezovskiy has quit IRC01:51
*** _degorenko|afk has quit IRC01:51
*** iberezovskiy has joined #openstack-meeting-401:52
*** unicell1 has quit IRC01:53
*** xenolog has joined #openstack-meeting-401:53
*** s3wong has quit IRC01:54
*** degorenko has joined #openstack-meeting-401:55
*** banix has quit IRC01:55
*** elemoine has joined #openstack-meeting-401:56
*** mattymo has joined #openstack-meeting-401:57
*** klamath has quit IRC01:57
*** sacharya has joined #openstack-meeting-401:57
*** klamath has joined #openstack-meeting-401:57
*** vishwanathj has joined #openstack-meeting-402:03
*** zeih has joined #openstack-meeting-402:06
*** banix has joined #openstack-meeting-402:09
*** kylek3h has joined #openstack-meeting-402:09
*** Niham has quit IRC02:10
*** zeih has quit IRC02:11
*** yamahata has quit IRC02:11
*** cwolferh has joined #openstack-meeting-402:13
*** iyamahat has quit IRC02:14
*** sdake has joined #openstack-meeting-402:16
*** kylek3h has quit IRC02:16
*** rtheis_ has quit IRC02:17
*** sdake has quit IRC02:18
*** itisha has quit IRC02:30
*** yujunz has joined #openstack-meeting-402:35
*** galstrom is now known as galstrom_zzz02:38
*** woodard_ has quit IRC02:38
*** rbak has quit IRC02:59
*** rbak has joined #openstack-meeting-402:59
*** vishwanathj has quit IRC03:01
*** cwolferh has quit IRC03:02
*** julim has joined #openstack-meeting-403:05
*** yamamoto_ has joined #openstack-meeting-403:10
*** shaohe_feng has joined #openstack-meeting-403:12
*** cwolferh has joined #openstack-meeting-403:13
*** kylek3h has joined #openstack-meeting-403:13
*** JRobinson__ has quit IRC03:17
*** JRobinson__ has joined #openstack-meeting-403:18
*** shaohe_feng has quit IRC03:21
*** kylek3h has quit IRC03:22
*** shaohe_feng has joined #openstack-meeting-403:24
*** yamahata has joined #openstack-meeting-403:27
*** shaohe_feng has quit IRC03:31
*** shaohe_feng has joined #openstack-meeting-403:32
*** zeih has joined #openstack-meeting-403:35
*** julim has quit IRC03:36
*** zeih has quit IRC03:39
*** shaohe_feng has quit IRC03:42
*** yamamoto_ has quit IRC03:42
*** shaohe_feng has joined #openstack-meeting-403:43
*** yujunz has quit IRC03:46
*** shaohe_feng has quit IRC03:52
*** shaohe_feng has joined #openstack-meeting-403:55
*** thorst has quit IRC03:58
*** thorst has joined #openstack-meeting-403:58
*** zeih has joined #openstack-meeting-404:02
*** shaohe_feng has quit IRC04:02
*** shaohe_feng has joined #openstack-meeting-404:03
*** zhurong has quit IRC04:03
*** zhurong has joined #openstack-meeting-404:04
*** cwolferh has quit IRC04:06
*** zeih has quit IRC04:06
*** thorst has quit IRC04:07
*** Niham has joined #openstack-meeting-404:09
*** Niham has quit IRC04:10
*** Niham has joined #openstack-meeting-404:11
*** shaohe_feng has quit IRC04:12
*** shaohe_feng has joined #openstack-meeting-404:13
*** banix has quit IRC04:17
*** kylek3h has joined #openstack-meeting-404:20
*** shaohe_feng has quit IRC04:23
*** shaohe_feng has joined #openstack-meeting-404:23
*** erikmwilson has quit IRC04:24
*** xiaohhui has quit IRC04:24
*** irenab has quit IRC04:24
*** erikmwilson has joined #openstack-meeting-404:25
*** xiaohhui has joined #openstack-meeting-404:25
*** kylek3h has quit IRC04:27
*** yamamoto_ has joined #openstack-meeting-404:29
*** lipt has joined #openstack-meeting-404:29
*** xingchao has quit IRC04:31
*** shaohe_feng has quit IRC04:33
*** shaohe_feng has joined #openstack-meeting-404:34
*** dave-mccowan has quit IRC04:36
*** shaohe_feng has quit IRC04:43
*** shaohe_feng has joined #openstack-meeting-404:44
*** shaohe_feng has quit IRC04:53
*** shaohe_feng has joined #openstack-meeting-404:56
*** sacharya has quit IRC04:57
*** Niham has quit IRC04:57
*** iyamahat has joined #openstack-meeting-404:59
*** shaohe_feng has quit IRC05:04
*** thorst has joined #openstack-meeting-405:05
*** unicell has joined #openstack-meeting-405:05
*** Niham has joined #openstack-meeting-405:06
*** shaohe_feng has joined #openstack-meeting-405:06
*** unicell has quit IRC05:09
*** unicell has joined #openstack-meeting-405:10
*** thorst has quit IRC05:12
*** shaohe_feng has quit IRC05:14
*** shaohe_feng has joined #openstack-meeting-405:14
*** unicell has quit IRC05:15
*** anilvenkata has joined #openstack-meeting-405:17
*** amotoki_ is now known as amotoki05:19
*** unicell has joined #openstack-meeting-405:24
*** shaohe_feng has quit IRC05:24
*** kylek3h has joined #openstack-meeting-405:25
*** shaohe_feng has joined #openstack-meeting-405:25
*** hdaniel has joined #openstack-meeting-405:30
*** zeih has joined #openstack-meeting-405:30
*** kylek3h has quit IRC05:31
*** xingchao has joined #openstack-meeting-405:31
*** shaohe_feng has quit IRC05:34
*** zeih has quit IRC05:35
*** shaohe_feng has joined #openstack-meeting-405:35
*** xingchao has quit IRC05:36
*** tfukushima has joined #openstack-meeting-405:41
*** tfukushima has quit IRC05:41
*** xingchao has joined #openstack-meeting-405:41
*** tfukushima has joined #openstack-meeting-405:41
*** GB21 has joined #openstack-meeting-405:42
*** delatte has quit IRC05:44
*** shaohe_feng has quit IRC05:45
*** shaohe_feng has joined #openstack-meeting-405:45
*** Niham has quit IRC05:46
*** unicell has quit IRC05:53
*** unicell1 has joined #openstack-meeting-405:53
*** shaohe_feng has quit IRC05:55
*** numans has joined #openstack-meeting-405:55
*** sacharya has joined #openstack-meeting-405:57
*** zeih has joined #openstack-meeting-405:57
*** shaohe_feng has joined #openstack-meeting-405:58
*** xingchao has quit IRC06:01
*** zeih has quit IRC06:02
*** GB21 has quit IRC06:02
*** sacharya has quit IRC06:02
*** cdelatte has joined #openstack-meeting-406:03
*** xingchao has joined #openstack-meeting-406:04
*** unicell has joined #openstack-meeting-406:05
*** shaohe_feng has quit IRC06:05
*** unicell1 has quit IRC06:06
*** shaohe_feng has joined #openstack-meeting-406:06
*** cwolferh has joined #openstack-meeting-406:07
*** vishnoianil has quit IRC06:10
*** thorst has joined #openstack-meeting-406:10
*** iyamahat has quit IRC06:14
*** GB21 has joined #openstack-meeting-406:15
*** shaohe_feng has quit IRC06:15
*** zhurong has quit IRC06:16
*** shaohe_feng has joined #openstack-meeting-406:16
*** thorst has quit IRC06:17
*** zhurong has joined #openstack-meeting-406:19
*** hdaniel has quit IRC06:22
*** unicell1 has joined #openstack-meeting-406:24
*** unicell has quit IRC06:25
*** shaohe_feng has quit IRC06:26
*** shaohe_feng has joined #openstack-meeting-406:26
*** zenoway has joined #openstack-meeting-406:27
*** kylek3h has joined #openstack-meeting-406:29
*** mandre has left #openstack-meeting-406:29
*** shaohe_feng has quit IRC06:36
*** shaohe_feng has joined #openstack-meeting-406:37
*** kylek3h has quit IRC06:37
*** vtech has quit IRC06:41
*** numans has quit IRC06:44
*** coolsvap_ has joined #openstack-meeting-406:44
*** shaohe_feng has quit IRC06:46
*** nkrinner_afk is now known as nkrinner06:46
*** shaohe_feng has joined #openstack-meeting-406:46
*** Niham has joined #openstack-meeting-406:51
*** numans has joined #openstack-meeting-406:52
*** zenoway has quit IRC06:56
*** shaohe_feng has quit IRC06:56
*** Niham has quit IRC06:57
*** zenoway has joined #openstack-meeting-406:57
*** sdake has joined #openstack-meeting-406:57
*** shaohe_feng has joined #openstack-meeting-406:57
*** zenoway has quit IRC07:01
*** zenoway has joined #openstack-meeting-407:04
*** vtech has joined #openstack-meeting-407:05
*** seanmurphy has joined #openstack-meeting-407:06
*** seanmurphy has quit IRC07:06
*** shaohe_feng has quit IRC07:07
*** shaohe_feng has joined #openstack-meeting-407:07
*** hdaniel has joined #openstack-meeting-407:11
*** coolsvap_ has quit IRC07:13
*** thorst has joined #openstack-meeting-407:15
*** vishwanathj has joined #openstack-meeting-407:15
*** coolsvap_ has joined #openstack-meeting-407:15
*** vishwana_ has joined #openstack-meeting-407:15
*** shaohe_feng has quit IRC07:17
*** shaohe_feng has joined #openstack-meeting-407:18
*** vishwanathj has quit IRC07:19
*** zenoway has quit IRC07:21
*** zenoway has joined #openstack-meeting-407:22
*** thorst has quit IRC07:22
*** paul-carlton2 has joined #openstack-meeting-407:22
*** zenoway has quit IRC07:23
*** zenoway has joined #openstack-meeting-407:23
*** JRobinson__ has quit IRC07:25
*** nkrinner has quit IRC07:25
*** vishwana_ is now known as vishwanathj07:26
*** nkrinner has joined #openstack-meeting-407:27
*** jichen has joined #openstack-meeting-407:27
*** shaohe_feng has quit IRC07:27
*** shaohe_feng has joined #openstack-meeting-407:27
*** vishwanathj has quit IRC07:34
*** kylek3h has joined #openstack-meeting-407:34
*** zeih has joined #openstack-meeting-407:35
*** GB21 has quit IRC07:36
*** shaohe_feng has quit IRC07:37
*** shaohe_feng has joined #openstack-meeting-407:38
*** sdake has quit IRC07:39
*** danpawlik has joined #openstack-meeting-407:39
*** lipt has quit IRC07:41
*** kylek3h has quit IRC07:42
*** lipt has joined #openstack-meeting-407:46
*** lipt has quit IRC07:46
*** shaohe_feng has quit IRC07:48
*** shaohe_feng has joined #openstack-meeting-407:49
*** lipt has joined #openstack-meeting-407:51
*** lipt has quit IRC07:51
*** lipt has joined #openstack-meeting-407:51
*** lipt has quit IRC07:51
*** lipt has joined #openstack-meeting-407:56
*** lipt has quit IRC07:56
*** shaohe_feng has quit IRC07:58
*** shaohe_feng has joined #openstack-meeting-407:59
*** sacharya has joined #openstack-meeting-407:59
*** matrohon has joined #openstack-meeting-407:59
*** coolsvap_ has quit IRC07:59
*** zeih has quit IRC08:01
*** GB21 has joined #openstack-meeting-408:03
*** sacharya has quit IRC08:03
*** lipt has joined #openstack-meeting-408:04
*** lipt has quit IRC08:04
*** paul-carlton2 has quit IRC08:05
*** mbound has joined #openstack-meeting-408:08
*** shaohe_feng has quit IRC08:08
*** shaohe_feng has joined #openstack-meeting-408:09
*** vishwanathj has joined #openstack-meeting-408:14
*** lipt has joined #openstack-meeting-408:15
*** lipt has quit IRC08:15
*** shaohe_feng has quit IRC08:18
*** paul-carlton2 has joined #openstack-meeting-408:18
*** shaohe_feng has joined #openstack-meeting-408:19
*** Niham has joined #openstack-meeting-408:19
*** chem has joined #openstack-meeting-408:19
*** lipt has joined #openstack-meeting-408:19
*** lipt has quit IRC08:19
*** yujunz has joined #openstack-meeting-408:19
*** thorst has joined #openstack-meeting-408:20
*** lipt has joined #openstack-meeting-408:20
*** lipt has quit IRC08:20
*** lipt has joined #openstack-meeting-408:21
*** lipt has quit IRC08:21
*** ihrachys has joined #openstack-meeting-408:21
*** lipt has joined #openstack-meeting-408:22
*** lipt has quit IRC08:22
*** paul-carlton2 has quit IRC08:24
*** thorst has quit IRC08:27
*** prithiv has joined #openstack-meeting-408:28
*** shaohe_feng has quit IRC08:29
*** markvoelker has quit IRC08:29
*** shaohe_feng has joined #openstack-meeting-408:29
*** markvoelker has joined #openstack-meeting-408:30
*** lipt has joined #openstack-meeting-408:34
*** lipt has quit IRC08:34
*** lipt has joined #openstack-meeting-408:34
*** lipt has quit IRC08:34
*** lipt has joined #openstack-meeting-408:37
*** cznewt has joined #openstack-meeting-408:38
*** fwdit has joined #openstack-meeting-408:39
*** shaohe_feng has quit IRC08:39
*** shaohe_feng has joined #openstack-meeting-408:40
*** kylek3h has joined #openstack-meeting-408:40
*** zeih has joined #openstack-meeting-408:40
*** lipt has joined #openstack-meeting-408:43
*** lipt has quit IRC08:43
*** lipt has joined #openstack-meeting-408:44
*** lipt has quit IRC08:44
*** lipt has joined #openstack-meeting-408:45
*** lipt has quit IRC08:45
*** eyalb has joined #openstack-meeting-408:46
*** eyalb has quit IRC08:47
*** kylek3h has quit IRC08:47
*** shaohe_feng has quit IRC08:49
*** mbound has quit IRC08:49
*** lipt has joined #openstack-meeting-408:50
*** lipt has quit IRC08:50
*** shaohe_feng has joined #openstack-meeting-408:50
*** lipt has joined #openstack-meeting-408:52
*** lipt has quit IRC08:52
*** zeih has quit IRC08:52
*** lipt has joined #openstack-meeting-408:59
*** lipt has quit IRC08:59
*** shaohe_feng has quit IRC08:59
*** shaohe_feng has joined #openstack-meeting-409:00
*** lipt has joined #openstack-meeting-409:02
*** lipt has quit IRC09:02
*** yujunz has quit IRC09:03
*** lipt has joined #openstack-meeting-409:04
*** lipt has quit IRC09:04
*** irenab has joined #openstack-meeting-409:06
*** cznewt has quit IRC09:08
*** dtardivel has joined #openstack-meeting-409:08
*** lipt has joined #openstack-meeting-409:09
*** lipt has quit IRC09:09
*** cznewt has joined #openstack-meeting-409:09
*** shaohe_feng has quit IRC09:10
*** shaohe_feng has joined #openstack-meeting-409:11
*** hughhalf has quit IRC09:12
*** irenab has quit IRC09:12
*** sdake has joined #openstack-meeting-409:13
*** yamahata has quit IRC09:14
*** cznewt has quit IRC09:18
*** cznewt has joined #openstack-meeting-409:19
*** shaohe_feng has quit IRC09:20
*** shaohe_feng has joined #openstack-meeting-409:21
*** thorst has joined #openstack-meeting-409:25
*** shaohe_feng has quit IRC09:30
*** shaohe_feng has joined #openstack-meeting-409:31
*** thorst has quit IRC09:32
*** sdake has quit IRC09:40
*** shaohe_feng has quit IRC09:40
*** shaohe_feng has joined #openstack-meeting-409:41
*** irenab has joined #openstack-meeting-409:42
*** irenab has quit IRC09:43
*** kylek3h has joined #openstack-meeting-409:44
*** irenab has joined #openstack-meeting-409:47
*** tfukushima has quit IRC09:47
*** hughhalf has joined #openstack-meeting-409:48
*** shaohe_feng has quit IRC09:51
*** shaohe_feng has joined #openstack-meeting-409:51
*** zeih has joined #openstack-meeting-409:51
*** sambetts|afk is now known as sambetts09:51
*** kylek3h has quit IRC09:52
*** irenab has quit IRC09:56
*** zeih has quit IRC09:56
*** vishwanathj has quit IRC09:57
*** cznewt has quit IRC09:58
*** sacharya has joined #openstack-meeting-410:00
*** amotoki has quit IRC10:01
*** shaohe_feng has quit IRC10:01
*** shaohe_feng has joined #openstack-meeting-410:02
*** vtech_ has joined #openstack-meeting-410:02
*** vtech has quit IRC10:02
*** amotoki has joined #openstack-meeting-410:04
*** sacharya has quit IRC10:04
*** chem has quit IRC10:06
*** vishwanathj has joined #openstack-meeting-410:07
*** pbourke_ has quit IRC10:10
*** pbourke_ has joined #openstack-meeting-410:10
*** zhurong has quit IRC10:10
*** shaohe_feng has quit IRC10:11
*** shaohe_feng has joined #openstack-meeting-410:14
*** GB21 has quit IRC10:14
*** GB21 has joined #openstack-meeting-410:16
*** vishwanathj has quit IRC10:21
*** shaohe_feng has quit IRC10:21
*** Niham has quit IRC10:22
*** shaohe_feng has joined #openstack-meeting-410:22
*** Niham has joined #openstack-meeting-410:24
*** thorst has joined #openstack-meeting-410:30
*** shaohe_feng has quit IRC10:32
*** shaohe_feng has joined #openstack-meeting-410:32
*** thorst has quit IRC10:37
*** amotoki has quit IRC10:37
*** vtech_ has quit IRC10:37
*** vtech has joined #openstack-meeting-410:38
*** amotoki has joined #openstack-meeting-410:39
*** shaohe_feng has quit IRC10:42
*** shaohe_feng has joined #openstack-meeting-410:43
*** sdague has joined #openstack-meeting-410:46
*** rtheis has joined #openstack-meeting-410:46
*** kylek3h has joined #openstack-meeting-410:49
*** xingchao has quit IRC10:50
*** shaohe_feng has quit IRC10:52
*** shaohe_feng has joined #openstack-meeting-410:53
*** GB21 has quit IRC10:53
*** mclaren_ has quit IRC10:54
*** kylek3h has quit IRC10:58
*** zeih has joined #openstack-meeting-410:59
*** shaohe_feng has quit IRC11:02
*** shaohe_feng has joined #openstack-meeting-411:03
*** irenab has joined #openstack-meeting-411:05
*** amotoki has quit IRC11:07
*** shaohe_feng has quit IRC11:13
*** shaohe_feng has joined #openstack-meeting-411:13
*** irenab has quit IRC11:14
*** hvprash has joined #openstack-meeting-411:15
*** amotoki has joined #openstack-meeting-411:15
*** hvprash_ has joined #openstack-meeting-411:15
*** yujunz has joined #openstack-meeting-411:20
*** hvprash has quit IRC11:20
*** GB21 has joined #openstack-meeting-411:22
*** yujunz has quit IRC11:23
*** shaohe_feng has quit IRC11:23
*** banix has joined #openstack-meeting-411:24
*** shaohe_feng has joined #openstack-meeting-411:26
*** thorst has joined #openstack-meeting-411:26
*** julim has joined #openstack-meeting-411:31
*** prithiv has quit IRC11:32
*** shaohe_feng has quit IRC11:33
*** shaohe_feng has joined #openstack-meeting-411:34
*** nmadhok has quit IRC11:37
*** banix has quit IRC11:42
*** baoli has joined #openstack-meeting-411:43
*** shaohe_feng has quit IRC11:43
*** baoli has quit IRC11:44
*** baoli has joined #openstack-meeting-411:44
*** shaohe_feng has joined #openstack-meeting-411:44
*** zhurong has joined #openstack-meeting-411:45
*** baoli_ has joined #openstack-meeting-411:46
*** baoli has quit IRC11:49
*** shaohe_feng has quit IRC11:54
*** shaohe_feng has joined #openstack-meeting-411:54
*** yujunz has joined #openstack-meeting-411:56
*** sacharya has joined #openstack-meeting-412:00
*** shaohe_feng has quit IRC12:04
*** sacharya has quit IRC12:05
*** kylek3h has joined #openstack-meeting-412:05
*** shaohe_feng has joined #openstack-meeting-412:05
*** irenab has joined #openstack-meeting-412:07
*** prithiv has joined #openstack-meeting-412:08
*** irenab has quit IRC12:08
*** irenab has joined #openstack-meeting-412:09
*** dtardivel has quit IRC12:10
*** amotoki has quit IRC12:11
*** shaohe_feng has quit IRC12:14
*** shaohe_feng has joined #openstack-meeting-412:15
*** irenab has quit IRC12:17
*** amotoki has joined #openstack-meeting-412:18
*** GB21 has quit IRC12:18
*** amotoki has quit IRC12:18
*** shaohe_feng has quit IRC12:24
*** shaohe_feng has joined #openstack-meeting-412:25
*** dave-mccowan has joined #openstack-meeting-412:28
*** v1k0d3n has joined #openstack-meeting-412:30
*** dshakhray has joined #openstack-meeting-412:31
*** yujunz has quit IRC12:32
*** irenab has joined #openstack-meeting-412:33
*** xingchao has joined #openstack-meeting-412:34
*** woodard has joined #openstack-meeting-412:34
*** shaohe_feng has quit IRC12:35
*** shaohe_feng has joined #openstack-meeting-412:36
*** bobh has joined #openstack-meeting-412:36
*** amotoki has joined #openstack-meeting-412:36
*** irenab has quit IRC12:38
*** julim has quit IRC12:41
*** bobh has quit IRC12:41
*** shaohe_feng has quit IRC12:45
*** Niham has quit IRC12:45
*** shaohe_feng has joined #openstack-meeting-412:46
*** iurygregory has joined #openstack-meeting-412:51
*** amotoki has quit IRC12:53
*** shaohe_feng has quit IRC12:55
*** shaohe_feng has joined #openstack-meeting-412:56
*** yamamoto_ has quit IRC12:58
*** iyamahat has joined #openstack-meeting-412:59
*** vtech has quit IRC13:04
*** stanchan has joined #openstack-meeting-413:04
*** shaohe_feng has quit IRC13:05
*** shaohe_feng has joined #openstack-meeting-413:06
*** nmadhok has joined #openstack-meeting-413:07
*** mbound has joined #openstack-meeting-413:11
*** njohnston is now known as njohnston|afk13:11
*** mbound has quit IRC13:13
*** mbound has joined #openstack-meeting-413:13
*** pmesserli has joined #openstack-meeting-413:13
*** julim has joined #openstack-meeting-413:14
*** klamath has quit IRC13:15
*** klamath has joined #openstack-meeting-413:16
*** shaohe_feng has quit IRC13:16
*** yamahata has joined #openstack-meeting-413:16
*** shaohe_feng has joined #openstack-meeting-413:17
*** stanchan has quit IRC13:22
*** jichen has quit IRC13:22
*** zeih has quit IRC13:22
*** stanchan has joined #openstack-meeting-413:24
*** zxen has joined #openstack-meeting-413:24
*** vtech has joined #openstack-meeting-413:25
*** zxen is now known as wxy113:25
*** woodard has quit IRC13:26
*** shaohe_feng has quit IRC13:26
*** shaohe_feng has joined #openstack-meeting-413:27
*** woodard has joined #openstack-meeting-413:28
*** xingchao has quit IRC13:30
*** xingchao has joined #openstack-meeting-413:32
*** zeih has joined #openstack-meeting-413:34
*** vtech has quit IRC13:34
*** crinkle has quit IRC13:35
*** shaohe_feng has quit IRC13:36
*** crinkle has joined #openstack-meeting-413:36
*** xingchao has quit IRC13:37
*** Niham has joined #openstack-meeting-413:37
*** shaohe_feng has joined #openstack-meeting-413:37
*** Niham has quit IRC13:38
*** rbak has quit IRC13:38
*** vtech has joined #openstack-meeting-413:38
*** hdaniel has quit IRC13:38
*** abhishekk has joined #openstack-meeting-413:39
*** tsymanczyk has joined #openstack-meeting-413:40
*** wxy1 has quit IRC13:41
*** tonytan4ever has joined #openstack-meeting-413:41
*** shaohe_feng has quit IRC13:46
*** shaohe_feng has joined #openstack-meeting-413:47
*** jmckind has joined #openstack-meeting-413:50
*** rbak has joined #openstack-meeting-413:53
*** bunting has joined #openstack-meeting-413:55
*** rromans has joined #openstack-meeting-413:55
*** bpoulos has joined #openstack-meeting-413:56
*** croelandt has joined #openstack-meeting-413:56
*** shaohe_feng has quit IRC13:57
*** mfedosin has joined #openstack-meeting-413:57
*** shaohe_feng has joined #openstack-meeting-413:58
*** spotz_zzz is now known as spotz13:58
*** emagana has joined #openstack-meeting-413:59
*** wxy1 has joined #openstack-meeting-413:59
nikhilCourtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat13:59
*** kairat has joined #openstack-meeting-414:00
nikhil#startmeeting glance14:00
openstackMeeting started Thu Jun  2 14:00:13 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
kairato/14:00
tsymanczyk\o14:00
nikhil#topic roll call14:00
bpouloso/14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
mfedosino/14:00
abhishekko/14:00
*** ddieterly has joined #openstack-meeting-414:00
wxy1o/14:00
nikhilwelcome all14:00
nikhillet's get started14:00
nikhil#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
croelandto/14:00
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
dshakhrayo/14:01
buntingo/14:01
nikhilI have set up a few items on tuesday that struck me worth discussing , earlier in the week14:01
jokke_o/14:01
nikhilbut we can substitute those items for anything more important that comes up14:01
*** sacharya has joined #openstack-meeting-414:01
nikhil#topic Updates14:01
*** openstack changes topic to "Updates (Meeting topic: glance)"14:01
nikhil#info Glare updates ( mfedosin )14:02
mfedosinhey!14:02
mfedosinso, we're testing Glare14:02
mfedosinit seems, like all things are done14:03
* nikhil hears great news, starts dancing14:03
mfedosinand next week we'll start preparing the code for review14:03
mfedosinwe're going to spend 3 days on that14:03
mfedosinwed-fri14:03
*** yujunz has joined #openstack-meeting-414:04
mfedosinso, next Friday you'll be able to start reviewing it14:04
nikhilgreat14:04
mfedosinalso, last week generics types were implemented14:04
* jokke_ orders beer & popcorn. Time to flex the -2 finger :P14:05
mfedosinand you can define dictionary property as Dict + element_type14:05
mfedosinbefore you had to define your own type14:05
mfedosinlike DictOfStrings14:05
*** sacharya has quit IRC14:06
nikhilall this needs good documentation otherwise we will have problem of lack of shared understanding14:07
mfedosinI got several comments on the spec14:07
jokke_mfedosin: so is this now the final experimental API or is this considered as stable?14:07
*** yamamoto has joined #openstack-meeting-414:07
mfedosinjokke_: it will be experimental14:07
*** shaohe_feng has quit IRC14:07
mfedosininitially14:07
jokke_Like Stable candidate :)14:07
mfedosinrc1 if you want :)14:08
*** shaohe_feng has joined #openstack-meeting-414:08
mfedosinafter that we'll start integrating Glare in Murano and Heat14:08
mfedosinand if it requires (I hope not) we'll make changes based on their feedback14:09
mfedosinI thinks that's all Glare updates14:10
nikhilthanks14:10
nikhil#info Nova v1, v2  (mfedosin, sudipto)14:10
*** xingchao has joined #openstack-meeting-414:10
nikhilI guess we are still waiting no reviews14:10
mfedosinI finished porting Xenapi plugin14:10
mfedosinhttps://review.openstack.org/#/c/324536/14:10
mfedosinand yeah - we're waiting for reviews14:11
*** emagana has quit IRC14:11
nikhilok, any blockers?14:12
jokke_mfedosin: that xenapi plugin was the last bit to provide them the functionality, right now it's just matter of reviews and merge?14:12
mfedosinfrankly speaking, we also have hyper-v14:12
mfedosinand for some reason it fails several tests if v2 is enabled14:12
*** emagana has joined #openstack-meeting-414:13
*** bobh has joined #openstack-meeting-414:13
mfedosinI hope I'll fix'em today, based on logs14:13
mfedosinother things work pretty fine14:13
*** kairat_ has joined #openstack-meeting-414:13
nikhilThanks mfedosin14:13
jokke_nnice14:13
nikhilLet's make sure we sync with nova team upcoming monday14:13
*** emagana has quit IRC14:14
mfedosinjokke_: (they did in February)14:14
nikhiltheir target was mid-june and many reviews are ready for review14:14
*** emagana has joined #openstack-meeting-414:14
*** emagana has quit IRC14:14
nikhilmfedosin: great, any more updates?14:15
*** emagana has joined #openstack-meeting-414:15
mfedosinnope :)14:15
nikhilThanks again14:15
nikhil#topic Releases (nikhil)14:15
*** openstack changes topic to "Releases (nikhil) (Meeting topic: glance)"14:15
mfedosinwelcome14:15
nikhilso, newton-1 is released14:15
nikhil#info glance newton-1 https://review.openstack.org/#/c/323533/114:15
nikhil#info I plan to propose a client and store release later this week14:16
nikhilbut release team is reluctant on releasing those in the later half of the week so we cannot expect them to be out until early next.14:16
*** yamamoto has quit IRC14:16
jokke_++14:16
jokke_never good idea to release at Fri14:16
nikhil:)14:17
nikhilnewton-2 has begun14:17
*** wxy1 has quit IRC14:17
nikhilso, let's make sure out important specs, esp. lite-specs are done in this timeframe14:17
*** shaohe_feng has quit IRC14:17
nikhilif something is slow, feel free to flag the author that it is so14:17
*** xingchao has quit IRC14:17
nikhilsame goes for reviews, if there's -1 for long time (>1 week) please feel free to ping the reviewer and move on if no response14:18
nikhilthat's it on releases14:18
nikhil#topic Announcements (nikhil)14:18
*** openstack changes topic to "Announcements (nikhil) (Meeting topic: glance)"14:18
*** shaohe_feng has joined #openstack-meeting-414:18
nikhil#info annoucement/poll for virtual mid: http://lists.openstack.org/pipermail/openstack-dev/2016-May/096180.html14:18
nikhilI got one response back on the email about them attending14:19
*** fwdit has quit IRC14:19
nikhilrest of you please say either +1, 0, -114:19
nikhilby default your vote goes as +114:19
nikhilAlso, note:14:19
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/096175.html14:19
nikhilour soft freeze is due soon14:19
nikhilI've posted comments on the glance-specs indicating to the author about the dates14:20
nikhilif there are new specs and you think authors may be unaware then feel free to add the comment indicating the same14:20
*** banix has joined #openstack-meeting-414:20
nikhilthat's it here14:21
nikhil#topic Lite-specs final discussion for newton (nikhil)14:21
*** openstack changes topic to "Lite-specs final discussion for newton (nikhil) (Meeting topic: glance)"14:21
nikhilSo, i wanted to finalize the process this week14:22
nikhilWe have one lite spec merged14:22
nikhilbut I can move that as required14:22
nikhilI had some feedback from hemanth and jokke_14:23
nikhilbut if there are no serious issues, I can either talk to flaper87 and get this resolved14:23
nikhilif you have opinion please add a comment on https://review.openstack.org/#/c/315339/14:24
nikhilbasically, a few things are important:14:24
*** banix_ has joined #openstack-meeting-414:24
jokke_'m still against of turning the process around in the middle of the cycle14:24
*** yamamoto has joined #openstack-meeting-414:24
nikhil1. we need a way to restrict lite-specs a few weeks before newton-314:24
nikhiljokke_: currently there's no process14:24
nikhiland the email I sent to ML was the indication of process14:25
nikhil(I am sort of disapppointed about all the issues not raised then and delay already)14:25
nikhilSo, this is the last week and I will ninja approach otherwise14:26
nikhilthanks14:26
mfedosinsorry for dumb question... what's the difference between lite-specs and release notes?14:26
nikhilgood stuff for documentation14:26
nikhil(third time, this is being asked)14:27
nikhilmfedosin: refer this for initial feedback http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-05-14.00.log.html#l-4814:27
*** banix has quit IRC14:27
mfedosinit was semi-rhetorical question :)14:27
*** shaohe_feng has quit IRC14:27
*** banix has joined #openstack-meeting-414:27
nikhilmfedosin: then it's not a dumb question in the first place14:28
nikhilmfedosin: if you WANT TO KNOW MORE read up the need for lite-spec here: http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.log.html#l-15514:28
*** shaohe_feng has joined #openstack-meeting-414:28
nikhil#topic Specs14:29
*** openstack changes topic to "Specs (Meeting topic: glance)"14:29
mfedosinnikhil: gotcha thanks14:29
nikhil#info Upgrades & registry14:29
nikhilunfortunately, a lot of this discussion is happening without all stakeholders participating14:29
nikhilagain something I may ninja approve if people give last minute -1s, -2s14:30
nikhilgood place to refer:14:30
*** banix_ has quit IRC14:30
nikhilhttps://review.openstack.org/#/c/299726/14:30
nikhilhttps://review.openstack.org/32271214:30
mfedosinnikhil: but we can't deprecate registry, while glance v1 is still supported14:31
nikhilWe need the right story to guide us to either deprecate the registry or tell us if we can asset tag for rolling upgrade or what more needs done.14:31
nikhilHemanth mentioned he was working on the research -- what other projects are doing in openstack. That may help.14:32
nikhilBut a lot of the upgrade stories are subjective to the deployments, something that I may bring up in the ops sync next week (if that happens).14:32
* jokke_ agrees with flaper87 that us keeping registry and having rolling upgrade has no common factor14:32
nikhiljokke_: then you are welcome to give the detailed feedback on the above review (299726) indicating why. Michal seems to indicate the need for conductor like service or I may have mis-interpret that. Either way, shared understanding should be our goal.14:34
jokke_we need implement any plans for rolling upgrades for API-db communications anyways as that's supported model in v2 and apprently the more used one14:34
nikhilI do not find that as enough indicator to take the decision either way.14:35
*** ajmiller has joined #openstack-meeting-414:35
*** amotoki has joined #openstack-meeting-414:35
nikhilWe need the How-s, Why-s and What-s on upgrades.14:35
nikhil#info glance_store & image_props14:35
nikhil#link https://review.openstack.org/32326014:36
nikhilThere's something holding me back on -2 such proposals... and that is I care about our volumes-stakeholders14:37
nikhilif you represent one of that groups, please provide feedback ASAP,14:37
*** shaohe_feng has quit IRC14:38
nikhilthere's only a little time in newton to accept any more proposals and if they are conceptual changes, there's not enough bandwidth to do the research.14:38
*** banix_ has joined #openstack-meeting-414:38
nikhilI'm assuming there's no feedback here.14:38
*** shaohe_feng has joined #openstack-meeting-414:38
*** ajmiller_ has quit IRC14:38
nikhilmoving on14:38
*** banix has quit IRC14:39
*** banix_ is now known as banix14:39
nikhil#info Race conditions on properties: good-s vs. bad-s14:39
nikhil#link https://review.openstack.org/#/c/315483/14:39
nikhilSO, there are two things in that spec14:39
mfedosindshakhray: it's yours :)14:39
nikhil#1. the scope of transactional semantics are not defined14:39
nikhilthat's the reason why a straight away -1 from Jay14:39
nikhilfor example, the transaction layer won't help with race conditions when:14:40
nikhila) there are 1M PATCH requests14:40
mfedosinwhy?14:40
nikhilb) there are 100K PATCH requests14:40
nikhilc) may be in some cases there are 1k PATCH requests14:40
nikhilthat include C, U & D operations14:41
nikhilthe input for each of these request is consistent14:41
nikhilbut the output will always be variable because the atomiticity is built in the DB layer14:41
nikhiland the transaction layer is merely isolating two separate calls and does not gurantee the sequence of them14:41
nikhilso, we have to use the work 'transaction' carefully14:42
kairatSo14:42
mfedosinnikhil: but do we need this gurantee?14:42
nikhil^14:42
kairatThat's REST)14:42
nikhilword*14:42
mfedosinno, I mean if two users want to update name at one time...14:42
nikhiland pythong14:42
nikhilpython*14:43
mfedosinthey both send request, one updates first, another is second14:43
*** yamamoto has quit IRC14:43
mfedosinthe second user just rewrites first value14:43
nikhilyep, the sequence of those calls is not transactional14:44
*** david-lyle has joined #openstack-meeting-414:44
nikhilthat has more than one element to it 1. eventlet 2. python 3. REST ...14:44
mfedosinnikhil: I think we need to talk more on that matter14:44
jokke_so as long as we don't implement locks and start to be really bitchy about this, we will never get rid of all races14:45
*** devananda has quit IRC14:45
nikhiljokke_: correct14:45
jokke_but what dshakhray and mfedosin are proposing at least limits the scope quite a bit14:45
kairatIt at least guarantees what only changes will be applied to db14:45
kairatand nothing more14:45
jokke_it limits the scope of the races only to the same keys that has been changed in multiple places14:45
mfedosinjokke_: and also optimizes db insertions14:46
nikhilsure, that the point #2. limit the transactional gurantee of that layer14:46
jokke_mfedosin: that's database voodoo for me :P14:46
nikhilLet's not call it transactional layer14:46
jokke_mfedosin: but I do understand the logic of updating only changes, not the whole state+changes when the change started14:46
nikhilbecause there's a lot more to transactions than just preventing isolation from two separate API calls14:47
mfedosinnikhil: how do you prefer to call it?14:47
jokke_Blue14:47
*** cdelatte has quit IRC14:47
jokke_Purple would do as well, but definitely not yellow14:47
nikhilit can be isolation layer or may be something along that lines14:48
mfedosinnikhil: okay, we'll think about it14:48
*** shaohe_feng has quit IRC14:48
nikhilmfedosin: this is my feedback to help prevent -1 from the experts like Jay (who is right on target there)14:48
*** shaohe_feng has joined #openstack-meeting-414:49
*** wxy1 has joined #openstack-meeting-414:49
nikhilalso, I wanted to bring this up as mfedosin mentioned to me that this spec is related to the academic completion for dshakhray14:49
jokke_nikhil: are we talking about the same thing?14:49
nikhilso early feedback to her will only help14:49
jokke_Only comment I see from Jay is just preventing updates during saving14:49
jokke_as alternative14:49
mfedosinJay wants to deprecate any image updates if status is saving14:50
mfedosinI think it's not a good solution14:50
nikhiljokke_ there is some email that mentions about not writing transcations in python14:50
jokke_mfedosin: ++14:50
kairatit is not compatible14:51
nikhilv1 and v2 do not need to be compatible14:51
nikhil(fyi)14:51
jokke_nikhil: ++ that's why it's called Major version change :D14:51
nikhil;)14:52
nikhilanyway, we can continue this in open discussion. but I want to give others a chance to ask questions..14:52
nikhil#topic open discussion14:52
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:52
jokke_mut I still don't think it's a fgood idea14:52
nikhilI never said good or bad about it14:52
nikhil(specifically)14:52
mfedosinthanks for feedback14:52
kairatnikhil, I was not talking about v1 and v214:52
mfedosinDarja will update the spec soon :)14:53
kairatbut14:53
kairatlet's move discussion to spec14:53
kairatHow about expiring old bugs14:53
kairatin glance?14:53
nikhilkairat: yeah, I get it. I (too) mentioned it's not backwards compat.14:53
nikhilkairat: oh heck yes!14:53
nikhillet's get a bug day going ?14:54
mfedosinso, today I mentioned that hyper-v doesn't work with v2... I found the reason14:54
kairatPrevisouslu I periodically reviewed bugs14:54
nikhilJune 13th?14:54
kairatWe can do that14:55
mfedosinin v1 we have purge_props flag, that removes all unspecified properties and it's True by default https://github.com/openstack/nova/blob/master/nova/image/glance.py#L41314:55
*** ajmiller has quit IRC14:55
kairatbut I was talking about solution like this: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.14:55
kairatWDYT?14:55
nikhil#startvote Would you like Glance to have bug day on June 13, 2016? (yes, no, maybe)14:56
openstackBegin voting on: Would you like Glance to have bug day on June 13, 2016? Valid vote options are , yes, no, maybe, .14:56
openstackVote using '#vote OPTION'. Only your last vote counts.14:56
mfedosinbut if we provide properties as empty dict, then this flag is ignored. Hyper-v use this feature (or bug)14:56
nikhil#vote yes14:56
mfedosin#vote yes14:56
bunting#vote yes14:56
kairatJune 13 is holiday in Russia14:56
kairatmfedosin, ^14:56
tsymanczyk#vote yes14:56
*** devananda has joined #openstack-meeting-414:56
kairatOk, will try  also14:57
kairat#vote yes14:57
nikhilWe can try June 13 and 1414:57
jokke_#vote maybe14:57
nikhiland we can let people choose14:57
*** zhurong has quit IRC14:57
mfedosinkairat: ouch14:57
nikhilit's not like people are co-located14:57
*** raddaoui has joined #openstack-meeting-414:57
nikhil#endvote14:57
openstackVoted on "Would you like Glance to have bug day on June 13, 2016?" Results are14:57
openstackmaybe (1): jokke_14:57
openstackyes (5): bunting, mfedosin, nikhil, kairat, tsymanczyk14:57
*** sjmc7 has joined #openstack-meeting-414:58
nikhilkairat: I think that's a good idea in general. I am curious who would like to maintain that process?14:58
*** zeih has quit IRC14:58
*** shaohe_feng has quit IRC14:58
*** shaohe_feng has joined #openstack-meeting-414:58
nikhilkairat: Can we assume you will have b/w to do that over time? or are you suggesting one time thing?14:58
kairatOk, I will try to lead that next week14:58
jokke_perhaps we need liaison or workgroup for that :P14:58
*** yamamoto has joined #openstack-meeting-414:58
*** ajmiller has joined #openstack-meeting-414:59
kairatI suggest to clean it first14:59
nikhilwe've shortage of people already14:59
*** lei-zh has joined #openstack-meeting-414:59
buntingI think on the bug days, its probably worth having a etherpad with priorities14:59
*** TravT has joined #openstack-meeting-414:59
nikhilkairat: To be 'really' honest, what we need a clean up of specs more than of old bugs14:59
*** galstrom_zzz is now known as galstrom14:59
nikhilat least for the next couple of weeks14:59
jokke_nikhil: IIRC the original proposal for nova was including scripting that talks with the LP api and does it, not manual labor14:59
*** yingjun_ has joined #openstack-meeting-415:00
nikhilok15:00
kairatjokke_, yep, that's good option15:00
kairatno manual work15:00
*** njohnston|afk is now known as njohnston15:00
nikhilLet's discuss that a bit more on -glance15:00
*** RickA-HP has joined #openstack-meeting-415:00
nikhilwe're out of time today15:00
kairatOk, thanks15:01
jokke_thanks all15:01
nikhilI'm available to chat on -glance for a bit for any outstanding questions from this meeting15:01
nikhilThanks all.15:01
nikhil#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Jun  2 15:01:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-06-02-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-06-02-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-06-02-14.00.log.html15:01
*** emagana has quit IRC15:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Jun  2 15:01:34 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
TravTo/15:01
*** bunting has left #openstack-meeting-415:01
*** bpoulos has left #openstack-meeting-415:01
david-lyleo/15:01
Kevin_Zheng\o/15:01
sjmc7o/15:01
RickA-HPo/15:02
lei-zho/15:02
TravThow is everybody today?15:02
*** tsymanczyk has left #openstack-meeting-415:02
sjmc7sunny15:02
RickA-HPFine, thanks for joining us from Florida!15:02
TravTsure... i am technically on vacation right now15:03
TravTbut couldn't get the kids moving this morning15:03
*** emagana has joined #openstack-meeting-415:03
TravTso, figured i might as well join the fun here15:03
TravTanyway15:03
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:03
*** stanchan has quit IRC15:03
TravTnot much on the agenda list today15:03
TravT#topic newton-1 milestone15:03
*** openstack changes topic to "newton-1 milestone (Meeting topic: openstack search)"15:03
TravTWe have hit the newton 1 milestone.15:04
TravTi submitted the tag requests for searchlight ui and searchlight last night15:04
TravTDoug approved them through.15:04
*** fitoduarte has quit IRC15:04
*** kairat has left #openstack-meeting-415:04
sjmc7yeah, i got the release email spam15:04
TravTas we had previously discussed, we are targeting 1.0 this time.15:04
TravTseeing how this is actually our 4th release, seems about time15:05
TravTi didn't submit a release request for the client.15:05
TravTthat is release independent anyway15:05
TravTi don't believe there are any huge changes needing to be released15:05
sjmc7nope15:06
TravTfor searchlight UI, it is worth noting that it is not backwards compatible with mitaka horizon15:06
*** basilAB has quit IRC15:06
TravTbut this is due to changes in upstream horizon15:06
sjmc7i think that’s true for most horizon plugins15:06
TravTyeah, i think so15:06
* TravT can hear david-lyle groaning15:06
*** konstantinos has quit IRC15:07
*** masteinhauser has quit IRC15:07
TravTokay, well, milestone 1 is mostly a non-event15:07
TravTjust a marker in time.15:07
*** vdrok-afk has quit IRC15:07
*** zeih has joined #openstack-meeting-415:07
TravTbut it is a good time to talk about where we are in the release15:07
TravT#topic open reviews15:07
*** openstack changes topic to "open reviews (Meeting topic: openstack search)"15:07
*** phil_h has joined #openstack-meeting-415:08
*** konstantinos has joined #openstack-meeting-415:08
*** patrickeast has quit IRC15:08
TravTcoming out of the summit15:08
TravTwe had really established a couple of primary goals15:08
TravT1) production readiness15:08
TravT2) improved notifications (related to above)15:08
*** basilAB has joined #openstack-meeting-415:08
*** shaohe_feng has quit IRC15:08
TravT3) supporting nova fully15:09
*** masteinhauser has joined #openstack-meeting-415:09
Kevin_ZhengCool15:09
*** patrickeast has joined #openstack-meeting-415:09
TravTIn addition, we would like to bring in the pipeline architecture early in the cycle if it is coming in.15:09
*** wxy1 has quit IRC15:09
TravTI think we have made good progress on 1. The zero downtime indexing has gone well. A few more BPs are open15:10
*** vdrok-afk has joined #openstack-meeting-415:10
TravTThe notifications have been improved or are in progress15:10
TravTES 2.x seems to be fully supported now15:11
sjmc7yeah, though still some room to improve15:11
*** zeih has quit IRC15:11
sjmc7yes, i think es2 is fully supported. we’ll try to move the CI jobs to it15:11
TravTYeah, that'll be great15:11
sjmc7and then devstack, though that will be harder15:11
*** shaohe_feng has joined #openstack-meeting-415:11
lei-zhcool, will upgrade my dev environment to use 2.x15:11
RickA-HPDoes Searchlight recommend any version of ES (1.* vs 2.)?15:12
sjmc7RickA-HP: 1.7 for mitaka15:12
sjmc7though we should be compatible with both15:12
sjmc7we haven’t used any 2.x-only features, nor relied on any 1.x ones that have been removed15:12
TravTThe primary reason to recommend 2.x is that ES is trying to push people in that direction15:13
TravTWe don't have a formal statement of ES support though15:13
TravTIt wouldn't hurt to document it.15:14
RickA-HPI'm wondering if I should upgrade my dev env to 2.*, or stay at 1.7 to help verify that 1.7 stays working.15:14
TravTI have both setup15:14
TravTmy devstack is 1.7.something15:14
sjmc7yeah, i use both15:14
RickA-HPDeath by combinatorics!15:14
TravTand my local setup (non devstack) has es 2.x and 1.x.  Just depends on which one I decide to turn on.15:15
TravTI think it would be good to push towards 2.x15:15
TravTmaybe we can even get openstack to agree to a deprecation of 1.x15:15
TravTsjmc7 had sent out an email on that early in newton, with limited response15:15
sjmc7ceilometer team said “give it a go and see what breaks” :)15:16
TravTyeah, we should really push for that devstack change now15:16
TravTso that teams have time to address issues.15:16
*** vhoward has joined #openstack-meeting-415:17
TravTis anybody already signed up to do that?15:17
*** anilvenkata has quit IRC15:18
sjmc7i guess i can give it a go15:18
TravTok, maybe it won't be too hard. just submit the change to the script.15:18
*** shaohe_feng has quit IRC15:19
*** weezS has joined #openstack-meeting-415:19
TravTwe have a few specs to review15:19
TravThttps://review.openstack.org/#/q/project:openstack/searchlight-specs+status:open15:19
*** irenab has joined #openstack-meeting-415:19
TravTKevin_Zheng: I added a comment on the server groups one this morning.15:20
Kevin_ZhengYeah, thanks I just saw it15:21
*** shaohe_feng has joined #openstack-meeting-415:22
Kevin_ZhengWill update tomorrow15:22
TravTsounds good15:22
TravTjust in case you didn't see it before, here is a plugin authoring guide: http://docs.openstack.org/developer/searchlight/authoring-plugins.html15:23
Kevin_ZhengAh, thanks15:23
TravTmight be helpful to you15:23
Kevin_ZhengYes looks really useful15:24
Kevin_ZhengThanks a lot15:24
TravTthank sjmc7 for most of it.15:24
TravThe did a nice job on writing it up15:24
sjmc7aww, shucks15:24
*** croelandt has left #openstack-meeting-415:25
Kevin_ZhengReally cool15:25
TravTlei-zh: looks like you just addressed feedback on the pipeline spec15:25
TravTi probably won't be able to look until next week (still on vacation).15:25
TravTbut if others can please take a look as well15:25
sjmc7i’ll take another look15:26
sjmc7think it’s mostly done15:26
lei-zhyes, I konw it's a difficult one, comments and concerns are welcome15:26
TravTI think we are all still conceptually alligned15:26
TravTand the difficult part will be the code... ;)15:27
lei-zhsure, it requires lots of work : )15:28
TravTlet's plan on doing a formal BP review for priority, etc in a couple weeks.15:29
TravTsee if there are things that need to be bumped out.15:29
*** shaohe_feng has quit IRC15:29
TravTare there any BP's anybody wants to bring up now?15:29
sjmc7don’t think so15:30
*** shaohe_feng has joined #openstack-meeting-415:30
sjmc7most of the high priority ones are either underway or for new plugins that folks are working on15:30
*** zeih has joined #openstack-meeting-415:30
*** iyamahat has quit IRC15:30
TravTok15:31
sjmc7we’re waiting on upstream changes for some stuff15:31
sjmc7like some of the neutron ports, cinder backups15:31
TravTyes, anything we need to / can do to help those along?15:31
*** yamahata has quit IRC15:31
lei-zhis the ironic plugin also waiting for notifications to be implemented15:32
sjmc7i’m still not really sure of the etiquette around asking for changes in other projects15:32
TravTwell, yes and no.15:32
TravTironic "instances" all will be available via nova.15:33
sjmc7i guess the obvious answer is “submit patches” but a lot of the code is pretty opaque to just waltz into15:33
TravTbut i'm wondering if we need to do something to detect the difference between ironic and vm instances and show as a different resource type15:33
sjmc7does nova know?15:34
TravTi don't know?15:34
sjmc7sorry, does nova make that apparently to a user15:34
TravTlei-zh: ironic is working on more notifications15:34
TravThttps://bugs.launchpad.net/searchlight/+bug/152640815:34
openstackLaunchpad bug 1526408 in Ironic "[RFE] Add notification support to ironic" [Wishlist,In progress] - Assigned to Mario Villaplana (mario-villaplana-j)15:34
TravTand at the summit 3 folks from ironic came to our session and told us to comment on the patches15:35
TravTto make sure we get what we need15:35
*** zeih has quit IRC15:35
lei-zhseems it's still under work15:36
TravTif you or anybody knows enough about ironic to comment on their notifications, it wouldn't hurt.15:36
TravTi think the same message we give to all the teams.15:36
TravTplease give out all data you'd want to be indexed via notification15:36
TravTwe don't want to do any callbacks15:37
Kevin_ZhengSure15:37
lei-zhyeah, I'll try to find someone to have a look15:38
TravTlei-zh: thanks!15:38
lei-zhyou are welcome :)15:38
TravTokay, well, is there anything else that people would like to discuss today?15:39
*** shaohe_feng has quit IRC15:39
sjmc7nope15:40
*** shaohe_feng has joined #openstack-meeting-415:40
TravTi assume some of our friends here would like to get to sleep tonight.15:40
TravTthanks everybody!15:40
Kevin_ZhengThanks15:41
lei-zhthanks, bye15:41
TravT#endmeeting15:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:41
openstackMeeting ended Thu Jun  2 15:41:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
*** sjmc7 has left #openstack-meeting-415:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-06-02-15.01.html15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-06-02-15.01.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-06-02-15.01.log.html15:41
*** numans has quit IRC15:41
*** GB21 has joined #openstack-meeting-415:42
*** lei-zh has left #openstack-meeting-415:42
*** RickA-HP has left #openstack-meeting-415:43
*** TravT has quit IRC15:44
*** sacharya has joined #openstack-meeting-415:46
*** sacharya has quit IRC15:46
*** spzala has joined #openstack-meeting-415:48
*** vishnoianil has joined #openstack-meeting-415:48
*** shaohe_feng has quit IRC15:49
*** iyamahat has joined #openstack-meeting-415:50
*** shaohe_feng has joined #openstack-meeting-415:50
*** minwang2 has joined #openstack-meeting-415:51
*** yamahata has joined #openstack-meeting-415:52
*** minwang2 has quit IRC15:53
*** iyamahat has quit IRC15:54
*** cloudnull has joined #openstack-meeting-415:56
*** ddieterly is now known as ddieterly[away]15:57
*** matrohon has quit IRC15:57
*** zeih has joined #openstack-meeting-415:58
*** jmccrory_ has joined #openstack-meeting-415:58
mhaydenmeeting about to start in #openstack-meeting-4: cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, mhayden, scarlisle, luckyinva, ntt, javeriak, automagically, spotz, vdo, jmccrory, alextricity25, jasondotstar,15:59
mhaydenKLevenstein, admin0, michaelgugino, ametts, v1k0d3n, severion, bgmccollum, darrenc, JRobinson__, asettle, colinmcnamara15:59
mhaydenoops, wrong channel15:59
cloudnullha!15:59
cloudnullo/15:59
cloudnull:)15:59
spotzhehehe15:59
spotz\o/15:59
hughsaundersmhayden: better to have the ping in this channel :)15:59
mhayden#startmeeting OpenStack-Ansible15:59
openstackMeeting started Thu Jun  2 15:59:56 2016 UTC and is due to finish in 60 minutes.  The chair is mhayden. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
rromansmhayden: HERE15:59
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:00
openstackThe meeting name has been set to 'openstack_ansible'16:00
*** ametts has joined #openstack-meeting-416:00
*** shaohe_feng has quit IRC16:00
mhayden#topic Rollcall & agenda16:00
*** openstack changes topic to "Rollcall & agenda (Meeting topic: OpenStack-Ansible)"16:00
odyssey4meo/16:00
rromans\o16:00
*** shaohe_feng has joined #openstack-meeting-416:00
spotz\o/16:00
*** asettle has joined #openstack-meeting-416:00
mhaydenin case anyone needs a link, the agenda is here -> https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:00
*** evrardjp has joined #openstack-meeting-416:00
*** automagically has joined #openstack-meeting-416:00
*** messy has joined #openstack-meeting-416:00
automagicallyo/16:00
evrardjpo/16:00
amettso/16:00
keekzo/16:00
antonymo/16:00
mhayden𝘩𝘰𝘸𝘥𝘺16:01
*** stevelle has joined #openstack-meeting-416:01
cloudnullyo16:01
andymccro/16:01
phil_hHello16:01
* mhayden gives it one more minute16:02
*** ddieterly[away] is now known as ddieterly16:02
*** uck has joined #openstack-meeting-416:02
jmccrory_o/16:02
*** zeih has quit IRC16:03
*** fsunaval has joined #openstack-meeting-416:03
mhaydenokay, so let's do the thing :)16:03
mhayden#topic Review action items16:03
*** openstack changes topic to "Review action items (Meeting topic: OpenStack-Ansible)"16:03
asettle\o/16:03
mhayden#link http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-26-16.00.html16:03
*** gregfaust has joined #openstack-meeting-416:03
mhaydenautomagically: you were going to think about potential dates for hosting the midcycle?16:03
mhaydenand odyssey4me was going to talk about possibly hosting at Rackspace's HQ in San Antonio, along with dates16:04
mhaydenso i guess this is a general midcycle discussion here :)16:04
odyssey4memhayden my bad, I haven't managed to do the queries for dates and such16:04
automagicallyYes, we could host 60 from 8/29-31 if thats of interest16:05
*** yujunz has quit IRC16:05
odyssey4meI marked it as an action item for me in the absense of other volunteers - if anyone wants to take over that aciton item I'd be happy to release it16:05
automagicallyI have the space reserved temporarily, and would like to know if we want to use it in the next two weeks16:05
mhaydenodyssey4me: we had the security midcycle here last year and may have it here again -- i can ask someone who is working on that one16:05
odyssey4meautomagically wow, 60 is a lot... we'd likely only need room for 10-20, max 30 at a push16:05
mhaydenautomagically: and yours is in Pennsylvania?16:06
automagicallyYes, downtown Phildelphia in the Comcast HQ16:06
mhayden#info automagically has room for 60 people August 29-31 in Philadelphia at Comcast's HQ16:06
odyssey4meit would be nice to have it hosted somewhere that's not SAT :)16:06
odyssey4mefor a change16:06
mhaydenwe are having some wild weather as of late ...16:06
mhaydenshould we get some Rackspace options as well and decide on this next week?16:07
*** yingjun_ has quit IRC16:07
odyssey4mewell, at the very least each of the core team members and any others who want to attend will need to validate whether they can get budget for a trip16:08
*** yingjun has joined #openstack-meeting-416:08
odyssey4mejmccrory automagically cloudnull d34dh0r53 stevelle mattt hughsaunders andymccr mhayden ^16:08
mhaydenquite true16:08
odyssey4meso we have a proposed date and venue, so now we get to work on figuring out who can make it and whether that'll be suitable16:08
mhaydenso it sounds like two actions: 1) get options on space at Rackspace and 2) determine who could travel to Philadelphia and/or San Antonio16:08
odyssey4meyes16:09
mhayden#action mhayden and odyssey4me to find out about Rackspace hosting options for midcycles16:09
odyssey4meare we happy with a three day format?16:09
cloudnullmhayden automagically: ++16:09
andymccri think 3 days is good.16:09
automagicallyI’m good with 2 days16:09
mhayden#action All community members should determine if they can get budget to travel to San Antonio or Philadelphia16:09
*** iyamahat has joined #openstack-meeting-416:09
automagically3 days rather16:09
d34dh0r53+1 on 3 days16:09
cloudnullI think i can swing a philly trip16:09
mhayden+1 on 316:09
mhaydensounds like we're in agreement on 3 days? any objections?16:09
cloudnull+1 on 3 and !  SAT16:10
odyssey4menope, looks good to me - probably worth noting as an info item16:10
mhayden#agreed OSA midcycle should be 3 days long16:10
*** greg_faust has joined #openstack-meeting-416:10
*** shaohe_feng has quit IRC16:10
mhaydenokay, are we good with this topic for now?16:10
automagicallyAFK for a few16:10
mhaydenautomagically: thanks for checking on space at Comcast! :)16:10
evrardjpthanks indeed16:10
mhaydennext item is andymccr's repository -> https://github.com/andymcc/openstack-ansible-testing-core16:11
mhaydenthe action from last week was to review it and ideally test16:11
*** mohankumar has quit IRC16:11
*** shaohe_feng has joined #openstack-meeting-416:11
*** gregfaust has quit IRC16:11
evrardjpI didn't test it :/16:11
evrardjpI read it16:11
*** greg_faust is now known as gregfaust16:11
mhaydeni've looked over it but haven't tested it quite yet16:11
evrardjplooks a good start16:11
mhayden#link https://github.com/andymcc/openstack-ansible-testing-core16:12
andymccri tested it! :D but evrardjp had some additional ideas to try - would be good to get more feedback and ideas to improve/change/scrap16:12
*** hvprash_ has quit IRC16:12
mhaydenwould someone like to volunteer to give it a test (besides andymccr) :)16:12
stevelleI'm somewhat uncomfortable with the test vars being in a different repo for each role16:12
stevellethat seems like a maintenance headache16:12
odyssey4meI unfortunately haven't had the chance to give it a thorough look through.16:12
*** yingjun has quit IRC16:12
*** hvprash has joined #openstack-meeting-416:12
andymccrstevelle: the vars are the same for each repo - the problem mostly is that we are duplicating the same sets of vars for each repo that uses a set role (e.g. keystone is common, or galera)16:13
odyssey4mestevelle as I understood it from discussions with andymccr the test vars there are just a base which can be overridden by the role tests16:13
evrardjpthis is a first iteration, I guess we could indeed have a more integrated view?16:13
*** breton_ is now known as breton16:13
andymccrbut yeh they can be overridden.16:13
jmccroryi tested the glance role, worked well. just ran into small issue with clone command of test playbooks in tox.ini16:13
stevelleandymccr: my concern is that the test vars are not in the role repo. When the role changes and requires var changes it has an order of operations issue that will cause extra review traffic and challenging coordination of them16:14
odyssey4meso we have the option of doing a full set of transition reviews to switch over to using this method, and trying it out for a while - we can always import the repo later16:14
stevelleI fear the same for the tasks16:14
andymccrstevelle: thats one of the main benefits though - because the vars are specific to one repo16:14
andymccrwhereas before if you changed a keystone var (for example) you would have to go into every other repo and change the var there --> 15 changes16:15
* stevelle doesn't think he is being clear16:15
andymccryou mean, id have to change the test repo before changing keystone in order to pass it?16:16
evrardjpyou want to set vars in the inventory only in this, this way we can override inside the roles?16:16
stevelleandymccr: that is some of the concern yes16:16
automagicallyback16:17
andymccrstevelle: sure i guess its a trade off between that and having to manage 15 repo changes due to 1 change on a common repo.16:17
andymccrbut if there is a good way to get hte best of both! i'd prefer that.16:17
stevellewe already have this coordination issue when we removed db create from the roles into the playbooks, it involves lots of extra steps16:17
automagicallyI read through it and I like it16:17
automagicallyI didn’t think I would, but I do. Nice work andymccr16:17
*** jmckind_ has joined #openstack-meeting-416:17
mhaydenwould anyone be able to volunteer to test on it and help andymccr iterate?16:18
evrardjpfine for me16:18
stevelleIf we can smooth that one point of friction I would be enthusiastic, other than that friction point this is really good.16:18
evrardjplacking time 'though16:18
odyssey4meyeah, I'd ideally like another core at least to spend some quality time testing it out - and as evrardjp has good context with Ansible outside of OSA I think it'd be valuable for him to also test and help iterate16:19
mhaydenshould we get a writeup about this repo along with its purpose out to the ML and ask for volunteers?16:19
mhaydenthat would help me understand the goals16:19
evrardjpyeah sure odyssey4me I'll help, don't worry :D16:19
automagicallyThat would be good. A specific call out of stevelle concerns would help contextualize16:19
asettleHappy to help with the write-up. IF that's what's needed.16:19
*** jmckind has quit IRC16:20
mhaydenasettle: could you and andymccr work on an email to the ML?16:20
asettle\o/ team ginger on the job16:20
* mhayden chuckles16:20
jmccroryi'll be out most of next week, but happy to help test as well16:20
asettleWow I just got massive stink eye from andymccr16:20
andymccrok. will get that done tomorrow16:20
*** shaohe_feng has quit IRC16:20
*** amotoki has quit IRC16:20
automagicallyhaha ‘team ginger'16:20
*** alextricity25 has joined #openstack-meeting-416:20
mhayden#action asettle and andymccr to send out an email to the mailing list about the testing repository16:20
*** paul-carlton2 has joined #openstack-meeting-416:20
mhaydenare we good to move on out of action items?16:20
andymccri think so!16:20
asettleandymccr just wants to run from team ginger16:21
mhaydenasettle requested a little time earlier in the meeting since she needs to leav early, so i'll skip around here a little16:21
mhayden#topic OSA Installation Guide restructure16:21
*** openstack changes topic to "OSA Installation Guide restructure (Meeting topic: OpenStack-Ansible)"16:21
mhaydenasettle: you're up!16:21
asettleThanks mhayden16:21
*** shaohe_feng has joined #openstack-meeting-416:21
asettleHey everybody!16:21
asettleAs some of you may know, we're focusing our efforts after the summit to rework the installation guide16:21
asettleI've proposed a blueprint, and a subsequent spec with detailed information on how we're goin to do this16:21
* mhayden is really pleased about these efforts :)16:21
asettleI"m working alongside Darren Chan, who was at the summit and many of you met. His IA (information architecture) experience is assisting me in coming up with a new ToC16:22
asettleI'd appreciate a community review of the spec: https://review.openstack.org/#/c/323471/16:22
mhayden#link asettle's spec -> https://review.openstack.org/#/c/323471/16:22
asettleWe're looking to clarify a few points to ensure the community is happy with the output16:22
*** amotoki has joined #openstack-meeting-416:22
asettleWe need clarification on is whether we are simply documenting installation for a test environment and production environment16:22
asettleAnd we've had a few conflicting suggestions that we also need to include examples and configs for role based documentation16:23
asettleWe're looking to get this spec approved asap, but we want to ensure everyone is on the same page16:23
asettleIf this makes sense16:23
asettleThe spec is still in WIP stage, but I will be removing that tag shortly and opening it up for full reviews.16:23
asettleI'd like to have this approved within the next two weeks to get started on it16:23
asettleQuestions, comments, concerns?16:23
* asettle drops mic16:23
odyssey4meyeah, all agreeing on the end goal is important16:23
*** david-lyle has quit IRC16:24
mhaydenthanks for doing this -- it should make it easier for new deployers to get through the manual and use opinionated defaults16:24
automagicallyMy commentary about the role docs is just that as we move a lot of config-specific doc out of the main guide, I want to make sure that it doesn’t just get removed, but rather ends up in the role-specific docs16:24
odyssey4methis is going to be quite disruptive and can be easily misunderstood, so I'd like to ensure we're all agreed on the way it'll look at the end16:24
asettleVery much so. I believe we have so far included everyone's thoughts and opinions from the summit, but please speak up if you feel like something else is required or missing16:24
mhaydenchapter four of the install guide currently hurts! :)16:24
automagicallyI’m all for the re-orig16:24
automagicallyre-org, rather16:24
asettleautomagically: yeah absolutely16:24
asettleodyssey4me: yes, definitely.16:24
automagicallyasettle: Great16:25
asettleDoes anyone have any immediate concerns?16:25
mhaydennone here16:25
evrardjpnone, if all the content is maintained16:25
odyssey4meautomagically yeah, I was thinking that step one would quite literally be a lift and shift of chapter 4 into the respective repositories16:25
palendaeI'd just echo automagically, making sure anything about roles is kept somewhere16:25
asettleIf not, please have a read through and comment. IF you'd prefer to talk directly to me, please just email me at alexandra.settle@rackspace.com16:25
evrardjpwhatever the way it is maintained16:25
mhaydensounds good16:25
automagicallyWill take another read through the proposed spec and add additional comments, but so far, I’m very supportive and happy to help however I can16:26
mhaydenokay, going back to discussion topics, we've covered the tests repo and the midcycle planning16:26
mhaydenso we're up to...16:26
asettlepalendae and automagically - to answer that properly, I believe there is a plan for it to be moved into a configuration guide, but that's in the future. In the immediate future moving it to the developer docs16:26
mhayden#topic Astara16:26
odyssey4measettle everyone will need edit rights to see the comments and draft bits in https://docs.google.com/document/d/1WdcA7jIp8w1C52pJu4JmympFe8cOvcxi1I2E19Y6XYE/edit16:26
*** openstack changes topic to "Astara (Meeting topic: OpenStack-Ansible)"16:26
mhaydenphil_h: you're up16:26
mhaydenanything new for this week, phil_h?16:26
asettleodyssey4me: I think it's best that that is just open for review at the moment. Otherwise we'll end up with a thousand different voices on a google doc when we should be concentrating our community efforts on the spec16:26
phil_hyes, we have a blueprint up and a straw man in an etherpad16:26
phil_hhttps://blueprints.launchpad.net/openstack-ansible/+spec/add-support-for-astara16:27
*** sacharya has joined #openstack-meeting-416:27
phil_hhttps://etherpad.openstack.org/p/astara-openstack-ansible16:27
cloudnullNice!16:27
asettleOkay, Alex out - tahnks everyone!16:27
mhaydenthanks, asettle16:27
evrardjpthanks asettle16:27
phil_hthis is for adding a "chapter for astara"16:27
*** Swami has joined #openstack-meeting-416:27
phil_hWe will use PlumGrid as a model16:27
automagicallyCool, thanks for the etherpad and blueprint phil_h16:28
mhaydenwould a deployer need to choose Astara *or* neutron's l3 agent?16:28
cloudnullphil_h: very cool.16:28
phil_hI am hoping that they could use astara for the loadbalancer16:28
phil_hand neutron l3 or astara for everything16:28
mhaydengot it16:28
phil_hWe need some testing on the mixed model16:29
mhaydenphil_h: what help could you use from the OSA community on your BP/etherpad?16:29
phil_hIf everyone can have a look and give us feedback16:29
mhaydenlooks like odyssey4me is already on the case :P16:29
phil_hthanks, I will have the astara folks on this also16:29
mhaydensounds good -- i'd like to compare notes on Astara vs. Octavia for load balancers16:30
cloudnull+1 for the boolean approach. Mixed referrence L3 + Astara doesn't seem like a good idea (if it's even possible).16:30
*** zenoway has quit IRC16:30
*** shaohe_feng has quit IRC16:30
mhayden#action All to review phil_h's etherpad on Astara and provide comments16:30
odyssey4mecloudnull ++ agreed16:31
*** michaelgugino has joined #openstack-meeting-416:31
phil_hThe astara folks prefer the boolean approach16:31
*** nkrinner has quit IRC16:31
odyssey4meCertainly in terms of what we document and recommend it should be a binary approach. If people want to try and mix and match then they're on their own.16:31
mhaydenmixing sounds scary16:31
odyssey4meWe can't afford to stretch the test matrix.16:31
*** shaohe_feng has joined #openstack-meeting-416:31
mhaydenwow, lots of stuff going into the etherpad already16:32
mhaydennice16:32
phil_hThanks everyone16:32
mhaydenanything else on Astara, phil_h ?16:32
phil_hnot right now16:32
*** amotoki has quit IRC16:32
mhayden#link phil_h's etherpad for Astara -> https://etherpad.openstack.org/p/astara-openstack-ansible16:32
mhaydenokay, next up...16:32
*** sdake has joined #openstack-meeting-416:32
mhayden#topic Deprecation of pip_lockdown16:32
*** openstack changes topic to "Deprecation of pip_lockdown (Meeting topic: OpenStack-Ansible)"16:32
mhaydenautomagically: you're up! :)16:33
* automagically scrambles to find the starred review16:33
* mhayden plays jeopardy music16:33
mhayden:)16:33
automagically#link https://review.openstack.org/#/c/313878/16:33
automagicallyThat review is what we got proposed following the last meeting16:34
automagicallyThanks jmccrory for the quick turn-around on it16:34
*** jmckind_ has quit IRC16:34
automagicallyI think we just need to get the feedback from odyssey4me resolved16:34
jmccroryhad some thoughts on where to go forward from there16:34
automagicallycloudnull: You were missing last week and we though you’d probably have some opinions, now is your chance to weigh in16:35
* automagically hands mic to jmccrory 16:35
* cloudnull reading16:35
jmccroryhard set the lockdown var to true in os playbooks, since pip_links are always to go be defined in group vars16:35
*** cwolferh has quit IRC16:35
*** jmckind has joined #openstack-meeting-416:35
jmccroryremove pip_lock_down dependency entirely from IRRs and just add the isolated option to pip_options for developer mode16:36
cloudnullI think https://review.openstack.org/#/c/320216/10/meta/main.yml makes sense if we want to keep the API the same.16:36
automagicallyI’d like to still test the length of pip_links which would allow a deployer to ignore the internal repo16:36
jmccrorythat way it'll avoid any existing lock down for both independent role use or it's they're deployed as part of integrated release16:36
cloudnullIf we're going to change it, keying off of links makes sense16:36
automagicallyI agree entirely with the rest of that jmccrory16:36
*** sdake has quit IRC16:37
*** hvprash has quit IRC16:37
odyssey4mefor the meta, all we need is the role inclusion16:37
cloudnullas long as the links has a value of >=116:37
jmccrorysure length would work then, would be possible for deployment to override and empty it16:37
automagicallyodyssey4me: ++16:37
automagicallyyep jmccrory16:37
odyssey4meit defaults to no lock down, so having the dep on developer mode makes no sense16:37
automagicallyConsensus reached then it seems16:37
automagically:D16:37
cloudnull++ jmccrory typie typie change all the open reviews :)16:38
odyssey4methe only trick here is to cater for automagically's situation where he overrides the links in some builds, so the group_vars are negated16:38
jmccroryyeah, was only in case someone wanted to set developer mode on a single role while doing an OSA deployment. and that's seems to have happened16:38
automagicallyI _do_ appreciate being catered to16:38
mhaydenhah16:38
mhaydenso we're agree on this one? :)16:38
automagicallyIt seems we are16:38
mhaydens/agree/agreed/ :)16:38
cloudnullwe can set that at runtime for a given role16:38
mhaydenwoot16:38
stevelleagreed here16:38
odyssey4mejmccrory in that particular case a deployer has other options to negate the lock down16:38
jmccroryhttps://bugs.launchpad.net/openstack-ansible/+bug/158560416:38
openstackLaunchpad bug 1585604 in openstack-ansible "horizon_developer_mode does not work" [Undecided,New]16:39
* automagically passes mic back to mhayden 16:39
mhaydenautomagically: all good on this topic?16:39
mhaydenwoot16:39
mhaydennext up...16:39
mhayden#topic Support for Xen via libvirt16:39
*** openstack changes topic to "Support for Xen via libvirt (Meeting topic: OpenStack-Ansible)"16:39
mhaydenand antonym is up!16:39
antonymo/16:39
odyssey4mewelcome antonym16:39
*** cwolferh has joined #openstack-meeting-416:39
antonymhow's it going?16:39
antonymwas chatting with major a bit yesterday about looking into libvirt and xen and he suggested we mention it here16:40
mhaydenlet's just say that antonym works on a *very* large OpenStack cloud that happens to run on xen :)16:40
evrardjpgood indeed16:40
antonymwanted to see what the thoughts were on adding it as a supported hypervisor to openstack-ansible16:40
automagicallySeems like something that might be popular16:40
antonymwas probably going to throw together a blueprint if it's something that has interest16:40
mhaydensince it's just another option in libvirt, it could work well16:40
odyssey4meantonym it should be pretty easy I expect, probably not much more than extending https://github.com/openstack/openstack-ansible-os_nova/blob/master/defaults/main.yml#L93-L12616:40
mhaydengate testing could get interesting16:40
*** shaohe_feng has quit IRC16:41
antonymodyssey4me: yeah, i had a proof of concept in december in openstack-ansible that built a vm using libvirt, needed to dig into the networking still16:41
antonymbut i don't think it should be a major effort16:41
evrardjpWill this have a larger impact than nova? like a lots of changed due to specific ovs/cinder/glance way of doing things?16:41
evrardjpjust to be informed how it's planned :D16:41
*** shaohe_feng has joined #openstack-meeting-416:41
odyssey4methere's some work going in to support powervm too which is extending that and may introduce some more patterns which could be useful16:42
antonymi think it aligns to kvm pretty well right now since it's mostly libvirt16:42
antonymthe xen guys have been busy stabilizing it too16:42
evrardjpcool news16:42
mhaydenwould we need a spec for this work?16:43
mhaydeni'm on the fence16:43
automagicallycan’t hurt16:43
antonymanyways just wanted to bring it up, sounds like there is some interest16:43
odyssey4meantonym it would be ideal to have some sort of external CI checks in place to validate that any ongoing work doesn't break xen support, but if that's not possible then it's just going to place more responsibility on anyone using it to test properly before upgrading16:43
mhaydenantonym: want help building a spec + BP?16:43
*** kairat_ has quit IRC16:43
antonymmhayden: yeah, i can try and slap one together16:43
odyssey4meyeah, it would be best to put the thoughts into a spec16:44
mhayden#action antonym to build a blueprint and spec for Xen+libvirt support16:44
*** sdake has joined #openstack-meeting-416:44
mhaydenthanks, antonym16:44
antonymodyssey4me: yeah, i'm kinda new on the CI checks but it's something we should look into as well16:44
odyssey4methe powervm spec will be a good one to model from16:44
*** stanchan has joined #openstack-meeting-416:44
antonymodyssey4me: cool, i'll take a look at it16:44
antonymmhayden: no prob16:44
mhaydenmany thanks to the IBM folks for coming by and proposing good patches and doing reviews! :)16:44
odyssey4me++16:44
evrardjpindeed16:44
*** doonhammer has joined #openstack-meeting-416:44
antonymhopefully 16.04 still has some basic xen support :D16:44
mhaydenantonym: anything else on Xen?16:45
antonymmhayden: nope i'm done :)16:45
mhaydensweet16:45
mhaydenthat wraps up the discussion topics... on to...16:45
*** LouisF has joined #openstack-meeting-416:45
mhayden#topic Release planning and decisions16:45
*** openstack changes topic to "Release planning and decisions (Meeting topic: OpenStack-Ansible)"16:45
mhaydenodyssey4me: you're up!16:45
odyssey4medo we have any blockers for the next tag for Liberty or Mitaka?16:46
* mhayden is not aware of any16:46
* automagically not that I know16:46
odyssey4meas expressed in http://lists.openstack.org/pipermail/openstack-dev/2016-June/096466.html we're waiting for the final kilo-eol tags before we do our own Kilo eol16:47
* mhayden sheds a tear for kilo16:47
odyssey4meI need to request the Newton-1 tags today as well - I'm just trying to finalise a tool to help me simplify my release request process.16:47
*** prithiv has quit IRC16:48
*** flaviodsr has joined #openstack-meeting-416:48
odyssey4meok then16:48
evrardjpgood odyssey4me16:48
stevelledoes it use ansible?16:48
mhaydenit's written in perl16:48
evrardjp:p16:48
odyssey4me#action odyssey4me to request Newton-1 tags, and next tag releases for Liberty & Mitaka16:48
odyssey4mestevelle nope, just python - I'm raging at different opinions about yaml formats16:49
mhaydenwoot16:49
mhaydenanything else on this odyssey4me?16:49
odyssey4mewell, not raging, just trying to make yaml.dump output it the way that the release team wants it16:49
stevelleI know that feel16:49
evrardjp:D16:49
odyssey4meI'll take the problem to the channel. Maybe someone can help.16:49
odyssey4memhayden no, thanks - all done16:50
evrardjpdo you need help?16:50
mhaydenokay, we got asettle's update already, so we're on to blueprints!16:50
mhayden10 minutes left16:50
mhayden#topic Blueprint - Ubuntu 16.04 LTS Support16:50
*** openstack changes topic to "Blueprint - Ubuntu 16.04 LTS Support (Meeting topic: OpenStack-Ansible)"16:50
mhayden#link https://etherpad.openstack.org/p/openstack-ansible-newton-ubuntu16-0416:50
*** sambetts is now known as sambetts|afk16:50
mhaydenlots more strikethroughs there!16:50
stevelleI have the gnocchi role in progress right now16:51
stevellepretty close, might submit a review today16:51
evrardjpmy neutron role needs core reviews16:51
*** shaohe_feng has quit IRC16:51
cloudnullits progressing nicely16:51
cloudnullcent7 support too :)16:51
michaelguginonova seems to be working locally, I basically just copied and pasted the work from neutron16:51
evrardjphttps://review.openstack.org/#/c/322249/16:51
*** julim has quit IRC16:51
*** paul-carlton2 has quit IRC16:52
odyssey4meit looks like we're actually largely ahead of schedule here16:52
mhayden#action Core reviewers can lend a hand on evrardjp's review -> https://review.openstack.org/#/c/322249/16:52
automagicallyodyssey4me: don’t jix it16:52
automagicallyjinx, rather16:52
mhaydenin the interest of time, i'll keep moving16:52
*** shaohe_feng has joined #openstack-meeting-416:52
mhayden#topic Blueprint - Install Documentation Update16:52
odyssey4meall we needed to do for Newton-1 was get the vars split out implemented... but we're quite far down the road of getting Xenial working16:52
*** openstack changes topic to "Blueprint - Install Documentation Update (Meeting topic: OpenStack-Ansible)"16:52
mhaydenactually -- i think asettle covered this well16:52
mhayden#topic Blueprint - Ansible 2.1 Support16:53
*** openstack changes topic to "Blueprint - Ansible 2.1 Support (Meeting topic: OpenStack-Ansible)"16:53
odyssey4meyep, I think we should move to discussion16:53
mhaydenodyssey4me: you wanna open it up?16:53
odyssey4meconsidering we have 5 mins left16:53
mhayden#topic Open Discussion16:53
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack-Ansible)"16:53
michaelguginoI vote 2.1 moves to O cycle16:53
mhaydeni'd like to thank everyone for helping learn the ways of a core reviewer16:53
evrardjpwould be happy to remove all the non 2.1 supported things for now16:53
*** numans has joined #openstack-meeting-416:54
michaelguginonova-lxd driver support will be implemented by my team soon, as soon as I can make them do it16:54
odyssey4memichaelgugino cool :)16:54
evrardjpyeah cool news michaelgugino16:54
odyssey4meFYI to all https://review.openstack.org/#/q/project:openstack-infra/project-config+branch:master+topic:osa-additional-core-teams16:54
odyssey4methere's another one for the swift role, and I can add any more if anyone wants to propose that we should have more role specific cores16:55
*** regXboi has joined #openstack-meeting-416:55
evrardjpif the discussion is still open, please prepare your opinion on this: https://review.openstack.org/#/c/321582/16:55
evrardjpgoal is to simplify tox.ini, ansible.cfg ...16:55
michaelguginoI'll also be working on the Watcher project, which has just made it into the big tent.  I'll be developing small contribs to that codebase, and acting as a liason between this project and that one16:55
*** georgewang has joined #openstack-meeting-416:55
evrardjpnot only for 2.116:55
*** singlethink has joined #openstack-meeting-416:56
michaelguginoThey want to have OSA support for watcher, and I am happy to help them/do it16:56
odyssey4memichaelgugino great, I'm happy that someone is - it looks like an interesting one to perhaps instrument into OSA at some point16:56
evrardjpinteresting project16:56
*** cathy_ has joined #openstack-meeting-416:56
odyssey4meevrardjp I'm not sure that it simplifies anything at all to have the plugins as a role requirement16:57
*** khushbu has joined #openstack-meeting-416:57
*** mohankumar has joined #openstack-meeting-416:57
automagicallyVery cool michaelgugino16:57
michaelguginoI also need to submit some more openvswitch patches for neutron.  Right now, it only supports provider networking AFAIK.  I need to patch the config files to support the bridge mappings16:57
michaelguginobr-int and br-ex, for example.16:58
evrardjpodyssey4me: happy to discuss about your concerns (and everyone's)16:58
*** azbiswas has joined #openstack-meeting-416:58
odyssey4meok, we need to clear the room mhayden16:59
mhaydensounds good16:59
mhaydenthanks, everyone!16:59
evrardjpty everyone16:59
mhayden#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu Jun  2 16:59:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-06-02-15.59.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-06-02-15.59.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-06-02-15.59.log.html16:59
*** hvprash has joined #openstack-meeting-416:59
*** stevelle has left #openstack-meeting-417:00
*** automagically has left #openstack-meeting-417:00
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Jun  2 17:00:22 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
*** evrardjp has left #openstack-meeting-417:00
openstackThe meeting name has been set to 'service_chaining'17:00
cathy_Hi everyone17:00
*** flaviodsr has left #openstack-meeting-417:00
scsnowhi17:00
mohankumarHi cathy17:00
iyamahathello17:00
igordcardhi cathy_17:00
doonhammerHi Cathy17:00
georgewanghi17:00
regXboio/17:00
*** messy has quit IRC17:00
cathy_Let's start with topic #1 listed in the meeting page17:01
cathy_#topic Action status17:01
*** openstack changes topic to "Action status (Meeting topic: service_chaining)"17:01
*** shaohe_feng has quit IRC17:01
cathy_1. use case status17:01
LouisFhi17:01
pcarverhi17:01
*** shaohe_feng has joined #openstack-meeting-417:02
cathy_pcarver: How is it going? Could you write a use case for this feature?17:02
*** unicell1 has quit IRC17:02
doonhammercathy: LouisF helped by posting my use cases - I still cannot get access to tehg wiki - I have raised a case with support.openstack.org - is that the right place?17:02
cathy_doonhammer: ok, thanks.17:03
cathy_LouisF: have you posted the use case?17:03
pcarverI haven't received any actual use cases from the teams that actually use our cloud. I can provide info on what features we have been asked for, but I don't have use cases for the features.17:03
igordcarddoonhammer: can you log-in successfully?17:03
LouisFcathy_: yes17:03
regXboidoonhammer: going to s.o.o should do the trick17:03
cathy_LouisF: cool, could you post the link here?17:04
LouisFhttps://wiki.openstack.org/wiki/Neutron/ServiceChainUseCases17:04
cathy_pcarver: Sure, please provide features. If you can try to get one or two usage scenarios for those features, that will be great17:05
doonhammerLouisF: I had some hyperlinks in the references - problem did not come through with the mail - I can send them to you17:05
cathy_pcarver: you are one of the best person to provide the usage scenarios:-)17:05
*** pvaneck has joined #openstack-meeting-417:05
fsunavalHi17:06
LouisFdoonhammer: ok thanks send them and I will add them17:06
*** michaelgugino has left #openstack-meeting-417:06
*** coolsvap_ has joined #openstack-meeting-417:07
pcarvercathy_: unfortunately I don't actually use our cloud. I coordinate with a bunch of other teams that use it so I'm dependent on them to supply what details they will on what they need. Sometimes they have a tendency to only say what they want without providing details on how they'll use it when they get it.17:07
fsunavaldoonhammer:  I will send you the use case I mentioned.17:07
doonhammerLouisF: thanks17:07
cathy_igordcard: I know there is a use case spec in IETF. Could you "translate" them into detail usage scenarios and post them on the wiki link?17:07
cathy_fsunaval: hi17:07
LouisFfsunaval: you can add it to the wiki17:07
LouisFfsunaval: at https://wiki.openstack.org/wiki/Neutron/ServiceChainUseCases17:07
fsunavalLouisF: Ok. Will do.17:08
cathy_pcarver: Understand. If you can push them to give more details, that will be helpful. Could you continue working on getting details on your use cases?17:08
cathy_fsunaval: thanks!17:08
pcarvercathy_: yes, I'll keep asking17:08
igordcardcathy_: I'll see what I can do - I also have a concrete example of the use case I've posted at the wiki already, so I'll start with that one17:09
cathy_pcarver: thanks!17:09
cathy_igordcard: great. Thanks!17:09
*** s3wong has joined #openstack-meeting-417:09
s3wonghello17:09
cathy_From all those use cases, we can analyze the missing pieces to satisfy the requirements.17:10
cathy_s3wong: hi17:10
*** jmckind has quit IRC17:10
*** coolsvap_ has quit IRC17:11
*** jmckind has joined #openstack-meeting-417:11
cathy_#action pcarver will post the required features on the wiki and will continue working on the usage scenarios17:11
doonhammercathy: I would image we could write simple REST applications that use the networking-sfc to match the use cases/examples?17:11
*** shaohe_feng has quit IRC17:11
*** shaohe_feng has joined #openstack-meeting-417:12
cathy_#action igordcard will try to "translate" the IETF use cases into detail usage scenarios and post them on the wiki link17:12
cathy_#action fsunaval will post a use case17:12
*** pmesserli has quit IRC17:13
cathy_doonhammer: Yes17:13
igordcard#action igordcard will expand SFC Encapsulation/branching use case based on a concrete example17:13
*** spzala has quit IRC17:13
cathy_doonhammer: or you can use the Horizon GUI17:14
cathy_#topic FC priority status17:15
*** openstack changes topic to "FC priority status (Meeting topic: service_chaining)"17:15
cathy_mohankumar: you are working on this, right?17:15
mohankumarcathy, completed code changes and have to add/cover required UT testcases, Maybe tmrw will push and open code for review17:15
doonhammercathy: networking-sfc has horizon support now ?17:15
scsnowmohankumar, did you implement support in ovs driver?17:16
mohankumar@pavel, i've done some code changes in ovs agent as well , please check and feel free to append patch on top17:16
*** pmesserli has joined #openstack-meeting-417:16
cathy_mohankumar: Cool. Thank you very much for your great contribution to this project!17:16
mohankumarthanks cathy_17:16
cathy_doonhammer: yes, mohankumar designed and implemented that17:16
*** Srilatha_ has joined #openstack-meeting-417:16
*** tonytan4ever has quit IRC17:17
doonhammermohankumar: way cool17:17
igordcardcathy_: doonhammer: are you talking about horizon too, or only fc priority?17:18
doonhammerigordcard: horizon17:18
*** dshakhray has quit IRC17:19
igordcarddoonhammer: okay17:19
cathy_igordcard: we are talking about FC priority. And provide info to doonhammer that networking-sfc already has Horizon support17:19
igordcardcathy_: where?17:19
mohankumar doonhammer: yes , i ve developed horizon code  ,  but the current code having some dependency with horizon main code tree17:19
cathy_mohankumar: could you provide the link?17:19
igordcardcathy_: mohankumar : I see a work-in-progress patch, but I don't see horizon code in tree yet..17:20
mohankumarhttps://review.openstack.org/#/c/258430/17:20
scsnowcan someone clarify what is sf_paremeters in port pairs? I see, that currently it supports correlation parameter, but it's not handled in ovs driver.17:20
scsnowthis parameter is not described in spec either17:21
cathy_scsnow: it should have been described in the API spec.17:21
*** shaohe_feng has quit IRC17:22
cathy_scsnow: this param allows the specification of SF associated attributes17:22
igordcardscsnow: perhaps to describe attributes about individual functions, like if one is notn sfc-aware17:22
igordcardis this a correct interpretation cathy_ ?17:22
mohankumarigordcard ,  this code still need some changes to implement  sfc as plugin17:23
*** shaohe_feng has joined #openstack-meeting-417:23
cathy_For example, the user can specify whether a SF is sfc-encap-aware or not17:23
cathy_igordcard: yes17:23
LouisFscsnow: sf-parameters are intended to allow various parameters be attached to a SF17:24
igordcardmohankumar: alright, I'm interested in trying it when it's ready, I'll follow the updates17:24
cathy_another example is to specify the weight of a SF when there are multiple functional-like SFs in a group17:24
scsnowcathy_, LouisF, igordcard thanks17:24
cathy_currently we only has definition of whether a SF is SFC-aware or not. In the future we can add the "weight" and more other attributes to support richer SFC features17:25
cathy_let's go to next status item17:26
cathy_Move the Path ID generation17:26
cathy_Anyone working on this?17:26
LouisFcathy_: I have added a bug for this17:27
s3wongcathy_: doing #topic?17:27
igordcardmy question too, if not I can volunteer17:27
georgewangI can contribute to the work of path id generation17:27
LouisFhttps://bugs.launchpad.net/networking-sfc/+bug/158846017:27
openstackLaunchpad bug 1588460 in networking-sfc "Move path-id generation from ovs driver to plugin" [Undecided,New] - Assigned to Louis Fourie (lfourie)17:27
igordcardwe can coordinate then georgewang17:27
cathy_s3wong: this is an item under the "action status" topic":-)17:27
cathy_igordcard: georgewang thanks17:27
*** jmckind has quit IRC17:27
s3wongcathy_: but current topic is "FC priority status" :-)17:28
cathy_s3wong: good point17:28
cathy_Sorry I mistype that.17:28
cathy_Let me use "topic" then17:28
cathy_#topic Move the Path ID generation17:28
*** openstack changes topic to "Move the Path ID generation (Meeting topic: service_chaining)"17:28
cathy_#link https://bugs.launchpad.net/networking-sfc/+bug/158846017:28
openstackLaunchpad bug 1588460 in networking-sfc "Move path-id generation from ovs driver to plugin" [Undecided,New] - Assigned to Louis Fourie (lfourie)17:28
cathy_#action georgewang and igordcard will coordinate to implement this17:29
cathy_#topic OVN driver for networking-sfc spec and implementation17:29
*** openstack changes topic to "OVN driver for networking-sfc spec and implementation (Meeting topic: service_chaining)"17:29
cathy_LouisF: are you working on this?17:30
LouisFcathy_: fsunaval and I are working on it17:30
cathy_LouisF: great. Thanks17:30
LouisFregXboi: you also right?17:30
doonhammercathy: I am working with regXboi and team to get a set of patches in17:30
LouisFand doonhammer17:31
cathy_#action LouisF and fsunaval will work on the OVN driver spec for supporting networking-sfc17:31
doonhammerwe have patches coming for networking-sfc/ovn and ovs/ovn17:31
regXboiack to doonhammer's comments - we're trying to get the first wave of WIP/RFC patches in asap17:31
cathy_#action LouisF and fsunaval and doonhammer will work on the OVN driver spec for supporting networking-sfc17:31
s3wongcathy_17:31
LouisFdoonhammer: regXboi does this support the port-pair-group?17:32
doonhammercathy: once doonhammer has wiki access :-(17:32
s3wongcathy_: didn't know LouisF and fsunaval are working on this also...17:32
cathy_doonhammer: regXboi great progress!17:32
*** shaohe_feng has quit IRC17:32
regXboiit may not initially, but it will17:32
*** ddieterly is now known as ddieterly[away]17:32
cathy_doonhammer: regXboi thanks17:32
*** unicell has joined #openstack-meeting-417:32
doonhammerLouisF: yes I have the full networking-sfc interface into ovs/ovn17:32
*** amotoki has joined #openstack-meeting-417:32
doonhammerLouisF: almost17:32
*** shaohe_feng has joined #openstack-meeting-417:33
LouisFregXboi: doonhammer can send you the nb-schema we have for port-chains17:33
s3wongdoonhammer: there are changes to OVN / OVS community, right?17:33
regXboiLouisF: I've seen it, and short of the flow classifier, it's reasonable17:33
regXbois3wong: yes, there will be17:33
LouisFincluding port-chain, port-pair-group and port-pairs17:33
fsunavaldoonhammer: how is load-balancing handled currently in OVN driver ?17:34
regXbois3wong: changes to ovnnb schema/ovn-northd/ovnsb schema/ovn controller17:34
LouisFOVN ACLs would serve as flow-classifier17:34
regXboiLouisF: that's where I'm going17:34
doonhammers3wong: yes changes to ovn-nb.ovsschema, ovn_northd.c and ovn-nbctl.c17:34
regXboifsunaval: the select group action in open vswitch17:34
LouisFwith an action that references a named port-chain17:34
regXboithat's the intent for load balancing17:35
doonhammerLouisF:regXboi: flow-classifier and load-balacning are the area that need most work17:35
LouisFregXboi: yes the ppg would be implemented as an ovs group table17:35
LouisFregXboi: with each bucket being a port-pair in the PPG17:36
regXboiLouisF: ack17:36
LouisFthat is the way it is currently implemated in the ovs driver and works ok17:36
*** vtech has quit IRC17:37
*** iberezovskiy is now known as iberezovskiy_afk17:38
*** amotoki has quit IRC17:38
cathy_doonhammer: regXboi it will be great to have a consistent mechanism of adding/modifying the OVS group table and flow table between the OVS driver path and the OVN path17:38
regXboicathy_: I don't think that is possible17:39
regXboithe ML2 driver and the OVN approach have distinctly different views of what OVS table does what17:39
LouisFregXboi: agree but the use of the ovs group can be similar17:39
doonhammercathy: not sure it is desirable as the logical model of OVN provides location independance of VNFs17:40
fsunavalregXboi:  Also, we need to make sure that the design allows for SFC encapsulation (NSH or whatever). Simply changing the logical DI is not enough.17:40
regXboiLouisF: depends on your definition of "similar" :)17:40
LouisFto use the ovs group with buckets17:40
regXboiLouisF: that, I agree with :)17:41
regXboifsunaval: in my mind, if the design works without encapsulation, then adding it should be relatively simple (famous last words)17:41
*** tonytan4ever has joined #openstack-meeting-417:42
*** shaohe_feng has quit IRC17:42
igordcardregXboi: yes, at the dataplane level yes, the bottleneck then lies in the user-exposed API - unless to encapsulate for the sake of encapsulating17:43
LouisFregXboi: sfc encap is needed to deal with the case where dpi classifers are used17:43
*** shaohe_feng has joined #openstack-meeting-417:43
*** yamamoto has quit IRC17:43
scsnowIs someone working on adding NSH support in ovs driver?17:43
igordcardLouisF: a good example, I agree17:43
cathy_scsnow: that is our next topic:-)17:44
*** SumitNaiksatam has joined #openstack-meeting-417:44
s3wongscsnow: the better question is: is anyone having any success on adding support of NSH into OVS in general :-)17:44
regXboiLouisF: that becomes (in my mind) an add-on to the basic flows17:44
scsnows3wong, yes, I have some problems with patched 2.5.90 =)17:44
igordcardscsnow: was waiting for the next topic, but yes I've started in a local branch17:45
cathy_scsnow: what do you mean problems?17:45
*** ihrachys has quit IRC17:45
cathy_scsnow: not working?17:45
cathy_OK, let's go to the next topic17:45
LouisFregXboi: we should look at that17:45
scsnowIt does not pass packets. having:17:45
scsnowJun  1 14:31:45 localhost ovs-vswitchd: ovs|00019|odp_util(handler4)|ERR|attribute tcp_flags has length 4 but should have length 217:45
regXboiLouisF: look at what?17:45
s3wongscsnow: problem as in not working (doesn't exist) at all?  :-)17:46
LouisFsfc encap17:46
igordcardscsnow: are you using yi's april patches?17:46
regXboiLouisF: getting the basic stuff working without sfc encap is my first goal17:46
scsnowI use patches from https://github.com/yyang13/ovs_nsh_patches17:46
LouisFregXboi: ok17:46
igordcardscsnow: yep those17:46
mohankumarscsnow , our ONOS development team  used it and they able to make it work17:47
cathy_igordcard: scsnow two topic threads are being discussed here. let's hold on the discussion on Yi' NSH patch to next topic:-)17:47
scsnowcathy_, ok17:47
igordcardscsnow: I have compiled that OVS but haven't actually made packets flow through yet, I'll try it an come back to you17:47
*** singlethink has quit IRC17:47
igordcardand*17:47
s3wongcathy_: agreed17:47
s3wongLouisF, regXboi: anything else to discuss for OVN SFC driver?17:48
LouisFregXboi: are you working in a repo?17:48
regXbois3wong: no - just trying to get patches out ...17:48
regXboiLouisF: no - I'm trying to get the patches submitted to r.o.o and patchworks17:48
cathy_regXboi: I think Louis's point is that if you take encap into consideration, the place to set the next hop could be changed. You may want to set the next hop in the ingress place, not the egress place17:48
cathy_regXboi: we can take this detail discussion off line via emails17:49
regXboicathy_: that becomes an addition flow rule, that's all17:49
LouisFcathy_: ok17:49
regXboiso the base stuff goes in, and that goes in as a new flow rule17:49
regXboibut I agree that the ML is a good place...17:49
s3wongI think they are working with doonhammer's private repo --- which hopefully can instead be a patch posted on gerrit against networking-sfc soon17:49
doonhammers3wong: that is the plan17:50
cathy_doonhammer: cool.17:50
cathy_can we go to next topic?17:50
LouisF+117:50
regXbois3wong: *that* is my goal17:50
s3wongdoonhammer, regXboi: cool17:51
cathy_#action doonhammer regXboi will post a patch in gerrit against networking-sfc after it is baked complete enough17:51
cathy_#topic add PPG parameter to specify insert-mode behavior for all PPs in a PPG17:52
*** openstack changes topic to "add PPG parameter to specify insert-mode behavior for all PPs in a PPG (Meeting topic: service_chaining)"17:52
cathy_This is about the L2/L3 mode doonhammer raised before17:52
cathy_who would like to work on this item?17:52
*** shaohe_feng has quit IRC17:52
LouisFi have added a bug for that https://bugs.launchpad.net/networking-sfc/+bug/158846317:53
openstackLaunchpad bug 1588463 in networking-sfc "Add port-pair-group parameter" [Undecided,New] - Assigned to Louis Fourie (lfourie)17:53
scsnowcathy_, is this just an api change or it should be supported in ovs driver as well?17:53
cathy_#link https://bugs.launchpad.net/networking-sfc/+bug/158846317:53
s3wongcathy_: how do we do L3 insertion in OVS driver?17:53
LouisFscsnow: it would be a api change17:53
cathy_scsnow: it should be supported in the OVS driver17:53
fsunavals3wong: we change the MAC DA.17:54
cathy_LouisF: this bug is for APi change, but we should have codes in OVS driver too17:54
LouisFdoonhammer: you have the use case for bitw SFs?17:54
LouisFcathy_: i can add that to the bug17:54
cathy_I will create another bug for the OVS driver, OVS agent change17:54
LouisFcathy_: ok17:55
scsnowI can do an API change17:55
LouisFscsnow: ok17:55
doonhammerLouisF: Yes manly for east-west/micro-segmentation17:55
s3wongfsunaval: so do we (OVS driver for SFC) serve as a virtual router also?17:55
*** shaohe_feng has joined #openstack-meeting-417:56
cathy_#action scsnow will do the API change for bug 1588463. Thanks!17:56
openstackbug 1588463 in networking-sfc "Add port-pair-group parameter" [Undecided,New] https://launchpad.net/bugs/1588463 - Assigned to Louis Fourie (lfourie)17:56
scsnowFor ovs driver change I would need some more initial description17:56
doonhammerLouisF: For a lot of VNFs not having to participate in networking directly makes scaling and management significantly easier17:56
fsunavals3wong: Currently, we only support the case where the VNF is a L3 function. For this, the OVS flow rule changes the MAC DA to match that of the VNF.17:56
LouisFdoonhammer: agree17:56
cathy_scsnow: Louis and I will add more description to that bug on the OVS driver change17:57
fsunavalThe VNF then does its stuff and sends the packet with the MAC SA changed to itself. doonhammer's case is tricky to implement in OVS. The VNF forwards the same packet without modification.17:57
scsnowcathy_, after that I'll let you know whether I'm able to handle driver part17:57
cathy_scsnow: OK, I will create another bug for the driver and agent part.17:58
cathy_fsunaval: could I assign the driver and agent bug to you?17:59
fsunavalcathy_: Yes, you can. We will need to discuss thoroughly how to implement the agent though.17:59
s3wongfsunaval, scsnow, cathy_, LouisF: still can't quite picture it... when kanzhe and I proposed service insertion back in Juno cycle, the 'router' insertion is closest to this, but the service needs to be integrated into router17:59
cathy_sorry we are running out of time18:00
LouisFbye18:00
scsnowdo we have team channel in irc?18:00
mohankumarbye18:00
igordcardcya18:00
cathy_Let's continue the discussion next week.18:00
LouisFscsnow: no18:00
doonhammerbye18:01
igordcarda channel would be nice18:01
fsunavals3wong: let us discuss over email.18:01
s3wongbye18:01
cathy_scsnow: no. shoot emails:-)18:01
s3wongfsunaval: sure18:01
LouisFscsnow: lets add one18:01
scsnowok, bye then18:01
cathy_bye for now18:01
fsunavalbye18:01
cathy_#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Thu Jun  2 18:01:23 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-06-02-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-06-02-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-06-02-17.00.log.html18:01
*** regXboi has left #openstack-meeting-418:01
*** spzala has joined #openstack-meeting-418:01
*** cathy_ has quit IRC18:02
*** shaohe_feng has quit IRC18:03
*** shaohe_feng has joined #openstack-meeting-418:04
*** georgewang has quit IRC18:05
*** spzala has quit IRC18:06
*** galstrom is now known as galstrom_zzz18:06
*** degorenko is now known as _degorenko|afk18:06
*** iurygregory_ has joined #openstack-meeting-418:07
*** vtech has joined #openstack-meeting-418:07
*** galstrom_zzz is now known as galstrom18:08
*** david-lyle has joined #openstack-meeting-418:09
*** Srilatha_ has quit IRC18:09
*** shaohe_feng has quit IRC18:13
*** shaohe_feng has joined #openstack-meeting-418:14
*** jichen has joined #openstack-meeting-418:14
*** kylek3h has quit IRC18:15
*** uck has quit IRC18:16
*** mohankumar has quit IRC18:17
pcarver18:21
*** spotz is now known as spotz_zzz18:22
*** shaohe_feng has quit IRC18:23
*** julim has joined #openstack-meeting-418:23
*** shaohe_feng has joined #openstack-meeting-418:24
*** spzala has joined #openstack-meeting-418:29
*** shaohe_feng has quit IRC18:33
*** amotoki has joined #openstack-meeting-418:34
*** shaohe_feng has joined #openstack-meeting-418:34
*** david-lyle has quit IRC18:35
*** ddieterly[away] is now known as ddieterly18:37
*** vishnoianil has quit IRC18:38
*** amotoki has quit IRC18:39
*** sarob has joined #openstack-meeting-418:43
*** ddieterly has quit IRC18:43
*** shaohe_feng has quit IRC18:44
*** yamamoto has joined #openstack-meeting-418:44
*** shaohe_feng has joined #openstack-meeting-418:45
*** Srilatha has joined #openstack-meeting-418:45
*** jmckind has joined #openstack-meeting-418:46
*** galstrom is now known as galstrom_zzz18:47
*** vhoward has quit IRC18:47
*** nmadhok has quit IRC18:47
*** javeriak has joined #openstack-meeting-418:47
*** fsunaval has quit IRC18:53
*** yamamoto has quit IRC18:53
*** shaohe_feng has quit IRC18:54
*** nmadhok has joined #openstack-meeting-418:54
*** shaohe_feng has joined #openstack-meeting-418:55
*** doonhammer has quit IRC18:56
*** cartik has joined #openstack-meeting-418:56
*** pmesserl_ has joined #openstack-meeting-418:57
*** numans has quit IRC18:58
*** Srilatha has quit IRC19:00
*** Srilatha has joined #openstack-meeting-419:01
*** shaohe_feng has quit IRC19:04
*** shaohe_feng has joined #openstack-meeting-419:05
*** Srilatha has quit IRC19:05
*** cartik has quit IRC19:06
*** GB21 has quit IRC19:10
*** shaohe_feng has quit IRC19:14
*** shaohe_feng has joined #openstack-meeting-419:15
*** antongribok has joined #openstack-meeting-419:16
*** weezS has left #openstack-meeting-419:22
*** doonhammer has joined #openstack-meeting-419:24
*** david-lyle has joined #openstack-meeting-419:24
*** shaohe_feng has quit IRC19:25
*** shaohe_feng has joined #openstack-meeting-419:25
*** Sukhdev has joined #openstack-meeting-419:28
*** azbiswas has quit IRC19:28
*** azbiswas has joined #openstack-meeting-419:29
*** Jeffrey4l_ has quit IRC19:30
*** Jeffrey4l_ has joined #openstack-meeting-419:31
*** Srilatha has joined #openstack-meeting-419:32
*** azbiswas has quit IRC19:33
*** amotoki has joined #openstack-meeting-419:34
*** iyamahat has quit IRC19:35
*** sdake has quit IRC19:35
*** shaohe_feng has quit IRC19:35
*** dshakhray has joined #openstack-meeting-419:35
*** zeih has joined #openstack-meeting-419:35
*** azbiswas has joined #openstack-meeting-419:36
*** SumitNaiksatam has quit IRC19:36
*** Srilatha has quit IRC19:36
*** sdake has joined #openstack-meeting-419:38
*** shaohe_feng has joined #openstack-meeting-419:38
*** amotoki has quit IRC19:39
*** openstack has joined #openstack-meeting-419:42
*** ChanServ sets mode: +o openstack19:42
*** sdake has quit IRC19:43
*** shaohe_feng has quit IRC19:45
*** shaohe_feng has joined #openstack-meeting-419:46
*** uck has joined #openstack-meeting-419:48
*** doonhammer has quit IRC19:51
*** mbound has quit IRC19:53
*** uck has quit IRC19:53
*** uck_ has joined #openstack-meeting-419:53
*** shaohe_feng has quit IRC19:55
*** shaohe_feng has joined #openstack-meeting-419:56
*** jichen has quit IRC19:57
*** david-lyle has quit IRC19:57
*** jichen has joined #openstack-meeting-419:59
*** zeih has joined #openstack-meeting-420:03
*** galstrom_zzz is now known as galstrom20:04
*** sshnaidm is now known as sshnaidm|afk20:04
*** shaohe_feng has quit IRC20:06
*** shaohe_feng has joined #openstack-meeting-420:06
*** zeih has quit IRC20:07
*** spzala has quit IRC20:08
*** dshakhray has quit IRC20:09
*** Sukhdev has quit IRC20:09
*** jmccrory_ has quit IRC20:09
*** Sukhdev has joined #openstack-meeting-420:09
*** Srilatha has joined #openstack-meeting-420:10
*** dshakhray has joined #openstack-meeting-420:10
*** mfedosin has quit IRC20:10
*** Sukhdev has quit IRC20:13
*** iyamahat has joined #openstack-meeting-420:13
*** spzala has joined #openstack-meeting-420:14
*** shaohe_feng has quit IRC20:16
*** shaohe_feng has joined #openstack-meeting-420:16
*** spzala has quit IRC20:19
*** jmckind has quit IRC20:19
*** Srilatha has quit IRC20:20
*** Srilatha has joined #openstack-meeting-420:21
*** emagana has quit IRC20:24
*** jmckind has joined #openstack-meeting-420:26
*** shaohe_feng has quit IRC20:26
*** dshakhray has quit IRC20:26
*** shaohe_feng has joined #openstack-meeting-420:27
*** dshakhray has joined #openstack-meeting-420:28
*** banix has quit IRC20:29
*** emagana has joined #openstack-meeting-420:30
*** emagana has quit IRC20:30
*** emagana has joined #openstack-meeting-420:30
*** uck has joined #openstack-meeting-420:32
*** uck_ has quit IRC20:32
*** spzala has joined #openstack-meeting-420:33
*** piet_ has joined #openstack-meeting-420:34
*** amotoki has joined #openstack-meeting-420:35
*** vishnoianil has joined #openstack-meeting-420:36
*** shaohe_feng has quit IRC20:36
*** shaohe_feng has joined #openstack-meeting-420:37
*** amotoki has quit IRC20:40
*** tonytan4ever has quit IRC20:41
*** antongribok has quit IRC20:41
*** shaohe_feng has quit IRC20:47
*** doonhammer has joined #openstack-meeting-420:47
*** phil_h has quit IRC20:48
*** pmesserli has quit IRC20:51
*** shaohe_feng has joined #openstack-meeting-420:52
*** julim has quit IRC20:53
*** mbound has joined #openstack-meeting-420:53
*** shaohe_feng has quit IRC20:57
*** woodard_ has joined #openstack-meeting-420:58
*** mbound has quit IRC20:58
*** shaohe_feng has joined #openstack-meeting-420:58
*** woodard has quit IRC21:01
*** woodard_ has quit IRC21:03
*** iurygregory_ has quit IRC21:03
*** thorst has quit IRC21:03
*** phil_h has joined #openstack-meeting-421:04
*** jichen has quit IRC21:05
*** baoli_ has quit IRC21:05
*** thorst has joined #openstack-meeting-421:05
*** shaohe_feng has quit IRC21:07
*** thorst_ has joined #openstack-meeting-421:08
*** Srilatha has quit IRC21:08
*** shaohe_feng has joined #openstack-meeting-421:08
*** thorst has quit IRC21:10
*** thorst_ has quit IRC21:12
*** shaohe_feng has quit IRC21:17
*** shaohe_feng has joined #openstack-meeting-421:19
*** yamahata has quit IRC21:21
*** rtheis has quit IRC21:25
*** shaohe_feng has quit IRC21:28
*** shaohe_feng has joined #openstack-meeting-421:29
*** thorst has joined #openstack-meeting-421:30
*** messy has joined #openstack-meeting-421:32
*** messy has left #openstack-meeting-421:32
*** thorst has quit IRC21:35
*** amotoki has joined #openstack-meeting-421:36
*** shaohe_feng has quit IRC21:38
*** javeriak has quit IRC21:39
*** shaohe_feng has joined #openstack-meeting-421:39
*** nmadhok has quit IRC21:40
*** amotoki has quit IRC21:42
*** woodard has joined #openstack-meeting-421:43
*** Srilatha has joined #openstack-meeting-421:44
*** doonhammer has quit IRC21:47
*** shaohe_feng has quit IRC21:48
*** shaohe_feng has joined #openstack-meeting-421:49
*** spzala has quit IRC21:51
*** jmckind has quit IRC21:53
*** zenoway has joined #openstack-meeting-421:56
*** galstrom is now known as galstrom_zzz21:57
*** markvoelker has quit IRC21:58
*** shaohe_feng has quit IRC21:58
*** shaohe_feng has joined #openstack-meeting-421:59
*** ametts has quit IRC22:03
*** Srilatha has quit IRC22:05
*** Srilatha has joined #openstack-meeting-422:06
*** doonhammer has joined #openstack-meeting-422:09
*** shaohe_feng has quit IRC22:09
*** shaohe_feng has joined #openstack-meeting-422:09
*** Srilatha has quit IRC22:09
*** dshakhray has quit IRC22:12
*** banix has joined #openstack-meeting-422:13
*** sacharya has quit IRC22:17
*** Srilatha has joined #openstack-meeting-422:17
*** zenoway has quit IRC22:18
*** shaohe_feng has quit IRC22:19
*** klamath has quit IRC22:19
*** shaohe_feng has joined #openstack-meeting-422:20
*** Srilatha has quit IRC22:21
*** bobh has quit IRC22:22
*** cwolferh has quit IRC22:28
*** Srilatha_ has joined #openstack-meeting-422:29
*** shaohe_feng has quit IRC22:29
*** shaohe_feng has joined #openstack-meeting-422:30
*** IlyaG has joined #openstack-meeting-422:30
*** dave-mccowan has quit IRC22:30
*** Srilatha_ has quit IRC22:30
*** prithiv has joined #openstack-meeting-422:31
*** Srilatha_ has joined #openstack-meeting-422:31
*** azbiswas has quit IRC22:33
*** azbiswas has joined #openstack-meeting-422:34
*** Srilatha has joined #openstack-meeting-422:34
*** Srilatha_ has quit IRC22:35
*** LouisF has quit IRC22:37
*** azbiswas has quit IRC22:38
*** Srilatha has quit IRC22:39
*** Srilatha has joined #openstack-meeting-422:39
*** shaohe_feng has quit IRC22:39
*** shaohe_feng has joined #openstack-meeting-422:40
*** Srilatha_ has joined #openstack-meeting-422:42
*** Srilatha has quit IRC22:44
*** JRobinson__ has joined #openstack-meeting-422:44
*** cwolferh has joined #openstack-meeting-422:48
*** dave-mccowan has joined #openstack-meeting-422:48
*** rbak has quit IRC22:49
*** shaohe_feng has quit IRC22:50
*** shaohe_feng has joined #openstack-meeting-422:51
*** Adri2000 has quit IRC22:53
*** Adri2000 has joined #openstack-meeting-422:54
*** pmesserl_ has quit IRC22:54
*** doonhammer has quit IRC22:56
*** markvoelker has joined #openstack-meeting-422:58
*** shaohe_feng has quit IRC23:00
*** shaohe_feng has joined #openstack-meeting-423:01
*** nmadhok has joined #openstack-meeting-423:02
*** markvoelker has quit IRC23:03
*** JRobinson__ has quit IRC23:06
*** emagana has quit IRC23:06
*** tonytan4ever has joined #openstack-meeting-423:06
*** sulo has quit IRC23:06
*** iyamahat has quit IRC23:07
*** sulo has joined #openstack-meeting-423:07
*** vishnoianil has quit IRC23:07
*** shaohe_feng has quit IRC23:10
*** shaohe_feng has joined #openstack-meeting-423:13
*** emagana has joined #openstack-meeting-423:15
*** hvprash has quit IRC23:15
*** hvprash has joined #openstack-meeting-423:15
*** weezS has joined #openstack-meeting-423:18
*** IlyaG has quit IRC23:18
*** prithiv has quit IRC23:19
*** emagana has quit IRC23:19
*** david-lyle has joined #openstack-meeting-423:20
*** shaohe_feng has quit IRC23:20
*** shaohe_feng has joined #openstack-meeting-423:21
*** weezS has quit IRC23:24
*** kylek3h has joined #openstack-meeting-423:25
*** rbak has joined #openstack-meeting-423:27
*** kylek3h_ has joined #openstack-meeting-423:29
*** shaohe_feng has quit IRC23:31
*** shaohe_feng has joined #openstack-meeting-423:32
*** kylek3h has quit IRC23:32
*** zhurong has joined #openstack-meeting-423:36
*** amotoki has joined #openstack-meeting-423:39
*** zhurong has quit IRC23:40
*** shaohe_feng has quit IRC23:41
*** shaohe_feng has joined #openstack-meeting-423:44
*** amotoki has quit IRC23:44
*** vishwanathj has joined #openstack-meeting-423:49
*** shaohe_feng has quit IRC23:51
*** Srilatha_ has quit IRC23:52
*** shaohe_feng has joined #openstack-meeting-423:52
*** sdake has joined #openstack-meeting-423:54
*** hvprash_ has joined #openstack-meeting-423:56
*** sdake_ has quit IRC23:56
*** sdake has quit IRC23:57
*** sdake has joined #openstack-meeting-423:57
*** sdague has quit IRC23:58
*** doonhammer has joined #openstack-meeting-423:58
*** hvprash has quit IRC23:59

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