openstack/openstack-manuals
Code Issues Proposed changes

Merge "Link unlinked URLs in arch-design"

Browse Source
This commit is contained in:
Jenkins 2014-08-05 07:05:54 +00:00 committed by Gerrit Code Review
commit eb83691fa9
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design/ch_glossary.xml
View File

@ -120,7 +120,7 @@
resources and involvement to drive interoperability by resources and involvement to drive interoperability by
creating the minimum standards for products labeled creating the minimum standards for products labeled
"OpenStack." See "OpenStack." See
https://wiki.openstack.org/wiki/Governance/CoreDefinition <link xlink:href="https://wiki.openstack.org/wiki/Governance/CoreDefinition">https://wiki.openstack.org/wiki/Governance/CoreDefinition</link>
for more information.</para> for more information.</para>
</listitem> </listitem>
<listitem> <listitem>

8
doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml
View File

@ -128,7 +128,7 @@
cloud.</para></section> cloud.</para></section>
<section xml:id="cpu-and-ram-compute-focus"><title>CPU and RAM</title> <section xml:id="cpu-and-ram-compute-focus"><title>CPU and RAM</title>
<para>(Adapted from: <para>(Adapted from:
http://docs.openstack.org/openstack-ops/content/compute_nodes.html#cpu_choice)</para> <link xlink:href="http://docs.openstack.org/openstack-ops/content/compute_nodes.html#cpu_choice">http://docs.openstack.org/openstack-ops/content/compute_nodes.html#cpu_choice</link>)</para>
<para>In current generations, CPUs have up to 12 cores. If an <para>In current generations, CPUs have up to 12 cores. If an
Intel CPU supports Hyper-Threading, those 12 cores are doubled Intel CPU supports Hyper-Threading, those 12 cores are doubled
to 24 cores. If a server is purchased that supports multiple to 24 cores. If a server is purchased that supports multiple
@ -252,7 +252,7 @@
different ratios of CPU versus RAM versus HDD different ratios of CPU versus RAM versus HDD
requirements.</para> requirements.</para>
<para>For more information on Flavors refer to: <para>For more information on Flavors refer to:
http://docs.openstack.org/openstack-ops/content/flavors.html</para> <link xlink:href="http://docs.openstack.org/openstack-ops/content/flavors.html">http://docs.openstack.org/openstack-ops/content/flavors.html</link></para>
</section> </section>
<section xml:id="performance-compute-focus"><title>Performance</title> <section xml:id="performance-compute-focus"><title>Performance</title>
<para>The infrastructure of a cloud should not be shared, so that <para>The infrastructure of a cloud should not be shared, so that
@ -354,7 +354,7 @@
client machines and API endpoints and therefore must be client machines and API endpoints and therefore must be
secured.</para> secured.</para>
<para>More information on OpenStack Security can be found <para>More information on OpenStack Security can be found
at http://docs.openstack.org/security-guide/</para> at <link xlink:href="http://docs.openstack.org/security-guide/">http://docs.openstack.org/security-guide/</link></para>
</section> </section>
<section xml:id="openstack-components-compute-focus"> <section xml:id="openstack-components-compute-focus">
<title>OpenStack components</title> <title>OpenStack components</title>
@ -398,7 +398,7 @@
may choose to use other external solutions to fulfill their may choose to use other external solutions to fulfill their
metering and monitoring requirements.</para> metering and monitoring requirements.</para>
<para>See also: <para>See also:
http://docs.openstack.org/openstack-ops/content/logging_monitoring.html</para> <link xlink:href="http://docs.openstack.org/openstack-ops/content/logging_monitoring.html">http://docs.openstack.org/openstack-ops/content/logging_monitoring.html</link></para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>OpenStack Block Storage (Cinder)</para> <para>OpenStack Block Storage (Cinder)</para>