Welcome!

Cloud Expo Authors: Pat Romanski, Amy Lindberg, Carmen Gonzalez, Greg Schulz, Lori MacVittie

Related Topics: Cloud Expo, Virtualization

Cloud Expo: Article

Cloud Computing: A Transition Methodology

Roadmap to the Cloud

Cloud computing refers to the practice of leveraging third-party computing resources, such as network grids and server farms, to extend IT capabilities and reduce the cost of ownership. This practice offers numerous potential benefits to organizations that want to centralize software and data storage management while eliminating the costly overhead of in-house hardware and software maintenance and the personnel required to build, support, and maintain enterprise computing solutions.

Cloud computing has emerged as a new computing paradigm that gathers massive numbers of computers in centralized data centers to deliver Web-based applications, application platforms, and services via a utility model. The primary difference between the service models of cloud computing and previous software (e.g., outsourcing or data center consolidation) is scale. The premise is that as the scale of the cloud infrastructure increases, the incremental time and cost of application delivery trends toward zero.

Cloud computing allows users to dynamically and remotely control processing, memory, data storage, network bandwidth, and specialized business services from pools of resources, providing the ability to specify and deploy computing capacity on-demand. If there's a need to scale up to accommodate sudden demand, users can add the necessary resources using a Web browser. The large data center can provide similar services to multiple external customers (multi-tenancy), leveraging its shared resources to increase economies of scale and reducing service costs.

Although cloud computing is in its early stages and definitions vary greatly, the underlying technologies today are consistent. These technologies include the following:

  • Grid computing: A form of distributed parallel computing whereby processes are split up to leverage the available computing power of multiple CPUs acting in concert.
  • Utility computing: A model of purchasing computing capacity, such as CPU, storage, and bandwidth, from an IT service provider, billed based on consumption.
  • Virtualization technologies: Virtual servers and virtual private networks provide the ability to quickly reconfigure available resources on-demand and provide the necessary security assurance.

There are a number of service offerings and implementation models under the cloud computing umbrella, each with associated pros and cons. These models can be grouped into the following three categories: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS). These models target varying levels of services, ranging from general infrastructure services, such as operating systems or database services provided by IaaS vendors to targeted functional services provided by SaaS vendors (e.g., customer relationship management from Salesforce.com).

The various players in the current market can be differentiated into the following two categories:

  • Cloud Providers: Offer one or more of the cloud models (i.e., IaaS, PaaS, or SaaS) as a service. Examples include Amazon and Google.
  • Cloud Enablers: Provide technology or have adapted existing technology to run on or support cloud computing. A recent example is Oracle's partnership with Amazon to add Oracle 11g database support (technology and licensing) to Amazon's existing EC2 services offering.

We recognize that the transition to a cloud computing paradigm presents a number of challenges. Issues associated with information security, reliability, and service level agreements challenge mission-critical systems. Furthermore, we've identified what we consider the key characteristics of a cloud computing environment:

  • Minimized capital expenditure - infrastructure is provider-owned
  • Device and location independence
  • Multi-tenancy - enables resource and cost sharing among a large pool of users
  • Monitored and consistent performance - can be affected by high network load
  • Reliability via redundant sites - allows for business continuity and disaster recovery
  • Scalability to ever-changing user demands - results in lower costs
  • Improved security from centralized data and increased security-focused resources

My experience has emphasized the importance of "architecting for the cloud" versus simply deploying system components to the cloud to ensure that business requirements are met. Typical software and systems that are not designed to take advantage of the scalability and parallelism of the cloud will likely not achieve the full benefit that is provided by a cloud computing environment. It's also highlighted the need to transition the role of IT managers to brokers and negotiators of IT services rather than the day-to-day management of the operating platform.

