I think that would depends on how would you use the mesos cluster. We have a mesos cluster of ~20 nodes to run all the production web services. From the POV of other teams, the mesos cluster is like an internal PaaS, and they only need to know how to manage their own apps - how to create app instances and upgrade them (we do that with a slack chat bot), much like the way you use a public PaaS.
The operational team does all the heavy lifting - server provisioning and monitoring, shared service management (e.g. mysql/cache/mq) for apps running in mesos cluster. If you would create your own mesos framework, it would require more close interaction between the project team and the operational team. Hope that helps. Regards, Shuai On Tue, Dec 1, 2015 at 12:55 AM, aurelien.de...@gmail.com < aurelien.de...@gmail.com> 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. > >
