diff --git a/doc/arch-design/hybrid/section_architecture_hybrid.xml b/doc/arch-design/hybrid/section_architecture_hybrid.xml index 640e528b2c..b30aa68bfa 100644 --- a/doc/arch-design/hybrid/section_architecture_hybrid.xml +++ b/doc/arch-design/hybrid/section_architecture_hybrid.xml @@ -81,15 +81,15 @@ implemented across all of the cloud platforms. For platforms that do not support a given service, create a service on top of that platform and apply it to the - workloads as they are launched on that cloud. For - example, OpenStack, via the Database service for OpenStack - (trove), supports MySQL as a - service but not NoSQL databases in production. To move - from or to run alongside on AWS a NoSQL workload would - require recreating the NoSQL database on top of - OpenStack and automate the process of implementing it - using a tool such as the Orchestration module - (heat). + workloads as they are launched on that cloud. + For example, through the Database Service + for OpenStack (trove), + OpenStack supports MySQL as a service but not NoSQL + databases in production. To either move from or run + alongside AWS, a NoSQL workload must use an automation + tool, such as the Orchestration module (heat), to + recreate the NoSQL database on top of OpenStack. + Deploy a Platform-as-a-Service (PaaS) diff --git a/doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml b/doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml index e448406328..e1667adbb1 100644 --- a/doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml +++ b/doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml @@ -145,34 +145,50 @@ queuing algorithms.
Cloud storage - Another common use case for OpenStack environments is to - provide a cloud based file storage and sharing service. While - this may initially be considered to be a storage focused use - case there are also major requirements on the network side - that place it in the realm of requiring a network focused - architecture. An example for this application is cloud - backup. - There are two specific behaviors of this workload that have - major and different impacts on the network. Since this is both - an externally facing service and internally replicating - application there are both North-South and East-West traffic - considerations. - North-South traffic is primarily user facing. This means - that when a user uploads content for storage it will be coming - into the OpenStack installation. Users who download this - content will be drawing traffic from the OpenStack - installation. Since the service is intended primarily as a - backup the majority of the traffic will be southbound into the - environment. In this case it is beneficial to configure a - network to be asymmetric downstream as the traffic entering - the OpenStack installation will be greater than traffic - leaving. - East-West traffic is likely to be fully symmetric. Since - replication will originate from any node and may target - multiple other nodes algorithmically, it is less likely for - this traffic to have a larger volume in any specific - direction. However this traffic may interfere with north-south - traffic. + + Another common use case for OpenStack environments is to provide + a cloud-based file storage and sharing service. You might + consider this a storage-focused use case, but its network-side + requirements make it a network-focused use case. + + For example, consider a cloud backup application. This workload + has two specific behaviors that impact the network. Because this + workload is an externally-facing service and an + internally-replicating application, it has both north-south and + east-west traffic + considerations, as follows: + + + + north-south traffic + + + When a user uploads and stores content, that content moves + into the OpenStack installation. When users download this + content, the content moves from the OpenStack + installation. Because this service is intended primarily + as a backup, most of the traffic moves southbound into the + environment. In this situation, it benefits you to + configure a network to be asymmetrically downstream + because the traffic that enters the OpenStack installation + is greater than the traffic that leaves the installation. + + + + + east-west traffic + + + Likely to be fully symmetric. Because replication + originates from any node and might target multiple other + nodes algorithmically, it is less likely for this traffic + to have a larger volume in any specific direction. However + this traffic might interfere with north-south traffic. + + + + - This application will prioritize the North-South traffic - over East-West traffic as it is the customer-facing data. QoS - is implemented on East-West traffic to be a lower priority - Class Selector, while North-South traffic requires a higher - level in the priority queue because of this. + + This application prioritizes the north-south traffic over + east-west traffic: the north-south traffic involves + customer-facing data. + The network design in this case is less dependant on availability and more dependant on being able to handle high bandwidth. As a direct result, it is beneficial to forego diff --git a/doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml b/doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml index a4b1ffc91e..00f1aad5e2 100644 --- a/doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml +++ b/doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml @@ -49,10 +49,10 @@ management system. Once the Heat template is created, deploying additional stacks will be a trivial thing and can be performed in an automated fashion. - The OpenStack-On-OpenStack project (TripleO) is addressing - this issue—although at the current time the project does - not provide comprehensive coverage for the nested stacks. More - information can be found at The OpenStack-on-OpenStack project (TripleO) + addresses this issue—currently, however, the project does + not completely cover nested stacks. For more information, see + https://wiki.openstack.org/wiki/TripleO. diff --git a/doc/glossary/glossary-terms.xml b/doc/glossary/glossary-terms.xml index a3a7b4aff8..2f57f5b260 100644 --- a/doc/glossary/glossary-terms.xml +++ b/doc/glossary/glossary-terms.xml @@ -2730,6 +2730,19 @@ E + + east-west traffic + + east-west traffic + + + + + Network traffic between servers in the same cloud or data center. + See also north-south traffic. + + + EBS boot volume @@ -5496,6 +5509,20 @@ + + north-south traffic + + north-south traffic + + + + + Network traffic between a user or client (north) and a + server (south), or traffic into the cloud (south) and + out of the cloud (north). See also east-west traffic. + + + nova @@ -8054,6 +8081,20 @@ + + TripleO + + TripleO + + + + + OpenStack-on-OpenStack program. The code name for the + OpenStack Deployment program. + + + + trove