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@christian-reiss.de /"\ ASCII Ribbon
support@alpha-labs.net \ / Campaign
X against HTML
WEB alpha-labs.net / \ in eMails
GPG Retrieval
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgpg.christian-reiss.de&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C10740de9320c48fbdc1f08d7669b31e3%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637090689055392493&sdata=01npgnFxYPrXvTPpM6EqHiWTlxrBYHAO7E4m4CYVg8c%3D&reserved=0
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.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement:
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fsite%2Fprivacy-policy%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C10740de9320c48fbdc1f08d7669b31e3%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637090689055402486&sdata=iZ7TOgwp94a7ehjBiPFthu7RLfyei%2BPXWf2%2BIKulgE8%3D&reserved=0
oVirt Code of Conduct:
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C10740de9320c48fbdc1f08d7669b31e3%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637090689055402486&sdata=B2zYZkSFsTEoGIMyvbS%2FsWGBkpgl0NeCpkWg9u7rHYI%3D&reserved=0
List Archives:
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FEGET3LTPKJNOURRBURS65MT76LMT6DK5%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C10740de9320c48fbdc1f08d7669b31e3%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637090689055402486&sdata=K4HNHfG1xXAN%2FCtNX2DlHyrQ4OWhIXOigdz6fFBm1Ws%3D&reserved=0