Jump to: navigation, search
(Created target blank page For Version: HTCC:9.0.0)
 
(Update with the copy of version: 9.0.0DRAFT)
 
Line 1: Line 1:
−
<!-- Creation of the target page -->
+
=Upgrading Web Services and Applications=
 +
 
 +
The following steps are applicable for all 9.0 releases except Web Services and Applications release 9.0.002.57, for which you need to follow specific [[UpgradeFrom57|upgrade]] and [[RollBackTo57|roll back]] instructions.
 +
 
 +
During a migration, it is strongly recommended that you avoid changing the configuration files if the changes are not required by the migration procedure. Configuration changes can cause the migration to fail.
 +
 
 +
===Implementation Steps===
 +
<ol>
 +
<li> If you have a separate deployment of Elasticsearch, please follow the [https://docs.genesys.com/Documentation/HTCC/9.0.0DRAFT/MIG/UpgradeES Upgrading Elasticsearch] procedure.
 +
<li>Unpack the installation package (e.g. '''IP_HTCCDev_9000197b1_ENU_dockerlinux.zip''' file) and navigate to the '''ip''' folder which contains the following files:
 +
* '''gws-microservices.tgz'''
 +
* exported microservices in tar.gz format (e.g. '''gws-platform-configuration_9.0.000.42.tar.gz''')
 +
</li>
 +
<li>Unpack the '''gws-microservices.tgz''' archive to the '''/opt/genesys/gws''' directory.
 +
<source lang="text">
 +
mkdir -p /opt/genesys/gws
 +
tar xvf gws-microservices.tgz -C /opt/genesys/gws
 +
</source>
 +
</li>
 +
<li>Populate Docker images (presented in *.tar.gz format) from the installation package to your corporate docker registry.
 +
<source lang="text">
 +
for i in *.tar.gz; do /opt/genesys/gws/kubernetes/bin/push-containers-to-local-registry.sh $i %corporate_registry_address% --push; done
 +
</source>
 +
{{NoteFormat|This script must be run with Docker-capable privileges and you must log in to your registry before pushing.}}
 +
</li>
 +
<li>Navigate to '''/opt/genesys/gws/kubernetes'''.</li>
 +
<li>Configure the [https://docs.genesys.com/Documentation/HTCC/9.0.0DRAFT/Dep/InstallingAndDeploying#YamlParameters parameters.yaml] file. </li>
 +
<li>Invoke Helm:
 +
<source lang="text">
 +
helm upgrade gws gws/ -n gws-service -f gws-versions.yaml -f parameters.yaml -i
 +
</source>
 +
 
 +
Where:
 +
* '''gws''' is the name of deployment.
 +
* '''gws/''' is the helm chart directory.
 +
* '''-n gws-service''' is the Kubernetes namespace name to deploy to.
 +
* '''-f gws-versions.yaml''' is the config file where versions of containers are defined.
 +
* '''-f parameters.yaml''' is the previously customized config file where deployment parameters are defined.
 +
</li>
 +
<li>Wait until the Helm upgrade Web Services and Applications and Kubernetes cluster start all the requested containers.</li>
 +
</ol>
 +
 
 +
===Rollback===
 +
 
 +
In the event of a migration failure, you must rollback to the previous version instead of rolling back only the changed options.
 +
To perform rollback, please invoke:
 +
<source lang="text">
 +
helm rollback gws 0 -n gws-service
 +
</source>
 +
Where:
 +
* '''gws''' is the deployment name.
 +
* '''0''' is an option to roll back to the last successful release.
 +
* '''-n gws-service''' is the Kubernetes namespace name to deploy to.
 +
 
 +
[[Category:V:HTCC:9.0.0]]

Latest revision as of 19:48, December 22, 2020

Upgrading Web Services and Applications

The following steps are applicable for all 9.0 releases except Web Services and Applications release 9.0.002.57, for which you need to follow specific upgrade and roll back instructions.

During a migration, it is strongly recommended that you avoid changing the configuration files if the changes are not required by the migration procedure. Configuration changes can cause the migration to fail.

Implementation Steps

  1. If you have a separate deployment of Elasticsearch, please follow the Upgrading Elasticsearch procedure.
  2. Unpack the installation package (e.g. IP_HTCCDev_9000197b1_ENU_dockerlinux.zip file) and navigate to the ip folder which contains the following files:
    • gws-microservices.tgz
    • exported microservices in tar.gz format (e.g. gws-platform-configuration_9.0.000.42.tar.gz)
  3. Unpack the gws-microservices.tgz archive to the /opt/genesys/gws directory. 
    mkdir -p /opt/genesys/gws
tar xvf gws-microservices.tgz -C /opt/genesys/gws
  4. Populate Docker images (presented in *.tar.gz format) from the installation package to your corporate docker registry. 
    for i in *.tar.gz; do /opt/genesys/gws/kubernetes/bin/push-containers-to-local-registry.sh $i %corporate_registry_address% --push; done
    Important
    This script must be run with Docker-capable privileges and you must log in to your registry before pushing.
  5. Navigate to /opt/genesys/gws/kubernetes.
  6. Configure the parameters.yaml file.
  7. Invoke Helm: 
    helm upgrade gws gws/ -n gws-service -f gws-versions.yaml -f parameters.yaml -i

    Where:

    • gws is the name of deployment.
    • gws/ is the helm chart directory.
    • -n gws-service is the Kubernetes namespace name to deploy to.
    • -f gws-versions.yaml is the config file where versions of containers are defined.
    • -f parameters.yaml is the previously customized config file where deployment parameters are defined.
  8. Wait until the Helm upgrade Web Services and Applications and Kubernetes cluster start all the requested containers.

Rollback

In the event of a migration failure, you must rollback to the previous version instead of rolling back only the changed options. To perform rollback, please invoke: 

helm rollback gws 0 -n gws-service

Where:

  • gws is the deployment name.
  • 0 is an option to roll back to the last successful release.
  • -n gws-service is the Kubernetes namespace name to deploy to.
This page was last edited on December 22, 2020, at 19:48.
Comments or questions about this documentation? Contact us for support!