codingcoffee/slides
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

chore: update presentation

Browse source 
Signed-off-by: Ameya Shenoy <shenoy.ameya@gmail.com>
This commit is contained in:
Ameya Shenoy 2021-08-17 13:13:01 +05:30
parent 209444a343
commit b60f4b6a33
Signed by: codingcoffee
GPG key ID: 88174D3C138A243E
1 changed files with 39 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

47
0002-containers/index.html
View file

@ -30,6 +30,8 @@
Feel free to heckle.
Interupt me. Ask questions in the middle, makes this fun, I like it.
Or you can wait till the end, but interactive is good
I'll be talking about containers, their basic underlying working, their functionality how eYantra can benefit it
</textarea>
</section>
</section>
@ -37,28 +39,56 @@
<section>
<section data-markdown data-separator="---" data-separator-notes="^Note:">
<textarea data-template>
What is a container?
Note:
- feels like a VM
- we can SSH into it
- but its not a VM
- cgroups and namespaces
- been around since 2008, as c-groups in linux, this paved the path for containers later on
- cgroups are used to control CPU and Memory
- namespaces
---
<img data-src="./images/cgroups.jpg"></img>
---
<img data-src="./images/vm_vs_container.jpg"></img>
<br/>
VM Vs Container
Note:
I'll be talking about containers, their basic underlying working, their functionality how eYantra can benefit it
been around since 2008, as c-groups in linux, this paved the path for containers later on
- examples: firejail, lxc, docker
- VM: dedicated resource
Container: shared resources
- No inconcistency issues
- Demo container
- cp -r /usr/bin/ .
- cp -r /usr/lib/ .
- cp -r /usr/lib64/ .
- touch sample.txt
- pwd
- I dont think setting up a VM is that easy!
- examples of container runtimes: firejail, lxc, docker
---
Limitations of VM
- dependency hell
- versioning
- upgrades
- replication
- upgrades
Note:
- originally traditional servers, perfect replication not possible, multiple variables
- os, os version, os deps and versions, application deps and versions
- probelems
- versioning: i setup test env today, and setup production tomorrow, there may be inconcistency in the OS level deps, which may cause incompatibility
- upgrade: keeping all deps updated is important to avoid security vulns, but it comes at a cost of inconcistency
- upgrade:
- keeping all deps updated is important to avoid security vulns, but it comes at a cost of inconcistency
- security upgrades and patching needs to be done across all VMs, in docker only on host OS
- replication: b/w qa and prod env, local dev, works on my machine, doesnt work in prod, dev work on mac books, prod is centos
---
@ -87,6 +117,7 @@
- network:
- d run -it --rm python:3.9.4-alpine3.13 sh
- d run -it --rm --network none python:3.9.4-alpine3.13 sh
- ping 1.1.1.1
- scaling: better utilization of resources, resource allocation and sharing
---
@ -98,9 +129,9 @@
Note:
- Production-Grade Container Orchestration Platform
- container orchestration takes away a lot of operations workload from engg
- Orchestration takes away a lot of operations workload from engg
- SSL termination
- think of k8s as a knowledge base of all the best practicies of deployment for applications built at scale by Google
- Think of k8s as a knowledge base of all the best practicies for deployment of applications built at scale by Google
</textarea>
</section>