March 2015 - hawkular-dev - Jboss List Archives

by Brett Meyer

Excited to announce Artificer 1.0.0.Alpha1! Details: https://developer.jboss.org/en/artificer/blog/2015/03/11/artificer-100alp...

11 years

6
6
0 / 0

Default user, or alternative realm file?

by Juraci Paixão Kröhling

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, Alexandre (and others) asked about the possibility of adding a default user on Keycloak for the Hawkular realm. While adding a default user with the requirement of changing the password on the first login is a possibility, I'd rather have an alternative realm file to import during first boot. This means: a dev (or user) have to actively copy this JSON file into standalone/configuration in order to have a default user. The idea is that we wouldn't ship with a default username/password on the main distribution. Having a default username is usually not recommended from the security perspective, as it's half of the information required to login with super power rights (and you would be surprised to know how many admins set their passwords to "admin"). Given these two alternatives, which one would you prefer? Voting is open and I'll take the results on Monday 9am CET (08:00 UTC). [ ] Default user on the main realm JSON file that will ship with Kettle [ ] Alternate JSON realm file with a default user, which can be copied over the default JSON realm file. - - Juca. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVAGy2AAoJECKM1e+fkPrXIkMH/jyS4BIJCpcIntF12G6+Ofai IaxuopgbS6rDqNnemABBQhb14Kd1mJelAz8/xnyFQsjHtzV3BZr4cqJqgC4vMpkX cuCQWqmz5v3nTFsoxYjFXNMK2FR/K6srG/N95eg0/vO+pXVOmC5Fy8FSE1h2cUmh 9yL1Zd8hR28xV8JDQgnRulmAsE4INY3QhpzaBpVnJczZKSsM54Hq4mDEQx5Wmr+i k1PE9sdcysoWXmjqHSpR4cG4HNHKZXkbaBWubpaFzrI40ZkGiYVg5Vg//LqPtvQe G16+/HNo4cgUw0HBbiVUvcXTRE3k2y/UFWVw9laQxZrAadl9Byr/7B4PnRcZxEw= =G8QS -----END PGP SIGNATURE-----

11 years

7
14
0 / 0

Onward to Alpha2 - not Alpha1

by Heiko W.Rupp

Hey, we are so we will not release an explicit Alpha1, but directly work on the Alpha2 requirements of the MVP. On top of that we also need to work on the Openshift integration. Heiko

11 years

1
0
0 / 0

Titan's future at Datastax and Hawkular Inventory

by Lukas Krejci

