10 Reasons why Telcos will Dominate Enterprise Cloud Computing?
The entire article comes from
http://www.on-demandenterprise.com/…Telcos_Will_Dominate_Enterprise_Cloud_Computing
I’m capturing some key bullets from it with my personal highlight in bold and italic… It’s worth to take time to read this through.
A cloud definition:
it will be helpful to define what a cloud service is. I define it as a CLOUD: Common, Location-independent, Online Utility provisioned on-Demand. Common (i.e., shared) in that it multiplexes demand from multiple customers and applications into a common pool of resources. Location-independent, because it shouldn’t matter where you are or where the service is. Online, in the sense that it is accessible over a network, as well as “not down.” A utility because it provides value and offers usage-sensitive pricing. And on-demand in that the ability to provision capacity or service should be as fast as possible to meet variable demand requirements, enhancing business agility and providing capacity at the lowest total cost.
Under this definition, not only can computing be cloud-based, but so can be storage, security, audio conferencing, video conferencing, Web conferencing, messaging, collaboration, software as a service and so forth. In fact, cloud services have been around since well before today’s latest networked IT architectures and business models. Hotel chains are cloud services: they time- and space-division multiplex guests traveling as individuals and in groups, on vacation or business, into dynamically allocated units of capacity (rooms). They are location-independent, in that no matter what city you are in, you are likely to find a service node (a local hotel from the chain). They are online, accessible over wide-area highways and local-area hallways. They also are utilities (pay per room per night). And they are available on-demand (although reservations are recommended during peak season).
…
In fact, such providers have 10 major strategic advantages in this market:
- Enterprise sales capability — Telcos have a long history of selling to enterprises as well as consumers. For example, AT&T had annual revenues of $119 billion in 2007 — more than either IBM or HP — and roughly half of those revenues come from businesses. Unlike their consumer or start-up counterparts, enterprise CIOs do not want to go online to initiate and manage a relationship. They want dedicated account teams collaborating closely with them and their teams for the long term, in many cases with a permanent on-site presence. Some might argue that there is a major business model transformation underway. After all, who needs an enterprise sales force when employees can just use their credit card to provision services?
This is unlikely to happen in the enterprise for three reasons. First, most enterprises have tight controls on purchasing that extend to $10 worth of business cards, much less buying online computing and storage capacity. Second, no corporate information security officer is likely to appreciate the idea of tens of thousands of employees purchasing cloud services and placing proprietary corporate data willy-nilly across providers and platforms. Third, enterprise IT shops already have experienced the chaos and hidden costs associated with loss of control of applications, desktop images, and foundation architecture in departmental computing and rich desktop environments, and thus are not likely to support a model of individual purchases of cloud capacity and services. If the enterprise wants to avail itself of the benefits of the cloud, credit card purchasing is not the way to go.
- Lifecycle service and support — It’s not just sales, but also after-sales service and support, including: lifecycle management teams ensuring successful service delivery 24/7; advanced tooling for service monitoring and management; portals for network and application performance, usage monitoring and configuration and provisioning changes; and even e-bonding between enterprise systems and service provider systems.
- Reliable operations at scale — Rather than offering services that still remain in “Preview Release” or permanent “Beta” purgatory after many years to avoid any implied service reliability or feature stability commitments, service providers go through a comprehensive suite of pre-launch interoperability, certification, and scalability engineering and testing. In fact, telcos are used to engineering services for four or five nines of availability, even as they scale up to tens of millions of customers. This reliability at scale is in telcos’ DNA and service culture, as well as in regulatory requirements. Imagine a trauma victim calling 911 and getting a pre-recorded message saying, “Your call did not go through — but, hey, we’re still in beta.” It isn’t clear that a new economy culture of random innovation is compatible with a culture of continuous delivery of the same service to tens of millions of customers day after day.
- SLAs with financial penalties – Not only won’t enterprises accept “Well, after all, it’s still in beta” as an excuse for service outages, they demand meaningful SLAs (service level agreements) with clear metrics for evaluating achievement of those SLAs, backed up by monitoring and management systems, and financial penalties such as credits or refunds if service levels aren’t met. A “free” or low-cost service with questionable delivery quality is about as attractive to a CIO as an offer of free neurosurgery from someone who just skimmed a blog on how to do it in three easy steps.
- Full enterprise solutions portfolio — Cloud computing services don’t exist in a vacuum; many other services may be procured in conjunction with them, either due to technical architecture requirements or due to contracting benefits, such as discounts for total spend. Related services such as network access and transport, MPLS VPNs for backhauling to the enterprise datacenter, application management, global load balancing, asymmetric Web acceleration, network-based firewalls and other network-based security services, content delivery, Voice over IP, Video over IP, managed messaging, Web conferencing and remote access can offer synergies when combined with cloud computing and storage.
- Integrated hosting and network services — This has real benefits in terms of cost and performance. It generates cost advantages in a number of ways. First, having hosting facilities on net — that is, in the same locations as core network backbone switching and routing facilities — eliminates expenses associated with building additional access facilities to reach a third-party datacenter. Integrated providers also can access network facilities at cost, rather than at market prices. And larger providers should be able to achieve more compelling economies of scale. Having hosting facilities on net also means better performance by reducing router hops and associated physical propagation delays.
- Vendor independence — Service providers tend to be software and hardware vendor-agnostic. The reason for this is that their broad customer bases have wide ranges of requirements and preferences, and service providers are strategically intent on reaching as wide a market as possible. Consequently, lock-in to a specific storage, server, operating system, hypervisor, middleware, database or application vendor would be self-defeating by limiting market penetration. This contrasts with some of the existing players, who mostly seem to have at least some proprietary elements to their platforms.
- Global footprint — It’s not news that today’s enterprises have gone global. Whether it’s a global base of employees, customers, supply chain partners, offshore contact centers or skill base for innovation, reach and footprint are critical. Large, integrated global service providers have the capability to provide services locally and consistently virtually anywhere in the world to support today’s increasingly interactive applications with proximate infrastructures that reduce response time — and with the sales and support resources to directly engage with regional or local leadership, or corporate executives headquartered anywhere from Shanghai to Dubai, Bangalore to Brussels, or Sydney to Sao Paulo.
- Financial stability and market commitment — In today’s tumultuous economic environment, enterprises are more focused than ever on the financial stability, brand and business viability of service providers providing key parts of their infrastructures. Commitment to hosting and cloud computing as part of their provider’s core business is important, as opposed to cloud services being a potentially temporary excursion from different core businesses such as online retailing or advertising. Over the last few years, high and rising stock prices have permitted some new economy players substantial flexibility in capital investments, but recent drops of fifty or sixty percent may slow such adventurism for the foreseeable future.
- Technologies are easier to replicate than relationships and operations — Don’t the famously highly paid developers at the new economy companies have an edge in creating new technologies such as automated provisioning that enable cloud services to rapidly scale up and down? If they do — which is arguable — it isn’t sustainable. Such technologies have been around for years from companies as small as BladeLogic and as large as IBM (e.g., Tivoli Provisioning Manager), with variations such as VMware’s vCenter and VMotion fitting into the mix. For every highly paid developer at an online bookseller, there is a highly motivated developer at a start-up or large global software firm, developing software tools for others, like integrated service providers, to incorporate into their tooling and management platforms. Even Animoto, the poster child for non-consumer use of cloud computing services, leveraged a third party, RightScale, to manage dynamic allocation of these services. Service providers also can choose best-in-class capabilities and focus on integration. Much harder to replicate are global networks that have been built for literally hundreds of billions of dollars of investment, and the experienced skill base, long-term enterprise customer relationships, management tools, support organizations, service culture, and local access and regulatory relationships that enable services to be delivered successfully at scale.
A Pragmatic, Incremental Approach to Cloud Computing
Source: http://www.rpath.com/corp/cloud-adoption-model
The cloud computing adoption approach
- Level 1: Virtualization. The first level of cloud adoption employs hypervisor-based infrastructure and application virtualization technologies for seamless portability of applications and shared server infrastructure.
- Level 2: Cloud Experimentation. Virtualization is taken to a cloud model, either internally or externally, based on controlled and bounded deployments utilizing the Amazon Elastic Compute Cloud (EC2) for compute capacity and as the reference architecture.
- Level 3: Cloud Foundations. Governance, controls, procedures, policies, and best practices begin to form around the development and deployment of cloud applications. Initially, level 3 efforts will focus on internal, non-mission critical applications.
- Level 4: Cloud Advancement. Governance foundations allow organizations to scale up the volume of cloud applications through broad-based deployments in the cloud
- Level 5: Cloud Actualization. Dynamic workload balancing across multiple utility clouds. Applications are distributed based on cloud capacity, cost, proximity to user and other criteria.
View a PDF of the basics of the model.
Opening the Cloud
Cloud-computing platforms such as Amazon’s Elastic Compute Cloud (EC2), Microsoft’s Azure Services Platform, and Google App Engine have given many businesses flexible access to computing resources, ushering in an era in which, among other things, startups can operate with much lower infrastructure costs. Instead of having to buy or rent hardware, users can pay for only the processing power that they actually use and are free to use more or less as their needs change.
However, relying on cloud computing comes with drawbacks, including privacy, security, and reliability concerns. So there is now growing interest in open-source cloud-computing tools, for which the source code is freely available. These tools could let companies build and customize their own computing clouds to work alongside more powerful commercial solutions.
One open-source software-infrastructure project, called Eucalyptus, imitates the experience of using EC2 but lets users run programs on their own resources and provides a detailed view of what would otherwise be the black box of cloud-computing services.
Another open-source cloud-computing project is the University of Chicago’s Globus Nimbus, which is widely recognized as having pioneered the field. And a European cloud-computing initiative coordinated by IBM, called RESERVOIR, features several open-source components, including OpenNebula, a tool for managing the virtual machines within a cloud. Even some companies, such as Enomaly and 10gen, are developing open-source cloud-computing tools.
Rich Wolski, a professor in the computer-science department at the University of California, Santa Barbara, who directs the Eucalyptus project, says that his focus is on developing a platform that is easy to use, maintain, and modify. “We actually started from first principles to build something that looks like a cloud,” he says. “As a result, we believe that our thing is more malleable. We can modify it, we can see inside it, we can install it and maintain it in a cloud environment in a more natural way.”
Reuven Cohen, founder and chief technologist of Enomaly, explains that an open-source cloud provides useful flexibility for academics and large companies. For example, he says, a company might want to run most of its computing in a commercial cloud such as that provided by Amazon but use the same software to process sensitive data on its own machines, for added security. Alternatively, a user might want to run software on his or her own resources most of the time, but have the option to expand to a commercial service in times of high demand. In both cases, an open-source cloud-computing interface can offer that flexibility, serving as a complement to the commercial service rather than a replacement.
Indeed, Wolski says that Eucalyptus isn’t meant to be an EC2 killer (for one thing, it’s not designed to scale to the same size). However, he believes that the project can make a productive contribution by offering a simple way to customize programs for use in the cloud. Wolski says that it’s easier to assess a program’s performance when it’s possible to see how it operates both at the interface and from within a cloud.
Wolski says that Eucalyptus will also imitate Amazon’s popular Simple Storage Surface, which allows users to access storage space on demand, as well as its Elastic IP addresses, which keeps the address of Web resources the same, even if the physical location changes.
Ignacio Llorente, a professor in the distributed systems architecture group at the Universidad Complutense de Madrid, in Spain, who works on OpenNebula, says that Eucalyptus’s main advantage is that it uses the popular EC2 interface. However, he adds that “the open-source interface is only one part of the solution. Their back-end [the system's internal management of physical resources and virtual machines] is too basic. A complete cloud solution requires other components.” Llorente says that Eucalyptus is just one example of a growing ecosystem of open-source cloud-computing components.
Wolski expects many of Eucalyptus’s users to be academics interested in studying cloud-computing infrastructure. Although he doubts that such a platform would be used as a distributed system for ordinary computer users, he doesn’t discount the possibility. “You can argue it both ways,” he notes. But Wolski says that he thinks some open-source cloud-computing tool will become important in the future. “If it’s not Eucalyptus, I suspect [it will be] something else,” he says. “There will be an open-source thing that everyone gets excited about and runs in their environment.”
Copyright Technology Review 2008.
What does RackSpace offer?
Part of the following comes from: http://www.comparewebhosts.com/…htm
Rackspace’s cloud strategy is supported by three core offerings, all part of Mosso, Rackspace’s Cloud Hosting Division. The company’s existing Hosting Cloud and CloudFS storage offerings have been re-branded to reflect the company’s newly integrated approach:
· Cloud Sites — Rackspace’s flagship cloud offering, The Hosting Cloud, is now Cloud Sites. Developed by Mosso, Rackspace’s cloud division, it offers a scalable platform for handling huge traffic spikes and a pay-as-you-grow pricing model. Cloud Sites is a heterogeneous environment, supporting both Windows and Linux.
· Cloud Files — Rackspace’s internet-based storage service, CloudFS, is now Cloud Files. Cloud Files gives developers instant access to an enterprise-grade storage infrastructure and reduces overall investment and IT costs while providing infinite scalability. Cloud Files offers an industry leading SLA and a highly competitive pricing model with replicated storage starting at $0.15/GB. Also later this year, Limelight Networks will team with Rackspace to allow developers to easily distribute content to millions of end users around the world and bring scalable content delivery and application acceleration services to the masses. While continuing to support the Amazon S3 platform, Jungle Disk will port to Rackspace’s Cloud Files system in the coming months. Jungle Disk comes in both desktop and workgroup editions across the Windows, Mac and Linux platforms.
· Cloud Servers — This new hosting solution, which will deliver on-demand server capacity to businesses of all sizes, will leverage key technology developed by Slicehost, which uses Xen virtualization software. Slicehost will remain as the company’s developer brand, creating innovative new features driven through shared intellectual property in conjunction with development initiatives from Rackspace. As part of the announcement, Slicehost also announced new, larger slices for high performance computing, lower prices as well as IP sharing for high availability computing.
…
To understand Mosso > http://www.mosso.com
Mosso architectures > http://www.mosso.com/cloud.jsp > look at “Benefit” @ bottom left.
The selling point to our customer >
Step One: Load it up
You can create a new Mosso-powered site – and even add some email accounts – in less than five minutes. Load-Balancing, clustering, and redundant storage are all inherited by your application automatically, without any effort.
Step Two: Watch it scale
From the first byte served, your site is hosted on advanced clustered technology designed for high- traffic, high- performance websites. When your site grows bigger than what it’s included, you pay inexperience scale pricing for exactly what you use and nothing more.
- Scale your bandwidth
- Starts at 500GB/mo. As much as you need for 25¢ per GB
- Scale your SAN storage
- Starts at 50GB/mo. As much as you need for 50¢ per GB
- Scale your compute
- Starts at 10,000 compute cycles/mo. As many as you need for 1¢ per compute cycle
Closer watch with screenshots > http://www.mosso.com/screenshots.jsp > this describes the ease of process when a client requests a host.
=-=-
http://www.slicehost.com is equal to Cloud Servers. This pretty much looks like VPS - virtual private server on Xen.
- Included in Every Slice™
- Full root access and rebooting
- Choice of Linux distro
- Dedicated IP address and Tier-1 redundant bandwidth
- RAID-10 disk storage
- Reserved RAM
- Guaranteed CPU share and more when available
- 4-core servers running Xen virtualization instances
- Slicehost management portal for reboots and software installs
- Mobile management portal for smartphones
- Ajax console access
- Bootable rescue mode
- Private IPs for inter-slice communication
- HA capabilities via shared IPs
- Machines running with fixed usage limits, below full capacity
=-=-
JungleDisk http://www.jungledisk.com/ uses Hadoop with friendly UI to provide backup/ redundancy. For security, all personal data is encrypted by personal key known only to you.
Q&A: Citrix exec says cloud to carry Xen against VMware
Source: http://news.cnet.com/8301-1001_3-10076377-92.html?tag=inside
Author: Peter Judge
Copyright: ZDNet
I’m looking for the comparison between Xen and VMWare. I believe this interview tells some result and I highlight the key points in italic and bold from my understanding.
=-=-=-=-=-=-=-
Citrix aims to beat VMware at virtualization. A year ago it bought XenSource, the company created by the founders of the Xen open-source hypervisor, and switched the Citrix business focus to virtualization.
Ian Pratt, vice president, Citrix
Citrix made XenServer, the commercial system based on Xen, central to its strategy, and applied a Xen brand to other Citrix products involved in delivering applications to desktops. XenSource staff gained senior positions at Citrix and have been setting the company’s future direction.
Ian Pratt, the original project leader of Xen and a founder of XenSource, remains a Fellow of King’s College, Cambridge, but is now also vice president for special products at Citrix–and remains chairman of Xen.org.
ZDNet UK spent a day at Citrix’s U.K. headquarters with Pratt and his colleague, Simon Crosby, who has moved from chief technology officer of XenSource to become chief technology officer of Citrix. After lengthy briefings on Citrix products and the future of virtualization, we sat down with Pratt to understand where Citrix is going and why.
In the first of what will be a two-part interview, Pratt discusses how Citrix hopes to make headway in the virtualization market.
At the moment there is a lot of publicity for VMware and Microsoft Hyper-V. Is there a danger XenWare will be overlooked–especially as it is difficult to measure market share in virtualization? Could XenWare become the Liberal Democrats of virtualization?
Pratt: In the market, there is obviously a big incumbent player, VMware, and Microsoft has a very basic product that covers the low end. And then there is XenServer, which is going head to head with VMware, with an enterprise feature set.
If you look toward the cloud, all the cloud vendors use Xen. It gets used in all the largest deployments, by folks like Amazon and other large providers, because of all the features it offers.
It is very hard to judge what the market share is. With VMware, you just look at VMware’s bank account.
But if you are looking at market share for Xen in general, you’ve got XenServer, Virtual Iron, XenApps, and products from other companies. And then there are all the Linux distributions that include Xen, most of which are free, and no one really has any idea of how many copies are in use.
Even with something like XenServer, because there’s a free version, we keep stumbling into customers–particularly people doing software as a service, where it all runs on XenServer Express Edition (the free unsupported version of XenServer).
They haven’t paid us any money as yet and they have thousands of servers running it. But we’d much rather they were running our stuff than VMware, because it’s an opportunity for us.
With the Cloud Edition we recently announced, there will be lots of people wanting to pay for support and get features added.
If cloud providers are mostly on the free XenServer, is this the whole reason for the Cloud Edition–to turn them into “real” customers and start getting some money in?
Pratt: Simon Crosby has this analogy, that Xen is an engine and needs a car built around it. (The point of the analogy is that the Xen hypervisor is open-source, with a GPL license, so users can make additional technology outside that hypervisor and keep it proprietary, building commercial products that work with Xen.)
If you are a cloud provider or a big software-as-a-service (SaaS) vendor, you can download the open-source engine and build your own car around it. That’s fine if you have the engineering resource to do that, but a lot of this stuff is going to become more commoditized. SaaS vendors don’t all have very particular needs. They don’t have to do this for themselves–they have just had to do it that way until now.
Cloud Edition gives them a standard framework, so they can just concentrate on the value-added bits that they are interested in.
So it’s just like many software developments in the past, where it’s become obvious that everyone is doing the same thing, and a supported version of that is produced?
Pratt: Yes. And they just switch over to the supported version.
So VMware is the big competitor, then. What is the state of things between you and VMware at the moment?
Pratt: VMware has been really successful as a virtualization vendor. But virtualization as a category will disappear. The basic use of virtualization–server consolidation–is now a commodity.
Virtualization will be included in every operating system and on every server. XenSource Express is built into every HP and Dell server, on a USB stick soldered into the box. Users can run multiple virtual machines on those machines out of the box.
This is the only thing VMware does, and it has 100,000 customers. VMware is preparing for this to happen, by building management tools. But this puts them in direct competition with huge established players, like Tivoli and HP OpenView.
Citrix’s approach is to concentrate on application delivery. The function of an IT department is to deliver applications, and we are doing it end to end, from the data center to the client device.
We don’t need to do systems management, and we don’t need to compete head on. It is all about application delivery. People won’t buy virtualization–but they will buy high availability and fault tolerance.
Citrix has 200,000 customers. That’s a pretty good beachhead to deliver more Citrix stuff to customers.
What is distinctively better about Xen’s approach compared with VMware’s?
Pratt: We don’t want to create a class of people called virtualization administrators who you need to manage your virtual machines. That’s how VMware works.
VMware is operating system virtualization–or hardware virtualization. That puts a lot of effort into a problem that is no longer there (since modern hardware from Intel and AMD has evolved to support virtualization).
What we did was to start out with the idea that hardware should support virtualization and the virtual machine should be aware. We call that para-virtualization, and Microsoft calls it enlightenment. That’s marketing.
If you employ virtualization to get a separation not just in the hardware layer, then you can compose things dynamically. That’s the way to bring down the real cost of IT.
We want to be as much of an appliance as possible. We’ve always seen Xen as an appliance that hosts virtual appliances. You want it to be an appliance and manage it like an appliance. It’s like a Netgear router–you just plug it in and go. Adding a new machine to a XenServer pool should be as easy as that.
It is also quite hard to establish the relative performance of VMware’s hypervisor and XenServer because of VMware’s licensing terms. Are you working on a way round that problem?
Pratt: The VMware EULA (end-user licensing agreement) prohibits the publication of any benchmark results to a third party. We tried to publish results in 2002, and that clause has been in the VMware EULA ever since.
As XenSource, we might have had fun and games around the policy, but as Citrix, we have to be more circumspect. It’s possible to publish comparisons against “Hypervisor A” and “Hypervisor B,” though.
How about comparisons with Microsoft? Pretty soon, Microsoft will be able to claim that all the people who have Server 2008 have Hyper-V, won’t it?
Pratt: Yes, but then there will be the question of how many people are using it, and how many people have the bits. If we wanted to measure Xen market share like that, we would be in great shape, because every Linux distro has Xen included in it.
Is Amazon Ready For The Enterprise?
Source: http://www.nytimes.com/…is-amazon-ready-for-the-enterprise-26615.html
Author: ALISTAIR CROLL
Copyright: GigaOm
With a flurry of announcements in recent weeks, Amazon has extended its cloud computing lead. The beta label’s gone. It can run Windows applications. By investing in firms like Elastra, it’s tackling enterprise deployment. And there’s a 99.95 percent uptime guarantee.
Much of this is a pre-emptive strike at Microsoft’s upcoming cloud offering. Microsoft has a huge advantage: It owns the stack from OS and virtual machine through to application. Amazon wants to compete on reliability and performance, rather than software suites and licensing. But there are still some things missing before enterprises will really embrace it.
Back in May, most of the people we asked were more likely to trust Amazon than Microsoft with their enterprise applications. But while enterprise customers are using Amazon already, in many cases that use is limited to a department or a short-term project. If Amazon wants to capture entire IT departments, it needs to prove it’s as good or better than in-house infrastructure. And that means delivering responsive, highly available applications, not just an SLA.
To accomplish this, Amazon needs to tackle performance and availability at an architectural level. When companies build their own applications, they rely on building blocks like load-balancing, WAN acceleration, managed DNS and redundant data centers. Fortunately, this is where much of Amazon’s roadmap leads.
- Network performance: Amazon’s CDN will get static content closer to users. With availability zones, Amazon can also get computation near the edge. All of this reduces the time it takes to deliver bits to users. But it can be faster still: Modern enterprises squeeze every millisecond out of the network. Amazon should also add route optimization, HTTP and TCP optimization to really address network delay.
- Processing performance: Internet architects improve server performance with load-balancing. First send the request to the fastest data center, then send it to the fastest machine in that data center. If there aren’t any fast machines, the newly announced dynamic scaling will make new ones. All that’s missing (though hinted at) is the ability to measure user experience so EC2 knows when to add new servers. Amazon needs a complete load balancing/monitoring/scaling strategy — with proper controls so IT staff can manage it — to make elastic computing a reality. While they’re at it, a performance SLA would be great, too.
- Network availability: Those same load balancing technologies improve uptime, using DNS or BGP to bypass unreachable data centers. Amazon needs to launch a SimpleDNS service, tied to availability zones and performance, that gives operators more control. It’s going to have to deal with DNS when it launches its CDN anyway. This looks less like managed DNS (Amazon uses UltraDNS already) and more like products from F5, Citrix or others. Amazon also needs to open up about its carriers and peering arrangements for enterprises to feel comfortable.
- Processing availability: Big Internet sites don’t achieve high uptime with machines that always work. Instead, they monitor for failure and then have the load balancers take out bad servers. That way, overall availability can be high, even when individual components are broken. Amazon should add load testing and profiling capabilities – particularly since EC2 doesn’t give users deep visibility into the platform — to ensure that applications work worldwide under stress.
Amazon’s plans for integrated scaling, monitoring, and load balancing in EC2
As Amazon CTO Werner Vogels pointed out, enterprises like cloud computing for its economics, its elastic capacity and its ability to deliver high reliability. With this roadmap, Amazon goes after Microsoft’s weak spots. But it’s not there yet.
The Cloud Computing Adoption Model
Source: http://www.ddj.com/web-development/211201818
The Cloud Computing Adoption Model
Think of any historical IT transformation and you’ll likely recall the pain associated with change. For large organizations, change isn’t easy and it certainly doesn’t occur overnight. It requires a finessed combination of planning, validating, selling and a fair amount of political cajoling to get people signed up for the change. It also requires an incremental, stepwise progression that yields benefits along the way — without this, stakeholders become fatiqued, enthusiasm wanes and projects lose steam. When merchandised effectively, these incremental wins become the kindling that stokes the fire, building the enthusiasm, conviction and confidence required for transformation.
This was true for ERP and SOA projects in years past, and it’s true for cloud computing projects today.
Cloud computing promises to reduce operating costs by increasing infrastructure utilization and reducing server sprawl; to reduce the cost of software consumption by allowing business lines to align cost with value received; and to dramatically improve business agility by compressing deployment cycles and time to value for application functionality.
It’s no surprise that cloud has attracted dozens of new entrants and forced incumbent vendors to articulate their own cloud strategy. This heightened level of interest has both advanced the thinking in this space and added to the considerable confusion today’s enterprises face. If history is any prologue, this confusion will only continue and compound. The forecast for cloud: strong chance of fog.
This certainly doesn’t help matters as organizations try to sort out their own cloud strategies.
For any large-scale IT transformation, the question becomes: How do you eat the elephant? The answer, of course, is quite simple: one bite at a time. This is the explicit goal of the Cloud Computing Adoption Model — a graduated, stepwise approach for the adoption of cloud technologies. It helps to cut through the hype and lay out a clear game plan, incrementing toward cloud without putting projects, budgets and even careers at risk.
Loosely modeled after the Capability Maturity Model (CMM) from the Software Engineering Institute (SEI) at Carnegie Mellon University, the Cloud Computing Adoption Model proposes five steps:
Level 1: Virtualization. The first level of cloud adoption employs hypervisor-based infrastructure and application virtualization technologies for seamless portability of applications and shared server infrastructure.
Level 2: Cloud Experimentation. Virtualization is taken to a cloud model, either internally or externally, based on controlled and bounded deployments utilizing Amazon Elastic Compute Cloud (EC2) for compute capacity and as the reference architecture.
Level 3: Cloud Foundations. Governance, controls, procedures, policies, and best practices begin to form around the development and deployment of cloud applications. Initially, Level 3 efforts focus on internal, non-mission critical applications.
Level 4: Cloud Advancement. Governance foundations allow organizations to scale up the volume of cloud applications through broad-based deployments in the cloud.
Level 5: Cloud Actualization. Dynamic workload balancing across multiple utility clouds. Applications are distributed based on cloud capacity, cost, proximity to user, and other criteria.
For each level, the Model outlines the strategic goals, key investment requirements, expected returns, risk factors, and readiness criteria for graduating to the next step.
At the end of the day, architectural innovations like cloud have transformational potential for enterprises. But the reality is that transformation can’t happen overnight — and it certainly can’t happen without a plan. While the Cloud Computing Adoption Model may not represent a panacea for enterprise cloud computing, it does provide a context for thinking strategically about the pace, pattern and sequence of investments and returns that will set organizations on a pragmatic path to cloud.
Cloud Computing with Linux
Source: http://www.ibm.com/developerworks/linux/./l-cloud-computing
Author: M. Tim Jones, Consultant Engineer, Emulex Corp.
Click the source URL to view the original article. I brief some key points with diagrams
Figure 1. Cloud Computing migrates resources within internet

Figure 2. Virtualization and resource use

Figure 3. The layers of Cloud Computing

Figure 4. Cloud Computing landscape

Linux and open source in the Cloud
SaaS is the ability to access software over the Internet as a service. An early approach to SaaS was the Application Service Provider (ASP). ASPs provide subscriptions to software that is hosted or delivered over the Internet. The ASP delivers the software and charges fees based on its use. In this way, you don’t purchase the software but simply lease it on an as-needed basis.
|
Another perspective on SaaS is the use of software over the Internet that executes remotely. This software can be in the form of services used by a local application (defined as Web services) or a remote application observed through a Web browser. One example of a remote application service is Google Apps, which provides several enterprise applications through a standard Web browser. Remotely executing applications commonly rely on an application server to expose needed services. An application server is a software framework that exposes APIs for software services (such as transaction management or database access). Examples include Red Hat JBoss Application Server, Apache Geronimo, and IBM® WebSphere® Application Server. Many other application servers exist, and an extensive list is included in Resources.
Another recent example of SaaS is Google’s Chrome browser. The browser is an ideal environment as a new desktop through which applications can be delivered (either locally or remotely) in addition to the traditional Web browsing experience. (For more information, see Resources.)
PaaS can be described as an entire virtualized platform that includes one or more servers (virtualized over the set of physical servers), operating systems, and specific applications (such as Apache and MySQL for Web-based applications). In some cases, these platforms can be predefined and selected; in others, you can provide a VM image that contains all the necessary user-specific applications.
One interesting example of a PaaS is Google App Engine. App Engine is a service that allows you to deploy your Web applications on Google’s very scalable architecture. App Engine provides you with a sandbox for your Python application that can be referenced over the Internet (and additional languages will be supported in the future). App Engine provides Python APIs for persistently storing and managing data (using the Google Query Language, or GQL) in addition to support for authenticating users, manipulating images, and sending e-mail. The sandbox in which the Web application runs restricts access to the underlying operating system. Although App Engine limits the functionality available to your application, it supports the construction of useful Web services. Check out Resources for more information.
Note: Deploying applications in App Engine is free within certain bandwidth and storage constraints. To build production Web sites with App Engine, usage fees are assessed.
Another example of a PaaS is 10gen, which is both a cloud platform and a downloadable open source package for creating your own private cloud. A software stack similar to App Engine, 10gen provides similar functionality to App Engine—with certain differences. With 10gen, you can develop applications in Python as well as the JavaScript and Ruby programming languages. The platform also uses the sandbox concept to isolate applications and provide a reliable environment over a large number of computers (built, of course, on Linux) using their own application server.
IaaS is the delivery of computer infrastructure as a service. This layer differs from PaaS in that the virtual hardware is provided without a software stack. Instead, the consumer provides a VM image that is invoked on one or more virtualized servers. IaaS is the rawest form of computing as a service (outside of access to the physical infrastructure). The most well-known commercial IaaS provider is Amazon Elastic Compute Cloud (EC2). In EC2, you can specify a particular VM (operating system and application set), and then deploy your applications on it or provide your own VM image to execute on the servers. You’re then billed simply for compute time, storage, and network bandwidth.
The Eucalyptus project (Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems) is an open source implementation of Amazon EC2 that is interface-compatible with the commercial service. Like EC2, Eucalyptus relies on Linux with Xen for operating system virtualization. Eucalyptus was developed at the University of California, Santa Barbara, for the purpose of cloud computing research. You can download it from the university’s Web site (see Resources), or you can experiment with it via the Eucalyptus Public Cloud with certain restrictions.
Another EC2 style of IaaS is the Enomalism cloud computing platform. Enomalism is an open source project that provides a cloud computing framework with functionality similar to EC2. Enomalism is based on Linux, with support for both Xen and the Kernel Virtual Machine (KVM). But unlike other pure IaaS solutions, Enomalism provides a software stack based on the TurboGears Web application framework and Python.



