Re: Team


Ronak Banka
 

Hi Amulya,

Using cups for service binding has no down side because that is how
services are consumed if we ignore service broker.

Whole point of using service broker with cf is to consume service api's in
best possible way , managing 1 or 2 services with cups sounds good but when
you have large number of services then service broker plays important role
specially in service provisioning automation .

We have different teams exposing their api's and it is very easy for us to
consume those services and provide them to users on platform, increases
value of platform itself on business side .

It also helps our users to get information about their provisioned services
and manage them without maintaining any other information documents.

Thanks
Ronak Banka

On Tue, May 17, 2016 at 6:59 AM, Amulya Sharma <amulya.sharma(a)gmail.com>
wrote:

Thanks Dan,

but Services have nothing to do with cloud foundry .. the only job broker
is doing here is publishing themselves in marketplace .. wondering why it
need to be this way why not totally independent from cloud foundry..



On Mon, May 16, 2016 at 12:40 PM Dan Wendorf <dwendorf(a)pivotal.io> wrote:

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 ?


Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.