openstack
/
deb-networking-midonet
Code Issues Proposed changes

doc: Fix unreferenced footnotes warnings 

Closes-Bug: #1697836
Change-Id: I4e8916185e2b95b7543854f0518abbd408ac6cb8
This commit is contained in:
YAMAMOTO Takashi 2017-06-14 13:38:55 +09:00
parent 210a8d2e7b
commit 5ba33dd4b2
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/mitaka/device_management_update.rst
View File

@ -15,7 +15,7 @@ provide device-level gateway management service to the operators.
This API is required in order to propagate device connectivity details to enable
Midonet to manage VTEP Logical Switch configuration upon Logical Gateway definition.
In order to support Router Peering and Direct Connect use cases following definition
in [2]_, Overlay VTEP Router device is supported by MidoNet.
in [2]_, Overlay VTEP Router device is supported by MidoNet. [3]_
While for the routing functionality this device is managed as
traditional neutron Router, it should be possible for operator
(or Orchestration Layer) to enable its VTEP functionality.

2
specs/mitaka/logging-API-for-firewall-rules.rst
View File

@ -11,7 +11,7 @@ Logging API for firewall-rules
This document describes MidoNet's implementation of
logging for firewall rules.
FWaaS v2.0 will be implemented in newton,
FWaaS v2.0 [2]_ will be implemented in newton,
However, first of all we implement MidoNet for mitaka with FWaaS v1.0
because development schedule between
networking-midonet and neutron does not match.