<div dir="ltr">Here the first problem I would like to solve is really to start a server (say a server crashed) from Hawkular.<div>Second, discover servers that are not yet instrumented and/or started.</div><div><br></div><div>I'm looking for options (extending/reusing existing projects is definitely a +1)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 9, 2016 at 3:20 PM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I mean WF servers<br>
<br>
The Hawkular Wildfly Agent can monitor remote WildFly servers. It just doesn't discover them nor does it have the ability to start them (but it does have the ability to restart them, or shut them down).<br>
<br>
The "embedded agent" can live in any WildFly server. So really, we could ship a standalone agent that consists of nothing more than a vanilla WildFly Server with the agent installed in it (we used to be able to run in WildFly Core, but I don't think it can today with some dependencies the agent has). But a stripped down WildFly (removing unused things like the tx manager, deployment scanner, things like that) could be used to house a standalone agent.<br>
<br>
If something can auto-discovery WildFly servers, they can issue JBoss CLI commands to the wildfly server/agent combo to add a <remote-dmr> setting so that agent can start monitoring those discovered servers. Or you can inject an agent to discovered WildFly servers using the installer. What that "auto-discovery" process is, I dunno.<br>
<br>
Just wanted to bring that up.<br>
<div class="HOEnZb"><div class="h5"><br>
----- Original Message -----<br>
> I mean WF servers<br>
><br>
> On Tue, Feb 9, 2016 at 2:16 PM, John Mazzitelli <<a href="mailto:mazz@redhat.com">mazz@redhat.com</a>> wrote:<br>
><br>
> > When you say "discover servers" and "start servers" - what do you mean by<br>
> > servers? WildFly servers or just machines (bare metal computers, VMs, etc)?<br>
> ><br>
> > ----- Original Message -----<br>
> > ><br>
> > > With embedded agents, we lost few main features:<br>
> > > - Ability to discover servers that are off or not (yet) instrumented<br>
> > > - Ability to start servers remotely<br>
> > > - Ability to report DOWN availability (other than by lack of UP)<br>
> > ><br>
> > > Should we reintroduce a small (optional ?) host agent ?<br>
> > ><br>
> > > The agent would only fulfill those tasks (+ embedded agent installer) and<br>
> > > redirect all other tasks to the embedded agents.<br>
> > ><br>
> > > We can address a limited set of platforms (Linux only) to start with, and<br>
> > > maybe use environment specific features if those exists (Like RHEV-M host<br>
> > > agent if appropriate)<br>
> > ><br>
> > > WDYT ?<br>
> > ><br>
> > > Thomas<br>
> > ><br>
> > > _______________________________________________<br>
> > > hawkular-dev mailing list<br>
> > > <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> > > <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> > ><br>
> > _______________________________________________<br>
> > hawkular-dev mailing list<br>
> > <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> ><br>
> ><br>
> ><br>
><br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>