I have to go back and see the directory layout your proposing. I
didn't see a specific proposal in the JIRA so if I'm covering
existing ground my apologies.
How about for purposes of this discussion:
$G == GERONIMO_HOME
We organize servers by default as:
$G/var/servers/geronimo01/config
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
I have to go back and see the directory layout your proposing. I
iki.apache.org/GMOxDOC20/running-multiple-instances-of-geronimo.html
didn't see a specific proposal in the JIRA
Some information is here:
So, we have 2 directories that need to be created for every instance -
/deploy
/var
The easiest way to keep users (who will have less working knowledge of Geronimo
than us developers) from screwing up their server when trying to use multiple
instances, is to put both of those directories
Some clarification (inline)...
--- Anita Kulshreshtha [EMAIL PROTECTED] wrote:
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
I have to go back and see the directory layout your proposing. I
iki.apache.org/GMOxDOC20/running-multiple-instances-of-geronimo.html
didn't see a specific
On Apr 26, 2007, at 8:43 AM, Anita Kulshreshtha wrote:
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
I have to go back and see the directory layout your proposing. I
iki.apache.org/GMOxDOC20/running-multiple-instances-of-geronimo.html
didn't see a specific proposal in the JIRA
Some
On Apr 26, 2007, at 9:17 AM, Donald Woods wrote:
Can't we just reorganize the existing layout to be a simpler -
GHOME/instances/template/var/...
GHOME/instances/template/deploy/
GHOME/instances/default/var/...
GHOME/instances/default/deploy/
where instances could be a word we all vote
On a closer inspection this alternative (2) does not look so
attractive. IIUC, The classes to determine the geronimo install
directory and directory copy are available in system module. Either we
duplicate the code in kernel or wait till later (after booting kernel,
loading bootstrap
Just make users copy the directory and be done with it.
--jason
On Apr 25, 2007, at 4:58 AM, Anita Kulshreshtha wrote:
On a closer inspection this alternative (2) does not look so
attractive. IIUC, The classes to determine the geronimo install
directory and directory copy are available in
I agree. I don't think normal geronimo startup should involve
copying stuff from one location to another to set up a new server
location. We could build some kind of admin server to manage setting
up/removing server clones but I don't think it should be part of
the base server normal
Admin server or boot strap shell might not be a bad idea. Since G
needs so many flags to set endorsed + ext dirs muck now, it might be
a good idea to introduce a tiny shell which can handle invoking the
server correctly. Maybe something to think about for 2.1...
--jason
On Apr 25,
--- David Jencks [EMAIL PROTECTED] wrote:
I agree. I don't think normal geronimo startup should involve
copying stuff from one location to another to set up a new server
location.
This is needed because we need to keep a pristine copy of 'var'
directory to create additional
Just make it a manual step for now... as time goes on we may need to
add a boostrap jvm-overlord thingy to handle more simplified/
automatically cloning, but for now... telling users to cp -r a/ b/ is
probably easiest with the least amount of wrinkles.
--jason
On Apr 25, 2007, at 7:10 PM,
What about creating a jar/zip of the var directory when the assembly is created,
so you always have a pristine copy and could easily use a script to unjar/unzip
it into a new directory via the user's JVM?
-Donald
Anita Kulshreshtha wrote:
--- David Jencks [EMAIL PROTECTED] wrote:
I agree.
I would like to set the property o.a.g.server.name=geronimo in
MainConfigurationBootstrapper. This will prevent accidental corruption
of 'var' directory. If the user did not create a geronim/var the server
will not start.
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
Just make it a
Actually, what is in var that needs to be so pristine? Stuff put
into var dirs are generally very dynamic and heavily state driven...
not sure why that would need to be kept pristine across instances...
sans the log4j configuration files, which really belong in an etc/ or
conf/ and no in
On Apr 25, 2007, at 7:31 PM, Anita Kulshreshtha wrote:
I would like to set the property o.a.g.server.name=geronimo in
MainConfigurationBootstrapper. This will prevent accidental corruption
of 'var' directory. If the user did not create a geronim/var the
server
will not start.
Okay, so if
If I was creating new server instances, I'd like to always start with a known
var/config.xml
The other thought with preserving the base /var files in a jar/zip - it allows an
admin/root user to install the base server files and then allow users to create
their own instances by extracting the
Why is it making geronimo/var? Its usually much better to let Java
handle making directories and other complicated tasks and keep
platform scripts as simple as possible.
--jason
On Apr 24, 2007, at 4:51 AM, Anita Kulshreshtha wrote:
Could someone please help me with testing a unix
The other option is to update MainConfigurationBootstrapper as
follows:
1. if geronimo.org.apache.geronimo.server.name system property is not
set, set it to 'geronimo'.
2. If 'geronimo' dir does not exist, create one and copy 'var' to it.
3. do the rest...
Thanks
Anita
--- Jason Dillon
Well, that sounds better than putting that muck into platform scripts.
Though, why not simplify this even more and force users to make the
correct directories with the right configuration, and then just die
quickly if the directory is missing with an informative error message
to that
+1
I think the platform scripts should be as thin as possible
-dain
On Apr 24, 2007, at 12:38 PM, Jason Dillon wrote:
Well, that sounds better than putting that muck into platform scripts.
Though, why not simplify this even more and force users to make the
correct directories with the
21 matches
Mail list logo
