Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt network to ScaleUp BER3 datacenter #86

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Adapt network to ScaleUp BER3 datacenter #86

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fdad326
Add new network config for ScaleUp BER3
fzakfeld Dec 18, 2024
625f671
Clarify Purpose
fzakfeld Dec 18, 2024
5877835
Fix NAT Addresses
fzakfeld Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## Purpose of this repository

This Git repository documents, configures and automates the management and setup of the Sovereign Cloud Stack hardware environment.
This environment is build in the context of the VP18 project workpackage and in running at a colocation of [JH Computers](https://jh-computers.de/).
This environment is build in the context of the VP18 project workpackage and in running at a colocation of [ScaleUp Technologies](https://scaleuptech.com).
fzakfeld marked this conversation as resolved.
Show resolved Hide resolved

The main goals of this environment are:

Expand Down
62 changes: 32 additions & 30 deletions documentation/System_Networks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,17 @@ Domain naming scheme: `<hostname>.<net>.landscape.scs.community`.
With the exception of the networks marked with Uplink “Yes”, no host in the listed networks
has direct access to the Internet. Services that are deployed on the manager hosts must be used for DNS, NTP, HTTP and HTTPS.

| Networkname | Network | Router | V(x)Lan | Description | Uplink |
|--------------|-------------------|----------------|-----------|---------------------------------------------|--------|
| vpn1 | 10.10.1.0/24 | 10.10.2.1 | - | VPN transfer/client network | |
| zone1-public | 10.80.0.0/20 | 10.80.0.1 | VXLAN 80 | Provider LAN | Yes |
| zone1 | 10.10.21.0/24 | 10.10.21.1 | - | Production Node Network | |
| mgmt-p2p | 10.10.22.0/24 | 10.10.22.1 | - | Out of band for rack level | |
| mgmt | 10.10.23.0/24 | 10.10.23.1 | VLAN 23 | Out of band access for switches and servers | |
| lab | 10.10.24.0/24 | 10.10.24.1 | VLAN 24 | Lab Node Network | |
| datacenter | 192.168.104.40/29 | 192.168.104.41 | - | Internet Uplink Datacenter | Yes |
| mgmt-docker | 172.16.0.0/12 | | - | Network used for Docker containers in mgmt | Yes |
| Networkname | Network | Router | V(x)Lan | Description | Uplink |
| ------------ | ------------------------- | ---------- | -------- | ------------------------------------------- | ------ |
| vpn1 | 10.10.1.0/24 | 10.10.2.1 | - | VPN transfer/client network | |
| zone1-public | 10.80.0.0/20 | 10.80.0.1 | VXLAN 80 | Provider LAN | Yes |
| zone1 | 10.10.21.0/24 | 10.10.21.1 | - | Production Node Network | |
| mgmt-p2p | 10.10.22.0/24 | 10.10.22.1 | - | Out of band for rack level | |
| mgmt | 10.10.23.0/24 | 10.10.23.1 | VLAN 23 | Out of band access for switches and servers | |
| lab | 10.10.24.0/24 | 10.10.24.1 | VLAN 24 | Lab Node Network | |
| datacenter | 10.202.0.0/24 | 10.202.0.1 | - | Internet Uplink Datacenter | Yes |
| datacenter | 2a00:12e8:701:1e:ec4::/64 | SLAAC | - | Internet Uplink Datacenter (IPv6) | Yes |
| mgmt-docker | 172.16.0.0/12 | | - | Network used for Docker containers in mgmt | Yes |

To provide connections, two auxiliary scripts are integrated which ensure that access is configured, filtered and translated (NAT).

Expand All @@ -37,7 +38,7 @@ The containing ips are not statically assigned to a particular host.
| prod1 | 10.10.21.202 | | Controller Kubernetes, Static |
| prod1 | 10.10.21.203 | 10.10.21.220 | Kubernetes Loadbalancer IPs, Dynamic |
| prod1 | 10.10.21.221 | 10.10.21.250 | Loadbalancer URLs for Openstack, Dynamic |
| datacenter | 192.168.104.42 | 192.168.104.43 | IPs for Basition Host Uplinks |
| datacenter | 10.202.0.4 | 10.202.0.254 | IPs for Basition Host Uplinks |


## Port Forwarding Access
Expand All @@ -47,29 +48,30 @@ The containing ips are not statically assigned to a particular host.

* MAC: 0c:c4:7a:fe:e6:6d
* Firewall IP (NAT):
* IP: 188.244.104.28 (old setup @JH computers)
* Ports:
* SSH: 22/TCP (internal 22/TCP)
* Wireguard: 51820/UDP (internal 51820/UDP)
* Internal interface (old setup @JH computers)
* IP: 45.139.159.109 (BINAT -> 10.202.0.30)
* Internal interface
* Interface: eno2 (Remote OSBA-DL-S7-L)
* Internal IP: 192.168.104.43
* Subnet: 255.255.255.248 (/29)
* Gateway: 192.168.104.41
* DNS: 192.168.104.41
* Internal IP: 10.202.0.30
* Subnet: 255.255.255.0 (/24)
* Gateway: 10.202.0.1
* IPv6: 2a00:12e8:701:1e:ec4:7aff:fefe:e66d
* DNS: 85.158.4.230, 93.92.134.126
* Ports:
* SSH: 22/TCP from 0.0.0.0/0 + ::/0
* Wireguard: 51820/UDP from 0.0.0.0/0 + ::/0

### st01-mgmt-r01-u31

* MAC: 0c:c4:7a:fe:e6:75
* Firewall IP (NAT):
* IP: 153.92.93.119 (old setup @JH computers)
* Ports:
* SSH: 41115/TCP (internal 22/TCP)
* Wireguard: 51820/UDP (internal 51820/UDP)
* Internal interface (old setup @JH computers)
* IP: 45.139.159.110 (BINAT -> 10.202.0.31)
* Internal interface
* Interface: eno2 (Remote Temp-Downlink-S…)
* Internal IP: 192.168.104.42
* Subnet: 255.255.255.248 (/29)
* Gateway: 192.168.104.41
* DNS: 192.168.104.41

* Internal IP: 10.202.0.31
* Subnet: 255.255.255.0 (/24)
* Gateway: 10.202.0.1
* IPv6: 2a00:12e8:701:1e:ec4:7aff:fefe:e675
* DNS: 85.158.4.230, 93.92.134.126
* Ports:
* SSH: 22/TCP from 0.0.0.0/0 + ::/0
* Wireguard: 51820/UDP from 0.0.0.0/0 + ::/0
Loading