Discussion of the Computing Cloud have returned to the forefront, if they've ever really receded from post "boom" media and vendor marketing pitches. Cloud Computing is an intriguing notion and has seemingly become an achievable state of infrastructure, especially for organizations that have either deep-pockets or deep (compelling?) needs.
But underneath Cloud Computing, what is really happening? What is the real metamorphosis that has occurred to make such an outcome attainable? I'll tip my hand by saying that this outcome is result of several significant prerequisites.
The first prerequisite is robust and manageable local/wide area networking, meaning transmission and verbose protocols. The second, and complementary prerequisite, is distributed computing. I'm sure that sounds to many readers like the definition of "cloud computing," but I assure you its not. Distributed computing means that it is no longer cost prohibitive to implement like servers across multiple tiers of infrastructure nor does such a deployment scheme prohibit an organization from running the applications it chooses - in the main. Again, sounds like "cloud computing," but not yet. These two prerequisites are broadly available to organizations of all sizes today. The gating factors to deploying systems that capitalize on these changes are cost, skills, need and vision - to name a few.
The third, and certainly not final, component is the metamorphosis is the one that will present the biggest challenge, and also deliver the biggest most affective outcomes. Yes, even bigger than both the 20 year revolution in networking and the 15 year revolution in distributed computing. On the "plus-side," I don't expect this revolution to take a decade more to deliver results. Still, some could argue, as even my own past statements can imply, that this revolution has been in the making for nearly a decade already. So, what is it I'm talking about?
The change that I believe poses a new and ultimately liberating challenge is that programs and data will become essentially indistinguishable.
To level set, we are not near to the day when data is "executable," but that capability is closer than you may think. The at-hand instantiation of "programs as data," and vice-versa, is found in server and application virtualization. Server virtualization is, today, premised on this change. Those IT professionals wrestling with the novel impact of virtualization on data protection and recovery schemes are all too familiar with this condition.
Today, virtualized servers are transformed into a file. That file contains all of the many programmatic elements and installed applications of a traditional operating system. It also holds specific notations regarding state, configuration and security elements of the encapsulated system. It also includes information about the "hard" network and the "soft" network pathways, qualities of services, I/O prioritization and - of course - proprietary information or data.
The object, or VM file itself, must be captured and cataloged in a number of management systems. Those systems are the virtual infrastructure manager or other systems management frameworks, CMDB-based change control and inventory system(s), compliance enforcement, security and identity systems and lastly, but not least, data protection schemes from back-up to BC/DR and migration. As many storage-centric professionals know, the act of moving or "failing-over" a VM from one physical system to another, or even within the confines of a common blade system, requires a very complex ballet within the supporting SAN that demands the exact coordination of WWN relocation, port reassignment and path redirection (with all of the zoning and QoS attributes intact). Not a trivial act!
So, what does it mean for storage/information management when, as the above example foreshadows, data and programs become nearly indistinguishable? For one, its easy to see that a major burden or operational obligation is pushed out of the domain of sever/host based functionality and into the realm of networking and information management. By way of a plug, and toward keeping this, and most entries to this BLOG, short, I'll point you to the first in a series of vision papers produced by my firm. The TAP Model, and other forthcoming and complementary papers, are meant to address this issue either directly or the impact of the transformation of programs and data within explicit functional domains.
This BLOG will be primarily concerned with these changes and their impact on the "legacy," meaning the infrastructure you are tasked with running as if it were a part Indy car, part open sand-box.
One final word. The "cloud" is obviously a metaphor. So, think of it as such. What do clouds do? They obscure and hide clear skies, produce thunder, lightening and rain and can be the heart of a storm. So, when looking at the "cloud," your cloud, remember to look for the internal components that come with clouds. I'll expand on this metaphor and clarify other aspects of the "data/program" duality.
More to come, soon!