0% found this document useful (0 votes)
17 views13 pages

Understanding Virtualization and Cloud Principles

Uploaded by

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

Understanding Virtualization and Cloud Principles

Uploaded by

SHAIK SAMEER
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Unit -01

Q1) Virtualization
Ans: -
 Virtualization refers to the partitioning the resources of physical system into multiple
virtual resources.
 Virtualization enables pooling of resources to serve multiple users using multi-tenancy
in cloud computing.
 Users are assigned virtual resources that run on top of the physical resources.

Types of Virtualizations: -
1. Hypervisor: -
 A hypervisor is software that creates and manages virtual machines.
 It allows multiple operating systems to run on a single physical machine by sharing
resources.
 It acts as a bridge between the hardware and the guest operating systems.
Types of Hypervisors: -
i. Type – 1 Hypervisor or Native Hypervisor
 It runs directly on the physical hardware (not inside an operating system).
 It manages the hardware and controls the guest operating systems
directly.
 Commonly used in data centers for better performance and efficiency.
 Ex : Citrix Xen Server, Oracle VM, KVM, VMWare ESX/ESXi (Elastic
Sky X) ,Hyper-V.
ii. Type – 2 Hypervisor or Hosted Hypervisor
 Hypervisor run on the top of the conventional operating
system and monitor the guest operating system.
 Ex: VMWare Workstation, Virtual Box.

 It is an operating system that is installed in a virtual machine


in addition to the host or main OS.
2. Full Virtualization:
 In this the virtualization layer completely decouples the guest OS from
the underlying hardware.
 The guest OS requires no modification and is not aware that it is being
virtualized.
 Full virtualization is enabled by direct execution of user requests and
binary translation of OS requests.

3. Hardware Virtualization:
 It uses special features built into computer chips to improve virtualization.
 Examples include Intel VT-x and AMD-V, which help virtual machines run faster
and more efficiently.
 In this privileged and sensitive calls are set to automatically trap to the hypervisor.

Unit – 02
Q1) 5-4-3 Principle of cloud computing
Ans: - The 5-4-3 principles of cloud computing by NIST describes: -
 the 5 essential characteristic features that promotes cloud computing,
 the 4 deployment models that are used to narrate cloud computing opportunities to customers
while looking at the architectural models and
 the 3 service offering models by cloud computing.

1. The Five essential characteristics:


Cloud Computing has five essential characteristics that are listed below:
i. On-demand self-service: -
 Users can get computing resources (like servers or storage) whenever they need them.
 No need to ask or wait for help from the service provider—it happens automatically.
ii. Broad Network access: -
 Cloud services can be used over the internet from anywhere.
 They work on different devices like phones, laptops, and tablets using standard access
methods.
iii. Elastic resource pooling: -
 Cloud providers share computing resources among many users, adjusting them based
on demand.
 Users don’t know the exact location of these resources but can choose general areas
like country or data center.
iv. Rapid Elasticity: -
 Cloud resources can quickly increase or decrease based on need, often automatically.
 To users, it feels like unlimited resources are always available and can be used anytime.
v. Measured Services: -
 Cloud systems track and manage how much of each resource (like storage or
bandwidth) is used.
 This helps both users and providers see usage clearly and optimize costs and
performance.
2. The Four Deployment Models:
 Deployment models describe the way with which the cloud services can be deployed or made
available to its customers.
 The four deployment models are usually distinguished namely, public, private, community and
hybrid cloud service usage:
i. Private Cloud: -
 A private cloud is used only by one organization, even if it has many departments.
 It can be managed by the organization itself, a third party, or both, and located
anywhere.
ii. Public Cloud: -
 A public cloud is available for anyone to use, like individuals or companies.
 It’s run by providers such as businesses or governments and located at their data center.
iii. Community Cloud: -
 A community cloud is shared by multiple organizations with common goals or needs.
 It can be managed by them or a third party, and located either locally or remotely.
vi. Hybrid Cloud: -
 A hybrid cloud combines two or more types of clouds (private, public, or community).
 They stay separate but work together using special technology to share data and apps
easily.
3. The Three Service Offering Models:
The three kinds of services with which the cloud-based computing resources are available to end
customers are: Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a
Service (IaaS).
i. Cloud Software as a Service (SaaS): -
 SaaS (software as Service) lets users access software over the internet without
managing servers or infrastructure.
 Apps run on the provider’s cloud and are available through browsers or app interfaces.
 Users can use the software but have limited control over its settings.
 Common examples include CRM tools, analytics platforms, and online accounting
software.
ii. Cloud Platform as a Service (PaaS): -
 PaaS (Platform as a Service) lets users build and run their own apps using tools provided
by the cloud vendor.
 Users control the apps but not the servers or infrastructure, which are managed by the
provider.
 The provider handles scalability, maintenance, and system resources.
 Examples include Google App Engine and Microsoft Azure Services.
iii. Cloud Infrastructure as a Service (IaaS): -
 IaaS (Infrastructure as a Service) lets users rent basic computing resources like storage,
servers, and networks.
 They can install and run their own software, including operating systems and apps.
 Users can install and run their own software but don’t manage the physical
infrastructure, which is handled by the provider.
 The cloud provider (like AWS) manages hardware, cooling, and maintenance.

Q2) Cloud Ecosystem


Ans: - A cloud ecosystem in cloud computing refers to a connected network of cloud services, tools,
applications, users, and providers that work together to deliver cloud-based solutions.

 It consists a central control server manages traffic and user requests in the cloud.
 It uses protocols (rules for communication) and middleware (special software) to help different
systems talk to each other.
 Middleware allows computers in the cloud to share data smoothly and efficiently.
 The Cloud ecosystem consists of three main actors they are: -
i. Cloud Service User (CSU): A person, company, app, or machine that uses cloud services.
ii. Cloud Service Provider (CSP): The company that offers and manages the cloud services.
iii. Cloud Service Partner (CSN): A helper organization that supports building and delivering
cloud services.

Working Of Cloud Ecosystem:

 A public cloud provider (like AWS or Salesforce) is the central part of the cloud ecosystem.
 Other tech companies build their services using the provider’s platform.
 Consultants and partner businesses connect with the provider to expand the ecosystem.
 Services from different providers can work together—there’s no strict vendor lock-in.
 For example, Salesforce uses AWS infrastructure and lets users access AWS tools like S3.
 This creates a flexible, connected environment where apps and data move easily across platforms.
Advantages: -

 Easily available on private or public clouds.


 Quick setup of development and testing tools to save time.
 Self-service access for managing users and resources.
 Pay only for what you use, with flexible capacity.
 Built-in security and compliance features.
 Access to a wide range of ready-to-use services.
 Fast provisioning to speed up the development cycle.

Benefits: -

 Cloud ecosystems make it easier to combine and analyze data from different sources.
 They help track trends, like patient health records or device logs, across large groups.
 Deployment models and readiness evaluations guide how cloud solutions are planned and
implemented.
 Use cases and scenarios help choose which tasks are best suited for the cloud.
 Architecture analysis ensures both data and applications are well-structured for cloud environments.
 A clear strategy and governance plan are important for successful cloud adoption.

Unit – 03
Q1) Cloud Architecture
Ans: -
1. Introduction: -
 Cloud Architecture refers to the overall design, structure, and components involved in
delivering cloud computing services over the Internet.
 It defines how cloud resources such as servers, storage, applications, databases, and
networking components are organized and interact to provide scalable, reliable, and on-
demand services to users.
 Cloud architecture ensures cloud systems are flexible, cost-efficient, secure, and capable of
handling large-scale computing needs.
2. Major Components of Cloud Architecture: -
i. Client Devices: -
 Client devices are the tools used by users to access cloud services.
 Examples include laptops, smartphones, tablets, and thin clients.
 They interact with the cloud through browsers, applications, or APIs.
 They act only as an interface and do not perform major processing or data storage.
ii. Frontend: -
 The front-end is the user-facing layer that allows users to interact with cloud
