learning-hub/cloud-devops.html at main · 7vikfox/learning-hub · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>Cloud & DevOps Notes | Self Learning</title>
  <link rel="stylesheet" href="style.css">
</head>

<body>

<h1>Cloud Computing & DevOps Knowledge Base</h1>

<p>
Focused notes on cloud infrastructure, DevOps practices,
automation, CI/CD pipelines, containerization, and modern deployment strategies.
</p>

<hr>
<p>
<b>Scope:</b> Conceptual and practical learning in Cloud and DevOps.
Includes architecture design, automation tools, monitoring, scalability,
and best practices. No offensive security or exploit content included.
</p>
<hr>

<h2 id="cloud">Cloud Computing Notes</h2>

<ul>
  <li><b>1. Introduction to Cloud Computing</b>
    <ul>
      <li><b>Definition:</b> Delivery of services (storage, servers, software etc.) over the Internet.</li>
      <li><b>Goal:</b> Use IT resources without owning physical hardware.</li>
      <li><b>Example:</b> Storing files on Google Drive instead of a personal PC.</li>
    </ul>
  </li>

  <!-- List Item: Characteristics of Cloud Computing -->
<li>
  <!-- Main Heading -->
  <b>2. Characteristics of Cloud Computing</b>

  <!-- Sub-list for detailed characteristics -->
  <ul>

    <!-- On-demand self-service -->
    <li>
      <b>On-demand self-service:</b>
      <!-- Explanation -->
      Users can access computing resources such as servers, storage,
      and applications whenever needed without requiring human interaction
      with the service provider.
    </li>

    <!-- Broad network access -->
    <li>
      <b>Broad network access:</b>
      <!-- Explanation -->
      Cloud services are available over the internet and can be accessed
      from various devices like smartphones, laptops, and tablets from
      anywhere in the world.
    </li>

    <!-- Resource pooling -->
    <li>
      <b>Resource pooling:</b>
      <!-- Explanation -->
      The cloud provider pools computing resources to serve multiple users.
      These resources are dynamically assigned and reassigned based on
      demand, ensuring efficient utilization.
    </li>

    <!-- Rapid elasticity -->
    <li>
      <b>Rapid elasticity:</b>
      <!-- Explanation -->
      Resources can be quickly scaled up or down depending on the user's
      requirements. This gives the illusion of unlimited resources.
    </li>

    <!-- Measured service -->
    <li>
      <b>Measured service:</b>
      <!-- Explanation -->
      Cloud systems automatically monitor and optimize resource usage.
      Users are charged based on actual consumption (pay-as-you-go model).
    </li>

  </ul>
</li>

  </li>

<!-- List Item: Cloud Service Models -->
<li>
  <!-- Main Heading -->
  <b>3. Cloud Service Models</b>

  <!-- Sub-list explaining each model -->
  <ul>

    <!-- IaaS -->
    <li>
      <b>IaaS (Infrastructure as a Service):</b>
      <!-- Explanation -->
      Provides basic computing resources such as virtual machines,
      storage, and networking over the internet. Users have full control
      over the operating system and applications but do not manage
      the underlying physical infrastructure.
      <br>
      <!-- Example -->
      Example: AWS EC2 (Amazon Elastic Compute Cloud)
    </li>

    <!-- PaaS -->
    <li>
      <b>PaaS (Platform as a Service):</b>
      <!-- Explanation -->
      Provides a platform that allows developers to build, test,
      and deploy applications without worrying about managing
      hardware or operating systems. It includes tools, libraries,
      and frameworks for development.
      <br>
      <!-- Example -->
      Example: Google App Engine
    </li>

    <!-- SaaS -->
    <li>
      <b>SaaS (Software as a Service):</b>
      <!-- Explanation -->
      Provides ready-to-use software applications over the internet.
      Users can access these applications through a web browser
      without installing or maintaining them.
      <br>
      <!-- Example -->
      Example: Gmail, Zoom
    </li>

  </ul>
</li>


  <li><b>4. Deployment Models</b>
    <ul>
      <li><b>Public Cloud:</b> Services for everyone (e.g., AWS, Azure)</li>
      <li><b>Private Cloud:</b> Used by one organization</li>
      <li><b>Hybrid Cloud:</b> Public + Private combined</li>
    </ul>
  </li>

  <li><b>5. Advantages</b>
    <ul>
      <li>Cost-effective</li>
      <li>Scalable</li>
      <li>Accessible from anywhere</li>
      <li>Automatic updates</li>
      <li>Backup & disaster recovery</li>
    </ul>
  </li>

  <li><b>6. Disadvantages</b>
    <ul>
      <li>Needs internet connection</li>
      <li>Data security concerns</li>
      <li>Limited control</li>
      <li>Possible downtime</li>
    </ul>
  </li>

  <li><b>7. Real World Applications</b>
    <ul>
      <li><b>Storage:</b> Google Drive, Dropbox</li>
      <li><b>Streaming:</b> Netflix, Hotstar</li>
      <li><b>E-commerce:</b> Amazon</li>
      <li><b>Education:</b> Coursera</li>
      <li><b>Banking:</b> Secure cloud-based transactions</li>
    </ul>
  </li>

  <li><b>Quick Recap (Easy Examples)</b>
    <ul>
      <li><b>IaaS</b> → Renting a house (AWS EC2)</li>
      <li><b>PaaS</b> → Furnished apartment (Google App Engine)</li>
      <li><b>SaaS</b> → Hotel stay (Gmail, Zoom)</li>
    </ul>
  </li>
</ul>


<hr>

<h2 id="devops">DevOps Notes</h2>

<ul>
  <li>
    <b>DevOps</b> is a set of practices that combines
    <b>Development (Dev)</b> and <b>Operations (Ops)</b>
    to deliver software faster and more reliably.
  </li>

  <li>
    <b>Why DevOps?</b>
    <ul>
      <li>Faster software delivery</li>
      <li>Better collaboration between teams</li>
      <li>More stable and reliable systems</li>
      <li>Continuous improvement</li>
    </ul>
  </li>

  <li>
    <b>DevOps Lifecycle</b>
    <pre>
Plan → Code → Build → Test → Release → Deploy → Operate → Monitor
    </pre>
  </li>

  <li>
    <b>Key DevOps Concepts</b>
    <ul>
      <li>CI – Continuous Integration</li>
      <li>CD – Continuous Delivery / Continuous Deployment</li>
      <li>Infrastructure as Code (IaC)</li>
      <li>Automation</li>
      <li>Monitoring and Logging</li>
    </ul>
  </li>

  <li>
    <b>Common DevOps Tools</b>
    <ul>
      <li>Version Control: Git, GitHub</li>
      <li>CI/CD: GitHub Actions, Jenkins</li>
      <li>Containers: Docker</li>
      <li>Container Orchestration: Kubernetes</li>
      <li>Configuration Management: Ansible</li>
      <li>Cloud Platforms: AWS, Azure, GCP</li>
    </ul>
  </li>

  <li>
    <b>Containers & Docker</b>
    <ul>
      <li>Containers package application + dependencies</li>
      <li>Lightweight and portable</li>
      <li>Docker is the most popular container platform</li>
    </ul>
  </li>

  <li>
    <b>CI/CD Example Flow</b>
    <pre>
