Arch Design: Small edits
Fix capitalization and markup. Change-Id: I38a4a20cf9830fa07c769c34eb1ffd7578948317
This commit is contained in:
parent
5659c36a2b
commit
32e98f5045
@ -31,13 +31,13 @@
|
|||||||
<para>Platform-as-a-Service (PaaS)</para>
|
<para>Platform-as-a-Service (PaaS)</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Signal processing for Network Function Virtualization (NFV)</para>
|
<para>Signal processing for network function virtualization (NFV)</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
<para>Based on the use case requirements, such clouds might need to provide
|
<para>Based on the use case requirements, such clouds might need to provide
|
||||||
additional services such as a virtual machine disk library, file or object
|
additional services such as a virtual machine disk library, file or object
|
||||||
storage, firewalls, load balancers, IP addresses, and network connectivity
|
storage, firewalls, load balancers, IP addresses, and network connectivity
|
||||||
in the form of overlays or virtual Local Area Networks (VLANs). A
|
in the form of overlays or virtual local area networks (VLANs). A
|
||||||
compute-focused OpenStack cloud will not typically use raw block storage
|
compute-focused OpenStack cloud will not typically use raw block storage
|
||||||
services since the applications hosted on a compute-focused OpenStack
|
services since the applications hosted on a compute-focused OpenStack
|
||||||
cloud generally do not need persistent block storage.</para>
|
cloud generally do not need persistent block storage.</para>
|
||||||
|
@ -10,16 +10,18 @@
|
|||||||
network communication in order to function properly due to a
|
network communication in order to function properly due to a
|
||||||
service-based nature. In some cases, however, use cases
|
service-based nature. In some cases, however, use cases
|
||||||
dictate that the network is elevated beyond simple
|
dictate that the network is elevated beyond simple
|
||||||
infrastructure. This section is a discussion of architectures
|
infrastructure. This chapter is a discussion of architectures
|
||||||
that are more reliant or focused on network services. These
|
that are more reliant or focused on network services. These
|
||||||
architectures are heavily dependent on the network
|
architectures are heavily dependent on the network
|
||||||
infrastructure and need to be architected so that the network
|
infrastructure and need to be architected so that the network
|
||||||
services perform and are reliable in order to satisfy user and
|
services perform and are reliable in order to satisfy user and
|
||||||
application requirements.</para>
|
application requirements.</para>
|
||||||
<para>Some possible use cases include:</para>
|
<para>Some possible use cases include:</para>
|
||||||
<itemizedlist>
|
<variablelist>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Content delivery network</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Content Delivery Network: This could include
|
<para>This could include
|
||||||
streaming video, photographs or any other cloud based
|
streaming video, photographs or any other cloud based
|
||||||
repository of data that is distributed to a large
|
repository of data that is distributed to a large
|
||||||
number of end users. Mass market streaming video will
|
number of end users. Mass market streaming video will
|
||||||
@ -36,21 +38,30 @@
|
|||||||
as well as the WAN architecture and the cache
|
as well as the WAN architecture and the cache
|
||||||
methodology.</para>
|
methodology.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Network management functions</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Network Management Functions: A cloud that provides
|
<para>A cloud that provides
|
||||||
network service functions would be built to support
|
network service functions would be built to support
|
||||||
the delivery of back-end network services such as DNS,
|
the delivery of back-end network services such as DNS,
|
||||||
NTP or SNMP and would be used by a company for
|
NTP or SNMP and would be used by a company for
|
||||||
internal network management.</para>
|
internal network management.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Network service offerings</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Network Service Offerings: A cloud can be used to
|
<para>A cloud can be used to
|
||||||
run customer facing network tools to support services.
|
run customer facing network tools to support services.
|
||||||
For example, VPNs, MPLS private networks, GRE tunnels
|
For example, VPNs, MPLS private networks, GRE tunnels
|
||||||
and others.</para>
|
and others.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Web portals or web services</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Web portals / Web Services: Web servers are a common
|
<para>Web servers are a common
|
||||||
application for cloud services and it is recommended
|
application for cloud services and it is recommended
|
||||||
to have an understanding of the network requirements.
|
to have an understanding of the network requirements.
|
||||||
The network will need to be able to scale out to meet
|
The network will need to be able to scale out to meet
|
||||||
@ -59,8 +70,11 @@
|
|||||||
bandwidth must be considered depending on the details
|
bandwidth must be considered depending on the details
|
||||||
of the portal architecture.</para>
|
of the portal architecture.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>High speed and high volume transactional systems</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>High Speed and High Volume Transactional Systems:
|
<para>
|
||||||
These types of applications are very sensitive to
|
These types of applications are very sensitive to
|
||||||
network configurations. Examples include many
|
network configurations. Examples include many
|
||||||
financial systems, credit card transaction
|
financial systems, credit card transaction
|
||||||
@ -73,8 +87,11 @@
|
|||||||
performance database back ends that need to be
|
performance database back ends that need to be
|
||||||
accessed.</para>
|
accessed.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>High availability</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>High Availability: These types of use cases are
|
<para>These types of use cases are
|
||||||
highly dependent on the proper sizing of the network
|
highly dependent on the proper sizing of the network
|
||||||
to maintain replication of data between sites for high
|
to maintain replication of data between sites for high
|
||||||
availability. If one site becomes unavailable, the
|
availability. If one site becomes unavailable, the
|
||||||
@ -83,8 +100,11 @@
|
|||||||
important to size network capacity to handle the loads
|
important to size network capacity to handle the loads
|
||||||
that are desired.</para>
|
that are desired.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Big data</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Big Data: Clouds that will be used for the
|
<para>Clouds that will be used for the
|
||||||
management and collection of big data (data ingest)
|
management and collection of big data (data ingest)
|
||||||
will have a significant demand on network resources.
|
will have a significant demand on network resources.
|
||||||
Big data often uses partial replicas of the data to
|
Big data often uses partial replicas of the data to
|
||||||
@ -94,8 +114,11 @@
|
|||||||
NuoDB, RIAK and other No-SQL and distributed
|
NuoDB, RIAK and other No-SQL and distributed
|
||||||
databases.</para>
|
databases.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Virtual desktop infrastructure (VDI)</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Virtual Desktop Infrastructure (VDI): This use case
|
<para>This use case
|
||||||
is very sensitive to network congestion, latency,
|
is very sensitive to network congestion, latency,
|
||||||
jitter and other network characteristics. Like video
|
jitter and other network characteristics. Like video
|
||||||
streaming, the user experience is very important
|
streaming, the user experience is very important
|
||||||
@ -105,8 +128,11 @@
|
|||||||
caching for the delivery of the application to the end
|
caching for the delivery of the application to the end
|
||||||
user.</para>
|
user.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Voice over IP (VoIP)</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Voice over IP (VoIP): This is extremely sensitive to
|
<para>This is extremely sensitive to
|
||||||
network congestion, latency, jitter and other network
|
network congestion, latency, jitter and other network
|
||||||
characteristics. VoIP has a symmetrical traffic
|
characteristics. VoIP has a symmetrical traffic
|
||||||
pattern and it requires network quality of service
|
pattern and it requires network quality of service
|
||||||
@ -116,8 +142,11 @@
|
|||||||
jitter fluctuations and can detect them at very low
|
jitter fluctuations and can detect them at very low
|
||||||
levels.</para>
|
levels.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>Video Conference or web conference</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Video Conference / Web Conference: This also is
|
<para>This also is
|
||||||
extremely sensitive to network congestion, latency,
|
extremely sensitive to network congestion, latency,
|
||||||
jitter and other network flaws. Video Conferencing has
|
jitter and other network flaws. Video Conferencing has
|
||||||
a symmetrical traffic pattern, but unless the network
|
a symmetrical traffic pattern, but unless the network
|
||||||
@ -126,8 +155,11 @@
|
|||||||
Similar to VOIP, users will be sensitive to network
|
Similar to VOIP, users will be sensitive to network
|
||||||
performance issues even at low levels.</para>
|
performance issues even at low levels.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
<varlistentry>
|
||||||
|
<term>High performance computing (HPC)</term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>High Performance Computing (HPC): This is a complex
|
<para>This is a complex
|
||||||
use case that requires careful consideration of the
|
use case that requires careful consideration of the
|
||||||
traffic flows and usage patterns to address the needs
|
traffic flows and usage patterns to address the needs
|
||||||
of cloud clusters. It has high East-West traffic
|
of cloud clusters. It has high East-West traffic
|
||||||
@ -135,7 +167,8 @@
|
|||||||
substantial North-South traffic depending on the
|
substantial North-South traffic depending on the
|
||||||
specific application.</para>
|
specific application.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</varlistentry>
|
||||||
|
</variablelist>
|
||||||
|
|
||||||
<xi:include href="network_focus/section_user_requirements_network_focus.xml"/>
|
<xi:include href="network_focus/section_user_requirements_network_focus.xml"/>
|
||||||
<xi:include href="network_focus/section_tech_considerations_network_focus.xml"/>
|
<xi:include href="network_focus/section_tech_considerations_network_focus.xml"/>
|
||||||
|
@ -17,34 +17,50 @@
|
|||||||
for each use case:</para>
|
for each use case:</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Specialized Networking: This describes running
|
<para>
|
||||||
networking-oriented software that may involve reading
|
<link
|
||||||
packets directly from the wire or participating in
|
linkend="specialized-networking-example">Specialized
|
||||||
routing protocols.</para>
|
Networking</link>: This describes running
|
||||||
|
networking-oriented software that may involve reading
|
||||||
|
packets directly from the wire or participating in
|
||||||
|
routing protocols.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Software-Defined Networking: This use case details
|
<para>
|
||||||
both running an SDN controller from within OpenStack
|
<link
|
||||||
as well as participating in a software-defined
|
linkend="software-defined-networking-sdn">Software-defined
|
||||||
network.</para>
|
networking (SDN)</link>: This use case details both
|
||||||
|
running an SDN controller from within OpenStack as well
|
||||||
|
as participating in a software-defined network.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Desktop-as-a-Service: This is for organizations that
|
<para>
|
||||||
want to run a virtualized desktop environment on a
|
<link
|
||||||
cloud. This can apply to private or public
|
linkend="desktop-as-a-service">Desktop-as-a-Service</link>:
|
||||||
clouds.</para>
|
This is for organizations that want to run a virtualized
|
||||||
|
desktop environment on a cloud. This can apply to
|
||||||
|
private or public clouds.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>OpenStack on OpenStack: Some organizations are
|
<para>
|
||||||
finding that it makes technical sense to build a
|
<link
|
||||||
multi-tiered cloud by running OpenStack on top of an
|
linkend="arch-guide-openstack-on-openstack">OpenStack on
|
||||||
OpenStack installation.</para>
|
OpenStack</link>: Some organizations are finding that it
|
||||||
|
makes technical sense to build a multi-tiered cloud by
|
||||||
|
running OpenStack on top of an OpenStack
|
||||||
|
installation.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Specialized Hardware: Some highly specialized
|
<para>
|
||||||
situations will require the use of specialized
|
<link linkend="specialized-hardware">Specialized
|
||||||
hardware devices from within the OpenStack
|
hardware</link>: Some highly specialized situations will
|
||||||
environment.</para>
|
require the use of specialized hardware devices from
|
||||||
|
within the OpenStack environment.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
|
@ -5,8 +5,8 @@
|
|||||||
version="5.0"
|
version="5.0"
|
||||||
xml:id="software-defined-networking-sdn">
|
xml:id="software-defined-networking-sdn">
|
||||||
<?dbhtml stop-chunking?>
|
<?dbhtml stop-chunking?>
|
||||||
<title>Software Defined Networking</title>
|
<title>Software-defined networking</title>
|
||||||
<para>Software Defined Networking (SDN) is the separation of the data
|
<para>Software-defined networking (SDN) is the separation of the data
|
||||||
plane and control plane. SDN has become a popular method of
|
plane and control plane. SDN has become a popular method of
|
||||||
managing and controlling packet flows within networks. SDN
|
managing and controlling packet flows within networks. SDN
|
||||||
uses overlays or directly controlled layer 2 devices to
|
uses overlays or directly controlled layer 2 devices to
|
||||||
|
Loading…
Reference in New Issue
Block a user