91–100 of 248 posts
Earlier quoted context omitted.
Yes, it's a real issue. Kubernetes burns too much RAM and CPU even with no workload.
Docker on macOS also suffers from that issue though.
Earlier quoted context omitted.
> systemd sucks balls No it doesn't. Shell scripts in your init system sucks balls. Systemd is great.
I am in favor of a new discussion about existential philosophical differences again. Almost missed the systemd drama. I use systemd on pretty much any linux machine but am very sympathetic to the arguments of its detractors, which to a significant degree results from the behavior of its proponents and the inability to see that you actually do loose flexibility in theory. You could argue taht GNU/linux could be called…
But they did not. Functionally, systemd is great. I don't like the architecture, for its monolithic non unix characteristics. I begrudgingly started to use it when Debian switched to systemd. After some time, I must admit it is leaps and bounds better than sysv init, and better than the alternatives that appeared before it.
Can anyone offer a good guide to DevOps for people who don't directly use these tools but work with engineers who do and would like to learn more? The whole ecosystem of servers, cloud infrastructure (and all of the different offerings there), Docker, Kubernetes, CICD tools etc is a bit overwhelming to get into.
Docker shit so hard on the established linux community with such arrogance Jessie Frazelle, a Docker employee at the time, would gloat about closing systemd-specific PRs. She wore a name tag @ DockerCon.EU 2015 proudly showing "I say no to systemd specific PRs". Docker's plight? Good riddance.
To be fair, arrogance seems to be quite popular in systemd as well
Can anyone offer a good guide to DevOps for people who don't directly use these tools but work with engineers who do and would like to learn more? The whole ecosystem of servers, cloud infrastructure (and all of the different offerings there), Docker, Kubernetes, CICD tools etc is a bit overwhelming to get into.
DevOps is two things:
1. Applying the methods of modern software development (version control, automation, DSLs...) to operations (provisioning, config, deployment, monitoring, backups...).
2. Reducing silo barriers between devs and ops groups so that everyone is working together as a team, rather than blaming each other for poor communication and the resulting messes.
Then there are all the DevOps hijacking attempts, such as equating it to Agile or Scrum or XP, or insisting that it's a way to stop paying for expensive operations experts by making devs do it, or a way to stop paying for expensive devs by making ops do it, or a way to stop paying for expensive hardware by paying Amazon/Google/$CLOUD to do it.
No matter what your software-as-a-service company actually does, it will need to execute certain things:
- have computers to run software
- have computers to develop software
- have computers to run infrastructure support
You can outsource various aspects of these things to different degrees. Anywhere you need computers, you have a choice of buying computers (and figuring out where to put them and how to run them and maintain them), or leasing computers (just a financing distinction), or renting existing computers (dedicated machines at a datacenter) or renting time on someone else's infrastructure. If you rent time, you can do so via virtual machines (which pretend to be whole servers) or containers (which pretend to be application deployments) or "serverless", which is actually a small auto-scaled container.
Docker is a management scheme for containers. VMWare provides management schemes for virtual machines. Kubernetes is an extensive management scheme for virtual machines or containers.
A continuous integration tool is, essentially, a program that notes that you have committed changes to your version control system and tries to build the resulting program. A continuous deployment system takes the CI's program and tries to put it into production (or, if you're sensible, into a QA deployment first).
This article seems to be arguing that Docker’s primary downfall was being hostile to its open source community. Without having an opinion on whether that’s true, I suspect the core issue was not that but their business model and execution. Before Kubernetes was the dominant container tech, they were pushing Swarm but I remember being confused about where Docker “standalone” stopped and where Swarm began. Perhaps it w…
I fail to see how an alleged threat of universal cloud platform compatibility was neutralized by commoditizing the services you mentioned.
The problem i have with cubernetes is the following: I as a small developer and small server owner don't have the ressources to even get started. The first thing i see at cubernetes is a cluster. Why a cluster. Do i need to cluster my Raspberry pi's to get something out of it? Do i need to buy 3 servers just to run 5 containers? In docker its easy. Download Docker. Start container. Install container manager like plat…
> as a small developer Do you need kubernetes? I know the hype cycle is mad for copying big tech, but if stackoverflow can operate on a couple of IIS instances I’d argue that you almost never need kubernetes.
Ten years ago you started with PHP + memcache + MySQL running on just a physical box running linux. No Docker or Kubernetes. No virtual machine for what it is worth. Then you split it in multiple PHP frontends with a load balancer or MySQL master and slaves as the traffic demanded it.
I think a lot of systems these days are over-engineered and over-paid from day one. It may cost you 10-20 times what you would if you keep the "old day" approach.
That said Docker and Kubernetes are nice. They give you a lot of flexibility. But the most important part, I think, has been that they consolidated the shift from "pet" to "cattle" servers that simplifies a lot the sysOp and sysAdm work.
Can anyone offer a good guide to DevOps for people who don't directly use these tools but work with engineers who do and would like to learn more? The whole ecosystem of servers, cloud infrastructure (and all of the different offerings there), Docker, Kubernetes, CICD tools etc is a bit overwhelming to get into.
Try focusing on "what do I want?", get a superficial understanding on how the tool works, then try to apply that knowledge to your search engine query.
For example: Say you know that docker has images and containers. That means it is somehow going to install an operating system into your operating system and make an image. Then you will copy your program into that image. Then you will start a container (an instance) based on that image. And this is basically all you need to know about docker to start searching for how to do things. Like "how to build a docker image?" or "how to start a docker container?".
Another example. You know that Integration Testing means running your servers and running tests against them as if they are in actual production and continuous integration is a service that runs your integration tests everytime someone merges a branch to a monitored branch in a version control system. From here on, you are able to look up how to set a monitored branch, how to create a build machine and how to scale it.
Earlier quoted context omitted.
>> I as a small developer and small server owner... You'll never ever need either Docker or Kubernetes or even the latest and greatest javascript frameworks. I started running a server before I knew anything and that server is still purring along happily. But if you're ever targeting an enterprise, either as a freelancer or as an employee, those words are invaluable in your resume. It of course helps if you actually…
> You'll never ever need either Docker or Kubernetes or even the latest and greatest javascript frameworks. I agree with "no need for k8s and the latest JS frameworks", but strongly disagree on not needing Docker. It is extremely useful for setting up separate development instances for your projects - no matter if you're doing PHP development with N different versions of PHP (as some sites may still be stuck at 5.6 w…