Dell ObjectScale 1.3 Administration Guide

Upgrade ObjectScale on OpenShift

Steps for upgrading ObjectScale version 1.3.0 to 1.3.x on OpenShift deployment.

1. Upgrade CSI Components.
   1. Create environment variables.

      export CSI_VERSION=1.3.0-648.59a295a
      export CSI_OPERATOR_VERSION=1.3.0-121.2e006fb
      export CSI_CHARTS_DIR=<CHART_DIRECTORY>/1.3.0-121.2e006fb

      NOTE:<CHART_DIRECTORY> is the directory that you created and where you downloaded the ObjectScale charts.tgz files.
   2. Get existing installation values from helm.
      NOTE:<CSI_NAMESPACE>

      is the namespace where CSI components are installed.

      helm -n <CSI_NAMESPACE> get values csi-baremetal -o yaml > csi-baremetal.yaml
      helm -n <CSI_NAMESPACE> get values csi-baremetal-operator -o yaml > csi-baremetal-operator.yaml
      helm -n <CSI_NAMESPACE> get values csi-baremetal-alerts -o yaml > csi-baremetal-alerts.yaml
      helm -n openshift-secondary-scheduler-operator get values secondary-scheduler-operator -o yaml > secondary-scheduler-operator.yaml
      helm -n objectscale get values objs -o yaml > objectscale-portal-values.yaml

   3. Upgrade CSI Secondary Scheduler.

      helm upgrade -n openshift-secondary-scheduler-operator secondary-scheduler-operator $CSI_CHARTS_PATH/secondaryscheduleroperator-1.3.0-121.2e006fb.tgz -f secondary-scheduler-operator.yaml --set global.registry=$REGISTRY --set csv.version=secondaryscheduleroperator.v1.1.2 --set image.tag=1.3.0-121.2e006fb 

   4. Upgrade CSI Operator.

      helm upgrade -n csi-ns csi-baremetal-operator $CSI_CHARTS_PATH/csi-baremetal-operator-1.3.0-121.2e006fb.tgz -f csi-baremetal-operator --set global.registry=$REGISTRY --set image.tag=$1.3.0-121.2e006fb

   5. Upgrade CSI deployment.

      helm upgrade -n csi-ns csi-baremetal $CSI_CHARTS_PATH/csi-baremetal-deployment-1.3.0-121.2e006fb.tgz -f csi-baremetal.yaml --set global.registry=$REGISTRY --set image.tag=1.3.0-648.59a295a

   6. Upgrade CSI Bare-Metal alerts.
      Download the latest version of CSI Bare-metal alerts file from the Dell Support Site.

      helm upgrade -n csi-ns csi-baremetal-alerts <CHART_DIRECTORY>/csi-baremetal-alerts-1.3.0.tgz csi-bm-alerts.yaml
      

      NOTE:After upgrading CSI, ensure all the pods in the CSI namespace are up and running.
2. Upgrade Postgres.

   helm -n objectscale get values postgres -o yaml > postgres-values.yamlhelm upgrade postgres -n <OBJECTSCALE_NAMESPACE> ./postgres-ha-1.3.0.tgz --set global.registry=$REGISTRY -f postgres-values.yaml

3. Upgrade ObjectScale Portal.
   Run the below command for objectscale-portal upgrade.

   # ObjectScale 1.3.0 to 1.3.x upgrade
   helm -n objectscale upgrade <objectscale_portal_name> ./objectscale-portal-1.3.0.tgz --version 1.3.0 -f objectscale-portal-values.yaml
   

   NOTE:After the portal upgrade, the ObjectScale portal, graphql, and install-controller pods should be restarted. Ensure they are running before moving to the next step.
4. Log in to the ObjectScale Portal using the admin account to upgrade ObjectScale components.
5. From the ObjectScale Portal user interface, click Administration.
   The Administration sections that the user is authorized to view are displayed.
6. Click Upgrades.
   The Components tab is displayed and lists ObjectScale Components.
7. Select all the ObjectScale components and click Pre-Upgrade Health Check to check the components for upgrade readiness.
   The Last Health Check column provides a pass or fail status. If any of the component health checks failed, you must resolve any issues with the component prior to performing the upgrade.
8. After successfully checking the components for upgrade readiness, clear all components, and then select the kahm ObjectScale component. Click Upgrade to begin the upgrade of the component.
   For kahm ObjectScale component, Up to date is displayed in the Available Upgrades column.
9. Select the objectscale-manager ObjectScale component. Click Upgrade to begin the upgrade of the component.
   NOTE:Before going to the next step, ensure that all related pods are ready. Use the below command to find and list all the pods.

   kubectl get pod -n objectscale -l release=objectscale-manager

   For objectscale-manager ObjectScale component, Up to date is displayed in the Available Upgrades column.
10. Select the decks ObjectScale component. Click Upgrade to begin the upgrade of the component.
    NOTE:Before going to the next step, ensure that all related pods are ready.
    For decks ObjectScale component, Up to date is displayed in the Available Upgrades column.
11. Select the SupportAssist if it is configured previously. Click Upgrade to begin the upgrade of the component.
    NOTE:Before going to the next step, ensure that all related pods are ready.
    For SupportAssist ObjectScale component, Up to date is displayed in the Available Upgrades column.
12. Upgrade snmp-notifier if it is configured previously.

    helm upgrade snmp-notifier snmp-notifier-2.3.0-<VERSION>.tgz --set product=objectscale --set snmpServer.host=myhost --set global.registry=$REGISTRY -n objectscale

    NOTE:Before going to the next step, ensure that all related pods are ready.
    All the ObjectScale components are upgraded to the latest version.
13. Click the Object Stores tab to upgrade Object Stores.
    The upgrade package is displayed for available versions from which you can choose the version for the target release.
14. Click Precheck and confirm by clicking Start precheck.
    The precheck process starts.
15. When the Precheck Passed message is displayed on the top of the screen, click Upgrade
    A dialogue box is displayed with the upgrade version details.
16. Click Start Upgrade
    The upgrade starts, and the various stages of progress are displayed.