KEMBAR78
S017 - Assignment 1&2 | PDF | Virtualization | Virtual Machine
0% found this document useful (0 votes)
20 views9 pages

S017 - Assignment 1&2

Uploaded by

Fardeen Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views9 pages

S017 - Assignment 1&2

Uploaded by

Fardeen Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Name – Fardeen Patel

Roll no – S017
SAP Id - 70522200078
Class – MBA Tech Data Science

Assignment 1&2

Q1) Explain the Concept of Virtualization Along with Their Types, Mechanisms, and
Implementation Levels

1. Introduction to Virtualization

• What is Virtualization?
• Virtualization is the creation of a virtual (rather than actual) version of
something, such as operating systems, servers, storage devices, or network resources. It
allows a single physical machine to run multiple virtual environments or operating systems
simultaneously.
• Importance of Virtualization in Cloud Computing:
• Key enabler of cloud computing because it helps maximize hardware resource
utilization.
• Reduces IT costs by allowing multiple applications and users to share the
same physical infrastructure.

2. Types of Virtualization

• Hardware Virtualization:
• Full Virtualization: The guest OS runs unmodified and believes it has full
control of the hardware. Examples include VMware ESXi and Microsoft Hyper-V.
• Para-Virtualization: Guest OS is aware it is virtualized and interacts with the
hypervisor directly for better performance. Used in Xen.
• Hardware-Assisted Virtualization: Uses CPU features like Intel VT-x or AMD-
V to improve the efficiency of full virtualization.
• Example: VMware Workstation uses full virtualization to run different OSs on
a single physical machine.
• OS-Level Virtualization (Containers):
• Lightweight virtualization where multiple containers run isolated instances on
a single OS kernel.
• Examples: Docker, Kubernetes.
• Application Virtualization:
• Applications are decoupled from the underlying OS, allowing them to run in
isolated environments.
• Examples: Citrix Virtual Apps, Microsoft App-V.
• Desktop Virtualization:
• Allows users to run desktop environments remotely.
• Examples: VMware Horizon, Citrix Virtual Desktops.
• Network Virtualization:
• Virtualizes network resources such as firewalls, switches, and load balancers.
• Example: VMware NSX, Cisco ACI.
• Storage Virtualization:
• Pools physical storage from multiple devices to appear as a single storage
device.
• Example: IBM Spectrum Virtualize.

3. Virtualization Mechanisms

• Hypervisor:
• The core component that manages virtual machines (VMs).
• Type 1 Hypervisors: Run directly on the physical hardware (bare-metal).
Examples: VMware ESXi, Microsoft Hyper-V.
• Type 2 Hypervisors: Run on top of an existing operating system. Examples:
Oracle VirtualBox, VMware Workstation.
• Virtual Machine Monitor (VMM):
• Component that provides an abstraction of the physical hardware.
• Containerization vs Virtualization:
• Containers share the OS kernel but isolate applications. They are lightweight
compared to traditional VMs.
• Virtual Machines emulate an entire operating system.

4. Levels of Virtualization Implementation


• Operating System Level:
• Examples: Linux containers (LXC), Docker.
• Virtualization at this level is generally lightweight and ideal for cloud-native
applications.
• Application Level:
• Examples: Java Virtual Machine (JVM), .NET Common Language Runtime
(CLR).
• Applications are abstracted from the underlying hardware but not the entire
OS.
• Hardware Level:
• Virtualization techniques directly interact with hardware (via hypervisors).
Example: VMware ESXi.
• Network Level:
• Software-Defined Networking (SDN) virtualizes the entire networking layer.
• Example: OpenStack Neutron.

Q2) What is EC2? Explain the Lifecycle of EC2, Along with Its Types, Images, and
Security Groups.

Introduction to EC2

• Definition:
• Amazon EC2 (Elastic Compute Cloud) is a web service that provides resizable
compute capacity in the cloud.
• Features:
• On-demand instances, pay-as-you-go pricing, and various instance types for
different use cases.
• Allows businesses to run applications without purchasing physical servers.

2. EC2 Lifecycle

• Instance Launch:
• Starts when a user selects an Amazon Machine Image (AMI) and the desired
instance type. Key attributes such as storage, security groups, and networks are configured.
• Running State:
• The EC2 instance is running and can execute applications.
• Users can connect via SSH for Linux instances or RDP for Windows
instances.
• Stopping/Restarting:
• Stopping an instance retains the instance data, but halts its operation.
Restarting brings it back online.
• Hibernation:
• Saves the instance state and data to disk and powers off the machine, allowing
quick restarts.
• Termination:
• Permanently deletes the instance and all associated data unless specified
otherwise.
3. EC2 Instance Types

• General Purpose:
• Instances that provide a balance between compute, memory, and networking
resources. Examples: t3.micro, m5.large.
• Compute Optimized:
• For CPU-bound applications. Examples: c5.large, c6g (ARM-based).
• Memory Optimized:
• For applications that need a lot of RAM. Examples: r5.large, x1e.32xlarge.
• Storage Optimized:
• Optimized for I/O-intensive tasks like databases. Examples: i3.large,
d2.xlarge.
• Accelerated Computing:
• For GPU-based workloads like AI/ML. Examples: p3.large, g4dn.xlarge.

4. EC2 Images (AMIs)

• Definition:
• AMI is a template that contains a software configuration (OS, application
server, etc.).
• Types of AMIs:
• Pre-built AMIs: Provided by AWS or third parties (e.g., Linux, Windows, Red
Hat).
• Custom AMIs: Users can create their own AMIs to replicate software
environments.

