際際滷shows by User: jpetazzo / http://www.slideshare.net/images/logo.gif 際際滷shows by User: jpetazzo / Tue, 13 Jun 2017 12:50:35 GMT 際際滷Share feed for 際際滷shows by User: jpetazzo Use the Source or Join the Dark Side: differences between Docker Community and Enterprise Editions (devopscon berlin) /slideshow/use-the-source-or-join-the-dark-side-differences-between-docker-community-and-enterprise-editions-devopscon-berlin/76900911 devopscon-petazzoni-170613125035
The Docker Project delivers a complete open source platform to build, ship, and run any application, anywhere, using containers. The Docker Engine and the other main components (Compose, Machine, and the SwarmKit orchestration system) are free; but Docker Inc. (the company who started the Docker Project) also has a complete commercial offering named Docker EE (for Enterprise Edition) that adds an extra set of features geared at larger organizations, as well as an extended support and release cycle. In this talk, I will explain (and show with demos) what you can do using exclusively Docker CE (community, free edition) and which features are added by Docker EE. This talk is for you if you are in the process of selecting a container platform; or if youre just curious, and want to know exactly what you can do (and cannot do) with Docker CE and EE. ]]>
The Docker Project delivers a complete open source platform to build, ship, and run any application, anywhere, using containers. The Docker Engine and the other main components (Compose, Machine, and the SwarmKit orchestration system) are free; but Docker Inc. (the company who started the Docker Project) also has a complete commercial offering named Docker EE (for Enterprise Edition) that adds an extra set of features geared at larger organizations, as well as an extended support and release cycle. In this talk, I will explain (and show with demos) what you can do using exclusively Docker CE (community, free edition) and which features are added by Docker EE. This talk is for you if you are in the process of selecting a container platform; or if youre just curious, and want to know exactly what you can do (and cannot do) with Docker CE and EE. ]]> Tue, 13 Jun 2017 12:50:35 GMT /slideshow/use-the-source-or-join-the-dark-side-differences-between-docker-community-and-enterprise-editions-devopscon-berlin/76900911 jpetazzo@slideshare.net(jpetazzo) Use the Source or Join the Dark Side: differences between Docker Community and Enterprise Editions (devopscon berlin) jpetazzo The Docker Project delivers a complete open source platform to build, ship, and run any application, anywhere, using containers. The Docker Engine and the other main components (Compose, Machine, and the SwarmKit orchestration system) are free; but Docker Inc. (the company who started the Docker Project) also has a complete commercial offering named Docker EE (for Enterprise Edition) that adds an extra set of features geared at larger organizations, as well as an extended support and release cycle. In this talk, I will explain (and show with demos) what you can do using exclusively Docker CE (community, free edition) and which features are added by Docker EE. This talk is for you if you are in the process of selecting a container platform; or if youre just curious, and want to know exactly what you can do (and cannot do) with Docker CE and EE. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopscon-petazzoni-170613125035-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> The Docker Project delivers a complete open source platform to build, ship, and run any application, anywhere, using containers. The Docker Engine and the other main components (Compose, Machine, and the SwarmKit orchestration system) are free; but Docker Inc. (the company who started the Docker Project) also has a complete commercial offering named Docker EE (for Enterprise Edition) that adds an extra set of features geared at larger organizations, as well as an extended support and release cycle. In this talk, I will explain (and show with demos) what you can do using exclusively Docker CE (community, free edition) and which features are added by Docker EE. This talk is for you if you are in the process of selecting a container platform; or if youre just curious, and want to know exactly what you can do (and cannot do) with Docker CE and EE.
Use the Source or Join the Dark Side: differences between Docker Community and Enterprise Editions (devopscon berlin) from J莨rme Petazzoni
]]> 3117 5 https://cdn.slidesharecdn.com/ss_thumbnails/devopscon-petazzoni-170613125035-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Orchestration for the rest of us /slideshow/orchestration-for-the-rest-of-us/70760352 orchestrationfortherestofus-170106234729
Orchestration, resource schedulingWhat does that mean? Is this only relevant for data centers with thousands of nodes? Should I care about Mesos, Kubernetes, Swarm, when all I have is a handful of virtual machines? The motto of public cloud IAAS is "pay for what you use," so in theory, if I deploy my apps there, I'm already getting the best "resource utilization" aka "bang for my buck," right? In this talk, we will answer those questions, and a few more. We will define orchestration, scheduling, and others, and show what it's like to use a scheduler to run containerized applications there. ]]>
Orchestration, resource schedulingWhat does that mean? Is this only relevant for data centers with thousands of nodes? Should I care about Mesos, Kubernetes, Swarm, when all I have is a handful of virtual machines? The motto of public cloud IAAS is "pay for what you use," so in theory, if I deploy my apps there, I'm already getting the best "resource utilization" aka "bang for my buck," right? In this talk, we will answer those questions, and a few more. We will define orchestration, scheduling, and others, and show what it's like to use a scheduler to run containerized applications there. ]]> Fri, 06 Jan 2017 23:47:29 GMT /slideshow/orchestration-for-the-rest-of-us/70760352 jpetazzo@slideshare.net(jpetazzo) Orchestration for the rest of us jpetazzo Orchestration, resource schedulingWhat does that mean? Is this only relevant for data centers with thousands of nodes? Should I care about Mesos, Kubernetes, Swarm, when all I have is a handful of virtual machines? The motto of public cloud IAAS is "pay for what you use," so in theory, if I deploy my apps there, I'm already getting the best "resource utilization" aka "bang for my buck," right? In this talk, we will answer those questions, and a few more. We will define orchestration, scheduling, and others, and show what it's like to use a scheduler to run containerized applications there. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/orchestrationfortherestofus-170106234729-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Orchestration, resource schedulingWhat does that mean? Is this only relevant for data centers with thousands of nodes? Should I care about Mesos, Kubernetes, Swarm, when all I have is a handful of virtual machines? The motto of public cloud IAAS is &quot;pay for what you use,&quot; so in theory, if I deploy my apps there, I&#39;m already getting the best &quot;resource utilization&quot; aka &quot;bang for my buck,&quot; right? In this talk, we will answer those questions, and a few more. We will define orchestration, scheduling, and others, and show what it&#39;s like to use a scheduler to run containerized applications there.
Orchestration for the rest of us from J莨rme Petazzoni
]]> 1947 3 https://cdn.slidesharecdn.com/ss_thumbnails/orchestrationfortherestofus-170106234729-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Cgroups, namespaces, and beyond: what are containers made from? (DockerCon Europe 2015) /slideshow/cgroups-namespaces-and-beyond-what-are-containers-made-from-dockercon-europe-2015/56860600 2015-11-16-dockercon-container-internals-160109181844
Linux containers are different from Solaris Zones or BSD Jails: they use discrete kernel features like cgroups, namespaces, SELinux, and more. We will describe those mechanisms in depth, as well as demo how to put them together to produce a container. We will also highlight how different container runtimes compare to each other. This talk was delivered at DockerCon Europe 2015 in Barcelona.]]>
Linux containers are different from Solaris Zones or BSD Jails: they use discrete kernel features like cgroups, namespaces, SELinux, and more. We will describe those mechanisms in depth, as well as demo how to put them together to produce a container. We will also highlight how different container runtimes compare to each other. This talk was delivered at DockerCon Europe 2015 in Barcelona.]]> Sat, 09 Jan 2016 18:18:43 GMT /slideshow/cgroups-namespaces-and-beyond-what-are-containers-made-from-dockercon-europe-2015/56860600 jpetazzo@slideshare.net(jpetazzo) Cgroups, namespaces, and beyond: what are containers made from? (DockerCon Europe 2015) jpetazzo Linux containers are different from Solaris Zones or BSD Jails: they use discrete kernel features like cgroups, namespaces, SELinux, and more. We will describe those mechanisms in depth, as well as demo how to put them together to produce a container. We will also highlight how different container runtimes compare to each other. This talk was delivered at DockerCon Europe 2015 in Barcelona. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-11-16-dockercon-container-internals-160109181844-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Linux containers are different from Solaris Zones or BSD Jails: they use discrete kernel features like cgroups, namespaces, SELinux, and more. We will describe those mechanisms in depth, as well as demo how to put them together to produce a container. We will also highlight how different container runtimes compare to each other. This talk was delivered at DockerCon Europe 2015 in Barcelona.
Cgroups, namespaces, and beyond: what are containers made from? (DockerCon Europe 2015) from J莨rme Petazzoni
]]> 20509 7 https://cdn.slidesharecdn.com/ss_thumbnails/2015-11-16-dockercon-container-internals-160109181844-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Docker : quels enjeux pour le stockage et reseau ? Paris Open Source Summit 2015 https://fr.slideshare.net/slideshow/docker-quels-enjeux-pour-le-stockage-et-reseau-paris-open-source-summit-2015/55263425 possdocker-quelsenjeuxpourlestockageetreseau-151118181149-lva1-app6891
Pr辿sentation donn辿e le 18 novembre 2015 au Paris Open Source Summit par Herv辿 Leclerc (Alterway) et J辿r担me Petazzoni (Docker), pr辿sentant entre autres les nouvelles fonctionalit辿s de Docker pour le stockage et le r辿seau arriv辿es dans la version 1.9 du Docker Engine.]]>
Pr辿sentation donn辿e le 18 novembre 2015 au Paris Open Source Summit par Herv辿 Leclerc (Alterway) et J辿r担me Petazzoni (Docker), pr辿sentant entre autres les nouvelles fonctionalit辿s de Docker pour le stockage et le r辿seau arriv辿es dans la version 1.9 du Docker Engine.]]> Wed, 18 Nov 2015 18:11:49 GMT https://fr.slideshare.net/slideshow/docker-quels-enjeux-pour-le-stockage-et-reseau-paris-open-source-summit-2015/55263425 jpetazzo@slideshare.net(jpetazzo) Docker : quels enjeux pour le stockage et reseau ? Paris Open Source Summit 2015 jpetazzo Pr辿sentation donn辿e le 18 novembre 2015 au Paris Open Source Summit par Herv辿 Leclerc (Alterway) et J辿r担me Petazzoni (Docker), pr辿sentant entre autres les nouvelles fonctionalit辿s de Docker pour le stockage et le r辿seau arriv辿es dans la version 1.9 du Docker Engine. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/possdocker-quelsenjeuxpourlestockageetreseau-151118181149-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Pr辿sentation donn辿e le 18 novembre 2015 au Paris Open Source Summit par Herv辿 Leclerc (Alterway) et J辿r担me Petazzoni (Docker), pr辿sentant entre autres les nouvelles fonctionalit辿s de Docker pour le stockage et le r辿seau arriv辿es dans la version 1.9 du Docker Engine.
from Jrme Petazzoni
]]> 5230 8 https://cdn.slidesharecdn.com/ss_thumbnails/possdocker-quelsenjeuxpourlestockageetreseau-151118181149-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Making DevOps Secure with Docker on Solaris (Oracle Open World, with Jesse Butler) /jpetazzo/making-devops-secure-with-docker-on-solaris-oracle-open-world-with-jesse-butler con8724-making-devops-secure-with-docker-v7-151030232846-lva1-app6892
Docker, the container Engine and Platform, is coming to Oracle Solaris! This is the talk that J辿r担me Petazzoni (Docker) and Jesse Butler (Oracle) gave at Oracle Open World in November 2015.]]>
Docker, the container Engine and Platform, is coming to Oracle Solaris! This is the talk that J辿r担me Petazzoni (Docker) and Jesse Butler (Oracle) gave at Oracle Open World in November 2015.]]> Fri, 30 Oct 2015 23:28:45 GMT /jpetazzo/making-devops-secure-with-docker-on-solaris-oracle-open-world-with-jesse-butler jpetazzo@slideshare.net(jpetazzo) Making DevOps Secure with Docker on Solaris (Oracle Open World, with Jesse Butler) jpetazzo Docker, the container Engine and Platform, is coming to Oracle Solaris! This is the talk that J辿r担me Petazzoni (Docker) and Jesse Butler (Oracle) gave at Oracle Open World in November 2015. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/con8724-making-devops-secure-with-docker-v7-151030232846-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Docker, the container Engine and Platform, is coming to Oracle Solaris! This is the talk that J辿r担me Petazzoni (Docker) and Jesse Butler (Oracle) gave at Oracle Open World in November 2015.
Making DevOps Secure with Docker on Solaris (Oracle Open World, with Jesse Butler) from J莨rme Petazzoni
]]> 10909 17 https://cdn.slidesharecdn.com/ss_thumbnails/con8724-making-devops-secure-with-docker-v7-151030232846-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Containers, docker, and security: state of the union (Bay Area Infracoders Meetup) /slideshow/containers-docker-and-security-state-of-the-union-bay-area-infracoders-meetup/54290204 containersdockerandsecuritystateoftheunion-151023045641-lva1-app6891
Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. ]]>
Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. ]]> Fri, 23 Oct 2015 04:56:41 GMT /slideshow/containers-docker-and-security-state-of-the-union-bay-area-infracoders-meetup/54290204 jpetazzo@slideshare.net(jpetazzo) Containers, docker, and security: state of the union (Bay Area Infracoders Meetup) jpetazzo Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/containersdockerandsecuritystateoftheunion-151023045641-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was &quot;can I safely colocate containers on the same machine?&quot; and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: &quot;containers do not contain!&quot;, and at last year&#39;s LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular.
Containers, docker, and security: state of the union (Bay Area Infracoders Meetup) from J莨rme Petazzoni
]]> 6961 6 https://cdn.slidesharecdn.com/ss_thumbnails/containersdockerandsecuritystateoftheunion-151023045641-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 From development environments to production deployments with Docker, Compose, Machine, Swarm, and ECS CLI (AWS re:invent 2015) /slideshow/from-development-environments-to-production-deployments-with-docker-compose-machine-swarm-and-ecs-cli-aws-reinvent-2015/53716262 0-slides-151008225854-lva1-app6891
In this session, we will learn how to define and run multi-container applications with Docker Compose. Then, we will show how to deploy and scale them seamlessly to a cluster with Docker Swarm; and how Amazon EC2 Container Service (ECS) eliminates the need to install,operate, and scale your own cluster management infrastructure. We will also walk through some best practice patterns used by customers for running their microservices platforms or batch jobs. Sample code and Compose templates will be provided on GitHub afterwards. ]]>
In this session, we will learn how to define and run multi-container applications with Docker Compose. Then, we will show how to deploy and scale them seamlessly to a cluster with Docker Swarm; and how Amazon EC2 Container Service (ECS) eliminates the need to install,operate, and scale your own cluster management infrastructure. We will also walk through some best practice patterns used by customers for running their microservices platforms or batch jobs. Sample code and Compose templates will be provided on GitHub afterwards. ]]> Thu, 08 Oct 2015 22:58:54 GMT /slideshow/from-development-environments-to-production-deployments-with-docker-compose-machine-swarm-and-ecs-cli-aws-reinvent-2015/53716262 jpetazzo@slideshare.net(jpetazzo) From development environments to production deployments with Docker, Compose, Machine, Swarm, and ECS CLI (AWS re:invent 2015) jpetazzo In this session, we will learn how to define and run multi-container applications with Docker Compose. Then, we will show how to deploy and scale them seamlessly to a cluster with Docker Swarm; and how Amazon EC2 Container Service (ECS) eliminates the need to install,operate, and scale your own cluster management infrastructure. We will also walk through some best practice patterns used by customers for running their microservices platforms or batch jobs. Sample code and Compose templates will be provided on GitHub afterwards. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/0-slides-151008225854-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> In this session, we will learn how to define and run multi-container applications with Docker Compose. Then, we will show how to deploy and scale them seamlessly to a cluster with Docker Swarm; and how Amazon EC2 Container Service (ECS) eliminates the need to install,operate, and scale your own cluster management infrastructure. We will also walk through some best practice patterns used by customers for running their microservices platforms or batch jobs. Sample code and Compose templates will be provided on GitHub afterwards.
From development environments to production deployments with Docker, Compose, Machine, Swarm, and ECS CLI (AWS re:invent 2015) from J莨rme Petazzoni
]]> 33091 21 https://cdn.slidesharecdn.com/ss_thumbnails/0-slides-151008225854-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 How to contribute to large open source projects like Docker (LinuxCon 2015) /jpetazzo/how-to-contribute-to-large-open-source-projects-like-docker-linuxcon-2015 contributingtolargeopensourceprojects-150908165829-lva1-app6891
Contributing to a large open source project can seem daunting at first; but fear not! You too can join thousands of successful contributors. First, you don't have to be an expert in Golang, Python, or C, to contribute to Docker, OpenStack, or the Linux Kernel. Many projects also need help with documentation, translation, testing, triaging issues, and more. Very often, just going through bug reports to reproduce them and confirm "this also happens on my setup, with version XYZ" is extremely helpful. If you decide to take the leap and propose a change (be it code or documentation), each open source project has different contribution guidelines and workflows. In this talk, Arnaud and J辿r担me will explain some of those workflows, how maintainers review your patches, and highlight the details that make your changes more likely to be merged into the project. ]]>
Contributing to a large open source project can seem daunting at first; but fear not! You too can join thousands of successful contributors. First, you don't have to be an expert in Golang, Python, or C, to contribute to Docker, OpenStack, or the Linux Kernel. Many projects also need help with documentation, translation, testing, triaging issues, and more. Very often, just going through bug reports to reproduce them and confirm "this also happens on my setup, with version XYZ" is extremely helpful. If you decide to take the leap and propose a change (be it code or documentation), each open source project has different contribution guidelines and workflows. In this talk, Arnaud and J辿r担me will explain some of those workflows, how maintainers review your patches, and highlight the details that make your changes more likely to be merged into the project. ]]> Tue, 08 Sep 2015 16:58:29 GMT /jpetazzo/how-to-contribute-to-large-open-source-projects-like-docker-linuxcon-2015 jpetazzo@slideshare.net(jpetazzo) How to contribute to large open source projects like Docker (LinuxCon 2015) jpetazzo Contributing to a large open source project can seem daunting at first; but fear not! You too can join thousands of successful contributors. First, you don't have to be an expert in Golang, Python, or C, to contribute to Docker, OpenStack, or the Linux Kernel. Many projects also need help with documentation, translation, testing, triaging issues, and more. Very often, just going through bug reports to reproduce them and confirm "this also happens on my setup, with version XYZ" is extremely helpful. If you decide to take the leap and propose a change (be it code or documentation), each open source project has different contribution guidelines and workflows. In this talk, Arnaud and J辿r担me will explain some of those workflows, how maintainers review your patches, and highlight the details that make your changes more likely to be merged into the project. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/contributingtolargeopensourceprojects-150908165829-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Contributing to a large open source project can seem daunting at first; but fear not! You too can join thousands of successful contributors. First, you don&#39;t have to be an expert in Golang, Python, or C, to contribute to Docker, OpenStack, or the Linux Kernel. Many projects also need help with documentation, translation, testing, triaging issues, and more. Very often, just going through bug reports to reproduce them and confirm &quot;this also happens on my setup, with version XYZ&quot; is extremely helpful. If you decide to take the leap and propose a change (be it code or documentation), each open source project has different contribution guidelines and workflows. In this talk, Arnaud and J辿r担me will explain some of those workflows, how maintainers review your patches, and highlight the details that make your changes more likely to be merged into the project.
How to contribute to large open source projects like Docker (LinuxCon 2015) from J莨rme Petazzoni
]]> 8892 21 https://cdn.slidesharecdn.com/ss_thumbnails/contributingtolargeopensourceprojects-150908165829-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Containers, Docker, and Security: State Of The Union (LinuxCon and ContainerCon 2015) /slideshow/containers-docker-and-security-state-of-the-union-linuxcon-and-containercon-2015/52010205 containersdockerandsecuritystateoftheunion-150824160132-lva1-app6892
Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. ]]>
Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. ]]> Mon, 24 Aug 2015 16:01:32 GMT /slideshow/containers-docker-and-security-state-of-the-union-linuxcon-and-containercon-2015/52010205 jpetazzo@slideshare.net(jpetazzo) Containers, Docker, and Security: State Of The Union (LinuxCon and ContainerCon 2015) jpetazzo Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was "can I safely colocate containers on the same machine?" and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: "containers do not contain!", and at last year's LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/containersdockerandsecuritystateoftheunion-150824160132-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Docker is two years old. While security has always been at the core of the questions revolving around Docker, the nature of those questions has changed. Last year, the main concern was &quot;can I safely colocate containers on the same machine?&quot; and it elicited various responses. Dan Walsh, SELinux expert, notoriously said: &quot;containers do not contain!&quot;, and at last year&#39;s LinuxCon, J辿r担me delivered a presentation detailing how to harden Docker and containers to isolate them better. Today, people have new concerns. They include image transport, vulnerability mitigation, and more. After a recap about the current state of container security, J辿r担me will explain why those new questions showed up, and most importantly, how to address them and safely deploy containers in general, and Docker in particular.
Containers, Docker, and Security: State Of The Union (LinuxCon and ContainerCon 2015) from J莨rme Petazzoni
]]> 7446 14 https://cdn.slidesharecdn.com/ss_thumbnails/containersdockerandsecuritystateoftheunion-150824160132-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Anatomy of a Container: Namespaces, cgroups & Some Filesystem Magic - LinuxCon /slideshow/anatomy-of-a-container-namespaces-cgroups-some-filesystem-magic-linuxcon/51837004 anatomyofacontainer-150819222754-lva1-app6891
Containers are everywhere. But what exactly is a container? What are they made from? What's the difference between LXC, butts-nspawn, Docker, and the other container systems out there? And why should we bother about specific filesystems? In this talk, J辿r担me will show the individual roles and behaviors of the components making up a container: namespaces, control groups, and copy-on-write systems. Then, he will use them to assemble a container from scratch, and highlight the differences (and likelinesses) with existing container systems. ]]>
Containers are everywhere. But what exactly is a container? What are they made from? What's the difference between LXC, butts-nspawn, Docker, and the other container systems out there? And why should we bother about specific filesystems? In this talk, J辿r担me will show the individual roles and behaviors of the components making up a container: namespaces, control groups, and copy-on-write systems. Then, he will use them to assemble a container from scratch, and highlight the differences (and likelinesses) with existing container systems. ]]> Wed, 19 Aug 2015 22:27:54 GMT /slideshow/anatomy-of-a-container-namespaces-cgroups-some-filesystem-magic-linuxcon/51837004 jpetazzo@slideshare.net(jpetazzo) Anatomy of a Container: Namespaces, cgroups & Some Filesystem Magic - LinuxCon jpetazzo Containers are everywhere. But what exactly is a container? What are they made from? What's the difference between LXC, butts-nspawn, Docker, and the other container systems out there? And why should we bother about specific filesystems? In this talk, J辿r担me will show the individual roles and behaviors of the components making up a container: namespaces, control groups, and copy-on-write systems. Then, he will use them to assemble a container from scratch, and highlight the differences (and likelinesses) with existing container systems. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/anatomyofacontainer-150819222754-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Containers are everywhere. But what exactly is a container? What are they made from? What&#39;s the difference between LXC, butts-nspawn, Docker, and the other container systems out there? And why should we bother about specific filesystems? In this talk, J辿r担me will show the individual roles and behaviors of the components making up a container: namespaces, control groups, and copy-on-write systems. Then, he will use them to assemble a container from scratch, and highlight the differences (and likelinesses) with existing container systems.
Anatomy of a Container: Namespaces, cgroups & Some Filesystem Magic - LinuxCon from J莨rme Petazzoni
]]> 98840 35 https://cdn.slidesharecdn.com/ss_thumbnails/anatomyofacontainer-150819222754-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Microservices. Microservices everywhere! (At OSCON 2015) /slideshow/microservices-microservices-everywhere-at-oscon-2015/50821414 2015-07-22-microservices-oscon-150722211711-lva1-app6891
]]>
]]> Wed, 22 Jul 2015 21:17:11 GMT /slideshow/microservices-microservices-everywhere-at-oscon-2015/50821414 jpetazzo@slideshare.net(jpetazzo) Microservices. Microservices everywhere! (At OSCON 2015) jpetazzo <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-07-22-microservices-oscon-150722211711-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Microservices. Microservices everywhere! (At OSCON 2015) from J莨rme Petazzoni
]]> 8130 5 https://cdn.slidesharecdn.com/ss_thumbnails/2015-07-22-microservices-oscon-150722211711-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Deploy microservices in containers with Docker and friends - KCDC2015 /slideshow/kcdc2015/49882528 deploymicroservicesincontainerswithdockerandfriends-150626160213-lva1-app6891
Docker lets us build, ship, and run any Linux application, on any platform. It found many early adopters in the CI/CD industry, long before it reached the symbolic 1.0 milestone and was considered "production-ready." Since then, its stability and features attracted enterprise users in many different fields, including very demanding ones like finance, banking, or intelligence agencies. We will see how Docker is particularly suited to the deployment of distributed applications, and why it is an ideal platform for microservice architectures. In particular, we will look into three Docker related projects that have been announced at DockerCon Europe last December: Machine, Swarm, and Compose, and we will explain how they improve the way we build, deploy, and scale distributed applications.]]>
Docker lets us build, ship, and run any Linux application, on any platform. It found many early adopters in the CI/CD industry, long before it reached the symbolic 1.0 milestone and was considered "production-ready." Since then, its stability and features attracted enterprise users in many different fields, including very demanding ones like finance, banking, or intelligence agencies. We will see how Docker is particularly suited to the deployment of distributed applications, and why it is an ideal platform for microservice architectures. In particular, we will look into three Docker related projects that have been announced at DockerCon Europe last December: Machine, Swarm, and Compose, and we will explain how they improve the way we build, deploy, and scale distributed applications.]]> Fri, 26 Jun 2015 16:02:13 GMT /slideshow/kcdc2015/49882528 jpetazzo@slideshare.net(jpetazzo) Deploy microservices in containers with Docker and friends - KCDC2015 jpetazzo Docker lets us build, ship, and run any Linux application, on any platform. It found many early adopters in the CI/CD industry, long before it reached the symbolic 1.0 milestone and was considered "production-ready." Since then, its stability and features attracted enterprise users in many different fields, including very demanding ones like finance, banking, or intelligence agencies. We will see how Docker is particularly suited to the deployment of distributed applications, and why it is an ideal platform for microservice architectures. In particular, we will look into three Docker related projects that have been announced at DockerCon Europe last December: Machine, Swarm, and Compose, and we will explain how they improve the way we build, deploy, and scale distributed applications. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/deploymicroservicesincontainerswithdockerandfriends-150626160213-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Docker lets us build, ship, and run any Linux application, on any platform. It found many early adopters in the CI/CD industry, long before it reached the symbolic 1.0 milestone and was considered &quot;production-ready.&quot; Since then, its stability and features attracted enterprise users in many different fields, including very demanding ones like finance, banking, or intelligence agencies. We will see how Docker is particularly suited to the deployment of distributed applications, and why it is an ideal platform for microservice architectures. In particular, we will look into three Docker related projects that have been announced at DockerCon Europe last December: Machine, Swarm, and Compose, and we will explain how they improve the way we build, deploy, and scale distributed applications.
Deploy microservices in containers with Docker and friends - KCDC2015 from J莨rme Petazzoni
]]> 8929 3 https://cdn.slidesharecdn.com/ss_thumbnails/deploymicroservicesincontainerswithdockerandfriends-150626160213-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Containers: from development to production at DevNation 2015 /slideshow/containers-from-development-to-production-at-devnation-2015/49878837 2015-06-22-devnation-sepopconcerns-150626141903-lva1-app6892
In Docker, applications are shipped using a lightweight format, managed with a high-level API, and run within software containers which abstract the host environment. Operating details like distributions, versions, and network setup no longer matter to the application developer. Thanks to this abstraction level, we can use the same container across all steps of the life cycle of an application, from development to production. This eliminates problems stemming from discrepancies between those environments. Even so, these environments will always have different requirements. If our quality assurance (QA) and production systems use different logging systems, how can we still ship the same container to both? How can we satisfy the backup and security requirements of our production stack without bloating our development stack? In this sess, you will learn about the unique features in containers that allow you to cleanly decouple system administrator tasks from the core of your application. Well show you how this decoupling results in smaller, simpler containers, and gives you more flexibility when building, managing, and evolving your application stacks.]]>
In Docker, applications are shipped using a lightweight format, managed with a high-level API, and run within software containers which abstract the host environment. Operating details like distributions, versions, and network setup no longer matter to the application developer. Thanks to this abstraction level, we can use the same container across all steps of the life cycle of an application, from development to production. This eliminates problems stemming from discrepancies between those environments. Even so, these environments will always have different requirements. If our quality assurance (QA) and production systems use different logging systems, how can we still ship the same container to both? How can we satisfy the backup and security requirements of our production stack without bloating our development stack? In this sess, you will learn about the unique features in containers that allow you to cleanly decouple system administrator tasks from the core of your application. Well show you how this decoupling results in smaller, simpler containers, and gives you more flexibility when building, managing, and evolving your application stacks.]]> Fri, 26 Jun 2015 14:19:03 GMT /slideshow/containers-from-development-to-production-at-devnation-2015/49878837 jpetazzo@slideshare.net(jpetazzo) Containers: from development to production at DevNation 2015 jpetazzo In Docker, applications are shipped using a lightweight format, managed with a high-level API, and run within software containers which abstract the host environment. Operating details like distributions, versions, and network setup no longer matter to the application developer. Thanks to this abstraction level, we can use the same container across all steps of the life cycle of an application, from development to production. This eliminates problems stemming from discrepancies between those environments. Even so, these environments will always have different requirements. If our quality assurance (QA) and production systems use different logging systems, how can we still ship the same container to both? How can we satisfy the backup and security requirements of our production stack without bloating our development stack? In this sess, you will learn about the unique features in containers that allow you to cleanly decouple system administrator tasks from the core of your application. Well show you how this decoupling results in smaller, simpler containers, and gives you more flexibility when building, managing, and evolving your application stacks. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-06-22-devnation-sepopconcerns-150626141903-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> In Docker, applications are shipped using a lightweight format, managed with a high-level API, and run within software containers which abstract the host environment. Operating details like distributions, versions, and network setup no longer matter to the application developer. Thanks to this abstraction level, we can use the same container across all steps of the life cycle of an application, from development to production. This eliminates problems stemming from discrepancies between those environments. Even so, these environments will always have different requirements. If our quality assurance (QA) and production systems use different logging systems, how can we still ship the same container to both? How can we satisfy the backup and security requirements of our production stack without bloating our development stack? In this sess, you will learn about the unique features in containers that allow you to cleanly decouple system administrator tasks from the core of your application. Well show you how this decoupling results in smaller, simpler containers, and gives you more flexibility when building, managing, and evolving your application stacks.
Containers: from development to production at DevNation 2015 from J莨rme Petazzoni
]]> 6430 2 https://cdn.slidesharecdn.com/ss_thumbnails/2015-06-22-devnation-sepopconcerns-150626141903-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Immutable infrastructure with Docker and containers (GlueCon 2015) /slideshow/immutable-infrastructure-with-docker-and-containers-gluecon-2015/48410280 2015-05-20-gluecon-immutable-150520235939-lva1-app6892
"Never upgrade a server again. Never update your code. Instead, create new servers, and throw away the old ones!" That's the idea of immutable servers, or immutable infrastructure. This makes many things easier: rollbacks (you can always bring back the old servers), A/B testing (put old and new servers side by side), security (use the latest and safest base system at each deploy), and more. However, throwing in a bunch of new servers at each one-line CSS change is going to be complicated, not to mention costly. Containers to the rescue! Creating container "golden images" is easy, fast, dare I say painless. Replacing your old containers with new ones is also easy to do; much easier than virtual machines, let alone physical ones. In this talk, we'll quickly recap the pros (and cons) of immutable servers; then explain how to implement that pattern with containers. We will use Docker as an example, but the technique can easily be adapted to Rocket or even plain LXC containers.]]>
"Never upgrade a server again. Never update your code. Instead, create new servers, and throw away the old ones!" That's the idea of immutable servers, or immutable infrastructure. This makes many things easier: rollbacks (you can always bring back the old servers), A/B testing (put old and new servers side by side), security (use the latest and safest base system at each deploy), and more. However, throwing in a bunch of new servers at each one-line CSS change is going to be complicated, not to mention costly. Containers to the rescue! Creating container "golden images" is easy, fast, dare I say painless. Replacing your old containers with new ones is also easy to do; much easier than virtual machines, let alone physical ones. In this talk, we'll quickly recap the pros (and cons) of immutable servers; then explain how to implement that pattern with containers. We will use Docker as an example, but the technique can easily be adapted to Rocket or even plain LXC containers.]]> Wed, 20 May 2015 23:59:39 GMT /slideshow/immutable-infrastructure-with-docker-and-containers-gluecon-2015/48410280 jpetazzo@slideshare.net(jpetazzo) Immutable infrastructure with Docker and containers (GlueCon 2015) jpetazzo "Never upgrade a server again. Never update your code. Instead, create new servers, and throw away the old ones!" That's the idea of immutable servers, or immutable infrastructure. This makes many things easier: rollbacks (you can always bring back the old servers), A/B testing (put old and new servers side by side), security (use the latest and safest base system at each deploy), and more. However, throwing in a bunch of new servers at each one-line CSS change is going to be complicated, not to mention costly. Containers to the rescue! Creating container "golden images" is easy, fast, dare I say painless. Replacing your old containers with new ones is also easy to do; much easier than virtual machines, let alone physical ones. In this talk, we'll quickly recap the pros (and cons) of immutable servers; then explain how to implement that pattern with containers. We will use Docker as an example, but the technique can easily be adapted to Rocket or even plain LXC containers. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-05-20-gluecon-immutable-150520235939-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> &quot;Never upgrade a server again. Never update your code. Instead, create new servers, and throw away the old ones!&quot; That&#39;s the idea of immutable servers, or immutable infrastructure. This makes many things easier: rollbacks (you can always bring back the old servers), A/B testing (put old and new servers side by side), security (use the latest and safest base system at each deploy), and more. However, throwing in a bunch of new servers at each one-line CSS change is going to be complicated, not to mention costly. Containers to the rescue! Creating container &quot;golden images&quot; is easy, fast, dare I say painless. Replacing your old containers with new ones is also easy to do; much easier than virtual machines, let alone physical ones. In this talk, we&#39;ll quickly recap the pros (and cons) of immutable servers; then explain how to implement that pattern with containers. We will use Docker as an example, but the technique can easily be adapted to Rocket or even plain LXC containers.
Immutable infrastructure with Docker and containers (GlueCon 2015) from J莨rme Petazzoni
]]> 20216 7 https://cdn.slidesharecdn.com/ss_thumbnails/2015-05-20-gluecon-immutable-150520235939-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 The Docker ecosystem and the future of application deployment /slideshow/the-docker-ecosystem-and-the-future-of-application-deployment/46863728 2015-03-25-qconsp-150410121137-conversion-gate01
Ten years ago, virtualization ignited a revolution which gave birth to the Cloud and the DevOps initiative. Today, with containers, we are at the dawn of a similar breakthrough. How can we capture the value of containers? How can we use their features to implement microservices and immutable infrastructures, while retaining as much as possible of our existing practices? The answer is in the rich ecosystem that developed around Docker, an open-source platform to build, ship, and run applications in containers. In this keynote well explore what the applications of tomorrow will look like, how theyll be deployed and distributed and how to leverage those tools today.]]>
Ten years ago, virtualization ignited a revolution which gave birth to the Cloud and the DevOps initiative. Today, with containers, we are at the dawn of a similar breakthrough. How can we capture the value of containers? How can we use their features to implement microservices and immutable infrastructures, while retaining as much as possible of our existing practices? The answer is in the rich ecosystem that developed around Docker, an open-source platform to build, ship, and run applications in containers. In this keynote well explore what the applications of tomorrow will look like, how theyll be deployed and distributed and how to leverage those tools today.]]> Fri, 10 Apr 2015 12:11:37 GMT /slideshow/the-docker-ecosystem-and-the-future-of-application-deployment/46863728 jpetazzo@slideshare.net(jpetazzo) The Docker ecosystem and the future of application deployment jpetazzo Ten years ago, virtualization ignited a revolution which gave birth to the Cloud and the DevOps initiative. Today, with containers, we are at the dawn of a similar breakthrough. How can we capture the value of containers? How can we use their features to implement microservices and immutable infrastructures, while retaining as much as possible of our existing practices? The answer is in the rich ecosystem that developed around Docker, an open-source platform to build, ship, and run applications in containers. In this keynote well explore what the applications of tomorrow will look like, how theyll be deployed and distributed and how to leverage those tools today. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-03-25-qconsp-150410121137-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Ten years ago, virtualization ignited a revolution which gave birth to the Cloud and the DevOps initiative. Today, with containers, we are at the dawn of a similar breakthrough. How can we capture the value of containers? How can we use their features to implement microservices and immutable infrastructures, while retaining as much as possible of our existing practices? The answer is in the rich ecosystem that developed around Docker, an open-source platform to build, ship, and run applications in containers. In this keynote well explore what the applications of tomorrow will look like, how theyll be deployed and distributed and how to leverage those tools today.
The Docker ecosystem and the future of application deployment from J莨rme Petazzoni
]]> 2947 3 https://cdn.slidesharecdn.com/ss_thumbnails/2015-03-25-qconsp-150410121137-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Docker: automation for the rest of us /slideshow/docker-automation-for-the-rest-of-us/46175931 2015-03-19-tiad-150323103812-conversion-gate01
Docker landed almost two years ago, making it possible to build, ship, and run any Linux application, on any platform, it was quickly adopted by developers and ops, like no other tool before. The CI/CD industry even took it to production long before it was stamped "production-ready." Why does everyone (or almost!) love Docker? Because it puts powerful automation abilities within the hands of normal developers. Automation almost always involves building distribution packages, virtual machine images, or writing configuration management manifests. With Docker, those tasks are radically transformed: sometimes they're far easier than before, other times they're no longer needed at all. Either way, the intervention of a seasoned sysadmin guru is no longer required.]]>
Docker landed almost two years ago, making it possible to build, ship, and run any Linux application, on any platform, it was quickly adopted by developers and ops, like no other tool before. The CI/CD industry even took it to production long before it was stamped "production-ready." Why does everyone (or almost!) love Docker? Because it puts powerful automation abilities within the hands of normal developers. Automation almost always involves building distribution packages, virtual machine images, or writing configuration management manifests. With Docker, those tasks are radically transformed: sometimes they're far easier than before, other times they're no longer needed at all. Either way, the intervention of a seasoned sysadmin guru is no longer required.]]> Mon, 23 Mar 2015 10:38:12 GMT /slideshow/docker-automation-for-the-rest-of-us/46175931 jpetazzo@slideshare.net(jpetazzo) Docker: automation for the rest of us jpetazzo Docker landed almost two years ago, making it possible to build, ship, and run any Linux application, on any platform, it was quickly adopted by developers and ops, like no other tool before. The CI/CD industry even took it to production long before it was stamped "production-ready." Why does everyone (or almost!) love Docker? Because it puts powerful automation abilities within the hands of normal developers. Automation almost always involves building distribution packages, virtual machine images, or writing configuration management manifests. With Docker, those tasks are radically transformed: sometimes they're far easier than before, other times they're no longer needed at all. Either way, the intervention of a seasoned sysadmin guru is no longer required. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-03-19-tiad-150323103812-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Docker landed almost two years ago, making it possible to build, ship, and run any Linux application, on any platform, it was quickly adopted by developers and ops, like no other tool before. The CI/CD industry even took it to production long before it was stamped &quot;production-ready.&quot; Why does everyone (or almost!) love Docker? Because it puts powerful automation abilities within the hands of normal developers. Automation almost always involves building distribution packages, virtual machine images, or writing configuration management manifests. With Docker, those tasks are radically transformed: sometimes they&#39;re far easier than before, other times they&#39;re no longer needed at all. Either way, the intervention of a seasoned sysadmin guru is no longer required.
Docker: automation for the rest of us from J莨rme Petazzoni
]]> 9942 3 https://cdn.slidesharecdn.com/ss_thumbnails/2015-03-19-tiad-150323103812-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Docker Non Technical Presentation /slideshow/docker-non-technical-presentation/44369230 2015-02-06-nontech-pres-150206173250-conversion-gate01
This is a non-technical, short presentation of Docker. For a longer, more technical intro, check the Docker 101.]]>
This is a non-technical, short presentation of Docker. For a longer, more technical intro, check the Docker 101.]]> Fri, 06 Feb 2015 17:32:50 GMT /slideshow/docker-non-technical-presentation/44369230 jpetazzo@slideshare.net(jpetazzo) Docker Non Technical Presentation jpetazzo This is a non-technical, short presentation of Docker. For a longer, more technical intro, check the Docker 101. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2015-02-06-nontech-pres-150206173250-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This is a non-technical, short presentation of Docker. For a longer, more technical intro, check the Docker 101.
Docker Non Technical Presentation from J莨rme Petazzoni
]]> 4164 2 https://cdn.slidesharecdn.com/ss_thumbnails/2015-02-06-nontech-pres-150206173250-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Introduction to Docker, December 2014 "Tour de France" Bordeaux Special Edition /slideshow/introduction-to-docker-december-2014-tour-de-france-bordeaux-special-edition/42874925 2014-12-19-bordeaux-141219103510-conversion-gate01
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, 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 :-)]]> Fri, 19 Dec 2014 10:35:10 GMT /slideshow/introduction-to-docker-december-2014-tour-de-france-bordeaux-special-edition/42874925 jpetazzo@slideshare.net(jpetazzo) Introduction to Docker, December 2014 "Tour de France" Bordeaux Special Edition jpetazzo 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 :-) <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2014-12-19-bordeaux-141219103510-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 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 &quot;Tour de France&quot; 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 :-)
Introduction to Docker, December 2014 "Tour de France" Bordeaux Special Edition from J莨rme Petazzoni
]]> 6490 4 https://cdn.slidesharecdn.com/ss_thumbnails/2014-12-19-bordeaux-141219103510-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Introduction to Docker, December 2014 "Tour de France" Edition /slideshow/introduction-to-docker-december-2014-tour-de-france-edition/42874778 2014-12-09-tourdefrance-141219102937-conversion-gate01
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 "Tour de France" in Paris, Lille, Lyon, Nice...]]>
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 "Tour de France" in Paris, Lille, Lyon, Nice...]]> Fri, 19 Dec 2014 10:29:37 GMT /slideshow/introduction-to-docker-december-2014-tour-de-france-edition/42874778 jpetazzo@slideshare.net(jpetazzo) Introduction to Docker, December 2014 "Tour de France" Edition jpetazzo 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 "Tour de France" in Paris, Lille, Lyon, Nice... <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2014-12-09-tourdefrance-141219102937-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 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 &quot;Tour de France&quot; in Paris, Lille, Lyon, Nice...
Introduction to Docker, December 2014 "Tour de France" Edition from J莨rme Petazzoni
]]> 3805 16 https://cdn.slidesharecdn.com/ss_thumbnails/2014-12-09-tourdefrance-141219102937-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Containers, Docker, and Microservices: the Terrific Trio /slideshow/containers-docker-and-microservices-the-terrific-trio/41883462 2014-11-20-microservices-141122015640-conversion-gate02
One of the upsides of Microservices is the ability to deploy often,at arbitrary schedules, and independently of other services, instead of requiring synchronized deployments happening on a fixed time. But to really leverage this advantage, we need fast, efficient, and reliable deployment processes. That's one of the value propositions of Containers in general, and Docker in particular. Docker offers a new, lightweight approach to application portability.It can build applications using easy-to-write, repeatable, efficient recipes; then it can ship them across environments using a common container format; and it can run them within isolated namespaces which abstract the operating environment, independently of the distribution,versions, network setup, and other details of this environment. But Docker can do way more than deploy your apps. Docker also enables you to generalize Microservices principles and apply them on operational tasks like logging, remote access, backups, and troubleshooting.This decoupling results in independent, smaller, simpler moving parts.]]>
One of the upsides of Microservices is the ability to deploy often,at arbitrary schedules, and independently of other services, instead of requiring synchronized deployments happening on a fixed time. But to really leverage this advantage, we need fast, efficient, and reliable deployment processes. That's one of the value propositions of Containers in general, and Docker in particular. Docker offers a new, lightweight approach to application portability.It can build applications using easy-to-write, repeatable, efficient recipes; then it can ship them across environments using a common container format; and it can run them within isolated namespaces which abstract the operating environment, independently of the distribution,versions, network setup, and other details of this environment. But Docker can do way more than deploy your apps. Docker also enables you to generalize Microservices principles and apply them on operational tasks like logging, remote access, backups, and troubleshooting.This decoupling results in independent, smaller, simpler moving parts.]]> Sat, 22 Nov 2014 01:56:40 GMT /slideshow/containers-docker-and-microservices-the-terrific-trio/41883462 jpetazzo@slideshare.net(jpetazzo) Containers, Docker, and Microservices: the Terrific Trio jpetazzo One of the upsides of Microservices is the ability to deploy often,at arbitrary schedules, and independently of other services, instead of requiring synchronized deployments happening on a fixed time. But to really leverage this advantage, we need fast, efficient, and reliable deployment processes. That's one of the value propositions of Containers in general, and Docker in particular. Docker offers a new, lightweight approach to application portability.It can build applications using easy-to-write, repeatable, efficient recipes; then it can ship them across environments using a common container format; and it can run them within isolated namespaces which abstract the operating environment, independently of the distribution,versions, network setup, and other details of this environment. But Docker can do way more than deploy your apps. Docker also enables you to generalize Microservices principles and apply them on operational tasks like logging, remote access, backups, and troubleshooting.This decoupling results in independent, smaller, simpler moving parts. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/2014-11-20-microservices-141122015640-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One of the upsides of Microservices is the ability to deploy often,at arbitrary schedules, and independently of other services, instead of requiring synchronized deployments happening on a fixed time. But to really leverage this advantage, we need fast, efficient, and reliable deployment processes. That&#39;s one of the value propositions of Containers in general, and Docker in particular. Docker offers a new, lightweight approach to application portability.It can build applications using easy-to-write, repeatable, efficient recipes; then it can ship them across environments using a common container format; and it can run them within isolated namespaces which abstract the operating environment, independently of the distribution,versions, network setup, and other details of this environment. But Docker can do way more than deploy your apps. Docker also enables you to generalize Microservices principles and apply them on operational tasks like logging, remote access, backups, and troubleshooting.This decoupling results in independent, smaller, simpler moving parts.
Containers, Docker, and Microservices: the Terrific Trio from J莨rme Petazzoni
]]> 17750 7 https://cdn.slidesharecdn.com/ss_thumbnails/2014-11-20-microservices-141122015640-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-jpetazzo-48x48.jpg?cb=1706984641 jpetazzo.github.io/ https://cdn.slidesharecdn.com/ss_thumbnails/devopscon-petazzoni-170613125035-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/use-the-source-or-join-the-dark-side-differences-between-docker-community-and-enterprise-editions-devopscon-berlin/76900911 Use the Source or Join... https://cdn.slidesharecdn.com/ss_thumbnails/orchestrationfortherestofus-170106234729-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/orchestration-for-the-rest-of-us/70760352 Orchestration for the ... https://cdn.slidesharecdn.com/ss_thumbnails/2015-11-16-dockercon-container-internals-160109181844-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/cgroups-namespaces-and-beyond-what-are-containers-made-from-dockercon-europe-2015/56860600 Cgroups, namespaces, a...