Hi Amulya,

Using user-provided-services can be a good way to manage your service
instances if it is challenging to automate provisioning, but it sounds like
one of your main hurdles is needing to coordinate with an CF admin to
update a broker.

There's a relatively new option to create a private service broker that is
scoped to a particular space. Dr. Nic has a good blog post
<https://blog.starkandwayne.com/2015/11/18/register-your-own-service-broker-with-any-cloud-foundry/> explaining
this. I think the advantages of using the CF services workflow are nice,
especially not needing to learn an external system and having
dynamically-generated and secure credentials.


Cheers,
Dan

On Mon, May 16, 2016 at 11:20 AM, Amulya Sharma <amulya.sharma(a)gmail.com>
wrote:

Question on not using cf Service Broker or only use Private Broker,

We have Service Broker in CF its kind of hassel to maintain service
brokers as it need admin privileges to register also unique names and all
upgrade path is complex.

What if we do not use service brokers at all instead we just create a
portal to create service instance and at the end of creation just show VCAP
variables of service and a CUPS Command to create that service instance in
CF CLI

my question is

Q What are the downside of this approach of not using service broker at
all?

pro side is decoupling of service offering from CF ?

Actually, we are creating the a service marketplace, and meet the same
problem, too: when we add a new service from the service marketplace, it
need to be registered in the CF side.

But with the service broker, we can manage the services just like managing
the instances. You can set a usage restrictions on the service, make it
only be consumed by a given team/org (defined in CF).

Actually, we are creating the a service marketplace, and meet the same
problem, too: when we add a new service from the service marketplace, it
need to be registered in the CF side.

But with the service broker, we can manage the services just like managing
the instances. You can set a usage restrictions on the service, make it
only be consumed by a given team/org (defined in CF).

Sorry for the name misunderstanding... We use the word "marketplace", but
not the term in CF.

The background is, firstly it is a public cloud, people use CF and the
services provided by the CF; We built a framework (not like service broker)
to help people contribute different service, then sell the services in it
to the developers using Cloud Foundry. (The services can be used in CF, by
the service broker we build; but it also in K8S and other PaaS. But mainly
it is used in CF currently...)

So the problem is, when a new contribution, such as MySQL based on
Brooklyn added to the marketplace, we need to register it to the CF.

I am not sure if it is clear enough, if you interested in it, I can share
some introduction videos.

Thank You all .. for responding ..

my whole idea is to simplify

Large Market place
Service/Plan visibility
Billing and offering
self hosted or SaaS providers

by taking market place as separate component to pair with Cloud Foundry


but we all are saying same thing .. believe me after running multiple bosh
services managing marketplace in a large org is kind of a messy jobs ..



On Tue, May 17, 2016 at 1:27 AM Layne Peng <layne.peng(a)emc.com
<javascript:_e(%7B%7D,'cvml','layne.peng(a)emc.com');>> wrote:

Sorry for the name misunderstanding... We use the word "marketplace", but
not the term in CF.

The background is, firstly it is a public cloud, people use CF and the
services provided by the CF; We built a framework (not like service broker)
to help people contribute different service, then sell the services in it
to the developers using Cloud Foundry. (The services can be used in CF, by
the service broker we build; but it also in K8S and other PaaS. But mainly
it is used in CF currently...)

So the problem is, when a new contribution, such as MySQL based on
Brooklyn added to the marketplace, we need to register it to the CF.

I am not sure if it is clear enough, if you interested in it, I can share
some introduction videos.

but we all are saying same thing .. believe me after running multiple

bosh

services managing marketplace in a large org is kind of a messy jobs ..

I cannot agree more!