[
https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin...
]
Rafal Korytkowski edited comment on TEIID-5372 at 6/22/18 9:33 AM:
-------------------------------------------------------------------
I looked at "thorntail-teiid-examples" and one of them
"vdb-datafederation" is actually showcasing OpenShift as one of deployment
scenarios. We have a lot of good tutorials, but somehow I do not find them unless you
point me to them :) I think what we need is to create a page summarizing possible teiid
deployments (or maybe there's one?) including wildfly, wildfly with docker, thorntail
and openshift. It should be linked from the teiid/REAMDE.md and be part of Teiid
documentation. It doesn't make sense to me to duplicate examples using different
deployment scenarios. The least I'd do is to point to a document with other deployment
options and, depending on how much work it is, use one deployment option e.g. thorntail
across as many examples as possible.
When using Thorntail, the Docker image you create is never a base one, rather a targeted
one for your specific purpose with selected data source drivers, teiid translators, vdbs.
It uses maven as a build tool to produce a customized version of Teiid. It's
definitely the way forward for microservices.
I still think there's a value of supporting a standalone Teiid on Wildfly as a base
image. It's an interesting option for building a Teiid instance purely with Docker as
a build tool. It also allows to quickly evaluate Teiid giving an ability to start it with
just one docker command. No Java tooling and experience needed. Similarly it can be handy
for development purposes when working on Teiid core. However, we would need a proper
HOWTO. I found
https://developer.jboss.org/wiki/QuickstartExampleWithDockerizedTeiid, but
I don't think it does things in the easiest way (it's 3 years old now and things
got improved). JBoss images I checked are all based on jboss/base (CentOS), which seems to
be preferred so I'd stick to that and would not introduce Alpine at this point.
was (Author: rkorytkowski):
I looked at "thorntail-teiid-examples" and one of them
"vdb-datafederation" is actually showcasing OpenShift as one of deployment
scenarios. We have a lot of good tutorials, but somehow I do not find them unless you
point me to them :) I think what we need is to create a page summarizing possible teiid
deployments (or maybe there's one?) including wildfly, wildfly with docker, thorntail
and openshift. It should be linked from the teiid/REAMDE.md and be part of Teiid
documentation. It doesn't make sense to me to duplicate examples using different
deployment scenarios. The least I'd do is to point to a document with other deployment
options and depending on how much work it is use one deployment option e.g. thorntail
across as many examples as possible.
When using Thorntail, the Docker image you create is never a base one, rather a targeted
one for your specific purpose with selected data source drivers, teiid translators, vdbs.
It uses maven as a build tool to produce a customized version of Teiid. It's
definitely the way forward for microservices.
I still think there's a value of supporting a standalone Teiid on Wildfly as a base
image. It's an interesting option for building a Teiid instance purely with Docker as
a build tool. It also allows to quickly evaluate Teiid giving an ability to start it with
just one docker command. No Java tooling and experience needed. Similarly it can be handy
for development purposes when working on Teiid core. However, we would need a proper
HOWTO. I found
https://developer.jboss.org/wiki/QuickstartExampleWithDockerizedTeiid, but
I don't think it does things in the easiest way (it's 3 years old now and things
got improved). JBoss images I checked are all based on jboss/base (CentOS), which seems to
be preferred so I'd stick to that and would not introduce Alpine at this point.
Enhance docker support
----------------------
Key: TEIID-5372
URL:
https://issues.jboss.org/browse/TEIID-5372
Project: Teiid
Issue Type: Enhancement
Reporter: Rafal Korytkowski
Assignee: Rafal Korytkowski
Priority: Optional
Currently there's limited support for docker in Teiid, which can be enabled by adding
-Ddocker=true to the build command. The generated image is based on CentOS and running
standalone on the Wildfly server. Latest builds are pushed to
https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with
releases. Development with Docker is not supported.
Proposed changes:
1. Produce docker image based on Alpine, which is better suited for microservices, in
addition to CentOS.
2. Automatically tag versions in Docker when doing releases.
3. Support development by providing a docker-compose file with the possibility to start
server in a debug mode and enabled auto-redeployment of code changes.
4. Optionally provide a Docker image for building code using maven in Docker. Having
Docker as the only prerequisite is convenient for CI environments and makes the build
environment agnostic.
[~shawkins], [~rareddy], thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)