+1 for Chanaka's suggestion if that possibility is there to have one node with both worker/manager roles.
Regards, Dilan. *Dilan U. Ariyaratne* Software Engineer WSO2 Inc. <http://wso2.com/> Mobile: +94775149066 lean . enterprise . middleware On Thu, Dec 4, 2014 at 12:05 PM, Chanaka Fernando <[email protected]> wrote: > Hi Isuru, > > If we take the JMS listener proxy scenario with a worker/manager concept, > user need to view whether this artifact is deployed in the worker node by > looking at the manager node. In the meantime, he needs that JMS listener > proxy only runs on the worker node but not it the management node. Pinned > server approach is not possible in this scenario since that particular > artifact is not shown in the management node if we do not add that node as > a pinned server. > > I think only possibility is to use the manager node as both worker/manager > and keep the other nodes as workers. > > WDYT? > > Thanks, > Chanaka > > > > > On Thu, Dec 4, 2014 at 11:47 AM, Isuru Udana <[email protected]> wrote: > >> >> >> On Thu, Dec 4, 2014 at 11:41 AM, Chanaka Fernando <[email protected]> >> wrote: >> >>> Hi Isuru, >>> >>> I agree with what you are saying. We need to have the same artifacts >>> deployed in both worker and manager nodes. This is a requirement which came >>> with the JMS listener proxy use case. I think the best solution for this >>> kind of scenario would be to use the management node as both worker/manager >>> profile. That would make sure that it will serve the requests as well as >>> capable of doing the management tasks. >>> >> +1. This might be the best solution we have with 4.8.1. >> >>> >>> WDYT? >>> >>> Thanks, >>> Chanaka >>> >>> On Thu, Dec 4, 2014 at 11:33 AM, Isuru Udana <[email protected]> wrote: >>> >>>> Hi Chanaka, >>>> >>>> I think we may able to achieve your this particular requirement using >>>> the pinned server concept. >>>> >>>> IMO we should not make differences to artifact deployment in worker >>>> nodes vs manager node. If we do that, we won't be able to clearly see what >>>> is actually deployed in workers by looking at the manager node. It will add >>>> an extra overhead when it comes to troubleshooting. So deployment wise all >>>> the artifacts should be identical and we need some other mechanism to >>>> prevent execution in the manager. >>>> >>>> Thanks. >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Dec 4, 2014 at 10:51 AM, Imesh Gunaratne <[email protected]> >>>> wrote: >>>> >>>>> Hi Chanaka, >>>>> >>>>> This looks like a valid requirement. >>>>> May be we could achieve this by defining two different server roles in >>>>> manager and worker nodes (in carbon.xml file): >>>>> >>>>> In management nodes: >>>>> <ServerRoles> >>>>> <Role>EnterpriseServiceBusManager</Role> >>>>> </ServerRoles> >>>>> >>>>> In worker nodes: >>>>> <ServerRoles> >>>>> <Role>EnterpriseServiceBusWorker</Role> >>>>> </ServerRoles> >>>>> >>>>> Afterwards we could define the role EnterpriseServiceBusWorker to all >>>>> the artifacts that should only be deployed in workers. WDYT? >>>>> >>>>> Thanks >>>>> >>>>> On Thu, Dec 4, 2014 at 7:53 AM, Chanaka Fernando <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Is it possible to do $subject? Requirement is to deploy the same >>>>>> artifact in 2 different servers with the same CAR file. >>>>>> >>>>>> As an example, when we have a JMS listener proxy in our CAR file and >>>>>> we have a worker/manager separated cluster with dep-sync enabled, once we >>>>>> deploy this CAR file in the manager node, It would be deployed there and >>>>>> synced to the worker node. But in this scenario, we do not need the JMS >>>>>> listener proxy in the management node to listen to the JMS queue. But If >>>>>> we >>>>>> have the same "ServerRole" in both worker/manager nodes, they will be >>>>>> deployed and we have to manually stop the proxy service from management >>>>>> node. >>>>>> >>>>>> If we have a capability like defining multiple server roles in >>>>>> artifact.xml file, we can avoid this behavior by having two different >>>>>> "ServerRoles" for worker and manager and then defining both ServerRoles >>>>>> in >>>>>> the required artifacts and defining only one server role for JMS listener >>>>>> proxy. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> Chanaka >>>>>> >>>>>> >>>>>> -- >>>>>> -- >>>>>> Chanaka Fernando >>>>>> Technical Lead >>>>>> WSO2, Inc.; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> mobile: +94 773337238 >>>>>> Blog : http://soatutorials.blogspot.com >>>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>>>>> Twitter:https://twitter.com/chanakaudaya >>>>>> Wordpress:http://chanakaudaya.wordpress.com >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Imesh Gunaratne* >>>>> Technical Lead >>>>> WSO2 Inc: http://wso2.com >>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>> W: http://imesh.gunaratne.org >>>>> Lean . Enterprise . Middleware >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Isuru Udana* >>>> Senior >>>> *Software Engineer* >>>> WSO2 Inc.; http://wso2.com >>>> email: [email protected] cell: +94 77 3791887 >>>> blog: http://mytecheye.blogspot.com/ >>>> twitter: http://twitter.com/isudana >>>> >>> >>> >>> >>> -- >>> -- >>> Chanaka Fernando >>> Technical Lead >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 773337238 >>> Blog : http://soatutorials.blogspot.com >>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>> Twitter:https://twitter.com/chanakaudaya >>> Wordpress:http://chanakaudaya.wordpress.com >>> >>> >>> >>> >> >> >> -- >> *Isuru Udana* >> Senior >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> twitter: http://twitter.com/isudana >> > > > > -- > -- > Chanaka Fernando > Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > Wordpress:http://chanakaudaya.wordpress.com > > > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
