14:00:08 #startmeeting Airship 14:00:09 Meeting started Tue Feb 19 14:00:08 2019 UTC and is due to finish in 60 minutes. The chair is dwalt. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:10 #topic rollcall 14:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 The meeting name has been set to 'airship' 14:00:21 Hey everyone! I am hosting today's meeting since mattmceuen has a conflict. 14:00:33 Here is today's agenda: https://etherpad.openstack.org/p/airship-meeting-2019-02-19 14:00:35 Good Morning everyone ! 14:00:53 Please add any topics you would like to discuss as everyone joins. We'll get started in a few minutes. 14:01:56 o/ 14:02:18 hi 14:02:28 hi 14:02:37 o/ 14:03:00 o/ 14:03:40 It looks like the dust has settled on the etherpad, let's get started 14:03:44 #topic New Airskiff storyboard items 14:04:06 Some new items have recently been added to the Treasuremap storyboard 14:04:12 #link https://storyboard.openstack.org/#!/project/openstack/airship-treasuremap 14:04:36 Several are geared towards Airskiff 14:05:10 One of the things I have been doing is marking those that seem like good "starting" issues with the label "low-hanging fruit" 14:06:16 Of course, anyone can work on them! But these items are a more easily digestible in size 14:06:43 roman_g: I see you added some items here. Would you like to discuss those? 14:08:40 I think Roman may still be AFK. Anyway, we'd like to open storyboard up a bit more to anyone else who has items they would like to add 14:09:25 Airskiff seemed like a natural starting place for this, since several new contributors are using this to ramp-up on the project 14:09:52 So please feel free to do so or claim any of the new items! 14:10:25 sure dwalt ! That sounds good. 14:10:57 Anything else on the new storyboard items or storyboard in general? 14:11:47 * roman_g is back 14:12:00 Any way to select and see tags easily in th storyboard? 14:12:04 hey roman_g! 14:12:17 "low-hanging fruit"'s 14:12:52 Let me know if you find a way. 14:13:02 I think you have to either click on a storyboard item to view tags or filter by them 14:13:12 Does anyone know of a better way? 14:13:46 All right. Will ask you for a screenshot. 14:13:56 Next topic. 14:14:22 Sure, I will update later with a query to use 14:14:24 #topic New meeting hours 14:14:56 So this idea was bounced around last week. mattmceuen proposed a new meeting time of two hours later 14:15:26 We've been keeping a vote on this on the meeting agenda. Is anyone opposed? 14:15:38 Submit a patch to the repo with new proposed meeting time, and add +1/-1 there. 14:15:39 Or have any other suggestions for a new meeting time 14:15:56 roman_g: that's a great idea. What is the proper repo to do that? 14:16:02 We have folks from Korea, which would be against the change. 14:16:37 That's a good point, I don't think they are represented here today 14:16:43 dwalt: openstack-infra/irc-meetings 14:17:10 #action propose new meeting time to openstack-infra/irc-meetings 14:17:14 thanks roman_g 14:17:26 SK-Telekom 14:17:41 Does anyone have any suggestions for a more inclusive time? 14:18:05 No way. It's already early for US-based team. 14:18:18 Like 6-7 or 8am 14:18:49 agreed. It seems to be easier in the summer when much of the U.S. is on Daylight savings time 14:19:10 Other countries also have DST 14:19:21 I like this tool for comparing times. 14:20:00 No time will be perfect, which is why I think it's important to push important decisions to places like the mailing list, which knows no time zones. 14:20:02 https://www.worldtimebuddy.com 14:20:40 That's helpful, thanks hogepodge 14:21:28 I believe we have hosted votes over the mailing list before to promote core reviewers. I'll sync-up with mattmceuen about using the mailing list thread for this proposal 14:21:40 #action propose new meeting time in airship-discuss mailing list 14:21:53 thanks roman_g. Any other thoughts before we move on? 14:22:14 #topic ReadTheDocs 14:22:29 roman_g: I believe this is yours! 14:22:38 Yes. Should now be fixed. 14:23:05 There was a pull request to the RTD folks, which has been merged a few hours ago. 14:23:17 * b-str So something changed in RTD? 14:23:35 Waiting for Zuul to run this job again to see the results: http://zuul.openstack.org/builds?job_name=trigger-readthedocs-webhook 14:23:46 * sthussey You don't need to emote your questions. 14:24:11 b-str: RTD started to require CSRF token in December, all RTD jobst started to fail that time. 14:24:11 Sorry, bad control-enter behavior due to another chat application 14:24:27 Ok, thanks! 14:24:33 Glad to hear that, thanks for the update, roman_g 14:24:49 =) 14:25:02 I suppose this means we will need to manually re-trigger all documentation jobs once we confirm it works? 14:25:20 No. I have re-triggered all docs an hour ago. 14:25:41 Fantastic! 14:25:49 Found 1 new failing docs build 14:25:55 I think that is a strange explanation for why Deckhand's docs were failing on a dependency, but if it works, I'll take it. 14:26:02 Divingbell is failing 14:26:25 Deckhand is failing since October, patch is pending review 14:26:41 Do you have a link to that patch, roman_g? 14:26:49 oh, this is separate from the Deckhand issue. got it. 14:26:54 https://review.openstack.org/635357 - openstack/airship-deckhand - Embed UML generated diagrams into docs, fix docs build 14:27:17 Rumour has it that RTD now supports UML 14:27:23 I did not submit a patch for the Divingbell yet. https://storyboard.openstack.org/#!/story/2005046 Divingbell docs builds failure 14:27:28 So we should look at refactoring the build to utilize that 14:27:45 sthussey: yes, it is. integrated into my patch here https://review.openstack.org/635357 - openstack/airship-deckhand - Embed UML generated diagrams into docs, fix docs build 14:28:11 Ah, nice 14:28:45 That's great roman_g, thanks for taking the initiative on that 14:29:19 If anyone has the capacity, there is a storyboard item to fix the Divingbell documentation 14:29:21 #link https://storyboard.openstack.org/#!/story/2005046 14:29:51 Any other additional comments on this topic? 14:30:12 no 14:30:32 Cool. Moving on! 14:30:35 #topic Stories published on storyboard for Airship-* projects 14:30:45 Full list has been sent to Matt by roman_g 14:30:53 What do we do with those stories? 14:31:17 roman_g: is this list of stories on the ML or elsewhere? 14:31:23 Really, we need to find a way to work on them and close. 14:31:30 In corporate mail. 14:31:46 It's a copy-paste of all stories we have in storyboard. 14:32:08 I know some of these items have not been visited in a long time, so some may now be invalid 14:32:37 I imagine especially so in AIAB 14:32:49 Would we may be distribute them between us and work on them? Ask if help is still needed, or may be submit a patch or give a recommendation? 14:33:51 I think that's a good first step; comment on the items and see if they're still valid 14:34:15 Maybe once we do that, we could work to develop a proper labeling system? 14:34:36 I am not too familiar with how other OpenStack projects are using storyboard today 14:35:35 #action roman_g to ask if issue is still valid in Storyboard, make an announcement in mailing list 14:36:01 I am also happy to help with that effort, roman_g 14:36:02 How long to wait until people reply? 14:36:18 Say, wait for 2 weeks and close as "invalid"? 14:36:31 That's a good question. Two weeks seems reasonable to me 14:36:48 sthussey, b-str - what you think? 14:37:04 hogepodge 14:37:36 Probably should live in the governance work 14:38:25 Agree. Would be good to have it defined there. 14:38:28 I doubt this is the correct forum at this point until we outline the governance model 14:38:42 other communities mark as stale as long as 30-90 days, but it largely depends on the size and activity of your community. 14:39:12 I think there is some question too about if the items in storyboard are "tasks" or "roadmap" (probably both), they probably have different lifecycles. 14:39:15 If you start with two you can adjust from there. I don't have any strong thoughts on it right now 14:39:33 Then I will just re-visit all stories and ask if it's still valid. 14:39:42 there are mostly bugs. 14:39:54 not roadmaps and tasks 14:40:04 that's a good point, b-str. A lot of these are questions on errors I assume have been fixed by now 14:40:26 Right - bugs, support requests, enhancement requests, outlines of features, etc... it's a lot of things. 14:40:40 Maybe we can avoid closing them for now and just check up on their status 14:41:02 the point is well taken though, needs some TLC. 14:41:07 Sure. Will not close, just will ask if it's still valid. 14:42:22 Sounds like a plan! Any other thoughts on this one before roundtable? 14:43:05 #topic roundtable 14:43:53 Any other items/thoughts that didn't make it into the meeting agenda? 14:44:11 I didn't have the link to the agenda, but for next meeting I'd like folks to consider what onboarding environment seems the most valuable 14:44:23 https://etherpad.openstack.org/p/airship-meeting-2019-02-19 14:44:26 Currently there is too much maintenance overhead 14:45:06 So IMO we need to cut down the number of 'out of the box' things Airship proves 14:45:29 sthussey: like what, from we have today? 14:45:32 Airskiff, Airship-in-a-bottle local VM, Airship-in-a-bottle multi-VM, treasuremap 14:45:48 I don't see enough value maintaining all of them 14:46:49 So a thing to consider and discuss next meeting 14:46:57 I agree. 14:47:32 That's a good thought, sthussey. I know there have been some grumblings of consolidating more of these items in treasuremap 14:47:57 I will make sure this gets added to the agenda for the next meeting. Thanks for bringing this up 14:48:51 #action add item to next meeting agenda to discuss onboarding environments 14:49:43 I realize now I skipped over the requests for review :p. I'll post those in a second, sorry folks 14:49:53 anything else beforehand? 14:50:25 No. 14:50:30 #topic Requests for review 14:50:37 I've added item to the next meeting agenda 14:50:45 Some patches from roman_g 14:50:50 https://review.openstack.org/635357 - openstack/airship-deckhand - Embed UML generated diagrams into docs, fix docs build 14:50:50 https://review.openstack.org/635507 - openstack/airship-treasuremap - Add cache for results of requests to quay.io in Updater tool (gate fails, but issue is not related to the patch) 14:50:50 https://review.openstack.org/636324 - openstack/airship-in-a-bottle - Fix: docs formatting 14:50:50 https://review.openstack.org/632457 - openstack/airship-in-a-bottle - Fix: publish MAAS dashboard 14:51:07 Any extra eyes on these would be much appreciated! 14:51:42 https://review.openstack.org/#/c/635357/ - Zuul -2 on gates. Will look at it. 14:52:21 roman_g: ah, perhaps another dependency issue 14:52:35 That's it for the agenda, everyone. Any other parting thoughts? 14:53:27 Any specs in process? 14:53:47 Thanks for running the meeting today @dwalt 14:53:54 I believe we still have the ansible and ironic ones roman_g 14:54:03 my pleasure b-str! 14:54:15 Torpedo is pending 14:54:29 https://review.openstack.org/#/q/projects:openstack/airship-specs+status:open 14:54:39 I have a spec for Divingbell Ansible Framework- https://review.openstack.org/#/c/628221/ 14:54:49 The spec for minimirror - is it implemented and can be moved to Implemented? 14:54:56 Would like to see some more feeedback. Thanks. 14:55:09 Sure thing, nishant_ 14:55:28 Likely should be removed 14:55:36 As minimirror is not an Airship solution 14:55:52 roman_g: agree with sthussey. It was realized as a part of OpenStack-Helm-addons 14:56:16 I can take care of updating that 14:56:20 OK. 14:56:25 #action resolve mini-mirror spec 14:57:32 I think that's it. Thanks for coming, everyone. Have a great day! 14:57:41 #endmeeting