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
2.0 KiB
Standard Configuration with Controller Storage
supports a small-scale deployment option using a small Ceph cluster as a back-end for Kubernetes deployed on the controller nodes instead of using dedicated storage nodes.
See Common Components <common-components> for a
description of common components of this deployment configuration.
This deployment configuration consists of a two node HA controller+storage cluster managing up to 200 worker nodes. The limit on the size of the worker node pool is due to the performance and latency characteristics of the small integrated Ceph cluster on the controller+storage nodes.
This configuration optionally uses dedicated physical disks configured on each controller+storage node as Ceph . The typical solution requires one primary disk used by the platform for system purposes and subsequent disks are used for Ceph .
Optionally, instead of using an internal Ceph cluster across controllers, you can configure an external Netapp Trident storage backend.
On worker nodes, the primary disk is used for system requirements and for container local ephemeral storage.
HA controller services run across the two controller+storage nodes in either Active/Active or Active/Standby mode. The two node Ceph cluster on the controller+storage nodes provides HA storage through replication between the two nodes.
In the event of an overall controller+storage node failure, all controller HA services become active on the remaining healthy controller+storage node, and the above mentioned nodal Ceph replication protects the Kubernetes .
On overall worker node failure, hosted application containers on the failed worker node are recovered on the remaining healthy worker nodes.