Seamless Upgrade from a Previous Version

Prior to v5.2.1, the Agent stored flow state keys on Cassandra, which is no longer mandatory. To support a seamless upgrade from previous versions and for backwards compatibility, the MidoNet Agent read state keys upon reboot or after a port migration from Cassandra and from local storage.

Thus, the upgrade path is the same as the operator would expect in normal circumstances, i.e. install the new package version and reboot the MidoNet Agent. After reboot, the agent will start writing to local disk and stop storing data on Cassandra. After all agents have been upgraded to the new version, it is safe to shut down the Cassandra daemons and repurpose the nodes for other functionalities.

Questions? Discuss on Mailing Lists or Chat.
Found an error? Report a bug.

loading table of contents...