You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Tobias Weingartner (JIRA)" <ji...@apache.org> on 2014/08/07 22:23:12 UTC
[jira] [Commented] (MESOS-1651) Configuration file option with
command line flags override
[ https://issues.apache.org/jira/browse/MESOS-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089757#comment-14089757 ]
Tobias Weingartner commented on MESOS-1651:
-------------------------------------------
Related: https://reviewboard.twitter.biz/r/415373/
> Configuration file option with command line flags override
> ----------------------------------------------------------
>
> Key: MESOS-1651
> URL: https://issues.apache.org/jira/browse/MESOS-1651
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: Tobias Weingartner
>
> It would be awesome if the extensive command lines were shorted by being able to specify a configuration file instead of command line arguments. A couple wishlist style things:
> * command line flags override configuration file options
> * ability to specify a sequence of configuration files to facilitate rolling out a new feature and having backup configurations if the config file contains incompatible information
> * Possibly a stored configuration within the meta directory, and a way to update this configuration for non-impacting changes. Possibly using the stored/check-pointed configuration as a fall-back if it would be task affecting.
> Pie in the sky:
> * have the slave generate inverse offers and manage transitioning to new configurations. Possibly by including a method to tell the environment how else to mitigate (please reboot host, kernel is incompatible, etc).
--
This message was sent by Atlassian JIRA
(v6.2#6252)