Hi Sagara, That's not a dummy node, it used to do some sort of governance and that's the real registry node and other two nodes behave as Management nodes. This kind of deployment pattern propose by Greg team to avoid the subscription related issues.
@Senaka and Ajith, please elaborate more details about this deployment pattern. Regards, Aparna. On Tue, Aug 4, 2015 at 5:29 PM, Sagara Gunathunga <[email protected]> wrote: > > > On Tue, Aug 4, 2015 at 5:26 PM, Chandana Napagoda <[email protected]> > wrote: > >> HI Evanthika/Chalitha, >> >> In most cases there is no dummy node to manage the subscriptions. There >> you have to define "mgtHost" and "remoteinstance" properly. But better to >> validate other scenarios as well. >> > > I'm curious to know what is 'dummy node" concept here, can someone > explain ? > > Thanks ! > >> >> Regards, >> Chandana >> >> On Tue, Aug 4, 2015 at 5:01 PM, Evanthika Amarasiri <[email protected]> >> wrote: >> >>> Hi Shazni, >>> >>> On Tue, Aug 4, 2015 at 4:01 PM, Shazni Nazeer <[email protected]> wrote: >>> >>>> Hi Pubudu, >>>> >>>> There are few ways you can do the testing. In addition to the two >>>> methods you have mentioned >>>> >>> >>> As per the offline discussion I had with Chandana, we were under the >>> impression that a dummy node is not required and we don't recommend this >>> topology anymore. Can you please confirm? >>> >>> >>> >>>> following basic clustering topologies can be used as well. >>>> >>>> Two G-Reg nodes in cluster without fronting with a load balancer >>>> Two G-Reg nodes in cluster without fronting with load balancer >>>> One G-Reg instance with just a jdbc mount (This is not a clustered >>>> scenario) >>>> >>>> For your second question, from G-Reg 5.0.0 inwards, API-M related >>>> scripts won't be packed in the G-Reg server by default. It'll only be >>>> available if you install API-M features on top of G-Reg. Nevertheless, for >>>> clustering to work, you do not necessarily need to have a datasource >>>> configuration for API-M db. So that part can be omitted in the default >>>> pack. >>>> >>>> This would need to be reflected in the doc as well [1] >>>> >>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2109 >>>> >>>> Shazni Nazeer >>>> Mob : +94 777737331 >>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>> Blog : http://shazninazeer.blogspot.com >>>> >>>> On Tue, Aug 4, 2015 at 1:13 PM, Pubudu Priyashan <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> We are currently testing the GREG clustering setup for 5.0.0. >>>>> >>>>> 1. Previously in 4.6 GREG version the recommended setup was with three >>>>> GREG instances with one dummy node and the registry mount. >>>>> But in 5.0.0 we've been told to test the clustering set up with two >>>>> GREG manager nodes using one IS instance as the external IDP with user >>>>> store and registry mount. >>>>> >>>>> Can you please confirm what is the recommended set up for GREG 5.0.0 >>>>> and the document link? >>>>> >>>>> >>>>> 2. Also in GREG clustering tutorial with nginx[1], it requires user to >>>>> access '$GREG_HOME/dbscripts/apimgt/mysql.sql' location. But apimgt >>>>> directory is not available in GREG 5.0.0 version by default. Do we need to >>>>> update the document [1] to reflect most recent clustering setup? >>>>> >>>>> Appreciate your advise on above two questions. Thanks. >>>>> >>>>> [1] >>>>> https://docs.wso2.com/display/CLUSTER420/Clustering+Governance+Registry+with+Nginx#ClusteringGovernanceRegistrywithNginx-Environment >>>>> >>>>> >>>>> Best Regards, >>>>> Pubudu D.P >>>>> Senior Software Engineer - QA Team | WSO2 inc. >>>>> Mobile : +94775464547 >>>>> >>>> >>>> >>> >> >> >> -- >> *Chandana Napagoda* >> Senior Software Engineer >> WSO2 Inc. - http://wso2.org >> >> *Email : [email protected] <[email protected]>**Mobile : +94718169299 >> <%2B94718169299>* >> >> *Blog : http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>* >> >> > > > -- > Sagara Gunathunga > > Architect; WSO2, Inc.; http://wso2.com > V.P Apache Web Services; http://ws.apache.org/ > Linkedin; http://www.linkedin.com/in/ssagara > Blog ; http://ssagara.blogspot.com > > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
