You should really take a closer look at Apache Aurora. It is build with multi-user support in mind, and has quite a few features helping in that regard:
* namespaces per user and per environment * authentication * production quota and preemption * ... Best Regards, Stephan ________________________________ From: Harry Metske <[email protected]> Sent: Monday, November 30, 2015 6:40 PM To: [email protected] Subject: Re: Team organization around Mesos cluster We are in a similar stage and also have similar questions, starting with about 20 devops teams, but that could grow to over 50 teams. I am a bit worried having all these teams work in a shared mesos cluster. * they share the name-space for (marathon) applications * share all the mesos slave machines ==> share the CPU, share the same diskspace, share the same memory, share the file hierarchy * I am not aware of any means to authorize the use of resources in the cluster * within marathon you can run a task with any userid, even root (if you run mesos slave with root) * hard to audit (who did what in the cluster) Having a couple of years experience with these same teams in a more classic environment (JEE AppServers), I would opt for a Mesos cluster per devops and take the "infrastructure waste" for granted. In short the question is how to properly operate the cluster(s), and how "multi tenant proof" is it, right? kind regards, Harry On 30 November 2015 at 18:01, David Greenberg <[email protected]<mailto:[email protected]>> wrote: We have a three-tier model: One team manages Mesos itself (from machine provioning to installing & configuring Mesos). A small group of teams each manage the "approved" production-quality frameworks; these teams are clients of the team above. Many teams use the frameworks, they are clients of the framework teams. Thus one team provides infrastructure, several teams provide different platforms (services, batch computing, etc), and many other teams consume the platforms for their particular applications. On Mon, Nov 30, 2015 at 11:55 AM [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> wrote: Hello. I'm in the process of demonstrate and talk about mesos all around my company. Everybody is quite interested, by anytime we talk, they always raise the "operation" problem. We are a quite big company (100k in France), we're doing operation and system management the "old way", with big operation team taking care of a lot of projects, with dozen of operating procedure for each task (from Apache restart to database restoration). Project team think that Mesos fits quite badly in this way of doing things, and wonder how "real people" running a Mesos cluster are doing. Therefore, If you don't mind how you are doing things for operations, without disclosing any sensible information of course, any info would be appreciated. Thanks.
