• Share
  • Email
  • Embed
  • Like
  • Private Content
Autopilot for your Cloud
 

Autopilot for your Cloud

on

  • 829 views

An overview of how to build a sustainable cloud

An overview of how to build a sustainable cloud

Statistics

Views

Total Views
829
Views on SlideShare
829
Embed Views
0

Actions

Likes
0
Downloads
24
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • So one of the biggest problems we all the time is the fact that infrastructure sprawl is really hurting your ability to innovate for your businesses and, in fact, the numbers you see on this slide are actually real numbers based on a global survey where people are saying that they spend 70% of their IT dollars running legacy infrastructure and only spend about 30% of their dollars really on the things that make IT a hero to their businesses – bringing out new innovations, new applications to help become more competitive in the businesses you are already in, or new applications that help you get into new businesses to help generate more revenue and profit for your companies ... or for your agencies. So we want to is help you spend less money managing legacy things and more money doing the things you want to do around innovation.15-20 years of IT sprawl have business at the breaking point. What this means is that customers are struggling very hard to balance the growing business demands and pressure from the business with an increasingly siloed and inflexible data center that’s based on traditional infrastructures .. And that’s not enabling them to meet the demands of the business as quickly as they need to.>> This is a fairly typical slide showing complexityApplications more complex, at DC level multiple boxes, not energy efficient, cables, running out of space in data centersDifficult to manage: Mgmt different tools, complex, can’t keep track of apps – too many people, too much infrastructure, too many appsMultiply by1000s of apps, dozens of data centersIT is spiraling out of control, customers are afraid, they know what they want but don’t know how to get there, need guidance, Don’t want to rip and replaceThis sprawl has a wide-reaching ripple effect across the business. It causes business to suffer from slow time to revenue … opportunity cost through lost time, effort, opportunity … and the lack of predictability around business cycles. Business application owners are looking for faster time to value, quicker returns on technology investments, and increased service levels. They’re happy with over-provisioning if that gives them the assurance of better application performance. But on the infrastructure operations side, IT is under tremendous pressure. Because of sprawl, trapped resources, manual processes, rigid and aging infrastructure, and application and information complexity … has all lead to over provisioning and underutilization of the infrastructure ... stranded capacity … and the exponential potential for errors. For two decades, IT organizations have been adding servers, storage, and networking devices to keep pace with business demand for applications and the terabytes of data they generate. The problem is, because of the sprawl, those resources are tangled up in legacy architectures and inflexible stacks of IT. The result is that the average business spends 70% of the IT budget on operations versus innovation … bringing businesses to the breaking point.Plus, back to my earlier point … the cost to operate and manage all this is unacceptable. Essentially, they are on the wrong side of the 70/30 ratio, they are on the 70 side from a maintenance standpoint. They are spending more time on maintenance and less time on innovation and new services and BOTH IT and the business want to change that ratio and flip it.When you look at a major trend today in the marketplace – virtualization – its only serving to help accelerate that sprawl and make the problem even worse. So, the key message here is that you require new way of thinking about the traditional infrastructure to flip that ratio and make IT the strategic driver for the business.Were hearing from customers that they definitely have an increased sense of urgency to have their datacenter assets and their investments work better together to drive the business forward. HP has been investing in and working hard for many years to make our solutions better together. So, as we see customers looking to work with fewer more strategic partners, there is no better partner to work with than HP to deliver on the vision to move towards Converged Infrastructure or a shared services environment so that they can manage their entire environment as dynamic pools of resources so that they can have a lot more flexibility.
  • Foto from HP Media Library, un-restrictedlicenses.
  • Help you transform your infrastructure to optimize for cloud
  • IT architectures are evolvingWe are now moving from the traditional physical service to a virtual service (analysts state that 50% of all x86 servers would be virtualized by 2012); many of our customers are also considering adopting cloud solutions – either using public cloud environments or creating public Cloud data centers. As the services evolve, the complexity of the services is also increasing. And so is the dynamic nature of the service. The virtualized service changes at a much faster rate than the physical service and the cloud-based services, change even faster
  • The cloud environment is very diverse - There are many delivery modes and usage models for clouds. Clouds can deliver:Infrastructure as a service – deliver compute, storage to end customersPlatform as a service – deliver application building blocks – web servers, J2EE/.NET server, DB servers to build custom appsApplications as a service – where fully packaged apps are delivered to customers (example Salesforce.com, SErviceNow etc.)Enterprises can also use a public cloud service (example Amazon, Force.com), build and deliver services via a private cloud or use a hybrid environment – leveraging public and private clouds. Whatever the choices, enterprises need to manage the health – performance and availability of the services – infrastructure, platform, applications – delivered via the cloud environment.
  • Today, when most people think of cloud, they either think of applications in the cloud, such as Software as a Services – which is fine if your application is available in a SaaS model – or they think of Infrastructure as a Service such as Amazon or other emerging players. Or they may think of building their own internal private cloud. These approaches provide many benefits, including faster provisioning and better utilization of resources
  • Without the right management suite and partner to pull it off, the job gets more difficult not less. Cloud may not have the silver lining you were expecting.
  • Some of the symptoms of that problem is that it takes an incredibly long time to get a server up and running and an application up and running.Multiple organizations, different areas of expertise whether it be server, storage, network and management, facilties. Whenever you plug in a server into this infrastructure, you have to cable it up to all those domains, but its not just the cable clutter if you will that is slowing things down, its also that every time you do one of these things, theres a process associated with it. And that process has a lot of manual overhead as well. So the end result is that the architecture that we have built in the last 10-15 years in the data center, kind of the rack, stack and wired world as its called in the past, this architecture forces some incredible organizational complexity on the customers when they go to a larger deployment. Complexity in terms of phy. As well as process complexity.We understand what the problem is and where it came from.[this slide is a simplification of the time-consuming process of standing up complex infrastructure. Make sure the customer sees their own process in all or part of the diagram]To provision new application infrastructure can takes weeks or months due to complexity. This process typically involves reviews and approvals, meetings and more meetings, plus the unpacking and implementation of the systems. The bottom left hand corner reflects the siloed nature of data center teams that must coordinate the build process across servers, network, storage and facilities, as in the previous slide. These meetings, handoffs and wait times between teams are just one aspect of the complexity in the overall provisioning process. [Note stop sign and heading back to the beginning in an endless loop] And sometimes the process can get derailed, requiring a return to the starting point and creating further delays.GET MORE NOTES IN HERE
  • Some of the symptoms of that problem is that it takes an incredibly long time to get a server up and running and an application up and running.Multiple organizations, different areas of expertise whether it be server, storage, network and management, facilties. Whenever you plug in a server into this infrastructure, you have to cable it up to all those domains, but its not just the cable clutter if you will that is slowing things down, its also that every time you do one of these things, theres a process associated with it. And that process has a lot of manual overhead as well. So the end result is that the architecture that we have built in the last 10-15 years in the data center, kind of the rack, stack and wired world as its called in the past, this architecture forces some incredible organizational complexity on the customers when they go to a larger deployment. Complexity in terms of phy. As well as process complexity.We understand what the problem is and where it came from.[this slide is a simplification of the time-consuming process of standing up complex infrastructure. Make sure the customer sees their own process in all or part of the diagram]To provision new application infrastructure can takes weeks or months due to complexity. This process typically involves reviews and approvals, meetings and more meetings, plus the unpacking and implementation of the systems. The bottom left hand corner reflects the siloed nature of data center teams that must coordinate the build process across servers, network, storage and facilities, as in the previous slide. These meetings, handoffs and wait times between teams are just one aspect of the complexity in the overall provisioning process. [Note stop sign and heading back to the beginning in an endless loop] And sometimes the process can get derailed, requiring a return to the starting point and creating further delays.GET MORE NOTES IN HERE
  • Some of the symptoms of that problem is that it takes an incredibly long time to get a server up and running and an application up and running.Multiple organizations, different areas of expertise whether it be server, storage, network and management, facilties. Whenever you plug in a server into this infrastructure, you have to cable it up to all those domains, but its not just the cable clutter if you will that is slowing things down, its also that every time you do one of these things, theres a process associated with it. And that process has a lot of manual overhead as well. So the end result is that the architecture that we have built in the last 10-15 years in the data center, kind of the rack, stack and wired world as its called in the past, this architecture forces some incredible organizational complexity on the customers when they go to a larger deployment. Complexity in terms of phy. As well as process complexity.We understand what the problem is and where it came from.[this slide is a simplification of the time-consuming process of standing up complex infrastructure. Make sure the customer sees their own process in all or part of the diagram]To provision new application infrastructure can takes weeks or months due to complexity. This process typically involves reviews and approvals, meetings and more meetings, plus the unpacking and implementation of the systems. The bottom left hand corner reflects the siloed nature of data center teams that must coordinate the build process across servers, network, storage and facilities, as in the previous slide. These meetings, handoffs and wait times between teams are just one aspect of the complexity in the overall provisioning process. [Note stop sign and heading back to the beginning in an endless loop] And sometimes the process can get derailed, requiring a return to the starting point and creating further delays.GET MORE NOTES IN HERE
  • This is a typical workflow process for setting up private (internal IT) clouds.
  • This is a typical workflow process for setting up private (internal IT) clouds.
  • This is a typical workflow process for setting up private (internal IT) clouds.
  • Need to make sure that people know that CSA for Matrix is a tuned version for Matrix.HP is focusing on three delivery models for Cloud Computing. HP BladeSystem Matrix for infrastructure on-demandHP BTO Heterogeneous Cloud Solution for large enterprises or managed service providers that require complex integrations and additional management needs associated with chargeback, billing and mediation,
  • Demand Definition: This layer represents all aspects of capturing and meeting demand from your customers (internal or external), captured and made available as configure-to-order – that is to say highly standardized and simplified services that can be readily delivered at the press of a button in mins/hours not days/weeks/months. The demand layer encompasses the lifecycle of the relationship between the consumers and service instances.Delivery Definition: This layer represents all aspects of assembling and managing the underlying resources into a form that can be offered as a useful/appropriate service to consumers in an automated fashion. The delivery layer encompasses the lifecycle of both the service offering and the service instance and binds the resources to the appropriate service instances.Supply Definition: This layer represents the building blocks (resources) that a service is comprised of – which could be a combination of compute/storage/network, or an existing IaaS/PaaS – internally or externally to the company. The supply layer encompasses the lifecycle of resources – which may be assets of the company or sourced as services from external entities.Service Governance Definition: This represents key aspects of service strategy and service design (ITIL v3) – managing the portfolio, suppliers, partners, markets, customers, finance, enterprise architectures and policies, demand, cost models, investments, service lifecycle (inception to retired), security requirements, business continuity, etcService Management Definition: This represents key aspects of service transition, service operations and continual service improvement (ITIL v3) – change, configuration and release management, incident/problem management, event management, service level monitoring, continuity/capacity/security/performance management.Another way to think about the distinction between Service Governance and Service Management is time frame – governance is about the big picture over the entire lifecycle of services from strategy generation through to design.Where as service management is (largely) about operating the service environment – getting stuff into production – making sure it is meeting SLAs – fixing it when it is not – providing feedback into the lifecycle for improvementsKey point: Building a cloud offering is not performed in isolation – the full range of service management and governance principles and products apply and your cloud offering must integrate with these.
  • Picture from HP Media Library, norestrictions
  • Picture from HP Media Library, norestrictions
  • The combination of the upcoming release of Application Deployment Manager, Virtual Machine Cloning and our comprehensive consulting and design services will help customers speed the time to cloud adoption by: automating the deployment of applications in the cloud (whether public or private), automatically provisioning compute capacity to support the application deployment and by monitoring and managing the ongoing performance and availability of the application and supporting infrastructure. With this approach, clients can expect to realize significant savings in CAPEX as well as better utilization of resources and faster time to deployment.
  • More from service provider view nowCloud Assure: combination of sw and services to address to 3 cloud concerns - security, performance, availability: ASC, PC, BAC - team of experts do security scans, executes perf tests, and deploys availabilty monitoringCost: videon on youtube how to use OO to Announce at SWU Hamburg 2009 (same as BMC function)HP OO can now integrate external cloud services,OO provisions server in Amazon's EC2 external cloud
  • First of all, HP BSM enables you to manage your cloud service as a black box service. We can manage the end user experience of that service and tell you if it meets the SLA of the business.
  • The HP Software system is comprised of a comprehensive and effective portfolio of software and services.The BTO portfolio addresses all the key domains of the IT organization – strategy, applications and operations. In each of these areas, we have identified multiple centers, which are tightly integrated groupings of products that solve a particular set of concerns for various IT teams. Additionally, our integration technologies allow us to share information not only across product centers, but with practically any relevant IT data source. HP’s BTO system provides workflow or process automation capabilities within all three IT domains. In the highly complex and constantly changing production environment, this capability is provided by HP's Operations Orchestration offering, tying together service health, service automation and service management areas of operations.The Universal CMDB, together with HP’s Discovery and Dependency Mapping capabilities, provides a federated repository that captures critical information to help you manage your production environment. This allows you to quickly discover configuration items (CIs) and their relationships, and to determine the impact that various events and changes have on your IT infrastructure, applications and services.A number of these specific product centers can be delivered very quickly to the customer using our software as a service offering. The capabilities that can be delivered by software as a service are denoted with a cloud icon.Here are the key capabilities of the BTO centers:Project and Portfolio Management Center – provides the ability to capture demand from the enterprise and create a single IT portfolio plan, and related resource plan, for that portfolio.SOA Center – provides all necessary governance and management for the implementation of a service-oriented architecture.Quality Center – provides a complete environment to assure application functionality including requirements management, test planning, and test script design and execution.Performance Center – validates application performance by simulating user loads to ensure applications can scale as required in production.Application Security Center – allows IT to address security concerns before applications are rolled into production.Business Availability Center – enables IT to understand the business impact of services that are being delivered; additionally, BAC allows IT organizations to measure success by monitoring transactions that span multiple applications and complex infrastructures.Operations Center – provides a single pane of glass for event and basic performance information spanning networks, systems, applications and storage.Network Management Center – a robust suite of network management capabilities that provides information regarding network inventory, availability, performance and changes.Data Center Automation Center – based on technology acquired from Opsware, this center provides a complete approach to automating change across all the key aspects of the data center, including networks, servers, storage devices and applications.Client Automation Center – this technology complements the Data Center Automation Center by providing model-based change and configuration management for clients across the enterprise.Service Management Center – provides two critical capabilities for the enterprise: first, a consolidated service desk and, second, industry-leading asset management solutions.
  • M

Autopilot for your Cloud Autopilot for your Cloud Presentation Transcript