Merge "Arch Design: Add internal links"
This commit is contained in:
commit
508912a1b4
|
@ -21,45 +21,64 @@
|
|||
include:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>General purpose: A cloud built with common
|
||||
components that should address 80% of common use
|
||||
cases.</para>
|
||||
<para>
|
||||
<link linkend="generalpurpose">General purpose</link>: A
|
||||
cloud built with common components that should address
|
||||
80% of common use cases.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Compute focused: A cloud designed to address compute
|
||||
intensive workloads such as high performance computing
|
||||
(HPC).</para>
|
||||
<para>
|
||||
<link linkend="compute_focus">Compute focused</link>: A
|
||||
cloud designed to address compute intensive workloads
|
||||
such as high performance computing (HPC).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Storage focused: A cloud focused on storage
|
||||
intensive workloads such as data analytics with
|
||||
parallel file systems.</para>
|
||||
<para>
|
||||
<link linkend="storage_focus">Storage focused</link>: A
|
||||
cloud focused on storage intensive workloads such as
|
||||
data analytics with parallel file systems.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Network focused: A cloud depending on high
|
||||
performance and reliable networking, such as a content
|
||||
delivery network (CDN).</para>
|
||||
<para>
|
||||
<link linkend="network_focus">Network focused</link>: A
|
||||
cloud depending on high performance and reliable
|
||||
networking, such as a content delivery network
|
||||
(CDN).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Multi-site: A cloud built with multiple sites
|
||||
available for application deployments for
|
||||
geographical, reliability or data locality
|
||||
reasons.</para>
|
||||
<para>
|
||||
<link linkend="multi_site">Multi-site</link>: A cloud
|
||||
built with multiple sites available for application
|
||||
deployments for geographical, reliability or data
|
||||
locality reasons.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Hybrid cloud: An architecture where multiple
|
||||
disparate clouds are connected either for failover,
|
||||
hybrid cloud bursting, or availability.</para>
|
||||
<para>
|
||||
<link linkend="hybrid">Hybrid cloud</link>: An
|
||||
architecture where multiple disparate clouds are
|
||||
connected either for failover, hybrid cloud bursting, or
|
||||
availability.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Massively Scalable: An architecture that is intended
|
||||
for cloud service providers or other extremely large
|
||||
installations.</para>
|
||||
<para>
|
||||
<link linkend="massively_scalable">Massively
|
||||
scalable</link>: An architecture that is intended for
|
||||
cloud service providers or other extremely large
|
||||
installations.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>A section titled Specialized Use Cases provides information
|
||||
on architectures that have not previously been covered in the
|
||||
defined use cases.</para>
|
||||
<para>
|
||||
A chapter titled <link linkend="specialized">Specialized
|
||||
cases</link> provides information on architectures that have not
|
||||
previously been covered in the defined use cases.
|
||||
</para>
|
||||
<para>Each chapter in the guide is then further broken down into
|
||||
the following sections:</para>
|
||||
<itemizedlist>
|
||||
|
|
Loading…
Reference in New Issue