Developer pushes code →
Tests run automatically →
Build is created →
Application is deployed
    </pre>
  </li>

   <h1>CI/CD Pipeline Notes</h1>

    <h2>1. Introduction to CI/CD</h2>
    <p>
        CI/CD stands for <strong>Continuous Integration</strong> and <strong>Continuous Delivery/Deployment</strong>.
        It is a modern DevOps practice that automates software building, testing, and deployment.
    </p>

    <h2>2. Continuous Integration (CI)</h2>
    <ul>
        <li>Developers frequently merge code into a shared repository.</li>
        <li>Each merge triggers automated builds and tests.</li>
        <li>Helps detect bugs early.</li>
        <li>Improves collaboration among team members.</li>
    </ul>

    <h3>Key CI Tools</h3>
    <ul>
        <li><a href="https://git-scm.com/" target="_blank">Git</a></li>
        <li><a href="https://www.jenkins.io/" target="_blank">Jenkins</a></li>
        <li><a href="https://about.gitlab.com/" target="_blank">GitLab CI</a></li>
        <li><a href="https://github.com/features/actions" target="_blank">GitHub Actions</a></li>
    </ul>

    <h2>3. Continuous Delivery (CD)</h2>
    <ul>
        <li>Code changes are automatically prepared for release.</li>
        <li>Deployment to staging or production can be done manually.</li>
        <li>Ensures software is always in a deployable state.</li>
    </ul>

    <h2>4. Continuous Deployment</h2>
    <ul>
        <li>Extends Continuous Delivery.</li>
        <li>Automatically deploys every successful build to production.</li>
        <li>No manual intervention required.</li>
    </ul>

    <h2>5. CI/CD Pipeline Stages</h2>
    <ol>
        <li><strong>Source Stage</strong> – Code commit to repository.</li>
        <li><strong>Build Stage</strong> – Compile and package application.</li>
        <li><strong>Test Stage</strong> – Run automated tests.</li>
        <li><strong>Deploy Stage</strong> – Deploy to staging/production.</li>
        <li><strong>Monitor Stage</strong> – Monitor application performance.</li>
    </ol>

    <h2>6. Benefits of CI/CD</h2>
    <ul>
        <li>Faster release cycles.</li>
        <li>Reduced manual errors.</li>
        <li>Improved software quality.</li>
        <li>Better team productivity.</li>
    </ul>

    <h2>7. Best Practices</h2>
    <ul>
        <li>Maintain a single source repository.</li>
        <li>Automate testing at every stage.</li>
        <li>Keep builds fast.</li>
        <li>Monitor continuously after deployment.</li>
        <li>Implement rollback strategies.</li>
    </ul>

    <h2>8. Conclusion</h2>
    <p>
        CI/CD pipelines are essential for modern software development.
        They ensure faster delivery, higher quality, and reliable deployments.
    </p>

    <h1>Docker Notes</h1>

    <h2>1. Introduction to Docker</h2>
    <p>
        <a href="https://www.docker.com/" target="_blank">Docker</a> is an open-source platform used to develop, ship, and run applications inside lightweight containers.
        Containers package an application with all its dependencies so it can run consistently across different environments.
    </p>

    <h2>2. Why Docker?</h2>
    <ul>
        <li>Environment consistency (Works on my machine problem solved)</li>
        <li>Lightweight compared to virtual machines</li>
        <li>Fast deployment</li>
        <li>Easy scalability</li>
        <li>Efficient resource usage</li>
    </ul>

    <h2>3. Docker Architecture</h2>
    <ul>
        <li><strong>Docker Client</strong> – Command line interface (CLI).</li>
        <li><strong>Docker Daemon</strong> – Runs containers and manages images.</li>
        <li><strong>Docker Images</strong> – Read-only templates to create containers.</li>
        <li><strong>Docker Containers</strong> – Running instances of images.</li>
        <li><strong>Docker Registry</strong> – Stores Docker images (e.g., Docker Hub).</li>
    </ul>

    <h2>4. Key Docker Concepts</h2>

    <h3>Docker Image</h3>
    <p>
        A lightweight, standalone, executable package that includes application code, libraries, dependencies, and configuration files.
    </p>

    <h3>Docker Container</h3>
    <p>
        A running instance of a Docker image. Containers are isolated but share the host OS kernel.
    </p>

    <h3>Dockerfile</h3>
    <p>
        A text file containing instructions to build a Docker image.
    </p>

    <h3>Docker Hub</h3>
    <p>
        A cloud-based registry service where Docker images are stored and shared.
    </p>

    <h2>5. Common Docker Commands</h2>
    <ul>
        <li><code>docker --version</code> – Check Docker version</li>
        <li><code>docker pull image_name</code> – Download image</li>
        <li><code>docker build -t image_name .</code> – Build image</li>
        <li><code>docker run image_name</code> – Run container</li>
        <li><code>docker ps</code> – List running containers</li>
        <li><code>docker stop container_id</code> – Stop container</li>
        <li><code>docker rm container_id</code> – Remove container</li>
        <li><code>docker rmi image_name</code> – Remove image</li>
    </ul>

    <h2>6. Docker vs Virtual Machines</h2>
    <table border="1">
        <tr>
            <th>Docker</th>
            <th>Virtual Machine</th>
        </tr>
        <tr>
            <td>Lightweight</td>
            <td>Heavyweight</td>
        </tr>
        <tr>
            <td>Shares host OS kernel</td>
            <td>Has its own guest OS</td>
        </tr>
        <tr>
            <td>Fast startup</td>
            <td>Slow startup</td>
        </tr>
        <tr>
            <td>Less resource usage</td>
            <td>More resource usage</td>
        </tr>
    </table>

    <h2>7. Docker Compose</h2>
    <p>
        Docker Compose is a tool used to define and run multi-container Docker applications using a YAML file.
    </p>

    <h2>8. Benefits of Docker</h2>
    <ul>
        <li>Portability</li>
        <li>Scalability</li>
        <li>Isolation</li>
        <li>Continuous Deployment support</li>
        <li>Improved DevOps workflow</li>
    </ul>

    <h2>9. Best Practices</h2>
    <ul>
        <li>Use official base images</li>
        <li>Keep images small</li>
        <li>Use multi-stage builds</li>
        <li>Do not run containers as root</li>
        <li>Use .dockerignore file</li>
    </ul>

    <h2>10. Conclusion</h2>
    <p>
        Docker simplifies application deployment by using containerization technology.
        It is widely used in DevOps and CI/CD pipelines for modern application development.
    </p>

  <li>
    <b>DevOps & Security (DevSecOps)</b>
    <ul>
      <li>Security integrated early in development</li>
      <li>Automated security testing</li>
      <li>Continuous vulnerability monitoring</li>
    </ul>
  </li>
</ul>

<p>
  <b>Next Topics:</b>
  Docker commands, Kubernetes basics, GitHub Actions,
  cloud fundamentals, monitoring tools.
</p>
</body>
</html>

<hr>
<p>Last updated: 2026 · Self-learning </p>