No concept of a platform?
John Mazzitelli
mazz at redhat.com
Wed Jan 7 21:04:41 UTC 2015
In fact, I've already started down this path. Using Wildfly 8, i've got prototypes for the messaging infrastructure as well as the "agent" component (which is not a good name because I think server components will be able to use this too) - where the "agent" component can deploy wars/ears directly from its "modules" (thus making use of the new patching capability since its in the module itself).
See my threads on the rhq.next forums about this:
https://developer.jboss.org/thread/251228
https://developer.jboss.org/thread/250816
I have a prototype "audit" subsystem that uses Wildfly 8 as its base and the other rhq.next (aka hawkular) code. My code is all over the place in different repos, but those forum threads should point to the code.
----- Original Message -----
> Guys, ay what point do you want to start thinking about a platform for all
> the bits and pieces you throw together? Possibly even a platform that
> supports coordinated multi-node deployments and operations?
>
> How do you think is a bunch of EAR’s and WAR’s creating a coherent whole at
> the end?
>
> I can understand that Wildfly might not be your first choice for achieving
> this. But we did great length to make sure some your basic requirements are
> covered. I still believe wildfly-core would offer a reasonable baseline for
> RHQ metrics and related projects. But it seems to me that you cannot or just
> don’t want to see the value in it.
>
> If you have another proposal for a managed runtime, bring it up, but please
> don’t tell me that your idea of a system architecture is limited to a
> servlet container.
>
> The more developer-centric artefacts you create, the less likely it becomes
> to integrate as managed, secure and scalable system at the end. I know
> integration is the Cinderella of software development, but if you don’t
> account for it from the beginning it’s very unlikely to happen at the end.
>
> RHQ metrics started on good grounds, with several reasonable approaches to
> things. But the project’s structure degrades the more things you slam onto
> it.
>
> I hope this email creates room for another discussion. About the big picture,
> about the system architecture for RHQ metrics and integration options for
> projects like Wildfly that have been looking forward to it so far.
>
> Regards, Heiko B.
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
More information about the rhq-devel
mailing list