Late last week we became aware of a group of vendors promoting an Open Cloud Manifesto from a Microsoft blog post. A great deal has already been written about the manifesto and a bit of controversy it created on ZDnet, eweek, cnet, Silicon Alley Insider, and others.

The manifesto attempts to broadly define cloud computing, the issues it can create for users, and a list of principles the supporters suggest cloud vendors should adhere to:

1. Cloud providers must work together to ensure that the challenges to cloud adoption (security, integration, portability, interoperability, governance/management, metering/monitoring) are addressed through open collaboration and the appropriate use of standards.

2. Cloud providers must not use their market position to lock customers into their particular platforms and limiting (sic) their choice of providers.

3. Cloud providers must use and adopt existing standards wherever appropriate. The IT industry has invested heavily in existing standards and standards organizations; there is no need to duplicate or reinvent them.

4. When new standards (or adjustments to existing standards) are needed, we must be judicious and pragmatic to avoid creating too many standards. We must ensure that standards promote innovation and do not inhibit it.

5. Any community effort around the open cloud should be driven by customer needs, not merely the technical needs of cloud providers, and should be tested or verified against real customer requirements.

6. Cloud-computing standards organizations, advocacy groups, and communities should work together and stay coordinated, making sure that efforts do not conflict or overlap.

In the end, the manifesto simply puts in words the guiding principles 3tera has held to for the past three and a half years. We’ve embraced numerous existing standards, used open source where possible, introduced no new APIs, worked with existing management systems, ensured data portability, made sure users have a choice of providers across the globe, posted all our docs and specs online from day one, and when invited we’ve participated in interoperability discussions. We’re pleased these values are being embraced.

However, the manifesto is not without issue. First, the major cloud service providers weren’t participants in it’s creation, which raises questions about it’s viability. Second, as pointed out in the Microsoft post, acceptance is required “as is” with no acceptance of feedback. Third, it’s unclear exactly who controls the manifesto, what it’s future is, and whether there’s a process for participation in moving it forward. For these reasons, we’re holding off on endorsing the manifesto at this time.

3tera is fully committed to open cloud computing not just in principle, but in deeds. When there’s a truly open effort to define interoperability, application and data portability, and cross-cloud integration we’ll be a full participant.

What a difference a few years can make. When we launched AppLogic and described how IT could use resources outside their own data centers to run their apps, many folks were initially very skeptical. Although Nicholoas Carr had written and spoken about this for a couple years already at that point, more than a few told us we were nuts. Our ideas on packaging operating systems into appliances was even more controversial at times, prompting some heated blog posts. It all reminded me of the old quote “If (your idea) is original, you will have to ram it down their throats.”

Of course, today cloud computing has become one of the hottest topics in technology, and the current economic climate is only accelerating that interest. As IT shops in companies large and small try to do more with less resources, they are looking to cloud computing for its flexible resource usage, low capital costs and ease of management.

Join 3tera and Forrester Research Principal Analyst James Staten for a free Webinar on March 4th as explore the new frontier of global cloud computing. Jame will discuss what he’s learned from enterprises that are looking to build their cloud strategy about their concerns and considerations. In addition, we’ll also demonstrate some capabilities of the global cloud live, incorporating both public cloud services and private clouds behind the corporate firewall.

Nicholas Carr has an article in The Atlantic titled Is Google Making Us Stupid? that got me thinking over the weekend. I’ve noted before how Google’s ubiquitous nature can have unintended consequences, such as the de facto standardization of spelling and grammar. In his article Nick notes that the nature of searching for information is having profound impact on the way in which he and others read:

“. . . what the Net seems to be doing is chipping away my capacity for concentration and contemplation. My mind now expects to take in information the way the Net distributes it: in a swiftly moving stream of particles. Once I was a scuba diver in the sea of words. Now I zip along the surface like a guy on a Jet Ski.”

I’ve noticed this myself as well, a feeling that the Internet is condensing all information into Cliff’s Notes. In particular, this has been quite concerning in the blogosphere, where it often seems folks expect hard issues to be discussed and resolved as quickly as they can post. In a previous post on standards for cloud computing I cited a few threads where folks expected publication of specifications and standards as easily as posts to a blog. Of course, that simple isn’t possible, but I believe that the speed with which we access information online builds that expectation.

It appears that one unintended consequence of unhindered access to information is a sort of commoditization of thought. Information is simply so easy to come by that we tend to value it less. Worse, ideas and the effort to communicate them are discounted by the sheer volume of information that floods our senses at every waking moment.

