December 2015 - hawkular-dev - Jboss List Archives

is it time for a bom? or for version definitions in parent pom?

by John Mazzitelli

I just released the wildfly agent (0.13.7.Final) and I just realized I may not have moved things up to the latest releases of its dependencies. It would be really nice now if we had something (even if its just versions in the parent pom) that defines the latest releases that components should be using because right now, how many of our pom.xml files have things like this: <version.org.hawkular.accounts>1.1.1.Final</version.org.hawkular.accounts> <version.org.hawkular.bus>0.7.3.Final</version.org.hawkular.bus> <version.org.hawkular.cmdgw>0.10.4.Final</version.org.hawkular.cmdgw> <version.org.hawkular.commons>0.2.3.Final</version.org.hawkular.commons> <version.org.hawkular.inventory>0.9.0.Final</version.org.hawkular.inventory> <version.org.hawkular.metrics>0.10.0.Final</version.org.hawkular.metrics> It would be nice if we aren't required to set these (but we could override them, right? if we want to try out a different version than what the parent pom defines). This would make releasing easier. We just comment out all the <version...> entries in all our pom.xml files (if they are there at all), thus falling back to what the parent-pom has defined. Or maybe we build a bom?? I dunno - all I know is, there is going to come a time when something breaks because "uh-oh, this component built on version x.y.z of metrics, but THIS component built on version a.b.c of metrics".

8 years, 5 months

6
15
0 / 0

autoVersionSubmodules = true

by Juraci Paixão Kröhling

Team, Is anyone against setting the property autoVersionSubmodules to true in the parent? This property instructs maven to set the same version of "parent" (your parent, not Hawkular parent) to all sub modules, so, during release, there's only one question about "what's the version to be released?" and "what's the next development version", no matter how many sub modules you have. It seems that some of us already have it either on the pom.xml for the project (Inventory), while others use the property via CLI (-DautoVersionSubmodules=true). So, if nobody is against it, I'll send a PR by Friday to our parent setting this to true. - Juca.

8 years, 5 months

3
2
0 / 0

agent inventory scan

by John Mazzitelli

I think I remember why I made the agent periodic inventory scan one hour :) Right now, every time the agent does a scan, it takes the newly discovered inventory and completely overwrites the old inventory with the new. It's the same scan the agent does at startup. This means (in the current implementation) if we discover 200 resources, we send all 200 to inventory (even if nothing changed!). Even though we try to use the inventory bulk/ REST API, we still send multiple requests (we end up splitting up into multiple bulk/ requests - might send 5 resources one time, 2 another, 10 another... its the way the current implementation works) and this means it takes a long time to finish. I haven't looked at the numbers recently, but it wouldn't surprise me if it takes longer than 10 minutes for the inventory bulk/ requests to finish. So changing the scan to happen every 10 minutes might mean the agent will continuously be sending bulk/ requests. The second problem is that when resources DO change, and the agent puts the already existing-but-changed resources in its inventory, when it sends those resources to hawkular-inventory via bulk/ those resources aren't updated. Inventory will see the resources already exist, and just return a 409 and not change anything. Lukas said he is going to change that behavior (such that when you send a resource to inventory it will do a create-or-update for the caller, rather than the caller do a double round trip (send a create, receive a 409, send an update, receive a 201). I don't know when that will be in place (Lukas?) but I don't think it works like that now. So what am I saying? Doing a periodic scan will really only benefit you if a NEW resource was added to the WF hierarchy. If one was updated (say, a resource configuration property value changed) the UI won't see that change because it never gets updated into inventory. I'm working on trying to figure out how to change the implementation to fix these problems. So right now, think we should keep the scan interval at 1 hour, unless we are doing a demo that needs to find new resources quickly. You can change that setting in "autoDiscoveryScanPeriodSecs" attribute in the agent's <subsystem> element in standalone.xml. Setting it to 0 disables auto-scans.

8 years, 5 months

1
0
0 / 0

Hawkular build and -Dsrcdeps.forwardProperties

by Jay Shaughnessy

For anyone trying to build Hawkular and running into checkstyle issues despite adding -Dcheckstyle.skip to the mvn command line, you may need to add this as well to make sure it makes it to the recursive builds... > mvn blahblah '-Dsrcdeps.forwardProperties=srcdeps.*,revapi.skip -Dcheckstyle.skip' p.s. the revapi.skip is not relevant to checkstyle but if you happen to hit a revapi issue it may help you out.

8 years, 5 months

1
0
0 / 0

Aggregated Hawkular REST api

by Jiri Kremser

Good news everyone, I was finally able to open the pull request [1] with first shot of the new rest api module for Hawkular. It's goal is to simplify the overall api, in which each component/microservice has very fine-grained api. Currently it can't do much. All it does is manipulation with URls, but if you look into our current UI code here: http://git.io/v0I9p the addUrl function takes 248 LoC. It's creating a resource, computing md5 hash, creating 2 metrics, creating bunch of triggers with dampenings and conditions. Quite a lot. The drawback with this approach, where UI layer works as an integration layer, was visible during the android client creation. Artur had no idea why he needs to mimic all the logic that was already there in JavaScript. Module uses the Hystrix library, because it seems to be a great fit for api aggregation. It's heavily rx-java based and it supports the Circuit Breaker pattern that can help if the components are under heavy load. Similarly, like rx-java it takes quite a while to wrap your head around the concepts of reactive streams, though. Hopefully, it's not an overkill. Perhaps we can even closer integrate with their metric features [2]. [1]: https://github.com/hawkular/hawkular/pull/704 [2]: https://github.com/Netflix/Hystrix/wiki/Metrics-and-Monitoring jk

8 years, 5 months

1
0
0 / 0

Monitoring Systems Article

by mike thompson

I thought this was an interesting article, especially around syntactic monitoring systems: http://container-solutions.com/monitoring-performance-microservice-archit... <http://container-solutions.com/monitoring-performance-microservice-archit...>

8 years, 5 months

3
3
0 / 0

Hawkular Alpha 8 still on WF 9 !

by Heiko W.Rupp

Hey, as this may be unclear: We will do the Hawkular 1 alpha 8 release on WF 9 (as before) and only move to WF 10 after the release - no matter if WF 10 will be released until then. Heiko

8 years, 5 months

1
0
0 / 0

agent can now periodically perform discovery scans

by John Mazzitelli

FYI. The Hawkular WildFly Agent can now be configured to perform automatic discovery scans periodically. By default, the agent will perform auto-discovery every hour. You can make this more frequent or less frequent by adding the "autoDiscoveryScanPeriodSecs" to the agent's top level <subsystem> element in standalone.xml. It is specified in seconds as the name implies (again, default is 3600 == 1 hour). If you set this value to 0, auto-discovery will be disabled and the agent will act just like it acts now (performs an initial scan at startup to get the inventory, but that's it). That is all.

