Thursday, 2016-05-12

*** thorst__ has quit IRC00:00
*** padkrish has joined #openstack-meeting-400:00
*** thorst__ has joined #openstack-meeting-400:00
*** thors____ has quit IRC00:01
*** thorst___ has joined #openstack-meeting-400:01
*** thor_____ has quit IRC00:02
*** bpokorny_ has joined #openstack-meeting-400:02
*** uck has quit IRC00:03
*** thors____ has joined #openstack-meeting-400:03
*** nmadhok has quit IRC00:03
*** thorst_ has quit IRC00:03
*** thorst_ has joined #openstack-meeting-400:04
*** thor_____ has joined #openstack-meeting-400:05
*** thorst__ has quit IRC00:05
*** bpokorny has quit IRC00:05
*** thorst___ has quit IRC00:05
*** thorst__ has joined #openstack-meeting-400:06
*** shaohe_feng has quit IRC00:06
*** thorst___ has joined #openstack-meeting-400:07
*** bpokorny_ has quit IRC00:07
*** tho______ has joined #openstack-meeting-400:08
*** thors____ has quit IRC00:08
*** IlyaG has quit IRC00:08
*** thorst_ has quit IRC00:08
*** thorst_ has joined #openstack-meeting-400:08
*** shaohe_feng has joined #openstack-meeting-400:09
*** thors____ has joined #openstack-meeting-400:09
*** thor_____ has quit IRC00:09
*** thorst__ has quit IRC00:10
*** thorst___ has quit IRC00:11
*** tho______ has quit IRC00:12
*** thorst__ has joined #openstack-meeting-400:12
*** thorst_ has quit IRC00:13
*** thorst_ has joined #openstack-meeting-400:13
*** thors____ has quit IRC00:14
*** ddieterly has joined #openstack-meeting-400:14
*** thorst___ has joined #openstack-meeting-400:14
*** thors____ has joined #openstack-meeting-400:15
*** thor_____ has joined #openstack-meeting-400:16
*** shaohe_feng has quit IRC00:17
*** shaohe_feng has joined #openstack-meeting-400:17
*** thorst__ has quit IRC00:17
*** thorst__ has joined #openstack-meeting-400:17
*** thorst_ has quit IRC00:18
*** thorst_ has joined #openstack-meeting-400:18
*** thorst___ has quit IRC00:18
*** thors____ has quit IRC00:19
*** thorst___ has joined #openstack-meeting-400:19
*** thors____ has joined #openstack-meeting-400:20
*** thor_____ has quit IRC00:20
*** thor_____ has joined #openstack-meeting-400:21
*** tho______ has joined #openstack-meeting-400:22
*** thorst__ has quit IRC00:22
*** thorst_ has quit IRC00:23
*** thorst_ has joined #openstack-meeting-400:23
*** thorst___ has quit IRC00:23
*** doonhammer has quit IRC00:24
*** thors____ has quit IRC00:24
*** thorst__ has joined #openstack-meeting-400:24
*** thorst___ has joined #openstack-meeting-400:25
*** thor_____ has quit IRC00:25
*** tho______ has quit IRC00:26
*** thors____ has joined #openstack-meeting-400:26
*** thor_____ has joined #openstack-meeting-400:27
*** shaohe_feng has quit IRC00:27
*** thorst_ has quit IRC00:27
*** shaohe_feng has joined #openstack-meeting-400:28
*** thorst_ has joined #openstack-meeting-400:28
*** thorst__ has quit IRC00:29
*** bobh has quit IRC00:29
*** thorst__ has joined #openstack-meeting-400:29
*** thorst___ has quit IRC00:30
*** thorst___ has joined #openstack-meeting-400:30
*** thors____ has quit IRC00:31
*** thors____ has joined #openstack-meeting-400:31
*** thor_____ has quit IRC00:31
*** thorst_ has quit IRC00:32
*** thorst_ has joined #openstack-meeting-400:32
*** thor_____ has joined #openstack-meeting-400:33
*** asalkeld has left #openstack-meeting-400:34
*** tho______ has joined #openstack-meeting-400:34
*** thorst__ has quit IRC00:34
*** thorst___ has quit IRC00:35
*** thorst__ has joined #openstack-meeting-400:35
*** thors____ has quit IRC00:36
*** thorst___ has joined #openstack-meeting-400:37
*** thorst_ has quit IRC00:37
*** shaohe_feng has quit IRC00:37
*** thor_____ has quit IRC00:37
*** thorst_ has joined #openstack-meeting-400:38
*** tho______ has quit IRC00:38
*** shaohe_feng has joined #openstack-meeting-400:38
*** thors____ has joined #openstack-meeting-400:39
*** gangil has quit IRC00:39
*** thorst__ has quit IRC00:39
*** thorst__ has joined #openstack-meeting-400:40
*** thor_____ has joined #openstack-meeting-400:41
*** thorst___ has quit IRC00:41
*** klamath has quit IRC00:42
xgermano/00:42
*** thorst___ has joined #openstack-meeting-400:42
*** thorst_ has quit IRC00:42
*** thorst_ has joined #openstack-meeting-400:43
*** thors____ has quit IRC00:43
*** thors____ has joined #openstack-meeting-400:44
*** thorst__ has quit IRC00:44
*** thorst__ has joined #openstack-meeting-400:45
*** thor_____ has quit IRC00:45
*** baoli has joined #openstack-meeting-400:45
*** lifeless has quit IRC00:46
*** thorst___ has quit IRC00:46
*** lifeless has joined #openstack-meeting-400:47
*** thorst___ has joined #openstack-meeting-400:47
*** thorst_ has quit IRC00:47
*** shaohe_feng has quit IRC00:47
*** shaohe_feng has joined #openstack-meeting-400:48
*** thorst_ has joined #openstack-meeting-400:48
*** thors____ has quit IRC00:48
*** thors____ has joined #openstack-meeting-400:49
*** thorst__ has quit IRC00:49
*** thorst__ has joined #openstack-meeting-400:50
*** thor_____ has joined #openstack-meeting-400:51
*** thorst___ has quit IRC00:52
*** thorst___ has joined #openstack-meeting-400:52
*** thorst_ has quit IRC00:53
*** thors____ has quit IRC00:53
*** thorst_ has joined #openstack-meeting-400:54
*** thorst__ has quit IRC00:55
*** thorst__ has joined #openstack-meeting-400:55
*** thor_____ has quit IRC00:56
*** fitoduarte has quit IRC00:56
*** thors____ has joined #openstack-meeting-400:56
*** thorst___ has quit IRC00:56
*** thorst___ has joined #openstack-meeting-400:57
*** shaohe_feng has quit IRC00:58
*** thor_____ has joined #openstack-meeting-400:58
*** shaohe_feng has joined #openstack-meeting-400:58
*** thorst_ has quit IRC00:58
*** thorst_ has joined #openstack-meeting-400:59
*** mbound has quit IRC00:59
*** thorst__ has quit IRC01:00
*** zhurong has joined #openstack-meeting-401:00
*** thorst__ has joined #openstack-meeting-401:01
*** thors____ has quit IRC01:01
*** thorst___ has quit IRC01:01
*** thorst___ has joined #openstack-meeting-401:01
*** thor_____ has quit IRC01:02
*** thors____ has joined #openstack-meeting-401:03
*** thorst_ has quit IRC01:03
*** thorst_ has joined #openstack-meeting-401:04
*** markvoelker_ has joined #openstack-meeting-401:05
*** thorst__ has quit IRC01:05
*** thor_____ has joined #openstack-meeting-401:05
*** thorst___ has quit IRC01:06
*** thorst__ has joined #openstack-meeting-401:06
*** thorst___ has joined #openstack-meeting-401:07
*** thors____ has quit IRC01:08
*** shaohe_feng has quit IRC01:08
*** thorst_ has quit IRC01:09
*** shaohe_feng has joined #openstack-meeting-401:09
*** thors____ has joined #openstack-meeting-401:09
*** thorst_ has joined #openstack-meeting-401:10
*** thor_____ has quit IRC01:10
*** trozet has quit IRC01:10
*** thorst__ has quit IRC01:10
*** thorst__ has joined #openstack-meeting-401:10
*** thorst___ has quit IRC01:11
*** thorst___ has joined #openstack-meeting-401:11
*** thor_____ has joined #openstack-meeting-401:12
*** tho______ has joined #openstack-meeting-401:13
*** thors____ has quit IRC01:13
*** thors____ has joined #openstack-meeting-401:14
*** thorst_ has quit IRC01:14
*** thorst__ has quit IRC01:15
*** thorst_ has joined #openstack-meeting-401:15
*** thorst___ has quit IRC01:16
*** thorst__ has joined #openstack-meeting-401:16
*** thorst__ has quit IRC01:16
*** thorst__ has joined #openstack-meeting-401:16
*** thor_____ has quit IRC01:17
*** tho______ has quit IRC01:18
*** shaohe_feng has quit IRC01:18
*** thorst__ has quit IRC01:19
*** thors____ has quit IRC01:19
*** shaohe_feng has joined #openstack-meeting-401:19
*** thorst_ has quit IRC01:20
*** pvaneck has quit IRC01:20
*** shakamunyi has joined #openstack-meeting-401:23
*** raddaoui has quit IRC01:27
*** woodard has quit IRC01:28
*** shaohe_feng has quit IRC01:28
*** shaohe_feng has joined #openstack-meeting-401:29
*** shaohe_feng has quit IRC01:39
*** shaohe_feng has joined #openstack-meeting-401:39
*** hvprash has joined #openstack-meeting-401:41
*** zhurong has quit IRC01:42
*** zhurong has joined #openstack-meeting-401:43
*** hvprash has quit IRC01:46
*** amotoki has joined #openstack-meeting-401:46
*** shaohe_feng has quit IRC01:49
*** shaohe_feng has joined #openstack-meeting-401:49
*** bharathm has quit IRC01:51
*** salv-orlando has joined #openstack-meeting-401:51
*** markvoelker_ has quit IRC01:51
*** salv-orlando has quit IRC01:56
*** s3wong has quit IRC01:58
*** markvoelker has joined #openstack-meeting-401:59
*** shaohe_feng has quit IRC01:59
*** markvoelker_ has joined #openstack-meeting-401:59
*** mbound has joined #openstack-meeting-402:00
*** shaohe_feng has joined #openstack-meeting-402:00
*** markvoelker has quit IRC02:03
*** zhurong has quit IRC02:04
*** mbound has quit IRC02:04
*** zhurong has joined #openstack-meeting-402:05
*** shaohe_feng has quit IRC02:09
*** shaohe_feng has joined #openstack-meeting-402:10
*** padkrish has quit IRC02:15
*** spotz_zzz is now known as spotz02:17
*** samP has joined #openstack-meeting-402:18
*** shaohe_feng has quit IRC02:20
*** shaohe_feng has joined #openstack-meeting-402:21
*** tonytan4ever has joined #openstack-meeting-402:21
*** samP has quit IRC02:22
*** ddieterly has quit IRC02:23
*** zaneb has quit IRC02:28
*** woodard has joined #openstack-meeting-402:29
*** shaohe_feng has quit IRC02:30
*** shaohe_feng has joined #openstack-meeting-402:31
*** markvoelker_ has quit IRC02:31
*** Swami_ has joined #openstack-meeting-402:34
*** woodard has quit IRC02:34
*** spzala has quit IRC02:35
*** Swami has quit IRC02:38
*** markvoelker_ has joined #openstack-meeting-402:38
*** shaohe_feng has quit IRC02:40
*** shaohe_feng has joined #openstack-meeting-402:41
*** shaohe_feng has quit IRC02:50
*** baoli has quit IRC02:51
*** shaohe_feng has joined #openstack-meeting-402:53
*** shaohe_feng has quit IRC03:01
*** unicell has quit IRC03:01
*** spzala has joined #openstack-meeting-403:01
*** unicell has joined #openstack-meeting-403:01
*** shaohe_feng has joined #openstack-meeting-403:01
*** unicell has quit IRC03:01
*** unicell has joined #openstack-meeting-403:01
*** Sukhdev has quit IRC03:02
*** spzala has quit IRC03:05
*** bobh has joined #openstack-meeting-403:06
*** tonytan4ever has quit IRC03:08
*** gangil has joined #openstack-meeting-403:08
*** gangil has joined #openstack-meeting-403:08
*** shaohe_feng has quit IRC03:11
*** unicell has quit IRC03:11
*** shaohe_feng has joined #openstack-meeting-403:11
*** britthou_ has joined #openstack-meeting-403:11
*** markvoelker_ has quit IRC03:13
*** britthouser has quit IRC03:14
*** v1k0d3n has quit IRC03:17
*** zaneb has joined #openstack-meeting-403:19
*** shaohe_feng has quit IRC03:21
*** shaohe_feng has joined #openstack-meeting-403:22
*** shaohe_feng has quit IRC03:31
*** shaohe_feng has joined #openstack-meeting-403:32
*** julim has joined #openstack-meeting-403:40
*** shaohe_feng has quit IRC03:42
*** shaohe_feng has joined #openstack-meeting-403:42
*** shaohe_feng has quit IRC03:52
*** shaohe_feng has joined #openstack-meeting-403:52
*** shaohe_feng has quit IRC04:02
*** shaohe_feng has joined #openstack-meeting-404:05
*** bobh has quit IRC04:05
*** julim has quit IRC04:07
*** bobh has joined #openstack-meeting-404:08
*** shaohe_feng has quit IRC04:12
*** bobh has quit IRC04:14
*** shaohe_feng has joined #openstack-meeting-404:15
*** Liuqing has joined #openstack-meeting-404:21
*** shaohe_feng has quit IRC04:23
*** shaohe_feng has joined #openstack-meeting-404:23
*** v1k0d3n has joined #openstack-meeting-404:24
*** pcaruana has joined #openstack-meeting-404:25
*** vishnoianil has quit IRC04:27
*** gangil has quit IRC04:30
*** pcaruana has quit IRC04:32
*** uck has joined #openstack-meeting-404:33
*** shaohe_feng has quit IRC04:33
*** shaohe_feng has joined #openstack-meeting-404:33
*** reedip__ has joined #openstack-meeting-404:37
*** coolsvap has joined #openstack-meeting-404:39
*** salv-orlando has joined #openstack-meeting-404:39
*** shaohe_feng has quit IRC04:43
*** shaohe_feng has joined #openstack-meeting-404:44
*** salv-orlando has quit IRC04:46
*** coolsvap has quit IRC04:52
*** shaohe_feng has quit IRC04:53
*** cloudtrainme has quit IRC04:54
*** shaohe_feng has joined #openstack-meeting-404:55
*** Sukhdev has joined #openstack-meeting-404:56
*** sdake has quit IRC04:57
*** salv-orlando has joined #openstack-meeting-404:58
*** spzala has joined #openstack-meeting-405:01
*** shaohe_feng has quit IRC05:04
*** shaohe_feng has joined #openstack-meeting-405:05
*** spzala has quit IRC05:07
*** coolsvap has joined #openstack-meeting-405:08
*** qwebirc96578 has joined #openstack-meeting-405:09
*** qwebirc96578 has left #openstack-meeting-405:09
*** mohankumar has joined #openstack-meeting-405:12
*** gangil has joined #openstack-meeting-405:13
*** armax has quit IRC05:13
*** shaohe_feng has quit IRC05:14
*** shaohe_feng has joined #openstack-meeting-405:15
*** mohankumar has quit IRC05:17
*** javeriak has joined #openstack-meeting-405:22
*** nmadhok has joined #openstack-meeting-405:24
*** shaohe_feng has quit IRC05:24
*** shaohe_feng has joined #openstack-meeting-405:25
*** javeriak_ has joined #openstack-meeting-405:26
*** iyamahat has joined #openstack-meeting-405:26
*** javeriak has quit IRC05:27
*** nmadhok has quit IRC05:29
*** shaohe_feng has quit IRC05:34
*** zenoway has joined #openstack-meeting-405:35
*** shaohe_feng has joined #openstack-meeting-405:36
*** nmadhok has joined #openstack-meeting-405:39
*** amotoki_ has joined #openstack-meeting-405:39
*** nmadhok has quit IRC05:40
*** nmadhok has joined #openstack-meeting-405:40
*** iyamahat has quit IRC05:43
*** amotoki has quit IRC05:43
*** shaohe_feng has quit IRC05:45
*** shaohe_feng has joined #openstack-meeting-405:46
*** gangil has quit IRC05:46
*** zenoway has quit IRC05:50
*** gangil has joined #openstack-meeting-405:54
*** shaohe_feng has quit IRC05:55
*** shaohe_feng has joined #openstack-meeting-405:56
*** spzala has joined #openstack-meeting-406:03
*** shaohe_feng has quit IRC06:05
*** nmadhok has quit IRC06:06
*** vishnoianil has joined #openstack-meeting-406:06
*** nmadhok has joined #openstack-meeting-406:06
*** spzala has quit IRC06:07
*** shaohe_feng has joined #openstack-meeting-406:08
*** cwolferh has quit IRC06:08
*** pcaruana has joined #openstack-meeting-406:12
*** shaohe_feng has quit IRC06:16
*** shaohe_feng has joined #openstack-meeting-406:16
*** elemoine- has quit IRC06:17
*** elemoine has joined #openstack-meeting-406:17
*** shaohe_feng has quit IRC06:26
*** shaohe_feng has joined #openstack-meeting-406:26
*** evgenyf has joined #openstack-meeting-406:30
*** nkrinner_afk is now known as nkrinner06:33
*** shaohe_feng has quit IRC06:36
*** salv-orlando has quit IRC06:36
*** anilvenkata has joined #openstack-meeting-406:39
*** shaohe_feng has joined #openstack-meeting-406:39
*** cloudtrainme has joined #openstack-meeting-406:43
*** belmoreira has joined #openstack-meeting-406:44
*** paul-carlton1 has joined #openstack-meeting-406:45
*** belmoreira has quit IRC06:45
*** Hunner has quit IRC06:46
*** Hunner has joined #openstack-meeting-406:46
*** Hunner has quit IRC06:46
*** Hunner has joined #openstack-meeting-406:46
*** iyamahat has joined #openstack-meeting-406:46
*** shaohe_feng has quit IRC06:46
*** Swami_ has quit IRC06:47
*** shaohe_feng has joined #openstack-meeting-406:47
*** nmadhok has quit IRC06:48
*** yamamoto has quit IRC06:49
*** Swami_ has joined #openstack-meeting-406:50
*** yamamoto has joined #openstack-meeting-406:50
*** belmoreira has joined #openstack-meeting-406:51
*** cloudtrainme has quit IRC06:54
*** cloudtrainme has joined #openstack-meeting-406:55
*** evgenyf has quit IRC06:55
*** shaohe_feng has quit IRC06:57
*** crinkle_ has joined #openstack-meeting-406:59
*** Sukhdev has quit IRC06:59
*** crinkle has quit IRC07:00
*** shaohe_feng has joined #openstack-meeting-407:00
*** crinkle_ is now known as crinkle07:00
*** mmedvede has quit IRC07:00
*** spzala has joined #openstack-meeting-407:04
*** fwdit has joined #openstack-meeting-407:05
*** shaohe_feng has quit IRC07:07
*** shaohe_feng has joined #openstack-meeting-407:08
*** spzala has quit IRC07:09
*** matrohon has joined #openstack-meeting-407:11
*** jichen has joined #openstack-meeting-407:14
*** cloudtrainme has quit IRC07:17
*** shaohe_feng has quit IRC07:17
*** shaohe_feng has joined #openstack-meeting-407:18
*** jed56 has joined #openstack-meeting-407:19
*** cloudtrainme has joined #openstack-meeting-407:19
*** uck has quit IRC07:25
*** mmedvede has joined #openstack-meeting-407:27
*** shaohe_feng has quit IRC07:27
*** acabot_ has joined #openstack-meeting-407:27
*** shaohe_feng has joined #openstack-meeting-407:28
*** zeih has joined #openstack-meeting-407:29
*** acabot_ has quit IRC07:31
*** yamahata has joined #openstack-meeting-407:31
*** iyamahat has quit IRC07:32
*** salv-orlando has joined #openstack-meeting-407:37
*** shaohe_feng has quit IRC07:38
*** shaohe_feng has joined #openstack-meeting-407:38
*** paul-carlton1 has quit IRC07:41
*** zenoway has joined #openstack-meeting-407:42
*** zenoway has quit IRC07:42
*** salv-orlando has quit IRC07:42
*** zenoway has joined #openstack-meeting-407:42
*** shaohe_feng has quit IRC07:48
*** shaohe_feng has joined #openstack-meeting-407:48
*** Swami_ has quit IRC07:49
*** cloudtrainme has quit IRC07:52
*** paul-carlton1 has joined #openstack-meeting-407:55
*** shaohe_feng has quit IRC07:58
*** shaohe_feng has joined #openstack-meeting-407:59
*** paul-carlton1 has quit IRC08:00
*** spzala has joined #openstack-meeting-408:05
*** javeriak_ has quit IRC08:05
*** shaohe_feng has quit IRC08:08
*** chem has joined #openstack-meeting-408:09
*** shaohe_feng has joined #openstack-meeting-408:09
*** spzala has quit IRC08:10
*** zhurong has quit IRC08:11
*** zhurong has joined #openstack-meeting-408:12
*** javeriak has joined #openstack-meeting-408:15
*** shaohe_feng has quit IRC08:19
*** shaohe_feng has joined #openstack-meeting-408:19
*** zhurong_ has joined #openstack-meeting-408:20
*** Liuqing_ has joined #openstack-meeting-408:20
*** Jeffrey4l has quit IRC08:22
*** zhurong has quit IRC08:22
*** Liuqing has quit IRC08:22
*** bharathm has joined #openstack-meeting-408:25
*** spotz is now known as spotz_zzz08:26
*** Jeffrey4l has joined #openstack-meeting-408:26
*** shaohe_feng has quit IRC08:29
*** shaohe_feng has joined #openstack-meeting-408:29
*** gangil has quit IRC08:31
*** gangil has joined #openstack-meeting-408:31
*** mjblack has quit IRC08:34
*** mjblack has joined #openstack-meeting-408:34
*** paul-carlton1 has joined #openstack-meeting-408:38
*** yamahata has quit IRC08:38
*** shaohe_feng has quit IRC08:39
*** shaohe_feng has joined #openstack-meeting-408:39
*** paul-carlton1 has quit IRC08:42
*** dtardivel has joined #openstack-meeting-408:42
*** GB21 has joined #openstack-meeting-408:47
*** shaohe_feng has quit IRC08:49
*** shaohe_feng has joined #openstack-meeting-408:50
*** gangil has quit IRC08:52
*** gangil has joined #openstack-meeting-408:55
*** salv-orlando has joined #openstack-meeting-408:56
*** gangil has quit IRC08:57
*** shaohe_feng has quit IRC09:00
*** shaohe_feng has joined #openstack-meeting-409:01
*** pcaruana is now known as pcaruana|afk|09:01
*** salv-orlando has quit IRC09:02
*** spzala has joined #openstack-meeting-409:06
*** gangil has joined #openstack-meeting-409:07
*** shaohe_feng has quit IRC09:10
*** spzala has quit IRC09:11
*** shaohe_feng has joined #openstack-meeting-409:12
*** GB21 has quit IRC09:16
*** shaohe_feng has quit IRC09:20
*** shaohe_feng has joined #openstack-meeting-409:21
*** evgenyf has joined #openstack-meeting-409:29
*** shaohe_feng has quit IRC09:30
*** shaohe_feng has joined #openstack-meeting-409:31
*** GB21 has joined #openstack-meeting-409:33
*** alexchadin has joined #openstack-meeting-409:37
*** shaohe_feng has quit IRC09:41
*** shaohe_feng has joined #openstack-meeting-409:42
*** gangil has quit IRC09:43
*** shaohe_feng has quit IRC09:51
*** amotoki has joined #openstack-meeting-409:52
*** evgenyf has quit IRC09:52
*** shaohe_feng has joined #openstack-meeting-409:53
*** amotoki_ has quit IRC09:54
*** alexchad_ has joined #openstack-meeting-409:56
*** alexchadin has quit IRC09:58
*** shaohe_feng has quit IRC10:01
*** shaohe_feng has joined #openstack-meeting-410:02
*** yamamoto has quit IRC10:05
*** zhurong_ has quit IRC10:06
*** GB21 has quit IRC10:08
*** Liuqing_ has quit IRC10:08
*** alexchad_ is now known as alexchadin10:10
*** shaohe_feng has quit IRC10:11
*** shaohe_feng has joined #openstack-meeting-410:12
*** nmadhok has joined #openstack-meeting-410:15
*** chem has quit IRC10:16
*** __szilard_cserey has joined #openstack-meeting-410:18
*** shaohe_feng has quit IRC10:22
*** shaohe_feng has joined #openstack-meeting-410:22
*** dshakhray has joined #openstack-meeting-410:24
*** GB21 has joined #openstack-meeting-410:25
*** shaohe_feng has quit IRC10:32
*** reedip__ has quit IRC10:33
*** sdague has joined #openstack-meeting-410:34
*** yamamoto_ has joined #openstack-meeting-410:34
*** shaohe_feng has joined #openstack-meeting-410:35
*** zaneb has quit IRC10:35
*** zaneb has joined #openstack-meeting-410:35
*** nmadhok has quit IRC10:36
*** alexchadin has quit IRC10:39
*** shaohe_feng has quit IRC10:42
*** shaohe_feng has joined #openstack-meeting-410:43
*** shaohe_feng has quit IRC10:52
*** shaohe_feng has joined #openstack-meeting-410:53
*** GB21 has quit IRC10:56
*** hvprash has joined #openstack-meeting-410:58
*** rtheis has joined #openstack-meeting-410:59
*** hvprash has quit IRC11:00
*** GB21 has joined #openstack-meeting-411:00
*** hvprash has joined #openstack-meeting-411:02
*** shaohe_feng has quit IRC11:03
*** shaohe_feng has joined #openstack-meeting-411:03
*** hvprash_ has joined #openstack-meeting-411:04
*** amotoki has quit IRC11:06
*** spzala has joined #openstack-meeting-411:07
*** hvprash has quit IRC11:07
*** amotoki has joined #openstack-meeting-411:10
*** spzala has quit IRC11:12
*** shaohe_feng has quit IRC11:13
*** shaohe_feng has joined #openstack-meeting-411:13
*** amotoki has quit IRC11:14
*** dansmith has quit IRC11:14
*** dansmith has joined #openstack-meeting-411:17
*** hvprash_ has quit IRC11:17
*** dansmith is now known as Guest5192611:17
*** julim has joined #openstack-meeting-411:22
*** hvprash has joined #openstack-meeting-411:22
*** shaohe_feng has quit IRC11:23
*** shaohe_feng has joined #openstack-meeting-411:24
*** alexchadin has joined #openstack-meeting-411:24
*** Liuqing has joined #openstack-meeting-411:25
*** salv-orlando has joined #openstack-meeting-411:30
*** shaohe_feng has quit IRC11:33
*** salv-orlando has quit IRC11:35
*** Liuqing has quit IRC11:38
*** shaohe_feng has joined #openstack-meeting-411:38
*** coolsvap has quit IRC11:38
*** Liuqing has joined #openstack-meeting-411:39
*** shaohe_feng has quit IRC11:44
*** shaohe_feng has joined #openstack-meeting-411:44
*** baoli has joined #openstack-meeting-411:46
*** baoli has quit IRC11:46
*** baoli has joined #openstack-meeting-411:47
*** emagana has quit IRC11:47
*** baoli_ has joined #openstack-meeting-411:49
*** baoli has quit IRC11:52
*** shaohe_feng has quit IRC11:54
*** shaohe_feng has joined #openstack-meeting-411:54
*** emagana has joined #openstack-meeting-411:55
*** javeriak has quit IRC11:56
*** ttx has quit IRC11:56
*** alexchadin has quit IRC11:57
*** alexchadin has joined #openstack-meeting-411:58
*** ninag has joined #openstack-meeting-411:59
*** salv-orlando has joined #openstack-meeting-411:59
*** hvprash has quit IRC12:00
*** shaohe_feng has quit IRC12:04
*** shaohe_feng has joined #openstack-meeting-412:05
*** ninag has quit IRC12:05
*** ttx has joined #openstack-meeting-412:07
*** spzala has joined #openstack-meeting-412:08
*** bobh has joined #openstack-meeting-412:11
*** spzala has quit IRC12:12
*** shaohe_feng has quit IRC12:14
*** shaohe_feng has joined #openstack-meeting-412:15
*** ddieterly has joined #openstack-meeting-412:21
*** bobh has quit IRC12:22
*** javeriak has joined #openstack-meeting-412:23
*** shaohe_feng has quit IRC12:25
*** shaohe_feng has joined #openstack-meeting-412:25
*** julim has quit IRC12:28
*** ddieterly is now known as ddieterly[away]12:30
*** GB21 has quit IRC12:31
*** shaohe_feng has quit IRC12:35
*** javeriak has quit IRC12:35
*** shaohe_feng has joined #openstack-meeting-412:35
*** ninag has joined #openstack-meeting-412:38
*** alexchadin has quit IRC12:38
*** ninag has quit IRC12:38
*** ninag has joined #openstack-meeting-412:38
*** alexchadin has joined #openstack-meeting-412:41
*** shaohe_feng has quit IRC12:45
*** shaohe_feng has joined #openstack-meeting-412:46
*** andymaier has joined #openstack-meeting-412:47
*** nmadhok has joined #openstack-meeting-412:49
*** andymaier has quit IRC12:49
*** dixiaoli has quit IRC12:51
*** ddieterly[away] is now known as ddieterly12:54
*** reedip__ has joined #openstack-meeting-412:55
*** shaohe_feng has quit IRC12:55
*** shaohe_feng has joined #openstack-meeting-412:55
*** julim has joined #openstack-meeting-412:57
*** ddieterly has quit IRC12:59
*** pcaruana|afk| is now known as pcaruana13:01
*** chem has joined #openstack-meeting-413:01
*** sbezverk has quit IRC13:01
*** prithiv has joined #openstack-meeting-413:02
*** prithiv has quit IRC13:02
*** sbezverk has joined #openstack-meeting-413:02
*** shaohe_feng has quit IRC13:06
*** shaohe_feng has joined #openstack-meeting-413:06
*** andymaier has joined #openstack-meeting-413:06
*** spzala has joined #openstack-meeting-413:09
*** itisha has quit IRC13:09
*** spzala has quit IRC13:13
*** anilvenkata has quit IRC13:14
*** pmesserli has joined #openstack-meeting-413:14
*** pmesserli has quit IRC13:14
*** pmesserli has joined #openstack-meeting-413:15
*** shaohe_feng has quit IRC13:16
*** spzala has joined #openstack-meeting-413:16
*** bobh has joined #openstack-meeting-413:16
*** shaohe_feng has joined #openstack-meeting-413:17
*** javeriak has joined #openstack-meeting-413:17
*** cloudtrainme has joined #openstack-meeting-413:17
*** chem has quit IRC13:19
*** coolsvap has joined #openstack-meeting-413:21
*** chem has joined #openstack-meeting-413:21
*** amotoki has joined #openstack-meeting-413:21
*** klamath has joined #openstack-meeting-413:24
*** dshakhray has quit IRC13:25
*** Guest51926 is now known as dansmith13:26
*** shaohe_feng has quit IRC13:26
*** shaohe_feng has joined #openstack-meeting-413:26
*** dshakhray has joined #openstack-meeting-413:27
*** jichen has quit IRC13:27
*** sigmavirus24_awa is now known as sigmavirus2413:28
*** zeih has quit IRC13:31
*** zeih has joined #openstack-meeting-413:31
*** yamamoto_ has quit IRC13:33
*** ramishra has quit IRC13:35
*** reedip__ has quit IRC13:35
*** ddieterly has joined #openstack-meeting-413:36
*** shaohe_feng has quit IRC13:36
*** shaohe_feng has joined #openstack-meeting-413:37
*** tsymanczyk has joined #openstack-meeting-413:37
*** ramishra has joined #openstack-meeting-413:38
*** hvprash has joined #openstack-meeting-413:42
*** emagana has quit IRC13:43
*** cloudtrainme has quit IRC13:43
*** emagana has joined #openstack-meeting-413:43
*** wanghua has quit IRC13:44
*** shaohe_feng has quit IRC13:47
*** ddieterly is now known as ddieterly[away]13:47
*** javeriak has quit IRC13:47
*** emagana has quit IRC13:48
*** reedip__ has joined #openstack-meeting-413:48
*** shaohe_feng has joined #openstack-meeting-413:50
*** abhishekk has joined #openstack-meeting-413:54
*** raj_singh has left #openstack-meeting-413:55
*** ddieterly[away] is now known as ddieterly13:55
*** bunting has joined #openstack-meeting-413:55
*** andymaier has quit IRC13:56
*** shaohe_feng has quit IRC13:57
*** shaohe_feng has joined #openstack-meeting-413:57
*** mfedosin has joined #openstack-meeting-413:58
*** belmoreira has quit IRC13: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
sigmavirus24o/14:00
nikhil#startmeeting glance14:00
openstackMeeting started Thu May 12 14:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
wxyo/14:00
dshakhrayo/14:00
sigmavirus24o/14:00
hemanthmo/14:00
mfedosino/14:00
rosmaitao/14:00
buntingo/14:01
tsymanczyko\14:01
tsymanczyk\o14:01
abhishekko/14:01
nikhilwelcome everyone14:01
nikhillet's get started14:01
nikhil#topic agenda14:01
flaper87o/14:01
*** openstack changes topic to "agenda (Meeting topic: glance)"14:01
nikhilwe've a few items today, thanks to mfedosin and flaper8714:01
flaper87:D14:01
nikhilI do want to discuss newton specific dates before that14:02
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
flaper87go ahead, I don't think I'll need much time for my items14:02
nikhilfirst things first:14:02
*** nkrinner is now known as nkrinner_afk14:02
flaper87most of them are heads ups14:02
* flaper87 stfu14:02
nikhilflaper87: cool, ty14:02
nikhil#topic Updates14:02
*** openstack changes topic to "Updates (Meeting topic: glance)"14:02
nikhil#info Glare ( mfedosin )14:02
mfedosinokay14:03
mfedosinI'm back from vacation14:03
flaper87mfedosin: welcome back14:03
mfedosinno special activity for Glare was done in last 2 weeks14:03
mfedosinkairat and dshakhray fixed several bugs we had14:04
mfedosinand I updated the spec14:04
nikhilhope you enjoyed14:04
mfedosin#link https://review.openstack.org/#/c/283136/14:04
nikhilok (on the no-activity update)14:04
mfedosinplans to continue the development and implement new features14:05
*** sdake has joined #openstack-meeting-414:05
nikhilmfedosin: ok, it would be nice to discuss the action plan for Glare in the monday's meeting. Also, possible start small discussions on the spec.14:05
mfedosinI got nice feedback on the summit14:05
mfedosinnikhil: yeah14:05
nikhilgreat14:06
nikhilanything else on this today?14:06
mfedosinnope14:06
nikhilty14:06
nikhil#info Nova v1, v2 ( mfedosin , flaper87 , nikhil )14:06
nikhilSo, the spec needs updating, and addressing comments:14:07
nikhil#link https://review.openstack.org/#/c/301741/14:07
*** shaohe_feng has quit IRC14:07
mfedosinkk14:07
flaper87I'm working on getting the gate ready14:07
* flaper87 gets link14:07
*** shaohe_feng has joined #openstack-meeting-414:08
nikhilLook at the summary recap from Matt:14:08
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094380.html14:08
flaper87#link https://review.openstack.org/#/c/315190/14:08
flaper87That should allow us to use either version of the API in the gate14:08
flaper87Nova gets the version from the `/versions` endpoint14:08
mfedosinnumber of comments soon will exceed the number of lines there14:08
flaper87mfedosin: LOL14:08
*** fwdit has quit IRC14:08
nikhilThanks flaper8714:08
nikhilmfedosin: you bet14:09
nikhilflaper87 is working on disabling the v1 by default to that the gate can run on simply v214:09
nikhilflaper87: no, the plan is for nova to have a top level config that will allow them to run either v1 or v214:09
flaper87I think we'll end up with 1 new v1-only job that we'll get rid of in the future.14:09
flaper87nikhil: yeah, I meant to say it does check `/versions` now14:10
*** emagana has joined #openstack-meeting-414:10
nikhil#info the version discovery support has been cancelled14:10
flaper87IIRC14:10
nikhilflaper87: ok, cool14:10
flaper87whenever that config is added, we'll update devstack14:10
mfedosinalso we have to add removing version discoverability in working items for the spec14:10
nikhilmfedosin: so when this gate is enabled to run just v2, we will know what all drivers/pieces of code fail with v214:11
*** emagana has quit IRC14:11
*** emagana has joined #openstack-meeting-414:11
flaper87yup, I'll add it as a non-voting gate14:11
nikhilwe need to come to an eventual green gate for v2 when the config in nova will be removed and it will be safe to deprecate glance v114:11
nikhilmfedosin: yes14:11
flaper87we'll switch to using v2 as default in the other gates as soon as we're confident enough it won't break14:11
* flaper87 stops spamming14:12
nikhilflaper87: thanks, that's useful too.14:12
mfedosinflaper87: thanks Flavio14:12
nikhillet's keep a weekly sync on #openstack-glance for nova work too.14:12
nikhilmoving on if we're done here14:12
nikhil#topic Cross Prj14:13
*** openstack changes topic to "Cross Prj (Meeting topic: glance)"14:13
nikhilthe CP meetings have become ad-hoc only14:13
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094443.html14:13
*** rbak has joined #openstack-meeting-414:13
nikhilif anyone wishes to start a CP effort, they will need to act accordingly14:14
nikhil#topic Announcements14:14
*** openstack changes topic to "Announcements (Meeting topic: glance)"14:14
*** d0ugal has quit IRC14:14
nikhilI sent out the Newton priorities, processes, etc. email14:15
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094780.html14:15
*** emagana has quit IRC14:15
nikhilWanted to ensure everyone was particularly aware about the dates.14:15
*** sbezverk_ has joined #openstack-meeting-414:15
*** emagana has joined #openstack-meeting-414:16
*** d0ugal has joined #openstack-meeting-414:16
* flaper87 hasn't read that email yet14:16
nikhilWe are being very strict on accepting any more specs this cycle, the justification comes in the reviewer bandwidth section.14:16
flaper87I'll catch up and reply to the thread14:16
nikhilAll the necessary commits to glance-specs, glance docs, releases will be done.14:16
*** vikram_ has joined #openstack-meeting-414:16
*** sbezverk has quit IRC14:17
*** zeih has quit IRC14:17
nikhilFeel free to reach out to me with any questions/concerns or ML works.14:17
*** shaohe_feng has quit IRC14:17
flaper87Last cycle, we tried to focus reviews on specific parts of glance depending on the milestones14:17
flaper87I think we should do the same this time around14:18
flaper87it helped with the shortage of reviewers14:18
flaper87For example, we focused a lot on specs rather than doing code reviews at the beginning14:18
flaper87then we started switching progressively to code14:18
*** shaohe_feng has joined #openstack-meeting-414:18
flaper87mostly specs14:18
flaper87and then progressively to bugs14:18
nikhil++ to focus on specs14:18
flaper87and then FF, RCs, etc14:18
* sigmavirus24 wasn't around last cycle but this sounds like a solid idea14:18
nikhilthe the dates have been designed for that purpose too.14:19
flaper87I didn't made that public but I basically silently transitioned everyone towards the reviews we needed14:19
* rosmaita is glad sigmavirus24 is around for this cycle14:19
flaper87SorryNotSorry :P14:19
mfedosinsigmavirus24: we missed you14:19
* flaper87 is not sure if people noticed that14:19
flaper87sigmavirus24: <314:19
nikhilI do not want to enforce business from not getting important bugs fixed early in the cycle but the focus needs to be on the specs.14:19
sigmavirus24rosmaita: that's not guaranteed but I'm going to try to swindle some review time14:20
nikhilthe assignment of the cores on the spec is another important factor for understanding if a spec can move in relatively decent pace or we need to think of alternate mechanisms.14:20
nikhilLet's all follow the process completely and see if it works, I will gather feedback in a couple of weeks.14:21
*** spotz_zzz is now known as spotz14:21
nikhilAn individual already reachout out to me to see if lite-specs will require cores associated.14:21
nikhilreached*14:21
nikhilI think this will help keep focus and good pace. Also, it's easier to work with distributed and flexibly structured team.14:22
nikhilAnyway, the practicality of all this will be known within a few days of adoption.14:23
*** d0ugal has quit IRC14:23
nikhilThanks all for the great input.14:23
nikhilmoving on14:23
nikhil#topic Glance v2 transaction layer (dshakhray, mfedosin)14:23
*** openstack changes topic to "Glance v2 transaction layer (dshakhray, mfedosin) (Meeting topic: glance)"14:23
mfedosindshakhray: can you find the links?14:23
dshakhrayhttps://review.openstack.org/#/c/272118/14:24
*** flaper87 has quit IRC14:24
dshakhrayspec https://review.openstack.org/#/c/315483/14:24
mfedosinso, in short we have an old issue in glance v214:24
*** user154752_ has joined #openstack-meeting-414:24
mfedosinwhen we update an image we rewrite all data in db14:24
mfedosinit leads to 1. race conditions, 2. increased burden on db14:25
mfedosinit's not seen when load is low14:25
*** sudipto has joined #openstack-meeting-414:25
mfedosinbut on high-load deployments we saw these issues14:26
mfedosinso, Darja's work is about to fix it14:26
*** user154752 has quit IRC14:26
*** spotz is now known as spotz_zzz14:26
nikhilok, so we just need reviews?14:27
*** flaper87 has joined #openstack-meeting-414:27
*** flaper87 has quit IRC14:27
*** flaper87 has joined #openstack-meeting-414:27
mfedosinthe idea is to add transaction layer in domain model that will compare image after and before db layer14:27
flaper87!ping14:27
openstackpong14:27
flaper87crap, I got disconnected14:27
flaper87sorry about that14:27
mfedosinand save only modified attributes14:27
*** shaohe_feng has quit IRC14:28
flaper87:/14:28
mfedosinyeah, we need reviews14:28
mfedosintest coverage is really good there14:28
nikhilmfedosin: correct, I had done a brief review on this.14:28
nikhilok, I guess we need to review the spec first.14:29
jokke_o/14:29
mfedosinperformance testing results will be done soon14:29
jokke_sorry, late14:29
dshakhrayI spent performance testing with a small number of requests14:29
dshakhrayresult http://pixs.ru/showimage/yotxru2png_8513882_21907859.png14:30
dshakhrayblue line - old code14:30
dshakhrayred line - with transaction layer14:30
nikhildshakhray: english please :)14:30
mfedosindshakhray: cool :)14:30
nikhilI got the numbers but not what they represent.14:31
mfedosinnikhil: I understand her ;)14:31
dshakhraysorry for my english : (14:31
flaper87dshakhray: he meant on the graph14:31
mfedosinwe'll talk later about performance testing :)14:31
nikhil#action glance-cores: review spec  https://review.openstack.org/#/c/315483/14:31
flaper87:)14:31
flaper87your english is great14:32
*** zeih has joined #openstack-meeting-414:32
nikhildshakhray: indeed, it's good.14:32
*** shaohe_feng has joined #openstack-meeting-414:32
nikhildshakhray: please refer a graph that will help us collaboratively provide input.14:32
*** reedip__ has quit IRC14:32
nikhilanything else on this topic?14:33
mfedosinwe can continue this discussion in the spec comments14:33
nikhilthanks14:33
nikhilmoving on14:33
nikhil#topic Glance Registry deprecation (flaper87)14:33
*** openstack changes topic to "Glance Registry deprecation (flaper87) (Meeting topic: glance)"14:33
*** yamamoto_ has joined #openstack-meeting-414:33
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094773.html14:34
flaper87So, this was discussed at the summit to some extent but it needs more "talking"14:34
flaper87I've sent out that email to kick off the discussion and, hopefully, get feedback from OPs14:34
flaper87(and anyone, really)14:34
flaper87SOOOOO, if you have anything to say on this, please do14:34
nikhilflaper87: for some reason (either this has not reached my inbox or got filtered to an unknown place)14:35
flaper87The feedback so far has been that it might not be actually needed. Except from 1 person (IIRC) that mentioned it's important for them14:35
flaper87nikhil: I cross-posted it in dev and ops14:35
flaper87mmh14:35
*** sdake has quit IRC14:35
flaper87perhaps you have it in one of those folders ?14:35
nikhilflaper87: ok thanks.14:35
flaper87that's it14:36
nikhilI will try to find it and respond.14:36
flaper87I don't mean to use the meeting to discuss that at this point14:36
*** alexchadin has quit IRC14:36
flaper87I'll bring this topic up again when we have more "data"14:36
nikhilYes, we also need to research on rolling upgrades that is related to this.14:36
*** GB21 has joined #openstack-meeting-414:36
nikhilmoving on14:37
mfedosincan they describe how they use registry?14:37
flaper87mfedosin: hope to get that info in this thread14:37
flaper87nikhil: I need to double check the relation between the registry deprecation and rolling upgrades14:37
flaper87I'll sync with rosmaita14:37
rosmaitaflaper87: we should reach out to that guy from australia, he always shows up at the glance ops sessions14:37
flaper87It's not clear to me why this depends on rolling upgrades anymore14:37
flaper87rosmaita: I don't know his name/company :(14:38
*** shaohe_feng has quit IRC14:38
flaper87Was e from AU or NZ ?14:38
nikhilyes, sync with rolling upgrades researchers14:38
jokke_flaper87: I think it's almost other way around ... rolling upgrades depends on this ;)14:38
nikhilmfedosin: flaper87 : https://review.openstack.org/#/c/268865/14:38
flaper87jokke_: still, no idea why14:38
nikhillook at the bug associated to know how they use it14:38
nikhilthe bug is actually a lite-spec14:38
rosmaitaflaper87: i think i can track him down14:39
flaper87rosmaita: please, thanks :)14:39
flaper87point him to the thread14:39
flaper87ok, that's all from me on this topic at this point14:39
nikhilflaper87 rosmaita: Jake Yip (look at the link)14:39
flaper87nikhil: thanks14:39
nikhil#topic Deprecate `show_multiple_locations`14:39
*** openstack changes topic to "Deprecate `show_multiple_locations` (Meeting topic: glance)"14:39
nikhil    https://review.openstack.org/#/c/313936/14:40
nikhil#link https://review.openstack.org/#/c/313936/14:40
nikhilflaper87: that's you again, I think14:40
flaper87I published this draft to kick of a public discussion on this topic14:40
flaper87I believe we should get rid of that option and manage locations using policies14:40
mfedosinit was kairat dream :)14:40
flaper87Stuart is on the side that having a way to turn this off is good14:40
*** myatsenko has quit IRC14:41
*** shaohe_feng has joined #openstack-meeting-414:41
flaper87so, before I go and start fixing all the gate issues related to this, I wanted to get people's thoughts14:41
nikhilwell, I linked it to the Nova spec.14:41
jokke_flaper87: so what's the benefit of moving that from one config file to multiple options on the other?14:41
flaper87It'd be cool to get +1/-1 on the idea14:41
flaper87jokke_: you already have all of that ;)14:41
nikhilthere are some outstanding questions on the Nova side that we need to see the effect on.14:41
flaper87you need to have all the policies and that config option14:41
*** raddaoui has joined #openstack-meeting-414:41
nikhilflaper87: man, I would probably introduce a few more config options just to make it hard to use it14:42
*** GB21 has quit IRC14:42
flaper87nikhil: lol14:42
flaper87That's a different discussion that I'd also be happy to have14:42
jokke_nikhil: that would fit perfectly to the current trend of glance14:42
flaper87When this option was added, we didn't have the granularity in the policy.json file14:43
flaper87it was then added and the option was kept14:43
*** yamamoto_ has quit IRC14:43
flaper87I think removing the policies around this would be a step backwards, hence the proposal to remove the other option14:43
sigmavirus24there's lots of python enforcing admin-only-ness of things that are also in the policy.json file14:43
nikhilI would make the policies as admin by default and yet keep the config option14:44
flaper87I wish we had another known role for services so that I could make this non-admin only14:44
sigmavirus24nikhil: I think the option should be deprecated though14:44
rosmaitaflaper87: i am in favor of killing option and using policy instead14:44
nikhilsigmavirus24: having policy control is not very descriptive14:44
nikhilfor example: with hemanthm 's changes we can define it to be an advanced option14:44
flaper87I just don't see the point of having it if we're already enforcing it elsewhere and returning better HTTP codes on that path14:45
nikhiland that way, people know to not use it14:45
*** galstrom_zzz is now known as galstrom14:45
nikhilthere's no technical reason to keep it14:45
flaper87nikhil: are you suggesting switching it to True by default and the policies to admin ?14:45
jokke_flaper87: so only problem I have with that is the read side14:45
nikhilbut there's operational one14:45
nikhilflaper87: no, both off by default (False and admin)14:45
jokke_of we currently have policy preventing something, we return apropriate code and tell the user that  it was prevented14:45
flaper87FWIW, I think setting options in a config file is not a problem anymore for OPs.14:46
* flaper87 waits for OPs to kill him14:46
nikhilflaper87: "only trusted deployments with admins are encouraged to use that config option"14:46
nikhil"with advanced admins"14:46
flaper87nikhil: but again, we have 4 options to do the same14:46
flaper871 global and 3 granular options14:46
nikhilyes, and that is exactly what I feel we need to make people not use it14:46
flaper87I don't see the point of the config option except for having 1 key to turn on/off this thing14:47
jokke_of we move the locations under policies we really can't do that and tell the user that they can't have details of their image because policy prevents them seeing locations and on the other hand if we just hide it we are inconsistent with the rest of the policies14:47
nikhilotherwise, it's a simple policy change for whoever wants read, write or delete.14:47
flaper87I think adding more config options is the wrong way to communicate something shouldn't be used. Really.14:48
jokke_s/of/if/14:48
flaper87or at least in this case14:48
jokke_flaper87: ++14:48
mfedosinbtw, if we have several locations and show_direct_url is enabled, then glance shows only the first one?14:48
nikhilflaper87: the point isn't clear yet. I want the categorization effort to hide this config option very similar to the social networks hide your privacy settings.14:48
*** shaohe_feng has quit IRC14:48
*** shaohe_feng has joined #openstack-meeting-414:48
flaper87I want this config option gone14:48
jokke_if we take that stand, we're sending pretty clear message that Glance shouldn't be used :P14:48
flaper87like, BOOOM14:48
rosmaitamfedosin: yes, there is some kind of weird interaction between multiple loc and direct url14:48
rosmaitaunfortunately, i can't remember what it is!14:49
nikhilmfedosin: yes (as per the default location strategy)14:49
mfedosinmaybe we should deprecate this one as well?14:49
mfedosinbecause it may confuse users14:49
flaper87So, let's do this. Let's give ppl some time to think this through and vote next week14:49
flaper87thoughts?14:49
flaper87please, comment on the review14:49
nikhilThanks!14:50
mfedosinI vote for deprecation14:50
flaper87mfedosin: <314:50
tsymanczykdeprecation14:50
nikhilI vote for deprecation of multiple-locations.14:50
mfedosin(feels like I vote for Trump)14:50
flaper87mfedosin: tsymanczyk put all that on the review, please14:50
flaper87mfedosin: not the trump part14:50
flaper87:P14:50
nikhilmoving on14:50
jokke_mfedosin: but That IS good thing :P14:50
nikhil#topic Deprecate `/file` endpoint14:50
*** openstack changes topic to "Deprecate `/file` endpoint (Meeting topic: glance)"14:50
jokke_easy, No can do14:51
rosmaitamfedosin: make glance great again!14:51
nikhil    #link https://review.openstack.org/#/c/313947/14:51
* sigmavirus24 slaps rosmaita's wrist with a ruler14:51
flaper87ok, as promissed, I amended the original spec to reflect we're not remiving the `/file` endpoint14:51
sigmavirus24stop that rosmaita14:51
mfedosinI vote against this time14:51
flaper87There's a comment from jokke_ on why we shouldn't make it admin only14:51
*** tonytan4ever has joined #openstack-meeting-414:51
flaper87removing, even.14:51
flaper87Wait, the title of the IRC topic is misleading14:52
flaper87go and read the spec14:52
flaper87:P14:52
nikhilso, I will need to consider this carefully.14:52
flaper87The spec actually says: Don't deprecate14:52
jokke_nikhil: no you don't we just can't do it14:52
nikhilFor Nova we need this enabled by default in devstack/gate.14:52
flaper87Now, I'm on the side this should be admin only for the lack of a better role to have there14:53
nikhiljokke_: correct, I need to think for all the reasons why not so that we don't discuss this again :)14:53
flaper87The reasons I don't think we should have this open are the same reasons we've expressed in the import spec14:53
jokke_nova and Cinder are relying on it and good luck convincing them to change that now after all this v2 hassle14:53
flaper87We want to move away from this endpoint as a public endpoint14:53
flaper87users *must* use the new workflow14:53
nikhilNo, it has been agreed that Nova will use this endpoint14:53
flaper87whereas internal services can use the old one14:53
jokke_flaper87: unfortunately we do not have ways to do that reasonably either14:54
nikhilNow, flaper87 needs to chat with the Service Catalog TNG folks to determine if this is even a possiblity14:54
flaper87nikhil: what?14:54
* flaper87 just realized he needs to talk to the Service Catalog TNG team14:54
flaper87:P14:54
nikhilflaper87: the summit discussion did not clarify if we will differentiate between public and private glance installations.14:54
flaper87jokke_: right, #sadpanda14:54
nikhiland people are generally against that idea14:55
jokke_only way to do this is to deploy specific public nodes and prevent using /file in policy14:55
nikhil(because it doesn't make sense for small scale clouds)14:55
* rosmaita is confused and scared by the Service Catalog TNG14:55
flaper87well, you can't tell people how to deploy their stuff. Glance not differentiating public/private doesn't mean others won't14:55
nikhilrosmaita: yep, me too.14:55
flaper87jokke_: that's the way people are deploying glance today, AFAIK14:55
jokke_flaper87: correct14:55
flaper87jokke_: which is why I went ahead and proposed making it admin only14:55
flaper87since you can open it internally14:56
nikhilyes, but we need to start thinking of what comes out of a devstack pull.14:56
flaper87sorry, too many different convos in parallel14:56
nikhilsorry, we're running out of time14:56
nikhilneed to discuss this later14:56
jokke_flaper87: and small deployments hates it because they need the resources to run those nodes even they don't need the capacity for it14:56
flaper87Again, folks, please, comment on the spec14:56
flaper87This is an important change14:56
nikhil#topic Refactor glance_store public API14:56
*** openstack changes topic to "Refactor glance_store public API (Meeting topic: glance)"14:56
nikhil#link https://review.openstack.org/#/c/315025/14:56
nikhilflaper87: you have 1 min14:57
nikhil:)14:57
flaper87Again, as promissed, I got my stuff done! :)14:57
flaper87go and review the spec14:57
flaper87period14:57
flaper87actually, +2A and we're good14:57
flaper87I'll buy beers for everyone14:57
jokke_;)14:57
*** TravT has joined #openstack-meeting-414:57
* flaper87 is on top of his s@$#@$@ today14:57
* flaper87 is done14:58
nikhilI almost feel we need to have spec related syncs14:58
flaper87thanks for listening14:58
nikhilanyway, thanks flaper8714:58
nikhil#topic open discussion14:58
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:58
*** woodard has joined #openstack-meeting-414:58
*** woodard has quit IRC14:58
nikhil90 seconds14:58
flaper87nikhil: no, please, no other meetings/syncs :D14:58
*** hvprash_ has joined #openstack-meeting-414:58
*** shaohe_feng has quit IRC14:58
mfedosinflaper87: I like this spec14:58
flaper87mfedosin: w000h00014:58
mfedosinand will review it14:58
nikhilflaper87: yeah, there's no plan. But I will ping people ad-hoc for syncs.14:58
hemanthmneed help with improving the help text14:58
flaper87mfedosin: thanks14:58
*** cwolferh has joined #openstack-meeting-414:59
tsymanczykad hoc syncs at least, yes please.14:59
*** woodard has joined #openstack-meeting-414:59
*** iyamahat has joined #openstack-meeting-414:59
nikhilso, from next week onward14:59
tsymanczyksometimes i worry that i'm off in the weeds. cannot be the only one.14:59
hemanthmhere are the options https://etherpad.openstack.org/p/improving-glance-config-opts (please feel free to pick up a few of them you are comfortable with)14:59
*** shaohe_feng has joined #openstack-meeting-414:59
nikhilwe will limit the agenda to 4 items + open discussion (and updates)14:59
*** lei-zh has joined #openstack-meeting-414:59
*** yingjun has joined #openstack-meeting-415:00
nikhilyou need to post the agenda by Wednesday 2100 UTC to get it approved for the Thurs meeting15:00
nikhilThanks all!15:00
nikhil#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
*** matt-borland has joined #openstack-meeting-415:00
openstackMeeting ended Thu May 12 15:00:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
*** zeih has quit IRC15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-12-14.00.html15:00
*** sjmc7 has joined #openstack-meeting-415:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-12-14.00.txt15:00
matt-borlando/15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-12-14.00.log.html15:00
TravT#startmeeting openstack search15:01
openstackMeeting started Thu May 12 15:01:22 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
*** bunting has left #openstack-meeting-415:01
TravTo/15:01
yingjuno/15:01
rosmaitao/15:01
lei-zho/15:01
sjmc7ello15:02
*** hvprash has quit IRC15:02
*** thorst_ has joined #openstack-meeting-415:02
TravThello everybody!15:02
*** lakshmiS_ has joined #openstack-meeting-415:02
TravTso meeting agenda is here15:02
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:02
*** sbezverk_ has quit IRC15:02
TravTplease add anything you see fit15:02
lakshmiS_o/15:02
*** sbezverk has joined #openstack-meeting-415:02
*** Liuqing has quit IRC15:03
TravTi'm going to skip the first topic and come back to it, because i don't see tyr yet15:03
*** tsymanczyk has left #openstack-meeting-415:03
TravT#topic versioned notifications15:03
*** openstack changes topic to "versioned notifications (Meeting topic: openstack search)"15:03
*** sbezverk_ has joined #openstack-meeting-415:03
TravTSo, we brought it up a bit last week15:04
TravThttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093962.html15:04
TravTin the context of the nova v2 cells announcement that they were going to look into searchlight for multi-cell deployments15:04
TravTi spent some time going through the specs15:04
TravTand chatted a bit with sjmc715:04
sjmc7i was honored15:05
*** ddieterly is now known as ddieterly[away]15:05
TravTi'll just share a few thoughts and then maybe yingjun also had some time15:05
*** ddieterly[away] is now known as ddieterly15:05
TravTto look over things15:05
*** ddieterly is now known as ddieterly[away]15:05
TravTanyway, it seems that versioned notifications will certainly help with being able to tell when notification payloads change15:05
TravTbut they don't necessarily guarantee we'll get all the data15:06
*** ddieterly[away] is now known as ddieterly15:06
sjmc7well, that depends what they decide to do :)15:06
sjmc7or have they made a decision?15:06
TravTspec is still unchanged15:06
TravTstill has a few -1's15:06
TravTi went to what I thought would be the meeting time this week15:06
TravTbut nobody appeared15:07
*** sbezverk has quit IRC15:07
TravTso maybe they are still doing in every two weeks15:07
*** sbezverk_ has quit IRC15:07
sjmc7so there actually is a chance it’ll make things worse than now if they become just a delta15:07
TravTsjmc7 do you want to explain that a bit for everybody here15:08
sjmc7right now notification payloads are mostly identical indepdenent of the event15:08
sjmc7and they contain a (mostly) full representation of the instance15:08
*** shaohe_feng has quit IRC15:09
sjmc7there is some talk of moving to sending payloads that are deltas of what the event changed15:09
sjmc7since elasticsearch has no ‘update’ mechanism per se, it’s a bit more work for us to do that (though not insurmountable)15:09
*** shaohe_feng has joined #openstack-meeting-415:09
sjmc7but it increases the risk of dangerous race conditions15:09
sjmc7because we can no longer ignore notifications older than the record we have stored15:10
sjmc7right now it’s moot since we hit nova’s API but we really need to stop doing that if possible15:10
sjmc7i’m done explaining15:11
TravTsjmc7: i'm not sure exactly where is the best place to leave those comments, but maybe you could just add them to this spec in the comments so they are captured somewhere15:11
TravThttps://review.openstack.org/#/c/286675/15:11
*** sbezverk has joined #openstack-meeting-415:11
sjmc7yeah, will do15:11
sjmc7it’s not clear what the motiviation for making the versioned change is (i.e. the specific use cases)15:12
sjmc7so we’ll see how much influence we have15:12
*** coolsvap has quit IRC15:12
TravTso, the main motivation as i understand it is so that consumers know when the payload changes15:12
TravTeg. version 1.0 of notification to version 1.1 to 2.015:12
sjmc7which consumers though?15:13
sjmc7i get the overall reasoning, i’m just not sure what drives specific decisions15:13
TravTthat is unclear and is part of the spirit of the notes i left on the spec15:13
sjmc7but i guess we’ll find out15:13
sjmc7the advantage of it all though is that they can potentially add info to payloads15:14
TravTyes.15:14
sjmc7which might let us stop mashing at nova’s api15:14
TravTso, sjmc7 and i were thinking that we should do the following in newton15:14
sjmc7interestingly, one counter argument was that it would actually be better if services could query nova’s api more cheaply and do exactly what we do now15:14
TravT1) update our callbacks and mapping to nova to request the latest version15:15
TravT2) https://blueprints.launchpad.net/searchlight/+spec/nova-optionally-disable-some-events15:15
TravT3) keep working on versioned notification with the nova team as consumers, but since we can't count on them 100% do 1) & 2)15:16
*** yamahata has joined #openstack-meeting-415:16
TravTthoughts? (hope we didn't suck the oxygen out of the room)15:16
sjmc7breathe!15:17
*** sdake has joined #openstack-meeting-415:17
rosmaitai got nothin'15:17
TravTrosmaita coffee running low today? ;)15:17
*** d0ugal has joined #openstack-meeting-415:17
rosmaitaTravT: just one large this morning, guess that's the problem15:18
* rosmaita needs another coffee with extra oxygen15:18
TravTwell, i know we just threw a lot of info out there15:18
*** shakamunyi has quit IRC15:19
*** shaohe_feng has quit IRC15:19
TravTwe can come back to this if others have more thoughts.15:19
TravT#topic backport 0.2.115:19
*** openstack changes topic to "backport 0.2.1 (Meeting topic: openstack search)"15:19
TravTstill wanting to finish out items so we can tag stable/mitaka15:19
*** shaohe_feng has joined #openstack-meeting-415:20
TravTdefinite ones are bugs relates to ES 2.015:20
TravTi believe this is the last one for the service: https://review.openstack.org/#/c/311834/15:20
sjmc7gonna look at it again today. it was more complicated than i initially thought15:21
TravTokay15:21
TravTcan you also cherry pick this one to stable/mitaka: https://review.openstack.org/#/c/307504/15:21
TravT?15:21
*** vikram_ has left #openstack-meeting-415:21
sjmc7yeah. looks like there’s a merge conflict but i’ll do it after this15:22
TravTsjmc7: i think backporting the nova spec could be a follow on backport15:22
TravThttps://review.openstack.org/#/c/307504/15:22
TravToops15:22
TravT https://blueprints.launchpad.net/searchlight/+spec/nova-optionally-disable-some-events15:22
TravTfor a different release tag15:22
sjmc7yeah, that’s fine. we’re not really meant to backport features, though this one’s kind of a bug-ture15:22
TravTyeah, it could perhaps be considered a scalability bug...15:23
*** regXboi has joined #openstack-meeting-415:23
TravTok, still not tyr or david-lyle it looks like, so will come back to the searchlight ui topic15:23
TravTlooks like rosmaita topic is next15:23
david-lyleTravT: I'm here15:24
TravThey david-lyle15:24
david-lylejust reading along15:24
TravTokay15:24
TravT#topic upcoming changes to glance that will affect the searchlight plugin15:24
*** openstack changes topic to "upcoming changes to glance that will affect the searchlight plugin (Meeting topic: openstack search)"15:24
TravTrosmaita: ^15:24
rosmaitaok15:24
rosmaitathe change is that there will be more image 'visibility' values15:24
sjmc7we like a challenge :)15:25
rosmaitaand the community scheme will allow people to create quasi-public images15:25
rosmaitaanyone can use them15:25
rosmaitabut they only appear in your image-list if you "bookmark" them15:25
rosmaitaby using the member-list thing we already use for 'shared' images15:25
rosmaitaand 'shared' will become an actual visibility15:25
rosmaitaand after that, there's a push for what i'm calling 'protected' images15:26
rosmaita(though there will be bikeshedding over the name)15:26
rosmaitathese will be images that appear in the default image-list of descendant tenants in the keystone hierarchical tenancy scam15:26
rosmaitai mean 'scheme'15:27
sjmc7hahahaha15:27
TravTlol15:27
sjmc7tip your waiter!15:27
rosmaitaso, it occurs to me that that is a lot of logic to be duplicating into the searchlight plugin15:27
sjmc7yeah :(15:27
david-lylestill don't understand why HMT won't die15:27
rosmaitaand also, i wonder whether there is any thing we can do in glance to make this easier for indexing15:27
sjmc7as long as we know what it is towards the end of a release, it’s not a huge deal15:27
TravTcommunity concept didn't initially freak me out (maybe it should), but that second one scares me15:28
sjmc7the big concern is that we are never more permissive than glance15:28
rosmaitaright15:28
rosmaitaanyway, i wanted to put this on people's radar15:28
sjmc7yeah, thanks. are there specs/bps for this?15:28
TravThttps://review.openstack.org/#/c/271019/15:28
rosmaitaon the agenda15:28
TravTso rosmaita, shared will actually be a value now?15:29
sjmc7ah! splendid15:29
*** coolsvap has joined #openstack-meeting-415:29
rosmaitaTravT: yes15:29
*** shaohe_feng has quit IRC15:29
*** shaohe_feng has joined #openstack-meeting-415:29
TravTand all deployments will get this by default?15:29
TravTfor v2?15:30
rosmaitawell, it will be in newton (if the spec is approved)15:30
*** hvprash has joined #openstack-meeting-415:30
* rosmaita has 50 windows open and can't find the relevant ones15:30
TravTcommunity sounds pretty easy15:30
rosmaitahere's the community spec, close to approval: https://review.openstack.org/#/c/271019/15:31
TravTthe diff between get by ID actually is a new use case...15:31
TravT:-S15:31
*** trozet has joined #openstack-meeting-415:32
rosmaitathe multitenancy stuff is discussed here, though it's preliminary: https://etherpad.openstack.org/p/newton-image-visibility-changes15:32
TravTbasically, community is "if i know the ID of it, I can get it directly".  "If i'm added as a member to it, I can list it"15:32
TravTrosmaita: ? ^15:32
rosmaitaTravT: yes, plus you can discover community images15:32
rosmaitaGET v2/images?visibility=community15:33
TravThow do you discover them?15:33
rosmaitaand the listing is subject to the member_status==accepted, just like shared images15:33
*** hvprash_ has quit IRC15:34
*** armax has joined #openstack-meeting-415:34
*** spzala has quit IRC15:34
rosmaitaanyway, just wanted to request a quick look-over if y'all have some free time, just to point out if we're proposing anything insane15:35
TravTthanks!15:35
sjmc7as long as we can translate the api to filters we’re good15:35
TravTwhat's the probability of all this making it into newton?15:36
*** doonhammer has joined #openstack-meeting-415:36
TravTfrom a glance perspective15:36
TravTrosmaita would you mind opening a searchlight BP for each of these?15:36
rosmaitayou make it sound so easy15:37
TravT:)15:37
TravThttps://blueprints.launchpad.net/searchlight/+addspec15:37
TravT;)15:37
rosmaitasorry, that comment was addressed to sjmc715:37
rosmaitabut sure, i can open a bp15:37
sjmc7:)15:37
rosmaitafor each15:37
rosmaitacommunity should make it into newton15:38
TravTeverything is easy for sjmc7... at least he makes it look that way15:38
sjmc7i’m actually juggling plates right now15:38
TravTokay, next topic15:39
TravTwas hoping tyr might show up15:39
rosmaitanikhil has 'image sharing changes' as a priority for newton, that will def include the community spec, possibly the hierarchical15:39
rosmaita(sorry, i have severe typing lag today)15:39
*** shaohe_feng has quit IRC15:39
nikhil++15:39
TravTokay cool15:40
TravTrosmaita all done with this topic for now?15:40
*** shaohe_feng has joined #openstack-meeting-415:40
rosmaitayep15:40
TravT#topic Searchlight UI as top level Dashboard instead of panel15:41
*** openstack changes topic to "Searchlight UI as top level Dashboard instead of panel (Meeting topic: openstack search)"15:41
* sjmc7 puts on helmet15:41
TravTtyr isn't here, but we have matt-borland and david-lyle15:41
matt-borlando/15:41
TravTi took a screenshot http://imgur.com/a/p7dmB15:41
TravTbasically right now, the SL ui is a panel under the "Project" dashboard15:41
TravTtyr has a patch up to move it into its own dashboard15:42
TravThttps://review.openstack.org/#/c/313666/15:42
TravTright now, you can already check an option to search across projects from the SL dashboard (if you are admin)15:42
*** azbiswas has joined #openstack-meeting-415:42
TravTand with yingjun's latest patch merging (hypervisors), SL now also has data that is admin only and only shown to admins15:43
TravTdavid-lyle had some comments on the patch above^15:43
* david-lyle looking for trouble 15:44
TravTso, just wanted to open this up for any additional discussion15:44
david-lyleI just wanted to point out that mixing admin and owner roles can be confusing to users as well as complicate the action invocation15:44
sjmc7i’m not a huge fan of it15:44
sjmc7from a consistency standpoint i think it makes more sense to make it available from Project and Admin15:45
sjmc7for pretty much the same reasons as david-lyle15:45
matt-borlandsjmc7, does that basically mean that scope is limited to project when within 'project', and across projects when in 'admin'?15:46
sjmc7i think the usage is likely to be quite different in those two contexts15:46
sjmc7yeah15:46
sjmc7it would also allow us to potentially define changes in behavior in the two contexts15:46
david-lylean admin very rarely wants to do more than observe unless cleaning up a problem15:46
david-lylewhere as an admin acting on their own project will make changes freely15:47
matt-borlandI think that although it seems strange from a dev's perspective, 2 searches makes more sense from an implementation/use perspective15:47
*** azbiswas has quit IRC15:47
david-lylethe line of ownership gets blurry15:47
matt-borlandalso is becomes really unclear how/when you can perform actions on the project side15:48
TravTso, david-lyle we have also talked about top-nav search (a searchbar from top nav).  if a user clicked into that, wouldn't that face a similar problem.15:48
matt-borland(when you lump everything together across projects)15:48
sjmc7two searches also allow us to e.g. change default columns without it looking weird15:48
sjmc7the top search wouldn’t have actions in the same way, at least in the incarnation we showed in vancouver15:48
david-lyleTravT: yes and no, depending on whether you expose the actions or redirect15:48
TravTbut would you link them into projects or into admin15:48
david-lyleyes15:48
david-lylethere is some UX needed to make that choice clear15:49
*** GB21 has joined #openstack-meeting-415:49
*** matrohon has quit IRC15:49
sjmc7off the top of my head i’d defauit top search to all but make it clear in results which ones were in your current project15:49
david-lylesjmc7: ++15:49
*** shaohe_feng has quit IRC15:50
sjmc7being in the left-nav causes a lot of the inconsistency for me15:50
*** shaohe_feng has joined #openstack-meeting-415:50
* matt-borland is in another meeting, ping if needed15:50
TravTso, here's a couple of items to consider either way15:50
sjmc7it feels like it fits more neatly in the existing dashboards to me15:50
TravTthe available plugins will need to expose context15:50
TravTright now, if you come in with an admin token and list plugins, you just get them all15:51
*** jmccrory_ has joined #openstack-meeting-415:51
*** azbiswas has joined #openstack-meeting-415:51
TravTso if the ui remains in project and gets an admin one, then project should not show them15:51
sjmc7yeah, there is a BP to implement ‘admin only’ plugins whatever that means15:51
sjmc7i agree that’s currently a bit weird. although it’s weird however this discussion goes15:51
TravTthere also is another alternative to think about if we go with a global search15:52
TravTmaybe SL could provide data on each item as to why you got it?15:52
david-lyleanother option is change how the actions are invoked15:52
TravTthe only way I know of doing this would be to to do both a project scoped search and if admin also doing admin scoped search15:52
*** hvprash_ has joined #openstack-meeting-415:52
TravTand then mark the admin only ones as such15:53
david-lyleif there is a choice of admin vs owner, make the user explicitly select that15:53
david-lylecould still be in a separate dash15:53
david-lyleI just think the UX needs more thought15:53
*** Swami has joined #openstack-meeting-415:53
sjmc7yeah, i’m not gonna argue it to death15:53
* david-lyle trails the discussion a bit15:53
sjmc7but this discussion might’ve been better with some mockups beforehand rather than a full review15:54
TravTthe actions are definitely problematic15:54
david-lyle2 things to be separate dash15:54
*** zenoway has quit IRC15:54
david-lyle1) clear indicator of ownership vs not15:54
david-lyle2) very explicit user choice as to scope of the action15:54
*** stevelle has joined #openstack-meeting-415:55
*** zenoway has joined #openstack-meeting-415:55
*** zenoway has quit IRC15:55
*** prometheanfire has joined #openstack-meeting-415:55
david-lyleagain fixable, but it's not just as trivial as throwing the views into a new dash15:55
*** hvprash has quit IRC15:56
*** gangil has joined #openstack-meeting-415:56
TravTthe scope of actions seems rather tricky... with a lot of possible implications.15:57
david-lyleyes15:57
david-lyleand batch actions become a nightmare of scope15:57
david-lylenot sure whether those are in plan15:57
*** MarkAtwood has joined #openstack-meeting-415:57
sjmc7ooo!15:58
TravTokay, so, we are low on time, but i'd like to continue this discussion later if possible.15:59
*** ninag has quit IRC15:59
sjmc7in the thunderdome!15:59
TravTi think we need a little matrix of scenarios15:59
TravTin any case, i think we need to give more info on plugins16:00
TravTor filter by project or something16:00
*** shaohe_feng has quit IRC16:00
TravTbut we are out of time for this meeting16:00
TravTthanks everybody16:00
matt-borlandgood discussion, good points!16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May 12 16:00:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-12-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-12-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-12-15.01.log.html16:00
*** matt-borland has left #openstack-meeting-416:00
*** ddieterly is now known as ddieterly[away]16:00
*** lei-zh has left #openstack-meeting-416:00
*** spzala has joined #openstack-meeting-416:00
*** lakshmiS_ has left #openstack-meeting-416:00
odyssey4me#startmeeting OpenStack-Ansible16:01
openstackMeeting started Thu May 12 16:01:00 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:01
openstackThe meeting name has been set to 'openstack_ansible'16:01
*** sjmc7 has left #openstack-meeting-416:01
*** shaohe_feng has joined #openstack-meeting-416:01
odyssey4me#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack-Ansible)"16:01
prometheanfirealready here :P16:02
andymccro/16:02
*** asettle has joined #openstack-meeting-416:02
*** michaelgugino has joined #openstack-meeting-416:02
*** ametts has joined #openstack-meeting-416:02
michaelguginohere16:02
amettso/16:02
asettleyep16:03
*** ddieterly[away] is now known as ddieterly16:03
*** TravT has left #openstack-meeting-416:03
v1k0d3no/16:04
jmccrory_o/16:04
stevelleo/16:04
*** flaviodsr has joined #openstack-meeting-416:04
odyssey4meHowdy all :)16:05
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:05
odyssey4me#topic Shall we retire https://github.com/openstack/openstack-ansible-py_from_git ?16:05
*** openstack changes topic to "Shall we retire https://github.com/openstack/openstack-ansible-py_from_git ? (Meeting topic: OpenStack-Ansible)"16:05
cloudnullo/16:06
cloudnullyes16:06
odyssey4meWe've managed to eradicate this role from stable/mitaka and master. The question is whether we should keep it around because it may be useful to someone, or whether we should retire it?16:06
cloudnulllet it die16:06
*** gangil has quit IRC16:06
*** rromans has joined #openstack-meeting-416:06
andymccrif we're not using/testing it - i think we should let it die16:07
odyssey4meyeah, that's my sentiment16:07
odyssey4meany objections to doing this?16:07
*** __szilard_cserey has quit IRC16:07
jasondotstaro/16:08
odyssey4mealright, I'll process the retirement in the next week16:08
odyssey4me#action odyssey4me to retire https://github.com/openstack/openstack-ansible-py_from_git16:09
d34dh0r53o/16:09
odyssey4me#topic Tests Repo16:09
*** openstack changes topic to "Tests Repo (Meeting topic: OpenStack-Ansible)"16:09
*** GB21 has quit IRC16:09
odyssey4meAt the summit we discussed splitting the tests from the openstack-ansible repo into its own repo.16:09
odyssey4meI wanted to discuss whether this repo should include the bootstrap-host role, or whether we think the bootstrap-host role should be in its own repo?16:10
*** shaohe_feng has quit IRC16:10
prometheanfireI'm in favor of it being in it's own repo16:10
prometheanfireI think it's still useful outside of tests16:10
odyssey4memy hope is that we can create a tests repo and consolidate all integrated and role test stuff into it, hopefully massively reducing duplication16:11
*** shaohe_feng has joined #openstack-meeting-416:11
stevelleI'm confused about moving tests to their own repo16:12
*** azbiswas has quit IRC16:12
stevelleobviously I missed that discussion16:12
andymccrmy understanding is we'd have a generic "test" repo so we can facilitate the tests for the indivdual repositories,16:12
cloudnull^ +116:13
andymccrat the moment we have a situation where any minor change to the generic testing parts needs to change in the 15 or so repos16:13
andymccrbut i dont think it needs to do ALL the things16:13
andymccrthat may be overcomplicating it16:13
odyssey4meessentially there is a lot of duplication in the test plays & vars across the roles, so the general idea is to put the common requirements there and have the roles consume those things and only hold the things special to the role16:13
andymccrto start with we probably just need keystone, galera, rabbit, memcache16:13
*** sdake has quit IRC16:13
*** sacharya has joined #openstack-meeting-416:14
andymccrthen individual test-vars and inventory/host_vars/group_vars can be included in the roles themselves - which would customize the testing.16:14
stevelleI'd suggest we have that stuff centralized if we want to use it: it's in the os_keystone repo16:14
odyssey4meok, so the burning need is primarily for the roles right now16:14
*** azbiswas has joined #openstack-meeting-416:15
jmccrory_prepare-host test playbooks are already starting to drift between IRRs with multi distro changes16:15
odyssey4meyeah, keeping them similar is becoming a lot of work16:15
andymccryeh we need to make this happen sooner rather than later.16:16
andymccri already ran into a few bugs that would take a fix to each repo16:16
odyssey4mealso, for new projects coming in it'd be very useful to have them simply 'include' a base set of infra and build on it16:16
andymccragree16:16
andymccrbut id like to keep it as simple as possible upfront16:16
stevelle^16:16
odyssey4meok, how do we want to approach doing this?16:16
andymccrwe can grow it as needed - im scared of over engineering a "DO ALL THE THINGS" testing plan that we really dont need right now16:16
stevelleI'd be concerned about it growing to be a rubbish heap16:16
stevelleis there a PoC to see scope yet?16:17
andymccrstevelle: not yet16:17
odyssey4medoes one person want to try it out on a github repo for a PoC - then we look at it together, discuss it and take it from there?16:17
andymccrodyssey4me: i'll give it a go16:17
odyssey4meeveryone good with that?16:18
odyssey4mewhat do we want as a success criteria here?16:18
*** mohankumar_ has joined #openstack-meeting-416:18
andymccrim gonna say glance, keystone, nova, swift all working with a base set of "generic" tasks from a repo?16:18
odyssey4meI would suggest a review in for at least two openstack roles that consume a shared set of test configs/resources16:18
andymccrsounds good16:18
odyssey4meglance/keystone/nova/swift actually sounds like a good set16:19
andymccri might skip glance if it's taking too long :P but yeah.16:19
andymccri think it'll be the easiest to get working upfront16:20
odyssey4mesure, I was going to suggest that you could16:20
stevellegood plan16:20
odyssey4meok, we'll discuss it again every week and can always review in time too16:20
*** shaohe_feng has quit IRC16:20
odyssey4me#action andymccr to PoC a role test repository16:20
*** d0ugal has quit IRC16:20
odyssey4me#topic Ops/Contrib Repo16:21
*** openstack changes topic to "Ops/Contrib Repo (Meeting topic: OpenStack-Ansible)"16:21
odyssey4meAt the summit we also discussed having some sort of Ops/Contrib repository where users of OSA could share related plays, tools, or whatever16:21
*** d0ugal has joined #openstack-meeting-416:22
michaelguginoI like that idea, I don't have anything really pressing to put in it at the moment.16:22
*** andymaier has joined #openstack-meeting-416:22
odyssey4meone thing we could do is direct these sorts of contributions into https://github.com/openstack/osops-tools-generic/16:23
*** FrankZhang has joined #openstack-meeting-416:23
odyssey4meOsOps is an Operator community working group.16:23
*** shaohe_feng has joined #openstack-meeting-416:23
*** b3rnard0 has joined #openstack-meeting-416:23
odyssey4meWe could submit reviews to have an openstack-ansible folder in there and add the same sort of things16:23
odyssey4memy thinking is that it could improve exposure, and also means that we don't have to manage the dumping ground16:24
michaelguginothat repo hasn't had a merge since feb.16:24
*** gb21 has joined #openstack-meeting-416:24
*** sbezverk has quit IRC16:25
odyssey4meyeah, they're still a pretty new group and the operators are notorious for being too busy to submit code reviews ;)16:25
odyssey4mewe could, of course, have our own repo and then just add our repo to the bottom of their README as an additional resource16:26
michaelguginoI like that idea16:26
*** sbezverk has joined #openstack-meeting-416:26
*** spotz_zzz is now known as spotz16:26
*** jamesdenton has joined #openstack-meeting-416:26
odyssey4meany thoughts on a repo name for this?16:27
stevelleI like the idea of supporting the osops program16:27
*** d0ugal has quit IRC16:27
stevellebut that has problems as noted16:27
odyssey4mesomething like openstack-ansible-contrib ?16:28
spotzIf not supporting osops what about osaops - yeah I'm late16:28
*** woodard has quit IRC16:28
*** bpokorny has joined #openstack-meeting-416:28
michaelguginocontrib is too developer sounding16:30
odyssey4menot a fan of osaops myself - I'd rather not label it 'ops' but instead prefer to keep it generic16:30
michaelguginomaybe something like 'add-ons' or something a non dev would use16:30
michaelgugino'extensions' even16:30
spotzadd-ons is nice16:30
*** spzala has quit IRC16:30
michaelguginoor 'extras'16:30
*** shaohe_feng has quit IRC16:31
*** asettle has quit IRC16:31
michaelguginowe should also change our name from OpenStack-Ansible to something like the other projects (a cute name that means nothing).  I propose 'Jingle'16:31
cloudnullhahaha16:31
*** shaohe_feng has joined #openstack-meeting-416:31
odyssey4meextras I'm ok with I thikn16:32
odyssey4me*think16:32
*** azbiswas has quit IRC16:32
*** bpokorny has quit IRC16:32
odyssey4melol, renaming won't happen - it will break every downstream consumer16:32
*** bpokorny has joined #openstack-meeting-416:32
odyssey4meany objections to creating an openstack-ansible-extras repository for the purpose of contributors to share stuff outside of the integrated build?16:34
*** spzala has joined #openstack-meeting-416:36
spotz+116:36
*** sridhar_ram has joined #openstack-meeting-416:36
odyssey4mejmccrory automagically cloudnull d34dh0r53 stevelle mattt hughsaunders andymccr mhayden ping - hello anyone there?16:36
andymccri think my only concern is how we define what goes into that repository16:37
stevelleI'm not a hard no on 'extras' at all, just not sure it gives good guidance about what goes into it. Thinking about it :)16:37
andymccryeah i dont mind hte name16:37
cloudnulli like osaops16:37
*** prometheanfire has left #openstack-meeting-416:38
spotzyeah cloudnull:)16:38
odyssey4meie openstack-ansible-ops ?16:38
cloudnullbut im not -1 on extras16:38
d34dh0r53^16:38
andymccrthat seems fine to me16:38
d34dh0r53openstack-ansible-ops looks good to me16:38
d34dh0r53extras seems a little vague to me16:39
andymccri guess we can create the repo and define the other criteria once we start seeing traction/use cases16:39
spotzandymccr: I'm assuming stuff would still get reviewed so we'd be able to say something wasn't right for the repo16:39
odyssey4meyeah, at this point I'm looking to create the repo with nothing in it - I can then propose an initial readme where we can discuss scope and define it16:40
*** spzala has quit IRC16:40
odyssey4meI intend to also seed an initial bit into the repo to 'set the scene'.16:41
*** shaohe_feng has quit IRC16:41
michaelguginoosaops singles a little narrowly focused, but I'm not sure what wouldn't fit under 'ops' that would go in there, so I suppose it's doable.  Just calling it ops seems like it's saying 'you definitely want what's in here'16:41
michaelguginowhen I think it's more of a 'you might want some of what's in here'16:41
*** shaohe_feng has joined #openstack-meeting-416:41
*** ccesario has quit IRC16:41
odyssey4meIt'll basically be a doc describing how you can implement NTP across all your hosts using Ansible, the OSA dynamic inventory and an Ansible Galaxy role16:42
*** d0ugal has joined #openstack-meeting-416:42
jmccrorythat sounds good. maybe more of the pre-setup tasks that get asked about, networking, disks, etc16:43
*** uck has joined #openstack-meeting-416:43
*** azbiswas has joined #openstack-meeting-416:43
odyssey4meyep, that's exactly what I'd like to see go in there16:43
*** yingjun has quit IRC16:43
*** vinsh has left #openstack-meeting-416:43
odyssey4mecloudnull has some magic to setup all the networking given a set of assumptions16:43
*** yingjun has joined #openstack-meeting-416:44
odyssey4methese are all useful things, but not things we want to make promises about in the integrated build16:44
cloudnullyes thats in my osic repos16:44
cloudnullhttps://github.com/os-cloud/osic-ironic-impl/tree/master/templates16:44
*** andymaier has quit IRC16:44
*** gangil has joined #openstack-meeting-416:45
odyssey4meI think openstack-ansible-ops would be fine. While I agree with michaelgugino that it does suggest a limited scope, I think useful things for operators is the primary target.16:45
*** Jeffrey4l has quit IRC16:45
cloudnullI also have preseeds for host paritioning and other things if we want to move those bits16:45
odyssey4mecloudnull yeah, all those things would be nice to include there for broader exposure16:45
odyssey4meand I'll share the repo presence with the osops community16:46
odyssey4mealright, let's go with that16:46
odyssey4me#action odyssey4me to request the creation of a blank openstack-ansible-ops repository to carry useful plays/tools for operators16:47
odyssey4me#topic Open discussion16:47
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack-Ansible)"16:47
*** spzala has joined #openstack-meeting-416:48
odyssey4meConsidering we're pretty much done for time I figured I'd open it up for open discussion instead of continuing with the agenda16:48
spotzIs anyone working on the conversion of os-horizon? Don't want to pick one someone's working on16:48
odyssey4meif no-one has anything specific then I wouldn't mind discussing the Mid Cycle16:48
*** yingjun has quit IRC16:48
cloudnullits all your ;)16:48
stevellespotz: I had hoped to but pulled my name off, just not finding time16:48
spotzThanks stevelle, I accidently picked one cloudnull was working on last time so want an unloved one:)16:49
*** sdake has joined #openstack-meeting-416:49
*** alex_xu has quit IRC16:49
michaelguginocloudnull: have you started the keystone work for xenial?16:50
cloudnullI have not16:50
*** thorst_ has quit IRC16:50
michaelguginoI was thinking about picking that up if you don't mind16:50
cloudnullgo ahead16:50
michaelguginoalright, will do.16:50
cloudnullive been a little swamped with osic work16:50
michaelguginoOnce we have that and galera server merged, the rest of the roles will follow16:51
*** chem has left #openstack-meeting-416:51
*** LouisF has joined #openstack-meeting-416:51
*** shaohe_feng has quit IRC16:51
*** mageshgv has joined #openstack-meeting-416:51
*** mageshgv has quit IRC16:51
*** shaohe_feng has joined #openstack-meeting-416:51
michaelguginoodyssey4me: I had some question about testing16:51
michaelguginocan we deploy multiple instances for running different checks in parallel?16:52
odyssey4mehave we covered all the dependent roles? os_keystone relies on quite a few and I don't think we have all the basic infra roles covered yet?16:52
*** spzala has quit IRC16:52
odyssey4memichaelgugino I will take care of getting another functional check in for openvswitch.16:52
*** alex_xu has joined #openstack-meeting-416:52
michaelguginook, that's what I was wondering about16:52
odyssey4me#action odyssey4me to prep os_neutron openvswitch job in OpenStack-CI16:53
stevellehave any of the os_roles started running tempest in their role repo gate?16:53
*** emagana has quit IRC16:53
odyssey4mestevelle yes, mattt's been working on that16:53
*** mohankumar has joined #openstack-meeting-416:53
odyssey4meI think nova is done.16:53
*** georgewang has joined #openstack-meeting-416:53
odyssey4meHe's currently revising the tempest role, horizon role and designate role to cover the tempest plugin use-case16:54
spotzironic, switft, nova are theones without names odyssey4me16:54
odyssey4methere are a few reviews ongoing - please support him by reviewing.16:54
*** javeriak has joined #openstack-meeting-416:54
*** sambetts is now known as sambetts|afk16:55
stevelleodyssey4me: found it, thx16:55
odyssey4mespotz I think andymccr will cover swift16:55
*** antonyfm has joined #openstack-meeting-416:55
odyssey4mespotz so you're welcome to go with ironic/nova for the var break-out16:55
spotzIf I get through horizon I'll pick up ironic16:55
odyssey4methere is also zaqar and rally, which would be a far easier start16:55
odyssey4menova/ironic have some nasty dragons :p16:56
spotzooh maybe I'll do one of those then try horizon16:56
*** thorst_ has joined #openstack-meeting-416:56
spotzwork has been busy, slacking on my reviewing:(16:56
stevellelast topic I wanted to ask about, has anyone picked up the challenge of trying to document how to use our inventory more thoroughly yet?16:57
stevelleenv.d and conf.d bits esp.16:57
*** cathy__ has joined #openstack-meeting-416:58
odyssey4mestevelle nope, not to my knowledge16:58
*** michaelgugino has left #openstack-meeting-416:58
stevelleok, it's going to start becoming a hotter topic for me as I try to get more folks familiar with OSA. I will need help but will try to at least start a draft on that in the next 2 weeks16:59
odyssey4meexcellent, thanks stevelle16:59
spotzstevelle if you draft I'll help finish16:59
*** mfedosin has quit IRC17:00
*** spzala has joined #openstack-meeting-417:00
*** thorst_ has quit IRC17:01
odyssey4mealright, we're out of time17:01
odyssey4methanks all!17:01
odyssey4me#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
cloudnullsee you all later.17:01
openstackMeeting ended Thu May 12 17:01:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-12-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-12-16.01.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-12-16.01.log.html17:01
cathy__#startmeeting service_chaining17:01
openstackMeeting started Thu May 12 17:01:32 2016 UTC and is due to finish in 60 minutes.  The chair is cathy__. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: service_chaining)"17:01
openstackThe meeting name has been set to 'service_chaining'17:01
*** shaohe_feng has quit IRC17:01
cathy__hi everyone17:02
LouisFhi cathy__17:02
scsnowhi17:02
yamahatahello17:02
pcarverhi17:02
doonhammerHi Cathy17:02
*** shaohe_feng has joined #openstack-meeting-417:02
georgewanghi17:02
*** tung_doan has joined #openstack-meeting-417:02
cathy__Let's start17:02
vishnoianilhi everyone17:02
cathy__#topic Status update17:02
*** openstack changes topic to "Status update (Meeting topic: service_chaining)"17:03
*** azbiswas has quit IRC17:03
mohankumarhi17:03
cathy__1. Add support for Querying Driver capability for SFC functionality support17:03
*** srwilkers has joined #openstack-meeting-417:03
*** pvaneck has joined #openstack-meeting-417:03
*** thorst_ has joined #openstack-meeting-417:03
*** azbiswas has joined #openstack-meeting-417:03
*** flaviodsr has left #openstack-meeting-417:04
*** spzala has quit IRC17:04
cathy__scsnow: did you take this work?17:05
cathy__or maybe someone else?17:05
*** twm2016 has joined #openstack-meeting-417:05
scsnowI did a quick look into neutron microversions proposal and it seems for me, that it does not what we need17:05
*** lakshmiS has joined #openstack-meeting-417:06
scsnowso we would need to work on spec to define requirements17:06
regXboiso.. I would point out that isn't just neutron's microversioning - it's openstack's17:06
scsnowcurrently it's implemented only in nova17:07
scsnowand that's about API capabilities17:07
*** thorst_ has quit IRC17:07
LouisFregXboi: only implemented in nova?17:07
LouisFscsnow: +117:08
regXboiI would disagree with that statement17:08
regXboibut that is neither here nor there17:08
*** srwilkers has quit IRC17:08
cathy__scsnow: I agree with you that It is about API cap, not the driver cap.17:09
*** stevelle has left #openstack-meeting-417:10
LouisFscsnow: agree microversioning does not really expose different driver capablities17:10
cathy__scsnow: Yes, we need a spec on the requirement and mechanism how to do it to satisfy the requirement. Could you start working on this?17:11
scsnowper my understanding we need to extend sfc api by adding additional method let's say get_driver_capabilities17:11
LouisFdoes neutron itself address differences in the ml2 driver capablities?17:11
cathy__scsnow: yes, agree on that direction.17:11
scsnowand each driver should implement it to report its capabilities17:11
*** spzala has joined #openstack-meeting-417:11
*** shaohe_feng has quit IRC17:12
LouisFit must exist as a issue with neutron itself17:12
*** shaohe_feng has joined #openstack-meeting-417:12
cathy__Another aspect is that if a user specify a SFC requirement in the API, the API needs to query the driver cap to see if it can meet that req, if not reject the API request17:13
scsnowLouisF, I think no. At least there is not way to identify whether specific type driver in supported in specific mech driver17:13
mohankumarLouisF: good question , thought of same17:13
LouisFthere are different ml2 drivers and they certainly don't offer the  same support17:13
pcarverLouisF: The one place I know Neutron does something has to do with VLAN transparency. I don't think it's part of ML2 specifically, but there's a Neutron API to check whether a network will pass VLAN tags transparently between VMs17:13
LouisFpcarver: yes i saw that17:13
LouisFdoes the same problem exist with neutron and there is a solution already17:14
cathy__LouisF: scsnow mohankumar pcarver Yes, I think we should investigate whether Neutron has similar mechanism since Neutron should have the same problem.17:15
LouisFi would prefer a common solution to this17:15
cathy__But the case could be that Neutron has not done it or not done it in a generic way. Agree with Louis that this is a generic issue not specific to SFC and we should implement a generic mechanism that can be used by other features in the future17:16
*** spzala has quit IRC17:16
LouisFthat said we should also look into the implications of microversioning the api17:16
LouisFthe networking-sfc api that is17:17
cathy__LouisF: microversioning should be done for all networking-sfc API, not just this specific one\17:17
*** unicell has joined #openstack-meeting-417:17
LouisFcathy__: you mean neutron api17:18
scsnowI also prefer generic approach. But currently neutron does not provide anything useful for our case. Even API microversioning is not implemented there.17:18
cathy__LouisF: no, we do the API for SFC but do it in a generic way17:19
cathy__or try to do it in a generic way17:19
mohankumarGenerally team will update their driver support to marketplace : https://www.openstack.org/marketplace/drivers/17:19
LouisFscsnow: we should adopt what neutron does17:19
cathy__scsnow: let's just do it for SFC driver capability for now17:19
cathy__But the query mechanism should be easily extended for querying more capability or new capability in the future17:20
scsnowcathy__, ok. can someone would help me to work on spec? at least define the list of driver capabilities, i.e. ability to handle symmetric chains and so on17:21
cathy__LouisF: what do you mean by adopt what Neutron does? Does Neutron have the mechanism of querying the driver cap for Neutron API feature support?17:21
*** s3wong has joined #openstack-meeting-417:21
LouisFcathy__: i meant neutron microversioning17:21
s3wongsorry, late (again)17:21
cathy__scsnow: I can help you on that17:21
scsnowcathy__, thanks17:21
LouisFscsnow: can help17:21
scsnowLouisF, thanks17:21
*** shaohe_feng has quit IRC17:22
*** shaohe_feng has joined #openstack-meeting-417:22
cathy__OK, Louis and I will send you a list of API caps that a driver can support.17:23
cathy__Ok, let's go to next item17:23
LouisFhttp://specs.openstack.org/openstack/neutron-specs/specs/liberty/microversioning.html17:23
*** spzala has joined #openstack-meeting-417:23
cathy__2. Networking-sfc SFC driver for OVN17:24
cathy__John, are you there?17:24
doonhammeryes cathy17:24
*** salv-orlando has quit IRC17:24
doonhammerI have been working with Ryan/regXboi17:25
doonhammerto merge the changes into a patch set17:25
cathy__doonhammer: great!17:25
doonhammerI have sfc and ovn done now working on OVN17:25
*** jamesdenton has left #openstack-meeting-417:25
cathy__Yes, I saw emails in the OVS alias17:25
*** ddieterly is now known as ddieterly[away]17:25
s3wongdoonhammer: seems like there are changes in OVS, logically that should go in first17:25
*** rromans has left #openstack-meeting-417:26
cathy__s3wong: yes, that is where they have been working17:26
s3wongdoonhammer: and I guess next would be networking-ovn actually adding the support for the new NB schema17:26
doonhammeryes but they are harder :-)17:26
regXboiwell... not exactly17:26
s3wongdoonhammer: networking-sfc changes (if any) should be last... is the OVN SFC driver going to be in networking-ovn repo or networking-sfc?17:27
regXboiwith respect to the patch set for ovs/ovn, having the other patch sets to refer to for E2E testing will help the ovs/ovn review process immensely17:27
doonhammeronce I have a clean version I need to convert the ovs/ovn code to use port-pair model ala Russell's approach17:27
cathy__regXboi: Ok, got it. We have done E2E testing for the OVS driver path.17:27
LouisFdoonhammer: we need to finalize the extensions to the ovn nb schema17:28
*** spzala has quit IRC17:28
cathy__regXboi: We are working on automating the E2E testing and will post the testing scripts soon. Is this the help you need?17:28
doonhammerLouisF: yes a lot of work remains - I just wanted to get something that showed it would work then the really work begins17:28
regXboicathy__: the OVS driver patch doesn't really help17:29
cathy__doonhammer: :-)17:29
regXboicathy__: automation is always good, but the ovn/ovs patch will needs its own unit tests as part of its commit, since we can't depend on openstack there17:29
LouisFdoonhammer: sounds good17:29
regXboicathy__: on the other hand, being able to say that the patch also works with n-ovn and n-sfc does carry weight in the review process17:30
cathy__regXboi: I see. So what you need is the UT and E2E testing on the OVN path17:30
regXboicathy__: ack17:30
doonhammerwe probably need a simple dumb VNF to test - I have been using our NGFW in my test cases17:30
*** kylek3h has joined #openstack-meeting-417:31
s3wongcathy__: this begs the question... if the SFC drivers live in a different repo (i.e., such as ODL driver), obviously it is strange for each SDN / networking repo which has SFC driver to have functional test on SFC features, how are we (networking-sfc) supposed to provide a CI test framework to ensure all drivers are sane (like Neutron does)?17:32
*** shaohe_feng has quit IRC17:32
cathy__doonhammer: yes, for the testing, we do not really needs real VNF functionality since we are testing the chain, not the VNF functionality17:32
*** shaohe_feng has joined #openstack-meeting-417:33
LouisFdoonhammer: we do need to account for the vnf insertion mode: bump in wire, l2, ..17:33
cathy__s3wong: That is a good question. That is why I have the topic discussion in last meeting on which repo the drivers should go17:33
*** gb21 has quit IRC17:33
*** IlyaG has joined #openstack-meeting-417:33
*** IlyaG has quit IRC17:34
*** d0ugal has quit IRC17:34
doonhammerI think we need end to end testing especially when we have a chain17:34
*** IlyaG has joined #openstack-meeting-417:34
cathy__s3wong: I guess each driver needs to ensure their "insane" if the driver resides outside of networking-sfc. But for driver that resides inside networking-sfc, networking-sfc team and CI needs to ensure that17:34
*** julim has quit IRC17:35
regXboiso... having drivers live inside of n-sfc that depend on other projects is a recipe for a mess17:35
regXboilook at the time being spent pulling the *aaS code out of neutron17:35
regXboithe contract should be API driven, and then the other projects can have unit tests for those pieces of the API17:36
LouisFregXboi: i think that was agreed to at the last meeting17:36
cathy__s3wong: make sense. For those drivers that reside inside networking-sfc, they are SFC's reference implementation and any new API extensions need to be supported by those drivers and comprehensive testing needs to be ensured17:37
doonhammerregXboi: +117:37
cathy__s3wong: make sense?17:37
regXboiLouisF: it was - I'm hoping we aren't reopening it :)17:37
*** spzala has joined #openstack-meeting-417:37
doonhammerone of the comments regXboi had on my code was that and I am fixing it. Once we have and OVS and OVN driver would be good to do a review and make sure we are doing the right abstraction17:38
s3wongcathy__: I think the model for even the stadium projects is that drivers are decomposed just like Neutron; my gut tells me most drivers will reside OUTSIDE of networking-sfc repo (just like Neutron)17:38
*** alex_xu has quit IRC17:38
s3wongcathy__: so we may (eventually) need to provide a driver CI like Neutron17:38
cathy__s3wong: could you look into the driver CI for networking-sfc?17:39
cathy__s3wong: similar to what Neutron does?17:39
s3wongcathy__: I can take a look at how Neutron does it :-)17:39
cathy__Ok, this item is assigned to you since most other people are full on hand:-)17:40
*** nmadhok has quit IRC17:40
*** nmadhok has joined #openstack-meeting-417:40
*** spzala has quit IRC17:41
*** srwilkers has joined #openstack-meeting-417:41
*** markvoelker has joined #openstack-meeting-417:41
cathy__#action s3wong will investigate the driver CI for networking-sfc.17:41
*** Sukhdev has joined #openstack-meeting-417:42
*** SumitNaiksatam has joined #openstack-meeting-417:42
*** shaohe_feng has quit IRC17:42
*** shaohe_feng has joined #openstack-meeting-417:43
cathy__doonhammer: regXboi Very good progress. Thanks! Let us know if you need any help.17:43
cathy__3. Networking-sfc SFC driver for ODL17:43
cathy__AFAIK this driver spec is approved. How is the code development going?17:44
cathy__yamahata: are you there?17:44
cathy__vishnoianil: ?17:44
yamahatacathy__: yes?17:44
cathy__yamahata: vishnoianil any update on the code side?17:44
yamahataSo far it's up to vishnoianil.17:44
yamahatano patch isn't uploaded yet.17:45
yamahatapatch for code17:45
doonhammercathy: once I have the basic version done will need help looking at all the edge conditions - I will start a list on issues I see - any place I can post it?17:45
cathy__vishnoianil: are you there? Are you working on the code patch?17:45
*** ninag has joined #openstack-meeting-417:46
*** ninag has quit IRC17:46
cathy__doonhammer: You can either send it via emails or post it on our wiki project wiki page.17:46
doonhammercathy: ack17:47
cathy__doonhammer: or we can have a f2f meeting to go through them if that is more effective.17:47
vishnoianilcathy__, sorry doing double shifting between opendaylighjt tsc meeting and this one17:47
vishnoianilcathy__, i already pushed the yang models to opendaylight project17:48
vishnoianiland the next step is to write the driver in networking-odl17:48
*** ninag has joined #openstack-meeting-417:48
*** spzala has joined #openstack-meeting-417:49
cathy__vishnoianil: good progress! Thanks for your work!17:49
*** mjblack has quit IRC17:49
cathy__4. Networking-sfc integration with ONOS completion status update17:49
mohankumarcathy__ , code already developed and we tested internally, driver code already magred to networking-onos sub-roject repo17:50
mohankumarhttps://github.com/openstack/networking-onos/blob/master/doc/source/devref/sfc_driver.rst17:50
mohankumarhttps://github.com/openstack/networking-onos/blob/master/networking_onos/services/sfc/driver.py17:50
mohankumarhttps://github.com/openstack/networking-onos/blob/master/doc/source/devref/flowclassifier_driver.rst17:50
mohankumarhttps://github.com/openstack/networking-onos/blob/master/networking_onos/services/flowclassifier/driver.py17:50
*** ninag_ has joined #openstack-meeting-417:50
cathy__mohankumar: Great. Yes, I know codes have been merged. Have you uploaded UT and functional testing codes too?17:51
mohankumaryes cathy__  Test codes already wrote17:51
mohankumar** UT17:52
mohankumarfunctional Test , i need to check17:52
cathy__Ok, great!17:52
cathy__Now last one17:52
*** d0ugal has joined #openstack-meeting-417:52
cathy__5. Tacker Driver for networking-sfc17:52
*** shaohe_feng has quit IRC17:53
cathy__LouisF: has this spec been merged in tacker repo?17:53
*** ninag has quit IRC17:53
*** reedip__ has joined #openstack-meeting-417:53
LouisFneed final review of https://review.openstack.org/#/c/290771/17:53
*** spzala has quit IRC17:53
*** shaohe_feng has joined #openstack-meeting-417:53
*** spzala has joined #openstack-meeting-417:54
*** srwilkers has quit IRC17:54
LouisFis has had comment and i have updated some time ago17:54
cathy__Ok, you may want to ping Scridhar on this to get it reviewed and merged so that coding can be started.17:54
LouisFcathy__: will do17:55
s3wongLouisF: yeah, you updated the spec during the summit, and most people probably missed it :-)17:55
LouisFs3wong: i will ping again17:55
cathy__I mean final review17:55
cathy__LouisF: Good. Thanks.17:55
*** sbezverk_ has joined #openstack-meeting-417:55
cathy__s3wong: Could you please help on getting the final review done and the patch merged?17:56
s3wongcathy__, LouisF: a lot of comments came from trozet, and during the summit, he and I spoke --- and he indicated he is fine with the current version17:56
*** sbezverk has quit IRC17:57
LouisFs3wong: i have pinged17:57
s3wongcathy__, LouisF: given the understanding of VNFFG in general, the +2s will likely have to come from sridhar_ram and me17:57
cathy__LouisF: s3wong good. Thanks!17:57
*** coolsvap has quit IRC17:57
LouisFs3wong: i incorporated his comments17:57
*** zenoway has joined #openstack-meeting-417:57
s3wongLouisF: yes, I noticed :-)17:58
*** pcaruana has quit IRC17:58
cathy__We do not have time for the other topics. We have made very good progress on our driver integration work!17:59
*** dtardivel has quit IRC17:59
cathy__Keep up the good work! Bye for now17:59
LouisFbye17:59
scsnowbye17:59
doonhammerbye18:00
cathy__#endmeeting18:00
mohankumarbye18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu May 12 18:00:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-12-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-12-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-12-17.01.log.html18:00
*** regXboi has left #openstack-meeting-418:00
*** cathy__ has quit IRC18:00
*** dshakhray has quit IRC18:01
*** zenoway has quit IRC18:02
*** srwilkers has joined #openstack-meeting-418:02
*** shaohe_feng has quit IRC18:03
*** shaohe_feng has joined #openstack-meeting-418:03
*** azbiswas has quit IRC18:03
*** andymaier has joined #openstack-meeting-418:04
*** dave-mccowan has quit IRC18:05
*** azbiswas has joined #openstack-meeting-418:06
*** srwilkers has quit IRC18:06
*** jichen has joined #openstack-meeting-418:06
*** twm2016 has left #openstack-meeting-418:07
*** klamath has quit IRC18:07
*** d0ugal has quit IRC18:08
*** andymaier has quit IRC18:11
*** ninag_ has quit IRC18:13
*** shaohe_feng has quit IRC18:13
*** sudipto has quit IRC18:13
*** shaohe_feng has joined #openstack-meeting-418:14
*** javeriak has quit IRC18:14
*** vishnoianil has quit IRC18:15
*** nmadhok has quit IRC18:15
*** ninag has joined #openstack-meeting-418:15
*** javeriak has joined #openstack-meeting-418:16
*** nmadhok has joined #openstack-meeting-418:16
*** vhoward has joined #openstack-meeting-418:17
*** julim has joined #openstack-meeting-418:17
*** azbiswas has quit IRC18:17
*** jwagner is now known as jwagner[away]18:18
*** markvoelker_ has joined #openstack-meeting-418:19
*** andymaier has joined #openstack-meeting-418:20
*** javeriak has quit IRC18:21
*** hvprash has joined #openstack-meeting-418:22
*** markvoelker has quit IRC18:22
*** shaohe_feng has quit IRC18:23
*** shaohe_feng has joined #openstack-meeting-418:24
*** hvprash_ has quit IRC18:25
*** azbiswas has joined #openstack-meeting-418:25
*** ddieterly[away] has quit IRC18:26
*** trozet has quit IRC18:28
*** doonhammer has quit IRC18:28
*** doonhammer has joined #openstack-meeting-418:30
*** shaohe_feng has quit IRC18:34
*** shaohe_feng has joined #openstack-meeting-418:34
*** belmoreira has joined #openstack-meeting-418:34
*** ninag has quit IRC18:35
*** ninag has joined #openstack-meeting-418:35
*** ninag has quit IRC18:35
*** mjblack has joined #openstack-meeting-418:36
*** ninag has joined #openstack-meeting-418:36
*** hvprash has quit IRC18:36
*** ddieterly has joined #openstack-meeting-418:36
*** spzala has quit IRC18:38
*** jmccrory_ has quit IRC18:39
*** ninag has quit IRC18:39
*** hvprash has joined #openstack-meeting-418:40
*** s3wong has quit IRC18:40
*** jwagner[away] is now known as jwagner18:43
*** trozet has joined #openstack-meeting-418:43
*** azbiswas has quit IRC18:43
*** spzala has joined #openstack-meeting-418:44
*** shaohe_feng has quit IRC18:44
*** tung_doan has quit IRC18:44
*** shaohe_feng has joined #openstack-meeting-418:44
*** reedip__ has quit IRC18:44
*** sdake has quit IRC18:44
*** ninag has joined #openstack-meeting-418:46
*** vhoward has quit IRC18:48
*** spzala has quit IRC18:48
*** IlyaG has quit IRC18:49
*** ninag has quit IRC18:51
*** shaohe_feng has quit IRC18:54
*** ddieterly is now known as ddieterly[away]18:54
*** shaohe_feng has joined #openstack-meeting-418:55
*** zenoway has joined #openstack-meeting-418:58
*** sambetts|afk has quit IRC18:59
*** srwilkers has joined #openstack-meeting-418:59
*** antonyfm has quit IRC19:01
*** mohankumar has quit IRC19:01
*** omnipresent has joined #openstack-meeting-419:01
*** zenoway has quit IRC19:02
*** d0ugal has joined #openstack-meeting-419:02
*** sambetts has joined #openstack-meeting-419:03
*** sbezverk_ is now known as sbezverk19:04
*** mjblack has quit IRC19:04
*** shaohe_feng has quit IRC19:04
*** shaohe_feng has joined #openstack-meeting-419:05
*** doonhammer has quit IRC19:06
*** armax has quit IRC19:07
*** vishnoianil has joined #openstack-meeting-419:08
*** uck has quit IRC19:10
*** spzala has joined #openstack-meeting-419:10
*** spzala has quit IRC19:11
*** spzala has joined #openstack-meeting-419:11
*** uck has joined #openstack-meeting-419:11
*** doonhammer has joined #openstack-meeting-419:14
*** gangil has quit IRC19:14
*** trozet has quit IRC19:14
*** woodard has joined #openstack-meeting-419:14
*** shaohe_feng has quit IRC19:15
*** shaohe_feng has joined #openstack-meeting-419:15
*** uck has quit IRC19:16
*** salv-orlando has joined #openstack-meeting-419:16
*** ddieterly[away] is now known as ddieterly19:17
*** bpokorny has quit IRC19:18
*** shaohe_feng has quit IRC19:25
*** raj_singh has joined #openstack-meeting-419:25
*** trozet has joined #openstack-meeting-419:25
*** srwilkers has quit IRC19:26
*** shaohe_feng has joined #openstack-meeting-419:27
*** srwilkers has joined #openstack-meeting-419:28
*** Sukhdev has quit IRC19:32
*** Sukhdev has joined #openstack-meeting-419:32
*** shaohe_feng has quit IRC19:35
*** shaohe_feng has joined #openstack-meeting-419:36
*** ninag has joined #openstack-meeting-419:38
*** antonyfm has joined #openstack-meeting-419:40
*** ninag has quit IRC19:41
*** ninag has joined #openstack-meeting-419:42
*** yingjun has joined #openstack-meeting-419:44
*** ninag has quit IRC19:45
*** yingjun has quit IRC19:45
*** yingjun has joined #openstack-meeting-419:45
*** bpokorny has joined #openstack-meeting-419:45
*** shaohe_feng has quit IRC19:45
*** shaohe_feng has joined #openstack-meeting-419:46
*** mbound has joined #openstack-meeting-419:49
*** yingjun has quit IRC19:50
*** matrohon has joined #openstack-meeting-419:51
*** yamahata has quit IRC19:52
*** iyamahat has quit IRC19:52
*** sacharya_ has joined #openstack-meeting-419:53
*** sacharya has quit IRC19:53
*** sacharya has joined #openstack-meeting-419:53
*** srwilkers has quit IRC19:53
*** belmoreira has quit IRC19:54
*** Swami has quit IRC19:54
*** sacharya_ has quit IRC19:54
*** doonhammer has quit IRC19:55
*** shaohe_feng has quit IRC19:56
*** shaohe_feng has joined #openstack-meeting-419:57
*** azbiswas has joined #openstack-meeting-419:57
*** Swami has joined #openstack-meeting-419:57
*** woodard has quit IRC19:58
*** yamahata has joined #openstack-meeting-419:58
*** doonhammer has joined #openstack-meeting-419:59
*** ccesario has joined #openstack-meeting-420:03
*** gangil has joined #openstack-meeting-420:03
*** iyamahat has joined #openstack-meeting-420:06
*** shaohe_feng has quit IRC20:06
*** shaohe_feng has joined #openstack-meeting-420:06
*** ddieterly is now known as ddieterly[away]20:07
*** yamahata has quit IRC20:09
*** ddieterly[away] is now known as ddieterly20:11
*** doonhammer has quit IRC20:13
*** njohnston__ is now known as njohnston_afk20:13
*** doonhammer has joined #openstack-meeting-420:13
*** iyamahat has quit IRC20:16
*** shaohe_feng has quit IRC20:16
*** belmoreira has joined #openstack-meeting-420:16
*** spzala_ has joined #openstack-meeting-420:16
*** doonhammer has quit IRC20:17
*** spzala has quit IRC20:18
*** shaohe_feng has joined #openstack-meeting-420:19
*** Sukhdev has quit IRC20:23
*** uck has joined #openstack-meeting-420:23
*** Sukhdev has joined #openstack-meeting-420:24
*** shaohe_feng has quit IRC20:26
*** shaohe_feng has joined #openstack-meeting-420:29
*** dshakhray has joined #openstack-meeting-420:31
*** wznoinsk has quit IRC20:32
*** bobh has quit IRC20:32
*** iyamahat has joined #openstack-meeting-420:33
*** yamahata has joined #openstack-meeting-420:33
*** raj_singh has left #openstack-meeting-420:34
*** bobh has joined #openstack-meeting-420:34
*** belmoreira has quit IRC20:34
*** cwolferh has quit IRC20:35
*** ninag has joined #openstack-meeting-420:36
*** shaohe_feng has quit IRC20:37
*** shaohe_feng has joined #openstack-meeting-420:39
*** thorst_ has joined #openstack-meeting-420:42
*** wznoinsk has joined #openstack-meeting-420:45
*** Sukhdev has quit IRC20:46
*** ddieterly is now known as ddieterly[away]20:46
*** shaohe_feng has quit IRC20:47
*** shaohe_feng has joined #openstack-meeting-420:48
*** armax has joined #openstack-meeting-420:50
*** andymaier has quit IRC20:51
*** jichen has quit IRC20:53
*** shaohe_feng has quit IRC20:57
*** shaohe_feng has joined #openstack-meeting-420:58
*** hvprash has quit IRC21:00
*** emagana has joined #openstack-meeting-421:00
*** sdake has joined #openstack-meeting-421:03
*** azbiswas_ has joined #openstack-meeting-421:04
*** hvprash has joined #openstack-meeting-421:04
*** spzala_ has quit IRC21:06
*** shaohe_feng has quit IRC21:07
*** azbiswas has quit IRC21:07
*** shaohe_feng has joined #openstack-meeting-421:08
*** baoli_ has quit IRC21:10
*** ddieterly[away] is now known as ddieterly21:12
*** lakshmiS has quit IRC21:13
*** nmadhok has quit IRC21:13
*** nmadhok has joined #openstack-meeting-421:18
*** shaohe_feng has quit IRC21:18
*** Sukhdev has joined #openstack-meeting-421:18
*** claired has joined #openstack-meeting-421:18
*** shaohe_feng has joined #openstack-meeting-421:18
*** cwolferh has joined #openstack-meeting-421:21
*** sdake_ has joined #openstack-meeting-421:24
*** thorst_ has quit IRC21:27
*** thorst_ has joined #openstack-meeting-421:27
*** shaohe_feng has quit IRC21:28
*** claired has quit IRC21:28
*** sdake has quit IRC21:28
*** shaohe_feng has joined #openstack-meeting-421:28
*** sdake has joined #openstack-meeting-421:31
*** thorst_ has quit IRC21:31
*** sdake_ has quit IRC21:32
*** dshakhray has quit IRC21:32
*** thorst_ has joined #openstack-meeting-421:33
*** ametts has quit IRC21:33
*** nmadhok has quit IRC21:33
*** lkoranda has quit IRC21:33
*** thorst_ has quit IRC21:36
*** georgewang has quit IRC21:36
*** thorst_ has joined #openstack-meeting-421:36
*** lkoranda has joined #openstack-meeting-421:37
*** shaohe_feng has quit IRC21:38
*** shaohe_feng has joined #openstack-meeting-421:38
*** ddieterly is now known as ddieterly[away]21:38
*** ddieterly[away] has quit IRC21:41
*** rtheis has quit IRC21:43
*** brucet has joined #openstack-meeting-421:45
*** shaohe_feng has quit IRC21:48
*** shaohe_feng has joined #openstack-meeting-421:49
*** matrohon has quit IRC21:49
*** ninag has quit IRC21:50
*** nmadhok has joined #openstack-meeting-421:52
*** bobh has quit IRC21:58
*** shaohe_feng has quit IRC21:59
*** thorst_ has quit IRC21:59
*** shaohe_feng has joined #openstack-meeting-421:59
*** sigmavirus24 is now known as sigmavirus24_awa22:00
*** cdelatte has joined #openstack-meeting-422:04
*** thorst_ has joined #openstack-meeting-422:05
*** thorst_ has quit IRC22:05
*** thorst_ has joined #openstack-meeting-422:06
*** brucet has quit IRC22:06
*** brucet has joined #openstack-meeting-422:07
*** Sukhdev has quit IRC22:07
*** shaohe_feng has quit IRC22:09
*** shaohe_feng has joined #openstack-meeting-422:09
*** daneyon has joined #openstack-meeting-422:12
*** nmadhok has quit IRC22:15
*** thorst_ has quit IRC22:16
*** daneyon_ has quit IRC22:16
*** brucet has quit IRC22:16
*** shaohe_feng has quit IRC22:19
*** shaohe_feng has joined #openstack-meeting-422:20
*** brucet_ has joined #openstack-meeting-422:22
*** thorst_ has joined #openstack-meeting-422:22
*** andymaier has joined #openstack-meeting-422:22
*** lakshmiS has joined #openstack-meeting-422:24
*** markvoelker_ has quit IRC22:25
*** thorst_ has quit IRC22:27
*** spotz is now known as spotz_zzz22:28
*** azbiswas_ has quit IRC22:28
*** shaohe_feng has quit IRC22:29
*** shaohe_feng has joined #openstack-meeting-422:30
*** brucet_ has quit IRC22:30
*** emagana has quit IRC22:30
*** brucet_ has joined #openstack-meeting-422:30
*** omnipresent has quit IRC22:33
*** emagana has joined #openstack-meeting-422:33
*** emagana has quit IRC22:34
*** emagana has joined #openstack-meeting-422:34
*** dave-mccowan has joined #openstack-meeting-422:34
*** cwolferh has quit IRC22:35
*** galstrom is now known as galstrom_zzz22:36
*** dave-mcc_ has joined #openstack-meeting-422:36
*** MarkAtwood has quit IRC22:38
*** brucet_ has quit IRC22:39
*** shaohe_feng has quit IRC22:40
*** dave-mccowan has quit IRC22:40
*** azbiswas has joined #openstack-meeting-422:40
*** shaohe_feng has joined #openstack-meeting-422:40
*** daneyon has quit IRC22:43
*** bpokorny_ has joined #openstack-meeting-422:47
*** shaohe_feng has quit IRC22:50
*** shaohe_feng has joined #openstack-meeting-422:50
*** bpokorny has quit IRC22:51
*** ninag has joined #openstack-meeting-422:52
*** spzala has joined #openstack-meeting-422:52
*** ninag has quit IRC22:57
*** azbiswas has quit IRC22:58
*** shaohe_feng has quit IRC23:00
*** lakshmiS has quit IRC23:01
*** shaohe_feng has joined #openstack-meeting-423:01
*** emagana has quit IRC23:01
*** sdague has quit IRC23:01
*** spzala has quit IRC23:02
*** rbak has quit IRC23:05
*** sridhar_ram has quit IRC23:05
*** sridhar_ram has joined #openstack-meeting-423:06
*** dave-mcc_ has quit IRC23:06
*** unicell has quit IRC23:06
*** unicell has joined #openstack-meeting-423:07
*** emagana has joined #openstack-meeting-423:07
*** Sukhdev has joined #openstack-meeting-423:09
*** LouisF has quit IRC23:09
*** tonytan4ever has quit IRC23:09
*** shaohe_feng has quit IRC23:10
*** pmesserli has quit IRC23:11
*** shaohe_feng has joined #openstack-meeting-423:13
*** mjblack has joined #openstack-meeting-423:13
*** andymaier has quit IRC23:16
*** dcwangmit01 has quit IRC23:17
*** dcwangmit01 has joined #openstack-meeting-423:17
*** shaohe_feng has quit IRC23:21
*** shaohe_feng has joined #openstack-meeting-423:21
*** dcwangmit01 has quit IRC23:21
*** dcwangmit01 has joined #openstack-meeting-423:21
*** dcwangmit01 has quit IRC23:23
*** dcwangmit01 has joined #openstack-meeting-423:23
*** Swami has quit IRC23:24
*** cdelatte has quit IRC23:25
*** daneyon has joined #openstack-meeting-423:26
*** markvoelker has joined #openstack-meeting-423:26
*** bobh has joined #openstack-meeting-423:26
*** bpokorny_ has quit IRC23:28
*** bpokorny has joined #openstack-meeting-423:29
*** markvoelker has quit IRC23:31
*** shaohe_feng has quit IRC23:31
*** shaohe_feng has joined #openstack-meeting-423:31
*** galstrom_zzz is now known as galstrom23:33
*** bobh has quit IRC23:34
*** cwolferh has joined #openstack-meeting-423:35
*** daneyon_ has joined #openstack-meeting-423:36
*** daneyon has quit IRC23:36
*** antonyfm has quit IRC23:36
*** emagana has quit IRC23:38
*** emagana has joined #openstack-meeting-423:39
*** trozet has quit IRC23:40
*** shaohe_feng has quit IRC23:41
*** shaohe_feng has joined #openstack-meeting-423:42
*** emagana has quit IRC23:43
*** brucet_ has joined #openstack-meeting-423:47
*** Sukhdev has quit IRC23:48
*** shaohe_feng has quit IRC23:51
*** shaohe_feng has joined #openstack-meeting-423:52
*** galstrom is now known as galstrom_zzz23:54
*** emagana has joined #openstack-meeting-423:54
*** emagana has quit IRC23:57
*** gangil has quit IRC23:57
*** emagana has joined #openstack-meeting-423:57
*** gangil has joined #openstack-meeting-423:59
*** SumitNaiksatam has quit IRC23:59

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