Feeds

NASA drops Ubuntu's Koala food for (real) open source

Open core is not open source: a cautionary tale

New hybrid storage solutions

NASA is dropping Eucalyptus from its Nebula infrastructure cloud not only because its engineers believe the open source platform can't achieve the sort of scale they require, but also because it isn't entirely open source.

NASA chief technology officer Chris Kemp tells The Reg that as his engineers attempted to contribute additional Eucalyptus code to improve its ability to scale, they were unable to do so because some of the platform's code is open and some isn't. Their attempted contributions conflicted with code that was only available in a partially closed version of platform maintained by Eucalyptus Systems Inc., the commercial outfit run by the project's founders.

Instead, Kemp's team built their own compute engine and fabric controller from scratch. The new platform — dubbed Nova — has been open sourced under the Apache 2.0 license and is now part of the OpenStack project announced today by Rackspace.

OpenStack, Kemp says, is an effort to create a Linux-like ecosystem for so-called infrastructure clouds, which are online services that provide on-demand access to compute power and storage capable of scaling as needed. NASA is intent on building Nebula from open technologies not only to avoid the dreaded "vendor lock-in" but also to save a few dollars for the American taxpayer. "Nebula is designed to be both massively scalable and incredibly cheap," Kemp says. "You cannot certify commercial software in Nebula. We're not even going to think about that."

Eucalyptus — a platform that attempts to mimic Amazon's infrastructure cloud inside private data centers — was created as an open source project at the University of California, Santa Barbara. In the spring of 2009, the founders took the project commercial with the formation of Eucalyptus Systems. The company eventually adopted what CEO Marten Mickos — the former boss of MySQL — calls an "open core" model. With open core, an open code base is joined by a commercial product that includes proprietary software.

With Mickos installed at the helm of Eucalyptus Systems and the software platform finding its way into Mark Shuttleworth's Ubuntu Linux distro — that's why he called it Karmic Koala — Eucalyptus has won a fair amount of open source cred over the past two years. But some open source zealots have questioned whether an open core outfit is worthy of the open source name.

NASA — along with Eli Lilly — was one of the company's flagship customers. The word is that Nebula will eventually power websites and other services across not only NASA but the entire federal government, and though Eucalyptus repeatedly told us that an announcement related to this expansion across the government was on the way, it never actually arrived.

The company was not available to discuss NASA's switch from Eucalyptus to Nova.

NASA is working to build an infrastructure cloud that spans one million physical machines and 60 million servers — an enormous scale, to be sure — and according to Chris Kemp, Eucalyptus just wasn't designed to reach such levels. "With the architecture of the open source code in Eucalyptus, by our team's analysis, you couldn't get close to that," he says.

"Part of that is that Eucalyptus is a product. It's not a framework. If you need a faster queuing service or a faster database engine, all of that stuff is integrated directly into the Eucalyptus product. You can't pull it apart and replace the queuing engine or networking engine with other systems that are designed to scale better...When you're doing something at exascale, a product designed to work for hundreds of thousands of servers just doesn't work."

Though Eucalyptus was built to mimic the Amazon Web Services cloud — it uses the same APIs — the project's founders never claimed it would scale to Amazon-like levels. In fact, when the company was formed, CTO and University of California, Santa Barbara professor Rich Wolski said it wouldn't — though he indicated that at least part of this involved limitations beyond the software itself.

"One of the misconceptions about Eucalyptus is that it is able to allow an org to compete with Amazon," Wolski told us. "The Amazon AWS [Amazon Web Services] cloud is far more than a collection of software components. It operates on a gigantic scale, multiple time zones, multiple data centers, human resources that must be committed to maintain it so it can operate at that scale. It's not likely — maybe even impossible — that you're going to download something from the internet that is going to be able to operate at that scale. Eucalyptus can’t really be used for that purpose."

Security for virtualized datacentres

Next page: (Super) Nova

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Top 5 reasons to deploy VMware with Tegile
Data demand and the rise of virtualization is challenging IT teams to deliver storage performance, scalability and capacity that can keep up, while maximizing efficiency.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.