[c-nsp] Tail-f / NCS

Jared Mauch jared at puck.nether.net
Sat Mar 12 20:03:12 EST 2016

You need the culture of automation before an automation tool makes sense. Cut and paste only takes you so far, notepad, vim, pico and others as well. 

Parameterized templates are the better path to be on. XR and JunOS support commit replace type operations, as do others like Arista.

Building your culture must come first, so it outlives the one or two people who make it, as many a provider have failed to remember how to do things, or use the tools of their predecessors. 

Here's a link to emphasize my point :-) 

Jared Mauch

> On Mar 12, 2016, at 3:03 PM, CiscoNSP List <CiscoNSP_list at hotmail.com> wrote:
> Hi Guys - Have some of our "sales" team at Cisco Live atm, and they are raving about Tail-f / NCS and how we need to purchase it, and it will improve our provisioning efficiency by a whopping 90% (lol)....anyway, just after some "real world" feedback on this product...anyone tried it/using it....or is it way too early to be even considering these types of automation/orchestration products....Im very sceptical about handing provisioning control over to "another" software platform...
> notepad might be slow, but at least I know what commands are being issued on our switches and routers :)
> Cheers
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list