You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/10/28 20:41:44 UTC

[jira] Created: (GERONIMO-4382) New Server Instance via plugins

New Server Instance via plugins
-------------------------------

                 Key: GERONIMO-4382
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4382
             Project: Geronimo
          Issue Type: New Feature
      Security Level: public (Regular issues)
          Components: commands, Plugins
    Affects Versions: 2.2
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 2.2


After staring at the farming sample long enough I realized that it's pretty easy to duplcate a server by the same process as used in the farm sample to install the same plugin list on a bunch of servers running in the same geronimo install.  Basically, just fire up a new ServerInfo for the new instance, construct a PluginInstallerGBean around it, and install all the existing plugins  into the new instance.

This might be enough of a solution to close GERONIMO-3123.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-4382) New Server Instance via plugins

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643530#action_12643530 ] 

David Jencks commented on GERONIMO-4382:
----------------------------------------

Missed the groovy command, added in rev 708938.  Thanks jbohn!

> New Server Instance via plugins
> -------------------------------
>
>                 Key: GERONIMO-4382
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4382
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: commands, Plugins
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2
>
>
> After staring at the farming sample long enough I realized that it's pretty easy to duplcate a server by the same process as used in the farm sample to install the same plugin list on a bunch of servers running in the same geronimo install.  Basically, just fire up a new ServerInfo for the new instance, construct a PluginInstallerGBean around it, and install all the existing plugins  into the new instance.
> This might be enough of a solution to close GERONIMO-3123.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (GERONIMO-4382) New Server Instance via plugins

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-4382.
----------------------------------

    Resolution: Fixed

Implemented rev 708650.  This also required splitting up the boilerplate plugin into install bits (lib, bin...) and instance bits (var).

We might want the command to let you create lots of servers at once, e.g. -n server --from 1 --to 10  would create server1, server2.... server10.

> New Server Instance via plugins
> -------------------------------
>
>                 Key: GERONIMO-4382
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4382
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: commands, Plugins
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2
>
>
> After staring at the farming sample long enough I realized that it's pretty easy to duplcate a server by the same process as used in the farm sample to install the same plugin list on a bunch of servers running in the same geronimo install.  Basically, just fire up a new ServerInfo for the new instance, construct a PluginInstallerGBean around it, and install all the existing plugins  into the new instance.
> This might be enough of a solution to close GERONIMO-3123.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-4382) New Server Instance via plugins

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645018#action_12645018 ] 

David Jencks commented on GERONIMO-4382:
----------------------------------------

Jbohn noticed this didn't actually work... persistenceConfigurationList reference turned out to be misconfigured.  FIxed in rev 711325.

> New Server Instance via plugins
> -------------------------------
>
>                 Key: GERONIMO-4382
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4382
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: commands, Plugins
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2
>
>
> After staring at the farming sample long enough I realized that it's pretty easy to duplcate a server by the same process as used in the farm sample to install the same plugin list on a bunch of servers running in the same geronimo install.  Basically, just fire up a new ServerInfo for the new instance, construct a PluginInstallerGBean around it, and install all the existing plugins  into the new instance.
> This might be enough of a solution to close GERONIMO-3123.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.