Difference between revisions of "TelcoWorkingGroup"
(→Use Cases: Add ETSI NFV reference.) |
(→Use Cases: Start adding characteristics.) |
||
Line 57: | Line 57: | ||
! Workload Type !! Description || Characteristics !! Examples !! Requirements | ! Workload Type !! Description || Characteristics !! Examples !! Requirements | ||
|- | |- | ||
− | | Data plane || Tasks related to packet handing in an end-to-end communication between edge applications. || | + | | Data plane || Tasks related to packet handing in an end-to-end communication between edge applications. || |
+ | * Intensive I/O requirements | ||
+ | * Intensive memory R/W requirements | ||
+ | || - | ||
+ | || - | ||
|- | |- | ||
− | | Control plane || Any other communication between network functions that is not directly related to the end-to-end data 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. || |
+ | * Less intensive I/O and R/W requirements than control plane, due to lower packets per second | ||
+ | * More complicated transactions resulting in (potentially) higher CPU load per packet. | ||
+ | || - || - | ||
|- | |- | ||
| Signal processing || All network function tasks related to digital processing || - || - || - | | Signal processing || All network function tasks related to digital processing || - || - || - |
Revision as of 18:46, 10 June 2014
Contents
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.
Nick | Name | Affiliation | Interests |
---|---|---|---|
adrian-hoban | Adrian Hoban | Intel OpenStack team | NFV & SDN extensions across OpenStack projects |
cgoncalves | Carlos Goncalves | Instituto de Telecomunicacoes | Service Function Chaining, Traffic Steering |
danpb | Daniel Berrange | Red Hat | Libvirt, KVM & Nova performance & enablement for NFV |
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 |
ijw | Ian Wells | Cisco's Openstack team | Vendor neutral NFV infrastructure, Cisco NFV appliances |
martin_t | Martin Taylor | Metaswitch Networks | Neutron networking and data plane acceleration |
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 |
sgordon | Steve Gordon | Red Hat | NFV and SDN enablement across OpenStack projects but particularly Nova and the Libvirt driver. |
Mission statement
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.
Agenda: [1]
Previous meetings
Use Cases
Workload Type | Description | Characteristics | Examples | Requirements |
---|---|---|---|---|
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. | - | - | - |
References:
Development Efforts
Active Bugs
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
Active Blueprints
PRIORITY - repeatedly mentioned at the BOF as blockers:
Description | Project(s) | Status | Blueprint(s) | Design |
---|---|---|---|---|
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 |
The rest: