[jira] [Commented] (MESOS-85) Need to update semantics of MESOS_HOME

["Charles Reiss (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199222#comment-13199222 ] 

Charles Reiss commented on MESOS-85:
------------------------------------

After the auttools patches, most uses of MESOS_HOME are gone.

A survey of the source reveals some remaining ones:

- deploy/*.sh uses it;
- configuration default documentation (presumably for --help) says MESOS_HOME is used for several options.
    * it is actually used for default logfile location, config file location, work dir location
- mesos-launcher and ExecutorLauncher pass it and use it for locating executors under some circumstances

                
> Need to update semantics of MESOS_HOME
> --------------------------------------
>
>                 Key: MESOS-85
>                 URL: https://issues.apache.org/jira/browse/MESOS-85
>             Project: Mesos
>          Issue Type: Improvement
>          Components: build, master, slave, test
>            Reporter: Benjamin Hindman
>            Assignee: Charles Reiss
>            Priority: Blocker
>
> Currently MESOS_HOME is getting used for too much stuff. It is used to represent where the slave should store it's "work" directory, where the slave expects "killtree" to be, where the master and slave should put logging, where the tests assume certain scripts live, etc. In practice this has meant that if mesos gets installed at /usr/local/mesos, then slave work directories go there, logs go there, etc, which is totally unacceptable.
> MESOS_HOME should either be eliminated, or it's semantics should be changed so that it only represents where binaries live, but not where things like work directories exist, logs go, etc. In addition, the testing infrastructure should get updated so that the external tests can find the scripts they need to run things *without* needing MESOS_HOME while still supporting a remote build directory.
> This issue is tagged as a blocker because in order to do the port to autotools cleanly, this really needs to get done in order to run the external tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira