oshien – Best DevOps

Final post test – answer – oshien

oshien — Sat, 18 Jun 2022 09:55:37 +0000

What is SRE? – 3-4 Lines
A – SRE are those who have major focus on monitoring the system stability,
tracking the issue/bugs through various tools and fixing them.
Creating new systems and automating the development procedures along with other teams.
SRE mainly try to build a system with least downtime possible.
5 Action items to perform to transform from Ops to SRE
A – Work with development teams to build systems/processes
Automate development process
Drive SLO from the system observability
Enhance monitoring to better maintain systems
Establish processes that help in better incident management
Top 10 SRE tools to be implemented
A – Datadog, Kubernetes, Ansible, Terraform, ELK, Nginx, jira, AWS, Docker, jenkins

Day1 – Post test – answer – oshien

oshien — Thu, 16 Jun 2022 07:40:14 +0000

Define SRE in your own Words- 2 Lines
A – SRE are the ones who involve themselves in every possible aspect of product/service development. They not only do the operations to maintain the stability of the system but work on engineering as well to improve the system performance.
Define 3-4 bullets points on migrating process of Ops to SRE?
A – Invove in development along with operations
Setup engineer tasks for the operations
Try to reduce toil.
Try automation to enable faster development
3 Charactertics to identify Toil in SRE
A – repetative
Not adding to any enhancement
Can be automated
1 line explanation of SLI – SLO and SLA
A – In terms of a metric that is critical for the system stability.
SLI – The actual metric value that the system currently provides
SLO – THe metric value that we try to adhere in order to maintain system stability within organization
SLA – The metric value which client has agreed to and cannot be violated.

Pre-test Solved (oshien)

oshien — Thu, 16 Jun 2022 04:06:04 +0000

Q1 – What are the differences between SRE and DevOps?
A – SRE and devops have similar work profile. Devops are more on developing new tech/systems whereas SRE are more concentrated on the system availability.

Q2 – What SRE team is responsible for?
A – Making sure the end user is not affected with any of the service not available.

Q3 – What is an error budget?
A – Note sure, may be its how much a service downtime can be allowed.

Q4 – What are MTTF (mean time to failure) and MTTR (mean time to repair)? What these metrics help us to evaluate?
A – MTTF – How long it took for system(process) to fail
MTTR – How long it took for system(process) to repair
long running process, CPU usage.

Q5 – What is the role of monitoring in SRE?
A – Very important role as SRE need to be alerted for any issues in the running infra before any one else. SO monitoring has to be very accurate to catch any such situation.

Q6 – How do you differentiate between process and thread?
A – Process is combination of many threads. One thread is one task that is to be performed, combined forms a process.

Q7 – What activity means Reducing Toil?
A – It means to make sure the fault notifications should report to the correct team instead of any other team which then assign it to correct team.

Q8 – Have you ever heard of SLO? If yes then explain.
A – service level objectives, it is basically particular application agreement for its uptime/response time.

Q9 – Enlist all the Linux signals you are aware of
A – SIGKILL – kill signal
SIGTERM – Termination signal

Q10 – What is obserbability
A – It means to understand the working of a system from the output that is generated through monitoring or any other medium.