Thursday, 2015-07-23

*** galstrom is now known as galstrom_zzz00:01
*** akwasnie has quit IRC00:01
*** xingchao has quit IRC00:08
*** igordcard has quit IRC00:19
*** bharath__ has quit IRC00:34
*** FallenPegasus has quit IRC00:38
*** jasondotstar has quit IRC00:47
*** bknudson has joined #openstack-meeting-400:47
*** jasondotstar has joined #openstack-meeting-400:49
*** DericHorn-HP has joined #openstack-meeting-400:49
*** yamamoto has joined #openstack-meeting-400:50
*** shalq has quit IRC00:51
*** jasondotstar has quit IRC00:54
*** padkrish has quit IRC00:58
*** padkrish has joined #openstack-meeting-400:59
*** Brian___ has joined #openstack-meeting-401:00
*** Brian___ has quit IRC01:02
*** padkrish has quit IRC01:03
*** salv-orlando has quit IRC01:03
*** Brian___ has joined #openstack-meeting-401:04
*** yamamoto has quit IRC01:06
*** padkrish has joined #openstack-meeting-401:11
*** puranamr has quit IRC01:11
*** dannywilson has quit IRC01:24
*** s3wong has quit IRC01:41
*** harshs has quit IRC01:45
*** Brian___ has quit IRC01:48
*** Brian___ has joined #openstack-meeting-401:48
*** EmilienM|off is now known as EmilienM01:52
*** padkrish has quit IRC01:53
*** Brian___ has quit IRC01:54
*** jerryz has quit IRC01:54
*** yamamoto has joined #openstack-meeting-401:58
*** shangxdy has joined #openstack-meeting-401:59
*** vivek-ebay has quit IRC02:01
*** Brian___ has joined #openstack-meeting-402:02
*** salv-orlando has joined #openstack-meeting-402:04
*** blahRus has quit IRC02:07
*** xingchao has joined #openstack-meeting-402:10
*** lexholden has quit IRC02:11
*** salv-orlando has quit IRC02:16
*** DericHorn-HP has quit IRC02:17
*** yamahata has quit IRC02:27
*** Brian___ has quit IRC02:31
*** amotoki has joined #openstack-meeting-402:34
*** Brian___ has joined #openstack-meeting-402:35
*** DericHorn-HP has joined #openstack-meeting-402:38
*** sbalukoff has quit IRC02:47
*** jckasper has joined #openstack-meeting-402:53
*** krtaylor has quit IRC02:54
*** Brian___ has quit IRC02:54
*** vivek-ebay has joined #openstack-meeting-402:57
*** bradjones has quit IRC03:03
*** bradjones has joined #openstack-meeting-403:04
*** bradjones has quit IRC03:04
*** bradjones has joined #openstack-meeting-403:04
*** Brian___ has joined #openstack-meeting-403:05
*** krtaylor has joined #openstack-meeting-403:07
*** KunalGan_ has quit IRC03:14
*** shangxdy has quit IRC03:16
*** vivek-ebay has quit IRC03:24
*** vivek-ebay has joined #openstack-meeting-403:24
*** salv-orlando has joined #openstack-meeting-403:28
*** wei-wang has joined #openstack-meeting-403:31
*** coolsvap|away is now known as coolsvap03:34
*** salv-orlando has quit IRC03:38
*** KunalGandhi has joined #openstack-meeting-403:39
*** DericHorn-HP has quit IRC03:40
*** sbalukoff has joined #openstack-meeting-403:42
*** KunalGandhi has quit IRC03:45
*** KunalGandhi has joined #openstack-meeting-403:48
*** jerryz has joined #openstack-meeting-403:50
*** HenryG has quit IRC04:09
*** Brian___ has quit IRC04:11
*** HenryG has joined #openstack-meeting-404:12
*** daneyon_ has joined #openstack-meeting-404:22
*** harshs has joined #openstack-meeting-404:23
*** daneyon has quit IRC04:24
*** puranamr has joined #openstack-meeting-404:34
*** DericHorn-HP has joined #openstack-meeting-404:39
*** Brian___ has joined #openstack-meeting-404:45
*** vishwana_ has quit IRC04:45
*** yamahata has joined #openstack-meeting-404:48
*** FallenPegasus has joined #openstack-meeting-404:49
*** dannywilson has joined #openstack-meeting-404:52
*** dannywilson has quit IRC04:52
*** DericHorn-HP has quit IRC04:53
*** dannywilson has joined #openstack-meeting-404:53
*** xingchao has quit IRC04:54
*** puranamr has quit IRC05:02
*** sbalukoff has quit IRC05:04
*** xingchao has joined #openstack-meeting-405:11
*** xingchao has quit IRC05:16
*** harshs has quit IRC05:20
*** vivek-eb_ has joined #openstack-meeting-405:23
*** DericHorn-HP has joined #openstack-meeting-405:25
*** numan has joined #openstack-meeting-405:25
*** vivek-ebay has quit IRC05:26
*** yamamoto has quit IRC05:27
*** Brian___ has quit IRC05:28
*** yamamoto has joined #openstack-meeting-405:29
*** jerryz has quit IRC05:31
*** sam__ has joined #openstack-meeting-405:34
*** Brian___ has joined #openstack-meeting-405:35
*** DericHorn-HP has quit IRC05:41
*** vivek-eb_ has quit IRC05:42
*** nkrinner has joined #openstack-meeting-405:43
*** salv-orlando has joined #openstack-meeting-405:43
*** salv-orlando has quit IRC05:48
*** numan has quit IRC05:53
*** zeih has joined #openstack-meeting-405:53
*** zeih has quit IRC05:58
*** yamahata has quit IRC06:03
*** xingchao has joined #openstack-meeting-406:04
*** zeih has joined #openstack-meeting-406:06
*** kobis has joined #openstack-meeting-406:06
*** FallenPegasus has quit IRC06:10
*** KunalGan_ has joined #openstack-meeting-406:12
*** Brian___ has quit IRC06:12
*** KunalGandhi has quit IRC06:15
*** yamahata has joined #openstack-meeting-406:16
*** zeih has quit IRC06:16
*** KunalGan_ has quit IRC06:17
*** zeih has joined #openstack-meeting-406:26
*** banix has quit IRC06:32
*** Brian___ has joined #openstack-meeting-406:34
*** zeih has quit IRC06:38
*** zeih has joined #openstack-meeting-406:42
*** jpekkari has joined #openstack-meeting-406:42
*** vivek-ebay has joined #openstack-meeting-406:43
*** lakshmiS has joined #openstack-meeting-406:46
*** vivek-ebay has quit IRC06:47
*** jasondotstar has joined #openstack-meeting-406:55
*** salv-orlando has joined #openstack-meeting-406:56
*** yamamoto has quit IRC07:10
*** daneyon_ has quit IRC07:20
*** daneyon has joined #openstack-meeting-407:21
*** yamamoto has joined #openstack-meeting-407:24
*** Brian___ has quit IRC07:26
*** xingchao has quit IRC07:26
*** kobis has quit IRC07:30
*** kobis has joined #openstack-meeting-407:31
*** Brian___ has joined #openstack-meeting-407:36
*** zeih has quit IRC07:43
*** numan has joined #openstack-meeting-407:51
*** FallenPegasus has joined #openstack-meeting-407:59
*** zeih has joined #openstack-meeting-407:59
*** Brian___ has quit IRC08:02
*** FallenPegasus has quit IRC08:03
*** Brian___ has joined #openstack-meeting-408:04
*** lakshmiS has quit IRC08:11
*** asselin_ has quit IRC08:13
*** Brian___ has quit IRC08:15
*** Brian___ has joined #openstack-meeting-408:19
*** numan_ has joined #openstack-meeting-408:25
*** numan has quit IRC08:26
*** igordcard_ has quit IRC08:26
*** Brian___ has quit IRC08:40
*** Brian___ has joined #openstack-meeting-408:41
*** FallenPegasus has joined #openstack-meeting-409:14
*** sbalukoff has joined #openstack-meeting-409:18
*** Brian___ has quit IRC09:23
*** jasondotstar has quit IRC09:25
*** jasondotstar has joined #openstack-meeting-409:38
*** jasondotstar has quit IRC09:43
*** dannywilson has quit IRC09:44
*** Brian___ has joined #openstack-meeting-409:54
*** Brian___ has quit IRC09:55
*** amotoki has quit IRC10:05
*** zeih has quit IRC10:07
*** Brian___ has joined #openstack-meeting-410:09
*** lakshmiS has joined #openstack-meeting-410:11
*** Brian___ has quit IRC10:19
*** Brian___ has joined #openstack-meeting-410:20
*** igordcard_ has joined #openstack-meeting-410:22
*** igordcard_ has quit IRC10:22
*** igordcard_ has joined #openstack-meeting-410:22
*** igordcard_ has quit IRC10:22
*** igordcard_ has joined #openstack-meeting-410:22
*** igordcard_ has quit IRC10:22
*** igordcard_ has joined #openstack-meeting-410:22
*** igordcard_ has quit IRC10:23
*** Brian___ has quit IRC10:24
*** coolsvap is now known as coolsvap|away10:27
*** zeih has joined #openstack-meeting-410:30
*** jasondotstar has joined #openstack-meeting-410:31
*** dims_ has joined #openstack-meeting-410:52
*** FallenPegasus has joined #openstack-meeting-411:02
*** FallenPegasus has quit IRC11:07
*** yamamoto has quit IRC11:13
*** lazy_prince has joined #openstack-meeting-411:30
*** zeih has quit IRC11:37
*** nkrinner has quit IRC11:37
*** nkrinner has joined #openstack-meeting-411:41
*** ajayaa has joined #openstack-meeting-411:43
*** klamath has joined #openstack-meeting-411:46
*** yamamoto has joined #openstack-meeting-411:49
*** Brian___ has joined #openstack-meeting-411:49
*** yamamoto has quit IRC11:53
*** dims_ has quit IRC12:02
*** banix has joined #openstack-meeting-412:08
*** jasondotstar has quit IRC12:11
*** jpekkari has quit IRC12:18
*** ajayaa has quit IRC12:18
*** sam__ has quit IRC12:18
*** geoffarnold has quit IRC12:23
*** geoffarnold has joined #openstack-meeting-412:23
*** lexholden has joined #openstack-meeting-412:24
*** yamamoto has joined #openstack-meeting-412:29
*** yamamoto_ has joined #openstack-meeting-412:30
*** zeih has joined #openstack-meeting-412:34
*** yamamoto has quit IRC12:34
*** VW_ has joined #openstack-meeting-412:35
*** banix has quit IRC12:37
*** lakshmiS has quit IRC12:43
*** geoffarnold has quit IRC12:44
*** geoffarnold has joined #openstack-meeting-412:44
*** FallenPegasus has joined #openstack-meeting-412:51
*** Brian___ has quit IRC12:54
*** FallenPegasus has quit IRC12:56
*** shalq has joined #openstack-meeting-413:02
*** geoffarnold has quit IRC13:05
*** geoffarnold has joined #openstack-meeting-413:06
*** banix has joined #openstack-meeting-413:10
*** ajayaa has joined #openstack-meeting-413:23
*** geoffarnold has quit IRC13:25
*** geoffarnold has joined #openstack-meeting-413:26
*** jasondotstar has joined #openstack-meeting-413:30
*** zeih has quit IRC13:33
*** zeih has joined #openstack-meeting-413:36
*** xingchao has joined #openstack-meeting-413:36
*** bknudson has quit IRC13:40
*** xingchao has quit IRC13:41
*** xingchao has joined #openstack-meeting-413:42
*** shalong has joined #openstack-meeting-413:42
*** pbourke has quit IRC13:43
*** bpoulos has joined #openstack-meeting-413:43
*** dims_ has joined #openstack-meeting-413:44
*** pbourke has joined #openstack-meeting-413:44
*** dims_ has quit IRC13:45
*** dims_ has joined #openstack-meeting-413:45
*** ninag_ has joined #openstack-meeting-413:49
*** DericHorn-HP has joined #openstack-meeting-413:49
*** carl_baldwin has joined #openstack-meeting-413:49
*** lakshmiS has joined #openstack-meeting-413:51
*** ninag_ has quit IRC13:53
*** ninag has joined #openstack-meeting-413:53
*** krtaylor has quit IRC13:53
*** Brian___ has joined #openstack-meeting-413:54
*** wxy has joined #openstack-meeting-413:55
*** wxy_ has joined #openstack-meeting-413:55
*** dshakhray has joined #openstack-meeting-413:59
*** wxy has quit IRC13:59
*** Brian___ has quit IRC13:59
*** bnemec has joined #openstack-meeting-413:59
*** kent_w has joined #openstack-meeting-414:00
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk14:00
*** ativelkov has joined #openstack-meeting-414:00
nikhil_k#startmeeting glance14:00
openstackMeeting started Thu Jul 23 14:00:35 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
ativelkovo/14:00
krykowskio/14:00
bpouloso/14:00
nikhil_k#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
lakshmiSo/14:00
mfedosino/14:00
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
dshakhrayo/14:01
*** agalkin has joined #openstack-meeting-414:01
flaper87o/14:01
hemanthmo/14:02
kragnizo/14:02
agalkino/14:02
flaper87(ish)14:02
flaper87really bad internet connection where I'm at right now14:02
*** mclaren has joined #openstack-meeting-414:02
rosmaitao/14:03
nikhil_kThanks all for joining14:03
nikhil_k#topic Updates14:03
*** openstack changes topic to "Updates (Meeting topic: glance)"14:03
nikhil_k#info mid-cycle14:03
nikhil_k#link https://etherpad.openstack.org/p/liberty-glance-mid-cycle-meetup14:03
nikhil_k#info We will do a video+audio conf with co-located midcycle14:04
*** aventerav has joined #openstack-meeting-414:04
flaper87awesome14:04
nikhil_k#info This would be our virtual meetup too14:04
flaper87is the info for that on the etherpad?14:04
nikhil_k#action all: please add your name timezone info against the session interested in14:04
flaper87I'll try to be on-line... you know, TZs14:04
nikhil_kflaper87: ^14:05
nikhil_kWe have it spread over 3 days for remote convenience14:05
nikhil_kSo that people from different tz can find it easier to get some face to face time14:05
nikhil_kFor the rest of period we will do brainstorming + fun activities if not usual work14:06
*** jckasper has quit IRC14:06
*** krtaylor has joined #openstack-meeting-414:06
jokke_o/14:07
*** belmoreira has joined #openstack-meeting-414:08
mclarenWould having some v3 discussion be worthwhile?14:08
*** bunting has joined #openstack-meeting-414:08
nikhil_ksure, I have to add some more sessions.14:08
*** VW_ has quit IRC14:08
*** sigmavirus24_awa is now known as sigmavirus2414:08
nikhil_kmclaren: it would be most likely on thursday 30th14:08
*** xek has joined #openstack-meeting-414:09
*** VW_ has joined #openstack-meeting-414:09
mclarenok, cool. (Hopefully remote will work out ok for ativelkov and mfedosin)14:09
mfedosinwe have a good Internet connection, so yes :)14:10
*** melissa_u has joined #openstack-meeting-414:10
*** yamamoto_ has quit IRC14:10
*** malini_ has joined #openstack-meeting-414:11
nikhil_kSo, to help schedule the time please add some tz info against your name on each topic interested. Also, if you have conflicts at specfic times/days that would help14:11
malini_good morning14:11
*** bknudson has joined #openstack-meeting-414:11
nikhil_kmoving on14:12
nikhil_k#topic Glance Registry v2 and RPC calls14:12
*** openstack changes topic to "Glance Registry v2 and RPC calls (Meeting topic: glance)"14:12
nikhil_kflaper87: ^14:12
krykowskithats me14:12
krykowskistill digging through rolling upgrade issues, need some clarification14:12
krykowskido I understand correctly that registry-v2 service is not required in my setup to have fully working Glance?14:12
mclarencorrect14:13
krykowskiit's just used as an optional component in api for accesing data from the database using RPC calls instead of direct access to the database14:13
krykowskiand despite registry service there are no other RPC communication in the Glance at all, right?14:13
nikhil_kyep14:13
*** VW_ has quit IRC14:13
nikhil_kkrykowski: there's a possibility of rpc conn when using tasks (that's optional too)14:14
krykowskigreat news, so I guess it will help a lot in performing rolling upgrades in Glance as we can setup only glance-api14:14
nikhil_kkrykowski: in case of tasks, you can setup a set of glance-tasks nodes14:15
*** wei-wang has quit IRC14:15
mclarenkrykowski: I think it's great someone is thinking about rolling upgrades, it's an important consideration, which maybe hasn't got the attention it deserves14:15
nikhil_kHowever, I think in that particular case I would think we don't need migration14:15
sabario/14:15
krykowskiwoah, is it documented anywhere so I can get a better understanding of it?14:15
krykowskiI mean the glance-tasks service14:16
nikhil_knope, because that happens proxy via taskflow14:16
jokke_krykowski: obviously that means that you can actually consume v2 API only as v1 API still needs the registry14:16
nikhil_kkrykowski: we can chat offline on that or better yet do it in the mid-cycle and identify if we are not going to touch tasks db-schema14:16
*** yamamoto has joined #openstack-meeting-414:17
nikhil_kflaper87: wanted to do some on the task info, but I think it would be a bad experience for a public cloud given the info fields can be gigantic14:18
*** VW_ has joined #openstack-meeting-414:18
nikhil_kthat was a tentative hint on the migration though14:18
flaper87nikhil_k: oh I didn't want to do something on that, I was more asking why we had it14:18
nikhil_kflaper87: hush, glad to hear it14:19
*** belmoreira has quit IRC14:19
nikhil_ktwo conflicting qually qualified use cases for that migration would be a nightmare14:19
nikhil_kequally*14:19
nikhil_kkrykowski: do you have more questions?14:21
krykowskinikhil_k: will ping you later about the tasks to better understand it14:21
krykowskinikhil_k: for now I'm fine14:21
nikhil_kthanks14:21
nikhil_k#topic api requests and the req-body14:21
*** openstack changes topic to "api requests and the req-body (Meeting topic: glance)"14:21
nikhil_kbunting: ^14:22
buntingYeah, i am working on a bug, where if you provide a body to a http request when the api does not expect it it 500s14:22
buntingI am wondering what the expected responce should be14:22
buntingto ignore the body or return some error14:23
jokke_bunting: you have a link for that bug?14:23
buntinghttps://bugs.launchpad.net/glance/+bug/147564714:23
openstackLaunchpad bug 1475647 in Glance "Returns 500 if a body is included where not expected" [Undecided,New] - Assigned to Niall Bunting (niall-bunting)14:23
mclarenkragniz: you had some wisdom on this?14:24
nikhil_kbunting: it's bad sematics to pass the body on verbs that ideally don't expect them14:24
nikhil_kbunting: but it's possible nonetheless14:24
kragnizmclaren: not so much, people seem to be split on what to do in this situation on other projects14:24
kragnizsigmavirus24: would probably have a good idea14:25
sigmavirus24so14:25
buntingnikhil_k: Yeah, i imagine it is never a good idea to go down unexpected paths, as it could lead to future exploits or something14:25
sigmavirus24500 means the server fubar'd when what we want is to say "That was a bad request"14:25
nikhil_kbunting: so, I think the wsgi wrapper is possible not expecting that14:25
kragnizsigmavirus24: we certainly want to change it from a 50014:26
jokke_++14:26
mclarenok, from memory, it's impossible for us not to read in the full body (wsgi will always read it in)14:26
sigmavirus24That said, I looked at the review that bunting did for that bug and it looks like they were preventing against going down paths where we are expecting a body14:26
jokke_mclaren: correct14:26
sigmavirus24mclaren: right, because wsgi is terrible and everything should be written in Java ;)14:26
mclarenso we can either read it in and return 400 or read it in and ignore it14:26
* jokke_ send cruise missile towards sigmavirus24's general location14:27
nikhil_kI think body is read uptil a buffer before processing the api req14:27
sigmavirus24Ah so that bug is different from the review I saw14:27
mclarensigmavirus24: not Java ... [insert latest hipster language of your choice] ;-)14:27
sigmavirus24mclaren: Java is Enterprise14:27
sigmavirus24So for a GET like that14:27
sigmavirus24I would say ignore it14:27
jokke_I do not agree14:28
sigmavirus24Ignore it and return a 200 even if that is a bad request14:28
jokke_we should fain, not ignore for malformed requests14:28
jokke_fail even14:28
nikhil_kwell, we need to validate the body and not just ignore it14:28
mclarenI think ignoring it is probably consistent with some current requests that don't return 50014:28
nikhil_kbecause it can be a dos possibility14:28
sigmavirus24So GETs are /allowed/ to have bodies but semantically they have no meaning14:28
sigmavirus24jokke_: so considering the RFCs around this, I would say that ignoring a body in a GET is perfectly valid14:29
*** banix has quit IRC14:29
sigmavirus24And in fact a load balancer/proxy would strip it out entirely if Glance were running behind it14:29
malini_actually we should detect body, not read all of it -- that is a way of denial of service, quick say malformed.14:29
mclarenmalini_: we don't have that option, as I mentioned14:29
kragnizmalini_: we can't do that with the wsgi layer14:29
nikhil_knot yet14:30
mclarenthe library that glance is wrapped in will helpfully read in the entire body (that's out of our control currently)14:30
*** banix has joined #openstack-meeting-414:30
mclarennikhil_k: is there a plan to change something there?14:30
nikhil_kbut I agree, this is out of scope for glance given proxies can handle such validation14:31
*** briancurtin has quit IRC14:31
nikhil_kmclaren: nothing yet, some features are using wsme14:31
*** briancurtin has joined #openstack-meeting-414:31
*** vsaienko has quit IRC14:31
mclarenI guess maybe pinging other projects to see if there is any rough consensus on unexpected bodies in openstack couldn't hurt14:31
nikhil_kgood cpl topic jokke_14:32
nikhil_kbunting: ^14:32
sigmavirus24mclaren: already talking in #openstack-api about this14:32
mclarencool14:32
sigmavirus24nikhil_k: so I wouldn't say that in order to run glance you need a proxy14:32
*** numan_ has quit IRC14:32
sigmavirus24That's certainly not something we've ever stated as being part of the ref architecture14:33
sigmavirus24I'm merely pointing out that if someone *were* running glance behind such a service, they'd never see a 50014:33
*** banix has quit IRC14:33
sigmavirus24And we can behave the same way14:33
nikhil_ksigmavirus24: yep, we can't madate it but it's out of scope for various reasons and having a proxy is good practice for other reasons too14:33
*** malini__ has joined #openstack-meeting-414:33
sigmavirus24Because it's reasonable as defined by the semantics in RFC 723[0-5] (because I can't remember specifically which)14:33
*** malini_ has quit IRC14:34
nikhil_klike  auth groups, endpoint validation, other custom headers validations14:34
sigmavirus24Sure, but we should still DTRT here14:34
kragniznikhil_k: we shouldn't assume people are running glance behind a proxy, though14:34
nikhil_kbtw, everyone: it's already on the CPL meeting agenda next week jokke_ mclaren bunting sigmavirus24 #link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting14:34
nikhil_k#link https://review.openstack.org/#/c/184358/14:35
jokke_good, so lets postpone any further discussion until we hear wider consensus?14:35
nikhil_kit's a good practice is all I have to say14:35
buntingGetting consensus from the other projects seems the best course of action for me14:36
nikhil_kbunting: do you mind starting a ML thread before that?14:37
sigmavirus24nikhil_k: do you know the CPL meeting room/time by chance?14:37
nikhil_ksigmavirus24: Tuesdays @ #openstack-meeting 2100UTC (Weekly for 1 hour)14:37
sabariso elastic search api allows body in GET requests. So may be it's important in searchlight :)14:37
sabarihttps://www.elastic.co/guide/en/elasticsearch/reference/1.6/search-request-body.html14:37
nikhil_ksabari: yeah, it's bit different yet imp case ;)14:38
sigmavirus24sabari: Good example14:38
nikhil_kAnyways, we should move one for now14:38
sigmavirus24agreed14:38
nikhil_k#topic Reviews, Bugs and Releases14:38
*** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: glance)"14:38
nikhil_k#info Prevent glance-api hangups during connection to rbd14:38
mfedosinit's mine14:39
nikhil_k#link https://review.openstack.org/#/c/200554/14:39
sigmavirus24mfedosin: no it's ours =P You contributed it to the community ;)14:39
sabarihaha14:39
mfedosinsigmavirus24, my topic14:39
mfedosinnot a bug :)14:39
buntingnikhil_k: I will14:39
mfedosinflaper87, some time ago I mentioned about hangups in ceph14:40
jokke_nikhil_k: we need creative commons license header to the agenda etherpad :P14:40
mfedosinso the solution is obvious14:40
*** FallenPegasus has joined #openstack-meeting-414:40
jokke_don't use it?14:40
mfedosinlet's add licences in commit messages14:40
sigmavirus24jokke_: lol14:40
kragnizjokke_: harsh14:41
sigmavirus24Solution to hangups in ceph is to add licenses to commit messages... interesting14:41
sigmavirus24Ceph truly is a mysterious and glorious beast14:41
sigmavirus24=P14:41
*** TheIntern has joined #openstack-meeting-414:41
*** krtaylor has quit IRC14:41
mfedosinsigmavirus24, stop trolling me :)14:41
mfedosinI'm laughing and can't write14:42
mfedosinso I have two questions about the commit14:42
mfedosinshould I add some unit tests there14:42
mfedosinand should I add retries in our rbd driver?14:42
mfedosinfolks in cinder do it not a long time ago14:43
mfedosinhttps://review.openstack.org/#/c/190579/814:43
*** vishwanathj has joined #openstack-meeting-414:44
*** FallenPegasus has quit IRC14:45
nikhil_kmfedosin: +1 on unit tests14:46
sabari+1 for unit tests. I think retrying connection is a good idea.14:46
kragnizmfedosin: I'd say yes on a retry, but I like retries14:46
nikhil_kI am not too sure about retries and if, how many. May be ask on operators channel14:46
mfedosinsabari, it can be another commit14:46
jokke_0 for the unit tests +1 for the retry, but I'm not convinced if the retry should happen on this change14:47
sabarithe vmware store has a vmware_api_retry_count14:47
kragnizwe have retries for the swift store, also14:47
mfedosinbut ceph doesn't14:48
*** spredzy is now known as spredzy|afk14:48
jokke_I think it's one of those things that would be nice to have, but it really does not fix this bug so I don't think it should be done in this change ;)14:49
mfedosinso I'm going to add some unit test on that change14:49
sigmavirus24kragniz: did we merge swift retries?14:49
sigmavirus24I forget now14:49
sabari jokke_ agree.14:49
mfedosinand then will try add reties14:49
sigmavirus24mfedosin: maybe add retries as off by default?14:49
mfedosinsigmavirus24, yes14:50
kragnizsigmavirus24: before my time14:50
malini__mfedosin, most such things have timeout interval and # of retries, and sensible defaults14:50
mfedosinsigmavirus24, agree. they can be switched off by default, but can be configured14:50
sigmavirus24mfedosin: also, maybe if cinder and glance are doing rbd things like this, there will be other places this is necessary and it will be worth an oslo.rbd library =P14:50
kragnizsigmavirus24: https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/store.py#L122-L12414:51
sigmavirus24kragniz: ah, I thought you had something to do with swift retries last cycle but I'm probably forgetting14:51
kragnizsigmavirus24: I did, that was about a sleep and backoff between retries14:51
mfedosinsigmavirus24, btw oslo.rbd is not a bad idea, it prevents serious code duplication14:52
sigmavirus24mfedosin: we should mention it at the oslo meeting on Monday14:52
sigmavirus24It'll have to go through the incubator first probably, but that's fine14:52
mfedosinsigmavirus24, when will it be?14:52
dims_mfedosin: sigmavirus24: if you create a core team with who ever you want, either glance or cinder can own the git repo too14:53
sigmavirus24dims_: ooo14:53
*** zeih has quit IRC14:53
sigmavirus24dims_: why not both? =P14:53
kragnizdims_: do you have oslo on highlight or something? :P14:53
dims_sigmavirus24: one git repo goes into one project in the governance repo14:53
dims_kragniz: yep :)14:53
sigmavirus24mfedosin: http://eavesdrop.openstack.org/#Oslo_Team_Meeting14:53
kragnizhow much code could we remove from our rdb driver, though?14:54
dims_practically it does not matter which project owns it as long as folks from both projects are on the core14:54
mfedosinokay, I'm going to be there14:54
kragnizthere's the rdb uri parsing14:54
*** krtaylor has joined #openstack-meeting-414:54
*** melissa_u has left #openstack-meeting-414:54
nikhil_kbtw, next review is #link https://review.openstack.org/#/c/203679/14:54
kragnizI guess there's all the connection stuff, actually14:55
nikhil_kany last min objections?14:55
kragnizyeah, let's move on14:55
sabari+1. It helped a lot to have oslo.vmware in case of the vmware store driver.14:55
nikhil_knothing, we can +A that one then14:56
nikhil_k#topic Open Discussion14:56
*** openstack changes topic to "Open Discussion (Meeting topic: glance)"14:56
nikhil_kNext week's irc  weekly-meeting is cancelled14:57
*** igordcard_ has joined #openstack-meeting-414:57
sabariHow about https://review.openstack.org/#/c/181347/ ?14:57
sabariI think this needs a migration change too.14:57
sabariflaper87: ^14:57
malini__https://review.openstack.org/#/c/194868/ and this would like +2, we are making good progress on implementation14:58
*** Brian___ has joined #openstack-meeting-414:58
nikhil_kyep, it needs data correction on the existing old deployments14:58
nikhil_kbut it's gone now to contradict given that it merged in oslo.db14:59
jokke_I'm tempted to block that merge14:59
jokke_put a -1 comment in14:59
jokke_and there is lots of those what I flagged14:59
nikhil_kjokke_: we had deprecated the config a while back14:59
sabarinikhil_k: https://review.openstack.org/#/c/75898/7 has all history15:00
jokke_nikhil_k: I mean that flake8 change15:00
jokke_you just approved15:00
nikhil_kjokke_: ohk15:00
sabariso I think may be we should fix this for newer deployments and error out on older if they haven't fixed thier tables to utf815:00
nikhil_kmclaren: also +Aed it15:00
nikhil_kjokke_: what do you want us to do?15:01
*** harshs has joined #openstack-meeting-415:01
jokke_lets continue on -glance we're out of time15:01
*** sjmc7_ has joined #openstack-meeting-415:01
nikhil_kThanks all15:01
shalqnikhil_k: I have a request to review https://review.openstack.org/#/c/190895/15:01
malini__bye everyone!15:01
nikhil_kshalq: on #openstack-glance please15:02
nikhil_k#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Thu Jul 23 15:02:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-23-14.00.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-23-14.00.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-23-14.00.log.html15:02
*** jckasper has joined #openstack-meeting-415:02
sjmc7_nikhil_k, TravT's on his way15:02
*** ninag has left #openstack-meeting-415:02
*** shalq has left #openstack-meeting-415:02
nikhil_ksjmc7_: ok, youboth want us to wait or start the proceedings15:02
nikhil_k?15:02
*** TravT has joined #openstack-meeting-415:03
sjmc7_he's very close :)15:03
*** bpoulos has left #openstack-meeting-415:03
*** Brian___ has quit IRC15:03
nikhil_k#startmeeting openstack search15:03
openstackMeeting started Thu Jul 23 15:03:24 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: openstack search)"15:03
nikhil_k#chair TravT15:03
openstackThe meeting name has been set to 'openstack_search'15:03
openstackCurrent chairs: TravT nikhil_k15:03
TravTthanks, nikhil_k15:03
rosmaitao/15:03
nikhil_k#topic agenda and roll call15:03
*** openstack changes topic to "agenda and roll call (Meeting topic: openstack search)"15:03
kragnizo/15:03
nikhil_ko/15:03
TravTo/15:03
lakshmiSo/15:03
nikhil_khey TravT15:03
sjmc7_o/15:03
TravTagenda here: https://etherpad.openstack.org/p/search-team-meeting-agenda15:04
*** wxy_ has left #openstack-meeting-415:04
*** bunting has left #openstack-meeting-415:04
TravTadd anything to it that you'd like15:04
TravT#topic Horizon integration update --> Endpoint in Keystone (include v1 or not?) TravT, sjmc715:05
*** openstack changes topic to "Horizon integration update --> Endpoint in Keystone (include v1 or not?) TravT, sjmc7 (Meeting topic: openstack search)"15:05
TravTso, sjmc7 and i are at the horizon mid-cycle15:05
sigmavirus24o/15:05
TravTmy focus has been trying to get images table angularized and getting a widget called magic search on top of it.15:05
TravTthis lays the groundwork for utilizing searchlight15:06
TravTand yesterday sjmc7 started porting over our concept patch that we showed at the summit15:06
TravTvery early, but we did encounter one question15:06
TravTthat is the endpoint in keystone15:06
sjmc7_currently devstack puts in 'host:9393/'15:07
*** kobis has quit IRC15:07
sjmc7_which means the client has to append v1/15:07
sjmc7_there seems to be about a 50/50 split with how other services do it15:07
TravTin the endpoint list for other services there doesn't seem to be consistency15:07
TravTfor example, cinder has a totally different service listed15:07
TravTfor their v215:07
nikhil_khmm, yeah15:08
TravTso, we were wondering if we should keep the endpoint in the service catalog to not have the 'vX' appended15:08
TravTand force the user of the service to add that15:08
TravTor if we should have the endpoint in the catalog15:08
sjmc7_especially since we dpn't have a client to do that auto-versioning thingy the python clients seem to have15:08
TravThave the vX on it15:08
kragnizwe should have it unversioned15:09
kragnizthat's where other projects are trying to move to15:09
lakshmiSseems like cinder is good way to solve it since it also tells clients what versions are supported as endpoints15:09
sigmavirus24== kragniz15:10
sjmc7_that's 2 - 1. any other takers? :)15:10
TravTwe could put this out on the mailing list and announce our intention to not have it versioned in the endpoint list15:11
ekarlsoguys15:11
ekarlsohey guys :915:11
TravThowdy ekarlso!15:11
*** banix has joined #openstack-meeting-415:12
*** jasondotstar has quit IRC15:12
*** dannywilson has joined #openstack-meeting-415:12
ekarlsounversioned with discovery is the typical pattern15:12
ekarlsono /vFOO in the endpoints :P15:12
ekarlsoat least what we did for designate15:12
TravTallright, we'll stick with the unversioned for now.  that's what the current horizon patch assumes.15:12
sjmc7_we have no client15:12
*** dannywilson has quit IRC15:12
sjmc7_and thus no autodiscovery15:12
ekarlsosjmc7_: u can easily do that by using the adapter / session stuffi n ksauth15:13
*** dannywilson has joined #openstack-meeting-415:13
TravTwe don't have a discovery api right now (unless I missed something), so do we need to add that?15:13
ekarlsoTravT: u can pass a endpoint too to ks if you want to with a token15:13
TravTtypically you put in the requested version and client tries, right?15:14
sjmc7_let's put this on the mailing list and get a decision by next week15:14
ekarlsoTravT: yeah it'll try discovery if you dont pass a explicit endpoint15:14
*** shalong has quit IRC15:14
TravTok, well, let's stick with no version in keystone then.15:14
TravTso next topic is bug review15:15
TravT#topic     Ceilometer / Notifications: https://review.openstack.org/#/c/20239215:15
*** openstack changes topic to "Ceilometer / Notifications: https://review.openstack.org/#/c/202392 (Meeting topic: openstack search)"15:15
TravTlakshmiS: any updates here?15:15
lakshmiSafter several discussions/reviews we have the patch in decent shape now15:15
lakshmiShaven't seen any further -1's and works fine with ceilometer running15:16
TravTok. I'm guilty of not doing reviews in about a week, but tomorrow i'm intending to get on that.15:16
sjmc7_yeah, i'm good with it too, thanks for addressing my suggestions15:16
TravTtoday is last day of horizon meetup15:16
*** kent_w has left #openstack-meeting-415:16
*** david-lyle has joined #openstack-meeting-415:17
TravTok, on to next15:17
TravTany other bugs anybody needs discussion?15:18
sjmc7_https://bugs.launchpad.net/searchlight/+bug/146933615:18
openstackLaunchpad bug 1469336 in OpenStack Search (Searchlight) "Errors are returned as html" [Medium,New] - Assigned to Ian Cordasco (icordasc)15:18
sjmc7_we hit this doing the horizon integration and it's a pain15:18
*** zeih has joined #openstack-meeting-415:18
sjmc7_doesn't need discussion i don't think15:18
*** asselin_ has joined #openstack-meeting-415:19
TravTok15:19
TravT#topic     Blueprint review (Please add any blueprints needing attention below) https://blueprints.launchpad.net/searchlight15:19
*** openstack changes topic to "Blueprint review (Please add any blueprints needing attention below) https://blueprints.launchpad.net/searchlight (Meeting topic: openstack search)"15:19
TravTekarlso, there were several the last two weeks you had added but i don't think we discussed15:19
*** vivek-ebay has joined #openstack-meeting-415:20
TravTekarlso, can you re-share the info for setting up designate in devstack15:20
TravThttps://blueprints.launchpad.net/searchlight/+spec/designate-plugin15:20
TravTi'd like to get that setup so i can properly review and get that patch in15:20
ekarlsohttp://paste.ubuntu.com/11925639/15:21
lakshmiSekarlso: I would like to review that but what setup needs to be done?15:21
ekarlsothat's the localrc15:22
TravTdoes it setup sample data as well?15:22
ekarlsou just clone searchlight to /opt/stack/searchlight, checkout the PS15:22
ekarlsoehm15:22
ekarlsolemme write up instructions :p15:22
*** gregdek has quit IRC15:23
sjmc7_well, if there are eisting designate instructions we can follow that15:23
*** zeih has quit IRC15:23
TravTi was talking to a guy at time warner about desginate15:23
TravThe said he's happy it'll be in searchlight15:23
TravTbut also asked "will it give me any more data than I get from the CLI"15:23
sjmc7_i'll try and test the designate patch tomorrow or monday as well, be great to get that merged15:23
TravTi didn't know what to tell him?15:24
*** vivek-ebay has quit IRC15:24
TravTis there anything else on the designate plugin we should know for reviewing it?15:25
TravTif so, just add a comment on the patch i guess.15:25
TravTi will get to it tomorrow or monday15:25
TravTa big monkey on our back right now are nova instances15:25
TravT#topic  https://blueprints.launchpad.net/searchlight/+spec/nova-instances-plugin15:25
*** openstack changes topic to "https://blueprints.launchpad.net/searchlight/+spec/nova-instances-plugin (Meeting topic: openstack search)"15:25
nikhil_ko/15:25
*** xingchao has quit IRC15:25
sjmc7_yeah, any reviews on that patch are welcome15:26
TravTnikhil_k have you had any chance to look at that one?15:26
TravTi also intend to look at it tomorrow or Monday15:26
nikhil_kTravT: I did take a look and I think we should be good to go ahead on that based on the initial feedback.15:26
TravTit seems if it is a reasonable start and functions that we could get it in and do additional iteration.15:26
nikhil_kTravT: but I need to test it functionally :)15:26
TravTcool.15:26
sjmc7_woo. yes, please test it. let me know if you have questions15:27
*** harshs has quit IRC15:27
nikhil_kTravT: btw, if you happen visit last week's meeting and channel logs for thursday, I did some sharing on thoughts on what could be potential enhancements needed15:27
ekarlsohttps://etherpad.openstack.org/p/designate-searchlight15:27
ekarlso^ TravT sjmc7_ lakshmiS15:28
TravTekarlso: thanks!15:28
sjmc7_great, thanks15:28
ekarlsogtg, house maintenance on the works!15:28
lakshmiSekarlso: will ping you on irc if needed. whats your timezone?15:28
TravTnikhil_k, I did read the logs.  I guess anything needed to be kept forever could be added to the BP.15:28
ekarlsouhm, Norwegian / GMT+2 I believe :P15:28
TravTekarlso.  thanks!  we'll get your stuff going!15:28
lakshmiSok good for me15:29
TravTthere are two more BP listed on the meeting agenda15:29
TravT    BP: https://blueprints.launchpad.net/searchlight/+spec/openstack-client-usage15:29
TravTwhose is that?15:29
nikhil_kTravT: sjmc7_ can we schedule a session during the glance midcycle for some discussion around indexing and nova instances?15:30
nikhil_kcurious to know what our participation looks like15:30
sjmc7_uh.. sure15:30
TravTsure, i'll be around all next week15:30
nikhil_kcool15:30
nikhil_kmelissa can possibly join us15:30
*** igordcar1_ has joined #openstack-meeting-415:30
TravTok. i had a call with her a couple weeks ago.15:31
*** Bjoern_ has joined #openstack-meeting-415:31
TravTshe seemed very interested in utilizing searchlight15:31
TravTi think you and rosmaita will have the most context15:31
*** igordcar1_ has quit IRC15:32
*** sballe has quit IRC15:32
TravTnobody seems to own the client bp?15:32
*** sballe has joined #openstack-meeting-415:32
TravTguess we can move onto the named queries bp15:32
TravT https://blueprints.launchpad.net/searchlight/+spec/named-queries15:32
lakshmiSi am working on that15:32
nikhil_kTravT: we did a intial discussion yday but not so much on instances. I wanted to get some feedback on the use cases to see how we can proceed for long term indexing on that15:32
TravTnikhil_k, she has a very strong interest in utilizing searchlight for cross resource searching as well15:33
nikhil_kTravT: yeah, that part15:33
TravTto help facilitate a concept like amazon resource groups.15:33
nikhil_k+ cross region15:33
TravTyeah, we really could spend some time brainstorming on cross region.15:34
nikhil_kturtles all the way down, may be15:34
*** vivek-ebay has joined #openstack-meeting-415:34
TravTit would be good to have a working vidyo session on some of these topics15:34
TravTif we could get a few more of these basic patches in.15:35
nikhil_kTravT: so I think my misunderstanding was around the indexing through command line. Does HP use cases never needs direct db indexing?15:35
sjmc7_i don't think a use case ever dictates how you index15:36
TravTbut we're not aware of that right now.15:36
nikhil_kTravT: becasue for some API calls like the ones that have potentially large queries -- changes-since can be really expensive indexing operation and in some cases is 413'ed internally15:36
sjmc7_we're not habitually doing a changes-since query though15:37
nikhil_kpagination would take forever to index it, may be days!15:37
nikhil_ksjmc7_: yeah, I meant deleted stuff that can be potentially retrieved using that15:37
TravTnikhil_k, what's the likelihood of us getting notification in nova to carry the full data we need?15:37
nikhil_kbecause deleted stuff isn't really exposed via the api15:38
TravTis that a BP that we should open on nova?15:38
TravT(spec)15:38
sjmc7_i don't think i understand what you mean about 'deleted stuff'15:38
nikhil_kTravT: I think I would need to discuss the scope of such notifications with you both. we can do that offline15:38
TravTyeah, that would be good.15:39
nikhil_ksjmc7_: deleted instances, images (for now) (that's soft deleted)15:39
sjmc7_maybe we should have a call about nova because i think my understanding is lagging behind yours15:39
sjmc7_deleted instances send a notification15:39
sjmc7_deleted glance images i don't know about15:39
sjmc7_but i thought they did too15:39
nikhil_kyeah, but old ones won't. anyways we can chat later :)15:39
TravTyes, this would be a good working session / vidyo session15:40
TravTlet's schedule that15:40
nikhil_kcool15:40
TravT#action nikhil_k schedule nova design session15:40
TravTapparently that isn't how you do actions15:40
TravTthanks nikhil_k, i also feel like I'm missing some important information here.15:41
nikhil_kTravT: hmm, I thought it was the right way for doing # action15:41
nikhil_khttps://wiki.debian.org/MeetBot15:41
TravTgoing back on the topic of named queries.15:42
TravTlakshmiS, i don't know any exact named queried yet15:42
nikhil_kok, sure TravT15:42
lakshmiSTravT: I only have some basic quries for now.15:42
TravTi was wondering if for glance if rosmaita, nikhil_k, kragniz might know the most common searches needed or requested15:42
lakshmiScurrenlty the queries are part of the plugin but once plugin config file patch lands I can move it to the config file15:42
lakshmiSputting in config file will easier to add queries later easily15:43
*** mestery has joined #openstack-meeting-415:43
TravTlakshmiS, there isn't a plugin specific config patch up yet, is there?15:43
nikhil_k1. /images/details?name=foobar15:44
lakshmiSTravt: haven't seen one but heard someone was working on it. ekarlso? or may be no one is working on it15:44
rosmaitaTravT: name, name wildcard, instance_uuid, base_image_ref15:44
nikhil_k2. /images/details?updated_at=when??15:44
rosmaitaprob wildcards on all those i guess15:45
TravTfor updated_at, are time ranges important?15:45
rosmaitaprobably15:45
TravTeg between X dates or after X dates15:45
rosmaitayes15:45
*** jasondotstar has joined #openstack-meeting-415:45
rosmaitaforget the wildcards on UUID, don't know what i was thinking there15:45
sigmavirus24rosmaita: :D15:46
rosmaitaprobably the operating system15:46
sjmc7_let's stick these on the BP or an etherpad15:46
rosmaitaand version15:46
TravTrosmaita, is that just a well known property?  i didn't think that was in the common images properties list15:46
rosmaitai am pretty sure those are "common image properties"15:47
rosmaitathough i don't know that anyone uses them much15:47
*** FallenPegasus has joined #openstack-meeting-415:47
* TravT admits it has been a few months since reading those15:47
rosmaitabut if they are indexed, that will motivate people!15:47
TravTthey'll all be indexed!15:47
TravTeverything is indexed15:47
rosmaitahttp://docs.openstack.org/developer/glance/common-image-properties.html15:48
*** zeih has joined #openstack-meeting-415:48
nikhil_kI think we may need some on the min disk, min ram too15:48
TravTrosmaita: nikhil_k: could you add the notes above to the blueprint?15:49
TravThttps://blueprints.launchpad.net/searchlight/+spec/named-queries15:49
rosmaitaok15:49
TravTone thing i want to see about adding to horizon (although i know you public cloud rackspace guys don't care) is a drop down list of common queries15:49
TravTand we'd pull that from these named queries15:49
TravTthanks guys.15:50
TravT#topic liberty 2 release plan15:50
*** openstack changes topic to "liberty 2 release plan (Meeting topic: openstack search)"15:50
lakshmiSi should have the named queries patch up by tomorrow15:50
TravTthanks lakshmiS15:50
TravTso, we don't have a release plan yet15:51
* TravT slightly embarrassed15:51
TravTi think the action is for nikhil_k and I to talk offline about that15:51
nikhil_kyes15:52
*** DericHorn-HP has quit IRC15:52
TravTi'm guessing we get questioned on that later today, because we'll be talking about searchlight for a small bit in the horizon meetup this afternoon15:52
nikhil_kTravT: sjmc7_ and I agreed last week that it would be good to release after nova instances merges15:52
TravTok.15:52
TravTso, let's make it a goal that we have that and designate plugin merged by next meeting.15:52
TravTassuming they are ready of course15:53
TravT#topic open discussion15:53
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:53
nikhil_kI added a section for glance+searchlight in the glance's midcycle etherpad #link https://etherpad.openstack.org/p/liberty-glance-mid-cycle-meetup15:53
nikhil_k#action all interested: please add name and timezone info so that we can try to schedule it accordingly15:54
nikhil_kor if we need to split it15:54
TravTThanks, nikhil, just added me name15:54
rosmaitalakshmiS: i put some notes on the "whiteboard" on your BP15:55
lakshmiSrosmaita: saw that. thanks15:55
*** FallenPegasus has quit IRC15:55
rosmaitai have a general discussion question, viz., what are people thinking currently about how to do multi-region searchlight?15:55
TravTwe briefly spoke at summit, but haven't come up with a concrete plan.15:56
*** vivek-ebay has quit IRC15:56
lakshmiSi think initial idea was having multiple index one for each region15:56
rosmaitawe had informally said at some point that we'd keep a searchlight in each region, and then mabye a super-serachlight that would index them all15:56
TravTyeah, searchlight of searchlights15:57
sjmc7_*shudder*15:57
rosmaitasearchlight++15:57
sjmc7_authentication is a problem15:57
lakshmiSauthenticate is always pain15:57
sjmc7_i *think* tokens are always region scoped15:57
*** skath has quit IRC15:57
lakshmiSspecially across resource types15:57
*** skath has joined #openstack-meeting-415:58
sjmc7_that's maybe something we should have a proper discussion about, maybe next week15:58
sjmc7_figure out what we want it to look like and then if we can do it15:58
rosmaitasounds good15:58
*** zhiyan has quit IRC15:58
TravTagreed... also maybe get a few high level ideas up and get some ML input as well.15:58
*** zhiyan has joined #openstack-meeting-415:58
TravTanything else for today?  2 mins left15:59
sjmc7_if we're done with that, we've tried to discuss this a couple of times, but if people could give some thought to the implemenation around authenticating the service clients i would welcome suggestions; i'm not sure the current method is ideal15:59
sjmc7_currently SL requires admin creds that it uses to intiailize the various clients, and tries to cache a successful auth when the listener's running15:59
*** zeih has quit IRC16:00
sjmc7_it works and it's not insecure but i'd appreciate someone taking a look at it since it was diret from the summit prototype which i didn't put a huge amount of thought or optimization into16:00
*** cloudnull has joined #openstack-meeting-416:00
*** b3rnard0 has joined #openstack-meeting-416:00
TravTok, plz link patch / bp16:00
TravTand we'll call it a meeting16:00
*** odyssey4me has joined #openstack-meeting-416:00
nikhil_kThanks16:00
sjmc7_https://blueprints.launchpad.net/searchlight/+spec/openstack-client-usage16:01
TravTthank everybody.16:01
TravT#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Jul 23 16:01:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-23-15.03.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-23-15.03.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-23-15.03.log.html16:01
cloudnull#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Jul 23 16:01:46 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. 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 Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** lakshmiS has left #openstack-meeting-416:01
*** sjmc7_ has left #openstack-meeting-416:01
palendaeo/16:01
cloudnull#topic rollcall16:02
*** openstack changes topic to "rollcall (Meeting topic: OpenStack Ansible Meeting)"16:02
palendaeo/16:02
Apsuo/16:02
*** TravT has left #openstack-meeting-416:02
d34dh0r53*/16:02
jwagnero/16:02
odyssey4meo/16:02
b3rnard0hello16:03
sigmavirus24o/16:03
*** rromans has joined #openstack-meeting-416:04
* sigmavirus24 clears throat16:05
cloudnullso i guess thats all of us16:05
cloudnull...16:05
cloudnull#topic Review action items from last week16:05
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
*** aruncewind has joined #openstack-meeting-416:05
palendaeGood meeting16:05
sigmavirus24Better than some glance meetings attendance =P16:05
cloudnullRegarding EPOC and pip - add more hours to the day so sigmavirus24 can put together a POC <- sigmavirus2416:06
cloudnull*epoch16:06
sigmavirus24Yeah, I haven't gotten to that yet16:06
*** zeih has joined #openstack-meeting-416:06
sigmavirus24Still need those hours16:06
cloudnull#action add more hours to the day so sigmavirus24 can put together a POC for pip and epoch's16:07
*** TheIntern has quit IRC16:07
*** mstachow has quit IRC16:07
cloudnullcarried16:07
palendaeWould that solely be part of the upgrade script?16:07
palendaeOr changes to yaprt?16:07
cloudnullid assume either can be done.16:07
cloudnullor both .16:07
palendaeOk16:07
cloudnullsigmavirus24:  what did you have in mind16:07
sigmavirus24I was thinking keep it in the upgrade script for now16:08
sigmavirus24Or go for that to see if that alone will work16:08
palendaeMay not be a bad idea to make the master upgrade script be kilo -> liberty at this point16:08
sigmavirus24I don't think yaprt needs this, unless we want to force yaprt to build with epochs16:08
sigmavirus24which will then be something that has to happen for every upgrade after that16:08
palendaeAnd any juno -> kilo upgrade stuff just goes straight to kilo16:08
*** KLevenstein has joined #openstack-meeting-416:09
cloudnullok next item16:09
cloudnullreenable the successerator for a single retry within the gate. To be removed as soon as Ansible v2 drops upstream - someone16:09
cloudnullthis was done.16:09
cloudnull#link https://review.openstack.org/#/c/203257/16:10
*** jwitko has joined #openstack-meeting-416:10
sigmavirus24:thumbsup:16:10
odyssey4me:)16:10
cloudnullnext16:10
cloudnullget a thread going on the mailing list surrounding issues with upgrading Kilo > Liberty - someone16:10
cloudnulland we're carrying that until there are more hours in a day16:10
cloudnull#action get a thread going on the mailing list surrounding issues with upgrading Kilo > Liberty - someone16:10
cloudnullo/ jwitko :)16:11
jwitkoHello!16:11
cloudnull#topic Blueprints16:11
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:11
cloudnull#link https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment-specs,n,z16:11
cloudnullwe have a few open ones, please review them when you get a chance16:12
cloudnullimportant ones IMHO are https://review.openstack.org/#/c/203708/16:12
cloudnullhttps://review.openstack.org/#/c/203706/16:12
cloudnulland https://review.openstack.org/#/c/203754/16:12
cloudnullalso https://review.openstack.org/#/c/202373/116:13
cloudnullwhich is a clean up of the specs dir16:13
palendaeI will commit to getting at least one of those reviewed today16:14
*** serverascode has quit IRC16:14
odyssey4meI've looked through most of them already and have posted some questions. I'll get through a few more tomorrow.16:15
*** serverascode has joined #openstack-meeting-416:15
palendaecloudnull: Does the my.conf one depend on the v10 one at all?16:15
cloudnullpalendae:  no16:15
palendaek16:15
*** s3wong has joined #openstack-meeting-416:16
*** zeih has quit IRC16:16
*** yamamoto has quit IRC16:16
cloudnullalso we have https://review.openstack.org/#/c/205062/ which is a continuation of the work done by svg16:17
cloudnull#link https://review.openstack.org/#/c/181957/16:17
*** Slower has quit IRC16:18
*** Bjoern_ has quit IRC16:18
cloudnull#topic Reviews16:18
*** openstack changes topic to "Reviews (Meeting topic: OpenStack Ansible Meeting)"16:18
cloudnullanything that we want to highlight regarding open reviews ?16:19
odyssey4mecloudnull I think that https://review.openstack.org/#/c/205062/ is a spec by our team to cover the work done by svg, but with our revisions in it16:19
cloudnullyes16:20
odyssey4meit'll become the blueprint for that work - the team will revise svg's patch and bring it up to date and do some heavy testing on it16:20
cloudnull++16:20
cloudnullin our open reviews we have a few inflight that would be good to get nailed down soon-ish https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z16:22
*** Bjoern_ has joined #openstack-meeting-416:22
cloudnulldoes anyone have any issues with backporting https://review.openstack.org/#/c/205008/ https://review.openstack.org/#/c/205056/ and https://review.openstack.org/#/c/204996/16:23
cloudnulli'd like to have them in Kilo, to rid ourselves of key distribution issues.16:23
odyssey4mecloudnull I'm happy with that - I'm surprised that they built first time!16:24
cloudnull#startvote Should we backort the new key distribution process? Yes, No, Maybe16:24
openstackBegin voting on: Should we backort the new key distribution process? Valid vote options are Yes, No, Maybe.16:24
openstackVote using '#vote OPTION'. Only your last vote counts.16:24
odyssey4me#vote yes16:25
cloudnull#vote yes16:25
andymccr#vote yes16:25
d34dh0r53#vote yes16:25
palendae#vote yes16:25
Apsu#vote yes16:25
cloudnull#showvote16:26
openstackYes (6): d34dh0r53, palendae, odyssey4me, andymccr, Apsu, cloudnull16:26
cloudnullok i think its safe to say its a yes.16:26
cloudnull#endvote16:26
openstackVoted on "Should we backort the new key distribution process?" Results are16:26
openstackYes (6): d34dh0r53, palendae, odyssey4me, andymccr, Apsu, cloudnull16:26
andymccrdone :D16:26
*** FallenPegasus has joined #openstack-meeting-416:26
cloudnull#action backport https://review.openstack.org/#/c/205008/ https://review.openstack.org/#/c/205056/ and https://review.openstack.org/#/c/204996/ to kilo - someone16:27
andymccralready done16:27
cloudnullsweet16:27
cloudnull#topic Open discussion16:28
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:28
cloudnullwhat do we want to talk about? its time for festivus .16:28
odyssey4mewe could do with some eyes on https://review.openstack.org/194474 - the Keystone SSL cert/key distribution16:28
odyssey4methat review brings that into line with the same mechanism as is used for horizon and fixes a lot of the brokenness16:29
odyssey4meit also appropriately fixes the haproxy configuration depending on whether you have Keystone setup with SSL or not16:29
*** agalkin has quit IRC16:30
cloudnullcan we modify the commit to use the process outlined by andymccr which is being done in swift ? or do you think that can be done in a dependent patch ?16:30
cloudnullfor ssl cert sync16:31
odyssey4mecloudnull this one's thoroughly tested and consistent with all other ssl cert distributions16:31
odyssey4meI'd like to try out the method discussed with andymccr, but that'll be when there's time for that in a subsequent patch.16:31
odyssey4methis one works as-is and fixes a lot of broken16:32
andymccryeh i think if its working now lets mark as "to do:" work and get it done at some point16:32
cloudnullok16:32
cloudnullill get a review in on all that today16:33
odyssey4methanks16:33
cloudnulleveryones favorite topic https://review.openstack.org/#/c/204315/16:33
sigmavirus24cloudnull: oh?16:34
*** lexholden has quit IRC16:34
sigmavirus24I don't recall that being my favorite topic =P16:34
cloudnulltrying to make gate runs happier in hpb416:34
cloudnullyou kno w you love it :)16:34
sigmavirus24Oh hpb4 is my favorite topic. Carry on =P16:34
cloudnullthis forces an update to happen in all containers and logs all the things in a new gate directory "http://logs.openstack.org/15/204315/8/check/os-ansible-deployment-dsvm-check-commit/a495ded/logs/ansible_cmd_logs/"16:35
odyssey4mecloudnull not the neatest of logs, but something's better than nothing16:35
cloudnullyea the ansible return data is kinda shit to read16:35
*** Slower has joined #openstack-meeting-416:36
sigmavirus24cloudnull: do we want to recheck that until we get it to hpb4?16:36
sigmavirus24last run was against raxdfw16:36
odyssey4meI don't think so - the best way we're going to get it running on hpcloud-b4 is to merge it in16:36
*** xingchao has joined #openstack-meeting-416:37
sigmavirus24odyssey4me: I saw one of the last rechecks was "recheck -hp1 success"16:37
sigmavirus24so I figured we could keep rolling the nodepool dice16:37
*** jckasper has quit IRC16:37
cloudnullodyssey4me:  i think i can make the return output from ansible better if i add in "--one-line" to the ansible commands16:37
cloudnullit will be a lot to read on oneline however it wont be something like http://logs.openstack.org/15/204315/8/check/os-ansible-deployment-dsvm-check-commit/a495ded/logs/ansible_cmd_logs/force_apt_update/aio1_memcached_container-541276d916:38
*** KunalGandhi has joined #openstack-meeting-416:38
cloudnullyoure call. if you think it best to rev it16:38
Apsucloudnull: Why not pipe to python -m json.tool to format it a little?16:38
cloudnulleach log file is generated with per node.16:39
cloudnulli guess we could do a post process16:39
odyssey4mecloudnull I think it's fine as-is and can be improved in a later patch16:40
cloudnullok16:40
odyssey4mefor now we need some sort of diagnostics for hpcloud-b416:40
cloudnull++16:40
cloudnulli hate hpb4 .. .16:40
odyssey4meand we won't be getting it unless we recheck ad nauseum, or merge it16:40
cloudnullokiedokie typie typie make it go :)16:40
cloudnullwhat else we got ?16:41
odyssey4mesigmavirus24 made it go :)16:41
cloudnullsigmavirus24: for PTL16:41
cloudnull:)16:41
sigmavirus24of?16:41
cloudnullyes16:41
sigmavirus24-_-16:41
*** FallenPegasus is now known as MarkAtwood16:41
*** xingchao has quit IRC16:42
cloudnullah liberty keystone is unhappy here https://review.openstack.org/#/c/199126/16:42
cloudnullif someone is board it would be a great help to get that narrowed down16:42
cloudnullif its an upstream issue or an us issue, idk16:43
*** TheIntern has joined #openstack-meeting-416:43
odyssey4mecloudnull on another issue - upstream kilo merged the urllib cap, do you plan to rev the SHA's next week? if so, we can remove our cap in the same review16:44
cloudnullah good point,16:44
cloudnulli plan on being on vacation next week16:44
cloudnull:)16:44
cloudnullmaybe we rev it today16:45
odyssey4mecloudnull ah ok, we can chat a bit after this then - we have a few things to sort out for your absence16:45
cloudnulland remove our cap16:45
*** TheIntern has quit IRC16:45
cloudnullFYI odyssey4me will be handling bussiness while im gone.16:45
ApsuMeet the new boss, same as the old boss16:47
b3rnard0what can possible go wrong?16:48
d34dh0r53I for one welcome our UK overlords16:48
Apsu^16:48
d34dh0r53b3rnard0: you could forget a y?16:48
odyssey4melol16:49
odyssey4meI suppose that we're done here?16:49
cloudnullyup16:50
cloudnullthanks everyone16:50
cloudnull#endmeeting16:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:50
openstackMeeting ended Thu Jul 23 16:50:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-23-16.01.html16:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-23-16.01.txt16:50
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-23-16.01.log.html16:50
*** odyssey4me has left #openstack-meeting-416:50
*** yamamoto has joined #openstack-meeting-416:51
*** LouisF has joined #openstack-meeting-416:52
*** vikram has joined #openstack-meeting-416:54
*** dahoo has joined #openstack-meeting-416:56
*** dahoo is now known as jerryz16:56
*** carl_baldwin has quit IRC16:57
*** Mohankumar__ has joined #openstack-meeting-416:59
*** jwarendt has joined #openstack-meeting-417:00
*** puranamr has joined #openstack-meeting-417:01
*** cathy_ has joined #openstack-meeting-417:01
cathy_startmeeting service_chaining17:01
cathy_#startmeeting service_chaining17:02
openstackMeeting started Thu Jul 23 17:02:07 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: service_chaining)"17:02
openstackThe meeting name has been set to 'service_chaining'17:02
s3wonghello17:02
cathy_hi everyone17:02
*** puranamr has quit IRC17:02
LouisFhi17:02
pcarverhi17:02
Mohankumar__hi17:02
vikramhi17:02
cathy_good let's start17:03
*** jasondotstar has quit IRC17:03
*** puranamr has joined #openstack-meeting-417:03
*** bouthors_ has joined #openstack-meeting-417:03
*** johnsom has joined #openstack-meeting-417:03
cathy_we posted a new patch for the API spec to address Sean's comment on adding the API URL table. Have you got a chance to review it?17:03
LouisF#link https://review.openstack.org/#/c/20469517:03
*** AlanClark has joined #openstack-meeting-417:03
LouisFthis adds detail on the url and resource endpoints17:04
cathy_sc68cal: are you there?17:04
s3wongLouisF: may want to just add sc68cal as reviewer, so it would be on his review queue17:05
cathy_s3wong: good point. will do17:05
sc68callooking now17:05
pcarverI missed that one, but looking at it now I like it. I'll spend a little more time later before putting in a review.17:06
cathy_anything you folks would like to discuss in today's meeting? We have a wiki page posted in last IRC meeting. you can go there to add items you would like to discuss in the coming IRC meeting17:06
vikramcathy_: will review it17:06
*** zehicle_IRL has quit IRC17:06
sc68calI have an item17:06
cathy_pcarver: thanks.17:06
cathy_vikram: thanks17:06
sc68calCan we get some cross-collaboration on this spec? https://review.openstack.org/18666317:07
s3wongsc68cal: that was fast :-)17:07
cathy_sc68cal: I am looking at that spec.17:07
sc68cals3wong: well my objection was just that the info was in a wiki, not in the actual API spec - it wasn't an objection to the API overall17:07
s3wongsc68cal: sure17:08
sc68calhttps://review.openstack.org/186663 - I would like to see just one API for forwarding and forwarding-like things17:08
pcarverinteresting. That does seem like it overlaps17:08
sc68calyes they may be slightly different - re the whole chain concept but we don't benefit from having multiple ways to express similar concepts17:08
cathy_sc68cal: yes, we have been collaborating with that spec. Vikram had worked with Yuji of that spec on reaching consensus on the Classifier API we put in the service chain spec.17:08
s3wongsc68cal: we do also --- the tradeoff however is that networking-sfc would have a dependency on this to land17:09
vikramcathy_: this is another spec..17:09
cathy_sc68cal: if you look at previous meeting logs, we have discussion on that and community consensus on that17:09
vikramsc68cal: i feel this spec is unrelated to service function chaining17:09
vikramspec just try to provide a way in which a transparent packet can be directed to a particular dest-port. Here the idea of chain is not involved as the packet will only be routed from a particular source to the required destination.17:10
LouisFvikram: agree - it addresses filtering but not service chaining17:10
cathy_sc68cal: Sorry this seems another spec, not the one Yuji posted on flow classifier. Sorry for the confusion17:10
vikramsc68cal: what is your felling?17:10
vikram*felling17:11
LouisFthe common classifier spec is https://review.openstack.org/#/c/190463/17:11
vikrami am really bad at spellings :-)17:11
s3wongsc68cal: though mestery and armax are on the reviewers list, I don't see a whole lot of core awareness on this effort --- so definitely a bit concerning if we make this a dependency17:11
pcarvervikram: it's not the same but it has a lot in common. If we're going to have both there will need to be extremely clear documentation to guide operators and tenants on when to use each.17:11
*** dims_ has quit IRC17:12
pcarverEspecially if the two can interact in unpredictable ways17:12
vikrampcarver: i agree..17:12
sc68calI just feel like there are some things that are in common, the idea of redirecting traffic - the mechanics may be different but I don't like this idea of "oh it's just a little bit different, therefore a whole new separate API is justified"17:12
vikramsc68cal: hmmmm17:12
pcarvercathy_: I understand the desire to not have too many dependencies, but it may make sense to have a have one be a degenerate case of the other17:13
vikramsc68cal: we can hold it unless we have a definite usecase which could not be resolved using service function chaining17:13
cathy_sc68cal: +117:13
pcarveras opposed to two unrelated things that appear similar to the user17:13
LouisFsc68cal: the sfc is more general than the forwarding spec17:14
*** MarkAtwood has quit IRC17:14
LouisFits functionality can be covered by the sfc spec17:14
vikramsc68cal, pcarver: I agree, service function chaining can achieve the use case defined in forwarding spec17:14
pcarverLouisF, vikram: I haven't reviewed 186663 before looking at it just now, but is there a reason why it couldn't be implemented as a trivially simple service chain?17:15
vikramHow about holding it unless we have a definite usecase which could not be resolved using service function chaining17:15
s3wongpcarver: in theory I 100% agree with not duplicate effort. But we also understand that merging things in Neutron is of a different pace than merging things in networking-sfc (the point of separate repo is to iterate faster)17:15
cathy_vikram:agree with you. Would you like to talk with Yuji on that ?17:15
vikrampcarver: I believe it can17:15
LouisFpcarver: yes I think that can be done17:15
*** vishwanathj has quit IRC17:15
sc68calyeah I mean I could be stupid but the forwarding API is basically just a chain of 117:16
vikramcathy_: We can put our concerns over the etherpad link shared for this spec17:16
sc68caland BTW - fwaas is going to be a chain of 117:16
vikramhttps://etherpad.openstack.org/p/forwarding-rule17:16
sc68calif we're inserting a firewall between an instance and the rest of the network17:16
sc68calI had hoped to consume SFC, to look into making fwaas more flexible17:16
vikramsc68cal:+++10017:17
pcarversc68cal: +1, security functions are a primary example of the reason for SFC, although not all chained functions are firewallish17:17
*** dannywilson has quit IRC17:17
jwarendt+117:17
*** dannywilson has joined #openstack-meeting-417:18
*** jaypipes has joined #openstack-meeting-417:18
*** padkrish has joined #openstack-meeting-417:18
cathy_So we all agree that the service chain API can cover the functionality needed in https://review.openstack.org/#/c/186663/17:18
*** asselin__ has joined #openstack-meeting-417:18
*** DericHorn-HP has joined #openstack-meeting-417:18
LouisF+117:18
*** harshs has joined #openstack-meeting-417:18
pcarverI'm also hearing requirements from the NFV side wanting to replicate hub and spoke topologies. I'm viewing that also as a subset of SFC17:18
*** asselin_ has quit IRC17:19
sc68calpcarver: agreed17:19
cathy_#agreed the service chain API can cover the functionality needed in https://review.openstack.org/#/c/186663/17:19
cathy_So how should we make sure there is no duplicate API? Maybe Vikram can communicate this with Yuji? Suggestion?17:21
sc68calI'd say maybe an e-mail to the ML, with the results of this meeting, and say that we want to try and converge where there is commonality17:22
*** coolsvap|away is now known as coolsvap17:22
vikramcathy_: sure.. i have posted a comment on the spec.. will try to catch him tomorrow over IRC as wekk17:22
cathy_sc68cal: agree.17:22
pcarvercathy_: I haven't gone through the review in detail, but I'm thinking that it might not be wrong to have a sort of a wrapper for specific subcases. What I wouldn't want to see is uncoordinated duplication of effort.17:23
cathy_#action Cathy send an email to ML summarizing the consensus that the service chain API can cover the functionality needed in https://review.openstack.org/#/c/186663/17:23
pcarverIt may be that 186663 shouldn't just be abandoned, but revised to be based on SFC17:24
cathy_#action: Vikram try to catch him tomorrow over IRC and pass our consensus to him, get his input.17:24
*** sbalukoff has quit IRC17:24
*** yamamoto has quit IRC17:24
*** yamahata has quit IRC17:25
cathy_pcarver: OK with me . You may want to post that suggestion to that spec17:25
s3wongpcarver: but you are still advocating that the forwarding-rules/classifier effort be done on Neutron repo?17:25
*** padkrish has quit IRC17:26
pcarvers3wong: Not advocating anything specific yet. I haven't read the 186663 spec yet.17:26
pcarvercathy_: I will review that spec and post my thoughts17:26
*** padkrish has joined #openstack-meeting-417:26
cathy_pcarver: good. thanks. I think the key is not to have duplicate APIs to confuse the community.17:27
cathy_sc68cal: Thanks for starting this discussion topic!17:27
sc68calnp17:28
cathy_any other topic you folks would like to discuss?17:28
pcarverI've been looking at Google search results related to Neutron service chaining. I'm thinking we need to do some cleanup.17:29
pcarverThe top results tend to show up obsolete information17:29
pcarverLouis' abandonded spec for example, and a wiki with old info and an outdated document17:29
*** padkrish_ has joined #openstack-meeting-417:29
pcarvere.g. https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining17:29
s3wongpcarver: yeah, the top result (https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining) has been obsolete since Juno...17:30
pcarverI'm going to start doing a little editing, but it would be good if other people took a look too17:30
cathy_pcarver: not sure how to fix that? Any clue?17:30
*** padkrish has quit IRC17:30
LouisFthat work was started some ago and was abandoned17:30
pcarverThe wiki is easy. Launchpad also. Gerrit I'm not sure17:31
*** malini__ has quit IRC17:31
pcarverAnybody good with Gerrit URLs?17:31
cathy_pcarver: so you are going to fix the search result of wiki and launchpad?17:32
cathy_pcarver: I will talk with you offline about how to fix that. I would like to learn:-)17:32
pcarverThis blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-api-extension-for-service-chaining lists this URL: https://review.openstack.org/#/q/topic:bp/neutron-api-extension-for-service-chaining,n,z17:32
s3wongcathy_: I think pcarver is going to remove the wiki and launchpad pages :-)17:32
s3wongGoogle search / cache, we can't do much about...17:33
pcarveranybody know the correct URL to replace that so that it shows the new spec rather than the abandoned one?17:33
cathy_pcarver: I can fix that17:33
cathy_#action cathy modify the BP to reference the new spec17:34
cathy_s3wong: :-)17:34
*** Slower has quit IRC17:34
cathy_how is the dependency issue of the Neutron SC client on the base code going? Vikram: any update?17:35
vikramresolved:-)17:35
cathy_vikram: Cool !17:35
vikramthanks to amotoki17:35
Mohankumar__yes , We got solution for base dependecency issue( by adding requirements in requirements.txt)17:35
s3wongpcarver: https://review.openstack.org/#/c/192933/17:35
vikramwe need to add something in test-requirement.txt17:35
cathy_Mohankumar__: great. that simple :-)17:35
Mohankumar__cathy_ yes :)17:36
pcarvers3wong: That URL is in there, but it's a different view than the other one17:36
pcarvers3wong: That URL is listed as "Addressed by" whereas the incorrect URL is listed as "Gerrit topic"17:37
pcarverOh, I think I just figured it out17:37
pcarverOur topic is someone confusingly called "initial-manifesto"17:37
pcarverthe incorrect one is called neutron-api-extension-for-service-chaining17:38
cathy_pcarver: ?17:38
s3wongpcarver: yeah, I noticed that a while back :-)  was wondering what the heck does that mean...17:38
s3wongwhat is the official "Topic"?17:38
*** lexholden has joined #openstack-meeting-417:39
cathy_pcarver: could you clarify what you are talking about?17:39
pcarverIt looks like blueprints typically list a Gerrit search URL at the top followed by a series of "Addressed by" links to specific URLs17:39
pcarvercathy_: take a look at https://blueprints.launchpad.net/neutron/+spec/neutron-api-extension-for-service-chaining and scroll down to the Whiteboard section17:40
pcarvercathy_: Note that there are two URLs, one "Gerrit topic" and one "Addressed by"17:40
pcarverThe "Gerrit topic" is actually a dynamic query that hits on Louis' abandoned changed17:41
*** MarkAtwood has joined #openstack-meeting-417:41
s3wongyeah, so fixing the Gerrit topic link should suffice17:41
LouisFpcarver: will fix17:41
cathy_So we need to change the Gerrit topic to the new one, right? We cna manually change that I assume?17:41
pcarverThe Addressed by is a correct link to our merged spec17:41
pcarvercathy_: I think the correct link to replace the Gerrit topic is: https://review.openstack.org/#/q/status:merged+project:openstack/networking-sfc+branch:master+topic:initial-manifesto,n,z17:42
*** aruncewind has quit IRC17:42
*** lexholden has quit IRC17:42
*** dwalleck has joined #openstack-meeting-417:42
pcarverit's just a little weird because the actual topic name isn't as natural17:42
*** dwalleck has quit IRC17:43
cathy_pcarver: So we might need to make the topic name natural17:43
*** TheIntern has joined #openstack-meeting-417:43
*** dwalleck has joined #openstack-meeting-417:43
cathy_otherwise it is confusing.17:43
pcarvercathy_: I'm not sure it's worth changing17:43
s3wongwhat's wrong with initial-manifesto?   :-)17:43
pcarverI was just commenting that it's a bit odd17:44
cathy_s3wong: what is meant by initial-manifesto? I did not pay attention to this before17:45
*** dims has joined #openstack-meeting-417:45
s3wongcathy_: look at the "Topic" field at the gerrit for the API spec (https://review.openstack.org/#/c/192933/)17:45
pcarverLouisF: Did you just update the blueprint? I don't think that's quite right. I think we want it to list all the reviews including the one that just merged.17:46
s3wong"initial-manifesto"17:46
LouisFpcarver: ok17:47
cathy_pcarver: I agree we should list both specs which have many comments since the new one is a rebase of the old one.17:47
cathy_#action Louis update the BP to refer to both specs which have all the reviews17:48
pcarverAnd multiple links to the correct info should help improve the ranking in search engine results. I'll update the wiki to point to the blueprint and the API spec17:48
cathy_pcarver: Thanks!17:49
cathy_#action pcarver updates the wiki to point to the blueprint and the API spec17:49
*** yamahata has joined #openstack-meeting-417:49
cathy_Just an update on the API implementation. We are almost done and will post it for review mid next week.17:50
*** dwalleck has quit IRC17:50
*** vishwanathj has joined #openstack-meeting-417:51
cathy_Any other issues for discussion?17:51
pcarvercathy_: roughly where in the code are you working on the implementation?17:51
cathy_pcarver: not sure what you mean?17:51
s3wongcathy_: may be worthwhile to put unfinished patches on gerrit for early review (with workflow set to -1)17:52
pcarverI mean where is the flow table manipulation happening?17:52
cathy_pcarver: We will add SFC API handling and DB codes in the Neutron Server17:52
s3wongpcarver: flow table? the OVS flow table?17:53
pcarverI'm not sure if we'll be able to leverage any of it, but AT&T is in the process of open sourcing some code we did for a number of OvS manipulations including flow steering17:53
cathy_pcarver: that is in the OVS Agent on the compute node in the data path if I understand your quesiton correctly17:53
pcarvers3wong: Yes, I'm asking about the actual mechanics of the implementation17:53
LouisFpcarver: is you can share that would be useful17:53
LouisFif17:53
s3wongpcarver: and the code you guys will open-source is not OpenStack related code?17:54
pcarverLouisF: I'll share once we get it out in the open. It's software that started out in AT&T Labs research for QoS and was subsequently enhanced for flow steering and some work has been looked at for port mirroring17:54
*** SumitNaiksatam has joined #openstack-meeting-417:54
LouisFpcarver: great17:54
*** yamahata has quit IRC17:55
pcarvers3wong: correct. It was built to work with OpenStack (uses Keystone and Neutron APIs) but manipulates OvS independently of Neutron.17:55
*** yamahata has joined #openstack-meeting-417:55
pcarverWe just recently got VP approval to open source it, but it needs to be cleaned up before release17:55
pcarvermostly on the documentation side from what I understand17:55
cathy_I aasume that in AT&T codes, the OVS Driver and OVS Agent will coordinate together and program the OVS flow table?17:56
LouisFcan it operate on conjunction with neutron control of ovs?17:56
LouisFin conjunction17:56
s3wongpcarver: sounds good. Looking forward to seeing it out in the open. Please share with us the github link (I assume you guys will put it on github) once it become available. Thanks!17:56
pcarvercathy_: I haven't seen exactly what's being released. The original implemenation used Floodlight, but there have been changes since then.17:56
cathy_pcarver: Ok.17:57
pcarverI don't think we would leverage it as a whole, but maybe we can gain something from it. I'm talking to the people who developed it.17:57
cathy_time is up. Could everyone please go to the new spec patch to review it?17:57
cathy_I mean review it as soon as possible17:57
pcarverLouisF: For the limited use we're using it for, yes.17:57
Mohankumar__cathy_ okay , sure !17:58
cathy_Thanks everyone for joining the meeting. By for now17:59
LouisFbye17:59
s3wongthanks. bye!17:59
jwarendtbye17:59
Mohankumar__bye17:59
vikrambye17:59
*** vikram has quit IRC17:59
*** bouthors_ has quit IRC17:59
cathy_#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Jul 23 18:00:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-23-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-23-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-23-17.02.log.html18:00
*** jckasper has joined #openstack-meeting-418:00
*** ivar-lazzaro has joined #openstack-meeting-418:01
*** cathy_ has quit IRC18:01
*** ivar-lazzaro has quit IRC18:02
*** ivar-lazzaro has joined #openstack-meeting-418:03
*** dwalleck has joined #openstack-meeting-418:04
*** jckasper has quit IRC18:05
*** carl_baldwin has joined #openstack-meeting-418:10
*** Mohankumar__ has quit IRC18:11
*** dwalleck has quit IRC18:16
*** jckasper has joined #openstack-meeting-418:17
*** carl_baldwin has quit IRC18:20
*** Slower has joined #openstack-meeting-418:22
*** Slower has quit IRC18:22
*** Slower has joined #openstack-meeting-418:22
*** dwalleck has joined #openstack-meeting-418:23
*** MarkAtwood has quit IRC18:29
*** yamamoto has joined #openstack-meeting-418:31
*** MarkAtwood has joined #openstack-meeting-418:32
*** rromans has left #openstack-meeting-418:32
*** vivek-ebay has joined #openstack-meeting-418:34
*** vivek-ebay has quit IRC18:34
*** vivek-ebay has joined #openstack-meeting-418:35
*** carl_baldwin has joined #openstack-meeting-418:35
*** lazy_prince has quit IRC18:36
*** yamamoto has quit IRC18:36
*** geoffarnold has quit IRC18:42
*** jaypipes has quit IRC18:44
*** zehicle_IRL has joined #openstack-meeting-418:44
*** dwalleck has quit IRC18:45
*** dwalleck has joined #openstack-meeting-418:46
*** sbalukoff has joined #openstack-meeting-418:46
*** carl_baldwin has quit IRC18:46
*** dwalleck has quit IRC18:54
*** dwalleck has joined #openstack-meeting-418:55
*** bitblt has joined #openstack-meeting-418:55
*** vivek-ebay has quit IRC18:57
*** davi8784 has joined #openstack-meeting-418:57
*** bitblt has quit IRC18:58
*** dwalleck has quit IRC18:58
*** VW_ has quit IRC18:58
*** TheIntern has quit IRC18:59
*** Sukhdev_ has joined #openstack-meeting-418:59
*** VW_ has joined #openstack-meeting-418:59
*** VW_ has quit IRC18:59
*** VW_ has joined #openstack-meeting-418:59
*** dwalleck has joined #openstack-meeting-419:00
*** dwalleck has quit IRC19:02
*** b3rnard0 has left #openstack-meeting-419:02
*** dwalleck has joined #openstack-meeting-419:03
*** zehicle_IRL has quit IRC19:04
*** dwalleck has quit IRC19:05
*** galstrom_zzz is now known as galstrom19:09
*** ivar-laz_ has joined #openstack-meeting-419:10
*** DericHorn-HP has quit IRC19:13
*** MarkAtwood has quit IRC19:13
*** ivar-lazzaro has quit IRC19:14
*** igordcard_ has quit IRC19:15
*** davi8784 has quit IRC19:17
*** puranamr has quit IRC19:19
*** ajayaa has quit IRC19:22
*** puranamr has joined #openstack-meeting-419:22
*** ivar-laz_ has quit IRC19:27
*** ivar-lazzaro has joined #openstack-meeting-419:27
*** LouisF has quit IRC19:28
*** ivar-lazzaro has quit IRC19:32
*** Brian___ has joined #openstack-meeting-419:33
*** Brian___ has quit IRC19:38
*** DericHorn-HP has joined #openstack-meeting-419:40
*** DericHorn-HP has quit IRC19:44
*** DericHorn-HP has joined #openstack-meeting-419:45
*** SumitNaiksatam has quit IRC19:47
*** geoffarnold has joined #openstack-meeting-419:52
*** padkrish_ has quit IRC19:55
*** padkrish has joined #openstack-meeting-419:56
*** padkrish has quit IRC19:56
*** padkrish has joined #openstack-meeting-419:57
*** dims has quit IRC19:58
*** geoffarnold has quit IRC19:58
*** asselin__ has quit IRC20:00
*** ivar-lazzaro has joined #openstack-meeting-420:03
*** dwalleck has joined #openstack-meeting-420:07
*** padkrish has quit IRC20:08
*** padkrish has joined #openstack-meeting-420:08
*** puranamr has quit IRC20:09
*** DericHorn-HP has quit IRC20:12
*** padkrish has quit IRC20:13
*** ivar-lazzaro has quit IRC20:13
*** johnsom has left #openstack-meeting-420:14
*** harshs has quit IRC20:15
*** SumitNaiksatam has joined #openstack-meeting-420:21
*** lexholden has joined #openstack-meeting-420:25
*** nkrinner has quit IRC20:25
*** SumitNaiksatam has quit IRC20:26
*** ivar-lazzaro has joined #openstack-meeting-420:31
*** padkrish has joined #openstack-meeting-420:36
*** dwalleck has quit IRC20:36
*** vivek-ebay has joined #openstack-meeting-420:38
*** markvoelker has quit IRC20:42
*** ivar-lazzaro has quit IRC20:47
*** ivar-lazzaro has joined #openstack-meeting-420:48
*** jwagner is now known as jwagner_away20:50
*** vivek-ebay has quit IRC20:50
*** ivar-lazzaro has quit IRC20:52
*** rfolco has quit IRC20:55
*** puranamr has joined #openstack-meeting-420:57
*** Sukhdev_ has quit IRC20:59
*** padkrish has quit IRC20:59
*** dannywil_ has joined #openstack-meeting-420:59
*** igordcard_ has joined #openstack-meeting-421:00
*** padkrish has joined #openstack-meeting-421:00
*** VanL has joined #openstack-meeting-421:01
*** dannywilson has quit IRC21:01
*** blahRus has joined #openstack-meeting-421:01
*** padkrish_ has joined #openstack-meeting-421:02
*** padkrish has quit IRC21:03
*** jckasper has quit IRC21:07
*** ivar-lazzaro has joined #openstack-meeting-421:13
*** Sukhdev_ has joined #openstack-meeting-421:14
*** ivar-lazzaro has quit IRC21:17
*** vivek-ebay has joined #openstack-meeting-421:27
*** VanL has quit IRC21:30
*** bknudson has quit IRC21:31
*** VW_ has quit IRC21:32
*** DericHorn-HP has joined #openstack-meeting-421:33
*** VW_ has joined #openstack-meeting-421:33
*** jasondotstar has joined #openstack-meeting-421:36
*** MarkAtwood has joined #openstack-meeting-421:36
*** VW_ has quit IRC21:37
*** VW_ has joined #openstack-meeting-421:40
*** dannywil_ has quit IRC21:40
*** MarkAtwood has quit IRC21:41
*** VanL has joined #openstack-meeting-421:42
*** pleia2 has quit IRC21:42
*** sigmavirus24 is now known as sigmavirus24_awa21:43
*** TheIntern has joined #openstack-meeting-421:44
*** padkrish_ has quit IRC21:48
*** dannywilson has joined #openstack-meeting-421:51
*** klamath has quit IRC21:53
*** kevinbenton has quit IRC22:01
*** igordcard_ has quit IRC22:07
*** cloudnull is now known as cloudull_zzz22:08
*** igordcard_ has joined #openstack-meeting-422:08
*** DericHorn-HP has quit IRC22:08
*** DericHorn-HP has joined #openstack-meeting-422:10
*** geoffarnold has joined #openstack-meeting-422:10
*** igordcard_ has quit IRC22:12
*** igordcard_ has joined #openstack-meeting-422:12
*** AlanClark has quit IRC22:13
*** KLevenstein has quit IRC22:15
*** pleia2 has joined #openstack-meeting-422:16
*** bnemec has quit IRC22:18
*** TheIntern has quit IRC22:19
*** Brian___ has joined #openstack-meeting-422:22
*** igordcard_ has quit IRC22:23
*** igordcard_ has joined #openstack-meeting-422:24
*** Brian___ has quit IRC22:27
*** dims has joined #openstack-meeting-422:39
*** CheKoLyN has joined #openstack-meeting-422:40
*** jasondotstar has quit IRC22:40
*** geoffarnold has quit IRC22:41
*** ivar-lazzaro has joined #openstack-meeting-422:42
*** carl_baldwin has joined #openstack-meeting-422:44
*** galstrom is now known as galstrom_zzz22:52
*** aventerav has quit IRC22:58
*** banix has quit IRC23:00
*** coolsvap is now known as coolsvap|away23:00
*** david-lyle has quit IRC23:02
*** MarkAtwood has joined #openstack-meeting-423:03
*** ssd has joined #openstack-meeting-423:04
*** padkrish has joined #openstack-meeting-423:04
*** padkrish has joined #openstack-meeting-423:05
*** ssd has quit IRC23:05
*** carl_baldwin has quit IRC23:06
*** lexholden has quit IRC23:08
*** ashuk has joined #openstack-meeting-423:10
*** Bjoern_ has quit IRC23:10
*** VW_ has quit IRC23:12
*** VW_ has joined #openstack-meeting-423:13
*** Sukhdev_ has quit IRC23:14
*** VW_ has quit IRC23:17
*** dims_ has joined #openstack-meeting-423:24
*** harshs has joined #openstack-meeting-423:24
*** DericHorn-HP has quit IRC23:24
*** dims has quit IRC23:27
*** VW_ has joined #openstack-meeting-423:27
*** bknudson has joined #openstack-meeting-423:31
*** VanL has quit IRC23:34
*** david-lyle has joined #openstack-meeting-423:36
*** asselin has quit IRC23:44
*** blahRus has quit IRC23:45
*** rfolco has joined #openstack-meeting-423:45
*** dims_ has quit IRC23:46
*** MarkAtwood has quit IRC23:51
*** MarkAtwood has joined #openstack-meeting-423:56
*** jasondotstar has joined #openstack-meeting-423:56
*** dannywilson has quit IRC23:57
*** salv-orlando has quit IRC23:58

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