Category: Latest Posts

Docker Tour de France

We are happy to announce that the Docker team will be Dockerizing France from Dec 8th to Dec 22nd 2014, right after DockerCon Europe 2014.


Jerome Petazzoni, Victor Coisne and Julien Barbier will be visiting Paris, Lyon, Lille, Nice and Bordeaux, and will present Docker to accelerators, incubators, schools and universities, including The Family, Epitech, 42, Paris Est, ENSEIRB… and to a lot of French companies and banks.

On top of this Docker is co-organizing with 42, Epitech and Zenika, several events open to the community:

  1. Dec 10th afternoon, Jerome Petazzoni will give a technical presentation of Docker, hosted at Epitech Lyon. Register here.
  2. Dec 11th afternoon, Docker will give three talks at 42:
    1. Marketing for hackers, by Julien Barbier. Register here.
    2. Panel: Work in the US as a French Tech Engineer. With Matthieu Laban, Florent Crivello, Jerome Petazzoni and Julien Barbier. Register here.
    3. Docker 101, a technical presentation of Docker, by Jerome Petazzoni. Register here.
  3. Dec 12th morning, Docker will give two talks at Epitech:
    1. Docker 101, a technical presentation of Docker, by Jerome Petazzoni. Register here.
    2. Marketing and Community at Docker, by Julien Barbier and Victor Coisne. Register here.
  4. Dec 12th afternoon to Dec 15th morning, Docker and Epitech are organizing a Docker Hackathon. This event will be open to anyone who wants to hack on Docker. The winning team will be offered tickets to DockerCon SF 2015, as well as plane tickets and hotel to go there. Register here
  5. Dec 17th morning, Docker and Zenika will host a breakfast with Partners and French companies. We will have a high level presentation of what Docker is and meet over breakfast. Contact us if interested.
  6. Dec 17th afternoon, Docker and Zenika will host a Docker technical presentation where we will dig into more technical detail. Contact us if interested.
  7. Dec 19th afternoon in Bordeaux at ENSEIRB: Docker 101, a technical presentation of Docker, by Jerome Petazzoni. Register here.
  8. More to be announced!

If you are interested to meet us in France, let’s talk! Please send us an email at

See you in France!

Docker-based Multi-Container Applications Run on AWS Cloud with Introduction of the EC2 Container Service


It was great to have Werner Vogels up on stage talking about “why developers love containers.”  That was a wonderful lead in to my Docker presentation in front of the 13,500+ person audience at AWS re:Invent listening to Werner’s keynote.  That kind of visibility is inspiring, but the thing I’m most excited about today is what great news there is for Docker and AWS customers with the launch of the Amazon EC2 Container Service.

This new product reflects AWS’ customer-driven approach to their cloud services and a recognition that their application developer community is clamoring for more Docker-based capabilities.  One can understand why, after listening to fellow keynote presenter Pristine highlight their application that provides seamless, secure Google Glass communication powered by Docker and AWS.  Pristine’s application is reshaping industries like healthcare where it can bring remote providers to the point of care in a new highly interactive fashion.

The initial focus of the Amazon EC2 Container Service is to address multi-container multi-host clustering, which aligns with customer requirements for high-performance and scale as they move their Dockerized distributed applications into production. We are thrilled that Amazon is pursuing a Docker-native approach to clustering.

The Amazon EC2 Container Service is a great follow-up to their announced support of Docker containers in Elastic Beanstalk in April of this year.   Both are signs of AWS’ commitment to Docker containers.  The launch of the Amazon EC2 Container Service comes with collaboration around Docker Hub our hosted registry service where Docker container-based applications are distributed, shared and collaborated on across the entire development community, or privately within an organization.  Making Dockerized application “content” directly accessible to AWS customers means that customers have access to over 50,000 Dockerized components that reside in Docker Hub.  These modular components allow an organization to leverage the best content from the community, while focusing its development efforts on a core set of differentiated services.   AWS also contributes directly to the Docker Hub Official Repository program most recently contributing a Dockerized GlassFish application server.

In addition to collaborating on content, both AWS and Docker are focused on improving application portability.  Dockerized applications are instantly portable to any infrastructure-–laptop, bare-metal server, VM or cloud.  Docker has focused on enabling AWS developers directly from their laptops to natively build Dockerized distributed applications on a Docker engine on AWS.  An early technical preview of Docker’s work in this area will be demonstrated today at AWS re:Invent in Session App303:  “Lightning Fast Deploys with Docker and AWS.”

The power of our collaboration can be seen in the results of another joint customer, the Gilt Groupe. Gilt is the market leader in flash e-tail, and has rebuilt its site on a Docker, micro-services based architecture leveraging AWS. “Docker helps us keep services isolated and simplifies our continuous delivery pipeline that in turn encourages innovation and experimentation across all of our teams” said Michael Bryzek, Gilt Groupe, CTO and founder.   Thanks to Docker and AWS, Gilt is able to make real-time changes to their service on average 100 times a day.  The ability to innovate at that pace is where all organizations should want to be with their next generation of distributed applications.

Amazon and Docker have a longer-term plan to provide close integration between the Amazon EC2 Container Service and the growing ecosystem of Docker-based services.  Both AWS and Docker, Inc are focused on enabling developers to quickly and easily take full advantage of container-based applications and deployment.

View AWS blog post

Read More on the news

tc-logo   forbes  gigaom     Zdnet-lightbg-200px   vb data The_Register_r   logo_infoq   iw

Announcing Docker Global Hack Day #2 Winners!

We are excited to share with you the final results from Docker Global Hack Day #2! We were super impressed by the level of participation from the Docker community with over 1,500 registrations in 82 countries. Thirty meetup groups organized local editions from which we received 34 projects. Kudos to the Docker community and the 60 Docker Meetup co-organizers for organizing an incredible event!

Screen Shot 2014-11-11 at 2.30.34 PM

Voting closed this morning and the results are in. Congratulations to Wei-Ting Kuo and Hsiao-Jung Peng of Docker Taipei who received 546 votes from the community for their project “Enable Fig to deploy to multiple Docker servers”. Wei-Ting and Hsiao-Jung, we look forward to welcoming you in Amsterdam for DockerCon14 EU!

Docker Taipei!



Other projects receiving top votes:

2. “Visual Docker” by Thomas Alrin & Yeshwanth Kumar & Rajthilak – 457 votes

3. “oki-docki” by Nicolas De Loof & Yoanna Dubreuil – 251 votes

4. “Dockit – Docker GlusterFS integration” by Humble Chirammal & Navid Shaikh & Saifi Khan – 244 votes

5. “Learning Data with Docker!” by Chia-Chi Chang – 152 votes

6. docker-stats” by Kristopher Francisco & Garrett Gregory & Matthias Blankenhaus – 128 votes

Thanks again to Rackspace, Geekdom SF, Microsoft AzureDigital Ocean and Online Labs for their support.

See you next year for the next Docker Global Hack Day!

Learn More

DockerCon Europe Hackathon

On the weekend before DockerCon 2014 which took place on June 9-10th in San Francisco, the Docker team decided to host a 24-hour Docker-centric hackathon at Docker HQ. The 3 winning teams (below) were offered free tickets for the conference and a chance to present their projects during the conference.



We all had a really good time thanks to all the participants and thought it would be fun to organize the European version of this DockerCon hackathon. Unlike the SF edition, we decided to schedule this hackathon on the Saturday following DockerCon Europe for people to hack on the new features and project announced during the conference.


As a Team of 1 to 3 hackers you will hack on a project using Docker as the central piece. You will have under 12 hours to complete this project including the time to create all materials needed for your 90 seconds presentation.

Although It is not allowed to start the project before the hackathon, we encourage you to think of the idea before coming to the hackathon.

The DockerCon Europe hackathon is limited to the first 150 RSVP. Please do not register if you are not sure to come.

The exact theme of the hackathon will be revealed at the last minute.


Even-though it is better to know about Docker before joining the hackathon, anyone can join.


The winning team will be offered:

– A ticket for DockerCon 2015 for each of the team members

– Plane tickets for each of the team members


The hackathon will take place at Nemo Science Center Oosterdok 2, Amsterdam

During the event, several Docker employees will be there to answer technical questions and help you fine-tune your Docker projects.


9am: Door opens

9:15 to 9:45am: Presentation by the Docker Team

9:45am to 10:30am: Find a team and an idea

10:30am: Start hacking!

9:00pm: Demo time

10:00pm: End of Hackathon

Let’s hack!

=> Register for the DockerCon Europe Hackathon

Learn More

Dockerized by Marianna Tessel SVP Engineering




I am incredibly excited to be spending my first week here at Docker!  The shift from a big, more established company back to the start-up world was a key element in my job exploration. For those of you who are also looking to be a part of the great things that are happening in tech, I want to share what drew me specifically to this thrilling opportunity at Docker:

  • Right concept:  The technology solves a huge problem for developers––it simplifies the development process and puts it on a continuum with deployment.  That leads to a new generation of applications that can be rapidly developed and incorporated into new services.
  • Open source:  This is the way to develop code today––you have an entire community of passionate users contributing. I am working on my first contribution too. Stay tuned!
  • Small but poised for growth: I can’t wait to have my hands in the details again and help with scale.
  • Ecosystem /Partners:  This became a passion of mine while at VMware. This is critical for any transformational software solution; Docker clearly falls under this category.  Good software is one thing, but for it to have enduring value, it has to have a vast and vibrant technology partner ecosystem collaborating and building upon it.
  • Important Intangibles:  On top of everything else, all the intangibles at Docker were right too!  It is a nice group of talented and humble people. The focus is on driving big changes and making the world better. The technology challenges are compelling. The pace is fast. Even the logo is right.

From what I can tell after two full days here, my choice was truly the right one!  I’m looking forward to becoming part of the Docker family and collaborating with the open source community and partners. As for my immediate plans, I am focusing on coming up to speed as fast as I can, and while I do not know the entire plan, I am certain of a few things: we will continue to build outstanding software users love, we’ll grow an already great team and culture, and we will have plenty of fun!


View the press release


Read More on the news

siliconANGLEtwitter    gigaom   Zdnet-lightbg-200px



Learn More

Docker Joins Dell’s Multi-Cloud Roadmap


Today, Dell took another stride forward with its multi-cloud roadmap by launching the Dell Cloud Marketplace beta program, which includes key industry alliances with Docker, Delphix and Pertino. The Dell Cloud Marketplace provides developers and IT managers with the ability to compare, purchase, use and manage public cloud services from a range of vendors, including Amazon Web Services, Google Cloud Platform and Joyent. This can be achieved through a single, unified console on




We at Docker are in full support of Dell’s commitment to accelerating the adoption of multi-cloud environments, particularly given the imperative of the Docker open platform toward ensuring portability across any infrastructure. Dell’s model for multi-cloud environments is forces, we are further validating the power of Docker for the cloud.

Together, we will provide developers with the ability to utilize Docker for frictionless application portability with a wide-selection of public cloud platforms via the Dell Cloud Marketplace.

Integrating Docker in the Dell Cloud Marketplace enables developers and system administrators to access the more than 50,000 “Dockerized” applications that are currently available in Docker Hub – while having the flexibility to choose public cloud solutions that are best suited for their respective business needs. Developers will be able to allocate their time more effectively, spending more time creating applications and less time creating and maintaining infrastructure.

Through this alliance, we are enabling accelerated development and deployment of distributed applications, and providing new dynamic business opportunities. We look forward to continued collaboration with Dell, and propelling the adoption of multi-cloud environments.

Dell is planning to provide Docker, Delphix and Pertino solutions via the Dell Cloud Marketplace in 2015.

Learn More

Docker Governance Advisory Board: Output of First Meeting

Docker has always prided itself on being a very open project. This past week, we took additional steps to provide visibility into the state of the project and explore ways to improve it by holding our first Docker Governance Advisory Board meeting.


The Docker project has been experiencing explosive growth for some time now. There are over 650 contributors (95% of whom do not work for Docker, Inc.). Non-Docker contributors and maintainers play a significant role in the project, and meaningful areas of functionality are now being led by organizations such as Red Hat, Google, IBM,  Microsoft, and others. Around Docker, a huge ecosystem of tools has emerged (over 16.5K projects on GitHub now have “Docker” in the title), and there are some 50,000 Dockerized apps in the Docker Hub public registry.

Of course, this volume of activity makes it especially important for the project to have a governance process that is both open and effective. And, given the close association between the Docker project and the commercial entity, Docker, Inc., it is critical that people building on the Docker platform have confidence that the project is being run in a way that encourages the ecosystem, that there are clear “firewalls” between the project and the company, and that the project has accountability to the broader ecosystem.

To that end, in June, we formed a Docker Governance Advisory Board, consisting of elected representatives drawn from contributors, maintainers, vendors, and users. The DGAB is intended to meet regularly to provide advice and input to the project leadership, to serve as a focal point for reporting on the state of the project, and to provide an additional forum for raising concerns and discussing major issues. We also committed to making all output and notes from these meetings public.

