14:06:16 <tbachman> #startmeeting opnfv-sfc-weekly
14:06:16 <collabot> Meeting started Wed Jul  8 14:06:16 2015 UTC.  The chair is tbachman. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:16 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:06:16 <collabot> The meeting name has been set to 'opnfv_sfc_weekly'
14:06:21 <tbachman> #chair ebrjohn
14:06:21 <collabot> Current chairs: ebrjohn tbachman
14:06:24 <lmcdasm> #info Daniel Smith
14:06:27 <tbachman> #info tbachman
14:06:42 <tbachman> #topic Agenda
14:06:45 <bouthors> #info Nicolas Bouthors
14:06:49 <DaveD_> #info Dave Dolson
14:07:08 <paulq> #info Paul Quinn
14:07:16 * tbachman waves to paulq
14:07:33 <ebrjohn> #link https://wiki.opnfv.org/service_function_chaining
14:07:35 <paulq> talk and type: we are getting old ;)
14:08:44 <tbachman> #info ebrjohn says we’re skipping the clustering action item for now
14:09:40 <tbachman> #info paulq asks why opnfv doesn’t use specific mailing lists
14:10:06 <tbachman> #info ebrjohn says that opnfv early on decided to have a single list and use filters
14:10:52 <tbachman> #info bryan_att says that you can set filters using mailman
14:11:32 <tbachman> #info ebrjohn says the agenda is carrying on with the slides that cover initializing OPNFV and SFC, and openstack orchestration
14:11:51 <tbachman> #topic OPNFV SFC initialization
14:12:24 <tbachman> looks like topics might not work with this meetbot :(
14:12:29 <ebrjohn> #link https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit?usp=sharing
14:12:30 * tbachman isn’t seeing them change
14:12:44 <tbachman> ebrjohn: don’t sweat it
14:12:47 <tbachman> #undo
14:12:47 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2bdee50>
14:13:00 <tbachman> #link https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit?usp=sharing Slides for OPNFV/SFC
14:13:11 <tbachman> (providing some context for the link for the minutes)
14:13:15 <tbachman> ebrjohn: we can see it
14:14:10 <tbachman> #info ebrjohn says he added the GBP endpoints, added SFC/OpenStack coordinator
14:14:42 <tbachman> #info paulq says the GBP depiction might be a bit off — wrt to the classifier; he’ll collect his feedback and provide it in an email to ebrjohn
14:15:20 <tbachman> bryan_att: asks if the coordinator is outside ODL, or something else
14:15:22 <tbachman> oops
14:15:34 <tbachman> #info bryan_att asks if the coordinator is outside ODL, or something else
14:15:48 <paulq> #info tbachman says oops
14:15:54 <tbachman> paulq: nice ;)
14:15:55 <tbachman> lol
14:16:32 <tbachman> #info ebrjohn says there’s a configuration hole: SFC needs to know information about the VMs (e.g. addressing); this is one of the functions of the coordinator
14:17:01 <tbachman> #info daniel notes that most of the info is available from the neutron DB
14:17:10 * tbachman didn’t know daniel’s nick
14:17:21 <lmcdasm> *lmcdasm
14:17:52 <tbachman> lmcdasm: thx!
14:17:54 <tbachman> #undo
14:17:54 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2be69d0>
14:18:05 <tbachman> #info lmcdasm notes that most of the info is available from the neutron DB
14:20:13 <tbachman> #info lmcdasm says if you want to know the port definition, then you can query neutron for this information; one of the catch-22’s is if the VNF or Service Function is set up as a VM, then neutron may not be aware; otherwise, this is a simple query to neutron
14:20:29 <tbachman> #info paulq asks if you can find the relationship between a VM (e.g. a firewall) and the OVS instance it’s connected to
14:21:03 <tbachman> #info lmcdasm says nova fires up the VM, neutron attaches the port; openstack isn’t aware of what the VM is doing (e.g. firewall); but you can associate the port with the vritual NIC for that VM
14:21:48 <tbachman> #info lmcdasm says you can’t have 2 ports on the same subnet, so you know which port is connected to a given subnet
14:22:19 <tbachman> #info rapenno says from an ODL provisioning perspective, you create a Service Function, and then goes to an orchestrator to request a VM to get the information
14:23:20 <tbachman> #info bryan_att says he’d like to hear more information on how the life cycle works
14:23:44 <tbachman> #info paulq says he’d like to get a bullet-point list and API pointers so we can see how this looks and works
14:24:58 <tbachman> #info lmcdasm says his initial understanding was that it was a pull model from openstack; this new model suggests that ODL is interacting with OpenStack to create VMs for things (e.g. firewalls)
14:25:36 <tbachman> #info ebrjohn says we should create two mini-groups: 1 to work on the coordinator, another to work on a setup
14:26:08 <tbachman> #info ebrjohn says there are two use cases: reactive approach and proactive approach; the first is reacting to VM creation, the second creates VMs
14:26:27 <tbachman> #info lmcdasm is in favor of picking one approach or the other, rather than both
14:28:52 <tbachman> #info ebrjohn says we need work on both the coordinator, and work on the piece that brings everything up
14:29:14 <tbachman> #info lmcdasm says that we have everything with the exception of the coordinator today
14:29:39 <bryan_att> I would like to help in the group for the "coordinator" analysis. This is part of what I had planned for the OPNFV Hackfest... To figure out and demo how to coordinate function chaining info between openstack and ODL, e.g. using a python program which uses the NB APIs of Openstack and ODL
14:29:59 <tbachman> #info paulq asks what is a service function and what is it’s relation to OVS
14:30:30 <tbachman> #info lmcdasm says a service function is something an application does; the relation between an SF and OVS is that OVS is the fabric that the SF runs on
14:30:57 <tbachman> #info ebrjohn says we need a mapping for a service function type (e.g. FW) to actual glance images
14:31:25 <tbachman> #info bryan_att says we should take that as part of the coordinator discussion — he’d like to address this at the upcoming hackfest/summit
14:32:45 <tbachman> #info bryan_att says the reactive and proactive approaches should be part of the bullet-list analysis
14:32:57 <tbachman> #info lmcdasm says something missing is what do you want to run with those applications
14:33:59 <tbachman> #info lmcdasm says we should start simple — pick to things that you’d like to chain today and see how to make that work
14:34:01 <bryan_att> As noted VNFD is the place where the metadata about "what type of function this VM provides" would live
14:34:08 <tbachman> #info paulq says firewall and DPI would be a good first start
14:34:29 <tbachman> #info bryan_att says as noted VNFD is the place where the metadata about “what type of function this VM provides” would live
14:35:28 <tbachman> #info lmcdasm says the first thing a mini-group should do is define the specifics — what is the VM, what is the glance image, etc.
14:36:04 <bryan_att> The purpose of each vNIC on a VM also needs to be clear in the metadata, so that the proper port can be chained, e.g. "Service", "admin", "storage", etc
14:36:21 <tbachman> #info bryan_att says the purpose of each vNIC on a VM also needs to be clear in the metadata, so that the proper port can be chained, e.g. "Service", "admin", "storage", etc
14:37:38 <DaveD_> I'm interested in participating in the architecture.
14:37:46 <bouthors> I do too
14:38:16 <tbachman> #info DaveD_ and bouthors are interested in working with the architecture mini-group
14:39:08 <tbachman> #info ebrjohn wants a mini group to investigate how to stand up architecture shown in his “OPNFV SFC Initial NW Topology, V2” slide
14:40:12 <ebrjohn> DaveD_: what's your email? I'll include you
14:40:34 <tbachman> #info bryan_att notes that what the user wants and what the service provider wants might be two different perspectives — we should take this into account when looking at the architectures
14:40:35 <paulq> count me in
14:40:39 <DaveD_> ddolson@sandvine.com
14:40:48 <bryan_att> Yes, let's say what we want, but at different user perspectives, e.g. End-user and VNFi provider
14:42:45 <tbachman> #info lmcdasm says he wasn’t clear from ebrjohn’s email whether this includes enabling/disabling or configuring ports on physical switches
14:43:09 <tbachman> #info ebrjohn says he wouldn’t want to remove any functionality we already have — we should just be adding to it
14:43:54 <tbachman> #info lmcdasm says an end-user asks for creation of a service function, but the service provider might have to provision the virtual and physical resources for this; do we want to supercede this and have SFC be in control of this?
14:44:18 <tbachman> #info repenno agrees — we have to decide who is the master of a give vSwitch
14:44:29 * ebrjohn remembering a quote from Seinfeld: Are you the master of your domain? ;)
14:44:34 <tbachman> yikes
14:44:36 <tbachman> lol
14:49:01 <tbachman> #info lmcdasm says we already have an injector that reads an OVF file and deploys it into openstack
14:50:30 <tbachman> #action repenno to create a workflow diagram for SFC
14:50:37 <tbachman> #undo
14:50:37 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x2c60a90>
14:50:56 <tbachman> #action repenno to create a workflow diagram for SFC and will email to the OPNFV-SFC group
14:51:26 <tbachman> #link https://docs.google.com/document/d/1CQ6HODjk-sa5jSdZm9l6ygxc3TWTE8Zpgq3_NFbK1mc/edit?usp=sharing Document that shows the SFC workflow
14:51:29 <bryan_att> Let's also put on the wiki links to any demos, code, etc that can be shared about what's been done before.
14:51:53 <bryan_att> For example Daniel mentioned an "injector" demo done earlier
14:51:54 <tbachman> #info bryan_att asks to put links in OPNFV-SFC wiki to any demos, code, etc. that can be shared about what’s been done before
14:52:44 <MR_Sandvine> #link https://docs.google.com/document/d/1CQ6HODjk-sa5jSdZm9l6ygxc3TWTE8Zpgq3_NFbK1mc/edit#heading=h.rrqnx1heyzli
14:52:45 <tbachman> #info lmcdasm says we should bring in icbts (Jamie Goodyear) or others who are karaf experts
14:53:15 <tbachman> MR_Sandvine: this is a list of items to cover at the hackfest?
14:53:28 <tbachman> #undo
14:53:28 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2c60c50>
14:53:32 <tbachman> #undo
14:53:32 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2c60d90>
14:53:51 <tbachman> #link https://docs.google.com/document/d/1CQ6HODjk-sa5jSdZm9l6ygxc3TWTE8Zpgq3_NFbK1mc/edit#heading=h.rrqnx1heyzli Agenda for upcoming Hackfest
14:53:59 <tbachman> #info lmcdasm says we should bring in icbts (Jamie Goodyear) or others who are karaf experts
14:54:26 <tbachman> #info DaveD_ asks what the forum is for discussing slide 5
14:54:46 <tbachman> #info ebrjohn says the best place for now is the mailing list (use tag/filter in brackets)
14:55:26 * tbachman has to drop soon
14:55:43 <DaveD_> opnfv-tech-discuss ?
14:56:09 <tbachman> DaveD_: I think that’s the main email list — but you need to add a filter/tag in brackets in the subject
14:56:14 <tbachman> [opnfv-sfc]
14:56:35 <tbachman> that allows folks to only receive traffic based on that filter
14:56:45 <tbachman> (rather than receive all mail to opnfv-tech-discuss)
14:56:53 <DaveD_> I see [SFC] used, here for example: http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-July/003570.html
14:57:27 <tbachman> ah
14:57:33 <tbachman> Use that then :)
14:57:34 <tbachman> thx
14:57:50 <tbachman> (and sorry for the confusion)
14:58:09 * tbachman is dropping — ebrjohn can you do the #endmeeting?
14:58:52 <tbachman> #endmeeting