Accounts 1.0.16.Final released
by Juraci Paixão Kröhling
All,
As we have a Hawkular release tomorrow, I just released Accounts
1.0.16.Final. This is pretty much the same as the Accounts we had last
week, plus a couple of minor bug fixes. Unfortunately, Keycloak hasn't
been released yet, so, the offline tokens feature is coming only for the
next release.
It should be safe for consumers of a recent Accounts to use this newer
version. As such, I'm sending PRs for all projects that are consuming
Accounts (to my knowledge):
- Hawkular
- Agent
- Alerts
- BTM
- Command Gateway
- Inventory
- Juca.
8 years, 6 months
agent release
by John Mazzitelli
New releases have been done to get the latest agent ready for kettle.
This PR is to move kettle to the latest agent:
https://github.com/hawkular/hawkular/pull/581
Problem is - UI looks to be broken. The application server page just spins with no data. However, I do see inventory populated with my agent data (resources, types, etc). So I don't know what's wrong. The only thing I see in the browser debug console is the following error that gets logged repeatedly every few seconds (the log messages aren't time stamped, so I don't know how often it is, but it looks like something is polling something).
Error: res.properties is undefined
AppServerListController.prototype.getResourceListForOneFeed/</</<@http://127.0.0.1:8080/dist/hawkular-console.js?v=2015-10-19T21:49:55Z:2475:25
resourceFactory/</Resource[name]/promise<@http://127.0.0.1:8080/libs/angular-resource/angular-resource.js?v=1445291596061:634:18
processQueue@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14745:28
scheduleProcessQueue/<@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:14761:27
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15989:16
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:15800:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:16097:13
done@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10546:36
completeRequest@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10744:7
requestLoaded@http://127.0.0.1:8080/libs/angular/angular.js?v=1445291596061:10685:1
8 years, 6 months
Review High-level Hawkular MS6 Test Plan
by Michael Foley
The following is a new meeting request:
Subject: Review High-level Hawkular MS6 Test Plan
Organizer: "Michael Foley" <mfoley(a)redhat.com>
Location: bluejeans http://www.bluejeans.com/mfoley51
Time: Friday, October 23, 2015, 9:00:00 AM - 9:30:00 AM GMT -05:00 US/Canada Eastern
Required: jon-qa-list(a)redhat.com
Optional: jboss-on-team(a)redhat.com; hawkular-dev(a)lists.jboss.org
*~*~*~*~*~*~*~*~*~*
Hi,
The developer demo for MS6 is scheduled for October 22, so let's today review how we will test and qualify MS6.
I have an etherpad here that we can use a strawman -->> http://pad.engineering.redhat.com/HawkularMS6TestPlanning
Regards,
Michael Foley
QE Supervisor, Middleware QE
8 years, 6 months
agent i-test "failures" - false negatives
by John Mazzitelli
We need to fix those transient errors, I'm seeing this a lot with the agent builds. Seems to fail 50% of the time, pass 50% of the time.
Peter - is there anything we can do to fix the i-tests? Otherwise, I recommend we disable them in travis - false negatives are bad because I am afraid to merge PRs when I see them. But most times, the failures aren't really failures and the code is good. I normally just kick off another build - wait the N minutes it takes for travis to run, see it go green, then merge. (just like what heiko is saying happened to him).
----- Forwarded Message -----
From: "Heiko W. Rupp" <notifications(a)github.com>
To: "hawkular/hawkular-agent" <hawkular-agent(a)noreply.github.com>
Sent: Sunday, October 18, 2015 5:30:00 AM
Subject: Re: [hawkular-agent] HAWKULAR-604 The message field of ExecuteOperationResponse should not… (#87)
@josejulio Thank you for your contribution - the Travis failure seems transient - I've kicked of a 2nd build that passes. I am sure @ppalaga will have a look at your patch on Monday.
8 years, 6 months
Funny compilation issue on Hawkular? Downgrade to JDK 1.8.0_51 for a minute
by Juraci Paixão Kröhling
Team,
We just had a case today about Hawkular failing to build on my machine
after updating to a specific version of the Agent. While *this* specific
issue is going away with a change from Peter, you might still see this
for a while.
So, if you see a build error on Hawkular related to a compilation issue
for
agent/hawkular-dmr-client/src/main/java/org/hawkular/dmr/api/OperationBuilder.java
, you can just:
- switch to Oracle's or OpenJDK's 1.8.0_51
- cd ~/.m2/dependency-sources/agent
- mvn clean install
- build Hawkular (with whatever JDK you want)
The third step will build the required version of Agent inside srcdep's
cache directory, effectively bypassing the issue.
- Juca.
8 years, 6 months
some new agent features
by John Mazzitelli
Just wanted to blast out a message about some new wildfly agent features.
1) Agent now supports secure communications between itself and any of its managed WildFly servers. I documented how to enable security in the management interface of WildFly here:
https://github.com/hawkular/hawkular.github.io/blob/pages/src/main/jbake/...
2) Agent now supports monitoring JMX resources via Jolokia interface.
The agent now can collect JMX metrics and availability data and can inventory JMX resources in the same manner as it can with DMR resources using the Jolokia interface (Jolokia is a very nice REST interface to JMX). Just as we have <metric-dmr>, <avail-dmr>, <resource-type-dmr>, <remote-dmr>, and related DMR settings in the agent subsystem, we now have <metric-jmx>, <avail-jmx>, <resource-type-jmx>, <remote-jmx> settings as well. So the agent can be given metadata that tells it what to do. As with remote WF servers, the agent also supports secure comm to the remote jolokia JMX server.
There are a few things currently on the TODO for the agent:
1) utilize the new inventory "name" attribute - they now have "name" as a first-class setting - I need to see what the agent has to do to use it
2) utilize the inventory's "operation" metadata - I believe operations are now first class concepts in inventory - I need to figure out how to populate it
3) provide a mechanism for the agent to detect runtime changes to inventory. Right now, after the agent does its initial inventory scan, that's it. The inventory is fixed, all resource configuration is fixed, and all we do is collect metrics. The caveat is that if someone deploys a new app or adds a new JDBC driver, we force a new scan. We need a way to detect new resources in inventory (and old resources removed from inventory) and we need a way to detect changes to resource config. This should work for both DMR and JMX inventory items.
4) Need a way to consume wildfly notifications that other subsystems emit and figure out how to send that to a hawkualr events subsystem.
5) Peter is implementing/has implemented the JDBC driver CRUD and datasource CRUD, gonna see how easy it is to implement reload.
I'm sure I'm forgetting something, but .. that's what I remember.
8 years, 6 months
Travis cache pruning
by Peter Palaga
Hi *,
because we had no cache pruning in place, the cached ~/.m2/repository in
hk main became too bing. As a consequence of that, when Travis attempted
to zip the cached folder, the cache archive made the disk full and not
only that the cache could not be uploaded outside of the transient
docker container, also all subsequent tasks (deployment of SNAPSHOTs)
failed.
I could not find a working pruning script quickly enough. To solve the
problem temporarily at least, I deleted the cache manually under
https://travis-ci.org/hawkular/hawkular/caches
Best,
Peter
8 years, 6 months
Hawkular Inventory 0.6.0.Final released
by Lukas Krejci
Hi all,
I'd like to announce that we've just released Hawkular Inventory 0.6.0.Final.
This release doesn't have many new features, in fact it doesn't have any. This
is purely a bugfix release but we decided to bump the minor version anyway
because of the one big improvement we've made. The read queries should now be
way more performant than they used to (up to an order of magnitude).
The release includes:
* improved logging of initialization failures
* adaptation to the new bus API introduced in Hawkular Bus 0.7.x
* more consistency checks on relationships of inventory entities
* streaming serialization should now work (still off by default) giving a
slight speed boost to REST calls
* Many querying optimizations (collapsing of hops into a single index lookup,
more indices on frequently queries properties, reducing the number of
scenarios requiring backtracking in graph queries, filtering on mirrored
immutable properties of vertices on edges) giving up to an order of magnitude
speed up on read REST calls.
* Moved integration tests to the component so that we can properly test all
scenarios conveniently.
* Fixes to support windows paths in configuration.
This release was made possible thanks to the contributions of the following
fine gentlemen:
Jay Shaughnessy
Jirka Kremser
John Mazzitelli
Lukas Krejci
Pavol Loffay
Peter Palaga
Future releases already have some pull requests ready for inclusion - namely:
* introduction of "name" as a first-class property on entities (instead of
being just a free-form unindexed user-defined property),
* move of feeds from environments directly under tenants, making it possible
to easily move feeds between envs and requiring 1 less thing to remember by
feeds (this will break clients but is hopefully worth it given the early stage
of development of everything Hawkular).
Well under way is the development of "metadata packs", aka "global resource
types". A feature that will enable feeds to very quickly check for presence of
a set of resource, metric and operation types with precise properties
(configurations, parameters, units, etc.) by computing their "content hash"
locally and checking with inventory if a pack with such hash exists.
Thanks,
Lukas
8 years, 6 months