On Wed, Jun 8, 2016 at 5:42 PM, Akila Ravihansa Perera <[email protected]> wrote:
> Hi KasunG, > > How do you handle multiple manager scenario (for HA deployment) with the > implementation that you have done? And what do you mean by standalone > cluster mode? > > What I meant was that this is for clustered deployments that are not deployed on containers. A typical standard cluster. > If we run this cron job on multiple managers then it can cause overwrites > unless there is some kind of cluster coordination right? > Active-active multiple managers are not easy handle with rsync as I see since you can't sync the folders in a bi-directional manner. In cases like that, some kind of version control system is needed. This is where the SVN based depsync comes in. > > Thanks. > > > On Wednesday, 8 June 2016, KasunG Gajasinghe <[email protected]> wrote: > >> >> We've also written rsync based artifact synchronization for the >> stand-alone cluster mode. [1] This pushes the artifacts to workers >> periodically via a cron job. A shared public key is used for >> authentication. >> >> [1] https://gist.github.com/kasunbg/444df28a2e51a16bbd74 >> >> On Wed, Jun 8, 2016 at 5:05 PM, Akila Ravihansa Perera < >> [email protected]> wrote: >> >>> Hi Manoj, >>> >>> How are those multiple managers going to sync artifacts between each >>> other using rsync? LB will route traffic only to 1st manager node and the >>> 2nd manager node as the fail-over, right? If all the managers try to push >>> artifacts to workers then there will be conflicts/overwrites. >>> >>> >>> I think the whole artifacts deployment/sync strategy is going to be >>> changed from C5 on-wards. AFAIU, we will not be publishing artifacts to >>> gateway nodes directly in C5. Rather those artifacts will be injected at >>> the Docker image build process. So why don't we stick with SVN based >>> DepSync for now (C4 products)? What is the problem that we are trying to >>> solve by moving to rsync that we couldn't/cannot fix in SVN based model? >>> >>> Thanks. >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
