2. 程式人生 > 其它 >雲端計算第四章

雲端計算第四章

阿新 • • 發佈：2022-03-17

本篇文章是對課程大型軟體系統設計與體系結構(雙語)【又名：雲端計算】第四章的課堂內容總結，適用於大連交通大學。

Fundamental Concepts and Models（基本概念和模型）

Roles and Boundaries 角色與邊界

Cloud Provider 雲提供者

  • provides cloud-based IT resources
  • as per agreed upon SLA guarantees
  • ensure the on-going operation

Cloud Consumer 雲使用者

  • an organization (or a human) that has a formal contract or arrangement
    to access a cloud service

Cloud Service Owner 雲服務擁有者

  • The person or organization that legally owns a cloud service

Cloud Resource Administrator 雲資源管理者

  • person or organization responsible for administering a cloud-based IT resource (including cloud services).

Additional Roles 其他角色

  • Cloud Auditor 雲審計者
  • Cloud Broker 雲代理
  • Cloud Carrier 雲運營商

Organizational Boundary 組織邊界

  • represents the physical perimeter that surrounds a set of IT resources that are owned and governed by an organization.

Trust Boundary 信任邊界

  • a logical perimeter that typically spans beyond physical boundaries to represent the extent to which IT resources are trusted
## Cloud Characteristics 雲特徵
  • on-demand usage 按需使用
  • ubiquitous access 隨處訪問
  • multitenancy (and resource pooling)
    多租戶（和資源池）
  • Elasticity 彈性
  • measured usage 可測量的使用
  • resiliency 可恢復性

On-Demand Usage 按需使用

  • A cloud consumer can unilaterally access cloud-based IT resources giving the cloud consumer the freedom to self-provision these IT resources.
  • on-demand self-service usage, this characteristic enables the service-based and usage-driven features found in mainstream clouds

Ubiquitous Access 無處不在地訪問

  • represents the ability for a cloud service to be widely accessible.

Multitenancy (and Resource Pooling) 多租戶

  • The characteristic of a software program that enables an instance of the program to serve different consumers (tenants) whereby each is isolated from the other
  • Through the use of multitenancy technology, IT resources can be dynamically assigned and reassigned, according to cloud service consumer demands.

Elasticity彈性

  • the automated ability of a cloud to transparently scale IT resources, as required in response to runtime conditions or as pre-determined by the cloud consumer or cloud provider

Measured Usage可測量的使用

  • represents the ability of a cloud platform to keep track of the usage of its IT resources, primarily by cloud consumers.

Resiliency 可恢復性

  • a form of failover that distributes redundant implementations of IT resources across physical locations.

Cloud Delivery Models 雲交付模型

represents a specific, pre-packaged combination of IT resources offered by a cloud provider.

  • Infrastructure-as-a-Service (IaaS)
    基礎設施作為服務
  • Platform-as-a-Service (PaaS)
    平臺作為服務
  • Software-as-a-Service (SaaS)
    軟體作為服務

infrastructure-as-a-Service (IaaS)

  • The IaaS delivery model represents a self-contained IT environment comprised of infrastructure-centric IT resources that can be accessed and managed via cloud service-based interfaces and tools.
  • This environment can include hardware, network, connectivity, operating systems, and other “raw” IT resources.
  • infrastructure-as-a-Service (IaaS)

Platform-as-a-Service (PaaS)

  • The PaaS delivery model represents a pre-defined “ready-to-use” environment typically comprised of already deployed and configured IT resources.

The cloud consumer wants to extend on-premise environments into the cloud for scalability and economic purposes.
The cloud consumer uses the ready-made environment to entirely substitute an on-premise environment.
The cloud consumer wants to become a cloud provider and deploys its own cloud services to be made available to other external cloud consumers.

Software-as-a-Service (SaaS)

  • A software program positioned as a shared cloud service and made available as a “product” or generic utility represents the typical profile of a SaaS offering.
A comparison of typical cloud delivery model control levels
Typical activities carried out by cloud consumers and cloud providers in relation to the cloud delivery models
用火鍋類比雲端計算交付模型
第一層IaaS
第二層PaaS

Cloud Deployment Models 雲部署模型

  • A cloud deployment model represents a specific type of cloud environment, primarily distinguished by ownership, size, and access.

Public cloud 公有云
Community cloud 社群雲
Private cloud 私有云
Hybrid cloud 混合雲

Public Clouds 公有云

  • a publicly accessible cloud environment owned by a third-party cloud provider.
  • The cloud provider is responsible for the creation and on-going maintenance of the public cloud and its IT resources.
Public Clouds

Community Clouds 社群雲

  • A community cloud is similar to a public cloud except that its access is limited to a specific community of cloud consumers.
  • Membership in the community does not necessarily guarantee access to or control of all the cloud’s IT resources. Parties outside the community are generally not granted access unless allowed by the community.
Community Clouds

Private Clouds 私有云

  • A private cloud is owned by a single organization.
  • With a private cloud, the same organization is technically both the cloud consumer and cloud provider

    1.a separate organizational department typically assumes the responsibility for provisioning the cloud (and therefore assumes the cloud provider role)
    2.departments requiring access to the private cloud assume the cloud consumer role

Private Clouds

Hybrid Clouds 混合雲

  • A hybrid cloud is a cloud environment comprised of two or more different cloud deployment models.

summary

1.Fundamental Concepts

  • Cloud Provider雲提供者
  • Cloud Consumer雲使用者
  • Cloud Service Owner雲服務擁有者
  • Cloud Resource Administrator雲資源管理者
  • Organizational Boundary組織邊界
  • Trust Boundary信任邊界

2.Cloud Characteristics

  • on-demand usage按需使用
  • ubiquitous access泛在連線
  • multitenancy (and resource pooling)多租戶和資源池
  • Elasticity彈性
  • measured usage可測量的使用
  • Resiliency可恢復性

3.Cloud Delivery Models

  • Infrastructure-as-a-Service (IaaS)基礎設施作為服務
  • Platform-as-a-Service (PaaS) 平臺作為服務
  • Software-as-a-Service (SaaS) 軟體作為服務

4.Cloud Deployment Models

  • Public cloud公有云
  • Community cloud社群雲
  • Private cloud私有云
  • Hybrid cloud混合雲

個人部落格本文地址：https://kohler19.gitee.io/2022/03/17/cloud-computing2/

相關推薦

雲端計算第四章

本篇文章是對課程大型軟體系統設計與體系結構(雙語)【又名：雲端計算】第四章的課堂內容總結，適用於大連交通大學。

Cloud Computing Chapter3 (雲端計算第三章)

本篇文章是對課程大型軟體系統設計與體系結構(雙語)【又名：雲端計算】的課堂內容總結，適用於大連交通大學。

計算機組成原理期末第四章【計算部分】

Cache計算 佔坑待補· 漢明碼的計算 1）求漢明碼 書寫的步驟： 2）檢查第幾位出錯：

MATLAB 第四章 符號計算

課程匯入 數值計算：必須先對變數賦值，然後才能參與運算，運算結果是數值。

c語言程式設計第五版課後答案譚浩強 第四章課後答案

第四章 選擇結構程式設計 1. 什麼是算術運算？什麼是關係運算？什麼是邏輯運算？

[ APUE ] 第四章 檔案和目錄

1. stat,fstat,fstatat,lstat函式 #include <sys/types.h> #include <sys/stat.h> #include <unistd.h>

第四章 常用API（上）

4.1、Object類 描述：該類是所有類的最終根類 方法 描述 public boolean equals(Object obj)

Java講義第四章學習筆記

chapter 4流程控制與陣列 4.1順序結構 　　順序結構就是程式從上到下逐行地執行，中間沒有任何判斷和跳轉。

第四章 深入類和物件

4.1 鴨子型別和多型 class Cat(object): def say(self): print("i am a cat") class Dog(object):

【PYTEST】第四章Fixture

知識點： 利用fixture共享資料 conftest.py共享fixture 使用多個fixture fixture作用範圍 usefixture

第四章 Redis的事務、鎖及管理命令

一.事務介紹 1.Redis的事務與關係型資料庫中的事務區別 1）在MySQL中講過的事務，具有A、C、I、D四個特性

C++第四章經驗整理2

We have to declare the operator function by using the operator, operator sign. Example “operator +” where the operator is a keyword and + is the symbol need to be overloaded.

演算法筆記-第四章簡單貪心題解

背景 目前演算法筆記的學習已經進展到第四章，下面會記錄第四章貪心演算法的兩道題解。寫這篇部落格的目的也是鼓勵自己繼續學習下去。

第三天 第四章 元組

與列表不同的是，元組的元素是不可變的。因此它也被稱為不可變的列表。列式上，所有元素都放在小括號中，相鄰元素以逗號分隔。在內容上，可以將python支援的型別都放入元組中，在同一個元組中，元素型別可以不同。通

第三天 第四章 字典

字典與列表類似，也是可變序列，但它是無序的可變序列，儲存的內容以“鍵值對”的形式存放。一個鍵（key）對應一個值（value）。鍵是唯一的，而值可以有多個，也可以重複。

【C++】《Effective C++》第四章

第四章 設計與宣告 條款18：讓介面容易被正確使用，不易被誤用 請記住 好的介面很容易被正確使用，不容易被誤用。你應該在你的所有介面中努力達到這些性質。

第四章 NFS故障與實時同步

一、統一使用者 1.httpd的使用者 Apache-->www 2.NFS掛載目錄 anonuid=666,anongid=666 3.rsyncd的使用者 nfsnobody-->www

第四章 異常

4.1 異常 Erlang通過throw(Exception)、exit(Exception)、erlang:error(Exception)來丟擲異常。 Erlang捕獲異常的兩種方式：

《動手學深度學習》mxnet版/第四章學習筆記

第四章 概括深度學習計算的各個重要組成部分，如模型構造、引數的訪問和初始化等，自定義層，讀取、儲存和 使用GPU

SpringMVC 學談（第四章）

寫在前面：分享技術，共同進步，有不足請見諒，相關意見可評論告知~ 程式設計路漫之遠兮，運架構式之簡化；