Slightly different version (original is here http://www.slideshare.net/d0cent/orchestrating-docker-containersatscale). This version was presented during first #Docker meetup in Kraków / Poland.
Container security involves securing containers at both the host and application level. At the host level, Linux technologies like namespaces, cgroups, SELinux, and seccomp provide isolation between containers. Container images are also scanned for vulnerabilities. The OpenShift platform provides additional security features like role-based access control, network policies, encrypted communications, and controls over privileged containers and storage. Application security best practices within containers include using HTTPS, securing secrets, and API management tools.
This document provides an introduction to Docker. It discusses key Docker concepts like OS virtualization using containers as opposed to virtual machines. Containers isolate processes and filesystems using cgroups, namespaces and UnionFS. Namespaces provide isolation for processes, networking, mounts etc. Cgroups are used to limit, account and isolate resource usage. The document also covers Docker storage and networking as well as security best practices.
Linux containers provide isolation between applications using namespaces and cgroups. While containers appear similar to VMs, they do not fully isolate applications and some security risks remain. To improve container security, Docker recommends: 1) not running containers as root, 2) dropping capabilities like CAP_SYS_ADMIN, 3) enabling user namespaces, and 4) using security modules like SELinux. However, containers cannot fully isolate applications that need full hardware or kernel access, so virtual machines may be needed in some cases.
A Gentle Introduction To Docker And All Things ContainersJérôme Petazzoni
Docker is a runtime for Linux Containers. It enables "separation of concern" between devs and ops, and solves the "matrix from hell" of software deployment. This presentation explains it all! It also explains the role of the storage backend and compares the various backends available. It gives multiple recipes to build Docker images, including integration with configuration management software like Chef, Puppet, Salt, Ansible. If you already watched other Docker presentations, this is an actualized version (as of mid-November 2013) of the thing!
Docker Networking - Common Issues and Troubleshooting TechniquesSreenivas Makam
This document discusses Docker networking components and common issues. It covers Docker networking drivers like bridge, host, overlay, topics around Docker daemon access and configuration behind firewalls. It also discusses container networking best practices like using user-defined networks instead of links, connecting containers to multiple networks, and connecting managed services to unmanaged containers. The document is intended to help troubleshoot Docker networking issues.
This document provides an overview of a talk about Docker. It introduces Docker features like images, containers, and the workflow. It describes how Docker uses namespaces and control groups for isolation. It compares Docker to virtual machines and explains why Docker is popular. The document then demonstrates Docker through a tutorial of pulling an image, running a container, and viewing container logs. It also discusses the Dockerfile for automating builds.
The document discusses potential issues that can occur with Docker containers and summarizes ways to address some of these issues in 3 sentences or less. It begins by explaining that Docker uses cgroups and namespaces to isolate resources and that exceeding limits of certain resources like open file handles or network interfaces can cause problems. It then summarizes that storage drivers like devicemapper and AUFS can impact disk performance, with AUFS utilizing page caching more efficiently. The document advocates for storage drivers like Btrfs that are more production ready.
What should be PID 1 in a container ? by Ranjith Rajaram for #rootConf 2017Ranjith Rajaram
The document discusses what process should be PID 1 inside a container. It explains that PID 1 has special responsibilities like reaping orphaned child processes and properly handling signals. The document evaluates different options for PID 1 like shell scripts, barebone init processes like Tini and Dumb-init, and systemd. It recommends using a minimal init process as PID 1 to ensure orphaned processes are reaped and signals are propagated correctly. This allows containers to be started and stopped gracefully.
Docker from A to Z, including Swarm and OCCSFrank Munz
This document provides an overview of Docker from A to Z including using Docker with Oracle Container Cloud Service. It discusses basics of Docker including how it provides isolation using Linux namespaces and cgroups. It compares Docker containers to virtual machines and covers Docker images, containers, limitations, networking, security concerns and suggestions. It also discusses using Docker with Oracle technologies including Dockerfiles on GitHub, the Oracle Container Registry, and Oracle Container Cloud Service.
Short Introduction to Docker. These slides show the basic idea behind the container technology Docker. The slides present the basic features for the daily use with Docker, Docker Compose, Docker Machine and Docker Swarm.
Docker is specially important for DevOps, because it gives Software Developers more control about their dependencies in different environments.
Introduction to Docker at SF Peninsula Software Development Meetup @GuidewiredotCloud
This document provides an introduction and overview of Docker and containers. It discusses that Docker is an open source tool that allows applications to be packaged with all their dependencies and run as isolated processes on any machine. Containers provide lightweight virtualization that improves efficiency by sharing resources but still isolating processes. The document outlines how Docker uses containers powered by Linux namespaces and cgroups to package and deploy applications easily and consistently across environments.
CONTAINERS WORKSHOP DURING SAUDI HPC 2016 : DOCKER 101, DOCKER, AND ITS ECO SYSTEM FOR DISTRIBUTED SYSTEMS by Walid Shaari
This workshop will cover the Theory and hands-on of Docker containers, and Its eco system. The foundations of the Docker platform, including an overview of the platform system components, images, containers and repositories, installation , using Docker containers from repositories e.g. dockerhub, how to create a container using Dockerfile, containers development life cycle. The strategy is to demonstrate through "live demo, and shared exercise" the reuse and customization of components to build a distributed system case service gradually
http://www.hpcsaudi.com/
1. The document discusses Docker's roadmap which includes standardizing interfaces for container sandboxing (libcontainer), communication between containers and components (libchan), and orchestrating distributed services (libswarm).
2. It announces libcontainer becoming a standalone project and new contributors joining its development. Libchan is introduced as a lightweight communication protocol and libswarm is presented as a toolkit for composing network services.
3. Identity and authorization are mentioned as upcoming areas of focus, and the document encourages participation in developing these Docker projects.
This document introduces Docker and provides an overview of its key features and benefits. It explains that Docker allows developers to package applications into lightweight containers that can run on any Linux server. Containers deploy instantly and consistently across environments due to their isolation via namespaces and cgroups. The document also summarizes Docker's architecture including storage drivers, images, and the Dockerfile for building images.
Introduction to Containers - SQL Server and DockerChris Taylor
Containers provide lightweight virtualization that packages applications and dependencies together. The document introduces containers and Docker, discusses the differences between containers and virtual machines, and covers key Docker concepts like images, Dockerfiles, Docker Hub, and running SQL Server in containers. It also addresses container setup, licensing, and performance considerations for using containers with SQL Server.
Docker allows for the delivery of applications using containers. Containers are lightweight and allow for multiple applications to run on the same host, unlike virtual machines which each require their own operating system. Docker images contain the contents and configuration needed to run an application. Images are built from manifests and layers of content and configuration are added. Running containers from images allows applications to be easily delivered and run. Containers can be connected to volumes to preserve data when the container is deleted. Docker networking allows containers to communicate and ports can be exposed to the host.
Overview of Docker 1.11 features(Covers Docker release summary till 1.11, runc/containerd, dns load balancing ipv6 service discovery, labels, macvlan/ipvlan)
Introduction to Docker, December 2014 "Tour de France" Bordeaux Special EditionJérôme Petazzoni
Docker, the Open Source container Engine, lets you build, ship and run, any app, anywhere.
This is the presentation which was shown in December 2014 for the last stop of the "Tour de France" in Bordeaux. It is slightly different from the presentation which was shown in the other cities (http://www.slideshare.net/jpetazzo/introduction-to-docker-december-2014-tour-de-france-edition), and includes a detailed history of dotCloud and Docker and a few other differences.
Special thanks to https://twitter.com/LilliJane and https://twitter.com/zirkome, who gave me the necessary motivation to put together this slightly different presentation, since they had already seen the other presentation in Paris :-)
Docker is a technology that uses lightweight containers to package applications and their dependencies in a standardized way. This allows applications to be easily deployed across different environments without changes to the installation procedure. Docker simplifies DevOps tasks by enabling a "build once, ship anywhere" model through standardized environments and images. Key benefits include faster deployments, increased utilization of resources, and easier integration with continuous delivery and cloud platforms.
This document discusses Docker security. It begins by introducing Docker and containers, then covers securing Docker images through signing and scanning. It discusses how Docker uses namespaces and cgroups for isolation. It also addresses securing the Docker daemon and containers, as well as operational concerns around deployment, networking, monitoring, and logging of containers. It concludes by looking at future directions like unikernels and serverless architectures.
Este documento define los conceptos de riesgo, riesgo estático, riesgo dinámico, riesgo común, riesgo ocupacional y riesgo profesional. Explica que un riesgo es la posibilidad de sufrir un daño y clasifica los riesgos según si su probabilidad de ocurrencia depende de la actitud de la persona expuesta o de la energía cinética de un objeto, y según si la exposición ocurre en actividades cotidianas, trabajo sin vínculo contractual o trabajo con vínculo laboral.
28ª semana del tiempo ordinario. Domingo A: Mt 22, 1-14P Sabana Grande
Jesús cuenta la parábola de un rey que prepara un gran banquete de bodas para su hijo, pero los invitados iniciales se niegan a asistir. El rey entonces invita a cualquier persona que encuentre, buena o mala. Esta parábola enseña que el Reino de Dios es como un banquete al que Dios invita a todos, pero se requiere estar preparado y vestido adecuadamente para participar.
El documento presenta los cálculos estructurales para la remodelación de una Escuela de Enfermería en la región de Los Lagos. Describe el proyecto, los materiales utilizados como hormigón y acero, los parámetros sísmicos y de suelo considerados, y los métodos de análisis y diseño estructural utilizados como el software SAP2000 y códigos como la NCh 433. Finalmente, presenta ejemplos de verificación de elementos como marcos metálicos y cerchas.
The document summarizes the construction and early history of the Berlin Wall from 1961 to the 1960s. It describes how on August 13, 1961 soldiers started building the wall with barbed wire and fencing to divide East and West Berlin. Over time, it developed into a heavily fortified border with walls, fences, guard towers, and checkpoints. More than 100,000 East Germans tried to escape to the West between 1961 and 1988, with over 600 being shot and killed during escape attempts. Photos from LIFE magazine show the wall's construction and impact on dividing the city and its residents.
Este documento describe la anatomía y fisiología de las vías biliares y la vesícula biliar, así como patologías como la litiasis biliar y la colecistitis aguda. Explica los conductos hepáticos, el triángulo de Calot, y proporciona detalles sobre la vesícula biliar, la formación de cálculos, sus complicaciones y el diagnóstico de la colecistitis aguda.
Este documento presenta un examen de física elemental sobre conceptos básicos de movimiento para estudiantes de primer grado de secundaria. Consiste en tres secciones: 1) relacionar términos de movimiento con sus definiciones, 2) completar frases con palabras relacionadas al movimiento extraídas de un crucigrama, y 3) dibujar ejemplos de diferentes tipos de movimiento. El examen evalúa la comprensión básica de conceptos como posición, velocidad, sistemas de referencia, y diferentes tipos de trayectorias de movimiento
1.CALIGRAFÍA EN EL DISEÑO GRÁFICOPrimer ParcialProfesor Elid Hernández AvilésAlejandra Herrera
Rosales
2. Historia: Los orígenes de Apple se remontan al 1976 cuando Steven P. Jobs y Stephen G.Wozniak instalaron un taller en el garaje de la casa del padre de Jobs en Cupertino,California. Jobs vendió su van Volkswagen y Wozniak vendió su calculadora programable para financiar la fabricación de los primeros 50 circuitos del ordenador Apple I. Jobs buscó el consejo de varios industriales de éxito. Entre ellos se encontraba Mike Markkula, que redactó los fundamentos de la nueva empresa y oficialmente se incorporó a ella como socio y presidente cuando la misma fue reconocida oficialmente en enero de1977. Crearon un logotipo, el primer logotipo multicolor que atraía las miradas y que hoy en día sigue siendo uno de los logotipos más reconocidos. En los cuatro años siguientes la industria del computador personal prospera rápidamente. En 1983 Apple ingresó en la lista de Fortune 500 (que agrupa a las compañías de mayor suceso en los Estados Unidos) y adicionalmente ganó renombre en Wall Street al designar al entonces presidente de Pepsi-Cola, John Sculley como su nuevo director ejecutivo. Hombre que en un futuro, despedirá a Jobs.
El 23 de octubre de 2001, Apple anunció el iPod (reproductor portàtil de audio digital) , y comenzó a venderlo el 10 de noviembre. El producto fue un éxito fenomenal. Más de 100 millones de unidades fueron vendidas en los seis años. El 9 de Enero de 2007, Jobs anunció que Apple Computer, Inc. que a partir de entonces se conoce como Apple Inc., ya que los equipos ya no eran el objetivo principal de la empresa, que había cambiado su énfasis en dispositivos electrónicos móviles. El evento también vio el anuncio del iPhone y el Apple TV. Al día siguiente, las acciones de Apple alcanzó los US $ 97.80, un máximo histórico en ese punto.
En octubre de 2010, las acciones de Apple alcanzaron un máximo histórico, superando US $ 300. Además, el 20 de octubre, Apple actualiza su MacBook Air portátiles, iLife suite de aplicaciones, y dio a conocer Mac OS X Lion. El 6 de enero de 2011, la compañía abrió su Mac App Store, una plataforma de software de distribución digital, similar a la existente iOS App Store.
3.Usos y Aplicaciones
4.Conceptos Relacionados: Innovación
Simpleza
Originalidad
Elegancia
Calidad
Exclusivo
5.Argumentación: El estilo caligráfico que se expone se escogió después de una serie de bocetos e ideas intentando crear una nueva tipografía caligráfica para Apple totalmente lo opuesto a la actual. Es tambien por esa razon que se utilizó la figura retórica de hipérbole, que es donde se exagera la idea original creando una idea completamente diferente o lo contrario a esta.
6.Bocetos
7.Comparación
8.Aplicaciones
This document summarizes a simulation study examining the transmembrane transport of poly(amidoamine) (PAMAM) dendrimers across a lipid bilayer. The study modifies an existing dissipative particle dynamics (DPD) model to include receptor molecules in the bilayer. It analyzes how changes to the soft-core repulsion parameters between dendrimer beads, receptor beads, and lipid tails affect binding and penetration. The simulations found that including receptor molecules did not disrupt bilayer self-assembly. Binding and penetration were affected by an attractive interaction between receptors and ligands coupled with changes to repulsion parameters. For certain parameters, encapsulation of the dendrimer by the bilayer was observed, resembling a phagocytic
Equity and Transparency in the New Province of HumanityValnora Leister
This document summarizes Valnora Leister's presentation on ensuring equity and transparency in outer space activities. Leister argues that leading space powers prioritize national military and economic aims over benefiting humanity. She outlines four paths to expand global participation in space: 1) engage civil society, 2) work with emerging space powers, 3) apply principles of international environmental law, and 4) use new governance concepts like "economic governance" and "charter cities" to ensure equity and transparency in shared space resources. Leister concludes that developing a "Universal Law of Humanity" could help realize outer space as the "New Province of Mankind" by replacing the current system based on state supremacy.
Universidad nacional de chimborazo.docx periferitos de entaradajhon pintag
Este documento presenta una lista y breve descripción de varios dispositivos de entrada comunes para computadoras. Algunos de los dispositivos mencionados incluyen teclados, ratones, micrófonos, escáneres, cámaras web, lápices ópticos y controles de juego. Cada dispositivo convierte una forma de entrada como texto, imágenes o sonido en señales digitales que pueden ser procesadas por una computadora.
This document discusses strategies for breaking down taboos around discussing death, money, and legacy fundraising. It explores using humor, social norming by showing many others participate in legacy giving, telling stories of living donors, sharing a vision of the future impact of a gift, appealing to symbolic immortality and a donor's desire to continue their impact after death. Research is presented showing that providing social information on others' participation can increase intentions to leave a legacy gift. Overall, the document examines how charities can overcome emotional and conversational prohibitions to have more open and impactful conversations about legacy fundraising.
Citations needed for the sum of all human knowledge: Wikidata as the missing ...Dario Taraborelli
This document discusses Wikidata and WikiCite's role as central hubs for open knowledge and citations. It notes that Wikidata is a free knowledge base with over 20 million items and 100 million statements that is edited by volunteers. WikiCite aims to build a repository of citations from Wikimedia projects to improve coverage, quality and machine-readability of citations. Examples are given of using Wikidata and SPARQL to query biomedical information and citations. Challenges and opportunities are discussed around expert curation, open data, and accelerating impact of open access.
This document repeatedly promotes "For Consulting & Business Solutions" over multiple lines without providing any other details. It concludes by thanking the reader but does not specify what the thanks is for.
Nestor Garcia Tayag Jr. passed away on September 20, 2010. In a letter to Ninong, the author expresses gratitude for all he has done and the love he gave. They remark that Ninong faced many hardships but always seemed to smile, and was one of the strongest men they knew. The author and others regret not getting to say "I love you" one last time or see him before he passed. Though sad about his passing, the author takes comfort knowing Ninong is in a better place without pain.
This document provides guidance for student organization advisors at Babson College. It outlines the general responsibilities of advisors which include understanding the group's mission, empowering students, being aware of policies, and helping students develop leadership skills. It also details specific expectations such as maintaining contact with students and attending meetings. Additionally, it provides resources for student groups, including offices for funding, event planning, catering, printing and public safety contacts. The document aims to prepare advisors to support their student organizations effectively.
This document provides information about various animals and their abilities, as well as lessons about being grateful to God. It discusses how different birds fly, how ants farm fungus, and special adaptations of penguins, koalas and camels. It emphasizes that God created each species perfectly for their environment and needs. The document concludes with messages about loving God and expressing gratitude for His blessings, being honest, and complying with His moral teachings.
Global CCS Institute - Day 1 - Panel 2 - CCS in Developing CountriesGlobal CCS Institute
The document discusses CCS projects in developing countries. It notes that of the 75 large-scale CCS projects globally, 17 are in developing countries, including 11 in China, 2 in Korea, and 3 in the United Arab Emirates. The Global CCS Institute provides support to build capacity for CCS in several developing countries, including Brazil, China, India, Indonesia, Malaysia, Mexico, South Africa, and Trinidad and Tobago.
Dockerizing Symfony2 application. Why Docker is so cool And what is Docker? And what are Containers? How they works? What are the ecosystem of Docker? And how to dockerize your web application (can be based on Symfony2 framework)?
VMware@Night Container and VirtualizationOpvizor, Inc.
The last VMware@Night in Zurich had Container on top of Virtualization as a headline. Urs Alder, Michael Abmayer and Dennis Zimmer (CEO, Opvizor) presented how to plan, use and monitor Docker (Container) on top of VMware vSphere or other virtualization solutions.
www.opvizor.com
Mit Urs Stephan Alder (CEO Kybernetika), Michael Abmayer (Senior Consultant Opvizor) und Dennis Zimmer (CEO Opvizor) präsentierten gleich 3 hochkarätige Referenten an der vergangenen VMware@Night bei Digicomp. Sie zeigten zusammen auf, welche Auswirkungen Container in der Virtualisierung auf den täglichen Betrieb sowie die Performance- und Kapazitätsplanung haben.
Vor allem Docker ist derzeit in aller Munde und die bekannteste und meist genutzte Container-Technologie. Container werden vielfach in virtuellen Maschinen betrieben und stellen eine neue Herausforderung für VMware- Administratoren, aber auch IT-Manager dar. Gewährleistung und Überwachung der Performance sowie eine möglichst genaue Kapazitätsplanung sind Herausforderungen, denen man sich zügig stellen muss.
Nach einer kurzen Einführung in die Thematik der Container, in der auch die Unterschiede zur Virtualisierung aufgezeigt wurde, widmeten sich die Referenten dem Umgang mit Conteinern am Beispiel von Docker mit VMware vSphere. Zum Abschluss wurde die Performanceüberwachung und Kapazitätsplanung behandelt.
Docker Seattle Meetup April 2015 - The Docker Orchestration Ecosystem on AzurePatrick Chanezon
This document discusses the Docker ecosystem and provides an overview of containerization technologies. It covers the history of containerization from mainframes in the 1960s to Docker in 2013. It discusses Docker's success due to cloud adoption, portability, and hybrid environments. It outlines the Docker ecosystem including Docker Engine, Docker Hub, Docker Machine, Docker Compose, Docker Swarm, and Kitematic. It also discusses companies in the Docker ecosystem like Docker Inc., CoreOS, Deis, Kubernetes, Cloud Foundry/IBM Bluemix, and others.
We have HAX / ELMS:LN DevOps Lead Michael Potter to talk about Docker and container technology. This is one of the most difficult concepts to grasp because of the layers of abstraction involved but we're going to work through a playground called Play with Docker and great directions from Mike to get going.
Docker New York Meetup May 2015 - The Docker Orchestration Ecosystem on Azure Patrick Chanezon
Docker Inc. provides products and services for managing containers. The Docker ecosystem includes open source tools for building, shipping, and running applications packaged into containers. Key components include Docker Engine for building containers, Docker Hub for sharing container images, and orchestration tools like Docker Swarm and Kubernetes for deploying containers across multiple hosts. Many companies are developing technologies that work with Docker to provide additional container management capabilities.
Docker San Francisco Meetup April 2015 - The Docker Orchestration Ecosystem o...Patrick Chanezon
The document discusses the Docker ecosystem including:
- The history and components of Docker including the Docker Engine, Hub, Machine, Compose, and Swarm.
- How Docker provides isolation using Linux kernel features like namespaces and cgroups.
- Other projects in the Docker ecosystem like Weave, Flocker, and Powerstrip.
- Orchestration tools like Docker Swarm and Kubernetes that manage Docker containers across multiple hosts.
- Platforms that are built on Docker like CoreOS, Deis, Cloud Foundry, and IBM Bluemix.
This document discusses containerization and the Docker ecosystem. It provides a brief history of containerization technologies and an overview of Docker components like Docker Engine, Docker Hub, and Docker Inc. It also discusses developing with Docker through concepts like Dockerfiles, images, and Fig for running multi-container apps. More advanced topics covered include linking containers, volumes, Docker Machine for provisioning, and clustering with Swarm and Kubernetes.
From Monolith to Docker Distributed ApplicationsCarlos Sanchez
Docker is revolutionizing the way people think about applications and deployments. It provides a simple way to run and distribute Linux containers for a variety of use cases, from lightweight virtual machines to complex distributed microservice architectures. But migrating an existing Java application to a distributed microservice architecture is no easy task, requiring a shift in the software development, networking, and storage to accommodate the new architecture. This presentation provides insights into the experience of the speaker and his colleagues in creating a Jenkins platform based on distributed Docker containers running on Apache Mesos and Marathon and applicable to all types of applications, especially Java- and JVM-based ones.
V1. This document introduces Vagrant and Docker, tools for efficiently building and running virtual machines and containers. It discusses how Vagrant can be used to create standardized development environments and Docker allows building and sharing applications and their dependencies.
V2. The document then covers how to install, access, customize, and provision Vagrant virtual machines as well as how to build, run, network, and manage Docker containers and images.
V3. Advanced topics discussed include linking containers, using Docker Compose for orchestration, the Docker Hub registry, security considerations, and other Docker tools like Machine for provisioning remote hosts and Swarm for clustering.
This summarizes the key points from DockerCon 2016 based on a presentation by Philipp Garbe:
1. Docker 1.12 introduced built-in orchestration capabilities including swarm mode, routing mesh, and a new service API for desired state reconciliation and scheduling.
2. Demos showed deploying an app using the new service command, scaling the app, performing rolling updates, and rescheduling tasks after node failures.
3. Other announcements included Docker for Mac/Windows public betas, Docker Store for publishing content, and Docker DataCenter for deploying applications to AWS and Azure.
Docker-Hanoi @DKT , Presentation about Docker EcosystemVan Phuc
The document provides an overview of Docker Platform and Ecosystem. It begins with introductions and background on Docker, explaining how Docker solves the problem of dependency hell and portability issues by allowing applications to run in isolated containers that package code and dependencies. It then discusses key components of Docker including Engine, Registry, Machine, Swarm, Compose and tools like Toolbox and Cloud. The document concludes with examples of using Docker for continuous integration pipelines and microservices architectures.
Sebastien goasguen cloud stack and dockerShapeBlue
This document discusses how Docker can be used with CloudStack. It provides several options: 1) Running Docker in VMs on CloudStack templates that include Docker, 2) Using Docker-optimized OS templates, 3) Launching containers through a container service API, 4) Using CloudStack plugins within the Docker ecosystem like Docker Machine. The document concludes that CloudStack should not try to write a Docker hypervisor plugin, but instead focus on Docker-optimized OS templates and deploying application frameworks to orchestrate Docker.
- Docker is a platform for building, shipping and running applications. It allows applications to be quickly assembled from components and eliminates discrepancies between development and production environments.
- Docker provides lightweight containers that allow applications to run in isolated environments called containers without running a full virtual machine. Containers are more portable and use resources more efficiently than virtual machines.
- Docker Swarm allows grouping Docker hosts together into a cluster where containers can be deployed across multiple hosts. It provides features like service discovery, load balancing, failure recovery and rolling updates without a single point of failure.
The document provides an overview of the Docker ecosystem, including its definition, architecture, and status. It describes how Docker allows for applications to be bundled and run in a portable way across various environments using containers. The key components of Docker like images, containers, registries, and Dockerfiles are explained. The document also discusses the container ecosystem and adoption of Docker by various companies and projects. It outlines the security features and best practices for containers. Finally, it provides a brief history of resource management capabilities in Linux that enabled and influenced the development of containers.
This document provides an overview of Docker, including its history and community, what it is, how it compares to virtual machines and native environments, its internal architecture involving images, layers and containers, common use cases, and a demonstration of basic Docker commands. Docker is an open source platform for automating application development by packaging applications into containers that can be easily built, shipped and run on any infrastructure. It provides portability and versioning of applications with minimal overhead compared to virtual machines.
- Docker can be integrated with CloudStack in several ways, including running Docker in CloudStack virtual machine guests, packaging CloudStack as Docker containers, and using Docker orchestrators to manage containers.
- CloudStack could potentially be re-architected to run its components in Docker containers and use Docker networking for isolation, with an orchestrator like Mesos or Kubernetes managing the CloudStack application.
- There are open questions around whether CloudStack or other orchestrators should schedule virtual machines or containers as the primary compute resource in a private cloud data center.
This document discusses containers, virtual machines, and Docker. It provides an overview of containers and how they differ from virtual machines by sharing the host operating system kernel and making more efficient use of system resources. The document then covers Docker specifically, explaining that Docker uses containerization to package applications and dependencies into standardized units called containers. It also provides examples of Docker commands to build custom images and run containers.
This document provides an overview of Docker for web developers. It defines Docker as a platform for developing, shipping and running applications using container virtualization technology. It describes the main Docker products and tools. It provides examples of using Docker for various programming languages and frameworks like PHP, Java, Python, Node.js, Go, databases and content management systems like WordPress, Joomla and Drupal. The document also discusses Dockerfiles, Docker Compose, Docker commands and repositories.
Similar to Orchestrating docker containers at scale (#DockerKRK edition) (20)
Programowanie AWSa z CLI, boto, Ansiblem i libcloudemMaciej Lasyk
The document describes a session that demonstrates how to program AWS using the AWS CLI, Boto, and Ansible. It provides an agenda for the session that includes a short AWS introduction, demonstrations of the AWS console, AWS CLI, AWS shell, Boto library, Ansible configuration management tool, and Libcloud library. Contact information is also provided for learning more about AWS programming and joining the training organization.
Under the Dome (of failure driven pipeline)Maciej Lasyk
The document discusses various topics related to DevOps including:
1. Different types of shells (login, non-login, interactive, non-interactive, su, sudo su, sudo -i, sudo /bin/bash, sudo -s) and how they affect environment variables and profile files.
2. Stories of organizational "anti-types" that go against DevOps principles like not seeing the need for operations teams.
3. How automation, consistency, and reducing errors leads to stable environments and less unplanned work, allowing teams to focus on delivery.
This document discusses integrating security into DevOps practices through continuous delivery. It proposes including security automation and monitoring at each stage of the software development pipeline from development through production. Specific techniques mentioned include performing continuous security scanning, integrating security testing with other testing stages, automating security tasks using tools like Ansible, and sharing security data and lessons learned across teams to improve processes over time. The overall message is that security should be built into delivery rather than treated separately to avoid slowing software releases while still maintaining quality.
This document contains a list of various tools related to terminals, privacy, communication, productivity, and mobile topics. It discusses terminal emulators like guake and iterm2, VPN services like OpenVPN, messaging clients like IRC and XMPP, note taking apps like Evernote and Geeknote, and more. It concludes by inviting questions about any of the topics mentioned.
High Availability (HA) Explained - second editionMaciej Lasyk
I gave this talk at one of the biggest Linux conferences in Poland: 11 Liux Session that took place in Wrocław on 5/6-04-2014. It was a lightning talk covering subject of High Availability solutions, architecture, planning and deploying.
How could one create very sophisticated, open - source based monitoring solution that is very scalable and easy to deploy?
I gave this talk during on of the biggest Linux conferences in Poland: 11 Linux Session which took place in Wrocław on 5/6-04-2013
I gave this talk during first Infosec meetup in Kraków/Poland on 13th March 2014. After viewing this presentation you'll know how and why you should use SELinux (or others LSMs).
I gave this talk at Krakow/Poland DevOPS meetup. It was a lightning talk covering subject of High Availability solutions, architecture, planning and deploying.
How to run system administrator recruitment process? By creating platform based on open source parts in just 2 nights! I gave this talk in Poland / Kraków OWASP chapter meeting on 17th Octomber 2013 at our local Google for Entrepreneurs site. It's focused on security and also shows how to create recruitment process in CTF / challenge way.
This story covers mostly security details of this whole platform. There's great chance, that I will give another talk about this system but this time focusing on technical details. Stay tuned ;)
How to run system administrator recruitment process? By creating platform based on open source parts in just 2 nights! I gave this talk in Poland / Kraków OWASP chapter meeting on 17th October 2013 at our local Google for Entrepreneurs site. It's focused on security and also shows how to create recruitment process in CTF / challenge way.
This story covers mostly security details of this whole platform. There's great chance, that I will give another talk about this system but this time focusing on technical details. Stay tuned ;)
Book dating , international dating phgrathomaskurtha9
International dating programhttps: please register here and start to meet new people todayhttps://www.digistore24.com/redir/384521/godtim/.
get started. https://www.digistore24.com/redir/384521/godtim/
Have you ever built a sandcastle at the beach, only to see it crumble when the tide comes in? In the digital world, our information is like that sandcastle, constantly under threat from waves of cyberattacks. A cybersecurity course is like learning to build a fortress for your information!
This course will teach you how to protect yourself from sneaky online characters who might try to steal your passwords, photos, or even mess with your computer. You'll learn about things like:
* **Spotting online traps:** Phishing emails that look real but could steal your info, and websites that might be hiding malware (like tiny digital monsters).
* **Building strong defenses:** Creating powerful passwords and keeping your software up-to-date, like putting a big, strong lock on your digital door.
* **Fighting back (safely):** Learning how to identify and avoid threats, and what to do if something does go wrong.
By the end of this course, you'll be a cybersecurity champion, ready to defend your digital world and keep your information safe and sound!
Tama Tonga MFT T shirts Tama Tonga MFT T shirtsexgf28
Tama Tonga MFT T shirts
https://www.pinterest.com/youngtshirt/tama-tonga-mft-t-shirts/
Tama Tonga MFT T shirts,Tama Tonga MFT shirt,Tama Tonga MFT Sweatshirts,MFT T shirts Grabs yours today. tag and share who loves it.
The advent of social media has revolutionized communication, transforming the way people connect, share, and interact globally. At the forefront of this digital revolution are visionary entrepreneurs who recognized the potential of the internet to foster social connections and create communities. This essay explores the founders of some of the most influential social media platforms, their journeys, and the lasting impact they have made on society.
Mark Zuckerberg, along with his college roommates Eduardo Saverin, Andrew McCollum, Dustin Moskovitz, and Chris Hughes, founded Facebook in 2004. Initially created as a social networking site for Harvard University students, Facebook rapidly expanded to other universities and eventually to the general public. Zuckerberg's vision was to create an online directory that connected people through their real-life social networks.
Twitter, founded in 2006 by Jack Dorsey, Biz Stone, and Evan Williams, brought a new dimension to social media with its microblogging platform. Dorsey envisioned a service that allowed users to share short, real-time updates, limited to 140 characters (now 280). This concise format encouraged rapid sharing of information and fostered a culture of brevity and immediacy.
Kevin Systrom and Mike Krieger co-founded Instagram in 2010, focusing on photo and video sharing. Systrom, who studied photography, wanted to create an app that made mobile photos look professional. The app's unique filters and easy-to-use interface quickly gained popularity, amassing over a million users within two months of its launch.
Instagram's emphasis on visual content has had a significant cultural impact. It has popularized the concept of influencers, giving rise to a new industry where individuals can monetize their popularity and reach. The platform has also revolutionized digital marketing, enabling brands to connect with consumers in more authentic and engaging ways. Acquired by Facebook in 2012, Instagram continues to be a dominant force in social media, shaping trends and cultural norms.
Reid Hoffman founded LinkedIn in 2002 with the goal of creating a professional networking platform. Unlike other social media sites focused on personal connections, LinkedIn was designed to connect professionals, facilitate job searches, and foster business relationships. The platform allows users to create professional profiles, network with colleagues, and share industry insights.
LinkedIn has become an indispensable tool for job seekers, recruiters, and businesses. It has transformed the job market by making it easier to find and connect with potential employers and employees. LinkedIn's influence extends beyond job searches; it has become a hub for professional development, thought leadership, and industry news. Hoffman's vision has significantly impacted how professionals manage their careers and build their networks.
Jan Koum and Brian Acton co-founded WhatsApp in 2009, aiming to create a simple, reliable..
2. Maciej Lasyk, Docker containers at scale
Maciej Lasyk
#DockerKRK meetup 1
Kraków, 2015-01-28
1/64
Orchestrating Docker containers at scale
3. Maciej Lasyk, Docker containers at scale 2/64
Join Fedora Infrastructure!
- learn Ansible
- learn Docker with Fedora Dockerfiles
http://fedoraproject.org/en/join-fedora
4. Maciej Lasyk, Docker containers at scale 3/64
- Why use Docker?
- Brief history of envs evolution
- Docker – what is it?
- To PaaS or not to PaaS
- Orchestration at scale
Agenda
6. Maciej Lasyk, Docker containers at scale
- How many of you...
- Knows what Docker is?
Quick survey
4/64
7. Maciej Lasyk, Docker containers at scale
- How many of you...
- Knows what Docker is?
- Played with Docker?
Quick survey
4/64
8. Maciej Lasyk, Docker containers at scale
- How many of you...
- Knows what Docker is?
- Played with Docker?
- Runs it on production?
Quick survey
4/64
9. Maciej Lasyk, Docker containers at scale 5/64
With Docker we can solve many problems
Why use Docker?
10. Maciej Lasyk, Docker containers at scale
With Docker we can solve many problems
- “it works on my machine”
Why use Docker?
5/64
11. Maciej Lasyk, Docker containers at scale
With Docker we can solve many problems
- “it works on my machine”
- reducing build & deploy time
Why use Docker?
5/64
12. Maciej Lasyk, Docker containers at scale
With Docker we can solve many problems
- “it works on my machine”
- reducing build & deploy time
- Infrastructure configuration spaghetti – automation!
Why use Docker?
5/64
13. Maciej Lasyk, Docker containers at scale
With Docker we can solve many problems
- “it works on my machine”
- reducing build & deploy time
- Infrastructure configuration spaghetti – automation!
- Libs dependency hell
Why use Docker?
5/64
14. Maciej Lasyk, Docker containers at scale
With Docker we can solve many problems
- “it works on my machine”
- reducing build & deploy time
- Infrastructure configuration spaghetti – automation!
- Libs dependency hell
- Cost control and granularity
Why use Docker?
5/64
15. Maciej Lasyk, Docker containers at scale 6/64
- classical approach (for & scp/ssh & conf.d)
A brief story of envs evolution
16. Maciej Lasyk, Docker containers at scale
- classical approach (for & scp/ssh & conf.d)
- configuration management
A brief story of envs evolution
6/64
17. Maciej Lasyk, Docker containers at scale
- classical approach (for & scp/ssh & conf.d)
- configuration management
- Bare vs IaaS vs PaaS
A brief story of envs evolution
6/64
18. Maciej Lasyk, Docker containers at scale
- classical approach (for & scp/ssh & conf.d)
- configuration management
- Bare vs IaaS vs PaaS
- Continuous Integration
A brief story of envs evolution
6/64
19. Maciej Lasyk, Docker containers at scale
- classical approach (for & scp/ssh & conf.d)
- configuration management
- Bare vs IaaS vs PaaS
- Continuous Integration
- So when to use Docker?
A brief story of envs evolution
6/64
21. Maciej Lasyk, Docker containers at scale 8/64
“automates the deployment of any
application as a lightweight, portable,
self-sufficient container
that will run virtually anywhere”
Docker – what is it?
22. Maciej Lasyk, Docker containers at scale 9/64
Java’s promise: Write Once. Run Anywhere.
Docker – what is it?
23. Maciej Lasyk, Docker containers at scale
Java’s promise: Write Once. Run Anywhere.
Docker – what is it?
Even on Windows now!
https://blog.docker.com/2014/10/docker-microsoft-partner-distributed-applications/
9/64
24. Maciej Lasyk, Docker containers at scale 10/64
Docker – what is it?
Docker is lightweight
25. Maciej Lasyk, Docker containers at scale
======================================================
Package Arch Version Repository Size
======================================================
Installing:
docker-io x86_64 1.3.0-1.fc20 updates 4.3 M
Docker – what is it?
Docker is lightweight
10/64
26. Maciej Lasyk, Docker containers at scale 11/64
Docker – what is it?
http://sattia.blogspot.com/2014/05/docker-lightweight-linux-containers-for.html
27. Maciej Lasyk, Docker containers at scale 12/64
Docker – how it works?
http://blog.docker.com/2014/03/docker-0-9-introducing-execution-drivers-and-libcontainer/
28. Maciej Lasyk, Docker containers at scale 13/64
- LXC & libcontainer
Docker – how it works?
29. Maciej Lasyk, Docker containers at scale 13/64
- LXC & libcontainer
- control groups
Docker – how it works?
30. Maciej Lasyk, Docker containers at scale 13/64
- LXC & libcontainer
- control groups
- kernel namespaces
Docker – how it works?
31. Maciej Lasyk, Docker containers at scale 13/64
- LXC & libcontainer
- control groups
- kernel namespaces
- layered filesystem
- btrfs
- devmapper thin provisioning & loopback mounts
- no more AUFS
- http://developerblog.redhat.com/2014/09/30/overview-storage-scalability-docker/
Docker – how it works?
32. Maciej Lasyk, Docker containers at scale 14/64
- images
- read only
- act as templates
Docker – concepts
33. Maciej Lasyk, Docker containers at scale 14/64
- images
- read only
- act as templates
- Dockerfile
- like a makefile
- commands order & cache'ing
- extends the base image
- results in a new image
Docker – concepts
34. Maciej Lasyk, Docker containers at scale 14/64
- images
- read only
- act as templates
- Dockerfile
- like a makefile
- commands order & cache'ing
- extends the base image
- results in a new image
- Containers: instances running apps
Docker – concepts
35. Maciej Lasyk, Docker containers at scale 14/64
- images
- read only
- act as templates
- Dockerfile
- like a makefile
- commands order & cache'ing
- extends the base image
- results in a new image
- Containers: instances running apps
Docker – concepts
dockerfile + base image = docker container
36. Maciej Lasyk, Docker containers at scale 15/64
FROM fedora
MAINTAINER scollier <scollier@redhat.com>
RUN yum -y update && yum clean all
RUN yum -y install nginx && yum clean all
RUN echo "daemon off;" >> /etc/nginx/nginx.conf
RUN echo "nginx on Fedora" > /srv/www/index.html
EXPOSE 80
CMD [ "/usr/sbin/nginx" ]
Dockerfile
37. Maciej Lasyk, Docker containers at scale 16/64
Docker – registry
http://osv.io/blog/blog/2014/06/19/containers-hypervisors-part-2/
38. Maciej Lasyk, Docker containers at scale 17/64
Docker – registry
- git like semantics
- pull, push, commit
- private and public registry
- https://github.com/dotcloud/docker-registry
- yum install docker-registry
$ docker pull
$ docker push
$ docker commit
39. Maciej Lasyk, Docker containers at scale 18/64
base image
-> child image
-> grandchild image
Docker – images hierarchy
40. Maciej Lasyk, Docker containers at scale
base image
-> child image
-> grandchild image
Docker – images hierarchy
Git’s promise: Tiny footprint with
lightning fast performance
18/64
41. Maciej Lasyk, Docker containers at scale 19/64
Docker – images hierarchy
http://blog.octo.com/en/docker-registry-first-steps/
42. Maciej Lasyk, Docker containers at scale 20/64
FROM ubuntu:14.04 MAINTAINER james@example.com
ENV REFRESHED_AT 2014-06-01
RUN apt-get update -qq && apt-get install -qqy curl
[...]
Docker – images hierarchy
43. Maciej Lasyk, Docker containers at scale 20/64
- Isolation via kernel namespaces
- Additional layer of security: SELinux / AppArmor / GRSEC
- Each container gets own network stack
- control groups for resources limiting
Docker – security
f20 policy: https://git.fedorahosted.org/cgit/selinux-policy.git/tree/docker.te?h=f20-contrib
What's there?
seinfo -t -x | grep docker
sesearch -A -s docker_t (and the rest)
or just unpack docker.pp with semodule_unpackage
45. Maciej Lasyk, Docker containers at scale 21/64
Docker – use cases
CI Stack
http://sattia.blogspot.com/2014/05/docker-lightweight-linux-containers-for.html
46. Maciej Lasyk, Docker containers at scale 22/64
Continuous Integration
- local dev
- with Docker it's easy to standardize envs
- deployment
- rolling updates (e.g. w/Ansible)
- testing
- unit testing of any commit on dedicated env
- don't worry about cleaning up after testing
- parrarelized tests across any machines
Docker – use cases
47. Maciej Lasyk, Docker containers at scale 23/64
- version control system for apps
- microservices
- Docker embraces granularity
- Services can be deployed independently and faster
- paralleled tests across any machines
- continuous delivery
- PaaS
Docker – use cases
48. Maciej Lasyk, Docker containers at scale 24/64
- 2013-01: dotCloud worked on own PaaS (Python based)
- 2013-03: Docker went public (AUFS, LXC)
- middle 2013: Red Hat joined, devmapper, SELinux
- late 2013: removed LXC, rewritten in Go
- 2014-02: stable 1.0
Docker – history
57. Maciej Lasyk, Docker containers at scale 33/64
- you think PaaS will solve your problems?
To Paas or not to PaaS?
58. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
To Paas or not to PaaS?
33/64
59. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
- running PaaS might be easy
To Paas or not to PaaS?
33/64
60. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
- running PaaS might be easy
- operating PaaS will be tough
To Paas or not to PaaS?
33/64
61. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
- running PaaS might be easy
- operating PaaS will be tough
- so is operating your apps tough enough to move?
To Paas or not to PaaS?
33/64
62. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
- running PaaS might be easy
- operating PaaS will be tough
- so is operating your apps tough enough to move?
- private PaaS or not?
To Paas or not to PaaS?
33/64
63. Maciej Lasyk, Docker containers at scale
- you think PaaS will solve your problems?
- it will rather clone them :)
- running PaaS might be easy
- operating PaaS will be tough
- so is operating your apps tough enough to move?
- private PaaS or not?
- Rainbow and Unicorn Piss:
http://blog.lusis.org/blog/2014/06/14/paas-for-realists/
To Paas or not to PaaS?
33/64
64. Maciej Lasyk, Docker containers at scale
- flynn.io
- Open source PaaS (Go)
- Uses Docker to manage containers
- Ops should be a product team, not consultants
- under development
- Git push deployment
- https://flynn.io
To Paas or not to PaaS?
34/64
65. Maciej Lasyk, Docker containers at scale
- flynn.io
- Open source PaaS (Go)
- Uses Docker to manage containers
- Ops should be a product team, not consultants
- under development
- Git push deployment
- https://flynn.io
- dokku
- The smallest PaaS implementation you've ever seen
- Docker powered mini-Heroku
- Less than 100 lines of Bash
- Git push deployment
- https://github.com/progrium/dokku
To Paas or not to PaaS?
34/64
66. Maciej Lasyk, Docker containers at scale
- flynn.io
- Open source PaaS (Go)
- Uses Docker to manage containers
- Ops should be a product team, not consultants
- under development
- Git push deployment
- https://flynn.io
- dokku
- The smallest PaaS implementation you've ever seen
- Docker powered mini-Heroku
- Less than 100 lines of Bash
- Git push deployment
- https://github.com/progrium/dokku
- deis.io
- Open source PaaS (Python)
- Git push deployment
- On top of CoreOS w/ Docker
- http://deis.io/
To Paas or not to PaaS?
34/64
67. Maciej Lasyk, Docker containers at scale
- flynn.io
- Open source PaaS (Go)
- Uses Docker to manage containers
- Ops should be a product team, not consultants
- under development
- Git push deployment
- https://flynn.io
- dokku
- The smallest PaaS implementation you've ever seen
- Docker powered mini-Heroku
- Less than 100 lines of Bash
- Git push deployment
- https://github.com/progrium/dokku
- deis.io
- Open source PaaS (Python)
- Git push deployment
- On top of CoreOS w/ Docker
- http://deis.io/
To Paas or not to PaaS?
34/64
Don't forget maestro-ng!
https://github.com/signalfuse/maestro-ng
68. Maciej Lasyk, Docker containers at scale 35/64
Remember, that PaaS might fail; plan & test for disaster !
To Paas or not to PaaS?
70. Maciej Lasyk, Docker containers at scale 37/64
Or via Dockerfile:
$ docker build -t fedora –rm .
$ docker run --name=nginx fedora
Docker & CLI
71. Maciej Lasyk, Docker containers at scale 38/64
- http://www.fig.sh
- for single host env
FIG
72. Maciej Lasyk, Docker containers at scale 39/64
- http://www.fig.sh
- for single host env
FIG
FROM python:2.7
ENV PYTHONUNBUFFERED 1
RUN mkdir /code
WORKDIR /code
ADD requirements.txt /code/
RUN pip install -r requirements.txt
ADD . /code/
73. Maciej Lasyk, Docker containers at scale 40/64
FIG
db:
image: postgres
web:
build: .
command: python manage.py runserver 0.0.0.0:8000
volumes:
- /srv/app/code:/code
ports:
- "8000:8000"
links:
- db
74. Maciej Lasyk, Docker containers at scale 41/64
FIG
$ fig run web django-admin.py startproject figexample .
$ fig up
Management during runtime?
$ fig run web python manage.py syncdb
75. Maciej Lasyk, Docker containers at scale 42/64
Ansible + Docker
&
Docker + Ansible
Docker & Ansible
76. Maciej Lasyk, Docker containers at scale 43/64
Ansible docker core module:
http://docs.ansible.com/docker_module.html
Docker & Ansible
- hosts: web
sudo: yes
tasks:
- name: run tomcat servers
docker: >
image=centos
command="service tomcat6 start"
ports=8080
count=5
memory_limit=128MB
link=mysql
expose=8080
registry=...
volume=...
77. Maciej Lasyk, Docker containers at scale 44/64
Building image with Ansible:
Docker & Ansible
FROM ansible/centos7-ansible:stable
ADD ansible /srv/example/
WORKDIR /srv/example
RUN ansible-playbook web.yml -c local
EXPOSE 80
ENTRYPOINT ["/usr/sbin/nginx", "-DFOREGROUND"]
78. Maciej Lasyk, Docker containers at scale
Building image with Ansible:
Docker & Ansible
FROM ansible/centos7-ansible:stable
ADD ansible /srv/example/
WORKDIR /srv/example
RUN ansible-playbook web.yml -c local
EXPOSE 80
ENTRYPOINT ["/usr/sbin/nginx", "-DFOREGROUND"]
ansible/web.yml:
- hosts: localhost
tasks:
- yum: pkg=nginx state=latest
- copy:
src: web.conf
dest: /etc/nginx/conf.d/web.conf
group: "nginx"
mode: "0644"
44/64
79. Maciej Lasyk, Docker containers at scale 45/64
- Designed for massive server deployments
- Support Docker container out of the box
- It's a Chrome OS fork
- Consists of couple of components:
- SystemD – not just a init system ;)
- Fleet – cluster level manager & scheduler
- etcd – light & distributed key / value store
- Docker – the only packaging method in CoreOS
CoreOS
87. Maciej Lasyk, Docker containers at scale 55/64
- automated service discovery and registration framework
- ideal for SOA architectures
- ideal for continuous integration & delivery
- solves “works on my machine” problem
SmartStack
88. Maciej Lasyk, Docker containers at scale 56/64
- automated service discovery and registration framework
- ideal for SOA architectures
- ideal for continuous integration & delivery
- solves “works on my machine” problem
SmartStack
haproxy + nerve + synapse + zookeper = smartstack
89. Maciej Lasyk, Docker containers at scale 57/64
Synapse
- discovery service (via zookeeper or etcd)
- installed on every node
- writes haproxy configuration
- application doesn't have to be aware of this
- works same on bare / VM / docker
- https://github.com/airbnb/nerve
SmartStack
91. Maciej Lasyk, Docker containers at scale 59/64
Nerve
- health checks (pluggable)
- register service info to zookeper (or etcd)
- https://github.com/airbnb/synapse
SmartStack
94. Maciej Lasyk, Docker containers at scale 60/64
SmartStack
Smartstack + Docker = <3
95. Maciej Lasyk, Docker containers at scale 61/64
Summary
Wanna learn Docker?
http://dockerbook.com/
96. Maciej Lasyk, Docker containers at scale
w/ Docker Sky is the limit!
Summary
61/64
97. Freenode #docker
Krk DevOPS meetups (http://www.meetup.com/Docker-Krakow-Poland/)
https://github.com/docker/docker
Maciej Lasyk, Docker containers at scale 62/64
98. Maciej Lasyk, Docker containers at scale 61/64
Looking for a job?
- software developer
- sysadmin
- devops
Catch me: maciek@lasyk.info
99. Maciej Lasyk, Docker containers at scale 61/64
Atmosphere Conference 2015
atmo-2015-dockerkrk
Atmosphere-conference.com
100. sources?
- docker.io documentation
- dockerbook.com
- slideshare!
- zounds of blogposts (urls provided)
- and some experience ;)
Maciej Lasyk, Docker containers at scale 63/64
101. Maciej Lasyk
#DockerKRK meetup 1
2015-01-27, Kraków
http://maciej.lasyk.info
maciej@lasyk.info
@docent-net
Orchestrating Docker containers at scale
Thank you :)
Maciej Lasyk, Docker containers at scale 64/64
Editor's Notes
- knows vagrant?
- knows differences between hyplev2 hyplev1 and containers?
- czy quick sort jest szybszy od heap sorta (kopcowanie)?
Bare: na pczątku był serwer, potem OS a potem wirtualna maszyna javy żeby to wszystko działało tak samo ;)