19:08:06 <SotK> #startmeeting storyboard
19:08:07 <openstack> Meeting started Wed Feb  6 19:08:06 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:08:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:08:10 <openstack> The meeting name has been set to 'storyboard'
19:08:22 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda
19:09:10 <SotK> There are no announcements and I think nothing new about migrations, so lets skip past those
19:09:37 <SotK> #topic Story Attachments
19:09:52 <fungi> this is the hot topic of the week, to be sure
19:09:52 * diablo_rojo has reviews to do
19:10:00 <diablo_rojo> It is indeed
19:10:26 <SotK> #link https://review.openstack.org/#/q/status:open+topic:story-attachments Attachment changes
19:11:17 <SotK> I implemented the basic functionality needed for story attachments
19:12:01 <SotK> there are some bits missing, for example if your backend has attachments disabled the webclient just hits a bunch of errors instead of behaving sensibly
19:12:18 <fungi> i call that "polish"
19:12:34 <SotK> yep, me too
19:12:53 <fungi> er, "polishing" perhaps so as not to be confused with the national language of poland ;)
19:13:27 <SotK> on a similar note, you have to manually set the ACL on the swift container even if you let storyboard create it automatically
19:14:10 <diablo_rojo> Looks like a solid start to me.
19:14:35 <diablo_rojo> Way further than I would be if I was the primary dev on the hook ;)
19:14:40 <diablo_rojo> So thank you SotK!
19:14:50 <SotK> np :)
19:15:22 <SotK> I started prototyping it and then accidentally made most of it and just decided to finish
19:15:57 <fungi> in theory if sb can create a container it should also be able to set acls via the same api?
19:16:10 <SotK> yep, should be trivial to add
19:16:23 <fungi> again, detail which can be ironed out later, if it just ends up as documentation i think that's perfectly fine too
19:17:06 <fungi> and also irrelevant for deployments which don't expect to make use of private stories
19:17:39 <SotK> the default is fully private so it needs doing for every deployment
19:17:52 <SotK> but yeah, its not exactly onerous, it would just be neater to add it in
19:18:08 <fungi> oh, got it
19:18:21 <fungi> fail closed is safer anyway at least
19:19:06 <SotK> indeed
19:19:17 <diablo_rojo> indeed
19:19:35 <fungi> i've only just skimmed so far, but i like that this is all fairly bite-sized changes. nothing massive
19:20:20 <SotK> yeah it turned out to be quite a bit easier than I expected since all the hard bits are handled by swift itself
19:20:21 <diablo_rojo> Yeah that is super appreciated
19:22:19 <SotK> I also pushed my config file and a docker-compose.yml file which runs the services needed to test the patches to my github for now
19:22:36 <SotK> #link https://github.com/ColdrickSotK/storyboard-environment Config for testing
19:22:57 <diablo_rojo> Oh cool
19:23:16 <SotK> I intend to turn that into something more complete and push it to the storyboard repo in the near future
19:23:30 <diablo_rojo> Sounds good.
19:24:29 <fungi> that'll be awesome for getting new contributors up to speed, i think
19:24:30 <SotK> along with some docs to go along with it, which hopefully will allow a quick way to get a development environment up and running without needing to remember to install and configure all of the things
19:24:42 <fungi> absolutely
19:24:50 <fungi> that's a huge help
19:26:15 <diablo_rojo> Yes, super helpful
19:26:21 <SotK> I think that's all I have on attachments
19:26:32 <SotK> looking forward to reviews :)
19:27:01 <fungi> thanks!!!
19:28:23 <SotK> #topic Moving database closer to site
19:28:56 <fungi> #link https://etherpad.openstack.org/p/gCj4NfcnbW Database move from Trove to local MySQL service on storyboard.openstack.org
19:29:08 <fungi> that's the current migration plan
19:29:31 <fungi> the new xenial-based deployment is up and you can in theory test it out with a local /etc/hosts edit in the meantime
19:29:44 <fungi> though it's still using trove until the migration is performed
19:30:28 <fungi> i am also suddenly worried by the story jungleboyj just mentioned in #storyboard a few minutes ago, and would like to rule out any relationship to the db move before proceeding
19:30:46 <fungi> #link https://storyboard.openstack.org/#!/story/2004948 Unable to create worklists ... I am getting a 500 error
19:31:29 <diablo_rojo> Yeah, somewhat concerning
19:31:59 <SotK> me too, looks a bit suspicious
19:32:18 <fungi> once we're comfortable with the maintenance plan (it's basically a reflection of what i did for storyboard-dev.o.o a few weeks ago), we just need to pick a quiet 5-ish minutes to do the move
19:32:25 <jungleboyj> eharney:  Was seeing a number of HTTP 500's as well.
19:32:46 <jungleboyj> That was all in the last hour if you have logs.
19:32:47 <SotK> though, I expect that the code that threw that error could be improved significantly
19:33:07 <jungleboyj> We were trying to do some design for moving Cinder to storyboard but couldn't make much progress.
19:33:14 <fungi> jungleboyj: we definitely have logs, though the sql error is likely sufficient to track it down
19:33:39 <jungleboyj> We had a number of other questions that I will follow up on at some point in the storyboard channel.
19:33:49 <fungi> much appreciated!
19:34:02 <SotK> indeed, sorry about the issues :(
19:34:19 <SotK> the plan looks sensible to me
19:34:34 <SotK> but yeah, we should make sure this is unrelated (or fix it if it is)
19:35:03 <diablo_rojo> jungleboyj, happy to help with suggestions for organization if you want help too
19:35:10 <fungi> well, we likely need to fix it either way
19:35:36 <SotK> yeah, I realised that was terribly phrased after pressing enter
19:35:43 <fungi> and even SotK and diablo_rojo have local shell accounts on the storyboard-dev server so doesn't just need me to look into it
19:36:00 <jungleboyj> diablo_rojo:  Thanks.  I think we have come up with a plan going forward but would like to be able to set up a PoC first.
19:36:20 <SotK> anything else on the db move?
19:36:48 <fungi> nope, only other thing i haven't done yet is to test out the new deployment and confirm it seems to be serving the correct stuff
19:36:51 <diablo_rojo> jungleboyj, sounds good
19:37:00 <fungi> services are running but i haven't exercised it yet
19:38:10 <SotK> #topic In Progress Work
19:39:24 <SotK> I also sent various small patches to make things nicer and fix various issues that came up whilst working on attachments
19:39:27 <diablo_rojo> I have several patches I need to update..
19:40:26 <SotK> I still have to review one of yours I think
19:41:01 <SotK> and I want to try to reproduce the weird login bug that fatema was seeing the other week to work out whats going wrong
19:41:13 <diablo_rojo> I saw several reviews from you, but haven't checked if they were all covered :)
19:41:23 <diablo_rojo> I have plenty of work to do either way
19:42:32 <SotK> good :)
19:44:17 <SotK> #topic Open Discussion
19:45:07 <SotK> I'll leave this open for a minute or two in case anyone has anything they want to raise
19:47:10 <diablo_rojo> There's that Manila ML thread
19:47:12 <diablo_rojo> about issues
19:47:39 <diablo_rojo> I was going to post on it about the migration and how they should keep storyboard in mind when planning/discussing things
19:47:39 <SotK> oh I think I've missed that
19:47:41 <fungi> a new one? did i miss spotting it?
19:47:53 <diablo_rojo> uhh theres a link on the agenda
19:47:55 <diablo_rojo> one sec
19:48:00 <fungi> i'll find
19:48:04 <SotK> ha so there is
19:48:05 <SotK> sorry
19:48:20 <SotK> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
19:48:22 <fungi> thanks for spotting that!
19:49:06 <fungi> okay, so i did read that one (and suggested they move from google spreadsheets to ethercalc for openness/inclusivity, and they seem interested in doing that too)
19:50:21 <fungi> oh, wait, it was another (neutron?) bug triaging thread where i recommended ethercalc... this is the one which spontaneously inticated they were moving there
19:50:28 <diablo_rojo> fungi, huh, I don't see a response from you on that thread
19:50:48 <diablo_rojo> Got a link to that one?
19:50:51 <fungi> and i remember it warming the cockles of my heart
19:50:57 <fungi> sure, just a sec
19:51:23 <diablo_rojo> Lol
19:51:49 <fungi> http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002372.html
19:52:04 <fungi> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002372.html [Neutron] - Bug Report for the week of Jan 29th- Feb4th.
19:53:11 * SotK agrees that it may be worth emailing about keeping storyboard in mind
19:53:21 <fungi> yes, absolutely
19:53:44 <diablo_rojo> Its one of my pinned emails to reply to today
19:53:52 <diablo_rojo> still digging out of the FOSDEM hole
19:53:53 <fungi> oh, speaking of neutron, it may be a worthwhile exercise to repeat the import attempt on storyboard-dev again now that it's a different server and db backend
19:54:07 <diablo_rojo> Oh good call
19:54:26 <diablo_rojo> I can definitely add that to my list of things to do
19:54:27 <fungi> since we can at least quickly rule those out and likely confirm the same behavior is still present
19:55:13 <diablo_rojo> Yeah totally
19:55:27 <diablo_rojo> One other thing.
19:55:43 <diablo_rojo> If we want to try to get another outreachy intern we need to apply by the 12th of March.
19:56:01 <diablo_rojo> I don't know we can get anyone as awesome as fatema, but I think we should try :)
19:56:16 <SotK> yeah I agree
19:56:29 <diablo_rojo> Will put together an etherpad with the application info for you both to look over if you're willing to help me out :)
19:56:36 <diablo_rojo> SotK, wanna be my co mentor again?
19:56:36 <SotK> and this is significantly more time to prepare than we had last year I think
19:56:46 <diablo_rojo> Yep :)
19:56:54 <SotK> sure, and I'll try to be more around this time too
19:57:52 <diablo_rojo> Worked out pretty well last time, but I won't object to more help :)
19:58:34 <SotK> :)
19:58:43 <SotK> we're almost out of time
19:58:46 <SotK> anything else?
19:59:32 <fungi> i got nothin'
19:59:57 <SotK> in that case, thanks for coming folks!
20:00:01 <SotK> #endmeeting