My analysis of the benefits and challenges presented by the cloud computing paradigm has resulted in the identification of the following three cloud variations:

  • Commercial Cloud: It consists of deployment to one or more of the commercial cloud providers (e.g., Amazon or Google). It could be a simple integration with an existing SaaS service to support a subset of application functionality or could consist of a complete migration to the cloud. This may be appropriate for non-mission critical systems (e.g., < 99.99% availability) that do not process sensitive data or where sensitive data won't traverse system boundaries to the cloud.
  • On-Premises (Private) Cloud: An on-premises cloud could be created to provide some of the benefits of cloud computing. Booz Allen selected a similar option in our implementation for the FBI to address the security concerns associated with a classified environment; however, the multi-tenancy aspect is then limited to a single agency. Consequently, this option doesn't provide the massive scalability that's characteristic of a true cloud.
  • Government Cloud: The creation of one or more government cloud computing environments. These environments would be designed specifically to address the concerns that are unique to the government. For civilian agencies, this cloud could be an extension of the current eGovernment lines of business (LoBs).

Though many cloud providers proclaim that moving existing applications to the cloud is seamless and doesn't require code changes, my experience has shown that greater analysis and re-engineering are required to achieve the full benefits of a cloud computing environment. Complexities remain that organizations must consider when moving to the cloud, and careful planning is essential.

Based on the lessons learned from previous efforts, a phased Cloud Computing Transition Methodology designed to address the issues and risks associated with migrating an existing system to the cloud is developed. Figure 1 provides an overview of this approach.

The Cloud Strategy and Planning phase (Phase 1) consists of three steps designed to ensure that all aspects of moving to a cloud environment have been appropriately evaluated and agreed upon. The three steps are:

1. Conduct a Strategic Diagnostic
The objective of the strategic diagnostic is to identify the major factors influencing the decision to move to the cloud environment and determine the best approach. During the diagnostic step, we will validate the key objectives of moving to the cloud and the "pain points" that the organization wants to address. The drivers during this step include reducing day-to-day risk, reducing the level of involvement in day-to-day IT management, eliminating overhead, achieving better productivity, reducing or eliminating the cost of adding additional users, and protecting the information system from misuse and unauthorized disclosure.

The primary areas to be addressed during the diagnostic step are security and privacy, technical, business and customer impact, economics, and governance and policy. We will evaluate the implications of moving to the cloud environment in each of these categories and document the key issues and considerations revealed during the diagnostic step. The outcome of this diagnostic will be sufficient analysis to support a "go/no go" decision to move to a cloud computing environment and the development of an agreed-on cloud strategy.

2. Define a Cloud Strategy
To define a cloud strategy, the organization should document a complete understanding of each component of its existing architecture. The analysis examines the required user services, processing services, information security, application software standards, and integrated software down to each component. This can be achieved by leveraging existing architectural documents and ensuring the appropriate level of detail is documented, including system-to-system interfaces, data storage, forms processing and reporting, distributed architecture, access control (authentication and authorization), and security and user provisioning.

3. Create an Implementation Plan
The implementation plan identifies the roles and responsibilities, operating model, major milestones, Work Breakdown Structure (WBS), risk plan, dependencies, and quality control mechanisms to implement the cloud strategy successfully.

After completing Phase 1, the organization will have fully analyzed its options, identified all requirements, thoroughly assessed short-term and long-term costs and benefits, gained executive governance approval, and socialized the solution with stakeholders (including oversight entities). This phase ensures that the organization will have a high degree of confidence in successfully moving to the cloud environment, reap the expected benefits, not constrain future functionality, and avoid hidden future costs.

The Cloud Deployment phase (Phase 2) focuses on implementing the strategy developed in the planning phase. Leveraging the various cloud models helps identify the most effective solution(s) based on the existing organization architecture. Some of the criteria used in recommending a vendor are the vendor's primary service model (i.e., infrastructure, platform, or software), business model, how much existing technology can they leverage, end-user experience, and risks involved in porting to the cloud. Deploying to the cloud involves taking the decision analysis from Phase 1 as input and proceeding with the following four steps:

