*** tosky has quit IRC | 00:36 | |
*** jamesmcarthur has joined #storyboard | 01:17 | |
*** jamesmcarthur has quit IRC | 01:42 | |
*** jamesmcarthur has joined #storyboard | 01:42 | |
*** jamesmcarthur has quit IRC | 01:47 | |
*** jamesmcarthur has joined #storyboard | 02:36 | |
*** jamesmcarthur has quit IRC | 02:37 | |
*** jamesmcarthur has joined #storyboard | 03:44 | |
*** jamesmcarthur has quit IRC | 04:15 | |
*** jamesmcarthur has joined #storyboard | 04:17 | |
*** jamesmcarthur has quit IRC | 06:11 | |
*** jamesmcarthur has joined #storyboard | 06:12 | |
*** jamesmcarthur has quit IRC | 06:17 | |
*** jamesmcarthur has joined #storyboard | 06:42 | |
*** jamesmcarthur has quit IRC | 08:39 | |
*** tosky has joined #storyboard | 08:49 | |
*** jamesmcarthur has joined #storyboard | 10:36 | |
*** jamesmcarthur has quit IRC | 10:41 | |
*** jamesmcarthur has joined #storyboard | 11:37 | |
*** jamesmcarthur has quit IRC | 11:42 | |
*** jamesmcarthur has joined #storyboard | 11:53 | |
*** jamesmcarthur has quit IRC | 11:59 | |
*** jamesmcarthur has joined #storyboard | 12:09 | |
*** jamesmcarthur has quit IRC | 12:14 | |
*** jamesmcarthur has joined #storyboard | 13:51 | |
*** jamesmcarthur has quit IRC | 13:55 | |
*** jamesmcarthur has joined #storyboard | 16:33 | |
*** diablo_rojo has joined #storyboard | 17:04 | |
diablo_rojo | Meeting in 5! SotK fungi! | 17:56 |
---|---|---|
fungi | k | 17:57 |
SotK | \o/ | 17:57 |
* diablo_rojo runs to grab more caffeine and breakfast | 17:57 | |
diablo_rojo | Ready! | 18:02 |
SotK | #startmeeting storyboard | 18:03 |
openstack | Meeting started Thu Jan 14 18:03:41 2021 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:03 |
*** openstack changes topic to " (Meeting topic: storyboard)" | 18:03 | |
openstack | The meeting name has been set to 'storyboard' | 18:03 |
diablo_rojo | Hello! | 18:04 |
SotK | hi everyone! | 18:04 |
diablo_rojo | Happy New Year! | 18:04 |
SotK | happy new year :) | 18:04 |
fungi | samesies | 18:05 |
SotK | I'd link the agenda but its about 6 months old so it feels a bit pointless | 18:05 |
diablo_rojo | Lets skip the part where we all feel guilty and move on to more productive things. | 18:05 |
SotK | agreed | 18:05 |
diablo_rojo | Lol yeah. I did not update it. I opted for more caffeine instead. | 18:05 |
SotK | a good choice imo | 18:05 |
fungi | we can always choose to feel guilty in private later ;) | 18:05 |
diablo_rojo | I always do :) | 18:06 |
SotK | I quite fancy a meeting where we think about what we want to actually get done in the coming months and start with a fresh agenda next time, unless folk have other ideas | 18:06 |
diablo_rojo | Sounds like a solid plan to me | 18:06 |
diablo_rojo | +1 | 18:06 |
fungi | i'm all for that | 18:06 |
SotK | alright then | 18:07 |
SotK | #topic Planning | 18:07 |
*** openstack changes topic to "Planning (Meeting topic: storyboard)" | 18:07 | |
SotK | that seems like a good heading | 18:07 |
diablo_rojo | I do love plans. | 18:07 |
fungi | i have quite a few things queued up, which all depend on opendev switching the storyboard.o.o deployment to using the container images we've been publishing | 18:07 |
fungi | so for me at least, that's the top storyboard-related priority | 18:08 |
SotK | yup, I think that feels like top priority for me too | 18:08 |
diablo_rojo | +2 | 18:08 |
fungi | gets our continuous deployment continuous again, so folks in opendev can take advantage of more recent fixes which have merged | 18:08 |
fungi | and also unblocks me from making progress on setting up the artifact storage backend | 18:09 |
SotK | do we know what the concrete steps to get that switch done are? | 18:09 |
diablo_rojo | Yes to all of that. | 18:09 |
SotK | is it something I can help with somehow? | 18:09 |
fungi | we do it all at this point with stuff in the system-config repo, including like-production test deployments in zuul jobs | 18:09 |
* fungi looks for a good example | 18:10 | |
fungi | #link https://opendev.org/opendev/system-config/src/branch/master/playbooks | 18:10 |
fungi | the various service-* playbooks in there | 18:10 |
fungi | service-zuul.yaml might be a good example | 18:11 |
fungi | the meat of the "zuul" role it refers to is here: | 18:12 |
fungi | #link https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/zuul/tasks/main.yaml | 18:12 |
diablo_rojo | so we need something like that for storyboard? | 18:13 |
fungi | zuul might be an unnecessary complicated example the closer i look at it | 18:15 |
diablo_rojo | There are a lot of parts :) | 18:15 |
fungi | part of the challenge is that we have a mix of some services which we deploy from containers we build our own forked versions of images for, and some where we consume externally-supplied images | 18:15 |
SotK | it makes some sense I think, presumably we'll need start and stop tasks like those in https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/zuul-scheduler/tasks too? | 18:16 |
fungi | likely | 18:17 |
SotK | (or just put the docker-compose stuff inside the main file, like the etherpad deployment seems to have I guess) | 18:17 |
fungi | etherpad isn't python-based but might be a cleaner example: | 18:18 |
fungi | #link https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/etherpad | 18:18 |
fungi | we do a docker-compose file for it in a template like this: | 18:19 |
fungi | #link https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/etherpad/templates/docker-compose.yaml.j2 | 18:19 |
fungi | but could just be installed as a normal file if we don't need to parameterize zecrets | 18:19 |
fungi | the other major part i hinted at earlier is deployment testing | 18:20 |
fungi | #link https://opendev.org/opendev/system-config/src/branch/master/zuul.d/system-config-run.yaml | 18:22 |
diablo_rojo | Yeeeah.. | 18:22 |
fungi | if you scroll down to the system-config-run-etherpad job for example, that is a production-like deployment test which exercises all of the deployment tooling for a service | 18:23 |
fungi | it gives the job two nodes, one of which is our deployment bastion (bridge.o.o) and the other of which is a server to set up as an etherpad instance (etherpad01.o.o) | 18:23 |
fungi | these aren't our actual production servers, they're just ephemeral job nodes set up similarly at job runtime for testing purposes | 18:24 |
fungi | you'll see the job runs our actual production deployment playbooks on them though | 18:24 |
diablo_rojo | I'm still following. | 18:24 |
diablo_rojo | So its the playbooks for like service-etherpad and defining the ansible roles we don't have/need to write for storyboard? | 18:25 |
fungi | basically, whatever we need to glue together the right docker images | 18:26 |
*** jamesmcarthur has quit IRC | 18:26 | |
SotK | that's a really nice testing setup | 18:26 |
SotK | OK I think I understand what is needed | 18:26 |
fungi | the other key bit for the testing is the testinfra scripts, which basically exercise their respective services: https://opendev.org/opendev/system-config/src/branch/master/testinfra | 18:26 |
fungi | so the etherpad one for example just checks that you can reach the api socket over loopback | 18:27 |
fungi | but we can do far more complex testing of a service, that's a very simple example | 18:27 |
fungi | anyway, the goal is not to test the software itself, but to test that it was able to deploy and start up correctly | 18:27 |
fungi | basically exercise the deployment tooling itself | 18:28 |
diablo_rojo | Yeah okay. That makes sense. | 18:28 |
SotK | makes sense | 18:28 |
SotK | are you likely to have time to get to this soon, or shall I do some work on it over the next few weeks? | 18:29 |
fungi | it's really hard to say. i'm often sucked into trying to deal with emergencies (like right now afs is on fire), and that's rarely predictable | 18:29 |
fungi | so if anybody else is interested in trying to make progress on it, that would be amazing | 18:30 |
fungi | the up-side to this new deployment+testing model is that you can basically end-to-end test that the proposed deployment will work before we ever stand up a production server for it | 18:30 |
fungi | we can also fairly easily hold a node from the test job and manually poke it to do more thorough exploration | 18:31 |
SotK | alright then, I'll make that my priority to work on then | 18:31 |
fungi | thanks! | 18:31 |
diablo_rojo_phon | Ugh. Flaky WiFi today. | 18:32 |
diablo_rojo_phon | If there's anything I can do to help SotK, let me know. | 18:32 |
SotK | will do | 18:32 |
SotK | I think after that's sorted and we've got the blocked stuff moving again, I think the next priority needs to be addressing the impending death of AngularJS | 18:34 |
SotK | #link https://docs.angularjs.org/misc/version-support-status | 18:34 |
*** diablo_rojo has quit IRC | 18:34 | |
diablo_rojo_phon | I can sign up to do an audit of open patches and see if anything needs updating. | 18:34 |
fungi | feel free to hit me up with questions or remind me what changes you've pushed for feedback too | 18:34 |
diablo_rojo_phon | Ah yes. What fun. | 18:34 |
SotK | tbh I'd guess that we're currently on an older version and out of support anyway | 18:34 |
diablo_rojo_phon | Yeah I would guess the same. | 18:35 |
fungi | i fully expect that to be the case | 18:35 |
diablo_rojo_phon | I know there are a lot of dependencies that need updating. | 18:35 |
diablo_rojo_phon | We had a list of them if I recall. | 18:35 |
* SotK expects that list would now contain our entire dependency list | 18:35 | |
diablo_rojo_phon | Hahahahahaha | 18:35 |
fungi | probably so | 18:36 |
diablo_rojo_phon | I really hope not, but probably. | 18:36 |
diablo_rojo_phon | So we need to replace angular.js with something else? | 18:37 |
SotK | ideally yes | 18:37 |
SotK | which basically means rewriting the webclient afaict | 18:38 |
SotK | modern Angular (the ostensible replacement for AngularJS) is quite different | 18:38 |
diablo_rojo_phon | Ughhhh alright. Well I can start some research into alternatives. | 18:38 |
SotK | to the extent that if we were to be switching to it I'd rather just switch to a nicer framework | 18:38 |
SotK | I know (I think I know anyway) that zuul uses react for its webclient | 18:39 |
fungi | right, if it's a full on rewrite to begin with, then evaluating alternatives is prudent | 18:39 |
SotK | I'm not really familiar with react, though I've used it a bit | 18:40 |
diablo_rojo_phon | Yeah I figured I would look into those two and see what else we have. I can probably put together an etherpad. | 18:40 |
fungi | yeah, zuul is using react currently | 18:40 |
SotK | I've used Vue a reasonable amount and am currently using it actively in my day job, so that would be my broad preference | 18:40 |
fungi | and react seems to rely on a js derivative language called jsx? | 18:41 |
SotK | indeed, I find it a bit distasteful but have been trying to teach myself to like it xD | 18:41 |
diablo_rojo_phon | I was just about to mention Vue lol | 18:41 |
SotK | I actually put together a prototype vue storyboard client last year to help me learn vue | 18:41 |
diablo_rojo_phon | Oh nice. | 18:42 |
SotK | which we could use as a starting point for something if we want to go that route | 18:42 |
fungi | also probably a good opportunity to fix some places where we ended up with business logic in the client rather than behind api methods | 18:42 |
SotK | there's an old and broken version of that prototype here: https://storyboard-vue.sotk.co.uk/ | 18:43 |
diablo_rojo_phon | Seems like a reasonable option. I'll add that to my notes. | 18:43 |
*** diablo_rojo has joined #storyboard | 18:43 | |
diablo_rojo_phon | Thanks! | 18:43 |
SotK | yeah I think that we can use this as an opportunity to address quite a few issues really | 18:43 |
fungi | particularly the current search implementation seems liek it does more client-side than it should | 18:43 |
* SotK looks pointedly at searching | 18:43 | |
fungi | heh | 18:43 |
diablo_rojo | Yay! I'm back. | 18:43 |
diablo_rojo | LOL | 18:43 |
diablo_rojo | Well I will take the research todo and present my findings next week? | 18:45 |
SotK | sounds good | 18:45 |
diablo_rojo | Coolio. | 18:45 |
SotK | I'll try to get that link updated with a working version of what I had | 18:45 |
diablo_rojo | Will wait to check that one out. | 18:46 |
diablo_rojo | I'll start with React and Angular. | 18:46 |
fungi | got a link handy for info on teh vue framework? | 18:47 |
diablo_rojo | https://vuejs.org/ | 18:47 |
diablo_rojo | ? | 18:47 |
diablo_rojo | https://vuejs.org/v2/guide/comparison.html | 18:48 |
fungi | perfect, thanks! | 18:48 |
diablo_rojo | might be more helpful | 18:48 |
* SotK was just about to send that same link xD | 18:48 | |
diablo_rojo | :D | 18:48 |
diablo_rojo | Cool. Then I guess we all have stuff to work on till next week. | 18:49 |
SotK | yup | 18:50 |
diablo_rojo | We have ten min left in the meeting. | 18:50 |
SotK | anyone have anything else they want to discuss? | 18:50 |
diablo_rojo | I don't think so. | 18:50 |
SotK | #endmeeting | 18:51 |
*** openstack changes topic to "StoryBoard - A task tracker for OpenStack development needs :: http://storyboard.openstack.org/ :: https://wiki.openstack.org/wiki/StoryBoard" | 18:51 | |
fungi | yeah, i think we've got some good direction on near-term priorities for now | 18:51 |
openstack | Meeting ended Thu Jan 14 18:51:18 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:51 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/storyboard/2021/storyboard.2021-01-14-18.03.html | 18:51 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2021/storyboard.2021-01-14-18.03.txt | 18:51 |
openstack | Log: http://eavesdrop.openstack.org/meetings/storyboard/2021/storyboard.2021-01-14-18.03.log.html | 18:51 |
SotK | thank you all! | 18:51 |
fungi | thanks SotK! | 18:51 |
diablo_rojo | Thanks SotK! | 18:52 |
SotK | alright, the prototype at https://storyboard-vue.sotk.co.uk/ is mostly working again (and also updated with everything I did) | 19:06 |
diablo_rojo | Yay! | 19:07 |
SotK | it doesn't have any way of signing in, but there's an old webclient up at https://storyboard.sotk.co.uk/ if you want to add content for some reason | 19:07 |
diablo_rojo | Got it. Thank you! | 19:08 |
*** diablo_rojo has quit IRC | 21:48 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!