bvmhost-a64 for rdu3

Here's the 4 bvmhost's for rdu3 + one staging one.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi
2025-06-23 14:20:42 -07:00
parent b7bd7b0e35
commit 63b3d333d6
8 changed files with 340 additions and 0 deletions

View File

@@ -250,6 +250,10 @@ bvmhost-a64-01.iad2.fedoraproject.org
bvmhost-a64-02.iad2.fedoraproject.org
bvmhost-a64-03.iad2.fedoraproject.org
bvmhost-a64-04.iad2.fedoraproject.org
bvmhost-a64-01.rdu3.fedoraproject.org
bvmhost-a64-02.rdu3.fedoraproject.org
bvmhost-a64-03.rdu3.fedoraproject.org
bvmhost-a64-04.rdu3.fedoraproject.org
# These are lenovo emags in IAD2
bvmhost-a64-01.stg.iad2.fedoraproject.org
# ppc
@@ -262,12 +266,17 @@ bvmhost-p09-01.stg.iad2.fedoraproject.org
[buildvmhost_rdu3]
bvmhost-p10-01.rdu3.fedoraproject.org
bvmhost-a64-01.rdu3.fedoraproject.org
bvmhost-a64-02.rdu3.fedoraproject.org
bvmhost-a64-03.rdu3.fedoraproject.org
bvmhost-a64-04.rdu3.fedoraproject.org
[buildvmhost_stg_iad2]
bvmhost-a64-01.stg.iad2.fedoraproject.org
bvmhost-p09-01.stg.iad2.fedoraproject.org
[buildvmhost_stg_rdu3]
bvmhost-a64-01.stg.rdu3.fedoraproject.org
[buildhw]
# mt snow

View File

@@ -0,0 +1,56 @@
---
br0_ipv4_ip: 10.16.170.11
br0_ipv4_gw: 10.16.170.254
br0_ipv4_nm: 24
datacenter: rdu3
dns1: 10.16.163.33
dns2: 10.16.163.34
dns_search1: "rdu3.fedoraproject.org"
dns_search2: "fedoraproject.org"
has_ipv4: yes
mac0: d8:5e:d3:e6:20:b0
mac1: d8:5e:d3:e6:20:b1
mac2: b8:ce:f6:51:94:50
mac3: b8:ce:f6:51:94:50
network_connections:
# Bridge profile
- name: br0
state: up
type: bridge
mtu: 9000
autoconnect: yes
ip:
address:
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
gateway4: "{{ br0_ipv4_gw }}"
# Bond profile
- name: bond0
type: bond
interface_name: bond0
mtu: 9000
controller: br0
bond:
mode: 802.3ad
# Port profile for the 1st Ethernet device
- name: bond0-port1
mac: "{{ mac2 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
# Port profile for the 2nd Ethernet device
- name: bond0-port2
mac: "{{ mac3 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
nrpe_procs_crit: 4500
nrpe_procs_warn: 4000

View File

@@ -0,0 +1,56 @@
---
br0_ipv4_ip: 10.16.170.12
br0_ipv4_gw: 10.16.170.254
br0_ipv4_nm: 24
datacenter: rdu3
dns1: 10.16.163.33
dns2: 10.16.163.34
dns_search1: "rdu3.fedoraproject.org"
dns_search2: "fedoraproject.org"
has_ipv4: yes
mac0: d8:5e:d3:e6:25:a0
mac1: d8:5e:d3:e6:25:a1
mac2: b8:ce:f6:51:8c:e0
mac3: b8:ce:f6:51:8c:e0
network_connections:
# Bridge profile
- name: br0
state: up
type: bridge
mtu: 9000
autoconnect: yes
ip:
address:
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
gateway4: "{{ br0_ipv4_gw }}"
# Bond profile
- name: bond0
type: bond
interface_name: bond0
mtu: 9000
controller: br0
bond:
mode: 802.3ad
# Port profile for the 1st Ethernet device
- name: bond0-port1
mac: "{{ mac2 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
# Port profile for the 2nd Ethernet device
- name: bond0-port2
mac: "{{ mac3 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
nrpe_procs_crit: 4500
nrpe_procs_warn: 4000

View File

@@ -0,0 +1,56 @@
---
br0_ipv4_ip: 10.16.170.13
br0_ipv4_gw: 10.16.170.254
br0_ipv4_nm: 24
datacenter: rdu3
dns1: 10.16.163.33
dns2: 10.16.163.34
dns_search1: "rdu3.fedoraproject.org"
dns_search2: "fedoraproject.org"
has_ipv4: yes
mac0: d8:5e:d3:e6:23:00
mac1: d8:5e:d3:e6:23:01
mac2: b8:ce:f6:51:8c:e4
mac3: b8:ce:f6:51:8c:e5
network_connections:
# Bridge profile
- name: br0
state: up
type: bridge
mtu: 9000
autoconnect: yes
ip:
address:
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
gateway4: "{{ br0_ipv4_gw }}"
# Bond profile
- name: bond0
type: bond
interface_name: bond0
mtu: 9000
controller: br0
bond:
mode: 802.3ad
# Port profile for the 1st Ethernet device
- name: bond0-port1
mac: "{{ mac2 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
# Port profile for the 2nd Ethernet device
- name: bond0-port2
mac: "{{ mac3 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
nrpe_procs_crit: 4500
nrpe_procs_warn: 4000

View File

@@ -0,0 +1,56 @@
---
br0_ipv4_ip: 10.16.170.14
br0_ipv4_gw: 10.16.170.254
br0_ipv4_nm: 24
datacenter: rdu3
dns1: 10.16.163.33
dns2: 10.16.163.34
dns_search1: "rdu3.fedoraproject.org"
dns_search2: "fedoraproject.org"
has_ipv4: yes
mac0: d8:5e:d3:e6:25:80
mac1: d8:5e:d3:e6:25:81
mac2: b8:ce:f6:51:37:7c
mac3: b8:ce:f6:51:37:7d
network_connections:
# Bridge profile
- name: br0
state: up
type: bridge
mtu: 9000
autoconnect: yes
ip:
address:
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
gateway4: "{{ br0_ipv4_gw }}"
# Bond profile
- name: bond0
type: bond
interface_name: bond0
mtu: 9000
controller: br0
bond:
mode: 802.3ad
# Port profile for the 1st Ethernet device
- name: bond0-port1
mac: "{{ mac2 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
# Port profile for the 2nd Ethernet device
- name: bond0-port2
mac: "{{ mac3 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
nrpe_procs_crit: 4500
nrpe_procs_warn: 4000

View File

@@ -0,0 +1,56 @@
---
br0_ipv4_ip: 10.16.170.11
br0_ipv4_gw: 10.16.170.254
br0_ipv4_nm: 24
datacenter: rdu3
dns1: 10.16.163.33
dns2: 10.16.163.34
dns_search1: "rdu3.fedoraproject.org"
dns_search2: "fedoraproject.org"
has_ipv4: yes
mac0: d8:5e:d3:e6:25:80
mac1: d8:5e:d3:e6:25:81
mac2: b8:ce:f6:51:37:7c
mac3: b8:ce:f6:51:37:7d
network_connections:
# Bridge profile
- name: br0
state: up
type: bridge
mtu: 9000
autoconnect: yes
ip:
address:
- "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
dhcp4: no
dns:
- "{{ dns1 }}"
- "{{ dns2 }}"
dns_search:
- "{{ dns_search1 }}"
- "{{ dns_search2 }}"
gateway4: "{{ br0_ipv4_gw }}"
# Bond profile
- name: bond0
type: bond
interface_name: bond0
mtu: 9000
controller: br0
bond:
mode: 802.3ad
# Port profile for the 1st Ethernet device
- name: bond0-port1
mac: "{{ mac2 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
# Port profile for the 2nd Ethernet device
- name: bond0-port2
mac: "{{ mac3 }}"
type: ethernet
controller: bond0
state: up
mtu: 9000
nrpe_procs_crit: 4500
nrpe_procs_warn: 4000

View File

@@ -837,6 +837,7 @@ bvmhost-x86-05.stg.iad2.fedoraproject.org
bvmhost-p09-01.stg.iad2.fedoraproject.org
bvmhost-s390x-01.stg.s390.fedoraproject.org
bvmhost-a64-01.stg.iad2.fedoraproject.org
bvmhost-a64-01.stg.rdu3.fedoraproject.org
bvmhost-x86-01.stg.rdu3.fedoraproject.org
bvmhost-x86-02.stg.rdu3.fedoraproject.org
bvmhost-x86-03.stg.rdu3.fedoraproject.org

View File

@@ -1112,3 +1112,53 @@ host ocp03 {
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
# These are for aarch64 boxes to initially provision on their 1g interfaces
host bvmhost-a64-01-provision {
hardware ethernet d8:5e:d3:e6:20:b0;
fixed-address 10.16.163.150;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host bvmhost-a64-02-provision {
hardware ethernet D8:5E:D3:E6:25:A0;
fixed-address 10.16.163.151;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host bvmhost-a64-03-provision {
hardware ethernet D8:5E:D3:E6:23:00;
fixed-address 10.16.163.152;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host bvmhost-a64-04-provision {
hardware ethernet d8:5e:d3:e6:25:80;
fixed-address 10.16.163.153;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host buildhw-a64-01-provision {
hardware ethernet D8:5E:D3:E6:24:34;
fixed-address 10.16.163.154;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host buildhw-a64-02-provision {
hardware ethernet D8:5E:D3:E6:21:A4;
fixed-address 10.16.163.155;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}
host bvmhost-a64-01-stg-provision {
hardware ethernet D8:5E:D3:E6:25:98;
fixed-address 10.16.163.156;
next-server 10.16.163.10;
option routers 10.16.163.254;
option subnet-mask 255.255.255.0;
}