1.  Assess/Select the Cloud Provider(s)
The assessment step deals with analyzing the components of the architecture and identifying the optimal vendor offerings. One of the main criteria in selecting a provider is its ability to leverage existing technologies. For example, current Oracle customers can use their software licenses on Amazon's EC2 cloud, which allows for reusing existing technologies, whereas current databases can simply be moved to the cloud. In addition, Oracle lets customers deploy on the Amazon cloud through Amazon Machine Images (AMI). This way, a new virtual machine is ready for use with the Oracle database loaded in a matter of minutes.

The assessment step captures three important inputs: the current organization technical architecture, objectives, and the vendor selection criteria that are tailored to meet the organizational objectives. The vendor assessment results in recommendations on the most appropriate cloud vendor, assists in selecting the most effective cloud model, develops deployment strategies, highlights reusable components, and identifies the security options for the cloud architecture.

2. Establish Service Level Agreements (SLAs)
Unlike traditional computing models, where most, if not all, of the components are on-premises and there's direct control over services, cloud computing involves handing off the system to a third-party vendor or vendors. In this case, SLAs address concerns like performance, downtime, provisioning, security, backup, and recovery, and ensure that objectives and established benchmarks are being met. SLAs formalize the contractual agreement between the organization and the selected vendor(s) and will highlight the offerings of the vendor(s), so the expectations on both sides are clear.

A typical SLA will identify service levels for the following:

  • Retention Time: During an emergency/outage, how long would it take for the organization to sustain its operations
  • Uptime: The percent of the time that the system will be available (e.g., 99.9%) and the period over which the measurement is taken
  • Performance and throughput
  • Security and Data protection: Where is the data stored? What precautions are taken by the vendor to ensure the data isn't tampered with?
  • The level of support offered (e.g., 24/7)
  • Service credits if the SLA isn't met
  • The SLA can also address specific concerns like the guarantee of data protection and privacy when other foreign entities are hosted

3. Execute Transition
The execution step involves the actual transition of components identified in earlier steps. Based on the number and type of components that are being ported to the cloud, execution can be an iterative process. One of the primary steps in execution is to establish multiple environments, such as development, testing, production, and training. The preliminary questionnaire to set up an environment can include items like the number of instances required, memory, storage space, and basic software that needs to be installed.

4. O&M and Help Desk
The level of O&M and help desk provided by the cloud vendor may be driven by the selected cloud model(s) and will be determined by the SLAs previously established. If an IaaS is chosen where the vendor just provides the hardware resources and the organization installs the software components and deploys the applications, the maintenance provided by the vendor will be limited. Different vendors provide different support models and at different levels. It's important to ensure the kind of essential support functions that will be provided by vendors for successful continuity of operations (COOP) and to understand how operations will be restored on time at the backup site.

Deploying cloud computing solutions requires both a short-term and a long-term strategy. For example, besides the improved scalability and reliability provided by the cloud, which organizations may achieve through the initial transition, re-engineering some components to take advantage of the parallelism provided by the cloud could improve system performance and overall scalability further. Transitioning an existing system to the cloud requires an approach that addresses not only the technical aspects of cloud computing but also considers the objectives of the organization, the constraints imposed by the existing system, and the impact to its existing customers. As an experienced cloud computing strategist, I believe that corporations and even the government sector are prepared to consider the complexities of cloud computing technologies.

More Stories By Rod Fontecilla

