[Hawkular-dev] About configuration

[Heiko W.Rupp]

> Am 05.02.2015 um 16:25 schrieb John Mazzitelli <mazz at redhat.com>:
> 
> 1) all configuration, for everything, is in one place. Remember JBoss 4, with all their many .xml config files? It was hard to manage, which is one reason why they went to a single .xml file (though, granted, I believe they are thinking about making it possible to import .xml files into the main config - don't know if that's available yet).
> 
> 2) It gives us, for free, a CLI - we don't have to write and maintain one. If everything is in standalone.xml, we can use the JBoss CLI to look at our config and change it along with the rest of the wildfly subsystems.
> 
> 3) If our components consist of Wildfly Extensions, then this is how you configure that extension. So it would be natural to have all config (for the extension and the other pieces of the component) in the same place.
> 
> 4) Address and port assignments. Right now, standalone.xml allows you to define socket binding groups - allowing a "one stop shop" to define all your port bindings. Adjusting the port-offset provides a nice way to easily offset ports so you can run multiple components on the same box. If we have different configs (that need to specify hostnames/ports), we now have multiple places where this is configured - thus opening up to possible conflicts plus just a pain to have to now go to different places to configure bindings. The port bindings in one place is nice for manageability.
> 
I am absolutely with Mazz here.


> The one negative of this approach is if our components can run outside of being embedded in Wildfly, we lose all of the above. We would need our own configuration mechanism (and CLI) if we can run outside of WildFly.

And still. Hawkular Metrics will still need a container (e.g. WildFly to run on), so for now that standalone metrics will not
be a process. 
And as Mazz said, the properties inside standalone.xml can be read like system properties you pass in via -Dkey=val,
but just live in that central place and not scattered around.

Ptrans is different, agreed.

And in general: we should out of the box (as it was said) deliver settings that are good most of the time.
The installer in RHQ, that is firing a AS7, then modifying its port settings, then rebooting it and using the new
settings should have taught us something...