On Fri, Mar 7, 2014 at 1:12 PM, Sanjeewa Malalgoda <sanje...@wso2.com>wrote:
> > > > On Fri, Mar 7, 2014 at 12:28 PM, Kasun Gajasinghe <kas...@wso2.com> wrote: > >> >> >> On Friday, March 7, 2014, Sanjeewa Malalgoda <sanje...@wso2.com> wrote: >> >>> >>> >>> >>> On Fri, Mar 7, 2014 at 11:47 AM, Ajith Vitharana <aji...@wso2.com>wrote: >>> >>>> >>>> >>>> >>>> On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias <nuw...@wso2.com> wrote: >>>> >>>>> I think we should get rid of the 'gateway-worker' and >>>>> 'gateway-manager' profiles and have a 'gateway' profile only. The >>>>> worker/manager differentiation should be handled by -DworkerNode. >>>>> >>>> >>>> +1. Please re-factor this, because this should be consistence with >>>> other products. >>>> >>> Anyway we need 4 profiles for API manager even we moved gateway-worker >>> and gateway-manager in to gateway. It is make sense to have -DworkerNode >>> property for gateway profile but if we get store, publisher and key manager >>> profiles -DworkerNode property doesn't have any meaning. To be consistent >>> with other products we might need to support something like this. >>> >>> -Dprofile=gateway -DworkerNode=true >>> >>> -Dprofile=gateway -DworkerNode=false >>> >>> -Dprofile=api-key-manager >>> >>> >>> -Dprofile=api-publisher >>> >>> -Dprofile=api-store >>> >>> >>> >> +1. We need to treat profiles, and worker mode as two different concepts. >> Currently, the first two scenarios does not work since if you set >> workerNode=true, then carbon tries to start with a profile called 'worker'. >> (this is hard-coded). Since APIM does not have that profile, start-up will >> fail. We need to fix this. >> > IMO APIM should not have worker profile simply because APIM server(not > distributed mode) could not behave as worker or manager if it is not in > gateway node. In APIM case default mode should be all in one server(store, > publisher, gateway, key manager). Can you point me how user can start > gateway manager node with your suggestion? > > Yes, my comment is a little misleading. I meant to say that we should hard-code to start the server with the 'worker' profile if -DworkerNode=true is set. :) > Thanks, > sanjeewa. > > > >> >> >>> If we didn't pass -DworkerNode property it should consider as management >>> node. If you check profile creation process to support -DworkerNode=true we >>> need to create profile named worker with following tag(and another profile >>> named default to handle gateway manager scenario). >>> <profile>worker</profile> >>> >>> Then if someone tried API manager with -DworkerNode=true it will start >>> as *gateway worker*. If anyone started without it server will start in >>> default profile (which is not *gateway manager*). So IMHO we cannot go >>> for above mentioned suggestion with current profile creation process. AFAIK >>> multi profile and worker manager profile separation will not work at the >>> same time. >>> >>> >> What I suggest is that, if you only set the workerNode property then the >> server should use the default profile. If the user need a different >> profile, say gateway, then the user should set the 'profile' property along >> with the workerNode. >> > > >> >> >> >>> Thanks, >>> >>> >>> >>> sanjeewa >>> >>> >>> Thanks. >>> Ajith >>> >>> >>> Thanks, >>> NuwanD. >>> >>> >>> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda >>> <sanje...@wso2.com>wrote: >>> >>> >>> >>> >>> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana <aji...@wso2.com>wrote: >>> >>> Hi KasunG, >>> >>> >>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe <kas...@wso2.com>wrote: >>> >>> Hi, >>> >>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable >>> workerNode mode by modifying the startup script itself, instead of passing >>> -DworkerNode=true property via command-line? >>> >>> We have noticed that lot of users are passing the said property via the >>> command-line, but they sometimes miss to set that. That might lead to lot >>> of issues especially in DepSync. If we set as above, we can lower the human >>> errors. WDYT? >>> >>> >>> How this is applicable for AM ? Because they use different system >>> property to start the GW worker/manager nodes[1]. >>> >>> [1] >>> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile >>> >>> When we create multiple profiles for API manager decide to add 5 >>> profiles as APIM case is bit different compared to other servers in >>> distributed deployment. In APIM case we can set -Dprofile=gateway-worker >>> to start up script in the same way you suggested. @KasunG please >>> confirm, do we specifically check -DworkerNode=true for any scenario. >>> Otherwise it will not cause to any issue. >>> >>> Thanks, >>> sanjeewa. >>> >>> >>> Thanks. >>> Ajith >>> >>> >>> Thanks, >>> KasunG >>> >>> -- >>> *Kasun Gajasinghe* >>> Software Engineer; >>> WSO2 Inc.; http://wso2.com >>> >>> >>> , >>> *email: * >>> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >>> 678-0813* >>> *linked-in: *http://lk.linkedin.com/in/gajasinghe >>> >>> >>> >>> *blog: * <http://kasunbg.org> >>> >>> >>> >>> >>> -- >>> >>> *Sanjeewa Malalgoda* >>> Senior Software Engineer >>> WSO2 Inc. >>> Mobile : +94713068779 >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>> >>> >>> >> >> -- >> *Kasun Gajasinghe* >> Software Engineer; >> WSO2 Inc.; http://wso2.com >> >> >> , >> *email: * >> *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) >> 678-0813 <%2B94%20%2877%29%20678-0813>* >> *linked-in: *http://lk.linkedin.com/in/gajasinghe >> >> >> >> *blog: **http://kasunbg.org* <http://kasunbg.org> >> >> >> >> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> >> >> >> > > > -- > > *Sanjeewa Malalgoda* > Senior Software Engineer > WSO2 Inc. > Mobile : +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> > > > -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com <http://wso2.com> ** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* <http://kasunbg.org> *twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev