geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Server farm management based on plugins
Date Fri, 25 Sep 2009 16:44:01 GMT
Hi Viola,

On Sep 25, 2009, at 1:04 AM, viola lu wrote:

> Thanks. David.
> I tried this function, and some details to confirm with you:
>  1.Farm Controller should install plugin-farm, plugin-farm- 
> datasource plugins , set its DefaultPluginRepository attribute in  
> file as a share repository  
> accessible by all farm members.If farm members has no access  
> authority to this share repository, farm deploy will fail.

>  2.Every farm member should install plugin-farm-member plugin, set  
> NodeName, and ServerHostname=[NODE_IP] attributes in file config- 
> ServerHostname is not set to its  
> corresponding IP, this farm node will not be added into this farm  
> goup.Also farm member should add share install plugin repository to  
> its file including access username  
> and password like
> http\://\:8080/plugin/maven-repo/=system 

> So that access passes.
>  3.After run cluster/deploy remove -l pluginlist1 -a **/hello/**,  
> this will remove the plugin from all farm members, but fail to  
> delete the plugin record from table PLUGINLIST_PLUGIN of   
> PluginFarmDatatabase db on controller node,

this command turns into farm.removePluginFromPluginList, so this seems  
like a bug.

> this will result in duplicate(redundant) records in db, and if  i  
> run cluster/deploy remove -c cluster1 -l pluginlist1, plugin list  
> will be removed from table PLUGINLIST_CLUSTER, but pluginlist1 is  
> still kept in table PLUGINLIST,

this seems correct to me, a plugin list can exist even if it is not  
associated with any clusters

> when add a pluginlist to cluster, both tables are updated meantime,

I'd expect this to create records in cluster and pluginlist if they  
are missing, and then insert into cluster_pluginlist.

> so seems PluginFarmDatatabase can't keep integrity when delete.

I think you found some bugs :-)

Looking at the groovy ClusterCommand, I'd guess that we need some more  
remove commands:

remove --cluster deletes a cluster from the cluster table after  
removing any cluster_pluginlist records that refer to the cluster
remove --pluginlist deletes a pluginlist from the pluginlist table  
after removing appropriate cluster_pluginlist and pluginlst_plugin  
remove --pluginartifact deletes a plugin from the plugin table after  
removing appropriate pluginlist_plugin records.

Does this make sense to you?

david jencks
> Thanks.
> After
> On Wed, Sep 23, 2009 at 9:19 AM, David Jencks  
> <> wrote:
> On Sep 22, 2009, at 2:25 AM, viola lu wrote:
>> Hi, David:
>>  According to jira 
>> , there should be a FarmComand.groovy file under server/trunk/ 
>> framework/modules/geronimo-commands/src/main/groovy/org/apache/ 
>> geronimo/commands/FarmCommand.groovy , which should implement  
>> deploy/farm, but from Geronimo 2.2 branch and server trunk, this  
>> file is missing.
>> And also from doc 
>> , there should be a GShell deploy/farm command to mange farm.But  
>> after i installed plugins below,
>> org.apache.geronimo.configs/plugin-farm-datasource/2.2-SNAPSHOT/car
>> org.apache.geronimo.configs/plugin-farm-member/2.2-SNAPSHOT/car
>> org.apache.geronimo.configs/plugin-farm/2.2-SNAPSHOT/car
>> i still can't find out this command via gshell command, just  
>> cluster/deploy and cluster/heartmonitor.Can you give some hints?
> At some point the "farm" commands were renamed to "cluster".  AFAIK  
> there are no gshell commands related to deployment based clustering  
> since you set that up with some special repositories in the server  
> that are then accessed using normal gshell commands.
>> And "Server farm management based on plugins" means install plugins  
>> to farm members, but if we want to deploy applications (non-plugin  
>> forma) to farm members, we still follow "Farming using Deployment "  
>> article: 
>> , right?
> I think you should first consider which farm technology better suits  
> your needs, then decide whether to pre-deploy your apps as plugins  
> and use the plugin based clustering or deploy your apps directly to  
> a deployment based cluster.  I can't think of any good reasons to  
> use the deployment based cluster, but other people might be able to.
> hope this is correct and helps
> thanks
> david jencks
>> Thanks.
>> -- 
>> viola
> -- 
> viola

View raw message