From a711ce8f00eb52496540f6e39d335da602c0abde Mon Sep 17 00:00:00 2001 From: Kevin Benton Date: Tue, 29 Sep 2015 09:30:35 -0700 Subject: [PATCH] Add a note about agent/server compat to 'effective neutron' Change-Id: I4e7476c4cf29aa0eb2722885c7d407d8ea197f1b --- doc/source/devref/effective_neutron.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/source/devref/effective_neutron.rst b/doc/source/devref/effective_neutron.rst index 98bf8e9fb..d0bd6a5b2 100644 --- 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 ~~~~~~~~~~~~~~~~~~ -- 2.45.2