Updrading SL1 Extended Architecture

This section provides detailed steps for performing an upgrade on SL1 Extended Architecture.

Use the following menu options to navigate the SL1 user interface:

• To view a pop-out list of menu options, click the menu icon ().
• To view a page containing all of the menu options, click the Advanced menu icon ().

Workflow

The following sections describe the steps to plan and deploy an SL1 update.

If would like assistance planning an upgrade path that minimizes downtime, contact your Customer Success Manager.

The workflow for upgrading SL1 is:

1. Plan the update.
2. Schedule maintenance windows.
3. Review pre-upgrade best practices for SL1.
4. Back up SSL certificates.
5. Set the timeout for PhoneHome Watchdog.
6. Adjust the timeout for slow connections.
7. Run the system status script on the Database Server or All-In-One before upgrading.
8. Upgrade the SL1 Distributed Architecture using the System Update tool (System > Tools > Updates).
9. Remove SL1 appliances from maintenance mode.
10. Upgrade the Extended Architecture
11. Upgrade MariaDB, if needed.
12. Reboot SL1 appliances, if needed.
13. Restore SSL certificates.
14. Reset the timeout for PhoneHome Watchdog.
15. Update the default PowerPacks.
16. Configure Subscription Billing (one time only). For details, see .

For details on all steps in this list except step 10, see the section on Upgrading SL1.

Prerequsites

• ScienceLogic recommends that for production systems, each Compute Cluster contains six (6) Compute Nodes. Lab systems can continue to use Compute  Clusters that include only three (3) Compute Nodes.
• The Storage Cluster requires a (possibly additional) node to act as the Storage Manager.
• Perform the installation steps in the Installation manual to install these additional nodes (for the Computer Cluster and the Storage Cluster) before upgrading your existing nodes.
• Ensure that all nodes in the SL1 Extended Architecture can access the internet.
• You must use the same password for the em7admin account during ISO installation of the Database Server and ISO installation of the appliances in the SL1 Extended Architecture.

To perform the upgrade, you must have a ScienceLogic customer account that allows you access to the harbor repository page on the ScienceLogic Support Site. For details, contact your Customer Success Manager. To verify your access, go to https://registry.scilo.tools/harbor/ .

Resizing the Disks on the Compute Node

The Kafka Messaging service requires additional disk space on each Compute Node. Before upgrading, ensure that each disk on each existing Compute Node in the Compute Node cluster is at least 350 GB.

If each disk on each existing Compute Node is not at least 350 GB, perform the following steps on each Compute Node:

1. Resize the hard disk via your hypervisor to at least 350 GB.
2. Note the name of the disk that you expanded in your hypervisor.
3. Power on the virtual machine.
4. Either go to the console of the Compute Node or use SSH to access the Compute Node.
5. Open a shell session on the server.
6. Log in with the system password for the Compute Node.
7. At the shell prompt, enter:

sudo lsblk | grep <disk_size>

where:

disk_size is your hard disk size from step #1.

8. Note the name of the disk that you expanded in your hypervisor.
9. At the shell prompt, enter:

sudo fdisk /dev/<disk_name>

where:

disk_name is the name of the disk you want to expand.

10. Enter p to print the partition table.
11. Enter n to add a new partition.
12. Enter p to make the new partition the primary partition.
13. Select the default values for partition number, first sector, and last sector.
14. Enter w to save these changes
15. Restart the VM.
16. At the shell prompt, enter:

sudo fdisk -l

17. Notice that now another partition is present.
18. To initialize the new partition as a physical volume, enter the following at the shell prompt:

sudo pvcreate <partition_name>

19. To add the physical volume to the existing volume group, enter the following at the shell prompt:

sudo vgextend em7vg <partition_name>

20. To verify and confirm that the volume group has grown to the expected size, enter the following at the shell prompt:

sudo vgdisplay | grep "VG Size

Upgrading to 12.1.x

Upgrading from 11.2.x or 11.3.x to 12.1.x

To upgrade the SL1 Extended Architecture to 12.1.x from 11.2.x or 11.3.x:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

4. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
5. Click Login via OIDC Provider.
6. Click Customer Login.
7. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
8. Click the username in the upper right and select User Profile.



9. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
10. Exit the browser session.
11. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
12. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 9).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 9).

13. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:12.1

cd sl1x-deploy

14. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

15. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 12.1.0. (This is the latest service version for 12.1 code line; however, this might change in the future.)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

16. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

17. Complete the upgrade by running the full deployment:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x --skip-tags maxconnections

18. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

19. Update your classic SL1 appliances. For more information, see the section on Updating SL1.

Upgrading from 11.1.x to 12.1.x

To upgrade the SL1 Extended Architecture from 11.1.x to 12.1.x:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

4. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
5. Click Login via OIDC Provider.
6. Click Customer Login.
7. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
8. Click the username in the upper right and select User Profile.



9. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
10. Exit the browser session.
11. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
12. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 9).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 9).

13. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:12.1

cd sl1x-deploy

14. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

15. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

16. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:12.1

cd sl1x-deploy

17. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

18. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 12.1.0. (This is the latest service version for 12.1 code line; however, this might change in the future.)
• Add the variable deployment: onprem.
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

19. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

20. Complete the upgrade by running the full deployment:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x --skip-tags maxconnections

21. Update security packages on all nodes: 

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

22. Update your classic SL1 appliances. For more information, see the section on Updating SL1.

Upgrading to 11.3.x

Upgrading from 11.3.x to the Latest Version of 11.3.x

To upgrade the SL1 Extended Architecture from 11.3.0 to 11.3.1:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. Back up the following files:

• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

5. Delete any failed charts:

helm ls | awk '/FAILED/'

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

7. Exit the Ansible shell session:

exit

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

9. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
10. Click Login via OIDC Provider.
11. Click Customer Login.
12. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the username in the upper right and select User Profile.



14. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
17. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 14).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 14).

18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.3

cd sl1x-deploy

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.3.1. (This is the latest service version for 11.3 code line; however, this might change in the future).
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

21. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

23. Run the following deploy command at the shell prompt to upgrade RKE and Kubernetes on the Compute Nodes:

docker-compose -f docker-compose.external.yml run --rm deploy cn

24. Update the SL1 Extended system services:

docker-compose -f docker-compose.external.yml run --rm deploy app --skip-tags maxconnections

25. Update security packages on all nodes: 

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 11.2.x to 11.3.x

To upgrade the SL1 Extended Architecture from the 11.2.x line to 11.3.x:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. Back up the following files:

• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

5. Delete any failed charts:

helm ls | awk '/FAILED/'

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

7. Exit the Ansible shell session:

exit

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
10. Click Login via OIDC Provider.
11. Click Customer Login.
12. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the username in the upper right and select User Profile.



14. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
17. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 14).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 14).

18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.3

cd sl1x-deploy

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.3.0. (Alternatively, if you want to upgrade to 11.3.1, make sure the sl1_version value is sl1_version: 11.3.1).
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

21. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

23. Run the following deploy commands at the shell prompt to upgrade RKE and Kubernetes on the Compute Nodes:

docker-compose -f docker-compose.external.yml run --rm deploy rke-preupgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

docker-compose -f docker-compose.external.yml run --rm deploy rke-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy rke-postupgrade --skip-tags ten

You can run the deploy rke-upgrade and deploy rke-postupgrade commands only once.

24. Re-enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

25. Run the following command:

kubectl get nodes

26. Verify that all node versions listed are upgraded to RKE2 and Kubernetes v1.22. For example, you might see v1.22.9+rke2r2 listed as the version.
27. Exit out of the Ansible shell session:

exit

28. Update the SL1 Extended system services:

docker-compose -f docker-compose.external.yml run --rm deploy app --skip-tags maxconnections

29. Update security packages on all nodes: 

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

30. Re-enter the Ansible shell and run the following command:

kubectl --kubeconfig=/ansible/output-files/kube_config_cluster.yml delete deployment rke2-ingress-nginx-defaultbackend -n kube-system

This command ensures that all old resources are deleted. The output can be resource delete/Error from server (NotFound).

Upgrading from 11.1.x to 11.3.x

To upgrade the SL1 Extended Architecture from the 11.1.x line to 11.3.x:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. Back up the following files:

• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

5. Delete any failed charts:

helm ls | awk '/FAILED/'

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

7. Exit the Ansible shell session:

exit

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
10. Click Login via OIDC Provider.
11. Click Customer Login.
12. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the username in the upper right and select User Profile.



14. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
17. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 14).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 14).

18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.3

cd sl1x-deploy

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.3.0. (Alternatively, if you want to upgrade to 11.3.1, make sure the sl1_version value is sl1_version: 11.3.1).
• Make sure that the deployment value is: deployment: on-prem.
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

21. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

23. Run the following deploy commands at the shell prompt to upgrade RKE and Kubernetes on the Compute Nodes:

docker-compose -f docker-compose.external.yml run --rm deploy rke-preupgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

docker-compose -f docker-compose.external.yml run --rm deploy rke-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy rke-postupgrade --skip-tags ten

You can run the deploy rke-upgrade and deploy rke-postupgrade commands only once.

24. Re-enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

25. Run the following command:

kubectl get nodes

26. Verify that all node versions listed are upgraded to RKE2 and Kubernetes v1.22. For example, you might see v1.22.9+rke2r2 listed as the version.
27. Exit out of the Ansible shell session:

exit

28. At the shell prompt, run the following deploy commands to update the SL1 Extended system services:

docker-compose -f docker-compose.external.yml run --rm deploy sn

docker-compose -f docker-compose.external.yml run --rm deploy sm

docker-compose -f docker-compose.external.yml run --rm deploy app --skip-tags maxconnections

29. Update security packages on all nodes: 

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

30. Re-enter the Ansible shell and run the following command:

kubectl --kubeconfig=/ansible/output-files/kube_config_cluster.yml delete deployment rke2-ingress-nginx-defaultbackend -n kube-system

This command ensures that all old resources are deleted. The output can be resource delete/Error from server (NotFound).

Upgrading from 10.2.x to 11.3.x

To upgrade the SL1 Extended Architecture from the 10.2.x line to 11.3.x:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

3. Back up the following files:

• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

5. Delete any failed charts:

helm ls | awk '/FAILED/'

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

7. Exit the Ansible shell session:

exit

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
10. Click Login via OIDC Provider.
11. Click Customer Login.
12. Log in with the username and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the username in the upper right and select User Profile.



14. On the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the system password you defined in the ISO menu.
17. Log in to Harbor repository:

oras login registry.scilo.tools/sciencelogic/

• Enter the username you used to log in to the browser-based session of Harbor (step 14).
• Enter the password (CLI Secret) that you saved from the browser-based session of Harbor (step 14).

18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.3

cd sl1x-deploy

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.3.0. (Alternatively, if you want to upgrade to 11.3.1, make sure the sl1_version value is sl1_version: 11.3.1).
• Make sure that the deployment value is: deployment: on-prem.
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).

21. Pull the Docker image that is referenced in the docker-compose file

docker-compose -f docker-compose.external.yml pull

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

When prompted, enter the System Password that you entered on the ISO menu.

23. Run the cn-helm-upgrade service:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

24. Run the following deploy commands at the shell prompt to upgrade RKE and Kubernetes on the Compute Nodes:

docker-compose -f docker-compose.external.yml run --rm deploy rke-preupgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

docker-compose -f docker-compose.external.yml run --rm deploy rke-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy rke-postupgrade --skip-tags eleven

You can run the deploy rke-upgrade and deploy rke-postupgrade commands only once.

25. Re-enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

26. Run the following command:

kubectl get nodes

