geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <>
Subject Re: [jira] Created: (GERONIMO-4424) Move Create Plugin and Assemble Server portlets to new Tools category
Date Fri, 21 Nov 2008 18:36:11 GMT
I disagree on the Plugin portlet belonging to Applications:
- Exporting plugins has nothing to do with deploy/redeploy/undeploy of 
applications or starting/stopping/uninstalling modules.  Exporting an 
existing app (WAR/EAR once it works) or module is more of a "gui tool" 
for creating a plugin (which sucks for modules, as it requires the user 
to manually add the geronimo-plugins.xml into the created CAR.) 
Exporting existing CARs seems redundant and should be considered a 
"convenience tool", given the Plugin installer can install CARs from 
another server.
- Creating new server assembly (or server instances once we create a 
portlet for it :-) ) is also more of a tool, as it has nothing to do 
with installing Plugins or apps into the existing server, but instead 
allows "building/exporting" existing plugins into a new custom server.

Plan Creator is really a tool, as it doesn't update the existing WAR/EAR 
and provide a way to deploy it once it is updated.  If it did, then it 
could go on the Applications -> Deploy page, as a way to update and 
deploy apps designed for other JEE5 server vendors.

Monitoring is a tool (just like a JMX viewer.)  Most production users 
who really want to monitor their servers and apps for up-time, should be 
using an out-of-JVM (JMX) and off-server monitoring (Nagios), instead of 
a server plugin that will die with the server when encounters an OOM. 
It should really be an optional plugin, but that topic is in another 
thread that I need to restart.

And I'll start a discuss thread to detail all of the changes I'm 
thinking about....


David Jencks wrote:
> I need a lot more convincing before I think this move and some of those 
> proposed in 4423 are a good idea.  More specifically...
> I think these operations are conceptually similar:
> - deploying new apps
> - installing plugins
> - extracting plugins
> - extracting servers
> - turning plugins on and off.
> Plan creator sort of belongs nearby since you'd use it to get ready to 
> deploy a new app.
> I think monitoring needs to be its own category, together with (future) 
> cluster management.
> I don't think Tools is a good category name.  The entire admin console 
> is a bunch of tools.... how do you distinguish the ones you are putting 
> in tools from all the others?  "Debug Views" always seemed like a 
> strange name but at least it indicated the category pretty well -- stuff 
> you'd look at when you were trying to root around inside the server and 
> needed hard to find info because something wasn't set up right.
> I'd prefer to see discussion on the dev list with the entire plan you 
> have for organization.
> thanks
> david jencks
> On Nov 21, 2008, at 8:27 AM, Donald Woods (JIRA) wrote:
>> Move Create Plugin and Assemble Server portlets to new Tools category
>> ---------------------------------------------------------------------
>>                 Key: GERONIMO-4424
>>                 URL:
>>             Project: Geronimo
>>          Issue Type: Improvement
>>      Security Level: public (Regular issues)
>>          Components: console
>>            Reporter: Donald Woods
>>            Assignee: Donald Woods
>>            Priority: Minor
>>             Fix For: 2.2
>> Move the Create Plugin and Assemble Server portlets from the 
>> Applications -> Plugins page to new pages under the Tools category, as 
>> these portlets have nothing to do with managing applications.
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.

View raw message