What does this have to do with the just concluded April 2013 OpenStack Summit? Everything! The Summit was a big turning point for the just under three year old Open Source Cloud Platform Project. Never before has the Summit felt more like a real business conference with a clear-eyed agenda to architect a stable and viable enterprise ready cloud platform, rather than just a bunch of wild developers on a mission to save the world. After several years of intense development and shakedown, OpenStack is finally more than ready to take on the unique challenges of enterprises that want to deploy private clouds.

There were plenty of great examples of respected organizations, public and private that have crossed the innovation chasm by deploying OpenStack clouds into their production environments. The keynote sessions all highlighted large enterprise case studies to emphasis the message that OpenStack is a strong and very viable option. Here are just a few to whet your appetite:

• • Bloomberg has deployed a large scale internal cloud, for a variety of applications including analytics and support of their backend systems.
• • BestBuy built an OpenStack cloud to support their extremely spiky holiday rush traffic. In just eight months, 25% of their systems ran on their new cloud in time for the 2012 Christmas buying season. They found the new platform, combined with a move to a PaaS push button development environment and a server side delivery architecture, allowed them to speed delivery of their catalog content pages down to under 2 seconds, while saving over $500K per platform upgrade. How is that for some serious discounting!
• • Comcast Cable and NBC/Universal built an OpenStack cloud to move content delivery out of proprietary limited function set-top boxes and into backend servers, giving them more flexibility and capabilities for the development of new interactive features such as live streaming and gaming.
• • The NSA, yes the spies in DC, are using OpenStack. Of course, what, how and why they are using it were not shared, but clearly they are not overly concerned with reports of security deficiencies.
• • Samsung is rolling out a production grade platform that will support millions of users across the globe. If the success of the new Android based smartphones and tablets are any indication, Apple should be looking over its shoulder very carefully.

In conclusion, if your company is contemplating a public or private cloud deployment, you should be putting OpenStack at the top of your shortlist. The rich ecosystem of big names, such as Dell, IBM, RedHat and Cisco is a clear signal that OpenStack has arrived!

About the Author
Beth Cohen is a senior cloud architect for Cloud Technology Partners, Inc., focused on delivering solutions to help enterprises leverage the efficiencies of cloud architectures and technologies. Previously, Ms. Cohen was the director of engineering IT for BBN Corporation, where she was involved with the initial development of the Internet, working on some of the hottest networking and web technology protocols in their infancy.

From the Enterprise perspective, now has never been a better time to invest in cloud services. Enterprises are broadly adopting all types of cloud services at multiple levels in the organization. Initial predictions were for the enterprise to favor private and community clouds over public services, but the hottest trends in Cloud adoption has been Software as a Service (SaaS) and cloud-based business applications which are projected to grow from $13.4 billion in 2011 to $32.2 billion in 2016, a 19.1% five-year CAGR! The rapid adoption of SaaS applications of all flavors by the enterprise has been a surprise to many, but the vastly reduced costs due to the pay as you go pricing models, and high degree of service delivery flexibility has overcome any perceptions of needing to trade price for reduced feature sets. Unsurprisingly, the most often added cloud-based application services are Customer Relationship Management (CRM), Supply Chain Management (SCM) and Enterprise Content Management (ECM), with Web Conferencing, teaming platforms and social software suites nipping at their heels.

Infrastructure as a Service (IaaS) continues to appeal to companies that want to replace in-house and traditional data center models for the cloud hardware abstraction approach. Gartner is predicting Infrastructure-as-a-Service (IaaS), cloud management & security devices, and Platform-as-a-Service (PaaS) are growing from $7.6B in 2011 to $35.5B in 2016, a CAGR of 36%. A word of warning for companies that think just because the Amazon cloud is easy to use, it is easy to build and manage. Building a private cloud still requires a degree of expertise that few enterprises have in-house. In the next year or so expect more companies to see the value of using the services of cloud consultants to avoid painful and expensive mistakes when building private clouds; or alternatively using emerging enterprise focused public cloud services such as Bluelock or Terremark.
Platform as a Service (PaaS) which still does not quite know what it wants to be when it grows up, is lagging with only about $1B in revenue in 2012, but as the market matures, expect to see rapid uptake as companies recognize the value of standardized tools that can ease the pain of Cloud application deployments. Some of the newer PaaS tools like the ServiceMesh Agility Platform combine the features of a SDLC workflow engine, production support and orchestration across different cloud platforms.

New Cloud Technology Directions

Ultimately, innovation is the marriage of technology and organization change. The dilemma is how to pull innovation into IT core functionality without disrupting the flow of new ideas, when the modern enterprise understanding of IT is focused on operational excellence and cost control. The CIO should be leading the cultural change to the new flat organization by leveraging cloud and mobile application in new and interesting ways. The trick is to create tools for people to quickly test and validate their ideas so they can implement new ideas that work within the enterprise framework. Cloud tools can be used to deliver on that promise, but is the enterprise up to that challenge?

This is not the first time wrenching technology innovation has changed how companies do business, and it certainly will not be the last. Companies able to use disruptive technologies, such as cloud computing, effectively will leave companies who do not have that ability in the dust. By recognizing the seeds of change and embracing them, the smart company can leverage cloud services by using the efficiencies of pooled IT resources at the same time allowing greater flexibility to meet the challenges of the global economy. This combination of combining commodity utilities with innovation allows companies to compete effectively using the efficiency and flexibility strategies simultaneously.

Challenges, Always Challenges…

Consumers intuitively get cloud and have been more than willing to embrace it warts and all as it has matured. They are highly price sensitive and will easily sacrifice features in exchange for low cost. On the other side of the market spectrum, the more conservative enterprise market is still struggling with the basic model. Some companies worry that the emerging cloud companies are too small to do business with, while others are concerned with how to incorporate new technologies into existing technology portfolio investments. To address their concerns, at the same time as Cloud technology continues to mature and standards develop , innovation around service delivery and breakthroughs in storage technologies are making it ever more enterprise ready. The pace of cloud vendor consolidation has already picked up as the traditional enterprise vendors such as HP and IBM has rushed to add enterprise ready cloud services to their portfolios. This should alleviate the fears of even the most technology adverse companies.

A final word for any remaining cloud technology skeptics, as with any innovative force, the cloud is just a tool to drive change, not an embodiment of change itself. Enterprise cloud consulting leaders, have firsthand experience with how companies willing to ride the Cloud revolution will not only survive in today’s hyper-competitive world, but thrive. I cannot wait to see where the next wave takes us!

About the Author
Beth Cohen, Beth Cohen is a senior cloud architect for Cloud Technology Partners, Inc., focused on delivering solutions to help enterprises leverage the efficiencies of cloud architectures and technologies. Previously, Ms. Cohen was the director of engineering IT for BBN Corporation, where she was involved with the initial development of the Internet, working on some of the hottest networking and web technology protocols in their infancy.

As I mentioned my previous post on the recently concluded OpenStack Summit held in San Diego October 2012, OpenStack needs to be taken seriously by anyone who is interested in building a public or private cloud.  For the more technically inclined the latest Folsom release has several new modules and features of interest to the enterprise and cloud service provider alike:

Quantum – Software Defined Networking (SDN), the latest darling of the cloud world is moving forward quickly with some really valuable features including L2 to L3 tunneling and a network API.  Expect to see lots of new development here.  On a side note, there was a great panel on the future of SDN moderated by Ken Pepple from Cloud Technology Partners, with people from Midokura, Big Switch and HP Cloud Services talking about their vision of the future for SDN.

Cinder – Now that Cinder has been spun out as its own named project, new features include intelligent location of Virtual Machine image storage, real snapshots, live migration, and more capability for large scale simultaneous VM initiations.

