Weekly NFV sub-team IRC meeting
MEETING TIME: (Proposed, subject to change) Wednesdays, 1400 UTC, #openstack-meeting-alt, starting June 4
Who we are
Add your name here if you're joining the meetings - IRC nicks are pretty anonymous unless you give us a clue! Please keep the list in alphabetical order by IRC nick.
|adrian-hoban||Adrian Hoban||Intel OpenStack team||NFV & SDN extensions across OpenStack projects|
|cdub||Chris Wright||Red Hat||NFV and SDN work between OpenStack and OpenDaylight|
|cgoncalves||Carlos Goncalves||Instituto de Telecomunicacoes||Service Function Chaining, Traffic Steering|
|cloudon||Calum Loudon||Metaswitch Networks||Neutron, data plane acceleration, orchestration|
|cliljenstolpe||Christopher Liljenstolpe||Metaswitch Networks||Neutron, orchestration, network architecture|
|danpb||Daniel Berrange||Red Hat||Libvirt, KVM & Nova performance & enablement for NFV|
|davidpc||David Pérez Caparrós||DOCOMO Euro-Labs||Supporting NFV in OpenStack|
|eranb||Eran Bello||ASOCS||NFV compute and accelerator resources integration with OpenStack|
|fjramons||Francisco-Javier Ramón Salguero||Telefónica||Libvirt, KVM & Nova performance & enablement for NFV|
|ggarcia||Gerardo García||Telefónica||Libvirt, KVM & Nova performance & enablement for NFV|
|heyongli||Yongli He||Intel Openstack team||nova enabling NFV SRIOV PCI passthrough|
|ian_ott||Ian Jolliffe||Wind River||Openstack, NFV, Networking|
|ijw||Ian Wells||Cisco's Openstack team||Vendor neutral NFV infrastructure, Cisco NFV appliances|
|irenab||Irena Berezovsky||Mellanox||NFV, SDN, NFV SRIOV PCI passthrough|
|lukego||Luke Gorrie||Snabb||Making open source NFV work for Deutsche Telekom's TeraStream project|
|LouisF||Louis Fourie||Huawei||NFV-MANO, Service Function chaining, Traffic steering|
|martin_t||Martin Taylor||Metaswitch Networks||Neutron networking and data plane acceleration|
|rseth||Rajeev Seth||Sonus Networks||NFV integration with OpenStack|
|russellb||Russell Bryant||Project: OpenStack TC, Nova. Corporate: Red Hat||Nova. Ensuring requirements and designs are consumable by OpenStack developers. Reviewing designs and implementations.|
|s3wong||Stephen Wong||Midokura||NFV support on OpenStack|
|sasud||S Sud||Intel||NFV and SDN use case PoCs|
|smazziotta||Sandro Mazziotta||eNovance||OpenStack extensions required to meet NFV requirements|
|sgordon||Steve Gordon||Red Hat||NFV and SDN enablement across OpenStack projects but particularly Nova and the Libvirt driver.|
|yjiang5||Yunhong Jiang||Intel||Nova enablement for NFV|
|zeddii||Bruce Ashfield||Wind River||KVM, libvirt, nova and platform awareness for NFV|
|zuqiang||Zu Qiang||Ericsson||NFV support in OpenStack|
|yamahata||Isaku Yamahata||Intel||Neutron, servicevm, service chaining, traffic steering|
|jmsoares||João Soares||Portugal Telecom||Service Function Chaining, Traffic Steering|
|nijaba||Nick Barcet||eNovance||NFV support on OpenStack|
|imendel||Itai Mendelsohn||Alcatel-Lucent||NFV in general and how OpenStack can enable it|
|dmitry_huawei||Dmitry Meytin||Huawei||MANO integration with OpenStack|
|kalyan||Kalyanjeet Gogoi||Juniper Networks||NFV integration with OpenStack|
|runarut||Larry Pearson||AT&T||OpenStack as NFVI, VNF Service Chaining|
|yukiarbel||Yuki Arbel||Alcatel Lucent||NFV, Openstack for NFV|
The sub-team aims to define the use cases and identify and prioritise the requirements which are needed to run Network Function Virtualization (NFV) workloads on top of OpenStack. This work includes identifying functional gaps, creating blueprints, submitting and reviewing patches to the relevant OpenStack projects and tracking their completion in support of NFV.
The requirements expressed by this group should be made so that each of them have a test case which can be verified using an OpenSource implementation. This is to ensure that tests can be done without any special hardware or proprietary software, which is key for continuous integration tests in the OpenStack gate. If special setups are required which cannot be reproduced on the standard OpenStack gate, the use cases proponent will have to provide a 3rd party CI setup, accessible by OpenStack infra, which will be used to validate developments against.
Chair: Russell Bryant (russellb)
Agenda for next meeting
Wednesday, June 4 at 1400 UTC in #openstack-meeting-alt.
|Data plane||Tasks related to packet handing in an end-to-end communication between edge applications.||
|Control plane||Any other communication between network functions that is not directly related to the end-to-end data communication between edge applications.||
|Signal processing||All network function tasks related to digital processing||
|Storage||All tasks related to disk storage.||
ETSI-NFV Use Cases - High Level Description
- Use Case #1: Network Functions Virtualisation Infrastructure as a Service
This is a reasonably generic IaaS requirement.
- Use Case #2: Virtual Network Function as a Service (VNFaaS).
This primarily targets Customer Premise Equipment (CPE) devices such as access routers, enterprise firewall, WAN optimizers etc. with some Provider Edge devices possible at a later date. ETSI-NFV Performance & portability considerations will apply to deployments that strive to meet high performance and low latency considerations.
- Use Case #3: Virtual Network Platform as a Service (VNPaaS).
This is similar to #2 but at the service level. At larger scale and not at the "app" level only.
- Use Case #4: VNF Forwarding Graphs
Dynamic connectivity between apps in a "service chain".
- Use Case #5: Virtualisation of Mobile Core Network and IMS.
Primarily focusing on Evolved Packet Core appliances such as the Mobility Management Entity (MME), Serving Gateway (S-GW), etc. and the IP Multimedia Subsystem (IMS).
- Use Case #6: Virtualisation of Mobile base station
Focusing on parts of the Radio Access Network such as eNodeB's, Radio Link Control and Packet Data Convergence Protocol, etc..
- Use Case #7: Virtualisation of the Home Environment.
Similar to Use Case 2, but with a focus on virtualising residential devices instead of enterprise devices. Covers DHCP, NAT, PPPoE, Firewall devices, etc.
- Use Case #8: Virtualisation of CDNs
Content Delivery Networks focusing on video traffic delivery.
- Use Case #9: Fixed Access Network Functions Virtualisation
Wireline related access technologies.
- Network Functions Virtualization NFV Performance & Portability Best Practices - DRAFT
- ETSI-NFV Use Cases V1.1.1 
Add the "nfv" tag to bugs to have them appear in these queries:
- Nova: https://bugs.launchpad.net/nova/+bugs?field.tag=nfv
- Neutron: https://bugs.launchpad.net/neutron/+bugs?field.tag=nfv
PRIORITY - repeatedly mentioned at the BOF as blockers:
|Support two interfaces from one VM attached to the same network||Nova||first BP submit||https://blueprints.launchpad.net/nova/+spec/2-if-1-net||https://review.openstack.org/97716|
|VLAN trunking networks for NFV||Neutron||first BP submit||https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks https://blueprints.launchpad.net/neutron/+spec/l2-gateway https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms||https://review.openstack.org/97714 https://review.openstack.org/#/c/94612/ https://review.openstack.org/#/c/92541/ (patch)|
|Permit unaddressed interfaces for NFV use cases||Neutron||first BP submit||https://blueprints.launchpad.net/neutron/+spec/nfv-unaddressed-interfaces||https://review.openstack.org/97715|
neutron port enhancement related to servicevm is summarized at https://wiki.openstack.org/wiki/ServiceVM/neutron-port-attributes