16:36:15 <bryan_att> #startmeeting SFC F2F at ODL Hackfest
16:36:15 <collabot> Meeting started Fri Jul 31 16:36:15 2015 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:36:15 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:36:15 <collabot> The meeting name has been set to 'sfc_f2f_at_odl_hackfest'
16:39:13 <cgoncalves> #info Carlos Goncalves
16:41:29 <bryan_att> #info Bryan Sullivan
16:45:03 <cgoncalves> #link http://eavesdrop.openstack.org/#Neutron_Service_Chaining_meeting
16:47:20 <cgoncalves> #link https://git.openstack.org/cgit/openstack/networking-sfc
16:48:49 <bryan_att> #info A project has been initiated in OpenStack
16:52:33 <bryan_att> #info ... Brady provides an intro into the OPNFV SFC project so far
16:55:03 <bryan_att> #link https://docs.google.com/presentation/d/1JOWN-Xf0_GrV5v_n5q9_j9nUQcM8MjlNl3Sw1YN1bxU/edit?usp=sharing
16:55:17 <bryan_att> #info Slides presented at ODL Summit
17:07:02 <bryan_att> #info Brady directs us to slide 5 of the OPNFV SFC working deck
17:07:15 <bryan_att> #link https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit#slide=id.gb69fe6cbf_1_0
17:07:57 <bryan_att> #info Are SFs assumed to be NSH-aware?
17:08:37 <bryan_att> #info Maybe for some... there are variety of issues to be addressed if they are not, e.g. scalability
17:09:01 <bryan_att> #info OVS support for NSH is another dependency
17:09:31 <bryan_att> #info There is a patch pending for this in OVS, and we have to have official release with this patch
17:10:26 <bryan_att> #info The IETF draft Rev 1 should be published soon, mostly a cleanup of Rev 0 - no change to arch etc
17:11:29 <bryan_att> #info DPDK-based OVS is being pursued by Intel, and is part of OVS mainstream, and is a patch Intel controls
17:12:07 <bryan_att> #info what version of ODL will B release be using? Lithium is assumed, but there may be some features we need from Beryllium
17:12:44 <bryan_att> #info What OVS version do we need? 2.4 is late Aug, 2.5 will include Contract
17:13:37 <bryan_att> #info If its in the official release then ok but a private branch is not
17:16:44 <bryan_att> #info clarifying the point above - the VM will need to be NSH-aware (specifically the kernel and/or OVS) rather than the application (SF) running in that VM
17:17:37 <bryan_att> #info Brady: next issue being considered was how VMs are launched as part of SFC setup
17:18:13 <bryan_att> #info Uri: asks about the role of the "SFC-Openstack coordinator"
17:18:43 <bryan_att> #info Brady: what's the trigger to start the VMs is the focus of the coordinator
17:20:28 <bryan_att> #info ... Some discussion about starting a new project in ODL related to this
17:20:42 <bryan_att> #info ... slide 6-8 are 3 options for how this could work
17:22:06 <bryan_att> #info ... we agreed to go with option 2 (slide 7) . In this slide the VNFM is the "coordinator" from the earlier slide
17:23:15 <bryan_att> #info Paul: The user doesn't care just needs a FW, LB, etc
17:23:53 <bryan_att> #info ... e.g. log into AWS and ask for the function, you don't specify the type
17:24:18 <bryan_att> #info Brady: we will need the option for both
17:24:43 <paulq> https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit#slide=id.g5bc8f02e2_53_0
17:25:06 <bryan_att> #info Reinaldo: need to show how to go from slide 7 to a chain (slide is about setting up a SF)
17:26:09 <bryan_att> #info ... the whole problem is who is the master of the VNF?
17:29:02 <bryan_att> #info Keith: something needs to coordinate the compute, storage, network elements; we need to consider the series of events and the level of abstraction
17:29:46 <bryan_att> #info Chris: the orchestration part is more clear to us, our focus is on the MANO stack
17:31:01 <bryan_att> #info Bryan: we also have a lot of interest in that function, monitoring inventory and allocating resources at the VM/VNF and service (chain) levels
17:31:46 <bryan_att> #info Brady: there's an error on slide 9, originally thinking SFFs would live in their own bridges in OVS
17:33:54 <bryan_att> #info Keith: yes the SFFs will live in br_int along with GBP otherwise NSH info will be lost in the transfer (it wont work)
17:34:38 <bryan_att> #info Brady: this is where we have gotten to in the meetings - now that we have option 2 as our plan we will dive into the next level
17:36:16 <bryan_att> #info ... e.g. the VNFM and the initial installation of the VMs - Dan Smith will help with Fuel installation
17:37:27 <bryan_att> #info Bryan: we should setup a demo in parallel on multiple implementations if possible e.g. the APEX and/or JOID based installs if we can get support
17:37:46 <alagalah> ebrjohn: I don't have edit access
17:42:13 <bryan_att> #info Bryan: I will refer to SFC and GBP in the Copper project as the mechanisms to make service chains work, and focus on the overall VNFM/NFVO functions to coordinate
17:42:54 <bryan_att> #info The ODL API browser provides the details on the API
17:45:08 <bryan_att> #info the GBP-SFC demo is available on github, and you can see the API docs thru the UI
17:45:11 <bryan_att> #link https://github.com/alagalah/gbpsfc-env
17:49:01 <bryan_att> #info how will we deliver the VNFM etc parts, e.g. where (what upstream project) and based upon what needs to be determined
17:49:32 <bryan_att> #info Brady: we may have to carry some glue code in the OPNFV-SFC code base for the time being
17:49:53 <bryan_att> #info Bryan: we should try to avoid carrying code over a release boundary
17:50:15 <bryan_att> #info the options include XOS, Tacker, OpenMano, etc
17:50:45 <bryan_att> #info OpenStack contributors are trying to get SFC into it but progress is unclear
17:52:05 <bryan_att> #info Uri: we can carry a test VNFM driver for the short term, knowing that it is not the final solution and that might give us some time to work out the upstream
17:58:15 <bryan_att> #info Bryan suggests that we include some documentation on the stack elements underlying SFC using NSH
17:59:39 <bryan_att> #endmeeting