00:01:25 #startmeeting congressteammeeting 00:01:26 Meeting started Thu Aug 17 00:01:25 2017 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:01:29 The meeting name has been set to 'congressteammeeting' 00:02:22 hi all! as usual, the collaborative topics list for the meeting is here: https://etherpad.openstack.org/p/congress-meeting-topics 00:02:39 feel free to add/comment 00:09:50 Hi all. 00:10:15 (Sorry I'm late. Got to leave early too.) 00:11:23 oh hi thinrichs ! 00:11:39 ramineni on vacation this week and masahito may be traveling. 00:12:25 Ok 00:12:33 so we can spend some time talking or just catch up next week. 00:15:34 Either way. I only have 15min or so. 00:17:07 ok. well. I’ve been dropping down thoughts in the PTG etherpad. 00:17:13 https://etherpad.openstack.org/p/congress-ptg-queens 00:17:47 I think in the past few cycles we had clear deficiencies and problems to work on. 00:18:36 at this point though, I feel we may need to consider higher level directions to inform our lower level priorities. 00:18:47 your input would be super helpful. 00:19:44 that’s one thing I wanted to bring to your attention. 00:20:31 I think it'd be valuable to start targeting specific use-cases that folks have and solve them end-to-end. 00:20:45 We're doing that to some extent with the policy library and remediating problems. 00:21:42 Talking to Bryan from ATT and to NFV operators as you suggest could point to real pain points 00:22:43 There's also the suggested use-case around configuration invariants that came up a couple weeks back. 00:23:42 right. 00:24:25 It may be a cycle where we spend a lot of time talking to people to understand what the major pain points in OpenStack are that we can help with. 00:25:15 One thing that was on my list for a long time is working to help people manage all the policy.json files. 00:25:55 Security groups is another popular one 00:25:56 hmm good point about the possibility of focusing the cycle on that instead of features. 00:26:59 For me I feel like there is a bit of a bifurcation between the traditional enterprise use cases and the NFV use cases. 00:27:47 And I’d like to understand much better whether/where congress provides value in the NFV use cases. 00:27:54 That could be. It'd be fine to pick 1 class of use-cases and focus on that for a while. 00:28:19 Probably even smart to pick 1 class of use-cases 00:28:25 Or even better 1 use case 00:29:19 hmm makes sense. 00:32:50 one way to break down the classes of use cases: 00:33:06 1. “human” policy kind of cases. 00:33:21 2. “fault-recovery” kind of cases 00:33:42 I think congress was originally designed to address 1. 00:33:53 but there have emerged many people interested in using congress for 2. 00:34:32 and what use-case(s) we pick to focus on may depend on a better understanding of whether/where congress plays in 2. 00:36:29 so I’m studying up on things and hopefully connecting with some people to have more context for PTG. 00:37:09 Talking to people who have ideas definitely sounds like a good plan. 00:37:39 (I'm not sure what 1 is — someone looking at violations in a dashboard?) 00:40:00 that’d be one case. I’m still formulating what it means really. but seems qualitatively diferent from the idea of 00:41:11 writing policy as a way to react to contingencies in a self-managing system. 00:47:03 ending meeting now. I’m available in #congress if anyone wants to talk! 00:47:05 #endmeeting