Re: Templating/automating configuration

On Wed, Jun 14, 2017 at 3:55 PM, Job Snijders wrote: > On Wed, Jun 14, 2017 at 09:35:59PM +0100, Nick Hilliard wrote: >> Graham Johnston wrote: >> > Would you be able to provide any further insight into your Don’t #5 – >> > “Don’t agree to change management. Managers are rarely

Re: Templating/automating configuration

On Wed, 14 Jun 2017 21:35:59 +0100, Nick Hilliard may have written: > What do you think the purpose of change control / management is? To provide employment for change managers of course. -- Mike Meredith, University of Portsmouth Chief Systems Engineer, Hostmaster, Security,

Re: Templating/automating configuration

On Wed, Jun 14, 2017 at 09:35:59PM +0100, Nick Hilliard wrote: > Graham Johnston wrote: > > Would you be able to provide any further insight into your Don’t #5 – > > “Don’t agree to change management. Managers are rarely engineers and > > should not be making technical decisions. (nor should

Re: Templating/automating configuration

Graham Johnston wrote: > Would you be able to provide any further insight into your Don’t #5 – > “Don’t agree to change management. Managers are rarely engineers and > should not be making technical decisions. (nor should sales)“. What do you think the purpose of change control / management is?

Re: Templating/automating configuration

Hi Graham, The talk was giving in context of motivating people to start with network automation and help them go from 'no automation' to a step further 'some automation'. On Wed, Jun 14, 2017 at 07:50:05PM +, Graham Johnston wrote: > Would you be able to provide any further insight into your

RE: Templating/automating configuration

:03 PM To: Brian Knight <m...@knight-networks.com>; Graham Johnston <johnst...@westmancom.com> Cc: nanog@nanog.org Subject: Re: Templating/automating configuration Hi, Here are some extra pointers: https://youtube.com/watch?v=C7pkab8n7ys https://www.nanog.org/sites/d

Re: Templating/automating configuration

agree again all of the above thanks > On Jun 11, 2017, at 7:58 PM, Gordon Cook wrote: > > again I understand and agree > > > > the reach of your drowning analysis and understanding is awesome > > hi randy bush > > > oops and hi jp confused of calcutta and chris

Re: Templating/automating configuration

again I understand and agree the reach of your drowning analysis and understanding is awesome hi randy bush oops and hi jp confused of calcutta and chris locke rage boy > On Jun 7, 2017, at 6:17 PM, Andrew Dampf wrote: > > Salt is great for generating configs based on

Re: Templating/automating configuration

Salt is great for generating configs based on jinja templates, and you can use napalm in conjunction with salt to push the configs to the device on a set schedule (typically this is done hourly). If manual changes are made to the router, salt would override them on the next run, so it's a great

Re: Templating/automating configuration

On 7 June 2017 at 19:52, Brian Knight wrote: > The import process to the database runs directly on our rancid server, > reading the downloaded configs out of the appropriate directory within > rancid. Most of our gear is Cisco, so the ciscoconfparse module for Python

Re: Templating/automating configuration

On Wed, 07 Jun 2017 04:23:33 -0500 t...@pelican.org wrote Hi Brian, On Tuesday, 6 June, 2017 21:48, "Brian Knight" m...@knight-networks.com said: Because we had different sources of truth which were written in-house, we wound up rolling our own template engine in Python.

Re: Templating/automating configuration

Hi Brian, On Tuesday, 6 June, 2017 21:48, "Brian Knight" said: > Because we had different sources of truth which were written in-house, we > wound up > rolling our own template engine in Python. It took about 3 weeks to write the > engine and adapt existing templates.

Re: Templating/automating configuration

On 7 June 2017 at 00:43, Vincent Bernat wrote: > ❦ 6 juin 2017 14:30 +0100, Oliver Elliott : > >> I echo Ansible. I'm using it with NAPALM and jinja2 templates to push and >> verify config on switches. > > Why not using the builtin ability of

Re: Templating/automating configuration

❦ 6 juin 2017 14:30 +0100, Oliver Elliott  : > I echo Ansible. I'm using it with NAPALM and jinja2 templates to push and > verify config on switches. Why not using the builtin ability of ansible for most vendors? (genuine question)

Re: Templating/automating configuration

I echo Ansible. I'm using it with NAPALM and jinja2 templates to push and verify config on switches. Oli On 6 June 2017 at 14:27, Pui Edylie wrote: > Hi, > > Take a look at Ansible > > https://www.ansible.com/ > > Our whole infra is automated using it and it is great! > >

Re: Templating/automating configuration

Go templates: http://golang.org Fast and simple with gRPC and other good stuff like kelsey’s confd (a daemon that watches for changes and update templates) % go doc text/template package template // import "text/template" Package template implements data-driven templates

Re: Templating/automating configuration

Hi, Here are some extra pointers: https://youtube.com/watch?v=C7pkab8n7ys https://www.nanog.org/sites/default/files/dosdontsnetworkautomation.pdf https://github.com/coloclue/kees Kind regards, Job On Tue, 6 Jun 2017 at 13:49, Brian Knight wrote: > Because we had

Re: Templating/automating configuration

Because we had different sources of truth which were written in-house, we wound up rolling our own template engine in Python. It took about 3 weeks to write the engine and adapt existing templates. Given a circuit ID, it generates the full config for copy and paste into a terminal session. It

Re: Templating/automating configuration

https://youtu.be/ltqXgtLWXFo and the assocaited pdf https://www.nanog.org/meetings/nanog44/presentations/Monday/Gill_programatic_N44.pdf On Tue, Jun 6, 2017 at 10:09 AM, Nick Hilliard wrote: > Graham Johnston wrote: > > Short of complete SDN, for those of you that have some

Re: Templating/automating configuration

http://ipspace.net - search on everything ref network automation, under webinars. Ivan is among the best in analysis and consolidation of such info, and in documenting all options you may have. Once you see what he has to offer, and definitely not only in the network automation space, you may

Re: Templating/automating configuration

Graham Johnston wrote: > Short of complete SDN, for those of you that have some degree of > configuration templating and/or automation tools what is it that you > run? I'm envisioning some sort of tool that let's me define template > snippets of configuration and aids in their deployment to

Re: Templating/automating configuration

Hi, Take a look at Ansible https://www.ansible.com/ Our whole infra is automated using it and it is great! Regards, Edy On 6/6/2017 9:22 PM, Graham Johnston wrote: Short of complete SDN, for those of you that have some degree of configuration templating and/or automation tools what is it

Templating/automating configuration

Short of complete SDN, for those of you that have some degree of configuration templating and/or automation tools what is it that you run? I'm envisioning some sort of tool that let's me define template snippets of configuration and aids in their deployment to devices. I'm okay doing the