One of the attendees of our network automation course asked a question along these lines:
In a previous Ansible-based project I used Excel sheet to contain all relevant customer data. I converted this spreadsheet using python (xls_to_fact) and pushed the configurations to network devices accordingly. I know some people use YAML to define the variables in Git. What would be the advantages of doing that over Excel/xsl_to_fact?
Whenever you’re choosing a data store for your network automation solution you have to consider a number of aspects including:
One of the attendees of our network automation course asked a question along these lines:
In a previous Ansible-based project I used Excel sheet to contain all relevant customer data. I converted this spreadsheet using python (xls_to_fact) and pushed the configurations to network devices accordingly. I know some people use YAML to define the variables in Git. What would be the advantages of doing that over Excel/xsl_to_fact?
Whenever you’re choosing a data store for your network automation solution you have to consider a number of aspects including:
It has been a long time – more than 15 years – since AMD has been in a position to pressure larger rival Intel in supplying processors to server OEMs and ODMs for the datacenter. …
AMD’s Top Brass Take Another Swing At Intel With Milan Epycs was written by Jeffrey Burt at The Next Platform.
Managing infrastructure at Google is a lot more than just putting stuff into containers and letting Borg push it around. …
Keeping Infrastructure And Applications Humming Along Like Google was written by Jeffrey Burt at The Next Platform.
By using cloud platforms, we can take advantage of different resource configurations and compute capacities. However, deploying containerized applications on cloud platforms is proving to be quite challenging, especially for new users who have no expertise on how to use that platform. As each platform may provide specific APIs, orchestrating the deployment of a containerized application can become a hassle.
Docker Compose is a very popular tool used to manage containerized applications deployed on Docker hosts. Its popularity is maybe due to the simplicity on how to define an application and its components in a Compose file and the compact commands to manage its deployment.
Since cloud platforms for containers have emerged, being able to deploy a Compose application on them is a most-wanted feature by many developers that use Docker Compose for their local development.
In this blog post, we discuss how to use Docker Compose to deploy containerized applications to Amazon ECS. We aim to show how the transition from deploying to a local Docker environment to deploying to Amazon ECS is effortless, the application being managed in the same way for both environments.
In order to exercise the examples in this blogpost, the following tools need Continue reading
This section explains the process how to build an on-prem Cisco Viptela based SD-WAN control plane system. It starts by setting up an enterprise Certificate Server using the Cisco CSR1000V cloud router. Next, it goes through the process of root certificate generation. The rest of the chapter explains the initial configuration and certification installation processes from vManage, vBond, and vSmart viewpoints.
![]() |
| Figure 1-1: Control-Plane Components Topology. |
Palo Alto Networks CloudBlades and AWS Transit Gateway Connect can automate the setup of SD-WAN networks from branch offices to the public cloud. Here's how.
The post Automate SD-WAN Connections To AWS With Palo Alto Networks Prisma SD-WAN appeared first on Packet Pushers.

What percentage of business-impacting application outages are caused by networks? According to a recent survey by the Uptime Institute, about 30% of the 300 operators they surveyed, 29% have experienced network related outages in the last three years—the highest percentage of causes for IT failures across the period.
A secondary question on the survey attempted to “dig a little deeper” to understand the reasons for network failure; the chart below shows the result.
We can be almost certain the third-party failures, if the providers were queried, would break down along the same lines. Is there a pattern among the reasons for failure?
Configuration change—while this could be somewhat managed through automation, these kinds of failures are more generally the result of complexity. Firmware and software failures? The more complex the pieces of software, the more likely it is to have mission-impacting errors of some kind—so again, complexity related. Corrupted policies and routing tables are also complexity related. The only item among the top preventable causes that does not seem, at first, to relate directly to complexity is network overload and/or congestion problems. Many of these cases, however, might also be complexity related.
The Uptime Institute draws this same lesson, though Continue reading
Palo Alto Networks sponsors today's Tech Bytes. We drill into key differentiators of the Prisma SD-WAN platform including its use of machine learning, the unique CloudBlades offering, and its app-defined approach to path selection and policy enforcement. Our guest from Palo Alto Networks is Rohan Grover, Senior Director of Product Management.
The post Tech Bytes: How Palo Alto Networks Differentiates Prisma SD-WAN (Sponsored) appeared first on Packet Pushers.
I’ll be joining Jeff Tantsura, Nick Buraglio, and Brooks Westbrook for a roundtable on March 16, 9 am PST (that’s tomorrow if you’re reading this the day it publishes) about the development of wide area networking technologies up until today. This is the first part of a two part series on changes in the wide area network.
With every passing year, as AMD first talked about its plans to re-enter the server processor arena and give Intel some real, much needed, and very direct competition and then delivered again and again on its processor roadmap, it has gotten easier and easier to justify spending at least some of the server CPU budget with Intel’s archrival in the X86 computing arena. …
The Third Time Charm Of AMD’s Milan Epyc Processors was written by Timothy Prickett Morgan at The Next Platform.
This week's Network Break discusses new ASICs from Cisco, new metadata fields in AWS VPC flow logs, a cloud visibility fabric from packet broker specialist Gigamon, lessons from a data center fire, and more tech news.
The post Network Break 324: Cisco ASIC Hits 25.6Tbps; AWS Extends VPC Flow Logs For Better Visibility appeared first on Packet Pushers.