>> Virtualization and Cloud technology.
The learning objectives for this lesson are to
describe Cloud deployment and service models,
explore Cloud storage technology,
and to differentiate virtualization technologies.
Let's get started. Now,
we went over our virtualization in
a previous lesson but we're going to
get into it a little bit deeper here.
If you remember, we have two
>> types of virtualization and
>> these are the Type 1 and Type 2 hypervisors.
The key thing to keep in mind is that Type 1
doesn't need a host operating system but Type 2 does.
With a Type 1 hypervisor,
this is also known as bare metal.
You don't need a host operating system because
the hypervisor is the operating system
for that set of hardware.
You take the hardware, you
install the hypervisor directly onto
the hardware and then you log into
the system and configure
your virtual machines from there.
This is usually done via a web browser.
Examples of this are Microsoft Hyper-V,
XEN, Proxmox, and VMware ESXi.
Then we have Type 2 hypervisors.
These do require an operating system because they're
just an application that is installed
inside of the operating system.
An example of this would be to take
your Microsoft Windows machine,
install VirtualBox on it,
and then you can install anything you
want inside of a virtual machine
that's handled by a VirtualBox.
But whatever happens inside that virtual machine,
it doesn't do any impact at all to
your Microsoft Windows-based operating system.
Examples of Type 2 hypervisors are
VirtualBox, VMware Workstation,
and Parallels Workstation. Structure Side Note.
If you'd like to get a hand on this
and play with both of these,
there are free versions of
both Type 1 and Type 2 hypervisors that you can learn on.
For a Type 1,
you can use Proxmox.
You install Proxmox on the PC and
that will become the entire virtual environment.
You log onto it with a web browser and
you create the virtual machines from inside there.
We use this in a lot of areas of my company and in fact,
we have one Proxmox server here that has
12 VMs running at the same time.
It's a lot easier to do that than it would be to run that
with a Type 2 such as VirtualBox.
But if you want to get started with virtualization,
it doesn't matter if you're running Mac or Windows,
or Linux, VirtualBox is available for all of them.
You can download VirtualBox at
no cost and then download the ISO of
any operating system you want and load that into
a virtual machine that will be handled by VirtualBox.
This is a good way if you're new to
Linux and you'd like to try it out, for example,
you could download the ISO of Mint or Ubuntu
and then spool up a VM
inside of your Windows operating system.
That way you could start playing with it and get a hand
on learning how to use Linux
without having to give up your Windows machine.
By the way, links to both of these are available
in the supplemental material for this course.
Application virtualization.
This is when a client
accesses an app that is hosted on a server.
This is usually done using
the web browser because this is more familiar to
end-users and also where
most apps have been geared towards being delivered.
This allows for us to share
a specific app from
a single server through the user's browser.
Examples of this technology would be App-V,
XenApp, and ThinApp.
Containers. The differentiator between containers and
virtualization is that containers use
a single base kernel for all of the containers.
The containers, they
contain the minimum necessary amount of libraries,
apps, and files to function.
Each container relies on
the base kernel to run and because of this,
we get enormous performance benefits.
The most common example of this will be Docker.
If we're looking at the picture,
we can see that all three containers
even though they're set up for different purposes,
rely on the base operating systems kernel.
If we were to have
a Linux Ubuntu Server
and then we put Docker on top of that,
each of the containers that we create would
rely on the base Ubuntu kernel to function.
This is a good breakdown of
the differences between virtual machines and containers.
The virtual machine that is depicted here is a Type II.
We can see that it has
a host operating system and
the hypervisor lays on top of that
and then we have a separate virtual machine that
has other three of them and each
of them has their own guest OS,
their own binaries,
and libraries, and their own applications.
The advantage of a virtual machine here is that all of
those guest OSs can be completely
different from what the host operating system is.
For example, we could have a
Windows host operating system
and then we could have a guest OS
in one of the VMs that's Mac,
and then another that is Linux,
and then in the third, it could be FreeBSD.
It doesn't matter what
the guest operating systems are when
we're using a virtual machine,
however, on the container side, it does matter.
Whatever the operating system is,
all of the containers must be
compatible with that operating system.
They all use the same kernel
so they have to be compatible.
We can see that we have a base operating system,
the Docker Engine lays on top of that,
and then we have three separate containers
that each contain their own app,
their own binaries, and libraries but again,
refer back to the base operating system's kernel.
Cloud Deployment Models.
The first we have is a public Cloud or multi-tenant.
This is offered over
the Internet by a Cloud service provider.
It is shared by many different users and
all the resources are spread across
all of the clients of the CSP.
Next, we have hosted private.
This is when you're using a third party but the service
they're offering is only used by you and your company.
This gives you security benefits
over a public Cloud version.
Next, we have Private Cloud.
This is where the infrastructure is completely
owned and operated by a given organization.
Because of this, the security is much
stronger than being hosted by a third party.
Then finally, we have community Cloud
which is where several organizations share
the cost of the hosted private or totally private cloud.
Cloud-related business directives.
Cost is important but before you consider cost,
you should consider the confidentiality,
the integrity, and the availability of your data.
Scalability. Are you able to respond to business demands
that cause you to have to scale
upwards or in a horizontal way without downtime?
Resources. Do you need an additional virtual machines,
networking capacity, stores or applications?
Location. The Cloud allows for
us to easily relocate data or services
anywhere around the world but this
brings up jurisdictional issues that we will discuss
later in another module but keep in mind that
this is something you need to consider
when you're choosing a Cloud service.
Finally, data protection.
If it's not on your corporate resources,
you must consider additional security requirements.
Instructor Side Note. I like to tell
people there is no such thing as the Cloud,
is just someone else's computer.
If you don't fully own
the infrastructure that you're
using for example a private Cloud,
then your data is just stored on someone else's computer.
You need to fully understand
the security implications and
the configurations that you're
using when you're deploying Cloud technology.
Let's go over some Cloud service models.
To the left, we have on-site.
This is where you manage everything.
Everything is controlled and owned by you.
The next step over to the right
is Infrastructure as a Service.
With this, you manage the applications,
the data, the runtime, the middleware,
and the operating system but
the service provider handles the virtualization,
the servers, the storage, and the networking.
Next, we have Platform as a Service.
This is where you manage the applications and
the data but the service provider
handles everything else.
Finally, we have Software as
a Service where the service
provider is managing everything.
A good example of Software as
a Service would be Salesforce.
Salesforce sells you access to
an application and they manage everything on the backend.
Let's discuss Cloud storage models.
The first one we want to discuss is object storage.
This supports Cloud-based apps
that need access to documents,
videos, and image files.
Next, we have file-based storage which is
a hierarchical file system that stores
files by path that includes attributes
such as the owner and access permissions of those files.
Then we have block storage,
this supports high-performance transactional apps
like databases and finally,
we have Blob Storage which
supports storage of large amounts of
unstructured data and it's often
used to store archives and backups.
Cloud storage databases.
The first we have is relational.
This is widely implemented and is
designed for ACID transactions.
Then we have key value which is designed
to store and retrieve large amounts of data.
Next is in -memory.
This is real-time access to data for applications.
Next is document which stores
data in a semi-structured manner.
Finally, we have
a wide-column which is a type of NoSQL database.
Finally, Cloud storage databases.
A graph supports millions of
relationships between highly connected datasets.
A good example of this is social media.
Then we have time-series,
this is focused on supporting apps that
analyze data and changes that occur
over time and it best represents using time intervals.
Finally, we have ledger. This enables
trusted and verifiable authority
for banking transactions and systems of record.
Let's summarize what we discussed in this lesson.
We went over virtualization technology
and containerization,
also discussed Cloud deployment models
and Cloud service models.
Let's do some example questions.
Question 1; Which type of
storage model is best used for backups and archives?
Blob storage. Question 2;
you have been asked to arrange
a Cloud service model to
support your company's newest app,
it will need database and web support included,
which service model do you need?
Platform as a Service?
Question 3; you have been asked to
set up a Cloud infrastructure instance for
your company that will be shared
with another company to help control costs,
what type of Cloud is this?
Community Cloud. Finally, question 4;
in which Cloud service model would you receive access to
the hardware and nothing
else so that you could configure it as needed?
Infrastructure as a Service.
Well, that brings us to the end of
this lesson, I'll see you in the next one.