Презентация 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
- Автор:неизвестен
Слайды и текст к этой презентации:
№3 слайд
![Why Docker? My World Needed](/documents_6/be19582f5029f3dce9201ed190b111b9/img2.jpg)
Содержание слайда: 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
№6 слайд
![Why Docker? LOCK IN! How](/documents_6/be19582f5029f3dce9201ed190b111b9/img5.jpg)
Содержание слайда: 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?
№14 слайд
![Why Is Docker Important?](/documents_6/be19582f5029f3dce9201ed190b111b9/img13.jpg)
Содержание слайда: 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
№16 слайд
![But Containers Aren t Enough!](/documents_6/be19582f5029f3dce9201ed190b111b9/img15.jpg)
Содержание слайда: 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
№18 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img17.jpg)
Содержание слайда: 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
№20 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img19.jpg)
Содержание слайда: 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
№22 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img21.jpg)
Содержание слайда: 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
№24 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img23.jpg)
Содержание слайда: 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
№26 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img25.jpg)
Содержание слайда: 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
№28 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img27.jpg)
Содержание слайда: 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
№30 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img29.jpg)
Содержание слайда: 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
№32 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img31.jpg)
Содержание слайда: 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
№34 слайд
![Drillinginfo Docker Platform](/documents_6/be19582f5029f3dce9201ed190b111b9/img33.jpg)
Содержание слайда: 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](/documents_6/be19582f5029f3dce9201ed190b111b9/img34.jpg)
Содержание слайда: 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
Скачать все slide презентации Running Your Services On Docker одним архивом:
Похожие презентации
-
Техніка безпеки. Електронна пошта. Урок 1
-
Топ 10 сайтов
-
Залогинивание
-
Концепция сайта кафе Авокадо
-
Правила участия в скайп-конференциях
-
Информационная кампания для родителей (законных представителей) ДДЮТ
-
Сервис Рука помощи на официальном сайте Череповца
-
Задача регистрации курсов (use case)
-
Социальная сеть деловых контактов SkillsNet (www. SkillsNet. ru)
-
Потребление в Интернете: преимущества и вызовы
-
Универсальные поисковые системы