Add a note about agent/server compat to 'effective neutron'

Change-Id: I4e7476c4cf29aa0eb2722885c7d407d8ea197f1b

diff --git a/doc/source/devref/effective_neutron.rst b/doc/source/devref/effective_neutron.rst
index 98bf8e9fb68138d33016623cf294f793c54d2a61..d0bd6a5b2c7b485b8d2e1c7cfebfff910c4e47b5 100644 (file)
--- a/doc/source/devref/effective_neutron.rst
+++ b/doc/source/devref/effective_neutron.rst
@@ -105,6 +105,12 @@ Backward compatibility
 
 Document common pitfalls as well as good practices done when extending the RPC Interfaces.
 
+* The neutron upgrade path requires the server to support the previous version of
+  the agent. Any changes to the existing RPC methods must be compatible with the
+  previous version of the agent. Otherwise a version bump is required and the old
+  method must be kept under the previous version RPC endpoint.
+
+
 Scalability issues
 ~~~~~~~~~~~~~~~~~~