Upgrading cloudSwXtch

WHAT TO EXPECT

In this article, users will learn how to update their cloudSwXtch when new versions are available. The following commands are cloud agnostic, so they should work regardless of what cloud they're using.

What to know:
The upgrade plan from 3.x to 4.x would be to create a new cloudSwXtch, manually configure with the desired configuration, and then install existing bridge(s) and xNIC(s) against the new cloudSwXtch.
The upgrade plan from 4.x to 4.x is a matter of re-running the installation with the new version However it is important to note that if you have any configuration data you want to keep, you should use the “—persist” argument as shown in the example below.

To update your cloudSwXtch, do the following:

Sign in to the VM where the cloudSwXtch is running.
Get the new version by running the following commands (this step may take some time to download the new version):
NOTE
The “persist” argument should be used between 4.x versions. It should not be used from a 3.x to a 4.x version. In this case, note your settings, and they will have to be re-entered into your new 4.x system. The “—auto-deps” will automatically install any dependencies.
```
token="si=RDONLY&spr=https&sv=2021-06-08&sr=c&sig=xyPF7SyI1cagUAEIZViqCHz7RroFTy2Fkltn2wwvMzc%3D"
ver="v4.0.0"
curl -X GET -H "x-ms-date: $(date -u)"  "https://sdmcdevstorage.blob.core.windows.net/imagebuilder/swx-swxtch-${ver}.tar.gz?$token" -o /tmp/swx-swxtch-${ver}.tar.gz 
tar -xvf /tmp/swx-swxtch-${ver}.tar.gz -C /tmp; /tmp/swx-swxtch-${ver}/swx-install.sh --persist 
```
After the installation, run the following command to see if the container is running:
```
docker ps
```

You should see a line with the name swx-swxtch.
Example:

$ docker ps
CONTAINER ID   IMAGE               COMMAND                  CREATED      STATUS       PORTS                                             NAMES
4138870d045a   swx-swxtch:latest   "./entrypoint.sh"        3 days ago   Up 2 hours                                                     swx-swxtch
5087e0922650   registry:2          "/entrypoint.sh /etc…"   3 days ago   Up 2 hours   0.0.0.0:443->443/tcp, :::443->443/tcp, 5000/tcp   registry