DevOps

1. Storage Area Network (SAN):

●​ Definition: SAN is a high-speed network that provides access to consolidated

block-level data storage.

Block-Level Data Storage:

●​ Definition:​
Block-level data storage is a method of storing data where data is divided into
fixed-sized blocks, and each block is assigned a unique identifier. The storage system
manages these blocks independently.

Key Features:

1.​ Raw Data Storage:​

○​ Data is stored as blocks without any file structure.

○​ The operating system or application organizes and manages the data on these
blocks.
2.​ Flexibility:​

○​ Supports any file system format (e.g., NTFS, ext4, FAT32).

○​ Applications can access and manage data at the block level.
3.​ Independent Access:​

○​ Each block can be accessed directly using its identifier, making it suitable for
random access.
4.​ High Performance:​

○​ Ideal for high-speed read/write operations, especially in databases and

virtualized environments.
How It Works:

●​ Storage systems (like SANs) provide block storage to servers over a network.
●​ Servers interact with this storage as if it were a local disk.
●​ Applications or operating systems handle the file system structure and data organization.

Use Cases:

1.​ Databases:​

○​ Databases require fast, random read/write access to data, which is best achieved
with block storage.
2.​ Virtual Machines:​

○​ Block storage can create virtual disks for virtualized environments like VMware or
Hyper-V.
3.​ Transaction-Heavy Workloads:​

○​ Applications like ERP systems benefit from block-level access for real-time data
processing.

Comparison with File and Object Storage:

Feature Block Storage File Storage Object Storage

Data Unit Blocks Files Objects (data + metadata)

Performance High (random Moderate (hierarchical High (optimized for large

access) access) data)

Use Case Databases, VMs File sharing, directories Cloud storage, backups
Examples of Block Storage Solutions:

●​ SAN (Storage Area Network)

●​ iSCSI (Internet Small Computer System Interface)
●​ AWS EBS (Elastic Block Store)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

●​ Purpose: Primarily used to enhance storage devices' performance, reliability, and

accessibility in enterprise environments.
●​ Key Features:
○​ High Performance: Uses Fibre Channel or iSCSI (Internet Small Computer
System Interface) for fast data transfer.
○​ Centralized Storage: All data is stored in a centralized location for easier
management.
○​ Scalability: Allows seamless addition of storage devices.
○​ Data Security: Provides robust access controls and data encryption.
●​ Components:
○​ Host Bus Adapters (HBAs): Connect servers to the SAN.
○​ Switches: Manage data flow within the SAN.
○​ Storage Devices: Disk arrays or tape libraries for data storage.
●​ Advantages:
○​ Improved data availability.
○​ Centralized backups and disaster recovery.
○​ High-speed performance compared to traditional storage.

2. Virtualization:

●​ Definition: A technology that allows creating virtual versions of physical hardware,

operating systems, or networks.
●​ Types:
○​ Server Virtualization: Dividing a physical server into multiple virtual servers.
○​ Desktop Virtualization: Running multiple desktop environments on a single
machine.
○​ Network Virtualization: Combining multiple networks into one or dividing a
single network into multiple.
○​ Storage Virtualization: Abstracting physical storage into a single virtual pool.
●​ Benefits:
○​ Efficient resource utilization.
○​ Cost reduction by minimizing hardware needs.
○​ Simplified IT management.
 ○​ Enhanced disaster recovery and testing environments.
●​ Tools: VMware, Hyper-V, VirtualBox.

3. Docker:

●​ Definition: An open-source platform for developing, shipping, and running applications

in lightweight, portable containers.
●​ Key Concepts:
○​ Container: A standalone executable package containing an application and its
dependencies.
○​ Dockerfile: A script used to build Docker images. (blueprints or templates that
encapsulate everything needed to run a specific software application)
○​ Docker Hub: A repository for Docker images.
●​ Advantages:
○​ Fast deployment and startup.
○​ Resource efficiency compared to virtual machines.
○​ Consistent development and production environments.
●​ Use Cases:
○​ Microservices development.
○​ CI/CD pipelines.
○​ Cross-platform development.

