15:00:13 <serverascode> #startmeeting operators_telco_nfv
15:00:14 <openstack> Meeting started Wed Jul 27 15:00:13 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:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:18 <openstack> The meeting name has been set to 'operators_telco_nfv'
15:00:23 <serverascode> #topic roll call
15:00:35 <serverascode> hi, anyone here for the ops telecom/nfv meeting? :)
15:01:01 <ulik> #info uli
15:01:19 <serverascode> hi ulik
15:01:46 <ulik> Hi
15:02:18 <serverascode> we'll give it a couple min to see if anyone else shows up
15:02:44 <ulik> ok
15:03:35 <ulik> I have another meeting in parallel, so I hope my replies will not be too slow...
15:03:43 <serverascode> ok no worries
15:05:05 <serverascode> anyone else lurking around for this meeting?
15:05:43 <wznoinsk> hi
15:06:02 <serverascode> hi wznoinsk :)
15:06:20 <wznoinsk> I'm only passing by... I'm a dev/CI ops here at Intel, what's the main goal of the WG?
15:06:55 <serverascode> #link https://wiki.openstack.org/wiki/Ops-telecom-nfv
15:07:01 <serverascode> I started to put together the wiki page
15:07:08 <serverascode> we have been working on a mission statement
15:07:17 <serverascode> it's still early in the groups formation though
15:07:40 <serverascode> but in general, we're here to help openstack operators who are running telelcom/NFV related clouds
15:08:02 <wznoinsk> ok, is ops and wg in the name you'll be limiting your work to less development, more benchmarking, stress testing etc?
15:08:32 <serverascode> yeah, likely not much development work, other than perhaps commiting operational tools to osops
15:09:23 <serverascode> #topic general info
15:09:51 <serverascode> I'm just going to do a bit of general info regarding the last couple weeks, then move on to open discussion
15:10:03 <serverascode> INFO: A wiki page has been created
15:10:12 <serverascode> #info a wiki page has been created https://wiki.openstack.org/wiki/Ops-telecom-nfv
15:11:06 <ulik> Maybe we can link from the wiki also to the opnfv wiki on openstack relation
15:11:20 <serverascode> #info It seems like we will be a functional team under the user commitee http://lists.openstack.org/pipermail/user-committee/2016-July/001144.html
15:11:44 <serverascode> I'm still working on figuring out what the user committee process is, but the above email seems a good sign
15:12:00 <serverascode> ulik: ok I can add that
15:12:24 <serverascode> #info We have a page for mid to long term project ideas: https://etherpad.openstack.org/p/ops-telecom-nfv-project-ideas
15:12:29 <ulik> I was getting the #link.... https://wiki.opnfv.org/display/COM/OpenStack
15:13:11 <serverascode> #info openstack ops midcycle is in NYC at the tail end of august https://opsmidcyclenyc2016.eventbrite.com
15:13:15 <ulik> I have a question to the wording "project ideas"
15:13:35 <ulik> What kind of project ideas do you think of?
15:14:08 <serverascode> well, I'm modelling it off of the large deployments team
15:14:21 <serverascode> essentially they pick a project to work on over a certain period of time
15:14:41 <serverascode> something they can shepherd through the openstack ecosystem
15:14:51 <serverascode> for example they worked on the "just get me a network" idea
15:15:05 <serverascode> and now changes have been made in neutron to allow that concept
15:15:21 <ulik> Could a requirement / use case be a project in that way?
15:15:27 <serverascode> yeah for sure
15:16:03 <ulik> So we could pick one of the OPNFV requirements that don't yet progress and try to do such a project from it?
15:16:15 <serverascode> yup
15:17:55 <serverascode> if you have any projects or requirements, just put them into that page and we can figure out which one we'd like to work on over a mid to long term timeframe
15:18:05 <ulik> So some options would be on the https://wiki.opnfv.org/display/COM/OpenStack already listed. We need to pick one - one where there is no BP yet.
15:18:13 <ulik> I need to check....
15:20:25 <serverascode> #topic open discussion
15:20:52 <serverascode> given there is only 3 of us today, I'll put it into open discussion now :)
15:20:56 <wznoinsk> 1. a nit, is it telco not telecom now?
15:20:56 <ulik> you said in beginning:
15:22:05 <serverascode> wznoinsk: I was asked by the foundation to use telecom, but it's not reflected everywhere yet
15:22:23 <serverascode> so we started out with telco and are now working to change it to telecom
15:22:41 <serverascode> also we started out using the term "working group" but I believe we are actually a "functional team"
15:22:50 <serverascode> so there is some naming to fix :)
15:23:25 <wznoinsk> 2. what's the difference between this and TelcoWG which I think was quite close to ProductWG as well?
15:23:39 <serverascode> right, good question
15:23:51 <serverascode> this is an openstack operators group
15:24:12 <serverascode> so it's specifically for people who run openstack clouds, be it in test or production
15:24:31 <serverascode> the telcowg, as far as I know, mostly around defining telecom/NFV user stories
15:24:41 <ulik> you said "we're here to help openstack operators who are running telelcom/NFV related clouds". Do you know such ops?
15:25:02 <wznoinsk> if you're only operators (hence no core developers/reviewers) the only way to influence the projects roadmap is thru TC/UC right?
15:25:44 <serverascode> ulik: I am myself one of those, and I know a couple others. I believe there will be a session at the NYC meetup with some telecom ops, I hope anyways
15:26:00 <wznoinsk> serverascode: telcoWG to define user stories and help to drive them thru OS AFAIK, this groups is kind of same (or I'm missing some subtle differences)
15:26:41 <ulik> I think the telcoWG is rather dormant
15:26:47 <serverascode> wznoinsk: yeah I think it might be subtle differences
15:27:03 <serverascode> the telcowg actually felt they completed their goals and closed the wg
15:27:07 <wznoinsk> ulik: possibly
15:27:15 <serverascode> technically wgs are supposed to be short term things
15:27:22 <ulik> so it is not dormant but terminated?
15:27:44 <serverascode> I believe so yup
15:28:21 <serverascode> #link: https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit
15:28:40 <serverascode> we looked at that doc last meeting, but it defines a few things like working groups, functional teams, etc
15:29:02 <wznoinsk> serverascode: yes technically WG wouldn't be a Project Team or a project  Team but some 'temporary' solutions are the most permanent ones :-) http://eavesdrop.openstack.org/meetings/log_wg/
15:29:33 <serverascode> for sure
15:30:23 <serverascode> basically as someone who operates telecom/nfv clouds I'm just kinda looking to find some peers to discuss things with :)
15:30:36 <serverascode> maybe do some cool stuff
15:30:51 <serverascode> no more no less :)
15:31:33 <serverascode> any other thoughts/questions/comments?
15:31:42 <wznoinsk> sure, if you can get enough of ops and their properly defined use cases and wishlists that could be even more - i.e.: NFV flavor of ProductWG?
15:31:45 <ulik> OK. So you expect some discussion topics coming from those ops?
15:31:50 <ulik> would be great!
15:32:06 <serverascode> I hope so
15:32:17 <ulik> Do you have a personal wish list?
15:32:26 <serverascode> I did put a couple of items into that page
15:32:33 <serverascode> first, celiometer scaling
15:32:41 <serverascode> second, perhaps programmable provider netowrks
15:32:49 <serverascode> which is a OPNFV netready related item
15:32:57 <serverascode> those were my only two idesa
15:33:01 <serverascode> *ideas
15:33:03 <serverascode> so far
15:33:05 <wznoinsk> bear in mind you'd need a proper backing of the ideas (ideally with numbers, company names) for TC/UC to take them into consideration into main upstream
15:33:57 <serverascode> wznoinsk: right. I definitely suggest looking at what the large deployments team did around "just get me a network"
15:34:07 <serverascode> they did manage to shepherd some changes over time
15:34:17 <wznoinsk> if you could have a kind of polling/voting system from ops, kind of survey maybe to show interest and ideas that could make ops voice heard better
15:34:53 <serverascode> ok, interesting idea
15:35:24 <wznoinsk> I mean, you need companies, customers, numbers speak for themselves before UC/TC will trust in this team's own suggestions/opinions
15:35:29 <serverascode> #idea some kind of polling or voting system for telecom/nfv openstack ops
15:36:26 <ulik> I think some of those ideas can also have some push by OPNFV.
15:36:44 <serverascode> I don't think uc or tc approval is required for everything though, there are lots of ways to affect change in openstack
15:37:28 <ulik> Yes. OPNFV in some cases came with developers who did the work.
15:38:04 <ulik> but when we didn't have those, it just needed waiting...
15:38:06 <serverascode> sometimes all it takes is showing up at a midcycle :)
15:38:28 <ulik> I've not been at a midcycle yet.
15:39:33 <serverascode> most projects in openstack have a midcycle event
15:39:39 <ulik> I think I will ask some of our OPNFV guys who had pushed things whether they have done that via midcycles.
15:41:04 <serverascode> ok anything else?
15:41:25 <serverascode> oh I should mention openstack east is in NYC also, just before the ops meetup
15:41:33 <serverascode> #link http://www.openstackeast.com/
15:41:43 <serverascode> #link https://opsmidcyclenyc2016.eventbrite.com
15:42:03 <serverascode> also the OPNFV hackfest is in Toronto just before the ops meetup
15:42:11 <ulik> can you help my ignorance and point me to every info about the ops meetup?
15:42:12 <serverascode> I'm planning on going to that on my way to NYC
15:42:55 <serverascode> #link https://etherpad.openstack.org/p/NYC-ops-meetup
15:43:04 <ulik> .. or necessary midcycle
15:43:10 <serverascode> ^^ that's the scheduling brainstorm page
15:43:37 <serverascode> that's about all I have, the event registration page and the etherpad schedule brainstorm
15:44:26 <ulik> midcycles are per project, right? Are they all in one place?
15:44:41 <serverascode> right, typically per project
15:44:50 <serverascode> they are self-organized by the team and can be anywhere
15:44:59 <serverascode> some have remote capabilities, most don't
15:45:21 <serverascode> I don't think they are usually co-located with other midcycles
15:47:39 <wznoinsk> I won't be able to attend midcycle(s) but I'll be tuning into this WG, mainly to hear what ops/users want to see to be tested around NFV features (if Intel NFV CI doesn't cover it yet) :-)
15:48:06 <ulik> ok. I am getting a better picture. Thanks
15:48:51 <serverascode> ulik: if you are on the openstack ops mailing list there have been a couple of emails on it
15:49:00 <serverascode> but they mostly just point to the links I entered here
15:49:50 <serverascode> wznoinsk: cool, thanks. Is there a page that describes a bit about hte intel nfv ci?
15:49:52 <ulik> I was not reading the mails without the telecomnfv tag.
15:51:34 <serverascode> ok, well unless there is anything else, I will prob end the meeting
15:51:50 <serverascode> thanks wznoinsk and ulik for coming by :) much appreciated
15:52:13 <serverascode> ulik if you have any other questions on the ops midcycle just let me know
15:52:18 <ulik> I got good input for the next 2 weeks untill the next one....
15:52:38 <serverascode> awesome :)
15:52:42 <serverascode> #endmeeting