EAP Galleon

All

Intro

This a project to make EAP more efficient and smaller specifically for deployment in containers. You basically don’t need the whole EAP with full functionalities, but only the ones you will actually use.

Basically, if I want feature pack 1, 2, 3 and gallons will get the jars needed for those and then it will some how have an example config
and basically pulls the jars from maven

Galleon ~ Cloud native EAP

    Installation

From Git

   Creating an EAP with only the minimal you need ~ using layers:

Just run the command

galleon.sh install wildfly:current --layers=cloud-profile,core-server,core-tools --dir=my-wildfly-server

~ this will create a minimal wildly with cloud-profile, core services, and core tools.

OCP integration

It’s very useful then, to use with Open Shift and provide easy integration. EAP images on OCP are built with Galleon straight from Si2 using Galleon, i.e. Galleon layers, and only brings that specific feature.

Example with jboss-logmanager-2.1.5.Final-redhat-00001.jar

Instead of $JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.5.Final-redhat-00001.jar, which is in EAP 7.x, within a container we will have:

$ find . -name jboss-log\*.jar
./wildfly/s2i/galleon/galleon-m2-repository/org/jboss/logmanager/jboss-logmanager/2.1.15.Final-redhat-00001/jboss-logmanager-2.1.15.Final-redhat-00001.jar
./wildfly/s2i/galleon/galleon-m2-repository/org/jboss/logging/jboss-logging/3.4.1.Final-redhat-00001/jboss-logging-3.4.1.Final-redhat-00001.jar

REFs

https://wildfly.org/news/2019/03/01/Galleon_Openshift/

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s