4. Kubernetes:

●​ Definition: An open-source system for automating deployment, scaling, and

management of containerized applications.
●​ Key Components:
○​ Pods: Smallest unit that holds containers.
○​ Nodes: Machines (virtual/physical) where containers run.
○​ Cluster: A group of nodes managed by Kubernetes.
○​ Master Node: Manages the cluster and its operations.
●​ Features:
○​ Load Balancing: Efficient distribution of network traffic.
○​ Self-Healing: Restarts failed containers automatically.
○​ Scaling: Adds or removes containers based on load.
●​ Advantages:
○​ Simplifies container management.
○​ Improves resource utilization.
○​ Enhances application availability and resilience.
5. Introduction to Virtual Private Cloud (VPC):

●​ Definition: A virtual network isolated within a public cloud environment to provide a

private, secure area for resources.
●​ Key Features:
○​ Isolation: Ensures resources are private using subnets.
○​ Customizable: Choose IP ranges, route tables, and gateways.
○​ Connectivity: Integrates with on-premises networks via VPN or direct
connection.
●​ Advantages:
○​ High security within a public cloud.
○​ Customizable and scalable.
○​ Cost-efficient compared to private clouds.
●​ Example Providers: AWS VPC, Google Cloud VPC.

6. Private Cloud Setup:

●​ Definition: A cloud environment exclusively dedicated to a single organization, offering

greater control and security.
●​ Steps to Set Up:
○​ Choose a private cloud platform (e.g., OpenStack, VMware vSphere).
○​ Set up hardware (servers, storage, and networking).
○​ Install private cloud software.
○​ Configure security policies and access controls.
○​ Monitor and maintain the cloud environment.
●​ Benefits:
○​ Enhanced data privacy and security.
○​ Better control over resources.
○​ Tailored infrastructure to specific needs.
●​ Challenges:
○​ High initial setup cost.
○​ Requires skilled staff for management.

7. Automation Using Cloud API:

●​ Definition: The use of APIs (Application Programming Interfaces) to automate cloud

tasks such as provisioning, configuration, and scaling.
●​ How It Works:
○​ APIs act as a communication interface between the user and the cloud service.
○​ Common APIs include REST and SOAP.
 ●​ Examples of Tasks:
○​ Automatically scaling resources based on demand.
○​ Setting up virtual machines or containers.
○​ Automating backups and monitoring.
●​ Benefits:
○​ Reduces manual effort and human errors.
○​ Increases operational efficiency.
○​ Improves deployment speed.
●​ Popular Tools:
○​ AWS CLI/SDK.
○​ Azure REST API.
○​ Google Cloud API.

1. Version Control System (VCS):

●​ Definition: A tool that tracks changes in files or code, enabling collaboration, version
management, and rollback capabilities.
●​ Types:
○​ Centralized VCS: Single server stores all versions (e.g., SVN).
○​ Distributed VCS: Every user has a complete copy of the repository (e.g., Git).
●​ Key Features:
○​ Commit: Save changes to the repository.
○​ Branching: Create independent versions of code for parallel work.
○​ Merging: Combine changes from different branches.
○​ Rollback: Revert to previous versions in case of errors.
●​ Advantages:
○​ Simplifies collaboration among teams.
○​ Maintains a history of changes for audits or debugging.
○​ Facilitates continuous integration and delivery (CI/CD).
●​ Popular Tools: Git, Mercurial, Apache Subversion.

2. Containerization with Docker:

(See Docker explanation from above for general understanding)​

Key Advantages in Containerization:

●​ Isolation: Each container operates independently of others.

 ●​ Portability: Containers run consistently across different environments.
●​ Resource Efficiency: Containers share the host OS kernel, reducing overhead.
●​ How to Use Docker for Containerization:
1.​ Write a Dockerfile defining application dependencies.
2.​ Build a Docker image using docker build.
3.​ Run the image as a container using docker run.
4.​ Manage containers with Docker commands like docker ps, docker stop, etc.

