openstack/openstack-manuals
Code Issues Proposed changes

[arch-guide] Remove reference to Icehouse

Browse Source 
Change-Id: I55d138c562303492c1ba9b25be35aae2c0b80161
Implements: blueprint arch-guide
This commit is contained in:
KATO Tomoyuki 2015-08-14 19:19:25 +09:00
parent fae4895f32
commit fbefa274ef
4 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design/multi_site/section_operational_considerations_multi_site.xml
View File

@ -123,7 +123,7 @@
shared.</para> shared.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
<para>Note that, as of the OpenStack Icehouse release, compute <para>Note that Compute
upgrades within each site can also be performed in a rolling upgrades within each site can also be performed in a rolling
fashion. Compute controller services (API, Scheduler, and fashion. Compute controller services (API, Scheduler, and
Conductor) can be upgraded prior to upgrading of individual Conductor) can be upgraded prior to upgrading of individual

2
doc/arch-design/network_focus/section_architecture_network_focus.xml
View File

@ -124,7 +124,7 @@
This alters the requirements for any address plan as single-stacked and This alters the requirements for any address plan as single-stacked and
transitional IPv6 deployments can alleviate the need for IPv4 transitional IPv6 deployments can alleviate the need for IPv4
addresses.</para> addresses.</para>
<para>As of the Icehouse release, OpenStack has limited support for <para>OpenStack has limited support for
dynamic routing, however there are a number of options available by dynamic routing, however there are a number of options available by
incorporating third party solutions to implement routing within the incorporating third party solutions to implement routing within the
cloud including network equipment, hardware nodes, and instances. Some cloud including network equipment, hardware nodes, and instances. Some

3
doc/arch-design/specialized/section_multi_hypervisor_specialized.xml
View File

@ -43,8 +43,7 @@
vCenter rather than spawning directly on a hypervisor. vCenter rather than spawning directly on a hypervisor.
The vCenter then requests scheduling for the instance to run on The vCenter then requests scheduling for the instance to run on
an ESXi hypervisor.</para> an ESXi hypervisor.</para>
<para>As of the Icehouse release, this functionality requires <para>This functionality requires that VMware Distributed Resource
that VMware Distributed Resource
Scheduler (DRS) is enabled on a cluster and set to <guilabel>Fully Scheduler (DRS) is enabled on a cluster and set to <guilabel>Fully
Automated</guilabel>. The vSphere requires shared storage because the DRS Automated</guilabel>. The vSphere requires shared storage because the DRS
uses vMotion, which is a service that relies on shared storage.</para> uses vMotion, which is a service that relies on shared storage.</para>

6
doc/arch-design/storage_focus/section_architecture_storage_focus.xml
View File

@ -204,10 +204,8 @@
server density than a blade server solution, but are often server density than a blade server solution, but are often
limited to dual-socket, multi-core CPU configurations.</para> limited to dual-socket, multi-core CPU configurations.</para>
<note> <note>
<para>As of the Icehouse release, neither HP, IBM, <para>Due to cooling requirements, it is rare to see 1U
nor Dell offered 1U rack servers with more than 2 CPU rack-mounted servers with more than 2 CPU sockets.</para>
sockets.
</para>
</note> </note>
<para>To obtain greater than dual-socket support in <para>To obtain greater than dual-socket support in
a 1U rack-mount form factor, customers need to buy a 1U rack-mount form factor, customers need to buy