Heiko W.Rupp wrote on 07/27/16 14:57:
On 21 Jul 2016, at 0:49, Aleksandar Kostadinov wrote:
> I should have explained better. The config is saved on container. But
> container being stateless loses changes on restart. At least for
Yeah, that is a bit of an issue. One needs to mount the whole config
dir to an external volume(*) and then on container creation populate it
with a default configuration.
Or externalize the changes of the standard config and apply it each
time at container start (docker run, not docker start).
OpenShift does support persistent volumes. Thinking about auto-scale I'm
not sure that would help a lot though.
I'm wondering whether domain mode can help - having domain node(s) with
persistent storage configuration for management. Then the worker nodes
would read config from domain.
I suspect though most people would not want to waste resources for
non-worker nodes and would expect to have things working OOB in some
simple manner. Perhaps wildfly may support committing configuration
changes in whatever format to some external system (git, file server,
whatever), then read it from there.
e.g. if wildfly can commit any and all configuration changes to git, an
OpenShift deployment config can trigger redeploy based on the noticed
changes automatically (or user can trigger manually).
btw it would help if Wildfly records only changes from defaults (not all
configuration files). In this way migrating between versions and
changing defaults might work much smoother.