3b5b6b92a8
The need to execute config init before importing harness in congress_servers.py causes a style violation in hacking 1.1.0. Here we move the initialization in bin/congress-server because it's the first place that sees the command line options. It also allows the work on upping hacking to 1.1.0 to go ahead. Change-Id: I7fbc12195f5d79d7df8da3bb835f3f89c1244efc |
||
---|---|---|
antlr3runtime | ||
bin | ||
congress | ||
contrib/nova | ||
devstack | ||
doc | ||
etc | ||
examples | ||
library | ||
releasenotes | ||
scripts | ||
thirdparty | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
Makefile | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
future-features.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
thirdparty-requirements.txt | ||
tox.ini |
README.rst
Welcome to Congress
Congress is an open policy framework for the cloud. With Congress, a cloud operator can declare, monitor, enforce, and audit "policy" in a heterogeneous cloud environment. Congress gets inputs from a cloud's various cloud services; for example in OpenStack, Congress fetches information about VMs from Nova, and network state from Neutron, etc. Congress then feeds input data from those services into its policy engine where Congress verifies that the cloud's actual state abides by the cloud operator's policies. Congress is designed to work with any policy and any cloud service.
- Free software: Apache license
- Documentation: https://docs.openstack.org/congress/latest/
- Wiki: https://wiki.openstack.org/wiki/Congress
- Source: https://github.com/openstack/Congress
- Bugs: https://bugs.launchpad.net/congress
- Blueprints: https://blueprints.launchpad.net/congress
Installing Congress
Please refer to the installation guide >>>>>>> Add wiki Source Bugs and Blueprints notes link to README.rst