I am curious, why exactly do you want to co-locate? What are the requirements imposed by your legacy app?
There might be different solutions for different problems (e.g., bind-mount a shared filesystem into the the sandbox, setup reverse proxies to allow communication via localhost etc...) Regards, Stephan ________________________________________ From: Bill Farner <wfar...@apache.org> Sent: Wednesday, December 2, 2015 9:34 PM To: dev@aurora.apache.org Subject: Re: Colocate services support in Aurora Two options come to mind: - configure them as separate processes within the same job. Downside is that they will contend for resources (though in your case, this may already be an issue). - designate specific mesos machines for them using the dedicated attribute, and size them so they both fit on the same machine. On Wed, Dec 2, 2015 at 11:44 AM, Tengfei Mu <tengfei...@gmail.com> wrote: > As we are trying to migrate legacy services to Aurora cluster, one > requirement comes out is 'multiple service colocation'. What's the best way > to do this in Aurora world? If it is not supported today, is it a legit > thing worth to explore/pursue for Aurora? > > > Thanks for your help! > - TF >
