There are two primary storage services that are served up
in the hypervisor pool of resources.
One is the basic storage option of object storage.
Object storage is file storage.
You end up with a file folder type of construction. In volume storage, it's
the appearance of a disk drive inside of a physical server.
The analogy is the volume being attached to the instance.
This is based upon blocks of storage.
The primary cloud provider's storage options look like this,
from a block perspective, and also from an object perspective.
Some of the names are intuitive, for instance,
Azure's blobs,
binary large object, or Azure's disks, and AWS's Elastic Block Storage.
Let's focus on the block storage.
When you think of data in the cloud,
it would be the same as in the data center from the standpoint of a
volume storage scenario. Data that goes through the
first‑in‑first‑out processing of registers into cache and through
memory then have a repeated, pre‑allocated block that is associated
with the actual disk that they are on.
From a consumption perspective,
if you were to add storage to your virtual machine in the
Management Console, it would look like this.
You would see that you have the opportunity to select a volume type, which
would actually have a direct translation to the physical underpinnings that
are inside of the data center hosting your instance.
Also, automatically associated with your instance would
be a default size, drive, or volume.
Here's another example of what it would look like from an object storage
perspective. In Amazon's S3, they're called buckets, and these buckets are
where you would put files and folders on your system.
Those files and folders end up being a really great place of doing
transactional storage across the cloud to connect with public
customers. Join me in the next clip as we combine all of the
resource pool into the management plane.