Software-defined storage (SDS) has usually meant storage that augments, optimizes, aggregates, and presents some form of cloud gateway. It is storage manipulated by an automation with an orchestration layer that ties differing data functions together. The ultimate in automation and orchestration for storage is the inclusion of Docker. Docker, or any container technology, needs storage—persistent storage. How storage is presented to Docker is unimportant to Docker. It is, however, important to the storage team. SDS is about making storage simpler by reusing, improving, or automating delivery. How does your storage fit with Docker?
Articles Tagged with Docker
RightScale just published its annual report on the state of the cloud, and some of the key findings are very interesting. Topics range from cloud vendor market share to cloud adoption concerns, DevOps tools adoption, public vs. private cloud adoption, and much more. Below, I highlight the major findings I thought most interesting and follow each with my perspective on it.
Docker, the leading vendor in the container industry, has been dipping into its pockets again, this time to acquire French file sync company Infinit. Yep, Docker, the company whose core product is a container management and deployment technology, is acquiring a consumer file sync company.
At first glance, this is an odd acquisition. Infinit is a company with a product that appears similar to Aspera, Accellion, or even good old-fashioned FTP. If you need to share your files, but email send or receive limits are getting in the way, Infinit allows you to create a Share directly to other Infinit users or a link that can be emailed to non–Infinit users to access your files directly, thereby allowing them to download them for review or further work.
When we were first introduced to Docker containers, we were told that they should be ephemeral and stateless. It turns out that there are lot of great uses for Docker containers that are either stateful or long-lived. The stateful part is leading to a bunch of startups that have storage products to deliver persistent storage to these stateful containers. Even our old friends at VMware are in on this game. Their Photon platform is going to include VSAN to provide persistent storage for containers.
How do you distribute an application that uses containers? This seems to be an odd question. Container-based applications are usually associated with Software as a Service (SaaS) applications and public cloud deployment. However, there is still a place for software that is purchased and installed on-premises in a data center. If the software is in the form of containers that will run inside the customer’s data center, then how will the software be deployed and managed? How will scaling work, and how will updates be deployed?
There has been a lot of discussion recently about whether forking Docker makes sense. Driving this discussion are complaints from the Docker community and ecosystem about the speed at which Docker is releasing software and the perceived quality of those releases. Unless you have been hiding under a rock lately, you know that Docker is one of the most popular open-source projects in the world. Docker’s rise from a concept to a dominant force in the industry is a story for the ages. As Docker and containers continue to gain adoption in both non-production and production environments, vendors have been flocking to provide services that support or enhance Docker containers.