19:02:31 <SotK> #startmeeting storyboard
19:02:32 <openstack> Meeting started Wed Dec  5 19:02:31 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:02:35 <openstack> The meeting name has been set to 'storyboard'
19:03:13 <diablo_rojo> Hello!
19:03:36 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting Agenda (ish)
19:03:40 <SotK> hey :)
19:03:58 * diablo_rojo just updated the agenda so you might want to refresh :)
19:04:03 <SotK> thank you!
19:04:20 <SotK> #topic Migration Updates
19:05:27 <diablo_rojo> No updates
19:05:36 <diablo_rojo> still haven't had time to dig into the neutron failure
19:06:16 <SotK> fair
19:06:29 <SotK> #topic Story Attachments
19:07:05 <diablo_rojo> I got a few more comments yesterday from fungi and clarkb that I can add to the spec.
19:07:14 <SotK> #link https://review.openstack.org/#/c/607377/
19:07:15 <diablo_rojo> After that I think it might be ready to merge?
19:07:18 <fungi> oh, right, there's a meeting! ;)
19:07:23 <diablo_rojo> fungi, ;)
19:07:43 <SotK> heh :)
19:07:45 <clarkb> diablo_rojo: I was curious to get fungi's thoughts on my comment too (did that happen) as a primary consumer of the embargoed data
19:07:51 <fungi> my reminder highlighted but i was engrossed in other things as usual, sorry!
19:08:07 <fungi> clarkb: yeah, i responded
19:08:12 <diablo_rojo> clarkb, yeah I think fungi agreed
19:08:27 <diablo_rojo> but that it might be something to be done later?
19:08:55 <fungi> i think it sounds like a useful (perhaps swift-only) feature but i think it could be added to the current design as a future improvement without much disruption
19:09:17 <fungi> basically just a toggle which causes sb to obtain and serve swift tempurls instead of persistent ones
19:09:18 <SotK> I agree
19:10:39 <diablo_rojo> I will get that added today
19:10:50 <SotK> thanks
19:11:10 <SotK> I think it'll probably be ready after that
19:11:14 <fungi> the sb database would still store the persistent url either way, i assume, and then optionally could use that to obtain a request-specific url with a short-ish lifetime
19:12:22 <fungi> the same creds it uses to authorize uploads should be sufficient for obtaining tempurls too
19:12:46 <fungi> so really no redesign necessary to accommodate that feature
19:13:43 <SotK> yep, just a "stretch goal"
19:14:04 <diablo_rojo> Sounds like a solid plan to me
19:15:07 <fungi> but yeah, i'm fine with the security we get from unguessable persistent urls for the time being
19:15:16 <SotK> excellent
19:15:32 <diablo_rojo> Sweet :)
19:15:44 <fungi> in openstack services, there is plenty of security which merely relies on attackers being unable to guess a uuid
19:16:02 <fungi> this is (or at least should be) no different
19:17:06 <SotK> #topic Moving the database closer to the site
19:17:18 <SotK> has anyone thought about this any more since last week?
19:19:10 <fungi> yeah, we discussed it in the infra meeting yesterday
19:19:45 <fungi> clarkb laid out a basic plan, and ianw mentioned he could help writing up a slightly more robust maintenance plan or at least provide an example
19:20:34 <fungi> we'll want to start by first adding the puppet info for creating a local mysql database on the server
19:20:39 <diablo_rojo> fungi, if I can get an example etherpad to workfrom like clarkb was talking about I can start cobbling a plan together
19:20:41 <clarkb> I volunteered to help fill in details too
19:20:49 <fungi> then we can take some brief downtime to copy the data over
19:21:27 <diablo_rojo> corvus, had a good idea to run the test migration first before doing the cutover to know how long it would take
19:21:44 <fungi> after which we should be able to just update the secret store we use where the databse url and password are kept
19:22:17 <fungi> yeah, that's a good point, though i expect it to be fast i haven't done a db dump recently
19:23:06 <SotK> sounds like a good plan to me
19:23:09 <fungi> looking at the timestamps on our db backups though i expect it's under a minute
19:24:01 <fungi> looks like 13 seconds
19:24:12 <fungi> Modify: 2018-12-05 00:00:13.669085331 +0000
19:24:42 <fungi> (the cron to call mysqldump is scheduled for utc midnight)
19:25:23 <diablo_rojo> Oh nice.
19:25:25 <diablo_rojo> Super fast
19:25:49 <diablo_rojo> Okay so fungi can you handle the initial setup?
19:26:03 <fungi> yeah, i'll see if i can get on that in the next 24 hours
19:26:31 <fungi> added to the top of my to do pile
19:27:10 <SotK> thanks fungi
19:28:21 <SotK> #topic In Progress Work
19:28:33 <diablo_rojo> thanks fungi!
19:29:14 <SotK> so I didn't get round to looking at tests I'm afraid, but I did finally update my patch to fix worklist ordering to address persia's comment
19:30:00 <SotK> I also sent a patch to start addressing an easy looking story about adding some information about popularity to tags
19:30:18 <SotK> #link https://review.openstack.org/#/c/600472/
19:30:24 <diablo_rojo> I saw! gmann will be thrilled :)
19:30:36 <SotK> #link https://review.openstack.org/#/c/621046/
19:30:41 <diablo_rojo> They are all on my review docket for today
19:30:42 <fungi> yeah, that was related to the suggestion that we could sort the typeahead on tags by popularity?
19:30:54 <SotK> indeed
19:31:13 <fungi> would definitely cur down on people making up random tags when there's a good one already for their need, or worse mistyping tags
19:31:20 <fungi> s/cur/cut/
19:31:53 <diablo_rojo> speaking of misspellings :)
19:32:03 <SotK> actually making it possible to tell the api to return ordered results for tags will need a bit more work still
19:32:30 <SotK> but with that patch there is enough data available for clients to attempt to do something useful
19:32:48 <diablo_rojo> Sounds good.
19:32:53 <fungi> yep, incremental is good
19:34:46 <SotK> next on my list is to look at tests, I just saw the notification for that story being created and immediately wanted to make the solution
19:35:09 <diablo_rojo> SotK, ha ha sounds good
19:35:30 <diablo_rojo> My todo list is reviews and then help with the db migration and see if we can finish that spec up
19:36:03 <SotK> also sounds good :)
19:38:20 <diablo_rojo> I think i have one or two patches out there waiting for reviews still too
19:38:36 <SotK> I'll try to finally take a look at them too then
19:38:39 <diablo_rojo> adding new pagination size and exposing emails with names in searches
19:38:44 <diablo_rojo> Thanks SotK!
19:39:32 <SotK> anything else?
19:40:16 <diablo_rojo> dont think so
19:40:56 <SotK> #topic Open Discussion
19:41:22 <diablo_rojo> SotK, so you have denver on your calendar right?
19:41:41 <diablo_rojo> I think registration is open ;)
19:42:25 <SotK> I do
19:42:36 <fungi> though maybe wait for ptg attendee discounts to go out? (if you went to one of the recent ptgs)
19:42:45 <SotK> what counts as recent?
19:42:56 <fungi> either of the past 2 is what we've done in the past
19:43:11 <fungi> so dublin or denver i think?
19:43:30 <SotK> ok cool, I'll wait for that to come out and get something sorted
19:43:42 <fungi> (not the upcoming denver ptg obviously, the one we had earlier this year)
19:44:10 <diablo_rojo> #snowpenstack
19:45:36 <fungi> and #choochoostack
19:46:44 <diablo_rojo> I can't wait for what happens next..
19:50:10 <fungi> as long as it doesn't involve fireball shots
19:52:15 <diablo_rojo> fungi, they always do ;)
19:54:54 <fungi> seems open discussion has wound down
19:56:22 <diablo_rojo> yeah we can probably end it
19:56:54 <SotK> fireball shots sound exciting
19:56:59 <SotK> thanks for coming :)
19:57:02 <SotK> #endmeeting