Docker Acquires Tutum
blog.docker.com
blog.docker.com
Fix this, please, Docker. A few more points towards black isn't going to destroy the look and feel of your page.
Before: http://i.imgur.com/usg7GfW.png
I think Docker is just passing through the early adopter status in terms of actual production usage (it's much more mature in its lifecycle for dev), and having one of many cloud Docker providers owned by Docker might have a chilling effect on other 'container in the cloud' providers using Docker as their primary container format/platform.
Hosting companies will do what's in their best interest, and competing against an 'official' Docker container hosting solution might be less appealing than telling customers about their own system that uses (what may or may not be) a 'better' container format.
I don't think companies should want to lock you in with container formats. The ones that do should die. They should lock you in with services. IBM should lock you into its cloud by making you depend on Watson API, for instance.
In particular, Mesos seems super strong in the orchestration/scheduling layer, and its not clear that Docker will be able to dislodge them.
Swarm and compose are cute, but they simply aren't made for that kind of massive scale. The inverse of course, is that they are incredibly easy to setup, and they work for a very large number of workloads reasonably well.
I manage mesos clusters as part of $day_job. There is a certain level of setup required and if you don't need the scale, you simply don't need mesos for it. I really see them as complementary in the longer term. Perhaps a swarm mesos framework could be written. It is highly unlikely that Docker will ever do the resource scheduling better than Mesos.
There is a swarm/mesos integration whereby the Swarm API is offered to the developer but it uses the Mesos framework to do the scheduling.
It works, and there's more to come in terms of demos around the corner.
Both Microsoft and Amazon offer the Docker Subscription service on their respective Marketplaces and have active campaigns to promote them.
There are Docker Machine drivers that operate with every major cloud provider, allowing you to spin up new Docker nodes in seconds.
And as mentioned elsewhere in the thread, swarm integrates with Mesos and you can imagine any pure resource scheduler/framework can be integrated. Our goal is to provide the Docker experience to developers while being able to target disparate infrastructures, some of which are built purely with Docker and others built with an aggregation of tools.
I switched to Heroku only to realize that I had the same problem there too, obviously it was an issue in my app but at least Heroku have me an specific R14 error code and description of what was happening and finally knew what I was dealing with. For the next 48h that I was debugging the memory leak I had my dynos switched to 1X to get even more resource metrics, once the issue was solved I switched my dynos back to hobby.
I'm considering going back to Tutum now that I have deferpanic installed and configured in my app and my Heroku bills are around 100 USD monthly(20USD SSL endpoint x 3 + 7USD hobby dynos x 3 + 22.50USD Compose RethinkDB), but I was shocked to realize how much value a mature PaaS can deliver for clients even for a hobby-ish app like mine.
If I want to run locally, I have to ditch Docker entirely and just use Ansible: https://github.com/ansible/ansible-examples/tree/master/mong...
With plugins your volume can either live locally or on some other storage management system, like ceph, gluster, s3, etc. These are all working solutions today. `docker run -v importatndata:/var/lib/mydata --volume-driver ceph` Run that on two hosts and you get the same data.
In 1.9 there is the volume API that allows you to wire this up prior to docker run `docker volume create --driver ceph --o foo=bar --name importantdata`, then `docker run -v importantdata:/var/lib/mydata`
But "passes mustard" did give me a pretty funny visual image. :)
In 2011 dotCloud launches as a platform-as-a-service company.
In 2013 dotCloud releases docker, software based on the lessons they learned building their PaaS product.
In 2013 Tutum starts to build a PaaS based on Docker.
In 2014 Docker (renamed from dotCloud) sells their PaaS to cloudControl.
In 2015 Docker buys Tutum.
Anyone know how that actually works? Is it similar to Flocker at all?
Not sure if finally was the solution ;-)
Congrats too all teams!
edit:
updated tentative pricing image url as it looks like someone has deleted it off the tutum slack team site.
I have almost never been treated like such a piece of shit in my life. The attitude I got from multiple people on the Tutum team really drove home that they don't give a shit about loners like me, don't have time for my bug reports, and don't care what my questions are. It really left me thinking I must have said something inadvertently that totally offended them, but I couldn't find it anywhere when I looked.
I really hope I just got some of their team on a one-off bad day, or those people have since left, or something. It was really strange, and of course I immediately stopped using their software.
Yes, you can run Tutum on AWS, but why? When products can't substantially differentiate themselves against AWS, the customer will choose AWS. Customers don't want to be stuck in choice paradox.
Seriously - Tutum lets me rebuild my infra on Digital Ocean if/when AWS dies, and quickly. ECS, by contrast, is just POOF in that scenario.
The whole user experience is awesomely simple. If I had to describe these guys I'd say they are the Digital Ocean of the docker ecosystem.
Their 'Stacks' are so similar to docker-compose that only minor edits are required - and I expect with this acquisition even that will go in time.
And yes, finally a revenue stream for Docker I can believe in!
I've also been using Tutum and it's made life really easy, especially on my BYONode. I just hope they don't price the product out of reach for us hobbyists.
can you elaborate on this?
We're engaged with over 300 companies that are technically integrating in to Docker to enhance their product offerings, with 6-10 added every week.
Searching for "Tatum video introduction" on a search engine only returns results about a certain movie star, which is not terribly helpful.
Here is another youtube video: Getting Started with Tutum https://www.youtube.com/watch?v=fnV92aHLmyE
Congrats to the tutum team, they have built a really nice project that makes really easy to build and maintain container pipelines.
Can't wait to see the integrations with the other docker tools...
This has been in the works for much longer than that.
The Tutum team built a pretty amazing product that their users love, and the passion, excitement, and forethought both Borja and Fernando have around the space has impressed me since I met them in October of 2013.
I meant (as a user) that Docker Hub was at risk of losing its appeal because probably couldn't rival AWS's registry (pricing, speed, etc). IMO this move gives Docker a breath of fresh air ...
What's gone fast is the trajectory of these guys from launch (they're not even out of beta) to acquisition..
So, congrats to both teams!
Yes, lambda and friends (AWS Mobile Hub, JAWS Stack, etc) are the next paradigm, but it's not ripe yet. For instance the newly introduced cronjob only allows 5 mins periods as minimum, when for one of my projects I needed full cron precision (I was starting to build on Lambda and had to return to docker...)
Maybe in 6-12 months thing will be fully ready...
(I used to work for Iron.io)