WEBVTT

00:00.000 --> 00:01.365
>> As I said earlier,

00:01.365 --> 00:03.450
virtualization just
naturally leads

00:03.450 --> 00:06.134
itself to discussions
on Cloud computing.

00:06.134 --> 00:08.265
If we're looking at
Cloud computing,

00:08.265 --> 00:10.530
it really exists because
of virtualization.

00:10.530 --> 00:12.720
Like we said, makes
it profitable is

00:12.720 --> 00:14.865
organizations like
Google, Amazon,

00:14.865 --> 00:16.410
and Microsoft investing in

00:16.410 --> 00:18.255
a lot of really
high-end equipment,

00:18.255 --> 00:20.250
then divvying it
up and leasing it

00:20.250 --> 00:22.455
out to individual organizations,

00:22.455 --> 00:25.185
that's where we get
Cloud computing.

00:25.185 --> 00:29.070
Now, NIST has a definition
that they give us.

00:29.070 --> 00:30.840
Ultimately, what
they're saying is

00:30.840 --> 00:32.370
Cloud computing is a model

00:32.370 --> 00:34.445
and listens to some
of the requirements.

00:34.445 --> 00:37.055
It's ubiquitous and
available everywhere,

00:37.055 --> 00:38.935
it's convenient and on-demand,

00:38.935 --> 00:41.595
I can access my
Cloud-based resources,

00:41.595 --> 00:43.550
I have access to
a shared pool of

00:43.550 --> 00:46.780
configurable computing
resources and that's with me.

00:46.780 --> 00:49.385
I don't have to go through
the Cloud service provider,

00:49.385 --> 00:51.770
if I've Infrastructure
as a Service and I'm

00:51.770 --> 00:54.155
in components of the
Cloud service provider,

00:54.155 --> 00:57.460
I can spin up 100 hard drives
or servers very quickly,

00:57.460 --> 00:58.860
and then I can decommission

00:58.860 --> 01:00.224
>> them once I don't need them,

01:00.224 --> 01:02.005
>> which is rapid provisioning.

01:02.005 --> 01:04.220
I can very quickly
add to my network and

01:04.220 --> 01:06.485
very quickly release
those resources.

01:06.485 --> 01:08.555
Again, because this
is software-driven,

01:08.555 --> 01:10.490
we have a lot of flexibility.

01:10.490 --> 01:12.830
What are the drivers
to move to the Cloud?

01:12.830 --> 01:14.840
Honestly, it comes
down to the fact that

01:14.840 --> 01:16.040
senior leadership believes

01:16.040 --> 01:17.930
the benefits outweigh the costs.

01:17.930 --> 01:20.690
Part of this is the pay as
you use benefit rather than

01:20.690 --> 01:23.555
paying a flat fee regardless
of how much I use,

01:23.555 --> 01:26.150
I'm only going to pay for
what I use in this case.

01:26.150 --> 01:27.740
There's a lower total cost

01:27.740 --> 01:29.870
of ownership and
that's the goal.

01:29.870 --> 01:32.400
If I'm not paying
for excessive use,

01:32.400 --> 01:34.215
then it costs less in long-run.

01:34.215 --> 01:37.070
In some cases, it may
be like leasing a car.

01:37.070 --> 01:38.990
If I buy a car, that
I have to worry

01:38.990 --> 01:41.110
about all the maintenance
and deprecation,

01:41.110 --> 01:42.560
but if at lease the car,

01:42.560 --> 01:45.320
then over time it winds
up costing me more money.

01:45.320 --> 01:46.910
But I do have those
benefits of being

01:46.910 --> 01:48.590
able to return the
car when I'm done,

01:48.590 --> 01:50.390
and any of those major upgrades

01:50.390 --> 01:52.460
are often taken care of for me.

01:52.460 --> 01:55.140
Lower total cost of
ownership is the goal,

01:55.140 --> 01:57.245
but sometimes we
see that over time

01:57.245 --> 01:59.960
we could conceivably
spend more money.

01:59.960 --> 02:02.390
If that's the case, then
what we're really doing is

02:02.390 --> 02:06.020
trading capital expenditure
for operational expenses,

02:06.020 --> 02:07.640
rather than having
all that money

02:07.640 --> 02:10.615
upfront or paying a monthly
or quarterly basis.

02:10.615 --> 02:12.785
Ideally, we get
greater reliability,

02:12.785 --> 02:15.085
scalability, and sustainability.

02:15.085 --> 02:17.060
We're taking advantage
of the resources that

02:17.060 --> 02:19.160
these major organizations have

02:19.160 --> 02:21.685
and the investments
they've made.

02:21.685 --> 02:24.110
It keeps me from
having to purchase

02:24.110 --> 02:25.790
my own data center and to

02:25.790 --> 02:27.610
develop or build my
own data center.

02:27.610 --> 02:28.855
Stock or with servers,

02:28.855 --> 02:29.980
heat it, cool it,

02:29.980 --> 02:32.825
secure it, control
access to it, and so on.

02:32.825 --> 02:35.900
Now, everything that used
to be my data center is

02:35.900 --> 02:37.400
simply access to the Internet

02:37.400 --> 02:39.020
at the Cloud service provider.

02:39.020 --> 02:40.580
Ideally, because of the many

02:40.580 --> 02:42.305
tremendous resources they have,

02:42.305 --> 02:43.850
we get greater up time,

02:43.850 --> 02:46.060
and ideally, we get
additional security,

02:46.060 --> 02:47.495
but that's only guaranteed based

02:47.495 --> 02:49.540
on your service level agreement.

02:49.540 --> 02:52.460
Many times I've heard people
say they'll secure it

02:52.460 --> 02:54.965
better than me will,
but not necessarily.

02:54.965 --> 02:56.450
Your service level agreement

02:56.450 --> 02:57.740
with your Cloud service provider

02:57.740 --> 02:59.030
is really going to be critical

02:59.030 --> 03:00.440
as to what you can expect,

03:00.440 --> 03:03.175
and a service level agreement
is just commitment.

03:03.175 --> 03:06.080
If we don't have audits or
some third-party assurance

03:06.080 --> 03:08.795
that are Cloud service
provider honors their SLAs,

03:08.795 --> 03:10.190
then we need to
move on and look at

03:10.190 --> 03:12.560
another Cloud service provider.

03:12.560 --> 03:15.380
I'm not going to read
every one of these,

03:15.380 --> 03:16.625
but it's for automation,

03:16.625 --> 03:18.720
easy deployment, you
don't get much easier

03:18.720 --> 03:21.420
than software-based
deployment of components.

03:21.420 --> 03:24.770
Device and location-independent
often a company like

03:24.770 --> 03:25.940
Amazon is going to have

03:25.940 --> 03:28.345
distributed devices
throughout the world.

03:28.345 --> 03:30.230
If there's a local
issue that happens,

03:30.230 --> 03:32.240
our deal is still going to
be available because it

03:32.240 --> 03:35.340
resides in so many
other locations.

03:35.780 --> 03:38.480
24-7 support is something we

03:38.480 --> 03:40.355
may not have in
our organization,

03:40.355 --> 03:42.200
so with your Cloud
service provider,

03:42.200 --> 03:44.180
assuming it's in the
service level agreement,

03:44.180 --> 03:45.760
we'll provide those benefits.

03:45.760 --> 03:47.300
What most people focus on for

03:47.300 --> 03:48.680
the Cloud is that it's going to

03:48.680 --> 03:50.064
>> save us money over time.

03:50.064 --> 03:52.215
>> We're not going to have
to buy these servers,

03:52.215 --> 03:53.945
we're not going to have to
heat them and cool them,

03:53.945 --> 03:55.685
which is a really
expensive cost,

03:55.685 --> 03:57.920
and we're not going to
have to secure them.

03:57.920 --> 03:59.450
We're going to be able to access

03:59.450 --> 04:01.535
our information from
anywhere on the planet,

04:01.535 --> 04:03.355
and that's a tremendous benefit.

04:03.355 --> 04:06.960
Cloud computing has a
lot of selling points.