Details
Improvement Request
Resolved
Major
-
- Environment:
- Debian
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Blocker [ 1 ] | |
| Description |
Petals Registry Overlay is distributed as a ZIP archive ( 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 ( 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 |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Component/s | Packaging [ 10280 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.0.0 [ 10430 ] | |
| Resolution | Fixed [ 1 ] |
| Link |
This issue blocks |
| Link |
This issue depends on |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
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.