Cloud computing Azure overview
Download as PPTX, PDF1 like273 views
The document discusses IT infrastructure capacity and cloud computing models. It covers topics like installing operating systems, routers, patching, upgrades, environments, load balancers, and hard drive failures. It compares actual and allocated IT capacities over time and how "IaaS", "PaaS", and "SaaS" cloud models work. The models differ in what layers of the stack vendors manage versus what users manage themselves.
Cloud computing Azure overview
- 2. Installing OS Routers Patching Zero downtime Network Hard drive failure Memory Storage Upgrades Environments Load balancers
- 5. IT CAPACITY Not Enough Power Too Much Power Actual Load 5 Allocated ITcapacities TIME Load Forecast
- 9. IT CAPACITY Lower Capex No screaming customers Capacity on Demand No capital laying idle Load Foreca st Knob goes up... And... down Actual Load TIME
- 11. Packaged Software Applications Applications Software Applications Applications Data Data Runtime Runtime Middleware Middleware Middleware O/S O/S O/S Virtualization Virtualization Servers Servers Storage Storage Networking Networking Middleware Runtime You manage You manage Runtime Data Managed by vendor Virtualization Servers Storage Networking O/S Virtualization Servers Storage Networking Managed by vendor (as a Service) (as a Service) Managed by vendor (as a Service) Data You manage Platform Infrastructure
- 13. Hard disks and Power
- 14. Set up Racks
- 15. Pack the racks into a Container
- 16. Install the optimized HyperV, Host VM, Guest VM(8)
Editor's Notes
- #3: Need to worry about the h/w, setting it up, n/w, load balancingThen installation and patching up of applications as well as hwThen need a lot human resource to jst managing thisNeeds to worry more about the infrastructure than application itselfAdditional cost overheads
- #4: First buys h/w for setting up the serverSupport staff needed for maintenance and supportMaintenance activities
- #6: Slide Objectives:Understand the challenges of irregular load in applicationsUnderstand the challenges of both too much capacity and not enough capacity and the sort of groups they impact within a customerUnderstand that traditionally IT capacity is purchased in a stepwise fashion involving capital expenditure at each pointSpeaking Points:To understand the value and opportunity for cloud computing, I believe it’s important to think about how IT capacity is typically used by applications today in most environments.Today most organizations significantly over estimate or underestimate the amount of resources they need to run their applications.This leads to a higher cost for the infrastructure and the delivery of the overall applications. Build Steps:Forecast load is to grow steadilyPlanned capacity grows in a stepwise fashion. Need to plan in advance due to hardware lead timesActual load is highly variable over timePeriods where we have excess capacity. Capital laying idle, opex wasted powering and cooling serversPeriods where we have insufficient capacity and our customers get a bad experience
- #7: Slide Objectives:Explain how Microsoft thinks of the cloudSpeaking Points:Cloud is the new buzzwordTechEd 2011 focus was on cloud, wp7Can be defined as a set hardware, networks, storage, services, and interfaces that combine to deliver aspects of computing as a serviceBasically a set of connected servers on which developers can install and run services, store and retrieve data
- #8: Slide Objectives:Explain how Microsoft thinks of the cloudSpeaking Points:Cloud is the new buzzwordTechEd 2011 focus was on cloud, wp7Can be defined as a set hardware, networks, storage, services, and interfaces that combine to deliver aspects of computing as a serviceBasically a set of connected servers on which developers can install and run services, store and retrieve data
- #9: A set of connected servers spanned over the internetOn which dev can install and run services, store and retrieve data
- #12: Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaking Points:With this in mind, it’s important to understand how to talk about our Cloud Services offerings.There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
- #13: Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaking Points:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure Platform best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.