On 21/11/2007, at 7:55 AM, Joe Bohn wrote:
Regarding the list-modules command, it lists all the
configurations per target, i.e. configuration store.
As Kevan also pointed out, I think that we need to consider the
multiple configuration stores in the console when more than one is
present
On 17/11/2007, at 12:30 AM, Kevan Miller wrote:
On Nov 13, 2007, at 9:36 PM, Gianny Damour wrote:
Hi Joe,
After some investigations, here is my understanding of problem 1:
there are two deployments because by default, i.e. when no target
is specified, the distribute command executes
Gianny Damour wrote:
On 17/11/2007, at 12:30 AM, Kevan Miller wrote:
On Nov 13, 2007, at 9:36 PM, Gianny Damour wrote:
Hi Joe,
After some investigations, here is my understanding of problem 1:
there are two deployments because by default, i.e. when no target is
specified, the
On Nov 13, 2007, at 9:36 PM, Gianny Damour wrote:
Hi Joe,
After some investigations, here is my understanding of problem 1:
there are two deployments because by default, i.e. when no target is
specified, the distribute command executes against all the
configuration stores defined by a
On 13/11/2007, at 8:01 PM, Jeff Genender wrote:
Gianny Damour wrote:
I hope we are not talking about the same thing. I am talking about a
deployment time constraint and not a runtime constraint mandating
that all the servers are reachable when an application is *deployed*.
FWIW, such a
Gianny Damour wrote:
Nous parlons enfin la meme langue :).
Nous avons toujours compris les uns les autres ;-)
I'll bet you didn't know I am in Paris right now...did ya? ;-)
Jeff
Agreed: this would be a nice enhancement.
Jeff
Hi Joe,
After some investigations, here is my understanding of problem 1:
there are two deployments because by default, i.e. when no target is
specified, the distribute command executes against all the
configuration stores defined by a Geronimo instance. Note that this
default behavior
Distribution and start/stop of clustered deployments
Key: GERONIMO-3597
URL: https://issues.apache.org/jira/browse/GERONIMO-3597
Project: Geronimo
Issue Type: New Feature
Security
[
https://issues.apache.org/jira/browse/GERONIMO-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianny Damour reassigned GERONIMO-3597:
---
Assignee: Gianny Damour
Distribution and start/stop of clustered deployments
[
https://issues.apache.org/jira/browse/GERONIMO-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianny Damour closed GERONIMO-3597.
---
Resolution: Fixed
This is now implemented.
Distribution and start/stop of clustered
Hi,
I have just checked in support for distribution of configurations to
clusters and also management, i.e. start/stop, of such clustered
deployments.
I will try to explain how everything hangs together so that people
can jump in, provide feedback, request enhancements etc.
There is
Gianny Damour wrote:
2. The clustered store uploads the backed configuration to the
registered cluster members, which subsequently locally install them. If
the remote installation fails for one of the members, then the
clustered store removes the configuration from all the members having
On 13/11/2007, at 4:35 AM, Jeff Genender wrote:
Gianny Damour wrote:
2. The clustered store uploads the backed configuration to the
registered cluster members, which subsequently locally install
them. If
the remote installation fails for one of the members, then the
clustered store
Hi Gianny,
Lots of newbie questions from me. I'm not even going to pretend that I
understand your clustering changes just yet ... so please bear with me.
I just want to point out a few things that I noticed with a single
server instance and get your take on them.
1) Deploying a simple
Gianny Damour wrote:
You can successfully distribute when all the configured cluster
members are running. If one of them is down, then the installation
fails. This seems to be a typical scenario - at least based on the
clustered deployments I have been working with.
Hmmm...I have found
On 13/11/2007, at 4:42 PM, Jeff Genender wrote:
Gianny Damour wrote:
You can successfully distribute when all the configured cluster
members are running. If one of them is down, then the installation
fails. This seems to be a typical scenario - at least based on the
clustered deployments I
16 matches
Mail list logo
