<div dir="ltr"><div>Thomas,</div><div><br></div><div>Here is some threads about the provisioning discussion:</div><div><br></div><div><a href="http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002330.html">http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002330.html</a></div>
<div><a href="http://lists.jboss.org/pipermail/wildfly-dev/2014-July/002523.html">http://lists.jboss.org/pipermail/wildfly-dev/2014-July/002523.html</a></div><div><a href="http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002831.html">http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002831.html</a></div>
<div><a href="http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002912.html">http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002912.html</a></div><div><a href="http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002919.html">http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002919.html</a></div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-09-04 7:15 GMT-03:00 Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I would need to provision Wildfly remotely with something like JON or<br>
Fabric8 for instance, the CLI would not work for that if I understand<br>
correctly.<br>
<br>
REST-ish API would work better I think (I guess option 3 covers that),<br>
Fabric8 preference would likely be option 1 though (note that in this<br>
usecase the end-user doesn't really touch the XML files, he's using a tool)<br>
<br>
BTW: I completely missed the discussion about provisioning tool until<br>
this email so please forgive my ignorance. If there is a document or<br>
email thread that would help me catch up I would love to have a look.<br>
<span class="HOEnZb"><font color="#888888"><br>
Thomas<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 09/04/2014 06:16 AM, Stuart Douglas wrote:<br>
> Hi everyone,<br>
><br>
> Work on the provisioning tool is now well underway, so I would like to<br>
> revisit something I mentioned in my original email, which is allowing<br>
> the provisioning tool to customize a provisioned server.<br>
><br>
> I think there are a few options here, some more palatable than others.<br>
> In no particular order:<br>
><br>
> 1) Customize the XML directly<br>
><br>
> Using this approach we would just directly customize the XML<br>
> configuration files. This would basically require the use of XSLT<br>
> (yuck), or require us to basically invent our own version of XSLT (even<br>
> more yuck). Even though this approach will work, and will be fairly easy<br>
> to implement, I think it would really suck from an end-user point of<br>
> view, and I think we should discount it.<br>
><br>
> 2) Allow the user to provide CLI commands to customise the server<br>
><br>
> This is by far my favorite approach. The provisioning file would just<br>
> contain a list of CLI commands, and would execute them in order. I think<br>
> this is by far the most intuitive, and the CLI is well documented.<br>
><br>
> 3) Allow the user to provide DMR operations to customize the server<br>
><br>
> Similar to 2, but allow the user to provide DMR or JSON operations to<br>
> customize the server. I think this is not nearly as nice as 2, as users<br>
> are much more likely to be familiar with the CLI rather than DMR.<br>
><br>
><br>
> I think 2 is by far the best approach, however it does open up the<br>
> question of how and when to execute the operations. I think the easiest<br>
> way to do this would be to just start the server in admin only mode on a<br>
> custom port (so it will not interfere with any existing running Wildfly<br>
> instances), and just execute the CLI commands in admin only mode.<br>
><br>
> Does this all sound reasonable?<br>
><br>
> Stuart<br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><span style="font-family:Arial;font-size:small">________________</span><span style="font-family:Arial;font-size:small">__________</span><br>
</div><div><div align="left" style="font-family:Arial;font-size:small">Eduardo Sant'Ana da Silva - Dr.</div><div style="font-family:Arial;font-size:small"><font face="Arial">Pesquisador / Consultor de TI<br></font></div>
<div style="font-family:Arial;font-size:small"><br></div></div></div>
</div>