CC MODULE 3

1. EXPLAIN INFRASTRUCTURE OR H/W AS SERVICES.

IaaS/HaaS provides customizable infrastructure on demand, ranging from single servers to entire systems,
including networks, databases, and web servers.

1. Technology:
a. Based on hardware virtualization, where virtual machines (VMs) form the building blocks.
b. VMs are configured with specific features like memory, processors, and storage.
2. Benefits:
a. For Providers: Efficient use of IT infrastructure and secure environments for running third-party
applications.
b. For Customers: Reduced hardware costs, lower maintenance needs, and full customization of
infrastructure.
3. VM Customization:
a. Users can configure VMs with required software and operating systems.
b. Prepackaged system images (e.g., web servers, LAMP stacks) are also available.
4. Additional Services:
a. Resource allocation based on Service Level Agreements (SLAs).
b. Workload management, infrastructure design tools, and integration with third-party IaaS.
5. Three Layers in IaaS Architecture:
a. Physical Infrastructure: Hardware resources like datacenters, clusters, or PCs.
b. Software Management: Handles VM scheduling, billing, monitoring, and SLA management.
c. User Interface: Web portals, APIs, or applications for accessing and managing services.

6. Key Software Management Components:

a. Scheduler: Allocates VMs to physical resources.
b. Billing: Calculates usage costs.
 c. Monitoring: Tracks VM performance.
d. VM Repository: Stores and provides VM images.
e. Provisioning: Integrates resources from external IaaS providers.
7. Scenarios:
a. Large service providers like Amazon or Rackspace use massive datacenters for public cloud
IaaS.
b. Small enterprises or universities may rely on local clusters or grids.
8. Hybrid Solutions: Some solutions integrate private infrastructures with third-party services, offering
only management and user interfaces.
9. Applications: Commonly used for computing resources, but the architecture also supports storage
virtualization with similar layers.

2. EXPLAIN PUBLIC, PRIVATE, & HYBRID CLOUDS

Public Clouds:

1. Definition: Public clouds are accessible to anyone via the internet and offer services on demand, such as
infrastructure, platforms, or applications.
2. Structure: They consist of distributed systems, typically using multiple datacenters to provide services.
3. Use Cases: Ideal for small businesses to avoid large upfront costs and to scale IT resources up or down
as needed. Used to completely replace or extend existing IT infrastructure.
4. Key Feature: Multitenancy: Multiple users share the cloud infrastructure but have isolated
environments.
5. Advantages: Cost-effective, scalable, and capable of handling peak loads dynamically.
6. Examples: Amazon EC2 (Infrastructure as a Service), Google AppEngine (Platform as a Service), and
SalesForce.com (Software as a Service).
7. Geographical Scalability: Datacenters are often globally distributed, enabling better service based on
user locations (e.g., AWS regions like us-east-1 and eu-west-1).

Private Clouds:

1. Definition: Private clouds operate within an organization's boundaries, providing IT services

exclusively to internal users.
2. Security: Sensitive data stays within the organization, reducing risks and ensuring compliance with
regulations.
3. Control: Organizations retain full control over their infrastructure and data.
4. Infrastructure: Built using existing IT resources like datacenters, clusters, or desktop grids, combined
with virtualization technologies (e.g., Xen, VMware).
5. Use Cases: Ideal for organizations needing strict control over data, such as government or military
agencies.
6. Advantages: Enables better utilization of existing resources, supports internal testing, and ensures
compliance with organizational policies.
7. Examples of Software: VMware vCloud, Eucalyptus, OpenNebula for infrastructure management, and
Aneka for application execution.

Hybrid Clouds:
 1. Definition: Hybrid clouds combine private and public cloud infrastructures, enabling data and
application sharing between them.
2. Structure: A heterogeneous distributed system that integrates private IT infrastructure with public cloud
services.
3. Use Cases: Ideal for enterprises needing to maintain sensitive data on-premises while scaling resources
dynamically during peak demands.
4. Key Feature: Dynamic provisioning enables temporary leasing of public cloud resources to handle
excess workloads.
5. Advantages: Offers the flexibility of private clouds with the scalability and cost-efficiency of public
clouds.
6. Examples: Solutions like OpenNebula (integrates public cloud resources), Aneka (dynamic
provisioning with QoS), and cloudbursting scenarios.
7. Geographical Scalability: Resources can be extended globally through public cloud datacenters while
keeping sensitive data localized in private setups.

3. OPEN CHALLENGES

