6 ms·
Give Me Bare-Metal
- voidz 12y agoDocker is written by developers of which there are too many. But it sucks to many of us who are sysadmins. Docker's networking isn't all that, and the storage is basically just nifty because of already-existent tech like AFS and BTRFS. I think docker is nothing more than a hype from a new generation who wants everything hip, simple, fun, fantastic and awesuummm and the older and more experienced sysadmins like me have seen this coming years ago. It was inevitable, and now it's just a matter of waiting until the lazy generation finds out what we've been seeing all along: Docker is an abstraction of other technologies and you don't need Docker at all.
- jraedisch 12y agoAnd everyone will eventually realize, that he/she should have learned those other technologies right from the start? Would it really be worth the effort, especially if you are devops and app dev in one person, always having to weigh benefits? Or could Docker in the end prove to be good enough?
- matthewmacleod 12y agoThat's stupid. Developers want the ability to deploy applications easily, and keep them stateless. The tools to do that are of course available, and Docker builds on top of them to provide a much more effective interface than rolling an entire infrastructure from scratch each time. What the hell is wrong with that?
- gaius 12y agoNo, he has a point. Why are applications hard to deploy and manage? Because of how they are structured. If deployability was factored in at the time applications were being designed, they would look very different. You know there were entire 1000-page books written on how to deploy RoR applications? Why was it ever so complicated? Any why is creating a problem that never existed before, then solving it, considered a good use of anyone's time?
- matthewmacleod 12y agoIt is complex to deploy applications because applications are complex. They have dependencies, they require reproducible environments. We want them to be scalable, so we can easily fire up more instances as required. Hand-waving this away as a problem that "never existed before" is nonsense. And increase in individual machine power and the demands of applications means that we now have—quite validly—more complex applications, and more of them running on each machine. Administration of this is objectively difficult, and Docker is one of the tools that will help to make it easier.
- voidz 12y agoBut you are not addressing what I am saying at all. I am saying that this is convenient for developers, but for us sysadmins, who have to implement Docker apps in already existent systems, it is just not all that convenient, so now we have a surplus of happy developers.... and the sysadmin "should just stop being so grumpy". Sysadmins are expected to cheer in the same happy way, but in my opinion, many of us already knew how to build the kick ass systems /without/ containerization that the new developers ("devops"... yuch) are so cheery about.
- matthewmacleod 12y agoSysadmins are expected to cheer in the same happy way, but in my opinion, many of us already knew how to build the kick ass systems /without/ containerization that the new developers ("devops"... yuch) are so cheery about. I don't think this is the case. My goal as a developer is to be able to deploy applications quickly and easily, to be able to scale them, and to avoid worrying about dependencies. That's all good practice. I still need a sysadmin to handle that infrastructure, so Docker et. al. are not a tool to replace sysadmins. That being the case, why do you think there is pressure from developers to adopt these tools? If sysadmins are generally capable of building 'kick ass systems' that offer the same features but without using Docker, then why aren't developers happy with the situation? Docker is a tool that allows sysadmins to provide these useful features without having to arse about building them by hand. It's a tool for sysadmins, and dismissing it out-of-hand in the way you do is totally stupid.
- al2o3cr 12y ago"now it's just a matter of waiting" Keep waiting. It'll make it way easier to replace you with a small shell script.
- programminggeek 12y agoThe virtualization and containerization of computing is a long term net win, but there isn't a lot of huge benefits financially or otherwise for the scale most companies operate at. For example, I witnessed a co-worker spend days messing around with docker to host incredibly simple PHP/MySQL and Ruby apps. Instead of renting a few VM's on say Digital Ocean or Amazon and spending probably $50 a month, my co-worker spent at least 50-100 hours of time to put everything on Docker and Puppet. Let's say the net cost of that orchestration was around $10,000 in terms of billable time. You could rent a separate VM for every project and still come out ahead without trying very hard and still spend less time doing the project. The total cost on that was way out of whack AND docker continued to be a source of bugs and ongoing overhead costs in terms of time. My point is that these tools are great when they save you time, energy, and money, but a lot of people are overinvesting in tools like docker too early and they will never get a good ROI on their investment. I don't know at what scale these tools start to make a lot of sense, but I imagine it is somewhere over 20 or 30 machines or projects before containerization shows itself to be a good investment. I'd be curious to see someone run the numbers on that.
- jraedisch 12y agoComparing Docker and Puppet to VMs is not really fair. How do you configure them at scale? What about failures? That would need a lot more getting into cloud configuration/scripting. Having started with devops only recently, I find the concept of CoreOS + Docker Containers/Images/Dockerfiles (that are close enough to Bash scripting) easier to get into than learning custom UI/API of custom company to deploy to their cloud.
- IanCal 12y ago> How do you configure them at scale? That's not really a concern if you're deploying simple RoR or php + mysql apps, which is point of the post.
- ownagefool 12y agoBut DR is and removing variables in the environment is a worthwhile endevour for anything that's not fire and forget.
- DigitalJack 12y agoBare metal doesn't mean what it used to.
- gaius 12y agoYou know, Unix has a pretty good abstraction already for managing resources: a process. Nowadays it is fashionable to deploy applications consisting of hundreds of files in a complex structure, but this is fashion and not technology and that's easy to demonstrate: in the old days, a C application consisted of hundreds of files in a complex structure, that would compile into one self-contained executable. There's no technical reason you couldn't take a RoR app (for example) and "compile" it and manage it just like any other process. Start it, stop it, move it around, one binary executable and one plain text file for configuration, that's really all you need for any application. Really. I look at things like Docker and think, you are solving a completely artificial problem, and as soon as fashion swings the other way (10 years at most) people will wonder why people ever did this.
- vidarh 12y ago> You know, Unix has a pretty good abstraction already for managing resources: a process. And that's what Docker is built on: processes + namespaces to restrict what each process group can access. > I look at things like Docker and think, you are solving a completely artificial problem, and as soon as fashion swings the other way (10 years at most) people will wonder why people ever did this. Things like Docker will still have value with single-executable containers. Problems that people have had for years. Even with single-executables. You still need to manage privileges. You still need service discovery. You still need to manage the network. You still need to manage data volumes. You still need to manage the environment. Docker provides mechanisms that either solves all of that, or provides information for tools to hook into (e.g. ability to query what ports the currently running containers expose). I agree with you that there is distinct benefit in self-contained executables, and I think you'll find a lot of people working with Docker thinks the same. Partly this is part of what Docker gives us: We get to treat a bigger hairball of an environment pretty much like a single entity, even if we're not able to slim it down. But partly, note that a lot of the adoption of Go within devops tools appears to at least partially be motivated by the simplicity of distribution and installation from getting static binaries (without having to use C). I prefer Ruby, and find Go to be a ugly, too low level, language, but I definitively understand the appeal Go has when it comes to simplicity. Yet despite having those devops tools as single executables, people want to put them in containers to manage them properly. If anything, I hope and think that things will move even further down this route. For my part, I'm containerising my desktop environment part by part. There's no reason we should not move to far more locked down process environments.
- akerl_ 12y agoI'm not sure where folks decided there was a competition between containers and VMs. They solve very different needs. > If I’m a front-end app developer, it’s much more convenient for me to use a container-based cluster management solution on bare-metal without dealing with VMs. If you're spinning up containers on bare metal, you need to manage bare metal systems, or pay someone to do it for you. Or, you could put your containers in VMs, where you manage the VMs or pay somebody to do it for you. Bare metal gives you some advantages (like tighter control over the components and the ability to customize the hardware to suit up-front needs) and some disadvantages (harder to dynamically scale, spin up/down times are longer), and VMs have their own advantages and disadvantages. VMs are here to stay, just like dedicated servers are here to stay. Containers change what we do inside of our systems.
- bluedino 12y agoI think a lot of people would be surprised at how many users and traffic you can really handle on a single server, or single pair of servers (web/DB).
- chubot 12y agoWell yes, because a lot of hosting companies claim 100+ customer VMs per machine. Pretty sure Linode and Digital Ocean run somewhere in that neighborhood. So if you just run on a beefy bare metal server yourself, you can probably serve 50-100x as much traffic as you could on a typical VM. I guess the issue is that your software is probably not written to make use of the full machine. You might have to start 50 copies of a process, which might be OK. Ruby, node.js, and Python will probably neat that treatment.