Installing and Configuring ECS Service Broker for PCF
This topic describes how to install and configure ECS Service Broker for Pivotal Cloud Foundry (PCF).
The ECS Service Broker installs as a single PCF-deployed application, which makes API calls to an externally-hosted Dell EMC ECS installation. The broker uses
a combination of both the ECS
management API (which typically runs on port
on ECS) and the S3 API (which runs on ports
HTTPS). If you
do not yet have access to an ECS environment, you have two options:
To install the service broker, you must configure the broker application to connect to the ECS management API. If desired, you may also customize the services and plans offered in the PCF marketplace with additional pages in the Tile interface.
To start running the ECS broker, do the following:
Download the product file from Pivotal Network.
Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.
Under the Import a Product button, click + next to the version number of ECS Service Broker for PCF. This adds the tile to your staging area.
Click the newly added ECS Service Broker for PCF tile.
Click Service Broker Application.
For Service Broker Application Name, enter the name the broker should run as when running as a Cloud Foundry application.
For Service Broker Application version, enter the version of the service broker app. The final app name will include an app version like
For Service Broker Application URI, enter the URI for the service broker app (on push to CF). This will be the route PCF creates when deployed.
For Open up Security Groups, check to open up a security group on CF for the service broker to access other apps or CF Cloud Controller.
For Enable Global access to all Services and Plans, check the checkbox to open up access to all service plans across all orgs and spaces.
Navigate to Dell EMC ECS Connectivity.
For ECS Management Endpoint, enter the URI/endpoint for the ECS HTTPS management API. This typically runs on port
4443of the ECS. For ECS Test Drive users, see the ECS Management page.
For Replication Group, enter the name of the ECS replication group to be used for created buckets. For ECS Test Drive users, this should be
For Namespace, enter the name of the ECS namespace to be used for created buckets and users.
For ECS Admin Username, enter the name of the ECS Management API user. In ECS terminology, this is a Management User (not an Object User), which should configured as either a Namespace Administrator or System Administrator.
For ECS Admin Password, enter the ECS Management API password.
(Optional) For ECS Base URL, enter the name of the ECS configured base URL that should be used with bucket credentials. If no value is entered, the broker will attempt to discover a default value. If this feature is enabled, ensure that the management user has System Monitor access on the ECS.
Specify whether the ECS system has a certificate installed, which is signed by an available trust authority. This may not be available for development environments, and is not the case for self-signed certificates.
If the installed ECS certificate is not signed by a trust authority, complete the ECS Management Certificate field by entering the ECS certificate.
To overload a value determined from the Base URL, or if no Base URL was provided, complete the ECS Object Endpoint field by entering the URI/endpoint for the ECS S3 API.
Navigate to Service Broker Webservice Settings.
For Service Broker API Version, enter the version of Cloud Foundry Service Broker API to which the broker should respond, or choose * for all versions.
(Optional) For ECS Repository Prefix, enter a string used to prefix broker-created buckets and users. For ECS Test Drive users, use your Namespace value here to ensure that there are no username conflicts between public users.
(Optional) For Repository Endpoint, enter the URI/endpoint for the ECS S3 API that should be used for persisting broker metadata. This defaults to the object endpoint or base URL.
(Optional) For Repository User, enter the name of the user that should be created/used for managing broker metadata.
(Optional) For Repository Bucket, enter the name of the bucket that should be created/used for managing broker metadata.
Navigate to Catalog Service 1.
Review settings for catalog service and plans. These settings define the services available in the PCF marketplace. If any changes are made, click Save.
Review the remaining catalog services. Services 4 and 5 are both disabled by default, but available for customization.
Note: File-enabled buckets and Namespace services will not function on ECS Test Drive.
Return to the Ops Manager Installation Dashboard and click Apply Changes.