[jboss-as7-dev] Management Configuration

[Darran Lofthouse]

Just had a chat with Brian in IRC.

I am going to mock up some proposed configurations for features I know 
are needed and will then open this up to see if anyone else working on 
aspects of the centralised domain management have any additional 
configuration requirements identified.

Regards,
Darran Lofthouse.


On 02/16/2011 02:11 PM, Darran Lofthouse wrote:
> How fixed are we on having the existing<management>  element actually
> called management?
>
> At the moment the only use for that element is to list the management
> APIs that should be enabled on specific hosts or in the case of
> standalone on the single instance.  Converting to something like
> <management-apis>  would be more meaningful for it's actual intent.
>
> For the general top level element for domain management a few names
> start to come to mind: -
>     <management>
>     <domain-management>
>     <administration-management>  /<admin-management>
>
> Or as the domain and server elements are their own complex types in the
> xsd could we have<domain-management>  in a domain.xml and
> <host-management>  in a standalone.xml?
>
> Regards,
> Darran Lofthouse.
>
>
>
> On 02/09/2011 03:25 PM, Brian Stansberry wrote:
>> The intent was to use the domain-controller-localType in host.xml.
>> However, that doesn't work very well for anything that needs to get
>> pushed to other hosts (i.e. the central management security policy
>> config). For that we need something in domain.xml. The outer element for
>> that should be something fairly general (e.g. not "security") so we can
>> drop in other things besides the security policy if its clear they are
>> needed.
>>
>> We'll need to sort the names of elements a bit, plus how the
>> domain-level config propagates through the host and server level
>> in-memory management trees. We are already using "management" for a
>> particular purpose in host.xml and standalone.xml. Thinking simply, any
>> central management config that comes from the DC would get slotted into
>> the host and server level in-memory management trees as siblings of what
>> gets parsed out of the host.xml/standalone.xml "managementType". But
>> that may not work cleanly; it needs thought.
>>
>>
>> On 2/9/11 5:10 AM, Darran Lofthouse wrote:
>>> Has there been any consideration yet regarding where the actual
>>> configuration for the management of the servers will take place?
>>>
>>> Looking at the schemas we have a 'managementType' that can exist either
>>> in the standalone.xml or in the host.xml - at the moment this element
>>> only controls which APIs are available and I think these locations make
>>> sense as which to expose could be a host by host decision.
>>>
>>> For the actual security of the management APIs I think we are going to
>>> want something more central that applies to a full domain so something
>>> that would be in both the domain.xml and the standalone.xml.
>>>
>>> Also longer term could this require additional centralised
>>> configuration?  Possibly thinks like persistence policies, console
>>> customisation, rules for which hosts can join etc...
>>>
>>> Regards,
>>> Darran Lofthouse.
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev