[jboss-jira] [JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly

[James Strachan (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245106#comment-13245106 ] 

James Strachan commented on WFCORE-433:
---------------------------------------

BTW we have an implementation of a reusable microservice or command for automatically upgrading the git commit sha used to provide configuration files from git in kubernetes here:
https://github.com/fabric8io/gitcontroller

This lets you mount configuration files to a volume in kubernetes; such as this example:
https://github.com/jstrachan/springboot-config-demo/blob/master/src/main/fabric8/deployment.yml#L5-L14

so provided the standalone.xml files or whatever are stored in git; it'd be easy to use them in an EAP/wildfly/wildfly swarm docker image. The only thing to watch with gitRepo volumes with kubernetes is to ensure that the configuration files are mounted to a folder that your microservice can then read them from (and you don't try and mix and match the same folder for configuration and secrets/code).

There's more detail on the configuration tradeoffs of microservices on kubernetes here:
http://fabric8.io/guide/develop/configuration.html

> git backend for loading/storing the configuration XML for wildfly
> -----------------------------------------------------------------
>
>                 Key: WFCORE-433
>                 URL: https://issues.jboss.org/browse/WFCORE-433
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: James Strachan
>            Assignee: Jason Greene
>
> when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker, heroku et al) it'd be great to have a git repository for the configuration folder so that writes work something like:
> * git pull
> * write the, say, standalone.xml file
> * git commit -a -m "some comment"
> * git push
> (with a handler to deal with conflicts; such as last write wins).
> Then an optional periodic 'git pull' and reload configuration if there is a change.
> This would then mean that folks could use a number of wildfly containers using docker / openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly management console within cloud environments (as the management console would, under the covers, be loading/saving from/to git)
> Folks could then benefit from git tooling when dealing with versioning and audit logs of changes to the XML; along with getting the benefit of branching, tagging.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)