mirror of
https://github.com/linux-system-roles/network.git
synced 2026-07-28 21:40:43 +00:00
6fdf07fff1
This way one will be able to reliably detect when the example playbook was forgotten to be upated with correct addresses, as the RFC 5737 addresses are never used in production (the original RFC 1918 ones often are). https://github.com/linux-system-roles/network/issues/5
35 lines
767 B
YAML
35 lines
767 B
YAML
---
|
|
- hosts: network-test
|
|
vars:
|
|
network_connections:
|
|
|
|
# Create a bridge profile, which is the parent of VLAN.
|
|
- name: prod2
|
|
state: up
|
|
type: bridge
|
|
interface_name: bridge2
|
|
ip:
|
|
dhcp4: no
|
|
auto6: no
|
|
|
|
# enslave an ethernet to the bridge
|
|
- name: prod2-slave1
|
|
state: up
|
|
type: ethernet
|
|
interface_name: "{{ network_interface_name2 }}"
|
|
master: prod2
|
|
slave_type: bridge
|
|
|
|
# on top of it, create a VLAN with ID 100 and static
|
|
# addressing
|
|
- name: prod2.100
|
|
state: up
|
|
type: vlan
|
|
parent: prod2
|
|
vlan_id: 100
|
|
ip:
|
|
address:
|
|
- "192.0.2.{{ network_iphost }}/24"
|
|
|
|
roles:
|
|
- network
|