[
https://issues.apache.org/jira/browse/ARTEMIS-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736049#comment-17736049
]
Gary Tully commented on ARTEMIS-4324:
-------------------------------------
podman and docker are interchangeable for the purpose of the
[README.md|https://github.com/apache/activemq-artemis/blob/587ffb223cd2461a9da5c53e5ac189b9aa24640c/artemis-image/README.md],
the project creates an OCI image.tar that can be published or loaded into a
registry.
In the
[README.md|https://github.com/apache/activemq-artemis/blob/587ffb223cd2461a9da5c53e5ac189b9aa24640c/artemis-image/README.md]
for comprehension - s/podman/docker/
Why a java main line?
- for simplicity - the intent is to present the broker as a java app and
expose that, so that the JVM is visible and configurable etc. artemis run and
the distro scripts are focused on bare metal where it has to coexist and be
update-able etc... none of that is relevant for an immutable image. In
addition, as the JVM becomes more container aware w.r.t to container limits,
less and less of the bare metal defaults make sense.
The main wraps the current embedded broker (which is well proven and tested)
and waits for it to exit (like ArtemisRun).
I think there is a case to be made for a single entry point, and maybe I can
replace the Main with the ArtemisRun wrapper, or extract out the relevant bits
and reuse, but I don't want to expose any unnecessary options, just the
necessary ones.
I also want properties to be the mechanism for customisation. ie a broker is a
Broker 'bean' and a few property files that tweak the defaults. A derived
broker adds some more custom.properties and that is it.
> extensible OCI image tar for the broker; java -jar with properties files and
> optional base xml config
> ------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4324
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4324
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, Configuration, image
> Affects Versions: 2.29.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.29.0
>
>
> Provide the ability to build a simple usable but extensible base image of the
> embedded broker.
> java -jar Broker with its defaults and a mount point for property files that
> can augment configuration.
> This is an OCI tar image that can be built from source and loaded into any
> container registry.
> For a image, that is extensible and configurable, but ultimately idempotent,
> there is no need for a build or install or artemis create, we can just use
> the java jar dependencies and run a simple java app with full control of env,
> classpath and configuration via mount points.
> The properties config in the broker is at the point where 90% of the xml
> configuration is possible via property files. We can add the last 10% as the
> need arises.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
