Nearly every major at LinuxCon, and of course each private conversation I had with the people here are engaged in some kind of "cloud". How Red Hat CEO Jim Whitehurst said in his keynote, no single definition of "cloud" exists. There is no doubt that Amazon really pioneer default cloud offering, but there are a lot of work going on to build a better, more reliable and more open solutions cloud.
Red Hat has the OpenShift, their platform as a service and CloudForms, their infrastructure as a service offering. Long term, according to Whitehurst is that programmers the company will start to build something on OpenShift and not worry about any of the underlying infrastructure. If the product is ready to be deployed inside the country, it will go to the CloudForms client installation inside the company firewall. In principle, developers will select the platform and you can own and manage the operations of this platform.
Canonical pushes ensemble, their "service orchestration solution. Instead of thinking about applications, Canonical wants to see people start to think about services. Instead of deploying the Web server application that talks to a database application for reporting and to receive input from visitors to the Internet, instead of thinking about the "blog tools" that can be deployed through a series of recipes. According to the Canonical Allison Randal Canonical feels that Amazon AWS sets a high standard and Amazon API must be accepted by everyone. This allows users of cloud services have some modicum of portability: if my ISP cloud connectors to their prices, I should be able to smoothly move to a different provider or cloud-my own private cloud — because the fundamental mechanisms for interacting with him (published API) must be the same between the suppliers.
When Randall told me this, I was initially skeptical. If your ISP cloud connectors to their prices, it is a business task. This is not specific to the cloud or the technology sector as a whole. There is real value in the ability to switch from one cloud provider to another or make the decision public cloud House? Then I listened to Marten Mickos keynote. Mickos, the former CEO of MySQL AB, now in eucalyptus systems, innovative solutions to the private cloud. His principal stopped for a couple of very interesting things.
Firstly he briefly cleared up confusion around public and private clouds and how you can use both. Turn on the phone. Telephone infrastructure has been around for about a hundred years, and nearly every company still performs its own internal PBX system. This is a pretty solid lines of clouds.
But the most interesting thing that raised Mickos the importance of the principles of free software in relation to the decisions of the cloud. With the old paradigm of Linux distributions four freedoms provided by the GPL was crucial to ensure the long-term success of the platform, because it explicitly allows derivative works. Moving to the cloud, however, we look at the image, not distributions, and the whole notion of the derivative work is fuzzy at best. How are the four freedoms applied to situations, cloud GPL?
Suddenly a lot more sense Randall in the commentary. So, too, whether OpenStack, is the result of cooperation between RackSpace and NASA establish a framework of common, open cloud.
Mickos has its major repeating that Linux has gone from the destructive forces of innovation. Its concluding comments, the very nicely in line with Whitehurst keynote: Linux is now the default selection for the deployment of new technologies and is the basis on which to build the best future technological advances. Whitehurst and Mickos said that the transition that we are now seeing in the cloud, at least as fundamentally radical as the transition from MAINFRAME to client server.
As innovation continues over Linux in the cloud, Mickos offering some very insightful tips: we must strive to ensure that no one, which we opened closes.
Photo credit: clouds, karindalziel, on Flickr.
No comments:
Post a Comment