WEBVTT

00:00:00.740 --> 00:00:05.160
There are two primary storage services that are served up

00:00:05.170 --> 00:00:08.680
in the hypervisor pool of resources.

00:00:08.690 --> 00:00:13.210
One is the basic storage option of object storage.

00:00:13.220 --> 00:00:16.170
Object storage is file storage.

00:00:16.180 --> 00:00:21.020
You end up with a file folder type of construction. In volume storage, it's

00:00:21.020 --> 00:00:25.040
the appearance of a disk drive inside of a physical server.

00:00:25.050 --> 00:00:28.780
The analogy is the volume being attached to the instance.

00:00:28.790 --> 00:00:31.590
This is based upon blocks of storage.

00:00:31.600 --> 00:00:35.760
The primary cloud provider's storage options look like this,

00:00:35.760 --> 00:00:39.830
from a block perspective, and also from an object perspective.

00:00:39.830 --> 00:00:42.270
Some of the names are intuitive, for instance,

00:00:42.280 --> 00:00:43.920
Azure's blobs,

00:00:43.920 --> 00:00:51.170
binary large object, or Azure's disks, and AWS's Elastic Block Storage.

00:00:51.310 --> 00:00:53.940
Let's focus on the block storage.

00:00:54.290 --> 00:00:56.640
When you think of data in the cloud,

00:00:56.680 --> 00:01:00.830
it would be the same as in the data center from the standpoint of a

00:01:00.840 --> 00:01:04.519
volume storage scenario. Data that goes through the

00:01:04.519 --> 00:01:08.850
first‑in‑first‑out processing of registers into cache and through

00:01:08.850 --> 00:01:16.080
memory then have a repeated, pre‑allocated block that is associated

00:01:16.090 --> 00:01:18.400
with the actual disk that they are on.

00:01:18.710 --> 00:01:20.480
From a consumption perspective,

00:01:20.490 --> 00:01:24.650
if you were to add storage to your virtual machine in the

00:01:24.650 --> 00:01:27.150
Management Console, it would look like this.

00:01:27.160 --> 00:01:32.500
You would see that you have the opportunity to select a volume type, which

00:01:32.500 --> 00:01:38.130
would actually have a direct translation to the physical underpinnings that

00:01:38.130 --> 00:01:40.740
are inside of the data center hosting your instance.

00:01:41.640 --> 00:01:45.420
Also, automatically associated with your instance would

00:01:45.420 --> 00:01:49.560
be a default size, drive, or volume.

00:01:52.640 --> 00:01:56.620
Here's another example of what it would look like from an object storage

00:01:56.620 --> 00:02:02.480
perspective. In Amazon's S3, they're called buckets, and these buckets are

00:02:02.480 --> 00:02:06.160
where you would put files and folders on your system.

00:02:06.230 --> 00:02:11.009
Those files and folders end up being a really great place of doing

00:02:11.020 --> 00:02:15.540
transactional storage across the cloud to connect with public

00:02:15.540 --> 00:02:20.210
customers. Join me in the next clip as we combine all of the

00:02:20.210 --> 00:02:23.750
resource pool into the management plane.