Need advice about agent plugin design
by Steven North
I am trying to design an RHQ/JON agent plugin to manage a software
resource with the following characteristics:
- there is the software itself (the installation);
- there are a variable number of "bundles" of configuration information
about 250KB in size each which need to be read from and written to the
agent; and
- there are "log" files which can 10-50MB in size each which need to be
read from the agent.
I think I am pretty clear on how to handle the software itself--just
like any number of other agents.
I am not sure how to handle the configuration bundles and the large log
files.
We might want to have the RHQ/JON server manage different versions of
these configuration files and distribute them to multiple remote agents.
Is there some existing domain object that would handle the read/write
aspect of the configuration bundles (zip files)? Could the "package"
concept be used for these? Would we need to create a new domain object
on the server side for these bundles? If so, is there an example of
this kind of thing?
For the log files, I see some mention of the SupportFacet. Would this
be appropriate for retrieving large log files? Is there an example of this?
We expect to access the configuration bundles and the log files using
remote client operations because we have a separate GUI tool to
build/edit the configuration bundles and to correlate and analyze the
log files. Is there an example of using a remote client to pull files
from and push files to remote agents?
Thanks in advance for any advice you can give or examples you can point to.
Steve
10 years, 1 month
MeasurementUnits (EPOCH_MILLISECONDS, EPOCH_SECONDS)
by Jiri Kremser
Hi,
in plugin descriptor, there can be a metric definition with unit type "epoch_milliseconds" or "epoch_seconds" (rhq-configuration.xsd allows it). What kind of metric should could be represented by epoch_milliseconds? Shouldn't the exact time moments (what values epoch_milliseconds represent) be addressed rather by traits?
I am asking because the values of this type are not formatted (https://bugzilla.redhat.com/show_bug.cgi?id=857144).
I think these two unit types should be removed from MeasurementUnits and xml schema, however there might be some plugins out there using it, so what about deprecation? Are there any edge cases, when these unit types do make sense?
JK
10 years, 1 month
GitHub migration again -- The Plan
by Heiko W.Rupp
Hi,
I've updated the wiki page including "The Plan".
I would like to finish this Plan within the coming 7 days so that
we will be able to switch over soon.
https://docs.jboss.org/author/display/RHQ/GitHub+migration#GitHubmigratio...
Please comment. If you think it is ok, also say so please.
Heiko
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera
11 years, 1 month
bundle / content api redesign
by John Mazzitelli
(This is more for Lukas, but it seems appropriate to discuss over the rhq-devel ML)
Lukas,
Jay and I went through the Bundles vs. Content design page,
https://docs.jboss.org/author/display/RHQ/Bundles+vs.+Content+-+On+Its+Head
In general the ideas sound good.
However, there are two things I'm questioning:
1) this is a major re-design/re-implementation - I'm not sure if we need to be concerned with backward compatibility with the older content API (i.e. I think we should release this in RHQ 5 timeframe, the new major release should indicate it contains some backward incompatible changes with RHQ 4).
2) (this is the bigger concern), it seems like you deferred to maintaining the Content/Package API and deprecated the Bundle API. In my opinion, we should do this in reverse. We should maintain the Bundle API (merging in the Content/Package API where applicable) and deprecate the Content/Package API.
Bundles has been a successful feature - more people are using it and like it (and they are using it successfully for things we didn't anticipate) compared to the Content/Package API (few people use it, and fewer like it :-)
The Content/Package classes are what needs to be deprecated, not the Bundle classes. I would recommend that where you say things like:
Bundle
@Deprecated NON_ENTITY computed from Package
...
BundleVersion
@Deprecated NON_ENTITY computed from PackageVersion
should instead be flipped like:
Package
@Deprecated NON_ENTITY computed from Bundle
...
PackageVersion
@Deprecated NON_ENTITY computed from BundleVersion
and things like:
PackageVersionDeployment NEW CLASS
exact copy of BundleDeployment, which become @Deprecated NON_ENTITY
...
PackageDestination NEW CLASS
copy of BundleDestination, which becomes @Deprecated NON_ENTITY
should instead just use the Bundle classes (BundleDeployment, BundleDestination) and just add data fields to the entities as necessary.
We can discuss further as to why Content/Package API is being retained and Bundle API is being deprecated, but those are my immediately thoughts.
11 years, 1 month
AS is killed if the agent is killed (provided it was started/restarted by the agent)
by Jiri Kremser
Hi,
wrt https://bugzilla.redhat.com/show_bug.cgi?id=909341
I suggest 2 possible fixes.
1) To provide some intermediate simple script, for instance rhq-background-launcher.sh:
#!/bin/sh
$@&
and then calling the launch script with ./rhq-background-launcher.sh ${path_to_standalone.sh}
I was trying it and it solves the problem (trying it only in terminal, but it should work also for the case agent has executed the script).
2) Search for the "trap" commands in the launch script (they are the culprit) and comment them out before the execution, then uncomment them out (or create a temp. copy just for 1 usage).
I think the fix should be hidden to the end user. If you have any other suggestions please respond to this email.
JK
11 years, 1 month
Charting Meeting
by mike thompson
Hi All,
For those that we unable to attend the charting meeting on 2/25:
http://youtu.be/ordiOu94KZk
Major topics include:
Pulling availability out of the main charts and placing into a chart of its own so as not to confuse the two concepts
Discussion of using Dual slider control for selecting time ranges (and issues surrounding it's implementation)
11 years, 1 month
JBoss Modules
by John Sanda
David Lloyd spent some time over the past couple days helping me debug a problem with loading a native library in our installer module. As it turns out, I do not think the problem had anything to do with the library being JNI code. It had to do with how the 3rd party library was trying to load the code which simply won't work in JBoss modules. The documentation[1] is a bit sparse but if you are interesting check out presentation that gives a detailed overview of modules.
[1] https://docs.jboss.org/author/display/MODULES/Home
[2] http://vimeo.com/32211344
- John
11 years, 1 month