dc64fa1c04
We are updating all Python projects to publish artifacts to PyPI. The name "congress" is already taken there by another project, and they have not responded to our request to claim the name. We therefore need to change the dist name used to package congress. We have some other projects publishing using an "openstack-" prefix, so I propose using the name "openstack-congress". This will not change the imports or anything else about how the code works, just how it is packaged. Change-Id: I076a4025c40e71845e62fe1747cb7c33a477ea16 Signed-off-by: Doug Hellmann <doug@doughellmann.com> |
||
---|---|---|
antlr3runtime | ||
bin | ||
congress | ||
contrib/nova | ||
devstack | ||
doc/source | ||
etc | ||
examples | ||
library | ||
playbooks/legacy | ||
releasenotes | ||
scripts | ||
thirdparty | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
Makefile | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
future-features.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.
Congress is free software and is licensed with Apache.
- Free software: Apache license
- Documentation: https://docs.openstack.org/congress/latest/