openstack/neutron
Code Issues Proposed changes

release note to deprecate prevent_arp_spoofing option

Browse Source 
This option was originally intended to deprecate in Mitaka
and remove in Newton, but we missed to announce it in Mitaka
release note. It looks better to deprecate it in Newton release
and remove it in Ocata release.

Change-Id: Iad466abbb0716da77801315d1a8766ba2f7c06b9
Closes-Bug: #1546010
This commit is contained in:
Akihiro Motoki 2016-04-01 14:45:38 +09:00
parent 4d7409bb8e
commit 2131340d74
3 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
neutron/plugins/ml2/drivers/agent/config.py
View File

@ -43,7 +43,7 @@ agent_opts = [
"added to any ports that have port security disabled. "
"For LinuxBridge, this requires ebtables. For OVS, it "
"requires a version that supports matching ARP "
"headers. This option will be removed in Newton so "
"headers. This option will be removed in Ocata so "
"the only way to disable protection will be via the "
"port security extension."))
]

2
neutron/plugins/ml2/drivers/openvswitch/agent/common/config.py
View File

@ -134,7 +134,7 @@ agent_opts = [
"added to any ports that have port security disabled. "
"For LinuxBridge, this requires ebtables. For OVS, it "
"requires a version that supports matching ARP "
"headers. This option will be removed in Newton so "
"headers. This option will be removed in Ocata so "
"the only way to disable protection will be via the "
"port security extension.")),
cfg.BoolOpt('dont_fragment', default=True,

10
releasenotes/notes/deprecate_prevent_arp_spoofing_option-a09e673fc8f9fee4.yaml Normal file
View File

@ -0,0 +1,10 @@
---
deprecations:
- The option ``[AGENT] prevent_arp_spoofing`` has been deprecated
and will be removed in Ocata release. ARP spoofing protection
should always be enabled unless its explicitly disabled via the
port security extension via the API. The primary reason it was
a config option was because it was merged at the end of Kilo
development cycle so it was not considered stable. It has been
enabled by default since Liberty and is considered stable
and there is no reason to keep this configurable.