1. Cloud Definition:
a. Despite widespread adoption, there is no universally accepted definition of cloud computing.
This lack of clarity creates confusion for users, businesses, and researchers about what
constitutes a cloud service.
b. The challenge lies in the diversity of cloud models (public, private, hybrid) and services (IaaS,
PaaS, SaaS) that overlap with traditional computing systems.
c. This ambiguity hampers standardization and uniform expectations across the industry.
2. Cloud Interoperability and Standards:
a. Cloud interoperability refers to the ability to move workloads seamlessly across different cloud
providers or environments.
b. Challenges:
i. Lack of standard APIs and protocols makes integration across different platforms
difficult.
ii. Proprietary technologies by providers like AWS, Azure, and Google Cloud lead to
vendor lock-in, limiting flexibility.
c. Impact: Organizations face difficulties in multi-cloud strategies, migrating workloads, or
creating distributed systems using multiple providers.
3. Scalability and Fault Tolerance:
a. Cloud systems must handle rapid changes in workload, ensuring they scale up or down as needed
while maintaining reliability.
b. Challenges:
i. Elasticity can lead to resource contention or underutilization during peak demands.
ii. Building fault-tolerant systems to ensure continuity in case of hardware or software
failures is complex.
c. Example: Applications like e-commerce platforms require high scalability during sales events
and fault tolerance to prevent downtime.
4. Security, Trust, and Privacy:
a. Storing sensitive data on cloud platforms introduces risks such as unauthorized access, data
breaches, and insider threats.
b. Challenges:
 i. Lack of transparency from providers about security measures.
ii. Compliance with data protection regulations like GDPR, HIPAA, etc.
iii. Trust issues arise when organizations feel they lose control over their data.
c. Example: Data breaches like the Capital One incident highlight vulnerabilities in cloud storage
and configurations.
5. Organizational Aspects:
a. Transitioning to cloud environments affects organizational workflows, cost structures, and
expertise.
b. Challenges:
i. Resistance to change among employees due to a lack of training or understanding of
cloud technologies.
ii. Cost management issues arise due to unexpected bills from dynamic resource usage.
iii. Aligning cloud adoption with business goals and ensuring ROI can be difficult.
c. Example: Organizations need to retrain IT teams to manage cloud services effectively instead of
traditional on-premises infrastructure.

4. CLOUD COMPUTING ARCHITECTURE

Cloud computing architecture can be visualized as a layered stack, starting from the underlying physical
hardware to high-level application services delivered to end users. Each layer in this architecture serves a
specific purpose, providing an organized way to deploy, manage, and utilize cloud services.

Cloud Resources (System Infrastructure Layer)

• Foundation layer with physical servers, storage, and networking devices.
• Virtualization partitions resources like CPU and memory into virtual units.
• Datacenters host thousands of interconnected nodes for computing power.
• Enables storage and network virtualization for flexibility.
• Acts as the base for building all other cloud services.
2. Core Middleware
• Manages infrastructure and provides runtime environments for applications.
• Handles tasks like SLA management, billing, and resource monitoring.
• Supports APIs for developers to access virtualized resources.
• Essential for implementing IaaS solutions.
• Ensures efficient utilization of cloud resources.
3. Cloud Hosting Platforms
• Provides platforms for hosting and managing applications.
• Offers tools for pricing, execution management, and dynamic scaling.
• Combines physical infrastructure with resource management layers.
• Forms the backbone of IaaS solutions.
• Facilitates seamless application hosting and scaling.

4. Cloud Programming Environments and Tools (PaaS)

• Offers a platform for developing cloud-based applications.
• Includes APIs, web interfaces, and programming tools like Java or Python.
• Developers use it to build applications without managing the underlying infrastructure.
• Ensures portability and scalability for cloud-native apps.
• Simplifies the development process through middleware services.

5. Cloud Applications (SaaS)

• Delivers software directly to users over the internet.
• Includes web-based tools like CRM, email, and productivity apps.
• Dynamically scales services based on user demand.
• Enables users to access applications without installation.
• Ideal for businesses requiring scalable, subscription-based solutions.

6. Adaptive Management Layer

• Ensures elasticity by scaling resources based on demand.
• Provides APIs for developers to integrate fault tolerance.
• Automatically handles resource allocation for SaaS applications.
• PaaS and IaaS layers expose these features for custom scaling.
• Enables cloud services to adapt dynamically to workload changes.

7. Everything-as-a-Service (XaaS)
• Combines services across layers for integrated solutions.
• Reduces upfront IT costs by providing virtual resources on demand.
• Supports custom deployments like web farms with load balancers.
• Allows startups to grow IT infrastructure as revenue increases.
• Delivers end-to-end computing solutions using a mix of cloud layers.