You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Santhosh Kumar Shanmugham (JIRA)" <ji...@apache.org> on 2017/01/25 05:31:26 UTC
[jira] [Updated] (AURORA-1882) Add support for Mesos
ContainerLaunchInfo
[ https://issues.apache.org/jira/browse/AURORA-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Santhosh Kumar Shanmugham updated AURORA-1882:
----------------------------------------------
Description:
Mesos-1.2.0 changes the interface for MesosContainerizer binary and drops support for multiple switches. Without support for this Thermos Executor will not be able to launch tasks successfully.
{noformat}
/usr/local/libexec/mesos/mesos-containerizer launch --help
Usage: launch [options]
--[no-]help Prints this help message (default: false)
--launch_info=VALUE
--namespace_mnt_target=VALUE The target 'pid' of the process whose mount namespace we'd like
to enter before executing the command.
--pipe_read=VALUE The read end of the control pipe. This is a file descriptor
on Posix, or a handle on Windows. It's caller's responsibility
to make sure the file descriptor or the handle is inherited
properly in the subprocess. It's used to synchronize with the
parent process. If not specified, no synchronization will happen.
--pipe_write=VALUE The write end of the control pipe. This is a file descriptor
on Posix, or a handle on Windows. It's caller's responsibility
to make sure the file descriptor or the handle is inherited
properly in the subprocess. It's used to synchronize with the
parent process. If not specified, no synchronization will happen.
--runtime_directory=VALUE The runtime directory for the container (used for checkpointing)
--[no-]unshare_namespace_mnt Whether to launch the command in a new mount namespace. (default: false)
{noformat}
https://issues.apache.org/jira/browse/MESOS-6648
was:
Mesos-1.2.0 changes the interface for MesosContainerizer binary and drops support for multiple switches. Without support for this Thermos Executor will not be able to launch tasks successfully.
https://issues.apache.org/jira/browse/MESOS-6648
> Add support for Mesos ContainerLaunchInfo
> -----------------------------------------
>
> Key: AURORA-1882
> URL: https://issues.apache.org/jira/browse/AURORA-1882
> Project: Aurora
> Issue Type: Task
> Components: Executor, Thermos
> Reporter: Santhosh Kumar Shanmugham
> Priority: Critical
>
> Mesos-1.2.0 changes the interface for MesosContainerizer binary and drops support for multiple switches. Without support for this Thermos Executor will not be able to launch tasks successfully.
> {noformat}
> /usr/local/libexec/mesos/mesos-containerizer launch --help
> Usage: launch [options]
> --[no-]help Prints this help message (default: false)
> --launch_info=VALUE
> --namespace_mnt_target=VALUE The target 'pid' of the process whose mount namespace we'd like
> to enter before executing the command.
> --pipe_read=VALUE The read end of the control pipe. This is a file descriptor
> on Posix, or a handle on Windows. It's caller's responsibility
> to make sure the file descriptor or the handle is inherited
> properly in the subprocess. It's used to synchronize with the
> parent process. If not specified, no synchronization will happen.
> --pipe_write=VALUE The write end of the control pipe. This is a file descriptor
> on Posix, or a handle on Windows. It's caller's responsibility
> to make sure the file descriptor or the handle is inherited
> properly in the subprocess. It's used to synchronize with the
> parent process. If not specified, no synchronization will happen.
> --runtime_directory=VALUE The runtime directory for the container (used for checkpointing)
> --[no-]unshare_namespace_mnt Whether to launch the command in a new mount namespace. (default: false)
> {noformat}
> https://issues.apache.org/jira/browse/MESOS-6648
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)