Cloud Computing Foundations · Study deck

Deployment Models and Virtualization

The previous chapter's responsibility bracket answered "who runs which layer of the stack" -- infrastructure, platform, or application.

Cloud Clara is your guide for this deck.

clouddeployment-modelsvirtualization

Cloud Clara, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Distinguish NIST's four deployment models -- public, private, community, and hybrid -- from distributed, multi-cloud, and inter-cloud architecture or operating patterns
Classify a deployment arrangement using the on-premise/off-premise by dedicated/shared-access synthesis
Explain why a virtual machine needs a per-instance guest OS and hypervisor while a container does not
Trace a worked Dockerfile from image definition through build and run to see the container model operate end to end

Major section

Start With What a Deployment Model Actually Decides

The previous chapter's responsibility bracket answered "who runs which layer of the stack" -- infrastructure, platform, or application.

This chapter builds that third pillar in full, then drops one level lower again, to the virtualization mechanism that makes any of these models physically possible.

A pump fleet separates local private control, private-cloud records, public-cloud analytics, and a signed hybrid evidence path.

Major section

The Four NIST Deployment Models

Together they describe who may use the cloud infrastructure and how distinct cloud environments are composed.

Distributed cloud, multi-cloud, and inter-cloud are useful architecture or operating patterns, but they are not additional members of this NIST pillar.
Cloud services or resources are placed across multiple physical locations while governance and operation remain coordinated.

Major section

The Four NIST Deployment Models (continued)

A cloud set-up for the use of any person or industry, typically owned by the organization that offers the service.

Two or more distinct private, community, or public cloud infrastructures joined by technology that supports data and application portability.
Public cloud is what most people picture first: Amazon Web Services, Google Compute Engine, and Microsoft Azure are the source material's own named examples.
Public-resource computing and volunteer cloud are two possible distributed arrangements.

Major section

The Four NIST Deployment Models (continued)

An organization deliberately uses services from more than one cloud provider or cloud environment, often to improve flexibility, resilience, or negotiating control.

The advantages are total control over the system and data, and correspondingly fewer security concerns to negotiate with a shared tenant base.
The named disadvantage is the mirror image of public cloud's low up-front cost: regular maintenance is the organization's own burden, not something absorbed into a shared bill.
Separate clouds interoperate or federate so that services, data, or capacity can cross provider boundaries under agreed technical and governance rules.

Major section

Under the Hood: Virtual Machines, Containers, and a Worked Docker Example

Every deployment model above describes an ownership and sharing arrangement -- it says nothing yet about the mechanism that lets one physical server safely host more than one tenant's workload at once.

Each instance carries its own full guest OS.

Major section

Under the Hood: Virtual Machines, Containers, and a Worked Docker Example (continued)

Execution stays safe to the kernel even if an application inside a container has security issues.

Containers are isolated from each other, but they share the host OS, and share binaries/libraries wherever that sharing is safe to do.
Every one of those five advantages is a direct consequence of the same structural fact -- there is simply less machinery to start, stop, and duplicate per instance than a virtual machine requires.
The first command builds the image and tags it docker-file (the name the source's own walkthrough uses for the docker run step).

Major section

Summary

NIST's four models are public, private, community, and hybrid.

Distributed cloud, multi-cloud, and inter-cloud instead describe placement, coordination, or federation patterns that may be used with those models.
A worked Dockerfile -- build steps, a base image, an exposed port, and a run command with a port mapping -- shows that mechanism operating end to end.

Deck summary

Key takeaways

The previous chapter's responsibility bracket answered "who runs which layer of the stack" -- infrastructure, platform, or application.

Together they describe who may use the cloud infrastructure and how distinct cloud environments are composed.
A cloud set-up for the use of any person or industry, typically owned by the organization that offers the service.
An organization deliberately uses services from more than one cloud provider or cloud environment, often to improve flexibility, resilience, or negotiating control.
Execution stays safe to the kernel even if an application inside a container has security issues.

Retrieval practice

Recall check 1 of 3

Cloud Clara says: answer from memory, then check your reasoning.

Q1A group of partner hospitals wants a cloud set-up shared only among themselves, all subject to the same compliance and jurisdiction requirements, with management either kept in-house or handed to a trusted third party. Which deployment model does this describe?

ACommunity cloud -- a shared set-up between organizations with common concerns such as security, compliance, and jurisdiction, managed internally or by a third party.

BPublic cloud -- open for use by any person or industry, with no shared-concern restriction.

CPrivate cloud -- functioning only for a single organization.

DMulti-cloud -- multiple cloud computing services offered via a single heterogeneous architecture.

Show answer

Answer: A Community cloud is the named pattern for several organizations with a shared concern (security, compliance, or jurisdiction) pooling one set-up, managed internally or by a third party.

Retrieval practice

Recall check 2 of 3

Cloud Clara says: answer from memory, then check your reasoning.

Q2Per the on-premise/off-premise by dedicated/shared-access matrix, which cell describes a hosted private cloud?

ADedicated access, off-premise -- a private cloud whose infrastructure is hosted and managed by a third party rather than run on the organization's own site.

BDedicated access, on-premise -- this cell is the organization's own private cloud, run on its own site, not a hosted arrangement.

CShared access, on-premise -- this cell is community cloud, not a hosted private cloud.

DShared access, off-premise -- this cell is public cloud, not a hosted private cloud.

Show answer

Answer: A A hosted private cloud sits at dedicated access x off-premise: dedicated because it serves one organization, hosted because a third party runs the infrastructure off that organization's own site.

Retrieval practice

Recall check 3 of 3

Cloud Clara says: answer from memory, then check your reasoning.

Q3A team wants to run five isolated instances of an application on one server, spin new instances up and down quickly, and avoid installing a separate guest operating system for each one. Which approach fits, and why does it not need what a virtual machine needs?

AContainers -- they run directly on the host OS (sharing its binaries/libraries where appropriate) instead of each carrying its own guest OS on top of a hypervisor, which is exactly why they are fast to instantiate and destroy.

BVirtual machines -- they are faster to instantiate because the hypervisor manages resource allocation directly.

CContainers, but each one still needs its own hypervisor, the same as a virtual machine.

DNeither approach applies -- isolating five application instances on one server always requires five physical machines.

Show answer

Answer: A Containers isolate workloads by sharing the host OS directly, with no per-instance guest OS or hypervisor -- the structural difference behind every one of their named advantages over virtual machines.

Print reference

Answers 1 of 2

Answer key.

A · Community cloud is the named pattern for several organizations with a shared concern (security, compliance, or jurisdiction) pooling one set-up, managed internally or by a third party.
A · A hosted private cloud sits at dedicated access x off-premise: dedicated because it serves one organization, hosted because a third party runs the infrastructure off that organization's own site.

Print reference

Answers 2 of 2

Answer key.

A · Containers isolate workloads by sharing the host OS directly, with no per-instance guest OS or hypervisor -- the structural difference behind every one of their named advantages over virtual machines.