If you want to immerse yourself in the results of the DGAB meeting, you can view the notes, DGAB charter, presentations, and action items located here.

If you’d like to get a first hand view of the meeting itself, please read the excellent guest blog post by Nicola Paolucci of Atlassian, one of the “user” representatives on the DGAB.


From my perspective, there were a number of interesting outcomes. First, we reported on the progress made as a project, both in terms of adoption and in terms of community openness. As you can see from the tables below, Docker has been experiencing tremendous growth, with a huge uptake across almost all measures since DockerCon in June.


Table 1: Selected metrics change since Docker Con (June, 2014)


Table 2: Docker Growth (stars) vs. Select Other Open Source Projects



In order to keep up with this growth, the team has been evolving its processes and procedures for maintaining, contributing, merging, etc.  Some key stats are replicated below. As you can see, the project has had close to 4,900 pull requests since inception, over 76% of which have been merged and approximately 2% of which are still open. Over 50% of all PRs are merged or closed within 1 day, and over 94% are merged or closed within 30 days. Critically, these stats do not change markedly for PRs created by non-Docker, Inc. employees, athough there is clearly some room for improvement in addressing a small number of PRs that are not closed in a timely manner, and there is some room for improving the experience of non-Docker, Inc. contributors


Table 3: PRs for the project


Table 4: PRs over time


While we are, in general, happy with the state of the project, it is clear that there is more work to do. While the detail can be seen in the notes,there are three broad areas where we should drive improvement

1)Providing more mature tooling, CI, process, etc. to enable the project to scale as a whole

2)Ensuring that we address the small percentage of PRs that have been outstanding for a long period of time

3)Ensuring that the is a clear boundary between Docker Inc and the Docker project, including mechanisms for explicitly addressing situations where a decision made by the project leadership is perceived to be  driven by Docker, Inc. commercial interests rather than what is best for the project as a whole.


Table 5: Areas for Improvement

Some of the concrete steps that were proposed include:

1)Docker, Inc. is creating a separate organization (called Team Meta) that is funded and chartered solely with making the project more effective (e.g. dedicated resources on tooling, docs, PR review, roadmap publication, etc.) This team will have significant organizational autonomy from the rest of Docker Inc.

2)We have enabled an escalation process for perceived conflicts of interest (see meeting notes for more details)

3)The team has enabled a regular, open process for reviewing long-standing PRs (the first such session was held this week)

4)The team is creating a more easily digestible version of the long term roadmap, including a mechanism for seeing the status of proposals for major, new functional areas (e.g. networking, storage, etc.)


Again, for more information, please see the notes and output of the meeting.

If you have specific feedback, please either write to or, better yet, open a pull request!

Thanks to all of the participants. Special thanks to Nicola Paloucci of Atlassian for taking notes and Van Lindberg of Rackspace for serving as Chair.



Guest Post: Notes on the First Docker Advisory Board Meeting

*This is a guest post by Nicola Paolucci, Developer Advocate at Atlassian.


Last Tuesday (October 28th, 2014) downtown San Francisco hosted the first Docker Advisory Board meeting. I was very flattered and humbled to sit on the board as one of the representatives of the Docker users.

I came away from the works of the Advisory Board with a great sense of accomplishment and excitement. I feel the Docker maintainers addressed with clarity and openness many of the delicate issues that were brought up.

In addition to that, the details of the Docker roadmap were very juicy and exciting to me!

That the Docker project is listening intently to feedback from developers became even more apparent to me with the recent 1.3 release which smashed many usability issues I ran into in my Docker practices. So much so that my talk on being a happier developer with Docker is in dire need for a rewrite. And that’s a good thing!

What happened at the Advisory Board? Several intensive hours of analysis and dialog happened. The works of the board are obviously hard to summarize in a single post, so in the following I’ll pick a few themes that I found interesting. Others are welcome to chime in with their take. In any case the minutes of the meeting are public now. All documents presented during the meeting are in the open too.

Managing a thriving community is complex: Docker needs more maintainers.

Number were shared on the state of the project and the size and number of community contributions is really impressive. You can check the charts in the Docker Project Governance presentation. Numbers were both encouraging and healthy, and the conversation focused on how to improve the process so that pull requests would not stall and be ignored.

The maintainers proposed that to stay responsive to contributions they must expand the number of the maintainers and specialize them. To this end they plan to appoint several new figures in the community like a “Roadmap maintainer”, a “Tooling maintainer”, a “QA maintainer”, and so on.

