Networking PTL

IRC: mestery

Kyle Mestery

Kilo Update

OpenStack Networking

To implement services and associated libraries to

provide on-demand, scalable, and technology-

agnostic network abstraction.

Neutron Kilo Prioritieshttp://git.openstack.org/cgit/openstack/neutron-specs/tree/priorities/kilo-priorities.rst

● Ensure each prioritized task has a specification

associated with it

● Prioritize high-level community tasks into Kilo

milestones

● Be transparent with developers, users, and

distributions around what we want to land in Kilo

● Provide a roadmap for distributions to plan for

what features will land in Kilo

Achieving parity with nova-network

● Icehouse set the groundwork for achieving this

● In Juno, features such as DVR closed the

functionality gap

● During Kilo, the focus will be on migrating nova-

network installs to Neutron

REST / RPC / Plugin API Refactor

● Focused on paying down technical debt by

refactoring the core of Neutron

● This will enable better support for out of tree

extensions

● Switching to pecan from homegrown WSGI

Plugin Decomposition

● Addresses pain points: review time, iteration

speed, easier to use vendor specific modules

● Move to thin in-tree plugins and drivers, with

plugin and driver functionality maintained outside

of Neutron

● Allows for fast iteration for both core Neutron as

well as plugins and drivers

Testing

● Full-stack testing

● Functional testing of OVS, LB, DHCP and

metadata agents

● Retargetable functional tests

Agent Refactoring

● L2 Agent●Scalability

●Agent functional testing

●RPC improvements

●OVSDB monitoring improvements

● L3 Agent●Scalability

●Paying down technical debt

●Abstracting out service agents

● DHCP Agent●Scalability

●Restart improvements

●Load based scheduling

●Dead agent rescheduling

●Functional Tests

Advanced Services Split

● Migrate out LBaaS, VPNaaS, and FWaaS into

separate git repositories

● Allow operators the flexibility of running the

services they want to offer their tenants

● Allow the services teams the chance to iterate

quickly outside the scope of core neutron

● Reduce gate testing complexity

● Optimize core parts of Neutron into a library

Pluggable IPAM

● Create a pluggable IPAM system inside of

Neutron

● Allows the use of third-party and vendor IPAM

system

Speed and Reliability Improvements

● Agent Child Process Status: Monitors agents and

restarts them when they exit

● Rootwrap Daemon Mode: High performance

access to root for commands run by Neutron

agents

Flavor Framework

● A way for operators to offer network services to

their clients

● Allows separation of driver functionality and

configuration from consumers of services

● Allows operators to configure additional vendor

features in an end-user agnostic way

Neutron NFV Work

● Working with the NFV sub-team in OpenStack to

integrate features relevant in this space

● More seamlessly connect hardware and neutron

L2 segments

● Trunk ports to virtual machines

New Plugins Proposed

● A10 Networks LBaaS V2 Driver

● Brocade Vyatta FWaaS, L3, LBaaS and VPNaaS Drivers

● ML2 MechanismDriver for Project Calico

● Cisco Nexus 1000v ML2 MechanismDriver

● Cisco UCS ML2 MechanismDriver

● Freescale FWaaS Plugin

● Huawei ML2 MechanismDriver

● IBM SDN-VE ML2 MechanismDriver

● Infoblox IPAM/DHCP Plugin

● Neutron OVS Agent on Windows

● Mcafee NGFW FWaaS Driver

Things disappearing in Kilo

● Ryu Plugin (ML2 + ofagent replaces this)