Former NASA CTO Chris Kemp explains his startup's appliance that manages commodity servers as a cloud resource. His plan: Out-innovate the competition.
(click image for larger view)
Slideshow: NASA, Microsoft Reveal Mars In Pictures
Chris Kemp resigned as chief technology officer at NASA on March 14 and launched Nebula, a company that will supply a new class of product, a controller for commodity cloud servers in the enterprise. After announcing the new company Wednesday, Kemp spoke with InformationWeek Editor at Large Charles Babcock about what will go into Nebula's appliance, what he thought of Vivek Kundra's resignation as federal CIO, and what his own experience at NASA was like. Kemp is CEO of Nebula and says its sole goal is to produce a product that manages sets of commodity servers as a private cloud.
InformationWeek: Let me take the discussion off the cloud for a moment to ask, were you surprised when federal CIO Vivek Kundra resigned in May?
Kemp: Yes, I was. Working for the government is a very difficult job. Few appreciate how little you can innovate from within the federal government. It's an institution designed for stability, not innovation. That's not a bad thing. But it makes being a change agent very difficult. As you get closer to an election, everything you do gets harder. It's viewed through a political lens. What may be the right thing to do gets viewed as something that's helping someone get re-elected. That's particularly difficult for change agents.
InformationWeek: How did you find your own experience inside a government agency?
Kemp: It was a great experience. Everyone should take time to serve in government or the military. I wish more people in NASA could go out and try to be entrepreneurs. If people could jump around to different companies, they would be able to see different infrastructures. When I left NASA, I left with no patents or special licenses. Everything we did became open source code. Once I resigned, I downloaded OpenStack [cloud provisioning open source code] just like everybody else. Too many contractors write into the contract that, if they solve the problem, then they own the software that they developed, while being paid by the taxpayer. They then go and sell it to another agency. That code should be open source. I'm just excited that there's so much interest in [NASA and Rackspace-sponsored] OpenStack. I hope everyone looks back someday and sees OpenStack as a valuable spinoff from NASA.
InformationWeek: What about trying to promote cloud computing in the federal government in a recessionary budget climate?
Kemp: All the budget stuff was a huge distraction. A lot of cloud stuff requires investment in staff training and change management. But most agencies are working under continuing resolutions that dole out a few more months of money. We didn't have the procurement or contracts in place to build the [NASA Nebula] cloud. The small amounts of money injected inhibited that.
InformationWeek: Are you happy to be back in the private sector?
Kemp: I am at heart an entrepreneur who somehow ended up in NASA. This is my fourth startup. I haven't made any money on any [of the previous three]. I'm still interested in doing something significant and successful. At NASA, we created Google Moon [Google's topographical maps of the moon built from NASA data] and Google Mars. We created the Microsoft Worldwide Telescope [a virtual telescope looking at NASA planetary image data]. We were trying to make massive amounts of data available [in remote data centers]. It inspired me to work on cloud computing at NASA.
Now that I'm outside NASA, I might be able to move the government toward cloud computing faster by having influence in the private sector. Even if Nebula has no government customers, it may have influence [on future government cloud decisions].
Multicloud Infrastructure & Application ManagementEnterprise cloud adoption has evolved to the point where hybrid public/private cloud designs and use of multiple providers is common. Who among us has mastered provisioning resources in different clouds; allocating the right resources to each application; assigning applications to the "best" cloud provider based on performance or reliability requirements.