14:00:12 <jokke_> #startmeeting glance
14:00:13 <openstack> Meeting started Thu Jun 20 14:00:12 2019 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:16 <openstack> The meeting name has been set to 'glance'
14:00:19 <jokke_> #topic roll-call
14:00:23 <jokke_> o/
14:00:45 <abhishekk> o/
14:01:03 <davee_> o/
14:01:13 <jokke_> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
14:01:46 <jokke_> I think Brian is still off and Sean might be bit busy with his new job
14:02:25 <abhishekk> yes, rosmaita will be on vacation till 24th
14:02:25 <jokke_> #topic release updates
14:02:52 <jokke_> Soo we got the glance_store sorted, thanks abhishekk for getting it out as well
14:03:08 <abhishekk> \./
14:03:24 <abhishekk> so that release has fixed failing periodic jobs as well
14:03:31 <abhishekk> now everything is green
14:04:44 <jokke_> yeap, so now we can move on, reintroduce that change and do all the dance around it
14:04:56 <abhishekk> we are approx month away from Train milestone 2 release
14:04:59 <jokke_> and get the rest of the housekeeping done for 1.0.0
14:05:08 <jokke_> Yeah
14:05:18 <abhishekk> jokke_, right
14:05:51 <abhishekk> I will resubmit that patch tomorrow (backend >> store change)
14:06:46 <jokke_> sounds good. I went through pile or reviews yesterday ... small things that would be nice to tock out of the review queue
14:06:58 <abhishekk> great
14:07:39 <jokke_> will go through another pile today
14:08:15 <jokke_> do we have anything else around release for now?
14:08:19 <abhishekk> cool, I will followup with those tomorrow
14:08:26 <abhishekk> that's it from me
14:08:50 <jokke_> #topic migration script for backend->store
14:09:23 <abhishekk> yep, as we have discussed last week, I have added a script
14:10:02 <abhishekk> kindly have a look, this is the best possible way to update the column value which has data type as PickleType
14:13:12 <jokke_> abhishekk: ok will have a look, obviously that is needed only after we do the key change ... thanks for having it ready to go
14:13:15 <abhishekk> The query is compatible with sqlite and mysql as ell
14:13:22 <jokke_> nice
14:13:36 <abhishekk> ack
14:13:48 <abhishekk> s/ell/well
14:14:03 <abhishekk> that's it from me
14:14:13 <jokke_> kk
14:14:19 <jokke_> #topic open discussion
14:14:57 <davee_> I do not have anything at this time
14:15:08 <abhishekk> I have one question, on cache enhancement we have decided to add wrapper around glanceclient
14:15:39 <jokke_> have we?
14:15:47 <abhishekk> so is it target for this cycle or we can enhance cache-management now and add wrapper during next cycle?
14:15:48 * jokke_ is hitting totally blank on this
14:16:38 <abhishekk> #link https://etherpad.openstack.org/p/Glance-Train-PTG-planning
14:16:42 <abhishekk> line #57
14:17:05 <jokke_> oh yeah, abhishekk https://review.opendev.org/#/c/643336 could do with some love as well ;)
14:17:46 <abhishekk> jokke_, will do shortly
14:19:35 <jokke_> ohh that one, correct me if I remember this totally wrong, but the idea was to wrap glanceclient once we get the caching stuff to API so that we can still have the glance-cache-manage for people's tools that exists atm.
14:21:14 <abhishekk> jokke_, yes
14:21:37 <abhishekk> so I have a PoC ready where I have moved caching stuff to API
14:21:50 <abhishekk> with pre-caching of image
14:22:38 <abhishekk> so at the moment I am wondering how can I keep all commands under same tool
14:23:44 <jokke_> if you send me patch file I'll have a look and bounce some ideas
14:24:03 <abhishekk> or should I simply write new modules and keep old cache-manage tool as it is for the time being?
14:24:25 <abhishekk> jokke_, I will send after the meeting
14:24:49 <jokke_> That's what I've been thinking but honestly I'm not 100% sure how much we need to blow up to migrate this stuff
14:25:13 <jokke_> that's why I thought I could have a look on your approach and bounce some ideas based on that
14:25:42 <davee_> I would do new modules and make calls to them from the existing code base
14:25:56 <davee_> keep it modular
14:26:45 <jokke_> davee_: so the problem is that the caching as it is now, is running inmemory sqlite db for the local cache management. Which the tooling and the middleware pokes
14:27:12 <jokke_> well it's inmemory that gets written eventually to disk for restarts etc.
14:27:28 <jokke_> and it's in each api-node
14:27:31 <davee_> ahh, I need to get more familiar with ALL of the moving parts
14:28:36 <jokke_> yeah, the caching part has way more moving parts atm. than what would be great. Also most of the cache tooling is actually individual pieces of code that were designed to be ran independently
14:30:51 <jokke_> So one problem of single tool just interfacing the API of any given node is that it would need (admin) credentials to glance, which has quite a bit of security concerns vs. just having access to the local sqlite "directly" on the node
14:31:05 <abhishekk> jokke_, just sent you the patch file (NOTE: as it is a POC I have removed some existing commands like queue, delete all etc)
14:31:53 <jokke_> abhishekk: sure ... I'll just have a look of your approach and see what we can get out of it ... I wasn't expecting it to be exactly production ready code even your pocs tend to be close normally :P
14:32:07 <abhishekk> :D
14:32:19 <davee_> salute
14:32:37 <abhishekk> ./
14:32:44 <jokke_> as I want to make sure we can reasonably integrate the Rabbit stuff to it as well
14:32:59 <abhishekk> yeah
14:33:02 <jokke_> which is giving me headache ... surprisingly again due to the fecking onion
14:33:35 <abhishekk> aha
14:34:38 <jokke_> you can imagine how much headache it is causing when I try to serialize our request to nice lil json blop so it can be sent to the message queue and deserialized on the receiving end for processing
14:34:58 <jokke_> and none of our damn objects are behaving as expected
14:34:59 <davee_> Jokke: take 2 aspirins and call the team back in the morning, lol
14:35:29 <abhishekk> Its really a nightmare
14:36:32 <jokke_> abhishekk: I might need to be doing it literally at the top API layer just below mapping to keep it out of the onion
14:37:12 <abhishekk> jokke_, yes, that would be better
14:37:21 <abhishekk> I would like to have a look at the design if possible
14:37:51 <jokke_> like catching the response we'd be sending, if it's something else than 2XX then sending out the MQ fanout and seeing if we get 2XX from there
14:38:07 <jokke_> and reconstructing the response
14:39:14 <jokke_> just lots of pokeypokey
14:39:45 <jokke_> and obviously blocking calls keeping the client waiting
14:39:55 <abhishekk> right
14:41:02 <jokke_> but I keep poking it and hopefully your approach on the caching gets me some inspiration how we can streamline at least some parts of it
14:41:36 <abhishekk> I hope so that my approach will make sense :P
14:41:58 <jokke_> btw, I'll be working from Finland for the beginning of July so earlier TZ
14:42:27 <abhishekk> cool, thank you for the update
14:42:55 <abhishekk> I will might take a leave or two next wee due to festival
14:44:55 <jokke_> ah, something going on locally again?
14:45:18 <jokke_> that's not the big festives is it?
14:45:44 <abhishekk> nope, we will have big one in september and october end
14:46:19 <jokke_> ah it was the last fall denver ptg we were talking about that not the one at the spring :)
14:46:46 <abhishekk> ohh you remember :D
14:47:08 <jokke_> ofc
14:47:31 <jokke_> well I think that's all from me, reviews would be welcome, lets try to clean out our Q a bit
14:47:39 <abhishekk> ack
14:47:50 <abhishekk> nothing from me as well
14:47:54 <jokke_> I'll hopefully have better update for the Rabbit stuff next week
14:48:18 <abhishekk> great, all the best with onion :D
14:48:19 <jokke_> I'll see if I can catch up with you abhishekk tomorrow morning about the cache stuff
14:48:26 <jokke_> I'll have a look at it tonight
14:48:31 <abhishekk> jokke_, that would be nice
14:48:37 <abhishekk> thank you
14:48:55 <jokke_> ok, thanks all! getting your 10min this afternoon back :)
14:48:57 <abhishekk> thank you all, have a good day ahead
14:49:03 <jokke_> #endmeeting