0% found this document useful (0 votes)
26 views12 pages

Resume Cloud

Uploaded by

Rayen Benmassoud
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)
26 views12 pages

Resume Cloud

Uploaded by

Rayen Benmassoud
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
You are on page 1/ 12

CH1 : Cloud Computing Basics

1. Definition
Cloud computing is an omnipresent business model, 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.

2. Key Technologies
Outsourcing: Delegating IT resources to third parties.
Virtualization: Abstracting physical resources (servers, storage, networks) into virtual
components.
Resource Sharing: Enabling remote access to shared resources, promoting cost efficiency.

3. Characteristics of Cloud Computing


On-demand Self-service: Users can provision resources without human interaction.
Broad Network Access: Services accessible via various devices.
Resource Pooling: Multi-tenant model with dynamically assigned resources.
Rapid Elasticity: Scalability according to demand.

Measured Service: Resource usage is monitored and reported for transparency.

CH2 : Cloud Service Models


1. Definition
A service model is a pre-packaged combination of IT resources offered by a cloud provider. The main
models are IaaS, PaaS, and SaaS, as defined by NIST, with additional specialized models like NaaS,
DaaS, and StaaS.

2. Service Models
Infrastructure as a Service (IaaS): Provides fundamental computing resources like
servers, storage, and networks. Users can manage operating systems and applications but not
the underlying infrastructure.
Platform as a Service (PaaS): Offers a platform for users to deploy applications
developed using supported programming languages and tools. Users manage applications but
not the infrastructure.

Software as a Service (SaaS): Delivers software applications over the internet. Users can
access applications but cannot manage the underlying infrastructure.
3. Characteristics
IaaS:
Resource Distribution as a Service: Offers hardware resources (e.g., servers, storage) as on-demand
services.
Multi-User Setup: Typically involves sharing physical hardware resources among multiple users in a
virtualized environment.
Dynamic Scaling: Enables users to scale resources (compute, storage) up or down based on real-time
demand.
Utility Pricing Model: Charges are based on usage, with prices varying depending on factors such as time,
resource consumption, and service levels.
PaaS:
User Interface Creation Tools: Provides cloud-based tools for developing web interfaces.
Multi-Tenant Architecture: Enables multiple users to work within the same environment, sharing
development resources.
Scalable Resources: Built on virtualization, which facilitates efficient resource management and scaling
based on demand.
Usage-Based Fees: Costs are determined by the number of users and the length of time the platform is in use,
making it flexible for different team sizes.
Main Functions/Tools Offered by Cloud Service Providers (CSPs) for PaaS:
 Runtime Environments: Supports multiple programming languages (e.g., Python, Java) for application
testing.
 SDK (Software Development Kit): A collection of tools for developing applications.
 Administration Console: Manages cloud-based applications via a centralized console.
 Data Storage and Management: Provides repositories for data storage, management, and distribution.

SaaS:
Browser-Based Access: SaaS applications can be accessed via a web browser, sometimes even without an
internet connection.
"One to Many" Delivery Model: The software is provided to multiple users from a single instance.
Automatic Updates: Users are not responsible for software updates or patches, as these are managed by the
service provider.
Centralized and Remote Hosting: SaaS applications are centrally managed and hosted on remote servers,
simplifying maintenance and accessibility.

4. Comparing Service Models


CH3 : Cloud Deployment Models
Definition

A cloud deployment model defines how a cloud infrastructure is built, managed, and
accessed. The NIST identifies four primary cloud deployment models:

1. Public Cloud
Accessible to the general public or a large industry group.
Managed by a service provider and accessed via the Internet.

Resources are shared among multiple clients, requiring strong security measures (e.g.,
access control, encryption).

2. Private Cloud

Dedicated solely to a single organization.


Can exist on-premises or off-premises, managed either internally or by a third party.

Ensures complete data and resource isolation but may not always be more secure than
public clouds.

3. Community Cloud
Shared by multiple entities with similar regulatory, security, or policy requirements.

Can be located on-premises or off-premises and managed by organizations or a third party.

4. Hybrid Cloud
Combines two or more clouds (public, private, or community).
Allows data and applications to move between environments for flexibility and load
balancing.

Offers maximum adaptability but adds complexity to security and identity management.

General Notes:

 Cloud deployment models involve key considerations like network dependency, data
exchange, multi-tenancy, and performance limitations.
 Each model has its own strengths and is chosen based on the specific needs of the
organization, workload location, and compliance requirements.
Comparison between deployment models

CH4 : Cloud Virtualization


