An open source framework provides a starting point for building your own analytics system.
Automating virtualized infrastructure management with technologies like hyperconvergence is essential.
Here’s another interesting coincidence:
Homework for today: listen to the podcast, read the article, and start exploring some new technology (network automation immediately comes to mind).
After much delay – I’ve finally found time to take a look at Ansible. I’ve spent some time looking at possible platforms to automate network deployment and Ansible seems to be a favorite in this arena. One of the primary reasons for this is that Ansible is ‘clientless’ (I’m putting that in quotes for a reason, more on that in a later post). So unlike Chef, Puppet, and Salt (Yes – there are proxy modes available in some products) Ansible does not require an installed client on the remote endpoints. So let’s get right into a basic lab setup.
While the end goal will be to use Ansible to automate network appliances, we’re going to start with the a more standard use case – Linux servers. The base lab we will start with is two servers, one acting as the Ansible server and the second being a Ansible client or remote server. Both hosts are CentOS 7 based Linux hosts. So our base lab looks like this…
![]()
Pretty exciting right? I know, it’s not, but I want to start with the basics and build from there…
Note: I’ll refer to ansibleserver as Continue reading
Welcome to the Network Break! Today we look at why it took Netflix 7 years for full cloud adoption, the latest hurdle Google's driverless AI has jumped, LinkedIn's white box strategy, and more!
The post Network Break 74: Recalibrating Cloud Hype; Google AI Jumps Hurdle appeared first on Packet Pushers.
Welcome to the Network Break! Today we look at why it took Netflix 7 years for full cloud adoption, the latest hurdle Google's driverless AI has jumped, LinkedIn's white box strategy, and more!
The post Network Break 74: Recalibrating Cloud Hype; Google AI Jumps Hurdle appeared first on Packet Pushers.

To recap (or rather, as they used to say in old television shows, “last time on ‘net Work…”), this series is looking at BGP security as an exercise (or case study) in understanding how to approach engineering problems. We started this series by asking three questions, the third of which was:
What is it we can actually prove in a packet switched network?
From there, in part 2 of this series, we looked at this question more deeply, asking three “sub questions” that are designed to help us tease out the answer this third question. Asking the right questions is a subtle, but crucial, part of learning how to deal with engineering problems of all sorts. Those questions can be summed up as:
Let’s quickly look at the first of these two to see why it’s not provable in the context of a packet switched network, using the network diagram below.
When working with BGP at Internet scale, we tend to think of an autonomous system as one “thing”—we Continue reading
OpenStack for NFV will be production-ready in 2016 based on development blueprints of documented telecom, OPNFV, and ETSI NFV requirements.

This is a guest post by Kalpesh Patel, an Architect, who works from home. He and his colleagues spends their productive hours scaling one of the largest distributed file-system out there. He works at Egnyte, an Enterprise File Synchronization Sharing and Analytics startup and you can reach him at @kpatelwork.
Your Laptop has a filesystem used by hundreds of processes, it is limited by the disk space, it can’t expand storage elastically, it chokes if you run few I/O intensive processes or try sharing it with 100 other users. Now take this problem and magnify it to a file-system used by millions of paid users spread across world and you get a roller coaster ride scaling the system to meet monthly growth needs and meeting SLA requirements.
Egnyte is an Enterprise File Synchronization and Sharing startup founded in 2007, when Google drive wasn't born and AWS S3 was cost prohibitive. Our only option was to roll our sleeves and build an object store ourselves, overtime costs for S3 and GCS became reasonable and because our storage layer was based on a plugin architecture, we can now plug-in any storage backend that is cheaper. We have re-architected many of Continue reading

The post Worth Reading: Virtualization Slides appeared first on 'net work.