Installing and Configuring Azure Open Service Broker for PCF
This topic describes how to install and configure Azure Open Service Broker for Pivotal Cloud Foundry (PCF).
Note: This software is beta quality. Releases prior to v1.0.0 may introduce breaking changes, and should not be used in production.
In this step, you configure your Azure account to allow the Microsoft Open Service Broker for Azure to create and manage Azure resources.
Create an Azure account by following these steps.
Create a service principal by following these steps.
Contributor role needs to be assigned to the service principal.
The Azure Open Service Broker for PCF stores information, like the provisioning information of a service instance, in the Redis database. Follow these steps to create a Redis Cache instance on Azure.
Download the product file from Pivotal Network.
Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.
Click Add next to the uploaded Microsoft Open Service Broker for Azure tile in the Ops Manager Available Products view to add it to your staging area.
Click the newly added Microsoft Open Service Broker for Azure tile to configure the sections as described below. After the configuration, return to the Ops Manager Installation Dashboard and click Apply Changes to install the Azure Open Service Broker for PCF tile.
The setup in Step 1 must be successfully completed before beginning this configuration. You will need the Azure and database parameters from that step to successfully configure the broker.
Click Azure Config.
For Azure Environment, select
Azure Public Cloudfor Azure accounts on public Azure.
Enter the Subscription Id from Step 1.
Enter the Tenant Id, Client Id, and Client Secret from Step 1.
Click Broker Config.
For Log Level, select
INFOif you are not tracking broker issues.
For Minimum Module Stability, it determines the modules to be exposed to developers, which reach the minimum stability. See the Using Microsoft Open Service Broker for Azure topic to check modules’ stability.
For Storage Redis Host and Storage Redis Password, enter the
primaryKeyyou got from Step 2.
For Storage Redis Port, enter
6380for the default-created Azure Redis Cache.
For Storage Redis DB, enter
0to use the first database in Redis to store the information of service instances.
Check the Storage Redis Enable TLS checkbox for default-created Azure Redis Cache.
AES256as Storage Encryption Scheme. It is the only supported encryption scheme for now.
For Storage AES256 KEY, enter a 32-character string. Keep this string somewhere in case it is needed in the future.
For Async Redis Host, Async Redis Password, and Async Redis Port, you can reuse the same Redis Host as Storage. And set Async Redis DB by
1to use a different database. Then also check the box of Async Redis Enable TLS.
Note: The Azure Open Service Broker for PCF installs an app
open-services-broker-azure in the
open-service-broker-azure-space space of the
After Ops Manager finishes the installation, the Microsoft Open Service Broker for Azure appears as a green tile in the Installation Dashboard.
In Apps Manager, the new services are listed in the Marketplace, and are exposed to all orgs and spaces. Users can create instances of these services only by using the Cloud Foundry Command Line Interface (cf CLI) because Apps Manager does not support asynchronous services. See the Using Microsoft Open Service Broker for Azure topic for more information.
The Azure Open Service Broker for PCF is installed with all services enabled by default. All services can be listed in the Marketplace.
You can disable or enable any services through the cf CLI using the
cf disable-service-access or
cf enable-service-access commands.