forked from ksator/netbox_automation
-
Notifications
You must be signed in to change notification settings - Fork 0
/
variables.yml.orig
214 lines (202 loc) · 6.02 KB
/
variables.yml.orig
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
---
# Edit this file to define the details to configure on Netbox
# netbox server ip @
ip: 192.168.134.178
# netbox user token you want to use
token: 'b2d4afa62b3a78f51604feb713da5230a3bf7726'
# netbox tenants you want to create. please create one single tenant.
tenants:
- evpn-vxlan-demo
# netbox sites you want to create. the sites are assigned to the tenant.
sites:
- dc1
# netbox device-roles you want to create
device-roles:
- "junos-spine"
- "junos-leaf"
# device-types qfx5100-48s-6q and qfx10002-36q are automatically created.
# interface_templates are automatically created for device-types qfx5100-48s-6q and qfx10002-36q
# power_port_templates are automatically created for device-types qfx5100-48s-6q and qfx10002-36q
# Juniper Junos platform is automatically created with a junos napalm_driver
# prefix roles you want to create
prefix_roles:
- out_of_band_management
- devices_interconnection
# prefixes you want to create.
# These prefixes are assigned to the tenant.
prefixes:
- prefix: 100.0.0.0/24
role: devices_interconnection
- prefix: 172.25.90.0/24
role: out_of_band_management
# devices you want to create. the devices are assigned to the tenant.
devices:
- name: QFX5110-32Q-169
device_type: qfx5110-32q
device_role: junos-spine
site: dc1
- name: QFX5110-32Q-170
device_type: qfx5110-32q
device_role: junos-spine
site: dc1
- name: QFX5110-32Q-171
device_type: qfx5110-32q
device_role: junos-spine
site: dc1
- name: QFX5110-32Q-172
device_type: qfx5110-32q
device_role: junos-leaf
site: dc1
- name: QFX5110-32Q-174
device_type: qfx5110-32q
device_role: junos-leaf
site: dc1
- name: QFX5110-32Q-175
device_type: qfx5110-32q
device_role: junos-leaf
site: dc1
- name: QFX5110-32Q-188
device_type: qfx5110-32q
device_role: junos-leaf
site: dc1
- name: QFX5110-32Q-189
device_type: qfx5110-32q
device_role: junos-leaf
site: dc1
# management ip addresses you want to create. the IP addresses are assigned to the tenant.
management_addresses:
- ip: 172.25.45.169
device: QFX5110-32Q-169
interface: em0
mgmt_only: True
- ip: 172.25.45.170
device: QFX5110-32Q-170
interface: em0
mgmt_only: True
- ip: 172.25.45.171
device: QFX5110-32Q-171
interface: em0
mgmt_only: True
- ip: 172.25.45.172
device: QFX5110-32Q-172
interface: em0
mgmt_only: True
- ip: 172.25.45.174
device: QFX5110-32Q-174
interface: em0
mgmt_only: True
- ip: 172.25.45.175
device: QFX5110-32Q-175
interface: em0
mgmt_only: True
- ip: 172.25.45.188
device: QFX5110-32Q-188
interface: em0
mgmt_only: True
- ip: 172.25.45.189
device: QFX5110-32Q-189
interface: em0
mgmt_only: True
# Other ip addresses you want to create. the IP addresses are assigned to the tenant.
ip_addresses:
- ip: 100.169.0.1/16
device: QFX5110-32Q-169
interface: xe-0/0/5:0
- ip: 100.170.0.1/16
device: QFX5110-32Q-170
interface: xe-0/0/5:0
- ip: 100.171.0.1/16
device: QFX5110-32Q-171
interface: xe-0/0/5:0
- ip: 100.172.0.1/16
device: QFX5110-32Q-172
interface: xe-0/0/3:0
- ip: 100.174.0.1/16
device: QFX5110-32Q-174
interface: xe-0/0/3:0
- ip: 100.175.0.1/16
device: QFX5110-32Q-175
interface: xe-0/0/3:0
- ip: 100.188.0.1/16
device: QFX5110-32Q-188
interface: xe-0/0/3:0
- ip: 100.189.0.1/16
device: QFX5110-32Q-189
interface: xe-0/0/3:0
# define how the interfaces are connected (physical topology).
interface_connections:
- device_a: QFX5110-32Q-169
interface_a: et-0/0/0
device_b: QFX5110-32Q-172
interface_b: et-0/0/0
connection_status: Connected
- device_a: QFX5110-32Q-169
interface_a: et-0/0/1
device_b: QFX5110-32Q-174
interface_b: et-0/0/0
connection_status: Connected
- device_a: QFX5110-32Q-169
interface_a: et-0/0/2
device_b: QFX5110-32Q-175
interface_b: et-0/0/0
connection_status: Connected
- device_a: QFX5110-32Q-169
interface_a: et-0/0/3
device_b: QFX5110-32Q-188
interface_b: et-0/0/0
connection_status: Connected
- device_a: QFX5110-32Q-169
interface_a: et-0/0/4
device_b: QFX5110-32Q-189
interface_b: et-0/0/0
connection_status: Connected
- device_a: QFX5110-32Q-170
interface_a: et-0/0/0
device_b: QFX5110-32Q-172
interface_b: et-0/0/1
connection_status: Connected
- device_a: QFX5110-32Q-170
interface_a: et-0/0/1
device_b: QFX5110-32Q-174
interface_b: et-0/0/1
connection_status: Connected
- device_a: QFX5110-32Q-170
interface_a: et-0/0/2
device_b: QFX5110-32Q-175
interface_b: et-0/0/1
connection_status: Connected
- device_a: QFX5110-32Q-170
interface_a: et-0/0/3
device_b: QFX5110-32Q-188
interface_b: et-0/0/1
connection_status: Connected
- device_a: QFX5110-32Q-170
interface_a: et-0/0/4
device_b: QFX5110-32Q-189
interface_b: et-0/0/1
connection_status: Connected
- device_a: QFX5110-32Q-171
interface_a: et-0/0/0
device_b: QFX5110-32Q-172
interface_b: et-0/0/2
connection_status: Connected
- device_a: QFX5110-32Q-171
interface_a: et-0/0/1
device_b: QFX5110-32Q-174
interface_b: et-0/0/2
connection_status: Connected
- device_a: QFX5110-32Q-171
interface_a: et-0/0/2
device_b: QFX5110-32Q-175
interface_b: et-0/0/2
connection_status: Connected
- device_a: QFX5110-32Q-171
interface_a: et-0/0/3
device_b: QFX5110-32Q-188
interface_b: et-0/0/2
connection_status: Connected
- device_a: QFX5110-32Q-171
interface_a: et-0/0/4
device_b: QFX5110-32Q-189
interface_b: et-0/0/2
connection_status: Connected