16:01:11 <mattmceuen> #startmeeting airship
16:01:12 <openstack> Meeting started Tue Apr  2 16:01:11 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:15 <openstack> The meeting name has been set to 'airship'
16:01:17 <mattmceuen> #topic Rollcall
16:01:31 <dwalt> o/
16:01:34 <seaneagan> o/
16:01:42 <mattmceuen> GM/GE everyone!  let's give it a few minutes for folks to join.  Please add anything you'd like to discuss to the etherpad agenda:
16:01:52 <mattmceuen> https://etherpad.openstack.org/p/airship-meeting-2019-04-02
16:02:02 <michael-beaver> o/ GM
16:03:09 <Nishant_> o/
16:05:01 <mattmceuen> Ok, let's get started
16:05:03 <levmorgan> o/
16:05:04 <mattmceuen> #topic Season of Docs
16:05:46 <mattmceuen> Last week we'd brought up that Google is running a Season of Docs program, which pairs open source orgs who need documentation help with technical writers in a quasi-internship capacity
16:06:16 <mattmceuen> I'd like for Airship to apply for this program, and to do so we need some compelling examples of projects that writers could work on
16:07:06 <mattmceuen> Now that we've had a week for the idea to soak, let's brainstorm a bit -- things that would add real value for Airship in the Fall timeframe, and which would be really interesting for a tech writer
16:07:30 <mattmceuen> I put a few ideas in the etherpad https://etherpad.openstack.org/p/airship-meeting-2019-04-02
16:07:51 <shauno_> I would suggest starting with a clear reference architecture.
16:07:59 <mattmceuen> +1
16:09:09 <mattmceuen> We have some good diagrams already, but Airship has been a moving target and I think there's an opportunity to true those up, expand them, and then (most importantly) tell a story around them of what makes airship tick
16:09:24 <shauno_> +1
16:09:50 <shauno_> Anything that make getting a clear understanding and baseline would help people get started
16:10:55 <mattmceuen> Another thought I'd had is a real Contributor Guide.  I was looking into Go's contributor guide this weekend, and it really outlines a lot of steps to help people get started and contribute.  We're working on enhancing Dev Docs today, but it'll take additional technical writing focus to get to that level of getting folks started on the right foot
16:12:19 <mattmceuen> Another thing that just popped in my mind is "how does one add a new workload onto Airship" -- we really have no documentation in this area.  Fits into a larger need of "how do I author site manifests for Airship"
16:12:41 <mattmceuen> We have some site authoring guidage today, but there's a lot more that can be documented
16:13:09 <shauno_> Are you talking about additional non-OpenStack workloads? i.e. K8's native?
16:13:34 <sthussey> That should be the case as Airship only supports Kubernetes native workloads
16:14:07 <mattmceuen> Yep, if someone wanted to run a workload other than openstack itself.   For example, the team had to go through this to get jenkins running on Airship - there's tribal knowledge on how to do this but we need written knowledge
16:14:19 <mattmceuen> It's not rocket science, just needs some description
16:14:26 <sthussey> I mean, there are lots of examples
16:14:44 <sthussey> Unless you mean 'charts that don't use helm-toolkit' as LMA isn't Openstack
16:15:18 <sthussey> So maybe the use case should specifically be for deploying charts from https://github.com/helm/charts
16:15:41 <mattmceuen> What I'm thinking is, outlining the steps involved in adding a new chart.  What do I need to add, what do I need to edit
16:15:54 <mattmceuen> I like that sthussey
16:16:54 <mattmceuen> Any other ideas you guys have for what would benefit the most from pen-to-paper?
16:17:47 <shauno_> Within the contributor guide, a blueprint mechanism could be helpful (I am assuming there isn't one)
16:18:29 <mattmceuen> Agree.  Outlining Airship's approach to Stories + Specs + Code Changes
16:18:42 <shauno_> +1
16:19:25 <mattmceuen> we still have plenty of time before the submission deadline, so keep noodling; I won't have time this week to start on the application anyway :)
16:19:36 <mattmceuen> anything else on this before we move on?
16:19:56 <mattmceuen> #topic  How do manage Roadmaps for Airship
16:20:19 <mattmceuen> I guess we need to iron this out before we document it, huh jezogwza :D
16:20:27 <mattmceuen> The floor is yours
16:21:04 * mattmceuen copying from etherpad:
16:21:07 <mattmceuen> - How does Roadmap items / features relate to storyboard or patchsets or labels
16:21:07 <mattmceuen> - How do roadmap features relate to treasuremap Monthly Tags
16:22:29 <mattmceuen> I think jezogwza may have stepped away, let's come back to that topic
16:22:35 <mattmceuen> #topic Armada v2 schema and upcoming changes to `wait`
16:23:05 <mattmceuen> seaneagan is working on some updates to Armada and I wanted to make sure we all understood the direction and saw them coming
16:23:32 <seaneagan> thanks Matt
16:23:53 <seaneagan> Coming Soon: Armada v2 docs
16:24:04 <seaneagan> We need to make some breaking changes to Armada documents to:
16:24:11 <seaneagan> 1) remove unuseful APIs
16:24:18 <seaneagan> 2) tweak some APIs to make them more useful
16:24:29 <seaneagan> To address this, rather than breaking v1 docs, we are implementing v2 doc schemas:
16:24:38 <seaneagan> armada/Manifest/v2, armada/ChartGroup/v2, armada/Chart/v2
16:24:53 <seaneagan> WIP: https://review.openstack.org/#/c/648246/
16:25:03 <seaneagan> v2 docs are not ready to be used just yet
16:25:11 <seaneagan> there are a few more breaking changes to be discussed/implemented
16:25:26 <seaneagan> once v2 docs are finalized, v1 docs will be deprecated, and will not receive feature updates
16:25:45 <seaneagan> after a TBD migration period support for v1 docs would be removed
16:25:53 <seaneagan> there will be a migration guide provided for moving from v1-v2
16:26:01 <seaneagan> we will make another announcement once v2 docs are ready for consumption
16:26:15 <seaneagan> One of the biggest drivers for implementing this now is that we need to make some potentially breaking changes to the default wait configuration to make it more useful:
16:26:22 <seaneagan> https://review.openstack.org/#/c/636440/
16:26:36 <seaneagan> More information will be provided on this change along with the v2 docs announcement
16:26:54 <seaneagan> That's all i have, thanks
16:27:16 <mattmceuen> I kept typing questions and you keep answering them before I hit enter seaneagan - that's awesome info
16:27:43 <mattmceuen> appreciate the care for the deprecation cycle and migration guide
16:27:53 <mattmceuen> any other questions for sean on this?
16:28:40 <mattmceuen> Hey jezogwza, are you back?
16:29:40 <mattmceuen> ok - let's punt to next week topic:  How do manage Roadmaps for Airship
16:29:46 <mattmceuen> #topic Roundtable
16:30:27 <mattmceuen> Anything else on y'alls minds today team
16:31:00 <mattmceuen> in that case - we will adjourn!
16:31:08 <mattmceuen> Thanks everybody and have a great week
16:31:11 <roman_g> reviwes!
16:31:15 <mattmceuen> OOOO
16:31:15 <shauno_> Thanks
16:31:26 <roman_g> =)
16:31:36 <mattmceuen> anything in particular roman_g or just call-to-action for reviews in general :)  I missed the standing item
16:31:47 <roman_g> https://review.openstack.org/#/c/645041/ Minor: Git URI schema and URL change - openstack/airship-divingbell
16:31:50 <roman_g> https://review.openstack.org/#/c/635507/ Add cache for results of requests to quay.io in Updater tool - openstack/airship-treasuremap
16:32:01 <roman_g> That's it.
16:32:03 <roman_g> Thank you
16:32:08 <mattmceuen> thanks for getting those on there
16:32:20 <openstackgerrit> Merged openstack/airship-armada master: Use python3 when creating the docker image tags  https://review.openstack.org/643605
16:32:22 <mattmceuen> any other review requests?
16:32:44 <roman_g> The last one is super old.
16:32:53 <roman_g> No other changes for review.
16:33:07 <mattmceuen> alright - for real this time, meeting ajourned (although feel free to always ping for reviews in here when needed as well)
16:33:11 <mattmceuen> #endmeeting