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

[Harald Pehl (JIRA)]

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

Harald Pehl commented on WFCORE-433:
------------------------------------

Thanks [~brian.stansberry] for summarizing! 

I fully agree with you on 2). The WildFly admin console is just a web app which sends DMR requests against a management endpoint. Normally this endpoint is on the same host which the console was shipped form. But since WildFly 9 the console can also be hosted anywhere and connect to arbitrary management endpoints (leveraging CORS and an allowed origins setup) [1]. 

Regarding 3) I patched WF Core to support the console in admin only mode [2]. At first glance, everything seems to work as expected. I can make changes to the management model which end up in the configuration files. This needs to be tested more thoroughly, but the basic setup seem to work. 

In this scenario the user would open a standalone WF admin console and choose a management endpoint to connect to. This endpoint is a WF instance running in admin only mode. Changes to the configuration would then be synced to ConfigAdmin / git. 

[1] https://hal.gitbooks.io/dev/content/release-coordination/distribution.html
[2] https://github.com/hpehl/wildfly-core/commit/c72a14c18faa3ea2044f0580627d487f7b49e0d4

> 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)