Skip to main content

Syllabus

 PUNYASHLOK AHILYADEVI HOLKAR SOLAPUR UNIVERSITY, SOLAPUR 

Final Year B.Tech. 

(COMPUTER SCIENCE & ENGINEERING) 

SEMESTER - I 

CS415 : DevOps 

  • Teaching Scheme: Lectures: 2 Hours /Week, 2 credits, Practical: 2 Hour/Week, 1 credit 
  • Examination Scheme:  ISE - 25 marks, POE – 50 marks, ICA - 25 marks,

Course Objectives: 

  1. To introduce DevOps terminology, definition & concepts 
  2. To understand the different Version control tools. 
  3. To understand the concepts of Continuous Integration / Continuous Deployment) 
  4. To get acquainted with concept of docker and kubernets 
  5. To Illustrate the benefits and drive the adoption of cloud-based Devops tools to solve real world problems 

Course Outcomes: 

At the end of the course, students will be able to 

  1. Apply DevOps principles to meet software development requirements. 
  2. Apply CI/CD using tools such as Jenkins, Git and Maven 
  3. Analyze the Containerization ofimages and deployment of applications over Docker 
  4. Collaborate and adopt Devops in real-time projects. 

***

SECTION - I 

Chapter1:Introduction to Devops (05) 

Devops Essentials - Introduction To AWS, GCP, Azure - Version control systems: Git and Github, Introduction to GitLab, Introduction to BitBucket 


Chapter 2 : Compile and Build Using Maven (05) 

Introduction, Installation of Maven, POM files, Maven Build lifecycle, Build Phases (compile build,test, package) Maven Profiles, Maven Repositories (local, central, global), Maven plugins, Maven Create and Build Artifacts, Dependency Management 


Chapter 3 : Continuous Integration Using Jenkins (06) 

Introduction to CI/CD, Install & Configure Jenkins,Jenkins Architecture Overview, Build Jobs and Configurations, Jenkins Plugins, Jenkins Integration with other Tools 

SECTION – II 

Chapter 4 :Containerization with Docker (05) 

Introduction to Containerization, Introduction to Docker, Understanding Images and Containers, Working with Containers. 


Chapter 5 : Kubernetes (05) 

Introduction to Kubernetes, Need of Kubernetes, Kubernetes Architecture, Setup Kubernetes, Kubernetes Concepts 


Chapter 6 : Building Devops Pipelines Using any Cloud Platform (05) 

Create Github Account, Create Repository, Create Organization, Create a New Pipeline, Build a Sample Code 

***

 Text Books : 

  1. DevOps Tools from Practitioner's Viewpoint. Deepak Gaikwad, Viral Thakkar,. Wiley publications. 
  2. Jenkins, The Definitive Guide, John Ferguson Smart,O'Reilly Publication. 

***

 Reference Books: 

  1. The DevOps2.1 ToolKit : Docker Swarm, Building, Testing, Deploying, and Monitoring services inside Docker Swarm clusters by Viktor FarcicPackt Birmingham, Mumbai. 
  2. MariotTsitoara, “Ansible 6. Beginning Git and GitHub: A Comprehensive Guide to Version Control, Project Management, and Teamwork for the New Developer”, Second Edition, 2019. 
  3. https://maven.apache.org/guides/getting-started/ 

___

 Internal Continuous Assessment (ICA): ICA shall include Minimum 8 to 10 practical assignments based on the syllabus topics.

Comments

Post a Comment

Popular posts from this blog

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend
Post a Comment
Read more

Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server

  Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server  Objective: The objective of this experiment is to set up a CI/CD pipeline for a web development project using Jenkins, Git, and webhooks, without the need for a Jenkinsfile. You will learn how to automatically build and deploy a web application to a local HTTP server whenever changes are pushed to the Git repository, using Jenkins' "Execute Shell" build step. Introduction: Continuous Integration and Continuous Deployment (CI/CD) is a critical practice in modern software development, allowing teams to automate the building, testing, and deployment of applications. This process ensures that software updates are consistently and reliably delivered to end-users, leading to improved development efficiency and product quality. In this context, this introduction sets the stage for an exploration of how to apply CI/CD principles specifically to web development using J
1 comment
Read more

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories. Local Repository: Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux). Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment. Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies. Central Repository: Location: The central repo
Post a Comment
Read more