applications.
 It includes user interfaces, dashboards, web portals, mobile apps, and APIs.
 Examples include AWS Console, Google Cloud Console, Gmail front-end, and
Salesforce UI.
iii. Backend: -
 This is the core part of cloud architecture, controlled by cloud providers. It includes:
a) Servers & Virtual Machines: - Handle processing tasks and run cloud
applications.
b) Storage Systems: - Store user data, logs, files, backup, and media.
c) Databases: - Store structured and unstructured data.
d) Hypervisors / Virtualization: - Allow multiple virtual machines to run on one
physical machine.
e) Application Logic: - Executes cloud-based applications and services.
f) Security Components: - IAM, access control, encryption, firewalls.
g) Management Tools: - Monitoring, logging, auto-scaling, orchestration.
 The backend ensures:
a. Application execution.
b. Data Storage.
c. Resource Management.
d. Performance and reliability.
iv. Cloud Delivery Models (Service Models): -
 IaaS (Infrastructure as a Service): - Provides virtualized hardware resources like
compute, storage, and networks.
 Examples: AWS EC2, Google Compute Engine, Azure Virtual Machines
 PaaS (Platform as a Service): - Provides platforms and tools for developers
including OS, middleware, and runtime.
 Examples: - Google App Engine, Heroku, Azure App Services.
 SaaS (Software as a Service): - Provides ready-to-use software accessible through
the Internet.
 Examples: Gmail, Google Docs, Salesforce, Office 365
 These models help different users choose the right level of control and development
environment.
v. Cloud Network: -
 The cloud network includes Internet, VPC, VPN, Firewalls, Load Balancers, Routers,
and Switches.
 It enables secure communication and traffic routing.
3. Cloud Architecture Layers: -
 Application Layer (SaaS)
 Platform Layer (PaaS)
 Infrastructure Layer (IaaS)
 Kernel Layer
 Hardware Layer

4. Key Characteristics of Cloud Architecture: -


 Scalability
 Elasticity
 High Availability
 Fault Tolerance
 Multi-Tenancy
 On-Demand Service
 Pay-as-you-go Model
5. Conclusion: -
 Cloud Architecture provides a powerful design that supports scalable, flexible, and cost-
efficient operations.
 It enables high performance and global availability for modern applications.

Q2) Anatomy of Cloud Computing


Ans: -
 Cloud anatomy refers to the basic structure of the cloud system.
 It is not the same as cloud architecture, which includes both structure and dependencies.
 Architecture gives a complete, layered view of technologies used and how they depend on each
other.
 Anatomy is a subset of architecture, focusing only on the foundational layout.
 The level of detail in describing the cloud can vary depending on the person’s needs.
 A standard cloud anatomy model helps explain the base structure of cloud systems.
 There are basically five components of the cloud: -

1. Application: -
 The upper layer is the application layer.
 In this layer, any applications are executed.
2. Platform: -
 This component consists of platforms that are responsible for the execution of the application.
 This platform is between the infrastructure and the application.
3. Infrastructure: -
 The infrastructure consists of resources over which the other components work.
 This provides computational capability to the user.
4. Virtualization: -
 Virtualization is the process of making logical components of resources over the existing
physical resources.
 The logical components are isolated and independent, which form the infrastructure.
5. Physical hardware: -
 The physical hardware is provided by server and storage units.

Unit – 04
Q1) Cloud Deployment Models
Ans: -
1. Private Cloud
 Used by one single organization only → high security and full control.
 Can be on-premise or outsourced; costly to build & maintain.

 Best for companies needing privacy, autonomy, and have good budget.

Characteristics
 Exclusive use by one organization → very secure.
 Full central control over resources.

 Weak SLAs (internal agreements).

Types
 On-premise Private Cloud – hosted inside organization.
 Outsourced Private Cloud – hosted by third party.
Issues
 On-premise: strong security, easy management, low multitenancy risks.
 Outsourced: third-party risks, location/law issues, performance depends on provider.

Advantages
 High security & privacy.

 Full control by organization.


 Easier to maintain (small size).

