Hello David.
thanks for the feedback. I understand you have a quite restraint number of team to handle mesos+frameworks. Does the mesos team (and therefore the framework team) only take care of mesos (resp. frameworks)? Or do they have another tasks? thansk. ________________________________ De : David Greenberg <[email protected]> Envoyé : lundi 30 novembre 2015 18:01 À : [email protected] Objet : Re: Team organization around Mesos cluster 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.
