 Hello, welcome to StarliX Training Club. Today we are going to talk about StarliX patching. StarliX patching provides the capability to update current StarliX systems before the next major release. It can be used for bug fixings, security enhancement, feature enhancement and so on. First, let's make a StarliX patch. Before making a patch for a deployed StarliX system, we need to understand its software version. We can run system show to check the field of software version or we can check the build info file under ETC folder. Then we need a codebase to build updated rpms and the patch. Make sure you are using the right codebase for the specific software version. Before building packages for the updated rpms files, make sure the TIS patch version is also updated. Only a version updated rpms file can be patched into a StarliX. When all the rpms are ready, we can use the patch build tool provided in STX Update project to build a StarliX patch. Read the help to understand all options of a patch build, then we can start to build our example. In this example, we will specify the patch ID as 0001 and software version as we checked before. And we will specify this is a reboot required patch as there are changes in the kernel. Then describe the detailed changes in this patch, and then specify the new rpms files to be updated to controllers and workers. We also have options to update the rpms to all nodes or to controllers or workers or storages only. Wait for a while and the 0001.patch is generated. Now we are ready with several patches. We will try to patch them into a duplex deployment. The first step is to upload the patches to StarliX using swpatch command. The first patches uploaded successfully, but there is a failure when uploading the second one. This is caused by a version conflict. This is why we need to update the TIS patch version at build time. So this time we have to skip this patch. And then the third patch is also successfully uploaded. We can check what we have till now with swpatch query and all the patches are in available status. And we can also check the details of the patches we uploaded with swpatch show like this. Besides the patches, we also need to understand the status of the StarliX hosts. We can do it with swpatch query hosts. In this list we can learn that all the hosts, including controller 1 and controller 0, are patched with the latest patch list and there is no require for reboots. In other words, everything is good and there is nothing to be updated. In order to make some changes, we will apply a patch. This operation will add the patch into the current patch list. Now the status of 0.001 becomes partial apply and the status of hosts are also changed. No for patch current and yes for reboot required. So now we can use swpatch host install to install the patch list to a specific StarliX host. But as in our example, the 0.001 patch is a reboot required patch. A lock unlock is needed for the host to be updated. In this case, we can do the following operations. Lock controller 1. Install the patches on controller 1. Unlock controller 1. After controller 1 becomes available, do a host to a SWACT and let controller 1 be the active controller. Then do the same patch in star steps for controller 0. After the installation done on all hosts, the status of the patch becomes applied while the hosts are all under good status and the related rpms are successfully updated. All these operations can also be done on StarliX dashboard, which is even easier to understand. We can check the uploaded patches in the software management panel and we can also upload patches here. We can check the details of the patch and easily apply the patch with the click on the apply patch button. Then let's move back to the host inventory panel. And the status of the hosts becomes not patch current. Then we can install patches on the hosts one by one. After that, the patch will become applied. Thanks for watching! See you next time!