You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:28:13 UTC
[jira] [Issue Comment Deleted] (MESOS-4052) Simple hook
implementation proxying out to another daemon process
[ https://issues.apache.org/jira/browse/MESOS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated MESOS-4052:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> Simple hook implementation proxying out to another daemon process
> -----------------------------------------------------------------
>
> Key: MESOS-4052
> URL: https://issues.apache.org/jira/browse/MESOS-4052
> Project: Mesos
> Issue Type: Wish
> Components: modules
> Reporter: Zhitao Li
> Priority: Minor
>
> Right now, if Mesos user needs hooks like slavePreLaunchDockerHook, they would need to maintain the compiling, building and packaging of a dynamically linked library in c++ in house.
> Designs like [Docker's Volume plugin|https://docs.docker.com/engine/extend/plugins_volume/] simply requires user to implement a predefined REST API in any language and listen at a domain socket. This would be more flexible for companies that does not use c++ as primary language.
> This ticket is exploring the possibility of whether Mesos could provide a default module that 1) defines such API and 2) proxies out to the external agent for any heavy lifting.
> Please let me know whether you think is seems like a reasonable feature/requirement.
> I'm more than happy to work on this than maintain this hook in house in the longer term.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)