Definition of Virtualization:

Virtualization is the process of creating a software-based representation of resources like


applications, servers, storage, and networks. It abstracts the physical hardware to allow
multiple operating systems or applications to run on a single machine.

Key virtualization techniques include:

 Multiplexing: Creating multiple virtual objects from one physical object (e.g., dividing a
processor among processes).
 Aggregation: Combining multiple physical resources into a single virtual entity (e.g., RAID).
 Emulation: Simulating a different type of physical object (e.g., virtual memory).
 Isolation & Encapsulation: Separating virtual machines to protect them from interference or
failures.

Virtualization in Cloud Computing

Virtualization is the foundation of cloud computing and enables the delivery of its key
benefits, such as scalability, resource efficiency, and flexibility. It transforms modern data
centers and underpins multi-tenancy in cloud business models. Virtualization supports key
cloud concepts like on-demand usage, resource pooling, elasticity, and resiliency.

Different Types of Virtualization in Cloud Computing:

1. Access Virtualization:
Enables clients to request cloud services from any location.
2. Application Virtualization:
Directs user requests to appropriate application instances based on specific conditions,
supporting multi-instance applications.
3. CPU Virtualization:
Divides a single computer into multiple virtual machines, each assigned a specific workload
using load-balancing techniques.
4. Storage Virtualization:
Stores data across multiple devices and often replicates it for redundancy and high availability.

Key Characteristics of Virtualization:


1. Partitioning:
o Enables multiple operating systems (OS) and applications to run on a single physical
system.
2. Isolation:
o Protects virtual machines (VMs) from crashes, viruses, or faults affecting others on
the same physical host.
o Ensures that security compromises are contained within the affected VM.
3. Encapsulation:
o Represents each VM as a single file, making it easy to manage and move.
4. Hardware Independence:
o VMs can run on any physical server, allowing flexibility in provisioning and
migration.

Key Capabilities of Virtualization:

1. Server Consolidation:
Multiple virtual servers can run different operating systems on the same host, maximizing
resource usage.
2. Resource Pooling:
Virtual resources abstract physical ones (e.g., processors, memory) into shared pools, ensuring
efficient utilization and cost-effectiveness.
3. Load Balancing:
Distributes workloads across servers to reduce response times, optimize performance, and
increase fault tolerance.
4. Isolation:
Each virtual machine is isolated, ensuring security and fault containment. Failures in one VM
do not affect others.
5. Migration:
Virtual machines can be moved live between hosts (e.g., using vMotion), enabling workload
balancing and minimizing downtime.

Importance of Virtualization in Cloud


 Enhances IT operational efficiency through server consolidation.
 Enables rapid provisioning of resources for on-demand scaling.
 Supports multi-tenancy by securely sharing infrastructure.
 Offers fault tolerance and high availability with live migrations and isolated environments.
 Reduces costs by minimizing hardware requirements and maximizing resource utilization

Virtualization Layers in Cloud Computing


CH5 : Cloud Computing Management
Introduction
What was once a network management product is now a cloud management product

Introduction to Cloud Management


Cloud management uses tools and software to run and monitor apps, data, and services in the
cloud, making sure everything works well and interacts smoothly with users and other
services. Key aspects include:
 Resource Deployment
 Use Tracking
 Data Integration
 Disaster Recovery
Cloud management tools are critical for ensuring that cloud-based resources function
optimally and meet business objectives.

Business Benefits of Cloud Management


1. Increased Uptime:
o Detects and resolves issues before they lead to outages.
o Boosts productivity and saves costs.
2. SLA Monitoring:
o Tracks response times, latency, and uptime.
o Ensures cloud providers adhere to established service level agreements (SLAs).
3. Compliance Management:
o Monitors the effectiveness of security and compliance protocols.
4. Disaster Analysis:
o Tracks cloud system operations to understand failures and improve reliability.

Key Characteristics of Cloud Management:


 Pay-as-you-go Billing: Ensures cost-efficiency.
 Scalability: Adjust resources dynamically based on demand.
 Ubiquity: Allows seamless communication across systems using cloud networking standards.
Challenges in Cloud Management:
1. Scale:
o Traditional centralized management systems fail to handle the scale of millions of
cloud resources.
o Requires scalable solutions for failure management and performance optimization.
2. Multiple Abstraction Layers:
o IaaS, PaaS, and SaaS layers often have separate management systems, leading to
inefficiencies and redundancy.
o Better coordination is required across these layers.
3. Federation:
o Cloud providers may need to collaborate to meet high demand.
o Managing federated clouds involves extending monitoring while maintaining a unified
view for users.
4. Dynamism:
o Frequent workload changes and migrations increase complexity.
o Management software must ensure stability and low overhead.
Cloud Monitoring:
Purpose of Cloud Monitoring:
 Ensures efficient operation of cloud computing platforms.
 Manages the growing complexity and security needs of cloud environments.
