[
https://issues.apache.org/jira/browse/MESOS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163620#comment-14163620
]
Jay Buffington commented on MESOS-156:
--------------------------------------
It looks like this was opened before Aurora and Marathon were open sourced. I
suspect these frameworks meet your needs. Can this Jira be closed?
> Create framework that provides a high level resource request language
> ---------------------------------------------------------------------
>
> Key: MESOS-156
> URL: https://issues.apache.org/jira/browse/MESOS-156
> Project: Mesos
> Issue Type: Story
> Components: framework
> Reporter: Andy Konwinski
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> One of the primary points of confusion about Mesos is the mechanism it
> provides frameworks to acquire new resources (e.g. cpu, ram, etc.).
> Currently, frameworks receive callbacks with resource offers which they can
> accept (entirely or only a portion) or reject. When they accept them, they
> provide a task to be executed on those resources.
> Many engineers we have spoken to have said that they would find it more
> intuitive to provide their executable up front with a description of which
> and how many resources they want, and then have mesos do the scheduling.
> I propose that Mesos should ship with a framework that can very easily be
> installed and run by new users, and this framework should accept "Launch Job
> Requests" expressed via some language that describes the resource
> requirements and where to find the executable for the tasks in the job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
