On 2015-09-01 09:08, Thomas Heute wrote:
On 08/31/2015 06:48 PM, Peter Palaga wrote:
> Hi *,
>
> there is a requirement for Agent to support adding JDBC drivers
>
https://issues.jboss.org/browse/HAWKULAR-517
>
> The named Jira does not name any standalone/domain/local/remote related
> limitations for the functionality, hence the functionality should be
> there for all modes.
>
> As already noticed on IRC, WildFly 9's jboss-cli.sh offers the
> possibility to add a module, but it works only for the local machine in
> standalone mode. Remote servers or domain mode are not supported.
>
> So clearly, for now, we can support the standalone local mode using the
> same means as jboss-cli, but how should we proceed further?
So that the agent subsystem can install the driver on the WF server it
is installed on ?
Yes, exactly.
> Should we
> (a) wait for WildFly to implement the missing functionality, or
Is there a JIRA ?
There is this "container" Jira
https://issues.jboss.org/browse/WFCORE-661 that refers to subtasks
https://issues.jboss.org/browse/WFCORE-422 File upload/manipulation
through management API - modules, config files
https://issues.jboss.org/browse/WFCORE-428 cli - command to add/remove
AS modules from non-default module root
> (b) contribute to Wildfly or
Unlikely
> (c) create a minimal Agent to install on remote servers to provide the
> functionality missing in WildFly itself (as proposed by Heiko)?
Personally I am fine if we require the "complete" subsystem to be
installed so that a WF server becomes manageable (ie, no remote install).
Thomas
> Thanks,
>
> Peter
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev