12 hours 9 minutes
this is less than 12. Done. One virtualization and cloud technologies are virtual and cloud computing concepts.
So in this lesson, our objectives are to talk about common cloud technologies. We're going to talk about common cloud technologies as well as some other cloud concepts that you should be aware of whether you're a technician on dure, assisting in a cloud, set up or configuration
or you're working in a business and you may be cloud the call to
help with the cloud on technology. So you know, the difference is also more importantly, free from a comp Tia es. Plus, you'll want to know these common cloud technology. So let's go ahead and get started Infrastructure As a service, I A s
cloud technology has many different models that you can use to configure your applications.
Infrastructure is a service or I II s as where you're provided with all the hardware to run your applications. This is also known as has our hardware is the service. So you're responsible for installing the applications on that hardware. You're responsible for the updates that patches etcetera.
So the infrastructure is laid out. You're responsible for the software.
An example of This will be a Web hosting provider on the Web hosting provider. Have the hardware and you're running that hardware in your use of it. You're gonna install your own website and build your own website and what other Web application that you're gonna use in that environment. So that's infrastructure after the service, where a provider provides you the in user as an infrastructure
and you put whatever applications is software you want on that particular hardware.
So that's one cloud concept. Their infrastructure as a service
software's, the service says, suffers the service is often referred as software on demand. Now, if says you log until a control panel or site and you immediately have access to preinstalled software
with says the application of the data are all maintained by the third party provider, there's no development work you have to do on your side. Nothing you have to do. No update, no patches. The software is provided for you. A good example of this will be hosted email. That's an example of SAS software. As a service,
you just go into the software
and set it up to your needs and issue user's email accounts. And so forth. So that's just one example off software as a service centralized management of your data. Now the software is not yours, but the data is yours. And one thing you want to consider what this type of setup is
again. Software's not yours, but the data is yours, and that data is being used on another company's software.
So just keep that in mind
platform as a service or pass platform. As the service is a platform where you customize and shoes from pre built applications, you don't have to worry about any part of the infrastructure again. You don't have to do any of the heavy lifting. You just use preinstalled software. Put them together to your use
so it's a little bit more different. Their software. The service Where's this is a platform
allows customers to develop run manage applications without having to maintain the infrastructure sales force. Our windows azure are examples of pass. You don't You do not have direct control of your data.
Trained security staff watches over your data for you, So that's one thing to consider when using this type of cloud technology. So that is platform as a service
now, private versus public versus hybrid versus community clouds. What are these? Let's talk about him in detail.
Different cloud development platforms. Private cloud is you on the hardware. It's in your localized data center. Your virtualized applications and hardware is in your data center. So this is your cloud Uses your data center. You may have your virtuous virtualized applications
and v EMS right in your own data center. So, traditionally, this is quote your data center. But this is your your private cloud.
Now a public cloud is available to anyone on the Internet. So it again, another example with this would be Microsoft Microsoft Azure I'm is on Web service is on examples of this. It's public to any bound Internet and you're just putting your information into their cloud into their platform.
Hybrid cloud is a mix of public and private cloud. Lot of organizations may have a little mixture. In my previous resulting, I had a client that had both ah had a heart of a hybrid cloud. It was local hardware, virtue and and software.
And also they had things in the cloud as well. So it was a little bit of both
community cloud is a group of organization sharing the costs of the cloud they share. The same resource is, but they all chip in in their arm, getting the benefits of using that community cloud. And again, you're re sources are in a place where another company's resources are as well
shared. Resource is internal versus external internal cloud one of benefits of ah, internal cloud. No shared resource is the resource is air yours. You don't have to share anything with anyone. You build out everything, though you're responsible for everything. The upfront costs
eyes all yours. Now there's no ongoing costs like a monthly service or fee
other than lights, electricity and Internet. But all the cost is yours up front, you build your data center or wherever you're hosting, platform is gonna be
now on external cloud. Shared resource is with the public cloud. Other customers have their information on that cloud as well. Sometimes you may not have them your own public I p address, depending on the platform, so you have to share that as well. So that is a shared external cloud environment.
The infrastructure is owned by someone else, and the cost may be meter or up front.
So that's the difference between a shared resource is internal and external
meter cloud service is now meter. Cloud services are pretty much just what it means. You pay for what you use cost to a blow. There's a cost to store your data. There's a cost to download every time you access and use it. There is a cost associated to that. So that's a meter cloud service now non meter Carl Service's.
Are you paying for a flat cost for a block of time?
There's no cost to upload. There's no cost a store, but there's no cost to download, but you're playing forward in a block so that maybe like a monthly fee or annual fee of some sort like that. So those are two different cloud concepts that you want to be aware of. Depending on your application, in which you may need
cloud characteristics so rapid elasticity. Let's talk about that. You can scale up or scale down, asked need it. Now, This scaling up in scale down is not like in the old days where you had a data center and you needed more servers, so you have to purchase hardware, install them and turn them up and load it. And it was some downtime as you migrate things.
This is seamless.
There's no interruptions Year service would. Sometimes it could be just a flick of a button or a switch or command, and you have instant of ST scaled up to add additional servers on demand service. You can add applications at servers at networks, even when needed. Instant resource provisioning
Resource pooling is something else that you may want to consider.
Resource pulling is like a large resource is instead of multiple small re sources. Say difference. If you had your own servers, there were multiple small servers with resource pulling.
You can pull all your service together quickly and and wrap up quickly. It's seamless to your service. There's no interruptions. You can combine low or idle servers. Let me give an example of this one particular client we had. They had servers in their quote in House Data Center,
and there were low volume servers. So when we
obtained the account, there was multiple servers not really doing anything. So instead of the hard work costs of maintaining the hardware, the patches in the update, we combine those into a virtual server. So we took those small roles that the service plate virtualized them
and save the clients of money on the long run. So
that's that's resource bully.
Measured service costs and it uses is tracked closely with reporting track. How many users? The value of usage, etcetera, resource reporting eyes with the grand you'll ever and chargebacks Say, for instance, if you are getting a service from a provider and turn around and reselling that out,
that's one example right there hasn't reporting as far as who accessed what or whatever.
Whether you may not even be reselling service, it could be your business. Your business is getting a metered or measured service from a provider and you contract who long in what they did on the usage that you're using and so forth. So that's measured service.
Okay, so what? We've learned this lesson We went over common cloud technologies.
We've talked about infrastructure as a service I A s. We talked about software as a service sass s, A S and pass platform. As a service, we talked about public and private clouds versus hybrid in community clowns.
We talked about shared resource is internal and external rapid elasticity, undermanned and resource pooling.
So those are key concepts that you need to know for the comp Tia es plus as well as in the real world as you is the technician where they're working out of business or you are helping a client and move into the virtual world. These are some core calm concepts that you need to know when dealing with cloud technologies. So
that is it for this lesson,
and we will see you in the next lesson.