Thursday, 2016-07-28

*** salv-orlando has joined #openstack-meeting-400:01
*** Swami has quit IRC00:02
*** ihrachys has quit IRC00:02
*** thorst_ has joined #openstack-meeting-400:02
*** shaohe_feng has quit IRC00:03
*** shaohe_feng has joined #openstack-meeting-400:03
*** mbound has quit IRC00:04
*** salv-orlando has quit IRC00:06
*** thorst_ has quit IRC00:10
*** shaohe_feng has quit IRC00:13
*** shaohe_feng has joined #openstack-meeting-400:14
*** banix has joined #openstack-meeting-400:15
*** shaohe_feng has quit IRC00:23
*** shaohe_feng has joined #openstack-meeting-400:24
*** sarob has quit IRC00:26
*** david-lyle_ has joined #openstack-meeting-400:28
*** limao has joined #openstack-meeting-400:32
*** shaohe_feng has quit IRC00:34
*** shaohe_feng has joined #openstack-meeting-400:34
*** emagana has joined #openstack-meeting-400:37
*** emagana has quit IRC00:41
*** thorst_ has joined #openstack-meeting-400:43
*** thorst_ has quit IRC00:44
*** shaohe_feng has quit IRC00:44
*** thorst_ has joined #openstack-meeting-400:44
*** shaohe_feng has joined #openstack-meeting-400:45
*** pvaneck has quit IRC00:47
*** thorst_ has quit IRC00:52
*** shaohe_feng has quit IRC00:54
*** shaohe_feng has joined #openstack-meeting-400:55
*** cdelatte has quit IRC00:55
*** mbound has joined #openstack-meeting-401:03
*** shaohe_feng has quit IRC01:04
*** shaohe_feng has joined #openstack-meeting-401:05
*** mbound has quit IRC01:08
*** yamamoto_ has joined #openstack-meeting-401:12
*** david-lyle_ has quit IRC01:14
*** shaohe_feng has quit IRC01:15
*** shaohe_feng has joined #openstack-meeting-401:15
*** mfisch has quit IRC01:17
*** Sukhdev has quit IRC01:18
*** bobh has joined #openstack-meeting-401:19
*** bpokorny has quit IRC01:21
*** bobh has quit IRC01:23
*** banix has quit IRC01:24
*** shaohe_feng has quit IRC01:25
*** zhurong has joined #openstack-meeting-401:25
*** thorst_ has joined #openstack-meeting-401:25
*** shaohe_feng has joined #openstack-meeting-401:26
*** sdague has quit IRC01:29
*** banix has joined #openstack-meeting-401:30
*** thorst_ has quit IRC01:34
*** shaohe_feng has quit IRC01:35
*** shaohe_feng has joined #openstack-meeting-401:35
*** mfisch has joined #openstack-meeting-401:39
*** mfisch has quit IRC01:39
*** mfisch has joined #openstack-meeting-401:39
*** shaohe_feng has quit IRC01:45
*** shaohe_feng has joined #openstack-meeting-401:46
*** s3wong has quit IRC01:47
*** shaohe_feng has quit IRC01:56
*** shaohe_feng has joined #openstack-meeting-401:56
*** woodster_ has quit IRC01:59
*** ddieterly has quit IRC01:59
*** coolsvap has joined #openstack-meeting-401:59
*** banix has quit IRC02:00
*** bpokorny has joined #openstack-meeting-402:04
*** thorst_ has joined #openstack-meeting-402:04
*** shaohe_feng has quit IRC02:06
*** baoli has quit IRC02:06
*** shaohe_feng has joined #openstack-meeting-402:06
*** amotoki has quit IRC02:10
*** thorst_ has quit IRC02:10
*** unicell has quit IRC02:10
*** banix has joined #openstack-meeting-402:12
*** iyamahat_ has quit IRC02:12
*** yamahata has quit IRC02:13
*** ajmiller has joined #openstack-meeting-402:13
*** shaohe_feng has quit IRC02:16
*** shaohe_feng has joined #openstack-meeting-402:17
*** itisha has quit IRC02:20
*** ajmiller has quit IRC02:22
*** srwilkers_ has joined #openstack-meeting-402:23
*** shaohe_feng has quit IRC02:26
*** shaohe_feng has joined #openstack-meeting-402:27
*** srwilkers_ has quit IRC02:29
*** bklei has joined #openstack-meeting-402:29
*** yamamoto_ has quit IRC02:31
*** amotoki has joined #openstack-meeting-402:32
*** bklei has quit IRC02:34
*** amotoki has quit IRC02:36
*** sarob has joined #openstack-meeting-402:36
*** shaohe_feng has quit IRC02:37
*** shaohe_feng has joined #openstack-meeting-402:37
*** xenogear has quit IRC02:38
*** thorst_ has joined #openstack-meeting-402:40
*** amotoki has joined #openstack-meeting-402:40
*** sarob has quit IRC02:41
*** thorst_ has quit IRC02:41
*** shaohe_feng has quit IRC02:47
*** shaohe_feng has joined #openstack-meeting-402:47
*** xenogear has joined #openstack-meeting-402:53
*** zhurong has quit IRC02:56
*** shaohe_feng has quit IRC02:57
*** shaohe_feng has joined #openstack-meeting-402:57
*** amotoki has quit IRC03:01
*** zhurong has joined #openstack-meeting-403:03
*** bpokorny has quit IRC03:06
*** shaohe_feng has quit IRC03:07
*** shaohe_feng has joined #openstack-meeting-403:08
*** amotoki has joined #openstack-meeting-403:10
*** vishwanathj has joined #openstack-meeting-403:11
*** iurygregory has quit IRC03:15
*** iurygregory has joined #openstack-meeting-403:15
*** sdake has joined #openstack-meeting-403:15
*** tonytan4ever has joined #openstack-meeting-403:17
*** shaohe_feng has quit IRC03:18
*** shaohe_feng has joined #openstack-meeting-403:18
*** emagana has joined #openstack-meeting-403:19
*** salv-orlando has joined #openstack-meeting-403:20
*** bobh has joined #openstack-meeting-403:21
*** emagana has quit IRC03:24
*** sdake_ has joined #openstack-meeting-403:25
*** Liuqing has joined #openstack-meeting-403:26
*** shz has joined #openstack-meeting-403:26
*** sdake has quit IRC03:27
*** shaohe_feng has quit IRC03:28
*** Kevin_Zheng has joined #openstack-meeting-403:28
*** shaohe_feng has joined #openstack-meeting-403:28
*** shihanzhang has quit IRC03:29
*** salv-orlando has quit IRC03:30
*** shaohe_feng has quit IRC03:38
*** shaohe_feng has joined #openstack-meeting-403:39
*** anilvenkata has joined #openstack-meeting-403:40
*** anilvenkata has quit IRC03:44
*** vishnoianil has quit IRC03:45
*** david-lyle_ has joined #openstack-meeting-403:45
*** sdake_ has quit IRC03:46
*** sdake has joined #openstack-meeting-403:46
*** shaohe_feng has quit IRC03:48
*** shaohe_feng has joined #openstack-meeting-403:49
*** nmadhok has quit IRC03:50
*** david-lyle_ is now known as david-lyle03:54
*** shaohe_feng has quit IRC03:59
*** julim has quit IRC03:59
*** shaohe_feng has joined #openstack-meeting-403:59
*** julim has joined #openstack-meeting-404:02
*** julim has quit IRC04:02
*** links has joined #openstack-meeting-404:03
*** david-lyle has quit IRC04:07
*** shaohe_feng has quit IRC04:09
*** shaohe_feng has joined #openstack-meeting-404:10
*** david-lyle has joined #openstack-meeting-404:11
*** Sukhdev has joined #openstack-meeting-404:15
*** shaohe_feng has quit IRC04:19
*** IlyaG has joined #openstack-meeting-404:20
*** shaohe_feng has joined #openstack-meeting-404:20
*** bobh has quit IRC04:23
*** shaohe_feng has quit IRC04:29
*** shaohe_feng has joined #openstack-meeting-404:30
*** javeriak has joined #openstack-meeting-404:36
*** javeriak has quit IRC04:38
*** shaohe_feng has quit IRC04:40
*** shaohe_feng has joined #openstack-meeting-404:40
*** javeriak has joined #openstack-meeting-404:48
*** shaohe_feng has quit IRC04:50
*** shaohe_feng has joined #openstack-meeting-404:51
*** banix has quit IRC04:55
*** javeriak has quit IRC04:57
*** Sukhdev has quit IRC04:58
*** IlyaG has quit IRC04:58
*** shaohe_feng has quit IRC05:00
*** shaohe_feng has joined #openstack-meeting-405:00
*** vikasc has joined #openstack-meeting-405:04
*** khushbu has joined #openstack-meeting-405:07
*** shaohe_feng has quit IRC05:10
*** shaohe_feng has joined #openstack-meeting-405:11
*** shaohe_feng has quit IRC05:21
*** shaohe_feng has joined #openstack-meeting-405:21
*** unicell has joined #openstack-meeting-405:24
*** bobh has joined #openstack-meeting-405:24
*** javeriak has joined #openstack-meeting-405:25
*** javeriak has quit IRC05:25
*** javeriak has joined #openstack-meeting-405:25
*** bobh has quit IRC05:29
*** shaohe_feng has quit IRC05:31
*** shaohe_feng has joined #openstack-meeting-405:31
*** khushbu has quit IRC05:36
*** javeriak_ has joined #openstack-meeting-405:37
*** iyamahat has joined #openstack-meeting-405:37
*** anilvenkata has joined #openstack-meeting-405:38
*** javeriak has quit IRC05:38
*** shaohe_feng has quit IRC05:41
*** gongysh has joined #openstack-meeting-405:41
*** shaohe_feng has joined #openstack-meeting-405:42
*** iyamahat has quit IRC05:43
*** dshakhray_ has joined #openstack-meeting-405:47
*** amotoki_ has joined #openstack-meeting-405:48
*** sarob has joined #openstack-meeting-405:49
*** unicell has quit IRC05:49
*** unicell has joined #openstack-meeting-405:50
*** khushbu has joined #openstack-meeting-405:50
*** amotoki has quit IRC05:51
*** mohankumar has joined #openstack-meeting-405:51
*** shaohe_feng has quit IRC05:51
*** shaohe_feng has joined #openstack-meeting-405:52
*** sarob has quit IRC05:53
*** mohankumar has quit IRC05:55
*** yamahata has joined #openstack-meeting-405:55
*** gongysh has quit IRC05:58
*** shaohe_feng has quit IRC06:02
*** david-lyle has quit IRC06:02
*** shaohe_feng has joined #openstack-meeting-406:02
*** mohankumar has joined #openstack-meeting-406:09
*** shaohe_feng has quit IRC06:12
*** javeriak_ has quit IRC06:12
*** shaohe_feng has joined #openstack-meeting-406:13
*** lelouch_ has joined #openstack-meeting-406:17
*** pcaruana has joined #openstack-meeting-406:17
*** gongysh has joined #openstack-meeting-406:19
*** shaohe_feng has quit IRC06:22
*** shaohe_feng has joined #openstack-meeting-406:23
*** bobh has joined #openstack-meeting-406:25
*** yamamoto_ has joined #openstack-meeting-406:27
*** bobh has quit IRC06:31
*** gongysh has quit IRC06:32
*** shaohe_feng has quit IRC06:32
*** shaohe_feng has joined #openstack-meeting-406:33
*** tonytan4ever has quit IRC06:38
*** sdake has quit IRC06:42
*** shaohe_feng has quit IRC06:43
*** shaohe_feng has joined #openstack-meeting-406:43
*** salv-orlando has joined #openstack-meeting-406:48
*** vishwanathj has quit IRC06:49
*** shaohe_feng has quit IRC06:53
*** shaohe_feng has joined #openstack-meeting-406:53
*** javeriak has joined #openstack-meeting-406:57
*** irenab has joined #openstack-meeting-407:03
*** shaohe_feng has quit IRC07:03
*** shaohe_feng has joined #openstack-meeting-407:04
*** vishnoianil has joined #openstack-meeting-407:04
*** shaohe_feng has quit IRC07:13
*** shaohe_feng has joined #openstack-meeting-407:14
*** ihrachys has joined #openstack-meeting-407:21
*** shaohe_feng has quit IRC07:24
*** shaohe_feng has joined #openstack-meeting-407:24
*** gongysh has joined #openstack-meeting-407:25
*** bobh has joined #openstack-meeting-407:27
*** tonytan4ever has joined #openstack-meeting-407:29
*** bobh has quit IRC07:32
*** shaohe_feng has quit IRC07:34
*** shaohe_feng has joined #openstack-meeting-407:34
*** ihrachys has quit IRC07:40
*** khushbu has quit IRC07:41
*** dshakhray_ has quit IRC07:44
*** shaohe_feng has quit IRC07:44
*** shaohe_feng has joined #openstack-meeting-407:44
*** sarob has joined #openstack-meeting-407:49
*** armax has quit IRC07:50
*** emagana has joined #openstack-meeting-407:51
*** andymaier has joined #openstack-meeting-407:51
*** vikasc has quit IRC07:53
*** sarob has quit IRC07:54
*** shaohe_feng has quit IRC07:54
*** shaohe_feng has joined #openstack-meeting-407:55
*** emagana has quit IRC07:56
*** matrohon has joined #openstack-meeting-408:01
*** salv-orlando has quit IRC08:01
*** shaohe_feng has quit IRC08:05
*** andymaier has quit IRC08:05
*** shaohe_feng has joined #openstack-meeting-408:05
*** reedip has quit IRC08:11
*** shaohe_feng has quit IRC08:15
*** shaohe_feng has joined #openstack-meeting-408:16
*** vikasc has joined #openstack-meeting-408:23
*** shaohe_feng has quit IRC08:25
*** reedip has joined #openstack-meeting-408:27
*** shaohe_feng has joined #openstack-meeting-408:28
*** bobh has joined #openstack-meeting-408:29
*** khushbu_ has joined #openstack-meeting-408:30
*** vikasc has quit IRC08:31
*** bobh has quit IRC08:33
*** numans has joined #openstack-meeting-408:34
*** shaohe_feng has quit IRC08:35
*** shaohe_feng has joined #openstack-meeting-408:36
*** dshakhray_ has joined #openstack-meeting-408:36
*** Liuqing_ has joined #openstack-meeting-408:39
*** Liuqing has quit IRC08:40
*** shaohe_feng has quit IRC08:46
*** sambetts|afk is now known as sambetts08:46
*** shaohe_feng has joined #openstack-meeting-408:47
*** tonytan4ever has quit IRC08:51
*** khushbu_ has quit IRC08:53
*** andymaier has joined #openstack-meeting-408:53
*** shaohe_feng has quit IRC08:56
*** shaohe_feng has joined #openstack-meeting-408:57
*** shaohe_feng has quit IRC09:06
*** shaohe_feng has joined #openstack-meeting-409:07
*** javeriak has quit IRC09:07
*** javeriak has joined #openstack-meeting-409:08
*** shaohe_feng has quit IRC09:16
*** shaohe_feng has joined #openstack-meeting-409:17
*** limao has quit IRC09:22
*** rahuls has quit IRC09:22
*** rahuls has joined #openstack-meeting-409:22
*** shaohe_feng has quit IRC09:27
*** shaohe_feng has joined #openstack-meeting-409:27
*** rahuls_ has joined #openstack-meeting-409:28
*** rahuls has quit IRC09:28
*** reedip has quit IRC09:29
*** bobh has joined #openstack-meeting-409:29
*** javeriak has quit IRC09:29
*** bobh has quit IRC09:34
*** shaohe_feng has quit IRC09:37
*** shaohe_feng has joined #openstack-meeting-409:38
*** lelouch_ has quit IRC09:39
*** yamamoto_ has quit IRC09:43
*** shaohe_feng has quit IRC09:47
*** shaohe_feng has joined #openstack-meeting-409:48
*** lelouch_ has joined #openstack-meeting-409:51
*** jschwarz is now known as jschwarz|afk09:51
*** ihrachys has joined #openstack-meeting-409:54
*** iyamahat has joined #openstack-meeting-409:55
*** _degorenko|afk is now known as degorenko09:56
*** mbound has joined #openstack-meeting-409:56
*** shaohe_feng has quit IRC09:57
*** shaohe_feng has joined #openstack-meeting-409:58
*** yamahata has quit IRC09:58
*** iyamahat has quit IRC10:01
*** zhurong has quit IRC10:07
*** shaohe_feng has quit IRC10:08
*** salv-orlando has joined #openstack-meeting-410:08
*** shaohe_feng has joined #openstack-meeting-410:09
*** Liuqing_ has quit IRC10:09
*** jschwarz|afk is now known as jschwarz10:15
*** salv-orlando has quit IRC10:15
*** iberezovskiy|off is now known as iberezovskiy10:16
*** shaohe_feng has quit IRC10:18
*** shaohe_feng has joined #openstack-meeting-410:19
*** shaohe_feng has quit IRC10:28
*** shaohe_feng has joined #openstack-meeting-410:29
*** bobh has joined #openstack-meeting-410:30
*** mbound has quit IRC10:32
*** bobh has quit IRC10:35
*** emagana has joined #openstack-meeting-410:36
*** shaohe_feng has quit IRC10:38
*** sdague has joined #openstack-meeting-410:39
*** shaohe_feng has joined #openstack-meeting-410:39
*** emagana has quit IRC10:41
*** yamamoto has joined #openstack-meeting-410:46
*** shaohe_feng has quit IRC10:49
*** yamamoto has quit IRC10:49
*** shaohe_feng has joined #openstack-meeting-410:49
*** yamamoto has joined #openstack-meeting-410:54
*** liwei has joined #openstack-meeting-410:54
*** dshakhray_ has quit IRC10:55
*** dshakhray has joined #openstack-meeting-410:55
*** thorst has joined #openstack-meeting-410:56
*** shaohe_feng has quit IRC10:59
*** shaohe_feng has joined #openstack-meeting-411:00
*** shaohe_feng has quit IRC11:09
*** shaohe_feng has joined #openstack-meeting-411:10
*** shz has quit IRC11:16
*** shz has joined #openstack-meeting-411:16
*** GB21 has quit IRC11:18
*** shaohe_feng has quit IRC11:19
*** shaohe_feng has joined #openstack-meeting-411:20
*** tinwood is now known as tinwood-lunch11:23
*** shaohe_feng has quit IRC11:30
*** shaohe_feng has joined #openstack-meeting-411:30
*** bobh has joined #openstack-meeting-411:31
*** salv-orlando has joined #openstack-meeting-411:33
*** rtheis has joined #openstack-meeting-411:34
*** bobh has quit IRC11:35
*** gongysh has quit IRC11:37
*** shaohe_feng has quit IRC11:40
*** shaohe_feng has joined #openstack-meeting-411:40
*** banix has joined #openstack-meeting-411:45
*** sarob has joined #openstack-meeting-411:50
*** shaohe_feng has quit IRC11:50
*** shaohe_feng has joined #openstack-meeting-411:50
*** tonytan4ever has joined #openstack-meeting-411:53
*** sarob has quit IRC11:55
*** banix has quit IRC11:55
*** Liuqing has joined #openstack-meeting-411:56
*** tonytan4ever has quit IRC11:57
*** shaohe_feng has quit IRC12:00
*** hvprash has quit IRC12:01
*** shaohe_feng has joined #openstack-meeting-412:03
*** bogdando has quit IRC12:04
*** liwei has quit IRC12:05
*** amotoki_ has quit IRC12:06
*** shaohe_feng has quit IRC12:11
*** shaohe_feng has joined #openstack-meeting-412:11
*** amotoki has joined #openstack-meeting-412:13
*** cbits has joined #openstack-meeting-412:15
*** bogdando has joined #openstack-meeting-412:15
*** hvprash has joined #openstack-meeting-412:16
*** tinwood-lunch is now known as tinwood12:16
*** hvprash has quit IRC12:18
*** hvprash has joined #openstack-meeting-412:20
*** shaohe_feng has quit IRC12:21
*** shaohe_feng has joined #openstack-meeting-412:21
*** bogdando has quit IRC12:22
*** hvprash_ has joined #openstack-meeting-412:22
*** bogdando has joined #openstack-meeting-412:25
*** hvprash has quit IRC12:25
*** sarob has joined #openstack-meeting-412:27
*** hvprash has joined #openstack-meeting-412:30
*** shaohe_feng has quit IRC12:31
*** bobh has joined #openstack-meeting-412:31
*** shaohe_feng has joined #openstack-meeting-412:32
*** sarob has quit IRC12:32
*** hvprash has quit IRC12:33
*** hvprash_ has quit IRC12:33
*** amotoki has quit IRC12:34
*** dave-mccowan has joined #openstack-meeting-412:35
*** bobh has quit IRC12:36
*** salv-orlando has quit IRC12:36
*** amotoki has joined #openstack-meeting-412:39
*** links has quit IRC12:40
*** yamamoto has quit IRC12:40
*** shaohe_feng has quit IRC12:41
*** shaohe_feng has joined #openstack-meeting-412:42
*** julim has joined #openstack-meeting-412:43
*** klamath has joined #openstack-meeting-412:46
*** klamath has quit IRC12:46
*** klamath has joined #openstack-meeting-412:46
*** amotoki has quit IRC12:47
*** mbound has joined #openstack-meeting-412:49
*** shaohe_feng has quit IRC12:52
*** shaohe_feng has joined #openstack-meeting-412:52
*** baoli has joined #openstack-meeting-412:53
*** baoli_ has joined #openstack-meeting-412:54
*** cleong has joined #openstack-meeting-412:54
*** woodster_ has joined #openstack-meeting-412:55
*** baoli has quit IRC12:58
*** shaohe_feng has quit IRC13:02
*** shaohe_feng has joined #openstack-meeting-413:03
*** numans has quit IRC13:06
*** shaohe_feng has quit IRC13:12
*** amotoki has joined #openstack-meeting-413:12
*** shaohe_feng has joined #openstack-meeting-413:13
*** gongysh has joined #openstack-meeting-413:16
*** pmesserli has joined #openstack-meeting-413:16
*** numans has joined #openstack-meeting-413:17
*** rainya has joined #openstack-meeting-413:18
*** emagana has joined #openstack-meeting-413:19
*** shaohe_feng has quit IRC13:22
*** rainya has quit IRC13:23
*** emagana has quit IRC13:24
*** rainya has joined #openstack-meeting-413:24
*** shaohe_feng has joined #openstack-meeting-413:25
*** banix has joined #openstack-meeting-413:26
*** markvoelker has joined #openstack-meeting-413:30
*** trozet has quit IRC13:32
*** shaohe_feng has quit IRC13:33
*** markvoelker has quit IRC13:34
*** trozet has joined #openstack-meeting-413:35
*** shaohe_feng has joined #openstack-meeting-413:36
*** sdake has joined #openstack-meeting-413:36
*** woodard has joined #openstack-meeting-413:40
*** yamamoto has joined #openstack-meeting-413:41
*** shaohe_feng has quit IRC13:43
*** shaohe_feng has joined #openstack-meeting-413:44
*** yamamoto has quit IRC13:46
*** itisha has joined #openstack-meeting-413:46
*** liwei has joined #openstack-meeting-413:48
*** aavraham has joined #openstack-meeting-413:51
*** Liuqing has quit IRC13:51
*** croelandt has joined #openstack-meeting-413:52
*** Liuqing has joined #openstack-meeting-413:52
*** tonytan4ever has joined #openstack-meeting-413:52
*** shaohe_feng has quit IRC13:53
*** shaohe_feng has joined #openstack-meeting-413:54
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, kairat, aavraham13:57
*** mfedosin has joined #openstack-meeting-413:57
*** ddieterly has joined #openstack-meeting-413:58
*** rbak has joined #openstack-meeting-413:58
dshakhrayo/13:58
nikhil#startmeeting glance14:00
openstackMeeting started Thu Jul 28 14:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
hemanthmo/14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
rosmaitao/14:00
hemanthmo/14:00
itishao/14:00
kragnizo/14:00
mfedosino/14:00
nikhilwelcome all14:00
nikhillet's get started14:00
nikhil#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
nikhil#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
*** anilvenkata has quit IRC14:00
nikhilwe've a full agenda today14:01
nikhilso, I have set a recommended time limit to help us plan our conversations properly14:01
*** bunting has joined #openstack-meeting-414:01
nikhilplease take a look at the agenda etherpad for more details14:01
*** sskripnick has joined #openstack-meeting-414:01
nikhil#topic Glare  ( mfedosin )14:01
*** openstack changes topic to "Glare ( mfedosin ) (Meeting topic: glance)"14:01
buntingo/14:01
mfedosinhi :)14:02
mfedosinI don't know where to start...14:02
nikhilI know this one update14:02
nikhil#link https://review.openstack.org/34799914:02
mfedosinwe fixed few bugs in glare code14:02
*** Jokke_ has joined #openstack-meeting-414:02
Jokke_o/14:02
croelandt\o14:03
mfedosinyeah, it was a request from app-catalog community14:03
mfedosinto store content-type for blobs14:03
flaper87o/14:03
*** shaohe_feng has quit IRC14:03
mfedosinbecause as you may know glance supports only application/octet-stream14:03
nikhilI think the use case needs to go in the spec14:04
mfedosinso, for this reason we had to think off our own content-type when user wants to add a location to blob14:04
*** shaohe_feng has joined #openstack-meeting-414:04
mfedosinpreviously it was 'application/json'14:04
*** hvprash has joined #openstack-meeting-414:04
mfedosinbut now we have to differentiate them somehow14:04
mfedosinnikhil: there is a use-case in the spec14:05
mfedosininitially we wanted to call it application/glare-external-location14:05
mfedosinbut then I found out that this name is not restful :)14:06
mfedosinand now it is application/vnd+openstack.glare-custom-location+json14:06
*** dshakhray_ has joined #openstack-meeting-414:06
sskripnickthis is not looks like separate use-case. User uploaded blob with content-type "image/gif" and other user can see "Content-type: image/gif" when getting this blob14:06
mfedosinwe were guided by http://restcookbook.com/Resources/using-custom-content-types/14:07
* sigmavirus is late, sorry14:07
mfedosinsskripnick: makes sense, I'll add it to the spec14:07
mfedosinanyway I'll have to update it, because commit message is wrong...14:08
rosmaitai am confused about the 'location' part of the name when it's a content type, or am i confusing 2 different use casees14:08
* nikhil will have to dig into glare spec again..14:08
sigmavirusnikhil: me too14:09
sskripnickwe can avoid custom content-type by using other url for external blobs14:09
nikhil:)14:09
sigmavirusmfedosin: why not application/vnd+openstack.glare.custom-location+json?14:09
*** hvprash_ has joined #openstack-meeting-414:09
rosmaitaok, we can discuss on the spec patch14:09
nikhilI like what sskripnick suggests but yes on the spec would be nice14:10
* sigmavirus nods14:10
sskripnicklike POST /api/artifacts/glance-image/some-uuid/icon/external (with application/json)14:10
nikhil1 min to go on this topic14:10
nikhilouch, that prolly won't work14:10
mfedosinthe use case is called * **Use Case 8.** Add a custom location for artifact.14:10
mfedosinalso I wanted to share sskripnick's work with you14:10
mfedosinhttp://r-ci.tk:8100/14:10
mfedosinit's app-catalog based on glare v114:10
*** ajmiller has joined #openstack-meeting-414:11
mfedosinit's very early prototype14:11
rosmaitacool!14:11
mfedosinbut I think it looks good14:11
* nikhil wonders why is 'image' again being referred in glare14:11
nikhilexcellent, can't wait to see it14:11
mfedosinnikhil: because app-catalog wants to distribute images14:11
mfedosinit's what we have now http://apps.openstack.org/14:12
*** pmesserli has quit IRC14:12
*** hvprash has quit IRC14:12
nikhilso they need to use glance14:12
nikhilI am asking why is images being used in glare API14:12
mfedosinnikhil: no, they don't14:12
nikhilok14:12
mfedosinask docaedo14:12
nikhilwell, we WONT support images in glare API14:12
nikhiland that was decided14:12
*** pmesserli has joined #openstack-meeting-414:12
nikhilwe need to move on the next topic14:12
nikhilsorry, this needs further discussion14:12
nikhil#topic Nova v1, v2 ( nikhil )14:13
*** openstack changes topic to "Nova v1, v2 ( nikhil ) (Meeting topic: glance)"14:13
sskripnickdo we have to use glare to store all artifacts, and something other to store glance images (in app catalog?)14:13
mfedosinyou work in one company and I think you'll find some strategic vision with docaedo :)14:13
*** shaohe_feng has quit IRC14:14
mfedosinoh, there was a bug with glance's schemas in Nova14:14
*** Liuqing has quit IRC14:14
nikhilsorry guys, sskripnick , mfedosin  we need to talk offline on this. they can't use images API in glare and that's it. it's not about companies, it's about ecosystem. we14:14
*** dshakhray_ has quit IRC14:14
*** shaohe_feng has joined #openstack-meeting-414:14
nikhil(we're on the next topic)14:14
nikhilthere's this bug that was causing some pain14:14
nikhil#link https://bugs.launchpad.net/python-glanceclient/+bug/159660214:14
openstackLaunchpad bug 1596602 in python-glanceclient "Instance Snapshot failure: "Unable to set 'kernel_id' to 'None'. Reason: None is not of type u'string'"" [High,Fix released] - Assigned to Mike Fedosin (mfedosin)14:14
nikhilthanks to mfedosin for a quick fix14:15
*** Liuqing has joined #openstack-meeting-414:15
mfedosinI did not have time to finish the second patch today14:15
nikhilwe've resolved the issue with snapshots14:15
*** gongysh has quit IRC14:15
*** kairat has joined #openstack-meeting-414:15
kairato/14:15
mfedosinbut I agree with Matt14:15
nikhilbut there could be more places in nova when the additional properties may not be matching schema and nova isn't validating schema14:15
mfedosinI'll send the update right after this meeting14:16
nikhilif you know people who are using virt drivers and have a test missing by chance, please ask them to negative test that snapshot, update image using nova, etc.14:16
nikhilthat way we will be able to exhaustively exclude corner cases and avoid last minute hustle14:17
nikhilotherwise, we're looking good on nova using v2. and they've deprecated the proxy for images as per my last read on the ML email.14:17
*** hvprash_ has quit IRC14:17
nikhilI will try to find time to propose the v1 deprecartion spec as it overlaps with some other work. more on this next week.14:18
*** hvprash has joined #openstack-meeting-414:18
nikhilmoving on14:18
nikhil#topic Releases  ( nikhil )14:18
*** openstack changes topic to "Releases ( nikhil ) (Meeting topic: glance)"14:18
nikhilI was able to get glance_store 0.15.0 released this week14:18
nikhilthe 0.14.0 caused issues in gate and has been blocked in g-r u-c14:19
nikhilwe need a couple more of store releases this cycle14:19
nikhilespecially one that includes the removal of s314:19
*** hvprash_ has joined #openstack-meeting-414:19
nikhilyou can find more updates:14:19
nikhilhttps://bugs.launchpad.net/glance-store/+bug/160564814:19
openstackLaunchpad bug 1605648 in glance_store "help text string on config fails translations and breaks glance docs" [Critical,Confirmed]14:19
Jokke_so that sohuld be a big one 1.0.0?14:20
nikhilhttps://bugs.launchpad.net/glance-store/+bug/160674614:20
openstackLaunchpad bug 1606746 in glance_store "cinder driver config string with %(tenant)s breaks glance gate and is preventing further store release" [Critical,Fix released] - Assigned to Nikhil Komawar (nikhil-komawar)14:20
nikhilhttps://review.openstack.org/#/c/347595/14:20
*** piet has joined #openstack-meeting-414:20
nikhilI plan to release one right after removal of s3 is merged14:20
nikhilJokke_: last time we removed one driver it was a minor bump14:21
kairatI think we need to refactor store api a bit before releasing 1.014:21
nikhilour 1.0.0 is expected after the api refactor14:21
Jokke_nikhil: oh we did14:21
*** galstrom_zzz is now known as galstrom14:21
mfedosinI liked s3, even if it didn't work well :(14:21
* Jokke_ tought that backwards incompatibilities were major14:21
mfedosinagree with kairat, only after the refactoring14:22
Jokke_or was it agreed minor due to the 0. series versioning still?14:22
nikhilI will check the semver docs and see what comes up14:22
*** hvprash has quit IRC14:22
nikhilwill share the details before proposing a release and add Jokke_ to that review q.s.14:23
Jokke_anyways, fortunately version numbers are cheap14:23
Jokke_:D14:23
nikhil:)14:23
nikhilso the release of client libs is earlier than n-314:23
nikhilplease prioritize your reviews on store first, then client and server14:23
nikhilthat's it from me on this topic14:24
*** shaohe_feng has quit IRC14:24
nikhilmoving on14:24
nikhil#topic Project Mascot  ( nikhil )14:24
*** openstack changes topic to "Project Mascot ( nikhil ) (Meeting topic: glance)"14:24
nikhilSo, congrats all: our mascot has been selected14:24
nikhilillustrator has been given details about the same14:25
*** shaohe_feng has joined #openstack-meeting-414:25
nikhil#info Email confirmed Chipmunk as selected mascot for glance14:25
nikhil    Note sent to ask the designer to ensure that the chipmunk is shown chewing nuts14:25
nikhilIllustrations will include text and logo, another with just logo and one with just text.14:25
Jokke_ \\o \o/ o// o/714:25
nikhiltentatively available before summit for team to use in their presentations14:25
rosmaitawe need an ascii art version too, so we can put it in specs14:26
hemanthmhaha14:26
nikhilha14:26
Jokke_rosmaita: ++14:26
nikhilI think that would not be official unless our default one is in ascii14:26
Jokke_rosmaita: and release commit messages14:26
nikhilbut that would mean everyone needs to choose that way14:26
nikhilwhich is right hard to get14:26
nikhils/right/rather/14:27
rosmaitawe need to send a strongly worded message to the TC saying we must have ascii art14:27
nikhilawesome :)14:27
Jokke_flaper87: get it done14:27
nikhilmoving one in the interest of time14:27
nikhil#topic Alembic for Glance migrations (hemanthm)14:27
*** openstack changes topic to "Alembic for Glance migrations (hemanthm) (Meeting topic: glance)"14:27
hemanthmLast week we spoke briefly about moving glance migrations to alembic.14:27
hemanthmI'm working on a PoC to port the migrations over to alembic.14:28
hemanthmWhile I have a couple of things to discuss related to it, let me first see if there are any comments/concerns/suggestions from last week.14:28
hemanthm(since we didn't get enough time in last week's meeting to discuss this)14:28
* nikhil finds link to last weeks mtg14:29
Jokke_hemanthm: one quick one14:29
nikhilhttp://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-07-21-14.00.html14:29
nikhilrather:14:29
nikhil#link http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-07-21-14.00.log.html#l-25314:29
Jokke_hemanthm: will we need to have both, sqlalchemy to do versions until now and then alembic taking care from that, or migrate all our current ones to alembic?14:29
hemanthmJokke_: the latter14:29
hemanthmessentially replacing migrate with alembic14:30
Jokke_that needs to be well tested between all supported version bumps then that we get same results14:30
hemanthmJokke_: absolutely14:31
hemanthmand this sort of leads to the first thing I wanted to discuss today14:31
hemanthmSince we are taking a fresh look at the migrations, how about starting directly with the kilo schema?14:31
hemanthmIs there any reason we would like to preserve the previous migrations?14:31
nikhilhemanthm are you planning ahead for ocata?14:31
hemanthmnikhil: yes14:31
nikhilk, ty14:32
hemanthmnot planning on getting this one into newton14:32
hemanthmjust trying to keep it ready when Ocata opens14:32
hemanthmthat way we can use that for Ocata migrations14:32
nikhilhemanthm: we would like to preserve old style migrations for stable branches14:32
hemanthmyes, so starting from kilo should be fine right?14:33
nikhilatm, I think so but need to ask around if there're any concerns14:33
nikhilbasically, we/openstack support n, n+1 so that way it's acceptable14:34
nikhilnot sure what happens when someone jumps a migrations and what our message needs to be14:34
*** shaohe_feng has quit IRC14:34
nikhils/jumps a migrations/jumps a cycle/14:34
rosmaitai don't think we support skipping releases?14:34
hemanthm(FYI) Neutron did the same thing, they started with kilo as a base and ported migrations from there on to alembic14:34
nikhilwe dont14:34
hemanthmyeah, we don't14:35
*** shaohe_feng has joined #openstack-meeting-414:35
rosmaitathough i noticed that someone proposed a talk about how to skip releases in openstack14:35
rosmaitaso everyone vote it down!14:35
rosmaita(if you can find it)14:35
nikhilbut that's not stopping someone fromo doing that and if a big corporation does it14:35
*** spotz_zzz is now known as spotz14:35
nikhildoes it ... you reflected my exact thoughts above ( rosmaita )14:35
rosmaitathat's true, it's open source, people can do anything14:36
*** zhurong has joined #openstack-meeting-414:36
rosmaitabut they shouldn't!14:36
*** matrohon has quit IRC14:36
nikhilhemanthm: any other important point? ( 3 more mins)14:36
hemanthmyes, just one more14:36
hemanthmHow about dropping downgrades altogether?14:37
nikhiljust review the proposal already14:37
nikhilspec is approved iirc14:37
hemanthmI mean, not porting over the downgrades to alembic14:37
nikhil#link https://review.openstack.org/22922014:37
rosmaitajust need to check when openstack stopped supporting downgrades14:38
rosmaitahopefully it was in kilo14:38
nikhiloh well, for now we can go with that. let's see what people think.14:38
hemanthmsure, not porting downgrades for now then14:38
hemanthmthat's all from me on this topic14:39
*** marst has quit IRC14:39
nikhil#link http://specs.openstack.org/openstack/openstack-specs/specs/no-downward-sql-migration.html14:39
nikhilthanks hemanthm , we finished this one on time14:39
nikhil#topic What to do about alernative location strategies? (rosmaita)14:39
*** openstack changes topic to "What to do about alernative location strategies? (rosmaita) (Meeting topic: glance)"14:39
rosmaitaOK, i will try to be brief about this.  We are talking about:14:39
rosmaita#link https://review.openstack.org/#/c/336761/14:40
rosmaitaHere is what is at issue, it is associated with multiple image locations14:40
rosmaitaWe have a config setting that allows you to specify a location_strategy to use14:40
rosmaitaGlance comes with 2 strategies14:40
rosmaitaOperators have requested some more and actually submitted patches for some, here is an example:14:40
rosmaita#link https://review.openstack.org/#/c/268865/14:40
rosmaita(i am typing as fast as i can)14:40
rosmaitaA change was made at some point as part of refactoring to use oslo_config better that restricted the value of the config option to the 2 pre-packaged ones14:40
nikhilrosmaita: np, you14:40
nikhilyou have 9 mins14:41
rosmaitaBut the location strategy code uses stevedore to load the modules and figures out what strategy names are available from that way14:41
rosmaitaSo it looks like this functionality was designed to be easily extensible by operators14:41
rosmaitaBut, the original blueprint (pre-spec days) does not explicitly say that14:41
rosmaitaFurther, as Jokke_ points out on the patch, the image locations present security problems even when used properly14:41
*** hvprash_ has quit IRC14:41
rosmaitaBut, if you look at the proposed new location strategy on review 268865 (link above), you can see that any customized policy is going to be very idiosyncratic to each deployment.14:42
*** hvprash has joined #openstack-meeting-414:42
rosmaitaThe one on that patch is designed to be general, but you can see that in one of the comments, I tried to see how it would work, and it is very tricky.14:42
rosmaitaI think the deployment who proposed it will get it to work OK, but difficult for others14:42
rosmaitaAnyway, the point is: what is our attitude toward this kind of thing?  Do we want to make operators submit new location strategies as patches to Glance and only allow ones that make it through Glance code review?  Of just make them fork/patch Glance if they want a custom strategy?14:42
* rosmaita takes deep breath14:42
nikhilthanks14:43
nikhilI did not digest the issue Jokke_ poised on the location stuff to be used with strategy14:43
kairatsame for me14:43
kairatwhat is security issue with stevedore?14:43
*** singlethink has joined #openstack-meeting-414:43
nikhilmay be we need to discuss deprecating the multiple locations config option and use policies by default?14:43
nikhil#link https://review.openstack.org/31393614:44
kairatI know that Heat used it for custom resources14:44
nikhilif the strategy be used by admins, we won't have serious issue (no more than what exists in nova, ironic, etc)14:44
*** shaohe_feng has quit IRC14:44
*** shaohe_feng has joined #openstack-meeting-414:45
*** piet has quit IRC14:45
*** dasanind has joined #openstack-meeting-414:45
* nikhil puts this review on his priority list14:45
Jokke_so if we decide to open the location strategies to the wild, IMO we encourage to utilize the multiple locations options (the strategies really doesn't make any sense without them)14:45
kairatah14:45
Jokke_And that opens up the can of worms we have tried to patch over 2 cycles now14:45
nikhilif that's the case:14:46
nikhilI think we need to take a stand either:14:46
nikhil1) remove this feature in glance where you can set custom locations14:46
kairatnow it is more clear, thanks14:46
nikhil2) document clearly how this is for admins only and what repercussions are when they use it14:47
nikhilsince a lot of the teams are asking for this feature like fast snapshots in nova, I was inclining towards 2)14:47
nikhilthe use case proposed by Jake Yip with his complex strategy is for (Again) ceph based use case14:48
* Jokke_ could imagine that limiting it admin only will probably kill most of the use cases for this functionality14:48
nikhil(where resiliency of swift is having competition of performance of ceph)14:48
nikhils/of/with/14:48
mfedosinnikhil: Can you to provide feedback http://lists.openstack.org/pipermail/openstack-dev/2016-July/100040.html14:48
Jokke_anyways, I think this is seriously matter of spec, not a bug fix14:49
kairat++14:49
mfedosinI got a lot of requests from Horizon and they don't know what to do with locations14:49
Jokke_mfedosin: tell them to stop using them ;)14:49
nikhilmfedosin: I will, just that I find it tiring to type the same things :) these teams have asked for feedback earlier and haven't paid attn.14:49
Jokke_the best solution ever14:49
kairatmaybe redesign it14:49
kairat?14:49
rosmaitaok, so what do we want a spec to be about?14:50
nikhilkairat: and fei long: please work on a redesign or workaround for this together. we can review your work on a spec. works?14:50
nikhilrosmaita: yeah, I think that's a good question:14:50
kairatI can help with consultation for fei long14:50
mfedosinJokke_: not to use glance? :)14:50
kairatsince I was involved in glare implmentation14:51
nikhilit should include:14:51
Jokke_rosmaita: the use cases, what option we do have reaching them and their impact/dependency of the multiple locations access14:51
nikhil1) fei long's use case as a subset of use cases for image location14:51
Jokke_mfedosin: good luck with that, but not use custom locations14:51
hemanthmit feels like we just shouldn't encourage any changes to location strategy before figuring out the locations issue14:51
Jokke_hemanthm: ++14:51
nikhil2) concerns poised by image locations (PLEASE DO NOT LINK PRIVATE BUGS UNLESS YOU CONSULT glance-core-sec)14:51
hemanthmbe it a spec or bug fix14:52
mfedosinJokke_: users will be disappointed14:52
nikhil3) workaround or a redesign14:52
kairatJokke_, what if we validate checksum and size when uploading location14:52
kairatand make them trully external14:52
mfedosinthey won't have copy-from and custom-locations14:52
Jokke_hemanthm: that's why I'd like to see the spec there so we have at least some of the multiple locations needs documented when we try to fix the issues14:52
mfedosinbut what to do with Heat?14:52
Jokke_mfedosin: send them some comforting pictures of kittens14:52
nikhilmfedosin: we are getting to this point when app-catalog is being given more importance than the standards def-core is trying to set14:52
rosmaitaok, so part of this new spec will be to write the spec that does not exist for multiple image locations?14:53
nikhilmfedosin: I really want to avoid getting to a situation where we need to involve TC for this conversation14:53
mfedosinHeat can't work without setting custom locations14:53
rosmaitawhich i would like, because i have never completely understood them14:53
nikhilso either these teams need to work "with" glance or we go to TC14:53
kairatHeat can de-precate properties AFAIK14:53
rosmaitaJokke_: you mean comforting pictures of chipmunks14:53
kairatSo it is not a problem to ask them to deprecate location attrs14:53
hemanthmrosmaita: I think just explain the need for removing the strategy restriction?14:54
*** vhoward has joined #openstack-meeting-414:54
Jokke_rosmaita: I'd rather say that this spec might end up depending the multiple locations refactoring, but this spec would definitely provide context for that ... bit of a chicken and egg situation really14:54
kairatthe problem is what to do with locations=))14:54
nikhilat this point we've multiple conversations streams in this meeting14:54
Jokke_rosmaita: them as well ... and chipmunks beating kittens14:54
nikhilso...14:54
nikhil#topic open discussion14:54
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:54
kairatrosmaita, what about https://review.openstack.org/#/c/273196/14:54
rosmaitaso does fei long (who is not here) get the action item for the locations spec?14:55
*** shaohe_feng has quit IRC14:55
mfedosinJokke_: we have to prepare a collection of kitten pictures we will send to users :)14:55
kairatWDYT, can we go with the patch and update the rests after that14:55
*** Swami has joined #openstack-meeting-414:55
*** Swami_ has joined #openstack-meeting-414:55
*** marst has joined #openstack-meeting-414:55
*** shaohe_feng has joined #openstack-meeting-414:55
Jokke_mfedosin: google can help14:55
rosmaitakairat: good question14:55
kairatI think our tests are quite stable14:56
kairatso we can rely on them14:56
rosmaitai haven't run the code coverage14:56
rosmaitaare all the changes covered?14:56
kairatI hope so, additionally, we have reviewers14:57
*** emagana has joined #openstack-meeting-414:57
nikhilcroelandt: you want more update on your topic proposed?14:57
rosmaitamy point isn't just about this particular patch, i think we (glance) should have a policy about making these type of changes14:57
kairatwhy don't we rely on reviewers here?14:57
croelandtnikhil: yep14:58
kairatit is possible to make an error in any patch IMO=)14:58
nikhilrosmaita: fwiw, I am with the proposal there14:58
croelandtWe're currently not making much progress on the image import refactorign14:58
nikhilI would use the words carefully14:58
croelandtflaper87, Jokke_ and I were wondering if we could release an MVP14:58
rosmaitakairat: sure, but these are patches where there are a bunch of copy-and-paste changes, it is really easy to miss something14:58
croelandtand if so, what exactly this MVP could be14:58
nikhilI think it was decided at the summit14:59
*** matt-borland has joined #openstack-meeting-414:59
croelandtyeah, but things seem to have changed a bit since then14:59
nikhilI can arrange a virtual hangout next thursday for us to discuss this14:59
*** numans has quit IRC14:59
*** lei-zh has joined #openstack-meeting-414:59
*** TravT has joined #openstack-meeting-414:59
nikhil(btw, we're out of time)14:59
nikhillet's carry over to #openstack-glance14:59
rosmaita+1 for virtual hangout on image-import14:59
croelandtnikhil: sure14:59
nikhil#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Jul 28 15:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
hemanthmthanks all15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-07-28-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-07-28-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-07-28-14.00.log.html15:00
kairatrosmaita, yep, it is but from what I see OS rely on reviewers15:00
nikhilTravT: floor is yours15:00
nikhil:)15:00
matt-borlando/15:00
kairatthanks all15:00
TravTthx15:00
*** bunting has left #openstack-meeting-415:00
*** croelandt has left #openstack-meeting-415:00
*** janzian has joined #openstack-meeting-415:00
TravT#startmeeting openstack search15:00
*** yingjun has joined #openstack-meeting-415:00
*** sskripnick has left #openstack-meeting-415:00
openstackMeeting started Thu Jul 28 15:00:39 2016 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
matt-borlando/15:00
*** janzian has left #openstack-meeting-415:00
TravTo/15:01
*** sjmc7 has joined #openstack-meeting-415:01
*** kairat has left #openstack-meeting-415:01
yingjuno/15:01
lei-zho/15:01
rosmaitao/15:01
*** Swami__ has joined #openstack-meeting-415:01
*** hvprash_ has joined #openstack-meeting-415:01
TravTgive it one more min15:02
sjmc7morning15:02
*** RickA-HP has joined #openstack-meeting-415:02
RickA-HPo/15:02
TravTOkay15:02
TravTnot too long of an agenda today15:02
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:03
*** iyamahat has joined #openstack-meeting-415:03
TravT#topic mascot15:03
*** openstack changes topic to "mascot (Meeting topic: openstack search)"15:03
TravTI tallied all of the etherpad voting15:03
TravTand submitted the firefly15:04
rosmaitahopefully the mooning firefly?15:04
RickA-HPLet the t-shirts and stickers begin!15:04
TravTrosmaita: that much is out of our hands. :)15:04
*** hvprash has quit IRC15:05
*** Swami has quit IRC15:05
rosmaitai was surprised by all the negative votes on the anglerfish ... i guess trying to eat Nemo has given them all a bad name15:05
*** shaohe_feng has quit IRC15:05
sjmc7:)15:05
TravTi saw that anglerfish also made the list of suggestion for infra voting15:05
TravTbut didn't win15:06
*** yamamoto has joined #openstack-meeting-415:06
rosmaitanot a popular fish15:06
*** shaohe_feng has joined #openstack-meeting-415:06
TravThere is what the foundation marketing lady said15:06
TravTI think a firefly is an awesome idea, and I’m speaking with the design team about ensuring it will look great. I also like the concept that fireflies are pervasive and flexible, which seems to extend on a searchlight. More to come!15:06
TravTi guess i should have asked her if she liked that they mooned people15:06
*** vikasc has joined #openstack-meeting-415:07
*** piet has joined #openstack-meeting-415:07
rosmaitai just like the thumbs-up over the shoulder look on that image i found15:07
TravTok15:07
TravTyeah, maybe i'll forward it along to her15:07
rosmaitabut, i must admit, the searchlight mascot is not just for my amusement15:07
*** Swami has joined #openstack-meeting-415:08
TravTwell, i'm not really sure what the mascot is for if not our amusement15:08
sjmc7yes, it is a bit strnage15:08
rosmaitano more midcycles, mascots instead15:08
TravTlet's take projects of a type15:08
TravTgive most of them an obscure name15:09
TravTand now add an unrelated mascot15:09
TravTo?15:09
*** DrifterZA has joined #openstack-meeting-415:09
rosmaitafrom the obscure name standpoint, searchlight is the most transparent15:09
TravTyeah, i know15:09
rosmaitaprobably the best-named project in openstack15:09
*** armax has joined #openstack-meeting-415:09
TravTbut they didn't like using a searchlight for our mascot15:09
*** dshakhray has quit IRC15:10
rosmaitait would embarass the other projects15:10
TravT"hey i know what that is!"15:10
sjmc7an all angler fish lineup would’ve been fun15:10
TravT"no fair"15:10
*** aavraham has left #openstack-meeting-415:10
*** yamamoto has quit IRC15:10
*** emagana has quit IRC15:10
rosmaitathe glance mascot is going to be a chipmunk with its mouth full of nuts15:10
rosmaita(i have no follow-up comment to that)15:11
TravTummm15:11
TravTis that really it?15:11
*** Swami__ has quit IRC15:11
rosmaitayes, and specific instructions to the artist about the mouth full of nuts15:11
rosmaitawe will probably get into a dispute with disney15:12
TravTthis is why people around me wonder why i randomly laugh15:12
rosmaitabut they use openstack, don't they?15:12
TravTwell, given some people are giving up sleep for this, we should probably move on15:13
TravT#topic rick aulino for core15:13
*** openstack changes topic to "rick aulino for core (Meeting topic: openstack search)"15:13
TravTi sent out a message to the ML.15:13
TravTif you can't stand rick, go out there and -1 him15:14
sjmc7:)15:14
RickA-HP:)15:14
RickA-HPAs a core do I get my own mascot?15:14
TravTotherwise, i'll look to add him to the core list by monday morning15:14
rosmaitaRickA-HP: sure, but it must be an anglerfish15:15
RickA-HP:)15:15
*** shaohe_feng has quit IRC15:15
TravTas a core, you get the joy of being able to be blamed for more things15:15
*** Liuqing has quit IRC15:16
*** shaohe_feng has joined #openstack-meeting-415:16
lei-zhnuclear button?15:16
*** Liuqing has joined #openstack-meeting-415:16
TravTthankfully on this project there should be too much ire15:16
TravTshould -> shouldn't15:17
TravTokay, moving on15:17
*** emagana has joined #openstack-meeting-415:17
TravT#topic Strategy for Nova specs for Ocata (rosmaita)15:17
*** openstack changes topic to "Strategy for Nova specs for Ocata (rosmaita) (Meeting topic: openstack search)"15:17
*** bpokorny has joined #openstack-meeting-415:18
rosmaitai spoke with john garbutt (johnthetubaguy) former nova ptl about some of our specs that didnt' get newton love in nova15:18
rosmaitaasked him how we can push them along more effieciently15:18
rosmaitaso, the good news is that he says there is much interest in searchlight for nova cells v215:19
rosmaitaso searchlight will be a hot topic15:19
rosmaitabut his other advice is more general15:19
rosmaitamake sure the topic of the spec is raised in nova meetings, at the midcycle, summit, etc15:20
rosmaitaalso, there are nova subteams15:20
rosmaitalike for the notifications15:20
rosmaitaso for those, you talk directly to the subteam person15:20
sjmc7yeah, we did, and we went to that subteam’s meetings15:20
TravTi do feel somewhat to blame for some of this. i started going to some of their meetings after the summit, but stopped attending regularly because of so many activities.15:21
sjmc7well, also we didn’t have much influence with it15:21
sjmc7there was already a decided path for the most part15:21
TravTi'll say that i also felt like it became clear a few weeks into it that they were only going to the base versioned notifications this release15:21
TravTwith no extra data15:21
rosmaitasjmc7: that is the problem, we need a nova core to champion searchlight needs15:21
RickA-HPWhen/how does Nova prioritize work for Ocata? Can we participate/influence there?15:22
*** pcaruana has quit IRC15:22
rosmaitathey are starting now15:22
rosmaitabelieve it or not15:22
RickA-HPI believe it!15:22
rosmaitaso we probably need to resubmit the newton specs for ocata, and begin pushing them again15:23
TravTyingjun, do you have links handy?15:23
TravTthe thing is, is that we had specs for adding a couple15:24
rosmaitahttps://review.openstack.org/#/c/321336/15:24
TravTbut we didn't actually submit one asking for all the data, i think15:24
TravTon instances15:24
yingjunthanks rosmaita, and this https://review.openstack.org/34571415:24
TravTwe really should submit something on that15:25
*** shaohe_feng has quit IRC15:25
yingjunthe hypervisor one have a -2 from Matt, not sure when will it be removed15:26
*** shaohe_feng has joined #openstack-meeting-415:26
TravTthe code right?15:27
TravTnot the spec15:27
yingjunyes15:27
TravTthey'll usually remove that after the rc 1 release tag and branch are created, i think15:27
*** zhurong has quit IRC15:27
*** uxdanielle has joined #openstack-meeting-415:28
yingjunokay15:29
TravTbrian thanks for the heads up...15:29
TravTour nova lead messaged me last week about having some things to talk to me about15:29
TravTbut i was out15:30
TravTi'll follow up with him today15:30
rosmaitawell, soon as they start needing us, we'll get better traction15:30
TravTdefinitely15:30
* rosmaita wonders if it is inappropriate to ask TravT for a health update15:31
TravTsure...15:31
TravTi'm doing better.15:31
TravTstill spending full day on couch with leg elevated.15:31
TravTbut am nearly off the worst of the pain meds15:32
rosmaitawow, well best wishes15:32
TravTmaybe by next week it'll be just the over the counter stuff15:32
TravTso, i'll reach out to our nova lead15:33
TravTand at least one of us should go to some nova meetings next week15:33
TravTi'll try.15:33
*** emagana has quit IRC15:34
TravTbut maybe i can twist sjmc7's arm to also attend15:34
sjmc7i can go15:34
TravTthanks.15:34
TravTrosmaita thanks for the heads up15:35
*** ddieterly is now known as ddieterly[away]15:35
*** liwei has quit IRC15:35
sjmc7the flipside of this is how much we should get involved in projects we have dependencies on15:35
*** vikasc has quit IRC15:35
*** emagana has joined #openstack-meeting-415:35
sjmc7because it’s much easier to get a patch merged than it is to have someone else do it (obv aside from large-scale changes like versioned notifications)15:35
*** shaohe_feng has quit IRC15:36
rosmaitasjmc7: +115:36
TravTyes, we've not had much luck on the patches over in neutron and cinder15:36
sjmc7the obvious problem is that the active development team on SL is already very small15:36
TravTwhere it is somebody random15:36
sjmc7but now we’re at a point were most of the foundations are laid, maybe that’s something to pursue15:36
rosmaitai am trying to get some osic interest in searchlight, the nova interest associated with cells v2 will help that15:37
TravT+1.  Thankful that yingjun has been active on the nova front15:37
rosmaitathough, i don't know that osic "interest" will translate into dev-power15:37
*** Swami__ has joined #openstack-meeting-415:37
sjmc7maybe just more awareness on its own would be useful15:37
*** Swami__ has quit IRC15:38
*** shaohe_feng has joined #openstack-meeting-415:38
*** Swami__ has joined #openstack-meeting-415:38
TravTanything more on this topic?15:39
rosmaitanot from me15:39
*** gibi has quit IRC15:39
sjmc7no. i guess we should prioritize what we need from other projects15:39
sjmc7and focus more time working with them (and i think that’ll mostly be nova)15:39
*** ddieterly[away] is now known as ddieterly15:40
*** Swami has quit IRC15:40
yingjunand by the way, i proposed a bp on kolla to support sl15:40
*** Swami_ has quit IRC15:40
TravT#topic open discussion15:41
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:41
TravTyingjun that's great! do you have a link?15:41
RickA-HPFYI, the requirements team has approved the update of the Elasticsearch python client. The ES client will now be 2.X based.15:41
yingjunhttps://blueprints.launchpad.net/kolla/+spec/searchlight15:41
TravTare you thinking of doing that work or did you just propose it?15:41
yingjunwhat’s currently missing is that we don’t have debian/rpm for sl15:42
yingjunme or someone from my team will do that:)15:42
*** gibi has joined #openstack-meeting-415:43
yingjunwe have to install it from source for now15:43
TravTdo any other kolla projects do it from source?15:44
yingjunthey support both binary and source by default for other projects15:44
TravTok, cool15:45
TravTshould be a fun project to do that. :)15:46
*** shaohe_feng has quit IRC15:46
TravTany other items of interest?15:47
*** shaohe_feng has joined #openstack-meeting-415:47
*** unicell1 has joined #openstack-meeting-415:47
yingjunno, nothing else from me15:47
TravTokay. thanks everybody!15:48
RickA-HPBye.15:48
rosmaitahasta la vista15:48
TravT#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:48
openstackMeeting ended Thu Jul 28 15:48:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-07-28-15.00.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-07-28-15.00.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-07-28-15.00.log.html15:48
*** RickA-HP has quit IRC15:48
*** yingjun has left #openstack-meeting-415:48
*** piet has quit IRC15:48
*** lei-zh has left #openstack-meeting-415:48
*** mfedosin has quit IRC15:48
*** woodster_ has quit IRC15:49
*** unicell has quit IRC15:50
*** Liuqing has quit IRC15:50
*** emagana has quit IRC15:51
*** mfedosin has joined #openstack-meeting-415:52
*** emagana has joined #openstack-meeting-415:52
*** stevelle has joined #openstack-meeting-415:54
*** messy has joined #openstack-meeting-415:56
*** duvarenkov has quit IRC15:56
*** shaohe_feng has quit IRC15:56
*** shaohe_feng has joined #openstack-meeting-415:56
*** anilvenkata has joined #openstack-meeting-415:57
*** automagically has joined #openstack-meeting-415:57
*** michaelgugino has joined #openstack-meeting-415:57
michaelguginohere15:57
*** asettle has joined #openstack-meeting-415:58
evrardjpmichaelgugino: starting in two minutes :D15:58
*** eil397 has joined #openstack-meeting-415:58
*** matt-borland has left #openstack-meeting-415:58
*** duvarenkov has joined #openstack-meeting-415:58
*** prometheanfire has joined #openstack-meeting-415:59
*** uxdanielle has quit IRC15:59
*** janki has joined #openstack-meeting-415:59
mhayden#startmeeting OpenStack-Ansible16:00
openstackMeeting started Thu Jul 28 16:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is mhayden. 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
mhayden#topic Roll Call16:00
evrardjphello16:00
*** openstack changes topic to "Roll Call (Meeting topic: OpenStack-Ansible)"16:00
*** sjmc7 has left #openstack-meeting-416:00
eil397o/16:00
evrardjpo?16:00
DrifterZAhi16:00
stevelleo/16:00
jankio/16:00
DrifterZAo/16:00
michaelguginohere16:00
*** Swami__ has quit IRC16:00
* mhayden ( ͡° ͜ʖ ͡°)16:00
jankiHI, I am Janki. This is my first meeting here.16:00
automagicallyo/16:00
mhaydenwelcome, janki!16:00
odyssey4meo/16:00
jankimhayden: thank you16:01
*** eil397_ has joined #openstack-meeting-416:01
adrezneco/16:01
jmccroryo/16:01
eil397_welcome, janki !16:01
* mhayden gives d34dh0r53 a nudge16:02
andymccro/16:02
*** alextricity25 has joined #openstack-meeting-416:02
alextricity25o/16:02
evrardjpwelcome janki16:02
asettleo/16:03
asettleyerp16:03
jankieil397_: evrardjp: thanks for the warm welcome :)16:03
mhaydenlet's roll!16:03
mhayden#topic Action items16:03
*** openstack changes topic to "Action items (Meeting topic: OpenStack-Ansible)"16:03
mhaydenfirst up was for automagically to update the xenial status etherpad16:03
automagicallyIts been done16:03
mhaydenwoot16:03
mhaydenthe other was for me to test xenial in the lab16:04
mhaydeni ran into some failures there that i haven't been able to visit, but i might have gotten dinged by one of those gate blocker bugs :(16:04
odyssey4methanks, I need to run through the CI jobs and shift more from non-voting to voting16:04
mhaydeni'll do my best to revisit that tomorrow16:04
prometheanfireo/16:04
mhayden#action mhayden to continue testing xenial in the lab16:04
mhaydenodyssey4me: thanks for that!16:04
mhaydenthat's it for action items16:05
mhayden#topic OSA Mascot16:05
*** openstack changes topic to "OSA Mascot (Meeting topic: OpenStack-Ansible)"16:05
cloudnullo/16:05
d34dh0r53o/16:05
* mhayden is still sad that d34dh0r53 can't be our mascot, but we have other options :)16:05
odyssey4merighto16:05
odyssey4meso I sent through the list to the foundation16:05
odyssey4methey've fed back that another team has opted for a bee so the OSA bug would likely not be the best choice, and they're happy with the Cape Buffalo16:06
odyssey4methere are no conflicts there16:06
odyssey4meis everyone happy to go ahead with that?16:06
cloudnull+116:06
stevelle+116:06
*** bcafarel has joined #openstack-meeting-416:06
DrifterZA+116:06
mhaydenhttps://en.wikipedia.org/wiki/Buffalo_buffalo_Buffalo_buffalo_buffalo_buffalo_Buffalo_buffalo16:06
odyssey4meapparently they'll be dishing out stickers at the summit :)16:06
d34dh0r53+0.516:06
mhayden+1 here16:06
eil397_+116:06
*** shaohe_feng has quit IRC16:06
odyssey4melol, ok awesome I'll let them know we're all in16:06
automagically+116:07
evrardjp+116:07
*** david-lyle has joined #openstack-meeting-416:07
mhaydenat least we don't have to bison more time to decide16:07
jmccrory+116:07
*** shaohe_feng has joined #openstack-meeting-416:07
odyssey4me:p16:07
d34dh0r53uggh16:07
* odyssey4me hands the mic back to mhayden 16:07
evrardjpI vote for mhayden's sentence to be our motto16:07
mhaydenhaha16:07
mhaydeni'll take the mic back before odyssey4me realizes that's a bad idea :)16:08
palendaeOSA: When you need to bison time16:08
mhayden#topic Applying for stable:follows-policy governance tag16:08
*** openstack changes topic to "Applying for stable:follows-policy governance tag (Meeting topic: OpenStack-Ansible)"16:08
mhayden#link https://governance.openstack.org/reference/tags/stable_follows-policy.html16:08
odyssey4mealright, I guess that's me again :p16:08
* mhayden assumes this is odyssey4me16:08
odyssey4meWe have the option of applying to apply this governance tag to the project's deliverables.16:08
odyssey4meThis would be a signal to the world that we take our stable branches seriously.16:09
evrardjpit doesn't mean they have to16:09
odyssey4meI honestly assumed that this was a requirement once bing an official project, but apparently not.16:09
spotzo/16:09
stevellehistorically we have been rather free with backports, and those habits can be hard to break. Are we ready to take this step?16:09
evrardjpoh interesting odyssey4me16:09
odyssey4meSo I'd like to suggest that we apply for the tag, and that we stick to the rules far better going forward.16:10
mhayden#link http://docs.openstack.org/project-team-guide/stable-branches.html16:10
odyssey4mestevelle agreed, this will take more discipline16:10
mhayden^^ rules16:10
evrardjpif it's not a requirement, why would we want to apply for the tag? It seems more restrictive than its benefits16:10
automagicallyLooks like we need a stable branch maint team...16:10
stevelleAre you advocating a separate stable maint core list?16:10
odyssey4mebut we have been pretty good about applying these rules during this cycle16:10
stevelleI know some projects use separate cores for stable16:10
evrardjpWe could have the discipline without being officially flagged as this16:10
DrifterZAbrb16:10
odyssey4mewe can, but it's not a requirement - the same core team can do stable reviews16:10
mhaydenwhat would the negative outcome be if we chose not to apply?16:11
odyssey4meit affects the view of our maturity as a project16:11
palendaeodyssey4me, How would that affect upgrade work, given that that's been happening post-release?16:11
evrardjpoh in the project navigator?16:11
stevelleTC tags: gotta catch em all.16:11
*** emagana has quit IRC16:11
mhaydenah, palendae brings up a good question16:11
automagicallyHow do we test backward compatibility of backports? In other words, does adopting this suggest that we should have some mechanism for ensuring such backware compatibility16:11
odyssey4mealso, not having this tag does mean that we get people trying to shove features into stable branches16:11
palendaee.g. I don't think anyone is working on Mitaka -> Newton right now16:11
odyssey4meit becomes very hard to justify why not16:11
automagicallyGiven the mid-cycle is not far off, should we discuss further then, or is there a good reason to push for adoption earlier than that?16:12
*** GB21 has joined #openstack-meeting-416:12
odyssey4methe cycle planning which I've been trying very hard to get us to stick to has all been around being able to discipline our development into the cycle properly16:12
odyssey4mepart of that is for us to ensure that we do the upgrade work *within* the cycle16:12
stevelleone implication of this tag would be that we have to be careful when bumping SHAs on stable that we only bump SHAs on projects which also have that tag, no?16:13
odyssey4meie by the time we release Newton, we should have a working upgrade16:13
palendaeodyssey4me, I don't disagree with that approach, just pointing out we've not been able to hit that historically16:13
automagicallystevelle: Great point16:13
automagicallyWe could always move upgrade plays into their own repo that doesn’t carry the tag...16:13
odyssey4mestevelle hmm, not sure about that - I could discuss that and see how that works16:13
palendaeautomagically, I'm -1 to that16:14
palendaeRepo-itis is bad16:14
mhayden#info If we apply for stable tag, what about upgrade playbooks that need to be adjusted after release?16:14
*** emagana has joined #openstack-meeting-416:14
odyssey4meautomagically I think that's a terrible idea. Upgrades are essential to the success of the project's deliverables.16:14
palendae^16:14
evrardjpagreed with palendae and odyssey4me16:14
odyssey4mebear in mind that this doesn't prevent us fixing bugs once a stable branch is cut16:14
mhayden#info If we apply for stable tag, are we limited on the projects we can do SHA bumps on in stable releases? (Do those need to have stable tag, too?)16:14
palendaeIMO, upgrades are more important than greenfield install16:14
palendaeGreenfields won't nuke existing clouds16:15
odyssey4meit just means we don't backport large features16:15
odyssey4mewhich we have been good about in this cycle16:15
automagicallyI don’t disagree, I just find it hard to believe that we’ll have them done at the same time as the release16:15
odyssey4mewe have already had our releases inspected for the whole of the cycle, and have had no negative feedback\16:15
palendaeautomagically, yeah, I share the skepticism. I would definitely prefer it that way16:15
odyssey4methe only times we had a comeback, we had to bumpt the minor tag16:15
odyssey4me(which is why that happened a few times)16:15
automagicallyI’m not opposed to adoption so long as we understand what we are signing up for and legitimately believe we can hit those targets16:15
evrardjpwe need a better CI to automatically test upgrades between versions, only that will force us to care about upgrades16:15
michaelgugino-116:16
stevelleI don't trust the lack of negative feedback to indicate we haven't let stuff slip by16:16
evrardjpnot better but more extensive16:16
palendaeI'm not against adding that tag. I do think shoehorning in big features needs to stop...but the tag isn't strictly necessary to stop that, either16:16
michaelguginoI like the ability to backport features.  This project is such a moving target, it's hard to be able to implement features as upstream projects commit them.16:16
palendaeThe upgrade problem is my biggest concern right now16:16
*** uxdanielle has joined #openstack-meeting-416:16
mhaydenit sounds like we have good questions/opinions here -- should we table that for the mid-cycle and have a more thorough discussion?16:16
odyssey4meevrardjp not entirely true, but yes if we had people who would process the messages in the QA mailing list then periodic upgrade checks would have value16:16
*** shaohe_feng has quit IRC16:17
jmccroryi think a lot of the standard upgrade playbooks are there, just needs some reorganization and any release->release specifics, which are hard to know until the next release stablize16:17
jmccrorys16:17
palendaemhayden, I'd agree that midcycle would be nice16:17
odyssey4meright now our stakeholders are implementing their own upgrade testing and feeding back - that's a fairly good start16:17
automagicallymhayden: ++ on midcycle discusssion16:17
stevellemhayden: I think this should go to the list before midcycle to solicit more feedback16:17
palendaejmccrory, Yeah, that's also true16:17
* mhayden is working to figure out if we can do VC at the midcycle -- fingers crossed16:17
palendaeAgreed with stevelle16:17
mhaydenstevelle: not a bad idea16:17
automagicallystevelle: also a good point16:17
palendaePre-meetup homework16:17
mhaydenreminds me of the "why not both?" meme16:17
palendaeI need to do some of that myself16:17
stevelleindeed16:17
*** shaohe_feng has joined #openstack-meeting-416:17
odyssey4memhayden please don't try and accommodate VC... we have tried and failed many times16:17
mhayden#agreed Send something to the ML about stable:follows-policy tag, follow up with discussion at the mid-cycle16:18
*** v1k0d3n has joined #openstack-meeting-416:18
mhaydenodyssey4me: okay16:18
odyssey4memhayden VC is a distraction at the mid cycle and generally ends up being frustrating and not contributing16:18
mhaydenwho will mail the list?16:18
odyssey4memhayden me16:18
mhayden#action odyssey4me to send something to the ML about stable:follows-policy tag16:18
evrardjpit's definitely a deployer opinion to give16:19
mhaydenodyssey4me: can you update the etherpad too so it's on the agenda?16:19
michaelguginowhat is this VC business?16:19
mhayden(for the midcycle)16:19
mhaydenmichaelgugino: videoconference16:19
michaelguginoah16:19
odyssey4memhayden yep, doing it now16:19
*** baoli_ has quit IRC16:19
mhaydeni'm sure we can fire up etherpads and link those pads in the channel for remote folks to jump in16:19
michaelguginowe did VC with watcher, it worked out okay, but it was a much smaller group.16:19
*** liwei has joined #openstack-meeting-416:19
palendaeBiggest hurdle last time was timezones16:20
michaelguginoI think there are too many people going to the mid cycle for VC to work16:20
palendaeI intterupted discussions when joining16:20
stevelle== michaelgugino16:20
mhaydenokay, are we good on this topic for now?16:20
automagically+116:20
*** woodster_ has joined #openstack-meeting-416:20
automagicallynext topic16:20
odyssey4meyep16:20
mhaydenthanks for bringing it up, odyssey4me :)16:20
mhayden#topic wsgi vs uwsgi and Apache vs nginx role consistency16:20
*** openstack changes topic to "wsgi vs uwsgi and Apache vs nginx role consistency (Meeting topic: OpenStack-Ansible)"16:20
mhaydenstevelle / cloudnull / odyssey4me have the mic16:21
*** ddieterly is now known as ddieterly[away]16:21
* odyssey4me points at stevelle :)16:21
michaelguginoI thought we were tabling this until the midcycle.16:21
* cloudnull wants nginx+uwsgi all the things16:21
stevelleI think we covered this last week16:21
automagicallyYeah, don’t think we have anything new on this topic16:21
mhaydenah, it was still in the agenda16:21
odyssey4meyep, are we stuck or anything?16:21
cloudnullfederation is an issue.16:21
cloudnulli think16:21
mhayden#agreed Talk more on wsgi/uwsgi/nginx/apache at the mid-cycle16:22
stevelleIt needs time, and I thought we agreed there wouldn't be enough before M316:22
automagically^ That16:22
*** mbound has quit IRC16:22
mhaydencool beans, we can move on16:22
mhayden#topic Mid-cycle planning16:22
*** openstack changes topic to "Mid-cycle planning (Meeting topic: OpenStack-Ansible)"16:22
mhaydeni'll be sending the list of names from the etherpad to the physical security team here to make badges and things16:23
*** mbound has joined #openstack-meeting-416:23
mhaydenso be sure to get your name on there before next week16:23
mhaydenand i'll be sure to get some instructions out about where to go, where to park, etc16:23
mhaydenyou'll need a Racker to escort you up to the room, we can tackle that too16:23
palendaemhayden, Do we have actual times for stuff yet? I was going to invite the Craton team for the inventory discussions16:24
mhaydenpalendae: mainly just an outline16:24
mhayden#link https://etherpad.openstack.org/p/osa-midcycle-newton16:24
palendaeOk16:24
odyssey4mepalendae for things that need a set time (like using a VC for a discussion) we can specifically set a time on day 2 I think16:24
mhayden#action mhayden to email security folks with the list and email extra venue instructions to attendees16:24
jankimhayden: possible to have meeting online. I am in India16:24
mhaydenjanki: i'm hearing that it didn't work so well in the past /16:25
palendaeodyssey4me, Ok. I notice that Day 1's list is well over 8 hours :(16:25
odyssey4meI'd suggest that we have a more strict schedule for day 2 - day 1 is for us to catch up and organise the rest of the week16:25
odyssey4mebut we can set times for day 216:25
automagically#link http://dolphm.com/retrospective-on-openstack-midcycles/16:25
*** LouisF has joined #openstack-meeting-416:25
automagicallySuggest reading that ^ for those of you attending16:25
*** ntpttr__ has joined #openstack-meeting-416:25
odyssey4meif we do any VC stuff it must be no longer than an hour and have a well organised agenda and set of outcomes16:25
odyssey4meautomagically ++16:25
mhaydenautomagically: that's a good one16:26
jankimhayden: :(16:26
palendaeJust looking at the list of topics, day 2 will be at least half discussion if we hit everyting16:26
*** ddieterly[away] is now known as ddieterly16:26
mhaydenjanki: at a minimum, we will have some etherpads and link to them in #openstack-ansible16:26
mhaydenand we'll probably have some recaps written up16:26
odyssey4mejanki trying to include other time zones is even worse and far more disruptive - this is why the mid cycle is in-person to ensure that we're all in the same TZ16:26
*** shaohe_feng has quit IRC16:27
odyssey4methe focal point of the mid cycle is to assess where we're at in terms of this cycle's deliverables, to identify anything that's at risk of not making it, and to address that risk16:27
*** shaohe_feng has joined #openstack-meeting-416:27
mhaydenanything else on the mid-cycle for now?16:28
jankimhayden: odyssey4me: understand. Will keep tracking etherpads :)16:28
odyssey4meanything that's idea orientated or not specifically on this cycle's list can be discussed briefly and needs to take limited time and should only be for the purpose of seeding discussion to be had at the next summit16:28
mhaydennext topic?16:29
*** emagana has quit IRC16:29
automagicallymhayden: ++16:29
odyssey4me+!16:29
*** emagana has joined #openstack-meeting-416:29
odyssey4me:116:29
mhaydenhah16:29
odyssey4mebah16:29
mhayden+3.1416:29
mhayden#topic Release Planning & Decisions16:29
*** openstack changes topic to "Release Planning & Decisions (Meeting topic: OpenStack-Ansible)"16:29
evrardjp+$116:29
mhaydenlooks like 13.3.0 and 12.2.0 are on deck?16:30
evrardjp$!16:30
odyssey4meyeah, I've had feedback from RPC that the recent changes have broken some of the requirements16:30
odyssey4meor more accurately, now that the requirements are being properly calculated, it's broken the builds16:30
automagicallyRuh roh16:31
evrardjp:p16:31
odyssey4mewhat that means is that I may have to revert a patch or two16:31
evrardjpif we do things the right way now, why would you want to revert?16:31
odyssey4memore testing is being done right now16:31
automagicallyIs it not possible for RPC to adapt16:31
odyssey4meyeah, we worked on that today but it seems that our requirements processing isn't working the way it's supposed to either16:31
automagicallyAh, so a melange of bugs16:32
odyssey4meso we fixed one thing, but it's exposed another issue16:32
automagicallyyaks as far as the eye can see ;)16:32
odyssey4meyeah - so we're testing a bit more16:32
odyssey4meI'll hold back the release requests until tomorrow.16:32
michaelguginothat's why we have stable releases.  I think if more things are broken, we commit forward, not backward16:32
odyssey4meit's likely that RPC will simply not do a SHA bump16:33
odyssey4meOSA's build is right, but we need to also take care of our downstream consumers16:33
automagicallyNo disagreement there16:33
michaelguginoif you broke a stable branch, sure.  But we still need to be able to implement features during a cycle16:33
automagicallySo, we should expect to see some bugs show up in Launchpad with the result of the RPC testing?16:33
*** coolsvap is now known as coolsvap_16:34
odyssey4meautomagically maybe, not sure right now - we're still at the stage of confirming that there is a bug16:35
automagicallyk16:35
odyssey4meanyway16:35
odyssey4meon another note - I did the N2 rleease request16:35
odyssey4meit does work16:35
mhaydenhooray!16:35
*** liwei has quit IRC16:35
odyssey4meI got the sweet spot between all the broken shenanigans. :)16:35
eil397_: )16:36
odyssey4methe last few weeks have been a bit rough and really exposed our need for cross-repo testing, which I'm working on.16:36
eil397_integration testing it is infinite thing16:37
automagicallyHappy to help out on getting more/better testing16:37
eil397_recursive : - )16:37
*** shaohe_feng has quit IRC16:37
mhaydenalrighty, open discussion time?16:37
evrardjpfine for me16:37
mhayden#topic Open Discussion16:37
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack-Ansible)"16:37
*** v1k0d3n_ has joined #openstack-meeting-416:37
eil397_do we have etherpad to track centos support ?  I would like to work in it16:38
michaelguginoI propose we add a requirements.yml to each role repository, so each role is a little more self-contained16:38
*** shaohe_feng has joined #openstack-meeting-416:38
odyssey4meI'd appreciate some eyes on https://review.openstack.org/347930 - it's python, and it's cloudnull... so I really don't understand what it's doing. :)16:38
odyssey4meI can vouch only for the outcome.16:38
michaelguginoI have written a script to do the work for us, so we can run the script each time we tag the commits on the osa repo16:38
mhaydeneil397_: not sure on that one16:38
michaelguginohttps://gist.github.com/michaelgugino/fc3fe3d635396f0c15df401fb087c0c416:38
*** cbits has quit IRC16:38
cloudnull^ awesome!16:39
*** ninag has joined #openstack-meeting-416:39
michaelguginothis will allow people that want to utilize just one of our roles an easy way to install the dependencies16:39
odyssey4memichaelgugino what do you hope to achieve with this?16:39
automagicallymichaelgugino: Cool16:39
odyssey4meoh I see - for the role requirements16:39
odyssey4methat's nifty and should probably go in the openstack-ansible-ops repo for now16:40
michaelguginosay someone wants to just use our swift play or something.  This lets us put those requirements in each role, based on the role's meta, and the ansible-role-requirements.yml in the osa repo16:40
odyssey4meI'd really rather not duplicate more stuff across all repositories16:40
automagicallyeil397_ You can start one modeled on https://etherpad.openstack.org/p/openstack-ansible-newton-ubuntu16-0416:40
*** severion has quit IRC16:40
*** unicell1 has quit IRC16:40
odyssey4meI haven't done the tests repo.16:40
*** v1k0d3n has quit IRC16:41
*** iyamahat has quit IRC16:41
eil397_automagically: thanks. will do16:41
odyssey4me#action odyssey4me to request the creation of the tests repository16:41
DrifterZATend to aggree with odyssey4me, ansible-ops repo seems the best way to do specific builds16:41
michaelguginocurrently, there isn't an easy way to install the requirements if you just want to use one or two roles.  You have to dig through the meta, and then check the role requirements file from osa, and manually install each requirement or build a requirements.yml yourself.16:41
*** v1k0d3n_ has quit IRC16:41
mhaydenspeaking of openstack-ansible-ops -- i could use another look at my improvements for osa-differ -> https://review.openstack.org/34486616:41
*** cbits has joined #openstack-meeting-416:41
odyssey4memichaelgugino does it resolve the requirements recursively?16:42
*** vhoward has quit IRC16:42
michaelguginono, I don't believe so16:42
*** v1k0d3n has joined #openstack-meeting-416:42
michaelguginoI could make it do that, I suppose16:43
odyssey4meit's kinda rebuilding ansible-galaxy16:43
*** ntpttr__ has quit IRC16:43
*** ninag has quit IRC16:43
evrardjpI agree odyssey4me16:43
evrardjpwe should fix our usage then16:43
odyssey4mehmm, ok I think this is best suited as a tool in the ops repo for now16:44
*** ntpttr__ has joined #openstack-meeting-416:44
odyssey4meit could perhaps be useful to have an ansible-role-requirements.yml file in each repo which contains the bits it needs16:44
michaelguginoyeah, that's why I wrote the script16:44
odyssey4methat tool could possibly used to do the initial generation16:44
jmccroryis there a plan to publish osa roles to galaxy?16:45
odyssey4meok, that should be fine16:45
evrardjpthat's if we don't care about the meta16:45
odyssey4mejmccrory yes, but it's still in discussion between infra and ansible16:45
evrardjpjmccrory's question is valid16:45
jmccroryah ok16:45
evrardjpbecause that's the limiting factor16:45
odyssey4methere are some things that can't be automated right now, which infra want to automate16:45
michaelguginoit uses the meta of each role to determine which roles from osa to include in requirements.yml16:45
automagicallyVersioning of the roles with semver will be desirable then16:45
odyssey4memichaelgugino unfortunately that is not enough, because roles depended on also depend on roles16:46
evrardjpautomagically: galaxy doesn't enforce semver versioning. it just wants tags16:46
odyssey4meright now the role requirements can largely be derived from the test requirements and the meta16:46
michaelguginoyes, but I'm using osa + meta to generate them because osa has the specific sha's we want.16:47
odyssey4mefor a role requirements file in each role we would not want SHA's16:47
michaelguginoso, you update sha's in osa, commit, then run this script, then update each role's masters16:47
odyssey4meansible will fetch the latest tag by default16:47
*** shaohe_feng has quit IRC16:47
michaelguginothat won't work for tagged releases, like mitaka, we depending on specific versions for each role16:48
odyssey4meI'm definitely not keen to create another place to manage SHA's16:48
evrardjpcould we discuss this usage on the mid-cycle? it's a use case of osa, it's interesting16:48
*** shaohe_feng has joined #openstack-meeting-416:48
automagicallyevrardjp: ++16:48
palendaeDoes it need to wait?16:49
odyssey4memichaelgugino FYI the tags are applied to all repositories simultaneously16:49
palendaeI'm concerned the mid cycle is already bulging with topics16:49
*** dasanind has quit IRC16:49
evrardjpnot that I require more topics there, but it would help understand to meet irl16:49
odyssey4mepalendae yep, we will likely have to prune the list16:49
*** dasanind has joined #openstack-meeting-416:49
*** emagana has quit IRC16:49
mhaydenevrardjp gets one point for using irl16:49
*** emagana_ has joined #openstack-meeting-416:49
palendaePoint taken, but lots of stuff we discuss on IRC could also be done IRL, yet we carry forward :)16:50
*** Swami has joined #openstack-meeting-416:50
automagicallyhaha16:50
*** LouisF_ has joined #openstack-meeting-416:50
odyssey4memichaelgugino for now I suggest putting the tool in the ops repo so that people can use it16:51
mhaydenICW to meet IRL ASAP at the HQ16:51
michaelguginook, sounds good to me16:51
odyssey4mesubmit a basic description of what it's for and how to use it16:51
michaelguginobut, it just generates requirements.yml files for each role, so not of particular use to people outside of us16:51
michaelguginook16:51
mhaydenokay, we're reaching the end of the hour -- anyhting else?16:51
*** LouisF has quit IRC16:51
mhayden...16:52
mhaydenthanks everyone! :)16:52
cloudnulleverything is awesome!16:52
cloudnull:)16:53
andymccrcloudnull: +216:53
mhayden#endmeeting16:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:53
openstackMeeting ended Thu Jul 28 16:53:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:53
eil397_: )16:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-07-28-16.00.html16:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-07-28-16.00.txt16:53
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-07-28-16.00.log.html16:53
*** automagically has left #openstack-meeting-416:53
*** prometheanfire has left #openstack-meeting-416:53
DrifterZAcheers16:53
*** DrifterZA has left #openstack-meeting-416:53
*** Bali_Bao has joined #openstack-meeting-416:53
*** LouisF_ has left #openstack-meeting-416:53
*** stevelle has left #openstack-meeting-416:53
*** eil397_ has left #openstack-meeting-416:53
*** LouisF has joined #openstack-meeting-416:54
*** asettle has quit IRC16:54
*** numans has joined #openstack-meeting-416:54
*** banix has quit IRC16:54
*** amotoki has quit IRC16:54
*** sambetts is now known as sambetts|afk16:56
*** alextricity25 has left #openstack-meeting-416:57
*** shaohe_feng has quit IRC16:58
*** doonhammer has joined #openstack-meeting-416:58
*** shaohe_feng has joined #openstack-meeting-416:58
*** iyamahat has joined #openstack-meeting-416:59
*** amotoki has joined #openstack-meeting-417:00
*** yamahata has joined #openstack-meeting-417:00
LouisF#startmeeting service_chaining17:01
openstackMeeting started Thu Jul 28 17:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: service_chaining)"17:01
openstackThe meeting name has been set to 'service_chaining'17:01
LouisFhi all17:01
pcarverhi17:01
igordcardhi17:01
*** michaelgugino has left #openstack-meeting-417:01
Bali_BaoHi17:01
bcafarelhello17:01
doonhammerhi17:01
*** ddieterly is now known as ddieterly[away]17:01
mohankumarHi17:01
yamahatahello17:02
LouisFmeeting agenda:https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting#.5BProposed.5D_Agenda_for_the_Networking-SFC_Meeting_.287.2F28.2F2016.2917:02
LouisF#topic move to Openstack Client (OSC)17:03
*** openstack changes topic to "move to Openstack Client (OSC) (Meeting topic: service_chaining)"17:03
*** david-lyle has quit IRC17:03
mohankumarLouisF , some plugin support in neutronclinet repo and in-progress https://review.openstack.org/#/c/348097/1 , we have to wait still all the supporting changes are get in , as of now the osc sfc plugin is done and able to register our clis .17:03
LouisFmohankumar: what is status?17:03
*** amotoki has quit IRC17:03
LouisFmohankumar: thanks17:04
LouisFmohankumar: what changes are you refering to?17:04
mohankumar https://review.openstack.org/#/c/348097/117:04
LouisFmohankumar: ok thanks17:05
*** ddieterly[away] is now known as ddieterly17:06
LouisF#topic Tacker driver integration17:06
*** openstack changes topic to "Tacker driver integration (Meeting topic: service_chaining)"17:06
*** emagana_ has quit IRC17:06
*** emagana has joined #openstack-meeting-417:06
LouisFlooks like stephen is not on will come back to that17:06
LouisF#topic api reference17:07
*** fsunaval has joined #openstack-meeting-417:07
*** openstack changes topic to "api reference (Meeting topic: service_chaining)"17:07
LouisFthat was merged17:07
pcarverIs publishing enabled or is that another step?17:08
LouisFpcarver: were you able to generate the html files?17:08
*** shaohe_feng has quit IRC17:08
pcarverLouisF: no, no luck17:08
LouisFpcarver: that would be  another step17:08
pcarvertox gives errors on multiple machines17:08
*** juanmafg_ has joined #openstack-meeting-417:08
*** shaohe_feng has joined #openstack-meeting-417:08
LouisFpcarver: i think you need to make chnages to tox.ini17:09
pcarvermaybe I'm missing some pre-req installation but I don't know what17:09
pcarverLouisF: do you mean the tox.ini in the repo or is there a separate local one that I need to manually setup?17:09
LouisFin the repo17:10
LouisFshould work17:10
pcarverwell I'm cloning the repo from Gerrit, so I should have what you have in the commit.17:10
*** anilvenkata has quit IRC17:11
pcarverThere must be some outside dependency that explains why you get success and I get failure. Maybe a version issue or some pre-req package missing or something17:11
*** uxdanielle has quit IRC17:11
LouisFpcarver: i will check the prcoedure i used17:12
pcarverand it's got to be something that Devstack doesn't setup either because one of the machines I tried on was a fresh install of Ubuntu 14.04.3 on which I had run stack.sh with the line in local.conf to pull in and install networking-sfc17:12
LouisFpcarver: i will email you17:12
pcarverThanks17:12
LouisF#topic port-pair group parameter17:13
*** openstack changes topic to "port-pair group parameter (Meeting topic: service_chaining)"17:13
pcarverwait, on the API docs topic17:13
LouisFpcarver: go ahead17:13
pcarverDo we know what is needed in the infra repo to enable API docs publishing or is that still an unknown?17:13
*** unicell has joined #openstack-meeting-417:14
pcarverwe need to get the output onto api.openstack.org17:14
LouisFpcarver: i am looking into that17:14
*** unicell has quit IRC17:14
pcarverI've looked too and haven't found clear instructions17:14
*** unicell has joined #openstack-meeting-417:14
LouisFthe neutron api docs are going to land in  neutron-lib17:14
pcarverThere seem to be bits and pieces, but not the full picture17:15
*** banix has joined #openstack-meeting-417:15
LouisFthere is conversion work in progress17:15
LouisFpcarver: armando will let us know when that is complete17:15
*** cloudtrainme has joined #openstack-meeting-417:16
pcarverok17:16
LouisFback to port-pair-group parameter; i done see george wang on17:16
LouisFi will contact him for progress17:17
LouisF#topic tempest tests17:17
*** openstack changes topic to "tempest tests (Meeting topic: service_chaining)"17:17
LouisFthere is a patch in review for tempest testing17:18
LouisFhttps://review.openstack.org/#/c/321870/17:18
LouisFplease review17:18
*** shaohe_feng has quit IRC17:18
*** ddieterly is now known as ddieterly[away]17:18
*** shaohe_feng has joined #openstack-meeting-417:19
mohankumarLouisF , gate job failures are because of this ?17:19
mohankumargate-tempest-dsvm-networking-sfc-nv17:19
LouisFmohankumar: right - i don't think so17:20
*** s3wong has joined #openstack-meeting-417:20
LouisFmohankumar: its another issue17:20
*** sabari has quit IRC17:20
mohankumarLouisF , ok , i ll check .. i ve failures still in this patch set changes also17:20
LouisFmohankumar: ok thanks17:21
s3wonghello... sorry, late...17:21
LouisFs3wong: hi17:21
LouisFs3wong: what is status on the tacker / networking-sfc driver?17:21
*** baoli has joined #openstack-meeting-417:22
*** emagana has quit IRC17:22
*** emagana has joined #openstack-meeting-417:22
s3wongLouisF: patches are out17:23
LouisFdo you have a link?17:23
s3wongLouisF:   https://review.openstack.org/#/c/347563/17:23
s3wongand  https://review.openstack.org/#/c/347568/17:23
s3wongthe second one (really) is WIP at this point17:24
s3wongLouisF: will put you in as reviewer also17:24
*** mfedosin has quit IRC17:24
LouisFs3wong: ok thanks17:24
*** nmadhok has joined #openstack-meeting-417:25
mohankumarLouisF, s3wong : i've an question about tacker . do we have duplicate effort by working heat and tacker in my understanding both are orchestration services to enable sfc right .17:25
mohankumars3wong: is there any difference/ advantage in tacker ?17:25
LouisFs3wong: can you set workflow to -117:25
s3wongmohankumar: Tacker has a VNFM in place17:25
s3wongmohankumar: which allows for config and monitoring driver17:26
s3wongmohankumar: also, for Tacker, we really aren't just doing SFC, we are providing an implementation of VNFFG (forwarding graph)17:26
s3wongLouisF: will do17:26
*** pmesserli has quit IRC17:26
mohankumars3wong :  okay thanks , have to read more :)17:27
s3wongLouisF: done :-)17:27
*** pmesserli has joined #openstack-meeting-417:27
s3wongmohankumar: it is really quite fasinat17:27
*** sabari has joined #openstack-meeting-417:27
LouisFmohankumar: this is useful for networking-sfc as it provides another way to test and evaluate the api17:27
s3wongfascinating what one can do on top of  networking-sfc API17:27
LouisFs3wong: thanks17:27
mohankumars3wong , LouisF: agree17:28
*** uxdanielle has joined #openstack-meeting-417:28
*** shaohe_feng has quit IRC17:28
*** david-lyle has joined #openstack-meeting-417:28
LouisF#topic sfc agent naming issue17:28
*** openstack changes topic to "sfc agent naming issue (Meeting topic: service_chaining)"17:28
LouisFhttps://review.openstack.org/33439817:29
*** shaohe_feng has joined #openstack-meeting-417:29
LouisFfsunaval: you are looking into this17:29
fsunavalI have something working. I will send out diffs tomorrow.... A rewrite is not necessary.17:29
*** cloudtrainme has quit IRC17:29
LouisFfsunaval: great17:29
fsunavalBut I have modified some core neutron files.  Will need to see what the neutron folks say about the change.17:29
LouisFfsunaval: ok thanks17:30
*** emagana has quit IRC17:30
fsunavalWill send out the diffs for internal review today and if all goes well send it out for external review tomorrow.17:30
*** emagana has joined #openstack-meeting-417:30
LouisFfsunaval: ok17:30
*** pmesserli has quit IRC17:31
*** pmesserli has joined #openstack-meeting-417:32
LouisF#topic networking-sfc / OVN driver17:32
*** openstack changes topic to "networking-sfc / OVN driver (Meeting topic: service_chaining)"17:32
LouisFthere is a patch https://review.openstack.org/33317217:32
LouisFthere were some comments from Na Zhu - not sure they all got answered?17:33
*** v1k0d3n has quit IRC17:33
LouisFis Na Zhu on?17:33
*** bryan_att has quit IRC17:33
doonhammerLouis: probably not very late in China17:34
LouisFBali_Bao: do you know if Na Zhu is ok with the latest patch?17:34
LouisFdoonhammer: ok i will email her17:34
Bali_Baonot sure..sorry17:34
LouisFanyway please review17:35
LouisFnext topic is bug scrub. before that any other topics to discuss?17:35
mohankumarLouisF,pcarver: there are patches correct minor nit(s) , fixing typos waiting for workflow approval , could you please review :)17:36
*** Swami has quit IRC17:36
LouisFmohankumar: can provide links17:36
igordcardLouisF: I've submitted an early patch for the refactoring work around bringing SFP mgmt/gen to the SFC plugin17:36
mohankumarhttps://review.openstack.org/#/c/338874/17:37
mohankumarhttps://review.openstack.org/#/c/337577/17:37
igordcard#link https://review.openstack.org/#/c/346175/17:37
LouisFall please review these17:37
*** Swami has joined #openstack-meeting-417:37
igordcardI will soon start working on the nsh patch using that one as a dependency, while still improving it17:37
igordcardthere is one thing I would like to raise here about the refactoring patch17:38
LouisFigordcard: do those changes pass the unit tests?17:38
LouisFigordcard: go ahead17:38
igordcardLouisF: no, it's still a WIP and I will address the unit tests later17:38
LouisFigordcard: ok17:38
igordcardit works though, but no unit tests yet17:38
*** shaohe_feng has quit IRC17:39
LouisFigordcard: need the unit tests also17:39
igordcardso because I have split the models that were mostly managed by the OVS driver, into abstract models managed by the plugin and specific models managed by the OVS driver, there is now more dependency in the order to the CRUD methods need to take place17:39
igordcardespeciall, when updating a port chain17:40
*** shaohe_feng has joined #openstack-meeting-417:40
LouisFigordcard: elaborate17:40
igordcardthere is no pre/post-commit-like interface with the SFC drivers, which makes it difficult to carry out the update port chain method correctly17:40
igordcardthe order for the update method should be: 1. tell OVS to undo previous chain and remove specific resources 2. remove old abstract resources 3. create new abstract resources 4. tell OVS to create new chain and generate new specific resources17:41
*** bobh has joined #openstack-meeting-417:42
mohankumarigordcard : agree17:42
LouisFigordcard: are you refering to inserting/removing a PPG in the port chain?17:43
igordcardwe can discuss this in more detail in the patch that I've submitted, just wanted to raise the issue here... as such the update method is not yet working on the patch that I submitted17:43
igordcardLouisF: for example17:43
LouisFigordcard: how is the crud order significant?17:44
igordcardLouisF: the OVS driver will not know what flows to generate until the abstract resources have been updated by the plugin... but the plugin cannot update them before telling the OVS driver to clean - or the old ones will be left dangling17:45
*** andymaier has quit IRC17:45
igordcardanother alternative is to force a full refresh in the OVS driver, but I couldn't find that functionality today.. I believe networking-sfc used to have that in the past17:45
LouisFigordcard: a port chain update operation has both the previous PPG list and new PPG list17:47
igordcardor every old resource can be hard copied and then sent to the driver so it can clean the old ones... which may entail changing the driver's interface17:47
igordcardor the update port chain can simply call delete port chain and the create port chain, there are different alternatives but I prefer to have your feedback before implementing the update-port-chain17:47
*** banix has quit IRC17:49
LouisFigordcard: the current implementation is the delete the port chain with old ppgs then create a new port chain17:49
*** shaohe_feng has quit IRC17:49
LouisFigordcard: i would have to check where that is done in the code17:49
igordcardLouisF: yes but that is done inside the driver's update method... the plugin simply delegates all logic to the driver17:49
*** shaohe_feng has joined #openstack-meeting-417:50
*** ihrachys has quit IRC17:50
igordcardbut I will investigate a bit more in regards to the ppgs diff... there's also the fact that the other flow classifiers can be given17:50
LouisFigordcard: different drivers may have differing implementations17:50
*** emagana has quit IRC17:50
*** emagana has joined #openstack-meeting-417:50
LouisFigordcard: correct, port chain update may also chnage the flow classifiers17:50
igordcardLouisF: right, but I'm attempting to abstract what should be common to all drivers (which essentially is nsp+nsi and the list of path nodes [without technical details])17:51
LouisFigordcard: agree the nsp generation should be common17:52
igordcardhere's what I'm gonna do, I'll leave some comments in my own patch so you can follow the reasoning here (instead of polluting it with python comments) and we can continue from there, sounds good?17:52
igordcardI mean, gerrit comments17:53
LouisFigordcard: ok17:53
*** cbits has quit IRC17:53
mohankumarLouisF,pcarver : Please check these patches also., (correct minor nit(s) , fixing typos)17:53
mohankumarhttps://review.openstack.org/#/c/339911/17:53
mohankumarhttps://review.openstack.org/#/c/341310/17:53
mohankumarhttps://review.openstack.org/#/c/341293/17:53
mohankumarhttps://review.openstack.org/#/c/323783/17:53
mohankumarhttps://review.openstack.org/#/c/343402/17:53
mohankumarhttps://review.openstack.org/#/c/325838/17:53
mohankumarhttps://review.openstack.org/#/c/335717/17:53
LouisFmohankumar: thanks17:53
LouisFall - please review these17:54
pcarverok17:54
*** fsunaval has quit IRC17:54
s3wongmohankumar: yikes, patches from OpenStack Proposal Bot17:55
*** emagana has quit IRC17:55
s3wongmohankumar: we have two +2s, why not just merge?17:55
mohankumars3wong:  have to set workflow +1 , just want to make sure all are ok17:56
s3wongmohankumar: well, both you and vikram has +A rights, you guys can go ahead :-)17:56
s3wongmohankumar: in our cores we trust :-)17:57
LouisFmohankumar: lets +1 on workflow17:57
mohankumars3wong :  ;)17:57
*** eil397 has quit IRC17:57
mohankumarLouisF : ok17:57
Bali_BaoLouiseF: as the OVN SFC driver, I had a comment before that to update the lchain-add,  you said you want to change to lchain-add lswitch lport-chain [lport-pair-group] ..., but it still  lchain-add lport-chain [lport-pair-group] .. so do we need the l2switch in it?17:57
pcarveryeah, no need for deep analysis of proposal bot reviews17:57
*** v1k0d3n has joined #openstack-meeting-417:57
LouisFok thats it for today17:58
LouisFBali_Bao: no17:58
*** cloudtrainme has joined #openstack-meeting-417:58
LouisFBali_Bao: the intention is the lchains to span multiple lswitches17:59
*** shaohe_feng has quit IRC17:59
LouisFthanks all will bug scrub next week17:59
Bali_Baook, got that, so we can support SFC across multiple networks, right?17:59
LouisFBali_Bao: yes18:00
LouisFbye all18:00
LouisF#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
mohankumarBye all18:00
openstackMeeting ended Thu Jul 28 18:00:24 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-07-28-17.01.html18:00
Bali_Baothanks, bye18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-07-28-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-07-28-17.01.log.html18:00
*** shaohe_feng has joined #openstack-meeting-418:00
igordcardcya18:00
*** bobh has quit IRC18:00
*** emagana has joined #openstack-meeting-418:02
*** juanmafg_ has quit IRC18:02
*** emagana has quit IRC18:03
*** cloudtra_ has joined #openstack-meeting-418:05
*** cloudtra_ has quit IRC18:05
*** dasanind has quit IRC18:05
*** Sukhdev has joined #openstack-meeting-418:07
*** cloudtrainme has quit IRC18:08
*** mohankumar has quit IRC18:08
*** shaohe_feng has quit IRC18:09
*** cloudtrainme has joined #openstack-meeting-418:10
*** Sukhdev has quit IRC18:10
*** shaohe_feng has joined #openstack-meeting-418:10
*** janki has quit IRC18:12
*** ajmiller has quit IRC18:14
*** messy has left #openstack-meeting-418:15
*** Sukhdev has joined #openstack-meeting-418:17
*** ddieterly[away] has quit IRC18:18
*** piet has joined #openstack-meeting-418:19
*** shaohe_feng has quit IRC18:20
*** iberezovskiy is now known as iberezovskiy|off18:20
*** degorenko is now known as _degorenko|afk18:20
*** shaohe_feng has joined #openstack-meeting-418:21
*** ddieterly has joined #openstack-meeting-418:25
*** banix has joined #openstack-meeting-418:25
*** ntpttr__ has quit IRC18:26
*** dshakhray has joined #openstack-meeting-418:26
*** baoli has quit IRC18:29
*** shaohe_feng has quit IRC18:30
*** dasanind has joined #openstack-meeting-418:30
*** shaohe_feng has joined #openstack-meeting-418:31
*** vishwanathj has joined #openstack-meeting-418:34
*** GB21 has quit IRC18:37
*** tonytan4ever has quit IRC18:38
*** lelouch_ has quit IRC18:40
*** shaohe_feng has quit IRC18:40
*** shaohe_feng has joined #openstack-meeting-418:41
*** david-lyle has quit IRC18:42
*** vishnoianil has quit IRC18:46
*** shaohe_feng has quit IRC18:50
*** shaohe_feng has joined #openstack-meeting-418:51
*** kikas has joined #openstack-meeting-418:52
*** ddieterly is now known as ddieterly[away]18:53
*** baoli has joined #openstack-meeting-418:54
*** TravT has quit IRC18:57
*** ddieterly[away] is now known as ddieterly18:59
*** shaohe_feng has quit IRC19:01
*** shaohe_feng has joined #openstack-meeting-419:01
*** ddieterly is now known as ddieterly[away]19:02
*** Bali_Bao has quit IRC19:04
*** lelouch_ has joined #openstack-meeting-419:09
*** kikas has quit IRC19:10
*** shaohe_feng has quit IRC19:11
*** numans has quit IRC19:12
*** shaohe_feng has joined #openstack-meeting-419:12
*** bpokorny has quit IRC19:14
*** Sukhdev has quit IRC19:17
*** LouisF has quit IRC19:19
*** shaohe_feng has quit IRC19:21
*** shaohe_feng has joined #openstack-meeting-419:24
*** matrohon has joined #openstack-meeting-419:30
*** tonytan4ever has joined #openstack-meeting-419:30
*** ddieterly[away] is now known as ddieterly19:31
*** shaohe_feng has quit IRC19:31
*** shaohe_feng has joined #openstack-meeting-419:32
*** cdelatte has joined #openstack-meeting-419:34
*** vishnoianil has joined #openstack-meeting-419:35
*** automagically has joined #openstack-meeting-419:38
*** shaohe_feng has quit IRC19:42
*** shaohe_feng has joined #openstack-meeting-419:42
*** woodster_ has quit IRC19:49
*** shaohe_feng has quit IRC19:52
*** shaohe_feng has joined #openstack-meeting-419:53
*** cloudtrainme has quit IRC19:56
*** doonhammer has quit IRC19:57
*** hvprash has joined #openstack-meeting-419:58
*** doonhammer has joined #openstack-meeting-420:00
*** woodard_ has joined #openstack-meeting-420:01
*** hvprash_ has quit IRC20:02
*** shaohe_feng has quit IRC20:02
*** hvprash has quit IRC20:03
*** shaohe_feng has joined #openstack-meeting-420:03
*** cloudtrainme has joined #openstack-meeting-420:04
*** baoli has quit IRC20:04
*** doonhammer has quit IRC20:04
*** woodard has quit IRC20:04
*** woodard_ has quit IRC20:05
*** hvprash has joined #openstack-meeting-420:06
*** mbound has quit IRC20:08
*** lelouch_ has quit IRC20:10
*** eil397 has joined #openstack-meeting-420:10
*** lelouch_ has joined #openstack-meeting-420:10
*** bpokorny has joined #openstack-meeting-420:11
*** shaohe_feng has quit IRC20:12
*** ddieterly is now known as ddieterly[away]20:13
*** shaohe_feng has joined #openstack-meeting-420:13
*** bpokorny has quit IRC20:16
*** matrohon has quit IRC20:22
*** shaohe_feng has quit IRC20:23
*** shaohe_feng has joined #openstack-meeting-420:23
*** dasanind has quit IRC20:24
*** sabari has quit IRC20:26
*** cdelatte has quit IRC20:26
*** hemanthm is now known as hemanthm|afk20:29
*** dasanind has joined #openstack-meeting-420:30
*** coolsvap_ has quit IRC20:31
*** shaohe_feng has quit IRC20:33
*** shaohe_feng has joined #openstack-meeting-420:34
*** Swami has quit IRC20:34
*** sabari has joined #openstack-meeting-420:34
*** andymaier has joined #openstack-meeting-420:36
*** Swami has joined #openstack-meeting-420:37
*** dshakhray has quit IRC20:37
*** lelouch_ has quit IRC20:38
*** ddieterly[away] has quit IRC20:40
*** shaohe_feng has quit IRC20:43
*** shaohe_feng has joined #openstack-meeting-420:44
*** eil397 has left #openstack-meeting-420:45
*** emagana has joined #openstack-meeting-420:45
*** mfranc213_ has quit IRC20:47
*** ntpttr__ has joined #openstack-meeting-420:48
*** woodster_ has joined #openstack-meeting-420:49
*** mfranc213 has joined #openstack-meeting-420:49
*** emagana has quit IRC20:49
*** matrohon has joined #openstack-meeting-420:53
*** lelouch_ has joined #openstack-meeting-420:53
*** shaohe_feng has quit IRC20:53
*** shaohe_feng has joined #openstack-meeting-420:54
*** hvprash_ has joined #openstack-meeting-420:54
*** cleong has quit IRC20:54
*** woodard has joined #openstack-meeting-420:56
*** hvprash has quit IRC20:57
*** woodard has quit IRC20:57
*** woodard has joined #openstack-meeting-420:58
*** marst has quit IRC21:02
*** rtheis has quit IRC21:02
*** marst has joined #openstack-meeting-421:03
*** shaohe_feng has quit IRC21:04
*** shaohe_feng has joined #openstack-meeting-421:04
*** marst has quit IRC21:05
*** yamamoto has joined #openstack-meeting-421:09
*** mbound has joined #openstack-meeting-421:09
*** ntpttr__ has quit IRC21:09
*** ntpttr__ has joined #openstack-meeting-421:09
*** woodard has quit IRC21:11
*** woodard has joined #openstack-meeting-421:12
*** matrohon has quit IRC21:13
*** mbound has quit IRC21:14
*** shaohe_feng has quit IRC21:14
*** shaohe_feng has joined #openstack-meeting-421:14
*** marst has joined #openstack-meeting-421:19
*** yamamoto has quit IRC21:21
*** shaohe_feng has quit IRC21:24
*** shaohe_feng has joined #openstack-meeting-421:25
*** andymaier has quit IRC21:26
*** spotz is now known as spotz_zzz21:27
*** ddieterly has joined #openstack-meeting-421:33
*** ddieterly is now known as ddieterly[away]21:33
*** thorst has quit IRC21:33
*** ddieterly[away] is now known as ddieterly21:33
*** thorst has joined #openstack-meeting-421:34
*** baoli has joined #openstack-meeting-421:34
*** shaohe_feng has quit IRC21:34
*** shaohe_feng has joined #openstack-meeting-421:35
*** v1k0d3n has quit IRC21:35
*** dasanind has quit IRC21:36
*** piet has quit IRC21:37
*** thorst has quit IRC21:38
*** hvprash has joined #openstack-meeting-421:40
*** hvprash_ has quit IRC21:44
*** shaohe_feng has quit IRC21:45
*** shaohe_feng has joined #openstack-meeting-421:45
*** rahuls_ has quit IRC21:46
*** shaohe_feng has quit IRC21:55
*** shaohe_feng has joined #openstack-meeting-421:55
*** v1k0d3n has joined #openstack-meeting-421:57
*** galstrom is now known as galstrom_zzz21:58
*** lelouch_ has quit IRC21:59
*** ddieterly has quit IRC22:01
*** shaohe_feng has quit IRC22:05
*** shaohe_feng has joined #openstack-meeting-422:06
*** uxdanielle has quit IRC22:06
*** marst has quit IRC22:09
*** marst has joined #openstack-meeting-422:09
*** ddieterly has joined #openstack-meeting-422:10
*** tonytan4ever has quit IRC22:10
*** ddieterly has quit IRC22:11
*** bpokorny has joined #openstack-meeting-422:13
*** shaohe_feng has quit IRC22:15
*** shaohe_feng has joined #openstack-meeting-422:16
*** spotz_zzz is now known as spotz22:17
*** bpokorny has quit IRC22:18
*** yamamoto has joined #openstack-meeting-422:22
*** shaohe_feng has quit IRC22:26
*** shaohe_feng has joined #openstack-meeting-422:27
*** yamamoto has quit IRC22:27
*** krtaylor has quit IRC22:31
*** ntpttr- has quit IRC22:31
*** shaohe_feng has quit IRC22:36
*** ntpttr- has joined #openstack-meeting-422:36
*** rbak has quit IRC22:37
*** shaohe_feng has joined #openstack-meeting-422:41
*** singlethink has quit IRC22:41
*** sarob has joined #openstack-meeting-422:41
*** pmesserli has quit IRC22:44
*** sarob has quit IRC22:46
*** shaohe_feng has quit IRC22:46
*** sarob has joined #openstack-meeting-422:46
*** yamahata has quit IRC22:47
*** shaohe_feng has joined #openstack-meeting-422:47
*** bpokorny has joined #openstack-meeting-422:53
*** shaohe_feng has quit IRC22:56
*** shaohe_feng has joined #openstack-meeting-422:57
*** yamahata has joined #openstack-meeting-423:00
*** ddieterly has joined #openstack-meeting-423:04
*** shaohe_feng has quit IRC23:07
*** shaohe_feng has joined #openstack-meeting-423:08
*** nmadhok has quit IRC23:10
*** tonytan4ever has joined #openstack-meeting-423:11
*** sdague has quit IRC23:11
*** ddieterly is now known as ddieterly[away]23:13
*** tonytan4ever has quit IRC23:16
*** emagana has joined #openstack-meeting-423:16
*** shaohe_feng has quit IRC23:17
*** aderyugin has quit IRC23:17
*** shaohe_feng has joined #openstack-meeting-423:18
*** andymaier has joined #openstack-meeting-423:18
*** emagana has quit IRC23:20
*** bobh has joined #openstack-meeting-423:21
*** nmadhok has joined #openstack-meeting-423:23
*** tonytan4ever has joined #openstack-meeting-423:23
*** yamamoto has joined #openstack-meeting-423:24
*** tonytan_brb has joined #openstack-meeting-423:24
*** ntpttr__ has quit IRC23:26
*** shaohe_feng has quit IRC23:27
*** shaohe_feng has joined #openstack-meeting-423:28
*** tonytan4ever has quit IRC23:28
*** ddieterly[away] has quit IRC23:28
*** yamamoto has quit IRC23:29
*** bobh has quit IRC23:30
*** shaohe_feng has quit IRC23:37
*** sdague has joined #openstack-meeting-423:38
*** shaohe_feng has joined #openstack-meeting-423:38
*** sdague has quit IRC23:43
*** shaohe_feng has quit IRC23:48
*** shaohe_feng has joined #openstack-meeting-423:48
*** tonytan_brb has quit IRC23:52
*** rainya has quit IRC23:53
*** klamath has quit IRC23:58
*** shaohe_feng has quit IRC23:58
*** shaohe_feng has joined #openstack-meeting-423:59

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