Hi all, today, Jirka and me attended the webinar organized by Datastax where they outlined their plans for Titan - our candidate graph database to use for inventory storage. The outcome is IMHO both good and bad. Datastax is committed to push Titan to 1.0 and port it to Tinkerpop3 API (which is due "imminently" and the port is well under way - https://github.com/thinkaurelius/titan/tree/titan09). They are also committed to be further involved in the design of the Tinkerpop3 API (i.e. the equivalent of JDBC for graph databases). Once Titan 1.0 is out they plan to "let the community take over" and don't plan any further work on it. After that, they're shifting focus on DSE Graph - a proprietary graph database that will be integrated into DSE - their proprietary offering expanding on Cassandra's capabilities. This is not going to be open source but will support the Tinkerpop3 API as its primary interface. So there are 2 outcomes for us from this IMHO. First, if we are to stick with a graph database as the storage platform (which I think makes sense), we should adopt Tinkerpop. We currently support Tinkerpop2 which is radically different from Tinkerpop3 but the contact surface between us and their API is quite small (at least at the moment) and in an area that actually didn't change that much (the Gremlin graph traversal DSL). Second, given the unique advantage of the shared storage for metrics and inventory, we should stick with Titan (perf benchmarks still pending) for now and see how it will evolve post 1.0. If it dies slowly and we hit issues that we would not be able to solve ourselves, we can choose another database implementing Tinkerpop3. At the moment the only other choice is Neo4j, but given the involvement of many graphdb companies in the design of the Tinkerpop3 API (http://www.tinkerpop.com/docs/3.0.0.M7/#tinkerpop-contributors), I am quite confident that there are going to be more choices in due time. As a side note, our inventory API is not tied to the Tinkerpop API in any way. It's just that the graph API naturally fits for implementing the inventory API and in fact, the impl is quite compact. But should we, due to some cataclysmic findings, choose to abandon tinkerpop API altogether, then only a fraction of the inventory codebase would be affected - the REST API, UI and all the other future integration code would be unaffected by that departure. WDYT? Lukas

11 years

2
2
0 / 0

Re: [Hawkular-dev] agent implementation

by John Mazzitelli

> I'm sorry for asking this, but I'm not familiar with the details of > how the RHQ agent works. > > What is the scope of the agent? Will it gather only data about the > environment, like, memory consumption, span of worker threads, CPU > consumption, GC-time, ...? Or business metrics as well, like "requests > per second", "number of exceptions in the last X minutes", "average > time spent on database", and so on? > > Also, is the same agent also responsible for capturing non-JVM related > data, like, disk space utilization, network traffic, ...? Ahhh!! You are one step ahead of me! This was going to be the SECOND question I was going to ask I haven't sent that email yet. But I will copy-n-paste your questions since it asks some of the things I was going to ask :-)

11 years

1
0
0 / 0

GSOC2015 - Hawkular - Android client

by Samat Gayazov

Hello! My name is Samat Gayazov, and I’m interested in contributing towards the project Hawkular - Android client. I am a student of Software Engineering at HSE Moscow, I have strong background in Java, C++, Python, and C#. Previously I developed some apps for mobile Windows platform and for Android. I know a lot about Android’s Material Design, and here is my apps: https://play.google.com/store/apps/developer?id=dieserSamat http://apps.microsoft.com/windows/app/travelassist/83f6db61-b655-4986-be5... <http://www.google.com/url?q=http%3A%2F%2Fapps.microsoft.com%2Fwindows%2Fa...> I have also finished course of iOS Swift Programming and course about building UIs, which, I think, will help me to develop better mobile apps. So, I’m really looking forward to participating in Google Summer of Code and contributing to Hawkular - Android client.

11 years

2
1
0 / 0

Interested in android development

by Raghu Ram

Hi all, I am extremely interested in Android development. And I came across the idea Hawkular in you ideas page. I am excited by it. I am looking forward to contribute to JBoss during this summer during GSoC. I wanted to work on android client. Is there any repository already existing or should I start a new one based on studying desktop version? I could not find any android app here -https://github.com/hawkular.

11 years

2
1
0 / 0

Hawkular Metrics - PR155 Merged

by Stefan Negrea

Hello Everybody, I've merged PR155 [1] into master of Hawkular Metrics. The code is in fairly good shape but will need adjustments since the refactoring is far from done. I wanted to merge today because the branch was diverging too much from master and was impeding other PRs from being completed and merged. My focus was to simplify the public API implementation with two main goals: faster implementation of additional features and enable additional implementation in the future (eg. Undertow or Websocket). I've changed very little in the mechanics for storing and retrieving data from Cassandra. Here are few principles that I tried to follow: 1) Simplify everything as much as possible 2) No more intermediary mapper classes in the jaxrs module; expose meaningful fields of domain models via the public API 3) No complicated and individual callbacks in the jaxrs module, prefer specialized data transforms with generic callbacks 4) The public API implementation should be as uniform and monotone as possible 5) Keep all domain code away from jaxrs module and vice-versa 6) Avoid circular dependencies between models where the children have a reference to the parent Here is a list of things to cover in the following weeks: 1) Simplify core-api and core-impl composition; right now there is no clear differentiator between the two 2) The domain classes are not settled in yet, the composition needs more tweaks to get a clean domain 3) Add more integration tests, the set in there right now is really minimal 4) Add more swagger documentation 5) Expose schema for each end-point via */schema URL Next steps for Hawkular integration: 1) Get the current API stable (probably another week) 2) Work with projects that interact and/or consume Hawkular Metrics to adjust the integration. All feedback is more than welcomed :) [1] https://github.com/hawkular/hawkular-metrics/pull/155 Thank you, Stefan Negrea Software Engineer

11 years

1
0
0 / 0

Heads up: registration/login for console is coming soon

by Juraci Paixão Kröhling

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, I've just sent a PR for console that enables the Keycloak integration. What does this mean for you, as a developer? - - When opening the console, you'll be presented with the login page provided by Keycloak. If it's the first time you are opening after building the kettle, you'll need to register an account. After that, you'll be redirected back to the console. On the subsequent runs, you'll just need to login again, as long as the data directory is preserved (ie: until you rebuild kettle) - - Running your UI plugin via ui-components with "connect-COMPONENT" is *not* affected. - - Your WAR deployment is not protected, meaning, you can still call your backend without passing any credentials. Note that the UI integration is temporary, as hawt.io will provide a better Keycloak integration "natively". - - Juca. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU/wpKAAoJECKM1e+fkPrXKkUH/RDGtIIfTqxyVBxNhXfQcnzr jpA2nRLTp56eMZYP43d2Om13lbDYtAguiUPP2k5Y3huDAYQLQLAVHbF9hRenaiie actkuiEZ60rxZ+qYUMt/EjBpPdFupHnRra3Uc/G5LMAWOh1eSEjmrBM4bShSgj3M CSmtrTcXuK+QdFJ7OkzA4BoX+uK5z/EX2iNsYRITAI1281xG1zK3ndAt6HQwKCvs DDJauCw/DVdOiucJzXrfzFx4CwecjyK9lJUNRvCkyO4qtukH+i/LP09nnt+RC2Di +fyeDhEzQrLIQTpk8vpbCe4aRKZvLP25AVCgVnh0017aUMgtMO2neOleM/4weWg= =38rr -----END PGP SIGNATURE-----

11 years

1
0
0 / 0

Clustering and Scalability

by Matt Wringe

Hey, I am trying to figure out how clustering and scalability works in Hawkular/Hawkular metrics. Do we have any documentation on this? Thanks, Matt Wringe

11 years

6
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev March 2015