[jira] [Comment Edited] (MESOS-5070) Introduce more flexible subprocess interface for child options.
[
https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481886#comment-15481886
]
Joerg Schad edited comment on MESOS-5070 at 9/11/16 5:37 PM:
-
1.
Fair, do you feel it needs to be part of this reviews?
2.
Watchdog is a different concept than a ChildHook:
A ChildHook is a function which is executed before the actual function, where
the watchdog process is running during the entire lifetime of the process.
{code}
// Creates a seperate watchdog process to monitor the child process and
// kill it in case the parent process dies.
{code}
I would be happy to rename it 'Supervisor', but in a different review :-).
was (Author: js84):
1.
Where do you want to rename Hook -> ParentHook? If you refer to
Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no
reason to rename it.
2.
Watchdog is a different concept than a ChildHook:
A ChildHook is a function which is executed before the actual function, where
the watchdog process is running during the entire lifetime of the process.
{code}
// Creates a seperate watchdog process to monitor the child process and
// kill it in case the parent process dies.
{code}
I would be happy to rename it 'Supervisor', but in a different review :-).
> Introduce more flexible subprocess interface for child options.
> ---
>
> Key: MESOS-5070
> URL: https://issues.apache.org/jira/browse/MESOS-5070
> Project: Mesos
> Issue Type: Improvement
>Reporter: Joerg Schad
>Assignee: Joerg Schad
> Labels: tech-debt
>
> We introduced a number of parameters to the subprocess interface with
> MESOS-5049.
> Adding all options explicitly to the subprocess interface makes it
> inflexible.
> We should investigate a flexible options, which still prevents arbitrary code
> to be executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5735) Update WebUI to use v1 operator API
[ https://issues.apache.org/jira/browse/MESOS-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482094#comment-15482094 ] haosdent commented on MESOS-5735: - [~xujyan] I think in MESOS-5911, we don't want to use Accept headers to CORS (the simplest way), so the only possible way here is to proxy requests which send to agents from the master. > Update WebUI to use v1 operator API > --- > > Key: MESOS-5735 > URL: https://issues.apache.org/jira/browse/MESOS-5735 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Jay Guo > > Having the WebUI use the v1 API would be a good validation of it's usefulness > and correctness. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6147) Configure: error: can not find mvn on your path when running ../configure
[ https://issues.apache.org/jira/browse/MESOS-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482068#comment-15482068 ] haosdent commented on MESOS-6147: - >added to your PATH or set the MAVEN_HOME environment variable Have you try this? > Configure: error: can not find mvn on your path when running ../configure > - > > Key: MESOS-6147 > URL: https://issues.apache.org/jira/browse/MESOS-6147 > Project: Mesos > Issue Type: Bug > Components: build >Affects Versions: 1.0.1 > Environment: Suse Linux Enterprise Server 12 >Reporter: Roberto Grandi > > I am trying to build mesos on SLES 12, following as base your getting started > guide. > when running "../configure" I get this error > configure: error: can not find mvn on your path > --- > You may want verify that Maven has been correctly installed and > added to your PATH or set the MAVEN_HOME environment variable > to point to your Maven installation. > --- > I've installed maven manually on the machine (there is no official maven > package for Suse) and it is on our path. > Can you help us to solve this issue? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-5070) Introduce more flexible subprocess interface for child options.
[ https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schad updated MESOS-5070: --- Comment: was deleted (was: 1. Where do you want to rename Hook -> ParentHook? If you refer to Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no reason to rename it. 2. Watchdog is a different concept than a ChildHook: A ChildHook is a function which is executed before the actual function, where the watchdog process is running during the entire lifetime of the process. [code] // Creates a seperate watchdog process to monitor the child process and // kill it in case the parent process dies. [code] I would be happy to rename it 'Supervisor', but in a different review :-).) > Introduce more flexible subprocess interface for child options. > --- > > Key: MESOS-5070 > URL: https://issues.apache.org/jira/browse/MESOS-5070 > Project: Mesos > Issue Type: Improvement >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: tech-debt > > We introduced a number of parameters to the subprocess interface with > MESOS-5049. > Adding all options explicitly to the subprocess interface makes it > inflexible. > We should investigate a flexible options, which still prevents arbitrary code > to be executed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-5070) Introduce more flexible subprocess interface for child options.
[
https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481886#comment-15481886
]
Joerg Schad edited comment on MESOS-5070 at 9/11/16 3:06 PM:
-
1.
Where do you want to rename Hook -> ParentHook? If you refer to
Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no
reason to rename it.
2.
Watchdog is a different concept than a ChildHook:
A ChildHook is a function which is executed before the actual function, where
the watchdog process is running during the entire lifetime of the process.
{code}
// Creates a seperate watchdog process to monitor the child process and
// kill it in case the parent process dies.
{code}
I would be happy to rename it 'Supervisor', but in a different review :-).
was (Author: js84):
1.
Where do you want to rename Hook -> ParentHook? If you refer to
Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no
reason to rename it.
2.
Watchdog is a different concept than a ChildHook:
A ChildHook is a function which is executed before the actual function, where
the watchdog process is running during the entire lifetime of the process.
[code]
// Creates a seperate watchdog process to monitor the child process and
// kill it in case the parent process dies.
[code]
I would be happy to rename it 'Supervisor', but in a different review :-).
> Introduce more flexible subprocess interface for child options.
> ---
>
> Key: MESOS-5070
> URL: https://issues.apache.org/jira/browse/MESOS-5070
> Project: Mesos
> Issue Type: Improvement
>Reporter: Joerg Schad
>Assignee: Joerg Schad
> Labels: tech-debt
>
> We introduced a number of parameters to the subprocess interface with
> MESOS-5049.
> Adding all options explicitly to the subprocess interface makes it
> inflexible.
> We should investigate a flexible options, which still prevents arbitrary code
> to be executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5070) Introduce more flexible subprocess interface for child options.
[ https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481886#comment-15481886 ] Joerg Schad commented on MESOS-5070: 1. Where do you want to rename Hook -> ParentHook? If you refer to Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no reason to rename it. 2. Watchdog is a different concept than a ChildHook: A ChildHook is a function which is executed before the actual function, where the watchdog process is running during the entire lifetime of the process. [code] // Creates a seperate watchdog process to monitor the child process and // kill it in case the parent process dies. [code] I would be happy to rename it 'Supervisor', but in a different review :-). > Introduce more flexible subprocess interface for child options. > --- > > Key: MESOS-5070 > URL: https://issues.apache.org/jira/browse/MESOS-5070 > Project: Mesos > Issue Type: Improvement >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: tech-debt > > We introduced a number of parameters to the subprocess interface with > MESOS-5049. > Adding all options explicitly to the subprocess interface makes it > inflexible. > We should investigate a flexible options, which still prevents arbitrary code > to be executed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5070) Introduce more flexible subprocess interface for child options.
[ https://issues.apache.org/jira/browse/MESOS-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481887#comment-15481887 ] Joerg Schad commented on MESOS-5070: 1. Where do you want to rename Hook -> ParentHook? If you refer to Subprocess::Hook this is used for both ParentHooks and ChildHooks, so I see no reason to rename it. 2. Watchdog is a different concept than a ChildHook: A ChildHook is a function which is executed before the actual function, where the watchdog process is running during the entire lifetime of the process. [code] // Creates a seperate watchdog process to monitor the child process and // kill it in case the parent process dies. [code] I would be happy to rename it 'Supervisor', but in a different review :-). > Introduce more flexible subprocess interface for child options. > --- > > Key: MESOS-5070 > URL: https://issues.apache.org/jira/browse/MESOS-5070 > Project: Mesos > Issue Type: Improvement >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: tech-debt > > We introduced a number of parameters to the subprocess interface with > MESOS-5049. > Adding all options explicitly to the subprocess interface makes it > inflexible. > We should investigate a flexible options, which still prevents arbitrary code > to be executed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
