IBM Cloud Private Cloud Foundry platform
IBM® Cloud Private Cloud Foundry platform brings Cloud Foundry web application capability to your data center on VMware vSphere, AWS, and OpenStack.
You can extend IBM Cloud Private Cloud Foundry by using IBM or community releases while you continue to receive IBM certified releases. This capability offers you the ability to use new or specialized features that are not always present in Cloud Foundry deployments.
IBM Cloud Private Cloud Foundry that is available in IBM Cloud Private Version 3.1.2 offers Cloud Foundry Version 4.5.0.
Capabilities
IBM Cloud Private Cloud Foundry
- Is built on the Cloud Foundry Diego architecture
- Uses a dockerized installation and update tool
- Offers several authentication options, including built-in UAA and corporate LDAP
- Contains the Cloud Foundry community buildpacks for the IBM versions of Node.js, Liberty, and Swift
- Allows the following user customizations:
- Change the Director or Cloud Foundry deployment configurations (modify settings and add or remove releases)
- Add or remove buildpacks
- Modify certificates, secrets, and passwords
- Use a customized Stemcell
- Connect to your existing logging and monitoring services or use an IBM Cloud Private service from the Catalog
Offerings
You can deploy IBM Cloud Private Cloud Foundry in two modes, Developer and Enterprise. Developer mode uses a small footprint and is good way to learn about the product. It still deploys into an enterprise infrastructure, but its footprint is minimal. In Enterprise mode, you deploy all components to 2 or 3 node clusters. This deployment model provides a second layer of protection, in addition to the protection that is offered by infrastructure as a service (IaaS) high availability (HA), to make sure that your workloads stay running. After the HA platform is initialized, you can expand or reduce its nodes to fit your specific requirements.
Both of these deployment options are available as a single binary file from IBM Passport Advantage® 
to support an AirGap scenario. The installer is small enough that you can run it on a small virtual machine (VM) by using Docker. You can run the VM on an individual computer or on enterprise infrastructure.