Re: [Architecture] carbon native linux platform packages

2014-01-10 Thread Geeth Munasinghe
Yes, It is because JVM isolation. I was thinking about the production environments which will give more robust if we use separate JVMs for separate servers. As you have mentioned It can be done using LXC container. Thanks. *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com

Re: [Architecture] carbon native linux platform packages

2014-01-08 Thread chris snow
Did my previous email make any sense? Is the recommendation to install separate servers because of JVM isolation, or is there another reason? On Wed, Jan 8, 2014 at 11:25 AM, chris snow chsnow...@gmail.com wrote: What is the driver for recommending to install separate servers for each

Re: [Architecture] carbon native linux platform packages

2014-01-07 Thread chris snow
Hi Lasantha, I'm hoping that it would be possible to automate installing carbon core and also automate installing features. My hope is that features would be able to coexist on the same carbon core platform without interfering with each other. It should be up to the administrator to decide

Re: [Architecture] carbon native linux platform packages

2014-01-07 Thread Geeth Munasinghe
+1 Interesting idea. I think installing features on carbon kernel will not be flexible thing here. Instead we should package a single server to install. Because if some one wants to install both ESB and App Server as separate servers on the same machine, then person has to install carbon kernal

Re: [Architecture] carbon native linux platform packages

2014-01-06 Thread chris snow
Today I was thinking of more examples to help explain my previous email. Here is one example from the eclipse world: Package: eclipse-jdt (3.8.0~rc4-1) - http://packages.debian.org/wheezy/eclipse-jdt dep: default-jre Standard Java or Java compatible Runtime or java5-runtime virtual package