Презентация Running Your Services On Docker онлайн

На нашем сайте вы можете скачать и просмотреть онлайн доклад-презентацию на тему Running Your Services On Docker абсолютно бесплатно. Урок-презентация на эту тему содержит всего 44 слайда. Все материалы созданы в программе PowerPoint и имеют формат ppt или же pptx. Материалы и темы для презентаций взяты из открытых источников и загружены их авторами, за качество и достоверность информации в них администрация сайта не отвечает, все права принадлежат их создателям. Если вы нашли то, что искали, отблагодарите авторов - поделитесь ссылкой в социальных сетях, а наш сайт добавьте в закладки.
Презентации » Интернет » Running Your Services On Docker



Оцените!
Оцените презентацию от 1 до 5 баллов!
  • Тип файла:
    ppt / pptx (powerpoint)
  • Всего слайдов:
    44 слайда
  • Для класса:
    1,2,3,4,5,6,7,8,9,10,11
  • Размер файла:
    2.20 MB
  • Просмотров:
    85
  • Скачиваний:
    0
  • Автор:
    неизвестен



Слайды и текст к этой презентации:

№1 слайд
Running Your Services On
Содержание слайда: Running Your Services On Docker Running Your Services On Docker

№2 слайд
Who Am I? Robert Bastian
Содержание слайда: Who Am I? Robert Bastian Director, Platform and Architecture at Drillinginfo 20+ years industry experience in Telcos, Gaming and Energy I love APIs and services! Agile and DevOps advocate

№3 слайд
Why Docker? My World Needed
Содержание слайда: Why Docker? My World Needed To Change 5+ individual teams building “micro services” in Java and Scala Frictionless deployment of “micro-services” using Chef & AWS 25+ separate “micro-services” deployed in the previous 18 months Each service is typically deployed to a single AWS virtual machine Each service is deployed 6x - dev, test, staging (2x) and production (2x) 25+ “micro-services” became nearly 150 AWS virtual machines

№4 слайд
Why Docker? COST! The AWS
Содержание слайда: Why Docker? COST! The AWS bill is too damn high! Decline in the global price of oil causing churn in our business 6 AWS virtual machines per service isn’t sustainable with our budget AWS monthly bill started to gain visibility from sr. management and the board

№5 слайд
Why Docker? WASTE! We weren t
Содержание слайда: Why Docker? WASTE! We weren’t using the compute and memory resources purchased from AMZN! Nearly all “micro-services” were at 1% CPU utilization Nearly all “micro-services’ were only using 40% of memory (JVM) 150+ virtual machines essentially sitting idle

№6 слайд
Why Docker? LOCK IN! How
Содержание слайда: Why Docker? LOCK IN! How would we leave AMZN if we wanted to? Could we use Drillinginfo IT’s Openstack platform? What about alternate IaaS providers like Rackspace or Azure? What about Container as a Service (CaaS) providers like Joyent, Tutum or Profitbricks? What about using Amazon’s Container Service?

№7 слайд
My World Needs To Change -
Содержание слайда: My World Needs To Change - Problem Statement “How can we deploy fewer virtual machines while increasing the density and utilization of services per machine without locking us into a specific IaaS provider?”

№8 слайд
How Docker Solves All The
Содержание слайда: How Docker Solves All The Problems

№9 слайд
Docker Containers - Shipping
Содержание слайда: Docker Containers - Shipping Matrix From Hell

№10 слайд
Docker Containers - Standard
Содержание слайда: Docker Containers - Standard Shipping Container

№11 слайд
What s Inside Doesn t Matter
Содержание слайда: What’s Inside Doesn’t Matter

№12 слайд
Why Docker Is Important -
Содержание слайда: Why Docker Is Important - Before Containers

№13 слайд
Why Docker Is Important -
Содержание слайда: Why Docker Is Important - After Containers

№14 слайд
Why Is Docker Important?
Содержание слайда: Why Is Docker Important? Docker container technology provides our “micro-services” platform: Increased density of isolated “micro-services” per virtual machine (9:1!) Containerized “micro-services” are portable across machines and providers Containerized “micro-services” are much faster than virtual machines

№15 слайд
Containers Alone Aren t Enough
Содержание слайда: Containers Alone Aren’t Enough

№16 слайд
But Containers Aren t Enough!
Содержание слайда: But Containers Aren’t Enough! Running containerized “micro-services” in production requires much more than just Docker. It requires a “Platform” that can do the following: Building and pushing Docker images to an image repository Pulling images, provisioning and scheduling containers Discovering and binding to services running as containers Containers discovering and binding to other containers Operating and managing services in containers

№17 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Build & Store Images

№18 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Jenkins & Dockerhub Problem: How do we build images? Jenkins automates the image builds. We started building our images with Ubuntu 14.04 (1GB) We settled on Alpine, a minimal linux distribution (5MB) Typical “micro-services” now ~ 390MB Problem: Where do we put them? Dockerhub. Tried Docker Trusted Registry and Core OS Enterprise Registry Settled on using Dockerhub Use latest and sem-ver tags on our images

№19 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Provisioning, Scheduling

№20 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Chef Problem: How do we determine which host to run a container on and how do we configure and start the container? We solve scheduling and provisioning with Chef. Chef schedules containers on specific hosts using Chef roles Chef provisions and configures containers using Chef recipes and environments Each “micro-service” has an associated Chef recipe that converts Chef attributes into container environment variables

№21 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Service Directory

№22 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Consul Problem: How do our browser applications locate service containers? We use Hashicorp’s Consul as our service directory. Containers automatically register themselves with Consul when started. The Docker daemon emits real-time lifecycle events for container start We use a utility container called Registrator to automate the registration of “micro-service” containers with Consul Containers are registered with a health check that Consul polls to determine the health of the container

№23 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Service Discovery

№24 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Consul Template Problem: How do our browser applications use services deployed in containers? We use Hashicorp’s Consul Template for service discovery and Varnish for load balancing. Consul Template detects containers in Consul and updates Varnish configuration Consul Template participates in the Consul cluster using Consul Client Consul Template automatically adds healthy containers and removes sick containers from the Varnish load balancer by updating Varnish configuration Browser applications use Varnish routes to reach services running in containers

№25 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Container Dependencies

№26 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Service Proxy Problem: How can containers find their containerized dependencies on the same host and different hosts? We use Consul, Nginx and Consul Template to implement a “Service Proxy” for inter and intra-host container communication. We built a utility container called “Service Proxy” that uses Consul’s service directory to locate a container's ip address and port “Service Proxy” then uses Consul Template to create an nginx.conf with load balanced routes for each service container Docker Links work for intra-host dependencies but with a gotcha

№27 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Operations & Monitoring

№28 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Operations & Monitoring Problem: How do we monitor containers and notify and escalate when containerized services aren’t healthy? We use Uptime and VictorOps monitor our containerized services. A utility container monitors Docker container lifecycle events and automatically registers a service check with Uptime when a container starts Uptime service interruptions to VictorOps for on-call scheduling, paging and escalation

№29 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform: Operations & Monitoring

№30 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Operations & Monitoring Problem: How do we monitor our Docker host’s resource usage? We use Datadog to monitor the Docker host utilization and the service’s metrics. Datadog helps us visualize the resource usage on a host Datadog helps us understand how our services are performing Datadog helps us understand how to “pack” containers onto hosts by exposing the current utilization of CPU and memory resources on the host

№31 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Overview

№32 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Wrap Up The Docker container technology and the Drillinginfo Docker Platform provide our “micro-services” infrastructure the following benefits: Reduced cost for IaaS hosting Reduced waste of virtual machine resources Standardized deployment mechanism for “micro-services” Standardized service directory, service discovery Standardized metrics dashboards, monitoring and alerting

№33 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Future Chef has gotten us where we are today but not where we want to be. Container orchestration Host provisioning and pooling

№34 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Orchestration Docker Compose will replace Chef roles defining the “micro-services” deployed on our platform and which Docker host they run on. The Docker Compose YAML file: Defines which containerized “micro-services” run on which host Define the environment variables for each container I believe that IaaS providers will standardize on Docker Compose for container orchestration.

№35 слайд
Drillinginfo Docker Platform
Содержание слайда: Drillinginfo Docker Platform - Provisioning & Pooling Docker Machine will replace Chef for provisioning virtual machines with Docker. Docker Machine automates the provisioning of Docker hosts Docker Swarm will replace Chef for scheduling containers on a host. Swarm combines Docker Machines into a single pool of compute and memory resources Swarm provides container scheduling and supports plug-in schedulers Docker Compose will define all the containers that run on the Swarm

№36 слайд
Running Your Services On
Содержание слайда: Running Your Services On Docker: Thank You! Questions?

№37 слайд
Contact Info Please feel free
Содержание слайда: Contact Info Please feel free to contact me with any additional questions or comments! Email: robert.bastian@drillinginfo.com LinkedIn: rbastian Twitter: @rbastian

№38 слайд
Running Your Services On
Содержание слайда: Running Your Services On Docker - Links https://www.docker.com/ https://hub.docker.com/ https://jenkins-ci.org/ https://www.chef.io https://www.consul.io/ https://github.com/gliderlabs/registrator https://hashicorp.com/blog/introducing-consul-template.html

№39 слайд
Содержание слайда:

№40 слайд
Synerzip in a Nutshell
Содержание слайда: Synerzip in a Nutshell

№41 слайд
Synerzip Clients
Содержание слайда: Synerzip Clients

№42 слайд
Next Webinar
Содержание слайда: Next Webinar

№43 слайд
Connect with Synerzip
Содержание слайда: Connect with Synerzip

№44 слайд
Running Your Services On
Содержание слайда: Running Your Services On Docker: Thank You! Questions?

Скачать все slide презентации Running Your Services On Docker одним архивом: