Thursday, 2016-03-31

*** akanksha_ has joined #openstack-searchlight00:26
*** itisha has joined #openstack-searchlight00:47
*** yingjun has joined #openstack-searchlight00:49
*** bpokorny_ has joined #openstack-searchlight01:12
*** bpokorny has quit IRC01:15
*** bpokorny_ has quit IRC01:16
*** bpokorny has joined #openstack-searchlight02:32
*** akanksha_ has quit IRC02:57
*** itisha has quit IRC02:59
*** bpokorny has quit IRC03:01
*** krotscheck has joined #openstack-searchlight03:30
*** krotscheck_dcm has quit IRC03:32
*** bpokorny has joined #openstack-searchlight03:40
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973303:41
*** bpokorny has quit IRC04:08
*** bpokorny has joined #openstack-searchlight04:24
*** TravT_ has joined #openstack-searchlight04:41
*** TravT has quit IRC04:43
*** bpokorny has quit IRC04:47
*** nikhil has quit IRC05:13
*** nikhil has joined #openstack-searchlight05:14
*** GB21 has joined #openstack-searchlight05:22
*** GB21 has quit IRC05:35
*** pcaruana has quit IRC05:49
*** GB21 has joined #openstack-searchlight06:31
*** pcaruana has joined #openstack-searchlight07:41
*** GB21 has quit IRC07:45
*** briancli1e has quit IRC08:12
*** briancline has joined #openstack-searchlight08:13
*** GB21 has joined #openstack-searchlight08:30
*** yingjun has quit IRC09:24
*** exploreshaifali has joined #openstack-searchlight09:36
*** GB21 has quit IRC10:41
*** GB21 has joined #openstack-searchlight11:00
*** TravT_ has quit IRC11:17
*** TravT has joined #openstack-searchlight11:18
*** dhellmann has quit IRC11:22
*** dhellmann_ has joined #openstack-searchlight11:22
*** dhellmann_ is now known as dhellmann11:26
*** yingjun has joined #openstack-searchlight11:57
*** GB21 has quit IRC12:05
*** exploreshaifali has quit IRC12:44
*** exploreshaifali has joined #openstack-searchlight12:56
*** exploreshaifali has quit IRC13:19
*** yingjun has quit IRC13:19
*** yingjun has joined #openstack-searchlight13:20
*** yingjun has quit IRC13:24
*** sigmavirus24_awa is now known as sigmavirus2414:05
*** sigmavirus24 is now known as sigmavirus24_awa14:14
*** sigmavirus24_awa is now known as sigmavirus2414:15
sjmc7rosmaita: when you have a sec, could i trouble you for your blessing on https://review.openstack.org/#/c/298315? adds some missing documentation i’d like to get in for rc214:43
* rosmaita looking14:44
sjmc7ta14:49
rosmaitasjmc7: may take a bit, i am in 2 concurrent meetings atm14:52
sjmc7only two? :)  no rush14:53
*** lei-zh has joined #openstack-searchlight14:59
TravTCourtesy Searchlight meeting reminder in #openstack-meeting-4: lakshmiS, nikhil_k, rosmaita, TravT, david-lyle, sjmc7, abhijeetm, itisha, GB21, briancline, lei-zh, yingjun, RickA-HP15:00
*** yingjun has joined #openstack-searchlight15:00
*** bpokorny has joined #openstack-searchlight15:24
*** bpokorny has quit IRC15:28
*** bpokorny has joined #openstack-searchlight15:30
openstackgerritMerged openstack/searchlight: Add missing zero-downtime indexing documentation  https://review.openstack.org/29831515:38
*** sigmavirus24 is now known as sigmavirus24_awa15:38
*** sigmavirus24_awa is now known as sigmavirus2415:40
*** sigmavirus24 is now known as sigmavirus24_awa15:41
*** sigmavirus24_awa is now known as sigmavirus2415:41
*** bpokorny has quit IRC15:48
*** bpokorny has joined #openstack-searchlight15:48
*** yingjun has quit IRC16:01
*** lakshmiS has joined #openstack-searchlight16:02
*** lei-zh has quit IRC16:04
sjmc7lakshmiS: the reason the ‘records’ data isn’t structured is that the structure isn’t very structured16:06
sjmc7for dns16:06
sjmc7seems very context dependent16:06
lakshmiSits a text blob of ip's and stuff16:07
sjmc7it’s bloody confusing, is what it is :)16:07
*** pcaruana has quit IRC16:08
sjmc7lakshmiS: i’m seeing recordset.create notifications arriving after record.create under the v1 API16:13
sjmc7which makes the record handling fail with a 40416:14
sjmc7this is eerily reminiscent of the problem i had with DHCP ports16:14
lakshmiSi got it in the right order16:14
lakshmiSrecordset and then record with v116:14
sjmc7actually, i’m not sure i get a recordset one at all. there’s a zone update that gets sent16:17
lakshmiSso you ran designate record-create ?16:17
sjmc7yeah16:17
sjmc7ah, there it is16:18
sjmc7hmm.. this seems like a potential race condition16:19
sjmc7it looks like this will work as long as the recordset create is processed in time for the record.create16:20
lakshmiSwe will have to lookup recordset instead of relying on notification when record.create arrives then..16:21
lakshmiSexception condition when its not in es16:21
sjmc7from the api?16:21
lakshmiSyes16:21
sjmc7yeah, maybe. naively i guess we could always reindex the recordset from the api16:21
sjmc7depends how big that race is16:25
sjmc7because the other danger is that if we pull the recordset from the api and then the recordset event comes in we’ll wipe out the records that way :)16:26
lakshmiShmm16:28
lakshmiSits going to endup all api lookups :)16:29
sjmc7kind of feels like for a v1 api call we should go back to the api16:29
sjmc7except of course we don’t know whether it is v116:30
lakshmiSthats the problem with recordset. let me check if they show that in payload for the origin16:31
sjmc7doubtful; probably the empty record list would be the indicator16:32
lakshmiSyeah nothing there to indicate. for the empty check - have to make sure v2 recordset create allows empty records or not16:35
sjmc7doesn’t seem to16:36
sjmc7—records is required by the CLI16:36
sjmc7so one option might be to ignore recordset create events with empty records, and always index from the API for record.create?16:37
sjmc7all the record.create handlers would hit the api, v2 notifications wouldn't16:37
lakshmiSyes that would be better16:37
sjmc7since we’re removing that code anyway once v1 is gone, not too worried about efficiency16:38
lakshmiSits not efficient even for record.update due to api design16:39
sjmc7v1 looks very fiddly, i can see why they wanted to change it16:39
sjmc7yeah, i think we could hit the reocrdset API on *any* record event16:39
sjmc7delete is a bit complicated too16:40
sjmc7with v1 i don’t see how you delete a recordset at all16:41
lakshmiSv1 doesnt have recordset conept16:42
openstackgerritBrian Rosmaita proposed openstack/searchlight: Eliminate stray asterisk  https://review.openstack.org/30008816:42
lakshmiSso if users exclusively use v1 api16:42
sjmc7ah, ok. it just sends a few notifications for good measure16:42
lakshmiSforward compatibility :)16:42
sjmc7so what happens if i delete all the records in a zone under v1..?16:43
sjmc7the recordset becomes empty?16:43
lakshmiSyou end up with a recordset with type NS and SOA records16:43
sjmc7ah, those are special?16:43
lakshmiSyes16:43
sjmc7ok, so let’s just hit the API on all record. events16:44
sjmc7that seems easier16:44
sjmc7unless it really is just create that’s the problem16:44
lakshmiSyes to the efficiency(to make sure v1 users not use SL)16:44
sjmc7users will use both16:45
sjmc7wait, if i delete a record, i see the associated recordset go away too16:51
lakshmiSdid you get a recordset delete event too?16:52
sjmc7i don’t think so :(16:52
lakshmiSso you verified that recordset is gone from v2 cli?16:52
sjmc7yeah16:53
lakshmiSdamn16:53
sjmc7it took a while to do it16:53
sjmc7yeah, no recordset-delete as far as i can see16:53
lakshmiSmay be it will come eventually otherwise its a bug in designate16:54
sjmc7yeah. so what’s a sensible compromise we can make?16:54
sjmc7option 1 is do nothing :)16:54
sjmc7mugsie: you around?16:54
mugsiesjmc7: just about to hop on to a meeting - can I ping you in 30?16:55
sjmc7sure16:55
sjmc7thanks16:55
lakshmiSeven for delete we could lookup the api and remove recordset if its not in designate16:56
sjmc7i don’t know how instantaneous it is16:56
lakshmiSyeah time dependent16:56
sjmc7it actually seems to take a while until the record disappears from the api16:56
sjmc7for delete, if the record list is empty, the set can be deleted16:57
lakshmiSwhich is ok as long as designate guarantees notification but that's something we cannot address16:57
sjmc7for update, i think what you have is fine16:57
sjmc7designate seems to guarantee NO recordset.delete notification for record deletes16:57
sjmc7so i think that’d be ok16:58
sjmc7for creates…16:58
sjmc7i’m leaning towards go to the api16:58
lakshmiShope you don't get that delete recordset notification by lunch :)16:58
sjmc7ignore recordset.create with empty records16:58
sjmc7if we do, we’ll ignore it16:58
sjmc7it’ll be a silent 40416:58
lakshmiSapi makes sense for create record16:59
sjmc7i think the other two are fine, but delete needs to remove the recordset if the list of records is empty after filtering17:03
sjmc7at this point in time it’s gonna be a bit of a best-effort17:04
lakshmiSyeah no other way17:07
sjmc7does that make sense, to do that?17:07
sjmc7so create: ignore recordset.create events with empty ‘record’ lists17:07
sjmc7and index from the api17:07
lakshmiSdelete can make an extra check for recordset17:08
sjmc7update: leave as you have it from the api17:08
sjmc7delete: leave as you have it except that if ‘records’ is empty, delete the recordset17:08
lakshmiSi will try to comment as much as i can. god help someone who wants to understand it :)17:09
sjmc7:)17:09
sjmc7well, we can drop it all in newton :)17:09
lakshmiShopefully17:09
sjmc7ok. i’ll add comments on the review as a note17:11
*** sigmavirus24 is now known as sigmavirus24_awa17:17
openstackgerritTravis Tripp proposed openstack/searchlight-ui: Fix issues when magic search facet uses range queries  https://review.openstack.org/30010717:38
-openstackstatus- NOTICE: Job failures for missing traceroute packages are in the process of being fixed now, ETA 30 minutes to effectiveness for new jobs17:49
openstackgerritTravis Tripp proposed openstack/searchlight-ui: Fix issues when magic search facet uses range queries  https://review.openstack.org/30010718:01
TravTsjmc7: ^ that one is ready for testing.  I'll go look at your comments on the parent patch.18:02
mugsiesjmc7: sorry - got distracted18:09
mugsiethe recordset.delete event question? (on the deletion of the last record in it) seems like a bug18:11
mugsiewe should emit that notification18:11
sjmc7mugsie: yeah, probably. when’s the v1 api going away though?18:12
mugsiefirst commit of Octa if I have my way18:13
sjmc7ok. well, given we have to get RC 2 done today we’ll go with this18:14
sjmc7we can tweak it in newton18:14
openstackgerritTravis Tripp proposed openstack/searchlight-ui: Searchlight UI Query Error Handling  https://review.openstack.org/29956618:19
openstackgerritTravis Tripp proposed openstack/searchlight-ui: Fix issues when magic search facet uses range queries  https://review.openstack.org/30010718:20
*** sigmavirus24_awa is now known as sigmavirus2418:20
*** sigmavirus24 is now known as sigmavirus24_awa18:22
*** sigmavirus24_awa is now known as sigmavirus2418:24
*** bpokorny has quit IRC18:24
sjmc7lakshmiS: can we disable the functional test CI jobs? we’re getting an unacceptably high failure rate18:38
lakshmiSseems like elasticsearch connection is timing out. have seen that happen on busy systems. i wanted to check if we can increase es timeout setting18:39
*** bpokorny has joined #openstack-searchlight18:40
*** bpokorny has quit IRC18:40
sjmc7no, there’re a lot of memory errors18:40
sjmc7timeouts are a result of crashes18:40
*** bpokorny has joined #openstack-searchlight18:41
lakshmiScan we try incrasing heap space?. temporarily we can disable for now, but it will be tough to test since it only fails on jenkins18:44
sjmc7i’d like to disable it if possible18:44
sjmc7we have to get RC2 done today18:44
sjmc7and we’ll incur the wrath of infra18:45
lakshmiSthat may be a problem18:45
lakshmiShopefully they approve soon. i will try18:45
sjmc7we can try decreasing memory usage too. lemme take a look at what we’re using now18:45
sjmc7the problem is i think there are two errors; that the JVM runs out, and that the machine runs out18:46
sjmc7looks like we’ve got it set pretty low. i’ll increase it and see if it helps. i don’t know how much memory the VMs have18:47
sjmc7lakshmiS: i’ll put a patch up to increase the heap space for now18:49
sjmc7and make a note to do it more efficiently18:49
lakshmiSok18:50
lakshmiSits easy to try out in our code anyway, but i will keep the patch up ready incase...18:51
openstackgerritSteve McLellan proposed openstack/searchlight: Increase heap for elasticsearch in func tests  https://review.openstack.org/30015018:51
lakshmiSapproved18:53
sjmc7we should be able to just run one for all the tests with different base index names i think18:53
sjmc7but i don’t want to try to do that now18:53
lakshmiSyeah we could18:55
sjmc7it’s tricky cos of the multiprocessing18:55
openstackgerritMerged openstack/searchlight: Fix _is_multiple_alias_exception signature  https://review.openstack.org/29894718:58
*** openstackgerrit has quit IRC19:03
*** openstackgerrit has joined #openstack-searchlight19:05
openstackgerritMerged openstack/searchlight: Increase heap for elasticsearch in func tests  https://review.openstack.org/30015019:05
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973319:17
TravTsjmc7: are you going to cherry pick this one to stable/mitaka as well?19:29
TravThttps://review.openstack.org/#/c/300150/19:29
sjmc7no19:29
sjmc7i wasn’t planning to19:29
sjmc7i guess it doesn’t hurt though in case we have to do backports in future19:29
TravTyeah, i'm not seeing a downside19:30
sjmc7ok. i was trying to reduce what we’re pushing but it doesn’t do any harm. unless it makes nodepool machines run out of memory19:30
sjmc7next time, don’t change infra the week of the release :)19:31
TravTwhat could possibly go wrong!19:31
sjmc7https://review.openstack.org/#/c/300181/19:31
openstackgerritMerged openstack/searchlight: Eliminate stray asterisk  https://review.openstack.org/30008819:31
TravTcool19:31
openstackgerritMerged openstack/searchlight: Disable oslo_config file discovery in tests  https://review.openstack.org/29883019:32
sjmc7it seems to have sorted it out, fingers crossed19:32
TravTwhen in doubt, increase memory19:32
sjmc7looks like they recommend 8GB of RAM for nodepool machines so a few hundred MB shouldn’t tip the balance19:32
lakshmiSif fails we will increase again :)19:33
TravTi got a sweet pop-up ad offering to download more memory to my system the other day. maybe we could do that for the nodepool machines. :-P19:33
sjmc7TravT: looking at https://review.openstack.org/#/c/300107 (facet qs)19:34
sjmc7to save me some time, what was the before/after?19:34
sjmc7oh wait, they’re in the commit message19:35
sjmc7haha19:35
TravTyeah19:35
TravTi can also screenshare show you as well19:35
sjmc7nah, that’s ok19:35
sjmc7what was the problem before?19:35
TravTturned out to be two things really19:36
TravTfirst of all, the facets were all doing a term query, so for things like min_ram or size or date, etc19:36
sjmc7ok19:36
TravTit would only match if you put in exact match19:36
TravTyou couldn't do like min_ram <51219:37
TravTit would just not match19:37
sjmc7got it19:37
TravTnext thing was that I found when testing >=  <= that due to how magic search sends facets through, it was only grabbing part of the input19:37
TravTand if you have say a search phrase (for like description) or something that had an = sign in it, it would only grab part19:38
TravTmagic search sends facets through in URL query parameter status, but it doesn't url encode things first19:38
sjmc7sigh19:38
TravTyeah,19:38
sjmc7nothing you tell me about magicsearch makes me like it :)19:39
TravTme more so than you19:39
TravTother than it makes the facets discoverable for less technical users19:39
sjmc7i think by now you could’ve written it :)19:39
TravTyeah, in retrospect...19:39
TravTthat actually was what I woke up debating19:39
sjmc7can you approve 300181 for the stable branch?19:40
sjmc7hitting the same memory error merging the cherrypicks19:40
sjmc7i think after that the designate one’s the last patch for rc2, gonna test again now19:41
TravTyeah, that's why i asked about backporting the memory fix19:41
sjmc7i’ve +2ed the UI ones, both look fine19:41
sjmc7lakshmiS: aside from the test failures the designate one’s finished?19:42
sjmc7i feel like i’ve spent a day in travis’ shoes, reviewing patches :)19:42
TravThehe... i could crank out a couple more ui fixes for you if you want.19:43
lakshmiSah aah. i have added functional tests for zones. debating whether to add for recordset/record or not coz that will take more time19:43
TravT;)19:43
sjmc7lakshmiS: given we didn’t have any before, i’m ok with not adding them now19:43
sjmc7we really should be trying to finish up19:43
lakshmiSyeah i will lave the records to another patch for which a bug is already there19:44
lakshmiSs/lave/leave19:44
TravTlakshmiS: i really want to get the backports done and kick off a fresh stack from stable/mitaka19:44
TravTso I can put up the release tags19:44
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973319:44
lakshmiSok dnoe19:44
lakshmiSdone19:44
lakshmiSlets wait for gate gods19:45
TravTlakshmiS: can you please look at the UI patches as well?19:45
lakshmiSwill do that now19:45
lakshmiSone last change. my editor ends up with tab instead of spaces...19:46
TravTok.19:46
sjmc7the test files are still full of tabs, lakshmiS19:53
lakshmiSyeah fixing the same19:54
-openstackstatus- NOTICE: Any jobs which erroneously failed on missing traceroute packages should be safe to recheck now19:55
sjmc7also the create and update record handlers are identical i think now?19:57
*** briancline has quit IRC19:58
*** briancline has joined #openstack-searchlight19:58
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973319:58
lakshmiSsjmc7: i left them separate to have the comments to explain the reason20:00
sjmc7hmm.. ok20:00
sjmc7i’m not a big fan of duplicated functions though20:01
lakshmiSif another commit is required i can optimize the comments ;(20:05
TravTi just found something a little odd with the search panel.20:07
*** briancline has quit IRC20:10
TravTfalse alarm.20:14
openstackgerritMerged openstack/searchlight-ui: Searchlight UI Query Error Handling  https://review.openstack.org/29956620:15
*** briancline has joined #openstack-searchlight20:17
*** briancline has quit IRC20:26
openstackgerritRick Aulino proposed openstack/searchlight: Zero Downtime Re-indexing Unit Tests.  https://review.openstack.org/30020320:31
*** bpokorny has quit IRC20:32
TravTlakshmiS: the new dns recordsets i'm creating don't seem to have a project id20:34
*** bpokorny has joined #openstack-searchlight20:34
sjmc7TravT: through the v1 or v2 api?20:35
TravTwhatever openstack client uses20:35
sjmc7i see project_ids20:35
sjmc7from both20:35
lakshmiSyeah just check that20:35
lakshmiSchecked20:36
TravTlet me see debug breakpoint to see what comes in via notification.20:36
TravTs/see/set20:36
sjmc7it’s not explicitly in the mapping but there’s a dynamic template that catches it20:36
sjmc7be aware that debugging it is REALLY annoying20:37
sjmc7because it sends several updates at weird intervals20:37
sjmc7i kept getitng bounced around threads20:37
sjmc7keep an eye on which thread is handling which events20:37
TravTugh20:37
sjmc7yeah20:37
TravTso, i'm running the resources script20:38
TravThttps://review.openstack.org/#/c/230697/14/sample-scripts/resources.sh20:38
TravTwhich executes line 18820:38
TravTresources.sh -n designate -t OS::Designate::Zone20:39
*** briancline has joined #openstack-searchlight20:43
TravTi just re-ran it 5 times.20:46
openstackgerritRick Aulino proposed openstack/searchlight: Zero Downtime Re-indexing Unit Tests.  https://review.openstack.org/30020320:47
lakshmiSso do you see a tenant_id in notification event payload ?20:47
TravTit isn't hitting the breakpoint...20:48
TravTlet me dump it out20:48
TravToh, this is interesting20:49
TravTtry adding all_projects to your query20:49
TravTthe couple of records that are created automatically when you create a zone have project20:51
TravTthe record i create with designate record-create "$zone_id" --name www."$zone_name" --type A --data 192.0.2.120:51
TravTdoesn't have it20:51
TravTi don't have the object dumped yet20:52
lakshmiSthat is strange. same cli command you showed creates a tenant_id for me20:52
TravTbut i'm almost wondering if line 175 overwrites it20:52
TravThttps://review.openstack.org/#/c/299733/4/searchlight/elasticsearch/plugins/designate/notification_handlers.py20:52
lakshmiSdesignate record-create 6837da17-ffd3-46ca-9fb3-f82804a26c9f --name www.domain1-example.com. --type A --data 192.0.2.120:52
lakshmiSevent_type:dns.record.create20:52
lakshmiSevent_type:{u'status': u'PENDING', u'zone_id': u'6837da17-ffd3-46ca-9fb3-f82804a26c9f', u'managed': False, u'managed_resource_id': None, u'managed_resource_type': None, u'tenant_id': u'80264096ac454d3d904002491fafe2ec', u'created_at': u'2016-03-30T04:23:48.000000', u'managed_extra': None, u'updated_at': None, u'managed_plugin_type': None, u'version': 1, u'managed_plugin_name': None, u'managed_tenant_id': None, u'action': u'CREATE',20:52
lakshmiSu'hash': u'bc16c7fc29e740c99f580efa9fc0d247', u'managed_resource_region': None, u'recordset_id': u'7f36cd3a-7ad8-49ec-b5c2-253eb495fd32', u'data': u'192.0.2.1', u'id': u'55af5e51-9550-471b-8fbd-791f8f2e53f1', u'serial': 1459311828, u'description': None}20:52
TravThmmm20:52
TravTmaybe something changed in designate?20:53
TravTdid they land code to move to project_id recently?20:53
TravTlet me dump the data20:53
lakshmiShas to be very recent in that case. my devstack is 2 days old20:53
lakshmiSTravT: ui patch 300107 looks good. when you use date fields, i guess it only checks if its a number and not necessarily any date format?20:56
TravTthere is something wrong with my pycharms i think.20:57
TravTit is not using the code i see in my editor20:57
TravTwill restart it20:57
sjmc7i’m only getting project id, not tenant20:58
lakshmiSin event payload?21:00
sjmc7indexed21:00
lakshmiSthats correct21:01
sjmc7yeah21:01
lakshmiSapi gives project_id and event gives tenant_id21:01
TravTlakshmiS: the date formatting for the ui patch doesn't do anything special21:01
TravTit allows same syntax ES allows for query strings.21:02
lakshmiSTravT: checked with date =0 and no error. is there a date format to be followed?21:02
sjmc7wait, what? we get both?21:02
TravTokay, if API provides project_id, then the line i mentioned about would be a problem, right?21:03
TravTwell, maybe not21:03
sjmc7we may need to alter the serialization functions to write both21:03
TravT    def _serialize(self, obj):21:03
TravT        obj['project_id'] = obj.pop('tenant_id')21:03
sjmc7no…21:04
sjmc7i can do that as a separate patch in a sec21:04
sjmc7i will say though that i’m not seeing tenant_id anywhere21:05
lakshmiSall my notification event payloads has only tenant_id. no project_id21:06
sjmc7my devstack was up to date as of march 23rd21:06
lakshmiShttp://paste.openstack.org/show/492669/21:06
lakshmiSmine is 2 days old21:06
sjmc7urgh, maybe v1 is tenant_id?21:07
TravTwhich means it is newton...21:07
TravTbut i don't see any patches on designate that mention project id21:07
lakshmiSnope even v2 is tenant_id21:07
sjmc7we’re not directly indexing v1 records though, we’re going to the api, so that’s fine21:07
sjmc7argh21:07
lakshmiSsee the link21:07
sjmc7wait, we are intentionally turning it into project id21:08
sjmc7i’m really confused now21:08
sjmc7TravT: are you having a problem searching?21:09
sjmc7or did you just look at the raw notification payload?21:09
TravTwhen i do search, i don't see a project id21:09
TravTand the only way i see the created recordset is to turn on all_projects21:10
lakshmiShere's what i think21:11
TravTbut something is really horky with my env21:11
TravTi'm putting log statements in that don't show21:11
lakshmiSfor initial indexing, api provides project_id21:11
TravTand debug doesn't hit breakpoint21:11
TravTbut i don't see extra processes21:11
lakshmiSand https://github.com/openstack/searchlight/blob/master/searchlight/elasticsearch/plugins/designate/recordsets.py#L93 saves it21:11
sjmc7api gives project id, events we turn teannt id into project it21:11
sjmc7one sec, testing it myself21:11
sjmc7i am seeing records without all_projects21:12
lakshmiSone issue i see is tenant_id is not set when we create recordset for v1 record create event21:13
sjmc7we’re going to the api for create21:14
lakshmiSah yes. enough on this now ;)21:14
TravTlakshmiS: which type has a facet named date?21:14
lakshmiSTravT: i was checking just the query for designate created_at date field21:15
TravTso, that last patch only changes magic search facets21:15
TravTif you are mucking around with full text search21:16
TravTthat's unrelated21:16
lakshmiSyeah was a side question21:16
lakshmiS:)21:16
TravTdate you can do things like21:16
TravTdate: [now TO now-1m/d]21:17
sjmc7i think we need to pull the trigger on these or decide not to; we are running the risk of not getting the release tagged at all21:17
lakshmiSi need to patch it for another thing i found. parent linking was not happening for v1 api21:18
TravTlakshmiS: if you don't see anything else with this21:18
TravThttps://review.openstack.org/#/c/300107/21:18
TravTcan you pull the trigger?21:18
lakshmiSsure21:18
TravTi do need to submit the release tag21:18
TravTsjmc7: so you don't see issues with project id?21:19
sjmc7no.21:19
TravTi don't trust my env right now.21:19
sjmc7and it’s been like that for ages21:19
TravTi don't see any phantom python processes21:19
sjmc7the notifications do not include project_id, that is true21:19
TravTbut it definitely is not running my code at the moment21:19
sjmc7but the code makes the switcheroo21:19
sjmc7good catch on the parent lakshmiS :(21:20
sjmc7i’ll wait for an updated patch21:20
openstackgerritMerged openstack/searchlight-ui: Fix issues when magic search facet uses range queries  https://review.openstack.org/30010721:25
sjmc7that’s everything for the ui repo, TravT21:25
TravTyep, going to submit release request now21:26
TravTi killed off all my pycharms21:26
TravTand it is now re-indexing itself21:26
TravTso hoping designate is happier afterwards21:26
TravThttps://review.openstack.org/#/c/300222/21:29
TravTsjmc7^21:29
sjmc7yay!21:30
TravT\o/21:30
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973321:34
sjmc7lakshmiS: doesn’t the parent id come from the parent_field?21:37
lakshmiSi was just thinking about that.21:38
lakshmiSwhy is it even mapped currenlty21:38
sjmc7?21:38
lakshmiShttps://github.com/openstack/searchlight/blob/master/searchlight/elasticsearch/plugins/designate/recordsets.py#L100 is that required?21:38
sjmc7no, i don’t think so21:39
lakshmiShmm, i thought i missed it so added same :)21:39
lakshmiSso no effect21:40
sjmc7if adding it does no harm then i’m going to +2 it , we’re really out of time21:40
lakshmiSyup21:40
sjmc7we’ve got to revert it :(21:45
*** TravT has quit IRC21:46
lakshmiSso we have to remove it from indexing too then?21:47
sjmc7checking21:47
*** TravT has joined #openstack-searchlight21:48
sjmc7lakshmiS: looks like it’s leaving junk there too, might as well take it out21:48
lakshmiSyeah its there in source21:49
lakshmiSpatch coming through...21:49
sjmc7ok21:49
sjmc7i’ll do a quick sanity test then i’ll +221:49
openstackgerritLakshmi N Sampath proposed openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973321:50
lakshmiSok. i really have to leave now. will be back in 15 mins.21:50
TravTi'm pulling it as well21:50
sjmc7ok, i’m comfortable with it21:53
TravTlet's do it!21:54
sjmc7i’ve +2ed, can cherypick it once it merges21:54
TravTare there any missing cherry picks...21:55
sjmc7checking21:55
sjmc7although honestly it’s a little hard to tell21:55
*** sigmavirus24 is now known as sigmavirus24_awa21:56
TravTwill try to correlate from here21:57
sjmc7one missing, i think21:57
sjmc7https://review.openstack.org/#/c/298830/21:58
sjmc7picked it to https://review.openstack.org/#/c/300228/21:59
sjmc7looks like that’s everything21:59
lakshmiSback22:07
openstackgerritMerged openstack/searchlight: Backward compatibility with designate v1 api  https://review.openstack.org/29973322:08
*** akanksha_ has joined #openstack-searchlight22:10
TravTok, i'm double checking this22:10
TravThttps://launchpad.net/searchlight/+milestone/mitaka-rc222:10
TravTonce the cherry picks land, can you guys also kick off a devstack on stable/mitaka?22:11
TravTjust make sure we don't have any surprises22:11
sjmc7ok, but i have to go quite soon22:12
lakshmiSwill check it ou22:12
lakshmiSneed to get tempest working soon22:14
TravTok, everything listed in rc2 has backports... just waiting for designate22:15
TravTto finish gate jobs22:15
openstackgerritRick Aulino proposed openstack/searchlight: Zero Downtime Re-indexing Unit Tests.  https://review.openstack.org/30020322:16
TravTgate jobs done.22:17
lakshmiSok installing now22:19
*** bpokorny_ has joined #openstack-searchlight22:28
*** bpokorny_ has quit IRC22:30
*** bpokorny_ has joined #openstack-searchlight22:30
*** bpokorny has quit IRC22:32
sjmc7tested initial indexing, some searches, created some stuff and seen it appear22:32
sjmc7i’m happy22:32
sjmc7i mean, not happy, but i think it works22:32
TravTcool22:32
TravTi'm still watching it scroll22:32
TravTi have the release request ready to submit22:33
sjmc7i had to cheat a bit since i’m already late, but i’m running the mitaka code22:33
sjmc7against mitaka services22:33
TravTWell, fantastic work sjmc7!22:33
TravTit has been quite a haul22:34
TravTi went ahead and pulled the trigger on the release request patch.  at least get it up there.22:36
TravThttps://review.openstack.org/#/c/300235/22:36
TravTi could put a WIP -1 until we finish this devstack verification22:36
sjmc7ok, i have to scoot. i’ll be back a later for a bit22:38
TravTcool22:38
TravTi have to go help coach son's football in 20 minutes as well22:38
openstackgerritTravis Tripp proposed openstack/searchlight: Simple Script for Generating Resources  https://review.openstack.org/23069722:42
*** bpokorny_ has quit IRC22:44
*** bpokorny has joined #openstack-searchlight22:44
TravTlakshmiS22:49
TravTi just hit this error again:22:49
TravT2016-03-31 22:49:28.603 | ovs-ofctl: br-tun is not a bridge or a socket22:49
TravT2016-03-31 22:49:28.626 | ovs-ofctl: br-tun is not a bridge or a socket22:49
TravTin devstack (not a searchlight error)22:50
TravThow did you fix that?22:50
lakshmiSdidnt really fix it. removed nuetron22:50
TravToh geez22:50
lakshmiSbut i didnt get that error 2 days back when i installed22:50
lakshmiSso looks like its broken again then22:51
lakshmiSmy stack is still installing. lets see if i hit it today22:51
TravTok.22:51
TravTwell, i actually have to leave22:51
TravTi'll check back in later22:51
lakshmiSok22:52
*** bpokorny_ has joined #openstack-searchlight23:41
*** bpokorny has quit IRC23:41
*** bpokorny_ has quit IRC23:41
*** bpokorny has joined #openstack-searchlight23:42

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