15:00:32 <gagehugo> #startmeeting openstack-helm
15:00:33 <openstack> Meeting started Tue Mar  9 15:00:32 2021 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:36 <openstack> The meeting name has been set to 'openstack_helm'
15:00:43 <gagehugo> #link https://etherpad.opendev.org/p/openstack-helm-weekly-meeting agenda
15:00:55 <reddy> o/
15:00:57 <sangeet> Good Morning!
15:00:57 <jinyuanliu> \o
15:01:02 <miniroy> \o
15:01:39 <srwilkers> o/
15:02:31 * sophieh2020 \o
15:02:35 <stevthedev> o/
15:04:38 <gagehugo> Alright let's get started
15:04:40 <gagehugo> #topic Simplfied openstack deployment using helm3
15:04:46 <gagehugo> portdirect: o/
15:05:03 <portdirect> hey!
15:05:38 <portdirect> so ive been working on a simplified lcm for openstack via helm
15:06:29 <portdirect> the repo is here: https://github.com/portdirect/openstack-in-a-can
15:07:00 <portdirect> in summary it deploys a full stack (nova, neutron/ovs & heat) using rook as the storage backend
15:07:19 <portdirect> the control-plane is in a single k8s deployment
15:07:25 <portdirect> rather than spread out
15:07:45 <portdirect> which makes troubleshooting a bit easier
15:08:34 <portdirect> compared to osh - i think this model may be a good fit for edge and small deployments
15:08:42 <srwilkers> i'm really liking the templating approach here
15:09:11 <portdirect> and so was wondering if it would be possibble to make a branch in osh to house this?
15:09:36 <portdirect> srwilkers: i thought you would
15:10:03 <portdirect> it basicly does everything in gotpl as variables, before finally rendering out
15:10:32 <portdirect> which allows us to overlay at various stages
15:10:33 <portdirect> eg:
15:10:42 <srwilkers> call me mad, but i find this much simpler to read and work with
15:10:50 <portdirect> https://github.com/portdirect/openstack-in-a-can/blob/master/openstack/values.yaml#L90-L107
15:10:50 <sangeet> So the k8s will still be deployed as is done in AIO
15:11:14 <portdirect> sangeet: yes!
15:11:23 <sangeet> I like the approach
15:11:39 <portdirect> this would get you working openstack for a small (>50 nodes) deployment withL
15:11:51 <portdirect> 1) deploy k8s (eg minikube/aio/capi)
15:11:52 <lamt> this is the same approach as one used for airship/charts right?
15:11:54 <portdirect> 2) deploy rook
15:11:59 <portdirect> 3) deploy openstack chart
15:12:12 <portdirect> lamt: its an evoultion of that - but the same core
15:12:19 <lamt> ah
15:12:42 <portdirect> the biggest thing being the storing of default config files: https://github.com/portdirect/openstack-in-a-can/tree/master/openstack/files/defaults
15:13:20 <gagehugo> I see there are default values for each service
15:13:32 <portdirect> im still working on this, but should have it pushed within the next hour
15:13:47 <portdirect> but this uspports either in place templating, eg: https://github.com/portdirect/openstack-in-a-can/blob/master/openstack/files/defaults/nova/etc/nova/nova.conf#L11
15:14:12 <portdirect> or using the same format we have for osh:
15:14:15 <portdirect> https://www.irccloud.com/pastebin/MGTVlRec/
15:14:44 <portdirect> which then lets us override via the values simpley
15:14:46 <portdirect> https://www.irccloud.com/pastebin/6f1yfV4h/
15:16:14 <srwilkers> i'd definitely like to see a branch set up for this - it's enticing
15:16:58 <gagehugo> we can probably do a branch for this
15:17:04 <gagehugo> maybe "edge" branch
15:17:13 <portdirect> gagehugo: that would be great!
15:17:35 <srwilkers> its so edgy
15:17:40 <portdirect> if the commiunity is up for it - i could push this, and some gates soon as its up
15:18:11 <gagehugo> that would be great
15:18:25 <lamt> I think folks have been asking for helm3 support for awhile so this would be great
15:18:30 <srwilkers> i'd give it a look over and sprinkle some reviews in
15:18:47 <portdirect> srwilkers: that would be great
15:19:04 <sangeet> +1
15:20:35 <srwilkers> hows it going, supporting both helm v2 and v3?
15:20:41 <srwilkers> not to derail too much, but curious given the comment
15:20:52 <stevthedev> Interesting chart structure. Took me a bit to wrap my head around but that is pretty cool portdirect
15:21:06 <gagehugo> it "works" with v2 and v3
15:21:25 <portdirect> stevthedev: yes - there are a few things i took from kustomise etc as inspriation
15:21:45 <portdirect> with the goal of making the charts/templates really easy to work with
15:22:11 <portdirect> but there are quite a few deltas from where we have been - using gotpl to render text
15:22:17 <jinyuanliu> i think for quite a long time, both V2 and V3 should coexist
15:22:32 <portdirect> jinyuanliu: this works with both
15:22:59 <portdirect> though i do recommend v3 - its got support, and also a better rendering engine
15:23:16 <miniroy> how easy would it be to "patch" with this, since everything is in a single deployment
15:23:48 <portdirect> oh miniroy
15:23:58 <portdirect> our pains with patching
15:24:04 <portdirect> is why this thing exists :D
15:24:33 <miniroy> I figure as much but felt like asking anyway  :)
15:24:37 <portdirect> whats here: https://github.com/portdirect/openstack-in-a-can/blob/master/openstack/templates/helpers/_template.tpl#L10-L162
15:24:40 <miniroy> since I have never seen it mentioned or done
15:24:54 <portdirect> was originally the 'yaml slammer' that was discussed at the ptg a few years ago
15:25:11 <portdirect> and it lets us over-ride every aspect of the rendered output if required
15:25:23 <srwilkers> i was going to mention the yaml-slammer, but figured the reference would be lost on most
15:26:05 <portdirect> eg, changing this to 'Always' https://github.com/portdirect/openstack-in-a-can/blob/master/openstack/templates/Deployment-openstack-layers/_glance.tpl#L9
15:26:19 <portdirect> can either do it via the template itself
15:26:21 <miniroy> I get the name, it looks pretty terrifying as-is
15:26:48 <portdirect> or can layer over it: https://github.com/portdirect/openstack-in-a-can/blob/master/openstack/values.yaml#L90-L99
15:26:57 <portdirect> its actually pretty robust code
15:27:04 <srwilkers> i mean, it's not as crazy as the daemonset overrides foo
15:27:09 <srwilkers> so there's that
15:27:20 <portdirect> as lamt pointed out - the airship charts repo has been using this for several months now, though as a 'latent' feature
15:27:27 <portdirect> lamt: have we seen any issues?
15:27:50 <miniroy> I am with stevthedev, it will take us mortals awhile to wrap our head around this
15:28:01 <lamt> nope that structure works well, though I think we could use more documentation
15:28:19 <portdirect> miniroy / stevthedev: it helps if you sit upside down - gotpl is a mind warp sometimes
15:28:23 <lamt> on how to provide the overrides - it is not obvious at first
15:28:36 <portdirect> lamt: thats very fair - and is lacking atm
15:28:36 <lamt> lol
15:28:40 <gagehugo> more documentation is always good
15:29:03 <miniroy> and a good yoga mat
15:29:24 <portdirect> so - if we get a branch up, i can seed with code this week, and start on docs over the weekend
15:29:36 <miniroy> I do admit I at least like the concept
15:32:22 <gagehugo> sure
15:32:50 <gagehugo> portdirect: I'll see about getting a branch for this
15:32:51 <portdirect> one other thing that id like to bring up
15:33:04 <portdirect> is that u was using victoria images based on debian bullseye
15:33:13 <portdirect> and needed to patch up loci a bit
15:33:27 <portdirect> https://github.com/portdirect/openstack-in-a-can/blob/master/docker/openstack/build.sh#L9-L19
15:33:41 <portdirect> can someone take a look at this?
15:34:00 <sangeet> I can
15:34:17 <gagehugo> Seeing sed in a script is always comforting
15:34:34 <portdirect> sangeet: that would be great
15:34:46 <portdirect> gagehugo: thought youd like the 'quality' work there :D
15:35:13 <portdirect> oh one more thing
15:35:24 <gagehugo> do we have victoria images?
15:35:25 <portdirect> its already e2e tls ;)
15:35:41 <portdirect> gagehugo: i dont think so, one of the reasons i built some
15:36:15 <gagehugo> hmm ok
15:36:25 <lamt> should probably get all the images updated to the latest - is it W?
15:36:41 <gagehugo> W is the soon to be released release
15:36:52 <lamt> ah thought that's released already
15:37:08 <gagehugo> then it will be warrior princess
15:37:18 <lamt> lol
15:37:42 <portdirect> the one thing this needs 'above' the osh images is in horizon: https://github.com/portdirect/openstack-in-a-can/blob/master/docker/openstack/build.sh#L112
15:38:07 <portdirect> everywhere else - the deps/profiles are cut back to match the loci defaults
15:40:59 <portdirect> that was i had for now :)
15:41:42 <gagehugo> thanks portdirect, we can get a branch for this, it looks interesting
15:42:07 <gagehugo> #topic Open Discussion/Reviews
15:42:20 <gagehugo> Anyone have anything they want to discuss or something they want reviewed?
15:45:54 <gagehugo> thanks everyone, have a good week
15:45:57 <gagehugo> #endmeeting