Consensus also formed to create a process to review pending pull requests that stay open for more than 30/60/90 days. This process would verify why contributions stalled and take action if needed.

Chief Maintainer Solomon Hykes made clear that the main reason why a (relatively low) number of PRs stall is because the maintainers really care about clean design and are wary to accept a big drop of tens of thousands of lines without some previous design discussion happening. They want to get better at fostering a conversation before the big drops happen.

They care very much about being transparent about this so they want to change how people can submit larger contributions.

Contributors are encouraged to start a major piece of work by submitting a “documentation” pull request so that a conversation can happen around design before the implementation gets too far without review. The board talked about establishing PEP like process, and Docker itself already has a “DEP” like process but with the above tweaks they want to improve it.

Clear statements about keeping Docker Open

At several points during the morning some concerns were voiced about the relation between “Docker Inc. the commercial entity” and “Docker the Open Source project”. Docker Inc.’s CEO Ben Golub clarified repeatedly that the success of Docker lies in it being a fully Open and community embraced.

In addition to the above Solomon reiterated several times that concerns about monetization are very much outside of the worries and thoughts of the maintainers. Their major design principle are clean design and usability.

To support the above vision of openness Docker Inc. proposes to sponsor a separate team called “Team Meta” which will work independently from the commercial entity Docker Inc. and is tasked with the maintenance of the Open Source project.

Distribution specific contributions, extensibility concerns and the Registry

The meeting had a healthy dose of polite debate over several governance topics.

RedHat contributors voiced relevant questions regarding patch approval and Distributions specific needs.

Google representative voiced the need for Docker architecture to be pluggable or at least extensible enough for companies to plug-in their own auth systems, storage systems, private “Registry”, etc. This concern matched well with one of the top priorities of the maintainers: to provide a high level of pluggability in Docker.

Several times during the works of the board the topic of the public Docker “Registry” came up. A healthy debate spurred on the need for a stable, globally available name-space and how to go about it, if a central authority was needed, if to use URLs to uniquely identify containers, if a config file would be ideal or not.

Solomon explained his current thinking on the registry: Docker the Open Source project needs a well funded central registry to be able to operate viably. He cited his past experience with PyPI as an example of a best effort central repository which had a huge problematic impact at his previous startup. He wants to avoid this flakiness very much.

Solomon is in favor of a short form, global name-space, managed by a central entity. But the Registry is designed to be swappable and replaceable as a founding design principle, even though in the current implementation it is more coupled to Docker than they’d like. Major work is ongoing to improve this.


An exciting section of the works was on the “Docker Project Statement of Direction“. This roadmap presentation was very interesting and I can only scratch the surface of what was presented. The maintainers highlighted the major areas where they intend to or already are directing efforts. The areas are:

– Orchestration: I was told wait for the Global Hack Day for a sneak peak :D. That didn’t disappoint!
– Networking: this is known ad *”links v2″* and they are making the default design more IP centric.
– Storage
– Provenance: 1.4 will have image self signing most likely. They will also work on key management.
– Plugin API: they are reworking Docker to have a Plugin architecture.
– Multi-Architecture Support: support for ARM architectures and 32-bit architecture was mentioned and efforts are ongoing.

Clarification on the Microsoft Partnership

Recently Docker announced a partnership with Microsoft. The maintainers are very excited about the partnership with Microsoft. To address platform concerns they made clear that:

-The Docker Windows Daemon will be created in the open, under the governance of the overall Docker project.

– Microsoft will not have back channels or priority into the contribution process, they will have the same access as any other contributing organisation

-Community members can review and contribute to the Docker Windows daemon as they would any other part of the project

– Rackspace is very keen to participate in the efforts to get to a Windows client.

Electing Chair and Vice Chair

The works of the board ended with a quick ballot to elect the Chair and Vice Chair of the Board: we appointed Van Lindberg (Rackspace) as Chair and Brandon Phillips (CoreOS) as Vice Chair.


Last week was very eventful and full of happenings in the Docker sphere. Not only the DGAB convened for the first time but the demos of the Global Hack Day, Docker hosts and Docker clustering, were very very impressive. I can’t wait for those efforts to be available to the general public too.

I am now more convinced than ever that the future is bright, distributed and dockerized!

*Nicola will be presenting “Be a better developer with Docker: tricks of the trade” at DEVOXX next week and will hold a surprise BOF session at DockerCon EU 4th-5th December in Amsterdam, stay tuned!*

Save the date for DockerCon 2015

Today we are very happy to announce DockerCon 2015, the second edition of the official Docker conference organized by Docker, Inc in the United States. The conference will take place in San Francisco, at the the San Francisco Marriott Marquis on June 22nd and June 23rd, 2015.



With more than 400 people on the wait list for both DockerCon 2014 and DockerCon Europe and due to popular demand, we decided to significantly increase the number of attendees to 2000 people. While we want to preserve the ambiance and simplicity of the first DockerCon, increasing the number of attendees, speakers and sponsors seems necessary to reflect Docker’s blooming ecosystem and community.

The official website is still under construction as we are still working on DockerCon Europe, but today we can announce that the vast majority of the Docker team will be present as well as incredible speakers from the Docker community.

DockerCon 2015 will be a two-day Docker-centric conference gathering Docker experts, contributors and partners from various countries and fields of study. In addition to the classic Docker use cases (i.e Continuous Integration, Continuous Delivery, Cross Cloud Deployment and Portability, Agile scaling, Testing, PaaS, etc), we hope to receive submissions from speakers who (we know) have been using Docker for Bioinformatics analysis, Radio Astronomy, Energy data transmission and more. So without waiting for the website to be ready, we’re thrilled to announce that the Call For Papers opens today.

We will also be speaking about the future of Docker from quality & security improvements to new features and projects around authentication, provenance, networking, composition, clustering, etc. There will be plenty of talks for a large audience of Developers, SysAdmins as well as C-level executives whether they are newbies or seasoned users.

Following the success of the Docker Global Hack Day #2, we are organizing a 2 days Hackathon during the week-end prior to DockerCon 2015 and full day of training following the conference. Led by our team of Docker experts, this training will be the best way to get up to speed with the latest features, patterns and best practices announced during the conference.

 In a nutshell, here is what you need to know (for now):

  • Venue: San Francisco Marriott Marquis, 780 Mission St, San Francisco, CA 94103
  • Hackathon dates: June 20 – 21, 2015
  • Conference dates: June 22 – 23, 2015
  • Training date: June 24th, 2015
  • CFP: You can submit your talk here.
  • Sponsorship: If you are interested in our sponsorship options, please contact us at

We invite you to follow the official twitter account: @DockerCon and hashtag #dockercon in order to get the latest updates.

Save the dates and stay tuned for more announcements!


– The Docker Team


Learn More

Your Docker Schedule at the OpenStack Summit in Paris


OpenStack (1)openstack




Next week starts the OpenStack Summit at the Palais des congrès in Paris, France. If you are attending the conference, come talk to us and learn more about Docker at the Intel booth A2. Our very own Eric Windisch will be there on Wednesday morning to lead an expert session and answer all the questions you might have. A big thanks and shout out to Intel for hosting a Docker demo station at their booth.


Here is the list of Docker-related talks, demos, discussions that we think you’ll find interesting:

Monday, November 3rd


12:30 – 13:10 – Marketplace Theater

Digging Deep: OpenStack Neutron and NSX with KVM, Docker, vSphere, Hyper-V, Xen and Bare-Metal Hosts

Speakers: Somik Behera (VMware) and Eric Lopez (VMware)

This session is a technical deep dive on the OpenStack Neutron’s Network Virtualization capabilities with default NSX Plugin and demonstrates an OpenStack Cloud with KVM, Xen, vSphere, Hyper-V, Docker, & Bare-metal compute platforms communicating over a single virtual Network.The good, the bad & the ugly from a field deployment practitioners perspective. We will  also cover one of Neutron’s Network Virtualization plugin’s detailed overview and deep dive into real life benefits & challenges. We will be covering NSX Plugin – a virtual networking platform powering many OpenStack production environments as the networking engine behind Neutron. In this session we will explore the distributed systems architecture of the NSX Controller Cluster, the core functionality and behavior of NSX primary system components, and the logical networking devices and security tools NSX produces for consumption. High availability deployments, and packet flows for common scenarios will be discussed.And finally, we’ll take a look at how the physical network fabric can be architected for Virtualized Network deployment architectures, be it with out without NSX.


19:00 – 21:00 – Le Méridien Etoile

The New Stack WarmUp at OpenStack

