This blog article was inspired by some infuriating reads and blogs doing the rounds doing significant damage to business thinking.
I’ve heard so many conversations that confuse Software Defined Networking with Software Driven Networking, automation mixed up with abstraction and MANO (Management and Orchestration) mixed up with configuration management tools that are used for building mutable infrastructure like Puppet, Chef, Ansible and Salt. Is it possible to cross pollinate all of these technologies? Sure, but do not expect people to happy about it. Nerds will love it, process people will hate it and failures will be dominant. Don’t even go there with failing fast. That statement is out of scope as an excuse.
Mutable Infrastructure
Mutable in this sense means to mutate and change. Configuration management tools can create virtual machines, populate them with the packages required to deliver services and place domain specific configuration in order to make them live and in production.
Mutable infrastructure as we know it today is "treat your VMs like cattle, not pets" and this is achieved with well known tools.
Immutable Infrastructure
Think about containers here and unikernels. The idea is we build applications with as few dependencies as possible. Ultimately building applications Continue reading
IPv6 registrations are steady, but demand for IPv4 remains sky high since ARIN's IPv4 supply ran out.
Enterprise networks are under constant attack, but companies lack the security expertise needed to protect their data.
One of my friends plans to replace existing FabricPath data center infrastructure, and asked whether it would make sense to stay with FabricPath (using the new Nexus 5600 switches) or migrate to ACI.
I proposed a third option: go with simple VXLAN encapsulation on Nexus 9000 switches. Here’s why:
Read more ...