Cisco ACI & F5 Integrate to Transform the Data Center

Editor's Notes

• #10: (This scripted slide is part of the ACI Core “Ease” Message presentation – if seen by itself, the script might not make sense) Cisco introduced Application Centric Infrastructure (ACI) publicly in November 2013 and we started shipping ACI to customers in July 2014. There are a number of key characteristics that form the foundation of ACI that we will cover in more detail in the rest of the presentation. Apps + Infra: ACI is focused on an Applications infrastructure needs, not just about forwarding packets. For the first time a network understands that the packets it is forwarding belong to applications and for the first time a network can provide application relevant information about the applications infrastructure behavior/needs. Physical and Virtual: The new DC networks (or fabrics as we started calling them) have changed in that there are now much more virtual workloads that need to be supported. The new way of developing applications also changed the communication needs from north-south to east-west (more on that later). But in the end, physical systems are a very relevant part of a data-center. It is our view that any network must support both virtual as well as physical system and provide network services to both equally. Secure: ACI is built from the ground up with security and multi-tenancy in mind. Todays DC network has a default policy that allows end points (workloads) to communicate unless there is a specific configuration that forbids it. It is open from a security perspective. ACI fundamentally changes the security level as the default policy is to deny communication between end points (workloads) unless there is a specific policy that allows it. (Note: I’m specifically not mentioning more about security at this stage, there is specific Security slide coming later). Open: Open is top of mind in many of our customers conversations with us. Open protocols, open source, open programing interfaces etc… ACI is designed to be open. Open with regards to a single API that can be used to talk to ACI. Open with regards to the protocols used inside the ACI fabric, Open with regards to the eco-system and the protocol used to distribute policy (Note: I’m specifically not mentioning OpFlex at this stage yet, just want to set the scene for open, to have a more detailed follow-up conversation later in the presentation) OnPrem and Cloud: Of the 4 points this is the least tangible. Decide if you want to talk about his or not. ACI can be deployed on premises by enterprises and services providers. It is multi-tenant and secure. However we see ACI as the fabric foundation for cloud offerings. Cisco has introduced the Cisco Global Intercloud, an initiative to build the worlds largest cloud of clouds, together with our service provider partners. The foundation for that is ACI. OnPrem and Cloud: A significant portion of customers have moved to Converged Stacks, and in the most recent Gartner Magic Quadrant, Cisco is represented in the leaders quadrant twice, with the Vblock and FlexPod offerings. Both of these converged stacks will announce ACI versions of their stacks in the 2H 2014.
• #18: And finally the Application Services Fabric hosts a catalog of application services. Focused on five major areas: Security Identity and Access Mgmt Availability Mobility And Performance
• #52: to meet with F5 technical experts and watch live solution demos