Jump to: navigation, search

Difference between revisions of "Tacker/neutron-port-attributes"

(Neutron port attribute enhancement)
Line 1: Line 1:
 
= Neutron port attribute enhancement =
 
= Neutron port attribute enhancement =
 +
NFV and ServiceVM need extensions/enhancements for neutron port.
 +
With this page, use cases/requirements are collected and then they will be broken down to actual blueprints and implemtations.
 +
 
== Use case 1==
 
== Use case 1==
 
Service VM implements some service, e.g., routing or VPN. That VM will then be connected to a number of Neutron Networks/Subnets in some tenant.
 
Service VM implements some service, e.g., routing or VPN. That VM will then be connected to a number of Neutron Networks/Subnets in some tenant.

Revision as of 06:23, 10 June 2014

Neutron port attribute enhancement

NFV and ServiceVM need extensions/enhancements for neutron port. With this page, use cases/requirements are collected and then they will be broken down to actual blueprints and implemtations.

Use case 1

Service VM implements some service, e.g., routing or VPN. That VM will then be connected to a number of Neutron Networks/Subnets in some tenant. To provide its service the VM must be able to FORWARD traffic (i.e., packets come in on one VM interface and same packets leave on another one).

Requirement

It must be possible to disable security groups on Neutron Ports used by a service VM. There exists an extension for this: https://github.com/openstack/neutron/blob/master/neutron/extensions/portsecurity.py However it is not implemented by the free plugins like ML2, Openvswitch etc.

Use case

Requirement