<div dir="ltr"><div><div><div>Best would be to go with 3)<br><br></div>as it works directly with mgmt interface without need for CLI interpreter.<br></div>This way commands an be executed ether localy or remotely via REST api.<br>
<br></div><div>CLI enhancements are not all that useful for customizations, beyond few shortcuts with high-level commands.<br></div><div><br></div>Tomaz<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 4, 2014 at 6:16 AM, Stuart Douglas <span dir="ltr"><<a href="mailto:sdouglas@redhat.com" target="_blank">sdouglas@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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>
</blockquote></div><br></div>