yadt-config-rpm-maker:这个程序被称为配置 SVN 存储库中的提交钩子，并在每次提交后自动创建必要的配置 R

yadt-config-rpm-maker [](https://travis-ci.org/yadt/yadt-config-rpm-maker) ===================== * Organize the configuration of your data center hosts in a subversion repository. * Run `config-rpm-maker` as post-commit hook of your configuration repository: * Builds RPMs containing the configuration for each host. * Builds only the configuration RPMs for the affected hosts. * Uploads configuration RPMs to a repository using a configurable command. ``` Usage: config_rpm_maker repo-url revision [options] Arguments: repo-url URL to subversion repository or absolute path on localhost revision subversion revision for which the configuration rpms are going to be built Options: -h, --help show this help message and exit --config-viewer-only Only generate files for config viewer. Skip RPM build and upload. --debug force DEBUG log level on console --no-clean-up do not clean up working directory --no-syslog switch logging of debug information to syslog off --rpm-upload-cmd=RPM_UPLOAD_COMMAND Overwrite rpm_upload_config in config file --verbose increase number of logging messages --version show version ``` ### Examples ```bash config-rpm-maker /path-to/your/svn/repository/ 123 ``` Builds all relevant configuration RPMs from the repository at `file:///path-to/your/svn/repository/` in revision `123`. ```bash config-rpm-maker file://host/path-to/your/svn/repository/ 123 ``` ```bash config-rpm-maker svn://host/repository/ 123 ``` ## Features * Creates data for configviewer (visualises the configuration of your hosts) * Templating for your configuration files. * Preserves encoding and will not replace tokens within binary files [see TokenReplace.filter_file](https://github.com/yadt/yadt-config-rpm-maker/blob/master/src/config_rpm_maker/token/tokenreplacer.py#L172) ## Getting Started If you simply want to try and understand how _yadt-config-rpm-maker_ works we recommend to "[setup a devlopment enviroment](https://github.com/yadt/yadt-config-rpm-maker#setup-a-devlopment-enviroment)". #### Step by Step Installation ##### Step 1 Install the build dependencies ```bash sudo yum install python-devel python-setuptools python-mock mock -y ``` Install dependencies ```bash sudo yum install subversion rpm-build pysvn python-yaml -y ``` ##### Step 2 Build the source rpm ```bash ./setup.py bdist_rpm --source-only ``` Build the rpm from the source rpm using mock. ```bash sudo mock rebuild yadt-config-rpm-maker-2.0-1.src.rpm -v ``` ##### Step 3 Set up a subversion repository. There are several tutorials available in the web. Some examples: * [How To Set Up An SVN Repository In 7 Simple Steps](http://www.civicactions.com/blog/2010/may/25/how_set_svn_repository_7_simple_steps) * [Creating and Configuring Your Repository](http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html) and run `config-rpm-maker` in a `post-commit` hook. #### Configuration _yadt-config-rpm-maker_ is configured using a yaml file. Read more in "[Configuration Documentation](https://github.com/yadt/yadt-config-rpm-maker/blob/master/docs/CONFIGURATION.md#configuration)". ### Example Content for Configuration Repository The [testdata](https://github.com/yadt/yadt-config-rpm-maker/tree/master/testdata/svn_repo/) directory contains an example tree for a config repository. It also contains the SPEC file template that is used to build the config RPMs. Use this as a starting point to setup your own environment. ## Build ### Setup a Development Environment _yadt-config-rpm-maker_ is created for Red Hat Linux Distributions. We recommend to develop in a vagrant box. Read our tutorial "[Build and install in a vagrant box](https://github.com/yadt/yadt-config-rpm-maker/tree/master/develop-in-a-vagrant-box)". Of course you can set up a development environment on other platforms too: * [How to develop under CentOS](https://github.com/yadt/yadt-config-rpm-maker/blob/master/docs/HOWTO_CentOS.md) * [How to develop under OpenSUSE](https://github.com/yadt/yadt-config-rpm-maker/blob/master/docs/HOWTO_OpenSUSE.md) * [How to develop under Debian / Mint / Ubuntu](https://github.com/yadt/yadt-config-rpm-maker/blob/master/docs/HOWTO_Debian.md) ### Run Tests ```bash python setup.py test ``` The feedback of the test loader is not helping if the imports fail. This is a known issue (see [7559](http://bugs.python.org/issue7559)). But there are import checks in [`test/__init__.py`](https://github.com/yadt/yadt-config-rpm-maker/blob/master/test/__init__.py) Run the checks to see if you have import errors by executing: ```bash PYTHONPATH=src python test/__init__.py ``` When you run the integration tests _yadt-config-rpm-maker_ will build test RPMs. Measuring test coverage using [coverage](https://pypi.python.org/pypi/coverage) ```bash coverage run --branch setup.py test && coverage report --omit=test/*,/usr/*,setup.py,src/config_rpm_maker/utilities/magic.py ``` ### Execution in the working directory ```bash ./config-rpm-maker ``` The `config-rpm-maker` script allows you to execute yadt-config-rpm-maker in your working directory. ### Build yadt-config-rpm-maker RPM ```bash python setup.py bdist_rpm ``` ### Contribute Please don't forget to add our repository as remote to your fork ```bash git remote add upstream https://github.com/yadt/yadt-config-rpm-maker.git ``` ... and pull from time to time via ... ```bash git remote update git merge upstream/master --ff-only ``` ... to omit merge problems. Authors ======= * [Sebastian Herold](https://github.com/heroldus) * [Schlomo Schapiro](https://github.com/schlomo) * [Ingmar Krusch](https://github.com/ingmarkrusch) * [Maximillien Riehl](https://github.com/mriehl) * [Oliver Schmitz-Hennemann](https://github.com/oli99sc) * [Michael Gruber](https://github.com/aelgru) * [Hasan Hosgel](https://github.com/alosdev) * Konrad Hosemann License ======= yadt-config-rpm-maker Copyright (C) 2011-2014 Immobilien Scout GmbH This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.