14:03:13 #startmeeting airship 14:03:14 Meeting started Tue May 26 14:03:13 2020 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:17 The meeting name has been set to 'airship' 14:03:19 #topic Rollcall 14:03:32 o/ 14:03:33 Hello all, and for those in the US welcome back from a long weekend :) 14:03:40 Here's our agenda for today: https://etherpad.opendev.org/p/airship-meeting-2020-05-26 14:03:41 o/ 14:03:42 o/ hey! 14:03:46 o/ 14:04:05 o/ 14:04:15 o/ 14:04:38 Great to see you all here today, thanks for joining 14:04:40 o/ 14:04:42 let's get started: 14:04:55 #topic Project Creation Request: airship helm chart repository 14:06:10 This is to discuss the need for a new airship project, which will serve as a home for airship-related helm charts, as well charts maintained by the airship team for airship-related "use cases" 14:06:28 as much as possible, airship will simply be a "consumer" of helm charts 14:06:51 but occasionally, we'll need to fill a gap, as we have in the past 14:07:48 What is this specific chart for? 14:07:50 in Airship 1, airship typically leveraged a lot of helm charts form the openstack-helm projects, and we still will in the future. However, OpenStack-Helm is trying to focus its mission more specifically on the OpenStack projects (and their dependencies) and to avoid being a clearinghouse for unrelated helm charts 14:08:51 roman_g: a good example is the podsecuritypolicy helm chart that lives in openstack-helm-infra -- that one has nothing to do with openstack, but was created by the airship team. That would make a good candidate to move into the airship namespace 14:09:32 In addition, we'll need new charts for airship 2 use cases -- portdirect has a couple (e.g. dex) in his personal github which need to find a home 14:09:32 We usually have been placing charts alongside Airship 1 Microservices code. So in this case it's 3rd party code, which provides own helm-chart, but we need to host our own version for some reason, right? 14:09:46 exactly roman_g 14:10:16 when it makes sense, we'll just use an upstream chart that is maintained by another project 14:10:23 So are you looking at airship-helm to be that storageplace? 14:10:25 rather than having it live in airship 14:11:10 yep, that's the gist jtwill98 -- and per our community conventions, we discuss creation of any new airship projects here before pulling the trigger (to cut down on project sprawl) 14:11:33 gotcha 14:11:45 does anyone have any concerns with creating a new project for this use? 14:11:50 Sounds reasonable, I'm fine with it, as long as code and patches there get enough attention (maintenance, gates, code reviews), which we lately have been struggling on getting. 14:12:08 no - but please lets call it `charts` rather than `helm` 14:12:31 as it makes it much easier to explain to 3rd parties what it is 14:12:42 sounds great to me portdirect 14:12:45 (exp from OSH here) 14:12:46 thx 14:12:48 me too 14:12:51 :) 14:13:40 great! I will treat this conversation as an exercise in lazy consensus (an I am a very lazy person). If anyone has any concerns / additional thoughts, please bring them up here or later; I'll try to get that created this week! 14:13:46 sounds reasonable to me 14:13:49 ++ 14:13:50 ++ 14:14:07 alright, next topic: 14:14:14 #topic Virtual PTG next week 14:15:06 Y'all are aware already that the virtual Open Infra PTG will be held next week -- here is our agenda, which I've also been using to cross-link in some airship-related sessions with other groups at other times during the week: https://etherpad.opendev.org/p/airship-virtual-ptg-2020 14:16:05 In addition to the Airship sessions on Thursday and Friday (western hemisphere a.m.) we'll have a discussion on Monday with StarlingX and Wednesday with the Edge Group if anyone is interested in those particular topics 14:16:57 Feel free to add to the agenda anything else you'd like to do a deep dive into at the PTG, and links other team's agendas 14:17:30 I didn't add them to our etherpad yet, but OpenStack-Helm and Ironic will also be having PTG sessions - those will be good ones for interested airship parties 14:18:09 any additional thoughts / questions on this one team? 14:19:19 :dancer: Just arrived! 14:19:28 o/ abhijekjaiswal.kol 14:20:24 normally we cancel our weekly team meeting during the week of the PTG 14:20:44 O/ 14:20:48 But this time, we may or may not have any conflicts, since the PTG schedule is so spread out and opt-in 14:21:50 Travis Neely proposed airship/porthole master: [WIP] Convert pgutils to dbutils for MariaDB and ETCD support https://review.opendev.org/730779 14:21:54 So I could go either way. I'd suggest that if we don't end up with any agenda topics by next week, or a PTG conflict arises, we can cancel this meeting next week (I'd send out an email in that case) 14:22:38 Travis Neely proposed airship/porthole master: [WIP] Convert pgutils to dbutils for MariaDB and ETCD support https://review.opendev.org/730779 14:22:43 Sounds like a plan 14:22:52 cool - then I think we can move on to: 14:23:01 #topic Review Requests & Roundtable 14:23:07 https://review.opendev.org/#/c/709873/ [#24] Fix airshipctl config get-cluster filtering 14:23:07 https://review.opendev.org/#/c/707483/ document info subcommand 14:23:15 Yes agreed Wirth Metal3 M3 changes to CR and Ironic updates we have lot to catch up on nodux CI for both Centos8 and Ubuntu18 third party cu 14:23:24 Travis Neely proposed airship/porthole master: [WIP] Convert pgutils to dbutils for MariaDB and ETCD support https://review.opendev.org/730779 14:23:29 +1 pramchan 14:23:51 Nordix 14:24:16 A couple patchsets ready for review above - please give them a look today if possible! 14:24:36 Any additional roundtable topics today? 14:25:57 No. 14:26:18 alrighty, then I will give you a half hour of your day back. Thank you all for your participation today, and have a great week! 14:26:27 #endmeeting