starlingx/docs
Code Issues Proposed changes
docs/doc/source/deploy_install_guides/release/openstack/hybrid-cluster-c7a3134b6f2a.rst
Ron Stone f98eb51fb4 Simplify install dirs 
Simplify install doc dir structure
- Remove r6 directory
- Rename r7 directory to be non release-specific
- Delete unused files
- Delete obsolete include files
- Delete obsolete commented sections in install topics
- Remove redundent version menu entry

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I59634826d4b3af41410e9d26cc182f6b4aed8ade
2023-01-04 07:30:40 -05:00

1.7 KiB
Raw Blame History

Hybrid Cluster

A Hybrid Cluster occurs when the hosts with a worker function ( controllers and worker nodes) are split between two groups, one running for hosting payloads and the other for hosting containerized payloads.

The host labels are used to define each worker function on the Hybrid Cluster setup. For example, a standard configuration (2 controllers and 2 computes) can be split into (2 controllers, 1 openstack-compute and 1 kubernetes-worker).

partner

Limitations

  • Worker function on controllers MUST both be either Kubernetes or OpenStack.
    • Hybrid Cluster does not apply to or setups.
  • A worker must have only one function, either it is OpenStack compute or k8s-only worker, never both at the same time.
    • The sriov and sriovdp labels cannot coexist on the same host, in order to prevent the device plugin from conflicting with the OpenStack driver.
    • No host will assign and application containers to application cores at the same time.
  • Standard Controllers cannot have openstack-compute-node label; only Controllers can have openstack-compute-node label.
  • Taints must be added to OpenStack compute hosts (i.e. worker nodes or -Controller nodes with the openstack-compute-node label) to prevent end users' hosted containerized workloads/pods from being scheduled on OpenStack compute hosts.