16:00:35 <eglute> #startmeeting interopwg
16:00:36 <openstack> Meeting started Wed Sep  6 16:00:35 2017 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:40 <openstack> The meeting name has been set to 'interopwg'
16:00:41 <markvoelker> o/
16:00:57 <eglute> #chair markvoelker hogepodge
16:00:58 <openstack> Current chairs: eglute hogepodge markvoelker
16:01:06 <mguiney> o/
16:01:26 <eglute> #topic agenda
16:01:36 <hogepodge> hi!
16:01:51 <eglute> #link https://etherpad.openstack.org/p/InteropVertigo.14
16:02:15 <eglute> everyone, please take a look at the agenda and update as needed!
16:02:33 <markvoelker> #info No meeting next week due to PTG in Denver
16:02:42 <Rockyg> o/
16:03:06 <markvoelker> #topic PTG
16:03:23 <markvoelker> For those of you coming to Denver, have a look at the PTG schedule here:
16:03:28 <markvoelker> #link https://docs.google.com/spreadsheets/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/edit#gid=397241312 PTG schedule
16:03:43 <markvoelker> Interop/RefStack have Monday and Tuesday full-day sessions
16:04:26 <markvoelker> Also, don't forget there's a BoD meeting on Sunday:
16:04:31 <markvoelker> #link https://wiki.openstack.org/wiki/Governance/Foundation/10Sep2017BoardMeeting BoD Meeting Info
16:04:50 <hogepodge> On the schedule, please feel free to suggest other sessions or times.
16:04:59 <eglute> i will be at the board meeting! anyone else planning to attend ?
16:05:12 <markvoelker> eglute: I should be there too
16:05:22 <eglute> markvoelker great!
16:05:23 <hogepodge> markvoelker: eglute: if you feel we need more time for anything you can push things around. I loaded our mornings and left the late afternoons free
16:05:29 <hogepodge> I'll be at the board meeting also
16:05:45 <eglute> thank you hogepodge for working on the schedule. i will take a look in more detail
16:05:49 <eglute> but so far looks good to me
16:05:54 * markvoelker notes that someone named Irma may yet mess with travel plans, but doesn't currently forsee issues
16:06:18 <eglute> hogepodge markvoelker and i will be working on the board report as well, if anyone want us to note anything in that report, please let us know
16:06:37 <eglute> we will be presenting to the board the new guidelines and asking for approval
16:07:10 * eglute hopes weather cooperates and Irma gets demoted to a sprinkle....
16:07:21 <markvoelker> One other important PTG note: team photos!
16:07:25 <markvoelker> #info Team Photo will be Tuesday at 10:40am
16:07:57 <hogepodge> You have to think about all sorts of things when you're a PTL
16:08:12 <hogepodge> Oh, one item we might want to add to the agenda is converting from a WG to a SIG
16:08:13 * eglute wonders if we could dress up as onions for the photo shoot
16:08:37 <markvoelker> #link https://etherpad.openstack.org/p/InteropDenver2017PTG InteropWG PTG schedule
16:08:39 <hogepodge> The main benefit would be that we could roll RefStack into the Interop SIG
16:08:58 <eglute> hogepodge please add that to the agenda then!
16:09:05 <markvoelker> hogepodge: Seems reasonable to add; I know this has come up a couple of times over the past few weeks.
16:10:07 <hogepodge> Yeah, I've been crabby about it. We change our names too much ;-)
16:10:35 <markvoelker> Any other PTG-related items we want to discuss today?
16:11:30 <markvoelker> Ok, let's move on then.
16:11:36 <eglute> can't wait to see everyone there :D
16:11:43 <markvoelker> #topic Extension programs
16:12:11 <markvoelker> Let's take a quick pass at the queue as we have a few patches out
16:12:24 <markvoelker> #link https://review.openstack.org/#/c/492635/ Designate extenstion program
16:13:01 <eglute> looks good to me!!
16:13:07 <eglute> +2 :D thank you hogepodge
16:13:35 <markvoelker> This one feels like we're pretty much in agreement on the basics.  I'm still not sure I like the "ptl_proposed" achievement that we talked about the other week though.
16:14:19 <markvoelker> How do other folks feel about that?
16:14:37 <markvoelker> See line ~55 of https://review.openstack.org/#/c/492635/2/extensions/dns.next.json for info
16:14:44 <eglute> i think we should update that before it goes into required
16:15:00 <eglute> but good for now
16:15:52 <hogepodge> I can send a patch up right now removing it.
16:16:15 <markvoelker> One concern for me is how the BoD might react to it, as this is not a criteria that has been in previous programs
16:16:59 <eglute> markvoelker what do you propose? i think we talked about replacing it with something else before
16:17:21 <hogepodge> I think it would make sense to ask for their guidance on it. Part of my reasoning was that we should be listening to project leadership, as they are the subject matter experts.
16:17:46 <markvoelker> Personally I'm not sure we need it at all...using the criteria we have for Powered but scoping to an appropriate audience for an extension program seems sufficient to me.
16:18:15 <hogepodge> Plus, I want to encourage all projects to generate their own guidelines that we can draw upon.
16:18:16 <markvoelker> Talking to the PTL's/cores/other parts of the community is already something we do in Powered too.
16:18:36 <eglute> hogepodge i agree on listening to PTL, but perhaps just having them document how things are scored?
16:18:39 <hogepodge> But we don't explicitly mark their opinions as a reason for inclusion.
16:18:58 <markvoelker> My main concern is that it boils down to an opinion of a small part of the community (and carries a relatively hefty weight).
16:19:34 <Rockyg> or exclusion
16:20:16 <hogepodge> All of this is negotiable, and since nothing is required the proposal cost is low. I can remove it though, either way it's no big deal to me. It's mainly there because I didn't know what criteria to include originally, so all my decisions as to what was added came from PTL suggestions.
16:20:22 <hogepodge> That's the reason any capability is there.
16:20:59 <hogepodge> Just let me know and I can adjust the patches.
16:21:20 <markvoelker> Personally I'd favor removing it if no one has strong opinions in favor of keeping it....
16:21:42 <eglute> +1 on removal
16:23:01 * markvoelker doesn't hear anyone advocating for keeping so suggests we go ahead and remove it
16:23:36 <eglute> +2
16:24:19 <markvoelker> Ok, I'll keep an eye out for the update from hogepodge then, and we'll land this after that.
16:24:24 <markvoelker> Sound good?
16:24:26 <hogepodge> dns review updated
16:24:40 <markvoelker> =)
16:24:56 <Rockyg> kewl
16:25:22 <hogepodge> uh wait, needs more work
16:25:44 <markvoelker> Ok, let's talk about Heat while Jenkins runs and we get kinks ironed out...
16:26:02 <markvoelker> #link https://review.openstack.org/#/c/490648/ Heat extension
16:28:02 <markvoelker> So, a bit more discussion on this one.  I think that last patch added stack-update and worked out a few organizational suggestions...
16:28:18 <markvoelker> But I've not reviewed patchset 5 yet
16:29:03 <markvoelker> err...6 now =)
16:29:34 <hogepodge> (I'm getting on a plane soon so I'm motivated to finish off work)
16:29:36 <markvoelker> Anyone else have things to say about the current set?
16:30:00 <eglute> i need to review newest patches as well
16:31:12 <Rockyg> my browser is having problems, so can't see :-(
16:31:58 <markvoelker> Ok, let's see if we can polish this off in the next day or two then--I'd like to be able to show the preliminaries off to the BoD on Sunday
16:32:12 * markvoelker blocks a couple hours on his calendar
16:33:07 <markvoelker> Anything else on the Heat extension?
16:33:25 <eglute> same as you markvoelker need to do final review
16:33:34 <eglute> no, nothing else
16:34:01 <hogepodge> need to update based on comments on patch set 3, so another review is coming soon
16:34:09 <eglute> thank you hogepodge
16:34:15 <markvoelker> Ok, last one on the queue is this one then:
16:34:20 <markvoelker> #link https://review.openstack.org/#/c/472785/ Extensions draft
16:35:39 <eglute> there are some good comments from hogepodge that i think need to be addressed
16:35:58 * hogepodge just pushed up another heat review, patch set 7 should be the final barring errors or new comments
16:36:16 <hogepodge> eglute: markvoelker: we're planning on bringing this to the board on Sunday, right?
16:36:24 * luzC1 enter and sit at the back
16:36:28 <eglute> it would be good if we did
16:36:50 <markvoelker> Sure.  Doesn't even have to be final--the Board's input would be welcome too.
16:37:37 <markvoelker> I'll note that we've showed this to them once before as well (in June)
16:37:42 <eglute> agreed
16:38:54 <markvoelker> I plan on making a few touch-ups in the next day or so.  One thing that would be nice to settle on: is "extension" the term we've agreed upon? =)
16:39:03 <eglute> thank you hogepodge for patching things so quickly, will review!
16:39:26 * Rockyg luzC there's p;ent of room at the table ;-)
16:39:26 <eglute> i think naming is up to foundation. hogepodge what have you heard?
16:39:39 <Rockyg> plenty
16:40:10 <Rockyg> ouch.  bad timing on my correction.  Sorry
16:40:29 <luzC1> Rockyg ;)
16:40:58 <markvoelker> I don't really have much of an opinion on "add-on" vs "extension" vs something else personally
16:41:00 <luzC1> I'll take a look at the patches too... I'm a little behind on reviewing the extensions
16:41:01 <hogepodge> haha, I think it's a community choice.
16:41:08 <hogepodge> I've been saying extension because I like it better
16:41:32 <hogepodge> I can ask the exec staff for their preferences though
16:41:35 <markvoelker> I've been saying "add-on" because "extension" had a negative connotation for interoperability for a time there. =)
16:41:47 <eglute> hogepodge i was thinking that marketing people might have some input
16:42:01 <eglute> i do like add-on as well
16:42:21 <markvoelker> But again, the name doesn't matter much to me...just trying to be consistent
16:42:21 <eglute> but i do not have strong preferences for the names
16:42:59 <eglute> agreed, for as long as we are consistent and marketing people approve :)
16:43:19 <markvoelker> Ok, so I'll just pick one and stick with it when I update the patch and we can get feedback on a final name later.
16:44:33 <hogepodge> Consensus from exec and marketing staff is "add on"
16:44:38 <markvoelker> BTW hogepodge: by "logo assets are out of date" I assume you were talking about the old OpenStack 3D/shadow logo vs the new 2D one?
16:44:45 <markvoelker> Ok, thanks...I'll go with that for now then
16:44:47 <hogepodge> markvoelker: yeah
16:44:55 <markvoelker> Cool, I'll update that too
16:45:02 <hogepodge> I'll update language where I've used it. New patches coming soon :-D
16:45:13 <eglute> thank you hogepodge
16:45:50 <eglute> and thank you for checking with the exec and marketing staff!
16:46:06 <markvoelker> Any other major issues we want to discuss with this one?
16:46:34 <eglute> nope!
16:47:12 <eglute> reminder for everyone to add yourselfs to the list on PTG agenda if you are attending in person or would like to join in remotely
16:47:24 <markvoelker> #topic open floor
16:47:39 <markvoelker> Anything else to talk about today folks?
16:48:00 <eglute> I hope nobody was hit by Harvey and are away from Irma...
16:48:32 <Rockyg> agreed
16:48:53 <Rockyg> and away from the fires in the west
16:49:08 <eglute> +1
16:49:18 <eglute> hogepodge are you affected by the fires?
16:49:18 <luzC1> +1
16:49:24 <eglute> and luzC1?
16:49:46 <Rockyg> we got lots of pollution from them in the bay area.
16:50:00 <Rockyg> Like visiting Beijing
16:50:16 <luzC1> there is ashes comming down
16:50:35 <hogepodge> it's pretty bad here
16:51:02 <hogepodge> One of the most beautiful natural areas in the PNW is on fire, and they don't expect it to recover to 100 years
16:51:09 <mguiney> :(
16:51:13 <eglute> :(
16:51:24 <Rockyg> :9
16:51:28 <hogepodge> It's raining ash in the city, and they're cancelling school and advising people to stay indoors until the fires die down and the wind shifts
16:51:29 <eglute> mguiney hogepodge and luzC1 i hope you are far away from it
16:51:29 <Rockyg> :(
16:51:37 <hogepodge> Still, it's nothing like what's happening in Texas
16:51:37 <eglute> wow that is really really bad
16:51:54 <mguiney> it's been a natural disaster summer all around
16:52:12 <eglute> yeah, the coast here is wrecked. as well as some other areas outside of San Antonio
16:52:16 <hogepodge> How are the SA folks doing? Have you been impacted by the hurricane?
16:52:36 <eglute> it skipped us, we barely got any wind and a bit of rain
16:52:59 <eglute> north of SA got a lot of rain and wind
16:53:08 <eglute> but still nothing as bad as Houston and the rest of the coast
16:53:31 <hogepodge> markvoelker: Is your family ready for Irma?
16:53:45 <markvoelker> I'll be keeping an eye on Irma as the latest tracks have it more likely to affect my area than before.  I should be in Colorado when/if it comes to town though.
16:54:25 <markvoelker> We're currently not expecting major issues in our area (beyond rain/wind/trees down/power out) but we're preparing for worse if necessary.
16:54:26 <eglute> markvoelker i hope it skips your town...
16:55:09 <Rockyg> I hope it skips everyone's town
16:55:15 <eglute> SA had a gas shortage this last week. News went a bit crazy with their headlines and people panicked.
16:55:35 <eglute> Rockyg agreed.. would be nice if it just died in the ocean.
16:55:42 <Rockyg> ++
16:56:18 <markvoelker> Ok folks, stay safe and travel safe where ever you are this week!  Hope to see most of you in Denver.
16:56:29 <eglute> bye!!
16:56:35 <markvoelker> #endmeeting