Re: [Architecture] Multiple profile support for C5 based products.

2016-10-26 Thread Manuranga Perera
AFAIK most customers don't run the single profile we provide. EG: sometime store+publisher in a single node make scene, sometimes store alone is better, same thing for keymanger+tragicmanger. So isn't it better if we can individually turn them on and off. EG: ./server.sh -profiles store,publisher

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Afkham Azeez
Please note that during a discussion this week, we decided that instead of all carbon servers running on the same ports, each of the 5 products will have their own well known ports. For example, APIM GW port will be 8084 (just an example). So while we would still have portOffset support, we won't n

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Muhammed Shariq
The options are either build all the different distributions at runtime itself or provide a tool to create the different runtime from a base distribution. If we build all the individual runtimes at build time and package it into a single archive, the download time will be bigger cz there'll be many

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Nuwan Dias
On Wed, Oct 12, 2016 at 11:09 PM, Imesh Gunaratne wrote: > > > On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: > >> Do we really need multi-profile support (at an osgi level) on C5? What if >> we have separate dedicated runtimes per profile? Which means that we have a >> gateway runtime, stor

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Nuwan Dias
On Wed, Oct 12, 2016 at 7:36 PM, Kishanthan Thangarajah wrote: > > > On Wed, Oct 12, 2016 at 7:00 PM, Nuwan Dias wrote: > >> >> >> On Wed, Oct 12, 2016 at 6:55 PM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> >>> >>> On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: >>>

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Imesh Gunaratne
On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: > Do we really need multi-profile support (at an osgi level) on C5? What if > we have separate dedicated runtimes per profile? Which means that we have a > gateway runtime, store runtime, etc. within the same distribution? Each > will run on its

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Kishanthan Thangarajah
On Wed, Oct 12, 2016 at 7:00 PM, Nuwan Dias wrote: > > > On Wed, Oct 12, 2016 at 6:55 PM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> >> >> On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: >> >>> Do we really need multi-profile support (at an osgi level) on C5? What >>> if we h

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Nuwan Dias
On Wed, Oct 12, 2016 at 6:55 PM, Kishanthan Thangarajah wrote: > > > On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: > >> Do we really need multi-profile support (at an osgi level) on C5? What if >> we have separate dedicated runtimes per profile? Which means that we have a >> gateway runtime

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Kishanthan Thangarajah
On Wed, Oct 12, 2016 at 6:29 PM, Nuwan Dias wrote: > Do we really need multi-profile support (at an osgi level) on C5? What if > we have separate dedicated runtimes per profile? Which means that we have a > gateway runtime, store runtime, etc. within the same distribution? Each > will run on its

Re: [Architecture] Multiple profile support for C5 based products.

2016-10-12 Thread Nuwan Dias
Do we really need multi-profile support (at an osgi level) on C5? What if we have separate dedicated runtimes per profile? Which means that we have a gateway runtime, store runtime, etc. within the same distribution? Each will run on its own port, maybe using offsets by default (no need to worry ab