afee550e70
Properties now form a tree, instead of the flat list used before. This simplifies propigation of Info from the Properties used inside a container to the outer host; the Property that docks the container on the host can just have as child properties all the inner Properties, and their Info can then be gathered recursively. (Although in practice it still needs to be filtered, since not all Info should propigate out of a container.) Note that there is no change to how Properties are actually satisfied. Just because a Property lists some child properties, this does not mean they always have their propertySatisfy actions run. It's still up to the parent property to run those actions. That's necessary so that a container's properties can be satisfied inside it, not outside. It also allows property combinators to add the combined Properties to their childProperties list, even if, like onChange, they don't always run the child properties at all. Testing: I tested that the exact same Info is calculated before and after this change, for every Host in my config file. |
||
|---|---|---|
| debian | ||
| doc | ||
| privdata.joey | ||
| src | ||
| .gitignore | ||
| CHANGELOG | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| Setup.hs | ||
| config-joey.hs | ||
| config-simple.hs | ||
| config.hs | ||
| propellor.cabal | ||
README.md
Propellor is a configuration management system using Haskell and Git. Each system has a list of properties, which Propellor ensures are satisfied.
Propellor is configured via a git repository, which typically lives
in ~/.propellor/ on your development machine. Propellor clones the
repository to each host it manages, in a
secure way. The git repository
contains the full source code to Propellor, along with its config file.
Properties are defined using Haskell. Edit ~/.propellor/config.hs
to get started. There is fairly complete
API documentation,
which includes many built-in Properties for dealing with
Apt
and
Apache
,
Cron
and
Commands
,
Dns
and
Docker, etc.
There is no special language as used in puppet, chef, ansible, etc.. just the full power of Haskell. Hopefully that power can be put to good use in making declarative properties that are powerful, nicely idempotent, and easy to adapt to a system's special needs!
If using Haskell to configure Propellor seems intimidating, see configuration for the Haskell newbie.
quick start
- Get propellor installed on your development machine (ie, laptop).
cabal install propellororapt-get install propellor - Run
propellorfor the first time. It will set up a~/.propellor/git repository for you. - If you don't have a gpg private key already, generate one:
gpg --gen-key - Run:
propellor --add-key $KEYID, which will make propellor trust your gpg key, and will sign your~/.propellorrepository using it. - Edit
~/.propellor/config.hs, and add a host you want to manage. You can start by not adding any properties, or only a few. - Run:
propellor --spin $HOST - Now you have a simple propellor deployment, but it doesn't do
much to the host yet, besides installing propellor.
So, edit~/.propellor/config.hsto configure the host, add some properties to it, and re-run step 6.
Repeat until happy and move on to the next host. :) - Optionally, set up a centralized git repository
so that multiple hosts can be updated with a simple
git commit -S; git push - Write some neat new properties and send patches!