15:00:24 #startmeeting airship 15:00:25 Meeting started Tue Jan 14 15:00:24 2020 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:29 The meeting name has been set to 'airship' 15:00:35 #topic Rollcall 15:00:36 o/ 15:00:39 o/ 15:00:46 good morning/everyone! 15:00:59 https://etherpad.openstack.org/p/airship-meeting-2020-01-14 15:01:05 o/ 15:01:06 o/ 15:01:09 please add anything to the agenda you'd like to discuss 15:01:16 we'll wait a min 15:01:47 Merged airship/election master: Add Roman Gorshunov as a Technical Committee candidate https://review.opendev.org/702059 15:02:38 o/ 15:02:47 o/ 15:02:51 o/ 15:05:58 #topic Jira to GitHub Issues migration 15:06:04 Ok first up! 15:06:17 Should have started with - Happy New Year (since I missed last week :) 15:07:03 We've discussed/publicized the idea to migrate from Jira to GitHub Issues for story and issue tracking for a while now, and there's been only positive reception 15:07:31 So to begin talking about "how" we will GH Issues, we will discuss in tomorrow's Flight Plan meeting 15:07:56 Please join if you'd like to be part of that discussion -- invite details can be found here: 15:07:57 https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Management_Meetings 15:08:09 that's all on that topic 15:08:20 #topic Procuring docs.airshipit.org 15:09:09 Now that Airship is a full-fledged OpenStack Foundation project, we have available to us the ability to leverage OpenStack Infra for our rendered documentation site 15:09:26 \o/ 15:09:38 And icing on the cake is that it gets a nice vanity URL, docs.airshipit.org 15:10:08 There are just a couple steps that need to be coordinated with the OpenStack Infra sysadmins (outlined in the etherpad) 15:10:37 I'm looking for a volunteer to coordinate those steps (not a lot of work on the individual themself) 15:11:13 which docs would be there? 15:11:37 I think this will set us up really nicely for 1) A great home Airship 2.0 doc, 2) easy-to-find developer docs that describe the new GitHub Issues process 15:12:06 roman_g - I think all airship airship docs could be available through there 15:12:18 i.e., I think we could migrate from readthedocs 15:12:29 ++ 15:12:32 and preserve a consistent look-n-feel with airship / openstack themeage 15:12:44 good time for project leads to double check their documentation too - specifically to ensure there were no readthedocs hardcoded links 15:13:03 good catch alexanderhughes 15:13:09 It would be great if someone with technical writing exp could help here 15:13:14 Should docs be written&migrated only for Airship 2.x, or also for Airship 1.x? 15:13:29 Is Lindsey on irc? 15:13:30 I see no reason not to do both 15:13:46 portdirect: no 15:14:34 Would anyone like to volunteer to take lead on this effort? 15:15:28 mattmceuen: I need to digest and understand, then I could take it 15:16:03 sure thing, thanks for considering it roman_g! Take a look at the agenda and let me know your thoughts 15:16:41 Ashlee from the OSF helped get us that info and can answer any questions, but the main thing is just to reach out to the infra team over irc or email 15:16:49 they've been incredibly helpful in my experience 15:17:22 ok - if nothing else for this one, we can move on: 15:17:47 #topic 3rd Party Gates for virtual full-stack testing 15:18:24 I'll preface this with, as you probably have heard, our dear colleague kskels has moved on to some different work 15:18:39 * roman_g haven't 15:18:52 * mattmceuen cries a little 15:19:11 One of the things he was focusing on was third-party full-stack testing for Airship patchsets 15:19:34 So I wanted to bring that up and get the rest of us on the same page 15:20:04 There was/is one third-party gate (on Treasuremap) for Airship-in-a-Bottle 15:20:18 (single node full stack testing) 15:20:44 Was he not also the force behind treasuremap tagging? 15:20:54 But I heard (haven't confirmed) that that may be turned off -- does anyone have any insight? 15:21:08 portdirect: yes, he is/was 15:21:17 Yes - Arijit has taken formal lead on that one portdirect 15:21:19 mattmceuen: it still runs, require AF VPN to see logs 15:21:24 ahhh 15:21:31 *requires 15:21:43 Does it post results to gerrit? 15:21:49 portdirect: yes 15:21:55 Fantastic :) 15:22:00 https://review.opendev.org/#/c/701023/ - here, for example 15:22:06 but only SUCCESS/FAILURE 15:22:10 something like that. 15:22:13 ABORTED 15:22:36 Which check is it? 15:22:41 and it's not really voting 15:22:50 it's in comments 15:22:57 Toggle Extra CI 15:23:19 Ah, it's just posting comments - so not gating atm? 15:23:42 yes 15:23:57 Still its fantastic to see 15:24:02 I am happy to have incorrect info on it not being run then, roman_g. That's great. 15:24:16 Is there documentation on the runner (jenkins?) Etc 15:25:02 jenkins/gerrit integration, you mean? standard, as usual 15:25:17 runs on AF resources 15:25:20 I mean where the Jenkins is/jobs for it etc 15:25:20 Deepak proposed airship/airshipctl master: AIR-61 - Adding gate test in zuul for vbmc https://review.opendev.org/690870 15:25:32 portdirect: no, nothing like that 15:26:01 Ok, other than kaspars who knows the setup there, and has access to it? 15:26:22 jenkins job is in att-comdev/cicd, if I'm not mistaken 15:26:42 I have VPN access, could have bare-metal access 15:26:57 You have ssh keys for those servers? 15:26:58 need to re-check if I still able to logon 15:27:11 portdirect: I think so. I should have it. 15:27:24 If we could validate that it would be great 15:27:34 portdirect: I would. 15:27:36 So someone can take over admin of it 15:27:57 worst case we can reset credentials 15:28:06 Arijit and I believe Alex Noskov have admin capabilities (I don't think they're here though) 15:28:16 I think credentials are all fine 15:28:52 I recall now that we were interested in getting the logs publically available, what's the next step for that roman_g? 15:29:05 (sorry to put you on the spot, you just know a lot in this area) 15:29:42 mattmceuen: we have had tls certs expired, and couldn't got them renewed for some reason (I don't remember) 15:30:13 the certs for the lab? I know Arijit is working on that today 15:30:24 and Artifactory license has also expired 15:30:28 sigh 15:31:04 if we would have this problems solved, then we could enable logs publishing again 15:31:58 ok. Let's take that as a follow-up item and move on for now... this is quite important but there are also some other things in the agenda 15:32:01 revisit next week 15:32:29 and hopefully get the lab re-certed in the meantime 15:32:38 ok 15:33:03 #topic Need help with https://review.opendev.org/#/c/694776/ - some python skills are needed 15:33:13 That's mine. 15:33:30 As you all have seen, roman_g is very proactive and takes lead to drive needful things forward 15:33:40 So let's please be eager to help him when he asks :) 15:33:42 Would appreciate someone to help me out with some python coding 15:34:13 mattmceuen: well... that has been asked in November 15:34:33 in that case... let's be eager to help him two months after he asks 15:34:33 roman_g: can you provide some context for people as to what's being done here 15:34:46 As that may help you get some volunteers 15:34:52 portdirect: sure 15:35:48 I'm changeing verification tool used by OpenDev infra to validate yaml format of document which specifies repositories and their settings 15:36:34 specifically adding a parameter which would set Gitea git web-gui to point Issues link to arbitrary URL 15:36:53 in our case that initially was Jira, and now - GitHub issues 15:37:41 so it would let us tie commits to github issues? 15:38:04 I'm being asked to define extensible format for the URL, and I'm unsure how to make it. May be a call with screensharing would help me to get better understanding on how to code what has been asked. 15:38:45 portdirect: not really. only to set up our issues link on e.g. opendev.org/airship/treasuremap to point to github issues 15:39:31 I know we have some strong python developers here, could anyone hop on a bridge w/ Roman to get him pointed in the right direction? 15:40:47 there are another 1 or 2 related patch sets from me on that point, but they are not important at the moment and I think I would be able to get them merged by myself once this one in the subject is merged 15:41:56 next topic? 15:43:20 next question was mine, does anyone know whether we have anything similar to airskiff for airship2.0 15:43:25 Let's move on for now and revisit roman_g 15:43:34 #topic airskiff for airship2.0 15:44:17 thanks mattmceuen for setting topic 15:44:17 mattmceuen: no, not at the moment 15:44:38 nothing what could be easily tried out 15:44:54 madhumati: not yet, but in the design call (right before this IRC meeting) we were discussing continuing to build the ansible playbooks that'll facilitate both zuul-based execution and dev on-demand execution 15:45:12 not exactly the same thing but we're moving toward it 15:45:45 to expand on this a little 15:46:06 with airship 2.0 the control plane is much lighter weight 15:46:09 mattmceuen thats great. what could be the availability date of such environment 15:46:23 and so the need for a 'lightweight airship' should be much less 15:46:35 portdirect you mean we no need to worry about hardware 15:46:36 ++ 15:46:57 "soon" madhumati, it's being very actively worked (since it's critical to CICD for airship2) 15:47:25 madhumati: i would hope so, i epxect the k8s provisioning side of things to consume FAR less resources than in airship1 15:47:28 cool then ... Thanks portdirect mattmceuen and roman_g 15:47:48 you bet! 15:47:49 madhumati: good news are that airship 1.x is in production, you can use it right now. Another good news is that at the moment it's rather easy to contribute to feature development for the airship 2.x. 15:48:12 ++ 15:48:35 Ok, moving on to next topic: 15:48:45 #topic Extension of nominations for WC special election? 15:48:45 yeah i have installed it on my local machine roman_g but i could see openstack version is bold its havana 15:49:01 oops sorry, I jumped the gun madhumati 15:49:13 madhumati: im not sure about that - we never did any havana development ? 15:49:17 :D mattmceuen no problem 15:49:34 the very earliest deployment airship supported for osh was ocata 15:50:22 hmm no worries will check the latest build if we are modifying the build for airskiff portdirect 15:50:44 Thanks mattmceuen you can jump to next topic :) 15:51:13 if you guys got havana to run through OSH that would be fun to know madhumati :) let us know what you find! 15:51:35 :) surely will post it mattmceuen 15:51:49 ok alexanderhughes: like you said, nominations have closed for the empty TC and WC seats 15:51:58 we have a couple of nominations for the TC, but zero for the WC! 15:52:22 For the question of what do we do with the empty WC seat, I plan to bring it up with the WC. My personal feeling is, 15:52:37 Just leave it at 4 for the duration of the term 15:53:15 If anyone wanted to nominate but missed the notification or the deadline, though, we could take that into account :) if so please let me know 15:53:46 any other thoughts/discussion on this one? 15:54:19 my opinion is leave this open for anyone that missed notification til next WC meeting, then decide amongst the WC what to do - I second the suggestion to just ride out the term with 4 seats 15:54:29 mattmceuen: we have 2x AT&T and 2x of whom in WC? 15:55:10 Ericsson + Mirantis 15:55:12 assuming no one missed notification and has cause for a late nomination, no need to extend an election indefinitely if no one is running for it 15:55:13 found it 15:55:13 Only 2x WC seats filled by AT&T -- anyone from any other employer could have nominated 15:55:29 agree alexanderhughes 15:55:43 ok, moving on to last topic! 15:55:48 #topic Meeting dates/times 15:56:02 Just gonna copy and paste ya, alexanderhughes :) 15:56:06 Meeting dates/times have been updated on the wikis recently to ensure the CST / UTC times listed are accurate. Perhaps a good time to send out a wave of fresh calendar invites to mailing lists to ensure everyone has accurate invites (and for new community members to add to their calendars) 15:56:06 Should this review activity take place twice a year during daylight savings, and on an as-needed basis as calls change? 15:56:11 yeah I was pretty verbose on agenda :) 15:57:00 Good thought, let me reach out to Claire & Ashlee to see if they wouldn't mind doing that 15:57:25 so quick rationale for this item - Jan-Erik noticed some items had the wrong time listed in UTC as a result of DST changing and wiki not getting updated. I just want to make sure we're making it easy for community to stay engaged regardless of what timezone they live in 15:57:54 yeah, a very easy (and important) thing to lose track of 15:58:08 #topic Roundtable 15:58:19 Any other items team, we have just a couple mins left? 15:59:18 alright, thanks everyone for the discussion and for your time! 15:59:24 have a great week 15:59:26 #endmeeting