News for hackers. Stuff that matters.
Re:The future of Kubernetes is virtual machines by mcguire on Wednesday December 26, 2018 @10:20PM (#18766988)
As someone who has been a sysadmin and system programmer for 25 years and a crusty rat bastard for almost that long, I have to wonder how long it is going to be until someone realizes that a piece of hardware doing a task is more efficient than 27 layers of virtual machines and a long pair of tongs.
Re:The future of Kubernetes is virtual machines by dilyevsky on Thursday December 27, 2018 @03:48AM (#18768346)
Your definition of efficiency is too simplistic. In many cases it’s more “efficient” to have rapid development cycle and low ops overhead than save a few bucks on hardware.

Even if we accept that server cost is key, Google realized long time ago that they can squeeze more out of their fleet if they can overcommit it because many workloads have variable utilization over time. Hence “containers” were conceived.

Re:The future of Kubernetes is virtual machines by caymanjim on Thursday December 27, 2018 @04:22AM (#18768479)
Very much this. People time is always the biggest cost. Docker and Kubernetes have been a game changer in time-to-production. Unless you need maximum performance out of the biggest iron available, it's cheaper to buy the next tier of EC2 instance than to waste developer and operations staff time trying to squeeze more out of existing servers. There are many levels of abstraction, but...who cares? It's about productivity per dollar.
Re:The future of Kubernetes is virtual machines by rbanffy on Thursday December 27, 2018 @10:27AM (#18769944)
> People time is always the biggest cost

It really depends on scale. If I spend 15 minutes improving the utilization of my home cluster by 10%, the only payoff I get is experience. If I do the same to Google's indexing infrastructure, I probably delayed the collapse of civilization by global warming by a full year.

This attitude leaves a lot of low-hanging fruit that, as the operation grows, can shave a couple million dollars off the operating costs.

Re:The future of Kubernetes is virtual machines by otabdeveloper1 on Thursday December 27, 2018 @05:07AM (#18768637)
> People time is always the biggest cost.

False.

> Docker and Kubernetes have been a game changer in time-to-production.

False.

> ...it's cheaper to buy the next tier of EC2 instance than to waste developer and operations staff time trying to squeeze more out of existing servers.

Only if your management is completely clueless. You can't solve people problems by buying machines or installing containers.

> It's about productivity per dollar.

No. Or, rather, only if by "productivity" you mean "clueless management KPI, meaning wasted company dollars per hour".

The root problem is higher-up management being unable to any set useful goals except "let's get investment capital and waste it ASAP to get more investment capital next year, growth, #yolo lol".

Re:The future of Kubernetes is virtual machines by sascha_sl on Thursday December 27, 2018 @07:03AM (#18768991)
how can you say these are false when they're quite evidently true in some circumstances?

I'm on a team that provides a kubernetes-based internal SaaS thing and personnel costs seem to be easily recouped by the money we save from having autoscaling and a common node pool instead of 2 machines per service.

This has been going on for a number of years now and the most important part has always been to be backwards compatible with whatever developers have been doing for those years. That is productivity.

That's not to mention the leverage Kubernetes gives you to optimize and discover costs. Being able to see where optimization yields the best results is much better than optimizing everything. Sometimes it just isn't worth it.

Re:The future of Kubernetes is virtual machines by clagio on Wednesday December 26, 2018 @11:09PM (#18767231)
I agree with you, being in the same position. I wonder if the DevOps trend started because of the constant friction between devs and ops. While devs main concern and job is to deliver new features, ops main concern and job is to keep things stable. These different goals caused ops to be seen as an obstacle to dev job. Being the devs close to the business was easy to predict that we would be taken out or at least required to change. I think, we (ops) are mainly the one to blame for the current situation and now we can only adapt or die.
Re:The future of Kubernetes is virtual machines by de_watcher on Thursday December 27, 2018 @05:43AM (#18768753)
It has become manageable to do both for one person.
Re:The future of Kubernetes is virtual machines by kacbskjbc on Thursday December 27, 2018 @07:01AM (#18768981)
Unfortunately, it's only really possible when you stand on the shoulders of massive companies like Amazon and Google, at which point you're not really doing "dev" and "ops", you're just doing "dev" and outsourcing "ops" to a big company that'll only do half the work for you.
Re:The future of Kubernetes is virtual machines by romeisendcoming on Thursday December 27, 2018 @08:20AM (#18769260)
Using recipes, pre-built images, automation, and mostly opaque system controllers that abstract away all the underlying detail. That isn't a reliable/secure system and only salesmen and those who have a stake in that model push it. Unfortunately this is the new normal, fait accompli.
Re:The future of Kubernetes is virtual machines by Bombthecat on Thursday December 27, 2018 @11:53AM (#18770628)
But not allowed in many many organizations and firms.

Governance and security forbid people to be op and dev in one person.

Or God forbid: control the dev, pre stage and production environment.

Re:The future of Kubernetes is virtual machines by tlrobinson on Wednesday December 26, 2018 @11:03PM (#18767203)
Or maybe raw performance isn’t always the most important attribute of a system?
Re:The future of Kubernetes is virtual machines by clagio on Wednesday December 26, 2018 @11:15PM (#18767260)
Not directly, but cost usually it is. Being able to serve the same number of customers with less computational power means reducing your cost.
Re:The future of Kubernetes is virtual machines by pbalau on Thursday December 27, 2018 @02:48AM (#18768123)
That's a very simplistic view on the issue.

Most businesses do not have a constant workload 24/7, which means the ability to scale up and down will save more money than reducing the overhead of not running directly on metal.

There is also the cost of having to care about hardware to begin with.

Also, in the big picture, having 100 companies doing their own bare metal deployments is not terrible efficient, compared to 1 company doing that and 99 paying the first company for this service.

The list could go on, but I think you get my point.

Re:The future of Kubernetes is virtual machines by romeisendcoming on Thursday December 27, 2018 @08:32AM (#18769302)
This sounds like classic devops/cloud snake oil. I wonder what industry pays your bills?

* The most businesses/always on reasoning appeals to executive decision makers and rolls down hill to the technical people who are best educated to make the decision. Many people who believe that you can cut cost by sizing workloads end up racing their own models when it doesn't scale financially or computationally over time.

* What is so difficult about hardware? The cost of forgetting how to deal with it will be much higher in the long run.

* Yes, monopolies are healthy.

Re:The future of Kubernetes is virtual machines by pbalau on Thursday December 27, 2018 @11:05AM (#18770265)
> Yes, monopolies are healthy.

Seems all 3 major cloud providers, aws, google and azure, are providing facilities to run docker containers. Seems Digital Ocean is getting there too. Hardly a monopoly, init?

> What is so difficult about hardware?

All of it. This is knowledge my company doesn't have and there is no point in investing in accuiring this knowledge at this time, since we have an easier solution. Not to mention that if we decide going bare metal is the way to go, we can do that later.

> The most businesses [...]

I think my english is failing me, I don't really understand this paragraph.

> This sounds like classic devops/cloud snake oil. I wonder what industry pays your bills?

Not the snarky remarks industry...

Re:The future of Kubernetes is virtual machines by barrkel on Thursday December 27, 2018 @08:57AM (#18769443)
The biggest cost for growth companies is opportunity cost: what they aren't able to sell and deliver because of constraints in their development and operational setup.

If you have customers beating down your door to buy your product after you add n+1 feature, you can find investors to eat the extra operational cost without a problem as long as you can build n+1 fast enough that those customers don't go elsewhere.

The other element is elastic workload, of course. Having the application dynamically scale across a pool of machines in as tractable a manner as possible at the developer level can be an enormous cost saving all on its own. Instead of allocating machines based on individual high water marks, you can allocate a cluster based on the sum of average usage + as many standard deviations of resource usage to get as many 9s as you need.

Re:The future of Kubernetes is virtual machines by sigi45 on Thursday December 27, 2018 @10:00AM (#18769764)
10 Years ago when i needed a machine for anything, i had to create a ticket, wait a week or so to get what? One machine.

Than i got told, that they have to control it, otherwise backup and restore is not supported and on the other hand, they were only able to install stuff like svn by spending virtual 3 project days! 3! I never asked what it would cost to install some etherpad.

Two years ago in a startup, i logged into aws, clicked around for an hour and had 2 isolated networks, 4 instances, a load balancer, dns server, snapshot and backup configured. A few mouseclicks later i could have had an autoscaler as well.

Ops / own Hardware is a means to an end.

Re:The future of Kubernetes is virtual machines by barrkel on Thursday December 27, 2018 @08:55AM (#18769436)
I want to be in a world where allocating hardware is as simple (at the API level) as allocating a block of memory or creating a thread. Kubernetes is a means to that end, and with an API that isn't tied to a specific vendor.

The efficiency of the actual code executing on the hardware is secondary to the efficiency of being able to automate allocation of hardware at the application level.

Re:The future of Kubernetes is virtual machines by stubish on Thursday December 27, 2018 @02:30AM (#18768057)
This is why things like MAAS exist, which is a 'cloud provider' that lets you provision bare metal machines. Plug in a new rack of servers, let them netboot, and let the clients spin up a machine matching their requirements in the same way they would spin up an AWS or Azure instance.

We mix bare metal spun up this way with Open Stack VMs, depending on the requirements. And slice up into containers using LXD when that makes sense.

Re:The future of Kubernetes is virtual machines by shaklee3 on Thursday December 27, 2018 @01:11AM (#18767748)
That's kind of the point of k8s. Are you saying containers have too much overhead?
Re:The future of Kubernetes is virtual machines by akvadrako on Thursday December 27, 2018 @08:37AM (#18769329)
I don't think he knows what he's saying. At a small scale you have overhead because you need to run the orchestration software.

But everything else (disk, CPU, network) typically amounts to less than 1%.

Re:The future of Kubernetes is virtual machines by nimbius on Wednesday December 26, 2018 @10:37PM (#18767072)
amen. At first i figured containers were a good way to run code with difficult dependencies and weird operating environments, but that still doesnt make sense.

- systemd and uwsgi for example play well when run as a single user per wsgi application under a single nginx/lb.

- php-fpm already handles a ton of overhead from php apps.

- ansible deployments called from gitlab-ci can roll out apps just as well as deploying from the registry.

then i figured maybe they were on to something with the autoscaling thing...but that seems like a meaningless feature. Every good project already has metrics and forecasting...it would be absurd to think a final product like imgur.com or twitter does not know (down to the byte) how much storage theyll need in 4 months and the potential drivers.

auto-scaling infrastructure just betrays the fact that most developers throw resources at load problems instead of waiting for ops to figure out the actual issue.

Re:The future of Kubernetes is virtual machines by latchkey on Wednesday December 26, 2018 @11:13PM (#18767251)
I helped build an e-commerce marketplace, which is essentially a shopping cart system that was used by third parties. We had no idea how to predict traffic loads because we had no idea when one of our customers would run a successful campaign. Autoscaling on google appengine was a lifesaver for us. Our very small dev team focused on building features because we had zero devops and we didn't have to carry a pager.
Re:The future of Kubernetes is virtual machines by rhinoceraptor on Thursday December 27, 2018 @03:44PM (#18772492)
I don't think most developers or admins really have the toolset/skills to debug to root cause. Most people see debugging as the process of making problems go away, not as the science of understanding a problem.

You need both developer and admin skills, as well as a pretty good understanding of the whole stack - the application, the framework/libraries, the application runtime/support libraries, the database, the kernel and the network.

Re:The future of Kubernetes is virtual machines by halbritt on Wednesday December 26, 2018 @11:37PM (#18767347)
Never.