Benefits of Cloud Monitoring Tools:
 Helps administrators keep cloud environments running at peak efficiency.
 Monitors the performance of physical and virtual servers, shared resources, and
applications.
Key monitoring indicators:
 Performance: Throughput, latency, memory usage, and response time.
 Reliability: Uptime, downtime, and time to repair failures.
 Security: Resistance to attacks, access control, and data protection.

Monitoring Activities in Cloud:


1. Capacity Planning: Ensures sufficient resources for demand.
2. Data Center Management: Tracks and analyzes metrics for optimization.
3. SLA Management: Monitors adherence to SLAs.
4. Billing: Tracks resource usage for accurate cost allocation.
5. Troubleshooting: Identifies and resolves performance or security issues.

Cloud Monitoring Categories:


1. End-User Services: Monitoring protocols like HTTP, TCP, and SMTP.
2. Browser performance on the client
3. Application Performance: Tracks apps like Apache and MySQL.
4. Cloud Infrastructure: Monitors services such as AWS, GoGrid, and Rackspace.
5. Machine Instances: Measures CPU, memory, disk usage, and more.
6. Network Monitoring: Uses protocols like SNMP and CMDB.
CH6 : Automation and Orchestration
Introduction:
 Objective: Facilitate better collaboration among IT, development, and cloud teams by
removing service delivery roadblocks.
 Benefits: Reduces human error, enhances efficiency, and reallocates time for
innovation.
Automation:
 Definition: The use of processes and tools to reduce manual effort in provisioning and
managing cloud workloads and services across private, public, and hybrid clouds.
 Key Functions:
o Configuring and installing systems, containers, and virtual machines.
o Automatically provisioning and deprovisioning servers to support auto-scaling.
o Allocating resources to optimize performance without manual intervention.

Automation Benefits:
 Simplifies complex cloud environments.
 Reduces operational costs and frees up human resources for strategic projects.
 Ensures continuous delivery, leading to fewer errors and more predictable workflows.

Orchestration:
 Definition: A higher-level process that coordinates automated tasks, managing
interconnections between systems, and streamlining resource allocation and workload
distribution.
 Key Functions:
o Efficient deployment of services across multiple servers or environments.
o Continuous monitoring for vulnerabilities and compliance.
o Facilitates complex workflows and manages distributed systems interactions.
 Examples of Tools: AWS CloudFormation, Cisco CloudCenter, Puppet Bolt.

Orchestration Benefits:
 Streamlines complex cloud operations.
 Ensures resource efficiency and effective workload management.
 Provides critical data and Key Performance Indicators (KPIs) for performance,
reliability, and security.
Cloud Automation vs. Cloud Orchestration:
 Automation: Focuses on specific tasks that are executed without manual input.
 Orchestration: Integrates and manages these tasks into a cohesive, automated
workflow.
 Tool Selection Considerations:
o Depends on the nature of the task (infrastructure vs. development).
o Factors include simplicity, auditability, scalability, and data processing
capabilities.
Use Cases:
 Managing IT infrastructure and automating routine tasks.
 Coordinating software development workflows.
 Ensuring seamless operations during organizational expansions or merger
CH7 : Migration in Cloud Computing
1. Cloud Reference Models
Cloud reference models provide a structured understanding of cloud operations and actors.

Types of Models:

 Layer-Based Models: Activities are mapped to architectural layers:


o Examples: NIST Cloud Computing Reference Architecture, Cisco Cloud Reference
Framework.
 Role-Based Models: Focus on the roles and their responsibilities.

Key Actors:

1. Cloud Consumer: Uses cloud services.


2. Cloud Provider:
o Delivers cloud services by managing infrastructure and software.
o Activities include service deployment, orchestration, management, and ensuring
security and privacy.
3. Cloud Broker:
o Intermediates between cloud providers and consumers.
o Roles:
 Service Intermediation: Enhancing services for consumers.
 Service Aggregation: Combining multiple services.
 Service Arbitrage: Flexibly integrating services.
4. Cloud Auditor:
o Assesses security, performance, and compliance.
o Focuses on confidentiality, integrity, and availability.
5. Cloud Carrier: Provides secure network connectivity between providers and consumers.

