Containers are the next evolutionary step in how applications are managed and consumed. Allowing application teams to control and optimize their application deployment process. Along with the advantages provided to application teams, it's also a dynamic shift for data center design. Allowing for better resource utilization, and management resulting in both cost savings and faster IT. This session will explain how Cisco IT has delivered this new paradigm in Cloud Technology by using Cisco ACI, Cisco UCS and open-source solutions like Kubernetes.
Welcome!
As you already know, containers are disrupting the way IT and data centers host and deliverer applications and services.
We have seen with past innovative technologies, it can be difficult to deploy new solutions like containers on compute and networking in a manageable way at enterprise scale.
Yet we as IT are placed In a position where if we don’t adopt containers, we will inevitably lose resources, money, and agility in our organizations.
We at Cisco IT using a combination of Cisco and Open Source products and technologies are delivering a container based cloud, that we feel can serve as a template in your own journey.
During our conversation this evening, my hope is that you will understand the core technologies and see in our demo the power of a container based cloud.
At the end of this talk, you should be able to leave this building with the foundation to deploy your own container cloud solution, while learning from our successes, and our hardships in our journey to our Container Cloud Solution.
My name is Mike Duarte
I’ve been working in IT for 15 Years
Been at Cisco since 2011
I’m the Lead Design Engineer for Containers
What do you want out of this Session?
I really want you to ask Questions!
I really would like this to be more of a dialog than just a monologue!
Going to talk first about Our Global Cloud Strategy
Second, will be looking at how containers are redefining application delivery
Third, I’m going to talk about how we are using UCS Compute for our container cloud
Then, will dive into ACI Networking and how Containers and Contiv really bring the Application into the ACI Fabric
Finally, I’ll show how all these pieces come together to build out our container platform, with a demo.
Compaq, in 1996 coined the term, it occurred while they were plotting the future of their Internet business.
https://www.technologyreview.com/s/425970/who-coined-cloud-computing/
So let’s start on this journey together by taking a 50,000 foot view of our, as in Cisco IT’s Global Cloud Strategy.
Need to introduce “legacy” to cloud tolerant slide. Should we have a slide for this alone?
Changes to Cloud Native applications are the norm: apps scale up/down, move around to accommodate operations and work around failures. This is in contrast to todays environment where change management is driving when and how changes are made. Difference: automation. Runtime policies replace pre-approvals.
What’s the use of programmability if we can’t automate and break away from manual intervention.
Vertical Scale
Application Teams
Responsible for uptime of application code.
How? Lifecycles, A/B Deployment Models
Infrastructure Teams
Responsible for uptime of infrastructure that the application utilizes.
How? Providing High Availability based data center verticals.
Horizontal Scale
Application Teams
Responsible for uptime of application code.
How? Lifecycles, A/B Deployment Models
Responsible for horizontal scalability.
How? Horizontal scale out of replicated services handled either by the application or the platform scheduler.
Infrastructure Teams
Responsible for providing spare capacity that the application or platform can utilize
How? Providing affordable, failure domain based data centers
Faster you can deliever hardware into your data center, the less you have to predict growth, and the less of a “runway” you need. Driving better efficency, aiming for just in time capacity for our application owners, just as just in time delivery has transformed manufacturing.
Distribution = Flexibility, Choice, and Resiliency
HA to Single Legged
Design to Fail (Failure Domains/Availability Zones)
Cluster of Failure Domains = Region
Unified control plane for all the elements in the system
Centralizing global policies, service profiles, inventory, ID pools and templates
Distributed Container Orchestration System
Cisco Systems was founded in December 1984 by Leonard Bosack and Sandy Lerner, two Stanford University computer scientists, who pioneered the concept of a local area network (LAN) being used to connect geographically disparate computers over a multiprotocol router system.
https://en.wikipedia.org/wiki/Cisco_Systems
Tim Berners-Lee hosted the first webserver at CERN on a NeXT Workstation (Specifically the NeXTcube)
https://commons.wikimedia.org/wiki/File:First_Web_Server.jpg
In conclusion, I hope you have seen that cisco IT is using a combination of cisco and open source products and technologies to deliver a container based cloud, that can serve as a template for you own journey.
Feel free to connect with me after this session, or on spark.
Hopefully now at the end of this discussion, you have the building blocks to deploy your own container cloud solution, while learning from our successes, and hardships from our own journey.
Thank You! Any Questions?
Should we standardize on a container format?
Should we standardize on a container scheduler
Should we prohibit 3rd party containers
Can we detect vulnerabilities and vulnerable containers?
Can we detect malicious behavior?
How to enforce security without minimizing the benefits of containers?
