Cloud Essentials | Maher Dahdour | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Cloud Essentials

teacher avatar Maher Dahdour

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

9 Lessons (42m)
    • 1. Cloud Course 1 Introduction to Cloud

    • 2. Cloud Course 2 Cloud Definition Part 1

    • 3. Cloud Course 3 Cloud Definition Part 2

    • 4. Cloud Course 4 Virtualization Introduction

    • 5. Cloud Course 5 Virtualization and Cloud Computing Value

    • 6. Cloud Course 6 Virtualization Cloud and Adoption Fitness to purpose

    • 7. Cloud Course 7 Could Computing Service Models

    • 8. Cloud Course 8 Service Models and Deployment Models

    • 9. Cloud Course 9 Deployment Models and Summary

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

Must know about cloud computing from an expert.Introduction to terms, cloud computing service models and deployment models. Cloud Computing and Virtualization introduction and contextual.

Meet Your Teacher

Class Ratings

Expectations Met?
  • 0%
  • Yes
  • 0%
  • Somewhat
  • 0%
  • Not really
  • 0%
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Cloud Course 1 Introduction to Cloud: Hello, everyone, and welcome to cloud essential. This is my had a dual your instructor for this course, I bean training and managing in the areas off a Cloud I T and software development for almost 20 years. I am also certified in project management in Surprise, Architectural Service Management and Enterprise. I t. Governance. In terms of prerequisite for this course, there's no formal prerequisites. It's recommended to have some exposure to gaiety to mean well, the agenda for this coast. We going over three items, major items. One of them is introduction to cloud computing. The 2nd 1 is business perspective, and the 3rd 1 is technical of respect. We will discuss the definition the concepts from both business and technical and also will go over all the elements that needed for you to understand what is cloud computing, including the service models and also the deployment models and in terms off control, management, maintenance and related aspect to the coast and risk and security. Thank you. The first unit We are going over the definition off cloud computing, the characteristic off cloud computing, the main concepts and also the service models and deployed models off cloud computing the objective of this class, we are going over the terminology of cloud computing, the definition off cloud computing and specialization. We're also going to discuss what makes a clout. What is a cloud? What are the characteristic off a cloud based on nest? And also, we will define the concept off How cloud brings value to organization. What do you do to bring value out of club? In addition to that, will discuss the service models and also the deployment models in cloud computing. Having said that, we will discuss a lot of issues related to this migration. This transformation, this movement off building blocks from your organization, from your enterprise to another business entity, call service supervisor or closer. So Will does discuss that from them back on the I t and business. Now we just have an overarching concept before we even start. Before we even define what supplies computing. Think about that. I'm having two entities. Business Entity one is my business into one is my enterprise. My organization and another entity is their service provider, the cloud service providers and there are certain things I need to be using, taken consuming from there, cloud sort of supervisor, as if now probably have everything in my organization, my enterprise, if I have everything in the classes so I'm gonna consume everything from the cloud service provider. In this case, this is my entity. Head is that cloud set of supervisor? The more I move from building blocks to the other side, that's basically will determine what service model I would have. So the from the high level concert we have two entities, the provider, the consumer. We have a building blocks. It depends on the building blocks that were moving and whatever related management requirements administration updates, security is going to be but off what the service provided to the enterprise. So in a high level in somebody we have two entities one will consume from the other one how much you consume and why. What level of controls and management will determine the whole concept off a club And what is their value? We will discuss as you move forward 2. Cloud Course 2 Cloud Definition Part 1: Now let's understand what's cloud computing? The definition of cloud as a mission. The overarching slide that there are two entities, one consuming services, one of providing services. Those services mainly our I T capabilities, I t services and also Resource is related to the ICTY. And when we say cloud computing, we're talking about something that we can use. But technically we may don't need to understand how it's really manage. It's in the cloud. There is some ambiguity about in terms off what goes beyond that. But all we have to do is consume those services and make sure the services that we consume satisfy our needs. So that's basically the main concepts off cloud computing. Cloud Computing is a service model is a business service model where we as an organization can consume services and resources from the sale of a cell provider. So that's basically the main concept about Cloud is that we have an organization. We have another organization, one organization consume. One organization provides the same goes with if you let's say, a utility company while you with electricity or gas, you only have to use a turn it on and off as needed. use as much possible as needed on demand. I need little now more after increased stop. That's your choice, but you pay for what you use. You don't have to build Jenna or to buy generators to generate gas and electricity. All you have to do is to use it. So technically, what we're saying here is it's a business model to utilize, to consume, to use services and resources from another organization. Just think about the utility model. Think about that. You don't have to have the infrastructure to utilize those services. Yes, you can have those services in your organization, but there are reasons where you don't want to have that, and we'll discuss some of the benefits now as a result, off using this cloud model, this service Business service model there are There is a lot off discussion about what made this cloud reality, what technology that built and used to enable cloud to have in this way, and we'll discuss about the concept off virtual ization virtual layer that's action layer virtual server bm from a level that you can understand. What is the value off a crowd? What we see here in the picture on the slide that we have multiple resources, we can consume those resources and at the same time chose you that we can access from different channels from the cloud provider. We can use the services we can use applications, subscript application and data. We can also consume or build application using the services provided by the cloud computing computing provider. We can't even use their computing resources, have their only their infrastructure to build our own APS. What could you do? A lot of stuff with cloud computing, But the bottom line we have to go through the Internet and we have toe. We can access them from different channels. Could have ABS on devices, smart devices Who could have a machine species. Okay, laptops. This stops. We could use him from different chance. That's one thing. Accessibility is easy, can be from multiple chance and has to go through the Internet. So we consume in a different way and all consume at any time. But that how we will determine how we are going to consume on what we consume. That's more onto the discussion off the details of that 3. Cloud Course 3 Cloud Definition Part 2: No, the cloud computing. It brings some terminology as a mission. What's a cloud? What's cloud services with cloud service providers to provide that someone to provide closers is what are the cloud services? I mentioned the building blocks in summary. Here we have hardware who had networks? Connectivity, storage we have, Sarah says. We have interfaces where it cloud services. It could be software. Could be infrastructure. Could be storage could be others. But it has to re be related to those I t capabilities that we can consume. So we have the cloud, which is the sit off hard when it works, studies service interfaces. That's basically a sit off providing. But the whole concept of the definition is a business model to provide those services. Who provides him a provider who considered them we consume as an organization as an enterprise, and there are the closer's is that we are consuming so consumer provider assets or resources or services that we consume. That's basically the terminology that we're using Cloud cloud services and cloud service providers. Now let's go to the characteristic or flat cloud computing. Can you have a cloud computing without those kind attributes is going to be difficult if I can't have a cloud. But the cloud has to be access in or by multiple channels, broad network accessibility. And at the same time, when I say okay, it has to have resource pooling MEES. The providers will save multiple clients, customers, tenants. Okay. And technically, this services can be updated, upgraded, lowered, so changed based on they used. So technically, the providers will serve multiple consumers. Multiple tenants. Okay. And they have to make it scalable is kind of service providing let's small those can Things have to be part of the resource willing concept, elasticity, but rabid elasticity. I can the sake I want to use this much stories today. But I do want it tomorrow so I can't end this off. Lower the usage off this specific. Ah, storage. I'm using one terabyte today, but I don't need one terabyte, so I can change that. The same goes with other services. So the rabid elasticity that I can do this change ability to revise scalable services that can be changed in terms of capacity, as I need it now on the mind. So, service I can I requested this change myself and I can't even requires changing it myself, and they have to be changed. That's on demand, as I need it, and I pay Pierre what I use. So I am as an inter bus, I can take what I need based on what I need from the cloud provider now major services or media services. It means those service has to be monitored and have to be midget when it, in this case with the cloud provider measures and monitors the provision services for various reasons for billing, for effectiveness, performance many things. So they have to have a way to monitor and manage those services. That's basically what the middle services so we have on demand services. We have resource bowling we have brought at network access, and we have rabid ah, elasticity, elasticity and means can increase up and down. Scalable. A resource willing means we had. They are providers, there are consumers, and they have to support multiple consumers. Tenants wherever you call now and broad network access means that we can actually from different channels. BC's tablets, smartphones, whatever Okay, made a set of says they have to be managed and monitored for many reasons. As I mentioned for effectiveness, for billing and Sarah and those basically the are they mean characteristic 4. Cloud Course 4 Virtualization Introduction: is off cloud computing now. Virtual ization is the technology that enabled this happening. And visualization is about capacity is about improving the effectiveness off, using the resources off, commuting okay, and virtualization is not computing, but it enable. The computing is the I T F aspect concept that enable the concept off cloud that made it happen. How it's applied. That's another discussion. But the bottom line of visualization is what makes cloud happening. So in another sense, virtual ization brought into the concept that we need to improve on our resources, how we use them, how to optimize them, how to consolidate them, how to make him run more efficient. So the visualization came and say, Okay, well, you know that's fine since we are, or the organization they don't use their resources the right way or that should be utilized . So will bring some kind of abstraction layer between the hardware side and operating side to separate that and manage the hardware side from the virtual ization from the abstract level. So anything on the operating system or could be different operating system after adding that visual ization abstraction layer that can use the virtualization toe access the resources instead of accessing it directly, and instead of being 1 to 11 operating system, accessing the resources off the computing, their sourcing off the computing are what the CPU, the processor, the storage, the memory, the network connectivity aspect, like the neck, those kind of things. Those are the resources abstraction came on top of them and say, OK, well, you can give me whatever driver for any operating system and will interact with the visualization layer, and they can access those resources. But I'll manage the resources the interfaces aspect, so the operating systems they can access the visualization visualization will manage the accessibility to the computing resources. That's basically the concept behind the virtualization. That's basically what enabled the whole thing. Now multiple operating systems can run on the same machine or same server. You could have multiple of the EMS, the end. They can be by used by multiple users, not one user. And they can basically have better way of scheduling and optimizing the utilization off the resources. So that came as part off this abstraction layer or the visualization layer. So when we have a server that have a visualization layer, we call it visually for actualization server, and in this case, we don't need to have multiple hardware servers we can consolidate. Bring multiple okay server into one. So the concept off having to have, ah lot of cooling a lot of electricity associated with multiple hardware servers. Now we can consolidate it into once ever. That can have multiple operating systems and that basically will reduce the size reduce also. Ah, the spending on multiple hard ones. That's a good constant. And that's basically what they're using in the club. The infrastructure now is basically consolidated. They can be using multiple virtualized servers. They're better than having hundreds of virtual assessor. I think cos they do like 10 or 20 servers consulted it into one virtual answer. That's a great advancement. That's basically what the enablement. But the virtualization is moving us to a new area. It's moving us to a better way off doing things, optimizing the resources, consolidate on the overarching concept. It is better capacity for the organization. That's basically where the virtualization aspect, but so visualization is more I t aspect. While Cloud is more business model of providing delivering services to the consumers and again. The transformation aspect is really important. If you look at the slide is saying we're moving from legacy, using virtualization to that to the cloud that's basically the enabling. 5. Cloud Course 5 Virtualization and Cloud Computing Value: ask people, Uh, this the common, um, the teams between visualization and the cloud and are the difference is the other. But it is the common barta lower, but is more The differences both shield their user from detail. The physical hardware multiple user can share the hardware resources. Both allow flexible deployment off city assets, Much hyped concert much. I mean, I get you gets you You understand that the ah bullets before, but much hype concert Because I e I mean, if you go toe in any discussion, you will find a lot off teams going back and forth and different understanding off. You know, cloud versus virtualization. They mix between them, but from the separation off concern. Think about that. The visualization as that I t cite the enabler side that allow was to optimize the resources off. I t okay and consolidate better while the cloud is the way we are or the cloud provider provides services to the consumer and both of them again, they try to shield you from their physical technicality. The hardware, how they do it all. You have to just consume from the consumers on multiple user captured the hardware resources we mentioned that before because when when we have a cloud computing in the provider support multiple consumers, the consumer the can sit on the same server. That's one, by the way, one way, even though there is a cloud service model that where you could have your own private cloud on Do you could have something Ah, hybrid mix between public and private, but we'll discuss some of that later. Both allow flexible to blow meant if I t as it Either way, you could buy that We have virtualized servers in your data center and you don't have to goto provider. I seen that so you could have your own. Ah, but the point here is really you the the main concept off Movinto Cloud has to have a strong enablement technologies such as virtualization. We have had a long time ago with the concept off hosting websites, and the co hosting websites basically does not have the elasticity, but on its little bit different than the cloud on does not very meet all the characteristics off the cloud. But the concept of posting also associated with the with the cloud where you basically you could build something and move it to, AH, hosting company and and basically divorce your your now in terms of what are the differences? Differences between them. Virtualization is a technology. While the cloud computing is a business concept, actualization is an enabling technology for many cloud services. That's basically summarized. What is the solution you've provided by Cloud to the organization, to the enterprises. If you are an executive or manager, what what do you think the cloud and virtualization will help you to resolve? So technically, the main thing is coast of access capacity. Because before you even start in, let's say that you don't have the cloud option before he even starts thinking about the solution. You have to start thinking about how much I'm going to spend on it. What hardware do I need to book your? Ah, what's so for? I need to book it. Those kind of questions from the capital expense, our point of view, something you have to account for. This is one aspect. So the financial aspect, the spending on buying infrastructure, computing resources, that's the one thing running out of capacity. It means that you could buy the best hardware now, but you made the better on. Okay, you need more because technically, probably use software updates. Its on I require higher, better, ah, capacity off the hardware that you have all the computing resources and at the same time, your capital is basically tied up and your hardware that you bought. Unfortunately, it just happens that way. So technically you cannot eliminate or you cannot do anything about it. It's already time while in the cloud computing. If you don't need this much capacity, you just don't take it. You turned its back and you get money for it, so you don't spend on it from the operational side. If I I'm using now, for example, ah, server that basically that cancer boat 100,000 users. Now I need a server that can support. Let's see 50,000 users so technically would reduce the CPU would use that started to reduce the memory. You could do that. You can say, OK, I don't want this much. I want this much. That's basically it's not tight, but when you buy it and you did isn't that you pay for? That's basically it. Solve a lot of issues from the business side. Ah, on the financial asked. No virtualization cloud 6. Cloud Course 6 Virtualization Cloud and Adoption Fitness to purpose: eating non suitability organization might not benefit from virtualization and cloud computing if they have Now, this is kind of concerned. Sometimes you see, a cool cloud is gonna resolve all the issues. Sometimes you have. I want to say those issues are, um, obstacles that you cannot eliminate some you could you could you could technically move on that and basically moved to the cloud. But technically, there are certain issues is so difficult to move to the cloud that do you have to account for, For example, if you have steady and fixed war clothes, you know that you the capacity is kinda clear to you, the coast clear to you. And also the source of supporting that clear to you, then probably moving to the cloud. Justin, you wanna dime that? You're gonna adopt a lot to do it. While you know that what you're doing is sufficient. You don't need to move. Then probably you don't see a value for for a club. Um, if you own large data centers, movinto a cloud is gonna be like a lot off work. And also a lot of course associated. So you need to consider moving to the cloud if you have a high compliance to standards, Um, we'll say from the health care from, um, real time critical systems. Ah, some system they have require a lot of security and privacy issues a lot off controls over those areas. So you need to think about nothing. You cannot. But there is an impediment. There is associated. There's a risk. You have to have an organization that have ah, the about I to this kind of risk to take advantage for the long term by moving. And they will take a lot off coast. So you just think about it. If you're gold behind, cloud is too. Contain the cost. Cut the coast. Technically, when you do some of those, he will have to put some course up front. Um, and technically will lose some of this. You just think about those issues and also high degree off operational assurance and you have a lot off editing. You have large operational teams. It's also, and governance. It means that there is a lot involved in the operational side. Moving to the cloud needs to be really and, you know, studied deeply as it cannot just be moving there so those issues on those types off works me not really benefit from moving to the club. I'm not saying they cannot. They can, but technically you had has to be a good study around. Now, let's say reason to adopt a cloud computing for email and document management. If you have even won a specific app or this the enterprise level app that you wanna move or not move our support or not support the rationale behind moving, why you need to move or why you don't need to move. You will find all those benefits here and there. Let's it look at the benefits for Let's say, adopt cloud computing for email means that outsource this piece or move this piece to, Let's say, the two Google email or some other cloud business ah supporting e e mail and document management at enterprise level. Their benefits benefits for the firm to adopt cloud computing for email and document management because the firm is expanding at will be easier to upgrade the capacity. This capital is required to be invested for this change. Okay, while the negative aspect while the firm should not adopt cult commuting document, madam is the core activity court activity. They wanted to be on any platform that can be shared with another tent with another consumer. There's a security, an issue about this one. And also there is competition aspect because this is our core. It's something we have to maintain. We have to control. So this is lot off, you know? Think about should we move it? Should we keep it? Because this is our core business and high risk is involved with the cloud services provider. Highly confidential information acquires in house storage. So the issue here is security and privacy. And if you cannot assure that with the service of right, even though you can assure now will serve supervisor at this ah stage, many organizations provide a lot of certification such as Microsoft Azure. Ah, um Amazon aws do provide certification around those kind of issues security. So you will find head value will have to find ah ah, other other certification. That's basically already in there. So technically you could find a solution for those. Well, just think about it always when you do something related to moving enterprise level application, think about those elements Ah, risk and privacy Coast. Um ah ha 7. Cloud Course 7 Could Computing Service Models: that's gonna em back. The stability of the organization. If you move it, how you gonna move it? That's basically a bigger discussion. But that's something the introduction that you need to be aware. No models for a cloud computing as a mission. There are always building blocks or services that you want to move. And if you move based on how much how many of them you move will dictate what is the model unities of cloud computing? If you want to move everything, you just become a sub sub Socratic burr to services like toe Google email. Okay, then everything is going to be on the cloud provider side. You only subsequent view only consume you only use utilize the service. But everything on the building blocks the services is going to be about off the cloud provider. That's gold cess. It's for the users, the consumers you consume. Now, if you are a developer, if you are someone who creates something APS Okay, then technically, you are going to the glad that form service combined to that P A s platform as a service. So technically you still need the runtime environment, the middle where the operating system correct. That's basically Bart off what they provide you. Okay? And sometimes this is a risky because if imagine that you are locked into Google, have engine and technically, Google provide you with a set off platform services execution environment to create and run your abs. Then you are locked to him. The same goes if you do with Microsoft or ah aws. There is a concept. Hair is just it's you locked yourself to specific vendor vendor has a specific set off technology that you have to stay with and moving after. That's gonna be costly and risky. So you need to think about this way. That's basically the blood form service component that's basically the second model we quote platform. As a service, infrastructure is basically about the computing resources we are now consuming. Only the commuting deserves the computers. That's basically for the administrator. They manage that they administrate that we're basically saying that they will do that So technically we're using their hardware, their servers. They provide us sometimes with even drive it environment. Multiple consolidated servers with the capacity off for those needed for our organization. CP use storages memories. It set up eso that's basically about of the infrastructure, which is the building block here. Network storage, memory, etcetera. That's basically what we do with the infrastructure, the computing aspect. Who's using the SAS, who's using the P. A s pass and who's using last? I asked Intrasection. Basically, the developer will use the platform while the user will consume. The developer will create the apse consumer off the SAS will be the users users off this, using the software well on the operations side, the admits will basically will use di ous to provide application services as basically something you have to remember who's using and why they used. Now the user accounts. It's wide, let's say wa wide access global collaboration subscription based Just what examples here some Islington and others, Facebook and others. It's easy to digest technically all other building blocks, services and resources. All of them are in the class of supervised. And now, if you go to that again, this is more about the use for the SAS. If we go about the black form side, when we give me environment where I can develop certain things like azure or Google and have engine, I'm a developer I need to build some things. I need to create something. So I have to use a platform. Give me, then. Environment, runtime environment that I can build. Give me the job. A platform. The spring. Give me Give me those kind off. Give me Let's say they give you the Microsoft Studio, um, framework so I can build Build that. Give me the runtime, Inbar. 8. Cloud Course 8 Service Models and Deployment Models: and for the middle, where their take and use okay, just to support building abs and services as physically about of the blood forms. It's easy to digest allows users to create their own cloud application using existing tools as script languages. And also, I want to add to this one beanstalk from, Ah, Amazon AWS. That's another one. Now, if you go toe i A s infrastructure as a service infrastructure as a service is technically for more the operators, the admits, um, there are many examples. I guess even Microsoft is moving to that by now and supporting it. And also Rackspace and Amazon is the biggest and has basically the, you know, the biggest infrastructural compared to the others even though, um, Google Microsoft, especially Microsoft trying to catch up. But those are the ones that you provide the computing resources. Would they allow you to run old times of application on selected oclock? Cloud hard work the broader with the computing sources, the hard with the actual hardware. Now the virtual hardware, just the actual hardware, any cavern on top of that, whatever virtual on. But the actual processors computers it, Sarah servers that's basically provided in the infrastructure. That's basically what what you have and usually the bride of virtual servers, including storage. And also it's a flexible use. They can change that and basically we want to stay flexible use. There is a reason for that one, but because this is really critical and technically speaking, when you see the five characterise characteristics off ah cloud computing, we know that this is really if you don't have that one and you don't have cloud, you have Barschel clam and especially on the first section cannot be. That has to be very flexible because this is basically what hosted platform, what was the software and that cannot be, ah, below that blood has four deployment models or in somebody could be three deployment models because we have the public ah Cloud, which is operated by 1/3 party in general. And also there is the private cloud, which is operated for exclusive use off of articular group, and the mixture, which is some combination off the public and bright. So in summer you could say that three deployment model off bladder could seek out a deployment models. You really the cloud deployment model means that the Amazon Cloud Provider services provider opens up the my cloud infrastructure for open usedto open use for everybody that they can use. So then infrastructure will be in the premises off the service provider, but it will be operated by whomever come and you wants to use it. Whether it's academia, government, business, health care. It's also, technically, they will be operated by that one. We offer. There's a cloud are for the service, and there is a consumer would basically operate this specific ah club. And if you look at it from the perspective with that fits in the state of this model, technically, it fits on the infrastructure side. So in the infra sexual as a serious side, that's basically what's the offering now? What's different between public and private? A bribe it has. You have more control, more secure coast, more sometimes even the drive. It can be hosted by internally and not necessarily extended. That's an option. So look at it from that perspective. Just do you have a cloud provider are for this infrastructure and anybody can come and use it if it's in the share environment as basically public because it's used by others also. So this is why I technically say, has a good security. But it's not like the drive the cloud where we have better security. And also it's probably easier to implement and also low operational costs because it's basically based on the cloud provider ah, administration maintenance operational course. So technically, it's going to be lower cost for the consumer. The cloud consumer and from the coast's definitely better cost effective than the right cloud. While the gravity cloud is it could be in your as a mission could be in your data center. It could be in the cloud provider. Ah, infrastructure with a block, a public cloud. You don't dictate their location while in the grabs cloud you could dictate the location, so they just keep that in mind. So just think about it. Cloud has different deployment by that have services in for a sexual sense that there can be consumed whether they consume on the shed environment or they consumed on the you're a private environment. Even in the 9. Cloud Course 9 Deployment Models and Summary: the environment is going to be even like you want to say, I want to have my order. Private cloud But I wanted to be on the cloud provider environment that's going to be dedicated to your organization. You're been it it. Okay, so that's basically what's different between public and private. Now. Hybrid is in between. It means that you could have, like a public and a private cloud. You could have some some ah services hosted on the ah public cloud, and some hosted privately. And there's some direct connection between the baby and it or whatever. But this is basically where the in between the same goes with the community cloud could be the community cloudy, just also a mix off the combination. But it's for the for a specific community from the social aspect from It could be political cultural aspect. It could be based on city. I think it's a little bit, ah, different from the type off the consumers, the user type, but it's basically it's a mix between between public and private. So we have four deployment models, private community, public on hybrid, okay, and we've drive it. We know it's going to cost us more, it's gonna be more secure, more reliable, and you will have over control. Better control over the cloud infrastructure that you have. Um, and user get both network access and computational resources from revived higher. Better and again, it's more scalable than you know. The public out there isn't why it's now. It's more used by you, not shed environment now in in terms off Just summarizing what we have discussed. We mission that there are three Cloud Service models software as a service. It's basically application use. You subscribe to the service every build. All the building blocks are on the cloud provider side, and we provided examples on that. The thing goes with the platform as a service. Who said this is an application of creation side They provide you with the FBI's with execution environment? Run time environments are so this is for the developers while their social as a service for the users. And he said the 3rd 1 is the infrastructure as a service, i e. A s, which is me about the infrastructure, the hardware replacement. Ah, we also mentioned there are different cloud deployment models. We mentioned that there is a public cloud operated by 1/3 party in general. And also we have arrived the clouds overrated for the exclusive use off articular. A group always said that combination between public and drives. We called mixing there many types, some of them. They call him hybrid community itself. Now, from the user profile as a mission earlier cloud solutions On the profile side, they use that they use the cess. The developers. You mainly use the P. A s the platform as a service the letters and admitted to use the infrastructural as self. Just keep those in mind and I mission also there are certain essential characteristics known to everybody, that if we're talking about the cloud we're talking about, it's going to be accessed through the Internet. So Internet based uses were charging shared resources. When you say the source schooling Ah, scalability and elasticity. Ah, as common attribute. So this is basically what we describe from the definition ball interviewed. We said when we say cloud is a business model, often I t services and resources management and we also say that this is a business model. Okay, The way we're using things, managing things from the technology said. They said we cannot have a cloud without a virtualization because this is enabling technology for the cloud. And we said the relationship between the cloud and visualization, it's more about the capacity. Okay. And we discussed some aspect about the visualization that we will discuss and technical, I hope, Discover the introduction Bart, and address some of the main things about the essentials for Thank you, Let's go.