Starting off, we have NIST 800-145.
And this is our standard or basic application guide
for implementing our cloud platform
and everything related to that cloud platform
and suggested security requirements.
This is not necessarily a Cisco thing,
but an overall standard for the community of IT
so that way we can be all on the same page.
And Cisco goes even further by delving into some of the tools
which we'll be getting into later.
But I do want to touch on some of the things WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But I do want to touch on some of the things
that are covered inside of this special publication.
For instance, one of the first things that we cover
is on-demand self-service,
where we're basically allowing users
to automatically provision things like server time
and storage requirements without human interaction
so that way it's as seamless as possible
with each service provider.
Now some of this can be things like
a user has maxed out their storage requirements
and there's a macro setup or some sort of configuration
inside of that cloud environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
inside of that cloud environment
that automatically expands storage
in certain increments.
So that way the user doesn't necessarily think
they're running out of storage.
It just keeps expanding so that way
their requirements are met.
Now we're not going to be covering the cost
or anything like that because that varies
based on who the actual cloud provider is.
We're just saying that in this particular skill
and course that that can be configured automatically
through different configuration points
and as we go through we'll be looking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and as we go through we'll be looking
at some of those different methods for Cisco
outside of the NIST standard.
Then we have broad network access which is basically
saying that cloud services are accessible over the network
and can be used through standard devices
like laptops, regular desktop computers
and mobile devices.
Because as we start to expand on our cellular devices
the capabilities of those also expand.
You can do more on a cellular device now
than you've ever been able to do before
and it makes it a little bit easier
to access some of those cloud resources. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to access some of those cloud resources.
So if you're working on let's say a tablet
and you're accessing a cloud storage device
or let's say a server farm
and you want to be able to implement a new server
and you run out of storage
that automatic configuration we just went over
should be able to handle that for you
according to our NIST standard of usability.
800-145 also covers resource pooling
and where we provide computer resources
in a pooled environment for that cloud environment
to be able to operate. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to be able to operate.
So you have many physical systems out there
or many virtual machines out there
pooling their resources together
to be able to provide what looks like
one specified service for the actual user.
So instead of having 10 different hard drives out there
for that storage requirement
that we're trying to expand on the fly
we have one setup, a virtual setup
to where the user sees that one storage space
let's say a drive letter D or something like that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's say a drive letter D or something like that
and it just keeps expanding
using those multiple physical devices
and allows for those different servers
or virtual machines to be able to pull the resources together
to provide that capability.
This means that the data may be spread out
over multiple physical devices
but for the purposes of the actual user looking
at the resource or utilize that resource
we're talking about just one in terms of visibility.
Now I do want to point out this also works
into that multi-tinet model
where we're basically using a single system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
where we're basically using a single system
physical or virtual machine like we just covered
and serving multiple users.
So that physical or virtual machine
might be able to pool together different resources
for multiple different places
or systems on the actual cloud environment
and pull them together in that one system
whether it be a virtual machine or a physical system
and provide it to that user and that's multi-tinet.
We also want to be able to provide rapid response
to the actual user when we do this resource expansion WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to the actual user when we do this resource expansion
or making sure that different aspects of cloud usage
is made available to the user
and that's done through rapid elasticity.
Rapid elasticity is allowing us to quickly
and easily scale up or down as in terms of a rubber band
how much resources or how many different types of resources
that we're using based on the actual utilization metrics
that the user is either meeting or providing.
Think of it like this.
If you have a user that has a virtual system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If you have a user that has a virtual system
within that your cloud environment running 200 gigs of RAM
and they're only utilizing let's say 25 gigs of it,
rapid elasticity will allow you to be able to lower the amount
of RAM allocated to that particular usage
and allocated somewhere else that's needed
inside of that cloud environment.
And it also works the other way around
if you're limited to 200 gigs of RAM on that particular system
and for whatever reason you need more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and for whatever reason you need more
the resource pooling will allow us to be able to expand
the amount of RAM allocated to that particular system service
or device virtualized within the cloud
and expand it on the fly to make it as easy as possible
for the user to be able to commit
to their resource allocation requirements.
Whole point behind that is as much uninterrupted use
as possible so that way the user doesn't have any downtime.
If you've been through some of our other courses together
you know that we're always banging on about the five nines WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
you know that we're always banging on about the five nines
to 99.99% availability rate.
And rapid elasticity allows us to be able to run by that
with ease of use.
Now all this is done under a measured service
and we're taking account of everything that the user
or organization that is using our cloud resources
is needing or is currently using
and maintain an automatic control over those systems
to enable things like rapid elasticity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to enable things like rapid elasticity
or the resource pooling or the actual network access
for those different systems that way we know
and we have accountability of the different things
we may or may not need.
So we're not just using macros or pre-programmed measures
to be able to go out and give organizations
or users extra resources or take them away
without having some sort of accountability mechanism
in place to make sure that that's actually the type of tool
or service that we need to do for those different users. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or service that we need to do for those different users.
So just keep this in mind as we start going through
the rest of the skills together
that are basic background and kind of regulation,
if you will, is missed 800-145 to make sure
that we're staying in line with all the cloud needs
of our actual servers, platforms, organizations
and individual users.