Install and configure IIoT Core Services

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Observe the following prerequisites before installing IIoT Core Services. These are global prerequisites that apply to all IIoT Core Services components, including the platform component.

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Child Topics

• IIoT Core Services prerequisites

  To install IIoT Core Services, complete the following prerequisites.

• Registry requirements
• Example of how to set up a Docker registry

-r myregistry.example.com:6000

-r myharbor.example.com:6000/my_project

docker stop registry; 
docker rm registry

To use IIoT Core Services, you must provide access to the ports used by the system services and databases.

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Child Topics

• Message brokers, databases, and external-facing services
• Internal core services

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Use the following tools to assist you in the installation process.

Parent Topic

• Preparing for IIoT Core Services installation

  Before you begin installing IIoT Core Services, you should review all of the information in this chapter, gather the required information, and complete any necessary installations.

Child Topics

• Installation checklist

cat <read-write-json-token> | docker login -u _json_key --password-stdin <gcr-url>
cat <read-write-json-token> | HELM_EXPERIMENTAL_OCI=1 helm registry login <gcr-url> -u _json_key --password-stdin

Procedure

1. Download the following tarballs to a node that can connect to the hosted DTR and has Docker installed:

   • iiot-docker-images-release-5.1.0.tgz
   • iiot-installer-release-5.1.0.tgz
   • (Optional) mlservice-docker-images-1.2.0.tgz
   • (Optional) aaf-docker-images-5.1.0.tgz (Digital Twin Beta)
   On this node, the partition with /var/lib/docker (Docker default local repository) should have at least 120 GB free space. You can check how much space is available using the command df -h /var/lib/docker. The partition is needed later for loading and pushing Docker images to the registry.

2. Open the core software package by executing the following command:

   tar xvf iiot-installer-release-5.1.0.tgz

   A new directory is created: iiot-installer-release-5.1.0

3. Open the Docker images TAR file:

   tar xvf iiot-docker-images-5.1.0.tgz

4. (Optional) Open the Machine learning service images TAR file and add og move the untarred folder to iiot-installer-release-5.1.0/mlaas/images:

   tar xvf mlservice-docker-images-5.1.0.tgz
   mv mlaas/images iiot-installer-release-5.1.0/mlaas/

5. (Optional) Open the Digital Twin Beta docker image file and add og move the untarred folder to iiot-installer-release-5.1.0/aaf/images:

   tar xvf aaf-docker-images-5.1.0.tgz
   mv aaf/images iiot-installer-release-5.1.0/aaf/

6. Push the hiota-solutions Helm chart and corresponding solution package to the IIoT Core Services DTR.

   This push only needs to be done once before starting the installation process so that the Solution Control Plane can manage hiota-solutions. Otherwise, hiota-solutions will not appear on the control plane user interface even though the IIoT Core Services is running.

   export HELM_EXPERIMENTAL_OCI=1
   helm chart save <path to IIoT Core Services 5.1.0 image>/iiot-installer-release-5.0.0/Module-4/hiota-solutions-5.0.0.tgz <core-dtr url>/hiota-solutions:5.0.0
   helm registry login <core-dtr url> -u <username> -p <password>
   helm chart push <core-dtr url>/hiota-solutions:5.1.0
   kubectl apply -f <path to IIoT Core Services 5.1.0 image>/iiot-installer-release-5.0.0/Module-4/roles/core-services/install/files/hiota_solution_package.yaml

7. Obtain the hosted GCR login information (json_key file with read-write permission, for example).

8. Tag the Docker images and push them to the hosted registry. This push needs to be done only once.

   The script can also be found in the IIoT Core Services installer script image folder: iiot-installer-release-5.1.0/tag-push-docker-images.sh.

9. Create the GKE three-node cluster.

   NoteTo run Machine learning service, five nodes are recommended.

10. Create the installer VM on GCP with Python 3, Helm 3.6.3, and kubectl installed.

    Check if you can connect to the Kubernetes cluster with the kubectl command. The rest of the IIoT Core Services installation process is performed on the installer VM.

Results

Parent Topic

• Setting up the Kubernetes cluster

  IIoT Core Services can be deployed on different types of Kubernetes clusters:

