14:00:04 <b-str> #startmeeting Airship Community meeting 2018-08-07 14:00:04 <openstack> Meeting started Tue Aug 7 14:00:04 2018 UTC and is due to finish in 60 minutes. The chair is b-str. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 <openstack> The meeting name has been set to 'airship_community_meeting_2018_08_07' 14:00:17 <roman_g> o/ 14:00:20 <roman_g> Good morning 14:00:27 <b-str> #topic Attendance 14:00:32 <mattmceuen> o/ 14:00:41 <aaronsheffield> o/ 14:00:52 <seaneagan> o/ 14:00:54 <b-str> Please record your attendance on today's etherpad: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:00:59 <hemanth_n> o/ 14:01:54 <sofioni> Hi, can anyone share the meeting details please. 14:02:04 <roman_g> https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:03:27 <sofioni> Thanks 14:03:33 <sthussey> here 14:03:44 <b-str> #topic Old Business - timeout issue (Armada) - patchset has been merged, any futher discussion? Will continue in 60 seconds with no feedback. 14:05:08 <b-str> #topic Old Business - PTG Agenda https://etherpad.openstack.org/p/AirshipPTG4 - does not appear to be much here. Any thoughts/comments? Will continue in 60 seconds with no feedback. 14:06:28 <mattmceuen> What does Regiestered mean in the agenda? 14:06:29 <roman_g> I'm not coming. 14:06:36 <mattmceuen> Registered for the PTG attendance? 14:06:45 <b-str> Ok, - I have an item here - do we need to assign someone to drum up info? 14:06:58 <b-str> I don't see "registered" 14:07:04 <b-str> is it because I'm using meetbot topics? 14:07:08 <sthussey> It is in the AirshipPTG4 14:07:22 <mattmceuen> I think it means "registered to attend", but just double checking 14:07:23 <b-str> ah, I see 14:07:25 <sthussey> ... etherpad. I believe it means registered for the PTG 14:08:23 <b-str> Would anyone like to take an action item to drive forward in that etherpad? 14:08:32 <mattmceuen> I can take that 14:08:54 <b-str> #action mattmceuen will drive action on https://etherpad.openstack.org/p/AirshipPTG4 14:08:56 <mattmceuen> For all attending please be sure to add your name to the list and any topics you'd like to plan to address @ the PTG - I'll do the same 14:09:42 <mattmceuen> (offline, don't have to do it now) 14:10:03 <b-str> Any further discussion or thoughts on the PTG topic? 14:10:40 <sthussey> Is there any expectation or actions from the PTG for those not attending? 14:11:05 <mattmceuen> Only thing would be to add anything you'd like to be discussed in your absence to the agenda - that would be welcome 14:11:32 <sthussey> Okay. Well I don't have any topics to be discussed that I wouldn't want to be part of the discussion. 14:12:07 <portdirect> Normally people set up telepresence so that those not attending in person can participate 14:13:39 <sthussey> Okay. I see a topic of Design Meetings, so would be interested in telepresence 14:13:47 <b-str> looks like that made it to the etherpad. 14:14:21 <b-str> Maybe add the topics that telepresence would be desired for, so it can be arranged? 14:14:53 <portdirect> ++ 14:15:15 <mattmceuen> Yeah - as topics get populated in there, if you're not attending the PTG, please drop a note in the etherpad if it's something you'd like to participate in over telepresence 14:15:33 <b-str> #action add topics that are desired for telepresence to https://etherpad.openstack.org/p/AirshipPTG4 14:16:07 <b-str> #topic Current Items: Core reviewer list nominations 14:16:37 <b-str> Let's move on to the core reviewer nominations. Pleas add nominees to the etherpad at https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:16:59 <b-str> There is a sub-heading under `Current Items` 14:17:06 <mattmceuen> There's a set of practices around this already for OpenStack. I suggest we use those unless we find something that doesn't work 14:17:46 <mattmceuen> We're starting with a list of core reviewers already (inherited from the pre-existing dev team) 14:18:06 <b-str> Ok - there was a request from last week to experiment with something simple. We can defer the nominations to that process instead. 14:18:16 <mattmceuen> For new reviewers, they would be proposed on the ML (generally by the PTL, but I don't think that's always the case), and the team votes 14:18:36 <mattmceuen> Did I miss anything, folks familiar with the process? 14:19:12 <sthussey> How about pruning inactive cores? 14:19:16 <portdirect> That's how it's usually done 14:19:16 <mattmceuen> As openstack-helm PTL I've proposed exactly one core, so I'm not the most knowlegeable :) 14:19:30 <mattmceuen> Pruning inactive cores: I looked into this for a similar OSH situation 14:19:52 <mattmceuen> Step 1: Ping them and ask if they're ok with just bowing out -- i.e. whether they intend to keep on core reviewing in the future 14:19:59 <mattmceuen> Step 1 usually does it 14:20:28 <mattmceuen> There is a more heavyweight formal process to surgically remove a core, but it's a lot of work / suffering I believe 14:20:50 <mattmceuen> When people bow out as Core, they or the PTL can send out a note on the ML 14:21:14 <b-str> Ok -sounds like the mailing list is the avenue for most all of this. 14:21:42 <portdirect> Pinging in private is really the 1st step though 14:22:05 <b-str> makes sense 14:22:12 <portdirect> As it looks a bit heavy handed to call people out on the ml out of the blue without context 14:22:24 <mattmceuen> Reminder: the ML sign-up is here! http://lists.airshipit.org/cgi-bin/mailman/listinfo 14:22:38 <b-str> feel free to add that to the etherpad 14:22:44 <mattmceuen> will do 14:23:20 <b-str> Any further discussion here? 60 seconds. 14:24:27 <b-str> #topic Current Items: Meeting time reschedule 14:24:53 <roman_g> Do we keep old time or re-schedule it? 14:25:15 <b-str> Looks like we had a proposal for 13:30 UTC, but haven't moved it yet. I suspect that next week will also be on the old time as well. 14:25:30 <b-str> The plan was to use the mailing list to socialize the new time. 14:25:43 <mattmceuen> I think Mark didn't get to that before heading out on vacation :) 14:26:18 <mattmceuen> Were we all good with the 13:30 time, or were we going to give a few options for folks to vote on? I thought the latter but may have missed it 14:26:39 <b-str> I think this is true - he's scheduled to be back for the 8/21 meeting - Can this delay until then, or do we need an action on this right.now. 14:26:50 <sthussey> So 1330 UTC is 0830 CDT correct? 14:26:56 <b-str> yes 14:27:05 <sthussey> Just to be clear, that will be 0730 CST correct? 14:27:29 <mattmceuen> I'm personally ok punting a couple more weeks till Mark gets back 14:27:29 <b-str> right - UTC - 6 14:27:36 <mattmceuen> and keeping as-is till then 14:27:38 <portdirect> That's 6:30 in CA right? 14:27:54 <b-str> it would be 5:30 during standard time. 14:27:59 <sthussey> 0630 PDT, 0530 PST 14:28:00 <portdirect> May be a bit early for those guys... 14:28:08 <sthussey> So Nov - Mar, 0530 14:28:21 <b-str> indeed. Let's get this on the mailing list in a few weeks and get some good ideas there. 14:28:29 <b-str> For now, keep as-is 14:29:16 <sthussey> It seems like an async model using mail or a newsgroup may fit the global audience better 14:29:33 <mattmceuen> One thing I've learned the hard way: 14:29:44 <mattmceuen> Different people strongly prefer different communication media 14:29:58 <b-str> indeed. 14:30:01 <mattmceuen> I for one am terrible at email - PSA, if you want me to read an email you may need to tell me 14:30:13 <b-str> ^ this 14:30:22 <roman_g> in chat? 14:30:34 <mattmceuen> But some folks (e.g. some non-native-english speakers) really prefer the cadence of an email exchange 14:30:47 <mattmceuen> So it's nice having a little of each 14:31:02 <mattmceuen> roman_g yep 14:31:04 <b-str> Let's make a few notes about concerns and ideas on the etherpad please. 14:31:41 <b-str> #action update etherpad with ideas/concerns about new meeting time and communication models here: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:32:07 <b-str> I'd like to move on to new business - any last words? 60 seconds. 14:33:07 <b-str> #topic New Business: Gerrit Dashboard 14:33:58 <roman_g> if needed - just vote, if not - then not 14:34:13 <b-str> roman_g has added a link to an example dashboard used for other project areas. Let him know in the etherpad if you'd like to see the same for airship. There is a line item to vote this up, and you can leave comments there as well. 14:34:29 <roman_g> Thanks :) 14:35:13 <b-str> Personally, I think this is a nice-to-have thing, as it would be nice to have 14:36:09 <hemanth_n> +1 for dashboard 14:36:40 <b-str> Any thoughts or comments? Please put your +1's in the etherpad: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 Moving on in 60 seconds with no conversation. 14:37:04 <b-str> #action add votes for Gerrit dashboard to etherpad: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:38:00 <b-str> #topic New Business: Bi-weekly Airship sync with OSF 14:38:22 <b-str> I'm not aware of what this is exactly, brief description anyone? 14:38:25 <mattmceuen> Reminder (and/or news to you) that we will have a bi-weekly meeting around Airship in Zoom 14:38:42 <sthussey> What is Zoom? 14:38:53 <mattmceuen> The goal is to facilitate some open discussion around project governance and design for Airship 14:39:03 <mattmceuen> just a teleprecense web app, like bluejeans etc 14:39:05 <soumitrakhuntia> +1 for dashboard 14:39:20 <mattmceuen> so a phone meeting 14:39:23 <sthussey> Could you clarify 'design' there? 14:39:51 <roman_g> http://lists.airshipit.org/pipermail/airship-discuss/2018-August/000053.html - invitation to the meeting 14:40:07 <roman_g> http://lists.airshipit.org/pipermail/airship-discuss/2018-August/000054.html - notification e-mail' 14:40:23 <mattmceuen> Yep, to drive the design of Airship - opening up the kind of design call that Rodolfo would host with a private audience previously 14:40:40 <b-str> #action add links and details of Airship/OSF sync meeting to the etherpad at: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:40:50 <sthussey> Hmm, so it seems like this is settled business? 14:40:51 <mattmceuen> It's not fully formed yet, and the bi-weekly meeting is a step in that direction. Since it's the first one, I expect a little "figuring out how the meeting should function" to go on there 14:42:17 <b-str> so this is 2x a week? 14:42:18 <mattmceuen> sthussey, yeah, I just added this to the agenda to make sure it's communicated well, since folks (<- this guy) aren't always good at the mailing list ;-) 14:42:22 <mattmceuen> every other week 14:42:28 <mattmceuen> to begin with 14:42:28 <b-str> ok 14:42:47 <mattmceuen> that is all from me - thanks 14:42:47 <sthussey> ok 14:43:29 <b-str> Ok- any further discussion on this topic? I'll move on in 60 seconds with no discussion. 14:44:31 <b-str> #topic New Business: Methodology for running true gates 14:45:15 <sthussey> I put this topic in 14:45:19 <b-str> This topic is attempting to address the limitations/needs for "bigger" gate test environments. 14:45:39 <sthussey> currently the zuul gates do testing, but only at the unit and possibly single-project functional level 14:45:57 <sthussey> there is no integrated platform testing done, which is needed 14:46:35 <sthussey> so this is just bringing in the community on something that needs to be done. if there is no community interest in this integrated testing, it can be handled purely 3rd party 14:46:51 <mattmceuen> One suggestion - I put together this repo that integrates Shipyard + Armada + Deckhand + Pegleg for a dev / learning env: https://github.com/mattmceuen/airskiff 14:47:18 <mattmceuen> It's not a full integration but a partial one, and ought to run in openstack infra adequately if we're gentle with it 14:47:41 <sthussey> Okay, that is fine though I don't feel adequate as it isn't running on a cluster deployed with Promenade 14:47:43 <mattmceuen> One of our new college hires at my company has been playing with it and volunteered to try to turn it into a gate yesterday, so I've been chewing on it 14:47:47 <mattmceuen> 100% agree 14:48:18 <mattmceuen> it's in the spirit of "something is better than nothing" and "more is better" :) 14:48:21 <b-str> Ok, mattmceuen, in passing you pondered aloud "how does ironic do their stuff" 14:48:39 <mattmceuen> there are many ponderables 14:49:05 <mattmceuen> I don't know the answer to that one yet, anybody have experience w/ Ironic gating? 14:49:10 <b-str> I think the point I was trying to make is: Is there a model we can leverage? 14:50:11 <mattmceuen> portdirect have you seen the ironic gating strategy perchance? 14:51:23 <mattmceuen> sthussey, other thoughts on airship gating in openstack infra 14:51:24 <mattmceuen> ? 14:51:38 <b-str> #action determine if there is a model existing in the OpenStack infra space that would allow for e2e gating of airship as a platform 14:52:09 <sthussey> I'm not particularly interested in rewriting a rational gate system to adapt to the limitations of openstack 14:52:24 <b-str> #action detemine if 3rd party gating is sustainable and maintainable 14:52:35 <sthussey> but will hold any judgments until details of alternatives are available 14:53:06 <b-str> #action document alternatives/ideas/strategies on the etherpad at: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 14:53:47 <b-str> Ok, any last thoughts before we move on and leave that for "current business" next week? I'll move in 60 seconds. 14:54:59 <b-str> #topic Info and Action items. 14:55:28 <b-str> I've moved the last two items under new business to a new header in the etherpad. DId not look like discussion items so much as "good info" and "things to do" 14:55:56 <sthussey> mattmceuen can correct me, but I believe the documentation topic might be up for discussion 14:56:07 <mattmceuen> yes, but 14:56:14 <mattmceuen> with 4 mins left maybe good for next time? 14:56:24 <mattmceuen> thanks sthussey 14:56:29 <b-str> Sounds like a plan. 14:56:39 <b-str> #topic open forum for next weeks topics 14:57:42 <b-str> Please add any items for next week's discussion to the etherpad at: https://etherpad.openstack.org/p/airship-meeting-2018-08-14 (this is next week's agenda) 14:58:06 <b-str> #topic Thank You for all that you do to make Airship a thing :) 14:58:42 <b-str> #endmeeting