8 years, 5 months

1
0
0 / 0

Cancelled: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1

by Michael Foley

A single instance of the following meeting has been cancelled: Subject: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1 Organizer: "Michael Foley" <mfoley(a)redhat.com> Location: Bluejeans http://www.bluejeans.com/mfoley51 Time: Wednesday, December 9, 2015, 3:00:00 PM - 3:30:00 PM GMT -05:00 US/Canada Eastern Required: pruan(a)redhat.com; mmahoney(a)redhat.com; vnguyen(a)redhat.com; snegrea(a)redhat.com; jsanda(a)redhat.com; mwringe(a)redhat.com Optional: jon-qa-list(a)redhat.com; jboss-on-team(a)redhat.com; hawkular-dev(a)lists.jboss.org *~*~*~*~*~*~*~*~*~* Hi, Let's have a discussion and planning session on testing Openshift & Hawkular Integration! Let's use this etherpad to coordinate the discussion -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning 5 Point Plan for Openshift 3.1 GA * Unit tests .... owned by Hawk-Metrics developers * Integration tests ... owned by Hawk-Metrics developers and Hawk-Metrics QE * Performance CI on Hawk-Metrics (this one is actually new and was not discussed on Wednesday , but I now see it makes sense) * Functional Integration tests on Hawk-Metrics latest + Openshift Origin latest * Funtional/UI .... Cucumber/Ruby tests ...owned by Openshift QE * Functional/Rest ... Cucumber/Ruby tests ... owned by Openshift QE * Performance & Scalability .... owned by Openshift QE Regards, Michael Foley QE Supervisor, Middleware BU

8 years, 5 months

1
0
0 / 0

Fwd: [hawkular-ui-services] Slash hell: Preserving the encoded slashes in the resource ids. (#71)

by Heiko W.Rupp

Before we implement this - should we finally go and ban characters that are not valid in URIs in a literal way (see RFC 2396)? reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" | "$" | "," Also: 2.4.3. Excluded US-ASCII Characters control = <US-ASCII coded characters 00-1F and 7F hexadecimal> delims = "<" | ">" | "#" | "%" | <"> unwise = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`" Data corresponding to excluded characters must be escaped in order to be properly represented within a URI. > From: Jirka Kremser <notifications(a)github.com> > To: hawkular/hawkular-ui-services > <hawkular-ui-services(a)noreply.github.com> > Subject: [hawkular-ui-services] Slash hell: Preserving the encoded > slashes in the resource ids. (#71) > Date: Fri, 04 Dec 2015 06:53:17 -0800 > > Currently the interceptor replaces all the encoded slashes to the > simple ones, but we need to have the way to pass the encoded slash in > the resource id. If the resource id is manually encoded with > window.encodeURI() and then angular does it once more for the > 'percent' symbol, it ends up as '%252F' here we turn it back to simple > '%2F' for which the inventory backend is prepared. In short: '/' are > allowed as resource separators: r1/r2/r3 and '%2F' are allowed in the > resource ids: r%2F1/r%2F2 > > @ammendonca could you please check? > You can view, comment on, or merge this pull request online at: > > https://github.com/hawkular/hawkular-ui-services/pull/71 > > -- Commit Summary -- > > * Preserving the encoded slashes in the resource ids. Currently the > interceptor replaces all the encoded slashes to the simple ones, but > we need to have the way to pass the encoded slash in the resource id. > If the resource id is manually encoded with window.encodeURI() and > then angular does it once more for the 'percent' symbol, it ends up as > '%252F' here we turn it back to simple '%2F' for which the inventory > backend is prepared. In short: '/' are allowed as resource separators: > r1/r2/r3 and '%2F' are allowed in the resource ids: r%2F1/r%2F2 > > -- File Changes -- > > M src/rest/hawkRest-inventory-provider.ts (10) > > -- Patch Links -- > > https://github.com/hawkular/hawkular-ui-services/pull/71.patch > https://github.com/hawkular/hawkular-ui-services/pull/71.diff > > --- > Reply to this email directly or view it on GitHub: > https://github.com/hawkular/hawkular-ui-services/pull/71

8 years, 5 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev December 2015