Skip to content

Create learning-plan.md #753

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sneha-Sah-22-23 wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Create learning-plan.md #753

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6b3ea01
Create learning-plan.md
Sneha-Sah-22-23 Aug 5, 2026
d99f07c
Create linux-architecture-notes.md
Sneha-Sah-22-23 Aug 6, 2026
87d60d6
Update linux-architecture-notes.md
Sneha-Sah-22-23 Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions 2026/day-01/learning-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# 90-Day DevOps Learning Plan

## Current Level
- Student, Final year B.Tech CSE
- Intermediate Level

## Why DevOps & Cloud
- DevOps is the bridge between Development and Operations.
- DevOps is about Automation instead of doing tasks manually.
- Cloud is delivery of on-demand Computing power, database storage, networking via aws, azure etc.
- Using cloud-native services to build elastic, scalable environments that run automated delivery processes seamlessly.

## Goals (Next 90 Days)
1. Deploy a full working end-to-end software.
2. Stay consistent for next 90-days.
3. Work on as much as cloud services as possible.

## Core Skills to Build
1. Terraform, Ansible.
2. CI/CD pipeline- Github Actions, Jenkins etc.
3. Kubernetes

## Weekly Time Budget
- Weekdays: 2 hours
- Weekends: 5 hours

## Staying Consistent
- Set Alarm, Follow a timetable.
- Track my progress at every end of week.
31 changes: 31 additions & 0 deletions 2026/day-02/linux-architecture-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Day 02 – Linux Architecture, Processes, and systemd

## Linux Architecture
- It is divided into different layers:
1. Hardware: Physical Components, the actual machine (CPU, RAM, Disk)
2. Kernel: The core of linux, the heart of the machine that runs everything- memory, CPU scheduling, devices, file systems.
3. Shell: Interface between the User and kernel. User sends command through shell to Kernel.
4. Application: The apps used by users in the system- nginx, docker, podman etc.

## Processes
- Executing instance of any program is a process.
- Every process have a unique PID.
- systemd is the first process with PID = 1.
- Types of processes:
1. Running: Process that is actively using CPU.
2. Sleeping: Process that is waiting for some result, input or output.
3. Zombie: Process that is terminated but waiting for parent process to exit (takes no resource just a empty process).
4. Stopped: Process that is stopped by interruption (mostly by ctrl + Z).
5. Dead: Process that is completely terminated by Kernel.

## systemd
- It is the service manager in linux
- Handles all the services running in background
- have PID = 1, first process that is always running under the hood.

## 5 most common commands used in Linux used on daily basis
1. systemctl: To check status or start/stop a service.
2. df -h: Check the disk usage.
3. top: live process monitor
4. ps aux: show running processes.
5. kill -9 PID: forcefully kill a process.