0% found this document useful (0 votes)
4 views

Lecture_1

The document outlines the course CS409 on Selected Topics in Computer Science, focusing on cloud computing and its various components, services, and deployment models. It includes a detailed academic calendar, grading criteria, and an introduction to the limitations of traditional computing approaches. Key topics covered in the course include cloud architecture, virtualization, resource pooling, and cloud delivery models such as IaaS, PaaS, and SaaS.

Uploaded by

jouf00008
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)
4 views

Lecture_1

The document outlines the course CS409 on Selected Topics in Computer Science, focusing on cloud computing and its various components, services, and deployment models. It includes a detailed academic calendar, grading criteria, and an introduction to the limitations of traditional computing approaches. Key topics covered in the course include cloud architecture, virtualization, resource pooling, and cloud delivery models such as IaaS, PaaS, and SaaS.

Uploaded by

jouf00008
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/ 40

LECTURE 1

Selected Topics in Computer Science CS409


By
Dr.Ashraf Hendam
OUTLINE
• Course Content
• Academic calender
• Textbooks
• Grading
• Introduction
• Computing layers
• Computing as the Utility Service
• What is Cloud Computing?
• Cloud characteristics
• Cloud components
• Cloud services
• Cloud Deployment Models
Course Content
Week Lecture
Week1 Introduction
Computing layers, Cloud Computing, Cloud Characteristics, Cloud components,
Cloud services, Cloud Deployment Models.
Week2 Cloud Reference Architecture (1)
Evolution of Cloud Computing, NIST Cloud Computing Reference Architecture,
Cloud provider.
Week3 Cloud Reference Architecture (2)
Cloud consumer, Cloud pricing models, Cloud Carrier, Cloud Broker, Cloud Auditor,
File System and Storage, DATA-INTENSIVE COMPUTING, Cloud file systems
challenges, Big-data.
Week4 Hadoop Distributed File System (HDFS) (1)
Big Data sources, Characteristics, Data Open Source Tools, management tools,
HDFS attributes.
Week5 Hadoop Distributed File System (HDFS) (1)
HDFS Goals and Architecture, Data Organization, NameNode, Data Replication,
Heartbeats, Block Placement, Data Correctness, Data Pipelining, Rebalancer, failure
types.
Week6 Virtualization
physical computing resources, advantages of virtualization to business, machine or
server level virtualization, server virtualization products and vendors, emulation,
virtualization and security
Course Content
Week Lecture
Week6 Virtualization
physical computing resources, advantages of virtualization to business, machine or
server level virtualization, server virtualization products and vendors, emulation,
virtualization and security
Week7 Resource Pooling
Resource Pooling , Sharing and Provisioning
Week8 Cloud Scaling
scaling in cloud computing, scaling foundation , scalable application, scaling
strategies, auto scaling,
scaling types
Week9 Capacity Planning
cloud capacity, capacity planning approaches, auto-scaling , capacity and
performance, capacity planning steps
Week10 Cloud Load Balancing+ Exam (2)
importance of load balancing, load balancing goals, categories, parameters and
algorithms, application delivery controller
Week11 Service-Oriented Architecture(SOA)
role of soa in cloud computing, service-oriented architecture, open standard
implementation
Academic calendar

Back
Textbooks
• Cloud Computing Sandeep Bhowmik (2017)
• Engineering of Big Data Processing PIOTR FULMAŃSKI(2022)

Back
Grading
Lecture Attendance 7
Lab. Attendance 3
Midterm 40
Exam2 20
Final Exam 90
Total 150

Back
Introduction
LIMITATIONS OF THE TRADITIONAL COMPUTING
APPROACHES
Enterprise Perspective
• Business organizations need to invest huge volumes of
capital to setup the required IT infrastructure such as
Servers, client terminals, network infrastructure and
moreover, arranging adequate power supply, cooling
system.
• Enterprises (or IT service firms) need to maintain a team
of experts.
• Get an updated version of application with new releases
to keep up with changing business scenario.
Back
Introduction
LIMITATIONS OF THE TRADITIONAL COMPUTING APPROACHES
Individual User’s Perspective
• Initial capital investment for setting up computing
infrastructure
• Procure unnecessary volume/capacity of hardware
resources, which remain unutilized.
• Professional help can be obtained against payment

Back
Introduction
Solution
An organization or an individual user needs to
set up in-house IT infrastructure (small
or big) for computing purpose, they have two
options:
• Doing it themselves (by deploying in-house
team, in case of an organization)
• Outsourcing the responsibility to some
third party who are well-trained for the job
Back
Computing layers
Different people use different categories of
computing facilities. These computing facilities
can be segmented into three categories:
• Application
• Platform
• Infrastructure
Back
Computing layers
• Application
- Applications (application software) constitute the topmost layer of this
layered architecture.
- It provides interfaces for interaction with external systems (human or
machine)
- A user actually works on the application layer while he or she is going to
edit a document, play a game or use the calculator in a computer.
- Organizations access enterprise applications using application interfaces
to run their business.

Back
Computing layers
• Platform
The term ‘computing platform’ refers to different
abstract levels.
It consists of:
• Certain hardware components, only.
• Hardware loaded with an operating system (OS).
• Hardware and OS, additionally, loaded with run-
time libraries. Back
Computing layers
• Infrastructure
• The bottom layer or the foundation is the ‘computing
infrastructure’ facility.
• This includes all physical computing devices or hardware
components like the processor, memory, network, storage devices
and other hardware appliances.
• Infrastructure refers to computing resources in their bare-metal form
(without any layer of software installed over them, not even the
operating system).

Back
Computing layers
• Different users/subscribers of three computing layers

• Elements of three computing layers

Back
Computing as the Utility Service
• Computing facilities are supplied in the same way as like as a
civic authority supplies water or electricity in a city.
• Customers can use those facilities without being worried
about how they are being supplied or who is managing all
of these activities.
• The three major aspects of computing which were
represented in three-layered computing architecture are
delivered as utility services

Back
What is Cloud Computing?
•Cloud Computing is a general term used to describe a new
class of network based computing that takes place over the
Internet,
–a collection/group of integrated and networked hardware,
software and Internet infrastructure (called a platform).
–Using the Internet for communication and transport provides
hardware, software and networking services to clients
•These platforms hide the complexity and details of the
underlying infrastructure from users and applications by
providing very simple graphical interface or API (Applications
Programming Interface).
Back
What is Cloud Computing?
• In addition, the platform provides on demand
services, that are always on, anywhere, anytime
and any place.
• Pay for use and as needed, elastic
– scale up and down in capacity and functionalities
• The hardware and software services are available
to
– general public, enterprises, corporations and
businesses markets
What is Cloud Computing?
Cloud Computing Definition
The National Institute of Standards and Technology
(NIST) defines cloud computing as follows:
Cloud computing is a model for enabling ubiquitous,
convenient, ondemand 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
Back
What is Cloud Computing?

• Shared pool of configurable computing resources


• On-demand network access
• Provisioned by the Service Provider Back
Cloud characteristics
• Rapid elasticity
– You can go from 5 servers to 50 or from 50 servers
to 5
• Measured service
– You pay for what you use
• On-demand self-service
– You get elasticity automatically
• Ubiquitous network access
– You can access the cloud from anywhere
• Location-independent resource pooling
– You work with virtual machines that could be hosted
anywhere
Cloud components
3 components
• Clients
• Datacenter
• Distributed servers
Cloud components
Clients
• Mobile
• SmartPhones, Tablets, Service Hubs
• Thin
• No internal hard drives, lets servers do all
work, displays info
• Thick
• Laptops, desktop computers
• Which is the best?
• Thin - lower costs, security, power
consumption, easy to replace, less noise
Cloud components
Datacenter
Data Center – facility used to house computer
systems and associated components
Cloud components
Distributed servers
• Compute nodes
• Provides CPU, Memory, Scratch Storage, and Networking resources
through virtualized interfaces.
• Hosts guest operating systems (Virtual Machines) using one or more
VM hypervisors
• Resource interface depends on the type of cloud (horizontal/vertical
cloud)
• Storage nodes
• Compute nodes only provide temporary storage space for
users/applications
• Storage nodes provide long term data storage solutions
• Can be mapped to specific processes running on compute
Cloud services
• Machines in the cloud
– Can I move my VM elsewhere?
• Storage in the cloud
– Can I move my data elsewhere?
• Databases in the cloud
– Can I move my data elsewhere?
• Applications in the cloud
– Can I run my application elsewhere?
Cloud services
• Machines in the cloud
Many cloud providers allow you to create a Virtual
Machine (VM) and deploy it in the cloud:
• Your VM images are stored in cloud storage
• You can create as many images as you need
• You can automatically start and stop running
instances of those images as needed
This is the simplest way to get started in the cloud,
particularly if you’ve been using virtualization already
Cloud services
Storage
Most cloud storage systems are designed as
distributed, redundant systems
• Your data are stored on more than one disk in
more than one place
• If one part of the system goes down, the rest of
the system keeps going
• “There should never be a single point of failure”
is a stated design goal
But you can’t think of cloud storage as just another
hard drive
Cloud services
Cloud databases
have similar design points Datasets are distributed for
reliability
• Some cloud databases support schemas, some
don’t
• Some cloud databases support joins, most don’t
• Some cloud databases are relational, almost all
aren’t
• Some cloud databases are transactional, some
aren’t
Cloud services
Applications in the cloud(Software as a Service (SaaS))
• SaaS is a model of software deployment where
an application is hosted as a service provided to
customers across the Internet.
• Saas smoothes the load of software
maintenance/support
– but users quit control over software versions and
requirements.
Cloud Deployment Models

