Re: [Hawkular-dev] Hawkular Services as Middleware Manager and Ansible

I'd like to resume the discussion as how we will enable the following features: - Start a server/domain - Find Wildfly servers and instrument them with the agent with Ansible in the Middleware Manager ? I'm questioning the packaging and dependencies, Rubens spent some time a while back and we need to resume/conclude: https://github.com/hawkular/hawkular-commons/pull/83/files If I read fast and correctly it seems that: - we have a cyclic dependency(with commons and inventory) - 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) - 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 ? - The code is currently specific to Wildfly ? (Would not work for Fuse on Karaf or should be modified ?) https://github.com/hawkular/hawkular-commons/pull/83/ files#diff-dd195df81855017bb54e44d7c140c04fR72

Note: While I am not directly suggesting Hawkular Services to be more specialized as the middleware manager, it may be something we would want. 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. It would simplify development and message. Thomas