15:00:13 #startmeeting openstack-helm 15:00:14 Meeting started Tue Aug 11 15:00:13 2020 UTC and is due to finish in 60 minutes. The chair is stevthedev. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:17 The meeting name has been set to 'openstack_helm' 15:00:29 Good morning 15:00:32 o/ 15:00:42 Im on this opendev container security call so Im double booked 15:00:44 o/ 15:00:50 morning! 15:01:13 That sounds important 15:01:24 How is the vr conference so far? 15:01:26 \o I am multitasking 15:01:46 VR conference would be cool 15:01:54 #link https://etherpad.opendev.org/p/openstack-helm-weekly-meeting agenda btw 15:02:39 dwalt haven't heard from you in a while. Hope everything is going well 15:03:06 Good to see you stevthedev! how's it going? 15:03:08 I am doing well 15:03:34 Just got situated in a new apartment :) 15:03:39 Pretty good all n all 15:03:57 Haha, so did I. Well, still getting situated 15:04:11 That's good to hear 15:04:16 Nice! Where at? 15:04:32 I am all too familiar with the "getting situated" period 15:04:59 Downtown, kinda near work. It seems like we probably wont return there anytime soon though 15:05:12 Anyway, 5m in. Would you like to start? 15:05:24 #topic Airship 2 OpenStack composite 15:05:48 Very nice. Yeah, it sounds like we are stuck at home for a bit longer :P 15:05:54 I am closer to downtown now, fwiw 15:06:01 sure! I can start 15:06:09 * dwalt begins typing 15:06:39 Nice! Not to put you on the spot or anything, but the agenda is light today :P 15:09:03 Airship is a heavy user of openstack-helm. Since Airship 1, we have stored Airship documents that can deploy openstack-helm in the airship/treasuremap repository. Downstream operators adjust the documents in treasuremap to deploy private openstack-helm clouds using Airship. This model has not been without several issues. For one, documents downstream tend to drift significantly from the ones in treasuremap 15:09:03 since each update requires changes in two different repositories. Secondly, those chart overrides live very far away from the openstack-helm charts. The Airship team does everything we can to keep them up-to-date, but they inevitably fall out-of-date overtime since we are not aware of new chart changes. 15:10:02 With Airship 2, our model is changing. Using kustomize, we have introduced the idea of functions and composites. These are bite-sized units of YAML documents that define deployable software. For example, a function might represent a chart, and a composite might be composed of several functions. In Airship 2, our goal is to define all of the OpenStack charts as a single composite that can be inherited in a 15:10:02 downstream context and used with very few site-specific modifications. 15:12:50 The reason I am discussing this here today is that we would like to propose creating a new project to host an openstack-helm composite for Airship 2 operators or add an OpenStack composite to an existing openstack-helm repository. As most of you are Airship and openstack-helm operators yourselves, it would allow you to package your software for your airship deployments the way it is supposed to be. We have 15:12:50 started this process for some of our core components in airship/treasuremap, and we would like to help kick off that process here (i.e. set up proper gating and the structure of the repository). We also have some proof of concept OpenStack functions that we are testing in a downstream lab. 15:14:20 Sorry for the wall of text. I know it's a lot for an IRC meeting :D 15:15:19 As long as the use case is clearly defined, a new repo may be good 15:15:26 No, thank you! It's an interesting idea and it makes sense to start planning for Airship 2 compatibility 15:17:40 Unfortunately I'm still pretty new to the concepts of Kustomize. If I understand correctly, we need a place to define all of the OS functions (which are references to the OSH carts + values?) and the wrapping composite object ? 15:18:20 dwalt: I assume you could assist with this effort? 15:18:21 That would give us a single 'thing' to deploy OS in airship 2 clusters? 15:19:21 stevthedev Exactly. Here is an example of some we have defined in airshipctl #link https://github.com/airshipit/airshipctl/tree/master/manifests/function 15:19:56 And the composites just group those functions together #link https://github.com/airshipit/airshipctl/tree/master/manifests/composite 15:20:46 gagehugo: of course! The Airship team wants to help setup these functions and composites + gate them. After they're in place, adding the values overrides is straightforward 15:20:57 ok cool 15:22:43 Im leaning towards a new repo maybe, but could possible also store these in the charts themselves. Im also not super familiar with Kustomize 15:24:46 Yeah. Looking through eg, the baremetal-operator function, it looks similar to a chart structure on its own. Does Kustomize play with the existing charts very well, or would we be creating some new yaml for each component? 15:25:04 I assume its the latter 15:25:37 That's the impression I get, if so then I think a separate repo for these documents makes sense 15:25:53 Glad your team is open to the idea. We can let this soak a while if you'd like 15:26:11 Our team is eager to get OSH deployed with Airship 2 soon 15:27:15 Since Airship 2 relies on a very specific directory structure, I'm not sure if storing the functions in each chart would be possible 15:28:17 We've been moving our functions/composites to treasuremap since it essentially becomes a library of well-defined software ready to be deployed on airship 15:29:09 idk if another airship repo would work too with a group of osh people to maintain it 15:29:19 stevthedev: the new YAML would essentially just be a helmrelease file that replaces the Armada chart documents we used in Airship 1 and a kustomization.yaml file. It looks very similar 15:31:28 gagehugo: do you mean a repo like airship/openstack? 15:31:54 potentially, otherwise another osh repo would work too 15:32:03 thinking about the use cases for these documents 15:34:30 And dwalt, the aim here is the OS-specific components, right? Do you see components like LMA ending up as functions in treasuremap? 15:36:57 gagehugo: would hosting the composite in the airship namespace be more convenient for osh contributors? We thought bringing the composite/functions here would keep them closer to the charts themselves and reduce drift, since changing those overrides would be part of the osh workflow 15:37:37 If the goal is to keep them alongside the charts, then osh may be a better fit with them relying on the actual charts for gating 15:39:54 Said differently, changes that go into OSH right now require making an update to a set of downstream manifests. Since composites in Airship 2 more or less replace the need for downstream changes, moving them here would mean that all of the OpenStack gating in Airship 2 happens in one place, and in the same change or a change to an adjacent repository 15:41:15 My thinking is if Airship 2.0 is the primary consumer of these docs, a repo there may make sense. 15:41:20 I see the benefits to storing them in OSH too. We chose the standalone repository model since it's a bit more organized and would be considerably smaller in size. But the single repo model has its benefits too 15:41:23 We should discuss with the airship team 15:45:24 stevthedev: Possibly. We've been focusing on OpenStack for now, but we've discussed trying to store all functions as close to their charts/code as possible. So that could be LMA as well 15:46:36 gagehugo: Sure. Maybe this was too big of a bite to take for an IRC meeting. Would you be open to discussing this on the next Airship design meeting? This Thurs, 10am CDT 15:48:32 Sure 15:48:41 dwalt: This was a good topic though 15:48:53 Great. I'll add an agenda item 15:48:57 Thanks for the discussion all! 15:49:08 Thanks for bringing it! 15:49:44 Where's the Airship design meeting held? 15:52:05 looks like channel: #airshipit 15:52:11 bridge: #link https://attcorp.webex.com/attcorp/j.php?MTID=m931aabac041bb2548d4c0a6a93a363d3 15:52:21 agenda: #link https://etherpad.opendev.org/p/Airship_OpenDesignDiscussions 15:52:29 Cool, thanks! 15:52:31 sorry for the delay. Lots of clicking to find that :) 15:52:36 No worries 15:52:55 No worries at all. if there's nothing else for today, shall we wrap up? 15:54:47 #endmeeting