openstack/security-doc
Code Issues Proposed changes

Moving System documentation intro 'up' to chapter file

Browse Source 
Change-Id: I7298b5f3270949c196d0a5ec0ffaf2ff9d7165d0
Partial-Bug: #1349555
This commit is contained in:
dillonn
2015-03-10 12:01:49 -07:00
parent 28c9b28e79
commit 248f4b4869
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
security-guide/ch_documentation.xml
View File

@@ -6,6 +6,15 @@
xml:id="documentation">
<title>System documentation</title>
<para>The system documentation for an OpenStack cloud deployment
should follow the templates and best practices for the Enterprise
Information Technology System in your organization. Organizations
often have compliance requirements which may require an overall
System Security Plan to inventory and document the architecture of a
given system. There are common challenges across the industry
related to documenting the dynamic cloud infrastructure and keeping
the information up-to-date.</para>
<xi:include href="section_system-documentation-requirements.xml"/>
<xi:include href="section_case-studies-system-documentation.xml"/>

8
security-guide/section_system-documentation-requirements.xml
View File

@@ -6,14 +6,6 @@
xml:id="system-documentation-requirements">
<?dbhtml stop-chunking?>
<title>System documentation requirements</title>
<para>The system documentation for an OpenStack cloud deployment
should follow the templates and best practices for the Enterprise
Information Technology System in your organization. Organizations
often have compliance requirements which may require an overall
System Security Plan to inventory and document the architecture of
a given system. There are common challenges across the industry
related to documenting the dynamic cloud infrastructure and
keeping the information up-to-date.</para>
<section xml:id="system-documentation-requirements-system-roles-and-types">
<title>System roles and types</title>
<para>The two broadly defined types of