Merge "change to section_architecture_network_focus"

This commit is contained in:
Jenkins 2014-12-23 02:38:10 +00:00 committed by Gerrit Code Review
commit dfd9f7e62f

View File

@ -7,12 +7,12 @@
<title>Architecture</title> <title>Architecture</title>
<para>Network focused OpenStack architectures have many <para>Network focused OpenStack architectures have many
similarities to other OpenStack architecture use cases. There similarities to other OpenStack architecture use cases. There
a number of very specific considerations to keep in mind when are a number of very specific considerations to keep in mind when
designing for a network-centric or network-heavy application designing for a network-centric or network-heavy application
environment.</para> environment.</para>
<para>Networks exist to serve a as medium of transporting data <para>Networks exist to serve as a medium of transporting data
between systems. It is inevitable that an OpenStack design between systems. It is inevitable that an OpenStack design
have inter-dependencies with non-network portions of OpenStack has inter-dependencies with non-network portions of OpenStack
as well as on external systems. Depending on the specific as well as on external systems. Depending on the specific
workload, there may be major interactions with storage systems workload, there may be major interactions with storage systems
both within and external to the OpenStack environment. For both within and external to the OpenStack environment. For
@ -152,7 +152,7 @@
protocols. While OpenStack was initially built with only IPv4 protocols. While OpenStack was initially built with only IPv4
support, Networking now supports IPv6 and dual-stacked networks. support, Networking now supports IPv6 and dual-stacked networks.
Note that, as of the Icehouse release, this only includes Note that, as of the Icehouse release, this only includes
stateless address autoconfiguration but work is in stateless address auto configuration but work is in
progress to support stateless and stateful DHCPv6 as well as progress to support stateless and stateful DHCPv6 as well as
IPv6 floating IPs without NAT. Some workloads become possible IPv6 floating IPs without NAT. Some workloads become possible
through the use of IPv6 and IPv6 to IPv4 reverse transition through the use of IPv6 and IPv6 to IPv4 reverse transition