Hi, Artifact deployment coordination is a very critical feature since only Carbon server/components would know whether an artifact was properly deployed. I think this is applicable for file based artifacts where a file or a set of files needs to be copied to the server and the Carbon deployer would read those files and create relevant services. Just because those files were copied does not necessarily mean that the corresponding service got created. That's why we need a mechanism to publish the status of artifacts deployed to the Carbon server.
I've few concerns regarding artifact deployment coordination - Artifact versioning support. This is important to ensure consistency across a cluster - REST API to query the status. I'd rather go ahead with a REST API before a JMS based implementation. IMO it's much simpler and easy to use. - Why don't we provide a REST API to deploy artifacts rather than copying files (whenever applicable)? We can immediately notify the client (via HTTP response status) whether artifact deployment was successful. Thanks. On Thu, Mar 31, 2016 at 3:07 PM, Ruwan Abeykoon <[email protected]> wrote: > Hi All, > Do we really want artifact deployment coordination in C5? > > What is preventing us to build the new image with the new version of > artifacts and let the k8s take care of deployment? > > Cheers, > Ruwan > > On Wed, Mar 30, 2016 at 2:54 PM, Isuru Haththotuwa <[email protected]> > wrote: > >> Hi Kasun, >> >> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe <[email protected]> >> wrote: >> >>> Hi, >>> >>> Given several issues we discovered with automatic artifact >>> synchronization with DepSync in C4, we have discussed how to approach this >>> problem in C5. >>> >>> We are thinking of not doing the automated artifact synchronization in >>> C5. Rather, users should use their own mechanism to synchronize the >>> artifacts across a cluster. Common approaches are RSync as a cron job and >>> shell scripts. >>> >>> But, it is vital to know the artifact deployment status of the nodes in >>> the entire cluster from a central place. For that, we are providing this >>> deployment coordination feature. There will be two ways to use this. >>> >>> 1. JMS based publishing - the deployment status will be published by >>> each node to a jms topic/queue >>> >>> 2. Log based publishing - publish the logs by using a syslog appender >>> [1] or our own custom appender to a central location. >>> >> Both are push mechanisms, IMHO we would need an API to check the status >> of a deployed artifacts on demand, WDYT? >> >>> >>> The log publishing may not be limited to just the deployment >>> coordination. In a containerized deployment, the carbon products will run >>> in disposable containers. But sometimes, the logs need to be backed up for >>> later reference. This will help with that. >>> >>> Any thoughts on this matter? >>> >>> [1] >>> https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender >>> >>> Thanks, >>> KasunG >>> >>> >>> >>> -- >>> ~~--~~ >>> Sending this mail via my phone. Do excuse any typo or short replies >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Ruwan Abeykoon* > *Architect,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- 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
