Microgateway setup without Service Broker

We are using HSDP (our company's wrapper around pivotal cloud foundry) for hosting our backend, and are unable to deploy the Apigee Service Broker, described in the setup instructions for both Microgateway and Microgateway-Coresident.

HSDP does not allow us to deploy our own service broker, so I am wondering how we can install the Apigee Microgateway Service manually, without using the convenience of the Apigee Service Broker, to do so.

Specifically, we are hoping we can use "cf create-user-provided-service" to create a service from a microgateway service built locally and pushed via "cf push", instead of having the Apigee Service Broker create it for us (as specified in the instructions here -- https://github.com/apigee/cloud-foundry-apigee/blob/master/docs/setup-microgateway-coresident.md)

Can you help us achieve this? We only saw instructions for using the convenient Apigee Service Broker, and did not find any related topics in the community!

0 4 275
4 REPLIES 4

Hey Jesse,

The convenience that the service broker does for the MG plan is that it sets up the microgateway proxy's edge component for you as well as returning back to cloud foundry the correct url to reroute to (e.g your container running the MG application). So as long as you're fine going through the steps to create the edge component of the MG proxy separately from the service broker, I don't see why you couldn't do this through a CUPS with the route options provided.

If you're more curious about the co-resident plan, that's a bit different since we don't use route services. For that one, we still set up the edge component of the MG for you, but instead of passing back the route for CF to re-route requests to, we use your parameters to set certain VCAP_SERVICES configurations which the supply buildpack can read in and configure the the associated MG with. So you could do this with a CUPS as well, you'd just need to be sure to pass in the correct parameters such that the buildpack can read them in (e.g org, env, key, secret, proxy). In addition, when you do set up the MG on the edge side of things, you'll need to make sure it sets the target to be localhost with the correct port of your application that's running.

Hope this helps!

Kyle

Hey @Kyle Wiese: do you know if there is an open-source repo somewhere for us to create the CUPS with, which will be similar to what the service broker would otherwise create?

We saw that Edge Microgateway also pushes analytics, so we would like to keep that functionality (and other features provided by the service instance typically created with the service broker) as well.

We'd really like to create an Edge Microgateway Service instance identical to the one that the service broker would create, through open-source/etc usage. Do you know if that is possible, or if not, perhaps a good starting place or reference material?

Thanks!

Unfortunately I'm not aware of any open source repos that are currently using CUPS to mimic the apigee service broker. So the closest I know of is by taking a closer look at our opensource Service Broker implementation to see if that will help you get closer to where you need to be.

Thank You so much for sharing this information! It was really helpful, nice thread!