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
4.1 KiB
All-in-one (AIO) Duplex Configuration
AIO Duplex provides a scaled-down deployment option that combines controller, storage, and worker functionality on a redundant pair of hosts.
See Common Components <common-components> for a
description of common components of this deployment configuration.
This deployment configuration provides a solution for situations in which protection against overall server hardware faults and only a small amount of cloud processing / storage power is required.
HA services run on the controller function across the two physical servers in either Active/Active or Active/Standby mode.
The optional storage function is provided by a small-scale two node Ceph cluster using one or more disks/ from each server, and provides the backend for Kubernetes' .
The typical solution requires two or more disks per server; one for system requirements and container ephemeral storage, and one or more for Ceph .
Optionally, instead of using an internal Ceph cluster across servers, you can configure an external Netapp Trident storage backend.
Hosted application containers are scheduled on both worker functions.
In the event of an overall server hardware fault:
- all controller HA services enter active mode on the remaining healthy server, and
- all hosted application containers impacted by the failed server are recovered on the remaining healthy server.
On an All-in-one Duplex system, two modes of connection are supported for the management and cluster host network.
- Direct
-
This mode uses direct peer-to-peer connections between the two nodes for the management and an internal cluster host network connection, eliminating the need for a switch port for these networks.
recommends a 10GE shared management and cluster host network with for direct connections. If the management network must be 1GE (to support PXE booting), then a separate 10GE cluster host network with is also recommended. The use of addresses failover considerations unique to peer-to-peer connections.
- Switch-based
-
This mode uses a switch to complete the management and cluster host network connections.
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 if required.
Extending the capacity of the AIO-Duplex Deployment
Up to fifty worker/compute nodes can be added to the All-in-one Duplex deployment, allowing a capacity growth path if starting with an AIO-Duplex deployment.
The extended capacity is limited up to fifty worker/compute nodes as the controller/worker function on the AIO controllers has only a portion of the processing power of the overall server.
Hosted application containers can be scheduled on either of the AIO controller nodes and/or the worker nodes.