14:00:24 #startmeeting telcowg 14:00:25 Meeting started Wed Sep 23 14:00:24 2015 UTC and is due to finish in 60 minutes. The chair is sgordon. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:29 #link https://etherpad.openstack.org/p/nfv-meeting-agenda 14:00:30 The meeting name has been set to 'telcowg' 14:00:32 #topic roll call 14:00:34 hola! 14:00:38 hello 14:00:39 hi 14:01:24 hi 14:01:43 #topic BGP use case 14:02:01 #info Still need a volunteer to take BGP use case as a "guinea pig" to turn into RFEs/backlog 14:02:12 (i have had a crack at the vIMS one, will get to that in a second) 14:02:57 #action sgordon to contact Mathieu directly 14:03:05 #topic vIMS usecase 14:03:12 #link https://bugs.launchpad.net/openstack-telcowg/+bug/1498922 14:03:13 Launchpad bug 1498922 in openstack-telcowg "Tracker: Virtual IMS Core" [Undecided,New] - Assigned to Stephen Gordon (sgordon) 14:03:18 #link https://review.openstack.org/#/c/224325/ 14:03:48 i took the vIMS use case and raised a Nova backlog spec for the affinity gap (N+k pools) - see the review link above 14:04:00 i know cloudon had already provided a comment on there but more reviews likely welcome 14:04:46 Steve, did you make a change a short time ago? Couldn't see any delta 14:05:08 i removed the WIP flag 14:05:24 ah, ok 14:06:59 ok 14:07:06 #topic Open Reviews 14:07:12 #link https://review.openstack.org/#/q/status:open+project:stackforge/telcowg-usecases,n,z 14:07:26 i will put aside those that have had -1s forever 14:07:42 i am going to make an attermpt to contact the authors again and then potentially abandon 14:07:42 sgordon: what's Monty's change for? 14:07:50 aveiga, great question! 14:07:58 secret infra stuff 14:08:02 I figured 14:08:05 Change ignore-errors to ignore_errors 14:08:05 Needed for coverage 4.0 14:08:09 in .coveragerc 14:08:17 which tbh i couldnt tell you what it does ;p 14:08:19 would be nice if he explained t he change... 14:08:32 I assume it's part of the "migrate stackforge" stuff 14:08:40 https://pypi.python.org/pypi/coverage/4.0a1 14:09:00 ah! that's more useful 14:09:01 i suspect it's broader than that 14:09:09 and is just that every project has this rc file 14:09:17 and thus has been hit with a patch if it uses the old syntax 14:09:28 https://review.openstack.org/#/q/owner:mordred%2540inaugust.com+status:open,n,z 14:09:37 seems to contain a lot of them 14:10:05 #link https://pypi.python.org/pypi/coverage/4.0a1 14:10:11 #link https://review.openstack.org/#/q/owner:mordred%2540inaugust.com+status:open,n,z 14:10:18 #link https://review.openstack.org/#/c/225904/ 14:10:53 #link https://review.openstack.org/#/c/199654/ 14:11:05 i can see aveiga just +2'd that template update so that is off the list 14:11:24 which leaves the outstanding review with no negative feedback.. 14:11:34 #info SBC review open with no -1/-2 14:11:36 #link https://review.openstack.org/#/c/176301/ 14:11:55 it has +2 from myself and DaSchab 14:12:02 so at this point can actually be approved 14:12:13 SBC is okay, but maybe needs some +1 14:12:25 yeah 14:12:41 the other part is somebody has to be ready to then pick it apart and try turn into RFEs/backlog specs 14:12:42 yes, I was hoping to get some internal feedback on that from my voice team before I +w it 14:12:53 yeah, makes sense 14:12:59 i would be happy to see some more comments on it 14:13:12 yup, comments welcome 14:13:23 #info wait for some further comments on the SBC use case to confirm it is on the right path 14:13:36 #topic Meeting schedule 14:13:55 so this has been an ongoing issue, but last week the *only* person there for the later meeting time slot was myself 14:14:08 so at this point im looking to consolidate on this time slot each week 14:14:30 makes sense 14:14:34 +1 14:15:02 #action sgordon to mail list and update wiki listing early slot as the only meeting time going forward 14:16:20 one last thing that i had failed to put in the etherpad but just remembered... 14:16:36 #topic productwg - Capacity/Quota Management User Stories 14:16:53 this actually came up in the product working group but thought might be relevant to some people here 14:17:19 one of the user stories we have been asked to try and nail down is around capacity and quota management (there is a separate but related task around vm lifecycle management) 14:17:32 just wondering if anyone here would be interested in contributing to that discussion 14:18:16 that's pretty vague 14:18:43 it is indeed 14:18:51 hence the need to define it ;) 14:19:00 #link https://github.com/openstack/openstack-user-stories/blob/master/user-stories/draft/capacity_management.rst 14:19:35 tl;dr sounds a lot like reservations 14:19:49 ah 14:20:13 so they're really looking for guaranteed availability of a quota? 14:20:20 seems that way yeah 14:20:34 i mention it here because i know this was on the original ETSI NFV gap analysis 14:20:41 wondering if anyone has concrete use case info 14:20:48 that's going to be extremely tricky, especially considering that some VMs may have affinity/anti-affinity hints 14:20:51 seems broader than that.. for example the ref to supporting ephe#meral VMs 14:21:29 aveiga, yeah - for now we're just focused on the use case, i dont debate that it's non-trivial to solve 14:24:55 ok 14:25:03 let's call it there for now 14:25:18 In OPNFV we have a project which is trying to also address similar resource management requests. 14:25:21 i will keep reporting back to this group on the product wg stuff to see if it becomes clearer/more relevant for you 14:25:35 margaret__, this isn't NFV specific, it's part of the product working group 14:26:05 I know - but just to let you know we are thinking of addressing parts of it from an NFV perspective in OPNFV 14:26:23 We get into versions of NIC, dpdk, ovs... 14:26:52 cpu pinning... 14:27:08 that seems to be putting the horse ahead of the cart when there is no designed capability for reserving capacity period 14:27:12 even at the basic levels 14:27:55 * sgordon mixes up his metaphor nicely 14:27:56 well we can help shape the blueprint as we talk through the whole perspective.. 14:28:07 yeah thats really where i am going 14:28:22 is that requirements project engaging with the openstack community (e.g. product wg) on this 14:28:28 or in a vacuum? 14:28:58 I'm not sure. I can ask our tsc on this - chris price 14:29:12 Is there going to be a Telco WG meeting in Tokyo? 14:29:27 I was suggesting to the OPNFV crowd that we should attend. 14:29:45 every time i hear "we are thinking of addressing parts of it from an NFV perspective in OPNFV" what I think is "we are making up our own way of doing things irrespective of consulting the relevant community": 14:30:09 +1 14:30:22 the concern being that if e.g. the product wg comes up with requirements and circulates them in the absence of opnfv engagement then what opnfv requires wont actually be there 14:30:49 yes we have been given a 40 min slot 14:30:51 More of a set of telcom folks discussing what our real needs are - vs each company coming up with their view of needs and they are all over the place. 14:30:55 i believe 2pm on the tuesday 14:31:20 #link http://mitakadesignsummit.sched.org/event/b060647ccd40868b30ef2ab5cab76fda#.VgK3tbOf7lY 14:31:44 ok - there is a BOF slot that OPNFV took and I don't know the time - but it is Tuesday. 14:33:09 #action sgordon to email opnfv list highlighting that someone from the promise project probably needs to be engaged in the product wg discussion around capacity management 14:34:34 ok I just sent email to chris on overall the different OPNFV projects need to engage with the product WG on the different topics 14:34:51 yeahhh 14:35:04 i am only highlighting capacity management as that is the one i am most directly engaged with 14:35:12 there are a couple of others that are likely also of interest 14:35:31 #link https://wiki.openstack.org/wiki/ProductTeam 14:35:34 yes I know. which is why I sent it to chris as chair. 14:35:38 #link https://docs.google.com/spreadsheets/d/1d1ZKuZ6gsiG6CXXrfONBwAGGHA8SYINbYC9BSPBKllI/edit#gid=1956934401 14:37:00 margaret__, full list is in that google doc 14:37:19 there are drafts for some of them here: 14:37:24 #link https://github.com/openstack/openstack-user-stories/tree/master/user-stories/draft 14:38:08 ok thanks. 14:39:49 alright 14:39:53 thanks all for your time 14:39:56 #endmeeting