Cloud Computing
Lecture 1: Introduction
Mr. Nisar Ali
Institute of Computer Sciences and
Information Technology (ICS/IT)
1
Lecture 1 Introduction
Instructor
Mr. Nisar Ali
Visiting Lecturer
Qualification:
MS Cyber Security with Excellent grade – UET Peshawar
BS Computer Science - UET Peshawar
Contact:
17PWBCS0579@uetpeshawar.edu.pk
nisaricup@gmail.com
Lecture 1 Introduction
Books
Reference Books
Cloud Computing By Sandeep Bhowmik (CAMBRIDGE)
Cloud Computing Basics By T.B. Rehman, Pd.D.
Recommended Resources
Various Research Papers
Lecture 1 Introduction
Grading Criteria
Exams
Midterm: 20%
Final Term: 70%
Sessional
Assignments: 10%
Lecture 1 Introduction
Course Objective
To study the principles/methods and current technologies in
•Cloud Computing Fundamentals
•Cloud Service Models: IaaS, PaaS, SaaS
•Hands-on Experience with AWS, Azure, or Google Cloud
•Design and Deployment of Scalable Cloud Solutions
•Security Best Practices in Cloud Computing
•Big Data
•HDFS
•MapReduce
Lecture 1 Introduction
Course Contents
Weekly Schedule
Week Course Contents
Week 01 Intro to Cloud
Week 02 Distributed Systems
Week 03 Service Oriented Computing
Week 04 Virtualization
Week 05 Cloud Characteristics, Deployment and service models
Week 06 IaaS
Week 07 PaaS, SaaS
Midterm Examination
Week 08 web middleware
Week 09 Cloud Storage
Week 10 Big Data
Week 11 Cloud Security
Week 12 AWS Services
Week 13 HSFS 6
Week 14 Map Reduce
Week 15 Big Data and Machine Learning
Week 16 Cloud Sim
Final Term Examination
Lecture 1 Introduction
•
–
• “
”
•
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
• “
•
…
“
’ ”
• “
•
• ’
• ’
• ’
• ’
•
•
•
• A single-site cloud (aka “datacenter”) consists of
• Compute nodes (grouped into racks)
• Switches, connecting the racks
• A network topology, e.g., hierarchical
• Storage (backend) nodes connected to the
network
• Front-end for submitting jobs and receiving
client requests
• Software services
• A geographically distributed cloud consists of
• Multiple such sites
• Each site perhaps with a different structure
and services
–
•
•
•
–
• –
•
•
•
• –
•
•
•
•
• ’
•
•
•
’
•
“
”
• ’
•
•
•
•
•
•
•
•
••
•
•
•
•
•
•
•
•
•
•
•
•
http://gigaom.com/cleantech/a-rare-look-inside-
facebooks-oregon-data-center-photos-video/
Front
Seeweb | CC BY-SA 2.0
Back
Robert Scoble | CC BY 2.0
Inside
Intel Free Press | CC BY 2.0
•
U.S. Army | CC BY 2.0
•
Greg Goebel | CC BY-SA 2.0
David Goehring | CC BY 2.0
•
•
•
Tim Dorr | CC BY-SA 2.0
Leslie Hawthorn | CC BY-SA 2.0 ChrisDag| CC BY 2.0
II. On-demand access: *aaS Classification
On-demand: renting a cab vs. (previously) renting a car, or
buying on e. Ex.:
• AW S Elastic Compute Cloud (EC2): a few cents to a few
$ per CPU hour
• AW S Simple Storage Service (S3): a few cents to a few $ per
GB-month
• H aaS: H ardware as a Service
• You get access to barebones hardware machines, do
whatever you want with them, ex: your own cluster
• Not always a good idea because of security risks
• IaaS: In frastructure as a Service
• You get access to flexible computing and storage
infrastructure. Virtualization is one way of achieving this
(what’s another way, e.g., using Linux). Often said to
subsume HaaS.
• Ex: Amazon Web Services (AW S: EC2 and S3),
Eucalyptus, Rightscale, Microsoft Azure
II. On-demand access: *aaS Classification
• PaaS: Platform as a Service
• You get access to flexible computing and
storage infrastructure, coupled with a
software platform (often tightly)
• Ex: Google’s AppEngine (Python, Java, Go)
• SaaS: Software as a Service
• You get access to software services, w hen you
need them. Often said to subsume SOA
(Service Oriented Architectures).
• Ex: Google docs, M S Office on dem and
IV. New Cloud Programming Paradigms
• Easy to write and run highly parallel programs in new cloud
programming paradigms:
• Google: MapReduce and Sawzall
• Amazon: Elastic MapReduce service (pay-as-you-go)
• Google (MapReduce)
• Indexing: a chain of 24 MapReduce jobs
• ~200 K jobs processing 50 PB/month (in 2006)
• Yahoo! (H adoop + Pig)
• WebMap: a chain of 10 0 MapReduce jobs
• 280 TB of data, 250 0 nodes, 73 hours
• Facebook (H adoop + H ive)
• ~30 0 TB total, adding 2TB /day (in 200 8)
• 3K jobs processing 55TB/day
• Similar numbers from other companies, e.g., Yieldex,
eharm ony.com , etc.
• NoSQL: MySQL is an industry standard, but Cassandra is
2400 times faster!
•
• ’
•
•
•
•
•
•
•
•
•
•
•
• •
•
•
•
• •
•
•
•
•
–
•
•
Thank You
