thecodeteam / ecs-broker-tile Goto Github PK

The latest Pivotal tile generator has support for additional deployment types, including a Cloud Foundry hosted app service-broker.

This support will greatly simplify the broker tile, as the custom BOSH jobs which deploy, register and delete the broker can (potentially) be eliminated.

In order to accomplish this, however, the process of deploying the broker will need to be simplified. Currently, the BOSH release generates an application.yml file and certificate.pem file, and recomplies the JAR file of the app with these additions. This process is too customized to be supported by the new Tile generator method.

Alternatively, the broker can make use of environment variables to configure the certificate, broker configuration and environment variables.

Current service icon looks bad and is a bit outdated. So are the links to support and documentation.
For example, product link should point not to emc.com, but to Dell Technologies page: https://www.delltechnologies.com/en-us/storage/ecs/index.htm

Retention policy classes are 'key-value' entries in a map, currently supported only via additional parameters for create operations. Worth adding inputs to tile UI.

Added issue t track in the docs repo:
pivotal-cf/docs-ecs-service-broker#11

Add optional deployment settings, allowing to choose org, space and broker name.

Namespace binding request has two optional parameters - 'base url' and 'use-ssl' - affecting how S3 url is generated. Those two options can be added to namespace catalog service definition.

After install / upgrade to 2.0, marketplace missing image and descriptions for services provided by ECS broker.
When catalog is queried, all values are present in service metadata, but keys are lowercase (imageurl instead of `imageUrl, etc).

This turned out to be caused by behavior change in Spring Boot variables binder. Tile should provide values with changed env names: instead of CATALOG_SERVICES[0]_METADATA[imageUrl] use 'catalog.services[0].metadata.imageUrl'.

Need to verify TAS 2.11 compatibility:
https://docs.pivotal.io/application-service/2-11/overview/release-notes/runtime-rn.html

Java 11 is the current LTS, tile should start using it in runtime.

Currently, the catalog configuration allows the operator to create up to 5 services, with a variable number of plans for each service. These services are then injected into the broker application by a BOSH release, which generates an application.yml file with each service and plan details.

When using tile generator process outlined in #15, The catalog services will need to be injected by environment variables. The format for these environment variables will look something like:

...
  CATALOG_SERVICES_0_ID: 09cac1c6-1b0a-11e6-b6ba-3e1d05defe78
  CATALOG_SERVICES_0_NAME: ecs-namespace
  CATALOG_SERVICES_0_BINDABLE: true
  CATALOG_SERVICES_0_TAGS_0: s3
...

I'm not quite sure yet how to handle the variable number of plans when injecting them as env variables...

This means, that the ECS CF service broker may need to be updated to handle "disabled" services.

Please refer to the changes in #7 (closed without merge) for catalog entries can should be removed.

Currently, there is overlap between services and plans, and it's confusing. We should explicitly call out overlap, or eliminate it.

For Ops Manager, version migrations are defined as Javascript files that convert previous tile properties to new ones.

An example of this can be found here.

After upgrade from 1.2.x, users end up with two applications and two brokers, and that is at least very confusing, at most - causes upgrade errors.

Review upgrade code - check if renames are really needed for installations done in current-styled namespaces.