2. Migration to the Cloud


Definition: Moving data, applications, or IT resources to the cloud or between clouds.

Key Considerations:

 Fluctuating Demand: Efficient for unpredictable workloads.


 Standardization: Automation is cost-effective for standardized processes.
 Independence: Highly interdependent systems may face latency issues in public clouds.
 Criticality: Critical workloads with stringent requirements (e.g., availability and recovery)
may not be ideal for public clouds.

3. The Seven-Step Migration Model


1. Assess infrastructure and identify candidates.
2. Define goals and choose a migration strategy.
3. Plan and test migration (small-scale first).
4. Execute migration using automation.
5. Validate performance and optimize.
6. Monitor workloads post-migration for efficiency.
Return on Investment (ROI): Cloud migration enhances ROI by:
 Reducing upfront infrastructure costs.
 Enabling faster scalability to meet fluctuating demands.
 Increasing operational efficiency.
4. Application Migration
Migrating applications involves strategic decisions and evaluation:

Key Questions:

 Should the organization use public or private clouds?


 Adapt existing applications, rebuild, or hybridize?
 Is portability across multiple clouds necessary?

Assessment Criteria:

 Business goals, resource demand, network dependencies, and regulatory compliance.

Service Models:

 SaaS: Leverage existing software solutions.


 PaaS: Use application platforms like Java EE or .NET.
 IaaS: Deploy applications on cloud providers’ infrastructure.

Evaluation Factors:

 SLAs (availability, scalability, performance).


 Data portability and security policies.
 Long-term costs and scalability requirements.

5. Gartner’s Five Migration Strategies


Ways to migrate applications into the cloud:

1. Rehost (IaaS): Lift and shift applications with minimal changes.


2. Refactor (PaaS): Adjust applications to fit platform capabilities.
3. Revise: Modify code for better compatibility with cloud environments.
4. Rebuild (PaaS): Redesign applications to use innovative cloud features.
5. Replace (SaaS): Switch to commercial off-the-shelf software delivered as a service.

6. Cloud-to-Cloud Migration (C2C)


Definition: Moving workloads (data, applications, and configurations) from one cloud
provider to another.

Challenges:

 Vendor lock-in and lack of portability standards.


 Ensuring secure and interoperable data migration.

Solutions:

 Use platforms like OpenStack, CloudStack, or Eucalyptus for seamless migration.


 Focus on flexibility and compatibility during provider selection.
CH8 : Cloudonomics
1. The Value of Cloud Computing

 Key Benefits:
o Converts capital expenditures (CapEx) into operational expenditures (OpEx).
o Decouples growth from cash flow constraints.
o Mitigates risks by shifting responsibility to providers.
 Key Metrics:
o Return on Investment (ROI): Measures financial gains relative to investment costs,
considering factors like time-to-market and developer productivity.
o Total Cost of Ownership (TCO): Accounts for all costs (development, maintenance,
operations) for on-premises vs. cloud infrastructure.

2. The Laws of Cloudonomics

1. Utility Services Cost Less Even When They Cost More: You pay only for what you use,
reducing waste.
2. On-Demand Trumps Forecasting: Cloud adapts to demand spikes, avoiding under or over-
provisioning.
3. The Peak of the Sum Is Less Than the Sum of the Peaks: Shared cloud resources handle
demand more efficiently.
4. Aggregate Demand Is Smoother: Clouds utilize resources better by averaging demand
variations across users.
5. Economies of Scale: Cloud providers reduce unit costs through bulk purchasing.
6. Superiority in Numbers: Large-scale providers combat cyber threats effectively.
7. Parallel Processing: Accelerates decision-making through distributed computing.
8. Latency Minimization: Multi-site cloud setups reduce delays.
9. Reliability: Geographic dispersion increases uptime and fault tolerance.
10. Flexibility in Location: Clouds optimize data center locations based on efficiency, not legacy
constraints.

3. Advantages and Challenges

 Advantages:
o Lower upfront costs and improved cost efficiency.
o Scalability and flexibility for changing demands.
o Increased security and end-user productivity.
 Challenges:
o Requires strong SLAs to manage performance and reliability expectations.
o Concerns over data security, latency, and vendor lock-in.

4. Service Level Agreements (SLAs)

 Purpose: Define quality-of-service (QoS) metrics like availability, reliability, scalability, and
performance.
 Parameters:
o Uptime, response times, responsibilities, and warranties.
o Monitoring and measurement scope for QoS guarantees.

You might also like