Introduction to DevOps RT5 2021-2022 Today’s program 1. How was life before DevOps 2. What’s DevOps 1. Guidelines 2. Priorities 3. How can it be achieved 3. Automation 4. Operation 5. Deployment models 2 1 Before DevOps Before DevOps ▸ Disagreement between development team and operations team ▸ Operations: It doesn’t work in production servers, we are going to roll back ▸ Developer: It works on my machine, I don’t care about your systems 2 What’s DevOps DevOps Guidelines: CAMS ▸ Culture: Let’s communicate more ▸ Automation: Let’s deploy faster ▸ Measurement: How much? ▸ Sharing: We are on the same team 6 DevOps as a philosophy ▸ Priorities are set: ▹ People over Process over Tools How it can be achieved ▸ Splitting teams into small ones ▸ Mix teams: Development and Operations work closer to each others ▸ Automation: Less humain error and more efficiency 3 Automation CI/CD Pipelines ▸ It’s a never ending loop of improvements ▸ Relies on automating a big portion of the SDLC (especially redundent tasks) ▸ Reduces time-to-market IaC: Infrastructure as Code ▸ Infrastructure is written as code: ▹ Idempotent (if applied twice, it leads to the same state) ▹ Can be versioned (using any VCS like GIT) ▹ Easy to replicate and less like likely to be affected by human error when applied 3 Operating Operating It involves: ▸ Logging: Saving all events ▸ Monitoring: Observing the health of the system and application ▸ Alerting: Notifying the team about abnormal behaviour of the system 4 Deployment models On Premise (Old) ▸ Not Cheap ▸ Requires: ▹ System administrators ▹ Network administrators ▹ Electrical Engineering ▹ Etc.. 15 On Premise (Old) ▸ Up to you to: ▹ Buy expensive hardware all-at-once ▹ Manage everything by yourself: ▹ Redundant and backup power ▹ Network ▹ Server hardware: CPU, Disks, Memory, boards and cards ▹ Hypervisors (Virtualization Layer) 16 Cloud Computing (New) ▸ You manage less compared to premises ▸ Faster provisioning ▸ On-demand billing or upfront subscriptions based on your company’s needs ▸ Faster deployment ▸ Requires less IT experts 17 Cloud types Private Public Only people from inside the company are able to access the cloud. It can use company’s on-premise hardware to provide more flexibility and control, or can use dedicated hardware from a provider Everyone is able to use the cloud. Hardware is managed and maintained by the provider and also shared between different users. Users have no access to the hardware. Hybrid Community This kind of cloud relies on both public and private clouds. It uses the company’s premises but communicates to some cloud services for burst computations. User can match whatever combination of public and private clouds. Community clouds are a hybrid form of private clouds built and operated specifically for a targeted group. These communities have similar cloud requirements and their ultimate goal is to work together to achieve their business objectives. 18 Cloud Service types Infrastructure as a Service (IaaS) Containers as a Service (CaaS) Platform as a Service (PaaS) Functions as a Service (FaaS) Software as a Service (SaaS) 19 How do they compare? 20 fasten your seatbelt ▸ Ensure everyone has an AWS Educate account ▸ SSH Client working perfectly 21
