Good day
I have my own OpenFlow instance hosted on linux in Azure cloud. I would like to upgrade to the latest version (I have not done an upgrade before).
What would be the best approach to upgrade OpenFlow? Downtime should not be an issue.
I also have noderedagents connected to OpenFlow installed on a local machine. I assume the agent would not need updating as the OpenFlow instance starts the agent from the image on the server, but I don’t want to make the wrong assumption and cause additional downtime that is not needed.
I have searched the forum for previous posts but could not find a related post with the correct upgrade procedures.
I do not recommend using the latest tag for production. You should always “pin” your installation to a specific version number. Right now, the latest version is 1.5.12.64. This version has been running stably for several months, but we are planning on releasing a new version soon with some UI optimizations (mostly around filters on different pages).
Generally, updating is as simple as updating the version tag (or run docker compose up pull, if you are using the :latest tag, and then run docker compose up up).
Upgrading from 1.4 to 1.5 was challenging as it involved removing all NodeRED instances and re-creating them as agents in the new setup. But besides that, it was basically just updating the version number and running docker compose up or helm upgrade openflow openflow --values=......
Upgrading from a version less than 1.5.10 to something higher than 1.5.10 can be tricky for people who have enabled multi-tenancy, but for 99% of people, it has no impact.
So for you, since you are over 1.4, it should be as simple as editing your docker compose file with the new tag you want to run, then run docker compose up. (If you used the batch/shell files, it could also be normal-up or letsencrypt-up, or whatever version you are using.)