## Frequently asked questions: 

GLYPH<SM590000> Does IBM Cloud Private Cloud Foundry Enterprise Environment install IBM Cloud Private? 

IBM Cloud Private is a pre-requirement for the installation of IBM Cloud Private CFEE. 

IBM Cloud Private CFEE gets installed on top of an IBM Cloud Private installation. 

GLYPH<SM590000> Do I need IBM Cloud Private to install IBM Cloud Private Cloud Foundry? 

IBM Cloud Private Cloud Foundry (not the CFEE flavor) doesn’t need IBM Cloud 

Private to get installed. IBM Cloud Private is only needed for the IBM Cloud Private 

CFEE flavor. The IBM Cloud Private Cloud Foundry can be installed on different platforms (AWS, OpentStack and VMWare) and it relies on BOSH CPI to request resources on these platforms. 

## 10.2 Installation and extensions 

In this section we introduce the installation process and the notions of extensions which allows the deployer to customize the installation. 

The installation is done in two steps, first the creation of the installer container and second Cloud Foundry deployment itself using the Cloud Foundry deployment tool. 

The customer must download the installation kit from (link). The installation kit, if needed, must be copied to a Linux base server that has network connectivity with the targeted environment. 

The installer host has different requirements depending if the target environment is Cloud Foundry Enterprise Environment (CFEE) or Cloud Foundry Full Stack.The installer container is created either by using the provided scripts or by deploying the provided Cloud Pak in IBM Cloud Private. Once the installer container is created, the installation is similar on all supported platforms. The installer container is used only for deployment and upgrades. Once deployment or upgrade of Cloud Foundry is done, the installer container is not needed anymore. 

## 10.2.1 Installation of the installer container in a Cloud Foundry Full Stack environment 

For Cloud Foundry Full Stack, the installer host is the server where the installation kit is downloaded and run. In case of an airgap environment, the deployer needs to copy the installation kit to a server that has access to the target environment. One prerequisite is to have Docker installed on that server. The deployer decompresses the installation kit and then runs the import_image.sh  script which reads the installer kit directory. 

It then uploads all images into Docker and executes l aunch.sh  with some parameters to create the installation container.  One of the parameters is the directory where the installation data should reside. It is useful to have a backup of the data directory and this eases the subsequent upgrade of the Cloud Foundry Full Stack as this directory contains all configuration parameters for the installation and upgrades. Once the installer container is installed, the environment is ready to get deployed. 

