inno-devops-labs · SrbskiDobrovilci · Jan 30, 2026 · Feb 11, 2026 · Feb 20, 2026 · Feb 20, 2026
diff --git a/.github/workflows/github-actions-demo.yml b/.github/workflows/github-actions-demo.yml
@@ -0,0 +1,18 @@
+name: GitHub Actions Demo
+run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
+on: [push]
+jobs:
+  Explore-GitHub-Actions:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
+      - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
+      - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
+      - name: Check out repository code
+        uses: actions/checkout@v5
+      - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
+      - run: echo "🖥️ The workflow is now ready to test your code on the runner."
+      - name: List files in the repository
+        run: |
+          ls ${{ github.workspace }}
+      - run: echo "🍏 This job's status is ${{ job.status }}."
diff --git a/labs/image-1.png b/labs/image-1.png
diff --git a/labs/image-10.png b/labs/image-10.png
diff --git a/labs/image-11.png b/labs/image-11.png
diff --git a/labs/image-12.png b/labs/image-12.png
diff --git a/labs/image-13.png b/labs/image-13.png
diff --git a/labs/image-14.png b/labs/image-14.png
diff --git a/labs/image-15.png b/labs/image-15.png
diff --git a/labs/image-16.png b/labs/image-16.png
diff --git a/labs/image-17.png b/labs/image-17.png
diff --git a/labs/image-18.png b/labs/image-18.png
diff --git a/labs/image-19.png b/labs/image-19.png
diff --git a/labs/image-2.png b/labs/image-2.png
diff --git a/labs/image-20.png b/labs/image-20.png
diff --git a/labs/image-21.png b/labs/image-21.png
diff --git a/labs/image-22.png b/labs/image-22.png
diff --git a/labs/image-23.png b/labs/image-23.png
diff --git a/labs/image-24.png b/labs/image-24.png
diff --git a/labs/image-25.png b/labs/image-25.png
diff --git a/labs/image-26.png b/labs/image-26.png
diff --git a/labs/image-27.png b/labs/image-27.png
diff --git a/labs/image-28.png b/labs/image-28.png
diff --git a/labs/image-29.png b/labs/image-29.png
diff --git a/labs/image-3.png b/labs/image-3.png
diff --git a/labs/image-30.png b/labs/image-30.png
diff --git a/labs/image-31.png b/labs/image-31.png
diff --git a/labs/image-32.png b/labs/image-32.png
diff --git a/labs/image-33.png b/labs/image-33.png
diff --git a/labs/image-34.png b/labs/image-34.png
diff --git a/labs/image-35.png b/labs/image-35.png
diff --git a/labs/image-36.png b/labs/image-36.png
diff --git a/labs/image-37.png b/labs/image-37.png
diff --git a/labs/image-38.png b/labs/image-38.png
diff --git a/labs/image-39.png b/labs/image-39.png
diff --git a/labs/image-4.png b/labs/image-4.png
diff --git a/labs/image-40.png b/labs/image-40.png
diff --git a/labs/image-41.png b/labs/image-41.png
diff --git a/labs/image-42.png b/labs/image-42.png
diff --git a/labs/image-43.png b/labs/image-43.png
diff --git a/labs/image-44.png b/labs/image-44.png
diff --git a/labs/image-45.png b/labs/image-45.png
diff --git a/labs/image-46.png b/labs/image-46.png
diff --git a/labs/image-47.png b/labs/image-47.png
diff --git a/labs/image-48.png b/labs/image-48.png
diff --git a/labs/image-49.png b/labs/image-49.png
diff --git a/labs/image-5.png b/labs/image-5.png
diff --git a/labs/image-50.png b/labs/image-50.png
diff --git a/labs/image-51.png b/labs/image-51.png
diff --git a/labs/image-52.png b/labs/image-52.png
diff --git a/labs/image-53.png b/labs/image-53.png
diff --git a/labs/image-54.png b/labs/image-54.png
diff --git a/labs/image-55.png b/labs/image-55.png
diff --git a/labs/image-56.png b/labs/image-56.png
diff --git a/labs/image-57.png b/labs/image-57.png
diff --git a/labs/image-58.png b/labs/image-58.png
diff --git a/labs/image-59.png b/labs/image-59.png
diff --git a/labs/image-6.png b/labs/image-6.png
diff --git a/labs/image-60.png b/labs/image-60.png
diff --git a/labs/image-61.png b/labs/image-61.png
diff --git a/labs/image-62.png b/labs/image-62.png
diff --git a/labs/image-63.png b/labs/image-63.png
diff --git a/labs/image-64.png b/labs/image-64.png
diff --git a/labs/image-65.png b/labs/image-65.png
diff --git a/labs/image-66.png b/labs/image-66.png
diff --git a/labs/image-67.png b/labs/image-67.png
diff --git a/labs/image-68.png b/labs/image-68.png
diff --git a/labs/image-69.png b/labs/image-69.png
diff --git a/labs/image-7.png b/labs/image-7.png
diff --git a/labs/image-70.png b/labs/image-70.png
diff --git a/labs/image-71.png b/labs/image-71.png
diff --git a/labs/image-72.png b/labs/image-72.png
diff --git a/labs/image-73.png b/labs/image-73.png
diff --git a/labs/image-74.png b/labs/image-74.png
diff --git a/labs/image-75.png b/labs/image-75.png
diff --git a/labs/image-76.png b/labs/image-76.png
diff --git a/labs/image-77.png b/labs/image-77.png
diff --git a/labs/image-78.png b/labs/image-78.png
diff --git a/labs/image-79.png b/labs/image-79.png
diff --git a/labs/image-8.png b/labs/image-8.png
diff --git a/labs/image-80.png b/labs/image-80.png
diff --git a/labs/image-81.png b/labs/image-81.png
diff --git a/labs/image-82.png b/labs/image-82.png
diff --git a/labs/image-83.png b/labs/image-83.png
diff --git a/labs/image-84.png b/labs/image-84.png
diff --git a/labs/image-85.png b/labs/image-85.png
diff --git a/labs/image-86.png b/labs/image-86.png
diff --git a/labs/image-9.png b/labs/image-9.png
diff --git a/labs/image.png b/labs/image.png
diff --git a/labs/submission1.md b/labs/submission1.md
diff --git a/labs/submission2.md b/labs/submission2.md
@@ -0,0 +1,96 @@
+### Task 1 
+
+![alt text](image-2.png)
+
+![alt text](image-3.png)
+
+![alt text](image-4.png)
+
+blob - 38e739694be035dc31fcbea00e9151dab938dbe6    test.txt (  any single file changed)
+
+tree - tree 1da10c0dfa022559f46478f9684228d99f64a341    labs (  and any folder)
+
+commit ojbect content - " tree c79f51b057b9701a598453e063ca55cc84e5e19b
+parent 1c7fefcaae674f36b4a1bfd187eb9b82ddfcc067
+author Nikita Stepankov <gfnmjg@gmail.com> 1770788139 +0300
+committer Nikita Stepankov <gfnmjg@gmail.com> 1770788139 +0300 "
+
+### Task 2
+after reset --soft ,  back to second, third removed
+log --oneline
+![alt text](image-5.png)
+reflog
+![alt text](image-6.png)
+after --hard
+
+log --oneline
+![alt text](image-8.png)
+reflog
+![alt text](image-7.png)
+
+after back
+outline 
+![alt text](image-12.png)
+
+reflog
+![alt text](image-11.png)
+
+
+| Reset Type | HEAD Moves | Index Changes | Working Tree Changes | Best For                       |
+|------------|------------|---------------|----------------------|--------------------------------|
+| --soft     | ✓ Yes      | ✗ Kept        | ✗ Kept               | Edit commit message/reorganize |
+| --hard     | ✓ Yes      | ✓ Discarded   | ✓ Discarded          | Discard all changes completely |
+
+### Task 3
+graph snippet
+![alt text](image-13.png)
+
+commit messaeg list
+Side branch commit
+
+Add test file
+
+docs: done lab1 submissions
+
+Fix submission
+
+test
+
+change pull_request template
+
+Add pull_request_template in git
+
+docs: add lab1 submission stub
+
+docs: add commit signing summary
+
+
+it clearly show structure of the repo with all commits
+
+### Task 4
+
+tag
+![alt text](image.png)
+
+hash
+![alt text](image-1.png)
+
+Tags imporatnt for versioning, CI/CD triggers, documentation and stability. It improves realization of thise feature of repo
+
+
+### Task 5
+commands
+![alt text](image-14.png)
+
+git status 
+![alt text](image-15.png)
+
+gir branch
+![alt text](image-16.png)
+
+Git status shows file that are not added to next commit, so it show whats file are can be added to save last changes of this file
+Gir branch show on what branch you are and all structure of repo with all branches in
+
+### GitHub Community
+
+Starring repositories helps maintainers gauge interest and impact, while giving you a bookmark to revisit useful code, learn patterns, and track influential projects. Following developers builds professional networks, keeps you aware of best practices and emerging tools, and fosters mentorship opportunities within your team and the broader community.
diff --git a/labs/submission3.md b/labs/submission3.md
@@ -0,0 +1,38 @@
+#  Task 1
+Worflow run succefully
+![alt text](image-17.png)
+
+
+Logs of worflow
+![alt text](image-18.png)
+
+In GitHub Actions, there are several key components:
+
+Jobs - a collection of sequential steps executed by a runner
+
+Steps - individual tasks within a job
+
+Runners - virtual machines responsible for running workflows
+
+Triggers - events that initiate workflow execution (e.g., push operations)
+
+The workflow was initiated following a git push command, as specified in the configuration with "on: [push]".
+
+Upon receiving a push event, GitHub validates the workflow configuration files and provisions a virtual machine to carry out the steps defined in the YAML file.
+
+
+# Task 2
+Add manual worflow runner 
+![alt text](image-19.png)
+
+![alt text](image-20.png)
+
+Gathering information wtih github workflow
+![alt text](image-21.png)
+
+![alt text](image-22.png)
+
+Automatic triggers (push) occur whenever changes are submitted to the repository.
+Manual triggers (workflow_dispatch) are initiated by users through the "Run workflow" button in the GitHub interface. Manual execution is particularly useful for testing purposes, as it eliminates the need to create a new commit.
+
+The workflow runs on a GitHub-hosted runner using the Ubuntu operating system. This runner provides a standard Linux environment equipped with pre-installed tools such as Git, Python, Node.js, and others. This setup is well-suited for automated builds, testing procedures, and script execution.
diff --git a/labs/submission4.md b/labs/submission4.md
@@ -0,0 +1,77 @@
+## Task 1.1 
+systemd-analyze
+
+![alt text](image-23.png)
+
+systemmd-analyze blame
+![alt text](image-24.png)
+
+Checked System Load:
+![alt text](image-33.png)
+
+## Task 1.2
+Identify Resource-Intensive Processes:
+![alt text](image-26.png)
+
+### Answers and observation
+Top memory consuming is PID 231       1 /usr/bin/python3 /usr/share  0.2  0.0 = 0.2. 
+Top cpu consumption is     1       0 /sbin/init                   0.1  0.6
+
+Basic ones just system proccess that needs to run fot system
+
+## Task 1.3
+Map Service Relationships:
+![alt text](image-27.png)
+
+![alt text](image-28.png)
+
+## Task 1.4
+Audit Login Activity:
+![alt text](image-29.png)
+
+![alt text](image-30.png)
+
+### Obseration
+I entered the system with name gfnmj
+
+## Task 1.5
+Inspect Memory Allocation:
+
+![alt text](image-32.png)
+
+### Obseration
+
+Have a lot of free memery to use, no additional files used to extend memory load
+
+
+## Task 2.1
+
+traceroute
+![alt text](image-34.png)
+### insights
+The traceroute shows your traffic takes a path from Russia through Sweden to Germany before reaching GitHub, with multiple timeouts suggesting routers configured to not respond to ICMP requests rather than actual connectivity issues. Despite these timeouts, the connection works with reasonable latency (~60ms) to GitHub's servers, though the routing path appears somewhat indirect.
+Dig 
+![alt text](image-35.png)
+### insights
+This dig output shows a successful DNS lookup for github.com resolving to IP address 140.82.121.4 in just 7 milliseconds. Your DNS server at 10.255.255.254 responded quickly with the correct GitHub address, and the short TTL (Time-To-Live) of 3 seconds indicates this record expires very quickly.
+
+
+## Task 2.2
+No captureed  traffic ![alt text](image-36.png)
+
+### example of dns query
+Example DNS query: Out IP 172.17.222.XXX.44383 > 8.8.8.8.53: 17629+ [1au] A? gith, teub.com.
+This shows my local WSL machine, with its IP address partially redacted, initiating a DNS resolution. It forwards a request to Google's public DNS server at 8.8.8.8, specifically asking for the IPv4 address (an 'A' record) associated with github.com.
+
+Example response: In IP 8.8.8.8.53 > 172.17.222.XXX.44383: ... A 20.205.243.166
+The public DNS server replies, providing the resolved information. The query is successful, returning the specific IP address 20.205.243.166 for the requested domain.
+
+## Task 2.3
+8.8.4.4
+![alt text](image-37.png)
+1.1.2.2
+![alt text](image-38.png)
+
+Comparison of reverse lookup results: The reverse lookup for 8.8.4.4 successfully resolved to dns.google., confirming that Google has configured a valid PTR record for this IP. On the other hand, the lookup for 1.1.2.2 timed out and returned NXDOMAIN (non-existent domain), indicating that there is no reverse DNS (PTR) record associated with this IP address.
+
+
diff --git a/labs/submission5.md b/labs/submission5.md
@@ -0,0 +1,82 @@
+# Task 1
+Installed succes,  without any issues
+Platfrom : Windows 11 Home
+Version of VM box :  7.2.4 r17099
+![alt text](image-39.png)
+
+# Task 2
+## VM config:
+![alt text](image-40.png)
+
+![alt text](image-41.png)
+
+## CPU info: 
+### tools:
+lscpu
+### used command:
+lscpu
+cat /proc/cpuinfo | grep -E "model name|cpu MHz|cpu cores|siblings"
+### output
+![alt text](image-42.png)
+
+## Memory infomation
+### tools:
+free
+### used command:
+free -h
+### output
+![alt text](image-43.png)
+
+## Network Configuration
+
+used command
+ip addr show
+hostname -I
+![alt text](image-44.png)
+
+## Storage Information
+### tools :
+df
+lsblk
+fdisk
+### used command:
+df -h
+lsblk
+sudo fdisk -l
+### output
+![alt text](image-45.png)
+
+![alt text](image-46.png)
+![alt text](image-47.png)
+## Operating System
+### tools : 
+lsb_release
+uname
+hostnamectl
+
+### used commands :  
+lsb_release -a
+cat /etc/os-release
+uname -a
+hostnamectl
+### output
+![alt text](image-48.png)
+![alt text](image-49.png)
+
+## Virtualization Detection
+tools: 
+systemd-detect-virt
+lscpu
+dmesg
+dmidecode
+### command used: 
+systemd-detect-virt
+lscpu | grep Hypervisor
+dmesg | grep -i virtual
+dmidecode -s system-manufacturer  
+### output
+![alt text](image-50.png)
+
+
+## Analyze
+Most useful lscpu, shows a lot of useful info about cpu frequnecy nad hypervisor. And fdisk -l, showed whole segmentation of memory disk.