bc8e3704db
File location changes to support DS flattend Install TOC Add minitocs and remove duplicate include directive Convert images to figures and add captions Incorporate server prep. steps Add links to post-install steps. Inline overview and HW topics in procs. Patchset 1 review updates. Rework to reuse some StX install content in partner context and some partner install content in StX context. Conditionalize ipv6_note Share aio_duplex_extend Conditionalize Openstack prod name Add HW requirement includes for worker and storage nodes. Link worker and stor reqs to DX, StD and Dedicated install topics. Fix comment notation Correct for duplicate strings in output Updates and additions based on GW review Make ansible_install_time_only note available DS. Move link target from r6 > r7 Temporarily restore alarms to satisfy build Migrate DX flattening to new layout Additional HW requirements to DX, Std and Dedicated tables. Migrate Standard flattening to new layout Roll this-ver forward to r7 Migrate Dedicated Storage flattening to new layout Address review comments. Standardize HW requirement tables Support horizontally conditionalized inline content Address additional review comments Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: I14c8a1e51f6b6ceff69be063a654b4aadb7d3b8c
3.0 KiB
All-in-one (AIO) Simplex Configuration
The AIO Simplex deployment configuration provides a scaled-down that combines controller, storage, and worker functionality on a single non-redundant host.
Note
Physical L2 switches are not shown in this deployment diagram and in subsequent deployment diagrams. Only the L2 networks they support are shown.
See Common Components <common-components> for a
description of common components of this deployment configuration.
This deployment configuration provides no protection against an overall server hardware fault. However, there may be hardware component protection if, for example, HW RAID or 2x Port is used in the deployment.
Typically, this solution is used where only a small amount of cloud processing / storage power is required, and protection against overall server hardware faults is either not required or done at a higher level.
Optionally, Ceph is deployed in this configuration using one or more disks for , and provides the backend for Kubernetes' .
Typically, the solution requires two or more disks, one for system requirements and container ephemeral storage, and one or more for Ceph .
Optionally, instead of using an internal Ceph cluster on the server, you can configure an external Netapp Trident storage backend.
The internal management network is not required in this scenario as it is configured on the loopback interface. The cluster host network is internal by default and also configured on the loopback interface with application container external connectivity being achieved through either the external OAM network or optional additional external networks. However, the cluster host network can be re-configured on a physical interface depending on external connectivity requirements.
Intel Xeon D Processor
In addition to regular all-in-one deployments, Simplex and Duplex provide support for small scale deployments on the Intel Xeon D family of processors using a smaller memory and CPU footprint than the standard Simplex configuration.
For low-cost or low-power applications with minimal performance demands (40 Containers or fewer), Simplex can be deployed on a server with a single Intel Xeon D class processor. The platform-reserved memory and the maximum number of worker threads are reduced by default, but can be reconfigured as required.