[teiid-issues] [JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-5007:
---------------------------------------

> I am guessing that will work for Teiid.

What I thought you were getting at was using as a reference is https://github.com/jboss-openshift/openshift-examples/blob/master/helloworld/configuration/standalone-openshift.xml

Which then requires adding in the module for KUBE_PING support.

I thought there would be a wildfly image with support already there and change our image to layer on it, but I haven't found one yet.  The official images https://github.com/openshift-s2i/s2i-wildfly/tree/master/11.0 don't seem to have anything for ha.

> we need to use same stack as "kubernates" which looks same as in clustered.xml

What are you referring to?


> Changes to reduce Teiid in the cloud footprint
> ----------------------------------------------
>
>                 Key: TEIID-5007
>                 URL: https://issues.jboss.org/browse/TEIID-5007
>             Project: Teiid
>          Issue Type: Quality Risk
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.1
>
>
> A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint.   This includes:
> * container aware auto-sizing.  Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection.  We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data)
> * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions.
> * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)