inno-devops-labs · Draeston · Nov 10, 2024 · Nov 10, 2024 · Nov 10, 2024 · Nov 10, 2024
diff --git a/.github/workflows/github-actions-demo.yml b/.github/workflows/github-actions-demo.yml
@@ -0,0 +1,39 @@
+name: GitHub Actions Demo
+run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
+on: [push,workflow_dispatch]
+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@v4
+      - 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 }}."
+
+      - name: Gather System Information
+        run: |
+          echo "System Information"
+          echo "Runner Info"
+          echo "Name: $RUNNER_NAME"
+          echo "OS: $RUNNER_OS"
+          echo "OS Version: $RUNNER_OS_VERSION"
+          echo ""
+
+          echo "Hardware Info"
+          echo "CPU Info:"
+          lscpu
+          echo "Memory Info:"
+          free -h
+          echo "Disk Info:"
+          df -h
+          echo ""
+
+          echo "OS Info"
+          lsb_release -a
diff --git a/labs/lab1/1.png b/labs/lab1/1.png
diff --git a/labs/lab1/submission1.md b/labs/lab1/submission1.md
@@ -0,0 +1,44 @@
+## Task 1
+
+Signing commits is a way to improve security of the repository as it ensures that changes are made by the trusted individual.
+
+## Task 2
+
+### Standard Merge
+
+Pros:
+
+- Keeps complete history of commits
+- Default approach, thus it is easier for all collaborators to understand and use it
+
+Cons:
+
+- History of changes is harder to follow and can become a mess
+
+Why default?
+
+It enhances the ability of collaborators to trace changes made in the repository as well as the ability to keep track of context of these changes.
+
+### Squash and Merge
+
+Pros:
+
+- Produces cleaner history by reducing number of commits
+
+Cons: 
+
+- Loses metadata about individual contributions thus making detailed history harder to trace back.
+
+### Rebase and Merge
+
+Pros:
+
+- Clear and linear history which is really easy to navigate
+
+Cons:
+
+- Possibility to rewrite changes made earlier
+- Harder conflict resolution
+
+
+![](1.png)
diff --git a/labs/lab10/submission10.md b/labs/lab10/submission10.md
@@ -0,0 +1,47 @@
+## Task 1
+
+1. AWS - Elastic Container Registry
+
+- It has fully managed infrastructure allowing for the simplification of storing and managing Docker container images.
+- Also, it lets to seamlessly integrate with Amazon ECS and Amazon EKS, simplifying all underlying processes
+- Has in-built Amazon tools for managing security of the registry
+- Lastly, it has high performance, scalability and availability
+
+2. GCP - Google Cloud Artifact Registry
+
+- It has detailed access control and logging
+- Allows to manage both container images and popular packages in a single repository
+- Has vulnerability scanning for enhancing security
+- Provides different regional options
+
+3. Azure - Azure Container Registry
+
+- It also has fully managed infrastructure allowing for the simplification of storing and managing Docker container images.
+- Provides integration with Azure services for managing CI/CD
+- Has geo-replication across multiple regions
+- Has integration with Azure services for enhancing security
+
+## Task 2
+
+1. AWS - AWS Lambda
+
+- Payment only for used computational power
+- Supports code on most popular frameworks/languages, such as Node.js, Python, Java, Go, etc.
+- Has integration with other AWS services
+- Automatically scales the application based on the current needs
+
+2. GCP - Google Cloud Functions
+
+- It has an auto-scaling based on incoming events
+- Also, supports an integration with different Google Cloud services
+- Primarily supports Node.js, but also has support for other popular languages
+- Performs execution of code in response to various events
+
+3. Azure - Azure Functions
+
+- Supports popular languages such as Python and JS
+- Also, automatically scales based on current needs
+- Has a seamless integration with Microsoft services
+- Has Durable Functions to introduce stateful function execution
+
+Based on these points, it seems like one of main deciding factors among these three would be other services with which those offer integration to, i.e. infrastructure of the whole AWS, GCP or Azure
diff --git a/labs/lab2/1.png b/labs/lab2/1.png
diff --git a/labs/lab2/2.png b/labs/lab2/2.png
diff --git a/labs/lab2/3.png b/labs/lab2/3.png
diff --git a/labs/lab2/4.png b/labs/lab2/4.png
diff --git a/labs/lab2/submission2.md b/labs/lab2/submission2.md
@@ -0,0 +1,27 @@
+## Task 1
+
+### Docker
+
+![](1.png)
+
+### Bandwidth
+
+![](2.png)
+
+### Peers
+
+![](3.png)
+
+### Hash
+
+I've uploaded blank PDF file with hash of ```QmRM9uHF4EqTB5xFUJYwSKXTEhkwoawigsvnhR5C4Ub5vj```.
+
+Checked on https://ipfs.io/ipfs/QmRM9uHF4EqTB5xFUJYwSKXTEhkwoawigsvnhR5C4Ub5vj
+
+![](4.png)
+
+## Task 2
+
+https://incalculable-ice-substantial.on-fleek.app/
+
+Hash: ```bafybeic73agkthlrs2ugaiy7pvxcgybashwu4nm6i4zkysutzzs7nrqv3u```
diff --git a/labs/lab3/1.png b/labs/lab3/1.png
diff --git a/labs/lab3/2.png b/labs/lab3/2.png
diff --git a/labs/lab3/3.png b/labs/lab3/3.png
diff --git a/labs/lab3/submission3.md b/labs/lab3/submission3.md
@@ -0,0 +1,10 @@
+## Task 1
+
+![](1.png)
+
+## Task 2
+
+![](2.png)
+![](3.png)
+
+As you can see on screenshot, first of all I made all three test commits, then made soft reset, which has removed the commit but left changes made, then I did hard reset, which also reverted the changes, so we're left only with the changes made in 1st commit. After that, ```reflog``` command has let me to get hash of the 3rd commit and revert to it by 
diff --git a/labs/lab3/test1.md b/labs/lab3/test1.md
@@ -0,0 +1 @@
+Test1
diff --git a/labs/lab3/test2.md b/labs/lab3/test2.md
@@ -0,0 +1 @@
+Test2
diff --git a/labs/lab3/test3.md b/labs/lab3/test3.md
@@ -0,0 +1 @@
+Test3
diff --git a/labs/lab4/1.png b/labs/lab4/1.png
diff --git a/labs/lab4/2.png b/labs/lab4/2.png
diff --git a/labs/lab4/3.png b/labs/lab4/3.png
diff --git a/labs/lab4/4.png b/labs/lab4/4.png
diff --git a/labs/lab4/5.png b/labs/lab4/5.png
diff --git a/labs/lab4/6.png b/labs/lab4/6.png
diff --git a/labs/lab4/7.png b/labs/lab4/7.png
diff --git a/labs/lab4/8.png b/labs/lab4/8.png
diff --git a/labs/lab4/9.png b/labs/lab4/9.png
diff --git a/labs/lab4/submission4.md b/labs/lab4/submission4.md
@@ -0,0 +1,54 @@
+## Task 1
+
+1. Create a Local Repository
+
+![](1.png)
+
+2. Generate the Package Index
+
+![](2.png)
+
+3. Add the Local Repository to Your Sources List
+
+![](3.png)
+
+4. Verify the Contents of the Packages.gz File
+
+![](4.png)
+
+5. Install a Package from the Local Repository
+
+![](5.png)
+
+## Task 2
+
+1. Choose a Package to Simulate
+
+![](6.png)
+
+Here, I've chosen ```net-tools``` package, as well as for next task
+
+2. Simulate the Installation
+
+![](7.png)
+
+3. Analyze the Output
+
+![](8.png)
+
+As we can see, as the dependencies this package has libc6 and libselinux1,
+and only the package itself would be installed
+
+
+
+## Task 3
+
+1. Install a Package, ```sudo apt install your-package-name```
+
+2. Hold the Package, ```sudo apt-mark hold your-package-name```
+
+3. Verify the Hold Status, ```apt-mark showhold```
+
+4. Unhold the Package, ```sudo apt-mark unhold your-package-name```
+
+![](9.png)
diff --git a/labs/lab5/1.png b/labs/lab5/1.png
diff --git a/labs/lab5/2.png b/labs/lab5/2.png
diff --git a/labs/lab5/3.png b/labs/lab5/3.png
diff --git a/labs/lab5/4.png b/labs/lab5/4.png
diff --git a/labs/lab5/5.png b/labs/lab5/5.png
diff --git a/labs/lab5/6.png b/labs/lab5/6.png
diff --git a/labs/lab5/7.png b/labs/lab5/7.png
diff --git a/labs/lab5/TerraformAndNginx.md b/labs/lab5/TerraformAndNginx.md
@@ -0,0 +1,19 @@
+## Task 2
+
+I have installed terraform with Chocolatey that I had pre-installed ```choco terraform```, then I copied ```main.tf``` file from the tutorial.
+
+After that, I executed ```terraform init```
+
+![](4.png)
+
+Then, ```terraform apply```
+
+![](5.png)
+
+Then, I checked that website was running
+
+![](6.png)
+
+And lastly, I destroyed infrastructure with ```terraform destroy```
+
+My main challenge was that it refused to connect with the server at first, until I used VPN, spent considerable amount of time on that issue.
diff --git a/labs/lab5/submission5.md b/labs/lab5/submission5.md
@@ -0,0 +1,11 @@
+## Task 1
+
+1. Monitor System Resources
+
+![](1.png)
+
+![](2.png)
+
+2. Disk Space Management
+
+![](3.png)
diff --git a/labs/lab5/terraform/.terraform.lock.hcl b/labs/lab5/terraform/.terraform.lock.hcl