18:07:22 <SotK> #startmeeting storyboard
18:07:22 <openstack> Meeting started Thu Jun 18 18:07:22 2020 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:07:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:07:25 <openstack> The meeting name has been set to 'storyboard'
18:07:34 <diablo_rojo> Agenda is updated
18:07:41 * SotK hopes he's not imagining that meetings are in here now
18:07:46 <SotK> thanks diablo_rojo
18:07:57 <diablo_rojo> SotK, I honestly don't remember, but it seems right?
18:08:11 <fungi> meetings can be anywhere, but happy to update the meeting location in irc-meetings if needed
18:08:17 <diablo_rojo> I suppose now that there is a #opendev-meeting and we are not under the openstack namespace anymore we could do them there?
18:08:36 * SotK is happy with either location for the future
18:08:42 <diablo_rojo> Not really important though, that can wait till open discussion :)
18:08:46 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda
18:09:06 <fungi> #opendev-meeting might work too, but in here is probably better
18:09:21 <SotK> #topic Migration Updates
18:09:40 <diablo_rojo> No new migrations that I am aware of.
18:09:53 <SotK> I see we have "refstack situation" on the agenda; I've been absent enough that I'm not actually sure what that is
18:10:04 <fungi> unless you count refstack finally closing down the lp project, yeah
18:10:14 <diablo_rojo> Yeah, that.
18:10:33 <diablo_rojo> Basically I saw a community member make a launchpad bp for refstack and I was like.. uhhhhh we migrated them already.
18:10:49 <diablo_rojo> And so I emailed them and asked that they replicate the bp as a story and use sb instead
18:11:09 <fungi> yeah, just confirmed, our meeting is officially scheduled in here anyway, so nothing need updating in that regard
18:11:19 <diablo_rojo> and emailed David Lenwell (who seems to be the Refstack lp admin) asking him to add me or the openstack admin group as admins or to shut it down himself.
18:11:32 <diablo_rojo> fungi, oh cool :)
18:11:44 <diablo_rojo> #nailedIt SotK :)
18:11:45 <fungi> not just any community member, the osf board member running the interop working group
18:13:32 <diablo_rojo> Yeah... someone that I would hope is more in the loop and should be setting an example, but hopefully we are all cleared up now.
18:15:22 * SotK wonders if the "stackforge" prefix on the refstack project in sb needs changing
18:15:42 <SotK> do we know if there was some reason for using LP or if it was just crossed wires?
18:16:21 <fungi> knowing just enough about that situation, i'm quite certain someone's wires were crossed
18:16:56 <diablo_rojo> I think when we migrated them the LP never actually got shut down.
18:17:12 <diablo_rojo> Looking at the list of folks with power to do so, none of them are around anymore.
18:17:32 <diablo_rojo> The description was updated, but the ability to report new bugs + add bps wasn't disabled.
18:18:30 <diablo_rojo> I guess the person that made the new bp wasn't 'in the loop' enough to know/read sufficiently about how he should be doing things in SB and not LP
18:19:30 <SotK> makes sense, sounds like the situation is in hand now anyway
18:19:54 <SotK> #topic In Progress Work
18:20:36 <diablo_rojo> Pretty sure the lovely tracking board probably needs an update.
18:20:43 * diablo_rojo hasn't touched it in waaaaay too long
18:21:32 <SotK> #link https://storyboard.openstack.org/#!/board/1
18:21:44 <SotK> yeah it probably wants an update, I've also not used it for ages
18:22:18 <diablo_rojo> I will dedicate time in the next week to do that.
18:22:24 <SotK> thanks
18:23:27 <SotK> I'll also try to finally look at what we can do to speed things up at some point soon
18:24:08 <diablo_rojo> SotK, want me to look into getting new logs? Or do you have a tentative plan?
18:24:29 <fungi> as mentioned just before the meeting, i was able to try SotK's suggested curl command to call the attachments api on storyboard-dev for an upload_url but am getting back a forbidden access error from the swift api in rackspace, so either i haven't configured the credentials for it correctly or haven't set up the acls right on the rackspace end or maybe the credentials aren't getting handed off by
18:24:31 <fungi> storyboard as expected, but i'll try to debug further
18:24:57 <fungi> diablo_rojo: i can help get updated mysql slow query logs and run the analysis commands over them
18:25:04 <fungi> if that's at all useful
18:25:28 <SotK> new logs might be helpful, but I do have some ideas based on the old findings that I want to try so its not a priority atm
18:27:46 <diablo_rojo> fungi, that would be great
18:28:34 <fungi> i'll make a note on my to do list, but it doesn't take long
18:28:35 <diablo_rojo> SotK, if there is anything I can do to help from like.. running queries to see if they match yours or like.. just poking at you to remind you, let me know.
18:30:09 <SotK> will do, the main blocker atm is me procrastinating generating a big enough test dataset so maybe poking will help xD
18:31:13 <diablo_rojo> can't we just use the storyboard-dev data?
18:31:42 <fungi> it's not especially representative
18:32:11 <fungi> but we could probably still generate sufficient datasets to produce the requisite pathological behaviors
18:33:00 <fungi> i want to say one of our last interns identified an online tool which would generate arbitrary mysqldump data sets from an input schema
18:33:26 <fungi> and successfully used it to generate a large set of test data for a local storyboard instance
18:34:17 <fungi> #link http://filldb.info/ Automatically generate data and fill your database tables with test data
18:34:18 <diablo_rojo> Ohh interesting.
18:34:25 <diablo_rojo> That does sound vaguely right.
18:35:15 <fungi> no idea if it would be sufficient for this purpose, but worth checking out at least
18:35:37 * SotK bookmarks
18:35:47 <SotK> sounds like it claims to do the job we need anyway
18:36:08 <fungi> i remember asking mordred and other former mysql'ers if they were aware of common tools for that purpose, but nobody seemed to have suggestions
18:37:02 <diablo_rojo> Seems like is its what we need.
18:38:30 <SotK> anything else to discuss about in-progress stuff?
18:38:37 <fungi> i don't think so
18:38:52 <diablo_rojo> I dont think so.
18:38:58 <fungi> unless we wanted to talk about contanierization
18:39:29 <fungi> but i don't have bandwidth this week to work on redeploying the servers, so am happy to postpone
18:41:02 <SotK> maybe next week for that then? (also so I have time to think about how storyboard's containers work again)
18:41:12 <fungi> yeah, that's cool
18:41:32 <fungi> i thnik mordred already had some work in progress for automated image building too
18:42:44 <diablo_rojo> Yeah I think so.
18:43:07 <SotK> #topic Open Discussion
18:43:12 <SotK> anything else to discuss?
18:43:32 <SotK> I think we should probably start to have these meetings a bit more frequently again
18:44:11 <fungi> yep, i'm good with that
18:44:24 <fungi> and no, i didn't have anything else to bring up
18:45:24 <diablo_rojo> I think we settled the meting thing so (good with here) so I have nothing else.
18:45:44 <diablo_rojo> And yes more frequently than like.. quarterly lol
18:47:40 <SotK> haha yes
18:48:00 <mordred> what did I do?
18:48:20 <fungi> storyboard container image builds
18:48:28 <mordred> yeah - those should exist now yeah?
18:48:35 <mordred> I believe they're all perfect :)
18:49:42 <fungi> #link https://hub.docker.com/u/opendevorg container images
18:49:49 <fungi> i do see some storyboard ones there, yep
18:50:10 <fungi> 7 in fact
18:50:14 <mordred> \o/
18:52:03 <SotK> nice, I guess all that's left is figuring out how we want to deploy them then
18:53:45 <fungi> well, and trying them out to make sure they work (though i totally trust mordred's claim that they're practically perfect in every way)
18:55:09 <mordred> when have I ever been wrong :)
18:57:37 <SotK> if there's nothing else then let's end the meeting :)
18:58:07 <SotK> #endmeeting