[Hawkular-dev] Host agent ?

[Thomas Heute]

Here the first problem I would like to solve is really to start a server
(say a server crashed) from Hawkular.
Second, discover servers that are not yet instrumented and/or started.

I'm looking for options (extending/reusing existing projects is definitely
a +1)

On Tue, Feb 9, 2016 at 3:20 PM, John Mazzitelli <mazz at redhat.com> wrote:

> > I mean WF servers
>
> 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).
>
> 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.
>
> 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.
>
> Just wanted to bring that up.
>
> ----- Original Message -----
> > I mean WF servers
> >
> > On Tue, Feb 9, 2016 at 2:16 PM, John Mazzitelli <mazz at redhat.com> wrote:
> >
> > > When you say "discover servers" and "start servers" - what do you mean
> by
> > > servers? WildFly servers or just machines (bare metal computers, VMs,
> etc)?
> > >
> > > ----- Original Message -----
> > > >
> > > > With embedded agents, we lost few main features:
> > > > - Ability to discover servers that are off or not (yet) instrumented
> > > > - Ability to start servers remotely
> > > > - Ability to report DOWN availability (other than by lack of UP)
> > > >
> > > > Should we reintroduce a small (optional ?) host agent ?
> > > >
> > > > The agent would only fulfill those tasks (+ embedded agent
> installer) and
> > > > redirect all other tasks to the embedded agents.
> > > >
> > > > We can address a limited set of platforms (Linux only) to start
> with, and
> > > > maybe use environment specific features if those exists (Like RHEV-M
> host
> > > > agent if appropriate)
> > > >
> > > > WDYT ?
> > > >
> > > > Thomas
> > > >
> > > > _______________________________________________
> > > > hawkular-dev mailing list
> > > > hawkular-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > > >
> > > _______________________________________________
> > > hawkular-dev mailing list
> > > hawkular-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > >
> > >
> > >
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160209/c9a0f6fb/attachment-0001.html