The role of Docker, orchestration and container ecosystems in the OpenStack ecosystem. We’ll have discussions, do interviews and trade stories about this new movement. Come meet The New Stack Founder Alex Williams and enjoy some food, drink and conversation at Le Méridien Etoile during the OpenStack Summit.


Tuesday, November 4th


11:15 – 11:55 – Room 242AB

Building the Cloud Ecosystem OpenStack, Docker, Kubernetes

Speakers: Shane Gibson (Symantec, Corp), Chinmay Naik (Symantec, Corp)

Abstract:  Openstack has slowly and steadily grown into a main stream IaaS cloud solution provider technology. At Symantec, we have primarily used Openstack to virtualize our datacenters and help drive infrastructure automation to ensure maximum use of our compute, network and storage capabilities. But many of our enterprise use-cases demand more than just virtualized environments. There is a need for certain applications to run on linux container like environments and make use of some of the advantages provided by these platforms.In this presentation we will talk about how Openstack can be used along with other open source cloud technologies to build an ecosystem to solve all use cases and problems faced by today s enterprise world. We will try to present a performance based evaluation of the three most popular technologies out there Openstack, Docker and Google s Kubernetes and propose a solution that may help you achieve infrastructure automation in its complete sense.The following topics will be covered in this presentation:

  • Categorize enterprise use cases that can be solved using Openstack, Docker or Kubernetes.
  • Performance analysis and benchmarking
  • How can Openstack be used as the central scheduling and orchestration engine to integrate with other open-source cloud technologies?
  • Can the ecosystem eventually be scalable, reliable, secure and truly multi-tenant?


12:05 – 12:45 – Room 253

The New New Thing: Turning Docker Tech into a Full Speed Hypervisor

Speakers: Tycho Andersen (Canonical) and Dustin Kirkland (Canonical)

Abstract:  From PAAS to IAAS, this is the container session that will most accelerate your plans for 2015. Linux containers are all the rage these days, with LXC, Docker and Parallels moving to the centre of large-scale operational thinking. Ubuntu and Canonical have lead this revolution, with Canonical-led LXC at the centre of standardisation of different approaches to containerisation. In this talk, we’ll look at how the Docker phenomenon will generalise into a full-scale, full-speed hypervisor for your scale-out infrastructure.


14:50 – 15:30 – Salle Passy

A Practical Approach to Dockerizing OpenStack High Availability

Speakers: Kalonji Bankole and Daniel Krook (IBM)

Abstract:  High availability in OpenStack can be achieved in many ways.  In this session we will describe how Docker can be used to provide an active-active highly available OpenStack environment. We will focus the real world work that we have done to “Dockerize” OpenStack services, detail the advantages to this type of deployment (rapid deployment, rapid scale out, versioning, etc.), and walk through our design – from requirements, limitations, obstacles, and especially our decisions.

We will use our experiences as examples to provide real world best practices, as well as showing a demonstration of the environment in action.


15:40 – 16:20 – Room 242AB

Docker Meets Swift: A Broadcaster’s Experience

Speakers: Alberto Messina and Eran Rom

Abstract:  RAI (Radiotelevisione Italiana), Italy’s national public broadcasting company, has to deal with the growing cost for new storage hungry media formats (e.g., 4K UHDTV), while also enabling its employees to collaborate and manage content across geographically separated sites throughout the media production cycle. To address these needs, we have integrated Docker with Swift via a generic mechanism we call “storlets”. Integrating Docker with Swift keeps the storage cost low as well as co-locating compute to avoid costly network transfer for a wide range of media workflows. In this talk we will present the problem RAI is solving including its requirements, present the storlet mechanism, demonstrate how storlets can be used for media workflows and other scenarios, and place our work in the context of other efforts.


16:40 – 17:20 – Room 242AB

Orchestrating Docker with OpenStack

Speakers: Eric Windisch

Abstract: The Nova driver for Docker has been maturing rapidly since its mainline removal in Icehouse. During the Juno cycle, substantial improvements have been made to the driver, and greater parity has been reached with other  virtualization drivers. We will explore these improvements and what they mean to deployers. Eric will additionally showcase deployment scenarios for the deployment of OpenStack itself inside and underneath of Docker for powering traditional VM-based computing, storage, and other cloud services. Finally, users should expect a preview of the planned integration with the new OpenStack Containers Service effort to provide automation of advanced containers functionality and Docker-API semantics inside of an OpenStack cloud.

Dockerize early and often,

– The Docker Team

Learn More