git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: looking for suggestions for managing a tree of server configs

From
Ddavid@lang.hm <david@lang.hm>
Date
Oct 14, 2012, 04:57 UTC
Message-ID
<alpine.DEB.2.02.1210132153040.6253@asgard.lang.hm>
In-Reply-To
<7vpq4l1x86.fsf@alter.siamese.dyndns.org>
On Sat, 13 Oct 2012, Junio C Hamano wrote:
Show 18 quoted lines
> david@lang.hm writes:
>
>> I've got a directory tree that holds config data for all my
>> servers. This consists of one directory per server (which is updated
>> periodically from what is currently configured on that server), plus
>> higher level summary reports and similar information.
>>
>> today I have just a single git tree covering everything, and I make a
>> commit each time one of the per-server directories is updated, and
>> again when the top-level stuff is created.
>
> It is quite clear to me what you are keeping at the top-level files,
> but if a large portion of the configuration for these servers are
> shared, it might not be a bad idea to have a canonical "gold-master"
> configuration branch, to which the shared updates are applied, with
> a branch per server that forks from that canonical branch to keep
> the machine specific tweaks as differences from the canonical stuff,
> instead of having N subdirectories (one per machine).

In an ideal world yes, but right now these machines are updated by many different tools (unforuntantly including 'vi'), so these directories aren't the config to be pushed out to the boxes (i.e. what they should be), it's instead an archived 'what is', the result of changes from all the tools.

The systems are all built with a standard image, but the automation tools I do have tend to push identical files out to many of the systems (or files identical except for a couple of lines)

David Lang
Previous: Junio C HamanoNext: Drew Northup
Message 3 of 7 in “looking for suggestions for managing a tree of server configs”
  1. david@lang.hmOct 13, 2012
  2. Junio C HamanoOct 14, 2012
  3. david@lang.hmOct 14, 2012
  4. Drew NorthupOct 21, 2012
  5. david@lang.hmOct 21, 2012
  6. Drew NorthupOct 21, 2012
  7. david@lang.hmOct 21, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.