Dr. Rod Fontecilla is a Principal at Booz Allen Hamilton. He has over 25 years of professional experience in the design, development, implementation, and management of Large Information Management Systems. He is an expert in the field of Computer Science within the federal government and private sectors. Dr. Fontecilla has Ph.D. in Applied Mathematics and previously served as a Professor at the University of Maryland Computer Science Department before entering the consulting industry.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@CloudExpo Stories
SYS-CON Events announced today that Gridstore™, the leader in hyper-converged infrastructure purpose-built to optimize Microsoft workloads, will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Gridstore™ is the leader in hyper-converged infrastructure purpose-built for Microsoft workloads and designed to accelerate applications in virtualized environments. Gridstore’s hyper-converged infrastructure is the ...
DevOps Summit 2015 New York, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete...
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective ...
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using ...
"SAP had made a big transition into the cloud as we believe it has significant value for our customers, drives innovation and is easy to consume. When you look at the SAP portfolio, SAP HANA is the underlying platform and it powers all of our platforms and all of our analytics," explained Thorsten Leiduck, VP ISVs & Digital Commerce at SAP, in this SYS-CON.tv interview at 15th Cloud Expo, held Nov 4-6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
SAP is delivering break-through innovation combined with fantastic user experience powered by the market-leading in-memory technology, SAP HANA. In his General Session at 15th Cloud Expo, Thorsten Leiduck, VP ISVs & Digital Commerce, SAP, discussed how SAP and partners provide cloud and hybrid cloud solutions as well as real-time Big Data offerings that help companies of all sizes and industries run better. SAP launched an application challenge to award the most innovative SAP HANA and SAP HANA...
There's Big Data, then there's really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at Big Data Expo®, Hannah Smalltree, Director at Treasure Data, discussed how IoT, Big D...
DevOps Summit 2015 New York, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Ar...
The term culture has had a polarizing effect among DevOps supporters. Some propose that culture change is critical for success with DevOps, but are remiss to define culture. Some talk about a DevOps culture but then reference activities that could lead to culture change and there are those that talk about culture change as a set of behaviors that need to be adopted by those in IT. There is no question that businesses successful in adopting a DevOps mindset have seen departmental culture change, ...
SYS-CON Media announced today that Skytap blog on "DevOps Journal" exceeded 84,000 story reads. DevOps Journal is focused on this critical enterprise IT topic in the world of cloud computing. DevOps Journal brings valuable information to DevOps professionals who are transforming the way enterprise IT is done. Noel Wurst is the managing content editor at Skytap. Skytap provides SaaS-based dev/test environments to the enterprise. Skytap solution removes the inefficiencies and constraints that comp...
The 4th International DevOps Summit, co-located with16th International Cloud Expo – being held June 9-11, 2015, at the Javits Center in New York City, NY – announces that its Call for Papers is now open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's large...
SYS-CON Events announced today Isomorphic Software, the global leader in high-end, web-based business applications, will exhibit at SYS-CON's DevOps Summit 2015 New York, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Isomorphic Software is the global leader in high-end, web-based business applications. We develop, market, and support the SmartClient & Smart GWT HTML5/Ajax platform, combining the productivity and performance of traditional desktop software ...
The security devil is always in the details of the attack: the ones you've endured, the ones you prepare yourself to fend off, and the ones that, you fear, will catch you completely unaware and defenseless. The Internet of Things (IoT) is nothing if not an endless proliferation of details. It's the vision of a world in which continuous Internet connectivity and addressability is embedded into a growing range of human artifacts, into the natural world, and even into our smartphones, appliances, a...
Fundamentally, SDN is still mostly about network plumbing. While plumbing may be useful to tinker with, what you can do with your plumbing is far more intriguing. A rigid interpretation of SDN confines it to Layers 2 and 3, and that's reasonable. But SDN opens opportunities for novel constructions in Layers 4 to 7 that solve real operational problems in data centers. "Data center," in fact, might become anachronistic - data is everywhere, constantly on the move, seemingly always overflowing. Net...
"ElasticBox is an enterprise company that makes it very easy for developers and IT ops to collaborate to develop, build and deploy applications on any cloud - private, public or hybrid," stated Monish Sharma, VP of Customer Success at ElasticBox, in this SYS-CON.tv interview at DevOps Summit, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happe...
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges. In his session at @ThingsExpo, Jeff Kaplan, Managing Director of THINKstrateg...
The Internet of Things promises to transform businesses (and lives), but navigating the business and technical path to success can be difficult to understand. In his session at @ThingsExpo, Sean Lorenz, Technical Product Manager for Xively at LogMeIn, demonstrated how to approach creating broadly successful connected customer solutions using real world business transformation studies including New England BioLabs and more.