14:00:17 <mattmceuen> #startmeeting airship 14:00:18 <openstack> Meeting started Tue Aug 13 14:00:17 2019 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:21 <openstack> The meeting name has been set to 'airship' 14:00:23 <mattmceuen> #topic Rollcall 14:00:33 <mattmceuen> Hey everyone, Happy Tuesday 14:00:57 <mattmceuen> Here's the agenda for today - please add anything you'd like to discuss while folks trickle in: https://etherpad.openstack.org/p/airship-meeting-2019-08-13 14:00:57 <jamesgu_> o/ 14:01:01 <mattmceuen> o/ 14:01:03 <dwalt> o/ 14:01:07 <seaneagan> o/ 14:01:16 <nishantkr> o/ 14:01:22 <sthussey> here 14:02:00 <openstackgerrit> Sirajudeen proposed airship/airship-in-a-bottle master: [debug-report-fix] - set KUBECONFIG env https://review.opendev.org/676198 14:02:35 <souradage> o/ 14:02:59 <mattmceuen> Ok, let's get started 14:03:06 <mattmceuen> #topic Announcements 14:03:39 <mattmceuen> Just one reminder: core reviewers have 5 hours left to vote in the working committee election, please do your duty 14:04:25 <mattmceuen> any other announcements from others? 14:04:57 <mattmceuen> ok - moving on: 14:05:04 <mattmceuen> #topic Learnings/feedback on site-level overrides for Tunsten Fabric 14:05:30 <mattmceuen> obravo has been working on integrating TF as site-level overrides into the treasuremap repo, and has hit some struggles 14:06:05 <mattmceuen> I want to discuss/understand those, as we work through the Airship 2.0 yaml layering + rendering approach, to make sure we're solving for real world use cases 14:06:17 <mattmceuen> obravo - how's that work going? 14:07:44 <obravo> I faced some bugs in deployment , after i "replaced" my aiab-tf direcotry on latest aiab version 14:08:12 <obravo> It takes too much time to do what git normally shoud be doing 14:09:13 <mattmceuen> I believe this one's the current PS, right obravo: https://review.opendev.org/#/c/672688/ 14:09:51 <obravo> Looks like if you want to logically "fork" some deployer (to avoid user from editing configs) - you should not use separate dirctory , but all common files 14:10:30 <obravo> yes , suddenly i haven`t pushed new version for comparison 14:10:59 <mattmceuen> Is the main issue you hit duplication of manifests between aiab site and aiab-tf site? Or something else? 14:12:40 <obravo> Yes , fact that all changes in duplications in aiab deployer should be manually checked and applied to aiab-tf - is mostly painfull 14:12:51 <mattmceuen> ++ 14:13:24 <obravo> But we shoudn`t forget , that updates in global and type may broke your site-layer fork 14:14:07 <mattmceuen> Fully agree on duplication between the sites being a challenge. FYI, I've been using TF integration as one of our examples that must be solved for in our weekly SIG-YAML design calls :) 14:14:09 <obravo> For example - aiab chart is using type-layer version as parent 14:14:51 <mattmceuen> Updates to global and type shouldn't break the site after the site is merged (assuming we lint on the site, which we should) 14:15:08 <mattmceuen> Problem there is that your changes are in a patchset, so the linting isn't done yet 14:15:21 <obravo> If you change type-layer naming - you should change all implementations in any deploers using it , otherwise you broke them 14:15:23 <mattmceuen> a global change that breaks a site should not pass its gates 14:15:37 <mattmceuen> yep that's correct 14:16:23 <mattmceuen> We're working on some finer-grained layering in 2.0 that should help in the future, but that doesn't help you now 14:16:45 <mattmceuen> If you could push what you have to your patchset, I'd love to take a look and see if we can simplify anything 14:17:24 <mattmceuen> The challenge with keeping TF integration as a patchset is that it will drift from the main globals definition over time -- it's certainly an option though 14:17:39 <mattmceuen> but I'd call it Plan B 14:19:49 <mattmceuen> obravo, would you be able to add your latest & greatest to your PS? If so I'll add your PS to the "please review" list so we can see if we can help get you unstuck 14:20:05 <obravo> In 5 minutes 14:20:22 <mattmceuen> Perfect, thanks - no rush! I'll go ahead an add it :) 14:20:24 <obravo> it`s an in-work version 14:20:49 <mattmceuen> Understood 14:20:58 <mattmceuen> #topic Roundtable 14:21:19 <mattmceuen> Brief agenda today, so there's a wide open floor if anyone would like to bring up any other topics 14:21:34 <alexanderhughes> have we got an airship youtube account going yet? 14:21:48 <mattmceuen> I don't believe so! 14:21:54 <sthussey> Just an FYI, but the multinode framework in airship-in-a-bottle will soon support configurable VM disk layouts and network topologies 14:22:15 <alexanderhughes> one of the items that came up on TC meeting was consolidating airship videos in one location. a youtube account would be a great vessel for us to do so, we could set up playlists from various sources/topics and then drop the channel on the airship wiki 14:22:19 <sthussey> So folks that would like to put together a site definition for some known site configuration should be able to mock it up 14:22:27 <mattmceuen> sthussey: that's awesome 14:23:22 <mattmceuen> alexanderhughes: agree. the OSF owns the airship twitter account, I think they'd be the ideal folks to create a youtube account as well, so we can curate some playlists 14:23:39 <sthussey> @alexanderhughes as I'm no longer a core, I can give you reddit.com/r/airshipit 14:23:49 <mattmceuen> hogepodge FYI on youtube stuff^ 14:23:59 <sthussey> in case OpenStack ever decides to utilize that forum 14:25:14 <alexanderhughes> does matt have access to the reddit? 14:25:32 <sthussey> I don't believe so 14:25:38 <alexanderhughes> if he does he can socialize it out as needed 14:25:49 <mattmceuen> I didn't even know it existed :D that's a good one for us to have, thanks for staking the claim sthussey 14:25:58 <sthussey> Probably leads to a greater conversation about overall management of all public faces 14:26:03 <sthussey> quay.io, readthedocs.io 14:26:31 <sthussey> I have admin access to most of these and I don't really want them 14:26:58 <mattmceuen> Yeah, we should get those persisted and shared appropriately 14:27:16 <alexanderhughes> nominate mattmceuen as keeper of all those for now, and then over time as we start having interest in expanding our communications/marketing efforts into other platforms we can start using those 14:27:38 <sthussey> personally I think it should be formalized in governance 14:27:46 <mattmceuen> I'm happy to jot them down for now, with a goal of reducing the bus factor asap 14:28:22 <mattmceuen> I think this^ is a good thing for the working committee to solve/propose, once we have a working committee to solve/propose 14:29:13 <alexanderhughes> agreed. in the mean time I'd like to work towards getting an airship youtube channel set up, and start the effort of creating playlists linking to existing videos out in the wild. don't need to upload new copies, but we should be able to just link 14:29:32 <mattmceuen> yeah, agree 14:29:41 <openstackgerrit> Ian Pittwood proposed airship/spyglass master: [WIP] Addresses some of the TODO notes in engine https://review.opendev.org/673910 14:29:42 <mattmceuen> good add 14:29:54 <mattmceuen> Only other thing I had today was - please add these to your to-review list team: 14:29:55 <mattmceuen> https://review.opendev.org/#/c/675998/ 14:29:55 <mattmceuen> https://review.opendev.org/#/c/673914/ 14:29:55 <mattmceuen> https://review.opendev.org/#/c/672599/ 14:29:55 <mattmceuen> https://review.opendev.org/#/c/674963/ 14:29:55 <mattmceuen> https://review.opendev.org/#/c/668980 14:29:55 <mattmceuen> https://review.opendev.org/#/c/672688/ -- TF integration 14:31:37 <mattmceuen> any other topics for today? 14:32:19 <mattmceuen> Alright - thanks everyone, good meeting. have a great day! 14:32:23 <mattmceuen> #endmeeting