cdist/doc/internal/config-layout
Nico Schottelius a836b92082 describe main differences of manifests vs. providers
Signed-off-by: Nico Schottelius <nico@yoda.schottelius.org>
2011-01-15 17:55:31 +01:00

40 lines
1.2 KiB
Text

On the server:
conf/manifests/init
- the central entry point
- is a shell script
- defines mapping from providers to hosts
- will be called by cdist and the name
will be available for tracking in
cdist core functions
core/manifests/* (all other)
- same function as above
- but won't be called by cdist
- method to seperate configuration parts
conf/providers/<name>/
- provide standard types
- have required and optional arguments
- are independent of hosts
- 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
lib/providers/<name>/
- same as above, but provided by the cdist distribution
- if name exists in both, conf/ has priority
Differences manifests vs. providers
manifests providers
main purpose map config to host provide functionality
can change config no (prevent conflicts) yes (allow inheritance)
specificness site specific (globally) reusable