[#PETALSESBCONT-276] Make the topology dynamic - Petals Link JIRA

Details

Type: New Feature
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.2.0
Fix Version/s: 5.0.0
Component/s: Topology/network
Security Level: Public

Description:
Hide
To prepare Petals ESB to be cloud ready, make the topology dynamic:

to add a new Petals node to a running topology without stopping its nodes,

to remove a new Petals node to a running topology without stopping its nodes,

to migrate a running Petals node from a running topology to another one.
Show
To prepare Petals ESB to be cloud ready, make the topology dynamic:

to add a new Petals node to a running topology without stopping its nodes,

to remove a new Petals node to a running topology without stopping its nodes,

to migrate a running Petals node from a running topology to another one.

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSESBCONT-295~~ Service invocation on remote container fails
~~PETALSESBCONT-280~~ The JMX API for the service 'Topology' is not the expected one
~~PETALSESBCONT-287~~ Move the composite 'Container' inside the composite 'JBI-Management'
~~PETALSESBCONT-288~~ Introduce the Fractal component 'ContainerController'
~~PETALSESBCONT-289~~ 'Installer' should be referenced inside the 'ContainerService' instead of the 'AdminService'
~~PETALSESBCONT-290~~ 'ServiceAssemblyLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
~~PETALSESBCONT-291~~ 'ComponentLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
~~PETALSESBCONT-292~~ 'SharedLibraryLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
~~PETALSESBCONT-267~~ Externalize the registry implementation

This issue blocks:
~~PETALSDISTRIB-66~~ Support dynamic topology
~~PETALSESBCONT-285~~ A sub-domain supports the mode 'static' and 'dynamic'
~~PETALSESBCLI-85~~ Introduce the command 'move-container'

Activity

Descending order - Click to sort in ascending order

Hide

Permalink

Christophe DENEUX added a comment - Mon, 2 Jun 2014 - 11:06:10 +0200

The user documentation of the dynamic topology is written here: https://doc.petalslink.com/display/petalsesbsnapshot/Topology+Configuration

Show

Christophe DENEUX added a comment - Mon, 2 Jun 2014 - 11:06:10 +0200 The user documentation of the dynamic topology is written here: https://doc.petalslink.com/display/petalsesbsnapshot/Topology+Configuration

Hide

Permalink

Christophe DENEUX added a comment - Wed, 28 May 2014 - 16:47:39 +0200

Reopen to write the user documentation

Show

Christophe DENEUX added a comment - Wed, 28 May 2014 - 16:47:39 +0200 Reopen to write the user documentation

Hide

Permalink

Christophe DENEUX added a comment - Wed, 28 May 2014 - 16:46:25 +0200

The last step (svn#36112 A container can be detached from a topology) resolves this issue in the trunk

Show

Christophe DENEUX added a comment - Wed, 28 May 2014 - 16:46:25 +0200 The last step (svn#36112 A container can be detached from a topology) resolves this issue in the trunk

Hide

Permalink

Christophe DENEUX added a comment - Thu, 10 Apr 2014 - 11:14:36 +0200

svn#36069: A container moved to another topology restarts with this target topology (not with its initial topology)

Show

Christophe DENEUX added a comment - Thu, 10 Apr 2014 - 11:14:36 +0200 svn#36069: A container moved to another topology restarts with this target topology (not with its initial topology)

Hide

Permalink

Christophe DENEUX added a comment - Fri, 4 Apr 2014 - 10:45:30 +0200

svn#36057: the topology is dynamic. A container can be moved from a standalone topology to another topology.

Next steps:

Check the use case: a container member of a sub-domain with several nodes is moved to another topology
A container moved to another topology must restart with this target topology (not with its initial topology)

Show

Christophe DENEUX added a comment - Fri, 4 Apr 2014 - 10:45:30 +0200 svn#36057: the topology is dynamic. A container can be moved from a standalone topology to another topology. Next steps:

Check the use case: a container member of a sub-domain with several nodes is moved to another topology
A container moved to another topology must restart with this target topology (not with its initial topology)

Hide

Permalink

Christophe DENEUX added a comment - Thu, 16 Jan 2014 - 15:37:03 +0100

svn #35908 reworks the configuration service to improve the configuration management and to introduce the initialization of the topology against an existing dynamic topology stored in the registry

Show

Christophe DENEUX added a comment - Thu, 16 Jan 2014 - 15:37:03 +0100 svn #35908 reworks the configuration service to improve the configuration management and to introduce the initialization of the topology against an existing dynamic topology stored in the registry

Hide

Permalink

Christophe DENEUX added a comment - Mon, 16 Dec 2013 - 16:29:30 +0100

Depends on the registry externalization because now the topology will be shared through the registry

Show

Christophe DENEUX added a comment - Mon, 16 Dec 2013 - 16:29:30 +0100 Depends on the registry externalization because now the topology will be shared through the registry

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Mon, 16 Dec 2013 - 16:11:27 +0100

Updated:

Mon, 2 Jun 2014 - 11:06:10 +0200

Resolved:

Mon, 2 Jun 2014 - 11:06:10 +0200

Petals ESB Container

Make the topology dynamic

Details

Issue Links

Activity

People

Dates