-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathlecture5.html
976 lines (897 loc) · 28.7 KB
/
lecture5.html
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
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
<!DOCTYPE html>
<!--
Web 2.0, CTU course slides
(cc) 2010-2014 Tomas Vitvar, [email protected]
-->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="course" content="Web 2.0" />
<meta name="lecture" content="Lecture 5" />
<meta name="keywords" content="SaaS, IaaS, PaaS" />
<link type="text/css" rel="stylesheet" href="css/meta.css">
</link>
<link type="text/css" rel="stylesheet" href="css/ctu-fit.css">
</link>
<link type="text/css" rel="stylesheet" href="humla/lib/core/humla.css">
</link>
<script type="text/javascript" src="humla/lib/humla.js"></script>
<title>Cloud Architectures</title>
</head>
<body>
<footer>
<p><b>#META_LECTURE#: #TITLE#</b>, <span class="meta_semester" />,
<span class="meta_twitter" />
</p>
<p><b>‒ #SLIDE_NO# ‒</b></p>
</footer>
<div class="slide intro">
<hgroup>
<h1><span class="meta_course" /></h1>
<h2>#META_LECTURE#: #TITLE#</h2>
</hgroup>
<div class="author">
<p class="meta_author" />
<p><span class="meta_email" /> • <span class="meta_twitter" /> •
<span class="meta_web" />
</p>
</div>
<center>
<div class="meta_logo"></div>
</center>
<div class="org">
<p class="meta_org" />
<p><span class="meta_orgfac" /> • <span class="meta_field" />
• <span class="meta_orgweb" /></p>
</div>
<div class="etc">
<div class="text-info">
Modified: #LAST_MODIFIED#<br />
Humla v#HUMLA_VERSION#
</div>
<a href="http://creativecommons.org/licenses/by-sa/3.0/">
<div class="license"></div>
</a>
<div class="oppa"></div>
</div>
</div>
<div class="slide outline"></div>
<section>
<header>Introduction</header>
<div class="slide">
<hgroup>
<h1>Terminology</h1>
</hgroup>
<ul>
<li>Cloud computing</li>
<li>*aaS</li>
<li>DevOps</li>
<li>Cloud Native, Microservices</li>
<li>Serverless</li>
</div>
<div class="slide">
<hgroup>
<h1>What is a Cloud?</h1>
</hgroup>
<ul class="small">
<li>A different way of thinking</li>
<ul>
<li>Got your grand mum's savings under your pillow?</li>
<ul>
<li>probably not, you better have them in your bank</li>
</ul>
<li>Data is your major asset</li>
<li>you better have them in a "bank" too</li>
<li>Someone can abuse your data?<br />
<li>banks bankrupt too, sometimes – it is a risk you take</li>
<li>there is a market and a competition</li>
</li>
</ul>
<li>Outsourcing of application infrastructure</li>
<ul>
<li>Reliability and availability</li>
<li>Low costs – pay-per-use</li>
<li>Elasticity – can dynamically grow with your apps</li>
<li>CAPEX vs. OPEX</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>What is a Cloud?</h1>
</hgroup>
<ul class="small">
<li>Any app you access over the web?</li>
<li>A datacenter?</li>
<ul>
<li>Offers virtualization</li>
<li>Any company having a datacenter wants to move to</li>
</ul>
<li>Cloud provider should also offer services, such as:</li>
<ul>
<li>scalability, storage</li>
<li>Possible to configure programmatically</li>
<ul>
<li>integration to enterprise administration processes</li>
<li>usually REST interface</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Traditional Solution to Infrastructure</h1>
</hgroup>
<ul class="small">
<li>Traditional hardware model</li>
<ul>
<li>Up-front hardware investments</li>
<li>Hardware not optimally utilized</li>
</ul>
</ul>
<div class="h-drawing" style="height: 350px; margin-left: -10px"
id="17jEYye-th5U5T-N-iE1gR7f_k5Bwrk9P7z9yYC4EZlw"><img style="height: 350px; "
alt="traditional-hardware"
src="https://docs.google.com/drawings/export/svg?id=17jEYye-th5U5T-N-iE1gR7f_k5Bwrk9P7z9yYC4EZlw"
title="traditional-hardware"></div>
</div>
<div class="slide">
<hgroup>
<h1>Good Performance – Cloud Solution</h1>
</hgroup>
<ul class="small">
<li>Cloud Computing model</li>
<ul>
<li>No up-front hardware investments</li>
<li>Hardware optimally utilized</li>
</ul>
</ul>
<div class="h-drawing" style="height: 350px; margin-left: -10px"
id="1yeHPc2AqDeXanOV0Zi8MirHApMjf1Sa_2UCOt_9Avds"><img style="height: 350px; "
alt="scalable-cloud-model"
src="https://docs.google.com/drawings/export/svg?id=1yeHPc2AqDeXanOV0Zi8MirHApMjf1Sa_2UCOt_9Avds"
title="scalable-cloud-model"></div>
</div>
<div class="slide">
<hgroup>
<h1>CAPEX vs. OPEX</h1>
</hgroup>
<ul class="xx-small">
<li>Captial expenditure/capital expense (CAPEX)</li>
<ul>
<li>money to spend to buy, maintain or improve fixed assets</li>
<ul>
<li>buildings, vehicels, equipment or land</li>
</ul>
<li>have impact on costs vs. profit and tax</li>
</ul>
<div class="h-drawing" style="text-align: left; height: 200px"
id="1sdY1xuBXn_jH1t2dnBjOygeesr41TiV44Ht_Kfum6pU"></div>
<li>Operational expenditure (OPEX)</li>
<ul>
<li>ongoing costs for running a product, business, or systems</li>
<li>OPEX are entirely tax-deductible</li>
</ul>
<li>Cloud lets you trade CAPEX for OPEX</li>
<ul>
<li>No investments in data centers and infrastructures</li>
<li>You pay only when you consume resources</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Cloud Computing Concepts</h1>
</hgroup>
<ul class="xx-small">
<li><b>On-demand and self-service</b></li>
<ul>
<li>Resources are provisioned as they are requested<br />and when they are required</li>
<li>No human interaction, automatic</li>
</ul>
<li><b>Broad network access</b></li>
<ul>
<li>Capabilities are available over the network</li>
</ul>
<li><b>Resource pooling</b></li>
<ul>
<li>Provider's computing resources reused by multiple tenants (multitenancy)</li>
<li>Resourcces are dynamically assigned/re-assigned according to demand</li>
<li>Computing resources: CPU, memory, storage, network</li>
</ul>
<li><b>Scalability and elasticity</b></li>
<ul>
<li>Infrastructure may grow and shrink according to needs</li>
<li>Automatic or manual</li>
</ul>
<li><b>Measured service</b></li>
<ul>
<li>Resource usage can be monitored, controlled and reported</li>
</ul>
<li><b>Pay-per-use</b></li>
<ul>
<li>Consumers only pay for resources when they use them</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Cloud Computing Concepts (Cont.)</h1>
</hgroup>
<ul class="small">
<li>Service Models (aka Cloud Layers)</li>
<ul>
<li>IaaS – Infrastructure as a Service</li>
<li>PaaS – Platform as a Service, Serverless</li>
<ul>
<li>MWaaS, DBaaS, ...</li>
<li>FaaS</li>
</ul>
<li>SaaS – Software as a Service</li>
</ul>
<li>Deployment Models</li>
<ul>
<li>Public Cloud</li>
<li>Private Cloud</li>
<li>Hybrid Cloud</li>
</ul>
</ul>
</div>
</section>
<div class="slide outline"></div>
<section>
<header>Cloud Architecture</header>
<section>
<header>Service Models</header>
<div class="slide">
<hgroup>
<h1>Service Models</h1>
</hgroup>
<img style="width: 750px; margin-left: 10px; margin-top: 60px" src="img/cloud-service-models.png" />
</div>
<div class="slide">
<hgroup>
<h1>IaaS: Infrastructure as a Service</h1>
</hgroup>
<ul class="xx-small">
<li>Usage</li>
<ul>
<li>Predefined shapes of compute instances (e.g. micro, small, large, extra-large)</li>
<ul>
<li>for example: RedHat 7.8, 613 MB of memory, 1 TB block storage</li>
</ul>
<li>Pay-per-use – pay for resources you use (time or amount)</li>
<ul>
<li>no up-front costs</li>
</ul>
</ul>
<li>IaaS Services Examples</li>
<ul>
<li>Load balancer</li>
<li>Autoscaling</li>
<li>Connectivity with on-premise network</li>
<li>Resource monitoring</li>
</ul>
<li>IaaS providers</li>
<ul>
<li>Amazon EC2, GoGrid, Rackspace, OpenNebula, Google Cloud, Oracle OCI, ...</li>
</ul>
</ul>
<!-- <div class="h-drawing" style="height: 270px; padding-left: 220px; margin-top: -250px;" alt="Web 2.0 web architecture" id="1GnYOqlP5qCv8LMyd3yuLNdfsymoDKVRhYrSvorh4suw"></div> -->
</div>
<div class="slide">
<hgroup>
<h1>PaaS: Platform as a Service</h1>
</hgroup>
<ul class="x-small">
<li>Usage</li>
<ul>
<li>Choose software platform, e.g., JEE, .NET, Python, etc.</li>
<li>Pay-per-use – pay for the resources you use; no up-front costs</li>
<li>Cloud native, microservices, containers</li>
</ul>
<li>PaaS features</li>
<ul>
<li>Serverless</li>
<li>Auto Scalling and Load balancing</li>
<li>Local development environment</li>
<li>Administration API</li>
</ul>
<li>PaaS providers</li>
<ul>
<li>Google App Engine – first PaaS service</li>
<li>Today, mostly Kubernetes, Google, Heroku, Azure, AWS, Oracle</li>
</ul>
</ul>
<!-- <div class="h-drawing" style="height: 270px; padding-left: 220px; margin-top: -220px;" alt="Platfor as a Service example" id="1WPWgHjgD4Ew-bljCiWeyTvbNuFWs_dXnjhI333vtVbs"></div> -->
</div>
<div class="slide">
<hgroup>
<h1>SaaS: Software as a Service</h1>
</hgroup>
<ul class="x-small">
<li>Software delivery model for applications hosted in the cloud</li>
<ul>
<li>typically software for end-users</li>
<li>services accessed using a web browser</li>
<li>provides API for programmatic access</li>
</ul>
<li>SaaS characteristics</li>
<ul>
<li>Typically build on top of IaaS or PaaS</li>
<li>Configurable and customizable modern Web applications</li>
<li>Usually basic version for free, need to pay for "pro" version</li>
<li>Global availability - any computer, any device</li>
<li>Easy management - automatic and fast updates</li>
<li>Pay-per-use – pay for the time you use</li>
</ul>
<li>SaaS providers</li>
<ul>
<li>Google Apps, Salesforce, ...</li>
</ul>
</ul>
</div>
</section>
<div class="slide outline"></div>
<section>
<header>Multitenancy</header>
<div class="slide">
<hgroup>
<h1>Multitenancy</h1>
</hgroup>
<ul class="x-small">
<li>Architectural approach where resources are shared between multiple tenants or consumers</li>
<li>Implications</li>
<ul>
<li>Centralization of infrastructure in locations with lower costs</li>
<li>Peak-load capacity increases</li>
<li>Utilisation and efficiency improvements for systems that are not well utilised</li>
</ul>
<li>Sharing options</li>
<ul>
<li>Shared Everything</li>
<li>Shared Infrastructure</li>
<ul>
<li>Virtual Machines</li>
<li>OS "virtualization"</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Shared Everything</h1>
</hgroup>
<ul class="x-small">
<li>Resources are shared between all tenants or consumers</li>
<ul>
<li>tenant: a service consumer</li>
</ul>
<li>Common for the SaaS model</li>
<li>The application should provide tenant isolation</li>
<li>Data for multiple tenants is stored in the same database tables</li>
</ul>
<div class="h-drawing" style="height: 220px; margin-left: 0px; margin-top: 20px"
alt="Web 2.0 web architecture" id="17wNMQNs3vf2yyE0VzFhGbnNTjJBKKONbeS9jijYHbN4"></div>
</div>
<div class="slide">
<hgroup>
<h1>Shared Infrastructure: Virtual Machines</h1>
</hgroup>
<ul class="x-small">
<li>Infrastructure shared via virtual machines</li>
<ul>
<li>each tenant has its own virtual environment</li>
<li>Isolation provided by hypervisor</li>
<ul>
<li>hypervisor: virtual machine manager, runs virtual machines</li>
</ul>
<li>Resource contention depends on VM capability and configuration</li>
<li>Adds an additional layer and processes to run and manage</li>
</ul>
</ul>
<div class="h-drawing" style="height: 280px; margin-left: 0px; margin-top: 10px"
alt="Web 2.0 web architecture" id="1y5TMPeDujUG9aBUZ8Tf8a5vwrqT3LpjmYjb_HS5Ux1E"></div>
</div>
<div class="slide">
<hgroup>
<h1>Shared Infrastructure: OS Virtualization</h1>
</hgroup>
<ul class="x-small">
<li>Infrastructure shared via OS Virtualization</li>
<ul>
<li>Each tenant has its own processing zone</li>
<li>Isolation provided by the operating system</li>
<li>Resource contention depends on zone configuration</li>
<li>No VMs to run and manage, no abstraction layer between app & OS</li>
</ul>
</ul>
<div class="h-drawing" style="height: 280px; margin-left: 0px; margin-top: 10px"
alt="Web 2.0 web architecture" id="1OIg4KQRqj_G3YUsoCFQS1E4JOpxx3Yg63PGeRMhkupE"></div>
</div>
</section>
</section>
<div class="slide outline"></div>
<section>
<header>Infrastructure as a Service</header>
<div class="slide">
<hgroup>
<h1>Overview</h1>
</hgroup>
<ul class="x-small">
<li>Infrastructure = environment where your app is running</li>
<li>Tenancy = your "space" in the cloud</li>
<li>What you need</li>
<ul>
<li>Servers (compute instances) to run your app in a location (region)</li>
<li>Connectivity</li>
<ul>
<li>Private network for intra-communication</li>
<li>Public network for internet communication</li>
<li>Firewall (security) rules</li>
<li>Route tables</li>
</ul>
<li>Storage</li>
<ul>
<li>Operating system</li>
<li>Your app data</li>
</ul>
<li>Identity Management</li>
<ul>
<li>Who and how can access and control your tenancy</li>
</ul>
<li>Monitoring, Logging, Auditing</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Region</h1>
</hgroup>
<ul class="xx-small">
<li>Region = location on a planet where cloud data centers are located</li>
<img src="img/cloud-regions.png" style="width: 650px; padding-bottom: 10px" />
<li>Why location matters...</li>
<ul>
<li>Latency - your users should be close to your app</li>
<li>Regulations - your data should be stored in EU</li>
<li>Connectivity to external providers</li>
<ul>
<li>Such as other cloud vendors</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Datacenters</h1>
</hgroup>
<ul class="xx-small">
<li>Datacenter (aka Availability Domain – AD)</li>
<ul>
<li>Computing resources in a location within a region</li>
<li>One or more datacenters exsit in a region</li>
<ul>
<li>They are completely de-correlated, independent</li>
<li>They have separated power supply, do not share underlying infrastructure</li>
<li>If one DC fails, the other one is up and running</li>
</ul>
</ul>
<img src="img/cloud-iaas-layers.png" style="width: 650px; padding-top: 0px" />
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Off-box Network Virtualization</h1>
</hgroup>
<ul class="xx-small">
<li>Gen 1.0 Cloud, inefficient Resource Sharing</li>
<ul>
<li>On-Premise virtualization to share resources amongst multiple tenants in the cloud.</li>
<img src="img/network-virt-gen10.png" style="width: 650px; padding-top: 0px" />
</ul>
<li>Gen 2.0 Cloud</li>
<ul>
<li>Smart-NIC accelerated SR-IOV (Single Root I/O Virtualization)</li>
<ul>
<li>Networking is a specialized function, needs hardware/sillicon to accelerate it</li>
</ul>
<img src="img/sr-iov.png" style="width: 450px; padding-top: 0px" />
</ul>
</ul>
</div>
<div class="slide outline"></div>
<section>
<header>Networking</header>
<div class="slide">
<hgroup>
<h1>Virtual Cloud Network</h1>
</hgroup>
<ul class="xx-small">
<li>VCN = a private network in a <b>single region</b> in which your instances reside</li>
<li>A a single and contigous IPV4 CIDR block of your choice</li>
<ul>
<li>CIDR (classless inter-domain routing) notation</li>
<li>IP address:</li>
<ul>
<li>network prefix (the most significant bits) and</li>
<li>interfaces on the network (least significant bits) ~ network hosts</li>
</ul>
<li>Example: <code>192.168.1.0/24</code></li>
<ul>
<li>IP range: <code>192.168.1.0</code> - <code>192.168.1.255</code></li>
</ul>
</ul>
<li>You further create subnets on a VCN to organize your instances</li>
<ul>
<li>The subnets must be "within" the VCN, they can span across ADs</li>
<li>Example: using <code>27</code> bits for a subnet mask allow for 8 subnets</li>
<ul>
<li><code>192.168.1.0/27</code>, <code>192.168.1.32/27</code>, <code>192.168.1.64/27</code>,
...</li>
<li>Each subnet can have 32 hosts</li>
</ul>
</ul>
<div class="h-drawing" style="text-align: left; height: 140px; margin-left: 0px; margin-top: 0px"
alt="CIDR network and subnets" id="1dXQa_c6etroY6oHBgXWaDg5obRiFPG4fu5n7r2os830"></div>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>VCN Routing and Security</h1>
</hgroup>
<ul class="xx-small">
<li>Private and Public subnets</li>
<ul>
<li>Public can communicate in/out from/to Internet</li>
<li>Internet traffic routed to public subnet</li>
<li>Private can be completely isolated or communicate to Internet only</li>
</ul>
<li>Route tables</li>
<ul>
<li>Required to route across subnets and in/out from the Internet</li>
</ul>
<li>Security</li>
<ul>
<li>Control access to/from the subnet</li>
</ul>
<img src="img/vcn-example.png" style="height: 250px; padding-top: 0px; padding-left: 10px" />
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Peering</h1>
</hgroup>
<ul class="xx-small">
<li>Local Peering</li>
<ul>
<li>Connecting two VCNs in a region</li>
</ul>
<li>Remote Peering</li>
<ul>
<li>Connecting two VCNs across regions</li>
</ul>
<li>Connectivity with on-premise datacenter</li>
<ul>
<li>Fast connection needs to be in place</li>
<li>Secure VPN needs to be established</li>
</ul>
<img src="img/peering.png" style="height: 250px; padding-top: 10px; padding-left: 10px" />
</ul>
</div>
</section>
<div class="slide outline"></div>
<section>
<header>Compute</header>
<div class="slide">
<hgroup>
<h1>Compute Instances</h1>
</hgroup>
<ul class="xx-small">
<li>Shape = amount of memory and CPU an instance is using</li>
<ul>
<li>There are classes of shapes that you can choose from</li>
<li>Standard and HPC/GPU shapes</li>
</ul>
<li>Virtual Machine (VM) – multi-tenant model</li>
<ul>
<li>A hypervisor to virtualize the underlying Bare Metal server into smaller VMs</li>
</ul>
<li>Bare Metal (BM) – single-tenant model</li>
<ul>
<li>Direct hardware access, full bare metal server</li>
<li>Types of workloads: performance intensive, require a specific hypervisor</li>
</ul>
<li>Dedicated VM Hosts (DVM) – single-tenant model</li>
<ul>
<li>VM instances running on dedicated single-tenant servers</li>
<li>Not shared with other customers</li>
</ul>
<img src="img/compute-instances.png"
style="text-align: right; height: 120px; padding-top: 5px; margin-bottom: -20px; padding-left: 10px" />
<li>States: start, stop, reboot, terminate</li>
<ul>
<li>Billing pauses in STOP state but depends on shape</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Image</h1>
</hgroup>
<ul class="xx-small">
<li>Image</li>
<ul>
<li>A template of a virtual hard drive with OS</li>
<li>Other software, libraries, configurations, etc.</li>
</ul>
<li>Stored on a boot volume</li>
<li>Base images are provided</li>
<ul>
<li>CentOS, Ubuntu, Windows Server, Oracle Linux, RedHat, etc.</li>
<li>Some may require licence costs</li>
</ul>
<li>Custom images</li>
<ul>
<li>You can create a custom image from the base image</li>
<li>Specific packages, libraries or custom configuiration</li>
<li>You store the image in the object storage</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Autoscaling</h1>
</hgroup>
<ul class="xx-small">
<li>Instance configuration</li>
<ul>
<li>OS image, metadata, shape, vNICs, storage, subnets</li>
<li>Apply configuration to multiple instances at the same time</li>
<ul>
<li>You can manage them all together (start, stop, terminate)</li>
</ul>
<img src="img/instance-config-pool.png" style="height: 100px; margin-top: 0px" />
</ul>
<li>Autoscaling</li>
<ul>
<li>Automatically adjust a number of compute instances in an instance pool</li>
<li>Control using performance metrics such CPU or memory utilization</li>
<li>cooldown period – time between scale in and scale out (e.g. 300 seconds)</li>
</ul>
<img src="img/autoscaling.png" style="height: 170px; margin-top: 0px" />
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Load Balancer</h1>
</hgroup>
<ul class="xx-small">
<li>Managed service</li>
<ul>
<li>Health check – checks health status of backends (TCP, HTTP)</li>
<li>Algorithm – round-robin, IP hash, least connections</li>
</ul>
<li>Supports protocols</li>
<ul>
<li>TCP, HTTP 1.1, HTTP/2, WebSocket, SSL termination, end-to-end SSL</li>
<li>Supports sticky sessions (sessions persistence)</li>
</ul>
<li>High Availability</li>
<ul>
<li>Primary and stand-by LB</li>
<li>Each LB is in different AD</li>
<li>Failover uses floating IP</li>
</ul>
<img src="img/load-balancer.png" style="height: 320px; margin-left: 300px; margin-top: -120px" />
</ul>
</div>
</section>
<div class="slide outline"></div>
<section>
<header>Storage</header>
<div class="slide">
<hgroup>
<h1>Object Storage</h1>
</hgroup>
<ul class="xx-small">
<li>Types of data to store</li>
<ul>
<li>Storage for unstructured data (images, media files, logs, backups)</li>
<li>Data managed as objects, provides API using HTTP verbs</li>
</ul>
<li>Namespace</li>
<ul>
<li>Logical entity that serves as top-level container for all bueckts and objects</li>
<li>Each tenancy is provided one unique namespace</li>
</ul>
<li>Bucket</li>
<ul>
<li>A logical container for storing objects</li>
<li>Bucket names must be unique within tenancy</li>
<li>Hot bucket – standard, can be accessed immediatelly</li>
<li>Cold bucket – rarely accessed data, need to be restored</li>
<ul>
<li>Minimum retention, such as 90 days</li>
<li>Time to First Byte (TTFB) is in hours, e.g. 4 hours</li>
</ul>
</ul>
<li>Object and metadata</li>
<ul>
<li>data managed as objects regardless data type</li>
</ul>
<li>Example object URL path:</li>
<ul>
<li class="no-bullet"><code>/n/<namespace>/b/<bucket>/o/<object_name></code>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Block Storage</h1>
</hgroup>
<ul class="xx-small">
<li>Local NVMe SSD device</li>
<ul>
<li>Locally attached device, provided by some shapes, 200K IOPS - 1M IOPS</li>
<li>Workloads that require high storage performance</li>
<li>usually no RAID, snapshots, backups</li>
</ul>
<li>Block volumes</li>
<ul>
<li>Reside in storage servers</li>
<li>NVMe SSD based, up to 35K IOPS</li>
<li>Data stored on block volumes beyond the lifespan of compute instance</li>
<li>Multiple replicas across multiple storage servers</li>
</ul>
<li>File Storage</li>
<ul>
<li>Network file server (NFS)</li>
<li>Client mounts a <b>mount target</b> (NFS endpoint) and an <b>export path</b></li>
<li>Example</li>
<ul>
<li class="no-bullet"><code>sudo mount 10.0.0.6/example1/path /mnt/mountpointA</code>
</ul>
</ul>
</ul>
</div>
</section>
<!-- <div class="slide">
<hgroup>
<h1>Terminology (1)</h1>
</hgroup>
<ul class="xx-small">
<li>Region</li>
<ul>
<li>A localized geographical area</li>
<li>A cloud provider usually has multiple regions around the world.</li>
</ul>
<li>Availability Domain</li>
<ul>
<li>A datacenter in a region; there can be more AD in a region</li>
</ul>
<li>Tenancy</li>
<ul>
<li>Isolated partition where a customer creates and organizes cloud resources.</li>
</ul>
<li>Instance</li>
<ul>
<li>Compute host running in the cloud</li>
</ul>
<li>Bare Metal</li>
<ul>
<li>Physical host that run directly on bare metal servers without hypervisor</li>
</ul>
<li>Shape/Class</li>
<ul>
<li>Amount of computing resources allocated to the instance</li>
<li>CPUs, Memory, Local Disk, Network Bandwidth, Number of VNICs</li>
</ul>
<li>Image</li>
<ul>
<li>A template of a virtual hard drive that defines operating system and other software for an instance.</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Terminology (2)</h1>
</hgroup>
<ul class="xx-small">
<li>Instance Pool</li>
<ul>
<li>A group of instances</li>
</ul>
<li>Virtual Cloud Network (VCN)</li>
<ul>
<li>A virtual network in which instances run</li>
<li>It includes: <b>subnets</b>, <b>route tables</b>, <b>firewall rules</b>, <b>gateways</b></li>
</ul>
<li>Block Volume</li>
<ul>
<li>A virtual disk providing persistent storage</li>
<li>It can be used as a volume attached to the instance</li>
</ul>
<li>Object Storage</li>
<ul>
<li>Allows to store and manage data as objects in logical containers (<b>buckets</b>)</li>
<li>The data can be of any type and are usually of large size</li>
<li>The data does not change frequently</li>
<li>Examples: data backup, storing unstructured data, sensor-generated data</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Access and Usage</h1>
</hgroup>
<ul class="x-small">
<li>Layers</li>
<ul>
<li>Cloud Infrastructure → REST API → CLI, Web Console, other tools</li>
</ul>
<li>Key pair</li>
<ul>
<li>Authentication mechanism using <b>public</b> and <b>private</b> key</li>
<li>public key is uploaded to an instance, a client uses the private key to authenticate</li>
<li>Example: ssh using key authentication to access ssh deamon running in Linux</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>IaaS Example</h1>
</hgroup>
<img src="img/example-iaas.png" style="width: 700px; padding: 20px"></img>
</div> -->
<div class="slide outline"></div>
<section>
<header>Infrastructure as Code</header>
<div class="slide">
<hgroup>
<h1>Overview</h1>
</hgroup>
<ul class="x-small">
<li>Definition</li>
<ul>
<li>Application envs (in a cloud) managed via definition files</li>
<li>Version control, team development, scripting, etc.</li>
</ul>
<li>Major Technologies</li>
<ul>
<li><b>Configuration Management Tools</b></li>
<ul>
<li>install and manage software on machines that already exist</li>
<li>Examples: Ansible, Chef, Puppet</li>
</ul>
<li><b>Abstraction of cloud infrastructure</b></li>
<ul>
<li>Terraform</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Terraform</h1>
</hgroup>
<ul class="x-small">
<li>Higher-level abstraction of the datacenter and associated services</li>
<li>Supports many service providers</li>
<ul>
<li>Google, Microsoft, Oracle, AWS</li>
</ul>
<li>Steps</li>
<ol>
<li>Description of resources in Hashicorp Configuration Language (HCL)</li>
<ul>
<li>instances, networks, firewall rules, routing tables, etc. </li>
</ul>
<li>Terraform generates execution plan to reach the desired state</li>
<li>Terraform executes the plan to reach the desired state; can generate incremental execution
plan</li>
</ol>
</div>
</section>
</section>
</body>
</html>