Petals ESB Container

During container shutdown, keep endpoints in registry and container in topology

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.0
  • Fix Version/s: 5.0.1
  • Component/s: Registry, Topology/network
  • Security Level: Public
  • Description:
    Hide

    The endpoint directory and the topology are meant to reflect the state of the bus/domain that is expected by the administrators of a bus, and not simply the current state of online containers.

    This is justified for several reasons:

    • they (directory and topology) should not behave differently if a container is down for maintenance or because of a problem
    • leaving a topology is an administrative action and not simply the result of stopping a container (i.e., an admin should explicitly detach a container from a topology for it to be effective).

    Hence, the only reason why we remove endpoints from the endpoint directory (apart from stopping a SU of course) and remove a container from a topology is the detachment of a container from said topology.
    Another more technical reason is when a container is restarted in order to ensure coherence of the endpoint directory (see PETALSESBCONT-416).

    Show
    The endpoint directory and the topology are meant to reflect the state of the bus/domain that is expected by the administrators of a bus, and not simply the current state of online containers. This is justified for several reasons:
    • they (directory and topology) should not behave differently if a container is down for maintenance or because of a problem
    • leaving a topology is an administrative action and not simply the result of stopping a container (i.e., an admin should explicitly detach a container from a topology for it to be effective).
    Hence, the only reason why we remove endpoints from the endpoint directory (apart from stopping a SU of course) and remove a container from a topology is the detachment of a container from said topology. Another more technical reason is when a container is restarted in order to ensure coherence of the endpoint directory (see PETALSESBCONT-416).
  • Environment:
    -

Issue Links

Activity

Victor NOËL made changes - Wed, 18 May 2016 - 14:11:32 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Wed, 18 May 2016 - 14:12:08 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Wed, 18 May 2016 - 14:13:28 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.1 [ 10579 ]
Resolution Fixed [ 1 ]
Victor NOËL made changes - Wed, 18 May 2016 - 14:13:50 +0200
Link This issue blocks PETALSESBCONT-416 [ PETALSESBCONT-416 ]
Christophe DENEUX made changes - Thu, 26 May 2016 - 09:32:54 +0200
Link This issue blocks PETALSREGOVER-15 [ PETALSREGOVER-15 ]

People

Dates

  • Created:
    Wed, 18 May 2016 - 14:11:24 +0200
    Updated:
    Thu, 26 May 2016 - 09:32:54 +0200
    Resolved:
    Wed, 18 May 2016 - 14:13:28 +0200