Internal approach

Deployment of IBM Storage Fusion Data Foundation entirely within Red Hat OpenShift Container Platform has all the benefits of operator based deployment and management. You can use the internal-attached device approach in the graphical user interface (GUI) to deploy Fusion Data Foundation in internal mode using the local storage operator and local storage devices.

Ease of deployment and management are the highlights of running Fusion Data Foundation services internally on OpenShift Container Platform. There are two different deployment modalities available when Fusion Data Foundation is running entirely within Red Hat OpenShift Container Platform:
  • Simple
  • Optimized
Simple deployment
Fusion Data Foundation services run co-resident with applications. The operators in Red Hat OpenShift Container Platform manages these applications.
A simple deployment is best for situations where,
  • Storage requirements are not clear.
  • Fusion Data Foundation services runs co-resident with the applications.
  • Creating a node instance of a specific size is difficult, for example, on bare metal.
For Fusion Data Foundation to run co-resident with the applications, the applications must have local storage devices, or portable storage devices attached to them dynamically, like EBS volumes on EC2, or vSphere Virtual Volumes on VMware, or SAN volumes.
Note: PowerVC dynamically provisions the SAN volumes.
Optimized deployment
IBM Storage Fusion Data Foundation services run on dedicated infrastructure nodes. Red Hat OpenShift Container Platform manages these infrastructure nodes.
An optimized approach is best for situations when,
  • Storage requirements are clear.
  • IBM Storage Fusion Data Foundation services run on dedicated infrastructure nodes.
  • Creating a node instance of a specific size is easy, for example, on cloud, virtualized environment, and so on.