content_image/980983.jpg
GLYPH<SM590000> Network and storage policy-based controls for application isolation and security. 

GLYPH<SM590000> Automated application health checking and recovery from failures. 

GLYPH<SM590000> Support over IaaS infrastructure, including OpenStack and VMware. 

GLYPH<SM590000> Through the Cloud Automation Manager component, support for Terraform and Chef to allow the orchestration of infrastructure. 

## 1.2 IBM Cloud Private node types 

## 1.2.1 Boot node 

An IBM Cloud Private cluster has the following node types: 

GLYPH<SM590000> Boot node 

GLYPH<SM590000> Master node 

GLYPH<SM590000> Worker node 

GLYPH<SM590000> Management node 

GLYPH<SM590000> Proxy node 

GLYPH<SM590000> VA node 

GLYPH<SM590000> etcd node 

A boot or bootstrap node is used for running installation, configuration, node scaling and cluster updates. Only one boot node is required for any cluster. A single node can be used for both master and boot. See Figure 1-3. 

Note:  In the following images, the clusters represent minimal IBM Cloud Private configurations. Actual production configurations can vary. 

<img src='content_image/980983.jpg'>

Note:  You can use a single boot node for multiple clusters. In such a case, the boot and master cannot be on a single node. Each cluster must have its master node. On the boot node, you must have a separate installation directory for each cluster. If you are providing your own certificate authority (CA) for authentication, you must have a separate CA domain for each cluster. 

