[teiid-issues] [JBoss JIRA] (TEIID-5372) Enhance docker support

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-5372:
---------------------------------------

> Great, I could work on a page describing different deployment models some time next week and put it under Teiid 4 Ways.

I took a pass at changing that page to Teiid Runtimes and reduce the number of mentions of embedded.  We could also use the term Application Runtimes to fully align with RHOAR messaging. 

At most we would then describe each of standalone, docker, and openshift for each of the supported (wildfly, thorntail, spring boot) runtimes.

Based upon our comments we would probably start with:

WildFly: standalone, docker
Thorntail: standalone, openshift
Spring Boot: standalone, openshift

> I'd expect docker instances to be persistently mutable. I'd envision wildfly with docker to be used two-fold:

1) This is similar to the JDV strategy - but there has always been contention around what is the appropriate way to configure EAP.  Since this would be community only, we can show whatever makes sense for us:  A base image, an directory structure of an overlay of modules and other files, cli files that get run as part, etc.  My preference though would be to emphasize or start with 2 to avoid confusion or overlap with what JDV 6.4 and the new tooling is doing.

[~rareddy] any thoughts?



> 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)