Introduction to basic concepts of Cloud Computing including AWS, GCP and Azure

2. Introduction to
Cloud Computing
Samuel Dratwa
Samuel.Dratwa@gmail.com

3. Course agenda
• Introduction
• Demo and comparison
• Cloud architecture
• Hands on AWS
• Security & encryption
• Hands on GCP
• The future of the cloud

4. What is
Cloud Computing ?
4

5. Definition
5
 Wikipedia - Cloud computing is the on-demand availability
of computer system resources, especially data storage and computing power,
without direct active management by the user. The term is generally used to
describe data centers available to many users over the Internet.
 Academic (simple) - provide on-demand resources or services over a
network, often the Internet, with the scale and reliability of a data center.
 Mine – distributed mainframe, reachable from any device connected to the
internet

6. Cloud computing is kind of hosting
6

7. Three layers of services
7
IaaS
Infrastructure as a Service
PaaS
Platform as a Service
SaaS
Software as a Service
7

8. SaaS
PaaS
IaaS
IaaS, PaaS and SaaS Point of View
8
Platform as a Service
PRODUCT: storage, compute and other
services to simplify application
development, especially of web
applications.
USERS: Application Developers
Software as a Service
PRODUCT: Finished application
available on demand to end user
USERS: Software consumer
Infrastructure as a Service
PRODUCT: Compute power, storage and
networking infrastructure over the
internet, provided as a virtual machine
image
USERS: Developers
8

9. The “old way”
Server(s)
PC(s) / Laptop(s)
Software
Buy, Install,
Maintain, Upgrade
9

10. The “new way”
Server(s)
PC(s) / Laptop(s)
Software
Buy, Install,
Maintain, Upgrade
10

11. It’s not just above the line
11

12. Also (almost) all the rest
X
X
X
X
12

13. Outsourcing to the extreme
13

14. • No hardware or software to manage
• Service delivered through a browser
• Examples:
• CRM
• Financial Planning
• Human Resources
• Word processing
• Commercial Services:
• Salesforce.com
• email
SaaS - Software delivery model
14

15. SaaS examples
15

16. • Pay per use
• Instant Scalability
• Security
• Availability/Reliability
• Disaster recovery
• APIs
SaaS - Advantages
16
16

17. • Is Skype a SaaS ?
• Is YouTube a SaaS
SaaS Attention Test ;-)
17

18. • Estimating demand is not a science!
• Platform management is not fun!
• Examples:
• Storage
• Database
• Scalability
• Commercial Services:
• GCP
• Azure
• AWS
PaaS - Platform delivery model
18

19. PaaS examples
19

20. AWS pricing
20

21. 21

22. 22

23. Price comparison
23

24. • Pay per use
• Instant Scalability
• Security
• Availability/Reliability
• Disaster recovery
• APIs
PaaS - Advantages
24

25. PaaS Attention Test ;-)
25

26. • Access to infrastructure stack:
• CPU, Memory
• Baremetal
• Firewalls
• Routers
• Load balancing
• Commercial Services:
• Flexiscale
• AWS
• RackSpace
IaaS - infrastructure delivery model
26

27. • Pay per use
• Instant Scalability
• Security
• Availability/Reliability
• Disaster recovery
• APIs
IaaS - Advantages
27

28. IaaS vs. PaaS
28

29. Common Factors Advantages
• Pay per use
• Instant Scalability
• Security
• Reliability
• APIs
• Lower cost of ownership
• Reduce infrastructure
management
responsibility
• Allow for unexpected
resource loads
• Faster application rollout
IaaS
PaaS
SaaS
29

30. 30

31. Public
Cloud
Cloud Ecosystem
31
Enterprise
Private Cloud Private Cloud
External
Internal
Virtual Private Cloud
31

32. AWS Outpost
32

33. 33

34. Risks
 Security
 Downtime
 Access
 Dependency
 Interoperability
 Regulation
IaaS
PaaS
SaaS
34

35. The market
35

36. 36

37. 37

38. 38

39. 39

40. Cloud architecture
40

41. Cloud computing is kind of hosting
41

42. What is there in a Cloud?
Individuals Corporations Non-Commercial
Cloud provisioning
Storage
Provisioning
OS
Provisioning
Network
Provisioning
Service(apps)
Provisioning
SLA(monitor),
Security, Billing,
Payment
Services Storage Network OS
Resources
42

