15:00:27 #startmeeting operators_telco_nfv 15:00:37 Meeting started Wed Jun 15 15:00:27 2016 UTC and is due to finish in 60 minutes. The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:41 The meeting name has been set to 'operators_telco_nfv' 15:00:52 #topic rollcall 15:01:07 hi, is anyone here for the ops telecom/nfv meeting? 15:01:09 :) 15:01:37 hi 15:02:13 hi shintaro 15:02:28 lets give a couple minutes to see if anyone else shows up 15:03:14 ok 15:03:21 if anyone is here for the ops telecom nfv meeting let me know :) 15:04:53 shintaro where are you located? 15:05:28 I am. 15:05:31 Japan. so its midnight. the agenda etherpad says there are conference call number. is this the right channel? 15:06:06 yup it is the right channel, there is also a conference number but I can't get on it 15:06:20 we are still figuring things out in terms of how this meeting will operate 15:06:37 ok. since it midnight and I'm at home, IRC is better :) 15:07:04 there was one person so far that asked for a conference number so far, but we'll see what happens 15:07:41 #topic APAC meeting time 15:08:03 while you are here do you have any thoughts on an APAC meeting time? 15:08:22 yes, this is tough time for APAC. one hour earlier would be better 15:08:34 are there people who would attend another meeting at another time? 15:08:43 like one meant specifically for APAC? 15:09:22 ie. if we had a even meeting and an odd week meeting where the odd week was an APAC time? 15:09:28 oh, ok. Im not sure if we have enough people in APAC to have different meetings 15:09:41 ok 15:10:01 well, it's been 10 min and I don't think we are going to get anyone else. It's going to take some time to gather people up for this. :) 15:10:03 and need someone to attend both to link them together 15:10:19 yeah I would attend both if there was two 15:10:23 People are still joining the channel... 15:10:35 ah, ok :) 15:10:53 and I'm somewhat assuming that people joining when there's a meeting that's just started are joining for that meeting. 15:12:01 Though I guess by now anyone else is pretty much late, so probably not worth waiting around. 15:12:08 ok if anyone is here for the ops telecom/nfv meeting other than shinto and PerfectChaos do let me know :) 15:14:03 yeah I don't think anyone else is on 15:14:08 #topic open discussion 15:14:27 shinto or PerfectChaos do you have anything you'd like to add/ask/suggest etc? 15:14:34 so will there be a BoF at OPNFV Summit? 15:14:43 yeah there will be 15:15:00 I'm not completely sure of the time yet 15:15:14 there will be a few openstack related sessions, but one will be an operators birds of a feather 15:15:35 great. so I will check the session schedule. 15:15:39 I think it's on tuesday, but I will send out an email to the openstack operators list when I know for sure as well 15:16:06 serverascode: thanks 15:16:10 #info There will be an operators bof at the opnfv summit, email to follow 15:16:36 #action serverascode to email to operators list when we know when the opnfv ops bof will be 15:17:03 ok, well I'm sorry we didn't get much of a turnout, there is some work to do to make sure people know about this meeting 15:17:12 it'll take some time to get this all ironed out 15:17:48 unless there are any objections I will end the meeting and we will hopefully see you at the next meeting or even the opnfv summit :) 15:17:57 Yup. Though the e-mails seemed pretty clear to me... 15:18:18 yeah 15:18:26 I have a couple of thoughts before closing up... 15:18:28 yes. just I was confused on the conference call nuber on the etherpad 15:18:58 right, sorry about the confusion 15:19:35 The in-person meetings at the last couple of summits that I've been to (Telecoms workgroup, then NFV/Telecoms Ops) have never felt hugely coherent or focused 15:20:13 I agree +1 15:20:20 So I expect some people might not necessarily expect much to come out of meetings like these without much focus 15:20:41 I think if we had a clearer view of what we're actually trying to achieve here people might be more inclined to turn up. 15:21:13 For sure, the only problem is that we have to figure out that purpose somehow 15:21:35 my initial thoughts were to follow the large deployments team lead and try to find one or two big things to work on over time 15:21:42 but that was just my thinking 15:22:11 if you have any thoughts on what we should lbe working on I'd love to hear them 15:22:13 I don't mean necessarily in terms of "make component X do Y", but higher-level goals, like "identify N major NFV shortfalls before the next release and try to make sure someone is looking at them" 15:22:36 yes. I agree. especially relation between OPNFV need to be cleared. OPNFV has more ops and requirements discussed. 15:23:19 And then meetings can be more focused along the lines of "in this meeting we're looking to hear what problems people have, Ops people come and tell us" or whatever. 15:24:15 ok, so what do you think we should do before the next meeting? 15:24:48 do you want to jot down some ideas in the etherpad? 15:26:45 so perhaps have the entire topic of the next meeting be try to determine what we are actually doing? 15:29:07 I mean, intuitively I'd think that the Telecom/NFV ops group should be about trying to make life easier for Telecom/NFV ops. 15:29:48 Identify the problems they face, or the features they need, and take actions to ensure that those things are resolved. 15:29:55 Just an idea, but how about looking at some of NFV related user stories in the Product WG repo (if there are any, I'm not sure) and help make them merged and/or do the gap analysis? 15:30:13 yeah that could be interesting 15:30:47 But the group in its various guises so far hasn't had much visible output, and I think people are inclined to just work on those problems/features outside of the context of the group if they need them because it's not obvious how the group can help that. 15:30:48 there was a telecom working group that wrote several nfv/telecom related user stories, that's essentially what they did 15:31:04 before they disbanded and simply became part of the product working group 15:31:26 but it wasn't an "operators" working group to be clear 15:31:36 I suppose having a well-defined mission statement would be a good start. 15:32:06 for sure...is that something you'd like to take a crack at? 15:32:14 at least an initial version we could look at 15:32:57 Sure, I'll give it a shot. 15:33:02 cool 15:33:22 #action PerfectChaos to try writing a first version of a group mission statement or purpose 15:33:49 other thoughts? 15:33:59 That style of writing isn't exactly my strongest point, but I can at least come up with something as a starting point. 15:34:31 no worries, I think we just need something to work with, critique, agree with, etc 15:34:46 +1 15:35:26 any other open discussion ideas/thoughts? 15:36:02 None from me for the time being. 15:36:16 same here 15:36:53 all right, well thanks for your help, sorry not much of an attendance this week, about the same as the last meeting :) but we'll figure it out 15:36:58 #endmeeting