Should the components depend on the bus ?
by Thomas Heute
When we started the hawkular efforts, I had in mind that the components
would do minimum tasks as a library with REST/Java APIs and do them well.
Inventory would manage resources (user defined (an "application", a
cluster) or architecture defined (an EAP server, a VM, a Kube pod...)),
assign ids...
Metrics would store/aggregate/compact metrics (like it is today)
Alerts would define some alert definition "model" and run an engine to
define when to trigger an alert.
...
Hawkular project would then be a firm/comprehensive solution that are
using all those components, would proxy the APIs, add security there
(instead of in each component),...
But now I start to see that client aspect of the communication bus is
part of those components I think I understand the motivation for that
but not sure that this is what we really need. Am I the only one
thinking that the communication aspect should be left out of the
components ?
For instance in http://docs.hawkularinventory.apiary.io/ for the
DumbFeed, I don't think it's the role of the Metrics to send
notification to the bus, if we need more than collecting metrics then it
is a job for Hawkular IMO (who may proxy the metrics request and send
notification to the bus).
Thomas
9 years, 3 months
Re: [Hawkular-dev] Keycloak integration
by John Sanda
Hi Juca,
For the dev environment, it looks like the keycloak appliance is used. Does it use an embedded h2 database or something similar? Will realms, user, and other auth info be persisted across restarts?
What are the steps for creating realms/users? I am thinking about after I do whatever is necessary to install/start the appliance and after I start the metrics server.
Is there a way to easily disable the authentication/authorization? While it is not critical, I am thinking it might be nice if we could do that in situations where we are debugging test failures for instance.
> On Jan 14, 2015, at 9:00 AM, Juraci Paixão Kröhling <jpkroehling(a)redhat.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have collected some thoughts on this work created an "article" on
> the RHQ.next space.
>
> If there are more details needed/wanted, I can expand it. I didn't
> want to put all the details there, otherwise "tl;dr" :-)
>
> https://developer.jboss.org/wiki/KeycloakIntegration
>
> - - Juca.
>
> On 01/08/2015 03:33 PM, Juraci Paixão Kröhling wrote:
>> On 01/08/2015 12:40 PM, Heiko W.Rupp wrote:
>>> Also keep in mind that in the longer run we need to have a way
>>> of granting some access rights to GET /tenants/foo/metrics/bla
>>> from a user of tenant=acme.
>>
>> This is pretty much the only part which is not done yet on the PR.
>> I can think of some solutions for that, but I'd wait until the
>> initial version is merged.
>>
>> - Juca.
>>
>> _______________________________________________ rhq-devel mailing
>> list rhq-devel(a)lists.fedorahosted.org
>> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUtnZtAAoJECKM1e+fkPrXJzQH/isLKuqKwG9XgO9MWO8hcxmz
> fbc1EpBbloifJOuQfN67SzrQ2lOrFyV3LB9q9o/vLHakhGGhM0eZIbadChKta60k
> MI02vppahpEp+pdW9aDnyr1dCyIbuecWikqPeyNPxCwfuhzYmAsFpUOwX3gUvtXN
> /s0qDXrJ1yOsMzW3fGnjOCLWs6BtXERCxxklfbTbxtPn0Y8YV5Bv2Z4oV9C+syIs
> kuGFMK3eTNA0OEQsqdQsAO2Tjd43I9Z0/9zpiaVtgRvIAm109Y/sBcOjS+AwNH2b
> rhCOm+7Rh9NNgIXAkVMPWXLXX4yWaxWtpzhm/6/jYw5t6Xmg/vHpYdWgqAfd2Z8=
> =SbsT
> -----END PGP SIGNATURE-----
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
9 years, 3 months
Re: [Hawkular-dev] Should the components depend on the bus ?
by Thomas Segismont
Le 20/01/2015 13:56, Heiko W.Rupp a écrit :
> If I understand you correctly, the question is about the api between bus ("JMS") and the
> components that so far have a REST-api and where it lives.
> If we try not to "pollute" the individual sub-projects with integration code, which makes a lot of
> sense, we probably need to easily define "bus-listeners" inside the bus module, that read
> a configuration (file) and know where to listen for events, how to invoke which rest-call and
> how to proceed with responses.
I like the idea
9 years, 3 months
Re: [Hawkular-dev] Should the components depend on the bus ?
by Thomas Segismont
Le 20/01/2015 11:14, Lukas Krejci a écrit :
> But I don't think it is
> worth the effort to suppose that the components will primarily be used and
> deployed on their own - I think the opposite is true.
I think nobody expects the components to be primarily used on their own.
It may not be our team's priority to work on individual components
packaging or to promote them individually. But I believe it's worth the
effort to keep that kind of usage in mind before taking design
decisions. Otherwise it will quickly become hard to do, thus lowering
the chances for community to take over.
9 years, 3 months
[metrics] Looking for advice on ListenableFuture usage
by Thomas Segismont
Hi everyone,
I'm looking for advice on how to use Futures#transform[1] and friends
(#addCallback, #withFallback)
These methods all have an overloaded version which takes a JDK Executor
instance as additional argument.
When the base method is called, Guava will use the so-called
"sameThreadExecutor". Consequently, the code will be executed:
* by the caller thread, if the underlying Future has completed already
* otherwise, by the thread completing the underlying Future
When the overloaded method is called, Guava will submit tasks to the
provided executor.
In the metrics code right now, the base method is used almost
everywhere. Considering that in most cases it will take more time to get
the response from C* than to complete the REST Handler code, it's the
Datastax driver threads which will execute the chain of callbacks, down
to the call to javax.ws.rs.container.AsyncResponse#resume
Could that be a problem? I guess it's safe when callbacks only
transforms the data loaded. I'm not sure about the call to
AsyncResponse#resume.
Thoughts?
Thanks,
Thomas
[1]
http://docs.guava-libraries.googlecode.com/git-history/v16.0.1/javadoc/co...
9 years, 3 months
Welcome to Hawkular-dev
by Heiko W.Rupp
Hello and welcome to Hawkular.
This list is intended to discuss the development of Hawkular and all of its sub-projects.
Heiko
9 years, 3 months
