Policy masterfiles that are shipped with CFEngine packages
Python Shell HTML M4 Makefile PHP
Latest commit 2dbd5c7 Jun 16, 2017 @nickanderson nickanderson committed on GitHub Merge pull request #932 from olehermanse/cfnet
Fix Masterfiles travis failures
Permalink
Failed to load latest commit information.
3rdparty/core Bring latest determine-version.py from Core. May 31, 2017
cfe_internal CFE-2326: Add bundle to track component variables to restart when nec… Jun 13, 2017
controls Do not use bindtointerface on windows Jun 13, 2017
inventory ENT-3117: Add aix OOTB oslevel inventory Apr 25, 2017
lib CFE-2533: Add zypper package module May 18, 2017
m4 Make pkgsrc tests dependent on all the required platform tools. Nov 12, 2015
modules/packages zendesk#3432: fix zypper package downgrade failing because zypper pre… May 29, 2017
services Add: split systemd unit support Oct 25, 2016
sketches/meta Support CFEngine 3.7 and remove support for 3.4 Apr 18, 2014
templates ENT-2831: Fix bootstrap hanging on non-systemd platforms. Oct 26, 2016
tests Add cf-net to testall Jun 16, 2017
.gitignore Added CFVersion to gitignore Oct 17, 2016
.travis.yml Disabled latest/master tests in travis Jun 16, 2017
CHANGELOG.md Changelog update from 3.10.0b1. Dec 16, 2016
CONTRIBUTING.md Add a link to core's test procedures. Dec 16, 2013
LICENSE Fix some typos (most of them found by codespell) Sep 25, 2016
MPF.md Link to Augments docs Jun 14, 2017
Makefile.am Update determine-version.py from Core. Sep 16, 2016
README.md Fix build badges Feb 13, 2017
autogen.sh Update determine-version.py from Core. Sep 16, 2016
configure.ac ENT-3155: Change self upgrade now uses standalone policy May 18, 2017
example_def.json CFE-2458: Allow specification of files_single_copy via augments Apr 12, 2017
promises.cf.in CFE-2533: Add zypper package module May 18, 2017
standalone_self_upgrade.cf.in ENT-3155: Change self upgrade now uses standalone policy May 18, 2017
update.cf ENT-3155: Change self upgrade now uses standalone policy May 18, 2017

README.md

Version Core MPF
master Core Build Status MPF Build Status
3.10.x Core Build Status MPF Build Status
3.7.x Core Build Status MPF Build Status

Looking for help?

IRC channel

Developer IRC channel

CFEngine 3 masterfiles

CFEngine 3 is a popular open source configuration management system. Its primary function is to provide automated configuration and maintenance of large-scale computer systems.

The MPF or Masterfiles Policy Framework is intended to provide a stable base policy installations and upgrades, and is used by both CFEngine Enterprise and CFEngine community in versions 3.6 and newer. The documentation for the MPF is highly recommended.

Installation

There are several methods available for installing the CFEngine Masterfiles Policy Framework.

  • From pkg tarball
  • From git
  • From source tarball

From pkg tarball

If you have downloaded a package tarball from our website (not from github), you don't need to autogen, configure or make anything. Instead simply unpack the tarball to the desired location using tar.

For example:

tar zxvf cfengine-masterfiles-MAJOR.MINOR.PATCH.pkg.tar.gz --exclude="modules" -C /var/cfengine/masterfiles --strip-components=2

Note: The above command installs only the policy from masterfiles. Typically the modules that are distributed within the masterfiles repository are not installed until the binaries are upgraded. However, if you wish to install the modules along with the policy you can use this simplified command:

tar zxvf cfengine-masterfiles-MAJOR.MINOR.PATCH.pkg.tar.gz /var/cfengine/masterfiles

From git

Clone this repository

git clone https://github.com/cfengine/masterfiles

If you have cloned the repository from github:

Run autogen and make to build masterfiles.

./autogen.sh
make

Optionally configure masterfiles to install to a differnt location (perhaps your own version control checkout)

./configure --prefix=/tmp/cfengine/
make
make install

From source tarball

If you have downloaded a release tarball from our website (not from github), you don't need to run autogen.sh. By default it installs in /var/cfengine/masterfiles but you can override that easily:

./configure --prefix=/install/directory
make install

Note that the last directory component will always be called masterfiles.

Host report

A very important piece of functionality, which you may want for your own use but will certainly be helpful for debugging or submitting bugs to CFEngine (core, masterfiles, or any other are) is the host report.

Run the host report like so: cf-agent -b host_info_report

You should see output like:

R: Host info report generated and available at '/var/cfengine/reports/host_info_report.txt'

Take a look at the resulting file, it has lots of useful information about the system.

Contributing

Please see the CONTRIBUTING.md file.

The CFEngine masterfiles are under the MIT license, see LICENSE