Hi all,
In the proposed Patching mechanism for Carbon C5 based Servers, we are hoping to overcome some of the limitations in the Carbon 4 based patching model. Some limitations in the carbon 4 based patching mechanism 1. Can only patch OSGi bundles 2. Server always has to be restarted in order to the patch to be affected In the new Solution we are hoping to introduce the following features/improvements 1. Install patches on the fly ( install hot patches) 2. Revert patches on the fly ( revert hot patches) 3. Patch multiple file types e.g OSGi bundles , config files , *.jar files, *.jag files, *.properties files, *.xml file etc Whenever a newly applied, the server not have to be restarted in order to the patch to be affected. (For some scenarios requirement of a server restart may not be unavoidable for e.g a config file ) In this model we are hoping to follow the following format for a patch file. A patch is a zip file, which consist of the below items, 1. A descriptor file (a xml file that contains the details about the patch files) 2. One or more patch files to be applied to the server Lets take an example patch file Consider a sample patch, org.wso2.carbon.clustering_5.0.0.jar , carbon.xml to be applied to the server. Then the patch file name will be a zip file called patch00001.zip. (The name has to be the patchXXXXX.zip where XXXXX has to be the largest number in the patch folder) In this instance the zip file will contain three files, 1. descriptor.xml 2. org.wso2.carbon.clustering_5.0.0.jar 3. carbon.xml The Patch zip would be like, descriptor.xml When the patch is applied the /c5-home/repository/patches folder - unzip the patch0001.zip to the folder to */c5-home/tmp* folder - Original Files will be backed up in the /c5-home/repository/backup folder - Apply the patch list in the patch00001.zip file - If a single patch file is failed all the patches in the patch00001.zip is reverted I would like to know your suggestions and thoughts on proposed solution for the C5 patching mechanism. The document prepared for the Solution for Patching C5 Carbon servers can be found here [1]. [1]. https://docs.google.com/a/wso2.com/document/d/1wz-2dURyaInm3nu8f7__TLEOF1ScLhs3hsDAV_pkai4/edit?usp=sharing Regards, -- * Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: [email protected] | Web: www.wso2.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
