aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay Buffington>
Subject Re: Using a config file to support custom executors: potential paradigm shift
Date Thu, 09 Jul 2015 18:19:15 GMT
On Wed, Jul 8, 2015 at 9:10 PM, <> wrote:

> In general the number of executors supported would be not very dynamic but
> as needed in that deployment environment. The config file listing all the
> supported executors can be simply put in the deb or rpm package of the
> scheduler for example.

This configuration differs in no way from other configuration.

> If values are fairly dynamic then the mesos approach makes sense. In the
> end even if passed command line where does that blob live? It will end up
> in systems like puppet or maybe some data store.

It should live in the same place all of the other configuration live (such
as  -allowed_container_types=...).  Probably in your start up script, which
could be put in place by the deb/rpm package or by puppet/chef.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message