11–20 of 21 posts
I cant read this whateveritis because the fonts are too gray/white as the background. Skimming through it, yes whatever you define as "enterprise" can fit your definition and whatever claim you are doing in the article or blog, can be fulfilled.
Sorry about that, antocv. I've spoken to our web team about the colour scheme a few times already.
Thanks to agumonkey for the link!
I cant read this whateveritis because the fonts are too gray/white as the background. Skimming through it, yes whatever you define as "enterprise" can fit your definition and whatever claim you are doing in the article or blog, can be fulfilled.
It happens every time. As soon as you hit an environment where there are > 20 people using the system you need a plethora of tools and systems involved which remove the terms, "simple" and "lightweight," from the specification. Access control, authentication, auditing, operations... you can't eschew complexity by ignoring it. I've learned this time and again. If you start out with "simple" and "lightweight" you're go…
> I wouldn't be surprised if even Rocket becomes bloated as they realize they cannot design for simplicity when complexity is a requirement. That was pretty much what I was trying to get at with the question of how a "Rocket ecosystem" would address these requirements. I think vidarh makes a valid point that these could be met by tools outside the container system that are better suited...but I am curious as to what…
I think we're finally seeing the first iterations of the operating system disappearing into the network... an idea that has been touted for some decades.
You've got your conclusions backwards. Docker is the one that's trying to do things the simple way. Rocket embraces the Unix process model and philosophy. They don't have to solve this particular security problem because it's been solved over almost 40 years of Unix evolution. The Docker simplicity is why they've had so much success. That's how it started: as a tool to make using LXC simpler.
> The Docker simplicity is why they've had so much success. That's how it started: as a tool to make using LXC simpler. Do you feel Machine, Swarm and Compose add to or detract from the value proposition of Docker, in that case? Just to ensure I'm understanding your point about Rocket benefiting from 40 years of Unix evolution correctly: do you think that Rocket will be able to remain simple as a result of this? And…
It happens every time. As soon as you hit an environment where there are > 20 people using the system you need a plethora of tools and systems involved which remove the terms, "simple" and "lightweight," from the specification. Access control, authentication, auditing, operations... you can't eschew complexity by ignoring it. I've learned this time and again. If you start out with "simple" and "lightweight" you're go…
The Rocket ecosystem will be necessarily complex.
I cant read this whateveritis because the fonts are too gray/white as the background. Skimming through it, yes whatever you define as "enterprise" can fit your definition and whatever claim you are doing in the article or blog, can be fulfilled.
Well, I can't read it at all on my android phone, because whatever javascript they use, prevents me from scrolling down. While the page was loading, scrolling worked, but as soon as everything loaded up, it jumped back to the top and stuck there. I hate today's web, where people are apparently unable to serve a plain text article without javascript.
Earlier quoted context omitted.
Well, I can't read it at all on my android phone, because whatever javascript they use, prevents me from scrolling down. While the page was loading, scrolling worked, but as soon as everything loaded up, it jumped back to the top and stuck there. I hate today's web, where people are apparently unable to serve a plain text article without javascript.
sigh . Sorry about that. Did agumonkey's link work for you?
It happens every time. As soon as you hit an environment where there are > 20 people using the system you need a plethora of tools and systems involved which remove the terms, "simple" and "lightweight," from the specification. Access control, authentication, auditing, operations... you can't eschew complexity by ignoring it. I've learned this time and again. If you start out with "simple" and "lightweight" you're go…
Of course Docker in an enterprise will never be as simple as running a Rails app on your Macbook, but it provides an encapsulation primitive that looks as powerful for deployment as object orientation and functional programming were for development.
SICP lecture #1: we manage complexity through means of abstraction and means of combination. Docker is a means of abstraction, and it leaks less than the others we have so far (Chef cookbooks, etc.) We haven't quite figured out what the means of combination is. It won't be trivial - writing programs certainly isn't - but it will be better than handrolled assembly.
It happens every time. As soon as you hit an environment where there are > 20 people using the system you need a plethora of tools and systems involved which remove the terms, "simple" and "lightweight," from the specification. Access control, authentication, auditing, operations... you can't eschew complexity by ignoring it. I've learned this time and again. If you start out with "simple" and "lightweight" you're go…
The difference is that some technologies use encapsulation and abstraction to manage complexity, while others vomit megabytes of configuration on the floor. Of course Docker in an enterprise will never be as simple as running a Rails app on your Macbook, but it provides an encapsulation primitive that looks as powerful for deployment as object orientation and functional programming were for development. SICP lecture…
Definitely. And I think if we can move more to discussions along the lines of "how do we best abstract/encapsulate/handle the inevitable complexity," rather than "wow, this technology looks like it will solve all our problems," that would be great.
I know the latter sounds absurdly simplistic, but I still hear an awful lot of it around.
He's setting up a nice strawman. I didn't see anything in the Rocket proposal that implied they thought the things Docker wants to add aren't needed , just that they object to the direction and want to be able to pick and choose from components that fit their purpose better, and want guarantees of interop through open formats etc. Who is propagating this myth of the "Simple, Lightweight Enterprise Platform" to begin…
> I didn't see anything in the Rocket proposal that implied they thought the things Docker wants to add aren't needed I was referring mainly to this statement: "We should stop talking about Docker containers, and start talking about the Docker Platform. It is not becoming the simple composable building block we had envisioned." I agree with you that that doesn't necessarily mean that the Rocket team disputes the need…
That's part of the point. They want to be free to compose components depending on their customers needs.
CoreOS already includes Fleet (orchestration of individual units), and their are putting effort into Flannel (overlay network), and Kubernetes (orchestration of "pods" of containers).
But their market is enterprises that in many cases will want to fit CoreOS into an existing enterprise platform.
Nothing in how CoreOS is acting has shown any indication that they think enterprise is "simple". On the contrary, Rocket, while smaller in scope than Docker, if anything is more complex (with the signing, composability of filesets, and implied support for running systemd in the containers).
I'm not convinced Rocket is the right thing - they'll have to show me tooling that makes it as simple as Docker first - but some of the decisions appeals to me (a clear spec for the format, that alternative runtimes can conform to; e.g. nothing appears to prevent someone from making a Rocket runtime ("ACE") that uses KVM or Virtualbox or Xen, and hence it could be potentially supported by things like OpenStack, or even shoehorned into a VMware deployment; making things like whether or not an overlay filesystem is used an implementation detail; and while I won't need it often, and it may be an annoyance in some cases, support for signed images).
So I just see nothing to imply that CoreOS is a good exponent for some idea of "simple, lightweight enterprise platform". They are providing a set of tools that individually are simple and lightweight, that you can use to start building the lower levels of an enterprise platform with, though, and understandably don't want one of those tools to grow into a platform itself (whether or not Docker will grow into that in a way that doesn't allow the core container execution mechanism to be easily lifted out, is a separate discussion).