Disadvantages
 High cost to build & maintain.

 Weak SLAs.
 Not suitable for large user base.

2. Public Cloud
 Open for general public use (e.g., AWS, Azure).
 Cheap, highly scalable, no maintenance required for users.

 Less secure; data is stored at provider’s location.

Characteristics
 Open to public; owned/operated by providers (AWS, Azure).
 Highly scalable, affordable, strict SLAs.
 Less secure (data shared across many users).

Types
 (No specific types mentioned in the PDF.)

Issues
 SLA management is complex due to many users.
 Network depends on Internet; provider not responsible for user-side issues.

 High multitenancy risks; data stored across countries → legal issues.

Advantages
 No infrastructure required.
 Low cost (pay-as-you-go).

 Highly scalable and available.

Disadvantages
 Low security & privacy.
 No autonomy for users.
 Provider controls everything.

3. Community Cloud
 Shared by multiple organizations with similar goals (e.g., banks, govt groups).

 Cost and responsibilities are shared, more secure than public cloud.
 Requires cooperation among organizations.

Characteristics
 Shared by multiple organizations with common goals.

 Collaborative maintenance; partially secure.


 Costs and responsibility shared.

Types
 On-premise Community Cloud – maintained collectively.
 Outsourced Community Cloud – managed by a provider.

Issues
 On-premise: coordination needed, moderate multitenancy risks.

 Outsourced: third-party risks, legal issues across countries.

Advantages
 Cheaper alternative to private cloud.
 Shared responsibility.
 More secure than public cloud.

Disadvantages
 Less secure than private cloud.
 Requires cooperation among organizations.

 Loss of autonomy.

4. Hybrid Cloud
 Combination of two or more clouds (private + public).
 Gives both security (private) + scalability (public).

 Complex to manage; security risk exists due to public part.

Characteristics
 Mix of private + public + community clouds.
 Provides scalability (public) + security (private).

 Complex management; strict SLAs.

Types
 (Not divided into types; model itself is a combination.)

Issues
 SLAs vary (strict public + weak private).

 More security risks due to public part.


 Complex network, legal, and management challenges.

Advantages
 Combines strengths of private & public.

 Highly scalable.
 More secure than public cloud alone.

Disadvantages
 Less secure than private cloud.
 Complex and expensive to manage.

 Strict SLAs and mixed environments.


Q2) Cloud Service Models

Ans: -

i. IaaS (Infrastructure as a Service)


 Provides virtual machines, storage, networks on rent.
 Users control OS & applications; provider manages infrastructure.
 Flexible, scalable, and pay-as-you-use.

Characteristics
 Provides servers, storage, networks, VMs on rent.
 Web-based access; elastic & scalable.

 Pay only for usage.

Advantages
 No upfront cost; scalable.
 Better resource utilization.

 Supports green IT.

Disadvantages
 Security risks (hypervisor attacks).
 Vendor lock-in.

 Performance affected by latency.

2. PaaS (Platform as a Service)


 Provides complete development environment (tools, runtime, database).

 Developers build & deploy apps without handling servers.


 Fast development, supports teamwork, but causes vendor lock-in.

Characteristics
 Complete development environment (tools, runtime, DB).

 Supports teamwork, automated scaling, web-based access.


 Fast testing & deployment.

Advantages
 Faster development (Agile).

 Reduces cost (no tools needed).


 Low maintenance, easy to use.

Disadvantages
 Vendor lock-in.
 Less flexibility vs IaaS.

 Security concerns (off-premise storage).

3. SaaS (Software as a Service)


 Ready-made software delivered over the internet (e.g., Gmail, Office 365).
 No installation; used via browser with subscription/pay-per-use.
 Easy to access but limited customization.

Characteristics
 Ready-made software delivered online (no installation).
 Access via browser; subscription/pay-per-use.

 Provider manages everything.

Advantages
 No installation required.
 Cheapest & easiest for users.

 Accessible from anywhere.

Disadvantages
 Limited customization.
 Privacy/security risks.

 Full dependence on provider.

You might also like