What Docker Means For VMware, Cloud

About Us

Advertise

Newest First | Oldest First | Threaded View

[close this box]

50%

BanuP423,
User Rank: Apprentice
6/7/2015 | 1:37:17 PM

Docker in the enterprise

Docker may solve the issue off vmware node based pricing model but increases the license cost for enterprise software for weblogic or websphere etc.. For example if we were to Dockerize weblogic for each microservices, the number of weblogic deployments will increase dramatically. in the pre-Docker/containerization world we could deploy multiple services on to one instance of weblogic and pay the license for one weblogic instance.

With Docker, enterprises are forced to enter into ELAs with Oracle, IBM or EMC/VMware to leverage economies of scale. Unless the enterprises decide to move away from these enterprise software and adopt opensource software such as ngnix, tomcat or nodejs, the costs will out weigh the benefit.

It is great that Docker abstracts the datacenter but it opens the door for increased license costs on the enterprise software.

Start ups can benefit greatly from Docker but large established enterprises will have to do some real homework before they sign up for Docker.

Reply | Post Message | Messages List | Start a Board

50%

bobneurone,
User Rank: Apprentice
12/13/2014 | 5:35:33 AM

economy will drive container adoption

If do not doubt at all that container management and migration will be the key of its adoption by cloud providers, I also do think the economic factor will be an important one. The current stack logic of a virtualization layer with VM's embedding each an operating system impose a costly structure because hypervisor cost is based on node infrastructure RAM size plus an operating system cost for each VM on top. Containers invert this logic with one single operating system per infrastructure node and multiple containers with likely much lower costs than the hypervisor. Beyond that the lower resource footprint of containers versus the virtualization architecture should help to make quickly an economic difference.

Historically, operating systems role was to manage infrastructure resources (memory cpu, network, storage) thus providing technical services to applications. As someone mentionned, it is really too bad that operating systems did not provide earlier containers. This would have probably avoided the costly parenthesis of virtualization. Containers will put the operating system back at the right place it should have never quit on top of hardware.

Reply | Post Message | Messages List | Start a Board

50%

Laurianne,
User Rank: Author
6/19/2014 | 3:48:12 PM

Re: Online Migration of Containers works

Charlie, what do you make of the security questions being asked around containers in the past few days? Was this a big topic in thre halls at Structure conference?

Reply | Post Message | Messages List | Start a Board

50%

Charlie Babcock,
User Rank: Author
6/16/2014 | 3:13:27 PM

Re: Online Migration of Containers works

Good point, Neuroserve. I think it should be possible to move containers around among like hosts, increasing server utilization and energy efficiency. Just because we're not there yet doesn't mean we won't get there. In some ways, containers should be easier to migrate than VMs. But it will help if there is one management system to do both.

Reply | Post Message | Messages List | Start a Board

50%

neuroserve,
User Rank: Apprentice
6/14/2014 | 2:45:59 AM

Online Migration of Containers works

You write: "Workloads can be moved around while running to maximize utilization of servers -- containers cannot."

That is probably true for the current state of Docker containers. Live migration of OpenVZ containers works for a very long time already. If you have a recent Linux kernel you probably have the patches from CRIU (criu.org) and should be able to do "checkpoint and restore" with "normal" containers, as well. If you use ploop for your container images, your live migrations can be very fast. I'm looking forward to see criu and ploop used with docker. But with Docker there seems to come a "doctrine", that favours short running containers instead of long running ones (hypervisor based VMs are also long running). Container = Application is the mantra here (ore more specific: One instance of an application is one container - just like Google does it).

Neuroserve

Reply | Post Message | Messages List | Start a Board

50%

Charlie Babcock,
User Rank: Author
6/13/2014 | 6:27:06 PM

About that $10, Joshua...

By unlikely allies, I mean Red Hat, IBM and Rackspace, among others. For months, Red Hat has seen the value of Docker, worked closely with Docker Inc. and moved to get Docker containerization inserted into Open Stack through a PaaS approach in Project Solum. Meanwhile, IBM and Rackspace put their money down on Cloud Foundry, with its different approach to PaaS. Piston's Joshua McKenty even bet $10 that Red Hat would join Cloud Foundry by the end of the year. At DockerCon, all the movement was in the other direction. Rackspace CTO John Engates praised Project Solum from the podium. IBM cited Docker's efficiencies and Cloud Foundry announced it was a Docker backer too. Instead of Red Hat joining Cloud Foundry, it looks like Cloud Foundry members are trying to catch up with Red Hat.

Reply | Post Message | Messages List | Start a Board

50%

TeaPartyCitizen,
User Rank: Apprentice
6/13/2014 | 6:17:17 PM

It never would have been a big deal

If Unix and Linux had seperate name spaces per process by default when Unix was invented and had the ability to share name spaces with groups, containers would have never been a big deal. People would have always programmed like that and the paradigms and models would all be very mature by now. It's not like we needed the Higgs Bozon descovered inorder to develope this feature. I'm just saying it could have been done earlier. That said, containers will make a release engineer's eyes glow. I saw this when I first learned of them.

Reply | Post Message | Messages List | Start a Board

50%

Charlie Babcock,
User Rank: Author
6/12/2014 | 4:32:57 PM

Containers below the radar of most systems management

Laurie, Kubernetes could be the next big thing in open source code. If we get a proliferation of Linux containers, The need to create, deploy and manage them will overwhelm IT because they'll be outside the view of virtual machine and physical systems management, Is Kubernetes up to the job?

Reply | Post Message | Messages List | Start a Board

50%

Laurianne,
User Rank: Author
6/12/2014 | 12:58:57 PM

Kubernetes

I had not heard of Kubernetes befire this week, and I'm guessing many people had not heard of Docker. Charlie brings some useful context to why containers have quickly become a polarizing topic in cloud.

Reply | Post Message | Messages List | Start a Board

Reports

The State of Cloud Computing - Fall 2020

Download this report to compare how cloud usage and spending patterns have changed in 2020, and how respondents think they'll evolve over the next two years.

Download Now!

More Reports