f125a8b892
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
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.