Thursday, 2016-04-07

*** spotz_zzz is now known as spotz00:00
*** thorst has quit IRC00:02
*** zenoway has joined #openstack-meeting-400:12
*** zenoway has quit IRC00:16
*** iyamahat has quit IRC00:17
*** bobh_ has joined #openstack-meeting-400:19
*** cbits has quit IRC00:23
*** thorst has joined #openstack-meeting-400:25
*** ddieterly[away] has quit IRC00:26
*** vtech has quit IRC00:33
*** dslevin has joined #openstack-meeting-400:33
*** dslevin has quit IRC00:34
*** dslevin has joined #openstack-meeting-400:34
*** dslevin has quit IRC00:35
*** SimonChung1 has quit IRC00:35
*** dslevin has joined #openstack-meeting-400:35
*** dslevin has quit IRC00:36
*** dslevin has joined #openstack-meeting-400:37
*** dslevin has quit IRC00:37
*** dslevin has joined #openstack-meeting-400:39
*** dslevin has quit IRC00:39
*** ddieterly has joined #openstack-meeting-400:40
*** dslevin has joined #openstack-meeting-400:41
*** dslevin has quit IRC00:42
*** dslevin has joined #openstack-meeting-400:43
*** dslevin has quit IRC00:43
*** thorst has quit IRC00:45
*** thorst has joined #openstack-meeting-400:46
*** zenoway has joined #openstack-meeting-400:48
*** Jeffrey4l has joined #openstack-meeting-400:48
*** annegentle has joined #openstack-meeting-400:49
*** dave-mcc_ has quit IRC00:51
*** prashantD has quit IRC00:51
*** dave-mccowan has joined #openstack-meeting-400:54
*** thorst has quit IRC00:54
*** annegentle has quit IRC00:54
*** zenoway has quit IRC00:54
*** iyamahat has joined #openstack-meeting-400:55
*** zhurong has joined #openstack-meeting-400:58
*** bpokorny has quit IRC01:02
*** dave-mccowan has quit IRC01:03
*** pvaneck has quit IRC01:03
*** zenoway has joined #openstack-meeting-401:03
*** zenoway has quit IRC01:08
*** harshs has left #openstack-meeting-401:14
*** sridhar_ram1 has quit IRC01:18
*** kebray_ has quit IRC01:21
*** reedip has quit IRC01:22
*** reedip has joined #openstack-meeting-401:25
*** sdake has quit IRC01:28
*** sdake has joined #openstack-meeting-401:32
*** ajmiller has joined #openstack-meeting-401:38
*** ajmiller has quit IRC01:39
*** julim has joined #openstack-meeting-401:40
*** baoli has joined #openstack-meeting-401:44
*** baoli has quit IRC01:47
*** ddieterly is now known as ddieterly[away]01:47
*** baoli has joined #openstack-meeting-401:48
*** thorst has joined #openstack-meeting-401:51
*** s3wong has quit IRC01:54
*** JieLi has joined #openstack-meeting-401:57
*** thorst has quit IRC01:59
*** salv-orlando has joined #openstack-meeting-402:03
*** baoli has quit IRC02:06
*** prashantD has joined #openstack-meeting-402:14
*** xingchao has joined #openstack-meeting-402:16
*** piet has joined #openstack-meeting-402:17
*** sdake_ has joined #openstack-meeting-402:20
*** ddieterly[away] is now known as ddieterly02:21
*** sdake has quit IRC02:22
*** salv-orlando has quit IRC02:23
*** ddieterly is now known as ddieterly[away]02:26
*** iyamahat has quit IRC02:27
*** salv-orlando has joined #openstack-meeting-402:28
*** minwang2 has quit IRC02:30
*** salv-orlando has quit IRC02:33
*** piet has quit IRC02:37
*** yamamoto_ has joined #openstack-meeting-402:37
*** iyamahat has joined #openstack-meeting-402:51
*** spotz is now known as spotz_zzz02:54
*** bobh_ has quit IRC02:54
*** piet has joined #openstack-meeting-402:55
*** thorst has joined #openstack-meeting-402:56
*** avarner_ has joined #openstack-meeting-403:01
*** openstackstatus has quit IRC03:01
*** zhurong_ has joined #openstack-meeting-403:02
*** zhurong has quit IRC03:02
*** thorst has quit IRC03:04
*** JRobinson__ has quit IRC03:04
*** avarner has quit IRC03:04
*** sdake_ has quit IRC03:06
*** reedip__ has quit IRC03:07
*** sdake has joined #openstack-meeting-403:07
*** reedip__ has joined #openstack-meeting-403:07
*** JRobinson__ has joined #openstack-meeting-403:08
*** sdake has quit IRC03:17
*** sdake has joined #openstack-meeting-403:18
*** v1k0d3n has joined #openstack-meeting-403:19
*** yamamoto_ has quit IRC03:20
*** jmccrory has quit IRC03:26
*** ddieterly[away] has quit IRC03:26
*** jmccrory has joined #openstack-meeting-403:26
*** JieLi has quit IRC03:28
*** sdake has quit IRC03:28
*** piet has quit IRC03:29
*** vtech has joined #openstack-meeting-403:33
*** piet has joined #openstack-meeting-403:34
*** vishnoianil has quit IRC03:40
*** vtech has quit IRC03:41
*** fitoduarte has joined #openstack-meeting-403:41
*** FallenPegasus has joined #openstack-meeting-403:42
*** neelashah has joined #openstack-meeting-403:49
*** salv-orlando has joined #openstack-meeting-403:50
*** Daviey has quit IRC03:50
*** Daviey has joined #openstack-meeting-403:50
*** v1k0d3n has quit IRC03:51
*** sekrit has quit IRC03:51
*** salv-orlando has quit IRC03:52
*** salv-orlando has joined #openstack-meeting-403:53
*** neelashah has quit IRC03:56
*** piet has quit IRC03:56
*** dave-mccowan has joined #openstack-meeting-403:57
*** julim has quit IRC03:57
*** salv-orlando has quit IRC03:58
*** dave-mcc_ has joined #openstack-meeting-403:58
*** FallenPegasus has quit IRC04:01
*** dave-mccowan has quit IRC04:01
*** thorst has joined #openstack-meeting-404:01
*** sekrit has joined #openstack-meeting-404:05
*** numan_ has joined #openstack-meeting-404:07
*** thorst has quit IRC04:09
*** yamamoto_ has joined #openstack-meeting-404:10
*** Sukhdev has joined #openstack-meeting-404:11
*** minwang2 has joined #openstack-meeting-404:17
*** amotoki has joined #openstack-meeting-404:20
*** javeriak has joined #openstack-meeting-404:25
*** iyamahat has quit IRC04:26
*** banix has joined #openstack-meeting-404:26
*** persia has quit IRC04:31
*** persia has joined #openstack-meeting-404:33
*** SimonChung has joined #openstack-meeting-404:37
*** irenab has quit IRC04:37
*** askb has joined #openstack-meeting-404:38
*** SimonChung1 has joined #openstack-meeting-404:39
*** SimonChung has quit IRC04:39
*** vishnoianil has joined #openstack-meeting-404:40
*** SimonChung has joined #openstack-meeting-404:41
*** SimonChung1 has quit IRC04:44
*** salv-orlando has joined #openstack-meeting-404:57
*** armax has quit IRC04:59
*** GB21 has joined #openstack-meeting-405:00
*** salv-orlando has quit IRC05:01
*** xingchao has quit IRC05:03
*** thorst has joined #openstack-meeting-405:06
*** numan_ has quit IRC05:08
*** minwang2 has quit IRC05:10
*** salv-orlando has joined #openstack-meeting-405:11
*** javeriak has quit IRC05:12
*** thorst has quit IRC05:13
*** hdaniel has joined #openstack-meeting-405:24
*** banix has quit IRC05:25
*** anilvenkata has joined #openstack-meeting-405:33
*** irenab has joined #openstack-meeting-405:36
*** mohankumar__ has joined #openstack-meeting-405:37
*** JRobinson__ is now known as JRobinson__afk05:39
*** javeriak has joined #openstack-meeting-405:39
*** Sukhdev has quit IRC05:40
*** tfukushima has joined #openstack-meeting-405:41
*** minwang2 has joined #openstack-meeting-405:43
*** xingchao has joined #openstack-meeting-405:46
*** minwang2 has quit IRC05:47
*** minwang2 has joined #openstack-meeting-405:47
*** nkrinner has joined #openstack-meeting-405:49
*** xingchao has quit IRC05:53
*** minwang2 has quit IRC05:57
*** prashantD has quit IRC05:57
*** minwang2 has joined #openstack-meeting-405:59
*** numan_ has joined #openstack-meeting-406:10
*** thorst has joined #openstack-meeting-406:11
*** GB21 has quit IRC06:12
*** GB21 has joined #openstack-meeting-406:12
*** unicell has quit IRC06:13
*** JRobinson__afk is now known as JRobinson__06:15
*** unicell has joined #openstack-meeting-406:15
*** hdaniel has quit IRC06:17
*** paul-carlton1 has joined #openstack-meeting-406:18
*** thorst has quit IRC06:18
*** minwang2 has quit IRC06:19
*** askb has quit IRC06:23
*** minwang2 has joined #openstack-meeting-406:24
*** pcaruana has joined #openstack-meeting-406:26
*** GB21 has quit IRC06:26
*** GB21 has joined #openstack-meeting-406:28
*** numan_ has quit IRC06:28
*** numan_ has joined #openstack-meeting-406:28
*** vtech has joined #openstack-meeting-406:40
*** vtech has quit IRC06:40
*** GB21 has quit IRC06:44
*** GB21 has joined #openstack-meeting-406:44
*** zeih has joined #openstack-meeting-406:50
*** GB21 has quit IRC06:51
*** salv-orlando has quit IRC06:52
*** GB21 has joined #openstack-meeting-406:54
*** javeriak has quit IRC06:56
*** hdaniel has joined #openstack-meeting-406:58
*** minwang2 has quit IRC07:00
*** GB21 has quit IRC07:02
*** GB21 has joined #openstack-meeting-407:03
*** vtech has joined #openstack-meeting-407:04
*** hdaniel has quit IRC07:05
*** dshakhray has joined #openstack-meeting-407:06
*** dave-mcc_ has quit IRC07:09
*** ihrachys has joined #openstack-meeting-407:11
*** javeriak has joined #openstack-meeting-407:14
*** jichen has joined #openstack-meeting-407:15
*** GB21 has quit IRC07:16
*** thorst has joined #openstack-meeting-407:16
*** hdaniel has joined #openstack-meeting-407:21
*** thorst has quit IRC07:24
*** JRobinson__ has quit IRC07:28
*** matrohon has joined #openstack-meeting-407:29
*** GB21 has joined #openstack-meeting-407:29
*** mbound has quit IRC07:31
*** rbak has quit IRC07:32
*** rbak has joined #openstack-meeting-407:32
*** GB21 has quit IRC07:37
*** jichen has quit IRC07:43
*** zenoway has joined #openstack-meeting-407:50
*** zeih_ has joined #openstack-meeting-407:51
*** matrohon_ has joined #openstack-meeting-407:51
*** matrohon_ has quit IRC07:51
*** hdaniel has quit IRC07:52
*** salv-orlando has joined #openstack-meeting-407:54
*** zeih_ has quit IRC08:01
*** hdaniel has joined #openstack-meeting-408:05
*** mbound has joined #openstack-meeting-408:07
*** zeih_ has joined #openstack-meeting-408:09
*** salv-orlando has quit IRC08:10
*** zeih_ has quit IRC08:14
*** Jeffrey4l has quit IRC08:16
*** thorst has joined #openstack-meeting-408:21
*** Jeffrey4l has joined #openstack-meeting-408:22
*** GB21 has joined #openstack-meeting-408:26
*** salv-orlando has joined #openstack-meeting-408:26
*** openstackstatus has joined #openstack-meeting-408:29
*** ChanServ sets mode: +v openstackstatus08:29
*** thorst has quit IRC08:30
-openstackstatus- NOTICE: jobs depending on npm are now working again08:33
*** alexchadin has joined #openstack-meeting-408:39
*** dshakhray has quit IRC08:41
*** zehicle_ has quit IRC08:45
*** alexchadin has quit IRC08:45
*** alexchadin has joined #openstack-meeting-408:45
*** zehicle_ has joined #openstack-meeting-408:46
*** pbourke has quit IRC08:51
*** pbourke has joined #openstack-meeting-408:52
*** salv-orl_ has joined #openstack-meeting-408:52
*** salv-orlando has quit IRC08:55
*** zeih has quit IRC08:59
*** javeriak has quit IRC09:05
*** sambetts|afk is now known as sambetts09:05
*** zhurong_ has quit IRC09:09
*** qwebirc52297 has joined #openstack-meeting-409:21
*** javeriak has joined #openstack-meeting-409:22
qwebirc52297any concerns around using a Symantec Protection Engine 7.x for Linux/Solaris in OS?09:25
qwebirc52297trying to determine if running scanning in OS could lead to a compute breakout09:25
*** thorst has joined #openstack-meeting-409:27
*** alex_xu has quit IRC09:32
*** thorst has quit IRC09:34
*** alex_xu has joined #openstack-meeting-409:36
*** JieLi has joined #openstack-meeting-409:38
*** yamamoto_ has quit IRC09:40
*** alexchadin has quit IRC09:41
*** javeriak has quit IRC09:53
*** JieLi has quit IRC09:53
*** allen_gao has quit IRC09:56
*** obondarev has quit IRC10:00
*** allen_gao has joined #openstack-meeting-410:01
*** obondarev has joined #openstack-meeting-410:06
*** numan_ has quit IRC10:07
*** qwebirc52297 has quit IRC10:08
*** obondarev has quit IRC10:12
*** Kiall has quit IRC10:14
*** Kiall has joined #openstack-meeting-410:14
*** sdague has joined #openstack-meeting-410:20
*** numan_ has joined #openstack-meeting-410:21
*** numan_ has quit IRC10:22
*** numan_ has joined #openstack-meeting-410:22
*** GB21 has quit IRC10:28
*** GB21 has joined #openstack-meeting-410:31
*** obondarev has joined #openstack-meeting-410:31
*** thorst has joined #openstack-meeting-410:32
*** _degorenko|afk is now known as degorenko10:32
*** thorst has quit IRC10:39
*** yamamoto has joined #openstack-meeting-410:42
*** GB21 has quit IRC10:49
*** GB21 has joined #openstack-meeting-410:50
*** andymaier has joined #openstack-meeting-410:53
*** alex_xu has quit IRC10:55
*** mfedosin has joined #openstack-meeting-410:56
*** iberezovskiy_ is now known as iberezovskiy10:57
*** alex_xu has joined #openstack-meeting-410:57
*** yamamoto has quit IRC11:04
*** yamamoto has joined #openstack-meeting-411:06
*** thorst has joined #openstack-meeting-411:11
*** thorst_ has joined #openstack-meeting-411:11
*** thorst has quit IRC11:15
*** rtheis has joined #openstack-meeting-411:18
*** GB21 has quit IRC11:21
*** mbound has quit IRC11:24
*** tfukushima has quit IRC11:25
*** mbound has joined #openstack-meeting-411:29
*** bobh_ has joined #openstack-meeting-411:31
*** mfedosin has quit IRC11:34
*** vtech has quit IRC11:34
*** vtech has joined #openstack-meeting-411:35
*** alex_xu has quit IRC11:41
*** alex_xu has joined #openstack-meeting-411:43
*** dslevin1 has joined #openstack-meeting-411:44
*** dslevin1 has quit IRC11:44
*** jhesketh has joined #openstack-meeting-411:45
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"11:45
*** dslevin1 has joined #openstack-meeting-411:46
*** banix has joined #openstack-meeting-411:50
*** anilvenkata has quit IRC11:50
*** GB21 has joined #openstack-meeting-411:52
*** mbound has quit IRC11:54
*** mbound has joined #openstack-meeting-411:54
*** mbound has quit IRC11:56
*** xingchao has joined #openstack-meeting-411:56
*** javeriak has joined #openstack-meeting-411:58
*** andymaier has quit IRC11:59
*** mbound has joined #openstack-meeting-412:01
*** xingchao has quit IRC12:01
*** jhesketh has quit IRC12:07
*** jhesketh has joined #openstack-meeting-412:07
*** cbits has joined #openstack-meeting-412:11
*** baoli has joined #openstack-meeting-412:13
*** baoli_ has joined #openstack-meeting-412:13
*** GB21 has quit IRC12:16
*** neelashah has joined #openstack-meeting-412:17
*** javeriak has quit IRC12:17
*** baoli has quit IRC12:18
*** neelashah has quit IRC12:22
*** woodard has joined #openstack-meeting-412:23
*** mohankumar__ has quit IRC12:24
*** woodard has quit IRC12:24
*** woodard has joined #openstack-meeting-412:25
*** salv-orl_ has quit IRC12:28
*** bobh_ has quit IRC12:28
*** cdelatte has quit IRC12:30
*** banix has quit IRC12:31
*** banix has joined #openstack-meeting-412:32
*** banix has quit IRC12:32
*** cbits has quit IRC12:32
*** Shahid_ has joined #openstack-meeting-412:35
*** mohankumar__ has joined #openstack-meeting-412:36
*** salv-orlando has joined #openstack-meeting-412:40
*** sigmavirus24_awa is now known as sigmavirus2412:47
*** cdelatte has joined #openstack-meeting-412:47
*** piet has joined #openstack-meeting-412:50
*** julim has joined #openstack-meeting-412:51
*** annegentle has joined #openstack-meeting-412:51
*** v1k0d3n has joined #openstack-meeting-412:53
*** delattec has joined #openstack-meeting-412:53
*** dshakhray has joined #openstack-meeting-412:54
*** cdelatte has quit IRC12:56
*** mbound has quit IRC12:58
*** vikram has joined #openstack-meeting-412:59
*** mbound has joined #openstack-meeting-413:00
*** vtech has quit IRC13:04
*** vtech has joined #openstack-meeting-413:05
*** Steap has joined #openstack-meeting-413:05
*** xingchao has joined #openstack-meeting-413:12
*** anilvenkata has joined #openstack-meeting-413:12
*** pmesserli has joined #openstack-meeting-413:13
*** javeriak has joined #openstack-meeting-413:14
*** mbound has quit IRC13:22
*** bobh_ has joined #openstack-meeting-413:23
*** cbits has joined #openstack-meeting-413:24
*** mbound has joined #openstack-meeting-413:28
*** banix has joined #openstack-meeting-413:34
*** annegentle has quit IRC13:38
*** xingchao has quit IRC13:39
*** xingchao has joined #openstack-meeting-413:39
*** yamamoto has quit IRC13:40
*** rbak has quit IRC13:42
*** irenab has quit IRC13:44
*** Shahid_ has quit IRC13:45
*** piet has quit IRC13:49
*** mbound has quit IRC13:51
*** mbound_ has joined #openstack-meeting-413:51
*** cbits has quit IRC13:51
*** zeih has joined #openstack-meeting-413:54
*** ddieterly has joined #openstack-meeting-413:54
*** cbits has joined #openstack-meeting-413:56
*** piet has joined #openstack-meeting-413:56
*** ddieterly is now known as ddieterly[away]13:56
*** bunting has joined #openstack-meeting-413:56
*** mfedosin has joined #openstack-meeting-413:57
*** yamamoto has joined #openstack-meeting-413:57
*** paul-carlton1 has quit IRC13:59
nikhilCourtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k13:59
nikhilCourtesy meeting reminder: Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting13:59
sigmavirus24o/13:59
nikhilCourtesy meeting reminder: dshakhray, wxy, dhellmann, kairat13:59
sigmavirus24Thanks nikhil13:59
*** kairat has joined #openstack-meeting-413:59
nikhil:)13:59
nikhil#startmeeting glance13:59
openstackMeeting started Thu Apr  7 13:59:58 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
nikhilo/14:00
mfedosino/14:00
buntingo/14:00
rosmaitao/14:00
hemanthmo/14:00
Steapo/14:01
*** avarner has joined #openstack-meeting-414:01
avarnero/14:01
nikhillet's get started14:01
nikhil#topic agenda14:01
*** openstack changes topic to "agenda (Meeting topic: glance)"14:01
kairato/14:01
nikhilwe've a short agenda today14:01
*** yamahata has joined #openstack-meeting-414:01
nikhilI want to spend as much time as possible on discussing summit sessions14:02
nikhilhttps://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
nikhil#topic Updates14:02
*** openstack changes topic to "Updates (Meeting topic: glance)"14:02
tjcocozzo/14:02
nikhil#info Glare updates ( mfedosin )14:02
mfedosinhey!14:02
nikhilhi Mike14:03
nikhilhow are things?14:03
nikhil(in the artifacts world)14:03
*** yamamoto has quit IRC14:03
mfedosinwe spent last three days discussing possible improvements of Glare architecture14:03
mfedosin1. we simplified our engine14:04
*** rpjr_ has joined #openstack-meeting-414:05
mfedosinfyi engine is a thing that does policies check, notifications and access control14:05
dshakhrayo/14:05
*** cloudtrainme has joined #openstack-meeting-414:05
mfedosincode was reduced twice there14:05
mfedosin2. we rethought how we delete artifacts14:06
mfedosinif you read the spec deletion was rather complicated there14:06
mfedosinwe decided to keep it simple14:06
mfedosinfirst of all we got rid of 'killed' and 'deleted' statuses for blobs14:07
mfedosinand deletion looks like:14:07
*** sdake has joined #openstack-meeting-414:07
mfedosin1. Glare set status 'deleted' to artifact and 'pending_delete' to all his blobs14:07
mfedosinit's a transaction operation14:08
mfedosin2. Then Glare starts to remove files from store and remove blob instances from db in cycle14:08
mfedosinIf something bad happens like lost connection with data storage then glare raises exception and leaves other blobs in penging_delete status14:09
mfedosinand operator can clean the storage with scrubber14:09
*** xingchao_ has joined #openstack-meeting-414:10
mfedosinIf delayed delete is activated then only 1 step is performed and Glare misses the second14:10
*** neelashah has joined #openstack-meeting-414:10
mfedosinthat's all updates we have from Glare14:11
mfedosinthanks :)14:11
*** xingchao has quit IRC14:11
*** rbak has joined #openstack-meeting-414:11
nikhilThanks mfedosin14:11
nikhilAre you wanting to get feedback on any of these items?14:11
nikhilguess, that's a no14:11
mfedosinI'm not sure if it's the best place to get the feedback14:12
hemanthmmfedosin: just curious, how do you ensure #1 is a transaction?14:12
*** sdake has quit IRC14:12
hemanthm(feel free to say we can take it offline)14:12
mfedosinif you have something to say feel free to join glare meeting on Monday14:12
*** nkrinner has quit IRC14:12
nikhilmfedosin:  sure, I was saying if  we need to link something here so that people can go and give that feedback14:12
mfedosinhemanthm: it's a regular update14:12
mfedosinone call to db14:12
hemanthmtwo updates?14:12
hemanthmok14:13
nikhilok, mfedosin can link the spec or feedback form later14:13
nikhilmoving on14:13
nikhil#info Nova v1, v2 updates14:13
mfedosinset status 'deleted' to artifacts and 'pending_delete' to its blobs14:13
mfedosinit's me again :)14:13
mfedosinso, I proposed a spec for this update14:14
mfedosin#link https://review.openstack.org/#/c/301741/14:14
mfedosinthere is huge feedback14:14
nikhilyes and some more feedback is on this email thread14:15
nikhil#link https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg79862.html14:15
mfedosinalso I send an email to ML where I describe things that are done14:15
mfedosinand should be done14:15
nikhil#link https://www.mail-archive.com/openstack-dev@lists.openstack.org/thrd2.html#7986214:16
mfedosinhope to find some time today to answer there14:16
mfedosinthanks nikhil14:16
nikhilnp14:16
nikhilI think we've a good momentum on the work14:16
nikhilAlso, the thread has some context that I got from irc conversation on -nova14:16
nikhilthe proposed changes look like something that can be done in specless BP14:17
mfedosinem... what?14:17
nikhilWe should ad-sync on Monday (decide on a time offline) on this topic (whomever interested)14:17
mfedosinI think spec is needed there14:18
nikhilin a gist, the discovery related changes14:18
nikhilI don't want to say what nova spec is needed or not needed, if possible I'd refrain from proposing another nova spec14:19
nikhillet's try to get things done in a specless BP for things that are not too broad in changes proposed14:19
*** julim has quit IRC14:19
nikhilI can update more stuff on -glance14:19
mfedosinhmm... we need to discuss it later14:20
nikhilmoving on14:20
nikhil#topic Releases14:20
*** openstack changes topic to "Releases (Meeting topic: glance)"14:20
mfedosinnikhil: yes14:20
nikhilTHere were some release notes changes that release team was trying to get in14:20
*** thorst_ has quit IRC14:21
*** sdake has joined #openstack-meeting-414:21
nikhilif you see a holler on #openstack-glance please courtesy them with a review. Thanks in advance.14:21
nikhilthat's it on this on14:21
nikhilmoving on14:21
nikhil#topic Announcements14:21
*** openstack changes topic to "Announcements (Meeting topic: glance)"14:21
nikhilTwo things14:21
nikhil#info Glance virtual pre summit sync is on Tuesday April 12 1400-1800 UTC14:22
*** julim has joined #openstack-meeting-414:22
nikhilwe will be using the same etherpad for summit planning viz.14:22
*** thorst_ has joined #openstack-meeting-414:22
nikhil#link https://etherpad.openstack.org/p/newton-glance-summit-planning14:22
nikhilif someone needs to discuss a CP topic, we may be able to give short feedback (~20 mins)14:23
*** blahRus has joined #openstack-meeting-414:23
nikhil#link https://etherpad.openstack.org/p/newton-cross-project-sessions14:23
nikhilthose are in the process of being selected14:23
nikhilsecond14:24
nikhil#info Glance Newton-mid-cycle will be in Boston (we're finalizing on the dates with the sponsors)14:24
mfedosinwhen?14:24
nikhilHopefully that will give you some time to start planning travel14:24
nikhilIt will be sometime in mid-June14:25
nikhilfinal dates will be announced once the sponsors give thumbs up14:25
nikhilany questions or other announcements?14:25
mfedosinalso there was a doodle afair14:26
*** baoli_ has quit IRC14:26
nikhilyes, that was to get feedback from the team. sponsors are on their independent timeline :)14:26
*** thorst__ has joined #openstack-meeting-414:26
nikhilif you're interested in knowing14:26
nikhilhere's the tentative dates14:27
nikhil#link http://doodle.com/poll/2c6dqs9ab253a59m14:27
mfedosinit also show who's going to attend it14:27
nikhils/is/may be/14:27
*** thorst_ has quit IRC14:27
*** spotz_zzz is now known as spotz14:28
nikhilwe will have a more concrete agenda for mid cycle closer to the event14:28
nikhilthis was done to help plan travel14:28
nikhilthat document will be more accurate of the anticipated participation, schedule and related events during the meetup14:29
nikhilmoving on14:29
*** yamamoto has joined #openstack-meeting-414:29
nikhil(you can ask me ques offline)14:29
nikhil#topic     Glance summit sessions continued14:29
*** openstack changes topic to "Glance summit sessions continued (Meeting topic: glance)"14:29
nikhil#link     https://etherpad.openstack.org/p/newton-glance-summit-planning14:29
nikhilSO, the continuation is from this part14:30
nikhil#link http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-03-24-13.59.log.html#l-11214:30
*** javeriak has quit IRC14:30
*** baoli has joined #openstack-meeting-414:30
*** matrohon has quit IRC14:31
nikhilwe've discussed proposals 3, 4, 8, 9 & 16 as of now14:31
*** matrohon has joined #openstack-meeting-414:31
nikhiloops14:31
nikhil15 too14:31
nikhilrosmaita: I am putting you on the spot here to discuss proposal #14 if you14:32
nikhilyou14:32
nikhileh14:32
rosmaitasure14:32
nikhilkeyboard fail14:32
nikhil#info discussion on Proposal #14 ( rosmaita )14:32
rosmaitatwo related issues about image properties14:33
rosmaitaone is whether glance shoudl enforce metadef-defined property values on images14:33
rosmaitathe other is whether we can come up with a lifecycle for public images14:33
rosmaitain this sense14:33
rosmaitadeployers create image 1, end-users boot from it14:34
rosmaitasomebody finds an issue with image 1, so the deployer creates image 214:34
rosmaitaall new people who want to use that operating system should use image 214:34
*** javeriak has joined #openstack-meeting-414:34
rosmaitabut some people may still want to use image 1 and patch by themselves14:34
rosmaitaso the problem is: how to "hide" image 1 but have it still be public14:35
rosmaitaand obviously this will be a series of >2 images for the lifecycle of a particular operating system image14:35
hemanthmimage deprecation :)14:35
rosmaitathere's been interest in this kind of thing for a while, various clouds have their own hacks to make it work, but it seems like a real use case that we should actually provide a solution for14:36
rosmaitasomeone was in the glance channel earlier this week asking about this14:36
hemanthmrosmaita: so these older images are expected to stay around forever?14:36
*** thorst__ has quit IRC14:37
rosmaitahemanthm: yes14:37
nikhilrosmaita: are we trying to present a set of formal (protected) properties for this?14:37
rosmaitai think so14:38
nikhilI guess your problem statement is quite clear, I'm curious about the title14:38
*** spotz is now known as spotz_zzz14:38
rosmaitaactually, i am not sure14:38
rosmaitahence the discussion14:38
nikhilok, so this will be something that will revolve around feedback?14:38
rosmaitaunless we can come up with somethign that we think will work pre-summit14:38
rosmaita(that's what i'd prefer)14:38
nikhilI am trying to collect this info to tag potential particular sessions for other tracks too (for example, this one could be operator track)14:39
rosmaitai haven't had time to brainstorm a solution yet14:39
nikhilcool14:39
rosmaitayes, it would be good to have operator input for sure14:39
nikhilI do have _some_ reservations around lifecycle management using metadata as properties can be ephemeral protected or not14:39
rosmaitanikhil: i agree, that's why i paired these two topics together14:40
rosmaitanamely14:40
nikhilgotcha14:40
rosmaitaexpanding "common image properties" to be really common image properties14:40
*** TravT has joined #openstack-meeting-414:40
rosmaitaand then maybe these lifecycle things would be one of those14:40
nikhilhm, that's good thought14:41
rosmaitait will help with import, too14:41
*** spotz_zzz is now known as spotz14:41
*** thorst_ has joined #openstack-meeting-414:41
rosmaitahave specific image properties that are required14:41
nikhil+114:41
rosmaitait's an interoperability thing, really14:41
nikhilin general, it would be good to think how we can provide more context to this proposal so that rest of the clouds who may not need aren't really affected14:41
nikhilbut if you're thinking interop then may be all are involved14:42
*** ddieterly has joined #openstack-meeting-414:42
*** banix has quit IRC14:42
rosmaitaso all clouds for topic (a), maybe not for topic (b)14:42
nikhilI see14:42
rosmaitametadefs gives us some tools we didn't have back in grizzly for common image properties14:43
nikhilcool14:43
nikhilrosmaita: I'm assuming you want to discuss (a) later?14:44
nikhilor that you tied those up together in that problem statement?14:44
rosmaitai could discuss now14:44
nikhilsure, we've about 5 mins for this one :)14:45
rosmaitathe description is kind of self-explanatory14:45
rosmaitaso maybe no discussion? anyone have any questions? or it metadata too boring?14:46
*** cbits has quit IRC14:46
rosmaitaor am i netsplit?14:46
nikhilnah14:47
nikhilI think it's one of those that may be good to discuss with other teams14:47
*** numan_ has quit IRC14:47
nikhilparticularly Nova in this case14:47
rosmaitayes, nova should have some opinions14:47
nikhilI want to know what other teams are using14:47
nikhiland hopefully this feedback will help with the nova's compat layer conversation14:48
rosmaitaok, well maybe discuss further on april 1214:48
nikhilThanks rosmaita!14:48
nikhilmoving on14:48
nikhil#info Proposal #13 Deprecate glance-registry14:48
nikhilflaper87: proposed this one, but I guess he's not here today14:49
nikhilI think we need to give this one another 20 mins on april 1214:49
*** javeriak_ has joined #openstack-meeting-414:49
rosmaitai became interested in it while working on a bug, and realized that the registry is a PITA14:49
nikhil:)14:49
nikhilOne initial feedback from me:14:49
nikhilWe need to figure out which other services are using registry. for example, scrubber14:50
nikhiland who all prefer that14:50
nikhilmay be I can replace services with tools above14:50
*** javeriak has quit IRC14:50
nikhilanyone have comments?14:51
rosmaita+1 to discuss on april 1214:51
nikhilthanks14:51
mfedosinyep14:51
nikhilmoving on14:51
nikhil#info Proposal #12 Glance + Microversions14:51
nikhilWell, I am interested to gather feedback14:52
*** salv-orl_ has joined #openstack-meeting-414:52
nikhilBut I don't think we'd do this in parallel with other important API changes14:52
rosmaitai agree it's worth looking into, but maybe not now14:52
nikhilanyone else?14:52
*** paul-carlton1 has joined #openstack-meeting-414:52
nikhilmoving on14:53
nikhil#info Proposal #11     Glance Store 1.0.0 Let's get the re-factor done14:53
*** salv-orl_ has quit IRC14:53
nikhilagain, flaper87's proposal14:53
nikhilwe can just give him 45 mins slot on april 12 to discuss these items14:53
mfedosinnikhil: frankly speaking refactor is needed14:53
mfedosinbecause Glare is going to use glance_store14:54
nikhilok14:54
nikhilmfedosin: but do you think refactor can be done in that small amount of time?14:54
*** salv-orlando has quit IRC14:54
mfedosinand it doesn't satisfy our requirements14:54
*** thorst__ has joined #openstack-meeting-414:54
nikhilI see14:54
mfedosinno, we have a layer that hides all things14:54
*** sigmavirus24 is now known as sigmavirus24_awa14:55
mfedosinbut it's better to refactor glance_store's code14:55
nikhilwell, there are some CP discussions around backward compatibility scope14:55
*** anilvenkata has quit IRC14:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
nikhilI think it would be worth for you to be at that CP session on Tuesday14:55
mfedosinand make it usable for all services not only Glance14:55
mfedosinwhat time again?14:56
rosmaita1400-1800 utc14:56
rosmaitaoops, that's not it14:56
nikhilyep, let's discuss the rest of the sessions next week on tuesday and those who don't get time can be discussed on thursday's meeting14:56
nikhilrosmaita: that's correct14:56
rosmaitaoh, ok14:57
nikhilTuesday April 12, 1400-1800 UTC14:57
rosmaita(i need 1 min of "general discussion" before meeting ends)14:57
mfedosinnot perfect for me but not bad14:57
nikhilsure14:57
nikhil#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:57
rosmaitafollowing up on my action item from last week, i put up a patch to the glance in-tree docs about "the future" of glance14:57
*** javeriak has joined #openstack-meeting-414:57
rosmaita#link https://review.openstack.org/#/c/301359/14:57
nikhilmfedosin: there's a email thread if you want to provide feedback14:57
rosmaitaplease take a look, especially cores, so we can all be on the same page before the summit14:57
nikhilbut I'd say a bit too late to change the time14:58
rosmaitaa few people have made some good suggestions about restructuring the glance in-tree docs, but at this point i'd really like to concentrate on content14:58
*** thorst_ has quit IRC14:58
rosmaitathe aim of this exercise is to make sure that we're in agreement (more or less) about both (a) where the glance project should be going, and (b) some text that says where the glance project is going that we can point people to14:58
rosmaitathat's it, thanks!14:58
nikhilThanks rosmaita! This is really useful effort, especially prior to summit.14:58
*** avarner has quit IRC14:59
*** javeriak_ has quit IRC14:59
nikhil#info we may have to skip meeting on thursday april 21 so, please be ready next week with any important discussions14:59
mfedosinwe can skip april 28 too15:00
nikhilThat's it for today. Thanks all for joining. Cya on Tuesday.15:00
mfedosinthanks! bye15:00
nikhilconnection info on the virtual sync will be on #openstack-glance ~1400 UTC15:00
nikhil#endmeeting15:00
*** thorst__ is now known as thorst________15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Apr  7 15:00:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-04-07-13.59.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-04-07-13.59.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-04-07-13.59.log.html15:00
*** yingjun has joined #openstack-meeting-415:00
*** RickA-HP has joined #openstack-meeting-415:00
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Apr  7 15:01:02 2016 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
*** bunting has left #openstack-meeting-415:01
*** iyamahat has joined #openstack-meeting-415:01
TravTo/15:01
rosmaitao/15:02
yingjuno/15:02
RickA-HPo/15:02
*** xingchao_ has quit IRC15:02
*** sjmc7 has joined #openstack-meeting-415:03
TravTokay15:03
sjmc7hey, sorry, connection issue15:03
TravTso. https://etherpad.openstack.org/p/search-team-meeting-agenda15:03
TravT#topic Mitaka release15:04
*** openstack changes topic to "Mitaka release (Meeting topic: openstack search)"15:04
*** lei-zh1 has joined #openstack-meeting-415:04
TravTMitaka is officially released15:04
TravTjust chatted with thierry about it15:04
TravTno more RCs15:04
sjmc7woo!15:04
TravT\o/15:04
TravTGreat job everybody15:04
TravT!15:04
TravTwhich brings us to:15:05
TravT#topic     Candidates for backports (potential 0.2.1)15:05
*** openstack changes topic to "Candidates for backports (potential 0.2.1) (Meeting topic: openstack search)"15:05
TravTwe don't have any more rcs15:05
*** kairat has left #openstack-meeting-415:05
TravTbut we can request a point release at any time15:05
TravTso 0.2.115:05
TravTand sjmc7 found a couple candidates there15:06
*** lakshmiS_ has joined #openstack-meeting-415:06
sjmc7found/caused15:06
TravT    Fix for updating nova server on volume attach/detach (sjmc7): https://review.openstack.org/#/c/301943/15:06
TravTthat's merged15:06
*** stevelle has joined #openstack-meeting-415:06
sjmc7i already put up a backport review for that one15:06
TravTlink?15:06
sjmc7https://review.openstack.org/30281415:07
TravTis anybody opposed to me approving that for stable/mitaka?15:07
*** ajmiller has joined #openstack-meeting-415:07
lei-zh1nope15:08
*** thorst________ is now known as thorst_15:08
rosmaitaseems kind of important15:08
TravTokay, then i'm going to do that.15:08
nikhilo/15:09
TravTsjmc7 want to talk about:     Discussion on https://bugs.launchpad.net/searchlight/+bug/1565028; any fix is going to be a bit unpleasant, not sure about the payoff15:09
openstackLaunchpad bug 1565028 in OpenStack Search (Searchlight) "Neutron port detach isn't detected by nova event handler" [Critical,New]15:09
sjmc7this is a similar issue; detecting port attach/detach events for servers15:09
sjmc7the solution’s much less straightforward, but i will have another think about it15:10
*** fitoduarte has quit IRC15:10
sjmc7i think this is a much less common occurrence (it only affects explicitly attaching a neutron port to an instance, not automatic port creation)15:10
rosmaitai guess this is compounded by the nova-networks vs neutron situation (which i know nothing about other than that it used to be a "thing")15:11
sjmc7and we do currently deal with port attach, just not detach, which is troublesome15:11
sjmc7yeah, nova networks is another kettle of fish15:11
*** Steap has left #openstack-meeting-415:11
sjmc7nova abstracts some parts of that but not all15:11
sjmc7this is one of them15:11
sjmc7i actually think it’s kind of a bug on nova’s side in a way15:11
yingjunI added nova to the bug, not sure if what’s the nova guys think15:11
sjmc7it should send interface-attach/detach events15:12
rosmaitai agree15:12
rosmaita(though that doesn't help much)15:12
sjmc7right. so i don’t know if it’s worth a hacky fix for this15:12
rosmaitahow bad would it be to have not port info indexed?15:13
rosmaita*no15:13
sjmc7that’s the other option. it’s nice being able to get servers by IP address15:13
rosmaitajust wondering if inaccurate data is worse than no data at all15:13
sjmc7yeah15:13
rosmaitano, you answered the question15:13
rosmaitapeople like to get servers by ip address15:13
sjmc7the denormalized fields the nova API gives us cause trouble in this respect, but they are quite useful15:13
sjmc7i would like ot persuade nova to have the server notifications match the API output but that seems like a long shot15:14
TravTi just wonder how often this happens in the real world?15:14
rosmaitawell, probably a lot if you have your own subnet15:14
sjmc7floating IPs i suspect would be one example15:14
sjmc7and yeah, that too15:14
rosmaitathey are kind of small, may have to add/subtract servers15:15
sjmc7maybe a hacky solution is better than none15:15
TravTsjmc7, the other events will cause us to update the port details as well, correct?15:15
*** javeriak has quit IRC15:15
TravTeg. restart15:15
sjmc7yes15:15
rosmaitaTravT: that's a good point15:15
sjmc7yeah, anything where we have to reindex servers for another reason will pick up any changes15:15
rosmaitamaybe we should just leave the bug open until nova fixes it15:16
sjmc7so yeah, all these reasons leave me on the fence15:16
TravTwhat is your hacky fix?15:16
sjmc7the only solution i’ve got is not very reliable - it’d mean searching for instances matching the port id15:16
sjmc7and we’ve stayed away from searching the e-s data during updates because of potential races with updating the search index15:17
sjmc7it’d work most of the time15:17
*** javeriak has joined #openstack-meeting-415:18
sjmc7i guess i can put up a fix and see what it looks like?15:18
*** baoli has quit IRC15:19
sjmc7we do need, again, to come up with a general answer for when notifications don’t match API output; we keep running into these kinds of problems15:19
TravTI'm probably suffering from amnesia, but i feel like i missed a part of your proposal. are you saying on a *neutron* port event, we'd do this search and update instances appropriately?15:19
sjmc7yep15:19
*** xingchao has joined #openstack-meeting-415:20
TravTokay here's my .0215:21
rosmaitaso the neutron info is up to date, but the nova is not?15:21
sjmc7yep15:22
TravT thanks yingjun for adding nova... i think it would be good if sjmc7 cleaned up the description a bit for nova patch team ease of consumption15:22
*** zeih has quit IRC15:22
TravTi think the idea you have sjmc7 is interesting, but i'm slightly hesitant to immediately backport to stable15:22
TravTso maybe could go on master first for a bit?15:23
sjmc7ok15:23
*** zeih has joined #openstack-meeting-415:23
sjmc7looking at the code there is actually a pretty serious bug we may have to backport :(  i’ll file it separately15:23
rosmaitai don't like this proposal, because the ip search is rough on the nova api15:23
TravTrosmaita?15:24
sjmc7rosmaita: i wouldn’t search nova’s api, just the SL data15:24
rosmaitaok, i misunderstood15:24
sjmc7yeah, that’d be a no-no15:24
*** neelashah has quit IRC15:25
lakshmiS_here's a crazy idea. Make just port as parent of nova and let neutron port updates go there.15:25
*** ddieterly is now known as ddieterly[away]15:25
sjmc7?15:25
*** alex_xu has quit IRC15:25
sjmc7ports can belong to routers or subnets15:25
sjmc7or rather, be attached to15:25
*** minwang2 has joined #openstack-meeting-415:26
TravThmm... that's be network --> port --> server15:26
sjmc7wait, wait15:26
sjmc7servers are not logically descendents of ports15:26
TravTthat seems a bit wrong15:26
*** yamahata has quit IRC15:26
lakshmiS_hmm let me think through if there is a way to normalize for updates15:27
sjmc7the problem is that a port detach contains no information indicating what it was attached from15:27
sjmc7err, detached from15:27
TravThmm15:27
TravTthat seems like it could be a bug / bp on neutron15:27
*** cloudtrainme has quit IRC15:28
*** zeih has quit IRC15:28
sjmc7spread the wealth :)15:28
rosmaitaTravT: +115:28
sjmc7in the meantime, what’s the consensus15:28
*** Swami has joined #openstack-meeting-415:28
*** alex_xu has joined #openstack-meeting-415:29
rosmaitai think do nothing, figure eventully server updates will make the data consistent15:29
rosmaitaleave the bug open15:29
rosmaitasee if more people complain15:29
sjmc7ok. we can maybe bring it to neutron’s attention too15:29
rosmaitabecause i think TravT has a good point that we may not see this very much15:30
rosmaitasjmc7: +!15:30
rosmaita+1, even15:30
TravTis +! the same as a -1?15:30
TravT(plus not)15:30
*** armax has joined #openstack-meeting-415:30
TravT;)15:31
sjmc7*tumbleweed*15:31
TravTtough crowd15:31
*** cloudtrainme has joined #openstack-meeting-415:31
TravTokey15:31
TravTdokey15:31
TravTso, back to 0.2.115:31
TravTi think the volume attach bug alone is worth a point release15:32
david-lyleTravT: point release of which?15:32
sjmc7ok. i’m filing another related server notification bug that i’ll fix today, so can we hold off until then?15:32
TravTis there anything else critical that could be solved in a few days that also should go in point release15:32
TravTsearchlight15:32
TravTit is too late for rc3 (mitaka out)15:32
david-lylewe're not release independent15:33
TravTbut thierry said we can do a 0.2.1 at any time15:33
david-lyleoh O_o15:33
david-lyleI thought that was owned by stable15:33
david-lyleprobably shifted again15:33
david-lylettx would know15:33
TravTwe own stable for searchlight, but that's what i was told this morning15:33
david-lyleinteresting15:34
david-lylego back to ignoring me15:35
david-lyle:)15:35
TravTi think for things that aren't patch releases (e.g. 0.2.x) it would be diff15:35
* david-lyle is tempted to start with "back in my day"15:36
TravTlol15:36
*** iyamahat has quit IRC15:36
TravTso, anybody against me putting up a point release once https://review.openstack.org/#/c/302814/ lands?15:36
TravTor is there anything else to consider?15:36
sjmc7yes :)15:37
sjmc7i’ve got another similar change i’d like to get in15:37
TravTokay, do share15:37
sjmc7i’m filing the bug15:37
sjmc7related to the port stuff15:37
TravTi really need some time for summit planning as well15:37
sjmc7go for it15:37
*** ddieterly[away] is now known as ddieterly15:37
*** galstrom_zzz is now known as galstrom15:37
TravT#topic summit planning15:38
*** openstack changes topic to "summit planning (Meeting topic: openstack search)"15:38
TravTi need to get things uploaded into eventbrite asap15:38
TravT#link https://etherpad.openstack.org/p/searchlight-newton-summit15:38
TravTfirst thing to notice is that we will have some discussion on search in a horizon session. and looks like a good chance there will be a swift session15:39
TravTi put links for that at the top15:39
TravTnext, we have 3 sessions15:39
TravT1 fishbowl15:39
TravT2 working15:39
TravTcurrently 5 ideas listed15:40
TravTi'll pause for a minute to let people look at what is there now.15:40
sjmc7i’ve got one i haven’t put on there about weaning ourselves off API calls15:41
TravTand to add ideas15:41
TravTsjmc7: d'oh!  can't believe i don't have that one on after rambling about maybe doing a fishbowl on it15:41
sjmc7adding it now15:41
TravTi think that would be a good fishbowl and we could also tag neutron, nova, cinder on it.15:42
*** GB21 has joined #openstack-meeting-415:42
TravTironic as well15:42
sjmc7maybe, but i also mean from our perspective, what our general approach should be15:42
*** spzala has joined #openstack-meeting-415:43
*** ddieterly is now known as ddieterly[away]15:44
*** prashantD has joined #openstack-meeting-415:44
*** javeriak has quit IRC15:45
*** ddieterly[away] is now known as ddieterly15:46
TravTlei-zh1: are you there?15:46
*** xingchao has quit IRC15:47
TravTThe pipeline topic surely would benefit from some face to face time, but need to know if anybody from your team will be there to talk about it15:47
*** gregfaust has joined #openstack-meeting-415:48
lei-zh1yes, yuntong will be there15:48
TravTwill malini be there as well?15:48
lei-zh1although he carries some other tasks, but he can have a discussion on that15:48
TravTdoes she care about this?15:48
*** baoli has joined #openstack-meeting-415:49
lei-zh1I'll confirm with her about it15:49
*** matrohon has quit IRC15:49
TravTok.15:49
lei-zh1not sure about her schedule15:49
TravTso, i think the cross project aspect of notifications makes that one the most likely candidate for fishbowl out of what we have right now15:50
TravTthat one meaning the notification topic15:50
lei-zh1shall we submit a spec of pipeline, it will be helpful for the discussion15:51
TravTso different than the one you already have?15:51
lei-zh1I think it's more with pipeline architecture15:52
lei-zh1we didn't define that too much on the zaqar plugin15:52
TravTok, if you think it would be helpful to all of us, then please do15:52
*** xingchao has joined #openstack-meeting-415:52
lei-zh1ok15:52
*** pcaruana has quit IRC15:53
TravTyingjun: any topics you propose or would like to vote for? also do you know if you will be able to come or not?15:53
TravTi guess we still need to add david-lyle 's beer bash as an idea15:54
TravT;)15:54
*** numan_ has joined #openstack-meeting-415:54
yingjuni’ll come to the summit15:54
TravT\o/15:55
TravTthat's great!15:55
*** dstanek has left #openstack-meeting-415:55
TravTokay, well please add votes / ideas to the etherpad15:56
*** SimonChung has quit IRC15:56
TravTi'll arrange and upload to eventbrite on monday-ish15:56
TravT#topic open discussion15:57
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:57
TravTdoes anybody have any other topics?15:57
TravTsjmc7, have that bug ready for us to discuss?15:57
sjmc7https://bugs.launchpad.net/searchlight/+bug/156752515:58
openstackLaunchpad bug 1567525 in OpenStack Search (Searchlight) "port.create.end events are handled incorrectly by nova" [Critical,New]15:58
sjmc7in short - novca currently listens to port.create.end for reasons only i could have answered, 7 months ago15:58
*** sridhar_ram has joined #openstack-meeting-415:58
sjmc7which a) doesn’t make much sense and b) doesn’t handle them correctly. in light of the conversation we had i’m gonna remove the handler for backporting15:59
sjmc7and then see if we can handle port updates consistently for Newton until we can get the notifications fixed15:59
TravTokay, i'll look at it in detail.15:59
*** jmccrory_ has joined #openstack-meeting-415:59
*** automagically has joined #openstack-meeting-416:00
*** eil397 has joined #openstack-meeting-416:00
TravTtime is up for us16:00
TravTthanks everybody16:00
*** minwang2 has quit IRC16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Apr  7 16:00:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-04-07-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-04-07-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-04-07-15.01.log.html16:00
*** lakshmiS_ has left #openstack-meeting-416:00
*** lei-zh1 has left #openstack-meeting-416:01
*** RickA-HP has left #openstack-meeting-416:01
odyssey4me#startmeeting OpenStack-Ansible16:01
openstackMeeting started Thu Apr  7 16:01:45 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack-Ansible)"16:01
openstackThe meeting name has been set to 'openstack_ansible'16:01
odyssey4me#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack-Ansible)"16:01
*** mgariepy has joined #openstack-meeting-416:01
*** yingjun has left #openstack-meeting-416:02
*** javeriak has joined #openstack-meeting-416:02
*** sjmc7 has left #openstack-meeting-416:02
*** armax has quit IRC16:02
spotz\o/16:02
v1k0d3no/16:02
odyssey4me#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:02
*** armax has joined #openstack-meeting-416:02
eil397\o16:02
*** evrardjp has joined #openstack-meeting-416:02
jmccrory_o/16:03
*** basilAB has joined #openstack-meeting-416:03
evrardjphi16:03
*** automagically has quit IRC16:03
*** dave-mccowan has joined #openstack-meeting-416:03
*** automagically has joined #openstack-meeting-416:04
*** mbound_ has quit IRC16:04
*** angdraug has joined #openstack-meeting-416:04
*** julim has quit IRC16:05
* mhayden woots16:06
*** mattt has joined #openstack-meeting-416:06
*** yamamoto has quit IRC16:06
*** vtech has quit IRC16:07
*** annegent_ has joined #openstack-meeting-416:08
*** yamahata has joined #openstack-meeting-416:08
*** prometheanfire has joined #openstack-meeting-416:08
*** vtech has joined #openstack-meeting-416:08
odyssey4meAlright, we had no action items from last week so let's move to discussion topics.16:08
odyssey4me#topic Release notes in the IRR's16:08
*** openstack changes topic to "Release notes in the IRR's (Meeting topic: OpenStack-Ansible)"16:08
odyssey4mepalendae any updates?16:08
palendaeNope, been working on testing liberty upgrades all week16:08
odyssey4mealright, let me at least set an action item to instrument all the repositories for release notes16:09
odyssey4me#action odyssey4me to instrument all repositories for release notes16:09
*** zenoway has quit IRC16:09
odyssey4medo you need help with anything or would you like to raise anything related to the topic?16:10
*** zenoway has joined #openstack-meeting-416:10
*** vtech has quit IRC16:10
palendaeI don't have much to raise at the moment16:11
*** bobh_ has quit IRC16:11
odyssey4meok, we'll move on then16:11
odyssey4me#topic Newton Summit Planning16:11
*** openstack changes topic to "Newton Summit Planning (Meeting topic: OpenStack-Ansible)"16:11
*** zenoway has quit IRC16:11
*** zenoway has joined #openstack-meeting-416:11
odyssey4meThe schedule is up. I'm busy populating the details into it. It should be done early next week.16:12
odyssey4meI'll put a link to the filtered schedule up asap.16:12
odyssey4meDoes anyone have any summit related questions or comments?16:12
matttany way for those of us not at the summit to participate in anything?16:13
evrardjpgood question16:13
spotzI wonder if we could stream via vidyo on a laptop?16:13
*** unicell has quit IRC16:13
odyssey4mewell, we did try that at the mid-cycle and it wasn't great16:14
matttyeah you don't want it to distract from the in-person stuff as that time is precious, but if there is a mechanism it'd be great for those of us not there to join in on16:14
spotzodyssey4me I need to see my whole schedule but would like to make the doc sessions, any way to coordinate?16:14
odyssey4mealso we don't really have the same facilities available at the summit16:14
cloudnullo/16:14
spotzodyssey4me And it depends on network:(16:15
matttyeah if it's a hurdle then i wouldn't worry about it16:15
*** unicell has joined #openstack-meeting-416:15
odyssey4meso I think the best way to facilitate is to work through each topic's etherpad beforehand and discuss with anyone's who's going so that your views are well represented16:15
cloudnullodyssey4me: maybe we can do it w/ hangouts live + IRC16:15
*** zenoway has quit IRC16:15
cloudnullre: remote participation16:15
odyssey4meThe sessions are 40m so there's not even much time to try and use IRC to discuss, but we can try and ensure that some people are around on IRC and can therefore interact with anyone who's around16:16
*** zenoway has joined #openstack-meeting-416:16
matttodyssey4me: fair enough16:16
evrardjpirc isn't gonna work I think16:16
odyssey4meThe session times due to time zone differences will also make it a bit hard for anyone outside of the US to participate16:17
odyssey4me#action odyssey4me to complete uploading session details and publish a link for review16:17
evrardjpI agree with odyssey4me : let's prepare beforehand16:17
odyssey4mefor now the session list is https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-27&summit_types=2&tags=354216:17
odyssey4mealthough I see that some other stray sessions are in the list - not sure what's going on there16:17
odyssey4methat also seems to be missing some sessions16:18
stevelleas much as possible, having an outline and related reading items linked in the etherpads for each session seems important so folks can choose sessions and prepare to contribute in them16:18
mhaydenmattt: i could bring a better quality webcam to the summit and try to use it16:18
odyssey4meaha, this is better: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=OpenStackAnsible16:19
matttmhayden: sounds like it may not be worth it, and you don't want in-person time wasted fiddling w/ cams, networks, etc.16:19
spotzfishbowl goes right up to my session but I'll come for the start16:20
mhaydenmattt: i'll do it for you, though16:20
matttmhayden: you da bayst16:20
odyssey4meyeah, what stevelle said - please ensure that you prepare yourself for each session based on the outline in the session details16:20
*** zenoway has quit IRC16:20
odyssey4meeveryone needs to come with ideas and ideally PoC patches prepared16:20
odyssey4mewith the limited time for each session we need to try and make the most of the in-person time16:21
spotzI need a clone on Wednesday:(16:21
odyssey4meI'm putting them in the order we decided on here: https://etherpad.openstack.org/p/openstack-ansible-newton-summit16:22
evrardjpspotz only one ?16:22
odyssey4mecan anyone see any specific clashes with other sessions that means we should switch things around a bit?16:22
spotzevrardjp Just one so far16:22
*** avarner_ is now known as avarner16:22
*** doonhammer has joined #openstack-meeting-416:22
stevelleI would like to ask we consider moving dynamic inventory earlier16:22
odyssey4meyeah, I thought about that - maybe the first session on Wednesday?16:23
*** ddieterly is now known as ddieterly[away]16:23
stevellethat works16:23
odyssey4memaybe switch it up with the role documentation session?16:24
stevellethe 9:50 slot is ideal for me, personally16:24
stevelleto do inventory16:24
spotzJust don't put docs middle of the day on Wednesday and I'll make it work16:24
odyssey4meah, I meant the first on Thu - not Wed16:25
stevelleany slot thurs before lunch works16:25
odyssey4mespotz the suggested time for the docs session is 4:30-5:10 or the later one16:25
odyssey4me(on Wed)16:26
spotzThat'll work, I can do video's of the hands-ons I wanted to go to but can't miss the session I'm running:)16:26
*** TravT has left #openstack-meeting-416:26
odyssey4mespotz which works better - the 4:30-5:10 or the 5:20-6:00?16:28
mhaydeni'm good with either of those docs-wise16:28
*** daneyon_ has quit IRC16:28
spotzodyssey4me Either will work:)16:29
*** daneyon has joined #openstack-meeting-416:29
*** bpokorny has joined #openstack-meeting-416:29
odyssey4meok, I'll put some thought into the demands of the other sessions and put a suggested schedule down16:29
odyssey4meanything else from anyone?16:30
spotzappreciate it odyssey4me!16:30
*** unicell has quit IRC16:31
odyssey4me#topic Release Planning and Decisions16:31
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: OpenStack-Ansible)"16:31
*** minwang2 has joined #openstack-meeting-416:31
*** sridhar_ram has quit IRC16:32
*** scsnow has joined #openstack-meeting-416:32
odyssey4meso due to our current project tagging, we didn't get the chance to go through a release candidate process - so Mitaka is effectively released16:32
odyssey4meplease keep testing to identify any bugs\16:32
spotzSo we're bug fixing and newton?16:33
odyssey4mealso keep a lookout for backports or patches to the stable/mitaka branch - I expect that we'll be doing quite a few of them all the way up to Newton-116:33
odyssey4meI've applied to change the project tag to follow the releases and will discuss what that means at the summit.16:34
*** xingchao has quit IRC16:34
odyssey4mespotz yeah, master is on Newton already16:34
spotznice:)16:34
odyssey4mewe have some patches that need herding or votes: https://review.openstack.org/#/q/project:%255Eopenstack/openstack-ansible.*+status:open+branch:stable/mitaka16:34
*** egoust has joined #openstack-meeting-416:35
odyssey4meit looks like the upstream projects are pretty much done at RC3, but I'd like to get those patches merged so that we can tag 13.0.1 as the finalised release including any additional role patches needed16:36
*** david-lyle has quit IRC16:36
stevellelooks like we have some gate instability issues right now too16:37
odyssey4mestevelle yeah, some of the providers are quite problematic although I haven't been digging into those failures in detail16:37
odyssey4meif you have a gap to do so to try and figure out whether there are other problems then that'd be appreciated16:38
evrardjplet me guess, ovh apt issues16:38
*** spzala has quit IRC16:38
odyssey4meevrardjp for the most part we're using the infra provided apt/pypi/pip repositories which are localised per provider/region so we shouldn't be16:39
odyssey4meif that hasn't been done in the role, then that's a fix-up needed for sure16:39
*** spzala has joined #openstack-meeting-416:39
evrardjpindeed, it's not what I see on the first ones16:39
odyssey4meI think that the galera extra download bits is hurting the galera_server role success16:39
stevelle^16:39
odyssey4methose aren't mirrored, so we either need to figure out something better or make another plan16:40
stevelleso many galera_server timeouts, but that reflects something delaying those tests16:40
evrardjppkg-query: package 'mariadb-galera-server-10.0' is not installed and no information is available16:41
stevelleIt seems like there are a few issues in that role we might identify16:41
*** dslevin1 has quit IRC16:41
*** LouisF has joined #openstack-meeting-416:41
*** vishnoianil has quit IRC16:41
odyssey4meyeah, that role does a lot of things - we might have to pare it down a little or figure out another way to test what it's testing16:41
evrardjpthat's a discussion we can have outside the meeting right?16:42
odyssey4mebut ideally I'd like to identify real problems and resolve them16:42
*** eil397 has quit IRC16:42
odyssey4meyeah, we can do that16:42
*** eil397 has joined #openstack-meeting-416:42
odyssey4meare there any issues with the Kilo/Liberty branches that should prevent a fresh tag?16:43
*** spzala has quit IRC16:43
*** javeriak_ has joined #openstack-meeting-416:44
*** georgewang has joined #openstack-meeting-416:44
odyssey4meit looks like https://review.openstack.org/301283 / https://review.openstack.org/302333 / https://review.openstack.org/280844 need review for kilo16:44
*** spzala has joined #openstack-meeting-416:45
odyssey4meand there are some patches in review for liberty: https://review.openstack.org/#/q/project:%255Eopenstack/openstack-ansible.*+status:open+branch:liberty16:45
*** javeriak has quit IRC16:45
*** ddieterly[away] is now known as ddieterly16:46
*** galstrom is now known as galstrom_zzz16:46
odyssey4meas the release team is pretty much on skeleton crew until after the summit, I'm not sure that our tags will be done - but I'll ask16:47
odyssey4me#topic Open discussion16:47
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack-Ansible)"16:47
odyssey4mealright - we have 10 mins for open discussion16:47
odyssey4meanyone got anything to discuss or raise?16:47
*** spzala has quit IRC16:47
*** spzala has joined #openstack-meeting-416:48
*** annegent_ has quit IRC16:49
*** annegentle has joined #openstack-meeting-416:49
evrardjpnothing right now, except thanks for the meeting16:51
odyssey4mealright, as there's nothing else - thank you all for attending!16:52
odyssey4me#endmeeting16:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:53
openstackMeeting ended Thu Apr  7 16:53:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-04-07-16.01.html16:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-04-07-16.01.txt16:53
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-04-07-16.01.log.html16:53
*** spzala has quit IRC16:53
*** julim has joined #openstack-meeting-416:53
*** prometheanfire has left #openstack-meeting-416:55
*** stevelle has left #openstack-meeting-416:55
*** cloudtrainme has quit IRC16:57
*** Cathy__ has joined #openstack-meeting-416:57
*** hdaniel has quit IRC16:58
*** singlethink has joined #openstack-meeting-416:58
*** angdraug has quit IRC16:58
*** mohankumar__ has quit IRC16:59
*** mohankumar__ has joined #openstack-meeting-416:59
Cathy__#startmeeting service_chaining17:00
vikramhi17:00
openstackMeeting started Thu Apr  7 17:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is Cathy__. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
pcarverHello17:00
georgewanghello17:00
Cathy__hi everyone17:00
*** s3wong has joined #openstack-meeting-417:00
s3wonghello17:01
scsnowhi17:01
LouisFhi17:01
Cathy__s3wong: scsnow LouisF hi17:01
Cathy__let's start17:01
s3wongCathy__: your nic keeps on changing :-)17:01
doonhammerHi17:01
Cathy__doonhammer: hi17:01
LouisFdoonhammer: hi17:02
*** csun has joined #openstack-meeting-417:02
mohankumar__hi17:02
Cathy__s3wong: really? I don't know why17:02
vikramCathy__: register a nick for you17:02
raofeihi everyone17:02
*** neelashah has joined #openstack-meeting-417:02
Cathy__vikram: OK, will do17:03
*** automagically has left #openstack-meeting-417:03
Cathy__hi raofei17:03
Cathy__#topic Source port specification in the FC17:03
*** openstack changes topic to "Source port specification in the FC (Meeting topic: service_chaining)"17:03
*** iyamahat has joined #openstack-meeting-417:03
*** vishnoianil has joined #openstack-meeting-417:04
Cathy__Let me try to explain why we need the source port in the SFC FC specification17:04
Cathy__hi iyamahat vishnoianil17:04
vishnoianilCathy__, hi17:04
*** SimonChung has joined #openstack-meeting-417:05
*** azbiswas has joined #openstack-meeting-417:05
Cathy__With the source port specified, we know where to instantiate the FC17:05
iyamahatCathy__, hi17:06
*** yamahata has quit IRC17:06
*** david-lyle has joined #openstack-meeting-417:06
vikramCathy__: Why we can't put it as a part of the chain17:06
Cathy__That will enhance the performance17:06
vikramCathy__: I mean in service_chain_param17:06
Cathy__vikram: I guess we can consider that17:07
vikramCathy__: Doing so we can keep FC generic17:07
*** yamamoto has joined #openstack-meeting-417:07
LouisFvikram: it is used to select traffic entering the chain so the FC is the right place to have  it17:07
*** pcaruana has joined #openstack-meeting-417:08
vikramLouisF: Agreed.. but this kills generic design for FC17:08
*** ddieterly is now known as ddieterly[away]17:08
mohankumar__vikram: +117:08
vishnoianilSFC spec do have source port as a match attribute for classifier, isn't it?17:08
Cathy__raofei: pcarver s3wong what's your thought?17:08
LouisFthe FC will evolve and have other parameters such as DSCP, vlan-id etc17:08
Cathy__vishnoianil: yes17:08
vikramLouisF: The problem here is we are making Src port as mandatory17:09
pcarverCathy__: I'm definitely concerned about putting SFC specific info in the FC because we would like the FC to be generic across things other than SFC17:09
s3wongCathy__: source port as in Neutron port? I don't even know FC has a networking location association...17:09
Cathy__In current way, the user can specify that all traffic coming from a source port will go through the chain17:09
LouisFthere was discussion on a common FC some months ago but that work has not progressed17:09
trozetstupid question, does FC == Flow Classifier?17:10
LouisFpcarver: a port is not really SFC specific - is likely can be  used by other features such as qos17:10
pcarverAlso, we need to maintain a clean separation between the abstract design of the API and the particular needs of one implementation. So we should ask whether the source port is required for all SFC drivers or just the OvS agent based one.17:10
s3wongtrozet: yes :-)17:10
vikramtrozet:bingo17:10
vishnoianilCathy__, sorry i missed the initial context, are we talking about source port (L4 ) or "Ingress Port" ?17:10
*** unicell has joined #openstack-meeting-417:10
*** david-lyle has quit IRC17:11
vikramsource port17:11
Cathy__since the source port can be used as a FC rule to classify the traffic, I am not sure if it is appropriate to move it out of the FC17:11
s3wongvishnoianil: yeah, that was my question as well :-)17:11
pcarverI have the same question as vishnoianil17:11
LouisFvishnoianil: neutron src port17:11
Cathy__vishnoianil: s3wong source port in the FC17:11
pcarverI'm assuming we're talking Neutron port where VM attaches17:11
pcarvernot TCP/UDP port17:11
vikrampcarver: +117:11
LouisFpcarver: yes17:11
s3wongpcarver: yes, that's what I was thinking17:11
vikramCathy__: I didn't get your reasoning17:12
trozetI think the issue is when you want to SFC to operate at a service/admin role, you want to be able to classify based on traffic from specific neutron networks or ports17:12
pcarverI understand that for the OvS based implementation we need to know where to put the flow rules, but I'm not sure that's a generic SFC API requirement17:12
Cathy__pcarver: yes, but it is not the source port of a SF VM, it is a source port to identify traffic coming to the chain17:12
*** salv-orlando has joined #openstack-meeting-417:12
s3wongCathy__: wound't ingress network port part of FC?17:12
vikramCathy__: since the source port can be used as a FC rule to classify the traffic, I am not sure if it is appropriate to move it out of the FC : My proposal is not to mandate this field17:12
s3wong* wouldn't17:12
vishnoianili think with that, it gets bit vague, because "ingress port" basically considered as a L0 match criteria17:12
Cathy__trozet: yes17:12
trozetCathy__: so with RBAC, doesn't that enable this type of behavior?17:13
pcarverThinking in terms of physical switches and firewalls for a moment. Normally an ACL or ruleset is defined and then it is applied to one or more (physical) ports17:13
*** ddieterly[away] is now known as ddieterly17:13
LouisFvishnoianil: yes it is a match on packet metadata not packet contents17:13
Cathy__s3wong: it is the ingress network port of a traffic flow which is currently part of the FC.17:13
*** annegentle has quit IRC17:14
s3wongvikram: as you said, given that ingress Neutron port should be part of classification, shouldn't it be part of FC? Why would you opposed to including it as part of FC?17:14
*** MarkAtwood has joined #openstack-meeting-417:14
*** annegentle has joined #openstack-meeting-417:14
mohankumar__i believe src port made mandatory to check does traffic coming from same compute host or not17:14
LouisFthere are use cases where all traffic to/from a VM port must be steered into a SFC17:14
vikrams3wong: classification can be done for a stream of traffic coming from / to a neutron src17:14
*** annegentle has quit IRC17:15
trozetshouldn't we also include neutron network? and not just VM port here?17:15
Cathy__vishnoianil: our matching criteria is very large, can be up to L717:15
*** annegentle has joined #openstack-meeting-417:15
vikramtrozet: initial design is chaining ports17:15
*** salv-orlando has quit IRC17:15
trozetthere are cases where a service operator wants all tenant traffic from a specific network to go through an admin chain before going to an external network, it makes sense to define one chain there in the admin space and not for every tenant17:16
vishnoianilCathy__, then in my opinion it make sense to me, i don' think it's breaking generic nature of the API17:16
*** yamamoto has quit IRC17:16
vikramtrozet: which address all the scenarios17:16
trozetvikram: i'm not talking about chaining, im talking about classification17:16
*** baoli has quit IRC17:16
vikramtrozet: Ok.. so you mean adding a param net in the FC?17:16
trozetvikram: yeah network and ports both in FC17:17
*** baoli has joined #openstack-meeting-417:17
*** fitoduarte has joined #openstack-meeting-417:17
*** david-lyle has joined #openstack-meeting-417:17
LouisFtrozet: ports already exist in the FC17:17
Cathy__trozet: I understand your point. Yes that is a use case we need to cover. Could one or a group of source ports represent that network whose traffic go through the chain?17:17
vikramtrozet: anyways it can be done.. if we already support ports.. at the end nets are collection of ports17:17
trozetvikram: of course one would only be able ot match on network/ports outside of his tenant if he had proper admin rights given by RBAC I think17:17
vishnoianilCathy__, LouisF i think classification in general should provide all the attribute on which you can steer the traffic, except it enforces which attribute to be made mandatory or enforces any dependency between the matching attributes17:17
*** spzala has joined #openstack-meeting-417:17
s3wongtrozet: I got to be honest, on the plumbing side, I don't know how to render 'network' into something like OVS flow table... subnet? VLAN?17:17
Cathy__trozet: If we can use existing way to cover other scenarios, I would rather not add more and more primitives in the FC17:18
LouisFs3wong: +117:18
trozets3wong: in ODL its matched on in flows17:18
trozets3wong: in OVS17:18
vikramvishnoianil, I am not suggesting to remove the src port attribute17:18
vishnoianils3wong, ideally it should be associated subnet, because it's lower level construct then network17:18
trozets3wong: i think its part of hte tunnel ID for vxlan, but need to confirm17:19
vishnoianilnetwork has one to many associativity with subnet17:19
vikramvishnoianil, Just not to mandate it17:19
Cathy__s3wong: good point17:19
s3wongCathy__, vikram. LouisF: how about this then? If a source port is specified in the FC, we know where to put it; if not, all traffic is subjected to classification and matching?17:19
vishnoianilvikram, okay, i think mandating it might create a problem17:19
Cathy__s3wong: that is existing way:-)17:20
*** fitoduarte has quit IRC17:20
Cathy__OK, so now the issue is "mandatory" or not17:20
vikramvishnoianil, Yup..17:20
vikramCathy__: +117:20
s3wongCathy__: I see --- how the discussion is much more clear :-)17:20
s3wong* now17:20
vishnoianilCathy__, "ingress port" actually scope your traffic to the specific port, so any classification you will specify after specify ingress port, will be scoped to that ingress port only17:21
LouisFit can made optional in the FC with the caveat that in certain implementations there may be performance impact17:21
Cathy__raofei: I remember you have some point on this.17:21
vikramLouisF: For this one can provide this info using service_chainparam17:21
s3wongCathy__: in that context, I actually side with vikram here... we want the FC to be flexible enough to be specified as "all traffic from all port should be matched against this"17:21
vikramLouisF: For this one can provide this info using service_chain_parameter17:21
*** spzala has quit IRC17:22
vishnoianilso if make ingress port mandatory, to specify classification at switch level you will have to cater traffic each port basis and that can lead to flow explosion at the device level :)17:22
s3wongLouisF: +1, exactly!17:22
trozetso from reading this discussion, matching on port is already supported, the discussion is whether to make it mandatory or not?17:22
Cathy__trozet: yes17:23
LouisFtrozet: correct17:23
vikramtrozet: +100017:23
s3wongtrozet: yep, my understanding as well (finally, after some long discussions) :-)17:23
*** baoli has quit IRC17:23
vikram:(17:23
trozetwhy would you want to make it mandatory?17:23
trozetthat doesn't make much sense to me17:23
vishnoianiltrozet, In my personal opinion, that's not good idea17:23
Cathy__there is a reason we later made it mandatory. I am still thinking about why.17:23
*** david-lyle has quit IRC17:23
vikramCathy__: IIRC, it was for identifying the flow on the other compute node17:24
trozetCathy__: was that simply because then you know where to place the classifier flow?17:24
Cathy__trozet: no17:24
*** woodard has quit IRC17:24
LouisFit is currently mandatory, if it is made optional then the OVS rules for matching must be installed on all OVS switches17:24
Cathy__vikram: yes, something like that. I remember I described the scenario in one of our previous IRC meeting.17:25
vikramCathy__: If the chain span across multiple nodes then we need to identify th flow17:25
LouisFtrozet: +117:25
mohankumar__Cathy__ , i remember , to find Compute node belongs to same tenent nw or different tenent (or OVS rather )17:25
vikramcoming from chain / it's normal packet17:25
trozetLouisF: yeah they should be on every OVS if not specific to a port17:25
LouisFtrozet: yep17:25
s3wongLouisF: which probably is the user intent in this context (that the flow rules should be matched on all OVS switches)17:26
*** iberezovskiy is now known as iberezovskiy_17:26
LouisFs3wong: yes17:26
Cathy__So if the same flow comes back to SF VMs which happen to run on the same computer node, we need a way to distinguish this since depending on where the flow comes, the next hop is different.17:27
trozetso I guess the question is, who in the room wants to keep it mandatory?17:27
vikramtrozet: +1000.. and where to mandate this17:27
vikramMy proposal is we can pass the src port info "[--chain-parameters <chain-parameter>]" here, if needed17:29
Cathy__If I remember correctly, we decided to use the source port as a way to distinguish the traffic entering the chain from the traffic that loop back to the compute node17:29
*** banix has joined #openstack-meeting-417:30
s3wongCathy__: I think it is perfectly fine if we happen to render the chain / FC into flow rules with source port context --- so that is something we (drivers) can do, without subjecting users to specify a source port17:30
*** sambetts is now known as sambetts|afk17:30
vikrams3wong: I didn't get you17:31
trozetCathy__: yeah if you have to specify port in classifier so you know that a return packet to OVS shouldnt be reclassified and is still part of the chain--that seems to me like you are fixing a chain problem by restricting the classifier17:31
trozetCathy__: the chain flows should know where the packet is in the chain, and not restrict the classifier IMO17:32
s3wongvikram, Cathy__: in your example, say SF1->SF2->SF3, a FC matches traffic to SF117:32
Cathy__trozet: could you calrify what you mean by "chain flows should know where the packet is in the chain"?17:32
s3wongvikram, Cathy__: if say SF3 happens to be in the same node as SF1, we can render a source port on the return traffic from SF2 -> SF3 with the same flow rules17:33
LouisFtrozet: return packets from the egress port of SF are re-classified on the current design17:34
raofeiyes, s3wrong, for one scenario, service path is sf1->sf2->sf1->sf3, if we don't assign the source port,  it's difficult to distinguish the return the traffic.17:34
Cathy__trozet: when the flow loops back to the same vSwitch that the traffic originally enters the chain, how does the vSwitch determine the different next hop?17:34
trozetCathy__: well NSH solves that problem17:34
LouisFthe ovs driver/agent acts like a sfc proxy device17:34
Cathy__trozet: yes17:35
vishnoianilCathy__, LouisF trozet , are we talking of this specific problem, when we don't use NSH encap?17:35
vikramtrozet: ;) Reality is tough17:35
Cathy__trozet: if we use NSH, we can use the service_index to solve it17:35
trozetCathy__: I'm not as familiar with how you are doing SFC in networking-sfc17:35
*** spzala has joined #openstack-meeting-417:35
s3wongvishnoianil: technically OVS has no NSH support17:35
vikramvishnoianil: yes17:35
s3wongvishnoianil: independently of what ODL SFC is using :-)17:35
mohankumar__vishnoianil , its not included to ovs officially17:35
vishnoianils3wong, agree, but in ODL we do run OVS with NSH (that's not official version)17:36
*** fitoduarte has joined #openstack-meeting-417:36
Cathy__trozet: when we proposed the SCH spec which merged with NSH, we considered this case and service_index can be used for solving it17:36
*** ddieterly is now known as ddieterly[away]17:36
LouisFraofei: but the driver/agent matches on the egress port so is can distinguish return traffic from that originating from the source port17:36
trozets3wong: :) let's not go down that road... it will be in a few months17:36
vishnoianils3wong, vishnoianil mohankumar__ agree17:36
s3wongraofei: in that case, how would user specify source port for SF1->SF2 vs SF1->SF3?17:36
LouisFvishnoianil: does odl support nsh-aware SFs?17:36
vikramTime is really draining fast ;)17:37
*** pvaneck has joined #openstack-meeting-417:37
trozetCathy__: so in current networking-sfc implementation, how do you distinguish a packet that is part of a chain versus regular tenant traffic?17:37
vishnoianilLouisF, ODL can support NSH, but having SF NSH aware is kind of out of scope for ODL17:37
vikramtrozet: https://github.com/openstack/networking-sfc/blob/master/doc/source/ovs_driver_and_agent_workflow.rst17:38
Cathy__trozet: through the FC. Not sure if I understand your question properly17:38
s3wongvikram: the beauty of explaining things via IRC ... a whiteboard session would have explained the problem in 10 minutes :-)17:38
LouisFvishnoianil: so the odl driver for sfc must do re-classification of packets returned from each SF17:38
Cathy__If OVS officially supports NSH, then we do not need this "mandatory".17:38
vikrams3wong :)17:38
vishnoianils3wong, Cathy__ trozet LouisF , i think won't it be good if we take this topic to mailing list, probably that will bring us to conclusion faster :), just an opinion17:39
LouisFCathy__: it depends on  whether the SF is nsh-aware and the need to do reclassifcation on return traffic17:39
*** spzala has quit IRC17:39
Cathy__trozet: Do you mean that OVS will officially support NSH in a few months? About what time will NSH be merged into OVS officially?17:39
vishnoianilCathy__, Yes, 2.6 should have support for NSH17:39
vikramCathy__: My opinion is  we should resolve the issue by disturbing a generic API17:39
Cathy__vishnoianil: great! when is that?17:40
s3wongvishnoianil: really? was it finally merged? I've seen the outstanding patch there forever...17:40
raofeiagree with Louis17:40
*** degorenko is now known as _degorenko|afk17:40
LouisFvikram: not sure what you mean17:40
vishnoianilvikram, do you mean "by NOT disturbing" ?17:40
LouisFvishnoianil: who is doing that work?17:41
vikramvishnoianil, LouisF: Not imposing a restriction on a generic API17:41
*** vtech has joined #openstack-meeting-417:41
*** ihrachys has quit IRC17:41
Cathy__Maybe we can put this in the back burner for now and if we can get NSH support soon, then we will remove the "mandatory" at that "soon" time.17:41
vikramwhat we are having today by making the src port as a mandatory field17:41
trozetCathy__: ok now I see you are using the MPLS header to track if its part of the chain17:41
*** vtech has quit IRC17:41
LouisFvikram: you mean by making the src port mandatory in the FC?17:42
vikramtrozet: You are fast :)17:42
Cathy__trozet: yes, that is a place holder for future NSH header17:42
trozetCathy__: so then what loop packet are we talking about that gets accidentally reclassified?17:42
*** vtech has joined #openstack-meeting-417:42
trozetCathy__: egress from the chain?17:42
vikramLouisF: I am half sleepy now.. ;) I mean not to make it mandatory17:42
vikramLouisF: It's time to bed :(17:42
LouisFvikram: thanks for joining17:43
Cathy__trozet: not egress from the chain. Think about if all SF VM runs on the same Computer Node (vSwitch)17:43
mohankumar__Cathy__ : i agree , to remove mandatory once we ve NSH suppport17:43
vikramLouisF: Please forgive if I sound stupid today .. Tiering day17:43
Cathy__mohankumar__: Ok, good.17:44
Cathy__vikram: mohankumar__ thanks for joining at your mid night!17:44
vikramCathy__: Does ODL has any issues ?17:44
LouisFtrozet: the end-of-chain case is ok because the ovs driver/agent reclassifies on the egress port of the last SF17:44
Cathy__raofei: Thanks to you too at your 1am time !!!17:44
vikramCathy__: Does ODL has any issues if we continu src port as mandatory in the FC API?17:45
trozetCathy__: yeah so if you have multiple SF on the same node, when the packet from SF1-->OVS-->SF2 that is where you are worried about a reclassification problem if you dont specify a port?17:45
LouisFraofei: +100017:45
Cathy__vikram: not that I am aware of17:45
vikramtrozet, vishnoianil, any inputs?17:45
trozetvikram: yeah it's not good17:46
LouisFvikram: is it an issue for the onos driver?17:46
vikrami don't remeber for ONOS17:46
Cathy__so SourcePort->OVS->SF1->OVS->SF217:46
vikrambut I remember we were able to do it without src port as well17:47
trozetvirkam: then if you want to match on tcp port 80 traffic, you have to create N number of classifiers for every port, or you just ignore any match port criteria from networking-sfc in the ODL driver17:47
Cathy__If no source port, then FC rules with no SourcePort->OVS->SF1->OVS->SF217:47
trozetCathy__: so your ingress packet from SF1, dont you have flows tha match ont eh MPLS header to decide if the packet is still part of the chain?17:48
vikramtrozet: Agreed.. but frankly speaking classifier should be deployed a separate node and all the traffic should pass through it17:48
Cathy__how about this? I will send out a diagram describing this scenario. We have spent enough time on this discussion:-) I think a diagram will explain the problem easier.17:49
LouisFvikram: that depends on the usage scenario - for mobile Gi LAN that would be correct, but the DC is different17:49
s3wongtrozet: yes, exactly what I was thinking... the match from unencapulated packet to SF1 and the second time it hits SF1 should be different17:50
vikramLouisF: Yes.. I realized17:50
*** spzala has joined #openstack-meeting-417:50
pcarvervikram: Can't assume traffic will be small enough to all pass through a single node17:50
vikrampcarver: make sense..17:50
*** mgariepy has left #openstack-meeting-417:50
vishnoianiltrozet, SF on same SFF problem, why we can't solve that problem using NXM-REG?17:50
vikramReally learning SFC now ;)17:50
trozetCathy__: so the issue is you dont encap the tunnel header if you are on the same OVS node, so you don't know the packet is part of the chain?17:51
vikramtrozet: for your question, yes ONOS currently installs flow for N ports separately17:51
Cathy__trozet: yes, no need for tunnel header since it will not go through the tunnel17:51
LouisFvishnoianil: for multiple SFs on the same SFF (OVS) it is not a problem beacuse the rules will match on the egress port of each SF17:51
*** SumitNaiksatam has joined #openstack-meeting-417:51
*** davidsha has joined #openstack-meeting-417:51
vishnoianilLouisF, okay17:52
vishnoianilLouisF, reading trough chat with your max speed,sometime confuses you :P17:52
trozetvishnoianil: yeah maybe im sure shague would have a good fix for this17:52
vishnoianiltrozet, yeah17:53
Cathy__vishnoianil: it will match on the egress port of each SF, so we need a source port to distinguish traffic on the source port from traffic on the egress port of each SF17:53
LouisFtrozet: it would be good to find out how odl handles the non-nsh-aware SF17:53
*** mfedosin has quit IRC17:53
Cathy__with NSH support, this issue is gone.17:54
LouisFCathy__: agree, for nsh-aware SFs17:54
trozetCathy__: so cant you match on ingress port for the chain, rather than ingress port with the classifier?17:54
trozetCathy__: if you just make the chain rule match on SF1 in_port17:55
trozetCathy__: but then what if that VNF is part of multiple chains, how do you know what is the next hop?17:55
trozetsince you have no header17:55
LouisFtrozet: the "ingress port" for the chain is the ingress port of the FC17:55
trozetLouisF: i mean in_port from the previous VNF in the chain17:55
*** david-lyle has joined #openstack-meeting-417:56
*** david-lyle has quit IRC17:56
s3wongtrozet: even if we have to reclassify, that is OK --- as long as the rules are replicated with the ingress port added ... I still think driver is a right place to do this, as opposed to having user specify a port17:56
Cathy__trozet: we still need to distinguish the traffic on the source port which is before the SF1, from the traffic on SF1 in_port17:57
trozets3wong: yeah thats a good point17:57
LouisFtrozet: by egress port from a SF port-pair would be the OVS in_port17:57
trozets3wong: just making the OVS networking-sfc driver apply the classifier to each port17:57
Cathy__trozet: since all the traffic is handled by the same Compute Node and vSwitch17:57
*** david-lyle has joined #openstack-meeting-417:58
s3wongCathy__: traffic into chain is FC, traffic to SF1 is in_port SF1 + FC, which the driver needs to be smart enough to add... does that work?17:58
LouisFtrozet: the VNF re-classify will discriminate the chains when multiple chains use that VNF17:59
Cathy__s3wong: that seems a good way. let me think about it more17:59
Cathy__Hi folks, time is up.17:59
scsnowI have a question regarding currect SFC implemenation in OVS driver. Where can I ask it?17:59
vikram:)17:59
s3wonggood discussion!17:59
Cathy__Let's continue the discussion in next meeting. We only cover one topic today:-)17:59
LouisFscsnow: here17:59
vikramscsnow: Mailing List17:59
Cathy__scsnow: could you send your Q via email17:59
Cathy__Ok, by everyone18:00
vikrambye18:00
s3wongbye18:00
mohankumar__bye18:00
scsnowI was waiting for open discussion topic here )18:00
Cathy__scsnow: :-)18:00
vikramscsnow :)18:00
doonhammerbye18:00
*** csun has left #openstack-meeting-418:00
Cathy__#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Apr  7 18:00:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
*** vikram has quit IRC18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-04-07-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-04-07-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2016/service_chaining.2016-04-07-17.00.log.html18:00
*** cloudtrainme has joined #openstack-meeting-418:01
*** egoust has quit IRC18:01
davidshaCathy__: Hey, I'm looking into inter operability between features using openflows, I'm planning on hosting a design session at the summit to discuss this if you're interested in attending?18:03
*** julim has quit IRC18:04
Cathy__sure. Could you send me the time and location via email? I have a talk on Thursday, as long as the time does not conflict.18:05
*** singlethink has quit IRC18:05
*** piet has quit IRC18:06
davidshaCathy__: Kk, there isn't any times yet but I'll let you know once I know.18:06
Cathy__davidsha: ok.18:07
Cathy__by now18:07
*** Cathy__ has quit IRC18:07
*** blahRus has quit IRC18:08
*** davidsha has quit IRC18:10
*** zenoway has joined #openstack-meeting-418:12
*** sridhar_ram has joined #openstack-meeting-418:14
*** annegentle has quit IRC18:16
*** annegentle has joined #openstack-meeting-418:16
*** zenoway has quit IRC18:16
*** javeriak_ has quit IRC18:17
*** jmccrory_ has quit IRC18:18
*** v1k0d3n has quit IRC18:19
*** cbits has joined #openstack-meeting-418:22
*** sdake_ has joined #openstack-meeting-418:26
*** sdake has quit IRC18:26
*** mohankumar__ has quit IRC18:26
*** paul-carlton1 has quit IRC18:29
*** zenoway has joined #openstack-meeting-418:30
*** s3wong has quit IRC18:32
*** salv-orlando has joined #openstack-meeting-418:32
*** ddieterly[away] has quit IRC18:36
*** doonhammer has quit IRC18:36
*** salv-orlando has quit IRC18:38
*** nihilifer has quit IRC18:39
*** spzala has quit IRC18:42
*** ddieterly has joined #openstack-meeting-418:42
*** sambetts|afk has quit IRC18:42
*** angdraug has joined #openstack-meeting-418:44
*** ddieterly is now known as ddieterly[away]18:44
*** spzala has joined #openstack-meeting-418:44
*** bobh_ has joined #openstack-meeting-418:46
*** sambetts has joined #openstack-meeting-418:46
*** automagically has joined #openstack-meeting-418:46
*** ddieterly[away] is now known as ddieterly18:46
*** doonhammer has joined #openstack-meeting-418:47
*** annegentle has quit IRC18:49
*** delattec has quit IRC18:49
*** njohnston has quit IRC18:49
*** annegentle has joined #openstack-meeting-418:50
*** bobh_ has quit IRC18:50
*** scsnow has quit IRC18:50
*** bobh_ has joined #openstack-meeting-418:50
*** spzala_ has joined #openstack-meeting-418:50
*** SumitNaiksatam has left #openstack-meeting-418:51
*** vtech has quit IRC18:51
*** bobh_ has quit IRC18:52
*** salv-orlando has joined #openstack-meeting-418:52
*** annegentle has quit IRC18:52
*** spzala has quit IRC18:53
*** spzala has joined #openstack-meeting-418:53
*** bobh_ has joined #openstack-meeting-418:54
*** mlima has joined #openstack-meeting-418:55
*** spzala_ has quit IRC18:55
*** neelashah has quit IRC18:56
*** neelashah has joined #openstack-meeting-418:56
*** spzala has quit IRC18:57
*** woodard has joined #openstack-meeting-418:59
*** sambetts has quit IRC19:00
*** ddieterly is now known as ddieterly[away]19:00
*** bobh_ has quit IRC19:00
*** salv-orlando has quit IRC19:01
*** emagana has joined #openstack-meeting-419:02
*** cbits has quit IRC19:03
*** GB21 has quit IRC19:03
*** cdelatte has joined #openstack-meeting-419:03
*** sambetts has joined #openstack-meeting-419:03
*** nikhil has quit IRC19:07
*** nikhil has joined #openstack-meeting-419:11
*** david-lyle_ has joined #openstack-meeting-419:13
*** salv-orlando has joined #openstack-meeting-419:14
*** vtech has joined #openstack-meeting-419:14
*** spzala has joined #openstack-meeting-419:15
*** david-lyle has quit IRC19:15
*** bobh_ has joined #openstack-meeting-419:16
*** cbits has joined #openstack-meeting-419:16
*** sigmavirus24 is now known as sigmavirus24_awa19:17
*** bobh_ has quit IRC19:17
*** iyamahat has quit IRC19:18
*** hdaniel has joined #openstack-meeting-419:18
*** Sukhdev has joined #openstack-meeting-419:18
*** david-lyle_ has quit IRC19:19
*** ddieterly[away] is now known as ddieterly19:21
*** bpokorny_ has joined #openstack-meeting-419:23
*** ihrachys has joined #openstack-meeting-419:24
*** bpokorny has quit IRC19:26
*** mfedosin has joined #openstack-meeting-419:28
*** david-lyle has joined #openstack-meeting-419:29
*** david-lyle has quit IRC19:31
*** david-lyle has joined #openstack-meeting-419:31
*** cdelatte has quit IRC19:31
*** minwang2 has quit IRC19:31
*** Jeffrey4l_ has joined #openstack-meeting-419:32
*** julim has joined #openstack-meeting-419:33
*** Jeffrey4l has quit IRC19:34
*** banix has quit IRC19:36
*** david-lyle has quit IRC19:37
*** cloudtrainme has quit IRC19:37
*** baoli has joined #openstack-meeting-419:39
*** bpokorny_ has quit IRC19:40
*** bpokorny has joined #openstack-meeting-419:41
*** iyamahat has joined #openstack-meeting-419:41
*** minwang2 has joined #openstack-meeting-419:42
*** mlima has left #openstack-meeting-419:47
*** rbak_ has joined #openstack-meeting-419:48
*** rbak has quit IRC19:51
*** bpokorny has quit IRC19:52
*** bpokorny has joined #openstack-meeting-419:53
*** alex_xu has quit IRC19:54
*** alex_xu has joined #openstack-meeting-419:55
*** yamahata has joined #openstack-meeting-420:00
*** hdaniel has quit IRC20:00
*** LouisF has quit IRC20:01
*** baoli has quit IRC20:03
*** baoli has joined #openstack-meeting-420:04
*** hdaniel has joined #openstack-meeting-420:05
*** cloudtrainme has joined #openstack-meeting-420:08
*** ddieterly is now known as ddieterly[away]20:10
*** mfedosin has quit IRC20:12
*** galstrom_zzz is now known as galstrom20:13
*** jed56 has quit IRC20:13
*** vishwanathj has quit IRC20:14
*** ddieterly[away] is now known as ddieterly20:15
*** bpokorny has quit IRC20:16
*** annegentle has joined #openstack-meeting-420:16
*** azbiswas has quit IRC20:20
*** sdake_ is now known as sdake20:23
*** rbak has joined #openstack-meeting-420:26
*** mfedosin has joined #openstack-meeting-420:27
*** rbak_ has quit IRC20:27
*** numan_ has quit IRC20:28
*** woodard has quit IRC20:32
*** vtech has quit IRC20:36
*** julim has quit IRC20:36
*** vtech has joined #openstack-meeting-420:38
*** spzala has quit IRC20:40
*** baoli has quit IRC20:41
*** hdaniel has quit IRC20:41
*** cdelatte has joined #openstack-meeting-420:41
*** baoli has joined #openstack-meeting-420:45
*** baoli_ has joined #openstack-meeting-420:46
*** vishwana_ has joined #openstack-meeting-420:47
*** Sukhdev has quit IRC20:47
*** ddieterly is now known as ddieterly[away]20:49
*** baoli has quit IRC20:50
*** mfedosin has quit IRC20:50
*** baoli_ has quit IRC20:50
*** baoli has joined #openstack-meeting-420:51
*** ddieterly[away] has quit IRC20:52
*** nihilifer has joined #openstack-meeting-420:54
*** rpjr__ has joined #openstack-meeting-420:56
*** david-lyle has joined #openstack-meeting-420:56
*** rpjr_ has quit IRC20:57
*** georgewang has quit IRC20:58
*** pcaruana has quit IRC21:01
*** bpokorny has joined #openstack-meeting-421:02
*** vishnoianil has quit IRC21:03
*** fitoduarte has quit IRC21:04
*** eil397 has quit IRC21:06
*** automagically has quit IRC21:08
*** thorst_ has quit IRC21:12
*** Devon has joined #openstack-meeting-421:14
*** Devon has left #openstack-meeting-421:14
*** shakamunyi has joined #openstack-meeting-421:17
*** thorst_ has joined #openstack-meeting-421:18
*** salv-orl_ has joined #openstack-meeting-421:18
*** njohnsto_ has joined #openstack-meeting-421:20
*** thorst__ has joined #openstack-meeting-421:21
*** eil397 has joined #openstack-meeting-421:21
*** rbak has quit IRC21:21
*** thorst_ has quit IRC21:22
*** salv-orlando has quit IRC21:22
*** rbak has joined #openstack-meeting-421:22
*** markvan has quit IRC21:24
*** woodard has joined #openstack-meeting-421:24
*** shakamunyi has quit IRC21:24
*** rbak has quit IRC21:24
*** rbak has joined #openstack-meeting-421:24
*** Sukhdev has joined #openstack-meeting-421:25
*** DevonBoatwright has joined #openstack-meeting-421:25
*** bpokorny has quit IRC21:25
*** thorst__ has quit IRC21:25
*** vishnoianil has joined #openstack-meeting-421:25
*** DevonBoatwright has left #openstack-meeting-421:26
*** bpokorny has joined #openstack-meeting-421:26
*** markvan has joined #openstack-meeting-421:27
*** spotz is now known as spotz_zzz21:30
*** rtheis has quit IRC21:31
*** SimonChung1 has joined #openstack-meeting-421:32
*** SimonChung has quit IRC21:32
*** SimonChung1 has quit IRC21:33
*** SimonChung has joined #openstack-meeting-421:33
*** SimonChung has quit IRC21:33
*** SimonChung has joined #openstack-meeting-421:33
*** iyamahat has quit IRC21:34
*** SimonChung has quit IRC21:35
*** SimonChung1 has joined #openstack-meeting-421:35
*** galstrom is now known as galstrom_zzz21:36
*** baoli has quit IRC21:37
*** sridhar_ram has quit IRC21:37
*** baoli has joined #openstack-meeting-421:38
*** woodard has quit IRC21:38
*** cartik has joined #openstack-meeting-421:39
*** cloudtrainme has quit IRC21:41
*** iyamahat has joined #openstack-meeting-421:41
*** thorst_ has joined #openstack-meeting-421:44
*** thorst_ has quit IRC21:48
*** Sukhdev has quit IRC21:52
*** sukhdev has joined #openstack-meeting-421:56
*** rpjr_ has joined #openstack-meeting-421:57
*** rpjr__ has quit IRC22:00
*** bpokorny_ has joined #openstack-meeting-422:01
*** bpokorny_ has quit IRC22:01
*** ddieterly has joined #openstack-meeting-422:01
*** bpokorny_ has joined #openstack-meeting-422:02
*** pvaneck has quit IRC22:03
*** bpokorny has quit IRC22:04
*** ihrachys has quit IRC22:05
*** dave-mccowan has quit IRC22:06
*** cbits has quit IRC22:10
*** s3wong has joined #openstack-meeting-422:13
*** rpjr_ has quit IRC22:14
*** shakamunyi has joined #openstack-meeting-422:18
*** dave-mccowan has joined #openstack-meeting-422:18
*** ddieterly is now known as ddieterly[away]22:18
*** ddieterly[away] is now known as ddieterly22:19
*** JRobinson__ has joined #openstack-meeting-422:19
*** JRobinson__ has quit IRC22:20
*** neelashah has quit IRC22:21
*** Sukhdev_ has joined #openstack-meeting-422:21
*** aunnam_ has joined #openstack-meeting-422:22
*** shakamunyi has quit IRC22:24
*** Sukhdev_ has quit IRC22:26
*** hdaniel has joined #openstack-meeting-422:26
*** rpjr_ has joined #openstack-meeting-422:28
*** ddieterly is now known as ddieterly[away]22:30
*** ddieterly[away] is now known as ddieterly22:30
*** gregfaust has quit IRC22:31
*** cloudtrainme has joined #openstack-meeting-422:31
*** rpjr__ has joined #openstack-meeting-422:32
*** cloudtrainme has quit IRC22:32
*** angdraug has quit IRC22:32
*** rpjr___ has joined #openstack-meeting-422:32
*** cloudtrainme has joined #openstack-meeting-422:32
*** hdaniel has quit IRC22:33
*** SimonChung1 has quit IRC22:33
*** SimonChung has joined #openstack-meeting-422:33
*** rpjr_ has quit IRC22:35
*** annegentle has quit IRC22:35
*** aunnam_ has quit IRC22:35
*** rpjr__ has quit IRC22:36
*** cloudtrainme has quit IRC22:37
*** aunnam_ has joined #openstack-meeting-422:37
*** minwang2 has left #openstack-meeting-422:41
*** qwebirc92702 has joined #openstack-meeting-422:44
*** qwebirc92702 has quit IRC22:44
*** rpjr___ has quit IRC22:48
*** prashantD_ has joined #openstack-meeting-422:48
*** prashantD has quit IRC22:50
*** baoli has quit IRC22:52
*** rpjr_ has joined #openstack-meeting-422:54
*** sdake has quit IRC22:54
*** sdague has quit IRC22:57
*** sdake has joined #openstack-meeting-422:58
*** rpjr_ has quit IRC23:06
*** rbak_ has joined #openstack-meeting-423:07
*** rbak_ has quit IRC23:07
*** rbak has quit IRC23:10
*** banix has joined #openstack-meeting-423:11
*** sdake has quit IRC23:12
*** pmesserli has quit IRC23:15
*** reedip__ has quit IRC23:16
*** aunnam_ has quit IRC23:22
*** salv-orl_ has quit IRC23:24
*** cartik has quit IRC23:27
*** banix has quit IRC23:27
*** markvoelker has quit IRC23:29
*** doonhammer has quit IRC23:30
*** sridhar_ram has joined #openstack-meeting-423:31
*** ddieterly is now known as ddieterly[away]23:33
*** ddieterly[away] has quit IRC23:33
*** ddieterly has joined #openstack-meeting-423:37
*** vtech has quit IRC23:37
*** bpokorny has joined #openstack-meeting-423:40
*** bpokorny_ has quit IRC23:40
*** Jeffrey4l_ has quit IRC23:42
*** bpokorny has quit IRC23:46
*** eil397 has left #openstack-meeting-423:46
*** bpokorny has joined #openstack-meeting-423:47
*** ddieterly is now known as ddieterly[away]23:48
*** zenoway has quit IRC23:51
*** Sukhdev_ has joined #openstack-meeting-423:57
*** markvoelker has joined #openstack-meeting-423:59

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