This is probably a good time for the other Heiko (hrupp) to chime in.  But basically there are a variety of rhq.next, now hawkular, components being worked on, mainly in the design/poc stage.   Metrics is by far the most advanced effort because of it's more direct rhq heritage, but there is also the msg/audit stuff mazz has that is looking to provide a msg bus oriented backbone.  And the agent/platform mechanism he also mentioned.   But additionally there are efforts to offer up some of rhq's stuff in a new, more consumable way.  First and foremost is a more general approach to inventory (resources, resource types, etc), but also configuration, availability and alerting.  So, you'd have the metrics effort tied in, and the ability to feed in metrics for resources, perform alerting, etc.  It's possible, maybe likely, that the same cassandra cluster would be the repository for lots of other stuff, not just the metrics, but that is being hashed out.

You're right about the idea of a more loosely coupled approach, trying to break up the behemoth that is rhq/jon into some more consumable parts.  Hopefully the vision will start to turn into something more concrete in a fairly fast fashion.  Thank you for questioning things, we do need the answers. The overall goal, of course, it to provide parts to an overall mgmt offering that is coherent and consistent across the various offerings.


On 1/8/2015 11:19 AM, Heiko Braun wrote:
I think i’ve found it:
https://developer.jboss.org/en/rhq/next



On 08 Jan 2015, at 17:14, Heiko Braun <ike.braun@googlemail.com> wrote:

I did refer to wf-core to point to the base capabilities of wildfly. Nothing  prevents you from building upon the full EE server (wildfly), although you probably won’t need all the stock components. 

But what you say about Hawkular is interesting. I wasn’t aware of this effort until Mazz brought it forward. Listening to what you say Jay, it seems I confused rhq.metrics with rhq.next. 

Can you point me to some documentation about the architecture and design decisions behind rhq.next?  Is it correct to say that rhq.next  will leverage some of the rhq.metrics components? 

Regards, HeikoB

On 08 Jan 2015, at 16:54, Jay Shaughnessy <jshaughn@redhat.com> wrote:

HeikoB, as for Wildfly-core, we haven't really used that afaik, just using Wildfly at this point because I'm not sure Wildfly-core was quite ready last time we looked.  Has that changed?   I assume wfly-core is much lighter that wfly, and that is the main advantage, giving up the J2EE EAR/WAR support. etc.  Perhaps both wfly-core and wfly proper will both play a role going forward.




_______________________________________________
rhq-devel mailing list
rhq-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel