Welcome to a new series where we interview Ansible experts on IT automation and ask them to share their direct experiences building automation solutions, as well as any insights they have regarding the state of the industry.
In this post, I’ve asked Peter Sprygada and Eric McLeroy five questions about network automation.
Peter Sprygada is a Senior Principal Engineer at Ansible by Red Hat where he brings over 20 years experience building and operating global network infrastructures. He holds two patents in network configuration automation and currently leads the Ansible network engineering team that focuses on building and integrating network automation capabilities into Ansible. Formerly Peter was responsible for building and leading the Arista EOS+ Extensibility Engineering team where he focused on applying DevOps methodologies to enhancing network operations. Prior to that, he held senior network engineering and operations roles at various organizations including Cisco. You can follow him on twitter at @privateip.
Eric McLeroy is a Senior Solutions Architect for Ansible by Red Hat focused on networking use cases. Eric has over 10 years in networking in large scale environments working with a large variety of systems from routers, switches, load balancers, etc. He holds multiple industry certifications and Continue reading
The post Worth Reading: Connecting Nepal appeared first on rule 11 reader.
Artificial Intelligence has the potential to bring immense opportunities, but it also poses challenges.
Artificial intelligence (AI) is dominating the R&D agenda of the leading Internet industry. The Silicon Valley and other startup hubs are buzzing about artificial intelligence and the issue has come at the top of policymakers’ agenda including the G20, the ITU, and the OECD, where leaders gathered this week in Paris.
The peak attack size increased 60 percent year-over-year.
The server product includes Docker tooling and integrates with all Docker registries.
About a dozen partners have already committed to integrating Greengrass into their platforms.
The 40 hour work week is foremost a result of the physical limits of the human body—but we often fail to take into account the mental limits, as well. Why was working for more than 40 hours a week on a railroad dangerous? It was not just because people were physically tired, but also because they were mentally tired. The resulting discussion among coders has been rampant and widespread (see, for instance, here).
First, the focus on time and the length of the work week may be a little misdirected. We are still a world focused on physical presence as a proxy for accomplishing work. I know a lot of companies prefer to have people in the office—ironically, this is a big deal with most of the companies in the world that aim to bring networks, and network based services, to the masses. Continue reading
This is Cumulus’ first major announcement centered around performance monitoring.
Software-defined platform targets growing mix of physical data centers and public infrastructure.
The post Worth Reading: pbgpp appeared first on rule 11 reader.
SAP hopes to rival peers like GE Predix and IBM Watson in IoT.
Customers can do cost comparisons between private and public.