Sysadmins for sysadmins
Automatically setup a VPN on your own virtual server

Seems like sound principles and suggestions

More Memory, More Problems
The single Postgres setting that almost took down our database

About Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at:

New talk: Learning DNS in 10 years
By Julia Evans. Nice walkthrough on learning and troubleshooting, using DNS as example.

Even if you are not using AWS - there is a ton of info to learn from.

Load Balancing
Excellent article on http load balancing by [](

Five Koans of Software Architecture
Some food for thinking

Something to think about

Master the Art of Caching for System Design Interviews: A Complete Guide
Good article on understanding caching

On OpenAI’s Kubernetes Cluster
Interesting observations on how OpenAI uses Kubernetes

DevOps in Shorts
Atsibodo virtualios IT konferencijos? Mums taip pat. Todėl jau ši balandį norime Tave pakviesti į jau antrą kartą vyksiantį DevOps forumą "DevOps in Shorts".

Interesting info on how Uber operates it's infrastructure.

There is no such system that will not fail, so the question - how? Talks about failure domains, fault isolation and testing it (using chaos engineering)

Low Latency: The High-Speed Adventure in Distributed Systems
How to think about these systems

Actually quite good insights

Foundational DevOps Patterns
cross-posted from [!]( > Adopting DevOps practices is nowadays a recurring task in the industry. DevOps is a set of practices intended to reduce the friction between the software development (Dev) and the IT operations (Ops), resulting in higher quality software and a shorter development lifecycle. Even though many resources are talking about DevOps practices, they are often inconsistent with each other on the best DevOps practices. Furthermore, they lack the needed detail and structure for beginners to the DevOps field to quickly understand them. > > In order to tackle this issue, this paper proposes **four foundational DevOps patterns: Version Control Everything, Continuous Integration, Deployment Automation, and Monitoring**. The patterns are both detailed enough and structured to be easily reused by practitioners and flexible enough to accommodate different needs and quirks that might arise from their actual usage context. Furthermore, the **patterns are tuned to the DevOps principle of Continuous Improvement by containing metrics so that practitioners can improve their pattern implementations**. --- The article does not describes but actually identified and included 2 other patterns in addition to the four above (so actually 6): - **Cloud Infrastructure**, which includes cloud computing, scaling, infrastructure as a code, ... - **Pipeline**, "important for implementing Deployment Automation and Continuous Integration, and segregating it from the others allows us to make the solutions of these patterns easier to use, namely in contexts where a pipeline does not need to be present." ![Overview of the pattern candidates and their relation]( The paper is interesting for the following structure in describing the patterns: > - Name: An evocative name for the pattern. > - Context: Contains the context for the pattern providing a background for the problem. > - Problem: A question representing the problem that the pattern intends to solve. > - Forces: A list of forces that the solution must balance out. > - Solution: A detailed description of the solution for our pattern’s problem. > - Consequences: The implications, advantages and trade-offs caused by using the pattern. > - Related Patterns: Patterns which are connected somehow to the one being described. > - Metrics: A set of metrics to measure the effectiveness of the pattern’s solution implementation.

Some Terraform practices

I remember when reverse tunnel was a security issue - now it is widely used!

Production postmortem: The heisenbug server
Tracing back to the root

reliability capabilities in gcp

Simple intro into port scanning and a little bit on detection

So... the house of cards is starting to fall? Such and similar events always remind me two readings: [How complex systems fail]( and [Why Do Computers Stop and What Can Be Done About It?]( can this be prevented? I don't think so, but what could be done? Check this book - [Antifragile](

HELP! I am in an awkward situation: after unsuccessful attempt to mount new disks to my Yunohost, I got the above on the server (old laptop) screen. OF COURSE I have the password, saved in my KeePass. The problem is, there are characters there I do not know how to enter, like **ô¼Î** etc. Hints welcome.

If you want to dig deeper into sysadmin's area - this is a good article.

Some advice on preparing and passing the audit

Nice write-up on estimates

Wrong things at the wrong time

Diagram as Code tools are always interesting to me.

Question if one should run DB on K8s pops-up sometimes, here is a list of some options if you decide to do it. Have you tried any of it?

Taking a look into chaos engineering, rather old, but good one.

All the best engineering advice I stole from non-technical people
Not a recycled “truths”, but some interesting advice.

Sysadmins for sysadmins
    Create a post

    Kažkas turi tai padaryti / Somebody has to do it

    Fotkė camilo jimenez Unsplash

    • 0 users online
    • 1 user / day
    • 2 users / week
    • 3 users / month
    • 7 users / 6 months
    • 36 subscribers
    • 110 Posts
    • Modlog