Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 42575 invoked from network); 25 Sep 2009 16:44:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Sep 2009 16:44:35 -0000 Received: (qmail 1937 invoked by uid 500); 25 Sep 2009 16:44:34 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 1862 invoked by uid 500); 25 Sep 2009 16:44:34 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 1854 invoked by uid 99); 25 Sep 2009 16:44:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2009 16:44:34 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.136.44.58] (HELO smtp103.prem.mail.sp1.yahoo.com) (98.136.44.58) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 25 Sep 2009 16:44:23 +0000 Received: (qmail 31905 invoked from network); 25 Sep 2009 16:44:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Mime-Version:Subject:Date:References:X-Mailer; b=FDV3IInyNEWDBIricjRBfrh5jCCYPfx2DhxmcdDV7mjXSe6rt34OzP9UcRT5VRjMRrmjhLXy6fNhm3RPDGWnvqMThJR5W2vRNFOxvzrhmJ/4F3wu/P8F5POptZ2wfUMvW6fzLCFYiAAF1nwrapWUGa0cd3FWgXDr+rAxgfRHHAU= ; Received: from 076-076-148-215.pdx.net (david_jencks@76.76.148.215 with plain) by smtp103.prem.mail.sp1.yahoo.com with SMTP; 25 Sep 2009 09:44:01 -0700 PDT X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ-- X-YMail-OSG: _EtL4jsVM1kb5qgqNGq3qmQgXwl0JfOLKB48ae6YOdLhVWGZK8UyoWVs0_eCQWl22JcXaL6Slrp.yZgmuhhiOohjlmlA0hOKnNFbJ_NmghTgys1qg70zvRB7ow0NKR7kAsrJWk2yT7BM2b6xx6Il6SRrKb5lJ2ZVLChzgyy.WjNUcOT03UvAhjf9wG7ybQW0iPB5DIA5rGmsRYHEr9hknf4NLolsI2AAowAc6DZ5xYLS3uLQ5gWNIsw_acORMMLYQliFixQwMYVTqJRInR4- X-Yahoo-Newman-Property: ymail-3 Message-Id: <699609CE-52D7-478E-8507-F93C8CC12FD8@yahoo.com> From: David Jencks To: dev@geronimo.apache.org In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-56-711934313 Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Server farm management based on plugins Date: Fri, 25 Sep 2009 09:44:01 -0700 References: <1B63E2C4-7300-4D2A-AEED-017F805473E9@yahoo.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-56-711934313 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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 config-substitutions.properties as a share repository > accessible by all farm members.If farm members has no access > authority to this share repository, farm deploy will fail. yes... > > 2.Every farm member should install plugin-farm-member plugin, set > NodeName, and ServerHostname=[NODE_IP] attributes in file config- > substitutions.properties.If 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 plugin-repositories.properties including access username > and password like > http\://9.186.10.67\:8080/plugin/maven-repo/=system > \={Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwAAAAEHnh03EmiNu4VTuWH+xZiRBwdAADQUVT yes... > > 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 records remove --pluginartifact deletes a plugin from the plugin table after removing appropriate pluginlist_plugin records. Does this make sense to you? thanks 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 https://issues.apache.org/jira/browse/GERONIMO-4284 >> , 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 http://cwiki.apache.org/GMOxDOC22/plugin-based-farming.html >> , 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: http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html >> , 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 --Apple-Mail-56-711934313 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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 config-substitutions.properties as a share repository = accessible by all farm members.If farm members has no access authority = to this share repository, farm deploy will = fail.

yes...
=
 2.Every farm member should install plugin-farm-member plugin, = set NodeName, and ServerHostname=3D[NODE_IP] attributes in file = config-substitutions.properties.If 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 plugin-repositories.properties including access username and = password like
http\://9.186.10.67\:8080/plugin/maven-repo/=3Dsys= tem\=3D{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAAR= bAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBb= Gd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AI= AAHhwAAAAEHnh03EmiNu4VTuWH+xZiRBwdAADQUVT

y= es...

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 records
remove = --pluginartifact deletes a plugin from the plugin table after removing = appropriate pluginlist_plugin records.

Does = this make sense to you?

thanks
david = jencks

Thanks.


After =

On Wed, Sep 23, 2009 at 9:19 AM, = David Jencks <david_jencks@yahoo.com> = wrote:

On Sep = 22, 2009, at 2:25 AM, viola lu wrote:

Hi, David:
 According to jira https://issues.apache.org/jira/browse/GERONIMO-4284,= there should be a FarmComand.groovy file under server/trunk/framework/modules/geronimo-commands/src/mai= n/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 http://cwiki.apache.org/GMOxDOC22/plugin-based-farming.h= tml, 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-S= NAPSHOT/car
  • org.apache.geronimo.configs/plugin-farm-member/2.2-SNAPS= HOT/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: http://cwiki.apache.org/GMOxDOC22/farming-using-deployme= nt.html, 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

    = --Apple-Mail-56-711934313--