Each hawkular-metrics PR is now checked for performance regression
by Filip Brychta
Hello,
Please be aware that second check (first is continuous-integration/travis-ci/pr) on each hawkular-metrics PR now finally does something useful.
Following build (http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/haw-perf-stability-t...) is launched for each PR which will:
1 - build the PR
2 - build hawkular-dist using snapshot artifact from step 1
3 - deploy hawkular-dist
4 - start perf test which will
- generate as high load as the hawkular is able to server. Right now from 300 threads where each thread is using unique tenantId.
- measure average throughput (one request == POST one data point to http://${server.host}:${server.port}/hawkular/metrics/gauges/test/data and wait for response)
- check % diff with previous build
- if the % diff is < -2, it will fail the build. Right now it's still not 100% stable because of shared network, this problem should be fixed soon. Expected instability is now +/- 2 % so anything bigger than 2% should be considered as regression
5 - report status back to the PR
So please from now on pay attention to result of that check and ping me if it fails.
Consider this just as first step, there will be more next week since we have more time now (JON 3.3.3 is out).
It would be nice if anybody could create a PR which would test this (just include some tiny sleep into request processing)
Thanks,
Filip
11 years
faster dev build of hawkular
by Jiri Kremser
Hello there,
there is a PR hanging https://github.com/hawkular/hawkular/pull/342
that will change the way the -Pdev profile works. Currently, it creates the zip and gz archive, but most of us don't use it during the development. The directory is pretty much ok. So it won't be created anymore, if you need the zip/gz with precreated jdoe:password, use -Pdozip.
I am sending this not to break anyones automated workflow. I asked Filip and it seems QE don't depend on it.
Perhaps the dozip profile can go away completely, then.
jk
11 years
dev/inventory-0.3.0.Final integration branch opened
by Lukas Krejci
Hi all,
I've opened the integration branch for the new inventory version now even
though there is not much new yet in inventory that is consumable by remote
clients.
The only breaking change since 0.2.0.Final right now is that inventory paths
now use percent encoding like URIs to escape special characters instead of the
backslash which was used before. This is not even merged to inventory master
yet (only the PR is opened). This was done to make passing the paths to the
REST api easier and to actually re-enable support for resource hierarchies in
inventory REST.
In the pipeline is the adding the REST methods for storing resource
configurations (but not configuration definitions yet) for which a WIP PR is
also open.
Cheers,
Lukas
11 years
basic "deploy an app" should be working in kettle now
by John Mazzitelli
I got the basic use-case "deploy an application" working tonight so I released a new bus and agent with the feature so building hawkular/dist master branch should pull it in. I'll talk to the UI folks Monday morning on what they need to do next. But, in short, look at the DeployApplicationRequest JSON [1] - that's the JSON request. You must stream the application file content (the war or ear or whatever) immediately following the JSON text over the websocket as a single message.
My example .html [2] shows how I was able to stream data over the websocket to submit the request, but I did it by having the client browser load the file in memory first - not something I think we want to do in the product, but, this is how I got it to work:
=====
<html> ... <input type="file" id="file" name="file"/> ... </html>
...
<script>
...
document.getElementById('file').addEventListener('change', handleFileSelect, false);
var fileBinaryContent = null;
function handleFileSelect(evt) {
var theFile = evt.target.files[0];
var reader = new FileReader();
reader.onloadend = function(readEvent) {
if (readEvent.target.readyState == FileReader.DONE) {
fileBinaryContent = new Uint8Array(readEvent.target.result);
}
}
reader.readAsArrayBuffer(theFile);
}
...
// when you are ready to send, do the following
var text = "DeployApplicationRequest={...the json...}";
var binaryblob = new Blob([text, fileBinaryContent], {type: 'application/octet-stream'});
socket.send(binaryblob);
...
=====
That is all.
--John Mazz
[1] https://github.com/hawkular/hawkular-bus/blob/master/hawkular-feed-comm/f...
[2] https://github.com/hawkular/hawkular-bus/blob/master/hawkular-feed-comm/f...
11 years
[metrics] schema changes
by John Sanda
The work for HWKMETRICS-168 was merged into the master branch of the hawkular-metrics repo earlier today. If you work out of master, you will need to recreate your schema(s). Some changes were made to the task_queue and leases tables.
- John
11 years
Who is the maintainer of embedded Cassandra?
by Peter Palaga
Hi *,
I had hard time to figure out who was the best to ask for a review of a
PR that I have sent to embedded Cassandra yesterday.
Is there anybody here who feels to be the maintainer of that code? And
if not, would please somebody with enough expertise with Cassandra
overtook that position?
Thanks,
Peter
11 years
UI Dev upgrade to Typescript 1.5
by mike thompson
Hawkular UI Devs,
If you have not upgraded your dev environments to Typescript 1.5 please do so as we will be incorporating Typescript 1.5 language features into our codebase.
** If you just compile Hawkular in the Hawkular build, you can disregard this message, only if you are doing dev work does this apply (meaning you have the Typescript compiler already installed) **
Doing a compile in your dev environment might not compile if you have not updated your typescript compiler. To verify what version your ts compiler is type:
➜ hawkular: tsc --version
message TS6029: Version 1.5.3
It should read >= 1.5
If it does not you should upgrade your local environment via:
sudo npm update -g typescript
If you are not doing typescript development, then all of this unnecessary as the maven plugin handles downloading the proper tools for an automated build.
— Mike
11 years
New or noteworthy in hawkular-parent 19
by Peter Palaga
Hi *,
New or noteworthy in hawkular-parent 19 [1]:
* WildFly BoM import removed, the projects will have to import it
themselves where appropriate using
<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>jboss-javaee-7.0-wildfly</artifactId>
<version>${version.org.wildfly}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
* Debug port for tests changed to 8789 to not clash with the server
* License checks:
* Use slashstar style /* rather than JavaDoc style /** in Groovy
files license header
* *.adoc files excluded from license checks
* Checkstyle rule for imports order
* Both Eclipse and IJ settings were tested for compliance with the
rule
* IJ settings were updated today
* Please make sure that your settings are up to date:
https://github.com/hawkular/hawkular-build-tools/tree/master/ide-configs
* IJ users, beware of the issue described by Juca:
> For IntelliJ users out there: while testing this PR, I got into an
> interesting problem, in that IntelliJ seems to "forget" the settings.jar
> that was imported.
>
> If you get checkstyle errors even after using IntelliJ to "Organize
> Imports", you might want to check if you still have the settings.jar
> imported. The easiest way is to create a new class and see if the
> license headers are there. If they are not there, then:
>
> - Import the settings.jar
> - IntelliJ asks you to restart, which you comply
> - Once IntelliJ starts again, close it and start it again (manually)
> - Import the settings.jar again
> - It should be fixed (test by creating a new file/class).
I have sent PRs with an upgrade to parent 18 to Hawkular and Inventory
and I will continue tomorrow.
Best,
Peter
[1] https://github.com/hawkular/hawkular-parent-pom/commits/19
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
11 years
