15:03:27 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:03:27 <opendevmeet> Meeting started Tue Sep  6 15:03:27 2022 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:27 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:27 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:03:38 <noonedeadpunk> #topic rollcall
15:03:39 <alarmclock> o/
15:03:40 <noonedeadpunk> o/
15:03:45 <noonedeadpunk> lol
15:12:00 <noonedeadpunk> #topic office hours
15:12:15 <noonedeadpunk> well, seems it will be relatively quite today on the meeting
15:12:33 <noonedeadpunk> NeilHanlon: regarding Rocky 9 - do you need any help with adding that?
15:15:43 <damiandabrowski> hello (sorry for being late)
15:16:30 <NeilHanlon> noonedeadpunk: not right now, i just need to get back to it. hoping i have some free time this week to try and get the changes in. i worked with mgariepy a bit ago to try and get the necessary centos-release-* packages into the Rocky base repos which will eliminate at least one change i have
15:17:11 <noonedeadpunk> ok, great
15:17:36 <noonedeadpunk> as we're closer and closer to Zed release date. We need at least to understand where are we wrt to distro support
15:18:30 <noonedeadpunk> I had some idea about how to optimize another chunk of our code that is for openstack resources creation.
15:18:59 <mgariepy> hello :D
15:19:01 <noonedeadpunk> As simple example - we do have several places where we do upload images - magnum, octavia, tempest, trove
15:19:45 <noonedeadpunk> So it sounds like we could create a role, that will be in charge of all resource creation, and place it in plugins (and maybe to ansible-collections-openstack) in the future
15:19:50 <mgariepy> i wasn't me for the package in the repos :)
15:19:55 <mgariepy> it*
15:20:38 <NeilHanlon> sorry.. tab completion.. mnasiadka -- i think they do Kolla things :)
15:20:58 <noonedeadpunk> And basically what brings me to that  - https://review.opendev.org/c/openstack/openstack-ansible/+/854235
15:21:09 <mgariepy> no worries i just wanted to make the record straith :D haha
15:21:37 <noonedeadpunk> I can't tell what specifically I don't like in this patch, it just looks a bit off from what we're doing everywhere
15:22:09 <noonedeadpunk> this might be also good step to drop resource creation from os_tempest role
15:22:41 <rajesh_gunasekaran> Hey Guys, i want to contribute, could you please help me with picking out some task to work on?
15:24:03 <noonedeadpunk> I was told, that andrewbonney does have a big chunk of this and may advice on how we want to make the structure
15:24:05 <noonedeadpunk> rajesh_gunasekaran: how familiar are you with OSA?
15:24:13 <anskiy> noonedeadpunk: that's a nice step, but it's too restricted, I guess. But, anyways, you can't cover anything, so as much as I would wonder about dropping my own playbook for resource creation, I don't see it happen :(
15:24:17 <damiandabrowski> noonedeadpunk: one thing concerns me, to create a resource you just need to execute one ansible module
15:25:07 <damiandabrowski> i wonder how including external role can simplify that even more :D
15:25:31 <noonedeadpunk> damiandabrowski: it's not always a case? Like for image lifecycle management you would need to have quite complicated flow
15:25:40 <anskiy> I could be done via that ansible thing, where you dynamically define, which module to use
15:26:33 <noonedeadpunk> Same with creating usable network - you need to create net, subnet,l3 router,  and wire things
15:27:00 <noonedeadpunk> With images - you might want to download it from remote server, unpack, convert, etc
15:27:08 <noonedeadpunk> I'm looking at octavia code now https://opendev.org/openstack/openstack-ansible-os_octavia/src/branch/master/tasks/octavia_amp_image.yml
15:27:52 <noonedeadpunk> it's not _that_ trivial given you want to drop old images wherever you can
15:28:43 <noonedeadpunk> Also for some role, you might need to create both networks and images
15:29:05 <damiandabrowski> for images - i agree... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/iGYFmZWPnlHbHpADfrfTmAIG)
15:30:25 <anskiy> noonedeadpunk: the problem with that role is that AFAIK ansible module for image can't use glance's `image-create-via-import`, to which you can just simply pass URL
15:30:52 <rajesh_gunasekaran> @noonedeadpunk OSA - doesn't ring a bell
15:31:11 <damiandabrowski> OSA - openstack-ansible
15:32:25 <noonedeadpunk> anskiy: well, you need also to configure glance properly for that and have a storage where images will be locally placed and served through web server
15:32:59 <noonedeadpunk> and even then it won't solve image rotation as example
15:33:06 <NeilHanlon> you definitely don't wanna see how I did this in my lab...
15:33:14 <NeilHanlon> and it doesn't solve rotation anyways 😂
15:33:40 <rajesh_gunasekaran> ah okay! i would say am a new comer with basic knowledge about openstack-ansible
15:34:27 <noonedeadpunk> rajesh_gunasekaran: then I would say you can help out with ensuring, that AIO does survive reboots :)
15:35:09 <noonedeadpunk> firstly aio is a good start to get aware about osa. and secondly, I can recall a bug report that was claiming it's not working
15:36:00 <noonedeadpunk> ok, so as an overall result it feels that idea about role for creating resources is useless
15:36:07 <rajesh_gunasekaran> okay sure! will follow as per your guidance
15:36:53 <damiandabrowski> noonedeadpunk: maybe we want to create a role just for image management and lifecycle management? that would be useful for sure
15:37:08 <noonedeadpunk> rajesh_gunasekaran: ie https://bugs.launchpad.net/openstack-ansible/+bug/1819792 and https://bugs.launchpad.net/openstack-ansible/+bug/1819790
15:37:42 <noonedeadpunk> rajesh_gunasekaran: I know they're quite old, but would be great to ensure that things are working fine
15:38:44 <noonedeadpunk> damiandabrowski: well, what I wanted to achieve is not to handle resource creation at all in any of os_<service> roles
15:38:50 <noonedeadpunk> and manage and maintain that separately
15:39:31 <noonedeadpunk> so that when ansible-collection-openstack updates or changes, we won't need to search where we use it and what do we use out of it
15:40:19 <noonedeadpunk> rajesh_gunasekaran: you can find aio docs here: https://docs.openstack.org/openstack-ansible/latest/user/aio/quickstart.html
15:41:15 <rajesh_gunasekaran> @noonedeadpunk Thank you, will go through the docs
15:41:37 <anskiy> maybe, ability to just plug in user-defined playbook on various stages (like, pre-setup-hosts, post-setup-openstack...) could help?..
15:41:47 <noonedeadpunk> and then if we need to create or add some resource we could jsut run a playbook rather then re-run some os_<service> role
15:42:30 <noonedeadpunk> anskiy: that is tricky. We do have that for adding new compute, but it's done through the bash script
15:43:44 <noonedeadpunk> I _think_ we have that also for upgrade script...
15:44:07 <noonedeadpunk> I meant that https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/add-compute.sh#L22
15:44:10 <anskiy> well, there is another downside: it's shorter path to get things done and not contribute :)
15:45:57 <noonedeadpunk> well... I'd say that if we're talking about resources, you might want/need to run their creating after each role rather then pre-openstack and post-openstack
15:46:05 <noonedeadpunk> but not sure....
15:46:30 <noonedeadpunk> Also I kind of run that full setup only in sandbox lol
15:46:47 <noonedeadpunk> rest would be just single playbook
15:46:57 <noonedeadpunk> anyway
15:48:08 <noonedeadpunk> as it's quite arguable, I won't push it really. It's totally not top prio.
15:48:15 <noonedeadpunk> But thanks for the feedback!
15:48:42 <noonedeadpunk> Is there anything else e want to quickly discuss?
15:48:50 * noonedeadpunk needs to run in 5 mins
15:49:05 <anskiy> https://bugs.launchpad.net/cloud-archive/+bug/1988270 nothing's going on in here :(
15:49:39 <noonedeadpunk> ¯\(◉◡◔)/¯
15:49:52 <anskiy> noonedeadpunk: you've said, you can reach for UCA-guys somehow, or did I misunderstood?
15:50:56 <noonedeadpunk> nah, it was idea that we need to reach them via irc but I could not find any. THough yes, I can likely ping charms folks, and hopefully they know who should take care of that
15:51:16 <noonedeadpunk> I will try to take care of that tomorrow morning
15:52:29 <anskiy> thank you :)
15:52:35 <noonedeadpunk> #endmeeting