Unit5 - Subjective Questions

Definition:
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

Five Essential Characteristics:

1. On-demand Self-service: A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider.
2. Broad Network Access: Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations).
3. Resource Pooling: The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand.
4. Rapid Elasticity: Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand.
5. Measured Service: Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts).

In the context of Cloud Computing, the shift from CapEx to OpEx is a primary driver for adoption.

Conclusion: Cloud computing shifts IT spending from CapEx to OpEx, allowing businesses to reduce upfront risks and align spending with actual usage.

Cloud computing services are categorized into three distinct models, often referred to as the SPI model (SaaS, PaaS, IaaS).

1. Infrastructure as a Service (IaaS)

• Description: Provides fundamental computing resources such as virtualized servers, storage, and networking over the internet. The consumer manages the operating system, applications, and data, while the provider manages the physical hardware and virtualization layer.
• Key Features: Scalability, dynamic workloads, and control over infrastructure.
• Examples: Amazon Web Services (AWS) EC2, Google Compute Engine (GCE), Microsoft Azure Virtual Machines.

2. Platform as a Service (PaaS)

• Description: Provides a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure associated with developing and launching an app. It includes the OS, middleware, and runtime environment.
• Key Features: Focus on code, faster time to market, and built-in scalability.
• Examples: Google App Engine, AWS Elastic Beanstalk, Heroku, Microsoft Azure App Service.

3. Software as a Service (SaaS)

• Description: Delivers software applications over the internet, on a subscription basis. The cloud provider hosts and manages the software application and underlying infrastructure, and handles any maintenance, like software upgrades and security patching.
• Key Features: No installation required, accessible from anywhere, and vendor-managed updates.
• Examples: Google Workspace (Gmail, Docs), Microsoft 365, Salesforce, Dropbox.

Summary:

• IaaS: Host it.
• PaaS: Build it.
• SaaS: Consume it.

Public Cloud vs. Private Cloud

1. Public Cloud:

• Description: Infrastructure is owned and operated by a third-party cloud service provider and delivered over the public internet.
• Access: Available to the general public or a large industry group.
• Cost: Low upfront cost (OpEx); pay-per-use.
• Security: High, but distinct risk due to multi-tenancy (shared resources).
• Scalability: Unlimited elasticity ( theoretical limit).
• Example: AWS, Azure, Google Cloud.

2. Private Cloud:

• Description: Cloud computing resources used exclusively by a single business or organization. It can be physically located at the company's on-site data center or hosted by a third-party service provider.
• Access: Restricted to the specific organization via a private network.
• Cost: High upfront cost (CapEx) for hardware if on-premise, or higher hosting fees.
• Security: Maximum security and control; ideal for sensitive data.
• Scalability: Limited by the hardware owned or leased.
• Example: OpenStack deployed on company servers, VMware vSphere.

Key Difference: The trade-off is between control/security (Private) and cost/scalability (Public).

Virtualization:
Virtualization is the fundamental technology powering cloud computing. It creates a simulated, or "virtual," version of something, such as an operating system, a server, a storage device, or network resources.

• Function: It allows a single physical machine to run multiple virtual machines (VMs) simultaneously. Each VM acts as an independent computer with its own operating system and applications.
• Benefit: It maximizes the utilization of physical hardware. Instead of a server running at 15% capacity, virtualization allows it to run at 80-90% by hosting multiple workloads.

The Role of a Hypervisor:
A Hypervisor (or Virtual Machine Monitor - VMM) is the software layer that creates and runs virtual machines.

• Resource Allocation: It sits between the physical hardware and the VMs, allocating computing resources (CPU, RAM, Storage) dynamically to each VM.
• Isolation: It ensures that VMs are isolated from one another; if one VM crashes, the others are unaffected.

Types of Hypervisors:

1. Type 1 (Bare Metal): Runs directly on physical hardware (e.g., VMware ESXi, Microsoft Hyper-V).
2. Type 2 (Hosted): Runs as an application inside an OS (e.g., VMware Workstation, Oracle VirtualBox).

