Difference between revisions of "Tacker/neutron-port-attributes"
< Tacker
(Created page with "= neutron port attribute enhancement = == use case == == requirement ==") |
|||
| Line 1: | Line 1: | ||
| − | = | + | = Neutron port attribute enhancement = |
| − | == | + | == 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 == | ||
Revision as of 05:47, 10 June 2014
Contents
Neutron port attribute enhancement
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.
