Difference between revisions of "TelcoWorkingGroup"
m (→Needed Development Not Yet Started) |
(→Upcoming Meetings) |
||
Line 65: | Line 65: | ||
|- | |- | ||
| Thursday 5th February 2015 || 9ː00 Pacific || Access: (888) 875-9370, Bridge: 3; PC: 7053780 || https://etherpad.openstack.org/p/2_5_TWG_Ecosystem_and_Collateral_Team | | Thursday 5th February 2015 || 9ː00 Pacific || Access: (888) 875-9370, Bridge: 3; PC: 7053780 || https://etherpad.openstack.org/p/2_5_TWG_Ecosystem_and_Collateral_Team | ||
+ | |- | ||
+ | | Thursday 12th February 2015 || 9ː00 Pacific || Access: (888) 875-9370, Bridge: 3; PC: 7053780 || https://etherpad.openstack.org/p/2_12_TWG_Ecosystem_and_Collateral_Team | ||
|- | |- | ||
|} | |} |
Revision as of 17:06, 12 February 2015
Mission statement and scope
The working group aims to define the use cases and identify and prioritise the requirements which are needed to deploy, manage, and run telecommunication services 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 telecommunication services.
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.
The work group has also established a team to focus ecosystem development (both vendors and industry co-travelers), collateral development and marketing messaging to address the needs to Telco operators who are interested in deploying OpenStack today.
Membership
Members of the Telco Working Group come from a broad array of backgrounds and include service providers, equipment providers, and OpenStack vendors. We aim to include both operators and developers in an open discussion about the needs of this sector and how to meet them in OpenStack. You can find the current membership list of at TelcoWorkingGroup/Members. Feel free to add your name If you're interested in working with us to improve OpenStack for telecommunications workloads.
Meetings
Technical Team Meetings
The working group meets alternating on Wednesdays between 1400 UTC in #openstack-meeting-alt and 2200 UTC in #openstack-meeting.
Upcoming Meetings
Agenda: [1]
Date | Time | IRC Channel |
---|---|---|
Wednesday 7th January 2015 | 2200 UTC | #openstack-meeting |
Wednesday 14th January 2015 | 1400 UTC | #openstack-meeting-alt |
Wednesday 21st January 2015 | 2200 UTC | #openstack-meeting |
Wednesday 28th January 2015 | 1400 UTC | #openstack-meeting-alt |
Wednesday 4th February 2015 | 2200 UTC | #openstack-meeting |
Wednesday 11th February 2015 | 1400 UTC | #openstack-meeting-alt |
Previous Meetings
Ecosystem and Collateral Team
This team is focused on accelerating the deployment of OpenStack by Telco Operators by enaging with the Ecosystem (vendors and industry groups) and developing needed information/collateral (case studies, reference architectures, etc).
Upcoming Meetings
Date | Time | Bridge Information | Link to Etherpad Notes |
---|---|---|---|
Tuesday 9th December 2014 | 8ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/12_9_TWG_Ecosystem_and_Collateral |
Thursday 8th January 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/1_8_TWG_Ecosystem_and_Collateral |
Thursday 15th January 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/1_15_TWG_Ecosystem_and_Collateral_Team |
Thursday 22th January 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/1_22_TWG_Ecosystem_and_Collateral_Team |
Thursday 29th January 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/1_29_TWG_Ecosystem_and_Collateral_Team |
Thursday 5th February 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/2_5_TWG_Ecosystem_and_Collateral_Team |
Thursday 12th February 2015 | 9ː00 Pacific | Access: (888) 875-9370, Bridge: 3; PC: 7053780 | https://etherpad.openstack.org/p/2_12_TWG_Ecosystem_and_Collateral_Team |
What is NFV?
NFV stands for Network Functions Virtualization. It defines the replacement of usually stand alone appliances used for high and low level network functions, such as firewalls, network address translation, intrusion detection, caching, gateways, accelerators, etc, into virtual instance or set of virtual instances, which are called Virtual Network Functions (VNF). In other words, it could be seen as replacing some of the hardware network appliances with high-performance software taking advantage of high performance para-virtual devices, other acceleration mechanisms, and smart placement of instances. The origin of NFV comes from a working group from the European Telecommunications Standards Institute (ETSI) whose work is the basis of most current implementations. The main consumers of NFV are Service providers (telecommunication providers and the like) who are looking to accelerate the deployment of new network services, and to do that, need to eliminate the constraint of slow renewal cycle of hardware appliances, which do not autoscale and limit their innovation.
NFV support for OpenStack aims to provide the best possible infrastructure for such workloads to be deployed in, while respecting the design principles of a IaaS cloud. In order for VNF to perform correctly in a cloud world, the underlying infrastructure needs to provide a certain number of functionalities which range from scheduling to networking and from orchestration to monitoring capacities. This means that to correctly support NFV use cases in OpenStack, implementations may be required across most, if not all, main OpenStack projects, starting with Neutron and Nova.
For more details on NFV, the following references may be useful:
Glossary
Related Teams and Projects
- OpenStack Congress - Policy as a Service [2]
Development Efforts
Use Case Definition
Use cases are currently collected at TelcoWorkingGroup/UseCases, more are welcome! We also refer to the ETSI NFV gap analysis, currently available at https://wiki.openstack.org/wiki/File:NFV%2814%29000154r2_NFV_LS_to_OpenStack.pdf
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
The NFV use case mappings identified below are from the perspective of higher performing use cases. Please note that there are many possible configurations of devices for each of these use cases and it is not implied that they will all need the proposed capability in the relevant blueprint.
There is an automatically updated gerrit dashboard for all specs and code under review here: http://nfv.russellbryant.net
PRIORITY - repeatedly mentioned at the BOF as blockers:
Description | Project(s) | Status | Blueprint(s) | Design(s) | ETSI-NFV Use Cases |
---|---|---|---|---|---|
VLAN trunking networks for NFV
This line item now confuses various requirements together: VLAN tagged traffic transmissible over a tenant network is the most important (even if Openstack is otherwise VLAN unaware) decomposition of VLAN trunks to virtual networks VLAN tagged traffic to a physical appliance management of VLANs on ports as sub-ports (nice to have, not a blocker) |
Neutron | New | https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks (tenant trunking)
https://blueprints.launchpad.net/neutron/+spec/l2-gateway (physical appliance-specific decomposition) https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms (VLAN port management) |
https://review.openstack.org/#/c/100278/ (physical appliance-specific decomposition)
https://review.openstack.org/97714 (tenant trunking) https://review.openstack.org/#/c/94612/ (subports) https://review.openstack.org/#/c/92541/ (patch for subports) |
* #1 is a broadly applicable IaaS requirement.
|
Permit unaddressed interfaces for NFV use cases | Neutron | New | https://blueprints.launchpad.net/neutron/+spec/nfv-unaddressed-interfaces https://blueprints.launchpad.net/neutron/+spec/ml2-ovs-portsecurity | https://review.openstack.org/97715 https://review.openstack.org/#/c/99873/ |
|
The rest:
neutron port enhancement related to servicevm is summarized at https://wiki.openstack.org/wiki/ServiceVM/neutron-port-attributes
Description | Project(s) | Status | Blueprint(s) | Design(s) | ETSI-NFV Use Cases |
---|---|---|---|---|---|
Virt driver guest NUMA node placement & topology |
Nova | Design Approved / Needs Code Review | https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement | https://review.openstack.org/93636 |
|
Virt driver large page allocation for guest RAM * |
Nova | Design Approved / Needs Code Review | https://blueprints.launchpad.net/nova/+spec/virt-driver-large-pages | https://review.openstack.org/93653 |
|
Virt driver pinning guest vCPUs to host pCPUs |
Nova | Design Approved / Needs Code Review | https://blueprints.launchpad.net/nova/+spec/virt-driver-cpu-pinning | https://review.openstack.org/93652 |
|
|
Nova | Design Approved / Needs Code Review | https://blueprints.launchpad.net/nova/+spec/input-output-based-numa-scheduling | https://review.openstack.org/#/c/100871/ |
|
Soft affinity support for server groups | Nova | Abandoned | https://blueprints.launchpad.net/nova/+spec/soft-affinity-for-server-group | https://review.openstack.org/91328 |
|
Open vSwitch-based Security Groups: Open vSwitch Implementation of FirewallDriver | Neutron | Design review in progress | https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver | https://review.openstack.org/89712 |
|
Framework for Advanced Services in Virtual Machines | Neutron | Under Discussion | https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms |
| |
Neutron Services Insertion, Chaining, and Steering | Neutron | Design Approved / Needs Code Review | https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering | https://review.openstack.org/93524 |
NOTE: this service chaining BP is all about chaining aaS services, not chaining tenant NFVs. Is this the one we want or do we require a new BP?
|
OVF Meta-Data Import via Glance | Glance | New | https://blueprints.launchpad.net/glance/+spec/epa-ovf-meta-data-import | https://review.openstack.org/#/c/104904/ |
|
Support for high performance Intel(R) Data Plane Development Kit based vSwitches | |||||
|
Neutron | Superseded / Unknown | https://blueprints.launchpad.net/neutron/+spec/openvswitch-patch-port-use |
| |
|
Nova | Design review in progress | https://blueprints.launchpad.net/nova/+spec/libvirt-ovs-use-usvhost | https://review.openstack.org/95805 |
|
Snabb NFV mechanism driver | Neutron | Approved | https://blueprints.launchpad.net/neutron/+spec/snabb-nfv-mech-driver | https://review.openstack.org/95711 |
|
VIF_VHOSTUSER (qemu vhost-user) support | Nova | Approved | https://blueprints.launchpad.net/nova/+spec/vif-vhostuser | https://review.openstack.org/96138 |
|
Solver Scheduler - complex constraints scheduler with NFV use cases | Nova | Design review in progress | https://blueprints.launchpad.net/nova/+spec/solver-scheduler | https://review.openstack.org/#/c/96543/ |
|
Discless VM | Nova | Under discussion | https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe |
| |
Network QoS API | Neutron | Under discussion | https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api | https://review.openstack.org/#/c/88599 |
|
Port mirroring | Neutron | Under discussion | https://blueprints.launchpad.net/neutron/+spec/port-mirroring |
| |
Traffic Steering Abstraction | Neutron | Design review in progress | https://blueprints.launchpad.net/neutron/+spec/traffic-steering-abstraction | https://review.openstack.org/92477/ |
|
Implemented (Juno)
Description | Project(s) | Status | Blueprint(s) | Design(s) | ETSI-NFV Use Cases |
---|---|---|---|---|---|
Support two interfaces from one VM attached to the same network | Nova | Design Approved / Implemented | https://blueprints.launchpad.net/nova/+spec/multiple-if-1-net |
| |
SR-IOV Networking Support | Nova | Design Approved / Needs Code Review | https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov | https://review.openstack.org/#/c/86606/ |
|
Virt driver guest vCPU topology configuration | Nova | Design Approved / Implemented | https://blueprints.launchpad.net/nova/+spec/virt-driver-vcpu-topology | https://review.openstack.org/93510 |
|
Evacuate instance to scheduled host | Nova | Approved / Implemented (juno-2) | https://blueprints.launchpad.net/nova/+spec/find-host-and-evacuate-instance | https://review.openstack.org/84429 | |
Heat Multi-region Support | Heat | Approved / Code Review | https://blueprints.launchpad.net/heat/+spec/multi-region-support | https://blueprints.launchpad.net/openstack/?searchtext=multi-region-support |