Hey guys. Curious about how you run your automated tests.

I've playing a bit with openSLO in past few weeks. Really interesting stuff when applied to the development pipeline. I tought I'd share my perspective on this in a small blog post.

Hello,

TL:DR Atmospheric scientist with knowledge of cli, python want change to a SRE job

Let me explain my background, I am M.Sc in atmospheric science with a few publications in the field, during my studies I work most of my time working with cli tools so I am confident with shell and cli tools, pipelines, stdout, stderr, tmux, etc. I worked using numerical model that you need to compile, this teach me tools like makefiles, modules and cronjobs to did it operational. I have experience with python and other scientific languages like R, Matlab. During my free time took some course of docker. Even I set up a Nginx webpage that I leave to die for lack of time or setup a raspberry pi to download "linux isos" using docker.

I really enjoy the automation of process, and help other colleagues to setup and install the environment to work.

I know my lack of networking, monitoring, and I'm not sure if my self taught skills (science standards) are comparable with a CS worker.

I want to learn or get the certification needed to get a SRE job to mid 2024.

Any advice, course or certication to help me to get in the road?

Seems to be back up now, still waiting for information on the cause, so far have the vague reason "config change" from the GitLab issue linked

I use terraform fairly extensively in my role, and saw terraform cdk seems to be a nice extension to terraform. Unfortunately it’s convert feature hasn’t seemed to work for me and I’m hesitant to rewrite everything by hand.

Has anyone been using cdktf and enjoying it enough that could convince me to do that rewrite?

I'll start:

When I was first learning to use Docker, I didn't realize that most tutorials that include a database don't configure the database to persist. Imagine my surprise when I couldn't figure out why the database kept getting wiped!

No Idea if this will be a permanent coupon link, but figured I should share here.

source

I’ve only been getting alerts for GitHub statuses for a month or so now, but it feels like they have an incident like once a week. And it’s to the point where I am actually noticing when they go down at work and in my programming hobbies. Have they always been this rocky, is this a more recent thing, or is it just me?

Kubernetes is slowly making in-roads in the Gamedev world. This talk (not mine 🤣) introduces Agones and the benefits and challenges of running game Servers in Kubernetes.

Links to certain topics in video description

This year, JetBrains partnered with Google Cloud and DORA to put together the 2022 State of DevOps report. We are hosting a livestream to present the key takeaways and discuss how to achieve successful software delivery and operational performance.

In this livestream, we will:

Introduce the report, along with some highlights from the newly released Accelerate State of DevOps Report from Google Cloud. Discuss the operational performance practices currently employed by JetBrains.

cross-posted from: https://programming.dev/post/196935

To be clear, this isn't my project. Just cross-posting the author's post from [email protected] .

Sometimes unused class or function manages to slip into code base. Static code checkers like ruff, flake8 does not have rules for detecting such globally unused code.

I tried using vulture, but it has too many false positives to have it as part of CI/CD pipeline.

I have tried to implement my own, more reliable check for global deadcode detection.

Please let me know what you think about it.

Rolling Deployment

A rolling deployment strategy slowly replaces previous versions of an application with new versions by entirely switching out the environment in which the application is running. For example, containers running new versions of an application may take the place of containers running previous versions of an application....

Canary Deployment

To avoid risk, a canary deployment uses a phased approach in which traffic is shifted in increments. With the aid of a router or load balancer, new application code is released to a small group of users so it can be tested. Metrics measure the success of the new iteration....

Blue-Green Deployment

Blue-Green deployments eliminate downtime by running 2 identical production environments, one called Blue and the other called Green. Only one of the environments is live at any one time and handles all production traffic....

A/B Deployment

An A/B deployment strategy allows your company to test 2 versions of an application on users. The “A” version would be the old version, while the “B” version would contain a new or revised feature. Each version would be released to a subset of users for testing and feedback....

I don't know much about Bret's courses, but I do enjoy his podcast.

Topics cover anything DevOps, cloud management, sysadmin, Docker and container tools like Kubernetes and Swarm, and the full software lifecycle supply chain.