We went to Philadelphia recently for the Platform, Infrastructure and Networking Group (PING) Meetup at the SunGard office. Aside from being a great opportunity to meet some of the Philadelphia clouderati (and have an authentic cheesesteak sandwich…), it was a chance to hear about SunGard’s work with CloudStack from a principle engineer of cloud services, Chip Childers.
SunGard’s cloud work didn’t start with CloudStack. In 2010, when the company was initially examining its options, the company decided to roll its own cloud orchestration layer. Why? At the time, Childers said that the options weren’t what SunGard was looking for – so they decied it’d be easier to start from scratch than adopt existing options.
The homebrew solution from SunGard went live in 2011, and SunGard’s homebrew was handling multiple regions and growing capacity. Its team started focusing on higher-level solutions. At the same time, SunGard noticed that the open source cloud offerings had been maturing quickly.
SunGard decided to have a “bake-off” between three of the open source IaaS platforms: CloudStack, OpenNebula, and OpenStack. The criteria? Ease of installation/setup, a code review, and licensing and governance of the projects.
Timing is Everything
Childers says that SunGard liked that CloudStack “just worked,” and found its code quality and feature quality to be high. The problem? SunGard had reservations about the GPLv3 and that the project was governed by a single corporate entity without a clear governance structure going forward. Without those red flags, CloudStack would be a clear choice....