Let's take DAS, which has at least 3 types of profiles ( data receivers, BAM analyzers, CEP nodes). When we build an analytics app (.car), it has configs that should go to all 3 profiles.
Best user experience is that user upload it once, and something distribute to all profile types. Otherwise, user needs to understand different cluster types etc. We can fix this by OC, or by writing a manager App that intelligently copy the artifacts to all right places. point I want to make it that this NEEDS fixing. --Srinath On Thu, May 7, 2015 at 12:33 PM, Afkham Azeez <[email protected]> wrote: > umm... no. The CApp was designed so that you can take the same CApp and > deploy on multiple clusters, and the relevant clusters will pickup the bits > they are supposed to deploy. There was never a requirement for all the > nodes deploying a single CApp to all be in the same cluster while having > different ServerRoles. > > On Thu, May 7, 2015 at 12:24 PM, Srinath Perera <[email protected]> wrote: > >> This conflicts with CApps design which is one archive for one full app, >> where we sync CApp to all the servers and each server pick up its own >> parts. >> >> --Srinath >> >> On Thu, May 7, 2015 at 10:20 AM, Manoj Kumara <[email protected]> wrote: >> >>> Hi Srinath, >>> >>> To my understanding product profiles are made to support some pre >>> defined set of functionalists. So I think better to avoid synchronizing >>> artifacts across multiple product profiles unless it is unavoidable. >>> >>> >>> Regards, >>> Manoj >>> >>> >>> *Manoj Kumara* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94713448188 >>> >>> On Thu, May 7, 2015 at 8:41 AM, Srinath Perera <[email protected]> wrote: >>> >>>> Ah sorry APIM comment is not correct, I miss understood. >>>> >>>> --Srinath >>>> >>>> On Thu, May 7, 2015 at 8:40 AM, Srinath Perera <[email protected]> >>>> wrote: >>>> >>>>> But then a side effect is that artifacts will not be sync across >>>>> different clusters. >>>>> >>>>> APIM technically breaks this by putting publisher and store in the >>>>> same machine I think. >>>>> >>>>> --Srinath >>>>> >>>>> On Wed, May 6, 2015 at 11:10 AM, Manoj Kumara <[email protected]> wrote: >>>>> >>>>>> Hi Srinath, >>>>>> >>>>>> If I understood the question properly Isn't the correct approach is >>>>>> to cluster nodes with same profile. Today we do same with the APIM >>>>>> distributed setup as well. >>>>>> >>>>>> Regards, >>>>>> Manoj >>>>>> >>>>>> >>>>>> *Manoj Kumara* >>>>>> Software Engineer >>>>>> WSO2 Inc. http://wso2.com/ >>>>>> *lean.enterprise.middleware* >>>>>> Mobile: +94713448188 >>>>>> >>>>>> On Wed, May 6, 2015 at 8:58 PM, Srinath Perera <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Sorry,the reason for error is not clear on my message. Cluster >>>>>>> messages are send as java beans, and if those classes were not in >>>>>>> listeners, there will be a error. This can happen when you have nodes >>>>>>> with >>>>>>> different profiles in the same cluster. . >>>>>>> >>>>>>> On Wed, May 6, 2015 at 8:55 PM, Srinath Perera <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Sanjiva, >>>>>>>> >>>>>>>> Had a call with Azeez, and we cannot use same cluster across >>>>>>>> multiple profiles or products. If we do, there might be error due to >>>>>>>> lack >>>>>>>> of messages to process cluster messages. >>>>>>>> >>>>>>>> That means in a deployment with multiple profiles or clusters ( >>>>>>>> like CEP, DAS nodes, Receivers) we need to copy artefacts to at least >>>>>>>> one >>>>>>>> node of each type of clusters. This is the same with car files or >>>>>>>> individual files. >>>>>>>> >>>>>>>> I think story we want to tell is >>>>>>>> >>>>>>>> 1. Build a car and Test everything in single node. >>>>>>>> 2. Copy the car file to one node in each cluster >>>>>>>> >>>>>>>> Thanks >>>>>>>> Srinath >>>>>>>> >>>>>>>> p.s. As a work around, we can run full packs instead of running >>>>>>>> profiles, and then we can have one cluster as above problem will be >>>>>>>> gone. >>>>>>>> But it is not pretty. >>>>>>>> >>>>>>>> -- >>>>>>>> ============================ >>>>>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>>>>>> Site: http://people.apache.org/~hemapani/ >>>>>>>> Photos: http://www.flickr.com/photos/hemapani/ >>>>>>>> Phone: 0772360902 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ============================ >>>>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>>>>> Site: http://people.apache.org/~hemapani/ >>>>>>> Photos: http://www.flickr.com/photos/hemapani/ >>>>>>> Phone: 0772360902 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> ============================ >>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>> Site: http://people.apache.org/~hemapani/ >>>> 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 >>> >>> >> >> >> -- >> ============================ >> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >> Site: http://people.apache.org/~hemapani/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919>blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez* > <http://twitter.com/afkham_azeez> > *linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
