[jira] [Updated] (MESOS-2832) Enable configuring Mesos with environment variables without having them leak to tasks launched
[ https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman updated MESOS-2832: Story Points: 8 > Enable configuring Mesos with environment variables without having them leak > to tasks launched > -- > > Key: MESOS-2832 > URL: https://issues.apache.org/jira/browse/MESOS-2832 > Project: Mesos > Issue Type: Wish >Reporter: Cody Maloney >Assignee: Benjamin Hindman >Priority: Critical > Labels: mesosphere > Fix For: 0.23.0 > > > Currently if mesos is configured with environment variables (MESOS_MODULES), > those show up in every task which is launched unless the executor explicitly > cleans them up. > If the task being launched happens to be something libprocess / mesos based, > this can often prevent the task from starting up (A scheduler has issues > loading a module intended for the slave). > There are also cases where it would be nice to be able to change what the > PATH is that tasks launch with (the host may have more in the path than tasks > are supposed to / allowed to depend upon). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2832) Enable configuring Mesos with environment variables without having them leak to tasks launched
[ https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-2832: --- Sprint: (was: Mesosphere Sprint 12) > Enable configuring Mesos with environment variables without having them leak > to tasks launched > -- > > Key: MESOS-2832 > URL: https://issues.apache.org/jira/browse/MESOS-2832 > Project: Mesos > Issue Type: Wish >Reporter: Cody Maloney >Assignee: Benjamin Hindman >Priority: Critical > Labels: mesosphere > > Currently if mesos is configured with environment variables (MESOS_MODULES), > those show up in every task which is launched unless the executor explicitly > cleans them up. > If the task being launched happens to be something libprocess / mesos based, > this can often prevent the task from starting up (A scheduler has issues > loading a module intended for the slave). > There are also cases where it would be nice to be able to change what the > PATH is that tasks launch with (the host may have more in the path than tasks > are supposed to / allowed to depend upon). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2832) Enable configuring Mesos with environment variables without having them leak to tasks launched
[ https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman updated MESOS-2832: Sprint: Mesosphere Sprint 12 Shepherd: Till Toenshoff Assignee: Benjamin Hindman > Enable configuring Mesos with environment variables without having them leak > to tasks launched > -- > > Key: MESOS-2832 > URL: https://issues.apache.org/jira/browse/MESOS-2832 > Project: Mesos > Issue Type: Wish >Reporter: Cody Maloney >Assignee: Benjamin Hindman >Priority: Critical > Labels: mesosphere > > Currently if mesos is configured with environment variables (MESOS_MODULES), > those show up in every task which is launched unless the executor explicitly > cleans them up. > If the task being launched happens to be something libprocess / mesos based, > this can often prevent the task from starting up (A scheduler has issues > loading a module intended for the slave). > There are also cases where it would be nice to be able to change what the > PATH is that tasks launch with (the host may have more in the path than tasks > are supposed to / allowed to depend upon). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
