Compared to Microsoft Azure, Rackspace OpenStack lacks an ecosystem and needs to have one. Azure has everything that comes along with the Microsoft ecosystem. Whereas the problem with OpenStack is the fact that it is not commonly used. Also, it's not easy to get into and understand. In contrast, with something like Azure, there's a massive community around it. It's a very quick and easy thing to learn in comparison. That's one of the biggest drawbacks of Rackspace OpenStack.

We make telecommunications-specific customizations. For us, network utilization is the primary factor. We joined the network virtualization functions to understand how they are managed and how the underlying cloud supports them. There are specific parameters that we can add to a checklist. The seamless integration between MySQL services and the rabbitMQ database can be revised during debugging.

Rackspace OpenStack is constantly changing with new services and features being released every six months. This quick release cycle makes it difficult to keep up with all of the changes. 

VMware has a side-to-side replication feature, which is still more mature than Rackspace OpenStack's which can't be used in a production environment. By making this feature called Freezer more mature, enterprises may be more likely to adopt Rackspace OpenStack.

OpenStack's UI, while user-friendly, could be improved to offer a more intuitive experience. Additionally, the storage solutions, aside from S3, seem to be limited or restricted in their options, and expanding these choices could be beneficial.

OpenStack is difficult for the novice in terms of beginning to use cloud tools. If you want to do some tasks, for example, if you want to create a domain in OpenStack, you must do that in command line. There isn't any GUI available, and new users might find the command line difficult to understand. OpenStack isn't so easy for people who don't practice. They need to simplify the product and make it more visual for beginners. 

Pricing Overview.

In terms of what needs to be improved, I would say the support.

You're asking for the Rackspace OpenStack and I'm working on the open source OpenStack. Rackspace might have some good support but the open source OpenStack doesn't have support because there are too many versions coming and too many people are customizing it. That's why the support is a problem for open source versions.

It needs to develop a very good user interface which can compete with the public cloud.

In the next release, I would like to see more of the load balancing technologies and applications from the public cloud which OpenStack doesn't have right now.

It could use more examples in different languages (API use cases).