Procedure

1. Download the following tarballs to a node that can connect to the hosted DTR and has Docker installed.

   • iiot-docker-images-release-5.1.0.tgz
   • iiot-installer-release-5.1.0.tgz
   • (Optional) mlservice-docker-images-1.2.0.tgz
   • (Optional) aaf-docker-images-5.1.0.tgz (Digital Twin Beta)
   On this node, the partition with /var/lib/docker (Docker default local repository) should have at least 120 GB free space. You can check how much space is available using the command df -h /var/lib/docker. The partition is needed later for loading and pushing Docker images to the registry.

2. Open the core software package by executing the following command:

   tar xvf iiot-installer-release-5.1.0.tgz

   A new directory is created: iiot-installer-release-5.1.0

3. Open the Docker images TAR file:

   tar xvf iiot-docker-images-5.1.0.tgz

4. (Optional) Open the Machine learning service images TAR file and add og move the untarred folder to iiot-installer-release-5.1.0/mlaas/images:

   tar xvf mlservice-docker-images-1.2.0.tgz
   mv mlaas/images iiot-installer-release-5.1.0/mlaas/

5. (Optional) Open the Digital Twin Beta Docker image file and add og move the untarred folder to iiot-installer-release-5.1.0/aaf/images:

   tar xvf aaf-docker-images-5.1.0.tgz
   mv aaf/images iiot-installer-release-5.1.0/aaf/

6. Obtain the hosted core DTR login information, such as username and password.

7. Tag the Docker images and push them to the hosted registry. This push needs to be done only once.

   The script can also be found in the IIoT Core Services installer script image folder iiot-installer-release-5.1.0/tag-push-docker-images.sh.

8. Create an on-prem three-node Kubernetes cluster with a storage plugin.

   NoteTo run Machine learning service, five nodes are recommended.

9. Verify that Python 3, Helm 3.6.3, and kubectl are installed on the installation node.

Results

Parent Topic

• Setting up the Kubernetes cluster

  IIoT Core Services can be deployed on different types of Kubernetes clusters:

Before you begin

Procedure

1. Log in to the installation node.

2. Download the platform installation package to the installation node:

   Foundry-Control-Plane-2.4.1.tgz

3. Open the platform installation package by executing the following command:

   mkdir Foundry-Control-Plane-2.4.1
   tar xvf Foundry-Control-Plane-2.4.1.tgz -C ./Foundry-Control-Plane-2.4.1

   NoteYou must perform the installation from a directory that is at least two levels from the root level, as shown above.

4. Navigate to the platform software directory:

   cd Foundry-Control-Plane-2.4.1

5. Get an access token:

   gcloud auth print-access-token

6. To install Keycloak, manually create a file called foundry-control-plane-values.yaml, which is used with the control plane installation command, with the following contents:

   keycloakoperator:
     publicPath: /auth
   configuration:
     keycloak:
       enableDockerAuthentication: true
       instances: 3
   logging:
     enabled: false

7. If you have credentials for the IIoT Core Services Docker Trusted Registry (DTR), try logging into the DTR from the cluster nodes to verify access.

8. Navigate to the bin directory:

   cd foundry-control-plane-2.4.1/bin

   NoteYou must perform the installation from a directory that is at least two levels from the root level, as in /root/foundry-control-plane-2.4.1/bin

9. Install the platform cluster service using the following commands:

   For GKE:

   ./install-cluster-services.sh -r <core-dtr-url> -w service-type=NodePort -u oauth2accesstoken -p $(gcloud auth print-access-token)

   For on-premises:

   ./install-cluster-services.sh -r <core-dtr-url> -w service-type=NodePort -u <username> -p <password>

10. Set the number of replicas of istiod, istio-ingressgateway, and istio-egressgateway you want to run by scaling as follows:

    Example using three replicas:

    kubectl scale deployment -n istio-system --replicas=3 istiod
    kubectl scale deployment -n istio-system --replicas=3 istio-ingressgateway
    kubectl scale deployment -n istio-system --replicas=3 istio-egressgateway

