Anonymous | Login | Signup for a new account | 05-07-2024 20:14 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0006296 | [Resin] | minor | always | 11-20-19 00:19 | 12-13-19 16:56 | ||||
Reporter | nam | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | no change required | ||||||
Status | closed | Product Version | 4.0.63 | ||||||
Summary | 0006296: dynamic elastic servers should respect allow-non-reserved-ip configuration | ||||||||
Description |
(rep by Y. Guedj) Set the cluster in a hub-and-spoke topology which, unfortunately, we could not do due to the triad requesting a private IP for the machines on the spoke. None of our servers are AWS elastic servers, they’re all dedicated servers and therefore have a public IP. <server-multi id-prefix="app-" address-list="${app_servers}" port="6800" allow-non-reserved-ip="true"/> |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |