686886c8d6
The previous folding rules for TRACE log level had the effect that all TRACES were folded into the ERROR that was emitted before them. This was fine and appropriate. When we dropped TRACE tag for these and used ERROR, this was extended to ERROR. This is incorrect. While ERROR tags are used in stack traces in a multiline way, they also just emit some times. We don't want to *always* fold them into the previous line. Doing so means that logstash treats all our ERROR log messages as what came before. Typically INFO. One additional indication of a stacktrace is the log message always has a process id in it. We can minimally modify the grok rule to require %{NUMBER}, which should do the right thing here. This should bring back ERROR log lines in logstash being listed under loglevel:ERROR. Change-Id: I20372686212d080d4bc5c5578c418546005260fd |
||
---|---|---|
doc/source | ||
launch | ||
manifests | ||
modules/openstack_project | ||
playbooks | ||
tools | ||
.gitignore | ||
.gitreview | ||
README.md | ||
Rakefile | ||
install_modules.sh | ||
install_puppet.sh | ||
make_swap.sh | ||
modules.env | ||
mount_volume.sh | ||
roles.yaml | ||
run_all.sh | ||
run_puppet.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
Puppet Modules
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://docs.openstack.org/infra/system-config for more information.
Documentation
The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx