DEV Community: Hodard Hazwinayo

SRE vs DevOps vs Sys Admin vs Cloud engineer

Hodard Hazwinayo — Mon, 03 Oct 2022 17:11:11 +0000

What is SRE?

**
Site Reliability Engineering, or SRE, is an approach developed by Google in 2003 to continuously deploy new features while maintaining a high level of quality and availability of the infrastructure.

The SRE has become a full-fledged IT domain, whose objectives are to ensure that the platform is reliable and stable, ensure regular delivery of features and develop automated solutions for operational aspects. An SRE, according to Google's philosophy, is not allowed to do more than 50% of functional tasks. Like DevOps, this philosophy has led to the creation of a position, the Site Reliability Engineer. This SRE position is a continuation of the DevOps philosophy and is the "new DevOps."

What is DevOps?

**
DevOps is often seen as a way to apply agility to the production world. The agile method is used to reduce the distance between user needs and the development team. DevOps is the contraction of Devs and Ops because this methodology pushes Devs and Ops to collaborate to put new features into production faster. The notion of security is sometimes integrated to implement an approach called DevSecOps.

If DevOps is a philosophy, DevOps can be a job title (even if the term DevOps engineer is sometimes controversial). When we talk about a DevOps engineer, we are talking about a person who reconciles the stability of the platform and the approach of putting developers in the best conditions to produce quality features quickly. Their tasks range from automating processes to helping resolve bugs and optimizing platform monitoring.

How to choose between SRE and DevOps for your company?

**
Originally, SRE and DevOps were concepts, a way of working.

Today, these terms have become the name of the people working with this philosophy. You don't have to choose between these two profiles to recruit your internal Ops. SRE is a way to accomplish the DevOps philosophy and implement it, with specific standards and metrics defined by Google. But both SRE and DevOps remove organizational barriers to deliver faster while ensuring platform stability.

On the contrary, if you want to implement the Google SRE standards in your company, recruiting and training DevOps people should not be a problem because they will already share the concepts.
This topic is developed in depth by Google in this video.

What is a SysAdmin compared to DevOps and SRE?

**
The prominent role of the SysAdmin (or computer systems administrator) is to ensure the proper functioning of the computer servers of an entity or a system. The missions entrusted to him vary according to the size of the company: optimization of system resources, availability of servers, management of backups, resolution of problems and security breaches, maintenance…

The term SysAdmin defines system administrators when servers are still mainly physical. The transformation of IT and networks with the evolution of the possibilities offered by the technical environment (especially Cloud) has radically transformed the role and functions of the SysAdmin. Some Sysadmins have embarked on a DevOps approach. If the job of DevOps engineer has been widely developed, Sysadmin remains a widespread function, especially in companies that have barriers to move to the Cloud.

Finally, the objective of DevOps is to ensure collaboration between each part of an IT company (Devs and Ops). A SysAdmin, on the other hand, is more focused on the configuration and maintenance of servers and computer systems.

What is a Cloud engineer?

**
Cloud Computing is a data storage service accessible via the Internet. The Cloud engineer is in charge of deploying, storing, and managing data on servers located outside the company in data centers. He is a specialist in cloud technologies and services offered by the major cloud providers. He can be specialized in one of the big public clouds (AWS, GCP) and have several experiences with different providers. They generally master the concepts of containerization, automation, and CI/CD, allowing them to support developers and implement a DevOps approach in the company.

SRE, DevOps, and Cloud engineers are today several names that refer to the same concepts. Automation, collaboration with developers, and mastery of cloud tools. Even in companies where DevOps are called "SRE," we find more a DevOps role with a different terminology than an actual application of the Google methodology. On the other hand, the position, culture, and technologies of a SysAdmin are very different from those of these "new generation" Ops. When recruiting, it is this distinction that you need to pay attention to in order to ensure that the person you are recruiting has the culture of the role to which you are going to assign them.

Git Cheat Sheet – 50 Git Commands You Should Know

Hodard Hazwinayo — Tue, 30 Aug 2022 14:26:46 +0000

Git is a distributed version control system that helps developers collaborate on projects of any scale.

Linus Torvalds, the developer of the Linux kernel, created Git in 2005 to help control the Linux kernel's development.

What is a Distributed Version Control System?

A distributed version control system is a system that helps you keep track of changes you've made to files in your project.

This change history lives on your local machine and lets you revert to a previous version of your project with ease in case something goes wrong.

Git makes collaboration easy. Everyone on the team can keep a full backup of the repositories they're working on on their local machine. Then, thanks to an external server like BitBucket, GitHub or GitLab, they can safely store the repository in a single place.

This way, different members of the team can copy it locally and everyone has a clear overview of all changes made by the whole team.

Git has many different commands you can use. And I've found that these fifty are the ones I use the most often (and are therefore the most helpful to remember).

So I have written them down and thought it'd be nice to share them with the community. I hope you find them useful – Enjoy.

How to check your Git configuration:

The command below returns a list of information about your git configuration including user name and email:

git config -l

How to setup your Git username:
With the command below you can configure your user name:

git config --global user.name "Fabio"
How to setup your Git user email:
This command lets you setup the user email address you'll use in your commits.

git config --global user.email "hodardhazwinayo@test.com"

How to cache your login credentials in Git:

You can store login credentials in the cache so you don't have to type them in each time. Just use this command:

git config --global credential.helper cache

How to initialize a Git repo:

Everything starts from here. The first step is to initialize a new Git repo locally in your project root. You can do so with the command below:

git init

How to add a file to the staging area in Git:

The command below will add a file to the staging area. Just replace filename_here with the name of the file you want to add to the staging area.

git add filename_here

How to add all files in the staging area in Git

If you want to add all files in your project to the staging area, you can use a wildcard . and every file will be added for you.

git add .

How to add only certain files to the staging area in Git

With the asterisk in the command below, you can add all files starting with 'fil' in the staging area.

git add fil*

How to check a repository's status in Git:

This command will show the status of the current repository including staged, unstaged, and untracked files.

git status

How to commit changes in the editor in Git:

This command will open a text editor in the terminal where you can write a full commit message.

A commit message is made up of a short summary of changes, an empty line, and a full description of the changes after it.

git commit

How to commit changes with a message in Git:

You can add a commit message without opening the editor. This command lets you only specify a short summary for your commit message.

git commit -m "your commit message here"

How to commit changes (and skip the staging area) in Git:

You can add and commit tracked files with a single command by using the -a and -m options.

git commit -a -m"your commit message here"

How to see your commit history in Git:

This command shows the commit history for the current repository:

git log

How to see your commit history including changes in Git:

This command shows the commit's history including all files and their changes:

git log -p

How to see a specific commit in Git:

This command shows a specific commit.

Replace commit-id with the id of the commit that you find in the commit log after the word commit.

git show commit-id

How to see log stats in Git:

This command will cause the Git log to show some statistics about the changes in each commit, including line(s) changed and file names.

git log --stat

How to see changes made before committing them using "diff" in Git:

You can pass a file as a parameter to only see changes on a specific file.
git diff shows only unstaged changes by default.

We can call diff with the --staged flag to see any staged changes.

git diff
git diff all_checks.py
git diff --staged

How to see changes using "git add -p":

This command opens a prompt and asks if you want to stage changes or not, and includes other options.

git add -p

How to remove tracked files from the current working tree in Git:

This command expects a commit message to explain why the file was deleted.

git rm filename

How to rename files in Git:

This command stages the changes, then it expects a commit message.

git mv oldfile newfile

How to ignore files in Git:

Create a .gitignore file and commit it.

How to revert unstaged changes in Git:

git checkout filename

How to revert staged changes in Git:

You can use the -p option flag to specify the changes you want to reset.

git reset HEAD filename
git reset HEAD -p

How to amend the most recent commit in Git:

git commit --amend allows you to modify and add changes to the most recent commit.

git commit --amend

!!Note!!: fixing up a local commit with amend is great and you can push it to a shared repository after you've fixed it. But you should avoid amending commits that have already been made public.

How to rollback the last commit in Git:

git revert will create a new commit that is the opposite of everything in the given commit.
We can revert the latest commit by using the head alias like this:

git revert HEAD

How to rollback an old commit in Git:

You can revert an old commit using its commit id. This opens the editor so you can add a commit message.

git revert comit_id_here

How to create a new branch in Git:

By default, you have one branch, the main branch. With this command, you can create a new branch. Git won't switch to it automatically – you will need to do it manually with the next command.

git branch branch_name

How to switch to a newly created branch in Git:

When you want to use a different or a newly created branch you can use this command:

git checkout branch_name

How to list branches in Git:

You can view all created branches using the git branch command. It will show a list of all branches and mark the current branch with an asterisk and highlight it in green.

git branch

How to create a branch in Git and switch to it immediately:

In a single command, you can create and switch to a new branch right away.

git checkout -b branch_name

How to delete a branch in Git:

When you are done working with a branch and have merged it, you can delete it using the command below:

git branch -d branch_name

How to merge two branches in Git:

To merge the history of the branch you are currently in with the branch_name, you will need to use the command below:

git merge branch_name

How to show the commit log as a graph in Git:

We can use --graph to get the commit log to show as a graph. Also,
--oneline will limit commit messages to a single line.

git log --graph --oneline

How to show the commit log as a graph of all branches in Git:

Does the same as the command above, but for all branches.

git log --graph --oneline --all

How to abort a conflicting merge in Git:

If you want to throw a merge away and start over, you can run the following command:

git merge --abort

How to add a remote repository in Git

This command adds a remote repository to your local repository (just replace https://repo_here with your remote repo URL).

git add remote https://repo_here

How to see remote URLs in Git:

You can see all remote repositories for your local repository with this command:

git remote -v

How to get more info about a remote repo in Git:

Just replace origin with the name of the remote obtained by
running the git remote -v command.

git remote show origin

How to push changes to a remote repo in Git:

When all your work is ready to be saved on a remote repository, you can push all changes using the command below:

git push

How to pull changes from a remote repo in Git:

If other team members are working on your repository, you can retrieve the latest changes made to the remote repository with the command below:

git pull

How to check remote branches that Git is tracking:

This command shows the name of all remote branches that Git is tracking for the current repository:

git branch -r

How to fetch remote repo changes in Git:

This command will download the changes from a remote repo but will not perform a merge on your local branch (as git pull does that instead).

git fetch

How to check the current commits log of a remote repo in Git
Commit after commit, Git builds up a log. You can find out the remote repository log by using this command:

git log origin/main

How to merge a remote repo with your local repo in Git:

If the remote repository has changes you want to merge with your local, then this command will do that for you:

git merge origin/main

How to get the contents of remote branches in Git without automatically merging:

This lets you update the remote without merging any content into the
local branches. You can call git merge or git checkout to do the merge.

git remote update

How to push a new branch to a remote repo in Git:

If you want to push a branch to a remote repository you can use the command below. Just remember to add -u to create the branch upstream:

git push -u origin branch_name

How to remove a remote branch in Git:

If you no longer need a remote branch you can remove it using the command below:

git push --delete origin branch_name_here

How to use Git rebase:

You can transfer completed work from one branch to another using git rebase.

git rebase branch_name_here

Git Rebase can get really messy if you don't do it properly. Before using this command I suggest that you re-read the official documentation here

How to run rebase interactively in Git:

You can run git rebase interactively using the -i flag.
It will open the editor and present a set of commands you can use.

git rebase -i master

# p, pick = use commit
# r, reword = use commit, but edit the commit message
# e, edit = use commit, but stop for amending
# s, squash = use commit, but meld into previous commit
# f, fixup = like "squash", but discard this commit's log message
# x, exec = run command (the rest of the line) using shell
# d, drop = remove commit

How to force a push request in Git:
This command will force a push request. This is usually fine for pull request branches because nobody else should have cloned them.
But this isn't something that you want to do with public repos.

git push -f

Conclusion

These commands can dramatically improve your productivity in Git. You don't have to remember them all – that's why I have written this cheat sheet.

Thanks for reading! By the way, I am Hodard Hazwinayo, Senior Infrastructure Engineer and Senior DevOps Engineer in IT automation with Python & Bash Script.

Follow me Here