11. Apply Kubernetes custom resource definitions.

    For GKE:

    cd Foundry-Control-Plane/bin/
    ./apply-crds.sh -r <gcr-url> -e -u oauth2accesstoken -p $(gcloud auth print-access-token)

    For on-premises:

    cd Foundry-Control-Plane/bin/
    ./apply-crds.sh -r <core-dtr-fqdn>:[<port>] -e -u <username> -p <password> 
    --insecure

12. Install the control plane.

    For GKE:

    cd Foundry-Control-Plane/bin/
    ./install-control-plane.sh -r <gcr-url> -c https://<cluster-fqdn>:30443 -n hiota -u oauth2accesstoken -p $(gcloud auth print-access-token) -v
    <path-to>/foundry-control-plane-values.yaml --skip_cluster_url_check

    For on-premises:

    cd Foundry-Control-Plane/bin/
    ./install-control-plane.sh -I -r <core-dtr-url> -c https://<cluster-fqdn>:30443 -n hiota -u <username> -p <password> -v
    <path-to>/foundry-control-plane-values.yaml

Results

Parent Topic

• Installing IIoT Core Services

  After the software prerequisites are met and your hosted environment is set up, you can install IIoT Core Services.

Procedure

1. From the command line on the installation node, get the username and password for the Solution Management UI:

   • Username:

     echo $(kubectl get keycloakusers -n hiota keycloak-user -o jsonpath='{.spec.user.username}')

   • Password:

     echo $(kubectl get keycloakusers -n hiota keycloak-user -o jsonpath='{.spec.user.credentials[0].value}')

2. Log in to the Solution Management UI using the acquired credentials:

   https://<cluster-fqdn>:30443/hiota/hscp-hiota/solution-control-plane/

   where <cluster-fqdn> is the location where IIoT Core Services is installed.

3. Navigate to Configuration Registry and replace the JSON password as follows:

   1. Get the JSON token and save it to the file gcr-token.json.
   2. Insert _json_key in the Username field on the Registry tab.
   3. Open the gcr-token.json file to obtain the token.
   4. Copy the token to the Password field on the Registry tab by pasting the password in a single line, and click to save.
   5. Click the Solutions tab, then the Installed sub-tab, to verify the platfom software version.
   If the Version field shows the correct platform version number, the control plane is correctly installed.

4. Check for any port number conflicts for ports 30086, 30529, 30671, 30983, 30984, 30998, 31000, 32400, and 32500 by running the following command:

   kubectl get service -n istio-system istio-ingressgateway

   Alternatively, check one or more specific ports using the following command:

   kubectl get service -A | grep -e <port number A> -e <port number B>

5. If a record is found, edit istio-ingressgateway and alter the port number accordingly:

   kubectl edit service -n istio-system istio-ingressgateway

Results

Parent Topic

• Installing IIoT Core Services

  After the software prerequisites are met and your hosted environment is set up, you can install IIoT Core Services.

You can install and configure IIoT Core Services in your cluster using the following instructions.

Parent Topic

• Installing IIoT Core Services

  After the software prerequisites are met and your hosted environment is set up, you can install IIoT Core Services.

Child Topics

• Start IIoT Core Services installation
• Configure IIoT Core Services

Procedure

1. Log into the VM installation node as root.

2. Save each Helm chart to the registry:

   helm chart save <image> <registry>/<solution-name>:<tag>

3. Push each Helm chart using the following template:

   helm chart push <registry>/<solution-name>:<tag>

helm chart save hiota-solutions-5.1.0 us.gcr.io/<registry>/hiota-solutions:5.1.0
helm chart push us.gcr.io/<registry>/hiota-solutions:5.1.0

helm chart save lumada-ml-model-lifecycle-0.1.0-22.tgz us.gcr.io/<registry>/lumada-ml-model-lifecycle:0.1.0-22
helm chart push us.gcr.io/<registry>/lumada-ml-model-lifecycle:0.1.0-22

helm chart save lumada-ml-model-server-0.1.0-36.tgz us.gcr.io/<registry>/lumada-ml-model-server:0.1.0-36
helm chart push us.gcr.io/<registry>/lumada-ml-model-server:0.1.0-36

helm chart save lumada-ml-model-management-1.0.0-b7.tgz us.gcr.io/<registry>/lumada-ml-model-management:1.0.0-b7
helm chart push us.gcr.io/<registry>/lumada-ml-model-management:1.0.0-b7

helm chart save lumada-ml-notebook-0.2.0-76.tgz us.gcr.io/<registry>/lumada-ml-notebook:0.2.0-76
helm chart push us.gcr.io/<registry>/lumada-ml-notebook:0.2.0-76

helm chart save mlaas-ray-0.2.0-10.tgz us.gcr.io/<registry>/mlaas-ray:0.2.0-10
helm chart push us.gcr.io/<registry>/mlaas-ray:0.2.0-10

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

Child Topics

• Obtain a CA certificate for IIoT Core Services
• Enhance HTTPS security by using a hybrid certificate solution
• Obtain SSL certificate
• Check SSL certificate expiration

Procedure

1. Navigate to https://lumada-edge.hiota.<cluster_fqdn>:30443

   where: cluster_fqdn is the fully qualified domain name (FQDN) for the cluster (usually that of the load balancer).

2. Enter Username and Password.

   If you get an Access Denied message, you do not have the required permissions. Contact your administrator to set up access.

Results

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

IIoT Core Services includes a Modbus adapter that can be configured for TCP communication between a IIoT Gateway and IIoT Core Services.

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

Child Topics

• Install Modbus
• Configure a Modbus adapter
• Example: Configure multiple Modbus connections

Data Catalog is an optional software component that can be used with IIoT Core to perform data profiling and analyze the content and quality of the data.

To use Data Catalog, contact your Hitachi Vantara sales representative and purchase a separate license.

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

Child Topics

• Prerequisites for configuring Data Catalog integration
• Set database certificates in Data Catalog
• Verify Data Catalog user role permissions
• Enable Data Catalog integration
• View IIoT Core data in Data Catalog

Before you begin

Procedure

1. Log in as root user on the installation node.

2. Navigate to the IIoT Core Services installation directory where the Kafka installation script is located:

   cd <iiot-core-installer-dir>

3. Run the Kafka installer:

   ./iiot_kafka_install.sh

4. (Optional) Verify that Kafka has been properly installed by running the following commands:

   kubectl -n kafka get pods 
   kubectl -n zookeeper get pods

   Verify that the Kafka pods (kafka cluster, cruise control, kafka-operator) and the Zookeeper pods (zookeeper, zookeeper-operator) are running successfully.

Results

Parent Topic

• Perform core post installation tasks

  You can perform the following post installation tasks to verify that the IIoT Core Services installation is successful.

Before you begin

Procedure

1. Log in as a root user to a Kubernetes node in the cluster that is being upgraded.

2. Create a kubeconfig file for the Kubernetes node by running the following commands:

   sed -i -e 's/localhost/<kubernetes_node_ip>/' ~/.kube/config
   kubectl get nodes -o wide

3. Copy the Core-DTR CA into the truststore of the Kubernetes node operating system by running the following commands:

   cp /etc/docker/certs.d/<load-balancer-address>\:32400/ca.crt /etc/pki/ca-trust/source/anchors/<load-balancer-address>-32400-ca.crt
   update-ca-trust
   trust list | grep hitachi

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.

Before you begin

Procedure

1. Prepare passwordless SSH login from the installer VM to all Kubernetes nodes by running the following commands on each node:

   ssh-keygen
   ssh-copy-id root@<kubernetes_node_ip>

2. Download the kubeconfig file that you modified for the upgrade from a node that contains the file by using the following commands:

   scp root@<kubernetes_node_ip>:~/.kube/config ~/.kube/config
   kubectl get nodes -o wide
   helm list -A

   NoteFor information about modifying the kubeconfig file, see Prepare cluster nodes for 2.4.1 platform components upgrade.

3. Download the Core-DTR CA cert to the installer VM by using the following commands:

   mkdir -p /etc/docker/certs.d/<FQDN>\:32400/
   scp -r root@<kubernetes_node_ip>:/etc/docker/certs.d/<FQDN>\:32400/ /etc/docker/certs.d/

