Petals ESB Container

Launch several containers from one installation

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 3.1
  • Fix Version/s: 4.2.0
  • Component/s: Packaging
  • Security Level: Public
  • Description:
    Hide

    The Petals ESB Launcher should be able to launch several containers from one installation of the runtime.

    For example

    • Petals ESB is installed into /usr/local/petals-esb
    • Several available container configurations are available into /etc/petals-esb/containers-available
    • Several active container configurations are availbale into /etc/petals-esb/containers-enabled
    • For each container configured into /etc/petals-esb/containers-enabled, the Petals ESB launcher use the runtime to instanciate a container.
    • To de-activate temporarly a configuration, just unlink it into /etc/petals-esb/containers-enabled
    Show
    The Petals ESB Launcher should be able to launch several containers from one installation of the runtime. For example
    • Petals ESB is installed into /usr/local/petals-esb
    • Several available container configurations are available into /etc/petals-esb/containers-available
    • Several active container configurations are availbale into /etc/petals-esb/containers-enabled
    • For each container configured into /etc/petals-esb/containers-enabled, the Petals ESB launcher use the runtime to instanciate a container.
    • To de-activate temporarly a configuration, just unlink it into /etc/petals-esb/containers-enabled
  • Environment:
    -

Issue Links

Duplicate
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Roland Naudin added a comment - Mon, 30 Aug 2010 - 10:19:19 +0200

It seems to be a proposition for the Petals-Exploitation project?
I think this is not the goal of the actual launcher in Petals ESB.
The actual launcher is basic and may stay like that until the relay of the Petals-Exploitation tools.

Show
Roland Naudin added a comment - Mon, 30 Aug 2010 - 10:19:19 +0200 It seems to be a proposition for the Petals-Exploitation project? I think this is not the goal of the actual launcher in Petals ESB. The actual launcher is basic and may stay like that until the relay of the Petals-Exploitation tools.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 30 Aug 2010 - 11:01:55 +0200

I think a part of this issue impacts the launcher, for launch Petals with a specific configuration file. It seems to me that it's not possible today.
An other part (directory tree) impacts Petals-Exploitation.

Show
Christophe DENEUX added a comment - Mon, 30 Aug 2010 - 11:01:55 +0200 I think a part of this issue impacts the launcher, for launch Petals with a specific configuration file. It seems to me that it's not possible today. An other part (directory tree) impacts Petals-Exploitation.
Hide
Permalink
Sébastien André added a comment - Fri, 19 Nov 2010 - 17:34:31 +0100

The last version of the launcher cannot be fully parametrized by an external configuration file.

There is still some work to do in the container to centralize the configuration, then I can modify the launcher to allow this kind of startup:
$ petals-esb -c myconfig.xml

Show
Sébastien André added a comment - Fri, 19 Nov 2010 - 17:34:31 +0100 The last version of the launcher cannot be fully parametrized by an external configuration file. There is still some work to do in the container to centralize the configuration, then I can modify the launcher to allow this kind of startup: $ petals-esb -c myconfig.xml
Hide
Permalink
Christophe DENEUX added a comment - Mon, 22 Nov 2010 - 10:06:17 +0100

I prefer a mechanism as Apache2: in the directory /etc/petals, we have the following directories:

  • topologies-available: containing a directory per available topology. Such a directory contains all needed conf files and directories
  • topologies-enabled: containing a directory per running topology. Such a directory contains all needed conf files and directories

So, you can have two scripts:

  • petals-topology -c mytopology : to start all containers located on the current system, members of the topology 'mytopology'
  • petals-esb -c mytopology [-i instance] : to start the local node of the topology, if only one local node. Or to start the node 'instance' of the topology 'mytopology' if several nodes are local.
Show
Christophe DENEUX added a comment - Mon, 22 Nov 2010 - 10:06:17 +0100 I prefer a mechanism as Apache2: in the directory /etc/petals, we have the following directories:
  • topologies-available: containing a directory per available topology. Such a directory contains all needed conf files and directories
  • topologies-enabled: containing a directory per running topology. Such a directory contains all needed conf files and directories
So, you can have two scripts:
  • petals-topology -c mytopology : to start all containers located on the current system, members of the topology 'mytopology'
  • petals-esb -c mytopology [-i instance] : to start the local node of the topology, if only one local node. Or to start the node 'instance' of the topology 'mytopology' if several nodes are local.

People

Dates

  • Created:
    Fri, 27 Aug 2010 - 17:59:33 +0200
    Updated:
    Tue, 29 Oct 2013 - 10:56:15 +0100
    Resolved:
    Tue, 29 Oct 2013 - 10:52:18 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.