OpenStack Release Bot
6c524a7527
Update the URL to the upper-constraints file to point to the redirect rule on releases.openstack.org so that anyone working on this branch will switch to the correct upper-constraints list automatically when the requirements repository branches. Until the requirements repository has as stable/train branch, tests will continue to use the upper-constraints list on master. Change-Id: I7d4c7f5395419fc073486563bf82c8917be1484d |
||
---|---|---|
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