Hi All, This is the planned approach to resolve this BPS-139<https://wso2.org/jira/browse/BPS-139>[Keep process deployment related meta data in a file instead of registry, and synchronize across the cluster]
- meta files will be save to repository/deployment/server/bpelmetafiles directory. - When we first deploy a bpel process, a meta file will be created in the bpelmetafiles directory with *$packageName-$processVersion* - It contains the deploy.xml contents and the md5sum for the bpel zip - Reason for adding deploy.xml (dd) contents to a meta file is, deployment descriptor can be edited via UI, in that case there won't be new process version created, so that the same meta file needs to be updated for the new values in dd config. - If you modify the bpel zip, it creates a new version of the package. We create a new meta file *$packageName-$newProcessVersion* bpel meta files and bpel package deployment directory will be synced via the deployment synchronizer across the cluster. Welcome any thoughts on this. Thanks Thilini On Tue, Jul 9, 2013 at 12:40 PM, Thilini Ishaka <[email protected]> wrote: > > Hi Amila, > On Sat, Jun 8, 2013 at 4:58 PM, Amila Suriarachchi <[email protected]> wrote: > >> >> >> >> On Fri, Jun 7, 2013 at 10:08 PM, Nandika Jayawardana <[email protected]>wrote: >> >>> Actually, this is a pending item. Storing .zip files to registry was >>> done for sharing the artifacts across the cluster and for process >>> versioning purpose. >>> >> >> As I understood the version here means the artifact version. >> > Yes (BPEL package version). > >> >> Lets say in my dev environment I deployed one bpel process and due to >> some issue in that artefact I deployed that with the fix again. In this >> case does the second bpel process deployed as a newer version? >> > Yes > >> How this version is visible to the client? How client can access >> different versions? >> > Only the latest package version is in 'Active' state while the others > (previous versions of the same package) in 'Retired' state. When you send a > request to the process ep, it will hit the latest version. > But still you can communicate to older *instances* (active instances) > created by retired packages. > This information is not visible to the client,but an implementation detail. > > >> >>> >>> If we get rid of storing the bpel artifacts in registry, we will have to >>> keep the versioning information in the mata files. Then we will have to >>> make using dep sync mandatory for bps clustering in order to make >>> versioning work. However, there are customers who does not want to install >>> svn in their prod environments. >>> >> We have started https://wso2.org/jira/browse/BPS-139 and will send a > note on the planned approach. > > Thanks > Thilini > >> >> So in a BPS cluster when an artifact uploaded to a master node it writes >> the .zip file to registry. Now how the worker nodes pick this .zip file and >> deployed in their environment? >> >> For svn problem the solution is to write a registry based deployment >> synchroniser. i.e we try to provide the .svn functionality using registry. >> >> thanks, >> Amila. >> >> >> >> >>> >>> Regards >>> Nandika >>> >>> On Sat, Jun 8, 2013 at 4:58 AM, Amila Suriarachchi <[email protected]>wrote: >>> >>>> hi, >>>> >>>> During the BPS clustering we saw that BPS try to save the bpel files to >>>> the registry. I believe this is done to share a the .zip file artefacts >>>> among the nodes. Why can't we simply use the dep sync for that? >>>> >>>> thanks, >>>> Amila. >>>> >>>> -- >>>> *Amila Suriarachchi* >>>> >>>> Software Architect >>>> WSO2 Inc. ; http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> phone : +94 71 3082805 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Nandika Jayawardana >>> Senior Technical Lead >>> WSO2 Inc ; http://wso2.com >>> lean.enterprise.middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Amila Suriarachchi* >> >> Software Architect >> WSO2 Inc. ; http://wso2.com >> lean . enterprise . middleware >> >> phone : +94 71 3082805 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Thilini Ishaka > Senior Software Engineer** > WSO2 Inc. http://wso2.com* > *bolg: thiliniishaka.blogspot.com* > *linkedin: http://lk.linkedin.com/in/thiliniishaka* > *twitter: https://twitter.com/#!/ThiliniIsh* > -- *Thilini Ishaka Senior Software Engineer** WSO2 Inc. http://wso2.com* *bolg: thiliniishaka.blogspot.com* *linkedin: http://lk.linkedin.com/in/thiliniishaka* *twitter: https://twitter.com/#!/ThiliniIsh*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
