Relationship between Accounts and KeyCloak
by Gary Brown
Hi
Just curious whether there have been discussions with the KeyCloak project on the boundaries with Hawkular Accounts?
Its just it seems like concepts such as Organizations and Roles are generic and therefore should really be work contributed to KeyCloak, leaving just the relationship from Orgs/Users to resources as Accounts specific?
Regards
Gary
9 years, 12 months
[GSoC 2015] Hawkular Android Client Project details
by Araz Abishov
Dear Hawkular community,
The purpose of this letter is to briefly introduce myself as candidate for
implementation of "Hawkular Android client" project during this summer.
In first order, I want to apologize for contacting you so late. The reason
was time consuming work on my thesis at university.
My name is Araz Abishov and I am 4th year student pursuing bachelor's
degree in computer science at Azerbaijan State Oil Academy. My main passion
is contemporary technology, in particular development of mobile and web
applications. I have already participated in GSoC 2013 and GSoC 2014
working on mobile data capture application for District Health Information
System. GSoC 2015 is a great chance for me to face new challenges. It would
be pleasure for me to contribute to Hawkular community this summer.
I would like to learn more about main project goals as well as other
specific requirements:
Could you please:
- provide more details on REST API available for mobile apps?
- describe which features you are expecting in Android application?
I would like also to provide more details about me and my working
experience (I have attached my CV in pdf).
Hope to hear from you soon on project details.
Best Regards,
Araz Abishov
10 years
Jira and pull-requests
by Heiko W.Rupp
Hey,
please after merging a pull-request, also mark the jira as resolved.
Thanks
Heiko
10 years
Jira issues
by Heiko W.Rupp
Hey,
when it is obvious that a Jira issue does not need QA (e.g. "mavenize
build"), then directly close it after merging to master and do not put
it "ON QA".
Thanks
10 years
Hawkular-Team Update
by Heiko Rupp
Der folgende Sitzungstermin wurde geändert:
Betreff: Hawkular-Team Update
Organisator: "Heiko Rupp" <hrupp(a)redhat.com>
Ort: pc 204 2160 481
Uhrzeit: 15:30:00 - 16:00:00 GMT +01:00 Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
Wiederkehrend : Jeden Dienstag Kein Enddatum Ab 24. Mrz 2015
Eingeladene Teilnehmer: hawkular-dev(a)lists.jboss.org
*~*~*~*~*~*~*~*~*~*
This is a all-Hawkular team meeting to give updates where we are and so on.
This is *open to the public*.
Location: teleconference Reservationless+ , passcode 204 2160 481
You can find Dial-In telephone numbers here: https://www.intercallonline.com/listNumbersByCode.action?confCode=2042160481
RedHat internal short dial numbers are 16666 and 15555 (and probably others, depends on your location)
10 years
Hawkular-Team Update
by Heiko Rupp
Neue Sitzungsanfrage:
Betreff: Hawkular-Team Update
Organisator: "Heiko Rupp" <hrupp(a)redhat.com>
Ort: pc 204 2160 481
Uhrzeit: Dienstag, 24. März 2015, 15:30:00 - 16:00:00 GMT +01:00 Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
Eingeladene Teilnehmer: hawkular-dev(a)lists.jboss.org
*~*~*~*~*~*~*~*~*~*
This is a all-Hawkular team meeting to give updates where we are and so on.
This is *open to the public*.
Location: teleconference Reservationless+ , passcode 204 2160 481
You can find Dial-In telephone numbers here: https://www.intercallonline.com/listNumbersByCode.action?confCode=2042160481
RedHat internal short dial numbers are 16666 and 15555 (and probably others, depends on your location)
10 years
agent implementation
by John Mazzitelli
Time to start thinking about the agent. As you probably know, the "nest" started out being the "agent" - but it worked out to be something we could use for the server components and it ended up being used for the "kettle" - hosting everything (console, server components, data storage, etc). We can still use the "nest" for agents - that's not a problem. My question is - what do people think about that?
So, what do you think the Hawkular agent should "be"?
I see three options - Feel free to suggest others:
(I mention only one PRO/CON for each, though I'm sure there are many more)
1) It could be our own homegrown Java app (similar to what RHQ did, which means we build out our own agent container).
* PRO: We put in and control everything that goes into it - however big it gets (code size and runtime footprint size) is based on what we explicitly put in it.
* CON: We put in and control everything that goes into it :) It is not trivial to implement classloading isolation and plugin mechanisms.
2) Or it could be built on top of WildFly (either use the "nest" or use WildFly Core)
* PRO: We don't worry about things that WildFly gives us for free (e.g. JBoss Modules for plugin/deployments and classloading isolation; if we want, we can get EE capabilities)
* CON: The runtime footprint might be larger than we want or what customers expect.
3) Or it could be built on top of something else (Vert.x? Something else)?
* PRO: Depending on the technology, might provide us with a smaller runtime footprint than a full WildFly container
* CON: Depending on the technology, might not provide us all the capabilities we want
What are your ideas for what you think the "agent" should look like?
--John Mazz
10 years
ADMIN: set reply-to list?
by Heiko W.Rupp
Hey,
currently the reply-to for this list is not set,
to hitting reply makes the reply only go to the
author of an article and hitting reply all will also
put the author in cc.
Are there objections to add a reply-to header that
points to the list, so that simple replies go to this
list?
Thanks
Heiko
10 years
