Heus Habr!
Nuper articulus hic papaver ubi problema simile fossile usura solvebatur. Et quamvis opus omnino proprium sit, nihil simile habet de Habre. Audeo meam cursoriam ad honorandam IT communitatem offerre.
Non est prima cursoria ad tale negotium. Prima optio ante aliquot annos effecta est rursus in ansible poema 1.x.x. Birota raro usus est ideoque constanter rubiginosa est. In sensu, negotium ipsum non oritur quotiens versiones renovantur ansible. Quotienscumque opus est agitare, catena decidit vel rota decidit. Prima autem pars confis generans semper praeclare operatur, feliciter jinja2 Machina longa est. sed altera pars — ficos evolvit — admirationes plerumque attulit. Et quoniam mihi evolvendum config longius ad dimidium centum strophas, quarum aliquae milia chiliometrorum absunt, hoc instrumento parum taediosum est utens.
Hic fateor necesse est meam dubitationem maxime probabilem esse in carentia familiaritatis ansiblequam in delictis. Atque hoc obiter magni ponderis est. ansible omnino separatum est, suum spatium cognitionis cum suo DSL (Domain Specifica Language), quod in fidenti gradu servari debet. Bene, id momentum ansible Proficiscitur cito, et sine speciali respectu convenientiae retrorsum, fiduciam non addit.
Ergo non ita pridem altera versio birota completa est. Hoc tempore in pythonvel potius in ambitu scriptum python quod python nomine
Sic - Nornir microframework scriptum est python quod python et disposito automation. Similiter ac in casu cum ansible, ad solvendas quaestiones hic, requiritur competentis notitia praeparationis, i.e. inventarium exercituum earumque parametri, sed scripta non in DSL separato, sed in eodem non antiquissimo, sed valde bono p[i|i]ton.
Intueamur quid sit hoc vivo exemplo utens.
Retis ramum cum pluribus duodenis officiis per patriam habeo. Quodlibet officium habet iter LURIDUS, quod plures canales communicationis a diversis operatoribus terminat. Protocollum fuso est BGP. Iter itineris LURI veniunt in duo genera: Cisco ISG vel Iuniperus SRX.
Nunc opus: subnet dedicatum configurare debes pro speculatione vide in portu separato in omnibus itineribus WAN retis rami - praeconium hoc subnet in BGP - celeritatem limitis portus dedicati configurare.
Primum, duo exempla praeparare oportet, ex quibus schemata pro Cisco et Iunipero separatim generabuntur. Oportet etiam ut singula puncta et nexus parametri, i.e. colligere eadem inventarium
Promptus pro 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 anyFormula pro Iunipero:
$ 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 limiterMauris mattis ex a neque cursus tempus. Hae sunt essentialiter inter figurationes operantes quae fuerunt et fuerunt, solvendo negotium in duobus certis itineribus diversorum exemplorum.
Ex nostris exemplaribus perspicimus quaestionem solvendam, duobus parametris Iuniperis et 3 parametris pro Cisco tantum indigere. hic sunt:
- ifname
- ipsuffix
- asn
Nunc ad singulas fabricas parametros istos apponere oportet, i.e. idem facite inventarium.
Ad inventarium Nos stricte sequi documenta
hoc est, eundem fasciculum osseum faciamus;
.
├── config.yaml
├── inventory
│ ├── defaults.yaml
│ ├── groups.yaml
│ └── hosts.yamlScapus config.yaml fasciculus norma nornir configuration file
$ 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"Nos pelagus parametri in tabella indicant host.yamlCirculus (in casu meo haec sunt logins / passwords) in groups.yamlet in defaults.yaml Aliquid non indicamus, sed tres minuses ibi intrare debes - id quod est yaml tabella quamquam vacua est.
Hoc est quod host.yaml similis:
---
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: 65111Et hic circulos.yaml:
---
cisco:
platform: ios
username: admin1
password: cisco1
juniper:
platform: junos
username: admin2
password: juniper2Hoc est quod factum est inventarium ad negotium nostrum. Per initialization, parametri ex inventario documentorum ad exemplar objecti provisi sunt InventoryElement.
Infra praedo tabula exemplar InventoryElement est
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"
}
}
}
}
}Exemplar hoc parum confusum inspicere potest, praesertim primo. Ut sit figura, modus interactive in 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'
Ac denique ad ipsam scripturam transeamus. Hic nihil habeo quod maxime superbus est. Modo sumpsit paratum exemplum a et fere immutata usus est. Hoc est quod scriptum est similis operis operis:
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)Attende ad modulum dry_run = verus secundum quod initialization nr.
Hic idem quod in ansible curriculum test perductum est in quo nexus ad iter faciendum, nova conformatio modificata praeparatur, quae tunc per machinam convalescit (sed hoc certum non est; dependet a subsidio machini et in NAPALM exactoris) sed nova conformatio non directe applicatur. Ad usum pugnae, modulo removendum est dry_run aut mutare valorem suum False.
Cum scriptum est exsecutioni mandare, Nornir outputs tabulas singulas ad console.
Infra praedo est output pugnae in duobus itineribus testium:
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 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Tesserae in ansible_vault
In principio articuli ivi paulo e navi ansiblesed non omne malum. Ego vere similis eis firmamentum similis est, quae ad occultandam sensibilium informationem occultatur. Et probabiliter multi notaverunt nos omnes logins/passwords pro omnibus iteribus pugnare in forma aperta in tabella scintillantibus gorups.yaml. Non belle, sane. Sit scriptor notitia cum hac custodiat firmamentum.
Parametri transeamus a coetibus.yaml ad creds.yaml, et encrypt illam cum AES256 cum tessera 20 digiti:
$ 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
31393434653165613432326636616636383665316465623036376631313162646435Praesent id purus. Reliquum est ut doceremus nos Nornir-script ut retrieve et applicare haec data.
Ad hoc in nostro scripto post lineam initializationem nr = InitNornir(config_file=… codice sequenti adde:
...
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
...Scilicet, convex.passwd non debet poni iuxta creds.yaml ut in exemplo meo. Sed sit amet felis enim.
Quod ut 'quia iam omnia. Plures articuli duo sunt de Cisco + Zabbix venientes, sed hoc parum de automatione est. Et in proximo de RESTCONF scribere instituo in Cisco.
Source: www.habr.com