<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jun 14, 2016 at 3:53 AM, Stuart Douglas <span dir="ltr"><<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Everyone,<br><br></div>Recently a few of us had a meeting to discuss a new provisioning/patching system for Wildfly. I have written up the notes for this meeting which are at [1].<br></div></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The document contains the full details, but the basic idea is to design a provisioning/patching/package management system for Wildfly and downstream products. This will not be based on our existing patching or feature pack code, but should take over the responsibilities of both.<br><br></div><div>Obviously this is still in the early stages, and any feedback is welcome.<br></div><div><br></div>Stuart<br><div><div><div><br>[1] <a href="https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc" target="_blank">https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc</a><br></div></div></div></div>
<br></blockquote><div>Hi Stuart,</div><div><br></div><div>Thanks for the doc!</div><div><br></div><div>It wasn't quite clear to me from the 'Multiple FS Locations', section, but would the provisioning tool take a list of installed servers and attempt the same operation on them all (for example applying a the relevant patch to each individual server), or is it expected to operate on one server at a time?</div><div><br></div><div>Ken</div></div></div></div>