43. What is Cloud OS ?
Physical Node Physical Node Storage
Server
Storage
Server
Physical Node
Physical Node
Storage
Server
Storage
Server
Mail Virtual
Cluster
Compute Nodes
Backup
Virtual
Cluster
HC Virtual
Cluster
AppX Virtual
Cluster
Data Nodes
Service Nodes
System Service
daemons
Cloud OS agents
• System Management Software layer
– Physical Resource Provisioning
– Virtual Resource Management
• Improve manageability of massive Cloud
Data Center
• Enhance self-provisioning
• Optimize physical resource utilization
• High Availability for any single point of
failure
• Energy management
– Highly Available Distributed Storage
Management
– Service Load Balancing
– Security
– High Speed Networking
• What is it not?
– It’s not Operating System
– It’s not Virtualization Hypervisor
43

44. Load balancing
44

45. Google’s Chrome OS
45

46. Cloud Data Center
46

47. Google data center
47

48. Azure Virtualization Architecture
Azure Services (storage)
Load
Balancer
Public Internet
Worker
Role(s)
Front-end
Web Role
Switches
Highly-available
Fabric Controller
In-band
communication –
software control
Load-balancers
48

49. Azure Virtualization Architecture
Hypervisor
Guest Partition
(VM)
Host Partition
(VM)
Guest Partition
(VM)
Hardware
Virtualization
Stack
(VSP)
Drivers
Host OS
Server Core
Applications
Applications
RD OS
Virtualization
Stack
(VSC)
Guest OS
Server Enterprise
Virtualization
Stack
(VSC)
Guest OS
Server Enterprise
NIC Disk1
VMBUS VMBUS VMBUS
Disk2 CPU
Azure Services (storage)
Load
Balancer
Public Internet
Worker
Role(s)
Front-end
Web Role
49

50. Commitment to Interoperability
50

51. Amazon
1
51

52. 52

53. 53

54. OpenStack

55. • OpenStack APIs
• Nova: Open Stack Compute automates provisioning of virtual machines
• Cinder: Block storage system accessible by VMs
• Neutron: OpenStack service for establishing connectivity between VMs
• Swift: Large scale redundant object (i.e. VM) store
• Glance: Image service that catalogs and manages
(stores, retrieves, registers and delivers ) virtual
machine images
• Keystone: provides system-wide authentication
• Ironic: Bare metal management
• Horizon: Web-based dashboard access and management for users
Open Stack – A Cloud Operating System
55

56. • Stack: Collection of resources
• Virtual machines, networks, auto scaling rules
• Template: Definition of resources that make up the Stack
• Four sections
• Resources – Objects that will be created - like a server
• Properties – image, flavor
• Parameters – Property values
• Output – Information passed back to user or dashboard
Open Stack – A Cloud Operating System
Images
CentOS
XMS VNFc
CentOS
MRB VNFc
CentOS
Load Balancer VNFc
Flavors
4 CPU
8GB RAM
50GB Disk
8 CPU
16GB RAM
50GB Disk
12 CPU
16GB RAM
50GB Disk
Stacks
Auto scaling
policy
Parameters
Stack
Heat Templates contain info to create stacks
56

57. 57

58. 58

59. 59

60. OpenStack map to AWS
Horizon
Dashboard
Swift
object store
Glance
image store
Nova
compute node
Cinder
volume service
Keystone
identity service
Heat
Orchestration
Celiometer telemetry service
Trove
database
Neutron
networking
S3 EC2 EBS vPC RDS
AMI
IAM
Cloud
Formation
60

61. Provisioning flow
61

62. AWS Hands On

63. 63

64. AWS instance types
64

65. 65

66. Security & Encryption

67. • The good news
• The cloud providers are better at security than we are
(hey, it’s their specialty…)
• The bad news
• It’s a different ball game
• With bigger threats
Cloud and the “security problem”
67

68. Moving from “not so smart” to “the smarter”
8
68

69. Standards are key
69

70. 70

71. Identity and Access Management (IAM)
71

72. Security group
72
72

73. Key pair
73

74. GCP Hands On

75. 75

76. The migration path to a cloud
6

77. “Packaged”
Application
An application that I buy “off the
shelf” and run myself
Self Hosted “Home
Built”
An application that I develop and
run myself
Build
Buy
Hosted
“Home Built”
An application that I develop
myself, but run at a hoster
Hosted
“Packaged”
An application that I buy “off the
shelf” and then run at a hoster
Cloud Platform
An application that I develop
myself, but run in the cloud
“Software as a Service”
A hosted application that I
buy from a vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
77

78. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Bild
vs.
Buy
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted application
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Maximum
Economy of Scale
All acceptable options (trade off)
Maximum Control
78

79. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
Molecule Research
HR System
Email
Issue Tracking
ERP
“Too costly to run this myself,
but I’ve made too many
customizations”
79

80. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
Molecule Research
HR System
Email
Issue Tracking
ERP
“CRM and Email are commodity
services – They have no
customizations, and it’s cheaper for
someone else to run these”
80

81. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
Molecule Research
HR System
ERP
Email
Issue Tracking
“I can’t afford to maintain
this old HR application
written in VB – it’s driving
me mad!”
“…but due to privacy issues, I
prefer keeping my HR data
on-premises”
81

82. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
Molecule Research
HR System
ERP
Email
Issue Tracking
“I wish I had access to
cheaper compute and
storage when I need it”
82

83. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
HR System
ERP
Email
Issue Tracking
Molecule Research
83

84. “Packaged”
Application
An application that I buy
“off the shelf” and run
myself
Self Hosted
“Home Built”
An application that I
develop and run myself
Build
Buy
Hosted
“Home Built”
An application that I
develop myself, but run
at a hoster
Hosted
“Packaged”
An application that I buy
“off the shelf” and then
run at a hoster
Cloud Platform
An application that I
develop myself, but
run in the cloud
“Software as a
Service”
A hosted pplication
that I buy from a
vendor
On premises vs. Cloud
On premises Cloud
Bild
vs.
Buy
Clinical Trial
HR System
ERP
Email
Issue Tracking
Molecule Research
“THIS is where I want to
spend my IT resources – I’m
going to double down on this
application!”
84

85. The future of
the cloud

86. Kubernetes
Kubernetes (K8s) is an open-source system
for automating deployment, scaling, and
management of containerized applications.
It groups containers that make up an application
into logical units for easy management and
discovery. Kubernetes builds upon 15 years of
experience of running production workloads at
Google, combined with best-of-breed ideas and
practices from the community.
86
86

87. What is Kubernetes (aka K8s)
• Greek for Pilot or “Helmsman” of a Ship
• Project that was spun out of Google as an open source
container orchestration platform
• Planet Scale
• Run Anywhere
• On-Prem, Hybrid, Cloud
87
87

88. Kubernetes Features
• Self Healing
• Horizontal scaling
• Service discovery and load balancing
• Automatic bin packing
• Automated rollouts and rollbacks
• Secret and configuration management
88
88

89. K8s Cluster
Master
Master
Master
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
Worker
• Master Nodes:
• Cluster Management
• API Server
• Etcd (In-Mem DB)
• Scheduler
• Controller
• Worker Nodes
• aka Minions
• Doing the job
• Executing the Workload
89

90. Master Nodes
• Controller Manager
• Decides what needs to be executed
• Scheduler
• Decide where Pods need to be executed
• etcd:
• Distributed key/value store (In Mem DB)
• Store the State of Cluster/Nodes/Pods
• API Server
• Provides internal and external interface to Kubernetes
90
90

91. Worker Nodes
• Kubelet
• Kubernetes Agent running on each node
• Responsible to execute
• Proxy
• Network Proxy for cluster communication
• Forwarding and Load Balancing
• Container Runtime
• Docker
91
91

92. K8s Architecture
92

93. 93

94. • 1 MicroService == 1 POD + 1 Deployment + 1 ReplicationSet + 1 Service (+ 1 Ingress)
• Lifecycle Management of Applications is challenging
Kubernetes Pain Point
94

95. • Package manager for K8s
• like yum, apt, pip but for Kubernetes Application
• Search and reuse or start from scratch
• Lifecycle Management
• Create
• Install
• Upgrade/Rollback
• Delete
• Status
• Versioning
What is Helm
95

96. Benefits
96

97. • Helm Client
• Command-line client
• Interacts with Tiller Server
• Deploy Applications from Local/Public Repository
• Tiller Server
• In-cluster (Pod)
• Listens to the Helm client
• Interacts with Kubernetes API Server
• Manages the lifecycle
Helm Architecture
97

98. Technology Hierarchy
98

99. 99
99

100. Google trends
100
100

101. Thank you.
Thank you.