cdist configuration management Latest manual: Home page:
Go to file
Nico Schottelius 3de78bfaed + push architecture in readme
Signed-off-by: Nico Schottelius <>
2011-04-19 22:45:05 +02:00
bin Prepare files for the next release 2011-04-19 22:43:18 +02:00
conf import __ssh_authorized_key from Aurélien's tree 2011-04-19 22:30:06 +02:00
doc add tag support 2011-04-19 22:43:49 +02:00
.gitignore merge from upstream 2011-04-04 13:18:04 +02:00 include version in html directory on web 2011-04-06 21:01:27 +02:00
HACKERS_README shrink hackers_readme in favor for the manpage 2011-03-24 15:39:26 +01:00
README + push architecture in readme 2011-04-19 22:45:05 +02:00

[[!meta title="cdist - usable configuration management"]]

                 ..          .       .x+=:.        s   
               dF           @88>    z`    ^%      :8  
              '88bu.        %8P        .   <k    .88 
          .   '*88888bu      .       .@8Ned8"   :888ooo
     .udR88N    ^"*8888N   .@88u   .@^%8888"  -*8888888
    <888'888k  beWE "888L ''888E` x88:  `)8b.   8888
    9888 'Y"   888E  888E   888E  8888N=*8888   8888
    9888       888E  888E   888E   %8"    R88   8888
    9888       888E  888F   888E    @8Wou 9%   .8888Lu=
    ?8888u../ .888N..888    888&  .888888P`    ^%888*
     "8888P'   `"888*""     R888" `   ^"F        'Y" 
       "P'        ""         ""  

[[!toc levels=2]]

## Introduction

cdist is an alternative to other configuration management systems like
and [puppet](
But cdist ticks differently, here is the feature set that makes it unique: 

[[!table  data="""
Keywords | Description
Simplicity | There is only one type to extend cdist called ***type***
Design | Type and core cleanly seperated
Design | Sticks completly to the KISS (keep it simple and stupid) paradigma
Design | Meaningful error messages - do not lose time debugging error messages
Design | Consistency in behaviour, naming and documentation
Design | No surprise factor: Only do what is obviously clear, no magic
Design | Define target state, do not focus on methods or scripts
Design | Push architecture: Instantly apply your changes
Small core | cdist's core is very small - less code, less bugs
Fast development | Focus on straightforwardness of type creation is a main development objective
Requirements, Scalability | No central server needed, cdist operates in push mode and can be run from any computer
Requirements, Scalability, Upgrade | cdist only needs to be updated on the master, not on the target hosts
Requirements, Security | Uses well-know [SSH]( as transport protocol
Requirements, Simplicity | Requires only shell and SSH server on the target
UNIX | Reuse of existing tools like cat, find, mv, ...
UNIX, familar environment, documentation | Is available as manpages and HTML
UNIX, simplicity, familar environment | cdist is written in POSIX shell
UNIX, simplicity, familar environment | cdist is configured in POSIX shell

### Documentation

The cdist documentation is included as manpages in the distribution.
You can [browse the documentation for the latest version online](man) as well.

### OS support

cdist was tested or is know to run on at least

 * [Archlinux](
 * [Debian](
 * [Fedora](
 * [Gentoo](
 * [Mac OS X](
 * [OpenBSD](
 * [Redhat](
 * [Ubuntu](

## Requirements

### Server

 * A posix like shell
 * SSH-Client

### Client ("target host")

 * A posix like shell
 * SSH-Server

## Getting cdist

You can clone cdist from git, which gives you the advantage of having
a version control in place for development of your own stuff as well.

### Installation

To install cdist, execute the following commands:

    git clone git://
    cd cdist
    export PATH=$PATH:$(pwd -P)/bin

    # If you want the manpages (requires gmake and asciidoc to be installed)
    ./ man
    export MANPATH=$MANPATH:$(pwd -P)/doc/man

Afterwards you can run ***cdist-quickstart*** to get an impression on
how to use cdist.

### Available versions

There are at least the following branches available:

 * master: the development branch
 * 1.6: New types, cleaned up \_\_package* types, internal cleanup

Old versions:

 * 1.5: Focus on object orientation instead of global stage orientation
 * 1.4: Support for redefiniton of objects (if equal)
 * 1.3: Support for local and remote code execution (current stable)
 * 1.2: Dependencies supported
 * 1.1: \_\_file to \_\_file, \_\_directory, \_\_link migration
 * 1.0: First official release

Other branches may be available for features or bugfixes, but they
may vanish at any point. To select a specific branch use

    # Generic code
    git checkout -b <name> origin/<name>
    # Stay on a specific version
    git checkout -b $version origin/$version

### Mirrors

 * git:// ([github](
 * git:// ([sans](;a=summary))

## Update

To upgrade cdist in the current branch use

    git pull

    # Also update the manpages
    ./ man
    export MANPATH=$MANPATH:$(pwd -P)/doc/man

If you stay on a version branche (i.e. 1.0, 1.1., ...), nothing should break.
The master branch on the other hand is the development branch and may not be
working, break your setup or eat the tree in your garden.

### Upgrading from 1.5 to 1.6

* If you used **\_\_package_apt --preseed**, you need to use the new
  type **\_\_debconf_set_selections** instead.
* The **\_\_package** types accepted either --state deinstalled or
  --state uninstaaled. Starting with 1.6, it was made consistently
  to --state removed.

### Upgrading from 1.3 to 1.5

No incompatiblities.

### Upgrading from 1.2 to 1.3

Rename **gencode** of every type to **gencode-remote**.

### Upgrading from 1.1 to 1.2

No incompatiblities.

### Upgrading from 1.0 to 1.1

In 1.1 the type **\_\_file** was split into **\_\_directory**, **\_\_file** and
**\_\_link**. The parameter **--type** was removed from **\_\_file**. Thus you
need to replace **\_\_file** calls in your manifests:

 * Remove --type from all \_\_file calls
 * If type was symlink, use \_\_link and --type symbolic
 * If type was directory, use \_\_directory

## Support

### IRC

You can join the development ***IRC channel***
[#cLinux on](irc://

### Mailing list

Bug reports, questions, patches, etc. should be send to the
[cdist mailing list](

## Commercial support

You can request commercial support for cdist from
[my company](

## Used by

If you're using cdist, feel free to send a report to the mailing list.
Interesting information are for instance

 * Which services do you manage?
 * How many machines do you manage?
 * What are the pros/cons you see in cdist?
 * General comments/critics

### Nico Schottelius, Systems Group ETH Zurich and privately

Yes, I'm actually eating my own dogfood and currently managing

 * [plone]( (cms)
 * [moinmoin]( (wiki)
 * [apache]( (webserver)
 * [kerberos (mit)]( (authentication)
 * [nss-pam-ldapd]( (authentication)
 * [ircd-hybrid]( (chat)
 * [stunnel]( (SSL tunnel)
 * [mercurial-server]( (version control)
 * [xfce]( (lightweight desktop environment)
 * [slim]( (graphical login manager for X11)

with cdist on more than **60** production machines of the
[Systems Group]( at the
[ETH Zurich]( as well at home.

### Steven Armstrong, CBRG ETH Zurich

The CBRG is managing most of their compute clusters with cdist.