-
Notifications
You must be signed in to change notification settings - Fork 13
/
Clouds.ptml
168 lines (149 loc) · 5.58 KB
/
Clouds.ptml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
<!DOCTYPE html>
<html>
<head>
<link href="style.css" rel="stylesheet" type="text/css"/>
<title>
Clouds
</title>
</head>
<body>
<!--include menu.txt -->
<h1>
Clouds
</h1>
<div style="text-align:center">
<p>
<img
src="https://upload.wikimedia.org/wikipedia/commons/thumb/a/a3/Cumulus_clouds_panorama.jpg/320px-Cumulus_clouds_panorama.jpg">
</p>
</div>
<details>
<summary class="sum1">
Overview
</summary>
<p>
Five essential characteristics:
</p>
<ol>
<li>
<b>On-demand self-service</b>:
users do not need human help to add service.
</li>
<li>
<b>Broad network access</b>:
resources are available over the network via standard
mechanisms (e.g., http).
</li>
<li>
<b>Resource pooling</b>:
users acquire resources from a common pool, and have no
idea where "their" resources live.
</li>
<li>
<b>Rapid elasticity</b>:
fast an automatic scaling has loads change.
</li>
<li>
<b>Measured service</b>:
the services are metered much like electricity usage.
</li>
</ol>
<details>
<summary class="sum2">
Cloud computing video
</summary>
</details>
</details>
<details>
<summary class="sum1">
Clouds as a Service
</summary>
<ul>
<li>
<b>Infrastructure as a service (IAAS)</b>:
Offers direct access to a VM user can use as they see
fit.
</li>
<li>
<b>Platform as a service (PAAS)</b>:
Includes things such as web servers and databases.
</li>
<li>
Old worries gone: backup, power, cooling, scalability,
upgrading, etc.
</li>
<li>
New worries arrive: is data secure? What laws apply?
Can a co-hosted competitor snoop?
</li>
<li>
<b>Vendor lock-in</b>: once you choose a cloud
provider, can you ever (practically) leave?
</li>
</ul>
<figure>
<iframe width="560" height="315"
src="https://www.youtube.com/embed/vgI5F5Si518"
frameborder="0" allowfullscreen>
</iframe>
<figcaption>
IAAS video
</figcaption>
</figure>
</details>
<details>
<summary class="sum1">
Virtual Machine Migration
</summary>
<dl>
<dt>
How to migrate to faster hardware, off of broken
hardware, etc.?
</dt>
<dd>
We could shut down all virtual machines and re-start
them on new hardware: significant pause!
</dd>
<dd>
We could pause them, transfer their memory, and resume:
still a noticable pause.
</dd>
<dd>
Or, using <b>pre-copy memory migration</b>, we can copy
pages first, then do a <b>live migration</b>. If no one
notices, it was a <b>seamless live migration</b>!
</dd>
</dl>
<figure>
<iframe width="560" height="315"
src="https://www.youtube.com/embed/gFKGgoHDRi8"
frameborder="0" allowfullscreen>
</iframe>
<figcaption>
Live migration
</figcaption>
</figure>
</details>
<details>
<summary class="sum1">
Checkpointing
</summary>
<ul>
<li>
Captures the machine at various times, so we can
rollback if we need to.
</li>
<li>
Use <b>copy on write</b> to save time: only copy what
has changed.
</li>
<li>
Unsolvable: what to do about remote machines that were
interacting with ours? A: Nothing can be done (in
general).
</li>
</ul>
</details>
<!--include quizzes/quiz7.11.qhtm -->
</body>
</html>