Keystone – New features includes support for role-based identify management (RBAC), PKI functionality, tools to add integration capability with enterprise grade account management systems such as Active Directory and other LDAP based systems.  Rumors of Kerberos support coming were floating around.

Documentation and security are both finally being taken seriously, with a half day documentation track on Monday morning and a full day of security related sessions on Thursday.  There was recognition among the lead techs that the developers who are creating OpenStack are not the users.  This resulted in much discussion regarding new features to make it easier to do deployments, upgrades (finally!) and manage it by operations folks.  There even was some discussion of IaaS/PaaS integration and how the VM’s work with the platform, a long overdue recognition that the IaaS and PaaS layers of the cloud stack are intimately related.

On the subject of operations, the tools to manage OpenStack are still weak, but they are no longer non-existent.  Ceilometer and heat among others look promising, but the better operations management tools are still mostly part of separate distributions such as Cloudscaling, Nebula, StackOps and others rather than being part of the product core.  While I do see the reasoning behind this thinking, at the very least we really need to have some standardized installation tools.  There is little benefit for every instance and distribution to reinvent the wheel.

One final note, one thing that was quite noticeable was that the Grizzly design sessions had a very different vibe from previous summits.  While some were packed with lots of discussions about new features, more often the Technical Project Lead and a few others ran the show with little input from the other participants in the room.  As the number contributors grow, the community is going to need to work hard to avoid having the immediacy of the Summit be diluted.

That doesn’t mean there isn’t plenty of meat already, but as can be seen by this tiny sampling of the current hot projects, there is still much work to be done.  The good news is the OpenStack community is ready willing and capable of delivering the goods in the coming months and years.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

From CTP’s perspective, since the majority of our customers are the big enterprise, we need to evaluate IaaS providers against a very different set of criteria. The enterprise is going to be more cautious – partially because they need to be and partially because they can afford to be — about putting anything beyond dev/test in these types of public IaaS services.  Gartner only touched on the IaaS requirements that are really important to the enterprise, regulatory compliance, true high availability SLA’s, support for large scale global deployments and a cost structure that isn’t essentially linear.  From that perspective, the Magic Quadrant would look very different: CSC, IBM, HP, Savvis and Terremark would all be top tier players, with Rackspace and Amazon in the niche quadrant.

On a side note, it is quite noticeable just how many of the providers on the list have at least some OpenStack built into their infrastructure.  HP Cloud Services is 100% based on OpenStack, while RackSpace is migrating from their legacy infrastructure as fast as they can convert their customers.  Internap, AT&T and others have either already stood up OpenStack services or have announced that they are in the works.  Definitely validates the OpenStack approach.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

After four extraordinary days of immersion into all things OpenStack at the just concluded OpenStack Summit in San Diego, I can heartily say without reservations that OpenStack is not only very real, it is truly a game changer for the IT industry.  With that being said, yes, there is certainly plenty of hype about this Open Source Infrastructure as a Service (IaaS) offering – one wag even quipped that OpenStack was at the peak of the Gardner hype cycle, so it must be real.  Here are just a few highlights for the terminally busy:

• The technology has come a long way since the project’s August 2010 inception.  With 13 major corporate foundation contributors, it seems like the only major technology companies not involved are Amazon and Apple.
• There was much discussion about the newly created OpenStack Foundation as an organization and its long-term viability.  However, compared to where the Apache Foundation was at the same time in its lifecycle, the OpenStack Foundation is far ahead of the curve.
• OpenStack is definitely gaining market traction.  There were plenty of academic, enterprise and service provider IT folks kicking the tires.  To encourage more market adoption, the website is featuring user stories.  A new one from WebEx was inspired by a visit to the Boston conference where the engineers saw the Mercardo Libra success story.
• While there was still a preponderance of developers in attendence (it was a design summit after all), there were more operations and business types than ever.  The vendor area was busier than ever.
• The biggest technical buzz was around Quantum and virtualized Software Defined Networking (SDN) — standing room only at the technical update and all the design sessions, but Cinder, and Keystone were not far behind in incorporating new features and functionality.
• Every time I turned around there seemed to be a new distribution available from both the usual suspects, such as Piston and Nebula, and the big players such as Cisco, SuSe and ???.  Niki Acosta’ Vapor Trail blog has a nice summary of the many vendor announcements.  More on the case of the proliferating distributions coming…
• And finally, the parties this time were for the most part more subdued.  HP’s soirée at the New Children’s Art Museum was cool, but the endless Techno Musak at all of them just gave me a pulsating (pun intended) headache.

As can be seen from this tiny sampling of the Summit activities, an enormous amount of energy and momentum has built up in just over two years.  For a project that will likely eventually be as important as Apache and Linux, every organization and person who has contributed to it should be justifiably proud of their accomplishments so far.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

On paper, the concept of the development and operations part of an IT organization working in concert is wonderful.  In fairness when a company makes the effort to encourage the organizational changes that need to be done, the productivity gains, velocity and quality improvements of the IT systems more than make up for the pain of the organizational changes.  However the effort of making that transformation is often far more fraught with technical obstacles and political stumbling blocks than many over-stretched IT organizations is capable of handling.  Fortunately with proper guidance there are Agile and organizational transformational techniques that can be used to overcome the issues.

Often the reasons why these transformations are not as successful as they could be fall into three categories:

Organization, Political and Business Issues – Anyone who has ever worked knows that organizational issues are the most deep-seated and difficult to overcome.  The old boys’ networks and entrenched ways of thinking are sometimes insurmountable roadblocks.  There are several methods to address these issues, but in all cases strong sponsorship and support from the executive ranks is essential for a successful creation of a DevOps mindset in an organization.  One way to influence the change is to take a page out of the old organizational change playbook; create an organization that aligns with the desired outcome.  In one large enterprise the solution to the resistance to changing from the old IT operational mindset was to reorganize the entire IT organization so that the development and operations groups reported into the same structure.  The manager of both groups was a strong believer in the need for DevOps to support the company’s multi-million dollar cloud initiative.  By forcing the groups to work together in Agile Swarms, they were able to build the trust and skills needed to bring about the organizational transformations.

Outsourced IT Business Model – Yup, you read that correctly.  For all the touted benefits of outsourcing, and I will agree that there are many, agility and organizational transformation is not one of them.  The outsource vendor is motivated to manage risk by eliminating as many unknowns as possible.  Like traditional IT operations the easiest, but no always the best way to accomplish this goal is by minimizing changes in the environment.  This encourages rigid thinking and highly delimitated roles.  It isn’t always that the work is off-shored that causes problems.  Often the issues are related to poor project management, unclear articulation of the team goals, and a disconnect between the purchaser of the services and the vendor.  One company is mostly using American labor, but they are so stuck in their ways that they are just starting to think about breaking down the barriers between the functional groups.  Another is having an IT meltdown on the operations side of the house which is causing them major headaches.  Communications issues across the organization and between the vendor and the customer in this mixed shop are behind much of the conflict.

Staff Skills – This is an often overlooked aspect behind the failure of DevOps initiatives, the skills and working habits of development and operations people are typically wildly divergent.  Developers often work on new projects, so are typically more willing to take risks, work with underdeveloped and/or buggy code and generally are not very concerned if things break along the way.  They know that breaking things is just a routine part of the development process.  On the other hand, IT operations people are paid to keep systems running as smoothly as possible.  They are often held to strict SLA’s so they take five-nines seriously.  One way to keep an environment stable is to introduce change as little as possible.  IT operations are famously resistant to changing code on the fly or introducing other things that might cause them to be paged in the middle of the night when the systems have a hiccup.  Who can blame them really?  This defensive mindset can be addressed by applying newer architectures and technologies that are tolerant of component failure – the automated deployment and designed to fail architectures.  Once it is demonstrated that a failure of a component is not a catastrophe, just one more expected event that has no immediate impact on the systems, the next logical step is to build processes that allow continuous incremental changes to the systems.  Encouraging a set of shared standards is a good way to develop DevOps processes across the organization.  For one enterprise this meant building a service catalog of standard images for the developers use with all the commonly used tools.  The developers given the option of using either a pre-built applications tools platform or building a custom one took the easier path.  Standard tools problem solved.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

You would think that cloud technology would have standardized long time ago.  While network standards that shape the Internet have been widely accepted throughout the industry, cloud standards have had a much slower adoption path.  Sadly the current state of cloud standards is, after 15 years, still far less mature than it ought to be.  As cloud infrastructure technology matures, increased interest by the enterprise and emerging vendors is driving a renewed effort to create viable standards that will benefit everyone.

For companies looking for integration and the capability to build hybrid clouds, various standards and proprietary and open APIs have been proposed to provide interoperability up and down the three layers of the cloud stack.  The first and so far only, cloud-oriented standard that has been ratified is the Open Virtualization Format (OVF), which was approved in September 2010 after three years of processing by the DMTF.  OVF’s open packaging and distribution format offers some platform independence by allowing migration between some platforms, but it does not provide all the tools needed for full cloud interoperability.

I think we can all agree that everyone benefits from technology standards in the long-term – the operative word is long-term.  You would think that everyone would agree that cloud infrastructure technology standards should be given high priority, but creating compelling proprietary systems and discouraging standards gives early adopter companies competitive advantage in the short-term.  Think about Amazon and VMware’s vast technology and market leads in the cloud services and enterprise infrastructure systems respectively.  They have little motivation to support any standards that have the potential to undercut their monopoly market positions.

Users of cloud are asking when will cloud computing standards mature enough so that more companies will feel comfortable implementing cloud architectures and using cloud services without feeling locked in.  Ironically, while the commercial cloud offerings have been growing, built on the very standards that created the Internet itself, Amazon and others have been reluctant to publish their architectures.  Application Programming Interfaces (API), which hide the underlying architecture, are all well and good, but they do not guaranty true interoperability.  Downstream vendors quickly find that they need to build API interfaces for all the different services they need to support; adding significantly to the development and maintenance costs.  To address this and transparently transfer workloads among the different vendor based on predefined business rules, there needs to be much more comprehensive standards.

One obvious question to ask is if there is an opportunity for the commercial cloud systems to become standards.  After all, there have been precedents where formerly proprietary formats, such as VMDK (Virtual Machine Disk) which was developed by VMware, have become de facto standards simply by being widely adopted by the industry.  One could even argue that platforms such as Amazon’s AWS are already standards.  However, as many companies have found to their chagrin, while it has a vast variety of services, easy to use tools, and a significant technological head start on the competition, it is more of a cloud world roach motel.  Lots of companies have found it easy to get applications running quickly, but changing providers or taking the applications back in-house as requirements change is fraught with unexpected perils.  Amazon’s backing of Eucalyptus does not address that problem directly, but it does offer a viable option for companies that want to build what Amazon euphemistically calls, on-premise services.

In conclusion, the good news is that the cloud industry is finally reaching consensus that the time to build cloud interoperability standards is long overdue.   The biggest need remains for interoperability standards to allow virtual machines to be migrated between clouds transparently and for more robust hybrid cloud solutions.  For the moment companies that want to use multiple platforms or a mix of public and private options are stuck with complex architectures and emerging orchestration tools such as enStratus and Rightscale to bridge the gap.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

The 2012 MIT CIO symposium purported theme was the untethered enterprise.  Ironically for all the recent media buzz, there was little discussion of untethered enterprises, or even much mention of mobile at all.  Only one panel was slated to cover the topic, but that discussion quickly devolved into a tactical discussion of IT/vendor relationships and SLA’s.  That doesn’t mean that there was no discussion of mobile devices, just few of the in-depth conversations about how the enterprise can best incorporate emerging technologies that I expect from this usually forward thinking and informative conference. Reading between the lines, the enterprise is not quite ready to tackle these difficult considerations.

Very few companies are creating the holistic enterprise mobility strategy that is needed to drive real business advantage.  To put this all into perspective, an informal conference survey revealed that less than a third of the attendees had an enterprise BYOD policy in place today.  Some simply were letting their employees set the standards.  For one company this has resulted in far too many employees with two devices on their desks (one company issued and the other a BYOD of their own choice), and 11K unsupported iPads on their network.  That CIO wryly admitted that maybe it was time for their IT department to address the issue, if for no other reason than they were wasting millions on underused computer resources.

The push to add mobility is coming from both the top and the bottom of the organizations.  For every executive with their hot smartphone, there are 10 employees with three tablets.  However, IT is responding by pushing mobile apps out the door without a good understanding that mobile is a game changing strategy that takes the organization from the traditional top-down IT approach that has been fashionable in recent years back to a bottom up consumer driven initiative. Of course, this is completely runs counter to the traditional IT mindset.  As long as there is a disconnect between the demands of the workers and the services provided by IT, shadow IT will continue to remain a strong force in the enterprise.

From the technology perspective, while enterprise mobility has been around for 20 years in some form or another, the underlying technology to support the mobile apps is still quite brittle.  We are relying on a telecom infrastructure that isn’t fully capable of supporting millions of mobile endpoints.  Because mobility is primarily a device driven technology, it is completely dependent on the infrastructure.  The IT organization is better off getting into the way-back machine and treating them as dumb terminals.  The good news is that mobility security is finally being taken seriously.  Clearly there are some continuing issues that need to be addressed, but the technology and standards are there to make smartphones and tablet secure enough for even government standards.

Several times during the conference, the downsides of hyper-connectivity came up.  One panelist noted an interesting recent trend where formerly plugged-in 20-somethings were choosing to disconnect as they ramped up their careers and realized that separating their private and work lives was a sensible idea.  Several others commented on the need to provide a work environment that is attractive to the tech savvy worker, but old expectations of 100% worker availability is wearing thin.  Many American companies are realizing what the rest of the world has known forever, just because you can touch your workers 24 hours a day, doesn’t mean that you should.  There is an increasing awareness that for sanity if nothing else, you need to apply reasonable business etiquette for worker communications.  My only comment is that after living the 7/24 IT worker life for 20 years this revelation couldn’t come any sooner for me.

What I realized at the end of the day was that mobile and untethered is just a red herring.  The new generation of users sees it for what it really is, shared ubiquitous access to data in the cloud.   For that to succeed It has to be dirt simple and it has to be a thin client service that delivers the functionality that the users need.   That is not so hard, is it?

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

The magic of the cloud is that it can do anything.  It is both robust and flexible, the best of both worlds.  Ok, I admit that I have been spending far too much time reading cloud marketing materials lately.  Now back to reality.  Yes, the cloud is highly flexible and it can do almost anything, but if you want to get the most out of your private cloud investment, you need to pay attention to the underlying hardware as I discussed previously, and you need to define what you are planning on using it for by creating and testing use cases.

Use case planning seems counter-intuitive.  After all you can sign up for a web server with Amazon in about 5 minutes.  Amazon does not know what you are planning on doing with it.  Wrong.  Amazon’s product management department spends plenty of time figuring out exactly what would be attractive to their typical customer and honing the service to deliver it.  For the enterprise, the planning process is no different, but instead of planning for an external paying customer, for example, the use could be for internal application developers or a web portal.

To give you an idea of how this works, let us say, you are planning on using the cloud for the company’s E-commerce website.  This means that you will need to plan for applications that will support thousands of sessions per second, variable workloads and lots of complex and changing data.  By identifying the key metrics such as number of concurrent transactions per second, size of database, etc. you can then build a method for testing your assumptions.

To get the conversation started here is a short list of possible use cases for a private cloud.  Over the next few weeks I will be digging deeper into how to leverage the cloud model in the enterprise.

Archive storage — Many companies have moved to keeping their archives on line instead of on backup tape for many excellent reasons.  Using SAN or near-line storage is still expensive.  Cloud object or block storage is an attractive alternative because of its optimized approach to high availability.  It also scales nicely as archives grow over time.

Federated hypervisor/VM management – This is one of the main reasons that the enterprise is interested in the cloud in the first place – any server, any service, any time.  Adding self-service, charge back and transparent delivery of the right resources from a federated pool can be very cost effective.  Look for a cloud that provides cross platform hypervisor support and robust VM management tools.

Development and test – One of the best use cases for an enterprise cloud is a shared development and test environment.  Self-service is essential, but the private version allows much more control on resource use by using a rules based delivery model to optimize IT investments.  Creating an enterprise PaaS environment is also desirable because it allows better integration across applications and more standardized application development.

Application spaghetti rationalization – An enterprise cloud delivers better application portfolio management and more efficient deployment by leveraging self-service features, rules for deployments based on types of use.

Web services, portals and e-commerce – Web services of all sorts are a natural for the enterprise cloud.  They are well suited to being able to take advantage of the inherent elasticity and automated workload based provisioning and deployment capabilities.

VDI Support – VDI is another natural for an enterprise cloud.  VDI is often used to better maintain control over workers’ compute environments, but the workloads are inherently highly variable, which is an excellent reason for implementing such systems on the cloud.  An obvious extension is mobile application support which is a growing part of the enterprise service portfolio.

Disaster Recovery/Business Continuity — Again the cheap storage and VM management makes a good case for using the cloud as a secondary site.  The public cloud is already heavily used for these purposes, but moving the function in-house could be cost effective for a very large enterprise.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Transforming Businesses with Cloud Solutions

In our work, clients often ask for a cloud reference architecture.  They see it as a holy grail that will provide clear vision and help define their cloud strategies.  In response to a recent client inquiry about a cloud hardware reference architecture that could be used to define a joint venture with another company, I realized that defining a cloud reference architecture as the same hardware platforms was the wrong way to look at the question.  While I do agree a reference architecture is certainly a good starting point, it not something I would build an entire corporate cloud strategy around.

Reference architectures are supposed to be by their nature somewhat theoretical.  Like the OSI model and the cloud stack model, they are artificial constructs or frameworks that can be used to create real systems.  By themselves they tend to be so generic and broad that building an enterprise cloud based on a reference architecture without considerable work defining business objectives and system requirements would only be an exercise in frustration.  For example, an enterprise cloud designed to be used for internal use as a more flexible development platform is a far different animal than an enterprise cloud planned to be used to support massively scalable customer facing applications.

After looking at a few available cloud reference models, a reference architecture means very different things depending on the agenda of the creator.  A useful way to compare the perspectives of the various cloud reference architectures is to map them to the older and simpler Cloud Service Stack Model: IaaS, PaaS and SaaS.  For example: both the NIST and its closely related IBM architecture are relatively generic and high level, but they both have an operational focus which closely matches the IaaS layer.  The recently published RackSpace Private Cloud Reference Architecture while specific to OpenStack, also primarily has an operational/IaaS bias.  Microsoft has defined the cloud not surprisingly more from a development platform/PaaS view, but it also has an IaaS flavored version based on Hyper-V.  The HP and VMWare versions are more appropriate for companies building end to end applications, SaaS or otherwise.

In the end, a good cloud reference architecture should be robust enough to allow it to be used from a variety of different perspectives: business, operations, development and consumer.  However, any company that is foolish enough to try to use a cloud reference architecture to create its strategy without the application of a rigorous amount of common sense and basic good business practices, is likely to be disappointed with the results.

About the Author

Beth Cohen, Cloud Technology Partners, Inc.  Moving companies’ IT services into the cloud the right way, the first time!