Enabling Fast IT using Containers, Microservices and DevOps Model
•Als PPT, PDF herunterladen•
3 gefällt mir•556 views
Speaker: Balaji Sivasubramanian
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Enabling Fast IT using Containers, Microservices and DevOps Model
Ähnlich wie Enabling Fast IT using Containers, Microservices and DevOps Model (20)
Mehr von Cisco DevNet
Mehr von Cisco DevNet (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Enabling Fast IT using Containers, Microservices and DevOps Model
- 2. Enabling Fast IT using Containers, Microservices and DevOps Model Balaji Sivasubramanian, Director, Product Management, Open Source Solutions
- 3. • Introduction – Fast IT • Containers Eco-System and Use Cases • Contiv – Policy Based Infrastructure for Containerized Applications • Challenges with Fast IT adoptions • Conclusion Agenda
- 4. EfficiencyEfficiency SpeedSpeed IT Transformation: The Tale of Two ITs
- 5. Containers Eco-System and Use Cases
- 6. Containers is a popular technology and is being rapidly adopted in the market •5x user growth (to ~8% of customers) •Docker runs on 6% of monitored hosts from near zero earlier this year •Container adoption is higher in larger companies •Users triple number of containers in 3 months Source: Datadog survey (7000 customers) •2B Docker Hub Pulls •20x growth in past year! Docker Hub Usage Customer adoption / survey Source: Docker Inc
- 7. Even with such a tremendous growth, the potential for further adoption is still enormous and real 32% 14% 8% 8% 20% 35% 12% 10% 11% 36% 19% Ansible Salt Chef Puppet 3% 18% 14% 49% 55% 52% 20% Plan to use Use today26% 19% 13% 11% 5% 18% 20% 36% 10% 9% 11% Salt 14% Ansible 14% 3% 21% 49% Puppet 39% Chef 44% % of Enterprises using: % of SMBs using: Source: RightScale 2015 State of the cloud report
- 8. Containers are the next evolution of datacenter infrastructure technology Virtualmachines Containers • A Linux container allows to run multiple applications isolated from one another on the same operating system • Docker automates the deployment and portability of any application and all dependencies within a lightweight, editable, self-sufficient container • Containers have the potential to disrupt and replace traditional datacenter virtualization PortabilityPackaging Performance APP - Image contains all libraries needed for application - Easy to build, share, update - Unit of testing / distribution - Near bare metal performance - Minimal overhead per container - Near zero “boot” time - Move apps between private clouds - Shift workloads to/from public cloud - Easy to move through CI/CD What is a container?
- 9. Containers bring benefits in the app development space because of their portability and flexibility • Agility in app development • Application lifecycle management • CI/CD and ease of deployment • Improve business process architecture using a composition of services • Cost reduction: • Increase DC utilization / higher density than virtual machines • Reduce costs of virtualization Developer Version control QA / QE Sysadmin
- 10. The ecosystem is made of many players and it is a rapidly evolving eco-system PaaS or Container frameworks/Stacks Operating system Containers orchestration Container registry Container image - Application - Libraries Container runtime Configuration management CI/CD
- 11. Contiv – Policy Based Infrastructure for Containerized Applications
- 12. The Status Quo Variety of users: cars, trucks, ambulances, buses, pedestrians, two-wheelers, etc. No Policy: No Lights, No Lanes, No Rules, No Governance, No Enforcement, Best Effort Meskel Square [ Source: Reddit.com ] Status Quo: Deploying Applications on Shared Infrastructure
- 13. Container Orchestration need ability to leverage infrastructure differentiation better for Application Performance, Security and Visibility. Container Stacks Infrastructure Unified | Integrated | Automated Scheduling | Allocation Visibility Application Awareness Infrastructure Capabilities Nexus 2k-9k Contiv: Making Infrastructure/Solutions Ideal for containers
- 14. • Container industry is focused on creating ability to define applications through Docker Compose, Kubernetes Pod definition etc. • As applications move from development to production, there is need to able to define and enforce infrastructure operational policies • Contiv is creating industry thought leadership around need for infrastructure policies for containerized applications in a shared infrastructure • Contiv provides framework and implementation to address operation intent for Infrastructure. Contiv Addressing Enabling Infrastructure to Run Production Containerized Applications Better
- 15. • Agile - Increased speed of infrastructure provisioning • Networking: network creation, endpoint reachability convergence security policies instantiation • Storage: Storage policies for volumes as they are instantiated • Handling short lived containerized applications • Scalable providing higher performance • Support 10x scale (when compared to VMs) for network, compute, and storage entities • Scale performance by leveraging underlying infra capabilities • Predictable providing better reliability and easier to troubleshoot • Enable efficient resource utilization via enforce operational policies on Infrastructure • Enable application level visibility Contiv – Open Source Project focused on Policy Based Infrastructure for Containerized Applications
- 16. • Contiv.io is an open-source project that creates a policy framework in different domains of containers • Network Policies: Policies for Application Security, Prioritization, and Network Resource Allocation • Network Services for Apps (Virtual or Physical Service appliances) • Analytics/Diagnostics • Integrates with Cisco ACI, Nexus, and UCS Solutions • Ecosystem: Docker, Kubernetes • Status: Beta Contiv Networking provides policy-rich container networking that integrates with Cisco Nexus and ACI Application Composition + Policy Intent Node 1 Node2 Node-n Contiv Master Docker | Kubernetes | Mesos Plugin Agents
- 17. • Contiv Storage is an open-source policy framework for container storage • Storage Policies: • Allocation • Replication • Snapshots • Persistency • IOPs Rate Limiting • Multi-tenant • File System Types, Storage Types • Integrates with Ceph/NFS and Cisco UCS Solutions • Ecosystem: Docker, Kubernetes • Status: Beta/PoC Contiv Storage provides policy-rich container storage that leverages Ceph/NFS underneath Application Composition + Storage Policy Intent Node 1 Node2 Node-n Contiv Master Docker | Kubernetes | Volume Plugin Agents
- 18. Where does Contiv Fit in the Container Stack ? Optimized Infrastructure/ Cisco Integrated Infrastructure Cisco Hardware: UCS Compute, Nexus 9k, ACI Ops Orchestration/PaaS (Provides Roles/Multi-tenancy/Visibility/GUI), Contiv Plugins Container Optimized OS Container Cluster Scheduler | Contiv Cluster-wide Intent Manager Container Image Store Container Runtime (Docker, etc.) Contiv Networking/Volume Agents Developer DevOps SysAdmin Host-1 Host-n
- 19. Contiv– Best Choice for Enterprise Containerized Application Deployments • Best integration with existing infrastructure install-base, any network topology • No topology/connectivity/feature changes to get started with containers • Best leverage of infrastructure hardware (UCS, Nexus) • Integrated with Cisco ACI for container applications for highly scalable solutions • Consistent behavior with variety of workloads (VM, Container, Bare-metal) • Native visibility of container workloads in network • Value added features • Scalable Policies based approach, Multi-tenancy with telemetry and fully automated cluster maintenance • Feature Rich Integration with Container eco-system - Docker, Kubernetes/Mesos
- 20. Challenges in Adoption Fast IT
- 21. Integration and testing components Consistency of deployments Achieve fast payback and ROI Future agility and choice Avoid vendor lock-in Stable platforms/Lack of Maturity Supportable configurations Cost-efficient scale-out Access to skilled staff Business Challenges Around Fast IT Speed of Deployment Risk Management Retain FlexibilityRetain Flexibility
- 22. Most projects/distributions are community supported No single point of contact Which distribution/project/too ls? Which deployment system? Many deployment methods Many package / update systems Best practices on specific architectures? IT Challenges Around Fast IT Support Deployment ComplexityComplexity
- 23. Build Your OwnBuild Your Own As a Service On-Prem or in the Cloud Ownership Customer Cloud Providers Location On-Prem Cloud Providers Management Customer xaas Providers Cloud Providers BUYBUILD Cloud Managed Public CloudIT Operated Choose the Right Consumption Model for Your Deployments
- 24. • Project Mantl integrates different components of a container infrastructure (orchestration, etc.) to make it simple to deploy, also in multi DC environments • Project Shipped integrates different tools to make it easy for developers to deploy applications on an agnostic platform • Ecosystem: Mesosphere, Kubernetes, CloudFoundry (open-source), OpenShift, Docker • Contiv will provide infrastructure differentiation for Shipped/Mantl Shipped aims at creating an agnostic container experience for developers and with Contiv, provides infrastructure differentiation
- 25. Conclusion
- 26. • Containers and Micro services based applicaton architecture will likely disrupt /replace traditional data center virtualization • Contiv provides tools necessary to maintain operational policies in a containerized infrastructure. • IT needs to evolve to embrace Fast IT Conclusions 26
- 27. Fast IT is Here Disrupt or Be Disrupted
- 28. Thank you
Hinweis der Redaktion
- We are living in the world of two ITs. We have to support the traditional IT model but also support the new DevOps model. So what characterizes the two ITs? Mode 1 is about defining traditional strategies that build for long-term. Steady progressions of deployment, operation and long running life cycle is within the scope of the strategy. Efficiency is the primary focus. Mode 2 is about agility, and uses very short update cycles of prioritization, implementation and review. This dual approach allows flexibility which has become a necessity to allow the business to explore new directions. It is not the big eating small. It is the fast eating slow. Gartner predicts in their BiModal IT study that 47% of Enterprises will have two models of IT to support this transformation with separate tools, processes and people to manage and operate them. A Forrester study predicts that it will be 5-7 years before majority of applications are Cloud-Native. In this new age of IT, combining Efficiency (Mode 1) and Speed (Mode 2) enables greater success. Success that allows Business Transformation and Disruption.
- This shows customer’s Challenges/Complications regarding OpenStack. Implementing OpenStack is still an emerging technology area. You want to take advantage of what it offers, but minimize the challenges associated with moving your infrastructure in this new direction. Speed of Deployment: You want to shorten your learning curve and take advantage of proven solutions that will help you achieve business outcomes faster. You want to use consistent deployments to get infrastructure up and running in the shortest time possible. Manage Risk: At the same time, you need to minimize risk by choosing stable platforms that have been hardened for use in production environments. You want configurations designed for supportability, and that can be easily and cost-efficiently scaled. Retain Flexibility: You need solutions that will support future growth and give you the flexibility to adjust as your needs change. These are the areas where Cisco is focusing its efforts to engineer and deliver OpenStack solutions.
- IT faces different challenges when they attempt a DIY OpenStack implementation. There are many options, packages, and methods of distribution. Which one is best? Where do we get support? And support specifically on the platform we’re operating?
- To support today’s continuum of applications ranging from traditional to cloud-native in a fast-moving market, you must be free to choose the optimal consumption model for each workload. In other words, to support a continuum of traditional and cloud native applications, you need a continuum of cloud consumption models that span the range from build to buy. With our portfolio and partner ecosystem, we bring you that continuum and resulting speed by supporting any cloud consumption model with security and data sovereignty. When it comes to consumption models, your preference when it comes to ownership, management, and location of the IT assets and data / applications will ultimately influence the cloud solution Cisco can help you build or buy. If you want to retain ownership over your IT assets, manage your own private cloud and keep the data on premises, we can help you with our data center and private/hybrid cloud infrastructure offerings. If you want to retain varying degrees of ownership of your IT assets while shifting management to a third party, Cisco offers a range of ways we can help, from our Cisco OpenStack Private Cloud offering to on-demand private cloud services. And finally, if your consumption model of choice places ownership, management, and location of your IT assets with a third party, we offer cloud services from Cisco and our Intercloud partners. And across all consumption models, Cisco offers our Professional Services. Cisco brings you speed and agility by uniquely enabling you to act on your own choices and preferred ways of doing business, making the data center and cloud securely adapt to your consumption models and not the other way around. ----= Additional Notes: Cisco gives you tremendous flexibility regarding how you can consume Cloud solutions. Depending on your use case(s) you will have to decide three important elements: (1) Do you need/want to retain ownership of the IT assets associated with your Cloud project? (2) Do you want your IT organization to manage your Cloud environment? And (3) Do you prefer to keep the data and applications on-premises? These three elements: IT asset ownership, management of the environment and location of data will ultimately influence the Cloud solution Cisco can help you build or buy. For many businesses, deploying a private cloud environment for all their applications is not necessarily the best path. And IT transformation does not always equal ubiquitous adoption of private cloud in your environment. Furthermore, there are many varieties of private cloud deployment models, including internal private clouds, hosted or virtual private clouds, and managed or outsourced private clouds. Each of these deployment options has very different financial, organizational, and technological implications. For example, let’s take Private Cloud deployments. If you want to retain ownership over your IT assets, manage your own Private Cloud and keep the data on prem we can help you build your own private cloud. Conversely, if you want to retain ownership of your IT assets, and you prefer to have a third party manage your private cloud, Cisco can help you do that depending on your vendor preferences. In this case, your sensitive data remains on-prem. This is particularly important for some customers concerned about data privacy. We offer Managed services offerings for private cloud environments and Cloud managed private cloud offerings based on OpenStack such as Cisco OpenStack Private Cloud (ex MetaCloud) depending on your use cases. Hosted and virtual private cloud solutions are also growing in popularity. These models are well suited to support infrastructure-as-a-service (IaaS) testing and development use cases. With hosted and virtual private cloud solutions, standardized IT services can be efficiently deployed in the public cloud. For IaaS, this single-tenant approach is inherently more secure compared to the multitenant public cloud services that most public cloud providers typically offer.
- Fabio speaker’s notes