thecodeteam / ecs-broker-boshrelease Goto Github PK

Support a property to modify the number of running instances.

Currently the tile includes base configuration, but doesn't allow for customization of services and plans for namespaces and buckets. This will limit tile-based to deploys to situations when the default services are acceptable, which will be relatively few production deployments.

Object-endpoint parameter should be optional. The Base URL param is the preferred way to set this. Actually, the base URL is even optional, as the broker will attempt to detect a default.

Instructions that describe this should be handled in #4

Currently, the ECS Broker API Version can be configured via the BOSH release manifest, but not by environment variable. We will need to wire the environment variable to the BOSH release property.

The current tile UI should probably provide a bit more explanation on how the object-endpoint, base-url and repository-endpoint parameters interact.

The preferred method for broker configuration, should probably be the base-url. This allows the user to specify the name of the ECS configured "Base URL", and lookup the actual hostname through the ECS management API.

The object-endpoint is a way to configure the URL directly, without the use of a "Base URL" for situations when the actual URL is not configured in ECS. I think this should be relatively rare, but we ran into it when supporting ECS TestDrive.

The repository-endpoint is a way to override the object endpoint, when the repository bucket is accessible via a different endpoint than the buckets. Again, somewhat rare.

Customers have run into an issue with repointing the URL during tile upgrades. This can probably be best fixed by adding blue/green deploys of the broker app with autopilot.

I believe we should match up the version of the service broker API version to the currently release of PCF. As of PCF 1.11, the service broker API version should be 2.1, rather than 2.11. When PCF 1.12 drops, we can then up-rev to 2.1.

Maybe, PCF 1.12 is forthcoming very quickly, which would make this a mute point.

The one that I used originally scales kind of strange in the PCF apps-manager UI. Maybe we should use this one from the EMCECS GH org?

It looks pretty nice. Should probably find a way to incorporate it in the BOSH release instead of serving it over the internet, too. Maybe put it in the repository bucket...

Currently, credentials are supplied in the configuration. Since these credentials are really between the CAPI & broker, the customer really shouldn't care about how they're chosen. This secret can be automatically generated and added to the BOSH/OpsMgr credentials.