Hi all, According to the new BAM deployment architecture (discussed in architecture mailing list thread titled "Moving 2 BAM dashboard nodes to DMZ") this issue does not exists. One of the receiver/analyzer BAM node can be configured as the RW node and all other BAM nodes can be RO nodes. The issue is solved as both toolbox artifacts and receiver artifacts can be deployed from this RW node where dashboard nodes have nothing to commit from them.
*Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : [email protected] *Skype* : @manindae *Twitter* : @maninda On Thu, Oct 30, 2014 at 10:01 PM, Anjana Fernando <[email protected]> wrote: > Hi, > > Having two repos is not a solution. We have to make sure the setup is as > simple as possible, it is already pretty complicated, we don't want to add > anything more. So please make sure, it works in a simple way. > > Cheers, > Anjana. > > On Thu, Oct 30, 2014 at 1:58 AM, Gihan Anuruddha <[email protected]> wrote: > >> One solution is to have two repos. Other solution is to use the RW node >> to create both adapters and toolboxes and make other nodes RO. Even though >> we categorized these nodes as receiver/analyzer, we can use one manager >> node to do adapter changes and toolbox changes. >> >> @Aparna, >> >> Can you try the latter solution. >> >> Regards, >> Gihan >> >> On Thu, Oct 30, 2014 at 1:20 PM, Sriskandarajah Suhothayan <[email protected] >> > wrote: >> >>> Hi Gihan >>> >>> So want this make the deployment process complicated? >>> We have to now update 2 servers to add streams. >>> >>> Regards >>> Suho >>> >>> >>> On Wed, Oct 29, 2014 at 11:37 PM, Gihan Anuruddha <[email protected]> >>> wrote: >>> >>>> Hi Anjana, >>>> >>>> Can't we create two repositories, one for analyzer and one for >>>> receiver regarding this issue? Because analyzers and receivers don't have >>>> any common features and those two run independently. Since we are >>>> maintaining a two repos, I believe we can have two RW node. >>>> >>>> WDYT? >>>> >>>> Regards, >>>> Gihan >>>> >>>> On Thu, Oct 30, 2014 at 4:23 AM, Anjana Fernando <[email protected]> >>>> wrote: >>>> >>>>> On Wed, Oct 29, 2014 at 10:34 AM, Sriskandarajah Suhothayan < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Oct 29, 2014 at 7:27 AM, Aparna Karunarathna <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> Hi Anjana/KasunG/suho, >>>>>>> >>>>>>> According to the new BAM 2.5.0 deployment pattern [1] we have >>>>>>> configured the BAM cluster with 11 nodes(4 cassandra, 3 hadoop, 2 >>>>>>> analyzer >>>>>>> and 2 receiver). Since BAM 2.5.0 is releasing with CEP features, we >>>>>>> have to >>>>>>> enable the dep sync for receiver nodes as well. Therefore one of the >>>>>>> Analyzer/Receiver nodes were configured as RW nodes and other >>>>>>> analyzer/receiver nodes were configured as RO nodes and pointed to a >>>>>>> single >>>>>>> svn repo. >>>>>>> >>>>>>> Toolboxes can be deployed to the Analyzer RW node and CEP input >>>>>>> adapters to the Receiver RW node. We have seen svn conflicts when both >>>>>>> RW >>>>>>> nodes were trying to commit to svn repo. >>>>>>> >>>>>>> Therefore, how to configure the Dep Sync for Analyzer/Receiver nodes >>>>>>> in BAM 2.5.0 clustered setup? Please advice. >>>>>>> >>>>>> >>>>>> We cant have two RW nodes in a single cluster. Here we have to first >>>>>> find out a node that has both CEP and Toolbox deployment components and >>>>>> make that the RW node to make this work, I'm not sure either >>>>>> Analyzer/Receiver profiles have both CEP and Toolbox deployment >>>>>> components, >>>>>> If its not the case we have to fix the BAM profile. >>>>>> >>>>> >>>>> @Gihan, please note, check and fix if needed. >>>>> >>>>> Cheers, >>>>> Anjana. >>>>> >>>>> >>>>>> >>>>>> Regards >>>>>> Suho >>>>>> >>>>>> >>>>>>> >>>>>>> [1] >>>>>>> https://docs.wso2.com/display/CLUSTER420/Deploying+BAM+with+Puppet >>>>>>> >>>>>>> >>>>>>> Regards, >>>>>>> -- >>>>>>> *Aparna Karunarathna.* >>>>>>> >>>>>>> >>>>>>> *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533 >>>>>>> <0714002533>* >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *S. Suhothayan* >>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>> *WSO2 Inc. *http://wso2.com >>>>>> * <http://wso2.com/>* >>>>>> lean . enterprise . middleware >>>>>> >>>>>> >>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>> linked-in: >>>>>> http://lk.linkedin.com/in/suhothayan >>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Anjana Fernando* >>>>> Senior Technical Lead >>>>> WSO2 Inc. | http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> W.G. Gihan Anuruddha >>>> Senior Software Engineer | WSO2, Inc. >>>> M: +94772272595 >>>> >>> >>> >>> >>> -- >>> >>> *S. Suhothayan* >>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>> *WSO2 Inc. *http://wso2.com >>> * <http://wso2.com/>* >>> lean . enterprise . middleware >>> >>> >>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >>> >> >> >> >> -- >> W.G. Gihan Anuruddha >> Senior Software Engineer | WSO2, Inc. >> M: +94772272595 >> > > > > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
