[infinispan-issues] [JBoss JIRA] (ISPN-7973) Investigate Service Brokers

Sebastian Łaskawiec (JIRA) issues at jboss.org
Wed Jul 12 04:09:03 EDT 2017


    [ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434371#comment-13434371 ] 

Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 4:09 AM:
--------------------------------------------------------------------

Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]:
* Marko implemented En Masse.
* The Broker controls instances it created. E.g. we might imagine having a JDG Broker which will add a cache to all living instances.
* The {{ServicePlan}} is a resource incorporated into {{ServiceClass}}. It is not separate.
* The Broker can instantiate the service synchronously or asynchronously.
* The client can specify the name of a {{Secret}} with credentials. Currently users need to preconfigure their apps (to use the secret provided by the Catalog). There are plans to make it the other way around.
* An {{Endpoints}} object contains a list of IP addresses and ports to desired Pods (or other type of services)
* The Boker Pod can provide its own UI (it's just a running Pod).


was (Author: sebastian.laskawiec):
Based on [discussion between Marko Luksa and Emmanuel Bernard|https://bluejeans.com/s/uij6Y]:
* Marko implemented En Masse.
* The Broker controls instances it created. E.g. we might imagine having a JDG Broker which will add a cache to all living instances.
* The {{ServicePlan}} is a resource incorporated into {{ServiceClass}}. It is not separate.
* The Broker can instantiate the service synchronously or asynchronously.
* The client can specify the name of a {{Secret}} with credentials. Currently users need to preconfigure their apps (to use the secret provided by the Catalog). There are plans to make it the other way around.
* An {{Endpoints}} object contains a list of IP addresses and ports to desired Pods (or other type of services)
* The Boker Pod can provide its own UI (it's just a running Pod).

Things to clarify and other issues:
* No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it).
* Shall we create separate separate service or one service with multiple plans?

> Investigate Service Brokers
> ---------------------------
>
>                 Key: ISPN-7973
>                 URL: https://issues.jboss.org/browse/ISPN-7973
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cloud Integrations
>            Reporter: Sebastian Łaskawiec
>            Assignee: Sebastian Łaskawiec
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the infinispan-issues mailing list