15:00:29 #startmeeting openstack_ansible_meeting 15:00:29 Meeting started Tue May 10 15:00:29 2022 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:29 The meeting name has been set to 'openstack_ansible_meeting' 15:00:47 #topic rollcall 15:00:49 o/ 15:01:01 well, I'm actually semi-around 15:01:21 hey o/ 15:02:10 hello o/ 15:05:16 #topic office hours 15:05:16 o/ 15:05:46 I will be honest - I done nothing. I can't even recall what I was doing whole week... 15:06:03 Likely side-effect after moving to the new place... 15:06:26 jrosser: you had some issues with merging repo stuff - should we discuss it? 15:06:51 oh yes, i left it alone for a few days 15:07:01 but i think it's got all a bit circular 15:07:31 We can always disable CI to land that... 15:07:52 well maybe a couple of things to look at first 15:08:23 hi! 15:08:31 the glusterfs filesystem does not exist until we merge this https://review.opendev.org/c/openstack/openstack-ansible/+/837589/13/playbooks/repo-install.yml 15:08:57 the repo_install playbook needs updating to create it, as the current use of serial: breaks the installation 15:09:07 the tasks cannot be serial for those parts 15:09:40 but then logically the next patch to merge (until I thought about it) was this https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/839411 15:09:51 but i don't think thats ever going to pass without the first one 15:09:58 as the fs will not exist 15:11:25 i think rather than circular patches, i mean its very hard to get everything to pass in CI without making it circular 15:12:45 I also left comment for https://review.opendev.org/c/openstack/openstack-ansible/+/837589/13/ansible-collection-requirements.yml#40 just in case :) 15:12:58 ah yes i saw that 15:13:07 i got kind of diverted by playing with skyline 15:13:26 but we should try to get this gluster stuff merged becasue it is a big change and needs some testing for real 15:13:34 yeah 15:13:52 deleting / re-creating repo server containers has some subletlies now, for example 15:14:06 Btw regarding rbac topic - I guess there's no reall need to do changes this release since cinder/heat are still not ready 15:14:26 But I'd rather introduced service role anyway, despite discussions about it are still ongoing 15:15:01 we can suggest dropping all repo containers at once for example as well 15:15:10 as that should be fine I guess? 15:15:21 i mount /openstack/glusterfs in the current patches 15:15:24 As there's nothing _really_ important anyway 15:15:42 as there is UUID need to be preserved, else you can't re-create/join the cluster properly 15:15:56 so sometimes you need to keep that, sometimes you need to delete it 15:16:09 depends if you want to destroy the fs and start again, or to keep it 15:16:22 I actually thought it will get removed with force_containers_data_destroy ? 15:16:37 that does not seem to understand whatever bind mounts get made 15:16:37 But not sure 15:17:04 however in this case, i think that preserving it is the right thing to do for multinode 15:17:15 there is also an impact on re-deploying an infra node 15:18:12 having said all this - i really would like other eyes / opinions on it 15:20:02 yep, fair 15:20:24 another thing - do we want to have a presentation about project updates? 15:20:52 THere's no dedicated event during summit for that, but still marketing has some plan how to promote these 15:21:17 Basically they asked for a video 10mins tops to say about changes that were made lately 15:22:29 i guess we would have to look back over the etherpads to see what we did / did not do 15:23:14 yup, agree 15:23:38 I will try to put smth into other etherpad so we could review topics next week 15:24:50 okok, great 15:26:36 ok, what else we have on plate? 15:27:27 Except tons of stuff that needs to land? 15:27:47 hmmm yes - reviews / merging of lots of things 15:28:23 i should also say that i have done a proof-of-concept with the alternative dashboard, skyline 15:28:44 and it's ummmm - interesting to deploy 15:29:04 I can imagine, as it's nodejs iirc? 15:29:22 at least frontend part of it 15:30:00 there is a python part 'apiserver' then nodejs things for 'console' 15:30:02 i will spend some time on reviews tomorrow 15:30:12 and imho the code is very docker / kolla centric 15:30:43 and also confuses the service code with deployment tooling, as theres a executable to generate the required nginx config /o\ 15:32:05 but i think this is an opportunity to influence the skyline development to support wider tools and deployments 15:33:11 debugging this is really on the edge of my understanding though, so if anyone is interested with web development skills then please help out :) 15:42:08 tool to generate nginx config sounds as it sounds ofc... 15:42:26 And also I saw there's no SSO support atm 15:42:41 So I'd say they have plenty gaps as of todayy 15:43:14 but you're right, we'd better chime-in earlier then later 15:44:51 theres kind of two parts i think - ansible'ing up the deployment, pretty much whatever-it-takes to make it work 15:45:09 then work on tidying that all up and making it all more OSA-like 16:00:34 #endmeeting