Hey folks,
for production use quality it is recommended to have backend (storage)
and front end seperated. Let' assume:
- 85.0.0.0/24 public IP block
- 10.100.0.0/24 private IPs for DC internal usage
- 10.200.0.0/24 private IPs for storage only LAN
and running, as per recommendation 3 nodes:
- node01:
- fqdn:
node01.dc-example.com
- fqdn storage:
node02.storage.example.com
- no public IP
- 10.100.0.1 primary IP
- 10.200.0.1 storage IP
- node02:
- fqdn:
node02.dc-example.com
- fqdn storage:
node02.storage.example.com
- no public IP
- 10.100.0.2 primary IP
- 10.200.0.2 storage IP
- node03:
- fqdn:
node03.dc-example.com
- fqdn storage:
node02.storage.example.com
- no public IP
- 10.100.0.3 primary IP
- 10.200.0.3 storage IP
The storage network is its own physical network with 10gig that only
connects those three servers. How can I specify which IP to use for
storage, which for frontend traffic?
I am assuming this as the controller and all admins should be able to
reach the nodes via frontend, which is not the storage one.
Okay, I am lost. Whats the real solution here?
Or is "frontend" no-ip, just VM traffic and "backend" is the 10gig
storage "Only" where all the FQDN reside?
Thanks for clarification,
-Chris.
--
Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon
support(a)alpha-labs.net \ / Campaign
X against HTML
WEB
alpha-labs.net / \ in eMails
GPG Retrieval
https://gpg.christian-reiss.de
GPG ID ABCD43C5, 0x44E29126ABCD43C5
GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5
"It's better to reign in hell than to serve in heaven.",
John Milton, Paradise lost.