The account concept and usage database made billing integration straight forward. The API with CloudStack made integration into various external facing web applications simple enough. In my experience, customers appreciated the console proxy for initial set up and emergency situations.
We made money off of it. For our customers, it enabled them to spend a lot less money when compared to a full-blown infrastructure implementation, without drudging through the complexity of AWS.
With all that simplicity come limitations that need to be understood and planned for:
- Accounts, domains, and user accounts are set up with public cloud in mind, not private.
- The numerous, multi-layered drill-down menus make it difficult to find one simple knob to turn. It’s still easier to use than the competition but it used to be even simpler, in older versions of CloudStack.
- Cloud routers have always been lacking. They’re fine for public cloud applications but again, for private enterprise use cases, object-based firewalls are pretty important for large, complex set ups. If that sounds like too much of a lift, a description field would be a good Band-aid.
More than five years.
I’ve used, managed, and integrated it for about seven years in three different mid-sized companies. I started using CloudStack before Citrix acquired Cloud.com.