(no subject)
by Anuj Garg
hey.. Pull request for android client
https://github.com/hawkular/hawkular-android-client/pull/49
It is logging in successfully with master. but as there is issue in trigger
and all at master at present, they are not coming. but when replaced key
and secret and using with alpha 9 everything worked (by username password
coz key/secret were creating problem there ). Implies code is working
perfectly fine :)
8 years, 9 months
Receive data via bus from outside?
by Heiko W.Rupp
Hey,
while I am pretty sure we said we do not want to receive data
(Metrics, Inventory) from outside Hawkular via Bus, I wanted to
make sure anyway.
Do we make sure that the bus is only visible internally then
(e.g. only binding to management interface)?
8 years, 10 months
agent PR needs peer-review
by John Mazzitelli
Here's another agent PR that needs peer-review and merging.
PR: https://github.com/hawkular/hawkular-agent/pull/150
JIRA: https://issues.jboss.org/browse/HWKAGENT-57
The issue here is that when the agent is told to shutdown by the WildFly container controller, the agent should set availability metrics to DOWN for local resources. So in the shutdown code of the agent service, it now gets a list of all configured avail metrics that need to be set to DOWN and sets them, making sure WF doesn't completely shutdown until those metrics are set (needed to do some changes around async storage to the metrics REST API - had to add a wait period just so the stop() method doesn't return until after the metrics are set - otherwise, WF will shutdown potentially before all the REST calls are made).
Anyway, this doesn't fully solve the issue because there are cases when the agent's WF container dies abruptly (i.e. crashes). That's next on my todo - see https://issues.jboss.org/browse/HAWKULAR-407
8 years, 10 months
Use of jira trackers
by Heiko W.Rupp
Someone asked:
> I thought HAWKULAR project's metrics component means Hawkular-UI
> metrics component. Why is there a metrics component under
> Hawkular-JIRA? We have "HWKMETRICS" which should be used instead.
> Confusing.
HAWKULAR is the over all jira project for Hawkular.
Stuff that is needed for the overall project is recorded there.
For the individual subcomponents of Hawkular, we have
a jira-component and sometimes also a separate HWK*
tracker. Projects can use that to track their individual issues
or also breakdown of tasks that were originally recorded
in HAWKULAR as a "top level" item.
Users that download Hawkular and find an issue will file
it in HAWKULAR and not chase the individual HWK* jira -
most often because they do not know about it.
Also release notes for Hakular are created from HAWKULAR
jira (only)
UI-specific work is recorded in the UI component of HAWKULAR
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey,
Charlie Peters
8 years, 10 months
hawkular bower build failure
by John Mazzitelli
Red Alert! Hawkular fails to build (at least for me):
...
[ERROR] bower es5-dom-shim#* invalid-meta es5-dom-shim is missing "main" entry in bower.json
[ERROR] bower es5-dom-shim#* invalid-meta es5-dom-shim is missing "ignore" entry in bower.json
[INFO] bower es5-dom-shim#* resolved git://github.com/termi/ES5-DOM-SHIM.git#e25207e9ed
[INFO]
[INFO] Please note that,
[INFO] hawtio-oauth#2.0.38 depends on keycloak#~1.1.0 which resolved to keycloak#1.1.0
[INFO] hawkular-console depends on keycloak#1.3.1 which resolved to keycloak#1.3.1
[INFO] Resort to using keycloak#1.3.1 which resolved to keycloak#1.3.1
[INFO] Code incompatibilities may occur.
[INFO]
[ERROR] bower angular resolution Unsuitable resolution declared for angular: ~1.4.9
[ERROR] bower ECONFLICT Unable to find suitable version for angular
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Hawkular ........................................... SUCCESS [ 18.163 s]
[INFO] Hawkular: Admin console ............................ FAILURE [03:52 min]
[INFO] Hawkular: WildFly Agent Download WAR ............... SKIPPED
[INFO] Hawkular: Pinger ................................... SKIPPED
[INFO] Hawkular: Availability Creator ..................... SKIPPED
[INFO] Hawkular: API parent pom ........................... SKIPPED
[INFO] Hawkular: RX extensions layer ...................... SKIPPED
[INFO] Hawkular: REST API Web Application ................. SKIPPED
[INFO] Hawkular Feature Pack .............................. SKIPPED
[INFO] Hawkular: Distribution ............................. SKIPPED
[INFO] Hawkular: End-To-End integration tests ............. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:11 min
[INFO] Finished at: 2016-02-05T10:22:53-05:00
[INFO] Final Memory: 44M/468M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.26:bower (bower install) on project hawkular-console: Failed to run task: 'bower install' failed. (error code 1) -> [Help 1]
8 years, 10 months
Downsizing the Nest deployments
by Peter Palaga
Hi *,
there is a couple of jars our war deployments could load from WF modules
that are available either on a stock WF/EAP installation (apache
commons.*, guava 18, ...) or that are our own (c* driver, guava 16).
Technically, it would mean to mark those dependencies as provided and
declare them as dependencies in jboss-deployment-structure.xml.
The motivation is twofold:
(1) Make clear that (if applicable) it is the container teams who is
responsible for sustaining and productization of the jars.
(2) Make the wars smaller - faster to build, faster to release/upload,
faster to download, faster to deploy.
Can anybody see a reason why we should not follow this strategy?
Thanks,
Peter
8 years, 10 months
RfD: Installer
by Heiko W.Rupp
Hey,
while the All In One zip works well for demoing, using Hawkular in a
more serious scenario requires a lot of options and settings
* External C*: $CASSANDRA_NODES and -Dhawkular.backend=remote
* Binding to non-localhost: -b a.b.c.d and
-Dkeycloak.server.url=http://a.b.c.d:8080/auth
* Adding jdoe to a dist build:
-Dkeycloak.import=./standalone/configuration/hawkular-realm-for-dev.json
* Using an external RDBMS for keycloack users: "before the server first
boots, the `KeycloakDS` on `standalone.xml` should be changed to point
to an external database." (this applies when using the embedded KC and
not a separate standalone one)
* If not using jdoe above: setting user/password for the internal agent
after a user was created
* Dorking around with standalone.xml to chose up a mail server
* Setting other java opts
all the above involve a huge amount of manual steps and configuration
changes.
I think it is thus time to introduce some sort of installer or config
script that is able to make the changes. I think there is meanwhile even
a cli mode that can apply the changes (to standalone.xml) on a
non-running server. Some options could be set in env variables or
directly applied to the standalone.xml.
If we still need to supply env-variables we may potentially also create
a start script from the installer, which sets the variabls and then
calls standalone.sh
8 years, 10 months
