00:01:22 #startmeeting CongressTeamMeeting 00:01:23 Meeting started Thu Oct 13 00:01:22 2016 UTC and is due to finish in 60 minutes. The chair is thinrichs1. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:01:26 The meeting name has been set to 'congressteammeeting' 00:01:35 Good day" 00:01:39 o/ 00:01:46 Hi all! 00:02:00 njohnston: glad you made it back today! 00:02:20 This week ekcs is really running the meeting, but 00:02:35 he's trying to minimize typing b/c of RSI, 00:02:55 so he asked me to help out 00:03:03 Here's the agenda for the day… 00:03:08 thanks thinrichs1 ! 00:03:11 1. Barcelona 00:03:20 2. Newton.0.1 release 00:03:26 3. PTG 00:03:28 4. Status updates 00:03:31 5. Open discussion 00:03:35 Anything else to add? 00:03:44 ekcs: happy to help! 00:05:23 #topic Barcelona 00:06:07 Remember that the focus for the summit is around use-cases and new features to satisfy use cases 00:06:39 Here's our etherpad, where we're keeping track of who has ideas for use cases and when they're presenting those. 00:06:43 #link https://etherpad.openstack.org/p/congress-ocata-design-summit 00:07:09 We should all be thinking about use cases that we think are important, 00:07:15 making notes of them in the etherpad, 00:07:40 so that by the end of the summit we can prioritize use cases and the features needed to implement them 00:08:19 njohnston: Given your interests, perhaps now is a good time to introduce yourself to the group and say a bit about why you are interested in Congress 00:09:13 Hi! My name is Nate Johnston, and I am a core contributon for the neutron-fwaas team 00:09:47 neutron-fwaas implements Firewall as a Service, which is really just a large dictionary of policies to enforce and the enforcement mechanism to implement the rules 00:09:55 Maybe he stepped away. We can come back to him later. 00:09:55 Any questions or comments about Barcelona? Ideas about people to invite? 00:10:41 So I submitted this blueprint to talk about some of my use cases: https://blueprints.launchpad.net/congress/+spec/congress-fwaas 00:10:45 netsplit? 00:11:12 thinrichs1: I'm seeing njohnston's comments. 00:11:17 If a netsplit, seems it caught up now 00:11:42 I'm seeing njohnston's comments too now 00:12:28 I think that congress and fwaas are a very good combination, and I am excited to start looking at integrations 00:13:55 Adding to meeting summary. #link https://blueprints.launchpad.net/congress/+spec/congress-fwaas 00:14:25 njohnston: Cool! I read over your revised blueprint just now. Seems interesting and at first glance doable 00:14:36 njohnston: tried to leave a comment, but launchpad barfed. 00:15:03 thanks! 00:15:10 so other than that, I am here to watch and learn 00:15:44 njohnston: welcome (again)! I'm looking forward to discussing this use case in Barcelona! 00:16:11 Any other comments/questions for njohnston? 00:16:53 If you think of anything, hit me up anytime - I am usually in #openstack-neutron 00:17:05 speaking fo which, do you all have an IRC channel you use? 00:17:10 #congress 00:17:26 njohnston: good to know where to find you! 00:17:43 excellent! I joined #openstack-congress but I was sad and lonely. 00:17:56 :) 00:18:33 Besides njohnston we have 1 other speaker for that 40 minute slot in the large fishbowl room. 00:19:00 I'd say 2-3 speakers is probably the right number. 00:19:07 I reached out to the Monasca team, but Fabio who most of you know isn't making the trip. 00:19:57 Any other thoughts about a 3rd speaker to invite? 00:20:58 #topic Newton.0.1 00:21:15 has anyone talked to the vitrage guys lately? 00:21:29 ekcs: not me 00:22:03 I see on their workesssion agenda that they mentioned congress. 00:22:22 so seems they still have interest in something. I can shoot them an email. 00:22:51 ekcs: that'd be great! The other team that we met with last time was Watcher. 00:24:08 ekcs: I'm happy to help reach out to folks—let me know who you'd like me to ping 00:24:25 ok. 00:24:29 On to Newton I'd say, given the time. 00:25:08 There are a number of lingering issues we didn't have a chance to fix before the Newton release... 00:25:13 - ceilometer driver 00:25:26 - remove database locking #link https://review.openstack.org/#/c/384747/ 00:25:40 - check DB not mem in datasource create #link https://review.openstack.org/#/c/376166/ 00:25:49 Anything else come to mind? 00:27:21 I'd lean toward pushing those changes to stable/newton 00:28:06 We don't need to do a release until we feel there's enough different to warrant one 00:28:19 if we modify stable/newton, does that obligate a x.0.1 release at some point? 00:28:47 ekcs: not sure. This is the first cycle we've had the release team actually manage our releases. 00:28:53 most likely, I would thing, so that the packagers have something to release to consumers 00:29:04 like RDO and the debian build people 00:29:38 njohnston: agreed that we shouldn't be pushing stuff to stable/newton unless we expect to do a release at some point 00:30:03 what I don't know is whether the release team does 1 release for all the projects at the same time, or whether each project can release independently 00:30:24 I believe there is milestones 00:31:07 I wondered whether it’s worth putting more work into (non-critical) newton update given that ocata is right around the corner. 00:32:01 I believe that when O-1 drops N+1 usually drops at the same time, for non-client projects https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwi8m4i9w9bPAhVJeT4KHTtwA4kQFggnMAA&url=https%3A%2F%2Freleases.openstack.org%2Focata%2Fschedule.html&usg=AFQjCNElEllVCBXggiyMaeKmDtZ2Z0mRyQ&sig2=7I3cG_hrTsQQZAfgVVFIEg&bvm=bv.135475266,d.cWw 00:32:09 oops, bad link there 00:32:15 was trying to link to https://releases.openstack.org/ocata/schedule.html 00:33:52 but given that we are supporting newton for a couple more cycles I guess we should expect that there will be an update at some point. 00:33:53 so putting some of these changes in is not a big marginal cost if we’re going to do an update anyway. 00:33:53 main cost to us is manual testing. 00:33:53 I would expect another release on newton/stable given how many changes went in so late. 00:33:53 makes sense. 00:33:53 masahito: do you have any thoughts? 00:33:53 And it's time for us to start thinking about backporting bug-fixes periodically and doing releases 00:34:16 got it thanks njohnston ! 00:34:41 just make sure that you are following the stable branch policy from the release team: "The stable branches are intended to be a safe source of fixes for high impact bugs and security issues which have been fixed on master since a given release." 00:34:44 http://docs.openstack.org/project-team-guide/stable-branches.html 00:35:42 high-impact/security bugs….hmmmm…not sure any of our changes meet that criteria 00:35:49 ekcs: what do you think? 00:36:43 I think the bugs listed in above meets the criteria. 00:36:45 I’d htink ‘no’ to the DB changes. but maybe yes to ceilometer and testing changes. 00:36:53 based on this “Note It’s nevertheless allowed to backport fixes for other bugs if their safety can be easily proved. For example, documentation fixes, debug log message typo corrections, test only changes, patches that enhance test coverage, configuration file content fixes can apply to all supported branches. For those types of backports, stable maintainers will decide on case by case basis.” 00:37:38 Testing changes make sense to ensure we've got good tests for when we patch critical problems. 00:37:52 Ceilometer seems less critical, but certainly safe 00:39:23 well maybe we can decide later on the DB changes. 00:39:44 I don’t think they’re necessarily high-impact. 00:40:02 unless someone runs into problems. 00:40:08 ekcs: right. We could put those in if we need to patch another bug that is high impact and that depends on the new DB stuff 00:40:30 Time check: 20 min remain. 00:40:34 thinrichs1: agreed. 00:40:42 Let's move on to the next topic 00:40:44 #topic PTG 00:41:07 Remember that last week we discussed whether to have Congress meet-ups at the PTG. 00:41:24 If I remember right, everyone was in favor of the PTG meetups. 00:41:45 That doesn't stop us from also meeting up at the summit (without any meeting-rooms) 00:41:59 We need to decide in the next few days (if I remember right). 00:42:25 right. 00:42:26 Anyone NOT want us to set up PTG meetings for Congress? 00:42:51 Anyone know they won't be able to attend the PTG meetings? 00:42:55 note this is juts for the first PTG. we can always do something different in later PTGs if it doesn’t work well. 00:43:18 ekcs: Atlanta this time? 00:43:30 thinrichs1: yes. 00:43:32 Has Congress ever tried a virtual mid-cycle? 00:43:34 feb 00:44:01 aimeeu: nope 00:44:28 on meeting up at future summits, we are certainly free to meet, just that I don’t expect most to be there if we adopt PTG model. 00:44:48 ekcs: agreed 00:44:50 just asking about virtual because the Tacker team opted out of the PTG in favor of their normal virtual mid-cycle 00:45:10 so something to think about for the future 00:45:16 virtual would be interesting, though time-zones would be difficult 00:45:18 if budgets continue to shrink 00:45:35 masahito: are you planning to come to the Atlanta PTG? 00:45:36 thinrichs1: yes, we in the US would probably end up working 2nd shift 00:45:49 thinrichs1: yes if we have 00:46:29 aimeeu: do you know if tacker expects to do the “mid cycle” at the beginning of the cycle (feb) or the middle? 00:46:57 ekcs: nope - I didn't look into it that part 00:47:44 I'd vote for doing it if people think they'll have budgets to make the trip. 00:48:00 Otherwise, we could set up a virtual meet-up 00:48:54 ekcs: can you make the trip? 00:48:59 aimeeu: what about you? 00:49:24 I don't know yet - I just changed positions at work - new boss, new org, lots of unknowns as to travel 00:49:25 I can def make it. possibly whether we have work sessions or not. 00:50:05 maybe I’ll get ramineni’s take on whether she thinks she’ll be able to make it. 00:50:22 That sounds like 3 pretty strong Yes, 1 maybe, and 1 probably Yes (assuming ramineni continues to travel like she has in the past) 00:51:12 ok so on the PTG response, we can say YES or NO or MAYBE. 00:51:35 so we are either YES or MAYBE. seems like YES. 00:51:42 Well if ramineni can make it, I'd think it's a Yes. If she can't, I'd say it's a Maybe 00:51:49 great. 00:52:00 9 min left. 00:52:07 #topic Status and open discussion 00:52:57 Let's do this simultaneously since we're short on time. 00:53:03 masahito, aimeeu, ekcs: status updates? 00:53:17 Or anything else that needs to be discussed as a group? 00:53:45 not much from me - Summit prep mostly 00:54:20 I’m working on DB change and multi-proc haht tox test. looking into the antlr mess again. and summit prep. 00:55:13 but mostly I’m focused on gathering material for the work sessions. 00:55:18 anyone looked at the schedule and see any talks of interest to us? 00:55:36 There are a number that come up when searching for Congress 00:55:48 I haven't gone thru the talks other than that 00:56:44 got it. i’m in the process of going through them. some interesting policy things but I haven’t organized them in any way. 00:57:11 I'm working on use-case policy of Doctor fits current congress features for summit session. 00:57:28 ekcs: I'd be interested in seeing your list when you're finished. Maybe post to the ML when you're finished? 00:57:38 ok thinrichs1 00:57:38 I think there is at least one OPNFV talks that mentions Congress 00:57:56 masahito: cool! Looking forward to seeing your talk 00:58:10 aimeeu: it would be my session. 00:58:29 https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Congress 00:58:32 masahito: oh yes! I just found it 00:58:47 ekcs: BTW tacker will have a virtual in Feb 00:59:24 aimeeu: thanks! so they’ll have a virtual “start cycle" 00:59:33 ;p 01:00:26 Out of time for this week. 01:00:30 Thanks all! 01:01:02 thanks 01:01:23 #endmeeting