[
https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5372:
---------------------------------------
we have "thorntail-teiid-examples" but not yet
"openshift-teiid-examples"
I'm ok with having both Thorntail and OpenShift examples as needed.
we need a way to showcase how we can take the same example and deploy
standalone and OpenShift
Yes, we can create a subtask to convert all of the old embedded examples to either
Thorntail or full OpenShift.
What else can we think of improvements here?
Per some other discussions, perhaps a static build time validation when the metadata is
fully specified.
Define how other artifacts make it into the archive - just a maven assembly?
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)