| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
SR-IOV agent now can handle ports from different networks with the same |
| 5 |
MAC addresses. This feature implies an upgrade in the agent and the server |
| 6 |
RPC version (see ``neutron.plugins.ml2.rpc.RpcCallbacks`` version 1.9). |
| 7 |
Some agent RPC methods have been updated to pass not only the device MAC |
| 8 |
address but the PCI slot too. In case of having more than one port with |
| 9 |
the same MAC address, the PCI slot will discriminate the requested port. |
| 10 |
upgrade: |
| 11 |
- | |
| 12 |
Both the server and the agent RPC versions have been bumped to 1.9; to |
| 13 |
provide a smooth upgrade transition, the `Upgrade Procedure |
| 14 |
<https://docs.openstack.org/operations-guide/ops-upgrades.html>`_ should |
| 15 |
be followed, upgrading first the servers and then the agents. |
| 16 |
The agent RPC methods returned values are not modified to keep |
| 17 |
compatibility with other agents (Linux Bridge, Open vSwitch). The RPC |
| 18 |
server side is capable of attending calls from agent API < 1.9, in order to |
| 19 |
provide backwards compatibility. If the device PCI slot is not provided, |
| 20 |
the behavior will be the previous one. |