5. EC2 Security Groups

• Security Groups:
• Virtual firewalls that control inbound and outbound traffic for instances.
• Configuration:
• Rules are set up to allow or deny specific IPs, protocols (e.g., SSH, HTTP),
and ports.
• Default Settings:
• By default, all inbound traffic is blocked, and outbound traffic is allowed.

Q3) Compare and Contrast All the Types of Storages Supported by AWS Along With
Their Comparison With MS Azure, Google Cloud Platform, and OCI.

1. Introduction to AWS Storage Services

• Overview:
• AWS offers a broad range of storage services including object, block, and file
storage to cater to various needs.
• Key Advantage: Scalability and integration with other AWS services.

2. AWS Storage Types

• S3 (Simple Storage Service):


• Scalable object storage for any amount of data.
• Use Cases: Data lakes, backups, and media storage.
• EBS (Elastic Block Store):
• Persistent block storage for EC2 instances.
• Use Cases: Databases, transactional workloads.
• EFS (Elastic File System):
• Fully managed file storage for EC2 instances.
• Use Cases: Shared access to large datasets across multiple EC2 instances.
• Glacier:
• Archival storage for long-term backups.
• Use Cases: Archiving rarely accessed data with cost optimization.

3. Azure Storage Comparison

• Azure Blob Storage:


• Equivalent to S3, provides scalable object storage.
• Azure Managed Disks:
• Equivalent to EBS, used for block storage with virtual machines.
• Azure Files:
• Similar to EFS, used for file sharing between applications and VMs.
• Azure Archive:
• Equivalent to Glacier, used for long-term cold storage.

4. Google Cloud Storage Comparison

• Google Cloud Storage:


• Similar to S3, providing object storage.
• Persistent Disk:
• Block storage solution similar to EBS.
• Filestore:
• Network-attached file storage similar to EFS.
• Coldline Storage:
• Archival storage solution similar to Glacier.

5. OCI Storage Comparison

• OCI Object Storage:


• Similar to S3 for object storage.
• Block Volumes:
• Block storage similar to EBS.
• File Storage:
• File system storage similar to EFS.

6. Comparison Table
Q4) Explain Different Types of SQL and No-SQL Databases Supported by AWS, Azure,
and Google Cloud Platform.

1. SQL Databases

• AWS:
• RDS (Relational Database Service): Supports MySQL, PostgreSQL, Oracle,
SQL Server.
• Aurora: A highly available, scalable database service that is compatible with
MySQL and PostgreSQL.
• Azure:
• Azure SQL Database: Fully managed relational database with built-in high
availability.
• Azure Database for MySQL/PostgreSQL: Managed database solutions for
MySQL and PostgreSQL.
• GCP:
• Cloud SQL: Fully managed MySQL, PostgreSQL, and SQL Server instances.

2. NoSQL Databases

• AWS:
• DynamoDB: NoSQL key-value and document database with single-digit
millisecond performance.
• DocumentDB: MongoDB-compatible managed NoSQL database service.
• Azure:
• Cosmos DB: Globally distributed, multi-model NoSQL database service with
support for key-value, graph, and document data models.
• GCP:
• Bigtable: Scalable NoSQL database for large analytical and operational
workloads.
• Firestore: Flexible, scalable NoSQL database for mobile, web, and server
development.

3. SQL vs NoSQL Comparison

• SQL: Structured data with predefined schemas, supports complex queries


(joins, transactions).
• Use Cases: Traditional applications, ERP, CRM.
• NoSQL: Flexible schemas, designed for scalability and distributed data
models.
• Use Cases: Big data, real-time analytics, IoT.

4. Cloud-Specific Features

• AWS Aurora: Automatic scaling, self-healing storage, and fault-tolerant across


multiple AZs.
• Azure Cosmos DB: Guarantees low-latency, multi-region writes and reads
with global distribution.
• GCP BigQuery: A serverless, highly scalable, multi-cloud data warehouse with
built-in machine learning.
Q5) Explain Concept of CloudFormation, Lambda, Snowball (Edge Computing
Platform), and Redshift Services with Respect to AWS.

1. AWS CloudFormation

• Definition:
• Infrastructure as code (IaC) service that allows users to define and provision
AWS infrastructure through JSON or YAML templates.
• Use Case:
• Automating the deployment of multiple AWS services (e.g., EC2, S3, RDS)
without manual configuration.
• Example:
• Deploying a multi-tier web application with a load balancer, EC2 instances,
and an RDS database using a single CloudFormation template.

2. AWS Lambda
• Definition:
• Serverless compute service that lets you run code without provisioning or
managing servers.
• Use Case:
• Event-driven execution, such as running functions in response to S3 bucket
uploads or DynamoDB changes.
• Example:
• Running a thumbnail generator when images are uploaded to an S3 bucket.

3. AWS Snowball (Edge Computing)

• Definition:
• Physical device and service used for secure data transfer to AWS. Supports
edge computing for remote or disconnected environments.
• Use Case:
• Transferring large volumes of data to AWS without network congestion, or
running local compute jobs in remote areas.
• Example:
• A media company using Snowball to migrate petabytes of video data to AWS.

4. AWS Redshift

• Definition:
• A fully managed data warehouse service designed for large-scale analytics.
• Use Case:
• Performing analytics on terabytes to petabytes of structured and semi-
structured data, such as for business intelligence and reporting.
• Example:
• A retail company analyzing sales data for trend detection and forecasting using
Redshift.

You might also like