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

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 4:08 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). 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? 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). * Ideas: * We may use the Broker to instrument the deployed JDG instances * We may use the Broker to instantiate JDG instances outside of the cloud. During the Bind step we could provide credentials to connect to it. In addition to that we'd need to manually facilitate {{Endpoints}} objects pointing to the cluster. * During the bind operation we should provide {{hotrod-client.properties}}. * 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? -- This message was sent by Atlassian JIRA (v7.2.3#72005)