15:00:17 <serverascode> #startmeeting operators_telco_nfv
15:00:18 <openstack> Meeting started Wed Jul 13 15:00:17 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:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:21 <openstack> The meeting name has been set to 'operators_telco_nfv'
15:00:26 <serverascode> #topic rollcall
15:00:42 <serverascode> hello, anyone here for the ops telecom meeting? :)
15:00:55 <serverascode> #link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda
15:01:10 <serverascode> there's the agenda, please have a look and add items or make changes
15:02:26 <serverascode> will wait a few min
15:02:49 <ulik> #info Uli Kleber
15:03:12 <serverascode> hi Uli
15:04:22 <ulik> Hi, are we again small group?
15:04:32 <PerfectChaos> Looks like.
15:04:38 <PerfectChaos> (Also, hi~)
15:04:47 <serverascode> 3 so far looks like
15:05:07 <RandyLevensalor> Hi...I'm just lurking for my first meeting :)
15:05:28 <serverascode> hi RandyLevensalor, thanks for coming by
15:05:50 <ulik> So I at least someone heard my advertizing
15:06:01 <RandyLevensalor> #info Randy Levensalor
15:06:13 <RandyLevensalor> ulik, yeah
15:06:22 <serverascode> ok well perhaps we just kinda keep movin' on
15:06:28 <serverascode> #topic last meeting actions
15:06:54 <serverascode> 1. serverascode set [telecom-nfv] tag
15:06:54 <serverascode> 2. ulik share operators list and tag with OPNFV folks
15:07:24 <serverascode> so I did email the ops list, changing the email tag from [telco][nfv] to plain old [telecom-nfv]
15:07:48 <serverascode> ulik, sounds like you did share the meeting details with other OPNFVers so we completed both of those actions :)
15:08:18 <serverascode> next topic!
15:08:33 <ulik> There was one more info.
15:08:48 <ulik> We have a community page for OpenStack in OPNFV wiki
15:08:53 <ulik> #link https://wiki.opnfv.org/display/COM/OpenStack
15:09:03 <ulik> There is a lot of stuff there.
15:09:04 <serverascode> ah, cool ok
15:09:30 <ulik> It is far from complete.
15:09:52 <ulik> But we have a selection of OPNFV projects there together with the actions they tried to push in OpenStack.
15:10:21 <serverascode> yeah that is really handy
15:10:34 <serverascode> I will have to read through that
15:11:03 <serverascode> should we go on to the mission statement?
15:11:32 <serverascode> #topic mission statement
15:11:59 <serverascode> #link https://etherpad.openstack.org/p/ops-telecom-nfv-mission-statement
15:12:22 <serverascode> did anyone have a chance to look at it? I'm not sure where we go from here -- do we start editing collaboratively somehow?
15:12:57 <PerfectChaos> Side-note: It turned out there was a small amount clipped from the end of the first line when I pasted it in here last week, too.
15:13:18 <PerfectChaos> Hooray for working in a medium with character limits that aren't obvious on the client-side, I guess.
15:13:31 <PerfectChaos> I've just added the missing words back into the etherpad.
15:13:41 <serverascode> super thanks PerfectChaos
15:14:13 <PerfectChaos> Also it looks as though someone accidentally pasted in something else they were working on?
15:14:13 <serverascode> perhaps we can all take an action item to read through it and perhaps come up with some editing suggestions?
15:14:30 <serverascode> yeah I see that at the top there, the 180 ringing service?
15:14:33 <PerfectChaos> Yup.
15:14:41 <serverascode> I'll take that out, not sure where it came from
15:15:01 <ulik> Should we try the mission statement attract people, so they will use us to help them in OpenStack?
15:15:02 <serverascode> it'll be in the history if someone needs it back for some reason
15:15:36 <ulik> (that implies the question: who will use the mission statement?)
15:16:55 <serverascode> well, I think one of the mission statements uses is to describe what hte group does so other people can understand what we are doing
15:16:58 <serverascode> is that what you mean?
15:17:53 <ulik> Let's say, if I point OPNFV people to read that, I would hope, they understand that we can help them get their ideas discussed with the right people in OpenStack community.
15:18:06 <serverascode> ah, ok
15:18:45 <ulik> But if we need to convince some OpenStack leaders that this WG has value, we might need to have other stuff in the mission statement.
15:18:52 <ulik> :)
15:19:28 <serverascode> absolutely
15:19:42 <ulik> Do we need to do both?
15:20:34 <serverascode> I think we do yeah, we need people like the opensack foundation to understand, as well as that end users can ask us to help them get improvements into openstack
15:21:05 <serverascode> I put a section in for suggested changes, so feel free to add any ideas there too
15:22:00 <RandyLevensalor> Is there any relationship from this group to the ops working group?
15:22:39 <serverascode> which ops working group? the "osops" group in openstack?
15:22:45 <serverascode> or something in opnfv?
15:22:53 <RandyLevensalor> osops
15:23:11 <serverascode> not as of yet
15:23:40 <serverascode> but if we ever write any code to help with nfv operations it might end up in the osops repos
15:24:56 <serverascode> ok, so perhaps we all take an action item to review the mission statement and make some suggestions for next meeting, sound ok?
15:25:05 <ulik> What is osops?
15:25:12 <ulik> Yes. AI is good!
15:25:22 <serverascode> #link https://wiki.openstack.org/wiki/Osops
15:25:58 <serverascode> I'm not too sure where osops is now, but the original goal as far as I know was to get opentstack ATC (?) status for operators
15:26:21 <ulik> Great. That also gives an example mission statement :)
15:26:29 <serverascode> yeah good point
15:26:48 <serverascode> they have several repos where operational oriented code goes into
15:26:57 <serverascode> but that is just my impression
15:27:40 <serverascode> right, this is a good segue into the next topice
15:27:49 <serverascode> #topic openstack working group process
15:28:02 <serverascode> #link http://lists.openstack.org/pipermail/openstack-operators/2016-July/010997.html
15:28:24 <serverascode> Edgar from the openstack user commitee sent me that email
15:28:38 <serverascode> so one of the things we might have to do is work through that process to become and official working group
15:28:47 <serverascode> I'm not super clear on how that works though
15:29:23 <serverascode> if anyone wanted to take that as an action that'd be cool, just to figure out what it means
15:29:29 <serverascode> otherwise I will work on it :)
15:30:44 <serverascode> ok, next topic
15:30:51 <ulik> What is the main difference between a WG under TC or under UC?
15:31:10 <serverascode> I am not too sure right now
15:31:30 <RandyLevensalor> I think that UC is more focused on using openstack.  Where TC is focused on development of a component.
15:31:48 <serverascode> #link https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit
15:31:57 <Julien-zte> #info Julien
15:31:59 <serverascode> ^^ that's the user committee charter
15:32:13 <serverascode> they also have a mission statment :)
15:33:04 <ulik> Sounds like we can copy a lot from that mission statement ;-)
15:34:18 <serverascode> yeah
15:34:48 <serverascode> I guess this topic was more informational, that there is a user committee and that to be an official working group we'll need to work with them
15:35:04 <serverascode> I will investigate some more and report back next meeting
15:35:24 <serverascode> #action serverascode investigate user committee working group requirements
15:35:44 <serverascode> any other thoughts on that?
15:36:24 <ulik> I think we all need to read through the whole document, since it will tell us how we have to work as a UC WG
15:36:57 <serverascode> ok
15:37:08 <serverascode> #action everyone read the UC charter document
15:37:21 <serverascode> now we all have an action :)
15:37:56 <ulik> WGs for them are temporary. Functional teams are permanent. What are we?
15:38:23 <serverascode> yeah that is an interesting point
15:38:49 <serverascode> I would think we would be more a long term team
15:39:01 <PerfectChaos> If that's the main distinction, I'd see this more as a functional team
15:39:22 <ulik> yes. Me too
15:40:20 <serverascode> #agreed We are likely a functional team as opposed to a working group in the UC definition
15:40:56 <serverascode> I think it's going to take some time to move through that process
15:41:34 <ulik> Just another thought.
15:41:50 <ulik> This former telco wg. Did it have such a status?
15:42:12 <serverascode> I'm not sure, I think the UC thing might be new
15:42:38 <serverascode> I can look into that though
15:42:50 <ulik> But anyways. I feel that such a status will not protect us from a similar fate.
15:43:42 <serverascode> right
15:43:54 <PerfectChaos> As I understand it, the Telco WG had a specific end goal in mind, and achieved that.
15:44:15 <PerfectChaos> And so it somewhat fit the UC's definition.
15:45:06 <ulik> While we are working on bringing our wg to a proper status in OpenStack organization, we should try to create value for some people.
15:45:39 <serverascode> yup, that would be the next topic I believe :)
15:45:55 <serverascode> #topic Things to work on
15:46:15 <ulik> Maybe we find ideas for creating value when reading that community page in OPNFV wiki or such stuff.
15:46:52 <serverascode> as an informational note, I was kind of modelling this group on the openstack operators large deployment team
15:47:10 <serverascode> they would pick one or two major items to work on over medium to long term time frames
15:47:17 <serverascode> I don't know if that is what we should do, but it seems to work for them
15:47:39 <serverascode> that's the large deployment team that's listed in the UC doc we were just looking at
15:48:42 <serverascode> does anyone have any thoughts on that? should we be looking at a bunch of small projects, or a couple larger ones?
15:49:18 <ulik> I think that would be a good thing. We shouldn't pick too small (not much value) or too big (too challenging)
15:49:19 <RandyLevensalor> What about capturing several use cases and then deciding on the top ones to work on for the N or O release.
15:49:34 <serverascode> #link https://wiki.openstack.org/wiki/Large_Deployment_Team
15:49:49 <ulik> Yes. Everybody could bring proposals to next meeting :)
15:49:51 <RandyLevensalor> OPNFV could be leveraged for some of the use cases
15:50:03 <ulik> Yes!
15:50:45 <serverascode> all great points
15:51:04 <serverascode> I think a medium project sounds good too
15:51:43 <serverascode> but like ulik said, we need to start working on something
15:51:54 * PerfectChaos nods
15:51:59 <serverascode> so is it enough for today to say bring some proposals to the next meeting?
15:52:06 <PerfectChaos> Given the timescales, I'd say the O release looks more likely...
15:52:26 <serverascode> true
15:52:36 <RandyLevensalor> agreed
15:52:47 <serverascode> lets not forget too that our project could be not related to code, could be documentation or performance testing, etc
15:53:10 <serverascode> there's a lot of value in those kinds of projects as well
15:53:21 <PerfectChaos> Yup.
15:53:41 <serverascode> also it would be good to solve problems we are experiencing ourselves as operators, be it in production or in the lab, or otherwise
15:54:23 <serverascode> ok so bring some ideas to the next meeting?
15:54:52 <serverascode> #action Everyone bring project ideas for the next meeting
15:55:28 <serverascode> shall we move on to open topics/discussion?
15:56:01 <serverascode> #topic Open discussion
15:56:37 <serverascode> so we have a couple min of open discussion, so if you have anything to add throw it out there :)
15:57:34 <RandyLevensalor> OpenStack summit CFP ends today.  Should this WG submit a talk?
15:58:43 <serverascode> that's a good thought, I'm not sure what we would even submit though
15:58:49 <PerfectChaos> It feels a bit early in the day for that.
15:59:08 <serverascode> what's after barcelona? boston? I'm sure we could do something for that
15:59:16 <PerfectChaos> I'm not sure we have much to talk about that's specific to this WG yet.
15:59:31 <serverascode> also, is anyone coming to the operators meetup in NYC in August?
15:59:38 <PerfectChaos> But potentially something on challenges unique to NFV ops or such could be on the cards for Boston.
15:59:49 <serverascode> 20 seconds left ha
15:59:59 <RandyLevensalor> Ok.  We could talk about the mission statement and goals of the WG.  The top use cases.
16:00:09 <serverascode> ah, I'm going to have to close off the meeting
16:00:35 <serverascode> thanks everyone for coming!
16:00:42 <serverascode> #endmeeting