Posts Tagged ‘Docker’

Breakfast with ECS: Doubling Down on Docker

Corey O'Connor

Senior Product Marketing Manager at Dell EMC² ETD

Welcome to another edition of Breakfast with ECS, a series where we take a look at issues related to cloud storage and ECS (Elastic Cloud Storage), EMC’s cloud-scale storage platform.

Unless you’ve been living under a rock I’m sure you’ve heard of Docker at this point. If you haven’t, it’s time to dust yourself off and understand that Docker containers will wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools, system libraries – anything you can install on a server. This guarantees that it will always run the same, regardless of the environment it is running in. Genius right? Docker_1

The usage of containers has been around quite some time now, but the extra juice worth squeezing came from Docker’s ability to provide total isolation of resources to package and automate applications more effectively than ever before.  Docker provides system administrators and developers the ability to package any kind of software with all its dependencies into a container. Simply put, this resource efficiency standardizes each container and promotes massive scalability – this plugs in very nicely for cloud-scale, geo-distributed systems such as EMC’s Elastic Cloud Storage (ECS). In the early stages of product development, EMC took an early bet on Docker containers and it certainly has proved to payoff.


EMC {code} shares how to deploy ECS with Five Ways of Docker

Kendrick Coleman

Kendrick Coleman

Developer Advocate at EMC
Kendrick Coleman

Latest posts by Kendrick Coleman (see all)

We’ve been in a lot of conversations about DevOps recently, with customers, partners, community members and EMC teams. Whether or not you believe in the buzz around DevOps, there is definitively a wave of new and open tools, proclogo-emc-codeesses, and operational models being used in IT. These are all trends that can’t be ignored, and we’re continuously working to make sure EMC’s product strategy adapts with these changes.

EMC {code} is a developer evangelism team within EMC. We contribute to major open source projects, create our own tools and projects (also entirely in the open– in fact– you can find them all on GitHub, here), and engage with developer communities. Several of our team members have worked with EMC SDS products over the past few years, and we’ve enjoyed seeing the progress made to make our SDS tools readily accessible for developers and IT/ops alike.

ECS has long been a developer-friendly product, with universal protocols like object and HFDS, and a software-only download option. The recently announced ECS 2.0 is chock full of updates that are making the lives of dev/ops teams easier—including enhanced geo-caching, multi-tenancy capabilities, monitoring and reporting, and the ability to automatically and rapidly failover and recover from outages.

ECS 2.0 only enhances the experience for developers with a containerized download, free for test-and-dev environments (non-production use today). This has been another milestone in providing free and frictionless access to EMC software (along with the open-sourced CoprHD and free download of ScaleIO).

Our team works with Docker containers on a regular basis, and when ECS was announced, we rolled up our sleeves to see exactly how we could integrate Docker tools into the ECS experience.

In addition to the containerized download, we wanted to explore ways of deploying ECS with broader Docker technology. Deploying multi-node ECS is fast and easy with Docker tools. Using Docker Machine, you can deploy Ubuntu hosts that will be a part of a Docker Swarm cluster. With Docker Compose, you can deploy ECS from Docker Hub to a Docker Engine container on each host in the Docker Swarm cluster. If you are interested in how to do this, you can check out the GitHub repo or watch this quick video.

With this automated process, everything will be complete and configured in the span of 10-15 minutes. To get all of the details, please visit the EMC {code} blog post on the topic, or send us a tweet with your feedback to @EMCcode.



Connect with us on Twitter