1 January, 2012 Six Steps to Private Cloud Adoption Key Considerations, Insights and Recommendations By Shantanu Paknikar Happiest Minds, IT Services Group
2 Six Steps to Private Cloud Adoption In the very well-known book The Tipping Point by Malcolm Gladwell, the author defines a tipping point as a moment of critical mass, a threshold, a boiling point. The author also draws a parallel between the spread of certain ideas, products or concepts and the spread of viruses and epidemics once they are past the tipping point. While the concept of Cloud Computing is not completely new, it certainly appears to have reached the tipping point. The world over, across industry segments, across business and IT organizations, cloud computing is now being considered as one of the game changers. Organizations the world over have started moving to, or are planning to test the waters for the cloud. Cloud adoption appears to have acquired epidemic proportions. Some time back, the cloud usually meant the public cloud scenario software being delivered as services over the internet. Today however, there is an understanding that we could also have private (on-premise) or hybrid (combination of public and private) clouds. Private cloud implementations are happening and will continue to happen for the simple reason that implementing them makes good business sense for large enterprises with significant investments in their own data centers, applications and infrastructure i. The six step approach described in this paper is primarily focused towards a private cloud scenario. Business Overview The overall business drivers for cloud adoption are straightforward and well known: 1. Cost Optimization due to the increased utilization of resources [hardware and software] as a direct consequence of resource sharing. Optimization also results from the lower maintenance and upgrade costs that on-premise software would typically require. 2. Increased Agility due to the concept of elasticity or the rapid scale up and scale down of resources that is made possible by the cloud. With such agility, businesses can adapt rapidly to changes in their environment: For example, online retailers who see transaction volume spikes during the November December months in the USA. 3. Better Cash Flow Management due to the conversion of capital expenditure [e.g. software licenses, server and storage infrastructure] to operational expenditure [e.g. monthly rental]. A detailed discussion on the above is outside the scope of this paper; however there are some excellent references available for the same ii. The figure below illustrates the future (in some cases, present) scenario for a typical enterprise s private cloud implementation. The layers for infrastructure (IaaS), platforms (PaaS), Software (SaaS) and Business Processes (BPaaS) are well known from the As a Service terminology perspective.
3 Besides the IaaS, PaaS, SaaS and BPaaS layers, private cloud implementations will need to have layers for cloud security, cloud management, cloud integration, and cloud consumption. Cloud integration will need to happen both with on-premise applications that may not be moved to the cloud, as well as with public cloud applications. Figure 1: Cloud Scenario - Pictorial Depiction One of the fundamental questions to be addressed by most organizations is their readiness for cloud adoption. This paper describes six steps and key considerations for each that would help organizations during the initial strategy and roadmap definition phases for private cloud adoption. These six steps are depicted in figure 2 below. Figure 2: Six Steps to Private Cloud
4 Step 1: Virtualization Virtualization Overview The concept of Virtualization can be considered as the trigger or catalyst for the entire phenomenon of cloud computing to the extent that a lot of people believe that the terms virtualization and cloud can be used interchangeably. While cloud computing today is much more than virtualization, the fact is that without virtualization there would have been no business case for cloud computing anyway. Virtualization can be defined simply as The conversion of physical assets into virtual ones. Assets could be hardware (such as computers, servers or disks), network, and software applications. Usually however, the initial and primary focus of virtualization is conversion of physical infrastructure (for example, desktops, servers, storage) to a virtual form. In particular, the focus in this article is on virtualization in the context of physical machines being converted to virtual machines. The Business Case for Virtualization The business case for virtualization is simple: over the years, data collected shows that hardware infrastructure has been grossly under-utilized, averaging around 30% of maximum capacity iii. With virtualization, each physical server can be converted (in this case for example) into three virtual ones, moving the overall utilization to around 90%. Equally important is the fact that virtual machines can be provisioned and de-provisioned on demand. Consequently, the same physical infrastructure can be shared across multiple customers, by the allocation of virtual machines as and when needed, and the de-allocation when not. This results in the ability to charge the customer based on usage one of the cornerstones for the concept of cloud computing. Key Considerations The important factor to consider for virtualization is the analysis and selection of a software vendor. Today there are a large number of vendors to choose from in the market. The primary piece of software that enables the conversion of physical machines into virtual machines is the hypervisor. Therefore, vendor selection criteria include factors such as hypervisor robustness and performance, virtual machine density, supported platforms, and enterprise architecture suitability. Besides the hypervisor, there are usually other associated products offered by the vendor. The scale, number, and maturity of these products can also be used as additional vendor selection criteria. Output The output of this step is virtualized hardware or in the advanced case, a full-fledged Infrastructure-as-a-Service (IaaS) implementation. Planning for the Future The future is fairly easy to predict it is very likely that (almost) every desktop and server machine in the enterprise will be a virtual machine, being accessed through mobile devices
5 such as netbooks, tablet computers and smart phones. Therefore, the aim should always be for near 100% virtualization. There needs to be a clear plan and roadmap for this with execution closely tracked. Step 2: Portfolio Analysis To migrate, or not? Once the cloud adoption decision is taken, the next step after virtualization is in the area of Portfolio Analysis for the IT application landscape. The primary objective of portfolio analysis would be, at an application level, to decide on the migration strategy. Portfolio Analysis in itself is not a new area, being for example an integral part of approaches to Application Portfolio Rationalization initiatives which large IT organizations often execute. In this case, when the destination is a cloud, however, there are some unique aspects which need to be kept in mind. Unique Aspects during Portfolio Analysis 1. Some applications will need to move to the private cloud in a Lift and Shift manner, with the applications themselves remaining largely untouched. Typically, these are likely to be custom applications with business dependencies such that any re-engineering would be detrimental to business interest. 2. Some applications or application functionality will need to move to the public cloud. There could be two scenarios here: a. Some functionality could be consumed from the cloud out-of-the-box. For example, some organizations may have custom applications (e.g. for CRM, ERP, and other areas) which can be retired, with the same functionality being consumed as SaaS functionality from established players such as Sales Force (SFDC). b. Alternatively, some functionality could be developed on public cloud PaaS platforms like the Google App Engine or Force.com. 3. Some applications might get re-engineered to SaaS applications that are provided to the external world. That is, the organization becomes a provider of SaaS services in some scenarios. An example is a bank offering payments services to other banks, or the more easily understood software vendor offering their software as SaaS. 4. Finally, not all applications and functionality will move to the cloud. Several applications could continue to remain alive as on-premise applications. For example, this could be for reasons related to criticality high criticality implying a do not touch approach and low criticality implying a to be retired / killed in the future approach. Key Considerations The important questions that need to be addressed in the Portfolio Analysis step are 1. What is the split up of the above 4? 2. On what basis is the split up to be achieved? 3. How is the prioritization to be done? For example, which applications are cloud ready, and which require some effort to be made cloud ready?
6 Output The output of the Portfolio Analysis step is a document capturing the current application landscape and showing the recommendations, per application, for the Cloud Migration / Adoption strategy. Planning for the Future While hardware virtualization delivers the benefits of infrastructure optimization, the next level benefits of cloud adoption will be realized only when platform and application functionality is moved to the cloud. Therefore it is clear that any enterprise cloud adoption strategy will need to have a clear, precise and well planned approach towards Portfolio Analysis in place. The aim for this step should be that of Selective Adoption - Move platforms and applications in a phased manner and avoid a big bang / all or nothing approach! Step 3: SOA Revisited The cloud computing world of the future will be the world of Services. Every piece of application functionality on the cloud will need to be available as a service. The cloud will be the intermediate platform for service producers and service consumers to come together fulfilling the vision originally outlined by the concept of Service Oriented Architecture (SOA). In fact, just as SOA in the previous decade was synonymous with Web Services, SOA in the current decade is likely to become synonymous with Cloud Services. Key Considerations Service Definition is a well-known topic in the world of Service Oriented Architecture (SOA). The concepts will be similar in the cloud services world as well, though implementations could be different. The input to the Service Definition phase will be the portfolio analysis document produced at the end of step 2. While the portfolio analysis document focus on the applications themselves, the focus in step 3 will now be on the application functionality that will need to be available in the cloud, but may not be migrated as-is. This essentially means two types of application functionalities: a. Applications (e.g. Custom CRM) that will be retired on-premise and consumed from a public cloud provider. b. Applications (e.g. Custom Business Related) that will be retired on-premise and re-engineered to be hosted on the private cloud. During Service Definition, the work will be the identification of the application functionality that needs to be implemented as cloud services, and the definition of the cloud services. The service definition also needs to include the definition of service level agreements (SLAs) that the service can support. Output The output of the Service Definition phase is a document that provides, for the list of applications from the portfolio analysis document, the set of services that each application
7 maps to, the SLAs for those services, operations involved, input and output data, and a description of the service functionality. Planning for the Future Cloud services that replace on-premise application functionality should 1. Offer the same (or enhanced) functionality as the on-premise applications they are replacing 2. Offer nearly the same performance characteristics as the corresponding functionality on-premise. In private cloud scenarios, it is likely that the SLAs for cloud services / applications will be the same as the on-premise applications. However in public cloud scenarios, there is a possibility of deviations since the platform SLAs available might be different from the exact requirements. In either case, the key consideration in this step is to aim for near zero SLA deviation with the on-premise scenario. Step 4: Technology Planning The advent of Service Oriented Architecture (SOA) introduced a paradigm shift from the client server model to a service producer service consumer model. Cloud computing is likely to take this paradigm shift to a logical conclusion. The enterprise (cloud) architecture of the future will need to be built keeping in mind computing available as a service be it infrastructure, platforms, software, data, or business processes. Key Considerations Some of the things to keep in mind from a technology roadmap and architecture perspective would be as follows: 1. Vendor Selection: There are a large number of vendors at each layer of the cloud stack. During the technology planning activity, vendor selection should be an important focus area. 2. Private cloud scenario: For a private cloud, the architecture roadmap would need to cover most of the layers depicted in figure 1. It would also be necessary to keep in mind the perspectives of both the cloud provider [internal to the organization] and consumer [also internal to the organization]. For example, the provider perspective would need to consider application deployment and provisioning aspects, along with monitoring and management of cloud services. 3. Public Cloud Scenario: In this case, the architecture would need to address the perspective of the consumer only. 4. Hybrid cloud scenario: In this case, the architecture roadmap would need to elaborate on the interface and integration aspects. One other aspect to consider would be on how cloud burst situations would be handled. 5. Cloud Integration: As depicted in figure 1, in steady state an enterprise will have some applications migrated to the private cloud, some continuing as on-premise applications, and some applications retired with the corresponding functionality being consumed from the public cloud. Application integration in a cloud scenario
8 therefore becomes a key consideration in architecture planning. Service Oriented Integration, followed by SOA practitioners, would be the recommended approach to follow in this case. 6. Management & Monitoring: In case of private cloud implementations, one of the important things to keep in mind is the management and monitoring aspects. These are sometimes overlooked because of the mindsets that are oriented towards public cloud, where services are merely consumed and the consumer does not need to manage and monitor them. Management and monitoring includes health checks for services, usage data collection, access management, managing scale up and scale down requirements, and so on. 7. Security Considerations: These are outlined in the section below. Cloud Security Cloud Security is a topic that evokes strong reactions - usually these are concerns on the security aspects of cloud computing. Consequently there is a lot of material, some of it hype and some excellent references, around the area of security and cloud computing. One of the best starting places is the Cloud Security Alliance web site iv. Key Considerations for Cloud Security Private cloud security will be similar to on-premise security, with some unique aspects: 1. It is important to evaluate the vulnerability of the cloud enablement platform itself (e.g. hypervisor vulnerability). 2. You would also have access control policies for your on-premise applications. When moving these applications to your private cloud you might need to redefine these policies. Public cloud security is where there are some apprehensions. However, in an age where we have so much of internet e-commerce, payment systems, card transactions, all happening online, the issue of public cloud security might not be as complex as it appears. When consuming services from the public cloud, you would need to evaluate the Cloud Provider s security policies and keep some of the following in mind: 1. How does the provider implement Identity and Access Management (IDAM)? 2. What data protection / encryption mechanisms are being used? 3. What type of logging, tracking and audit mechanisms are in place? Where is the audit data stored? 4. Where is business data stored? 5. What types of application security standards (e.g. Web application security) are being followed? Output from Technology Planning The output from the technology planning phase is an Enterprise Cloud Architecture document this is the recommended blueprint for all the technology and architecture aspects of cloud adoption in the enterprise. This blueprint should outline the cloud scenarios applicable to the enterprise, a customized version of the cloud stack reference architecture,
9 the recommended technology platforms at each layer of the stack, integration aspects, security considerations, and management and monitoring approaches. Planning for the Future One of the challenges for cloud adoption is the fact that some of the technologies are not yet mature and there are limited reference architectures and implementations available. The industry is very fragmented with a large number of new vendors. Standards in cloud computing are in the process of getting defined. One way to deal with all this uncertainty would be to leverage the principles, learning and best practices from the world of Service Oriented Architecture (SOA) for Enterprise Cloud Architecture as well. For example, principles of SOA governance (e.g. registries, repositories, policy management) could be used as a base for coming up with cloud governance approaches as well. Regarding cloud security - apprehensions on cloud security should by no means be allowed to become an inhibitor for cloud adoption. One way to address cloud security concerns is to separate out the public and private cloud security requirements. Security aspects for each scenario can then be addressed separately. In a private cloud scenario, the aim should be to replicate, as far as possible, the security policies currently in place. Of course, there could possibly be some refinements and additions for the private cloud context; such as hypervisor security. In a public cloud scenario, it is important to assess and evaluate cloud policies of the provider, and check whether those are acceptable from the organization perspective. Step 5: Cloud Capacity Planning The traditional approach to capacity planning has some fundamental limitations, as outlined below. 1. Underutilization: Capacity is usually planned for a peak load expectation. However, during the large majority of the time when the load is below the peak, the capacity lies underutilized. 2. High upfront costs: Secondly, capacity is expensive and involves high upfront capital expenditure, along with significant time and effort for acquisition and provisioning. In addition, shrinking or de-provisioning of capacity is very difficult. 3. Minimal margin of error: As a logical conclusion, any planning errors can have a huge impact due to which the capacity planning exercise is usually very elaborate and time-consuming. The promise of cloud computing is the potential to address all of the above limitations. Cloud computing can dramatically increase capacity utilization percentages. In fact, if servers were not underutilized, one basic pillar of the cloud business case would have fallen apart. In the cloud, capacity is less expensive and does not involve an upfront capital investment. The time for acquisition and provisioning is measured in minutes rather than days or weeks. Planning errors can be rectified easily due to the concept of elasticity the ability of the cloud to increase or shrink capacity on demand.
10 Key Considerations Cloud adoption implies a paradigm shift for capacity planning related activities from a dedicated resources and peak load model to a shared resources and average load model. One other important aspect is that the focus for cloud capacity planning should be across the layers of the enterprise cloud architecture and not just at the infrastructure level. Some of the considerations would be as outlined below: 1. IaaS Layer: Key aspects of capacity planning will involve determining the number of virtual machines that can be accommodated on given physical hardware depending on the CPU, RAM, and storage capacities needed for each virtual machine (and also keeping in mind hypervisor capabilities). 2. PaaS layer: Key considerations on capacity planning include determining the number of applications that are likely to be developed and hosted on the platform that needs to be made available as a service. 3. SaaS and BPaaS layers: Key considerations would include the number of users for each application or process, peak hours of usage, and so on. One point to be noted is that capacity planning in the cloud is typically needed in the private cloud scenario, or when the enterprise is planning to be a provider of public cloud services. Output The output from this step is a Capacity Plan document, which outlines the capacity required [for example, number of virtual machines] to support the typical transaction volumes expected, interfaces that need to be built, management and monitoring requirements and security aspects. Planning for the Future With cloud adoption, the future of capacity planning looks much better than the past. One change in approach would be the consideration that traditional capacity planning is usually restricted to the infrastructure layer only. In the cloud scenario, besides the focus on the IaaS layer, it is important to have a holistic approach for capacity planning covering the PaaS, SaaS and BPaaS layers as well. It is also critical to keep in mind and plan for the dynamic allocation and de-allocation aspects. Step 6: Monetization Once cloud services are in place and available, they need to be monetized. The process of monetization of cloud services is often called chargeback. Usage based pricing is one of the fundamental building blocks of the cloud computing paradigm. Therefore approaches towards chargeback and monetization need to be planned and thought through carefully. Key Considerations The plans and strategies for chargeback approaches need to be thought through well before the cloud services go live. One obvious aspect here is to plan for usage metering and billing. There is a pitfall to be avoided though. Current approaches often look at chargeback
11 mechanisms from an individual cloud layer point of view rather than a holistic view. In other words, there could be an approach for chargeback of the IaaS layer, but none (or a completely disjoint one) for chargeback of the PaaS / SaaS layer. Ideally, what you would want is a single unified approach to charge the consumer for the usage of a service in the SaaS layer, which encompasses the implied usage of all the layers underneath. The main recommendation here would be to ensure that the chargeback strategies include a focus across all the 4 layers of the cloud, from infrastructure to applications. Output The output of this phase is a monetization methodology note, which outlines chargeback strategies, pricing models, and approaches to invoice generation from metered usage data. Conclusion While cloud computing becomes increasingly widespread and gains mass acceptance, legacy investments in data centers, software and hardware infrastructure cannot be wished away. Private cloud implementations will become increasingly common to leverage such legacy investments, as well as reap the benefits of cloud adoption. In this paper, we have discussed six key considerations for private cloud adoption. The recommendations and insights provide an overall framework that can assist organizations during the planning and strategy phases of their cloud adoption journey. At Happiest Minds, we can assist you towards leveraging this six step approach for your cloud adoption initiatives. References 1. The case for Energy-Proportional Computing, Luiz André Barroso and Urs Hölzle, VMware white paper: Cloud Computing An evolutionary approach to an IT revolution 3. Eucalyptus home page: 4. Amazon Web Services home page: 5. IBM Cloud Computing home page:
12 To learn more about the Happiest Minds Cloud Computing Offerings, please write to us at About Happiest Minds Happiest Minds is a next-generation IT services company helping clients differentiate and win with a unique blend of innovative solutions and services based on the core technology pillars of cloud computing, social computing, mobility and analytics. We combine an unparalleled experience, comprehensive capabilities in the following industries: Retail, Media, CPG, Manufacturing, Banking and Financial services, Travel and Hospitality and Hi-Tech with pragmatic, forward-thinking advisory capabilities for the world s top businesses, governments and organizations. Founded in 2011, Happiest Minds is privately held with headquarters in Bangalore, India and offices in the USA and UK. Corporate Office Happiest Minds Technologies Pvt. Ltd. Block II, Velankani Tech Park 43 Electronics City Hosur Road, Bangalore , INDIA Phone: Fax: About the author United States 116 Village Boulevard, Suite 200 Princeton, New Jersey, Phone: th Avenue NE #224 Bellevue, WA United Kingdom 200 Brook Drive, Green Park, Reading Berkshire, RG2 6UB Phone: Fax: Shantanu Paknikar is General Manager, Solution Initiatives in the IT Services division of Happiest Minds. His expertise areas include middleware systems, SOA, BPM, enterprise integration, cloud computing, multimedia, and distributed computing systems. He is passionate about innovation, research, and learning. He believes that the IT services industry has turned the corner and needs to focus primarily on customer business problems and holistic, end-to-end IT solutions addressing them rather than products, feature sets, individual technology or expertise based offerings. Footnotes i At the same time, a lot of non-core functions are being consumed from the public cloud. ii References for private cloud adoption can be found all over the net. Some good places to look for include the leading vendor sites such as Microsoft, IBM, VMware and Amazon. iii See reference 1 iv
Streamlining Identity and Access Management through Unified Identity and Access Governance Solutions By Iranna Hurakadli and Achutha Sridhar Happiest Minds, IMSS Practice Many enterprises that have implemented
Unified Cyber Security Monitoring and Management Framework By Vijay Bharti Happiest Minds, Security Services Practice Introduction There are numerous statistics published by security vendors, Government
January 2012 The Rise of the Social Enterprise By Rupa Shankar, Shahnawaz Khan Happiest Minds, Social Computing Practice The Rise of the Social Enterprise Social media is transforming how we connect and
March 2014, HAPPIEST MINDS TECHNOLOGIES Network Packet Monitoring Optimizations in Data Centre Author Dharmraj B Jhatakia 1 Copyright Information This document is an exclusive property of Happiest Minds
November 2013 Identity Relationship Management Identity Relationship Management Identity Relationship Management Kantara Initiative, Believers of the World Unite. The Internet of Things is completely redefining
Adopting ITIL Framework By Vinayak Ghadi Adopting ITIL Framework Contents 1. Who should read this paper?... 3 2. Do we know about ITIL framework?... 3 3. Key Adoption Challenges... 6 4. How do we prepare
January 2012 Effectiveness vs. Efficiency: Embracing the New Customer Experience Paradigm By Shahnawaz Khan, Rupa Shankar Happiest Minds, Social Computing Practice Effectiveness vs. Efficiency: Embracing
May 2012 DESKTOP VIRTUALIZATION Future of Smart Secure Workspaces By Sahana Subramanya Happiest Minds, Workspace and Mobility Practice PURPOSE OF THE DOCUMENT The purpose of this document is to provide
May 2012 The Next Generation Mobile Marketing Ecosystem: Beyond SMS Ads to Customer Insights and Offers A Road Map for Telecom Operators By Rupa Shankar, Shahnawaz Khan Happiest Minds, Social Computing
CHAPTER 8 CLOUD COMPUTING SE 458 SERVICE ORIENTED ARCHITECTURE Assist. Prof. Dr. Volkan TUNALI Faculty of Engineering and Natural Sciences / Maltepe University Topics 2 Cloud Computing Essential Characteristics
A new era for the Life Sciences industry Cloud computing changes the game Michael Whitworth Director, Clinical Data Strategy Accenture Accelerated R&D Services Michael.firstname.lastname@example.org Agenda: Accenture
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2009 Vol. 8, No. 7, November - December 2009 Cloud Architecture Mahesh H. Dodani, IBM, U.S.A.
January 2013 The Next Generation Learning Management System By Rupa Shankar, Nihar Routray Happiest Minds, Social Computing Practice Copyright Information This document is the exclusive property of Happiest
August 2014 Cloud Computing Sourcing Key Takeaways Market Penetration As of mid-2014, 87% of tech executives reported utilizing outsourced computing power for at least one task. Market Growth The service
Realizing the Value Proposition of Cloud Computing CIO s Enterprise IT Strategy for Cloud Jitendra Pal Thethi Abstract Cloud Computing is a model for provisioning and consuming IT capabilities on a need
View Point Lifting the Fog on Cloud There s a massive Cloud build-up on the horizon and the forecast promises a rain of benefits for the enterprise. Cloud is no more a buzzword. The enabling power of the
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2009 Vol. 8, No. 5, July-August 2009 The Five-Step Program To Cloud! Mahesh H. Dodani, IBM,
Cloud Computing: Elastic, Scalable, On-Demand IT Services for Everyone Cloud.com White Paper April 2010 Table of Contents 1 Executive Summary... 2 2 Motivation Around Cloud Computing... 2 3 Comparing Cloud
INTRODUCTION TO CLOUD COMPUTING CEN483 PARALLEL AND DISTRIBUTED SYSTEMS CLOUD COMPUTING Cloud computing is a model for enabling convenient, ondemand network access to a shared pool of configurable computing
Financial Services the way we see it Cloud Computing in Banking What banks need to know when considering a move to the cloud Contents 1 Overview 3 2 Why Cloud Computing for Banks? 4 2.1 Cost Savings and
Achieving Retail Agility Is Cloud Computing the Answer? By Bharat Popat and Jon Stine Cisco Internet Business Solutions Group (IBSG) Cisco IBSG 2012 Cisco and/or its affiliates. All rights reserved. It
IT Services Capita Private Cloud Cloud potential unleashed Cloud computing at its best Cloud is fast becoming an integral part of every IT strategy. It reduces cost and complexity, whilst bringing freedom,
IBM Academy of Technology Thought Leadership White Paper October 2010 Cloud computing insights from 110 implementation projects IBM Academy of Technology Survey 2 Cloud computing insights from 110 implementation
Ensuring High Service Levels for Public Cloud Deployments Keys to Effective Service Management Table of Contents Executive Summary... 3 Introduction: Cloud Deployment Models... 3 Private Clouds...3 Public
1 Introduction to Cloud Computing CERTIFICATION OBJECTIVES 1.01 Cloud Computing: Common Terms and Definitions 1.02 Cloud Computing and Virtualization 1.03 Early Examples of Cloud Computing 1.04 Cloud Computing
Cloud A view on why it s still overcast in CIOs minds By Sumeet Mehra Happiest Minds, Cloud Computing Practice 21 st July, 2013 CLOUD The Reality of present world! Many organizations want to adopt Software
IT Enterprise Services Capita Private Cloud Agile Infrastructure-as-a-Service (IaaS) Cloud potential unleashed Cloud computing at its best Cloud is now an integral part of every IT strategy. It reduces
IT Monitoring for the Hybrid Enterprise With a Look at ScienceLogic Perspective 2012 Neovise, LLC. All Rights Reserved. Report Published April, 2015 Hybrid IT Goes Mainstream Enterprises everywhere are
Courses Description 101: Fundamental Computing and Architecture Computing Concepts and Models. Data center architecture. Fundamental Architecture. Virtualization Basics. platforms: IaaS, PaaS, SaaS. deployment
Infrastructure as a Service: Accelerating Time to Profitable New Revenue Streams Cisco Infrastructure as a Service Cisco has made a significant investment in understanding customer needs around data center
Cloud Computing Key Considerations for Adoption Ramkumar Dargha Abstract Cloud Computing technology and services have been witnessing quite a lot of attention for the past couple of years now. We believe
Accenture Cloud Platform Unlocks Agility and Control 2 Accenture Cloud Platform Unlocks Agility and Control The Accenture Cloud Platform is at the heart of today s leading-edge, enterprise cloud solutions.
Research Publication Date: 23 November 2010 ID Number: G00209000 Private Cloud Computing: An Essential Overview Thomas J. Bittman Private cloud computing requires strong leadership and a strategic plan
White Paper: Private Clouds The ongoing debate on the differences between a Public and Private Cloud are broad and often loud. The bottom line is that it s really about how the resource, or computing power,
Managing the Real Cost of On-Demand Enterprise Cloud Services with Chargeback Models A Guide to Cloud Computing Costs, Server Costs, Pricing Plans, and Chargeback Implementation and Systems Introduction
Architectural Implications of Cloud Computing Grace Lewis Research, Technology and Systems Solutions (RTSS) Program Lewis is a senior member of the technical staff at the SEI in the Research, Technology,
Web Application Hosting Cloud Solution Architecture http://www.cloud-council.org/web-app-hosting-wp/index.htm February, 2015 Presenters Heather Kreger CTO International Standards, IBM US email@example.com
Your Platform of Choice The Cloud is Not Enough Why Hybrid Infrastructure is Shaping the Future of Cloud Computing Mark Cravotta EVP Sales and Service SingleHop LLC Talk About Confusing? Where do I start?
Transformational Benefits of the Cloud Information & Communication technology October 2013 Fifth Generation of Computing Cloud Mainframe 1970s Client Server 1980s Web 1990s 80% SOA 2000s 2010+ of new commercial
WHITE PAPER: Easing the Way to the Cloud: 1 WHITE PAPER Easing the Way to the Cloud: The Value of Using a Reference Architecture in Private Cloud Deployments for Microsoft Applications and Server Platforms
Evolution of the Defined Data Center Happiest People Happiest Customers Contents Abstract...3 The big promise of SDDC...3 Moving towards SDDC the adoption roadmap...4 Points to keep in mind...5 Challenges...5
Customer Needs and Strategies IT as a Service Emerges as a New Management Paradigm in the Software-Defined Datacenter Era Mary Johnston Turner IDC OPINION IT as a service (ITaaS) represents a fundamentally
Overview The purpose of this paper is to introduce the reader to the basics of cloud computing or the cloud with the aim of introducing the following aspects: Characteristics and usage of the cloud Realities
The Benefits of Cloud Computing to the E-Commerce Industry July 2011 A whitepaper on how hosting on a cloud platform can lower costs, improve productivity and stability and remove issues around scalability.
White Paper Elastic Private Clouds Agile, Efficient and Under Your Control 1 Introduction Most businesses want to spend less time and money building and managing IT infrastructure to focus resources on
GET CLOUD EMPOWERED. SEE HOW THE CLOUD CAN TRANSFORM YOUR BUSINESS. Cloud computing is as much a paradigm shift in data center and IT management as it is a culmination of IT s capacity to drive business
www.wipro.com CLOUD OPERATIONS CENTER TRANSFORMING TO A SEAMLESS HYBRID CLOUD EXPERIENCE DO BUSINESS BETTER Whether you use traditional data centers, virtualized environments, on/off-prem private clouds,
T EC H N O LO G Y B U S I N ES S R ES EAR C H, I N C. IBM Cloud Services Balancing compute options: How IBM Smart Business Cloud can be a catalyst for IT transformation Author: Stuart Williams Director,
Bringing the Cloud into Focus A Whitepaper by CMIT Solutions and Cadence Management Advisors Table Of Contents Introduction: What is The Cloud?.............................. 1 The Cloud Benefits.......................................
Securing the Cloud with IBM Security Systems 1 2012 2012 IBM IBM Corporation Corporation IBM Point of View: Cloud can be made secure for business As with most new technology paradigms, security concerns
Why Redknee s Pre-Integrated Real-Time Billing and Customer Care Solution is the Right Choice for CSPs > > Summary In an increasingly saturated and competitive market, telecom operators face huge challenges
Optimizing Environments for Desktop Virtualization This paper is designed for enterprise organizations evaluating or deploying application and desktop virtualization technologies Contents page Executive
TecTakes Value Insight How to Turn the Promise of the Cloud into an Operational Reality By David Talbott The Lure of the Cloud In recent years, there has been a great deal of discussion about cloud computing
Journey to Cloud 9 Navigating a path to secure cloud computing Alastair Broom Solutions Director, Integralis March 2012 Navigating a path to secure cloud computing 2 Living on Cloud 9 Cloud computing represents
Charting the Journey into the Cloud An Info-Tech Indaba White Paper Prepared for OnX by Info-Tech Research Group, Indaba Division Sponsored by Cisco, EMC, and VMware 2 Introduction Page 3 Cloud Overview
www.cloudtp.com Building Blocks of the Private Cloud Private clouds are exactly what they sound like. Your own instance of SaaS, PaaS, or IaaS that exists in your own data center, all tucked away, protected
WHITE PAPER Elastic Cloud Infrastructure: Agile, Efficient and Under Your Control - 1 - INTRODUCTION Most businesses want to spend less time and money building and managing infrastructure to focus resources
SERVICES SOLUTION SUMMARY SEIZE THE ADVANTAGE From the workplace to the datacenter, the enterprise cloud footprint is growing. It delivers on-demand development resources. It accommodates new digital workloads.
VIEW POINT Getting cloud management and sustenance right! It is not about cloud, it s about tomorrow s enterprise Soma Sekhar Pamidi, Vinay Srivastava, Mayur Chakravarty The dynamic technologies of cloud
> Solution Overview COGNIZANT CLOUD STEPS TRANSFORMATION FRAMEWORK A comprehensive, tool-based framework speeds up the time to value for your cloud-enabled business transformation projects. It s accepted:
An Oracle White Paper in Enterprise Architecture August 2009 Architectural Strategies for Cloud Computing Disclaimer The following is intended to outline our general product direction. It is intended for
6 Cloud strategy formation 6.1 Towards cloud solutions Based on the comprehensive set of information, collected and analysed during the strategic analysis process, the next step in cloud strategy formation
Seven Requirements for Hybrid Web Delivery Getting the best of both on-premises and SaaS Traditionally, IT risk management has balanced security investment and the impact of the threat, allowing each business
A Custom Technology Adoption Profile Commissioned By HP Private Or Public Cloud Isn t The Right Question It s Going To Be A Hybrid World April 2012 Setting The Stage: IT Must Get In Front Of Enterprise
IT AS A SERVICE BROKER MIT Sloan CIO Symposium May 21, 2014 Thomas P. Roloff Senior Vice President EMC Global Services twitter: @TRoloff 1 Why Transformation? Business is Changing Faster Than IT Business
HRG Insight: Cloud Computing Keeping apprised of terminology in today s constantly changing IT landscape can be a fulltime job for IT decisionmakers. Some terms lend themselves to a fairly educated guess
Chapter 1 Cloud Computing Defined In This Chapter Examining the reasons for cloud Understanding cloud types Defining the elements of cloud computing Comparing private and public clouds In a dynamic economic
Architecting the Cloud Sumanth Tarigopula Director, India Center, Best Shore Applications Services 2011Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without
Improving the Microsoft enterprise cloud network for public cloud connectivity Page 1 Improving network performance between Microsoft and the public Situation As Microsoft IT located more of its line-ofbusiness
Cloud Computing: The Next Computing Paradigm Ronnie D. Caytiles 1, Sunguk Lee and Byungjoo Park 1 * 1 Department of Multimedia Engineering, Hannam University 133 Ojeongdong, Daeduk-gu, Daejeon, Korea firstname.lastname@example.org,
Understanding the Value of Financial Intelligence for Cloud Management A white paper by David Linthicum Hybrid IT Computing 2 Executive Summary Most of those who fund and operate cloud-based or virtualized
Infrastructure Virtualization for Hybrid Cloud Technology Transformation Public cloud has delivered elastic computing to enterprises by offering on-demand resources to accommodate the burst computing needs.
Cloud computing for enterprises Best Practices Overview: For several years, software architects have discovered and implemented several concepts and best practices to build highly scalable applications.
Cloud Computing: It s In Your Future What You Need to Know about Logicalis and Cloud Computing Cloud computing is a transition that is changing the way you will buy, build, operate and consume information,
Hexaware E-book on Q & A for Cloud BI Hexaware Business Intelligence & Analytics Actionable Intelligence Enabled HEXAWARE Q & A E-BOOK ON CLOUD BI Layers Applications Databases Security IaaS Self-managed
Transformation to a ITaaS Model & the Cloud CIO Summit - Miami November, 2014 John Cullen Laddie Suk EMC Global Professional Services John.email@example.com Laddie.firstname.lastname@example.org 1 Agenda Business Challenges
Cloud computing and SAP Next Generation SAP Technologies Volume 1 of 2010 Table of contents Document history 1 Overview 2 SAP Landscape challenges 3 Infrastructure as a Service (IaaS) 4 Public, Private,
Private & Hybrid Cloud: Risk, Security and Audit Scott Lowry, Hassan Javed VMware, Inc. March 2012 Private and Hybrid Cloud - Risk, Security and Audit Objectives: Explain the technology and benefits behind
Planning the Migration of Enterprise Applications to the Cloud A Guide to Your Migration Options: Private and Public Clouds, Application Evaluation Criteria, and Application Migration Best Practices Introduction