Héy Habr!
Nembe hiji artikel muncul di dieu
Ieu sanés sapédah anu munggaran pikeun tugas sapertos kitu. Pilihan kahiji dilaksanakeun sababaraha taun ka pengker deui di ansible Vérsi 1.x.x. Sapédah éta jarang dipaké sahingga terus karat. Dina harti yén tugas sorangan teu timbul sakumaha mindeng versi diropéa ansible. Sarta unggal waktos Anjeun kudu ngajalankeun, ranté ragrag kaluar atawa kabayang ragrag kaluar. Sanajan kitu, bagian kahiji, generating configs, salawasna jalan pisan jelas, untungna jinja2 mesin geus lila ngadegkeun. Tapi bagian kadua - rolling kaluar configs - biasana mawa kejutan. Sarta saprak kuring kudu gulung kaluar config jarak jauh ka satengah ratus alat, sababaraha nu lokasina rébuan kilométer jauh, ngagunakeun alat ieu saeutik boring.
Di dieu kuring kudu ngaku yén kateupastian kuring paling dipikaresep perenahna di kurangna kuring familiarity kalawan ansiblebatan kakuranganana. Sareng ieu, ku jalan kitu, mangrupikeun titik anu penting. ansible mangrupakeun wewengkon lengkep misah, pangaweruh sorangan kalawan DSL sorangan (Domain Spésifik Basa), nu kudu dijaga dina tingkat yakin. Muhun, moment éta ansible Éta ngembang rada gancang, sareng tanpa merhatikeun khusus pikeun kasaluyuan mundur, éta henteu nambihan kapercayaan.
Ku alatan éta, teu jadi lila pisan versi kadua sapédah ieu dilaksanakeun. waktos Ieu on python, atawa rada dina kerangka ditulis dina python sareng pikeun python ngaranna
Jadi- Nornir mangrupa microframework ditulis dina python sareng pikeun python sarta dirancang pikeun automation. Sarua jeung dina kasus kalawan ansible, pikeun ngajawab masalah di dieu, persiapan data kompeten diperlukeun, i.e. inventory of sarwa sarta parameter maranéhna, tapi Aksara ditulis teu di DSL misah, tapi dina sarua teu pisan heubeul, tapi pohara alus p[i|i]ton.
Hayu urang tingali naon anu nganggo conto langsung di handap ieu.
Kuring boga jaringan cabang jeung sababaraha belasan kantor di sakuliah nagara. Unggal kantor boga router WAN nu terminates sababaraha saluran komunikasi ti operator béda. Protokol routing nyaéta BGP. routers Wan datangna dina dua jenis: Cisco ISG atanapi Juniper SRX.
Ayeuna tugas: anjeun kedah ngonpigurasikeun subnet khusus pikeun Panjagaan Video dina port anu misah dina sadaya router WAN jaringan cabang - Ngaiklan subnet ieu dina BGP - ngonpigurasikeun wates laju port khusus.
Mimiti, urang kedah nyiapkeun sababaraha témplat, dumasar kana konfigurasi anu bakal didamel nyalira pikeun Cisco sareng Juniper. Éta ogé perlu nyiapkeun data pikeun tiap titik sarta parameter sambungan, i.e. ngumpulkeun inventory sarua
Témplat siap pikeun Cisco:
$ cat templates/ios/base.j2
class-map match-all VIDEO_SURV
match access-group 111
policy-map VIDEO_SURV
class VIDEO_SURV
police 1500000 conform-action transmit exceed-action drop
interface {{ host.task_data.ifname }}
description VIDEOSURV
ip address 10.10.{{ host.task_data.ipsuffix }}.254 255.255.255.0
service-policy input VIDEO_SURV
router bgp {{ host.task_data.asn }}
network 10.40.{{ host.task_data.ipsuffix }}.0 mask 255.255.255.0
access-list 11 permit 10.10.{{ host.task_data.ipsuffix }}.0 0.0.0.255
access-list 111 permit ip 10.10.{{ host.task_data.ipsuffix }}.0 0.0.0.255 any
Citakan pikeun Juniper:
$ cat templates/junos/base.j2
set interfaces {{ host.task_data.ifname }} unit 0 description "Video surveillance"
set interfaces {{ host.task_data.ifname }} unit 0 family inet filter input limit-in
set interfaces {{ host.task_data.ifname }} unit 0 family inet address 10.10.{{ host.task_data.ipsuffix }}.254/24
set policy-options policy-statement export2bgp term 1 from route-filter 10.10.{{ host.task_data.ipsuffix }}.0/24 exact
set security zones security-zone WAN interfaces {{ host.task_data.ifname }}
set firewall policer policer-1m if-exceeding bandwidth-limit 1m
set firewall policer policer-1m if-exceeding burst-size-limit 187k
set firewall policer policer-1m then discard
set firewall policer policer-1.5m if-exceeding bandwidth-limit 1500000
set firewall policer policer-1.5m if-exceeding burst-size-limit 280k
set firewall policer policer-1.5m then discard
set firewall filter limit-in term 1 then policer policer-1.5m
set firewall filter limit-in term 1 then count limiter
Témplat, tangtosna, henteu kaluar tina hawa ipis. Ieu dasarna diffs antara konfigurasi gawé éta sarta sanggeus ngarengsekeun tugas dina dua routers husus model béda.
Ti témplat kami ningali yén pikeun ngajawab masalah, urang ngan butuh dua parameter pikeun Juniper na 3 parameter pikeun Cisco. ieu aranjeunna:
- lamun ngaran
- ipsufiks
- asn
Ayeuna urang kedah nyetél parameter ieu pikeun tiap alat, i.e. ngalakukeun hal anu sarua inventory.
keur inventory Urang bakal mastikeun nuturkeun dokuméntasi
nyaeta, hayu urang nyieun rorongkong file sarua:
.
├── config.yaml
├── inventory
│ ├── defaults.yaml
│ ├── groups.yaml
│ └── hosts.yaml
File config.yaml nyaéta file konfigurasi nornir standar
$ cat config.yaml
---
core:
num_workers: 10
inventory:
plugin: nornir.plugins.inventory.simple.SimpleInventory
options:
host_file: "inventory/hosts.yaml"
group_file: "inventory/groups.yaml"
defaults_file: "inventory/defaults.yaml"
Urang bakal nunjukkeun parameter utama dina file hosts.yaml, grup (bisi kuring ieu logins / sandi) di grup.yaml, sareng di standar.yaml Kami moal nunjukkeun nanaon, tapi anjeun kedah ngalebetkeun tilu minuses - nunjukkeun yén éta yaml file kosong sanajan.
Ieu sapertos host.yaml:
---
srx-test:
hostname: srx-test
groups:
- juniper
data:
task_data:
ifname: fe-0/0/2
ipsuffix: 111
cisco-test:
hostname: cisco-test
groups:
- cisco
data:
task_data:
ifname: GigabitEthernet0/1/1
ipsuffix: 222
asn: 65111
Sareng ieu grup.yaml:
---
cisco:
platform: ios
username: admin1
password: cisco1
juniper:
platform: junos
username: admin2
password: juniper2
Ieu kajadian inventory keur tugas urang. Salila initialization, parameter tina file inventory dipetakeun kana model obyék InventoryElement.
Handap spoiler mangrupa diagram model InventoryElement
print(json.dumps(InventoryElement.schema(), indent=4))
{
"title": "InventoryElement",
"type": "object",
"properties": {
"hostname": {
"title": "Hostname",
"type": "string"
},
"port": {
"title": "Port",
"type": "integer"
},
"username": {
"title": "Username",
"type": "string"
},
"password": {
"title": "Password",
"type": "string"
},
"platform": {
"title": "Platform",
"type": "string"
},
"groups": {
"title": "Groups",
"default": [],
"type": "array",
"items": {
"type": "string"
}
},
"data": {
"title": "Data",
"default": {},
"type": "object"
},
"connection_options": {
"title": "Connection_Options",
"default": {},
"type": "object",
"additionalProperties": {
"$ref": "#/definitions/ConnectionOptions"
}
}
},
"definitions": {
"ConnectionOptions": {
"title": "ConnectionOptions",
"type": "object",
"properties": {
"hostname": {
"title": "Hostname",
"type": "string"
},
"port": {
"title": "Port",
"type": "integer"
},
"username": {
"title": "Username",
"type": "string"
},
"password": {
"title": "Password",
"type": "string"
},
"platform": {
"title": "Platform",
"type": "string"
},
"extras": {
"title": "Extras",
"type": "object"
}
}
}
}
}
Modél ieu bisa kasampak saeutik ngabingungkeun, utamana dina mimitina. Dina raraga angka kaluar, mode interaktif asup ipython.
$ ipython3
Python 3.6.9 (default, Nov 7 2019, 10:44:02)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.1.1 -- An enhanced Interactive Python. Type '?' for help.
In [1]: from nornir import InitNornir
In [2]: nr = InitNornir(config_file="config.yaml", dry_run=True)
In [3]: nr.inventory.hosts
Out[3]:
{'srx-test': Host: srx-test, 'cisco-test': Host: cisco-test}
In [4]: nr.inventory.hosts['srx-test'].data
Out[4]: {'task_data': {'ifname': 'fe-0/0/2', 'ipsuffix': 111}}
In [5]: nr.inventory.hosts['srx-test']['task_data']
Out[5]: {'ifname': 'fe-0/0/2', 'ipsuffix': 111}
In [6]: nr.inventory.hosts['srx-test'].platform
Out[6]: 'junos'
Sarta pamustunganana, hayu urang ngaléngkah ka naskah sorangan. Kuring teu boga nanaon utamana bangga dieu. Kuring ngan nyokot conto siap-dijieun tina
from nornir import InitNornir
from nornir.plugins.tasks import networking, text
from nornir.plugins.functions.text import print_title, print_result
def config_and_deploy(task):
# Transform inventory data to configuration via a template file
r = task.run(task=text.template_file,
name="Base Configuration",
template="base.j2",
path=f"templates/{task.host.platform}")
# Save the compiled configuration into a host variable
task.host["config"] = r.result
# Save the compiled configuration into a file
with open(f"configs/{task.host.hostname}", "w") as f:
f.write(r.result)
# Deploy that configuration to the device using NAPALM
task.run(task=networking.napalm_configure,
name="Loading Configuration on the device",
replace=False,
configuration=task.host["config"])
nr = InitNornir(config_file="config.yaml", dry_run=True) # set dry_run=False, cross your fingers and run again
# run tasks
result = nr.run(task=config_and_deploy)
print_result(result)
Nengetan parameter dry_run = Leres dina garis obyék initialization nr.
Di dieu sarua jeung di ansible test ngajalankeun geus dilaksanakeun nu sambungan ka router dijieun, konfigurasi dirobah anyar geus disiapkeun, nu lajeng disahkeun ku alat (tapi ieu teu tangtu; eta gumantung kana rojongan alat jeung palaksanaan supir di NAPALM). , tapi konfigurasi anyar henteu langsung dilarapkeun. Pikeun pamakéan ngempur, Anjeun kudu miceun parameter dry_run atawa ngarobah nilai na palsu.
Nalika naskah dieksekusi, Nornir kaluaran log lengkep pikeun konsol.
Di handap spoiler nyaéta kaluaran tina tempur ngajalankeun dina dua routers test:
config_and_deploy***************************************************************
* cisco-test ** changed : True *******************************************
vvvv config_and_deploy ** changed : True vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv INFO
---- Base Configuration ** changed : True ------------------------------------- INFO
class-map match-all VIDEO_SURV
match access-group 111
policy-map VIDEO_SURV
class VIDEO_SURV
police 1500000 conform-action transmit exceed-action drop
interface GigabitEthernet0/1/1
description VIDEOSURV
ip address 10.10.222.254 255.255.255.0
service-policy input VIDEO_SURV
router bgp 65001
network 10.10.222.0 mask 255.255.255.0
access-list 11 permit 10.10.222.0 0.0.0.255
access-list 111 permit ip 10.10.222.0 0.0.0.255 any
---- Loading Configuration on the device ** changed : True --------------------- INFO
+class-map match-all VIDEO_SURV
+ match access-group 111
+policy-map VIDEO_SURV
+ class VIDEO_SURV
+interface GigabitEthernet0/1/1
+ description VIDEOSURV
+ ip address 10.10.222.254 255.255.255.0
+ service-policy input VIDEO_SURV
+router bgp 65001
+ network 10.10.222.0 mask 255.255.255.0
+access-list 11 permit 10.10.222.0 0.0.0.255
+access-list 111 permit ip 10.10.222.0 0.0.0.255 any
^^^^ END config_and_deploy ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
* srx-test ** changed : True *******************************************
vvvv config_and_deploy ** changed : True vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv INFO
---- Base Configuration ** changed : True ------------------------------------- INFO
set interfaces fe-0/0/2 unit 0 description "Video surveillance"
set interfaces fe-0/0/2 unit 0 family inet filter input limit-in
set interfaces fe-0/0/2 unit 0 family inet address 10.10.111.254/24
set policy-options policy-statement export2bgp term 1 from route-filter 10.10.111.0/24 exact
set security zones security-zone WAN interfaces fe-0/0/2
set firewall policer policer-1m if-exceeding bandwidth-limit 1m
set firewall policer policer-1m if-exceeding burst-size-limit 187k
set firewall policer policer-1m then discard
set firewall policer policer-1.5m if-exceeding bandwidth-limit 1500000
set firewall policer policer-1.5m if-exceeding burst-size-limit 280k
set firewall policer policer-1.5m then discard
set firewall filter limit-in term 1 then policer policer-1.5m
set firewall filter limit-in term 1 then count limiter
---- Loading Configuration on the device ** changed : True --------------------- INFO
[edit interfaces]
+ fe-0/0/2 {
+ unit 0 {
+ description "Video surveillance";
+ family inet {
+ filter {
+ input limit-in;
+ }
+ address 10.10.111.254/24;
+ }
+ }
+ }
[edit]
+ policy-options {
+ policy-statement export2bgp {
+ term 1 {
+ from {
+ route-filter 10.10.111.0/24 exact;
+ }
+ }
+ }
+ }
[edit security zones]
security-zone test-vpn { ... }
+ security-zone WAN {
+ interfaces {
+ fe-0/0/2.0;
+ }
+ }
[edit]
+ firewall {
+ policer policer-1m {
+ if-exceeding {
+ bandwidth-limit 1m;
+ burst-size-limit 187k;
+ }
+ then discard;
+ }
+ policer policer-1.5m {
+ if-exceeding {
+ bandwidth-limit 1500000;
+ burst-size-limit 280k;
+ }
+ then discard;
+ }
+ filter limit-in {
+ term 1 {
+ then {
+ policer policer-1.5m;
+ count limiter;
+ }
+ }
+ }
+ }
^^^^ END config_and_deploy ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nyumputkeun kecap akses dina ansible_vault
Dina awal artikel kuring indit saeutik overboard ansible, tapi teu kabeh nu goréng. Abdi resep pisan aranjeunna lomari wesi kawas, nu dirancang pikeun nyumputkeun informasi sénsitip kaluar tina tetempoan. Sareng sigana seueur anu perhatikeun yén urang ngagaduhan sadaya login / kecap akses pikeun sadaya router tempur sparkling dina bentuk kabuka dina file. gorups.yaml. Teu geulis, tangtu. Hayu urang ngajaga data ieu kalawan lomari wesi.
Hayu urang mindahkeun parameter tina groups.yaml ka creds.yaml, sareng énkripsi nganggo AES256 nganggo kecap akses 20 digit:
$ cd inventory
$ cat creds.yaml
---
cisco:
username: admin1
password: cisco1
juniper:
username: admin2
password: juniper2
$ pwgen 20 -N 1 > vault.passwd
ansible-vault encrypt creds.yaml --vault-password-file vault.passwd
Encryption successful
$ cat creds.yaml
$ANSIBLE_VAULT;1.1;AES256
39656463353437333337356361633737383464383231366233386636333965306662323534626131
3964396534396333363939373539393662623164373539620a346565373439646436356438653965
39643266333639356564663961303535353364383163633232366138643132313530346661316533
6236306435613132610a656163653065633866626639613537326233653765353661613337393839
62376662303061353963383330323164633162386336643832376263343634356230613562643533
30363436343465306638653932366166306562393061323636636163373164613630643965636361
34343936323066393763323633336366366566393236613737326530346234393735306261363239
35663430623934323632616161636330353134393435396632663530373932383532316161353963
31393434653165613432326636616636383665316465623036376631313162646435
Ieu nu basajan. Eta tetep ngajarkeun urang Nornir-skrip pikeun meunangkeun sareng nerapkeun data ieu.
Jang ngalampahkeun ieu, dina Aksara urang sanggeus garis initialization nr = InitNornir(config_file=… tambahkeun kodeu ieu:
...
nr = InitNornir(config_file="config.yaml", dry_run=True) # set dry_run=False, cross your fingers and run again
# enrich Inventory with the encrypted vault data
from ansible_vault import Vault
vault_password_file="inventory/vault.passwd"
vault_file="inventory/creds.yaml"
with open(vault_password_file, "r") as fp:
password = fp.readline().strip()
vault = Vault(password)
vaultdata = vault.load(open(vault_file).read())
for a in nr.inventory.hosts.keys():
item = nr.inventory.hosts[a]
item.username = vaultdata[item.groups[0]]['username']
item.password = vaultdata[item.groups[0]]['password']
#print("hostname={}, username={}, password={}n".format(item.hostname, item.username, item.password))
# run tasks
...
Tangtosna, vault.passwd henteu kedah aya di gigireun creds.yaml sapertos conto kuring. Tapi éta ok pikeun maén.
Sakitu wae kanggo ayeuna. Aya sababaraha langkung seueur tulisan ngeunaan Cisco + Zabbix, tapi ieu sanés sakedik ngeunaan otomatisasi. Sarta dina mangsa nu bakal datang kuring rencanana nulis ngeunaan RESTCONF di Cisco.
sumber: www.habr.com