|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5014 | minor | always | 04-02-12 15:12 | 06-13-12 16:25 | |
|
|
|||||
| Reporter: | rickHigh | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.28 | ||
|
|
|||||
| Summary: | 0005014: CONFIG EC2: need ability to connect to Resin using public IP only. | ||||
| Description: |
ext:{externalIP} forces ServerId to be passed for IP public/private discovery. Without this setting, server would need to be started from the CMD line as follows: sudo resinctl start -server app-1 or you would need to modify /etc/init.d/resin to pass the server id We don't want this. We want the ability to pass serverId via resin.xml like the homeCluster is configured. This requires a Resin code change to resin.xml similar to a change for homeCluster support. resin.xml near homeCluster: <serverId>${triadServerId}</serverId> resin.properties: # Assign a server id to this instance. # This is needed for EC2 environments when public IP is external Elastic IP #triadServerId=app-0 Assertions: homeCluster and triadServerId should not be both set. If triadServerId is null or empty, then there is no server id unless it is passed from the command line. Command line server id should override the property in the config. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||