27. Verify that all node versions listed are upgraded to RKE2 and Kubernetes v1.22. For example, you might see v1.22.9+rke2r2 listed as the version.
28. Exit out of the Ansible shell session:

exit

29. At the shell prompt, run the following deploy commands to update the SL1 Extended system services:

docker-compose -f docker-compose.external.yml run --rm deploy sn

docker-compose -f docker-compose.external.yml run --rm deploy sm

docker-compose -f docker-compose.external.yml run --rm deploy app --skip-tags maxconnections

30. Update security packages on all nodes: 

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

31. Re-enter the Ansible shell and run the following commands:

kubectl --kubeconfig=/ansible/output-files/kube_config_cluster.yml delete deployment rke2-ingress-nginx-defaultbackend -n kube-system

kubectl patch job migration-agent-addons-remove --type=strategic --patch '{"spec":{"suspend":true}}' -n kube-system

These commands ensure that all old resources are deleted. The output can be resource delete/Error from server (NotFound).

Upgrading to 11.2.x

Upgrading from 11.2.x to the Latest Version of 11.2.x

To upgrade the SL1 Extended Architecture from the 11.2.x line to a later release in the 11.2.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Back up the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

: ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Delete any failed charts:

helm ls | awk '/FAILED/'

 

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit the Ansible shell session:

exit

 

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



10. Click Login via OIDC Provider.
11. Click Customer Login.



12. Log in with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the user name in the upper right and select User Profile.



14. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
17. Log in to the Harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to log in to the browser-based session on of Harbor. (step 14)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 14)
18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.2

cd sl1x-deploy

 

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.2.3 (This is the latest service version for the 11.2 code line; however, this may change in the future. Alternatively, if you want to upgrade to 11.2.2, make sure the sl1_version value is sl1_version: 11.2.2)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).
21. Pull the docker image that is referenced in the docker-compose file:

docker-compose -f docker-compose.external.yml pull

 

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

23. Run the deploy commands at the shell prompt:

docker-compose -f docker-compose.external.yml run --rm deploy cn

docker-compose -f docker-compose.external.yml run --rm deploy app

 

24. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 11.1.x to 11.2.x

To upgrade the SL1 Extended Architecture from the 11.1.x line to the 11.2.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Back up the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

: ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the Docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Delete any failed charts:

helm ls | awk '/FAILED/'

 

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit the Ansible shell session:

exit

 

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



10. Click Login via OIDC Provider.
11. Click Customer Login.



12. Log in with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the user name in the upper right and select User Profile.



14. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
17. Log in to the Harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to log in to the browser-based session on of Harbor. (step 14)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 14)
18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.2

cd sl1x-deploy

 

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.2.3 (This is the latest service version for the 11.2 code line; however, this may change in the future. Alternatively, if you want to upgrade to 11.2.0 or 11.2.2, make sure the sl1_version value is sl1_version: 11.2.0 or sl1_version: 11.2.2.)

• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture, which can be obtained by contacting ScienceLogic Support.
• Save your changes and exit the file (:wq).
21. Pull the docker image that is referenced in the docker-compose file:

docker-compose -f docker-compose.external.yml pull

 

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

23. Run the deploy commands at the shell prompt:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

24. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 10.2.x to 11.2.x

To upgrade the SL1 Extended Architecture from the 10.2.x line to the 11.2.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Back up the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Delete any failed charts:

helm ls | awk '/FAILED/'

 

6. If the above command results in any output, run the following command:

helm delete --purge $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit the Ansible shell session:

exit

 

8. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

9. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
10. Click Login via OIDC Provider.
11. Click Customer Login.
12. Log in with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the user name in the upper right and select User Profile.



14. In the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
17. Log in to the Harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to log in to the browser-based session on of Harbor. (step 14)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 14)
18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.2

cd sl1x-deploy

 

19. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

20. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.2 (This is the latest service version for the 11.2 code line; however, this might change in the future.)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
21. Pull the docker image that is referenced in the docker-compose file:

docker-compose -f docker-compose.external.yml pull

 

22. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

23. Run the cn-helm-upgrade service and the app-purge service:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

 

24. Run the deploy commands at the shell prompt:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

25. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 10.1.x to 11.2.x

To upgrade the SL1 Extended Architecture from the 10.1.x line to the 11.2.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Back up the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals.

4. Run the following command to enter the Ansible shell on the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Delete the following Helm charts:

helm delete --purge sl1-cn-registration

helm delete --purge model-registry

helm delete --purge aiml-redis-inputcache

kubectl patch pvc redis-data-model-registry-redis-master-0 -p '{"metadata":{"finalizers":null}}'

kubectl patch pvc redis-data-aiml-redis-inputcache-master-0 -p '{"metadata":{"finalizers":null}}'

kubectl delete pvc redis-data-model-registry-redis-master-0 --force --cascade=true

kubectl delete pvc redis-data-aiml-redis-inputcache-master-0 --force --cascade=true

 

6. Delete any failed charts:

helm ls | awk '/FAILED/'

 

7. If the above command results in any output, run the following command:

helm delete --purge $(helm ls | awk '/FAILED/ { print $1 }')

 

8. Exit the Ansible shell session:

exit

 

9. If you have already installed ORAS, you can skip this step. If you have not already installed ORAS, run the following commands:

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

10. After installing ORAS, open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects
11. Click Login via OIDC Provider.
12. Click Customer Login.
13. Log in with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
14. Click the username in the upper right corner of the page and select User Profile.



15. In the User Profile page:



• Note the username.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
16. Exit the browser session.
17. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
18. Log in to the Harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to log in to the browser-based session on of Harbor (step 15).
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 15).
19. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.2

cd sl1x-deploy

 

20. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

21. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.2 (This is the latest service version for the 11.2 code line; however, this might change in the future.)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
22. Pull the Docker image that is referenced in the docker-compose file:

docker-compose -f docker-compose.external.yml pull

 

23. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

24. Run the cn-helm-upgrade service and the app-purge service:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

 

25. Run the deploy command:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

26. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading to 11.1.x

Upgrading from 11.1.x to the Latest Version of 11.1.x

To upgrade the SL1 Extended Architecture from the 11.1.x line to a later version of the 11.1.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Backup the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals

4. Run the following command to enter the Ansible shell on the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Delete any failed charts:

helm ls | awk '/FAILED/'

 

6. If the above command results in any output, run the following command:

helm delete $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit out of ansible shell session:

exit

 

8. Install ORAS. If you have already installed ORAS, you can skip this step.

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

9. Open a browser. Log in to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



10. Click Login via OIDC Provider.
11. Click Customer Login.



12. Log in with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the user name in the upper right and select User Profile.



14. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
17. Log in to harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to log in to the browser-based session on of Harbor. (step 14)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 14)
18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.1

cd sl1x-deploy

 

19. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.1.1 (This is the latest service version for 11.1 code line, however, this may change in the future.)
• Supply values in all the fields that are applicable. Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
20. Pull the docker image:

docker-compose -f docker-compose.external.yml pull

 

21. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

22. Run the deploy commands:

docker-compose -f docker-compose.external.yml run --rm deploy kafka-purge

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

23. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 10.2.x to 11.1.x

To upgrade the SL1 Extended Architecture from the 10.2.x line to the 11.1.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Backup the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals

4. Run the following command to enter the Ansible shell on the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. In the Ansible shell, delete the following deprecated helm charts:

helm delete --purge sl1-cn-registration

 

6. Delete any other failed charts:

helm ls | awk '/FAILED/'

 

7. If the above command results in any output, run the following command:

helm del --purge $(helm ls | awk '/FAILED/ { print $1 }')

 

8. Exit the Ansible shell session:

exit

 

9. Run the following commands to download and install ORAS. If you have already installed ORAS, you can skip this step.

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

10. After installing ORAS, open a browser. Login to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



11. Click Login via OIDC Provider.
12. Click Customer Login.



13. Login with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
14. Click the user name in the upper right and select User Profile.



15. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
16. Exit the browser session.
17. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
18. Login to harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to login to the browser-based session on of Harbor. (step 15)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 15)
19. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.1

cd sl1x-deploy

 

20. Rename old inventory file:

mv sl1x-inv.yml jfrog-sl1x-inv.yml

 

21. Copy the inventory template file to the file named sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

22. Edit the file sl1x-inv.yml to match your SL1 Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.1.1 (This is the latest service version for 11.1 code line, however, this may change in the future.)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
23. Update the docker image:

docker-compose -f docker-compose.external.yml pull

 

24. Update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

• When prompted, enter the System Password that you entered in the ISO menu.
25. Run the cn-helm-upgrade service and the app_purge service:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

 

26. Run the deploy commands at the shell prompt:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

27. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 10.1.x to 11.1.x

To upgrade the SL1 Extended Architecture from the 10.1.x line to the 11.1.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Backup the following files:
• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals

4. Run the following command to enter Ansible shell on the the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

5. Inside the Ansible shell delete the following helm charts:

helm delete --purge sl1-cn-registration

helm delete --purge model-registry

helm delete --purge aiml-redis-inputcache

kubectl patch pvc redis-data-model-registry-redis-master-0 -p '{"metadata":{"finalizers":null}}'

kubectl patch pvc redis-data-aiml-redis-inputcache-master-0 -p '{"metadata":{"finalizers":null}}'

kubectl delete pvc redis-data-model-registry-redis-master-0 --force --cascade=true

kubectl delete pvc redis-data-aiml-redis-inputcache-master-0 --force --cascade=true

 

6. Delete any failed charts:

helm ls | awk '/FAILED/'

 

If the above command results in any output, run the following command:

helm delete --purge $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit the ansible shell session:

exit

 

8. Run the following commands to download and install ORAS. If you have already installed ORAS, you can skip this step.

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

9. After installing ORAS, open a browser. Login to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



10. Click Login via OIDC Provider.
11. Click Customer Login.



12. Login with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
13. Click the user name in the upper right and select User Profile.



14. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
15. Exit the browser session.
16. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
17. Login to harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to login to the browser-based session on of Harbor. (step 14)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 14)
18. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.1

cd sl1x-deploy

 

19. Rename old inventory file:

mv sl1x-inv.yml jfrog-sl1x-inv.yml

 

20. Copy the inventory template file to the name sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

21. Edit the file sl1x-inv.yml to match your SL1Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.1.1 (This is the latest service version for 11.1 code line, however, this may change in the future.)
• Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
22. Update the docker image:

docker-compose -f docker-compose.external.yml pull

 

23. To update credentials on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

24. Run helm upgrade and purge app services:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

 

25. Run the deploy command:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

26. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates

Upgrading from 8.14.x to 11.1.x

To upgrade the SL1 Extended Architecture from the 8.14.x line to the 11.1.x line:

1. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
2. In the Management Node, navigate to the sl1x-deploy directory. To do this, enter the following at the shell prompt:

cd sl1x-deploy

 

3. Backup the following files:

• /home/em7admin/sl1x-deploy/sl1x-inv.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.yml
• /home/em7admin/sl1x-deploy/output-files/cluster.rkestate
• /home/em7admin/sl1x-deploy/output-files/kube_config_cluster.yml

ScienceLogic recommends that you back up these files at regular intervals

3. Run the following command to enter the Ansible shell on the docker container:

docker-compose -f docker-compose.external.yml run --rm deploy shell

 

4. Make a note of the HOSTS value from running the following command:

kubectl get ing responder-ingress

 

5. In the Ansible shell delete the the following services on helm chart:

helm delete --purge sl1-cn-registration

helm delete --purge sl1-streamer

helm delete --purge sls-api-storeconfig

helm delete --purge avail-store

helm delete --purge da-postprocessing-service

helm delete --purge bundle-manager

 

6. Delete any failed charts:

helm ls | awk '/FAILED/'

 

If the above command results in any output, run the following command:

helm delete --purge $(helm ls | awk '/FAILED/ { print $1 }')

 

7. Exit the Ansible shell session:

exit

 

8. Monitor the queues until they are drained:

check https://<HOSTS>/api/queues/list/?api_key=asdfQ345sdf

 

where:

HOSTS is the value from step #5.

Refresh that page until all queues have a value of 0 (zero).

9. Run the following commands to download and install ORAS. If you have already installed ORAS, you can skip this step.

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

10. If you have already installed ORAS, you can skip this step. Run the following commands to download and install ORAS.

sudo su

curl -LO https://github.com/oras-project/oras/releases/download/v0.12.0/oras_0.12.0_linux_amd64.tar.gz

mkdir -p oras-install/

tar -zxf oras_0.12.0_*.tar.gz -C oras-install/

mv oras-install/oras /usr/bin/

rm -rf oras_0.12.0_*.tar.gz oras-install/

exit

 

11. After installing ORAS, open a browser. Login to Harbor at: https://registry.scilo.tools/harbor/sign-in?redirect_url=%2Fharbor%2Fprojects



12. Click Login via OIDC Provider.
13. Click Customer Login.



14. Login with the user name and credentials that you use to access the ScienceLogic Support site (support.sciencelogic.com).
15. Click the user name in the upper right and select User Profile.



16. In the User Profile page:



• Note the user name.
• Click the pages icon next to the CLI secret field to copy the CLI secret to cache.
17. Exit the browser session.
18. Use SSH to access the Management Node. Open a shell session on the server. Log in with the System Password you defined in the ISO menu.
19. Login to the Harbor repository:

oras login registry.scilo.tools/sciencelogic/

 

• Enter the username you used to login to the browser-based session on of Harbor. (step 16)
• Enter the password (CLI Secret) that you saved from the browser-based session on of Harbor. (step 16)
20. Download the deployment files:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:10.1

cd sl1x-deploy

 

21. Rename old inventory file:

mv sl1x-inv.yml sl1x-inv.yml.8.14

 

22. Copy the inventory template file to the name sl1x-inv.yml:

cp sl1x-inv-template.yml sl1x-inv.yml

 

23. Edit the file sl1x-inv.yml to match your SL1Extended system:

vi sl1x-inv.yml

Do not remove colons when editing this file.

• Make sure that the sl1_version value is: sl1_version: 11.1.1 (This is the latest service version for 11.1 code line, however, this may change in the future.)
• Supply values in all the fields that are applicable. Supply values in all the fields that are applicable. For details on the sl1x-inv.yml, see the manual Installing SL1 Extended Architecture.
• Save your changes and exit the file (:wq).
24. Download the deployment latest files:

docker-compose -f docker-compose.external.yml pull

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

25. Update the SL1 Extended system compute nodes at the shell prompt:

docker-compose -f docker-compose.external.yml run --rm deploy cn

 

26. Navigate to the sl1x-deploy directory and download and extract latest templates:

cd /home/em7admin/

oras pull registry.scilo.tools/sciencelogic/sl1x-deploy:11.1

cd sl1x-deploy

 

27. Update libraries and credentials on all nodes:

docker-compose -f docker-compose.external.yml pull

docker-compose -f docker-compose.external.yml run --rm deploy ssh-keys --ask-pass

 

When prompted, enter the System Password that you entered in the ISO menu.

28. Run helm upgrade and purge app services:

docker-compose -f docker-compose.external.yml run --rm deploy cn-helm-upgrade

docker-compose -f docker-compose.external.yml run --rm deploy app-purge

 

29. Run the deploy command:

docker-compose -f docker-compose.external.yml run --rm deploy sl1x

 

30. Update security packages on all nodes:

docker-compose -f docker-compose.external.yml run --rm deploy package-updates