[ 
https://issues.apache.org/jira/browse/MESOS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-4882:
---------------------------------------
               Sprint: Mesosphere Sprint 33
    Affects Version/s: 0.28.0
                       0.27.2
         Story Points: 5
               Labels: cli mesosphere  (was: )
          Description: 
{{CommandInfo}} protobuf support two kinds of command:
{code}
// There are two ways to specify the command:
  // 1) If 'shell == true', the command will be launched via shell
  //            (i.e., /bin/sh -c 'value'). The 'value' specified will be
  //            treated as the shell command. The 'arguments' will be ignored.
  // 2) If 'shell == false', the command will be launched by passing
  //            arguments to an executable. The 'value' specified will be
  //            treated as the filename of the executable. The 'arguments'
  //            will be treated as the arguments to the executable. This is
  //            similar to how POSIX exec families launch processes (i.e.,
  //            execlp(value, arguments(0), arguments(1), ...)).
{code}

The mesos-execute cannot handle 2) now, enabling 2) can help with testing and 
running one off tasks.

  was:
The commandInfo support two kind of command:
{code}
// There are two ways to specify the command:
  // 1) If 'shell == true', the command will be launched via shell
  //            (i.e., /bin/sh -c 'value'). The 'value' specified will be
  //            treated as the shell command. The 'arguments' will be ignored.
  // 2) If 'shell == false', the command will be launched by passing
  //            arguments to an executable. The 'value' specified will be
  //            treated as the filename of the executable. The 'arguments'
  //            will be treated as the arguments to the executable. This is
  //            similar to how POSIX exec families launch processes (i.e.,
  //            execlp(value, arguments(0), arguments(1), ...)).
{code}

The mesos-execute cannot handle 2) now, enabling 2) can help some unit test 
with isolator.



           Issue Type: Improvement  (was: Bug)
              Summary: Add support for command and arguments to mesos-execute.  
(was: Enabled mesos-execute treat command as executable value and arguments.)

> Add support for command and arguments to mesos-execute.
> -------------------------------------------------------
>
>                 Key: MESOS-4882
>                 URL: https://issues.apache.org/jira/browse/MESOS-4882
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 0.28.0, 0.27.2
>            Reporter: Guangya Liu
>            Assignee: Guangya Liu
>              Labels: cli, mesosphere
>
> {{CommandInfo}} protobuf support two kinds of command:
> {code}
> // There are two ways to specify the command:
>   // 1) If 'shell == true', the command will be launched via shell
>   //          (i.e., /bin/sh -c 'value'). The 'value' specified will be
>   //          treated as the shell command. The 'arguments' will be ignored.
>   // 2) If 'shell == false', the command will be launched by passing
>   //          arguments to an executable. The 'value' specified will be
>   //          treated as the filename of the executable. The 'arguments'
>   //          will be treated as the arguments to the executable. This is
>   //          similar to how POSIX exec families launch processes (i.e.,
>   //          execlp(value, arguments(0), arguments(1), ...)).
> {code}
> The mesos-execute cannot handle 2) now, enabling 2) can help with testing and 
> running one off tasks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to