clufter

Files

Commit: fddfda9802f0be151234ee5d573fcc7562c2eb50

	__root__
	commands
	ext-plugins
	filters
	formats
	misc
	tests
	.gitattributes
	.gitignore
	.gitmodules
	.travis.yml
	__init__.py
	__main__.py
	_gone
	command.py
	command_context.py
	command_manager.py
	completion.py
	defaults.py.in
	error.py
	facts.py
	filter.py
	filter_manager.py
	format.py
	format_manager.py
	main.py
	plugin_registry.py
	protocol.py
	utils.py
	utils_cib.py
	utils_cman.py
	utils_func.py
	utils_prog.py
	utils_xml.py
	utils_xslt.py
	COPYING
	README.rst
	_go
	ccs_flatten
	doc
	run-check
	run-clean
	run-dev
	run-tests
	setup.py

README.rst

clufter (CLUster FilTER)

$ ./run-dev -h | sed '2,8p;d'

Tool/library for transforming/analyzing cluster configuration formats

While primarily aimed at (CMAN,rgmanager)->(Corosync/CMAN,Pacemaker) cluster
stacks configuration conversion (as per RHEL trend), the command-filter-format
framework (capable of XSLT) offers also other uses through its plugin library.

And nope, the name is not a pun, typo or lisp-pronounced cluster per se :-P

Historical curiosity: clufter logotype should actually make f look similar to ſ letter (long s, in use some 200 years ago) as an explicit association with an s-contained word (conversely, project name searchable in A new alphabetical vocabulary, Gailic and English OCR scan).

Usage

The package can either be used as a separate CLI tool (as per What) or as a Python library, which is the case, e.g., with pcs.

Dependencies

Python-wise:

lxml (python-lxml)

general:

Python 2
- 2.7 preferred
- 2.6 with ordereddict or some kind of collections.OrderedDict backport (#929258) required
ccs_flatten, embedded, originally pacemaker/extra/rgmanager:

./configure --with-cman=1 && ( cd extra/rgmanager && make )

tests:

outside of Python 2.7+, unittest2 (python-unittest2) is needed

Installation

TBD

https://travis-ci.org/jnpkrn/clufter.svg?branch=master

Development version

TBD

https://travis-ci.org/jnpkrn/clufter.svg?branch=next

Other remarks

Bash completion

For convenience, bash completion is at user's hands by just running within the session:

$ eval "$(clufter --completion-bash)"

Indeed, to make such a feature permanent, the produced script can be appended to or referred from some relevant file like ~/.bashrc, or when bash-completion package installed, stored to ~/.config/bash_completion (per-user) or /usr/share/bash-completion/bash_completion (system-wide). It's also possible this is already performed on the packaging level.