Hybrid Cloud Definition:
A Hybrid Cloud is a computing environment that combines a public cloud and a private cloud by allowing data and applications to be shared between them. It connects the two environments via an encrypted connection/VPN, allowing for orchestration.

Advantages:

1. Flexibility & Control: Organizations can keep sensitive data on their secure private cloud (e.g., financial records) while using the public cloud for less sensitive, high-volume data (e.g., marketing content).
2. Cloud Bursting: If the private cloud reaches capacity limits during a spike in demand (e.g., Black Friday sales), traffic can "burst" over to the public cloud to handle the excess load without service interruption.
3. Cost Optimization: Reduces capital expenditure by utilizing the public cloud for temporary workloads rather than purchasing permanent infrastructure for peak demand.
4. Compliance: Helps meet regulatory requirements by keeping specific data on-premise while still leveraging cloud scalability.

Relationship:
Data Analytics involves inspecting, cleansing, and modeling data to discover useful information. Cloud computing provides the underlying infrastructure required to perform these tasks at scale. They are mutually beneficial: Cloud provides the storage and compute power, while Analytics provides the value from the data stored in the cloud.

How Cloud Enables Big Data Processing:

1. Scalable Storage: Big Data generates terabytes or petabytes of data. Cloud storage services (like Amazon S3 or Google Cloud Storage) offer virtually unlimited, low-cost storage that scales automatically.
2. Parallel Processing: Processing Big Data requires massive compute power. Cloud platforms offer clusters of servers that can process data in parallel (using frameworks like MapReduce or Spark), reducing processing time from days to minutes.
3. Cost-Efficiency: Traditional data warehouses require expensive hardware. Cloud analytics allows companies to spin up thousands of processors for a few hours to run a complex query and then shut them down, paying only for the time used.
4. Tools and Services: Cloud providers offer managed analytics services (e.g., AWS EMR, Google BigQuery, Azure Synapse) that simplify the deployment of complex analytics pipelines without managing servers.

Community Cloud Definition:
A Community Cloud is a collaborative cloud deployment model where the infrastructure is shared between several organizations from a specific community with common concerns (e.g., security, compliance, jurisdiction, mission). It can be managed by the organizations themselves or a third party and can exist on-premise or off-premise.

Key Characteristics:

• Shared Costs: Costs are spread among fewer users than a public cloud but more than a private cloud.
• Shared Security/Compliance: All tenants adhere to the same regulatory standards.

Example Scenario:

• Banking/Finance: Several banks might form a community cloud to host a shared trading application that must meet specific and rigorous government financial regulations.
• Healthcare: Hospitals in a specific region might share a community cloud to manage patient records securely, ensuring all entities comply with health data privacy laws (like HIPAA) while sharing research data.

As cloud adoption grows, specialized job roles have emerged. Major roles include:

1. Cloud Architect:
   • Responsible for the overall design and strategy of the cloud environment.
   • They decide which cloud services to use and how to structure the application for reliability and scalability.
2. Cloud Engineer:
   • Focuses on the implementation, maintenance, and support of cloud services.
   • They handle the technical duties of migrating applications to the cloud and managing the infrastructure.
3. Cloud Security Specialist:
   • Ensures the integrity and security of cloud data.
   • They implement firewalls, encryption, and IAM (Identity and Access Management) policies to protect against breaches.
4. Cloud DevOps Engineer:
   • Combines development and operations.
   • They use tools to automate the deployment pipeline (CI/CD) and manage cloud infrastructure using code (Infrastructure as Code).
5. Cloud Administrator:
   • Manages the day-to-day operations of cloud networks, ensuring uptime, monitoring performance, and managing user access.

To succeed in cloud computing, a professional requires a mix of technical and soft skills:

Technical Skills:

1. Cloud Platform Knowledge: Proficiency in at least one major provider (AWS, Azure, or Google Cloud Platform).
2. Linux/OS Skills: Understanding of Operating Systems, particularly Linux, as most cloud servers run on Linux distributions.
3. Networking: Knowledge of DNS, TCP/IP, HTTP, VPNs, and software-defined networking (SDN).
4. Programming/Scripting: Skills in languages like Python, Java, or Node.js for application development, and Bash/PowerShell for automation.
5. DevOps & Containerization: Familiarity with Docker (containers), Kubernetes (orchestration), and CI/CD tools (Jenkins, GitLab).
6. Database Management: Understanding of SQL (RDS) and NoSQL (DynamoDB, MongoDB) databases in a cloud context.

Soft Skills:

• Problem-solving and adaptability (technologies change fast).
• Business acumen (understanding cost implications of technical decisions).

Cloud computing is utilized across various domains in application services:

1. File Storage and Sharing:
   • Services like Dropbox, Google Drive, and OneDrive allow users to store files remotely and access them from any device. It enables synchronization and collaboration.
2. Backup and Disaster Recovery (DR):
   • Cloud offers a cost-effective way to replicate data off-site. In the event of a physical disaster at a company's office, data can be restored from the cloud quickly, ensuring business continuity.
3. Web and Mobile Hosting:
   • Cloud platforms host websites and mobile app backends. They handle traffic spikes automatically (auto-scaling) so that websites don't crash during high usage.
4. Software Development and Testing:
   • Developers can instantly spin up test environments on the cloud, run tests, and tear them down. This reduces the time and cost of procuring physical test servers.
5. Big Data Analytics:
   • Organizations use the cloud to store massive datasets (Data Lakes) and run analytics tools to derive business insights (e.g., analyzing customer behavior).
6. Communication and Collaboration:
   • Tools like Zoom, Slack, and Microsoft Teams run entirely on the cloud, facilitating remote work.

Implementing and managing cloud environments requires specific tools and techniques:

1. Virtualization Tools:

• VMware vSphere / ESXi: Industry-standard tools for server virtualization.
• Microsoft Hyper-V: Virtualization platform for Windows environments.
• KVM (Kernel-based Virtual Machine): Open-source virtualization for Linux.

2. Containerization Tools:

• Docker: Allows packaging applications into portable containers that include all dependencies (code, runtime, libraries).
• Podman: An alternative to Docker for managing containers.

3. Orchestration Tools:

• Kubernetes: The standard for automating deployment, scaling, and management of containerized applications.
• Docker Swarm: Native clustering for Docker.

4. Infrastructure as Code (IaC):

• Terraform: An open-source tool to define and provision data center infrastructure using a high-level configuration language.
• Ansible: Automation tool for configuration management and application deployment.

5. Cloud Management Platforms:

• OpenStack: A free, open standard cloud computing platform for building public and private clouds.

While often used interchangeably, these terms have distinct meanings in cloud architecture.

Despite its benefits, cloud computing introduces specific security challenges:

1. Data Breaches: Since data is stored on third-party servers accessible via the internet, it is a target for hackers. Weak authentication or vulnerabilities in the provider's infrastructure can lead to leaks.
2. Data Privacy and Sovereignty: Storing data in the cloud means it may physically reside in a different country with different laws. This creates compliance issues (e.g., GDPR) regarding who can access the data.
3. Insecure APIs: Cloud providers expose a set of software user interfaces (APIs) to manage and interact with cloud services. If these APIs are not secure, attackers can manipulate the cloud environment.
4. Insider Threats: Malicious employees at the cloud provider or the client organization usually have authorized access to the network, making detection difficult.
5. Shared Technology Issues: In IaaS, hardware is shared. Vulnerabilities in the hypervisor (like "VM escape" attacks) could potentially allow a user on one VM to access data on another VM on the same physical host.
6. Account Hijacking: If a hacker gains access to a cloud administrator's credentials (via phishing), they can manipulate the entire infrastructure.

Cloud computing architecture is divided into two main parts: the Front-end and the Back-end, connected via a network (Internet).

1. Front-end:

• Client Side: This is the side visible to the client or user.
• Components: It includes the client's computer network (or mobile device) and the application required to access the cloud system.
• Interface: It can be a web browser (for SaaS like Gmail) or a specific client interface/app.

2. Back-end:

• Server Side: This is the "Cloud" itself, managed by the service provider.
• Components:
  • Servers & Storage: Massive amounts of data storage and computing power.
  • Virtualization: Software to create virtual instances.
  • Service: The specific utility provided (SaaS, PaaS, IaaS).
  • Security: Mechanisms to protect the data.
  • Management/Traffic Control: Middleware that coordinates the traffic, ensuring requests from the front-end are handled by the correct resources in the back-end.

Summary: The Front-end sends requests, and the Back-end executes the logic, retrieves data, and sends the response back.

Definition:
OpenStack is a free, open-source cloud computing platform. It is primarily deployed as an Infrastructure-as-a-Service (IaaS) solution. It consists of a set of interrelated software components that control diverse, multi-vendor hardware pools of processing, storage, and networking resources throughout a data center.

Significance:

1. Building Private Clouds: OpenStack is the standard tool for organizations that want to build their own private cloud on-premise, giving them the elasticity of AWS but with total control over the hardware.
2. Modularity: It is composed of separate components (projects) like Nova (compute), Swift (object storage), Neutron (networking), and Horizon (dashboard). Users can install only the components they need.
3. Vendor Neutrality: Since it is open-source, organizations avoid "vendor lock-in." They are not tied to a specific proprietary technology like Microsoft or VMware.
4. Standardization: It provides a standard API for managing infrastructure, making it easier for developers to write cloud-native applications.

A cloud environment is built upon a layered architecture where each layer abstracts the complexity of the one below it.

Layer 1: Infrastructure Layer (Hardware)

• The bottom-most layer consisting of physical assets: Servers, Storage arrays, Network switches, Power, and Cooling systems. This constitutes the physical data center.

Layer 2: Virtualization Layer

• This layer sits on top of the hardware. The Hypervisor resides here, abstracting physical resources into virtual resources (Virtual Machines).

Layer 3: Platform / Middleware Layer

• This layer provides the operating environment for applications. It includes Operating Systems (OS), database management systems, and development frameworks. It bridges the gap between the infrastructure and the application.

Layer 4: Application Layer

• The top-most layer visible to the end-user. This includes the actual software services being consumed (e.g., email, CRM, ERP software).

Visual Hierarchy:

Multi-Cloud:
Multi-cloud is a strategy where an organization uses two or more cloud computing services from different cloud providers (e.g., using AWS for storage and Google Cloud for AI analytics).

Differences:

Containerization:
Containerization involves encapsulating an application and its dependencies (libraries, configuration files, binaries) into a single lightweight unit called a "container." The most popular tool for this is Docker.

Comparison with Virtual Machines (VMs):

1. Architecture:
   • VMs: Virtualize the hardware. Each VM runs a full Guest Operating System (OS). This is heavy on resources (RAM/CPU).
   • Containers: Virtualize the Operating System. Multiple containers share the same Host OS kernel but run in isolated user spaces.

Why it is preferred (Advantages):

1. Lightweight: Containers measure in Megabytes (MB), whereas VMs measure in Gigabytes (GB). They start up in seconds vs. minutes for VMs.
2. Efficiency: Because they share the OS kernel, you can run many more containers on a single server than VMs.
3. Portability: "Write once, run anywhere." A container runs exactly the same on a developer's laptop, a test server, and the production cloud, eliminating "it works on my machine" issues.
4. DevOps Friendly: Ideal for Microservices architecture and CI/CD pipelines.

Definition:
A Service Level Agreement (SLA) is a formal contract between the cloud service provider and the customer that defines the standards of service expected.

Key Components of an SLA:

1. Availability (Uptime): Usually expressed as a percentage (e.g., 99.99% uptime). It defines how much time the service is guaranteed to be operational.
2. Performance: Metrics regarding throughput, response times, and latency.
3. Security/Privacy: Guarantees regarding data protection.
4. Penalties: Credits or refunds the provider must pay if they fail to meet the guaranteed standards.

Importance:

• Trust: It builds trust between the consumer and provider.
• Accountability: It ensures the provider is held accountable for outages or poor performance.
• Risk Management: It helps the business understand the risks of downtime and plan accordingly.
• mathematical example: If an SLA promises 99.9% uptime, the allowable downtime per year is: