+1, that's helpful :). For the detail of implementing such as auto re-load, I think we can let owner/shepherd to decide :).
---- Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform Symphony/DCOS Development & Support, STG, IBM GCG +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me On Mon, Nov 23, 2015 at 9:40 PM, Adam Avilla <a...@avil.la> wrote: > +1 I think it would be helpful. > > This may be orthogonal / feature creep, but would it be possible to have > the config file be able to be safely reloaded with a HUP or appropriate > signal? > > On Mon, Nov 23, 2015 at 5:32 AM, Guangya Liu <gyliu...@gmail.com> wrote: > > > +1000, introducing a new configuration file for mesos master and slave > can > > help end user take the configuration file as the source of all flags. > > > > The OpenStack is also using same way to manage all of the flags, it is > > putting all flags into a configuration file and the configuration file > > including all flag examples. Most of the flags are disabled by default > and > > the end user can just enable those flags based on his requirement. > > > > Also the flags in the configuration file can be classified to different > > groups for a better management, and mesos can also follow this to > classify > > those flags to different groups, such as ACL, Cluster, framework etc. > > > > > > On Mon, Nov 23, 2015 at 9:08 PM, Alexander Rojas < > alexan...@mesosphere.io> > > wrote: > > > > > Hey guys, > > > > > > Over the time I’ve been involved in Mesos I’ve seen that we went from a > > > handful of flags to around 42 supported flags in the master. At this > > point > > > I’m wondering if perhaps we should support a configuration file in > > > conjunction (or instead of) with all the command flags. > > > > > > My intuition is that it will make it easier for operators as well as > for > > > debuggers to be able to replicate configurations easier. > > > > > > Any comments on this idea? > > > > > > -- > /adam >