4. Test the Docker connection to the Core-DTR by logging in to the Core-DTR with the following command:

   docker login <FQDN>:32400 -u <user name> -p <password>

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.

Before you begin

Procedure

1. Log in to the installer VM as a root user.

2. On a node in the cluster, verify the version of istioctl by running the following command:

   istioctl version

3. Verify the version of the following images by running the following commands:

   kubectl get sa -A | grep istio

   kubectl describe deployment admin-app -n hiota | grep Image

   kubectl describe deployment keycloakoperator -n hiota | grep Image

   kubectl describe deployment istiod -n istio-system | grep Image

   kubectl describe deployment cert-manager -n cert-manager| grep Image

4. Verify that the installer VM is pointing to the cluster that is being upgraded by running the following command:

   kubectl get nodes -o wide

   NoteIf you do not see the correct nodes, the installer VM is not correctly configured to point to the cluster. For instructions on configuring the installer VM, see Prepare installer VM for 2.4.1 platform components upgrade.

5. Go to https://support.pentaho.com, download the Foundry-Control-Plane-2.4.1.tgz file and save the file to the directory where you want to install the upgrade.

   NoteYou must perform the installation from a directory that is at least two levels from the root level.

6. Untar the Foundry-Control-Plane-2.4.1.tgz file by running the following command:

   mkdir Foundry-Control-Plane-2.4.1
   tar xvfz Foundry-Control-Plane-2.4.1.tgz -C ./Foundry-Control-Plane-2.4.1

7. To reduce upgrade time, remove istio-injection: enabled from the hiota namespace by running the following command:

   kubectl edit ns -n hiota

   NoteIf you do not remove istio-injection: enabled from the hiota namespace, the upgrade might take a very long time and can result in a timeout error. The long upgrade time and timeout error happens because all -sso-gatekeeper pods are restarted when you run the upgrade command, ./upgrade-cluster-services.sh.

8. Upgrade cluster services by running the following command with a root user name and password:

   $ ./upgrade-cluster-services.sh -w service-type=NodePort -u <user name> -p <password>

   NoteUpgrading cluster services might take a long time.

9. After the upgrade completes, add istio-injection: enabled back to the hiota namespace by running the following command:

   kubectl edit ns -n hiota

10. Apply the Kubernetes custom resource definitions by running the following command:

    ./apply-crds.sh -r <FQDN>:32400 -u <user name> -p <password> --insecure

11. Upload the new control plane charts and images by running the following command:

    ./upload-solutions.sh -C /<filepath>/Foundry-Control-Plane-2.4.1/charts/   -I  /<filepath>/Foundry-Control-Plane-2.4.1/images/ -n hiota

12. Patch imagePullSecrets service account in the istiod-system namespace by running the following command:

    kubectl patch sa istiod -n istio-system -p '{"imagePullSecrets":[{"name":"istio-regcred"}]}'

13. Obtain the IIoT Core Services platform components user name and password by running the following commands:

    echo $(kubectl get keycloakusers -n hiota keycloak-user -o jsonpath='{.spec.user.username}')
    echo $(kubectl get keycloakusers -n hiota keycloak-user -o jsonpath='{.spec.user.credentials[0].value}')

Results

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.

Before you begin

Procedure

1. Log in to the installer VM as a root user.

2. Verify that the installer VM is pointing to the cluster that is being upgraded by running the following command:

   kubectl get nodes -o wide

   NoteIf you do not see the correct nodes, the installer VM is not correctly configured to point to the cluster. For instructions on configuring the installer VM, see Prepare installer VM for 2.4.1 platform components upgrade.

3. Go to https://support.pentaho.com, download the Foundry-Control-Plane-2.4.1.tgz file and save the file to the directory where you want to install the upgrade.

   NoteYou must perform the installation from a directory that is at least two levels from the root level.

4. Untar the Foundry-Control-Plane-2.4.1.tgz file by running the following command:

   mkdir Foundry-Control-Plane-2.4.1
   tar xvfz Foundry-Control-Plane-2.4.1.tgz -C ./Foundry-Control-Plane-2.4.1

5. Obtain the access token for the GKE cluster by running the following command:

   gcloud auth print-access-token

6. To reduce upgrade time, remove istio-injection: enabled from the hiota namespace by running the following command:

   kubectl edit ns -n hiota

   NoteIf you do not remove istio-injection: enabled from the hiota namespace, the upgrade might take a very long time and can result in a timeout error. The long upgrade time and timeout error happens because all -sso-gatekeeper pods are restarted when you run the upgrade command, ./upgrade-cluster-services.sh.

7. Upgrade cluster services by running the following command with the oauth2accesstoken user name and gcloud auth print-access-token password specified:

   ./upgrade-cluster-services.sh -w service-type=NodePort -u  oauth2accesstoken  -p '$(gcloud auth print-access-token)'

   NoteUpgrading cluster services might take a long time.

8. After the upgrade completes, add istio-injection: enabled back to the hiota namespace by running the following command:

   kubectl edit ns -n hiota

9. Apply the Kubernetes custom resource definitions by running the following command:

   ./apply-crds.sh -r <FQDN>:32400 -u <user name> -p <password> --insecure

10. Upload the new control plane charts and images by running the following command:

    ./upload-solutions.sh -C /<filepath>/Foundry-Control-Plane-2.4.1/charts/   -I  /<filepath>/Foundry-Control-Plane-2.4.1/images/ -n hiota

11. Patch imagePullSecrets service account in the istiod-system namespace by running the following command:

    kubectl patch sa istiod -n istio-system -p '{"imagePullSecrets":[{"name":"istio-regcred"}]}'

Results

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.

Before you begin

Procedure

1. Go to the Solution Management site at https://<FQDN>:30443/hiota/hscp-hiota/solution-control-plane/, and log in by using the IIoT Core Services platform components user name and password.

2. In the Solution Management window, click the Solution Control Plane box.

   The solution control plane window opens.

3. In the Installed tab of the solution control plane window, click the action menu icon , and then click Upgrade.

   The Upgrade Solution window opens.

4. In the Upgrade Solution window, click the Upgrade Version list, select 2.4.1, and then click Confirm.

5. Click Upgrade.

   NoteThe upgrade takes approximately 20 minutes to complete. If there are errors during the upgrade, you can roll back to the previous version by clicking the action menu icon and selecting a previous version.

6. After the upgrade completes, verify that the 2.4.1 upgrade was applied by navigating back to the Solution Management site at https://<FQDN>:30443/hiota/hscp-hiota/solution-control-plane/.

   In the Solution Management window, the checkmark on the Solution Control Plane tile turns green, indicating that the 2.4.1 upgrade was applied. The release version updates to 2.4.1. You are now ready to upgrade IIoT Core Services from v5.0 to v5.1.

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.

Before you begin

Procedure

1. Verify that the IIoT Core Services image that you want to use for the v5.1 upgrade is installed on the cluster by navigating to <iiot_installation_directory>/iiot-installer-release-5.1.0/ and running the following command:

   kubectl get secret -n hiota hiota-installation-configuration-values-secret -o=jsonpath="{.data.configuration\.yaml}" | base64 --decode  > configuration.yaml.bak

2. Log in to the installation node as a root user.

3. Untar the IIoT Core Services installer and Docker images by running the following commands:

   $ tar -xvf iiot-installer-release-5.1.0.tgz
   $ tar -xvf iiot-docker-images-release-5.1.0.tgz

4. Navigate to the new directory for the IIoT Core Services installer and Docker images by running the following command:

   cd iiot-installer-release-5.1.0

5. Run the following commands to install the required software libraries:

   export PATH=$PATH:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

   ln -sf /usr/bin/python3 /usr/bin/python

   pip3 install -r requirements.txt

6. To avoid certification-related issues, run the following pre-update script:

   ./iiot_pre_update.sh  <FQDN>

7. Start the IIoT Core Services v5.1.0 update procedure by running the following command:

   ./iiot_update.sh

8. Manually upgrade Kafka by running the following command:

   ./iiot_kafka_upgrade.sh

Results

Next steps

Parent Topic

• Upgrade IIoT Core Services from 5.0 to 5.1

  Use the following procedures to upgrade an existing installation of IIoT Core Services from v5.0 to v5.1.