[
https://issues.apache.org/jira/browse/MESOS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cody Roseborough updated MESOS-3155:
------------------------------------
Description:
The Simulator Containerizer (SC) is a containerizer that can be used in
conjunction with mesos-local to exercise frameworks at a large scale without
launching a large cluster. The SC launches a "fake" executor instead of the one
specified by the tasks, in order to avoid using actual resources. The SC
provides normal tasks updates as well as configurable task options via a
configuration JSON file.
Some of the options available for configuration might be length or failure
rate.
Other points of contact for this are: [~lukeleslie], [~derekchiang]
was:
This could have a user-defined configuration file. This would allow users to
locally test frameworks against a large, simulated cluster using mesos-local.
The Simulator Containerizer (SC) is a containerizer that can be used in
conjunction with mesos-local to exercise frameworks at a large scale without
launching a large cluster. The SC launches a "fake" executor instead of the one
specified by the tasks, in order to avoid using actual resources. The SC
provides normal tasks updates as well as configurable task options via a
configuration JSON file.
Some of the options available for configuration might be length or failure
rate.
Other points of contact for this are: [~lukeleslie], [~derekchiang]
> Add a containerizer and executor that simulate the launching of tasks.
> -----------------------------------------------------------------------
>
> Key: MESOS-3155
> URL: https://issues.apache.org/jira/browse/MESOS-3155
> Project: Mesos
> Issue Type: Improvement
> Components: containerization, slave
> Reporter: Cody Roseborough
> Assignee: Cody Roseborough
> Priority: Minor
>
> The Simulator Containerizer (SC) is a containerizer that can be used in
> conjunction with mesos-local to exercise frameworks at a large scale without
> launching a large cluster. The SC launches a "fake" executor instead of the
> one specified by the tasks, in order to avoid using actual resources. The SC
> provides normal tasks updates as well as configurable task options via a
> configuration JSON file.
> Some of the options available for configuration might be length or failure
> rate.
> Other points of contact for this are: [~lukeleslie], [~derekchiang]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
