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
Christophe DENEUX made changes - Wed, 6 Nov 2013 - 15:47:49 +0100
Field Original Value New Value
Priority Blocker [ 1 ]
Description 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
* 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

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

Christophe DENEUX made changes - Wed, 6 Nov 2013 - 15:48:07 +0100
Priority Blocker [ 1 ] Major [ 3 ]
Christophe DENEUX made changes - Wed, 6 Nov 2013 - 15:49:16 +0100
Component/s Packaging [ 10280 ]
Christophe DENEUX made changes - Tue, 8 Apr 2014 - 11:50:49 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Tue, 8 Apr 2014 - 11:50:52 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 8 Apr 2014 - 16:03:40 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.0.0 [ 10430 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Wed, 21 Jan 2015 - 16:45:10 +0100
Link This issue blocks PETALSDISTRIB-56 [ PETALSDISTRIB-56 ]
Christophe DENEUX made changes - Wed, 21 Jan 2015 - 16:45:28 +0100
Link This issue depends on PETALSREGOVER-1 [ PETALSREGOVER-1 ]

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.