Petals Registry Overlay

Create a Debian package to install Petals Registry Overlay

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: No version
  • Fix Version/s: 1.0.0
  • Component/s: Packaging
  • Security Level: Public
  • Description:
    Hide

    Petals Registry Overlay is distributed as a ZIP archive (PETALSREGOVER-2). Please create a Debian package to improve its integration with Linux Debian-based system.
    Requirements about the Debian package:

    • The package will be compliant with all Debian policies
    • Provide a script to automatically start/stop Petals Registry Overlay members booting the host:
      • Petals Registry Overlay members must be started before Petals ESB nodes
      • Petals Registry Overlay members must be stopped after Petals ESB nodes
    • One Petals Registry Overlay runtime can launch several Petals Registry Overlay members:
      • Several available member configurations are available into /etc/petals-esb/registry-member-available
      • Several active container configurations are availbale into /etc/petals-esb/registry-member-enabled
      • For each member configured into /etc/petals-esb/registry-member-enabled, the Petals Registry Overlay launcher uses the runtime to instantiate a member.
      • To de-activate temporary a configuration, just unlink it into /etc/petals-esb/registry-member-enabled
    Show
    Petals Registry Overlay is distributed as a ZIP archive (PETALSREGOVER-2). Please create a Debian package to improve its integration with Linux Debian-based system. Requirements about the Debian package:
    • The package will be compliant with all Debian policies
    • Provide a script to automatically start/stop Petals Registry Overlay members booting the host:
      • Petals Registry Overlay members must be started before Petals ESB nodes
      • Petals Registry Overlay members must be stopped after Petals ESB nodes
    • One Petals Registry Overlay runtime can launch several Petals Registry Overlay members:
      • Several available member configurations are available into /etc/petals-esb/registry-member-available
      • Several active container configurations are availbale into /etc/petals-esb/registry-member-enabled
      • For each member configured into /etc/petals-esb/registry-member-enabled, the Petals Registry Overlay launcher uses the runtime to instantiate a member.
      • To de-activate temporary a configuration, just unlink it into /etc/petals-esb/registry-member-enabled
  • Environment:
    Debian

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 8 Apr 2014 - 16:03:39 +0200

The Debian package was created in trunk.
No check is included to start registry members before Petals ESB nodes and to stop Petals ESB node before the registry members. Using a Petals registry overlay with several member, and Petals ESB containers configured to be connected on these different registry members is sufficient.

Show
Christophe DENEUX added a comment - Tue, 8 Apr 2014 - 16:03:39 +0200 The Debian package was created in trunk. No check is included to start registry members before Petals ESB nodes and to stop Petals ESB node before the registry members. Using a Petals registry overlay with several member, and Petals ESB containers configured to be connected on these different registry members is sufficient.

People

Dates

  • Created:
    Wed, 6 Nov 2013 - 13:39:34 +0100
    Updated:
    Wed, 21 Jan 2015 - 16:45:28 +0100
    Resolved:
    Tue, 8 Apr 2014 - 16:03:39 +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.