Thursday, 2016-05-26

*** openstack has joined #openstack-meeting-400:04
*** ChanServ sets mode: +o openstack00:04
*** sdake has quit IRC00:06
*** chem`` has quit IRC00:07
*** sdake has joined #openstack-meeting-400:08
*** nmadhok1 has quit IRC00:10
*** nmadhok has joined #openstack-meeting-400:10
*** takashin has joined #openstack-meeting-400:11
*** takashin has left #openstack-meeting-400:11
*** shaohe_feng has quit IRC00:11
*** shaohe_feng has joined #openstack-meeting-400:12
*** bobh has joined #openstack-meeting-400:12
*** sdague has joined #openstack-meeting-400:13
*** vishwana_ has quit IRC00:14
*** sarob has joined #openstack-meeting-400:18
*** _sarob has joined #openstack-meeting-400:19
*** khushbu has joined #openstack-meeting-400:19
*** shaohe_feng has quit IRC00:21
*** shaohe_feng has joined #openstack-meeting-400:22
*** sarob has quit IRC00:23
*** baoli has joined #openstack-meeting-400:25
*** klamath has quit IRC00:25
*** klamath has joined #openstack-meeting-400:25
*** bobh has quit IRC00:26
*** antongribok has joined #openstack-meeting-400:26
*** ddieterly has joined #openstack-meeting-400:27
*** bobh has joined #openstack-meeting-400:27
*** sdake_ has joined #openstack-meeting-400:28
*** bpokorny has quit IRC00:29
*** bpokorny has joined #openstack-meeting-400:29
*** bpokorny has quit IRC00:30
*** bpokorny has joined #openstack-meeting-400:30
*** sdake has quit IRC00:30
*** bobh has quit IRC00:31
*** shaohe_feng has quit IRC00:32
*** bpokorny has quit IRC00:32
*** _sarob has quit IRC00:32
*** bpokorny has joined #openstack-meeting-400:32
*** thorst_ has joined #openstack-meeting-400:33
*** shaohe_feng has joined #openstack-meeting-400:34
*** shaohe_feng has quit IRC00:42
*** bobh has joined #openstack-meeting-400:42
*** shaohe_feng has joined #openstack-meeting-400:42
*** vishwanathj has joined #openstack-meeting-400:44
*** khushbu has quit IRC00:44
*** banix has joined #openstack-meeting-400:48
*** zenoway has quit IRC00:48
*** sballe_ has quit IRC00:48
*** khushbu_ has joined #openstack-meeting-400:49
*** zenoway has joined #openstack-meeting-400:49
*** sdake_ has quit IRC00:50
*** openstack has joined #openstack-meeting-400:56
*** ChanServ sets mode: +o openstack00:56
*** shaohe_feng has quit IRC01:02
*** shaohe_feng has joined #openstack-meeting-401:03
*** pabelanger has left #openstack-meeting-401:03
*** zhurong has joined #openstack-meeting-401:04
*** aglarendil has quit IRC01:05
*** bpokorny has quit IRC01:06
*** aglarendil has joined #openstack-meeting-401:06
*** hvprash has joined #openstack-meeting-401:09
*** piet has quit IRC01:10
*** tonytan4ever has joined #openstack-meeting-401:11
*** JRobinson__ has joined #openstack-meeting-401:11
*** ddieterly is now known as ddieterly[away]01:11
*** ddieterly[away] is now known as ddieterly01:12
*** shaohe_feng has quit IRC01:13
*** gangil has quit IRC01:13
*** shaohe_feng has joined #openstack-meeting-401:13
*** gangil has joined #openstack-meeting-401:16
*** piet has joined #openstack-meeting-401:18
*** xiexianbin has joined #openstack-meeting-401:21
*** pvaneck has quit IRC01:23
*** shaohe_feng has quit IRC01:23
*** shaohe_feng has joined #openstack-meeting-401:23
*** nmadhok1 has joined #openstack-meeting-401:24
*** nmadhok has quit IRC01:24
*** sdake has quit IRC01:25
*** piet has quit IRC01:31
*** ddieterly has quit IRC01:33
*** shaohe_feng has quit IRC01:33
*** shaohe_feng has joined #openstack-meeting-401:34
*** zhurong has quit IRC01:35
*** zhurong has joined #openstack-meeting-401:36
*** nmadhok has joined #openstack-meeting-401:39
*** nmadhok1 has quit IRC01:39
*** shaohe_feng has quit IRC01:43
*** shaohe_feng has joined #openstack-meeting-401:44
*** tfukushima has joined #openstack-meeting-401:44
*** xiexianbin is now known as a01:45
*** a is now known as b01:45
*** b is now known as d01:46
*** d is now known as e01:46
*** e is now known as f01:46
*** kebray has quit IRC01:46
*** f is now known as Guest5024301:46
*** ddieterly has joined #openstack-meeting-401:47
*** Guest50243 is now known as a01:47
*** a is now known as Guest8181101:48
*** salv-orlando has joined #openstack-meeting-401:48
*** kebray has joined #openstack-meeting-401:49
*** Guest81811 is now known as l01:49
*** l is now known as Guest4641001:50
*** yamamot__ has joined #openstack-meeting-401:50
*** salv-orlando has quit IRC01:50
*** ddieterly is now known as ddieterly[away]01:51
*** ddieterly[away] is now known as ddieterly01:51
*** uck has joined #openstack-meeting-401:53
*** shaohe_feng has quit IRC01:54
*** Guest46410 has left #openstack-meeting-401:54
*** tonytan4ever has quit IRC01:55
*** shaohe_feng has joined #openstack-meeting-401:57
*** uck has quit IRC01:58
*** barmaley has joined #openstack-meeting-401:59
*** s3wong has quit IRC02:01
*** nmadhok has quit IRC02:03
*** shaohe_feng has quit IRC02:04
*** barmaley has quit IRC02:04
*** shaohe_feng has joined #openstack-meeting-402:05
*** barmaley has joined #openstack-meeting-402:05
*** yamamot__ has quit IRC02:05
*** nmadhok has joined #openstack-meeting-402:05
*** uck has joined #openstack-meeting-402:07
*** bobh has quit IRC02:09
*** uck has quit IRC02:11
*** shaohe_feng has quit IRC02:14
*** shaohe_feng has joined #openstack-meeting-402:15
*** ddieterly has quit IRC02:15
*** sdague has quit IRC02:15
*** sdake has joined #openstack-meeting-402:19
*** shaohe_feng has quit IRC02:24
*** asti has quit IRC02:25
*** gangil has quit IRC02:25
*** shaohe_feng has joined #openstack-meeting-402:25
*** antongribok has quit IRC02:30
*** hvprash has quit IRC02:33
*** shaohe_feng has quit IRC02:35
*** shaohe_feng has joined #openstack-meeting-402:36
*** raddaoui has quit IRC02:37
*** openstack has joined #openstack-meeting-402:40
*** ChanServ sets mode: +o openstack02:40
*** unicell has quit IRC02:40
*** vishwanathj has quit IRC02:41
*** shaohe_feng has quit IRC02:45
*** shaohe_feng has joined #openstack-meeting-402:46
*** thorst_ has quit IRC02:51
*** thorst_ has joined #openstack-meeting-402:52
*** zenoway has joined #openstack-meeting-402:55
*** shaohe_feng has quit IRC02:55
*** gangil has joined #openstack-meeting-402:56
*** shaohe_feng has joined #openstack-meeting-402:56
*** ddieterly has joined #openstack-meeting-402:57
*** zenoway has quit IRC02:59
*** zhurong has quit IRC02:59
*** zhurong has joined #openstack-meeting-403:00
*** thorst_ has quit IRC03:00
*** sdake_ has joined #openstack-meeting-403:00
*** sdake has quit IRC03:02
*** shaohe_feng has quit IRC03:05
*** sdake_ is now known as sdake03:05
*** shaohe_feng has joined #openstack-meeting-403:06
*** vishwanathj has joined #openstack-meeting-403:06
*** unicell has joined #openstack-meeting-403:09
*** unicell has quit IRC03:14
*** shaohe_feng has quit IRC03:16
*** shaohe_feng has joined #openstack-meeting-403:16
*** unicell has joined #openstack-meeting-403:16
*** KanagarajM has joined #openstack-meeting-403:17
*** JRobinson__ is now known as JRobinson__afk03:18
*** julim has joined #openstack-meeting-403:24
*** ddieterly is now known as ddieterly[away]03:25
*** ddieterly[away] is now known as ddieterly03:25
*** ddieterly is now known as ddieterly[away]03:25
*** shaohe_feng has quit IRC03:26
*** baoli has quit IRC03:26
*** shaohe_feng has joined #openstack-meeting-403:27
*** julim has quit IRC03:30
*** zenoway has joined #openstack-meeting-403:30
*** armax has quit IRC03:32
*** zenoway has quit IRC03:35
*** nmadhok has quit IRC03:35
*** shaohe_feng has quit IRC03:36
*** KanagarajM has left #openstack-meeting-403:36
*** shaohe_feng has joined #openstack-meeting-403:37
*** fawadkhaliq has joined #openstack-meeting-403:42
*** banix has quit IRC03:44
*** JRobinson__afk has quit IRC03:44
*** piet has joined #openstack-meeting-403:46
*** shaohe_feng has quit IRC03:46
*** shaohe_feng has joined #openstack-meeting-403:47
*** fawadkhaliq has quit IRC03:56
*** shaohe_feng has quit IRC03:57
*** thorst_ has joined #openstack-meeting-403:58
*** shaohe_feng has joined #openstack-meeting-403:58
*** JRobinson__ has joined #openstack-meeting-403:58
*** ramishra has quit IRC03:59
*** nmadhok has joined #openstack-meeting-404:01
*** piet has quit IRC04:03
*** iyamahat has joined #openstack-meeting-404:03
*** thorst_ has quit IRC04:05
*** shaohe_feng has quit IRC04:07
*** shaohe_feng has joined #openstack-meeting-404:08
*** yamahata has joined #openstack-meeting-404:17
*** shaohe_feng has quit IRC04:17
*** shaohe_feng has joined #openstack-meeting-404:18
*** nmadhok has quit IRC04:24
*** nmadhok has joined #openstack-meeting-404:24
*** ddieterly[away] has quit IRC04:25
*** baoli has joined #openstack-meeting-404:27
*** shaohe_feng has quit IRC04:27
*** javeriak has joined #openstack-meeting-404:27
*** shaohe_feng has joined #openstack-meeting-404:28
*** barmaley has quit IRC04:30
*** hvprash has joined #openstack-meeting-404:34
*** shaohe_feng has quit IRC04:38
*** shaohe_feng has joined #openstack-meeting-404:38
*** JRobinson__ has quit IRC04:38
*** hvprash has quit IRC04:39
*** salv-orlando has joined #openstack-meeting-404:41
*** irenab has quit IRC04:44
*** iyamahat has quit IRC04:44
*** shaohe_feng has quit IRC04:48
*** khushbu_ has quit IRC04:48
*** shaohe_feng has joined #openstack-meeting-404:48
*** salv-orlando has quit IRC04:48
*** tfukushima has quit IRC04:50
*** irenab has joined #openstack-meeting-404:52
*** Niham has joined #openstack-meeting-404:56
*** fawadkhaliq has joined #openstack-meeting-404:57
*** shaohe_feng has quit IRC04:58
*** vishnoianil has quit IRC04:59
*** shaohe_feng has joined #openstack-meeting-405:01
*** sacharya has quit IRC05:01
*** thorst_ has joined #openstack-meeting-405:03
*** salv-orlando has joined #openstack-meeting-405:05
*** kebray has quit IRC05:05
*** shaohe_feng has quit IRC05:08
*** kebray has joined #openstack-meeting-405:09
*** shaohe_feng has joined #openstack-meeting-405:09
*** thorst_ has quit IRC05:09
*** javeriak has quit IRC05:13
*** dave-mccowan has quit IRC05:13
*** GB21 has joined #openstack-meeting-405:15
*** shaohe_feng has quit IRC05:19
*** shaohe_feng has joined #openstack-meeting-405:19
*** GB21 has quit IRC05:21
*** yamamot__ has joined #openstack-meeting-405:21
*** shaohe_feng has quit IRC05:29
*** shaohe_feng has joined #openstack-meeting-405:29
*** bnemec has quit IRC05:30
*** javeriak has joined #openstack-meeting-405:31
*** bnemec has joined #openstack-meeting-405:31
*** anilvenkata has joined #openstack-meeting-405:31
*** irenab has quit IRC05:34
*** irenab has joined #openstack-meeting-405:39
*** shaohe_feng has quit IRC05:39
*** baoli has quit IRC05:39
*** barmaley has joined #openstack-meeting-405:40
*** shaohe_feng has joined #openstack-meeting-405:40
*** irenab has quit IRC05:43
*** bnemec has quit IRC05:44
*** javeriak has quit IRC05:46
*** GB21 has joined #openstack-meeting-405:47
*** vishnoianil has joined #openstack-meeting-405:48
*** shaohe_feng has quit IRC05:49
*** shaohe_feng has joined #openstack-meeting-405:50
*** tfukushima has joined #openstack-meeting-405:50
*** bnemec has joined #openstack-meeting-405:52
*** unicell1 has joined #openstack-meeting-405:53
*** sdake has quit IRC05:54
*** belmoreira has joined #openstack-meeting-405:54
*** unicell has quit IRC05:54
*** irenab has joined #openstack-meeting-405:58
*** sdake has joined #openstack-meeting-405:59
*** barmaley has quit IRC05:59
*** shaohe_feng has quit IRC06:00
*** shaohe_feng has joined #openstack-meeting-406:00
*** sacharya has joined #openstack-meeting-406:01
*** hvprash has joined #openstack-meeting-406:02
*** GB21 has quit IRC06:05
*** sacharya has quit IRC06:06
*** thorst_ has joined #openstack-meeting-406:07
*** shaohe_feng has quit IRC06:10
*** shaohe_feng has joined #openstack-meeting-406:11
*** bnemec has quit IRC06:12
*** bnemec has joined #openstack-meeting-406:14
*** thorst_ has quit IRC06:14
*** hvprash has quit IRC06:15
*** irenab has quit IRC06:15
*** pas-ha has left #openstack-meeting-406:18
*** irenab has joined #openstack-meeting-406:18
*** GB21 has joined #openstack-meeting-406:19
*** shaohe_feng has quit IRC06:20
*** shaohe_feng has joined #openstack-meeting-406:21
*** irenab has quit IRC06:23
*** bnemec has quit IRC06:23
*** sdake has quit IRC06:30
*** irenab has joined #openstack-meeting-406:30
*** shaohe_feng has quit IRC06:30
*** numans has joined #openstack-meeting-406:31
*** shaohe_feng has joined #openstack-meeting-406:31
*** May-meimei has quit IRC06:32
*** bnemec has joined #openstack-meeting-406:36
*** vishwanathj has quit IRC06:37
*** May-meimei has joined #openstack-meeting-406:37
*** paul-carlton2 has joined #openstack-meeting-406:38
*** javeriak has joined #openstack-meeting-406:38
*** shaohe_feng has quit IRC06:41
*** shaohe_feng has joined #openstack-meeting-406:41
*** dshakhray has joined #openstack-meeting-406:41
*** irenab has quit IRC06:42
*** vtech_ has quit IRC06:43
*** zenoway has joined #openstack-meeting-406:43
*** shaohe_feng has quit IRC06:51
*** shaohe_feng has joined #openstack-meeting-406:52
*** openstack has joined #openstack-meeting-406:55
*** ChanServ sets mode: +o openstack06:55
*** javeriak has quit IRC06:58
*** javeriak has joined #openstack-meeting-406:59
*** gangil has quit IRC06:59
*** shaohe_feng has quit IRC07:01
*** shaohe_feng has joined #openstack-meeting-407:02
*** vtech has joined #openstack-meeting-407:02
*** salv-orlando has quit IRC07:05
*** cfarquhar has quit IRC07:07
*** Niham has quit IRC07:08
*** irenab has joined #openstack-meeting-407:09
*** shaohe_feng has quit IRC07:11
*** thorst_ has joined #openstack-meeting-407:12
*** shaohe_feng has joined #openstack-meeting-407:12
*** sdake has quit IRC07:13
*** markvoelker has quit IRC07:13
*** sdake has joined #openstack-meeting-407:16
*** thorst_ has quit IRC07:20
*** jed56 has joined #openstack-meeting-407:20
*** cfarquhar has joined #openstack-meeting-407:20
*** cfarquhar has quit IRC07:20
*** cfarquhar has joined #openstack-meeting-407:20
*** sdake has quit IRC07:21
*** shaohe_feng has quit IRC07:22
*** shaohe_feng has joined #openstack-meeting-407:22
*** salv-orlando has joined #openstack-meeting-407:24
*** shaohe_feng has quit IRC07:32
*** shaohe_feng has joined #openstack-meeting-407:33
*** chem`` has joined #openstack-meeting-407:41
*** shaohe_feng has quit IRC07:42
*** shaohe_feng has joined #openstack-meeting-407:43
*** sdake has joined #openstack-meeting-407:44
*** sdake has quit IRC07:49
*** sdake has joined #openstack-meeting-407:50
*** shaohe_feng has quit IRC07:52
*** shaohe_feng has joined #openstack-meeting-407:53
*** zhurong_ has joined #openstack-meeting-407:57
*** paul-carlton2 has quit IRC07:58
*** matrohon has joined #openstack-meeting-408:00
*** zhurong has quit IRC08:01
*** javeriak has quit IRC08:02
*** shaohe_feng has quit IRC08:03
*** sacharya has joined #openstack-meeting-408:03
*** shaohe_feng has joined #openstack-meeting-408:03
*** salv-orlando has quit IRC08:04
*** vtech has quit IRC08:07
*** vtech_ has joined #openstack-meeting-408:07
*** sacharya has quit IRC08:08
*** javeriak has joined #openstack-meeting-408:08
*** ihrachys has joined #openstack-meeting-408:12
*** shaohe_feng has quit IRC08:13
*** Niham has joined #openstack-meeting-408:13
*** shaohe_feng has joined #openstack-meeting-408:14
*** thorst_ has joined #openstack-meeting-408:17
*** javeriak has quit IRC08:18
*** javeriak has joined #openstack-meeting-408:19
*** shaohe_feng has quit IRC08:23
*** shaohe_feng has joined #openstack-meeting-408:23
*** thorst_ has quit IRC08:25
*** shaohe_feng has quit IRC08:33
*** sshnaidm has quit IRC08:34
*** shaohe_feng has joined #openstack-meeting-408:34
*** fwdit has joined #openstack-meeting-408:36
*** matrohon has quit IRC08:37
*** matrohon has joined #openstack-meeting-408:38
*** alexchadin has joined #openstack-meeting-408:39
*** shaohe_feng has quit IRC08:44
*** shaohe_feng has joined #openstack-meeting-408:44
*** pbourke_ has quit IRC08:48
*** pbourke_ has joined #openstack-meeting-408:48
*** shaohe_feng has quit IRC08:54
*** shaohe_feng has joined #openstack-meeting-408:54
*** irenab has quit IRC08:57
*** matrohon has quit IRC09:04
*** shaohe_feng has quit IRC09:04
*** mfedosin has joined #openstack-meeting-409:05
*** shaohe_feng has joined #openstack-meeting-409:05
*** matrohon has joined #openstack-meeting-409:05
*** irenab has joined #openstack-meeting-409:05
*** GB21 has quit IRC09:06
*** GB21 has joined #openstack-meeting-409:09
*** mfedosin has quit IRC09:09
*** watanabe_isao has quit IRC09:13
*** markvoelker has joined #openstack-meeting-409:14
*** shaohe_feng has quit IRC09:14
*** shaohe_feng has joined #openstack-meeting-409:15
*** barmaley has joined #openstack-meeting-409:17
*** wznoinsk_ is now known as wznoinsk09:17
*** barmaley has quit IRC09:17
*** barmaley has joined #openstack-meeting-409:18
*** sambetts|afk is now known as sambetts09:18
*** markvoelker has quit IRC09:21
*** thorst_ has joined #openstack-meeting-409:22
*** mfedosin has joined #openstack-meeting-409:24
*** shaohe_feng has quit IRC09:25
*** shaohe_feng has joined #openstack-meeting-409:25
*** GB21 has quit IRC09:26
*** matrohon has quit IRC09:28
*** matrohon has joined #openstack-meeting-409:29
*** sshnaidm has joined #openstack-meeting-409:30
*** thorst_ has quit IRC09:30
*** GB21 has joined #openstack-meeting-409:32
*** tinx_ is now known as tinx09:34
*** shaohe_feng has quit IRC09:35
*** shaohe_feng has joined #openstack-meeting-409:35
*** salv-orlando has joined #openstack-meeting-409:36
*** matrohon has quit IRC09:37
*** matrohon has joined #openstack-meeting-409:38
*** shaohe_feng has quit IRC09:45
*** shaohe_feng has joined #openstack-meeting-409:46
*** yamamot__ has quit IRC09:50
*** sdague has joined #openstack-meeting-409:51
*** shaohe_feng has quit IRC09:55
*** shaohe_feng has joined #openstack-meeting-409:56
*** fawadkhaliq has quit IRC09:57
*** fawadkhaliq has joined #openstack-meeting-409:58
*** javeriak_ has joined #openstack-meeting-409:58
*** javeriak has quit IRC09:58
*** sacharya has joined #openstack-meeting-410:04
*** shaohe_feng has quit IRC10:06
*** zhurong_ has quit IRC10:08
*** shaohe_feng has joined #openstack-meeting-410:08
*** sacharya has quit IRC10:09
*** tfukushima has quit IRC10:10
*** daneel is now known as Guest5680410:11
*** tfukushima has joined #openstack-meeting-410:11
*** tfukushima has quit IRC10:11
*** tfukushima has joined #openstack-meeting-410:11
*** tfukushima has quit IRC10:13
*** tfukushima has joined #openstack-meeting-410:14
*** shaohe_feng has quit IRC10:16
*** shaohe_feng has joined #openstack-meeting-410:16
*** barmaley has quit IRC10:20
*** GB21 has quit IRC10:21
*** _degorenko|afk is now known as degorenko10:24
*** shaohe_feng has quit IRC10:26
*** shaohe_feng has joined #openstack-meeting-410:27
*** thorst_ has joined #openstack-meeting-410:28
*** rtheis has joined #openstack-meeting-410:31
*** thorst_ has quit IRC10:35
*** nmadhok has quit IRC10:36
*** shaohe_feng has quit IRC10:36
*** shaohe_feng has joined #openstack-meeting-410:37
*** alexchadin has quit IRC10:41
*** GB21 has joined #openstack-meeting-410:43
*** tfukushima has quit IRC10:46
*** shaohe_feng has quit IRC10:47
*** shaohe_feng has joined #openstack-meeting-410:47
*** shaohe_feng has quit IRC10:57
*** shaohe_feng has joined #openstack-meeting-410:58
*** shaohe_feng has quit IRC11:07
*** shaohe_feng has joined #openstack-meeting-411:08
*** Niham has quit IRC11:15
*** markvoelker has joined #openstack-meeting-411:16
*** shaohe_feng has quit IRC11:17
*** shaohe_feng has joined #openstack-meeting-411:18
*** markvoelker has quit IRC11:21
*** shaohe_feng has quit IRC11:28
*** shaohe_feng has joined #openstack-meeting-411:29
*** julim has joined #openstack-meeting-411:32
*** asti has joined #openstack-meeting-411:33
*** shaohe_feng has quit IRC11:38
*** woodard has joined #openstack-meeting-411:38
*** shaohe_feng has joined #openstack-meeting-411:39
*** woodard has quit IRC11:39
*** woodard has joined #openstack-meeting-411:40
*** shaohe_feng has quit IRC11:48
*** shaohe_feng has joined #openstack-meeting-411:49
*** thorst_ has joined #openstack-meeting-411:49
*** yamamoto has joined #openstack-meeting-411:56
*** javeriak_ has quit IRC11:57
*** shaohe_feng has quit IRC11:58
*** shaohe_feng has joined #openstack-meeting-411:59
*** julim has quit IRC12:03
*** sacharya has joined #openstack-meeting-412:04
*** markvoelker has joined #openstack-meeting-412:08
*** sacharya has quit IRC12:09
*** shaohe_feng has quit IRC12:09
*** iyamahat has joined #openstack-meeting-412:09
*** shaohe_feng has joined #openstack-meeting-412:09
*** javeriak has joined #openstack-meeting-412:10
*** iyamahat has quit IRC12:12
*** yamahata has quit IRC12:12
*** ddieterly has joined #openstack-meeting-412:13
*** piet has joined #openstack-meeting-412:14
*** shaohe_feng has quit IRC12:19
*** matrohon has quit IRC12:19
*** shaohe_feng has joined #openstack-meeting-412:20
*** matrohon has joined #openstack-meeting-412:21
*** GB21 has quit IRC12:22
*** ddieterly is now known as ddieterly[away]12:23
*** klamath has quit IRC12:26
*** klamath has joined #openstack-meeting-412:26
*** piet has quit IRC12:27
*** shaohe_feng has quit IRC12:29
*** shaohe_feng has joined #openstack-meeting-412:30
*** yamamoto has quit IRC12:30
*** yamamoto has joined #openstack-meeting-412:30
*** piet has joined #openstack-meeting-412:39
*** dave-mccowan has joined #openstack-meeting-412:39
*** shaohe_feng has quit IRC12:39
*** shaohe_feng has joined #openstack-meeting-412:40
*** salv-orlando has quit IRC12:42
*** ddieterly[away] is now known as ddieterly12:42
*** salv-orlando has joined #openstack-meeting-412:44
*** baoli has joined #openstack-meeting-412:46
*** claudiub has joined #openstack-meeting-412:47
*** fwdit has quit IRC12:49
*** julim has joined #openstack-meeting-412:49
*** baoli_ has joined #openstack-meeting-412:49
*** shaohe_feng has quit IRC12:50
*** shaohe_feng has joined #openstack-meeting-412:50
*** hvprash has joined #openstack-meeting-412:51
*** zhurong has joined #openstack-meeting-412:51
*** baoli has quit IRC12:52
*** yamamoto has quit IRC12:52
*** piet has quit IRC12:53
*** yamamoto has joined #openstack-meeting-412:54
*** hvprash_ has joined #openstack-meeting-412:59
*** shaohe_feng has quit IRC13:00
*** shaohe_feng has joined #openstack-meeting-413:01
*** vhoward has joined #openstack-meeting-413:01
*** ddieterly has quit IRC13:01
*** hvprash has quit IRC13:03
*** kylek3h has joined #openstack-meeting-413:04
*** pmesserli has joined #openstack-meeting-413:04
*** shaohe_feng has quit IRC13:10
*** shaohe_feng has joined #openstack-meeting-413:11
*** bobh has joined #openstack-meeting-413:14
*** croelandt has joined #openstack-meeting-413:15
*** spzala has joined #openstack-meeting-413:17
*** shaohe_feng has quit IRC13:20
*** piet has joined #openstack-meeting-413:20
*** shaohe_feng has joined #openstack-meeting-413:21
*** yamamoto has quit IRC13:23
*** matrohon has quit IRC13:26
*** javeriak has quit IRC13:26
*** abhishek has joined #openstack-meeting-413:27
*** javeriak has joined #openstack-meeting-413:28
*** banix has joined #openstack-meeting-413:30
*** shaohe_feng has quit IRC13:31
*** shaohe_feng has joined #openstack-meeting-413:31
*** yamamoto has joined #openstack-meeting-413:33
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting-413:40
*** shaohe_feng has quit IRC13:41
*** javeriak has quit IRC13:41
*** dave-mccowan has quit IRC13:42
*** shaohe_feng has joined #openstack-meeting-413:42
*** javeriak has joined #openstack-meeting-413:42
*** spotz_zzz is now known as spotz13:43
*** javeriak has quit IRC13:46
*** matrohon has joined #openstack-meeting-413:47
*** ddieterly has joined #openstack-meeting-413:49
*** yamamoto has quit IRC13:50
*** shaohe_feng has quit IRC13:51
*** shaohe_feng has joined #openstack-meeting-413:52
*** bunting has joined #openstack-meeting-413:55
*** kairat has joined #openstack-meeting-414:00
*** shaohe_feng has quit IRC14:01
*** tsymanczyk has joined #openstack-meeting-414:02
*** shaohe_feng has joined #openstack-meeting-414:02
mfedosinwhere's Glance meeting?14:02
nikhil#startmeeting glance14:03
openstackMeeting started Thu May 26 14:03:08 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: glance)"14:03
openstackThe meeting name has been set to 'glance'14:03
mfedosino/14:03
tsymanczyk\o14:03
flaper87o/14:03
dshakhrayo/14:03
rosmaitao/14:03
nikhilCourtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat14:03
hemanthmo/14:03
wxyo/14:03
sigmavirus24o/14:03
jokke_\o14:03
nikhilfor some reason my previous message did not go through14:03
* nikhil had to restart irc14:04
*** yamamoto has joined #openstack-meeting-414:04
jokke_ah14:04
nikhil#topic agenda14:04
mfedosinlet's beging then14:04
*** openstack changes topic to "agenda (Meeting topic: glance)"14:04
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:04
kairato/14:04
nikhilSmall agenda today14:04
nikhilsome people haven't read my mails14:05
nikhilLet's get to that later.14:05
nikhil#topic Updates14:05
*** openstack changes topic to "Updates (Meeting topic: glance)"14:05
*** sacharya has joined #openstack-meeting-414:05
nikhil#info Glare updates ( mfedosin , nikhil )14:05
buntingo/14:05
mfedosinwe finished the spec and waiting for reviews :)14:06
croelandto/14:06
mfedosin#link https://review.openstack.org/#/c/283136/14:06
mfedosinthere are a lot of use cases and examples, that should help you (in theory) to understand how API works14:07
*** sudipto has joined #openstack-meeting-414:07
mfedosinso if you have time leave your comments there14:07
mfedosinthanks in advance :)14:07
*** scsnow_ has joined #openstack-meeting-414:08
*** rbak has joined #openstack-meeting-414:08
mfedosinalso we are working on tests for Glare14:08
*** jmckind has joined #openstack-meeting-414:08
mfedosinI think we will present code for review on 6th of June14:09
mfedosinif you have any questions I'm happy to answer14:09
*** sacharya has quit IRC14:10
*** scsnow has quit IRC14:10
nikhilI have a few things to update/add14:10
mfedosinnikhil: shoot :)14:10
nikhilthat I've mentioned to mfedosin14:10
nikhil#1. Let's work on only a POC14:10
nikhil#2. All things upstream to help engage community in discussion and code. So, no internal discussions after a POC and openstack usualy channels based communication and development.14:11
*** shaohe_feng has quit IRC14:12
nikhil#3. Dissolving the ownership quotient -- since this is not a feature and entire service, we need everyone on the same page and ability to contribute. Let's provide a platform for that.14:12
mfedosinnikhil: also we decided that API will be marked as 'experimental' initially14:12
nikhil#4. Newton priority for Glare should be bare-bone code that will be used by a couple of early adopters that will help us evolve the API. By newton-3 we need to target a stable API.14:13
nikhil#5. Stop all discussions on extra features and work on builing the community right after a POC is ready for review. (something not a WIP and set up in small patches easier to review and contribute as applicable)14:13
nikhil#6. All bugs and stabilization should be done using LP and Mike was going to help setup a etherpad for that to enable pick up tasks/bugs to contribute.14:14
nikhilmfedosin: right, the 'experimental' within newton but Current by newton-314:14
nikhilmfedosin: anything else?14:14
mfedosin#7. Glare should be awesome14:15
nikhil++14:15
mfedosin^ it's the basic requirement :)14:15
nikhilIt will be -- all awesome people work in Glance.14:15
nikhilmoving on14:15
mfedosinthanks nikhil14:16
nikhil#info Nova v1, v2 (mfedosin, sudipto)14:16
mfedosinokay, I added unit tests there14:16
mfedosin#link https://review.openstack.org/#/c/321551/14:16
mfedosinnow there are 1750 LOC :)14:17
mfedosintoday I'll upload code for XEN14:17
mfedosinthen we have to wait for reviews14:18
mfedosinyesterday multinode gates were broken and Jenkins put -1 for that reason14:18
* nikhil can be added to the reviews when they are posted/ready14:19
mfedosinnikhil: sure, in a couple of hours14:19
nikhilnp, that's in general14:20
*** zhurong has quit IRC14:20
nikhilok, let's move on then14:20
nikhilThanks mfedosin14:20
*** zhurong has joined #openstack-meeting-414:21
mfedosinI'll add Matt, Sean and other Nova team members then14:21
*** shaohe_feng has joined #openstack-meeting-414:21
nikhilwell you'd ask them before you add14:21
mfedosinas reviewers14:21
*** raddaoui has joined #openstack-meeting-414:21
mfedosinbut I have to mention...14:21
mfedosinit's the final time I rewrite this code :)14:22
flaper87my changes for devstack are still pending review14:22
flaper87I'll probably start pinging ppl aggressively14:22
tsymanczyki think that's reasonable.14:22
mfedosinflaper87: give us the link14:22
*** shaohe_feng has quit IRC14:22
jokke_mfedosin: not blaming you for that14:22
nikhilflaper87: ++14:22
flaper87#link https://review.openstack.org/#/c/315190/14:22
flaper87mfedosin: it's a devstack review, I'll start pinging devstack folks14:23
flaper87:D14:23
flaper87mfedosin: you're fine14:23
flaper87:)14:23
flaper87... for now14:23
flaper87:P14:23
*** shaohe_feng has joined #openstack-meeting-414:23
jokke_flaper87: you give us the link, we keep it at the top of the list with nagging comments :D14:23
mfedosinI don't want to rewrite it from scratch again :(14:24
nikhilok, let's move on here14:24
nikhil#topic Releases (nikhil)14:24
*** openstack changes topic to "Releases (nikhil) (Meeting topic: glance)"14:24
nikhil#info newton-1 next Tuesday May 31st14:24
*** spzala has quit IRC14:25
nikhilSo, if anyone sees anything outstanding that needs to go in newton-1 let me know _today_14:25
nikhilthere's no release liaison in newton so, I am handling releases14:25
nikhilAlso, I think we can take the opportunity to propose a release for the client and store next week around Thursday14:26
nikhilthat way glance reviewers will have focus on knocking out release specific stuff14:26
nikhilthe release itself may not go through until later (as and when release team gets time to get those released)14:26
*** cwolferh has quit IRC14:26
nikhilmoving on14:27
nikhil#topic Announcements (nikhil)14:27
*** openstack changes topic to "Announcements (nikhil) (Meeting topic: glance)"14:27
nikhilI sent a Best practices for meetings email14:27
jokke_nikhil: does Newton-1 (supposed) wirk with the latest release of store?14:27
* jokke_ haven't check14:27
nikhiljokke_: me neither. but that's a detail. we can time the releases to make stuff work (whether to release store before or after newton-1)14:28
nikhilon my note about meetings:14:28
nikhil#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/095599.html14:28
nikhilplease read that carefully14:28
nikhiltry to be faster in updates (and precise)14:29
*** b3rnard0 has left #openstack-meeting-414:29
nikhilany doubts or concerns?14:29
kairat    Please make sure you add your discussion topic at least 24 hours before the scheduled meeting.14:29
kairatCan we make exception for request for reviews?14:30
nikhilnope14:30
*** belmoreira has quit IRC14:30
flaper87I'd actually like to avoid using the meeting to request reviews14:30
flaper87unless the review requires some actual discussion14:30
nikhil++14:30
jokke_++14:30
kairatSo do we have an etherpad where we can track that14:30
kairatMaybe I missed that14:31
nikhilwhat?14:31
nikhilkairat: you are asking for tracking reviews?14:31
flaper87my advice would be to reach out to the people you need reviews from if really needed.14:31
jokke_or ping out at #openstack-glance14:31
flaper87Also, keep in mind that pinging/requesting reviews so frequently is not really nice14:31
flaper87but that might be just me14:31
*** salv-orlando has quit IRC14:31
nikhilflaper87: yes and no14:31
nikhilflaper87: sometime people want/need reminders if they get busy with internal stuff14:32
nikhilso, please check with individuals you are asking for reviews14:32
flaper87nikhil: note that I said "so frequently" ;)14:32
*** shaohe_feng has quit IRC14:32
nikhilflaper87: ok, thanks :-)14:32
flaper87I didn't generalized14:32
kairatOk, I was talking about etherpad with priority reviews for that week like for example Heat does14:32
nikhilflaper87: perfect14:32
nikhilkairat: ok, thanks for that clarification14:33
rosmaitakairat: +1 , more work for nikhil but would be really helpful14:33
*** shaohe_feng has joined #openstack-meeting-414:33
*** vishwanathj has joined #openstack-meeting-414:33
nikhilI used to do that before but many times people didn't pay attention14:34
jokke_I'm fine without one extra etherpad I forget to follow ;)14:34
nikhilI can look into that process a bit more. It's a bit of maintenance by itself.14:34
flaper87Unless people make checking the ehterpad an habit, I believe it's not really useful14:34
nikhilyeah, people have their own preferences14:34
flaper87The dashboard helped a lot during Mitaka (IMHO) and for the cases it didn't, I used to chase people down14:34
flaper87:P14:34
rosmaitanikhil: or maybe a demo of good gerrit practices -- i have mostly "folk knowledge" of gerrit, i'm sure i don't use it effieciently14:34
*** zhurong has quit IRC14:34
nikhilrosmaita: noted14:34
rosmaitalike, i guess i should look at flaper87 's dashboard more often14:35
hemanthmcan we do something on the dashboard to reflect the importance?14:35
kairat++ to hemanthm14:35
flaper87hemanthm: yes and no14:35
jokke_rosmaita: add the repos you need as followed under your settings, never go past page 2 unless you're bored and wanna clean up ;)14:35
flaper87I mean, it can be done but it's a bit hacked in as there's no support for proper hashtags in our version of gerrit14:35
flaper87What I did in mitaka is tag reviews with "Mitaka Priority" or something like that14:36
flaper87and have the dashboard run a regex there and group those14:36
kairatIt looks like too long discussion14:36
kairatwe can discuss that in e-mail I guess14:36
nikhilok, let's see if we can come up with something offline14:36
flaper87topics would work but they are overwritten on every new ps14:36
* flaper87 stf14:36
flaper87u14:36
hemanthmthanks flaper8714:36
nikhilflaper87: mind taking a action item for what all you did in mitaka?14:37
flaper87sure, I can write all that down if that helps14:37
flaper87:D14:37
nikhilthanks, that's what we were looking for14:37
nikhilwe can share knowledge on this14:37
nikhilon the meetings' etherpad best practices section14:38
nikhillook at our agenda pad starting line 21 right now14:38
nikhilI can take questions offline14:38
nikhil#topic Deleting images that arebeing used by Nova: do we want the same behaviour for raw and qcow2 images? (croelandt)14:39
*** openstack changes topic to "Deleting images that arebeing used by Nova: do we want the same behaviour for raw and qcow2 images? (croelandt) (Meeting topic: glance)"14:39
nikhilcroelandt: floor is yours14:39
croelandtso :)14:39
croelandtAt Red Hat, we have a customer that complains about the following issue:14:40
croelandt1) They create an image in glance14:40
croelandt2) they boot a VM in Nova using the image created in 1)14:40
croelandt3) they try to delete the image in glance14:40
croelandtNow, depending on the format of the image, it may or may not be deleted14:40
croelandtif it is a raw image, it is considered "in use" and cannot be deleted14:40
croelandtif it is a qcow image, it can be deleted14:40
croelandtWe were wondering whether the behaviour should become more "consistent" from a user point of view14:41
flaper87So, lemme try to expand on this a bit more, if you don't mind.14:41
mfedosindo they delete image with Nova?14:41
croelandtEven though we might have to use some tricks to make it happen in glance14:41
croelandtflaper87: sure14:41
croelandtmfedosin: no, they use "glance image-delete" iirc14:41
sigmavirus24== flaper8714:41
flaper87The customer is using ceph and therefore, on raw images, ceph is doing a COW and basically marking the image as in-use14:41
* sigmavirus24 was catching up sorry14:42
flaper87I think this is a ceph specific case and I'm not sure we should expose it through the API.14:42
flaper87I don't think this happens with other sotres, at least.14:42
*** woodard has quit IRC14:42
*** shaohe_feng has quit IRC14:42
nikhilflaper87: correct14:42
jokke_flaper87: ++14:42
flaper87So, is the question: We should forbid deleting glance images if there's an instance running?14:43
*** woodard has joined #openstack-meeting-414:43
flaper87well, I failed to ask that with proper english14:43
flaper87but you got it14:43
*** woodard has quit IRC14:43
mfedosinbut it's a big security issue14:43
jokke_ceph puts a lock on the file and prevents the deletion on that level14:43
*** shaohe_feng has joined #openstack-meeting-414:43
flaper87I'd say no as I don't think we should have that sort of dependencies14:43
mfedosinif image is public and it cannot be deleted14:43
mfedosinif somebody uses it14:43
flaper87mfedosin: exactly, plus a bunch of other things14:43
flaper87that would imply adding support for "force" deletes and who knows what else14:44
jokke_mfedosin: that means that someone has failed on the deployment as glance clearly does not own the image data14:44
mfedosinflaper87: frankly speaking we have a bunch of those issues from our customers as well with ceph14:45
nikhilI'd a chat with nova folks on this ceph case14:45
flaper87mfedosin: that's fine but I think it's a ceph specific case14:45
flaper87I don't think it's Glance's problem, TBH14:45
jokke_nikhil: flaper87 ++14:45
nikhilthe reason they want to support this off-the-band on-line usage of the image data in ceph pool as it's a popular way14:45
hemanthmDealing with this on the glance side means glance now has to keep track of image usage, which really shouldn't be a concern for Glance.14:46
nikhiland they have some in-tree workarounds to keep consistency with glance constructs14:46
flaper87hemanthm: right and we should also consider multi-clouds14:46
kairat++ to hemanthm14:46
flaper87I mean, in general, I don't think Glance should get in the business of tracking this14:47
nikhilso, like flaper87 and hemanthm are saying it's an edge case and should not be a top level feature in glance.14:47
rosmaita+114:47
flaper87Now, we do want to provide a better story for this, though. Is the scrubber the answer for this? Just have delayed deletes enabled and deal with this on the scrubber side ?14:47
*** woodard has joined #openstack-meeting-414:48
flaper87jokke_ mentioned the scrubber is buggy but that's something we can work on to fix if it's14:48
mfedosinflaper87: in Glare we're going to use shadow copy + delayed delete14:48
croelandtWe'd have to know exactly *how* it is buggy, first :)14:48
nikhilI am not sure atm how I feel about scrubber14:48
jokke_croelandt: ++ :)14:48
hemanthmit works for the general case from what I have seen14:48
flaper87croelandt sure, that's why I'm pinging jokke_. He probably has more info14:48
hemanthmhowever, I don't know how scrubber can ensure there is no image usage anymore14:49
*** matrohon has quit IRC14:49
nikhilwe need to move on14:49
flaper87hemanthm: it doesn't. It just tries to delete the data14:49
nikhilcroelandt: did you get a direction?14:49
flaper87hemanthm: it'll keep retrying until it manages to delete it14:49
flaper87prolly not the right solution, though14:50
jokke_hemanthm: I think the idea behind that was to get user off from the synchronous delete and let scrubber fail as long as storage reports back busy14:50
nikhilflaper87: it feels like a hack14:50
flaper87just an idea, that's the best I can come upwith right now14:50
flaper87nikhil: it is a hack14:50
flaper87:D14:50
nikhilone can write a crop job14:50
flaper87but, the question is: Can we make it not a hack?14:50
hemanthmit's a decent workaround14:50
nikhilthat runs a script in periodic intervals doing "image-delete"14:50
croelandtnikhil: well, I guess I could discuss this with jokke_ and flaper8714:50
flaper87Can we support this use case through the scrubber ?14:50
croelandtand re-submit our findings for another meeting14:50
nikhilcron*14:50
jokke_please no14:50
* flaper87 stfu and lets the meeting to move on14:50
hemanthmjokke_: yes, makes sense14:50
jokke_for the support14:51
nikhillet's discuss offline14:51
nikhil#topic open discussion14:51
jokke_I really feel like that's can of worms we really don't want to open14:51
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:51
*** matrohon has joined #openstack-meeting-414:51
flaper87jokke_: I didn't mean support of the dependency use case but the delete retries (I'm done, I swear)14:51
mfedosinAlex asks for review https://review.openstack.org/#/c/320912/14:51
nikhilso, kairat you posted a late request14:51
*** jmckind has quit IRC14:52
kairatSo oslo.log folks are going to remove verbose option14:52
kairatwe need to be prepared for that14:52
kairatnikhil, yep, I know14:52
kairatThat's why I asked about clarification14:52
nikhil(but I guess we can ignore that for this week as you'd questions)14:52
nikhilcool14:52
*** shaohe_feng has quit IRC14:53
kairathttps://review.openstack.org/#/c/317579, https://review.openstack.org/#/c/317556 - please review that, oslo.folks asked to remove that a month ago14:53
kairatflaper87, jokke_ , hemanthm nikhil rosmaita ^14:53
*** shaohe_feng has joined #openstack-meeting-414:53
nikhilthanks kairat , good heads up. guess we can try to get that in by n-114:54
nikhilsame is the case with rosmaita (late request)14:54
rosmaitasame request as last meeting14:54
*** anilvenkata has quit IRC14:54
*** salv-orlando has joined #openstack-meeting-414:54
jokke_kairat: not against the change itself nor it's reasoning ... I'm sure oslo folks will follow standard deprecation so it's not huge rush ... but what I'd like to have is reference to that deprecation in the commit messages14:54
kairatSee "[openstack-dev] [oslo][all] oslo.log `verbose` and $your project" for more information14:54
*** vikram has joined #openstack-meeting-414:54
rosmaitawould like to get the v1 api-ref in-tree soon, will make it easier to make corrections14:54
kairatjokke_, ok, will do14:54
*** spzala has joined #openstack-meeting-414:54
hemanthm++ jokke_14:55
nikhilrosmaita: perfect14:55
jokke_rosmaita: can we not introduce that as we're deprecating the api14:55
* jokke_ ducks14:55
nikhillol14:56
*** spzala_ has joined #openstack-meeting-414:56
rosmaitajokke_: unfortunately, at the moment, it's "supported"14:56
nikhiljokke_: I hope that was not a serious question?14:56
rosmaitawhich includes providing docs14:56
jokke_rosmaita: that is quickly fixed14:56
rosmaita:)14:56
jokke_I think flaper87 has patch waiting14:56
rosmaitayes, one way to get people to not use it is to hide the docs!14:57
nikhilwell, we need to have API ref14:57
nikhildoesn't matter current, supported or deprecated14:57
nikhilno, we do not want to do that14:57
nikhilwe want to increase the docs14:57
flaper87I actually do14:57
flaper87:P14:57
nikhillast thing we need is another set of angry customers who do not have a reference14:57
jokke_I don't see point ot hold hand how to use something we don't want anyone to use14:57
nikhileven for the sake of migration14:57
jokke_;)14:58
nikhilso, docs docs docs!14:58
rosmaitaflaper87: trade you a review of your slide deck for a review of https://review.openstack.org/#/c/312259/ !14:58
flaper87rosmaita: deal14:58
rosmaitaexcellent!14:58
nikhillooks like those are the things for today?14:58
nikhillet's close this early to help setup the virtual sync14:58
rosmaitai will revise my timeframe and look at the deck this afternoon14:58
*** lei-zh has joined #openstack-meeting-414:58
* flaper87 is ready for the virtual meeting14:59
* rosmaita is not14:59
nikhilThanks all.14:59
nikhil#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Thu May 26 14:59:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-26-14.03.html14:59
*** armax has joined #openstack-meeting-414:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-26-14.03.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-26-14.03.log.html14:59
flaper87rosmaita: are you eveR? are you?14:59
flaper87:P14:59
* flaper87 runs14:59
*** spzala has quit IRC14:59
*** bunting has left #openstack-meeting-415:00
*** kebray has quit IRC15:00
*** tsymanczyk has left #openstack-meeting-415:00
*** ddieterly is now known as ddieterly[away]15:00
jokke_me has 4min clock pending15:00
* jokke_ 15:00
*** kairat has left #openstack-meeting-415:00
*** sjmc7 has joined #openstack-meeting-415:00
sjmc7#startmeeting openstack search15:01
openstackMeeting started Thu May 26 15:01:02 2016 UTC and is due to finish in 60 minutes.  The chair is sjmc7. 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
sjmc7morning all15:01
*** kebray has joined #openstack-meeting-415:01
lei-zho/15:01
*** tonytan4ever has joined #openstack-meeting-415:01
sjmc7#link https://etherpad.openstack.org/p/search-team-meeting-agenda15:02
*** RickA-HP has joined #openstack-meeting-415:02
rosmaitasjmc7: i am on vacation this week, will not be attending15:02
sjmc7but yet..!15:02
*** yingjun has joined #openstack-meeting-415:02
sjmc7thanks for letting me know, have a nice break!15:02
*** jmckind has joined #openstack-meeting-415:03
sjmc7travis is also out, so i’ve got the wheel this week15:03
sjmc7we’ll give it a few minutes15:03
*** shaohe_feng has quit IRC15:03
yingjun:)15:03
*** shaohe_feng has joined #openstack-meeting-415:03
sjmc7ok, will get started. others may drift in15:04
sjmc7#topic newton-1 milestone15:04
*** openstack changes topic to "newton-1 milestone (Meeting topic: openstack search)"15:04
sjmc7Sometime next week is the newton-1 milestone15:04
sjmc7i think our aim is to have any blueprints/specs that we expect to get implemented approved by then or soon after15:05
sjmc7so if anyone’s got anything they would like to see, it’d be good to get something written up in the next week15:05
sjmc7lei-zh: the pipeline one is the only big architectural one taht came to mind15:05
lei-zhI'll update pipeline spec soon15:06
lei-zhand we can have further discussion15:06
RickA-HPAre there any others that folks are thinking about? Or need help with?15:06
sjmc7ok. yeah, hopefully we can get that moving15:06
sjmc7the other high priority BPs we have are mostly plugins, but we’ll review next week15:07
sjmc7ok, moving on15:07
sjmc7#topic Request for mentoring15:07
*** openstack changes topic to "Request for mentoring (Meeting topic: openstack search)"15:07
*** croelandt has left #openstack-meeting-415:08
sjmc7there was some traffic on the mailing list over the last week15:08
sjmc7#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/095921.html15:08
sjmc7we do already have some contributors that we’ve been semi-officially mentoring, but if anyone would like to officially put themself forward for it, that’s the information15:08
*** vikram has quit IRC15:08
sjmc7as i understand it it’s intended to be a few hours a month of answering questions and being a contact for the person in the program; it’s not meant to be a full-time internship kind of thing15:09
Kevin_Zhengo/15:09
sjmc7ah, hi Kevin_Zheng15:10
Kevin_ZhengSorry15:10
Kevin_ZhengTo be late15:10
*** phil_h has joined #openstack-meeting-415:10
sjmc7ah, no worries. i think most of the people here are in china so thanks for attending at a late hour15:10
*** ddieterly[away] is now known as ddieterly15:10
sjmc7#topic Lei Zhang is now core15:10
*** openstack changes topic to "Lei Zhang is now core (Meeting topic: openstack search)"15:10
sjmc7thanks lei-zh !15:11
lei-zhit's my honor : )15:11
RickA-HPCongrats!15:11
yingjunCongrats!15:11
sjmc7you and yingjun don’t have to wait til the next day for +2s now :)15:11
Kevin_ZhengCong15:11
lei-zhhaha, indeed15:11
*** sshnaidm has quit IRC15:11
sjmc7#topic Nova notification updates15:12
*** openstack changes topic to "Nova notification updates (Meeting topic: openstack search)"15:12
sjmc7couple of things here15:12
*** hvprash_ has quit IRC15:13
sjmc7first, I put a review up that reduces the number of calls to nova’s API from about 9 to 3 during boot15:13
sjmc7https://review.openstack.org/#/c/317100/15:13
*** rromans has joined #openstack-meeting-415:13
sjmc7it’s a bit complicated because of some race conditions, so if people can test it that would be great15:13
*** hvprash has joined #openstack-meeting-415:13
*** yingjun has quit IRC15:13
*** yingjun_ has joined #openstack-meeting-415:13
*** shaohe_feng has quit IRC15:13
*** claudiub has quit IRC15:13
*** piet has quit IRC15:13
*** shaohe_feng has joined #openstack-meeting-415:14
sjmc7the other is that we’re still tracking nova’s move to versioned notifications15:14
sjmc7that spec has been approved (https://review.openstack.org/#/c/286675/) so we’ll keep an eye on it15:14
sjmc7it looks like initially they’ll reimplment the current notifications as versioned ones, and then consider additions/changes15:15
sjmc7anyone else have any information or questions about that?15:15
*** qwebirc38643 has joined #openstack-meeting-415:15
Kevin_ZhengSure15:15
*** javeriak has joined #openstack-meeting-415:15
Kevin_ZhengI'm working with them on that in nova15:16
sjmc7Kevin_Zheng actually works on nova so has real information on it :)15:16
sjmc7one thing that travis and i have requested once that initial work is done is making the notification payload look more like the API response since that helps us a lot with indexing15:16
sjmc7the nova team doesn’t seem that keen on it15:16
Kevin_ZhengYes, have just started15:17
sjmc7but we’ll wait until the first implementation is done15:17
yingjun_FYI, i uploaded the flavour notification spec today, https://review.openstack.org/#/c/321336/15:17
Kevin_ZhengThe first one as example, so long way to go15:17
sjmc7ok. we’ll keep an eye on it15:17
sjmc7ah, excellent yingjun_. GB21 put up a patch for indexing flavors without notifications that i think you’ve been reviewing15:18
Kevin_ZhengSure15:18
yingjun_yeah15:18
yingjun_and the hypervisor one needs one more +2 https://review.openstack.org/29980715:18
sjmc7ok. i’ll ask around and see if i can find anyone available to look at it15:19
sjmc7it’s always a long process getting specs reviewed for the established projects :)15:19
lei-zhI can find some nova people to look at that spec15:19
sjmc7that would be great too15:19
yingjun_great!15:20
Kevin_Zhengjohnthetubaguy will be a good choice15:20
*** galstrom_zzz is now known as galstrom15:21
sjmc7ok15:21
sjmc7next up, and quite related...15:21
sjmc7#topic Nova microversioning15:21
*** openstack changes topic to "Nova microversioning (Meeting topic: openstack search)"15:21
sjmc7this is the reason Kevin_Zheng is here15:21
*** javeriak_ has joined #openstack-meeting-415:22
sjmc7correct me if i’m wrong - it sounds like nova’s removing the non-microversioned API at some point15:22
sjmc7so we need to support it sooner rather than later. i see you put a patch up today which i’ll take a look at later15:22
*** javeriak has quit IRC15:23
sjmc7this’ll also let us support some additional fields from later versions of the API15:23
*** shaohe_feng has quit IRC15:23
sjmc7Kevin_Zheng: do you have a link for the nova work on that?15:23
*** shaohe_feng has joined #openstack-meeting-415:24
Kevin_ZhengI have15:25
Kevin_ZhengBut I'm now using mobile device15:25
sjmc7ah :)15:25
sjmc7then no worries - if you could drop it in the searchlight irc room tomorrow that would be really useful15:25
yingjun_https://review.openstack.org/#/c/321375/1/specs/newton/support-nova-microversions.rst15:25
Kevin_ZhengAnd it seems I forgot to include the links15:26
Kevin_ZhengI will update the spec15:26
sjmc7ok, that’d be good as well, thanks :)15:26
yingjun_is this one right? Kevin_Zheng15:26
Kevin_ZhengIn a minute15:26
Kevin_ZhengYes15:26
sjmc7it can wait til tomorrow, i know it’s late there15:26
Kevin_ZhengNo warriors15:26
Kevin_ZhengWorries15:27
sjmc7thanks for jumping in on this - it’s hard for us to keep up with changes like this across so many projects15:27
sjmc7ok, moving on unless anyone has any more comments on that...15:27
Kevin_ZhengI was planning to add it but I was distracted by something15:27
sjmc7i know how that feels :)15:27
sjmc7#topic Open reviews15:28
*** openstack changes topic to "Open reviews (Meeting topic: openstack search)"15:28
sjmc7#link https://review.openstack.org/#/q/status:open+AND+(project:openstack/searchlight+OR+project:openstack/searchlight-specs+OR+project:openstack/python-searchlightclient+OR+openstack/searchlight-ui)15:28
*** jaimguer has joined #openstack-meeting-415:28
sjmc7if anyone’s got any experience with angular, reviews for the UI patches would be good15:28
*** Swami has joined #openstack-meeting-415:28
sjmc7we do have some horizon cores that spend a little time on them, and i know yingjun_ has put some patches up15:28
sjmc7it’s not really my area of expertise15:29
sjmc7so i guess i should get better :)  thanks to everyone for being on top of reviews though; we’ve done a good job of not letting things sit for too long15:29
sjmc7ok.. that was all i had on the agenda15:30
sjmc7#topic Open discussion15:30
*** openstack changes topic to "Open discussion (Meeting topic: openstack search)"15:30
sjmc7if there’s anything else people want to discuss, feel free to bring it up15:31
sjmc7otherwise i’ll give it a few minutes and let everyone get to bed. meetings are quick when people are away on vacation15:31
david-lylesjmc7: or hiding in plain sight15:31
sjmc7:O15:31
sjmc7you’re just like my driving instructor; silent for 30 minutes then scaring me at the end15:32
david-lylethat was all wrong15:32
david-lyle;)15:32
sjmc7:)15:32
sjmc7i can already feel travis reading the transcript and shaking his head15:33
david-lylein your test environments, are you doing any rate limiting on nova API?15:33
sjmc7no, because i think we’d hit it :)  that’s why we’re desperately trying to reduce the number of calls we make15:33
david-lyleright15:33
david-lylethe move from 9 -> 3 is great15:33
*** yingjun_ has quit IRC15:34
sjmc7it’s still too many15:34
*** shaohe_feng has quit IRC15:34
david-lylebut 3  is still a lot15:34
david-lyleyes15:34
sjmc7yeah. we could remove another one15:34
*** yingjun has joined #openstack-meeting-415:34
sjmc7the pre-scheduling one15:34
sjmc7or do a partial document for that first one15:34
*** sacharya has joined #openstack-meeting-415:34
sjmc7maybe i’ll do that as well15:34
sjmc7i’ve always said though that we need to aim for no API calls at all15:34
*** shaohe_feng has joined #openstack-meeting-415:35
david-lyleI'm glad progress is being made15:35
sjmc7yeah. it’s definitely a very valid concern15:35
david-lylethat certainly should be the goal and if nova is going to point people to searchlight, seems like they should help with the notifications to make sure it works15:35
david-lylenot have two hands working in opposite directions15:35
*** piet has joined #openstack-meeting-415:36
sjmc7yeah, we’re hoping that is the case, although i’m not sure the two groups are working closely15:36
david-lylewell not to be solved here15:36
*** trozet has quit IRC15:36
sjmc7no. we’ll keep working on them15:36
sjmc7ok, unless anyone had anything else, i’ll call it15:36
* david-lyle is done15:36
sjmc7thanks everyone, especially where it’s 11pm!15:36
david-lylecongrats lei-zh15:37
sjmc7#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
RickA-HPBye15:37
openstackMeeting ended Thu May 26 15:37:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-26-15.01.html15:37
*** RickA-HP has left #openstack-meeting-415:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-26-15.01.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-05-26-15.01.log.html15:37
lei-zhthanks15:37
*** yingjun has left #openstack-meeting-415:37
lei-zhbye15:37
sjmc7g’night!15:37
lei-zhZzzzz:)15:37
*** lei-zh has left #openstack-meeting-415:38
*** trozet has joined #openstack-meeting-415:38
*** sudipto has quit IRC15:42
*** shaohe_feng has quit IRC15:44
*** shaohe_feng has joined #openstack-meeting-415:45
*** minwang2 has joined #openstack-meeting-415:45
*** hvprash has quit IRC15:48
*** hvprash has joined #openstack-meeting-415:48
*** uck has joined #openstack-meeting-415:53
*** tonytan4ever has quit IRC15:54
*** djkonro has joined #openstack-meeting-415:54
*** shaohe_feng has quit IRC15:54
*** shaohe_feng has joined #openstack-meeting-415:55
*** vtech_ has quit IRC15:56
*** asettle has joined #openstack-meeting-415:57
*** ddieterly is now known as ddieterly[away]15:59
odyssey4me#startmeeting OpenStack-Ansible16:00
openstackMeeting started Thu May 26 16:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:00
openstackThe meeting name has been set to 'openstack_ansible'16:00
*** jmccrory_ has joined #openstack-meeting-416:00
*** ddieterly[away] is now known as ddieterly16:00
odyssey4me#topic Rollcall & agenda16:00
*** openstack changes topic to "Rollcall & agenda (Meeting topic: OpenStack-Ansible)"16:00
*** automagically_ has joined #openstack-meeting-416:00
automagically_o/16:01
*** v1k0d3n has joined #openstack-meeting-416:01
*** evrardjp has joined #openstack-meeting-416:01
evrardjpo/16:01
*** michaelgugino has joined #openstack-meeting-416:01
michaelguginohi16:01
*** stevelle has joined #openstack-meeting-416:01
spotz\o/16:02
*** sshnaidm has joined #openstack-meeting-416:03
*** yamahata has joined #openstack-meeting-416:03
jmccrory_o/16:03
odyssey4mealrighty, let's get going on it16:04
odyssey4me#topic Review action items16:04
*** openstack changes topic to "Review action items (Meeting topic: OpenStack-Ansible)"16:04
*** steve_ruan has joined #openstack-meeting-416:04
*** shaohe_feng has quit IRC16:04
odyssey4meI did request the releases for Liberty & Mitaka - they finally got processed today.16:04
asettleBit late o/16:05
odyssey4meOur stable branch release requests now need to be reviewed by both the stable branch team and the release team.16:05
evrardjpasettle: that's rude16:05
*** paul-carlton2 has joined #openstack-meeting-416:05
evrardjpoh you meant for being there, not for the release16:05
evrardjpok16:05
*** steve_ruan has quit IRC16:05
asettleevrardjp: wow dude. ha.16:05
evrardjpETA odyssey4me?16:05
odyssey4me#info All stable branch releases now require a minimum of a two day lead time as they require reviews by both the stable team and the releases team.16:07
odyssey4meevrardjp the last release requests got processed today - they were requested last week16:07
evrardjpnow I understand16:07
odyssey4meit's just FYI - the process is now quite onerous and I'm trying to work with both teams to make it go quicker.16:07
odyssey4meAnother action item on me was to retire the py_from_git repo - that's in progress: https://review.openstack.org/#/q/status:open+topic:retire-repo16:08
*** piet has quit IRC16:08
*** matrohon has quit IRC16:08
odyssey4meunfortunately a lot of -infra's reviewers have been in sprints for the last two weeks, so I'm not getting much traction on reviews16:08
odyssey4meI have several waiting for reviews, and they're not getting attention even if I ask nicely: https://review.openstack.org/#/q/owner:jesse-pretorius+status:open+project:openstack-infra/project-config16:09
odyssey4meAnyway, I'll keep at that.16:10
*** shaohe_feng has joined #openstack-meeting-416:10
odyssey4me#topic Tests Repo16:10
*** openstack changes topic to "Tests Repo (Meeting topic: OpenStack-Ansible)"16:10
odyssey4meandymccr Do you have an update?16:10
odyssey4meok, we'll come back to it if he joins up16:11
odyssey4me#topic Mid Cycle Planning16:11
*** openstack changes topic to "Mid Cycle Planning (Meeting topic: OpenStack-Ansible)"16:11
odyssey4meWe discussed three options last week, and only two were of any sort of appeal.16:11
asettleodyssey4me: he's just logging on16:11
asettlelaptop crashed.16:11
odyssey4me1 - Have a fully co-located mid cycle, most likely in the US.16:12
odyssey4me2 - Have a rolling mid-cycle over multiple time zones, with handovers between co-located groups.16:12
odyssey4meHave we got any further thoughts or information regarding dates, venues, etc?16:13
andymccro/ sorry for the delay - ready to loop back on test repos16:13
automagically_I have not had a chance to determine which dates we could offer up to host in Philadelphia. Let me make a note to try to get that done this week16:14
*** dshakhray has quit IRC16:14
odyssey4meno worries andymccr - we'll get back to that shortly16:14
*** shaohe_feng has quit IRC16:15
odyssey4meping jmccrory d34dh0r53 stevelle mattt hughsaunders andymccr mhayden re: mid cycle16:15
*** shaohe_feng has joined #openstack-meeting-416:16
*** sambetts is now known as sambetts|afk16:16
andymccrno additional thoughts to last week - i think dates and ability to travel are the most important factor right now16:16
odyssey4meok, it seems like we don't have a decent quorum of cores here to make much of a decision either way, so I guess we'll have to defer that discussion to next week16:17
evrardjpk16:17
stevelleI'm here, no preset opinions on mid cycle16:17
stevelleI really just want to get dates first16:18
*** minwang2 has quit IRC16:18
jmccroryeither option still works for me, but yeah, the sooner we can get dates to better to work around vacations or anything else16:18
automagically_#action automagically to determine potential dates for hosting16:18
*** lakshmiS has joined #openstack-meeting-416:18
odyssey4methanks automagically_16:18
odyssey4me#topic Tests Repo16:19
*** openstack changes topic to "Tests Repo (Meeting topic: OpenStack-Ansible)"16:19
odyssey4meandymccr over to you16:19
automagically_There was some discussion about hosting in San Antonio as well IIRC. Who owns the action item there for potential dates?16:19
automagically_D’oh, sorry andymccr16:19
andymccrok So. I have a PoC finished: https://github.com/andymcc/openstack-ansible-testing-core16:19
andymccri ran into some blockers today with non-test related packaging issues16:19
andymccrbut i confirmed that glance/swift/keystone all worked before today and nova was basically finished (i think i fixed it).16:19
odyssey4me#action odyssey4me to check on RAX hosting option in SAT, and dates16:19
andymccrregardless, the point is to show how i split it out, and to show some additional questions/discussion points that may arise and things we can consider16:20
andymccrtl;dr if people want to take a look at that repo and the links in the readme to see the changes and decide whether its a good idea or not, and and how we should do it and discuss!16:20
stevellequeued!16:21
odyssey4methanks andymccr - and thanks for describing the intents in the README :)16:21
automagically_Looks cool, digging into the repo now16:21
evrardjplet's put this as an action point for next week?16:21
odyssey4me#action all to take a look through, and ideally test https://github.com/andymcc/openstack-ansible-testing-core16:21
odyssey4meyeah, I think it's best we discuss it generally over the week in the channel and next week we can raise any more things16:22
odyssey4me#topic Astara16:23
*** openstack changes topic to "Astara (Meeting topic: OpenStack-Ansible)"16:23
odyssey4meIs Phil Hopkins around?16:23
phil_hTHis is Phil16:23
phil_hI am here!!16:23
odyssey4mehi phil_h - over to you :)16:23
phil_hMajor has told me16:23
phil_hthat you have been looking at Octavia as a loadbalancing solution16:24
phil_hI wanted to introduce you to Astara which can do the same thing16:24
phil_hSimilar to Octavia it uses Vms as the loadbalancer16:24
*** shaohe_feng has quit IRC16:25
automagically_mhayden and phil_h - Are we talking about what the use as the OSA “opinionated” out of the box implementation?16:25
phil_hBut with the additional feature that it can implement routers in a VM also16:25
automagically_s/the/we16:25
automagically_Or what OSA will support and document?16:25
*** vtech has joined #openstack-meeting-416:26
phil_hI think for the future16:26
odyssey4mephil_h it sounds good, and we're happy to assist someone working with us to instrument the deployment of whichever components Astara provides - but we would want someone who knows and understands Asatara and is prepared to build and maintain any instrumentation in OSA for it on an ongoing basis16:27
phil_hAstara can replace the standard neutron L# stuff and set up both routers and loadbalancers16:27
phil_hI would be willing to help and I can recruit some of the Astara folks also16:27
odyssey4mephil_h there is also similar instrumentation for PlumGRID and Nuage already, so there's a fair amount of prior art to work with16:27
automagically_So, starting point would be an openstack-ansible-os_astara role16:27
automagically_Perhaps?16:27
*** sjmc7 has left #openstack-meeting-416:28
phil_hYes16:28
*** numans has quit IRC16:28
odyssey4meautomagically_ it depends...16:28
phil_hI have a simle ansible role that can convert to astara16:28
*** shaohe_feng has joined #openstack-meeting-416:28
phil_hwhich could be used as a basis16:28
automagically_Well, right…I’m just browsing the docs and it looks like there is talk of using diskimagebuilder to produce an LB appliance...16:28
phil_hsimle -> simple16:28
odyssey4meboth PlumGRID and Nuage maintain their own roles/playbooks to setup all their bits - we only have code to connect OSA with their bits16:28
automagically_phil_h - Basing that off of http://docs.akanda.io/en/latest/loadbalancer.html16:29
phil_hI think that is correct16:29
*** dave-mccowan has joined #openstack-meeting-416:29
phil_hAstara does use diskimagebuilder16:29
phil_hto create VM images such as the loadbalancer16:30
*** ddieterly is now known as ddieterly[away]16:30
phil_hSo what is the best way to proceed?16:30
*** ddieterly[away] is now known as ddieterly16:31
odyssey4meit appears that someone has registered a blueprint: https://blueprints.launchpad.net/openstack-ansible/+spec/add-support-for-astara16:31
phil_hI will talk to Eric about it16:32
odyssey4mephil_h the best starting point is probably to put together an etherpad with notes on what the components are and where the touch points are with the OSA implementation16:32
odyssey4mephil_h you can use the PlumGRID and Nuage implementations as a reference to see how they work to give you ideas16:32
phil_hI will get started on that and I will stay in touch with everyone16:33
odyssey4mephil_h FYI http://docs.openstack.org/developer/openstack-ansible/install-guide/app-plumgrid.html16:33
phil_hI will look at how they have things set up16:33
*** paul-carlton2 has quit IRC16:33
odyssey4mephil_h also http://docs.openstack.org/developer/openstack-ansible/install-guide/app-nuage.html16:33
phil_hThanks16:33
odyssey4meyou'll see how that all works in the neutron role itself https://github.com/openstack/openstack-ansible-os_neutron and for nuage there's also a bit in the nova role https://github.com/openstack/openstack-ansible-os_nova16:34
odyssey4mephil_h if you can make the next meeting with a prepared etherpad, then we can discuss it together and help work out the next steps with you16:34
phil_hOK, Thanks16:35
odyssey4meof course you're also welcome to ask questions in #openstack-ansible at any time16:35
phil_hI will!!!!16:35
phil_hor bug Major!!16:35
*** shaohe_feng has quit IRC16:35
odyssey4meheh, of course - you'll find plenty of peopl in the channel are always happy to help16:35
phil_hunderstand, I just like to tweek him from time to time16:36
odyssey4mealright, moving on16:36
odyssey4me#topic Ubuntu 16.04 LTS support16:36
*** shaohe_feng has joined #openstack-meeting-416:36
*** openstack changes topic to "Ubuntu 16.04 LTS support (Meeting topic: OpenStack-Ansible)"16:36
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-newton-ubuntu16-0416:36
automagically_odyssey4me: Don’t forget #topic Deprecation of pip_lock_down please ;)16:37
*** lcastell has joined #openstack-meeting-416:37
odyssey4meheh, you snuck that one in after my last refresh automagically_ :)16:37
*** ddieterly is now known as ddieterly[away]16:38
odyssey4meok, so the only roles we haven't done the var moves for to cover the Newton-1 milestone are nova, rally, ironic and magnum16:38
odyssey4mefor rally there's a review that didn't pass the gate check16:38
michaelguginocloudnull did an incredible amount of work in the last work16:39
michaelgugino*week16:39
automagically_odyssey4me: Yeah, I need to circle back to that Rally one and debug the apt issue16:39
michaelguginoI've been MIA working on internal sprints, I'm hoping to pick up nova possibly16:39
automagically_And rally isn’t really core now, i.e. not integrated into gate16:39
odyssey4medo we have any volunteers to take on the nova, ironic and magnum roles? remember that the Newton-1 goal is simply to apply the var pattern and have it pass the Trusty gate check, nothing more16:39
michaelguginounless someone else wants it16:39
*** ajmiller__ has quit IRC16:39
jmccroryi'll take magnum16:39
*** claudiub has joined #openstack-meeting-416:40
odyssey4meplease add your name to the etherpad, thanks jmccrory16:40
*** pvaneck has joined #openstack-meeting-416:40
michaelgugino<<< nova16:40
odyssey4methanks michaelgugino16:40
odyssey4meand yeah, cloudnull did manage to cover a lot of ground in the last week - but thanks to everyone for pitching in16:41
odyssey4mewhat is nice is that we now have some patterns to work with for systemd support, and I think all of the infrastructure roles are already working on at least Xenial16:41
odyssey4mecan we get a volunteer to do the ironic role?16:42
andymccri'll take a look16:42
odyssey4methanks andymccr16:43
odyssey4mecool, Newton-1 is next week Thu/Fri16:44
odyssey4meright, let's circle back16:44
automagically_Really sneaks up16:44
odyssey4me#topic Deprecation of pip_lockdown16:44
*** openstack changes topic to "Deprecation of pip_lockdown (Meeting topic: OpenStack-Ansible)"16:44
odyssey4meautomagically_ over to you16:44
automagically_Just wanted to get eyes on https://review.openstack.org/#/c/313890/ as the desirable pattern moving forward16:44
*** LouisF has joined #openstack-meeting-416:45
automagically_So we can unblock a whole raft of jmccrory patchs16:45
*** javeriak has joined #openstack-meeting-416:45
automagically_Looks like odyssey4me and mattt had objections, just want to see if we can clear those up16:45
*** shaohe_feng has quit IRC16:45
* odyssey4me is reading the discussion again16:46
evrardjpI'll read that too16:47
odyssey4meI've just been wondering why we should specifically apply the var there?16:47
*** unicell1 has quit IRC16:47
*** ajmiller has joined #openstack-meeting-416:48
*** unicell has joined #openstack-meeting-416:48
odyssey4mewhy not just include the role as normal, then apply the lock-down in the playbooks16:48
*** markvoelker has quit IRC16:48
*** shaohe_feng has joined #openstack-meeting-416:48
odyssey4methe trouble here is that we're adding yet another place to look for vars being set16:48
*** javeriak_ has quit IRC16:48
automagically_odyssey4me: I’d be okay with that, but we are always going to set it to true in the playbooks...16:48
odyssey4mewe already have role defaults, group_vars, playbooks and overrides16:49
*** spzala_ has quit IRC16:49
*** djkonro has quit IRC16:49
automagically_Sure, but this one is not something deployers are going to need to view/override16:49
jmccrorywe're doing this already a few other roles: https://github.com/openstack/openstack-ansible-galera_client/blob/master/meta/main.yml#L37-L39 https://github.com/openstack/openstack-ansible-repo_build/blob/master/meta/main.yml#L3316:49
odyssey4meautomagically_ not always, I don't think - certainly not for the repo server16:49
*** markvoelker has joined #openstack-meeting-416:49
odyssey4mejmccrory is there a reason why those can't live in the defaults instead?16:50
automagically_If we want to do it at the playbook level, than my earlier opinion on that review stands, which is that we should remove the hard role dependency altogether16:50
odyssey4methe role defaults?16:50
automagically_And pip install and config is a decision purely made at the playbook level16:50
*** spzala has joined #openstack-meeting-416:50
automagically_There really _is not_ a hard dependency as such, more of an order of operations. I think order of operations ownership between roles is largely a playbook-level concern, rather than a role concern16:52
odyssey4meautomagically_ I agree with you, but I know that cloudnull disagrees strongly and he's not present.16:52
automagically_Ah, alright, then this won’t be the meeting we solve this in then ;)16:52
jmccroryodyssey4me: they could, for the lock down case the same ternary could be a default as well.16:52
jmccroryif the main concern is where the variable is defined16:52
automagically_Agreed jmccrory. My remove the dependency altogether argument is a far more wide ranging and invasive one16:53
evrardjpCould we analyse this and give feedback next week?16:53
automagically_Anyway, sounds like we #action all table pip_lock_down deprecation discussion til cloudnull returns16:53
odyssey4meautomagically_ yeah, that's my concern with that - so I'm more inclined to let this through even if I don't like it16:53
automagically_odyssey4me: ++16:53
evrardjpAgreed too16:54
odyssey4meI would prefer the vars not being set in meta if possible - it just makes it that extra level more frustrating to figure things out16:54
automagically_So odyssey4me - you’ll +2 if it moves to role defaults16:54
odyssey4mebut as jmccrory has noted, we already have precedent16:54
evrardjpthe extra level is fine but for having a build dependencies system only IMO, not for using that directly16:54
*** spzala has quit IRC16:55
evrardjpbut yeah, I'll analyse this further16:55
odyssey4meautomagically_ for this particular case, I really don't see why the role needs to activate the lock down at all16:55
*** iyamahat has joined #openstack-meeting-416:55
automagically_I know…and I agree16:55
*** mohankumar has joined #openstack-meeting-416:55
odyssey4mefor the other cases jmccrory pointed out, yes I think those could happily live in role defaults instead16:55
evrardjpthen it's clearly a misuse of meta16:55
automagically_But…may be worthwhile to take small steps here sufficient to drop the lockdown role16:55
automagically_And then re-evaluate16:56
*** shaohe_feng has quit IRC16:56
odyssey4meautomagically_ sure16:56
odyssey4mejmccrory thoughts?16:56
*** shaohe_feng has joined #openstack-meeting-416:56
jmccroryi could see the lockdown var moved entirely to OSA's playbooks16:57
automagically_jmccrory: And the role as well, or would you keep the role deps the way they are?16:57
odyssey4meso if the var was set in the playbooks that need it, and the role still set as a dep then I'd be completely happy16:57
automagically_We are nearly out of time, I didn’t expect this conversation to go so long16:57
jmccroryonly pip_install in os_ role deps, OSA playbook would lock it down16:58
odyssey4meautomagically_ further suggestion to remove the role dep can be explored later16:58
automagically_agree16:58
odyssey4meok, we're pretty much out of time16:58
odyssey4methanks all!16:59
automagically_jmccrory: Will you propose that review to show that pattern? I think we like it16:59
odyssey4me#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu May 26 16:59:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-26-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-26-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-05-26-16.00.log.html16:59
*** automagically_ has left #openstack-meeting-416:59
*** automagically_ has joined #openstack-meeting-416:59
*** twm2016 has joined #openstack-meeting-416:59
*** stevelle has left #openstack-meeting-417:00
*** kebray has quit IRC17:00
*** minwang2 has joined #openstack-meeting-417:00
LouisF#startmeeting service_chaining17:00
openstackMeeting started Thu May 26 17:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
LouisFhello all17:01
pcarverhi17:01
*** evrardjp has left #openstack-meeting-417:01
mohankumarHI17:01
iyamahathello17:01
LouisFi'd like to start by going over action items from last meeting17:01
LouisF#topic action item  status17:02
*** openstack changes topic to "action item status (Meeting topic: service_chaining)"17:02
LouisFupdate of use cases to the wiki17:02
LouisFi see that Igor has added a use case17:02
*** doonhammer has joined #openstack-meeting-417:03
LouisFhi John17:03
doonhammerHi Louis17:03
*** ajmiller_ has joined #openstack-meeting-417:03
*** julim_ has joined #openstack-meeting-417:03
LouisFdoonhammer: any success on adding your use case to the wiki?17:03
*** cwolferh has joined #openstack-meeting-417:04
*** michaelgugino has left #openstack-meeting-417:04
LouisFpcarver: will you be able to add a use case to the wiki?17:04
*** s3wong has joined #openstack-meeting-417:04
LouisFs3wong: hi17:05
*** ddieterly[away] is now known as ddieterly17:05
s3wongLouisF: hello17:05
doonhammerLouisF: Ubuntu said it is a bug in Openstack - opened case at support.openstack.org17:05
LouisFs3wong: going over adding use cases to wiki17:05
pcarverLouisF: I asked about use cases but I haven't been able to find any yet. I don't actually work with the VNFs, so I only have the abstract feature requirements, not concrete use cases for specific VNFs.17:05
s3wongLouisF: I see, AI from last week17:05
LouisFdoonhammer: ok thanks17:05
*** baoli_ has quit IRC17:06
*** shaohe_feng has quit IRC17:06
LouisFpcarver: ok thanks17:06
*** baoli has joined #openstack-meeting-417:06
doonhammerLouisF: I have them done - perhaps someone else can post them until I can fix my wiki access problem17:06
*** fawadkhaliq has quit IRC17:07
*** julim has quit IRC17:07
*** asettle has quit IRC17:07
LouisFI can post them it you send them to me17:07
*** ajmiller has quit IRC17:07
*** automagically_ has left #openstack-meeting-417:07
doonhammerLouisF: Will do17:07
LouisFdoonhammer: thx17:07
LouisFnext item I see is the flow classifier priority17:08
*** gangil has joined #openstack-meeting-417:08
LouisFmohankumar: i see there have been reviews17:08
mohankumarLouisF :  I got little busy on other works17:08
LouisFof your patch17:08
*** shaohe_feng has joined #openstack-meeting-417:08
LouisFmohankumar: what is the patch?17:08
mohankumarLouisF: i ve raised WIP progress patch , may be update and open it for review17:09
*** numans has joined #openstack-meeting-417:09
LouisFmohankumar: ok thanks17:09
LouisFpavel was also going to help with that17:09
mohankumarLouisF : yes17:09
LouisFis he on the channel?17:10
LouisFok moving on17:11
mohankumarLouisF:  By next week the patche will be in goos shape17:11
mohankumar*good shape17:11
LouisFmohankumar: great will review then17:11
LouisFregarding the path id generation  - that work is under way17:12
*** spzala has joined #openstack-meeting-417:13
LouisFok lets move on to agenda items we missed from last meeting17:13
*** sc68cal_ has quit IRC17:13
LouisF#topic SF insertion type/mode17:13
*** openstack changes topic to "SF insertion type/mode (Meeting topic: service_chaining)"17:13
*** azbiswas has joined #openstack-meeting-417:13
LouisFwe started discussing last week17:14
*** zenoway has quit IRC17:15
LouisFwe need to distinguish behavior of bump-in-the wire vs l2 insertion17:16
doonhammerLouisF: A question I had was who needs to be aware of the VNF mode , I think the SFF and/or the SFProxy. They need to have the awareness ?17:16
*** shaohe_feng has quit IRC17:16
*** spzala has quit IRC17:17
LouisFdoonhammer: agree the SFF or SF proxy17:17
*** shaohe_feng has joined #openstack-meeting-417:17
LouisFi think this can be handled by attaching a parameter to the VNF (SF) and using a service_function_parameters attribute17:18
LouisFlike 'insert-mode=bitw' for example17:19
doonhammerLouisF: So if we agree on that then we need to decide what needs to be done to support the various modes yes?17:19
doonhammerLouisF: Agree on mode17:19
s3wongLouisF: do you considered what we do today bump-in-the-wire or L2?17:19
*** cwolferh has quit IRC17:19
*** Jeffrey4l has quit IRC17:19
LouisFs3wong: you mean in our sfc ovs driver?17:20
s3wongLouisF: we are Neutron port based, so the VNFs all have Neutron port in some Neutron network17:20
s3wongLouisF: yes17:20
*** cwolferh has joined #openstack-meeting-417:20
LouisFs3wong: currently the ovs driver uses l2 mode17:21
s3wongLouisF: but OTOH, we set flow in higher precedent table such that the flow got forwarded to VNF via tunnel, so no need to enforce all SFs in SFC to be in same Neutron network17:21
doonhammers3wong: bitw is fairly easy as it a passthrough, L2 and L3 get complicated as the VNF and SFF need to have an understanding17:21
*** iberezovskiy is now known as iberezovskiy_afk17:22
s3wongdoonhammer: sure --- I just tried to picture if we switch to a different mode, how would the backend implementation (such as OVS) be different...17:23
LouisFdoonhammer: how the backend driver actually handles this is really implementation17:23
doonhammerLouisF: by backend driver you mean ovs or ovs/ovn?17:23
LouisFwe need to pass a hint to the driver as to the VNF behavior17:23
*** degorenko is now known as _degorenko|afk17:23
LouisFdoonhammer: yes17:23
LouisFdoonhammer: or some other driver17:24
*** spzala has joined #openstack-meeting-417:24
s3wongLouisF: sure, on API side it is just adding a parameter and pass it straight to driver17:25
doonhammerLouisF: Just thinking of how I would go about configuring a service chain implementation - especially at scale - how to comunicate all the info17:25
*** isq has quit IRC17:25
s3wongLouisF: but at least you and I have to worry about the reference implementation :-)17:25
*** lcastell has quit IRC17:25
LouisFs3wong: agree17:25
*** isq has joined #openstack-meeting-417:26
doonhammers3wong: LOL17:26
*** jmckind has quit IRC17:26
*** shaohe_feng has quit IRC17:26
*** shaohe_feng has joined #openstack-meeting-417:27
s3wongLouisF: also, for L3, there is a RFE on L3 agent extension:   https://bugs.launchpad.net/neutron/+bug/158023917:27
openstackLaunchpad bug 1580239 in neutron "[RFE] Add agent extension framework for L3 agent" [Wishlist,In progress] - Assigned to Nate Johnston (nate-johnston)17:27
*** fawadkhaliq has joined #openstack-meeting-417:27
LouisFif we pass 'insert-mode' to the driver is can then do the right thing17:27
*** lcastell has joined #openstack-meeting-417:27
doonhammerLouisF: Yes that is the first step17:28
* njohnston lurks17:28
LouisFdoonhammer: if we have agreement we can move forward with that17:29
*** spzala has quit IRC17:29
*** hvprash has quit IRC17:29
*** baoli_ has joined #openstack-meeting-417:29
doonhammerLouisF +117:30
LouisFothers?17:30
s3wong+117:30
LouisFok I will open a bug for this17:30
pcarver+117:30
*** sc68cal has joined #openstack-meeting-417:30
doonhammerLouisF: it will be a port-pair parameter or port-pair-group17:30
*** spzala has joined #openstack-meeting-417:30
mohankumar+117:31
s3wongdoonhammer: presumably port-pair-group --- the entire group should have the same insertion mode, I would imagine17:31
*** hvprash has joined #openstack-meeting-417:31
LouisFprobably better on the PPG as I don't see a case for a mix of bitw/l2/l3 devices17:31
doonhammerLouisF +117:32
*** baoli has quit IRC17:32
LouisFok that meeans adding this to the PPG parameters17:32
doonhammerNot sure if it is possible be but would be nice to enforce the same VNF in a group17:32
*** mfedosin has quit IRC17:32
LouisFdoonhammer: +117:32
doonhammerbut probably too much17:33
LouisFneed add PPG parameter - but that has been discussed before17:33
LouisF#action Louis to add bud to add PPG parameter to specify insert-mode behavior for all PPs in a PPG17:34
LouisFbug17:34
doonhammerLouisF: may also need some info for load-balancing there too17:34
LouisFdoonhammer: agree17:34
*** spzala has quit IRC17:34
LouisFok moving on17:36
LouisFthat next item is adding 'nsh' encap to the chain parameter17:36
*** spzala has joined #openstack-meeting-417:36
*** shaohe_feng has quit IRC17:37
s3wongLouisF: long email thread on that on openstack-dev...17:37
LouisF#topic nsh encap specification in chain-parameter17:37
*** zenoway has joined #openstack-meeting-417:37
*** openstack changes topic to "nsh encap specification in chain-parameter (Meeting topic: service_chaining)"17:37
LouisFs3wong: yes17:37
mohankumarLouisF ,  yes17:37
*** ddieterly is now known as ddieterly[away]17:37
*** shaohe_feng has joined #openstack-meeting-417:38
LouisFfrom the api perspective this is simple - today the encap is mpls and we can easily add nsh17:38
LouisFthe issue is the reference implementation17:39
doonhammerWas Kyle not correct when he pointed Uri to the OVS mailing list17:39
LouisFdoonhammer: agree17:39
doonhammerUntil there is some agreement there not much we can do apart from try and push - use cases and requirements?17:40
doonhammernot sure how else to push?17:40
LouisFKyle was definitely said the openstack CI did not want patches17:40
s3wongLouisF: so Uri basically just wants us to define NSH parameters at our API level?17:40
*** SumitNaiksatam has joined #openstack-meeting-417:41
*** spzala has quit IRC17:41
*** zenoway has quit IRC17:41
doonhammerI have OVN working without NSH - I am not sure moving NSF into networking-sfc or networking-ovn is the right approach17:41
doonhammerthere is a new carrier service-chaining IETF RFC that is BGP focused17:42
*** sc68cal has quit IRC17:42
LouisFs3wong: I think Uri just wants nsh encap to be added to networking-sfc17:42
*** hvprash_ has joined #openstack-meeting-417:42
s3wongdoonhammer: and I am sure in near future some other people would raise us not having support for BGP based SFC to be slowing down the industry...17:42
doonhammerif networking-sfc is a good abstraction it should support different approaches17:42
doonhammers3wong: LOL17:43
LouisFnetworking-sfc is an abstract API it does not deal with dataplane implementation17:43
LouisFdoonhammer: +117:43
doonhammerLouisF +117:43
s3wongLouisF: our reference can't support it at this point...17:43
*** hvprash has quit IRC17:44
igordcardif you are goijg to support nsh, it would be preferable to allow nsh to do what it was intended to17:44
doonhammerSo I am with Kyle and we support what ever the drivers support17:44
*** vishwanathj has quit IRC17:44
LouisFs3wong: we can add nsh to the ovs driver but depends on the nsh supported by ovs17:45
mohankumarWe having ONOS  +openstack reference implemention with OVS NSH , ONOS community supporting NSH17:45
LouisFright now we use mpls encap as a proxy for nsh17:45
s3wongLouisF: we can add NSH encap as optional parameters, one which would be implemented by ODL backend (once that is ready)... and the reference would return 'not implemented' exception --- doesn't look too clean though...17:45
s3wongmohankumar: so ONOS also uses a forked version of OVS?17:46
mohankumars3wong , yes17:46
doonhammerIn real production deployments the encap is going to be different - e.g. carrier versus data center so we need to be agnostic17:46
*** hvprash has joined #openstack-meeting-417:46
LouisFs3wong: are there other cases in neutron where some drivers do not provide complete functionality for an api?17:46
*** david-lyle has quit IRC17:47
LouisFdoonhammer: +117:47
*** shaohe_feng has quit IRC17:47
*** sarob has joined #openstack-meeting-417:47
*** david-lyle has joined #openstack-meeting-417:47
*** shaohe_feng has joined #openstack-meeting-417:47
s3wongLouisF: for reference? Can't think of any. Because normally adding support in reference implementation is part of the job of extending APIs17:47
*** spzala has joined #openstack-meeting-417:48
LouisFs3wong: so the reference implementation always supports all options offered by the api?17:48
*** _sarob has joined #openstack-meeting-417:49
s3wongLouisF: I believe so... can't think of any exception from top of my head...17:49
*** hvprash_ has quit IRC17:49
*** devananda has joined #openstack-meeting-417:50
pcarverIt would be good if the reference implementation could support everything, but the problem is that it means that you have to bypass OpenStack for anything that's only supported by some backends.17:50
s3wongLouisF: and it is a good rule of thumb anyway, as it is difficult for user to try out new APIs but the default keeps returning 'not implemented' exception17:50
LouisFs3wong: ok if that is the case the ovs driver needs to support nsh17:51
pcarverIt's a high bar for the reference implementation to have a superset of all possible features, so what's more likely is that we would lack an API for some things that multiple SDN controllers each have their own API for17:51
s3wongLouisF: correct... unfortunately...17:51
LouisFthe ovs driver is our reference implematation17:51
*** sarob has quit IRC17:52
*** dave-mccowan has quit IRC17:52
s3wongLouisF: for analogy --- for a long time, OVS has no conntrack, and therefore security group's reference is iptables on Linux bridge hooking up with OVS17:52
LouisFs3wong: good case in point17:53
*** spzala has quit IRC17:53
s3wongLouisF: our problem is we need to have the same network driver as core driver for SFC to work, so even using a non-core supported fork of OVS is not acceptable17:53
LouisFs3wong: +117:54
LouisFok we will monitor the email exhange between Kyle, Armando and Uri to see there is any compromise/resolution17:54
doonhammerPerhaps framing it as what use cases we can support with each driver - and then ask the driver team for support in solving the other issues?17:54
doonhammerhelps to make it more specific17:55
*** sc68cal has joined #openstack-meeting-417:55
LouisFdoonhammer: i think the ref implementation should support most if not all use cases17:55
*** spzala has joined #openstack-meeting-417:56
doonhammerLouisF: Agree but we are between a rock and a driver place :-)17:56
LouisFdoonhammer: lets see what is decided17:57
*** shaohe_feng has quit IRC17:57
LouisFok i don't want to start a new topic17:57
*** kebray has joined #openstack-meeting-417:58
igordcardI can't resolve the question about nsh in the API vs. ref arch, but I don't mind doing a PoC of NSH via networking-sfc (with the latest yi yang's patch) demonstrating how SFC Encapsulation can be achieved (which requires changes to the API)17:58
s3wongdoonhammer: yeah... as cores. TBH, we are willing to entertain adding this if the community feels very strongly about it --- I mean, ODL and ONOS are both OSS projects anyway; but we are Neutron stadium, and we are subjected to be governed by Neutron driver team also17:58
*** shaohe_feng has joined #openstack-meeting-417:58
LouisFigordcard: nsh can be supported by simply adding 'correlation-nsh' in the chain-parameters17:59
igordcardLouisF: please see my use case at the wiki17:59
LouisFigordcard: ok17:59
LouisFok thats it folks18:00
LouisFbye18:00
s3wongthanks, guys!18:00
mohankumarbye18:00
igordcardbye18:00
s3wongbye18:00
pcarverbye18:00
LouisF#endmeeting18:00
doonhammerbye18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu May 26 18:00:22 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-26-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-26-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-05-26-17.00.log.html18:00
*** spzala has quit IRC18:04
*** pvaneck has quit IRC18:04
*** spzala has joined #openstack-meeting-418:07
*** shaohe_feng has quit IRC18:07
*** shaohe_feng has joined #openstack-meeting-418:08
*** spzala has quit IRC18:11
*** javeriak has quit IRC18:11
*** ihrachys has quit IRC18:12
*** unicell has quit IRC18:13
*** javeriak has joined #openstack-meeting-418:14
*** jaimguer has left #openstack-meeting-418:15
*** shaohe_feng has quit IRC18:18
*** baoli_ has quit IRC18:21
*** baoli has joined #openstack-meeting-418:21
*** unicell has joined #openstack-meeting-418:22
*** shaohe_feng has joined #openstack-meeting-418:23
*** doonhammer has quit IRC18:24
*** shaohe_feng has quit IRC18:28
*** shaohe_feng has joined #openstack-meeting-418:28
*** chem`` has quit IRC18:28
*** bpokorny has joined #openstack-meeting-418:29
*** chem`` has joined #openstack-meeting-418:29
*** mohankumar has quit IRC18:30
*** spzala has joined #openstack-meeting-418:31
*** vishnoianil has quit IRC18:33
*** pvaneck has joined #openstack-meeting-418:33
*** salv-orlando has quit IRC18:33
*** dave-mccowan has joined #openstack-meeting-418:35
*** ddieterly[away] has quit IRC18:38
*** shaohe_feng has quit IRC18:38
*** shaohe_feng has joined #openstack-meeting-418:38
*** asti has left #openstack-meeting-418:39
*** zenoway has joined #openstack-meeting-418:39
*** zenoway has quit IRC18:44
*** shaohe_feng has quit IRC18:48
*** shaohe_feng has joined #openstack-meeting-418:49
*** cloudtrainme has joined #openstack-meeting-418:50
*** claudiub has quit IRC18:50
*** ddieterly has joined #openstack-meeting-418:50
*** zenoway has joined #openstack-meeting-418:56
*** javeriak has quit IRC18:57
*** cwolferh has quit IRC18:57
*** shaohe_feng has quit IRC18:59
*** shaohe_feng has joined #openstack-meeting-418:59
*** baoli has quit IRC19:01
*** baoli has joined #openstack-meeting-419:01
*** jmckind has joined #openstack-meeting-419:02
*** omnipresent has joined #openstack-meeting-419:03
*** zenoway has quit IRC19:07
*** shaohe_feng has quit IRC19:09
*** shaohe_feng has joined #openstack-meeting-419:09
*** matrohon has joined #openstack-meeting-419:13
*** fawadkhaliq has quit IRC19:16
*** jmccrory_ has quit IRC19:19
*** shaohe_feng has quit IRC19:19
*** matrohon has quit IRC19:21
*** vishnoianil has joined #openstack-meeting-419:22
*** baoli has quit IRC19:23
*** matrohon has joined #openstack-meeting-419:23
*** shaohe_feng has joined #openstack-meeting-419:24
*** matrohon has quit IRC19:28
*** shaohe_feng has quit IRC19:29
*** shaohe_feng has joined #openstack-meeting-419:30
*** matrohon has joined #openstack-meeting-419:30
*** bpokorny has quit IRC19:34
*** shaohe_feng has quit IRC19:40
*** shaohe_feng has joined #openstack-meeting-419:40
*** twm2016 has left #openstack-meeting-419:40
*** unicell has quit IRC19:41
*** baoli has joined #openstack-meeting-419:41
*** unicell has joined #openstack-meeting-419:42
*** bpokorny has joined #openstack-meeting-419:47
*** salv-orlando has joined #openstack-meeting-419:49
*** shaohe_feng has quit IRC19:50
*** shaohe_feng has joined #openstack-meeting-419:50
*** ihrachys has joined #openstack-meeting-419:57
*** sdake_ has joined #openstack-meeting-419:58
*** shaohe_feng has quit IRC20:00
*** sdake has quit IRC20:00
*** cwolferh has joined #openstack-meeting-420:01
*** shaohe_feng has joined #openstack-meeting-420:03
*** minwang2 has quit IRC20:03
*** azbiswas has quit IRC20:04
*** unicell has quit IRC20:09
*** shaohe_feng has quit IRC20:10
*** shaohe_feng has joined #openstack-meeting-420:11
*** azbiswas has joined #openstack-meeting-420:12
*** kebray has quit IRC20:13
*** shaohe_feng has quit IRC20:21
*** shaohe_feng has joined #openstack-meeting-420:21
*** ddieterly is now known as ddieterly[away]20:22
*** shaohe_feng has quit IRC20:31
*** shaohe_feng has joined #openstack-meeting-420:32
*** unicell has joined #openstack-meeting-420:32
*** julim_ has quit IRC20:33
*** shaohe_feng has quit IRC20:41
*** numans has quit IRC20:41
*** shaohe_feng has joined #openstack-meeting-420:42
*** salv-orl_ has joined #openstack-meeting-420:44
*** salv-orlando has quit IRC20:47
*** minwang2 has joined #openstack-meeting-420:48
*** ddieterly[away] is now known as ddieterly20:50
*** shaohe_feng has quit IRC20:51
*** shaohe_feng has joined #openstack-meeting-420:52
*** takashin has joined #openstack-meeting-420:52
*** takashin has left #openstack-meeting-420:53
*** rtheis has quit IRC20:56
*** ddieterly is now known as ddieterly[away]20:57
*** ddieterly[away] is now known as ddieterly20:57
*** cloudtrainme has quit IRC21:01
*** shaohe_feng has quit IRC21:02
*** shaohe_feng has joined #openstack-meeting-421:02
*** kebray has joined #openstack-meeting-421:07
*** kebray_ has joined #openstack-meeting-421:08
*** unicell has quit IRC21:09
*** unicell has joined #openstack-meeting-421:09
*** thorst_ has quit IRC21:10
*** thorst_ has joined #openstack-meeting-421:10
*** yamahata has quit IRC21:11
*** kebray has quit IRC21:11
*** thorst__ has joined #openstack-meeting-421:12
*** shaohe_feng has quit IRC21:12
*** shaohe_feng has joined #openstack-meeting-421:13
*** thorst_ has quit IRC21:15
*** azbiswas has quit IRC21:15
*** thorst__ has quit IRC21:16
*** jmckind has quit IRC21:16
*** vhoward has quit IRC21:16
*** rstarmer has joined #openstack-meeting-421:22
*** shaohe_feng has quit IRC21:22
*** shaohe_feng has joined #openstack-meeting-421:23
*** Swami has quit IRC21:26
*** lakshmiS has quit IRC21:28
*** rstarmer has quit IRC21:30
*** woodard has quit IRC21:31
*** woodard has joined #openstack-meeting-421:31
*** shaohe_feng has quit IRC21:32
*** shaohe_feng has joined #openstack-meeting-421:33
*** ddieterly is now known as ddieterly[away]21:34
*** rstarmer has joined #openstack-meeting-421:42
*** shaohe_feng has quit IRC21:43
*** ddieterly[away] is now known as ddieterly21:43
*** rstarmer has quit IRC21:44
*** shaohe_feng has joined #openstack-meeting-421:45
*** rstarmer has joined #openstack-meeting-421:49
*** rbradfor is now known as rbradfor_not_fou21:51
*** rbradfor_not_fou is now known as rbradf_not_found21:52
*** shaohe_feng has quit IRC21:53
*** sdake has joined #openstack-meeting-421:53
*** shaohe_feng has joined #openstack-meeting-421:53
*** sdake_ has quit IRC21:54
*** rstarmer has quit IRC21:56
*** kylek3h has quit IRC21:57
*** amotoki has joined #openstack-meeting-422:02
*** shaohe_feng has quit IRC22:03
*** shaohe_feng has joined #openstack-meeting-422:04
*** ddieterly is now known as ddieterly[away]22:06
*** ddieterly[away] is now known as ddieterly22:06
*** armax_ has joined #openstack-meeting-422:12
*** armax has quit IRC22:13
*** armax_ is now known as armax22:13
*** hvprash_ has joined #openstack-meeting-422:13
*** shaohe_feng has quit IRC22:13
*** hvprash_ has quit IRC22:13
*** shaohe_feng has joined #openstack-meeting-422:14
*** hvprash has quit IRC22:16
*** galstrom is now known as galstrom_zzz22:19
*** LouisF has quit IRC22:20
*** shaohe_feng has quit IRC22:24
*** shaohe_feng has joined #openstack-meeting-422:24
*** spotz is now known as spotz_zzz22:29
*** bobh has quit IRC22:30
*** shaohe_feng has quit IRC22:34
*** shaohe_feng has joined #openstack-meeting-422:35
*** ddieterly has quit IRC22:35
*** shaohe_feng has quit IRC22:44
*** shaohe_feng has joined #openstack-meeting-422:45
*** bobh has joined #openstack-meeting-422:46
*** spzala has quit IRC22:50
*** bobh has quit IRC22:51
*** spzala has joined #openstack-meeting-422:51
*** darrenc is now known as darrenc_afk22:54
*** shaohe_feng has quit IRC22:54
*** spzala has quit IRC22:55
*** shaohe_feng has joined #openstack-meeting-422:55
*** salv-orl_ has quit IRC22:56
*** sdague has quit IRC23:00
*** rromans is now known as rromans_afk23:05
*** shaohe_feng has quit IRC23:05
*** shaohe_feng has joined #openstack-meeting-423:05
*** cwolferh has quit IRC23:05
*** rbak has quit IRC23:06
*** shaohe_feng has quit IRC23:15
*** shaohe_feng has joined #openstack-meeting-423:15
*** darrenc_afk is now known as darrenc23:16
*** ihrachys has quit IRC23:20
*** ihrachys has joined #openstack-meeting-423:21
*** pmesserli has quit IRC23:21
*** salv-orlando has joined #openstack-meeting-423:22
*** cwolferh has joined #openstack-meeting-423:23
*** ihrachys has quit IRC23:25
*** shaohe_feng has quit IRC23:25
*** omnipresent has quit IRC23:25
*** shaohe_feng has joined #openstack-meeting-423:25
*** markvoelker has quit IRC23:29
*** yamahata has joined #openstack-meeting-423:32
*** julim has joined #openstack-meeting-423:33
*** shaohe_feng has quit IRC23:35
*** shaohe_feng has joined #openstack-meeting-423:36
*** raddaoui has quit IRC23:37
*** zenoway has joined #openstack-meeting-423:37
*** zhurong has joined #openstack-meeting-423:41
*** zenoway has quit IRC23:42
*** shaohe_feng has quit IRC23:46
*** hvprash has joined #openstack-meeting-423:47
*** shaohe_feng has joined #openstack-meeting-423:48
*** spzala has joined #openstack-meeting-423:51
*** hvprash has quit IRC23:51
*** ddieterly has joined #openstack-meeting-423:51
*** salv-orlando has quit IRC23:54
*** shaohe_feng has quit IRC23:56
*** banix has quit IRC23:56
*** shaohe_feng has joined #openstack-meeting-423:57

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