cfee_faq.md

copyright	lastupdated
years 2018	2019-01-08

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:new_window: target="_blank"} {:tip: .tip}

FAQs

{: #cfeefaq}

What is the difference between IBM Cloud Foundry Enterprise Environment (CFEE) and public Cloud Foundry?

{: #cfee_diff}

You can use {{site.data.keyword.cloud}} Foundry public to run cloud-native applications that are using Cloud Foundry for simple setup, powerful scaling, and traffic management. You also have easy access to all {{site.data.keyword.cloud}} services.

You can use {{site.data.keyword.cfee_full}} for everything as you would with Cloud Foundry Public, but also to create and manage isolated environments for hosting Cloud Foundry applications exclusively for your enterprise.

How is the new offering different from previous IBM Cloud Foundry offerings?

{: #cfOfferings_diff}

With respect to the public multi-tenant the most noteworthy difference is certainly the isolation properties. With respect to the existing single-tenant offering on IBM Cloud infrastructure, the main two differences are the reduced infrastructure footprint (and therefore the cost) as well as the service integration model into such a single-tenant environment.

Where can I find the CFEE service?

{: #where}

You can find and instantiate the {{site.data.keyword.cfee_full}} service in the {{site.data.keyword.Bluemix_notm}} catalog.

Can I have more than one CFEE environment within a regional data center?

{: #multiple-cfees}

Yes, you can create CFEE instances on-demand, as many as you want in these regions{: new_window} .

Can a CFEE environment be provisioned across multiple data centers (multi-zone)?

{: #multizone} Yes. Starting with CFEE v2.2.0 the CFEE infrastructure (Kubernetes cluster nodes) can be distriburted across multiple data centers (zones) within a given region.

Will I need to start at some minimum capacity?

{: #minimum-capacity}

Yes. Creating a CFEE instance requires a minimum of two Cloud Foundry cells, each with 4 Cores of 16GB RAM, 25GB SSD primary disk, 100GB SSD secondary disk, and 1000Mbps network speed.

What is the underlying IaaS into which CFEE is deployed?

{: #why-kubs}

The CFEE service runs on Kuberneters containers, which allows for lower infrastructure cost and more efficient operations, since Kubernetes is a very smart IaaS that automates many operational activities.

What are my isolation options when creating a CFEE?

{: #isolation}

You have two hardware options on the type of Kubernetes infrastructure into which the CFEE instance is deployed: Virtual shared or Virtual dedicated hardware. With Virtual shared hardware, the worker nodes (into which the Cloud Foundry platform container is deployed) is distributed between you and other IBM customers. With Virtual dedicated the worker nodes are hosted on hardware that is dedicated exlusively to your account. Note that in both cases, Virtual shared and Virtual dedicated, each worker node is single-tenant to the customer. This means that the Cloud Foundry cells in which applications run are not shared with other customers.

Can a CFEE operate within an isolated network?

{: #isolation}

Yes. Starting with version 2.2.0, IBM® Cloud Foundry Enterprise Environment (CFEE) instances can operate inside an isolated networks that protects and secures the environment from external threats. See Operating in an isolated network documentation for more details.

Can I scale the capacity of a CFEE?

{: #scaling}

Yes, you can scale up or down the capacity of your CFEE as your needs change by adding or removing Cloud Foundry cells.

Can I upgrade my CFEE to a new version? How does it work?

{: #upgrading} Yes. The CFEE user interface notifies you when there is a new CFEE versions. You control when to update to a new version. The CFEE version update is invoked by CFEE administrators in the user interface. CFEE version updates may package new versions of its components or supporting services (e.g., Cloud Foundry, Kubernetes, etc). You update the CFEE control plane first and then the Cloud Foundry cells. The update process is optimized to minimize disruption.

What does it take to create a CFEE instance?

{: #create}

You can find the CFEE service listed in the {{site.data.keyword.Bluemix_notm}} catalog. You need to have an upgraded {{site.data.keyword.Bluemix_notm}} account and permissions to the CFEE service and its supported services (Kubernetes, Cloud Object Storage and Compose for PostgreSQL). Once you have those permissions, just provide a name for the environment and click Create. Creation takes approximately 90 minutes.

Can I use {{site.data.keyword.Bluemix_notm}} services in my CFEE?

{: #Services-ibmcloud}

Definitely! By being integrated in the {{site.data.keyword.Bluemix_notm}}, developers in a CFEE can create {{site.data.keyword.Bluemix_notm}} service instances (or use existing instances) and bind them to applications deployed in CFEE spaces.

Can I have my own services services in my CFEE?

{: #Services-ibmcloud}

Yes. An administrator can register a services broker in the CFEE and make custom service plans available to users in that CFEE. The local MCFEE marketplace includes the services from the {{site.data.keyword.Bluemix_notm}} catalog plus any customer services managed by the CFEE's local service broker.

How do I control user access to a CFEE?

{: #Services}

Like any other {{site.data.keyword.Bluemix_notm}} service, access to a CFEE is controlled through Identity & Access Management (IAM). Assigning user access policies (either individually or through access groups) with specific roles gives them specific levels of access to a CFEE. Beyond access to the CFEE service, access to Cloud Foundry organizations and spaces in the CFEE is controlled through Cloud Foundry membership and roles assigned to users in specific organizations and spaces.