On Fri, Nov 21, 2014 at 4:56 PM, Niklas Nielsen <nik...@mesosphere.io> wrote:
> That aside, our use-case involves hanging meta-data off the task with > labels which we cannot do with an event stream alone. > The metadata we need is produced by a 3rd party security infrastructure > which we invoke and use when setting up the executor environment in the > slave. > We actually only need the pre hook / filter mechanism to do this, but > wanted to come up with a generalized solution. > I still don't quite understand the use case. Why can't a framework(s) talk to the security infrastructure and setup the TaskInfo appropriately and opaquely to master? It sounds like the executor(s) need to be modified to understand the updated security information anyway.