Back
Cloud Deployment Models
1. Public Cloud - the infrastructure is made
available to the general public or a large
industry group and is owned by the
organization selling cloud services.
2. Private Cloud – The cloud is operated
solely for an organization. It may be
managed by the organization or a third
party and may exist on premise or off
premise.
Back
Cloud Deployment Models
3. Hybrid Cloud - composition of two or more
Clouds (public, private, or community) as unique
entities but bound by a standardised technology that
enables data and application portability.
4. Community Cloud- The cloud infrastructure is
shared by several organizations and supports a
specific community that has shared concerns.
It may be managed by the organizations or a third
party and may exist on premise or off premise

Back
Advantages of Cloud Computing
 Cloud computing do not need high quality
equipment for user, and it is very easy to use.
 Provides dependable and secure data storage
center.
 Reduce run time and response time.
 Cloud is a large resource pool that you can buy
on-demand service.
 Scale of cloud can extend dynamically providing
nearly infinite possibility for users to use internet.

Back
Cloud Computing Models, Resources, Attributes
Delivery models
Software as a Service (SaaS) Deployment models
Platform as a Service (PaaS) Public cloud

Infrastructure as a Service (IaaS) Private cloud


Community cloud
Hybrid cloud

Cloud computing
Infrastructure
Distributed infrastructure
Defining attributes
Resource virtualization
Massive infrastructure
Autonomous systems
Utility computing. Pay-per-usage
Resources
Accessible via the Internet
Compute & storage servers
Networks Services Elasticity

Applications
Cloud Delivery Models
1. Infrastructure as a Service (IaaS) (low level)
2. Platform as a Service (PaaS)
3. Software as a Service (SaaS) (high level)
Infrastructure-as-a-Service (IaaS)
• Infrastructure is compute resources, CPU, VMs, storage, etc
• The user is able to deploy and run arbitrary software, which
can include operating systems and applications.
• The user does not manage or control the underlying Cloud
infrastructure but has control over operating systems,
storage, deployed applications, and possibly limited
control of some networking components, e.g., host
firewalls.
• Services offered by this delivery model include: server
hosting, storage, computing hardware, operating systems,
virtual instances, load balancing, Internet access, and
bandwidth provisioning.
• Example: Amazon EC2
Back
Platform-as-a-Service (PaaS)
• Allows a cloud user to deploy consumer-created or acquired
applications using programming languages and tools
supported by the service provider.
• The user:
- Has control over the deployed applications and,
possibly, application hosting environment configurations.
• Does not manage or control the underlying Cloud
infrastructure including network, servers, operating systems,
or storage.
Not particularly useful when:
• The application must be portable.
• Proprietary programming languages are used.
• The hardware and software must be customised to improve
the performance of the application.
• Examples: Google App Engine, Windows Azure
Software-as-a-Service (SaaS)
• Applications are supplied by the service provider.
• The user does not manage or control the
underlying Cloud infrastructure or individual
application capabilities.
• Services offered include:
• Enterprise services such as: workflow management,
communications, digital signature, customer
relationship management (CRM), desktop software,
financial management, geo-spatial, and search.
• Not suitable for real-time applications or for those
where data is not allowed to be hosted externally.
• Examples: Gmail, Salesforce

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy