[teiid-issues] [JBoss JIRA] (TEIIDSB-23) Document image generation options

[Steven Hawkins (Jira)]

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

Steven Hawkins edited comment on TEIIDSB-23 at 2/18/19 11:50 AM:
-----------------------------------------------------------------

There is a question of whether to separate out the additional prometheus config from the base example.  Here are a couple of thoughts:
- doing that would only be meaningful if we turn off jmx_exporter (and probably jolokia) in the base image deployment config.  Since they are enabled by default, we are already using the base prometheus config from the s2i image.  If we do disable them, we'll have to also account for that template change in the prometheus project.
- related to the first point, we could determine how much overhead there is in exposing these - should we for example never have jolokia enabled?
- it seems like this will require the base project being an arche-type, or we'll have to have instructions / maven logic that will do a checkout of the example and overlay.  Alternatively it could all be done in a new deployment config template that injects the prometheus config via a configmap (like the prometheus template).


was (Author: shawkins):
There is a question of whether to separate out the additional prometheus config from the base example.  Here are a couple of thoughts:
- doing that would only be meaningful if we turn off jmx_exporter (and probably jolokia) in the base image deployment config.  Since they are enabled by default, we are already using the base prometheus config from the s2i image.  If we do disable them, we'll have to also account for that template change in the prometheus project.
- related to the first point, we could determine how much overhead there is in exposing these - should we for example never have jolokia enabled?
- it seems like this will require the base project being an arche-type, or we'll have to have instructions / maven logic that will do a checkout of the example and overlay.

> Document image generation options
> ---------------------------------
>
>                 Key: TEIIDSB-23
>                 URL: https://issues.jboss.org/browse/TEIIDSB-23
>             Project: Teiid Spring Boot
>          Issue Type: Task
>            Reporter: Steven Hawkins
>            Priority: Major
>             Fix For: Q119
>
>
> We need to document / validate all relevant image options:
> - inclusion of agent bond or other mechanism for jmx exposure to prometheus.  There may also be related service annotations
> - annotations for 3scale for rest and openapi exposure of odata
> - any common config options - disk buffer memory, max active plans / engine threads / connection pool sizes.  Ideally the buffer manager heap should auto-configure and we should probably always use off-heap for the fixed memory buffer.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)