19:00:18 #startmeeting telcowg 19:00:20 Meeting started Wed Apr 1 19:00:18 2015 UTC and is due to finish in 60 minutes. The chair is sgordon. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:23 The meeting name has been set to 'telcowg' 19:00:24 #link https://etherpad.openstack.org/p/nfv-meeting-agenda 19:00:29 #topic roll call 19:00:35 hello 19:00:38 hi 19:00:42 hi 19:00:59 hopefully didn't throw too many people for a curveball with the meeting time 19:01:36 #topic AIs from last week 19:01:48 ok we had kind of a laundry list of things here 19:02:32 im going to start with the ones where i found something happened and get to the others ;) 19:02:38 #info mkoderer and/or vks were to convert service chaining use case to RST 19:02:42 #link https://review.openstack.org/#/c/169201/ 19:02:59 actually submitted by ralfT in the end :) 19:03:46 #info sgordon was to add user stories/personas section to the template 19:04:04 #link https://review.openstack.org/#/c/169871/ 19:04:18 that covers only the user story aspect 19:04:26 I've added a comment on 19:04:26 personas i had somewhat of an epiphany on 19:04:43 in that there is already an openstack personas effort 19:04:58 i am wondering if we shouldnt just add needed personas to that and reference as needed 19:05:00 #link https://wiki.openstack.org/wiki/Personas 19:05:24 makes sense 19:05:31 +1 19:05:49 #info Feed personas to existing personas effort as/when needed 19:06:03 i see dcw snuck in :) 19:06:13 #info dcw was to draft SIP load-balancing use-case for wiki/etherpad initially, will need assistance with git submission 19:06:27 dcw, were you able to make any progress with this or need assistance? 19:06:47 i did not have a chance to look into this yet 19:07:18 will make a go of it on friday 19:07:30 ok np, i will just carry it over 19:07:31 if i get stuck will let you know 19:07:39 #action dcw to draft SIP load-balancing use-case for wiki/etherpad initially, will need assistance with git submission 19:08:02 #action sgordon to convert "access to physical network resources" to RST 19:08:13 * sgordon was naughty and did not complete his homework ^ 19:08:31 no problem. as I told you.. may colleague will do it. 19:08:37 #action cloudon to convert SBC to RST 19:08:45 cant see cloudon this week so carrying that over as well 19:08:45 he is the author of the use case 19:08:57 and same with this one: 19:09:03 #action matrohon to convert VPN Instantiation to RST 19:09:12 so still a fair bit of conversion to do 19:09:20 #link https://review.openstack.org/#/q/project:stackforge/telcowg-usecases+status:open,n,z 19:09:44 at the moment there are the four open reviews, one of which is just the template update i linked earlier 19:09:55 i need to update the vIMS submission to reflect feedback 19:10:18 i guess my question to the group having worked a few into the system now is do we think the template/process is ok? 19:10:22 (so far at least) 19:10:58 i have had positive feedback in some other circles like the win the enterprise group and opnfv with regards to potentially picking up a similar format 19:11:09 but still suspect we can fine tune 19:11:45 its good for review and minor comments, but how should we deal when a discussion comes up? 19:12:05 mailing list or irc? 19:12:17 now that the service chaining submission is up i bet we're about to find out 19:12:22 i suspect mailing list 19:12:26 given the diverse nature of the group 19:12:30 DaSchab: likely both, but better to use the ML 19:12:35 and also that some will require broader feedback 19:13:02 mail is good to reach all people 19:13:04 e.g. i could see discussion's coming up about how a given use case does or doesnt intersect with existing functionality etc 19:13:41 irc is good for the smaller stuff 19:13:43 sgordon: that's the point, though. gaps don't mean complete holes. Sometimes there's overlap 19:13:49 sure 19:14:09 just in terms of i dont claim to be a heat expert, for example 19:14:20 and im not sure anyone else in the group necessarily is either 19:14:31 yea, we're going to need to solicit larger feedback for many of these 19:14:43 +1 19:14:52 that is where the M/L is definitely the right venue 19:15:51 <[c]afeine> How can one become an *excellent* progrmmer? (advices). 19:16:16 there's no mention of a ML on the wiki 19:16:27 dcw, there is no special ML 19:16:38 openstack-dev and openstack-operators 19:16:45 dcw: we'll need to tag the topic with perceived relevant labels 19:16:57 i.e. [heat][neutron][nova] 19:17:06 understood 19:17:09 though some might just be [all] 19:17:29 i will update the page to make that clearer 19:18:25 #action sgordon to update wiki to make IRC/ML locations clear 19:19:41 DaSchab, did we answer your question 19:19:44 or just add confusion :) 19:20:05 everything is clear so far 19:20:06 a few hints will help... 19:21:59 ralfT, i think in many cases it's easier to ask as we go 19:22:16 there are no stupid questions etc. :) 19:23:05 yes ;-) 19:23:13 #link https://wiki.openstack.org/wiki/TelcoWorkingGroup#Communication 19:23:19 dcw, ^ 19:23:38 hopefully that helps 19:23:40 wow, realtime updates 19:24:26 +1 19:24:28 i was actually surprised we didnt have the irc bit there 19:24:36 must have lost it in one of the page restructures 19:25:13 sgordon: maybe we should decide to use [Telco] or [NFV] 19:25:19 DaSchab, yeahhhh 19:25:26 i have been using both since we started off with NFV 19:25:34 me too 19:25:50 we could also make it more explicitly [telcowg] 19:26:05 to align with what we are trying to do with everything else 19:26:18 +1 19:26:38 i think to have it formally defined as a tag in mailman i have to ask infra 19:26:53 but basically then i think i just send an email with some notice and we stop using the old tags 19:27:50 my preference is [telcowg] 19:29:19 ok 19:29:28 #action sgordon to work out what to do to move to using telcowg ML tag 19:29:39 does anyone have anything else they would like to discuss? 19:29:43 thanks all for attending bytw 19:29:52 much better attendance than we were getting at 2200 UTC 19:30:53 sgordon: is it time to start discussing agendas for Vancouver? 19:31:02 yeS! 19:31:06 yes 19:31:06 good reminder 19:31:36 yeah, it's coming up 19:31:38 now i just need to find the link again 19:31:50 #link http://lists.openstack.org/pipermail/openstack-operators/2015-March/006607.html 19:31:58 #link https://etherpad.openstack.org/p/YVR-ops-meetup 19:32:57 so telco working group is already suggested as a working session 19:33:11 the key to acceptance will be coming up with a defined agenda for this session 19:33:21 agenda is probably the wrong word 19:33:23 but goals/aims 19:34:17 sgordon: I strongly suggest a more defined listing 19:34:55 i strongly agree 19:35:05 i didnt actually add that one unless i did it in one of my drunken stupors 19:35:25 was holding off until had details (i did just put my name down the bottom to volunteer to facilitate tho) 19:35:46 #info Need a more defined listing for Vancouver summit session 19:36:27 i would also highlight given potential overlap that there is going to be some sort of OPNFV "thing" on the monday 19:36:29 I suppose I could volunteer as well 19:36:35 i am told in the form of space in the design summit area 19:36:46 i am still trying to establish what the goals for that will be 19:36:56 (this would be on the monday) 19:36:59 sgordon: are you liaising for them? 19:37:05 it would be good to get more concrete info 19:37:10 yeah i actually have a call at 5 EDT to try sort through this 19:37:25 ok, thanks 19:37:33 i had a preliminary discussion with someone from the linux foundation about it a week or two ago to explain the context of why this group exists etc 19:37:42 ouch 19:37:48 and also explain some more general "how summit works" stuff 19:38:21 for now just highlighting it because it might be of interest 19:38:28 as i get more clarity will broadcast it 19:39:09 i think we should focus on improving that ops summit proposal for next weeks meeting 19:39:31 +1 19:39:52 not sure exactly what tom's timeline for sorting out scheduling is but he has a lot of submissions in there already 19:39:58 i would also add if you plan on attending 19:40:11 please add your +1 so we have an idea of who is likely to attend 19:40:27 https://etherpad.openstack.org/p/YVR-ops-meetup <-- currently line 91 19:40:35 under "Session Ideas - Working Groups" 19:40:39 +1 19:41:45 ok 19:41:53 i think that is probably close to a wrap 19:41:59 thanks aveiga for the reminder about summit 19:42:10 i had been thinking about it when i saw the thread earlier but it slipped my mind 19:42:12 np, thanks for running the meeting as usual, sgordon 19:42:21 #endmeeting