![Basic Dockerfile Example
# 1. Specify a base image
FROM node:16
# 2. Set the working directory inside the container
WORKDIR /app
# 3. Copy application files to the container
COPY . .
# 4. Install dependencies
RUN npm install
# 5. Specify the default command to run the app
CMD ["npm", "start"]](https://image.slidesharecdn.com/im5-introductiontodevopstools-250629113402-c74c209a/85/IM5-Introduction-to-DevOps-tooools-pptx-44-320.jpg)
IM5- Introduction to DevOps tooools.pptx
- 2. Jenkins
- 4. Why Jenkins? • Automate building, testing, and deploying code efficiently. • Jenkins knowledge is valuable for roles like DevOps Engineer and Build Engineer. • Save time and reduce human error in software development. • Works with numerous tools like Git, Maven, Docker, and Kubernetes. • Supports large-scale projects with distributed builds.
- 5. Jenkins Workflow Developers check their source code Jenkins will pick up the changed source code and trigger a build and run any tests if required The build output will be available in the Jenkins dashboards. Automatic notification can also be sent back to the developer.
- 6. Jenkins History In 2004, Kohsuke Kawaguchi created an automation server called Hudson that automates build and test task. In 2011, Oracle had a dispute with Hudson open source community, so they forked Hudson and renamed it as Jenkins. But in short span of time, Jenkins acquired a lot of contributors and projects while Hudson remained with only 32 projects. Then with time, Jenkins became more popular, and Hudson is not maintained anymore.
- 7. Continuous Integration with Jenkins • Code Commit: Developers push changes to a version control system. • Build Trigger: Jenkins detects changes and triggers the CI pipeline. • Code Checkout: Fetches the latest codebase from the repository. • Build Process: Compiles code, resolves dependencies, and packages applications. • Automated Testing: Runs unit and integration tests to ensure code quality. • Feedback: Provides build and test results to developers in real-time.
- 8. Key Features of CI with Jenkins • Automation: Streamlines builds and testing processes. • Scalability: Supports distributed builds across multiple nodes. • Real-Time Feedback: Alerts developers about build or test failures instantly. • Extensibility: Offers plugins for integration with tools like Git, Maven, Docker, and Kubernetes.
- 9. Tools Used with Jenkins in CI • Version Control: Git, GitHub, Bitbucket. • Build Automation: Maven, Gradle. • Testing Frameworks: JUnit, Selenium, TestNG. • Artifact Repositories: Nexus, Artifactory.
- 16. Workflow in Jenkins Architecture • Developers commit code to a version control system (e.g., GitHub). • Jenkins Master detects changes via webhooks or polling. • Jobs are delegated to Jenkins Agents based on resource availability. • Agents execute the assigned tasks (e.g., building, testing). • Results are sent back to the Master for reporting. • The Master provides feedback to developers via logs, dashboards, or notifications.
- 17. Advantages of Jenkins Architecture • Scalability: Add more agents to handle large workloads. • Flexibility: Supports diverse environments (Windows, Linux, macOS). • Fault Tolerance: Jobs can continue on other agents if one fails. • Distributed Builds: Efficiently distributes tasks to reduce build time.
- 18. Jenkins Pipeline
- 20. What is Continuous Delivery Pipeline? Acontinuousdeliverypipelineisanautomatedexpressiontoshowyourprocessfor gettingsoftwareforversioncontrol.Thus,everychangemadeinyoursoftwaregoes throughanumberofcomplexprocessesonitsmannertobeingreleased.Italso involvesdevelopingthesoftwareinarepeatableandreliablemanner,and progressionofthebuiltsoftwarethroughmultiplestagesoftestinganddeployment.
- 23. Benefits of JenkinsFile • You can review your code on the pipeline. • You can review your Jenkins pipeline. • This is the singular source for your pipeline and can be customized by multiple users. • You can make pipelines automatically for all branches and can execute pull requests with just one JenkinsFile.
- 24. Docker
- 25. What is Docker? Docker isa setofPlatformsasaservice (PaaS)productsthatuseOperatingsystem- levelvirtualizationtodeliversoftwareinpackagescalledcontainers. Containersarelightinweightwhichmakesthemportableandtheyareisolated fromtheunderlyinginfrastructureandfromeachothercontainer.
- 26. Why should we learn Docker? • Simplifies Deployment: Ensures applications run consistently across environments. • Resource Efficiency: Uses less memory and resources than virtual machines. • Faster Development: Speeds up testing and deployment workflows. • Standardization: Widely adopted in CI/CD pipelines and DevOps. • Isolation: Keeps app dependencies separate and conflict-free. • Portability: "Build once, run anywhere" with containers.
- 27. Key Components of Docker Docker Engine Docker Image Docker Hub Dockerfile Docker Registry
- 30. How Does Docker Works?
- 31. Why is Docker Daemon? TheDockerdaemon(dockerd)listensforDockerAPIrequestsandmanagesDocker objectssuchasimages,containers,networks,andvolumes.Adaemoncanalso communicatewithotherdaemonstomanageDockerservices.
- 32. Docker Daemon Benefits • Efficiency: Uses fewer resources than VMs. • Portability: Consistent behavior across environments. • Speed: Faster application deployment and scaling. • Isolation: Keeps apps and dependencies separate. • Flexibility: Supports microservices and multi-cloud. • Version Control: Tracks image changes easily. • DevOps Integration: Simplifies CI/CD pipelines.
- 33. Docker CLI • The most widespread tool is the Docker CLI. • It is a command line tool that lets you talk to the Docker daemon. • Docker CLI is used to interact with the Docker Engine through APIs.
- 35. What is Docker Containers? Dockercontainerisaruntimeinstanceofanimage.Allowsdeveloperstopackage applicationswithallpartsneededsuchaslibrariesandotherdependencies.Docker ContainersareruntimeinstancesofDockerimages.Containerscontainthewhole kitrequiredforanapplication,sotheapplicationcanberuninanisolatedway.
- 36. What is Virtual Machines? VirtualMachines(VMs)aresoftware-basedemulationsofphysicalcomputersthat runanentireoperatingsystem,allowingmultipleOSinstancesonasinglephysical machineusingahypervisor.
- 37. Containers vs. Virtual Machines Containers 02 01 03 Virtual Machines 02 01 03 Docker Containers contain binaries, libraries, and configuration files along with the application itself. Containers share the host OS kernel, making them lightweight. Containers share host resources while ensuring OS-level isolation. VMs run on hypervisors, each with its own OS on a single machine. VMs include their own OS, making them larger and resource-heavy. They provide Hardware- level process isolation and are slow to boot.
- 38. Docker Images
- 39. What is Docker Images? Itisafile,comprisedofmultiplelayers,usedtoexecutecodeinaDockercontainer. Theyareasetofinstructionsusedtocreatedockercontainers.DockerImageisan executablepackageofsoftwarethatincludeseverythingneededtorunan application.Thisimageinformshowacontainershouldinstantiate,determining whichsoftwarecomponentswillrunandhow.
- 40. Docker Image Commands Command Purpose Example docker images Lists all locally stored Docker images. docker images docker pull <image> Downloads an image from Docker Hub/Registry. docker pull node:16 docker rmi <image> Removes a specific image by name or ID. docker rmi nginx docker history <image> Shows the image’s build history (layers). docker history nginx docker inspect <image> Displays detailed metadata of an image. docker inspect ubuntu
- 41. Dockerfile
- 43. What is Dockerfile? It is a text document that contains necessary commands which on execution help assemble a Docker Image.
- 44. Basic Dockerfile Example # 1. Specify a base image FROM node:16 # 2. Set the working directory inside the container WORKDIR /app # 3. Copy application files to the container COPY . . # 4. Install dependencies RUN npm install # 5. Specify the default command to run the app CMD ["npm", "start"]
- 45. Docker Commands for .NET
- 46. Docker Commands Command Purpose Example docker build Builds a Docker image from a Dockerfile. docker build -t myapp . docker run Runs a container from an image. docker run -d -p 5000:5000 myapp docker stop Stops a running container. docker stop mycontainer docker ps Lists running containers. docker ps docker ps -a Lists all containers (including stopped ones). docker ps -a docker exec Executes a command inside a running container. docker exec -it mycontainer bash docker logs Shows logs of a container. docker logs mycontainer docker rm Removes a stopped container. docker rm mycontainer docker images Lists all available Docker images. docker images
- 47. Introduction to Docker Hub
- 48. Docker Hub • A cloud registry to push or pull official and user-built Docker images. • Docker Hub is like GitHub but for downloading and publishing container images. • A cloud-based repository for public and private images. • Docker users and partners create, test, store and distribute container images. • Users can host and share their own custom images. • Pushing images triggers actions via webhooks to integrate Docker Hub with other services.
- 49. Docker File Docker Hub Image Container PUSH PULL
- 50. Use Cases and Best Practices
- 51. Use Cases Microservices Architecture: It facilitates the development, deployment, and management of microservices with enabling independent scaling and maintenance. Development Environment Consistency: It will ensures with consistent development, testing, and production environments, reducing “it works on my machine” issues. Continuous Integration and Continuous Deployment (CI/CD) : It helps in streamlining and automating the software delivery process with ensuring faster and more reliable releases. Multi-Cloud and Hybrid Cloud Deployments: It helps in simplifying the application deployment across various cloud platforms, enhancing flexibility and reducing vendor lock-in.
- 52. Best Practices • Use Official Images: Prefer official, secure images. • Minimize Image Size: Use smaller base images (e.g., Alpine). • Optimize Layers: Combine commands to reduce layers. • Multi-stage Builds: Separate build and runtime environments. • Use Environment Variables: Store configuration securely. • Monitor and Log: Implement proper logging and monitoring.
- 54. What is DevOps? TheDevOpsisa combinationoftwowords,oneis softwareDevelopment,and secondis Operations.Thisallowsasingleteamtohandletheentireapplication lifecycle,fromdevelopmenttotesting,deployment,andoperations.DevOpshelps youtoreducethedisconnectionbetweensoftwaredevelopers,qualityassurance (QA)engineers,andsystemadministrators.
- 55. Why DevOps? • The operation and development team worked in complete isolation. • After the design-build, the testing and deployment are performed respectively. • Without the use of DevOps, the team members are spending a large amount of time on designing, testing, and deploying instead of building the project. • Manual code deployment leads to human errors in production. • Quality, and Speed of the application delivery has primarily improved.
- 56. DevOps History 2009 2012 2014 2015 2017 In 2009, the first conference named DevOpsdays was held in Ghent Belgium. Belgian consultant and Patrick Debois founded the conference. In 2012, the state of DevOps report was launched and conceived by Alanna Brown at Puppet. In 2014, the annual State of DevOps report was published by Nicole Forsgren, and others. In 2015, Nicole Forsgren, Gene Kim, and Jez Humble founded DORA (DevOps Research and Assignment). In 2017, Nicole Forsgren published "Accelerate: Building and Scaling High Performing Technology Organizations".
- 57. DevOps Advantages • It is an excellent approach for quick development and deployment of applications. • It responds faster to the market changes to improve business growth. • It escalate business profit by decreasing software delivery time and costs. • It improves customer experience and satisfaction. • It simplifies collaboration and places all tools in the cloud for customers to access. • DevOps means collective responsibility, which leads to better team engagement and productivity.
- 58. DevOps Disadvantages • DevOps professional or expert's developers are less available. • Developing with DevOps is so expensive. • Adopting new DevOps technology into the industries is hard to manage in short time. • Lack of DevOps knowledge can be a problem in the continuous integration of automation projects.
- 61. 61
- 62. DevOps Workflow • Plan: Collaborative planning for features, or fixes using tools like Jira or Azure Boards. • Develop: Writing code and storing it in version control systems. • Build: CI pipelines automate the building of code and running unit tests. • Test: Automated testing ensures code quality before deployment.
- 63. DevOps Workflow • Release: Continuous delivery pipelines prepare code for deployment. • Deploy: Automated deployment to production or staging environments. • Operate: Monitoring and logging systems ensure operational stability. • Monitor: Continuous feedback loops for performance, reliability, and user satisfaction.
- 65. Benefits of DevOps Architecture • Faster Delivery: Automates workflows, reducing cycle time. • Improved Collaboration: Enhances communication and coordination. • Scalability: Facilitates infrastructure management for growing applications. • Resilience: Ensures quick recovery from failures. • Continuous Improvement: Provides actionable feedback to refine processes and software.
- 66. DevOps Lifecycle
- 68. 7Cs of DevOps
- 69. 7Cs of DevOps Continuous Development fosters a culture of collaboration among developers, testers, and other stakeholders. Continuous Testing Continuous testing involves the automation of testing activities to ensure that software changes are validated at each step of the pipeline, without the need for human intervention. Continuous Integration After the code has been written, it is committed to the shared repository, where a series of events to seamlessly integrate the code is put into motion. This is also known as the CI pipeline Continuous deployment takes continuous delivery one step further by fully automating the deployment process to production without any human intervention. Continuous Monitoring It should be noted that monitoring activities have always been fairly continuous. Continuous operations focuses on the ongoing management and maintenance of software systems in production environments, and available to users throughout its lifecycle. Continuous Feedback In this stage, user feedback is continuously collected to provide insights into how to optimize the codebase.
- 71. What is DevOps Workflow? DevOpsworkflowprovidesavisualoverviewofthesequenceinwhichinputis provided.Also,ittellsaboutwhichoneactionisperformed,andoutputisgenerated foranoperationsprocess.DevOpsworkflowallowstheabilitytoseparateand arrangethejobswhicharetoprequestedbytheusers.Also,itgivestheabilityto mirrortheiridealprocessintheconfigurationjobs.
- 72. DevOps Principles • Collaboration between teams. • Automation of workflows. • CI/CD for fast delivery. • IaC for consistent infrastructure. • Monitoring for real-time insights. • Feedback for continuous improvement. • Security integrated early. • Efficiency with lean practices.
- 73. DevOps Tools
- 74. DevOps Tools
- 75. DevOps Engineers
- 76. Who is DevOps Engineer? DevOpsEngineerisanITprofessionalwhoworkswithsystemoperators,software developers,andotherproductionITstafftoadministercodereleases. DevOpsengineerunderstandsthesoftwaredevelopmentlifecycleandvarious automationtoolsfordevelopingdigitalpipelines.
- 78. Roles and Responsibilities • Manage projects effectively through an open standard based platform. • Increases project visibility through traceability. • Improve quality and reduce the development cost with collaboration. • DevOps should have the soft skill of problem solver and a quick learner. • Analyze, design, and evaluate automation scripts and systems. • Able to perform system troubleshooting and problem-solving across the platform and application domains.
- 80. What is DevOps Pipeline? Apipelineinsoftwareengineeringteamisasetofautomatedprocesseswhich allowsDevOpsprofessionalsanddevelopertoreliablyandefficientlycompile,build, anddeploytheircodetotheirproductioncomputeplatforms.Themostcommon componentsofapipelineinDevOpsarebuildautomationorcontinuousintegration, testautomation,anddeploymentautomation.
- 82. Benefits of CI Pipelines • Small changes are easy to integrate into large codebases. • More comfortable for other team members to see what you have been working. • Fewer integration issues allowing rapid code delivery. • Bugs are identified early, making them easier to fix, resulting in less debugging work.
- 84. Benefits of CD Pipelines • Faster bug fixes and features delivery. • CD allows the team to work on features and bug fixes in small batches, which means user feedback received much quicker. It reduces the overall time and cost of the project.
- 85. DevOps Methodology • The Teams: Mission or project and cloud management. • Connectivity: Public, on-premise, and hybrid cloud network access. • Automation: Infrastructure as code, scripting and deployment of resources. • On-boarding Process: How the project gets started in the cloud. • Project Environment: TEST, DEV, PROD (deployment, testing, and production). • Shared Services: Common capabilities provided by the enterprise. • Naming Conventions: Vital aspect to track resource utilization and billing.
- 86. Introduction to AWS Services
- 87. What is Microsoft Azure? MicrosoftAzure isacloudcomputingplatformthatprovidesawidevarietyof servicesthatwecanusewithoutpurchasingandarrangingourhardware.Itenables thefastdevelopmentofsolutionsandprovidestheresourcestocompletetasksthat maynotbeachievableinanon-premisesenvironment.AzureServiceslikecompute, storage,network,andapplicationservicesallowustoputoureffortintobuilding greatsolutionswithoutworryingabouttheassemblyofphysicalinfrastructure.
- 88. Azure Services Compute services: It includes the Microsoft Azure Cloud Services, Azure Virtual Machines, Azure Website, and Azure Mobile Services, which processes the data on the cloud with the help of powerful processors. Data services: This service is used to store data over the cloud that can be scaled according to the requirements. It includes Microsoft Azure Storage, Azure SQL Database, and the Redis Cache. Application services: It includes services, which help us to build and operate our application, like the Azure Active Directory, Service Bus for connecting distributed systems, HDInsight for processing big data, the Azure Scheduler, and the Azure Media Services. Network services: It helps you to connect with the cloud and on- premises infrastructure, which includes Virtual Networks, Azure Content Delivery Network, and the Azure Traffic Manager.
- 89. How Azure Works?
- 90. Cloud Computing
- 91. What is Cloud Computing? CloudComputingisthedeliveryofcomputingservicessuchasservers,storage, databases,networking,software,analytics,intelligence,andmore,overtheCloud (Internet).
- 93. Advantages • Cost: It reduces the huge capital costs of buying hardware and software. • Speed: Resources can be accessed in minutes, typically within a few clicks. • Reliability: Backup and recovery of data are less expensive and fast for continuity. • Scalability: Increase or decrease the resources according to the requirements.
- 94. Types of Cloud Computing TYPES OF CLOUD COMPUTING Public Cloud The cloud resources that are owned and operated by a third-party cloud service provider are termed as public clouds. It delivers computing resources such as servers, software, and storage over the internet Hybrid Cloud It is the combination of public and private clouds, which is bounded together by technology that allows data applications to be shared between them. Hybrid cloud provides flexibility and more deployment options to the business. Private Cloud The cloud computing resources that are exclusively used inside a single business or organization are termed as a private cloud. A private cloud may physically be located on the company’s on-site datacentre or hosted by a third-party service provider.
- 99. Storage Services Azure Blob: We can have Azure Blob storage within the storage account, which is used to store the unstructured data such as media files, documents, etc. Azure file: Azure file can be used in case if we want to share files between two virtual machines, then we can create an Azure file share and access it on both of the virtual machines. We can share the data between two or more VMs. Azure Queues: It can be used to store messages. Azure Table: It can be used to store entities. The Azure Table is a bit different from the SQL table. This is a NoSQL datastore where the schema within the table is not enforced.
- 100. Creating Storage Account Step 1: Login to your Azure portal home screen and click on "Create a resource". Then type-in storage account in the search box and then click on "Storage account".
- 101. Creating Storage Account Step 2: Click on create, you will be redirected to Create a storage account window.
- 102. Creating Storage Account Step 3: Use your existing resource group or create a new one. Here we are going to create a new resource group.
- 103. Creating Storage Account Step 4: Then, fill the storage account name, and it should be all lowercase and should be unique across all over Azure.
- 104. Creating Storage Account Step 5: You are now on the Networking window. Here, you need to select the connectivity method, then click next.
- 105. Creating Storage Account Step 6: You are now on the Advanced window were you need to enable or disable security, Azure files, Data Protection, Data lake Storage and then click next.
- 106. Creating Storage Account Step 7: Now, you are redirected to the Tags window, where you can provide tags to classify your resources into specific buckets. Put the name and value and click next.
- 107. Creating Storage Account Step 8: This is the final step where the validation has been passed, and you can review all the elements that you have provided. Click on create finally.
- 108. Creating Storage Account Now our storage account has been successfully created, and a window will appear with the message "Your deployment is complete".
- 109. Creating Storage Account Click on "goto resource", then the following window will appear.
- 110. Azure Blob Storage Itis Microsoft'sobjectstoragesolution forthecloud.Blobstorageisoptimizedfor storingamassiveamountofunstructureddata,suchastextorbinarydata. AzureblobstorageisfundamentalfortheentireMicrosoftAzurebecausemany otherAzureserviceswillstorethedatawithinastorageaccount,insidetheblob storage,andactuponthatdata.Andeveryblobshouldbestoredinacontainer.
- 111. Blob Storage Usages • It serves images or documents directly to a browser. • It stores files for distributed access. • We can stream video and audio using blob storage. • Easy writing to log files. • It stores the data for backup, restore, disaster recovery, and archiving. • It stores the data for analysis by an on-premises or Azure-hosted service.
- 112. Blob Storage Usages Block blob: It stores text binary data up- to about 4.7 TB. It is the block of data that can be managed individually. We can use block blobs mainly to improve the upload-time when we are uploading the blob data into Azure. Append blob: It is made up of blocks like block blobs, but are optimized for append operations. It is ideal for an application like logging data from virtual machines. For example - application log, event log where you need to append the data to the end of the file. Page blob: It stores random access files up-to 8 TB. Page blobs store the VHD files that backs VMs.
- 115. Azure File Storage Service
- 118. Table Storage
- 121. Typical Uses of Table Storage • It is used for storing TBs of structured data capable of serving web-scale applications. • It is used for quickly querying data using a clustered index. • The other is LINQ queries with WCF Data Services with .NET Libraries. • It is used for storing datasets that don't require complex joins, foreign keys, or stored procedures and can be denormalized for fast access.
- 127. Azure VNET Capabilities • Isolation and segmentation • Communication with the Internet • Communication between resources • Communication with on-premises resources
- 130. Security Rule Properties • Name: The name should be unique within the network security group. • Priority: Rules are processed in order with a lower number has the highest priority. • Source or Destination: The ability to specify multiple individual IP addresses and ranges in a rule is referred to as augmented security rules. • Protocol: TCP, UDP, etc. • Port range: we can specify an individual or range of ports • Action: Allow or Deny
- 134. Why Use Ansible? • Ansible is free to use by everyone. • It is lightweight, and works across any OS or hardware without constraints. • It is very secure due to its agentless capabilities and open SSH security features. • Ansible does not need any special system administrator skills to install and use it.
- 135. Ansible Workflow
- 137. Ansible Workflow
- 138. Ansible Workflow • Inventory Definition – Lists target machines (hosts) to manage. • Playbook Execution – YAML files defining tasks to be automated. • Modules Execution – Prebuilt functions that execute tasks on remote systems. • Connection & Authentication – Uses SSH (Linux) or WinRM for communication. • Task Execution – Runs tasks in order, checking for idempotency. • Handlers & Roles – Handlers trigger only on changes, and roles organize playbooks. • Reports & Logs – Outputs execution details for troubleshooting.
- 139. Ansible Architecture
- 141. Ansible Architecture
- 142. Control Node (Ansible Server) • The machine where Ansible is installed and executed. • This node contains playbooks, inventory, and modules that define automation tasks. • It pushes commands to managed nodes using SSH (for Linux) or WinRM. • No agents are required on target machines.
- 143. Managed Nodes (Target Machines) • These are the machines that Ansible automates. • Managed nodes do not require Ansible installation. • They receive instructions from the Control Node and execute tasks. • Communication happens over SSH (Linux/macOS) or WinRM (Windows).
- 144. Ansible Playbooks
- 146. Ansible Playbooks
- 147. Ansible Playbook Example --- - name: Deploy Apache Web Server hosts: web_servers become: true # Run tasks as root (sudo) tasks: - name: Install Apache apt: name: apache2 state: present update_cache: yes - name: Start Apache Service service: name: apache2 state: started enabled: yes - name: Deploy Custom Web Page copy: content: "<h1>Welcome to Ansible Automated Web Server!</h1>" dest: /var/www/html/index.html
- 148. Ansible Command
- 150. Changing the Default Directory Thecommandwillalwaysexecuteinthedefaultdirectory.Youcanchangeand specifythedirectorypathwhereyouwanttorunthecommandusingthechdir parameter.Thisparameterisavailableforbothcommandandshellmodule.
- 151. Executing Multiple Commands - hosts: loc tasks: - name: Ansible command module multiple commands command: "touch {{ item }}" with_items: - hello.txt - hello1.txt - hello2.txt args: chdir: /root/ansible If you need to run multiple commands, then you can give them to both shell and command modules using the "with_items".
- 154. Infrastructure as a Code (IaC) InfrastructureasCode(IaC)isamethodofmanagingandprovisioningIT infrastructureusingcode,ratherthanmanualconfiguration.Itallowsteamsto automatethesetupandmanagementoftheirinfrastructure,makingitmore efficientandconsistent.ThisisparticularlyusefulintheDevOpsenvironment, whereteamsareconstantlyupdatinganddeployingsoftware.
- 155. Use Cases of Terraform • Provisioning Cloud Resources: Different types of cloud resources can be provisioned by using terraform like AWS,GCP, and others. The resources can be managed are compute, storage, networking, and application services. • Infrastructure Versioning and Collaboration: You can store the scripts which have been written to provision the infrastructure in the version control system like git form where other teams can collaborate on infrastructure changes, track revisions, and roll back to previous states if needed.
- 156. Terraform Workflow
- 157. Terraform Workflow 1 ️ 1️⃣Write → Define infrastructure in .tf files. 2️⃣Init → terraform init (Set up providers & backend). 3 ️ 3️⃣Plan → terraform plan (Preview changes). 4️⃣Apply → terraform apply (Create/modify resources). 5 ️ 5️⃣State → Tracks infrastructure in terraform.tfstate. 6️⃣Change → Update .tf & re-apply changes. 7 ️ 7️⃣Destroy → terraform destroy (Remove resources).
- 158. Terraform Workflow
- 159. Uses of Terraform • Infrastructure as Code (IaC) → Automate cloud infrastructure provisioning. • Multi-Cloud Management → Deploy across AWS, Azure, GCP, etc. • Scalability → Easily scale infrastructure up or down. • Automated Deployments → CI/CD integration for faster releases. • Resource Tracking → Manages state files to track infrastructure changes. • Efficient Updates → Applies only necessary changes (incremental updates).
- 160. Terraform VS Ansible
- 161. Terraform VS Ansible Terraform Ansible Focuses on setting up and managing infrastructure. Primarily for configuring systems and deploying applications. Uses HCL for infrastructure definitions. Uses YAML for defining tasks. Automatically ensures resources are created only if necessary. Requires careful task definition to avoid duplication. Manages infrastructure changes using plans and state. Executes tasks immediately without state tracking. Excellent multi-cloud capabilities. Useful for multi-cloud configurations but limited to system-level tasks.
- 163. Advantages of Terraform • Infrastructure as Code (IaC) → Automates infrastructure provisioning with code. • Multi-Cloud Support → Works with AWS, Azure, GCP, Kubernetes, etc. • Declarative Approach → Define desired state, and Terraform handles execution. • Modular & Reusable → Use Terraform modules for consistent infrastructure. • Parallel Execution → Deploys multiple resources simultaneously for speed.
- 164. Disadvantages of Terraform • Steep Learning Curve – Requires knowledge of HCL and infrastructure concepts. • Third-Party Dependency – Relies on cloud provider APIs, which can change. • Partial Rollback Support – No built-in rollback; relies on manual state adjustments. • Resource Locking Issues – Can face concurrency issues in multi-user environments.
- 165. Quick Quizz
- 166. Quick Quiz Q1. What is the key benefit of designing a scalable architecture in AWS? ● Reduces initial infrastructure costs ● Ensures applications can handle increased traffic efficiently ● Prevents the need for security measures ● Eliminates the need for backups
- 167. Quick Quiz Q1. What is the key benefit of designing a scalable architecture in AWS? ● Reduces initial infrastructure costs ● Ensures applications can handle increased traffic efficiently ● Prevents the need for security measures ● Eliminates the need for backups B) Ensures applications can handle increased traffic efficiently 💡 Explanation: Scalable architectures ensure that applications can dynamically handle increasing workloads by adding or removing resources as needed. Correct Answer
- 168. Quick Quiz Q2. Which tool is primarily used for containerization in DevOps? ● Jenkins ● Ansible ● Docker ● Terraform
- 169. Quick Quiz Q2. Which tool is primarily used for containerization in DevOps? ● Jenkins ● Ansible ● Docker ● Terraform C) Docker 💡 Explanation: Docker is a containerization platform that packages applications and their dependencies into containers, ensuring consistency across different environments. Correct Answer
- 170. Quick Quiz Q3. What is the role of Terraform in a DevOps toolchain? ● Automates infrastructure provisioning ● Manages source code repositories ● Handles continuous integration ● Manages network security
- 171. Quick Quiz Q3. What is the role of Terraform in a DevOps toolchain? ● Automates infrastructure provisioning ● Manages source code repositories ● Handles continuous integration ● Manages network security A) Automates infrastructure provisioning 💡 Explanation: Terraform is an Infrastructure-as-Code (IaC) tool that automates the provisioning and management of cloud infrastructure. Correct Answer
- 172. Quick Quiz Q4. Which DevOps tool is primarily used for configuration management and automation? ● GitHub ● Ansible ● Docker ● Kubernetes
- 173. Quick Quiz Q4. Which DevOps tool is primarily used for configuration management and automation? ● GitHub ● Ansible ● Docker ● Kubernetes B) Ansible 💡 Explanation: Ansible is an open-source automation tool used for configuration management, application deployment, and infrastructure orchestration. Correct Answer
- 174. Quick Quiz Q5. What is the primary purpose of AWS Auto Scaling? ● To manually add new instances to a workload ● To automatically adjust resources based on demand ● To reduce the need for monitoring AWS resources ● To replace EC2 instances only when they fail
- 175. Quick Quiz Q5. What is the primary purpose of AWS Auto Scaling? ● To manually add new instances to a workload ● To automatically adjust resources based on demand ● To reduce the need for monitoring AWS resources ● To replace EC2 instances only when they fail B) To automatically adjust resources based on demand 💡 Explanation: AWS Auto Scaling automatically adjusts compute resources based on traffic, ensuring cost efficiency and optimal performance. Correct Answer
- 176. THANK YOU