Developer: Network team, did you order the Code upgrade?!
Operations Manager: You don’t have to answer that question!
Network Engineer: I’ll answer the question. You want answers?
Developer: I think I’m entitled!
Network Engineer: You want answers?!
Developer: I want the truth!
Network Engineer: You can’t handle the truth! Son, we live in a world that has VLANs, and those VLANs have to be plumbed by people with CLIs. Who’s gonna do it? You? You, Database Admin? I have a greater responsibility than you can possibly fathom. You weep for app agility and you curse the network. You have that luxury. You have the luxury of not knowing what I know, that network plumbing, while tragically complex, delivers apps. And my existence, while grotesque and incomprehensible to you, delivers apps! You don’t want the truth, because deep down in places you don’t talk about at parties, you want me on that CLI. You need me on that CLI. We use words like “routing”, “subnets”, “L4 Ports”. We use these words as the backbone of a life spent building networks. You use them as a punch line. I have neither the time nor the inclination to explain myself to a man who rises and sleeps under the blanket of infrastructure that I provide, and then questions the manner in which I provide it! I would rather you just said “thank you”, and went on your way. Otherwise, I suggest you pick up a putty session, and configure a switch. Either way, I don’t give a damn what you think you are entitled to!
Developer: Did you order the Code upgrade?
Network Engineer: I did the job thatâ€”-
Developer: Did you order the Code upgrade?!!
Network Engineer: YOU’RE GODDAMN RIGHT I DID!!
In many IT environments today there is a distinct line between the application developers/owners and the infrastructure teams that are responsible for deploying those applications.Â These organizational silos lead to tension, lack of agility and other issues.Â Much of this is caused by the translation between these teams.Â Application teams speak in terms like: objects, attributes, provider, consumer, etc.Â Infrastructure teams speak in memory, CPU, VLAN, subnets, ports.Â This is exacerbated when delivering apps over the network, which requires connectivity, security, load-balancing etc.Â On todayâ€™s network devices (virtual or physical) the application must be identified based on Layer 3 addressing and L4 information.Â This means the app team must be able to describe components or tiers of an app in those terms (which are foreign to them.)Â This slows down the deployment of applications and induces problems with tight controls, security, etc.Â Iâ€™ve tried to describe this in the graphic below (for people who donâ€™t read good and want to learn to do networking things good too.)
As shown in the graphic, the definition of an application and its actual instantiation onto networking devices (virtual and physical) is very different.Â This causes a great deal of the slowed application adoption and the complexity of networking.Â Todayâ€™s networks donâ€™t have an application centric methodology for describing applications and their requirements.Â The same can be said for emerging SDN solutions.Â The two most common examples of SDN today are OpenFlow and Network Virtualization.Â OpenFlow simply attempts to centralize a control plane that was designed to be distributed for scale and flexibility.Â In doing so itÂ uses 5-tuple matches of IP and TCP/UDP headers to attempt to identify applications as network flows.Â This is no different from the model in use today.Â Network virtualization faithfully replicates todayâ€™s network constructs into a hypervisor, shifting management and adding software layers without solving any of the underlying problem.
Whatâ€™s needed is a common language for the infrastructure teams and development teams to use.Â that common language can be used to describe application connectivity and policy requirements in a way that makes sense to separate parts of the organization and business.Â Cisco Application Centric Infrastructure (ACI) uses policy as this common language, and deploys the logical definition of policy onto the network automatically.
Cisco ACI bases network provisioning on the application and the two things required for application delivery: connectivity and policy.Â By connectivity weâ€™re describing what group of objects is allowed to connect to other groups of objects.Â We are not defining forwarding, as forwarding is handled separately using proven methods, in this case ISIS with a distributed control plane.Â When we describe connectivity we simply mean allowing the connection.Â Policy is a broader term, and very important to the discussion.Â Policy is all of the requirements for an application: SLAs, QoS, Security, L4-7 services etc.Â Policy within ACI is designed using reusable â€˜contracts.â€™Â This way policy can be designed in advance by the experts and architects with that skill set and then reused whenever required for a new application roll-out.
Applications are deployed on the ACI fabric using an Application Network Profile. An application network profile is simply a logical template for the design and deployment of an applications end-to-end connectivity and policy requirements.Â If youâ€™re familiar with Cisco UCS itâ€™s a very similar concept to the UCS Service Profile.Â One of the biggest benefits of an Application Network profile is its portability.Â They can be built through the API, or GUI, downloaded from Cisco Developer Network (CDN) or the ACI Github community, or provided by the application vendor itself.Â Theyâ€™re simply an XML or JSON representation of the end-to-end requirements for delivering an application.Â The graphic below shows an application network profile.
This model provides that common language that can be used by developer teams and operations/infrastructure teams.Â To tie this back to the tongue-in-cheek start to this post based on dialogue from â€œA Few Good Menâ€, we donâ€™t want to replace the network engineer, but we do want to get them off of the CLI.Â Rather than hacking away at repeatable tasks on the command line, we want them using the policy model to define the policy â€˜contractsâ€™ for use when deploying applications.Â At the same time we want to give them better visibility into what the application requires and what itâ€™s doing on the network.Â Rather than troubleshooting devices and flows, why not look at application health?Â Rather than manually configuring QoS based on devices, why not set it per application or tier?Â Rather than focusing on VLANs and subnets as policy boundaries why not abstract that and group things based on those policy requirements?Â Think about it, why should every aspect of a servers policy change because you changed the IP?Â Thatâ€™s what happens on todayâ€™s networks.
Call it a DevOps tool, call it automation, call it what you will, ACI looks to use the language of applications to provision the network dynamically and automatically.Â Rather than simply providing better management tools for 15 year old concepts that have been overloaded we focus on a new model: application connectivity and policy.
**Disclaimer: I work as a Technical Marketing Engineer for the Cisco BU responsible for Nexus 9000 and ACI.Â Feel free to disregard this post as my biased opinion.**