-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathludus-config.yaml
49 lines (49 loc) · 1.71 KB
/
ludus-config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
ludus:
# Create parent domain and domain controller first using ludus's primary-dc role
# Then Join machine to Tailscale network using ludus_tailscale role passing in the authkey and apikey
- vm_name: "{{ range_id }}-pdc01"
hostname: "pdc01"
template: win2016-server-x64-template
vlan: 20
ip_last_octet: 10
ram_gb: 8
cpus: 2
windows:
sysprep: true
domain:
fqdn: acme.com
role: primary-dc
roles:
- ludus_tailscale # put this as it appears in `ludus ansible roles list` THIS WILL CHANGE BASED ON WHETHER YOU ADDED THE ROLE BY CLONING THE REPO OR THROUGH ANSIBLE GALAXY COMMAND
role_vars:
tailscale_state: present
tailscale_authkey: "tskey-auth-<REDACTED_KEY>"
tailscale_api_key: "tskey-api-<REDACTED_KEY>"
# Create a linux machine in the same VLAN as the domain controller
# Remove the machine from the Tailscale network using ludus_tailscale role
- vm_name: "{{ range_id }}-linux"
hostname: "{{ range_id }}-linux"
template: debian-12-x64-server-template
vlan: 20
ip_last_octet: 1
ram_gb: 12
cpus: 6
linux: true
testing:
snapshot: false
block_internet: false
roles:
- ludus_tailscale # put this as it appears in `ludus ansible roles list` THIS WILL CHANGE BASED ON WHETHER YOU ADDED THE ROLE BY CLONING THE REPO OR THROUGH ANSIBLE GALAXY COMMAND
role_vars:
tailscale_state: absent
tailscale_authkey: "tskey-auth-<REDACTED_KEY>"
tailscale_api_key: "tskey-api-<REDACTED_KEY>"
network:
inter_vlan_default: ACCEPT
rules:
- name: Allow all from 20
vlan_src: 20
vlan_dst: all
protocol: all
ports: all
action: ACCEPT