Can someone from Carbon team please explain why 2nd approach is better and what is meant by "*We will no longer be doing async deployments.*"?
* Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 On Fri, Aug 2, 2013 at 3:06 PM, Srinath Perera <[email protected]> wrote: > pls chat with Harshana .. we may have to do some tools > > > On Fri, Aug 2, 2013 at 2:38 PM, Anjana Fernando <[email protected]> wrote: > >> Hi, >> >> On Fri, Aug 2, 2013 at 2:30 PM, Srinath Perera <[email protected]> wrote: >> >>> If artifacts deployed as a car file initially, you need to repack the >>> car >>> >>> If you deploy it directly to the deployment folder as the artifact, not >>> as the car, then you can change that in the file system. >>> >> >> OK, yeah, but the thing is, is this already done by others? .. as in .. >> we have to keep this metadata somewhere to say where it came from, to use >> it when we are editing/updating an artifact, and there needs to be some >> utilities to re-pack the car file and all. >> >> Cheers, >> Anjana. >> >> >>> >>> --Srinath >>> >>> >>> On Fri, Aug 2, 2013 at 2:21 PM, Anjana Fernando <[email protected]> wrote: >>> >>>> Hi Srinath, >>>> >>>> On Fri, Aug 2, 2013 at 2:00 PM, Srinath Perera <[email protected]>wrote: >>>> >>>>> We should go with the #2 as Harshana mentioned. >>>>> >>>>> We want to deploy car without exploding to deployment directories, >>>>> otherwise a) delete is hard b) when dep sync get confused. >>>>> >>>> >>>> Well . what about my concerns I mentioned earlier .. there will be >>>> scenarios we need to have the deployment artifacts in the file system, like >>>> editing/saving it, like how are we going to handle that? .. are we suppose >>>> to put those changes back into the car file? .. and where we get problems >>>> like if this artifact came from an original car file or not. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>>> >>>>> --Srinath >>>>> >>>>> >>>>> On Fri, Aug 2, 2013 at 1:51 PM, Anjana Fernando <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> On Fri, Aug 2, 2013 at 1:34 PM, Harshana Martin <[email protected]>wrote: >>>>>> >>>>>>> Hi Sinthuja, >>>>>>> >>>>>>> >>>>>>> On Friday, August 2, 2013, Sinthuja Ragendran wrote: >>>>>>> >>>>>>>> Hi Ayashkantha, >>>>>>>> >>>>>>>> You should use the first approach IMO. We don't need duplicate the >>>>>>>> code for deploying the toolboxes. It'll become unmanageable and it >>>>>>>> won't be >>>>>>>> consistent also. >>>>>>>> >>>>>>>> Generally we follow the first method, as cApp will copy the >>>>>>>> artifacts in the respective servers' deployment directory, >>>>>>>> >>>>>>> >>>>>>> From Carbon 4.2.0 onward this is going to change. We will no longer >>>>>>> be doing async deployments. >>>>>>> >>>>>> >>>>>> What does that actually mean? .. the CAR deployment itself is async >>>>>> right? .. and also, what about the scenarios where we expect the actual >>>>>> artifact to be in the deployment directory, for example, data services, >>>>>> proxy services and all, because the user will be editing those and >>>>>> deploying again, and those changes will reflect in their deployment >>>>>> directories. >>>>>> >>>>>> Cheers, >>>>>> Anjana. >>>>>> >>>>>> >>>>>>> >>>>>>> Kishanthan will be able to provide more info on these changes. >>>>>>> >>>>>>> Thanks and Regards, >>>>>>> Harshana >>>>>>> >>>>>>>> and the specific deployer will handle the deployment logic for that >>>>>>>> artefact. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Sinthuja. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Aug 2, 2013 at 1:11 PM, Ayashkantha Ramasinghe < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> The "BAM car file deployer" is created to deploy toolboxes in the >>>>>>>>> server as a cApp. I have two approaches, >>>>>>>>> >>>>>>>>> 1. to copy the toolbox to bam-toolbox directly and let the toolbox >>>>>>>>> deployer run automatically and deploy the toolbox. >>>>>>>>> 2. to deploy the toolbox using the code while deploying cApp >>>>>>>>> without copying the toolbox to bam-toolbox directory directly. >>>>>>>>> >>>>>>>>> In 1st approach, we can go and manually see the toolbox deployed >>>>>>>>> inside the directory, bam-toolbox. But, in the 2nd approach, we can't >>>>>>>>> see >>>>>>>>> or undeploy it manually, only cApp undeployment does the undeployment >>>>>>>>> of >>>>>>>>> the toolbox. >>>>>>>>> >>>>>>>>> I am also thinking that the 1st approach is good, but, for now, >>>>>>>>> the deployer is created based on the 2nd approach. >>>>>>>>> >>>>>>>>> WDYT??? >>>>>>>>> >>>>>>>>> Thank you >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Ayashkantha Ramasinghe >>>>>>>>> Software Engineer >>>>>>>>> >>>>>>>>> Tel: +94 777 487 669 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Sinthuja Rajendran* >>>>>>>> Software Engineer <http://wso2.com/> >>>>>>>> WSO2, Inc.:http://wso2.com >>>>>>>> >>>>>>>> Blog: http://sinthu-rajan.blogspot.com/ >>>>>>>> Mobile: +94774273955 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Harshana Martin >>>>>>> Associate Technical Lead >>>>>>> WSO2 Inc. : http://wso2.com >>>>>>> >>>>>>> Mobile: +94 775 998 115 >>>>>>> Profile: https://www.google.com/profiles/harshana05 >>>>>>> Blog: http://harshana05.blogspot.com >>>>>>> Twitter: http://twitter.com/harshana05 >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Anjana Fernando* >>>>>> Technical Lead >>>>>> WSO2 Inc. | http://wso2.com >>>>>> lean . enterprise . middleware >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ============================ >>>>> Srinath Perera, Ph.D. >>>>> http://people.apache.org/~hemapani/ >>>>> http://srinathsview.blogspot.com/ >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Technical Lead >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> ============================ >>> Srinath Perera, Ph.D. >>> Director, Research, WSO2 Inc. >>> Visiting Faculty, University of Moratuwa >>> Member, Apache Software Foundation >>> Research Scientist, Lanka Software Foundation >>> Blog: http://srinathsview.blogspot.com/ >>> Photos: http://www.flickr.com/photos/hemapani/ >>> Phone: 0772360902 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Anjana Fernando* >> Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > ============================ > Srinath Perera, Ph.D. > Director, Research, WSO2 Inc. > Visiting Faculty, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > Photos: http://www.flickr.com/photos/hemapani/ > Phone: 0772360902 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
