fyi: pull master if you're making changes to coregui
by Jay Shaughnessy
Three significant check-ins went into master today in the coregui module:
- new charting!
- selenium test automation hook removal
- alert condition editing
To avoid conflicts, please pull master if you're going to make changes
to coregui.
Jay
11 years, 1 month
Evolution of hudson plugin
by Jérémie
Hi rhq team,
I want to create an alert if a hudson job has not been built for more
than two days. It seems to me that isn't possible on trait.
What do you think of adding two metrics on the hudson plugin giving
the time elapsed since the last build, and since the last successful
build. lastSuccessfulBuildElapsedTime and lastBuildElapsedTime.
Attached is a patch that seems appropriate for my use case.
Your feedback are welcome. I can create a jira for it.
Regards,
Jeremie.
11 years, 1 month
Alert condition modification
by Jiri Kremser
Hi,
I've finished the work on this RFE (BZ 914631). The changes are in this branch [1]. It allows for modification of an existing alert condition also for the templates and for alerts defined on groups. It doesn't allow to change completely the type of the condition.
It would still be nice to have some dialog popping up when user is leaving this page without saving the alert, as Heiko has suggested. I am not sure if there is any hook for that in GWT, I'll see.
I can present the changes next during week.
[1] http://git.fedorahosted.org/cgit/rhq/rhq.git/log/?h=jkremser/alert-condit...
jk
11 years, 1 month
Format of links in the rest-api with json
by Heiko W.Rupp
Hi,
I've made a change today that changes the format of links from
{ rel:bla, href=http://.... }
to
{ bla : { href : http:// .. }}
This has the benefit, that in javascript you can now say something like
href = $document.links.bla.href;
without the need to first parse the whole map of links.
See also https://bugzilla.redhat.com/show_bug.cgi?id=845244
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, 2 months
Provisioning Plugin API
by Lukas Krejci
Hi,
while waiting on some input for the provisioning subsystem requirements, I
actually went ahead and tried to design a new plugin API that kind of merges
the capabilities of the current bundle and content subsystems, keeping the
functionality I thought might be useful.
I've created a pull request (between 2 branches in my fork of RHQ on github)
where I'd like to start the discussion about the API. The reason I want to do
it on Github is that we can have a discussion directly at the pull request but
more importantly we can put comments inside the diff itself at the concrete
lines of code, making the discussion targeted and focused.
I would love to hear some comments on the design, your initial thoughts, some
pitfalls I managed to fall into that you already avoided in the past, etc. I'm
looking especially at you, Jay and Mazz, because your input so far was
invaluable for me.
Note that this is *only* the plugin API - i.e. it only defines the blueprint
for interactions between the plugin container and the agent plugins. This does
not deal at all with how the bundles/packages/deployable files/however we are
going to call them are stored on the server, nor does it in any way define a
workflow for deployment, reverts, etc. Obviously these things, once we get to
them, will affect this API, too, but I wanted to get some discussion on the
general direction I'm heading in this piece of code.
You can review the pull request here: https://github.com/metlos/RHQ/pull/8
and you can checkout the "feature/provision/plugin-api" branch from the above
repo to get the code yourselves.
Looking forward to your feedback,
Lukas
11 years, 2 months
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, 2 months