[JBoss JIRA] (TEIIDSB-23) Document image generation options
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIIDSB-23:
---------------------------------------
> Teams as in the virtualization developer? or overall Integration product?
Product - such that there is a known recommended way of creating and federating instances.
Looking at our image, we are not exporting our metrics. The base image https://hub.docker.com/r/fabric8/s2i-java/ has some well defined options for jolokia, but bakes in the prometheus opts and config file: https://github.com/fabric8io-images/s2i/blob/master/java/images/rhel/prom... (see the exec java javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=9779:/opt/prometheus/prometheus-config.yml)
So need to determine if we should be overriding / contributing to the prometheus config or if we should just use jolokia for now.
> 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)
5 years, 10 months
[JBoss JIRA] (TEIID-5660) With the change to the basebom v25, brings in issue with javadoc override in pipeline build
by Van Halbert (Jira)
Van Halbert created TEIID-5660:
----------------------------------
Summary: With the change to the basebom v25, brings in issue with javadoc override in pipeline build
Key: TEIID-5660
URL: https://issues.jboss.org/browse/TEIID-5660
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Affects Versions: 12.x
Reporter: Van Halbert
Assignee: Steven Hawkins
When the changes were committed last week that changed the basebom version to 25, it now causes a dependency issue with the javadoc override to 3.0.1. If I do the following:
{code}
<version.javadoc.plugin>${dep.plugin.javadoc.version}</version.javadoc.plugin>
{code}
It now builds.
Not sure what we're loosing by using version: 3.0.0-M1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIIDSB-37) Need to add a root pom to the teiid-openshift-examples repo
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-37?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIIDSB-37.
---------------------------------
Resolution: Done
Accepted the PR. I was not considering this to be in the pipeline build or Travis, but there is no harm in doing so. As I expect this repository to be more about showcase deployment into OpenShift that is more of How can I? type examples and documentation.
> Need to add a root pom to the teiid-openshift-examples repo
> -----------------------------------------------------------
>
> Key: TEIIDSB-37
> URL: https://issues.jboss.org/browse/TEIIDSB-37
> Project: Teiid Spring Boot
> Issue Type: Enhancement
> Components: examples
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> The teiid-openshift-examples needs a root pom in order to trigger the sub-projects for building.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIIDSB-23) Document image generation options
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIIDSB-23:
-------------------------------------
Teams as in the virtualization developer? or overall Integration product? I am proposing this example as the first case and a way to showcase how one can do that.
> 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)
5 years, 10 months