jperezduerto.info
History · Unit 06 · Lesson 4 of 4
Virtualization and the cloud
See how an old resource-sharing idea became on-demand infrastructure, with new management responsibilities.
Helpful before thisHow computers got here
After this lesson you can
- distinguish a virtual machine from a cloud service
- explain how management access differs from guest access
- connect resource sharing to ownership, isolation, and recovery
Explore the eras below. On wider screens, scroll sideways to see the full timeline.
-
CP research explores presenting separate machine environments.
Why it matters Sharing hardware need not mean sharing one user environment.
-
IBM brings an official VM product to System/370.
Why it matters Virtualization predates public cloud services by decades.
-
A public service offers virtual computing through remote management.
Why it matters Provisioning becomes an operation exposed through service interfaces.
-
A common definition separates service characteristics and models.
Why it matters A virtual machine alone does not establish a cloud service.
Imagine booking a room in a large building instead of constructing your own house. You gain convenience, but still need to know who controls the door, the front desk, and the building’s infrastructure. Virtualization and cloud services create similar questions about shared resources, although their technical boundaries are more precise than the analogy.
Virtual machines are older than the cloud boom
IBM’s experiments in the 1960s explored giving users separate virtual machine environments on shared hardware. The company announced VM/370 in 1972. A virtual machine presents machine resources to a guest system while another layer manages the underlying hardware. This could support different environments without buying a separate physical computer for every job.
The word “virtual” does not mean imaginary. Processor time, memory, storage, and electricity remain physical resources. What changes is how software presents and allocates them. Hardware faults, software defects, and administrative decisions can still affect several workloads.
Remote provisioning changed the workflow
Amazon’s 2006 EC2 limited beta is one visible milestone in public cloud history. Its announcement described virtual computing environments created through service interfaces. Instead of waiting for a machine to be purchased and installed, a developer could request capacity remotely. This was a change in the delivery of computing, not the invention of virtual machines.
NIST’s 2011 definition describes a service model with characteristics such as on-demand access, resource pooling, and rapid elasticity. Therefore, a VM running on your laptop is not automatically a cloud. Cloud services can also provide managed databases or complete applications without exposing a guest operating system to the customer.
The management door matters
Consider a fictional club website on a rented VM. One account administers the guest. Another account may create machines, attach storage, or change network settings through the provider’s control panel. Protecting the guest while neglecting the management account leaves a separate powerful authority unexamined.
Responsibility also depends on the service. With a rented VM, the club may maintain the guest OS and application. With a managed application, the provider may maintain more of that stack. The club still needs appropriate data access, recovery arrangements, and an understanding of the agreement.
PredictYou become administrator inside the club’s VM. Does that automatically authorize changes to another customer’s VM?
No. Guest authority and infrastructure authority are separate. Their separation depends on implemented controls; neither a product label nor a role name proves every boundary is correct.
New packaging, familiar questions
Containers commonly isolate processes while sharing a kernel. They can run inside VMs, but do not automatically provide the same boundary as separate guest kernels. Ask what is shared and which component enforces separation.
The lasting questions are ownership and recovery: who may change this resource, where are its copies, and what restores useful service? Rapid provisioning makes those questions more urgent because resources can appear and disappear faster than a manual inventory can follow.
Check yourself
No timer. No penalties. Read the explanation and try again whenever you like.
This lesson’s questions have changed. Your reading progress is saved; review the updated questions.
-
A laptop runs two local virtual machines. Is that fact alone enough to call it a cloud?
Show the answer
Correct answer: No; cloud describes service characteristics beyond virtualization. Self-service, pooling, elasticity, and other service properties need separate consideration.
-
An administrator controls one guest system. What else must be established before claiming host authority?
Show the answer
Correct answer: Separate permissions over the hypervisor or management service. Guest and infrastructure authority are distinct boundaries.
-
A club uses a managed cloud database. Which question remains important?
Show the answer
Correct answer: Who may read its data and who can restore a usable copy? Service contracts move some duties while data access and recovery still need owners.
-
Two containers share a host kernel. Are they equivalent to two VMs with separate guest kernels?
Show the answer
Correct answer: No; the isolation mechanisms and shared components differ. Evaluate the actual shared kernel, runtime, and surrounding controls.
Try it
- WriteDraw a fictional club website running on a rented virtual machine. Assign guest updates, application permissions, physical repairs, account recovery, and backups to named roles. Then move the site to a managed application service and identify which responsibilities change.