Details
-
Type:
Improvement Request
-
Status:
New
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: 3.1.1, 4.0.0
-
Fix Version/s: None
-
Component/s: JMX
-
Security Level: Public
-
- Environment:
- Webconsole 2.0.4/2.1-SNAPSHOT and its associated Petals 3.1.1/3.2-SNAPSHOT
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue depends on |
| Summary | Synchronization improvement | Use IP address for hostname between a Petals ESB client and a Petals ESB container |
| Assignee | Admin [ rnaudin ] | |
| Environment | Wenconsole 2.0.4/2.1-SNAPSHOT and its associated Petals 3.1.1/3.2-SNAPSHOT | Webconsole 2.0.4/2.1-SNAPSHOT and its associated Petals 3.1.1/3.2-SNAPSHOT |
| Priority | Blocker [ 1 ] | |
| Description |
Allow to recover IP address if for example a hostname "linux-node1" is given for "host" parameter in topology. Because frequently in production environment the name resolution isn't possible from the Webconsole, give the possibility to perform name resolution form Petals ESB.
Or return hostname and IP address when you recover the topology from a node. |
When getting a hostname of a Petals ESB container from a Petals ESB JMX client, the value set for the attribute '{{host}}' of the topology is returned.
In few case, a hostname instead of an IP address is set to '{{host}}' but it is resolvable only by the host running the Petals ESB container (for example, the hostname is declared into '/etc/hosts'). So, on a Petals ESB JMX client side, we can't use this IP address. So, the improvement could be: * only the IP address is exchange between Petals ESB container and Petals ESB JMX client, * Petals ESB JMX clients are in charge of resolving IP address into a hostname if possible. |
| Component/s | JMX [ 10256 ] |
| Description |
When getting a hostname of a Petals ESB container from a Petals ESB JMX client, the value set for the attribute '{{host}}' of the topology is returned.
In few case, a hostname instead of an IP address is set to '{{host}}' but it is resolvable only by the host running the Petals ESB container (for example, the hostname is declared into '/etc/hosts'). So, on a Petals ESB JMX client side, we can't use this IP address. So, the improvement could be: * only the IP address is exchange between Petals ESB container and Petals ESB JMX client, * Petals ESB JMX clients are in charge of resolving IP address into a hostname if possible. |
When getting a hostname of a Petals ESB container from a Petals ESB JMX client, the value set for the attribute '{{host}}' of the topology is returned.
In few case, a hostname instead of an IP address is set to '{{host}}' but it is resolvable only by the host running the Petals ESB container (for example, the hostname is declared into '/etc/hosts', or see So, the improvement could be: * only the IP address is exchange between Petals ESB container and Petals ESB JMX client, * Petals ESB JMX clients are in charge of resolving IP address into a hostname if possible. |
The 32 JIRa issue of Webconsole, allows us to identify this Petals ESB improvement.