As an example, when I was an undergrad some 25 years ago at CSUF, research was painful. I might spend hours scouring through microfiche, racks of books or the dreaded manual stack for the CDC Cyber mainframe trying to find information. Having unearthed what I was looking for, I was certain to write it down or copy it.  Today, however, I write down as little as possible. Written information is the first thing I lose. I also almost never copy of print information. Rather, I rely on my ability to search for it again. Google has become an integral part of my process for consuming information.

I can’t share Nick’s more pessimistic view of the situation though. Humans are resilient and have a way to adapting technology to their needs even if at first it appears the other way around. I, for instance, picked up an Amazon Kindle a couple months ago. Using the same technologies that can commoditize thought, the Kindle places entire books at my disposal even when I’m unconnected at 30,000 feet. Since getting it I’ve read two novels, three business books, a science book, and numerous magazines and newspapers. That would have been more than a year’s reading before. Plus, I’ve noted more young kids carrying books with them recently than laptops. They’ve got their phone for texting, and their iPod, but no laptop. Perhaps, the market is already pushing back.

Kevin Kelly has a post on The Technnium about whether google sized data sets will lead to a new way of doing science:

“There’s a dawning sense that extremely large databases of information, starting in the petabyte level, could change how we learn things. ”

Kevin’s post was pointed out to me by Jonah Stein and caught my attention because a couple AppLogic users are starting to build very large data sets and as a result we’re ocassionaly asked about how to access and distribute them. However, the post really is less about the technology of dealing with these data sets and more about whether they’ll change the way science is conducted, which is another subject I’m interested in so I read on. Kevin’s post was inspired by a Wired cover story “The End of Theory” by Chris Anderson who writes:

“There is now a better way. Petabytes allow us to say: “Correlation is enough.” We can stop looking for models. We can analyze the data without hypotheses about what it might show. We can throw the numbers into the biggest computing clusters the world has ever seen and let statistical algorithms find patterns where science cannot.”

So, Chris’ theory is that if we have sufficiently large data sets we’ll be able to act merely on the finding of correlation rather than waiting to understand the actual mechanism that relates the data - the cause and effect. However, IMHO data without understanding isn’t knowledge. In fact, it can be dangerous because the conclusions reached through statistics are very susceptible to influence by what data is collected.

In the 70’s Harvard medical school researchers had reams of data correlating breast feeding infants with juvenile cancer. Simply accepting the statistics could have lead to some horrible decisions. Fortunately, they didn’t accept the statistics and further research showed breast feeding doesn’t cause cancer, but that carcinogens in the mother’s environment and diet were being passed through to the baby.

The Eugenics movement a century ago was based on statistics correlating skull shape of different races with intelligence test scores. This psuedo-science was in part responsible for Nazi atrocities. Of course, we understand now that the intelligence tests were geared towards white Europeans, but without that knowledge, the statistics seemed compelling to people of that era.

Even the low birthrate issues in Europe today could provide miscues if you just accept the statistics. Is the cause that people are less religous than in previous generations? Is it that government subsidies are higher than other countries, or that they’re lower than 50 years ago? Is it pollution or economics? There are statistics to prove each of these.

In pure mathematical sciences huge data sets will provide scientists with interesting insights on where to focus their research. Used properly they will provide a sort of short cut to new theories to test and those theories will provide feedback into the system on what data to collect in the future.

After a couple decades building technology, you come to realize that technology development is really a cycle rather than a vector. For instance, the way in which AppLogic packages an application and its infrastructure is analogous to the way you’d launch an app on an SMP system with a shell script that starts processes and connects them through sockets. Jason Brooks has a short but interesting piece about this subject, and the way in which the iteration adds value.

Often the parallels aren’t obvious at first, because you start out trying to solve a problem rather than recreate a technology in a new space. As an example, we weren’t trying to create an operating system when we started AppLogic - we simply wanted to help folks scale web services. We wanted to give them a way to express the application structure so it could be implemented by a system rather than operators. Only after we had the first prototype running did it became clear we’d built a new kind of operating system, a meta operating system.

What’s unique is that a meta operating system has no APIs of it’s own, because the code runs in guest OS’s. Still, the meta OS controls resources, schedules processes and provides the user a console.

Realizing this was an important step and made completing the project easier. Realizing we had an OS meant we now had a template to refer to whenever we weren’t sure how to solve a problem.