Models and Architecture - Connected Services and Cloud Computing

Slide 1

Slide 1 text

  1 / 51 Connected Services Models & Architecture Dr.-Ing. Eueung Mulyana https://eueung.github.io/ET3010 ET-3010 | Attribution-ShareAlike CC BY-SA

Slide 2

Slide 2 text

Outline Basic Model Start Small - GMail Model Mapping Inside the Cloud Data Center Components, Models & Interactions 2 / 51

Slide 3

Slide 3 text

  Connected Services Basic Model 3 / 51

Slide 4

Slide 4 text

4 / 51 Connected Services & Cloud Model

Slide 5

Slide 5 text

5 / 51 System-Boxes inside Cloud Nested Clouds Zoom In

Slide 6

Slide 6 text

6 / 51 Historically, before the rise of CC, the term Cloud was very common to be used to refer to Networks or Interconnected- Systems. Depending on context, Cloud in this lecture may refer to both of them. In CC concept, Network is a part of CC, but Network is not used only for CC. Cloud (without "Computing") is sometimes used interchangebly with Networks or the Internet Cloud vs. Network

Slide 7

Slide 7 text

  GMail Service Start Small 7 / 51

Slide 8

Slide 8 text

8 / 51 GMail Service The Story of Send 

Slide 9

Slide 9 text

9 / 51 GMail Service The Story of Send 1. Sender 2. Sender's Provider (ISP) 3. Backbone 4. Data Center - Front Server 5. Data Center - GMail Backend (Cloud) 6. Backbone 7. Recipient's Provider 8. Recipient

Slide 10

Slide 10 text

  Model Mapping 10 / 51

Slide 11

Slide 11 text

(1) Sender e.g. Customer of an ISP (TLKM) 11 / 51

Slide 12

Slide 12 text

(2) Sender's ISP e.g. TLKM 12 / 51

Slide 13

Slide 13 text

13 / 51 (1) and (2)

Slide 14

Slide 14 text

(3) Outgoing Backbone - e.g. TLKM Peering / Upstream Channels 14 / 51

Slide 15

Slide 15 text

(4) Google DC - Front Server 15 / 51

Slide 16

Slide 16 text

(4) Google DC - Front Server 16 / 51

Slide 17

Slide 17 text

(4) Google DC - Front Server 17 / 51

Slide 18

Slide 18 text

(5) Google DC - GMail Backend 18 / 51

Slide 19

Slide 19 text

(5) Google DC - GMail Backend 19 / 51

Slide 20

Slide 20 text

20 / 51 (3), (4) and (5)

Slide 21

Slide 21 text

(6) Backbone - e.g. Google's Peering / Upstream Channels 21 / 51

Slide 22

Slide 22 text

(7) Receipient's ISP e.g. XL 22 / 51

Slide 23

Slide 23 text

(8) Recipient e.g. Customer of an ISP (XL) 23 / 51

Slide 24

Slide 24 text

24 / 51 (6), (7) and (8)

Slide 25

Slide 25 text

  Inside the Cloud 25 / 51

Slide 26

Slide 26 text

26 / 51 Providers' Cloud

Slide 27

Slide 27 text

An Example of Providers' Network (SPIRENT) 27 / 51

Slide 28

Slide 28 text

28 / 51 Google's Cloud

Slide 29

Slide 29 text

Mayes County, Oklahoma - Sunset & Landscape 29 / 51

Slide 30

Slide 30 text

Council Blu s, Iowa - Inside Google's Campus Network Room 30 / 51

Slide 31

Slide 31 text

Mayes County, Oklahoma - Rack, 4 Switches, Colorful Cables 31 / 51

Slide 32

Slide 32 text

Douglas County, Georgia - Colorful Pipes & G-Bike 32 / 51

Slide 33

Slide 33 text

33 / 51 Google DC 2004 From Jupiter Rising:... (Arjun Singh et.al.) SIGCOMM 2015

Slide 34

Slide 34 text

34 / 51 Transport & Interconnection Backbone

Slide 35

Slide 35 text

Sumarine Cables Map 35 / 51

Slide 36

Slide 36 text

36 / 51 Google's Cloud Notes

Slide 37

Slide 37 text

Backbone in the Cloud - Google's Global DC Facility 37 / 51

Slide 38

Slide 38 text

  Data Center 38 / 51

Slide 39

Slide 39 text

39 / 51 Literal: Facility to store and process data. A large group of networked computer servers typically used by organizations for the remote storage, processing, or distribution of large amounts of data (Google Def). A datacenter is a (centralized) facility, either physical or virtual, for the storage, management, and dissemination of data and information organized around a particular body of knowledge or pertaining to a particular business (techtarget.com). A data center is a facility that centralizes an organization's IT operations and equipment, and where it stores, manages, and disseminates its data. Data centers house a network's most critical systems and are vital to the continuity of daily operations (paloaltonetworks.com). Major Functional Components Compute (Servers) Storage Network

Slide 40

Slide 40 text

40 / 51 Data Center Example A Look into a Google Data Center 

Slide 41

Slide 41 text

  Components, Models & Interactions 41 / 51

Slide 42

Slide 42 text

Legacy Service Provider Prior to CS Era 42 / 51

Slide 43

Slide 43 text

Connected Service Provider CS Era 43 / 51

Slide 44

Slide 44 text

Connected Service Provider Part of the Global Cloud 44 / 51

Slide 45

Slide 45 text

Connected Service Provider Simpli cation 45 / 51

Slide 46

Slide 46 text

Connected Things CS is not only for Human, But also for Arbitrary Things 46 / 51

Slide 47

Slide 47 text

Connected Things Simpli cation 47 / 51

Slide 48

Slide 48 text

48 / 51 Connected Services Components Hardware Devices + Infrastructure Software System Client App + Backend Software System UI + Data (Local+Remote) + Process (Local+Remote)

Slide 49

Slide 49 text

  Refs 49 / 51

Slide 50

Slide 50 text

References 1. http://www.google.com/about/datacenters 2. http://www.google.com/green/storyofsend (N/A) 3. Urs Hoelzle, OpenFlow @ Google, ONS 50 / 51

Slide 51

Slide 51 text

  51 / 51 END Dr.-Ing. Eueung Mulyana https://eueung.github.io/ET3010 ET-3010 | Attribution-ShareAlike CC BY-SA