Preparing for software upgrade

Use this procedure to prepare for the software upgrade from the old release to the new release.
  1. Display the system information and status.
    Log in to the old deployer VM using SSH.
    1. Verify that the Helm charts are running the current release.
      [root@fss-deployer ~]# export KUBECONFIG=/var/lib/fss/config.fss
      [root@fss-deployer ~]# helm list
      NAME NAMESPACE REVISION UPDATED                                STATUS  CHART                              APP VERSION
      prod default  1       2023-05-29 06:08:37.917207827 +0000 UTC deployed fss-FSS_22_12_B1-charts-v22.12.2-11 1.0
      
    2. Verify that the pods are all up and running.
      [root@fss-deployer ~]# kubectl get pods
      NAME                                                   READY   STATUS    RESTARTS      AGE
      prod-cp-kafka-0                                        2/2     Running   2 (32m ago)   35m
      prod-cp-kafka-1                                        2/2     Running   1 (32m ago)   33m
      prod-cp-kafka-2                                        2/2     Running   0             32m
      prod-cp-zookeeper-0                                    2/2     Running   0             35m
      prod-cp-zookeeper-1                                    2/2     Running   0             32m
      prod-cp-zookeeper-2                                    2/2     Running   0             32m
      prod-ds-apiserver-75ffbd8dd8-bbgt2                     1/1     Running   0             35m
      prod-ds-cli-67bc6c89c7-dfdbn                           1/1     Running   0             35m
      prod-ds-docker-registry-589fb466d5-tdltk               1/1     Running   0             35m
      prod-ds-imgsvc-deploy-66dc945bf6-9k24k                 1/1     Running   0             35m
      prod-fss-alarmmgr-7b6ff65f97-mj5x8                     1/1     Running   0             35m
      prod-fss-auth-57648dff7c-vv8j2                         1/1     Running   0             35m
      prod-fss-catalog-75b6b87c69-rqg87                      1/1     Running   0             35m
      prod-fss-cfggen-6df55b9fd9-hnj99                       1/1     Running   0             35m
      prod-fss-cfgsync-6ccdd5474f-ppgfj                      1/1     Running   0             35m
      prod-fss-connect-686589bb65-vx8wj                      1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-42d52                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-674tl                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-7vzw8                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-fskd8                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-lj5wz                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-plx6s                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-tg67x                            1/1     Running   0             35m
      prod-fss-da-58b4fbbd5-w8gg7                            1/1     Running   0             35m
      prod-fss-deviationmgr-acl-66c754c6cc-h7c25             1/1     Running   0             35m
      prod-fss-deviationmgr-bfd-65c5ff9457-45sgz             1/1     Running   0             35m
      prod-fss-deviationmgr-interface-58fc8bb77d-xfdlp       1/1     Running   0             35m
      prod-fss-deviationmgr-netinst-b8cbccb9d-9gtl6          1/1     Running   0             35m
      prod-fss-deviationmgr-platform-7c9f6bf67b-x96mn        1/1     Running   0             35m
      prod-fss-deviationmgr-qos-6b97dcc884-8w5dv             1/1     Running   0             35m
      prod-fss-deviationmgr-routingpolicy-67df5489cc-w6tpc   1/1     Running   0             35m
      prod-fss-deviationmgr-system-67b85d8974-bgd8l          1/1     Running   0             35m
      prod-fss-dhcp-7b77b55746-27mh7                         1/1     Running   0             35m
      prod-fss-digitalsandbox-7c84dbfb85-wgngf               1/1     Running   0             35m
      prod-fss-filemgr-6d6cfcc68b-4wz4j                      1/1     Running   0             35m
      prod-fss-imagemgr-c8d7cdfb5-hsgnq                      1/1     Running   0             35m
      prod-fss-intentmgr-858587457f-ppk6g                    1/1     Running   0             35m
      prod-fss-inventory-69bdbf979-wp852                     1/1     Running   0             35m
      prod-fss-labelmgr-56cf479f99-ljbkm                     1/1     Running   0             35m
      prod-fss-maintmgr-569c964d89-4j7l7                     1/1     Running   0             35m
      prod-fss-mgmtstack-7dcddf4479-hlpd8                    1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-28xj4                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-gpvd4                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-hslvh                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-nsbgd                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-qtplh                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-x7rgg                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-xd964                       1/1     Running   0             35m
      prod-fss-oper-da-fdb879d95-xdczn                       1/1     Running   0             35m
      prod-fss-oper-topomgr-598c95fbc4-cm5hl                 1/1     Running   0             35m
      prod-fss-protocolmgr-5d67f4548b-9vxs7                  1/1     Running   0             35m
      prod-fss-topomgr-5d8dd6597f-n76xq                      1/1     Running   0             35m
      prod-fss-transaction-b678ff785-czgcz                   1/1     Running   0             35m
      prod-fss-version-758dfd6c49-7wxvg                      1/1     Running   0             35m
      prod-fss-web-59c677689-44dtr                           1/1     Running   0             35m
      prod-fss-workloadmgr-7469c5b46b-whgdw                  1/1     Running   0             35m
      prod-fss-ztp-646cd8df76-9gmt4                          1/1     Running   0             35m
      prod-keycloak-0                                        1/1     Running   0             35m
      prod-mongodb-arbiter-0                                 1/1     Running   0             35m
      prod-mongodb-primary-0                                 1/1     Running   0             35m
      prod-mongodb-secondary-0                               1/1     Running   0             35m
      prod-neo4j-core-0                                      1/1     Running   0             35m
      prod-postgresql-0                                      1/1     Running   0             35m
      prod-sftpserver-b68849d55-gsv7m                        1/1     Running   0             35m
  2. Back up the necessary files from the deployer VM.
    Copy the following files to a directory that is outside of the deployer VM:
    • SSH files

      /root/.ssh/id_rsa

      /root/.ssh/id_rsa.pub

      /root/.ssh/known_hosts

    • the input JSON configuration and user values YAML file (if any) that were used to install the Fabric Services System, for example:

      /root/customer-input.json

      /root/user_values.yaml

    • the HTTPS related certificate files that were used to install Fabric Services System, for example:

      /root/tls.crt

      /root/tls.key

    • optional files; for example, SRL image tar files that were added to the old deployer VM

  3. Back up the Fabric Services System.

    For instructions, see Backup and restore in the Fabric Services System User Guide.

  4. Temporarily remove all ACL and QoS profiles configured in the system.
    See the Release Notes for background information about this step. For instructions, see the ACL profile management and QoS profile management sections in the Fabric Services System User Guide.
  5. Shut down the old deployer VM.
    Note: Ensure that the old deployer VM is not configured to automatically restart.
  6. Create a new deployer VM using the image for the new release.
    For instructions, see Fabric Services System deployer VM creation. The new deployer should have the same network configuration and the same IP address of old deployer VM.
  7. Copy the files that you saved in Step 2 to the new deployer VM in the same locations.
Performing a software upgrade