Petals Distribution

Petals CLI and distributed deploiement

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.2.4
  • Fix Version/s: 5.0.0-M1
  • Component/s: Clients
  • Security Level: Public
  • Description:
    Hide

    To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently.

    As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine.

    In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. But if we can launch several Petals CLI instances in the same time, the script files can be executed concurrently launching a Petals CLI instance by script file, delegating the concurrency to the execution shell.

    Show
    To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently. As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine. In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. But if we can launch several Petals CLI instances in the same time, the script files can be executed concurrently launching a Petals CLI instance by script file, delegating the concurrency to the execution shell.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 7 May 2015 - 08:21:55 +0200
Field Original Value New Value
Link This issue depends on PETALSESBCLI-117 [ PETALSESBCLI-117 ]
Christophe DENEUX made changes - Thu, 7 May 2015 - 08:26:23 +0200
Priority Blocker [ 1 ]
Description To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently.

As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine.

In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. Petals CLI should be able to execute several script file in a dedicated context. 		To deploy a Petals ESB composed of several nodes, we should be able to deploy components and SAs on each node concurrently.

As Petals CLI is able to work with only one container at a time, we should be able to launch several Petals CLI in the same time on the same machine.

In script mode, as the connexion establishment must be done in the script file, we can imagine to execute several scripts concurrently with the same Petals CLI instance. But if we can launch several Petals CLI instances in the same time, the script files can be executed concurrently launching a Petals CLI instance by script file, delegating the concurrency to the execution shell.
Christophe DENEUX made changes - Thu, 7 May 2015 - 08:27:11 +0200
Fix Version/s 4.3.0 [ 10532 ]
Priority Blocker [ 1 ] Major [ 3 ]
Christophe DENEUX made changes - Wed, 27 May 2015 - 09:08:26 +0200
Fix Version/s 4.3.0 [ 10562 ]
Fix Version/s 4.3.0-beta-1 [ 10532 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 4 Jun 2015 - 15:24:33 +0200

A workaround is to set the parameter embedded.http.port to 0 in Petals CLI preferences.

Show
Christophe DENEUX added a comment - Thu, 4 Jun 2015 - 15:24:33 +0200 A workaround is to set the parameter embedded.http.port to 0 in Petals CLI preferences.
Christophe DENEUX made changes - Thu, 4 Jun 2015 - 15:28:04 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Thu, 4 Jun 2015 - 15:28:06 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 4 Jun 2015 - 15:28:27 +0200

Fixed by PETALSESBCLI-117

Show
Christophe DENEUX added a comment - Thu, 4 Jun 2015 - 15:28:27 +0200 Fixed by PETALSESBCLI-117
Christophe DENEUX made changes - Thu, 4 Jun 2015 - 15:28:27 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.0 [ 10412 ]
Fix Version/s 4.3.0 [ 10562 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
28d 7h 12m
1
Christophe DENEUX
Thu, 4 Jun 2015 - 15:28:04 +0200
Open Open In Progress In Progress
2s
1
Christophe DENEUX
Thu, 4 Jun 2015 - 15:28:06 +0200
In Progress In Progress Resolved Resolved
21s
1
Christophe DENEUX
Thu, 4 Jun 2015 - 15:28:27 +0200



People

Dates

  • Created:
    Thu, 7 May 2015 - 08:15:59 +0200
    Updated:
    Thu, 4 Jun 2015 - 15:28:27 +0200
    Resolved:
    Thu, 4 Jun 2015 - 15:28:27 +0200
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.