11:48 a.m.
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?
Should we
(a) wait for WildFly to implement the missing functionality, or
(b) contribute to Wildfly or
(c) create a minimal Agent to install on remote servers to provide the
functionality missing in WildFly itself (as proposed by Heiko)?
Thanks,
Peter
2:08 a.m.
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 ?
Should we
(a) wait for WildFly to implement the missing functionality, or
Is there a JIRA ?
(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
2:32 a.m.
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
6:18 a.m.
>> 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.
Do we need to make that distinction? In other words, is this only going to be able to
deploy the driver on the WF server the agent is installed in?
The agent can manage/monitor a remote WF server (by "remote" I mean one where
the agent is not co-located/installed in) - this could even be one WF server that is
running on the SAME MACHINE as the agent WF server (even if its a different WF Server).
So I just want to be clear the limitations this will have. Will the agent:
1) only be able to install JDBC drivers on the WF server the agent is installed in?
or
2) only be able to install JDBC drivers on WF servers running on the same machine as the
the agent?
or
3) Any remote or local WF Server?
I think you are saying this will only support 1). I just wanted to make sure that is the
case.
2:21 p.m.
Hi John, inline...
On 2015-09-01 13:18, John Mazzitelli wrote:
>>> 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.
Do we need to make that distinction? In other words, is this only going to be able to
deploy the driver on the WF server the agent is installed in?
The agent can manage/monitor a remote WF server (by "remote" I mean one where
the agent is not co-located/installed in) - this could even be one WF server that is
running on the SAME MACHINE as the agent WF server (even if its a different WF Server).
So I just want to be clear the limitations this will have. Will the agent:
1) only be able to install JDBC drivers on the WF server the agent is installed in?
Yes, this is the option I work on.
or
2) only be able to install JDBC drivers on WF servers running on the same machine as the
the agent?
I never considered this variant. Do we have means in the agent to know
that the non-hosting AS is on the same machine as the AS hosting the agent?
or
3) Any remote or local WF Server?
Out of the scope for now.
-- P
I think you are saying this will only support 1). I just wanted to
make sure that is the case.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3403
days inactive
3405
days old
4 comments
3 participants
participants (3)
-
John Mazzitelli -
Peter Palaga -
Thomas Heute