Switch to openstackdocstheme 2.1.1 version. Using ths version will allow parallelizing building of documents. Update Sphinx version as well. openstackdocstheme renames some variables, so follow the renames. A couple of variables are also not needed anymore, remove them. Set openstackdocs_auto_version to not version the documents. Set openstackdocs_auto_name to use project as name. Change pygments_style to 'native' since old theme version always used 'native' and the theme now respects the setting and using 'sphinx' can lead to some strange rendering. Remove 0.0.1 version from security-thread-analysis. Change-Id: Idd9c795d97ee33e4f121c5b4b97a9ee9e38ae50e
|2 weeks ago|
|case-studies||2 years ago|
|common||1 month ago|
|security-guide||1 week ago|
|security-notes||3 weeks ago|
|security-threat-analysis/source||1 week ago|
|tools||9 months ago|
|.gitignore||4 years ago|
|.gitreview||1 year ago|
|.zuul.yaml||7 months ago|
|README.rst||1 year ago|
|bindep.txt||3 years ago|
|doc-tools-check-languages.conf||2 years ago|
|test-requirements.txt||1 week ago|
|tox.ini||7 months ago|
This repository contains the OpenStack Security documentation.
For details on how to contribute to the documentation, see the OpenStack Documentation Contributor Guide.
It includes these manuals:
- Security Guide
- Security Notes
- Security Threat Analysis
Security Advisories are issued by the Vulnerability Management Team (VMT). For more information about OpenStack's Vulnerability Management Team (VMT) refer to the Vulnerability Management Process.
Security Guide is in the directory
security-guide, which source files in RST format in the directory
Security Threat Analysis is in the directory
security-threat-analysis, which source files in RST format in the directory
The security notes are in the directory
Install the python tox package and run
tox from the top-level directory to use the same tests that are done as part of our Jenkins gating jobs.
Our community welcomes all people interested in open source cloud computing, and encourages you to join the OpenStack Foundation.
The best way to get involved with the community is to talk with others online or at a meet up and offer contributions through our processes, the OpenStack wiki, blogs, or on IRC at
We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.
If you would like to contribute to the documents, please see the OpenStack Documentation contributor guide.
Bugs should be filed on Launchpad, not GitHub:
If you find a security issue in OpenStack, not in the contents of the Security Guide, please see How to Report Security Issues to OpenStack.
Refer to the OpenStack Security Guide to see where these documents are published and to learn more about the OpenStack Security Guide.