[
https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5131:
---------------------------------------
clustering - probably need to start with standalone-ha and utilize
and jgroups specifics from the infinispan cluster.xml
Utilizing a config similar to
https://github.com/jboss-openshift/openshift-examples/blob/master/hellowo...
we can specify kube_ping for ha clustering - however the WildFly community distro and
image (
https://github.com/jboss-dockerfiles/wildfly/blob/master/Dockerfile) do not include
the jgroups jars for this.
See
https://github.com/infinispan/infinispan/pull/4448/files that added them into infinispan.
My take away for now is that we won't have ha as part of this templating effort.
add a readiness health check, which could be an admin call testing
for vdb deployment
A readiness check has been added as well. We may want to consider using a less general
health check as it's possible due to metadata or connectvity issues that pod would be
seen as healthy, but not ready - and there wouldn't be any further re-deployments /
actions that would get it to a ready state.
Create ansible playbooks for the ansible service broker
-------------------------------------------------------
Key: TEIID-5131
URL:
https://issues.jboss.org/browse/TEIID-5131
Project: Teiid
Issue Type: Enhancement
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1
For some of the most common usage patterns, we should create playbooks that contribute
service brokers via the ansible service broker. This could be:
salesforce as db
couchbase as db/odata
mongodb as db/odata
other openshift databases as odata
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)