[jboss-as7-dev] Admin console

[David M. Lloyd]

The Domain Controller is a special case of the Host Controller.  The 
Host Controller is not a regular server instance; it's much more minimal 
than that.  Yes it is theoretically possible to squeeze the console into 
the DC but I wouldn't recommend it, at least not unless the console were 
bare-bones minimal (i.e. no dependency on jboss web, or servlets in 
general or any other EE stuff, nor other frameworks; just some miniature 
HTTP server like the Sun one and maybe one or two support libraries at 
most like GWT or whatever) because the HC needs to be able to patch 
itself and the fewer things it has loaded, the easier it is to make that 
process non-fuck-up-able.

I agree with Brian, the most likely solution for hosting the web console 
itself is to treat it as a generic client to the DC (in domain mode) or 
the server controller (in standalone mode).  If we treat the console as 
a special case of a deployment, which can be dropped into any server 
group, it should be very easy to create and configure it using mostly 
existing infrastructure.

On 12/22/2010 11:10 AM, Alan Santos wrote:
>
> The console definitely needs to support standalone as well as domain,
> and I agree that historic data collection is outside the scope of an
> unmanaged instance.
>
> I'm curious about the question of hosting the mgmt console as I assumed
> it would live in the domain controller.  I don't have my notes from
> Antwerp available to double check, but isn't the domain controller just
> another AS instance?  If so why wouldn't it always live in that process?
>
> And now that I've asked that question I'm curious - Are there
> expectations with regard to continuity for deployed applications when
> transitioning a server from a single instance to a domain?
>
> -alan
>
>
> On 12/22/10 11:25 AM, Brian Stansberry wrote:
>> On 12/22/10 8:19 AM, Heiko W.Rupp wrote:
>>> Hi,
>>>
>>> we were talking about admin console before, but I am not sure if we reached any conclusion about
>>> - console for standalone (=non-domain) server mode
>> IMO we need the console to properly support standalone mode.
>>
>>> - will we have a "dedicated" server within a domain to host the console or could
>>>     theoretically every server host the console?
>> Theoretically any server could host the console. The console is a client
>> to the admin interface exposed by the DomainController, the
>> HostController(s) and any ServerController(s).
>>
>> I expect a typical scenario is users will want a separate server to host
>> the console; i.e. separate from the regular servers that handle user
>> requests. Since servers all belong to a server group, that implies a
>> separate server group running a profile sufficient to support the
>> console webapp. The configuration utilities we provide to help users set
>> up their configs need to make it easy to create such a configuration.
>>
>>> - do users expect to see metrics for the last hour from the moment they first
>>>     access the console or already for some time before?
>>>
>> There is no committed requirement to support maintaining a 1 hour
>> history of metrics. IMO if we want to support this, it should be a JON
>> feature, with JON responsible for storing the history. (I realize that
>> begs the question "What about if JON wasn't running..." to which the
>> response is "there is no committed requirement...")
>>
>>>      Heiko
>>>
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
- DML