<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 29, 2016 at 3:03 PM, Thomas Heute <span dir="ltr"><<a href="mailto:theute@redhat.com" target="_blank">theute@redhat.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><div><div><div><div><div><div><div><div>I'd like to resume the discussion as how we will enable the following features:<br></div> - Start a server/domain<br></div> - Find Wildfly servers and instrument them with the agent<br></div>with Ansible in the Middleware Manager ?<br><br></div>I'm questioning the packaging and dependencies, Rubens spent some time a while back and we need to resume/conclude:<br><a href="https://github.com/hawkular/hawkular-commons/pull/83/files" target="_blank">https://github.com/hawkular/<wbr>hawkular-commons/pull/83/files</a><br><br></div>If I read fast and correctly it seems that:<br></div> - we have a cyclic dependency(with commons and inventory)<br></div> - the code should not be in common (actually the whole commands-gateway doesn't belong to commons if we consider that commons was supposed to be shared among Alert/Metrics/APM/Services)<br></div> - The playbooks are not part of Hawkular-services so they would be added separately ? Or hawkular-services would be less and less generic / more and more related to the MW Manager ?<br></div> - The code is currently specific to Wildfly ? (Would not work for Fuse on Karaf or should be modified ?)<br> <a href="https://github.com/hawkular/hawkular-commons/pull/83/files#diff-dd195df81855017bb54e44d7c140c04fR72" target="_blank">https://github.com/hawkular/<wbr>hawkular-commons/pull/83/<wbr>files#diff-<wbr>dd195df81855017bb54e44d7c140c0<wbr>4fR72</a></div></div></blockquote><div><br></div><div>Well the whole command-gateway depend on WF anyway, so we would need a twist for Karaf/JMX based products<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br><br></div>Note: While I am not directly suggesting Hawkular Services to be more specialized as the middleware manager, it may be something we would want.<br>Hawkular for Manage IQ (currently hawkular-services) and Hawkular for Kubernetes/OpenShift (currently HAM), the first should extend the second so that one could just use the first as MW Manager and solution for OpenShift.<br>It would simplify development and message.<span class="HOEnZb"><font color="#888888"><br><div><div><div><div><div><br><div><div><div><div><div><div><div><div><div><br></div><div>Thomas<br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></font></span></div>
</blockquote></div><br></div></div>