Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.0
-
Fix Version/s: 4.2.0
-
Component/s: Topology/network
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Blocker [ 1 ] | |
| Description |
The topology mode 'standalone' has no real sens, expect to save system resources not starting all Fractal's components as the remote transporter.
It is better to have a Fractal's components launcher that starts Fractal components according to the content of the topology. |
The topology mode 'standalone' has no real sens, expect to save system resources not starting all Fractal's components as the remote transporter.
It is better to have a Fractal's components launcher that starts Fractal components according to the content of the topology. So the topology mode 'standalone' can be removed. |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Description |
The topology mode 'standalone' has no real sens, expect to save system resources not starting all Fractal's components as the remote transporter.
It is better to have a Fractal's components launcher that starts Fractal components according to the content of the topology. So the topology mode 'standalone' can be removed. |
The topology mode 'standalone' has no real sens, expect to save system resources not starting all Fractal's components as the remote transporter.
It is better to have a Fractal's components launcher that starts Fractal components according to the content of the topology. So the topology mode 'standalone' can be removed. See PETALSESBCONT-221 |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 4.2.0 [ 10356 ] |