temp file in root?
by John Mazzitelli
Can we get rid of this?
temp-testng-customsuite.xml
Its in the top root directory - seems completely out of place. Looks
like some temporary file that mistakenly got checked in. If this isn't
temporary, it needs to move to a more appropriate place, probably in
some maven test directory.
14 years, 4 months
what is test-utils dependency?
by John Mazzitelli
I don't know what this is - can someone explain what this is for? Its a
dependency in the enterprise/server/jar pom.xml and it looks "odd". If
its a "test-util" why is it not in <scope>test</scope>?
<dependency>
<groupId>${groupId}</groupId>
<artifactId>test-utils</artifactId>
<version>${version}</version>
</dependency>
14 years, 4 months
RFC: Next release number
by Bryan Kearney
Per mazz's comments..
Any comments / issue with the next build being
3.0.0.1
3.0.0 Build 1?
We can drop the B notation, and add a GA when we need to. This should
alleviate any isues with Jopr / RHQ numbering conflicts.
-- bk
14 years, 4 months
Script and Script2 names
by Bryan Kearney
Any chance of making those friendlier names as they move from
experimental to "standard"?
-- bk
14 years, 4 months
testing server plugins across HA cluster
by John Mazzitelli
Mainly for the QA guys...
Up until recently, I've been developing and testing the server side
plugins on a single-node RHQ Server environment.
Yesterday I commited to master my first attempt to get multi-node RHQ
Server environments to work.
Here's what we need to test:
0) First, install N RHQ Servers, where N > 1. This is what we call the
RHQ Server "cloud". Its our HA environment where more than one RHQ
Server exists.
1) Install a new server plugin (you can use the sample server plugins to
test this) on a single RHQ Server. Confirm that within a certain time
limit (see rhq-server.properties "rhq.server.plugin-scan-period-ms" for
the actual amount of time), that plugin gets "magically" pushed/deployed
to all other servers in the "cloud". This means that all RHQ Servers get
the plugin stored in their
jbossas/server/default/deploy/rhq.ear/rhq-serverplugins directory and
the plugin is loaded into the master plugin container (you'll see
messages in the server logs when this happens).
2) Disable an enabled plugin via the Plugins GUI page. Confirm that
within a certain time limit (rhq.server.plugin-scan-period-ms) all
servers disable that plugin (you'll see messages in the logs when this
happens).
3) Similar to 2), only this time ENABLE a disabled plugin.
4) Finally, undeploy a plugin and see that all servers will eventually
undeploy that plugin, too (again, log messages will tell you when the
individual servers do this)
14 years, 4 months
First Plugin: Discovery
by Bryan Kearney
Writing a plugin for the fist time.. I have a couple of questions:
1) When new software is installed, how does the version information get
updated? Do you have to re-run discovery on regular intervals?
2) It looks like much of the code is using process-scan tags in the xml.
I assume this is a feature to look for running instances which can be
accessed via context.getAutoDiscoveredProcesses()
3) Given that 2 is my assumption, is this a best practice? It seems like
you would want to discover non-running servers as well.
4) What is the best practice with the new Raw config stuff is a server
has more than one config file? Does that matter at all in creating the
classes behind the plugin?
-- bk
14 years, 4 months
Stupid Noob Question: The ApI
by Bryan Kearney
Stupid Noob question.. when we talk about "the" external API... what
classes are we talking about?
-- bk
14 years, 4 months
Developer Release: 1.4.0-B1
by Bryan Kearney
The RHQ team is proud to announce the first developer build of the RHQ
1.4.0 platform. This initial developer release, 1.4.0-B1, provides an
early look at the new features which we are planning for the 1.4.0. This
release contains many of the plugins which had been available as part of
the Jopr project, along with the plugins that were included in previous
RHQ releases.
The message provides details on the release notes, how to download the
release, and how to get help and contribute to the project.
As with any developer build, it is possible for this build to do bad
things, like eat your cats. We would advise you to not use this build to
upgrade existing RHQ or Jopr environments.
Release Notes
=============
The complete release notes can be found at
http://rhq-project.org/display/RHQ/Release+Notes+1.4.0.B01.
New Features in this release include:
* A new Server Side plugin container which allows server side features
to be extended without changing core code. You can learn more about this
feature at http://rhq-project.org/display/RHQ/Server+Plugin+Development.
* Pluggable Alert Senders which allow uses to add their own notification
senders to the RHQ Engine. Learn more about this at
http://rhq-project.org/display/RHQ/Design+-+pluggable+alert+senders.
* Several new Alert senders including IRC, Microblogging, and Mobicents
* Improved plugin generator and Annotations to help automate generation
of plugin descriptors
* New ManualAddFacet for agent plugins that support manual adding of
resources
* New Perspectives subsystem facilitating customization of regions of
the RHQ UI. Learn about the design at
http://rhq-project.org/display/RHQ/Design-Perspectives.
Changes from earlier releases include:
* "Content Source" and "Channel" as content types have been renamed to
"Content Providers" and "Repositories", respectively.
* The SnmpTrapd plugin now uses manual add instead of autodiscovery
Getting the Release
===================
You can access this release in the following ways:
The Tarball binary is available from SourceForge at
http://sourceforge.net/projects/rhq/files/rhq/rhq-1.4.0.beta1/rhq-server-...
Source code is in the in the git repostiory at Fedora Hosted:
http://git.fedorahosted.org/git/rhq/rhq.git?p=rhq/rhq.git;a=shortlog;h=re....
Instructions for building the code can be found at
http://rhq-project.org/display/RHQ/Building+RHQ.
You can pull down the bits via maven from the JBoss repostory at
http://repository.jboss.com/maven2/. Use version 1.4.0.B01 in your pom
files.
Getting Help
============
If you would like to get in touch with the developers, you can find us
at #rhq on freenode or on the mailing lists:
Users List: https://fedorahosted.org/mailman/listinfo/rhq-users
Developers List: https://fedorahosted.org/mailman/listinfo/rhq-devel
Please use the lists above in favor of the RHQ and Jopr lists and forums
on rhq-project.org and jboss.org. The old lists will work, but we will
plan on decomissioning those older lists and forums in the future.
In additon, as mentioned earlier, Bugs can be submitted in Bugzilla at:
https://bugzilla.redhat.com/browse.cgi?product=RHQ%20Project. All
previous JIRAs have been moved over to Bugzilla.
Contributing
============
If you would like to contribute to the RHQ Project, please join Fedora
at https://admin.fedoraproject.org/accounts/user/new> Once you have done
that you can start to submit patches on the dev mailing list.
Thank you!
-- bk
14 years, 4 months