logo
  • Blog
  • The Cloud
  • DevOps
  • Trending
    • Blockchain
    • Bitcoin
  • How To
  • Kubernetes

 

  • Basic of Cloud Computing
  • What is Cloud Computing?
  • Benefit of Cloud Computing
  • History and Vision of Cloud Computing
  • How Cloud Computing works?
  • Characteristics of Cloud Computing as per NIST
  • Cloud Computing Standards
  • Cloud Computing Reference model
  • Cloud Computing conceptual reference model
  • Cloud Consumer
  • Cloud Providers
  • Cloud Auditor
  • Cloud Broker
  • Cloud Carrier
  • Scope of Control between Provider and Consumer
  • Types of Cloud Computing
  • Based on Cloud Service models
  • ↠ Infrastructure as a Service (IaaS)
  • ↠ Platform as a Service (PaaS)
  • ↠ Software as a Service (SaaS)
  • ↠ Network as a Service (NaaS)
  • Anything as a Service (XaaS)
  • ↠ Testing as a Service
  • ↠ Storage as a Service
  • ↠ Database as a Service
  • ↠ Information as a Service
  • ↠ Integration as a Service
  • ↠ Security as a Service
  • Based on Deployment models
  • ↠ Private Cloud
  • ↠ Public Cloud
  • ↠ Hybrid Cloud
  • ↠ Distributed Cloud
  • ↠ Community Cloud
  • Public Cloud vs Private Cloud
  • Cloud Computing Issues and challenges
  • Threats and opportunities of the cloud
  • Privacy issue in the Cloud
  • Security issue in the Cloud
  • Compliance issue in the Cloud
  • Legal issue in the Cloud
  • Sustainability issue in the Cloud
  • Introduction of Virtualization
  • What is Virtualization?
  • Fundamental concept of Compute
  • Fundamental concept of Storage
  • Fundamental concept of Networking
  • Desktop and application virtualization
  • Advantage of Virtualization
  • What is Virtual Servers?
  • Infrastructure requirement for Virtualization
  • What is Virtual LAN (VLAN)?
  • Benefits of Virtual LAN (VLAN)
  • What is Virtual SAN (VSAN)?
  • Benefits of Virtual SAN (VSAN)
  • Cloud Solutions and Services
  • Cloud Ecosystem
  • Cloud Business Process Model
  • Cloud Service Management
  • Cloud Analytics
  • Testing under control
  • Gartner’s Magic Quadrants
  • Magic Quadrants for IaaS 2016
  • Magic Quadrants for IaaS 2015
  • Magic Quadrants for IaaS 2014
  • Magic Quadrants for IaaS 2013
  • Magic Quadrants for IaaS 2012

Cloud Computing conceptual reference model

Cloud computing conceptual reference model identifies the major actors, their activities and functions in cloud computing.

Below figure 1 presents an overview of the NIST cloud reference architecture.

Figure 1 – The Conceptual Reference Model

As shown in Figure 1, the NIST cloud computing reference architecture defines five major actors: cloud consumer, cloud provider, cloud carrier, cloud auditor and cloud broker. Each actor is an entity (a person or an organization) that participates in a transaction or process and/or performs tasks in cloud computing.

Table 1 briefly lists the actors defined in the NIST cloud computing reference architecture. The general activities of the actors are discussed in further tutorial.

Actors in Cloud Computing

SNO Actor Definition
1 Cloud Consumer A person or organization that maintains a business relationship with, and uses service from, Cloud Providers.
2 Cloud Provider A person, organization, or entity responsible for making a service available to interested parties.
3 Cloud Auditor A party that can conduct independent assessment of cloud services, information system operations, performance and security of the cloud implementation.
4 Cloud Broker An entity that manages the use, performance and delivery of cloud services, and negotiates relationships between Cloud Providers and Cloud Consumers.
5 Cloud Carrier An intermediary that provides connectivity and transport of cloud services from Cloud Providers to Cloud Consumers.

Table 1 – Actors in Cloud Computing

Figure 2 illustrates the interactions among the actors. A cloud consumer may request cloud services from a cloud provider directly or via a cloud broker. A cloud auditor conducts independent audits and may contact the others to collect necessary information. The details will be discussed in the following sections and presented in increasing level of details in successive diagrams.

Figure 2 Interactions between the Actors in Cloud Computing

Usage Scenario 1: A cloud consumer may request service from a cloud broker instead of contacting a cloud provider directly. The cloud broker may create a new service by combining multiple services or by enhancing an existing service. In this example, the actual cloud providers are invisible to the cloud consumer and the cloud consumer interacts directly with the cloud broker.

Figure 3 Usage Scenario for Cloud Brokers

Usage Scenario 2: Cloud carriers provide the connectivity and transport of cloud services from cloud providers to cloud consumers. As illustrated in Figure 4, a cloud provider participates in and arranges for two unique service level agreements (SLAs), one with a cloud carrier (e.g. SLA2) and one with a cloud consumer (e.g. SLA1).

A cloud provider arranges service level agreements (SLAs) with a cloud carrier and may request dedicated and encrypted connections to ensure the cloud services are consumed at a consistent level according to the contractual obligations with the cloud consumers. In this case, the provider may specify its requirements on capability, flexibility and functionality in SLA2 in order to provide essential requirements in SLA1.

Figure 4 Usage Scenario for Cloud Carriers

Usage Scenario 3: For a cloud service, a cloud auditor conducts independent assessments of the operation and security of the cloud service implementation. The audit may involve interactions with both the Cloud Consumer and the Cloud Provider.

Figure 5 – Usage Scenario for Cloud Auditors

  • Previous page
  • Next page

 18,823 total views,  6 views today

Cloud Computing conceptual reference model was last modified: November 24th, 2018 by Sushil Verma
Share on Facebook
Facebook
0Tweet about this on Twitter
Twitter
Share on LinkedIn
Linkedin
Email this to someone
email

Latest Blogs

  • Linux: Viewing Log Messages
  • AWS CodeBuild: Getting Started
  • AWS CodeCommit: Set up Notifications
  • AWS CodeCommit: Securing The Repository and Branches
  • Managing Systemd units in Linux

Tags

Amazon EC2 AWS bash_shell bitcoin blockchain Cloud computing CodeCommit DevOps digital currency Kubernetes Linux trending ubuntu

For Improving Education

Categories

  • Amazon EC2
  • Amazon Web Services
  • AWS
  • AWS CodeCommit
  • Bash shell
  • Best Practices
  • Bitcoin
  • Blockchain
  • Chaincode
  • CLI
  • Cloud Computing
  • Cloud Security
  • CodeBuild
  • CodeCommit
  • CryptoCurrency
  • Cryptography
  • DevOps
  • Digital Currency
  • EC2 Lambda
  • Hyperledger
  • IBM Bluemix
  • IBM Garage
  • Kubernetes
  • Linux
  • Monitoring
  • OpenStack
  • Platform as a Service
  • TDD
  • Trending
  • Ubuntu
  • Virtual Server
Home | Site Map | Privacy Policy | Site Terms | Terms of use @2013, Times of Cloud.
The content is copyrighted to 'Times of Cloud' and may not be reproduced on other websites.