From fbefa274ef18ec4260dce9d72beb376772b071ce Mon Sep 17 00:00:00 2001 From: KATO Tomoyuki Date: Fri, 14 Aug 2015 19:19:25 +0900 Subject: [PATCH] [arch-guide] Remove reference to Icehouse Change-Id: I55d138c562303492c1ba9b25be35aae2c0b80161 Implements: blueprint arch-guide --- .../section_operational_considerations_multi_site.xml | 2 +- .../network_focus/section_architecture_network_focus.xml | 2 +- .../specialized/section_multi_hypervisor_specialized.xml | 3 +-- .../storage_focus/section_architecture_storage_focus.xml | 6 ++---- 4 files changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/arch-design/multi_site/section_operational_considerations_multi_site.xml b/doc/arch-design/multi_site/section_operational_considerations_multi_site.xml index 2bad8cbb10..d4e01284bd 100644 --- a/doc/arch-design/multi_site/section_operational_considerations_multi_site.xml +++ b/doc/arch-design/multi_site/section_operational_considerations_multi_site.xml @@ -123,7 +123,7 @@ shared. - Note that, as of the OpenStack Icehouse release, compute + Note that Compute upgrades within each site can also be performed in a rolling fashion. Compute controller services (API, Scheduler, and Conductor) can be upgraded prior to upgrading of individual diff --git a/doc/arch-design/network_focus/section_architecture_network_focus.xml b/doc/arch-design/network_focus/section_architecture_network_focus.xml index 476defdbc1..210d5a9d7e 100644 --- a/doc/arch-design/network_focus/section_architecture_network_focus.xml +++ b/doc/arch-design/network_focus/section_architecture_network_focus.xml @@ -124,7 +124,7 @@ This alters the requirements for any address plan as single-stacked and transitional IPv6 deployments can alleviate the need for IPv4 addresses. - As of the Icehouse release, OpenStack has limited support for + OpenStack has limited support for dynamic routing, however there are a number of options available by incorporating third party solutions to implement routing within the cloud including network equipment, hardware nodes, and instances. Some diff --git a/doc/arch-design/specialized/section_multi_hypervisor_specialized.xml b/doc/arch-design/specialized/section_multi_hypervisor_specialized.xml index d099224efb..0714e90f51 100644 --- a/doc/arch-design/specialized/section_multi_hypervisor_specialized.xml +++ b/doc/arch-design/specialized/section_multi_hypervisor_specialized.xml @@ -43,8 +43,7 @@ vCenter rather than spawning directly on a hypervisor. The vCenter then requests scheduling for the instance to run on an ESXi hypervisor. - As of the Icehouse release, this functionality requires - that VMware Distributed Resource + This functionality requires that VMware Distributed Resource Scheduler (DRS) is enabled on a cluster and set to Fully Automated. The vSphere requires shared storage because the DRS uses vMotion, which is a service that relies on shared storage. diff --git a/doc/arch-design/storage_focus/section_architecture_storage_focus.xml b/doc/arch-design/storage_focus/section_architecture_storage_focus.xml index 9ef1588a3e..218a43e7c0 100644 --- a/doc/arch-design/storage_focus/section_architecture_storage_focus.xml +++ b/doc/arch-design/storage_focus/section_architecture_storage_focus.xml @@ -204,10 +204,8 @@ server density than a blade server solution, but are often limited to dual-socket, multi-core CPU configurations. - As of the Icehouse release, neither HP, IBM, - nor Dell offered 1U rack servers with more than 2 CPU - sockets. - + Due to cooling requirements, it is rare to see 1U + rack-mounted servers with more than 2 CPU sockets. To obtain greater than dual-socket support in a 1U rack-mount form factor, customers need to buy