17:04:53 #startmeeting servicevm-device-manager 17:04:53 Meeting started Wed Nov 19 17:04:53 2014 UTC and is due to finish in 60 minutes. The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:04:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:04:56 The meeting name has been set to 'servicevm_device_manager' 17:05:04 #topic Announcement 17:05:18 #link https://wiki.openstack.org/wiki/Meetings/ServiceVM agenda 17:05:46 neutron advanced service mid cycle is planned 17:06:34 #link https://etherpad.openstack.org/p/advanced-services-kilo-midcycle advsvc nid cycle 17:07:09 yamahata: is the location & logistics decided yet ? 17:07:14 neutron spec proposal deadline(SPD) and spec approval deadline(SAD) is Dec 8, Dec 15 17:07:48 SridharRamaswamy: According to the link, it's under planning. not fixed yet. 17:07:50 SridharRamaswamy: no, as a member of the "advanced service library" team we have NOT decided when/where the mid-cycle will be 17:07:55 hello all, sorry a bit late to join 17:08:10 yamahata: s3wong: okay, thanks 17:08:41 any other announcement? 17:08:54 Adv. servie library... does that mean we're like librarians then? 17:09:15 bobmel: at this point, this is the language used in the proposal :-) 17:09:28 for those following NFV subgroup .. it now renamed as TelcoWorkingGroup! 17:09:32 s3wong: I know. :-) 17:10:26 bobmel: as you know --- we are really dissecting the language used in markmcclain's email :-) 17:10:55 yamahata: something probably every member of the team has looked at: http://lists.openstack.org/pipermail/openstack-dev/2014-November/050961.html 17:11:29 #link http://lists.openstack.org/pipermail/openstack-dev/2014-November/050961.html neutron split proposal 17:11:55 the proposal of splitting out advanced services (all L4-7) from Neutron into an independent repo is sent out by markmcclain and mestery 17:11:59 s3wong: you want to make sure everyone reads it :) 17:12:02 Tacker is already split. fotunately or unfortunately. 17:12:23 s3wong: we are all dissecting that for sure.. particularly the "optional" part ! 17:12:56 hareeshp: TBH, I want people to respond to it on the ML --- just to get the clearest of clarity of what it really means 17:13:10 #action everyone make sure read/respond http://lists.openstack.org/pipermail/openstack-dev/2014-November/050961.html 17:13:49 Guys: there is a suggestion that we should have the proposal on gerrit such that we can ALL comment on. I think we should (as a team) suggest that also (it was suggested by armax in the first place) 17:14:22 #link https://review.openstack.org/#/c/134680/ Proposal for Neutron core and vendor code decomposition 17:15:54 armando uploaded his proposal to gerrit. 17:16:45 any announcement? 17:17:14 yamahata: I updated the tacker wiki with descrition of tacker 17:17:14 moving on... 17:17:30 yamahata: And SridharRamaswamy added use cases 17:17:34 bobmel: great 17:17:47 #topic Action Items from the last week 17:18:17 yes, time to go over the action items from last week :-) 17:18:47 I added the use-cases.. tried to pencil in target release and priority 17:18:56 please review when u get a chance 17:19:21 SridharRamaswamy: I think they look good 17:19:36 SridharRamaswamy: So far it looks good. 17:19:46 SridharRamaswamy: looks good 17:20:06 bobmel: yamahata: hareeshp: thanks! 17:20:44 bobmel: also fullfilled his action. 17:20:49 But I failed. 17:20:59 #action yamahata to move current Tacker spec to a Google doc and share with team 17:20:59 i did a first cut on the tacker dependencies here servicevm/dependencies 17:21:14 yamahata: You're forgiven :-) 17:21:24 hareeshp: in fact, you did it right after the last meeting --- talk about efficiency :-) 17:21:29 bobmel: :-) 17:21:48 s3wong: i have a tendency to forget :) 17:22:33 any other items left? 17:22:35 if any of find, anything was missed (now or future), please let me know and i will update 17:22:45 this things move very fast 17:22:46 bobmel, SridharRamaswamy: the wiki page looks very informative now. Thanks, guys! 17:23:05 Yeah, very useful now. 17:23:09 yeah, i like the Mission & Scope 17:23:21 btw.. any more wiki-gardening or are we done.. 17:23:30 +1 17:23:39 the bottom half of the page has lots of links.. 17:24:06 i can take a first cut at arranging some of that 17:24:16 hareeshp: cool. 17:24:33 #action hareeshp more wiki-gardening 17:24:37 hareeshp: great, that will be help 17:25:36 SridharRamaswamy, and other new team members: you may want to update the incubation page with your names on it: #link https://wiki.openstack.org/wiki/ServiceVM/Incubation 17:25:56 s3wong: sure, will do 17:27:17 #action SridharRamaswamy add name to https://wiki.openstack.org/wiki/ServiceVM/Incubation 17:27:27 any items? 17:27:50 move on 17:27:53 #topic spec/code review 17:28:16 I created a page of review tracking following ML2 style. 17:28:30 #link https://wiki.openstack.org/wiki/Tracking_ServiceVM_Reviews review tracking wiki 17:28:44 and added the link from the project page. 17:28:55 I hope it helps review 17:29:06 I'm open of tracking page. 17:29:30 I just followed ML2 and use wiki. but others may want to use etherpad or something else. 17:30:38 yamahata: wiki is fine, i'll help as much to review some of these 17:31:18 anyway we can revise the use of wiki after some experiment period. 17:31:30 do we have special review topic? 17:31:33 yamahata: I thought we still want to finalize on the workflow? 17:32:12 IMO the next significant milestone is to identify the boundary between plugin & tacker API. There was some confusion how / where this boundary lies. 17:32:17 anyone knows how this nfv.russelbryant.net is setup? looks cool 17:32:21 s3wong: Oh sure. 17:32:38 good way of tracking patches 17:33:42 hareeshp: well, russellb has russelbryant.net domain, it is just a matter on adding sub-domain for his own domain 17:34:25 hareeshp: just like you can easily have hareeshputhalath.net also :-) and you can then set up tacker.hareeshputhalath.net :-) 17:34:37 SridharRamaswamy: Do you have any documentation to start with? 17:34:42 ya, i meant the way he can selectively track patches 17:34:57 s3wong : ;) 17:35:04 hareeshp: I believe that is setting up filters on gerrit 17:35:05 hareeshp: i believe the NFVImpact tag is used to scrub gerritt 17:35:22 at this point, api spec. (which I'll convert to google doc tomorrow. top priority) 17:35:25 hareeshp: during the NFV meeting, they talked about adding a tag on all NFV related gerrit reviews 17:35:44 yamahata: yes, that would be a good platform to start the workflow discussion :-) 17:36:36 s3wong: yamahata: after the google doc .. lets plan for a webex conf call 17:37:08 SridharRamaswamy: +1 for webex 17:37:14 SridharRamaswamy: sure --- assuming the current spec isn't perfect already :-) 17:37:15 +1 17:37:52 #agreed plan webex meeting after the google doc spec 17:38:00 s3wong: i'm sure it is :) .. atleast the call will help the newbies like me to come upto speed ;) 17:38:32 +1 17:38:52 +1 17:39:30 SridharRamaswamy, yamahata: once the GDoc is out, we can give it a week or so for team-members to comment on it; then we should have the webex session to discuss 17:39:49 s3wong: +1 17:39:55 next week being Thanksgiving week for US team-members, I think it is perfect... NOT :-) 17:40:03 s3wong: +1, make sense 17:40:04 #action yamahata once converted api spec, announce it 17:40:11 s3wong: +1 17:40:40 we can poll webex schedule 17:40:49 yamahata: +1 17:41:08 #action yamahata create poll page for webex meeting 17:41:22 yamahata: +1 17:41:40 Cisco friends can help to schedule one ? 17:41:55 yes, i can do that 17:42:10 i really miss webex after moving :( 17:42:24 once the day and time is set, just let me know 17:42:58 SridharRamaswamy: yeah, please don't let yamahata do it -- I have a meeting with Intel folks once and they used SilverLight, what a disaster :-) 17:43:31 s3wong: SilverLight ? SridharRamaswamy running away for a mile 17:43:32 s3wong: +1. We all have troubles with SilverLight... 17:45:27 anything else to discuss? 17:45:36 #topic Open Discussion 17:45:49 yamahata: well, may be better than lotus sametime 17:46:26 * yamahata googling lotus sametime... 17:46:27 yamahata: the router vm plugin + agent, 17:46:49 do you think that will get into kilo? 17:47:13 bobmel: I'd like to. I expect the possibility is low. 17:47:25 bobmel: can u provide a link for that effort ? 17:47:56 is it #link https://review.openstack.org/#/c/105078/ ? 17:47:57 given the focus of Kilo is to pay tech debt 17:47:59 yamahata: will it be separate from mcafee router plugin? 17:48:19 bobmel: Yes. They are separated. 17:49:03 SridharRamaswamy: Yes. 17:49:13 #link https://review.openstack.org/#/c/105078/ L3 router: modular l3 router plugin, l3 plugin/agent for routervm 17:50:34 any other questions? topic? 17:52:18 seems none. 17:52:19 for the US folks, do you guys still want to have a meeting next week? 17:52:31 it is a day before Thanksgiving holiday 17:53:03 I will be in office, so I am OK to meet --- just want to know if the rest of the US team-members have other plans 17:53:28 i'm okay to meet 17:53:39 I'm fine with either way 17:53:51 I create schedule poll page 17:53:53 http://doodle.com/c4dbdpp7cnsiuu4k 17:53:59 cool 17:54:02 I just used time slot UTC1700 17:54:23 But not sure which time slot is preferable. If you have another time slot prefered, please ping me. 17:54:29 then I'll add the time slot 17:55:02 #link http://doodle.com/c4dbdpp7cnsiuu4k schedule poll for webex meeting 17:55:47 s3wong: how about you? do you want to have meeting next week or not? 17:56:07 yamahata: I am good. Let's have a meeting next week 17:56:36 s3wong: okay ,no objection to meet next week. 17:56:54 any other topic? 17:57:42 thank you everyone. 17:57:46 see you next week 17:57:50 thanks! 17:57:53 thanks and see you all next week 17:57:58 ok, bye 17:58:07 #endmeeting