13:59:28 #startmeeting airship 13:59:29 Meeting started Tue Aug 4 13:59:28 2020 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:59:32 The meeting name has been set to 'airship' 13:59:37 #topic Rollcall 13:59:43 o/ 13:59:43 o/ 13:59:49 o/ 13:59:56 Hey everyone, good morning/evening! Let's give it a couple minutes for folks to filter in before we get started 14:00:09 in the meantime, here's our agenda, and feel free to add anything: https://etherpad.opendev.org/p/airship-meeting-2020-08-04 14:00:44 o/ 14:01:15 o/ 14:01:23 o/ 14:01:40 alright, let's get started! 14:01:43 #topic Announcements 14:01:55 Take it away alexander.hughes 14:02:51 Thanks @mattmceuen! The nomination period for the 2020-2021 WC election has ended. At the end of this extended period there were 5 candidates all eligible, and 5 seats. As a result no formal voting was necessary. Please join me in welcoming the following to the WC: 14:03:03 • Drew Walters, AT&T • James Gu, Insight Global • Kostiantyn Kalynovskyi, Mirantis • Matt McEuen, AT&T • Sreejith Punnapuzha, Ericsson 14:03:31 congrats! 14:03:33 Congrats all! 14:03:56 Thanks :) happy to continue to work for y'all 14:04:30 Thank you! ++, looking forward to a productive year 14:04:36 Also, a big THANKS to our outgoing WC members Nishant, Stas, and Ian P -- really appreciate the work you've done over the last year 14:04:43 Glad to see Drew and Matt still serving the community on the WC, to see 3 new faces, and to continue working in other capacities with Ian, Stas and Nishant who elected not to nominate for this year 14:04:48 Congrats All! 14:05:05 Congrats!! 14:05:14 Thank you! Look forward to working with everyone in the new role 14:05:20 :slightly_smiling_face: 14:05:27 For our new WC members, reminder that the next WC meeting agenda is here: https://etherpad.opendev.org/p/airship-wc-meeting-2020-08-10 14:05:49 And a reminder to everyone that everyone is welcome to attend these meetings if you'd like 14:06:18 and for anyone needing a reminder on when the meetings are, or previous meeting agendas, check out the wiki 14:06:20 #link https://wiki.openstack.org/wiki/Airship/Airship-WC 14:06:25 Thanks all, Looking forward to working with everyone. 14:06:39 +1 14:06:48 ty @mattmceuen, ty @alexander.hughes - for the details 14:07:17 Moving on, a reminder about the OpenInfra summit the week of October 19-23. This event is free to register for, and will be 100% virtual 14:07:25 #link https://www.eventbrite.com/e/open-infrastructure-summit-2020-tickets-96967218561 14:07:31 #link https://cfp.openstack.org/ 14:07:51 Special reminder -- *TONIGHT* at 11:59pm PST is the deadline to submit your presentations to the CFP link 14:08:06 o/ 14:08:50 o/ 14:09:05 on behalf of people that are bad at remembering things, thanks for the reminder alex :) 14:09:15 :slightly_smiling_face: 14:09:31 +1 14:09:46 next up, Airship2.0 is progression towards the Beta milestone. We reached alpha a while back, and learned a lot of lessons in reaching that milestone 14:10:23 Some of these lessons led to changes in design decisions that were referenced in the "Airship Blog series", so Alan and Rodolfo have put up a new post summarizing those lessons learned, and what changes have been made to the design. I encourage you to read this new blog post here - 14:10:32 #link https://www.airshipit.org/blog/airship2-is-alpha/ 14:11:10 I will be working on updating all the old blog posts that contain inaccurate information with a pointer to this new post summarizing the changes. and in future TC newsletters you'll start to see what we've been calling the "post-alpha" blog series to continue the technical deep dives periodically 14:11:49 that's it from me if there's no questions I'll hand it over to @mattmceuen 14:12:19 great plan - agree, design has evolved this year, and updating our blog posts to point to the latest will be very helpful - thanks alex 14:12:42 but thanks for keeping us up to date on all those things 14:12:45 next up: 14:12:55 #topic New project request: hostconfig-operator 14:13:08 So we have Sririsha here? 14:13:10 *do 14:13:24 Yes Matt 14:13:31 Hey thanks for joining us 14:13:42 Sure Thank you Matt 14:13:56 Sririsha has been working on a new project for airship 14:14:30 As is usually the case, it's been in POC mode in github for a while, and we're thinking it's the right time to bring it formally in as an airship project so we can continue development in opendev 14:14:39 https://github.com/SirishaGopigiri/airship-host-config 14:15:15 This project fills a similar role to divingbell in Airship1, managing host-level configuration in a declarative way 14:15:28 but takes a different approach, following the Ansible Operator pattern 14:16:04 Sririsha actually just gave a great demo in the design call that just occurred, so once Rodolfo gets the link for that recording posted, I'd encourage anyone interested to take a look 14:16:22 We discussed a few things in that demo, just to summarize here: 14:16:52 1. today the project has a number of branches; we should merge everything to master (and then delete the branches) prior to importing into opendev 14:17:30 2. there is some good documentation Sririsha shared which would ideally live in the project itself. That could probably be moved either before or after moving the project into airship 14:18:08 3. there's a work in progress patchset against airshipctl to integrate the operator; we decided that we should move that work to treasuremap instead 14:18:33 Any questions on the operator? 14:19:12 you mean https://opendev.org/airship 14:19:17 which main? 14:19:52 yeah, we'd be looking to put this in as https://opendev.org/airship/ @pramchan 14:20:12 I see -thx 14:20:25 that will help get more folks reviewing / contributing to it 14:21:11 One thing to sort out here is exactly what to call the project - I've alternately seen it called "airship-host-config", "ansible operator", and "host config operator" 14:21:33 I would suggest that "hostconfig-operator" might be a good one, since I think that aligns to other operator project naming conventions 14:21:42 What do you all think? 14:22:49 +1 14:23:07 among the tree, I'd vote for hostconfig-operator 14:23:12 +1 14:23:13 ree->three 14:23:14 Cool - does that sound good to you too @sirishagopigiri 14:23:18 +1 14:23:28 Host config operator makes sense - for clarity its based on the ansible operator framework 14:23:30 +1 14:23:42 Yes Sounds good Matt 14:23:43 +1 14:23:56 +1 14:24:23 Thanks for clarifying the subtlety @pb269f, and thanks also for laying the foundation for this project too :) 14:24:48 +1 14:25:00 Np - once its moved I think the 1st thing we should do is get some gating round it 14:25:04 there are two methods in it Vagarent based and BYOK, will we have both in it? 14:25:06 Thank you Pete and Matt for all support! 14:25:13 alright then I think we have consensus -- sirishagopigiri I'll start working on getting the project created but won't pull the trigger till the branches are cleaned up; just keep me in the loop on that 14:25:33 @sirishagopigiri you've done some great work with it - thank you! 14:26:40 Sure Matt will let you once I cleanup 14:26:59 @pramchan the BYOK kind of approach is what we'd use in real life, and also most likely in gating. The Vagrant setup will be good for developers 14:27:15 Thank you Pete 14:27:28 Ok! if there's nothing else on this topic, I think we can move on? 14:27:44 #topic airshipctl-gate-script-runner-test: no successful builds in 2 days (50 builds) 14:27:50 @mattmceuen thx 14:28:04 #link https://zuul.opendev.org/t/openstack/builds?job_name=airship-airshipctl-gate-script-runner-test&project=airship/airshipctl 14:28:07 ouch - just getting back from a long weekend today, so this is news to me. how's it looking alexanderhughes 14:28:24 the last 50 builds (which spans two days) have had: 10 timeouts, 29 node failures, 11 outright failures 14:28:44 we've asked core reviewers to recheck patches until we get at least one successful run of airshipctl-gate-script-runner-test prior to merging 14:28:53 Bijaya Sharma proposed airship/airshipctl master: [#309] Removed unused constant https://review.opendev.org/743817 14:28:54 so I'd like to break these down into two categories: 14:29:13 1. timeouts, currently set to 1hr, our timeouts are occuring at 1hr2m-1hr5m, does the timeout need to be raised? 14:29:35 https://review.opendev.org/#/c/744523 14:29:41 there is a ptachset for timeout 14:29:45 Re timeout - should be raised 14:29:50 Nice 14:30:07 2. node failures, seems related to ongoing node pool issues we've been discussing. there was an action out of a previous committee meeting on working with AT&T, Dell, Ericsson on expanding the pool. has there been any updates? 14:30:40 Not really from my end, no response from City Networks. I’ve contacted them again. 14:30:58 I’ve been disconnected for a week. Came back yesterday. 14:31:11 There's a plan in place for some 3rd party gates for airship- but not sure where the wheels are there 14:31:56 I have an email from Michel asking for accounts for two more Ericsson people, Rahul & Rajini. Michelle says “Rahul will install OpenStack in the lab” (Rahul Vadisetty). 14:32:04 I’ll ask for meeting to see what’s going on. Looks to me like they/we are planning a node pool again? 14:32:24 Hmm, that's news to me jemangs 14:32:28 Same 14:32:48 Yes, or they just plan to use OpenStack... 14:32:50 I think we'd settled on 3rd party gating consistently 'for the e2e testing 14:33:04 Yeah, using openstack for 3rd party gating is fine 14:33:04 jemangs: thats hopefully it 14:33:22 I haven't been in contact with then since I set up the hardware, I'll ask for a meeting... 14:33:30 Perfect, thanks jemangs 14:33:31 The plan as I was aware was to deploy openstack, then drive that through Jenkins for 3rd party gate 14:33:50 So this hopefully aligns with the request you got 14:34:09 Ok sounds fine. My comment about node-pool was just "guessing". FYI I checked in the weekend and it looks like no one has accessed the lab yet. 14:34:51 OK, I'll get Alex B to check up this week 14:35:01 But it seems like they're about to start, as per the request for these account. I'll meet with them and get more info 14:35:41 that's good news -- thanks for driving this jemangs and welcome back :) 14:35:43 @pramchan Joining other call? 14:36:00 Thanks :-) 14:36:07 wb Jan-Erik :slightly_smiling_face: 14:36:54 that's all I've got on this for now, thanks for sharing the timeout patchset @james.gu. I added it to the call for reviews today 14:37:16 Thanks alex for raising awareness. Last thing on the agenda: 14:37:30 It is Siraj's patchset. would be great to have some review on it! 14:37:48 two patchsets for which review has been asked - and one of them is that one^ 14:37:54 https://review.opendev.org/#/c/742979/ <- Make airshipctl's site validation runnable on external site def'n [e.g. on treasuremap] 14:37:54 https://review.opendev.org/#/c/744523 - raises timeout on airshipctl 14:38:09 Yes let's get the timeout change merged today for sure 14:38:38 any other changesets anyone would like to call out here for additional review? 14:39:29 Or any additional roundtable topics? 14:39:50 Ok! In that case, I'll give you 20min back 14:39:56 thanks all! 14:39:59 Thanks everyone for your participation & discussion today 14:39:59 diwakar thyagaraj proposed airship/porthole master: Add Apparmor Feature testing to mysqlclient,openstack and Postgresql Utility Containers https://review.opendev.org/744534 14:40:04 #endmeeting