[jboss-as7-dev] Configuration/management functionality AS/Fuse

[Andrig Miller]

This is a great topic, but it might be a couple of weeks premature. 

During the FY'14 kickoff meetings in NewCastle, we will be discussing this topic, from the idea of having a core/base that all products, including EAP would be layered on top of. 

I am responsible for presenting this basic idea, and have done some work already on understanding what I think that core or base infrastructure would look like. 

Having said that, my general idea is that the base or core infrastructure would consist of the MSC/and domain components (along with others) that form the basis of a runtime and a management layer, with one management and configuration API. Everything else would layer on top of that, and share the same management layer below. 

Andy 

----- Original Message -----

> From: "Thomas Diesler" <thomas.diesler at jboss.com>
> To: "Brian Stansberry" <brian.stansberry at redhat.com>, "Guillaume
> Nodet" <gnodet at redhat.com>
> Cc: "jboss-as7-dev at lists.jboss.org Development"
> <jboss-as7-dev at lists.jboss.org>, osgi-wrk-grp at redhat.com
> Sent: Friday, March 8, 2013 9:21:33 AM
> Subject: [jboss-as7-dev] Configuration/management functionality
> AS/Fuse

> Hi Brian/Guillaume,

> in the OSGi Working Group kick-off meeting I proposed a line of
> thought does goes like this:

> * AS can be seen as an R5 compliant Core Framework that can be
> bootstrapped like any other compliant framework. We can take proper
> behaviour of the OSGi API layer for granted and can therefore safely
> assume that the Core Framework that Karaf currently runs on (i.e.
> Felix) can be replaced by AS.
> * For long term consolidation of the two product lines (i.e. EAP &
> Fuse) there are two functional areas key: management and
> configuration
> * There should be one way to configure the various subsystems that
> run on the platform
> * There should be one API for managing the platform
> * The consolidation effort could initially focus on these two areas
> and aim to elliminate functional overlap and conflicts

> In parallel to the general requirement gathering I'd like to start a
> conversation about the respective management/configuration
> functionality in the two product lines and initially identify the
> overlap/conflicts. Perhaps we could start with the easier of the two
> (i.e. configuration) and hear from each other how this currently
> works.

> * How are Fuse products configured?
> * How does AS unified configuration work?

> The goal would be to come up with a specific set of requirements for
> the target platform that accommodates the configuration needs for
> both product lines. We could then have a simmilar approach for the
> management layer.

> What do you think?

> cheers
> --thomas

> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx

> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20130308/89c21824/attachment.html