Hi, 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. > > 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? How this version > is visible to the client? How client can access different versions? > > >> >> 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. >> > > 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. > I think we already have the registry based dep sync added to trunk. IMO we should test this in next BPS release. Also there was some effort on doing file based meta file persistence for bpel artifacts. We should complete that if not done, to get dep-sync (registry/svn/git) to be working. thanks, > > 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 > > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
