05:02:37 <yamahata> #startmeeting neutron/servicevm
05:02:38 <openstack> Meeting started Tue Mar 25 05:02:37 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.
05:02:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
05:02:41 <openstack> The meeting name has been set to 'neutron_servicevm'
05:03:15 <yamahata> hello. Does the new time slot work for you?
05:03:58 <s3wong> I believe people from US East Coast made a comment on the ML
05:04:29 <yamahata> very sorry for those.
05:05:19 <yamahata> #topic current-status
05:06:06 <yamahata> I summarized blueprints, patches at the page
05:06:14 <yamahata> #link https://wiki.openstack.org/wiki/Meetings/ServiceVM
05:06:47 <yamahata> No patch was updated since the last week.
05:07:17 <s3wong> yamahata: yes, I am still in the middle of reviewing the APIs; sorry for the delay
05:07:29 <yamahata> s3wong: no problem.
05:07:54 <yamahata> any questions on design/patches?
05:08:15 <yamahata> I'm going to update the patches this week or the next week.
05:08:54 <yamahata> It will include drivers/guest agent for lbaas
05:09:32 <s3wong> yamahata: good - it is good to see a sample service using this framework
05:10:10 <yamahata> s3wong: it just run haproxy in guest vm instead of namespace in network-node.
05:10:57 <yamahata> openstack RPC needs to be proxyied into tenant network from openstack management network
05:11:01 <s3wong> yamahata: is there going to be a pre-package image?
05:11:27 <yamahata> s3wong: hopefully. I'm working on it right now.
05:12:07 <yamahata> image + devstack patch
05:12:39 <s3wong> yamahata: interesting. LBaaS haproxy installation process was simply apt-get install haproxy on host OS
05:13:07 <s3wong> so now for service VM, we need to specify the image location?
05:13:55 <yamahata> s3wong: yes. At first we need register images as usual. And then register those ids for image to neutron.
05:14:37 <yamahata> The framework uses nova-client to boot VM with a given image
05:15:20 <s3wong> yamahata: is the image id registeration to Neutron automatically or manual (by tenants?)?
05:15:25 <yamahata> In theory, same work flow can be applied for other service like router, firewall
05:15:48 <yamahata> s3wong: It's manual at the moment.
05:16:35 <s3wong> yamahata: OK
05:17:22 <yamahata> s3wong: automation is desirable. But not sure it should be in this framework or by other external tool.
05:18:13 <s3wong> yamahata: sure, I am fine with it for initial implementation
05:19:16 <yamahata> any other questions?
05:19:50 <s3wong> yamahata: will look into the code further
05:19:56 <yamahata> I see.
05:20:09 <yamahata> #open discussion
05:20:47 <yamahata> other subteam are concerned about servicevm. advanced-service-requirement and group-policy
05:21:09 <yamahata> It's important to cooperate with them
05:21:18 <s3wong> yamahata: I am in both advanced-service and group-policy team - what is the primary concern you hear about?
05:21:37 <yamahata> s3wong: nothing special at the moment.
05:21:43 <s3wong> in group-policy we haven't really gotten into service yet
05:21:58 <yamahata> Unfortunately I can't attend their IRC meeting due to its time slots.
05:22:00 <s3wong> and in advanced service we had been discussing flavor and service context
05:22:23 <yamahata> I'm following their discussion via logs.
05:22:34 <s3wong> yamahata: I was going to say - even for a West coast person like me, it is now 10:22pm
05:22:55 <s3wong> yamahata: so you may find it difficult for others in US to join this meeting actively
05:23:19 <yamahata> s3wong: Right. such thing is inevitable.
05:24:22 <yamahata> So when there is a topic that is important for servicevm, please let me know. then I'll try to attend.
05:24:37 <s3wong> yamahata: sure
05:25:09 <yamahata> another concern is router vm patch
05:25:30 <s3wong> yamahata: please also let me know if there is anything you need from either group-policy side or advanced service side (which I would imagine you need things from advanced service side like service insertion via service context)
05:25:30 <yamahata> #link https://blueprints.launchpad.net/neutron/+spec/cisco-config-agent
05:25:48 <yamahata> s3wong: thanks, will do.
05:26:00 <yamahata> #link https://blueprints.launchpad.net/neutron/+spec/cisco-routing-service-vm
05:26:53 <yamahata> Their patches essentially do similar thing. So the patches(theirs and mine) should converge somehow
05:27:07 <yamahata> at some point
05:27:09 <s3wong> yamahata: do you plan to bundle L3 agent into a service VM too?
05:27:24 <yamahata> s3wong: That's the plan
05:27:51 <yamahata> s3wong: no, I mean lbaas-agent to bundle.
05:28:15 <yamahata> s3wong: for l3-agent, it's another story.
05:28:16 <s3wong> yamahata: yeah, who wants l3-agent :-)
05:29:11 <yamahata> s3wong: the planned image would include lbaas-agent with haproxy
05:29:38 <s3wong> yamahata: makes sense
05:30:15 <yamahata> hopefully some startup scripts.
05:31:23 <s3wong> yamahata: yeah, if it is meant for haproxy only image, some components should be spawned either in inittab or one of the Sxx scripts
05:33:47 <yamahata> okay. any topic to discuss?
05:34:32 <s3wong> yamahata: I am good
05:35:15 <yamahata> thanks. Since I plan to post new patches, let's have the meeting the next week.
05:35:35 <yamahata> #endmeeting