more thoughs about config layout and types

Signed-off-by: Nico Schottelius <nico@yoda.schottelius.org>
This commit is contained in:
Nico Schottelius 2011-01-15 15:38:05 +01:00
parent 87324ae7f4
commit 3403c1dd72

View file

@ -4,9 +4,24 @@ conf/MANIFEST
- the central entry point - the central entry point
- is a shell script - is a shell script
- defines mapping from modules or providers to hosts - defines mapping from modules or providers to hosts
=> will be called by $whatever - can call other MANIFESTs in modules
=> may source other files - will be called by $whatever and relative path
=> will be setup for source tracking:
Cached client: conf/providers/<modname>/
- provide standard types
- may make use of other providers to realise a new type
- how to overwrite stuff?
- overwrite in own tree?
- needs knowledge of inherited provider
- similar to current situation in puppet,
but more like reusable defines
- or may implement some functionality on their own
conf/modules/<modname>/
- configuration put together
- needed additionally to providers?
- perhaps as singletons / objects of class?
Cached client: ???????
Has generated file, which will be (re-)applied Has generated file, which will be (re-)applied