Server Binding #1

Closed
opened 2014-04-26 09:24:04 +00:00 by thorsten · 6 comments
thorsten commented 2014-04-26 09:24:04 +00:00 (Migrated from devops.tsommer.org)

Server binds on the oceanHostname configuration! Instead, it must bind to its local ip address

Server binds on the oceanHostname configuration! Instead, it must bind to its local ip address
thorsten commented 2014-06-05 11:59:04 +00:00 (Migrated from devops.tsommer.org)

Explanation: The oceanHostname configuration is for the whole data center. It should be the address for the customer (e.g. the address for the load balancing by e.g. Nginx). Instead, the binding for a single server within the data center must be the local IP address.

  • TODO: Check also the ICCCHost entry creation: Here is also the local address necessary.
**Explanation:** The oceanHostname configuration is for the whole data center. It should be the address for the customer (e.g. the address for the load balancing by e.g. Nginx). Instead, the binding for a single server within the data center must be the local IP address. - [x] **TODO:** Check also the ICCCHost entry creation: Here is also the local address necessary.
thorsten commented 2014-06-05 12:03:46 +00:00 (Migrated from devops.tsommer.org)

Note: Tools.ReadAllIPAddresses4ThisHost() determine all the local IP addresses!

Note: Tools.ReadAllIPAddresses4ThisHost() determine all the local IP addresses!
thorsten commented 2014-06-05 12:06:40 +00:00 (Migrated from devops.tsommer.org)
  • Issue: The ICCC is using the correct IP address (not oceanHostname) and the correct hostname but it uses the port from oceanHostname! This is wrong!
- [x] **Issue:** The ICCC is using the correct IP address (not oceanHostname) and the correct hostname but it uses the port from oceanHostname! This is wrong!
thorsten commented 2014-06-05 12:08:28 +00:00 (Migrated from devops.tsommer.org)
  • TODO: Provide a configuration for the desired port for all (!!!) nodes / servers.
  • TODO: Provide a cached function within Ocean's tools.
- [x] **TODO:** Provide a configuration for the desired port for all (!!!) nodes / servers. - [x] **TODO:** Provide a cached function within Ocean's tools.
thorsten commented 2014-06-05 12:12:15 +00:00 (Migrated from devops.tsommer.org)
  • Is it eventual necessary to use for the ICCC communication the OceanHostnameAndPort? Because it is necessary that all nodes are able to communicate with each other. No! Because it is fundamental that all servers are able to talk to each other. Otherwise, the whole architecture does not work.
  • Who is using OceanHostnameAndPort? At the moment: Nobody! But it would be used for e.g. generating public links etc.
- [x] Is it eventual necessary to use for the ICCC communication the OceanHostnameAndPort? Because it is necessary that all nodes are able to communicate with each other. No! Because it is fundamental that all servers are able to talk to each other. Otherwise, the whole architecture does not work. - [x] Who is using OceanHostnameAndPort? At the moment: Nobody! But it would be used for e.g. generating public links etc.
thorsten commented 2014-06-05 13:47:10 +00:00 (Migrated from devops.tsommer.org)

All tests passed :)

All tests passed :)
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Go/Ocean#1
No description provided.