Differences

This shows you the differences between two versions of the page.

--- cloudappliance/patches [2018_01_30 17:23] – external edit 127.0.0.1
+++ cloudappliance:patches [2023_06_22 05:41] – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== How To Apply a Patch ======
+== last updated on Sept. 27, 2021 ==
-  - Copy the patch file PATCH_FILE.tgz to the appliance using scp or any other tool
+<WRAP center round info 100%>
-  - ssh into the appliance as smeconfiguser
+See [[cloudappliance/patchingbp|this page]] for patching best practices.
-  - su to root su - root
+</WRAP>
-  - cd to var/www/smestorage/patches cd /var/www/smestorage/patches
-  - move the copied patch file to /var/www/smestorage/patches mv /home/smeconfiguser/PATCH_FILE.tgz .
+===== About File Fabric Patches =====
-  - chown of the file to smestorage chown smestorage:smestorage PATCH_FILE.tgz
+Patches are small changes that are confined to one or a few pieces of the File Fabric's code.  They are almost always issued for the purpose of resolving an issue that is affecting one or a small number of customers.  The patches are only provided to the affected customers. Customers who are not affected by the issue that a patch resolves need not concern themselves with the patch.
-  - su to smestorage su - smestorage
-  - cd to patches cd patches
+SME seldom issues patches, preferring to combine sets of changes into service packs which we release frequently. On those occasions when we do see fit to issue a patch, the changes included in the patch are always included in a subsequent service pack. In most cases this will be the next service pack to be released after the patch was developed.
-  - Apply the patch ./patch -patch PATCH_FILE.tgz
-  - Run any required Database migrations or schema updates php ../upgrade/dbupgrade.php
+===== How Patches are Provided =====
+If a patch is appropriate for your File Fabric then SME will provide you with a link to a compressed tar file //<patch_name>.tgz// containing the patch.
+===== Patching Steps =====
+Note that these steps should be completed for each appliance in a multi-node (HA) system.
+  * Copy the patch file PATCH_FILE.tgz to the appliance using scp or any other tool
+  * ssh into the appliance as smeconfiguser
+  - su to root
+''su - root''
+    * cd to var/www/smestorage/patches
+''cd /var/www/smestorage/patches''
+    * move the copied patch file to /var/www/smestorage/patches
+''mv /home/smeconfiguser/PATCH_FILE.tgz .''
+    * change the owner of the file to smestorage
+''chown smestorage:smestorage PATCH_FILE.tgz''
+  *  su to smestorage
+''su - smestorage''
+   * cd to patches
+''cd patches''
+   * Apply the patch
+''./patch -patch PATCH_FILE.tgz''
 If you encounter any issues during these steps, please contact Support.
@@ Line 16: / Line 46: @@
 ===== To Roll Back a Patch =====
-  - su to root su - root
+  * su to root
-  - su to smestorage su - smestorage
-  - cd to patches cd patches
+''su - root''
-  - Roll back the patch ./patch -rollback
+   * su to smestorage
+''su - smestorage''
+    * cd to patches
+''cd patches''
+    * Roll back the patch
+''./patch -rollback''