3. GitHub:

●​ Definition: A web-based platform built on Git that provides version control and
collaboration features.
●​ Key Features:
○​ Repositories (Repos): Store code and track changes.
○​ Pull Requests: Allow team members to propose changes and request reviews.
○​ Actions: Automate workflows, such as CI/CD.
○​ GitHub Pages: Host static websites directly from a repository.
○​ Collaboration: Supports team discussions and issue tracking.
●​ Advantages:
○​ Simplifies team collaboration.
○​ Integrates with DevOps tools for CI/CD workflows.
○​ Provides backup and access to code from anywhere.

4. AWS (Amazon Web Services):

●​ Definition: A cloud platform offering on-demand computing resources and services.

●​ Key Services:
○​ Compute: Amazon EC2 (virtual servers), Lambda (serverless computing).
○​ Storage: S3 (object storage), EBS (block storage).
○​ Database: RDS (relational databases), DynamoDB (NoSQL).
○​ Networking: VPC (Virtual Private Cloud), Route 53 (DNS).
○​ Other Services: AI/ML, analytics, IoT, and DevOps tools.
●​ Advantages:
○​ Scalability: Adjust resources based on demand.
○​ Cost-Efficiency: Pay-as-you-go pricing.
○​ High Availability: Data centers worldwide ensure reliability.
●​ Use Cases:
○​ Hosting websites or applications.
○​ Big data analytics.
○​ Backup and disaster recovery.
5. Microservice Deployment:

●​ Definition: Microservices are small, independent services designed to perform specific

functions within an application. Deployment focuses on running and managing these
services.
●​ Key Principles:
○​ Independence: Each service can be developed and deployed independently.
○​ Scalability: Services can scale individually based on demand.
○​ Communication: Uses APIs (REST or gRPC) to communicate.
●​ Deployment Methods:
○​ Containers: Deploy services in Docker containers for isolation.
○​ Orchestration: Use Kubernetes or Docker Swarm to manage service clusters.
○​ Serverless: Deploy functions as a service using AWS Lambda or Azure
Functions.
●​ Benefits:
○​ Faster updates and deployments.
○​ Fault isolation – issues in one service don’t affect others.
○​ Easier to adopt new technologies for specific services.

6. Terraform:

●​ Definition: An Infrastructure as Code (IaC) tool that allows defining, deploying, and
managing infrastructure in a declarative language.
●​ Key Features:
○​ Declarative Syntax: Write infrastructure configurations in .tf files.
○​ Multi-Cloud: Supports multiple cloud providers (AWS, Azure, Google Cloud).
○​ State Management: Tracks the state of infrastructure in .tfstate files.
○​ Reusability: Allows creating reusable modules for repetitive configurations.
●​ How It Works:
○​ Write the infrastructure code.
○​ Use terraform init to initialize the working directory.
○​ Apply the code with terraform apply to deploy resources.
○​ Modify and update infrastructure using terraform plan and terraform
apply.
●​ Benefits:
○​ Automates infrastructure provisioning.
○​ Ensures consistency across environments.
○​ Facilitates collaboration using version control for infrastructure code.
7. Ansible:

●​ Definition: An open-source automation tool for configuration management, application

deployment, and task automation.
●​ Key Features:
○​ Agentless: Does not require software installation on managed nodes.
○​ Playbooks: YAML files containing automation instructions.
○​ Modules: Predefined tasks, such as installing packages or restarting services.
○​ Idempotency: Ensures repeated tasks have the same outcome.
●​ How It Works:
○​ Define tasks in a playbook.
○​ Use the Ansible command-line tool to execute the playbook on managed nodes.
○​ Ansible communicates with nodes over SSH.
●​ Benefits:
○​ Simplifies complex IT tasks.
○​ Saves time and reduces human error.
○​ Supports hybrid cloud environments.
●​ Use Cases:
○​ Automating server setup.
○​ Rolling out application updates.
○​ Orchestrating containerized environments.